Acx Series

Junos OS
ACX Series Universal Access Router Configuration

Guide
Release
12.3X51-D10
Published: 2013-03-15
Copyright 2013, Juniper Networks, Inc.
Juniper Networks, Inc.

1194 North Mathilda Avenue
Sunnyvale, California 94089
USA
408-745-2000
www.juniper.net
This product includes the Envoy SNMP Engine, developed by Epilogue Technology, an Integrated Systems Company. Copyright 1986-1997,
Epilogue Technology Corporation. All rights reserved. This program and its documentation were developed at private expense, and no part
of them is in the public domain.
This product includes memory allocation software developed by Mark Moraes, copyright 1988, 1989, 1993, University of Toronto.
This product includes FreeBSD software developed by the University of California, Berkeley, and its contributors. All of the documentation
and software included in the 4.4BSD and 4.4BSD-Lite Releases is copyrighted by the Regents of the University of California. Copyright
1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994. The Regents of the University of California. All rights reserved.
GateD software copyright 1995, the Regents of the University. All rights reserved. Gate Daemon was originated and developed through
release 3.0 by Cornell University and its collaborators. Gated is based on Kirtons EGP, UC Berkeleys routing daemon (routed), and DCNs
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, Junos, Steel-Belted Radius, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the United
States and other countries. The Juniper Networks Logo, the Junos logo, and JunosE are trademarks of Juniper Networks, Inc. All other
trademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners.
Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify,
transfer, or otherwise revise this publication without notice.
Products made or sold by Juniper Networks or components thereof might be covered by one or more of the following patents that are
owned by or licensed to Juniper Networks: U.S. Patent Nos. 5,473,599, 5,905,725, 5,909,440, 6,192,051, 6,333,650, 6,359,479, 6,406,312,
6,429,706, 6,459,579, 6,493,347, 6,538,518, 6,538,899, 6,552,918, 6,567,902, 6,578,186, and 6,590,785.
Junos OS ACX Series Universal Access Router Configuration Guide

Release 12.3X51-D10
All rights reserved.
The information in this document is current as of the date on the title page.
YEAR 2000 NOTICE
Juniper Networks hardware and software products are Year 2000 compliant. Junos OS has no known time-related limitations through the
year 2038. However, the NTP application is known to have some difficulty in the year 2036.
END USER LICENSE AGREEMENT

The Juniper Networks product that is the subject of this technical documentation consists of (or is intended for use with) Juniper Networks
software. Use of such software is subject to the terms and conditions of the End User License Agreement (EULA) posted at
http://www.juniper.net/support/eula.html. By downloading, installing or using such software, you agree to the terms and conditions
of that EULA.
ii
Table of Contents
About the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix
Documentation and Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix
Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix
Using the Examples in This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix
Merging a Full Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx
Merging a Snippet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx
Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi
Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiii
Requesting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiii
Self-Help Online Tools and Resources . . . . . . . . . . . . . . . . . . . . . . . . . . xxiii
Opening a Case with JTAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiv
Part 1
Overview
Chapter 1
Router Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
ACX Series Universal Access Router Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
ACX Series Router Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Junos OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Mobile Backhaul . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Junos Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Protocols and Applications Supported by the ACX Routers . . . . . . . . . . . . . . . . . . . 5
ACX1000 and ACX1100 Routers Hardware and CLI Terminology Mapping . . . . . . . 11
ACX1000 Routers Hardware and CLI Terminology Mapping . . . . . . . . . . . . . . 11
ACX1100 Routers Hardware and CLI Terminology Mapping . . . . . . . . . . . . . . . 12
ACX2000 and ACX2100 Routers Hardware and CLI Terminology Mapping . . . . . 14
ACX2000 Hardware and CLI Terminology Mapping . . . . . . . . . . . . . . . . . . . . 14
ACX2100 Hardware and CLI Terminology Mapping . . . . . . . . . . . . . . . . . . . . . 15
ACX4000 Routers Hardware and CLI Terminology Mapping . . . . . . . . . . . . . . . . . 17
Router Hardware Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Part 2
Configuration
Chapter 2
Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Classifiers and Rewrite Rules at the Global and Physical Interface Levels
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
CoS on ACX Series Universal Access Routers Features Overview . . . . . . . . . . . . . 24
Gigabit Ethernet Autonegotiation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
IEEE 1588v2 PTP Boundary Clock Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
IEEE 1588v2 PTP Boundary Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Clock Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
iii
ACX Series Universal Access Router Configuration Guide
IEEE 1588v2 Precision Timing Protocol (PTP) on ACX Series Universal Access
Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Inverse Multiplexing for ATM (IMA) Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
IPv6 Support on ACX Series Universal Access Routers . . . . . . . . . . . . . . . . . . . . . 30
Pseudowire Overview for ACX Series Universal Access Routers . . . . . . . . . . . . . . 33
Synchronous Ethernet Overview on the ACX Series Universal Access Routers . . . 34
TDM CESoPSN Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
TDM CESoPSN on ACX Series Routers Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Channelization up to the DS0 Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Protocol Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Packet Latency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
CESoPSN Encapsulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
CESoPSN Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
show Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
CESoPSN Pseudowires . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Traffic Policing Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Congestion Management for IP Traffic Flows . . . . . . . . . . . . . . . . . . . . . . . . . 37
Traffic Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Traffic Color Marking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Forwarding Classes and PLP Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Policer Application to Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Understanding PoE on ACX Series Universal Access Routers . . . . . . . . . . . . . . . . . 41
ACX2000 PoE Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
PoE Classes and Power Ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
PoE Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Chapter 3
Autoinstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
ACX Series Autoinstallation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Supported Autoinstallation Interfaces and Protocols . . . . . . . . . . . . . . . . . . . 45
Typical Autoinstallation Process on a New Router . . . . . . . . . . . . . . . . . . . . . 46
Before You Begin Autoinstallation on an ACX Series Universal Access Router . . . 47
Autoinstallation Configuration of ACX Series Universal Access Routers . . . . . . . . 48
Verifying Autoinstallation on ACX Series Universal Access Routers . . . . . . . . . . . 49
USB Autoinstallation on ACX Series Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Chapter 4
CoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
CoS on ACX Series Universal Access Routers Features Overview . . . . . . . . . . . . . 53
CoS on ATM IMA Pseudowire Interfaces Overview . . . . . . . . . . . . . . . . . . . . . . . . . 54
ATM Policing (Cell Based) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
ATM Shaping (Cell Based) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Fixed Classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Understanding CoS CLI Configuration Statements on ACX Series Universal
Access Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Configuring CoS on ACX Series Universal Access Routers . . . . . . . . . . . . . . . . . . . 58
Configuring Classifiers and Rewrite Rules at the Global and Physical Interface
Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Configuring Fixed Classification on an ATM IMA Pseudowire . . . . . . . . . . . . . . . . 64
Configuring Policing on an ATM IMA Pseudowire . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Configuring an Input Policer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Configuring the ATM IMA Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
iv
Table of Contents
Configuring Shaping on an ATM IMA Pseudowire . . . . . . . . . . . . . . . . . . . . . . . . . 68

Example: Configuring Fixed Classification on an ATM IMA Pseudowire . . . . . . . . 69
Example: Configuring Policing on an ATM IMA Pseudowire . . . . . . . . . . . . . . . . . . 71
Example: Configuring Shaping on an ATM IMA Pseudowire . . . . . . . . . . . . . . . . . . 76
Chapter 5
Firewall Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Standard Firewall Filter Match Conditions and Actions on ACX Series Routers
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Standard Firewall Filter Match Conditions for IPv4 Traffic on ACX Series
Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Standard Firewall Filter Match Conditions for MPLS Traffic on ACX Series
Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Standard Firewall Filter Terminating Actions on ACX Series Routers . . . . . . . . . . 86
Standard Firewall Filter Nonterminating Actions on ACX Series Routers . . . . . . . 88
Filter-Based Forwarding for Routing Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Forwarding Table Filters for Routing Instances on ACX Series Routers . . . . . . . . . 91
Chapter 6
Interfaces and Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

BERT Support on CT1 and CE1 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Channelized OC3/STM1 (Multi-Rate) Circuit Emulation MIC with SFP
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Checklist for Monitoring Fast Ethernet and Gigabit Ethernet Interfaces . . . . . . . . 94
Checklist for Monitoring T1 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Configuring the Media MTU on ACX Series Routers . . . . . . . . . . . . . . . . . . . . . . . . 96
Media MTU Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
How to Configure the Media MTU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Encapsulation Overhead by Encapsulation Type . . . . . . . . . . . . . . . . . . . . . . 97
Media MTU Sizes by Interface Type for ACX Series Routers . . . . . . . . . . . . . . 98
Gigabit Ethernet Autonegotiation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Understanding Interfaces on ACX Series Universal Access Routers . . . . . . . . . . . 99
T1 and E1 Time-Division Multiplexing (TDM) Interfaces . . . . . . . . . . . . . . . . 100
Inverse Multiplexing for ATM (IMA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Gigabit Ethernet interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Understanding Encapsulation on an Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
SAToP Emulation on T1 and E1 Interfaces Overview . . . . . . . . . . . . . . . . . . . . . . . 102
User-Defined Alarm Relay Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Alarm Contact Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Alarm Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Alarm Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Configuring Chassis Alarm Relays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Configuring Chassis Alarm Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Configuring Chassis Alarm Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Chapter 7
Layer 2 and Layer 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Configuring Interfaces for Layer 2 Circuits Overview . . . . . . . . . . . . . . . . . . . . . . . 107
Configuring the Address for the Neighbor of the Layer 2 Circuit . . . . . . . . . . . . . . 108
Configuring the Neighbor Interface for the Layer 2 Circuit . . . . . . . . . . . . . . . . . . 108
Configuring a Community for the Layer 2 Circuit . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Configuring the Control Word for Layer 2 Circuits . . . . . . . . . . . . . . . . . . . . . . . . . 109
Configuring the Encapsulation Type for the Layer 2 Circuit Neighbor Interface . . 110
Configuring the MTU Advertised for a Layer 2 Circuit . . . . . . . . . . . . . . . . . . . . . . . 111

Configuring the Protect Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Configuring the Virtual Circuit ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Configuring the Interface Encapsulation Type for Layer 2 Circuits . . . . . . . . . . . . . 112
Configuring Layer 2 Circuits over Both RSVP and LDP LSPs . . . . . . . . . . . . . . . . . 113
Enabling the Layer 2 Circuit When the MTU Does Not Match . . . . . . . . . . . . . . . . 114
Enabling the Layer 2 Circuit When the Encapsulation Does Not Match . . . . . . . . 114
Chapter 8
MPLS, VPNs, and Pseudowires . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

MPLS Overview for ACX Series Universal Access Routers . . . . . . . . . . . . . . . . . . . 115
TTL Processing on Incoming MPLS Packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
ATM Pseudowire Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Ethernet Pseudowire Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
TDM Pseudowires Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Redundant Pseudowires for Layer 2 Circuits and VPLS . . . . . . . . . . . . . . . . . . . . . 121
Types of Redundant Pseudowire Configurations . . . . . . . . . . . . . . . . . . . . . . 121
Pseudowire Failure Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Configuring Redundant Pseudowires for Layer 2 Circuits and VPLS . . . . . . . . . . . 123
Configuring Pseudowire Redundancy on the PE Router . . . . . . . . . . . . . . . . 123
Configuring the Switchover Delay for the Pseudowires . . . . . . . . . . . . . . . . . 124
Configuring a Revert Time for the Redundant Pseudowire . . . . . . . . . . . . . . 124
Configuring the Pseudowire Status TLV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Example: TDM Pseudowire Base Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Example: ATM Pseudowire Base Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Example: Ethernet Pseudowire Base Configuration . . . . . . . . . . . . . . . . . . . . . . . 133
Example: Configuring the Pseudowire Status TLV . . . . . . . . . . . . . . . . . . . . . . . . 136
Chapter 9
Network Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Real-Time Performance Monitoring on ACX Series Routers . . . . . . . . . . . . . . . . . 139
Standard SNMP MIBs Supported by Junos OS . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Juniper Networks Enterprise-Specific MIBs and Supported Devices . . . . . . . . . . 155
Chapter 10
Operations, Administration, and Management (OAM) . . . . . . . . . . . . . . . . 167

Understanding Ethernet OAM Link Fault Management for ACX Series
Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Configuring Ethernet Local Management Interface . . . . . . . . . . . . . . . . . . . . . . . 169
Ethernet Local Management Interface Overview . . . . . . . . . . . . . . . . . . . . . 169
Configuring the Ethernet Local Management Interface . . . . . . . . . . . . . . . . . 171
Configuring an OAM Protocol (CFM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Assigning the OAM Protocol to an EVC . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Enabling E-LMI on an Interface and Mapping CE VLAN IDs to an
EVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Example E-LMI Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Configuring PE1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Configuring PE2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
vi
Table of Contents
Configuring Two UNIs Sharing the Same EVC . . . . . . . . . . . . . . . . . . . . . 176

Ethernet Frame Delay Measurements Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 177
ITU-T Y.1731 Frame Delay Measurement Feature . . . . . . . . . . . . . . . . . . . . . . 177
Ethernet CFM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Ethernet Frame Delay Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
One-Way Ethernet Frame Delay Measurement . . . . . . . . . . . . . . . . . . . . . . . 178
1DM Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
1DM Reception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
One-Way ETH-DM Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
One-Way ETH-DM Frame Counts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Synchronization of System Clocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Two-Way Ethernet Frame Delay Measurement . . . . . . . . . . . . . . . . . . . . . . . 180
DMM Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
DMR Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
DMR Reception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Two-Way ETH-DM Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Two-Way ETH-DM Frame Counts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Choosing Between One-Way and Two-Way ETH-DM . . . . . . . . . . . . . . . . . . 181
Restrictions for Ethernet Frame Delay Measurement . . . . . . . . . . . . . . . . . . . 181
Ethernet Frame Loss Measurement Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Ethernet OAM Connectivity Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . 183
IEEE 802.1ag OAM Connectivity Fault Management Overview . . . . . . . . . . . . . . 184
Connectivity Fault Management Key Elements . . . . . . . . . . . . . . . . . . . . . . . 185
Example: Configuring IEEE 802.3ah OAM Support for an Interface . . . . . . . . . . . 186
Ethernet Synthetic Loss Measurement Overview . . . . . . . . . . . . . . . . . . . . . . . . . 189
Transmission of ETH-SLM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Initiation and Transmission of SLM Requests . . . . . . . . . . . . . . . . . . . . . . . . 190
Reception of SLMs and Transmission of SLRs . . . . . . . . . . . . . . . . . . . . . . . . 191
Reception of SLRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Computation of Frame Loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Format of ETH-SLM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
SLM PDU Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
SLR PDU Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Data Iterator TLV Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Guidelines for Configuring ETH-SLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Scenarios for Configuration of ETH-SLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Upstream MEP in MPLS Tunnels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Downstream MEP in Ethernet Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Managing ETH-SLM Statistics and ETH-SLM Frame Counts . . . . . . . . . . . . . . . . 197
Displaying ETH-SLM Statistics Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Displaying ETH-SLM Statistics and Frame Counts . . . . . . . . . . . . . . . . . . . . 197
Displaying ETH-SLM Frame Counts for MEPs by Enclosing CFM Entity . . . . 198
Displaying ETH-SLM Frame Counts for MEPs by Interface or Domain
Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Clearing ETH-SLM Statistics and Frame Counts . . . . . . . . . . . . . . . . . . . . . . 199
Clearing Iterator Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Starting a Proactive ETH-SLM Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Configuring MEP Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Configuring an Iterator Profile for ETH-SLM . . . . . . . . . . . . . . . . . . . . . . . . . 202
vii
Associating the Iterator Profile with MEPs for ETH-SLM . . . . . . . . . . . . . . . 203

Starting an On-Demand ETH-SLM Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Chapter 11
Routing Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

IPv6 Support on ACX Series Universal Access Routers . . . . . . . . . . . . . . . . . . . . 207
Layer 3 VPNs for IPv4 and IPv6 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Configuring Multiprotocol BGP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Enabling MP-BGP for the IPv4 Address Family . . . . . . . . . . . . . . . . . . . . . . . 212
Enabling MP-BGP for the IPv6 Address Family . . . . . . . . . . . . . . . . . . . . . . . 212
Enabling MP-BGP for Address Families Other than Unicast IPv4 . . . . . . . . . 213
Enabling MP-BGP and VPN Signaling for the IPv4 Address Family . . . . . . . . 213
Enabling MP-BGP and VPN Signaling for the IPv6 Address Family . . . . . . . 214
Chapter 12
Time Division Multiplexing (TDM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

Configuring CESoPSN Encapsulation on DS Interfaces . . . . . . . . . . . . . . . . . . . . 215
Configuring CE1 Channels Down to DS Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . 216
Configuring SAToP Emulation on Channelized T1 and E1 Interfaces . . . . . . . . . . . 217
Setting the T1/E1 Emulation Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Configuring One Full T1 or E1 Interface on Channelized T1 and E1
Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Setting the SAToP Encapsulation Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Configure the Layer 2 Circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Configuring Inverse Multiplexing for ATM (IMA) . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Configuring E1 BERT Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Configuring T1 BERT Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Configuring E1 Loopback Capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Example: Configuring E1 Loopback Capability . . . . . . . . . . . . . . . . . . . . . . . . 233
Configuring T1 Loopback Capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Chapter 13
Timing and Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

Automatic Clock Selection Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Clock Source Selection Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Clock Selection and Quality Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Selection Mode for the Incoming ESMC Quality . . . . . . . . . . . . . . . . . . . . . . 238
Clock Sources for the ACX Series Universal Access Routers . . . . . . . . . . . . . . . . 239
External Clock Synchronization Overview for ACX Series Routers . . . . . . . . . . . 240
Automatic Clock Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Clock Source Selection Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Configuring External Clock Synchronization for ACX Series Routers . . . . . . . . . . 242
Global Positioning System (GPS) and the ACX Series Routers . . . . . . . . . . . . . . 248
PTP over Ethernet on ACX Series Routers Overview . . . . . . . . . . . . . . . . . . . . . . 248
Guidelines for Configuring PTP over Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Configuring Precision Time Protocol Clocking . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Configuring a PTP Master Boundary Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Configuring the PTP Master Boundary Clock Parameters . . . . . . . . . . . . . . 254
Configuring a PTP Master Boundary Clock Interface . . . . . . . . . . . . . . . . . . 256
Configuring a PTP Slave Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
Configuring the PTP Slave Clock Parameters . . . . . . . . . . . . . . . . . . . . . . . . 257
Configuring the PTP Slave Clock Interface . . . . . . . . . . . . . . . . . . . . . . . . . . 259
G.703 2.048MHz Signal Type for BITS Interfaces Overview . . . . . . . . . . . . . . . . . 259
viii
Table of Contents
Configuring PTP Multicast Master and Slave Ports for Ethernet

Encapsulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
Configuring the PTP over Ethernet Master Boundary Clock Parameters . . . 260
Configuring the PTP over Ethernet Master Boundary Clock Interface . . . . . 262
Configuring the PTP over Ethernet Slave Clock Parameters . . . . . . . . . . . . . 263
Configuring the PTP over Ethernet Slave Clock Interface . . . . . . . . . . . . . . . 264
Configuring PTP Dynamic Ports for Ethernet Encapsulation . . . . . . . . . . . . . . . . 265
Example: Configuring PTP over Ethernet for Multicast Master, Slave, and Dynamic
Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Example: Configuring a PTP Boundary Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Example: Configuring a PTP Boundary Clock With Unicast Negotiation . . . . . . . 275
Example: Configuring an Ordinary Slave Clock With Unicast-Negotiation . . . . . 279
Example: Configuring an Ordinary Slave Clock Without Unicast-Negotiation . . . 281
Example: Configuring PoE on ACX2000 Routers . . . . . . . . . . . . . . . . . . . . . . . . . 283
Example: Disabling a PoE Interface on ACX2000 Routers . . . . . . . . . . . . . . . . . . 287
Chapter 14
Upgrade and Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289

ACX Series Autoinstallation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
Supported Autoinstallation Interfaces and Protocols . . . . . . . . . . . . . . . . . 290
Typical Autoinstallation Process on a New Router . . . . . . . . . . . . . . . . . . . . 290
Dual-Root Partitioning ACX Series Universal Access Routers Overview . . . . . . . 291
Boot Media and Boot Partition on the ACX Series Routers . . . . . . . . . . . . . . 292
Important Features of the Dual-Root Partitioning Scheme . . . . . . . . . . . . . 292
Understanding How the Primary Junos OS Image with Dual-Root Partitioning
Recovers on the ACX Series Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
Junos OS Release 12.2 or Later Upgrades with Dual-Root Partitioning on ACX
Series Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
Installing Junos OS Using a USB Storage Device on ACX Series Routers . . . . . . 295
Installing Junos OS Upgrades from a Remote Server on ACX Series Routers . . . 296
Example: Installing Junos OS and Configuring a Dual-Root Partition on ACX
Series Routers Using the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
Hardware Architecture Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
Hardware Overview (ACX Series, M Series, MX Series, T Series, and TX Matrix
Routers) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
System Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
Storage Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Boot Sequence (ACX Series Routers) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Routing Engines and Storage Media Names (ACX Series, M Series, MX Series,
PTX Series, T Series, TX Matrix, TX Matrix Plus, and JCS 1200 Routers) . . . 303
Upgrading Software Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
Load and Commit the Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Checking the Current Configuration and Candidate Software Compatibility . . . 308
Understanding System Snapshot on an ACX Series Router . . . . . . . . . . . . . . . . 308
Example: Taking a Snapshot of the Software and Configuration . . . . . . . . . . . . 309
Chapter 15
Junos Configuration Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313

Key Configuration Statements Supported on ACX Series Routers . . . . . . . . . . . . 313
Chapter 16
Configuration Statement Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321

Key Configuration Statement Hierarchies Supported on ACX Series Routers . . . 321
ix
Part 3
Administration
Chapter 17
Monitoring Commands for the ACX Universal Access Router . . . . . . . . . . 325

clear oam ethernet connectivity-fault-management sla-iterator-statistics . . . . 326
clear oam ethernet connectivity-fault-management
synthetic-loss-measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
clear dhcp relay statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
clear dhcp relay binding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
monitor ethernet synthetic-loss-measurement . . . . . . . . . . . . . . . . . . . . . . . . . . 333
restart chassis-control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
request chassis feb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
request system snapshot (ACX Series) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
show bgp neighbor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
show bgp replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
show bgp summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
show chassis alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
show chassis craft-interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
show chassis environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
show chassis feb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
show chassis firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
show chassis fpc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
show chassis hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484
show chassis mac-addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588
show chassis pic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594
show chassis routing-engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607
show chassis synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627
show class-of-service interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631
show class-of-service system-defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657
show dhcp relay statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658
show dhcp relay binding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 661
show interfaces (ATM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 666
show interfaces (T1, E1, or DS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 701
show interfaces statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 726
show isis database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 739
show isis hostname . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746
show isis interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747
show isis overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 752
show isis route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755
show isis spf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 759
show isis statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 764
show oam ethernet connectivity-fault-management interfaces . . . . . . . . . . . . . 767
show oam ethernet connectivity-fault-management mep-statistics . . . . . . . . . 778
show oam ethernet connectivity-fault-management mep-database . . . . . . . . . 791
show oam ethernet connectivity-fault-management sla-iterator-statistics . . . 802
show oam ethernet connectivity-fault-management
synthetic-loss-statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807
show ospf database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 810
show ospf3 database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 819
show (ospf | ospf3) interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 830
Table of Contents
show (ospf | ospf3) io-statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 836

show (ospf | ospf3) log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 838
show (ospf | ospf3) neighbor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 842
show (ospf | ospf3) overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 849
show (ospf | ospf3) route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 854
show (ospf | ospf3) statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 860
show poe controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 864
show poe telemetries interface (ACX2000 Routers) . . . . . . . . . . . . . . . . . . . . . . 867
show ptp clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 869
show ptp global-information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 872
show ptp lock-status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 875
show ptp statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 877
show route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 879
show route active-path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 885
show route advertising-protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 890
show route all . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 895
show route aspath-regex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 897
show route best . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 899
show route brief . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 902
show route community . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 904
show route community-name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 906
show route damping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 908
show route detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 914
show route exact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 929
show route export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 931
show route extensive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 933
show route flow validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 948
show route forwarding-table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 950
show route hidden . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 964
show route inactive-path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 967
show route inactive-prefix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 971
show route instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973
show route next-hop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 980
show route no-community . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 986
show route output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 989
show route protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 993
show route receive-protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1005
show route table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1014
show route terse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1025
show system autoinstallation status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1028
show validation database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1030
show validation group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1032
show validation replication database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1034
show validation session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1036
show validation statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1039
test interface e1-bert-start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1041
test interface e1-bert-stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1042
test interface t1-bert-start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1043
test interface t1-bert-stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1044
xi
Part 4
Troubleshooting
Chapter 18
Troubleshooting Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1047

CT1 and CE1 Interfaces Alarms, Errors, and Defects . . . . . . . . . . . . . . . . . . . . . . 1047
Troubleshooting PoE Interfaces on ACX2000 Universal Access Routers . . . . . 1048
Part 5
Index
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1051
xii
List of Figures
Part 1
Overview
Chapter 1
Router Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Figure 1: ACX Series Router Packet Forwarding and Data Flow . . . . . . . . . . . . . . . . 4
Figure 2: ACX1000 Interface Port Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Figure 3: ACX1100 Interface Port Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Figure 4: ACX2000 Interface Port Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Figure 5: ACX2100 Interface Port Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Figure 6: ACX4000 Interface Port Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Part 2
Configuration
Chapter 2
Figure 7: Boundary Clocks in a Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Figure 8: Network Traffic and Burst Rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Chapter 6

Figure 9: Pseudowire Encapsulation with SAToP . . . . . . . . . . . . . . . . . . . . . . . . . 102
Chapter 8
MPLS, VPNs, and Pseudowires . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Figure 10: TTL Processing on Incoming MPLS Packets . . . . . . . . . . . . . . . . . . . . . 118
Chapter 10
Operations, Administration, and Management (OAM) . . . . . . . . . . . . . . . . 167

Figure 11: Scope of the E-LMI Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Figure 12: E-LMI Configuration for a Point-to-Point EVC (SVLAN) Monitored by
CFM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Figure 13: Relationship of MEPs, MIPs, and Maintenance Domain Levels . . . . . . . 178
Figure 14: Relationship Among MEPs, MIPs, and Maintenance Domain Levels . . 185
Figure 15: Relationship Among Bridges, Maintenance Domains, Maintenance
Associations, and MEPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Chapter 12
Time Division Multiplexing (TDM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

Figure 16: Pseudowire Encapsulation with SAToP . . . . . . . . . . . . . . . . . . . . . . . . . 218
Figure 17: Remote and Local E1 Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Figure 18: Remote and Local T1 Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Chapter 14

Figure 19: Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
xiii
xiv
List of Tables
About the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix
Table 1: Notice Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi
Table 2: Text and Syntax Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi
Part 1
Overview
Chapter 1
Router Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Table 3: Protocols and Applications Supported by ACX Series Routers . . . . . . . . . 5
Table 4: CLI Equivalents of Terms Used in Documentation for ACX1000
Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Table 9: Major Router Hardware Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Part 2
Configuration
Chapter 2
Table 10: PoE Specifications for the ACX2000 Routers . . . . . . . . . . . . . . . . . . . . . 41
Table 11: ACX2000 Universal Access Router PoE Specifications . . . . . . . . . . . . . . 42
Table 12: PoE Configuration Options and Default Settings . . . . . . . . . . . . . . . . . . . 43
Chapter 5
Firewall Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Table 13: Standard Firewall Filter Match Conditions by Protocol Family for ACX
Series Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Table 14: Standard Firewall Filter Action Categories for ACX Series Routers . . . . . 82
Table 15: Standard Firewall Filter Match Conditions for IPv4 Traffic on ACX Series
Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Table 16: Standard Firewall Filter Match Conditions for MPLS Traffic on ACX
Series Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Table 17: Terminating Actions for Standard Firewall Filters on ACX Series
Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Table 18: Nonterminating Actions for Standard Firewall Filters on ACX Series
Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Chapter 6
xv
Table 19: Platform Support for Channelized OC3/STM1 (Multi-Rate) Circuit

Emulation MIC with SFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Table 20: Checklist for Monitoring Fast Ethernet and Gigabit Ethernet
Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Table 21: Checklist for Monitoring T1 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Table 22: Encapsulation Overhead by Encapsulation Type . . . . . . . . . . . . . . . . . . 97
Table 23: Media MTU Sizes by Interface Type for ACX Series Routers . . . . . . . . . . 98
Chapter 9
Network Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Table 24: Standard MIBs Supported on Devices Running Junos OS . . . . . . . . . . 140
Table 25: Enterprise-Specific MIBs and Supported Devices . . . . . . . . . . . . . . . . . 156
Chapter 13
Timing and Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

Table 26: Components of the PoE Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 284
Chapter 14

Table 27: Routing Engines and Storage Media Names (ACX Series, M Series, MX
Series, T Series, TX Matrix, TX Matrix Plus, and JCS 1200 Routers) . . . . . . . 303
Part 3
Administration
Chapter 17
Monitoring Commands for the ACX Universal Access Router . . . . . . . . . . 325

Table 28: clear dhcp relay statistics Output Fields . . . . . . . . . . . . . . . . . . . . . . . . 329
Table 29: monitor ethernet synthetic-loss-measurement Output Fields . . . . . . 335
Table 30: show bgp neighbor Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
Table 31: show bgp replication Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
Table 32: show bgp summary Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
Table 33: show chassis alarms Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
Table 34: show chassis craft-interface Output Fields . . . . . . . . . . . . . . . . . . . . . 378
Table 35: show chassis environment Output Fields . . . . . . . . . . . . . . . . . . . . . . . 396
Table 36: show chassis feb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
Table 37: show chassis firmware Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . 448
Table 38: show chassis fpc Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463
Table 39: Routing Engines Displaying DIMM Information . . . . . . . . . . . . . . . . . . 486
Table 40: show chassis hardware Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . 489
Table 41: show chassis mac-addresses Output Fields . . . . . . . . . . . . . . . . . . . . . 589
Table 42: show chassis pic Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597
Table 43: show chassis routing-engine Output Fields . . . . . . . . . . . . . . . . . . . . . 609
Table 44: show chassis synchronization Output Fields . . . . . . . . . . . . . . . . . . . . 628
Table 45: show class-of-service interface Output Fields . . . . . . . . . . . . . . . . . . . 632
Table 46: show class-of-service system-defaults Output Fields . . . . . . . . . . . . . 657
Table 47: show dhcp relay statistics Output Fields . . . . . . . . . . . . . . . . . . . . . . . 659
Table 48: show dhcp relay binding Output Fields . . . . . . . . . . . . . . . . . . . . . . . . 662
Table 49: ATM show interfaces Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . 666
Table 50: T1 or E1 show interfaces Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . 702
Table 51: show isis database Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 740
Table 52: show isis hostname Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746
Table 53: show isis interface Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748
Table 54: show isis overview Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 752
Table 55: show isis route Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755
xvi
List of Tables
Table 56: show isis spf Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 759

Table 57: show isis statistics Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 765
Table 58: show oam ethernet connectivity-fault-management interfaces Output
Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 768
Table 59: show oam ethernet connectivity-fault-management delay-statistics
and mep-statistics Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 779
Table 60: show oam ethernet connectivity-fault-management mep-database
Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 792
Table 61: show oam ethernet connectivity-fault-management
sla-iterator-statistics Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 802
Table 62: show oam ethernet connectivity-fault-management
synthetic-loss-statistics Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 808
Table 63: show ospf database Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 811
Table 64: show ospf3 database Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . 820
Table 65: show (ospf | ospf3) interface Output Fields . . . . . . . . . . . . . . . . . . . . . 831
Table 66: show (ospf | ospf3) io-statistics Output Fields . . . . . . . . . . . . . . . . . . 836
Table 67: show (ospf | ospf3) log Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . 838
Table 68: show (ospf | ospf3) neighbor Output Fields . . . . . . . . . . . . . . . . . . . . 843
Table 69: show ospf overview Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . 849
Table 70: show (ospf | ospf3) route Output Fields . . . . . . . . . . . . . . . . . . . . . . . . 855
Table 71: show (ospf | ospf3) statistics Output Fields . . . . . . . . . . . . . . . . . . . . . 860
Table 72: show poe controller Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . 864
Table 73: show poe telemetries interface Output Fields . . . . . . . . . . . . . . . . . . . 867
Table 74: show ptp clock Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 869
Table 75: show ptp global-information Output Fields . . . . . . . . . . . . . . . . . . . . . 872
Table 76: show ptp lock-status Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . 875
Table 77: show ptp statistics Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 877
Table 78: show route Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 880
Table 79: show route advertising-protocol Output Fields . . . . . . . . . . . . . . . . . . . 891
Table 80: show route damping Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . 908
Table 81: show route detail Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 914
Table 82: Next-hop Types Output Field Values . . . . . . . . . . . . . . . . . . . . . . . . . . . 918
Table 83: State Output Field Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 920
Table 84: Communities Output Field Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . 922
Table 85: show route export Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 931
Table 86: show route extensive Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . 933
Table 87: show route flow validation Output Fields . . . . . . . . . . . . . . . . . . . . . . . 948
Table 88: show route forwarding-table Output Fields . . . . . . . . . . . . . . . . . . . . . 952
Table 89: show route instance Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973
Table 90: show route receive-protocol Output Fields . . . . . . . . . . . . . . . . . . . . 1005
Table 91: show route terse Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1025
Table 92: show system autoinstallation status Output Fields . . . . . . . . . . . . . . 1028
Table 93: show validation database Output Fields . . . . . . . . . . . . . . . . . . . . . . . 1031
Table 94: show validation group Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . 1032
Table 95: show validation replication database Output Fields . . . . . . . . . . . . . 1035
Table 96: show validation session Output Fields . . . . . . . . . . . . . . . . . . . . . . . . 1036
Table 97: show validation statistics Output Fields . . . . . . . . . . . . . . . . . . . . . . . 1039
xvii
Part 4
Troubleshooting
Chapter 18
Troubleshooting Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1047

Table 98: CT1 and CE1 Interface Alarms and Error Definitions . . . . . . . . . . . . . . 1047
Table 99: Troubleshooting a PoE Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1048
xviii
About the Documentation
Documentation and Release Notes on page xix
Supported Platforms on page xix
Using the Examples in This Manual on page xix
Documentation Conventions on page xxi
Documentation Feedback on page xxiii
Requesting Technical Support on page xxiii
Documentation and Release Notes
To obtain the most current version of all Juniper Networks technical documentation,
see the product documentation page on the Juniper Networks website at
http://www.juniper.net/techpubs/.
If the information in the latest release notes differs from the information in the
documentation, follow the product Release Notes.
Juniper Networks Books publishes books by Juniper Networks engineers and subject
matter experts. These books go beyond the technical documentation to explore the
nuances of network architecture, deployment, and administration. The current list can
be viewed at http://www.juniper.net/books.
Supported Platforms
For the features described in this document, the following platforms are supported:
ACX Series
Using the Examples in This Manual

If you want to use the examples in this manual, you can use the load merge or the load
merge relative command. These commands cause the software to merge the incoming
configuration into the current candidate configuration. The example does not become
active until you commit the candidate configuration.
If the example configuration contains the top level of the hierarchy (or multiple
hierarchies), the example is a full example. In this case, use the load merge command.
xix
If the example configuration does not start at the top level of the hierarchy, the example
is a snippet. In this case, use the load merge relative command. These procedures are
described in the following sections.
Merging a Full Example

To merge a full example, follow these steps:
1.
From the HTML or PDF version of the manual, copy a configuration example into a
text file, save the file with a name, and copy the file to a directory on your routing
platform.
For example, copy the following configuration to a file and name the file ex-script.conf.
Copy the ex-script.conf file to the /var/tmp directory on your routing platform.
system {
scripts {
commit {
file ex-script.xsl;
}
}
}
interfaces {
fxp0 {
disable;
unit 0 {
family inet {
address 10.0.0.1/24;
}
}
}
}
2. Merge the contents of the file into your routing platform configuration by issuing the
load merge configuration mode command:

[edit]
user@host# load merge /var/tmp/ex-script.conf
load complete
Merging a Snippet
To merge a snippet, follow these steps:
1.
From the HTML or PDF version of the manual, copy a configuration snippet into a text
file, save the file with a name, and copy the file to a directory on your routing platform.
For example, copy the following snippet to a file and name the file
ex-script-snippet.conf. Copy the ex-script-snippet.conf file to the /var/tmp directory
on your routing platform.
commit {
file ex-script-snippet.xsl; }
2. Move to the hierarchy level that is relevant for this snippet by issuing the following
configuration mode command:
xx
[edit]
user@host# edit system scripts
[edit system scripts]
3. Merge the contents of the file into your routing platform configuration by issuing the
load merge relative configuration mode command:

[edit system scripts]
user@host# load merge relative /var/tmp/ex-script-snippet.conf
load complete
For more information about the load command, see the CLI User Guide.
Documentation Conventions
Table 1 on page xxi defines notice icons used in this guide.
Table 1: Notice Icons

Icon
Meaning
Description
Informational note
Indicates important features or instructions.
Caution
Indicates a situation that might result in loss of data or hardware damage.
Warning
Alerts you to the risk of personal injury or death.
Laser warning
Alerts you to the risk of personal injury from a laser.
Table 2 on page xxi defines the text and syntax conventions used in this guide.
Table 2: Text and Syntax Conventions

Convention
Description
Examples
Bold text like this
Represents text that you type.
To enter configuration mode, type

theconfigure command:
user@host> configure
Fixed-width text like this
Represents output that appears on the

terminal screen.
user@host> show chassis alarms

No alarms currently active
xxi
Table 2: Text and Syntax Conventions (continued)

Convention
Description
Examples
Italic text like this
Introduces or emphasizes important

new terms.
Identifies book names.
A policy term is a named structure

that defines match conditions and
actions.
Identifies RFC and Internet draft titles.
Junos OS System Basics Configuration

Guide
RFC 1997, BGP Communities Attribute
Italic text like this
Represents variables (options for which

you substitute a value) in commands or
configuration statements.
Configure the machines domain name:
Represents names of configuration

statements, commands, files, and
directories; configuration hierarchy levels;
or labels on routing platform
components.
To configure a stub area, include the

stub statement at the[edit protocols
ospf area area-id] hierarchy level.
The console port is labeled CONSOLE.
< > (angle brackets)
Enclose optional keywords or variables.
stub <default-metric metric>;
| (pipe symbol)
Indicates a choice between the mutually

exclusive keywords or variables on either
side of the symbol. The set of choices is
often enclosed in parentheses for clarity.
broadcast | multicast
# (pound sign)
Indicates a comment specified on the

same line as the configuration statement
to which it applies.
rsvp { # Required for dynamic MPLS only
[ ] (square brackets)
Enclose a variable for which you can

substitute one or more values.
community name members [

community-ids ]
Indention and braces ( { } )
Identify a level in the configuration

hierarchy.
; (semicolon)
Identifies a leaf statement at a

configuration hierarchy level.
Text like this
[edit]
root@# set system domain-name
domain-name
(string1 | string2 | string3)
[edit]
routing-options {
static {
route default {
nexthop address;
retain;
}
}
}
J-Web GUI Conventions

Bold text like this
> (bold right angle bracket)
xxii
Represents J-Web graphical user

interface (GUI) items you click or select.
Separates levels in a hierarchy of J-Web

selections.
In the Logical Interfaces box, select

All Interfaces.
To cancel the configuration, click

Cancel.
In the configuration editor hierarchy,

select Protocols>Ospf.
Documentation Feedback
We encourage you to provide feedback, comments, and suggestions so that we can
improve the documentation. You can send your comments to
techpubs-comments@juniper.net, or fill out the documentation feedback form at
https://www.juniper.net/cgi-bin/docbugreport/ . If you are using e-mail, be sure to include
the following information with your comments:
Document or topic name
URL or page number
Software release version (if applicable)
Requesting Technical Support

Technical product support is available through the Juniper Networks Technical Assistance
Center (JTAC). If you are a customer with an active J-Care or JNASC support contract,
or are covered under warranty, and need post-sales technical support, you can access
our tools and resources online or open a case with JTAC.
JTAC policiesFor a complete understanding of our JTAC procedures and policies,

review the JTAC User Guide located at
http://www.juniper.net/us/en/local/pdf/resource-guides/7100059-en.pdf.
Product warrantiesFor product warranty information, visit

http://www.juniper.net/support/warranty/.
JTAC hours of operationThe JTAC centers have resources available 24 hours a day,
7 days a week, 365 days a year.
Self-Help Online Tools and Resources

For quick and easy problem resolution, Juniper Networks has designed an online
self-service portal called the Customer Support Center (CSC) that provides you with the
following features:
Find CSC offerings: http://www.juniper.net/customers/support/
Search for known bugs: http://www2.juniper.net/kb/
Find product documentation: http://www.juniper.net/techpubs/
Find solutions and answer questions using our Knowledge Base: http://kb.juniper.net/
Download the latest versions of software and review release notes:

http://www.juniper.net/customers/csc/software/
Search technical bulletins for relevant hardware and software notifications:

https://www.juniper.net/alerts/
xxiii
Join and participate in the Juniper Networks Community Forum:

http://www.juniper.net/company/communities/
Open a case online in the CSC Case Management tool: http://www.juniper.net/cm/
To verify service entitlement by product serial number, use our Serial Number Entitlement
(SNE) Tool: https://tools.juniper.net/SerialNumberEntitlementSearch/
Opening a Case with JTAC

You can open a case with JTAC on the Web or by telephone.
Use the Case Management tool in the CSC at http://www.juniper.net/cm/.
Call 1-888-314-JTAC (1-888-314-5822 toll-free in the USA, Canada, and Mexico).
For international or direct-dial options in countries without toll-free numbers, see

http://www.juniper.net/support/requesting-support.html.
xxiv
PART 1
Overview
Router Overview on page 3
CHAPTER 1
Router Overview
ACX Series Universal Access Router Overview on page 3
Protocols and Applications Supported by the ACX Routers on page 5
ACX1000 and ACX1100 Routers Hardware and CLI Terminology Mapping on page 11
ACX4000 Routers Hardware and CLI Terminology Mapping on page 17
Router Hardware Components on page 19
ACX Series Universal Access Router Overview

The ACX Series Universal Access Router is principally designed to provide superior
management for rapid provisioning to the access network. The ACX Series routers support
rich Gigabit Ethernet and 10-Gigabit Ethernet capabilities for uplink, along with support
for legacy interfaces and Gigabit Ethernet interfaces for radio and NodeB connectivity in
a compact form factor that is environmentally hardened and passively cooled. Seamless,
end-to-end MPLS can be used to address legacy and emerging requirements to provide
the foundation for a converged network that utilizes the same mobile backhaul
infrastructure for business or residential services.
ACX Series Router Architecture on page 3
Junos OS on page 4
Interfaces on page 4
Mobile Backhaul on page 4
Junos Space on page 5
ACX Series Router Architecture

The ACX Series router is a single-board router with a built-in Routing Engine and one
Packet Forwarding Engine that has two pseudo Flexible PIC Concentrators (FPC 0 and
FPC 1). Because there is no switching fabric, the single Packet Forwarding Engine takes
care of both ingress and egress packet forwarding.
Routing EngineProvides Layer 3 routing services and network management.
Packet Forwarding EnginePerforms Layer 2 and Layer 3 packet switching, route

lookups, and packet forwarding.
The general architecture for ACX Series routers is shown in Figure 1 on page 4.
Figure 1: ACX Series Router Packet Forwarding and Data Flow

Ingress classification
In order of
decreasing precedence:
MF classification (DFW)
Fixed classification
BA classification
Outgoing packet
Buffering
Queuing
Scheduling
Egress rewrite
g006408
Incoming packet
Junos OS
The ACX Series router is powered by Junos OS, supporting extensive L2 and L3 features,
IP/MPLS with traffic engineering, rich network management, fault management, service
monitoring and Operation, Administration, and Maintenance (OAM) capabilities, and an
open software development kit (SDK) system that allows providers to customize and
integrate operations with their own management systems. For a list of related Junos OS
documentation, see http://www.juniper.net/techpubs/software/junos/
As part of the mobile backhaul, the ACX Series router at the cell site and the MX Series
router at the aggregation layer provide comprehensive end-to-end Ethernet, MPLS, and
OAM features with the one Junos OS running on both platforms.
Interfaces
The ACX Series routers support time-division multiplexing (TDM) T1 and E1 interfaces
and Gigabit Ethernet (10GbE, 100GbE, 1000GbE copper, and 1GbE and 10GbE fiber)
interfaces to support both the legacy and evolution needs of the mobile network. Support
for Power over Ethernet Plus (PoE+) at 65 watts per port mitigates the need for additional
electrical cabling for microwaves or other access interfaces.
Mobile Backhaul
In the mobile backhaul scenario, the ACX Series router is primarily used in the access
layer as the cell site router and the MX Series router is used as the edge and aggregation
router. As the cell site router, the ACX Series router connects the base station (BS) to
the packet network. Several cell site routers can be connected in a ring or hub-and-spoke
fashion to the upstream preaggregation and aggregation routers (MX Series routers).
The ACX Series router meets and often exceeds the key requirements for a cell site router.
A one-rack unit (U) tall router, the ACX Series router is compliant with the European
Telecommunications Standardization Institute (ETSI) 300, as well as environmentally
hardened and passively cooled for easy deployment where space and cooling are limited
as at the cell site.
Timing and synchronization are key elements in cell site router deployment. To deliver
the highest quality of experience, the ACX Series router supports multiple high-precision
timing optionsfor example, Synchronous Ethernet, 1588v2, and Precision Time Protocol
(PTP).
Chapter 1: Router Overview
Junos Space
Junos Space is a suite of comprehensive Web-based tools for operational management
and administration of Juniper Networks routers, including the ACX Series and MX Series
platforms. With the unified Junos Space network management system, network
provisioning and operations can be streamlined. Juniper Networks has extended Junos
Space with powerful new features designed to address the demanding requirements of
mobile backhaul.
Related
Documentation
Understanding Interfaces on ACX Series Universal Access Routers on page 99
Protocols and Applications Supported by the ACX Routers on page 5
Protocols and Applications Supported by the ACX Routers

Table 3 on page 5 contains the first Junos OS Release support for protocols and
applications on ACX routers. A dash indicates that the protocol or application is not
supported.
NOTE: The [edit logical-systems logical-system-name] hierarchy level is not

supported on ACX Series routers.
Table 3: Protocols and Applications Supported by ACX Series Routers

Protocol or Application
ACX1000
ACX1100
ACX2000
ACX2100
ACX4000
Ethernet
interfaces1/100/1000, 1G,
10G
12.2
12.2R2
12.2
12.2R2
12.3x51-D10-D10
ATM interfaces (IMA only)
12.2
12.2R2
12.2
12.2R2
E1 interfaces
12.2
12.2R2
12.2
12.2R2
T1 interfaces
12.2
12.2R2
12.2
12.2R2
Circuit emulation interfaces

(SAToP)
12.2
12.2R2
12.2
12.2R2
12.3x51-D10-D10
Interface and
Encapsulation Types
SONET/SDH interfaces
12.3x51-D10-D10
(requires a MIC)
Layer 3
Static routes
12.2
12.2R2
12.2
12.2R2
12.3x51-D10-D10
Table 3: Protocols and Applications Supported by ACX Series Routers (continued)

ACX1000
ACX1100
ACX2000
ACX2100
ACX4000
OSPF
12.2
12.2R2
12.2
12.2R2
12.3x51-D10-D10
IS-IS
12.2
12.2R2
12.2
12.2R2
12.3x51-D10-D10
BGP
12.2
12.2R2
12.2
12.2R2
12.3x51-D10-D10
Internet Control Message

Protocol (ICMP)
12.2
12.2R2
12.2
12.2R2
12.3x51-D10-D10
Address Resolution
Protocol (ARP)
12.2
12.2R2
12.2
12.2R2
12.3x51-D10-D10
Bidirectional Forwarding
Detection (BFD) protocol
12.2
12.2R2
12.2
12.2R2
12.3x51-D10-D10
Dynamic Host
Configuration Protocol
(DHCP)
12.2
12.2R2
12.2
12.2R2
12.3x51-D10-D10
IP fast reroute (FRR)

(OSPF, IS-IS)
12.2
12.2R2
12.2
12.2R2
12.3x51-D10-D10
Maximum transmission unit

(MTU) 1518
12.2
12.2R2
12.2
12.2R2
12.3x51-D10-D10
RSVP
12.2
12.2R2
12.2
12.2R2
12.3x51-D10-D10
LDP (targeted and direct)
12.2
12.2R2
12.2
12.2R2
12.3x51-D10-D10
Static label-switched path

(LSP)
12.2
12.2R2
12.2
12.2R2
12.3x51-D10-D10
FRR
12.2
12.2R2
12.2
12.2R2
12.3x51-D10-D10
Traffic engineering
12.2
12.2R2
12.2
12.2R2
12.3x51-D10-D10
DiffServ traffic engineering
12.2
12.2R2
12.2
12.2R2
12.3x51-D10-D10
E-LINE
12.2
12.2R2
12.2
12.2R2
12.3x51-D10-D10
Pseudowire Emulation
Edge to Edge (PWE3
[signaled])
12.2
12.2R2
12.2
12.2R2
12.3x51-D10-D10
Static Ethernet PWs
12.2
12.2R2
12.2
12.2R2
12.3x51-D10-D10
Layer 2 circuits
12.2
12.2R2
12.2
12.2R2
12.3x51-D10-D10
MPLS, VPLS, VPNs

ACX1000
ACX1100
ACX2000
ACX2100
ACX4000
IEE802.1ag CC monitoring
on active and standby
pseudowires
12.2
12.2R2
12.2
12.2R2
12.3x51-D10-D10
Edge protection using

static Virtual Private Wire
Service (VPWS)
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
Ethernet in the first mile

(EFM 802.3ah)
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
802.1ag connectivity fault

management (CFM)
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
IEE802.1ag interface-status
type, length, and value
(TLV)
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
Firewall filters (access

control
listsACLs)family inet
on page 83
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
Standard firewall filter

match conditions for MPLS
traffic on page 86
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
Firewall filtersfamily
ccc/any
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
Policingper logical
interface
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
Policingper physical
interface
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
Policingper family
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
TrTCM (color aware, color

blind)
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
SrTCM (color aware, color

blind)
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
Host protection
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
Eight queues per port
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
Ethernet Layer 2
QoS

ACX1000
ACX1100
ACX2000
ACX2100
ACX4000
Priority queuing
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
Rate control
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
Scheduling with two

different priorities
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
Low-latency queue (LLQ)
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
Weighted random early

detection (WRED) drop
profile (DP)
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
ClassificationDSCP
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
ClassificationMPLS EXP
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
ClassificationIEEE 802.1p
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
RewriteDSCP
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
Rewrite MPLS EXP
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
Rewrite 802.1p
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
Rewrite MPLS and DSCP to

different values
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
Timing-1588-v2,
1588-2008backup clock
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
Synchronous Ethernet
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
Building-integrated timing
supply (BITS)
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
Clock synchronization
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
Redundant clock (multiple

1588 masters)
Timing
OAM, Troubleshooting, Manageability, Lawful Intercept
Network Time Protocol

(NTP)
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
SNMP
12.2
12.2R2
12.2
12.2R2
12.3x51-D10

ACX1000
ACX1100
ACX2000
ACX2100
ACX4000
802.1ag CFM
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
802.3ah EFM
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
Y.1731 Fault and

Performance Management
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
MPLS OAM
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
RMON
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
Layer 2 traceroute
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
DNS
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
TFTP for software

downloads
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
Port mirroring (local port

mirroring)
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
Interface loopback
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
Interface byte and packet

stats
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
Interface queue stats
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
Drop packet stats
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
Distinguish each 802.1ag

connection by VLAN-ID
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
Interface
passive-monitor-mode
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
Multipacket mirror
TACACS AAA
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
RADIUS authentication
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
Control plane DOS

prevention
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
Security
High Availability

ACX1000
ACX1100
ACX2000
ACX2100
ACX4000
MPLS FRR
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
BFD
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
ATM over PWE3
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
RFC4717 ATM
encapsulation: S6.1 ATM N
to one cell mode (required
as per standard)
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
RFC4717: S6.3ATM AAL5

SDU encapsulation
(optional)
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
ATM PWE3 control word
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
ATM PWE3 by means of

dynamic labels
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
ATM VPI/VCI swapping
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
ATM idle/unassigned cell

suppression
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
ATM support for N to 1 PW

promiscuous mode: 1 PW
per port and 1 PW per VPI
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
Cell concatenation (1 to 30
cells per packet)
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
Packet/byte counters per

VP and VC
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
Inverse multiplexing over

ATM (IMA)
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
ATM Transport
ATM Encapsulation
AAL5 SDU (n-to-1 cell
relay)
ATM Queuing
ATM service categories
(CBR, nrt-VBR, UBR) to the
UNI
10

ACX1000
ACX1100
ACX2000
ACX2100
ACX4000
MAP ATM service

categories to PW EXP bits
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
Input policing per VC
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
VC output shaping
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
Early packet discard
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
Standard SNMP MIBs
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
Juniper Networks
enterprise-specific MIBs
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
12.2
12.2R2
12.2
12.2R2
12.3x51-D10
MIBs
TDM Pseudowire
Structure-Agnostic TDM
over Packet (SAToP)
ACX1000 and ACX1100 Routers Hardware and CLI Terminology Mapping
ACX1000 Routers Hardware and CLI Terminology Mapping

Table 4 on page 11 describes the hardware terms used in ACX1000 router documentation
and the corresponding terms used in the Junos OS command line interface (CLI). Figure
2 on page 12 shows the port locations of the interfaces.
Table 4: CLI Equivalents of Terms Used in Documentation for ACX1000 Routers

Hardware
Item (as
displayed
in the CLI)
Description (as
displayed in the CLI)
Value (as
displayed in the
CLI)
Item in Documentation
Additional Information
Chassis
ACX1000
Router chassis
Chassis Physical Specifications

for ACX1000 and ACX1100
Routers
FPC (n)
Abbreviated name of the

Flexible PIC
Concentrator (FPC)
Value of n is
always 0.
The router does not have

actual FPCs. In this case,
FPC refers to the router
itself.
Interface Naming Conventions

Used in the Junos OS
Operational Commands
11
Table 4: CLI Equivalents of Terms Used in Documentation for ACX1000 Routers (continued)
Hardware
Item (as
displayed
in the CLI)
PIC (n)
Description (as
Value (as
displayed in the
CLI)

Physical Interface Card
(PIC)
n is a value in the
range of 02.

actual PIC devices; see
entries for PIC 0 through PIC
2 for the equivalent item on
the router.

8x T1/E1 (RJ-48)
PIC 0
Built-in network ports on the

front panel of the router
ACX1000 and ACX1100 Universal

Access Router Overview
8x 1GE (RJ-45)
PIC 1
Built-in uplink ports on the


One of the following:
PIC 2


4x 1GE (RJ-45)
4x 1GE (SFP)
Xcvr (n)

transceiver
n is a value
equivalent to the
number of the port
in which the
transceiver is
installed.
Optical transceivers
Uplink Ports on ACX1000 and

ACX1100 Routers
Power
supply (n)
Built-in power supply
Value of n is
always 0.
DC power supply
ACX1000 and ACX1100 Power

Overview
Fan
Fan
Fan
Cooling System and Airflow in

an ACX1000 and ACX1100
Router
NOTE: ACX1000 routers

are fanless models.
Figure 2: ACX1000 Interface Port Mapping

FPC 0, PIC 2
GE 0/2/0-0/2/3
FPC 0, PIC 0
T1/E1 0/0/0-0/0/7
ACX1000
0/0/4
0/0/5
0/0/0
0/0/1
T1/E1
0/0/6
0/0/7
0/1/4
0/1/5
0/0/2
0/0/3
0/1/0
0/1/1
GE
0/1/6
0/1/7
GE COMBO
0/2/3 (Cu)
0/2/2 (Cu)
0/1/2
0/1/3
0/2/0 (Cu)
ALARM
CONSOLE/AUX
1PPS
SYS
IN
OUT
GE COMBO
10MHz
IN
OUT
0/2/1 (Cu)
0/2/0 (SFP)
FPC 0, PIC 1
GE 0/1/0-0/1/7
0/2/1 (SFP)
0/2/2 (SFP)
0/2/3 (SFP)
g006413
MGMT
FPC 0, PIC 2
GE 0/2/0-0/2/3

12

Hardware
Item (as
displayed
in the CLI)
Description (as
Value (as
displayed in the
CLI)
Chassis
ACX1100
Router chassis

Routers
FPC (n)

Flexible PIC Concentrator
(FPC)
Value of n is
always 0.

itself.

PIC (n)

(PIC)
n is a value in the
range of 01.

entries for PIC 0 through
PIC 2 for the equivalent
item on the router.

8x 1GE (RJ-45)
PIC 0

ACX1000 and ACX1100

Universal Access Router
Overview
PIC 1

ACX1000 and ACX1100

Overview
4x 1GE (RJ-45)
4x 1GE (SFP)
Xcvr (n)

transceiver
n is a value
equivalent to the
number of the port
in which the
transceiver is
installed.

ACX1100 Routers
Power
supply (n)
Value of n is
always 0.
AC or DC power supply

Overview
Fan
Fan
Fan
Cooling System and Airflow in

an ACX1000 and ACX1100
Router
NOTE: ACX1100 routers

are fanless models.
13

FPC 0, PIC 1
GE 0/1/0-0/1/3
FPC 0, PIC 0
GE 0/0/0-0/0/7
0/0/5
0/0/6
0/0/7
0/1/2
0/1/3
0/0/0
0/0/1
0/0/2
0/0/3
0/1/0
0/1/1
COMBO PORTS
Related
Documentation
0/1/0
0/1/1
0/1/2
0/1/3
g017874
GE
0/0/4
CONSOLE/AUX
ACX1000 and ACX1100 Universal Access Router Overview
ACX2000 and ACX2100 Routers Hardware and CLI Terminology Mapping
ACX2000 Hardware and CLI Terminology Mapping on page 14
ACX2100 Hardware and CLI Terminology Mapping on page 15
ACX2000 Hardware and CLI Terminology Mapping


Hardware
Item (as
displayed
in the CLI)
Description (as
Value (as
displayed in the
CLI)
Chassis
ACX2000
Router chassis

Routers
FPC (n)

Flexible PIC
Concentrator (FPC)
Value of n is
always 0.

itself.

Used in the Junos OS Operational
Commands
PIC (n)

(PIC)
n is a value in the
range of 03.

the router.

Commands
16x T1/E1 (RJ-48)
PIC 0

ACX2000 and ACX2100

Overview
14
Hardware
Item (as
displayed
in the CLI)
Description (as
Value (as
displayed in the
CLI)
PIC 1

ACX2000 and ACX2100

Overview
2x 1GE (SFP)
PIC 2

ACX2000 and ACX2100

Overview
2x 10GE (SFP+)
PIC 3

ACX2000 and ACX2100

Overview
Xcvr (n)

transceiver
n is a value
equivalent to the
number of the
port in which the
transceiver is
installed.

ACX2100 Routers
Power
supply (n)
Value of n is
always 0.
DC power supply

Overview
Fan
Fan
Fan
Cooling System and Airflow in an

ACX2000 and ACX2100 Router
6x 1GE (RJ-45)
2x 1GE (POE RJ-45)
NOTE: ACX2000
routers are fanless
models.

FPC 0, PIC 0
T1/E1 0/0/0-0/0/15
ACX2000
0/0/8
0/0/9
0/0/10
0/0/11
0/0/0
0/0/1
0/0/2
0/0/3
T1/E1
0/0/12
0/0/13
0/0/14
0/0/15
0/1/4
0/0/4
0/0/5
0/0/6
0/0/7
0/1/0
0/1/5
GE
0/1/6
0/1/7 POE
CONSOLE/AUX
ALARM
1PPS
SYS
EXT REF CLK IN
IN
OUT
GE
10MHz
IN
OUT
0/1/1
0/1/2
XE
0/1/3 POE
0/2/0
FPC 0, PIC 2
GE 0/2/0-0/2/1
0/2/1
0/3/0
0/3/1
g006414
MGMT
FPC 0, PIC 1
GE 0/1/0-0/1/7
FPC 0, PIC 3
XE 0/3/0-0/3/1
ACX2100 Hardware and CLI Terminology Mapping

15

Hardware
Item (as
displayed
in the CLI)
Description (as
Value (as
displayed in the
CLI)
Chassis
ACX2100
Router chassis

Routers
FPC (n)
Abbreviated name of
the Flexible PIC
Concentrator (FPC)
n is a value in the
range of 01.

actual FPCs. In this case, FPC
refers to the router itself.

Commands
PIC (n)
Abbreviated name of
the Physical Interface
Card (PIC)
n is a value in the
range of 03.

the router.

Commands
16x T1/E1 (RJ-48)
PIC 0 on FPC 0

ACX2000 and ACX2100

Overview
4x 1GE (RJ-45)
PIC 0 on FPC 1

ACX2000 and ACX2100

Overview
PIC 1 on FPC 1

ACX2000 and ACX2100

Overview
2x 1GE (SFP)
PIC 2 on FPC 1

ACX2000 and ACX2100

Overview
2x 10GE (SFP+)
PIC 3 on FPC 1

ACX2000 and ACX2100

Overview
Xcvr (n)
Abbreviated name of
the transceiver
n is a value
equivalent to the
number of the port
in which the
transceiver is
installed.

ACX2100 Routers
Power
supply (n)
Value of n is always
0.

Overview
16
4x 1GE (RJ-45)
4x 1GE (SFP)
Hardware
Item (as
displayed
in the CLI)
Description (as
Value (as
displayed in the
CLI)
Fan
Fan
Fan
Cooling System and Airflow in an

ACX2000 and ACX2100 Router
NOTE: ACX2100
routers are fanless
models.
T1/E1
GE
0/0/8
0/0/9
0/0/10
0/0/11
0/0/12
0/0/13
0/0/14
0/0/15
1/0/2
1/0/3
1/1/2
1/1/3
0/0/0
0/0/1
0/0/2
0/0/3
0/0/4
0/0/5
0/0/6
0/0/7
1/0/0
1/0/1
1/1/0
1/1/1
CONSOLE/AUX
ALARM
1PPS
SYS
IN
EXT REF CLK IN
OUT
1/1/2
1/1/3
1/1/0
1/1/1
IN
OUT
COMBO PORTS
FPC 1, PIC 1
GE 1/1/0-1/1/3
Related
Documentation
1/2/1
10MHz
GE
1/2/0
1/3/0
XE
1/3/1
g017849
ACX2100
MGMT
FPC 1, PIC 2
GE 1/2/0-1/2/1
FPC 1, PIC 0
GE 1/0/0-1/0/3
FPC 0, PIC 0
T1/E1 0/0/0-0/0/15
FPC 1, PIC 3
XE 1/3/0-1/3/1
ACX2000 and ACX2100 Universal Access Router Overview


Hardware
Item (as
displayed
in the CLI)
Description (as
Value (as displayed

in the CLI)
Chassis
ACX4000
Router chassis
ACX4000 Router Physical

Specifications
FPC (n)
Abbreviated name of
the Flexible PIC
Concentrator (FPC)
Value of n is a value
in the range of 01.
The router does not have actual

FPC devices; see entries for
FPC 0 and FPC 1 for the
equivalent item on the router.
Interface Naming
Conventions Used in the
Junos OS Operational
Commands
FPC BUILTIN
FPC 0
Refers to the built-in FPC that

houses the built-in network
ports.
FPC BUILTIN
FPC 1
Slots in which one or two MICs

are installed
ACX4000
17
Hardware
Item (as
displayed
in the CLI)
Description (as
Value (as displayed

in the CLI)
Abbreviated name of
the Modular Interface
Cards (MICs) or built-in
interfaces
Either:
n is a value in the
range of 02.
The router supports up to two

MICs and has built-in interfaces,
both represented as PIC in the
CLI; see entries for PIC 0 through
PIC 2 for the equivalent item on
the router.
Interface Naming
Conventions Used in the
Junos OS Operational
Commands
FPC 0, PIC 0

ACX4000 Ports Overview
2x 1GE(LAN) SFP
FPC 0, PIC 1

2x 10GE(LAN) SFP+
FPC 0, PIC 2

<MIC 0 description>
FPC 1, PIC 0
MIC installed in slot 0
ACX4000 Modular
Interface Card (MIC)
Overview
<MIC 1 description>
FPC 1, PIC 1
MIC installed in slot 1
ACX4000 Modular
Interface Card (MIC)
Overview
Xcvr (n)
Abbreviated name of
the transceiver
n is a value
equivalent to the
number of the port in
which the transceiver
is installed.
PEM (n)
Power supply
Value of n is a value
in the range of 01.
ACX4000 Power Overview
Fan Tray
(n)
Fan Tray
Value of n is always
0.
Fan tray module
ACX4000 Cooling System

and Airflow
PIC (n)
18
8x 1GE(LAN) RJ45
8x 1GE(LAN) SFP

2
g006541
1 MIC slot 0 (FPC 1, PIC 0)
4 10-Gigabit Ethernet SFP+ ports (FPC 0, PIC

2)
2 MIC slot 1 (FPC 1, PIC 1)
5 Gigabit Ethernet SFP ports (FPC 0, PIC 1)
3Gigabit Ethernet ports (FPC 0, PIC 0)
Related
Documentation
ACX4000 Universal Access Router Overview
Router Hardware Components

The Junos OS runs on the following types of Juniper Networks routers and Packet
Transport Switches: ACX Series, J Series, M Series, MX Series, T Series, and PTX Series
Packet Transport Switches. Each network device consists of the major hardware
components as shown in Table 9 on page 19. One or more of the major hardware
components shown is used in each system.
NOTE: The ACX Series router is a single-board router with a built-in Routing
Engine and one Packet Forwarding Engine. The pseudo FPCs and PICs are
described in ACX2000 and ACX2100 Routers Hardware and CLI Terminology
Mapping on page 14
Table 9: Major Router Hardware Components

M Series
MX
Series
T Series
PTX
Series
J Series
Routing Engines
Control Board
Switch Interface Board

(SIB)
Forwarding Engine Board

(FEB)
Power Supply
19
Table 9: Major Router Hardware Components (continued)
Cooling System
M Series
MX
Series
T Series
PTX
Series
J Series
Dense Port Concentrators

(DPC)
Switch Control Board

(SCB)
Flexible PIC
Concentrators (FPC)
Physical Interface Module

(PIM)
(PIC)
Flexible PIC Concentrators (FPCs) are each populated by PICs for various interface types.
On some routers, the PICs are installed directly in the chassis.
For information about specific components in your router, see the hardware guide for
your router.
Related
Documentation
20
Junos OS Architecture Overview
PART 2
Configuration
Configuration Overview on page 23
Autoinstallation on page 45
CoS on page 53
Firewall Filters on page 81
Interfaces and Chassis on page 93
Layer 2 and Layer 3 on page 107
MPLS, VPNs, and Pseudowires on page 115
Network Management on page 139
Operations, Administration, and Management (OAM) on page 167
Routing Protocols on page 207
Time Division Multiplexing (TDM) on page 215
Timing and Synchronization on page 237
Upgrade and Installation on page 289
Junos Configuration Statements on page 313
Configuration Statement Hierarchies on page 321
21
22
CHAPTER 2
Configuration Overview
Classifiers and Rewrite Rules at the Global and Physical Interface Levels
Overview on page 23
CoS on ACX Series Universal Access Routers Features Overview on page 24
Gigabit Ethernet Autonegotiation Overview on page 25
IEEE 1588v2 PTP Boundary Clock Overview on page 26
IEEE 1588v2 Precision Timing Protocol (PTP) on ACX Series Universal Access
Routers on page 28
Inverse Multiplexing for ATM (IMA) Overview on page 30
IPv6 Support on ACX Series Universal Access Routers on page 30
Pseudowire Overview for ACX Series Universal Access Routers on page 33
Synchronous Ethernet Overview on the ACX Series Universal Access Routers on page 34
TDM CESoPSN Overview on page 34
TDM CESoPSN on ACX Series Routers Overview on page 35
Traffic Policing Overview on page 37
Understanding PoE on ACX Series Universal Access Routers on page 41
Classifiers and Rewrite Rules at the Global and Physical Interface Levels Overview
On ACX Series Universal Access Routers, CoS supports classification and rewrite at the
global level and physical interface levels.
At a global level, you can define EXP classification.
At a physical interface level, you can define the following features:
DSCP and inet-precedence classifiers
DSCP and inet-precedence rewrites
ieee-802.1 classifiers (inner and outer)
ieee-802.1 rewrites (outer)
At a logical interface level, you can define the fixed classification and EXP rewrites.
23
To configure global EXP classifiers, include the classfiers exp classifier-name statement
at the [edit class-of-service] system-defaults hierarchy level.
To configure classifiers or rewrite rules at the physical interface, include either the
classifiers statement or the rewrite-rules statement at the [edit class-of-service]
interfaces interface-name ] hierarchy level.
To display classifiers configured under system-defaults, enter the show class-of-service
system-defaults command.
To display classifiers and rewrite rules bound to physical interfaces, enter the show
class-of-service interfaces interface-name command.
Related
Documentation
Configuring Classifiers and Rewrite Rules at the Global and Physical Interface Levels
on page 63
CoS on ACX Series Universal Access Routers Features Overview

The following key CoS features are supported on ACX Series Universal Access Routers:
Physical interface-based classifiers at the [edit class-of-service interfaces

interfaces-name] hierarchy level
Fixed classification for all ingress packets traversing a logical interface to a single
forwarding class. Fixed classification is supported on all interface types.
EXP bits located in each MPLS label and used to encode the CoS value of a packet as
it traverses a label-switched path (LSP). To configure global EXP bits, include the exp
statement at the [edit class-of-service system-defaults classifiers] hierarchy level.
Rewrite rules at the physical and logical interface levels including the following: IP
type-of-service (ToS), DSCP, MPLS EXP bit value, and IEEE 802.1p bit value.
Attachment of the following rewrite rules to the physical interface at the [edit
class-of-service interfaces interface-name rewrite-rules] hierarchy level: IP ToS, DSCP,
and IEEE 802.1p bit value.
Rewrite rules for MPLS EXP bits on the logical interface at the [edit class-of-service
interfaces interface-name unit unit-number rewrite-rule] hierarchy level.
NOTE: Fine-grained rewrite is not possible, even when you use multifield
filters, because of the application-specific integrated circuit (ASIC)
limitation.
Queuing and scheduling features include:
24
Support for up to eight forwarding classes.
Support for up to eight egress queues per port.
Internal buffer of 2 MB with per-egress queue buffer management.
Chapter 2: Configuration Overview
Three weighted random early detection (WRED) curves for TCP and one WRED curve
for non-TCP. There are two fill levels and two drop probabilities per WRED curve; the
drop probability corresponding to the first fill must be zero.
Strict-priority and weighted deficit round-robin scheduling.
Multiple strict-priority queues per port.
Per-queue committed information rate (CIR) and peak information rate (PIR).
Per-physical-port shaping.
Queue statistics features include:
Related
Documentation
Per-egress-queue enqueue statistics in packets, bytes, packets per second (pps), and
bits per second (bps).
Per-egress-queue transmit statistics in packets, bytes, pps, and bps.
Per-egress-queue drop statistics in packets and pps.
Understanding CoS CLI Configuration Statements on ACX Series Universal Access

Routers on page 56
Configuring CoS on ACX Series Universal Access Routers on page 58
Gigabit Ethernet Autonegotiation Overview

Autonegotiation is enabled by default on all Gigabit Ethernet and Tri-Rate Ethernet
copper interfaces. However, you can explicitly enable autonegotiation to configure remote
fault options manually.
NOTE:
For Gigabit Ethernet interfaces installed in J4350 and J6350 Services

Routers, when you manually configure either the link mode or speed
settings, the system ignores the configuration and generates a system log
message. When autonegotiation is enabled and you specify the link mode
and speed, the link autonegotiates with the manually configured settings.
When autonegotiation is disabled and you configure both the link mode
and speed, the link operates with the manually configured settings. If you
disable autonegotiation and do not manually configure the link mode and
speed, the link operates at 1000 Mbps full duplex.
When you configure the Tri-Rate Ethernet copper interface to operate at

1 Gbps, autonegotiation must be enabled.
On ACX Series Universal Access Routers, when the autonegotiation is

disabled, the speed has to be explicitly configured to 10100 Mbps.
On T4000 routers, the auto-negotiation command is ignored for interfaces

other than Gigabit Ethernet.
25
Related
Documentation
Configuring Gigabit Ethernet Autonegotiation
Junos OS Ethernet Interfaces
IEEE 1588v2 PTP Boundary Clock Overview

The IEEE 1588v2 standard defines the Precision Time Protocol (PTP), which is used to
synchronize clocks throughout a network. The standard describes the PTP boundary
clocks hierarchical master/slave architecture for the distribution of time-of-day.
IEEE 1588v2 PTP Boundary Clock on page 26
Clock Clients on page 27
IEEE 1588v2 PTP Boundary Clock

An IEEE 1588v2 boundary clock has multiple network connections and can act as a source
(master) and a destination (slave or client) for synchronization messages. It synchronizes
itself to a best master clock through a slave port and supports synchronization of remote
clock clients to it on master ports. Boundary clocks can improve the accuracy of clock
synchronization by reducing the number of 1588v2-unaware hops between the master
and the client. Boundary clocks can also be deployed to deliver better scale because
they reduce the number of sessions and the number of packets per second on the master.
The boundary clock intercepts and processes all PTP messages and passes all other
traffic. The best master clock algorithm (BMCA) is used by the boundary clock to select
the best configured acceptable master clock that a boundary slave port can see. To
configure a boundary clock, include the boundary statement at the [edit protocols ptp
clock-mode] hierarchy level and at least one master with the master statement and at
least one slave with the slave statement at the [edit protocols ptp] hierarchy level.
Figure 7 on page 26 illustrates two ACX Series boundary clocks in a network in which the
clock flow is from the upstream node (BC-1) to the downstream node (BC-2).
Figure 7: Boundary Clocks in a Network

BC-1
ACX Series Router
Remote M
OC-5
Grandmaster
P-1 P-2 P-3 P-4

S
M
M
S
Remote M
OC-1
Grandmaster
P-1 P-2 P-3

S
M
M
Remote S
OC-2
Remote S
OC-3
M- Master
S - Slave
Remote S
OC-4
P - Ports on an ACX Series router

g017867
BC - Boundary Clock
OC - Ordinary Clock
BC-2
ACX Series Router
26
The first boundary clockBC-1has four ports. Each port is configured as follows:
BC-1 P-1 and BC-1 P-4 are boundary slave ports connected to two grandmaster
clocksOC-1 and OC-5. The grandmasters are included as the clock sources in the
slave port configurations. From the packets received on the slave ports, BC-1 selects
the best master, synchronizes its clock, and generates PTP packets, which are sent
over the master portsBC-1 P-2 and BC-1 P-3to the downstream clients.
BC-1 P-2, a master port, is connected to OC-2, an ordinary remote slave. OC-2 is included
as a clock client in BC-1 P-2s master configuration, and so receives PTP packets from
BC-1 P-2.
BC-1 P-3, a master port, is connected to BC-2 P-1, a remote boundary slave port. In this
situation, the master portBC-1 P-3is included as a clock source in the configuration
of the boundary slave portBC-2 P-1. In addition, the boundary slave portBC-2 P-1is
included as a clock client in the configuration of the master portBC-1 P-3. With this
configuration, the boundary slaveBC-2 P1receives PTP packets from BC-1 P3.
The second boundary clockBC-2has three ports. Each port is configured as follows:
BC-2 P-1 is a boundary slave port connected to the upstream master portBC-1 P3.
As described previously, BC-2 P-1 receives PTP packets from BC-1 P3. The master
portsBC-2 P-2 and BC-2 P-3synchronize their time from the packets received from
BC-2 P1.
BC-2 P-2 and BC-2 P-3, boundary master ports, are connected to ordinary remote
slavesOC-3 and OC-4. OC-3 and OC-4 are included as clock clients in the
configuration of the master portsBC-2 P2 and BC-2 P-3. Both slaves receive PTP
packets from the master boundary port to which they are connected.
In this example, the boundary clock synchronizes its clock from the packets received on
its slave ports from the upstream master. The boundary clock then generates PTP packets,
which are sent over the master port to downstream clients. These packets are
timestamped by the boundary clock by using its own time, which is synchronized to the
selected upstream master.
Clock Clients
A clock client is the remote PTP host, which receives time from the PTP master and is in
a slave relationship to the master.
NOTE: The term slave is sometimes used to refer to the clock client.
An ACX Series router acting as a master boundary clock supports the following types of
downstream clients:
Automatic clientAn automatic client is configured with an IP address, which includes

the subnet mask, indicating that any remote PTP host belonging to that subnet can
join the master clock through a unicast negotiation. To configure an automatic client,
include the subnet mask in the clock-client ip-address statement at the [edit protocols
ptp master interface interface-name unicast-mode] hierarchy level.
27
Manual clientA manual client is configured with the manual statement at the [edit
protocols ptp master interface interface-name unicast-mode clock-client ip-address
local-ip-address local-ip-address] hierarchy level. A manual client does not use unicast
negotiation to join the master clock. The manual statement overrides the unicast
negotiation statement configured at the [edit protocols ptp] hierarchy level. As soon
as you configure a manual client, it starts receiving announce and synchronization
packets.
Secure clientA secure client is configured with an exact IP address of the remote PTP
host, after which it joins a master clock through unicast negotiation. To configure a
secure client, include the exact IP address in the clock-client ip-address statement at
the [edit protocols ptp master interface interface-name unicast-mode] hierarchy level.
NOTE: You can configure the maximum number of clients (512 ) in the
following combination:
Related
Documentation
Automatic clients 256.
Manual and secure clients 256Any combination of manual and secure

clients is allowed as long as the combined total amounts to 256.
IEEE 1588v2 Precision Timing Protocol (PTP) on ACX Series Universal Access Routers
on page 28
Precision Time Protocol Overview
Configuring Precision Time Protocol Clocking on page 253
[edit protocols ptp] Hierarchy Level
Supported IPv4, TCP, and UDP Standards
The IEEE 1588v2 standard defines the Precision Time Protocol (PTP), which is used to
synchronize clocks throughout a packet-switched network. This synchronization is
achieved through packets that are transmitted and received in a session between a
master clock and a slave clock or remote clock client. The clocks used for the distribution
of accurate time are in an hierarchical master/slave architecture, which includes boundary
clocks, ordinary clocks, and grandmaster clocks. A boundary clock is both a clock source
and a clock client. An ordinary clock is either a clock source or a clock client. However, a
grandmaster clock is always a clock source. An ordinary clock on an ACX Series router is
always a clock client. In addition, User UDP over IPv4 and unicast mode are used to
transport PTP messages.
28
On an ACX Series router, the following key PTP features are supported:
Boundary clockA boundary clock has multiple network connections and can act as
a source (master) and a destination (slave or clock client) for synchronization messages.
It synchronizes itself to a best master clock through a slave port and supports
synchronization of clients to it on master ports. Boundary clocks can improve the
accuracy of clock synchronization by reducing the number of 1588v2-unaware hops
between the master and the client. Boundary clocks can also be deployed to deliver
better scale because they reduce the number of sessions and the number of packets
per second on the master.
Ordinary clockThe PTP ordinary clock has a single network connection and can act
as a source (master) or destination (slave or clock client) for synchronization messages.
On ACX Series routers, the ordinary clock is a slave, which receives synchronization
reference messages from a master, either a grandmaster or a master boundary clock.
You cannot configure an ordinary master on an ACX Series router. However, a boundary
clock can provide time to the ordinary slave.
PTP grandmaster clockThe PTP grandmaster clock communicates time information

to destination or slave ports. The grandmaster clock is an external device to which the
boundary or ordinary clock synchronizes. You cannot configure a grandmaster clock
on an ACX Series router. However, a boundary clock slave or an ordinary clock slave
can receive time from a grandmaster clock.
Clock sourceA clock source is the PTP master clock to which the slave synchronizes.
The clock source is included in the configuration of the slave clock.
NOTE: The term master is sometimes used to refer to the clock source.
Clock clientA clock client is the remote PTP host, which receives time from the PTP
master. The clock client is included in the configuration of the master clock.
NOTE: The term slave is sometimes used to refer to the clock client.
Related
Documentation
PTP over UDP over IPv4The IEEE1588v2 standard specifies different transport
protocols for carrying PTP packets. For example, PTP over Ethernet, PTP over UDP
over IPv4, and PTP over UDP over IPv6. ACX Series routers support PTP over UDP over
IPv4.
Unicast mode (IPv4 on Gigabit Ethernet interfaces only)Unicast mode is a user-to-user

protocol used to send a datagram to a single recipient. Unicast mode is used for
transporting PTP messages.
29
Supported IPv4, TCP, and UDP Standards
Inverse Multiplexing for ATM (IMA) Overview

Inverse multiplexing for ATM is a technique of transporting ATM traffic over a bundle of
T1 or E1 interfaces. Inverse multiplexing is the opposite of multiplexing. Multiplexing is a
technique of combining multiple signals into a single signal. Inverse multiplexing is a
technique that divides a data stream into multiple concurrent streams that are transmitted
at the same time across separate channels (such as T1 or E1 interfaces) and then
reconstructed at the other end back into the original data stream. Inverse multiplexing
is used to speed up the flow of data across a slower interface, such as a T1 or E1 interface,
by load balancing the data stream across multiple T1 or E1 interfaces, increasing the line
capacity.
With ATM inverse multiplexing, an ATM cell stream is transported over a bundle of T1 or
E1 interfaces called an IMA group. The ATM cells are inverse multiplexed and
demultiplexed cyclically across the IMA group to create a higher-bandwidth logical link
whose rate is approximately the sum of all the interfaces in the group.
Related
Documentation
Configuring Inverse Multiplexing for ATM (IMA) on page 224
IPv6 Support on ACX Series Universal Access Routers

IPv6 builds upon the functionality of IPv4, providing improvements to addressing,
configuration and maintenance, and security. The following IPv6 features are supported
on ACX Series routers:
IPv6 path maximum transmission unit (MTU) discovery

Path MTU Discovery is used by single-source devices to determine the correct size of
fragments. Path MTU Discovery is enabled for IPv6 packets by default.
Dynamic routes distribution through IS-IS and OSPF for IPv6

Routers learn routes through different routing protocols such as OSPF, BGP, or IS-IS.
Learned routes are put in the routing table to enable IPv6 traffic forwarding.
Dual stacking (IPv4 and IPv6)

Dual stacking allows a device to run both IPv4 and IPv6 at the same time. End nodes,
routers, and switches run both protocols and use IPv6 as the preferred protocol.
IPv6 forwarding
The ACX Series port forwarding engine software supports unicast IPv6 routes and next
hops. This includes basic route infrastructure, next-hop support, network infrastructure,
and exception packet processing.
IPv6 over MPLS (6PE)

ACX Series Universal Access Routers can interconnect IPv6 islands over an
MPLS-enabled IPv4 network. IPv6 information is sent over the MPLS core using MG-BGP
30
with IPv4. The BGP Next Hop field conveys the IPv4 address of the router so that MPLS
LSPs can be used without explicit tunnel configuration.
Neighbor Discovery
The Neighbor Discovery protocol facilitates a substantial number of functions related
to local network connectivity, datagram routing, and configuration. Both regular hosts
and routers in an IPv6 environment count on the Neighbor Discovery protocol to
facilitate the important exchanges of information that are necessary for proper
internetwork operations. Neighbor Discovery is a messaging protocol similar to ICMP.
The following functions are performed by the protocol:
Router discoveryHow a host locates routers residing on an attached link.
Prefix discoveryHow a host discovers address prefixes for destinations residing on

an attached link. Nodes use prefixes to distinguish between destinations that reside
on an attached link and those destinations that it can reach only through a router.
Parameter discoveryHow a node learns various parameters (link parameters or

Internet parameters) that it places in outgoing packets.
Address resolutionHow a node uses only a destination IPv6 address to determine

a link-layer address for destinations on an attached link.
Next-hop determinationThe algorithm that a node uses for mapping an IPv6

destination address into a neighbor IPv6 address (either the next router hop or the
destination itself) to which it plans to send traffic for the destination.
Neighbor unreachability detectionHow a node determines that it can no longer

reach a neighbor.
Duplicate address detectionHow a node determines whether an address is already

in use by another node.
Internet Control Message Protocol v6 (ICMPv6)

ICMP sends error messages and information messages related to IP operations. ICMPv6
defines additional error messages and informational messages specific to IPv6.
There are four different ICMPv6 error messages:
Destination UnreachableA packet cannot be delivered due to an inherent problem

with how it is being sent. Includes a code that indicates the nature of the problem
that caused the packet not to be delivered
Packet Too BigSent when a packet is too large to be delivered.
Time ExceededA packet cannot be delivered because it has exceeded the hop
count specified in the basic header hop-by-hop field.
Parameter ProblemIndicates a problem with a field in the IPv6 header or extension

headers that makes it impossible to process the packet.
ICMPv6 information messages are used for sharing the information required to
implement various test, diagnostic, and support functions that are critical to the
operation of IPv6. There are a total of eight different ICMPv6 informational messages:
31
Echo Request
Echo Reply
Router Advertisement
Router Solicitation
Neighbor Advertisement
Neighbor Solicitation
Redirect
Router Renumbering
Static routes for IPv6

Routing information can be configured statically. Whenever a route is configured
statically, the routing information base (RIB) is updated with routes specified through
the static route. These routes should be configured statically in the routing-options
hierarchy. The following configuration is used for enabling static routes for IPv6:
interfaces {
fe/0/1/0 {
unit 0 {
family inet6 {
address fec0:0:0:3::1/64;
}
}
}
}
routing-options {
rib inet6.0 {
static {
route fec0:0:0:4::/64 next-hop fec0:0:0:3::ffff;
}
}
}
user@router> show route table inet6.0
inet6.0: 3 destination, 3 routes (3 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
fec0:0:0:3::/64
*[Direct/0] 00:01:34
> via fe-0/1/0.0

fec:0:0:0:3::1/128
*[Local/0] 00:01:34
Local
fec0:0:0:4::/64
*[Static/5] 00:01:34
> to fec0:0:03:ffff via fe-0/1/0.0
Related
Documentation
32
IPv6 Overview
Understanding Dual Stacking
IS-IS Overview
OSPF Overview
ICMP Router Discovery Overview
MPLS Overview for ACX Series Universal Access Routers on page 115
Configuring the Junos OS for IPv6 Path MTU Discovery
IPv6 Neighbor Discovery Overview
Monitoring the Status of IPv6 Static Routes in the Routing Table
Pseudowire Overview for ACX Series Universal Access Routers

A pseudowire is a Layer 2 circuit or service, which emulates the essential attributes of a
telecommunications service such as a T1 line, over an MPLS packet-switched network.
The pseudowire is intended to provide only the minimum necessary functionality to
emulate the wire with the required degree of faithfulness for the given service definition.
On the ACX Series routers, Ethernet, Asynchronous Transfer Mode (ATM), and
time-division multiplexing (TDM) pseudowires are supported. The following pseudowire
features are supported:
Pseudowire transport service carrying Layer 1 and Layer 2 information over an IP and
MPLS network infrastructure. Only similar end points are supported on the ACX
Seriesfor example, T1 to T1, ATM to ATM, and Ethernet to Ethernet.
Redundant pseudowires backup connections between PE routers and CE devices,

maintaining Layer 2 circuits and services after certain types of failures. Pseudowire
redundancy improves the reliability of certain types of networks (metro for example)
where a single point of failure could interrupt service for multiple customers. The
following pseudowire redundancy features are supported:
Maintenance of Layer 2 circuit services after certain types of failures with a standby
pseudowire, which backs up the connection between PE routers and CE devices.
In case of failure, a protect interface, which backs up the primary interface. Network
traffic uses the primary interface only so long as the primary interface functions. If
the primary interface fails, traffic is switched to the protect interface.
Hot and cold standby enabling swift cut over to the backup or standby pseudowire.
Ethernet connectivity fault management (CFM), which can be used to monitor the
physical link between two routers. The following major features of CFM for Ethernet
pseudowires only are supported:
Connection protection using the continuity check protocol for fault monitoring. The
continuity check protocol is a neighbor discovery and health check protocol that
discovers and maintains adjacencies at the VLAN or link level.
Path protection using the linktrace protocol for path discovery and fault verification.
Similar to IP traceroute, the linktrace protocol maps the path taken to a destination
MAC address through one or more bridged networks between the source and
destination.
33
Related
Documentation
Layer 2 Circuits Overview
Layer 2 Circuits Configuration Guide
Redundant Pseudowires for Layer 2 Circuits and VPLS on page 121
Configuring a Maintenance Endpoint
IEEE 802.1ag OAM Connectivity Fault Management Overview on page 184
Configuring a Connectivity Fault Management Action Profile
Configuring Interfaces for Layer 2 Circuits
TDM Pseudowires Overview on page 120
ATM Pseudowire Overview on page 118
Ethernet Pseudowire Overview on page 119
Synchronous Ethernet Overview on the ACX Series Universal Access Routers

Synchronous Ethernet is supported on the ACX Series routers with Gigabit Ethernet and
10-Gigabit Ethernet SFP and SFP+ transceivers and is compliant with ITU-T
Recommendation G.8261: Timing and synchronization aspects in packet networks and
ITU-T Recommendation G8264: Distribution of timing through packet
networks.Synchronous Ethernet is a physical layer frequency transfer technology modeled
after synchronization in SONET/SDH. Traditional Ethernet nodes, which do not support
Synchronous Ethernet, do not carry synchronization from one node link to another.
Synchronous Ethernetcapable nodes however can synchronize their chassis clock to a
clock recovered from an interface connected to an upstream clock master. After this,
the clock is used to time data sent to downstream clock slaves, forming a synchronization
trail from a Primary Reference Clock (PRC) to Ethernet equipment clocks (EECs) and
transferring frequency synchronization along the trail.
The ITU-T G.8264 specification defines the Synchronization Status Message (SSM)
protocol and its format for Synchronous Ethernet to ensure interoperability between
Synchronous Ethernet equipment used for frequency transferfor example, SONET/SDH.
Synchronous Ethernet provides stable frequency synchronization to a PRC and is not
affected by load on the network. However, it requires that all the nodes from the PRC to
the last downstream node are Synchronous Ethernet capable. Synchronous Ethernet is
a recommended technology for mobile networks that require frequency-only
synchronizationfor example, 2G or 3G base stations.
Related
Documentation
Synchronous Ethernet Overview
TDM CESoPSN Overview

Circuit Emulation Service over Packet-Switched Network (CESoPSN) is an encapsulation
layer intended to carry NxDS0 services over a packet-switched network (PSN). CESoPSN
enables pseudowire emulation of some properties of structure-aware time division
multiplexed (TDM) networks.
34
Particularly, CESoPSN enables the deployment of bandwidth-saving fractional

point-to-point E1 or T1 applications as follows:
Related
Documentation
A pair of customer edge (CE) devices operate as though they were connected by an
emulated E1 or T1 circuit, which reacts to the alarm indication signal (AIS) and remote
alarm indication (RAI) states of the devices local attachment circuits.
The PSN carries only an NxDS0 service, where N is the number of actually used time
slots in the circuit connecting the pair of CE devices, thus saving bandwidth.
TDM CESoPSN on ACX Series Routers Overview on page 35
Configuring CESoPSN Encapsulation on DS Interfaces on page 215
Configuring CE1 Channels Down to DS Interfaces on page 216
TDM CESoPSN on ACX Series Routers Overview

Structure-aware time division multiplexed (TDM) Circuit Emulation Service over
Packet-Switched Network (CESoPSN) is a method of encapsulating TDM signals into
CESoPSN packets, and in the reverse direction, decapsulating CESoPSN packets back
into TDM signals. This method is also termed as Interworking Function (IWF). The following
CESoPSN features are supported on Juniper Networks ACX Series Universal Access
Routers:
Channelization up to the DS0 Level on page 35
Protocol Support on page 36
Packet Latency on page 36
CESoPSN Encapsulation on page 36
CESoPSN Options on page 36
show Commands on page 36
CESoPSN Pseudowires on page 36
Channelization up to the DS0 Level

The following numbers of NxDS0 pseudowires are supported for 16 T1 and E1 built-in
ports and 8 T1 and E1 built-in ports, where N represents the time slots on the T1 and E1
built-in ports.
16 T1 and E1 built-in ports support the following number of pseudowires:
Each T1 port can have up to 24 NxDS0 pseudowires, which add up to a total of up to

384 NxDS0 pseudowires.
Each E1 port can have up to 31 NxDS0 pseudowires, which add up to a total of up to

8 T1 and E1 built-in ports support the following number of pseudowires:
35
Each T1 port can have up to 24 NxDS0 pseudowires, which add up to a total of up to

Each E1 port can have up to 31 NxDS0 pseudowires, which add up to a total of up to

Protocol Support
All protocols that support Structure-Agnostic TDM over Packet (SAToP) support
CESoPSN NxDS0 interfaces.
Packet Latency
The time required to create packets (from 1000 through 8000 microseconds).
CESoPSN Encapsulation
The following statements are supported at the [edit interfaces interface-name] hierarchy
level:
ct1-x/y/z partition partition-number timeslots timeslots interface-type ds
ds-x/y/z:n encapsulation cesopsn
CESoPSN Options
The following statements are supported at the [edit interfaces interface-name
cesopsn-options] hierarchy level:
excessive-packet-loss-rate (sample-period milliseconds)
idle-pattern pattern
jitter-buffer-latency milliseconds
jitter-buffer-packets packets
packetization-latency microseconds
show Commands
The show interfaces interface-name extensive command is supported for t1, e1, and at
interfaces.
CESoPSN Pseudowires
CESoPSN pseudowires are configured on the logical interface, not on the physical
interface. So the unit logical-unit-number statement must be included in the configuration
at the [edit interfaces interface-name] hierarchy level. When you include the unit
logical-unit-number statement, circuit cross-connect (CCC) for the logical interface is
created automatically.
Related
Documentation
36
Setting the CESoPSN Options
Traffic Policing Overview

This topic covers the following information:
Congestion Management for IP Traffic Flows on page 37
Traffic Limits on page 38
Traffic Color Marking on page 39
Forwarding Classes and PLP Levels on page 40
Policer Application to Traffic on page 40
Congestion Management for IP Traffic Flows

Traffic policing, also known rate limiting, is an essential component of network access
security that is designed to thwart denial-of-service (DoS) attacks. Traffic policing enables
you to control the maximum rate of IP traffic sent or received on an interface and also
to partition network traffic into multiple priority levels, also known as classes of service.
A policer defines a set of traffic rate limits and sets consequences for traffic that does not
conform to the configured limits. Packets in a traffic flow that does not conform to traffic
limits are either discarded or marked with a different forwarding class or packet loss
priority (PLP) level.
With the exception of policers configured to rate-limit aggregate traffic (all protocol
families and logical interfaces configured on a physical interface), you can apply a policer
to all IP packets in a Layer 2 or Layer 3 traffic flow at a logical interface.
With the exception of policers configured to rate-limit based on physical interface media
rate, you can apply a policer to specific IP packets in a Layer 3 traffic flow at a logical
interface by using a stateless firewall filter.
You can apply a policer to inbound or outbound interface traffic. Policers applied to
inbound traffic help to conserve resources by dropping traffic that does not need to be
routed through a network. Dropping inbound traffic also helps to thwart denial-of-service
(DoS) attacks. Policers applied to outbound traffic control the bandwidth used.
NOTE: Traffic policers are instantiated on a per-PIC basis. Traffic policing

does not work when the traffic for one local policy decision function (L-PDF)
subscriber is distributed over multiple Multiservices PICs in an AMS group.
37
Traffic Limits
Junos OS policers use the token-bucket algorithm to enforce a limit on average transmit
or receive rate of IP traffic at an interface while allowing bursts of traffic up to a maximum
value based on the overall traffic load. The token-bucket algorithm offers more flexibility
than the leaky-bucket algorithm in that you can allow a specified amount of bursting
before starting to discard packets or apply a penalty to packet output-queuing priority
or packet drop priority.
In the token-bucket model, the bucket represents the policing function. Tokens are added
to the bucket at a fixed rate, but only up to the specified depth of the bucket. Each token
represents a credit for some number of bits, and tokens in the bucket are cashed in
for the ability to transmit or receive traffic at the interface. When sufficient tokens are
present in the bucket, a traffic flow continues unrestricted. Otherwise, packets might be
dropped or else re-marked with a lower forwarding class, a higher packet loss priority
(PLP) level, or both.
The rate at which tokens are added to the bucket represents the highest average
transmit or receive rate in bits per second allowed for a given service level. You specify
this highest average traffic rate as the bandwidth limit of the policer. If the traffic arrival
rate is so high that at some point insufficient tokens are present in the bucket, then the
traffic flow is no longer conforming to the traffic limit.
The depth of the bucket in bytes controls the amount of back-to-back bursting allowed.
You specify this factor as the burst-size limit of the policer. This second limit affects
the average transmit or receive rate by limiting the number of bytes permitted in a
transmission burst for a given interval of time. Bursts exceeding the current burst-size
limit are dropped until there are sufficient tokens available to permit the burst to
proceed.
Figure 8: Network Traffic and Burst Rates
As shown in the figure above, a UPC bar code is a good facsimile of what traffic looks
like on the line; an interface is either transmitting (bursting at full rate) or it is not. The
black lines represent periods of data transmission and the white space represents
periods of silence when the token bucket can replenish.
Depending on the type of policer used, packets in a policed traffic flow that surpasses
the defined limits might be implicitly set to a higher PLP level, assigned to a configured
forwarding class or set to a configured PLP level (or both), or simply discarded. If packets
38
encounter downstream congestion, packets with a low PLP level are less likely to be
discarded than those with a medium-low, medium-high, or high PLP level.
Traffic Color Marking

Based on the particular set of traffic limits configured, a policer identifies a traffic flow
as belonging to one of either two or three categories that are similar to the colors of a
traffic light used to control automobile traffic.
A two-color-marking policer categorizes traffic as either conforming to the traffic limits
(green) or violating the traffic limits (red):
GreenTwo-color-marking policers implicitly set the packets in a green flow to the

low PLP level, and you cannot configure any policer actions for conforming traffic.
RedTwo-color-marking policers do not perform any implicit actions on packets in a

red flow. Instead, those packets are handled according to the actions specified in the
policer configuration. You can configure a two-color-marking policer to simply discard
packets if the traffic flow is red. Alternatively, you can configure a two-color-marking
policer to handle the packets in a red flow by setting the PLP level to either low or high,
assigning the packets to any forwarding class already configured, or both.
On MX Series, M120, and M320 routers and M7i and M10i routers with the Enhanced
CFEB (CFEB-E) only, you can specify two additional PLP levels for packets in a red
flow: medium-low or medium-high.
Three-color-marking policers categorize traffic as conforming to the traffic limits (green),

violating the traffic limits (red), or exceeding the traffic limits but within an allowed range
(yellow):
GreenLike two-color-marking policers, three-color-marking policers implicitly set

the packets in a green flow to the low PLP level, and you cannot configure any policer
actions for conforming traffic.
YellowUnlike two-color-marking policers, three-color-marking policers categorize

a second type of nonconforming traffic: yellow.
Single-rate three-color policing categorizes as yellow traffic that exceeds the traffic
limits while conforming to a second defined burst-size limit. Two-rate three-color
policing categorizes as yellow traffic that exceeds the traffic limits while conforming
to both a second defined burst-size limit and a second defined bandwidth limit.
Three-color-marking policers implicitly set the packets in a yellow flow to the
medium-high PLP level so that the packets incur a less severe penalty than those in a
red flow. You cannot configure any policer actions for yellow traffic.
RedUnlike two-color-marking policers, three-color-marking policers implicitly set

the packets in a red flow to the high PLP level, which is the highest PLP value. You can
also configure a three-color-marking policer to discard the packets in a red flow instead
of forwarding them with a high PLP setting.
Two-color-marking policers allows bursts of traffic for short periods, whereas

three-color-marking policers allow more sustained bursts of traffic.
39
Forwarding Classes and PLP Levels

A packets forwarding class assignment and PLP level are used by the Junos OS
class of service (CoS) features. The Junos CoS features include a set of mechanisms
that you can use to provide differentiated services when best-effort traffic delivery is
insufficient. For router interfaces that carry IPv4, IPv6, and MPLS traffic, you can configure
CoS features to take in a single flow of traffic entering at the edge of your network and
provide different levels of service across the networkinternal forwarding and scheduling
(queuing) for outputbased on the forwarding class assignments and PLP levels of the
individual packets.
NOTE: Forwarding-class or loss-priority assignments performed by a policer

or a stateless firewall filter override any such assignments performed on the
ingress by the CoS default IP precedence classification at all logical interfaces
or by any configured behavior aggregate (BA) classifier that is explicitly
mapped to a logical interface.
Based on CoS configurations, packets of a given forwarding class are transmitted through
a specific output queue, and each output queue is associated with a transmission service
level defined in a scheduler.
Based on other CoS configurations, when packets in an output queue encounter
congestion, packets with higher loss-priority values are more likely to be dropped by the
random early detection (RED) algorithm. Packet loss priority values affect the scheduling
of a packet without affecting the packets relative ordering within the traffic flow.
Policer Application to Traffic

After you have defined and named a policer, it is stored as a template. You can later use
the same policer name to provide the same policer configuration each time you want to
use it. This eliminates the need to define the same policer values more than once.
You can apply a policer to a traffic flow in either of two ways:
You can configure a standard stateless firewall filter that specifies the
policer policer-name nonterminating action or the three-color-policer (single-rate |
two-rate) policer-name nonterminating action. When you apply the standard filter to
the input or output at a logical interface, the policer is applied to all packets of the
filter-specific protocol family that match the conditions specified in the filter
configuration.
With this method of applying a policer, you can define specific classes of traffic on an
interface and apply traffic rate-limiting to each class.
You can apply a policer directly to an interface so that traffic rate-limiting applies to
all traffic on that interface, regardless of protocol family or any match conditions.
You can configure policers at the queue, logical interface, or Layer 2 (MAC) level. Only a
single policer is applied to a packet at the egress queue, and the search for policers occurs
in this order:
40
Related
Documentation
Queue level
Logical interface level
Layer 2 (MAC) level
Stateless Firewall Filter Overview.
Traffic Policer Types
Order of Policer and Firewall Filter Operations
Packet Flow Through the CoS Process Overview
[Warning: element unresolved in stylesheets: <_bookmark> (in <concept>). This is

probably a new element that is not yet supported in the stylesheets.]
Understanding PoE on ACX Series Universal Access Routers

Power over Ethernet (PoE) is the implementation of the IEEE 802.3af and IEEE 802.3at
standards that allows both data and electrical power to pass over a copper Ethernet
LAN cable.
Juniper Networks provides PoE on ACX2000 Universal Access Routers that allows power
delivery up to 65 W per PoE port. PoE ports transfer electrical power and data to remote
devices over standard twisted-pair cables in an Ethernet network. Using PoE ports, you
can plug in devices that require both network connectivity and electrical power, such as
voice over IP (VoIP) and wireless LAN access points.
You can configure the ACX2000 Universal Access Router to act as a power sourcing
equipment (PSE), supplying power to powered devices that are connected on designated
ports.
This topic contains the following sections: :
ACX2000 PoE Specifications on page 41
PoE Classes and Power Ratings on page 42
PoE Options on page 42
ACX2000 PoE Specifications

Table 10 on page 41 lists the PoE specifications for the ACX2000 routers.
Table 10: PoE Specifications for the ACX2000 Routers

Specifications
For ACX2000 Universal Access Routers
Supported standards
IEEE 802.3 AF
IEEE 802.3 AT (PoE+)
Legacy (pre-standards)
Supported ports
Supported on only two Gigabit Ethernet ports (ge-0/1/3

and ge-0/1/7).
41
Table 10: PoE Specifications for the ACX2000 Routers (continued)

Specifications
For ACX2000 Universal Access Routers
Total PoE power sourcing capacity
130 W
Default per port power limit
32 W
Maximum per port power limit
65 W
Power management modes
classPower allocated for each interface can be
configured.
staticPower allocated for interfaces is based on the
class of powered device connected.
high-powerPower allocated for interfaces up to 65 W
per port.
PoE Classes and Power Ratings

A powered device is classified based on the maximum power that it draws across all
input voltages and operational modes. When class-based power management mode is
configured on the ACX2000 routers, power is allocated taking into account the maximum
power ratings defined for the different classes of devices.
Table 11 on page 42 lists the classes and their power ratings as specified by the IEEE
standards.
Table 11: ACX2000 Universal Access Router PoE Specifications

Class
Usage
Minimum Power Levels

Output from PoE Port
Default
15.4 W
Optional
4.0 W
Optional
7.0 W
Optional
15.4 W
Reserved
Class 4 power devices are

eligible to receive power up to
30 W according to the IEEE
standards.
PoE Options
For ACX2000 Universal Access Routers that support PoE ports, the factory default
configuration enables PoE on the PoE-capable ports, with default settings in effect. You
might not have to do any additional configuration if the default settings work for you.
Table 12 on page 43 shows the PoE configuration options and their default settings for
the PoE controller and for the PoE interfaces.
42
Table 12: PoE Configuration Options and Default Settings

Option
Default
Description
guard-band
0W
Reserves up to 19 W power from the PoE power budget to be used in

the case of a spike in PoE power consumption.
management
static
Sets the PoE power management mode for the router. The power
management mode determines how power to a PoE interface is
allocated:
PoE Controller Options
classPower allocated for each interface can be configured.
staticPower allocated for interfaces is based on the class of powered
device connected.
high-powerPower allocated for interfaces up to 65 W per port.
Interface Options
disable (Power over
Ethernet)
Not included in default

configuration
When included in the configuration, disables PoE on the interface. The

interface maintains network connectivity but no longer supplies power
to a connected powered device. Power is not allocated to the interface.
priority (Power over

Ethernet)
low
Sets an interfaces power priority to either low or high. If power is

insufficient for all PoE interfaces, the PoE power to low-priority interfaces
is shut down before power to high-priority interfaces is shut down. Among
interfaces that have the same assigned priority, the power priority is
determined by port number, with lower-numbered ports having higher
priority.
telemetries
Not included in default

configuration
When included in the configuration, enables the logging of power

consumption records on an interface. Logging occurs every 5 minutes
for 1 hour unless you specify a different value for interval (Power over
Ethernet) or duration.
Related
Documentation
Example: Configuring PoE on ACX2000 Routers on page 283
Example: Disabling a PoE Interface on ACX2000 Routers on page 287
43
44
CHAPTER 3
Autoinstallation
ACX Series Autoinstallation Overview on page 45
Before You Begin Autoinstallation on an ACX Series Universal Access Router on page 47
Autoinstallation Configuration of ACX Series Universal Access Routers on page 48
Verifying Autoinstallation on ACX Series Universal Access Routers on page 49
USB Autoinstallation on ACX Series Routers on page 50
ACX Series Autoinstallation Overview

Autoinstallation provides automatic configuration for a new router that you connect to
the network and turn on, or for a router configured for autoinstallation. The autoinstallation
process begins anytime a router is powered on and cannot locate a valid configuration
file in the CompactFlash (CF) card. Typically, a configuration file is unavailable when a
router is powered on for the first time, or if the configuration file is deleted from the CF
card. The autoinstallation feature enables you to deploy multiple routers from a central
location in the network.
For the autoinstallation process to work, you must store one or more host-specific or
default configuration files on a configuration server in the network and have a service
availabletypically Dynamic Host Configuration Protocol (DHCP)to assign an IP address
to the router.
Autoinstallation takes place automatically when you connect an Ethernet on a new
Juniper Networks router to the network and power on the router. To simplify the process,
you can explicitly enable autoinstallation on a router and specify a configuration server,
an autoinstallation interface, and a protocol for IP address acquisition.
This topic describes:
Supported Autoinstallation Interfaces and Protocols on page 45
Typical Autoinstallation Process on a New Router on page 46
Supported Autoinstallation Interfaces and Protocols

Before autoinstallation on a router can take place, the router must acquire an IP address
or a USB key. The protocol or protocols you choose for IP address acquisition determine
the router interface to connect to the network for autoinstallation. The router detects
the connected interface and requests an IP address with a protocol appropriate for the
45
interface. Autoinstallation is supported over an Ethernet LAN interface. For IP address

acquisition, the ACX Series router uses DHCP, BOOTP, or Reverse Address Resolution
Protocol (RARP) on an Ethernet LAN interface.
If the server with the autoinstallation configuration file is not on the same LAN segment
as the new router, or if a specific router is required by the network, you must configure
an intermediate router directly attached to the new router, through which the new router
can send HTTP, FTP, Trivial File Transfer Protocol (TFTP), BOOTP, and Domain Name
System (DNS) requests. In this case, you specify the IP address of the intermediate router
as the location to receive HTTP, FTP, or TFTP requests for autoinstallation.
Typical Autoinstallation Process on a New Router

When a router is powered on for the first time, it performs the following autoinstallation
tasks:
1.
The new router sends out DHCP, BOOTP, or RARP requests on each connected
interface simultaneously to obtain an IP address.
If a DHCP server responds, it provides the router with some or all of the following
information:
An IP address and subnet mask for the autoinstallation interface.
The location of the TFTP (typically), Hypertext Transfer Protocol (HTTP), or FTP
server on which the configuration file is stored.
The name of the configuration file to be requested from the HTTP, FTP, or TFTP
server.
The IP address or hostname of the HTTP, FTP, or TFTP server.

If the DHCP server provides only the hostname, a DNS server must be available on
the network to resolve the name to an IP address.
The IP address of an intermediate router if the configuration server is on a different

LAN segment from the new router.
2. After the new router acquires an IP address, the autoinstallation process on the router
attempts to download a configuration file in the following ways:

a. If the configuration file is specified as a URL, the router fetches the configuration
file from the URL by using HTTP, FTP, or TFTP depending on the protocol specified
in the URL.
b. If the DHCP server specifies the host-specific configuration file (boot file)
hostname.conf, the router uses that filename in the TFTP server request. (In the
filename, hostname is the hostname of the new router.) The autoinstallation process
on the new router makes three unicast TFTP requests for hostname.conf. If these
attempts fail, the router broadcasts three requests to any available TFTP server
for the file.
c. If the new router cannot locate hostname.conf, the autoinstallation process unicasts
or broadcasts TFTP requests for a default router configuration file called
46
Chapter 3: Autoinstallation
network.conf, which contains hostname-to-IP address mapping information, to
attempt to find its hostname.

d. If network.conf contains no hostname entry for the new router, the autoinstallation
process sends out a DNS request and attempts to resolve the new routers IP
address to a hostname.
e. If the new router can determine its hostname, it sends a TFTP request for the
hostname.conf file.
f.
If the new router is unable to map its IP address to a hostname, it sends TFTP
requests for the default configuration file router.conf.
3. After the new router locates a configuration file on a TFTP server, autoinstallation
downloads the file, installs the file on the router, and commits the configuration.
Related
Documentation
autoinstallation
show system autoinstallation status on page 1028
Before You Begin Autoinstallation on an ACX Series Universal Access Router

To configure a router for autoinstallation, complete the following tasks:
Make sure you have a DHCP server on your network to meet your network requirements.
Create one of the following configuration files and store it on an HTTP, FTP, or TFTP
server in the network:
A host-specific file with the name hostname.conf for each router undergoing
autoinstallation. Replace hostname with the name of a router. The hostname.conf
file typically contains all the configuration information necessary for the router with
this hostname.
A default configuration file named router.conf with the minimum configuration

necessary to enable you to telnet into the new router for further configuration.
Physically attach the router to the network using a Gigabit Ethernet interface.
If you configure the DHCP server to provide only the HTTP, FTP, or TFTP server
hostname, add an IP address-to-hostname mapping entry for the HTTP, FTP, or TFTP
server to the DNS database file on the DNS server in the network.
If the new router is not on the same network segment as the DHCP server (or other
router providing IP address resolution), configure an existing router as an intermediate
to receive HTTP, FTP, or TFTP and DNS requests and forward them to the HTTP, FTP,
or TFTP and DNS servers. You must configure the LAN on the intermediate router with
47
the IP addresses of the hosts providing HTTP, FTP, or TFTP and DNS service. Connect
this interface to the new router.
If you are using hostname.conf files for autoinstallation of host-specific configuration

files, you must also complete the following tasks:
Configure the DHCP server to provide a hostname.conf filename to each new router.
Each router uses its hostname.conf filename to request a configuration file from the
TFTP server. Copy the necessary hostname.conf configuration files to the TFTP server.
Create a default configuration file named network.conf and copy it to the TFTP server.
This file contains IP address-to-hostname mapping entries. If the DHCP server does
not send a hostname.conf filename to a new router, the router uses network.conf to
resolve its hostname based on its IP address.
Alternatively, you can add the IP address-to-hostname mapping entry for the new
router to a DNS database file.
The router uses the hostname to request a hostname.conf file from the server.
Related
Documentation
autoinstallation
Autoinstallation Configuration of ACX Series Universal Access Routers

No configuration is required on a router on which you are performing autoinstallation
because it is an automated process. However, to simplify the process, you can specify
one or more interfaces, protocols, and configuration servers to be used for autoinstallation.
To configure autoinstallation:
1.
Specify the URL address of one or more servers from which to obtain configuration
files.
[edit system]
user@host# set autoinstallation configuration-servers tftp://tftpconfig.sp.com
NOTE: You can also use an HTTP or FTP addressfor example,

http://user:password@httpconfig.sp.com or
ftp://user:password@sftpconfig.sp.com.
2. Configure one or more Ethernet interfaces to perform autoinstallation and IP address
acquisition protocols for each interface. The router uses the protocols to send a request
for an IP address for the interface:
48
[edit system]
user@host# set autoinstallation interfaces ge-0/0/0 bootp
Related
Documentation
autoinstallation
Verifying Autoinstallation on ACX Series Universal Access Routers

Purpose
Action
After you have configured autoinstallation, display the status of autoinstallation on an

ACX Series router.
From the CLI, enter the show system autoinstallation status command.
Sample Output
user@host> show system autoinstallation status
Autoinstallation status:
Master state: Active
Last committed file: None
Configuration server of last committed file: 10.25.100.1
Interface:
Name: ge-0/1/0
State: Configuration Acquisition
Acquired:
Address: 192.168.124.75
Hostname: host-ge-000
Hostname source: DNS
Configuration filename: router-ge-000.conf
Configuration filename server: 10.25.100.3
Address acquisition:
Protocol: DHCP Client
Acquired address: None
Protocol: RARP Client
Interface:
Name: ge-0/1/1
State: None
Meaning
Related
Documentation
The output shows the settings configured for autoinstallation. Verify that the values
displayed are correct for the router when it is deployed on the network.
49
autoinstallation
USB Autoinstallation on ACX Series Routers

If you have a new ACX Series router, you can use a Disk-on-Key USB memory stick (USB
key) to configure the router.
This configuration method has the following requirements:
A management device (PC or laptop).
A Disk-on-Key device with one of the following 16-bit or 32-bit file allocation table
(FAT) file systems:
DOS 3.0+ 16-bit FAT (up to 32 MB)
DOS 3.31+ 16-bit FAT (over 32 MB)
FAT32
FAT32, LBA-mapped
16-bit FAT, LBA-mapped
An ACX Series router with the factory configuration. If other Junos OS configuration
files exist on the router, the router cannot read the juniper-config.txt file from the
Disk-on-Key device.
NOTE: The USB-based autoinstallation process overrides the

network-based autoinstallation process. If the ACX Series router detects
a USB Disk-on-Key device containing a valid configuration file during
autoinstallation, it configures the router using the configuration file on
Disk-on-Key instead of fetching the configuration from the network.
To configure an ACX Series router using Disk-on-Key:

1.
Using a text editor on a PC or laptop, create the configuration file, named

juniper-config.txt, as a sequence of configuration commands (set commands). To
reuse configuration from another ACX Series router, the configuration can be saved
in configuration mode as a sequence of configuration commands on the router using
the show | display set | save <filename> command and then copying the <filename>
to the PC or router as juniper-config.txt.
2. Copy the juniper-config.txt file to a Disk-on-Key device.

3. Plug the Disk-on-Key device into the USB port on the new ACX Series router.
50
4. Power on the router by pressing the POWER button on the front panel. Wait for the
router to start and access the Disk-on-Key device (observe the LEDs on the Disk-on-Key
device).
The router reads the juniper-config.txt file from the Disk-on-Key device and commits
the configuration.
5. Remove the Disk-on-Key device from the router.
6. The configuration of the router is complete.
Related
Documentation
autoinstallation
51
52
CHAPTER 4
CoS
CoS on ATM IMA Pseudowire Interfaces Overview on page 54

Routers on page 56
Configuring Classifiers and Rewrite Rules at the Global and Physical Interface
Levels on page 63
Configuring Fixed Classification on an ATM IMA Pseudowire on page 64
Configuring Policing on an ATM IMA Pseudowire on page 65
Configuring Shaping on an ATM IMA Pseudowire on page 68
Example: Configuring Fixed Classification on an ATM IMA Pseudowire on page 69
Example: Configuring Policing on an ATM IMA Pseudowire on page 71
Example: Configuring Shaping on an ATM IMA Pseudowire on page 76
CoS on ACX Series Universal Access Routers Features Overview

The following key CoS features are supported on ACX Series Universal Access Routers:
Physical interface-based classifiers at the [edit class-of-service interfaces

interfaces-name] hierarchy level
Fixed classification for all ingress packets traversing a logical interface to a single
forwarding class. Fixed classification is supported on all interface types.
EXP bits located in each MPLS label and used to encode the CoS value of a packet as
it traverses a label-switched path (LSP). To configure global EXP bits, include the exp
statement at the [edit class-of-service system-defaults classifiers] hierarchy level.
Rewrite rules at the physical and logical interface levels including the following: IP
type-of-service (ToS), DSCP, MPLS EXP bit value, and IEEE 802.1p bit value.
53
Attachment of the following rewrite rules to the physical interface at the [edit
class-of-service interfaces interface-name rewrite-rules] hierarchy level: IP ToS, DSCP,
and IEEE 802.1p bit value.
Rewrite rules for MPLS EXP bits on the logical interface at the [edit class-of-service
interfaces interface-name unit unit-number rewrite-rule] hierarchy level.
NOTE: Fine-grained rewrite is not possible, even when you use multifield
filters, because of the application-specific integrated circuit (ASIC)
limitation.
Queuing and scheduling features include:
Support for up to eight forwarding classes.
Support for up to eight egress queues per port.
Internal buffer of 2 MB with per-egress queue buffer management.
Three weighted random early detection (WRED) curves for TCP and one WRED curve
for non-TCP. There are two fill levels and two drop probabilities per WRED curve; the
drop probability corresponding to the first fill must be zero.
Strict-priority and weighted deficit round-robin scheduling.
Multiple strict-priority queues per port.
Per-queue committed information rate (CIR) and peak information rate (PIR).
Per-physical-port shaping.
Queue statistics features include:
Related
Documentation
Per-egress-queue enqueue statistics in packets, bytes, packets per second (pps), and
bits per second (bps).
Per-egress-queue transmit statistics in packets, bytes, pps, and bps.
Per-egress-queue drop statistics in packets and pps.

Routers on page 56
CoS on ATM IMA Pseudowire Interfaces Overview

ACX Series routers configured with Asynchronous Transfer Mode (ATM) Inverse
Multiplexing ATM (IMA) pseudowire interfaces support class of service (CoS) features
for ingress and egress traffic. Policing is performed by monitoring the configured
parameters on incoming traffic to conserve resources by dropping traffic that may not
54
Chapter 4: CoS
meet those configured parameters. Egress shaping uses queuing and scheduling to
control the bandwidth used. Fixed classification is provided per interface.
ATM IMA pseudowires with the following encapsulation are supported:
atm-ccc-cell-relay
atm-ccc-vc-mux
The following ATM IMA CoS features are supported:
ATM Policing (Cell Based) on page 55
ATM Shaping (Cell Based) on page 56
Fixed Classification on page 56
ATM Policing (Cell Based)

Policing, or rate limiting, enables you to limit the amount of traffic that passes into or out
of the interface. It works with firewall filters to thwart denial-of-service (DoS) attacks.
Networks police traffic by limiting the input or output transmission rate of a class of traffic
on the basis of user-defined criteria. The ATM policer controls the maximum rate of traffic
sent from or received on the interface on which it is applied. To apply limits to the traffic
flow, configure the cdvt and peak-rate parameters within the policer. Define the
policing-action parameter as discard, discard-tag, or count to set a consequence for the
packets that exceed these limits. The consequence of configuring the discard-tag
statement is usually a higher loss priority so that if those packets encounter downstream
congestion, they are discarded first.
On ACX Series routers, policing is cell based and configured in the ingress path of the
ATM IMA pseudowire interface at the [edit firewall] hierarchy level. The following ATM
policing features are supported:
ATM Adaption Layer 5 (AAL5) pseudowires on which cell-based policing is performed

before packet assembly.
Per-ATM IMA channel policing.
Traffic classesConstant bit rate (cbr), real-time variable bit rate (rtvbr), nonreal-time
variable bit rate (nrtvbr), and unspecified bit rate (ubr). All traffic classes must include
the peak-rate and cdvt statements for the configuration to work. With the peak-rate
statement, you can limit the maximum traffic allowed by specifying the largest number
of cells per second that the policer processes before it drops packets. The cdvt
statement ensures that the configuration functions correctly.
With the peak-rate statement, you can limit the maximum traffic allowed by specifying
the largest number of cells per second that the policer processes before it drops packets
For nonconforming cells, the discard, discard-tag, and count actions at the [edit firewall
atm-policer policer-name] hierarchy level. The discard-tag action is applicable to variable
bit-ratenrtvbr and rtvbrtraffic classes.
55
ATM Shaping (Cell Based)

ATM cell-based shaping uses cell-based queuing and scheduling to determine the
maximum amount of traffic that can be transmitted on an ATM IMA pseudowire.
Packet-based shaping is not supported. On ACX Series routers, ATM shaping is configured
in the egress path of the ATM IMA pseudowire interface at the [edit class-of-service]
hierarchy level. The following ATM shaping features are supported:
Prioritized bit rateConstant bit rate (cbr) is the highest priority, followed by variable
bit ratenrtvbr and rtvbr. Unspecified bit rate (ubr) is similar to the best-effort service
for Ethernet traffic.
Constant bit rate shapingConstant bit rate (cbr) shaping uses the peak cell rate to
limit the number of cells per second that the shaper processes before it drops packets.
Variable bit rate shapingVariable bit rate shaping (nrtvbr and rtvbr) uses peak-rate
and sustained-rate.
Unspecified bit rateUnspecified bit rate (ubr) uses peak-rate with the lowest transmit
priority.
Default shaping parameterThe default shaping parameter is Unspecified bit rate,

which is similar to the best-effort service for Ethernet traffic.
Fixed Classification
Fixed classifiers map all traffic on an interface to the forwarding class and loss priority.
The forwarding class determines the output queue. A scheduler uses the loss priority to
control packet discard during periods of congestion by associating different drop profiles
with different loss priorities. On ACX Series routers, the fixed classifier is associated with
the ingress interface. Packets are assigned on the basis of the type of fixed classification
associated with the logical interface. To configure a fixed classifier, include the
forwarding-class class-name statement at the [edit class-of-service interface
interface-name unit logical-unit-number hierarchy level.
Related
Documentation

Routers
ACX Series Universal Access Routers have some statements or statement options
supported on other platforms that are not supported or may not have effect on ACX
Series devices.
The following CLI options are not applicable to ACX Series Universal Access Routers:
[edit class-of-service schedulers scheduler-name priority-level]
low;
56
Chapter 4: CoS
medium-low;
medium-high;
high;
Configure the strict-high-priority queue with unlimited transmission bandwidth so that

all traffic receives precedence over any non strict-high priority queues.
At the [edit class-of-service classifiers type classifier-name] hierarchy level, the dscp-ipv6
and ieee-802.1ad classifier types are not supported. For the dscp classifier type, only the
outer tag is supported.
The following CLI stanza is not applicable to ACX Series Universal Access Routers.
[edit class-of-service interfaces interface-name]
irb {
unit logical-unit-number {
classifiers {
type (classifier-name | default);
}
rewrite-rules {
dscp (rewrite-name | default);
dscp-ipv6 (rewrite-name | default);
exp (rewrite-name | default) protocol protocol-types;
ieee-802.1 (rewrite-name | default) vlan-tag (outer | outer-and-inner);
inet-precedence (rewrite-name | default);
}
}
}
The following CLI statements are not applicable to ACX Series Universal Access Routers.
[edit class-of-service routing-instances routing-instance-name]
[edit class-of-service scheduler-map-chassis map-name]
[edit class-of-service interfaces interface-name unit logical-unit-number]
input-shaping-rate (percent percentage | rate);
input-traffic-control-profile profiler-name shared-instance instance-name;
output-traffic-control-profile profile-name shared-instance instance-name;
per-session-scheduler;
scheduler-map map-name;
shaping-rate rate;
[edit class-of-service interfaces iinterface-name unit logical-unit-number]
classifiers {
type (classifier-name | default);
}
rewrite-rules {
dscp (rewrite-name | default);
dscp-ipv6 (rewrite-name | default);
exp (rewrite-name | default) protocol protocol-types;
exp-push-push-push default;
exp-swap-push-push default;
ieee-802.1 (rewrite-name | default) vlan-tag (outer | outer-and-inner);
inet-precedence (rewrite-name | default);
}
57
In the above stanza, [edit class-of-service interface-name unit logical-unit-number

rewrite-rule exp (rewrite-name | default)] is supported. However, edit [class-of-service
interface-name unit logical-unit-number rewrite-rule exp protocol protocol type] is not
supported.
[edit class-of-service interfaces interface-name interface-set interface-set-name]
excess-bandwidth-share;
internal-node;
output-traffic-control-profile profile-name;
output-traffic-control-profile-remaining profile-name;
Related
Documentation
Configuring CoS on ACX Series Universal Access Routers

Physical interface-based classifiers are supported at the [edit class-of-service interfaces
interfaces-name] hierarchy level. EXP bits are located in each MPLS label and used to
encode the CoS value of a packet as it traverses an LSP. To configure global EXP bits,
include the exp statement at the [edit class-of-service system-defaults classifiers]
hierarchy level.
To configure CoS on ACX Series routers:
1.
Configure the class of service.

[edit]
user@host# edit class-of-service
2. Configure the rewrite rules.
[edit class-of-service]
user@host# edit rewrite-rules (dscp | inet-precedence) rewrite-name
user@host# edit forwarding-class class-name
user@host# set loss-priority low class-name code-points (alias | bits)
3. Configure behavior aggregate classifiers for DiffServ CoS.
user@host# edit classifiers (dscp | inet-precedence) classifier-name
user@host# edit forwarding-classes class-name
user@host# set loss-priority class-name code-points (alias | bits)
4. Configure expedited forwarding class classifiers.
[edit class-of-service classifiers]

user@host# edit forwarding-classes class-name
user@host# set loss-priority class-name code-points (alias | bits)
5. Define the forwarding-class mappings.
user@host# edit forwarding-classes class queue-number queue-number
6. Configure network control forwarding class classifiers.
58
Chapter 4: CoS
user@host# edit forwarding-class class-name

user@host# set loss-priority low class-name code-points (alias | bits)
7. Apply the rewrite rules and classifiers to the interfaces.
[edit class-of-service interface interface-name unit unit-number]

user@host# set rewrite-rule (dscp | inet-precedence ) (rewrite-name| default)
user@host# set classifiers (dscp | inet-precedence ) classifier-name | default)
8. Set the global system default.
[edit ]
user@host# edit class-of-service system-defaults classifiers exp classifier-name
Following is a complete configuration. This example configures ge-1/0/2 as a

network-to-network (NNI) and ge-1/0/1 as a user-to-network (UNI) interface on the ACX
Series router F1, and ge-1/0/3 as an NNI and ge-1/0/4 as a UNI on F2. In addition, the
configuration includes the following:
Fixed classification of customer traffic on UNI ports.
Diffserv code point (DSCP)-based BA classification and rewrites on NNI ports for IP
control traffic at port level.
EXP-based global behavior aggregate (BA) classification and rewrites on NNI ports
for customer traffic from F1 to F2 by using pseudowire.
Common CoS configuration at F1 and F2:

[edit]
class-of-service {
classifiers {
dscp dscp-classf-core {
forwarding-class be {
loss-priority low code-points 011101;
}
forwarding-class be1 {
loss-priority high code-points 010101;
}
forwarding-class ef {
}
forwarding-class ef2 {
}
forwarding-class af {
}
forwarding-class af1 {
}
forwarding-class nc {
}
forwarding-class nc3 {
}
59
}
exp exp-rewrite-core {
loss-priority low code-point 111;
}
loss-priority high code-point 110;
}
}
}
}
}
}
}
}
}
forwarding-classes {
class be queue-num 0;
class ef queue-num 1;
class af queue-num 2;
class nc queue-num 3;
class be1 queue-num 4;
class ef1 queue-num 5;
class af1 queue-num 6;
class nc1 queue-num 7;
}
rewrite-rules {
dscp dscp-rewrite-core {
}
}
60
Chapter 4: CoS
}
}
}
}
}
}
exp exp-rewrite-core {
}
}
}
}
}
}
}
}
}
}
CoS configuration at F1:

class-of-service {
interfaces {
ge-1/0/1 {
unit 0 {
forwarding-class be;
}
}
ge-1/0/2 {
classifiers {
dscp dscp-classf-core;
61
}
rewrite-rules {
dscp dscp-rewrite-core;
}
unit 0 {
rewrite-rules {
exp exp-rewrite-core;
}
}
}
}
system-defaults {
classifiers {
exp exp-classf-core;
}
}
}
CoS configuration at F2:

class-of-service {
interfaces {
ge-1/0/4 {
unit 0 {
forwarding-class be;
}
}
ge-1/0/3 {
classifiers {
dscp dscp-classf-core;
}
rewrite-rules {
dscp dscp-rewrite-core;
}
unit 0 {
rewrite-rules {
exp exp-rewrite-core;
}
}
}
}
system-defaults {
classifiers {
}
}
}
Related
Documentation
62

Routers on page 56
Chapter 4: CoS
Configuring Classifiers and Rewrite Rules at the Global and Physical Interface Levels
On ACX Series Universal Access Routers, CoS supports classification and rewrite at the
global and physical interface levels.
To configure the global EXP classifier, include the following statements at the [edit
class-of-service] system-defaults hierarchy level.
{
system-defaults
{
classifiers exp classifier-name
}
}
CoS supports one global system default classifier of the EXP type, as shown in the
following example:
{
system-defaults {
classifiers {
}
}
}
To configure classifiers and rewrite rules at the physical interface level, include the
following statements at the [edit class-of-service] interfaces hierarchy level.
interfaces {
interface-name
classifiers dscp classifier-name
classifiers inet-precedence classifier-name
classifiers ieee-802.1 [vlan-tag (outer | inner)] classifier-name
rewrite-rules dscp rewrite-name
rewrite-rules inet-prec rewrite-name
rewrite-rules ieee-802.1 rewrite-name
}
The following example shows classifiers and rewrite rules configured on physical
interfaces:
ge-0/1/0 {
unit 0 {
rewrite-rules {
exp custom-exp;
}
}
classifiers {
dscp d1;
ieee-802.1 ci;
}
63
rewrite-rules {
dscp default;
}
}
ge-0/1/2 {
classifiers {
ieee-802.1 ci;
}
rewrite-rules {
ieee-802.1 ri;
}
}
ge-0/1/3 {
unit 0 {
rewrite-rules {
exp custom-exp2;
}
}
}
ge-0/1/7 {
classifiers {
dscp d1;
}
}
ge-0/1/8 {
classifiers {
dscp d1;
}
}
Related
Documentation
Classifiers and Rewrite Rules at the Global and Physical Interface Levels Overview on
page 23
Configuring Fixed Classification on an ATM IMA Pseudowire

You configure fixed classification on the ATM IMA pseudowire logical interface (unit) by
specifying a forwarding class, which is applied to all packets received by the logical
interface. To complete this configuration, you can define a forwarding class at the [edit
class-of-service forwarding-classes] hierarchy level or by not defining a forwarding class,
the default class is used.
The following steps require you to navigate various levels in the configuration hierarchy.
For information about navigating the CLI, see Using the CLI Editor in Configuration Mode
in the CLI User Guide.
To configure CoS fixed classification on an ATM IMA pseudowire:
1.
Define the ATM IMA pseudowire. For information about defining the ATM IMA
pseudowire, seeConfiguring Inverse Multiplexing for ATM (IMA) on page 224.
2. In configuration mode, go to the [edit class-of-service] hierarchy level:
[edit]
64
Chapter 4: CoS
3. Define the forwarding class to apply to the input logical interface, if the default
forwarding class is not used:

user@host# set forwarding-classes class class-name queue-num queue-num
4. Specify the ATM IMA interface on which to include the forwarding class:
user@host# edit interfaces at-fpc/pic/port
5. Configure the logical unit:
[edit class-of-service interfaces at-fpc/pic/port]

user@host# edit unit logical-unit-number
6. Apply the forwarding class to the logical interface:
[edit class-of-service interfaces at-fpc/pic/port unit logical-unit-number]

user@host# set forwarding-class class-name
After you have configured fixed classification, enter the commit command from
configuration mode.
Related
Documentation
Configuring Policing on an ATM IMA Pseudowire

On ACX Series routers, the ATM policer is attached to the ingress path of the ATM IMA
interface, making it an input policer configured at the [edit firewall] hierarchy level. This
input policer is then applied to an ATM IMA logical interface. The ATM IMA logical interface
must have circuit cross-connect (CCC) family encapsulation configured for the
configuration to work.
This topic includes the following tasks:
1.
Configuring an Input Policer on page 65
2. Configuring the ATM IMA Interface on page 67
Configuring an Input Policer

To configure policing on an ATM IMA pseudowire:
1.
2. In configuration mode, go to the [edit firewall] hierarchy level:
65
[edit]
user@host# edit firewall
3. Define the policer:
[edit firewall]
user@host# edit atm-policer atm-policer-name
The following steps describe the ATM policer options that you can configure. The
options include: atm-service, cdvt, logical-interface-policer, max-burst-size, peak-rate,
policing-action, and sustained-rate.
4. Specify the ATM service category:
[edit firewall atm-policer atm-policer-name]

user@host# set atm-service (cbr | nrt-vbr | rt-vbr | ubr)
Select one of the following service categories, depending on the policing needs of
your network: constant bit rate (cbr), nonreal-time variable bit rate (nrtvbr), real-time
variable bit rate (rtvbr), and unspecified bit rate ubr. All service categories must include
the peak-rate and cdvt statements for the configuration to work. The peak-rate
statement limits the maximum traffic allowed and the cdvt statement ensures that
the configuration functions correctly.
5. Apply limits to the traffic flow by configuring the cell delay variation tolerance (cdvt),
from 1 microsecond through 1,800,000,000 microseconds:

user@host# set cdvt cdvt-time
6. (Optional) Define the policer as a logical interface policer:

user@host# set logical-interface-policer
The logical interface policer is associated with the interface on which the policer is
applied. To configure the policer on multiple interfaces, you must apply this policer
on each interface explicitly.
7. (Optional) Define the maximum number of cells that a burst of traffic can contain,
from 1 through 4000 cells:

user@host# set max-burst-size max-burst-size
8. Apply limits to the traffic flow by specifying the largest number of cells per second
that the policer processes before it drops packets, from 61 cells per second (cps)
through 38,641 cps:
user@host# set peak-rate peak-rate
The maximum peak rate value depends on the number of links in the IMA bundlethe
more links, the higher the possible peak rate.
9. Define the policing-action parameter to set a consequence for the packets that exceed
the traffic limits:

user@host# set policing-action (discard | discard-tag | count)
66
Chapter 4: CoS
10. Define the normal traffic rate averaged over time, from 61 cps through 38,641 cps):

user@host# set sustained-rate cps
After you have configured policing, enter the commit command from configuration mode.
Configuring the ATM IMA Interface

To create the ATM IMA interface on which to apply the ATM policer:
1.
In configuration mode, go to the [edit interfaces] hierarchy level:

[edit]
user@host# edit interfaces
2. Define the ATM interface:
[edit interfaces]
user@host# edit at-fpc/pic/port
3. Specify the ATM interface unit:
[edit interfaces at-fpc/pic/port]

user@host# edit unit logical-unit-number
4. Apply the ATM policer:
[edit interfaces at-fpc/pic/port unit logical-unit-number]

user@host# set atm-policer input-atm-policer policer-name
5. Specify the encapsulation family type:
[edit interfaces at-fpc/pic/port unit logical-unit-number]

user@host# set family ccc
After you have configured the ATM IMA interface, enter the commit command from
configuration mode.
Related
Documentation
67
Configuring Shaping on an ATM IMA Pseudowire

On ACX Series routers, ATM shaping is applied in the egress direction only. Only cell-based
shaping is supported. A traffic control profile, which defines the ATM scheduling
parameters, is configured at the [edit class-of-service] hierarchy level. The traffic control
profile is then applied to the ATM logical interface configured at the [edit class-of-service]
hierarchy level.
NOTE: The configuration of ATM shaping requires the inclusion of the per-unit
scheduler statement at the [edit interfaces interface-name] hierarchy level.
To configure a traffic-shaping profile on an ATM IMA pseudowire:
1.
2. In configuration mode, go to the [edit class-of-service] hierarchy level:
[edit]
3. Specify the traffic -shaping profile:
user@host# edit traffic-control-profiles profile-name
The following steps describe the traffic control profile options that you can configure.
The options include: atm-service, delay-buffer-rate, max-burst-size, peak-rate, and
sustained-rate.
4. (Optional) Specify the service category that determines the traffic-shaping parameter
for the ATM queue at the ATM IMA pseudowire:

[edit class-of-service traffic-control-profiles profile-name]
user@host# set atm-service (cbr | nrt-vbr | rt-vbr)
Select one of the following service traffic categories, depending on the needs of your
network: constant bit rate (cbr), nonreal-time variable bit rate (nrtvbr), or real-time
variable bit rate (rtvbr). All service traffic categories must include the peak-rate and
cdvt statements for the configuration to work. The peak-rate statement limits the
maximum traffic allowed and the cdvt statement ensures that the configuration
functions correctly.
5. (Optional) Specify the delay-buffer calculation:

user@host# set delay-buffer-rate cps
The delay-buffer calculation can be specified as cells per second1000 cells per
second (cps) through 160,000,000,000 cps.
68
Chapter 4: CoS
6. (Optional) Define the maximum number of cells that a burst of traffic can contain,
from 1 through 4000 cells:

user@host# set max-burst-size max-burst-size
7. Define the largest number of cells per second that the shaper processes before it
drops packets, from 61 cps through 38,641 cps:

user@host# set peak-rate peak-rate
The maximum peak rate value depends on the number of links in the IMA bundlethe
more links, the higher the possible peak rate.
8. (Optional) Define the normal traffic rate averaged over time, from 61 cps through
38,641 cps:
user@host# set sustained-rate cps
9. To complete the configuration, configure the per-unit scheduler:
[edit interfaces interface-name]

user@host# set per-unit scheduler
After you have configured shaping on the ATM IMA interface, enter the commit command
from configuration mode.
Related
Documentation
Example: Configuring Fixed Classification on an ATM IMA Pseudowire

This example shows the configuration of fixed classification on an ATM IMA pseudowire.
Fixed classification is configured on the logical interface (unit) of the ATM IMA pseudowire.
The software assigns the fixed classification to packets on the basis of the fixed
classification parameters associated with the logical interface on which the ATM cells
are received.
Requirements on page 69
Overview on page 70
Configuration on page 70
Requirements
This example uses the following hardware and software components:
ACX Series router
Junos OS Release 12.2 or later
69
A previously configured ATM IMA pseudowire. For steps to configure an ATM IMA
pseudowire, see Configuring Inverse Multiplexing for ATM (IMA) on page 224.
Overview
In this example, the configured forwarding class fc-1 is applied to all packets received on
the ingress logical interface at-0/0/16 unit 0. The fixed classification classifies all traffic
on the logical interface unit zero (0) to queue-num 1.
Configuration
The following example requires you to navigate various levels in the configuration
hierarchy. For information about navigating the CLI, see Using the CLI Editor in
Configuration Mode in the CLI User Guide.
To configure fixed classification on an ATM IMA Pseudowire, perform these tasks:
CLI Quick
Configuration
Configuring a Forwarding Class on page 70
Applying the Forwarding Class on page 70
Results on page 71
To quickly configure this example, copy the following commands, paste them in a text
file, remove any line breaks, change any details necessary to match your network
configuration, and then copy and paste the commands into the CLI at the [edit] hierarchy
level:
set class-of-service forwarding-classes class fc-1 queue-num 1
set class-of-service interfaces at-0/0/16 unit 0 forwarding-class fc-1
Configuring a Forwarding Class

Step-by-Step
Procedure
To define a forwarding class, which is applied to the ingress logical interface:

1.
In configuration mode, go to the following hierarchy level:

[edit]
user@host# edit class-of-service forwarding-classes
2.
Define the forwarding class to apply to the input logical interface:

[edit class-of-service forwarding-classes]
user@host# set class fc-1 queue-num 1
Applying the Forwarding Class

Step-by-Step
Procedure
To apply the forwarding class to the logical ATM IMA pseudowire:

1.
Specify the ATM IMA interface on which to include the forwarding class:
user@host# edit interfaces at-0/0/16
2.
Configure the logical interface:

[edit class-of-service interfaces at-0/0/16 ]
70
Chapter 4: CoS
user@host# edit unit 0

3.
Apply the previously configured forwarding class to the logical interface:

[edit class-of-service interfaces at-0/0/16 unit 0]
user@host# set forwarding-class fc-1
Results
From configuration mode, confirm your configuration by entering the show command. If
the output does not display the intended configuration, repeat the configuration
instructions in this example to correct it.
In the following example, all packets coming into the router from the at-0/0/16 unit 0
interface are assigned to the fc-1 forwarding class:
user@host# show
forwarding-classes {
class fc-1 queue-num 1;
}
interfaces {
at-0/0/16 {
unit 0 {
forwarding-class fc-1;
}
}
}
After you have completed the configuration, enter the commit command from
configuration mode.
Related
Documentation
Example: Configuring Policing on an ATM IMA Pseudowire

This example shows the configuration of policing on an ATM IMA pseudowire. On ACX
Series routers, the ATM policer is an input policer that is applied to the ATM IMA logical
interface. The ATM IMA logical interface must have the circuit cross-connect (CCC)
encapsulation family configured for the configuration to work.
Overview on page 72
71
Requirements
ACX Series router
Overview
In this example, the ATM IMA pseudowire logical interfaces (unit 0, unit 1 and unit 2) are
configured with three input ATM policerspolicer-1, policer-2, and policer-3. The ATM
policers are configured with the following parameters:
logical-interface-policerThe logical interface policer is configured explicitly on each
logical interface (unit).
atm-serviceThe ATM service category used to define the bit rate at which traffic is
policed.
peak-rateThe peak rate is the top rate at which traffic can burst. This is a mandatory
statement that must be included for the configuration to work correctly.
sustained-rateThe sustained rate is the normal traffic rate averaged over time.
maximum-burst-sizeThe maximum burst size is the maximum number of cells that
a burst of traffic can contain.
cdvtThe Cell Delay Variation Tolerance is a mandatory statement that must be
included for the configuration to work correctly.
policing-actionThe specified policing action used when the traffic exceeds the limits
set for the policer.
Configuration
To configure policing on an ATM IMA pseudowire, perform these tasks:
CLI Quick
Configuration
72
Configuring an ATM Policer on page 73
Applying the ATM Policer on the ATM IMA Logical Interface on page 74
Results on page 74
level:
Chapter 4: CoS
set firewall atm-policer policer-1 logical-interface-policer

set firewall atm-policer policer-1 atm-service rtvbr
set firewall atm-policer policer-1 peak-rate 2k
set firewall atm-policer policer-1 sustained-rate 1800
set firewall atm-policer policer-1 max-burst-size 400
set firewall atm-policer policer-1 cdvt 900001
set firewall atm-policer policer-1 policing-action discard-tag
set firewall atm-policer policer-2 atm-service nrtvbr
set firewall atm-policer policer-2 peak-rate 1800
set firewall atm-policer policer-2 sustained-rate 1500
set firewall atm-policer policer-2 max-burst-size 300
set firewall atm-policer policer-2 policing-action discard
set firewall atm-policer policer-3 atm-service cbr
set firewall atm-policer policer-3 peak-rate 2k
set firewall atm-policer policer-3 policing-action count
set interfaces at-0/0/16 unit 0 atm-policer input-atm-policer policer-1
set interfaces at-0/0/16 unit 0 family ccc
Configuring an ATM Policer

Step-by-Step
Procedure
To configure the ATM policer, which is applied to the logical ATM IMA pseudowire:
1.
Define the policer:

[edit]
user@host# edit firewall atm-policer policer-1
2.
Specify the parameters for policer-1:

[edit firewall atm-policer policer-1]
user@host# set atm-service rtvbr
user@host# set peak-rate 2k
user@host# set sustained-rate 1800
user@host# set max-burst-size 400
user@host# set cdvt 900001
user@host# set policing-action discard-tag
3.

user@host# set atm-service nrtvbr
user@host# set peak-rate 1800
user@host# set sustained-rate 1500
user@host# set policing-action discard
4.
73

user@host# set atm-service cbr
user@host# set policing-action count
After you have configured the ATM policers, enter the commit command from
configuration mode.
Applying the ATM Policer on the ATM IMA Logical Interface

Step-by-Step
Procedure
To create the ATM IMA logical interface on which to apply the ATM policers:
1.
Define the ATM interface:

[edit interfaces]
user@host# edit interfaces at-0/0/16
2.
Specify the ATM interface unit and apply the first input policer:
[edit interfaces at-0/0/16]
user@host# set unit 0 atm-policer input-atm-policer policer-1
3.
Specify the encapsulation family type for unit 0:

user@host# set unit 0 family ccc
4.
Specify the ATM interface unit and apply the second input policer:
5.

6.
Specify the ATM interface unit and apply the third input policer:
7.

Results
[edit firewall]
user@host# show
atm-policer policer-1 {
logical-interface-policer;
atm-service rtvbr;
74
Chapter 4: CoS
peak-rate 2k;
sustained-rate 1800;
max-burst-size 400;
cdvt 900001;
policing-action discard-tag;
}
atm-service nrtvbr;
peak-rate 1800;
sustained-rate 1500;
max-burst-size 300;
cdvt 999991;
policing-action discard;
}
atm-service cbr;
peak-rate 2k;
cdvt 800001;
policing-action count;
}
[edit interfaces]
user@host# show
at-0/0/16 {
unit 0 {
atm-policer {
input-atm-policer policer-1;
}
family ccc;
}
unit 1 {
atm-policer {
}
family ccc;
}
unit 2 {
atm-policer {
}
family ccc;
}
}
configuration mode.
Related
Documentation
75
Example: Configuring Shaping on an ATM IMA Pseudowire

The following example shows the configuration of shaping on an ATM IMA pseudowire.
On ACX Series routers, the ATM shaper is applied on the egress logical (unit) interface.
Overview on page 76
Requirements
ACX Series router
Overview
In this example, an ATM IMA pseudowire logical interfaces (unit 0) is configured with
two egress ATM shapersprofile-1 and profile-2. The ATM shaping profiles are configured
with the following parameters:
atm-serviceATM service category used to define the bit rate at which traffic is policed.
peak-rateTop rate at which traffic can burst. This is a mandatory statement that
must be included for the configuration to work correctly.
sustained-rateNormal traffic rate averaged over time.
maximum-burst-sizeMaximum number of cells that a burst of traffic can contain.
In addition to the configuration of shaping, this example includes the configuration of

tracing operations for the class-of-service (CoS) configuration.
Configuration
To configure shaping on an ATM IMA pseudowire, perform these tasks:
CLI Quick
Configuration
Configuring Tracing Operations on page 78
Results on page 78
level:
set class-of-service traffic-control-profiles profile-1 atm-service rtvbr
set class-of-service traffic-control-profiles profile-1 peak-rate 5k
76
Chapter 4: CoS
set class-of-service traffic-control-profiles profile-1 sustained-rate 3k

set class-of-service traffic-control-profiles profile-1 max-burst-size 400
set class-of-service traffic-control-profiles profile-2 atm-service cbr
set class-of-service traffic-control-profiles profile-2 peak-rate 1k
set class-of-service interfaces at-0/0/16 unit 0 output-traffic-control-profile profile-1
set interfaces at-0/0/16 per-unit-scheduler
set class-of-service traceoptions file cos
set class-of-service traceoptions file size 1000000000
set class-of-service traceoptions flag all
Configuring Shaping on an ATM IMA Pseudowire

Step-by-Step
Procedure
To configure shaping on an ATM IMA pseudowire:
1.
In configuration mode, go to the [edit class-of-service] hierarchy level:

[edit]
2.
Specify the first traffic control profile:

user@host# edit traffic-control-profiles profile-1
3.
Specify the ATM real-time variable bit rate rtvbr service traffic category:
[edit class-of-service traffic-control-profiles profile-1]
user@host# set atm-service rtvbr
4.
Define the largest number of cells per second that the shaper processes before it
drops packets:
5.
Define the normal traffic rate averaged over time, from 61 cps through 38,641 cps:
user@host# set sustained-rate 3k
6.
Define the maximum number of cells that a burst of traffic can contain, from 1
through 4000 cells:
7.
Specify the second traffic control profile:

user@host# edit traffic-control-profiles profile-2
8.
Specify the ATM constant bit rate cbr service traffic category:
user@host# set atm-service cbr
77
9.
drops packets:
10.
drops packets:
11.
Apply the first shaping traffic profile to the ATM IMA pseudowire logical interface:
user@host# edit interfaces at-0/0/16 unit 101 output-traffic-control-profile profile-1
12.
Configure the per-unit scheduler:

user@host# set interfaces at-0/0/16 per-unit-scheduler
Configuring Tracing Operations

Step-by-Step
Procedure
To define tracing operations for the class-of-service (CoS) configuration:

1.
Configure class-of-service (CoS) tracing options:

[edit]
user@host# edit class of service traceoptions
2.
Create the file to receive the tracing operation output:

[edit class-of-service traceoptions]
user@host# set file cos
3.
Define the maximum size of the file:

user@host# set file size 1000000000
4.
Specify the tracing operation to perform:

user@host# set flag all
Results
user@host# show
traffic-control-profiles {
profile-1 {
atm-service rtvbr;
peak-rate 5k;
sustained-rate 3k;
max-burst-size 400;
78
Chapter 4: CoS
}
profile-2 {
atm-service cbr;
peak-rate 1k;
}
}
interfaces {
at-0/0/16 {
unit 101 {
output-traffic-control-profile profile-1;
}
}
}
traceoptions {
file cos size 1000000000;
flag all;
}
[edit interfaces]
user@host# show
at-0/0/16 {
per-unit-scheduler;
}
}
configuration mode.
Related
Documentation
79
80
CHAPTER 5
Firewall Filters
Standard Firewall Filter Match Conditions and Actions on ACX Series Routers
Overview on page 81
Standard Firewall Filter Match Conditions for IPv4 Traffic on ACX Series
Routers on page 83
Standard Firewall Filter Match Conditions for MPLS Traffic on ACX Series
Routers on page 86
Standard Firewall Filter Terminating Actions on ACX Series Routers on page 86
Standard Firewall Filter Nonterminating Actions on ACX Series Routers on page 88
Filter-Based Forwarding for Routing Instances on page 90
Forwarding Table Filters for Routing Instances on ACX Series Routers on page 91
Standard Firewall Filter Match Conditions and Actions on ACX Series Routers Overview
On ACX Series Universal Access Routers, you can configure firewall filters to filter packets
and to perform an action on packets that match the filter. The match conditions specified
to filter the packets are specific to the type of traffic being filtered.
NOTE: On ACX Series routers, the filter for the exiting traffic (egress filter)
can be applied only for interface-specific instances of the firewall filter.
Table 13 on page 81 describes the types of traffic for which you can configure standard
stateless firewall filters.
Table 13: Standard Firewall Filter Match Conditions by Protocol Family for ACX Series Routers
Traffic Type
Hierarchy Level at Which Match Conditions Are Specified
Protocol-independent
[edit firewall family any filter filter-name term term-name]
No match conditions are supported for this traffic type on ACX

Series routers.
81
Table 13: Standard Firewall Filter Match Conditions by Protocol Family for ACX Series
Routers (continued)
Traffic Type
Hierarchy Level at Which Match Conditions Are Specified
IPv4
[edit firewall family inet filter filter-name term term-name
For the complete list of match conditions, see Standard Firewall

Filter Match Conditions for IPv4 Traffic on ACX Series Routers
on page 83.
MPLS
[edit firewall family mpls filter filter-name term term-name]
For the complete list of match conditions, see Standard Firewall

Filter Match Conditions for MPLS Traffic on ACX Series Routers
on page 86.
Layer 2 CCC
[edit firewall family ccc filter filter-name term term-name]
No match conditions are supported for this traffic type on ACX

Series routers.
Under the then statement for a standard stateless firewall filter term, you can specify
the actions to be taken on a packet that matches the term.
Table 14 on page 82 summarizes the types of actions you can specify in a standard
stateless firewall filter term.
Table 14: Standard Firewall Filter Action Categories for ACX Series Routers
Type of Action
Description
Comment
Terminating
Halts all evaluation of a firewall filter for a specific

packet. The router performs the specified action,
and no additional terms are used to examine the
packet.
See Standard Firewall Filter

Terminating Actions on ACX Series
Routers on page 86.
You can specify only one terminating action in a

standard firewall filter. You can, however, specify
one terminating action with one or more
nonterminating actions in a single term. For
example, within a term, you can specify accept
with count and syslog.
Nonterminating
Related
Documentation
82
Performs other functions on a packet (such as

incriminating a counter, logging information about
the packet header, sampling the packet data, or
sending information to a remote host using the
system log functionality), but any additional terms
are used to examine the packet.
Guidelines for Configuring Standard Firewall Filters
Interface-Specific Firewall Filter Instances Overview
See Standard Firewall Filter

Nonterminating Actions on ACX
Series Routers on page 88.
Chapter 5: Firewall Filters
Standard Firewall Filter Match Conditions for IPv4 Traffic on ACX Series Routers
On ACX Series routers, you can configure a standard stateless firewall filter with match
conditions for IP version 4 (IPv4) traffic (family inet). Table 15 on page 83 describes the
match conditions you can configure at the [edit firewall family inet filter filter-name term
term-name from] hierarchy level.
Table 15: Standard Firewall Filter Match Conditions for IPv4 Traffic on ACX Series Routers
Match Condition
Description
destination-address address
Match the IPv4 destination address field.

NOTE: On ACX Series routers, you can specify only one destination address. A list of IPv4
destination addresses is not supported.
destination-port number
Match the UDP or TCP destination port field.

If you configure this match condition, we recommend that you also configure the protocol udp
or protocol tcp match statement in the same term to specify which protocol is being used on
the port.
NOTE: On ACX Series routers, you can specify only one destination port number. A list of port
numbers is not supported.
In place of the numeric value, you can specify one of the following text synonyms (the port
numbers are also listed): afs (1483), bgp (179), biff (512), bootpc (68), bootps (67), cmd (514),
cvspserver (2401), dhcp (67), domain (53), eklogin (2105), ekshell (2106), exec (512), finger (79),
ftp (21), ftp-data (20), http (80), https (443), ident (113), imap (143), kerberos-sec (88),
klogin (543), kpasswd (761), krb-prop (754), krbupdate (760), kshell (544), ldap (389), ldp (646),
login (513), mobileip-agent (434), mobilip-mn (435), msdp (639), netbios-dgm (138),
netbios-ns (137), netbios-ssn (139), nfsd (2049), nntp (119), ntalk (518), ntp (123), pop3 (110),
pptp (1723), printer (515), radacct (1813), radius (1812), rip (520), rkinit (2108), smtp (25),
snmp (161), snmptrap (162), snpp (444), socks (1080), ssh (22), sunrpc (111), syslog (514),
tacacs (49), tacacs-ds (65), talk (517), telnet (23), tftp (69), timed (525), who (513), or
xdmcp (177).
dscp number
Match the Differentiated Services code point (DSCP). The DiffServ protocol uses the
type-of-service (ToS) byte in the IP header. The most significant 6 bits of this byte form the
DSCP. For more information, see the Junos OS Class of Service Configuration Guide.
You can specify a numeric value from 0 through 63. To specify the value in hexadecimal form,
include 0x as a prefix. To specify the value in binary form, include b as a prefix.
In place of the numeric value, you can specify one of the following text synonyms (the field
values are also listed):
RFC 3246, An Expedited Forwarding PHB (Per-Hop Behavior), defines one code point: ef (46).
RFC 2597, Assured Forwarding PHB Group, defines 4 classes, with 3 drop precedences in
each class, for a total of 12 code points:
af11 (10), af12 (12), af13 (14)
af21 (18), af22 (20), af23 (22)
af31 (26), af32 (28), af33 (30)
af41 (34), af42 (36), af43 (38)
83
Routers (continued)
Match Condition
Description
fragment-flags number
(Ingress only) Match the three-bit IP fragmentation flags field in the IP header.
In place of the numeric field value, you can specify one of the following keywords (the field
values are also listed): dont-fragment (0x4), more-fragments (0x2), or reserved (0x8).
icmp-code number
Match the ICMP message code field.

If you configure this match condition, we recommend that you also configure the protocol icmp
match condition in the same term.
If you configure this match condition, you must also configure the icmp-type message-type
match condition in the same term. An ICMP message code provides more specific information
than an ICMP message type, but the meaning of an ICMP message code is dependent on the
associated ICMP message type.
values are also listed). The keywords are grouped by the ICMP type with which they are
associated:
icmp-type number
parameter-problem: ip-header-bad (0), required-option-missing (1)
redirect: redirect-for-host (1), redirect-for-network (0), redirect-for-tos-and-host (3),

redirect-for-tos-and-net (2)
time-exceeded: ttl-eq-zero-during-reassembly (1), ttl-eq-zero-during-transit (0)
unreachable: communication-prohibited-by-filtering (13), destination-host-prohibited (10),

destination-host-unknown (7), destination-network-prohibited (9),
destination-network-unknown (6), fragmentation-needed (4), host-precedence-violation (14),
host-unreachable (1), host-unreachable-for-TOS (12), network-unreachable (0),
network-unreachable-for-TOS (11), port-unreachable (3), precedence-cutoff-in-effect (15),
protocol-unreachable (2), source-host-isolated (8), source-route-failed (5)
Match the ICMP message type field.

If you configure this match condition, we recommend that you also configure the protocol icmp
match condition in the same term.
values are also listed): echo-reply (0), echo-request (8), info-reply (16), info-request (15),
mask-request (17), mask-reply (18), parameter-problem (12), redirect (5),
router-advertisement (9), router-solicit (10), source-quench (4), time-exceeded (11),
timestamp (13), timestamp-reply (14), or unreachable (3).
ip-options values
Match the 8-bit IP option field, if present, to the specified value.

ACX Series routers support only the ip-options_any match condition, which ensures that the
packets are sent to the Packet Forwarding Engine for processing.
NOTE: On ACX Series routers, you can specify only one IP option value. Configuring multiple
values is not supported.
84
Routers (continued)
Match Condition
Description
precedence
ip-precedence-field
Match the IP precedence field.

In place of the numeric field value, you can specify one of the following text synonyms (the
field values are also listed): critical-ecp (0xa0), flash (0x60), flash-override (0x80),
immediate (0x40), internet-control (0xc0), net-control (0xe0), priority (0x20), or routine (0x00).
You can specify precedence in hexadecimal, binary, or decimal form.
protocol number
Match the IP protocol type field. In place of the numeric value, you can specify one of the
following text synonyms (the field values are also listed): ah (51), dstopts (60), egp (8), esp (50),
fragment (44), gre (47), hop-by-hop (0), icmp (1), icmp6 (58), icmpv6 (58), igmp (2), ipip (4),
ipv6 (41), ospf (89), pim (103), rsvp (46), sctp (132), tcp (6), udp (17), or vrrp (112).
source-address address
Match the IPv4 address of the source node sending the packet.
source-port number
Match the UDP or TCP source port field.

If you configure this match condition for IPv4 traffic, we recommend that you also configure
the protocol udp or protocol tcp match statement in the same term to specify which protocol
is being used on the port.
In place of the numeric value, you can specify one of the text synonyms listed with the
destination-port number match condition.
tcp-flags value
Match one or more of the low-order 6 bits in the 8-bit TCP flags field in the TCP header.
To specify individual bit fields, you can specify the following text synonyms or hexadecimal
values:
fin (0x01)
syn (0x02)
rst (0x04)
push (0x08)
ack (0x10)
urgent (0x20)
In a TCP session, the SYN flag is set only in the initial packet sent, while the ACK flag is set in
all packets sent after the initial packet.
You can string together multiple flags using the bit-field logical operators.
For combined bit-field match conditions, see the tcp-initial match conditions.
If you configure this match condition, we recommend that you also configure the protocol tcp
match statement in the same term to specify that the TCP protocol is being used on the port.
tcp-initial
Match the initial packet of a TCP connection. This is an alias for tcp-flags "(!ack & syn)".
This condition does not implicitly check that the protocol is TCP. If you configure this match
condition, we recommend that you also configure the protocol tcp match condition in the same
term.
85
Routers (continued)
Match Condition
Description
ttl number
Match the IPv4 time-to-live number. Specify a TTL value or a range of TTL values. For number,
you can specify one or more values from 2 through 255.
Related
Documentation
on page 81
Standard Firewall Filter Match Conditions for MPLS Traffic on ACX Series Routers
On ACX Series routers, you can configure a standard stateless firewall filter with match
conditions for MPLS traffic (family mpls).
NOTE: The input-list filter-names and output-list filter-names statements for

firewall filters for the mpls protocol family are supported on all interfaces
with the exception of management interfaces and internal Ethernet interfaces
(fxp or em0), loopback interfaces (lo0), and USB modem interfaces (umd).
Table 16 on page 86 describes the match conditions you can configure at the [edit firewall
family mpls filter filter-name term term-name from] hierarchy level.
Table 16: Standard Firewall Filter Match Conditions for MPLS Traffic on ACX Series Routers
Match Condition
Description
exp number
Experimental (EXP) bit number or range of bit numbers in the MPLS header. For number, you
can specify one or more values from 0 through 7 in decimal, binary, or hexadecimal format.
Related
Documentation
on page 81
Standard Firewall Filter Terminating Actions on ACX Series Routers

Standard stateless firewall filters support different sets of terminating actions for each
protocol family.
86
NOTE: ACX Series routers do not support the next term action.
Table 17 on page 87 describes the terminating actions you can specify in a standard
firewall filter term.
Table 17: Terminating Actions for Standard Firewall Filters on ACX Series Routers
Terminating
Action
Description
Protocols
accept
Accept the packet.
family any
family inet
family mpls
family ccc
family any
family inet
family mpls
family ccc
discard
reject message-type
Discard a packet silently, without sending an Internet Control Message Protocol

(ICMP) message. Discarded packets are available for logging and sampling.
Reject the packet and return an ICMPv4 or ICMPv6 message:
If no message type is specified, a destination-unreachable message is returned by

default.
If tcp-reset is specified as the message type, tcp-reset is returned only if the packet
is a TCP packet. Otherwise, the administratively-prohibited message, which has a
value of 13, is returned.
If any other message type is specified, that message is returned.
family inet
NOTE:
Rejected packets can be sampled or logged if you configure the sample or syslog
action.
This action is supported on ingress only.
The message-type option can have one of the following values: address-unreachable,
administratively-prohibited, bad-host-tos, bad-network-tos, beyond-scope,
fragmentation-needed, host-prohibited, host-unknown, host-unreachable,
network-prohibited, network-unknown, network-unreachable, no-route,
port-unreachable, precedence-cutoff, precedence-violation, protocol-unreachable,
source-host-isolated, source-route-failed, or tcp-reset.
routing-instance
routing-instance-name
Direct the packet to the specified routing instance.
Related
Documentation
family inet
on page 81
87
Standard Firewall Filter Nonterminating Actions on ACX Series Routers

Standard stateless firewall filters support different sets of nonterminating actions for
each protocol family.
NOTE: ACX Series routers do not support the next term action.
Table 18 on page 88 describes the nonterminating actions you can configure for a standard
firewall filter term.
Table 18: Nonterminating Actions for Standard Firewall Filters on ACX Series Routers
Nonterminating Action
Description
Protocol Families
count counter-name
Count the packet in the named

counter.
family any
family inet
family mpls
family ccc
Classify the packet based on

the specified forwarding class:
family inet
family any
assured-forwarding
family mpls
best-effort
family ccc
expedited-forwarding
network-control
forwarding-class class-name
NOTE: This action is

supported on ingress only.
log
Log the packet header

information in a buffer within
the Packet Forwarding Engine.
You can access this
information by issuing the
show firewall log command at
the command-line interface
(CLI).
family inet

88
Routers (continued)
Description
Protocol Families
loss-priority (high | medium-high | low)
Set the packet loss priority

(PLP) level.
family any
family inet
You cannot also configure the
family mpls
three-color-policer
family ccc
family any
family inet
family mpls
family ccc
nonterminating action for the

same firewall filter term. These
two nonterminating actions
are mutually exclusive.
You must include the tri-color
statement at the [edit
class-of-service] hierarchy
level to commit a PLP
configuration with any of the
four levels specified. If the
tri-color statement is not
enabled, you can configure
only the high and low levels.
This applies to all protocol
families.
For information about the
tri-color statement and for
information about using
behavior aggregate (BA)
classifiers to set the PLP level
of incoming packets, see the
Junos OS Class of Service
Configuration Guide.
policer policer-name
port-mirror
Name of policer to use to

rate-limit traffic.
Port-mirror the packet based

on the specified family.
family inet

syslog
Log the packet to the system

log file.
family inet

89
Routers (continued)
Description
Protocol Families
three-color-policer (single-rate |
two-rate) policer-name
Police the packet using the

specified single-rate or
two-rate three-color policer.
family any
family inet
family mpls
You cannot also configure the

loss-priority action for the
same firewall filter term. These
two actions are mutually
exclusive.
family ccc
Related
Documentation
on page 81
Filter-Based Forwarding for Routing Instances

For IPv4 traffic only, you can use stateless firewall filters in routing instances to control
how packets travel in a network. This is called filter-based forwarding.
You can define a firewall filtering term that directs matching packets to a specified routing
instance. This type of filtering can be configured to route specific types of traffic through
a firewall or other security device before the traffic continues on its path. To configure a
stateless firewall filter to direct traffic to a routing instance, configure a term with the
routing-instance routing-instance-name terminating action at the [edit firewall family inet]
hierarchy level to specify the routing instance to which matching packets will be forwarded.
You can apply a forwarding table filter to a routing instance of type forwarding and also
to the default routing instance inet.0. To configure the filter to direct traffic to the master
routing instance, use the routing-instance default statement at the [edit firewall family
inet] hierarchy level.
The following limitations apply to filter-based forwarding table configured on routing
instances:
90
You cannot configure any of the following actions in a firewall filtering term when the
filtering term contains the routing-instance routing-instance-name terminating action:
count counter-name
discard
forwarding-class class-name
log
loss-priority (high | medium-high | low)
policer policer-name
port-mirror
reject message-type
syslog
three-color-policer (single-rate | two-rate) policer-name
You cannot configure the fragment-flags number match condition in the filter term.
You cannot attach a filter that is either default or physical interface-specific.
You cannot attach a filter to the egress direction of routing instances.
Although you can configure forwarding of packets from one VRF to another VRF, you
cannot configure forwarding from a VRF to the global routing instance.
You can configure a maximum of 256 firewall filter terms for filter-based forwarding.
The maximum number of routing instances supported is 64, which is the same as the
maximum number of virtual routers supported. Forwarding packets to the global table
(default VRF) is not supported for filter-based forwarding.
Related
Documentation
Example: Configuring Filter-Based Forwarding on the Source Address
Statement Hierarchy for Configuring FBF for IPv4 Traffic on ACX Series Routers
Forwarding Table Filters for Routing Instances on ACX Series Routers

Forwarding table filter is a mechanism by which all the packets forwarded by a certain
forwarding table are subjected to filtering and if a packet matches the filter condition,
the configured action is applied on the packet. You can use the forwarding table filter
mechanism to apply a filter on all interfaces associated with a single routing instance
with a simple configuration. You can apply a forwarding table filter to a routing instance
of type forwarding and also to the default routing instance inet.0. To configure a
forwarding table filter, include the filter filter-name statement at the [edit firewall family
inet] hierarchy level.
The following limitations apply to forwarding table filters configured on routing instances:
Related
Documentation
You cannot attach the same filter to more than one routing instance.
You cannot attach the same filter at both the [edit interfaces interface-name family
inet filter input filter-name] and [edit routing-instances instance-name forwarding-options
family inet filter input filter-name] hierarchy level.
You cannot attach a filter that is either interface-specific or a physical interface filter.
You cannot attach a filter to the egress direction of routing instances.
Configuring Forwarding Table Filters
91
92
CHAPTER 6
Interfaces and Chassis
BERT Support on CT1 and CE1 Interfaces on page 93
Channelized OC3/STM1 (Multi-Rate) Circuit Emulation MIC with SFP

Overview on page 94
Checklist for Monitoring Fast Ethernet and Gigabit Ethernet Interfaces on page 94
Checklist for Monitoring T1 Interfaces on page 95
Configuring the Media MTU on ACX Series Routers on page 96
Gigabit Ethernet Autonegotiation Overview on page 98
Understanding Encapsulation on an Interface on page 102
SAToP Emulation on T1 and E1 Interfaces Overview on page 102
User-Defined Alarm Relay Overview on page 103
Configuring Chassis Alarm Relays on page 104
Configuring Chassis Alarm Input on page 105
Configuring Chassis Alarm Output on page 106
BERT Support on CT1 and CE1 Interfaces

For ACX Series routers, BERT is supported on ct1 and ce1 interfaces. The following BERT
algorithms are supported:
all-ones-repeating
all-zeros-repeating
alternating-double-ones-zeros
alternating-ones-zeros
repeating-1-in-4
repeating-1-in-8
repeating-3-in-24
pseudo-2e11-o152
93
pseudo-2e15-o151
pseudo-2e20-o151
NOTE: User-defined BERT patterns are not supported.
Related
Documentation
Configuring E1 BERT Properties on page 229
Configuring T1 BERT Properties on page 231
Channelized OC3/STM1 (Multi-Rate) Circuit Emulation MIC with SFP Overview

The Channelized OC3/STM1 (Multi-Rate) Circuit Emulation MIC with SFP is a channelized
circuit emulation MIC with rate-selectability. Its port speed can be specified as
COC3-CSTM1 or COC12-CSTM4. The default port speed is COC3-CSTM1.
Table 19: Platform Support for Channelized OC3/STM1 (Multi-Rate) Circuit Emulation MIC with
SFP
Interface Name
Model Number
Platform Supported
Junos OS Release
Channelized OC3/STM1
(Multi-Rate) Circuit
Emulation MIC with SFP
MIC-3D-4COC3-1COC12-CE
MX Series routers
12.2R1
ACX-MIC-4COC3-1COC12CE
ACX4000 router
12.3X51
The following features are supported on this MIC:
Related
Documentation
Per-MIC SONET/SDH framing
Internal and loop clocking
Structure-Agnostic TDM over Packet (SAToP)
Pseudowire Emulation Edge to Edge (PWE3) control word for use over an MPLS
packet-switched network (PSN)
Configuring SAToP on Channelized OC3/STM1 (Multi-Rate) Circuit Emulation MIC with

SFP
Checklist for Monitoring Fast Ethernet and Gigabit Ethernet Interfaces

Purpose
Action
94
To monitor Fast Ethernet and Gigabit Ethernet interfaces and begin the process of isolating
interface problems when they occur.
Table 20 on page 95 provides links and commands for monitoring Fast Ethernet and
Gigabit Ethernet interfaces.
Chapter 6: Interfaces and Chassis
Table 20: Checklist for Monitoring Fast Ethernet and Gigabit Ethernet
Interfaces
Tasks
Command or Action
Monitor Fast Ethernet and Gigabit Ethernet Interfaces

1.
Display the Status of Fast Ethernet Interfaces
show interfaces terse (fe* | ge*)
2. Display the Status of a Specific Fast Ethernet or Gigabit

Ethernet Interface
show interfaces (fe-fpc/pic/port | ge-fpc/pic/port)
3. Display Extensive Status Information for a Specific Fast

Ethernet or Gigabit Ethernet Interface
show interfaces (fe-fpc/pic/port | ge-fpc/pic/port) extensive
4. Monitor Statistics for a Fast Ethernet or Gigabit Ethernet

Interface
monitor interface (fe-fpc/pic/port | ge-fpc/pic/port)
5. Fiber-Optic Ethernet Interface Specifications
Meaning
Related
Documentation
You can use the above described commands to monitor and to display the configurations
for Fast Ethernet and Gigabit Ethernet interfaces.
Display the Status of Gigabit Ethernet Interfaces
Display the Status of Fast Ethernet Interfaces
Checklist for Monitoring T1 Interfaces

Purpose
Action
To monitor T1 interfaces and beginning the process of isolating T1 interface problems

when they occur.
Table 21 on page 95 provides the links and commands for monitoring T1 interfaces.
Table 21: Checklist for Monitoring T1 Interfaces

Tasks
Command or Action
Monitor T1 Interfaces
1.
Display the Status of T1 Interfaces
show interfaces terse t1*
2. Display the Status of a Specific T1 Interface
show interfaces t1-fpc/pic/port
3. Display Extensive Status Information for a Specific T1

Interface
show interfaces t1-fpc/pic/port extensive
4. Monitor Statistics for a T1 Interface
monitor interface t1-fpc/pic/port
95
Configuring the Media MTU on ACX Series Routers
Media MTU Overview on page 96
How to Configure the Media MTU on page 97
Encapsulation Overhead by Encapsulation Type on page 97
Media MTU Sizes by Interface Type for ACX Series Routers on page 98
Media MTU Overview

The default media MTU size used on a physical interface depends on the encapsulation
used on that interface. In some cases, the default IP Protocol MTU depends on whether
the protocol used is IP version 4 (IPv4) or International Organization for Standardization
(ISO).
The default media MTU is calculated as follows:
Default media MTU = Default IP MTU + encapsulation overhead
When you are configuring point-to-point connections, the MTU sizes on both sides of the
connections must be the same. Also, when you are configuring point-to-multipoint
connections, all interfaces in the subnet must use the same MTU size. For details about
encapsulation overhead, see Encapsulation Overhead by Encapsulation Type on page 97.
NOTE: The actual frames transmitted also contain cyclic redundancy check
(CRC) bits, which are not part of the media MTU. For example, the media
MTU for a Gigabit Ethernet Version 2 interface is specified as 1514 bytes, but
the largest possible frame size is actually 1518 bytes; you need to consider
the extra bits in calculations of MTUs for interoperability.
The physical MTU for Ethernet interfaces does not include the 4-byte frame
check sequence (FCS) field of the Ethernet frame.
If you do not configure an MPLS MTU, the Junos OS derives the MPLS MTU
from the physical interface MTU. From this value, the software subtracts the
encapsulation-specific overhead and space for the maximum number of
labels that might be pushed in the Packet Forwarding Engine. Currently, the
software provides for three labels of four bytes each, for a total of 12 bytes.
In other words, the formula used to determine the MPLS MTU is the following:
MPLS MTU = physical interface MTU encapsulation overhead 12
If you configure an MTU value by including the mtu statement at the [edit
interfaces interface-name unit logical-unit-number family mpls] hierarchy level,
the configured value is used.
96
How to Configure the Media MTU

To modify the default media MTU size for a physical interface, include the mtu statement
at the [edit interfaces interface-name] hierarchy level:
mtu bytes;
If you change the size of the media MTU, you must ensure that the size is equal to or
greater than the sum of the protocol MTU and the encapsulation overhead.
NOTE: Changing the media MTU or protocol MTU causes an interface to be

deleted and added again.
You configure the protocol MTU by including the mtu statement at the following hierarchy
levels:
[edit interfaces interface-name unit logical-unit-number family family]
Encapsulation Overhead by Encapsulation Type

Table 22: Encapsulation Overhead by Encapsulation Type
Interface Encapsulation
Encapsulation Overhead (Bytes)
802.1Q/Ethernet 802.3
21
802.1Q/Ethernet Subnetwork Access Protocol (SNAP)
26
802.1Q/Ethernet version 2
18
ATM Cell Relay
ATM permanent virtual connection (PVC)
12
Cisco HDLC
Ethernet 802.3
17
Ethernet circuit cross-connect (CCC) and virtual private

LAN service (VPLS)
Ethernet over ATM
32
Ethernet SNAP
22
Ethernet translational cross-connect (TCC)
18
Ethernet version 2
14
97
Table 22: Encapsulation Overhead by Encapsulation Type (continued)

Interface Encapsulation
Encapsulation Overhead (Bytes)
Extended virtual local area network (VLAN) CCC and

VPLS
Extended VLAN TCC
22
Frame Relay
PPP
VLAN CCC
VLAN VPLS
VLAN TCC
22
Media MTU Sizes by Interface Type for ACX Series Routers

Table 23: Media MTU Sizes by Interface Type for ACX Series Routers
Related
Documentation
Interface Type
Default Media
MTU (Bytes)
Maximum MTU
(Bytes)
Default IP Protocol
MTU (Bytes)
Gigabit Ethernet
1514
9192
1500 (IPv4),
1497 (ISO)
10-Gigabit Ethernet
1514
9192
1500 (IPv4),
1497 (ISO)
Configuring Interface Encapsulation on Physical Interfaces
Setting the Protocol MTU
Gigabit Ethernet Autonegotiation Overview

Autonegotiation is enabled by default on all Gigabit Ethernet and Tri-Rate Ethernet
copper interfaces. However, you can explicitly enable autonegotiation to configure remote
fault options manually.
98
NOTE:
Related
Documentation
For Gigabit Ethernet interfaces installed in J4350 and J6350 Services

Routers, when you manually configure either the link mode or speed
settings, the system ignores the configuration and generates a system log
message. When autonegotiation is enabled and you specify the link mode
and speed, the link autonegotiates with the manually configured settings.
When autonegotiation is disabled and you configure both the link mode
and speed, the link operates with the manually configured settings. If you
disable autonegotiation and do not manually configure the link mode and
speed, the link operates at 1000 Mbps full duplex.
When you configure the Tri-Rate Ethernet copper interface to operate at

1 Gbps, autonegotiation must be enabled.
On ACX Series Universal Access Routers, when the autonegotiation is

disabled, the speed has to be explicitly configured to 10100 Mbps.
On T4000 routers, the auto-negotiation command is ignored for interfaces

other than Gigabit Ethernet.
Configuring Gigabit Ethernet Autonegotiation
Understanding Interfaces on ACX Series Universal Access Routers

The ACX Series routers support time-division multiplexing (TDM) T1 and E1 interfaces
and Ethernet (10GbE, 100GbE, 1000GbE copper, and 1GbE and10GbE fiber) interfaces
to support both the legacy and evolution needs of the mobile network. Support for Power
over Ethernet (PoE+) at 65 watts per port mitigates the need for additional electrical
cabling for microwaves or other access interfaces.
The ACX Series routers support the following:
TDM T1 and E1 ports:
The ACX1000 router contains eight T1 or E1 ports.
The ACX2000 router contains 16 T1 or E1 ports.
Inverse Multiplexing for ATM (IMA)
Gigabit Ethernet ports:
The ACX1000 router contains eight Gigabit Ethernet ports. The ACX1000 router also
supports either four RJ45 (Cu) ports or installation of four Gigabit Ethernet small
form-factor pluggable (SFP) transceivers.
The ACX2000 router contains 16 Gigabit Ethernet ports and two PoE ports. The
ACX2000 router also supports installation of two Gigabit Ethernet SFP transceivers
and two 10-Gigabit Ethernet SFP+ transceivers.
99
T1 and E1 Time-Division Multiplexing (TDM) Interfaces

On the ACX Series routers, existing Junos OS TDM features are supported without changes
to statements or functionality. The following key TDM features for T1 (ct1) interfaces and
E1 (ce1) interfaces are supported:
T1 and E1 channelization
T1 and E1 encapsulation
Alarms, defects, and statistics
External and internal loopback
TDM class of service (CoS)
T1 and E1 mode selection is at the PIC level. To set the T1 or E1 mode at the PIC level,
include the framing statement with the t1 or e1 option at the [chassis fpc slot-number pic
slot-number] hierarchy level. All ports can be T1 or E1. Mixing T1s and E1s is not supported.
T1 or E1 BITS Interface
(ACX2000)
The ACX2000 router has a T1 or E1 building-integrated timing supply (BITS) interface
that you can connect to an external clock. After you connect the interface to the external
clock, you can configure the BITS interface so that the BITS interface becomes a candidate
source for chassis synchronization to the external clock. The frequency of the BITS
interface depends on the Synchronous Ethernet equipment slave clock (EEC) selected
with the network-option statement at the [edit chassis synchronization] hierarchy level.
NOTE: The ACX1000 router does not support the BITS interface.
Inverse Multiplexing for ATM (IMA)

Defined by the ATM Forum, IMA specification version 1.1 is a standardized technology
used to transport ATM traffic over a bundle of T1 and E1 interfaces, also known as an IMA
group. Up to eight links per bundle and 16 bundles per PIC are supported. The following
key IMA features are supported:
IMA Layer 2 encapsulation
ATM CoS
ATM policing and shaping
Denied packets counter in the output for the show interfaces at-fpc/pic/port extensive
command
Gigabit Ethernet interfaces

On the ACX Series routers, existing Junos OS Ethernet features are supported without
changes to statements or functionality. The following key features are supported:
100
Media type specification (ACX1000 router with Gigabit Ethernet SFP and RJ45
interfaces)
Autonegotiation for RJ45 Gigabit Ethernet interfaces
Event handling of SFP insertion and removal
Explicit disabling of the physical interface
Flow control
NOTE: The ACX Series router does not support flow control based on
PAUSE frames.
Loopback
Loss of signal (LOS) alarm
Media access control (MAC) layer features
Maximum transmission unit (MTU)
Remote fault notification for 10-Gigabit Ethernet interfaces
Statistics collection and handling
Power over Ethernet (PoE) (ACX2000 router)
High power mode
The Gigabit Ethernet ports on the router have the capacity to work as a 1 or 10-Gigabit
Ethernet interface, depending on the type of small form-factor pluggable (SFP)
transceiver inserted. When you insert an SFP+ transceiver, the interface works at the
10-Gigabit speed. When you insert an SFP transceiver, the interface works at the 1-Gigabit
speed. Configuration is not required because the speed is determined automatically
based on the type of inserted SFP transceiver. The dual-speed interface is automatically
created with the xe prefix, for example, xe-4/0/0.
The same configuration statements are used for both speeds and CoS parameters are
scaled as a percentage of the port speed. To configure a dual-speed Gigabit Ethernet
interface, include the interface xe-fpc/pic/port statement at the [edit interfaces] hierarchy
level. To display the interface speed and other details, issue the show interfaces command.
NOTE: You need to use industrial grade of SFP below 0dC for ACX 1100 and
ACX 2100 boards.
Related
Documentation
Interface Names for ACX Series Universal Access Routers
101
Understanding Encapsulation on an Interface

Encapsulation is the process by which a lower-level protocol accepts a message from a
higher-level protocol and places it in the data portion of the lower-level frame. As a result,
datagrams transmitted through a physical network have a sequence of headers: the first
header for the physical network (or Data Link Layer) protocol, the second header for the
Network Layer protocol (for example, IP), the third header for the Transport Layer protocol,
and so on.
The following topics are general topics about the way encapsulation works on interfaces
and the Junos OS. For the ACX Series routers, keep the following points in mind when
referring to these topics:
Related
Documentation
The [edit logical-systems logical-system-name interfaces interface-name unit

logical-unit-number] hierarchy level is not supported on the ACX Series routers.
Not all encapsulation types or features are supported on the ACX Series routers, refer
to the documentation about the specific statement or feature for support details.
Configuring Interface Encapsulation on Logical Interfaces
Configuring Interface Encapsulation on Physical Interfaces
encapsulation (Physical Interface)
encapsulation (Logical Interface)
SAToP Emulation on T1 and E1 Interfaces Overview

Structure-Agnostic time-division multiplexing (TDM) over Packet (SAToP), as defined
in RFC 4553, Structure-Agnostic TDM over Packet (SAToP) is supported on the ACX Series
Universal Access routers with built-in T1 and E1 interfaces. SAToP is used for pseudowire
encapsulation for TDM bits (T1, E1). The encapsulation disregards any structure imposed
on the T1 and E1 streams, in particular the structure imposed by standard TDM framing.
SAToP is used over packet-switched networks, where the provider edge (PE) routers do
not need to interpret TDM data or participate in the TDM signaling.
Figure 9 on page 102 shows a packet-switched network (PSN) in which two PE routers
(PE1 and PE2) provide one or more pseudowires to customer edge (CE) routers (CE1 and
CE2), establishing a PSN tunnel to provide a data path for the pseudowire.
Figure 9: Pseudowire Encapsulation with SAToP

Attachment Circuit
g016956
Emulated Service
Attachment Circuit
PSN tunnel
Pseudowire 1
CE1
PE1
Native service
102
Pseudowire 2
CE2
PE2
Native service
Pseudowire traffic is invisible to the core network, and the core network is transparent
to the CEs. Native data units (bits, cells, or packets) arrive via the attachment circuit, are
encapsulated in a pseudowire protocol data unit (PDU), and carried across the underlying
network via the PSN tunnel. The PEs perform the necessary encapsulation and the
decapsulation of the pseudowire PDUs and handle any other function required by the
pseudowire service, such as sequencing or timing.
Related
Documentation
Configuring SAToP Emulation on Channelized T1 and E1 Interfaces on page 217
User-Defined Alarm Relay Overview

The ACX Series router alarm contact portlabeled ALARM on the front panelallows
you to manage sensors and external devices connected to the router in remote unstaffed
facilities.
Alarm Contact Port on page 103
Alarm Input on page 103
Alarm Output on page 103
Alarm Contact Port

The ACX Series router alarm contact port is a 15-pin D-type dry contact connector for
alarms. The alarm contact port is used to generate LED alarms on the router and to turn
external devices on or off. You can connect up to four input alarms and two output alarms.
The alarm setting is open or closed.
Alarm Input
Alarm input provides dry contacts to connect to security sensors such as door or window
monitors. The alarm inputopen or closedis sensed and reported to the management
software. You can configure up to four alarm input relay ports (0 through 3) to operate
as normally open or normally closed, and to trigger a red alarm condition or a yellow
alarm condition or to ignore alarm conditions.
Alarm Output
Alarm output provides dry contacts to connect to external equipment, such as an audible
or visual alarm that switches on or offfor example, a bell or a light. The four alarm output
relay ports0 through 3are set up as follows:
Ports 0 and 1These ports can be configured to trigger an alarm when the system
temperature goes to the red alarm status and when an alarm input port is triggered.
Ports 2 and 3These ports are not configured. They are used to indicate system major
and minor alarms and are normally open. When a condition triggers an alarm, an alarm
message is displayed.
To view the alarm input and output relay information, issue the show chassis craft-interface
command from the Junos OS command line interface.
103
Related
Documentation
Alarm Contact Port on the ACX2000 Router (Hardware topic)
Configuring Chassis Alarm Relays on page 104
Configuring Chassis Alarm Input on page 105
Configuring Chassis Alarm Output on page 106
relay (Chassis Alarm)
Configuring Chassis Alarm Relays

On ACX Series routers, you can configure alarm relays that can trigger alarms and turn
external devices on or off. For example, if the router heats up to more than the critical
temperature, the output port is activated and a device connected to the output portsuch
as a fanis turned on.
To configure conditions that trigger alarms, include the relay statement with the input
and output options at the [edit chassis alarm] hierarchy level.
[edit chassis alarm]
relay
input {
port port-number {
mode (close | open);
trigger (ignore | red | yellow);
}
}
output{
port port-number {
input-relay input-relay;
mode (close | open);
temperature;
}
}
The following output shows an example configuration of a chassis relay alarm:

[edit chassis alarm]
user@host# show
relay {
input {
port 1 {
mode close;
trigger red;
}
}
output {
port 0 {
temperature;
}
}
}
Related
Documentation
104
input
output
show chassis craft-interface on page 377
show chassis alarms on page 364
Configuring Chassis Alarm Input

facilities. You can configure up to four alarm input ports (0 through 3) to operate as
normally open or normally closed, and to trigger a red alarm condition or a yellow alarm
condition or to ignore alarm conditions.
To configure an input alarm:
1.
Configure the input port:

[edit chassis alarm relay input port port-number]
For example, to configure input port zero (0):

user@host# edit chassis alarm relay input port 0
2. Configure the mode in which the input alarm is not active:
[edit chassis alarm relay input port port-number mode (close | open)]
For example, to configure open mode:

[edit chassis alarm relay input port 0]
user@host# set mode open
3. Configure the trigger to set off the alarm:
[edit chassis alarm relay input port port-number trigger (ignore | red | yellow)]
For example, to set off the yellow alarm:

user@host# set trigger yellow
4. Verify the configuration with the show command:
user@host# show
mode open;
trigger yellow;
5. Commit the configuration with the commit command.
To view the alarm input relay information, issue the show chassis alarms or show chassis
craft-interface commands from the Junos OS command line interface.
Related
Documentation
output
105
Configuring Chassis Alarm Output

facilities. You can configure up to two alarm output relay ports (0 and 1) to operate as
normally open or normally closed, and to trigger an alarm when the system temperature
goes to the red alarm status and when an alarm input port is triggered.
NOTE: Ports 2 and 3 are not configured. They are used to indicate system
major and minor alarms and are normally open. When a condition triggers
an alarm, an alarm message is displayed, and the corresponding LED turns
on.
To configure an output alarm:

1.
Configure the output port:

[edit chassis alarm relay output port port-number]
For example, to configure output port zero (0):

user@host# edit chassis alarm relay output port 0
2. Configure the trigger to set off the alarm:
[edit chassis alarm relay output port port-number (input-relay | mode | temperature)]
For example, to set off the alarm when the system temperature goes into the red
status:
[edit chassis alarm relay output port 0]
user@host# set temperature
3. Verify the configuration with the show command:
[edit chassis alarm relay output port 0]
regress@fortius-m3# show
temperature;
4. Commit the configuration with the commit command.
To view the alarm output relay information, issue the show chassis alarms or show chassis
craft-interface command from the Junos OS command line interface.
Related
Documentation
106
input
CHAPTER 7
Layer 2 and Layer 3
Configuring Interfaces for Layer 2 Circuits Overview on page 107
Configuring the Address for the Neighbor of the Layer 2 Circuit on page 108
Configuring the Neighbor Interface for the Layer 2 Circuit on page 108
Configuring a Community for the Layer 2 Circuit on page 109
Configuring the Control Word for Layer 2 Circuits on page 109
Configuring the Encapsulation Type for the Layer 2 Circuit Neighbor Interface on page 110
Configuring the MTU Advertised for a Layer 2 Circuit on page 111
Configuring the Protect Interface on page 111
Configuring the Virtual Circuit ID on page 112
Configuring the Interface Encapsulation Type for Layer 2 Circuits on page 112
Configuring Layer 2 Circuits over Both RSVP and LDP LSPs on page 113
Enabling the Layer 2 Circuit When the MTU Does Not Match on page 114
Enabling the Layer 2 Circuit When the Encapsulation Does Not Match on page 114
Configuring Interfaces for Layer 2 Circuits Overview

A Layer 2 circuit or pseudowire is a point-to-point Layer 2 connection transported by
means of MPLS or another tunneling technology on the service providers network. Layer
2 circuits are also called pseudowires. A Layer 2 circuit is similar to a circuit cross-connect
(CCC), except that multiple Layer 2 circuits can be transported over a single
label-switched path (LSP) tunnel between two provider edge (PE) routers. In contrast,
each CCC requires a dedicated LSP.
The Junos OS implementation of Layer 2 circuits supports only the remote form of a
Layer 2 circuit; that is, a connection from a local customer edge (CE) router to a remote
CE router.
Related
Documentation
Configuring the Address for the Neighbor of the Layer 2 Circuit on page 108
107
Configuring the Address for the Neighbor of the Layer 2 Circuit

All the Layer 2 circuits using a particular remote PE router designated for remote CE
routers are listed under the neighbor statement (neighbor designates the PE router).
Each neighbor is identified by its IP address and is usually the end-point destination for
the label-switched path (LSP) tunnel transporting the Layer 2 circuit.
To configure a PE router as a neighbor for a Layer 2 circuit, specify the neighbor address
using the neighbor statement:
neighbor address {
...
}
You can include this statement at the following hierarchy levels:
Related
Documentation
[edit protocols l2circuit]
Configuring the Neighbor Interface for the Layer 2 Circuit

Each Layer 2 circuit is represented by the logical interface connecting the local provider
edge (PE) router to the local customer edge (CE) router. This interface is tied to the
Layer 2 circuit neighbor configured in Configuring the Address for the Neighbor of the
Layer 2 Circuit on page 108.
To configure the interface for a Layer 2 circuit neighbor, include the interface statement:
interface interface-name {
bandwidth (bandwidth | ctnumber bandwidth);
community community-name;
(control-word | no-control-word);
description text;
encapsulation-type type;
ignore-encapsulation-mismatch;
ignore-mtu-mismatch;
mtu mtu-number;
no-revert;
protect-interface interface-name;
pseudowire-status-tlv;
psn-tunnel-endpoint address;
virtual-circuit-id identifier;
}
108
Chapter 7: Layer 2 and Layer 3
Related
Documentation
[edit protocols l2circuit neighbor address]
Configuring a Community for the Layer 2 Circuit on page 109
Configuring the Control Word for Layer 2 Circuits on page 109
Configuring the Protect Interface on page 111
Configuring the Virtual Circuit ID on page 112
Configuring a Community for the Layer 2 Circuit

To configure a community for a Layer 2 circuit, include the community statement:
community community-name;
Related
Documentation
[edit protocols l2circuit neighbor address interface interface-name]
Configuring Policies for Layer 2 Circuits
Configuring the Control Word for Layer 2 Circuits

To emulate the virtual circuit (VC) encapsulation for Layer 2 circuits, a 4-byte control
word is added between the Layer 2 protocol data unit (PDU) being transported and the
VC label that is used for demultiplexing. For most protocols, a null control word consisting
of all zeroes is sent between Layer 2 circuit neighbors.
However, individual bits are available in a control word that can carry Layer 2 protocol
control information. The control information is mapped into the control word, which
allows the header of a Layer 2 protocol to be stripped from the frame. The remaining
data and control word can be sent over the Layer 2 circuit, and the frame can be
reassembled with the proper control information at the egress point of the circuit.
The following Layer 2 protocols map Layer 2 control information into special bit fields in
the control word:
Frame RelayThe control word supports the transport of discard eligible (DE), forward
explicit congestion notification (FECN), and backward explicit congestion notification
(BECN) information.
NOTE: Frame Relay is not supported on the ACX Series routers.
109
ATM AAL5 modeThe control word supports the transport of sequence number
processing, ATM cell loss priority (CLP), and explicit forward congestion indication
(EFCI) information. When you configure an AAL5 mode Layer 2 circuit, the control
information is carried by default and no additional configuration is needed.
ATM cell-relay modeThe control word supports sequence number processing only.
When you configure a cell-relay mode Layer 2 circuit, the sequence number information
is carried by default and no additional configuration is needed.
The Junos OS implementation of sequence number processing for ATM cell-relay mode
and AAL5 mode is not the same as that described in Sec. 3.1.2 of the IETF draft
Encapsulation Methods for Transport of Layer 2 Frames Over IP and MPLS Networks. The
differences are as follows:
A packet with a sequence number of 0 is considered as out of sequence.
A packet that does not have the next incremental sequence number is considered out
of sequence.
When out-of-sequence packets arrive, the sequence number in the Layer 2 circuit
control word increments by one and becomes the expected sequence number for the
neighbor.
The Junos OS can typically determine whether a neighboring router supports the control
word. However, if you want to explicitly disable its use on a specific interface, include the
no-control-word statement in the configuration.
Related
Documentation
Configuring the Encapsulation Type for the Layer 2 Circuit Neighbor Interface
You can specify the Layer 2 circuit encapsulation type for the interface receiving traffic
from a Layer 2 circuit neighbor. The encapsulation type is carried in the LDP-signaling
messages exchanged between Layer 2 circuit neighbors when pseudowires are created.
The encapsulation type you configure for each Layer 2 circuit neighbor varies depending
on the type of networking equipment or the type of Layer 2 protocol you have deployed
in your network. If you do not specify an encapsulation type for the Layer 2 circuit, the
encapsulation of the CE device interface is used by default.
Specify the encapsulation type for the Layer 2 circuit neighbor interface by including the
encapsulation-type statement:
encapsulation-type (atm-aal5 | atm-cell | atm-cell-port-mode | atm-cell-vc-mode |
atm-cell-vp-mode | cesop | ethernet | ethernet-vlan | interworking | satop-e1 | satop-e3
| satop-t1 | satop-t3);
You can include this statement at the [edit protocols l2circuit neighbor address interface
interface-name] hierarchy levels:
Related
Documentation
110
Enabling the Layer 2 Circuit When the Encapsulation Does Not Match on page 114
Configuring the MTU Advertised for a Layer 2 Circuit

By default, the MTU used to advertise a Layer 2 circuit is determined by taking the interface
MTU for the associated physical interface and subtracting the encapsulation overhead
for sending IP packets based on the encapsulation.
However, encapsulations that support multiple logical interfaces (and multiple Layer 2
circuits) rely on the same interface MTU (since they are all associated with the same
physical interface). This can prove to be a limitation for VLAN Layer 2 circuits using the
same Ethernet interface or for Layer 2 circuit DLCIs using the same Frame Relay interface.
This can also affect multivendor environments. For example, if you have three PE devices
supplied by different vendors and one of the devices only supports an MTU of 1500, even
if the other devices support larger MTUs you must to configure the MTU as 1500 (the
smallest MTU of the three PE devices).
You can explicitly configure which MTU is advertised for a Layer 2 circuit, even if the
Layer 2 circuit is sharing a physical interface with other Layer 2 circuits. When you explicitly
configure an MTU for a Layer 2 circuit, be aware of the following:
An explicitly configured MTU is signaled to the remote PE device. The configured MTU
is also compared to the MTU received from the remote PE device. If there is a conflict,
the Layer 2 circuit is taken down.
If you configure an MTU for an ATM cell relay interface on an ATM II PIC, the configured
MTU is used to compute the cell bundle size advertised for that Layer 2 circuit, instead
of the default interface MTU.
A configured MTU is used only in the control plane. It is not enforced in the data plane.
You need to ensure that the CE device for a given Layer 2 circuit uses the correct MTU
for data transmission.
To configure the MTU for a Layer 2 circuit, include the mtu statement at the [edit protocols
l2circuit neighbor address interface interface-name] hierarchy level.
mtu mtu-number;
Related
Documentation
Configure the Layer 2 Circuit on page 223
Configuring the Protect Interface

You can configure a protect interface for the logical interface linking a virtual circuit to
its destination, whether the destination is remote or local. A protect interface provides
a backup for the protected interface in case of failure. Network traffic uses the primary
111
interface only so long as the primary interface functions. If the primary interface fails,
traffic is switched to the protect interface. The protect interface is optional.
To configure the protect interface, include the protect-interface statement:
protect-interface interface-name;
For a list of hierarchy levels at which you can include this statement, see the statement
summary section for this statement.
Related
Documentation
Example: Configuring Layer 2 Circuit Protect Interfaces
Configuring the Virtual Circuit ID

You configure a virtual circuit ID on each interface. Each virtual circuit ID uniquely identifies
the Layer 2 circuit among all the Layer 2 circuits to a specific neighbor. The key to
identifying a particular Layer 2 circuit on a PE router is the neighbor address and the virtual
circuit ID. An LDP-FEC-to-label binding is associated with a Layer 2 circuit based on the
virtual circuit ID in the FEC and the neighbor that sent this binding. The LDP-FEC-to-label
binding enables the dissemination of the VPN label used for sending traffic on that Layer 2
circuit to the remote CE device.
You also configure a virtual circuit ID for each redundant pseudowire. A redundant
pseudowire is identified by the backup neighbor address and the virtual circuit ID.
To configure the virtual circuit ID, include the virtual-circuit-id statement:
virtual-circuit-id identifier;
Related
Documentation
Configuring Pseudowire Redundancy on the PE Router on page 123
Configuring the Interface Encapsulation Type for Layer 2 Circuits

The Layer 2 encapsulation type is carried in the LDP forwarding equivalence class (FEC).
You can configure either circuit cross-connect (CCC) or translational cross-connect
(TCC) encapsulation types for Layer 2 circuits. For more information, see the Junos OS
MPLS Applications Configuration Guide and Router Interfaces.
To configure the interface encapsulation for a Layer 2 circuit, include the encapsulation
statement:
encapsulation encapsulation;
112
Related
Documentation
Configuring Layer 2 Circuits over Both RSVP and LDP LSPs

You can configure two Layer 2 circuits between the same two routers, and have one
Layer 2 circuit traverse an RSVP LSP and the other traverse an LDP LSP. To accomplish
this, you need to configure two loopback addresses on the local router. You configure
one of the loopback address for the Layer 2 circuit traversing the RSVP LSP. You configure
the other loopback address to handle the Layer 2 circuit traversing the LDP LSP.
You also need to configure a packet switched network (PSN) tunnel endpoint for one of
the Layer 2 circuits. It can be either the Layer 2 circuit traversing the RSVP LSP or the one
traversing the LDP LSP. The PSN tunnel endpoint address is the destination address for
the LSP on the remote router.
To configure the address for the PSN tunnel endpoint, include the psn-tunnel-endpoint
statement:
[edit protocols l2circuit neighbor address interface interface-name]
By default, the PSN tunnel endpoint for a Layer 2 circuit is identical to the neighbor
address, which is also the same as the LDP neighbor address.
The tunnel endpoints on the remote router do not need to be loopback addresses.
The following example illustrates how you might configure a PSN tunnel endpoint:
neighbor 10.255.0.6 {
interface t1-0/2/2.0 {
psn-tunnel-endpoint 20.20.20.20;
virtual-circuit-id 1;
}
}
}
The Layer 2 circuit configured for the t1-0/2/2.0 interface resolves in the inet3 routing
table to 20.20.20.20. This could be either an RSVP route or a static route with an LSP
next hop.
113
Related
Documentation
Configuring Logical Units on the Loopback Interface for Routing Instances in Layer 3
VPNs
Enabling the Layer 2 Circuit When the MTU Does Not Match
You can configure the Junos OS to allow a Layer 2 circuit to be established even though
the MTU configured on the PE router does not match the MTU configured on the remote
PE router by including the ignore-mtu-mismatch statement at the [edit protocols l2circuit
neighbor address interface interface-name] hierarchy level.
Related
Documentation
Configuring the Media MTU
Enabling the Layer 2 Circuit When the Encapsulation Does Not Match
You can configure the Junos OS to allow a Layer 2 circuit to be established even though
the encapsulation configured on the CE device interface does not match the encapsulation
configured on the Layer 2 circuit interface by including the ignore-encapsulation-mismatch
statement. You can configure the ignore-encapsulation-mismatch statement for the
connection to the remote connection by including the statement at the [edit protocols
l2circuit neighbor address interface interface-name] hierarchy level or for the local
connection by including this statement at the [edit protocols l2circuit local-switching
interface interface-name] hierarchy level.
ignore-encapsulation-mismatch;
Related
Documentation
114
CHAPTER 8
MPLS, VPNs, and Pseudowires
TTL Processing on Incoming MPLS Packets on page 116
Redundant Pseudowires for Layer 2 Circuits and VPLS on page 121
Configuring Redundant Pseudowires for Layer 2 Circuits and VPLS on page 123
Configuring the Pseudowire Status TLV on page 125
Example: TDM Pseudowire Base Configuration on page 125
Example: ATM Pseudowire Base Configuration on page 129
Example: Ethernet Pseudowire Base Configuration on page 133
Example: Configuring the Pseudowire Status TLV on page 136
MPLS Overview for ACX Series Universal Access Routers

Multiprotocol Label Switching (MPLS) provides a mechanism for engineering network
traffic patterns that is independent of routing tables by assigning short labels to network
packets, which describe how to forward them through the network. MPLS is independent
of any routing protocol and can be used for unicast packets. On the ACX Series routers,
the following MPLS features are supported:
The configuration of a label-switching router (LSR) for processing of label-switched

packets and forwarding of packets based on their labels.
The configuration of an ingress label edge router (LER) where IP packets are
encapsulated within MPLS packets and forwarded to the MPLS domain, and as an
egress LER where MPLS packets are decapsulated and the IP packets contained within
the MPLS packets are forwarded using information in the IP forwarding table.
Configuring MPLS on the LER is the same as configuring an LSR.
Uniform and pipe mode configuration providing different types of visibility in the MPLS
network. Uniform mode makes all the nodes that a label-switched path (LSP) traverses
visible to nodes outside the LSP tunnel. Uniform mode is the default. Pipe mode makes
only the LSP ingress and egress points visible to nodes outside the LSP tunnel. Pipe
mode acts like a circuit and must be enabled with the global no-propagate-ttl statement
115
at the [edit protocols mpls] hierarchy level on each router that is in the path of the LSP.
The no-propagate-ttl statement disables time-to-live (TTL) propagation at the router
level and affects all RSVP-signalled or LDP-signalled LSPs. Only the global configuration
of TTL propagation is supported.
Related
Documentation
Exception packet handling of IP packets not processed by the normal packet flow
through the Packet Forwarding Engine. The following types of exception packet handling
are supported:
Router alert
Time-to-live (TTL) expiry value
Virtual circuit connection verification (VCCV)
LSP hot standby for secondary paths configuration to maintain a path in a hot-standby
state enabling swift cut over to the secondary path when downstream routers on the
current active path indicate connectivity problems.
Redundancy for a label-switched path (LSP) path with the configuration of fast reroute.
Configuration of link protection to ensure that traffic traversing a specific interface

from one router to another can continue to reach its destination in the event that this
interface fails.
Minimum MPLS Configuration
MPLS Configuration Guide
RSVP Configuration Guide
Disabling Normal TTL Decrementing
Fast Reroute Overview
Configuring Fast Reroute
MPLS and Traffic Protection
Configuring Link Protection on Interfaces Used by LSPs
Configuring Hot Standby of Secondary Paths
TTL Processing on Incoming MPLS Packets

The flow chart on Figure 10 on page 118 illustrates TTL processing on incoming MPLS
packets. On a transit LSR or an egress LER, MPLS pops one or more labels and can push
one or more labels. The incoming TTL of the packet is determined by the configured TTL
processing tunnel model.
When all of the following conditions are met, the incoming TTL is set to the TTL value
found in the immediate inner header:
116
The outer label is popped as opposed to being swapped
The TTL processing model is configured to pipe
Chapter 8: MPLS, VPNs, and Pseudowires
The inner header is MPLS or IP
If any of those conditions is not met, then the incoming TTL is set to the TTL value found
in the outermost label. In all cases, the TTL values of any further inner labels are ignored.
When an IP packet is exposed after MPLS pops all the labels that should be popped,
MPLS passes the packet to IP for further processing, including TTL checking. When the
uniform tunnel model for TTL processing is in effect, MPLS sets the TTL value of the IP
packet to the incoming TTL value that was just set. In other words, the TTL value is copied
from the outermost label to the IP packet. When the pipe model for TTL processing is in
effect, the TTL value in the IP header is left unchanged.
If an IP packet is not exposed by the label popping, then MPLS performs the TTL validation.
If the incoming TTL is less than 2, the packet is dropped. If innermost packet is IP, an
ICMP packet is built and sent. If the TTL does not expire and the packet needs to be sent
out, the outgoing TTL is determined by the rules for outgoing MPLS packets.
117
Figure 10: TTL Processing on Incoming MPLS Packets
Related
Documentation
Disabling Normal TTL Decrementing
no-propagate-ttl
ATM Pseudowire Overview

An Asynchronous Transfer Mode (ATM) pseudowire acts as a Layer 2 circuit or service,
which allows the migration of ATM services to an MPLS packet-switched network without
having to provision the ATM subscriber or customer edge (CE) device. When you configure
an ATM pseudowire, the network between the customer edge (CE) routers appears
transparent to the CE routers, making it seem that the CE routers are directly connected
118
across a time-division multiplex (TDM) leased line. ATM pseudowires are primarily used
in an ATM service providers network to connect existing ATM switches across a higher
speed packet-switched network or to provide ATM backhaul services for remote access
to existing ATM networks.
On ACX series routers, you configure an ATM pseudowire with Layer 2 encapsulation for
Inverse Multiplexing for ATM (IMA).
Related
Documentation
Ethernet Pseudowire Overview

An Ethernet pseudowire is used to carry Ethernet or 802.3 Protocol Data Units (PDUs)
over an MPLS network enabling service providers to offer emulated Ethernet services
over existing MPLS networks. Ethernet or 802.3 PDUs are encapsulated within the
pseudowire to provide a point-to-point Ethernet service. For the point-to-point Ethernet
service, the following fault management features are supported:
The IEEE 802.3ah standard for Operation, Administration, and Management (OAM).
You can configure IEEE 802.3ah OAM link-fault management on Ethernet point-to-point
direct links or links across Ethernet repeaters.
Ethernet OAM link-fault management can be used for physical link-level fault detection
and management. It uses a new, optional sublayer in the data link layer of the OSI
model. Ethernet OAM can be implemented on any full-duplex point-to-point or
emulated point-to-point Ethernet link. A system-wide implementation is not required;
OAM can be deployed on particular interfaces of a router. Transmitted Ethernet OAM
messages or OAM PDUs are of standard length, untagged Ethernet frames within the
normal frame length limits in the range 641518 bytes.
Ethernet connectivity fault management (CFM) to monitor the physical link between
two routers.
Connection protection using the continuity check protocol for fault monitoring . The
continuity check protocol is a neighbor discovery and health check protocol that
discovers and maintains adjacencies at the VLAN or link level.
Path protection using the linktrace protocol for path discovery and fault verification
. Similar to IP traceroute, the linktrace protocol maps the path taken to a destination
MAC address through one or more bridged networks between the source and
destination.
119
Related
Documentation
Configuring 802.3ah OAM Link-Fault Management
TDM Pseudowires Overview

A TDM pseudowire acts as Layer 2 circuit or service for T1 and E1 circuit signals across an
MPLS packet-switched network. On ACX Series routers, you configure a TDM pseudowire
with Structure-Agnostic Time Division Multiplexing (TDM) over Packet (SAToP) on the
ACX Series built-in channelized T1 and E1 interfaces. When you configure a TDM
pseudowire, the network between the customer edge (CE) routers appears transparent
to the CE routers, making it seem that the CE routers are directly connected. With the
SAToP configuration on the provider edge (PE) routers T1 and E1 interfaces, the
interworking function (IWF) forms a payload (frame) that contains the CE routers T1
and E1 Layer 1 data and control word. This data is transported to the remote PE over the
pseudowire. The remote PE removes all the Layer 2 and MPLS headers added in the
network cloud and forwards the control word and the Layer 1 data to the remote IWF,
which in turn forwards the data to the remote CE router.
Related
Documentation
120
SAToP Emulation on T1 and E1 Interfaces Overview on page 102
Redundant Pseudowires for Layer 2 Circuits and VPLS

A redundant pseudowire can act as a backup connection between PE routers and CE
devices, maintaining Layer 2 circuit and VPLS services after certain types of failures. This
feature can help improve the reliability of certain types of networks (metro for example)
where a single point of failure could interrupt service for multiple customers. Redundant
pseudowires cannot reduce traffic loss to zero. However, they provide a way to gracefully
recover from pseudowire failures in such a way that service can be restarted within a
known time limit.
NOTE: VPLS is not supported on ACX Series routers.
When you configure redundant pseudowires to remote PE routers, you configure one to
act as the primary pseudowire over which customer traffic is being transmitted and you
configure another pseudowire to act as a backup in the event the primary fails. You
configure the two pseudowires statically. A separate label is allocated for the primary
and backup neighbors.
For information about how to configure redundant pseudowires, see Configuring
Redundant Pseudowires for Layer 2 Circuits and VPLS on page 123.
The following sections provide an overview of redundant pseudowires for Layer 2 circuits
and VPLS:
Types of Redundant Pseudowire Configurations on page 121
Pseudowire Failure Detection on page 122
Types of Redundant Pseudowire Configurations

You can configure redundant pseudowires for Layer 2 circuits and VPLS in either of the
following manners:
You can configure a single active pseudowire. The PE router configured as the primary
neighbor is given preference and this connection is the one used for customer traffic.
For the LDP signalling, labels are exchanged for both incoming and outgoing traffic
with the primary neighbor. The LDP label advertisement is accepted from the backup
neighbor, but no label advertisement is forwarded to it, leaving the pseudowire in an
incomplete state. The pseudowire to the backup neighbor is completed only when the
primary neighbor fails. The decision to switch between the two pseudowires is made
by the device configured with the redundant pseudowires. The primary remote PE
router is unaware of the redundant configuration, ensuring that traffic is always switched
using just the active pseudowire.
Alternatively, you can configure two active pseudowires, one to each of the PE routers.
Using this approach, control plane signalling is completed and active pseudowires are
121
established with both the primary and backup neighbors. However, the data plane
forwarding is done only over a one of the pseudowires (designated as the active
pseudowire by the local device). The other pseudowire is on standby. The active
pseudowire is preferably established with the primary neighbor and can switch to the
backup pseudowire if the primary fails.
The decision to switch between the active and standby pseudowires is controlled by
the local device. The remote PE routers are unaware of the redundant connection, and
so both remote PE routers send traffic to the local device. The local device only accepts
traffic from the active pseudowire and drops the traffic from the standby. In addition,
the local device only sends traffic to the active pseudowire. If the active pseudowire
fails, traffic is immediately switched to the standby pseudowire.
The two configurations available for pseudowire redundancy have the following
limitations:
For the single active pseudowire configuration, it takes more time (compared to the
two active pseudowire configuration) to switchover to the backup pseudowire when
a failure is detected. This approach requires additional control plane signalling to
complete the pseudowire with the backup neighbor and traffic can be lost during the
switchover from primary to backup.
If you configure two active pseudowires, bandwidth is lost on the link carrying the
backup pseudowire between the remote PE router and the local device. Traffic is always
duplicated over both the active and standby pseudowires. The single active pseudowire
configuration does not waste bandwidth in this fashion.
You cannot enable GRES (graceful Routing Engine switchover) for redundant
pseudowires.
You cannot enable NSR (nonstop active routing) for redundant pseudowires.
NOTE: GRES and NSR are not supported on ACX Series routers.
Pseudowire Failure Detection

The following events are used to detect a failure (control and data plane) of the
pseudowire configured between a local device and a remote PE router and initiates the
switch to a redundant pseudowire:
122
Manual switchover (user initiated)
Remote PE router withdraws the label advertisement
LSP to the remote PE router goes down
LDP session with the remote PE router goes down
Local configuration changes
Periodic pseudowire OAM procedure fails (Layer 2 circuit-based MPLS ping to the PE
router fails)
When you configure a redundant pseudowire between a CE device and a PE router, a

periodic (once a minute) ping packet is forwarded through the active pseudowire to
verify data plane connectivity. If the ping fails, traffic is automatically switched to the
redundant pseudowire.
When a failure is detected, traffic is switched to the redundant pseudowire which is then
also designated as the active pseudowire. The switch is nonreversible, meaning that once
traffic has been switched to the redundant pseudowire, it remains active unless it also
fails unless the switch to the redundant pseudowire is never done unless there is a failure
in the currently active pseudowire. For example, a primary pseudowire has failed and
traffic has been successfully switched to the redundant pseudowire. After a period of
time, the cause of the failure of the primary pseudowire has been resolved and it is now
possible to reestablish the original connection. However, traffic is not switched back to
the original pseudowire unless a failure is detected on the now active pseudowire.
Related
Documentation
Example: Configuring H-VPLS Without VLANs
Configuring Redundant Pseudowires for Layer 2 Circuits and VPLS

A redundant pseudowire can act as a backup connection between PE routers and CE
devices, maintaining Layer 2 circuit and VPLS services after certain types of failures. This
feature can help improve the reliability of certain types of networks (metro for example)
where a single point of failure could interrupt service for multiple customers. Redundant
pseudowires cannot reduce traffic loss to zero. However, they provide a way to gracefully
recover from pseudowire failures in such a way that service can be restarted within a
known time limit.
For an overview of how redundant pseudowires work, see Redundant Pseudowires for
Layer 2 Circuits and VPLS on page 121.
To configure pseudowire redundancy for Layer 2 circuits and VPLS, complete the
procedures in the following sections:
Configuring Pseudowire Redundancy on the PE Router on page 123
Configuring the Switchover Delay for the Pseudowires on page 124
Configuring a Revert Time for the Redundant Pseudowire on page 124
Configuring Pseudowire Redundancy on the PE Router

You configure pseudowire redundancy on the PE router acting as the egress for the
primary and standby pseudowires using the backup-neighbor statement.
To configure pseudowire redundancy on the PE router, include the backup-neighbor
statement:
backup-neighbor {
community name;
123
standby;
virtual-circuit-id number;
}
summary for this statement.
The backup-neighbor statement includes the following configuration options:
communitySpecifies the community for the backup neighbor.
psn-tunnel-endpointSpecifies the endpoint address for the packet switched network
(PSN) tunnel on the remote PE router. The PSN tunnel endpoint address is the
destination address for the LSP on the remote PE router.
standbyConfigures the pseudowire to the specified backup neighbor as the standby.
When you configure this statement, traffic flows over both the active and standby
pseudowires to the CE device. The CE device drops the traffic from the standby
pseudowire, unless the active pseudowire fails. If the active pseudowire fails, the CE
device automatically switches to the standby pseudowire.
virtual-circuit-idUniquely identifies the primary and standby Layer 2 circuits. This
option is configurable for Layer 2 circuits only.
Configuring the Switchover Delay for the Pseudowires

To configure the time the router waits before switching traffic from the failed primary
pseudowire to a backup pseudowire, include the switchover-delay statement:
switchover-delay milliseconds;
Configuring a Revert Time for the Redundant Pseudowire

You can specify a revert time for redundant Layer 2 circuit and VPLS pseudowires. When
you have configured redundant pseudowires for Layer 2 circuits or VPLS, traffic is switched
to the backup pseudowire in the event that the primary pseudowire fails. If you configure
a revert time, when the configured time expires traffic is reverted back to the primary
pseudowire, assuming the primary pseudowire has been restored.
To configure a revert time for redundant pseudowires, specify the time in seconds using
the revert-time statement:
revert-time seconds;
Related
Documentation
124
Example: Configuring H-VPLS Without VLANs
Configuring the Pseudowire Status TLV

The pseudowire status type length variable (TLV) is used to communicate the status of
a pseudowire back and forth between two provider edge (PE) routers. For Layer 2 circuit
configurations, you can configure the PE router to negotiate the pseudowire with its
neighbor using the pseudowire status TLV. The pseudowire status TLV is configurable
for each pseudowire connection and is disabled by default. The pseudowire status
negotiation process assures that a PE router reverts back to the label withdraw method
for pseudowire status if its remote PE router neighbor does not support the pseudowire
status TLV.
Unlike the control word, a PE routers ability to support the pseudowire status TLV is
communicated when the initial label mapping message is sent to its remote PE router.
Once the PE router transmits its support for the pseudowire status TLV to its remote PE
router, it includes the pseudowire status TLV in every label mapping message sent to
the remote PE router. If you disable support for the pseudowire status TLV on the PE
router, a label withdraw message is sent to the remote PE router and then a new label
mapping message without the pseudowire status TLV follows.
To configure the pseudowire status TLV for the pseudowire to the neighbor PE router,
include the pseudowire-status-tlv statement at an appropriate hierarchy level.
For a list of the hierarchy levels at which you can include this statement, see the statement
summarysection for this statement.
Related
Documentation
Example: Configuring the Pseudowire Status TLV on page 136
pseudowire-status-tlv
Configuring Interfaces for Layer 2 Circuits
Example: TDM Pseudowire Base Configuration
Overview of a TDM Pseudowire Base Configuration on page 125
Configuring an TDM Pseudowire on page 126
Requirements
The following is a list of the hardware and software requirements for this configuration.
One ACX Series router
Overview of a TDM Pseudowire Base Configuration

The configuration shown here is the base configuration of an TDM pseudowire with T1
framing on an ACX Series router. This configuration is for one provider edge router. To
125
complete the TDM pseudowire configuration, you need to repeat this configuration on
an other provider edge router in the Multiprotocol Label Switched (MPLS) network.
Configuring an TDM Pseudowire

CLI Quick
Configuration
level:
set
set
set
set
set
set
set
set
set
set
set
set
set
set
set
set
set
1
chassis fpc 0 pic 0 framing t1

interfaces ct1-0/0/0 no-partition interface-type t1
interfaces t1-0/0/0 encapsulation satop
interfaces t1-0/0/0 unit 0
interfaces ge-0/2/0 unit 0 family inet address 20.1.1.2/24
interfaces ge-0/2/0 unit 0 family mpls
interfaces lo0 unit 0 family inet address 70.1.1.1/32
protocols rsvp interface ge-0/2/0.0
protocols mpls no-cspf
protocols mpls label-switched-path PE1-to-PE2 to 40.1.1.1
protocols mpls interface ge-0/2/0.0
protocols ospf traffic-engineering
protocols ospf area 0.0.0.0 interface ge-0/2/0.0
protocols ospf area 0.0.0.0 interface lo0.0 passive
protocols ldp interface ge-0/2/0.0
protocols ldp interface lo0.0
protocols l2circuit neighbor 40.1.1.1 interface t1-0/0/0.0 virtual-circuit-id
NOTE: To configure a TDM pseudowire with E1 framing, include the e1

statement at the [edit chassis fpc 0 pic 0 framing] hierarchy level instead of
the t1 statement shown in this example.
Step-by-Step
Procedure
1.
Configure the framing format:

[edit]
user@host# edit chassis
[edit chassis]
user@host# set fpc 0 pic 0 framing t1
2.
Create a T1 interface on a channelized T1 interface (ct1) and enable full

channelization with the no-partition statement. On the logical T1 interface, set the
Structure-Agnostic TDM over Packet (SAToP) encapsulation mode.
[edit]
[edit interfaces]
user@host# set ct1-0/0/0 no-partition interface-type t1
user@host# set t1-0/0/0 encapsulation satop
user@host# set t1-0/0/0 unit 0
126
3.
Create a Gigabit Ethernet interface and enable MPLS on that interface. Create the
loopback (lo0) interface:
[edit interfaces]
user@host# set ge-0/2/0 unit 0 family inet address 20.1.1.2/24
user@host# set ge-0/2/0 unit 0 family mpls
user@host# set lo0 unit 0 family inet address 70.1.1.1/32
4.
Enable the MPLS and RSVP protocols on the MPLS interfacege-0/2/0.0:

[edit]
user@host# edit protocols
[edit protocols]
user@host# set rsvp interface ge-0/2/0.0
user@host# set mpls interface ge-0/2/0.0
5.
Configure LDP. If you configure RSVP for a pseudowire, you must also configure
LDP:
[edit protocols]
user@host# set ldp interface ge-0/2/0.0
user@host# set ldp interface lo0.0
6.
Configure a point-to-point label-switched path (LSP) and disable constrained-path

LSP computation:
[edit protocols]
user@host# set mpls label-switched-path PE1-to-PE2 to 40.1.1.1
user@host# set mpls no-cspf
7.
Configure OSPF and enable traffic engineering on the MPLS interfacege-0/2/0.0,

and on the loopback (lo0) interface:
[edit protocols]
user@host# set ospf traffic-engineering
user@host# set ospf area 0.0.0.0 interface ge-0/2/0.0
user@host# set ospf area 0.0.0.0 interface lo0.0 passive
8.
Uniquely identify a Layer 2 circuit for the TDM pseudowire:

[edit protocols]
user@host# set l2circuit neighbor 40.1.1.1 interface t1-0/0/0.0 virtual-circuit-id 1
127
Results
[edit]
user@host# show
chassis {
fpc 0 {
pic 0 {
framing t1;
}
}
}
interfaces {
ct1-0/0/0 {
no-partition interface-type t1;
}
t1-0/0/0 {
encapsulation satop;
unit 0;
}
ge-0/2/0 {
unit 0 {
family inet {
address 20.1.1.2/24;
}
family mpls;
}
}
lo0 {
unit 0 {
family inet {
address 70.1.1.1/32;
}
}
}
}
protocols {
rsvp {
interface ge-0/2/0.0;
}
mpls {
no-cspf;
label-switched-path PE1-to-PE2 {
to 40.1.1.1;
}
}
ospf {
traffic-engineering;
area 0.0.0.0 {
interface lo0.0 {
passive;
}
}
}
ldp {
interface lo0.0;
}
l2circuit {
128
neighbor 40.1.1.1 {
}
}
}
}
Related
Documentation
Example: ATM Pseudowire Base Configuration
Overview of an ATM Pseudowire With Cell Mode Base Configuration on page 129
Configuring an ATM Pseudowire on page 129
Requirements
Overview of an ATM Pseudowire With Cell Mode Base Configuration

The configuration shown here is the base configuration of an ATM pseudowire with ATM
cell-relay encapsulation on an ACX Series router. This configuration is for one provider
edge router. To complete the configuration of an ATM pseudowire, you need to repeat
this configuration on an other provider edge router in the MPLS network.
Configuring an ATM Pseudowire

CLI Quick
Configuration
level:
set
set
set
set
set
set
set
set
set
set
set
set
set
set
set
interfaces at-0/0/0 atm-options vpi 0

interfaces at-0/0/0 unit 0 encapsulation atm-ccc-cell-relay
interfaces at-0/0/0 unit 0 vci 0.64
interfaces ct1-0/0/0 no-partition interface-type at
129
set protocols ldp interface lo0.0

set protocols l2circuit neighbor 40.1.1.1 interface at-0/0/0.0 virtual-circuit-id
1
NOTE: To configure an ATM pseudowire with ATM virtual circuit (VC)

multiplex encapsulation on CCC circuits, include the atm-ccc-vc-mux
statement at the [edit interfaces at-0/0/0 unit 0 encapsulation] hierarchy
level instead of the atm-ccc-cell-relay statement shown in this example.
Step-by-Step
Procedure
1.
Create an ATM interface on a channelized T1 interface (ct1) and enable full

channelization with the no-partition statement. On the ATM interface, set the ATM
virtual circuit identifier (VCI), the virtual path identifier (VPI), and set the
encapsulation cell mode.
[edit]
[edit interfaces]
user@host# set ct1-0/0/0 no-partition interface-type at
user@host# set at-0/0/0 unit 0 vci 0.64
user@host# set at-0/0/0 atm-options vpi 0
user@host# set at-0/0/0 unit 0 encapsulation atm-ccc-cell-relay
2.
Create a Gigabit Ethernet interface and enable MPLS on that interface. Create the
loopback (lo0) interface:
[edit interfaces]
3.
Enable the MPLS and RSVP protocols on the MPLS interfacege-0/2/0.0:

[edit]
[edit protocols]
4.
LDP:
[edit protocols]
user@host# set protocols ldp interface ge-0/2/0.0
user@host# set protocols ldp interface lo0.0
5.

LSP computation:
[edit protocols]
130
6.

[edit protocols]
7.
Uniquely identify a Layer 2 circuit for the ATM pseudowire:

[edit protocols]
user@host# set l2circuit neighbor 40.1.1.1 interface at-0/0/0.0 virtual-circuit-id 1
131
Results
[edit]
user@host# show
interfaces {
at-0/0/0 {
atm-options {
vpi 0;
}
unit 0 {
encapsulation atm-ccc-cell-relay;
vci 0.64;
}
}
ct1-0/0/0 {
no-partition interface-type at;
}
ge-0/2/0 {
unit 0 {
family inet {
address 20.1.1.2/24;
}
family mpls;
}
}
lo0 {
unit 0 {
family inet {
address 70.1.1.1/32;
}
}
}
}
protocols {
rsvp {
}
mpls {
no-cspf;
to 40.1.1.1;
}
}
ospf {
area 0.0.0.0 {
interface lo0.0 {
passive;
}
}
}
ldp {
interface lo0.0;
}
l2circuit {
neighbor 40.1.1.1 {
interface at-0/0/0.0 {
132
}
}
}
}
Related
Documentation
Example: Ethernet Pseudowire Base Configuration
Overview of an Ethernet Pseudowire Base Configuration on page 133
Configuring an Ethernet Pseudowire on page 133
Requirements
Overview of an Ethernet Pseudowire Base Configuration

The configuration shown here is the base configuration of an Ethernet pseudowire with
Ethernet cross-connect for physical interface encapsulation on an ACX Series router.
This configuration is for one provider edge router. To complete the configuration of an
Ethernet pseudowire, you need to repeat this configuration on an other provider edge
router in the Multiprotocol Label Switched (MPLS) network.
Configuring an Ethernet Pseudowire

CLI Quick
Configuration
level:
set
set
set
set
set
set
set
set
set
set
set
set
set
set
interfaces ge-0/1/1 encapsulation ethernet-ccc

interfaces ge-0/1/1 unit 0
protocols ldp interface lo0.0
133
set protocols l2circuit neighbor 40.1.1.1 interface ge-0/1/1.0 virtual-circuit-id

1
NOTE: To configure an Ethernet pseudowire with 802.1Q tagging for

cross-connect logical interface encapsulation, include the vlan-ccc statement
at the [edit interfaces ge-0/1/1 unit 0 encapsulation] hierarchy level instead
of the ethernet-ccc statement shown in this example.
Step-by-Step
Procedure
1.
Create two Gigabit Ethernet interfaces, set the encapsulation mode on one interface
and MPLS on the other interface. Create the loopback (lo0) interface:
[edit]
[edit interfaces]
user@host# set ge-0/1/1 encapsulation ethernet-ccc
user@host# set ge-0/1/1 unit 0
2.
Enable the MPLS and RSVP protocols on the interface configured with
MPLSge-0/2/0.0:
[edit]
[edit protocols]
3.
LDP:
[edit protocols]
user@host# set protocols ldp interface ge-0/2/0.0
user@host# set protocols ldp interface lo0.0
4.

LSP computation:
[edit protocols]
5.

[edit protocols]
6.
Uniquely identify a Layer 2 circuit for the Ethernet pseudowire:

[edit protocols]
user@host# set l2circuit neighbor 40.1.1.1 interface ge-0/1/1.0 virtual-circuit-id 1
134
Results
[edit]
user@host# show
interfaces {
ge-0/1/1 {
encapsulation ethernet-ccc;
unit 0;
}
ge-0/2/0 {
unit 0 {
family inet {
address 20.1.1.2/24;
}
family mpls;
}
}
lo0 {
unit 0 {
family inet {
address 70.1.1.1/32;
}
}
}
}
protocols {
rsvp {
}
mpls {
no-cspf;
to 40.1.1.1;
}
}
ospf {
area 0.0.0.0 {
interface lo0.0 {
passive;
}
}
}
ldp {
interface lo0.0;
}
l2circuit {
neighbor 40.1.1.1 {
interface ge-0/1/1.0 {
}
}
}
}
Related
135
Documentation
Example: Configuring the Pseudowire Status TLV

Requirements
One ACX Series Universal Access router
Overview
The configuration shown here is the base configuration of a pseudowire with
pseudowire-status-tlv enabled. The pseudowire-status-tlv is used to communicate the
status of a pseudowire between PE routers.
Configuration
CLI Quick
Configuration
level:
edit protocols l2circuit
set neighbor 10.255.64.26
set neighbor 10.255.64.26 interface xe-0/0/0
set neighbor 10.255.64.26 interface xe-0/0/0 pseudowire-status-tlv
set neighbor 10.255.64.26 interface xe-0/0/0 virtual-circuit-id 1024
Configuring the Pseudowire Status TLV

Step-by-Step
Procedure
1.
Navigate to the [edit protocols l2circuit] hierarchy level to configure Layer 2 circuits
over MPLS.
[edit]
user@host# edit protocols l2circuit
2.
Set the address for the neighbor provider edge router;, this example uses a fictitious
address, 10.255.64.26.
user@host# set neighbor 10.255.64.26
3.
Specify the name of the interface forming the Layer 2 circuit; this example uses
xe-0/0/0.
user@host# set neighbor 10.255.64.26 interface xe-0/0/0
4.
Enter the pseudowire-status-tlv statement.

user@host# set neighbor 10.255.64.26 interface xe-0/0/0 pseudowire-status-tlv
136
NOTE: You need to configure the virtual-circuit-id statement in order

for pseudowire-status-tlv to work.
5.
Set the virtual-circuit-id statement to identify the pseudowire as regular or

redundant. The identifier value can range from 1 through 4,294,967,295.
user@host# set neighbor 10.255.64.26 interface xe-0/0/0 virtual-circuit-id 1024
6.
Check your configuration by entering the show command.
Results
user@host# show
neighbor 10.255.64.26 {
interface xe-0-0-0 {
pseudowire-status-tlv;
}
}
Related
Documentation
Configuring the Pseudowire Status TLV on page 125
137
138
CHAPTER 9
Network Management
Real-Time Performance Monitoring on ACX Series Routers on page 139
Standard SNMP MIBs Supported by Junos OS on page 140
Juniper Networks Enterprise-Specific MIBs and Supported Devices on page 155
Real-Time Performance Monitoring on ACX Series Routers

Real-time performance monitoring (RPM) allows the user to perform service-level
monitoring. When RPM is configured on a router, the router calculates network
performance based on packet response time, jitter, and packet loss. RPM is supported
on all ACX Series routers. You can configure these values to be gathered by HTTP, Internet
Control Message Protocol (ICMP), TCP, and UDP requests. The router gathers RPM
statistics by sending out probes to a specified probe target, identified by an IP address.
When the target receives a probe, it generates responses that are received by the router.
You set the probe options in the test test-name statement at the [edit services rpm probe
owner] hierarchy level. You use the show services rpm probe-results command to view
the results of the most recent RPM probes.
NOTE: Packet Forwarding Engine timestamping is available only for ICMP

probes and for UDP probes with the destination port set to UDP_ECHO port
(7).
On ACX Series routers, the following statements are supported at the [edit services rpm]
hierarchy level:
probe owner {
test test-name {
data-fill data;
data-size size;
destination-interface interface-name;
destination-port port;
dscp-code-point dscp-bits;
hardware-timestamp;
history-size size;
moving-average-size number;
one-way-hardware-timestamp;
probe-count count;
probe-interval seconds;
139
probe-type type;
routing-instance instance-name;
source-address address;
target (url url | address address);
test-interval interval;
thresholds thresholds;
traps traps;
}
}
Related
Documentation
Configuring Real-Time Performance Monitoring
Examples: Configuring Real-Time Performance Monitoring
show services rpm probe-results
Standard SNMP MIBs Supported by Junos OS

Table 24 on page 140 contains the list of standard SNMP MIBs and RFCs that are supported
on various devices running Junos OS. RFCs can be found at http://www.ietf.org .
NOTE: In this table, a value of 1 in any of the platform columns (ACX, M, T, J,

MX, EX, and SRX) denotes that the corresponding MIB is supported on that
particular platform, and a value of 0 denotes that the MIB is not supported
on the platform.
Table 24: Standard MIBs Supported on Devices Running Junos OS

Platforms
SRX
MIB/RFC
ACX
MX
EX
LowEnd
MidRange
HighEnd
IEEE 802.1ab section 12.1, Link Layer Discovery

Protocol (LLDP) MIB
EX Series implementation of LLDP MIB supports

both IPv4 and IPv6 configuration.
For more information about LLDP MIB objects
supported on EX Series devices, see LLDP Standard
MIB Objects Supported on EX Series Devices.
140
Chapter 9: Network Management
Table 24: Standard MIBs Supported on Devices Running Junos OS (continued)

Platforms
SRX
MIB/RFC
ACX
MX
EX
LowEnd
MidRange
HighEnd
IEEE, 802.3ad, Aggregation of Multiple Link

Segments
RFC 1155, Structure and Identification of

Management Information for TCP/IP-based
Internets
RFC 1157, A Simple Network Management Protocol

(SNMP)
RFC 1195, Use of OSI IS-IS for Routing in TCP/IP and

Dual Environments (only the objects isisSystem,
isisMANAreaAddr, isisAreaAddr, isisSysProtSupp,
isisSummAddr, isisCirc, isisCircLevel,
isisPacketCount, isisISAdj, isisISAdjAreaAddr,
isisAdjIPAddr, isisISAdjProtSupp, isisRa, and isisIPRA
are supported)
RFC 1212, Concise MIB Definitions
Supported tables and objects:
dot3adAggPortTable, dot3adAggPortListTable,
dot3adAggTable, and dot3adAggPortStatsTable
NOTE: EX Series switches do not support the

dot3adAggPortTable and dot3adAggPortStatsTable.
dot3adAggPortDebugTable (only
dot3adAggPortDebugRxState,
dot3adAggPortDebugMuxState,
dot3adAggPortDebugActorSyncTransitionCount,
dot3adAggPortDebugPartnerSyncTransitionCount,
dot3adAggPortDebugActorChangeCount, and
dot3adAggPortDebugPartnerChangeCount)
NOTE: EX Series switches do not support the

dot3adAggPortDebugTable.
dot3adTablesLastChanged
NOTE: Gigabit Ethernet interfaces on J Series

Services Routers do not support the 802.3ad MIB.
141

Platforms
SRX
MIB/RFC
ACX
MX
EX
LowEnd
MidRange
HighEnd
RFC 1213, Management Information Base for

Network Management of TCP/IP-Based Internets:
MIB-II. Junos OS supports the following areas:
RFC 1215, A Convention for Defining Traps for use

with the SNMP (only MIB II SNMP version 1 traps
and version 2 notifications)
RFC 1406, Definitions of Managed Objects for the

DS1 and E1 Interface Types (T1 MIB is supported)

DS3/E3 Interface Type (T3 MIB is supported)

Link Control Protocol of the Point-to-Point Protocol
(only pppLink group is supported. The pppLink
group consists of the pppLcp 1 object and the tables
pppLinkStatustable and pppLinkConfigTable).

Fourth Version of the Border Gateway Protocol
(BGP-4) using SMIv2
RFC 1695, Definitions of Managed Objects for ATM

Management Version 8.0 Using SMIv2
MIB II and its SNMP version 2 derivatives,

including:
Statistics counters
IP, except for ipRouteTable, which has been

replaced by ipCidrRouteTable (RFC 2096, IP
Forwarding Table MIB)
SNMP management
Interface management
SNMPv1 Get, GetNext requests, and version 2

GetBulk request
Junos OS-specific secured access list
Master configuration keywords
Reconfigurations upon SIGHUP
142

Platforms
SRX
MIB/RFC
ACX
MX
EX
LowEnd
MidRange
HighEnd
RFC 1850, OSPF Version 2 Management Information

Base (except for the ospfOriginateNewLsas and
ospfRxNewLsas objects, the Host Table, and the
traps ospfOriginateLSA, ospfLsdbOverflow, and
ospfLsdbApproachingOverflow)
RFC 1901, Introduction to Community-based

SNMPv2
RFC 2011, SNMPv2 Management Information Base

for the Internet Protocol Using SMIv2

for the Transmission Control Protocol Using SMIv2

for the User Datagram Protocol Using SMIv2
RFC 2024, Definitions of Managed Objects for Data

Link Switching Using SMIv2 (except for the
dlswInterface and dlswSdlc object groups; the
dlswDirLocateMacTable, dlswDirNBTable, and
dlswDirLocateNBTable tables; the
dlswCircuitDiscReasonLocal and
dlswCircuitDiscReasonRemote tabular objects; and
the dlswDirMacCacheNextIndex and
dlswDirNBCacheNextIndex scalar objects; read-only
access)
RFC 2096, IP Forwarding Table MIB (The

ipCidrRouteTable has been extended to include the
tunnel name when the next hop is through an
RSVP-signaled LSP.)
RFC 2115, Management Information Base for Frame

Relay DTEs Using SMIv2 (frDlcmiTable only;
frCircuitTable and frErrTable are not supported)
RFC 2233, The Interfaces Group MIB Using SMIv2
NOTE: RFC 2096 has been replaced by RFC 4292.

However, Junos OS currently supports both RFC
2096 and RFC 4292.
NOTE: RFC 2233 has been replaced by RFC 2863,

IF MIB. However, Junos OS supports both RFC 2233
and RFC 2863.
143

Platforms
SRX
MIB/RFC
ACX
MX
EX
LowEnd
MidRange
HighEnd
RFC 2287, Definitions of System-Level Managed

Objects for Applications (only the objects
sysApplInstallPkgTable, sysApplInstallElmtTable,
sysApplElmtRunTable, and sysApplMapTable)
RFC 2465, Management Information Base for IP

Version 6: Textual Conventions and General Group
(except for IPv6 interface statistics)

DS1, E1, DS2, and E2 Interface Types (except for
dsx1FarEndConfigTable, dsx1FarEndCurrentTable,
dsx1FarEndIntervalTable, dsx1FarEndTotalTable,
and dsx1FracTable)
RFC 2515, Definitions of Managed Objects for ATM

Management (except atmVpCrossConnectTable,
atmVcCrossConnectTable, and aal5VccTable)
RFC 2570, Introduction to Version 3 of the

Internet-standard Network Management Framework
RFC 2571, An Architecture for Describing SNMP

Management Frameworks (read-only access)

However, Junos OS supports both RFC 2571 and
RFC 3411.
RFC 2572, Message Processing and Dispatching for
the Simple Network Management Protocol (SNMP)
(read-only access)
RFC 3412.
RFC 2576, Coexistence between Version 1, Version
2, and Version 3 of the Internet-standard Network
Management Framework
RFC 3584.
RFC 2578, Structure of Management Information
Version 2 (SMIv2)
144

Platforms
SRX
MIB/RFC
ACX
MX
EX
LowEnd
MidRange
HighEnd
RFC 2579, Textual Conventions for SMIv2
RFC 2580, Conformance Statements for SMIv2
RFC 2662, Definitions of Managed Objects for ADSL

Lines (J Series Services Routers. All MIB tables,
objects, and traps are applicable for the ADSL
ATU-R agent.)

Ethernet-like Interface Types

Virtual Router Redundancy Protocol (except row
creation, the Set operation, and the object
vrrpStatsPacketLengthErrors)
RFC 2790, Host Resources MIB
Only the hrStorageTable. The file systems /,

/config, /var, and /tmp always return the same
index number. When SNMP restarts, the index
numbers for the remaining file systems might
change.
Only the objects of the hrSystem and

hrSWInstalled groups.
RFC 2819, Remote Network Monitoring Management

Information Base
etherStatsTable (for Ethernet interfaces

only),alarmTable, eventTable, and logTable are
supported on all devices running Junos OS.
historyControlTable and etherHistoryTable

(except etherHistoryUtilization object) are
supported only on EX Series switches.

RFC 2863, The Interfaces Group MIB
NOTE: RFC 2863 replaces RFC 2233. However,
Junos OS supports both RFC 2233 and RFC 2863.
RFC 2864, The Inverted Stack Table Extension to
the Interfaces Group MIB
145

Platforms
SRX
MIB/RFC
ACX
MX
EX
LowEnd
MidRange
HighEnd
RFC 2922, The Physical Topology (PTOPO) MIB
RFC 2925, Definitions of Managed Objects for

Remote Ping, Traceroute, and Lookup Operations
(only the objects pingCtlTable, pingResultsTable,
pingProbeHistoryTable,
pingMaxConcurrentRequests, traceRouteCtlTable,
traceRouteResultsTable,
traceRouteProbeHistoryTable, and
traceRouteHopsTable)
RFC 2932, IPv4 Multicast Routing MIB
RFC 2934, Protocol Independent Multicast MIB for

IPv4
RFC 2981, Event MIB
RFC 3014, Notification Log MIB
RFC 3019, IP Version 6 Management Information

Base for The Multicast Listener Discovery Protocol
RFC 3410 Introduction and Applicability Statements

for Internet-Standard Management Framework
RFC 3411, An Architecture for Describing Simple

Network Management Protocol (SNMP)
Management Frameworks
Supported objects:
ptopoConnDiscAlgorithm,
ptopoConnAgentNetAddrType,
ptopoConnAgentNetAddr,
ptopoConnMultiMacSASeen,
ptopoConnMultiNetSASeen, ptopoConnIsStatic,
ptopoConnLastVerifyTime, ptopoConnRowStatus
NOTE: In Junos OS, RFC 2934 is implemented

based on a draft version, pimmib.mib, of the now
standard RFC.
Support for the pimNeighborLoss trap was added
in Release 11.4.
NOTE: RFC 3411 replaces RFC 2571. However, Junos

OS supports both RFC 3411 and RFC 2571.
146

Platforms
SRX
MIB/RFC
ACX
MX
EX
LowEnd
MidRange
HighEnd
RFC 3412, Message Processing and Dispatching for

RFC 3413, Simple Network Management Protocol

(SNMP) Applications (except for the Proxy MIB)
RFC 3414, User-based Security Model (USM) for

version 3 of the Simple Network Management
Protocol (SNMPv3)
RFC 3415, View-based Access Control Model

(VACM) for the Simple Network Management
Protocol (SNMP)
RFC 3416, Version 2 of the Protocol Operations for

RFC 3417, Transport Mappings for the Simple

Network Management Protocol (SNMP)
RFC 3418, Management Information Base (MIB) for


Synchronous Optical Network (SONET) Linear
Automatic Protection Switching (APS) Architectures
(implemented under the Juniper Networks
enterprise branch [jnxExperiment])
RFC 3584 Coexistence between Version 1, Version

2, and Version 3 of the Internet-standard Network
Management Framework
NOTE: RFC 3412 replaces RFC 2572. However,

Junos OS supports both RFC 3412 and RFC 2572.
NOTE: RFC 3416 replaces RFC 1905, which was

supported in earlier versions of Junos OS.
NOTE: RFC 3418 replaces RFC 1907, which was

supported in earlier versions of Junos OS.
147

Platforms
SRX
MIB/RFC
ACX
MX
EX
LowEnd
MidRange
HighEnd
RFC 3591 Managed Objects for the Optical Interface

Type

Synchronous Optical Network/Synchronous Digital
Hierarchy (SONET/SDH) Interface Type
RFC 3621, Power Ethernet MIB

Ethernet WAN Interface Sublayer (except
etherWisDeviceTable, etherWisSectionCurrentTable,
and etherWisFarEndPathCurrentTable)
RFC 3811, Definitions of Textual Conventions (TCs)

for Multiprotocol Label Switching (MPLS)
Management
optIfOTMnTable (except optIfOTMnOpticalReach,

optIfOTMnInterfaceType, and optIfOTMnOrder),
optIfOChConfigTable (except optIfOChDirectionality
and optIfOChCurrentStatus), optIfOTUkConfigTable
(except optIfOTUkTraceIdentifierAccepted,
optIfOTUkTIMDetMode, optIfOTUkTIMActEnabled,
optIfOTUkTraceIdentifierTransmitted,
optIfOTUkDEGThr, optIfOTUkDEGM,
optIfOTUkSinkAdaptActive, and
optIfOTUkSourceAdaptActive), and
optIfODUkConfigTable (except
optIfODUkPositionSeqCurrentSize and
optIfODUkTtpPresent)
148

Platforms
SRX
MIB/RFC
ACX
MX
EX
LowEnd
MidRange
HighEnd
RFC 3812, Multiprotocol Label Switching (MPLS)

Traffic Engineering (TE) Management Information
Base (MIB) (read only access)
RFC 3813, Multiprotocol Label Switching (MPLS)

Label Switching Router (LSR) Management
Information Base (MIB) (read-only access).
mplsInterfacePerfTable, mplsInSegmentPerfTable,
mplsOutSegmentPerfTable,
mplsInSegmentMapTable, mplsXCUp, and
mplsXCDown are not supported.
RFC 3826, The Advanced Encryption Standard

(AES) Cipher Algorithm in the SNMP User-based
Security Model

DS3/E3 Interface Type (except
dsx3FarEndConfigTable, dsx3FarEndCurrentTable,
dsx3FarEndIntervalTable, dsx3FarEndTotalTable,
and dsx3FracTable)
MPLS tunnels as interfaces are not supported.
The following objects in the TunnelResource

table are not supported:
mplsTunnelResourceMeanRate,
mplsTunnelResourceMaxBurstSize,
mplsTunnelResourceMeanBurstSize,
mplsTunnelResourceExBurstSize,
mplsTunnelResourceWeight.
mplsTunnelPerfTable and
mplsTunnelCRLDPResTable are not supported.
mplsTunnelCHopTable is supported on ingress
routers only.
NOTE: The branch used by the proprietary LDP
MIB (ldpmib.mib) conflicts with RFC 3812.
ldpmib.mib has been deprecated and replaced by
jnx-mpls-ldp.mib.
149

Platforms
SRX
MIB/RFC
ACX
MX
EX
LowEnd
MidRange
HighEnd
RFC 4087, IP Tunnel MIBDescribes MIB objects

in the following tables for managing tunnels of any
type over IPv4 and IPv6 networks:
tunnelIfTableProvides information about the
tunnels known to a router.
tunnelInetConfigTableAssists dynamic creation
of tunnels and provides mapping from end-point

addresses to the current interface index value.
NOTE: Junos OS supports MAX-ACCESS of
read-only for all the MIB objects in tunnelIfTable
and tunnelInetConfigTable tables.
BridgesSupports 802.1D STP(1998). Supports
only the following subtrees and objects:
dot1dStp subtree is supported on MX Series 3D
Universal Edge Routers .
dot1dTpFdbAddress, dot1dTpFdbPort, and

dot1dTpFdbStatus objects from the
dot1dTpFdbTable of the dot1dTp subtree are
supported on EX Series Ethernet Switches.

NOTE: dot1dTpLearnedEntryDiscards and
dot1dTpAgingTime objects are supported on M and
T Series routers.
RFC 4292, IP Forwarding MIB Describes a table
and MIB objects for forwarding IP packets that are
version independent:
inetCidrRouteTableProvides the ability to
display IP version-independent multipath CIDR

routes and obsoletes the ipCidrRouteTable
object.
inetCidrRouteNumberIndicates the number of
current routes and obsoletes the

ipCidrRouteNumber object.
inetCidrRouteDiscardsCounts the number of
valid routes that are discarded from

inetCidrRouteTable and obsoletes the
ipCidrRouteDiscards object.
NOTE: Junos OS currently supports these MIB
objects that will be deprecated in future releases:
ipCidrRouteTable, ipCidrRouteNumber, and
ipCidrRouteDiscards.
150

Platforms
SRX
MIB/RFC
ACX
MX
EX
LowEnd
MidRange
HighEnd

Bridges with Rapid Spanning Tree
ProtocolSupports 802.1w and 802.1t extensions
for RSTP.
RFC 4363b, Q-Bridge VLAN MIB
RFC 4382 MPLS/BGP Layer 3 Virtual Private

Network (VPN) MIB
RFC 4444, IS-IS MIB
RFC 4668, RADIUS Accounting Client Management

Information Base (MIB) for IPv6 (read-only access)
RFC 4670, RADIUS Accounting Client Management

Information Base (MIB) (read-only access)
The Junos OS support for RFC 4382 includes the

following scalar objects and tables:
mplsL3VpnActiveVrfs
mplsL3VpnConfiguredVrfs
mplsL3VpnConnectedInterfaces
mplsL3VpnVrfConfMidRteThresh
mplsL3VpnVrfConfHighRteThresh
mplsL3VpnIfConfRowStatus
mplsL3VpnIllLblRcvThrsh
mplsL3VpnNotificationEnable
mplsL3VpnVrfConfMaxPossRts
mplsL3VpnVrfConfRteMxThrshTime
mplsL3VpnVrfOperStatus
mplsL3VpnVrfPerfCurrNumRoutes
mplsL3VpnVrfPerfTable
mplsL3VpnVrfRteTable
mplsVpnVrfRTTable
mplsL3VpnVrfSecIllegalLblVltns
mplsL3VpnVrfTable
NOTE: The mplsL3VpnIfConfTable has not been

implemented in the MPLS/BGP Layer 3 Virtual
Private Network (VPN) MIB, because of limited
utility and difficulty in representing the DistProtocol
bit accurately.
151

Platforms
SRX
MIB/RFC
ACX
MX
EX
LowEnd
MidRange
HighEnd
RFC 4801, Definitions of Textual Conventions for

Generalized Multiprotocol Label Switching (GMPLS)
Management Information Base (MIB) (read-only
access)
RFC 4802, Generalized Multiprotocol Label

Switching (GMPLS) Traffic Engineering (TE)
access). gmplsTunnelReversePerfTable,
gmplsTeScalars, gmplsTunnelTable,
gmplsTunnelARHopTable, gmplsTunnelCHopTable,
and gmplsTunnelErrorTable are not supported.)
RFC 4803, Generalized Multiprotocol Label

Switching (GMPLS) Label Switching Router (LSR)
access). gmplsLabelTable and
gmplsOutsegmentTable are not supported.
NOTE: The tables in GMPLS TE (RFC 4802) and

LSR (RFC 4803) MIBs are extensions of the
corresponding tables from the MPLS TE (RFC 3812)
and LSR (RFC 3813) MIBs and use the same index
as the MPLS MIB tables.
152

Platforms
SRX
MIB/RFC
ACX
MX
EX
LowEnd
MidRange
HighEnd
RFC 5643, Management Information Base for

OSPFv3

Virtual Router Redundancy Protocol Version 3
(VRRPv3) (except row creation, the Set operation,
and the objects
vrrpv3StatisticsRowDiscontinuityTime and
vrrpv3StatisticsPacketLengthErrors)
Internet Assigned Numbers Authority, IANAiftype

Textual Convention MIB (referenced by RFC 2233,
available at
http://www.iana.org/assignments/ianaiftype-mib)
NOTE: Junos OS support for this MIB is read-only.

Junos OS does not support the following tables
and objects defined in this MIB.
ospfv3HostTable
ospfv3CfgNbrTable
ospfv3ExitOverflowInterval
ospfv3ReferenceBandwidth
ospfv3RestartSupport
ospfv3RestartInterval
ospfv3RestartStrictLsaChecking
ospfv3RestartStatus
ospfv3RestartAge
ospfv3RestartExitReason
ospfv3NotificationEnable
ospfv3StubRouterSupport
ospfv3StubRouterAdvertisement
ospfv3DiscontinuityTime
ospfv3RestartTime
ospfv3AreaNssaTranslatorRole
ospfv3AreaNssaTranslatorState
ospfv3AreaNssaTranslatorStabInterval
ospfv3AreaNssaTranslatorEvents
ospfv3AreaTEEnabled
ospfv3IfMetricValue
ospfv3IfDemandNbrProbe
153

Platforms
SRX
MIB/RFC
ACX
MX
EX
LowEnd
MidRange
HighEnd
Internet draft
draft-ietf-atommib-sonetaps-mib-10.txt,
Definitions of Managed Objects for SONET Linear
APS Architectures (as defined under the Juniper
Networks enterprise branch [jnxExperiment] only)
Internet draft draft-ieft-bfd-mib-02.txt,

Bidirectional Forwarding Detection Management
Information Base (Represented by
mib-jnx-bfd-exp.txt and implemented under the
Juniper Networks enterprise branch
[jnxExperiment]. Read only. Includes bfdSessUp
and bfdSessDown traps. Does not support
bfdSessPerfTable and bfdSessMapTable.)
Internet draft draft-ietf-idmr-igmp-mib-13.txt,

Internet Group Management Protocol (IGMP) MIB
Internet draft draft-ietf-idr-bgp4-mibv2-04.txt,

Definitions of Managed Objects for the Fourth
Version of Border Gateway Protocol (BGP-4),
Second Version (only jnxBgpM2PrefixInPrefixes,
jnxBgpM2PrefixInPrefixesAccepted, and
jnxBgpM2PrefixInPrefixesRejected objects)
Internet draft
draft-reeder-snmpv3-usm-3desede-00.txt,
Extension to the User-Based Security Model (USM)
to Support Triple-DES EDE in Outside CBC Mode
Internet draft draft-ietf-isis-wg-mib-07.txt,

Management Information Base for IS-IS (only
isisISAdjTable, isisISAdjAreaAddrTable,
isisISAdjIPAddrTable, and isisISAdjProtSuppTable)
NOTE: Replaced with RFC 4444, IS-IS MIB in Junos

OS Release 11.3 and later.
Internet draft
draft-ietf-ppvpn-mpls-vpn-mib-04.txt, MPLS/BGP
Virtual Private Network Management Information
Base Using SMIv2 (only mplsVpnScalars,
mplsVpnVrfTable, mplsVpnPerTable, and
mplsVpnVrfRouteTargetTable)
154

Platforms
SRX
MIB/RFC
ACX
MX
EX
LowEnd
MidRange
HighEnd
Internet draft draft-ietf-ospf-ospfv3-mib-11.txt,

Management Information Base for OSPFv3
(Represented by mib-jnx-ospfv3mib.txt and
implemented under the Juniper Networks
enterprise branch {jnxExperiment}. Support for
ospfv3NbrTable only. Read only. Object names are
prefixed by jnx. For example, jnxOspfv3NbrTable,
jnxOspfv3NbrAddressType, and
jnxOspfv3NbrPriority.)
Internet draft draft-ietf-idmr-pim-mib-09.txt,

Protocol Independent Multicast (PIM) MIB
ESO Consortium MIB, which can be found at
http://www.snmp.com/eso/
NOTE: The ESO Consortium MIB has been
replaced by RFC 3826.
Internet Draft P2MP MPLS-TE MIB
(draft-ietf-mpls-p2mp-te-mib-09.txt) (read-only
access) (except
mplsTeP2mpTunnelBranchPerfTable ).
Related
Documentation
Juniper Networks Enterprise-Specific MIBs
Loading MIB Files to a Network Management System
Juniper Networks Enterprise-Specific MIBs and Supported Devices

Table 25 on page 156 lists the enterprise-specific MIBs that are supported on various
devices running Junos OS.
NOTE: In this table, a value of 1 in any of the platform columns (ACX, M, MX,
T, EX, J, and SRX) denotes that the corresponding MIB is supported on that
particular platform. A value of 0 denotes that the MIB is not supported on
the platform.
155
NOTE: This topic uses the following classification for SRX devices: Low-End
(SRX100, SRX210, SRX220, and SRX240), Mid-Range (SRX550. SRX650
and SRX1400), and High-End (SRX3400, SRX3600, SRX5600, and
SRX5800).
Table 25: Enterprise-Specific MIBs and Supported Devices

Platforms
SRX
Enterprise-Specific MIB
ACX
MX
EX
LowEnd
MidRange
HighEnd
AAA Objects MIB
http://www.juniper.net/techpubs/en_US/junos12.3/
topics/reference/mibs/mib-jnx-user-aaa.txt
Access Authentication Objects MIB
topics/reference/mibs/mib-jnx-js-auth.txt
Alarm MIB
topics/reference/mibs/mib-jnx-chassis-alarm.txt
Analyzer MIB
topics/reference/mibs/mib-jnx-analyzer.txt
Antivirus Objects MIB
topics/reference/mibs/mib-jnx-js-utm-av.txt
ATM Class-of-Service MIB
topics/reference/mibs/mib-jnx-atm-cos.txt
ATM MIB
topics/reference/mibs/mib-jnx-atm.txt
BGP4 V2 MIB
topics/reference/mibs/mib-jnx-bgpmib2.txt
156
Table 25: Enterprise-Specific MIBs and Supported Devices (continued)

Platforms
SRX
ACX
MX
EX
LowEnd
MidRange
HighEnd
Bidirectional Forwarding Detection MIB
topics/reference/mibs/mib-jnx-bfd.txt
Chassis Forwarding MIB
topics/reference/mibs/mib-jnx-chassis-fwdd.txt
Chassis MIBs
topics/reference/mibs/mib-jnx-chassis.txt
topics/reference/mibs/mib-jnx-chas-defines.txt
Chassis Cluster MIBs
topics/reference/mibs/mib-jnx-jsrpd.txt
Class-of-Service MIB
topics/reference/mibs/mib-jnx-cos.txt
Configuration Management MIB
topics/reference/mibs/mib-jnx-cfgmgmt.txt
Destination Class Usage MIB
topics/reference/mibs/mib-jnx-dcu.txt
DHCP MIB
topics/reference/mibs/mib-jnx-jdhcp.txt
DHCPv6 MIB
topics/reference/mibs/mib-jnx-jdhcpv6.txt
157

Platforms
SRX
ACX
MX
EX
LowEnd
MidRange
HighEnd
Digital Optical Monitoring MIB
topics/reference/mibs/mib-jnx-dom.txt
DNS Objects MIB
topics/reference/mibs/mib-jnx-js-dns.txt
Dynamic Flow Capture MIB
topics/reference/mibs/mib-jnx-dfc.txt
Ethernet MAC MIB
topics/reference/mibs/jnx-mac.txt
Event MIB
topics/reference/mibs/mib-jnx-event.txt
EX Series MAC Notification MIB
topics/reference/mibs/mib-jnx-ex-mac-notification.txt
EX Series SMI MIB
topics/reference/mibs/mib-jnx-ex-smi.txt
Experimental MIB
topics/reference/mibs/mib-jnx-exp.txt
Firewall MIB
topics/reference/mibs/mib-jnx-firewall.txt
158

Platforms
SRX
ACX
MX
EX
LowEnd
MidRange
HighEnd
Flow Collection Services MIB
topics/reference/mibs/mib-jnx-coll.txt
Host Resources MIB
topics/reference/mibs/mib-jnx-hostresources.txt
Interface MIB
topics/reference/mibs/mib-jnx-if-extensions.txt
IP Forward MIB
topics/reference/mibs/mib-jnx-ipforward.txt
IPsec Generic Flow Monitoring Object MIB
topics/reference/mibs/mib-jnx-ipsec-flow-mon.txt
IPsec Monitoring MIB
topics/reference/mibs/mib-jnx-ipsec-monitor-asp.txt
IPsec VPN Objects MIB
topics/reference/mibs/mib-jnx-js-ipsec-vpn.txt
IPv4 MIB
topics/reference/mibs/mib-jnx-ipv4.txt
IPv6 and ICMPv6 MIB
topics/reference/mibs/mib-jnx-ipv6.txt
159

Platforms
SRX
ACX
MX
EX
LowEnd
MidRange
HighEnd
L2ALD MIB
topics/reference/mibs/mib-jnx-l2ald.txt
L2CP MIB
topics/reference/mibs/mib-jnx-l2cp-features.txt
L2TP MIB
topics/reference/mibs/mib-jnx-l2tp.txt
LDP MIB
topics/reference/mibs/mib-jnx-ldp.txt
License MIB
topics/reference/mibs/mib-jnx-license.txt
Logical Systems MIB
topics/reference/mibs/mib-jnx-lsys-securityprofile.txt
MIMSTP MIB
topics/reference/mibs/mib-jnx-mimstp.txt
MPLS LDP MIB
topics/reference/mibs/mib-jnx-mpls-ldp.txt
MPLS MIB
topics/reference/mibs/mib-jnx-mpls.txt
160

Platforms
SRX
MX
EX
LowEnd
MidRange
HighEnd
ACX
NAT Objects MIB
topics/reference/mibs/mib-jnx-js-nat.txt
NAT Resources-Monitoring MIB
topics/reference/ mibs/mib-jnx-sp-nat.txt
OTN Interface Management MIB
topics/reference/mibs/mib-jnx-otn.txt
Packet Forwarding Engine MIB
topics/reference/mibs/mib-jnx-pfe.txt
Packet Mirror MIB
topics/reference/mibs/mib-jnx-js-packet-mirror.txt
PAE Extension MIB
topics/reference/mibs/mib-jnx-pae-extension.txt
Passive Monitoring MIB
topics/reference/mibs/mib-jnx-pmon.txt
Ping MIB
topics/reference/mibs/mib-jnx-ping.txt
Policy Objects MIB
topics/reference/mibs/mib-jnx-js-policy.txt
161

Platforms
SRX
ACX
MX
EX
LowEnd
MidRange
HighEnd
Power Supply Unit MIB
topics/reference/mibs/mib-jnx-power-supply-unit.txt
PPP MIB
http://www.juniper.net/techpubs/en_US/junos12.3/topics/
reference/mibs/mib-jnx-ppp.txt.
PPPoE MIB
reference/mibs/mib-jnx-pppoe.txt.
Psuedowire ATM MIB
http://wwwu
j. np
i ern
. et/techpubs/en_US/u
j nos123
. /topc
i s/reference/mb
i s/mb
i -n
j x-pwatmt.xt
Psuedowire TDM MIB
reference/mibs/mib-jnx-pwtdm.txt .
Real-Time Performance Monitoring MIB
topics/reference/mibs/mib-jnx-rpm.txt
Reverse-Path-Forwarding MIB
topics/reference/mibs/mib-jnx-rpf.txt
RMON Events and Alarms MIB
topics/reference/mibs/mib-jnx-rmon.txt
RSVP MIB
topics/reference/mibs/mib-jnx-rsvp.txt
162

Platforms
SRX
ACX
MX
EX
LowEnd
MidRange
HighEnd
Security Interface Extension Objects MIB
topics/reference/mibs/mib-jnx-js-if-ext.txt
Security Screening Objects MIB
topics/reference/mibs/mib-jnx-js-screening.txt
Services PIC MIB
topics/reference/mibs/mib-jnx-sp.txt
SNMP IDP MIB
topics/reference/mibs/mib-jnx-js-idp.txt.
SONET APS MIB
topics/reference/mibs/mib-jnx-sonetaps.txt
SONET/SDH Interface Management MIB
topics/reference/mibs/mib-jnx-sonet.txt
Source Class Usage MIB
topics/reference/mibs/mib-jnx-scu.txt
SPU Monitoring MIB
topics/reference/mibs/mib-jnx-js-spu-monitoring.txt
Structure of Management Information MIB
topics/reference/mibs/mib-jnx-smi.txt
163

Platforms
SRX
ACX
MX
EX
LowEnd
MidRange
HighEnd
Subscriber MIB
topics/reference/mibs/mib-jnx-subscriber.txt
System Log MIB
topics/reference/mibs/mib-jnx-syslog.txt
Traceroute MIB
topics/reference/mibs/mib-jnx-traceroute.txt
Utility MIB
topics/reference/mibs/mib-jnx-util.txt
Virtual Chassis MIB
topics/reference/mibs/mib-jnx-virtualchassis.txt
VLAN MIB
topics/reference/mibs/mib-jnx-vlan.txt
VPLS MIBs
reference/mibs/mib-jnx-vpls-generic.txt
reference/mibs/mib-jnx-vpls-ldp.txt
reference/mibs/mib-jnx-vpls-bgp.txt
VPN Certificate Objects MIB
topics/reference/mibs/mib-jnx-js-cert.txt
164

Platforms
SRX
ACX
MX
EX
LowEnd
MidRange
HighEnd
VPN MIB
topics/reference/mibs/mib-jnx-vpn.txt
Related
Documentation
Juniper Networks Enterprise-Specific MIBs
Juniper Networks Enterprise-Specific SNMP Traps
Standard SNMP MIBs Supported by Junos OS on page 140
Loading MIB Files to a Network Management System
165
166
CHAPTER 10
Operations, Administration, and

Management (OAM)
Understanding Ethernet OAM Link Fault Management for ACX Series Routers on page 167
Configuring Ethernet Local Management Interface on page 169
Ethernet Frame Delay Measurements Overview on page 177
Ethernet Frame Loss Measurement Overview on page 182
Ethernet OAM Connectivity Fault Management on page 183
Example: Configuring IEEE 802.3ah OAM Support for an Interface on page 186
Ethernet Synthetic Loss Measurement Overview on page 189
Transmission of ETH-SLM Messages on page 190
Format of ETH-SLM Messages on page 192
Guidelines for Configuring ETH-SLM on page 194
Scenarios for Configuration of ETH-SLM on page 195
Managing ETH-SLM Statistics and ETH-SLM Frame Counts on page 197
Starting a Proactive ETH-SLM Session on page 200
Starting an On-Demand ETH-SLM Session on page 204
Understanding Ethernet OAM Link Fault Management for ACX Series Routers
The Juniper Networks Junos operating system (Junos OS) for Juniper Networks ACX
Series routers allows the Ethernet interfaces on these routers to support the IEEE 802.3ah
standard for the Operation, Administration, and Maintenance (OAM) of Ethernet in access
networks. The standard defines OAM link fault management (LFM). You can configure
IEEE 802.3ah OAM LFM on point-to-point Ethernet links that are connected either directly
or through Ethernet repeaters. The IEEE 802.3ah standard meets the requirement for
OAM capabilities even as Ethernet moves from being solely an enterprise technology to
a WAN and access technology, and the standard remains backward compatible with
the existing Ethernet technology.
Ethernet OAM provides tools that network management software and network managers
can use to determine how a network of Ethernet links is functioning. Ethernet OAM should:
167
Rely only on the media access control (MAC) address or virtual LAN identifier for
troubleshooting.
Work independently of the actual Ethernet transport and function over physical Ethernet
ports or a virtual service such as a pseudowire.
Isolate faults over a flat (or single-operator) network architecture or nested or

hierarchical (or multiprovider) networks.
The following OAM LFM features are supported on ACX Series routers:
Discovery and Link Monitoring

The discovery process is triggered automatically when OAM is enabled on the interface.
The discovery process permits Ethernet interfaces to discover and monitor the peer
on the link if it also supports the IEEE 802.3ah standard. You can specify the discovery
mode used for IEEE 802.3ah OAM support. In active mode, the interface discovers and
monitors the peer on the link if the peer also supports IEEE 802.3ah OAM functionality.
In passive mode, the peer initiates the discovery process. After the discovery process
has been initiated, both sides participate in the process. The router performs link
monitoring by sending periodic OAM protocol data units (PDUs) to advertise OAM
mode, configuration, and capabilities.
You can specify the number of OAM PDUs that an interface can skip before the link
between peers is considered down.
Remote Fault Detection

Remote fault detection uses flags and events. Flags are used to convey the following:
Link Fault means a loss of signal
Dying Gasp means an unrecoverable condition such as a power failure
Critical Event means an unspecified vendor-specific critical event
You can specify the interval at which OAM PDUs are sent for fault detection.
NOTE: ACX Series routers support the receipt of dying-gasp packets, but
cannot generate them.
Remote Loopback Mode

Remote loopback mode ensures link quality between the router and a remote peer
during installation or troubleshooting. In this mode, when the interface receives a frame
that is not an OAM PDU or a PAUSE frame, it sends it back on the same interface on
which it was received. The link appears to be in the active state. You can use the returned
loopback acknowledgement to test delay, jitter, and throughput.
If a remote data terminal equipment (DTE) supports remote loopback mode, Junos
OS can place the remote DTE into loopback mode. When you place a remote DTE into
loopback mode, the interface receives the remote loopback request and puts the
interface into remote loopback mode. When the interface is in remote loopback mode,
168
Chapter 10: Operations, Administration, and Management (OAM)
all frames except OAM PDUs and PAUSE frames are looped back. No changes are
made to the frames. OAM PDUs continue to be sent and processed.
Related
Documentation
Ethernet OAM Connectivity Fault Management on page 183
Configuring Ethernet Local Management Interface
Ethernet Local Management Interface Overview on page 169
Configuring the Ethernet Local Management Interface on page 171
Example E-LMI Configuration on page 172
Ethernet Local Management Interface Overview

MX Series routers with Gigabit Ethernet (ge), 10-Gigabit Ethernet (xe), or Aggregated
Ethernet (ae) interfaces support the Ethernet Local Management Interface (E-LMI). The
E-LMI specification is available at the Metro Ethernet Forum. E-LMI procedures and
protocols are used for enabling automatic configuration of the customer edge (CE) to
support Metro Ethernet services. The E-LMI protocol also provides user-to-network
interface (UNI) and Ethernet virtual connection (EVC) status information to the CE. The
UNI and EVC information enables automatic configuration of CE operation based on the
Metro Ethernet configuration.
The E-LMI protocol operates between the CE device and the provider edge (PE) device.
It runs only on the PE-CE link and notifies the CE of connectivity status and configuration
parameters of Ethernet services available on the CE port. The scope of the E-LMI protocol
is shown in Figure 11 on page 169.
Figure 11: Scope of the E-LMI Protocol
UNI
E-LMI
Metro Ethernet Network
UNI
E-LMI
CE
g017277
CE
The E-LMI implementation on MX Series routers includes only the PE side of the E-LMI
protocol.
E-LMI interoperates with an OAM protocol, such as Connectivity Fault Management
(CFM), that runs within the provider network to collect OAM status. CFM runs at the
provider maintenance level (UNI-N to UNI-N with up MEPs at the UNI). E-LMI relies on
the CFM for end-to-end status of EVCs across CFM domains (SVLAN domain or VPLS).
169
The E-LMI protocol relays the following information:
Notification to the CE of the addition/deletion of an EVC (active, not active, or partially

active)
Notification to the CE of the availability state of a configured EVC
Communication of UNI and EVC attributes to the CE:
UNI attributes:
UNI identifier (a user-configured name for UNI)
CE-VLAN ID/EVC map type (all-to-one bundling, service multiplexing with bundling,
or no bundling)
Bandwidth profile is not supported (including the following features):
CM (coupling mode)
CF (color flag)
CIR (committed Information rate)
CBR (committed burst size)
EIR (excess information rate)
EBS (excess burst size)
EVC attributes:
EVC reference ID
EVC status type (active, not active, or partially active)
EVC type (point-to-point or multipoint-to-multipoint)
EVC ID (a user-configured name for EVC)
Bandwidth profile (not supported)
CE-VLAN ID/EVC map
E-LMI on MX Series routers supports the following EVC types:
Q-in-Q SVLAN (point-to-point or multipoint-to-multipoint)Requires an end-to-end

CFM session between UNI-Ns to monitor the EVS status.
VPLS (BGP or LDP) (point-to-point or multipoint-to-multipoint)Either VPLS

pseudowire status or end-to-end CFM sessions between UNI-Ns can be used to monitor
EVC status.
L2 circuit/L2VPN (point-to-point)Either VPLS pseudowire status or end-to-end CFM

sessions between UNI-Ns can be used to monitor EVC status.
NOTE: l2-circuit and l2vpn are not supported.
170
Configuring the Ethernet Local Management Interface

To configure E-LMI, perform the following steps:
Configuring an OAM Protocol (CFM) on page 171
Assigning the OAM Protocol to an EVC on page 171
Enabling E-LMI on an Interface and Mapping CE VLAN IDs to an EVC on page 171
Configuring an OAM Protocol (CFM)

For information on configuring the OAM protocol (CFM), see IEEE 802.1ag OAM
Connectivity Fault Management Overview on page 184.
Assigning the OAM Protocol to an EVC

To configure an EVC, you must specify a name for the EVC using the evcsevc-id statement
at the [edit protocols oam ethernet] hierarchy level. You can set the EVC protocol for
monitoring EVC statistics to cfm or vpls using the evc-protocol statement and its options
at the [edit protocols oam ethernet evcs] hierarchy level.
You can set the number of remote UNIs in the EVC using the remote-uni-count number
statement at the [edit protocols oam ethernet evcs evcs-protocol] hierarchy level. The
remote-uni-count defaults to 1. Configuring a value greater than 1 makes the EVC
multipoint-to-multipoint. If you enter a value greater than the actual number of endpoints,
the EVC status will display as partially active even if all endpoints are up. If you enter a
remote-uni-count less than the actual number of endpoints, the status will display as
active, even if all endpoints are not up.
You can configure an EVC by including the evcs statement at the [edit protocols oam
ethernet] hierarchy level:
[edit protocols oam ethernet]
evcs evc-id {
evc-protocol (cfm (management-domain name management-association name ) | vpls
(routing-instance name)) {
remote-uni-count <number>; # Optional, defaults to 1
multipoint-to-multipoint;
# Optional, defaults to point-to-point if remote-uni-count is 1
}
}
Enabling E-LMI on an Interface and Mapping CE VLAN IDs to an EVC

To configure E-LMI, include the lmi statement at the [edit protocols oam ethernet]
hierarchy level:
[edit protocols oam ethernet]
lmi {
polling-verification-timer value;
# Polling verification timer (T392), defaults to 15 seconds
status-counter count; # Status counter (N393), defaults to 4
interface name {
evc evc-id {
default-evc;
171
vlan-list [ vlan-ids ];
}
evc-map-type (all-to-one-bundling | bundling | service-multiplexing);
polling-verification-time value; # Optional, defaults to global value
status-counter count; # Optional, defaults to global value
uni-id value; # Optional, defaults to interface-name
}
}
You can set the status counter to count consecutive errors using the status-counter count
statement at the [edit protocols oam ethernet lmi] hierarchy level. The status counter is
used to determine if E-LMI is operational or not. The default value is 4.
You can set the polling-verification-timer value statement at the [edit protocols oam
ethernet lmi] hierarchy level. The default value is 15 seconds.
You can enable an interface and set its options for use with E-LMI using the interface
name statement at the [edit protocols oam ethernet lmi] hierarchy level. Only ge, xe, and
ae interfaces are supported. You can use the interface uni-id option to specify a name
for the UNI. If uni-id is not configured, it defaults to the name variable of interface name.
You can specify the CE-VLAN ID/EVC map type using the evc-map-type type interface
option. The options are all-to-one-bundling, bundling, or service-multiplexing. Service
multiplexing is with no bundling. The default type is all-to-one-bundling.
To specify the EVC that an interface uses, use the evc evc-id statement at the [edit
protocols oam ethernet lmi interface name] hierarchy level. You can specify an interface
as the default EVC interface using the default-evc statement at the [edit protocols oam
ethernet lmi interface name evc evc-id] hierarchy level. All VIDs that are not mapped to
any other EVCs are mapped to this EVC. Only one EVC can be configured as the default.
You can map a list of VLANs to an EVC using the vlan-list vlan-id-list statement at the
[edit protocols oam ethernet lmi interface name evc evc-id] hierarchy level.
Example E-LMI Configuration

Figure 12 on page 172 illustrates the E-LMI configuration for a point-to-point EVC (SVLAN)
monitored by CFM. In this example, VLANs 1 through 2048 are mapped to evc1 (SVLAN
100) and 2049 through 4096 are mapped to evc2 (SVLAN 200). Two CFM sessions are
created to monitor these EVCs.
Figure 12: E-LMI Configuration for a Point-to-Point EVC (SVLAN)

Monitored by CFM
CE1
ge-1/1/1
PE1
ge-1/1/2
ge-2/2/2
PE2
ge-2/2/1
CE2
CFM sessions
UNI-C
172
E-LMI
UNI-N
CFM up MEP
Ethernet Virtual Connections
UNI-N
E-LMI
UNI-C
g017278
CFM up MEP
Configuring PE1
[edit]
interfaces {
ge-1/1/1 {
unit 0 {
family bridge {
interface-mode trunk;
vlan-id-list 1-2048;
}
}
unit 1 {
family bridge {
}
}
}
ge-1/1/2 {
unit 0 {
vlan-id 100;
family bridge {
inner-vlan-id-list 1-2048;
}
}
unit 1 {
vlan-id 200;
family bridge {
}
}
}
}
protocols {
oam {
ethernet {
connectivity-fault-management {
maintenance-domain md {
level 0;
maintenance-association 1 {
name-format vlan;
mep 1 {
direction up;
interface ge-1/1/1.0 vlan 1;
}
}
name-format vlan;
mep 1 {
direction up;
}
}
173
}
}
evcs {
evc1 {
evc-protocol cfm management-domain md management-association 1;
remote-uni-count 1;
}
evc2 {
remote-uni-count 1;
}
}
lmi {
interface ge-1/1/1 {
evc evc1 {
vlan-list 1-2048;
}
evc evc2 {
vlan-list 2049-4096;
}
evc-map-type bundling;
uni-id uni-ce1;
}
}
}
}
}
Configuring PE2
[edit]
interfaces {
ge-2/2/1 {
unit 0 {
family bridge {
}
}
unit 1 {
family bridge {
}
}
}
ge-2/2/2 {
unit 0 {
vlan-id 100;
family bridge {
}
}
unit 1 {
vlan-id 200;
174
family bridge {
}
}
}
}
protocols {
oam {
ethernet {
maintenance-domain md {
level 0;
name-format vlan;
mep 1 {
direction up;
}
}
name-format vlan;
mep 1 {
direction up;
}
}
}
}
evcs {
evc1 {
remote-uni-count 1;
}
evc2 {
uni-count 2;
}
}
lmi {
evc evc1 {
vlan-list 1-2048;
}
evc evc2 {
vlan-list 2049-4095;
}
evc-map-type bundling;
uni-id uni-ce2;
}
}
}
}
}
175
Configuring Two UNIs Sharing the Same EVC

[edit protocols]
oam {
ethernet {
connectivity-fault-management { ...}
evcs {
evc1 {
remote-uni-count 1;
}
}
lmi {
evc evc1 {
vlan-list 0-4095;
}
evc-map-type all-to-one-bundling;
uni-id uni-ce1;
}
evc evc1 {
vlan-list 0-4095;
}
evc-map-type all-to-one-bundling;
uni-id uni-ce2;
}
}
}
}
Related
Documentation
176
connectivity-fault-management
Creating the Maintenance Domain
Configuring Maintenance Intermediate Points
Creating a Maintenance Association
Continuity Check Protocol
Configuring Linktrace Protocol in CFM
Configuring Port Status TLV and Interface Status TLV
Configuring MAC Flush Message Processing in CET Mode
Configuring M120 and MX Series Routers for CCC Encapsulated Packets
Configuring Rate Limiting of Ethernet OAM Messages
Configuring 802.1ag Ethernet OAM for VPLS
Ethernet Frame Delay Measurements Overview
ITU-T Y.1731 Frame Delay Measurement Feature on page 177
One-Way Ethernet Frame Delay Measurement on page 178
Two-Way Ethernet Frame Delay Measurement on page 180
Choosing Between One-Way and Two-Way ETH-DM on page 181
Restrictions for Ethernet Frame Delay Measurement on page 181
ITU-T Y.1731 Frame Delay Measurement Feature

The IEEE 802.3-2005 standard for Ethernet Operations, Administration, and Maintenance
(OAM) defines a set of link fault management mechanisms to detect and report link
faults on a single point-to-point Ethernet LAN.
Junos OS supports key OAM standards that provide for automated end-to-end
management and monitoring of Ethernet service by service providers:
IEEE Standard 802.1ag, also known as Connectivity Fault Management (CFM).
ITU-T Recommendation Y.1731, which uses different terminology than IEEE 802.1ag and
defines Ethernet service OAM features for fault monitoring, diagnostics, and
performance monitoring.
These capabilities allow operators to offer binding service-level agreements (SLAs) and
generate new revenues from rate- and performance-guaranteed service packages that
are tailored to the specific needs of their customers.
Ethernet CFM
The IEEE 802.1ag standard for connectivity fault management (CFM) defines mechanisms
to provide for end-to-end Ethernet service assurance over any path, whether a single link
or multiple links spanning networks composed of multiple LANs.
For Ethernet interfaces on M320, MX Series, and T Series routers, Junos OS supports the
following key elements of the Ethernet CFM standard:
Fault monitoring using the IEEE 802.1ag Ethernet OAM Continuity Check protocol
Path discovery and fault verification using the IEEE 802.1ag Ethernet OAM Linktrace
protocol
Fault isolation using the IEEE 802.1ag Ethernet OAM Loopback protocol
In a CFM environment, network entities such as network operators, service providers, and
customers may be part of different administrative domains. Each administrative domain
is mapped into one maintenance domain. Maintenance domains are configured with
different level values to keep them separate. Each domain provides enough information
for the entities to perform their own management and end-to-end monitoring, and still
avoid security breaches.
177
Figure 13 on page 178 shows the relationships among the customer, provider, and operator
Ethernet bridges, maintenance domains, maintenance association end points (MEPs),
and maintenance intermediate points (MIPs).
Figure 13: Relationship of MEPs, MIPs, and Maintenance Domain Levels
NOTE: Maintenance intermediate points (MIP) are not supported on the ACX
Series routers.
Ethernet Frame Delay Measurement

Two key objectives of OAM functionality are to measure quality-of-service attributes
such as frame delay and frame delay variation (also known as frame jitter). Such
measurements can enable you to identify network problems before customers are
impacted by network defects.
Junos OS supports Ethernet frame delay measurement between MEPs configured on
Ethernet physical or logical interfaces on MX Series routers. Ethernet frame delay
measurement provides fine control to operators for triggering delay measurement on a
given service and can be used to monitor SLAs. Ethernet frame delay measurement also
collects other useful information, such as worst and best case delays, average delay,
and average delay variation. The Junos OS implementation of Ethernet frame delay
measurement (ETH-DM) is fully compliant with the ITU-T Recommendation Y.1731, OAM
Functions and Mechanisms for Ethernet-based Networks. The recommendation defines
OAM mechanisms for operating and maintaining the network at the Ethernet service
layer, which is called the "ETH layer" in ITU-T terminology.
MX Series routers with modular port concentrators (MPCs) and 10-Gigabit Ethernet
MPCs with SFP+ support ITU-T Y.1731 functionality on VPLS for frame-delay and
delay-variation.
One-Way Ethernet Frame Delay Measurement

In one-way ETH-DM mode, a series of frame delay and frame delay variation values are
calculated based on the time elapsed between the time a measurement frame is sent
from the initiator MEP at one router and the time when the frame is received at the receiver
MEP at the other router.
178
1DM Transmission
When you start a one-way frame delay measurement, the router sends 1DM
framesframes that carry the protocol data unit (PDU) for a one-way delay
measurementfrom the initiator MEP to the receiver MEP at the rate and for the number
of frames you specify. The router marks each 1DM frame as drop-ineligible and inserts a
timestamp of the transmission time into the frame.
1DM Reception
When an MEP receives a 1DM frame, the router that contains the receiver MEP measures
the one-way delay for that frame (the difference between the time the frame was received
and the timestamp contained in the frame itself) and the delay variation (the difference
between the current and previous delay values).
One-Way ETH-DM Statistics

The router that contains the receiver MEP stores each set of one-way delay statistics in
the ETH-DM database. The ETH-DM database collects up to 100 sets of statistics for
any given CFM session (pair of peer MEPs). You can access these statistics at any time
by displaying the ETH-DM database contents.
One-Way ETH-DM Frame Counts

Each router counts the number of one-way ETH-DM frames sent and received:
For an initiator MEP, the router counts the number of 1DM frames sent.
For a receiver MEP, the router counts the number of valid 1DM frames received and the
number of invalid 1DM frames received.
Each router stores ETH-DM frame counts in the CFM database. The CFM database stores
CFM session statistics and, for interfaces that support ETH-DM, any ETH-DM frame
counts. You can access the frame counts at any time by displaying CFM database
information for Ethernet interfaces assigned to MEPs or for MEPs in CFM sessions.
Synchronization of System Clocks

The accuracy of one-way delay calculations depends on close synchronization of the
system clocks at the initiator MEP and receiver MEP.
The accuracy of one-way delay variation is not dependent on system clock
synchronization. Because delay variation is simply the difference between consecutive
one-way delay values, the out-of-phase period is eliminated from the frame jitter values.
NOTE: For a given one-way Ethernet frame delay measurement, frame delay
and frame delay variation values are available only on the router that contains
the receiver MEP.
179
Two-Way Ethernet Frame Delay Measurement

In two-way ETH-DM mode, frame delay and frame delay variation values are based on
the time difference between when the initiator MEP transmits a request frame and
receives a reply frame from the responder MEP, subtracting the time elapsed at the
responder MEP.
DMM Transmission
When you start a two-way frame delay measurement, the router sends delay
measurement message (DMM) frames frames that carry the PDU for a two-way
ETH-DM requestfrom the initiator MEP to the responder MEP at the rate and for the
number of frames you specify. The router marks each DMM frame as drop-ineligible and
inserts a timestamp of the transmission time into the frame.
DMR Transmission
When an MEP receives a DMM frame, the responder MEP responds with a delay
measurement reply (DMR) frame, which carries ETH-DM reply information and a copy
of the timestamp contained in the DMM frame.
DMR Reception
When an MEP receives a valid DMR, the router that contains the MEP measures the
two-way delay for that frame based on the following sequence of timestamps:
1.
TI
TxDMM
2. TR
RxDMM
3. TR
TxDMR
4. TI
RxDMR
A two-way frame delay is calculated as follows:

[TI
RxDMR
TI
] [TR
TxDMM
TxDMR
TR
RxDMM
The calculation show that frame delay is the difference between the time at which the
initiator MEP sends a DMM frame and the time at which the initiator MEP receives the
associated DMR frame from the responder MEP, minus the time elapsed at the responder
MEP.
The delay variation is the difference between the current and previous delay values.
Two-Way ETH-DM Statistics

The router that contains the initiator MEP stores each set of two-way delay statistics in
the ETH-DM database. The ETH-DM database collects up to 100 sets of statistics for
any given CFM session (pair of peer MEPs). You can access these statistics at any time
by displaying the ETH-DM database contents.
180
Two-Way ETH-DM Frame Counts

Each router counts the number of two-way ETH-DM frames sent and received:
For an initiator MEP, the router counts the number DMM frames transmitted, the number
of valid DMR frames received, and the number of invalid DMR frames received.
For a responder MEP, the router counts the number of DMR frames sent.
Each router stores ETH-DM frame counts in the CFM database. The CFM database stores
CFM session statistics and, for interfaces that support ETH-DM, any ETH-DM frame
counts. You can access the frame counts at any time by displaying CFM database
information for Ethernet interfaces assigned to MEPs or for MEPs in CFM sessions.
NOTE: For a given two-way Ethernet frame delay measurement, frame delay
and frame delay variation values are available only at the router that contains
the initiator MEP.
Choosing Between One-Way and Two-Way ETH-DM

One-way frame delay measurement requires that the system clocks at the initiator MEP
and receiver MEP are closely synchronized. Two-way frame delay measurement does
not require synchronization of the two systems. If it is not practical for the clocks to be
synchronized, two-way frame delay measurements are more accurate.
When two systems are physically close to each other, their one-way delay values are
very high compared to their two-way delay values. One-way delay measurement requires
that the timing for the two systems be synchronized at a very granular level, and MX
Series routers currently do not support this granular synchronization.
Restrictions for Ethernet Frame Delay Measurement

The following restrictions apply to the Ethernet frame delay measurement feature:
The ETH-DM feature is not supported on aggregated Ethernet interfaces or

label-switched interface. (LSI) pseudowires.
Hardware-assisted timestamping for ETH-DM frames in the reception path is only

supported for MEP interfaces on Enhanced DPCs and Enhanced Queuing DPCs in MX
Series routers. For information about hardware-assisted timestamping, see Guidelines
for Configuring Routers to Support an ETH-DM Session and Enabling the
Hardware-Assisted Timestamping Option.
Ethernet frame delay measurements can be triggered only when the distributed periodic
packet management daemon (ppm) is enabled. For more information about this
limitation, see Guidelines for Configuring Routers to Support an ETH-DM Session and
Ensuring That Distributed ppm Is Not Disabled.
You can monitor only one session at a time to the same remote MEP or MAC address.
For more information about starting an ETH-DM session, see Starting an ETH-DM
Session.
181
Related
Documentation
ETH-DM statistics are collected at only one of the two peer routers in the ETH-DM
session. For a one-way ETH-DM session, you can display frame ETH-DM statistics at
the receiver MEP only, using ETH-DM-specific show commands. For a two-way ETH-DM
session, you can display frame delay statistics at the initiator MEP only, using the same
ETH-DM-specific show commands. For more information, see Managing ETH-DM
Statistics and ETH-DM Frame Counts.
ETH-DM frame counts are collected at both MEPs and are stored in the respective
CFM databases.
If graceful Routing Engine switchover (GRES) occurs, any collected ETH-DM statistics
are lost, and ETH-DM frame counts are reset to zeroes. Therefore, the collection of
ETH-DM statistics and ETH-DM frame counters has to be restarted, after the switchover
is complete. GRES enables a router with dual Routing Engines to switch from a master
Routing Engine to a backup Routing Engine without interruption to packet forwarding.
For more information, see the Junos OS High Availability Configuration Guide.
Accuracy of frame delay statistics is compromised when the system is changing (such
as from reconfiguration). We recommend performing Ethernet frame delay
measurements on a stable system.
Ethernet Frame Loss Measurement Overview on page 182
Example: One-Way Ethernet Frame Delay Measurement
Guidelines for Configuring Routers to Support an ETH-DM Session
Guidelines for Starting an ETH-DM Session
Guidelines for Managing ETH-DM Statistics and ETH-DM Frame Counts
On-Demand Mode
Proactive Mode
Ethernet Frame Loss Measurement Overview

The key objectives of the OAM functionality are to measure quality-of-service attributes
such as frame delay, frame delay variation (also known as frame jitter), and frame loss.
Such measurements enable you to identify network problems before customers are
impacted by network defects. For more information about Ethernet frame delay
measurement, see Ethernet Frame Delay Measurements Overview on page 177.
Junos OS supports Ethernet frame loss measurement (ETH-LM) between maintenance
association end points (MEPs) configured on Ethernet physical or logical interfaces on
MX Series routers and is presently supported only for VPWS service. ETH-LM is used by
operators to collect counter values applicable for ingress and egress service frames.
These counters maintain a count of transmitted and received data frames between a
pair of MEPs. Ethernet frame loss measurement is performed by sending frames with
ETH-LM information to a peer MEP and similarly receiving frames with ETH-LM information
182
from the peer MEP. This type of frame loss measurement is also known as single-ended
Ethernet loss measurement.
ETH-LM supports the following frame loss measurements:
Near-end frame loss measurementMeasurement of frame loss associated with

ingress data frames.
Far-end frame loss measurementMeasurement of frame loss associated with egress

data frames.
NOTE: The proactive and dual-ended loss measurement functionality of

ITU-T Y1731 is not supported on the ACX Series routers.
The Junos OS implementation of Ethernet frame delay measurement (ETH-DM) is fully

compliant with the ITU-T Recommendation Y.1731, as described in OAM Functions and
Mechanisms for Ethernet-Based Networks. The recommendation defines OAM mechanisms
for operating and maintaining the network at the Ethernet service layer, which is called
the "ETH layer" in ITU-T terminology.
Related
Documentation
Managing Continuity Measurement Statistics
On-Demand Mode
Proactive Mode
Ethernet OAM Connectivity Fault Management

The most complete connectivity fault management (CFM) is defined in IEEE 802.1ag.
This topic emphasizes the use of CFM in a Metro Ethernet environment.
The major features of CFM are:
Fault monitoring using the continuity check protocol. This is a neighbor discovery and
health check protocol which discovers and maintains adjacencies at the VLAN or link
level.
Path discovery and fault verification using the linktrace protocol. Similar to IP traceroute,
this protocol maps the path taken to a destination MAC address through one or more
bridged networks between the source and destination.
Fault isolation using the loopback protocol. Similar to IP ping, this protocol works with
the continuity check protocol during troubleshooting.
CFM partitions the service network into various administrative domains. For example,
operators, providers, and customers may be part of different administrative domains.
Each administrative domain is mapped into one maintenance domain providing enough
information to perform its own management, thus avoiding security breaches and making
end-to-end monitoring possible. Each maintenance domain is associated with a
183
maintenance domain level from 0 through 7. Level allocation is based on the network
hierarchy, where outermost domains are assigned a higher level than the innermost
domains. Customer end points have to highest maintenance domain level. In a CFM
maintenance domain, each service instance is called a maintenance association. A
maintenance association can be thought as a full mesh of maintenance endpoints (MEPs)
having similar characteristics. MEPs are active CFM entities generating and responding
to CFM protocol messages. There is also a maintenance intermediate point (MIP), which
is a CFM entity similar to the MEP, but more passive (MIPs only respond to CFM messages).
MEPs can be up MEPs or down MEPs. A link can connect a MEP at level 5 to a MEP at
level 7. The interface at level 5 is an up MEP (because the other end of the link is at MEP
level 7) and the interface at level 7 is a down MEP (because the other end of the link is
at MEP level 5).
In a Metro Ethernet network, CFM is commonly used at two levels:
By the service provider to check the connectivity among its provider edge (PE) routers
By the customer to check the connectivity among its customer edge (CE) routers
NOTE: The configured customer CFM level must be greater than service
provider CFM level.
In many Metro Ethernet networks, CFM is used to monitor connectivity over a VPLS and
bridge network.
Related
Documentation
Ethernet OAM
Ethernet Operations, Administration, and Maintenance
Example: Configuring Ethernet CFM over VPLS
Example: Configuring Ethernet CFM on Bridge Connections
Example: Configuring Ethernet CFM on Physical Interfaces
IEEE 802.1ag OAM Connectivity Fault Management Overview

Ethernet interfaces on M7i and M10i routers with the Enhanced CFEB (CFEB-E) and on
M120, M320, MX Series, T Series, and PTX Series routers support the IEEE 802.1ag standard
for Operation, Administration, and Management (OAM). The IEEE 802.1ag specification
provides for Ethernet connectivity fault management (CFM). The goal of CFM is to monitor
an Ethernet network that may comprise one or more service instances. Junos OS supports
IEEE 802.1ag connectivity fault management.
In Junos OS Release 9.3 and later, CFM also supports aggregated Ethernet interfaces.
On interfaces configured on Modular Port Concentrators (MPCs) and Modular Interface
Cards (MICs) on MX Series routers, CFM is not supported on untagged aggregated Ethernet
member links. MPCs and MICs do support CFM on untagged and tagged aggregated
Ethernet logical interfaces .
184
CFM does not support Multichassis Link Aggregation (MC-LAG). Do not configure the
mc-ae statement when you configure CFM.
On T Series routers, CFM is not supported on interfaces configured with CCC
encapsulation. If you configure CFM, the system displays the following message: MEPs
cannot be configured on ccc interface on this platform.
Network entities such as operators, providers, and customers may be part of different
administrative domains. Each administrative domain is mapped into one maintenance
domain. Maintenance domains are configured with different level values to keep them
separate. Each domain provides enough information for the entities to perform their own
management, perform end-to-end monitoring, and still avoid security breaches.
NOTE: As a requirement for Ethernet OAM 802.1ag to work, distributed

periodic packet management (PPM) runs on the Routing Engine and Packet
Forwarding Engine by default. You can only disable PPM on the Packet
Forwarding Engine. To disable PPM on the PFE, include the ppm
no-delegate-processing statement at the [edit routing-options ppm] hierarchy
level.
IEEE 802.1ag OAM supports graceful Routing Engine switchover (GRES). IEEE 802.1ag
OAM is supported on untagged, single tagged, and stacked VLAN interfaces.
Connectivity Fault Management Key Elements on page 185
Connectivity Fault Management Key Elements

Figure 14 on page 185 shows the relationships among the customer, provider, and operator
Ethernet bridges, maintenance domains, maintenance association end points (MEPs),
and maintenance intermediate points (MIPs).
Figure 14: Relationship Among MEPs, MIPs, and Maintenance Domain

Levels
NOTE: Maintenance intermediate points (MIP) are not supported on the ACX
Series routers.
185
A maintenance association is a set of MEPs configured with the same maintenance

association identifier and maintenance domain level. Figure 15 on page 186 shows the
hierarchical relationships between the Ethernet bridge, maintenance domains,
maintenance associations, and MEPs.
Figure 15: Relationship Among Bridges, Maintenance Domains,

Maintenance Associations, and MEPs
Related
Documentation
connectivity-fault-management
Creating the Maintenance Domain
Configuring Maintenance Intermediate Points
Creating a Maintenance Association
Continuity Check Protocol
Configuring Linktrace Protocol in CFM
Configuring Port Status TLV and Interface Status TLV
Configuring MAC Flush Message Processing in CET Mode
Configuring M120 and MX Series Routers for CCC Encapsulated Packets
Configuring Rate Limiting of Ethernet OAM Messages
Configuring 802.1ag Ethernet OAM for VPLS
Example: Configuring IEEE 802.3ah OAM Support for an Interface

Junos OS for ACX Series routers allows the Ethernet interfaces on these routers to support
the IEEE 802.3ah standard for the Operation, Administration, and Maintenance (OAM)
of Ethernet in access networks. The standard defines OAM link fault management (LFM).
You can configure IEEE 802.3ah OAM LFM on point-to-point Ethernet links that are
connected either directly or through Ethernet repeaters.
186
This example describes how to enable and configure OAM on a Gigabit Ethernet interface.
Requirements
Junos OS Release 12.2 or later for ACX Series routers.
An ACX1000 or ACX2000 router.
Overview and Topology

In this example, you configure a 10-Gigabit Ethernet interface on an ACX Series router
with 802.3ah OAM support, which includes: link discovery, protocol data units (PDUs),
remote loopback, negotiation, and event thresholds.
Configuring IEEE 802.3ah OAM on an ACX Series Router

CLI Quick
Configuration
To quickly configure IEEE 802.3ah Ethernet OAM, copy the following commands and
paste them into the CLI:
edit
edit protocols oam ethernet link-fault-management
set interface xe-0/0/0 link-discovery active pdu-interval 800 pdu-threshold 4
remote-loopback negotiation-options allow-remote-loopback
set interface xe-0/0/0 event-thresholds frame-error 30 frame-period 50
frame-period-summary 40 symbol-period 20
Step-by-Step
Procedure
To configure IEEE 802.3ah OAM support on an interface:

1.
Enable IEEE 802.3ah OAM support on an interface:

[edit protocols oam ethernet link-fault-management]
user@router1# set interface (OAM Link-Fault Management) xe-0/0/0

2.
Specify that the interface initiates the discovery process by setting the link discovery
mode to active:
user@router# set interface xe-0/0/0 link-discovery active
3.
Set the periodic OAM PDU-sending interval (in milliseconds) to 800:

user@router# set interface xe-0/0/0 pdu-interval 800
4.
Define the number of OAM PDUs to miss before an error is logged as 4:

user@router# set interface xe-0/0/0 pdu-threshold 4
5.
Configure the remote interface into loopback mode so that all frames except OAM
PDUs are looped back without any changes:
user@router# set interface xe-0/0/0 remote-loopback
6.
Configure remote loopback support for the local interface:

user@router# set interface xe-0/0/0 negotiation-options allow-remote-loopback
187
Set the threshold count for sending frame error events to 30:
7.
user@router# set interface xe-0/0/0 event-thresholds frame-error 30

Set the threshold count for sending frame period error events to 50:
8.
user@router# set interface xe-0/0/0 event-thresholds frame-period 50

Configure the threshold count for sending frame period summary error events to
40:
9.
user@router# set interface xe-0/0/0 event-thresholds frame-period-summary

40
10.
Set the threshold count for sending symbol period events to 20:
user@router# set interface xe-0/0/0 event-thresholds symbol-period 20
Results
Check the results of the configuration:

[edit]
user@router# show
[edit]
protocols {
oam {
ethernet {
link-fault-management {
interface xe-0/0/0 {
link-discovery active;
pdu-interval 800;
pdu-threshold 4;
remote-loopback;
negotiation-options {
allow-remote-loopback;
}
event-thresholds {
frame-error 30;
frame-period 50;
frame-period-summary 40;
symbol-period 20;
}
}
}
}
}
}
Related
Documentation
188
link-fault-management
IEEE 802.3ah OAM Link-Fault Management Overview
Configuring IEEE 802.3ah OAM Link-Fault Management
Enabling IEEE 802.3ah OAM Support
Ethernet Synthetic Loss Measurement Overview

Ethernet synthetic loss measurement (ETH-SLM) is an application that enables the
calculation of frame loss by using synthetic frames instead of data traffic. This mechanism
can be considered as a statistical sample to approximate the frame loss ratio of data
traffic. Each maintenance association end point (MEP) performs frame loss
measurements, which contribute to unavailable time.
A near-end frame loss specifies frame loss associated with ingress data frames and a
far-end frame loss specifies frame loss associated with egress data frames. Both near-end
and far-end frame loss measurements contribute to near-end severely errored seconds
and far-end severely errored seconds that are used in combination to determine
unavailable time. ETH-SLM is performed using synthetic loss message (SLM) and
synthetic loss reply (SLR) frames. ETH-SLM facilitates each MEP to perform near-end
and far-end synthetic frame loss measurements by using synthetic frames because a
bidirectional service is defined as unavailable if either of the two directions is determined
to be unavailable.
There are the two types of frame loss measurement, defined by the ITU-T Y.1731 standards,
ETH-LM and ETH-SLM. Junos OS supports only single-ended ETH-SLM. In single-ended
ETH-SLM, each MEP sends frames with the ETH-SLM request information to its peer
MEP and receives frames with ETH-SLM reply information from its peer MEP to perform
synthetic loss measurements. Single-ended ETH-SLM is used for proactive or on-demand
OAM to perform synthetic loss measurements applicable to point-to-point Ethernet
connection. This method allows a MEP to initiate and report far-end and near-end loss
measurements associated with a pair of MEPs that are part of the same maintenance
entity group (MEG).
Single-ended ETH-SLM is used to perform on-demand or proactive tests by initiating a
finite amount of ETH-SLM frames to one or multiple MEP peers and receiving the ETH-SLM
reply from the peers. The ETH-SLM frames contain the ETH-SLM information that is
used to measure and report both near-end and far-end synthetic loss measurements.
Service-level agreement (SLA) measurement is the process of monitoring the bandwidth,
delay, delay variation (jitter), continuity, and availability of a service. It enables you to
identify network problems before customers are impacted by network defects. In proactive
mode, SLA measurements are triggered by an iterator application. An iterator is designed
to periodically transmit SLA measurement packets in the form of ITU-Y.1731-compliant
frames for synthetic frame loss measurement . This mode differs from on-demand SLA
measurement, which is user initiated. In on-demand mode, the measurements are
triggered by the user through the CLI. When the user triggers the ETH-SLM through the
CLI, the SLM request that is generated is as per the frame formats specified by the ITU-T
Y.1731 standard.
Related
Documentation
189
Troubleshooting Failures with ETH-SLM
Transmission of ETH-SLM Messages

The ETH-SLM functionality can process multiple synthetic loss message (SLM) requests
simultaneously between a pair of MEPs. The session can be a proactive or an on-demand
SLM session. Each SLM request is identified uniquely by a test ID.
A MEP can send SLM requests or respond to SLM requests. A response to an SLM request
is called a synthetic loss reply (SLR). After a MEP determines an SLM request by using
the test ID, the MEP calculates the far-end and near-end frame loss on the basis of the
information in the SLM message or the SLM protocol data unit (PDU).
A MEP maintains the following local counters for each test ID and for each peer MEP
being monitored in a maintenance entity for which loss measurements are to be
performed:
TxFClNumber of synthetic frames transmitted toward the peer MEP for a test ID. A
source MEP increments this number for successive transmission of synthetic frames
with ETH-SLM request information while a destination or receiving MEP increments
this value for successive transmission of synthetic frames with the SLR information.
RxFClNumber of synthetic frames received from the peer MEP for a test ID. A source
MEP increments this number for successive reception of synthetic frames with SLR
information while a destination or receiving MEP increments it for successive reception
of synthetic frames with ETH-SLM request information.
The following sections describe the phases of processing of SLM PDUs to determine
synthetic frame loss:
Initiation and Transmission of SLM Requests

A MEP periodically transmits an SLM request with the OpCode field set as 55. The MEP
generates a unique Test ID for the session, adds the source MEP ID, and initializes the
local counters for the session before SLM initiation. For each SLM PDU transmitted for
the session (test ID), the local counter TxFCl is sent in the packet.
No synchronization is required of the test ID value between initiating and responding
MEPs because the test ID is configured at the initiating MEP, and the responding MEP
uses the test ID it receives from the initiating MEP. Because ETH-SLM is a sampling
technique, it is less precise than counting the service frames. Also, the accuracy of
measurement depends on the number of SLM frames used or the period for transmitting
SLM frames.
190
Reception of SLMs and Transmission of SLRs

After the destination MEP receives a valid SLM frame from the source MEP, an SLR frame
is generated and transmitted to the requesting or source MEP. The SLR frame is valid if
the MEG level and the destination MAC address match the receiving MEPs MAC address.
All the fields in the SLM PDUs are copied from the SLM request except for the following
fields:
The source MAC address is copied to the destination MAC address and the source
address contains the MEPs MAC address.
The value of the OpCode field is changed from SLM to SLR (54).
The responder MEP ID is populated with the MEPs MEP ID.
TxFCb is saved with the value of the local counter RxFCl at the time of SLR frame
transmission.
An SLR frame is generated every time an SLM frame is received; therefore, RxFCl in
the responder is equal to the number of SLM frames received and also equal to the
number of SLR frames sent. At the responder or receiving MEP, RxFCl equals TxFCl.
Reception of SLRs
After an SLM frame (with a given TxFCf value) is transmitted, a MEP expects to receive
a corresponding SLR frame (carrying the same TxTCf value) within the timeout value
from its peer MEP. SLR frames that are received after the timeout value (5 seconds) are
discarded. With the information contained in SLR frames, a MEP determines the frame
loss for the specified measurement period. The measurement period is a time interval
during which the number of SLM frames transmitted is statistically adequate to make a
measurement at a given accuracy. A MEP uses the following values to determine near-end
and far-end frame loss during the measurement period:
Last received SLR frame's TxFCf and TxFCb values and the local counter RxFCl value
at the end of the measurement period. These values are represented as TxFCf[tc],
TxFCb[tc], and RxFCl[tc], where tc is the end time of the measurement period.
SLR frame's TxFCf and TxFCb values of the first received SLR frame after the test
starts and local counter RxFCl at the beginning of the measurement period. These
values are represented as TxFCf[tp], TxFCb[tp], and RxFCl[tp], where tp is the start
time of the measurement period.
For each SLR packet that is received, the local RxFCl counter is incremented at the sending
or source MEP.
Computation of Frame Loss

Synthetic frame loss is calculated at the end of the measurement period on the basis of
the value of the local counters and the information from the last frame received. The
last received frames contains the TxFCf and TxFCb values. The local counter contains
the RxFCl value. Using these values, frame loss is determined using the following formula:
Frame loss (far-end) = TxFCf TxFCb
191
Frame loss (near-end) = TxFCb RxFCl

Related
Documentation
Format of ETH-SLM Messages

Synthetic loss messages (SLMs) support single-ended Ethernet synthetic loss
measurement (ETH-SLM) requests. This topic contains the following sections that
describe the formats of the SLM protocol data units (PDUs), SLR PDUs, and the data
iterator type length value (TLV).
SLM PDU Format

The SLM PDU format is used by a MEP to transmit SLM information. The following
components are contained in SLM PDUs:
Source MEP IDSource MEP ID is a 2-octet field where the last 13 least significant bits
are used to identify the MEP transmitting the SLM frame. MEP ID is unique within the
MEG.
Test IDTest ID is a 4-octet field set by the transmitting MEP and is used to identify a
test when multiple tests run simultaneously between MEPs (including both concurrent
on-demand and proactive tests).
TxFCfTxFCf is a 4-octet field that carries the number of SLM frames transmitted by
the MEP toward its peer MEP.
The following are the fields in an SLM PDU:
192
MEG LevelConfigured maintenance domain level in the range 07.
Version0.
OpCodeIdentifies an OAM PDU type. For SLM, it is 55.
FlagsSet to all zeros.
TLV Offset16.
Source MEP IDA 2-octet field used to identify the MEP transmitting the SLM frame.
In this 2-octet field, the last 13 least significant bits are used to identify the MEP
transmitting the SLM frame. MEP ID is unique within the MEG.
RESVReserved fields are set to all zeros.
Test IDA 4-octet field set by the transmitting MEP and used to identify a test when
multiple tests run simultaneously between MEPs (including both concurrent on-demand
and proactive tests).
TxFCfA 4-octet field that carries the number of SLM frames transmitted by the MEP
toward its peer MEP.
Optional TLVA data TLV may be included in any SLM transmitted. For the purpose
of ETH-SLM, the value part of data TLV is unspecified.
End TLVAll zeros octet value.
SLR PDU Format

The synthetic loss reply (SLR) PDU format is used by a MEP to transmit SLR information.
The following are the fields in an SLR PDU:
MEG LevelA 3-bit field the value of which is copied from the last received SLM PDU.
VersionA 5-bit field the value of which is copied from the last received SLM PDU.
OpCodeIdentifies an OAM PDU type. For SLR, it is set as 54.
FlagsA 1-octet field copied from the SLM PDU.
TLV OffsetA 1-octet field copied from the SLM PDU.
Source MEP IDA 2-octet field copied from the SLM PDU.
Responder MEP IDA 2-octet field used to identify the MEP transmitting the SLR
frame.
Test IDA 4-octet field copied from the SLM PDU.
TxFCfA 4-octet field copied from the SLM PDU.
TxFCbA 4 octet field. This value represents the number of SLR frames transmitted
for this test ID.
Optional TLVThe value is copied from the SLM PDU, if present.
End TLVA 1-octet field copied from the SLM PDU.
Data Iterator TLV Format

The data iterator TLV specifies the data TLV portion of the Y.1731 data frame. The MEP
uses a data TLV when the MEP is configured to measure delay and delay variation for
different frame sizes. The following are the fields in a data TLV:
TypeIdentifies the TLV type; value for this TLV type is Data (3).
LengthIdentifies the size, in octets, of the Value field containing the data pattern.
The maximum value of the Length field is 1440.
193
Related
Documentation
Data patternAn n-octet (n denotes length) arbitrary bit pattern. The receiver ignores
it.
Guidelines for Configuring ETH-SLM

Keep the following points in mind when you configure the ETH-SLM functionality:
The monitoring application for Ethernet OAM is initiated in the master Routing Engine.
When a stateful switchover process occurs, the monitoring application is disabled. For
on-demand ETH-SLM, graceful Routing Engine switchover (GRES) support is not
applicable. For proactive ETH-SLM, the service-level agreement (SLA) iterators are
restored during a stateful switchover process. If the adjacencies do not time out, the
ETH-SLM statistics are preserved and proactive ETH-SLM supports GRES.
ETH-SLM is initiated only when the MEP session is up. Unified in-service software
upgrade (ISSU) support for ETH-SLM depends on the unified ISSU support for CFM.
For CFM, unified ISSU is supported using the loss threshold TLV to avoid CFM
connectivity loss during the upgrade. The receiving or the destination MEP increases
the threshold time during the termination of sessions. If you start a unified ISSU
operation when on-demand ETH-SLM is in progress, the SLM request and reply
messages are lost at the local Packet Forwarding Engine.
When an on-demand ETH-SLM is requested, if the local source MEP undergoes a
unified ISSU, a message is displayed stating that the MEP is undergoing a unified ISSU.
If the remote MEP is undergoing a unified ISSU (detected through the loss threshold
TLV), a message is displayed stating that the remote MEP is undergoing a unified ISSU.
Also, if it is not possible to identify whether unified ISSU is in progress on a remote MEP,
the SLM packets are lost at the system where unified ISSU is in progress and the loss
calculation results do not provide a valid cause for the loss. Unified ISSU is not
supported for both on-demand and proactive ETH-SLM.
194
The maximum number of SLA iterator profiles that can be configured in the system is
255.
ETH-SLM is not supported for virtual private LAN service (VPLS) (point-to-multipoint
measurements are not supported). The ETH-SLM frames are not generated with
multicast class 1 destination address. Similarly, ETH-SLM does not respond to ETH-SLM
requests with multicast DA. ETH-SLM for VPLS for point-to-point Ethernet connection
is supported using directed unicast destination MAC addresses, although
point-to-multipoint topologies are not supported.
Related
Documentation
A unicast destination address may be used in provisioned environments for

point-to-point connections. However, it requires that the unicast destination address
of the downstream MEP must have been configured on the MEP transmitting an alarm
indication signal (AIS).
ETH-SLM is not supported on aggregated Ethernet (ae) interfaces and on downstream

MEPs on label-switched interfaces (LSIs).
The number of ETH-SLM sessions for proactive ETH-SLM that can be supported is
limited to the total number of iterators that can be supported in the system. This
limitation includes the iterator support for other measurement types such as loss,
statistical frame loss, and two-way delay. A new iterator type, SLM, is added to support
ETH-SLM. The total number of SLA iterators that you can configure in the system is
equal to the total number of iterations supported in the system.
For on-demand SLM, the minimum period between two SLM requests is 100
milliseconds.
For proactive SLM, the minimum period between two SLM requests is 10 milliseconds
for distributed mode and 100 milliseconds for non-distributed mode.
ETH-SLM frames are always marked as drop-ineligible in compliance with the ITU-T
Y.1731 standard.
Scenarios for Configuration of ETH-SLM

ETH-SLM measures near-end and far-end frame loss between two MEPs that are part
of the same MEG level. You can configure ETH-SLM to measure synthetic loss for both
upward-facing or upstream MEP and downward-facing or downstream MEP. This section
describes the following scenarios for the operation of ETH-SLM:
195
Upstream MEP in MPLS Tunnels

Consider a scenario in which a MEP is configured between the user network interfaces
(UNIs) of two ACX Series routers, ACX1 and ACX2, in the upstream direction. ACX1 and
ACX2 are connected over an MPLS core network. ETH-SLM measurements are performed
between the upstream MEP in the path linking the two routers. Both ACX1 and ACX2 can
initiate on-demand or proactive ETH-SLM, which can measure both far-end and near-end
loss at ACX1 and ACX2, respectively. The two UNIs are connected using MPLS-based
Layer 2 VPN virtual private wire service (VPWS).
Downstream MEP in Ethernet Networks

Consider a scenario in which a MEP is configured between two ACX Series routers, ACX1
and ACX2, on the Ethernet interfaces in the downstream direction. ACX1 and ACX2 are
connected in an Ethernet topology and downstream MEP is configured toward the
Ethernet network. ETH-SLM measurements are performed between the downstream
MEP in the path linking the two routers. ETH-SLM can be measured in the path between
these two routers.
Consider another scenario in which a MEP is configured in the downstream direction and
service protection for a VPWS over MPLS is enabled by specifying a working path or
protect path on the MEP. Service protection provides end-to-end connection protection
of the working path in the event of a failure. To configure service protection, you must
create two separate transport pathsa working path and a protect path. You can specify
the working path and protect path by creating two maintenance associations. To associate
the maintenance association with a path, you must configure the MEP interface in the
maintenance association and specify the path as working or protect.
In a sample topology, an ACX Series router, ACX1, is connected to two other ACX Series
routers, ACX2 and ACX3, over an MPLS core. The connectivity fault management (CFM)
session between ACX1 and ACX2 is the working path on the MEP and the CFM session
between ACX1 and ACX3 is the protect path on the MEP. ACX2 and ACX3 are, in turn,
connected on Ethernet interfaces to ACX4 in the access network. Downstream MEP is
configured between ACX1 and ACX4 that passes through ACX2 (working CFM session)
and also between ACX1 and ACX4 that passes through ACX3 (protected CFM session).
ETH-SLM is performed between these downstream MEPs. In both the downstream MEPs,
the configuration is performed on ACX1 and ACX4 UNIs, similar to upstream MEP.
Related
Documentation
196
Managing ETH-SLM Statistics and ETH-SLM Frame Counts
Displaying ETH-SLM Statistics Only on page 197
Displaying ETH-SLM Statistics and Frame Counts on page 197
Displaying ETH-SLM Frame Counts for MEPs by Enclosing CFM Entity on page 198
Displaying ETH-SLM Frame Counts for MEPs by Interface or Domain Level on page 199
Clearing ETH-SLM Statistics and Frame Counts on page 199
Clearing Iterator Statistics on page 200
Displaying ETH-SLM Statistics Only

Purpose
Display on-demand ETH-SLM statistics.

By default, the show oam ethernet connectivity-fault-management synthetic-loss-statistics
command displays on-demand ETH-SLM statistics for MEPs in the specified CFM
maintenance association within the specified CFM maintenance domain.
Action
To display the on-demand ETH-SLM statistics collected for MEPs belonging to

maintenance association ma1 within maintenance domain md1:
user@host> show oam ethernet connectivity-fault-management synthetic-loss-statistics
maintenance-domain md1 maintenance-association ma1
To display the on-demand ETH-SLM statistics collected for ETH-SLM sessions for the
local MEP 201 belonging to maintenance association ma2 within maintenance
domain md2:
maintenance-domain md2 maintenance-association ma2 local-mep 201
To display the on-demand ETH-SLM statistics collected for ETH-SLM sessions from
local MEPs belonging to maintenance association ma3 within maintenance domain md3
to the remote MEP 302:
maintenance-domain md3 maintenance-association ma3 remote-mep 302
Meaning
The output displays on-demand ETH-SLM statistics for MEPs in the specified maintenance
association within the specified maintenance domain. For details about the output of
this command and the descriptions of the output fields, see show oam ethernet
connectivity-fault-management synthetic-loss-statistics.
Displaying ETH-SLM Statistics and Frame Counts

Purpose
Display on-demand ETH-SLM statistics and ETH-SLM frame counts.

By default, the show oam ethernet connectivity-fault-management mep-statistics
command displays on-demand ETH-SLM statistics and frame counts for MEPs in the
specified CFM maintenance association within the specified CFM maintenance domain.
197
Action
To display the on-demand ETH-SLM statistics and ETH-SLM frame counts for MEPs
in maintenance association ma1 within maintenance domain md1:
user@host> show oam ethernet connectivity-fault-management mep-statistics
To display the on-demand ETH-SLM statistics and ETH-SLM frame counts for the
local MEP 201 in maintenance association ma2 within maintenance domain md2:
To display the on-demand ETH-SLM statistics and ETH-SLM frame counts for the
local MEP in maintenance association ma3 within maintenance domain md3 that
participates in an ETH-SLM session with the remote MEP 302:
maintenance-domain ma3 maintenance-association ma3 remote-mep 302
Meaning
The output displays on-demand ETH-SLM statistics and ETH-SLM frame counts for
MEPs in the specified maintenance association within the specified maintenance domain.
For details about the output of this command and the descriptions of the output fields,
see show oam ethernet connectivity-fault-management mep-statistics.
Displaying ETH-SLM Frame Counts for MEPs by Enclosing CFM Entity

Purpose
Display on-demand ETH-SLM frame counts for CFM maintenance association end points
(MEPs).
By default, the show oam ethernet connectivity-fault-management mep-database
command displays CFM database information for MEPs in the specified CFM maintenance
association within the specified CFM maintenance domain.
NOTE: At the router attached to the initiator MEP for a one-way session, or
at the router attached to the receiver MEP for a two-way session, you can
only display the ETH-SLM frame counts and not the MEP database details.
Action
To display CFM database information (including ETH-SLM frame counts) for all MEPs
in MA ma1 within maintenance domain md1:
user@host> show oam ethernet connectivity-fault-management mep-database
maintenance-domain ma1 maintenance-association ma1
To display CFM database information (including ETH-SLM frame counts) only for the
local MEP 201 in MA ma1 within maintenance domain md1:
remote MEP 302 in MA ma3 within maintenance domain md3:
maintenance-domain ma3 maintenance-association ma3 remote-mep 302
198
Meaning
The output displays ETH-SLM frame counts for MEPs within a particular maintenance
domain, or for a specific local or remote MEP. For details about the output of this
command and the descriptions of the output fields, see show oam ethernet
connectivity-fault-management mep-database.
Displaying ETH-SLM Frame Counts for MEPs by Interface or Domain Level

Purpose
Display on-demand ETH-SLM frame counts for CFM maintenance association end points
(MEPs).
By default, the show oam ethernet connectivity-fault-management interfaces command
displays CFM database information for MEPs attached to CFM-enabled Ethernet
interfaces on the router or at a maintenance domain level. For Ethernet interfaces that
support ETH-SLM, any frame counts are also displayed when you specify the detail or
extensive command option.
NOTE: At the router attached to the initiator MEP, you can only display the
ETH-SLM frame counts and not the MEP database details.
Action
To display CFM database information (including ETH-SLM frame counts) for all MEPs
attached to CFM-enabled Ethernet interfaces on the router:
user@host> show oam ethernet connectivity-fault-management interfaces detail
MEPs attached to CFM-enabled router interface ge-5/2/9.0:
user@host> show oam ethernet connectivity-fault-management interfaces ge-5/2/9.0 detail
To display CFM database information (including ETH-SLM frame counts) only for
MEPs enclosed within CFM maintenance domains at level 6:
user@host> show oam ethernet connectivity-fault-management interfaces level 6 detail
Meaning
The output displays ETH-SLM frame counts for MEPs for the specified interface. For
details about the output of this command and the descriptions of the output fields, see
show oam ethernet connectivity-fault-management interfaces.
Clearing ETH-SLM Statistics and Frame Counts

Purpose
Clear the on-demand ETH-SLM statistics and ETH-SLM frame counts.

By default, statistics and frame counts are deleted for all MEPs attached to CFM-enabled
interfaces on the router. However, you can filter the scope of the command by specifying
an interface name.
Action
To clear the on-demand ETH-SLM statistics and ETH-SLM frame counts for all MEPs
attached to CFM-enabled interfaces on the router:
user@host> clear oam ethernet connectivity-fault-management synthetic-loss-measurement
199
To clear the on-demand ETH-SLM statistics and ETH-SLM frame counts only for MEPs
attached to the logical interface ge-0/5.9.0:
ge-0/5/9.0
Clearing Iterator Statistics

Purpose
Clear the existing iterator statistics and proactive ETH-SLM counters.

Multiple iterators can be associated with remote MEP. However, by default, only one
result pertaining to one iterator profile can be cleared.
Action
To clear the iterator statistics for remote MEP 1 and iterator profile i1 with MEPs
belonging to the maintenance association ma1 within the maintenance domain
default-1:
user@host> clear oam ethernet connectivity-fault-management sla-iterator-statistics
sla-iterator i1 maintenance-domain default-1 maintenance-association ma1 local-mep 1
remote-mep 1
To clear the iterator statistics for remote MEP 1 and iterator profile i2 with MEPs
belonging to the maintenance association ma1 within the maintenance domain default-1:
user@host> clear oam ethernet connectivity-fault-management sla-iterator-statistics
remote-mep 1
Related
Documentation
clear oam ethernet connectivity-fault-management synthetic-loss-measurement on

page 327
show oam ethernet connectivity-fault-management synthetic-loss-statistics on page 807
show oam ethernet connectivity-fault-management interfaces on

page 767 (detail | extensive)
show oam ethernet connectivity-fault-management mep-statistics on page 778
show oam ethernet connectivity-fault-management mep-database on page 791
Starting a Proactive ETH-SLM Session

To start a proactive Ethernet synthetic loss measurement (ETH-SLM) session, you must
configure the Ethernet interfaces on maintenance association end points (MEPs) on
which packets transmitted with synthetic frame loss need to be analyzed. You must then
create an iterator profile to transmit service-level agreement (SLA) measurement packets
for ETH-SLM and associate the local and remote MEPs with the profile.
200
Configuring MEP Interfaces on page 201
Configuring an Iterator Profile for ETH-SLM on page 202
Associating the Iterator Profile with MEPs for ETH-SLM on page 203
Configuring MEP Interfaces

Before you can start an Ethernet synthetic frame loss measurement session across an
Ethernet service, you must configure two ACX Series routers to support ETH-SLM.
To configure an Ethernet interface on an ACX Series router to support ETH-SLM:
1.
On each router, configure two physical or logical Ethernet interfaces connected by a

VLAN. The following configuration is typical for single-tagged logical interfaces:
[edit interfaces]
interface {
ethernet-interface-name {
vlan-tagging;
unit logical-unit-number {
vlan-id vlan-id; # Both interfaces on this VLAN
}
}
}
Both interfaces will use the same VLAN ID.

2. On each router, attach peer MEPs to the two interfaces. The following configuration
is typical:
[edit protocols]
oam {
ethernet {
maintenance-domain md-name { # On both routers
level number;
maintenance-association ma-name { # On both routers
continuity-check {
interval 100ms;
hold-interval 1;
}
mep mep-id { # Attach to VLAN interface
auto-discovery;
direction (up | down);
interface interface-name;
priority number;
}
}
}
}
}
}
201
Configuring an Iterator Profile for ETH-SLM

You can create an iterator profile with its parameters to periodically transmit SLA
measurement packets in the form of ITU-Y.1731-compliant frames for synthetic loss
measurement.
To create an iterator profile:
1.

[edit]
user@host# edit protocols oam ethernet connectivity-fault-management
performance-monitoring
2. Configure the SLA measurement monitoring iterator:
[edit protocols oam ethernet connectivity-fault-management performance-monitoring]

user@host# edit sla-iterator-profiles
3. Configure an iterator profilefor example, i1:
[edit protocols oam ethernet connectivity-fault-management performance-monitoring

sla-iterator-profiles]
user@host# set i1
4. (Optional) Configure the cycle time, which is the amount of time (in milliseconds)
between back-to-back transmission of SLA frames for one connection, with a value
from 10 through 3,600,000. The default value is 1000 ms.
sla-iterator-profiles i1]
user@host# set cycle-time cycle-time-value
5. (Optional) Configure the iteration period, which indicates the maximum number of
cycles per iteration (the number of connections registered to an iterator cannot exceed
this value), with a value from 1 through 2000. The default value is 2000.
user@host# set iteration-period iteration-period-value
6. Configure the measurement type as synthetic loss measurement.

user@host# set measurement-type slm
7. Configure the disable statement to stop the iterator (that is, disable the iterator profile).

user@host# set disable
8. Verify the configuration.

sla-iterator-profiles]
user@host# show i1
cycle-time cycle-time-value;
iteration-period iteration-period-value;
202
measurement-type slm;
Associating the Iterator Profile with MEPs for ETH-SLM

You can associate a remote maintenance association end point (MEP) with more than
one iterator profile.
To configure a remote MEP with an iterator profile:
1.

user@host# edit protocols oam ethernet connectivity-fault-management
maintenance-domain md-name maintenance-association ma-name mep mep-id
2. Configure the remote MEP ID with a value from 1 through 8191.
[edit protocols oam ethernet connectivity-fault-management maintenance-domain

md-name maintenance-association ma-name mep mep-id]
user@host# set remote-mep remote-mep-id
3. Set the iterator profile.

md-name maintenance-association ma-name mep mep-id remote-mep
remote-mep-id]
user@host# set sla-iterator-profile profile-name
4. (Optional) Set the size of the data TLV portion of the Y.1731 data frame with a value
from 1 through 1400 bytes. The default value is 1.

md-name maintenance-association ma-name mep mep-id remote-mep remote-mep-id
sla-iterator-profile profile-name]
user@host# set data-tlv-size size
5. (Optional) Set the iteration count, which indicates the number of iterations for which
this connection should partake in the iterator for acquiring SLA measurements, with
a value from 1 through 65,535. The default value is 0 (that is, infinite iterations).
user@host# set iteration-count count-value
6. (Optional) Set the priority, which is the vlan-pcp value that is sent in the Y.1731 data
frames, with a value from 0 through 7. The default value is 0.

user@host# set priority priority-value
7. Verify the configuration.

md-name maintenance-association ma-name mep mep-id remote-mep
remote-mep-id]
user@host# show
sla-iterator-profile profile-name {
data-tlv-size size;
203
iteration-count count-value;
priority priority-value;
}
Related
Documentation
Starting an On-Demand ETH-SLM Session

To start an on-demand Ethernet synthetic loss measurement (ETH-SLM) session, type
the monitor ethernet synthetic-loss-measurement one-way command in operational
mode, and specify the peer MEP by its MAC address or by its MEP identifier.
For example:
user@host> monitor ethernet synthetic-loss-measurement 00:05:85:73:39:4a
maintenance-domain md6 maintenance-association ma6 count 10
ETH-SLM request to 00:05:85:73:39:4a, interface ge-1/0/0.0
Synthetic Loss measurement statistics:
SLM packets sent
: 100
SLR packets received
: 100
Accumulated SLM statistics:
Local TXFC1 value
: 100
Local RXFC1 value
: 100
Last Received SLR frame TXFCf(tc)
: 100
Last Received SLR frame TXFCb(tc)
: 100
SLM Frame Loss:
Frame Loss (far-end)
: 0 (0.00 %)
Frame Loss (near-end)
: 0 (0.00 %)
NOTE: If you attempt to monitor delays to a nonexistent MAC address, you

must press Ctrl + C to explicitly quit the monitor ethernet
synthetic-loss-measurement command and return to the CLI command
prompt.
Related
Documentation
204
205
206
CHAPTER 11
Routing Protocols
IPv6 Support on ACX Series Universal Access Routers on page 207
Layer 3 VPNs for IPv4 and IPv6 Overview on page 210
Configuring Multiprotocol BGP on page 212
IPv6 Support on ACX Series Universal Access Routers

IPv6 builds upon the functionality of IPv4, providing improvements to addressing,
configuration and maintenance, and security. The following IPv6 features are supported
on ACX Series routers:
IPv6 path maximum transmission unit (MTU) discovery

Path MTU Discovery is used by single-source devices to determine the correct size of
fragments. Path MTU Discovery is enabled for IPv6 packets by default.
Dynamic routes distribution through IS-IS and OSPF for IPv6

Routers learn routes through different routing protocols such as OSPF, BGP, or IS-IS.
Learned routes are put in the routing table to enable IPv6 traffic forwarding.
Dual stacking (IPv4 and IPv6)

Dual stacking allows a device to run both IPv4 and IPv6 at the same time. End nodes,
routers, and switches run both protocols and use IPv6 as the preferred protocol.
IPv6 forwarding
The ACX Series port forwarding engine software supports unicast IPv6 routes and next
hops. This includes basic route infrastructure, next-hop support, network infrastructure,
and exception packet processing.
IPv6 over MPLS (6PE)

ACX Series Universal Access Routers can interconnect IPv6 islands over an
MPLS-enabled IPv4 network. IPv6 information is sent over the MPLS core using MG-BGP
with IPv4. The BGP Next Hop field conveys the IPv4 address of the router so that MPLS
LSPs can be used without explicit tunnel configuration.
Neighbor Discovery
The Neighbor Discovery protocol facilitates a substantial number of functions related
to local network connectivity, datagram routing, and configuration. Both regular hosts
207
and routers in an IPv6 environment count on the Neighbor Discovery protocol to

facilitate the important exchanges of information that are necessary for proper
internetwork operations. Neighbor Discovery is a messaging protocol similar to ICMP.
The following functions are performed by the protocol:
Router discoveryHow a host locates routers residing on an attached link.
Prefix discoveryHow a host discovers address prefixes for destinations residing on

an attached link. Nodes use prefixes to distinguish between destinations that reside
on an attached link and those destinations that it can reach only through a router.
Parameter discoveryHow a node learns various parameters (link parameters or

Internet parameters) that it places in outgoing packets.
Address resolutionHow a node uses only a destination IPv6 address to determine

a link-layer address for destinations on an attached link.
Next-hop determinationThe algorithm that a node uses for mapping an IPv6

destination address into a neighbor IPv6 address (either the next router hop or the
destination itself) to which it plans to send traffic for the destination.
Neighbor unreachability detectionHow a node determines that it can no longer

reach a neighbor.
Duplicate address detectionHow a node determines whether an address is already

in use by another node.
Internet Control Message Protocol v6 (ICMPv6)

ICMP sends error messages and information messages related to IP operations. ICMPv6
defines additional error messages and informational messages specific to IPv6.
There are four different ICMPv6 error messages:
Destination UnreachableA packet cannot be delivered due to an inherent problem

with how it is being sent. Includes a code that indicates the nature of the problem
that caused the packet not to be delivered
Packet Too BigSent when a packet is too large to be delivered.
Time ExceededA packet cannot be delivered because it has exceeded the hop
count specified in the basic header hop-by-hop field.
Parameter ProblemIndicates a problem with a field in the IPv6 header or extension

headers that makes it impossible to process the packet.
ICMPv6 information messages are used for sharing the information required to
implement various test, diagnostic, and support functions that are critical to the
operation of IPv6. There are a total of eight different ICMPv6 informational messages:
208
Echo Request
Echo Reply
Router Advertisement
Router Solicitation
Neighbor Advertisement
Chapter 11: Routing Protocols
Neighbor Solicitation
Redirect
Router Renumbering
Static routes for IPv6

Routing information can be configured statically. Whenever a route is configured
statically, the routing information base (RIB) is updated with routes specified through
the static route. These routes should be configured statically in the routing-options
hierarchy. The following configuration is used for enabling static routes for IPv6:
interfaces {
fe/0/1/0 {
unit 0 {
family inet6 {
address fec0:0:0:3::1/64;
}
}
}
}
routing-options {
rib inet6.0 {
static {
route fec0:0:0:4::/64 next-hop fec0:0:0:3::ffff;
}
}
}
inet6.0: 3 destination, 3 routes (3 active, 0 holddown, 0 hidden)
fec0:0:0:3::/64
*[Direct/0] 00:01:34
> via fe-0/1/0.0

fec:0:0:0:3::1/128
*[Local/0] 00:01:34
Local
fec0:0:0:4::/64
*[Static/5] 00:01:34
> to fec0:0:03:ffff via fe-0/1/0.0
Related
Documentation
IPv6 Overview
Understanding Dual Stacking
IS-IS Overview
OSPF Overview
ICMP Router Discovery Overview
Configuring the Junos OS for IPv6 Path MTU Discovery
IPv6 Neighbor Discovery Overview
209
Monitoring the Status of IPv6 Static Routes in the Routing Table
Layer 3 VPNs for IPv4 and IPv6 Overview

A Layer 3 virtual private network (VPN) routing instance is a collection of routing tables,
interfaces, and routing protocol parameters. The interfaces belong to the routing tables,
and the routing protocol parameters control the information in the routing tables. In the
case of MPLS VPNs, each VPN has a VPN routing and forwarding (VRF) routing instance.
A VRF routing instance consists of one or more routing tables, a derived forwarding table,
the interfaces that use the forwarding table, and the policies and routing protocols that
determine what goes into the forwarding table. Because each instance is configured for
a particular VPN, each VPN has separate tables, rules, and policies that control its
operation. A separate VRF table is created for each VPN that has a connection to a
customer edge (CE) router. The VRF table is populated with routes received from directly
connected CE sites associated with the VRF routing instance, and with routes received
from other provider edge (PE) routers in the same VPN.
The standard or the global instance is called as the default routing instance. By default,
all interfaces are associated with the default routing instance and default routing
information base (RIB) (inet0). Routing options and routing policies supported on the
default routing instance are also applicable to other routing instances.
A VRF routing instance is a BGP and MPLS VPN environment in which BGP is used to
exchange IP VPN routes and discover the remote site, and in which VPN traffic traverses
an MPLS tunnel in an IP and MPLS backbone. You can enable an ACX Series router to
function as a PE router by configuring VRF routing instances.
You can configure routing instances on ACX Series routers at the [edit routing-instances
routing-instance-name protocols] hierarchy level for unicast IPv4, multicast IPv4, unicast
IPv6, and multicast IPv6 address families. If you do not explicitly specify the address
family in an IPv4 or an IPv6 environment, the router is configured to exchange unicast
IPv4 or unicast IPv6 addresses by default. You can also configure the router to exchange
unicast IPv4 and unicast IPv6 routes in a specified VRF routing instance. If you specify
the multicast IPv4 or multicast IPv6 address family in the configuration, you can use BGP
to exchange routing information about how packets reach a multicast source, instead
of a unicast destination, for transmission to endpoints.
NOTE: Only the forwarding and virtual router routing instances support
unicast IPv6 and multicast IPv6 address families. Unicast IPv6 and multicast
IPv6 address families are not supported for VRF routing instances.
You can configure the following types of Layer 3 routing instances on ACX Series routers:
210
ForwardingUse this routing instance type for filter-based forwarding applications.

For this instance type, there is no one-to-one mapping between an interface and a
routing instance. All interfaces belong to the default instance inet.0. There are multiple
forwarding tables and the selection of a table depends on the filter applied on the
interface.
Virtual routerA virtual router routing instance is similar to a VRF instance type, but is
used for non-VPN-related applications. There are no VRF import, VRF export, VRF
target, or route distinguisher requirements for this instance type. For this instance type,
there is a one-to-one mapping between an interface and a routing instance. This routing
instance type is used for routing and forwarding virtualization without VPNs (which is
achieved by using the VRF-Lite application).
VRFUse the VRF routing instance type for Layer 3 VPN implementations. This routing
instance type has a VPN routing table as well as a corresponding VPN forwarding table.
For this instance type, there is a one-to-one mapping between an interface and a
routing instance. Each VRF routing instance corresponds with a forwarding table. The
routes for each interface are installed in the forwarding table that is associated with
the VRF routing instance. This routing instance type is used to implement BGP or MPLS
VPNs in service provider networks or in big enterprise topologies.
Consider a sample VRF configuration scenario in which you want to configure two virtual
routers, one to transmit voice and data traffic and another to carry management traffic.
With such a configuration, the user and management networks are virtually separated,
although the physical infrastructure is unified and cohesive. Virtual router routing instances
enable you to isolate traffic without using multiple devices to segment your networks.
The virtual routers do not create IP, MPLS, or GRE tunnels, and automatic discovery of
remote sites that belong to the same network is not available. You must configure
interfaces that are part of a virtual network in a streamlined manner to suit your topology
requirements.
The following limitations apply to VRF routing instances that you configure on ACX Series
routers:
You cannot establish a communication between two virtual routing instances that are
connected by external loopback.
You cannot add a GRE or an MPLS tunnel to a virtual router.
In the Layer 3 lookup, up to 128 VRF tables are supported. Virtual routers without routing
protocols enabled (based on static routes) support 64 VRF tables and virtual routers
with all functions enabled within the routing instances support 16 VRF tables. When you
enable VRF table labels and you do not explicitly apply a classifier configuration to the
routing instance, the default MPLS EXP classifier is applied to the routing instance. You
can override the default MPLS EXP classifier and apply a custom classifier to the routing
instance. To perform this operation, you can filter the packets based on the IP header,
choose the VRF, and based on the selected VRF, create an EXP classifier and associate
it with the routing instance.
Related
Documentation
Routing Instances Overview
Configuring Virtual-Router Routing Instances in VPNs
Applying MPLS EXP Classifiers to Routing Instances
Configuring Routing Instances on PE Routers in VPNs
211
[edit routing-instances] Hierarchy Level for ACX Series Routers
Configuring Multiprotocol BGP

Multiprotocol Border Gateway Protocol (MP-BGP) is an extension to BGP that enables
BGP to carry routing information for multiple network layers and address families. MP-BGP
can carry the unicast routes used for multicast routing separately from the routes used
for unicast IP forwarding.
The following topics describe the ways in which you can configure MP-BGP on ACX Series
routers for IPv4 and IPv6 address families:
Enabling MP-BGP for the IPv4 Address Family on page 212
Enabling MP-BGP for the IPv6 Address Family on page 212
Enabling MP-BGP for Address Families Other than Unicast IPv4 on page 213
Enabling MP-BGP and VPN Signaling for the IPv4 Address Family on page 213
Enabling MP-BGP and VPN Signaling for the IPv6 Address Family on page 214
Enabling MP-BGP for the IPv4 Address Family

To enable MP-BGP to carry Layer 3 virtual private network (VPN) NLRI for the IPv4
address family, include the family inet-vpn statement at the [edit protocols bgp] or the
[edit routing-instances routing-instance-name protocols bgp] hierarchy level:
family inet-vpn {
(any | flow | multicast | unicast) {
accepted-prefix-limit {
maximum number;
teardown <percentage> <idle-timeout (forever | minutes)>;
}
<loops number>;
prefix-limit {
maximum number;
}
rib-group group-name;
}
}
Enabling MP-BGP for the IPv6 Address Family

To enable MP-BGP to carry NLRI for the IPv6 address family, include the family inet6
statement at the [edit protocols bgp] or the [edit routing-instances routing-instance-name
protocols bgp] hierarchy level:
family inet6 {
(any | labeled-unicast | multicast | unicast) {
maximum number;
}
212
<loops number>;
prefix-limit {
maximum number;
}
}
}
Enabling MP-BGP for Address Families Other than Unicast IPv4

To enable MP-BGP to carry network layer reachability information (NLRI) for address
families other than unicast IPv4, include the family inet statement at the [edit protocols
bgp] or the [edit routing-instances routing-instance-name protocols bgp] hierarchy level:
family inet {
(any | flow | labeled-unicast | multicast | unicast) {
maximum number;
}
<loops number>;
prefix-limit {
maximum number;
}
topology name {
community {
target identifier;
}
}
}
}
Enabling MP-BGP and VPN Signaling for the IPv4 Address Family
To enable MP-BGP to carry multicast VPN NLRI for the IPv4 address family and to enable
VPN signaling, include the family inet-mvpn statement at the [edit protocols bgp] or the
[edit routing-instances routing-instance-name protocols bgp] hierarchy level:
family inet-mvpn {
signaling {
maximum number;
}
<loops number>;
prefix-limit {
maximum number;
}
}
}
213
Enabling MP-BGP and VPN Signaling for the IPv6 Address Family
To enable MP-BGP to carry multicast VPN NLRI for the IPv6 address family and to enable
VPN signaling, include the family inet6-mvpn statement at the [edit protocols bgp] or
the [edit routing-instances routing-instance-name protocols bgp] hierarchy level:
family inet6-mvpn {
signaling {
maximum number;
}
<loops number>;
prefix-limit {
maximum number;
teardown <percentage> <idle-timeout <forever | minutes>;
}
}
}
Related
Documentation
214
Layer 3 VPNs for IPv4 and IPv6 Overview on page 210
Examples: Configuring Multiprotocol BGP
CHAPTER 12
Time Division Multiplexing (TDM)
Configuring CESoPSN Encapsulation on DS Interfaces on page 215
Configuring CE1 Channels Down to DS Interfaces on page 216
Configuring E1 Loopback Capability on page 232
Configuring T1 Loopback Capability on page 234
Configuring CESoPSN Encapsulation on DS Interfaces

Circuit Emulation Service over Packet-Switched Network (CESoPSN) is an encapsulation
layer intended to carry NxDS0 services over a packet-switched network (PSN).
To configure CESoPSN encapsulation on a DS interface:
1.
Create the DS interface.

[edit interfaces]
user@host# edit interface ds-fpc/pic/port:partition
For example:
[edit interfaces]
user@host# edit interface ds-0/0/1:1
2. Configure the encapsulation.
[edit interfaces ds-fpc/pic/port:partition]

user@host# set encapsulation cesopsn
3. Configure the logical interface.

user@host# set unit logical-unit-number
For example:
[edit interfaces ds-0/0/1:1]
user@host# set unit 0
215
When you are finished configuring CESoPSN encapsulation on the DS0 interface, enter
the commit command from configuration mode.
From configuration mode, confirm your configuration by entering the show command.
for example:
[edit interfaces]
user@host# show
ds-1/0/0:1:1 {
encapsulation cesopsn;
unit 0;
}
Related
Documentation
Mobile Backhaul and Circuit Emulation Overview
Configuring CESoPSN Encapsulation on DS Interfaces on Channelized OC3/STM1

(Multi-Rate) Circuit Emulation MIC with SFP
Configuring CE1 Channels Down to DS Interfaces

You can configure a DS interface on a channelized E1 interface (CE1) and then apply
CESoPSN encapsulation for the pseudowire to function. An NxDS0 interface can be
configured from a channelized CE1 interface, where N represents the time slots on the
CE1 interface. The value of N is 1 through 31 when a DS0 interface is configured from a
CE1 interface.
To configure CE1 channels down to a DS interface, include the partition statement at the
[edit interfaces ce1-fpc/pic/port] hierarchy level, as shown in the following example:
[edit interfaces]
user@host# show
ce1-0/0/1 {
partition 1 timeslots 1-4 interface-type ds;
}
After you partition the DS interface, configure the CESoPSN options on it. See Setting
the CESoPSN Options.
To configure CE1 channels down to a DS interface:
1.
Create the CE1 interface.

[edit interfaces]
user@host# edit interfaces ce1-fpc/pic/port
For example:
[edit interfaces]
user@host# edit interface ce1-0/0/1
2. Configure the partition, the time slot, and the interface type.
[edit interfaces ce1-fpc/pic/port]

user@host# set partition partition-number timeslots timeslots interface-type ds;
For example:
216
Chapter 12: Time Division Multiplexing (TDM)
[edit interfaces ce1-0/0/1]

user@host# set partition 1 timeslots 1-4 interface-type ds;
NOTE: You can assign multiple time slots on a CE1 interface; in the
configuration, separate the time slots by comma without spaces. For
example:
[edit interfaces ce1-0/0/1]
user@host# set partition 1 timeslots 1-4,9,2231 interface-type ds;
3. Configure the CESoPSN encapsulation for the DS interface.

user@host# set encapsulation encapsulation-type
For example:
user@host# set encapsulation cesopsn
4. Configure the logical interface for the DS interface.

user@host# set unit logical-unit-number;
For example:
user@host# set unit 0
When you are finished configuring CE1 channels down to a DS interface, enter the commit
command from configuration mode.
From configuration mode, confirm your configuration by entering the show command.
For example:
[edit interfaces]
user@host# show
ce1-0/0/1 {
partition 1 timeslots 1-4 interface-type ds;
}
ds-0/0/1:1 {
encapsulation cesopsn;
unit 0;
}
Related
Documentation
Mobile Backhaul and Circuit Emulation Overview
Configuring CESoPSN Encapsulation on DS Interfaces on Channelized OC3/STM1

(Multi-Rate) Circuit Emulation MIC with SFP
Configuring SAToP Emulation on Channelized T1 and E1 Interfaces

This configuration is the base configuration of SAToP on an ACX Series router as described
in RFC 4553, Structure-Agnostic Time Division Multiplexing (TDM) over Packet (SAToP).
217
When you configure SAToP on built-in channelized T1 and E1 interfaces, the configuration
results in a pseudowire that acts as a transport mechanism for the T1 and E1 circuit signals
across a packet-switched network.
The network between the customer edge (CE) routers appears transparent to the CE
routers, making it seem that the CE routers are directly connected. With the SAToP
configuration on the provider edge (PE) routers T1 and E1 interfaces, the interworking
function (IWF) forms a payload (frame) that contains the CE routers T1 and E1 Layer 1
data and control word. This data is transported to the remote PE over the pseudowire.
The remote PE removes all the Layer 2 and MPLS headers added in the network cloud
and forwards the control word and the Layer 1 data to the remote IWF, which in turn
forwards the data to the remote CE.
Figure 16: Pseudowire Encapsulation with SAToP

g016956
Emulated Service
Attachment Circuit
Attachment Circuit
PSN tunnel
Pseudowire 1
CE1
PE1
Pseudowire 2
Native service
CE2
PE2
Native service
In Figure 16 on page 218 the Provider Edge (PE) router represents the ACX Series router
that is being configured in these steps. The result of these steps is the pseudowire from
PE1 to PE2. Topics include:
Setting the T1/E1 Emulation Mode on page 218
Configuring One Full T1 or E1 Interface on Channelized T1 and E1 Interfaces on page 219
Setting the SAToP Encapsulation Mode on page 222
Setting the T1/E1 Emulation Mode

Emulation is a mechanism that duplicates the essential attributes of a service (such as
T1 or E1) over a packet-switched network. You set the emulation mode so that the built-in
channelized T1 and E1 interfaces on the ACX Series router can be configured to work in
either T1 or E1 mode. This configuration is at the PIC level, so all ports operate as either
T1 interfaces or E1 interfaces. A mix of T1 and E1 interfaces is not supported. By default
all the ports operate as T1 interfaces.
Configure the emulation mode:

[edit chassis fpc fpc-slot pic pic-slot]
user@host# set framing (t1 | e1)
For example:
[edit chassis fpc 0 pic 0]
user@host# set framing t1
After a PIC is brought online and depending on the framing option used (t1 or e1), on
the ACX2000 router, 16 CT1 or 16 CE1 interfaces are created, and on the ACX1000
router, 8 CT1 or 8 CE1 interfaces are created.
218
The following output shows this configuration:

user@host# show chassis
fpc 0 {
pic 0 {
framing t1;
}
}
The following output from the show interfaces terse command shows the 16 CT1
interfaces created with the framing configuration.
user@host# run show interfaces terse
Interface
Admin Link Proto
ct1-0/0/0
up
down
ct1-0/0/1
up
down
ct1-0/0/2
up
down
ct1-0/0/3
up
down
ct1-0/0/4
up
down
ct1-0/0/5
up
down
ct1-0/0/6
up
down
ct1-0/0/7
up
down
ct1-0/0/8
up
down
ct1-0/0/9
up
down
ct1-0/0/10
up
down
ct1-0/0/11
up
down
ct1-0/0/12
up
down
ct1-0/0/13
up
down
ct1-0/0/14
up
down
ct1-0/0/15
up
down
Local
Remote
NOTE: If you set the framing option incorrectly for the PIC type, the commit
operation fails.
If you change the mode, the router will reboot the built-in T1 and E1 interfaces.
Bit error rate test (BERT) patterns with all ones received by T1 and E1
interfaces configured for SAToP do not result in an alarm indication signal
(AIS) defect. As a result, the T1 and E1 interfaces remain up.
Configuring One Full T1 or E1 Interface on Channelized T1 and E1 Interfaces

You must configure a child T1 or E1 interface on the built-in channelized T1 or E1 interface
created because the channelized interface is not a configurable interface and SAToP
encapsulation must be configured (in the next step) for the pseudowire to function. The
following configuration creates one full T1 interface on the channelized ct1 interface. You
can follow the same process to create one E1 interface on the channelized ce1 interface.
Configure one full T1/E1 interface:

[edit interfaces ct1-fpc/pic /port]
user@host# set no-partition interface-type (t1 | e1)
For example:
[edit interfaces ct1-0/0/0
219
user@host# set no-partition interface-type t1

[edit]
user@host# show interfaces
ct1-0/0/0 {
no-partition interface-type t1;
}
The preceding command creates the t1-0/0/0 interface on the channelized ct1-0/0/0
interface. Check the configuration with the show interfaces interface-name extensive
command. Run the command to display output for the channelized interface and the
newly created T1 or E1interface. The following output provides an example of the output
for a CT1 interface and the T1 interface created from the preceding example configuration.
Notice that ct1-0/0/0 is running at T1 speed and that the media is T1.
user@host> show interfaces ct1-0/0/0 extensive
Physical interface: ct1-0/0/0, Enabled, Physical link is Up
Interface index: 152, SNMP ifIndex: 780, Generation: 1294
Link-level type: Controller, Clocking: Internal, Speed: T1, Loopback: None,
Framing: ESF, Parent: None
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps Internal: 0x0
Link flags
: None
Hold-times
: Up 0 ms, Down 0 ms
CoS queues
: 8 supported, 4 maximum usable queues
Last flapped
: 2012-04-03 06:27:55 PDT (00:13:32 ago)
Statistics last cleared: 2012-04-03 06:40:34 PDT (00:00:53 ago)
DS1
alarms
: None
DS1
defects : None
T1 media:
Seconds
Count State
SEF
0
0 OK
BEE
0
0 OK
AIS
0
0 OK
LOF
0
0 OK
LOS
0
0 OK
YELLOW
0
0 OK
CRC Major
0
0 OK
CRC Minor
0
0 OK
BPV
0
0
EXZ
0
0
LCV
0
0
PCV
0
0
CS
0
0
CRC
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: 0, Algorithm: 2^15 - 1, O.151, Pseudorandom (9)
220
Packet Forwarding Engine configuration:

Destination slot: 0 (0x00)
In the following output for the T1 interface, the parent interface is shown as ct1-0/0/0
and the link level type and encapsulation are TDM-CCC-SATOP.
user@host> show interfaces t1-0/0/0 extensive

Physical interface: t1-0/0/0, Enabled, Physical link is Up
Link-level type: TDM-CCC-SATOP, MTU: 1504, Speed: T1, Loopback: None, FCS:
16, Parent: ct1-0/0/0 Interface index 152
Device flags
: Present Running
Link flags
: None
Hold-times
CoS queues
Last flapped
: 2012-04-03 06:28:43 PDT (00:01:16 ago)
Egress queues: 8 supported, 4 in use
Queue counters:
Queued packets Transmitted packets
Dropped packets
0 best-effort
1 expedited-fo
2 assured-forw
3 network-cont
Queue number:
Mapped forwarding classes
0
best-effort
1
2
assured-forwarding
3
network-control
DS1
alarms
: None
DS1
defects : None
SAToP configuration:
Payload size: 192
Idle pattern: 0xFF
Octet aligned: Disabled
Jitter buffer: packets: 8, latency: 7 ms, auto adjust: Disabled
Excessive packet loss rate: sample period: 10000 ms, threshold: 30%
Destination slot: 0
CoS information:
Direction : Output
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
Logical interface t1-0/0/0.0 (Index 308) (SNMP ifIndex 789) (Generation 11238)
Flags: Point-To-Point SNMP-Traps Encapsulation: TDM-CCC-SATOP
CE info
Packets
Bytes Count
CE Tx
0
0
CE Rx
0
0
221
CE Rx Forwarded
0
CE Strayed
0
CE Lost
0
CE Malformed
0
CE Misinserted
0
CE AIS dropped
0
CE Dropped
0
0
CE Overrun Events
0
CE Underrun Events
0
Protocol ccc, MTU: 1504, Generation: 13130, Route table: 0
Setting the SAToP Encapsulation Mode

The built-in T1 and E1 interfaces must be configured with SAToP encapsulation at the
PE router so that the interworking function (IWF) can segment and encapsulate TDM
signals into SAToP packets, and in the reverse direction, to decapsulate the SAToP
packets and reconstitute them into TDM signals.
1.
On the PE router, configure SAToP encapsulation on the physical interface:

[edit interfaces (t1 | e1)fpc/pic /port]
user@host# set encapsulation satop
For example:
[edit interfaces t1-0/0/0
user@host# set encapsulation satop
2. On the PE router, configure the logical interface:
[edit interfaces ]
user@host# set (t1 | e1)fpc/pic/port unit logical-unit-number
For example:
[edit interfaces]
user@host# set t1-0/0/0 unit 0
It is not necessary to configure the circuit cross-connect (CCC) family because it is
automatically created for the preceding encapsulation. The following output shows
this configuration.
[edit interfaces]
regress@R7# show t1-0/0/0
encapsulation satop;
unit 0;
222
Configure the Layer 2 Circuit

When you configure the Layer 2 circuit, you designate the neighbor for the provider edge
(PE) router. Each Layer 2 circuit is represented by the logical interface connecting the
local PE router to the local customer edge (CE) router. All the Layer 2 circuits that use a
particular remote PE router, designated for remote CE routers, are listed under the neighbor
statement. Each neighbor is identified by its IP address and is usually the end-point
destination for the label-switched path (LSP) tunnel that transports the Layer 2 circuit.
Configure the Layer 2 circuit:
[edit protocols l2circuit neighbor address]

user@host# set interface interface-name virtual-circuit-id identifier
For example, for a T1 interface:
[edit protocols l2circuit neighbor 2.2.2.2
user@host# set interface t1-0/0/0.0 virtual-circuit-id 1
The preceding configuration is for a T1 interface. To configure an E1 interface, use the
E1 interface parameters. The following output shows this configuration.
regress@R7# show neighbor 2.2.2.2
}
Related
Documentation
Layer 2 Circuits Configuration Guide
223
Configuring Inverse Multiplexing for ATM (IMA)

Inverse multiplexing for ATM (IMA) is a standardized technology used to transport ATM
traffic over a bundle of T1 or E1 interfaces, also known as an IMA Group, allowing for an
increase in the bandwidth capacity. When you configure IMA on ACX Series routers, you
must configure the following:
The aggregated device countThe device count is the number of IMA group interfaces
created on the CT1 or CE1 interfaces. The logical ATM interface that is part of the IMA
group has the following naming format: at-fpc/pic/port with the port number taken
from the last port on the MIC plus 1. For example, on the ACX2000 router with a 16-port
built-in T1/E1 TDM MIC, the IMA group interface numbering starts with at-0/0/16 and
increments by 1 to at-0/0/17, and so on. On the ACX1000 router with an 8-port built-in
T1/E1 TDM MIC, the IMA group interface numbering starts with at-0/0/8 and increments
by 1 to at-0/0/9, and so on
The framing modeEmulation is a mechanism that duplicates the essential attributes

of a service, such as T1 or E1, over a packet-switched network. The built-in channelized
T1 and E1 interfaces (CT1 and CE1) on the ACX Series routers can be configured to work
in either T1 or E1 mode, and these child T1 and E1 interfaces can be configured to carry
ATM services over the packet-switched network.
One full T1 or E1 interface on the channelized CT1 or CE1 interfaceThe built-in

channelized interface is a non-configurable interface that requires a child T1 or E1 or
ATM interface on which you configure the parameters.
The T1 or E1 interface as a member of the IMA group of the respective IMA linkEach
child T1 or E1 interface of a channelized CT1 or CE1 interface is the physical interface
over which the ATM signals are carried. This T1 or E1 interface must be specified as a
member of an IMA group so that the IMA link will work.
IMA group interface configurationEach IMA group interface (at-fpc/pic/port) must

be configured with all ATM properties for it to work properly: logical link-layer
encapsulation type, the circuit cross-connect protocol suite, and the entire ATM device
must be dedicated to the ATM cell relay circuit.
Configure IMA on built-in channelized T1 and E1 interfaces:
224
1.
Configure the framing mode:

user@host# set framing (t1 | e1)
For example, to set E1 framing:
[edit chassis fpc 0 pic 0
user@host# set framing e1
This configuration is for E1 framing, which results in the PIC running at the E1 interface
speed. To configure T1 framing, use the t1 option. The following output shows this
configuration:
[edit]
fpc 0 {
pic 0 {
framing e1;
}
}
The following output shows eight CE1 interfaces created on an ACX1000 router:
user@host# run show interfaces terse
Interface
Admin Link Proto
ce1-0/0/0
up
up
ce1-0/0/1
up
up
ce1-0/0/2
up
up
ce1-0/0/3
up
up
ce1-0/0/4
up
up
ce1-0/0/5
up
up
ce1-0/0/6
up
up
ce1-0/0/7
up
up
Local
Remote
After a PIC is brought online and depending on the framing option used (t1 or e1), on
the ACX2000 router, 16 CT1 or 16 CE1 interfaces are created; on the ACX1000 router,
8 CT1 or 8 CE1 interfaces are created.
2. Configure the aggregated device count:

user@host# set aggregated-devices ima device-count number
For example:
[edit chassis fpc 0 pic 0
user@host# set aggregated-devices ima device-count 2
This configuration creates two IMA group interfaces on the Routing Engine. The
following output shows this configuration:
[edit]
fpc 0 {
pic 0 {
aggregated-devices {
ima {
device-count 2;
}
}
225
}
}
The following output shows the two IMA group interfaces created on an ACX1000
router with eight built-in channelized interfaces so the IMA group interface naming
starts with port 8, at-0/0/8 and increments by one to at-0/0/9:
user@host> show interfaces terse
Interface
Admin
ce1-0/0/0
up
e1-0/0/0
up
ce1-0/0/1
up
e1-0/0/1
up
ce1-0/0/2
up
ce1-0/0/3
up
ce1-0/0/4
up
ce1-0/0/5
up
ce1-0/0/6
up
ce1-0/0/7
up
at-0/0/8
up
at-0/0/9
up
Link Proto
up
up
up
up
up
up
up
up
up
up
up
up
Local
Remote
NOTE: When you change the aggregated device count, all interfaces on
the MIC are restarted.
3. Configure at least one full T1 or E1 interface on the channelized CE1 or CT1 interface:
[edit interfaces (ct1 | ce1)-fpc/pic /port]

user@host# set no-partition interface-type e1
In this example, you configure two full E1 interfaces because you have two IMA groups
configured in the previous step:
[edit interfaces ce1-0/0/0
[edit interfaces ce1-0/0/1
The following output shows this configuration. Notice that on each ce1 interface, a
corresponding e1 interface is created with the same fpc/pic/port parameters as its
parent ce1 interface:
[edit]
ce1-0/0/0 {
no-partition interface-type e1;
}
e1-0/0/0 {
}
ce1-0/0/1 {
no-partition interface-type e1;
}
e1-0/0/1 {
}
user@host> show interfaces terse
Interface
Admin Link Proto
226
Local
Remote
ce1-0/0/0
e1-0/0/0
ce1-0/0/1
e1-0/0/1
ce1-0/0/2
ce1-0/0/3
ce1-0/0/4
ce1-0/0/5
ce1-0/0/6
ce1-0/0/7
at-0/0/8
at-0/0/9
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
4. Specify the T1 or E1 interface as a member of the IMA group of the respective IMA link
(at-0/0/8 or at-0/0/9):
[edit interfaces (e1 | t1)-fpc/pic /port]
user@host# set ima-link-options group-id group-id
In this example, you configure IMA encapsulation on two E1 interfaces because you
have set up two IMA groups in Step 3.
[edit interfaces e1-0/0/0
user@host# set ima-link-options group-id 8
[edit interfaces e1-0/0/1
user@host# set ima-link-options group-id 9
[edit]
e1-0/0/0 {
ima-link-options group-id 8;
encapsulation ima;
}
e1-0/0/1 {
ima-link-options group-id 9;
encapsulation ima;
}
5. For each IMA group interface, configure a logical link-layer encapsulation type
(encapsulation atm-ccc-cell-relay) and the circuit cross-connect protocol suite (family

ccc), then dedicate the entire ATM device to the ATM cell relay circuit (allow-any-vci):
[edit interfaces at-fpc/pic /port unit logical-unit-number]
user@host# encapsulation atm-ccc-cell-relay
user@host# family ccc
user@host# allow-any-vci
In this example, you configure these statements on the two IMA group interfaces
at-0/0/8 and at-0/0/9.
[edit]
at-0/0/8 {
unit 0 {
allow-any-vci;
227
family ccc;
}
}
at-0/0/9 {
unit 0 {
allow-any-vci;
family ccc;
}
}
6. Verify that the interfaces are up:
The following output shows the channelized CE1 interface:

user@host> show interfaces ce1-0/0/0
Physical interface: ce1-0/0/0, Enabled, Physical link is Up
Interface index: 128, SNMP ifIndex: 530
Link-level type: Controller, Clocking: Internal, Speed: E1, Loopback: None,
Framing: G704,
Parent: None
Device flags
: Present Running
Link flags
: None
CoS queues
Last flapped
: 2012-04-07 13:42:45 PDT (01:52:59 ago)
DS1
alarms
: None
DS1
defects : None
Line encoding: HDB3
The following output shows the child E1 interfaces:

user@host> show interfaces e1-0/0/0
Physical interface: e1-0/0/0, Enabled, Physical link is Up
Link-level type: IMA-Link, MTU: 1504, Speed: E1, Loopback: None, FCS: 16,
Parent: ce1-0/0/0 Interface index 128
Device flags
: Present Running
Link flags
: None
CoS queues
Last flapped
: 2012-04-07 15:34:15 PDT (00:01:49 ago)
Input rate
: 0 bps (0 pps)
Output rate
: 0 bps (0 pps)
IMA Link alarms
: None
IMA Link defects : None
IMA Link state
: Line: OK, NE-Rx: Active, NE-Tx: Active, FE-Rx: Active,
FE-Tx: Active
DS1
alarms
: None
DS1
defects : None
Link-level type: IMA-Link, MTU: 1504, Speed: E1, Loopback: None, FCS: 16,
Parent: ce1-0/0/1 Interface index 130
Device flags
: Present Running
Link flags
: None
CoS queues
Last flapped
: 2012-04-07 16:19:25 PDT (00:04:48 ago)
Input rate
: 0 bps (0 pps)
228
Output rate
: 0 bps (0 pps)
IMA Link alarms
: None
IMA Link defects : None
IMA Link state
: Line: OK, NE-Rx: Active, NE-Tx: Active, FE-Rx: Active,
FE-Tx: Active
DS1
alarms
: None
DS1
defects : None
The following output shows the IMA group interfaces:

user@host> show interfaces at-0/0/8
Physical interface: at-0/0/8, Enabled, Physical link is Up
Link-level type: ATM-PVC, MTU: 2048, Speed: Unspecified, Loopback: None,
Payload scrambler: Enabled
Device flags
: Present Running
Link flags
: None
CoS queues
Current address: 84:18:88:c0:5a:08
Last flapped
: 2012-04-07 15:34:15 PDT (00:02:10 ago)
Input rate
: 0 bps (0 pps)
Output rate
: 0 bps (0 pps)
IMA Group alarms
: None
IMA Group defects : None
IMA Group state
: NE: Operational, FE: Operational
[edit]
Link-level type: ATM-PVC, MTU: 2048, Speed: Unspecified, Loopback: None,
Payload scrambler: Enabled
Device flags
: Present Running
Link flags
: None
CoS queues
Current address: 84:18:88:c0:5a:09
Last flapped
: 2012-04-04 21:16:08 PDT (15:25:39 ago)
Input rate
: 0 bps (0 pps)
Output rate
: 0 bps (0 pps)
IMA Group alarms
: None
IMA Group state
: NE: Operational, FE: Operational
Related
Documentation

Configuring E1 BERT Properties

This topic discusses BERT properties for the E1 interface specifically. For general
information about the Junos OS implementation of the BERT procedure, see Interface
Diagnostics.
You can configure an E1 interface or a CE1 or E1 partition on a channelized PIC to execute
a bit error rate test (BERT) when the interface receives a request to run this test. You
specify the duration of the test and the error rate to include in the bit stream by including
229
the bert-period and bert-error-rate statements at the [edit interfaces interface-name

e1-options] hierarchy level:
[edit interfaces interface-name e1-options]
bert-error-rate rate;
bert-period seconds;
By default, the BERT period is 10 seconds. You can configure the BERT period to last
from 1 through 239 seconds on some PICs and from 1 through 240 seconds on other PICs.
Standard CE1, standard E1, E1 IQ, and E1 IQE interfaces, and PICs partitioned to CE1 and
E1 channels, support an extended BERT period range, up to 86,400 seconds (24 hours),
and have a default BERT period value of 240 seconds.
NOTE: When configuring E1 and CE1 interfaces on 10-port Channelized E1/T1

IQE PICs, you must include the bert-period statement at the [edit interfaces
ce1-fpc/pic/port] hierarchy level.
NOTE: When configuring CE1 interfaces on the 16-port Channelized E1/T1

Circuit Emulation MIC (MIC-3D-16CHE1-T1-CE), you must include BERT
configuration options at the [edit interfaces ce1-fpc/pic/port] hierarchy level.
rate is the bit error rate. This can be an integer from 0 through 7, which corresponds to a
0
bit error rate from 10
(0, which corresponds to no errors) to 10
(1 error per 10 million
bits). The default is 0.
NOTE: The bit-error-rate statement in BERT procedure is not supported on

the 16-port Channelized E1/T1 Circuit Emulation MIC (MIC-3D-16CHE1-T1-CE).
Individual concatenated E1 interfaces do not support the bert-algorithm configuration

statement. For individual concatenated E1 interfaces, the bert-algorithm statement at
the [edit interfaces interface-name e1-options] hierarchy level is ignored. The algorithm
15
for the E1 BERT procedure is pseudo-2e15-o151 (pattern is 2 1, as defined in the CCITT/ITU
O.151 standard).
For channelized E1 intelligent queuing (IQ and IQE) interfaces, you can configure the
BERT algorithm by including the bert-algorithm statement at the [edit interfaces
ce1-fpc/pic/port e1-options] or [edit interfaces e1-fpc/pic/port e1-options] hierarchy level:
[edit interfaces ce1-fpc/pic/port e1-options]
bert-algorithm algorithm;
[edit interfaces e1-fpc/pic/port e1-options]
For a list of supported algorithms, enter a ? after the bert-algorithm statement; for
example:
[edit interfaces ce1-0/0/0 e1-options]
user@host# set bert-algorithm ?
230
Possible completions:
pseudo-2e11-o152 Pattern is 2^11 -1 (per O.152 standard)
pseudo-2e15-o151 Pattern is 2^15 - 1 (per O.151 standard)
Related
Documentation
Interface Diagnostics
Interface Diagnostics Operational Mode Commands
Configuring T1 BERT Properties

This section discusses BERT properties for the T1 interface specifically. For general
information about the Junos implementation of the BERT procedure, see Interface
Diagnostics.
You can configure a T1 interface or partitioned CT1 or T1 channel to execute a bit error
rate test (BERT) when the interface receives a request to run this test. You specify the
duration of the test and the error rate to include in the bit stream by including the
bert-period and bert-error-rate statements at the [edit interfaces interface-name t1-options]
hierarchy level:
[edit interfaces interface-name t1-options]
bert-error-rate rate;
bert-period seconds;
seconds is the duration of the BERT procedure. The test can last from 1 through
239 seconds; the default is 10 seconds. Standard CT1, standard T1, T1 IQ, and T1 IQE
interfaces, and PICs partitioned to CT1 and T1 channels, support an extended BERT period
range, up to 86,400 seconds (24 hours), and have a default BERT period value of 240
seconds.
NOTE: When configuring T1 and CT1 interfaces on 10-port Channelized E1/T1

IQE PICs, the bert-period statement must be included at the [edit interfaces
ct1-fpc/pic/port] hierarchy level.
NOTE: When configuring CT1 interfaces on the 16-port Channelized E1/T1

Circuit Emulation MIC (MIC-3D-16CHE1-T1-CE), you must include BERT
configuration options at the [edit interfaces ct1-fpc/pic/port] hierarchy level.
rate is the bit error rate. This can be an integer from 0 through 7, which corresponds to a
0
bit error rate from 10
(1 error per bit) to 10
(1 error per 10 million bits).
algorithm is the pattern to send in the bit stream. On T1 interfaces, you can also select
the pattern to send in the bit stream by including the bert-algorithm statement at the
[edit interfaces interface-name interface-options] hierarchy level:
231
[edit interfaces interface-name interface-options]

For a list of supported algorithms, enter a ? after the bert-algorithm statement; for
example:
[edit interfaces t1-0/0/0 t1-options]
user@host# set bert-algorithm ?
Possible completions:
pseudo-2e11-o152 Pattern is 2^11 -1 (per O.152 standard)
NOTE: The bit-error-rate statement in BERT procedure is not supported on

the 16-port Channelized E1/T1 Circuit Emulation MIC (MIC-3D-16CHE1-T1-CE).
For specific hierarchy information, see individual interface types. For information about
running the BERT procedure, see the Junos OS System Basics Configuration Guide.
Related
Documentation
Interface Diagnostics
Interface Diagnostics Operational Mode Commands
Configuring E1 Loopback Capability

You can configure loopback capability between the local E1 interface and the remote
channel service unit (CSU), as shown in Figure 17 on page 232. You can configure the
loopback to be local or remote. With local loopback, the E1 interface can transmit packets
to the CSU, but receives its own transmission back again and ignores data from the CSU.
With remote loopback, packets sent from the CSU are received by the E1 interface,
forwarded if there is a valid route, and immediately retransmitted to the CSU.
Figure 17: Remote and Local E1 Loopback
To configure loopback capability on an E1 interface, include the loopback statement at

the [edit interfaces interface-name e1-options] hierarchy level:
[edit interfaces interface-name e1-options]
loopback (local | remote);
232
Packets can be looped on either the local router or the remote CSU.
To exchange BERT patterns between a local router and a remote router, include the
loopback remote statement in the interface configuration at the remote end of the link.
From the local router, you issue the test interface command.
For more information about configuring BERT, see Interface Diagnostics. For more
information about using operational mode commands to test interfaces, see the Junos
OS Operational Mode Commands.
To turn off the loopback capability, remove the loopback statement from the configuration:
[edit]
user@host# delete interfaces e1-fpc/pic/port e1-options loopback
You can determine whether there is an internal problem or an external problem by

checking the error counters in the output of the show interface interface-name extensive
command:
user@host> show interfaces interface-name extensive
Example: Configuring E1 Loopback Capability

To determine whether a problem is internal or external, loop packets on both the local
and the remote router. To do this, include the no-keepalives and encapsulation cisco-hdlc
statements at the [edit interfaces interface-name] hierarchy level and the loopback local
statement at the [edit interfaces interface-name e1-options] hierarchy level.
With this configuration, the link stays up, so you can loop ping packets to a remote router.
The loopback local statement causes the interface to loop within the PIC just before the
data reaches the transceiver.
[edit interfaces]
e1-1/0/0 {
no-keepalives;
encapsulation cisco-hdlc;
e1-options {
loopback local;
}
unit 0 {
family inet {
address 10.100.100.1/24;
}
}
}
NOTE: To configure the CE1 loopback capability on the 16-port Channelized

E1/T1 Circuit Emulation MIC (MIC-3D-16CHE1-T1-CE), include the loopback
statement at the [edit interfaces ce1-fpc/pic/port] hierarchy level.
Related
Documentation
Configuring T1 Loopback Capability on page 234
Performing a Loopback Test on an Interface
233
Configuring T1 Loopback Capability

You can configure loopback capability between the local T1 interface and the remote
channel service unit (CSU), as shown in Figure 18 on page 234. You can configure the
loopback to be local or remote. With local loopback, the T1 interface can transmit packets
to the CSU, but receives its own transmission back again and ignores data from the CSU.
With remote loopback, packets sent from the CSU are received by the T1 interface,
forwarded if there is a valid route, and immediately retransmitted to the CSU.
Figure 18: Remote and Local T1 Loopback
To configure loopback capability on a T1 interface, include the loopback statement at

the [edit interfaces interface-name t1-options] hierarchy level:
[edit interfaces interface-name t1-options]
loopback (local | payload | remote);
Packets can be looped on either the local router or the remote CSU. Local and remote
loopback loop back both data and clocking information.
To exchange BERT patterns between a local router and a remote router, include the
loopback remote statement in the interface configuration at the remote end of the link.
From the local router, issue the test interface command.
For more information about configuring BERT, see Interface Diagnostics. For more
information about using operational mode commands to test interfaces, see the Junos
OS Operational Mode Commands.
For channelized T3, T1, and NxDS0 intelligent queuing (IQ) interfaces only, you can include
the loopback payload statement in the configuration to loop back data only (without
clocking information) on the remote routers PIC. In payload loopback, overhead is
recalculated. For T3 IQ interfaces, you can include the loopback payload statement at
the [edit interfaces ct3-fpc/pic/port] and [edit interfaces t3-fpc/pic/port:channel] hierarchy
levels. For T1 interfaces, you can include the loopback payload statement in the
configuration at the [edit interfaces t1-fpc/pic/port:channel] hierarchy level; it is ignored
if included at the [edit interfaces ct1-fpc/pic/port] hierarchy level. For NxDS0 interfaces,
payload and remote loopback are the same. If you configure one, the other is ignored.
NxDS0 IQ interfaces do not support local loopback.
To determine whether a problem is internal or external, you can loop packets on both
the local and the remote router. To do this, include the no-keepalives and encapsulation
cisco-hdlc statements at the [edit interfaces interface-name] hierarchy level and the
234
loopback local statement at the [edit interfaces interface-name t1-options] hierarchy level,
as shown in the following example:

[edit interfaces]
t1-1/0/0 {
no-keepalives;
encapsulation cisco-hdlc;
t1-options {
loopback local;
}
unit 0 {
family inet {
address 10.100.100.1/24;
}
}
}
NOTE: To configure the CT1 loopback capability on the 16-port Channelized

E1/T1 Circuit Emulation MIC (MIC-3D-16CHE1-T1-CE), use the loopback
statement at the [edit interfaces ct1-fpc/pic/port] hierarchy level.
With this configuration, the link stays up, so you can loop ping packets to a remote router.
The loopback local statement causes the interface to loop within the PIC just before the
data reaches the transceiver.
To turn off the loopback capability, remove the loopback statement from the configuration:
[edit]
user@host# delete interfaces t1-fpc/pic/port t1-options loopback
You can determine whether there is an internal problem or an external problem by

checking the error counters in the output of the show interface interface-name extensive
command, for example:
user@host> show interfaces t1-fpc/pic/port extensive
Related
Documentation
Configuring E1 Loopback Capability on page 232
Performing a Loopback Test on an Interface
235
236
CHAPTER 13
Timing and Synchronization
Automatic Clock Selection Overview on page 238
Clock Sources for the ACX Series Universal Access Routers on page 239
External Clock Synchronization Overview for ACX Series Routers on page 240
Configuring External Clock Synchronization for ACX Series Routers on page 242
Global Positioning System (GPS) and the ACX Series Routers on page 248
PTP over Ethernet on ACX Series Routers Overview on page 248
Guidelines for Configuring PTP over Ethernet on page 250
Configuring a PTP Master Boundary Clock on page 254
Configuring a PTP Slave Clock on page 257
G.703 2.048MHz Signal Type for BITS Interfaces Overview on page 259
Configuring PTP Multicast Master and Slave Ports for Ethernet Encapsulation on page 260
Configuring PTP Dynamic Ports for Ethernet Encapsulation on page 265
Ports on page 266
Example: Configuring a PTP Boundary Clock on page 273
Example: Configuring a PTP Boundary Clock With Unicast Negotiation on page 275
Example: Configuring an Ordinary Slave Clock With Unicast-Negotiation on page 279
Example: Configuring an Ordinary Slave Clock Without Unicast-Negotiation on page 281
Example: Disabling a PoE Interface on ACX2000 Routers on page 287
237
Automatic Clock Selection Overview

Automatic clock selection is the selection of the best quality clock source by the clock
source selection algorithm based on the Ethernet Synchronization Message Channel
(ESMC) Synchronization Status Message (SSM) quality level, the configured quality
level, and the priority.
Clock Source Selection Algorithm on page 238
Clock Selection and Quality Level on page 238
Selection Mode for the Incoming ESMC Quality on page 238
Clock Source Selection Algorithm

The clock source selection algorithm is triggered by the following events:
Changes in the received ESMC SSM quality level (QL)
Configuration changes. For example, the addition or deletion of a clock source, a change
to the QL mode, and so on.
Signal failure detected on the currently selected source.
When the router is configured with automatic clock selection, the system chooses up to
two best upstream clock sources. The system then uses the clock recovered from one
of the sources to lock the chassis clock. If an upstream clock with acceptable good quality
is not available or if the system is configured in free-run mode, the system uses the internal
oscillator.
Clock Selection and Quality Level

Automatic clock selection supports two modes: QL enabled and QL disabled.
QL disabled In this mode, the best clock is selected based on the configured ESMC
SSM QL. If the QL of the configured clocks are equal, the clock selection is based on
the configured priority. If both the configured QL and priority are equal, one of the
sources is randomly selected. Absence of the quality-mode-enable statement at the
[edit chassis synchronization] hierarchy level means that QL is disabled.
NOTE: The default setting is QL disable.
QL enabledIn this mode, the best clock is selected based on the incoming ESMC
SSM QL as long as the incoming QL is at least as good as the sources configured QL.
If the QLs are equal, the clock selection is based on the configured priority. If both the
received QL and the priority are equal, one of the sources is selected randomly.
Selection Mode for the Incoming ESMC Quality

Depending on the configuration, the clock source selection algorithm uses the configured
or received ESMC SSM quality level for clock selection. In both configured and received
selection modes, the interface qualifies for clock source selection only when the received
238
Chapter 13: Timing and Synchronization
ESMC SSM quality level on the interface is equal to or greater than the configured ESMC
SSM quality level for the interface.
Related
Documentation
synchronization
Clock Sources for the ACX Series Universal Access Routers

Clocking is an important feature on the ACX Series routers. The ACX Series routers can
be directly connected to different types of base stations (for example, base transceiver
station (BTS) in 2G, NodeB in 3G, and eNodeB in 4G networks) and different types of
routers that hand off time-division multiplexing (TDM, ATM, and Ethernet traffic to the
base station controller. ACX Series routers must extract the network clock from these
sources and pass on synchronization information to the base stations to help the routers
synchronize with the base station controller.
The ACX Series router timing hardware includes the following: two external clock inputs
(BITS and GPS), T1 and E1 ports (FPC 0, PIC 0), Gigabit Ethernet ports (RJ45), Gigabit
Ethernet ports (SFP) and 10-Gigabit Ethernet ports.
ACX Series router hardware and software support various clocking options:
The ACX series has an OCXO (Stratum 3E) type of oscillator.
External clocking includes a choice of GPS-based clock recovery (10 MHz) or BITS-T1
or E1 line synchronization (1.544 MHz and 2.048 MHz).
Synchronous Ethernet is supported based on the ITU G.8261, G.8262, and G.8264
specifications with line timing for ge and xe ports.
Synchronous Ethernet is a key requirement for circuit (emulation) services and mobile
radio access technologies. Synchronous Ethernet supports sourcing and transfer of
frequency for synchronization purposes for both wireless and wireline services and is
primarily used for mobile backhaul and converged transport.
Related
Documentation
The Precision Time Protocol (PTP) 1588v2compliant ordinary slave clock estimates
the time offset from the PTP master clock and tries to align its own time and frequency
with that of the master. PTP supports sourcing, transfer of frequency, and phase
synchronization. Also, PTP can be used for mobile backhaul when phase synchronization
is required, such as in Long Term Evolution-Time Division Duplex (LTE-TDD)
infrastructures.
Global Positioning System (GPS) and the ACX Series Routers on page 248
Synchronous Ethernet Overview on the ACX Series Universal Access Routers on page 34
on page 28
239
External Clock Synchronization Overview for ACX Series Routers

The ACX Series Universal Access routers support external clock synchronization and
automatic clock selection for Synchronous Ethernet, T1 or E1 line timing sources, and
external inputs. Configuring external clock synchronization and automatic clock selection
requires making clock selection, quality level (QL), and priority considerations. The clock
source selection algorithm is used to pick the two best upstream clock sources from
among all the various sources, based on system configuration and execution criteria such
as QL, priority, and hardware restrictions.
Automatic Clock Selection

With automatic clock selection, the system chooses up to two best upstream clock
sources. The system then uses the clock recovered from one of the sources to lock the
chassis clock. If an upstream clock with acceptable good quality is not available or if the
system is configured in free-run mode, the system uses the internal oscillator. The
following automatic clock selection features are supported for Synchronous Ethernet,
T1 or E1 line timing sources, and external inputs:
NOTE: Automatic clock selection does not apply to the IEEE 1588v2 recovered
clock.
Automatic clock selection is supported on the ACX Series routers. Automatic clock
selection of the best quality clock source is based on the Ethernet Synchronization
Message Channel (ESMC) Synchronization Status Message (SSM) quality level, the
configured quality level, and the priority. To configure automatic clock selection, include
the auto-select option at the [edit chassis synchronization] hierarchy level. You can also
configure the chassis to lock to the free-running local oscillator, which is the Stratum 3E
oscillator, by including the free-run option at the [edit chassis synchronization] hierarchy
level. The auto-select option enables the clock source selection algorithm to run. The
clock source selection algorithm is triggered by the following events:
Signal failure detected on the currently selected source
Changes in the received Ethernet Synchronization Message Channel (ESMC)

Synchronization Status Message (SSM) quality level (QL)
Configuration changes. For example, the addition or deletion of a clock source, a change
to the QL mode, and so on.
Automatic clock selection supports two modes on the ACX Series router: QL enabled
and QL disabled. To configure QL mode, include the quality-mode-enable statement at
the [edit chassis synchronization] hierarchy level.
240
QL disabledThe default setting is disable, which means that when the

quality-mode-enable statement is not configured, QL is disabled. In this mode, the best
clock is selected based on the configured ESMC SSM QL. If the QL of the best clocks
are equal, the clock selection is based on the configured priority. If both the configured
QL and priority are equal, one of the sources is randomly selected.
QL enabledIn this mode, the best clock is selected based on the incoming ESMC
SSM QL as long as the incoming QL is at least as good as the sources configured QL.
If the QLs are equal, the clock selection is based on the configured priority. If both the
received QL and the priority are equal, one of the sources is selected randomly.
Clock Source Selection Algorithm

The clock source selection algorithm uses the following logic and restrictions:
QL must be configured for non-external clocks, whether or not QL is enabled.
For network-option option-1, QL must be configured for external clocks (gps or bits)
whether or not QL is enabled.
In the case of network-option option-2, the default QL for the external clocks is QL_STU,
whether or not QL is enabled.
Configuring priority is optional. When not specified, gps has a higher default priority
than bits, and bits has a higher default priority than Gigabit Ethernet, 10-Gigabit Ethernet,
and T1 or E1 clock, which have the lowest default priority.
When QL is enabled, the received QL must be equal to or better than the configured
QL for that particular source or else that source will not be considered for clock
selection. This is so that a downstream client is guaranteed clock quality of a certain
level (that certain level being the configured QL).
During clock selection:
Related
Documentation
The active source with the highest QL is selected.
If QL is the same for two or more sources, then the source with the highest priority is
selected.
If two or more sources have the same QL and priority, then the currently active source,
if any, among these sources is selected.
If two or more sources have the same QL and priority, and none of these is currently
active, then any one of these may be selected.
If selection-mode is configured quality, then the configured (or default) QL of the

selected clock source is used for transmitting ESMC. If selection-mode is received
quality, then the received QL of the selected clock source is used for ESMC transmit.
In order to receive or transmit ESMC messages out of an interface, at least one logical
interface should be configured on that interface. If the interface is currently not
configured with a logical interface, you may do so using the set interfaces interface-name
unit 0 statement at the edit hierarchy level.
241
Configuring External Clock Synchronization for ACX Series Routers

The ACX Series Universal Access Routers support external clock synchronization for
Synchronous Ethernet, T1 or E1 line timing sources, and external inputs. Configuring
external clock synchronization requires making clock selection, quality level (QL), and
priority considerations. The clock source selection algorithm is used to pick the two best
upstream clock sources from among all the various sources, based on system
configuration and execution criteria such as QL, priority, and hardware restrictions.
To configure external synchronization on the router, include the synchronization statement
at the [edit chassis] hierarchy level.
Setting the Ethernet
equipment clock (EEC)
network type
The network type options set the frequency of the configured clock. When bits is
configured with option-1 on the ACX2000 router, the Synchronous Ethernet equipment
is optimized for 2048 Kbps, the speed of an E1 interface. When bits is configured with
option-2 on the ACX2000 router, the Synchronous Ethernet equipment is optimized for
1544 Kbps, the speed of a T1 interface. To set the clock type, use the following command:
set chassis synchronization network-option (option-1 | option-2)
For option-1, QL must be configured for external clocks (gps or bits) whether or not QL
is enabled. For option-2, the default QL for external clocks is QL_STU whether or not QL
is enabled.
The following output shows an example of the configuration of the network type with
option-1:
[edit]
synchronization {
network-option option-1;
}
Setting the clock mode
Clock mode sets the selection of the clock source from a free-running local oscillator or
from an external qualified clock. The default clock mode is auto-select, which uses the
best clock source. To set the clock mode, use the following command:
set chassis synchronization clock-mode (free-run | auto-select)
The following output shows an example of the configuration of the free-run option:
[edit]
synchronization {
clock-mode free-run;
}
NOTE: Automatic clock selection does not apply to the IEEE 1588v2 recovered
clock.
242
Setting the quality

mode
Specify the expected quality of the incoming clock on this source. The default is disable.
To set the synchronization quality mode, use the following command:
set chassis synchronization quality-mode-enable
The following output shows the configuration of the quality-mode-enable statement:

[edit]
synchronization {
quality-mode-enable;
}
Setting the selection

mode
The selection mode specifies whether the clock source selection algorithm should use
the configured or received ESMC SSM quality level for clock selection. In both selection
modes (configured-quality and received-quality), the interface qualifies for clock source
selection only when the received ESMC SSM quality level on the interface is equal to or
greater than the configured ESMC SSM quality level for the interface. To configure the
ESMC SSM quality-based clock source selection mode, use the following command:
set chassis synchronization selection-mode (configured-quality | received-quality)
The following output shows the configuration of the selection-mode statement with the
configured-quality option and the mandatory quality-mode-enable statement:
[edit]
synchronization {
selection-mode configured-quality;
quality-mode-enable;
}
NOTE: For the selection-mode statement configuration to take effect, you

must set the quality-mode-enable statement at the [edit chassis
synchronization] hierarchy level.
Setting the time

interval before a new
For routers operating with Synchronous Ethernet , set the time interval to wait before the
router selects a new clock source. After a change in the configuration, the time to wait
is between 15 and 60 seconds. After a reboot (restart), the time to wait is from 60 to 180
243
clock source is
selected
seconds. After clock recovery (switchover), the time to wait is from 30 to 60 seconds.
The default switchover time is 30 seconds and cold boot time is 120 seconds. To set the
time interval before a new clock source is selected, use the following command:
set chassis synchronization hold-interval (configuration-change | restart |
switchover) seconds
The following output shows the configuration of the hold-interval statement with the
configuration-change option:
[edit]
synchronization {
hold-interval {
configuration-change 20;
}
}
Setting the
synchronization
switching mode
The configured switching mode determines the clock source used. In revertive mode, the
system switches from a lower to a higher quality clock source whenever the higher clock
source becomes available. In non-revertive mode, the system continues to use the current
clock source as long as it is valid. The default mode is revertive. To set the synchronization
switchover mode, use the following command:
set chassis synchronization switchover-mode (revertive | non-revertive)
The following output shows the configuration of the switchover-mode statement with
the non-revertive option:
[edit]
synchronization {
switchover-mode non-revertive;
}
Setting the clock

source
The configured clock source is the candidate for selection by the clock selection algorithm.
The clock source can be the routers BITS T1 or E1 interface, GPS, or an interface with an
upstream clock source. To set the clock source, use the following command:
set chassis synchronization source (bits | gps | interfaces interface-name)
The following output shows the configuration of the source statement with the bits option
and the mandatory network-option statement. When bits is configured with option-1 on
the ACX2000 router, the Synchronous Ethernet equipment is optimized for 2048 Kbps,
the speed of an E1 interface.
[edit]
synchronization {
source {
bits;
}
}
244
NOTE: For the source statement configuration to take effect, you must set
the network-option (option-1 | option-2) statement at the [edit chassis
synchronization] hierarchy level.
The bits option is not supported on the ACX1000 router.
245
Setting ESMC transmit

interface
The ESMC transmit interface is the interface on which ESMC transmit messages are
permitted. To enable ESMC packet transmit, use the following command:
set chassis synchronization esmc-transmit interfaces interface-name
The following output shows the configuration of the esmc-transmit statement:

[edit]
synchronization {
esmc-transmit {
interfaces ge-0/1/0;
}
}
You can also enable ESMC on all interfaces with the interfaces all statement at the
preceding hierarchy level.
Setting the
synchronization source
quality level
Specify the expected quality of the incoming clock on this source. Specific quality-level
options are valid depending on the configured network-option; option-1 or option-2. Both
option-1 and option-2 SSM quality levels are supported. To set the synchronization source
quality level, use the following command:
quality-level (prc | prs |sec | smc | ssu-a | ssu-b | st2 | st3 | st3e | st4 |
stu | tnc)
The following output shows the configuration of the quality-level statement configured
with the prc option:
[edit]
synchronization {
source {
bits {
quality-level prc;
}
}
}
Setting the
priority
Specify a priority level between 1 and 5. When not specified, gps has a higher priority than
bits,and bits has a higher default priority than other Gigabit Ethernet or 10 Gigabit Ethernet
clock sources, which have the lowest priority. To set the synchronization source priority,
use the following command:
priority number
The following output shows the configuration of the priority statement:

[edit]
synchronization {
source {
bits {
priority 2;
}
}
246
Setting the
wait to restore time
A wait-to-restore time can be configured for each port. When a ports signal transitions
out of the signal fail state, it must be fault free for the wait-to-restore time before it is
again considered by the selection process. The range is from 0 through 12 minutes. The
default time is 5 minutes.
To set the synchronization source wait-to-restore time, use the following command:
set chassis synchronization source interfaces interface-name wait-to-restore
minutes
The following output shows the configuration of the wait-to-restore statement:

[edit]
synchronization {
source {
interfaces ge-0/1/0 {
wait-to-restore 2;
}
}
}
Setting the
lockout
A lockout may be configured for any source. When a lockout is configured for a source,
that source will not be considered by the selection process. To set the synchronization
source lockout, use the following command:
request lockout
The following output shows the configuration of the request lockout statement:
[edit]
synchronization {
source {
bits {
request lockout;
}
}
}
Setting the forced

switch
Force a switch to the source provided that the source is enabled and not locked out. Only
one configured source may be force-switched. To set the forced switch, use the following
command:
request force-switch
The following output shows the configuration of the request force-switch statement:
[edit]
synchronization {
source {
247
bits {
request force-switch;
}
}
}
Related
Documentation
synchronization
Interface and Router Clock Sources Overview
Global Positioning System (GPS) and the ACX Series Routers

Global Positioning System (GPS) is a navigation aid system that uses signals from
satellites to calculate the actual position of a GPS-capable receiver. These signals are
not only used for determining the position of the receiver on Earth but also as a very
accurate time base. There are GPS receivers with 10-MHz clock frequency output
synchronized to a GPS satellite. The ACX Series router has a SubMiniature version B
(SMB) connector that can take 10-MHz sine-wave input from a GPS receiver. To configure
this 10-MHz clock from a GPS receiver as a candidate clock source for chassis
synchronization, include the gps statement and options at the [edit chassis synchronization
source] hierarchy level.
Related
Documentation
source
PTP over Ethernet on ACX Series Routers Overview

Precision Time Protocol (PTP) is supported over IEEE 802.3 or Ethernet links on ACX
Series routers. This functionality is supported in compliance with the IEEE 1588-2008
specification. PTP over Ethernet enables effective implementation of packet-based
technology that enables the operator to deliver synchronization services on packetbased mobile backhaul networks that are configured in Ethernet rings. Deployment of
PTP at every hop in an Ethernet ring by using the Ethernet encapsulation method enables
robust, redundant, and high-performance topologies to be created that enables a highly
precise time and phase synchronization to be obtained.
The ACX Series routers can be directly connected to different types of base stations (for
example, base transceiver station (BTS) in 2G, NodeB in 3G, and eNodeB in 4G networks)
and different types of routers that hand off time- division multiplexing (TDM), ATM, and
Ethernet traffic to the base station controller. ACX Series routers must extract the network
clock from these sources and pass on synchronization information to the base stations
to help the routers synchronize with the base station controller.
Most of the network deployments that use Ethernet contain a minimum of two Ethernet
rings, while some of the network topologies might also contain up to three Ethernet rings.
Consider a scenario in which the first ring contains aggregation routers (MX Series routers)
248
and the second ring contains access routers (ACX Series routers). In such a network,
about 10 or 12 nodes of MX Series routers and ACX Series routers are present in the
aggregation and access Ethernet rings.
Some of the 4G base stations that are connected to ACX Series routers need to receive
the timing and synchronization information in a packet-based form. Such base station
vendors support only packet interfaces that use Ethernet encapsulation for PTP packets
for time and phase synchronization. Therefore, any node (an ACX Series router) that is
directly connected to a 4G base station must be able to use the Ethernet encapsulation
method for PTP on a master port to support a packet-based timing capability.
PTP over Ethernet encapsulation also facilitates an easier, optimal network deployment
model than PTP over IPv4. Using IPv4, the nodes (master and slave devices) participate
in unicast negotiation in which the slave node is provisioned with the IP address of the
master node and requests unicast messages to be sent to it from the master node. A
master node is the router that functions as the PTP server where the master clock is
located and a slave node is the router that functions as the PTP client where the slave
clock is located. Because PTP over Ethernet uses multicast addresses, the slave node
automatically learns about the master nodes in the network. Also, the slave node is able
to immediately receive the multicast messages from the master node and can begin
sending messages to the master node without the need for any provisioning configuration.
An interface on which the master clock is configured is called a master interface and an
interface on which the slave clock is configured is called a slave interface. A master
interface functions as the master port and a slave interface functions as the slave port.
For PTP over Ethernet, apart from configuring a port or a logical interface to operate as
a master clock or a slave clock, you can also configure a port or a logical interface to
function as both a master clock and a slave clock. This type of port is called a dynamic
port, stateful port, or a bidirectional port. Such a stateful port enables the network to more
efficiently adapt to the introduction and failure of timing sources by forming the shortest
synchronization trees from a particular source. This behavior is implemented as defined
by the best master clock algorithm (BMCA) in the ITU-T G.8265.1 Precision time protocol
telecom profile for frequency synchronization specification.
On both MX Series and ACX Series routers, you can achieve the highest quality
performance if you configure every node in a synchronization chain as a PTP boundary
clock. In Ethernet ring-based topologies, you can configure a port or a logical interface
to function either as a master port or as a slave port to enable redundancy when a node
or link failure occurs. This dynamic port or dual-port functionality is in accordance with
the IEEE 1588-2008 standard and enables the implementation of PTP in data center or
financial applications.
Apart from enabling every node to be available for configuration as a PTP boundary clock,
it is also necessary to enable a logical interface to be configured either as a master port
or a slave port. When you configure a logical interface or even a shared IP address to be
a master port or a slave port, a PTP protocol stack can represent dynamic ports and the
PTP application selects the correct state (master or slave) for any specific port in the
system based on the output of the default PTP BMCA and the states of other ports in
the system.
249
While an ACX Series router supports the PTP over Ethernet functionality, a Brilliant Grand
Master such as an MX Series router or a TCA Series Timing Client does not support PTP
over Ethernet. In such a scenario, the ACX Series router functions as a boundary clock
with a PTP slave port using IPv4 as the encapsulation mode and master ports using
Ethernet as the encapsulation mode for PTP traffic. For example, consider an ACX Series
router named ACX1 to have two potential slave interfaces, one that is fixed as a slave-only
port using IPv4 on the link toward an MX Series router named MX1, and a dynamic port
that functions as a slave port using PTP over Ethernet on the link toward another ACX
Series router named ACX2. In addition, ACX1 also contains a port that is a master-only
port using PTP over Ethernet and connects to the base station.
Because PTP over Ethernet uses multicast addresses, a slave port can automatically
start receiving the multicast announce messages transmitted by the master ports on a
network and can also start communication with the master node with minimal or no
configuration. Unlike PTP over IPv4 where IP addresses are used to identify the master
and slave ports, with PTP over Ethernet, multicast MAC addresses are used in the
forwarding of PTP traffic. The IEEE 1588 standard defines two types of multicast MAC
addresses 01-80-C2-00-00-0E (link local multicast) and 01-1B-19-00-00-00 (standard
Ethernet multicast) for PTP over Ethernet operations.
Related
Documentation
Configuring PTP Multicast Master and Slave Ports for Ethernet Encapsulation on
page 260
Ports on page 266
Guidelines for Configuring PTP over Ethernet

Keep the following points in mind when you configure PTP over Ethernet for multicast
mode of transmission of PTP traffic:
250
You can configure a port or a logical interface to be a master clock for PTP over Ethernet
to provide packet-based synchronization to base stations that support time and phase
alignment; this configuration is compliant with Annexure F of the IEEE 1588-2008
specification.
Two multicast MAC addresses are used for PTP over Ethernet: 01-1B-19-00-00-00
and 01-80-C2-00-00-0E. The first address is a more standard Ethernet MAC address
that is expected to be flooded by all types of Ethernet bridges and switches and also
by a large number of base station vendors. A node with this MAC address can be a
node that does not process PTP packets. The second address is a reserved address in
the IEEE 802.1Q standard for Ethernet encapsulation that is required to be filtered and
not forwarded. This MAC address is used to ensure complete end-to-end support of
PTP, instead of transmission of packets through any network element that does not
support PTP. This address is the default address for G.8275.1 (PTP Profile for time or
phase distribution) and a node with this MAC address is a node that supports processing
of PTP packets.
Both of the MAC addresses, 01-1B-19-00-00-00 and 01-80-C2-00-00-0E, are

supported on multiple ports simultaneously to enable maximum flexibility and extension
of existing networks for future deployments. A single PTP port is configured for one of
the MAC addresses at a time.
PTP packets are sent with the unique MAC address assigned to each port as the MAC
source address. In the PTP packet, the Ethernet frame portion of the packet contains
the Destination MAC field. This field contains either of the two MAC addresses,
01-1B-19-00-00-00 or 01-80-C2-00-00-0E. Also, the Ethernet frame portion contains
the Source MAC field that contains the MAC address of the source port and the
Ethertype field that contains the PTP Ethertype value of 0x88F7. Apart from the
Ethernet frame, the PTP packet contains the PTP payload.
When you configure a port for PTP over Ethernet to be a slave port, a master port, or
both by having a dynamic port that can be either a master port or a slave port depending
on the states of the other ports in the PTP application, it is possible to build an easily
provisioned, redundant PTP service in an Ethernet ring where every node is configured
as a boundary clock.
A boundary clock can function as a slave clock to a device using IP (such as a TCA
Series Timing Client or an MX Series router) on one port and can also function as a
slave clock, a master clock, or both on other ports using Ethernet as the encapsulation
method. This behavior occurs within a single PTP domain number.
Best Master Clock Algorithm (BMCA) and the port state machine are supported to
determine the states of all the ports in a system and the correct state (master or slave)
for a certain port to process PTP packets.
PTP over Ethernet supports fully redundant and resilient ring-based configurations of
up to 10 nodes for a form of fourth-generation (4G) evolution known as Long-Term
Evolution-Time Division Duplex (LTE-TDD). ACX Series routers support a single node
or link failure and all nodes maintain a phase accuracy of plus or minus 1.5 microseconds
matching a common source.
You can configure the asymmetry value between the master port and the slave port,
which indicates a value to be added to the path delay value to make the delay
symmetric and equal to the path from the master port to the slave port, on either a
dynamic-state port or a slave-only port.
You cannot enable PTP over Ethernet on Ethernet interfaces that are configured with
802.1Q VLAN tags or contain a user-configured MAC address.
While you can configure unique PTP slave interfaces or slave ports with different
encapsulation mechanisms (such as IPv4 and Ethernet), the boundary clock can use
only a single encapsulation method for all of the master ports. Therefore, you must
define either IPv4 or Ethernet encapsulation for all the ports or logical interfaces that
can possibly function as boundary clock masters. Master ports select the link-local
flag based on each port.
The following limitations apply to the maximum number of ports that you can configure
when you use PTP over Ethernet:
251
Related
Documentation
252
You can configure a maximum of four slave ports on a router. A slave port or logical
interface is defined as any slave-only port configured for IPv4 or Ethernet, or any
dynamic port configured for Ethernet.
You can configure up to 32 master ports on a router. A master port or logical interface
is defined as any master-only port configured for IPv4 or Ethernet, or any dynamic
port configured for Ethernet.
Any logical interface that you configure as a dynamic port is considered to be both
a slave port and a master port, even if it functions only as a slave port or a master
port in a network, when the total number of slave ports and master ports on a router
is computed.
In PTP over IPv4 deployment, it is necessary to configure certain basic settings on a

PTP master port before the PTP slave ports to connect to the master port. PTP over
Ethernet offers a plug-and-play service because any PTP client starts receiving packets
and can request delay-response packets from the master port after you configure an
interface to be a master.
PTP over Ethernet is compatible with Junos OS releases earlier than Release 12.3X51.
When you perform an upgrade to Release 12.3X51 and later from a previous release on
an ACX Series router, you can modify the slave and master ports previously configured
for IPv4 to enable PTP over Ethernet based on your network needs.
You cannot configure a fully redundant PTP ring using IP. A fully redundant PTP ring
is supported only when Ethernet encapsulation is used.
Configuration of dynamic ports in conjunction with Synchronous Ethernet to enable

hybrid mode is not supported.
Multiple PTP timing domains are not supported for PTP over Ethernet, similar to PTP
over IPv4. Although a single node can contain interfaces configured for PTP over IPv4
and PTP over Ethernet, both of these interfaces must be part of the same PTP domain.
SONET/SDH networks define the ability to configure a local priority to a synchronization

source in the ITU G.781 standard. Addition of such locally configured priorities to PTP
sources to influence BMCA to determine a particular path for PTP packets is not
supported.
Although you can configure a slave port to use either IP or Ethernet simultaneously, a
single slave port is selected based on the announce messages it receives from the
master port and the PTP event packets are exchanged only with a single master port.
The IPv4 unicast implementation of PTP enables you to limit the number of slave ports
that can be supported simultaneously in the system. With multicast Ethernet-based
implementation, in which the master port is not provisioned with the slave port
information, the master port cannot limit the number of slave ports that it services.
This control must be exercised with proper networking planning and design.
page 260
Ports on page 266
Configuring Precision Time Protocol Clocking

In a distributed network, you can configure Precision Time Protocol (PTP) master and
slave clocks to help synchronize the timing across the network. The synchronization is
achieved through packets that are transmitted and received in a session between the
master clock and the slave clock or clock client.
To configure Precision Time Protocol (PTP) options:
1.
In configuration mode, go to the [edit protocols ptp] hierarchy level.

[edit]
user@host# edit protocols ptp
2. Specify the clock as a boundary or ordinary clock. The boundary option signifies that
the clock can be both a master clock and a slave clock. The ordinary option signifies
that the clock is a slave clock.
[edit protocols ptp]
user@host# set clock-mode (boundary | ordinary)
3. (Optional) Configure the PTP domain with values from 0 through 127. The default
value is 0.
user@host# set domain domain-value
4. (Optional) Specify the DiffServ code point (DSCP) value (0 through 63) for all PTP
IPv4 packets originated by the router. The default value is 56.

user@host# set ipv4-dscp number
5. Specify the master clock parameters.

user@host# set master
For details about configuring the master clock parameters, see Configuring a PTP
Master Boundary Clock on page 254.
6. (Optional) Configure the priority value of the clock (0 through 255). This value is used
in selecting the best master clock. The priority1-value is advertised in the master clocks
announce message to clock clients. The default value is 128.
user@host# set priority1 priority1-value
7. (Optional) Configure the tie-breaker in selecting the best master clock (0 through
255). The priority2 value differentiates and prioritizes the master clock to avoid
confusion when the priority1-value is the same for different master clocks in a network.
The default value is 128.
253
user@host# set priority2 priority2-value

8. Specify the PTP slave clock parameters.

user@host# set slave
For information about configuring the slave clock options, see Configuring a PTP
Slave Clock on page 257.
9. (Optional) Enable unicast negotiation. Unicast negotiation is a method by which the
announce, synchronization, and delay response packet rates are negotiated between
the master clock and the clock client before a PTP session is established.
user@host# set unicast-negotiation
NOTE: Unicast negotiation, when enabled, does not allow you to commit
packet raterelated configurations.
Related
Documentation
Configuring a PTP Master Boundary Clock

On an ACX Series router, a Precision Time Protocol (PTP) master boundary clock sends
PTP messages to the clients (ordinary and boundary) so that they can establish their
relative time offset from this masters clock or clock reference. You cannot configure an
ordinary master clock on an ACX Series Router. The master boundary clock synchronizes
time through a boundary slave port. To configure a master boundary clock, you must
include the boundary statement at the [edit protocols ptp clock-mode] hierarchy level
and at least one master with the master statement and at least one slave with the slave
statement at the [edit protocols ptp] hierarchy level.
To configure a PTP master boundary clock, complete the following tasks:
Configuring the PTP Master Boundary Clock Parameters on page 254
Configuring a PTP Master Boundary Clock Interface on page 256
Configuring the PTP Master Boundary Clock Parameters

To configure the parameters of a PTP master boundary clock:
1.
254
Configure the clock mode.

user@host# set clock-mode boundary
2. Configure the master clock.

user@host# edit master
3. (Optional) Specify the log mean interval between announce messagesfrom 0
through 4. By default, one announce message is sent every two seconds. This
configuration is used for manual clock clients. The master boundary clock sends
announce messages to manual clock clients as specified in the announce-interval
value.
[edit protocols ptp master]
user@host# set announce-interval announce-interval-value
4. Configure the interface on which to respond to downstream PTP clients and slaves.

user@host# edit interface interface-name
For details about configuring the parameters for the master boundary clock interface,
see Configuring a PTP Master Boundary Clock Interface on page 256
5. (Optional) Specify the maximum log mean interval between announce
messagesfrom 0 through 4. The default value is 4.

user@host# set max-announce-interval max-announce-interval-value
6. (Optional) Specify the maximum log mean interval between delay-response

user@host# set max-delay-response-interval max-delay-response-interval-value
7. (Optional) Specify the maximum log mean interval between synchronization

user@host# set max-sync-interval max-sync-interval-value
8. (Optional) Specify the minimum log mean interval between announce messagesfrom
0 through 4. The default value is 0.

user@host# set min-announce-interval min-announce-interval
9. (Optional) Specify the minimum log mean interval between delay-response

user@host# set min-delay-response-interval min-delay-response-interval
10. (Optional) Specify the minimum log mean interval between synchronization

user@host# set min-sync-interval min-sync-interval-value
255
11. (Optional) Specify the log mean interval between synchronization messagesfrom
7 through 4. The default value is 6. This configuration is used for manual clock
clients. The master boundary clock sends synchronization messages to manual clock
clients as specified in the syn-interval-value statement.
user@host# set sync-interval sync-interval-value
After you have configured the PTP master boundary clock parameters, enter the commit
command from configuration mode. To complete the configuration of the master
boundary clock, complete Configuring a PTP Master Boundary Clock Interface on
page 256.
Configuring a PTP Master Boundary Clock Interface

After you have configured the master boundary clock parameters, complete the
configuration of the master boundary clock by configuring an interface to act in the role
of the master clock.
To configure a PTP master boundary clock interface:
1.
Configure the interface on which to respond to downstream PTP slaves or clients.

NOTE: For the configuration to work, the interface you specify must be
configured at the [edit interfaces interface-name] hierarchy level.
2. On this interface, configure downstream PTP clients.
[edit protocols ptp master interface interface-name]

user@host# edit unicast-mode
3. Configure the IP address of the remote PTP host, or configure a subnet mask so that
any host belonging to that subnet can join the master clock. You can configure up to
512 clients for each master boundary clock.
[edit protocols ptp master interface interface-name unicast-mode]
user@host# edit clock-client ip-address
NOTE: You can configure the maximum number of clients (512 ) in the
following combination:
Automatic clients 256.
Manual and secure clients 256Any combination of manual and secure

clients is allowed as long as the combined total amounts to 256.
4. Configure the IP address of the interface acting as the local PTP master.
[edit protocols ptp master interface interface-name unicast-mode clock-client

ip-address]
256
user@host# set local-ip-address local-ip-address

5. (Optional) When the unicast-negotiation statement is configured at the [edit protocols
ptp] hierarchy level, configure a clock client to immediately receive announce and
synchronization messages from the master boundary clock without unicast negotiation.
[edit protocols ptp master interface interface-name unicast-mode clock-client ip-address
local-ip-address local-ip-address]
user@host# set manual
6. Specify the encapsulation type for PTP packet transportIPv4. This statement is
mandatory.
[edit protocols ptp master interface interface-name unicast-mode]
user@host# set transport ipv4
After you have configured the PTP master clock interface, enter the commit command
Configuring a PTP Slave Clock

The slave port that you configure can be a Precision Time Protocol (PTP) boundary or
ordinary clock, depending on the configuration of the clock-mode statement at the [edit
protocols ptp] hierarchy level. An ordinary or boundary slave clock performs frequency
and phase recovery based on received and requested timestamps from a master clocka
grandmaster or a boundary clock master.
To configure a PTP slave clock, complete the following tasks:
Configuring the PTP Slave Clock Parameters on page 257
Configuring the PTP Slave Clock Interface on page 259
Configuring the PTP Slave Clock Parameters

To configure a PTP slave clock.
1.
Configure the clock mode:

user@host# set clock-mode (boundary | ordinary)
2. Configure the slave clock.

user@host# edit slave
3. (Optional) Specify the rate of announce messages that a PTP slave requests from
the master during a unicast-negotiation sessionfrom 0 through 4. The default value

is 1.
[edit protocols ptp slave]
257
NOTE: The configuration of the announce-interval statement is effective

only when the unicast-negotiation statement is also configured at the [edit
protocols ptp] hierarchy level.
4. (Optional) Specify the number of announce messages that a slaveconfigured on
an ACX Series routermust miss before an announce timeout is declaredfrom 2

through 10. The default value is 3.
user@host# set announce-timeout announce-timeout-value
5. (Optional) Override the default PTP clock class to Ethernet Synchronization Message
Channel (ESMC) mapping and specify the quality level for the PTP timing source.
user@host# set clock-class-to-quality-level-mapping quality-level (prc | prs |sec |
smc | ssu-a | ssu-b | st2 | st3 | st3e | st4 | stu | tnc)
6. (Optional) Enable retrieval of ESMC information from the PTP clock class.

user@host# set convert-clock-class-to-quality-level
7. (Optional) Specify the logarithmic mean interval in seconds between the delay request
messages sent by the slave to the masterfrom 6 through 3. The default value is
0.
user@host# set delay-request delay-request-value
8. (Optional) Specify the grant duration value. When unicast negotiation is enabled, the
local PTP slave requests announce, synchronization, and delay-response messages

from the master. In each request, the slave asks for the packets to be sent at a specified
rate and the slave provides a duration for which the rate is valid. The grant-duration
value is specified in seconds. The default grant duration is 300 seconds.
user@host# set grant-duration interval
9. Configure the interface for the slave.

For details about configuring the slave interface, see Configuring the PTP Slave Clock
Interface on page 259.
10. (Optional) Configure the log mean interval between synchronization messagesfrom
6 through -3. The default value is 6 or 64 synchronous interval messages sent per
second
258
After you have configured the PTP slave clock parameters, enter the commit command
from configuration mode. To complete the configuration of the slave clock, complete
Configuring the PTP Slave Clock Interface on page 259.
Configuring the PTP Slave Clock Interface

The slave clock interface responds to the upstream PTP master clock.
To configure the PTP slave clock interface:
1.
Configure the interface for the slave clock.

2. Configure the upstream unicast PTP master clock source parameters.
[edit protocols ptp slave interface interface-name]

3. Configure the IP address of the master, which acts as a source of time for this slave.
[edit protocols ptp slave interface interface-name unicast-mode]

user@host# edit clock-source ip-address
NOTE: To configure additional master clock sources for the slave, include
the clock-source statement up to four times. However, synchronization is
to only one master clock.
4. Specify the IP address of the interface acting as the local PTP slave port.
[edit protocols ptp slave interface interface-name unicast-mode clock-source ip-address]

user@host# set local-ip-address local-ip-address
configured with this IP address at the [edit interfaces interface-name]
hierarchy level.
5. Configure the encapsulation type for PTP packet transport. This statement is
mandatory.
[edit protocols ptp slave interface interface-name unicast-mode]
After you have configured the PTP slave clock interface, enter the commit command
G.703 2.048MHz Signal Type for BITS Interfaces Overview

The ITU-T Recommendation G.703, Physical/electrical characteristics of hierarchical
digital interfaces, is a standard method for encoding clock and data signals into a single
signal. This signal is then used to synchronize various data communications devices, such
as switches, routers and multiplexers at a data rate of 2.048 MHz. Both directions of the
259
G.703 signal must use the same signal type. To configure signal type parameters for a
building-integrated timing supply (BITS) interface, include the following statements at
the [edit chassis synchronization ] hierarchy level:
interfaces bits {
signal-type (2048khz | e1 | t1);
e1-options {
framing (g704 | g704-no-crc4);
}
t1-options {
framing (esf | sf);
}
}
}
Related
Documentation
synchronization (ACX Series)
show chassis synchronization on page 627
Configuring PTP Multicast Master and Slave Ports for Ethernet Encapsulation
On an ACX Series router, you can configure a Precision Time Protocol (PTP) master
boundary clock with IEEE 802.3 or Ethernet encapsulation of PTP messages to the clients
(ordinary and boundary) so that they can establish their relative time offset from this
master's clock or clock reference. PTP over Ethernet uses multicast addresses for
communication of PTP messages between the slave clock and the master clock. The
slave clock automatically learns of master clocks in the network, is immediately able to
receive the multicast messages from the master clock, and can begin sending messages
to the master clock without any pre-provisioning. The master boundary clock synchronizes
time through a slave boundary port.
To configure PTP over Ethernet with multicast master and slave ports, you must include
the multicast-mode transport 802.3 statement at the [edit protocols ptp master interface
interface-name] and [edit protocols ptp slave interface interface-name] hierarchy levels,
respectively.
To configure a PTP over Ethernet master boundary clock and slave boundary clock for
multicast transmission, complete the following tasks:
Configuring the PTP over Ethernet Master Boundary Clock Parameters on page 260
Configuring the PTP over Ethernet Master Boundary Clock Interface on page 262
Configuring the PTP over Ethernet Slave Clock Parameters on page 263
Configuring the PTP over Ethernet Slave Clock Interface on page 264
Configuring the PTP over Ethernet Master Boundary Clock Parameters

To configure the parameters of a PTP over Ethernet master boundary clock:
1.

260
2. Configure the master clock.

user@host# edit master
3. (Optional) Specify the log mean interval between announce messagesfrom 0
through 4. By default, one announce message is sent every two seconds. This
configuration is used for manual clock clients. The master boundary clock sends
announce messages to manual clock clients as specified in the announce-interval
value.
4. Configure the interface on which to respond to downstream PTP clients or slave ports.

For details about configuring the parameters for the master boundary clock interface,
see Configuring the PTP over Ethernet Master Boundary Clock Interface on page 262
5. (Optional) Specify the maximum log mean interval between announce

user@host# set max-announce-interval max-announce-interval-value
6. (Optional) Specify the maximum log mean interval between delay-response

user@host# set max-delay-response-interval max-delay-response-interval-value
7. (Optional) Specify the maximum log mean interval between synchronization

user@host# set max-sync-interval max-sync-interval-value
8. (Optional) Specify the minimum log mean interval between announce messagesfrom
0 through 4. The default value is 0.

user@host# set min-announce-interval min-announce-interval
9. (Optional) Specify the minimum log mean interval between delay-response

user@host# set min-delay-response-interval min-delay-response-interval
10. (Optional) Specify the minimum log mean interval between synchronization

user@host# set min-sync-interval min-sync-interval-value
11. (Optional) Specify the log mean interval between synchronization messagesfrom
7 through 4. The default value is 6. This configuration is used for manual clock
261
clients. The master boundary clock sends synchronization messages to manual clock
clients as specified in the syn-interval-value statement.
After you have configured the PTP master boundary clock parameters, enter the commit
command from configuration mode. To complete the configuration of the master
boundary clock, complete Configuring the PTP over Ethernet Master Boundary Clock
Configuring the PTP over Ethernet Master Boundary Clock Interface

After you configured the master boundary clock parameters for PTP over Ethernet with
multicast transmission of PTP traffic, complete the configuration of the master boundary
clock by configuring an interface to act in the role of the master clock.
To configure a PTP over Ethernet master boundary clock interface:
1.
Configure the interface on which to respond to downstream PTP slave ports or clients.
2. On this interface, configure multicast as the transmission mode of traffic for PTP
clients.
[edit protocols ptp master interface interface-name]
user@host# edit multicast-mode
3. Specify the encapsulation type for PTP packet transport as Ethernet or IEEE 802.3.
This statement is mandatory.

[edit protocols ptp master interface interface-name multicast-mode]
user@host# set transport 802.3
Alternatively, specify the encapsulation type as Ethernet with the link-local multicast
address to be used in the sending of PTP messages. If you specify the link-local
attribute, the master clock chooses either of the two MAC addresses defined in the
IEEE 1588-2008 standard. When you configure this option, the system attempts to
use the 01 -80-C2-00-00-0E MAC address (link-local multicast MAC address) for
multicast transmission. If this MAC address is not available, the 01-1B-19-00-00-00
address (standard Ethernet multicast address) is used as the second priority. The
standard Ethernet multicast address is used by default. You need to explicitly configure
the link-local multicast address.
[edit protocols ptp master interface interface-name multicast-mode]
user@host# set transport 802.3 link-local
After you have configured the PTP over Ethernet master clock interface, enter the commit
262
Configuring the PTP over Ethernet Slave Clock Parameters

An interface on which the master clock is configured is called a master interface and an
interface on which the slave clock is configured is called a slave interface. A master
interface functions as the master port and a slave interface functions as the slave port.
Because PTP over Ethernet uses multicast addresses, a slave port can automatically
start receiving the multicast announce messages transmitted by the master ports on a
network and can also start communication with the master port with minimal or no
configuration. You can optionally configure these settings for a slave port that
communicates with the master ports using PTP over Ethernet.
To configure a PTP over Ethernet slave clock.
1.

2. Configure the slave clock.

user@host# edit slave
3. (Optional) Specify the number of announce messages that a slave clock or
portconfigured on an ACX Series routermust miss before an announce timeout is

declaredfrom 2 through 10. The default value is 3.
user@host# set announce-timeout announce-timeout-value
4. (Optional) Specify the logarithmic mean interval in seconds between the delay request
messages sent by the slave port to the master portfrom 6 through 3. The default
value is 0.
user@host# set delay-request delay-request-value
5. Configure the interface for the slave clock.

For details about configuring the slave interface, see Configuring the PTP Slave Clock
6. (Optional) Configure the log mean interval between synchronization messagesfrom
6 through -3. The default value is 6, which means by default, 64 synchronous
interval messages sent per second.

After you have configured the PTP slave clock parameters, enter the commit command
in configuration mode. To complete the configuration of the slave clock, complete
Configuring the PTP over Ethernet Slave Clock Interface on page 264
263
Configuring the PTP over Ethernet Slave Clock Interface

The slave clock interface responds to the upstream PTP master clock.
To configure the PTP slave clock interface:
1.
Configure the interface for the slave clock.

2. Configure the upstream multicast PTP master clock source parameters.
[edit protocols ptp slave interface interface-name]


[edit protocols ptp slave interface interface-name multicast-mode]
[edit protocols ptp slave interface interface-name multicast-mode]
After you have configured the PTP over Ethernet slave clock interface, enter the commit
command in configuration mode.
Related
Documentation
264
Ports on page 266
Configuring PTP Dynamic Ports for Ethernet Encapsulation

For PTP over Ethernet, you can also configure a port to function as both a slave port and
a master port. This type of port is called a dynamic port, a stateful port, or a bidirectional
port. Such a dynamic port enables the transfer of frequency for synchronization services,
in addition to time and phase alignment, when PTP functionality is not hop-by-hop and
you have provisioned master and slave roles or interfaces.
To configure PTP over Ethernet with dynamic or bidirectional ports for multicast mode
of transmission, you must include the multicast-mode statement at the [edit protocols
ptp stateful interface interface-name] hierarchy level.
To enable a node to function as both a master and a slave port in PTP over Ethernet
networks:
1.
Configure the interface on which to respond to downstream PTP slave ports or clients.
[edit protocols ptp stateful]
2. Configure the upstream multicast PTP dynamic clock source parameters.
[edit protocols ptp stateful interface interface-name]


[edit protocols ptp stateful interface interface-name multicast-mode]
[edit protocols ptp stateful interface interface-name multicast-mode]
After you have configured the PTP over Ethernet slave clock interface, enter the commit
Related
Documentation
265
page 260
Ports on page 266
Ports
In PTP over Ethernet networks, the master sends the announce, synchronization, and
delay-response packets using the multicast method. If any unicast delay-request message
is received, the master disregards the message and does not send delay-response
messages to the slave. A PTP slave receives the multicast announce packets from the
master or multiple masters and determines the best master using Best Master Clock
Algorithm (BMCA). A slave receives and processes the synchronization from the selected
master clock. The slave sends delay-request messages to this master using the multicast
method and processes the delay-response messages from the master to establish
synchronization.
Both the link-local MAC address and the standard 802.3 multicast MAC address can be
present in a system. However, a PTP interface supports only one of the following at a
point in time:
Layer 2 multicast with link-local MAC address
Layer 2 multicast with standard multicast MAC address
PTP over IPv4
When you configure both IPv4 and Ethernet encapsulation, the unicast-negotiation
configuration applies only to IPv4 encapsulation. It is not effective for PTP over Ethernet
operation.
When you configure a logical interface by using the stateful statement at the [edit
protocols ptp] hierarchy level, each interface that you configure as a stateful or dynamic
port is considered to be both a master and a slave port. Although an ACX Series router
supports up to 32 master ports and 4 slave ports, you can configure only 4 unique logical
interfaces as potential PTP masters by using the stateful statement because the interface
is treated as both a slave and a master interface. You cannot configure the interface that
you specify to be a stateful or dynamic port with the master or slave statements.
This example shows how to configure a master port, slave port, and a dynamic port for
PTP over Ethernet and PTP over IPv4 encapsulation, and how to configure unicast and
multicast mode of transmission of PTP traffic among the master and slave nodes.
266
Overview on page 267
Verifying the PTP over Ethernet Multicast Dynamic, Master, and Slave
Settings on page 271
Requirements
An ACX Series router
Junos OS Release 12.3X51 or later
Overview
While an ACX Series router supports the PTP over Ethernet functionality, a Brilliant Grand
Master such as an MX Series router or a TCA Series Timing Client does not support PTP
over Ethernet. Consider a sample deployment in which an ACX Series router named ACX1
functions as a boundary clock with a PTP slave port using IPv4 as the encapsulation
mode and master ports using Ethernet as the encapsulation mode for PTP traffic. ACX1
contains two potential slave interfaces, one that is fixed as a slave-only port using IPv4
on the link toward an MX Series router named MX2, and a dynamic port that functions
as a slave using PTP over Ethernet on the link toward another ACX Series router named
ACX2. In addition, ACX1 also contains a port that is a master-only port using PTP over
Ethernet and connects to the base station.
In this example, the router uses either interface ge-0/2/0.0 or ge-0/2/1.0 as the selected
slave interface based on the announce messages received from the master and the port
that was selected using the Best Master Clock Algorithm (BMCA). The interface ge-0/1/4.0
is always in the master state. According to the IEEE 1588 specification, if port ge-0/2/0.0
is selected as the slave interface, interface ge-0/2/1.0 transitions to the master state. If
interface ge-0/2/1.0is selected as the slave port, interface ge-0/2/0.0 transitions to the
listening state. You can also configure the interface ge-0/1/4.0 as a slave only interface
for PTP over Ethernet, if necessary, for completeness of the configuration.
Configuration
In this example, you configure a master port, a slave port, and a dynamic port for PTP
over Ethernet and PTP over IPv4 encapsulation. You can also configure unicast and
multicast modes of transmission of PTP traffic among the master and slave nodes.
CLI Quick
Configuration
Configuring PTP over Ethernet for Multicast Master, Slave, and Dynamic
Ports on page 268
Results on page 270
level:
set interfaces ge-0/1/4 description to base-station
set interfaces ge-0/1/4 unit 0 family inet address 7.1.1.37/24
set interfaces ge-0/2/0 description to MX2
set interfaces ge-0/1/4 description to ACX2
set protocols ptp clock-mode boundary
267
set protocols ptp domain 110

set protocols ptp slave interface ge-0/2/0.0 unicast-mode transport ipv4
set protocols ptp slave interface ge-0/2/0.0 unicast-mode clock-source 110.1.1.250
local-ip-address 110.1.1.2
set protocols ptp master interface ge-0/1/4.0 multicast-mode transport 802.3
set protocols ptp stateful interface ge-0/2/1.0 multicast-mode transport 802.3
Configuring PTP over Ethernet for Multicast Master, Slave, and Dynamic Ports
Step-by-Step
Procedure
To configure the master, slave, and dynamic interfaces, and a boundary clock with unicast
and multicast mode of transmission of PTP packets in PTP over IPv4 and PTP over
Ethernet topologies:
1.
Configure the master interface, and enter edit mode for the interface.
[edit interfaces]
user@host#edit ge-0/1/4
2.
Configure a description for the interface.

[edit interfaces ge-0/1/4]
user@host#set description to base-station
3.
Configure a logical unit and specify the protocol family.

user@host#set unit 0 family inet
4.
Specify the address for the logical interface

[edit interfaces ge-0/1/4 unit 0 family inet]
user@host#set address 7.1.1.37/24
5.
Configure the slave interface, and enter edit mode for the interface.
[edit interfaces]
6.

user@host#set description to-MX2
7.

8.

9.
Configure the stateful interface, and enter edit mode for the interface.
[edit interfaces]
268
10.

user@host#set description to-ACX2
11.

12.

13.
Configure the clock mode as boundary clock.

14.
Specify the PTP domain value.

user@host# set domain 110
15.
Configure the local slave interface from which the boundary master receives time
and passes it on to the configured clock clients.
user@host# edit slave interface ge-0/2/0.0
16.
Configure the upstream unicast PTP master clock source parameters.

[edit protocols ptp slave interface ge-0/2/0.0]
17.
Configure the encapsulation type for PTP packet transport.

[edit protocols ptp slave interface ge-0/2/0.0 unicast-mode]
18.
Configure the PTP master parameters by specifying the IP address of the PTP
master clock and the IP address of the local interface.
[edit protocols ptp slave interface ge-0/1/0.0 unicast-mode]
user@host# set clock-source 110.1.1.250 local-ip-address 110.1.1.2
19.
Configure the master interface in this example.

user@host# edit master interface ge-0/1/4.0
20.
On the master interface, configure multicast transmission for downstream PTP

clock clients.
[edit protocols ptp master interface ge-0/1/4.0]
21.
On the master interface, configure the encapsulation type as Ethernet for PTP
packet transport.
[edit protocols ptp master interface ge-0/2/1.0 multicast-mode]
269
22.
Configure the dynamic or stateful interface in this example.

user@host# edit stateful interface ge-0/2/1.0
23.
On the dynamic interface, configure multicast transmission for downstream PTP

clock clients.
[edit protocols ptp stateful interface ge-0/2/1.0 ]
24.
On the dynamic interface, configure the encapsulation type as Ethernet for PTP
packet transport and the link-local multicast address to be used.
[edit protocols ptp stateful interface ge-0/2/1.0 multicast-mode]
Results
In configuration mode, confirm your configuration by entering the show command. If the
output does not display the intended configuration, repeat the configuration instructions
in this example to correct it.
user@host# show
clock-mode boundary;
domain 110;
slave {
unicast-mode {
transport ipv4;
clock-source 110.1.1.250 local-ip-address 110.1.1.2;
}
}
}
master {
multicast-mode {
transport 802.3;
}
}
}
stateful {
multicast-mode {
transport 802.3 link-local;
}
}
}
After you have configured the device, enter the commit command in configuration mode.
270
Verifying the PTP over Ethernet Multicast Dynamic, Master, and Slave Settings
Confirm that the configuration is working properly.
Verifying the PTP Clock Details on page 271
Verifying the Lock Status of the Slave on page 271
Verifying the PTP Options on the Slave on page 271
Verifying the PTP Options and the Current Status of the Master on page 272
Verifying the Number and Status of the PTP Ports on page 272
Verifying PTP Statistics on page 272
Verifying the PTP Clock Details

Purpose
Action
Meaning
Verify that the PTP clock is working as expected.

In operational mode, enter the run show ptp clock command to display comprehensive,
globally configured clock details.
The output displays the clock details, such as the encapsulation method used for
transmission of PTP traffic and the number of configured stateful or dynamic ports.
Although a dynamic port functions as either a slave or a master port, the value displayed
in the Stateful Ports field denotes the dynamic ports that you explicitly configured. The
number of dynamic ports is not computed and displayed in the fields that display the
explicitly configured master and slave ports. For more information about the run show
ptp clock operational command, see show ptp clock in the Junos OS Operational Mode
Commands.
Verifying the Lock Status of the Slave

Purpose
Action
Meaning
Verify that the slave clock is aligned to the master clock by checking the lock status of
the slave.
In operational mode, enter the run show ptp lock-status command to display the lock
status of the slave.
The output displays information about the lock status of the slave. The output shows
whether the slave is aligned to the master clock or not, and the interface name configured
for PTP on the slave. The Master Source Port field displays the address of the master
clock when PTP over IPv4 is configured and the multicast MAC address of the source
when PTP over Ethernet is configured. For more information about the run show ptp
lock-status operational command, see show ptp lock-status in the Junos OS Operational
Mode Commands.
Verifying the PTP Options on the Slave

Purpose
Verify the PTP options that are set on the slave and the current status of the master.
271
Action
Meaning
In operational mode, enter the run show ptp slave command to display the configured
slave.
The output displays information about the configured slave and the status of the slave.
For more information about the show ptp slave operational command, see show ptp
slave in the Junos OS Operational Mode Commands.
Verifying the PTP Options and the Current Status of the Master
Purpose
Verify the PTP options that are set for the master and its current status.
Action
In operational mode, enter the run show ptp master command to display the configured
options for the master.
Meaning
The output displays information about the configured master and the current status of
the master. For more information about the run show ptp master operational command,
see show ptp master in the Junos OS Operational Mode Commands.
Verifying the Number and Status of the PTP Ports

Purpose
Action
Meaning
Verify the number of PTP ports and their current status.

In operational mode, enter the run show ptp port command to display the configured
ports.
The output displays information about the number of ports created according to the
configuration and their current status. The name of the interface configured for PTP and
the number of times a stateful port transitioned from the slave to the master state and
vice versa is displayed. For more information about the run show ptp port operational
command, see show ptp port in the Junos OS Operational Mode Commands.
Verifying PTP Statistics

Purpose
Action
In operational mode, enter the run show ptp statistics command to display the statistical
information regarding the configured PTP clocks.
Meaning
The output displays brief or detailed information about the operation of configured PTP
clocks. Statistical parameters include information such as the total number of PTP
packets transmitted or received by a master or slave interface and the number of various
messages (such as announce and synchronization messages) that are sent between a
master and a slave. For more information about the show ptp statistics operational
command, see show ptp statistics in the Junos OS Operational Mode Commands.
Related
Documentation
272
Verify the statistical details of the PTP configuration.
page 260
Example: Configuring a PTP Boundary Clock

This example shows how to configure a Precision Timing Protocol (PTP) boundary clock.
A boundary clock must include the configuration of at least one master and at least one
slave. The boundary master receives time from a remote master through the slave, and
in turn passes that time on to clock clients, which are in a slave relationship to the
boundary master. In this example, you configure a master, slave, clock source, and clock
client.
Requirements
Overview
In this example, the slave clock or clock client immediately receives announce and
synchronization packets after completion of the configuration.
Configuration
CLI Quick
Configuration
level:
set protocols ptp master interface ge-1/0/0.0 unicast-mode transport ipv4
set protocols ptp master interface ge-1/0/0.0 unicast-mode clock-client 20.20.20.2/32
273
Step-by-Step
Procedure
To configure a boundary clock without unicast negotiation:
1.

2.
Configure the slave interface.

3.

4.

[edit protocols ptp slave interface ge-1/3/9.0 unicast-mode ]
5.
Configure the IP address of the master interface.

6.
Specify the IP address and subnet of the remote PTP host, and the IP address of
the local PTP master interface.
[edit protocols ptp master interface ge-1/0/0.0 ]
user@host# set protocols ptp master interface ge-1/0/0.0 unicast-mode clock-client
20.20.20.2/32 local-ip-address 20.20.20.1
NOTE: For the configuration to work, the master interface you specify
must be configured with this IP address at the [edit interfaces
interface-name] hierarchy level.
7.

[edit protocols ptp master interface ge-1/0/0.0 unicast-mode]
Results
user@host# show
slave {
274
unicast-mode {
transport ipv4;
}
}
}
master {
unicast-mode {
transport ipv4;
clock-client 20.20.20.2/32 local-ip-address 20.20.20.1;
}
}
}
After you have configured the device, enter the commit command from configuration
mode.
Related
Documentation
Example: Configuring a PTP Boundary Clock With Unicast Negotiation

This example shows how to configure a boundary clock with unicast negotiation turned
on and a mixture of manual, secure and automatic clock clients, which have a slave
relationship to the master boundary clock. The unicast negotiation applies to clock
sources, which are configured on the slave or clock client. Clock clients, configured on
the master, are not affected by unicast negotiation.
Note that in this example, unicast-negotiation is applicable only to clock-sources. For
clock clients the statement unicast-negotiation at the [edit protocols ptp] hierarchy level
is not effective.
Requirements
275
Overview
A PTP slave clock or clock client can join a master clock with and without unicast
negotiation. With unicast negotiation, the announce, synchronization, and delay response
packet rates are negotiated between the master and the slave or client before a PTP
session is established. Without unicast negotiation and after it is configured, the slave
or client immediately receives announce and synchronization packets.
A clock client is the remote PTP host, which receives time from the PTP master. The
following clock clients are configured in this example:
Secure clientA secure client is configured with an exact IP address, after which, it
joins a master clock through unicast negotiation. In this example, the clock client
clock-client 117.117.117.117/32 local-ip-address 109.109.109.53 is a secure client, which
means that only this specific host from the subnet can join the master clock through
a unicast negotiation .
Automatic clientAn automatic client is configured with an IP address, which includes

a subnet mask, indicating that any PTP host belonging to that subnet, can join the
master clock through a unicast negotiation. In this example, the clock client clock-client
109.109.109.0/24 local-ip-address 109.109.109.53 is an automatic client. Additionally,
this automatic client is configured on the same master clock
interface109.109.109.53as the secure client.
Manual clientA manual client does not use unicast negotiation to join the master
clock. The manual statement overrides the unicast-negotiation statement configured
at the [edit protocols ptp] hierarchy level. As soon as you configure a manual client, it
starts receiving announce and synchronization packets. In this example, the clock client
clock-client 7.7.7.7 local-ip-address 7.7.7.53 manual is the manual client and is configured
on a second master clock interface.
Configuration
A boundary clock must include the configuration of at least one master and at least one
slave. The boundary master receives time from a remote master through the slave, and
in turn passes that time on to clock clients, which are in a slave relationship to the
boundary master. In this example, you configure a boundary slave, two Precision Time
Protocol (PTP) boundary masters with three different kinds of clock clientsautomatic,
manual, and secure. Two of the clock clients are configured on the same boundary master.
CLI Quick
Configuration
level:
set protocols ptp unicast-negotiation
276

local-ip-address 7.7.7.53 manual
Step-by-Step
Procedure
To configure a boundary clock with unicast negotiation:
1.

2.
Enable unicast negotiation.

user@host# set unicast-negotiation
3.
Configure the local slave interface from which the boundary master receives time
and passes it on to the configured clock clients.
4.

5.

6.
Configure the PTP master parameters by specifying the IP address of the PTP
master clock and the IP address of the local interface.
user@host# set clock-source 10.10.10.50 local-ip-address 10.10.10.53
7.
Configure the first master interface in this example.

8.
On the first master interface, configure the downstream PTP clock clients.
[edit protocols ptp master interface ge-0/1/3.0 ]
9.
On the first master interface, configure the encapsulation type for PTP packet
transport.
277
10.
On the first master interface, configure the PTP master parameters by specifying
the exact IP address of the remote PTP host and the IP address of the local PTP
master interface.
user@host# set clock-client 117.117.117.117 local-ip-address 109.109.109.53
11.
On the first master interface, configure a second PTP master by specifying the IP
address and subnet of the second remote PTP host and the IP address of the local
PTP master interface.
user@host# set clock-client 109.109.109.0/24 local-ip-address 109.109.109.53
12.
Configure the second master interface with the following parameters: the
encapsulation type, the downstream PTP host, the IP address of the local PTP
master interface, and the manual statement so that this client does not use unicast
negotiation.
user@host# set interface ge-0/1/5.0 unicast-mode transport ipv4
user@host# set interface ge-0/1/5.0 unicast-mode clock-client 7.7.7.7
local-ip-address 7.7.7.53 manual
Results
user@host# show
unicast-negotiation;
slave {
unicast-mode {
transport ipv4;
}
}
}
master {
unicast-mode {
transport ipv4;
}
}
unicast-mode {
transport ipv4;
clock-client 7.7.7.7/32 local-ip-address 7.7.7.53 {
manual;
}
}
}
}
278
After you have configured the device, enter the commit command from configuration
mode.
Related
Documentation
Example: Configuring an Ordinary Slave Clock With Unicast-Negotiation

This example shows the base configuration of a Precision Time Protocol (PTP) ordinary
slave clock with unicast-negotiation on an ACX Series router.
Requirements
Overview
In this configuration, the ordinary slave clock uses unicast-negotiation and compensates
for some network asymmetry.
NOTE: The values in this example are for illustration purposes only. You can
set the values for each parameter according to your requirements.
Configuration
To configure an ordinary slave clock with unicast-negotiation, perform these tasks:
Configuring an ordinary slave clock with unicast-negotiation on page 280
Results on page 281
279
CLI Quick
Configuration
set ptp clock-mode ordinary

set ptp domain 110
set ptp unicast-negotiation
set ptp slave delay-request -6
set ptp slave announce-timeout 2
set ptp slave announce-interval 3
set ptp slave sync-interval -5
set ptp slave grant-duration 7200
set ptp slave interface ge-0/1/0.0 unicast-mode transport ipv4
set ptp slave interface ge-0/1/0.0 unicast-mode clock-source 10.10.10.50
local-ip-address 10.10.10.75 asymmetry -4500
Configuring an ordinary slave clock with unicast-negotiation

Step-by-Step
Procedure
1.
Configure the clock mode, domain, and unicast-negotiation:

user@host# set clock-mode ordinary domain 110 unicast-negotiation
2.
Configure the announce timeout and the announce interval:

user@host# set slave announce-timeout 2 announce-interval 3
3.
Configure the synchronization interval and the grant duration:

user@host# set slave sync-interval -5 grant-duration 7200
4.
Configure the slave interface:

5.
Configure the unicast transport mode:

user@host# set unicast-mode transport ipv4
6.
Configure the clock source:

user@host# edit unicast-mode clock-source 10.10.10.50 local-ip-address 10.10.10.75
7.
Configure the asymmetric path:

[edit protocols ptp slave interface ge-0/1/0.0 unicast-mode clock-source 10.10.10.50
local-ip-address 10.10.10.75]
user@host# set asymmetry -4500
8.
Verify the configuration:

[edit protocols ptp slave interface ge-0/1/0.0 unicast-mode clock-source 10.10.10.50
local-ip-address 10.10.10.75]
user@host# top
[edit]
[edit protocols]
user@host# show
See the output for the show command in the Results section.
280
Results
The following output shows the configuration of unicast-negotiation and compensation
for some network asymmetry. The unicast-negotiation statement includes the parameters
for the delay request, announce interval, synchronization interval, and grant duration
values. Interface ge-0/1/0.0 is configured to compensate for an asymmetric path to the
PTP master by subtracting 4.5 microseconds from the slave-to-master direction delay
calculations.
[edit protocols]
user@host# show
ptp {
clock-mode ordinary;
domain 110;
unicast-negotiation;
slave {
delay-request -6;
announce-timeout 2;
announce-interval 3;
sync-interval -5;
grant-duration 7200;
unicast-mode {
transport ipv4;
clock-source 10.10.10.50 local-ip-address 10.10.10.75 {
asymmetry -4500;
}
}
}
}
}
Related
Documentation
on page 28
slave
unicast-mode
Example: Configuring an Ordinary Slave Clock Without Unicast-Negotiation

This example shows the base configuration of a Precision Time Protocol (PTP) ordinary
slave clock without unicast-negotiation on an ACX Series router.
Requirements
281
Overview
In this configuration, unicast-negotiation is not configured, so the PTP slave has no control
over the rate of the negotiation. The PTP master (a Brilliant Grand Master or an MX Series
router) must be configured with the parameters of the PTP slave, such as announce,
synchronization, and delay-response packets to control the rate of the negotiation.
NOTE: The values in this example are for illustration purposes only. You can
set the values for each parameter according to your requirements.
Configuration
To configure an ordinary slave clock without unicast-negotiation, perform these tasks:
CLI Quick
Configuration
Configuring an ordinary slave clock without unicast-negotiation on page 282
Results on page 283
set protocols ptp clock-mode ordinary

set protocols ptp ipv4-dscp 46
Configuring an ordinary slave clock without unicast-negotiation

Step-by-Step
Procedure
1.

user@host# set clock-mode ordinary
2.
Configure the Differentiated Services code point (DSCP) value for all PTP IPv4
packets originated by the router:
user@host# set ipv4-dscp 46
3.
Configure the slave interface:

4.
Configure the unicast transport mode:

user@host# set unicast-mode transport ipv4
5.
Configure the clock source:

user@host# unicast-mode clock-source 12.1.1.4 local-ip-address 12.1.1.5
6.
Verify the configuration:

user@host# top
[edit]
282

[edit protocols]
user@host# show
See the output for the show command in the Results section.
Results
In this example, the PTP slave on the local interface ge-0/2/0 is assigned a local IP
address of 12.1.1.5. Unicast-negotiation is not configured so the PTP master must be
explicitly configured with the details of the PTP slave (12.1.1.5).
[edit protocols]
user@host# show
ptp {
clock-mode ordinary;
ipv4-dscp 46;
slave {
unicast-mode {
transport ipv4;
}
}
}
}
Related
Documentation
on page 28
slave
unicast-mode
Example: Configuring PoE on ACX2000 Routers

Power over Ethernet (PoE) ports supply electric power over the same ports that are used
to connect network devices. These ports allow you to plug in devices that need both
network connectivity and electric power, such as voice over IP (VoIP) phones, wireless
access points, and IP cameras.
This example shows how to configure PoE to deliver power up to 65 W on ACX2000
interfaces:
Verification on page 286
Requirements
This example uses the following software and hardware components:
283
Junos OS Release 12.2 or later for ACX Series routers
An ACX2000 router that supports PoE
Before you configure PoE, be sure you have:
Performed the initial router configuration. See ACX Series Autoinstallation Overview
on page 45,Verifying Autoinstallation on ACX Series Universal Access Routers on
page 49, and Boot Sequence (ACX Series Routers) on page 302 for details.
Overview
This example consists of a router that has eight ports. Only two portsge-0/1/3 and
ge-0/1/7support PoE, which means they provide both network connectivity and electric
power for powered devices such as VoIP telephones, wireless access points, and IP
security cameras that require power up to 65 W. The remaining six ports provide only
network connectivity. You use the standard ports to connect devices that have their own
power sources, such as desktop and laptop computers, printers, and servers.
Table 26 on page 284 details the topology used in this configuration example.
Table 26: Components of the PoE Configuration

Property
Settings
Hardware
ACX2000 router with 8 Gigabit Ethernet ports: Two PoE

interfaces (ge-0/1/3 and ge-0/1/7) and 6 non-PoE interfaces
(ge-0/1/0, ge-0/1/1, ge-0/1/2, ge-0/1/4, ge-0/1/5, ge-0/1/6).
VLAN name
default
Connection to a wireless access point (requires PoE)
ge-0/1/7
Power port priority
high
Maximum power available to PoE port
65 W
PoE management mode
high-power
Direct connections to desktop PCs, file servers, integrated

printer/fax/copier machines (no PoE required)
ge-0/1/0 through ge-0/1/2
Unused ports (for future expansion)
ge-0/1/4 through ge-0/1/6
Configuration
To configure PoE on an ACX2000 router:
CLI Quick
Configuration
To quickly configure this example, copy the following commands, paste them into a text
level.
set poe management high-power guard-band 19
284
set poe interface ge-0/1/3 priority high maximum-power 65 telemetries
Step-by-Step
Procedure
hierarchy. For instructions on how to do that, see Using the CLI Editor in Configuration
Mode in the CLI User Guide.
To configure PoE:
1.
Set the PoE management mode to high-power.

[edit]
user@host# set poe management high-power
NOTE:
Set the PoE management mode to high-power only when the power
requirement is more than 32 W and up to 65 W. If the power
requirement is less than or equal to 32 W, then you do not need to set
the PoE management mode to high-power.
2.
The default management mode is static. In this mode, the power

sourcing equipment can deliver power up to 32 W.
Reserve power wattage in case of a spike in PoE consumption.

[edit]
user@host# set poe guard-band 19
3.
Enable PoE.
[edit]
user@host# edit poe interface ge-0/1/3
4.
Set the power port priority.

[edit poe interface ge-0/1/3]
user@host# set priority high
5.
Set the maximum PoE power for a port.

user@host# set maximum-power 65
NOTE: Set the maximum PoE power for a port only when the power
requirement is more than 32 W and up to 65 W. If the power requirement
is less than or equal to 32 W, then you do not need to configure the
maximum PoE power.
6.
Enable the logging of PoE power consumption.

user@host# set telemetries
285
Results
In configuration mode, confirm your configuration by entering the show poe interface
ge-0/1/3 command. If the output does not display the intended configuration, repeat the
configuration instructions in this example to correct it.
[edit]
user@host# show poe interface ge-0/1/3
priority high;
maximum-power 65;
telemetries;
If you are done configuring the device, enter commit in configuration mode.
Verification
To confirm that the configuration is working properly, perform these tasks:
Verifying the Status of PoE Interfaces on page 286
Verifying the Telemetry Data (History) for the Specified Interface on page 286
Verifying PoE Global Parameters on page 287
Verifying the Status of PoE Interfaces

Purpose
Action
Verify that the PoE interfaces are enabled and set to the desired priority settings.
In operational mode, enter the show poe interface ge-0/1/3 command.
user@host> show poe interface ge-0/1/3
PoE interface status:
PoE interface
: ge-0/1/3
Administrative status
: Enabled
Operational status
: Powered-up
Power limit on the interface : 65 W
Priority
: High
Power consumed
: 6.6 W
Class of power device
: 0
Meaning
The show poe interface ge-0/1/3 command lists PoE interfaces configured on the
ACX2000 router, with their status, priority, power consumption, and class.
Verifying the Telemetry Data (History) for the Specified Interface

Purpose
Action
Verify the PoE interface's power consumption over a specified period.

In operational mode, enter the show poe telemetries interface command.
For all records:
user@host> show poe telemetries interface ge-0/1/3 all
Interface Sl No
Timestamp
Power
1
Mon May 14 00:45:05 2012 14.2 W
2
Mon May 14 00:44:04 2012 14.2 W
3
Mon May 14 00:43:03 2012 14.2 W
286
Voltage
53.9 V
53.9 V
53.9 V
For a specific number of records:

user@host> show poe telemetries interface ge-0/1/3 2
Interface Sl No
Timestamp
Power
1
Mon May 14 00:45:05 2012 14.2 W
2
Mon May 14 00:44:04 2012 14.2 W
Meaning
Voltage
53.9 V
53.9 V
The telemetry status displays the power consumption history for the specified interface,
provided telemetry has been configured for that interface.
Verifying PoE Global Parameters

Purpose
Action
Verify global parameters such as guard band, power limit, and power consumption.
In operational mode, enter the show poe controller command.
user@host> show poe controller
Controller Maximum
Power
index
power
consumption
0
Meaning
Related
Documentation
130.0 W
14.2 W
Guard
band
Management
0 W
high-power
Status
Lldp
Priority
UP
The show poe controller command lists the global parameters configured on the router.
Example: Disabling a PoE Interface on ACX2000 Routers

This example shows how to disable PoE on all interfaces or on a specific interface.
Requirements
Before you begin:
Configure PoE on all interfaces. See Example: Configuring PoE on ACX2000 Routers
on page 283.
Overview
In this example, you disable PoE on all interfaces and on a specific interface, which in
this case is ge-0/1/3.
287
Configuration
Step-by-Step
Procedure
Disable PoE on all interfaces.

[edit]
user@host# set poe interface all disable
Disable PoE on a specific interface.

[edit]
user@host# set poe interface ge-0/1/3 disable
Verification
To verify the configuration is working properly, enter the show poe interface command.
user@host> show poe interface
Interface
ge-0/1/3
ge-0/1/7
Admin
status
Disabled
Disabled
Oper
Max
status power
Disabled 32.0W
Disabled 32.0W
Priority
Low
Low
Power
consumption
0.0W
0.0W
Class
0
0
user@host> show poe interface ge-0/1/3

PoE interface status:
PoE interface
Administrative status
Operational status
Power limit on the interface
Priority
Power consumed
Class of power device
Related
Documentation
288
:
:
:
:
:
:
:
ge-0/1/3
Disabled
Disabled
32.0 W
Low
0.0 W
0
CHAPTER 14
Upgrade and Installation
Dual-Root Partitioning ACX Series Universal Access Routers Overview on page 291
Understanding How the Primary Junos OS Image with Dual-Root Partitioning Recovers
on the ACX Series Router on page 293
Junos OS Release 12.2 or Later Upgrades with Dual-Root Partitioning on ACX Series
Routers on page 294
Installing Junos OS Using a USB Storage Device on ACX Series Routers on page 295
Installing Junos OS Upgrades from a Remote Server on ACX Series Routers on page 296
Example: Installing Junos OS and Configuring a Dual-Root Partition on ACX Series

Routers Using the CLI on page 296
Hardware Architecture Overview on page 299
Hardware Overview (ACX Series, M Series, MX Series, T Series, and TX Matrix

Routers) on page 300
Boot Sequence (ACX Series Routers) on page 302
Routing Engines and Storage Media Names (ACX Series, M Series, MX Series, PTX
Series, T Series, TX Matrix, TX Matrix Plus, and JCS 1200 Routers) on page 303
Upgrading Software Packages on page 305
Load and Commit the Configuration File on page 307
Checking the Current Configuration and Candidate Software Compatibility on page 308
Understanding System Snapshot on an ACX Series Router on page 308
Example: Taking a Snapshot of the Software and Configuration on page 309
ACX Series Autoinstallation Overview

Autoinstallation provides automatic configuration for a new router that you connect to
the network and turn on, or for a router configured for autoinstallation. The autoinstallation
process begins anytime a router is powered on and cannot locate a valid configuration
file in the CompactFlash (CF) card. Typically, a configuration file is unavailable when a
router is powered on for the first time, or if the configuration file is deleted from the CF
card. The autoinstallation feature enables you to deploy multiple routers from a central
location in the network.
289
For the autoinstallation process to work, you must store one or more host-specific or
default configuration files on a configuration server in the network and have a service
availabletypically Dynamic Host Configuration Protocol (DHCP)to assign an IP address
to the router.
Autoinstallation takes place automatically when you connect an Ethernet on a new
Juniper Networks router to the network and power on the router. To simplify the process,
you can explicitly enable autoinstallation on a router and specify a configuration server,
an autoinstallation interface, and a protocol for IP address acquisition.
This topic describes:
Supported Autoinstallation Interfaces and Protocols on page 290
Typical Autoinstallation Process on a New Router on page 290
Supported Autoinstallation Interfaces and Protocols

Before autoinstallation on a router can take place, the router must acquire an IP address
or a USB key. The protocol or protocols you choose for IP address acquisition determine
the router interface to connect to the network for autoinstallation. The router detects
the connected interface and requests an IP address with a protocol appropriate for the
interface. Autoinstallation is supported over an Ethernet LAN interface. For IP address
acquisition, the ACX Series router uses DHCP, BOOTP, or Reverse Address Resolution
Protocol (RARP) on an Ethernet LAN interface.
If the server with the autoinstallation configuration file is not on the same LAN segment
as the new router, or if a specific router is required by the network, you must configure
an intermediate router directly attached to the new router, through which the new router
can send HTTP, FTP, Trivial File Transfer Protocol (TFTP), BOOTP, and Domain Name
System (DNS) requests. In this case, you specify the IP address of the intermediate router
as the location to receive HTTP, FTP, or TFTP requests for autoinstallation.
Typical Autoinstallation Process on a New Router

When a router is powered on for the first time, it performs the following autoinstallation
tasks:
1.
The new router sends out DHCP, BOOTP, or RARP requests on each connected
interface simultaneously to obtain an IP address.
If a DHCP server responds, it provides the router with some or all of the following
information:
290
An IP address and subnet mask for the autoinstallation interface.
The location of the TFTP (typically), Hypertext Transfer Protocol (HTTP), or FTP
server on which the configuration file is stored.
The name of the configuration file to be requested from the HTTP, FTP, or TFTP
server.
The IP address or hostname of the HTTP, FTP, or TFTP server.
Chapter 14: Upgrade and Installation
If the DHCP server provides only the hostname, a DNS server must be available on
the network to resolve the name to an IP address.
The IP address of an intermediate router if the configuration server is on a different

LAN segment from the new router.
2. After the new router acquires an IP address, the autoinstallation process on the router
attempts to download a configuration file in the following ways:

a. If the configuration file is specified as a URL, the router fetches the configuration
file from the URL by using HTTP, FTP, or TFTP depending on the protocol specified
in the URL.
b. If the DHCP server specifies the host-specific configuration file (boot file)
hostname.conf, the router uses that filename in the TFTP server request. (In the
filename, hostname is the hostname of the new router.) The autoinstallation process
on the new router makes three unicast TFTP requests for hostname.conf. If these
attempts fail, the router broadcasts three requests to any available TFTP server
for the file.
c. If the new router cannot locate hostname.conf, the autoinstallation process unicasts
or broadcasts TFTP requests for a default router configuration file called

network.conf, which contains hostname-to-IP address mapping information, to
attempt to find its hostname.
d. If network.conf contains no hostname entry for the new router, the autoinstallation
process sends out a DNS request and attempts to resolve the new routers IP
address to a hostname.
e. If the new router can determine its hostname, it sends a TFTP request for the
hostname.conf file.
f.
If the new router is unable to map its IP address to a hostname, it sends TFTP
requests for the default configuration file router.conf.
3. After the new router locates a configuration file on a TFTP server, autoinstallation
downloads the file, installs the file on the router, and commits the configuration.
Related
Documentation
autoinstallation
Dual-Root Partitioning ACX Series Universal Access Routers Overview

Dual-root partitioning allows the ACX Series router to remain functional even if there is
file system corruption and to facilitate easy recovery of the file system. Dual-root
291
partitioning means that the primary and backup Junos OS images are kept in two
independently bootable root partitions. If the primary root partition becomes corrupted,
the system can still boot from the backup Junos OS image located in the other root
partition and remain fully functional.
NOTE: All ACX Series routers run with dual-root partitioning.
This section contains the following topics:
Boot Media and Boot Partition on the ACX Series Routers on page 292
Important Features of the Dual-Root Partitioning Scheme on page 292
Boot Media and Boot Partition on the ACX Series Routers

With dual-root partitioning, the ACX Series router first tries to boot the Junos OS from
the primary root partition and then from the backup root partition on the internal NAND
flash. If both primary and backup root partitions of the internal NAND flash fail to boot,
you must insert a USB storage media with a copy of the Junos OS from which to boot.
The following is the storage media available on the ACX Series router:
USB media emergency boot device
NOTE: The USB media device is not dual-root partitioned.
Dual, internal NAND flash device (first daOs1, then daOs2)
Important Features of the Dual-Root Partitioning Scheme

The dual-root partitioning scheme has the following important features:
Related
Documentation
292
The primary and backup copies of Junos OS images reside in separate partitions. The
partition containing the backup copy is mounted only when required. With the
single-root partitioning scheme, there is one root partition that contains both the
primary and the backup Junos OS images.
The request system software add command for a Junos OS package erases the contents
of the other root partition. The contents of the other root partition will not be valid
unless software installation is completed successfully.
Add-on packages, such as jais or jfirmware, can be reinstalled as required after a new
Junos OS image is installed.
The request system software rollback command does not delete the current Junos OS
image. It is possible to switch back to the image by issuing the rollback command again.

on the ACX Series Router
If the ACX Series Universal Access router is unable to boot from the primary Junos OS
image and boots up from the backup Junos OS image in the backup root partition, a
message appears on the console at the time of login indicating that the device has booted
from the backup Junos OS image.
login: user
Password:
***********************************************************************
**
**
**
WARNING: THIS DEVICE HAS BOOTED FROM THE BACKUP JUNOS IMAGE
**
**
**
**
It is possible that the active copy of JUNOS failed to boot up
**
**
properly, and so this device has booted from the backup copy.
**
**
**
**
Please re-install JUNOS to recover the active copy in case
**
**
it has been corrupted.
**
**
**
***********************************************************************
Because the system is left with only one functional root partition, you should immediately
restore the primary Junos OS image using one of the following methods:
Install a new image using the CLI. When you install the new image, the new image is
installed on only one partitionthe alternate partition, meaning the router is now running
two images. When you reboot, the router boots from the newly installed image, which
becomes the primary image. So now there are two different images running on the
router. Run the installation process again to update the other partition.
Use a snapshot of the backup root partition by entering the request system snapshot
slice alternate command. After the primary root partition is recovered using this method,
the device will successfully boot from the primary root partition on the next reboot.
293
After the procedure, the primary root partition will contain the same version of Junos
OS as the backup root partition.
NOTE: You can use the CLI command request system snapshot slice
alternate to back up the currently running root file system (primary or
secondary) to the other root partition on the system.
You can use this command to:
Save an image of the primary root partition in the backup root partition
when the system boots from the primary root partition.
Save an image of the backup root partition in the primary root partition
when the system boots from the backup root partition.
WARNING: The process of restoring the alternate root by using the CLI
command request system snapshot slice alternate takes several minutes
to complete. If you terminate the operation before completion, the alternate
root might not have all required contents to function properly.
Related
Documentation

Routers
NOTE: If you are upgrading to Junos OS Release 12.2 without transitioning

to dual-root partitioning, use the conventional CLI installation method.
To format the media with dual-root partitioning while upgrading to Junos OS Release
12.2 or later, use either of the following installation methods:
NOTE: All ACX Series routers run with dual-root partitioning.
294
Installation using a USB storage device. We recommend this method if console access
to the system is available and the system can be physically accessed to plug in a USB
storage device. See Installing Junos OS Using a USB Storage Device on ACX Series
Routers.
Related
Documentation
Installation from the CLI. We recommend this method only if console access is not
available. This installation can be performed remotely. See Installing Junos OS Upgrades
from a Remote Server on ACX Series Routers.

Installing Junos OS Using a USB Storage Device on ACX Series Routers

To install the Junos OS image on ACX Series routers using a USB storage device, you
must have access to the USB port physically and you must also have console access.
Perform the following steps to install the Junos OS image:
1.
Insert the USB storage device that has a valid installation image into the USB port.
2. Reboot the router by either pressing the power button on the chassis or switching off
and turning on the power button behind the Routing Engine, or by entering the request
system reboot command from the CLI. The system LED starts blinking in green.
On the console, a message is displayed stating that your flash memory device (NAND
Flash device) will be formatted and you will lose all the data. You are prompted to
confirm the formatting of the flash memory device.
3. Press y to confirm and proceed with the formatting process. The flash memory device
is formatted and the image is installed on both the partitions.

After the installation is completed, a message is displayed on the console prompting
you to eject the USB storage device and to press Enter to reboot the device.
4. After you remove the USB port and press Enter, the reboot begins. After the router is
rebooted, the new Junos OS version is loaded and functional. The LED glows steadily
in green.
NOTE: If an installation error occurs, the LEDs turn red. You must have console
access to the router to troubleshoot an installation error.
Related
Documentation
Routers on page 294
295

Installing Junos OS Upgrades from a Remote Server on ACX Series Routers

You can use the CLI to install Junos OS packages that are downloaded with FTP or HTTP
from the specified location on internal media, such as the NAND Flash device.
Before you begin:
Verify the available space on the NAND Flash device.
Download the Junos OS package.
To install Junos OS upgrades from a remote server, enter the following command from
operational mode:
user@host>request system software add junos-juniper-12.2R1.9-domestic.tgz no-copy
no-validate reboot
The new Junos OS image is installed on the router and the device is rebooted.
Related
Documentation
Routers on page 294


Routers Using the CLI
This example shows how to install Junos OS Release 12.2 or later and configure a dual-root
partition on ACX Series routers with the CLI.
Requirements
This example requires an ACX Series router. Before you begin, back up any important
data.
296
Overview
This example formats the NAND Flash device and installs the new Junos OS image on
the media with dual-root partitioning. Install the Junos OS Release 12.2 or later image
from the CLI by using the request system software add command. Partitions are
automatically created on ACX Series routers and no option needs to be manually entered
for creating partitions. This command copies the image to the device, and then reboots
the device for installation. The device boots with the Release 12.2 or later image installed
with the dual-root partitioning scheme. The formatting and installation process is
scheduled to run on the next reboot. Therefore, we recommend that this option be used
together with the reboot option.
NOTE: The process might take 15 to 20 minutes. The system is not accessible
over the network during this time.
WARNING: Using the request system software add command erases the
existing contents of the media. Only the current configuration is preserved.
You should back up any important data before starting the process.
NOTE: Dual, internal NAND Flash device (first daOs1, then daOs2) and USB
storage device are the storage media available on the ACX Series router. The
USB storage device is not dual-root partitioned.
In this example, add the software package junos-juniper-12.2R1.9-domestic.tgz with the

following options:
no-copy option to install the software package. However, do not save the copies of
the package files. You should include this option if you do not have enough space on
the internal media to perform an upgrade that keeps a copy of the package on the
device.
no-validate option to bypass the compatibility check with the current configuration
before installation starts.
reboot option to reboot the device after installation is completed.
Configuration
CLI Quick
Configuration
To install Junos OS Release 12.2 or later and configure dual-root partitioning on ACX
Series routers, copy the following command, paste it in a text file, remove any line break,
and then copy and paste the command into the CLI.
From operational mode, enter:
user@host>request system software add junos-juniper-12.2R1.9-domestic.tgz no-copy
no-validate reboot
297
Step-by-Step
Procedure
To install Junos OS Release 12.2 or later and configure a dual-root partition:

1.
Upgrade the ACX Series router to Junos OS Release 12.2 or later using the CLI. See
Upgrading Software Packages on page 305.
2.
Install Junos OS Release 12.2 or later and configure the dual-root partition.
user@host>request system software add junos-juniper-12.2R1.9-domestic.tgz
no-copy no-validate reboot
Copying package junos-juniper-12.2R1.9-domestic.tgz to var/tmp/install
Rebooting ...
Results
In operational mode, confirm your configuration by entering the show system storage
command. If the output does not display the intended configuration, repeat the
configuration instructions in this example to correct it.
Sample output on a system with dual-root partitioning that displays information about
the root partition that is mounted (only one root partition is mounted at a point in time):
user@host> show system storage
Filesystem
Size
Used
Avail Capacity
Mounted on
/dev/da0s1a
872M
150M
713M
17% /
devfs
1.0K
1.0K
0B
100% /dev
/dev/md0
41M
41M
0B
100% /packages/mnt/jbase
/dev/md1
183M
183M
0B
100%
/packages/mnt/jkernel-ppc-12.2I20121026_1217_sranjan
/dev/md2
30M
30M
0B
100%
/packages/mnt/jpfe-ACX-12.2I20121026_1217_sranjan
/dev/md3
9.1M
9.1M
0B
100%
/packages/mnt/jdocs-12.2I20121026_1217_sranjan
/dev/md4
55M
55M
0B
100%
/packages/mnt/jroute-ppc-12.2I20121026_1217_sranjan
/dev/md5
12M
12M
0B
100%
/packages/mnt/jcrypto-ppc-12.2I20121026_1217_sranjan
/dev/md6
1.0G
8.0K
951M
0% /tmp
/dev/md7
1.0G
448K
950M
0% /mfs
/dev/da0s1e
92M
18K
91M
0% /config
procfs
4.0K
4.0K
0B
100% /proc
/dev/da0s3f
3.9G
3.6G
30M
99% /var
/dev/da0s3d
447M
2.8M
409M
1% /var/log
If you are done configuring the device, enter commit in configuration mode.
You can issue the fdisk command from the Junos prompt to display information about
the entire partition format on the NAND Flash device. All ACX Series routers run with
dual-root partitioning. The following example displays the partition details on an ACX
Series router with dual-root partitions:
user@host% fdisk
******* Working on device /dev/da0 *******
parameters extracted from in-core disklabel are:
cylinders=487 heads=255 sectors/track=63 (16065 blks/cyl)
parameters to be used for BIOS calculations are:
cylinders=487 heads=255 sectors/track=63 (16065 blks/cyl)
Media sector size is 512
298
Warning: BIOS sector numbering starts with sector 1

Information from DOS bootblock is:
The data for partition 1 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 567, size 1011528 (493 Meg), flag 80 (active)
beg: cyl 0/ head 9/ sector 1;
end: cyl 62/ head 254/ sector 63
start 1012662, size 1011528 (493 Meg), flag 0
In the preceding example, partition 1 and 2 contain two partitions each internally, a root
partition and a configuration partition.
Verification
Confirm that the configuration is working properly.
Verifying the Partitioning Scheme Details on page 299
Verifying the Partitioning Scheme Details

Purpose
Verify that the partitioning scheme details on the ACX Series router were configured.
Action
In operational mode, enter the show system storage command. For details about the
output of this command and the descriptions of the output fields, see show system
storage.
Related
Documentation
Routers on page 294
Installation and Upgrade Guide
Hardware Architecture Overview

Juniper Network routing platforms are made up of two basic routing components:
Routing EngineThe Routing Engine controls the routing updates and system
management.
299
Packet Forwarding Engine (PFE)The Packet Forwarding Engine performs Layer 2

and Layer 3 packet switching, route lookups, and packet forwarding.
From a system administration perspective, you install the software onto the Routing
Engine and during the installation, the appropriate software is forwarded to other
components as necessary. Most Routing Engines include a CompactFlash card that
stores Junos OS. On M Series Multiservice Edge Routers, MX240, MX480, and MX960
3D Universal Edge Routers, T Series Core Routers, and TX Matrix routers, the system also
includes a hard disk or solid-state drive (SSD) that acts as a backup boot drive. PTX
Series Packet Transport Switches and the TX Matrix Plus router include a solid state
drive as a backup boot drive.
NOTE: The MX80 router is a single-board router with a built-in Routing Engine
and single Packet Forwarding Engine. On an MX80 router, Junos OS is stored
on dual, internal NAND flash devices. These devices provide the same
functionality as a CompactFlash card and hard disk or solid-state drive (SSD).
NOTE: The ACX Series router is a single board router with a built-in Routing
Engine and one Packet Forwarding Engine. The ACX router supports dual-root
partitioning, which means that the primary and backup Junos OS images are
kept in two independently bootable root partitions. If the primary partition
becomes corrupted, the system remains fully functional by booting from the
backup Junos OS image located in the other root partition.
On routing platforms with dual Routing Engines, each Routing Engine is independent
with regard to upgrading the software. To install new software on both Routing Engines,
you need to install the new software on each Routing Engine. On platforms with dual
Routing Engines configured for high availability, you can use the unified in-service software
upgrade procedure to upgrade the software. For more information about this procedure,
see the Junos OS High Availability Configuration Guide.
Related
Documentation
Hardware Overview (ACX Series, M Series, MX Series, T Series, and TX Matrix Routers)
Figure 19 on page 301 shows examples of Routing Engines.
300
Figure 19: Routing Engines
The ACX Series, M Series, MX Series, PTX Series, T Series, TX Matrix, and TX Matrix Plus
routers include the following:
System Memory on page 301
Storage Media on page 302
System Memory
Starting with Junos OS Release 9.0, all routing platforms require a minimum of 512 MB
of system memory on each Routing Engine. All M7i and M10i routers delivered before
December 7, 2007, had 256 MB of memory. These routers require a system memory
upgrade before you install Junos OS Release 9.0 or a later release. To determine the
amount of memory currently installed on your system, use the show chassis routing-engine
command in the command-line interface (CLI).
301
For more information about upgrading your M7i or M10i router, see the Customer Support
Center JTAC Technical Bulletin PSN-2007-10-001:
https://www.juniper.net/alerts/viewalert.jsp?txtAlertNumber=PSN-2007-10-001&actionBtn=Search.
ACX2000 routers are shipped with 2 GB of memory and ACX1000 routers with 1 GB of
memory.
Storage Media
Except for the ACX Series and MX80 routers, the M Series, MX Series, PTX Series, T Series,
TX Matrix, and TX Matrix Plus routers use the following media storage devices:
CompactFlash cardThe CompactFlash card is typically the primary storage device

for most routers.
NOTE: M7i and M10i routers using RE-400 are not delivered from the factory
with the CompactFlash card installed. In this case, the hard disk is the
primary and only boot device. The M7i and M10i routers with RE-400 can
be upgraded to include the CompactFlash card.
Hard disk or solid -state driveFor most routers,, a hard disk or solid-state drive is the
secondary boot device. When the CompactFlash card is not installed on the router,
the hard disk or the solid-state drive becomes the primary boot device. The hard disk
or solid-state drive is also used to store system log files and diagnostic dump files.
Emergency boot deviceDepending on the router, the emergency boot device can be
a PC card, a USB storage device, or an LS-120 floppy disk.
On MX80 routers, the internal NAND flash devices (first da0, then da1) act as the primary
and secondary boot devices.
On ACX Series routers, the internal NAND flash devices (first da0s1, then da0s2) act as
the primary and secondary boot devices.
Emergency boot devices can be used to revive a routing platform that has a damaged
Junos OS. When an emergency boot device is attached to the router, the router attempts
to boot from that device before it boots from the CompactFlash card, solid-state drive
(SSD), or hard disk.
On an ACX Series router, the emergency boot device is a USB storage device.
When booting from an emergency boot device, the router requests a boot
acknowledgment on the console interface. If you enter yes, the emergency boot device
repartitions the primary boot device and reloads Junos OS onto the primary boot device.
After the loading is complete, the routing platform requests that you remove the
emergency boot device and reboot the system. After the reboot is complete, you must
perform an initial configuration of the router before it can be used on your network.
Boot Sequence (ACX Series Routers)

The router attempts to boot from the storage media in the following order:
302
1.
USB storage media device.
2. Dual, internal NAND flash device (first da0s1, then da0s2).
Related
Documentation
Routing Engines and Storage Media Names (ACX Series, M Series, MX Series, PTX
Series, T Series, TX Matrix, TX Matrix Plus, and JCS 1200 Routers)
Table 27 on page 303 specifies the storage media names by Routing Engine. The storage
media device names are displayed when the router boots.
Table 27: Routing Engines and Storage Media Names (ACX Series, M
Series, MX Series, T Series, TX Matrix, TX Matrix Plus, and JCS 1200
Routers)
Routing Engine
CompactFlash
Card
Hard Disk
Solid State
Drive
Removable
Media
Emergency
Boot Device
RE-400-768 (RE5)
ad0
ad1
No
ad3
RE-600-2048 (RE3)
ad0
ad1
No
ad3
RE-850-1536
(RE-850)
ad0
ad1
No
ad3
RE-A-1000-2048
(RE-A-1000)
ad0
ad2
No
da0
RE-A-1800x2
(RE-A-1800)
ad0
No
Yes
da0
SSD1: ad1
SSD2: ad2
RE-S-1300-2048
(RE-S-1300)
ad0
ad2
No
da0
RE-S-1800x2
RE-S-1800x4
(RE-S-1800)
ad0
No
Yes
da0
SSD1: ad1
SSD2: ad2
RE-B-1800X1-4G-S
ad0
No
Yes
da0
SSD1: ad1
RE-1600-2048 (RE4)
ad0
ad1
No
ad3 and ad4
303
Table 27: Routing Engines and Storage Media Names (ACX Series, M
Series, MX Series, T Series, TX Matrix, TX Matrix Plus, and JCS 1200
Routers) (continued)
CompactFlash
Card
Hard Disk
Solid State
Drive
Removable
Media
Emergency
Boot Device
RE-A-2000-4096
(RE-A-2000)
ad0
ad2
No
da0
RE-S-2000-4096
(RE-S-2000)
ad0
ad2
No
da0
RE-DUO-C2600-16G
(RE-DUO-2600)
ad0
No
ad1
da0
RE-DUO-C1800-8G(RE-DUO-1800)
ad0
No
ad1
da0
RE-DUO-C1800-16G
ad0
No
ad1
da0
RE-JCS1200-1x2330
da0
da1
No
da2
Routing Engine
NOTE: On MX80 routers, the Routing Engine is a built-in device and has no
model number. The dual internal NAND flash devices are da0 and da1. The
USB storage device is da2.
NOTE: On ACX Series routers, the Routing Engine is a built-in device, which
does not have a model number. The dual internal NAND flash devices are
da0s1 and da0s2. The USB storage device is da0s2a. Use the show chassis
hardware models command to obtain the field-replaceable unit (FRU) model
numberfor example, ACX2000BASE-DC for the ACX2000 router.
To view the storage media currently available on your system, use the CLI show system
storage command. For more information about this command, see the CLI User Guide.
Related
Documentation
304
Supported Routing Engines by Chassis
Routing Engine Specifications
RE-S-1300 Routing Engine Description
RE-S-2000 Routing Engine Description
RE-S-1800 Routing Engine Description for MX Series
JCS1200 Routing Engine Description
Upgrading Software Packages
NOTE: When you install individual software packages, the following notes
apply:
When upgrading from Junos OS Release 8.2 or earlier to Junos OS Release

8.5, use the system software add <image> no-validate command option.
Only use the jinstall Junos OS image when upgrading or downgrading to or

from Junos OS Release 8.5. Do not use the jbundle image.
Before upgrading to Junos OS Release 8.5, ensure that the routing

platforms CompactFlash card is 256 MB or larger to avoid disk size
restrictions. (M7i routers without a CompactFlash card are excluded.)
To upgrade an individual Junos OS package, follow these steps:

1.
Download the software packages you need from the Juniper Networks Support Web
site at http://www.juniper.net/support/. For information about downloading software
packages, see Downloading Software.
NOTE: We recommend that you upgrade all individual software packages

using an out-of-band connection from the console or management
Ethernet interface, because in-band connections can be lost during the
upgrade process.
2. Back up the currently running and active file system so that you can recover to a known,
stable environment in case something goes wrong with the upgrade:

user@host> request system snapshot
The root file system is backed up to /altroot, and /config is backed up to /altconfig.
The root and /config file systems are on the routers CompactFlash card, and the
/altroot and /altconfig file systems are on the routers hard disk or solid-state drive
(SSD).
NOTE: After you issue the request system snapshot command, you cannot
return to the previous version of the software, because the running copy
and the backup copy of the software are identical.
3. If you are copying multiple software packages to the router, copy them to the /var/tmp
directory on the hard disk or solid-state drive (SSD):

user@host> file copy ftp://username :prompt@ftp.hostname
.net/filename/var/tmp/filename
4. Add the new software package:
To add an individual software package:
305
user@host> request system software add/var/tmp/ installation-package validate

installation-package is the full URL to the file.
If you are upgrading more than one package at the same time, add jbase first. If you
are using this procedure to upgrade all packages at once, add them in the following
order:
user@host> request system software add /var/tmp/jbase-release-signed.tgz
user@host> request system software add /var/tmp/jkernel-release-signed.tgz
user@host> request system software add /var/tmp/jpfe-release-signed.tgz
user@host> request system software add /var/tmp/jdocs-release- signed.tgz
user@host> request system software add /var/tmp/jweb-release- signed.tgz
user@host> request system software add /var/tmp/jroute-release-signed.tgz
user@host> request system software add /var/tmp/jcrypto-release-signed.tgz
For M Series, MX Series, and T Series routers and Branch SRX Series firewall filters
running Junos OS Release 12.2 and above, you can add more than one software
package at the same time. To add multiple software packages:
user@host> request system software add set /var/tmp/
installation-package/var/tmp/ installation-package validate
installation-package can be any of the following:
A list of installation packages, each separated by a blank space. For example,

user@host> request system software add set /var/tmp/
jinstall-10.2R1.8domestic-signed.tgz /var/tmp/ jtools*.tgz validate
The full URL to the directory or tar file containing the list of installation packages.
Use the request system software add set command to retain any SDK configuration
by installing the SDK add-on packages along with the core Junos OS installation
package.
WARNING: Do not include the re0 | re1 option when you install a package
using the request system software add command, if the Routing Engine on
which the package is located and the Routing Engine on which you want
to install the package are the same. In such cases, the package gets
deleted after a successful upgrade.
The system might display the following message:

pkg_delete: couldnt entirely delete package
This message indicates that someone manually deleted or changed an item that was
in a package. You do not need to take any action; the package is still properly deleted.
For more information about the request system software add command, see the Junos
OS System Basics and Services Command Reference.
5. Reboot the router to start the new software:
306
user@host> request system reboot

6. After you have upgraded or downgraded the software and are satisfied that the new
software is successfully running, issue the request system snapshot command to back
up the new software:
NOTE: On an ACX router, you must issue the request system snapshot slice
alternate command.
The root file system is backed up to /altroot, and /config is backed up to /altconfig.
The root and /config file systems are on the routers CompactFlash card, and the
/altroot and /altconfig file systems are on the routers hard disk or solid-state drive
(SSD).
NOTE: After you issue the request system snapshot command, you cannot
return to the previous version of the software, because the running copy
and backup copy of the software are identical.
Load and Commit the Configuration File

Once the saved configuration file is copied to the router, you load and commit the file:
1.
Start the CLI configuration mode.

user@routername> configure
Entering configuration mode
[edit]
user@host#
2. Load the file into the current configuration. You should override the existing file.
user@host#
load override /var/tmp/filename
load complete
3. Commit the file.
user@host# commit
commit complete
4. Exit the CLI configuration mode.
user@host# exit
user@host>
5. Back up Junos OS.
After you have installed the software on the router, committed the configuration, and
are satisfied that the new configuration is successfully running, issue the request
system snapshot command to back up the new software to the /altconfig file system.
307
If you do not issue the request system snapshot command, the configuration on the
alternate boot drive will be out of sync with the configuration on the primary boot
drive.
The request system snapshot command causes the root file system to be backed up
to /altroot, and /config to be backed up to /altconfig. The root and /config file systems
are on the routers CompactFlash card, and the /altroot and /altconfig file systems
are on the routers hard disk or solid-state drive (SSD).
Checking the Current Configuration and Candidate Software Compatibility

When you upgrade or downgrade Junos OS, we recommend that you include the validate
option with the request system software add command to check that the candidate
software is compatible with the current configuration. By default, when you add a package
with a different release number, the validation check is done automatically. For more
information about the request system software add command, see the Junos OS System
Basics and Services Command Reference.
NOTE: On an ACX Series router, you must ensure that the primary and backup
partitions are synchronized after an upgrade by issuing the request system
snapshot command.
Related
Documentation
request system software add
request system snapshot
Understanding System Snapshot on an ACX Series Router

The system snapshot feature enables you to create copies of the software running on
an ACX Series router. You can use the system snapshot feature to take a snapshot of
the files currently used to run the routerthe complete contents of the root (/) and
/config directories, which include the running Juniper Networks Juniper operating system
(Junos OS) and the active configurationand copy all of these files to another media,
such as a universal serial bus (USB) storage device, the active slice of a dual-root
partitioned router, or the alternate slice of a dual-root partitioned router.
NOTE: Junos OS automatically uses the backup software if the currently

running software goes bad. For example, if the da0s1 slice goes bad, Junos
OS automatically comes up using the da0s2 slice, and takes a snapshot of
the da0s2 slice and copies it to the da0s1 slice if the auto snapshot
functionality is configured, which is disabled by default. However, you can
also do this manually using the system snapshot feature.
308
Typically, you can take a snapshot prior to the upgrade of an image on the dual internal
NAND flash device (da0s1 or da0s2), or to remedy a bad image, thereby preventing the
bad image from rendering the system useless. A snapshot to another media ensures that
the device can boot from the other media in case the system does not boot up from the
current image.
You can take a snapshot of the currently running software and configuration on a router
in the following situations:
The router's active slice (for example, da0s1) is updated with a new Junos OS image
(using the jinstall package). In such a case, you must update the other slice (da0s2)
with the new image.
NOTE: The active slice can be da0s1 or da0s2.
The router's active slice (for example, da0s1) is corrupted and the router is rebooted
from the backup slice (that is, from da0s2). Therefore, you must restore a new image
on the active slicethat is, on da0s1.
Both slices of the router's dual internal NAND flash device are corrupted and the router
continues trying to reboot. In this situation, you can insert a USB storage device, boot
the router from that device, and restore the NAND flash device slicesda0s1 and da0s2.
NOTE: Before you attempt to take a snapshot from the USB storage device,
ensure that the USB storage device contains an image of Junos OS from
which the router can boot up.
Related
Documentation
request system snapshot (ACX Series) on page 341
Example: Taking a Snapshot of the Software and Configuration

This example includes six scenarios in which you can take a snapshot of the currently
running software and configuration on an ACX Series router, prior to the upgrade of an
image or to remedy a bad image, thereby preventing the bad image from rendering the
system useless.
Taking a Snapshot on page 310
Requirements
309
Overview
In this example, the request system snapshot command is used to take a copy of the
currently running software and configuration on another mediafor example, a universal
serial bus (USB) storage device, the active slice (da0s1 or da0s2) of a dual-root partitioned
router, or the alternate slice (da0s1 or da0s2) of a dual-root partitioned router. A snapshot
to another media ensures that the device can boot from the other media in case the
system does not boot up from the current image.
CAUTION: After you run the request system snapshot command, you cannot
return to the previous version of the software, because the running and backup
copies of the software are identical.
Taking a Snapshot
Scenario: To take a snapshot from a NAND flash device slice to a USB storage device:
1.
Boot up the router from the NAND flash device and make sure that a formatted USB
storage device is plugged in to the routers USB port. The USB storage device must
be formatted for the root (/) and /config directories.
2. Issue the request system snapshot command.

Verifying compatibility of destination media partitions...
Running newfs (254MB) on usb media / partition (da1s1a)...
Running newfs (47MB) on usb media /config partition (da1s1e)...
Copying '/dev/da0s2a' to '/dev/da1s1a' .. (this may take a few minutes)
Copying '/dev/da0s2e' to '/dev/da1s1e' .. (this may take a few minutes)
The following filesystems were archived: / /config
The root (/) and /config directories from the currently mounted NAND flash slice are
copied to the USB storage device.
Scenario: To take a snapshot from a NAND flash device slice to a USB storage device
with formatting:
1.
Boot up the router from the NAND flash device and make sure that a USB storage
device is plugged in to the routers USB port.
NOTE: Formatting a USB storage device deletes all the data on the USB
storage device.
2. Issue the request system snapshot partition command.

user@host> request system snapshot partition
clearing current label...
Partitioning usb media (da1) ...
Partitions on snapshot:
310
Partition Mountpoint Size

Snapshot argument
a
/
312MB
root-size
e
/config
47MB
config-size
f
/var
620MB
var-size
Running newfs (620MB) on usb media /var partition (da1s1f)...
After the USB storage device is formatted, the root (/) and /config directories from
the currently mounted NAND flash slice are copied to the USB storage device.
Scenario: To take a snapshot from the active slice of the NAND flash device to the
alternate slice:
1.
Boot up the router from the NAND flash device.
2. Issue the request system snapshot slice alternate command.

user@host> request system snapshot slice alternate
Running newfs (439MB) on internal media / partition (da0s1a)...
Running newfs (46MB) on internal media /config partition (da0s1e)...
The root (/) and /config directories from the currently mounted NAND flash slice are
copied to the other slice.
Scenario: To take a snapshot from an active slice of the NAND flash device to the alternate
slice after partitioning:
1.
Boot up the router from the NAND flash device.
2. Issue the request system snapshot partition slice alternate command.

user@host> request system snapshot partition slice alternate
The BSD label (disk partitioning information) for the active flash slice is installed and
then the root (/) and /config directories from the currently mounted NAND flash slice
are copied to the other slice.
Scenario: To take a snapshot from a USB storage device to the active slice of the NAND
flash device:
1.
Boot up the router from a USB storage device containing the required Junos OS image.
2. Issue the request system snapshot command.

311

The root (/) and /config directories from the USB storage device are copied to the
active NAND flash slice.
Scenario: To take a snapshot from a USB storage device to the active slice of the NAND
flash device after partitioning:
1.
Boot up the router from a USB storage device containing the required Junos OS image.
2. Issue the request system snapshot partition command.

The BSD label (disk partitioning information) for the active flash slice is installed and
then the root (/) and /config directories from the USB storage device are copied to
the active NAND flash slice.
Related
Documentation
312
request system snapshot (ACX Series) on page 341
CHAPTER 15
Junos Configuration Statements
Key Configuration Statements Supported on ACX Series Routers on page 313
Key Configuration Statements Supported on ACX Series Routers

This topic includes key statements supported on ACX Series routers. The list does not
include every statement supported on the ACX Series routers. If a statement does not
appear in this list, you can take the following actions:
Find the statements using the Search Engine.
See Protocols and Applications Supported by the ACX Routers on page 5 for a
complete list of features and release dates.
The following list includes key statements supported on ACX Series routers:
access-profile
active
aggregate
aggregated-devices
alarm
alarm (chassis)
allow-any-vci
announce-interval (Slave Clock)
announce-interval (Master Clock)
as-path
asymmetry
atm-options
atm-policer (Firewall)
atm-service
auto-export
autoinstallation
313
314
autonomous-system
backup-neighbor
bits
brief
cdvt
cell-bundle-size
cell-bundle-size
cesopsn-options
chained-composite-next-hop
classifiers
classifiers (Physical Interface)
clock-class-to-quality-level-mapping
clocking
clock-client
clock-mode
clock-mode (Chassis Synchronization)
clock-source
color
community
confederation
convert-clock-class-to-quality-level
delay-buffer-rate
destination-networks
disable (Interface)
disable (Routing Options)
discard
dhcp-relay
dscp (Class of Service Classifier)
dscp (Classifier on Physical Interface)
dscp (Rewrite Rules on Physical Interface)
dynamic-tunnels
e1-options
e1-options (BITS Interfaces Signal Type)
Chapter 15: Junos Configuration Statements
ethernet-switch-profile
encapsulation (Logical Interface)
encapsulation (Physical Interface)
esmc-transmit
export
flow
flow-map
forwarding-cache
forwarding-class
forwarding-table
framing
framing (E1 Options for BITS Interfaces)
framing (T1 Options for BITS Interfaces)
full
generate
gigether-options
global-arp-prefix-limit
global-supplementary-blackout-timer
gps
graceful-restart
grant-duration
gre
group
hold-interval
host-fast-reroute
ieee-802.1 (Classifier on Physical Interface)
ieee-802.1 (Rewrite Rules on Physical Interface)
ima-group-options
ima-link-options
inet-precedence
inet-precedence (Classifier on Physical Interface)
inet-precedence (Rewrite Rules on Physical Interface)
ingress
315
316
input
input-relay (Alarm Relay Output Port)
interface
interface (Master Clock)
interface (PTP Slave)
interface-routes
interface-type
interfaces
interfaces bits
interfaces (Chassis Synchronization Source)
ipv4-dscp
l3vpn
label-switched-path-template
link-protection
local-ip-address
logical-interface-policer
management
manual
martians
master
max-announce-interval
max-burst-size
max-delay-response-interval
max-sync-interval
maximum-paths
maximum-prefixes
med-igp-update-interval
media-type
metric
min-announce-interval
min-delay-response-interval
min-sync-interval
mode
mtu
multicast
multicast-mode
native-vlan-id
network-option
no-bfd-triggered-local-repair
no-partition
oam-liveness
oam-period
options (Routing Options)
output
overrides
partition
passive
peak-rate
policing-action
policy
port (Alarm Relay Input)
port (Alarm Relay Output)
ppm
preference
primary
promiscuous-mode
priority
psn-vci
psn-vpi
quality-level (Chassis Synchronization Source Interface)
quality-level (Clock Class Mapping PTP Slave)
quality-mode-enable
relay
request
rewrite-rules (Physical Interfaces)
rib
317
318
rib-group (Routing Options)
route-distinguisher-id
route-record
router-id
routing-options
selection-mode
satop-options
signal-type
slave
source
source-address (Routing Options)
source-routing
standby
stateful
static (Protocols Layer 2 Circuit)
static (Origin Validation for BGP)
sustained-rate
switchover-mode
sync-interval (Slave)
sync-interval (Master)
synchronization
system-defaults
tag
t1-options
t1-options (BITS Interfaces Signal Type)
temperature (Alarm Relay Output)
timeslots
traceoptions (Routing Options)
traffic-control-profiles
transport
transport 802.3
trigger
unicast
Related
Documentation
unicast-mode (Master Clock)
unicast-mode (PTP Slave Interface)
validation
vci
vpi (Logical Interface and Interworking)
vpi (ATM CCC Cell-Relay Promiscuous Mode)
vpi (Define Virtual Path)
vrf-propagate-ttl
wait-to-restore
Key Configuration Statement Hierarchies Supported on ACX Series Routers on page 321
319
320
CHAPTER 16
Configuration Statement Hierarchies
Key Configuration Statement Hierarchies Supported on ACX Series Routers on page 321
Key Configuration Statement Hierarchies Supported on ACX Series Routers

This topic includes key statement hierarchies supported on ACX Series routers. The list
does not include every statement hierarchy supported on the ACX Series routers. If a
statement hierarchy does not appear in this list, you can take the following actions:
Find the statement hierarchy using the Search Engine.
See Protocols and Applications Supported by the ACX Routers on page 5 for a
complete list of features and release dates.
The following list includes key statement hierarchies supported on ACX Series routers:
[edit protocols bfd] Hierarchy Level
[edit protocols bgp] Hierarchy Level
[edit protocols esis] Hierarchy Level
[edit forwarding-options family] Hierarchy Level
[edit forwarding-options dhcp-relay] Hierarchy Level for ACX Series Routers
[edit protocols isis] Hierarchy Level
[edit protocols l2circuit] Hierarchy Level
[edit protocols ldp] Hierarchy Level
[edit protocols mpls] Hierarchy Level
[edit protocols msdp] Hierarchy Level
[edit protocols oam] Hierarchy Level
[edit protocols ospf] Hierarchy Level
[edit protocols ospf3] Hierarchy Level
[edit poe]
[edit protocols ppp] Hierarchy Level
[edit protocols ppp-service] Hierarchy Level
321
Related
Documentation
322
[edit protocols rip] Hierarchy Level
[edit protocols ripng] Hierarchy Level
[edit protocols rsvp] Hierarchy Level
[edit routing-instances] Hierarchy Level
[edit routing-options] Hierarchy Level
[edit switch-options] Hierarchy Level
[edit system] Hierarchy Level
Statement Hierarchy for Configuring FBF for IPv4 Traffic on ACX Series Routers
Key Configuration Statements Supported on ACX Series Routers on page 313
PART 3
Administration
Monitoring Commands for the ACX Universal Access Router on page 325
323
324
CHAPTER 17
Monitoring Commands for the ACX

325
clear oam ethernet connectivity-fault-management sla-iterator-statistics

Syntax
Release Information
Description
Options
clear oam ethernet connectivity-fault-management sla-iterator-statistics

maintenance-association maintenance-association-name
maintenance-domain maintenance-domain-name
<local-mep local-mep-id>
<remote-mep remote-mep-id>
sla-iterator sla-iterator
Command introduced in Junos OS Release 11.4 for EX Series switches.

Command introduced in Junos OS Release 12.2 for ACX Series routers.
Clear Ethernet Operation, Administration, and Maintenance (OAM) service-level
agreement (SLA) iterator statistics. For ACX Series routers, clear the SLA iterator statistics
and proactive Ethernet synthetic loss measurement (ETH-SLM) statistics
maintenance-association maintenance-association-nameName of the maintenance
association.
maintenance-domain maintenance-domain-nameName of the maintenance domain.
local-mep local-mep-id(Optional) Identifier of the local MEP.
remote-mep remote-mep-id(Optional) Identifier of the remote MEP.
sla-iterator sla-iterator Name of the SLA iterator profile.
Required Privilege
Level
Related
Documentation
view
Configuring an Iterator Profile on a Switch (CLI Procedure)
show oam ethernet connectivity-fault-management sla-iterator-statistics on page 802
List of Sample Output
clear oam ethernet connectivity-fault-management sla-iterator- statistics on page 326
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
clear oam ethernet
connectivity-fault
-management
sla-iterator- statistics
326
user@switch> clear oam ethernet connectivity-fault-management sla-iterator-statistics

maintenance-domain md1 maintenance-association ma1 local-mep 1 remote-mep 2 sla-iterator
i1
Iterator statistics entries cleared
Chapter 17: Monitoring Commands for the ACX Universal Access Router
clear oam ethernet connectivity-fault-management synthetic-loss-measurement

Syntax
Release Information
Description
Options

maintenance-domain md-name
maintenance-association ma-name
Command introduced in Junos OS Release 12.3X51 for ACX Series routers.

(ACX Series routers)For all routers that support IEEE 802.1ag OAM connectivity fault
management (CFM), clear the existing on-demand Ethernet synthetic loss measurement
(ETH-SLM) statistics and restart counting the ETH-SLM frame counts and statistics.
maintenance-domain md-nameName of an existing CFM maintenance domain.
maintenance-association ma-nameName of an existing CFM maintenance association.
local-mep local-mep-id(Optional) Clear connectivity fault management information
for the specified local MEP only.

remote-mep remote-mep-id(Optional) Clear connectivity fault management information
for the specified remote MEP only.

Required Privilege
Level
Related
Documentation
Output Fields
view
monitor ethernet synthetic-loss-measurement on page 333
show oam ethernet connectivity-fault-management synthetic-loss-statistics on

page 807

synthetic-loss-measurement on page 327
Sample Output
clear oam ethernet
connectivity-faultmanagement
synthetic-lossmeasurement

maintenance-domain md5 maintenance-association ma5 local-mep 100 remote-mep 102
Synthetic loss measurement restarted.
327
clear dhcp relay statistics

Syntax
clear dhcp relay statistics

<logical-system logical-system-name>
<routing-instance routing-instance-name>
Syntax
Syntax for EX Series switches:

show dhcp relay statistics
Release Information
Description
Options
Command introduced in Junos OS Release 8.3.

Statement introduced in Junos OS Release 12.1 for EX Series switches.
Command introduced in Junos OS Release 12.1X48R3 for PTX Series Packet Transport
Switches.
Clear all Dynamic Host Configuration Protocol (DHCP) relay statistics.
logical-system logical-system-name(On routers only) (Optional) Perform this operation
on the specified logical system. If you do not specify a logical system name, statistics
are cleared for the default logical system.
routing-instance routing-instance-name(Optional) Perform this operation on the specified
routing instance. If you do not specify a routing instance name, statistics are cleared
for the default routing instance.
Required Privilege
Level
Related
Documentation
Output Fields
328
view
show dhcp relay statistics on page 658
clear dhcp relay statistics on page 330

Table 28 on page 329 lists the output fields for the clear dhcp relay statistics command.
Table 28: clear dhcp relay statistics Output Fields

Field Name
Field Description
Packets dropped
Number of packets discarded by the extended DHCP relay agent application due to errors. Only
nonzero statistics appear in the Packets dropped output. When all of the Packets dropped statistics
are 0 (zero), only the Total field appears.
TotalTotal number of packets discarded by the extended DHCP relay agent application.
Bad hardware addressNumber of packets discarded because an invalid hardware address was
specified.
Bad opcodeNumber of packets discarded because an invalid operation code was specified.
Bad optionsNumber of packets discarded because invalid options were specified.
Invalid server addressNumber of packets discarded because an invalid server address was specified.
No available addressesNumber of packets discarded because there were no addresses available
for assignment.
No interface matchNumber of packets discarded because they did not belong to a configured
interface.
No routing instance matchNumber of packets discarded because they did not belong to a configured
routing instance.
Messages received
Messages sent
No valid local addressNumber of packets discarded because there was no valid local address.
Packet too shortNumber of packets discarded because they were too short.
Read errorNumber of packets discarded because of a system read error.
Send errorNumber of packets that the extended DHCP relay application could not send.
Option 60Number of packets discarded containing DHCP option 60 vendor-specific information.
Option 82Number of packets discarded because DHCP option 82 information could not be added.
Number of DHCP messages received.
BOOTREQUESTNumber of BOOTP protocol data units (PDUs) received
DHCPDECLINENumber of DHCP PDUs of type DECLINE received
DHCPDISCOVERNumber of DHCP PDUs of type DISCOVER received
DHCPINFORMNumber of DHCP PDUs of type INFORM received
DHCPRELEASENumber of DHCP PDUs of type RELEASE received
DHCPREQUESTNumber of DHCP PDUs of type REQUEST received
Number of DHCP messages sent.
BOOTREPLYNumber of BOOTP PDUs transmitted
DHCPOFFERNumber of DHCP OFFER PDUs transmitted
DHCPACKNumber of DHCP ACK PDUs transmitted
DHCPNACKNumber of DHCP NACK PDUs transmitted
329
Sample Output
clear dhcp relay
statistics
The following sample output displays the DHCP relay statistics before and after the clear
dhcp relay statistics command is issued.
user@host> show dhcp relay statistics
Packets dropped:
Total
0
Messages received:
BOOTREQUEST
DHCPDECLINE
DHCPDISCOVER
DHCPINFORM
DHCPRELEASE
DHCPREQUEST
116
0
11
0
0
105
Messages sent:
BOOTREPLY
DHCPOFFER
DHCPACK
DHCPNAK
44
11
11
11
user@host> clear dhcp relay statistics

Packets dropped:
Total
0
330
Messages received:
BOOTREQUEST
DHCPDECLINE
DHCPDISCOVER
DHCPINFORM
DHCPRELEASE
DHCPREQUEST
0
0
0
0
0
0
Messages sent:
BOOTREPLY
DHCPOFFER
DHCPACK
DHCPNAK
0
0
0
0
clear dhcp relay binding

Syntax
Release Information
Description
Options
clear dhcp relay binding

<address>
<all>
<interface interface-name>
<interfaces-vlan>
<interfaces-wildcard>

Options all and interface added in Junos OS Release 8.4.
Options interfaces-vlan and interfaces-wildcard added in Junos OS Release 12.1.
Switches.
Clear the binding state of a Dynamic Host Configuration Protocol (DHCP) client from
the client table.
address(Optional) Clear the binding state for the DHCP client, using one of the following
entries:
ip-addressThe specified IP address.
mac-addressThe specified MAC address.
session-idThe specified session ID.
all(Optional) Clear the binding state for all DHCP clients.

interface interface-name(Optional) Clear the binding state for DHCP clients on the
specified interface.
interfaces-vlan(Optional) Clear the binding state on the interface VLAN ID and S-VLAN
ID.
interfaces-wildcard(Optional) The set of interfaces on which to clear bindings. This
option supports the use of the wildcard character (*).

logical-system logical-system-name(Optional) Clear the binding state for DHCP clients
on the specified logical system.

routing-instance routing-instance-name(Optional) Clear the binding state for DHCP
clients on the specified routing instance.

Required Privilege
Level
Related
Documentation
view
Clearing DHCP Bindings for Subscriber Access
show dhcp relay binding on page 661
331
Output Fields
clear dhcp relay binding on page 332

clear dhcp relay binding all on page 332
clear dhcp relay binding interface on page 332
clear dhcp relay binding <interfaces-vlan> on page 332
clear dhcp relay binding <interfaces-wildcard> on page 332
See show dhcp relay binding for an explanation of output fields.
Sample Output
clear dhcp relay
binding
The following sample output displays the address bindings in the DHCP client table
before and after the clear dhcp relay binding command is issued.
user@host> show dhcp relay binding
IP address
Hardware address
Type
100.20.32.1
90:00:00:01:00:01 active
192.168.14.8
90:00:01:01:02:01 active
Lease expires at
2007-02-08 16:41:17 EST
2007-02-10 10:01:06 EST
user@host> clear dhcp relay binding 100.20.32.1

IP address
Hardware address
Type
192.168.14.8
90:00:01:01:02:01 active
clear dhcp relay

binding all
Lease expires at
2007-02-10 10:01:06 EST
The following command clears all DHCP relay agent bindings:

user@host> clear dhcp relay binding all
clear dhcp relay

binding interface
The following command clears DHCP relay agent bindings on a specific interface:
user@host> clear dhcp relay binding interface fe-0/0/3
clear dhcp relay

binding
<interfaces-vlan>
The following command uses the interfaces-vlan option to clear all DHCP relay agent
bindings on top of the underlying interface ae0, which clears DHCP bindings on all demux
VLANs on top of ae0:
user@host> clear dhcp relay binding interface ae0
clear dhcp relay

binding
The following command uses the interfaces-wildcard option to clear all DHCP relay agent
bindings over a specific interface:
user@host> clear dhcp relay binding ge-1/0/0.*
332
monitor ethernet synthetic-loss-measurement

Syntax
Release Information
Description

(remote-mac-address | mep remote-mep-id)
<count frame-count>
<wait interval-milliseconds>
<priority 802.1p value>
<size>
<xml>

(ACX Series routers) Start an ITU-T Y.1731 Ethernet synthetic loss measurement
(ETH-SLM) session between the specified local connectivity fault management (CFM)
maintenance association end point (MEP) and the specified remote MEP, and display a
summary of the frames exchanged in the measurement session. ETH-SLM (also called
synthetic frame loss measurement) statistics are stored at one of the MEPs for later
retrieval.
NOTE: If you attempt to monitor delays to a nonexistent MAC address, you

must press Ctrl +c to explicitly quit the monitor ethernet
synthetic-loss-measurement command and return to the CLI command
prompt.
To start an Ethernet synthetic frame loss measurement session, the router initiates an
exchange of frames carrying synthetic frame loss measurement protocol data units
(PDUs) between the local and remote MEPs. The frame countsthe types of and number
of Ethernet synthetic frame loss measurement PDU frames exchanged to measure frame
delay timesare displayed as the run-time output of the monitor ethernet
synthetic-loss-measurement command and are also stored at both the initiator and
receiver MEPs for later retrieval. Ethernet synthetic frame loss measurement statistics,
described below, are measured and stored at only one of the MEPs:
Frame delayThe difference, in microseconds, between the time a frame is sent and
when it is received.
Frame delay variationThe difference, in microseconds, between consecutive frame
delay values. Frame delay variation is sometimes called frame jitter.
Options

mep remote-mep-idNumeric identifier of the peer MEP with which to perform Ethernet
synthetic frame loss measurement. The discovered MAC address of the peer MEP
is used. The range of values is from 1 through 8191.
333
remote-mac-addressUnicast MAC address of the peer MEP with which to perform
Ethernet synthetic frame loss measurement. Specify the MAC address as six
hexadecimal bytes in one of the following formats: nnnn.nnnn.nnnn or
nn:nn:nn:nn:nn:nn. For example, 0011.2233.4455 or 00:11:22:33:44:55. Multicast MAC
addresses are not supported.
count frame-count(Optional) Number of frames to send to the specified peer MEP. The
range of values is from 1 through 65,535 frames. The default value is 10 frames.
wait interval-milliseconds(Optional) Number of milliseconds to wait between sending
frames. You must specify this value in multiples of 100 milliseconds. The range of
values is from 100 through 50000 milliseconds. The default value is 100 milliseconds.
priority 802.1p value(Optional) Priority of the ETH-SLM request frame supported. The
range of values is from 0 through 7. The default value is zero.

size(Optional) Size of the data TLV to be included in the request frame. The range of
values is from 1 through 1400 bytes.

xml(Optional) Allow the output of the command to be displayed in XML format for
ETH-SLM. Note that the only way to get output in XML format is to use the xml
argument. The display xml command does not work.
To display the frame counts collected at a MEP as the result of this command, use the
following commands as described in the Junos OS Operational Mode Commands:
show oam ethernet connectivity-fault-management interfaces detail
show oam ethernet connectivity-fault-management mep-database
show oam ethernet connectivity-fault-management mep-statistics
To display the statistics collected at a MEP as the result of this command, use the
following commands as described in the Junos OS Operational Mode Commands.
show oam ethernet connectivity-fault-management synthetic-loss-measurement
To clear both the frame counts and the statistics collected for MEPs, use the clear oam
ethernet connectivity-fault-management statistics command, described in the Junos OS
Operational Mode Commands.
For a complete description of Ethernet synthetic frame loss measurement, see the ITU-T
Y.1731 Ethernet Service OAM topics in the Junos OS Network Interfaces.
Required Privilege
Level
Related
Documentation
334
trace and maintenance

on page 327

Output Fields
show oam ethernet connectivity-fault-management loss-statistics

The monitor ethernet synthetic-loss-measurement command displays different output
at the CLI, depending on when you start a synthetic frame loss measurement:
Table 29 on page 335 lists the run-time output fields for the monitor ethernet
synthetic-loss-measurement command.
Output fields are listed in the approximate order in which they appear.
Table 29: monitor ethernet synthetic-loss-measurement Output Fields

Output Field Name
Output Field Description
ETH-SLM request to
Unicast MAC address of the remote peer MEP.
Interface
Name of the Ethernet physical, logical, or trunk interface to which the local MEP is attached.
SLM packets sent
Total number of synthetic loss message (SLM) PDU frames sent from the source MEP to the
remote MEP during this ETH-SLM session.
Total number of synthetic loss reply (SLR) PDU frames received by the source MEP from the
remote MEP during this measurement session.
Local TXFC1 value
Number of synthetic frames transmitted to the peer MEP for a test ID. A test ID is used to distinguish
each synthetic loss measurement because multiple measurements can be simultaneously activated
also on a given CoS and MEP pair. It must be unique at least within the context of any SLM for the
MEG and initiating MEP.
Local RXFC1 value
Number of synthetic frames received from the peer MEP for a test ID. The MEP generates a unique
test ID for the session, adds the source MEP ID, and initializes the local counters for the session
before SLM initiation. For each SLM PDU transmitted for the session (test ID), the local counter
TXFC1 is sent in the packet.
Last Received SLR frame

TXFCf(tc)
Value of the local counter TxFCl at the time of SLM frame transmission.

TXFCb(t
Value of the local counter RxFCl at the time of SLR frame transmission.
Frame loss (near-end)
Count of frame loss associated with ingress data frames.
Frame loss (far-end)
Count of frame loss associated with egress data frames.
335
Sample Output
monitor ethernet
synthetic-lossmeasurement
336
user@host> monitor ethernet synthetic-loss-measurement 00:05:85:73:39:4a

maintenance-domain md6 maintenance-association ma6 count 10
ETH-SLM request to 00:05:85:73:39:4a, interface ge-1/0/0.0
SLM packets sent
: 100
: 100
Local TXFC1 value
: 100
Local RXFC1 value
: 100
: 100
Last Received SLR frame TXFCb(tc)
: 100
SLM Frame Loss:
: 0 (0.00 %)
: 0 (0.00 %)
restart chassis-control
Syntax
<lcc number | sfc number>
<gracefully | immediately | soft>
Syntax (MX Series

Routers)
Syntax (PTX Series)
Release Information
Command introduced before JUNOS Release 7.4.

Command introduced in Junos OS Release 12.3 for MX2020 3D Universal Edge Routers.
Description
Options
Restart the chassis management process.

lcc number(Routing matrix only) (Optional) Restart the software process for a specific
T640 routing node that is connected to a TX Matrix platform. Replace number with
a value from 0 through 3.
sfc number(TX Matrix Plus routers only) (Optional) Restart the software process on
the TX Matrix Plus router (or switch-fabric chassis). Replace number with 0.
gracefully(Optional) Restart the software process.
immediately(Optional) Immediately restart the software process.
soft(Optional) Reread and reactivate the configuration without completely restarting
the software processes. For example, Border Gateway Protocol (BGP) peers stay
up and the routing table stays constant. Omitting this option results in a graceful
restart of the software process.
Required Privilege
Level
Related
Documentation
Output Fields
reset
restart
restart chassis-control gracefully on page 338

restart chassis-control soft on page 338
337
Sample Output
gracefully
user@host> restart chassis-control gracefully

Chassis control process started, pid 1631
soft
user@host> restart chassis-control soft

Chassis control process started, pid 1653
338
request chassis feb

Syntax
Syntax (ACX Series
Routers)
Release Information
Description
request chassis feb (offline | online | restart) slot slot-number

request chassis feb restart slot slot-number

Command introduced in Junos OS Release 12.2 for the ACX Series Universal Access
Routers.
(M120 router only) Control the operation of the specified Forwarding Engine Board (FEB).
(ACX Series routers) Restart the specified FEB.
Options
offlineTake the specified FEB offline.

onlineBring the specified FEB online.
restartRestart the specified FEB.
slot slot-numberFEB slot number. Replace slot-number with a value from 0 through 5.
Required Privilege
Level
Related
Documentation
Output Fields
maintenance
show chassis feb on page 442
show chassis fabric feb
show chassis fpc-feb-connectivity
feb
Switching Control Board Redundancy
request chassis feb offline slot 0 on page 340

request chassis feb online slot 0 on page 340
request chassis feb restart slot 0 on page 340
339
request chassis feb (M120 Router)

request chassis feb
offline slot 0
user@host> request chassis feb offline slot 0

Offline initiated, use show chassis feb to verify
request chassis feb

online slot 0
user@host> request chassis feb online slot 0

Online initiated, use show chassis feb to verify
request chassis feb

restart slot 0
user@host> request chassis feb restart slot 0

Restart initiated, use show chassis feb to verify
request chassis feb (ACX Series Routers)

user@host> request chassis feb restart slot 0
FEB will be restarted NOW.
340
request system snapshot (ACX Series)

Syntax
Release Information
Description
request system snapshot

<partition>
<partition slice alternate>
<slice alternate>
Command introduced in Junos OS Release 12.2 for ACX Series Routers.

On the router, take a snapshot of the files currently used to run the routerthe complete
contents of the root (/) and /config directories, which include the running Junos OS and
the active configuration.
CAUTION: After you run the request system snapshot command, you cannot
return to the previous version of the software, because the running and backup
copies of the software are identical.
Options
noneBack up the currently running software and configuration by copying the root (/)
and /config directoriesthe snapshotto the media that the router did not boot
from. If the router booted from internal media, the snapshot is copied to an external
universal serial bus (USB) storage media. If the router booted from external USB
media, the snapshot is copied to the active slice of the internal mediada0s1 or
da0s2. (If the snapshot destination is external media but a USB flash drive is not
connected, an error message is displayed.)
partition(Optional) Repartition the flash drive or the USB media before a snapshot
occurs. If the partition table on the flash drive is corrupted, the request system
snapshot partition command fails and reports errors.
slice alternate(Optional) Take a snapshot of the active slice and copy it to the alternate
slice on the boot media.

Required Privilege
Level
Related
Documentation
maintenance
request system snapshot on page 342

request system snapshot partition (USB Storage Device) on page 342
request system snapshot partition (Active Slice of the NAND Flash Device) on page 342
request system snapshot partition slice alternate on page 342
request system snapshot slice alternate on page 342
341
Sample Output
request system
snapshot

request system
snapshot partition
(USB Storage Device)

Clearing current label...
Partitioning usb media (da1) ...
Partitions on snapshot:
Partition Mountpoint Size
Snapshot argument
a
/
312MB
root-size
e
/config
47MB
config-size
f
/var
620MB
var-size
Running newfs (620MB) on usb media /var partition (da1s1f)...
request system
snapshot partition
(Active Slice of the
NAND Flash Device)

request system
snapshot partition
slice alternate
user@host> request system snapshot partition slice alternate

request system
snapshot slice
alternate
user@host> request system snapshot slice alternate

342
show bgp neighbor

Syntax
Syntax (EX Series

Switch and QFX
Series)
Release Information
Description
Options
show bgp neighbor

<exact-instance instance-name>
<instance instance-name>
<logical-system (all | logical-system-name)>
<neighbor-address>
<orf (detail | neighbor-address)
show bgp neighbor
<neighbor-address>
<orf (neighbor-address | detail)
Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 11.3 for the QFX Series.
orf option introduced in Junos OS Release 9.2.
exact-instance option introduced in Junos OS Release 11.4.
Display information about BGP peers.
noneDisplay information about all BGP peers.
exact-instance instance-name(Optional) Display information for the specified instance
only.
instance instance-name(Optional) Display information about BGP peers for all routing
instances whose name begins with this string (for example, cust1, cust11, and cust111
are all displayed when you run the show bgp neighbor instance cust1 command).
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical
systems or on a particular logical system.

neighbor-address(Optional) Display information for only the BGP peer at the specified
IP address.
orf (detail | neighbor-address)(Optional) Display outbound route-filtering information
for all BGP peers or only for the BGP peer at the specified IP address. The default is
to display brief output. Use the detail option to display detailed output.
Required Privilege
Level
Related
Documentation
For information about the local-address, nlri, hold-time, and preference statements, see
the Junos OS Routing Protocols Configuration Guide.
view
clear bgp neighbor
343
show bgp neighbor on page 351

show bgp neighbor (CLNS) on page 351
show bgp neighbor (Layer 2 VPN) on page 352
show bgp neighbor (Layer 3 VPN) on page 354
show bgp neighbor neighbor-address on page 355
show bgp neighbor neighbor-address on page 355
show bgp neighbor orf neighbor-address detail on page 356
Output Fields
Table 30 on page 344 describes the output fields for the show bgp neighbor command.
Table 30: show bgp neighbor Output Fields

Field Name
Field Description
Peer
Address of the BGP neighbor. The address is followed by the neighbor port number.
AS
AS number of the peer.
Local
Address of the local routing device. The address is followed by the peer port number.
Type
Type of peer: Internal or External.
State
Current state of the BGP session:
ActiveBGP is initiating a transport protocol connection in an attempt to connect to a peer. If the
connection is successful, BGP sends an Open message.
ConnectBGP is waiting for the transport protocol connection to be completed.
EstablishedThe BGP session has been established, and the peers are exchanging update messages.
IdleThis is the first stage of a connection. BGP is waiting for a Start event.
OpenConfirmBGP has acknowledged receipt of an open message from the peer and is waiting
to receive a keepalive or notification message.
OpenSentBGP has sent an open message and is waiting to receive an open message from the
peer.
Flags
Internal BGP flags:
Aggregate LabelBGP has aggregated a set of incoming labels (labels received from the peer) into
a single forwarding label.
CleanUpThe peer session is being shut down.
DeleteThis peer has been deleted.
IdledThis peer has been permanently idled.
ImportEvalAt the last commit operation, this peer was identified as needing to reevaluate all
received routes.
344
InitializingThe peer session is initializing.
SendRtnMessages are being sent to the peer.
SyncThis peer is synchronized with the rest of the peer group.
TryConnectAnother attempt is being made to connect to the peer.
UnconfiguredThis peer is not configured.
WriteFailedAn attempt to write to this peer failed.
Table 30: show bgp neighbor Output Fields (continued)

Field Name
Field Description
Last state
Previous state of the BGP session:
ActiveBGP is initiating a transport protocol connection in an attempt to connect to a peer. If the
connection is successful, BGP sends an Open message.
ConnectBGP is waiting for the transport protocol connection to be completed.
EstablishedThe BGP session has been established, and the peers are exchanging update messages.
IdleThis is the first stage of a connection. BGP is waiting for a Start event.
OpenConfirmBGP has acknowledged receipt of an open message from the peer and is waiting
to receive a keepalive or notification message.
OpenSentBGP has sent an open message and is waiting to receive an open message from the
peer.
Last event
Last activity that occurred in the BGP session:
ClosedThe BGP session closed.
ConnectRetryThe transport protocol connection failed, and BGP is trying again to connect.
HoldTimeThe session ended because the hold timer expired.
KeepAliveThe local routing device sent a BGP keepalive message to the peer.
OpenThe local routing device sent a BGP open message to the peer.
OpenFailThe local routing device did not receive an acknowledgment of a BGP open message
from the peer.
Last error
RecvKeepAliveThe local routing device received a BGP keepalive message from the peer.
RecvNotifyThe local routing device received a BGP notification message from the peer.
RecvOpenThe local routing device received a BGP open message from the peer.
RecvUpdateThe local routing device received a BGP update message from the peer.
StartThe peering session started.
StopThe peering session stopped.
TransportErrorA TCP error occurred.
Last error that occurred in the BGP session:
CeaseAn error occurred, such as a version mismatch, that caused the session to close.
Finite State Machine ErrorIn setting up the session, BGP received a message that it did not
understand.
Hold Time ExpiredThe session's hold time expired.
Message Header ErrorThe header of a BGP message was malformed.
Open Message ErrorA BGP open message contained an error.
NoneNo errors occurred in the BGP session.
Update Message ErrorA BGP update message contained an error.
Export
Name of the export policy that is configured on the peer.
Import
Name of the import policy that is configured on the peer.
345

Field Name
Field Description
Options
Configured BGP options:
AddressFamilyConfigured address family: inet or inet-vpn.
AutheKeyChainAuthentication key change is enabled.
DropPathAttributesCertain path attributes are configured to be dropped from neighbor updates
during inbound processing.
GracefulRestartGraceful restart is configured.
HoldTimeHold time configured with the hold-time statement. The hold time is three times the
interval at which keepalive messages are sent.
IgnorePathAttributesCertain path attributes are configured to be ignored in neighbor updates
during inbound processing.
Local AddressAddress configured with the local-address statement.
MultihopAllow BGP connections to external peers that are not on a directly connected network.
NLRIConfigured MBGP state for the BGP group: multicast, unicast, or both if you have configured
nlri any.
Peer ASConfigured peer autonomous system (AS).
PreferencePreference value configured with the preference statement.
RefreshConfigured to refresh automatically when the policy changes.
Rib-groupConfigured routing table group.
Path-attributes
dropped
Path attribute codes that are dropped from neighbor updates.
Path-attributes ignored
Path attribute codes that are ignored during neighbor updates.
Authentication key
change
(appears only if the authentication-keychain statement has been configured) Name of the
authentication keychain enabled.
Authentication
algorithm
(appears only if the authentication-algorithm statement has been configured) Type of authentication
algorithm enabled: hmac or md5.
Address families
configured
Names of configured address families for the VPN.
Local Address
Address of the local routing device.
Remove-private options
Options associated with the remove-private statement.
Holdtime
Hold time configured with the hold-time statement. The hold time is three times the interval at which
keepalive messages are sent.
Flags for NLRI

inet-label-unicast
Flags related to labeled-unicast:
346
TrafficStatisticsCollection of statistics for labeled-unicast traffic is enabled.

Field Name
Field Description
Traffic statistics
Information about labeled-unicast traffic statistics:
OptionsOptions configured for collecting statistics about labeled-unicast traffic.
FileName and location of statistics log files.
sizeSize of all the log files, in bytes.
filesNumber of log files.
Traffic Statistics
Interval
Time between sample periods for labeled-unicast traffic statistics, in seconds.
Preference
Preference value configured with the preference statement.
Outbound Timer
Time for which the route is available in Junos OS routing table before it is exported to BGP. This field
is displayed in the output only if the out-delay parameter is configured to a non-zero value.
Number of flaps
Number of times the BGP session has gone down and then come back up.
Peer ID
Router identifier of the peer.
Group index
Index number for the BGP peer group. The index number differentiates between groups when a single
BGP group is split because of different configuration options at the group and peer levels.
Peer index
Index that is unique within the BGP group to which the peer belongs.
Local ID
Router identifier of the local routing device.
Local Interface
Name of the interface on the local routing device.
Active holdtime
Hold time that the local routing device negotiated with the peer.
Keepalive Interval
Keepalive interval, in seconds.
BFD
Status of BFD failure detection.
Local Address
Name of directly connected interface over which direct EBGP peering is established.
NLRI for restart

configured on peer
Names of address families configured for restart.
NLRI advertised by peer
Address families supported by the peer: unicast or multicast.
NLRI for this session
Address families being used for this session.
Peer supports Refresh

capability
Remote peers ability to send and request full route table readvertisement (route refresh capability).
For more information, see RFC 2918, Route Refresh Capability for BGP-4.
Restart time configured

on peer
Configured time allowed for restart on the neighbor.
347

Field Name
Field Description
Stale routes from peer

are kept for
When graceful restart is negotiated, the maximum time allowed to hold routes from neighbors after
the BGP session has gone down.
Peer does not support

Restarter functionality
Graceful restart restarter-mode is disabled on the peer.
Peer does not support

Receiver functionality
Graceful restart helper-mode is disabled on the peer.
Restart time requested

by this peer
Restart time requested by this neighbor during capability negotiation.
Restart flag received

from the peer
When this field appears, the BGP speaker has restarted (Restarting), and this peer should not wait
for the end-of-rib marker from the speaker before advertising routing information to the speaker.
NLRI that peer supports

restart for
Neighbor supports graceful restart for this address family.
NLRI peer can save

forwarding state
Neighbor supporting this address family saves all forwarding states.
NLRI that peer saved

forwarding for
Neighbor saves all forwarding states for this address family.
NLRI that restart is

negotiated for
Router supports graceful restart for this address family.
NLRI of received
end-of-rib markers
Address families for which end-of-routing-table markers are received from the neighbor.
NLRI of all end-of-rib

markers sent
Address families for which end-of-routing-table markers are sent to the neighbor.
Peer supports 4 byte AS

extension (peer-as 1)
Peer understands 4-byte AS numbers in BGP messages. The peer is running Junos OS Release 9.1 or
later.
NLRIs for which peer

can receive multiple
paths
Appears in the command output of the local router if the downstream peer is configured to receive
multiple BGP routes to a single destination, instead of only receiving the active route.
Possible value is inet-unicast.
NLRIs for which peer

can send multiple
paths: inet-unicast
Appears in the command output of the local router if the upstream peer is configured to send multiple
BGP routes to a single destination, instead of only sending the active route.
Possible value is inet-unicast.
348

Field Name
Field Description
Table inet.number
Information about the routing table:
RIB StateBGP is in the graceful restart process for this routing table: restart is complete or restart
in progress.
BitNumber that represents the entry in the routing table for this peer.
Send stateState of the BGP group: in sync, not in sync, or not advertising.
Active prefixesNumber of prefixes received from the peer that are active in the routing table.
Received prefixesTotal number of prefixes from the peer, both active and inactive, that are in the
routing table.
Accepted prefixesTotal number of prefixes from the peer that have been accepted by a routing
policy.
Suppressed due to dampingNumber of routes currently inactive because of damping or other
reasons. These routes do not appear in the forwarding table and are not exported by routing
protocols.
Last traffic (seconds)
Last time any traffic was received from the peer or sent to the peer, and the last time the local routing
device checked.
Input messages
Messages that BGP has received from the receive socket buffer, showing the total number of messages,
number of update messages, number of times a policy is changed and refreshed, and the buffer size
in octets. The buffer size is 16 KB.
Output messages
Messages that BGP has written to the transmit socket buffer, showing the total number of messages,
number of update messages, number of times a policy is changed and refreshed, and the buffer size
in octets. The buffer size is 16 KB.
Input dropped path

attributes
Information about dropped path attributes:
Input ignored path

attributes
CodePath attribute code.
CountPath attribute count.
Information about ignored path attributes:
CodePath attribute code.
CountPath attribute count.
Output queue
Number of BGP packets that are queued to be transmitted to a particular neighbor for a particular
routing table. Output queue 0 is for unicast NLRIs, and queue 1 is for multicast NLRIs.
Trace options
Configured tracing of BGP protocol packets and operations.
Trace file
Name of the file to receive the output of the tracing operation.
Filter Updates recv
(orf option only) Number of outbound-route filters received for each configured address family.
NOTE: The counter is cumulative. For example, the counter is increased after the remote peer either
resends or clears the outbound route filtering prefix list.
349

Field Name
Field Description
Immediate
(orf option only) Number of route updates received with the immediate flag set. The immediate flag
indicates that the BGP peer should readvertise the updated routes.
NOTE: The counter is cumulative. For example, the counter is increased after the remote peer either
resends or clears the outbound route filtering prefix list.
Filter
(orf option only) Type of prefix filter received: prefix-based or extended-community.
Received filter entries
(orf option only) List of received filters displayed.
seq
(orf option only) Numerical order assigned to this prefix entry among all the received outbound route
filter prefix entries.
prefix
(orf option only) Address for the prefix entry that matches the filter.
minlength
(orf option only) Minimum prefix length, in bits, required to match this prefix.
maxlength
(orf option only) Maximum prefix length, in bits, required to match this prefix.
match
(orf option only) For this prefix match, whether to permit or deny route updates.
350
Sample Output
show bgp neighbor
user@host > show bgp neighbor

Peer: 10.255.7.250+179 AS 10
Local: 10.255.7.248+63740 AS 10
Type: Internal
State: Established
Flags: <Sync>
Last State: OpenConfirm
Last Event: RecvKeepAlive
Last Error: None
Export: [ redist_static ]
Options: <Preference LocalAddress PeerAS Refresh>
Local Address: 10.255.7.248 Holdtime: 90 Preference: 170 Outbound Timer: 50
Number of flaps: 0
Peer ID: 10.255.7.250
Local ID: 10.255.7.248
Active Holdtime: 90
Keepalive Interval: 30
Group index: 0
Peer index: 0
BFD: disabled, down
NLRI for restart configured on peer: inet-unicast
NLRI advertised by peer: inet-unicast
NLRI for this session: inet-unicast
Peer supports Refresh capability (2)
Stale routes from peer are kept for: 300
Peer does not support Restarter functionality
NLRI that restart is negotiated for: inet-unicast
NLRI of received end-of-rib markers: inet-unicast
NLRI of all end-of-rib markers sent: inet-unicast
Peer supports 4 byte AS extension (peer-as 10)
Peer does not support Addpath
Table inet.0 Bit: 10000
RIB State: BGP restart is complete
Send state: in sync
Active prefixes:
1
Received prefixes:
1
Accepted prefixes:
1
Suppressed due to damping:
0
Advertised prefixes:
1
Last traffic (seconds): Received 9
Sent 5
Checked 5
Input messages: Total 36
Updates 2
Refreshes 0
Octets 718
Output messages: Total 37
Updates 1
Refreshes 0
Octets 796
Output Queue[0]: 0
Peer: 10.255.162.214+52193 AS 100 Local: 10.255.167.205+179 AS 100
Type: Internal
State: Established (route reflector client)Flags: <Sync>
Last Error: None
Options: <Preference LocalAddress Cluster AddressFamily Rib-group Refresh>
Address families configured: inet-unicast inet-vpn-unicast route-target
Local Address: 10.255.167.205 Holdtime: 90 Preference: 170
Number of flaps: 0
Peer ID: 10.255.162.214 Local ID: 10.255.167.205
Active Holdtime: 90
Group index: 0
Peer index: 1
show bgp neighbor

(CLNS)
user@host> show bgp neighbor

Peer: 10.245.245.1+179 AS 200 Local: 10.245.245.3+3770 AS 100
Type: External
State: Established
Flags: <ImportEval Sync>
Last Error: None
Options: <Multihop Preference LocalAddress HoldTime AddressFamily PeerAS
Rib-group Refresh>
Address families configured: iso-vpn-unicast
Number of flaps: 0
Peer ID: 10.245.245.1
Local ID: 10.245.245.3
Active Holdtime: 90
351
Peer index: 0
NLRI advertised by peer: iso-vpn-unicast
NLRI for this session: iso-vpn-unicast
Table bgp.isovpn.0 Bit: 10000
RIB State: VPN restart is complete
Send state: in sync
Active prefixes:
3
Received prefixes:
3
0
3
Table aaaa.iso.0
Send state: not advertising
Active prefixes:
3
Received prefixes:
3
0
Sent 5
Updates 4
Updates 3
Output Queue[0]: 0
Output Queue[1]: 0
show bgp neighbor

(Layer 2 VPN)
352
Checked 5
Refreshes 0
Refreshes 0
Octets 33385
Octets 33305

Peer: 10.69.103.2
AS 65100 Local: 10.69.103.1
AS 65103
Type: External
State: Active
Flags: <ImportEval>
Last State: Idle
Last Event: Start
Last Error: None
Export: [ BGP-INET-import ]
Options: <Preference LocalAddress HoldTime GracefulRestart AddressFamily
PeerAS
Refresh>
Address families configured: inet-unicast
Number of flaps: 0
Peer: 10.69.104.2
AS 65100 Local: 10.69.104.1
AS 65104
Type: External
State: Active
Flags: <ImportEval>
Last State: Idle
Last Event: Start
Last Error: None
Export: [ BGP-L-import ]
Options: <Preference LocalAddress HoldTime GracefulRestart AddressFamily PeerAS
Refresh>
Address families configured: inet-labeled-unicast
Number of flaps: 0
Peer: 10.255.14.182+179 AS 69
Local: 10.255.14.176+2131 AS 69
Type: Internal
State: Established
Flags: <ImportEval>
Last Error: None
Rib-group Refresh>
Address families configured: inet-vpn-unicast l2vpn
Number of flaps: 0
Peer ID: 10.255.14.182
Local ID: 10.255.14.176
Active Holdtime: 90
NLRI for restart configured on peer: inet-vpn-unicast l2vpn
NLRI advertised by peer: inet-vpn-unicast l2vpn
NLRI for this session: inet-vpn-unicast l2vpn
Restart time configured on the peer:

Stale routes from peer are kept for:
Restart time requested by this peer:
NLRI that peer supports restart for:
NLRI peer can save forwarding state:
NLRI that peer saved forwarding for:
NLRI that restart is negotiated for:
NLRI of received end-of-rib markers:
Table bgp.l3vpn.0 Bit: 10000
RIB State: BGP restart in progress
RIB State: VPN restart in progress
Send state: in sync
Active prefixes:
10
Received prefixes:
10
Suppressed due to damping: 0
Send state: in sync
Active prefixes:
1
Received prefixes:
1
Table BGP-INET.inet.0 Bit: 30000
Send state: in sync
Active prefixes:
2
Received prefixes:
2
Table BGP-L.inet.0 Bit: 40000
Send state: in sync
Active prefixes:
2
Received prefixes:
2
Table LDP.inet.0 Bit: 50000
Send state: in sync
Active prefixes:
1
Received prefixes:
1
Table OSPF.inet.0 Bit: 60000
Send state: in sync
Active prefixes:
2
Received prefixes:
2
Table RIP.inet.0 Bit: 70000
Send state: in sync
Active prefixes:
2
Received prefixes:
2
Table STATIC.inet.0 Bit: 80000
Send state: in sync
120
300
120
inet-vpn-unicast
inet-vpn-unicast
inet-vpn-unicast
inet-vpn-unicast
inet-vpn-unicast
l2vpn
l2vpn
l2vpn
l2vpn
l2vpn
353
Active prefixes:
1
Received prefixes:
1
Table L2VPN.l2vpn.0 Bit: 90000
Send state: in sync
Active prefixes:
1
Received prefixes:
1
Sent 0
Updates 13
Updates 0
Output Queue[0]: 0
Output Queue[1]: 0
Output Queue[2]: 0
Output Queue[3]: 0
Output Queue[4]: 0
Output Queue[5]: 0
Output Queue[6]: 0
Output Queue[7]: 0
Output Queue[8]: 0
show bgp neighbor

(Layer 3 VPN)
354
Checked 0
Refreshes 0
Refreshes 0
Octets 1053
Octets 105

Peer: 4.4.4.4+179
AS 10045 Local: 5.5.5.5+1214
AS 10045
Type: Internal
State: Established
Flags: <ImportEval>
Last Error: None
Export: [ match-all ] Import: [ match-all ]
Rib-group Refresh>
Address families configured: inet-vpn-unicast
Flags for NLRI inet-labeled-unicast: TrafficStatistics
Traffic Statistics: Options: all File: /var/log/bstat.log
size 131072 files 10
Traffic Statistics Interval: 60
Number of flaps: 0
Peer ID: 192.168.1.110
Local ID: 192.168.1.111
Active Holdtime: 90
NLRI for restart configured on peer: inet-vpn-unicast
NLRI advertised by peer: inet-vpn-unicast
NLRI for this session: inet-vpn-unicast
Restart time configured on the peer: 120
Restart time requested by this peer: 120
NLRI that peer supports restart for: inet-vpn-unicast
NLRI peer can save forwarding state: inet-vpn-unicast
NLRI that peer saved forwarding for: inet-vpn-unicast
NLRI that restart is negotiated for: inet-vpn-unicast
NLRI of received end-of-rib markers: inet-vpn-unicast
NLRI of all end-of-rib markers sent: inet-vpn-unicast
Send state: in sync
Active prefixes:
2
Received prefixes:
2
Table vpn-green.inet.0 Bit: 20001

Send state: in sync
Active prefixes:
2
Received prefixes:
2
Sent 20
Checked 20
Updates 2
Refreshes 0
Updates 2
Refreshes 0
Output Queue[0]: 0
Output Queue[1]: 0
Trace options: detail packets
Trace file: /var/log/bgpgr.log size 131072 files 10
show bgp neighbor

neighbor-address
Octets 856
Octets 1066
user@host> show bgp neighbor 192.168.1.111

Peer: 10.255.245.12+179 AS 35 Local: 10.255.245.13+2884 AS 35
Type: Internal
State: Established (route reflector client)Flags: <Sync>
Last Error: None
Options: <Preference LocalAddress HoldTime Cluster AddressFamily Rib-group
Refresh>
Address families configured: inet-vpn-unicast inet-labeled-unicast
Flags for NLRI inet-vpn-unicast: AggregateLabel
Flags for NLRI inet-labeled-unicast: AggregateLabel
Number of flaps: 0
Peer ID: 10.255.245.12
Local ID: 10.255.245.13
Active Holdtime: 90
BFD: disabled
NLRI advertised by peer: inet-vpn-unicast inet-labeled-unicast
NLRI for this session: inet-vpn-unicast inet-labeled-unicast
Restart time configured on the peer: 300
Restart time requested by this peer: 300
NLRI that peer supports restart for: inet-unicast inet6-unicast
NLRI that restart is negotiated for: inet-unicast inet6-unicast
NLRI of received end-of-rib markers: inet-unicast inet6-unicast
NLRI of all end-of-rib markers sent: inet-unicast inet6-unicast
RIB State: restart is complete
Send state: in sync
Active prefixes: 4
Received prefixes: 6
Table inet6.0 Bit: 20000
RIB State: restart is complete
Send state: in sync
Active prefixes: 0
Received prefixes: 2
Sent 3
Checked 3
Updates 6
Refreshes 0
Octets 403
Updates 3
Refreshes 0
Octets 365
Output Queue[0]: 0
Output Queue[1]: 0
Trace options: detail packets
Trace file: /var/log/bgpgr size 131072 files 10
user@host> show bgp neighbor 192.168.4.222
355
show bgp neighbor

neighbor-address
Peer: 192.168.4.222+4902 AS 65501 Local: 192.168.4.221+179 AS 65500

Type: External
State: Established
Flags: <Sync>
Last Error: Cease
Export: [ export-policy ] Import: [ import-policy ]
Options: <Preference HoldTime AddressFamily PeerAS PrefixLimit Refresh>
Address families configured: inet-unicast inet-multicast
Holdtime: 60000 Preference: 170
Number of flaps: 4
Last flap event: RecvUpdate
Error: 'Cease' Sent: 5 Recv: 0
Peer ID: 10.255.245.6
Local ID: 10.255.245.5
Active Holdtime: 60000
Peer index: 0
BFD: disabled, down
Local Interface: fxp0.0
NLRI advertised by peer: inet-unicast inet-multicast
NLRI for this session: inet-unicast inet-multicast
Send state: in sync
Active prefixes:
8
Received prefixes:
10
Accepted prefixes:
10
0
3
Send state: in sync
Active prefixes:
0
Received prefixes:
0
Accepted prefixes:
0
0
0
Last traffic (seconds): Received 357 Sent 357 Checked 357
Input messages: Total 4 Updates 2 Refreshes 0 Octets 211
Output messages: Total 4 Updates 1 Refreshes 0 Octets 147
Output Queue[0]: 0
Output Queue[1]: 0
Trace options: all
Trace file: /var/log/bgp size 10485760 files 10
show bgp neighbor orf

neighbor-address
detail
user@host > show bgp neighbor orf 192.168.165.56 detail

Peer: 192.168.165.56+179 Type: External
Group: ext1
inet-unicast
Filter updates recv:
1 Immediate:
1
Filter: prefix-based receive
Received filter entries:
seq 1: prefix 2.2.2.2/32: minlen 32: maxlen 32: match deny:
inet6-unicast
Filter updates recv:
0 Immediate:
Filter: prefix-based receive
Received filter entries:
*:*
356
show bgp replication

Syntax
Release Information
Command introduced in JUNOS Release 8.5.

Description
Displays the status of BGP state replication between the master and backup Routing
Engines on devices that have nonstop active routing configured on them.
Options
This command has no options.
Required Privilege
Level
view
show bgp replication (for Master) on page 358

show bgp replication (for Backup) on page 358
Output Fields
Table 31 on page 357 lists the output fields for the show bgp replication command. Output
fields are listed in the approximate order in which they appear.
Table 31: show bgp replication Output Fields

Field Name
Field Description
session state
State of the current internal BGP state replication session, Up or Down, and the duration for which
the session has been in the indicated state.
flaps
Total number of flaps that occurred.
protocol state
Current state of the protocol operation, Active, Connect, Idle, and the duration for which the protocol
has been in the indicated state.
synchronization state
Synchronization state at the time of executing the command. The states can be:
number of peers waiting
Idle
NeighborIndicates that the neighbor state synchronization is in progress.
AckWaitIndicates that the request processing is over.
ORFIndicates that the outbound routing filter synchronization is in progress.
RIBIndicates that the routing table synchronization is in progress.
Complete
Total number of peers waiting for various messages:
AckWaitNumber of peers waiting for a connection establishment or completed acknowledgment
messages.
SoWaitNumber of peers waiting for TCP socket-related operations.
ScheduledNumber of peers being synchronized.
357
Table 31: show bgp replication Output Fields (continued)

Field Name
Field Description
messages sent
Number of various types of messages that have been sent since internal replication session became
active:
messages received
OpenNumber of Open messages sent.
EstablishNumber of connection establishment acknowledgment messages sent.
UpdateNumber of update messages sent.
ErrorNumber of error messages sent.
CompleteNumber of connection complete acknowledgment messages sent.
Total number of messages received:
OpenNumber of Open messages received.
RequestNumber of request messages received:
WildcardNumber of requests received that used wildcards in the target address.
TargetedNumber of requests received that used a specific address.
EstablishAckNumber of connection establishment acknowledgement messages received.
CompleteAckNumber of connection completed acknowledgement messages received.
Sample Output
(for Master)
user@host> show bgp replication

Synchronization master:
Session state: Up, Since: 44:07
Flaps: 0
Protocol state: Idle, Since: 14
Synchronization state: Complete
Number of peers waiting: AckWait: 0, SoWait: 0, Scheduled: 0
Messages sent: Open 1, Establish 924, Update 381, Error 60, Complete 114
Messages received: Open 1, Request 1 wildcard 113 targeted, EstablishAck 924,
CompleteAck 114

(for Backup)
user@host> show bgp replication

Synchronization backup:
State: Established 13 ago
, Unsync timer: 2
Unsync entry queue:
Instance: 0 Neighbor:
358
30.30.30.1
40.40.40.3
40.40.40.4
40.40.40.5
40.40.40.6
40.40.40.1
40.40.40.2
elapsed:
elapsed:
elapsed:
elapsed:
elapsed:
elapsed:
elapsed:
7
7
7
7
7
7
7
show bgp summary

Syntax
Syntax (EX Series

Switch and QFX
Series)
Release Information
Description
Options
show bgp summary

show bgp summary

exact-instance option introduced in Junos OS Release 11.4.
Display BGP summary information.
noneDisplay BGP summary information for all routing instances.
exact-instance instance-name(Optional) Display information for the specified instance
only.
instance instance-name(Optional) Display information for all routing instances whose
name begins with this string (for example, cust1, cust11, and cust111 are all displayed
when you run the show bgp summary instance cust1 command). The instance name
can be master for the main instance, or any valid configured instance name or its
prefix.

Required Privilege
Level
Output Fields
view
show bgp summary (When a Peer Is Not Established) on page 362

show bgp summary (When a Peer Is Established) on page 362
show bgp summary (CLNS) on page 362
show bgp summary (Layer 2 VPN) on page 362
show bgp summary (Layer 3 VPN) on page 363
Table 32 on page 359 describes the output fields for the show bgp summary command.
Table 32: show bgp summary Output Fields

Field Name
Field Description
Groups
Number of BGP groups.
Peers
Number of BGP peers.
359
Table 32: show bgp summary Output Fields (continued)

Field Name
Field Description
Down peers
Number of down BGP peers.
Table
Name of routing table.
Tot Paths
Total number of paths.
Act Paths
Number of active routes.
Suppressed
Number of routes currently inactive because of damping or other reasons. These routes do not appear
in the forwarding table and are not exported by routing protocols.
History
Number of withdrawn routes stored locally to keep track of damping history.
Damp State
Number of routes with a figure of merit greater than zero, but still active because the value has not
reached the threshold at which suppression occurs.
Pending
Routes in process by BGP import policy.
Peer
Address of each BGP peer. Each peer has one line of output.
AS
Peer's AS number.
InPkt
Number of packets received from the peer.
OutPkt
Number of packets sent to the peer.
OutQ
Number of BGP packets that are queued to be transmitted to a particular neighbor. It normally is 0
because the queue usually is emptied quickly.
Flaps
Number of times the BGP session has gone down and then come back up.
Last Up/Down
Last time since the neighbor transitioned to or from the established state.
360
Table 32: show bgp summary Output Fields (continued)

Field Name
Field Description
State|#Active
/Received/Accepted
/Damped
Multipurpose field that displays information about BGP peer sessions. The fields contents depend
upon whether a session is established and whether it was established on the main routing device or
in a routing instance.
If a peer is not established, the field shows the state of the peer session: Active, Connect, or Idle.
In general, the Idle state is the first stage of a connection. BGP is waiting for a Start event. A session
can be idle for other reasons as well. The reason that a session is idle is sometimes displayed. For
example: Idle (Removal in progress) or Idle (LicenseFailure).
If a BGP session is established on the main routing device, the field shows the number of active,
received, accepted, and damped routes that are received from a neighbor and appear in the inet.0
(main) and inet.2 (multicast) routing tables. For example, 8/10/10/2 and 2/4/4/0 indicate the
following:
8 active routes, 10 received routes, 10 accepted routes, and 2 damped routes from a BGP peer
appear in the inet.0 routing table.
2 active routes, 4 received routes, 4 accepted routes, and no damped routes from a BGP peer
appear in the inet.2 routing table.
If a BGP session is established in a routing instance, the field indicates the established (Establ)
state, identifies the specific routing table that receives BGP updates, and shows the number of
active, received, and damped routes that are received from a neighbor. For example, Establ
VPN-AB.inet.0: 2/4/0 indicates the following:
The BGP session is established.
Routes are received in the VPN-AB.inet.0 routing table.
The local routing device has two active routes, four received routes, and no damped routes from
a BGP peer.
When a BGP session is established, the peers are exchanging update messages.
361
Sample Output
show bgp summary
(When a Peer Is Not
Established)
user@host> show bgp summary

Groups: 2 Peers: 4 Down peers: 1
Table
Tot Paths Act Paths Suppressed
History Damp State
Pending
inet.0
6
4
0
0
0
0
Peer
AS
InPkt
OutPkt
OutQ
Flaps Last Up/Dwn
State|#Active/Received/Damped...
10.0.0.3
65002
86
90
0
2
42:54 0/0/0
0/0/0
10.0.0.4
65002
90
91
42:54 0/2/0
0/0/0
10.0.0.6
10.1.12.1
65002
65001
87
89
90
89
0
0
3
1
3 Active
42:54 4/4/0
0/0/0
show bgp summary

(When a Peer Is
Established)

Table
History Damp State
Pending
inet.0
6
4
0
0
0
0
Peer
AS
InPkt
OutPkt
OutQ
Flaps Last Up/Dwn
10.0.0.2
65002
88675
88652
0
2
42:38 2/4/0
0/0/0
10.0.0.3
65002
54528
54532
2w4d22h 0/0/0
0/0/0
10.0.0.4
65002
51597
51584
2w3d22h 2/2/0
OutPkt
OutQ
1737
0/0/0
show bgp summary

(CLNS)
show bgp summary

(Layer 2 VPN)
362

Peer
AS
InPkt
10.245.245.1
200
1735
bgp.isovpn.0: 3/3/0
aaaa.iso.0: 3/3/0
Flaps Last Up/Dwn

0
14:26:12 Establ

Table
History Damp State
bgp.l2vpn.0
1
1
0
0
0
inet.0
0
0
0
0
0
Peer
AS
InPkt
OutPkt
OutQ
Flaps Last
Up/Dwn State|#Active/Received/Damped...
10.255.245.35
65299
72
74
0
1
19:00
bgp.l2vpn.0: 1/1/0
frame-vpn.l2vpn.0: 1/1/0
10.255.245.36
65299
2164
2423
0
4
19:50
bgp.l2vpn.0: 0/0/0
10.255.245.37
65299
36
37
0
4
17:07
Pending
0
0
Establ
Establ
Establ
inet.0: 0/0/0
10.255.245.39
65299
bgp.l2vpn.0: 0/0/0
10.255.245.69
65299
inet.0: 0/0/0
show bgp summary

(Layer 3 VPN)
138
168
53:48 Establ
134
140
53:42 Establ

Table
History Damp State Pending
bgp.l3vpn.0
2
2
0
0
0
0
Peer
AS
InPkt
OutPkt
OutQ
Flaps Last Up/Dwn
10.39.1.5
2
21
22
0
0
6:26 Establ
VPN-AB.inet.0: 1/1/0
10.255.71.15
1
19
21
0
0
6:17 Establ
bgp.l3vpn.0: 2/2/0
VPN-A.inet.0: 1/1/0
VPN-AB.inet.0: 2/2/0
VPN-B.inet.0: 1/1/0
363
show chassis alarms

Syntax
show chassis alarms
Syntax (TX Matrix

Routers)
show chassis alarms

<lcc number | scc>
Syntax (TX Matrix Plus

Routers)
Syntax (MX Series
Routers)
show chassis alarms

show chassis alarms
<all-members>
<local>
<member member-id>
Syntax (MX2010 3D
Universal Edge
Routers)
show chassis alarms
Syntax (MX2020 3D
Universal Edge
Routers)
show chassis alarms
Syntax (QFX Series)
show chassis alarms

<interconnect-device name>
<node-device name>
Syntax (PTX Series

Packet Transport
Switches)
show chassis alarms
Syntax (ACX Series

Universal Access
Routers)
show chassis alarms
Release Information
Description
Options

sfc option for the TX Matrix Plus router introduced in Junos OS Release 9.6.
Command introduced in Junos OS Release 12.1 for the PTX Series Packet Transport
Switches.
Routers.
Display information about the conditions that have been configured to trigger alarms.
noneDisplay information about the conditions that have been configured to trigger
alarms.
364
all-members(MX Series routers only) (Optional) Display information about alarm
conditions for all the member routers of the Virtual Chassis configuration.
interconnect-device name(QFabric systems only) (Optional) Display information about
alarm conditions for the Interconnect device.

lcc number (TX Matrix and TX Matrix Plus routers only) (Optional) On the TX Matrix
router, show information about a specified T640 router (or line-card chassis) that
is connected to the TX Matrix router. On the TX Matrix Plus router, show information
about a specified T1600 router (or line-card chassis) that is connected to the TX
Matrix Plus router. Replace number with a value from 0 through 3.
local(MX Series routers only) (Optional) Display information about alarm conditions
for the local Virtual Chassis member.

member member-id(MX Series routers only) (Optional) Display information about alarm
conditions for the specified member of the Virtual Chassis configuration. Replace
member-id with a value of 0 or 1.
node-device name(QFabric systems only) (Optional) Display information about alarm
conditions for the Node device.

scc(TX Matrix router only) (Optional) Show information about the TX Matrix router (or
switch-card chassis).
sfc number(TX Matrix Plus router only) (Optional) Show information about the TX
Matrix Plus router (or switch-fabric chassis). Replace number with 0.

You cannot clear the alarms for chassis components. Instead, you must remedy the
cause of the alarm. When a chassis alarm is lit, it indicates that you are running the router
or switch in a manner that we do not recommend.
On routers, you can manually silence external devices connected to the alarm relay
contacts by pressing the alarm cutoff button, located on the craft interface. Silencing
the device does not remove the alarm messages from the display (if present on the
router) or extinguish the alarm LEDs. In addition, new alarms that occur after you silence
an external device reactivate the external device.
In Junos OS release 11.1 and later, alarms for fans also show the slot number of the fans
in the CLI output.
In Junos OS Release 11.2 and later, the command output on EX8200 switches shows the
detailed location (Plane/FPC/PFE) for link errors in the chassis.
In Junos OS Release 10.2 and later, an alarm is shown on T Series routers for a standby
sonic clock generator (SCG) that is offline or absent.
You may often see the following error messages, in which only the error code is shown
and no other information is provided:
Apr 12 08:04:10 send: red alarm set, device FPC 6, reason FPC 6 Major Errors - Error code:
257
365
559
To understand what CM_ALARM error codes mean, you need to first identify the structure
of the CM Alarm codes. A CM_ALARM code has the following structure:
Bits:
Error type:
1-31
Major (1)
Minor (0)
As per the above table, the LSB (bit 0) identifies the Error Type (major alarm, if the bit
is set and minor alarm if the bit is unset). The rest of the bits (1 - 31) identify the actual
error code.
Take an example of the following error code, which was logged on a T1600:
559
First, you have to convert 559 to binary; that is 1000101111. The LSB in this case is 1, which
means that this is a major alarm. After removing the LSB, you are left with 100010111,
which is equal to 279 in decimal. This is the actual error code, its meaning can be found
from the following list:
Chip Type: L Chip
Code
CMALARM_LCHIP_LOUT_DESRD_PARITY_ERR
CMALARM_LCHIP_LOUT_DESRD_UNINIT_ERR
CMALARM_LCHIP_LOUT_DESRD_ILLEGALLINK_ERR
CMALARM_LCHIP_LOUT_DESRD_ILLEGALSIZE_ERR
CMALARM_LCHIP_LOUT_HDRF_TOERR_ERR
CMALARM_LCHIP_LOUT_HDRF_PARITY_ERR
CMALARM_LCHIP_LOUT_HDRF_UCERR_ERR
CMALARM_LCHIP_LOUT_NLIF_CRCDROP_ERR
CMALARM_LCHIP_LOUT_NLIF_CRCERR_ERR
CMALARM_LCHIP_UCODE_TIMEOUT_ERR
10
CMALARM_LCHIP_LIN_SRCTL_ACCT_DROP_ERR
11
CMALARM_LCHIP_LIN_SRCTL_ACCT_ADDR_SIZE_ERR
12
366
CMALARM_LCHIP_SRAM_PARITY_ERR
13
CMALARM_LCHIP_UCODE_OVFLW_ERR
14
CMALARM_LCHIP_LOUT_HDRF_MTU_ERR
15
Chip Type: M Chip
Code
CMALARM_MCHIP_ECC_UNCORRECT_ERR
128
Chip Type: N Chip
Code
CMALARM_NCHIP_RDDMA_JBUS_TIMEOUT_ERR
256
CMALARM_NCHIP_RDDMA_FIFO_OVFLW_ERR
257
CMALARM_NCHIP_RDDMA_FIFO_UNFLW_ERR
258
CMALARM_NCHIP_RDDMA_SIZE_ERR
259
CMALARM_NCHIP_RDDMA_JBUS_CRC_ERR
260
CMALARM_NCHIP_WRDMA_PKTR_ERR
261
CMALARM_NCHIP_WRDMA_PKT_CRC_ERR
262
CMALARM_NCHIP_WRDMA_JBUS_TIMEOUT_ERR
263
CMALARM_NCHIP_WRDMA_FIFO_OVFLW_ERR
264
CMALARM_NCHIP_WRDMA_FIFO_UNFLW_ERR
265
CMALARM_NCHIP_WRDMA_PKT_LEN_ERR
266
CMALARM_NCHIP_WRDMA_JBUS_CRC_ERR
267
CMALARM_NCHIP_PKTR_DMA_AGE_ERR
268
CMALARM_NCHIP_PKTR_ICELLSIG_ERR
269
CMALARM_NCHIP_PKTR_FTTL_ERR
270
CMALARM_NCHIP_RODR_OFFSET_OVFLW_ERR
271
CMALARM_NCHIP_PKTR_TMO_CELL_ERR
272
CMALARM_NCHIP_PKTR_TMO_OUTRANGE_ERR
273
CMALARM_NCHIP_PKTR_MD_REQUEST_Q_OVFLW_ERR
274
367
CMALARM_NCHIP_PKTR_DMA_BUFFER_OVFLW_ERR
275
CMALARM_NCHIP_PKTR_GRT_OVFLW_ERR
276
CMALARM_NCHIP_FRQ_ERR
277
CMALARM_NCHIP_RODR_IN_Q_OVFLW_ERR
278
CMALARM_NCHIP_DBUF_CRC_ERR
279
Chip Type: R Chip
Code
CMALARM_RCHIP_SRAM_PARITY_ERR
512
Chip Type: R Chip
Code
CMALARM_ICHIP_WO_DESRD_ID_ERR
601
CMALARM_ICHIP_WO_DESRD_DATA_ERR
602
CMALARM_ICHIP_WO_DESRD_OFLOW_ERR
603
CMALARM_ICHIP_WO_HDRF_UCERR_ERR
604
CMALARM_ICHIP_WO_HDRF_MTUERR_ERR
605
CMALARM_ICHIP_WO_HDRF_PARITY_ERR
606
CMALARM_ICHIP_WO_HDRF_TOERR_ERR
607
CMALARM_ICHIP_WO_IP_CRC_ERR
608
CMALARM_ICHIP_WO_IP_INTER_ERR
609
CMALARM_ICHIP_WI_WAN_TIMEOUT_ERR
625
CMALARM_ICHIP_WI_FAB_TIMEOUT_ERR
626
CMALARM_ICHIP_RLDRAM_BIST_ERR
630
CMALARM_ICHIP_SDRAM_BIST_ERR
631
CMALARM_ICHIP_RLDRAM_PARITY_ERR
632
CMALARM_ICHIP_SDRAM_UNCORRECT_ERR
633
CMALARM_ICHIP_SDRAM_CORRECT_ERR
634
CMALARM_ICHIP_FUSE_DONE_ERR
635
368
According to the table above, the 279 error code corresponds to

CMALARM_NCHIP_DBUF_CRC_ERR; this means that new CRC errors were seen on the
NCHIP of this particular FPC, which is FPC as per the logs.
If you do not want to convert decimal to binary and vice-versa, you may use the following
shortcut:
For major alarms, the Actual Error Code = (Error Code - 1)/2, where Error Code is the
code that you get in the log message. For example, if you get the following log:
Apr 12 08:04:10 send: red alarm set, device FPC 6, reason FPC 6 Major Errors - Error
code: 257
Actual Error Code = (257-1)/2 = 128. Similarly, for minor alarms, Actual Error Code = (Error
Code)/2
Required Privilege
Level
Related
Documentation
view
Configuring an Alarm Entry and Its Attributes
Chassis Conditions That Trigger Alarms
show chassis alarms (Alarms Active) on page 371

show chassis alarms (No Alarms Active) on page 371
show chassis alarms (Fan Tray) on page 371
show chassis alarms (MX2020 Router) on page 371
show chassis alarms (MX2010 Router) on page 371
show chassis alarms (T4000 Router) on page 371
show chassis alarms (Unreachable Destinations Present on a T Series
Router) on page 371
show chassis alarms (FPC Offline Due to Unreachable Destinations on a T Series
Router) on page 372
show chassis alarms (SCG Absent on a T Series Router) on page 373
show chassis alarms (Alarms Active on a TX Matrix Router) on page 373
show chassis alarms (Alarms on a T4000 Router After the enhanced-mode Statement
is Enabled) on page 373
show chassis alarms (Backup Routing Engine) on page 374
show chassis alarms (Alarms Active on the QFX Series) on page 374
show chassis alarms node-device (Alarms Active on the QFabric System) on page 374
show chassis alarms (Alarms Active on the QFabric System) on page 375
show chassis alarms (Alarms Active on an EX8200 Switch) on page 375
show chassis alarms (Alarms Active on a PTX5000 Packet Transport
Switch) on page 375
show chassis alarms (Alarms Active on an ACX2000 Universal Access
Router) on page 376
Output Fields
Table 33 on page 370 lists the output fields for the show chassis alarms command. Output
369
Table 33: show chassis alarms Output Fields
370
Field Name
Field Description
Alarm time
Date and time the alarm was first recorded.
Class
Severity class for this alarm: Minor or Major.
Description
Information about the alarm.
Sample Output
show chassis alarms
(Alarms Active)

3 alarms are currently active
Alarm time
Class Description
2000-02-07 10:12:22 UTC Major fxp0: ethernet link down
2000-02-07 10:11:54 UTC Minor YELLOW ALARM - PEM 1 Removed
2000-02-07 10:11:03 UTC Minor YELLOW ALARM - Lower Fan Tray Removed
show chassis alarms

(No Alarms Active)

No alarms are currently active
show chassis alarms

(Fan Tray)

4 alarms currently active
Alarm time
Class
2010-11-11 20:27:38 UTC Major
2010-11-11 20:27:13 UTC Minor
2010-11-11 20:27:13 UTC Major
2010-11-11 20:27:13 UTC Major
Description
Side Fan Tray
Side Fan Tray
Side Fan Tray
Side Fan Tray
7
7
5
0
Failure
Overspeed
Failure
Failure
show chassis alarms

(MX2020 Router)

Alarm time Class Description
2012-10-03 12:14:59 PDT Minor Plane 0 not online
show chassis alarms

(MX2010 Router)

Alarm time
Class
2012-08-07 00:46:06 PDT Major
2012-08-06 18:24:36 PDT Minor
2012-08-06 07:41:04 PDT Minor
2012-08-04 02:42:06 PDT Minor
2012-08-03 21:14:24 PDT Minor
2012-08-03 12:26:03 PDT Minor
2012-08-03 10:40:18 PDT Minor
Description
Fan Tray 2 Failure
Redundant feed missing for
Loss of communication with

Alarm time
Class
2007-06-02 01:41:10 UTC Minor
2007-06-02 01:41:10 UTC Minor
2007-06-02 01:41:10 UTC Minor
2007-05-30 19:37:33 UTC Major
2007-05-30 19:37:29 UTC Minor
2007-05-30 19:37:13 UTC Major
2007-05-30 19:37:13 UTC Major
2007-05-30 19:37:03 UTC Major
2007-05-30 19:37:03 UTC Minor
Description
RE 0 Not Supported
CB 0 Not Supported
Mixed Master and Backup RE types
SPMB 1 not online
Front Bottom Fan Tray Absent
PEM 1 Input Failure
PEM 0 Not OK
PEM 0 Improper for Platform
Backup RE Active

Alarm time
Class
Description
show chassis alarms

(T4000 Router)
show chassis alarms

(Unreachable
PSM 6
PSM 8
PSM 5
Backup RE
PSM 4
PSM 7
371
Destinations Present
on a T Series Router)
2011-08-30
2011-08-30
2011-08-30
2011-08-30
2011-08-30
2011-08-30
2011-08-30
2011-08-30
2011-08-30
2011-08-30
show chassis alarms

(FPC Offline Due to
Unreachable

Alarm time
Class
2011-08-30 18:43:53 PDT Major
372
18:43:53
18:43:53
18:43:52
18:43:52
18:43:52
18:43:33
18:43:28
18:43:05
18:43:28
18:43:05
PDT
PDT
PDT
PDT
PDT
PDT
PDT
PDT
PDT
PDT
Major
Major
Major
Major
Minor
Minor
Minor
Minor
Minor
Major
FPC
FPC
FPC
FPC
SIB
SIB
SIB
SIB
SIB
PEM
7
5
3
2
0
4
3
2
1
1
has
has
has
has
Not
Not
Not
Not
Not
Not
unreachable
unreachable
unreachable
unreachable
Online
Online
Online
Online
Online
Ok
destinations
destinations
destinations
destinations
Description
FPC 7 offline due to unreachable destinations
Destinations on a T
Series Router)
2011-08-30
2011-08-30
2011-08-30
2011-08-30
2011-08-30
2011-08-30
2011-08-30
2011-08-30
2011-08-30
show chassis alarms

(SCG Absent on a T
Series Router)

Alarm time
Class
2011-01-23 21:42:46 PST Major
show chassis alarms

(Alarms Active on a TX
Matrix Router)

scc-re0:
-------------------------------------------------------------------------8 alarms currently active
Alarm time
Class Description
2004-08-05 18:43:53 PDT Minor LCC 0 Minor Errors
2004-08-05 18:43:53 PDT Minor SIB 3 Not Online
2004-08-05 18:43:52 PDT Major SIB 2 Absent
2004-08-05 18:43:33 PDT Major LCC 2 Major Errors
2004-08-05 18:43:28 PDT Major LCC 0 Major Errors
2004-08-05 18:43:05 PDT Minor LCC 2 Minor Errors
lcc0-re0:
Alarm time
Class Description
2004-08-05 18:43:28 PDT Major PEM 0 Not OK
lcc2-re0:
Alarm time
Class Description
2004-08-05 18:43:05 PDT Minor PEM 1 Absent
show chassis alarms

(Alarms on a T4000
Router After the
On T4000 routers, when you include the enhanced-mode statement at the [edit chassis
network-services] hierarchy level and reboot the system, only the T4000 Type 5 FPCs
present on the router are online while the remaining FPCs are offline, and FPC
misconfiguration alarms are generated. The show chassis alarm command output displays
18:43:53
18:43:52
18:43:52
18:43:52
18:43:33
18:43:28
18:43:05
18:43:28
18:43:05
PDT
PDT
PDT
PDT
PDT
PDT
PDT
PDT
PDT
Major
Major
Major
Minor
Minor
Minor
Minor
Minor
Major
FPC
FPC
FPC
SIB
SIB
SIB
SIB
SIB
PEM
5
3
2
0
4
3
2
1
1
offline due to unreachable destinations

Not Online
Not Online
Not Online
Not Online
Not Online
Not Ok
Description
SCG 0 NO EXT CLK MEAS-BKUP SCG ABS
373
enhanced-mode
Statement is Enabled)
FPC misconfiguration (FPC fpc-slot misconfig) as the reason for the generation of the
alarms.
Alarm time
Class
2011-10-22 10:10:47 PDT Major
2011-10-22 10:10:46 PDT Major
Description
FPC 1 misconfig
FPC 0 misconfig
show chassis alarms

(Backup Routing
Engine)

2 alarms are currently active
Alarm time
Class
2005-04-07 10:12:22 PDT Minor
2005-04-07 10:11:54 PDT Major
show chassis alarms

(Alarms Active on the
QFX Series)
user@switch> show chassis alarms

Alarm time
Class Description
2012-03-05 2:10:24 UTC Major FPC 0 PEM 0 Airflow not matching Chassis Airflow
show chassis alarms

node-device (Alarms
user@switch> show chassis alarms node-device ED3691

node-device ED3694
374
Description
Host 1 Boot from alternate media
Host 1 compact-flash missing in Boot List
Active on the QFabric

System)
Alarm time
2011-08-24 16:04:15 UTC
2011-08-24 16:04:14 UTC
2011-08-24 14:21:14 UTC
show chassis alarms

(Alarms Active on the
QFabric System)

IC-A0001:
Alarm time
Class Description
2011-08-24 16:04:15 UTC Minor Backup RE Active
Class
Major
Major
Major
Description
ED3694:fte-0/1/2: Link down
ED3694:fte-0/1/0: Link down
ED3694 PEM 0 is not supported/powered
ED3694:
Alarm time
Class Description
2011-08-24 16:04:15 UTC Major ED3694:fte-0/1/2: Link down
2011-08-24 16:04:14 UTC Major ED3694:fte-0/1/0: Link down
2011-08-24 14:21:14 UTC Major ED3694 PEM 0 is not supported/powered
SNG-0:
-------------------------------------------------------------------------NW-NG-0:
Alarm time
Class Description
2011-08-24 15:49:27 UTC Major ED3691 PEM 0 is not supported/powered
show chassis alarms

(Alarms Active on an
EX8200 Switch)
show chassis alarms

(Alarms Active on a

Alarm time
Class Description
2010-12-02 19:15:22 UTC Major Fan Tray Failure
2010-12-02 19:15:22 UTC Major Fan Tray Failure
2010-12-02 19:15:14 UTC Minor Check CB 0 Fabric Chip 1 on Plane/FPC/PFE: 1/5/0,
1/5/1, 1/5/2, 1/5/3, 1/7/0, 1/7/1, 1/7/2, 1/7/3, 2/5/0, 2/5/1, ...
2010-12-02 19:15:14 UTC Minor Check CB 0 Fabric Chip 0 on Plane/FPC/PFE: 1/5/0,
1/5/1, 1/5/2, 1/5/3, 1/7/0, 1/7/1, 1/7/2, 1/7/3, 2/5/0, 2/5/1, ...
2010-12-02 19:14:18 UTC Major PSU 1 Output Failure
2010-12-02 19:14:18 UTC Minor Loss of communication with Backup RE
375
PTX5000 Packet
Transport Switch)
Alarm time
2011-07-12
2011-07-12
2011-07-12
2011-07-12
2011-07-12
2011-07-12
2011-07-12
2011-07-12
2011-07-12
show chassis alarms

(Alarms Active on an
ACX2000 Universal
Access Router)

Alarm time
Class
2012-05-22 11:19:09 UTC Major
2012-05-22 11:19:09 UTC Major
2012-05-22 11:19:09 UTC Major
2012-05-22 11:19:09 UTC Major
2012-05-22 11:19:09 UTC Major
2012-05-22 11:19:09 UTC Major
2012-05-22 11:19:09 UTC Major
376
16:22:05
16:22:05
16:21:57
16:21:57
15:56:06
15:56:06
15:56:06
15:28:20
15:19:14
PDT
PDT
PDT
PDT
PDT
PDT
PDT
PDT
PDT
Class
Minor
Major
Minor
Major
Major
Minor
Major
Major
Minor
Description
No Redundant Power for Rear Chassis
PDU 0 PSM 1 Not OK
No Redundant Power for Fan 0-2
PDU 0 PSM 0 Not OK
PDU 1 PSM 2 Not OK
No Redundant Power for FPC 0-7
PDU 0 PSM 3 Not OK
PDU 0 PSM 2 Not OK
Backup RE Active
Description
xe-0/3/1: Link
xe-0/3/0: Link
ge-0/1/7: Link
ge-0/1/6: Link
ge-0/1/3: Link
ge-0/1/2: Link
ge-0/1/1: Link
down
down
down
down
down
down
down
show chassis craft-interface

Syntax
Syntax (MX Series

Routers)

<all-members>
<local>
<member member-id>
Syntax (MX2010
Universal Edge
Routers)
Syntax (MX2020
Universal Edge
Routers)
Syntax (TX Matrix

Routers)

<lcc number | scc>

Routers)

Syntax (ACX Series

Universal Access
Routers)
Release Information

sfc option for the TX Matrix Plus router introduced in Junos OS Release 9.6.
Command introduced in Junos OS Release 12.2 for ACX Series Universal Access Routers.
Description
For routers or switches that have a display on the craft interface, show the messages
that are currently displayed. On all routers except for the M20 router, you must enter this
command on the master Routing Engine.
Options
none(TX Matrix, TX Matrix Plus routers, MX2020 and MX2010 routers, and ACX Series
routers only) On a TX Matrix router, show messages that are currently displayed on
the craft interface on the TX Matrix router and its attached T640 routers. On a TX
Matrix Plus router, show messages that are currently displayed on the craft interface
on the TX Matrix Plus router and its attached T1600 routers.
all-members(MX Series routers only) (Optional) Display information currently on the
craft interface for all members of the Virtual Chassis configuration.

lcc number(TX Matrix and TX Matrix Plus routers only) (Optional) On a TX Matrix router,
show messages that are currently displayed on the craft interface for a specified
T640 router (or line-card chassis) that is connected to the TX Matrix router. On a
TX Matrix Plus router, show messages that are currently displayed on the craft
377
interface for a specified T1600 router (or line-card chassis) that is connected to the
TX Matrix Plus router. Replace number with a value from 0 through 3.
local(MX Series routers only) (Optional) Display information currently on the craft
interface for the local Virtual Chassis member.

member member-id(MX Series routers only) (Optional) Display information currently
on the craft interface for the specified member of the Virtual Chassis configuration.
For an MX Series Virtual Chassis, replace member-id with a value of 0 or 1.
scc(TX Matrix router only) (Optional) Show messages that are currently displayed on
the craft interface for the TX Matrix router (or switch-card chassis).
sfc number(TX Matrix Plus router only) (Optional) Show messages that are currently
displayed on the craft interface for the TX Matrix Plus router (or switch-fabric chassis).
Replace number with 0.
Required Privilege
Level
view
Related
Documentation
clear chassis display message
set chassis display message
show chassis craft-interface (M20 Router) on page 380

show chassis craft-interface (MX2020 Router) on page 381
show chassis craft-interface (MX2010 Router) on page 382
show chassis craft-interface (T4000 Router) on page 383
show chassis craft-interface (TX Matrix Routing Matrix) on page 384
show chassis craft-interface (TX Matrix Plus Routing Matrix) on page 386
show chassis craft-interface (ACX2000 Universal Access Router) on page 388
Output Fields
Table 34 on page 378 lists the output fields for the show chassis craft-interface command.
Table 34: show chassis craft-interface Output Fields

Field Name
Field Description
LCD screen
Contents of the Front Panel Module display:
or
FPM Display Contents
router-nameName of the router.
UpHow long the router has been operational, in days, hours, minutes, and seconds.
messageInformation about the router traffic load, the power supply status, the fan status, and
the temperature status. The display of this information changes every 2 seconds. If a text message
has been created with the set chassis display command, this message appears on all four lines of
the craft interface display. The display alternates between the text message and the standard
system status messages every 2 seconds.
378
Table 34: show chassis craft-interface Output Fields (continued)

Field Name
Field Description
Front Panel System

LEDs
(MX2010 and MX2020 Routers) Status of the Front Panel System LEDs. A dot (.) indicates the LED
is not lit. An asterisk (*) indicates the LED is lit.
Front Panel Alarm

Indicators
(MX2010 and MX2020 Routers) Status of the Front Panel Alarm indicators. A dot (.) indicates the
relay is off. An asterisk (*) indicates the relay is active.
Input Relay
Status of the configured input relay ports0 through 3. The mode is normally open or closed. The
status is clear or raised.
Output Relay
Status of the configured output ports0 or 1. The mode is normally open or closed. The status is clear
or raised.
Front Panel FPC LEDs
(MX2010 and MX2020 Routers) Status of the Front Panel Flexible PIC Concentrator (FPC) LEDs. A
dot (.) indicates the LED is not lit. An asterisk (*) indicates the LED is lit. On MX2010 routers, there are
10 (0-9) FPCs LEDs. On MX2020 routers, there are 20 (0-9 and 10-19) FPCs LEDs.
CB LEDs
Status of the Control Board (CB) LEDs. A dot (.) indicates the LED is not lit. An asterisk (*) indicates
the LED is lit.
PS LEDs
(MX2010 and MX2020 Routers) Status of the Power Supply (PS) LEDs. A dot (.) indicates the LED
is not lit. An asterisk (*) indicates the LED is lit. On MX2010 routers, there are 9 (0-8) PS LEDs. On
MX2020 routers, there are 18 (0-8 and 9-17) PS LEDs.
FAN Tray LEDs
(MX2010 and MX2020 Routers) Status of the Fan Tray LEDs. A dot (.) indicates the LED is not lit. An
asterisk (*) indicates the LED is lit.
Front Panel SFB LEDs
(MX2010 and MX2020 Routers) Status of the Front Panel Switch Fabric Boards (SFB) LEDs. A dot
(.) indicates the LED is not lit. An asterisk (*) indicates the LED is lit.
Front Panel Chassis Info
(MX2010 and MX2020 Routers) Information about the chassis such as the chassis number and role.
User can set the chassis number in multi-chassis configurations.
MCS and SFM LEDs
Status of the Miscellaneous Control Subsystem (MCS) and Switching and Forwarding Module (SFM)
LEDs. A dot (.) indicates the LED is not lit. An asterisk (*) indicates the LED is lit. When neither a dot
nor an asterisk is displayed, there is no board in that slot.
SIB LEDs
Status of the Switch Interface Board (SIB) LEDs. A dot (.) indicates the LED is not lit. An asterisk (*)
indicates the LED is lit.
SCG LEDs
Status of the SONET Clock Generator (SCG) LEDs. A dot (.) indicates the LED is not lit. An asterisk
(*) indicates the LED is lit.
379
Sample Output
show chassis
craft-interface (M20
Router)
user@host> show chassis craft-interface

Red alarm:
LED off, relay off
Yellow alarm: LED on, relay on
Host OK LED:
On
Host fail LED: Off
FPCs
0 1 2 3
------------------Green . * *.
Red
....
LCD screen:
+--------------------+
|host
|
|1 Alarm active
|
|Y: FERF
|
|
|
+--------------------+
show chassis
Router)

Front Panel LCD Display: enabled
Red alarm:
LED off, relay off
Yellow alarm: LED off, relay off
Host OK LED:
On
Host Fail LED: Off
NICs
0 1 2 3 4 5 6 7
------------------------------Green
*. *. *. *.
Red
........
LCD Screen:
+--------------------+
|host
|
|Up: 27+18:52:37
|
|
|
|52.649kpps Load
|
+--------------------+
show chassis
Router)

Front Panel System LEDs:
Routing Engine
0
1
-------------------------OK
*
.
Fail
.
.
Master
*
.
Front Panel Alarm Indicators:
----------------------------Red LED
*
Yellow LED
.
Major relay *
Minor relay .
Front Panel FPC LEDs:
FPC
0
1
2
3
4
5
---------------------------Red
.
.
.
.
.
.
Green .
*
.
*
*
*
380
CB LEDs:
CB
0
1
-------------Amber .
.
Green *
*
PS LEDs:
PS
0
1
-----------------------Red
.
.
Green *
*
FEB LEDs:
FEB 0
1
2
3
4
5
-----------------------------Red
.
.
.
.
.
.
Green .
.
.
*
*
*
Active .
.
.
*
*
*
show chassis
Router)

FPM Display contents:
+--------------------+
|hosts
|
|Up: 1+16:46
|
|
|
|Fans OK
|
+--------------------+
Host
0
1
-----------------------OK
.
*
Fail
. .
Master .
*
----------------------------Red LED
.
Yellow LED .
Major relay.
Minor relay.
FPC
0
1
2
3
4
5
6
7
-----------------------------------Red . . . . . . . .
Green *
* . . . . . .
MCS and SFM LEDs:
MCS
0
1
SFM
0
1
2
3
-------------------------------------Amber
.
. .
Green
.
. .
Blue
*
*
*
show chassis
craft-interface
(MX2020 Router)
user@host > show chassis craft-interface

Routing Engine 0 1
-------------------------OK * *
381
Fail . .
Master * .
----------------------------Red LED .
Yellow LED .
Major relay .
Minor relay .
FPC 0 1 2 3 4 5 6 7 8 9
----------------------------------------------------Red . . . . . . . . . .
Green * * * * * * * * * *
FPC 10 11 12 13 14 15 16 17 18 19
-----------------------------------------------------Red . . . . . . . . . .
Green * * * * * * * * * *
CB LEDs:
CB 0 1
-----------Amber . .
Green * *
PS LEDs:
PS 0 1 2 3 4 5 6 7 8
------------------------------------------------Red . . . . . . . . .
Green * * * * * . . * *
PS LEDs:
PS 9 10 11 12 13 14 15 16 17
------------------------------------------------Red . . . . . . . . .
Green * * * * * * * * *
Fan Tray LEDs:
FT 0 1 2 3
-------------------Red . . . .
Green * * * *
Front Panel SFB LEDs:
SFB 0 1 2 3 4 5 6 7
-----------------------------------Red . . . . . . . .
Green * * * * * * * *
Front Panel Chassis Info:
Chassis Number 0x57
Chassis Role M
show chassis
craft-interface
(MX2010 Router)
user@host > show chassis craft-interface

Routing Engine
0
1
-------------------------OK
*
.
Fail
.
*
Master
*
.
----------------------------Red LED
.
Yellow LED
*
Major relay .
Minor relay *
382

FPC
0
1
2
3
4
5
6
7
8
9
----------------------------------------------------Red
.
.
.
.
.
.
.
.
.
.
Green *
*
.
.
.
.
.
.
*
*
CB LEDs:
CB
0
1
-----------Amber .
.
Green *
*
PS LEDs:
PS
0
1
2
3
4
5
6
7
8
------------------------------------------------Red
.
.
.
.
.
.
.
.
.
Green
.
.
.
.
*
*
*
*
*
Fan Tray LEDs:
FT
0
1
2
3
-------------------Red
.
.
.
.
Green *
*
*
*
Front Panel SFB LEDs:
SFB
0
1
2
3
4
5
6
7
-----------------------------------Red
.
.
.
.
.
.
.
.
Green *
*
*
*
*
*
*
*
Front Panel Chassis Info:
Chassis Number
0x0
Chassis Role
S
show chassis
craft-interface (T4000
Router)

+--------------------+
|stymphalian
|
|2 Alarms active
|
|R: Front Top Fan Tra|
|Y: PEM 1 Absent
|
+--------------------|
Routing Engine
0
1
-------------------------OK
*
*
Fail
.
.
Master
*
.
----------------------------Red LED
*
Yellow LED
*
Major relay *
Minor relay *
FPC
0
1
2
3
383
-----------------------------------Red
.
.
.
.
.
.
.
.
Green *
.
.
*
.
*
*
.
CB LEDs:
CB
0
1
-------------Amber .
.
Green *
*
Blue
*
.
SCG LEDs:
SCG 0
1
-------------Amber .
.
Green *
*
Blue
*
.
SIB LEDs:
SIB 0
1
2
3
4
-------------------------Red
.
.
.
.
.
Green *
*
*
*
*
show chassis
craft-interface (TX
Matrix Routing Matrix)

scc-re0:
-------------------------------------------------------------------------FPM Display contents:
+--------------------+
|bradley
|
|8 Alarms active
|
|R: SIB 2 Absent
|
|R: SIB 1 Absent
|
+--------------------|
Routing Engine
0
1
-------------------------OK
* .
Fail
. .
Master
* .
----------------------------Red LED
*
Yellow LED
*
Major relay *
Minor relay *
CB LEDs:
CB
0
1
-------------Amber. .
Green * .
Blue
* .
SIB LEDs:
SIB 0
1
2
3
4
-------------------------Fail . . . . .
OK
. . . .
*
384
Active . . . .
lcc0-re0:
+--------------------+
|hybrid
|
|5 Alarms active
|
|R: SIB 2 Absent
|
|R: SIB 1 Absent
|
+--------------------|
Routing Engine
0
1
-------------------------OK
* .
Fail
. .
Master
* .
----------------------------Red LED
*
Yellow LED
*
Major relay *
Minor relay *
FPC
0
1
2
3
4
5
6
7
-----------------------------------Red . . . . . . . .
Green.
*
* . . . . .
CB LEDs:
CB
0
1
-------------Amber. .
Green * .
Blue
* .
SCG LEDs:
SCG 0
1
-------------Amber. .
Green * .
Blue
* .
SIB LEDs:
SIB 0
1
2
3
4
-------------------------Red . . . . .
Green. . . .
*
lcc2-re0:
+--------------------+
|prius
|
|5 Alarms active
|
|R: SIB 2 Absent
|
|R: SIB 1 Absent
|
+--------------------|
385

Routing Engine
0
1
-------------------------OK
* .
Fail
. .
Master
* .
----------------------------Red LED
*
Yellow LED
*
Major relay *
Minor relay *
FPC
0
1
2
3
4
5
6
7
-----------------------------------Red . . . . . . . .
Green *
*
* . . . . .
CB LEDs:
CB
0
1
-------------Amber. .
Green * .
Blue
* .
SCG LEDs:
SCG 0
1
-------------Amber. .
Green * .
Blue
* .
SIB LEDs:
SIB 0
1
2
3
4
-------------------------Red . . . . .
Green. . . .
*
show chassis
craft-interface (TX
386

sfc0-re0:
--------------------------------------------------------------------------
Matrix Plus
Routing Matrix)
FPM Display Contents:

+--------------------+
|finalfive
|
|22 Alarms active
|
|R: LCC 0 Major Error|
|R: SIB F2S 4/6 Absent|
+--------------------+
Routing Engine
0
1
-------------------------OK
*
*
Fail
.
.
Master
*
.
----------------------------Red LED
*
Yellow LED
*
Major relay *
Minor relay *
Front Panel F13 SIB LEDs:
SIB
0
1
2
3
4
5
6
7
8
9 10 11 12 13 14 15
-------------------------------------------------------------------Fail
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
OK
*
*
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Active *
*
.
.
.
.
.
.
.
.
.
.
.
.
.
.
PS LEDs:
PS
0
1
-----------Red
.
.
Green *
.
Fan Tray LEDs:
FT
0
1
2
3
4
5
---------------------------Red
.
.
.
.
.
.
Green *
*
*
*
*
*
CB LEDs:
CB
0
1
-------------Amber .
.
Green *
*
Blue
*
.
+--------------------+
|tigh
|
|5 Alarms active
|
|R: SIB-L - Fan Rev M|
|Y: Check SIB 0
|
+--------------------|
Routing Engine
0
1
-------------------------OK
*
*
Fail
.
.
Master
*
.
387

----------------------------Red LED
*
Yellow LED
*
Major relay *
Minor relay *
FPC
0
1
2
3
4
5
6
7
-----------------------------------Red
.
.
.
.
.
.
.
.
Green *
*
.
.
.
.
.
.
CB LEDs:
CB
0
1
-------------Amber .
.
Green *
*
Blue
*
.
SCG LEDs:
SCG 0
1
-------------Amber .
.
Green *
*
Blue
*
.
SIB LEDs:
SIB 0
1
2
3
4
-------------------------Red
.
.
.
.
.
Green *
.
.
.
.
show chassis
craft-interface
388

Routing Engine
(ACX2000 Universal
Access Router)
-----------------OK
*
Fail
.
----------------------------Red LED
.
Yellow LED
.
Major relay .
Minor relay .
Input relay:
-----------Port
Mode
0
Open
1
Open
2
Open
3
Open
Status
Clear
Clear
Clear
Clear
Output relay:
------------Port
Mode
0
Open
1
Open
Status
Clear
Clear
PS Status:
PS
0
1
--------------Red
.
.
Green *
*
389
show chassis environment

Syntax
Syntax (T320, T640,
T1600, and T4000
Routers)

<cb cb-slot-number>
<fpc fpc-slot-number>
<fpm>
<pem pem-slot-number>
<routing-engine re-slot-number>
<scg scg-slot-number>
<sib sib-slot-number>
Syntax (TX Matrix

Routers)

<lcc number | scc>

Routers)

Syntax (MX Series

Routers)

<all-members>
<local>
<member member-id>
Syntax (MX2020 3D
Universal Edge
Routers)

<adc adc-slot-number>
<cb cb-slot-number>
<fpm>
<monitored>
<psm psm-slot-number>
<sfb sfb-slot-number>
Syntax (MX2010 3D
Universal Edge
Routers)

<adc adc-slot-number>
<cb cb-slot-number>
<fpm>
<monitored>
<psm psm-slot-number>
<sfb sfb-slot-number>
Syntax (EX Series

Switch)

<all-members>
<cb cb-slot-number>
<local>
<member member-id>
390
Syntax (EX Series

Switch)
Syntax (QFX Series)

<all-members>
<cb cb-slot-number>
<local>
<member member-id>
<power-supply-unit psu-slot-number>
<routing-engine slot-number>
<cb slot-number <interconnect-device name>>
<fpc slot-number <interconnect-device name>>
<interconnect-device name <slot-number>
<node-device name>
<pem slot-number (interconnect-device name slot-number) | (node-device name)>
<routing-engine name <interconnect-device name slot-number>>
Syntax (PTX Series

Packet Transport
Switches)

<cb cb-slot-number>
<ccg ccg-slot-number >
<fpm>
<monitored>
<pdu pdu-slot-number>
<sib sib-slot-number>
Syntax (ACX Series

Universal Access
Routers)

<cb cb-slot-number>
<pem pem-slot-number>
Release Information
Description

sfc option introduced for the TX Matrix Plus router in Junos OS Release 9.6.
Command introduced in Junos OS Release 11.1 for QFX Series.
Command introduced in Junos OS Release 12.1 for PTX Series Packet Transport Switches.
monitored option added in Junos OS Release 12.1 for PTX Series Packet Transport
Switches.
Command introduced in Junos OS Release 12.1 for T4000 Core Routers.
pem option introduced in Junos OS Release 12.3 for ACX4000 Universal Access Routers.
Display environmental information about the router or switch chassis, including the
temperature and information about the fans, power supplies, and Routing Engine.
In addition on ACX4000 routers, display temperature information about the different
channels of a Modular Interface Card (MIC). The number of channels displayed depends
on the type of MIC installed.
391
Options
noneDisplay environmental information about the router or switch chassis. On a TX
Matrix router, display environmental information about the TX Matrix router and its
attached T640 routers. On a TX Matrix Plus router, display environmental information
about the TX Matrix Plus router and its attached T1600 routers.
all-members(MX Series routers and EX Series switches only) (Optional) Display chassis
environmental information for all the members of the Virtual Chassis configuration.
adc adc-slot-number(MX2020 and MX2010 routers only) (Optional) Display chassis
environmental information for the adapter cards. For MX2020 routers, replace
adc-slot-number with a value from 0 through 19. For MX2010 routers, replace
adc-slot-number with a value from 0 through 9.
cb cb-slot-number(ACX Series Universal Access Routers, EX Series switches, M120,
M320, and M40e routers, MX Series routers, MX2020 routers, MX2010 routers, PTX
Series Packet Transport Switches, QFX Series, and T Series routers only) (Optional)
Display chassis environmental information for the Control Board. On devices other
than EX Series switches, replace cb-slot with 0 or 1. For the EX Series switches, see
EX Series Switches Hardware and CLI Terminology Mapping for information on CB
slot numbering.
cb interconnect-device name(QFabric systems only) (Optional) Display chassis
environmental information for the Control Board on an Interconnect device.

ccg ccg-slot-number(PTX Series only) (Optional) Display chassis environmental
information for the Centralized Clock Generator. Replace cb-slot with a value of 0
or 1.
fpc fpc-slot(EX Series switches, M120, M320, and M40e routers, MX Series routers,
MX2010 routers, MX2020 routers, PTX Series Packet Transport Switches, QFX Series,
QFX3500 switches, QFabric systems, and T Series routers) (Optional) Display chassis
environmental information for a specified Flexible PIC Concentrator. For MX2010
routers, replace fpc-slot with a value from 0 through 9. For MX2020 routers, replace
fpc-slot with a value from 0 through 19. For information about FPC numbering, see
show chassis environment fpc. On a QFabric system, display chassis environmental
information for a specified Flexible PIC Concentrator on an Interconnect device. On
an EX Series switch, display chassis environmental information for a specified Flexible
PIC Concentrator; see EX Series Switches Hardware and CLI Terminology Mapping
for information on FPC numbering.
fpm(M120, M320, and M40e routers, MX2010 routers, MX2020 routers, PTX Series,
Packet Transport Switches, and T Series routers only) (Optional) Display chassis
environmental information for the craft interface (FPM).
interconnect-device name(QFabric systems only) (Optional) Display chassis
environmental information for the Interconnect device.

monitored(MX2020 routers and PTX Series Packet Transport Switches only) (Optional)
Display chassis environmental information for monitored temperatures only.

Temperatures that are not included in temperature alarm computations are not
displayed.
392
display chassis environmental information for a specified T640 router (or line-card
chassis) that is connected to the TX Matrix router. On a TX Matrix Plus router, display
chassis environmental information for a specified T1600 router (or line-card chassis)
that is connected to the TX Matrix Plus router. Replace number with a value from
0 through 3.
local(MX Series routers and EX Series switches) (Optional) Display chassis
environmental information for the local Virtual Chassis member.

member member-id(MX Series routers and EX Series switches only) (Optional) Display
chassis environmental information for the specified member of the Virtual Chassis
configuration. On MX Series routers, replace member-id with a value of 0 or 1. For EX
Series switches, see member for member ID values.
node-device name(QFabric systems only) (Optional) Display chassis environmental
information for the Node device.

pdu pdu-slot-number(PTX Series only) (Optional) Display chassis environmental
information for the specified power distribution unit.

pem(QFX3500 switches and QFabric systems only) (Optional) Display chassis
environmental information for the Power Entry Module on the specified Interconnect
device or Node device.
pem pem-slot-number(ACX Series Universal Access Routers, M120, M320, and M40e
routers, MX Series routers, QFX Series, and T Series routers only) (Optional) Display
chassis environmental information for the Power Entry Module on the specified
Power Entry Module. For information about the options, see show chassis environment
pem.
psm psm-slot-number(MX2020 and MX2010 routers only) (Optional) Display chassis
environmental information for the power supply module. For MX2020 routers, replace
psm-slot-number with a value from 0 through 17. For MX2010 routers, replace
psm-slot-number with a value from 0 through 8.
psu psu-slot-number(EX Series switches only) (Optional) Display chassis environmental
information for a specified power supply. See EX Series Switches Hardware and CLI
Terminology Mapping for detailed information.
routing-engine(QFX3500 switches and QFabric systems only) (Optional) Display
chassis environmental information for the Routing Engine on the specified

Interconnect device.
routing-engine re-slot-number(Optional) Display chassis environmental information
for the specified Routing Engine. For information about the options, see show chassis
environment routing-engine.
scg(T Series routers only) (Optional) Display chassis environmental information about
the SONET Clock Generator.
393
scc(TX Matrix routers only) (Optional) Display chassis environmental information
about the TX Matrix router (or switch-card chassis).

sfb sfb-slot-number(MX2020 and MX2010 routers only) (Optional) Display chassis
environmental information for the power supply module. Replace sfb-slot-number

with a value from 0 through 7.
sfc number(TX Matrix Plus routers only) (Optional) Display chassis environmental
information about the TX Matrix Plus router (or switch-fabric chassis). Replace
number with 0.
sib sib-slot-number(M320 routers, PTX Series Packet Transport Switches, and T Series
routers only) (Optional) Display chassis environmental information about the

specified switch interface board. For information about the options, see show chassis
environment sib.
Required Privilege
Level
Related
Documentation
394
view
show chassis environment adc
show chassis environment cb
show chassis environment ccg
show chassis environment cip
show chassis environment fpc
show chassis environment fpm
show chassis environment mcs
show chassis environment monitored
show chassis environment pcg
show chassis environment pdu
show chassis environment pem
show chassis environment psm
show chassis environment psu
show chassis environment routing-engine
show chassis environment scg
show chassis environment sfb
show chassis environment sib
show chassis environment (J2300 Router) on page 398

show chassis environment (J4300 or J6300 Router) on page 398
show chassis environment (M5 Router) on page 398
show chassis environment (M7i Router) on page 398
show chassis environment (M10i Router) on page 399

show chassis environment (M40e Router) on page 400
show chassis environment (MX240 Router) on page 403
show chassis environment (MX240 Router with Enhanced MX SCB) on page 403
show chassis environment (T320 Router) on page 425
show chassis environment (TX Matrix Router) on page 428
show chassis environment (TX Matrix Plus Router) on page 430
show chassis environment (EX4200 Standalone Switch) on page 433
show chassis environment (EX8216 Switch) on page 433
show chassis environment (QFX Series) on page 433
show chassis environment interconnect-device (QFabric System) on page 434
show chassis environment node-device (QFabric System) on page 436
show chassis environment pem node-device (QFabric System) on page 437
show chassis environment (PTX5000 Packet Transport Switch) on page 437
show chassis environment (ACX2000 Universal Access Router) on page 440
show chassis environment (ACX4000 Universal Access Router) on page 440
Output Fields
Table 35 on page 396 lists the output fields for the show chassis environment command.
395
Table 35: show chassis environment Output Fields

Field Name
Field Description
Class
Information about the category or class of chassis component:
Power: Power information:
(M5, M10, M20, and M40 routers and EX Series switches only) Power supply status: OK, Testing,
(during initial power-on), Failed, or Absent.
(M7i, M10i, M40e, M120, M160, M320, and T Series routers and EX Series switches only) Power
Entry Modules status: OK, Testing, (during initial power-on), Check, Failed, or Absent.
(PTX Series only) Power information is reported in PDU or PSM combinations. The status is: OK,
Testing, (during initial power-on), Check, Failed, or Absent.
Temp: Temperature of air flowing through the chassis in degrees Celsius (C) and Fahrenheit (F).
On PTX Series Packet Transport Switches and MX2010 and MX2020 Routers, multiple cooling
zones are supported. FRU temperatures in each zone are coordinated with the fan speed of fan
trays in those zones.
Pic: On ACX4000 Routers, multiple temperature channels on a MIC. The status is: OK and the
Measurement is in degrees Celsius (C) and Fahrenheit (F).
Fan: Fan status: OK, Testing (during initial power-on), Failed, or Absent.
On PTX Series Packet Transport Switches and MX2010 and MX2020 Routers, multiple fan trays
are supported. Fan status is reported in Fan Tray or Fan combinations. Measurement indicates
actual fan RPM (PTX and MX2010 and MX2020 Routers only).
Misc: Information about other components of the chassis.
On some routers, this field indicates the status of one or more additional components.
On the M40e, M160, and M320 router, Misc includes CIP (Connector Interface Panel). OK indicates
that the CIP is present. Absent indicates that the CIP is not present.
On T Series routers, Misc includes CIP and SPMB (Switch Processor Mezzanine Board). OK
indicates that the CIP or SPMB is present. Absent indicates that the CIP or SPMB is not present.
On PTX Series Packet Transport Switches, Misc includes the SPMB (Switch Processor Mezzanine
Board). The SPMB is located on the control boards. OK indicates that the control board is present.
Absent indicates that the control board is not present.
Item
(MX2010 and MX2020 Routers) Information about the chassis component: Routing Engines, Controls
Boards (CBs), Switch Fabric Boards (SFBs), PICs, Flexible PIC Concentrators (FPCs), and Adapter
Cards (ADCs).
Status
(MX2010 and MX2020 Routers) Status of the specified chassis component. For example, if the Class
is Fan, the fan status can be:
OK: The fans are operational.
Testing: The fans are being tested during initial power-on.
Failed: The fans have failed or the fans are not spinning.
Absent: The fan tray is not installed.
If the Class is Power, the power supply status can be:
396
OK: The power component is operational.
Testing: The power component is being tested during initial power-on.
Check: There is insufficient power---that is, fewer than the minimum required feeds are connected.
Failed: The inputs leads have failed.
Absent: The power component is not installed.
Table 35: show chassis environment Output Fields (continued)

Field Name
Field Description
Measurement
(MX2010 and MX2020 Routers) Dependant on the Class. For example, if the Class is Temp, indicates
the temperature in degree Celsius and degrees Fahrenheit. If the Class is Fan, indicates actual fan
RPM.
397
Sample Output
show chassis
environment (J2300
Router)
user@host> show chassis environment

Class Item
Status
Temp Routing Engine
OK
Fan
Fan
OK
show chassis
environment (J4300 or
J6300 Router)

Class Item
Status
Temp Routing Engine
OK
Fan
Fan 0
OK
Fan 1
OK
show chassis
environment (M5
Router)

Class Item
Status
Power Power Supply A
OK
Power Supply B
Absent
Temp FPC 0
OK
FEB
OK
PS Intake
OK
PS Exhaust
OK
Routing Engine
OK
Fans Left Fan 1
OK
Left Fan 2
OK
Left Fan 3
OK
Left Fan 4
OK
Misc Craft Interface
OK
show chassis
environment (M7i
Router)
show chassis
environment (M10
Router)
398

Class Item
Status
Power Power Supply 0
OK
Power Supply 1
Absent
Temp Intake
OK
FPC 0
OK
Power Supplies
OK
CFEB Intake
OK
CFEB Exhaust
OK
Routing Engine
OK
Fans Fan 1
OK
Fan 2
OK
Fan 3
OK
Fan 4
OK

Class Item
Status
OK
Power Supply B
Failed
Temp FPC 0
OK
FPC 1
OK
FEB
OK
PS Intake
OK
PS Exhaust
OK
Routing Engine
OK
Fans Left Fan 1
OK
Measurement
40 degrees C / 104 degrees F
Measurement
Measurement
30 degrees C / 86 degrees
Spinning at normal speed
F
F
F
F
F
Measurement
F
F
F
F
F
F
Measurement
F
F
F
F
F
F
Misc
show chassis
environment (M10i
Router)
show chassis
environment (M20
Router)
Left Fan 2
Left Fan 3
Left Fan 4
Craft Interface
OK
OK
OK
OK

Class Item
Status
Power Power Supply 0
OK
Power Supply 1
OK
Power Supply 2
Absent
Power Supply 3
Absent
Temp Intake
OK
FPC 0
OK
FPC 1
OK
Lower Power Supplies
OK
Upper Power Supplies
OK
CFEB Intake
OK
CFEB Exhaust
OK
Routing Engine 0
OK
Routing Engine 1
OK
Fans Fan Tray 0 Fan 1
OK
Fan Tray 0 Fan 2
OK
Fan Tray 0 Fan 3
OK
Fan Tray 0 Fan 4
OK
Fan Tray 0 Fan 5
OK
Fan Tray 0 Fan 6
OK
Fan Tray 0 Fan 7
OK
Fan Tray 0 Fan 8
OK
Fan Tray 1 Fan 1
Absent
Fan Tray 1 Fan 2
Absent
Fan Tray 1 Fan 3
Absent
Fan Tray 1 Fan 4
Absent
Fan Tray 1 Fan 5
Absent
Fan Tray 1 Fan 6
Absent
Fan Tray 1 Fan 7
Absent
Fan Tray 1 Fan 8
Absent

Class Item
Status
OK
Power Supply B
Absent
Temp FPC 0
OK
FPC 1
OK
Power Supply A
OK
Power Supply B
Absent
SSB 0
OK
Backplane
OK
Routing Engine 0
OK
Routing Engine 1
Testing
Fans Rear Fan
OK
Front Upper Fan
OK
Front Middle Fan
OK
Front Bottom Fan
OK
OK

Measurement
F
F
F
F
F
F
F
F
F
Measurement
Spinning
Spinning
Spinning
Spinning
at
at
at
at
normal
normal
normal
normal
speed
speed
speed
speed
399
show chassis
environment (M40
Router)
show chassis
environment (M40e
Router)
show chassis
environment (M120
Router)
400
Class Item
Power Supply B
Temp FPC 3
FPC 6
SCB
Backplane @ A1
Backplane @ A2
Routing Engine
Fans Top Impeller
Bottom impeller
Rear Left Fan
Rear Center Fan
Rear Right Fan
Status
OK
Absent
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK

Class Item
Status
Power PEM 0
OK
PEM 1
Absent
Temp PCG 0
OK
PCG 1
OK
Routing Engine 0
OK
Routing Engine 1
OK
MCS 0
OK
MCS 1
OK
SFM 0 SPP
OK
SFM 0 SPR
OK
SFM 1 SPP
OK
SFM 1 SPR
OK
FPC 0
OK
FPC 1
OK
FPC 2
OK
FPC 4
OK
FPC 5
OK
FPC 6
OK
FPC 7
OK
FPM CMB
OK
FPM Display
OK
Fans Rear Bottom Blower
OK
Rear Top Blower
OK
Front Top Blower
OK
Fan Tray Rear Left
OK
Fan Tray Rear Right
OK
Fan Tray Front Left
OK
Fan Tray Front Right
OK
Misc CIP
OK

Class Item
Temp PEM 0
PEM 1
Routing Engine 0
Routing Engine 1
CB 0 Intake
CB 0 Exhaust A
CB 0 Exhaust B
CB 1 Intake
Measurement
F
F
F
F
F
F
Measurement

Status
OK
OK
OK
OK
OK
OK
OK
OK
Measurement
43
44
33
36
35
34
degrees
degrees
degrees
degrees
degrees
degrees
C
C
C
C
C
C
/
/
/
/
/
/
109 degrees F
111 degrees F
91 degrees F
96 degrees F
95 degrees F
93 degrees F
Fans
show chassis
environment (M160
Router)
CB 1 Exhaust A
CB 1 Exhaust B
FEB 3 Intake
FEB 3 Exhaust A
FEB 3 Exhaust B
FEB 4 Intake
FEB 4 Exhaust A
FEB 4 Exhaust B
FPC 2 Exhaust A
FPC 2 Exhaust B
FPC 3 Exhaust A
FPC 3 Exhaust B
FPC 4 Exhaust A
FPC 4 Exhaust B
Front Top Tray Fan 1
Front Bottom Tray Fan 1
Rear Top Tray Fan 1
Rear Top Tray Fan 2
Rear Top Tray Fan 3
Rear Top Tray Fan 4
Rear Top Tray Fan 5
Rear Top Tray Fan 6
Rear Top Tray Fan 7
Rear Top Tray Fan 8
Rear Bottom Tray Fan 1

Class Item
Status
Power PEM 0
OK
Temp PCG 0
OK
PCG 1
Absent
Routing Engine 0
OK
Routing Engine 1
Absent
MCS 0
OK
SFM 0 SPP
OK
SFM 0 SPR
OK
SFM 1 SPP
OK
SFM 1 SPR
OK
SFM 2 SPP
OK
SFM 2 SPR
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK

Measurement
PEM 1
Absent
50
47
49
50
50
51
52
degrees
degrees
degrees
degrees
degrees
degrees
degrees
C
C
C
C
C
C
C
/
/
/
/
/
/
/
122
116
120
122
122
123
125
degrees
degrees
degrees
degrees
degrees
degrees
degrees
F
F
F
F
F
F
F
401
Fans
Misc
show chassis
environment (M320
Router)
402
SFM 3 SPP
SFM 3 SPR
FPC 0
FPC 6
FPM CMB
FPM Display
Rear Bottom Blower
Rear Top Blower
Front Top Blower
Fan Tray Rear Left
Fan Tray Rear Right
Fan Tray Front Left
Fan Tray Front Right
CIP
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK

Class Item
Status
Temp PEM 0
Absent
PEM 1
Absent
PEM 2
OK
PEM 3
OK
Routing Engine 0
OK
Routing Engine 1
OK
CB 0
OK
CB 1
OK
SIB 0
OK
SIB 1
OK
SIB 2
OK
SIB 3
OK
FPC 0 Intake
OK
FPC 0 Exhaust
OK
FPC 1 Intake
OK
FPC 1 Exhaust
OK
FPC 2 Intake
OK
FPC 2 Exhaust
OK
FPC 3 Intake
OK
FPC 3 Exhaust
OK
FPC 6 Intake
OK
FPC 6 Exhaust
OK
FPC 7 Intake
OK
FPC 7 Exhaust
OK
FPM GBUS
OK
Fan
Top Left Front fan
OK
Top Right Rear fan
OK
Top Right Front fan
OK
Top Left Rear fan
OK
Bottom Left Front fan OK
Bottom Right Rear fan OK
Bottom Right Front fan OK
Bottom Left Rear fan
OK
Rear Fan 1 (TOP)
OK
Rear Fan 2
OK
Rear Fan 3
OK
Rear Fan 4
OK
Rear Fan 5
OK
Rear Fan 6
OK
Rear Fan 7 (Bottom)
OK
Misc CIP
OK

Measurement
show chassis
environment (MX240
Router)
show chassis
environment (MX240

Class Item
Temp PEM 0
PEM 1
PEM 2
PEM 3
Routing Engine 0
Routing Engine 1
CB 0 Intake
CB 0 Exhaust A
CB 0 Exhaust B
CB 0 ACBC
CB 0 SF A
CB 0 SF B
CB 1 Intake
CB 1 Exhaust A
CB 1 Exhaust B
CB 1 ACBC
CB 1 SF A
CB 1 SF B
FPC 1 Intake
FPC 1 Exhaust A
FPC 1 Exhaust B
FPC 1 I3 0 TSensor
FPC 1 I3 0 Chip
FPC 1 I3 1 TSensor
FPC 1 I3 1 Chip
FPC 1 I3 2 TSensor
FPC 1 I3 2 Chip
FPC 1 I3 3 TSensor
FPC 1 I3 3 Chip
FPC 1 IA 0 TSensor
FPC 1 IA 0 Chip
FPC 1 IA 1 TSensor
FPC 1 IA 1 Chip
FPC 2 Intake
FPC 2 Exhaust A
FPC 2 Exhaust B
FPC 2 I3 0 TSensor
FPC 2 I3 0 Chip
FPC 2 I3 1 TSensor
FPC 2 I3 1 Chip
FPC 2 I3 2 TSensor
FPC 2 I3 2 Chip
FPC 2 I3 3 TSensor
FPC 2 I3 3 Chip
FPC 2 IA 0 TSensor
FPC 2 IA 0 Chip
FPC 2 IA 1 TSensor
FPC 2 IA 1 Chip
Fans Front Fan
Middle Fan
Rear Fan
Status
OK
OK
Absent
Absent
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
Measurement

Class Item
Temp PEM 0
Status
OK
Measurement

403
Router with Enhanced

MX SCB)
Fans
show chassis
environment (MX480
Router)
404
PEM 1
PEM 2
PEM 3
Routing Engine 0
Routing Engine 1
CB 0 Intake
CB 0 Exhaust A
CB 0 Exhaust B
CB 0 ACBC
CB 0 XF A
CB 0 XF B
CB 1 Intake
CB 1 Exhaust A
CB 1 Exhaust B
CB 1 ACBC
CB 1 XF A
CB 1 XF B
FPC 1 Intake
FPC 1 Exhaust A
FPC 1 Exhaust B
FPC 1 I3 0 TSensor
FPC 1 I3 0 Chip
FPC 1 I3 1 TSensor
FPC 1 I3 1 Chip
FPC 1 I3 2 TSensor
FPC 1 I3 2 Chip
FPC 1 I3 3 TSensor
FPC 1 I3 3 Chip
FPC 1 IA 0 TSensor
FPC 1 IA 0 Chip
FPC 1 IA 1 TSensor
FPC 1 IA 1 Chip
FPC 2 Intake
FPC 2 Exhaust A
FPC 2 Exhaust B
FPC 2 I3 0 TSensor
FPC 2 I3 0 Chip
FPC 2 I3 1 TSensor
FPC 2 I3 1 Chip
FPC 2 I3 2 TSensor
FPC 2 I3 2 Chip
FPC 2 I3 3 TSensor
FPC 2 I3 3 Chip
FPC 2 IA 0 TSensor
FPC 2 IA 0 Chip
FPC 2 IA 1 TSensor
FPC 2 IA 1 Chip
Front Fan
Middle Fan
Rear Fan

Class Item
Temp PEM 0
PEM 1
PEM 2
PEM 3
Routing Engine 0
Routing Engine 1
CB 0 Intake
CB 0 Exhaust A
OK
Absent
Absent
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
Status
OK
OK
Absent
Absent
OK
OK
OK
OK
Measurement

44
45
36
38
degrees
degrees
degrees
degrees
C
C
C
C
/
/
/
/
111 degrees F
113 degrees F
96 degrees F
100 degrees F
Fans
show chassis
environment (MX480
CB 0 Exhaust B
CB 0 ACBC
CB 0 SF A
CB 0 SF B
CB 1 Intake
CB 1 Exhaust A
CB 1 Exhaust B
CB 1 ACBC
CB 1 SF A
CB 1 SF B
FPC 0 Intake
FPC 0 Exhaust A
FPC 0 Exhaust B
FPC 0 I3 0 TSensor
FPC 0 I3 0 Chip
FPC 0 I3 1 TSensor
FPC 0 I3 1 Chip
FPC 0 I3 2 TSensor
FPC 0 I3 2 Chip
FPC 0 I3 3 TSensor
FPC 0 I3 3 Chip
FPC 0 IA 0 TSensor
FPC 0 IA 0 Chip
FPC 0 IA 1 TSensor
FPC 0 IA 1 Chip
FPC 1 Intake
FPC 1 Exhaust A
FPC 1 Exhaust B
FPC 1 I3 0 TSensor
FPC 1 I3 0 Chip
FPC 1 I3 1 TSensor
FPC 1 I3 1 Chip
FPC 1 I3 2 TSensor
FPC 1 I3 2 Chip
FPC 1 I3 3 TSensor
FPC 1 I3 3 Chip
FPC 1 IA 0 TSensor
FPC 1 IA 0 Chip
FPC 1 IA 1 TSensor
FPC 1 IA 1 Chip
Top Rear Fan
Bottom Rear Fan
Top Middle Fan
Bottom Middle Fan
Top Front Fan
Bottom Front Fan

Class Item
Temp PEM 0
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK

Status
OK
Measurement
405

MX SCB)
Fans
show chassis
environment (MX960
Router)
406
PEM 1
PEM 2
PEM 3
Routing Engine 0
Routing Engine 1
CB 0 Intake
CB 0 Exhaust A
CB 0 Exhaust B
CB 0 ACBC
CB 0 XF A
CB 0 XF B
CB 1 Intake
CB 1 Exhaust A
CB 1 Exhaust B
CB 1 ACBC
CB 1 XF A
CB 1 XF B
FPC 0 Intake
FPC 0 Exhaust A
FPC 0 Exhaust B
FPC 0 I3 0 TSensor
FPC 0 I3 0 Chip
FPC 0 I3 1 TSensor
FPC 0 I3 1 Chip
FPC 0 I3 2 TSensor
FPC 0 I3 2 Chip
FPC 0 I3 3 TSensor
FPC 0 I3 3 Chip
FPC 0 IA 0 TSensor
FPC 0 IA 0 Chip
FPC 0 IA 1 TSensor
FPC 0 IA 1 Chip
FPC 1 Intake
FPC 1 Exhaust A
FPC 1 Exhaust B
FPC 1 I3 0 TSensor
FPC 1 I3 0 Chip
FPC 1 I3 1 TSensor
FPC 1 I3 1 Chip
FPC 1 I3 2 TSensor
FPC 1 I3 2 Chip
FPC 1 I3 3 TSensor
FPC 1 I3 3 Chip
FPC 1 IA 0 TSensor
FPC 1 IA 0 Chip
FPC 1 IA 1 TSensor
FPC 1 IA 1 Chip
Top Rear Fan
Bottom Rear Fan
Top Middle Fan
Bottom Middle Fan
Top Front Fan
Bottom Front Fan

Class Item
Temp PEM 0
PEM 1
PEM 2
PEM 3
Routing Engine 0
OK
Absent
Absent
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
Status
Absent
Absent
Check
OK
OK
Measurement

Fans
show chassis
environment (MX960
Routing Engine 1
CB 0 Intake
CB 0 Exhaust A
CB 0 Exhaust B
CB 1 Intake
CB 1 Exhaust A
CB 1 Exhaust B
CB 1 ACBC
CB 1 SF A
CB 1 SF B
CB 2 Intake
CB 2 Exhaust A
CB 2 Exhaust B
CB 2 ACBC
CB 2 SF A
CB 2 SF B
FPC 4 Intake
FPC 4 Exhaust A
FPC 4 Exhaust B
FPC 7 Intake
FPC 7 Exhaust A
FPC 7 Exhaust B
Top Fan Tray Temp
Top Tray Fan 1
Top Tray Fan 2
Top Tray Fan 3
Top Tray Fan 4
Top Tray Fan 5
Top Tray Fan 6
Bottom Fan Tray Temp
Bottom Tray Fan 1
Bottom Tray Fan 2
Bottom Tray Fan 3
Bottom Tray Fan 4
Bottom Tray Fan 5
Bottom Tray Fan 6

Class Item
Temp PEM 0
Absent
OK
OK
OK
Absent
Absent
Absent
Absent
Absent
Absent
Absent
Absent
Absent
Absent
Absent
Absent
OK
OK
OK
OK
OK
OK
Failed
OK
OK
OK
OK
OK
OK
Failed
OK
OK
OK
OK
OK
OK
Status
Absent
24
36
38
24
36
42
degrees
degrees
degrees
degrees
degrees
degrees
C
C
C
C
C
C
/
/
/
/
/
/
75 degrees F
96 degrees F
100 degrees F
75 degrees F
96 degrees F
107 degrees F
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
at
at
at
at
at
at
normal
normal
normal
normal
normal
normal
speed
speed
speed
speed
speed
speed
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
at
at
at
at
at
at
normal
normal
normal
normal
normal
normal
speed
speed
speed
speed
speed
speed
Measurement
407

MX SCB)
408
PEM 1
PEM 2
PEM 3
Routing Engine 0
Routing Engine 0 CPU
Routing Engine 1
CB 0 Intake
CB 0 Exhaust A
CB 0 Exhaust B
CB 0 ACBC
CB 0 XF A
CB 0 XF B
CB 1 Intake
CB 1 Exhaust A
CB 1 Exhaust B
CB 1 ACBC
CB 1 XF A
CB 1 XF B
CB 2 Intake
CB 2 Exhaust A
CB 2 Exhaust B
CB 2 ACBC
CB 2 XF A
CB 2 XF B
FPC 0 Intake
FPC 0 Exhaust A
FPC 0 Exhaust B
FPC 0 I3 0 TSensor
FPC 0 I3 0 Chip
FPC 0 I3 1 TSensor
FPC 0 I3 1 Chip
FPC 0 I3 2 TSensor
FPC 0 I3 2 Chip
FPC 0 I3 3 TSensor
FPC 0 I3 3 Chip
FPC 0 IA 0 TSensor
FPC 0 IA 0 Chip
FPC 0 IA 1 TSensor
FPC 0 IA 1 Chip
FPC 1 Intake
FPC 1 Exhaust A
FPC 1 Exhaust B
FPC 1 LU 0 TCAM TSensor
FPC 1 LU 0 TCAM Chip
FPC 1 LU 0 TSensor
FPC 1 LU 0 Chip
FPC 1 MQ 0 TSensor
FPC 1 MQ 0 Chip
FPC 1 LU 1 TCAM TSensor
FPC 1 LU 1 TCAM Chip
FPC 1 LU 1 TSensor
FPC 1 LU 1 Chip
FPC 1 MQ 1 TSensor
FPC 1 MQ 1 Chip
FPC 2 Intake
FPC 2 Exhaust A
FPC 2 Exhaust B
FPC 2 I3 0 TSensor
FPC 2 I3 0 Chip
FPC 2 I3 1 TSensor
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
50
50
50
42
51
39
44
35
36
43
38
53
47
35
35
41
38
52
47
32
30
35
33
51
50
35
39
50
50
56
47
50
45
48
41
44
45
45
44
48
36
47
43
53
57
53
60
53
56
51
52
51
53
51
58
35
39
54
52
59
48
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
122 degrees F
122 degrees F
122 degrees F
107 degrees F
123 degrees F
102 degrees F
111 degrees F
95 degrees F
96 degrees F
109 degrees F
100 degrees F
127 degrees F
116 degrees F
95 degrees F
95 degrees F
105 degrees F
100 degrees F
125 degrees F
116 degrees F
89 degrees F
86 degrees F
95 degrees F
91 degrees F
123 degrees F
122 degrees F
95 degrees F
102 degrees F
122 degrees F
122 degrees F
132 degrees F
116 degrees F
122 degrees F
113 degrees F
118 degrees F
105 degrees F
111 degrees F
113 degrees F
113 degrees F
111 degrees F
118 degrees F
96 degrees F
116 degrees F
109 degrees F
127 degrees F
134 degrees F
127 degrees F
140 degrees F
127 degrees F
132 degrees F
123 degrees F
125 degrees F
123 degrees F
127 degrees F
123 degrees F
136 degrees F
95 degrees F
102 degrees F
129 degrees F
125 degrees F
138 degrees F
118 degrees F
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
2 I3 1 Chip
2 I3 2 TSensor
2 I3 2 Chip
2 I3 3 TSensor
2 I3 3 Chip
2 IA 0 TSensor
2 IA 0 Chip
2 IA 1 TSensor
2 IA 1 Chip
3 Intake
3 Exhaust A
3 Exhaust B
3 I3 0 TSensor
3 I3 0 Chip
3 I3 1 TSensor
3 I3 1 Chip
3 IA 0 TSensor
3 IA 0 Chip
5 Intake
5 Exhaust A
5 Exhaust B
5 LU 0 TSensor
5 LU 0 Chip
5 LU 1 TSensor
5 LU 1 Chip
5 LU 2 TSensor
5 LU 2 Chip
5 LU 3 TSensor
5 LU 3 Chip
5 MQ 0 TSensor
5 MQ 0 Chip
5 MQ 1 TSensor
5 MQ 1 Chip
5 MQ 2 TSensor
5 MQ 2 Chip
5 MQ 3 TSensor
5 MQ 3 Chip
7 Intake
7 Exhaust A
7 Exhaust B
7 QX 0 TSensor
7 QX 0 Chip
7 LU 0 TCAM TSensor
7 LU 0 TCAM Chip
7 LU 0 TSensor
7 LU 0 Chip
7 MQ 0 TSensor
7 MQ 0 Chip
8 Intake
8 Exhaust A
8 Exhaust B
8 I3 0 TSensor
8 I3 0 Chip
8 BDS 0 TSensor
8 BDS 0 Chip
8 IA 0 TSensor
8 IA 0 Chip
10 Intake
10 Exhaust A
10 Exhaust B
10 I3 0 TSensor
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
52
47
49
41
44
47
46
45
49
34
34
47
48
52
46
48
41
40
42
42
53
53
54
53
61
53
51
53
53
47
52
47
52
47
46
47
45
36
35
33
42
47
42
44
42
46
42
45
33
33
36
38
43
37
36
37
37
38
36
41
40
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
125 degrees F
116 degrees F
120 degrees F
105 degrees F
111 degrees F
116 degrees F
114 degrees F
113 degrees F
120 degrees F
93 degrees F
93 degrees F
116 degrees F
118 degrees F
125 degrees F
114 degrees F
118 degrees F
105 degrees F
104 degrees F
107 degrees F
107 degrees F
127 degrees F
127 degrees F
129 degrees F
127 degrees F
141 degrees F
127 degrees F
123 degrees F
127 degrees F
127 degrees F
116 degrees F
125 degrees F
116 degrees F
125 degrees F
116 degrees F
114 degrees F
116 degrees F
113 degrees F
96 degrees F
95 degrees F
91 degrees F
107 degrees F
116 degrees F
107 degrees F
111 degrees F
107 degrees F
114 degrees F
107 degrees F
113 degrees F
91 degrees F
91 degrees F
96 degrees F
100 degrees F
109 degrees F
98 degrees F
96 degrees F
98 degrees F
98 degrees F
100 degrees F
96 degrees F
105 degrees F
104 degrees F
409
Fans
show chassis
environment (MX2020
Router)
410
FPC 10 I3 0 Chip
FPC 10 I3 1 TSensor
FPC 10 I3 1 Chip
FPC 10 I3 2 TSensor
FPC 10 I3 2 Chip
FPC 10 I3 3 TSensor
FPC 10 I3 3 Chip
FPC 10 IA 0 TSensor
FPC 10 IA 0 Chip
FPC 10 IA 1 TSensor
FPC 10 IA 1 Chip
Top Fan Tray Temp
Top Tray Fan 1
Top Tray Fan 2
Top Tray Fan 3
Top Tray Fan 4
Top Tray Fan 5
Top Tray Fan 6
Bottom Fan Tray Temp
Bottom Tray Fan 1
Bottom Tray Fan 2
Bottom Tray Fan 3
Bottom Tray Fan 4
Bottom Tray Fan 5
Bottom Tray Fan 6

Class Item
Temp PSM 0
PSM 1
PSM 2
PSM 3
PSM 4
PSM 5
PSM 6
PSM 7
PSM 8
PSM 9
PSM 10
PSM 11
PSM 12
PSM 13
PSM 14
PSM 15
PSM 16
PSM 17
PDM 0
PDM 1
PDM 2
PDM 3
CB 0 IntakeA-Zone0
CB 0 IntakeB-Zone1
CB 0 IntakeC-Zone0
CB 0 ExhaustA-Zone0
CB 0 ExhaustB-Zone1
CB 0 TCBC-Zone0
CB 1 IntakeA-Zone0
CB 1 IntakeB-Zone1
CB 1 IntakeC-Zone0
CB 1 ExhaustA-Zone0
CB 1 ExhaustB-Zone1
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK

Status
Absent
Absent
OK
OK
OK
OK
OK
OK
OK
Absent
Absent
OK
OK
OK
OK
OK
OK
OK
OK
Absent
Absent
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
Measurement
41
39
39
38
38
38
37
degrees
degrees
degrees
degrees
degrees
degrees
degrees
C
C
C
C
C
C
C
/
/
/
/
/
/
/
105 degrees F
102 degrees F
102 degrees F
100 degrees F
100 degrees F
100 degrees F
98 degrees F
47
45
44
44
43
42
41
degrees
degrees
degrees
degrees
degrees
degrees
degrees
C
C
C
C
C
C
C
/
/
/
/
/
/
/
116
113
111
111
109
107
105
45
34
48
45
37
41
46
42
49
46
41
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
C
C
C
C
C
C
C
C
C
C
C
/
/
/
/
/
/
/
/
/
/
/
113 degrees F
93 degrees F
118 degrees F
113 degrees F
98 degrees F
105 degrees F
114 degrees F
107 degrees F
120 degrees F
114 degrees F
105 degrees F
degrees
degrees
degrees
degrees
degrees
degrees
degrees
F
F
F
F
F
F
F
CB 1 TCBC-Zone0
SPMB 0 Intake
SPMB 1 Intake
Routing Engine 0
Routing Engine 1
SFB 0 Intake-Zone0
SFB 0 Exhaust-Zone1
SFB 0 IntakeA-Zone0
SFB 0 IntakeB-Zone1
SFB 0 Exhaust-Zone0
SFB 0 SFB-XF2-Zone1
SFB 0 SFB-XF1-Zone0
SFB 0 SFB-XF0-Zone0
SFB 1 Intake-Zone0
SFB 1 Exhaust-Zone1
SFB 1 IntakeA-Zone0
SFB 1 IntakeB-Zone1
SFB 1 Exhaust-Zone0
SFB 1 SFB-XF2-Zone1
SFB 1 SFB-XF1-Zone0
SFB 1 SFB-XF0-Zone0
SFB 2 Intake-Zone0
SFB 2 Exhaust-Zone1
SFB 2 IntakeA-Zone0
SFB 2 IntakeB-Zone1
SFB 2 Exhaust-Zone0
SFB 2 SFB-XF2-Zone1
SFB 2 SFB-XF1-Zone0
SFB 2 SFB-XF0-Zone0
SFB 3 Intake-Zone0
SFB 3 Exhaust-Zone1
SFB 3 IntakeA-Zone0
SFB 3 IntakeB-Zone1
SFB 3 Exhaust-Zone0
SFB 3 SFB-XF2-Zone1
SFB 3 SFB-XF1-Zone0
SFB 3 SFB-XF0-Zone0
SFB 4 Intake-Zone0
SFB 4 Exhaust-Zone1
SFB 4 IntakeA-Zone0
SFB 4 IntakeB-Zone1
SFB 4 Exhaust-Zone0
SFB 4 SFB-XF2-Zone1
SFB 4 SFB-XF1-Zone0
SFB 4 SFB-XF0-Zone0
SFB 5 Intake-Zone0
SFB 5 Exhaust-Zone1
SFB 5 IntakeA-Zone0
SFB 5 IntakeB-Zone1
SFB 5 Exhaust-Zone0
SFB 5 SFB-XF2-Zone1
SFB 5 SFB-XF1-Zone0
SFB 5 SFB-XF0-Zone0
SFB 6 Intake-Zone0
SFB 6 Exhaust-Zone1
SFB 6 IntakeA-Zone0
SFB 6 IntakeB-Zone1
SFB 6 Exhaust-Zone0
SFB 6 SFB-XF2-Zone1
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
46
33
42
35
34
44
42
55
48
50
40
52
61
69
68
56
47
51
40
51
62
67
69
56
47
51
40
53
65
69
70
57
48
52
41
53
66
69
71
58
49
54
42
53
64
68
71
58
50
53
43
54
66
69
74
58
49
53
43
53
65
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
114 degrees F
91 degrees F
107 degrees F
95 degrees F
93 degrees F
111 degrees F
107 degrees F
131 degrees F
118 degrees F
122 degrees F
104 degrees F
125 degrees F
141 degrees F
156 degrees F
154 degrees F
132 degrees F
116 degrees F
123 degrees F
104 degrees F
123 degrees F
143 degrees F
152 degrees F
156 degrees F
132 degrees F
116 degrees F
123 degrees F
104 degrees F
127 degrees F
149 degrees F
156 degrees F
158 degrees F
134 degrees F
118 degrees F
125 degrees F
105 degrees F
127 degrees F
150 degrees F
156 degrees F
159 degrees F
136 degrees F
120 degrees F
129 degrees F
107 degrees F
127 degrees F
147 degrees F
154 degrees F
159 degrees F
136 degrees F
122 degrees F
127 degrees F
109 degrees F
129 degrees F
150 degrees F
156 degrees F
165 degrees F
136 degrees F
120 degrees F
127 degrees F
109 degrees F
127 degrees F
149 degrees F
411
SFB
SFB
SFB
SFB
SFB
SFB
SFB
SFB
SFB
SFB
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
412
6
6
7
7
7
7
7
7
7
7
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
2
2
2
2
2
2
2
2
2
2
2
2
2
SFB-XF1-Zone0
SFB-XF0-Zone0
Intake-Zone0
Exhaust-Zone1
IntakeA-Zone0
IntakeB-Zone1
Exhaust-Zone0
SFB-XF2-Zone1
SFB-XF1-Zone0
SFB-XF0-Zone0
Intake
Exhaust A
Exhaust B
LU 0 TSen
LU 0 Chip
LU 1 TSen
LU 1 Chip
LU 2 TSen
LU 2 Chip
LU 3 TSen
LU 3 Chip
MQ 0 TSen
MQ 0 Chip
MQ 1 TSen
MQ 1 Chip
MQ 2 TSen
MQ 2 Chip
MQ 3 TSen
MQ 3 Chip
Intake
Exhaust A
Exhaust B
LU 0 TSen
LU 0 Chip
LU 1 TSen
LU 1 Chip
LU 2 TSen
LU 2 Chip
LU 3 TSen
LU 3 Chip
MQ 0 TSen
MQ 0 Chip
MQ 1 TSen
MQ 1 Chip
MQ 2 TSen
MQ 2 Chip
MQ 3 TSen
MQ 3 Chip
Intake
Exhaust A
Exhaust B
LU 0 TSen
LU 0 Chip
LU 1 TSen
LU 1 Chip
LU 2 TSen
LU 2 Chip
LU 3 TSen
LU 3 Chip
MQ 0 TSen
MQ 0 Chip
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
68
72
57
50
53
43
54
68
69
73
41
48
62
59
62
59
64
59
53
59
53
47
49
47
51
47
44
47
45
40
49
58
55
56
55
58
55
49
55
51
47
48
47
50
47
44
47
44
39
49
61
58
60
58
65
58
51
58
53
47
50
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
154
161
134
122
127
109
129
154
156
163
105
118
143
138
143
138
147
138
127
138
127
116
120
116
123
116
111
116
113
104
120
136
131
132
131
136
131
120
131
123
116
118
116
122
116
111
116
111
102
120
141
136
140
136
149
136
123
136
127
116
122
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
2
2
2
2
2
2
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
MQ 1 TSen
MQ 1 Chip
MQ 2 TSen
MQ 2 Chip
MQ 3 TSen
MQ 3 Chip
Intake
Exhaust A
Exhaust B
LU 0 TSen
LU 0 Chip
LU 1 TSen
LU 1 Chip
LU 2 TSen
LU 2 Chip
LU 3 TSen
LU 3 Chip
MQ 0 TSen
MQ 0 Chip
MQ 1 TSen
MQ 1 Chip
MQ 2 TSen
MQ 2 Chip
MQ 3 TSen
MQ 3 Chip
Intake
Exhaust A
Exhaust B
LU 0 TSen
LU 0 Chip
LU 1 TSen
LU 1 Chip
LU 2 TSen
LU 2 Chip
LU 3 TSen
LU 3 Chip
MQ 0 TSen
MQ 0 Chip
MQ 1 TSen
MQ 1 Chip
MQ 2 TSen
MQ 2 Chip
MQ 3 TSen
MQ 3 Chip
Intake
Exhaust A
Exhaust B
LU 0 TSen
LU 0 Chip
LU 1 TSen
LU 1 Chip
LU 2 TSen
LU 2 Chip
LU 3 TSen
LU 3 Chip
MQ 0 TSen
MQ 0 Chip
MQ 1 TSen
MQ 1 Chip
MQ 2 TSen
MQ 2 Chip
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
47
52
47
45
47
46
40
49
61
58
61
58
62
58
51
58
53
48
50
48
54
48
45
48
48
40
49
62
59
62
59
65
59
51
59
53
48
52
48
53
48
46
48
47
41
50
63
60
63
60
66
60
56
60
54
49
52
49
53
49
48
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
116
125
116
113
116
114
104
120
141
136
141
136
143
136
123
136
127
118
122
118
129
118
113
118
118
104
120
143
138
143
138
149
138
123
138
127
118
125
118
127
118
114
118
116
105
122
145
140
145
140
150
140
132
140
129
120
125
120
127
120
118
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
413
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
414
5
5
6
6
6
6
6
6
6
6
6
6
6
6
6
6
6
6
6
6
6
7
7
7
7
7
7
7
7
7
7
7
7
7
7
7
7
7
7
7
8
8
8
8
8
8
8
8
8
8
8
8
8
8
8
8
8
8
8
9
9
MQ 3 TSen
MQ 3 Chip
Intake
Exhaust A
Exhaust B
LU 0 TSen
LU 0 Chip
LU 1 TSen
LU 1 Chip
LU 2 TSen
LU 2 Chip
LU 3 TSen
LU 3 Chip
MQ 0 TSen
MQ 0 Chip
MQ 1 TSen
MQ 1 Chip
MQ 2 TSen
MQ 2 Chip
MQ 3 TSen
MQ 3 Chip
Intake
Exhaust A
Exhaust B
LU 0 TSen
LU 0 Chip
LU 1 TSen
LU 1 Chip
LU 2 TSen
LU 2 Chip
LU 3 TSen
LU 3 Chip
MQ 0 TSen
MQ 0 Chip
MQ 1 TSen
MQ 1 Chip
MQ 2 TSen
MQ 2 Chip
MQ 3 TSen
MQ 3 Chip
Intake
Exhaust A
Exhaust B
LU 0 TSen
LU 0 Chip
LU 1 TSen
LU 1 Chip
LU 2 TSen
LU 2 Chip
LU 3 TSen
LU 3 Chip
MQ 0 TSen
MQ 0 Chip
MQ 1 TSen
MQ 1 Chip
MQ 2 TSen
MQ 2 Chip
MQ 3 TSen
MQ 3 Chip
Intake
Exhaust A
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
49
47
42
51
63
61
64
61
66
61
56
61
56
50
56
50
59
50
49
50
49
41
51
63
60
61
60
65
60
54
60
53
50
53
50
54
50
47
50
47
41
50
62
59
62
59
64
59
55
59
54
49
51
49
52
49
46
49
47
42
51
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
120
116
107
123
145
141
147
141
150
141
132
141
132
122
132
122
138
122
120
122
120
105
123
145
140
141
140
149
140
129
140
127
122
127
122
129
122
116
122
116
105
122
143
138
143
138
147
138
131
138
129
120
123
120
125
120
114
120
116
107
123
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
9 Exhaust B
9 LU 0 TSen
9 LU 0 Chip
9 LU 1 TSen
9 LU 1 Chip
9 LU 2 TSen
9 LU 2 Chip
9 LU 3 TSen
9 LU 3 Chip
9 MQ 0 TSen
9 MQ 0 Chip
9 MQ 1 TSen
9 MQ 1 Chip
9 MQ 2 TSen
9 MQ 2 Chip
9 MQ 3 TSen
9 MQ 3 Chip
10 Intake
10 Exhaust A
10 Exhaust B
10 LU 0 TSen
10 LU 0 Chip
10 LU 1 TSen
10 LU 1 Chip
10 LU 2 TSen
10 LU 2 Chip
10 LU 3 TSen
10 LU 3 Chip
10 MQ 0 TSen
10 MQ 0 Chip
10 MQ 1 TSen
10 MQ 1 Chip
10 MQ 2 TSen
10 MQ 2 Chip
10 MQ 3 TSen
10 MQ 3 Chip
11 Intake
11 Exhaust A
11 Exhaust B
11 LU 0 TSen
11 LU 0 Chip
11 LU 1 TSen
11 LU 1 Chip
11 LU 2 TSen
11 LU 2 Chip
11 LU 3 TSen
11 LU 3 Chip
11 MQ 0 TSen
11 MQ 0 Chip
11 MQ 1 TSen
11 MQ 1 Chip
11 MQ 2 TSen
11 MQ 2 Chip
11 MQ 3 TSen
11 MQ 3 Chip
12 Intake
12 Exhaust A
12 Exhaust B
12 LU 0 TSen
12 LU 0 Chip
12 LU 1 TSen
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
63
60
65
60
67
60
54
60
54
51
55
51
59
51
49
51
49
44
49
55
54
55
54
59
54
52
54
51
48
49
48
52
48
47
48
47
30
35
30
57
58
57
62
57
53
57
54
52
52
52
57
52
48
52
52
40
47
52
51
52
51
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
145 degrees F
140 degrees F
149 degrees F
140 degrees F
152 degrees F
140 degrees F
129 degrees F
140 degrees F
129 degrees F
123 degrees F
131 degrees F
123 degrees F
138 degrees F
123 degrees F
120 degrees F
123 degrees F
120 degrees F
111 degrees F
120 degrees F
131 degrees F
129 degrees F
131 degrees F
129 degrees F
138 degrees F
129 degrees F
125 degrees F
129 degrees F
123 degrees F
118 degrees F
120 degrees F
118 degrees F
125 degrees F
118 degrees F
116 degrees F
118 degrees F
116 degrees F
86 degrees F
95 degrees F
86 degrees F
134 degrees F
136 degrees F
134 degrees F
143 degrees F
134 degrees F
127 degrees F
134 degrees F
129 degrees F
125 degrees F
125 degrees F
125 degrees F
134 degrees F
125 degrees F
118 degrees F
125 degrees F
125 degrees F
104 degrees F
116 degrees F
125 degrees F
123 degrees F
125 degrees F
123 degrees F
415
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
416
12
12
12
12
12
12
12
12
12
12
12
12
12
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
14
14
14
14
14
14
14
14
14
14
14
14
14
14
14
14
14
14
14
15
15
15
15
15
15
15
15
15
15
LU 1 Chip
LU 2 TSen
LU 2 Chip
LU 3 TSen
LU 3 Chip
MQ 0 TSen
MQ 0 Chip
MQ 1 TSen
MQ 1 Chip
MQ 2 TSen
MQ 2 Chip
MQ 3 TSen
MQ 3 Chip
Intake
Exhaust A
Exhaust B
LU 0 TSen
LU 0 Chip
LU 1 TSen
LU 1 Chip
LU 2 TSen
LU 2 Chip
LU 3 TSen
LU 3 Chip
MQ 0 TSen
MQ 0 Chip
MQ 1 TSen
MQ 1 Chip
MQ 2 TSen
MQ 2 Chip
MQ 3 TSen
MQ 3 Chip
Intake
Exhaust A
Exhaust B
LU 0 TSen
LU 0 Chip
LU 1 TSen
LU 1 Chip
LU 2 TSen
LU 2 Chip
LU 3 TSen
LU 3 Chip
MQ 0 TSen
MQ 0 Chip
MQ 1 TSen
MQ 1 Chip
MQ 2 TSen
MQ 2 Chip
MQ 3 TSen
MQ 3 Chip
Intake
Exhaust A
Exhaust B
LU 0 TSen
LU 0 Chip
LU 1 TSen
LU 1 Chip
LU 2 TSen
LU 2 Chip
LU 3 TSen
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
55
51
47
51
50
46
46
46
50
46
44
46
46
40
48
52
51
52
51
55
51
48
51
48
46
46
46
50
46
44
46
46
40
50
51
50
50
50
54
50
47
50
49
47
46
47
51
47
45
47
48
44
49
60
50
56
50
50
50
58
50
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
131
123
116
123
122
114
114
114
122
114
111
114
114
104
118
125
123
125
123
131
123
118
123
118
114
114
114
122
114
111
114
114
104
122
123
122
122
122
129
122
116
122
120
116
114
116
123
116
113
116
118
111
120
140
122
132
122
122
122
136
122
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
15
15
15
15
15
15
15
16
16
16
16
16
16
16
16
16
16
16
16
16
16
16
16
16
16
16
17
17
17
17
17
17
17
17
17
17
17
17
17
17
17
17
17
17
17
18
18
18
18
18
18
18
18
18
18
18
18
18
18
18
18
LU 3 Chip
XM 0 TSen
XM 0 Chip
XF 0 TSen
XF 0 Chip
PLX Switch TSen
PLX Switch Chip
Intake
Exhaust A
Exhaust B
LU 0 TSen
LU 0 Chip
LU 1 TSen
LU 1 Chip
LU 2 TSen
LU 2 Chip
LU 3 TSen
LU 3 Chip
MQ 0 TSen
MQ 0 Chip
MQ 1 TSen
MQ 1 Chip
MQ 2 TSen
MQ 2 Chip
MQ 3 TSen
MQ 3 Chip
Intake
Exhaust A
Exhaust B
LU 0 TSen
LU 0 Chip
LU 1 TSen
LU 1 Chip
LU 2 TSen
LU 2 Chip
LU 3 TSen
LU 3 Chip
MQ 0 TSen
MQ 0 Chip
MQ 1 TSen
MQ 1 Chip
MQ 2 TSen
MQ 2 Chip
MQ 3 TSen
MQ 3 Chip
Intake
Exhaust A
Exhaust B
LU 0 TSen
LU 0 Chip
LU 1 TSen
LU 1 Chip
LU 2 TSen
LU 2 Chip
LU 3 TSen
LU 3 Chip
MQ 0 TSen
MQ 0 Chip
MQ 1 TSen
MQ 1 Chip
MQ 2 TSen
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
63
50
56
50
68
50
56
42
51
53
51
52
51
55
51
48
51
49
49
48
49
53
49
46
49
49
43
51
55
54
57
54
60
54
53
54
53
49
50
49
54
49
47
49
51
44
53
57
56
57
56
62
56
53
56
55
51
54
51
58
51
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
145
122
132
122
154
122
132
107
123
127
123
125
123
131
123
118
123
120
120
118
120
127
120
114
120
120
109
123
131
129
134
129
140
129
127
129
127
120
122
120
129
120
116
120
123
111
127
134
132
134
132
143
132
127
132
131
123
129
123
136
123
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
417
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
418
18 MQ 2 Chip
18 MQ 3 TSen
18 MQ 3 Chip
19 Intake
19 Exhaust A
19 Exhaust B
19 LU 0 TSen
19 LU 0 Chip
19 LU 1 TSen
19 LU 1 Chip
19 LU 2 TSen
19 LU 2 Chip
19 LU 3 TSen
19 LU 3 Chip
19 MQ 0 TSen
19 MQ 0 Chip
19 MQ 1 TSen
19 MQ 1 Chip
19 MQ 2 TSen
19 MQ 2 Chip
19 MQ 3 TSen
19 MQ 3 Chip
0 Intake
0 Exhaust
0 ADC-XF1
0 ADC-XF0
1 Intake
1 Exhaust
1 ADC-XF1
1 ADC-XF0
2 Intake
2 Exhaust
2 ADC-XF1
2 ADC-XF0
3 Intake
3 Exhaust
3 ADC-XF1
3 ADC-XF0
4 Intake
4 Exhaust
4 ADC-XF1
4 ADC-XF0
5 Intake
5 Exhaust
5 ADC-XF1
5 ADC-XF0
6 Intake
6 Exhaust
6 ADC-XF1
6 ADC-XF0
7 Intake
7 Exhaust
7 ADC-XF1
7 ADC-XF0
8 Intake
8 Exhaust
8 ADC-XF1
8 ADC-XF0
9 Intake
9 Exhaust
9 ADC-XF1
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
50
51
53
48
56
64
63
64
63
70
63
61
63
62
56
60
56
62
56
56
56
57
40
52
59
66
38
50
59
63
37
52
53
61
40
51
61
64
39
51
60
63
38
54
56
67
39
52
59
66
39
54
62
70
39
52
61
65
41
51
63
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
122 degrees F
123 degrees F
127 degrees F
118 degrees F
132 degrees F
147 degrees F
145 degrees F
147 degrees F
145 degrees F
158 degrees F
145 degrees F
141 degrees F
145 degrees F
143 degrees F
132 degrees F
140 degrees F
132 degrees F
143 degrees F
132 degrees F
132 degrees F
132 degrees F
134 degrees F
104 degrees F
125 degrees F
138 degrees F
150 degrees F
100 degrees F
122 degrees F
138 degrees F
145 degrees F
98 degrees F
125 degrees F
127 degrees F
141 degrees F
104 degrees F
123 degrees F
141 degrees F
147 degrees F
102 degrees F
123 degrees F
140 degrees F
145 degrees F
100 degrees F
129 degrees F
132 degrees F
152 degrees F
102 degrees F
125 degrees F
138 degrees F
150 degrees F
102 degrees F
129 degrees F
143 degrees F
158 degrees F
102 degrees F
125 degrees F
141 degrees F
149 degrees F
105 degrees F
123 degrees F
145 degrees F
Fans
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
9 ADC-XF0
10 Intake
10 Exhaust
10 ADC-XF1
10 ADC-XF0
12 Intake
12 Exhaust
12 ADC-XF1
12 ADC-XF0
13 Intake
13 Exhaust
13 ADC-XF1
13 ADC-XF0
14 Intake
14 Exhaust
14 ADC-XF1
14 ADC-XF0
15 Intake
15 Exhaust
15 ADC-XF1
15 ADC-XF0
16 Intake
16 Exhaust
16 ADC-XF1
16 ADC-XF0
17 Intake
17 Exhaust
17 ADC-XF1
17 ADC-XF0
18 Intake
18 Exhaust
18 ADC-XF1
18 ADC-XF0
19 Intake
19 Exhaust
19 ADC-XF1
19 ADC-XF0
Tray 0 Fan
Tray 0 Fan
Tray 0 Fan
Tray 0 Fan
Tray 0 Fan
Tray 0 Fan
Tray 1 Fan
Tray 1 Fan
Tray 1 Fan
Tray 1 Fan
Tray 1 Fan
Tray 1 Fan
Tray 2 Fan
Tray 2 Fan
Tray 2 Fan
Tray 2 Fan
Tray 2 Fan
Tray 2 Fan
Tray 3 Fan
Tray 3 Fan
Tray 3 Fan
Tray 3 Fan
Tray 3 Fan
Tray 3 Fan
1
2
3
4
5
6
1
2
3
4
5
6
1
2
3
4
5
6
1
2
3
4
5
6
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
63 degrees
48 degrees
53 degrees
67 degrees
66 degrees
49 degrees
54 degrees
67 degrees
67 degrees
49 degrees
57 degrees
66 degrees
69 degrees
51 degrees
59 degrees
69 degrees
74 degrees
50 degrees
59 degrees
68 degrees
69 degrees
52 degrees
58 degrees
68 degrees
70 degrees
52 degrees
59 degrees
69 degrees
71 degrees
53 degrees
59 degrees
68 degrees
73 degrees
50 degrees
59 degrees
68 degrees
72 degrees
7440 RPM
7200 RPM
6960 RPM
7200 RPM
7080 RPM
6840 RPM
6840 RPM
6960 RPM
6960 RPM
7080 RPM
6960 RPM
6960 RPM
8640 RPM
8640 RPM
8760 RPM
8760 RPM
8640 RPM
8640 RPM
8520 RPM
8520 RPM
8640 RPM
8640 RPM
8520 RPM
8520 RPM
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
145
118
127
152
150
120
129
152
152
120
134
150
156
123
138
156
165
122
138
154
156
125
136
154
158
125
138
156
159
127
138
154
163
122
138
154
161
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
419
show chassis
environment (MX2010
Router)
420

Class Item
Temp PSM 0
PSM 1
PSM 2
PSM 3
PSM 4
PSM 5
PSM 6
PSM 7
PSM 8
PDM 0
PDM 1
CB 0 IntakeA-Zone0
CB 0 IntakeB-Zone1
CB 0 IntakeC-Zone0
CB 0 ExhaustA-Zone0
CB 0 ExhaustB-Zone1
CB 0 TCBC-Zone0
CB 1 IntakeA-Zone0
CB 1 IntakeB-Zone1
CB 1 IntakeC-Zone0
CB 1 ExhaustA-Zone0
CB 1 ExhaustB-Zone1
CB 1 TCBC-Zone0
SPMB 0 Intake
SPMB 1 Intake
Routing Engine 0
Routing Engine 1
SFB 0 Intake-Zone0
SFB 0 Exhaust-Zone1
SFB 0 IntakeA-Zone0
SFB 0 IntakeB-Zone1
SFB 0 Exhaust-Zone0
SFB 0 SFB-XF2-Zone1
SFB 0 SFB-XF1-Zone0
SFB 0 SFB-XF0-Zone0
SFB 1 Intake-Zone0
SFB 1 Exhaust-Zone1
SFB 1 IntakeA-Zone0
SFB 1 IntakeB-Zone1
SFB 1 Exhaust-Zone0
SFB 1 SFB-XF2-Zone1
SFB 1 SFB-XF1-Zone0
SFB 1 SFB-XF0-Zone0
SFB 2 Intake-Zone0
SFB 2 Exhaust-Zone1
SFB 2 IntakeA-Zone0
SFB 2 IntakeB-Zone1
SFB 2 Exhaust-Zone0
SFB 2 SFB-XF2-Zone1
SFB 2 SFB-XF1-Zone0
SFB 2 SFB-XF0-Zone0
SFB 4 Intake-Zone0
SFB 4 Exhaust-Zone1
SFB 4 IntakeA-Zone0
OK
SFB 4 IntakeB-Zone1
SFB 4 Exhaust-Zone0
SFB 4 SFB-XF2-Zone1
Status
Measurement
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
Absent
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
SFB
SFB
SFB
SFB
SFB
SFB
SFB
SFB
SFB
SFB
SFB
SFB
SFB
SFB
SFB
SFB
SFB
SFB
SFB
SFB
SFB
SFB
SFB
SFB
SFB
SFB
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC 1 PLX
FPC
4 SFB-XF1-Zone0
4 SFB-XF0-Zone0
5 Intake-Zone0
5 Exhaust-Zone1
5 IntakeA-Zone0
5 IntakeB-Zone1
5 Exhaust-Zone0
5 SFB-XF2-Zone1
5 SFB-XF1-Zone0
5 SFB-XF0-Zone0
6 Intake-Zone0
6 Exhaust-Zone1
6 IntakeA-Zone0
6 IntakeB-Zone1
6 Exhaust-Zone0
6 SFB-XF2-Zone1
6 SFB-XF1-Zone0
6 SFB-XF0-Zone0
7 Intake-Zone0
7 Exhaust-Zone1
7 IntakeA-Zone0
7 IntakeB-Zone1
7 Exhaust-Zone0
7 SFB-XF2-Zone1
7 SFB-XF1-Zone0
7 SFB-XF0-Zone0
0 Intake
0 Exhaust A
0 Exhaust B
0 LU 0 TSen
0 LU 0 Chip
0 LU 1 TSen
0 LU 1 Chip
0 LU 2 TSen
0 LU 2 Chip
0 LU 3 TSen
0 LU 3 Chip
0 XM 0 TSen
0 XM 0 Chip
0 XM 1 TSen
0 XM 1 Chip
0 PLX Switch TSen
0 PLX Switch Chip
1 Intake
1 Exhaust A
1 Exhaust B
1 LU 0 TSen
1 LU 0 Chip
1 LU 1 TSen
1 LU 1 Chip
1 LU 2 TSen
1 LU 2 Chip
1 LU 3 TSen
1 LU 3 Chip
1 XM 0 TSen
1 XM 0 Chip
1 XF 0 TSen
1 XF 0 Chip
1 PLX Switch TSen
Switch Chip
2 Intake
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
421
FPC 2 Exhaust A
FPC 2 Exhaust B
FPC 2 LU 0 TSen
FPC 2 LU 0 Chip
FPC 2 LU 1 TSen
FPC 2 LU 1 Chip
FPC 2 LU 2 TSen
FPC 2 LU 2 Chip
FPC 2 LU 3 TSen
FPC 2 LU 3 Chip
FPC 2 XM 0 TSen
FPC 2 XM 0 Chip
FPC 2 XM 1 TSen
FPC 2 XM 1 Chip
FPC 2 PLX Switch
FPC 2 PLX Switch
FPC 3 Intake
FPC 3 Exhaust A
FPC 3 Exhaust B
FPC 3 LU 0 TSen
FPC 3 LU 0 Chip
FPC 3 LU 1 TSen
FPC 3 LU 1 Chip
FPC 3 LU 2 TSen
FPC 3 LU 2 Chip
FPC 3 LU 3 TSen
FPC 3 LU 3 Chip
FPC 3 MQ 0 TSen
FPC 3 MQ 0 Chip
FPC 3 MQ 1 TSen
FPC 3 MQ 1 Chip
FPC 3 MQ 2 TSen
FPC 3 MQ 2 Chip
FPC 3 MQ 3 TSen
FPC 3 MQ 3 Chip
FPC 4 Intake
FPC 4 Exhaust A
FPC 4 Exhaust B
FPC 4 LU 0 TSen
FPC 4 LU 0 Chip
FPC 4 LU 1 TSen
FPC 4 LU 1 Chip
FPC 4 LU 2 TSen
FPC 4 LU 2 Chip
FPC 4 LU 3 TSen
FPC 4 LU 3 Chip
FPC 4 XM 0 TSen
FPC 4 XM 0 Chip
FPC 4 XF 0 TSen
FPC 4 XF 0 Chip
FPC 4 PLX Switch
FPC 4 PLX Switch
FPC 5 Intake
FPC 5 Exhaust A
FPC 5 Exhaust B
FPC 5 LU 0 TSen
FPC 5 LU 0 Chip
FPC 5 LU 1 TSen
FPC 5 LU 1 Chip
FPC 5 LU 2 TSen
FPC 5 LU 2 Chip
422
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
TSen
Chip
TSen
Chip
OK
OK
OK
OK
OK
OK
OK
10 degrees C
10 degrees C
26 degrees C
25 degrees C
26 degrees C
26 degrees C
26 degrees C
17 degrees C
26 degrees C
22 degrees C
26 degrees C
34 degrees C
26 degrees C
26 degrees C
26 degrees C
20 degrees C
12 degrees C
16 degrees C
26 degrees C
23 degrees C
26 degrees C
23 degrees C
27 degrees C
23 degrees C
22 degrees C
23 degrees C
21 degrees C
15 degrees C
18 degrees C
15 degrees C
20 degrees C
15 degrees C
17 degrees C
15 degrees C
16 degrees C
11 degrees C
22 degrees C
28 degrees C
22 degrees C
33 degrees C
22 degrees C
21 degrees C
22 degrees C
26 degrees C
22 degrees C
33 degrees C
22 degrees C
30 degrees C
22 degrees C
37 degrees C
22 degrees C
23 degrees C
12 degrees C
12 degrees C
12 degrees C / 53
27 degrees C
28 degrees C
27 degrees C
27 degrees C
27 degrees C
19 degrees C
/ 50 degrees
/ 50 degrees
/ 78 degrees
/ 77 degrees
/ 78 degrees
/ 78 degrees
/ 78 degrees
/ 62 degrees
/ 78 degrees
/ 71 degrees
/ 78 degrees
/ 93 degrees
/ 78 degrees
/ 78 degrees
/ 78 degrees
/ 68 degrees
/ 53 degrees
/ 60 degrees
/ 78 degrees
/ 73 degrees
/ 78 degrees
/ 73 degrees
/ 80 degrees
/ 73 degrees
/ 71 degrees
/ 73 degrees
/ 69 degrees
/ 59 degrees
/ 64 degrees
/ 59 degrees
/ 68 degrees
/ 59 degrees
/ 62 degrees
/ 59 degrees
/ 60 degrees
/ 51 degrees
/ 71 degrees
/ 82 degrees
/ 71 degrees
/ 91 degrees
/ 71 degrees
/ 69 degrees
/ 71 degrees
/ 78 degrees
/ 71 degrees
/ 91 degrees
/ 71 degrees
/ 86 degrees
/ 71 degrees
/ 98 degrees
/ 71 degrees
/ 73 degrees
/ 53 degrees
/ 53 degrees
degrees F
/ 80 degrees
/ 82 degrees
/ 80 degrees
/ 80 degrees
/ 80 degrees
/ 66 degrees
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
F
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC 8 LU
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
5
5
5
5
5
5
5
5
6
6
6
6
6
6
6
6
6
6
6
6
6
6
6
6
6
6
6
7
7
7
7
7
7
7
7
7
7
7
7
7
7
7
7
7
8
8
8
8
8
1
8
8
8
8
8
8
8
8
8
8
8
LU 3 TSen
LU 3 Chip
XM 0 TSen
XM 0 Chip
XM 1 TSen
XM 1 Chip
PLX Switch
PLX Switch
Intake
Exhaust A
Exhaust B
LU 0 TSen
LU 0 Chip
LU 1 TSen
LU 1 Chip
LU 2 TSen
LU 2 Chip
LU 3 TSen
LU 3 Chip
MQ 0 TSen
MQ 0 Chip
MQ 1 TSen
MQ 1 Chip
MQ 2 TSen
MQ 2 Chip
MQ 3 TSen
MQ 3 Chip
Intake
Exhaust A
Exhaust B
LU 0 TSen
LU 0 Chip
LU 1 TSen
LU 1 Chip
LU 2 TSen
LU 2 Chip
LU 3 TSen
LU 3 Chip
XM 0 TSen
XM 0 Chip
XM 1 TSen
XM 1 Chip
PLX Switch
PLX Switch
Intake
Exhaust A
Exhaust B
LU 0 TSen
LU 0 Chip
TSen
LU 1 Chip
LU 2 TSen
LU 2 Chip
LU 3 TSen
LU 3 Chip
XM 0 TSen
XM 0 Chip
XF 0 TSen
XF 0 Chip
PLX Switch
PLX Switch
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
TSen
Chip
TSen
Chip
OK
TSen
Chip
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
27 degrees C
22 degrees C
27 degrees C
36 degrees C
27 degrees C
26 degrees C
27 degrees C
24 degrees C
12 degrees C
17 degrees C
28 degrees C
24 degrees C
29 degrees C
24 degrees C
30 degrees C
24 degrees C
24 degrees C
24 degrees C
22 degrees C
16 degrees C
19 degrees C
16 degrees C
20 degrees C
16 degrees C
17 degrees C
16 degrees C
16 degrees C
10 degrees C
10 degrees C
11 degrees C
26 degrees C
26 degrees C
26 degrees C
29 degrees C
26 degrees C
19 degrees C
26 degrees C
24 degrees C
26 degrees C
34 degrees C
26 degrees C
32 degrees C
26 degrees C
22 degrees C
10 degrees C
22 degrees C
28 degrees C
20 degrees C
33 degrees C
20 degrees C / 68
23 degrees C
20 degrees C
26 degrees C
20 degrees C
33 degrees C
20 degrees C
29 degrees C
20 degrees C
38 degrees C
20 degrees C
24 degrees C
/ 80 degrees F
/ 71 degrees F
/ 80 degrees F
/ 96 degrees F
/ 80 degrees F
/ 78 degrees F
/ 80 degrees F
/ 75 degrees F
/ 53 degrees F
/ 62 degrees F
/ 82 degrees F
/ 75 degrees F
/ 84 degrees F
/ 75 degrees F
/ 86 degrees F
/ 75 degrees F
/ 75 degrees F
/ 75 degrees F
/ 71 degrees F
/ 60 degrees F
/ 66 degrees F
/ 60 degrees F
/ 68 degrees F
/ 60 degrees F
/ 62 degrees F
/ 60 degrees F
/ 60 degrees F
/ 50 degrees F
/ 50 degrees F
/ 51 degrees F
/ 78 degrees F
/ 78 degrees F
/ 78 degrees F
/ 84 degrees F
/ 78 degrees F
/ 66 degrees F
/ 78 degrees F
/ 75 degrees F
/ 78 degrees F
/ 93 degrees F
/ 78 degrees F
/ 89 degrees F
/ 78 degrees F
/ 71 degrees F
/ 50 degrees F
/ 71 degrees F
/ 82 degrees F
/ 68 degrees F
/ 91 degrees F
degrees F
/ 73 degrees F
/ 68 degrees F
/ 78 degrees F
/ 68 degrees F
/ 91 degrees F
/ 68 degrees F
/ 84 degrees F
/ 68 degrees F
/ 100 degrees F
/ 68 degrees F
/ 75 degrees F
423
FPC 9 Intake
FPC 9 Exhaust A
FPC 9 Exhaust B
FPC 9 LU 0 TSen
FPC 9 LU 0 Chip
FPC 9 LU 1 TSen
FPC 9 LU 1 Chip
FPC 9 LU 2 TSen
FPC 9 LU 2 Chip
FPC 9 LU 3 TSen
FPC 9 LU 3 Chip
FPC 9 XM 0 TSen
FPC 9 XM 0 Chip
FPC 9 XM 1 TSen
FPC 9 XM 1 Chip
FPC 9 PLX Switch TSen
FPC 9 PLX Switch Chip
ADC 0 Intake
ADC 0 Exhaust
ADC 0 ADC-XF1
ADC 0 ADC-XF0
ADC 1 Intake
ADC 1 Exhaust
ADC 1 ADC-XF1
ADC 1 ADC-XF0
ADC 2 Intake
ADC 2 Exhaust
ADC 2 ADC-XF1
ADC 2 ADC-XF0
ADC 3 Intake
ADC 3 Exhaust
ADC 3 ADC-XF1
ADC 3 ADC-XF0
ADC 4 Intake
ADC 4 Exhaust
ADC 4 ADC-XF1
ADC 4 ADC-XF0
ADC 5 Intake
ADC 5 Exhaust
ADC 5 ADC-XF1
ADC 5 ADC-XF0
ADC 6 Intake
ADC 6 Exhaust
ADC 6 ADC-XF1
ADC 6 ADC-XF0
ADC 7 Intake
ADC 7 Exhaust
ADC 7 ADC-XF1
ADC 7 ADC-XF0
ADC 8 Intake
ADC 8 Exhaust
ADC 8 ADC-XF1
ADC 8 ADC-XF0
ADC 9 Intake
ADC 9 Exhaust
ADC 9 ADC-XF1
ADC 9 ADC-XF0
Fans Fan Tray 0 Fan 1
Fan Tray 0 Fan 2
Fan Tray 0 Fan 3
Fan Tray 0 Fan 4
424
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
3480 RPM
3480 RPM
3480 RPM
3360 RPM
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
show chassis
environment (T320
Router)
Tray
Tray
Tray
Tray
Tray
Tray
Tray
Tray
Tray
Tray
Tray
Tray
Tray
Tray
Tray
Tray
Tray
Tray
Tray
Tray
0
0
1
1
1
1
1
1
2
2
2
2
2
2
3
3
3
3
3
3
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
5
6
1
2
3
4
5
6
1
2
3
4
5
6
1
2
3
4
5
6

Class Item
Status
Power PEM 0
OK
PEM 1
Absent
Temp SCG 0
OK
SCG 1
OK
Routing Engine 0
OK
Routing Engine 1
OK
CB 0
OK
CB 1
OK
SIB 0
OK
SIB 1
OK
SIB 2
OK
FPC 0 Top
OK
FPC 0 Bottom
OK
FPC 1 Top
OK
FPC 1 Bottom
OK
FPC 2 Top
OK
FPC 2 Bottom
OK
FPM GBUS
OK
FPM Display
OK
Fans Top Left Front fan
OK
Top Left Middle fan
OK
Top Left Rear fan
OK
Top Right Front fan
OK
Top Right Middle fan
OK
Top Right Rear fan
OK
Bottom Left Middle fan OK
OK
Bottom Right Middle fan OK
Rear Tray Top fan
OK
Rear Tray Second fan
OK
Rear Tray Middle fan
OK
Rear Tray Fourth fan
OK
Rear Tray Bottom fan
OK
Misc CIP
OK
SPMB 0
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
3360
3480
3360
3360
3360
3480
3480
3480
3360
3360
3480
3480
3360
3480
3360
3360
3480
3480
3480
3360
RPM
RPM
RPM
RPM
RPM
RPM
RPM
RPM
RPM
RPM
RPM
RPM
RPM
RPM
RPM
RPM
RPM
RPM
RPM
RPM
Measurement
425
SPMB 1
show chassis
environment (T640
Router)
show chassis
environment (T4000
Router)
426
OK

Class Item
Status
Temp PEM 0
Absent
PEM 1
OK
SCG 0
OK
SCG 1
OK
Routing Engine 0
Present
Routing Engine 1
OK
CB 0
Present
CB 1
OK
SIB 0
Absent
SIB 1
Absent
SIB 2
Absent
SIB 3
Absent
SIB 4
Absent
FPC 4 Top
Testing
FPC 4 Bottom
Testing
FPC 5 Top
Testing
FPC 5 Bottom
Testing
FPC 6 Top
Testing
FPC 6 Bottom
Testing
FPM GBUS
OK
FPM Display
Absent
OK
Top Left Middle fan
OK
Top Left Rear fan
OK
Top Right Front fan
OK
OK
Top Right Rear fan
OK
OK
Fourth Blower from top OK
Bottom Blower
OK
Middle Blower
OK
Top Blower
OK
Second Blower from top OK
Misc CIP
OK
SPMB 0
OK
SPMB 1
OK

Class Item
Temp PEM 0
PEM 1
SCG 0
SCG 1
Routing Engine 0
Routing Engine 1
CB 0
CB 1
Measurement
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
Status
OK
Absent
OK
OK
OK
OK
OK
OK
OK
OK
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
normal
normal
normal
normal
normal
normal
normal
normal
normal
normal
normal
normal
normal
normal
normal
normal
normal
speed
speed
speed
speed
speed
speed
speed
speed
speed
speed
speed
speed
speed
speed
speed
speed
speed
Measurement
33
33
33
50
32
46
32
33
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
C
C
C
C
C
C
C
C
/
/
/
/
/
/
/
/
91 degrees F
91 degrees F
91 degrees F
122 degrees F
89 degrees F
114 degrees F
89 degrees F
91 degrees F
Fans
SIB
SIB
SIB
SIB
SIB
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPM
FPM
Top
Top
Top
Top
0
1
2
3
4
0 Fan Intake
0 Fan Exhaust
0 PMB
0 LMB0
0 LMB1
0 LMB2
0 PFE1 LU2
0 PFE1 LU0
0 PFE0 LU0
0 XF1
0 XF0
0 XM1
0 XM0
0 PFE0 LU1
0 PFE0 LU2
0 PFE1 LU1
3 Fan Intake
3 Fan Exhaust
3 PMB
3 LMB0
3 LMB1
3 LMB2
3 PFE1 LU2
3 PFE1 LU0
3 PFE0 LU0
3 XF1
3 XF0
3 XM1
3 XM0
3 PFE0 LU1
3 PFE0 LU2
3 PFE1 LU1
5 Top
5 Bottom
6 Fan Intake
6 Fan Exhaust
6 PMB
6 LMB0
6 LMB1
6 LMB2
6 PFE1 LU2
6 PFE1 LU0
6 PFE0 LU0
6 XF1
6 XF0
6 XM1
6 XM0
6 PFE0 LU1
6 PFE0 LU2
6 PFE1 LU1
GBUS
Display
Left Front fan
Left Middle fan
Left Rear fan
Right Front fan
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK

Spinning at high speed
427
Misc
show chassis
environment (TX
Matrix Router)

Top Right Rear fan
Bottom Left Front fan
Bottom Left Middle fan
Bottom Right Front fan
Bottom Right Middle fan
Bottom Right Rear fan
Rear Tray Top fan
Rear Tray Third fan
Rear Tray Fifth fan
Rear Tray Sixth fan
Rear Tray Seventh fan
CIP
SPMB 0
SPMB 1
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
high
high
high
high
high
high
high
high
high
high
high
high
high
high
high
high
speed
speed
speed
speed
speed
speed
speed
speed
speed
speed
speed
speed
speed
speed
speed
speed

scc-re0:
-------------------------------------------------------------------------Class Item
Status
Measurement
Temp PEM 0
Absent
PEM 1
OK
Routing Engine 0
OK
Routing Engine 1
OK
CB 0
OK
CB 1
OK
SIB 0
OK
SIB 0 (B)
OK
FPM GBUS
OK
FPM Display
OK
OK
Top Left Middle fan
OK
Top Left Rear fan
OK
Top Right Front fan
OK
OK
Top Right Rear fan
OK
OK
Rear Tray Top fan
OK
OK
Rear Tray Third fan
OK
OK
Rear Tray Fifth fan
OK
Rear Tray Sixth fan
OK
Rear Tray Seventh fan OK
OK
Misc CIP 0
OK
CIP 1
OK
SPMB 0
OK
SPMB 1
OK
lcc0-re0:
--------------------------------------------------------------------------
428
Class Item
Status
Temp PEM 0
OK
PEM 1
Absent
SCG 0
OK
SCG 1
Absent
Routing Engine 0
OK
Routing Engine 1
OK
CB 0
OK
CB 1
OK
SIB 0
OK
SIB 0 (B)
OK
FPC 0 Top
OK
FPC 0 Bottom
OK
FPC 1 Top
OK
FPC 1 Bottom
OK
FPM GBUS
OK
FPM Display
OK
OK
Top Left Middle fan
OK
Top Left Rear fan
OK
Top Right Front fan
OK
OK
Top Right Rear fan
OK
OK
Rear Tray Top fan
OK
OK
Rear Tray Third fan
OK
OK
Rear Tray Fifth fan
OK
Rear Tray Sixth fan
OK
Rear Tray Seventh fan OK
OK
Misc CIP
OK
SPMB 0
OK
SPMB 1
OK
Measurement
lcc2-re0:
-------------------------------------------------------------------------Class Item
Status
Measurement
Temp PEM 0
OK
PEM 1
Absent
SCG 0
OK
SCG 1
Absent
Routing Engine 0
OK
Routing Engine 1
OK
CB 0
OK
SIB 0
OK
SIB 0 (B)
OK
FPC 0 Top
OK
FPC 0 Bottom
OK
FPC 1 Top
OK
FPC 1 Bottom
OK
FPM GBUS
OK
FPM Display
OK
OK
Top Left Middle fan
OK
429
...
show chassis
environment (T1600
Router)
show chassis
environment (TX
Matrix Plus Router)
430

Class Item
Temp PEM 0
PEM 1
SCG 0
SCG 1
Routing Engine 0
Routing Engine 1
CB 0
CB 1
SIB 0
SIB 0 (B)
SIB 1
SIB 1 (B)
SIB 2
SIB 2 (B)
SIB 3
SIB 3 (B)
SIB 4
SIB 4 (B)
FPC 0 Top
FPC 0 Bottom
FPC 1 Top
FPC 1 Bottom
FPM GBUS
FPM Display
Top Left Middle fan
Top Left Rear fan
Top Right Front fan
Top Right Rear fan
Rear Tray Top fan
Rear Tray Third fan
Rear Tray Fifth fan
Rear Tray Sixth fan
Rear Tray Seventh fan
Misc CIP
SPMB 0
SPMB 1
Status
OK
Absent
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
Measurement

sfc0-re0:
-------------------------------------------------------------------------Class Item
Status
Measurement
Temp PEM 0
OK
PEM 1
Absent
Routing Engine 0
OK
Routing Engine 1
OK
Fans
CB 0 Intake
CB 0 Exhaust A
CB 0 Exhaust B
CB 1 Intake
CB 1 Exhaust A
CB 1 Exhaust B
SIB F13 0
SIB F13 0 (B)
SIB F13 1
SIB F13 1 (B)
SIB F2S 0/0
SIB F2S 0/2
SIB F2S 0/4
SIB F2S 0/6
SIB F2S 1/0
SIB F2S 1/2
SIB F2S 1/4
SIB F2S 1/6
SIB F2S 2/0
SIB F2S 2/2
SIB F2S 2/4
CIP 0 Intake
CIP 0 Exhaust A
CIP 0 Exhaust B
CIP 1 Intake
CIP 1 Exhaust A
CIP 1 Exhaust B
Fan Tray 0 Fan 1
Fan Tray 0 Fan 2
Fan Tray 0 Fan 3
Fan Tray 0 Fan 4
Fan Tray 0 Fan 5
Fan Tray 0 Fan 6
Fan Tray 1 Fan 1
Fan Tray 1 Fan 2
Fan Tray 1 Fan 3
Fan Tray 1 Fan 4
Fan Tray 1 Fan 5
Fan Tray 1 Fan 6
Fan Tray 2 Fan 1
Fan Tray 2 Fan 2
Fan Tray 2 Fan 3
Fan Tray 2 Fan 4
Fan Tray 2 Fan 5
Fan Tray 2 Fan 6
Fan Tray 2 Fan 7
Fan Tray 2 Fan 8
Fan Tray 2 Fan 9
Fan Tray 3 Fan 1
Fan Tray 3 Fan 2
Fan Tray 3 Fan 3
Fan Tray 3 Fan 4
Fan Tray 3 Fan 5
Fan Tray 3 Fan 6
Fan Tray 3 Fan 7
Fan Tray 3 Fan 8
Fan Tray 3 Fan 9
Fan Tray 4 Fan 1
Fan Tray 4 Fan 2
Fan Tray 4 Fan 3
Fan Tray 4 Fan 4
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
431
Misc
Fan Tray
Fan Tray
Fan Tray
Fan Tray
Fan Tray
Fan Tray
Fan Tray
Fan Tray
Fan Tray
Fan Tray
Fan Tray
Fan Tray
Fan Tray
Fan Tray
SPMB 0
SPMB 1
4
4
4
4
4
5
5
5
5
5
5
5
5
5
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
5
6
7
8
9
1
2
3
4
5
6
7
8
9
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
at
at
at
at
at
at
at
at
at
at
at
at
at
at
normal
normal
normal
normal
normal
normal
normal
normal
normal
normal
normal
normal
normal
normal
speed
speed
speed
speed
speed
speed
speed
speed
speed
speed
speed
speed
speed
speed
lcc0-re0:
-------------------------------------------------------------------------Class Item
Status
Measurement
Temp PEM 0
OK
PEM 1
Absent
SCG 0
OK
SCG 1
OK
Routing Engine 0
OK
Routing Engine 1
OK
CB 0
OK
CB 1
OK
SIB 0
OK
SIB 0 (B)
OK
SIB 1
OK
SIB 1 (B)
OK
SIB 2
OK
SIB 2 (B)
OK
SIB 3
OK
SIB 3 (B)
OK
SIB 4
OK
SIB 4 (B)
OK
FPC 0 Top
OK
FPC 0 Bottom
OK
FPC 1 Top
OK
FPC 1 Bottom
OK
FPM GBUS
OK
FPM Display
OK
OK
Top Left Middle fan
OK
Top Left Rear fan
OK
Top Right Front fan
OK
OK
Top Right Rear fan
OK
OK
OK
OK
OK
OK
OK
Rear Tray Top fan
OK
OK
Rear Tray Third fan
OK
OK
Rear Tray Fifth fan
OK
432
OK
OK
OK
OK
OK
OK

user@switch> show chassis environment

Class Item
Power FPC 0 Power Supply 0
FPC 0 Power Supply 1
Temp FPC 0 CPU
FPC 0 EX-PFE1
FPC 0 EX-PFE2
FPC 0 GEPHY Front Left
FPC 0 GEPHY Front Right
FPC 0 Uplink Conn
Fans FPC 0 Fan 1
FPC 0 Fan 2
FPC 0 Fan 3
Status
OK
Absent
OK
OK
OK
OK
OK
OK
OK
OK
OK
Measurement

Class Item
Power PSU 0
PSU 1
PSU 2
PSU 3
PSU 4
PSU 5
Temp CB 0 Intake
CB 0 Exhaust
CB 1 Intake
CB 1 Exhaust
FPC 4 Intake
FPC 4 Exhaust
SIB 5 Intake
SIB 5 Exhaust
SIB 6 Intake
SIB 6 Exhaust
Fans Top Fan 1
Top Fan 2
Top Fan 3
Top Fan 4
Top Fan 5
Top Fan 6
Top Fan 7
Top Fan 8
Top Fan 9
Bottom Fan 1
Bottom Fan 2
Bottom Fan 3
Bottom Fan 4
Bottom Fan 5
Bottom Fan 6
Bottom Fan 7
Bottom Fan 8
Bottom Fan 9
Status
OK
OK
OK
Check
Absent
Absent
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
Measurement
Misc
show chassis
environment (EX4200
Standalone Switch)
show chassis
environment (EX8216
Switch)
Rear
Rear
Rear
CIP
SPMB
SPMB
Tray Sixth fan

Tray Seventh fan
Tray Bottom fan
0
1

433
show chassis
environment (QFX
Series)
show chassis
environment
434
Class Item
Power FPC 0
FPC 0
Temp FPC 0
FPC 0
FPC 0
FPC 0
FPC 0
FPC 0
FPC 0
FPC 0
FPC 0
FPC 0
FPC 0
Fans FPC 0
FPC 0
FPC 0
Power Supply 0
Power Supply 1
Sensor TopLeft I
Sensor TopRight I
Sensor TopLeft E
Sensor TopRight E
Sensor TopMiddle I
Sensor TopMiddle E
Sensor Bottom I
Sensor Bottom E
Sensor Die Temp
Sensor Mgmnt Brd I
Sensor Switch I
Fan 1 (left)
Fan 2 (right)
Fan 3 (middle)
Status
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
Failed
OK
OK
Measurement
26
24
30
30
30
38
34
38
38
24
28
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
C
C
C
C
C
C
C
C
C
C
C
/
/
/
/
/
/
/
/
/
/
/
78 degrees F
75 degrees F
86 degrees F
86 degrees F
86 degrees F
100 degrees F
93 degrees F
100 degrees F
100 degrees F
75 degrees F
82 degrees F

user@switch> show chassis environment interconnect-device IC-A0004

Class Item
Status
Measurement
CB 0
interconnect-device
(QFabric System)
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
CB 0 L Intake
CB 0 R Intake
CB 0 L Exhaust
CB 0 R Exhaust
Routing Engine 0 CPU temp
CB 1
CB 1 L Intake
CB 1 R Intake
CB 1 L Exhaust
CB 1 R Exhaust
Routing Engine 1 CPU temp
FC 0 FPC 0
FPC 0 L Intake
FPC 0 R Intake
FPC 0 L Exhaust
FPC 0 R Exhaust
FC 7 FPC 7
FPC 7 L Intake
FPC 7 R Intake
FPC 7 L Exhaust
FPC 7 R Exhaust
RC 0 FPC 8
FPC 8 L Intake
FPC 8 R Intake
FPC 8 L Exhaust
FPC 8 R Exhaust
RC 7 FPC 15
FPC 15 L Intake
FPC 15 R Intake
FPC 15 L Exhaust
FPC 15 R Exhaust
TFT 0 Fan 0
TFT 0 Fan 1
TFT 0 Fan 2
TFT 0 Fan 3
TFT 0 Fan 4
TFT 0 Fan 5
BFT 1 Fan 0
BFT 1 Fan 1
BFT 1 Fan 2
BFT 1 Fan 3
BFT 1 Fan 4
BFT 1 Fan 5
SFT 0 Fan 0 Rotor 0
SFT 0 Fan 0 Rotor 1
SFT 0 Fan 1 Rotor 0
SFT 0 Fan 1 Rotor 1
SFT 0 Fan 2 Rotor 0
SFT 0 Fan 2 Rotor 1
SFT 0 Fan 3 Rotor 0
SFT 0 Fan 3 Rotor 1
SFT 1 Fan 0 Rotor 0
SFT 1 Fan 0 Rotor 1
SFT 1 Fan 1 Rotor 0
SFT 1 Fan 1 Rotor 1
SFT 1 Fan 2 Rotor 0
SFT 1 Fan 2 Rotor 1
SFT 1 Fan 3 Rotor 0
SFT 1 Fan 3 Rotor 1
SFT 2 Fan 0 Rotor 0
SFT 2 Fan 0 Rotor 1
OK
OK
OK
OK
OK
30
31
32
33
51
degrees
degrees
degrees
degrees
degrees
C
C
C
C
C
/
/
/
/
/
86 degrees F
87 degrees F
89 degrees F
91 degrees F
123 degrees F
OK
OK
OK
OK
OK
27
29
31
32
40
degrees
degrees
degrees
degrees
degrees
C
C
C
C
C
/
/
/
/
/
80 degrees F
84 degrees F
87 degrees F
89 degrees F
104 degrees F
OK
OK
OK
OK
25
28
28
29
degrees
degrees
degrees
degrees
C
C
C
C
/
/
/
/
77
82
82
84
degrees
degrees
degrees
degrees
F
F
F
F
OK
OK
OK
OK
25
26
28
29
degrees
degrees
degrees
degrees
C
C
C
C
/
/
/
/
77
78
82
84
degrees
degrees
degrees
degrees
F
F
F
F
OK
OK
OK
OK
25
26
32
30
degrees
degrees
degrees
degrees
C
C
C
C
/
/
/
/
77
78
89
86
degrees
degrees
degrees
degrees
F
F
F
F
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
Check
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
F
F
F
F
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
Spinning
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
normal
normal
normal
normal
normal
normal
normal
normal
normal
normal
normal
normal
normal
normal
normal
normal
normal
normal
normal
normal
speed
speed
speed
speed
speed
speed
speed
speed
speed
speed
speed
speed
speed
speed
speed
speed
speed
speed
speed
speed
435
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Fans
Power
Power
Power
Power
Power
Power
show chassis
environment
436
SFT
SFT
SFT
SFT
SFT
SFT
SFT
SFT
SFT
SFT
SFT
SFT
SFT
SFT
SFT
SFT
SFT
SFT
SFT
SFT
SFT
SFT
SFT
SFT
SFT
SFT
SFT
SFT
SFT
SFT
SFT
SFT
SFT
SFT
SFT
SFT
SFT
SFT
SFT
SFT
SFT
SFT
SFT
SFT
SFT
SFT
PEM
PEM
PEM
PEM
PEM
PEM
2
2
2
2
2
2
3
3
3
3
3
3
3
3
4
4
4
4
4
4
4
4
5
5
5
5
5
5
5
5
6
6
6
6
6
6
6
6
7
7
7
7
7
7
7
7
0
1
2
3
4
5
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
Fan
1
1
2
2
3
3
0
0
1
1
2
2
3
3
0
0
1
1
2
2
3
3
0
0
1
1
2
2
3
3
0
0
1
1
2
2
3
3
0
0
1
1
2
2
3
3
Rotor
Rotor
Rotor
Rotor
Rotor
Rotor
Rotor
Rotor
Rotor
Rotor
Rotor
Rotor
Rotor
Rotor
Rotor
Rotor
Rotor
Rotor
Rotor
Rotor
Rotor
Rotor
Rotor
Rotor
Rotor
Rotor
Rotor
Rotor
Rotor
Rotor
Rotor
Rotor
Rotor
Rotor
Rotor
Rotor
Rotor
Rotor
Rotor
Rotor
Rotor
Rotor
Rotor
Rotor
Rotor
Rotor
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
0
1
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
Absent
Absent
Absent

user@switch> show chassis environment node-device node1

Class Item
Status
Measurement
Power node1 Power Supply 0
Absent
node-device (QFabric
System)
Fans
node1
node1
node1
node1
Power Supply 1
Fan Tray 0
Fan Tray 1
Fan Tray 2
Absent
Testing
Testing
Testing
show chassis
environment pem
System)
user@switch> show chassis environment pem node-device node1

FPC 0 PEM 0 status:
State
Check
Airflow
Front to Back
Temperature
OK
AC Input:
OK
DC Output
Voltage(V) Current(A) Power(W) Load(%)
12
10
120
18
FPC 0 PEM 1 status:
State
Online
Airflow
Back to Front
Temperature
OK
AC Input:
OK
DC Output
Voltage(V) Current(A) Power(W) Load(%)
11
10
110
17
show chassis
environment

Class Item
Temp PDU 0
Status
OK
Measurement
437
(PTX5000 Packet
Transport Switch)
438
PDU 0 PSM 0
PDU 0 PSM 1
PDU 0 PSM 2
PDU 0 PSM 3
PDU 1
CCG 0
CCG 1
Routing Engine 0
Routing Engine 1
CB 0 Intake
CB 0 Exhaust A
CB 0 Exhaust B
CB 1 Intake
CB 1 Exhaust A
CB 1 Exhaust B
SIB 0 Intake
SIB 0 Exhaust
SIB 0 Junction
SIB 1 Intake
SIB 1 Exhaust
SIB 1 Junction
SIB 2 Intake
SIB 2 Exhaust
SIB 2 Junction
SIB 3 Intake
SIB 3 Exhaust
SIB 3 Junction
SIB 4 Intake
SIB 4 Exhaust
SIB 4 Junction
SIB 5 Intake
SIB 5 Exhaust
SIB 5 Junction
SIB 6 Intake
SIB 6 Exhaust
SIB 6 Junction
SIB 7 Intake
SIB 7 Exhaust
SIB 7 Junction
SIB 8 Intake
SIB 8 Exhaust
SIB 8 Junction
FPC 0 PMB
FPC 0 Intake
FPC 0 Exhaust A
FPC 0 Exhaust B
FPC 0 TL0
FPC 0 TQ0
FPC 0 TL1
FPC 0 TQ1
FPC 0 TL2
FPC 0 TQ2
FPC 0 TL3
FPC 0 TQ3
FPC 2 PMB
FPC 2 Intake
FPC 2 Exhaust A
FPC 2 Exhaust B
FPC 2 TL0
OK
OK
OK
OK
Absent
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
36
38
38
37
degrees
degrees
degrees
degrees
C
C
C
C
/
/
/
/
96 degrees F
100 degrees F
100 degrees F
98 degrees F
44
44
62
75
51
64
38
46
42
35
39
36
39
37
43
39
36
46
37
37
42
40
40
45
47
44
58
58
43
71
57
42
65
58
42
66
57
42
70
35
33
51
43
48
53
56
58
55
56
59
59
35
34
51
52
53
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
111 degrees F
111 degrees F
143 degrees F
167 degrees F
123 degrees F
147 degrees F
100 degrees F
114 degrees F
107 degrees F
95 degrees F
102 degrees F
96 degrees F
102 degrees F
98 degrees F
109 degrees F
102 degrees F
96 degrees F
114 degrees F
98 degrees F
98 degrees F
107 degrees F
104 degrees F
104 degrees F
113 degrees F
116 degrees F
111 degrees F
136 degrees F
136 degrees F
109 degrees F
159 degrees F
134 degrees F
107 degrees F
149 degrees F
136 degrees F
107 degrees F
150 degrees F
134 degrees F
107 degrees F
158 degrees F
95 degrees F
91 degrees F
123 degrees F
109 degrees F
118 degrees F
127 degrees F
132 degrees F
136 degrees F
131 degrees F
132 degrees F
138 degrees F
138 degrees F
95 degrees F
93 degrees F
123 degrees F
125 degrees F
127 degrees F
FPC
FPC
FPC
FPC
FPC
FPC
FPC
PIC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
PIC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
PIC
PIC
PIC
PIC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
2 TQ0
2 TL1
2 TQ1
2 TL2
2 TQ2
2 TL3
2 TQ3
2/0 Ambient
3 PMB
3 Intake
3 Exhaust A
3 Exhaust B
3 TL0
3 TQ0
3 TL1
3 TQ1
3 TL2
3 TQ2
3 TL3
3 TQ3
3/1
5 PMB
5 Intake
5 Exhaust A
5 Exhaust B
5 TL0
5 TQ0
5 TL1
5 TQ1
5 TL2
5 TQ2
5 TL3
5 TQ3
5/0 Ambient
5/1 Ambient
5/1 cfp-5/1/0
5/1 cfp-5/1/1
6 PMB
6 Intake
6 Exhaust A
6 Exhaust B
6 TL0
6 TQ0
6 TL1
6 TQ1
6 TL2
6 TQ2
6 TL3
6 TQ3
7 PMB
7 Intake
7 Exhaust A
7 Exhaust B
7 TL0
7 TQ0
7 TL1
7 TQ1
7 TL2
7 TQ2
7 TL3
7 TQ3
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
Absent
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
53
57
58
54
59
60
64
49
34
35
54
49
49
55
56
58
56
59
62
63
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
127 degrees F
134 degrees F
136 degrees F
129 degrees F
138 degrees F
140 degrees F
147 degrees F
120 degrees F
93 degrees F
95 degrees F
129 degrees F
120 degrees F
120 degrees F
131 degrees F
132 degrees F
136 degrees F
132 degrees F
138 degrees F
143 degrees F
145 degrees F
35
34
51
53
54
52
61
60
55
55
59
58
51
34
34
36
36
33
51
39
44
54
59
58
60
57
65
60
35
33
53
40
46
58
53
59
56
61
63
63
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
degrees
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
/
95 degrees F
93 degrees F
123 degrees F
127 degrees F
129 degrees F
125 degrees F
141 degrees F
140 degrees F
131 degrees F
131 degrees F
138 degrees F
136 degrees F
123 degrees F
93 degrees F
93 degrees F
96 degrees F
96 degrees F
91 degrees F
123 degrees F
102 degrees F
111 degrees F
129 degrees F
138 degrees F
136 degrees F
140 degrees F
134 degrees F
149 degrees F
140 degrees F
95 degrees F
91 degrees F
127 degrees F
104 degrees F
114 degrees F
136 degrees F
127 degrees F
138 degrees F
132 degrees F
141 degrees F
145 degrees F
145 degrees F
439
Fans
Misc
FPM I2CS
Fan Tray 0 Fan
Fan Tray 0 Fan
Fan Tray 0 Fan
Fan Tray 0 Fan
Fan Tray 0 Fan
Fan Tray 0 Fan
Fan Tray 0 Fan
Fan Tray 0 Fan
Fan Tray 0 Fan
Fan Tray 0 Fan
Fan Tray 0 Fan
Fan Tray 0 Fan
Fan Tray 0 Fan
Fan Tray 0 Fan
Fan Tray 1 Fan
Fan Tray 1 Fan
Fan Tray 1 Fan
Fan Tray 1 Fan
Fan Tray 1 Fan
Fan Tray 1 Fan
Fan Tray 2 Fan
Fan Tray 2 Fan
Fan Tray 2 Fan
Fan Tray 2 Fan
Fan Tray 2 Fan
Fan Tray 2 Fan
SPMB 0 Intake
SPMB 1 Intake
1
2
3
4
5
6
7
8
9
10
11
12
13
14
1
2
3
4
5
6
1
2
3
4
5
6
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
3042 RPM
3042 RPM
3000 RPM
3042 RPM
3000 RPM
3042 RPM
3085 RPM
3042 RPM
3042 RPM
3085 RPM
3085 RPM
3128 RPM
3128 RPM
3042 RPM
2299 RPM
2399 RPM
2299 RPM
2266 RPM
2266 RPM
2366 RPM
2199 RPM
2133 RPM
2366 RPM
2233 RPM
2399 RPM
2233 RPM
Status
OK
OK
OK
OK
OK
OK
OK
Measurement
44 degrees C
50 degrees C
70 degrees C
63 degrees C
66 degrees C
65 degrees C
54 degrees C
show chassis
environment
(ACX2000 Universal
Access Router)

Class Item
PCB Left
SFP+ Xcvr
FEB
PCB Up
PCB Mid
Telecom Mod
Routing Engine
Heater off
show chassis
environment
On the ACX4000 router, the MIC output of the show chassis environment command
varies depending on the number of temperature channels present in the installed MIC.
440
/
/
/
/
/
/
/
111
122
158
145
150
149
129
degrees
degrees
degrees
degrees
degrees
degrees
degrees
F
F
F
F
F
F
F
(ACX4000 Universal
Access Router)

Class Item
Temp PEM 0
PEM 1
PCB Bottom
PCB Middle
BCM56445
SFP+ Xcvr
Fan tray inlet
Exhaust
Routing Engine
Heater off
Pic
PIC 0/0 Channel
PIC 0/0 Channel
PIC 0/0 Channel
PIC 0/0 Channel
PIC 0/0 Channel
PIC 0/0 Channel
PIC 0/0 Channel
PIC 0/0 Channel
PIC 0/0 Channel
PIC 0/0 Channel
PIC 1/0 Channel
PIC 1/0 Channel
PIC 1/0 Channel
PIC 1/0 Channel
PIC 1/0 Channel
PIC 1/0 Channel
PIC 1/0 Channel
PIC 1/0 Channel
PIC 1/0 Channel
PIC 1/1 Channel
PIC 1/1 Channel
PIC 1/1 Channel
PIC 1/1 Channel
PIC 1/1 Channel
PIC 1/1 Channel
PIC 1/1 Channel
PIC 1/1 Channel
PIC 1/1 Channel
Fans Fan 1
Fan 2
0
1
2
3
4
5
6
7
8
9
0
1
2
3
4
5
6
7
8
0
1
2
3
4
5
6
7
8
Status
OK
Absent
OK
OK
OK
OK
OK
OK
OK
Measurement
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
30
34
33
32
39
30
32
degrees
degrees
degrees
degrees
degrees
degrees
degrees
C
C
C
C
C
C
C
/
/
/
/
/
/
/
86 degrees F
93 degrees F
91 degrees F
89 degrees F
102 degrees F
86 degrees F
89 degrees F
441
show chassis feb

Syntax
show chassis feb
Release Information

Routers.
Description
(ACX Series routers, and M5, M10, and M120 routers only) Display Forwarding Engine
Board (FEB) status information.
Options
Required Privilege
Level
view
Related
Documentation
request chassis feb on page 339
show chassis fabric feb
feb
Switching Control Board Redundancy
show chassis feb (M10 Router) on page 444

show chassis feb (M120 Router) on page 444
show chassis feb detail (M120 Router) on page 444
show chassis feb detail (ACX2000 Universal Access Router) on page 445
show chassis feb detail (ACX1000 Universal Access Router) on page 445
Output Fields
Table 36 on page 442 lists the output fields for the show chassis feb command. Output
Table 36: show chassis feb

Field Name
Field Description
State
State of the FEB:
OfflineFEB is powered down.
OnlineFEB is operational and running.
CheckFEB is in alarmed state where the Switch Interface Board (SIB) plane is partially operational
for the following reasons:
Temp (C) or Intake

temperature
442
FEB is not inserted properly.
Two or more links between the FEB and Packet Forwarding Engine fail.
Temperature of the air passing by the FEB, in degrees Celsius or in both degrees Celsius and degrees
Fahrenheit.
Table 36: show chassis feb (continued)

Field Name
Field Description
CPU Utilization (%)
Percentage of CPU being used:
TotalTotal percentage of CPU being used by the FEB processor.
InterruptOf the total CPU being used by the FEB processor, the percentage being used for interrupts.
Memory DRAM (MB)
Total DRAM, in megabytes, available to the FEB processor.
Utilization (%)
Percentage of memory utilization:
HeapPercentage of heap space (dynamic memory) being used by the FEB processor. If this
number exceeds 80 percent, you might experience a software problem (memory leak).
BufferPercentage of buffer space being used by the FPC processor for buffering internal messages.
Exhaust A temperature
Temperature of the air flowing past Exhaust A.
Exhaust B temperature
Temperature of the air flowing past Exhaust B.
Total DDR DRAM
Amount of double data rate dynamic random access memory (DDR DRAM) available to the FEB CPU.
Total RLDRAM
Amount of reduced latency dynamic random access memory (RLDRAM) available to the FEB CPU.
Start time (Detail
Time when the Routing Engine detected that the FEB was running.
output only)
Uptime (Detail output
only)
How long the Routing Engine has been connected to the FEB, and therefore, how long the Flexible
PIC Concentrator (PIC) has been up and running.
443
Sample Output
show chassis feb (M10
Router)
user@host> show chassis feb

FEB status:
Temperature
CPU utilization
Interrupt utilization
Heap utilization
Buffer utilization
Total CPU DRAM
Internet Processor II
Start time:
Uptime:
27
3
0
26
50
64
degrees C / 80 degrees F
percent
percent
percent
percent
MB
Version 1, Foundry IBM, Part number 9
2010-05-23 13:59:51 PDT
6 hours, 33 minutes, 11 seconds
show chassis feb

(M120 Router)

Temp CPU Utilization (%)
Slot State
(C) Total Interrupt
0 Online
47
4
0
1 Online
54
3
0
2 Online
50
4
0
3 Online
49
4
0
4 Online
46
3
0
5 Online
35
3
0
show chassis feb detail

(M120 Router)
user@host> show chassis feb detail

Slot 0 information:
State
Intake temperature
Total DDR DRAM
Total RLDRAM
Start time:
Uptime:
Slot 1 information:
State
Intake temperature
Total DDR DRAM
Total RLDRAM
Start time:
Uptime:
Slot 2 information:
State
Intake temperature
Total DDR DRAM
Total RLDRAM
Start time:
Uptime:
Slot 3 information:
State
Intake temperature
Total DDR DRAM
444
48
51
52
512
32
55
46
45
512
32
50
47
47
512
32
49
47
49
512
Memory
Utilization (%)
DRAM (MB) Heap
Buffer
512
7
60
512
7
59
512
7
59
512
7
59
512
7
59
512
7
59
Online
MB
MB
2006-06-28 15:00:40 PDT
10 minutes, 21 seconds
Online
MB
MB
2006-06-28 15:00:33 PDT
Online
MB
MB
2006-06-28 15:00:35 PDT
Online
MB
Total RLDRAM
Start time:
Uptime:
Slot 4 information:
State
Intake temperature
Total DDR DRAM
Total RLDRAM
Start time:
Uptime:
Slot 5 information:
State
Intake temperature
Total DDR DRAM
Total RLDRAM
Start time:
Uptime:

(ACX2000 Universal
Access Router)

(ACX1000 Universal
Access Router)

FEB status:
Slot 0 information:
State
Temperature
CPU utilization
Heap utilization
Buffer utilization
Total CPU DRAM
Start time:
Uptime:

FEB status:
Slot 0 information:
State
Temperature
CPU utilization
Heap utilization
Buffer utilization
Total CPU DRAM
Start time:
Uptime:
32 MB
2006-06-28 15:00:43 PDT
45
42
42
512
32
35
33
40
512
32
72
17
7
20
37
512
46
15
5
45
37
256
Online
MB
MB
2006-06-28 15:00:29 PDT
Online
MB
MB
2006-06-28 15:00:27 PDT
Online
percent
percent
percent
percent
MB
2012-05-09 00:58:51 PDT
5 days, 21 hours, 6 minutes, 34 seconds
Online
percent
percent
percent
percent
MB
2012-06-05 19:51:53 PDT
445
show chassis firmware

Syntax
Syntax (TX Matrix

Routers)

<lcc number | scc>

Routers)

Syntax (MX Series

Routers)

<all-members>
<local>
<member member-id>
Syntax (MX2010 3D
Universal Edge
Routers)
Syntax (MX2020 3D
Universal Edge
Routers)
Syntax (QFX Series)

interconnect-device name
node-device name
Syntax (ACX Series

Universal Access
Routers)
Syntax (EX Series

Switches)

<detail>
Release Information

Command introduced for EX8200 switches in Junos OS Release 10.2 for EX Series
switches.
Command introduced in Junos OS Release 12.3 for ACX4000 Universal Access Routers.
Description
On routers and switches, display the version levels of the firmware running on the System
Control Board (SCB), Switching and Forwarding Module (SFM), System and Switch
Board (SSB), Forwarding Engine Board (FEB), Flexible PIC Concentrators (FPCs), and
Routing Engines. On a TX Matrix Plus router, display the version levels of the firmware
running on the FPCs and the Switch Processor Mezzanine Board (SPMBs).
446
On EX2200, EX3200, and EX4200 switches, and the QFX Series, display the version
levels of the firmware running on the switch. On an EX8208 switch, display the version
levels of the firmware running on the Switch Fabric and Routing Engine (SRE) modules
and on the line cards (shown as FPCs). On an EX8216 switch, display the version levels
of the firmware running on the Routing Engine (RE) modules and on the line cards (shown
as FPCs).
Options
noneDisplay the version levels of the firmware running. For an EX4200 switch that is
a member of a Virtual Chassis, display version levels for all members. For a TX Matrix
router, display version levels for the firmware on the TX Matrix router and on all the
T640 routers connected to the TX Matrix router. For a TX Matrix Plus router, display
version levels for the firmware on the TX Matrix Plus router and on all the T1600
routers connected to the TX Matrix Plus router.
all-members(MX Series routers only) (Optional) Display the version levels of the
firmware running for all members of the Virtual Chassis configuration.

interconnect-device name(QFabric systems) (Optional) Display the version levels of
the firmware running on the Interconnect device.

display version levels for the firmware on a specified T640 router (or line-card
chassis) that is connected to the TX Matrix router. On a TX Matrix Plus router, display
the version levels for the firmware on a specified T1600 router (or line-card chassis)
that is connected to the TX Matrix Plus router. Replace number with a value from 0
through 3.
local(MX Series routers only) (Optional) Display the version levels of the firmware
running for the local Virtual Chassis member.

member member-id(MX Series routers only) (Optional) Display the version levels of
the firmware running for the specified member of the Virtual Chassis configuration.
Replace member-id with a value of 0 or 1.
node-device(QFabric systems only) (Optional) Display the version levels of the firmware
running on the Node device.

scc(TX Matrix router only) (Optional) Display version levels for the firmware on the TX
Matrix router (or switch-card chassis).

sfc number(TX Matrix Plus router only) (Optional) Display version levels for the firmware
on the TX Matrix Plus router (or switch-fabric chassis). Replace number with 0.
detail(EX3200, EX3300, EX4200, and EX4500 standalone and Virtual Chassis member
switches only) (Optional) Display version levels of the firmware running on the switch
for its programmable hardware components.
Required Privilege
Level
view
447
Related
Documentation
Output Fields
Upgrading the HSM Firmware
show chassis firmware (M10 Router) on page 450

show chassis firmware (MX240 Router) on page 450
show chassis firmware (MX240, MX480, MX960 Router with Application Services
Modular Line Card) on page 451
show chassis firmware (EX4200 Switch) on page 453
show chassis firmware (EX8200 Switch) on page 453
show chassis firmware lcc (TX Matrix Router) on page 453
show chassis firmware scc (TX Matrix Router) on page 453
show chassis firmware (TX Matrix Plus Router) on page 453
show chassis firmware lcc (TX Matrix Plus Router) on page 455
show chassis firmware sfc (TX Matrix Plus Router) on page 455
show chassis firmware (QFX Series) on page 456
show chassis firmware interconnect-device (QFabric System) on page 456
show chassis firmware (ACX2000 Universal Access Router) on page 456
show chassis firmware detail (EX3300 Switch) on page 456
show chassis firmware (MX Routers with Media Services Blade [MSB]) on page 456
Table 37 on page 448 lists the output fields for the show chassis firmware command.
Table 37: show chassis firmware Output Fields
448
Field Name
Field Description
Part
(MX Series, MX2010, and MX2020 routers) Chassis part name.
Type
(MX Series, MX2010, and MX2020 routers) Type of firmware: On

routers: ROM or O/S. On switches: uboot or loader.
Version
(MX Series, MX2010, and MX2020 routers) Version of firmware

running on the chassis part.
FPC
(detail option only) Number of FPC.

For a standalone switch, the value is 0.
For a Virtual Chassis configuration, value in the range of 0-9; refers
to the member ID assigned to the switch.
Boot
(detail option only) Version of the SYSPLD.
PoE
(detail option only) Version of the PoE firmware.
Table 37: show chassis firmware Output Fields (continued)

Field Name
Field Description
PFE-<number>
(detail option only) Version of the PFE used in the switch.
PHY-
(detail option only) Version of the physical layer device (PHY) used
in the switch.
microcode
(detail option only) Microcode of the physical layer devices (PHY)

used in the switch.
uboot
(detail option only) Version of the u-boot used in the switch.
loader
(detail option only) Version of the loader used in the switch.
449
Sample Output
(M10 Router)
user@host> show chassis firmware

Part
Type
Forwarding engine board ROM
O/S
Version
Juniper ROM Monitor Version 4.1b2
Version 4.1I1 by tlim on 2000-04-24 11:27

(M20 Router)

Part
Type
System switch board
ROM
O/S
FPC 1
ROM
O/S
FPC 2
ROM
O/S
Version
Juniper
Version
Juniper
Version
Juniper
Version
ROM Monitor Version 3.4b26

3.4I16 by smackie on 2000-02-29 2
3.4I4 by smackie on 2000-02-25 21
3.4I4 by smackie on 2000-02-25 21

Part
Type
System control board
ROM
O/S
FPC 5
ROM
O/S
Version
Juniper
Version
Juniper
Version
ROM Monitor Version 2.0i126Copyri

2.0i1 by root on Thu Jul 23 00:51
ROM Monitor Version 2.0i49Copyrig
2.0i1 by root on Thu Jul 23 00:59

FPC 2
ROM
O/S
FPC 3
ROM
O/S
FPC 4
ROM
O/S
FEB 3
ROM
O/S
FEB 4
ROM
O/S
Juniper
Version
Juniper
Version
Juniper
Version
Juniper
Version
Juniper
Version
ROM Monitor Version

8.2B1 by builder on
ROM Monitor Version
8.2B1 by builder on
ROM Monitor Version
8.2B1 by builder on
ROM Monitor Version
8.2B1 by builder on
ROM Monitor Version
8.2B1 by builder on

Part
Type
SFM 0
ROM
O/S
SFM 1
ROM
O/S
FPC 0
ROM
O/S
FPC 1
ROM
O/S
FPC 2
ROM
O/S
Version
Juniper
Version
Juniper
Version
Juniper
Version
Juniper
Version
Juniper
Version

4.0I1 by tlim on 2000-02-29
4.0I1 by tlim on 2000-02-29
4.0I1 by tlim on 2000-02-29
4.0I1 by tlim on 2000-02-29
4.0I1 by tlim on 2000-02-29

Part
Type
FPC 1
ROM
O/S
FPC 2
ROM
O/S
Version
Juniper
Version
Juniper
Version

9.0-20080103.0 by builder on 2008-0
9.0-20080103.0 by builder on 2008-0

(M40 Router)

(M120 Router)

(M160 Router)

(MX240 Router)
450
8.0b29
2006-10-18
8.0b29
2006-10-18
8.0b29
2006-10-18
8.0b29
2006-10-18
8.0b29
2006-10-18
16:2
16:2
16:2
16:1
16:1
11:50
11:50
11:56
11:56
11:56

(MX480 Router)

Part
Type
FPC 1
ROM
O/S
Version
Version 9.0-20070916.3 by builder on 2007-0

(MX960 Router)

Part
Type
FPC 4
ROM
O/S
FPC 7
ROM
O/S
Version
Juniper
Version
Juniper
Version

8.2I59 by artem on 2006-10-31 19:22
8.2-20061026.1 by builder on 2006-1

Part
Type
FPC 0
ROM
O/S
FPC 1
ROM
O/S
FPC 8
ROM
O/S
FPC 9
ROM
O/S
SPMB 0
ROM
O/S
SPMB 1
ROM
O/S
Version
Juniper
Version
Juniper
Version
Juniper
Version
Juniper
Version
Juniper
Version
Juniper
Version

12.3-20120718_ib_12_3_psd.0
12.3-20120718_ib_12_3_psd.0
12.3-20120718_ib_12_3_psd.0
12.3-20120718_ib_12_3_psd.0
12.3-20120718_ib_12_3_psd.0
12.3-20120718_ib_12_3_psd.0

(MX2010 Router)

(MX2020 Router)

Part
Type
FPC 0
FPC 1
FPC 2
FPC 3
FPC 4
FPC 5
FPC 6
FPC 7
FPC 8
FPC 9
FPC 10
FPC 11
FPC 12
FPC 13
FPC 14
FPC 15
FPC 16
FPC 17
FPC 18
FPC 19
SPMB 0
ROM
O/S
SPMB 1
ROM
O/S
by buil
by buil
by buil
by buil
by buil
by buil
Version
Juniper
Version
Juniper
Version

12.3I5 by psampath on 2012-11-04 03
12.3I5 by psampath on 2012-11-04 03
451
(MX240, MX480,
MX960 Router with
452
Part
FPC 1
Type
ROM
O/S
Version
Version 12.2I21 by manish on 2012-06-19 17:
Application Services
Modular Line Card)

(EX4200 Switch)
user@switch> show chassis firmware

Part
FPC 0
FPC 1
FPC 2

(EX8200 Switch)
Type
uboot
loader
uboot
loader
uboot
loader
Version
U-Boot 1.1.6 (Feb 6 2008 - 11:27:42)
FreeBSD/PowerPC U-Boot bootstrap loader 2.1
U-Boot 1.1.6 (Feb 6 2008 - 11:27:42)
U-Boot 1.1.6 (Feb 6 2008 - 11:27:42)

Part
FPC 0
FPC 3
FPC 5
FPC 7
Routing Engine 0
Routing Engine 1
Type
U-Boot
loader
U-Boot
loader
U-Boot
loader
U-Boot
loader
U-Boot
loader
U-Boot
loader
Version
U-Boot 1.1.6 (Mar 25 2009 - 06:13:12) 2.4.0
U-Boot 1.1.6 (Dec 4 2009 - 13:17:34) 3.1.0
U-Boot 1.1.6 (Mar 25 2009 - 06:13:12) 2.4.0
U-Boot 1.1.6 (Feb 6 2009 - 05:31:46) 2.4.0
U-Boot 1.1.6 (Mar 25 2009 - 06:13:12) 2.4.0
U-Boot 1.1.6 (Mar 25 2009 - 06:13:12) 2.4.0

lcc (TX Matrix Router)
user@host> show chassis firmware lcc 0

lcc0-re0:
-------------------------------------------------------------------------Part
Type
Version
FPC 1
ROM
O/S
FPC 2
ROM
O/S
SPMB 0
ROM
O/S

scc (TX Matrix Router)
user@host> show chassis firmware scc

scc-re0:
-------------------------------------------------------------------------Part
Type
Version
SPMB 0
ROM
O/S

(TX Matrix Plus
Router)

sfc0-re0:
-------------------------------------------------------------------------Part
Type
Version
Global FPC 4
Global FPC 6
Global FPC 7
Global FPC 12
453
Global
Global
Global
Global
Global
Global
Global
Global
Global
Global
Global
Global
SPMB 0
SPMB 1
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
14
15
20
21
22
23
24
25
26
28
29
31
ROM
O/S
ROM
O/S
Juniper
Version
Juniper
Version

9.6-20090507.0 by builder on 2009-0
9.6-20090507.0 by builder on 2009-0
lcc0-re1:
-------------------------------------------------------------------------Part
Type
Version
FPC 4
ROM
O/S
FPC 6
ROM
O/S
FPC 7
ROM
O/S
SPMB 0
ROM
O/S
SPMB 1
ROM
O/S
lcc1-re1:
-------------------------------------------------------------------------Part
Type
Version
FPC 4
ROM
O/S
FPC 6
ROM
O/S
FPC 7
ROM
O/S
SPMB 0
ROM
O/S
SPMB 1
ROM
O/S
lcc2-re1:
-------------------------------------------------------------------------Part
Type
Version
FPC 4
ROM
O/S
FPC 5
ROM
O/S
FPC 6
ROM
O/S
FPC 7
ROM
O/S
SPMB 0
ROM
O/S
SPMB 1
ROM
O/S
454
lcc3-re1:
-------------------------------------------------------------------------Part
Type
Version
FPC 0
ROM
O/S
FPC 1
ROM
O/S
FPC 2
ROM
O/S
FPC 4
ROM
O/S
FPC 5
ROM
O/S
FPC 7
ROM
O/S
SPMB 0
ROM
O/S
SPMB 1
ROM
O/S

lcc (TX Matrix Plus
Router)
user@host> show chassis firmware lcc 0

lcc0-re1:
-------------------------------------------------------------------------Part
Type
Version
FPC 4
ROM
O/S
FPC 6
ROM
O/S
FPC 7
ROM
O/S
SPMB 0
ROM
O/S
SPMB 1
ROM
O/S

sfc (TX Matrix Plus
Router)
user@host> show chassis firmware sfc 0

sfc0-re0:
-------------------------------------------------------------------------Part
Type
Version
Global FPC 4
Global FPC 6
Global FPC 7
Global FPC 12
Global FPC 14
Global FPC 15
Global FPC 20
Global FPC 21
Global FPC 22
Global FPC 23
Global FPC 24
Global FPC 25
Global FPC 26
Global FPC 28
Global FPC 29
Global FPC 31
SPMB 0
ROM
O/S
SPMB 1
ROM
O/S
455

(QFX Series)

Part
Type
FPC 0
Routing Engine 0
U-Boot
loader
Version
U-Boot 1.1.6 (Sep 15 2010 - 02:11:11) 1.0.5
FreeBSD/MIPS U-Boot bootstrap loader 0.1

interconnect-device
(QFabric System)
user@switch> show chassis firmware interconnect-device interconnect1

Part
Type
Version
Routing Engine 0
U-Boot
U-Boot 1.1.6 (May 10 2011 - 04:52:59) 1.1.1
loader
Routing Engine 1
U-Boot
U-Boot 1.1.6 (May 10 2011 - 04:52:59) 1.1.1
loader

(ACX2000 Universal
Access Router)

Part
Type
FPC
O/S
FEB
O/S

detail (EX3300
Switch)
user@switch> show chassis firmware detail

FPC 0
Boot SYSPLD
3
PoE firmware
4.1.6
PFE-0
3
PFE-1
3
PHY
microcode
0x514
Boot Firmware
uboot
U-Boot 1.1.6 (Aug 21 2011 - 01:45:26)
loader
FreeBSD/arm U-Boot loader 1.0

(MX Routers with
Media Services Blade
[MSB])
456

Part
Type
FPC 1
ROM
O/S
Version
Version 12.2I13 by jisjoy on 2012-05-29 06:
Version 12.2I13 by jisjoy on 2012-05-29 06:
1.0.0
Version
Version 12.2I21 by manish on 2012-06-19 17:
show chassis fpc

Syntax
Syntax (EX Series

Switches)
Syntax (T4000
Routers)
Syntax (TX Matrix and

TX Matrix Plus
Routers)
Syntax (MX Series
Routers)
show chassis fpc

<detail <slot>> | <pic-status <slot>>
show chassis fpc
<detail <fpc-slot>> | <pic-status <fpc-slot>>
<fpc-slot>
show chassis fpc
<detail <fpc-slot>>
<pic-status <fpc-slot>>
show chassis fpc
<slot>
show chassis fpc
<detail <slot>> | <pic-status <slot>>
<all-members>
<local>
<member member-id>
Syntax (MX2010 3D
Universal Edge
Routers)
show chassis fpc

<slot> detail | <detail <slot>> | <pic-status <slot>>
<fpc-slot>
Syntax (MX2020 3D
Universal Edge
Routers)
show chassis fpc

< slot> detail | <detail <slot>> | <pic-status <slot>>
<fpc-slot>
Syntax (QFX Series)
show chassis fpc

<detail>
<interconnect-device name <fpc-slot fpc-slot>>
<node-device name>
Syntax (PTX Series

Packet Transport
Switches)
show chassis fpc

<fpc-slot>
Syntax (ACX Series

Universal Access
Routers)
show chassis fpc

<fpc-slot>
Release Information

457
Description
Options
Display status information about the installed Flexible PIC Concentrators (FPCs)and
PICs.
noneDisplay status information for all FPCs. On a TX Matrix router, display status
information for all FPCs on the attached T640 routers in the routing matrix. On a TX
Matrix Plus router, display status information for all FPCs on the attached T1600
routers in the routing matrix.
NOTE: In EX8200 switches, line cards initialize Packet Forwarding Engine

during startup. If an error occurs during hardware initialization, the FPCs
with bad hardware parts power down after transferring the debug
information to the Routing Engine. The Routing Engine marks the FPC
offline, logs the error in system log messages (/var/log/messages), and
generates an alarm to inform the user.
See the following sample output:
user@host> show chassis fpc
Utilization (%)
Slot State
(C) Total Interrupt
Buffer
0 Empty
1 Empty
2 Empty
3 Empty
4 Empty
5 Offline
---Hard FPC error--6 Empty
7 Online
26
4
0
32
Memory
DRAM (MB) Heap
1024
The following sample output shows the alarm raised for the failed FPCs.
user@host > show chassis alarms
Alarm time
Class
2011-03-24 00:52:51 UTC Major
2011-03-24 00:52:31 UTC Major
2011-03-24 00:52:31 UTC Major
2011-03-24 00:51:26 UTC Minor
RE
458
Description
FPC 5 Hard errors
Fan Tray Failure
Fan Tray Failure
Loss of communication with Backup
NOTE: On T4000 routers, when you include the enhanced-mode

statement at the [edit chassis network-services] hierarchy level and reboot
the system, only the T4000 Type 5 FPCs present on the router become
online while the remaining FPCs are offline, and FPC misconfiguration
alarms are generated. The show chassis alarm command output displays
FPC misconfiguration (FPC fpc-slot misconfig) as the reason for the
generation the alarms.
The following sample output shows the FPC status after the
enhanced-mode statement is configured on the T4000 router. The T4000
Type 5 FPC present in slot 5 becomes online while the remaining FPCs
are offline.
Utilization (%)
Slot State
(C) Total Interrupt
Buffer
0 offline
---FPC misconfiguration--1 offline
---FPC misconfiguration--2 offline
---FPC misconfiguration--3 Empty
4 Empty
5 Online
66
50
0
27
Memory
DRAM (MB) Heap
2816
29
The following sample output shows FPC misconfiguration alarms.

user@host > show chassis alarms
Alarm time
Class
2011-03-24 00:52:51 PST Major
2011-03-24 00:52:31 PST Major
2011-03-24 00:52:31 PST Major
Description
FPC 1 misconfig
FPC 2 misconfig
FPC 3 misconfig
detail(Optional) Display detailed status information for all FPCs or for the FPC in the
specified slot (see fpc-slot or slot).

all-members(MX Series routers only) (Optional) Display status information for all FPCs
on all members of the Virtual Chassis configuration.

interconnect-device name(QFabric systems only) (Optional) Display status information
for all FPCs on the Interconnect device.

fpc-slot(Optional) FPC slot number:
(TX Matrix and TX Matrix Plus router onlyOn a TX Matrix router, if you specify
the number of the T640 router (or line-card chassis) by using the lcc number option
(the recommended method), replace fpc-slot with a value from 0 through 7.
Otherwise, replace fpc-slot with a value from 0 through 31. Likewise, on a TX Matrix
Plus router, if you specify the number of the T1600 router (or line-card chassis)
459
by using the lcc number option (the recommended method), replace fpc-slot with
a value from 0 through 7. Otherwise, replace fpc-slot with a value from 0 through
31. For example, the following commands have the same result:
user@host> show chassis fpc detail 1 lcc 1
user@host> show chassis fpc detail 9
M120 routerReplace fpc-slot with a value from 0 through 5.
MX80 routerReplace fpc-slot with a value from 0 through 1.
MX-960 routerReplace fpc-slot with a value from 0 through 11.
MX2010 routerReplace fpc-slot-number with a value from 0 through 9.
MX2020 routerReplace fpc-slot-number with a value from 0 through 19.
Other routersReplace fpc-slot with a value from 0 through 7.
EX Series switches:
EX3200 switches and EX4200 standalone switchesReplace fpc-slot with 0.
EX4200 switches in a Virtual Chassis configurationReplace fpc-slot with a

value from 0 through 9.
EX6210 switchesReplace fpc-slot with a value from 0 through 9.
QFX Series:
QFX3500 switchesReplace fpc-slot with 0.
QFabric systemsReplace fpc-slot with 0 through 31 on the Interconnect device.
PTX Series Packet Transport Switches:
PTX5000 Packet Transport SwitchReplace fpc-slot with a value from 0 through

7.
ACX Series Universal Access Routers:
ACX1000 and ACX2000 Universal Access RoutersReplace fpc-slot with 0.
local(MX Series routers only) (Optional) Display status information for all FPCs on the
local Virtual Chassis member.

member member-id(MX Series routers only) (Optional) Display status information for
all FPCs on the specified member of the Virtual Chassis configuration. Replace
node-device name(QFabric systems only) (Optional) Display status information for
each Node device. Each Node device is equivalent to an FPC.
460
pic-status(Optional) Display status information for all PICs or for the PIC in the specified
slot (see fpc-slot).
NOTE: On T1600 routers, Type 4 FPCs with ASICs based on the SL2.0
chipset do not support the 10-Gigabit Ethernet LAN/WAN PIC with SFP+
(10x10GE [LAN/WAN] SFPP). If you issue the show chassis fpc command
with the pic-status option, the CLI displays the string Not Supported
for 10x10GE(LAN/WAN) SFPP PICs installed on such FPCs. The following
is a sample output:
user@host> show chassis fpc pic-status
Slot 0
Online
E2-FPC Type 1
PIC 0 Online
1x G/E SFP, 1000 BASE
PIC 1 Online
Adaptive Services-II
PIC 2 Online
1x G/E IQ, 1000 BASE
PIC 3 Online
Slot 1
Online
FPC Type 3-ES
PIC 0 Present
UNUSED- Not Supported
Slot 2
Online
FPC Type 4-ES
PIC 0 Offline
4x OC-192 SONET XFP
PIC 1 Present
10x10GE(LAN/WAN) SFPP- Not Supported
<<<<<<
Slot 4
Offline
FPC Type 1-ES
Slot 5
Offline
FPC Type 2-ES
Slot 6
Online
E2-FPC Type 3
PIC 0 Online
1x OC-192 SONET XFP
PIC 1 Online
4x OC-48 SONET
PIC 2 Online
4x OC-48 SONET
PIC 3 Online
MultiServices 500
Slot 7
Online
FPC Type 4-ES
PIC 0 Online
4x 10GE (LAN/WAN) XFP
PIC 1 Online
In addition, an entry is logged in the system log messages

(/var/log/messages) that the PIC is not supported. The following is a
sample message logged in the system log:
Apr 5 08:47:36 router1 chassisd[2770]: CHASSISD_UNSUPPORTED_PIC:
PIC 1 in FPC 2 (type 763, version 257) is not supported
lcc number(TX Matrix and TX Matrix Plus router only) (Optional) On a TX Matrix router,
display status information for a T640 router (or line-card chassis) that is connected
to the TX Matrix router. On a TX Matrix Plus router, display status information for a
T1600 router (or line-card chassis) that is connected to the TX Matrix Plus router.
Replace number with a value from 0 through 3.
Required Privilege
Level
Related
Documentation
view
request chassis fpc
show chassis fabric fpcs
461
462
Configuring the Junos OS to Resynchronize FPC Sequence Numbers with Active FPCs
when an FPC Comes Online
MX960 Flexible PIC Concentrator Description
enhanced-mode
show chassis fpc (EX6210 Switch) on page 466

show chassis fpc (M10 Router) on page 466
show chassis fpc (M20 Router) on page 466
show chassis fpc detail (M Series Routers) on page 466
show chassis fpc detail (MX80 Router) on page 466
show chassis fpc (MX240 Router) on page 467
show chassis fpc (MX480 Router with 100-Gigabit Ethernet CFP) on page 467
show chassis fpc pic-status (MX480 Router with 100-Gigabit Ethernet CFP) on page 467
show chassis fpc (MX240, MX480, MX960 Routers with Application Services Modular
Line Card on page 468
show chassis fpc (MX240, MX480, MX960 with Application Services Modular Line
Card on page 468
show chassis fpc (MX2010 Routers) on page 469
show chassis fpc (MX2020 Routers) on page 469
show chassis fpc detail (MX Series Routers) on page 469
show chassis fpc (Hardware Not Supported) on page 469
show chassis fpc detail (Hardware Not Supported) on page 470
show chassis fpc pic-status on page 470
show chassis fpc pic-status (M Series Routers) on page 470
show chassis fpc pic-status (M120 Router) on page 471
show chassis fpc pic-status (MX240, MX480, and MX960 Routers with Application
Services Modular Line Card) on page 471
show chassis fpc lcc (TX Matrix Router) on page 472
show chassis fpc pic-status (TX Matrix Router) on page 472
show chassis fpc pic-status lcc (TX Matrix Router) on page 472
show chassis fpc (TX Matrix Plus Router) on page 473
show chassis fpc lcc (TX Matrix Plus Router) on page 473
show chassis fpc detail (TX Matrix Plus Router) on page 473
show chassis fpc pic-status (TX Matrix Plus Router) on page 476
show chassis fpc (T1600 Router) on page 477
show chassis fpc detail (T1600 Router) on page 477
show chassis fpc slot (T1600 Router) on page 477
show chassis fpc pic-status (T1600 Router) on page 478
show chassis fpc (T4000 Router) on page 478
show chassis fpc detail (T4000 Router) on page 478
show chassis fpc pic-status (T4000 Router) on page 479
show chassis fpc (QFX Series) on page 479
show chassis fpc detail (QFX3500 Switches) on page 479
show chassis fpc pic-status (QFX3500 Switches) on page 479
show chassis fpc interconnect-device (QFabric System) on page 479

show chassis fpc interconnect-device (QFabric System) on page 480
show chassis fpc interconnect-device detail (QFabric System) on page 480
show chassis fpc pic-status interconnect-device (QFabric System) on page 480
show chassis fpc pic-status node-device (QFabric System) on page 481
show chassis fpc (PTX5000 Packet Transport Switch) on page 481
show chassis fpc detail (PTX5000 Packet Transport Switch) on page 481
show chassis fpc pic-status (PTX5000 Packet Transport Switch) on page 482
show chassis fpc (ACX2000 Universal Access Router) on page 483
show chassis fpc 0 (ACX2000 Universal Access Router) on page 483
show chassis fpc detail (ACX2000 Universal Access Router) on page 483
show chassis fpc pic-status (ACX2000 Universal Access Router) on page 483
show chassis FPC 1 (MX Routers with Media Services Blade [MSB]) on page 483
show chassis FPC 1 detail (MX Routers with Media Services Blade [MSB]) on page 483
Output Fields
Table 38 on page 463 lists the output fields for the show chassis fpc command. Output
Table 38: show chassis fpc Output Fields

Field Name
Field Description
Level of Output
Slot or Slot State
Slot number and state. The state can be one of the following conditions:
all levels
DeadHeld in reset because of errors.
DiagSlot is being ignored while the FPC is running diagnostics.
DormantHeld in reset.
EmptyNo FPC is present.
Offline(PTX Series Packet Transport Switches only) One of the following
two states is displayed:
FPC offlined due to unreachable destinations
FPC Offlined due to degraded FPC action
OnlineFPC is online and running.
PresentFPC is detected by the chassis daemon but either is not supported
by the current version of Junos OS or is inserted in the wrong slot. The output
also states either Hardware Not Supported or Hardware Not In Right Slot. The
FPC is coming up but not yet online.
ProbedProbe is complete; awaiting restart of the Packet Forwarding Engine.
Probe-waitWaiting to be probed.
Logical slot
Slot number.
all levels
Temp (C) or
Temperature
Temperature of the air passing by the FPC, in degrees Celsius or in both Celsius
and Fahrenheit.
all levels
all levels
463
Table 38: show chassis fpc Output Fields (continued)

Field Name
Field Description
Level of Output
Temperature (PTX
Series)
On PTX Series Packet Transport Switches, temperature details are provided in

degrees Celsius and Fahrenheit. Output includes:
detail
Temperature (PMB)Temperature of the air passing by the Processor

Mezzanine Board (PMB) at the bottom of the FPC.
Temperature (Intake)Temperature of the air flowing into the chassis.
Temperature (Exhaust)Exhaust temperatures for multiple zones (Exhaust

A and Exhaust B).
Temperature (TLn)-Temperature of the specified Lookup ASIC (TL) of the

packet forwarding engine on the FPC.
Temperature (TQn)-Temperature of the specified Queuing and Memory

Interface ASIC (TQ) of the packet forwarding engine on the FPC.
Total CPU
Utilization (%)
Total percentage of CPU being used by the FPC's processor.
all levels
Interrupt CPU
Utilization (%)
Of the total CPU being used by the FPC's processor, the percentage being used
for interrupts.
none specified
Memory DRAM
(MB)
Total DRAM, in megabytes, available to the FPC's processor.
none specified
Heap Utilization
(%)
Percentage of heap space (dynamic memory) being used by the FPC's processor.
If this number exceeds 80 percent, there may be a software problem (memory
leak).
none specified
NOTE: On MX Series routers in a broadband edge environment, heap utilization

levels higher than 70 percent can affect unified ISSU, router stability, or scaling
capability.
Buffer Utilization
(%)
Percentage of buffer space being used by the FPC's processor for buffering
internal messages.
none specified
Total CPU DRAM
Amount of DRAM available to the FPC's CPU.
detail
Total RLDRAM
Amount of reduced latency dynamic random access memory (RLDRAM)

available to the FPC CPU.
detail
Total DDR DRAM
Amount of double data rate dynamic random access memory (DDR DRAM)
available to the FPC CPU.
detail
Total SRAM
Amount of static RAM (SRAM) used by the FPC's CPU.
detail
Total SDRAM
Total amount of memory used for storing packets and notifications.
detail
I/O Manager ASICs

information
I/O Manager version number, manufacturer, and part number.
detail
Start time
Time when the Routing Engine detected that the FPC was running.
detail
464
Table 38: show chassis fpc Output Fields (continued)

Field Name
Field Description
Level of Output
Uptime
How long the Routing Engine has been connected to the FPC and, therefore,
how long the FPC has been up and running.
detail
PIC type
(pic-status output only) Type of PIC.
none specified
465
Sample Output
show chassis fpc
(EX6210 Switch)
user@switch> show chassis fpc

Slot State
(C) Total Interrupt
0 Empty
1 Online
7
5
0
2 Empty
3 Empty
4 Online
25
17
2
5 Online
25
3
0
6 Online
6
5
0
7 Empty
8 Empty
9 Online
8
7
0
show chassis fpc (M10

Router)

FPC status:
Temp
Slot State
(C)
0 Online
27
1 Online
28
show chassis fpc (M20

Router)

FPC status:
Slot State
(C) Total Interrupt
0 Empty
0
0
0
1 Online
38
0
0
2 Online
35
0
0
3 Empty
0
0
0
show chassis fpc detail

(M Series Routers)

(MX80 Router)
466

Slot 1 information:
State
Temperature
Total CPU DRAM
Total SRAM
Total SDRAM
I/O Manager ASICs information
I/O Manager ASICs information
Start time
Uptime
user@host> show chassis fpc detail

Slot 0 information:
State
Temperature
Total CPU DRAM
Total SRAM
Total SDRAM
Start time
Uptime
Slot 1 information:
State
Temperature
48
32
4
256
47
1024
331
1280
Memory
Utilization (%)
DRAM (MB) Heap
Buffer
1024
32
2048
2048
1024
0
0
0
30
24
32
1024
32
Memory
Utilization (%)
DRAM (MB) Heap
Buffer
0
0
0
8
0
4
8
0
3
0
0
0
Online
degrees C
MB
MB
MB
Version 2.0, Foundry IBM, Part number 0
Version 2.0, Foundry IBM, Part number 0
2000-02-08 02:18:49 UTC
Online
MB
MB
MB
2010-02-08 12:25:33 PST
Online
Total CPU DRAM

Total SRAM
Total SDRAM
Start time
Uptime
show chassis fpc

(MX240 Router)
show chassis fpc

(MX480 Router)
1024 MB
331 MB
1280 MB
2010-02-08 12:25:33 PST

Temp
CPU Utilization (%)
Slot State
(C) Total Interrupt
0 Empty
1 Online
34
6
0
2 Online
33
9
0

Temp
Slot State
(C)
0 Empty
1 Online
36
2 Empty
3 Empty
4 Empty
5 Empty
CPU Utilization (%)

Total Interrupt
9
Memory
Utilization (%)
DRAM (MB) Heap
Buffer
1024
1024
18
24
Memory
Utilization (%)
DRAM (MB) Heap
Buffer
1024
17
show chassis fpc

(MX480 Router with
100-Gigabit Ethernet
CFP)

Memory
Utilization (%)
Slot State
(C) Total Interrupt
DRAM (MB) Heap
Buffer
0 Online
33
4
0
2048
10
13
1 Online
36
7
0
2048
16
13
2 Online
29
6
0
1024
27
29
3 Online
33
0
0
0
0
0
4 Online
36
7
0
2048
19
13
5 Online
34 31
11
2048
14
13
show chassis fpc

pic-status (MX480
Router with

Slot 1
Online
MPC Type 3
PIC 2 Online
1X100GE CFP
Slot 2 Online
DPCE 40x 1GE R EQ
30
30
57
467
CFP)
show chassis fpc

(MX960 Router)
PIC
PIC
PIC
PIC
Slot
PIC
PIC
Slot
PIC
PIC
Slot
PIC
PIC
PIC
PIC
0
1
2
3
3
0
2
4
0
2
5
0
1
2
3
Online
Online
Online
Online
Online
Online
Online
Online
Online
Online
Online
Online
Online
Online
Online
10x 1GE(LAN) EQ
10x 1GE(LAN) EQ
10x 1GE(LAN) EQ
10x 1GE(LAN) EQ
MPC Type 3
1X100GE CFP
1X100GE CFP
MPC Type 3
1X100GE CFP
1X100GE CFP
MPC Type 2 3D EQ
2x 10GE XFP
2x 10GE XFP
10x 1GE(LAN) SFP
10x 1GE(LAN) SFP

Memory
Slot State
(C) Total Interrupt
DRAM (MB) Heap
0 Empty
1 Empty
2 Empty
3 Online
25
19
0
1024
15
4 Empty
5 Online
26
27
0
1024
15
6 Empty
7 Empty
8 Empty
9 Empty
10 Empty
11 Empty
Utilization (%)
Buffer
show chassis fpc

(MX240, MX480,
MX960 Routers with
Modular Line Card
user@host>show chassis fpc 1

Memory
Utilization (%)
Slot State
(C) Total Interrupt
DRAM (MB) Heap
1 Online
34
5
0
3072
5
show chassis fpc

(MX240, MX480,
MX960 with
user@host>show chassis fpc 1 detail

Slot 1 information:
State
Temperature
468
57
57
Buffer
13
Online
34
Modular Line Card
show chassis fpc

(MX2010 Routers)
Total CPU DRAM

Total RLDRAM
Total DDR DRAM
Start time:
Uptime:
Max Power Consumption
3072 MB
259 MB
4864 MB
2012-06-19 10:51:43 PDT
550 Watts
user@host show chassis fpc

Memory
Utilization (%)
Slot State
(C) Total Interrupt
DRAM (MB) Heap
0 Online
34
9
0
2048
18
1 Online
32
9
0
2048
15
2 Empty
3 Empty
4 Empty
5 Empty
6 Empty
7 Empty
8 Online
31
13
0
2048
11
9 Online
33
10
0
2048
18
show chassis fpc

(MX2020 Routers)
user@host show chassis fpc

Temp
Slot State
(C)
0 Online
10
1 Online
8
2 Online
7
3 Online
8
4 Online
9
5 Online
8
6 Online
8
7 Online
9
8 Online
9
9 Online
10
10 Online
16
11 Online
11
12 Online
10
13 Online
11
14 Online
12
15 Online
13
16 Online
13
17 Online
12
18 Online
12
19 Online
14

(MX Series Routers)

Slot 0 information:
State
Temperature
Total CPU DRAM
Total RLDRAM
Total DDR DRAM
Start time:
Uptime:
show chassis fpc
CPU Utilization (%)

Total Interrupt
12
0
9
0
9
0
10
0
10
0
9
0
10
0
9
0
10
0
9
0
8
0
10
0
10
0
9
0
10
0
9
0
9
0
9
0
8
0
10
0
Buffer
13
13
13
13
Memory
Utilization (%)
DRAM (MB) Heap
Buffer
2048
18
13
2048
18
13
2048
18
13
2048
18
13
2048
18
13
2048
18
13
2048
18
13
2048
18
13
2048
18
13
2048
18
13
2048
18
13
2048
18
13
2048
18
13
2048
18
13
2048
18
13
2048
18
13
2048
18
13
2048
18
13
2048
18
13
2048
18
13
Online
MB
MB
MB
2009-08-11 21:20:30 PDT
335 Watts
36
1024
256
4096

show chassis fpc
469
(Hardware Not
Supported)

(Hardware Not
Supported)
Slot State
0 Online
1 Present
2 Online
3 Present
4 Empty
5 Empty
6 Online

Memory
Utilization (%)
(C) Total Interrupt
DRAM (MB) Heap
Buffer
-------------------- CPU less FPC ------------------------- Hardware Not In Right Slot -----0
0
0
0
0
------ Hardware Not Supported ------

Slot 0 information:
State
Total CPU DRAM
Start time
Uptime
Slot 1 information:
State
Reason
Slot 2 information:
State
Total CPU DRAM
Start time
Uptime
Slot 3 information:
State
Reason
Total CPU DRAM
Slot 6 information:
State
Total CPU DRAM
Start time
Uptime
Online
---- CPU less FPC ---2006-07-07 03:21:00 UTC
Present
--- Hardware Not In Right Slot --Online
32 MB
2006-07-07 03:20:59 UTC
Present
--- Hardware Not Supported --0 MB
Online
32 MB
2006-07-07 03:21:01 UTC
show chassis fpc

pic-status

Slot 0 Online
PIC 1
1x OC-12 ATM, MM
PIC 2
1x OC-12 ATM, MM
PIC 3
1x OC-12 ATM, MM
Slot 1 Online
PIC 0
1x OC-48 SONET, SMIR
Slot 2 Online
PIC 0
1x OC-192 SONET, SMSR
show chassis fpc

pic-status (M Series
Routers)

Slot 1
Online
FPC Type 1
PIC 0 Present
2x OC-3 ATM, MM- Hardware Error
PIC 1 Online
4x OC-3 SONET, SMIR
Slot 2
Online
E-FPC Type 2
PIC 0 Online
4x G/E, 1000 BASE-SX
PIC 1 Online
PIC 3 Online
1x Tunnel
Slot 3
Online
E-FPC Type 1
PIC 0 Online
PIC 2 Online
Slot 4
Online
E-FPC Type 2
PIC 0 Online
PIC 1 Online
470
PIC 2
PIC 3
Slot 5
...
Online
Online
Online

FPC Type 2
show chassis fpc

pic-status (M120
Router)

Slot 1
Online
M120 CFPC 10GE
PIC 0 Online
1x 10GE(LAN/WAN) XFP
Slot 3
Online
M120 FPC Type 2 (proto)
PIC 0 Online
PIC 1 Online
4x OC-3 SONET, SMIR
PIC 2 Online
PIC 3 Online
8x 1GE(LAN), IQ2
Slot 4
Online
PIC 0 Online
10x 1GE(LAN), 1000 BASE
Slot 5
Online
PIC 0 Present
1x G/E, 1000 BASE-LX- Not Supported
PIC 1 Online
1x CHOC3 IQ SONET, SMLR
PIC 2 Online
4x CHDS3 IQ
PIC 3 Online
show chassis fpc

pic-status (MX240,
MX480, and MX960
Routers with
In the following output Slot 1 and Slot 5 are the Application Services Modular Carrier
Cards (AS MCC), PIC 0 is the Application Services Modular Storage Card (AS MSC), and
PIC 2 is the Application Services Modular Processing Card (AS MXC).
user@host>show chassis fpc pic-status
471
Modular Line Card)
Slot 2
Slot 1
PIC 0
PIC 2
Slot 4
Slot 5
show chassis fpc lcc

(TX Matrix Router)
user@host> show chassis fpc lcc 0

lcc0-re0:
-------------------------------------------------------------------------Temp CPU
Utilization (%) Memory
Utilization (%)
Slot State
(C) Total Interrupt
DRAM (MB)
Heap
Buffer
0 Empty
1 Online
27
2
0
256
8
44
2 Online
27
3
0
256
15
44
3 Empty
4 Empty
5 Empty
6 Empty
7 Empty
show chassis fpc

pic-status (TX Matrix
Router)

lcc0-re0:
-------------------------------------------------------------------------Slot 0
Online
FPC Type 3
PIC 0 Online
1x OC-192 SM SR1
PIC 1 Online
1x OC-192 SM SR2
PIC 2 Online
1x OC-192 SM SR1
PIC 3 Online
1x Tunnel
Slot 1
Online
FPC Type 2
PIC 0 Online
PIC 1 Online
Online
Online
Online
Online
Offline
Offline
MPC Type 1 3D Q
AS-MCC
AS-MSC
AS-MXC
MPC 3D 16x 10GE
AS-MCC
lcc1-re0:
-------------------------------------------------------------------------lcc2-re0:
-------------------------------------------------------------------------Slot 1
Online
FPC Type 3
PIC 0 Online
1x OC-192 SM SR1
Slot 5
Online
FPC Type 2
PIC 0 Online
PIC 1 Online
2x G/E, 1000 BASE-LX
PIC 2 Online
2x G/E, 1000 BASE-LX
PIC 3 Online
lcc3-re0:
--------------------------------------------------------------------------
show chassis fpc

pic-status lcc (TX
Matrix Router)
472
user@host> show chassis fpc pic-status lcc 0

lcc0-re0:
-------------------------------------------------------------------------Slot 0
Online
FPC Type 3
PIC 0 Online
1x OC-192 SM SR2
Slot 1
Online
FPC Type 2
PIC 0 Online
2x OC-12 ATM2 IQ, MM
PIC 1 Online
PIC 2 Online
PIC 3 Online
show chassis fpc (TX

Matrix Plus Router)

lcc0-re0:
-------------------------------------------------------------------------Temp CPU Utilization (%)
Memory
Utilization (%)
Slot State
(C) Total Interrupt
DRAM (MB) Heap
Buffer
0 Empty
1 Online
38
4
0
2048
3
24
2 Online
43
8
0
2048
6
24
3 Empty
4 Online
43
6
0
2048
6
24
5 Empty
6 Online
42
13
0
2048
6
24
7 Online
45
7
0
2048
3
24
lcc2-re0:
Memory
Utilization (%)
Slot State
(C) Total Interrupt
DRAM (MB) Heap
Buffer
0 Online
42
10
0
2048
6
24
1 Empty
2 Online
42
11
0
2048
6
24
3 Online
40
5
0
2048
3
24
4 Online
33
26
0
1024
8
49
5 Empty
6 Online
43
8
0
2048
6
24
7 Online
46
6
0
2048
3
24
lcc3-re0:
Memory
Utilization (%)
Slot State
(C) Total Interrupt
DRAM (MB) Heap
Buffer
0 Empty
1 Empty
2 Online
39
30
0
2048
7
24
3 Empty
4 Online
41
8
0
2048
6
24
5 Online
41
12
0
2048
6
24
6 Online
40
8
0
2048
6
24
7 Online
42
4
0
2048
3
24
show chassis fpc lcc

(TX Matrix Plus
Router)
user@host> show chassis fpc lcc 0

lcc0-re0:
Memory
Utilization (%)
Slot State
(C) Total Interrupt
DRAM (MB) Heap
Buffer
0 Empty
1 Online
38
4
0
2048
3
24
2 Online
43
8
0
2048
6
24
3 Empty
4 Online
43
6
0
2048
6
24
5 Empty
6 Online
42
14
0
2048
6
24
7 Online
45
6
0
2048
3
24

(TX Matrix Plus
Router)
user@host> show chassis fpc details

lcc0-re0:
--------------------------------------------------------------------------
473
Slot 1 information:
State
Temperature
Total CPU DRAM
Total SRAM
Total SDRAM
Start time
Uptime
Slot 2 information:
State
Temperature
Total CPU DRAM
Total SRAM
Total SDRAM
Start time
Uptime
Slot 4 information:
State
Temperature
Total CPU DRAM
Total SRAM
Total SDRAM
Start time
Uptime
Slot 6 information:
State
Temperature
Total CPU DRAM
Total SRAM
Total SDRAM
Start time
Uptime
Slot 7 information:
State
Temperature
Total CPU DRAM
Total SRAM
Total SDRAM
Start time
Uptime
38
2048
64
1280
43
2048
128
2560
43
2048
128
2560
42
2048
128
2560
45
2048
64
1280
Online
MB
MB
MB
2010-10-04 20:06:22 PDT
1 hour, 32 minutes, 51 seconds
Online
MB
MB
MB
2010-10-04 20:06:37 PDT
Online
MB
MB
MB
2010-10-04 20:06:40 PDT
Online
MB
MB
MB
2010-10-04 20:06:42 PDT
Online
MB
MB
MB
2010-10-04 20:06:43 PDT
lcc2-re0:
-------------------------------------------------------------------------Slot 0 information:
State
Online
Temperature
Total CPU DRAM
2048 MB
Total SRAM
128 MB
Total SDRAM
2560 MB
Start time
2010-10-04 20:06:35 PDT
Uptime
Slot 2 information:
State
Online
Temperature
Total CPU DRAM
2048 MB
Total SRAM
128 MB
Total SDRAM
2560 MB
Start time
2010-10-04 20:06:37 PDT
Uptime
Slot 3 information:
State
Online
474
Temperature
Total CPU DRAM
Total SRAM
Total SDRAM
Start time
Uptime
Slot 4 information:
State
Temperature
Total CPU DRAM
Total SRAM
Total SDRAM
Start time
Uptime
Slot 6 information:
State
Temperature
Total CPU DRAM
Total SRAM
Total SDRAM
Start time
Uptime
Slot 7 information:
State
Temperature
Total CPU DRAM
Total SRAM
Total SDRAM
Start time
Uptime
40
2048
64
1280
33
1024
64
1280
43
2048
128
2560
46
2048
64
1280

MB
MB
MB
2010-10-04 20:06:28 PDT
Online
MB
MB
MB
2010-10-04 20:08:03 PDT
Online
MB
MB
MB
2010-10-04 20:06:44 PDT
Online
MB
MB
MB
2010-10-04 20:06:46 PDT
lcc3-re0:
-------------------------------------------------------------------------Slot 2 information:
State
Online
Temperature
Total CPU DRAM
2048 MB
Total SRAM
128 MB
Total SDRAM
2560 MB
Start time
2010-10-04 20:17:31 PDT
Uptime
Slot 4 information:
State
Online
Temperature
Total CPU DRAM
2048 MB
Total SRAM
128 MB
Total SDRAM
2560 MB
Start time
2010-10-04 20:17:34 PDT
Uptime
Slot 5 information:
State
Online
Temperature
Total CPU DRAM
2048 MB
Total SRAM
128 MB
Total SDRAM
2560 MB
Start time
2010-10-04 20:17:36 PDT
Uptime
Slot 6 information:
State
Online
Temperature
Total CPU DRAM
2048 MB
475
Total SRAM
Total SDRAM
Start time
Uptime
Slot 7 information:
State
Temperature
Total CPU DRAM
Total SRAM
Total SDRAM
Start time
Uptime
show chassis fpc

pic-status (TX Matrix
Plus Router)
128 MB
2560 MB
2010-10-04 20:17:39 PDT
42
2048
64
1280
Online
MB
MB
MB
2010-10-04 20:17:41 PDT

lcc0-re0:
-------------------------------------------------------------------------Slot 1
Online
FPC Type 2-ES
PIC 0 Online
8x 1GE(LAN), IQ2
Slot 2
Online
FPC Type 4-ES
PIC 0 Online
Slot 4
Online
FPC Type 4-ES
PIC 0 Online
Slot 6
Online
FPC Type 4-ES
PIC 0 Online
PIC 1 Online
Slot 7
Online
FPC Type 3-ES
PIC 0 Online
PIC 2 Online
1x OC-192 SM SR2
PIC 3 Online
lcc2-re0:
-------------------------------------------------------------------------Slot 0
Online
FPC Type 4-ES
PIC 0 Online
Slot 2
Online
FPC Type 4-ES
PIC 0 Online
PIC 1 Online
Slot 3
Online
FPC Type 2-ES
PIC 0 Online
8x 1GE(LAN), IQ2
Slot 4
Online
FPC Type 4
PIC 0 Online
10x10GE(LAN/WAN) SFPP
Slot 6
Online
FPC Type 4-ES
PIC 0 Online
4x OC-192 SONET XFP
Slot 7
Online
FPC Type 3-ES
PIC 0 Online
PIC 1 Offline
1x 10GE(LAN/WAN) IQ2E
PIC 2 Online
1x OC-192 SM SR2
PIC 3 Online
1x Tunnel
lcc3-re0:
-------------------------------------------------------------------------Slot 2
Online
FPC Type 4-ES
PIC 0 Online
Slot 4
Online
FPC Type 4-ES
PIC 0 Online
4x OC-192 SONET XFP
Slot 5
Online
FPC Type 4-ES
PIC 0 Online
4x OC-192 SONET XFP
PIC 1 Online
Slot 6
Online
FPC Type 4-ES
PIC 1 Online
476
Slot 7
PIC 0
PIC 1
PIC 2
show chassis fpc

(T1600 Router)

(T1600 Router)
Online
Online
Online
Online
FPC Type 3-ES

8x 1GE(TYPE3), IQ2E
4x OC-48 SONET

Temp
Slot State
(C)
0 Empty
1 Empty
2 Online
49
3 Online
46
4 Empty
5 Online
46
6 Empty
7 Online
44
CPU Utilization (%)

Total Interrupt
3
6
0
0
2048
2048
3
6
24
24
2048
24
1024
49

Slot 2 information:
State
Temperature
Total CPU DRAM
Total SRAM
Total SDRAM
Start time
Uptime
Slot 3 information:
State
Temperature
Total CPU DRAM
Total SRAM
Total SDRAM
Start time
Uptime
Slot 5 information:
State
Temperature
Total CPU DRAM
Total SRAM
Total SDRAM
Start time
Uptime
Slot 7 information:
State
Temperature
Total CPU DRAM
Total SRAM
Total SDRAM
Start time
Uptime
show chassis fpc slot

(T1600 Router)
Memory
Utilization (%)
DRAM (MB) Heap
Buffer
49
2048
64
1280
47
2048
128
2560
46
2048
64
1280
44
1024
64
1280
Online
MB
MB
MB
2010-10-04 21:12:52 PDT
Online
MB
MB
MB
2010-10-04 21:13:06 PDT
Online
MB
MB
MB
2010-10-04 21:12:56 PDT
Online
MB
MB
MB
2010-10-04 21:14:34 PDT
user@host> show chassis fpc slot 2
Slot State
2 Online
Temp
(C)
49
CPU Utilization (%)

Total Interrupt
3
0
Memory
Utilization (%)
DRAM (MB) Heap
Buffer
2048
3
24
477
show chassis fpc

pic-status (T1600
Router)
show chassis fpc

(T4000 Router)
Slot 2
PIC 0
PIC 1
PIC 3
Slot 3
PIC 0
PIC 1
Slot 5
PIC 0
PIC 1
PIC 2
PIC 3
Slot 7
PIC 0
Online
Online
Online
Online
Online
Online
Online
Online
Online
Online
Online
Online
Online
Online
FPC Type 1-ES

Load Type 1
4x 1GE(LAN), IQ2E
1x OC-12-3 SFP
FPC Type 4-ES
4x OC-192 SONET XFP
FPC Type 2-ES
Load Type 2
8x 1GE(LAN), IQ2E
8x 1GE(LAN), IQ2E
1x OC-48-12-3 SFP
FPC Type 4
regress@stymphalian# run show chassis fpc

Slot State
(C) Total Interrupt
0 Online
48
15
0
1 Empty
2 Empty
3 Online
51
15
0
4 Empty
5 Online
39
8
0
6 Online
49
15
0
7 Empty

(T4000 Router)
478

Slot 0 information:
State
Temperature
Total CPU DRAM
Total SRAM
Total SDRAM
Start time
Uptime
Slot 3 information:
State
Temperature
Total CPU DRAM
Total SRAM
Total SDRAM
Start time
Uptime
Slot 5 information:
State
Temperature
Total CPU DRAM
Total SRAM
Total SDRAM
Start time
Uptime
Slot 6 information:
State
Memory
Utilization (%)
DRAM (MB) Heap
Buffer
2816
21
27
2816
21
27
2048
2816
6
21
23
27
Online
2816 MB
1554 MB
10752 MB
2012-02-09 22:56:25 PST
Online
2816 MB
1554 MB
10752 MB
2012-02-09 22:56:22 PST
39
2048
128
2560
Online
MB
MB
MB
2012-02-09 22:51:27 PST
Online
Temperature
Total CPU DRAM
Total SRAM
Total SDRAM
Start time
Uptime
show chassis fpc

pic-status (T4000
Router)
show chassis fpc (QFX

Series)

2816 MB
1554 MB
10752 MB
2012-02-09 22:56:29 PST

Slot 0
Online
FPC Type 5-3D
PIC 0 Online
12x10GE (LAN/WAN)
PIC 1 Online
12x10GE (LAN/WAN)
Slot 3
Online
FPC Type 5-3D
PIC 0 Online
1x100GE
PIC 1 Online
12x10GE (LAN/WAN)
Slot 5
Online
FPC Type 4-ES
PIC 0 Online
100GE
PIC 1 Online
100GE CFP
Slot 6
Online
FPC Type 5-3D
PIC 0 Online
12x10GE (LAN/WAN)
PIC 1 Online
12x10GE (LAN/WAN)
SFPP
SFPP
SFPP
SFPP
SFPP
user@switch> show chassis fpc

Memory
Utilization (%)
Slot State
(C) Total Interrupt
DRAM (MB) Heap
0 Online
26
2
0
2820
0
Buffer
49

(QFX3500 Switches)
user@switch> show chassis fpc detail

Slot 0 information:
State
Online
Temperature
Total CPU DRAM
2820 MB
Total SRAM
0 MB
Total SDRAM
0 MB
Start time
2010-09-20 01:34:13 PDT
Uptime
show chassis fpc

pic-status (QFX3500
Switches)
user@switch> show chassis fpc pic-status

Slot 0
Online
QFX 48x10G 4x40G Switch
PIC 0 Online
48x 10G-SFP+
PIC 1 Online
15x 10G-SFP+
show chassis fpc

interconnect-device
(QFabric System)
user@switch> show chassis fpc interconnect-device interconnect1

FPC status:
Temp
Slot State
(C)
0 Online
0
1 Online
0
2 Online
0
3 Online
0
4 Online
0
5 Online
0
6 Online
0
7 Online
0
8 Online
0
9 Online
0
10 Online
0
11 Online
0
479
12
13
14
15
Online
Online
Online
Online
0
0
0
0
show chassis fpc

interconnect-device
(QFabric System)
user@switch> show chassis fpc interconnect-device interconnect1 3

FPC status:
Temp
Slot State
(C)
3 Online
0
show chassis fpc

interconnect-device
detail (QFabric
System)
user@switch> show chassis fpc interconnect-device interconnect1 3 detail

Slot 3 information:
State
Online
Temperature
Start time
2011-08-18 10:45:04 PDT
Uptime
1 minute, 49 seconds
show chassis fpc

pic-status
user@switch> show chassis fpc pic-status interconnect-device interconnect1

Slot 0
Online
QFX 16-port QSFP+ Front Card
PIC 0 Online
16x 40G-QSFP+
480
interconnect-device
(QFabric System)
PIC 1 Online
Slot 1
Online
PIC 0 Online
PIC 1 Online
Slot 2
Online
PIC 0 Online
PIC 1 Online
Slot 3
Online
PIC 0 Online
PIC 1 Online
Slot 4
Online
PIC 0 Online
PIC 1 Online
Slot 5
Online
PIC 0 Online
PIC 1 Online
Slot 6
Online
PIC 0 Online
PIC 1 Online
Slot 7
Online
PIC 0 Online
PIC 1 Online
Slot 8
Online
PIC 0 Online
Slot 9
Online
PIC 0 Online
Slot 10 Online
PIC 0 Online
Slot 11 Online
PIC 0 Online
Slot 12 Online
PIC 0 Online
Slot 13 Online
PIC 0 Online
Slot 14 Online
PIC 0 Online
Slot 15 Online
PIC 0 Online
16x 40G-GE
QFX 16-port QSFP+ Front
16x 40G-QSFP+
16x 40G-GE
16x 40G-QSFP+
16x 40G-GE
16x 40G-QSFP+
16x 40G-GE
16x 40G-QSFP+
16x 40G-GE
16x 40G-QSFP+
16x 40G-GE
16x 40G-QSFP+
16x 40G-GE
16x 40G-QSFP+
16x 40G-GE
QFX Fabric Rear Card
16x 40G-GE
16x 40G-GE
16x 40G-GE
16x 40G-GE
16x 40G-GE
16x 40G-GE
16x 40G-GE
16x 40G-GE
Card
Card
Card
Card
Card
Card
Card
show chassis fpc

pic-status node-device
(QFabric System)
user@switch> show chassis fpc pic-status node-device node1

Slot node1 Online
QFX 48x10G 4x40G Switch
PIC 0 Online
48x 10G-SFP+
PIC 1 Online
4x 40G-QSFP+
show chassis fpc

(PTX5000 Packet
Transport Switch)

Temp
Slot State
(C)
0 Empty
1 Empty
2 Online
50
3 Empty
4 Empty
5 Online
48
6 Empty
7 Online
49
CPU Utilization (%)

Total Interrupt
Memory
Utilization (%)
DRAM (MB) Heap
Buffer
2816
27
2816
27
2816
27

Slot 2 information:
481
(PTX5000 Packet
Transport Switch)
show chassis fpc

pic-status (PTX5000
482
State
Temperature
Temperature
Temperature
Temperature
Temperature
Temperature
Temperature
Temperature
Temperature
Temperature
Temperature
Temperature
Total CPU DRAM
Total SRAM
Total SDRAM
Start time
Uptime
Slot 5 information:
State
Temperature
Temperature
Temperature
Temperature
Temperature
Temperature
Temperature
Temperature
Temperature
Temperature
Temperature
Temperature
Total CPU DRAM
Total SRAM
Total SDRAM
Start time
Uptime
Slot 7 information:
State
Temperature
Temperature
Temperature
Temperature
Temperature
Temperature
Temperature
Temperature
Temperature
Temperature
Temperature
Temperature
Total CPU DRAM
Total SRAM
Total SDRAM
Start time
Uptime
35
35
50
54
54
52
61
58
57
58
62
61
2816
0
0
35
34
48
53
54
52
69
56
54
56
59
60
2816
0
0
35
33
50
55
56
56
61
57
55
59
62
62
2816
0
0
Online
degrees C / 95 degrees F (PMB)
degrees C / 95 degrees F (Intake)
degrees C / 122 degrees F (Exhaust A)
degrees C / 129 degrees F (Exhaust B)
degrees C / 129 degrees F (TL0)
degrees C / 125 degrees F (TQ0)
MB
MB
MB
2012-01-12 12:05:42 PST
Online
MB
MB
MB
2012-01-12 12:05:43 PST
Online
MB
MB
MB
2012-01-12 12:05:44 PST

Slot 2
Online
FPC
PIC 0 Online
24x 10GE(LAN) SFP+
Packet Transport
Switch)
PIC 1
Slot 5
PIC 0
PIC 1
Slot 7
PIC 0
PIC 1
show chassis fpc

(ACX2000 Universal
Access Router)

Temp
Slot State
(C)
0 Online
61
CPU Utilization (%)

Total Interrupt
17
6
Memory
Utilization (%)
DRAM (MB) Heap
Buffer
512
21
37
show chassis fpc 0

(ACX2000 Universal
Access Router)
user@host> show chassis fpc 0

Slot State
(C) Total Interrupt
0 Online
61
17
6
Memory
Utilization (%)
DRAM (MB) Heap
Buffer
512
21
37

(ACX2000 Universal
Access Router)

Slot 0 information:
State
Temperature
Total CPU DRAM
Start time
Uptime
show chassis fpc

pic-status (ACX2000
Universal Access
Router)

Slot 0
Online
PIC 0 Online
16x CHE1T1, RJ48
PIC 1 Online
8x 1GE(LAN) RJ45
PIC 2 Online
2x 1GE(LAN) SFP
PIC 3 Online
2x 10GE(LAN) SFP+
show chassis FPC 1

(MX Routers with
[MSB])
user@switch> show chassis fpc 1

Slot State
(C) Total Interrupt
1 Online
34
5
0
show chassis FPC 1

detail (MX Routers
with Media Services
Blade [MSB])
user@switch> show chassis fpc 1 detail

Slot 1 information:
State
Online
Temperature
34
Total CPU DRAM
3072 MB
Total RLDRAM
259 MB
Total DDR DRAM
4864 MB
Start time:
2012-06-19 10:51:43 PDT
Uptime:
550 Watts
Online
Online
Online
Online
Online
Online
Online
24x 10GE(LAN) SFP+

FPC
24x 10GE(LAN) SFP+
2x 40GE CFP
FPC
24x 10GE(LAN) SFP+
2x 40GE CFP
Online
512 MB
2012-05-29 02:52:06 PDT
Memory
Utilization (%)
DRAM (MB) Heap
Buffer
3072
5
13
483
show chassis hardware

Syntax

<detail | extensive>
<clei-models>
<models>
Syntax (EX Series)

<clei-models>
<models>
Syntax (T4000
Router)

<clei-models>
<models>
Syntax (TX Matrix

Router)

<clei-models>
<models>
<lcc number | scc>

Router)

<clei-models>
<models>
Syntax (MX Series

Routers)

<clei-models>
<models>
<all-members>
<local>
<member member-id>
Syntax (MX2010 3D
Universal Edge
Routers)

<clei-models>
<models>
Syntax (MX2020 3D
Universal Edge
Routers)

<clei-models>
<models>
Syntax (QFX Series)

<clei-models>
<node-device name>
<models>
484
Syntax (PTX Series

Packet Transport
Switches)

<clei-models>
<models>
Syntax (ACX Series

Universal Access
Routers)

<clei-models>
<models>
Release Information
Description

models option introduced in Junos OS Release 8.2.
Display a list of all Flexible PIC Concentrators (FPCs) and PICs installed in the router or
switch chassis, including the hardware version level and serial number.
In the EX Series switch command output, FPC refers to the following:
On EX2200 switches, EX3200 switches, EX4200 standalone switches, and EX4500

switchesRefers to the switch; FPC number is always 0.
On EX4200 switches in a Virtual Chassis configurationRefers to the member of a

Virtual Chassis; FPC number equals the member ID, from 0 through 9.
On EX8208 and EX8216 switchesRefers to a line card; FPC number equals the slot
number for the line card.
On a QFX3500 standalone switch, both the FPC and FPC number are always 0.
On Type 5 FPC on T4000 routers, there are no top temperature sensor or bottom
temperature sensor parameters. Instead, fan intake temperature sensor and fan exhaust
temperature sensors parameters are displayed.
Options
noneDisplay information about hardware. For a TX Matrix router, display information
about the TX Matrix router and its attached T640 routers. For a TX Matrix Plus router,
display information about the TX Matrix Plus router and its attached T1600 routers.
clei-models(Optional) Display Common Language Equipment Identifier (CLEI) barcode
and model number for orderable field-replaceable units (FRUs).

detail(Optional) Include RAM and disk information in output.
extensive(Optional) Display ID EEPROM information.
all-members(MX Series routers only) (Optional) Display hardware-specific information
for all the members of the Virtual Chassis configuration.
485
interconnect-device name(QFabric systems only) (Optional) Display hardware-specific
information for the Interconnect device.

display hardware information for a specified T640 router (or line-card chassis) that
is connected to the TX Matrix router. On a TX Matrix Plus router, display hardware
information for a specified T1600 router (or line-card chassis) that is connected to
the TX Matrix Plus router. Replace number with a value from 0 through 3.
local(MX Series routers only) (Optional) Display hardware-specific information for the
local Virtual Chassis members.

member member-id(MX Series routers only) (Optional) Display hardware-specific
information for the specified member of the Virtual Chassis configuration. Replace
models(Optional) Display model numbers and part numbers for orderable FRUs and,
for components that use ID EEPROM format v2, the CLEI code.
node-device name(QFabric systems only) (Optional) Display hardware-specific
information for the Node device.

scc(TX Matrix router only) (Optional) Display hardware information for the TX Matrix
router (or switch-card chassis).

sfc number(TX Matrix Plus router only) (Optional) Display hardware information for
the TX Matrix Plus router (or switch-fabric chassis). Replace number with 0.
The show chassis hardware detail command now displays DIMM information for the
following Routing Engines:
Table 39: Routing Engines Displaying DIMM Information

Routing Engines
Routers
RE-S-1800x2 and RE-S-1800x4
MX240, MX480, and MX960 routers
RE-A-1800x2
M120 and M320 routers
Required Privilege
Level
Related
Documentation
486
view
show chassis power
show chassis hardware (EX8216 Switch) on page 492

show chassis hardware clei-models (EX8216 Switch) on page 493
show chassis hardware clei-models (T1600 Router) on page 493
show chassis hardware detail (EX4200 Switch) on page 494
show chassis hardware models (EX4500 Switch) on page 494
show chassis hardware (J6350 Router) on page 494
show chassis hardware (J6300 Router) on page 494
show chassis hardware (M7i Router) on page 495

show chassis hardware (M10 Router) on page 495
show chassis hardware models (M10 Router) on page 496
show chassis hardware (M40e Router) on page 498
show chassis hardware detail (M120 Router) on page 499
show chassis hardware detail (M160 Router) on page 502
show chassis hardware (MX5 Router) on page 504
show chassis hardware (Fixed MX80 Router) on page 506
show chassis hardware (Modular MX80 Router) on page 506
show chassis hardware detail (MX 240 Router with Routing Engine Displaying DIMM
information) on page 508
show chassis hardware (MX240 Router with Enhanced MX SCB) on page 509
show chassis hardware (MX960 Router with Bidirectional Optics) on page 511
show chassis hardware models (MX960 Router with Enhanced MX SCB) on page 513
show chassis hardware detail (MX960 Router) on page 514
show chassis hardware extensive (MX2010 Router) on page 521
show chassis hardware models (MX2010 Router) on page 527
show chassis hardware clei-models (MX2010 Routers) on page 527
show chassis hardware models (MX2020 Router) on page 545
show chassis hardware clei-models (MX2020 Router) on page 547
show chassis hardware (MX Series routers with ATM MIC) on page 548
show chassis hardware (MX240, MX480, MX960 routers with Application Services
Modular Line Card) on page 548
show chassis hardware extensive (MX240, MX480, MX960 routers with Application
show chassis hardware (T320 Router) on page 550
show chassis hardware models (T640 Router) on page 552
show chassis hardware extensive (T640 Router) on page 552
487

show chassis hardware (T4000 Router with 16 GB line card chassis (LCC) Routing
Engine) on page 555
show chassis hardware clei-models (T4000 Router) on page 556
show chassis hardware detail (T4000 Router) on page 556
show chassis hardware models (T4000 Router) on page 558
show chassis hardware lcc (TX Matrix Router) on page 559
show chassis hardware scc (TX Matrix Router) on page 560
show chassis hardware (TX Matrix Plus Router) on page 562
show chassis hardware sfc (TX Matrix Plus Router) on page 567
show chassis hardware extensive (TX Matrix Plus Router) on page 568
show chassis hardware clei-models (TX Matrix Plus Router) on page 570
show chassis hardware detail (TX Matrix Plus Router) on page 572
show chassis hardware models (TX Matrix Plus Router) on page 574
show chassis hardware (16-Port 10-Gigabit Ethernet MPC with SFP+ Optics [MX Series
Routers]) on page 576
show chassis hardware (MPC3E [MX Series Routers]) on page 577
show chassis hardware (QFX3500 Switches) on page 578
show chassis hardware detail (QFX3500 Switches) on page 578
show chassis hardware models (QFX3500 Switches) on page 580
show chassis hardware clei-models (QFX3500 Switches) on page 580
show chassis hardware interconnect-device (QFabric Systems) on page 580
show chassis hardware node-device (QFabric Systems) on page 580
show chassis hardware (PTX5000 Packet Transport Switch) on page 580
show chassis hardware clei-models (PTX5000 Packet Transport Switch) on page 581
show chassis hardware detail (PTX5000 Packet Transport Switch) on page 582
show chassis hardware models (PTX5000 Packet Transport Switch) on page 584
show chassis hardware extensive (PTX5000 Packet Transport Switch) on page 584
show chassis hardware (MX Routers with Media Services Blade [MSB]) on page 585
show chassis hardware extensive (MX Routers with Media Services Blade
[MSB]) on page 585
Output Fields
488
Table 40 on page 489 lists the output fields for the show chassis hardware command.
Table 40: show chassis hardware Output Fields

Field Name
Field Description
Level of Output
Item
Chassis component:
All levels
(EX Series switches)Information about the chassis, Routing Engine (SRE

and Routing Engine modules in EX8200 switches), power supplies, fan trays,
and LCD panel. Also displays information about Flexible PIC Concentrators
(FPCs) and associated Physical Interface Cards (PICs). Information about
the backplane, midplane, and SIBs (SF modules) is displayed for EX8200
switches. See EX Series Switches Hardware and CLI Terminology Mapping.
(MX Series routers)Information about the backplane, Routing Engine, Power

Entry Modules (PEMs), and fan trays. Also displays information about Flexible
PIC Concentrators (FPCs) and associated Physical Interface Cards (PICs),
Modular Port Concentrators (MPCs) and associated Modular Interface Cards
(MICs), or Dense Port Concentrators (DPCs). MX80 routers have a single
Routing Engine and a built-in Packet Forwarding Engine that attaches directly
to MICs. The Packet Forwarding Engine has two pseudo FPCs (FPC 0 and
FPC1). MX80 routers also have a Forwarding Engine Board (FEB).
(M Series routers, except for the M320 router)Information about the

backplane; power supplies; fan trays; Routing Engine; maxicab (the connection
between the Routing Engine and the backplane, for the M40 router only);
SCB, SSB, SFM, or FEB; MCS and PCG (for the M160 router only); each FPC
and PIC; and each fan, blower, and impeller.
(M120, M320, and T Series routers)Information about the backplane, power

supplies, fan trays, midplane, FPM (craft interface), CIP, PEM, SCG, CB, FPC,
PIC, SFP, SPMB, and SIB.
(QFX Series)Information about the chassis, Routing Engine, power supplies,

fan trays, Interconnect devices, and Node devices. Also displays information
about Flexible PIC Concentrators (FPCs) and associated Physical Interface
Cards (PICs).
(PTX Series)Information about the chassis, midplane, craft interface (FPM),

power distribution units (PDUs) and Power Supply Modules (PSMs),
Centralized Clock Generators (CCGs), Routing Engines, Control Boards (CBs)
and Switch Processor Mezzanine Boards (SPMBs), Flexible PIC Concentrators
(FPCs), PICs, Switch Interface Boards (SIBs), and fan trays (vertical and
horizontal).
(MX2010 and MX2020 routers)Information about the chassis, midplane,

craft interface (FPM), power midplane (PMP), Power Supply Modules (PSMs),
Power Distribution Modules (PDMs), Routing Engines, Control Boards (CBs)
and Switch Processor Mezzanine Boards (SPMBs), Switch Fabric Boards
(SFBs), Flexible PIC Concentrators (FPCs), PICs, adapter cards (ADCs) and
fan trays.
Version
Revision level of the chassis component.
All levels
Part number
Part number of the chassis component.
All levels
Serial number
Serial number of the chassis component. The serial number of the backplane
is also the serial number of the router chassis. Use this serial number when you
need to contact Juniper Networks Customer Support about the router or switch
chassis.
All levels
Assb ID or
Assembly ID
(extensive keyword only) Identification number that describes the FRU hardware.
extensive
489
Table 40: show chassis hardware Output Fields (continued)

Field Name
Field Description
Level of Output
Assembly Version
(extensive keyword only) Version number of the FRU hardware.
extensive
Assembly Flags
(extensive keyword only) Flags.
extensive
FRU model number
(clei-models, extensive, and models keyword only) Model number of the FRU
hardware component.
none specified
CLEI code
(clei-models and extensive keyword only) Common Language Equipment

Identifier code. This value is displayed only for hardware components that use
ID EEPROM format v2. This value is not displayed for components that use ID
EEPROM format v1.
none specified
EEPROM Version
ID EEPROM version used by the hardware component: 0x00 (version 0), 0x01
(version 1), or 0x02 (version 2).
extensive
Description
Brief description of the hardware item:
All levels
Type of power supply.
Type of PIC. If the PIC type is not supported on the current software release,
the output states Hardware Not Supported.
Type of FPC: FPC Type 1, FPC Type 2, FPC Type 3, FPC Type 4 , or FPC
TypeOC192.
On EX Series switches, a brief description of the FPC.
On the J Series routers, the FPC type corresponds to the Physical Interface
Module (PIM). The following list shows the PIM abbreviation in the output
and the corresponding PIM name.
2x FEEither two built-in Fast Ethernet interfaces (fixed PIM) or dual-port
Fast Ethernet PIM
4x FE4-port Fast Ethernet ePIM
1x GE CopperCopper Gigabit Ethernet ePIM (one 10-Mbps, 100-Mbps, or
1000-Mbps port)
1x GE SFPSFP Gigabit Ethernet ePIM (one fiber port)
4x GE Base PICFour built-in Gigabit Ethernet ports on a J4350 or J6350
chassis (fixed PIM)
2x SerialDual-port serial PIM
2x T1Dual-port T1 PIM
2x E1Dual-port E1 PIM
2x CT1E1Dual-port channelized T1/E1 PIM
1x T3T3 PIM (one port)
1x E3E3 PIM (one port)
4x BRI S/T4-port ISDN BRI S/T PIM
4x BRI U4-port ISDN BRI U PIM
1x ADSL Annex AADSL 2/2+ Annex A PIM (one port, for POTS)
1x ADSL Annex BADSL 2/2+ Annex B PIM (one port, for ISDN)
2x SHDSL (ATM)G SHDSL PIM (2-port two-wire module or 1-port four-wire
module)
490
Table 40: show chassis hardware Output Fields (continued)

Field Name
Field Description
1x TGM550TGM550 Telephony Gateway Module (Avaya VoIP gateway

module with one console port, two analog LINE ports, and two analog
TRUNK ports)
1x DS1 TIM510TIM510 E1/T1 Telephony Interface Module (Avaya VoIP
Level of Output
media module with one E1 or T1 trunk termination port and ISDN PRI
backup)
4x FXS, 4xFX0, TIM514TIM514 Analog Telephony Interface Module (Avaya

VoIP media module with four analog LINE ports and four analog TRUNK
ports)
4x BRI TIM521TIM521 BRI Telephony Interface Module (Avaya VoIP media
module with four ISDN BRI ports)
Crypto Accelerator ModuleFor enhanced performance of cryptographic
algorithms used in IP Security (IPsec) services
MPC M 16x 10GE16-port 10-Gigabit Module Port Concentrator that supports
SFP+ optical transceivers. (Not on EX Series switches.)
For hosts, the Routing Engine type.
For small form-factor pluggable transceiver (SFP) modules, the type of fiber:
LX, SX, LH, or T.
LCD description for EX Series switches (except EX2200 switches).
MPC21-port MPC2 that supports two separate slots for MICs.
MPC3E1-port MPC3E that supports two separate slots for MICs
(MIC-3D-1X100GE-CFP and MIC-3D-20GE-SFP) on MX960, MX480, and

MX240 routers. The MPC3E maps one MIC to one PIC (1 MIC, 1 PIC), which
differs from the mapping of legacy MPCs.
100GBASE-LR4, pluggable CFP optics
Supports the Enhanced MX Switch Control Board with fabric redundancy

and existing SCBs without fabric redundancy.
Interoperates with existing MX Series line cards, including Flexible Port

Concentrators (FPC), Dense Port Concentrators (DPCs), and Modular Port
Concentrators (MPCs).
LCD description for MX Series routers
491
Sample Output
(EX8216 Switch)
492
user@host> show chassis hardware

Hardware inventory:
Item
Version Part number
Chassis
REV 06
Midplane
REV 06
710-016845
CB 0
REV 22
710-020771
CB 1
REV 22
710-020771
Routing Engine 1
BUILTIN
FPC 3
REV 19
710-020683
CPU
REV 13
710-020598
FPC 4
REV 17
710-020683
CPU
REV 10
710-020598
PIC 0
BUILTIN
Base-X
Xcvr 1
REV 01
740-011613
Xcvr 11
REV 01
740-011613
Xcvr 12
REV 01
740-011613
Xcvr 13
REV 01
740-011613
Xcvr 14
REV 01
740-011613
Xcvr 15
REV 01
740-011613
Xcvr 21
REV 01
740-011613
Xcvr 22
REV 01
740-011613
Xcvr 23
REV 01
740-011613
Xcvr 24
REV 01
740-011613
Xcvr 25
REV 01
740-011613
Xcvr 26
REV 01
740-011613
Xcvr 27
REV 01
740-011613
Xcvr 28
REV 01
740-011782
Xcvr 29
REV 01
740-011613
Xcvr 30
REV 01
740-011613
Xcvr 31
REV 01
740-011613
Xcvr 32
REV 01
740-011613
Xcvr 33
REV 01
740-011613
Xcvr 34
REV 01
740-011613
Xcvr 35
REV 01
740-011613
Xcvr 36
REV 01
740-011613
Xcvr 37
REV 01
740-011613
Xcvr 38
REV 01
740-011613
Xcvr 39
REV 01
740-011613
Xcvr 40
REV 01
740-011613
Xcvr 41
REV 01
740-011613
Xcvr 43
REV 01
740-011613
Xcvr 45
REV 01
740-011613
FPC 13
REV 16
710-016837
CPU
SIB 0
REV 10
710-021613
SIB 1
REV 10
710-021613
SIB 2
REV 10
710-021613
SIB 3
REV 10
710-021613
SIB 4
REV 10
710-021613
SIB 5
REV 10
710-021613
SIB 6
REV 10
710-021613
SIB 7
REV 10
710-021613
PSU 0
REV 17
740-021466
PSU 1
REV 17
740-021466
PSU 2
REV 17
740-021466
PSU 3
REV 17
740-021466
PSU 4
REV 17
740-021466
Serial number
CY0109220035
BA0909120112
AX0109197723
AX0109197726
BUILTIN
BC0109083125
BF0109144549
BC0108500127
BF0108460510
BUILTIN
Description
EX8216
EX8216-MP
EX8216-RE320
EX8216-RE320
RE-EX8216
EX8200-48F
EX8200-CPU
EX8200-48F
EX8200-CPU
48x 100 Base-QFX/1000
PE70V89
PE70YCE
PE70VSH
E08C02063
PE70VKU
E08E03372
PE70VAD
E08E01228
PE70VSL
E08E03409
PE70VL4
PDQ4L2Z
PE70WFK
PBD2B5U
PE70UQX
PE70VL5
PE70V0F
E08C02052
E08C02197
PE70V0L
E08E03390
PDQ4VL9
E08E03370
E08E03362
E08C02065
E08E03405
E08E03411
E08C02171
E08E03410
BB0109051344
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
EX8200-8XS
AY0109166244
AY0109166357
AY0109166362
AY0109166338
AY0109166350
AY0109166365
AY0109166361
AY0109166399
BG0709170003
BG0709170004
BG0709170020
BG0709170017
BG0709170008
EX8216-SF320
EX8216-SF320
EX8216-SF320
EX8216-SF320
EX8216-SF320
EX8216-SF320
EX8216-SF320
EX8216-SF320
EX8200-AC2K
EX8200-AC2K
EX8200-AC2K
EX8200-AC2K
EX8200-AC2K
PSU 5
Top Fan Tray
FTC 0
FTC 1
Bottom Fan Tray
FTC 0
FTC 1
LCD 0

clei-models (EX8216
Switch)

clei-models (T1600
Router)
REV 17
740-021466
BG0709170018
EX8200-AC2K
REV 4
REV 4
760-022620
760-022620
CX1209140212
CX1209140212
EX8216-FT
EX8216-FT
REV 4
REV 4
REV 04
760-022620
760-022620
710-025742
CX1209140211
CX1209140211
CE0109186919
EX8216-FT
EX8216-FT
EX8200 LCD
user@host> show chassis hardware clei-models

Hardware inventory:
Item
Version Part number CLEI code
Midplane
REV 08
710-016845
PSU 0
REV 05
740-023002
COUPAEAEAA
PSU 1
REV 05
740-023002
COUPAEAEAA
PSU 2
REV 05
740-023002
COUPAEAEAA
PSU 3
REV 05
740-023002
COUPAEAEAA
PSU 4
REV 05
740-023002
COUPAEAEAA
PSU 5
REV 05
740-023002
COUPAEAEAA
Top Fan Tray
Bottom Fan Tray

Hardware inventory:
Item
Midplane
REV 03
710-005608
FPM Display
REV 05
710-002897
CIP
REV 06
710-002895
PEM 0
Rev 07
740-017906
IPUPAC7KTA
PEM 1
Rev 18
740-002595
SCG 0
REV 15
710-003423
Routing Engine 0 REV 08
740-014082
740-014082
CB 0
REV 05
710-007655
CB 1
REV 03
710-017707
FPC 0
REV 07
710-013558
PIC 0
REV 01
750-010618
PIC 1
REV 06
750-001900
PIC 2
REV 14
750-001901
PIC 3
REV 07
750-001900
FPC 1
REV 06
710-013553
PIC 0
REV 08
750-001072
PIC 1
REV 10
750-012266
PIC 2
REV 22
750-005634
FPC 2
PIC 0
REV 16
750-007141
PIC 1
REV 06
750-015217
PIC 2
REV 05
750-004695
PIC 3
REV 17
750-009553
FPC 3
REV 01
710-010154
PIC 0
REV 07
750-012793
PIC 1
REV 25
750-007141
PIC 2
REV 17
750-009553
PIC 3
REV 32
750-003700
FPC 4
REV 16
710-013037
PIC 1
REV 06
750-034781
FPC 5
REV 02
710-013037
PIC 0
REV 16
750-012518
PIC 1
REV 01
750-010850
FPC 6
REV 14
710-013037
FRU model number

EX8200-PWR-AC3KR
EX8200-PWR-AC3KR
EX8200-PWR-AC3KR
EX8200-PWR-AC3KR
EX8200-PWR-AC3KR
EX8200-PWR-AC3KR
FRU model number

CHAS-BP-T640-S
CRAFT-T640-S
CIP-L-T640-S
PWR-T1600-3-80-DC-S
PWR-T-DC-S
SCG-T-S
RE-A-2000-4096-S
RE-A-2000-4096-S
CB-T-S
CB-T-S
T640-FPC2-E2
PB-4GE-SFP
PB-1OC48-SON-SMSR
PB-4OC12-SON-SMIR
PB-1OC48-SON-SMSR
T640-FPC1-E2
P-1GE-SX
PB-4GE-TYPE1-SFP-IQ2
PB-1CHOC12SMIR-QPP
PC-10GE-SFP
PC-8GE-TYPE3-SFP-IQ2
PC-TUNNEL
PC-4OC48-SON-SFP
T640-FPC3-E
PC-1XGE-TYPE3-XFP-IQ2
PC-10GE-SFP
PC-4OC48-SON-SFP
PC-1OC192-SON-VSR
T1600-FPC4-ES
PD-1CE-CFP
T1600-FPC4-ES
PD-4OC192-SON-XFP
PD-1OC768-SON-SR
T1600-FPC4-ES
493
PIC 0
PIC 1
FPC 7
PIC 0
PIC 1
PIC 2
PIC 3
SIB 0
SIB 1
SIB 2
SIB 3
SIB 4
Fan Tray 0
Fan Tray 1
Fan Tray 2
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
11
13
09
10
01
01
15
07
07
07
07
07
750-017405
750-017405
710-007529
750-012793
750-015217
750-015217
750-009450
710-013074
710-013074
710-013074
710-013074
710-013074

detail (EX4200
Switch)
user@host> show chassis hardware detail

Hardware inventory:
Item
Version Part number
Chassis
750-021256
Routing Engine 0
FPC 0
REV 11
750-021256
CPU
BUILTIN
PIC 0
BUILTIN
PIC 1
REV 03B 711-021270
BRD
REV 08
711-021264
Power Supply 0
REV 03
740-020957
Fan Tray

models (EX4500
Switch)
user@host> show chassis hardware models

Hardware inventory:
Item
Version Part number
750-035700
FPC 0
REV 01
750-035700
PIC 0
BUILTIN
Power Supply 1
REV 01
740-029654

(J6350 Router)

Hardware inventory:
Item
Version Part number
Chassis
Midplane
REV 03
710-014593
System IO
REV 01
710-016210
Crypto Module
Routing Engine
REV 08
710-015273
ad0
248 MB 256MB CKS
Flash
FPC 0
PIC 0
FPC 1
REV 06
750-010355
PIC 0
FPC 3
REV 06
750-011148
PIC 0
FPC 6
REV 06
750-013492
PIC 0
Power Supply 0
494
PD-4XGE-XFP
PD-4XGE-XFP
T640-FPC3
PC-1OC192-SON-SR2
SIB-I-T1600-S
SIB-I-T1600-S
SIB-I-T1600-S
SIB-I-T1600-S
SIB-I-T1600-S
FANTRAY-T-S
FANTRAY-T-S
FAN-REAR-TX-T640-S
Serial number
BM0208327733
BM0208327733
BM0208327733
BM0208327733
BUILTIN
BUILTIN
AR0208162285
AK0208328289
AT0508346354
Description
EX4200-24T
EX4200-24T, 8 POE
EX4200-24T, 8 POE
EX4200-24T, 8 POE
FPC CPU
24x 10/100/1000 Base-T
4x GE SFP
EX4200-24T, 8 POE
PS 320W AC
Fan Tray
Serial number
GG0210271867
GG0210271867
BUILTIN
H884FS00JC09
FRU model number

EX4500-40F-FB-C
EX4500-40F-FB-C
EX4500-40F-FB-C
EX4500-PWR1-AC-FB
Serial number
JN1090E07ADB
NP1265
NN9950
Description
JSR6350
JX350 System IO
Crypto Acceleration
NM6509
RE-J6350-3400
00102006C24A00000039 Compact
AI07030023
AJ06520151
NC4170
FPC
4x
FPC
2x
FPC
2x
FPC
4x
GE Base PIC
T1
E1
FE

(J6300 Router)

(M7i Router)

Hardware inventory:
Item
Version Part number
Chassis
Midplane
REV 02.04 710-010001
System IO
REV 02.00 710-010003
Routing Engine
RevX2.6 750-010006
FPC 0
PIC 0
FPC 1
RevX2.0 750-011380
PIC 0
FPC 2
RevX2.0 750-011380
PIC 0
FPC 3
REV 03
750-010354
PIC 0

Hardware inventory:
Item
Version Part number
Chassis
Midplane
REV 02
710-008761
Power Supply 0
Rev 04
740-008537
Routing Engine
REV 01
740-008846
CFEB
REV 02
750-009492
FPC 0
PIC 0
REV 04
750-003163
PIC 1
REV 04
750-003163
PIC 2
REV 04
750-003163
PIC 3
REV 02
750-003163
FPC 1
PIC 2
REV 01
750-009487
PIC 3
REV 01
750-009098
Hardware inventory:
Item
Version
Chassis
Midplane
REV 05
Power Supply 0
Rev 08
Routing Engine
REV 07
CFEB
REV 09
FPC 0
PIC 0
REV 12
Xcvr 0
REV 01
Xcvr 1
REV 01
Xcvr 2
REV 01
Xcvr 3
PIC 1
REV 03
Xcvr 0
REV 01
Xcvr 1
REV 01
Xcvr 3
REV 01
PIC 2
REV 15
PIC 3
REV 01
FPC 1
PIC 2
PIC 3
REV 09
Xcvr 0
REV 01
Fan Tray
Part number
Serial number
JN000164AB
CORE99570
CORE100848
IWGS40735390
N3960005
N3960002
N0780028
Serial number
31959
CA0209
PD10272
1000396803
CA0166
HJ6416
HJ6423
HJ6421
HJ0425
HM2275
CA0142
710-008761
740-008537
740-011202
750-010463
Serial number
B1157
DM0840
TE53755
1000736567
DK6952
750-012838
740-011614
740-011615
740-011614
NON-JNPR
750-023116
740-012434
740-012434
740-016064
750-014895
750-025390
DL7993
PD94TDJ
PAD5EER
PD94THU
PDC2E7A
JT0203
AGT063832PS
AGT063832LY
C06J19018
DM5757
JW9448
BUILTIN
750-009099
740-012434
BUILTIN
DM0899
AGT07150HGJ
Description
J6300
System IO board
RE-J.3
FPC
2x FE
FPC
1xADSL pic Annex A
FPC
1xADSL pic Annex B
FPC
1x T3
Description
M7i
M7i Midplane
AC Power Supply
RE-5.0
Internet Processor IIv1
E-FPC
E-FPC
ASP - Integrated
2x F/E, 100 BASE-TX
Description
M7i
M7i Midplane
AC Power Supply
RE-850
E-FPC
4x 1GE(LAN), IQ2
SFP-LX10
UNSUPPORTED
SFP-LX10
SFP-LX10
4x CHSTM1 SDH CE SFP
SFP-SR
SFP-SR
SFP-LR
MultiServices 100
12x T1/E1 CE
E-FPC
1x Tunnel
1x G/E, 1000 BASE
UNSUPPORTED
Rear Fan Tray

Hardware inventory:
495
(M10 Router)

models (M10 Router)

(M20 Router)
496
Item
Chassis
Midplane
Power supply A
Power supply B
Display
Host
FEB
FPC 0
PIC 0
PIC 1
FPC 1
Fan Tray 0
Fan Tray 1
Version
Part number
REV 01
710-001948
Serial number
1122
S/N AC6626
S/N LC36095
S/N LC36100
S/N AC6656
18000005dfb3fb01
S/N AC6632
REV
Rev
Rev
REV
710-001950
740-002497
740-002497
710-001995
REV 08
REV 01
750-001072
750-000613
S/N AB2485
S/N AA1048
1.1
01
01
1.2

Hardware inventory:
Item
Version Part number
Midplane
REV 04
710-008920
Power Supply 0
Rev 06
740-008537
Power Supply 1
Rev 06
740-008537
HCM 0
REV 03
710-010580
HCM 1
REV 03
710-010580
740-009459
CFEB 0
REV 05
750-010465
FPC 0
PIC 0
REV 10
750-002971
PIC 1
REV 11
750-002992
PIC 2
REV 03
750-002977
PIC 3
REV 08
750-005724
FPC 1
PIC 2
REV 12
750-008425
PIC 3
REV 13
750-005636
Fan Tray 0
Fan Tray 1

Hardware inventory:
Item
Version Part number
Chassis
Backplane
REV 07
710-001517
Power supply B
Rev 01
740-001465
Display
REV 02
710-001519
Host 0
SSB slot 0
REV 01
710-001951
SSRAM bank 0
REV 01
710-001385
SSRAM bank 1
REV 01
710-001385
SSRAM bank 2
REV 01
710-001385
SSRAM bank 3
REV 01
710-001385
SSB slot 1
N/A
N/A
FPC 1
REV 01
710-001292
SSRAM
REV 01
710-000077
SDRAM bank 0
REV 01
710-000099
SDRAM bank 1
REV 01
710-000099
PIC 0
REV 03
750-000612
PIC 1
REV 01
750-000616
PIC 2
REV 01
750-000613
PIC 3
REV 01
750-002501
FPC 2
REV 01
710-001292
SSRAM
REV 01
710-000077
Description
M10

AC
AC
teknor
FANTRAY-M10I-S
FANTRAY-M10I-S
CLEI code
FRU model number

CHAS-MP-M10i-S
PWR-M10i-M7i-AC-S
PWR-M10i-M7i-AC-S
HCM-M10i-S
HCM-M10i-S
RE-400-256-S
FEB-M10i-M7i-S
PE-4OC3-SON-MM
PE-4FE-TX
PE-2OC3-ATM-MM
PE-2OC3-ATM2-MM
PE-AS
PE-4CHDS3-QPP
FANTRAY-M10I-S
FANTRAY-M10I-S
Serial number
20033
S/N AA7940
S/N 000001
S/N AA9704
98000004f8f27501
S/N AD5905
S00480
S00490
S001:?
S00483
N/A
S/N AB7528
S/N 304209
S/N 000603
S/N 000414
S/N AB8433
S/N AA1168
S/N AA1008
S/N AD5810
S/N AC0119
S/N 503241
Description
M20
AC
teknor
2 MB
2 MB
2 MB
2 MB
Backup
1 MB
64 MB
64 MB
2x OC-3 ATM, MM
1x OC-12 ATM, MM
4x E3
1 MB
SDRAM bank 0
SDRAM bank 1
Fan Tray 0
Fan Tray 1
Fan Tray 2
Fan Tray 3

models (M20 Router)

(M40 Router)
REV 01
REV 01
710-000099
710-000099

Hardware inventory:
Item
Version Part number
Backplane
REV 03
710-002334
Power Supply A
REV 06
740-001465
Display
REV 04
710-001519
740-003239
740-003239
SSB 0
REV 02
710-001951
SSB 1
N/A
N/A
FPC 0
REV 03
710-003308
PIC 0
REV 08
750-002303
PIC 1
REV 07
750-004745
PIC 2
REV 03
750-002965
FPC 1
REV 03
710-003308
PIC 0
REV 03
750-002914
Fan Tray 0
Fan Tray 1
Fan Tray 2
Fan Tray 3

Hardware inventory:
Item
Version Part number
Backplane
REV 02
710-000073
Power supply A
Rev 2
740-000235
Maxicab
REV X1
710-000229
Minicab
REV X1
710-000482
Display
REV 06
710-000150
Host
SCB
REV X1
710-000075
SSRAM bank 0
REV 02
710-000077
SSRAM bank 1
REV 02
710-000077
SSRAM bank 2
REV 02
710-000077
SSRAM bank 3
REV 02
710-000077
FPC 0
REV 01
710-000175
SSRAM
REV 01
710-000077
SDRAM bank 0
REV 01
710-000099
SDRAM bank 1
REV X1
710-000099
PIC 0
REV 04
750-000613
PIC 1
REV 04
750-000613
PIC 2
REV 04
750-000613
PIC 3
REV 04
750-000613
FPC 2
REV 01
710-000175
SSRAM
REV 02
710-000077
SDRAM bank 0
REV 01
710-000099
SDRAM bank 1
REV 01
710-000099
PIC 0
REV X1
750-000603
PIC 1
REV X1
750-000615
PIC 2
REV X1
750-000611
PIC 3
REV 04
750-000613
FPC 4
REV 01
710-000175
SSRAM
REV 01
710-000077
S/N 306835
S/N 306832
64 MB
64 MB
Front Upper Fan Tray
Front Middle Fan Tray
Front Bottom Fan Tray
Rear Fan Tray
CLEI code
FRU model number

CHAS-MP-M20-S
PWR-M20-AC-S
CRAFT-M20-S
RE-333-768-S
RE-333-768-S
SSB-E-M20
FPC-E
P-4FE-TX
P-2MCDS3
PE-4CHDS3
FPC-E
P-2OC3-ATM-MM
FANTRAY-F-M20-S
FANTRAY-F-M20-S
FANTRAY-F-M20-S
FANTRAY-R-M20-S
Serial number
S/N AA0053
S/N 000042
S/N AAO139
S/N AA0201
S/N AA0905
S/N
S/N
S/N
S/N
S/N
S/N
S/N
S/N
S/N
S/N
S/N
S/N
S/N
S/N
S/N
S/N
S/N
S/N
S/N
S/N
S/N
S/N
S/N
AA0158
AA2267
AA2270
AA2269
AA2268
AA0048
AA2333
AA2332
AA2337
aa0343
AA0379
AA0377
AA0378
AA0042
AA2288
AA2331
AA2330
AA0143
AA0149
AA0148
AA0330
AA0050
AA2327
Description
DC
cpv5000
Internet Processor I
1 MB
1 MB
1 MB
1 MB
1 MB
64 MB
64 MB
1x Tunnel
1 MB
64 MB
64 MB
4x OC-3 SONET, SMIR
4x OC-3 SONET, MM
4x OC-3 SONET, MM
1 MB
497
SDRAM
SDRAM
PIC 0
PIC 2
PIC 3
FPC 5
SSRAM
SDRAM
SDRAM
PIC 1

(M40e Router)

(M120 Router)
498
bank 0
bank 1
bank 0
bank 1
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
01
04
05
08
10
01
01
01
01
710-000099
710-000099
750-000613
750-000616
750-001072
710-000175
710-000077
710-000099
710-000099
750-001323

Hardware inventory:
Item
Version Part number
Chassis
Midplane
REV 01
710-005071
FPM CMB
REV 03
710-001642
FPM Display
REV 03
710-001647
CIP
REV 04
710-002649
PEM 0
Rev 01
740-003787
PEM 1
Rev 01
740-003787
PCG 0
REV 07
710-001568
PCG 1
REV 07
710-001568
Host 0
MCS 0
REV 11
710-001226
SFM 0 SPP
REV 07
710-001228
SFM 0 SPR
REV 05
710-002189
SFM 1 SPP
REV 07
710-001228
SFM 1 SPR
REV 05
710-002189
FPC 0
REV 01
710-011725
CPU
REV 01
710-004600
PIC 0
REV 03
750-003737
FPC 1
REV 01
710-005197
CPU
REV 01
710-004600
PIC 0
REV 07
750-001900
FPC 2
REV 02
710-005197
CPU
REV 01
710-004600
PIC 0
REV 03
750-003737
FPC 4
REV 02
710-005078
CPU
REV 01
710-004600
PIC 0
REV 03
750-001894
PIC 2
REV 01
750-002575
FPC 6
REV 02
710-005078
CPU
REV 01
710-004600
PIC 0
REV 02
750-002911
PIC 2
REV 01
750-002577

Hardware inventory:
Item
Version Part number
Chassis
Midplane
REV 01
710-013667
FPM Board
REV 02
710-011407
FPM Display
REV 02
710-011405
FPM CIP
REV 02
710-011410
PEM 0
Rev 05
740-011936
PEM 1
Rev 05
740-011936
740-014080
CB 0
REV 03
710-011403
CB 1
REV 06
710-011403
S/N
S/N
S/N
S/N
S/N
S/N
S/N
S/N
S/N
S/N
AA2329
AA2328
AA0320
AA1341
AB2462
AA7663
501590
300949
300868
AB1670
64
64
1x
1x
1x
MB
MB
OC-12 SONET, SMIR
OC-12 ATM, MM
G/E, 1000 BASE-SX
1 MB
64 MB
64 MB
1x Tunnel
Serial number
AX3671
AR9074
AR7331
BB4449
MC12364
MC12383
AG1332
AR3789
3e000007c8176601
AN5813
AG4676
AE4735
AP1347
BE0063
BE0669
BD9504
AY3991
BD9842
BB4869
AR8278
BD9824
BD9531
AY3986
BE0664
BD9559
AG7963
AF2472
BE0652
BD9607
AN2286
AP6345
Serial number
JN000054AC
RB4170
CJ9186
CJ9173
CJ9221
RM28320
RM28321
1000642883
CM8346
CP6728
Description
m40e
Power Entry Module

Power Entry Module
Present
M40e-EP-FPC Type 1
M40e-FPC Type 2
M40e-FPC Type 2
M40e-FPC Type 1
4x OC-3 SONET, SMIR
M40e-FPC Type 1
4x F/E, 100 BASE-TX
4x OC-3 SONET, MM
Description
M120
M120 Midplane
M120 FPM Board
M120 FPM Display
M120 FPM CIP
AC Power Entry Module
RE-A-1000
M120 Control Board
M120 Control Board
FPC 1
PIC 0
Xcvr 0
FPC 3
PIC 0
Xcvr 0
Xcvr 1
PIC 1
PIC 2
Xcvr 0
Xcvr 1
PIC 3
Xcvr 0
Xcvr 6
Xcvr 7
Board B
FPC 4
PIC 0
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
03
16
01
01
09
16
01
01
07
01
01
01
02
02
16
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
FPC 5
PIC 0
PIC 1
REV
REV
REV
REV
REV
REV
REV
***
REV
01
740-011782
P922A1F
01
740-011782
P922A16
01
740-011782
P922A0U
01
740-011782
P9229UZ
01
740-009029
P11JXWP
01
740-011613
P9F1ALW
01
710-011388
CJ9088
Hardware Not Supported ***
05
750-012052
NB0410
REV
REV
REV
REV
REV
REV
01
01
01
04
04
04
0
1
2
3
4
6
PIC 2
PIC 3
Board B
FEB 3
FEB 4
FEB 5
Fan Tray 0
Fan Tray 1
Fan Tray 2
Fan Tray 3

detail (M120 Router)
REV 02
710-015908
BUILTIN
740-014279
710-011393
750-008155
740-011613
740-007326
750-007745
750-008155
740-011613
740-011613
750-011800
740-011613
740-011613
740-011782
710-011395
710-011398
750-007141
750-013167
750-010240
710-011390
710-011663
710-011663
710-011663
CP6925
BUILTIN
62E204N00007
CJ9234
NB5229
P9F15JB
P4Q0R9G
CG4360
ND7787
P9F12AS
P9F1ALU
JW1284
P9F1AM6
P9F16NN
P8C29Y7
CN3754
CP6741
NB2855
CM3824
CB5366
CJ9103
CP6673
CJ9368
CJ9386
M120 CFPC 10GE

XFP-10G-LR
M120 FPC Type 2
SFP-SX
SFP-SX
4x OC-3 SONET, SMIR
SFP-SX
SFP-SX
8x 1GE(LAN), IQ2
SFP-SX
SFP-SX
SFP-SX
M120 FPC Mezz
M120 FPC Type 3
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-LX
SFP-SX
M120 FPC Type 1
4x CHDS3 IQ
M120 FPC Mezz Board
M120 FEB
M120 FEB
M120 FEB
Front Top Fan Tray
Rear Top Fan Tray
Rear Bottom Fan Tray

Hardware inventory:
Item
Version Part number Serial number
Description
Chassis
JN000054AC
M120
Midplane
REV 01
710-013667
RB4170
M120 Midplane
FPM Board
REV 02
710-011407
CJ9186
M120 FPM Board
FPM Display
REV 02
710-011405
CJ9173
M120 FPM Display
FPM CIP
REV 02
710-011410
CJ9221
M120 FPM CIP
PEM 0
Rev 05
740-011936
RM28320
PEM 1
Rev 05
740-011936
RM28321
740-014080
1000642883
RE-A-1000
ad0
248 MB SILICONSYSTEMS INC 256M 126CT505S0763SC00110 Compact Flash
ad2
38154 MB HTE541040G9SA00
MPBBT0X2HS2E3M
Hard Disk
CB 0
REV 03
710-011403
CM8346
M120 Control Board
CB 1
REV 06
710-011403
CP6728
M120 Control Board
FPC 1
REV 02
710-015908
CP6925
M120 CFPC 10GE
PIC 0
BUILTIN
BUILTIN
Xcvr 0
REV 01
740-014279
62E204N00007
XFP-10G-LR
FPC 3
REV 03
710-011393
CJ9234
M120 FPC Type 2
PIC 0
REV 16
750-008155
NB5229
Xcvr 0
REV 01
740-011613
P9F15JB
SFP-SX
499
Xcvr 1
PIC 1
PIC 2
Xcvr 0
Xcvr 1
PIC 3
Xcvr 0
Xcvr 6
Xcvr 7
Board B
FPC 4
PIC 0
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
09
16
01
01
07
01
01
01
02
02
16
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
FPC 5
PIC 0
PIC 1
REV
REV
REV
REV
REV
REV
REV
***
REV
01
740-011782
P922A1F
01
740-011782
P922A16
01
740-011782
P922A0U
01
740-011782
P9229UZ
01
740-009029
P11JXWP
01
740-011613
P9F1ALW
01
710-011388
CJ9088
Hardware Not Supported ***
05
750-012052
NB0410
REV
REV
REV
REV
REV
REV
01
01
01
04
04
04
0
1
2
3
4
6
PIC 2
PIC 3
Board B
FEB 3
FEB 4
FEB 5
Fan Tray 0
Fan Tray 1
Fan Tray 2
Fan Tray 3

models (M120 Router)
500
740-007326
750-007745
750-008155
740-011613
740-011613
750-011800
740-011613
740-011613
740-011782
710-011395
710-011398
750-007141
750-013167
750-010240
710-011390
710-011663
710-011663
710-011663

Hardware inventory:
Item
Version Part number
Midplane
REV 01
710-013667
FPM CIP
REV 02
710-011410
PEM 0
Rev 05
740-011936
PEM 1
Rev 05
740-011936
740-014080
CB 0
REV 03
710-011403
CB 1
REV 06
710-011403
FPC 1
REV 02
710-015908
FPC 3
PIC 0
REV 16
750-008155
PIC 1
REV 09
750-007745
PIC 2
REV 16
750-008155
PIC 3
REV 07
750-011800
FPC 4
PIC 0
REV 16
750-007141
FPC 5
PIC 1
REV 05
750-012052
PIC 2
REV 01
750-013167
PIC 3
REV 01
750-010240
Fan Tray 0
Fan Tray 1
Fan Tray 2
Fan Tray 3
P4Q0R9G
CG4360
ND7787
P9F12AS
P9F1ALU
JW1284
P9F1AM6
P9F16NN
P8C29Y7
CN3754
CP6741
NB2855
SFP-SX
4x OC-3 SONET, SMIR
SFP-SX
SFP-SX
8x 1GE(LAN), IQ2
SFP-SX
SFP-SX
SFP-SX
M120 FPC Mezz
M120 FPC Type 3
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-LX
SFP-SX
M120 FPC Type 1
CM3824
CB5366
CJ9103
CP6673
CJ9368
CJ9386
4x CHDS3 IQ
M120 FPC Mezz Board
M120 FEB
M120 FEB
M120 FEB
Front Top Fan Tray
Rear Top Fan Tray
Rear Bottom Fan Tray
CLEI code
FRU model number

CRAFT-M120-S
PWR-M120-AC-S
PWR-M120-AC-S
RE-A-1000-2048-S
CB-M120-S
CB-M120-S
M120-cFPC-1XGE-XFP
PB-2GE-SFP-QPP
PC-4OC3-SON-SMIR
PB-2GE-SFP-QPP
PC-10GE-SFP
PB-1CHOC3-SMIR-QPP
PE-4CHDS3-QPP
PB-1GE-SFP
FFANTRAY-M120-S
FFANTRAY-M120-S
RFANTRAY-M120-S
RFANTRAY-M120-S

(M160 Router)


Item
Version Part number
Chassis
Midplane
REV 02
710-001245
FPM CMB
REV 01
710-001642
FPM Display
REV 01
710-001647
CIP
REV 02
710-001593
PEM 0
Rev 01
740-001243
PEM 1
Rev 01
740-001243
PCG 0
REV 01
710-001568
PCG 1
REV 01
710-001568
Host 1
MCS 1
REV 03
710-001226
SFM 0 SPP
REV 04
710-001228
SFM 0 SPR
REV 02
710-001224
SFM 1 SPP
REV 04
710-001228
SFM 1 SPR
REV 01
710-001224
FPC 0
REV 03
710-001255
CPU
REV 02
710-001217
PIC 1
REV 05
750-000616
PIC 2
REV 05
750-000616
PIC 3
REV 01
750-000616
FPC 1
REV 02
710-001611
CPU
REV 02
710-001217
PIC 0
REV 03
750-001900
PIC 1
REV 01
710-002381
FPC 2
CPU
REV 03
710-001217
PIC 0
REV 01
Fan Tray 0
Fan Tray 1
Fan Tray 2
Fan Tray 3
Hardware inventory:
Item
Version Part number
Midplane
REV 03
710-009120
FPM Display
REV 02
710-009351
CIP
REV 03
710-005926
PEM 2
Rev X4
740-009148
PEM 3
Rev X4
740-009148
740-008883
740-008883
FPC 0
REV 02
710-010419
PIC 0
REV 01
750-001323
PIC 1
REV 02
750-002987
PIC 2
REV 04
750-001894
PIC 3
REV 04
750-001896
FPC 1
REV 02
710-010419
PIC 0
REV 04
750-001894
PIC 1
REV 04
750-001894
PIC 3
REV 03
750-001894
FPC 2
REV 02
710-010419
PIC 0
REV 10
750-005634
PIC 1
REV 10
750-005634
PIC 2
REV 07
750-005634
PIC 3
REV 07
750-005634
PIC 1
REV 10
750-005634
PIC 2
REV 07
750-005634
Serial number
101
S/N AB4107
S/N AA2911
S/N AA2999
S/N AA9563
S/N KJ35769
S/N KJ35765
S/N AA9794
S/N AA9804
da000004f8d57001
S/N AA9777
S/N AA2975
S/N AA9838
S/N AA2860
S/N AB0139
S/N AA9806
S/N AA9590
S/N AA1527
S/N AA1535
S/N AA1519
S/N AA9523
S/N AA9571
S/N AA9626
S/N AD3633
Description
M160
DC
DC
teknor
FPC Type 1
1x OC-12
1x OC-12
1x OC-12
FPC Type
ATM, MM
ATM, MM
ATM, MM
2
1x STM-16 SDH, SMIR

FPC Type OC192
S/N AB3329
1x OC-192 SM SR-2
Rear Bottom Blower
Rear Top Blower
Front Top Blower
Front Fan Tray
CLEI code
FRU model number

CHAS-BP-M320-S
CRAFT-M320-S
CIP-M320-S
PWR-M-DC-S
PWR-M-DC-S
RE-1600-2048-S
RE-1600-2048-S
M320-FPC1
P-TUNNEL
PE-1OC12-SON-SMIR
PB-1GE-SX
PB-1OC12-SON-SMIR
M320-FPC1
PB-1GE-SX
PB-1GE-SX
PB-1GE-SX
M320-FPC1
PB-1CHOC12SMIR-QPP
PB-1CHOC12SMIR-QPP
PB-1CHOC12SMIR-QPP
PB-1CHOC12SMIR-QPP
PB-1CHOC12SMIR-QPP
PB-1CHOC12SMIR-QPP
501
PIC 3
FPC 3
PIC 0
PIC 1
PIC 3
FPC 4
FPC 5
FPC 6
FPC 7
PIC 0
PIC 1
PIC 2
PIC 3
SIB 0
SIB 1
SIB 2
SIB 3
Fan Tray 0
Fan Tray 1
Fan Tray 2

detail (M160 Router)
502
REV 07
750-005634
PB-1CHOC12SMIR-QPP
REV
REV
REV
REV
REV
REV
03
04
04
02
02
02
750-001895
750-001894
750-003141
710-010419
710-010419
710-010419
PB-1OC12-SON-MM
PB-1GE-SX
PB-1GE-SX-B
M320-FPC1
M320-FPC1
M320-FPC1
REV
REV
REV
REV
REV
REV
REV
REV
15
06
07
05
03
03
03
03
750-001901
750-001900
750-001900
750-003737
710-009184
710-009184
710-009184
710-009184
PB-4OC12-SON-SMIR
PB-1OC48-SON-SMSR
PB-1OC48-SON-SMSR
PB-4GE-SX
SIB-M-S
SIB-M-S
SIB-M-S
SIB-M-S
FFANTRAY-M320-S
FFANTRAY-M320-S
RFANTRAY-M320-S

Hardware inventory:
Item
Version Part number
Chassis
Midplane
REV 02
710-001245
FPM CMB
REV 01
710-001642
FPM Display
REV 01
710-001647
CIP
REV 02
710-001593
PEM 0
Rev 01
740-001243
PEM 1
Rev 01
740-001243
PCG 0
REV 01
710-001568
PCG 1
REV 01
710-001568
Host 1
MCS 1
REV 03
710-001226
SFM 0 SPP
REV 04
710-001228
SFM 0 SPR
REV 02
710-001224
SSRAM bank 0
REV 01
710-000077
SSRAM bank 1
REV 01
710-000077
SSRAM bank 2
REV 01
710-000077
SSRAM bank 3
REV 01
710-000077
SFM 1 SPP
REV 04
710-001228
SFM 1 SPR
REV 01
710-001224
SSRAM bank 0
REV 01
710-000077
SSRAM bank 1
REV 01
710-000077
SSRAM bank 2
REV 01
710-000077
SSRAM bank 3
REV 01
710-000077
FPC 0
REV 03
710-001255
CPU
REV 02
710-001217
SSRAM
REV 01
710-000077
SDRAM 0
REV 01
710-001196
SDRAM 1
REV 01
710-001196
SSRAM
REV 01
710-000077
SDRAM 0
REV 01
710-001196
SDRAM 1
REV 01
710-001196
SSRAM
REV 01
710-000077
SDRAM 0
REV 01
710-001196
SDRAM 1
REV 01
710-001196
SSRAM
REV 01
710-000077
SDRAM 0
REV 01
710-001196
SDRAM 1
REV 01
710-001196
Serial number
101
S/N AB4107
S/N AA2911
S/N AA2999
S/N AA9563
S/N KJ35769
S/N KJ35765
S/N AA9794
S/N AA9804
da000004f8d57001
S/N AA9777
S/N AA2975
S/N AA9838
S/N 306456
S/N 306474
S/N 306388
S/N 306392
S/N AA2860
S/N AB0139
S/N 302917
S/N 302662
S/N 302593
S/N 100160
S/N AA9806
S/N AA9590
S/N 302836
S00141
S0010;
S/N 302633
S00143
S00115
S/N 302952
S00135
S001=3
S/N 302892
S000?6
S001=5
Description
M160
DC
DC
teknor
1 MB
1 MB
1 MB
1 MB
1 MB
1 MB
1 MB
1 MB
FPC Type 1
1 MB
32 MB
32 MB
1 MB
32 MB
32 MB
1 MB
32 MB
32 MB
1 MB
32 MB
32 MB
PIC 1
PIC 2
PIC 3
FPC 1
CPU
SSRAM
SDRAM 0
SDRAM 1
SSRAM
SDRAM 0
SDRAM 1
SSRAM
SDRAM 0
SDRAM 1
SSRAM
SDRAM 0
SDRAM 1
PIC 0
PIC 1
FPC 2
... SSRAM

(M320 Router)

REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
05
05
01
02
02
01
01
01
01
01
01
01
01
01
01
01
01
03
01
REV 01
750-000616
750-000616
750-000616
710-001611
710-001217
710-000077
710-001196
710-001196
710-000077
710-001196
710-001196
710-000077
710-001196
710-001196
710-000077
710-001196
710-001196
750-001900
710-002381
710-000077

Hardware inventory:
Item
Version Part number
Chassis
Midplane
REV 05
710-009120
FPM GBUS
REV 04
710-005928
FPM Display
REV 05
710-009351
CIP
REV 04
710-005926
PEM 0
Rev 05
740-009148
PEM 1
Rev 05
740-009148
PEM 2
Rev 05
740-009148
PEM 3
Rev 05
740-009148
740-008883
CB 0
REV 07
710-009115
FPC 0
REV 02
710-005017
CPU
REV 01
710-011659
PIC 0
REV 07
750-001900
PIC 1
REV 03
750-001850
PIC 2
REV 05
750-010618
PIC 3
REV 06
750-001900
FPC 2
REV 02
710-005017
CPU
REV 01
710-011659
PIC 0
REV 05
750-003034
FPC 5
REV 02
710-005017
CPU
FPC 7
REV 02
710-005017
CPU
SIB 0
REV 09
710-009184
SIB 1
REV 09
710-009184
SIB 2
REV 09
710-009184
SIB 3
REV 09
710-009184
Fan Tray 0
Fan Tray 1
Fan Tray 2

Hardware inventory:
Item
Version Part number
S/N AA1527
S/N AA1535
S/N AA1519
S/N AA9523
S/N AA9571
S/N 306340
S00012
S0001?
S/N 306454
S00028
S0002?
S/N 306492
S00015
S00031
S/N 306363
S00013
S00032
S/N AA9626
S/N AD3633
S/N 306466
1x OC-12
1x OC-12
1x OC-12
FPC Type
ATM, MM
ATM, MM
ATM, MM
2
1 MB
32 MB
32 MB
1 MB
32 MB
32 MB
1 MB
32 MB
32 MB
1 MB
32 MB
32 MB
1x STM-16 SDH, SMIR
FPC Type OC192
1 MB
Serial number
67245
RB1202
HZ5697
HR1464
HT8672
QK34208
QK34262
QF10449
QJ18257
P11123901185
JB2382
CD9926
CJ6940
AT1594
HS2746
JE7117
HE6083
CH0319
CJ6942
BD8705
CD9938
Description
M320
M320 Midplane
M320 Board
M320 FPM Display
M320 CIP
DC Power Entry Module
RE-4.0
M320 Control Board
M320 FPC Type 2
M320 PCA SCPU
1x Tunnel
M320 FPC Type 1
M320 PCA SCPU
4x OC-3 SONET, SMIR
M320 FPC Type 2
CD9934
M320 FPC Type 2
JA6540
HV9511
HW2057
JA6687
M320 SIB
M320 SIB
M320 SIB
M320 SIB
Front Top Fan Tray
Rear Fan Tray
CLEI code
FRU model number
503
Midplane
REV 03
FPM Display
REV 02
CIP
REV 03
PEM 2
Rev X4
PEM 3
Rev X4
FPC 0
REV 02
PIC 0
REV 01
PIC 1
REV 02
PIC 2
REV 04
PIC 3
REV 04
FPC 1
REV 02
PIC 0
REV 04
PIC 1
REV 04
PIC 3
REV 03
FPC 2
REV 02
PIC 0
REV 10
PIC 1
REV 10
PIC 2
REV 07
PIC 3
REV 07
PIC 1
REV 10
PIC 2
REV 07
PIC 3
REV 07
FPC 3
PIC 0
REV 03
PIC 1
REV 04
PIC 3
REV 04
FPC 4
REV 02
FPC 5
REV 02
FPC 6
REV 02
FPC 7
PIC 0
REV 15
PIC 1
REV 06
PIC 2
REV 07
PIC 3
REV 05
SIB 0
REV 03
SIB 1
REV 03
SIB 2
REV 03
SIB 3
REV 03
Fan Tray 0
Fan Tray 1
Fan Tray 2

(MX5 Router)
504
710-009120
710-009351
710-005926
740-009148
740-009148
740-008883
740-008883
710-010419
750-001323
750-002987
750-001894
750-001896
710-010419
750-001894
750-001894
750-001894
710-010419
750-005634
750-005634
750-005634
750-005634
750-005634
750-005634
750-005634
CHAS-BP-M320-S
CRAFT-M320-S
CIP-M320-S
PWR-M-DC-S
PWR-M-DC-S
RE-1600-2048-S
RE-1600-2048-S
M320-FPC1
P-TUNNEL
PE-1OC12-SON-SMIR
PB-1GE-SX
PB-1OC12-SON-SMIR
M320-FPC1
PB-1GE-SX
PB-1GE-SX
PB-1GE-SX
M320-FPC1
PB-1CHOC12SMIR-QPP
PB-1CHOC12SMIR-QPP
PB-1CHOC12SMIR-QPP
PB-1CHOC12SMIR-QPP
PB-1CHOC12SMIR-QPP
PB-1CHOC12SMIR-QPP
PB-1CHOC12SMIR-QPP
750-001895
750-001894
750-003141
710-010419
710-010419
710-010419
PB-1OC12-SON-MM
PB-1GE-SX
PB-1GE-SX-B
M320-FPC1
M320-FPC1
M320-FPC1
750-001901
750-001900
750-001900
750-003737
710-009184
710-009184
710-009184
710-009184
PB-4OC12-SON-SMIR
PB-1OC48-SON-SMSR
PB-1OC48-SON-SMSR
PB-4GE-SX
SIB-M-S
SIB-M-S
SIB-M-S
SIB-M-S
FFANTRAY-M320-S
FFANTRAY-M320-S
RFANTRAY-M320-S

Hardware inventory:
Item
Version Part number
Chassis
Midplane
REV 01
711-038215
PEM 0
Rev 04
740-028288
PEM 1
Rev 04
740-028288
Routing Engine
BUILTIN
TFEB 0
BUILTIN
Processor
QXM 0
REV 05
711-028408
FPC 0
BUILTIN
MIC 0
BUILTIN
PIC 0
BUILTIN
FPC 1
BUILTIN
MIC 0
REV 24
750-028392
PIC 0
BUILTIN
Serial number
E1368
YF5288
VA01215
VA01218
BUILTIN
BUILTIN
Description
MX5-T
MX5-T
Routing Engine
Forwarding Engine
ZA9136
BUILTIN
BUILTIN
BUILTIN
BUILTIN
YX9820
BUILTIN
MPC QXM
MPC BUILTIN
4x 10GE XFP
4x 10GE XFP
MPC BUILTIN
3D 20x 1GE(LAN) SFP
10x 1GE(LAN) SFP
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
MIC 1
PIC 2
PIC 3
Fan Tray

(MX10 Router)

(MX40 Router)
0
1
2
3
4
9
REV
REV
REV
REV
REV
REV
01
01
01
01
01
01
0
1
2
3
4
5
6
7
8
9
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
01
01
01
01
01
01
01
01
01
20
740-031851
740-031851
740-031851
740-031851
740-031851
740-011613
BUILTIN
740-031851
740-011613
740-011613
740-011613
740-011613
740-011782
740-011613
740-011613
740-011613
740-011782
750-028380
BUILTIN
BUILTIN

Hardware inventory:
Item
Version Part number
Chassis
Midplane
REV 01
711-038211
PEM 0
Rev 04
740-028288
Routing Engine
BUILTIN
TFEB 0
BUILTIN
Processor
QXM 0
REV 05
711-028408
FPC 0
BUILTIN
MIC 0
BUILTIN
PIC 0
BUILTIN
FPC 1
BUILTIN
MIC 0
REV 24
750-028392
PIC 0
BUILTIN
Xcvr 0
REV 01
740-031851
PIC 1
BUILTIN
Fan Tray

Hardware inventory:
Item
Version Part number
Chassis
Midplane
REV 01
711-038211
PEM 0
Rev 04
740-028288
PEM 1
Rev 04
740-028288
Routing Engine
BUILTIN
TFEB 0
BUILTIN
Processor
QXM 0
REV 05
711-028408
FPC 0
BUILTIN
MIC 0
BUILTIN
PIC 0
BUILTIN
Xcvr 0
REV 01
740-014279
Xcvr 1
NON-JNPR
FPC 1
BUILTIN
MIC 0
REV 24
750-028392
AM1045SUAQ3
AM1045SUAPA
AM1045SUAN7
AM1045SU91Q
AM1045SUDDR
AM0848SB6A1
BUILTIN
AM1045SUAN0
AS0812S0719
AM0821SA121
PF21K21
AM0848SB69Z
P9P0XV3
AM0812S8WJN
PAM3G9Q
AM0848SB4A6
P9M0U37
ZG2657
BUILTIN
BUILTIN
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
10x 1GE(LAN) SFP
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
3D 2x 10GE XFP
1x 10GE XFP
1x 10GE XFP
Fan Tray
Serial number
E1372
YF5285
VB01678
BUILTIN
BUILTIN
Description
MX10-T
MX10-T
Routing Engine
Forwarding Engine
ZA9053
BUILTIN
BUILTIN
BUILTIN
BUILTIN
YX9436
BUILTIN
AM1107SUFQW
BUILTIN
MPC QXM
MPC BUILTIN
4x 10GE XFP
4x 10GE XFP
MPC BUILTIN
3D 20x 1GE(LAN) SFP
10x 1GE(LAN) SFP
SFP-SX
10x 1GE(LAN) SFP
Fan Tray
Serial number
E1367
YF5284
VB01680
VB01700
BUILTIN
BUILTIN
Description
MX40-T
MX40-T
Routing Engine
Forwarding Engine
ZA9048
BUILTIN
BUILTIN
BUILTIN
M7067UPP
K9J02UN
BUILTIN
YX3504
MPC QXM
MPC BUILTIN
4x 10GE XFP
4x 10GE XFP
XFP-10G-LR
XFP-10G-LR
MPC BUILTIN
3D 20x 1GE(LAN) SFP
505
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
MIC 1
PIC 2
Xcvr
PIC 3
Xcvr
Fan Tray

(Fixed MX80 Router)

(Modular MX80
Router)
506
0
1
2
3
4
5
6
7
8
9
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
01
01
01
01
02
01
01
01
01
0
1
2
3
4
5
6
8
9
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
01
01
01
01
01
01
01
01
01
REV 01
BUILTIN
740-011613
740-011613
740-031851
740-011613
740-011613
740-011613
740-011782
740-011782
740-011613
740-031851
BUILTIN
740-011613
740-031851
740-031851
740-011613
740-031851
740-031851
740-031851
740-011613
740-011613
750-021130
BUILTIN
740-011571
BUILTIN
NON-JNPR

Hardware inventory:
Item
Version Part number
Chassis
Midplane
REV 01
711-031603
Routing Engine
BUILTIN
FEB 0
BUILTIN
FPC 0
BUILTIN
MIC 0
BUILTIN
PIC 0
BUILTIN
Xcvr 0
NON-JNPR
Xcvr 1
REV 01
740-014279
Xcvr 2
REV 01
740-014289
Xcvr 3
REV 01
740-014289
FPC 1
BUILTIN
MIC 0
REV 01
711-029399
PIC 0
BUILTIN
PIC 1
BUILTIN
MIC 1
REV 01
BUILTIN
PIC 2
BUILTIN
PIC 3
BUILTIN
Fan Tray
BUILTIN
AM0812S8WTE
PFA6KV2
AM1045SUDDM
PD63C7M
PD63DJY
AA0950STLL9
PAR1YHC
P9P0XXL
PD63D95
AM1045SU9B8
BUILTIN
PF21L3Z
AM1045SU7M9
AM1045SUAPT
PFF2BZH
AM1045SUDDN
AM1039S00ZR
AM1045SUD6Y
PFM1QBS
PFF2E25
KG4391
BUILTIN
C645XJ04G
BUILTIN
CA49BK0AE
10x 1GE(LAN) SFP

SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
10x 1GE(LAN) SFP
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
3D 2x 10GE XFP
1x 10GE XFP
XFP-10G-SR
1x 10GE XFP
XFP-10G-SR
Fan Tray
Serial number
Description
MX80-48T
MX80-48T
Routing Engine
MPC BUILTIN
4x 10GE XFP
4x 10GE XFP
XFP-10G-LR
XFP-10G-LR
XFP-10G-SR
XFP-10G-SR
MPC BUILTIN
12x 1GE(LAN) RJ45
12x 1GE(LAN) RJ45
12x 1GE(LAN) RJ45
12x 1GE(LAN) RJ45
12x 1GE(LAN) RJ45
12x 1GE(LAN) RJ45
Fan Tray
KF9250
BUILTIN
BUILTIN
BUILTIN
BUILTIN
BUILTIN
M6439D41
6XE931N00202
C715XU05F
C650XU0EP
BUILTIN
JR6981
BUILTIN
BUILTIN
BUILTIN
BUILTIN
BUILTIN

Hardware inventory:
Item
Version
Chassis
Midplane
REV 02
PEM 0
Rev 01
Routing Engine
FEB 0
Part number
Serial number
711-031594
740-028288
BUILTIN
BUILTIN
JR7084
000018
BUILTIN
BUILTIN
Description
MX80
MX80
Routing Engine
QXM 0
FPC 0
MIC 0
PIC 0
FPC 1
MIC 0
PIC 0
Xcvr
PIC 1
Xcvr
MIC 1
PIC 2
Xcvr
PIC 3
Xcvr
Fan Tray

(MX240 Router)
REV 05
REV 02
0
REV 01
REV 01
REV 02
REV 02
REV 02
711-028408
BUILTIN
BUILTIN
BUILTIN
BUILTIN
750-028380
BUILTIN
740-014289
BUILTIN
740-014289
750-028380
BUILTIN
740-014289
BUILTIN
740-014289

Hardware inventory:
Item
Version Part number
Chassis
Midplane
REV 01
710-021041
FPM Board
REV 01
710-017254
PEM 0
Rev 02
740-017330
AC in
PEM 1
Rev 02
740-017330
AC in
740-013063
740-015113
CB 0
REV 07
710-013385
CB 1
REV 05
710-013385
FPC 1
REV 01
750-021679
CPU
REV 06
710-013713
PIC 0
BUILTIN
Xcvr 0
REV 01
740-011613
PIC 1
BUILTIN
PIC 2
BUILTIN
PIC 3
BUILTIN
FPC 2
REV 04
710-016669
CPU
REV 06
710-013713
PIC 0
BUILTIN
Xcvr 0
REV 01
740-011613
Xcvr 1
REV 01
740-011613
Xcvr 2
REV 01
740-011613
Xcvr 3
REV 01
740-011613
Xcvr 4
REV 01
740-011613
PIC 1
BUILTIN
Xcvr 0
REV 01
740-011613
Xcvr 1
REV 01
740-011613
Xcvr 2
REV 01
740-011613
Xcvr 3
REV 01
740-011613
PIC 2
BUILTIN
Xcvr 0
REV 01
740-011613
Xcvr 1
REV 01
740-011613
Xcvr 2
REV 01
740-011613
Xcvr 3
REV 01
740-011613
PIC 3
BUILTIN
Xcvr 0
REV 01
740-011613
Xcvr 1
REV 01
740-011613
Xcvr 2
REV 01
740-011613
JR7041
BUILTIN
BUILTIN
BUILTIN
BUILTIN
JR6598
BUILTIN
T07M86365
BUILTIN
T07M71094
JG8548
BUILTIN
T08L86302
BUILTIN
C810XU0BA
MPC QXM
MPC BUILTIN
4x 10GE XFP
4x 10GE XFP
MPC BUILTIN
3D 2x 10GE XFP
1x 10GE XFP
XFP-10G-SR
1x 10GE XFP
XFP-10G-SR
3D 2x 10GE XFP
1x 10GE XFP
XFP-10G-SR
1x 10GE XFP
XFP-10G-SR
Fan Tray
Serial number
JN10C7F7EAFC
TR1502
KD4017
000332
Description
MX240
MX240 Backplane
Front Panel Display
PS 1.2-1.7kW; 100-240V
000226
PS 1.2-1.7kW; 100-240V
1000703522
1000687625
KC9057
JY4760
KC7340
KD4078
BUILTIN
P9F18ME
BUILTIN
BUILTIN
BUILTIN
JS4529
KB3969
BUILTIN
PBG3Y79
PBG3XU8
PBG3YG6
PBG3XUG
PBG3XTJ
BUILTIN
PBG3ZUM
PBG3Y5H
PBG3UZT
PBG3US1
BUILTIN
PBG3YG7
PBG3XZ9
PBG3XTY
PBG3UZG
BUILTIN
PBG3Y8W
PBG3YVX
PBG3YB3
RE-S-2000
RE-S-1300
MX SCB
MX SCB
DPCE 40x 1GE
DPC PMB
10x 1GE(LAN)
SFP-SX
10x 1GE(LAN)
10x 1GE(LAN)
10x 1GE(LAN)
DPCE 40x 1GE
DPC PMB
10x 1GE(LAN)
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
10x 1GE(LAN)
SFP-SX
SFP-SX
SFP-SX
SFP-SX
10x 1GE(LAN)
SFP-SX
SFP-SX
SFP-SX
SFP-SX
10x 1GE(LAN)
SFP-SX
SFP-SX
SFP-SX
R EQ
EQ
EQ
EQ
EQ
507
Xcvr 3
Fan Tray 0

detail (MX 240 Router
with Routing Engine
508
REV 01
REV 01
740-011613
710-021113
PBG43VQ
JS4642
SFP-SX
MX240 Fan Tray
Serial number
JN11279B4AFC
Description
MX240 Backplane

Item
Chassis
Version
Part number
Displaying DIMM
information)

(MX240 Router with
Enhanced MX SCB)
Midplane
FPM Board
PEM 0
Routing Engine 0
ad0
3764 MB
REV 07
REV 03
Rev 03
REV 01
STEC M2+
760-021404
TS2474
760-021392
XC2643
740-017343
QCS0908A068
740-031117
AARCHOO
CF 9.0.2
STIM2Q3209239145303
ad1
28626 MB
usb0 (addr 1)
usb0 (addr 2)
DIMM 0
DIMM 1
DIMM 2
DIMM 3
CB 0
Fan Tray 0
WDC SSD-F0030S-5000 C933Z036237215548S00 Compact Flash

EHCI root hub 0
Intel
uhub0
product 0x0020 32
vendor 0x8087
uhub1
VL31B5263E-F8S DIE REV-0 PCB REV-0
MFR ID-ce80
MFR ID-ce80
MFR ID-ce80
SL31B5263E-F8S DIE REV-0 PCB REV-0
MFR ID-ce80
REV 03
710-021523
XD7225
MX SCB
REV 01
710-021113
WZ4986
MX240 Fan Tray

Hardware inventory:
Item
Version Part number
Chassis
Midplane
REV 01
710-021041
FPM Board
REV 01
710-017254
PEM 0
Rev 02
740-017330
AC in
PEM 1
Rev 02
740-017330
AC in
740-013063
740-015113
CB 0
REV 02
710-031391
CB 1
REV 05
710-031391
FPC 1
REV 01
750-021679
CPU
REV 06
710-013713
PIC 0
BUILTIN
Xcvr 0
REV 01
740-011613
PIC 1
BUILTIN
PIC 2
BUILTIN
PIC 3
BUILTIN
FPC 2
REV 04
710-016669
CPU
REV 06
710-013713
PIC 0
BUILTIN
Xcvr 0
REV 01
740-011613
Xcvr 1
REV 01
740-011613
Xcvr 2
REV 01
740-011613
Xcvr 3
REV 01
740-011613
Xcvr 4
REV 01
740-011613
PIC 1
BUILTIN
Xcvr 0
REV 01
740-011613
Xcvr 1
REV 01
740-011613
Xcvr 2
REV 01
740-011613
Xcvr 3
REV 01
740-011613
PIC 2
BUILTIN
Xcvr 0
REV 01
740-011613
Xcvr 1
REV 01
740-011613
Xcvr 2
REV 01
740-011613
Xcvr 3
REV 01
740-011613
PIC 3
BUILTIN
Xcvr 0
REV 01
740-011613
Xcvr 1
REV 01
740-011613
Xcvr 2
REV 01
740-011613
Xcvr 3
REV 01
740-011613
Fan Tray 0
REV 01
710-021113
MX240 Backplane
Front Panel Display
RE-S-1800x4
Removable Compact Flash
Serial number
JN10C7F7EAFC
TR1502
KD4017
000332
Description
MX240
MX240 Backplane
Front Panel Display
PS 1.2-1.7kW; 100-240V
000226
PS 1.2-1.7kW; 100-240V
1000703522
1000687625
YE8494
YOP5764
KC7340
KD4078
BUILTIN
P9F18ME
BUILTIN
BUILTIN
BUILTIN
JS4529
KB3969
BUILTIN
PBG3Y79
PBG3XU8
PBG3YG6
PBG3XUG
PBG3XTJ
BUILTIN
PBG3ZUM
PBG3Y5H
PBG3UZT
PBG3US1
BUILTIN
PBG3YG7
PBG3XZ9
PBG3XTY
PBG3UZG
BUILTIN
PBG3Y8W
PBG3YVX
PBG3YB3
PBG43VQ
JS4642
RE-S-2000
RE-S-1300
Enhanced MX SCB
Enhanced MX SCB
DPCE 40x 1GE R
DPC PMB
10x 1GE(LAN)
SFP-SX
10x 1GE(LAN)
10x 1GE(LAN)
10x 1GE(LAN)
DPCE 40x 1GE R EQ
DPC PMB
10x 1GE(LAN) EQ
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
10x 1GE(LAN) EQ
SFP-SX
SFP-SX
SFP-SX
SFP-SX
10x 1GE(LAN) EQ
SFP-SX
SFP-SX
SFP-SX
SFP-SX
10x 1GE(LAN) EQ
SFP-SX
SFP-SX
SFP-SX
SFP-SX
MX240 Fan Tray
509

(MX480 Router)

(MX480 Router with
Enhanced MX SCB)

(MX960 Router)
510

Hardware inventory:
Item
Version Part number
Chassis
Midplane
REV 04
710-017414
FPM Board
REV 02
710-017254
PEM 0
Rev 02
740-017330
AC in
PEM 1
Rev 02
740-017330
AC in
PEM 2
Rev 02
740-017330
AC in
740-013063
740-013063
CB 0
REV 07
710-013385
CB 1
REV 07
710-013385
FPC 0
REV 09
750-020452
CPU
REV 06
710-013713
PIC 0
BUILTIN
PIC 1
BUILTIN
PIC 2
BUILTIN
PIC 3
BUILTIN
Fan Tray

Hardware inventory:
Item
Version Part number
Chassis
Midplane
REV 04
710-017414
FPM Board
REV 02
710-017254
PEM 0
Rev 02
740-017330
AC in
PEM 1
Rev 02
740-017330
AC in
PEM 2
Rev 02
740-017330
AC in
740-013063
740-013063
CB 0
REV 07
710-013385
CB 1
REV 07
710-013385
FPC 0
REV 09
750-020452
CPU
REV 06
710-013713
PIC 0
BUILTIN
PIC 1
BUILTIN
PIC 2
BUILTIN
PIC 3
BUILTIN
Fan Tray

Hardware inventory:
Item
Version Part number
Chassis
Midplane
REV 01
710-013698
PIM
Rev 01
740-013110
PEM 2
PEM 3
Rev 01
740-013682
740-015113
CB 0
REV 05
710-013725
Serial number
JN10C7F7FAFB
TR2071
KB8459
QCS07519029
Description
MX480
MX480 Midplane
Front Panel Display
PS 1.2-1.7kW; 100-240V
QCS07519041
PS 1.2-1.7kW; 100-240V
QCS07519097
PS 1.2-1.7kW; 100-240V
1000733381
1000733540
KA8022
KA8303
KA8660
KA8185
BUILTIN
BUILTIN
BUILTIN
BUILTIN
RE-S-2000
RE-S-2000
MX SCB
MX SCB
DPCE 40x 1GE X EQ
DPC PMB
10x 1GE(LAN) EQ
10x 1GE(LAN) EQ
10x 1GE(LAN) EQ
10x 1GE(LAN) EQ
Left Fan Tray
Serial number
JN10C7F7FAFB
TR2071
KB8459
QCS07519029
Description
MX480
MX480 Midplane
Front Panel Display
PS 1.2-1.7kW; 100-240V
QCS07519041
PS 1.2-1.7kW; 100-240V
QCS07519097
PS 1.2-1.7kW; 100-240V
1000733381
1000733540
KA8022
KA8303
KA8660
KA8185
BUILTIN
BUILTIN
BUILTIN
BUILTIN
RE-S-2000
RE-S-2000
Enhanced MX SCB
Enhanced MX SCB
DPCE 40x 1GE X EQ
DPC PMB
10x 1GE(LAN) EQ
10x 1GE(LAN) EQ
10x 1GE(LAN) EQ
10x 1GE(LAN) EQ
Left Fan Tray
Serial number
AA6082
000008
Description
MX960
MX960 Midplane
Power Inlet Module
000038
1000617944
JK6947
PS 1.7kW; 200-240VAC in
RE-S-1300
MX960 Test SCB
FPC 4
CPU
PIC 0
PIC 1
FPC 7
CPU
PIC 0
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
Fan Tray
Fan Tray

(MX960 Router with
Bidirectional Optics)
REV 01
710-013305
JM7617
MX960 Test DPC
REV 01
BUILTIN
BUILTIN
710-013305
BUILTIN
BUILTIN
JL9634
1x 10GE(LAN/WAN)
10x 1GE
MX960 Test DPC
REV
REV
REV
REV
BUILTIN
NON-JNPR
BUILTIN
740-011782
740-011782
740-011782
740-011782
BUILTIN
MYBG65I82C
BUILTIN
P7N0368
P8J1W27
P8J1VSD
P8J1W25
1x 10GE(LAN/WAN)
XFP-10G-SR
10x 1GE
SFP-SX
SFP-SX
SFP-SX
SFP-SX
0
1
4
6
9
0
1
01
01
01
01

Hardware inventory:
Item
Chassis
JN10BA5B9AFA
Midplane
REV 03
710-013698
TR0234
FPM Board
REV 03
710-014974
JA0878
PDM
Rev 03
740-013110
QCS11135028
PEM 0
Rev 03
740-013682
QCS11154036
PEM 1
Rev 03
740-013682
QCS11154010
PEM 2
Rev 03
740-013682
QCS11154022
740-013063
1000691458
CB 0
REV 07
710-013385
KA2190
CB 1
REV 07
710-013385
KA0837
FPC 3
REV 02
750-018122
KB3890
CPU
FPC 4
REV 01
750-018122
KB3889
CPU
REV 06
710-013713
KB3976
PIC 0
BUILTIN
BUILTIN
Xcvr 1
REV 01
740-020426
4910549
Xcvr 2
REV 01
740-020426
4910551
Xcvr 5
REV 01
740-021340
77E245N00006
Xcvr 6
REV 01
740-020425
4882821
Xcvr 8
REV 01
740-020425
4882820
PIC 1
BUILTIN
BUILTIN
Xcvr 0
REV 01
740-020465
77E555N00894
Xcvr 1
REV 01
740-020465
75E467X00818
Xcvr 2
REV 01
740-020465
75E467X00573
Xcvr 3
REV 01
740-020465
4888227
Xcvr 4
REV 01
740-020465
4888241
Xcvr 5
REV 01
740-021340
77E245N00005
Xcvr 6
REV 01
740-021340
76E245X00487
Xcvr 7
REV 01
740-021341
5255889
Xcvr 8
REV 01
740-021341
5255887
Xcvr 9
REV 01
740-021340
77E245N00004
PIC 2
BUILTIN
BUILTIN
Xcvr 0
REV 01
740-020424
5007582
Xcvr 1
REV 01
740-020424
4888187
Xcvr 2
REV 01
740-020424
4656500
Xcvr 5
REV 01
740-021341
5255886
Xcvr 7
REV 01
740-021340
77E245N00003
Xcvr 8
REV 01
740-021341
5255888
PIC 3
BUILTIN
BUILTIN
Xcvr 0
REV 01
740-017726
74S184H30341
Xcvr 1
REV 01
740-017726
4814061
Xcvr 5
REV 01
740-017726
6ZS184H31108
Description
MX960
MX960 Backplane
Front Panel Display
Power Distribution Module
PS 1.7kW; 200-240VAC in
PS 1.7kW; 200-240VAC in
PS 1.7kW; 200-240VAC in
RE-S-2000
MX SCB
MX SCB
DPCE 40x 1GE R
DPCE 40x 1GE R
DPC PMB
10x 1GE(LAN)
SFP-1000BASE-BX40-D
SFP-1000BASE-BX40-D
SFP-1000BASE-BX10-U
SFP-1000BASE-BX40-U
SFP-1000BASE-BX40-U
10x 1GE(LAN)
SFP-1000BASE-BX10-D
SFP-1000BASE-BX10-D
SFP-1000BASE-BX10-D
SFP-1000BASE-BX10-D
SFP-1000BASE-BX10-D
SFP-1000BASE-BX10-U
SFP-1000BASE-BX10-U
SFP-1000BASE-BX10-U
SFP-1000BASE-BX10-U
SFP-1000BASE-BX10-U
10x 1GE(LAN)
SFP-1000BASE-BX10-D
SFP-1000BASE-BX10-D
SFP-1000BASE-BX10-D
SFP-1000BASE-BX10-U
SFP-1000BASE-BX10-U
SFP-1000BASE-BX10-U
10x 1GE(LAN)
SFP-EX
SFP-EX
SFP-EX
511
Xcvr 9
Fan Tray 0
Fan Tray 1

(MX960 Router with
Enhanced MX SCB)
512
REV 01
740-021340
76E245X00486
SFP-1000BASE-BX10-U
REV 03
740-014971
TP0850
Fan Tray

Hardware inventory:
Item
Description
Chassis
JN1096805AFA
MX960
Midplane
REV 03
710-013698
TR0183
MX960 Backplane
Fan Extender
REV 02
710-018051
JY5227
Extended Cable Manager
FPM Board
REV 03
710-014974
JZ6876
Front Panel Display
PDM
Rev 03
740-013110
QCS11035023
PEM 1
Rev 03
740-013682
QCS1109400L
PS 1.7kW; 200-240VAC in
PEM 2
Rev 03
740-013682
QCS11094015
PS 1.7kW; 200-240VAC in
PEM 3
Rev 03
740-013682
QCS11094012
PS 1.7kW; 200-240VAC in
740-013063
1000687969
RE-S-2000
740-013063
1000687955
RE-S-2000
CB 0
REV 11
750-031391
YZ6072
Enhanced MX SCB
CB 1
REV 11
750-031391
YZ6068
Enhanced MX SCB
CB 2
REV 11
750-031391
YZ6081
Enhanced MX SCB
FPC 0
REV 01
750-018122
KA5576
DPCE 40x 1GE R
CPU
REV 06
710-013713
KB3961
DPC PMB
PIC 0
BUILTIN
BUILTIN
10x 1GE(LAN)
Xcvr 0
REV 01
740-011613
P9F18GF
SFP-SX
Xcvr 2
REV 01
740-011782
P9M0TL9
SFP-SX
Xcvr 7
REV 01
740-011782
P9P0XXH
SFP-SX
Xcvr 9
REV 01
740-011782
P9M0TN1
SFP-SX
PIC 1
BUILTIN
BUILTIN
10x 1GE(LAN)
Xcvr 0
REV 01
740-011613
PAJ4UHC
SFP-SX
PIC 2
BUILTIN
BUILTIN
10x 1GE(LAN)
Xcvr 0
REV 01
740-011613
PFF2CD0
SFP-SX
Xcvr 1
REV 01
740-011613
PBG3ZUT
SFP-SX
Xcvr 2
REV 01
740-011613
PFF2DDV
SFP-SX
Xcvr 5
REV 01
740-011613
P8E2SST
SFP-SX
Xcvr 9
REV 01
740-011782
PB8329N
SFP-SX
PIC 3
BUILTIN
BUILTIN
10x 1GE(LAN)
Xcvr 0
REV 01
740-026192
1U0201084503342
SFP-100BASE-BX10-U
Xcvr 1
REV 01
740-026193
1U1201084503313
SFP-100BASE-BX10-D
Xcvr 2
REV 01
740-011613
PAJ4Y5B
SFP-SX
Xcvr 6
REV 01
740-011782
P9M0U3M
SFP-SX
Xcvr 7
REV 01
740-011782
P9M0TLA
SFP-SX
FPC 1
REV 16
750-031089
YL0719
MPC Type 2 3D
CPU
REV 06
711-030884
YL1463
MPC PMB 2G
MIC 0
REV 07
750-028387
JR6500
3D 4x 10GE XFP
PIC 0
BUILTIN
BUILTIN
2x 10GE XFP
Xcvr 0
REV 01
740-014279
733019A00154
XFP-10G-LR
Xcvr 1
REV 02
740-014289
T09F55034
XFP-10G-SR
PIC 1
BUILTIN
BUILTIN
2x 10GE XFP
Xcvr 0
REV 01
740-014279
913019B00791
XFP-10G-LR
Xcvr 1
REV 01
740-014289
98S803A90384
XFP-10G-SR
MIC 1
REV 24
750-028387
YJ3950
3D 4x 10GE XFP
PIC 2
BUILTIN
BUILTIN
2x 10GE XFP
Xcvr 0
REV 02
740-014279
T10B36134
XFP-10G-LR
Xcvr 1
REV 01
740-014289
T07M86354
XFP-10G-SR
PIC 3
BUILTIN
BUILTIN
2x 10GE XFP
FPC 2
REV 08
710-014219
JY9654
DPCE 4x 10GE R
CPU
REV 06
710-013713
JZ6549
DPC PMB
PIC 0
BUILTIN
BUILTIN
1x 10GE(LAN/WAN)
PIC 1
BUILTIN
BUILTIN
1x 10GE(LAN/WAN)
PIC 2
BUILTIN
BUILTIN
1x 10GE(LAN/WAN)
Xcvr 0
REV 03
740-011571
C931BK028
XFP-10G-SR
PIC 3
FPC 3
CPU
PIC 0
Xcvr 1
Xcvr 3
PIC 1
FPC 5
CPU
PIC 0
Xcvr 1
PIC 1
PIC 2
PIC 3
FPC 7
CPU
MIC 0
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
QXM 0
FPC 8
CPU
PIC 0
Xcvr 0
Xcvr 1
Xcvr 2
PIC 1
Xcvr 0
Xcvr 3
FPC 10
CPU
PIC 0
Xcvr 5
Xcvr 6
PIC 1
PIC 2
Xcvr 0
Xcvr 5
Xcvr 6
Xcvr 8
PIC 3
Fan Tray 0
Fan Tray 1

models (MX960
REV
REV
REV
REV
REV
REV
REV
REV
10
03
17
01
01
32
25
10
REV 01
REV 02
REV 01
REV 08
0
2
4
7
8
REV 01
0
1
9
REV
REV
REV
REV
REV
REV
REV
REV
01
01
01
04
05
03
08
01
REV
REV
REV
REV
REV
REV
01
08
01
01
04
05
REV 01
REV 01
REV 01
REV 01
REV 01
REV
REV
REV
REV
01
01
01
01
REV 03
REV 03
BUILTIN
750-024199
710-022351
750-009553
740-011785
740-011785
750-003700
750-028467
711-029089
BUILTIN
740-031980
BUILTIN
BUILTIN
BUILTIN
750-031092
711-030884
750-028392
BUILTIN
740-011782
NON-JNPR
740-011613
740-011613
740-011613
BUILTIN
740-011782
740-011613
740-011613
711-028408
750-024387
710-022351
750-014730
740-016065
NON-JNPR
740-011618
750-014637
740-011785
740-011785
710-013699
710-013713
BUILTIN
740-011782
740-011782
BUILTIN
BUILTIN
740-011782
740-011782
740-011782
740-011782
BUILTIN
740-014971
740-014971

Hardware inventory:
Item
Version Part number
BUILTIN
XJ6692
XF5182
RJ2945
PCP3YLL
PDS0MRY
DP2113
YM8256
YL3029
BUILTIN
AHN0X1Z
BUILTIN
BUILTIN
BUILTIN
JR6658
JZ9038
JZ8737
BUILTIN
PBE2C6Y
U8105N8
PFM18EF
PFF2AM8
PFF2CT6
BUILTIN
PB82VHH
PFF2CSW
PFF2BY0
JR6372
JW9754
KF1651
DM3664
81S290N00077
2191844
PD81EE5
DM3671
PCK3UNK
PDS0MPZ
JY4654
JS9717
BUILTIN
PAR1L72
P8N1YQ4
BUILTIN
BUILTIN
P8Q2AVL
PAR1L7B
PAR1L2J
P8N1YMY
BUILTIN
TP0567
TP0702
1x 10GE(LAN/WAN)
MX FPC Type 3
DPC PMB
4x OC-48 SONET
SFP-SR
SFP-SR
1x OC-192 12xMM VSR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
4x 10GE(LAN) SFP+
4x 10GE(LAN) SFP+
4x 10GE(LAN) SFP+
MPC Type 1 3D Q
MPC PMB 2G
3D 20x 1GE(LAN) SFP
10x 1GE(LAN) SFP
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
10x 1GE(LAN) SFP
SFP-SX
SFP-SX
SFP-SX
MPC QXM
MX FPC Type 2
DPC PMB
4x OC-3 1x OC-12 SFP
SFP-SR
SFP-SR
SFP-IR
4x OC-12-3 SFP
SFP-SR
SFP-SR
DPCE 40x 1GE R
DPC PMB
10x 1GE(LAN)
SFP-SX
SFP-SX
10x 1GE(LAN)
10x 1GE(LAN)
SFP-SX
SFP-SX
SFP-SX
SFP-SX
10x 1GE(LAN)
Fan Tray
Fan Tray
Serial number
FRU model number
513

MX SCB)
Midplane
REV 03
Fan Extender
REV 02
FPM Board
REV 03
CB 0
REV 11
CB 1
REV 11
CB 2
REV 11
FPC 0
REV 01
FPC 1
REV 16
MIC 0
REV 07
MIC 1
REV 24
FPC 2
REV 08
FPC 3
REV 10
PIC 0
REV 17
PIC 1
REV 32
FPC 5
REV 25
FPC 7
REV 02
MIC 0
REV 08
FPC 8
REV 05
PIC 0
REV 08
PIC 1
REV 08
FPC 10
REV 04
Fan Tray 0
REV 03
Fan Tray 1
REV 03

detail (MX960 Router)

Hardware inventory:
Item
Version Part number
Chassis
Midplane
REV 01
710-013698
PIM
Rev 01
740-013110
PEM 2
PEM 3
Rev 01
740-013682
740-015113
ad0
245 MB SanDisk SDCFB-256
ad2
38154 MB FUJITSU MHT2040BH
CB 0
REV 05
710-013725
FPC 4
REV 01
710-013305
CPU
PIC 0
BUILTIN
PIC 1
BUILTIN
FPC 7
REV 01
710-013305
CPU
PIC 0
BUILTIN
Xcvr 0
NON-JNPR
PIC 1
BUILTIN
Xcvr 1
REV 01
740-011782
Xcvr 4
REV 01
740-011782
Xcvr 6
REV 01
740-011782
Xcvr 9
REV 01
740-011782
Fan Tray 0
Fan Tray 1

(MX2010 Router)
514
710-013698
710-018051
710-014974
740-013063
740-013063
750-031391
750-031391
750-031391
750-018122
750-031089
750-028387
750-028387
710-014219
750-024199
750-009553
750-003700
750-028467
750-031092
750-028392
750-024387
750-014730
750-014637
710-013699
740-014971
740-014971
user@host > show chassis hardware

Hardware inventory:
Item
Version Part number
Chassis
Midplane
REV 01
750-044636
Midplane 1
REV 01
711-044557
TR0183
JY5227
JZ6876
1000687969
1000687955
YZ6072
YZ6068
YZ6081
KA5576
YL0719
JR6500
YJ3950
JY9654
XJ6692
RJ2945
DP2113
YM8256
JR6658
JZ8737
JW9754
DM3664
DM3671
JY4654
TP0567
TP0702
CHAS-BP-MX960-S
ECM-MX960
CRAFT-MX960-S
RE-S-2000-4096-S
RE-S-2000-4096-S
SCBE-MX-S
SCBE-MX-S
SCBE-MX-S
DPCE-R-40GE-SFP
MX-MPC2-3D
MIC-3D-4XGE-XFP
MIC-3D-4XGE-XFP
DPC-R-4XGE-XFP
MX-FPC3
PC-4OC48-SON-SFP
PC-1OC192-SON-VSR
MPC-3D-16XGE-SFPP
MX-MPC1-3D-Q
MIC-3D-20GE-SFP
MX-FPC2
PB-4OC3-1OC12-SON2-SFP
PB-4OC3-4OC12-SON-SFP
DPC-R-40GE-SFP
FFANTRAY-MX960-S
FFANTRAY-MX960-S
Serial number
AA6082
000008
Description
MX960
MX960 Midplane
Power Inlet Module
000038
1000617944
111419E1805T1141
NR0WT5925N77
JK6947
JM7617
PS 1.7kW; 200-240VAC in
RE-S-1300
Compact Flash
Hard Disk
MX960 Test SCB
MX960 Test DPC
BUILTIN
BUILTIN
JL9634
1x 10GE(LAN/WAN)
10x 1GE
MX960 Test DPC
BUILTIN
MYBG65I82C
BUILTIN
P7N0368
P8J1W27
P8J1VSD
P8J1W25
1x 10GE(LAN/WAN)
XFP-10G-SR
10x 1GE
SFP-SX
SFP-SX
SFP-SX
SFP-SX
Serial number
JN11E3217AFK
ABAB8506
ZY8296
Description
MX2010
Lower Backplane
Upper Backplane
PMP
REV 03
FPM Board
REV 06
PSM 4
REV 0C
Module
PSM 5
REV 0B
Module
PSM 6
REV 0B
Module
PSM 7
REV 0C
Module
PSM 8
REV 0C
Module
PDM 0
REV 0B
PDM 1
REV 0B
CB 0
REV 08
CB 1
REV 08
SPMB 0
REV 02
SPMB 1
REV 02
SFB 0
REV 06
SFB 1
REV 07
SFB 2
REV 07
SFB 3
REV 07
SFB 4
REV 07
SFB 5
REV 07
SFB 6
REV 07
SFB 7
REV 07
FPC 0
REV 33
CPU
REV 11
PIC 0
Xcvr 0
REV 01
Xcvr 1
REV 01
Xcvr 2
REV 01
Xcvr 3
REV 01
PIC 1
Xcvr 0
REV 01
Xcvr 1
REV 01
Xcvr 2
REV 01
Xcvr 3
REV 01
PIC 2
Xcvr 0
REV 01
Xcvr 1
REV 01
Xcvr 2
REV 01
Xcvr 3
REV 01
PIC 3
Xcvr 0
REV 01
Xcvr 1
REV 01
Xcvr 2
REV 01
Xcvr 3
REV 01
FPC 1
REV 21
CPU
REV 04
MIC 0
REV 03
PIC 0
Xcvr 0
REV 01
Xcvr 1
REV 01
Xcvr 2
REV 01
Xcvr 3
REV 01
Xcvr 4
REV 01
Xcvr 5
REV 01
Xcvr 6
REV 01
711-032426
711-032349
740-033727
ACAJ1388
ZX8744
VK00254
Power Midplane
Front Panel Display
DC 52V Power Supply
740-033727
VG00015
DC 52V Power Supply
740-033727
VH00097
DC 52V Power Supply
740-033727
VJ00151
DC 52V Power Supply
740-033727
VJ00149
DC 52V Power Supply
740-038109
740-038109
740-041821
740-041821
750-040257
750-040257
711-041855
711-041855
711-032385
711-032385
711-032385
711-032385
711-032385
711-032385
711-032385
711-032385
750-028467
711-029089
BUILTIN
740-021308
740-021308
740-021308
740-021308
BUILTIN
740-021308
740-021308
740-021308
740-021308
BUILTIN
740-021308
740-021308
740-021308
740-021308
BUILTIN
740-021308
740-021308
740-021308
740-021308
750-033205
711-035209
750-033307
BUILTIN
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
WA00008
WA00014
9009094134
9009094141
CAAB3491
CAAB3489
CAAA6135
CAAA6137
ZV1828
ZZ2568
ZZ2563
ZZ2564
ZZ2580
ZZ2579
CAAB4882
CAAB4898
CAAB1919
CAAB7174
BUILTIN
AMH02RE
AMH038C
AMH0390
AMG0SUA
BUILTIN
AMH0579
AMG0SGP
AMH04SV
AMH04X3
BUILTIN
AMH0135
AMH02NC
AMH02XB
AMH02PN
BUILTIN
AMH057Y
AMG0JHE
AMH02HT
AMH04V4
ZG5027
YT4780
ZV6299
BUILTIN
083363A00410
083363A00334
113363A00125
083363A00953
AHR013D
AJ40JUR
AJ40JKL
DC Power Dist Module

RE-S-1800x4
RE-S-1800x4
Control Board
Control Board
PMB Board
PMB Board
Switch Fabric Board
Switch Fabric Board
Switch Fabric Board
Switch Fabric Board
Switch Fabric Board
Switch Fabric Board
Switch Fabric Board
Switch Fabric Board
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPCE Type 3D
HMPC PMB 2G
10X10GE SFPP
10X10GE SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
515
Xcvr
Xcvr
Xcvr
MIC 1
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
FPC 8
CPU
MIC 0
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
MIC 1
PIC 2
Xcvr
Xcvr
PIC 3
FPC 9
CPU
PIC 0
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
PIC 1
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
PIC 2
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
PIC 3
Xcvr 0
Xcvr 1
516
7
8
9
REV
REV
REV
REV
01
01
01
03
0
1
2
3
4
5
6
7
8
9
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
01
01
01
01
01
01
01
01
01
22
06
26
0
1
2
3
4
5
6
7
8
9
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
01
02
02
02
02
01
01
01
01
0
1
2
3
4
5
REV
REV
REV
REV
REV
REV
REV
01
01
01
01
01
01
26
0
1
REV 11
REV 10
REV
REV
REV
REV
01
01
01
01
REV
REV
REV
REV
01
01
01
01
REV
REV
REV
REV
01
01
01
01
REV 01
REV 01
740-031980
740-021308
740-021308
750-033307
BUILTIN
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-021308
740-021308
750-031089
711-030884
750-028392
BUILTIN
740-031851
740-031851
740-011613
740-011613
740-011613
740-011613
740-031851
740-031851
740-031851
740-031851
BUILTIN
740-031851
740-031851
740-031851
740-031851
740-031851
740-031851
750-028387
BUILTIN
NON-JNPR
NON-JNPR
BUILTIN
750-036284
711-029089
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
AJ30ECK
19T511100864
19T511100868
ZV6268
BUILTIN
AJC0JML
AJ403PC
AJ10N25
AJ40JF4
AJ40JSJ
AJ403V7
AJ40JN3
AJ40JSU
19T511100468
19T511101363
ZT9746
ZS1271
ABBS1150
BUILTIN
PLG023C
PLG09C6
AM0950SF9L7
AM1001SFN1H
AM1001SFM9D
AM1001SFLTJ
AC1108S03L9
AC1102S00NC
AC1102S00MX
AC1102S0085
BUILTIN
AC1102S00KU
AC1102S00NG
AC1102S00K3
AC1102S008R
AM1107SUFVJ
AC1108S03LG
ABBR9582
BUILTIN
T10A91703
T09L42604
BUILTIN
ZL3591
ZL0513
BUILTIN
1YT517101825
1YT517101821
1YT517101682
ALQ13R6
BUILTIN
1YT517101828
1YT517101716
1YT517101732
ALP0TR1
BUILTIN
1YT517101741
1YT517101829
1YT517101669
ALQ14E3
BUILTIN
1YT517101826
1YT517101817
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
10X10GE SFPP
10X10GE SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC Type 2 3D
MPC PMB 2G
3D 20x 1GE(LAN) SFP
10x 1GE(LAN) SFP
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
10x 1GE(LAN) SFP
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
3D 4x 10GE XFP
2x 10GE XFP
XFP-10G-SR
XFP-10G-SR
2x 10GE XFP
MPC 3D 16x 10GE EM
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
ADC
ADC
ADC
ADC
Fan
Fan
Fan
Fan

detail (MX2010
Router)
Xcvr
Xcvr
0
1
8
9
Tray
Tray
Tray
Tray
2
3
0
1
2
3
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
01
05
01
01
02
2A
2A
2A
2A
740-031980
740-031980
750-043596
750-043596
750-043596
750-043596
760-046960
760-046960
760-046960
760-046960
1YT517101735
ALQ159A
CAAC2073
ZV4117
ZV4107
ZW1555
ACAY0015
ACAY0019
ACAY0020
ACAY0021
SFP+-10G-SR
SFP+-10G-SR
Adapter Card
Adapter Card
Adapter Card
Adapter Card
172mm FanTray
172mm FanTray
172mm FanTray
172mm FanTray
6
6
6
6
Fans
Fans
Fans
Fans
user@host > show chassis hardware detail

Hardware inventory:
Item
Description
Chassis
JN11E233DAFK
MX2010
Midplane
REV 26
750-044636
ABAB9357
Lower Backplane
Midplane 1
REV 01
711-044557
ABAB8643
Upper Backplane
PMP
REV 04
711-032426
ACAJ1677
Power Midplane
FPM Board
REV 08
760-044634
ABBV9726
Front Panel Display
PSM 0
REV 01
740-045050
1E02224000P
DC 52V Power Supply
Module
PSM 1
REV 01
740-045050
1E02224000M
DC 52V Power Supply
Module
PSM 2
REV 01
740-045050
1E022240010
DC 52V Power Supply
Module
PSM 3
REV 01
740-045050
1E02224000G
DC 52V Power Supply
Module
PSM 4
REV 01
740-045050
1E022240013
DC 52V Power Supply
Module
PSM 5
REV 01
740-045050
1E022240007
DC 52V Power Supply
Module
PSM 6
REV 01
740-045050
1E02224001C
DC 52V Power Supply
Module
PSM 7
REV 01
740-045050
1E02224001D
DC 52V Power Supply
Module
PSM 8
REV 01
740-045050
1E02224001B
DC 52V Power Supply
Module
PDM 0
REV 01
740-045234
1E262250067
740-041821
9009099704
RE-S-1800x4
ad0
3831 MB UGB30SFA4000T1
SFA4000T1 00000651 Compact Flash
ad1
30533 MB UGB94BPH32H0S1-KCI
11000019592
Disk 1
usb0 (addr 1) EHCI root hub 0
Intel
uhub0
usb0 (addr 2) product 0x0020 32
vendor 0x8087
uhub1
DIMM 0
SGU04G72H1BD2SA-BB DIE REV-52 PCB REV-54 MFR ID-ce80
DIMM 1
DIMM 2
DIMM 3
740-041821
9009099706
RE-S-1800x4
ad0
3998 MB Virtium - TuffDrive VCF P1T0200262860208 114 Compact Flash
ad1
30533 MB UGB94ARF32H0S3-KC
UNIGEN-499551-000404 Disk 1
CB 0
REV 13
750-040257
CAAF8436
Control Board
CB 1
REV 13
750-040257
CAAF8434
Control Board
SPMB 0
REV 02
711-041855
ABBV3825
PMB Board
SPMB 1
REV 02
711-041855
ABBV3833
PMB Board
SFB 0
REV 05
711-044466
ABBX5682
Switch Fabric Board
SFB 1
REV 05
711-044466
ABBX5676
Switch Fabric Board
SFB 2
REV 05
711-044466
ABBX5665
Switch Fabric Board
SFB 3
REV 05
711-044466
ABBX5699
Switch Fabric Board
SFB 4
REV 05
711-044466
ABBX5603
Switch Fabric Board
SFB 5
REV 05
711-044466
ABBX5587
Switch Fabric Board
SFB 6
REV 05
711-044466
ABBX5607
Switch Fabric Board
517
SFB 7
FPC 0
CPU
PIC 0
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
PIC 1
Xcvr 0
PIC 2
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
PIC 3
Xcvr 0
FPC 1
CPU
MIC 0
PIC 0
Xcvr 0
MIC 1
PIC 2
Xcvr 0
FPC 2
CPU
PIC 0
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
Xcvr 4
Xcvr 5
Xcvr 6
Xcvr 7
PIC 1
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
Xcvr 4
Xcvr 5
Xcvr 6
Xcvr 7
PIC 2
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
Xcvr 4
Xcvr 5
Xcvr 6
Xcvr 7
PIC 3
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
Xcvr 4
Xcvr 5
518
REV 05
REV 09
REV 08
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
711-044466
ABBX5669
750-037355
CAAF0924
711-035209
CAAB9842
BUILTIN
BUILTIN
01
740-021308
19T511101656
01
740-031980
AMA04RU
01
740-031980
193363A00558
01
740-031980
B10M00202
BUILTIN
BUILTIN
NON-JNPR
X12J00328
BUILTIN
BUILTIN
01
740-031980
AMA088W
01
740-031980
B10L04211
01
740-021308
19T511101602
01
740-031980
B10L04151
BUILTIN
BUILTIN
NON-JNPR
X12J00332
18
750-033205
ZE0128
06
711-035209
ZG5431
15
750-033199
ZP6435
BUILTIN
BUILTIN
01
740-032210
J11E46118
15
750-033199
ZP6442
BUILTIN
BUILTIN
01
740-032210
UMN03T4
16
750-037358
CAAL1001
08
711-035209
CAAK7927
BUILTIN
BUILTIN
01
740-031980
193363A00589
01
740-021308
973152A00028
01
740-031980
193363A00376
01
740-021308
973152A00016
01
740-031980
193363A00499
01
740-021308
973152A00039
01
740-031980
B11E01239
01
740-021308
973152A00058
BUILTIN
BUILTIN
01
740-031980
B10M00075
01
740-021308
973152A00014
01
740-031980
AMA0638
01
740-021308
973152A00063
01
740-031980
AMA0629
01
740-021308
973152A00053
01
740-031980
193363A00344
01
740-021308
973152A00046
BUILTIN
BUILTIN
01
740-031980
AMA062M
01
740-021308
973152A00080
01
740-031980
193363A00580
01
740-021308
973152A00064
01
740-031980
093363A01494
01
740-021308
973152A00020
01
740-031980
123363A00047
01
740-021308
973152A00072
BUILTIN
BUILTIN
01
740-021308
03DZ06A01033
01
740-021308
973152A00022
01
740-021308
03DZ06A01026
01
740-021308
973152A00013
01
740-021308
03DZ06A01028
01
740-021308
973152A00079
Switch Fabric Board

MPC Type 4-2
HMPC PMB 2G
4x10GE SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
1X100GE CFP
CFP-100G-SR10
4x10GE SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
1X100GE CFP
CFP-100G-SR10
MPCE Type 3D
HMPC PMB 2G
1X100GE CFP
1X100GE CFP
CFP-100G-LR4
1X100GE CFP
1X100GE CFP
CFP-100G-LR4
MPC Type 4-1
HMPC PMB 2G
8X10GE SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
8X10GE SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
8X10GE SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
8X10GE SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
Xcvr 6
Xcvr 7
FPC 3
CPU
PIC 0
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
PIC 1
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
PIC 2
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
PIC 3
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
FPC 4
CPU
MIC 0
PIC 0
Xcvr
Xcvr
MIC 1
PIC 2
Xcvr
Xcvr
FPC 5
CPU
PIC 0
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
Xcvr 4
Xcvr 5
Xcvr 6
Xcvr 7
PIC 1
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
Xcvr 4
Xcvr 5
Xcvr 6
Xcvr 7
PIC 2
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
Xcvr 4
Xcvr 5
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV 01
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
0
1
REV
REV
REV
0
1
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
01
33
11
740-021308
03DZ06A01018
740-021308
973152A00025
750-028467
CAAF5400
711-029089
CAAH7626
BUILTIN
BUILTIN
01
740-021308
973152A00066
01
740-021308
973152A00021
01
740-021308
973152A00062
01
740-021308
973152A00027
BUILTIN
BUILTIN
01
740-021308
973152A00065
740-021308
973152A00069
01
740-021308
973152A00026
01
740-021308
973152A00003
BUILTIN
BUILTIN
01
740-021308
973152A00035
01
740-021308
973152A00004
01
740-021308
973152A00049
01
740-021308
973152A00055
BUILTIN
BUILTIN
01
740-021308
973152A00010
01
740-021308
973152A00001
01
740-021308
973152A00073
01
740-021308
973152A00012
21
750-033205
ZG5028
05
711-035209
YX3911
03
750-036233
ZL2036
BUILTIN
BUILTIN
01
740-032986
QB220708
01
740-032986
QB220735
03
750-036233
ZL2028
BUILTIN
BUILTIN
01
740-032986
QB220727
01
740-032986
QB220715
11
750-037358
CAAE2196
08
711-035209
CAAD9074
BUILTIN
BUILTIN
01
740-031980
AMA062S
01
740-031980
AMA062P
01
740-031980
AMA052R
01
740-031980
AMA0632
01
740-031980
193363A00564
01
740-031980
193363A00229
01
740-031980
193363A00363
01
740-031980
193363A00278
BUILTIN
BUILTIN
01
740-031980
AMA04CC
01
740-021308
AD0927A001W
01
740-031980
AMA04N2
01
740-031980
AMA062U
01
740-031980
193363A00491
01
740-031980
183363A01511
01
740-031980
193363A00565
01
740-031980
193363A00405
BUILTIN
BUILTIN
01
740-031980
AMA07QX
01
740-031980
AMA06MS
01
740-031980
193363A00318
01
740-031980
193363A00402
01
740-031980
193363A00174
01
740-031980
193363A00388
SFP+-10G-SR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPCE Type 3D
HMPC PMB 2G
2X40GE QSFP
2X40GE QSFP
QSFP+-40G-SR4
QSFP+-40G-SR4
2X40GE QSFP
2X40GE QSFP
QSFP+-40G-SR4
QSFP+-40G-SR4
MPC Type 4-1
HMPC PMB 2G
8X10GE SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
8X10GE SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
8X10GE SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
519
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 6
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 7
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
520
6
7
0
1
2
4
5
6
7
REV 01
REV 01
REV
REV
REV
REV 01
REV
REV
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
REV
REV
0
1
2
3
4
5
6
7
REV
REV
REV
REV
REV
REV
REV
REV
0
1
2
3
4
5
6
7
REV
REV
REV
REV
REV
REV
REV
REV
0
1
2
3
4
5
6
REV
REV
REV
REV
REV
REV
REV
740-031980
193363A00377
740-031980
193363A00234
BUILTIN
BUILTIN
01
740-031980
AMA062T
01
740-031980
193363A00550
01
740-031980
193363A00364
740-031980
AMA0630
01
740-031980
193363A00509
01
740-031980
193363A00459
01
740-031980
113363A00191
01
740-031980
193363A00352
33
750-028467
CAAF5552
11
711-029089
CAAH7601
BUILTIN
BUILTIN
01
740-021308
AD0927A0036
01
740-021308
AD0927A003M
01
740-021308
AD0927A003G
01
740-021308
AD0927A0031
BUILTIN
BUILTIN
01
740-031980
193363A00331
01
740-031980
193363A00325
01
740-031980
193363A00417
01
740-031980
183363A02509
BUILTIN
BUILTIN
01
740-021308
T09K75140
01
740-031980
B11A04356
01
740-031980
B11K01952
01
740-031980
B11K01914
BUILTIN
BUILTIN
01
740-021308
T09K75157
01
740-021308
T09K75194
01
740-031980
B11K01926
01
740-031980
B11K01936
16
750-037358
CAAL1012
08
711-035209
CAAJ3851
BUILTIN
BUILTIN
01
740-031980
AMA04NK
01
740-031980
B11F00260
01
740-031980
B11E02192
01
740-031980
AMA04CP
01
740-031980
AJ40JKK
01
740-031980
B11F00238
01
740-031980
B10M00275
01
740-031980
193363A00211
BUILTIN
BUILTIN
01
740-031980
B11D05577
01
740-031980
B11G00586
01
740-031980
AMA08B7
01
740-031980
AMA04Q0
01
740-031980
B11D05840
01
740-031980
B11E00467
01
740-031980
B11E00029
01
740-021308
19T511101712
BUILTIN
BUILTIN
01
740-031980
193363A00568
01
740-031980
B10M00166
01
740-031980
B10M00212
01
740-031980
B11D05823
01
740-021308
03DZ06A01005
01
740-021308
03DZ06A01003
01
740-021308
03DZ06A01009
SFP+-10G-SR
SFP+-10G-SR
8X10GE SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC Type 4-1
HMPC PMB 2G
8X10GE SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
8X10GE SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
8X10GE SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
Xcvr 7
PIC 3
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
Xcvr 4
Xcvr 5
Xcvr 6
Xcvr 7
FPC 8
CPU
MIC 0
PIC 0
Xcvr
Xcvr
MIC 1
PIC 2
Xcvr
Xcvr
FPC 9
CPU
PIC 0
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
PIC 1
PIC 2
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
PIC 3
ADC 0
ADC 1
ADC 2
ADC 3
ADC 4
ADC 5
ADC 6
ADC 7
ADC 8
ADC 9
Fan Tray 0
Fan Tray 1
Fan Tray 2
Fan Tray 3

extensive (MX2010
Router)
REV 01
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
01
01
01
01
01
01
01
03
08
03
0
1
REV 01
REV 01
REV 03
0
1
REV
REV
REV
REV
01
01
09
08
REV
REV
REV
REV
01
01
01
01
REV
REV
REV
REV
01
01
01
01
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
13
13
13
13
13
13
13
13
13
07
03
2A
2A
2A
740-021308
03DZ06A01004
BUILTIN
BUILTIN
740-021308
03DZ06A01017
740-021308
03DZ06A01016
740-021308
03DZ06A01024
740-021308
03DZ06A01008
740-030658
AD0946A02UH
740-021308
T09J67913
740-021308
AD0837ES09G
740-021308
03DZ06A01015
750-045372
CAAD3111
711-035209
CAAD8033
750-036233
ZL2032
BUILTIN
BUILTIN
740-032986
QB230273
740-032986
QB230254
750-036233
ZL2021
BUILTIN
BUILTIN
740-032986
QB390962
740-032986
QB390960
750-037355
CAAF1531
711-035209
CAAB9927
BUILTIN
BUILTIN
740-031980
193363A00525
740-031980
193363A00504
740-031980
193363A00368
740-031980
AJ40JSS
BUILTIN
BUILTIN
BUILTIN
BUILTIN
740-031980
123363A00042
740-031980
B10M00023
740-031980
AJ802EM
740-031980
B11E02348
BUILTIN
BUILTIN
750-043596
ABBX5532
750-043596
ABBX5550
750-043596
ABBX5571
750-043596
ABBX5568
750-043596
ABBX5556
750-043596
ABBX5553
750-043596
ABBX5541
750-043596
ABBX5578
750-043596
ABBX5560
750-043596
ABBV7188
760-046960
ACAY0127
760-046960
ACAY0068
760-046960
ACAY0072
760-046960
ACAY0070
SFP+-10G-SR
8X10GE SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-USR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPCE Type 3D
HMPC PMB 2G
2X40GE QSFP
2X40GE QSFP
QSFP+-40G-SR4
QSFP+-40G-SR4
2X40GE QSFP
2X40GE QSFP
QSFP+-40G-SR4
QSFP+-40G-SR4
MPC Type 4-2
HMPC PMB 2G
4x10GE SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
1X100GE CFP
4x10GE SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
1X100GE CFP
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
172mm FanTray
172mm FanTray
172mm FanTray
172mm FanTray
6
6
6
6
Fans
Fans
Fans
Fans
user@host > show chassis hardware extensive

Hardware inventory:
Item
Description
Chassis
JN11E233DAFK
MX2010
Jedec Code:
0x7fb0
EEPROM Version:
0x02
S/N:
JN11E233DAFK
Assembly ID: 0x0557
Assembly Version: 00.00
Date:
00-00-0000
Assembly Flags:
0x00
ID: MX2010
Board Information Record:
Address 0x00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
I2C Hex Data:
521
Address 0x00: 7f b0 02 ff 05 57 00 00 00 00 00 00 00 00 00 00
Address 0x10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x20: 4a 4e 31 31 45 32 33 33 44 41 46 4b 00 00 00 00
Address 0x30: 00 00 00 ff 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Midplane
REV 26
750-044636
ABAB9357
Lower Backplane
Jedec Code:
0x7fb0
EEPROM Version:
0x02
P/N:
750-044636
S/N:
S/N ABAB9357
Assembly ID: 0x0b66
Date:
08-28-2012
Assembly Flags:
0x00
Version:
REV 26
CLEI Code:
PROTOXCLEI
ID: Lower Backplane
FRU Model Number: PROTO-ASSEMBLY
Address 0x00: ad 01 08 00 2c 21 72 70 a0 00 ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 ff 0b 66 01 1a 52 45 56 20 32 36 00 00
Address 0x10: 00 00 00 00 37 35 30 2d 30 34 34 36 33 36 00 00
Address 0x20: 53 2f 4e 20 41 42 41 42 39 33 35 37 00 1c 08 07
Address 0x30: dc ff ff ff ad 01 08 00 2c 21 72 70 a0 00 ff ff
Address 0x40: ff ff ff ff 01 50 52 4f 54 4f 58 43 4c 45 49 50
Address 0x50: 52 4f 54 4f 2d 41 53 53 45 4d 42 4c 59 00 00 00
Address 0x60: 00 00 00 00 00 00 41 30 30 ff ff ff ff ff ff ff
Address 0x70: ff ff ff c2 ff ff ff ff ff ff ff ff ff ff ff ff
Midplane 1
REV 01
711-044557
ABAB8643
Upper Backplane
Jedec Code:
0x7fb0
EEPROM Version:
0x01
P/N:
711-044557
S/N:
S/N ABAB8643
Assembly ID: 0x0b65
Date:
07-27-2012
Assembly Flags:
0x00
Version:
REV 01
ID: Upper Backplane
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 01 ff 0b 65 01 01 52 45 56 20 30 31 00 00
Address 0x10: 00 00 00 00 37 31 31 2d 30 34 34 35 35 37 00 00
Address 0x20: 53 2f 4e 20 41 42 41 42 38 36 34 33 00 1b 07 07
Address 0x30: dc ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 00 ff ff ff ff ff ff ff ff ff ff ff
PMP
REV 04
711-032426
ACAJ1677
Power Midplane
Jedec Code:
0x7fb0
EEPROM Version:
0x01
P/N:
711-032426
S/N:
S/N ACAJ1677
Assembly ID: 0x045d
Date:
07-20-2012
Assembly Flags:
0x00
Version:
REV 04
ID: Power Midplane
I2C Hex Data:
Address 0x00: 7f b0 01 ff 04 5d 01 04 52 45 56 20 30 34 00 00
Address 0x10: 00 00 00 00 37 31 31 2d 30 33 32 34 32 36 00 00
Address 0x20: 53 2f 4e 20 41 43 41 4a 31 36 37 37 00 14 07 07
522
FPM Board
REV 08
760-044634
ABBV9726
Front Panel Display
Jedec Code:
0x7fb0
EEPROM Version:
0x02
P/N:
760-044634
S/N:
S/N ABBV9726
Assembly ID: 0x0b64
Date:
09-10-2012
Assembly Flags:
0x00
Version:
REV 08
CLEI Code:
IPMYA4EJRA
ID: Front Panel Display
FRU Model Number: MX2010-CRAFT-S
I2C Hex Data:
Address 0x00: 7f b0 02 ff 0b 64 01 08 52 45 56 20 30 38 00 00
Address 0x10: 00 00 00 00 37 36 30 2d 30 34 34 36 33 34 00 00
Address 0x20: 53 2f 4e 20 41 42 42 56 39 37 32 36 00 0a 09 07
Address 0x40: ff ff ff ff 01 49 50 4d 59 41 34 45 4a 52 41 4d
Address 0x50: 58 32 30 31 30 2d 43 52 41 46 54 2d 53 00 00 00
Address 0x70: ff ff ff 93 ff ff ff ff ff ff ff ff ff ff ff ff
PSM 0
REV 01
740-045050
1E02224000P
DC 52V Power Supply
Module
Jedec Code:
0x7fb0
EEPROM Version:
0x02
P/N:
740-045050
S/N:
1E02224000P
Assembly ID: 0x0478
Date:
12-06-2012
Assembly Flags:
0x00
Version:
REV 01
CLEI Code:
XXXXXXXXXX
ID: DC 52V Power Supply Module FRU Model Number: MX2000-PSM-HC-DC-S-A
I2C Hex Data:
Address 0x00: 7f b0 02 ff 04 78 01 01 52 45 56 20 30 31 00 00
Address 0x10: 00 00 00 00 37 34 30 2d 30 34 35 30 35 30 00 00
Address 0x20: 31 45 30 32 32 32 34 30 30 30 50 00 00 06 0c 07
Address 0x40: ff ff ff ff 01 58 58 58 58 58 58 58 58 58 58 4d
Address 0x50: 58 32 30 30 30 2d 50 53 4d 2d 48 43 2d 44 43 2d
Address 0x60: 53 2d 41 00 00 00 31 30 31 ff ff ff ff ff ff ff
Address 0x70: ff ff ff 4a 00 00 00 00 00 00 00 00 00 00 00 00
PSM 1
REV 01
740-045050
1E02224000M
DC 52V Power Supply
Module
Jedec Code:
0x7fb0
EEPROM Version:
0x02
P/N:
740-045050
S/N:
1E02224000M
Assembly ID: 0x0478
Date:
12-06-2012
Assembly Flags:
0x00
Version:
REV 01
CLEI Code:
XXXXXXXXXX
ID: DC 52V Power Supply Module FRU Model Number: MX2000-PSM-HC-DC-S-A
I2C Hex Data:
Address 0x00: 7f b0 02 ff 04 78 01 01 52 45 56 20 30 31 00 00
Address 0x10: 00 00 00 00 37 34 30 2d 30 34 35 30 35 30 00 00
Address 0x20: 31 45 30 32 32 32 34 30 30 30 4d 00 00 06 0c 07
Address 0x40: ff ff ff ff 01 58 58 58 58 58 58 58 58 58 58 4d
Address 0x50: 58 32 30 30 30 2d 50 53 4d 2d 48 43 2d 44 43 2d
Address 0x60: 53 2d 41 00 00 00 31 30 31 ff ff ff ff ff ff ff
Address 0x70: ff ff ff 4a 00 00 00 00 00 00 00 00 00 00 00 00
...
PDM 0
REV 01
740-045234
1E262250067
Jedec Code:
0x7fb0
EEPROM Version:
0x02
P/N:
740-045234
S/N:
1E262250067
523
Assembly ID: 0x047b

Date:
06-28-2012
Assembly Flags:
0x00
Version:
REV 01
CLEI Code:
IPUPAJSKAA
ID: DC Power Dist Module
FRU Model Number: MX2000-PDM-DC-S-A
I2C Hex Data:
Address 0x00: 7f b0 02 ff 04 7b 01 01 52 45 56 20 30 31 00 00
Address 0x10: 00 00 00 00 37 34 30 2d 30 34 35 32 33 34 00 00
Address 0x20: 31 45 32 36 32 32 35 30 30 36 37 00 00 1c 06 07
Address 0x40: ff ff ff ff 01 49 50 55 50 41 4a 53 4b 41 41 4d
Address 0x50: 58 32 30 30 30 2d 50 44 4d 2d 44 43 2d 53 2d 41
Address 0x70: ff ff ff 89 00 00 00 00 00 00 00 00 00 00 00 00
740-041821
9009099704
RE-S-1800x4
Jedec Code:
0x7fb0
EEPROM Version:
0x02
P/N:
740-041821
S/N:
9009099704
Assembly ID: 0x09c0
Date:
03-15-2012
Assembly Flags:
0x00
Version:
REV 02
ID: RE-S-1800x4
FRU Model Number: RE-S-1800X4-16G-S
Address 0x00: 54 32 30 32 37 44 41 2d 34 34 47 42 23 41 23 00
I2C Hex Data:
Address 0x00: 7f b0 02 ff 09 c0 01 02 52 45 56 20 30 32 00 00
Address 0x10: 00 00 00 00 37 34 30 2d 30 34 31 38 32 31 00 00
Address 0x20: 39 30 30 39 30 39 39 37 30 34 00 00 00 0f 03 07
Address 0x30: dc ff ff ff 54 32 30 32 37 44 41 2d 34 34 47 42
Address 0x40: 23 41 23 00 01 00 00 00 00 00 00 00 00 00 00 52
Address 0x50: 45 2d 53 2d 31 38 30 30 58 34 2d 31 36 47 2d 53
Address 0x70: ff ff ff 8c ff ff ff ff ff ff ff ff ff ff ff ff
ad0
ad1
30533 MB UGB94BPH32H0S1-KCI
11000019592
Disk 1
Intel
uhub0
vendor 0x8087
uhub1
DIMM 0
DIMM 1
DIMM 2
DIMM 3
740-041821
9009099706
RE-S-1800x4
Jedec Code:
0x7fb0
EEPROM Version:
0x02
P/N:
740-041821
S/N:
9009099706
Assembly ID: 0x09c0
Date:
02-23-2012
Assembly Flags:
0x00
Version:
REV 02
ID: RE-S-1800x4
FRU Model Number: RE-S-1800X4-16G-S
Address 0x00: 54 32 30 32 37 44 41 2d 34 34 47 42 23 41 23 00
I2C Hex Data:
Address 0x00: 7f b0 02 ff 09 c0 01 02 52 45 56 20 30 32 00 00
Address 0x10: 00 00 00 00 37 34 30 2d 30 34 31 38 32 31 00 00
Address 0x20: 39 30 30 39 30 39 39 37 30 36 00 00 00 17 02 07
Address 0x30: dc ff ff ff 54 32 30 32 37 44 41 2d 34 34 47 42
Address 0x40: 23 41 23 00 01 00 00 00 00 00 00 00 00 00 00 52
Address 0x50: 45 2d 53 2d 31 38 30 30 58 34 2d 31 36 47 2d 53
Address 0x70: ff ff ff 8c ff ff ff ff ff ff ff ff ff ff ff ff
ad0
3998 MB Virtium - TuffDrive VCF P1T0200262860208 114 Compact Flash
ad1
UNIGEN-499551-000404 Disk 1
524
CB 0
REV 13
750-040257
CAAF8436
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
750-040257
S/N:
Assembly ID: 0x0b26
Assembly Version:
Date:
08-29-2012
Assembly Flags:
Version:
REV 13
CLEI Code:
ID: Control Board
FRU Model Number:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 ff 0b 26 01 0d 52 45 56 20
Address 0x10: 00 00 00 00 37 35 30 2d 30 34 30 32
Address 0x20: 53 2f 4e 20 43 41 41 46 38 34 33 36
Address 0x30: dc ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 01 50 52 4f 54 4f 58 43
Address 0x50: 52 4f 54 4f 2d 41 53 53 45 4d 42 4c
Address 0x60: 00 00 00 00 00 00 41 30 30 ff ff ff
Address 0x70: ff ff ff c2 ff ff ff ff ff ff ff ff
...
SPMB 0
REV 02
711-041855
ABBV3825
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
711-041855
S/N:
Assembly ID: 0x0b29
Assembly Version:
Date:
08-14-2012
Assembly Flags:
Version:
REV 02
ID: PMB Board
I2C Hex Data:
Address 0x00: 7f b0 01 ff 0b 29 01 02 52 45 56 20
Address 0x10: 00 00 00 00 37 31 31 2d 30 34 31 38
Address 0x20: 53 2f 4e 20 41 42 42 56 33 38 32 35
Address 0x40: ff ff ff ff 00 ff ff ff ff ff ff ff
Address 0x70: ff ff ff ff 00 00 00 00 00 00 00 00
...
SFB 0
REV 05
711-044466
ABBX5682
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
711-044466
S/N:
Assembly ID: 0x0b25
Assembly Version:
Date:
09-07-2012
Assembly Flags:
Version:
REV 05
CLEI Code:
ID: Switch Fabric Board
FRU Model Number:
I2C Hex Data:
Address 0x00: 7f b0 02 ff 0b 25 01 05 52 45 56 20
Address 0x10: 00 00 00 00 37 31 31 2d 30 34 34 34
Address 0x20: 53 2f 4e 20 41 42 42 58 35 36 38 32
Address 0x50: 52 4f 54 4f 2d 41 53 53 45 4d 42 4c
Address 0x60: 00 00 00 00 00 00 41 30 30 ff ff ff
Address 0x70: ff ff ff c2 00 00 00 01 00 00 00 00
...
FPC 0
REV 09
750-037355
CAAF0924
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
750-037355
S/N:
Assembly ID: 0x0b4e
Assembly Version:
Control Board
0x02
S/N CAAF8436
01.13
0x00
PROTOXCLEI
PROTO-ASSEMBLY
ff ff ff ff
31
35
00
ff
4c
59
ff
ff
33
37
1d
ff
45
00
ff
ff
00
00
08
ff
49
00
ff
ff
00
00
07
ff
50
00
ff
ff
PMB Board
0x01
S/N ABBV3825
01.02
0x00
ff ff ff ff
30
35
00
ff
ff
ff
ff
00
32
35
0e
ff
ff
ff
ff
00
00
00
08
ff
ff
ff
ff
00
00
00
07
ff
ff
ff
ff
00
Switch Fabric Board

0x02
S/N ABBX5682
01.05
0x00
PROTOXCLEI
PROTO-ASSEMBLY
ff ff ff ff
30
36
00
ff
4c
59
ff
00
35
36
07
ff
45
00
ff
00
00
00
09
ff
49
00
ff
48
00
00
07
ff
50
00
ff
00
MPC Type 4-2

0x02
S/N CAAF0924
01.09
525
Date:
05-21-2012
Assembly Flags:
0x00
Version:
REV 09
CLEI Code:
PROTOXCLEI
ID: MPC Type 4-2
FRU Model Number: MPC4E-2CGE-8XGE
I2C Hex Data:
Address 0x00: 7f b0 02 ff 0b 4e 01 09 52 45 56 20 30 39 00 00
Address 0x10: 00 00 00 00 37 35 30 2d 30 33 37 33 35 35 00 00
Address 0x20: 53 2f 4e 20 43 41 41 46 30 39 32 34 00 15 05 07
Address 0x40: ff ff ff ff 01 50 52 4f 54 4f 58 43 4c 45 49 4d
Address 0x50: 50 43 34 45 2d 32 43 47 45 2d 38 58 47 45 00 00
Address 0x70: ff ff ff c6 ff ff ff ff ff ff ff ff ff ff ff ff
CPU
REV 08
711-035209
CAAB9842
HMPC PMB 2G
Jedec Code:
0x7fb0
EEPROM Version:
0x01
P/N:
711-035209
S/N:
S/N CAAB9842
Assembly ID: 0x0b04
Date:
05-17-2012
Assembly Flags:
0x00
Version:
REV 08
ID: HMPC PMB 2G
I2C Hex Data:
Address 0x00: 7f b0 01 ff 0b 04 01 08 52 45 56 20 30 38 00 00
Address 0x10: 00 00 00 00 37 31 31 2d 30 33 35 32 30 39 00 00
Address 0x20: 53 2f 4e 20 43 41 41 42 39 38 34 32 00 11 05 07
Address 0x70: ff ff ff ff 00 00 00 00 00 00 00 00 00 00 00 00
PIC 0
BUILTIN
BUILTIN
4x10GE SFPP
Jedec Code:
0x0000
EEPROM Version:
0x00
P/N:
BUILTIN
S/N:
BUILTIN
Assembly ID: 0x0a53
Date:
00-00-0000
Assembly Flags:
0x00
ID: 4x10GE SFPP
Address 0x00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
I2C Hex Data:
Address 0x00: 00 00 00 00 0a 53 00 00 00 00 00 00 00 00 00 00
Address 0x10: 00 00 00 00 42 55 49 4c 54 49 4e 00 4d 58 43 00
Address 0x20: 42 55 49 4c 54 49 4e 00 4d 58 43 00 00 00 00 00
Address 0x30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x70: 00 00 00 00 c0 02 ae 64 00 00 00 00 0a 52 00 00
Xcvr 0
REV 01
740-021308
19T511101656
SFP+-10G-SR
Xcvr 1
REV 01
740-031980
AMA04RU
SFP+-10G-SR
Xcvr 2
REV 01
740-031980
193363A00558
SFP+-10G-SR
Xcvr 3
REV 01
740-031980
B10M00202
SFP+-10G-SR
...
ADC 0
REV 13
750-043596
ABBX5532
Adapter Card
Jedec Code:
0x7fb0
EEPROM Version:
0x02
P/N:
750-043596
S/N:
S/N ABBX5532
Assembly ID: 0x0b3d
Date:
09-12-2012
Assembly Flags:
0x00
Version:
REV 13
CLEI Code:
IPUCBA8CAA
ID: Adapter Card
FRU Model Number: MX2000-LC-ADAPTER
526
Board Information
Address 0x00: ff
I2C Hex Data:
Address 0x00: 7f
Address 0x10: 00
Address 0x20: 53
Address 0x30: dc
Address 0x40: ff
Address 0x50: 58
Address 0x60: 00
Address 0x70: ff
...

models (MX2010
Router)

clei-models (MX2010
Routers)
Record:
ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
b0
00
2f
ff
ff
32
00
ff
02
00
4e
ff
ff
30
00
ff
ff
00
20
ff
ff
30
00
3a
0b
37
41
ff
01
30
00
00
3d
35
42
ff
49
2d
00
00
01
30
42
ff
50
4c
41
00
0d
2d
58
ff
55
43
00
00
user@host > show chassis hardware models

Hardware inventory:
Item
Version Part number
FPM Board
REV 06
711-032349
PSM 4
REV 0C
740-033727
PSM 5
REV 0B
740-033727
PSM 6
REV 0B
740-033727
PSM 7
REV 0C
740-033727
PSM 8
REV 0C
740-033727
PDM 0
REV 0B
740-038109
PDM 1
REV 0B
740-038109
740-041821
740-041821
CB 0
REV 08
750-040257
CB 1
REV 08
750-040257
SFB 0
REV 06
711-032385
SFB 1
REV 07
711-032385
SFB 2
REV 07
711-032385
SFB 3
REV 07
711-032385
SFB 4
REV 07
711-032385
SFB 5
REV 07
711-032385
SFB 6
REV 07
711-032385
SFB 7
REV 07
711-032385
FPC 0
REV 33
750-028467
FPC 1
REV 21
750-033205
MIC 0
REV 03
750-033307
MIC 1
REV 03
750-033307
FPC 8
REV 22
750-031089
MIC 0
REV 26
750-028392
MIC 1
REV 26
750-028387
FPC 9
REV 11
750-036284
ADC 0
REV 05
750-043596
ADC 1
REV 01
750-043596
ADC 8
REV 01
750-043596
ADC 9
REV 02
750-043596
Fan Tray 0
REV 2A
760-046960
Fan Tray 1
REV 2A
760-046960
Fan Tray 2
REV 2A
760-046960
Fan Tray 3
REV 2A
760-046960
52
30
35
ff
43
2d
00
00
45
34
35
ff
42
41
ff
00
56
33
33
ff
41
44
ff
00
20
35
32
ff
38
41
ff
00
Serial number
ZX8744
VK00254
VG00015
VH00097
VJ00151
VJ00149
WA00008
WA00014
9009094134
9009094141
CAAB3491
CAAB3489
ZV1828
ZZ2568
ZZ2563
ZZ2564
ZZ2580
ZZ2579
CAAB4882
CAAB4898
CAAB1919
ZG5027
ZV6299
ZV6268
ZT9746
ABBS1150
ABBR9582
ZL3591
CAAC2073
ZV4117
ZV4107
ZW1555
ACAY0015
ACAY0019
ACAY0020
ACAY0021
user@host > show chassis hardware clei-models

Hardware inventory:
Item
FPM Board
REV 06
711-032349
PROTOXCLEI
PSM 4
REV 0C
740-033727
0000000000
PSM 5
REV 0B
740-033727
0000000000
PSM 6
REV 0B
740-033727
0000000000
31
39
00
ff
43
50
ff
00
33
36
0c
ff
41
54
ff
00
00
00
09
ff
41
45
ff
00
00
00
07
ff
4d
52
ff
00
FRU model number

711-032349
00000000000000000000000
00000000000000000000000
00000000000000000000000
00000000000000000000000
00000000000000000000000
RE-S-1800X4-16G-S
RE-S-1800X4-16G-S
750-040257
750-040257
711-032385
711-032385
711-032385
711-032385
711-032385
711-0323856
711-044170
711-044170
MPC-3D-16XGE-SFPP
MX-MPC3-3D
MIC3-3D-10XGE-SFPP
MIC3-3D-10XGE-SFPP
MX-MPC2-3D
MIC-3D-20GE-SFP
MIC-3D-4XGE-XFP
MPCE-3D-16XGE-SFPP
750-043596
750-043596
750-043596
750-043596
FRU model number

711-032349
00000000000000000000000
00000000000000000000000
00000000000000000000000
527
PSM 7
REV 0C
PSM 8
REV 0C
PDM 0
REV 0B
PDM 1
REV 0B
CB 0
REV 08
CB 1
REV 08
SFB 0
REV 06
SFB 1
REV 07
SFB 2
REV 07
SFB 3
REV 07
SFB 4
REV 07
SFB 5
REV 07
SFB 6
REV 07
SFB 7
REV 07
FPC 0
REV 33
FPC 1
REV 21
MIC 0
REV 03
MIC 1
REV 03
FPC 8
REV 22
MIC 0
REV 26
MIC 1
REV 26
FPC 9
REV 11
ADC 0
REV 05
ADC 1
REV 01
ADC 8
REV 01
ADC 9
REV 02
Fan Tray 0
REV 2A
Fan Tray 1
REV 2A
Fan Tray 2
REV 2A
Fan Tray 3
REV 2A

(MX2020 Router)
528
740-033727
740-033727
740-038109
740-038109
740-041821
740-041821
750-040257
750-040257
711-032385
711-032385
711-032385
711-032385
711-032385
711-032385
711-032385
711-032385
750-028467
750-033205
750-033307
750-033307
750-031089
750-028392
750-028387
750-036284
750-043596
750-043596
750-043596
750-043596
760-046960
760-046960
760-046960
760-046960
user@host > show chassis hardware

Hardware inventory:
Item
Version Part number
Chassis
Midplane
REV 27
750-040240
Midplane 1
REV 04
711-032386
PMP 1
REV 05
711-032428
PMP 0
REV 04
711-032426
FPM Board
REV 06
760-040242
PSM 0
REV 01
740-045050
Module
PSM 1
REV 01
740-045050
Module
PSM 2
REV 01
740-045050
Module
PSM 3
REV 01
740-045050
Module
PSM 4
REV 01
740-045050
Module
PSM 7
REV 01
740-045050
Module
PSM 8
REV 01
740-045050
Module
PSM 9
REV 01
740-045050
Module
PSM 10
REV 01
740-045050
Module
PSM 11
REV 01
740-045050
0000000000
0000000000
00000000000000000000000
00000000000000000000000
PROTOXCLEI
PROTOXCLEI
COUIBAYBAA
COUIA15BAA
COUIA16BAA
CMUIACGBAA
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
RE-S-1800X4-16G-S
RE-S-1800X4-16G-S
750-040257
750-040257
711-032385
711-032385
711-032385
711-032385
711-032385
711-0323856
711-044170
711-044170
MPC-3D-16XGE-SFPP
MX-MPC3-3D
MIC3-3D-10XGE-SFPP
MIC3-3D-10XGE-SFPP
MX-MPC2-3D
MIC-3D-20GE-SFP
MIC-3D-4XGE-XFP
MPCE-3D-16XGE-SFPP
750-043596
750-043596
750-043596
750-043596
Serial number
JN11E2227AFJ
ABAB9384
ABAB9386
ACAJ1579
ACAJ1524
ABBT8837
1E022240056
Description
MX2020
Lower Power Midplane
Upper Backplane
Upper Power Midplane
Front Panel Display
DC 52V Power Supply
1E022240054
DC 52V Power Supply
1E02224005H
DC 52V Power Supply
1E022240053
DC 52V Power Supply
1E02224004K
DC 52V Power Supply
1E02224006W
DC 52V Power Supply
1E022240062
DC 52V Power Supply
1E02224005B
DC 52V Power Supply
1E02224005A
DC 52V Power Supply
1E022240052
DC 52V Power Supply
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
Module
PSM 12
REV 01
Module
PSM 13
REV 01
Module
PSM 14
REV 01
Module
PSM 15
REV 01
Module
PSM 16
REV 01
Module
PSM 17
REV 01
Module
PDM 0
REV 01
PDM 1
REV 01
PDM 2
REV 01
PDM 3
REV 01
CB 0
REV 14
CB 1
REV 08
SPMB 0
REV 01
SPMB 1
REV 02
SFB 0
REV 03
SFB 1
REV 05
SFB 2
REV 05
SFB 3
REV 05
SFB 4
REV 05
SFB 5
REV 05
SFB 6
REV 03
SFB 7
REV 05
FPC 0
REV 30
CPU
REV 10
PIC 0
Xcvr 0
REV 01
Xcvr 1
REV 01
Xcvr 2
REV 01
Xcvr 3
REV 01
PIC 1
Xcvr 0
REV 01
Xcvr 1
REV 01
Xcvr 2
REV 01
Xcvr 3
REV 01
PIC 2
Xcvr 0
REV 01
Xcvr 1
REV 01
Xcvr 2
REV 01
Xcvr 3
REV 01
PIC 3
Xcvr 0
REV 01
Xcvr 1
REV 01
Xcvr 2
REV 01
Xcvr 3
REV 01
FPC 1
REV 30
CPU
REV 10
PIC 0
Xcvr 0
REV 01
Xcvr 1
REV 01
Xcvr 2
REV 01
Xcvr 3
REV 01
PIC 1
740-045050
1E022240051
DC 52V Power Supply
740-045050
1E022240058
DC 52V Power Supply
740-045050
1E02224004L
DC 52V Power Supply
740-045050
1E02224005M
DC 52V Power Supply
740-045050
1E02224006S
DC 52V Power Supply
740-045050
1E02224005Z
DC 52V Power Supply
740-045234
740-045234
740-045234
740-045234
740-041821
740-041821
750-040257
750-040257
711-041855
711-041855
711-044466
711-044466
711-044466
711-044466
711-044466
711-044466
711-044466
711-044466
750-028467
711-029089
BUILTIN
740-030658
740-030658
740-030658
740-030658
BUILTIN
740-030658
740-030658
740-030658
740-030658
BUILTIN
740-030658
740-030658
740-030658
740-030658
BUILTIN
740-030658
740-030658
740-030658
740-030658
750-028467
711-029089
BUILTIN
740-030658
740-030658
740-030658
740-030658
BUILTIN
1E012150033
1E012150027
1E012150028
1E012150045
9009089704
9009094138
CAAF8430
CAAB3482
ZS2290
CAAA6141
ABBV6789
ABBX5666
ABBX5678
ABBX5687
ABBX5609
ABBX5675
ABBV6805
ABBX5701
ABBN0284
ABBN0507
BUILTIN
B11E00990
B11E04357
B11F01327
B11E04375
BUILTIN
B11E02760
B11E02904
B11E03963
B11E00756
BUILTIN
B11E04418
B11E01077
B11E01128
B11F01253
BUILTIN
B11E01140
B11F01626
B11E01075
B11E01177
ABBN0208
ABBJ1084
BUILTIN
B11E04745
B11F01570
B11E04388
B11F01439
BUILTIN

RE-S-1800x4
RE-S-1800x4
Control Board
Control Board
PMB Board
PMB Board
Switch Fabric Board
Switch Fabric Board
Switch Fabric Board
Switch Fabric Board
Switch Fabric Board
Switch Fabric Board
Switch Fabric Board
Switch Fabric Board
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
529
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 2
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 3
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 4
CPU
PIC 0
530
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
REV
REV
01
01
01
01
30
10
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
REV
REV
01
01
01
01
30
10
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
REV
REV
01
01
01
01
30
10
740-030658
740-030658
740-030658
740-030658
BUILTIN
740-030658
740-030658
740-030658
740-030658
BUILTIN
740-030658
740-030658
740-030658
740-030658
750-028467
711-029089
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
750-028467
711-029089
BUILTIN
740-030658
740-030658
740-030658
740-030658
BUILTIN
740-030658
740-030658
740-030658
740-030658
BUILTIN
740-030658
740-030658
740-030658
740-030658
BUILTIN
740-030658
740-030658
740-030658
740-031980
750-028467
711-029089
BUILTIN
B11E04739
B11F01869
B11F01675
B11F01901
BUILTIN
B11F01346
B11F01288
B11F01824
B11E04312
BUILTIN
B11E02811
B11E03847
B11F01495
B11F01265
ZM5111
ZP6607
BUILTIN
AK80LJA
AK80MFZ
AK80NKL
AK80KF4
BUILTIN
AK80FBJ
AK80MM2
AK80LJV
AK80NXV
BUILTIN
AK80N1H
AK80NLS
AK80FL5
AK80NL9
BUILTIN
AK80NG2
AK80KDU
AK80MG1
AK80MM0
ABBN0302
ABBN0495
BUILTIN
B11F01581
B11E01176
B11F01251
B11E02752
BUILTIN
B11E00786
B11E01020
B11E01023
B11E02819
BUILTIN
B11E02812
B11D04437
B11F01279
B11F01333
BUILTIN
B11E00978
B11E01018
B11F01784
AK80NKP
ABBN0308
ABBJ1095
BUILTIN
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 5
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 6
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
REV
REV
01
01
01
01
30
10
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
REV
REV
01
01
01
01
32
10
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
REV 01
REV 01
740-030658
740-030658
740-030658
740-030658
BUILTIN
740-030658
740-030658
740-030658
740-030658
BUILTIN
740-030658
740-030658
740-030658
740-030658
BUILTIN
740-030658
740-030658
740-030658
740-030658
750-028467
711-029089
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
750-028467
711-029089
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
B11E04305
B11E01147
B11E01195
B11F01743
BUILTIN
B11F01892
B11E02880
B11E00725
B11E01057
BUILTIN
B11E02816
B11C04501
B11E02764
B11E00789
BUILTIN
B11F01250
B11E02847
B11E00787
B11E03803
ABBN0316
ABBJ1082
BUILTIN
B11K00523
B11K01848
B11K01865
B11K00540
BUILTIN
B11K00422
B11K00428
B11K00423
B11K01855
BUILTIN
B11K01847
B11K00526
B11K00529
B11K00525
BUILTIN
B11K00425
B11K00530
B11K01851
B11K00528
ABBN6832
ABBK6534
BUILTIN
AK80MB4
AK80FQ6
AK80N1F
AK80NLQ
BUILTIN
AK80KDR
AK80FGJ
AK80N5G
AK80KD8
BUILTIN
AK80LET
AK80N1X
AK80NRF
AK80NL2
BUILTIN
AK80N3D
AK80MRB
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
531
Xcvr
Xcvr
FPC 7
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 8
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 9
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
532
2
3
REV
REV
REV
REV
01
01
32
10
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
REV
REV
01
01
01
01
23
10
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
REV
REV
01
01
01
01
32
10
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
REV 01
REV 01
740-031980
740-031980
750-028467
711-029089
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
750-028467
711-029089
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
750-028467
711-029089
BUILTIN
740-021308
740-031980
740-021308
740-021308
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
AK80LEQ
AK80LER
ABBN6811
ABBN7288
BUILTIN
AK80NK8
AK80LJG
AK80LBU
AK80N21
BUILTIN
AK80LEU
AK80NLM
AK80NL6
AK80LES
BUILTIN
AK80LEN
AK80ME0
AK80LMG
AK80MM1
BUILTIN
AK80MG7
AK80KF9
AK80NRQ
AK80NLE
YN2977
YP1856
BUILTIN
183363A00875
183363A00851
183363A00772
183363A00882
BUILTIN
183363A00735
183363A00169
183363A00726
183363A00077
BUILTIN
183363A00168
183363A00676
183363A00732
183363A00091
BUILTIN
183363A00725
183363A00642
183363A00871
183363A00853
ABBN6798
ABBK6556
BUILTIN
9ZDZ06A00055
183363A00239
AD0915E003K
AD0915E003A
BUILTIN
AK80MRC
AK80NL5
AK80NKN
AK80N3U
BUILTIN
AK80N1T
AJ808DJ
SFP+-10G-SR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 10
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 11
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 12
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
2
3
REV 01
REV 01
0
1
2
3
REV
REV
REV
REV
REV
REV
01
01
01
01
32
10
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
REV
REV
01
01
01
01
30
10
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
REV
REV
01
01
01
01
32
10
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
REV 01
REV 01
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
750-028467
711-029089
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-021308
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
750-028467
711-029089
BUILTIN
740-030658
740-030658
740-030658
740-030658
BUILTIN
740-030658
740-030658
740-030658
740-030658
BUILTIN
740-030658
740-030658
740-030658
740-030658
BUILTIN
740-030658
740-030658
740-030658
740-030658
750-028467
711-029089
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
AK80NG4
AK80FND
BUILTIN
AK80FKQ
AK80NLT
AK80NKR
AK80LKM
ABBN6813
ABBK6542
BUILTIN
AK80NA3
AK80NLF
AK80MRH
AK80KE4
BUILTIN
973152A00030
AK80L9H
AK80ME8
AK80NLR
BUILTIN
AK80NG1
AK80MCA
AK80LFC
AK80LEM
BUILTIN
AK80N9X
AK80LAC
AK80LF2
AK80N8T
ABBN0281
ABBN0526
BUILTIN
B11F01326
B11E03973
B11E00950
B11E00674
BUILTIN
B11E00775
B11E04461
B11E01074
B11E02821
BUILTIN
B11E04501
B11E00757
B11F01623
B11E01022
BUILTIN
B11E04359
B11E02751
B11E02736
B11E01178
ABBN6796
ABBN7259
BUILTIN
B11K01856
B11K01853
B11K01863
163363A02863
BUILTIN
163363A02668
163363A02881
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
533
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 13
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 14
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 15
CPU
PIC 0
Xcvr
Xcvr
534
2
3
REV 01
REV 01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
REV
REV
01
01
01
01
30
10
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
REV
REV
01
01
01
01
32
10
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
REV
REV
01
01
01
01
32
10
0
1
REV 01
REV 01
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
750-028467
711-029089
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
750-028467
711-029089
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-021310
740-021310
740-021310
740-021310
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-021308
750-028467
711-029089
BUILTIN
740-031980
740-031980
163363A01671
163363A02627
BUILTIN
163363A02725
163363A02692
163363A02730
163363A03081
BUILTIN
163363A02736
163363A02568
163363A02747
163363A02579
ABBN0270
ABBJ0966
BUILTIN
AK80NL1
AK80NXW
AK80KD2
AK80FMD
BUILTIN
AK80NKQ
AK80MGH
AK80N38
AK80NL7
BUILTIN
AK80LEL
AK80NKD
AK80KCY
AK80LHK
BUILTIN
AK80M5J
AK80MBE
AK80NLG
AK80LFH
ABBN6790
ABBK6515
BUILTIN
AK80LZM
AK80MCC
AK80KCM
AK80KE0
BUILTIN
C10F99155
C10F99049
C10F99128
C10F99169
BUILTIN
AK80LF3
163363A02597
163363A03060
163363A03057
BUILTIN
AK80LEX
AK80FEU
AK80FNM
AJQ0Q5G
ABBN6791
ABBN7289
BUILTIN
B11K00424
B11K01849
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-LRM
SFP+-10G-LRM
SFP+-10G-LRM
SFP+-10G-LRM
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 16
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 17
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
2
3
REV 01
REV 01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
REV
REV
01
01
01
01
30
10
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
REV
REV
01
01
01
01
32
10
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-030658
740-030658
740-030658
740-031980
750-028467
711-029089
BUILTIN
740-030658
740-030658
740-030658
740-030658
BUILTIN
740-030658
740-030658
740-030658
740-030658
BUILTIN
740-030658
740-030658
740-030658
740-030658
BUILTIN
740-030658
740-030658
740-030658
740-030658
750-028467
711-029089
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
B11K01862
B11K01852
BUILTIN
B11K00427
B11K00430
B11K01854
B11K00426
BUILTIN
B11K00429
B11K01864
B11K01850
B11K00522
BUILTIN
B11E01144
B11E00985
B11E00796
B11K01866
ABBM4592
ABBN0465
BUILTIN
B11F01435
B11E01052
B11F01328
B11F01254
BUILTIN
B11E02738
B11E02881
B11F01624
B11E00889
BUILTIN
B11E02883
B11E00681
B11E04306
B11E02813
BUILTIN
B11F01801
B11E02753
B11E01156
B11E04324
ABBN6810
ABBN7237
BUILTIN
163363A02638
163363A02082
163363A01674
163363A03058
BUILTIN
163363A03048
163363A02729
163363A02566
163363A02567
BUILTIN
163363A02878
163363A02739
163363A01959
163363A02660
BUILTIN
163363A02731
163363A02588
163363A02673
163363A02654
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
535
FPC 18
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 19
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
ADC 0
ADC 1
ADC 2
ADC 3
ADC 4
ADC 5
ADC 6
ADC 7
ADC 8
ADC 9
ADC 10
ADC 11
ADC 12
ADC 13
ADC 14
ADC 15
ADC 16
536
REV 30
REV 10
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
REV
REV
01
01
01
01
32
10
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
01
01
01
13
13
13
13
13
13
13
07
07
07
13
13
13
13
13
13
13
750-028467
711-029089
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031981
740-031981
740-031981
740-031981
750-028467
711-029089
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
ABBM4739
ABBN0487
BUILTIN
163363A02569
163363A02886
163363A03082
133363A00297
BUILTIN
163363A02726
163363A03050
163363A02884
163363A03076
BUILTIN
163363A02581
163363A02873
163363A02582
163363A03083
BUILTIN
UL70BU6
UL50QC6
UL708N6
UL603KK
ABBN6827
ABBK6508
BUILTIN
163363A01688
163363A01724
163363A01773
163363A02593
BUILTIN
163363A03061
163363A03056
163363A02669
163363A03070
BUILTIN
163363A02572
163363A02697
163363A02585
163363A03052
BUILTIN
163363A02591
163363A02649
163363A02577
163363A02698
ABBX5561
ABBX5546
ABBX5535
ABBX5552
ABBX5581
ABBX5545
ABBX5554
ABBV7194
ABBV7251
ABBV7202
ABBX5538
ABBX5566
ABBX5542
ABBX5539
ABBX5555
ABBX5557
ABBX5536
MPC 3D 16x 10GE

AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-LR
SFP+-10G-LR
SFP+-10G-LR
SFP+-10G-LR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
ADC
ADC
ADC
Fan
Fan
Fan
Fan

detail (MX2020
Router)
17
18
19
Tray
Tray
Tray
Tray
0
1
2
3
REV
REV
REV
REV
REV
REV
REV
13
13
11
2A
2A
2A
2A
750-043596
750-043596
750-043596
760-046960
760-046960
760-046960
760-046960
ABBX5559
ABBX5537
ABBW5685
ACAY0030
ACAY0039
ACAY0033
ACAY0062
Adapter Card
Adapter Card
Adapter Card
172mm FanTray
172mm FanTray
172mm FanTray
172mm FanTray
6
6
6
6
Fans
Fans
Fans
Fans

Hardware inventory:
Item
Description
Chassis
JN11E2227AFJ
MX2020
Midplane
REV 27
750-040240
ABAB9384
Midplane 1
REV 04
711-032386
ABAB9386
Upper Backplane
PMP 1
REV 05
711-032428
ACAJ1821
Upper Power Midplane
PMP 0
REV 04
711-032426
ACAJ1524
FPM Board
REV 06
760-040242
ABBT8837
Front Panel Display
PSM 0
REV 01
740-045050
1E02224006G
DC 52V Power Supply
Module
PSM 1
REV 01
740-045050
1E022240053
DC 52V Power Supply
Module
PSM 2
REV 01
740-045050
1E02224004K
DC 52V Power Supply
Module
PSM 3
REV 01
740-045050
1E022240056
DC 52V Power Supply
Module
PSM 4
REV 01
740-045050
1E022240054
DC 52V Power Supply
Module
PSM 5
REV 01
740-045050
1E02224005H
DC 52V Power Supply
Module
PSM 6
REV 01
740-045050
1E02224006S
DC 52V Power Supply
Module
PSM 7
REV 01
740-045050
1E02224005M
DC 52V Power Supply
Module
PSM 8
REV 01
740-045050
1E022240062
DC 52V Power Supply
Module
PSM 9
REV 03
740-045050
1EDB2350095
DC 52V Power Supply
Module
PSM 10
REV 03
740-045050
1EDB235009L
DC 52V Power Supply
Module
PSM 11
REV 03
740-045050
1EDB2350092
DC 52V Power Supply
Module
PSM 12
REV 03
740-045050
1EDB23500AT
DC 52V Power Supply
Module
PSM 13
REV 03
740-045050
1EDB2350094
DC 52V Power Supply
Module
PSM 15
REV 03
740-045050
1EDB235008X
DC 52V Power Supply
Module
PDM 0
REV 01
740-045234
1E012150033
PDM 1
REV 01
740-045234
1E012150027
PDM 2
REV 01
740-045234
1E262250072
740-041821
9009094138
RE-S-1800x4
ad0
3998 MB Virtium - TuffDisk VCF3 20110825A021D0000064 Compact Flash
ad1
UNIGEN-499551-000347 Disk 1
Intel
uhub0
vendor 0x8087
uhub1
DIMM 0
DIMM 1
DIMM 2
DIMM 3
740-041821
9009089709
RE-S-1800x4
ad0
537
ad1
30533 MB
CB 0
CB 1
SPMB 0
SPMB 1
SFB 0
SFB 1
SFB 2
SFB 3
SFB 4
SFB 5
SFB 6
SFB 7
FPC 0
CPU
PIC 0
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
REV
PIC 1
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
PIC 2
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
PIC 3
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
FPC 1
CPU
PIC 0
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
PIC 1
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
PIC 2
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
PIC 3
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
FPC 2
CPU
PIC 0
Xcvr 0
538
UGB94ARF32H0S3-KC
UNIGEN-478612-001044 Disk 1
REV 08
750-040257
CAAB3482
Control Board
REV 04
750-040257
ZT2864
Control Board
REV 02
711-041855
CAAA6141
PMB Board
REV 01
711-041855
ZS2275
PMB Board
REV 05
711-044466
ABBT2161
Switch Fabric Board
REV 05
711-044466
ABBT2159
Switch Fabric Board
REV 05
711-044466
ABBX3718
Switch Fabric Board
REV 05
711-044466
ABBT2152
Switch Fabric Board
REV 05
711-044466
ABBT2160
Switch Fabric Board
REV 05
711-044466
ABBT2145
Switch Fabric Board
REV 05
711-044466
ABBT2150
Switch Fabric Board
REV 05
711-044466
ABBT2163
Switch Fabric Board
REV 30
750-028467
ABBN0284
MPC 3D 16x 10GE
REV 10
711-029089
ABBN0507
AMPC PMB
BUILTIN
BUILTIN
4x 10GE(LAN) SFP+
REV 01
740-030658
B11E00990
SFP+-10G-USR
REV 01
740-030658
B11E04357
SFP+-10G-USR
REV 01
740-030658
B11F01327
SFP+-10G-USR
01
740-030658
B11E04375
SFP+-10G-USR
BUILTIN
BUILTIN
4x 10GE(LAN) SFP+
REV 01
740-030658
B11E02760
SFP+-10G-USR
REV 01
740-030658
B11E02904
SFP+-10G-USR
REV 01
740-030658
B11E03963
SFP+-10G-USR
REV 01
740-030658
B11E00756
SFP+-10G-USR
BUILTIN
BUILTIN
4x 10GE(LAN) SFP+
REV 01
740-030658
B11E04418
SFP+-10G-USR
REV 01
740-030658
B11E01077
SFP+-10G-USR
REV 01
740-030658
B11E01128
SFP+-10G-USR
REV 01
740-030658
B11F01253
SFP+-10G-USR
BUILTIN
BUILTIN
4x 10GE(LAN) SFP+
REV 01
740-030658
B11E01140
SFP+-10G-USR
REV 01
740-030658
B11F01626
SFP+-10G-USR
REV 01
740-030658
B11E01075
SFP+-10G-USR
REV 01
740-030658
B11E01177
SFP+-10G-USR
REV 30
750-028467
ABBN0308
MPC 3D 16x 10GE
REV 10
711-029089
ABBJ1095
AMPC PMB
BUILTIN
BUILTIN
4x 10GE(LAN) SFP+
REV 01
740-030658
B11E04305
SFP+-10G-USR
REV 01
740-030658
B11E01147
SFP+-10G-USR
REV 01
740-030658
B11E01195
SFP+-10G-USR
REV 01
740-030658
B11F01743
SFP+-10G-USR
BUILTIN
BUILTIN
4x 10GE(LAN) SFP+
REV 01
740-030658
B11F01892
SFP+-10G-USR
REV 01
740-030658
B11E02880
SFP+-10G-USR
REV 01
740-030658
B11E00725
SFP+-10G-USR
REV 01
740-030658
B11E01057
SFP+-10G-USR
BUILTIN
BUILTIN
4x 10GE(LAN) SFP+
REV 01
740-030658
B11E02816
SFP+-10G-USR
REV 01
740-030658
B11C04501
SFP+-10G-USR
REV 01
740-030658
B11E02764
SFP+-10G-USR
REV 01
740-030658
B11E00789
SFP+-10G-USR
BUILTIN
BUILTIN
4x 10GE(LAN) SFP+
REV 01
740-030658
B11F01250
SFP+-10G-USR
REV 01
740-030658
B11E02847
SFP+-10G-USR
REV 01
740-030658
B11E00787
SFP+-10G-USR
REV 01
740-030658
B11E03803
SFP+-10G-USR
REV 30
750-028467
ABBN0316
MPC 3D 16x 10GE
REV 10
711-029089
ABBJ1082
AMPC PMB
BUILTIN
BUILTIN
4x 10GE(LAN) SFP+
REV 01
740-031980
B11K00523
SFP+-10G-SR
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr 0
Xcvr
Xcvr
Xcvr
FPC 3
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 4
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
1
2
3
REV 01
REV 01
REV 01
0
1
2
3
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
1
2
3
REV 01
REV
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
0
1
2
REV
REV
REV
740-031980
B11K01848
740-031980
B11K01865
740-031980
B11K00540
BUILTIN
BUILTIN
01
740-031980
B11K00422
01
740-031980
B11K00428
01
740-031980
B11K00423
01
740-031980
B11K01855
BUILTIN
BUILTIN
01
740-031980
B11K01847
01
740-031980
B11K00526
01
740-031980
B11K00529
01
740-031980
B11K00525
BUILTIN
BUILTIN
740-031980
B11K00425
01
740-031980
B11K00530
01
740-031980
B11K01851
01
740-031980
B11K00528
32
750-028467
ABBN6832
10
711-029089
ABBK6534
BUILTIN
BUILTIN
01
740-031980
AK80MB4
01
740-031980
AK80FQ6
01
740-031980
AK80N1F
01
740-031980
AK80NLQ
BUILTIN
BUILTIN
01
740-031980
AK80KDR
01
740-031980
AK80FGJ
01
740-031980
AK80N5G
01
740-031980
AK80KD8
BUILTIN
BUILTIN
01
740-031980
AK80LET
01
740-031980
AK80N1X
01
740-031980
AK80NRF
01
740-031980
AK80NL2
BUILTIN
BUILTIN
01
740-031980
AK80N3D
01
740-031980
AK80MRB
01
740-031980
AK80LEQ
01
740-031980
AK80LER
32
750-028467
ABBN6811
10
711-029089
ABBN7288
BUILTIN
BUILTIN
01
740-031980
AK80NK8
01
740-031980
AK80LJG
01
740-031980
AK80LBU
01
740-031980
AK80N21
BUILTIN
BUILTIN
01
740-031980
AK80LEU
01
740-031980
AK80NLM
01
740-031980
AK80NL6
01
740-031980
AK80LES
BUILTIN
BUILTIN
01
740-031980
AK80LEN
01
740-031980
AK80ME0
01
740-031980
AK80LMG
01
740-031980
AK80MM1
BUILTIN
BUILTIN
01
740-031980
AK80MG7
01
740-031980
AK80KF9
01
740-031980
AK80NRQ
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
539
Xcvr
FPC 5
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr 0
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 6
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 7
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
540
REV 01
REV 32
REV 10
740-031980
AK80NLE
750-028467
ABBN6791
711-029089
ABBN7289
BUILTIN
BUILTIN
01
740-031980
B11K00424
01
740-031980
B11K01849
01
740-031980
B11K01862
01
740-031980
B11K01852
BUILTIN
BUILTIN
740-031980
B11K00427
01
740-031980
B11K00430
01
740-031980
B11K01854
01
740-031980
B11K00426
BUILTIN
BUILTIN
01
740-031980
B11K00429
01
740-031980
B11K01864
01
740-031980
B11K01850
01
740-031980
B11K00522
BUILTIN
BUILTIN
01
740-030658
B11E01144
01
740-030658
B11E00985
01
740-030658
B11E00796
01
740-031980
B11K01866
30
750-028467
ABBM4592
10
711-029089
ABBN0465
BUILTIN
BUILTIN
01
740-030658
B11F01435
01
740-030658
B11E01052
01
740-030658
B11F01328
01
740-030658
B11F01254
BUILTIN
BUILTIN
01
740-030658
B11E02738
01
740-030658
B11E02881
01
740-030658
B11F01624
01
740-030658
B11E00889
BUILTIN
BUILTIN
01
740-030658
B11E02883
01
740-030658
B11E00681
01
740-030658
B11E04306
01
740-030658
B11E02813
BUILTIN
BUILTIN
01
740-030658
B11F01801
01
740-030658
B11E02753
01
740-030658
B11E01156
01
740-030658
B11E04324
32
750-028467
ABBN6810
10
711-029089
ABBN7237
BUILTIN
BUILTIN
01
740-031980
163363A03058
01
740-031980
163363A02082
01
740-031980
163363A01674
01
740-031980
163363A02638
BUILTIN
BUILTIN
01
740-031980
163363A03048
01
740-031980
163363A02729
01
740-031980
163363A02566
01
740-031980
163363A02567
BUILTIN
BUILTIN
01
740-031980
163363A02878
01
740-031980
163363A02739
01
740-031980
163363A01959
0
1
2
3
REV
REV
REV
REV
1
2
3
REV 01
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
0
1
2
REV
REV
REV
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr 2
Xcvr
FPC 8
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 9
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 10
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr 2
3
0
1
3
REV 01
REV
REV
REV 01
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
0
1
REV
REV
REV 01
740-031980
163363A02660
BUILTIN
BUILTIN
01
740-031980
163363A02731
01
740-031980
163363A02588
740-031980
163363A02673
01
740-031980
163363A02654
30
750-028467
ABBM4739
10
711-029089
ABBN0487
BUILTIN
BUILTIN
01
740-031980
163363A02569
01
740-031980
163363A02886
01
740-031980
163363A03082
01
740-031980
133363A00297
BUILTIN
BUILTIN
01
740-031980
163363A02726
01
740-031980
163363A03050
01
740-031980
163363A02884
01
740-031980
163363A03076
BUILTIN
BUILTIN
01
740-031980
163363A02581
01
740-031980
163363A02873
01
740-031980
163363A02582
01
740-031980
163363A03083
BUILTIN
BUILTIN
01
740-031981
UL70BU6
01
740-031981
UL50QC6
01
740-031981
UL708N6
01
740-031981
UL603KK
32
750-028467
ABBN6827
10
711-029089
ABBK6508
BUILTIN
BUILTIN
01
740-031980
163363A01688
01
740-031980
163363A01724
01
740-031980
163363A01773
01
740-031980
163363A02593
BUILTIN
BUILTIN
01
740-031980
163363A03061
01
740-031980
163363A03056
01
740-031980
163363A02669
01
740-031980
163363A03070
BUILTIN
BUILTIN
01
740-031980
163363A02572
01
740-031980
163363A02697
01
740-031980
163363A02585
01
740-031980
163363A03052
BUILTIN
BUILTIN
01
740-031980
163363A02591
01
740-031980
163363A02649
01
740-031980
163363A02577
01
740-031980
163363A02698
30
750-028467
ABBN0302
10
711-029089
ABBN0495
BUILTIN
BUILTIN
01
740-030658
B11F01581
01
740-030658
B11E01176
01
740-030658
B11F01251
01
740-030658
B11E02752
BUILTIN
BUILTIN
01
740-030658
B11E00786
01
740-030658
B11E01020
740-030658
B11E01023
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-LR
SFP+-10G-LR
SFP+-10G-LR
SFP+-10G-LR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
541
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 11
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 12
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 13
CPU
PIC 0
Xcvr
Xcvr
Xcvr
542
REV 01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
REV
REV
01
01
01
01
32
10
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
REV
REV
01
01
01
01
30
10
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
REV
REV
01
01
01
01
30
10
0
1
2
REV 01
REV 01
REV 01
740-030658
BUILTIN
740-030658
740-030658
740-030658
740-030658
BUILTIN
740-030658
740-030658
740-030658
740-031980
750-028467
711-029089
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-021310
740-021310
740-021310
740-021310
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-021308
750-028467
711-029089
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
750-028467
711-029089
BUILTIN
740-030658
740-030658
740-030658
B11E02819
BUILTIN
B11E02812
B11D04437
B11F01279
B11F01333
BUILTIN
B11E00978
B11E01018
B11F01784
AK80NKP
ABBN6790
ABBK6515
BUILTIN
AK80LZM
AK80MCC
AK80KCM
AK80KE0
BUILTIN
C10F99155
C10F99049
C10F99128
C10F99169
BUILTIN
AK80LF3
163363A02597
163363A03060
163363A03057
BUILTIN
AK80LEX
AK80FEU
AK80FNM
AJQ0Q5G
ZM5111
ZP6607
BUILTIN
AK80LJA
AK80MFZ
AK80NKL
AK80KF4
BUILTIN
AK80FBJ
AK80MM2
AK80LJV
AK80NXV
BUILTIN
AK80N1H
AK80NLS
AK80FL5
AK80NL9
BUILTIN
AK80NG2
AK80KDU
AK80MG1
AK80MM0
ABBN0208
ABBJ1084
BUILTIN
B11E04745
B11F01570
B11E04388
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-LRM
SFP+-10G-LRM
SFP+-10G-LRM
SFP+-10G-LRM
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 14
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 15
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 16
REV 01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
REV
REV
01
01
01
01
23
10
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
REV
REV
01
01
01
01
32
10
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
REV
01
01
01
01
30
740-030658
BUILTIN
740-030658
740-030658
740-030658
740-030658
BUILTIN
740-030658
740-030658
740-030658
740-030658
BUILTIN
740-030658
740-030658
740-030658
740-030658
750-028467
711-029089
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
750-028467
711-029089
BUILTIN
740-021308
740-031980
740-021308
740-021308
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
750-028467
B11F01439
BUILTIN
B11E04739
B11F01869
B11F01675
B11F01901
BUILTIN
B11F01346
B11F01288
B11F01824
B11E04312
BUILTIN
B11E02811
B11E03847
B11F01495
B11F01265
YN2977
YP1856
BUILTIN
183363A00875
183363A00851
183363A00772
183363A00882
BUILTIN
183363A00735
183363A00169
183363A00726
183363A00077
BUILTIN
183363A00168
183363A00676
183363A00732
183363A00091
BUILTIN
183363A00725
183363A00642
183363A00871
183363A00853
ABBN6798
ABBK6556
BUILTIN
9ZDZ06A00055
183363A00239
AD0915E003K
AD0915E003A
BUILTIN
AK80MRC
AK80NL5
AK80NKN
AK80N3U
BUILTIN
AK80N1T
AJ808DJ
AK80NG4
AK80FND
BUILTIN
AK80FKQ
AK80NLT
AK80NKR
AK80LKM
ABBN0270
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC 3D 16x 10GE
543
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 17
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 18
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
544
REV 10
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
REV
REV
01
01
01
01
32
10
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
REV
REV
01
01
01
01
30
10
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
711-029089
ABBJ0966
BUILTIN
BUILTIN
740-031980
AK80NL1
740-031980
AK80NXW
740-031980
AK80KD2
740-031980
AK80FMD
BUILTIN
BUILTIN
740-031980
AK80NKQ
740-031980
AK80MGH
740-031980
AK80N38
740-031980
AK80NL7
BUILTIN
BUILTIN
740-031980
AK80M5J
740-031980
AK80NKD
740-031980
AK80KCY
740-031980
AK80LHK
BUILTIN
BUILTIN
740-031980
AK80LEL
740-031980
AK80MBE
740-031980
AK80NLG
740-031980
AK80LFH
750-028467
ABBN6796
711-029089
ABBN7259
BUILTIN
BUILTIN
740-031980
B11K01856
740-031980
B11K01853
740-031980
B11K01863
740-031980
163363A02863
BUILTIN
BUILTIN
740-031980
163363A02668
740-031980
163363A02881
740-031980
163363A01671
740-031980
163363A02627
BUILTIN
BUILTIN
740-031980
163363A02725
740-031980
163363A02692
740-031980
163363A02730
740-031980
163363A03081
BUILTIN
BUILTIN
740-031980
163363A02736
740-031980
163363A02568
740-031980
163363A02747
740-031980
163363A02579
750-028467
ABBN0281
711-029089
ABBN0526
BUILTIN
BUILTIN
740-030658
B11F01326
740-030658
B11E03973
740-030658
B11E00950
740-030658
B11E00674
BUILTIN
BUILTIN
740-030658
B11E00775
740-030658
B11E04461
740-030658
B11E01074
740-030658
B11E02821
BUILTIN
BUILTIN
740-030658
B11E04501
740-030658
B11E00757
740-030658
B11F01623
740-030658
B11E01022
BUILTIN
BUILTIN
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
Xcvr
Xcvr
Xcvr
Xcvr
FPC 19
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
ADC 0
ADC 1
ADC 2
ADC 3
ADC 4
ADC 5
ADC 6
ADC 7
ADC 8
ADC 9
ADC 10
ADC 11
ADC 12
ADC 13
ADC 14
ADC 15
ADC 16
ADC 17
ADC 18
ADC 19
Fan Tray
Fan Tray
Fan Tray
Fan Tray

models (MX2020
Router)
0
1
2
3
REV
REV
REV
REV
REV
REV
01
01
01
01
32
10
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
01
01
01
13
13
13
13
13
13
13
07
07
07
13
13
13
13
13
13
13
13
13
11
04
04
04
04
0
1
2
3
740-030658
740-030658
740-030658
740-030658
750-028467
711-029089
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-021308
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
760-046960
760-046960
760-046960
760-046960
user@host > show chassis hardware models

Hardware inventory:
Item
Version Part number
Midplane
REV 27
750-040240
FPM Board
REV 06
760-040242
PSM 0
REV 01
740-045050
PSM 1
REV 01
740-045050
PSM 2
REV 01
740-045050
PSM 3
REV 01
740-045050
PSM 4
REV 01
740-045050
B11E04359
B11E02751
B11E02736
B11E01178
ABBN6813
ABBK6542
BUILTIN
AK80NA3
AK80NLF
AK80MRH
AK80KE4
BUILTIN
973152A00030
AK80L9H
AK80ME8
AK80NLR
BUILTIN
AK80NG1
AK80MCA
AK80LFC
AK80LEM
BUILTIN
AK80N9X
AK80LAC
AK80LF2
AK80N8T
ABBX5561
ABBX5546
ABBX5535
ABBX5552
ABBX5581
ABBX5545
ABBX5554
ABBV7194
ABBV7251
ABBV7202
ABBX5579
ABBX5548
ABBX5575
ABBX5539
ABBX5555
ABBX5557
ABBX5536
ABBX5559
ABBX5537
ABBW5685
ACAY0090
ACAY0088
ACAY0089
ACAY0108
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
172mm FanTray - 6
172mm FanTray - 6
172mm FanTray - 6
172mm FanTray - 6
Serial number
ABAB9384
ABBT8837
1E02224006G
1E022240053
1E02224004K
1E022240056
1E022240054
FRU model number

750-040240
760-040242
MX2000-PSM-HC-DC-S-A
Fans
Fans
Fans
Fans
545
PSM 5
REV 01
PSM 6
REV 01
PSM 7
REV 01
PSM 8
REV 01
PSM 9
REV 03
PSM 10
REV 03
PSM 11
REV 03
PSM 12
REV 03
PSM 13
REV 03
PSM 15
REV 03
PDM 0
REV 01
PDM 1
REV 01
PDM 2
REV 01
CB 0
REV 08
CB 1
REV 04
SFB 0
REV 05
SFB 1
REV 05
SFB 2
REV 05
SFB 4
REV 05
SFB 5
REV 05
SFB 7
REV 05
FPC 0
REV 30
FPC 1
REV 30
FPC 2
REV 30
FPC 3
REV 32
FPC 4
REV 32
FPC 5
REV 32
FPC 6
REV 30
FPC 7
REV 32
FPC 8
REV 30
FPC 9
REV 32
FPC 10
REV 30
FPC 11
REV 32
FPC 12
REV 30
FPC 13
REV 30
FPC 14
REV 23
FPC 15
REV 32
FPC 16
REV 30
FPC 17
REV 32
FPC 18
REV 30
FPC 19
REV 32
ADC 0
REV 13
ADC 1
REV 13
ADC 2
REV 13
ADC 3
REV 13
ADC 4
REV 13
ADC 5
REV 13
ADC 6
REV 13
ADC 7
REV 07
ADC 8
REV 07
ADC 9
REV 07
ADC 10
REV 13
ADC 12
REV 13
ADC 13
REV 13
ADC 14
REV 13
ADC 15
REV 13
ADC 16
REV 13
ADC 17
REV 13
ADC 18
REV 13
546
740-045050
740-045050
740-045050
740-045050
740-045050
740-045050
740-045050
740-045050
740-045050
740-045050
740-045234
740-045234
740-045234
740-041821
740-041821
750-040257
750-040257
711-044466
711-044466
711-044466
711-044466
711-044466
711-044466
750-028467
750-028467
750-028467
750-028467
750-028467
750-028467
750-028467
750-028467
750-028467
750-028467
750-028467
750-028467
750-028467
750-028467
750-028467
750-028467
750-028467
750-028467
750-028467
750-028467
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
1E02224005H
1E02224006S
1E02224005M
1E022240062
1EDB2350095
1EDB235009L
1EDB2350092
1EDB23500AT
1EDB2350094
1EDB235008X
1E012150033
1E012150027
1E262250072
9009094138
9009089709
CAAB3482
ZT2864
ABBT2161
ABBT2159
ABBX3718
ABBT2160
ABBT2145
ABBT2163
ABBN0284
ABBN0308
ABBN0316
ABBN6832
ABBN6811
ABBN6791
ABBM4592
ABBN6810
ABBM4739
ABBN6827
ABBN0302
ABBN6790
ZM5111
ABBN0208
YN2977
ABBN6798
ABBN0270
ABBN6796
ABBN0281
ABBN6813
ABBX5561
ABBX5546
ABBX5535
ABBX5552
ABBX5581
ABBX5545
ABBX5554
ABBV7194
ABBV7251
ABBV7202
ABBX5579
ABBX5575
ABBX5539
ABBX5555
ABBX5557
ABBX5536
ABBX5559
ABBX5537
MX2000-PSM-DC-S-A
MX2000-PSM-DC-S-A
MX2000-PSM-DC-S-A
MX2000-PSM-DC-S-A
MX2000-PSM-DC-S-A
MX2000-PSM-DC-S-A
MX2000-PDM-DC-S-A
RE-S-1800X4-16G-S
RE-S-1800X4-16G-S
750-040257
750-040257
MX2000-SFB-S
MX2000-SFB-S
MX2000-SFB-S
MX2000-SFB-S
MX2000-SFB-S
MX2000-SFB-S
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
PROTO-ASSEMBLY
PROTO-ASSEMBLY
MX2000-LC-ADAPTER
MX2000-LC-ADAPTER
MX2000-LC-ADAPTER
PROTO-ASSEMBLY
PROTO-ASSEMBLY
MX2000-LC-ADAPTER
MX2000-LC-ADAPTER
MX2000-LC-ADAPTER
MX2000-LC-ADAPTER
MX2000-LC-ADAPTER
PROTO-ASSEMBLY
PROTO-ASSEMBLY
MX2000-LC-ADAPTER
PROTO-ASSEMBLY
PROTO-ASSEMBLY
PROTO-ASSEMBLY
ADC
Fan
Fan
Fan
Fan

clei-models (MX2020
Router)
19
Tray
Tray
Tray
Tray
0
1
2
3
REV
REV
REV
REV
REV
11
04
04
04
04
750-043596
760-046960
760-046960
760-046960
760-046960
ABBW5685
ACAY0090
ACAY0088
ACAY0089
ACAY0108
user@ host > show chassis hardware clei-models

Hardware inventory:
Item
Midplane
REV 27
750-040240
PROTOXCLEI
FPM Board
REV 06
760-040242
PROTOXCLEI
PSM 0
REV 01
740-045050
IPUPAJMKAA
PSM 1
REV 01
740-045050
IPUPAJMKAA
PSM 2
REV 01
740-045050
IPUPAJMKAA
PSM 3
REV 01
740-045050
IPUPAJMKAA
PSM 4
REV 01
740-045050
IPUPAJMKAA
PSM 5
REV 01
740-045050
IPUPAJMKAA
PSM 6
REV 01
740-045050
IPUPAJMKAA
PSM 7
REV 01
740-045050
IPUPAJMKAA
PSM 8
REV 01
740-045050
IPUPAJMKAA
PSM 9
REV 03
740-045050
IPUPAJMKAA
PSM 10
REV 03
740-045050
IPUPAJMKAA
PSM 11
REV 03
740-045050
IPUPAJMKAA
PSM 12
REV 03
740-045050
IPUPAJMKAA
PSM 13
REV 03
740-045050
IPUPAJMKAA
PSM 15
REV 03
740-045050
IPUPAJMKAA
PDM 0
REV 01
740-045234
PDM 1
REV 01
740-045234
PDM 2
REV 01
740-045234
IPUPAJSKAA
740-041821
740-041821
CB 0
REV 08
750-040257
PROTOXCLEI
CB 1
REV 04
750-040257
PROTOXCLEI
SFB 0
REV 05
711-044466
IPUCBA6CAA
SFB 1
REV 05
711-044466
IPUCBA6CAA
SFB 2
REV 05
711-044466
IPUCBA6CAA
SFB 4
REV 05
711-044466
IPUCBA6CAA
SFB 5
REV 05
711-044466
IPUCBA6CAA
SFB 7
REV 05
711-044466
IPUCBA6CAA
FPC 0
REV 30
750-028467
FPC 1
REV 30
750-028467
FPC 2
REV 30
750-028467
FPC 3
REV 32
750-028467
FPC 4
REV 32
750-028467
FPC 5
REV 32
750-028467
FPC 6
REV 30
750-028467
FPC 7
REV 32
750-028467
FPC 8
REV 30
750-028467
FPC 9
REV 32
750-028467
FPC 10
REV 30
750-028467
FPC 11
REV 32
750-028467
FPC 12
REV 30
750-028467
FPC 13
REV 30
750-028467
FPC 14
REV 23
750-028467
FPC 15
REV 32
750-028467
FPC 16
REV 30
750-028467
FPC 17
REV 32
750-028467
FPC 18
REV 30
750-028467
FPC 19
REV 32
750-028467
ADC 0
REV 13
750-043596
PROTOXCLEI
ADC 1
REV 13
750-043596
PROTOXCLEI
PROTO-ASSEMBLY
FRU model number

750-040240
760-040242
MX2000-PSM-DC-S-A
MX2000-PSM-DC-S-A
MX2000-PSM-DC-S-A
MX2000-PSM-DC-S-A
MX2000-PSM-DC-S-A
MX2000-PSM-DC-S-A
MX2000-PDM-DC-S-A
RE-S-1800X4-16G-S
RE-S-1800X4-16G-S
750-040257
750-040257
MX2000-SFB-S
MX2000-SFB-S
MX2000-SFB-S
MX2000-SFB-S
MX2000-SFB-S
MX2000-SFB-S
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
PROTO-ASSEMBLY
PROTO-ASSEMBLY
547
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
Fan
Fan
Fan
Fan

(MX Series routers with
ATM MIC)
2
3
4
5
6
7
8
9
10
12
13
14
15
16
17
18
19
Tray
Tray
Tray
Tray
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
0
1
2
3
13
13
13
13
13
07
07
07
13
13
13
13
13
13
13
13
11
04
04
04
04
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
760-046960
760-046960
760-046960
760-046960

Hardware inventory:
Item
Version Part number
Chassis
Midplane
REV 07
760-021404
FPM Board
REV 03
760-021392
PEM 0
Rev 01
740-022697
AC in
PEM 1
Rev 01
740-022697
AC in
PEM 2
Rev 01
740-022697
AC in
PEM 3
Rev 01
740-022697
AC in
740-013063
740-013063
CB 0
REV 06
710-021523
CB 1
REV 06
710-021523
FPC 2
REV 14
750-031088
YH8446
CPU
REV 06
711-030884
MIC 0
MIC 1
REV 10
750-036132
PIC 2
BUILTIN
Xcvr 0
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
QXM 0
QXM 1
Fan Tray 0
1
2
3
4
5
6
7
REV
REV
REV
REV
REV
REV
REV
IPUCBA8CAA
IPUCBA8CAA
IPUCBA8CAA
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
IPUCBA8CAA
IPUCBA8CAA
PROTOXCLEI
PROTOXCLEI
IPUCBA8CAA
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
MX2000-LC-ADAPTER
MX2000-LC-ADAPTER
MX2000-LC-ADAPTER
PROTO-ASSEMBLY
PROTO-ASSEMBLY
MX2000-LC-ADAPTER
MX2000-LC-ADAPTER
MX2000-LC-ADAPTER
MX2000-LC-ADAPTER
MX2000-LC-ADAPTER
PROTO-ASSEMBLY
PROTO-ASSEMBLY
MX2000-LC-ADAPTER
PROTO-ASSEMBLY
PROTO-ASSEMBLY
PROTO-ASSEMBLY
PROTO-ASSEMBLY
Serial number
JN115736EAFC
ABAA5038
ABBA2758
QCS0937C07K
Description
MX240
MX240 Backplane
Front Panel Display
PS 1.2-1.7kW; 100-240V
QCS0939C04X
PS 1.2-1.7kW; 100-240V
QCS0937C06B
PS 1.2-1.7kW; 100-240V
QCS0937C07U
PS 1.2-1.7kW; 100-240V
9009042291
9009042266
ABBC1435
ABBC1497
RE-S-2000
RE-S-2000
MX SCB
MX SCB
MPC Type 2 3D Q
MPC PMB 2G
YH9612
ZP7062
BUILTIN
2xOC12/8xOC3 CC-CE
2xOC12/8xOC3 CC-CE
NON-JNPR
23393-00492
NON-JNPR
23393-00500
NON-JNPR
23393-00912
01
740-015638
22216-00575
01
740-015638
24145-00110
01
740-015638
24145-00016
01
740-015638
24145-00175
NON-JNPR
23393-00627
05
711-028408
YF4681
05
711-028408
YF4817
01
710-021113
XL3645
UNKNOWN
UNKNOWN
UNKNOWN
Load SFP
Load SFP
Load SFP
Load SFP
UNKNOWN
MPC QXM
MPC QXM
MX240 Fan Tray
548
(MX240, MX480,
MX960 routers with
Modular Line Card)
user@host>show chassis hardware
Hardware inventory:
Item
Chassis
JN11D969BAFA
Midplane
REV 03
710-013698
ACAA2362
FPM Board
REV 03
710-014974
ZR0639
PDM
Rev 03
740-013110
QCS152250SX
PEM 0
Rev 10
740-013683
QCS1512718W
PEM 1
Rev 10
740-013683
QCS1512702Y
740-013063
9012024667
740-013063
9012024649
CB 0
REV 14
750-031391
ZJ7749
CB 1
REV 14
750-031391
ZJ7750
CB 2
REV 14
750-031391
ZY9233
FPC 0
REV 17
750-031089
YR7434
CPU
FPC 1
REV 11
750-037207
ZW9727
CPU
REV 04
711-038173
ZW4817
MIC 0
REV 01
750-037214
ZH3764
PIC 0
BUILTIN
BUILTIN
MIC 1
REV 01
711-028408
JZ9200
PIC 2
BUILTIN
BUILTIN
FPC 4
REV 30
750-028467
ABBN0232
CPU
FPC 5
REV 04
750-037207
ZK9074
CPU
Fan Tray 0
REV 05
740-014971
VT5683
Fan Tray 1
REV 05
740-014971
VT5684

extensive (MX240,
MX480, MX960
routers with
Description
MX960
MX960 Backplane
Front Panel Display
RE-S-2000
RE-S-2000
Enhanced MX SCB
Enhanced MX SCB
Enhanced MX SCB
MPC Type 2 3D
AS-MCC
AS-MCC-PMB
AS-MSC
AS-MSC
AS-MXC
AS-MXC
MPC 3D 16x 10GE
AS-MCC
Fan Tray
Fan Tray
user@host> show chassis hardware extensive

ID: AS-MCC
FRU Model Number: 750-037207
I2C Hex Data:
549
Modular Line Card)

(T320 Router)
550
Address 0x00: 7f b0 02 ff 0b 37 01 0b 52 45 56 20
Address 0x10: 00 00 00 00 37 35 30 2d 30 33 37 32
Address 0x20: 53 2f 4e 20 5a 57 39 37 32 37 00 00
Address 0x50: 35 30 2d 30 33 37 32 30 37 00 00 00
Address 0x60: 00 00 00 00 00 00 31 31 00 ff ff ff
Address 0x70: ff ff ff 5e ff ff ff ff ff ff ff ff
CPU
REV 04
711-038173
ZW4817
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
711-038173
S/N:
Assembly ID: 0x0b38
Assembly Version:
Date:
12-30-2011
Assembly Flags:
Version:
REV 04
ID: AS-MCC-PMB
Address 0x00: 7f b0 02 ff 0b 38 01 04 52 45 56 20
Address 0x10: 00 00 00 00 37 31 31 2d 30 33 38 31
Address 0x20: 53 2f 4e 20 5a 57 34 38 31 37 00 00
Address 0x30: db ff ff ff ff ff ff ff ff ff ff ff
Address 0x50: 31 31 2d 30 33 38 31 37 33 00 00 00
Address 0x60: 00 00 00 00 00 00 30 34 00 ff ff ff
Address 0x70: ff ff ff 60 00 00 00 00 00 00 00 00
MIC 0
REV 01
750-037214
ZH3764
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
750-037214
S/N:
Assembly ID: 0x0a44
Assembly Version:
Date:
07-04-2011
Assembly Flags:
Version:
REV 01
ID: AS-MSC
Address 0x00: 7f b0 02 ff 0a 44 01 01 52 45 56 20
Address 0x10: 00 00 00 00 37 35 30 2d 30 33 37 32
Address 0x20: 53 2f 4e 20 5a 48 33 37 36 34 00 00
Address 0x50: 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x60: 00 00 00 00 00 00 00 00 00 ff ff ff
Address 0x70: ff ff ff f6 c0 03 e1 bc 00 00 00 00
PIC 0
BUILTIN
BUILTIN
FPC 4
REV 30
750-028467
ABBN0232
Jedec Code:
0x7fb0
EEPROM Version:

Hardware inventory:
Item
Version Part number
Chassis
Midplane
REV 04
710-004339
FPM GBUS
REV 03
710-004461
FPM Display
REV 04
710-002897
CIP
REV 05
710-002895
PEM 0
Rev 01
740-004359
SCG 0
REV 06
710-004455
Clock Gen.
Routing Engine 0
CB 0
REV 13
710-002728
Control Board
CB 1
REV 13
710-002728
31
30
00
ff
4c
00
ff
ff
31
37
11
ff
45
00
ff
ff
00 00
00 00
02 07
ff ff
49 37
00 00
ff ff
ff ff
AS-MCC-PMB
0x02
S/N ZW4817
01.04
0x00
ff
30
37
00
ff
4c
00
ff
00
ff
34
33
1e
ff
45
00
ff
00
ff ff
00 00
00 00
0c 07
ff ff
49 37
00 00
ff ff
00 00
AS-MSC
I2C Hex Data:
0x02
S/N ZH3764
01.01
0x00
ff
30
31
00
ff
00
00
ff
00
ff
31
34
04
ff
00
00
ff
00
ff ff I2C Hex Data:

00 00
00 00
07 07
ff ff
00 00
00 00
ff ff
00 00
AS-MSC
MPC 3D 16x 10GE
0x01
Serial number
19093
BC1436
BC1407
BE0763
BB2311
NB12546
AY4522
Description
T320
T320 Backplane
T320 FPM Board
FPM Display
T Series CIP
Power Entry Module
T320 Sonet
BC1577
unknown
T Series
BC1595
T Series
Control Board
FPC 1
REV 09
710-007531
HS1572
CPU
REV 15
710-001726
HR8763
PIC 0
REV 01
750-010618
CB5579
1000 BASE
SFP 0
REV 01
740-007326
P5809Z1
SFP 1
REV 01
740-007326
P4Q10XU
SFP 2
NON-JNPR
RA45020031
SFP 3
NON-JNPR
RA45020032
PIC 1
REV 01
750-010618
CD9587
1000 BASE
SFP 0
NON-JNPR
P5A08QZ
SFP 1
REV 01
740-007326
P4Q133K
SFP 2
REV 01
740-007326
P5809YY
SFP 3
REV 01
740-007327
4C81704
MMB 1
REV 03
710-005555
HR9401
PPB 0
REV 04
710-003758
HR2886
FPC 2
REV 07
710-005860
HP2392
CPU
REV 14
710-001726
HP7797
PIC 0
REV 02
750-007643
HM0853
1000 BASE
SFP 0
REV 01
740-007326
P11E9JJ
MMB 1
REV 02
710-005555
HN2379
PPB 0
REV 04
710-003758
HP8092
FPC 3
REV 07
710-005860
HP2393
CPU
REV 14
710-001726
HP0968
PIC 0
REV 01
750-010240
CB5363
1000 BASE
SFP 0
REV 01
740-007326
P4R0PNH
PIC 1
REV 03
750-003034
HD2832
SMIR
MMB 1
REV 02
710-005555
HN6307
PPB 0
REV 04
710-003758
HP5051
FPC 4
REV 01
710-010845
JD3872
CPU
REV 02
710-011481
JB6042
5
REV 01
710-005802
BC1566
CPU
REV 09
710-001726
AY4922
PIC 0
REV 02
750-008155
BE2114
1000 BASE
SFP 0
REV 01
740-007326
P4R0PMQ
SFP 1
REV 01
740-007326
P4R0PN9
PIC 1
REV 01
750-008155
BE2116
1000 BASE
SFP 0
REV 01
740-007326
P4R0PNZ
SFP 1
NON-JNPR
2908
MMB 1
REV 01
710-005555
AZ2246
PPB 0
REV 03
710-003758
AY4839
FPC 7
REV 01
710-005803
AZ2123
...

(T640 Router)

Hardware inventory:
Item
Version Part number
Chassis
Midplane
REV 04
710-002726
FPM GBUS
REV 02
710-002901
FPM Display
REV 02
710-002897
CIP
REV 05
710-002895
PEM 0
Rev 02
740-029522
PEM 1
Rev 02
740-029522
SCG 0
REV 03
710-003423
Serial number
19182
AX5608
HE3064
HE7864
HA5024
VH26235
VH26230
HA4508
FPC Type 2
FPC CPU
4x G/E SFP,
SFP-SX
SFP-SX
SFP-SX
SFP-SX
4x G/E SFP,
SFP-T
SFP-SX
SFP-SX
SFP-LX
MMB-288mbit
PPB Type 2
FPC Type 1
FPC CPU
1x G/E QPP,
SFP-SX
MMB-288mbit
PPB Type 2
FPC Type 1
FPC CPU
1x G/E SFP,
SFP-SX
4x OC-3 SONET,
MMB-288mbit
PPB Type 2
FPC Type 4
FPC CPU
FPC Type 2
FPC CPU
2x G/E QPP,
SFP-SX
SFP-SX
2x G/E QPP,
SFP-SX
SFP-T
MMB-288mbit
PPB Type 2
FPC Type 3
Description
T640
T640 Backplane
T640 FPM Board
FPM Display
T Series CIP
AC PEM 10kW US
AC PEM 10kW US
T640 Sonet Clock Gen.
551

CB 0
REV 01
FPC 2
REV 04
CPU
REV 06
PIC 1
REV 03
SFP 0
REV 01
PIC 2
REV 03
SFP 0
REV 01
PIC 3
REV 03
SFP 0
REV 01
PIC 4
REV 03
SFP 0
REV 01
FPC 5
REV 01
CPU
REV 01
PIC 0
REV 01
SFP 0
REV 01
PIC 1
REV 03
SFP 0
REV 01
PIC 2
REV 03
SFP 0
PIC 3
REV 04
FPC 4
REV 01
CPU
REV 02
Fan Tray 0
Fan Tray 1
Fan Tray 2

models (T640 Router)

extensive (T640
Router)
552
740-005022
710-002728
710-001721
710-001726
750-009567
740-009898
750-009567
740-011268
750-009567
740-012056
750-009567
740-012058
710-013553
710-013569
750-009567
740-009898
750-009567
740-009550
750-009467
NON-JNPR
750-005100
710-010845
710-011481

Hardware inventory:
Item
Version Part number
Midplane
REV 04
710-002726
FPM Display
REV 02
710-002897
CIP
REV 05
710-002895
PEM 0
Rev 01
740-002595
SCG 0
REV 04
710-003423
SCG 1
REV 04
710-003423
740-005022
740-005022
CB 0
REV 06
710-002726
CB 1
REV 06
710-002728
FPC 5
REV 05
710-007527
PIC 0
REV 05
750-002510
PIC 1
REV 05
750-001901
FPC 6
REV 03
710-001721
PIC 1
REV 01
750-009553
SIB 4
REV 02
750-005486
Fan Tray 0
Fan Tray 1
Fan Tray 2
210865700483
HD3044
HD5572
HA4712
HV2331
USC202R103
HV2332
USC202R112
HX4416
434TC004
HX4420
434TC124
JE4839
JW9163
HX4419
USC202RT05
HN7426
03L90051
HT7423
AY4850
JD3872
JB6042
CLEI code
RE-3.0 (RE-600)
T Series Control Board
FPC Type 3
FPC CPU
1x 10GE(LAN),XENPAK
XENPAK-SR
1x 10GE(LAN),XENPAK
XENPAK-ZR
1x 10GE(LAN),XENPAK
XENPAK-CX4
1x 10GE(LAN),XENPAK
XENPAK-LX4
E2-FPC Type 1
FPC CPU
1x 10GE(LAN),XENPAK
XENPAK-LR
1x 10GE(LAN),XENPAK
XENPAK-ER
1x 10GE(LAN),XENPAK
UNKNOW0N
1x 10GE(LAN),DWDM
FPC Type 4
FPC CPU
Front Top Fan Tray
Rear Fan Tray
FRU model number

CHAS-BP-T640-S
CRAFT-T640-S
CIP-L-T640-S
PWR-T-DC-S
SCG-T-S
SCG-T-S
RE-600-2048-S
RE-600-2048-S
CHAS-BP-T640-S
CB-L-T-S
T640-FPC2
PB-2GE-SX
PB-4OC12-SON-SMIR
T640-FPC3
PC-4OC48-SON-SFP
SIB-I-T640-S
FANTRAY-T-S
FANTRAY-T-S
FAN-REAR-TX-T640-S

Hardware inventory:
Item
Description
Chassis
T640
Jedec Code:
0x7fb0
EEPROM Version:
0x01
P/N:
...........
S/N:
...........
Assembly ID: 0x0507
Date:
00-00-0000
Assembly Flags:
0x00
Version:
...........
ID: Gibson LCC Chassis

Address 0x00: 00 00 00 00 00 00 00 00 00 00 00 00
I2C Hex Data:
Address 0x00: 7f b0 01 ff 05 07 00 00 00 00 00 00
Address 0x10: 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x30: 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x40: 00 00 00 00 00 00 00 00 00 00 00 00
Midplane
REV 04
710-002726
AX5633
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
710-002726.
S/N:
Assembly ID: 0x0127
Assembly Version:
Date:
06-27-2001
Assembly Flags:
Version:
REV 04.....
ID: Gibson Backplane
Address 0x00: ad 01 08 00 00 90 69 0e f8 00 ff ff
I2C Hex Data:
Address 0x00: 7f b0 01 ff 01 27 01 04 52 45 56 20
Address 0x10: 00 00 00 00 37 31 30 2d 30 30 32 37
Address 0x20: 53 2f 4e 20 41 58 35 36 33 33 00 00
Address 0x30: d1 ff ff ff ad 01 08 00 00 90 69 0e
FPM GBUS
REV 02
710-002901
HE3245
...
FPM Display
REV 02
710-002897
HA4873
...
CIP
REV 05
710-002895
HA4729
...
PEM 1
RevX02
740-002595
MD21815
...
SCG 0
REV 04
710-003423
HF6023
...
SCG 1
REV 04
710-003423
HF6061
...
740-005022
210865700292
...
CB 0
REV 06
710-002728
HE3614
...
FPC 1
REV 01
710-002385
HE3009
...
REV 06
710-001726
HC0010

(T4000 Router)

Hardware inventory:
Item
Version Part number
Chassis
Midplane
REV 01
710-027486
FPM GBUS
REV 13
710-002901
FPM Display
REV 01
710-021387
CIP
REV 06
710-002895
PEM 0
REV 01
740-036442
SCG 0
REV 18
710-003423
SCG 1
REV 18
710-003423
740-026941
740-026941
CB 0
REV 09
710-022597
CB 1
REV 09
710-022597
FPC 0
REV 26
750-032819
CPU
REV 12
711-030686
PIC 0
REV 07
750-034624
Xcvr 0
REV 01
740-031980
00 00 00 00
00
00
00
00
00
00
00
00
00
00
00
00
00
00
00
00
00
00
00
00
0x01
S/N AX5633.
01.04
0x00
ff ff ff ff
Serial number
JN1172F25AHA
RC8355
BBAE0927
EF6764
BBAD9210
VA00016
BBAD7248
BBAE3874
P737F-002248
P737F-002653
ED0295
EA6050
EK1173
EJ8584
EF6837
123363A01145
30
32
00
f8
ff
34
36
1b
00
ff
00
00
06
ff
ff
00
00
07
ff
ff
Power Entry Module
RE-3.0
FPC Type 1
Description
T4000
T-series Backplane
T640 FPM Board
T1600 FPM Display
T-series CIP
Power Entry Module 6x60
RE-DUO-1800
RE-DUO-1800
LCC Control Board
LCC Control Board
FPC Type 5-3D
SNG PMB
12x10GE (LAN/WAN) SFPP
SFP+-10G-SR
553
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
LMB 0
LMB 1
LMB 2
FPC 3
CPU
PIC 0
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
LMB 0
LMB 1
LMB 2
FPC 5
CPU
PIC 0
PIC 1
Xcvr
BRIDGE
MMB 0
MMB 1
FPC 6
CPU
PIC 0
Xcvr
Xcvr
Xcvr
554
1
2
3
4
5
6
7
8
9
10
11
0
1
2
3
4
5
6
7
8
9
10
11
0
0
1
2
3
4
5
6
7
8
9
10
11
0
0
0
1
2
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
01
01
01
01
01
01
01
01
01
01
07
01
01
01
01
01
01
01
01
01
01
01
01
05
04
05
07
09
08
01
10
01
01
01
01
01
01
01
01
01
01
01
01
04
03
04
03
11
09
03
01
03
07
07
05
06
10
01
01
01
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
750-034624
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
711-034381
711-035774
711-034381
750-032819
711-030686
750-035293
740-032210
750-034624
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
711-034381
711-035774
711-034381
710-033871
710-016744
750-029262
750-034781
740-032210
711-029995
710-025563
710-025563
750-010153
711-030686
750-034624
740-031980
740-031980
740-031980
123363A01147
AJJ01P3
B10M03256
AJJ01M2
123363A01137
AJJ01PN
AJJ01NW
123363A01139
AJJ01KE
123363A01336
B10M01325
EF6800
AJJ01SA
AJJ01QZ
AJH0217
AJJ01TE
AJJ01KV
AJJ01MU
AJJ01R0
AJJ01TC
AJJ0364
AJD0GV3
B10M03343
AJJ01QJ
EJ8490
EJ8517
EJ8489
EG3637
EG0150
EF3657
C22CQNJ
BBAN4098
B11J04902
B11J04891
AJJ01MX
B11J04183
B11J04894
B11J04184
B11J04897
B11J04899
AJJ01TV
B11J04057
AJJ01M4
B11J04905
EG1524
EG0345
EG1522
BBAJ0768
BBAH9342
EE6789
EE6655
J11A22334
EE6572
BBAJ4657
BBAJ3073
EF4936
EF4189
BBAN4109
B11J04895
B11J04898
B11J04021
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
Type-0 LMB
Type-1 LMB
Type-0 LMB
FPC Type 5-3D
SNG PMB
1x100GE
CFP-100G-LR4
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
Type-0 LMB
Type-1 LMB
Type-0 LMB
FPC Type 4-ES
ST-PMB2
100GE
100GE CFP
CFP-100G-LR4
100GE Bridge Board
ST-MMB2
ST-MMB2
FPC Type 5-3D
SNG PMB
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
LMB 0
LMB 1
LMB 2
SPMB 0
SPMB 1
SIB 0
SIB 1
SIB 2
SIB 3
SIB 4
Fan Tray
Fan Tray
-- Rev 2
Fan Tray

(T4000 Router with 16
3
4
5
6
7
8
9
10
11
0
1
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
Type-0 LMB
Type-1 LMB
Type-0 LMB
LCC Switch CPU
LCC Switch CPU
SIB-HC-3D
SIB-HC-3D
SIB-HC-3D
SIB-HC-3D
SIB-HC-3D
Front Top Fan Tray
Rear Fan Tray -- Rev 3
0
1
2
3
4
5
6
7
8
9
10
11
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
01
01
01
01
01
01
01
01
02
01
01
01
01
01
01
01
01
01
01
01
01
04
03
04
05
05
02
07
07
02
02
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
750-034624
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
711-034381
711-035774
711-034381
710-023321
710-023321
711-036340
711-036340
711-036340
711-036340
711-036340

Hardware inventory:
Item
Version Part number
B11J04903
B11J04311
B11J04059
B11J04016
B11J04017
B11J04887
B11J04297
B11J04893
B11J04022
EE3711
AJH033X
AJJ01N0
AJJ01SV
AJJ032L
B10M01593
AJD0FF1
AJJ01NU
123363A01305
B10M00361
AJJ01M7
AJJ032X
AJJ01PG
EF3838
EF3821
EF3834
ED1990
EA2768
EF8802
EG2286
EG2252
EF1358
EF8806
Serial number
Description
555
GB line card chassis

(LCC) Routing Engine)
Chassis
Midplane
REV 01
FPM GBUS
REV 13
FPM Display
REV 04
CIP
REV 06
PEM 0
Rev 03
PEM 1
Rev 03
SCG 0
REV 18
SCG 1
REV 18
CB 1
REV 11
CB 1
REV 11
FPC 0
REV 05
CPU
REV 11
PIC 0
REV 20
PIC 1
REV 17
MMB 0
REV 07
MMB 1
REV 07
FPC 1
REV 05
CPU
REV 11
PIC 0
REV 17
MMB 0
REV 07
MMB 1
REV 07
SPMB 1
REV 05
SIB 0
REV 11
SIB 1
REV 11
SIB 2
REV 11
SIB 3
REV 11
SIB 4
REV 11
Fan Tray 0
Fan Tray 1
Fan Tray 2

clei-models (T4000
Router)

Hardware inventory:
Item
Midplane
REV 01
710-027486
IPMJ700DRD
FPM Display
REV 01
710-021387
CIP
REV 06
710-002895
PEM 0
REV 01
740-036442
IPUPAG6KAA
SCG 0
REV 18
710-003423
SCG 1
REV 18
710-003423
740-026941
740-026941
CB 0
REV 09
710-022597
CB 1
REV 09
710-022597
FPC 3
PIC 0
REV 08
750-035293
XXXXXXXXBB
PIC 1
REV 10
750-034624
XXXXXXXXCC
FPC 5
REV 03
710-033871
IPUCAMBCTD
PIC 1
REV 03
750-034781
IPUIBKLMAA
FPC 6
PIC 0
REV 10
750-034624
XXXXXXXXCC
Fan Tray 0
Fan Tray 1
Fan Tray 2
556
710-027486
710-002901
710-021387
710-002895
740-026384
740-026384
710-003423
710-003423
740-042243
740-042243
710-022597
710-022597
710-033871
710-016744
750-017405
750-026962
710-025563
710-025563
710-033871
710-016744
750-026962
710-025563
710-025563
710-023321
710-013074
710-013074
710-013074
710-013074
710-013074
JN11BDF2CAHA
ACAJ0774
BBAL6812
BBAP2679
BBAP4758
XF86421
XF86429
BBAP1896
BBAN8659
737F-002238
737F-002403
EK4526
EK4527
EK5644
EK3428
EJ3041
EH7536
EK6039
EK6086
EK6583
EK3401
EJ8948
EK6202
EK6112
EK4900
EK5958
EK4606
EK5971
EK4609
EK4602
T1600
T640 Backplane
T640 FPM Board
T1600 FPM Display
T-series CIP
RE-DUO-1800-16G
RE-DUO-1800-16G
LCC Control Board
LCC Control Board
FPC Type 4-ES
ST-PMB2
ST-MMB2
ST-MMB2
FPC Type 4-ES
ST-PMB2
ST-MMB2
ST-MMB2
LCC Switch CPU
SIB-I8-SF
SIB-I8-SF
SIB-I8-SF
SIB-I8-SF
SIB-I8-SF
Front Top Fan Tray
FRU model number

CHAS-BP-T1600-S
CRAFT-T1600-S
CIP-L-T640-S
PWR-T-6-60-DC
SCG-T-S
SCG-T-S
RE-DUO-C1800-8G-S
RE-DUO-C1800-8G-S
CB-LCC-S
CB-LCC-S
PF-1CGE-CFP
PF-12XGE-SFPP
T1600-FPC4-ES
PD-1CE-CFP-FPC4
PF-12XGE-SFPP
FANTRAY-T-S
FANTRAY-T4000-S
FANTRAY-TXP-R-S

Hardware inventory:
detail (T4000 Router)
Item
Chassis
Midplane
FPM GBUS
FPM Display
CIP
PEM 0
SCG 0
SCG 1
Routing Engine 0
ad0
3823 MB
ad1
59690 MB
Routing Engine 1
ad0
3823 MB
ad1
62720 MB
CB 0
CB 1
FPC 0
CPU
PIC 0
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
Xcvr 4
Xcvr 5
Xcvr 6
Xcvr 7
Xcvr 8
Xcvr 9
Xcvr 10
Xcvr 11
PIC 1
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
Xcvr 4
Xcvr 5
Xcvr 6
Xcvr 7
Xcvr 8
Xcvr 9
Xcvr 10
Xcvr 11
LMB 0
LMB 1
LMB 2
FPC 3
CPU
PIC 0
Xcvr 0
PIC 1
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
Xcvr 4
Xcvr 5
Xcvr 6
Xcvr 7
Version
Part number
Serial number
Description
JN1172F25AHA
T4000
REV 01
710-027486
RC8355
T-series Backplane
REV 13
710-002901
BBAE0927
T640 FPM Board
REV 01
710-021387
EF6764
T1600 FPM Display
REV 06
710-002895
BBAD9210
T-series CIP
REV 01
740-036442
VA00016
REV 18
710-003423
BBAD7248
REV 18
710-003423
BBAE3874
REV 05
740-026941
P737F-002248
RE-DUO-1800
SMART CF
2009121602A661576157 Compact Flash
STEC MACH-8 SSD
STM000103FDB
Disk 1
REV 06
740-026941
P737F-002653
RE-DUO-1800
SMART CF
201011150153F52CF52C Compact Flash
SMART Lite SATA Drive 2010110900150A880A88 Disk 1
REV 09
710-022597
ED0295
LCC Control Board
REV 09
710-022597
EA6050
LCC Control Board
REV 26
750-032819
EK1173
FPC Type 5-3D
REV 12
711-030686
EJ8584
SNG PMB
REV 07
750-034624
EF6837
REV 01
740-031980
123363A01145
SFP+-10G-SR
REV 01
740-031980
123363A01147
SFP+-10G-SR
REV 01
740-031980
AJJ01P3
SFP+-10G-SR
REV 01
740-031980
B10M03256
SFP+-10G-SR
REV 01
740-031980
AJJ01M2
SFP+-10G-SR
REV 01
740-031980
123363A01137
SFP+-10G-SR
REV 01
740-031980
AJJ01PN
SFP+-10G-SR
REV 01
740-031980
AJJ01NW
SFP+-10G-SR
REV 01
740-031980
123363A01139
SFP+-10G-SR
REV 01
740-031980
AJJ01KE
SFP+-10G-SR
REV 01
740-031980
123363A01336
SFP+-10G-SR
REV 01
740-031980
B10M01325
SFP+-10G-SR
REV 07
750-034624
EF6800
REV 01
740-031980
AJJ01SA
SFP+-10G-SR
REV 01
740-031980
AJJ01QZ
SFP+-10G-SR
REV 01
740-031980
AJH0217
SFP+-10G-SR
REV 01
740-031980
AJJ01TE
SFP+-10G-SR
REV 01
740-031980
AJJ01KV
SFP+-10G-SR
REV 01
740-031980
AJJ01MU
SFP+-10G-SR
REV 01
740-031980
AJJ01R0
SFP+-10G-SR
REV 01
740-031980
AJJ01TC
SFP+-10G-SR
REV 01
740-031980
AJJ0364
SFP+-10G-SR
REV 01
740-031980
AJD0GV3
SFP+-10G-SR
REV 01
740-031980
B10M03343
SFP+-10G-SR
REV 01
740-031980
AJJ01QJ
SFP+-10G-SR
REV 05
711-034381
EJ8490
Type-0 LMB
REV 04
711-035774
EJ8517
Type-1 LMB
REV 05
711-034381
EJ8489
Type-0 LMB
REV 07
750-032819
EG3637
FPC Type 5-3D
REV 09
711-030686
EG0150
SNG PMB
REV 08
750-035293
EF3657
1x100GE
REV 01
740-032210
C22CQNJ
CFP-100G-LR4
REV 10
750-034624
BBAN4098
REV 01
740-031980
B11J04902
SFP+-10G-SR
REV 01
740-031980
B11J04891
SFP+-10G-SR
REV 01
740-031980
AJJ01MX
SFP+-10G-SR
REV 01
740-031980
B11J04183
SFP+-10G-SR
REV 01
740-031980
B11J04894
SFP+-10G-SR
REV 01
740-031980
B11J04184
SFP+-10G-SR
REV 01
740-031980
B11J04897
SFP+-10G-SR
REV 01
740-031980
B11J04899
SFP+-10G-SR
557
Xcvr
Xcvr
Xcvr
Xcvr
LMB 0
LMB 1
LMB 2
FPC 5
CPU
PIC 0
PIC 1
Xcvr
BRIDGE
MMB 0
MMB 1
FPC 6
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
LMB 0
LMB 1
LMB 2
SPMB 0
SPMB 1
SIB 0
SIB 1
SIB 2
SIB 3
SIB 4
Fan Tray
Fan Tray
-- Rev 2
Fan Tray

models (T4000
8
9
10
11
0
1
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
Type-0 LMB
Type-1 LMB
Type-0 LMB
FPC Type 4-ES
ST-PMB2
100GE
100GE CFP
CFP-100G-LR4
100GE Bridge Board
ST-MMB2
ST-MMB2
FPC Type 5-3D
SNG PMB
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
Type-0 LMB
Type-1 LMB
Type-0 LMB
LCC Switch CPU
LCC Switch CPU
SIB-HC-3D
SIB-HC-3D
SIB-HC-3D
SIB-HC-3D
SIB-HC-3D
Front Top Fan Tray
0
0
0
1
2
3
4
5
6
7
8
9
10
11
0
1
2
3
4
5
6
7
8
9
10
11
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
01
01
01
04
03
04
03
11
09
03
01
03
07
07
05
06
10
01
01
01
01
01
01
01
01
01
01
01
01
02
01
01
01
01
01
01
01
01
01
01
01
01
04
03
04
05
05
02
07
07
02
02
740-031980
740-031980
740-031980
740-031980
711-034381
711-035774
711-034381
710-033871
710-016744
750-029262
750-034781
740-032210
711-029995
710-025563
710-025563
750-010153
711-030686
750-034624
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
750-034624
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
711-034381
711-035774
711-034381
710-023321
710-023321
711-036340
711-036340
711-036340
711-036340
711-036340
AJJ01TV
B11J04057
AJJ01M4
B11J04905
EG1524
EG0345
EG1522
BBAJ0768
BBAH9342
EE6789
EE6655
J11A22334
EE6572
BBAJ4657
BBAJ3073
EF4936
EF4189
BBAN4109
B11J04895
B11J04898
B11J04021
B11J04903
B11J04311
B11J04059
B11J04016
B11J04017
B11J04887
B11J04297
B11J04893
B11J04022
EE3711
AJH033X
AJJ01N0
AJJ01SV
AJJ032L
B10M01593
AJD0FF1
AJJ01NU
123363A01305
B10M00361
AJJ01M7
AJJ032X
AJJ01PG
EF3838
EF3821
EF3834
ED1990
EA2768
EF8802
EG2286
EG2252
EF1358
EF8806

Hardware inventory:
558
Router)

lcc (TX Matrix Router)
Item
Version
Midplane
REV 01
FPM Display
REV 01
CIP
REV 06
PEM 0
REV 01
SCG 0
REV 18
SCG 1
REV 18
CB 0
REV 09
CB 1
REV 09
FPC 3
PIC 0
REV 08
PIC 1
REV 10
FPC 5
REV 03
PIC 1
REV 03
FPC 6
PIC 0
REV 10
Fan Tray 0
Fan Tray 1
Fan Tray 2
Part number
710-027486
710-021387
710-002895
740-036442
710-003423
710-003423
740-026941
740-026941
710-022597
710-022597
Serial number
RC8355
EF6764
BBAD9210
VA00016
BBAD7248
BBAE3874
P737F-002248
P737F-002653
ED0295
EA6050
FRU model number

CHAS-BP-T1600-S
CRAFT-T1600-S
CIP-L-T640-S
PWR-T-6-60-DC
SCG-T-S
SCG-T-S
RE-DUO-C1800-8G-S
RE-DUO-C1800-8G-S
CB-LCC-S
CB-LCC-S
750-035293
750-034624
710-033871
750-034781
EF3657
BBAN4098
BBAJ0768
EE6655
PF-1CGE-CFP
PF-12XGE-SFPP
T1600-FPC4-ES
PD-1CE-CFP-FPC4
750-034624
BBAN4109
PF-12XGE-SFPP
FANTRAY-T-S
FANTRAY-T4000-S
FAN-REAR-TXP-LCC
user@host> show chassis hardware lcc 0

lcc0-re0:
-------------------------------------------------------------------------Hardware inventory:
Item
Description
Chassis
65751
T640
Midplane
REV 03
710-005608
RA1408
T640 Backplane
FPM GBUS
REV 09
710-002901
RA2784
T640 FPM Board
FPM Display
REV 05
710-002897
RA2825
FPM Display
CIP
REV 06
710-002895
HT0684
T Series CIP
PEM 0
Rev 11
740-002595
PM18483
Power Entry Module
PEM 1
Rev 11
740-002595
qb13984
Power Entry Module
SCG 0
REV 11
710-003423
HT0022
740-005022
210865700363
RE-3.0 (RE-600)
CB 0
REV 03
710-007655
HW1195
Control Board (CB-T)
FPC 1
REV 05
710-007527
HM3245
FPC Type 2
CPU
REV 14
710-001726
HM1084
FPC CPU
PIC 0
REV 02
750-007218
AZ1112
2x OC-12 ATM2 IQ, SMIR
PIC 1
REV 02
750-007745
HG3462
4x OC-3 SONET, SMIR
PIC 2
REV 14
750-001901
BA5390
PIC 3
REV 09
750-008155
HS3012
SFP 0
NON-JNPR
P1186TY
SFP-S
SFP 1
REV 01
740-007326
P11WLTF
SFP-SX
MMB 1
REV 02
710-005555
HL7514
MMB-288mbit
PPB 0
REV 04
710-003758
HM4405
PPB Type 2
PPB 1
REV 04
710-003758
AV1960
PPB Type 2
FPC 2
REV 08
710-010154
HZ3578
E-FPC Type 3
CPU
REV 05
710-010169
HZ3219
FPC CPU-Enhanced
PIC 0
REV 02
750-009567
HX2882
1x 10GE(LAN),XENPAK
SFP 0
REV 01
740-009898
USC202U709
XENPAK-LR
PIC 1
REV 03
750-003336
HJ9954
PIC 2
REV 01
750-004535
HC0235
1x OC-192 SM SR1
PIC 3
REV 07
750-007141
HX1699
SFP 0
SFP 1
MMB 0
MMB 1
SPMB 0
REV
REV
REV
REV
REV
01
01
03
03
09
740-007326
740-007326
710-010171
710-010171
710-003229
2441042
2441027
HV2365
HZ3888
HW5245
SFP-SX
SFP-SX
MMB-5M3-288mbit
MMB-5M3-288mbit
T Series Switch CPU
559
SIB
B
SIB
B
3
Board
4
Board
REV
REV
REV
REV
07
06
07
06
710-005781
710-005782
710-005781
710-005782
HR5927
HR5971
HR5903
HZ5275
SIB-L8-F16
SIB-L8-F16 (B)
SIB-L8-F16
SIB-L8-F16 (B)

scc (TX Matrix Router)
user@host> show chassis hardware scc

scc-re0:
Item
Description
Chassis
TX Matrix
Midplane
REV 04
710-004396
RB0014
SCC Midplane
FPM GBUS
REV 04
710-004617
HW9141
SCC FPM Board
FPM Display
REV 04
710-004619
HS5950
SCC FPM
CIP 0
REV 01
710-010218
HV9151
SCC CIP
CIP 1
REV 01
710-010218
HV9152
SCC CIP
PEM 1
Rev 11
740-002595
QB13977
Power Entry Module
740-008883
P11123900153
RE-4.0 (RE-1600)
CB 0
REV 01
710-011709
HR5964
Control Board (CB-TX)
SPMB 0
REV 09
710-003229
HW5293
T Series Switch CPU
SIB 3
SIB 4
REV 01
710-005839
HW1177
SIB-S8-F16
B Board
REV 01
710-005840
HW1202
SIB-S8-F16 (B)

(T1600 Router)

Hardware inventory:
Item
Chassis
B2703
Midplane
REV 03
710-005608
RC4137
FPM GBUS
REV 10
710-002901
DT7062
FPM Display
REV 05
710-002897
DS3067
CIP
REV 06
710-002895
DT3386
PEM 0
Rev 07
740-017906
UA26344
PEM 1
Rev 18
740-002595
UF38441
SCG 0
REV 15
710-003423
DV0941
740-014082
9009014502
740-014082
9009009591
CB 0
REV 05
710-007655
JA9360
CB 1
REV 03
710-017707
DT3251
FPC 0
REV 07
710-013558
DR4253
CPU
REV 05
710-013563
DS3902
PIC 0
REV 01
750-010618
CB5446
Xcvr 0
REV 01
740-011613
P9F11CW
Xcvr 1
REV 01
740-011613
P9F15C2
Xcvr 2
REV 01
740-011782
PB94K0L
PIC 1
REV 06
750-001900
HB6399
PIC 2
REV 14
750-001901
AP1092
PIC 3
REV 07
750-001900
AR8275
MMB 1
REV 07
710-010171
DS1524
FPC 1
REV 06
710-013553
DL9067
CPU
REV 04
710-013563
DM1685
PIC 0
REV 08
750-001072
AB1688
PIC 1
REV 10
750-012266
JX5519
Xcvr 0
REV 01
740-011613
AM0812S8UK6
Xcvr 2
REV 01
740-011613
AM0812S8UK1
Xcvr 3
REV 01
740-011782
P8N1YHG
PIC 2
REV 22
750-005634
DP0083
MMB 1
FPC 2
560
REV 07
REV 01
710-008923
710-005548
DN1862
HJ9899
Description
T1600
T640 Backplane
T640 FPM Board
FPM Display
T-series CIP
Power Entry Module
RE-A-2000
RE-A-2000
E2-FPC Type 2
FPC CPU-Enhanced
SFP-SX
SFP-SX
SFP-SX
MMB-5M3-288mbit
E2-FPC Type 1
FPC CPU-Enhanced
4x 1GE(LAN), IQ2
SFP-SX
SFP-SX
SFP-SX
1x CHOC12 IQ SONET, SMIR
MMB 3M 288-bit
FPC Type 3
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
PIC 3
Xcvr
Xcvr
MMB 0
MMB 1
PPB 0
PPB 1
FPC 3
CPU
PIC 0
Xcvr
PIC 1
0
1
2
4
5
6
7
8
9
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
PIC 3
MMB 0
MMB 1
FPC 4
CPU
PIC 0
PIC 1
Xcvr
BRIDGE
MMB 0
MMB 1
FPC 5
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
MMB 0
0
1
2
4
5
0
1
2
4
5
6
7
0
1
REV 06
REV 16
710-001726
750-007141
HC0586
NC9660
FPC CPU
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
01
01
01
01
01
01
01
01
06
01
01
01
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
01
01
05
17
01
01
03
03
02
02
01
01
07
740-011613
740-011782
740-011613
740-011613
740-011613
740-011613
740-011613
740-011782
740-011613
750-015217
740-011782
740-013111
740-011613
NON-JNPR
740-011782
740-011613
740-011613
750-004695
750-009553
740-011785
740-011785
710-004047
710-004047
710-002845
710-002845
710-010154
710-010169
750-012793
NON-JNPR
750-007141
AM0812S8XAR
P920E7B
AM0812S8XAU
AM0812S8XAK
AM0812S8XAA
PAJ4NKY
AM0812S8UJW
PB81X89
AM0812S8UJX
DK3280
P8P0A3T
5090002
AM0814S93BQ
PDE0FAN
P8Q20XY
AM0812S8UJV
AM0812S8UP7
HT4383
RL0204
PDS3T23
P6Q0F3E
HD5843
HE3208
HA4524
HA4766
HR0863
HN3422
WF5096
M64294TP
DV2127
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
8x 1GE(TYPE3), IQ2
SFP-SX
SFP-T
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
1x Tunnel
4x OC-48 SONET
SFP-SR
SFP-SR
MMB-288mbit
MMB-288mbit
PPB Type 3
PPB Type 3
E-FPC Type 3
FPC CPU-Enhanced
1x 10GE(LAN/WAN) IQ2
XFP-10G-LR
740-011613
740-011782
740-011782
740-011782
NON-JNPR
750-009553
740-011785
750-003700
710-010171
710-010171
710-013037
710-016744
711-029996
711-029999
740-032210
711-029995
710-025563
710-025563
710-013037
710-016744
750-012518
740-014279
740-014279
740-014279
740-014279
750-010850
710-016036
PFA6LTJ
P9P0XV4
P9M0TNX
P9B0TTP
PBS4LED
RL0212
PDS3T8G
DL1279
HR0821
HR0818
EB4919
BBAA4382
EB1569
EB9983
J10G80746
EB2235
BBAA7112
BBAA7149
DE3407
DA2124
DF2554
AA0745N1FX8
AA0748N1HN5
AA0748N1HT6
AA0744N1EC9
JA0329
DE9577
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
4x OC-48 SONET
SFP-SR
1x OC-192 12xMM VSR
MMB-288mbit
MMB-288mbit
FPC Type 4-ES
ST-PMB2
100GE
100GE CFP
CFP-100G-LR4
100GE Bridge Board
ST-MMB2
ST-MMB2
FPC Type 4-ES
ST-PMB2
4x OC-192 SONET XFP
XFP-OC192-SR
XFP-OC192-SR
XFP-OC192-SR
XFP-OC192-SR
1x OC-768 SONET SR
ST-MMB2
0
REV 25
0
0
0
1
2
3
REV
REV
REV
REV
01
01
01
01
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
17
01
32
01
01
16
09
03
05
0
02
04
04
02
04
16
01
01
01
01
01
04
561
MMB 1
FPC 6
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
MMB 0
MMB 1
FPC 7
CPU
PIC 0
Xcvr
PIC 1
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
MMB 0
MMB 1
PPB 0
PPB 1
SPMB 0
SPMB 1
SIB 0
SIB 1
SIB 2
SIB 3
SIB 4
Fan Tray
Fan Tray
Fan Tray

(TX Matrix Plus
Router)
562
0
1
2
3
0
1
2
3
0
0
1
0
1
2
3
4
5
6
7
0
1
2
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
04
14
09
11
01
01
01
01
13
02
02
02
02
01
01
09
15
10
02
01
01
01
01
01
01
01
01
01
01
01
01
15
03
03
04
04
10
12
07
07
07
07
07
710-016036
710-013037
710-016744
750-017405
740-014289
740-014279
740-014289
740-014289
750-017405
740-011571
740-014289
740-014289
740-014289
710-025563
710-025563
710-007529
710-001726
750-012793
740-011571
750-015217
740-011782
740-011782
750-015217
740-011613
740-011613
740-011613
740-011613
740-011613
740-011782
740-011782
740-011613
750-009450
710-005555
710-005555
710-002845
710-002845
710-003229
710-003229
710-013074
710-013074
710-013074
710-013074
710-013074
DK4060
DV1431
DT9020
DM6261
C701XU05Q
AA0748N1HPT
T08E19189
C715XU058
DP8772
C850XJ037
C839XU0L9
C834XU05A
C810XU0CE
DT8454
DT8366
HZ7624
HZ1413
DM5627
C831XJ062
JT6762
P8Q25JU
P9B0U0K
JS4268
AM0812S8XBZ
AM0812S8XAP
AM0812S8XBY
AM0812S8XBX
P9F1652
P8Q21YC
P8Q27HQ
P8E2SSU
NB6790
HZ3450
HZ3415
HP0887
HW5255
HX3699
DT3091
DS4747
DS4942
DS4965
DS4990
DS4944
ST-MMB2
FPC Type 4-ES
ST-PMB2
XFP-10G-SR
XFP-10G-LR
XFP-10G-SR
XFP-10G-SR
XFP-10G-SR
XFP-10G-SR
XFP-10G-SR
XFP-10G-SR
ST-MMB2
ST-MMB2
FPC Type 3
FPC CPU
XFP-10G-SR
8x 1GE(TYPE3), IQ2
SFP-SX
SFP-SX
8x 1GE(TYPE3), IQ2
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
1x OC-192 SM SR2
MMB-288mbit
MMB-288mbit
PPB Type 3
PPB Type 3
T-series Switch CPU
T-series Switch CPU
SIB-I8-SF
SIB-I8-SF
SIB-I8-SF
SIB-I8-SF
SIB-I8-SF
Front Top Fan Tray

sfc0-re0:
Item
Description
Chassis
JN113186EAHB
TXP
Midplane
REV 05
710-022574
TS3822
SFC Midplane
FPM Display
REV 03
710-024027
DW4701
TXP FPM Display
CIP 0
REV 05
710-023792
DW7998
TXP CIP
CIP 1
REV 05
710-023792
DW7999
TXP CIP
PEM 0
Rev 04
740-027463
UM26367
Power Entry Module
PEM 1
Rev 04
740-027463
UM26346
Power Entry Module
740-026942
737A-1081
RE-DUO-2600
740-026942
737A-1043
RE-DUO-2600
CB 0
CB 1
SPMB 0
SPMB 1
SIB F13 0
B Board
SIB F13 3
B Board
SIB F13 6
SIB F13 8
B Board
SIB F13 11
B Board
SIB F13 12
B Board
SIB F2S 0/0
B Board
SIB F2S 0/2
B Board
SIB F2S 0/4
B Board
SIB F2S 0/6
B Board
SIB F2S 1/0
B Board
SIB F2S 1/2
B Board
SIB F2S 1/4
B Board
SIB F2S 1/6
B Board
SIB F2S 2/0
B Board
SIB F2S 2/2
B Board
SIB F2S 2/4
B Board
SIB F2S 2/6
B Board
SIB F2S 3/0
B Board
SIB F2S 3/2
B Board
SIB F2S 3/4
B Board
SIB F2S 3/6
B Board
SIB F2S 4/0
B Board
SIB F2S 4/2
B Board
SIB F2S 4/4
B Board
SIB F2S 4/6
B Board
Fan Tray 0
Fan Tray 1
Fan Tray 2
Fan Tray 3
Fan Tray 4
Fan Tray 5
REV 05
REV 09
REV
REV
REV
REV
04
03
04
03
710-022606
710-022606
BUILTIN
BUILTIN
750-024564
710-023431
750-024564
710-023431
DW4435
DW6100
DW5764
DW9053
DW5785
DW9030
SFC
SFC
SFC
SFC
F13
F13
F13
F13
Control Board
Control Board
Switch CPU
Switch CPU
SIB
SIB Mezz
SIB
SIB Mezz
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
04
03
04
03
03
02
05
05
05
05
04
05
04
05
04
05
05
05
04
05
05
05
04
05
04
05
05
05
04
05
05
05
03
03
05
05
03
03
03
03
05
05
04
05
03
03
02
02
05
750-024564
710-023431
750-024564
710-023431
750-024564
710-023431
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
760-024497
760-024497
760-024502
DW5752
DW9051
DW5782
DW9058
DT9466
DT6556
DW7898
DW7625
DW7811
DW7550
DW4873
DW8509
DW4867
DW8472
DW4871
DW8497
DW7868
DW7551
DW4854
DW8496
DW7889
DW7496
DW4852
DW8498
DW4845
DW8457
DW7802
DW7562
DW4822
DW8467
DW7815
DW7518
DV0068
DT9974
DW7874
DW7601
DV0033
DT9969
DV0043
DT9948
DW5446
DW7611
DW4826
DW8458
DV0026
DT9963
DR8290
DR8293
DR8280
F13 SIB
F13 SIB Mezz
F13 SIB
F13 SIB Mezz
F13 SIB
F13 SIB Mezz
F2S SIB
F2S SIB Mezz
F2S SIB
F2S SIB Mezz
F2S SIB
F2S SIB Mezz
F2S SIB
F2S SIB Mezz
F2S SIB
F2S SIB Mezz
F2S SIB
F2S SIB Mezz
F2S SIB
F2S SIB Mezz
F2S SIB
F2S SIB Mezz
F2S SIB
F2S SIB Mezz
F2S SIB
F2S SIB Mezz
F2S SIB
F2S SIB Mezz
F2S SIB
F2S SIB Mezz
F2S SIB
F2S SIB Mezz
F2S SIB
F2S SIB Mezz
F2S SIB
F2S SIB Mezz
F2S SIB
F2S SIB Mezz
F2S SIB
F2S SIB Mezz
F2S SIB
F2S SIB Mezz
F2S SIB
F2S SIB Mezz
F2S SIB
F2S SIB Mezz
Front Fan Tray
Front Fan Tray
Rear Fan Tray
REV 05
REV 02
760-024502
760-024502
DR8276
DP5643
Rear Fan Tray

Rear Fan Tray
563
lcc0-re0:
Item
Description
Chassis
JN11036F8AHA
T1600
Midplane
REV 03
710-017247
RC3799
T-series Backplane
FPM GBUS
REV 10
710-002901
DP7009
T640 FPM Board
FPM Display
REV 01
710-021387
DN7026
T1600 FPM Display
CIP
REV 06
710-002895
DP6024
T-series CIP
PEM 1
Rev 02
740-023211
WA50019
Power Entry Module 4x60A
SCG 0
REV 15
710-003423
DR6757
SCG 1
REV 15
710-003423
DS2225
740-026941
737F-1040
RE-DUO-1800
740-026941
737F-1016
RE-DUO-1800
CB 0
REV 06
710-022597
DX4011
LCC Control Board
CB 1
REV 06
710-022597
DX4017
LCC Control Board
FPC 1
REV 07
710-013035
DN5847
FPC Type 3-ES
CPU
REV 08
710-016744
DP2570
ST-PMB2
PIC 0
REV 05
750-015217
DB0418
8x 1GE(TYPE3), IQ2
Xcvr 0
REV 01
740-011782
P8Q27ZG
SFP-SX
Xcvr 1
NON-JNPR
PDA1U0D
SFP-SX
Xcvr 2
REV 01
740-011613
P9F1ALW
SFP-SX
Xcvr 3
REV 01
740-011782
PBA403V
SFP-SX
Xcvr 4
NON-JNPR
PDE09DP
SFP-SX
Xcvr 5
REV 01
740-011782
PCH2P4K
SFP-SX
Xcvr 6
REV 01
740-011782
PB94K0F
SFP-SX
Xcvr 7
REV 01
740-011782
PBA2R2A
SFP-SX
PIC 1
REV 03
750-004424
HJ4020
1x 10GE(LAN),DWDM
PIC 2
REV 01
750-003336
HG6073
MMB 0
REV 04
710-016036
DP3401
ST-MMB2
FPC 3
REV 12
710-013037
DR1169
FPC Type 4-ES
CPU
REV 08
710-016744
DP9429
ST-PMB2
PIC 0
REV 02
750-010850
JA0332
1x OC-768 SONET SR
MMB 0
REV 04
710-016036
DR0628
ST-MMB2
MMB 1
REV 04
710-016036
DR0592
ST-MMB2
FPC 4
REV 05
710-021534
DR7350
FPC Type 1-ES
CPU
REV 08
710-016744
DP8096
ST-PMB2
PIC 0
REV 04
750-014627
DP9171
Xcvr 0
REV 02
740-011615
PDE2RVR
SFP-SR
PIC 1
REV 22
750-005634
DS5815
1x CHOC12 IQ SONET, SMIR
564
PIC 2
PIC 3
Xcvr 0
MMB 0
FPC 5
CPU
PIC 0
Xcvr 0
PIC 1
REV
REV
REV
REV
REV
REV
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
MMB 0
MMB 1
PPB 0
REV
REV
REV
REV
REV
REV
REV
REV
REV
1
2
3
4
0
REV 09
REV 08
04
07
15
14
01
16
750-002911
750-021652
NON-JNPR
710-016036
710-007529
710-001726
750-009567
740-013170
750-007141
CF4539
DR2827
8
DR0809
HS5608
HX4351
WJ8961
J05K05961
JJ8146
4x F/E, 100 BASE-TX

1x CHOC12 IQE SONET
UNKNOWN
ST-MMB2
FPC Type 3
FPC CPU
1x 10GE(LAN),XENPAK
XENPAK-LR
01
01
01
01
12
02
03
03
04
740-011613
740-011782
740-011782
740-011613
750-009567
740-013170
710-005555
710-005555
710-002845
P9F117T
PBA2VCL
PB83DRB
AM0812S8UP8
WF3566
T07C94489
HZ1907
HW5283
HZ7717
SFP-SX
SFP-SX
SFP-SX
SFP-SX
1x 10GE(LAN),XENPAK
XENPAK-LR
MMB-288mbit
MMB-288mbit
PPB Type 3
PPB 1
FPC 6
CPU
PIC 0
Xcvr 0
PIC 1
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
Xcvr 4
Xcvr 5
Xcvr 6
Xcvr 7
PIC 2
Xcvr 0
Xcvr 1
Xcvr 6
Xcvr 7
MMB 0
FPC 7
CPU
PIC 0
PIC 1
PIC 2
Xcvr 0
Xcvr 1
PIC 3
Xcvr 0
MMB 0
SPMB 0
SPMB 1
SIB 0
B Board
SIB 1
B Board
SIB 2
SIB 3
B Board
SIB 4
B Board
Fan Tray 0
Fan Tray 1
Fan Tray 2
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
04
07
08
09
02
06
01
01
01
01
01
01
02
01
06
01
01
01
01
04
03
09
13
05
10
01
01
03
01
05
04
04
07
07
07
07
710-002845
710-013035
710-016744
750-009567
740-013170
750-015217
740-011782
740-011613
740-011782
740-011782
740-011782
740-011613
740-013111
740-011782
750-015217
740-011613
740-013111
740-011782
740-011613
710-016036
710-021540
710-016744
750-001901
750-001900
750-008155
740-011782
740-011782
750-014638
740-011785
710-016036
710-023321
710-023321
710-022594
710-023185
710-022594
710-023185
HS0110
DP7486
DP2545
NE6323
T09C71959
DN4775
P7E0T6M
AM0812S8XAY
P7E0T6J
PCH2P7D
P9B0QYT
AM0812S8WQJ
9301220
P9B0TZ5
DM6747
PAP0ZB2
70191002
PBA29H8
AM0812S8WQG
DP3238
DV3154
DT9053
HB4225
AD3644
HV0335
PCH2UKF
PCH2V19
JS9493
P6Q0ENK
DP3323
DX3004
DX3009
DW4195
DW3930
DW4179
DW3919
PPB Type 3
FPC Type 3-ES
ST-PMB2
1x 10GE(LAN),XENPAK
XENPAK-LR
8x 1GE(TYPE3), IQ2
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-T
SFP-SX
8x 1GE(TYPE3), IQ2
SFP-SX
SFP-T
SFP-SX
SFP-SX
ST-MMB2
FPC Type 2-ES
ST-PMB2
SFP-SX
SFP-SX
1x OC-48-12-3 SFP
SFP-SR
ST-MMB2
LCC Switch CPU
LCC Switch CPU
LCC SIB
LCC SIB Mezz
LCC SIB
LCC SIB Mezz
REV
REV
REV
REV
06
06
08
07
710-022594
710-023185
710-022594
710-023185
DT8251
DT5792
DW8014
DW3917
LCC SIB
LCC SIB Mezz
LCC SIB
LCC SIB Mezz
Front Top Fan Tray
lcc1-re0:
Item
Description
Chassis
JN1102270AHA
T1600
Midplane
REV 04
710-017247
RC5358
T-series Backplane
FPM GBUS
REV 10
710-002901
DS3443
T640 FPM Board
FPM Display
REV 01
710-021387
DS6411
T1600 FPM Display
CIP
REV 06
710-002895
DS4235
T-series CIP
PEM 0
Rev 02
740-023211
VM82438
Power Entry Module 4x60A
SCG 0
REV 15
710-003423
DS6649
SCG 1
REV 15
710-003423
DR6775
740-026941
737F-1083
RE-DUO-1800
740-026941
737F-1104
RE-DUO-1800
CB 0
REV 06
710-022597
DW8542
LCC Control Board
CB 1
REV 06
710-022597
DW8530
LCC Control Board
565
FPC 0
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
MMB 0
FPC 1
CPU
PIC 0
PIC 1
MMB 0
MMB 1
FPC 2
CPU
PIC 0
PIC 1
Xcvr
BRIDGE
MMB 0
MMB 1
FPC 3
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
PIC 3
MMB 0
FPC 4
CPU
PIC 0
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
02
02
11
01
01
01
01
03
16
09
03
06
04
04
16
09
03
05
0
02
04
04
10
09
13
01
REV
REV
REV
REV
REV
REV
REV
0
1
2
3
4
5
6
7
8
9
PIC 3
MMB 0
FPC 5
CPU
PIC 0
Xcvr 0
PIC 1
PIC 2
PIC 3
Xcvr 0
Xcvr 1
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
PIC 2
566
0
1
2
3
0
0
0
1
2
3
0
01
01
17
04
06
07
22
710-010845
710-011481
750-017405
740-014279
740-014279
740-014279
740-014279
710-010842
710-013037
710-016744
711-029996
750-034781
710-025563
710-025563
710-013037
710-016744
711-029996
750-034781
740-032210
711-029995
710-025563
710-025563
710-021534
710-016744
750-012266
740-011613
NON-JNPR
NON-JNPR
NON-JNPR
750-007641
740-011613
750-007444
710-025563
710-013035
710-016744
750-007141
JE2392
JF6820
DP7259
AA0741N1C8T
AA0746N1GAM
AA0747N1H0B
AA0748N1HZ5
HY7601
BBAA7398
BBAA2329
EB1575
EB9980
BBAA5325
BBAA5444
BBAA7185
BBAA3522
EB1557
EB4660
J10F73666
EB2237
BBAA5347
BBAA5401
DZ0941
DY6364
DK9192
AM0812S8WVD
PDD63Q4
PDE4G54
PD40MAG
HJ2003
AM0812S8WVG
JB6873
DZ0281
DK0614
DK1616
DM1870
FPC Type 4
FPC CPU-Enhanced
XFP-10G-LR
XFP-10G-LR
XFP-10G-LR
XFP-10G-LR
ST-MMB
FPC Type 4-ES
ST-PMB2
100GE
100GE CFP
ST-MMB2
ST-MMB2
FPC Type 4-ES
ST-PMB2
100GE
100GE CFP
CFP-100G-LR4
100GE Bridge Board
ST-MMB2
ST-MMB2
FPC Type 1-ES
ST-PMB2
4x 1GE(LAN), IQ2
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
1x CHSTM1 IQ SDH, SMIR
ST-MMB2
FPC Type 3-ES
ST-PMB2
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
01
01
01
01
01
01
01
01
01
16
05
740-011782
740-011782
740-007326
740-011782
740-011782
740-011782
740-011782
740-011782
740-011613
740-011782
750-009450
750-004424
PCL3UKW
P7E0T73
P4T0WLR
PAR1LRL
P9M0U3Z
P9M0U0C
P9M0TLG
P9M0U0F
PFA6LAP
PCH2P0U
CV2565
HH3057
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
1x OC-192 SM SR2
1x 10GE(LAN),10GBASE-LR
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
12
04
07
05
11
01
01
32
12
01
01
750-013423
710-016036
710-013560
710-013563
750-012793
740-014289
750-004695
750-003700
750-009553
740-011785
740-011785
DP0403
DK1988
DR0004
DR0089
DR6107
C743XU074
HD5980
DL3770
WB8901
P9D1GTQ
PDS0MMB
MultiServices 500
ST-MMB2
E2-FPC Type 3
FPC CPU-Enhanced
XFP-10G-SR
1x Tunnel
1x OC-192 12xMM VSR
4x OC-48 SONET
SFP-SR
SFP-SR
Xcvr 3
MMB 0
MMB 1
FPC 6
CPU
PIC 0
Xcvr 3
Xcvr 4
Xcvr 5
PIC 1
PIC 3
MMB 0
FPC 7
CPU
PIC 0
Xcvr 1
Xcvr 2
Xcvr 3
MMB 0
SPMB 0
SPMB 1
SIB 0
B Board
SIB 1
B Board
SIB 2
SIB 3
B Board
SIB 4
B Board
Fan Tray 0
Fan Tray 1
Fan Tray 2

sfc (TX Matrix Plus
Router)
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
07
07
07
07
07
01
01
01
03
02
04
08
04
11
01
02
01
04
04
04
07
07
07
07
740-011785
710-010171
710-010171
710-013035
710-016744
750-015217
740-011613
740-011782
740-011782
750-003336
750-012793
710-016036
710-010845
710-011481
750-017405
740-014279
740-011571
740-014279
710-010842
710-023321
710-023321
710-022594
710-023185
710-022594
710-023185
PDE1KXP
DP7374
DP7404
DM0994
DM3651
DN4743
AM0812S8XB0
PB829RB
P8J1SYX
HJ9954
JM7665
DN6913
JM3958
JK3669
DP8837
753019A00277
C850XJ00P
AA0813N1RTG
JN1971
DW3629
DW3621
DW4200
DW3932
DW4193
DW3904
SFP-SR
MMB-5M3-288mbit
MMB-5M3-288mbit
FPC Type 3-ES
ST-PMB2
8x 1GE(TYPE3), IQ2
SFP-SX
SFP-SX
SFP-SX
ST-MMB2
FPC Type 4
FPC CPU-Enhanced
XFP-10G-LR
XFP-10G-SR
XFP-10G-LR
ST-MMB
LCC Switch CPU
LCC Switch CPU
LCC SIB
LCC SIB Mezz
LCC SIB
LCC SIB Mezz
REV
REV
REV
REV
07
06
08
06
710-022594
710-023185
710-022594
710-023185
DW4210
DT5780
DW8019
DT5795
LCC SIB
LCC SIB Mezz
LCC SIB
LCC SIB Mezz
Front Top Fan Tray
user@host> show chassis hardware sfc 0

sfc0-re0:
Item
Description
Chassis
JN112F007AHB
TXP
Midplane
REV 05
710-022574
TS4027
SFC Midplane
FPM Display
REV 03
710-024027
DX0282
TXP FPM Display
CIP 0
REV 04
710-023792
DW4889
TXP CIP
CIP 1
REV 04
710-023792
DW4887
TXP CIP
PEM 0
Rev 07
740-027463
UM26368
Power Entry Module
740-026942
737A-1064
SFC RE
740-026942
737A-1082
SFC RE
CB 0
REV 09
710-022606
DW6099
SFC Control Board
CB 1
REV 09
710-022606
DW6096
SFC Control Board
SPMB 0
BUILTIN
SFC Switch CPU
SPMB 1
BUILTIN
SFC Switch CPU
SIB F13 0
REV 04
710-022600
DX0841
F13 SIB
B Board
REV 03
710-023431
DX0966
F13 SIB Mezz
SIB F13 1
REV 04
750-024564
DW5776
F13 SIB
B Board
REV 03
710-023431
DW9028
F13 SIB
SIB F13 3
REV 04
750-024564
DW5762
F13 SIB
B Board
REV 03
710-023431
DW9059
F13 SIB
SIB F13 4
REV 04
750-024564
DW5797
F13 SIB
B Board
REV 03
710-023431
DW9041
F13 SIB
SIB F13 6
REV 04
750-024564
DW5770
F13 SIB
B Board
REV 03
710-023431
DW9079
F13 SIB Mezz
567
SIB
B
SIB
B
SIB
B
SIB
B
SIB
B
SIB
B
SIB
B
SIB
B
SIB
B
SIB
B
SIB
B
SIB
B
SIB
B
SIB
B
SIB
B
SIB
B
SIB
B
SIB
B
SIB
B
SIB
B
SIB
B
SIB
B
SIB
B
SIB
B
SIB
B
Fan
Fan
Fan
Fan
Fan
Fan

extensive (TX Matrix
Plus Router)
568
F13 7
Board
F13 8
Board
F13 9
Board
F13 11
Board
F13 12
Board
F2S 0/0
Board
F2S 0/2
Board
F2S 0/4
Board
F2S 0/6
Board
F2S 1/0
Board
F2S 1/2
Board
F2S 1/4
Board
F2S 1/6
Board
F2S 2/0
Board
F2S 2/2
Board
F2S 2/4
Board
F2S 2/6
Board
F2S 3/0
Board
F2S 3/2
Board
F2S 3/4
Board
F2S 3/6
Board
F2S 4/0
Board
F2S 4/2
Board
F2S 4/4
Board
F2S 4/6
Board
Tray 0
Tray 1
Tray 2
Tray 3
Tray 4
Tray 5
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
04
03
04
03
04
03
04
03
04
03
05
05
05
05
05
05
05
05
04
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
06
06
06
06
06
06
750-024564
710-023431
750-024564
710-023431
750-024564
710-023431
710-022600
710-023431
750-024564
710-023431
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
760-024497
760-024497
760-024502
760-024502
760-024502
760-024502
DW5758
DW9047
DW5761
DW9043
DW5754
DW9078
DX0826
DX0967
DW5794
DW9044
DW7897
DW7657
DW7833
DW7526
DW7875
DW7588
DW7860
DW7589
DW4820
DW8510
DW7849
DW7525
DW7927
DW7556
DW7866
DW7651
DW7880
DW7523
DW7895
DW7591
DW7907
DW7590
DW7785
DW7524
DW7782
DW7634
DW7793
DW7548
DW7779
DW7587
DW7930
DW7505
DW7867
DW7656
DW7917
DW7640
DW7929
DW7643
DW7870
DW7635
DV7831
DV9614
DV9618
DV9616
DV7807
DV7828
F13 SIB
F13 SIB
F13 SIB
F13 SIB Mezz
F13 SIB
F13 SIB Mezz
F13 SIB
F13 SIB Mezz
F13 SIB
F13 SIB Mezz
F2S SIB
NEO PMB
F2S SIB
NEO PMB
F2S SIB
NEO PMB
F2S SIB
NEO PMB
F2S SIB
NEO PMB
F2S SIB
NEO PMB
F2S SIB
F2S SIB Mezz
F2S SIB
NEO PMB
F2S SIB
NEO PMB
F2S SIB
NEO PMB
F2S SIB
NEO PMB
F2S SIB
NEO PMB
F2S SIB
NEO PMB
F2S SIB
NEO PMB
F2S SIB
NEO PMB
F2S SIB
NEO PMB
F2S SIB
NEO PMB
F2S SIB
NEO PMB
F2S SIB
NEO PMB
F2S SIB
NEO PMB
Front Fan Tray
Front Fan Tray
Rear Fan Tray
Rear Fan Tray
Rear Fan Tray
Rear Fan Tray

sfc0-re0:
Item
Chassis
Jedec Code:
Version
0x7fb0
Part number
Serial number
Description
JN112F007AHB
TXP
EEPROM Version:
0x02
S/N:
JN112F007AHB
Assembly Flags:
0x00
Assembly ID: 0x052c

Date:
00-00-0000
ID: TXP
Address 0x00: 00 00 00 00 00 00 00 00 00 00 00 00
I2C Hex Data:
Address 0x00: 7f b0 02 ff 05 2c 00 00 00 00 00 00
Address 0x10: 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x20: 4a 4e 31 31 32 46 30 30 37 41 48 42
Address 0x30: 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x40: 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x50: 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x60: 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x70: 00 00 00 00 00 00 00 00 00 00 00 00
Midplane
REV 05
710-022574
TS4027
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
710-022574
S/N:
Assembly ID: 0x0962
Assembly Version:
Date:
03-23-2009
Assembly Flags:
Version:
REV 05
ID: SFC Midplane
Address 0x00: ad 01 ff ff 00 1d b5 14 00 00 ff ff
I2C Hex Data:
Address 0x00: 7f b0 01 ff 09 62 01 05 52 45 56 20
Address 0x10: 00 00 00 00 37 31 30 2d 30 32 32 35
Address 0x20: 53 2f 4e 20 54 53 34 30 32 37 00 00
Address 0x30: d9 ff ff ff ad 01 ff ff 00 1d b5 14
Address 0x40: ff ff ff ff 00 ff ff ff ff ff ff ff
FPM Display
REV 03
710-024027
DX0282
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
710-024027
S/N:
Assembly ID: 0x096c
Assembly Version:
Date:
02-10-2009
Assembly Flags:
Version:
REV 03
ID: TXP FPM Display
FRU Model Number:
I2C Hex Data:
Address 0x00: 7f b0 01 ff 09 6c 01 03 52 45 56 20
Address 0x10: 00 00 00 00 37 31 30 2d 30 32 34 30
Address 0x20: 53 2f 4e 20 44 58 30 32 38 32 00 00
Address 0x30: d9 ff ff ff ff ff ff ff ff ff ff ff
Address 0x50: 52 41 46 54 2d 54 58 50 00 00 00 00
Address 0x60: 00 00 00 00 00 00 ff ff ff ff ff ff
CIP 0
REV 04
710-023792
DW4889
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
710-023792
S/N:
Assembly ID: 0x0969
Assembly Version:
Date:
01-26-2009
Assembly Flags:
Version:
REV 04
ID: TXP CIP
FRU Model Number:
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
SFC
00
00
00
00
00
00
00
00
Midplane
0x01
S/N TS4027
01.05
0x00
ff ff ff ff
30
37
00
00
ff
ff
ff
ff
35
34
17
00
ff
ff
ff
ff
00
00
03
ff
ff
ff
ff
ff
TXP
00
00
07
ff
ff
ff
ff
ff
FPM Display
0x01
S/N DX0282
01.03
0x00
CRAFT-TXP
ff ff ff ff
30
32
00
ff
00
00
ff
ff
33
37
0a
ff
00
00
ff
ff
00
00
02
ff
00
00
ff
ff
TXP
00
00
07
ff
43
00
ff
ff
CIP
0x01
S/N DW4889
01.04
0x00
CIP-TXP
569


clei-models (TX Matrix
Plus Router)

sfc0-re0:
Item
FRU model number
Midplane
REV 05
710-022574
CHAS-BP-TXP-S
FPM Display
REV 03
710-024027
CRAFT-TXP-S
CIP 0
REV 05
710-023792
CIP-TXP-S
CIP 1
REV 05
710-023792
CIP-TXP-S
PEM 0
Rev 04
740-027463
IPUPAFGKTA
PWR-TXP-7-60-DC
PEM 1
Rev 04
740-027463
IPUPAFGKTA
PWR-TXP-7-60-DC
740-026942
RE-DUO-C2600-16G-S
740-026942
RE-DUO-C2600-16G-S
CB 0
REV 05
710-022606
CB-TXP-S
CB 1
REV 09
710-022606
CB-TXP-S
SIB F13 0
REV 04
750-024564
SIB-TXP-F13
SIB F13 3
REV 04
750-024564
SIB-TXP-F13
SIB F13 8
REV 04
750-024564
SIB-TXP-F13
SIB F13 11
REV 04
750-024564
SIB-TXP-F13
SIB F13 12
REV 03
750-024564
SIB-TXP-F13
SIB F2S 0/0
REV 05
710-022603
SIB-TXP-F2S-S
SIB F2S 0/2
REV 05
710-022603
SIB-TXP-F2S-S
SIB F2S 0/4
REV 04
710-022603
SIB-TXP-F2S-S
SIB F2S 0/6
REV 04
710-022603
SIB-TXP-F2S-S
SIB F2S 1/0
REV 04
710-022603
SIB-TXP-F2S-S
SIB F2S 1/2
REV 05
710-022603
SIB-TXP-F2S-S
SIB F2S 1/4
REV 04
710-022603
SIB-TXP-F2S-S
SIB F2S 1/6
REV 05
710-022603
SIB-TXP-F2S-S
SIB F2S 2/0
REV 04
710-022603
SIB-TXP-F2S-S
SIB F2S 2/2
REV 04
710-022603
SIB-TXP-F2S-S
SIB F2S 2/4
REV 05
710-022603
SIB-TXP-F2S-S
SIB F2S 2/6
REV 04
710-022603
SIB-TXP-F2S-S
SIB F2S 3/0
REV 05
710-022603
SIB-TXP-F2S-S
SIB F2S 3/2
REV 03
710-022603
SIB-TXP-F2S-S
SIB F2S 3/4
REV 05
710-022603
SIB-TXP-F2S-S
SIB F2S 3/6
REV 03
710-022603
SIB-TXP-F2S-S
SIB F2S 4/0
REV 03
710-022603
SIB-TXP-F2S-S
SIB F2S 4/2
REV 05
710-022603
SIB-TXP-F2S-S
SIB F2S 4/4
REV 04
710-022603
SIB-TXP-F2S-S
SIB F2S 4/6
REV 03
710-022603
SIB-TXP-F2S-S
Fan Tray 0
REV 02
760-024497
FANTRAY-TXP-H-S
Fan Tray 1
REV 02
760-024497
FANTRAY-TXP-H-S
Fan Tray 2
REV 05
760-024502
FANTRAY-TXP-V-S
Fan Tray 3
Fan Tray 4
REV 05
760-024502
FANTRAY-TXP-V-S
Fan Tray 5
REV 02
760-024502
FANTRAY-TXP-V-S
lcc0-re0:
Item
FRU model number
Midplane
REV 03
710-017247
CHAS-BP-T1600-S
FPM Display
REV 01
710-021387
CRAFT-T1600-S
CIP
REV 06
710-002895
CIP-L-T640-S
PEM 1
Rev 02
740-023211
IPUPAC8KTA
PWR-T1600-4-60-DC-S
SCG 0
REV 15
710-003423
SCG-T-S
SCG 1
REV 15
710-003423
SCG-T-S
740-026941
RE-DUO-C1800-8G-S
570

CB 0
REV 06
CB 1
REV 06
FPC 1
REV 07
PIC 0
REV 05
PIC 1
REV 03
PIC 2
REV 01
FPC 3
REV 12
PIC 0
REV 02
FPC 4
REV 05
PIC 0
REV 04
PIC 1
REV 22
PIC 2
REV 09
PIC 3
REV 08
FPC 5
REV 07
PIC 0
REV 14
PIC 1
REV 16
PIC 2
REV 12
FPC 6
REV 07
PIC 0
REV 09
PIC 1
REV 06
PIC 2
REV 06
FPC 7
REV 03
PIC 0
REV 13
PIC 1
REV 05
PIC 2
REV 10
PIC 3
REV 03
SIB 0
REV 07
SIB 1
REV 07
SIB 3
REV 06
SIB 4
REV 08
Fan Tray 0
Fan Tray 1
Fan Tray 2
740-026941
710-022597
710-022597
710-013035
750-015217
750-004424
750-003336
710-013037
750-010850
710-021534
750-014627
750-005634
750-002911
750-021652
710-007529
750-009567
750-007141
750-009567
710-013035
750-009567
750-015217
750-015217
710-021540
750-001901
750-001900
750-008155
750-014638
710-022594
710-022594
710-022594
710-022594
RE-DUO-C1800-8G-S
CB-LCC-S
CB-LCC-S
T640-FPC3-ES
PC-1XGE-LR
PC-4OC48-SON-SMSR
T1600-FPC4-ES
PD-1OC768-SON-SR
T640-FPC1-ES
PB-4OC3-1OC12-SON-SFP
PB-1CHOC12SMIR-QPP
PB-4FE-TX
PB-1CHOC12-STM4-IQE-SFP
T640-FPC3
PC-1XGE-XENPAK
PC-10GE-SFP
PC-1XGE-XENPAK
T640-FPC3-ES
PC-1XGE-XENPAK
T640-FPC2-ES
PB-4OC12-SON-SMIR
PB-1OC48-SON-SMSR
PB-2GE-SFP-QPP
PB-1OC48-SON-B-SFP
SIB-TXP-T1600-S
SIB-TXP-T1600-S
SIB-TXP-T1600-S
SIB-TXP-T1600-S
FANTRAY-T-S
FANTRAY-T-S
FANTRAY-TXP-R-S
lcc1-re0:
Item
FRU model number
Midplane
REV 04
710-017247
CHAS-BP-T1600-S
FPM Display
REV 01
710-021387
CRAFT-T1600-S
CIP
REV 06
710-002895
CIP-L-T640-S
PEM 0
Rev 02
740-023211
IPUPAC8KTA
PWR-T1600-4-60-DC-S
SCG 0
REV 15
710-003423
SCG-T-S
SCG 1
REV 15
710-003423
SCG-T-S
740-026941
RE-DUO-C1800-8G-S
740-026941
RE-DUO-C1800-8G-S
CB 0
REV 06
710-022597
CB-LCC-S
CB 1
REV 06
710-022597
CB-LCC-S
FPC 0
REV 02
710-010845
T640-FPC4-ES
PIC 0
REV 11
750-017405
PD-4XGE-XFP
FPC 1
REV 16
710-013037
T1600-FPC4-ES
PIC 1
REV 06
750-034781
PD-1CE-CFP
FPC 2
REV 16
710-013037
T1600-FPC4-ES
PIC 1
REV 05
750-034781
PD-1CE-CFP
FPC 3
REV 10
710-021534
T640-FPC1-ES
PIC 0
REV 13
750-012266
PIC 1
REV 01
750-007641
PE-1GE-SFP-QPP
PIC 3
REV 17
750-007444
PB-1CHSTM1-SMIR-QPP
FPC 4
REV 06
710-013035
T640-FPC3-ES
PIC 0
REV 22
750-007141
PC-10GE-SFP
571
PIC 1
PIC 2
PIC 3
FPC 5
PIC 0
PIC 1
PIC 2
PIC 3
FPC 6
PIC 0
PIC 1
PIC 3
FPC 7
PIC 0
SIB 0
SIB 1
SIB 3
SIB 4
Fan Tray 0
Fan Tray 1
Fan Tray 2

detail (TX Matrix Plus
Router)
572
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
16
05
12
07
11
01
32
12
07
07
03
02
08
11
07
07
07
08
750-009450
750-004424
750-013423
710-013560
750-012793
750-004695
750-003700
750-009553
710-013035
750-015217
750-003336
750-012793
710-010845
750-017405
710-022594
710-022594
710-022594
710-022594
PC-1OC192-SON-SR2
PC-1XGE-LR
PC-MS-500-3
T640-FPC3-E2
PC-TUNNEL
PC-1OC192-SON-VSR
PC-4OC48-SON-SFP
T640-FPC3-ES
PC-4OC48-SON-SMSR
T640-FPC4-ES
PD-4XGE-XFP
SIB-TXP-T1600-S
SIB-TXP-T1600-S
SIB-TXP-T1600-S
SIB-TXP-T1600-S
FANTRAY-T-S
FANTRAY-T-S
FANTRAY-TXP-R-S

sfc0-re0:
Item
Description
Chassis
JN111B023AHB
TXP
Midplane
REV 01
710-022574
TR7990
SFC Midplane
FPM Display
REV 03
710-024027
DW4699
TXP FPM Display
CIP 0
REV 01
710-023792
DR1437
TXP CIP
CIP 1
REV 02
710-023792
DS4564
TXP CIP
PEM 0
Rev 07
740-027463
UM26360
Power Entry Module
740-026942
737A-1024
SFC RE
ad0
3887 MB SMART CF
200811050193CEB1CEB1 Compact Flash
ad1
30533 MB SAMSUNG MCBQE32G8MPP-0V SY814A0762
Disk 1
740-026942
737A-1024
SFC RE
ad0
3887 MB SMART CF
20081105004C19A019A0 Compact Flash
ad1
Disk 1
CB 0
REV 03
710-022606
DR7134
SFC Control Board
CB 1
REV 01
710-022606
DP8890
SFC Control Board
SPMB 0
BUILTIN
SFC Switch CPU
SPMB 1
BUILTIN
SFC Switch CPU
SIB F13 0
REV 03
750-024564
DT9478
F13 SIB
B Board
REV 02
710-023431
DT6554
F13 SIB
SIB F13 1
REV 03
750-024564
DT9454
F13 SIB
B Board
REV 02
710-023431
DT6551
F13 SIB
SIB F2S 0/0
REV 02
710-022603
DT2838
F2S SIB
B Board
REV 02
710-023787
DT1725
NEO PMB
SIB F2S 0/2
REV 02
710-022603
DT2824
F2S SIB
B Board
REV 02
710-023787
DT1706
NEO PMB
SIB F2S 0/4
REV 02
710-022603
DT2822
F2S SIB
B Board
REV 02
710-023787
DT1696
NEO PMB
SIB F2S 0/6
REV 02
710-022603
DT2823
F2S SIB
B Board
REV 02
710-023787
DT1717
NEO PMB
SIB F2S 1/0
REV 03
710-022603
DV0059
F2S SIB
B Board
REV 03
710-023787
DT9942
NEO PMB
SIB F2S 1/2
REV 02
710-022603
DT2826
F2S SIB
B Board
REV 02
710-023787
DT1713
NEO PMB
SIB F2S 1/4
REV 03
710-022603
DV0092
F2S SIB
B Board
REV 03
710-023787
DV0000
NEO PMB
SIB
B
SIB
B
SIB
B
SIB
B
Fan
Fan
Fan
Fan
Fan
Fan
F2S 1/6
Board
F2S 2/0
Board
F2S 2/2
Board
F2S 2/4
Board
Tray 0
Tray 1
Tray 2
Tray 3
Tray 4
Tray 5
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
03
03
03
03
03
03
03
03
02
06
02
02
02
06
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
760-024497
760-024497
760-024502
760-024502
760-024502
760-024502
DV0079
DT9972
DV0100
DT9925
DV0050
DV0005
DV0097
DT9936
DR8286
DV9624
DR8259
DR8270
DR8284
DV7813
F2S SIB
NEO PMB
F2S SIB
NEO PMB
F2S SIB
NEO PMB
F2S SIB
NEO PMB
Front Fan Tray
Front Fan Tray
Rear Fan Tray
Rear Fan Tray
Rear Fan Tray
Rear Fan Tray
lcc0-re0:
Item
Description
Chassis
JN1101F27AHA
T1600
Midplane
REV 04
710-017247
RC5317
T Series Backplane
FPM GBUS
REV 10
710-002901
DS8197
T640 FPM Board
FPM Display
REV 01
710-021387
DS6433
T1600 FPM Display
CIP
REV 06
710-002895
DS1493
T Series CIP
PEM 0
Rev 08
740-017906
UD26601
SCG 0
REV 15
710-003423
DP5847
SCG 1
REV 15
710-003423
DR0924
740-026942
737F-1024
LCC RE
ad0
3887 MB SMART CF
2008110502B63E513E51 Compact Flash
ad1
Disk 1
740-026942
737F-1024
LCC RE
ad0
3887 MB SMART CF
2008110500F9A8A8A8A8 Compact Flash
ad1
Disk 1
CB 0
REV 05
710-022597
DV4264
LCC Control Board
CB 1
REV 03
710-022597
DP8558
LCC Control Board
FPC 0
REV 14
710-013037
DS9967
FPC Type 4-ES
CPU
REV 08
710-016744
DS3989
ST-PMB2
PIC 0
REV 12
750-013198
DL7506
1x Tunnel
PIC 1
REV 12
750-013198
DL7505
1x Tunnel
MMB 0
REV 01
710-025563
DS8524
ST-MMB2
MMB 1
REV 01
710-025563
DS8373
ST-MMB2
FPC 1
REV 14
710-013037
DT0027
FPC Type 4-ES
CPU
REV 09
710-016744
DS7684
ST-PMB2
PIC 0
REV 12
750-013198
DL7512
1x Tunnel
PIC 1
REV 12
750-013198
DL7498
1x Tunnel
MMB 0
REV 01
710-025563
DS8494
ST-MMB2
MMB 1
REV 01
710-025563
DS8436
ST-MMB2
SPMB 0
REV 04
710-023321
DV3867
LCC Switch CPU
SPMB 1
REV 02
710-023321
DP0238
LCC Switch CPU
SIB 0
REV 06
710-022594
DT8268
LCC SIB
B Board
REV 06
710-023185
DT5791
LCC SIB Mezz
SIB 1
REV 06
710-022594
DT8261
LCC SIB
B Board
REV 06
710-023185
DT5769
LCC SIB Mezz
SIB 2
REV 04
710-022594
DS2315
LCC SIB
B Board
REV 06
710-023185
DT5788
LCC SIB Mezz
SIB 3
REV 06
710-022594
DT8253
LCC SIB
B Board
REV 06
710-023185
DT5811
LCC SIB Mezz
SIB 4
REV 06
710-022594
DT8248
LCC SIB
B Board
REV 06
710-023185
DT5812
LCC SIB Mezz
Fan Tray 0
Front Top Fan Tray
Fan Tray 1
573
Fan Tray 2

models (TX Matrix
Plus Router)
Rear Fan Tray

sfc0-re0:
Item
FRU model number
FPM Display
REV 03
710-024027
DX0282
CRAFT-TXP
CIP 0
REV 04
710-023792
DW4889
CIP-TXP
CIP 1
REV 04
710-023792
DW4887
CIP-TXP
PEM 0
Rev 07
740-027463
UM26368

740-026942
737A-1064
RE-TXP-SFC-DUO-2600-16G
740-026942
737A-1082
RE-TXP-SFC-DUO-2600-16G
CB 0
REV 09
710-022606
DW6099
CB-TXP
CB 1
REV 09
710-022606
DW6096
CB-TXP
SIB F13 1
REV 04
750-024564
DW5776
SIB-TXP-F13
SIB F13 3
REV 04
750-024564
DW5762
SIB-TXP-F13
SIB F13 4
REV 04
750-024564
DW5797
SIB-TXP-F13
SIB F13 6
REV 04
750-024564
DW5770
SIB-TXP-F13
SIB F13 7
REV 04
750-024564
DW5758
SIB-TXP-F13
SIB F13 8
REV 04
750-024564
DW5761
SIB-TXP-F13
SIB F13 9
REV 04
750-024564
DW5754
SIB-TXP-F13
SIB F13 12
REV 04
750-024564
DW5794
SIB-TXP-F13
SIB F2S 0/0
REV 05
710-022603
DW7897
SIB F2S 0/2
REV 05
710-022603
DW7833
SIB F2S 0/4
REV 05
710-022603
DW7875
SIB F2S 0/6
REV 05
710-022603
DW7860
SIB F2S 1/0
REV 04
710-022603
DW4820
SIB F2S 1/2
REV 05
710-022603
DW7849
SIB F2S 1/4
REV 05
710-022603
DW7927
SIB-TXP-F2S
SIB F2S 1/6
REV 05
710-022603
DW7866
SIB F2S 2/0
REV 05
710-022603
DW7880
SIB F2S 2/2
REV 05
710-022603
DW7895
SIB F2S 2/4
REV 05
710-022603
DW7907
SIB F2S 2/6
REV 05
710-022603
DW7785
SIB F2S 3/0
REV 05
710-022603
DW7782
SIB F2S 3/2
REV 05
710-022603
DW7793
SIB F2S 3/4
REV 05
710-022603
DW7779
SIB F2S 3/6
REV 05
710-022603
DW7930
SIB F2S 4/0
REV 05
710-022603
DW7867
SIB F2S 4/2
REV 05
710-022603
DW7917
SIB F2S 4/4
REV 05
710-022603
DW7929
SIB F2S 4/6
REV 05
710-022603
DW7870
Fan Tray 0
REV 06
760-024497
DV7831
FANTRAY-TXP-F
Fan Tray 1
REV 06
760-024497
DV9614
FANTRAY-TXP-F
Fan Tray 2
REV 06
760-024502
DV9618
FANTRAY-TXP-R
Fan Tray 3
REV 06
760-024502
DV9616
FANTRAY-TXP-R
Fan Tray 4
REV 06
760-024502
DV7807
FANTRAY-TXP-R
Fan Tray 5
REV 06
760-024502
DV7828
FANTRAY-TXP-R
lcc0-re0:
Item
FRU model number
Midplane
REV 03
710-017247
RC3765
CHAS-BP-T1600-S
FPM Display
REV 01
710-021387
DN5441
CRAFT-T1600-S
CIP
REV 06
710-002895
DP6021
CIP-L-T640-S
PEM 0
Rev 07
740-017906
UA26384
PWR-T1600-3-80-DC-S
PEM 1
Rev 07
740-017906
UA26296
PWR-T1600-3-80-DC-S
SCG 0
REV 15
710-003423
DR0875
SCG-T-S
CB 0
REV 06
710-022597
DW8534
CB-LCC
574
CB 1
FPC 4
PIC 0
PIC 1
FPC 6
PIC 0
PIC 1
FPC 7
PIC 0
PIC 1
PIC 2
SIB 0
SIB 1
SIB 2
SIB 3
SIB 4
Fan Tray 0
Fan Tray 1
Fan Tray 2
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
06
12
11
11
14
13
13
07
16
08
10
08
08
08
08
08
710-022597
710-013037
750-017405
750-017405
710-013037
750-017405
750-017405
710-013035
750-007141
750-015749
750-009450
710-022594
710-022594
710-022594
710-022594
710-022594
DW8527
DJ8717
DP8795
DP8794
DS5335
DS7634
DS7637
DM0990
JJ8067
WE9598
HX6466
DW8033
DW8044
DW8020
DW8063
DW8064
CB-LCC
T1600-FPC4-ES
PD-4XGE-XFP
PD-4XGE-XFP
T1600-FPC4-ES
PD-4XGE-XFP
PD-4XGE-XFP
T1600-FPC3-ES
PC-10GE-SFP
PC-1OC192-SON-XFP
PC-1OC192-SON-SR2
SIB-TXP-T1600-S
SIB-TXP-T1600-S
SIB-TXP-T1600-S
SIB-TXP-T1600-S
SIB-TXP-T1600-S
FANTRAY-T-S
FANTRAY-T-S
FANTRAY-TXP-R-S
lcc1-re0:
Item
FRU model number
Midplane
REV 04
710-017247
RC5361
CHAS-BP-T1600-S
FPM Display
REV 01
710-021387
DS6430
CRAFT-T1600-S
CIP
REV 06
710-002895
DS4239
CIP-L-T640-S
PEM 0
Rev 08
740-017906
UD26649
PWR-T1600-3-80-DC-S
SCG 0
REV 15
710-003423
DP5820
SCG-T-S
CB 0
REV 06
710-022597
DW8523
CB-LCC
CB 1
REV 06
710-022597
DW8528
CB-LCC
FPC 4
REV 12
710-013037
DP8509
T1600-FPC4-ES
PIC 0
REV 11
750-017405
DP8808
PD-4XGE-XFP
PIC 1
REV 11
750-017405
DP7263
PD-4XGE-XFP
FPC 6
REV 14
710-013037
DS9961
T1600-FPC4-ES
PIC 0
REV 13
750-017405
DS5532
PD-4XGE-XFP
PIC 1
REV 13
750-017405
DS7639
PD-4XGE-XFP
FPC 7
REV 03
710-013035
DF5564
T1600-FPC3-ES
PIC 0
REV 16
750-007141
JJ8063
PC-10GE-SFP
SIB 0
REV 08
710-022594
DW8035
SIB-TXP-T1600-S
SIB 1
REV 10
710-022594
DX7672
SIB-TXP-T1600-S
SIB 2
REV 08
710-022594
DW8060
SIB-TXP-T1600-S
SIB 3
REV 08
710-022594
DW8072
SIB-TXP-T1600-S
SIB 4
REV 08
710-022594
DW8043
SIB-TXP-T1600-S
Fan Tray 0
FANTRAY-T-S
Fan Tray 1
FANTRAY-T-S
Fan Tray 2
FANTRAY-TXP-R-S
lcc2-re0:
Item
FRU model number
Midplane
REV 03
710-017247
RC3956
CHAS-BP-T1600-S
FPM Display
REV 01
710-021387
DN7030
CRAFT-T1600-S
CIP
REV 06
710-002895
DM3962
CIP-L-T640-S
PEM 0
Rev 08
740-017906
UD26519
PWR-T1600-3-80-DC-S
PEM 1
Rev 07
740-017906
UC26601
PWR-T1600-3-80-DC-S
SCG 0
REV 15
710-003423
DP0277
SCG-T-S
CB 0
REV 06
710-022597
DW8524
CB-LCC
CB 1
REV 06
710-022597
DW8536
CB-LCC
FPC 4
REV 12
710-013037
DR1194
T1600-FPC4-ES
575
PIC 0
PIC 1
FPC 5
PIC 1
FPC 6
PIC 0
PIC 1
FPC 7
PIC 0
SIB 0
SIB 1
SIB 2
SIB 3
SIB 4
Fan Tray 0
Fan Tray 1
Fan Tray 2
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
11
11
12
11
12
14
11
04
16
07
07
07
07
07
750-017405
750-017405
710-013037
750-017405
710-013037
750-012518
750-017405
710-013560
750-007141
710-022594
710-022594
710-022594
710-022594
710-022594
DP8811
DP8823
DR1184
DP4744
DN8622
JY9924
DP8776
JR3968
NC9330
DW4217
DW4213
DW4189
DW4173
DW4201
PD-4XGE-XFP
PD-4XGE-XFP
T1600-FPC4-ES
PD-4XGE-XFP
T1600-FPC4-ES
PD-4OC192-SON-XFP
PD-4XGE-XFP
T640-FPC3-E2
PC-10GE-SFP
SIB-TXP-T1600-S
SIB-TXP-T1600-S
SIB-TXP-T1600-S
SIB-TXP-T1600-S
SIB-TXP-T1600-S
FANTRAY-T-S
FANTRAY-T-S
FANTRAY-TXP-R-S
lcc3-re0:
Item
FRU model number
Midplane
REV 04
710-017247
RC5319
CHAS-BP-T1600-S
FPM Display
REV 01
710-021387
DS6402
CRAFT-T1600-S
CIP
REV 06
710-002895
DR9973
CIP-L-T640-S
PEM 0
Rev 07
740-017906
UC26496
PWR-T1600-3-80-DC-S
PEM 1
Rev 07
740-017906
UC26599
PWR-T1600-3-80-DC-S
SCG 0
REV 15
710-003423
DP5831
SCG-T-S
CB 0
REV 06
710-022597
DW8533
CB-LCC
CB 1
REV 06
710-022597
DW8538
CB-LCC
FPC 0
REV 14
710-013037
DS5345
T1600-FPC4-ES
PIC 0
REV 13
750-017405
DS7641
PD-4XGE-XFP
PIC 1
REV 13
750-017405
DS5479
PD-4XGE-XFP
FPC 1
REV 14
710-013037
DS7338
T1600-FPC4-ES
PIC 0
REV 13
750-017405
DS7631
PD-4XGE-XFP
PIC 1
REV 13
750-017405
DS7632
PD-4XGE-XFP
FPC 2
REV 14
710-013037
DS9962
T1600-FPC4-ES
PIC 0
REV 13
750-017405
DS7581
PD-4XGE-XFP
PIC 1
REV 13
750-017405
DS7627
PD-4XGE-XFP
FPC 4
REV 10
710-010845
JZ6573
T640-FPC4-ES
PIC 0
REV 14
750-012518
JT5124
PD-4OC192-SON-XFP
FPC 5
REV 14
710-013037
DT0016
T1600-FPC4-ES
PIC 0
REV 14
750-012518
JY9918
PD-4OC192-SON-XFP
FPC 7
REV 07
710-013035
DM0967
T1600-FPC3-ES
PIC 0
REV 16
750-007141
JJ8059
PC-10GE-SFP
PIC 1
REV 13
750-004695
DM5712
PC-TUNNEL
SIB 0
REV 07
710-022594
DW4174
SIB-TXP-T1600-S
SIB 1
REV 07
710-022594
DW4207
SIB-TXP-T1600-S
SIB 2
REV 06
710-022594
DT8231
SIB-TXP-T1600-S
SIB 3
REV 07
710-022594
DW4175
SIB-TXP-T1600-S
SIB 4
REV 07
710-022594
DW4209
SIB-TXP-T1600-S
Fan Tray 0
FANTRAY-T-S
Fan Tray 1
FANTRAY-T-S
Fan Tray 2
FANTRAY-TXP-R-S

(16-Port 10-Gigabit
Ethernet MPC with
576

Hardware inventory:
Item
Version Part number
Chassis
Serial number
JN112D865AFA
Description
MX960
SFP+ Optics [MX

Series Routers])

(MPC3E [MX Series
Routers])
Midplane
FPM Board
REV 03
REV 03
710-013698
710-014974
TS3339
WW6267
MX960 Backplane
Front Panel Display
PDM
Rev 03
Module
PEM 0
Rev 04
in
PEM 1
Rev 04
in
PEM 2
Rev 04
in
CB 0
REV 03
CB 1
REV 03
CB 2
REV 03
FPC 4
REV 02
CPU
REV 02
PIC 0
PIC 1
PIC 2
PIC 3
Fan Tray 0
REV 05
Fan Tray 1
REV 05
740-013110
QCS12485026
Power Distribution
740-013682
QCS12434086
PS 1.7kW; 200-240VAC
740-013682
QCS1243408Z
PS 1.7kW; 200-240VAC
740-013682
QCS1243407X
PS 1.7kW; 200-240VAC
9009009677
9009011510
XF0394
XF0550
XD7455
JR6127
JX0129
BUILTIN
BUILTIN
BUILTIN
BUILTIN
TP9990
VS1709
RE-S-1300
RE-S-1300
MX SCB
MX SCB
MX SCB
MPC M 16x 10GE
AS PMB
4x 10GE(LAN) SFP+
4x 10GE(LAN) SFP+
4x 10GE(LAN) SFP+
4x 10GE(LAN) SFP+
Fan Tray
Fan Tray
Serial number
JN1101AFEAFB
TR4444
KG6056
Description
MX480
MX480 Midplane
Front Panel Display
740-015113
740-015113
710-021523
710-021523
710-021523
750-028467
711-029089
BUILTIN
BUILTIN
BUILTIN
BUILTIN
740-014971
740-014971

Hardware inventory:
Item
Version Part number
Chassis
Midplane
REV 05
710-017414
FPM Board
REV 02
710-017254
PEM 0
Rev 03
740-017330
QCS082090FC
PS 1.2-1.7kW; 100-240V
PEM 1
Rev 03
740-017330
QCS082090FD
PS 1.2-1.7kW; 100-240V

740-013063
740-013063
CB 0
REV 07
710-021523
CB 1
REV 03
710-021523
FPC 1
REV 04.1.07 750-033205
CPU
REV 01
711-035209
MIC 1
REV 10
750-033199
PIC 2
BUILTIN
Xcvr 0
REV 01
740-032210
FPC 2
REV 26
750-016670
CPU
REV 07
710-013713
PIC 0
BUILTIN
Xcvr 0
REV 01
740-011613
PIC 1
BUILTIN
Xcvr 9
REV 01
740-011613
PIC 2
BUILTIN
Xcvr 0
REV 02
740-011613
Xcvr 2
REV 01
740-011613
PIC 3
BUILTIN
Xcvr 5
REV 01
740-011613
Xcvr 7
REV 01
740-011613
Xcvr 8
REV 01
740-011613
Xcvr 9
REV 01
740-011613
FPC 3
REV 12.2.09 750-033205
CPU
REV 03
711-035209
9009004124
9009005569
XZ3587
KH8306
P1240
YL0504
YX4495
BUILTIN
C22CQNE
KH0045
KF5448
BUILTIN
PF21JHU
BUILTIN
AM0813S8ZL6
BUILTIN
PGL2KYF
AM0806S8N4P
BUILTIN
AM0815S967N
AM0806S8N1X
AM0815S967J
AM0815S967M
YR9443
YL6931
RE-S-2000
RE-S-2000
MX SCB
MX SCB
MPCE Type 3D
HMPC PMB 2G
1X100GE CFP
1X100GE CFP
CFP-100G-LR4
DPCE 40x 1GE
DPC PMB
10x 1GE(LAN)
SFP-SX
10x 1GE(LAN)
SFP-SX
10x 1GE(LAN)
SFP-SX
SFP-SX
10x 1GE(LAN)
SFP-SX
SFP-SX
SFP-SX
SFP-SX
MPCE Type 3D
HMPC PMB 2G
R EQ
EQ
EQ
EQ
EQ
577
MIC 0
PIC 0
Xcvr 0
MIC 1
PIC 2
Xcvr 0
FPC 4
CPU
MIC 0
PIC 0
Xcvr 0
MIC 1
PIC 2
Xcvr 0
FPC 5
CPU
MIC 0
PIC 0
Xcvr 0
Xcvr 1
PIC 1
MIC 1
PIC 2
Xcvr 0
Xcvr 1
PIC 3
Xcvr 5
Xcvr 9
Fan Tray
REV 05
750-033199
BUILTIN
REV 01
740-032210
REV 02
750-033199
BUILTIN
REV 01
740-032210
REV 12.3.09 750-033205
REV 03
711-035209
REV 05
750-033199
BUILTIN
NON-JNPR
REV 10
750-033199
BUILTIN
REV 01
740-035329
REV 06
750-024884
REV 02
711-028401
REV 05
750-028387
BUILTIN
REV 01
740-014289
REV 02
740-014289
BUILTIN
REV 22
750-028392
REV 01
REV 01
REV 01
REV 02
BUILTIN
740-011613
740-011613
BUILTIN
740-013111
740-013111
YR3269
BUILTIN
ULH0KG3
YG3245
BUILTIN
ULH0KGF
YR9437
YT5857
YR3295
BUILTIN
X12000187
YX4518
BUILTIN
X12J00008
JW9769
JR6158
JR6197
BUILTIN
T07M71112
T08L85610
BUILTIN
YM0053
1X100GE CFP
1X100GE CFP
CFP-100G-LR4
1X100GE CFP
1X100GE CFP
CFP-100G-LR4
MPCE Type 3D
HMPC PMB 2G
1X100GE CFP
1X100GE CFP
CFP-100G-SR10
1X100GE CFP
1X100GE CFP
CFP-100G-SR10
MPC Type 2 3D EQ
MPC PMB 2G Proto
3D 4x 10GE XFP
2x 10GE XFP
XFP-10G-SR
XFP-10G-SR
2x 10GE XFP
3D 20x 1GE(LAN) SFP
BUILTIN
AM0703S005B
E07L01352
BUILTIN
6500217
8499527
10x 1GE(LAN) SFP

SFP-SX
SFP-SX
10x 1GE(LAN) SFP
SFP-T
SFP-T
Left Fan Tray
The PIC number for MIC 1 always starts from 2 (even if the first MIC is a 1X100GE CFP or
a legacy MIC).

(QFX3500 Switches)

detail (QFX3500
Switches)
578
user@switch> show chassis hardware

Hardware inventory:
Item
Version Part number
Chassis
Routing Engine 0
BUILTIN
FPC 0
REV 04
750-044071
CPU
BUILTIN
PIC 0
BUILTIN
PIC 1
BUILTIN
MGMT BRD
REV 02
750-044063
Xcvr 0
REV 01
740-011614
Xcvr 1
REV 02
740-013111
Power Supply 0
Rev 04
740-032091
Power Supply 1
REV 00
740-041741
Fan Tray 0
Front Airlfow
Fan Tray 1
Front Airlfow
Fan Tray 2
Front Airlfow
Serial number
BUILTIN
BBAR3902
BUILTIN
BUILTIN
BUILTIN
BBAR0398
AC0946S0BD1
A281922
UI00677
VJ00162
Description
QFX3500
QFX Routing Engine
QFX3500-48S4Q-AFI
FPC CPU
48x 10G-SFP+
15x 10G-SFP+
QFX3500-MGMT-SFP-AFO
SFP-LX10
SFP-T
JPSU-650W-AC-AFI
JPSU-650W-AC-AFO
QFX Fan Tray, Back to
user@switch> show chassis hardware detail

Hardware inventory:
Item
Chassis
JN000TEST5
Routing Engine 0
BUILTIN
BUILTIN
Description
QFX3500
QFX Routing Engine
FPC 0
REV 05
750-036931
EE0823
CPU
BUILTIN
BUILTIN
PIC 0
BUILTIN
BUILTIN
Xcvr 0
REV 01
740-030589
S99E270079
Xcvr 1
REV 01
740-030589
S9AK450099
Xcvr 2
REV 01
740-030589
S99E270078
Xcvr 3
REV 01
740-030589
S9AK450098
Xcvr 4
REV 01
740-030589
S99E270075
Xcvr 5
REV 01
740-030589
S9AK450093
Xcvr 6
REV 01
740-030589
S9AK450097
Xcvr 7
REV 01
740-030589
S9AK450095
Xcvr 8
REV 01
740-030589
S99E270072
Xcvr 9
REV 01
740-030589
S99E270073
Xcvr 10
REV 01
740-030589
S99E270080
Xcvr 11
REV 01
740-030589
S9AK450169
Xcvr 12
REV 01
740-030589
S99E270076
Xcvr 13
REV 01
740-030589
S9AK450167
Xcvr 14
REV 01
740-030589
S9AK450170
Xcvr 15
REV 01
740-030589
S9AK450166
Xcvr 16
REV 01
740-030589
S9AK450092
Xcvr 17
REV 01
740-030589
S9AK450163
Xcvr 18
REV 01
740-030589
S9AK450094
Xcvr 19
REV 01
740-030589
S9AK450100
Xcvr 20
REV 01
740-030589
S9AK450168
Xcvr 21
REV 01
740-030589
S9AK450165
Xcvr 22
REV 01
740-030589
S9AK450073
Xcvr 23
REV 01
740-030589
S9AK450164
Xcvr 24
REV 01
740-030589
S9AK450074
Xcvr 25
REV 01
740-030589
SA62270195
Xcvr 26
REV 01
740-030589
S9AK450078
Xcvr 27
REV 01
740-030589
S9AK450024
Xcvr 28
REV 01
740-030589
S9AK450027
Xcvr 29
REV 01
740-030589
S9AK450080
Xcvr 30
REV 01
740-030589
S9AK450030
Xcvr 31
REV 01
740-030589
S9AK450025
Xcvr 32
REV 01
740-030589
S9AK450023
Xcvr 33
REV 01
740-030589
S9AK450075
Xcvr 34
REV 01
740-030589
S9AK450161
Xcvr 35
REV 01
740-030589
S9AK450071
Xcvr 36
REV 01
740-030589
S9AK450072
Xcvr 37
REV 01
740-030589
S9AK450022
Xcvr 38
REV 01
740-030589
S9AK450021
Xcvr 39
REV 01
740-030589
S9AK450175
Xcvr 40
REV 01
740-030589
S9AK450162
Xcvr 41
REV 01
740-030589
S99E270074
Xcvr 42
REV 01
740-030589
S9AK450174
Xcvr 43
REV 01
740-030589
S9AK450077
Xcvr 44
REV 01
740-030589
S9AK450076
Xcvr 45
REV 01
740-030589
S9AK450026
Xcvr 46
REV 01
740-030589
S9AK450079
Xcvr 47
REV 01
740-030589
S9AK450029
PIC 1
BUILTIN
BUILTIN
Xcvr 1
REV 01
740-032986
QA170087
Xcvr 4
REV 01
740-032986
QA360442
Xcvr 8
REV 01
740-032986
QA170091
Xcvr 12
REV 01
740-032986
QA170042
MGMT BRD
REV 08
750-036946
EE0731
Power Supply 0
Rev 04
740-032091
UI00690
Power Supply 1
Rev 04
740-032091
UI00679
QFX3500-48S4Q-AFI
FPC CPU
48x 10G-SFP+
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
15x 10G-SFP+
QSFP+-40G-SR4
QSFP+-40G-SR4
QSFP+-40G-SR4
QSFP+-40G-SR4
QFX3500-MB
QFX PS 650W AC
QFX PS 650W AC
579
Fan Tray 0
Fan Tray 1
QFX Fan Tray

QFX Fan Tray

models (QFX3500
Switches)
user@switch> show chassis hardware models

Hardware inventory:
Item
Routing Engine 0
BUILTIN
BUILTIN
FPC 0
REV 02
711-032234
EC4074
Power Supply 0
PSMI 2C 11-d65800
--

clei-models (QFX3500
Switches)
user@switch> show chassis hardware clei-models

Hardware inventory:
Item
Routing Engine 0
BUILTIN
FPC 0
REV 02
711-032234
Power Supply 0
PSMI 2C 11-d65800

interconnect-device
(QFabric Systems)
user@switch> show chassis hardware interconnect-device interconnect1

Hardware inventory:
Item
Description
Chassis
REV 07
QFX_olive
Midplane
REV 07
750-021261
BH0208188289
QFX Midplane
CB 0
REV 07
750-021261
BH0208188289
QFXIC08-CB4S

Systems)
user@switch> show chassis hardware node-device node1

Routing Engine 0
BUILTIN
BUILTIN
QFX Routing Engine
node1
REV 05
711-032234
ED3694
QFX3500-48S4Q-AFI
CPU
PIC 0
Xcvr 8
...

(PTX5000 Packet
Transport Switch)
580
REV 01
BUILTIN
BUILTIN
740-030658

Hardware inventory:
Item
Version Part number
Chassis
Midplane
REV 03
711-031896
FPM
REV 08
760-030647
PDU 0
Rev 05
740-032019
PSM 0
Rev 05
740-032022
PSM 1
Rev 04
740-032022
PSM 2
Rev 04
740-032022
PSM 3
Rev 05
740-032022
CCG 0
REV 04
750-030653
CCG 1
REV 04
750-030653
740-026942
740-026942
CB 0
REV 08
750-030625
CB 1
REV 08
750-030625
FPC 0
REV 18
750-036844
CPU
REV 12
711-030686
FPC 2
REV 13
750-036844
CPU
REV 09
711-030686
PIC 0
REV 14
750-031913
Xcvr 0
REV 01
740-031980
FRU model number
FRU model number
BUILTIN
BUILTIN
AD0946A028B
FPC CPU
48x 10G-SFP+
SFP+-10G-USR
Serial number
JN11D1FD7AJA
ABAC5589
EG1679
ZE00006
ZJ00018
ZC00052
ZD00051
ZJ00060
EG3703
EG3698
P737A-002231
P737A-002438
EG5519
EG5516
EJ3080
EJ3260
EG5065
EG4082
EG5127
143363A00240
Description
PTX5000
Midplane-8S
Front Panel Display
DC Power Dist Unit
DC 12V Power Supply
DC 12V Power Supply
DC 12V Power Supply
DC 12V Power Supply
Clock Generator
Clock Generator
RE-DUO-2600
RE-DUO-2600
Control Board
Control Board
FPC
SNG PMB
FPC
SNG PMB
24x 10GE(LAN) SFP+
SFP+-10G-SR
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
FPC 3
CPU
PIC 1
FPC 5
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
FPC 6
CPU
FPC 7
CPU
SPMB 0
SPMB 1
SIB 0
SIB 1
SIB 2
SIB 3
SIB 4
SIB 5
SIB 6
SIB 7
SIB 8
Fan Tray
Fan Tray
Fan Tray
1
2
3
4
6
7
8
10
11
12
14
15
16
19
21
22
23
0
1
2
5
6
7
10
11
12
15
16
18
19
22
23
0
1
0
1
2
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
13
09
10
06
740-031981
740-031980
740-031981
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-021309
740-031980
740-031981
740-031980
750-036844
711-030686
750-031903
750-036844
UK90PZ1
AD1141A04XH
UK90Q46
AD1141A04X4
B11H02560
B11C01589
AD1141A04XF
123363A01094
AK80LKF
183363A01528
193363A01079
AK80MC8
AJC0BHC
J08D26856
AK80KCT
UK90PZL
AK80N1V
EG5074
EG4064
EG0325
EH3198
SFP+-10G-LR
SFP+-10G-SR
SFP+-10G-LR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-LR
SFP+-10G-SR
SFP+-10G-LR
SFP+-10G-SR
FPC
SNG PMB
SNG Load
FPC
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
14
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
08
01
01
18
12
18
12
10
09
07
07
07
07
07
07
07
07
07
04
04
02
750-031913
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-021309
740-031980
740-031980
750-036710
740-034554
740-034554
750-036844
711-030686
750-036844
711-030686
711-030686
711-030686
750-030631
750-030631
750-030631
750-030631
750-030631
750-030631
750-030631
750-030631
750-030631
760-032784
760-030642
760-030642
EG5134
AK80LBH
B11B03724
AK80FMH
B11J00818
193363A00743
B11B06125
B11H02529
AK80LFB
193363A01061
B11J00687
193363A00738
AK80MQX
J08C17257
B11J00730
AK80KEE
EG3105
B260HLT
B11C02847
EJ4391
EJ3257
EJ4382
EJ3238
EG5418
EG5373
EG4858
EG4872
EG4866
EG6011
EG4907
EG4879
EG4864
EG4899
EG4880
EG1496
EG1335
ED4952
24x 10GE(LAN) SFP+

SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-LR
SFP+-10G-SR
SFP+-10G-SR
2x 40GE CFP
CFP-40G-LR4
CFP-40G-LR4
FPC
SNG PMB
FPC
SNG PMB
SNG PMB
SNG PMB
SIB-I-8S
SIB-I-8S
SIB-I-8S
SIB-I-8S
SIB-I-8S
SIB-I-8S
SIB-I-8S
SIB-I-8S
SIB-I-8S
Vertical Fan Tray
Horizontal Fan Tray
Horizontal Fan Tray
user@switch> show chassis hardware clei-models
581

clei-models (PTX5000
Packet Transport
Switch)

detail (PTX5000
582
Hardware inventory:
Item
Version
FPM
REV 08
PDU 0
Rev 05
PSM 0
Rev 05
PSM 1
Rev 04
PSM 2
Rev 04
PSM 3
Rev 05
CCG 0
REV 04
CCG 1
REV 04
CB 0
REV 08
CB 1
REV 08
FPC 0
REV 18
FPC 2
REV 13
PIC 0
REV 14
FPC 3
REV 13
FPC 5
PIC 0
REV 14
FPC 6
REV 18
FPC 7
REV 18
SIB 0
REV 07
SIB 1
REV 07
SIB 2
REV 07
SIB 3
REV 07
SIB 4
REV 07
SIB 5
REV 07
SIB 6
REV 07
SIB 7
REV 07
SIB 8
REV 07
Fan Tray 1
REV 04
Part number
760-030647
740-032019
740-032022
740-032022
740-032022
740-032022
750-030653
750-030653
740-026942
740-026942
750-030625
750-030625
750-036844
750-036844
750-031913
750-036844
CLEI code
PROTOXCLEI
IPUPAHLKAA
IPUPAHNKAA
032022XXXX
032022XXXX
IPUPAHNKAA
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
FRU model number

CRAFT-PTX5000-S
PWR-SAN-PDU-DC
PSM-PTX-DC-120-S
PWR-SAN-12-DC
PWR-SAN-12-DC
PSM-PTX-DC-120-S
CCG-PTX-S
CCG-PTX-S
RE-DUO-C2600-16G-S
RE-DUO-C2600-16G-S
CB-PTX-S
CB-PTX-S
FPC-PTX-P1-A
FPC-PTX-P1-A
P1-PTX-24-10GE-SFPP
FPC-PTX-P1-A
750-031913
750-036844
750-036844
750-030631
750-030631
750-030631
750-030631
750-030631
750-030631
750-030631
750-030631
750-030631
760-030642
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
P1-PTX-24-10GE-SFPP
FPC-PTX-P1-A
FPC-PTX-P1-A
SIB-I-PTX5008
SIB-I-PTX5008
SIB-I-PTX5008
SIB-I-PTX5008
SIB-I-PTX5008
SIB-I-PTX5008
SIB-I-PTX5008
SIB-I-PTX5008
SIB-I-PTX5008
FAN-PTX-H-S
user@switch> show chassis hardware detail

Hardware inventory:
Item
Description
Packet Transport
Switch)
Chassis
Midplane
FPM
PDU 0
PSM 0
PSM 1
PSM 2
PSM 3
CCG 0
CCG 1
Routing Engine 0
ad0
3823 MB
ad1
62720 MB
Routing Engine 1
ad0
3823 MB
ad1
62720 MB
CB 0
CB 1
FPC 0
CPU
FPC 2
CPU
PIC 0
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
Xcvr 4
Xcvr 6
Xcvr 7
Xcvr 8
Xcvr 10
Xcvr 11
Xcvr 12
Xcvr 14
Xcvr 15
Xcvr 16
Xcvr 19
Xcvr 21
Xcvr 22
Xcvr 23
FPC 3
CPU
PIC 1
FPC 5
CPU
PIC 0
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 5
Xcvr 6
Xcvr 7
Xcvr 10
Xcvr 11
Xcvr 12
Xcvr 15
Xcvr 16
Xcvr 18
Xcvr 19
Xcvr 22
REV 03
REV 08
Rev 05
Rev 05
Rev 04
Rev 04
Rev 05
REV 04
REV 04
REV 05
SMART
SMART
REV 06
SMART
SMART
REV 08
REV 08
REV 18
REV 12
REV 13
REV 09
REV 14
REV 01
REV 01
REV 01
REV 01
REV 01
REV 01
REV 01
REV 01
REV 01
REV 01
REV 01
REV 01
REV 01
REV 01
REV 01
REV 01
REV 01
REV 01
REV 13
REV 09
REV 10
REV 06
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
14
01
01
01
01
01
01
01
01
01
01
01
01
01
01
JN11D1FD7AJA
PTX5000
ABAC5589
Midplane-8S
EG1679
Front Panel Display
ZE00006
DC Power Dist Unit
ZJ00018
DC 12V Power Supply
ZC00052
DC 12V Power Supply
ZD00051
DC 12V Power Supply
ZJ00060
DC 12V Power Supply
EG3703
Clock Generator
EG3698
Clock Generator
P737A-002231
RE-DUO-2600
CF
201006190039C02DC02D Compact Flash
Lite SATA Drive 2011042300CF4C6B4C6B Disk 1
740-026942
P737A-002438
RE-DUO-2600
CF
20100619053455F055F0 Compact Flash
Lite SATA Drive 20110423000AE8E7E8E7 Disk 1
750-030625
EG5519
Control Board
750-030625
EG5516
Control Board
750-036844
EJ3080
FPC
711-030686
EJ3260
SNG PMB
750-036844
EG5065
FPC
711-030686
EG4082
SNG PMB
750-031913
EG5127
24x 10GE(LAN) SFP+
740-031980
143363A00240
SFP+-10G-SR
740-031981
UK90PZ1
SFP+-10G-LR
740-031980
AD1141A04XH
SFP+-10G-SR
740-031981
UK90Q46
SFP+-10G-LR
740-031980
AD1141A04X4
SFP+-10G-SR
740-031980
B11H02560
SFP+-10G-SR
740-031980
B11C01589
SFP+-10G-SR
740-031980
AD1141A04XF
SFP+-10G-SR
740-031980
123363A01094
SFP+-10G-SR
740-031980
AK80LKF
SFP+-10G-SR
740-031980
183363A01528
SFP+-10G-SR
740-031980
193363A01079
SFP+-10G-SR
740-031980
AK80MC8
SFP+-10G-SR
740-031980
AJC0BHC
SFP+-10G-SR
740-021309
J08D26856
SFP+-10G-LR
740-031980
AK80KCT
SFP+-10G-SR
740-031981
UK90PZL
SFP+-10G-LR
740-031980
AK80N1V
SFP+-10G-SR
750-036844
EG5074
FPC
711-030686
EG4064
SNG PMB
750-031903
EG0325
SNG Load
750-036844
EH3198
FPC
711-031896
760-030647
740-032019
740-032022
740-032022
740-032022
740-032022
750-030653
750-030653
740-026942
750-031913
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-021309
740-031980
EG5134
AK80LBH
B11B03724
AK80FMH
B11J00818
193363A00743
B11B06125
B11H02529
AK80LFB
193363A01061
B11J00687
193363A00738
AK80MQX
J08C17257
B11J00730
24x 10GE(LAN) SFP+

SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-LR
SFP+-10G-SR
583
Xcvr
PIC 1
Xcvr
Xcvr
FPC 6
CPU
FPC 7
CPU
SPMB 0
SPMB 1
SIB 0
SIB 1
SIB 2
SIB 3
SIB 4
SIB 5
SIB 6
SIB 7
SIB 8
Fan Tray
Fan Tray
Fan Tray

models (PTX5000
Packet Transport
Switch)

extensive (PTX5000
584
23
0
1
0
1
2
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
08
01
01
18
12
18
12
10
09
07
07
07
07
07
07
07
07
07
04
04
02
740-031980
750-036710
740-034554
740-034554
750-036844
711-030686
750-036844
711-030686
711-030686
711-030686
750-030631
750-030631
750-030631
750-030631
750-030631
750-030631
750-030631
750-030631
750-030631
760-032784
760-030642
760-030642
AK80KEE
EG3105
B260HLT
B11C02847
EJ4391
EJ3257
EJ4382
EJ3238
EG5418
EG5373
EG4858
EG4872
EG4866
EG6011
EG4907
EG4879
EG4864
EG4899
EG4880
EG1496
EG1335
ED4952
SFP+-10G-SR
2x 40GE CFP
CFP-40G-LR4
CFP-40G-LR4
FPC
SNG PMB
FPC
SNG PMB
SNG PMB
SNG PMB
SIB-I-8S
SIB-I-8S
SIB-I-8S
SIB-I-8S
SIB-I-8S
SIB-I-8S
SIB-I-8S
SIB-I-8S
SIB-I-8S
Vertical Fan Tray
Horizontal Fan Tray
Horizontal Fan Tray
user@switch> show chassis hardware models

Hardware inventory:
Item
FPM
REV 08
760-030647
EG1679
PDU 0
Rev 05
740-032019
ZE00006
PSM 0
Rev 05
740-032022
ZJ00018
PSM 1
Rev 04
740-032022
ZC00052
PSM 2
Rev 04
740-032022
ZD00051
PSM 3
Rev 05
740-032022
ZJ00060
CCG 0
REV 04
750-030653
EG3703
CCG 1
REV 04
750-030653
EG3698
740-026942
P737A-002231
740-026942
P737A-002438
CB 0
REV 08
750-030625
EG5519
CB 1
REV 08
750-030625
EG5516
FPC 0
REV 18
750-036844
EJ3080
FPC 2
REV 13
750-036844
EG5065
PIC 0
REV 14
750-031913
EG5127
FPC 3
REV 13
750-036844
EG5074
FPC 5
PIC 0
REV 14
750-031913
EG5134
FPC 6
REV 18
750-036844
EJ4391
FPC 7
REV 18
750-036844
EJ4382
SIB 0
REV 07
750-030631
EG4858
SIB 1
REV 07
750-030631
EG4872
SIB 2
REV 07
750-030631
EG4866
SIB 3
REV 07
750-030631
EG6011
SIB 4
REV 07
750-030631
EG4907
SIB 5
REV 07
750-030631
EG4879
SIB 6
REV 07
750-030631
EG4864
SIB 7
REV 07
750-030631
EG4899
SIB 8
REV 07
750-030631
EG4880
Fan Tray 1
REV 04
760-030642
EG1335
user@switch> show chassis hardware extensive

Hardware inventory:
Item
FRU model number

CRAFT-PTX5000-S
PWR-SAN-PDU-DC
PSM-PTX-DC-120-S
PWR-SAN-12-DC
PWR-SAN-12-DC
PSM-PTX-DC-120-S
CCG-PTX-S
CCG-PTX-S
RE-DUO-C2600-16G-S
RE-DUO-C2600-16G-S
CB-PTX-S
CB-PTX-S
FPC-PTX-P1-A
FPC-PTX-P1-A
P1-PTX-24-10GE-SFPP
FPC-PTX-P1-A
P1-PTX-24-10GE-SFPP
FPC-PTX-P1-A
FPC-PTX-P1-A
SIB-I-PTX5008
SIB-I-PTX5008
SIB-I-PTX5008
SIB-I-PTX5008
SIB-I-PTX5008
SIB-I-PTX5008
SIB-I-PTX5008
SIB-I-PTX5008
SIB-I-PTX5008
FAN-PTX-H-S
Description
Packet Transport
Switch)

(MX Routers with
[MSB])

extensive (MX Routers
...............
PDU 0
Rev 04
740-032019
UE0003
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
740-032019
S/N:
Assembly ID: 0x043d
Assembly Version:
Date:
11-29-2010
Assembly Flags:
Version:
Rev 04
CLEI Code:
ID: DC Power Dist Unit
FRU Model Number:
I2C Hex Data:
Address 0x00: 7f b0 02 ff 04 3d 04 00 52 65 76 20
Address 0x10: 00 00 00 00 37 34 30 2d 30 33 32 30
Address 0x20: 53 2f 4e 20 55 45 30 30 30 33 00 00
Address 0x30: da ff ff ff ff ff ff ff ff ff ff ff
Address 0x50: 57 52 2d 53 41 4e 2d 50 44 55 2d 44
Address 0x60: 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x70: 00 00 00 a3 ff ff ff ff ff ff ff ff
PSM 0
Rev 04
740-032022
YG00065
Module
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
740-032022
S/N:
Assembly ID: 0x0440
Assembly Version:
Date:
07-30-2010
Assembly Flags:
Version:
Rev 04
CLEI Code:
ID: DC 12V Power Supply Module FRU Model Number:
I2C Hex Data:
Address 0x00: 7f b0 02 ff 04 40 04 00 52 65 76 20
Address 0x10: 00 00 00 00 37 34 30 2d 30 33 32 30
Address 0x20: 53 2f 4e 20 59 47 30 30 30 36 35 00
Address 0x30: da ff ff ff ff ff ff ff ff ff ff ff
Address 0x50: 57 52 2d 53 41 4e 2d 31 32 2d 44 43
Address 0x60: 20 20 20 20 20 20 01 00 ff ff ff ff
Address 0x70: ff ff ff 0c ff ff ff ff ff ff ff ff

Hardware inventory:
Item
Version Part number
Chassis
Midplane
REV 05
710-017414
FPM Board
REV 02
710-017254
PEM 2
Rev 02
740-017343
PEM 3
Rev 02
740-017343
740-015113
CB 0
REV 03
710-021523
FPC 1
REV 11
750-037207
CPU
REV 04
711-038173
MIC 0
REV 06
750-037214
PIC 0
BUILTIN
MIC 1
REV 00
750-037211
PIC 2
BUILTIN
ff ff ff ff
30
31
00
ff
58
43
00
ff
34
39
1d
ff
58
00
00
ff
00 00
00 00
0b 07
ff ff
58 50
00 00
00 00
ff ff
DC 12V Power Supply
0x02
S/N YG00065
04.00
0x00
032022XXXX
PWR-SAN-12-DC
ff ff ff ff
30
32
00
ff
58
20
ff
ff
34
32
1e
ff
58
20
ff
ff
Serial number
JN1100FB1AFB
TR3310
KG1872
QCS0812A00N
QCS0812A00U
1000740938
KF4630
ZW9726
ZW4819
ZW3574
BUILTIN
00
00
07
ff
58
20
ff
ff
00
00
07
ff
50
20
ff
ff
Description
MX480
MX480 Midplane
Front Panel Display
RE-S-1300
MX SCB
AS-MCC
AS-MCC PMB
AS-MSC
AS-MSC
AS-MXC
AS-MXC
BUILTIN
user@switch> show chassis hardware extensive

FPC 1
REV 11
750-037207
ZW9726
Jedec Code:
0x7fb0
EEPROM Version:
DC Power Dist Unit

0x02
S/N UE0003
04.00
0x00
032022XXXX
PWR-SAN-PDU-DC
AS-MCC
0x02
585
with Media Services

Blade [MSB])
586
P/N:
750-037207
S/N:
Assembly ID: 0x0b37
Assembly Version:
Date:
02-17-2012
Assembly Flags:
Version:
REV 11
CLEI Code:
ID: AS-MCC
I2C Hex Data:
Address 0x00: 7f b0 02 ff 0b 37 01 0b 52 45 56 20
Address 0x10: 00 00 00 00 37 35 30 2d 30 33 37 32
Address 0x20: 53 2f 4e 20 5a 57 39 37 32 36 00 00
Address 0x50: 35 30 2d 30 33 37 32 30 37 00 00 00
Address 0x60: 00 00 00 00 00 00 31 31 00 ff ff ff
Address 0x70: ff ff ff 5e ff ff ff ff ff ff ff ff
CPU
REV 04
711-038173
ZW4819
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
711-038173
S/N:
Assembly ID: 0x0b38
Assembly Version:
Date:
12-30-2011
Assembly Flags:
Version:
REV 04
ID: AS-MCC PMB
I2C Hex Data:
Address 0x00: 7f b0 02 ff 0b 38 01 04 52 45 56 20
Address 0x10: 00 00 00 00 37 31 31 2d 30 33 38 31
Address 0x20: 53 2f 4e 20 5a 57 34 38 31 39 00 00
Address 0x50: 31 31 2d 30 33 38 31 37 33 00 00 00
Address 0x60: 00 00 00 00 00 00 30 34 00 ff ff ff
Address 0x70: ff ff ff 60 00 00 00 00 00 00 00 00
MIC 0
REV 06
750-037214
ZW3574
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
750-037214
S/N:
Assembly ID: 0x0a44
Assembly Version:
Date:
02-19-2012
Assembly Flags:
Version:
REV 06
CLEI Code:
ID: AS-MSC
I2C Hex Data:
Address 0x00: 7f b0 02 ff 0a 44 01 06 52 45 56 20
Address 0x10: 00 00 00 00 37 35 30 2d 30 33 37 32
Address 0x20: 53 2f 4e 20 5a 57 33 35 37 34 00 00
Address 0x50: 35 30 2d 30 33 37 32 31 34 00 00 00
Address 0x60: 00 00 00 00 00 00 30 36 00 ff ff ff
Address 0x70: ff ff ff 60 c0 03 e5 f4 00 00 00 00
PIC 0
BUILTIN
BUILTIN
MIC 1
REV 00
750-037211
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
750-037211
Assembly ID: 0x0a43
Assembly Version:
Date:
255-255-65535
Assembly Flags:
Version:
REV 00
ID: AS-MXC
S/N ZW9726
01.11
0x00
PROTOXCLEI
ff ff ff ff
31
30
00
ff
4c
00
ff
ff
31
37
11
ff
45
00
ff
ff
00 00
00 00
02 07
ff ff
49 37
00 00
ff ff
ff ff
AS-MCC-PMB
0x02
S/N ZW4819
01.04
0x00
ff ff ff ff
30
37
00
ff
4c
00
ff
00
34
33
1e
ff
45
00
ff
00
00 00
00 00
0c 07
ff ff
49 37
00 00
ff ff
00 00
AS-MSC
0x02
S/N ZW3574
01.06
0x00
PROTOXCLEI
ff ff ff ff
30
31
00
ff
4c
00
ff
00
36
34
13
ff
45
00
ff
00
00 00
00 00
02 07
ff ff
49 37
00 00
ff ff
00 00
AS-MSC
AS-MXC
0x01
01.00
0x00
Address 0x00:
I2C Hex Data:
Address 0x00:
Address 0x10:
Address 0x20:
Address 0x30:
Address 0x40:
Address 0x50:
Address 0x60:
Address 0x70:
PIC 2
ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
7f
00
00
ff
ff
ff
ff
ff
b0
00
00
ff
ff
ff
ff
ff
01
00
00
ff
ff
ff
ff
ff
ff 0a 43
00 37 35
00 00 00
ff ff ff
ff 00 ff
ff ff ff
ff ff ff
ff c0 02
BUILTIN
01
30
00
ff
ff
ff
ff
e6
00
2d
00
ff
ff
ff
ff
6c
52 45 56
30 33 37
00 00 00
ff ff ff
ff ff ff
ff ff ff
ff ff ff
7f b0 02
BUILTIN
20
32
00
ff
ff
ff
ff
ff
30
31
00
ff
ff
ff
ff
0a
30
31
ff
ff
ff
ff
ff
44
00 00
00 00
ff ff
ff ff
ff ff
ff ff
ff ff
01 06
AS-MXC
587
show chassis mac-addresses

Syntax
Syntax (TX Matrix

Router)

<lcc number | scc>

Router)

Syntax (MX Series

Router)

<all-members>
<local>
<member member-id>
Syntax (MX2010 3D
Universal Edge
Routers)
Syntax (MX2020 3D
Universal Edge
Routers)
Syntax (QFX Series)

<node-group name>
Syntax (ACX Series

Universal Access
Routers)
Release Information
Description
Options
Command introduced before JUNOS Release 7.4.

Command introduced in JUNOS Release 9.0 for EX Series switches.
sfc option introduced for the TX Matrix Plus router in JUNOS Release 9.6.
Display the media access control (MAC) addresses for the router, switch chassis, or
switch.
none(TX Matrix, TX Matrix Plus routers, and the QFX Series) Display the MAC addresses
for the router chassis or switch. On a TX Matrix router, display MAC addresses on the
TX Matrix router and its attached T640 routers. On a TX Matrix Plus router, display
MAC addresses on the TX Matrix Plus router and its attached T1600 routers.
all-members(MX Series routers only) (Optional) Display the MAC addresses for all the
member routers of the Virtual Chassis configuration.

interconnect-device name(QFabric systems only) (Optional) Display the MAC addresses
for the Interconnect device.
588
display MAC addresses for a specified T640 router (or line-card chassis) that is
connected to the TX Matrix Plus router. On a TX Matrix Plus router, display MAC
addresses for a specified T640 router (or line-card chassis) that is connected to the
TX Matrix Plus router. Replace number with a value from 0 through 3.
local(MX Series routers only) (Optional) Display the MAC addresses for the local Virtual
Chassis member.
member member-id(MX Series routers only) (Optional) Display the MAC addresses for
the specified member of the Virtual Chassis configuration. Replace member-id with
a value of 0 or 1.
node-group name(QFabric systems only) (Optional) Display the MAC addresses for
the specified Node group.

scc(TX Matrix routers only) (Optional) Display MAC addresses for the TX Matrix router
(or switch-card chassis).

sfc number(TX Matrix Plus routers only) (Optional) Display MAC addresses for the TX
Matrix Plus router (or switch-fabric chassis).

Required Privilege
Level
Related
Documentation
Output Fields
view
show chassis mac-addresses on page 591

show chassis mac-addresses (MX2010 Router) on page 591
show chassis mac-addresses (MX2020 Router) on page 591
show chassis mac-addresses (TX Matrix Router) on page 591
show chassis mac-addresses (TX Matrix Plus Router) on page 591
show chassis mac-addresses (QFX3500 Switches) on page 592
show chassis mac-addresses interconnect-device (QFabric Systems) on page 592
show chassis mac-addresses node-group (QFabric Systems) on page 592
show chassis mac-addresses (ACX2000 Universal Access Router) on page 593
Table 41 on page 589 lists the output fields for the show chassis mac-addresses command.
Table 41: show chassis mac-addresses Output Fields

Field Name
Field Description
MAC address information

Public base address
Base address of the MAC addresses allocated to this router or

switch.
Public count
Number of allocated public addresses.
589
Table 41: show chassis mac-addresses Output Fields (continued)
590
Field Name
Field Description
Private base address
Base address of the private MAC addresses allocated to this router

or switch.
Private count
Number of allocated private addresses.
Sample Output
show chassis
mac-addresses
user@host> show chassis mac-addresses

MAC address information
Public base address
0:90:69:0:4:0
Public count
1008
0:90:69:0:7:f0
Private count
16
show chassis
mac-addresses
(MX2010 Router)

MAC address information:
Public base address
64:87:88:04:50:00
Public count
1984
64:87:88:04:57:c0
Private count
64
show chassis
mac-addresses
(MX2020 Router)

Public base address
2c:21:72:70:20:00
Public count
4032
2c:21:72:70:2f:c0
Private count
64
show chassis
mac-addresses (TX
Matrix Router)

scc-re0:
-------------------------------------------------------------------------MAC address information:
Public base address
00:05:85:9e:cc:00
Public count
8064
00:05:85:9e:eb:80
Private count
128
lcc0-re0:
Public base address
00:05:85:68:98:00
Public count
2032
00:05:85:68:9f:f0
Private count
16
lcc2-re0:
Public base address
00:05:85:68:78:00
Public count
2032
00:05:85:68:7f:f0
Private count
16
show chassis
mac-addresses (TX
Matrix Plus Router)

sfc0-re0:
Public base address
00:1d:b5:14:00:00
Public count
65023
00:1d:b5:14:fd:ff
Private count
512
lcc0-re0:
591

Public base address
00:1f:12:7a:84:00
Public count
2032
00:1f:12:7a:8b:f0
Private count
16
lcc1-re0:
Public base address
00:22:83:42:48:00
Public count
2032
00:22:83:42:4f:f0
Private count
16
lcc2-re0:
Public base address
00:1f:12:c3:58:00
Public count
2032
00:1f:12:c3:5f:f0
Private count
16
lcc3-re0:
Public base address
00:21:59:ef:b8:00
Public count
2032
00:21:59:ef:bf:f0
Private count
16
show chassis
mac-addresses
(QFX3500 Switches)
user@switch> show chassis mac-addresses

Public base address 02:00:08:00:00:00
Public count 512
Private base address 02:00:00:00:00:00
Private count 64
show chassis
mac-addresses
interconnect-device
(QFabric Systems)
user@switch> show chassis mac-addresses interconnect-device interconnect1

Public base address
00:1f:12:30:9c:c0
Public count
58
00:1f:12:30:9c:fa
Private count
6
show chassis
mac-addresses
user@switch> show chassis mac-addresses node-group NW-NG-0

------------------------
592
node-group (QFabric
Systems)
show chassis
mac-addresses
(ACX2000 Universal
Access Router)
RE:
FC MAC base
FC MAC count
VLAN MAC
EC6007
Base address
Count
EC6008
Base address
Count
00:11:00:00:00:00
2
00:11:00:00:00:09
00:00:01:76:00:00
64
00:22:83:22:52:ae
260
user@switch> show chassis mac-addresses

Public base address
84:18:88:c0:2b:00
Public count
112
84:18:88:c0:2b:70
Private count
16
593
show chassis pic

Syntax
show chassis pic fpc-slot slot-number pic-slot slot-number
Syntax (TX Matrix and

TX Matrix Plus
Routers)

<lcc number>
Syntax (MX Series

Routers)

<all-members>
<local>
<member member-id>
Syntax (MX2010 3D
Universal Edge
Routers)
Syntax (MX2020 3D
Universal Edge
Routers)
Syntax (QFX Series)
show chassis pic

<interconnect-device name (fpc-slot slot-number | pic-slot slot-number)>
<node-device name pic-slot slot-number>
Syntax (ACX Series

Universal Access
Routers)
Release Information
Description
Options

Display status information about the PIC installed in the specified Flexible PIC
Concentrator (FPC) and PIC slot.
fpc-slot slot-numberDisplay information about the PIC in this particular FPC slot:
On a TX Matrix router, if you specify the number of the T640 router by using the
lcc number option (the recommended method), replace slot-number with a value
from 0 through 7. Otherwise, replace slot-number with a value from 0 through 31.
Likewise, on a TX Matrix Plus router, if you specify the number of the T1600 router
by using the lcc number option (the recommended method), replace slot-number
with a value from 0 through 7. Otherwise, replace slot-number with a value from
0 through 31. For example, the following commands have the same result:
user@host> show chassis pic fpc-slot 1 lcc 1 pic-slot 1
user@host> show chassis pic fpc-slot 9 pic-slot 1
594
M120 routers onlyReplace slot-number with a value from 0 through 5.
MX80 routers onlyReplace slot-number with a value from 0 through 1.
Other routersReplace slot-number with a value from 0 through 7.
EX Series switches:
EX3200 switches and EX4200 standalone switchesReplace slot-number with

0.
EX4200 switches in a Virtual Chassis configurationReplace slot-number with

a value from 0 through 9 (switchs member ID).
EX8208 switchesReplace slot-number with a value from 0 through 7 (line

card).
EX8216 switchesReplace slot-number with a value from 0 through 15 (line

card).
QFX Series:
QFX3500 switchesReplace slot-number with 0. In the command output, FPC

refers to a line card. The FPC number equals the slot number for the line card.
QFabric systemsReplace slot-number with any number between 0 and 15. In

the command output, FPC refers to a line card. The FPC number equals the slot
number for the line card.
all-members(MX Series routers only) (Optional) Display PIC information for all member
routers in the Virtual Chassis configuration.

interconnect-device name(QFabric systems only) (Optional) Display PIC information
for a specified Interconnect device.

display PIC information for a specified T640 router (or line-card chassis) that is
connected to the TX Matrix router. On a TX Matrix Plus router, display PIC information
for a specified T1600 router (or line-card chassis) that is connected to the TX Matrix
Plus router. Replace number with a value from 0 through 3.
local(MX Series routers only) (Optional) Display PIC information for the local Virtual
Chassis member.
member member-id(MX Series routers only) (Optional) Display PIC information for the
specified member of the Virtual Chassis configuration. Replace member-id with a

value of 0 or 1.
595
node-device name(QFabric systems only) (Optional) Display PIC information for a
specified Node device.

pic-slot slot-numberDisplay information about the PIC in this particular PIC slot. For
routers, replace slot-number with a value from 0 through 3. For EX3200 and EX4200
switches, replace slot-number with 0 for built-in network interfaces and 1 for interfaces
on uplink modules. For EX8208 and EX8216 switches, replace slot-number with 0.
For the QFX3500 standalone switch and the QFabric system, replace slot-number
with 0 or 1.
Required Privilege
Level
Related
Documentation
596
view
request chassis pic
show chassis hardware on page 484
Configuring the PIC Type
100-Gigabit Ethernet PIC Overview
show chassis pic fpc-slot pic-slot on page 599

show chassis pic fpc-slot pic-slot (PIC Offline) on page 599
show chassis pic fpc-slot pic-slot (FPC Offline) on page 599
show chassis pic fpc-slot pic-slot (FPC Not Present) on page 599
show chassis pic fpc-slot pic-slot (PIC Not Present) on page 599
show chassis pic fpc-slot 3 pic-slot 0 (M120 Router) on page 599
show chassis pic fpc-slot pic-slot (MX960 Router Bidirectional Optics) on page 599
show chassis pic fpc-slot pic-slot (MX480 Router with 100-Gigabit Ethernet
MIC) on page 600
show chassis pic fpc-slot pic-slot (MX240, MX480, MX960 Routers with Application
show chassis pic fpc-slot pic-slot (MX2010 Router) on page 601
show chassis pic fpc-slot pic-slot (MX2020 Router) on page 601
show chassis pic fpc-slot pic-slot (T1600 Router with 100-Gigabit Ethernet
PIC) on page 601
show chassis pic fpc-slot pic-slot lcc (TX Matrix Router) on page 601
show chassis pic fpc-slot pic-slot lcc (TX Matrix Plus Router) on page 601
show chassis pic fpc-slot pic-slot (Next-Generation SONET/SDH SFP) on page 602
show chassis pic fpc-slot pic-slot (12-Port T1/E1) on page 602
show chassis pic fpc-slot 0 pic-slot 1 (4x CHOC3 SONET CE SFP) on page 602
show chassis pic fpc-slot 0 pic-slot 0 (SONET/SDH OC3/STM1 [Multi-Rate] MIC with
SFP) on page 603
show chassis pic fpc-slot 3 pic-slot 0 (8-port Channelized SONET/SDH OC3/STM1
[Multi-Rate] MIC with SFP) on page 603
show chassis pic fpc-slot 5 pic-slot 0 (4-port Channelized SONET/SDH OC3/STM1
[Multi-Rate] MIC with SFP) on page 603
show chassis pic fpc-slot 1 pic-slot 0 (1-port OC192/STM64 MIC with XFP) on page 604
show chassis pic fpc-slot 1 pic-slot 2 (8-port DS3/E3 MIC) on page 604
show chassis pic fpc-slot pic-slot (OTN) on page 604
show chassis pic fpc-slot pic-slot (QFX3500 Switch) on page 604

show chassis pic interconnect-device fpc-slot pic-slot (QFabric Systems) on page 604
show chassis pic node-device fpc-slot pic-slot (QFabric System) on page 604
show chassis pic fpc-slot 0 pic-slot 1 (ACX2000 Universal Access Router) on page 605
show chassis pic FPC-slot 1 PIC-slot 0 (MX Routers with Media Services Blade
[MSB]) on page 606
show chassis pic FPC slot 1, PIC slot 2 (MX Routers with Media Services Blade
[MSB]) on page 606
Output Fields
Table 42 on page 597 lists the output fields for the show chassis pic command. Output
Table 42: show chassis pic Output Fields

Field Name
Field Description
Type
PIC type.
NOTE: On the 1-port OC192/STM64 MICs with the SDH framing
mode, the type is displayed as MIC-3D-1STM64-XFP and with the
SONET framing mode, the type is displayed as MIC-3D-1OC192-XFP.
By default, the 1-port OC192/STM64 MICs displays the type as
MIC-3D-1OC192-XFP.
ASIC type
Type of ASIC on the PIC.
State
Status of the PIC. State is displayed only when a PIC is in the slot.
Online PIC is online and running.
OfflinePIC is powered down.
PIC version
PIC hardware version.
Uptime
How long the PIC has been online.
Package
(Multiservices PICs only) Services package supported: Layer-2 or

Layer-3.
Port Number
Port number for the PIC.
Cable Type
Type of cable connected to the port: LH, LX, or SX.
PIC Port Information

(MX480 Router 100-Gigabit
Ethernet CFP)
Port-level information for the PIC.
PortPort number
Cable typeType of optical transceiver installed.
Fiber typeType of fiber. SM is single-mode.
Xcvr vendorTransceiver vendor name.
Xcvr vendor part numberTransceiver vendor part number.
WavelengthWavelength of the transmitted signal. Uplinks and

downlinks are always 1550 nm. There is a separate fiber for each
direction
597
Table 42: show chassis pic Output Fields (continued)

Field Name
Field Description

(MX960 Router
Bidirectional Optics )
Port-level information for the PIC.
PortPort number
Cable typeType of small form-factor pluggable (SFP) optical

transceiver installed. Uplink interfaces display -U. Down link
interfaces display -D.
Fiber typeType of fiber. SM is single-mode.

(Next-Generation
SONET/SDH SFP)
598
BX10-10-km bidirectional optics.
BX40-40-km bidirectional optics.
SFP-LX-40-km SFP optics.
WavelengthWavelength of the transmitted signal. Uplinks are

always 1310 nm. Downlinks are either 1490 nm or 1550 nm.
Port-level information for the next-generation SONET/SDH SFP

PIC.
PortPort number.
Cable typeType of small form-factor pluggable (SFP) optical

transceiver installed.
Fiber typeType of fiber: SM (single-mode) or MM (multimode).
WavelengthWavelength of the transmitted signal.

Next-generation SONET/SDH SFPs use 1310 nm.
Multirate Mode
Rate-selectabilty status for the MIC: Enabled or Disabled.
Channelization
Indicates whether channelization is enabled or disabled on the

DS3/E3 MIC.
Sample Output
show chassis pic
fpc-slot pic-slot

PIC fpc slot 2 pic slot 0 information:
Type
ASIC type
H chip
State
Online
PIC version
1.1
Uptime
1 day, 50 minutes, 58 seconds
PIC Port Information:
Port
Cable
Xcvr
Xcvr Vendor
Number
Type
Vendor Name
Part Number
0
GIGE 1000EX
FINISAR CORP.
FTRJ8519P1BNL-J3
1
GIGE 1000EX
FINISAR CORP.
FTRJ-8519-7D-JUN
show chassis pic

fpc-slot pic-slot
(PIC Offline)

State
Offline
show chassis pic

fpc-slot pic-slot
(FPC Offline)

FPC 1 is not online
show chassis pic

fpc-slot pic-slot
(FPC Not Present)

FPC slot 4 is empty
show chassis pic

fpc-slot pic-slot
(PIC Not Present)

FPC 5, PIC 2 is empty
show chassis pic

fpc-slot 3 pic-slot 0
(M120 Router)

PC slot 3, PIC slot 0 information:
Type
ASIC type
IQ GE 2 VLAN-TAG FPGA
State
Online
PIC version
1.16
Uptime
3 hours, 3 minutes
PIC Port Information:
Port
Cable
Number
Type
0
GIGE 1000SX
1
GIGE 1000SX
show chassis pic

fpc-slot pic-slot
Xcvr
Vendor Name
FINISAR CORP.
FINISAR CORP.
Xcvr Vendor
Part Number
FTRJ8519P1BNL-J3
FTRJ-8519-7D-JUN

FPC slot 4, PIC slot 1 information:
Type
10x 1GE(LAN)
599
(MX960 Router
Bidirectional Optics)
State
PIC version
Uptime
Online
0.0
PIC port information:

Port
0
1
2
3
4
5
6
7
8
9
show chassis pic

fpc-slot pic-slot
(MX480 Router with
MIC)
Fiber
Cable type
type
SFP-1000BASE-BX10-D SM
SFP-1000BASE-BX10-U SM
Xcvr vendor
part number
SBP6H44-J3-BW-49
SBP6H44-J3-BW-49
SBP6H44-J3-BW-49
TRXBG1LXDBVM2-JW
TRXBG1LXDBVM2-JW
SBP6H44-J3-BW-31
SBP6H44-J3-BW-31
TRXBG1LXDBBMH-J1
TRXBG1LXDBBMH-J1
SBP6H44-J3-BW-31
Xcvr vendor
SumitomoElectric
SumitomoElectric
SumitomoElectric
OCP
OCP
SumitomoElectric
SumitomoElectric
OCP
OCP
SumitomoElectric
Wavelength
1490 nm
1490 nm
1490 nm
1490 nm
1490 nm
1310 nm
1310 nm
1310 nm
1310 nm
1310 nm

Type
1X100GE CFP
State
Online
PIC version
2.10
Uptime
Fiber
Port Cable type
0
100GBASE LR4
type
SM
Xcvr vendor
Xcvr vendor
FINISAR CORP.
part number
FTLC1181RDNS-J3
Wavelength
1310 nm
Xcvr vendor
firmware version
1.8
show chassis pic

fpc-slot pic-slot
(MX240, MX480,
MX960 Routers with
600
user@host>show chassis pic fpc-slot 1 pic-slot 2

Type
AS-MXC
State
Online
PIC version
1.0
Uptime
Modular Line Card)
show chassis pic

fpc-slot pic-slot
(MX2010 Router)

Type
1X100GE CFP
State
Online
PIC version
0.0
Uptime
14 hours, 51 seconds
show chassis pic

fpc-slot pic-slot
(MX2020 Router)

Type
4x 10GE(LAN) SFP+
State
Online
PIC version
0.0
Uptime
1 day, 11 hours, 26 minutes, 36 seconds
Fiber
Port Cable type
Firmware
0
10GBASE SR
show chassis pic

fpc-slot pic-slot
(T1600 Router with
PIC)
Xcvr vendor
Wave-
Xcvr
type
Xcvr vendor
part number
length
MM
SumitomoElectric
SPP5200SR-J6-M
850 nm
0.0
10GBASE SR
MM
SumitomoElectric
SPP5200SR-J6-M
850 nm
0.0
10GBASE SR
MM
SumitomoElectric
SPP5200SR-J6-M
850 nm
0.0
10GBASE SR
MM
SumitomoElectric
SPP5200SR-J6-M
850 nm
0.0
user@host> run show chassis pic fpc-slot 3 pic-slot 1

Type
100GE SLOT1
ASIC type
Brooklyn 100GE FPGA
State
Online
PIC version
1.3
Uptime
Port
0
Cable type
100GBASE LR4
Fiber
type Xcvr vendor
SM
Opnext Inc.
Xcvr vendor
part number
TRC5E20ENFSF000F
Wavelength
1310 nm
show chassis pic

fpc-slot pic-slot lcc
(TX Matrix Router)
user@host> show chassis pic fpc-slot 1 pic-slot 1 lcc 0

lcc0-re0:
-------------------------------------------------------------------------PIC fpc slot 1 pic slot 1 information:
Type
4x OC-3 SONET, SMIR
ASIC type
D chip
State
Online
PIC version
1.2
Uptime
show chassis pic

fpc-slot pic-slot lcc
user@host> show chassis pic pic-slot 0 fpc-slot 8

lcc0-re0:
--------------------------------------------------------------------------
601
(TX Matrix Plus

Router)

Type
1x 10GE(LAN/WAN)
State
Online
Uptime
show chassis pic

fpc-slot pic-slot
(Next-Generation
SONET/SDH SFP)
Port
Cable type
Fiber
type Xcvr vendor
part number
Wavelength
0
0
10GBASE ZR
10GBASE ZR
SM
SM
TRF7061BN-LF150
FTRX-1811-3-J2
1550 nm
1550 nm
Opnext Inc.
FINISAR CORP.

Type
ASIC type
D FPGA
State
Online
PIC version
1.3
Uptime
1 day, 50 minutes, 4 seconds
Port
Cable type
Fiber
type Xcvr vendor
Xcvr vendor
part number
Wavelength
0
1
2
3
OC48 short reach

OC3 short reach
OC3 short reach
OC12 inter reach
SM
MM
MM
SM
FTRJ1321P1BTL-J2
TRPA03MM3BAS-JE
TRXA03MM3BAS-JW
FTLF1322P1BTR
1310
1310
1310
1310
FINISAR CORP.
OCP
OCP
FINISAR CORP.
show chassis pic

fpc-slot pic-slot
(12-Port T1/E1)

Type
12x T1/E1 CE
State
Online
PIC version
1.1
CPU load average
1 percent
Interrupt load average
0 percent
Total DRAM size
128 MB
Memory buffer utilization
100 percent
Memory heap utilization
4 percent
Uptime
Internal Clock Synchronization
Normal
show chassis pic

fpc-slot 0 pic-slot 1 (4x

Type
4x CHOC3 SONET CE SFP
602
nm
nm
nm
nm
CHOC3 SONET CE
SFP)
State
PIC version
1.3
CPU load average
1
Interrupt load average
0
Total DRAM size
128
Memory buffer utilization
99
Memory heap utilization
4
Uptime
1
Internal Clock Synchronization
Online
percent
percent
MB
percent
percent
day, 22 hours, 55 minutes, 37 seconds
Normal

Port
0
1
3
show chassis pic

(SONET/SDH
OC3/STM1
[Multi-Rate] MIC with
SFP)
Cable type
OC3 short reach
OC3 short reach
OC3 long reach
Fiber
type
MM
MM
SM
Xcvr vendor
AVAGO
AVAGO
OPNEXT INC
Xcvr vendor
part number
HFBR-57E0P-JU2
HFBR-57E0P-JU2
TRF5456AVLB314
Wavelength
n/a
n/a
1310 nm

Type
MIC-3D-8OC3OC12-4OC48
State
Online
PIC version
1.8
Uptime
Port Cable type
1
OC12 inter reach
7
OC12 inter reach
Multirate Mode
show chassis pic

(8-port Channelized
SONET/SDH
OC3/STM1
SFP)
Xcvr vendor
part number
FTRJ1322P1BTR-J3
FTRJ1322P1BTR-J3
Wavelength
1310 nm
1310 nm

Type
MIC-3D-8CHOC3-4CHOC12
State
Online
PIC version
1.9
Uptime
Port
0
1
2
4
5
6
7
show chassis pic

(4-port Channelized
SONET/SDH
OC3/STM1
Fiber
type Xcvr vendor
SM
FINISAR CORP
SM
FINISAR CORP
Enabled
Cable type
OC12 short
OC12 short
OC12 inter
OC12 short
OC12 short
OC12 short
OC12 short
reach
reach
reach
reach
reach
reach
reach
Fiber
type
SM
SM
SM
SM
SM
SM
SM
Xcvr vendor
FINISAR CORP.
FINISAR CORP.
FINISAR CORP.
FINISAR CORP.
FINISAR CORP.
FINISAR CORP.
FINISAR CORP.
Xcvr vendor
part number
FTRJ1322P1BTR-J3
FTRJ1322P1BTR-J3
FTRJ1322P1BTR-J2
FTRJ1322P1BTR-J3
FTRJ1322P1BTR-J3
FTRJ1322P1BTR-J3
FTRJ1322P1BTR-J3
Wavelength
1310 nm
1310 nm
1310 nm
1310 nm
1310 nm
1310 nm
1310 nm

Type
MIC-3D-4CHOC3-2CHOC12
State
Online
PIC version
1.9
Uptime
1 hour, 21 minutes
603

SFP)

Port
1
2
3
show chassis pic

(1-port OC192/STM64
MIC with XFP)
Cable type
OC12 inter reach
OC12 inter reach
OC12 short reach
Fiber
type
SM
SM
SM
Xcvr vendor
FINISAR CORP.
FINISAR CORP.
FINISAR CORP.
Xcvr vendor
part number
FTRJ1322P1BTR-J3
FTRJ1322P1BTR-J3
FTRJ1322P1BTR-J3
Wavelength
1310 nm
1310 nm
1310 nm

Type
MIC-3D-1OC192-XFP
State
Online
PIC version
1.2
Uptime
Port
0
Fiber
Cable type
type Xcvr vendor
OC192 short reach n/a
FINISAR CORP.
Xcvr vendor
part number
FTLX1412M3BCL-J3
Wavelength
1310 nm
show chassis pic

(8-port DS3/E3 MIC)

Type
MIC-3D-8DS3-E3
State
Online
PIC version
1.10
Uptime
4 days, 1 hour, 29 minutes, 19 seconds
Channelization Mode
Disabled
show chassis pic

fpc-slot pic-slot (OTN)

Type
1x10GE(LAN),OTN
ASIC type
H chip
State
Online
PIC version
1.0
Uptime
show chassis pic

fpc-slot pic-slot
(QFX3500 Switch)
user@switch> show chassis pic fpc-slot 0 pic-slot 0

Type 48x 10G-SFP+ Builtin
State Online
Uptime 3 days, 3 hours, 5 minutes, 20 seconds
show chassis pic

interconnect-device
fpc-slot pic-slot
(QFabric Systems)
user@switch> show chassis pic interconnect-device interconnect1 fpc-slot 9 pic-slot 0

Type
16x 40G-GEBuiltin
State
Online
Uptime
show chassis pic

node-device fpc-slot
user@switch> show chassis pic node-device node1 pic-slot 0

FPC slot node1, PIC slot 0 information:
Type
48x 10G-SFP+Builtin
604
pic-slot (QFabric
System)
State
Uptime
Online

Port
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
show chassis pic

Cable type
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
Fiber
type
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
Xcvr vendor
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
Xcvr vendor
part number
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
Wavelength
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm

Type
8x 1GE(LAN) RJ45 Builtin
605
(ACX2000 Universal
Access Router)
State
Uptime
Online
show chassis pic

FPC-slot 1 PIC-slot 0
(MX Routers with
[MSB])

Type
AS-MSC
State
Online
PIC version
1.6
Uptime
show chassis pic FPC

slot 1, PIC slot 2 (MX
Routers with Media
Services Blade [MSB])

Type
AS-MXC
State
Online
PIC version
1.0
Uptime
606
show chassis routing-engine

Syntax

<bios | slot>
Syntax (EX Series

Switches)

<slot>
Syntax (T Series
routers)

<bios | slot>
Syntax (TX Matrix

Routers)

<bios | slot>
<lcc number | scc>

Routers)

<bios | slot>
Syntax (QFX Series)

<node-device name>
Syntax (MX Series

Routers)

<bios | slot>
<all-members>
<local>
<member member-id>
Syntax (MX2010 3D
Universal Edge
Routers)

<bios | slot>
Syntax (MX2020 3D
Universal Edge
Routers)

<bios | slot>
Syntax (ACX Series

Universal Access
Routers)
Release Information
Description

sfc option introduced for the TX Matrix Plus router in Junos OS Release in 9.6.
Display the status of the Routing Engine.
607
Options
noneDisplay information about one or more Routing Engines. On a TX Matrix router,
display information about all Routing Engines on the TX Matrix router and its attached
T640 routers. On a TX Matrix Plus router, display information about all Routing
Engines on the TX Matrix Plus router and its attached T1600 routers.
all-members(MX Series routers only) (Optional) Display Routing Engine information
for all members of the Virtual Chassis configuration.

bios(Optional) Display the (BIOS) firmware version.
interconnect-device number(QFabric systems only) (Optional) Display Routing Engine
information for a specified Interconnect device.

display Routing Engine information for a specified T640 router (or line-card chassis)
that is connected to the TX Matrix router. On a TX Matrix Plus router, display Routing
Engine information for a specified T1600 router (or line-card chassis) that is
connected to the TX Matrix Plus router. Replace number with a value from 0 through
3.
local(MX Series routers only) (Optional) Display Routing Engine information for the
local Virtual Chassis member.

member member-id(MX Series routers only) (Optional) Display Routing Engine
information for the specified member of the Virtual Chassis configuration. For an MX
Series Virtual Chassis, replace member-id with a value of 0 or 1.
node-device number(QFabric systems only) (Optional) Display Routing Engine
information for a specified Node device.

scc(TX Matrix routers only) (Optional) Display Routing Engine information for the TX
Matrix router (or switch-card chassis).

sfc number(TX Matrix Plus routers only) (Optional) Display Routing Engine information
for the TX Matrix Plus router (or switch-fabric chassis). Replace number with 0.
slot(Systems with multiple Routing Engines) (Optional) Display information for an
individual Routing Engine. Replace slot with 0 or 1. For QFX3500 switches, there is
only one Routing Engine, so you do not need to specify the slot number.
Required Privilege
Level
Related
Documentation
608
view
request chassis routing-engine master
Configuring Routing Engine Redundancy
Switching the Global Master and Backup Roles in a Virtual Chassis Configuration
show chassis routing-engine (M5 Router) on page 612


show chassis routing-engine (MX240 Router) on page 615
show chassis routing-engine (T320 router) on page 617
show chassis routing-engine (TX Matrix Router) on page 620
show chassis routing-engine lcc (TX Matrix Router) on page 621
show chassis routing-engine bios (TX Matrix Router) on page 621
show chassis routing-engine (TX Matrix Plus Router) on page 622
show chassis routing-engine lcc (TX Matrix Plus Router) on page 623
show chassis routing-engine bios (TX Matrix Plus Router) on page 624
show chassis routing-engine (QFX Series) on page 624
show chassis routing-engine (PTX Series Packet Transport Switch) on page 624
show chassis routing-engine (ACX2000 Universal Access Router) on page 625
show chassis routing-engine (ACX1000 Universal Access Router) on page 625
Output Fields
Table 43 on page 609 lists the output fields for the show chassis routing-engine command.
Table 43: show chassis routing-engine Output Fields

Field Name
Field Description
Slot
(Systems with single and multiple Routing Engines) Slot number.
Current state
(Systems with multiple Routing Engines) Current state of the Routing Engine: Master, Backup, or
Disabled.
Election priority
(Systems with multiple Routing Engines) Election priority for the Routing Engine: Master or Backup.
Temperature
Temperature of the air flowing past the Routing Engine.
CPU Temperature
Temperature of the CPU.
DRAM
Total DRAM available to the Routing Engine's processor.
Memory utilization
Percentage of Routing Engine memory being used.
609
Table 43: show chassis routing-engine Output Fields (continued)

Field Name
Field Description
CPU utilization
Information about the Routing Engine's CPU utilization:
UserPercentage of CPU time being used by user processes.
BackgroundPercentage of CPU time being used by background processes.
KernelPercentage of CPU time being used by kernel processes.
InterruptPercentage of CPU time being used by interrupts.
IdlePercentage of CPU time that is idle.
Model
Routing Engine model number.
Serial ID
(Systems with multiple Routing Engines) Identification number of the Routing Engine in this slot.
Start time
Time at which the Routing Engine started running.
Uptime
How long the Routing Engine has been running.
Routing Engine BIOS

Version
BIOS version being run by the Routing Engine.
610
Table 43: show chassis routing-engine Output Fields (continued)

Field Name
Field Description
Last reboot reason
Reason for last reboot, including:
power cycle/failureHalt of the Routing Engine using the halt command, powering down using the
power button on the chassis or any other method (such as removal of the control board or Routing
Engine), and then powering back the Routing Engine. A halt of the operating system also occurs if
you enter the request system halt command. You can enter this command to halt the system
operations on the chassis or specific Routing Engines. To restart the software, press any key on the
keyboard.
watchdogReboot due to a hardware watchdog. A watchdog is a hardware monitoring process
that examines the health and performance of the router to enable the device to recover from
failures. A watchdog checks for problems at certain intervals, and reboots the routing engine if a
problem is encountered.
reset-button reset(Not available on the J Series router or EX Series switch) Reboot due to pressing
of the reset button on the Routing Engine.
power-button hard power offReboot due to pressing of the power button on the chassis. A powering
down of the software also occurs if you enter the request system power-off command. You can
enter this command to power down the chassis or specific Routing Engines; you can then restart
the software.
misc hardware reasonReboot due to miscellaneous hardware reasons.
thermal shutdownReboot due to the router or switch reaching a critical temperature at which
point it is unsafe to continue operations.
hard disk failureReboot due to a hard disk or solid-state drive (SSD) failure.
reset from debuggerReboot due to reset from the debugger.
chassis control resetRestart the chassis process that manages PICs, FPCs, and other hardware
components. The chassis control module that runs the Routing Engine performs management and
monitoring functions, and it provides a single access point for operational and maintenance functions.
A reset of the chassis management process occurs when you enter the restart chassis-control
command.
bios auto recovery resetReboot due to a BIOS auto-recovery reset.
could not be determinedReboot due to an undetermined reason.
Router rebooted after a normal shutdownReboot due to a normal shutdown. This reason is displayed
if the Routing Engine is powered down by pushing and holding the online/offline button on the
Routing Engine faceplate for 30 seconds, and then powered back. A reboot of the software also
occurs if you enter the request system reboot command. You can enter this command to reboot
the chassis or specific Routing Engines.
Load averages
Routing Engine load averages for the last 1, 5, and 15 minutes.
611
Sample Output
show chassis
routing-engine (M5
Router)
user@host> show chassis routing-engine

Routing Engine status:
Temperature
DRAM
768 MB
Memory utilization
21 percent
CPU utilization:
User
0 percent
Background
0 percent
Kernel
0 percent
Interrupt
0 percent
Idle
100 percent
Model
RE-2.0
Serial ID
31000007349bf701
Start time
2003-12-04 09:42:17 PST
Uptime
Last reboot reason
Router rebooted after a normal shutdown
Load averages:
1 minute
5 minute 15 minute
0.00
0.01
0.00
show chassis
routing-engine (M10
Router)

Temperature
DRAM
768 MB
Memory utilization
21 percent
CPU utilization:
User
0 percent
Background
0 percent
Kernel
0 percent
Interrupt
0 percent
Idle
100 percent
Model
RE-2.0
Serial ID
31000007349bf701
Start time
2003-12-04 09:42:17 PST
Uptime
Last reboot reason
Load averages:
1 minute
5 minute 15 minute
0.00
0.01
0.00
show chassis
routing-engine (M20
Router)

Slot 0:
Current state
Master
Election priority
Master (default)
Temperature
DRAM
768 MB
Memory utilization
20 percent
CPU utilization:
User
1 percent
Background
0 percent
Kernel
2 percent
Interrupt
0 percent
Idle
97 percent
Model
RE-2.0
Serial ID
58000007348d9a01
Start time
2003-12-30 07:05:47 PST
Uptime
612
Last reboot reason

Load averages:
Slot 1:
Current state
Election priority
Temperature
DRAM
Memory utilization
CPU utilization:
User
Background
Kernel
Interrupt
Idle
Model
Serial ID
Start time
Uptime
Last reboot reason

1 minute
5 minute 15 minute
0.00
0.02
0.00
Backup
Backup (default)
768 MB
0 percent
0
0
1
0
99
percent
percent
percent
percent
percent
RE-2.0
d800000734745701
2003-06-17 16:37:33 PDT
show chassis
routing-engine (M40
Router)

Temperature
DRAM
768 MB
Memory utilization
21 percent
CPU utilization:
User
0 percent
Background
0 percent
Kernel
0 percent
Interrupt
0 percent
Idle
100 percent
Model
RE-2.0
Serial ID
31000007349bf701
Start time
2003-12-04 09:42:17 PST
Uptime
Last reboot reason
Load averages:
1 minute
5 minute 15 minute
0.00
0.01
0.00
show chassis
routing-engine (M120
Router)

Slot 0:
Current state
Master
Election priority
Master (default)
Temperature
CPU temperature
DRAM
2048 MB
Memory utilization
18 percent
CPU utilization:
User
0 percent
Background
0 percent
Kernel
5 percent
Interrupt
0 percent
Idle
95 percent
Model
RE-A-1000
Serial ID
1000621154
Start time
2006-10-31 17:10:05 PST
Uptime
613
Last reboot reason

Load averages:
Slot 1:
Current state
Election priority
Temperature
CPU temperature
DRAM
Memory utilization
CPU utilization:
User
Background
Kernel
Interrupt
Idle
Model
Serial ID
Start time
Uptime
Last reboot reason
show chassis
routing-engine (M160
Router)
614

1 minute
5 minute 15 minute
0.02
0.07
0.07
45
42
2048
15
0
0
0
0
100
Backup
Backup (default)
MB
percent
percent
percent
percent
percent
percent
RE-A-1000
1000621151
2006-10-31 17:10:04 PST

Slot 0:
Current state
Master
Election priority
Master (default)
Temperature
DRAM
2048 MB
Memory utilization
11 percent
CPU utilization:
User
1 percent
Background
0 percent
Kernel
2 percent
Interrupt
0 percent
Idle
97 percent
Model
RE-3.0
Serial ID
210865700403
Start time
2003-12-23 12:25:55 PST
Uptime
Last reboot reason
Load averages:
1 minute
5 minute 15 minute
0.24
0.13
0.04
Slot 1:
Current state
Backup
Election priority
Backup (default)
Temperature
DRAM
2048 MB
Memory utilization
9 percent
CPU utilization:
User
0 percent
Background
0 percent
Kernel
0 percent
Interrupt
0 percent
Idle
100 percent
Model
RE-3.0
Serial ID
210865700332
Start time
2003-12-23 12:25:55 PST
Uptime
Last reboot reason
show chassis
routing-engine
(MX240 Router)

Slot 0:
Current state
Backup
Election priority
Master (default)
Temperature
CPU temperature
DRAM
3584 MB
Memory utilization
7 percent
CPU utilization:
User
0 percent
Background
0 percent
Kernel
0 percent
Interrupt
0 percent
Idle
100 percent
Model
RE-S-2000
Serial ID
1000703522
Start time
2007-12-19 10:35:40 PST
Uptime
Last reboot reason
show chassis
routing-engine
(MX480 Router)

Slot 0:
Current state
Master
Election priority
Master (default)
Temperature
CPU temperature
DRAM
2048 MB
Memory utilization
13 percent
CPU utilization:
User
0 percent
Background
0 percent
Kernel
2 percent
Interrupt
0 percent
Idle
98 percent
Model
RE-S-1300
Serial ID
1000697044
Start time
2008-01-04 06:46:08 PST
Uptime
8 hours, 17 minutes, 16
Last reboot reason
Router rebooted after a
show chassis
routing-engine
(MX960 Router)
F
F
seconds
normal shutdown

Slot 0:
Current state
Master
Election priority
Master (default)
Temperature
CPU temperature
DRAM
2048 MB
Memory utilization
18 percent
CPU utilization:
User
0 percent
Background
0 percent
Kernel
4 percent
Interrupt
0 percent
Idle
96 percent
615
Model
Serial ID
Start time
Uptime
Last reboot reason
Load averages:
show chassis
routing-engine
(MX2010 Router)

Slot 0:
Current state
Election priority
Temperature
CPU temperature
DRAM
Memory utilization
CPU utilization:
User
Background
Kernel
Interrupt
Idle
Model
Serial ID
Start time
Uptime
Last reboot reason
Load averages:
Slot 1:
Current state
Election priority
Temperature
CPU temperature
DRAM
Memory utilization
CPU utilization:
User
Background
Kernel
Interrupt
Idle
Model
Serial ID
Start time
Uptime
Last reboot reason
Load averages:
show chassis
routing-engine
(MX2020 Router)
616
RE-S-1300
1000617944
2006-10-26 12:37:13 PDT
1 minute
5 minute 15 minute
0.16
0.08
0.02
Master
Master (default)
17152 MB
13 percent
0
0
4
2
95
percent
percent
percent
percent
percent
RE-S-1800x4
9009099704
2012-10-02 14:33:32 PDT
Router rebooted after a normal shutdown.
1 minute
5 minute 15 minute
0.06
0.05
0.01
Backup
Backup (default)
17152 MB
11 percent
0
0
0
0
100
percent
percent
percent
percent
percent
RE-S-1800x4
9009099706
2012-10-02 10:36:06 PDT
1 minute
5 minute 15 minute
0.01
0.00
0.00

Slot 0:
Current state
Master
Election priority
Master (default)
Temperature
CPU temperature
DRAM
Memory utilization
CPU utilization:
User
Background
Kernel
Interrupt
Idle
Model
Serial ID
Start time
Uptime
Last reboot reason
Load averages:
Slot 1:
Current state
Election priority
Temperature
CPU temperature
DRAM
Memory utilization
CPU utilization:
User
Background
Kernel
Interrupt
Idle
Model
Serial ID
Start time
Uptime
Last reboot reason
Load averages:
show chassis
routing-engine (T320
router)
17152 MB
14 percent
1
0
7
2
91
Backup
Backup (default)
17152 MB
12 percent
0
0
0
0
99

Slot 0:
Current state
Election priority
Temperature
51
CPU temperature
55
DRAM
3584
Memory utilization
11
CPU utilization:
User
0
Background
0
Kernel
2
Interrupt
0
Idle
97
Model
Serial ID
Start time
Uptime
Last reboot reason
Load averages:
Slot 1:
Current state
percent
percent
percent
percent
percent
RE-S-1800x4
9009089704
2012-10-02 11:05:24 PDT
1 minute
5 minute 15 minute
0.10
0.05
0.01
percent
percent
percent
percent
percent
RE-S-1800x4
9009094138
2012-10-02 11:09:57 PDT
1 minute
5 minute 15 minute
0.00
0.00
0.00
Master
Master (default)
MB
percent
percent
percent
percent
percent
percent
RE-A-2000
9009010618
2012-10-10 01:24:05 PDT
0x1:power cycle/failure
1 minute
5 minute 15 minute
0.00
0.05
0.04
Backup
617
Election priority
Temperature
CPU temperature
DRAM
Memory utilization
CPU utilization:
User
Background
Kernel
Interrupt
Idle
Model
Serial ID
Start time
Uptime
Last reboot reason
show chassis
router)
45
48
3584
9
0
0
0
0
100

Slot 0:
Current state
Election priority
Temperature
50
CPU temperature
58
DRAM
3584
Memory utilization
14
CPU utilization:
User
1
Background
0
Kernel
4
Interrupt
1
Idle
95
Model
Serial ID
Start time
Uptime
Last reboot reason
Load averages:
Slot 1:
Current state
Election priority
Temperature
CPU temperature
DRAM
Memory utilization
CPU utilization:
User
Background
Kernel
Interrupt
Idle
Model
Serial ID
Start time
Uptime
Last reboot reason
44
49
3584
12
0
0
0
1
99
Backup (default)
MB
percent
percent
percent
percent
percent
percent
RE-A-2000
9009003642
2012-10-10 01:24:04 PDT
Master
Master (default)
MB
percent
percent
percent
percent
percent
percent
RE-A-2000
1000686556
2012-10-10 01:24:02 PDT
1 minute
5 minute 15 minute
1.24
0.33
0.12
Backup
Backup (default)
MB
percent
percent
percent
percent
percent
percent
RE-A-2000
1000702739
2012-10-10 01:24:02 PDT
618
show chassis
router)

Slot 0:
Current state
Election priority
Temperature
CPU temperature
DRAM
Memory utilization
CPU utilization:
User
Background
Kernel
Interrupt
Idle
Model
Serial ID
Start time
Uptime
Last reboot reason
Load averages:
Slot 1:
Current state
Election priority
Temperature
CPU temperature
DRAM
Memory utilization
CPU utilization:
User
Background
Kernel
Interrupt
Idle
Model
Serial ID
Start time
Uptime
Last reboot reason
show chassis
router)
48
58
3584
13
0
0
3
1
96
44
48
3584
12
0
0
0
0
100

Slot 0:
Current state
Election priority
Temperature
33
CPU temperature
50
DRAM
8960
Memory utilization
18
CPU utilization:
User
0
Background
0
Kernel
4
Interrupt
1
Idle
95
Model
Serial ID
Start time
Uptime
Last reboot reason
Master
Master (default)
MB
percent
percent
percent
percent
percent
percent
RE-A-2000
1000704521
2012-10-10 01:23:41 PDT
1 minute
5 minute 15 minute
0.05
0.03
0.01
Backup
Backup (default)
MB
percent
percent
percent
percent
percent
percent
RE-A-2000
9009006579
2012-10-10 01:23:42 PDT
Master
Master (default)
MB
percent
percent
percent
percent
percent
percent
RE-DUO-1800
P737F-002248
2012-02-09 22:49:53 PST
619
Load averages:
Slot 1:
Current state
Election priority
Temperature
CPU temperature
DRAM
Memory utilization
CPU utilization:
User
Background
Kernel
Interrupt
Idle
Model
Serial ID
Start time
Uptime
Last reboot reason
show chassis
routing-engine (TX
Matrix Router)
1 minute
0.00
32
46
8960
24
0
0
0
0
99
5 minute
0.04
15 minute
0.00
Backup
Backup (default)
MB
percent
percent
percent
percent
percent
percent
RE-DUO-1800
P737F-002653
2012-02-08 20:12:51 PST

scc-re0:
-------------------------------------------------------------------------Routing Engine status:
Slot 0:
Current state
Master
Election priority
Master (default)
Temperature
CPU temperature
DRAM
2048 MB
Memory utilization
12 percent
CPU utilization:
User
0 percent
Background
0 percent
Kernel
2 percent
Interrupt
0 percent
Idle
98 percent
Model
RE-4.0
Serial ID
P11123900153
Start time
2004-08-05 18:42:05 PDT
Uptime
Last reboot reason
Load averages:
1 minute
5 minute 15 minute
0.00
0.08
0.07
lcc0-re0:
Slot 0:
Current state
Master
Election priority
Master (default)
Temperature
CPU temperature
DRAM
2048 MB
Memory utilization
12 percent
CPU utilization:
User
0 percent
Background
0 percent
Kernel
1 percent
620
Interrupt
Idle
Model
Serial ID
Start time
Uptime
Last reboot reason
Load averages:
0 percent
98 percent
RE-3.0
210865700363
2004-08-05 18:42:05 PDT
1 minute
5 minute 15 minute
0.00
0.02
0.00
lcc2-re0:
Slot 0:
Current state
Master
Election priority
Master (default)
Temperature
CPU temperature
DRAM
2048 MB
Memory utilization
12 percent
CPU utilization:
User
0 percent
Background
0 percent
Kernel
2 percent
Interrupt
0 percent
Idle
98 percent
Model
RE-4.0
Serial ID
P11123900126
Start time
2004-08-05 18:42:05 PDT
Uptime
Last reboot reason
Load averages:
1 minute
5 minute 15 minute
0.01
0.01
0.0
show chassis
routing-engine lcc (TX
Matrix Router)
user@host> show chassis routing-engine 0 lcc 0

lcc0-re0:
-------------------------------------------------------------------------------Routing Engine status:
Slot 0:
Current state
Master
Election priority
Master (default)
Temperature
CPU temperature
DRAM
2048 MB
Memory utilization
12 percent
CPU utilization:
User
0 percent
Background
0 percent
Kernel
1 percent
Interrupt
0 percent
Idle
98 percent
Model
RE-3.0
Serial ID
210865700363
Start time
2004-08-05 18:42:05 PDT
Uptime
Last reboot reason
Load averages:
1 minute
5 minute 15 minute
0.00
0.00
0.00
user@host> show chassis routing-engine bios
621
show chassis
routing-engine bios
(TX Matrix Router)
scc-re0:
-------------------------------------------------------------------------Routing Engine BIOS Version: V1.0.0
lcc0-re0:
lcc2-re0:
show chassis
routing-engine (TX
Matrix Plus Router)

sfc0-re0:
Slot 0:
Current state
Master
Election priority
Master (default)
Temperature
CPU temperature
DRAM
3327 MB
Memory utilization
12 percent
CPU utilization:
User
0 percent
Background
0 percent
Kernel
2 percent
Interrupt
0 percent
Idle
98 percent
Model
RE-TXP-SFC
Serial ID
737A-1024
Start time
2009-05-11 17:39:49 PDT
Uptime
Last reboot reason
Load averages:
1 minute
5 minute 15 minute
0.00
0.00
0.00
Slot 1:
Current state
Backup
Election priority
Backup (default)
Temperature
CPU temperature
DRAM
3327 MB
Memory utilization
11 percent
CPU utilization:
User
0 percent
Background
0 percent
Kernel
0 percent
Interrupt
0 percent
Idle
100 percent
Model
RE-TXP-SFC
Serial ID
737A-1024
Start time
2009-05-11 17:08:54 PDT
Uptime
Last reboot reason
lcc0-re0:
Slot 0:
Current state
Master
Election priority
Master (default)
Temperature
622
CPU temperature
DRAM
Memory utilization
CPU utilization:
User
Background
Kernel
Interrupt
Idle
Model
Serial ID
Start time
Uptime
Last reboot reason
Load averages:
Slot 1:
Current state
Election priority
Temperature
CPU temperature
DRAM
Memory utilization
CPU utilization:
User
Background
Kernel
Interrupt
Idle
Model
Serial ID
Start time
Uptime
Last reboot reason
show chassis
routing-engine lcc (TX
Matrix Plus Router)

3327 MB
9 percent
0
0
2
0
98
30
43
3327
9
0
0
0
0
100
percent
percent
percent
percent
percent
RE-TXP-LCC
737F-1024
2009-05-11 17:40:32 PDT
1 minute
5 minute 15 minute
0.00
0.00
0.00
Backup
Backup (default)
MB
percent
percent
percent
percent
percent
percent
RE-TXP-LCC
737F-1024
2009-05-06 17:31:32 PDT
user@host> show chassis routing-engine 0 lcc 0

lcc0-re0:
Slot 0:
Current state
Master
Election priority
Master (default)
Temperature
CPU temperature
DRAM
3327 MB
Memory utilization
9 percent
CPU utilization:
User
0 percent
Background
0 percent
Kernel
2 percent
Interrupt
0 percent
Idle
98 percent
Model
RE-TXP-LCC
Serial ID
737F-1024
Start time
2009-05-11 17:40:32 PDT
Uptime
Last reboot reason
Load averages:
1 minute
5 minute 15 minute
0.00
0.00
0.00
623
Slot 1:
Current state
Election priority
Temperature
CPU temperature
DRAM
Memory utilization
CPU utilization:
User
Background
Kernel
Interrupt
Idle
Model
Serial ID
Start time
Uptime
Last reboot reason
show chassis
routing-engine bios
(TX Matrix Plus
Router)
30
43
3327
9
0
0
0
0
100
Backup
Backup (default)
MB
percent
percent
percent
percent
percent
percent
RE-TXP-LCC
737F-1024
2009-05-06 17:31:32 PDT
user@host> show chassis routing-engine bios

sfc0-re0:
-------------------------------------------------------------------------Routing Engine BIOS Version: V0.0.Z
lcc0-re0:
-------------------------------------------------------------------------Routing Engine BIOS Version: V0.0.N
show chassis
routing-engine (QFX
Series)
user@switch> show chassis routing-engine

Slot 0:
Current state Master
Election priority Master (default)
DRAM 2820 MB
Memory utilization 49 percent
CPU utilization:
User 1 percent
Background 0 percent
Kernel 1 percent
Interrupt 0 percent
Idle 97 percent
Model QFX3500-48S4Q
Serial ID S/N ED3709
Uptime 3 days, 4 hours, 29 minutes, 42 seconds
Last reboot reason 0x200:chassis control reset
Load averages: 1 minute 5 minute 15 minute
0.37 0.26 0.19
show chassis
routing-engine (PTX
user@switch> show chassis routing-engine

Slot 0:
624
Series Packet
Transport Switch)
Current state
Election priority
Temperature
CPU temperature
DRAM
Memory utilization
CPU utilization:
User
Background
Kernel
Interrupt
Idle
Model
Serial ID
Start time
Uptime
Last reboot reason
Load averages:
Slot 1:
Current state
Election priority
Temperature
CPU temperature
DRAM
Memory utilization
CPU utilization:
User
Background
Kernel
Interrupt
Idle
Model
Serial ID
Start time
Uptime
Last reboot reason
Master
Master (default)
17152 MB
11 percent
0
0
4
0
95
percent
percent
percent
percent
percent
RE-DUO-2600
P737A-002231
2011-12-21 16:54:37 PST
1 minute
5 minute 15 minute
0.01
0.02
0.06
Backup
Backup (default)
17152 MB
10 percent
0
0
0
0
99
percent
percent
percent
percent
percent
RE-DUO-2600
P737A-002438
2011-12-21 16:52:26 PST
show chassis
routing-engine
(ACX2000 Universal
Access Router)

Temperature
DRAM
1536 MB
Memory utilization
25 percent
CPU utilization:
User
0 percent
Background
0 percent
Kernel
0 percent
Interrupt
1 percent
Idle
99 percent
Model
RE-ACX-2000
Start time
2012-05-09 00:57:07 PDT
Uptime
Last reboot reason
Load averages:
1 minute
5 minute 15 minute
0.00
0.03
0.05
show chassis
routing-engine

Temperature
625
(ACX1000 Universal
Access Router)
626
DRAM
Memory utilization
CPU utilization:
User
Background
Kernel
Interrupt
Idle
Model
Start time
Uptime
Last reboot reason
Load averages:
768 MB
50 percent
3
0
6
0
91
percent
percent
percent
percent
percent
RE-ACX-1000
2012-05-10 07:12:23 PDT
1 minute
5 minute 15 minute
0.00
0.00
0.00
show chassis synchronization

Syntax
show chassis synchronization

<extensive>
<backup | master>
Release Information
Command introduced in Junos OS Release 7.6 for M320 routers.

Command introduced in Junos OS Release 8.3 for M40e routers.
Command introduced in Junos OS Release 9.3 for M120 routers.
Command introduced in Junos OS Release 10.2 for T320, T640, and T1600 routers.
Description
(ACX Series, M320, M40e,M120, T320, T640, and T1600 routers and PTX Series Packet
Transport Switches only) Display information about the external clock source currently
used for chassis synchronization.
Options
extensive(Optional) Display clock synchronization information in detail.

backup(Optional) Display clock synchronization information about the backup clock.
master (Optional) Display clock synchronization information about the master clock.
Required Privilege
Level
Related
Documentation
Output Fields
maintenance
request chassis synchronization switch
Configuring Clock Synchronization Interface for MX Series Routers
show chassis synchronization (MX Series Routers)
Supported Time Synchronization Standard
show chassis synchronization on page 629

show chassis synchronization master on page 629
show chassis synchronization backup on page 629
show chassis synchronization extensive on page 629
show chassis synchronization (T320, T640, and T1600 Routers) on page 629
show chassis synchronization (PTX Series Packet Transport Switches) on page 630
show chassis synchronization extensive (ACX Series Routers) on page 630
Table 44 on page 628 lists the output fields for the show chassis synchronization command.
Output fields are listed in the approximate order in which they appear.show chassis
synchronizationshow chassis synchronizationshow chassis synchronization
627
Table 44: show chassis synchronization Output Fields

Field Name
Field Description
Current state
Indicates current status of external clock sources:
backupSource is currently the backup clock source.
masterSource is currently the master clock source.
Online-Master(PTX Series Packet Transport Switches) Source is the master clock. Source is
online.
Online-Standby(PTX Series Packet Transport Switches) Source is the standby (backup) clock.
Source is online.
Current clock state
Indicates current source of external synchronization:
internalSource is providing its own clocking.
locked to master CB(M320, M40e, and M120 routers) Source is locked to master clock source.
locked to master SCG(T320, T640, and T1600 routers) Source is locked to master clock source.
locked to master CCG(PTX Series Packet Transport Switches) Source is locked to master clock
source.
Selected for
Number of seconds this clock has been the master or backup clock source.
Selected since
Timestamp for establishment as master or backup clock source.
Deviation (in ppm)
Difference in clock timing, in parts per million (ppm).
Last deviation (in ppm)
Previous difference in clock timing, if any, in ppm.
Configured sources
Information about clock sources eligible for selection as master clock.
Source
Information about external clock sources.
Priority
Indicates priority of external clock sources:
Deviation (in ppm)
Last deviation (in ppm)
primarySource is a primary reference.
secondarySource is a secondary reference.
Current difference in clock timing, in ppm:
measuringEstablishing source deviation.
numberDeviation in ppm.
Previous difference in clock timing, in ppm:
Status
628
numberDeviation in ppm.
Indicates status of external sources:
presentSource is configured and present.
qualifiedSource is eligible for synchronization source.
Sample Output
show chassis
synchronization
user@host> show chassis synchronization

Clock Synchronization Status :
Clock module on CB 0
Current state
: master
Current clock state
: internal
Selected for
: 18 hours, 12 minutes, 43 seconds
Selected since
: 2008-09-10 03:27:47 PDT
Deviation (in ppm)
: +0.00
Last deviation (in ppm): +0.00
Current state
: backup
Current clock state
: locked to master CB
Selected for
: 1 day, 12 hours, 49 minutes, 20 seconds
Selected since
: 2008-09-09 08:51:10 PDT
show chassis
synchronization
master
user@host> show chassis synchronization master

Current state
: master
Current clock state
: internal
Selected for
: 8 days, 21 minutes, 12 seconds
Selected since
: 2008-08-27 21:05:40 PDT
Deviation (in ppm)
: +0.00
show chassis
synchronization
backup
user@host> show chassis synchronization backup

Current state
: backup
Current clock state
Selected for
: 34 days, 20 hours, 17 minutes, 8 seconds
Selected since
: 2008-08-01 01:22:16 PDT
show chassis
synchronization
extensive
user@host> show chassis synchronization extensive

Current state
: master
Current clock state
: internal
Selected for
: 8 days, 36 minutes, 29 seconds
Selected since
: 2008-08-27 21:05:40 PDT
Deviation (in ppm)
: +0.00
Current state
: backup
Current clock state
Selected for
: 34 days, 20 hours, 19 minutes, 53 seconds
Selected since
: 2008-08-01 01:22:16 PDT
show chassis
synchronization (T320,

Clock module on SCG 0
629
T640, and T1600

Routers)
Current state
Current clock state
Selected for
Selected since
Configured sources
Source
Priority
:
:
:
:
master
locked to external-a
2006-02-17 01:12:58 PST
Deviation
Last deviation
Status
(in ppm)
(in ppm)
external-a primary
measuring
-0.10
in-use
external-b secondary -0.10
-0.10
qualified
Clock module on SCG 1
Current state
: backup
Current clock state
: locked to master SCG
Selected for
: 19 hours, 49 minutes, 14 seconds
Selected since
: 2006-02-16 07:51:48 PST
Configured sources
Source
Priority
Deviation
Last deviation
Status
(in ppm)
(in ppm)
external-a primary
-0.25
-0.25
qualified
external-b secondary -0.25
-0.25
qualified
show chassis
synchronization (PTX
Series Packet
Transport Switches)

Clock module on CCG 0
Current state
: Online - Master
Current clock state
: internal
Selected for
: 1 hour, 24 minutes, 21 seconds
Selected since
: 2011-03-21 15:59:37 PDT
Deviation (in ppm)
: +0.51
Clock module on CCG 1
Current state
: Online - Standby
Current clock state
: locked to master CCG
Selected for
: 1 hour, 39 minutes, 12 seconds
Selected since
: 2011-03-21 15:44:46 PDT
show chassis
synchronization
extensive (ACX Series
Routers)
user@host> show chassis synchronization extensive

Current clock status : Locked
Clock locked to
: Primary
Configured sources:
Interface
: ce1-0/0/4
Status
: Primary
Index
: 132
Clock source state : Clk qualified
Priority
: Default(8)
Configured QL
: PRC
ESMC QL
: Unknown
Clock source type
: ifd
Clock Event : Clock locked
Kernel flags
: Up,pri,
630
show class-of-service interface

Syntax
Release Information
Description
Options
show class-of-service interface

<detail | comprehensive> <interface-name>

Forwarding class map information added in Junos OS Release 9.4.
Command introduced in Junos OS Release 12.1 for the PTX Series Packet Transport
Switches.
routers.
Options detail and comprehensive introduced in Junos OS Release 11.4.
Display the logical and physical interface associations for the classifier, rewrite rules, and
scheduler map objects.
comprehensive(M Series, MX Series, and T Series routers) (Optional) Display
comprehensive quality-of-service (QoS) information about all physical and logical

interfaces.
detail(M Series, MX Series, and T Series routers) (Optional) Display QoS and CoS
information based on the interface.

If the interface interface-name is a physical interface, the output includes:
Brief QoS information about the physical interface
Brief QoS information about the logical interface
CoS information about the physical interface
Brief information about filters or policers of the logical interface
Brief CoS information about the logical interface
If the interface interface-name is a logical interface, the output includes:
Brief QoS information about the logical interface
Information about filters or policers for the logical interface
CoS information about the logical interface
interface-name(Optional) Display class-of-service (CoS) associations for the specified
interface.
noneDisplay CoS associations for all physical and logical interfaces.
Required Privilege
Level
view
show class-of-service interface (Physical) on page 643
631
show class-of-service interface (Logical) on page 643

show class-of-service interface (Gigabit Ethernet) on page 643
show class-of-service interface (PPPoE Interface) on page 643
show class-of-service interface (T4000 Routers with Type 5 FPCs) on page 643
show class-of-service interface detail on page 644
show class-of-service interface comprehensive on page 644
show class-of-service interface (ACX Series Routers) on page 654
Output Fields
Table 45 on page 632 describes the output fields for the show class-of-service interface
command. Output fields are listed in the approximate order in which they appear.
Table 45: show class-of-service interface Output Fields

Field Name
Field Description
Physical interface
Name of a physical interface.
Index
Index of this interface or the internal index of this object.
Dedicated Queues
Status of dedicated queues configured on an interface. Supported only on Trio MPC/MIC interfaces
on MX Series routers.
Queues supported
Number of queues you can configure on the interface.
Queues in use
Number of queues currently configured.
Total non-default
queues created
Number of queues created in addition to the default queues. Supported only on Trio MPC/MIC
interfaces on MX Series routers.
Rewrite Input IEEE

Code-point
(QFX Series only) IEEE 802.1p code point (priority) rewrite value. Incoming traffic from the Fibre
Channel (FC) SAN is classified into the forwarding class specified in the native FC interface (NP_Port)
fixed classifier and uses the priority specified as the IEEE 802.1p rewrite value.
Shaping rate
Maximum transmission rate on the physical interface. You can configure the shaping rate on the
physical interface, or on the logical interface, but not on both. Therefore, the Shaping rate field is
displayed for either the physical interface or the logical interface.
Scheduler map
Name of the output scheduler map associated with this interface.
Input shaping rate
For Gigabit Ethernet IQ2 PICs, maximum transmission rate on the input interface.
Input scheduler map
For Gigabit Ethernet IQ2 PICs, name of the input scheduler map associated with this interface.
Chassis scheduler map
Name of the scheduler map associated with the packet forwarding component queues.
Rewrite
Name and type of the rewrite rules associated with this interface.
Classifier
Name and type of classifiers associated with this interface.
Forwarding-class-map
Name of the forwarding map associated with this interface.
Congestion-notification
(QFX Series only) Congestion notification state, enabled or disabled.
632
Table 45: show class-of-service interface Output Fields (continued)

Field Name
Field Description
Logical interface
Name of a logical interface.
Object
Category of an object: Classifier, Fragmentation-map (for LSQ interfaces only), Scheduler-map, Rewrite,
or Translation Table (for IQE PICs only).
Name
Name of an object.
Type
Type of an object: dscp, dscp-ipv6, exp, ieee-802.1, ip, or inet-precedence.
Link-level type
Encapsulation on the physical interface.
MTU
MTU size on the physical interface.
Speed
Speed at which the interface is running.
Loopback
Whether loopback is enabled and the type of loopback.
Source filtering
Whether source filtering is enabled or disabled.
Flow control
Whether flow control is enabled or disabled.
Auto-negotiation
(Gigabit Ethernet interfaces) Whether autonegotiation is enabled or disabled.
Remote-fault
(Gigabit Ethernet interfaces) Remote fault status.
Device flags
OnlineAutonegotiation is manually configured as online.
OfflineAutonegotiation is manually configured as offline.
The Device flags field provides information about the physical device and displays one or more of the
following values:
DownDevice has been administratively disabled.
Hear-Own-XmitDevice receives its own transmissions.
Link-Layer-DownThe link-layer protocol has failed to connect with the remote endpoint.
LoopbackDevice is in physical loopback.
Loop-DetectedThe link layer has received frames that it sent, thereby detecting a physical loopback.
No-CarrierOn media that support carrier recognition, no carrier is currently detected.
No-MulticastDevice does not support multicast traffic.
PresentDevice is physically present and recognized.
PromiscuousDevice is in promiscuous mode and recognizes frames addressed to all physical
addresses on the media.
QuenchTransmission on the device is quenched because the output buffer is overflowing.
Recv-All-MulticastsDevice is in multicast promiscuous mode and therefore provides no multicast
filtering.
RunningDevice is active and enabled.
633

Field Name
Field Description
Interface flags
The Interface flags field provides information about the physical interface and displays one or more
of the following values:
Admin-TestInterface is in test mode and some sanity checking, such as loop detection, is disabled.
DisabledInterface is administratively disabled.
DownA hardware failure has occurred.
Hardware-DownInterface is nonfunctional or incorrectly connected.
Link-Layer-DownInterface keepalives have indicated that the link is incomplete.
No-MulticastInterface does not support multicast traffic.
No-receive No-transmitPassive monitor mode is configured on the interface.
Point-To-PointInterface is point-to-point.
Pop all MPLS labels from packets of depthMPLS 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:
1Takes effect for incoming packets with one label only.
2Takes effect for incoming packets with two labels only.
[ 1 2 ]Takes effect for incoming packets with either one or two labels.
PromiscuousInterface is in promiscuous mode and recognizes frames addressed to all physical
addresses.
Flags
Recv-All-MulticastsInterface is in multicast promiscuous mode and provides no multicast filtering.
SNMP-TrapsSNMP trap notifications are enabled.
UpInterface is enabled and operational.
The Logical interface flags field provides information about the logical interface and displays one or
more of the following values:
ACFC EncapsulationAddress control field Compression (ACFC) encapsulation is enabled
(negotiated successfully with a peer).
Device-downDevice has been administratively disabled.
DisabledInterface is administratively disabled.
DownA hardware failure has occurred.
Clear-DF-BitGRE tunnel or IPsec tunnel is configured to clear the Don't Fragment (DF) bit.
Hardware-DownInterface protocol initialization failed to complete successfully.
PFCProtocol field compression is enabled for the PPP session.
Point-To-PointInterface is point-to-point.
SNMP-TrapsSNMP trap notifications are enabled.
UpInterface is enabled and operational.
Encapsulation
Encapsulation on the logical interface.
Admin
Administrative state of the interface (Up or Down)
Link
Status of physical link (Up or Down).
Proto
Protocol configured on the interface.
634

Field Name
Field Description
Input Filter
Names of any firewall filters to be evaluated when packets are received on the interface, including
any filters attached through activation of dynamic service.
Output Filter
Names of any firewall filters to be evaluated when packets are transmitted on the interface, including
any filters attached through activation of dynamic service.
Link flags
Provides information about the physical link and displays one or more of the following values:
ACFCAddress control field compression is configured. The Point-to-Point Protocol (PPP) session
negotiates the ACFC option.
Give-UpLink protocol does not continue connection attempts after repeated failures.
Loose-LCPPPP does not use the Link Control Protocol (LCP) to indicate whether the link protocol
is operational.
Loose-LMIFrame Relay does not use the Local Management Interface (LMI) to indicate whether
the link protocol is operational.
Loose-NCPPPP does not use the Network Control Protocol (NCP) to indicate whether the device
is operational.
KeepalivesLink protocol keepalives are enabled.
No-KeepalivesLink protocol keepalives are disabled.
PFCProtocol field compression is configured. The PPP session negotiates the PFC option.
Hold-times
Current interface hold-time up and hold-time down, in milliseconds.
CoS queues
Number of CoS queues configured.
Last flapped
Date, time, and how long ago the interface went from down to up. The format is Last flapped:
year-month-day hour:minute:second:timezone (hour:minute:second ago). For example, Last flapped:
2002-04-26 10:52:40 PDT (04:33:20 ago).
Statistics last cleared
IPv6 transit statistics
Number and rate of bytes and packets received and transmitted on the physical interface.
Input bytesNumber of bytes received on the interface.
Output bytesNumber of bytes transmitted on the interface.
Input packetsNumber of packets received on the interface.
Output packetsNumber of packets transmitted on the interface.
Number of IPv6 transit bytes and packets received and transmitted on the logical interface if IPv6
statistics tracking is enabled.
635

Field Name
Field Description
Input errors
Input errors on the interface. The labels are explained in the following list:
ErrorsSum of the incoming frame aborts and FCS errors.
DropsNumber 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 errorsNumber of packets received with an invalid frame checksum (FCS).
RuntsNumber of frames received that are smaller than the runt threshold.
GiantsNumber of frames received that are larger than the giant threshold.
Bucket DropsDrops resulting from the traffic load exceeding the interface transmit or receive
leaky bucket configuration.
Policed discardsNumber of frames that the incoming packet match code discarded because they
were not recognized or not of interest. Usually, this field reports protocols that Junos OS does not
handle.
L3 incompletesNumber 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. Layer 3 incomplete errors can be ignored by configuring the ignore-l3-incompletes
statement.
L2 channel errorsNumber of times the software did not find a valid logical interface for an incoming
frame.
L2 mismatch timeoutsNumber of malformed or short packets that caused the incoming packet
handler to discard the frame as unreadable.
HS link CRC errorsNumber of errors on the high-speed links between the ASICs responsible for
handling the router interfaces.
HS link FIFO overflowsNumber 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 labels are explained in the following list:
Carrier transitionsNumber 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.
ErrorsSum of the outgoing frame aborts and FCS errors.
DropsNumber 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 packetsNumber 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 underflowsNumber of FIFO underflows on the high-speed links between the ASICs
responsible for handling the router interfaces.
Egress queues
636
MTU errorsNumber of packets whose size exceeds the MTU of the interface.
Total number of egress queues supported on the specified interface.

Field Name
Field Description
Queue counters
CoS queue number and its associated user-configured forwarding class name.
Queued packetsNumber of queued packets.
Transmitted packetsNumber of transmitted packets.
Dropped packetsNumber of packets dropped by the ASIC's RED mechanism.
SONET defects
(SONET) SONET media-specific alarms and defects that prevent the interface from passing packets.
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 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.
SONET alarms
SecondsNumber of seconds the defect has been active.
CountNumber of times that the defect has gone from inactive to active.
StateState of the error. A state other than OK indicates a problem.
The SONET PHY field has the following subfields:
SONET section
PLL LockPhase-locked loop
PHY LightLoss of optical signal
The SONET section field has the following subfields:
BIP-B1Bit interleaved parity for SONET section overhead
SEFSeverely errored framing
LOSLoss of signal
LOFLoss of frame
ES-SErrored seconds (section)
SES-SSeverely errored seconds (section)
SEFS-SSeverely errored framing seconds (section)
637

Field Name
Field Description
SONET line
Active alarms and defects, plus counts of specific SONET errors with detailed information.
The SONET line field has the following subfields:
SONET path
BIP-B2Bit interleaved parity for SONET line overhead
REI-LRemote error indication (near-end line)
RDI-LRemote defect indication (near-end line)
AIS-LAlarm indication signal (near-end line)
BERR-SFBit error rate fault (signal failure)
BERR-SDBit error rate defect (signal degradation)
ES-LErrored seconds (near-end line)
SES-LSeverely errored seconds (near-end line)
UAS-LUnavailable seconds (near-end line)
ES-LFEErrored seconds (far-end line)
SES-LFESeverely errored seconds (far-end line)
UAS-LFEUnavailable seconds (far-end line)
Active alarms and defects, plus counts of specific SONET errors with detailed information.
The SONET path field has the following subfields:
638
REI-PRemote error indication
LOP-PLoss of pointer (path)
AIS-PPath alarm indication signal
RDI-PPath remote defect indication
UNEQ-PPath unequipped
PLM-PPath payload (signal) label mismatch
ES-PErrored seconds (near-end STS path)
SES-PSeverely errored seconds (near-end STS path)
UAS-PUnavailable seconds (near-end STS path)
ES-PFEErrored seconds (far-end STS path)
SES-PFESeverely errored seconds (far-end STS path)
UAS-PFEUnavailable seconds (far-end STS path)

Field Name
Field Description
Received SONET
overhead
Values of the received and transmitted SONET overhead:
Transmitted SONET
overhead
C2Signal label. Allocated to identify the construction and content of the STS-level SPE and for
PDI-P.
F1Section user channel byte. This byte is set aside for the purposes of users.
K1 and K2These bytes are allocated for APS signaling for the protection of the multiplex section.
J0Section 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.
Received path trace

Transmitted path trace
HDLC configuration
Packet Forwarding
Engine configuration
CoS information
S1Synchronization status. The S1 byte is located in the first STS-1 number of an STS-N signal.
Z3 and Z4Allocated for future use.
SONET/SDH interfaces allow path trace bytes to be sent inband across the SONET/SDH link. Juniper
Networks 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.
Information about the HDLC configuration.
Policing bucketConfigured state of the receiving policer.
Shaping bucketConfigured state of the transmitting shaper.
Giant thresholdGiant threshold programmed into the hardware.
Runt thresholdRunt threshold programmed into the hardware.
Information about the configuration of the Packet Forwarding Engine:
Destination slotFPC slot number.
PLP bytePacket Level Protocol byte.
Information about the CoS queue for the physical interface.
CoS transmit queueQueue number and its associated user-configured forwarding class name.
Bandwidth %Percentage of bandwidth allocated to the queue.
Bandwidth bpsBandwidth allocated to the queue (in bps).
Buffer %Percentage of buffer space allocated to the queue.
Buffer usecAmount of buffer space allocated to the queue, in microseconds. This value is nonzero
only if the buffer size is configured in terms of time.
PriorityQueue priority: low or high.
LimitDisplayed 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.
Forwarding classes
Total number of forwarding classes supported on the specified interface.
Egress queues
639

Field Name
Field Description
Queue
Queue number.
Forwarding classes
Forwarding class name.
Queued Packets
Number of packets queued to this queue.
Queued Bytes
Number of bytes queued to this queue. The byte counts vary by PIC type.
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.
Tail-dropped packets
Number of packets dropped because of tail drop.
RED-dropped packets
Number of packets dropped because of random early detection (RED).
RED-dropped bytes
640
Low, non-TCPNumber of low-loss priority non-TCP packets dropped because of RED.
Low, TCPNumber of low-loss priority TCP packets dropped because of RED.
High, non-TCPNumber of high-loss priority non-TCP packets dropped because of RED.
High, TCPNumber of high-loss priority TCP packets dropped because of RED.
(MX Series routers with enhanced DPCs, and T Series routers with enhanced FPCs only) The output
classifies dropped packets into the following categories:
LowNumber of low-loss priority packets dropped because of RED.
Medium-lowNumber of medium-low loss priority packets dropped because of RED.
Medium-highNumber of medium-high loss priority packets dropped because of RED.
HighNumber of high-loss priority packets dropped because of RED.
Number of bytes dropped because of RED. The byte counts vary by PIC type.
Transmit rate
(M Series and T Series routers only) On M320 and M120 routers and the T Series routers, the total
number of dropped packets is displayed. On all other M Series routers, the output classifies dropped
packets into the following categories:
(M Series and T Series routers only) On M320 and M120 routers and the T Series routers, 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-TCPNumber of low-loss priority non-TCP bytes dropped because of RED.
Low, TCPNumber of low-loss priority TCP bytes dropped because of RED.
High, non-TCPNumber of high-loss priority non-TCP bytes dropped because of RED.
High, TCPNumber of high-loss priority TCP bytes dropped because of RED.
Configured transmit rate of the scheduler. The rate is a percentage of the total interface bandwidth.

Field Name
Field Description
Rate Limit
Rate limiting configuration of the queue. Possible values are :
NoneNo rate limit.
exactQueue transmits at the configured rate.
Buffer size
Delay buffer size in the queue.
Priority
Scheduling priority configured as low or high.
Excess Priority
Priority of the excess bandwidth traffic on a scheduler: low, medium-low, medium-high, high, or none.
Drop profiles
Display the assignment of drop profiles.
Loss priorityPacket loss priority for drop profile assignment.
ProtocolTransport protocol for drop profile assignment.
IndexIndex of the indicated object. Objects that have indexes in this output include schedulers
and drop profiles.
NameName of the drop profile.
TypeType of the drop profile: discrete or interpolated.
Fill LevelPercentage fullness of a queue.
Drop probabilityDrop probability at this fill level.
Excess Priority
Priority of the excess bandwidth traffic on a scheduler.
Drop profiles
Display the assignment of drop profiles.
Loss priorityPacket loss priority for drop profile assignment.
ProtocolTransport protocol for drop profile assignment.
IndexIndex of the indicated object. Objects that have indexes in this output include schedulers
and drop profiles.
NameName of the drop profile.
TypeType of the drop profile: discrete or interpolated.
Fill LevelPercentage fullness of a queue.
Drop probabilityDrop probability at this fill level.
641

Field Name
Field Description
Adjustment information
Display the assignment of shaping-rate adjustments on a scheduler node or queue.
642
Adjusting applicationApplication that is performing the shaping-rate adjustment.
The adjusting application can appear as ancp LS-0, which is the Junos OS Access Node Control
Profile process (ancpd) that performs shaping-rate adjustments on schedule nodes.
The adjusting application can also appear as pppoe, which adjusts the shaping-rate and
overhead-accounting class-of-service attributes on dynamic subscriber interfaces in a broadband
access network based on access line parameters in Point-to-Point Protocol over Ethernet
(PPPoE) Tags [TR-101]. This feature is supported on MPC/MIC interfaces on MX Series routers.
The shaping rate is based on the actual-data-rate-downstream attribute. The overhead
accounting value is based on the access-loop-encapsulation attribute and specifies whether
the access loop uses Ethernet (frame mode) or ATM (cell mode).
Adjustment typeType of adjustment: absolute or delta.
Configured shaping rateShaping rate configured for the scheduler node or queue.
Adjustment valueValue of adjusted shaping rate.
Adjustment targetLevel of shaping-rate adjustment performed: node or queue.
Adjustment overhead-accounting modeConfigured shaping mode: frame or cell.
Sample Output
show class-of-service
interface (Physical)
user@host> show class-of-service interface so-0/2/3

Physical interface: so-0/2/3, Index: 135
Queues supported: 8, Queues in use: 4
Total nondefault queues created: 4
Scheduler map: <default>, Index: 2032638653
Logical interface: fe-0/0/1.0, Index: 68, Dedicated Queues: no
Shaping rate: 32000
Object
Name
Type
Scheduler-map
<default>
Rewrite
exp-default
exp
Classifier
exp-default
exp
Classifier
ipprec-compatibility
ip
Forwardingclassmap
exp-default
exp
interface (Logical)
user@host> show class-of-service interface so-0/2/3.0

Logical interface: so-0/2/3.0, Index: 68, Dedicated
Shaping rate: 32000
Object
Name
Scheduler-map
<default>
Rewrite
exp-default
Classifier
exp-default
Classifier
Forwardingclassmap
exp-default
Index
27
21
5
8
5
Queues: no
Type
exp
exp
ip
exp
interface
(Gigabit Ethernet)
user@host> show class-of-service interface ge-6/2/0

Physical interface: ge-6/2/0, Index: 175
Input scheduler map: <default>, Index: 3
Chassis scheduler map: <default-chassis>, Index: 4
interface (PPPoE
Interface)
user@host> show class-of-service interface pp0.1

Logical interface: pp0.1, Index: 85
Object
Name
Traffic-control-profile tcp-pppoe.o.pp0.1
Classifier
Type
Output
ip
Index
27
21
5
8
5
Index
2726446535
13
Adjusting application: PPPoE

Adjustment type: absolute
Adjustment value: 5000000
Adjustment overhead-accounting mode: cell
Adjustment target: node
interface (T4000
user@host> show class-of-service interface xe-4/0/0

Physical interface: xe-4/0/0, Index: 153
643
Routers with Type 5

FPCs)
Shaping rate: 5000000000 bps

Congestion-notification: Disabled
Logical interface: xe-4/0/0.0, Index: 77
Object
Name
Type
Index
Classifier
ip
13
interface detail
user@host> show class-of-service interface ge-0/3/0 detail

Physical interface: ge-0/3/0, Enabled, Physical link is Up
Link-level type: Ethernet, MTU: 1518, Speed: 1000mbps, Loopback: Disabled,
Source filtering: Disabled, Flow control: Enabled, Auto-negotiation: Enabled,
Remote fault: Online
Device flags
: Present Running
Interface flags: SNMP-Traps Internal: 0x4000
Scheduler map: interface-schedular-map, Index: 58414
Input shaping rate: 10000 bps
Input scheduler map: schedular-map, Index: 15103
Chassis scheduler map: <default-chassis>, Index: 4
Logical interface ge-0/3/0.0
Flags: SNMP-Traps 0x4000 VLAN-Tag [ 0x8100.1 ]
inet
mpls
Interface
Admin Link Proto Input Filter
ge-0/3/0.0
up
up
inet
mpls
Interface
Admin Link Proto Input Policer
ge-0/3/0.0
up
up
inet
mpls
Logical interface: ge-0/3/0.0, Index: 68
Object
Name
Rewrite
exp-default
Classifier
exp-default
Classifier
644
Output Filter
Output Policer
Type
exp (mpls-any)
exp
ip
Logical interface ge-0/3/0.1

Flags: SNMP-Traps 0x4000 VLAN-Tag [ 0x8100.2 ]
inet
Interface
ge-0/3/0.1
up
up
inet
Interface
ge-0/3/0.1
up
up
inet
Object
Name
Classifier
Encapsulation: ENET2
Index
33
10
13
Encapsulation: ENET2
Output Filter
Output Policer
Type
ip
Index
13
user@host> show class-of-service interface so-1/3/0 comprehensive

interface
comprehensive

Link-level type: Ethernet, MTU: 1518, Speed: 1000mbps, BPDU Error: None,
MAC-REWRITE Error: None, Loopback: Disabled, Source filtering: Disabled, Flow
control: Enabled,
Auto-negotiation: Enabled, Remote fault: Online
Device flags
: Present Running
CoS queues
Schedulers
: 256
Hold-times
Current address: 00:14:f6:f4:b4:5d, Hardware address: 00:14:f6:f4:b4:5d
Last flapped
: 2010-09-07 06:35:22 PDT (15:14:42 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
IPv6 total statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Ingress traffic statistics at Packet Forwarding Engine:
Input bytes :
0
0 bps
Input packets:
0
0 pps
Drop
bytes :
0
0 bps
Drop
packets:
0
0 pps
Label-switched interface (LSI) traffic statistics:
Input bytes :
0
0 bps
Input packets:
0
0 pps
Input errors:
Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Policed discards: 0, L3
incompletes: 0, L2 channel errors: 0, L2 mismatch timeouts: 0, FIFO errors: 0,
Resource errors: 0
Output errors:
Carrier transitions: 5, Errors: 0, Drops: 0, Collisions: 0, Aged packets: 0,
FIFO errors: 0, HS link CRC errors: 0, MTU errors: 0, Resource errors: 0
Ingress queues: 4 supported, 5 in use
Queue counters:
Dropped packets
0 af3
1 af2
2 ef2
3 ef1

Queue counters:
Queued packets
Transmitted packets
Dropped packets
0 af3
1 af2
2 ef2
3 ef1
Active alarms
: None
645
Active defects : None

MAC statistics:
Receive
Transmit
Total octets
0
0
Total packets
0
0
Unicast packets
0
0
Broadcast packets
0
0
Multicast packets
0
0
CRC/Align errors
0
0
FIFO errors
0
0
MAC control frames
0
0
MAC pause frames
0
0
Oversized frames
0
Jabber frames
0
Fragment frames
0
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
0
Output packet pad count
0
Output packet error count
0
CAM destination filters: 0, CAM source filters: 0
Autonegotiation information:
Negotiation status: Complete
Link partner:
Link mode: Full-duplex, Flow control: Symmetric/Asymmetric, Remote fault:
OK
Local resolution:
Flow control: Symmetric, Remote fault: Link OK
Destination slot: 0
CoS information:
Direction : Output
CoS transmit queue
Bandwidth
Buffer Priority
Limit
%
bps
%
usec
2 ef2
39
19500
0
120
high
none
Direction : Input
CoS transmit queue
Bandwidth
Buffer Priority
Limit
%
bps
%
usec
0 af3
30
3000
45
0
low
none
Forwarding classes: 16 supported, 5 in use
Queue: 0, Forwarding classes: af3
Queued:
Packets
:
0
Bytes
:
0
Transmitted:
Packets
:
0
Bytes
:
0
Tail-dropped packets : Not Available
RED-dropped packets :
0
646
0 pps
0 bps
0 pps
0 bps
0 pps
RED-dropped bytes
:
Queued:
Packets
:
Bytes
:
Transmitted:
Packets
:
Bytes
:
RED-dropped bytes
:
Queue: 2, Forwarding classes: ef2
Queued:
Packets
:
Bytes
:
Transmitted:
Packets
:
Bytes
:
RED-dropped bytes
:
Queued:
Packets
:
Bytes
:
Transmitted:
Packets
:
Bytes
:
RED-dropped bytes
:
Forwarding classes: 16 supported, 5 in use
Queued:
Packets
:
Bytes
:
Transmitted:
Packets
:
Bytes
:
RL-dropped packets
:
RL-dropped bytes
:
RED-dropped bytes
:
Queued:
Packets
:
Bytes
:
Transmitted:
Packets
:
Bytes
:
RL-dropped packets
:
RL-dropped bytes
:
RED-dropped bytes
:
Queued:
Packets
:
Bytes
:
0 bps
0
0
0 pps
0 bps
0
0
0 pps
0 bps
0
0
0 pps
0 bps
0
0
0 pps
0 bps
0
0
0 pps
0 bps
0
0
0 pps
0 bps
0
0
0 pps
0 bps
0
0
0 pps
0 bps
0
0
0 pps
0 bps
0
0
0 pps
0 bps
0
0
0 pps
0 bps
0
0
0
0
0
0
0
0
0
0
0 pps
0 bps
0
0
0 pps
0 bps
0
0
0
0
0
0
0
0
0
0
0 pps
0 bps
pps
bps
pps
bps
pps
bps
pps
bps
647
Transmitted:
Packets
:
Bytes
:
RL-dropped packets
:
RL-dropped bytes
:
RED-dropped bytes
:
Queued:
Packets
:
Bytes
:
Transmitted:
Packets
:
Bytes
:
RL-dropped packets
:
RL-dropped bytes
:
RED-dropped bytes
:
0
0
0 pps
0 bps
0
0
0
0
0
0
0
0
0
0
0 pps
0 bps
0
0
0 pps
0 bps
0
0
0
0
0
0
0
0
Packet Forwarding Engine Chassis Queues:

Queues: 4 supported, 5 in use
Queued:
Packets
:
0
Bytes
:
0
Transmitted:
Packets
:
0
Bytes
:
0
Tail-dropped packets :
0
RED-dropped packets : Not Available
RED-dropped bytes
: Not Available
Queued:
Packets
:
0
Bytes
:
0
Transmitted:
Packets
:
0
Bytes
:
0
0
RED-dropped bytes
: Not Available
Queued:
Packets
:
0
Bytes
:
0
Transmitted:
Packets
:
0
Bytes
:
0
0
RED-dropped bytes
: Not Available
Queued:
Packets
:
108546
Bytes
:
12754752
Transmitted:
Packets
:
108546
Bytes
:
12754752
0
648
pps
bps
pps
bps
pps
bps
pps
bps
0 pps
0 bps
0 pps
0 bps
0 pps
0 pps
0 bps
0 pps
0 bps
0 pps
0 pps
0 bps
0 pps
0 bps
0 pps
0 pps
376 bps
0 pps
376 bps
0 pps
RED-dropped packets
RED-dropped bytes
: Not Available
: Not Available

Scheduler map: interface-schedular-map, Index: 58414
Scheduler: ef2, Forwarding class: ef2, Index: 39155
Transmit rate: 39 percent, Rate Limit: none, Buffer size: 120 us, Buffer
Limit: none, Priority: high
Excess Priority: unspecified
Drop profiles:
Loss priority
Protocol
Index
Name
Low
any
1
< default-drop-profile>
Medium low
any
1
Medium high
any
1
High
any
1
Drop profile: < default-drop-profile>, Type: discrete, Index: 1
Fill level
Drop probability
100
100
Fill level
Drop probability
100
100
Fill level
Drop probability
100
100
Fill level
Drop probability
100
100
Input shaping rate: 10000 bps
Input scheduler map: schedular-map
Scheduler map: schedular-map, Index: 15103
Scheduler: af3, Forwarding class: af3, Index: 35058
Transmit rate: 30 percent, Rate Limit: none, Buffer size: 45 percent, Buffer
Limit: none, Priority: low
Excess Priority: unspecified
Drop profiles:
Loss priority
Protocol
Index
Name
Low
any
40582
green
Medium low
any
1
Medium high
any
1
High
any
18928
yellow
Drop profile: green, Type: discrete, Index: 40582
Fill level
Drop probability
50
0
100
100
Fill level
Drop probability
100
100
Fill level
Drop probability
100
100
Drop profile: yellow, Type: discrete, Index: 18928
Fill level
Drop probability
50
0
100
100
Chassis scheduler map: < default-drop-profile>
649
Scheduler map: < default-drop-profile>, Index: 4

Scheduler: < default-drop-profile>, Forwarding class: af3, Index: 25
Excess Priority: low
Drop profiles:
Loss priority
Protocol
Index
Name
Low
any
1
Medium low
any
1
Medium high
any
1
High
any
1
Fill level
Drop probability
100
100
Fill level
Drop probability
100
100
Fill level
Drop probability
100
100
Fill level
Drop probability
100
100
Scheduler: < default-drop-profile>, Forwarding class: af2, Index: 25
Drop profiles:
Loss priority
Protocol
Index
Name
Low
any
1
Medium low
any
1
Medium high
any
1
High
any
1
Fill level
Drop probability
100
100
Fill level
Drop probability
100
100
Fill level
Drop probability
100
100
Fill level
Drop probability
100
100
Scheduler: < default-drop-profile>, Forwarding class: ef2, Index: 25
Drop profiles:
Loss priority
Protocol
Index
Name
Low
any
1
Medium low
any
1
Medium high
any
1
High
any
1
Fill level
Drop probability
100
100
650

Fill level
Drop probability
100
100
Fill level
Drop probability
100
100
Fill level
Drop probability
100
100
Scheduler: < default-drop-profile>, Forwarding class: ef1, Index: 25
Drop profiles:
Loss priority
Protocol
Index
Name
Low
any
1
Medium low
any
1
Medium high
any
1
High
any
1
Drop profile: , Type: discrete, Index: 1
Fill level
Drop probability
100
100
Fill level
Drop probability
100
100
Fill level
Drop probability
100
100
Fill level
Drop probability
100
100
Forwarding class
ID
Queue Restricted queue Fabric
priority Policing priority
af3
0
0
0
low
normal
af2
1
1
1
low
normal
ef2
2
2
2
high
normal
ef1
3
3
3
high
normal
af1
4
4
0
low
normal
Logical interface ge-0/3/0.0 (Index 68) (SNMP ifIndex 152) (Generation 159)
Flags: SNMP-Traps 0x4000 VLAN-Tag [ 0x8100.1 ] Encapsulation: ENET2
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Local statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Transit statistics:
Input bytes :
0
0 bps
Output bytes :
0
0 bps
651
Input packets:
0
0 pps
Output packets:
0
0 pps
Protocol inet, MTU: 1500, Generation: 172, Route table: 0
Flags: Sendbcast-pkt-to-re
Input Filters: filter-in-ge-0/3/0.0-i,
Policer: Input: p1-ge-0/3/0.0-inet-i
Protocol mpls, MTU: 1488, Maximum labels: 3, Generation: 173, Route table: 0
Flags: Is-Primary
Output Filters: exp-filter,,,,,
Logical interface ge-0/3/0.0 (Index 68) (SNMP ifIndex 152)
Input packets : 0
Output packets: 0
Interface
ge-0/3/0.0
Interface
ge-0/3/0.0
Admin Link Proto

up
up
inet
mpls
Admin Link Proto
up
up
inet
mpls
Input Filter
Output Filter
filter-in-ge-0/3/0.0-i
exp-filter
Input Policer
Output Policer
p1-ge-0/3/0.0-inet-i
Filter: filter-in-ge-0/3/0.0-i
Counters:
Name
count-filter-in-ge-0/3/0.0-i
Filter: exp-filter
Counters:
Name
count-exp-seven-match
count-exp-zero-match
Policers:
Name
p1-ge-0/3/0.0-inet-i
exp-default
Rewrite rule: exp-default, Code point

Forwarding class
af3
af3
af2
af2
ef2
ef2
ef1
ef1
Object
Name
Classifier
Packets
0
Bytes
0
0
Packets
0
0
Packets
0

Object
Name
Rewrite
Bytes
0
Type
exp (mpls-any)
type: exp, Index: 33

Loss priority
Code point
low
000
high
001
low
010
high
011
low
100
high
101
low
110
high
111
Type
exp-default
exp
Index
33
Index
10
Classifier: exp-default, Code point type: exp, Index: 10

Code point
Forwarding class
Loss priority
000
af3
low
652
001
010
011
100
101
110
111
Object
Classifier
af3
af2
af2
ef2
ef2
ef1
ef1
high
low
high
low
high
low
high
Name
Type
ip
Index
13
Classifier: ipprec-compatibility, Code point type: inet-precedence, Index: 13

Code point
Forwarding class
Loss priority
000
af3
low
001
af3
high
010
af3
low
011
af3
high
100
af3
low
101
af3
high
110
ef1
low
111
ef1
high
Forwarding class
ID
af3
0
0
0
low
normal
af2
1
1
1
low
normal
ef2
2
2
2
high
normal
ef1
3
3
3
high
normal
af1
4
4
0
low
normal
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
Flags: Sendbcast-pkt-to-re
Logical interface ge-0/3/0.1 (Index 69) (SNMP ifIndex 154)
Input packets : 0
Output packets: 0
Interface
Output Filter
653
ge-0/3/0.1
Interface
ge-0/3/0.1
up
up
mpls
up
up
mpls
Output Policer

Object
Name
Classifier
Type
Index
ip
13
Classifier: ipprec-compatibility, Code point type: inet-precedence, Index: 13

Code point
Forwarding class
Loss priority
000
af3
low
001
af3
high
010
af3
low
011
af3
high
100
af3
low
101
af3
high
110
ef1
low
111
ef1
high
Forwarding class
ID
af3
0
0
0
low
normal
af2
1
1
1
low
normal
ef2
2
2
2
high
normal
ef1
3
3
3
high
normal
af1
4
4
0
low
normal
interface (ACX Series
Routers)
user@host-g11# show class-of-service interface

Physical interface: at-0/0/0, Index: 130
Logical interface: at-0/0/0.0, Index: 69
Physical interface: at-0/0/1, Index: 133
Object
Name
Rewrite
dscp-default
Classifier
d1
654
Type
dscp
dscp
Index
31
11331
Classifier
ci

Object
Name
Rewrite
custom-exp
ieee8021p
583
Type
exp (mpls-any)
Index
46413
Type
ip
Index
13

Object
Name
Rewrite
ri
Classifier
ci
Type
ieee8021p (outer)
ieee8021p
Index
35392
583

Object
Name
Classifier
Type
ip
Index
13

Object
Name
Rewrite
custom-exp2
Type
exp (mpls-any)
Index
53581

Object
Name
Classifier
Type
ip
Index
13

Object
Name
Classifier
Type
ip
Index
13

Object
Name
Classifier
Type
ip
Index
13

Object
Name
Classifier

655

Object
Name
Classifier
d1
Type
dscp
Index
11331

Object
Name
Classifier
Type
ip
Index
13

Object
Name
Classifier
Type
ip
Index
13
Type
ip
Index
13
Type
ip
Index
13

Object
Name
Classifier
Object
Name
Classifier
[edit]
user@host-g11#
656
show class-of-service system-defaults

Syntax
Release Information
Description
Options
routers.
Display classifiers configured under system-defaults.
Required Privilege
Level
Related
Documentation
Output Fields
view
system-defaults
show class-of-service system-defaults on page 657

Table 46 on page 657 describes the output fields for the show class-of-service
system-defaults command. Output fields are listed in the order in which they appear.
Table 46: show class-of-service system-defaults Output Fields

Field Name
Field Description
Object
Category of an object: Classifier
Name
Name of an object
Type
Type of an object: exp is the only type allowed.
Index
Index of the indicated classifier
Sample Output
system-defaults
user@hostshow class-of-service system-defaults

Object
Name
Classifier
e1
Type
exp
Index
9280
657

Syntax

Syntax
Syntax for EX Series switches:

Release Information
Description
Options

Switches.
Display Dynamic Host Configuration Protocol (DHCP) relay statistics.
logical-system logical-system-name(On routers only) (Optional) Perform this operation
on the specified logical system. If you do not specify a logical system name, statistics
are displayed for the default logical system.
routing instance. If you do not specify a routing instance name, statistics are displayed
for the default routing instance.
Required Privilege
Level
Related
Documentation
Output Fields
658
view
clear dhcp relay statistics on page 328
show dhcp relay statistics on page 660

Table 47 on page 659 lists the output fields for the show dhcp relay statistics command.
Table 47: show dhcp relay statistics Output Fields

Field Name
Field Description
Packets dropped
Number of packets discarded by the extended DHCP relay agent application due to errors. Only
nonzero statistics appear in the Packets dropped output. When all of the Packets dropped statistics
are 0 (zero), only the Total field appears.
TotalTotal number of packets discarded by the extended DHCP relay agent application.
Bad hardware addressNumber of packets discarded because an invalid hardware address was
specified.
Bad opcodeNumber of packets discarded because an invalid operation code was specified.
Bad optionsNumber of packets discarded because invalid options were specified.
Invalid server addressNumber of packets discarded because an invalid server address was specified.
No available addressesNumber of packets discarded because there were no addresses available
for assignment.
No interface matchNumber of packets discarded because they did not belong to a configured
interface.
No routing instance matchNumber of packets discarded because they did not belong to a configured
routing instance.
Messages received
Messages sent
Packets forwarded
No valid local addressNumber of packets discarded because there was no valid local address.
Packet too shortNumber of packets discarded because they were too short.
Read errorNumber of packets discarded because of a system read error.
Send errorNumber of packets that the extended DHCP relay application could not send.
Option 60Number of packets discarded containing DHCP option 60 vendor-specific information.
Option 82Number of packets discarded because DHCP option 82 information could not be added.
Number of DHCP messages received.
BOOTREQUESTNumber of BOOTP protocol data units (PDUs) received
DHCPDECLINENumber of DHCP PDUs of type DECLINE received
DHCPDISCOVERNumber of DHCP PDUs of type DISCOVER received
DHCPINFORMNumber of DHCP PDUs of type INFORM received
DHCPRELEASENumber of DHCP PDUs of type RELEASE received
DHCPREQUESTNumber of DHCP PDUs of type REQUEST received
Number of DHCP messages sent.
BOOTREPLYNumber of BOOTP PDUs transmitted
DHCPOFFERNumber of DHCP OFFER PDUs transmitted
DHCPACKNumber of DHCP ACK PDUs transmitted
DHCPNACKNumber of DHCP NACK PDUs transmitted
DHCPFORCERENEWNumber of DHCP FORCERENEW PDUs transmitted
Number of packets forwarded.
BOOTREQUESTNumber of BOOTREQUEST protocol data units (PDUs) forwarded
BOOTREPLYNumber of BOOTREPLY protocol data units (PDUs) forwarded
659
Sample Output
show dhcp relay
statistics
660

Packets dropped:
Total
30
Bad hardware address
1
Bad opcode
1
Bad options
3
Invalid server address
5
No available addresses
1
No interface match
2
No routing instance match 9
No valid local address
4
Packet too short
2
Read error
1
Send error
1
Option 60
1
Option 82
2
Messages received:
BOOTREQUEST
DHCPDECLINE
DHCPDISCOVER
DHCPINFORM
DHCPRELEASE
DHCPREQUEST
116
0
11
0
0
105
Messages sent:
BOOTREPLY
DHCPOFFER
DHCPACK
DHCPNAK
DHCPFORCERENEW
0
2
1
0
0
Packets forwarded:
Total
BOOTREQUEST
BOOTREPLY
4
2
2
show dhcp relay binding

Syntax
Release Information
show dhcp relay binding

<address>
<brief>
<detail>
<interfaces-vlan>
<ip-address | mac-address>
<summary>

Options interface and mac-address added in Junos OS Release 8.4.
Options interfaces-vlan and interfaces-wildcard added in Junos OS Release 12.1.
Switches.
Description
Display the address bindings in the Dynamic Host Configuration Protocol (DHCP) client
table.
Options
address(Optional) Display DHCP binding information for a specific client identified by
one of the following entries:
ip-addressThe specified IP address.
mac-addressThe specified MAC address.
session-idThe specified session ID.
brief(Optional) Display brief information about the active client bindings. This is the
default, and produces the same output as show dhcp relay binding.
detail(Optional) Display detailed client binding information.
interface interface-name(Optional) Perform this operation on the specified interface.
You can optionally filter on VLAN ID and SVLAN ID.

interfaces-vlan(Optional) Show the binding state information on the interface VLAN
ID and S-VLAN ID.

interfaces-wildcard(Optional) The set of interfaces on which to show binding state
information. This option supports the use of the wildcard character (*).
logical-system logical-system-name(Optional) Perform this operation on the specified
logical system.
routing instance.
summary(Optional) Display a summary of DHCP client information.
661
Required Privilege
Level
Related
Documentation
Output Fields
view
Clearing DHCP Bindings for Subscriber Access
clear dhcp relay binding on page 331
show dhcp relay binding on page 664

show dhcp relay binding detail on page 664
show dhcp relay binding interface on page 664
show dhcp relay binding interface vlan-id on page 664
show dhcp relay binding interface svlan-id on page 664
show dhcp relay binding ip-address on page 665
show dhcp relay binding mac-address on page 665
show dhcp relay binding session-id on page 665
show dhcp relay binding <interfaces-vlan> on page 665
show dhcp relay binding <interfaces-wildcard> on page 665
show dhcp relay binding summary on page 665
Table 48 on page 662 lists the output fields for the show dhcp relay binding command.
Table 48: show dhcp relay binding Output Fields

Level of
Output
Field Name
Field Description
number clients,(number init, number bound,

number selecting, number requesting, number
renewing,number rebinding, number
releasing)
Summary counts of the total number of DHCP clients and the

number of DHCP clients in each state.
summary
IP address
IP address of the DHCP client.
briefdetail
Session Id
Session ID of the subscriber session.
briefdetail
Hardware address
Hardware address of the DHCP client.
briefdetail
Expires
Number of seconds in which the lease expires.
briefdetail
State
State of the DHCP relay address binding table on the DHCP

client:
briefdetail
BOUNDClient has an active IP address lease.
INITInitial state.
REBINDINGClient is broadcasting a request to renew the
IP address lease.
RELEASEClient is releasing the IP address lease.
RENEWINGClient is sending a request to renew the IP
address lease.
662
REQUESTINGClient is requesting a DHCP server.
SELECTINGClient is receiving offers from DHCP servers.
Table 48: show dhcp relay binding Output Fields (continued)

Field Name
Field Description
Level of
Output
Interface
Incoming client interface.
brief
Lease Expires
Date and time at which the clients IP address lease expires.
detail
Lease Expires in
Number of seconds in which the lease expires.
detail
Lease Start
Date and time at which the clients IP address lease started.
detail
Incoming Client Interface
Clients incoming interface.
detail
Server IP Address
IP address of the DHCP server.
detail
Server Interface
Interface of the DHCP server.
detail
Bootp Relay Address
IP address of BOOTP relay.
detail
Type
Type of DHCP packet processing performed on the router:
All levels
activeRouter actively processes and relays DHCP packets.
passiveRouter passively snoops DHCP packets passing
through the router.

Lease expires at
Date and time at which the clients IP address lease expires.
All levels
663
Sample Output
show dhcp relay
binding
show dhcp relay

binding detail
show dhcp relay

binding interface

IP address
Session Id Hardware address
100.20.32.11
41
00:10:94:00:00:01
Expires
86371
State
BOUND
Interface
ge-1/0/0.0
100.20.32.12
42
00:10:94:00:00:02
86371
BOUND
ge-1/0/0.0
100.20.32.13
43
00:10:94:00:00:03
86371
BOUND
ge-1/0/0.0
100.20.32.14
44
00:10:94:00:00:04
86371
BOUND
ge-1/0/0.0
100.20.32.15
45
00:10:94:00:00:05
86371
BOUND
ge-1/0/0.0
user@host> show dhcp relay binding detail
Client IP Address: 100.20.32.11

Hardware Address:
State:
Lease Expires:
Lease Expires in:
Lease Start:
Last Packet Received:
Incoming Client Interface:
Server Ip Address:
Server Interface:
Bootp Relay Address:
Session Id:
00:10:94:00:00:01
BOUND(DHCP_RELAY_STATE_BOUND_ON_INTF_DELETE)
2009-07-21 11:00:06 PDT
86361 seconds
2009-07-20 11:00:06 PDT
20090720 11:00:06 PDT
ge-1/0/0.0
100.20.22.2
none
100.20.32.2
41
Client IP Address: 100.20.32.12

Hardware Address:
State:
Lease Expires:
Lease Expires in:
Lease Start:
Last Packet Received:
Incoming Client Interface:
Server Ip Address:
Server Interface:
Bootp Relay Address:
Session Id:
00:10:94:00:00:02
BOUND(DHCP_RELAY_STATE_BOUND_ON_INTF_DELETE)
2009-07-21 11:00:06 PDT
86361 seconds
2009-07-20 11:00:06 PDT
20090720 11:00:06 PDT
ge-1/0/0.0
100.20.22.2
none
100.20.32.2
42
user@host> show dhcp relay binding interface fe-0/0/2

IP address
100.20.32.1
show dhcp relay

binding interface
vlan-id
Hardware address
90:00:00:01:00:01
Type
active
Lease expires at
2007-03-27 15:06:20 EDT
user@host> show dhcp relay binding interface ge-1/1/0:100

IP address
200.20.20.15
ge-1/1/0:100
Session Id
6
Hardware address
Expires
00:10:94:00:00:01 86124
State
BOUND
Interface
user@host> show dhcp relay binding interface ge-1/1/0:10-100
664
show dhcp relay

binding interface
svlan-id
IP address
200.20.20.16
ge-1/1/0:10-100
Session Id
7
Hardware address
Expires
00:10:94:00:00:02 86124
State
BOUND
Interface
show dhcp relay

binding ip-address
user@host> show dhcp relay binding 100.20.32.13

IP address
100.20.32.13
43
00:10:94:00:00:03
Expires
86293
State
BOUND
Interface
ge-1/0/0.0
show dhcp relay

binding mac-address
user@host> show dhcp relay binding 00:10:94:00:00:05

IP address
Expires
100.20.32.15
45
00:10:94:00:00:05 86279
State
BOUND
Interface
ge-1/0/0.0
show dhcp relay

binding session-id
user@host> show dhcp relay binding 41

IP address
100.20.32.11
41
00:10:94:00:00:01
State
BOUND
Interface
ge-1/0/0.0
show dhcp relay

binding
<interfaces-vlan>
user@host> show dhcp relay binding ge-1/0/0:100-200

IP address
Expires
192.168.0.17
42
00:10:94:00:00:02 86346
ge-1/0/0.1073741827
192.168.0.16
41
00:10:94:00:00:01 86346
ge-1/0/0.1073741827
show dhcp relay

binding
show dhcp relay

binding summary
Expires
86305
user@host> show dhcp relay binding ge-1/3/*

IP address
Expires
192.168.0.9
24
00:10:94:00:00:04 86361
ge-1/3/0.110
192.168.0.8
23
00:10:94:00:00:03 86361
ge-1/3/0.110
192.168.0.7
22
00:10:94:00:00:02 86361
ge-1/3/0.110
State
BOUND
Interface
BOUND
State
BOUND
Interface
BOUND
BOUND
user@host> show dhcp relay binding summary

3 clients, (2 init, 1 bound, 0 selecting, 0 requesting, 0 renewing, 0 rebinding,
0 releasing)
665
show interfaces (ATM)

Syntax
Release Information
Description
Options
show interfaces at-fpc/pic/port

<brief | detail | extensive | terse>
<descriptions>
<media>
<snmp-index snmp-index>
<statistics>

(M Series and T Series routers only) Display status information about the specified ATM
interface.
at-fpc/pic/portDisplay standard information about the specified ATM interface.
brief | detail | extensive | terse(Optional) Display the specified level of output.
descriptions(Optional) Display interface description strings.
media(Optional) Display media-specific information about network interfaces.
snmp-index snmp-index(Optional) Display the SNMP index of the interface.
statistics(Optional) Display static interface statistics.
Required Privilege
Level
Output Fields
view
show interfaces (ATM, IMA Group) on page 682

show interfaces extensive (ATM IMA Group) on page 682
show interfaces (ATM1, SONET Mode) on page 683
show interfaces brief (ATM1, SONET Mode) on page 684
show interfaces detail (ATM1, SONET Mode) on page 684
show interfaces extensive (ATM1, SONET Mode) on page 685
show interfaces (ATM2, SDH Mode) on page 687
show interfaces brief (ATM2, SDH Mode) on page 688
show interfaces detail (ATM2, SDH Mode) on page 689
show interfaces extensive (ATM2, SDH Mode) on page 690
show interfaces (ATM2, SONET Mode) on page 693
show interfaces brief (ATM2, SONET Mode) on page 694
show interfaces detail (ATM2, SONET Mode) on page 695
show interfaces extensive (ATM2, SONET Mode) on page 697
Table 49 on page 666 lists the output fields for the show interfaces (ATM) command.
Table 49: ATM show interfaces Output Fields

Field Name
Field Description
Level of Output
Physical Interface
666
Table 49: ATM show interfaces Output Fields (continued)

Field Name
Field Description
Level of Output
Physical interface
Name of the physical interface.
All levels
Enabled
State of the interface. Possible values are described in the Enabled Field
section under Common Output Fields Description.
All levels
Description
Configured interface description.
All levels
Interface index
Physical interface's index number, which reflects its initialization sequence.
detail extensive none
SNMP ifIndex
SNMP index number for the physical interface.
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-RELAYATM cell relay for CCC.
ATM-CCC-VC-MUXATM virtual circuit (VC) for CCC.
ATM-CISCO-NLPIDCisco-compatible ATM NLPID encapsulation.
ATM-MIPP-LLCATM MLPPP over ATM Adaptation Layer 5 (AAL5)/logical
link control (LLC).
ATM-NLPIDATM NLPID encapsulation.
ATM-PPP-LLCATM PPP over AAL5/LLC.
ATM-PPP-VC-MUXATM PPP over raw AAL5.
ATM-PVCATM permanent virtual circuits.
ATM-SNAPATM LLC/SNAP encapsulation.
ATM-TCC-SNAPATM LLC/SNAP for translational cross-connection.
ATM-TCC-VC-MUXATM VC for translational cross-connection.
ATM-VC-MUXATM VC multiplexing.
ETHER-OVER-ATM-LLCEthernet over ATM (LLC/SNAP) encapsulation.
ETHER-VPLS-OVER-ATM-LLCEthernet VPLS over ATM (bridging)
encapsulation.
MTU
All levels
Clocking
Reference clock source: Internal or External.
All levels
framing Mode
Framing mode: SONET or SDH.
All levels
Speed
Speed at which the interface is running as represented by the interface type

(for example, OC3, ADSL2+, and SHDSL(2-wire).
All levels
Loopback
Whether loopback is enabled and the type of loopback (local or remote).
All levels
Payload scrambler
Whether payload scrambling is enabled.
All levels
Device flags
Information about the physical device. Possible values are described in the
Device Flags section under Common Output Fields Description.
All levels
667

Field Name
Field Description
Level of Output
Link flags
Information about the link. Possible values are described in the Link Flags
All levels
CoS queues
Hold-times
detail extensive
Current address
Ethernet MAC address for this interface for Ethernet over ATM encapsulation.
Last flapped
Date, time, and how long ago the interface went from down to up. The format
is Last flapped: year-month-day hour:minute:second timezone (hour:minute:second
ago). For example, Last flapped: 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
Output Rate
Output rate in bps and pps.
None specified
Statistics last
cleared
Time when the statistics for the interface were last set to zero.
detail extensive
Traffic statistics
Statistics for traffic on the interface.
detail extensive
Input errors
Input bytesNumber of bytes received on the interface
Input packetsNumber of packets received on the interface
Input errors on the interface whose definitions are as follows:
extensive
ErrorsSum of the incoming frame aborts and frame check sequence (FCS)
errors.
DropsNumber 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 VCsNumber of cells that arrived for a nonexistent VC.
Framing errorsSum of AAL5 packets that have FCS errors, reassembly
timeout errors, and length errors.
Policed discardsNumber of frames that the incoming packet match code
discarded because they were not recognized or not of interest. Usually, this
field reports protocols that the Junos OS does not handle.
L3 incompletesNumber 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 errorsNumber of times the software did not find a valid logical
interface for an incoming frame.
L2 mismatch timeoutsNumber of malformed or short packets that caused
the incoming packet handler to discard the frame as unreadable.
668
Resource errorsSum of transmit drops.

Field Name
Field Description
Level of Output
Output errors
Output errors on the interface. The following paragraphs explain the counters
whose meaning might not be obvious:
extensive
Carrier transitionsNumber 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.
DropsNumber of packets dropped by the output queue of the I/O Manager
packet that is dropped by the ASIC's RED mechanism.
Aged packetsNumber of packets that remained so long in shared packet
SDRAM 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 errorsNumber of packets larger than the MTU threshold.
Egress queues
detail extensive
Queue counters
detail extensive
NOTE: Physical interface queue counters of ATM2 PICs displayed by the show
interfaces at-fpc/pic/port detail command show the packet forwarding stream
statistics associated with the ATM2 ports. Since multiple ports of the ATM2
PICs (except for the ATM2 dual-port OC12) share one packet forwarding stream,
the physical interface queue counters reflect the aggregate of ATM2 port
statistics.
SONET alarms
SONET defects
SONET media-specific defects that prevent the interface from passing packets.
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 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.
669

Field Name
Field Description
Level of Output
SONET PHY
extensive
StateState of the error. State other than OK indicates a problem.
Subfields are:
SONET section
extensive
Subfields are:
SONET line
LOLLoss of light
LOFLoss of frame
ES-SErrored seconds (section)
SES-SSeverely errored seconds (section)
SEFS-SSeverely errored framing seconds (section)
Active alarms and defects, plus counts of specific SONET errors with detailed
information.
extensive
Subfields are:
670
BIP-B2Bit interleaved parity for SONET line overhead
REI-LRemote error indication (near-end line)
RDI-LRemote defect indication (near-end line)
AIS-LAlarm indication signal (near-end line)
BERR-SFBit error rate fault signal failure
BERR-SDBit error rate defect signal degradation
ES-LErrored seconds (near-end line)
SES-LSeverely errored seconds (near-end line)
UAS-LUnavailable seconds (near-end line)
ES-LFEErrored seconds (far-end line)
SES-LFESeverely errored seconds (far-end line)
UAS-LFEUnavailable seconds (far-end line)

Field Name
Field Description
Level of Output
SONET path
Active alarms and defects, plus counts of specific SONET errors with detailed
information.
extensive
Subfields are:
Received SONET
overhead
REI-PRemote error indication
LOP-PLoss of pointer (path)
AIS-PPath alarm indication signal
RDI-PPath remote defect indication
UNEQ-PPath unequipped
PLM-PPath payload (signal) label mismatch
ES-PErrored seconds (near-end STS path)
SES-PSeverely errored seconds (near-end STS path)
UAS-PUnavailable seconds (near-end STS path)
ES-PFEErrored seconds (far-end STS path)
SES-PFESeverely errored seconds (far-end STS path)
UAS-PFEUnavailable seconds (far-end STS path)
Transmitted
SONET overhead
extensive
C2Signal label. Allocated to identify the construction and content of the
STS-level SPE and for PDI-P.
K1 and K2These bytes are allocated for APS signaling for the protection of
the multiplex section.
J0Section 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.
S1Synchronization status. The S1 byte is located in the first STS-1 of an
STS-N.
SDH alarms
SDH defects
Z3 and Z4Allocated for future use.
SDH media-specific defects that can prevent the interface from passing packets.
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 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.
All levels
671

Field Name
Field Description
Level of Output
SDH PHY
Active alarms and defects, plus counts of specific SDH errors with detailed
information.
extensive
Subfields are:
SDH regenerator
section
information.
extensive
Subfields are:
SDH multiplex
section
RS-BIP824-bit BIP for multiplex section overhead (B2 bytes)
OOFOut of frame
LOSLoss of signal
LOFLoss of frame
RS-ESErrored seconds (near-end regenerator section)
RS-SESSeverely errored seconds (near-end regenerator section)
RS-SEFSSeverely errored framing seconds (regenerator section)
information.
extensive
Subfields are:
672
MS-BIP248-bit BIP for high-order path overhead (B3 byte)
MS-FEBEFar-end block error (multiplex section)
MS-FERFFar-end remote fail (multiplex section)
MS-AISAlarm indication signal (multiplex section)
BERR-SFBit error rate fault (signal failure)
BERR-SDBit error rate defect (signal degradation)
MS-ESErrored seconds (near-end multiplex section)
MS-SESSeverely errored seconds (near-end multiplex section)
MS-UASUnavailable seconds (near-end multiplex section)
MS-ES-FEErrored seconds (far-end multiplex section)
MS-SES-FESeverely errored seconds (far-end multiplex section)
MS-UAS-FEUnavailable seconds (far-end multiplex section)

Field Name
Field Description
Level of Output
SDH path
information.
extensive
Subfields are:
Received SDH
overhead
HP-BIP88-bit BIP for regenerator section overhead (B1 byte)
HP-FEBEFar-end block error (high-order path)
HP-LOPLoss of pointer (high-order path)
HP-AISHigh-order-path alarm indication signal
HP-FERFFar-end remote fail (high-order path)
HP-UNEQUnequipped (high-order path)
HP-PLMPayload label mismatch (high-order path)
HP-ESErrored seconds (near-end high-order path)
HP-SESSeverely errored seconds (near-end high-order path)
HP-UASUnavailable seconds (near-end high-order path)
HP-ES-FEErrored seconds (far-end high-order path)
HP-SES-FESeverely errored seconds (far-end high-order path)
HP-UAS-FEUnavailable seconds (far-end high-order path)
Transmitted SDH
overhead
extensive
C2Signal label. This byte is allocated to identify the construction and content
of the STS-level SPE and for PDI-P.
K1 and K2These bytes are allocated for APS signaling for the protection of
the multiplex section.
J0Section trace. This byte is defined for STS-1 number 1 of an STS-N signal.
This bye is 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.
S1Synchronization status. The S1 byte is located in the first STS-1 of an
STS-N.
Received path trace

Transmitted path
trace
Z3 and Z4These bytes are allocated for future use.
SONET/SDH interfaces allow path trace bytes to be sent inband across the
SONET/SDH link. Juniper Networks 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.
extensive
673

Field Name
Field Description
Level of Output
ATM Status
ATM state information:
extensive
HCS StateStatus of the header check sequence. ATM uses the HCS field in
the cell header in the cell delineation process to frame ATM cell boundaries.
The HCS is an FCS-8 calculation over the first four octets of the ATM cell
header.
LOCCurrent loss of cell (LOC) delineation state. OK means that no LOC is
currently asserted.
674

Field Name
Field Description
Level of Output
ATM Statistics
ATM statistics for the interface:
extensive
Uncorrectable HCS errorsNumber of cells dropped because the cell
delineation failed. These errors most likely indicate that a SONET/SDH layer
problem has occurred.
Correctable HCS errorsNumber of correctable HCS errors that occurred. The
cell delineation process can recover from these errors and locate the ATM
cell boundary, although the framing process is not quite stable. The ATM cell
is not dropped. This counter increases when the cell delineation process
changes its state from present to sync (for example, when a cable is plugged
into the interface).
The following error statistics are from the framer:
Tx cell FIFO overrunsNumber of overruns in the transmit FIFO.
Rx cell FIFO overrunsNumber of overruns in the receive FIFO.
Rx cell FIFO underrunsNumber of underruns in the receive FIFO.
Input cell countNumber of ATM cells received by the interface (not including
idle cells).
Output cell countNumber of ATM cells transmitted by the interface (including
idle cells).
Output idle cell countNumber of idle cells sent by the port. When ATM has
nothing to send, it sends idle cells to fill the time slot.
Output VC queue dropsNumber of packets dropped by a port on the PIC.
Packets are dropped because of queue limits on the VCs.

The following error statistics are from the SAR:
Input no buffersNumber of AAL5 packets dropped because no channel
blocks or buffers were available to handle them.
Input length errorsNumber of AAL5 packets dropped because their length
was incorrect. Usually, these errors occur because a cell has been corrupted
or lost, or because the length field was corrupted. They can also mean the
AAL5 length field was zero.
Input timeoutsNumber of AAL5 packets dropped because of a reassembly
timeout.
Input invalid VCsNumber of AAL5 packets dropped because the header
was unrecognized (because the VC was not correct or not configured).
Input bad CRCsNumber of AAL5 packets dropped because of frame check
sequence errors.
Input OAM cell no buffersNumber of received OAM cells or raw cells dropped
because no buffers were available to handle them.
L2 circuit out-of-sequence packets(Layer 2 AAL5 mode) Number of AAL5
packets that are out of sequential order.
Denied packets countThe number of packets dropped due to VLAN priority
deny packets or due to an error forwarding configuration that might cause a

negative frame length, that is, the stripping size is larger than the packet size.
Packet Forwarding
Engine
configuration
extensive
675

Field Name
Field Description
Level of Output
CoS information
extensive
CoS transmit queueQueue number and its associated user-configured
forwarding class name.
Buffer usecAmount of buffer space allocated to the queue, in microseconds.
This value is nonzero only if the buffer size is configured in terms of time.
LimitDisplayed 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.
676

Field Name
Field Description
Level of Output
VPI
(ATM2) Virtual path identifier information:
FlagsVPI flags can be one or more of the following:
Active (virtual path is up)
OAM (operation and maintenance is enabled)
Shaping (shaping is configured)
CBR, Peak
OAM, PeriodInterval at which OAM F4 loopback cells are sent.
Up countNumber of F4 OAM cells required to consider the virtual path up;

the range is 1 through 255.
Down countNumber of F4 OAM cells required to consider the virtual path

down; the range is 1 through 255.
Total down timeTotal number of seconds the VPI has been down since it
was opened, using the format Total down time: hh:mm:ss or Never.
Last downTime of last Down transition, using the format Last down: hh:mm:ss
ago or Never.
OAM F4 cell statistics(Nonpromiscuous mode) OAM F4 statistics:
Total receivedNumber of OAM F4 cells received.
Total sentNumber of OAM F4 cells sent.
Loopback receivedNumber of OAM F4 loopback cells received.
Loopback sentNumber of OAM F4 loopback cells sent.
Last receivedTime at which the last OAM F4 cell was received.
Last sentTime at which the last OAM F4 cell was sent.
RDI receivedNumber of OAM F4 cells received with the remote defect
indication bit set.
RDI sentNumber of OAM F4 cells sent with the RDI bit set.
AIS receivedNumber of OAM F4 cells received with the alarm indication
signal bit set.
AIS sentNumber of OAM F4 cells sent with the AIS bit set.
Traffic statistics:
Input bytesNumber of bytes received on the VPI.
Output bytesNumber of bytes transmitted on the VPI.
Input packetsNumber of packets received on the VPI.
Output packetsNumber of packets transmitted on the VPI.
Logical Interface
Logical interface
Name of the logical interface.
All levels
Index
Logical interface index number, which reflects its initialization sequence.
SNMP ifIndex
Logical interface SNMP interface index number.
Generation
detail extensive
677

Field Name
Field Description
Level of Output
Flags
Information about the logical interface. Possible values are described in the
Logical Interface Flags section under Common Output Fields Description.
All levels
Input packets
Number of packets received on the logical interface.
None specified
Output packets
Number of packets transmitted on the logical interface.
None specified
Encapsulation
All levels
Traffic statistics
Total number of bytes and packets received and transmitted on the logical
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 a while (generally, less than 1 second) for this
counter to stabilize.
detail extensive
Local statistics
Statistics for traffic received from and transmitted to the Routing 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 a while (generally, less than 1 second) for this
counter to stabilize.
detail extensive
Transit statistics
Statistics for traffic transiting the router. When a burst of traffic is received, the
value in the output packet rate field might briefly exceed the peak cell rate. It
takes a while (generally, less than 1 second) for this counter to stabilize.
detail extensive
Input packets
None specified
Output packets
None specified
protocol-family
Protocol family configured on the logical interface. If the protocol is inet, the IP
address of the interface is also displayed.
brief
Protocol
Protocol family configured on the logical interface.
MTU
MTU size on the logical interface.
Generation
detail extensive
Route table
Routing table in which the logical interface address is located. For example, 0
refers to the routing table inet.0.
detail extensive
Flags
Information about the protocol family flags. Possible values are described in
the Family Flags section under Common Output Fields Description.
Addresses, Flags
Information about the address flags. Possible values are described in the
Addresses Flags section under Common Output Fields Description.
Destination
IP address of the remote side of the connection.
Local
IP address of the logical interface.
678

Field Name
Field Description
Level of Output
Broadcast
Broadcast address.
Generation
detail extensive
VCI
Virtual circuit identifier number and information:
All levels
FlagsVCI flags:
ActiveVCI is up and in working condition.
CCC downVCI CCC is not in working condition.
ClosedVCI is closed because the user disabled the logical or physical
interface from the CLI.
ConfiguredVCI is configured.
DownVCI is not in working condition. The VCI might have alarms, defects,
F5 AIS/RDI, or no response to OAM loopback cells.
ILMIVCI is up and in working condition.
OAMOAM loopback is enabled.
MulticastVCI is a multicast VCI or DLCI.
Multipoint destinationVCI is configured as a multipoint destination.
NoneNo VCI flags.
Passive-OAMPassive OAM is enabled.
ShapingShaping is enabled.
SustainedShaping rate is set to Sustained.
UnconfiguredVCI is not configured.
Total down timeTotal number of seconds the VCI has been down, using the
format Total down time: hh:mm:ss orNever.
Last downTime of last Down transition, using the format Last down: hh:mm:ss.
EPD threshold(ATM2 only) Threshold at which a packet is dropped when
the queue size (in number of cells) exceeds the early packet-discard (EPD)
value.
679

Field Name
Field Description
Level of Output
VCI (continued)
All levels
Transmit weight cells(ATM2 only) Amount of bandwidth assigned to this
queue.
ATM per-VC transmit statistics:
Tail queue packet dropsNumber of packets dropped because of bandwidth
constraints. This value indicates that packets are queued to send out at a
rate faster than allowed.
OAM F4 cell statistics(Nonpromiscuous mode) OAM F4 statistics:
Total receivedNumber of OAM F4 cells received.
Total sentNumber of OAM F4 cells sent.
Loopback receivedNumber of OAM F4 loopback cells received.
Loopback sentNumber of OAM F4 loopback cells sent.
Last receivedTime at which the last OAM F4 cell was received.
Last sentTime at which the last OAM F4 cell was sent.
RDI receivedNumber of OAM F4 cells received with the remote defect
indication bit set.
RDI sentNumber of OAM F4 cells sent with the RDI bit set.
AIS receivedNumber of OAM F4 cells received with the alarm indication
signal bit set.
AIS sentNumber of OAM F4 cells sent with the AIS bit set.
Traffic statisticsNumber and rate of bytes and packets received and
transmitted on the physical interface.
IMA group
properties
VersionThe specified IMA specification version, either IMA 1.0 or IMA 1.1.
Frame lengthThe specified frame size, which can be 32, 64, 128, or 256.
Differential delayMaximum differential delay among links in milliseconds.
SymmetryEither Common Transmit Clock or Independent Transmit Clock
timing mode.
Transmit clockThe specified IMA clock mode, either common or independent.
Minimum linksThe number of minimum active links specified in both transmit
and receive directions.
TransmitThe per-PIC limit on the number of minimum active links in the
transmit direction.
ReceiveThe per-PIC limit on the number of minimum active links in the
receive direction.
Frame synchronizationThe specified IMA frame synchronization state
transition variables (Alpha, Beta, and Gamma) and their specified values.
680
AlphaThe number of consecutive invalid ICP cells for IFSM.
BetaThe number of consecutive errored ICP cells for IFSM.
GammaThe number of consecutive valid ICP cells for IFSM.
LinksThe number of IMA links assigned to the IMA group.

Field Name
Field Description
Level of Output
IMA group alarms
Start-up-FEFar-end group alarm status
Config-AbortedNear-end configuration aborted group alarm status
Config-Aborted-FEFar-end configuration aborted group alarm status
Insufficient-LinksNear-end insufficient links group alarm status
Insufficient-Links-FEFar-end insufficient links group alarm status
Blocked-FEFar-end blocked group alarm status
GR-Timing-MismatchGroup timing mismatch alarm status
Start-up-FEFar-end group defect status
Config-AbortedNear-end configuration aborted group defect status
Config-Aborted-FEFar-end configuration aborted group defect status
Insufficient-LinksNear-end insufficient links group defect status
Insufficient-Links-FEFar-end insufficient links group defect status
Blocked-FEFar-end blocked group defect status
GR-Timing-MismatchGroup timing mismatch defect status
IMA group defects
IMA Group state
Near-end and far-end group status
IMA group media
IMA group media status, including seconds, count and state for the following
media parameters:
FC
FC-FE
Addr-Mismatch
Running
UAS
681
Sample Output
show interfaces (ATM,
IMA Group)

IMA group properties:
Version
: 1.1
Frame length
: 128
Differential delay
: 25 milliseconds
Symmetry
: Symmetrical Configuration and Operation
Transmit clock
: Common
Minimum links
: Transmit: 1, Receive: 1
Frame synchronization: Alpha: 2, Beta: 2, Gamma: 1
Links
: None
IMA group alarms : Start-up-FE Config-Aborted Config-Aborted-FE
Insufficient-Links Insufficient-Links-FE Blocked-FE GR-Timing-Mismatch
IMA group defects : Start-up-FE Config-Aborted Config-Aborted-FE
Insufficient-Links Insufficient-Links-FE Blocked-FE GR-Timing-Mismatch
IMA Group state:
Near end : Start up
Far end : Start up
IMA group media:
Seconds
Count State
FC
0
FC-FE
0
Addr-Mismatch
0
Running
0
UAS
0
show interfaces
extensive (ATM IMA
Group)
user@host> show interfaces at-0/0/10 extensive

Link-level type: ATM-PVC, MTU: 2048, Speed: Unspecified, Loopback: None, Payload
scrambler: Enabled
Device flags
: Present Running
Link flags
: None
CoS queues
Hold-times
Current address: 84:18:88:c0:33:0a
Last flapped
: 2012-03-16 16:49:15 PDT (2d 07:12 ago)
Statistics last cleared: 2012-03-16 16:56:58 PDT (2d 07:05 ago)
Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
IPv6 transit statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Input errors:
Errors: 0, Drops: 0, Invalid VCs: 0, Framing errors: 0, Policed discards:
0, L3 incompletes: 0, L2 channel errors: 0,
L2 mismatch timeouts: 0, Resource errors: 0
Output errors:
Carrier transitions: 0, Errors: 0, Drops: 0, Aged packets: 0, MTU errors:
0, Resource errors: 0
IMA group properties:
Version
: 1.1
Frame length
: 128
682
Differential delay
: 25 milliseconds
Symmetry
: Symmetrical Configuration and Operation
Transmit clock
: Common
Minimum links
: Transmit: 1, Receive: 1
Frame synchronization: Alpha: 2, Beta: 2, Gamma: 1
Link #1
: t1-0/0/4
up
IMA Group alarms
: None
IMA Group state:
Near end : Operational
Far end : Operational
IMA group media:
Seconds
Count State
FC
0
FC-FE
0
Addr-Mismatch
0
Running
198306
UAS
0
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
Destination slot: 0
VPI 2
Flags: Active
Total down time: 0 sec, Last down: Never
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Logical interface at-0/0/10.602 (Index 71) (SNMP ifIndex 1057) (Generation
17226)
Flags: Point-To-Point SNMP-Traps CCC-Down 0x0 Encapsulation:
ATM-CCC-Cell-Relay
L2 circuit cell bundle size: 1, bundle timeout: 125 usec, timeout count: 0
L2 circuit out-of-sequence count: 0, denied packets count: 0
show interfaces
(ATM1, SONET Mode)

Description: to allspice at-1/0/0
Link-level type: ATM-PVC, MTU: 4482, Clocking: Internal, SONET mode,
Speed: OC3, Loopback: None, Payload scrambler: Enabled
Device flags
: Present Running
Link flags
: None
CoS queues
Current address: 00:05:85:02:38:7e
Last flapped
: 2006-02-24 14:28:12 PST (6d 01:51 ago)
Input rate
: 0 bps (0 pps)
Output rate
: 0 bps (0 pps)
SONET alarms
: None
683
SONET defects
: None
Logical interface at-1/0/0.0 (Index 64) (SNMP ifIndex 204)

Flags: Point-To-Point SNMP-Traps Encapsulation: ATM-SNAP
Input packets : 0
Output packets: 0
Protocol inet, MTU: 4470
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
Input packets : 0
Output packets: 0
show interfaces brief

(ATM1, SONET Mode)
user@host> show interfaces at-1/0/0 brief

Device flags
: Present Running
Link flags
: None
Logical interface at-1/0/0.0
inet 192.168.220.26/30
iso
VCI 0.128
Flags: Active
show interfaces detail

(ATM1, SONET Mode)
684
user@host> show interfaces at-1/0/0 detail

Device flags
: Present Running
Link flags
: None
CoS queues
Hold-times
Last flapped
: 2006-02-24 14:28:12 PST (6d 01:55 ago)
Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
Queue counters:
Dropped packets
0 best-effort
1 expedited-fo
2 assured-forw
3 network-cont
SONET alarms
SONET defects
: None
: None
Logical interface at-1/0/0.0 (Index 64) (SNMP ifIndex 204) (Generation 5)

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
Flags: None
Broadcast: 192.168.220.27, Generation: 14
Protocol iso, MTU: 4470, Generation: 14, Route table: 0
Flags: None
VCI 0.128
Flags: Active
Tail queue packet drops: 0
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
show interfaces
extensive
(ATM1, SONET Mode)

Link-level type: ATM-PVC, MTU: 4482, Clocking: Internal,
Device flags
: Present Running
Link flags
: None
CoS queues
Hold-times
Last flapped
: 2006-02-24 14:28:12 PST (6d 01:56 ago)
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Input errors:
SONET mode,
0
0
0
0
bps
bps
pps
pps
685
Errors: 0, Drops: 0, Invalid VCs: 0, Framing errors: 0, Policed discards: 0,

L3 incompletes: 0, L2 channel errors: 0, L2 mismatch timeouts: 0,
Resource errors: 0
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
1 expedited-fo
2 assured-forw
3 network-cont
SONET alarms
: None
SONET defects : None
SONET PHY:
Seconds
Count
PLL Lock
0
0
PHY Light
0
0
SONET section:
BIP-B1
0
0
SEF
0
0
LOS
0
0
LOF
0
0
ES-S
0
SES-S
0
SEFS-S
0
SONET line:
BIP-B2
0
0
REI-L
0
0
RDI-L
0
0
AIS-L
0
0
BERR-SF
0
0
BERR-SD
0
0
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
AIS-P
0
0
RDI-P
0
0
UNEQ-P
1
1
PLM-P
0
0
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
:
686
State
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
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,
Destination slot: 1
CoS information:
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
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
Flags: None
Broadcast: 192.168.220.27, Generation: 14
Flags: None
VCI 0.128
Flags: Active
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
show interfaces

687
(ATM2, SDH Mode)

Link-level type: ATM-PVC, MTU: 4482, Clocking: Internal, SDH mode, Speed: OC3,
Loopback: None, Payload scrambler: Enabled
Device flags
: Present Running
Link flags
: None
CoS queues
Current address: 00:05:85:8f:30:3f
Last flapped
: 2006-03-24 13:29:58 PST (00:04:48 ago)
Input rate
: 0 bps (0 pps)
Output rate
: 0 bps (0 pps)
SDH
alarms
: None
SDH
defects : None
VPI 0
Flags: Active
Traffic statistics:
Input packets:
0
Output packets:
0
Flags: Point-To-Point SNMP-Traps 0x4000 Encapsulation: ATM-SNAP
Input packets : 0
Output packets: 0
Flags: None
Destination: 10.0.12.6, Local: 10.0.12.5
Flags: None
VCI 0.128
Flags: Active
EPD threshold: 2129, Transmit weight cells: 0
Input packets : 0
Output packets: 0
Flags: Point-To-Multipoint No-Multicast SNMP-Traps 0x4000
Encapsulation: ATM-VCMUX
Input packets : 0
Output packets: 0
VCI 0.4
Flags: Active
Input packets : 0
Output packets: 0

(ATM2, SDH Mode)
688

Link-level type: ATM-PVC, MTU: 4482, Clocking: Internal, SDH mode,
Device flags
: Present Running
Link flags
: None
inet 10.0.12.5
--> 10.0.12.6
iso
VCI 0.128
Flags: Active

VCI 0.4
Flags: Active

(ATM2, SDH Mode)

Device flags
: Present Running
Link flags
: None
CoS queues
Hold-times
Last flapped
: 2006-03-24 13:29:58 PST (00:05:10 ago)
Traffic statistics:
Input bytes :
0
0
Output bytes :
0
0
Input packets:
0
0
Output packets:
0
0
Queue counters:
bps
bps
pps
pps
Dropped packets
0 best-effort
1 expedited-fo
2 assured-forw
3 network-cont
SDH
alarms
: None
SDH
defects : None
VPI 0
Flags: Active
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Local statistics:
Input bytes :
0
Output bytes :
0
689
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
Flags: None
Destination: 10.0.12.6, Local: 10.0.12.5, Broadcast: Unspecified,
Generation: 58
Flags: None
VCI 0.128
Flags: Active
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
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
VCI 0.4
Flags: Active
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
show interfaces
extensive
(ATM2, SDH Mode)

Device flags
: Present Running
Link flags
: None
CoS queues
Hold-times
690
Last flapped
: 2006-03-24 13:29:58 PST (00:06:49 ago)
Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
Input errors:
Resource errors: 0
Output errors:
Resource errors: 0
Queue counters:
Queued packets
Transmitted packets
Dropped packets
0 best-effort
1 expedited-fo
2 assured-forw
3 network-cont
SDH
alarms
: None
SDH
defects : None
SDH PHY:
Seconds
PLL Lock
0
PHY Light
1
SDH regenerator section:
RS-BIP8
2
OOF
2
LOS
2
LOF
2
RS-ES
4
RS-SES
3
RS-SEFS
2
SDH multiplex section:
MS-BIP24
2
MS-FEBE
1
MS-FERF
2
MS-AIS
2
BERR-SF
0
BERR-SD
0
MS-ES
4
MS-SES
2
MS-UAS
0
MS-ES-FE
3
MS-SES-FE
2
MS-UAS-FE
0
SDH path:
HP-BIP8
1
HP-FEBE
1
HP-LOP
0
HP-AIS
2
HP-FERF
3
HP-UNEQ
1
HP-PLM
2
Count
0
1
State
OK
OK
8828
2
1
1
OK
OK
OK
771
17476
1
1
0
0
OK
OK
OK
OK
6
251
0
1
2
1
1
OK
OK
OK
OK
OK
691
HP-ES
4
HP-SES
3
HP-UAS
0
HP-ES-FE
3
HP-SES-FE
3
HP-UAS-FE
0
Received SDH 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 SDH 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:
Destination slot: 0
VPI 0
Flags: Active
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
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
Flags: None
Generation: 58
Flags: None
VCI 0.128
Flags: Active
692

Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
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
VCI 0.4
Flags: Active
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
show interfaces
(ATM2, SONET Mode)

Device flags
: Present Running
Link flags
: None
CoS queues
Current address: 00:14:f6:22:58:5e
Last flapped
: 2006-03-13 17:46:36 PST (16:01:12 ago)
Input rate
: 0 bps (0 pps)
Output rate
: 0 bps (0 pps)
SONET alarms
: None
VPI 0
Flags: Active, OAM, Shaping
CBR, Peak: 50kbps
OAM, Period 30 sec, Up count: 10, Down count: 10
OAM F4 cell statistics:
Total received: 4, Total sent: 4
Loopback received: 4, Loopback sent: 4
RDI received: 0, RDI sent: 0
AIS received: 0
Traffic statistics:
Input packets:
4
Output packets:
30
693
VPI 10
Flags: Active
Traffic statistics:
Input packets:
0
Output packets:
0
Flags: Point-To-Point Copy-PLP-To-CLP SNMP-Traps 0x4000
Encapsulation: ATM-SNAP
Input packets : 0
Output packets: 0
Flags: None
Destination: 10.0.59.5, Local: 10.0.59.6
Flags: None
VCI 0.128
Flags: Active
Input packets : 0
Output packets: 0
Flags: Point-To-Multipoint Copy-PLP-To-CLP No-Multicast SNMP-Traps 0x4000
Input packets : 4
Output packets: 30
VCI 0.16
Flags: Active, ILMI
Input packets : 0
Output packets: 26
VCI 0.4
Flags: Active, OAM
Input packets : 4
Output packets: 4
AIS received: 0, AIS sent: 0

(ATM2, SONET Mode)

Device flags
: Present Running
Link flags
: None
inet 10.0.59.6
--> 10.0.59.5
iso
VCI 0.128
694
Flags: Active
VCI 0.16
Flags: Active, ILMI
VCI 0.4
Flags: Active, OAM

(ATM2, SONET Mode)

Device flags
: Present Running
Link flags
: None
CoS queues
Hold-times
Last flapped
: 2006-03-13 17:46:36 PST (16:02:39 ago)
Traffic statistics:
Input bytes :
312
0 bps
Output bytes :
2952
0 bps
Input packets:
6
0 pps
Output packets:
50
0 pps
Queue counters:
Dropped packets
0 best-effort
44
44
1 expedited-fo
2 assured-forw
3 network-cont
SONET alarms
: None
VPI 0
CBR, Peak: 50kbps
Last received: 00:00:29, Last sent: 00:00:29
AIS received: 0
Traffic statistics:
Input bytes :
312
Output bytes :
2952
Input packets:
6
695
Output packets:
50
VPI 10
Flags: Active
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
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
Flags: None
Generation: 44
Flags: None
VCI 0.128
Flags: Active
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
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
696

Traffic statistics:
Input bytes :
0
Output bytes :
2640
Input packets:
0
Output packets:
44
VCI 0.4
Flags: Active, OAM
Traffic statistics:
Input bytes :
312
Output bytes :
312
Input packets:
6
Output packets:
6
show interfaces
extensive
(ATM2, SONET Mode)

Device flags
: Present Running
Link flags
: None
CoS queues
Hold-times
Last flapped
: 2006-03-13 17:46:36 PST (16:04:12 ago)
Traffic statistics:
Input bytes :
520
0 bps
Output bytes :
4240
0 bps
Input packets:
10
0 pps
Output packets:
72
0 pps
Input errors:
Resource errors: 0
Output errors:
Resource errors: 0
Queue counters:
Queued packets
0 best-effort
1 expedited-fo
Transmitted packets
Dropped packets
62
62
697
2 assured-forw
3 network-cont
10
10
SONET alarms
: None
SONET PHY:
Seconds
Count State
PLL Lock
0
0 OK
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
F1
: 0x00, J0
: 0x00, K1
: 0x00, K2
: 0x00
S1
: 0x00, C2
: 0x13, C2(cmp) : 0x13, F2
: 0x00
Z3
: 0x00, Z4
: 0x00, S1(cmp) : 0x00
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:
698

Destination slot: 0
VPI 0
CBR, Peak: 50kbps
AIS received: 0
Traffic statistics:
Input bytes :
520
Output bytes :
4240
Input packets:
10
Output packets:
72
VPI 10
Flags: Active
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
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
Flags: None
Generation: 44
Flags: None
VCI 0.128
Flags: Active
Traffic statistics:
Input bytes :
0
699
Output bytes :
Input packets:
Output packets:
0
0
0
Traffic statistics:
Input bytes :
660
Output bytes :
5473
Input packets:
11
Output packets:
83
Local statistics:
Input bytes :
660
Output bytes :
5473
Input packets:
11
Output packets:
83
VCI 0.16
Flags: Active, ILMI
Traffic statistics:
Input bytes :
0
Output bytes :
4320
Input packets:
0
Output packets:
72
VCI 0.4
Flags: Active, OAM
Traffic statistics:
Input bytes :
572
Output bytes :
572
Input packets:
11
Output packets:
11
700
show interfaces (T1, E1, or DS)

Syntax
Release Information
Description
Options
show interfaces interface-type

<descriptions>
<media>
<snmp-index snmp-index>
<statistics>

Display status information about the specified T1, E1, or DS interface.
interface-typeOn ACX Series, M Series, MX Series, and T Series routers, the T1 interface
type is t1-fpc/pic/port, whereas the E1 interface type is e1-fpc/pic/port, and DS

interface type is ds-fpc/pic/port:<channel>. On the J Series routers, the T1 interface
type is t1-pim/0/port, whereas the E1 interface type is e1-pim/0/port.
descriptions(Optional) Display interface description strings.
media(Optional) Display media-specific information about network interfaces.
snmp-index snmp-index(Optional) Display information for the specified SNMP index
of the interface.
statistics(Optional) Display static interface statistics.
Required Privilege
Level
Related
Documentation
Output Fields
view
show interfaces (T1, IMA Link) on page 714

show interfaces (T1, PPP) on page 714
show interfaces detail (T1, PPP) on page 715
show interfaces extensive (T1 CRC Errors) on page 715
show interfaces extensive (T1, PPP) on page 716
show interfaces (E1, Frame Relay) on page 717
show interfaces detail (E1, Frame Relay) on page 718
show interfaces extensive (E1, Frame Relay) on page 719
show interfaces (E1, IMA Link) on page 721
show interfaces extensive (T1, TDM-CCC-SATOP) on page 722
show interfaces extensive (DS, TDM-CCC-CESoPSN) on page 724
Table 50 on page 702 lists the output fields for the show interfaces (T1 or E1) command.
701
Table 50: T1 or E1 show interfaces Output Fields

Field Name
Field Description
Level of Output
Physical interface
Name of the physical interface.
All levels
Enabled
State of the interface. Possible values are described in the Enabled Field
All levels
Interface index
Physical interface's index number, which reflects its initialization sequence.
SNMP ifIndex
SNMP index number for the physical interface.
Generation
detail extensive
Link-level type
Encapsulation being used on the physical interface.
All levels
MTU
All levels
Clocking
Reference clock source: Internal or External.
All levels
Speed
Speed at which the interface is running.
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 for the E1 interface on the link: G704,
G704-NO-CRC4, or Unframed. The default is G704.
All levels
Physical Interface
Physical layer framing format used for the T1 interface on the link: SF and ESF.
The default is ESF.
Device flags
Information about the physical device. Possible values are described in the
Device Flags section under Common Output Fields Description.
All levels
Interface flags
Information about the interface. Possible values are described in the Interface
Flags section under Common Output Fields Description.
All levels
Link flags
Information about the link. Possible values are described in the Link Flags
All levels
Hold-times
detail extensive
702
Table 50: T1 or E1 show interfaces Output Fields (continued)

Field Name
Field Description
Level of Output
IMA Link alarms
Current active IMA link alarms, including the following:
IMA Link defects
IMA Link state
LIF
LODS
RFI-IMA
Tx-Mis-Connected
Tx-Unusable-FE
Rx-Unusable-FE
Link Fault
Current active IMA link defects, including the following:
LIF
LODS
RFI-IMA
Tx-Mis-Connected
Tx-Unusable-FE
Rx-Unusable-FE
Link Fault
Current active IMA link status, including the following:
Line: synchronized or not synchronized
Near end:Status of near-end receive and transmit links
Rx: Usable or Unusable
Tx: Usable or Unusable
Far end:Status of far-end receive and transmit links
Rx: Usable or Unusable
Tx: Usable or Unusable
703

Field Name
Field Description
Level of Output
IMA link media
IMA Link Media Status, which provides the seconds and count state for the
following link media parameters:
Keepalive settings
Keepalive statistics
LIF
LODS
Err-ICP
IV
Rx-FC
Tx-FC
FE-Defects
FE-Rx-FC
FE-Tx-FC
Rx-ICP
Rx-Stuff
Tx-ICP
Tx-Stuff
Rx-SES
Rx-UAS
Rx-UUS
Tx-UUS
FE-Rx-SES
FE-Rx-UAS
FE-Rx-UUS
FE-Tx-UUS
(PPP and HDLC) Configured settings for keepalives.
interval secondsThe time in seconds between successive keepalive requests.

The range is 10 seconds through 32,767 seconds, with a default of 10 seconds.
down-count numberThe 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 numberThe number of keepalive packets a destination must receive

to change a links status from down to up. The range is 1 through 255, with a
default of 1.
(PPP and HDLC) Information about keepalive packets. (When no level of output
is specified, the word statistics is not part of the field name and the last seen
text is not displayed.)
InputNumber 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.
OutputNumber of keepalive packets sent by PPP and how long ago the last
keepalive packets were sent and received.
704
(last seen 00:00:00 ago)Time since the last keepalive packet was sent,
in the format hh:mm:ss.

Field Name
Field Description
Level of Output
LMI settings
(Frame Relay) Settings for Local Management Interface (LMI) which can be
either 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:
LMI
DTE statistics
n391dteDTE full status polling interval (1255)
n392dceDCE error threshold (110)
n392dteDTE error threshold (110)
n393dceDCE monitored event count (110)
n393dteDTE monitored event count (110)
t391dteDTE polling timer (530 seconds)
t392dceDCE polling verification timer (530 seconds)
(Frame Relay) Local Management Interface (LMI) packet statistics:
InputNumber 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).
OutputNumber 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).
(Frame Relay) Statistics about messages transmitted from the data terminal
equipment (DTE) to the data communications equipment (DCE):
Enquiries sentNumber of link status enquiries sent from the DTE to the DCE.
Full enquiries sentNumber of full enquiries sent from the DTE to the DCE.
Enquiry responses receivedNumber of enquiry responses received by the
DTE from the DCE.
Full enquiry responses receivedNumber 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:
Enquiries receivedNumber of enquiries received by the DCE from the DTE.
Full enquiries receivedNumber of full enquiries received by the DCE from
the DTE.
Enquiry responses sentNumber of enquiry responses sent from the DCE to
the DTE.
Full enquiry responses sentNumber of full enquiry responses sent from the
DCE to the DTE.
705

Field Name
Field Description
Level of Output
Common statistics
(Frame Relay) Statistics about messages sent between the DTE and the DCE:
Unknown messages receivedNumber of received packets that do not fall
into any category.
Asynchronous updates receivedNumber of link status peer changes received.
Out-of-sequence packets receivedNumber of packets for which the sequence
of the packets received is different from the expected sequence.
Keepalive responses timedoutNumber of keepalive responses that timed
out when no Local Management Interface (LMI) packet was reported for
n392dte or n393dce intervals. (See LMI settings.)
Nonmatching
DCE-end DLCIs
(Frame Relay. Displayed only from the DTE.) Number of DLCIs configured from
the DCE.
LCP state
(PPP) Link Control Protocol state.
NCP state
CHAP state
Conf-ack-receivedAcknowledgement was received.
Conf-ack-sentAcknowledgement was sent.
Conf-req-sentRequest was sent.
DownLCP negotiation is incomplete (not yet completed or has failed).
Not configuredLCP is not configured on the interface.
OpenedLCP negotiation is successful.
(PPP) Network Control Protocol state.
Conf-ack-receivedAcknowledgement was received.
Conf-ack-sentAcknowledgement was sent.
Conf-req-sentRequest was sent.
DownNCP negotiation is incomplete (not yet completed or has failed).
Not configuredNCP is not configured on the interface.
OpenedNCP negotiation is successful.
(PPP) State of the Challenge Handshake Authentication Protocol (CHAP)

during its transaction.
Chap-Chal-receivedChallenge was received but response is not yet sent.
Chap-Chal-sentChallenge was sent.
Chap-Resp-receivedResponse was received for the challenge sent, but
CHAP has not yet moved into the Success state. (Most likely with RADIUS
authentication.)
Last flapped
706
Chap-Resp-sentResponse was sent for the challenge received.
DownCHAP authentication is incomplete (not yet completed or has failed).
Not-configuredCHAP is not configured on the interface.
OpenedCHAP authentication was successful.
Date, time, and how long ago the interface went from down to up. The format
is Last flapped: year-month-day hour:minute:second timezone (hour:minute:second
ago). For example, Last flapped: 2002-04-26 10:52:40 PDT (04:33:20 ago).

Field Name
Field Description
Level of Output
CoS Queues
Input rate
Input rate in bits per second (bps) and packets per second (pps).
None specified
Output rate
Output rate in bps and pps.
None specified
Statistics last
cleared
Time when the statistics for the interface were last set to zero.
detail extensive
Traffic statistics
Number and rate of bytes and packets received and transmitted on the physical
interface.
detail extensive
Input errors
Input errors on the interface. The following paragraphs explain the counters
ErrorsSum of the incoming frame aborts and FCS errors.
DropsNumber of packets dropped by the input queue of the I/O Manager
extensive
Framing errorsNumber of packets received with an invalid frame checksum
(FCS).
Policed discardsNumber of frames that the incoming packet match code
discarded because they were not recognized or not of interest. Usually, this
field reports protocols that the Junos OS does not handle.
L3 incompletesNumber 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 errorsNumber of times the software did not find a valid logical
interface for an incoming frame.
L2 mismatch timeoutsNumber of malformed or short packets that caused
the incoming packet handler to discard the frame as unreadable.
HS link CRC errorsNumber of errors on the high-speed links between the
ASICs responsible for handling the router interfaces.
SRAM errorsNumber 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.
707

Field Name
Field Description
Level of Output
Output errors
Output errors on the interface. The following paragraphs explain the counters
extensive
Carrier transitionsNumber 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.
DropsNumber of packets dropped by the output queue of the I/O Manager
Aged packetsNumber 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.
Queue counters
DS1 alarms
DS1 defects
708
MTU errorsNumber of packets whose size exceeded the MTU of the interface.
E1 media-specific defects that can prevent the interface from passing packets.
When a defect persists for a certain amount of time, it is promoted to an alarm.
Based on the 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.
AISAlarm indication signal.
LOFLoss of frame.
LOSLoss of signal.
YLWYellow alarm. Indicates errors at the remote site receiver.
detail extensive

Field Name
Field Description
Level of Output
T1 media or E1
media
Counts of T1 or E1 media-specific errors.
extensive
The T1 or E1 media-specific error types are:
SAToP
Configuration
BEEBit error
AISAlarm indication signal
LOFLoss of frame
LOSLoss of signal
YELLOWErrors at the remote site receiver
CRC MajorCyclic redundancy check major alarm threshold exceeded
CRC MinorCyclic redundancy check minor alarm threshold exceeded
BPVBipolar violation
EXZExcessive zeros
LCVLine code violation
PCVPulse code violation
CSCarrier state
CRCCyclic redundancy check
FEBEFar-end block error (E1 only)
LESLine error seconds
ESErrored seconds
BESBursty errored seconds
SESSeverely errored seconds
SEFSSeverely errored framing seconds
UASUnavailable seconds
Information about the SAToP configuration.
extensive
payload-sizeConfigure the payload size, in bytes (from 32 through 1024
bytes).
idle-patternAn 8-bit hexadecimal pattern to replace TDM data in a lost
packet (from 0 through 255).
jitter-buffer-packetsNumber of packets in the jitter buffer (from 1 through
64 packets).
jitter-buffer-latencyTime delay in the jitter buffer (from 1 through 1000
milliseconds).
excessive-packet-loss-rateSet packet loss options. The options are groups,

sample-period, and threshold.
sample-periodTime required to calculate excessive packet loss rate (from
1000 through 65,535 milliseconds).
thresholdPercentile designating the threshold of excessive packet loss rate
(1100 percent).
709

Field Name
Field Description
Level of Output
CESoPSN
Configuration
Information about the CESoPSN configuration.
extensive
packetization-latencyTime required to create packets (from 1000 through
8000 microseconds).
idle-patternAn 8-bit hexadecimal pattern to replace TDM data in a lost
packet (from 0 through 255).
jitter-buffer-packetsNumber of packets in the jitter buffer (from 1 through
64 packets).
jitter-buffer-latencyTime delay in the jitter buffer (from 1 through 1000
milliseconds).
excessive-packet-loss-rateSet packet loss options. The options are

sample-period and threshold.
sample-periodTime required to calculate excessive packet loss rate (from
1000 through 65,535 milliseconds).
thresholdPercentile designating the threshold of excessive packet loss rate
(1100 percent).
HDLC configuration
Information about the HDLC configuration.
extensive
Policing bucketConfigured state of the receiving policer.
Shaping bucketConfigured state of the transmitting shaper.
Giant thresholdGiant threshold programmed into the hardware.
Runt thresholdRunt threshold programmed into the hardware.
TimeslotsTime slots configured on the interface.
Buildout(T1 only) Buildout setting: 0-132, 133-265, 266-398, 399-531, or
532-655 feet.
DS1 BERT
configuration
TimeslotsConfigured time slots for the interface.
Byte encoding(T1 only) Byte encoding used: Nx64K or Nx56K.
Line encodingLine encoding used. For T1, the value can be B8ZS or AMI. For
E1, the value is HDB3.
Data inversionHDLC data inversion setting: Enabled or Disabled.
Idle cycle flagIdle cycle flags.
Start end flagStart and end flag.
BERT (bit error rate test) checks the quality of the line. This output appears
only when a BERT is run on the interface.
BERT time periodConfigured total time period that the BERT is to run.
ElapsedActual time elapsed since the start of the BERT (in seconds).
Induced error rateConfigured rate at which the bit errors are induced in the
BERT pattern.
Packet Forwarding
Engine
configuration
710
AlgorithmType of algorithm selected for the BERT.
PLP bytePacket Level Protocol byte.
extensive

Field Name
Field Description
Level of Output
CoS information
extensive
CoS transmit queueQueue number and its associated user-configured
forwarding class name.
Buffer usecAmount of buffer space allocated to the queue, in microseconds.
This value is nonzero only if the buffer size is configured in terms of time.
LimitDisplayed 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.
SNMP ifIndex
Logical interface SNMP interface index number.
Generation
detail extensive
Flags
Information about the interface. Possible values are described in the Interface
Flags section under Common Output Fields Description.
All levels
Encapsulation
All levels
Input packets
None specified
Output packets
None specified
Traffic statistics
(Frame Relay) Number and rate of bytes and packets received and transmitted
on the logical interface.
detail extensive
Local statistics
Input packetsNumber of packets received on the interface.
(Frame Relay) Statistics for traffic received from and transmitted to the Routing
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 a while (generally, less than
1 second) for this counter to stabilize.
detail extensive
711

Field Name
Field Description
Level of Output
Transit statistics
(Frame Relay) Statistics for traffic transiting the router. When a burst of traffic
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.
detail extensive
Protocol
Protocol family configured on the logical interface, such as iso, inet6, mlfr, or
mpls.
Multilink bundle
Interface name for the multilink bundle, if configured.
MTU
MTU size on the logical interface.
Generation
detail extensive
Route table
Routing table in which the logical interface address is located. For example, 0
refers to the routing table inet.0.
detail extensive
Flags
Information about the protocol family flags. Possible values are described in
the Family Flags section under Common Output Fields Description.
Addresses, Flags
Information about the address flags. Possible values are described in the
Addresses Flags section under Common Output Fields Description.
Destination
IP address of the remote side of the connection.
Local
IP address of the logical interface.
Broadcast
Broadcast address.
Generation
DLCI
(Frame Relay) DLCI number of the logical interface. The following DLCI
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:
ActiveSet when the link is active and the DTE and DCE are exchanging
information.
DownSet when the link is active, but no information is received from the
DCE.
DCE-UnconfiguredSet when the corresponding DLCI in the DCE is not
configured.
DLCI statistics
712
ConfiguredSet when the corresponding DLCI in the DCE is configured.
DCE-configuredDisplayed when the command is issued from the DTE.
(Frame Relay) Data-link connection identifier (DLCI) statistics.
Active DLCINumber of active DLCIs.
Inactive DLCINumber of inactive DLCIs.

Field Name
Field Description
Level of Output
CE Info
Information related to the circuit emulation statistics.
extensive
CE TxNumber of transmitted packets and bytes (TDM to PSN flow).
CE RxNumber of received packets and bytes and forward bytes (PSN to
TDM flow).
CE Rx ForwardedNumber of forwarded bytes.
CE StrayedNumber of stray packets.
CE LostNumber of lost packets.
CE MalformedNumber of malformed packets
CE MisinsertedNumber of misinserted packets.
CE AIS droppedNumber of dropped bytes due to buffer overrun (PSN to
TDM).
CE DroppedNumber of dropped packets during resynchronization
CE Overrun EventsNumber of overrun events.
CE Underrun EventsNumber of underrun events.
713
Sample Output
show interfaces (T1,
IMA Link)
show interfaces
(T1, PPP)
user@host> show interfaces t1-1/0/0

IMA Link alarms
: None
IMA Link defects : LIF, LODS
IMA Link state:
Line
: Not synchronized
Near end : Rx: Unusable, Tx: Usable
Far end : Rx: Unusable, Tx: Usable
IMA link media:
Seconds
LIF
LODS
Err-ICP
IV
Rx-FC
Tx-FC
FE-Defects
FE-Rx-FC
FE-Tx-FC
Rx-ICP
Rx-Stuff
Tx-ICP
Tx-Stuff
Rx-SES
0
Rx-UAS
0
Rx-UUS
1
Tx-UUS
0
FE-Rx-SES
0
FE-Rx-UAS
0
FE-Rx-UUS
0
FE-Tx-UUS
0
Count
0
0
0
0
0
0
0
0
0
0
0
11
0
State
OK
OK
OK
OK
OK
OK
user@host> show interfaces t1-1/1/0

Link-level type: PPP, MTU: 1504, Clocking: Internal, Speed: T1,
Loopback: None, FCS: 16, Framing: ESF
Device flags
: Present Running
Link flags
: Keepalives
Keepalive settings: Interval 10 seconds, Up-count 1, Down-count 3
Keepalive: Input: 0 (never), Output: 0 (never)
LCP state: Opened
NCP state: Opened
CHAP state: Opened
CoS queues
: 4 supported, 4 in use
Last flapped
: 2005-12-05 08:43:06 PST (02:13:35 ago)
Input rate
: 0 bps (0 pps)
Output rate
: 72 bps (0 pps)
DS1
alarms
: None
DS1
defects : None
Logical interface t1-1/1/0.0 (Index 66) (SNMP ifIndex 51)
Flags: Hardware-Down Point-To-Point SNMP-Traps Encapsulation: PPP
Flags: Protocol-Down
Addresses, Flags: Dest-route-down Is-Preferred Is-Primary
Destination: 1.1.1/24, Local: 1.1.1.1, Broadcast: 1.1.1.255
714

(T1, PPP)
user@host> show interfaces t1-1/1/0 detail

Device flags
: Present Running
Link flags
: Keepalives
Hold-times
Keepalive statistics:
Input : 0 (last seen: never)
Output: 0 (last sent: never)
LCP state: Opened
NCP state: Opened
CHAP state: Opened
CoS queues
Last flapped
: 2005-12-05 08:43:06 PST (02:13:52 ago)
Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
798
0 bps
Input packets:
0
0 pps
Output packets:
42
0 pps
Queue counters:
Dropped packets
0 best-effort
1 expedited-fo
2 assured-forw
3 network-cont
40
40
DS1
alarms
: None
DS1
defects : None
Induced Error rate: 10e-0, Algorithm: 2^15 - 1
Destination: 1.1.1/24, Local: 1.1.1.1, Broadcast: 1.1.1.255,
Generation: 18
show interfaces
extensive (T1 CRC
Errors)
user@host> show interfaces t1-3/2/0:1:1 extensive

Physical interface: t1-3/2/0:1:1, Enabled, Physical link is Down
:
:
DS1
alarms
: AIS, LOF, CRC Major, CRC Minor
DS1
defects : AIS, LOF, CRC Major, CRC Minor
T1 media:
Seconds
Count State
SEF
1
1 OK
BEE
1
1 OK
AIS
1128
1 Defect Active
LOF
1128
1 Defect Active
LOS
0
0 OK
715
YELLOW
CRC Major
CRC Minor
BPV
EXZ
LCV
PCV
CS
CRC
...
show interfaces
extensive (T1, PPP)
0
154
154
0
0
0
0
0
154
OK
Defect Active
Defect Active
user@host> show interfaces t1-1/1/0 extensive

Device flags
: Present Running
Link flags
: Keepalives
Hold-times
Output: 0 (last sent: never)
LCP state: Down
NCP state: inet: Not-configured, inet6: Not-configured, iso: Not-configured,
mpls: Not-configured
CHAP state: Closed
CoS queues
Last flapped
: 2005-12-05 08:43:06 PST (02:13:54 ago)
Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
817
72 bps
Input packets:
0
0 pps
Output packets:
43
0 pps
Input errors:
Errors: 0, Drops: 0, Framing errors: 0, Policed discards: 0,
HS link CRC errors: 0, SRAM errors: 0, Resource errors: 0
Output errors:
Resource errors: 0
Queue counters:
Queued packets
Transmitted packets
Dropped packets
0 best-effort
1 expedited-fo
2 assured-forw
3 network-cont
42
42
DS1
alarms
DS1
defects
T1 media:
SEF
BEE
AIS
LOF
716
0
1
1
0
0
0
0
0
15400
: None
: None
Seconds
1
0
0
1
Count
1
0
0
1
State
OK
OK
OK
OK
LOS
0
0 OK
YELLOW
1
1 OK
BPV
1
1
EXZ
1
1
LCV
1
65535
PCV
1
1023
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:
Start end flag: shared
Induced Error rate: 10e-0, Algorithm: 2^15 - 1
Destination slot: 1, PLP byte: 1 (0x00)
CoS information:
CoS transmit queue
Bandwidth
Buffer
Priority
%
bps
%
usec
0 best-effort
95
1459200
95
0
low
3 network-control
5
76800
5
0
low
flags,
Limit
none
none

Generation: 18
show interfaces
(E1, Frame Relay)

Link-level type: Frame-Relay, MTU: 1504, Clocking: Internal, Speed: E1,
Loopback: None, FCS: 16, Framing: G704
Device flags
: Present Running
Interface flags: Link-Layer-Down Point-To-Point SNMP-Traps 16384
Link flags
: Keepalives DTE
ANSI LMI settings: n391dte 6, n392dte 3, n393dte 4, t391dte 10 seconds
LMI: Input: 0 (never), Output: 11 (00:00:05 ago)
DTE statistics:
Enquiries sent
: 10
Full enquiries sent
: 1
Enquiry responses received
: 0
Full enquiry responses received
: 0
DCE statistics:
Enquiries received
: 0
Full enquiries received
: 0
Enquiry responses sent
: 0
Full enquiry responses sent
: 0
717
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)
Input rate
: 0 bps (0 pps)
Output rate
: 0 bps (0 pps)
DS1
alarms
: None
DS1
defects : None
Logical interface e1-3/0/0.0 (Index 72) (SNMP ifIndex 32)
Flags: Device-Down Point-To-Point SNMP-Traps Encapsulation: FR-NLPID
Input packets : 0
Output packets: 0
Flags: None
Destination: 10.1.3/24, Local: 10.1.3.1, Broadcast: 10.1.3.255
DLCI 100
Flags: Down, DCE-Unconfigured
Total down time: 00:01:13 sec, Last down: 00:01:13 ago
Input packets : 0
Output packets: 0
DLCI statistics:
Active DLCI :0 Inactive DLCI :1

(E1, Frame Relay)
718
user@host> show interfaces e1-3/0/0 detail

Device flags
: Present Running
Link flags
: Keepalives DTE
Hold-times
LMI statistics:
Output: 12 (last sent 00:00:02 ago)
DTE statistics:
Enquiries sent
: 10
Full enquiries sent
: 2
: 0
: 0
DCE statistics:
Enquiries received
: 0
: 0
: 0
: 0
Common statistics:
: 0
: 0
: 0
: 1
CoS queues
: 8 supported
Last flapped
: 2005-11-30 14:50:34 PST (4d 20:33 ago)
Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
225
56 bps
Input packets:
Output packets:
Queue counters:
0
0 pps
15
0 pps
Dropped packets
0 limited
1 expedited-fo
2 real-plus
15
15
3 network-cont
DS1
alarms
: None
DS1
defects : None
Induced Error rate: 10e-0, Algorithm: 2^15 - 1, O.151, Pseudorandom (9)
Logical interface e1-3/0/0.0 (Index 72) (SNMP ifIndex 32) (Generation 26)
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
Flags: None
Generation: 42
DLCI 100
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
DLCI statistics:
show interfaces
extensive
(E1, Frame Relay)
user@host> show interfaces e1-3/0/0 extensive

Device flags
: Present Running
Link flags
: Keepalives DTE
Hold-times
LMI statistics:
719

DTE statistics:
Enquiries sent
: 10
Full enquiries sent
: 2
: 0
: 0
DCE statistics:
Enquiries received
: 0
: 0
: 0
: 0
Common statistics:
: 0
: 0
: 0
: 1
CoS queues
: 8 supported
Last flapped
: 2005-11-30 14:50:34 PST (4d 20:33 ago)
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,
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:
Dropped packets
0 limited
1 expedited-fo
2 real-plus
15
15
3 network-cont
DS1
alarms
DS1
defects
E1 media:
SEF
BEE
AIS
LOF
LOS
YELLOW
BPV
EXZ
LCV
PCV
CS
FEBE
LES
ES
SES
SEFS
720
: None
: None
Seconds
0
5
0
245
245
0
0
9
0
0
0
0
0
0
0
0
Count
0
5
0
15
4
11
0
9
0
0
0
0
State
OK
OK
OK
OK
OK
OK
BES
0
UAS
271
HDLC configuration:
Policing bucket: Disabled
Shaping bucket : Disabled
Giant threshold: 1506, Runt threshold: 0
Timeslots
: All active
Line encoding: HDB3, Data inversion: Disabled, Idle cycle flag: flags,
Start end flag: shared
Induced Error rate: 10e-0, Algorithm: 2^15 - 1, O.151, Pseudorandom (9)
Destination slot: 3, PLP byte: 1 (0x00)
CoS information:
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)
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
Flags: None
Generation: 42
DLCI 100
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
DLCI statistics:
show interfaces (E1,

IMA Link)

IMA Link alarms
: None
IMA Link defects : LIF, LODS
IMA Link state:
Line
: Not synchronized
Near end : Rx: Unusable, Tx: Usable
Far end : Rx: Unusable, Tx: Usable
IMA link media:
Seconds
LIF
Count
0
State
721
LODS
Err-ICP
IV
Rx-FC
Tx-FC
FE-Defects
FE-Rx-FC
FE-Tx-FC
Rx-ICP
Rx-Stuff
Tx-ICP
Tx-Stuff
Rx-SES
Rx-UAS
Rx-UUS
Tx-UUS
FE-Rx-SES
FE-Rx-UAS
FE-Rx-UUS
FE-Tx-UUS
show interfaces
extensive (T1,
TDM-CCC-SATOP)
0
0
1
0
0
0
0
0
user@host>show interfaces t1-1/0/0:1:1 extensive

Physical interface: t1-1/0/0:1:1, Enabled, Physical link is Down
Link-level type: TDM-CCC-SATOP, MTU: 1504, Clocking: Internal, Speed: T1,
Loopback: None, FCS: 16, Framing: ESF,
Parent: coc1-1/0/0:1 Interface index 152
Device flags
: Present Running Down
Interface flags: Hardware-Down Point-To-Point SNMP-Traps Internal: 0x0
Link flags
: None
Hold-times
CoS queues
Last flapped
: 2012-10-28 02:12:40 PDT (22:32:13 ago)
Queue counters:
Dropped packets
0 best-effort
1 expedited-fo
2 assured-forw
3 network-cont
Queue number:
0
1
2
3
DS1
alarms
DS1
defects
T1 media:
SEF
BEE
AIS
LOF
LOS
YELLOW
CRC Major
CRC Minor
722
0
0
0
0
0
0
0
0
0
0
11
0

best-effort
assured-forwarding
network-control
: None
: None
Seconds
Count
0
0
0
0
0
0
0
0
State
0 OK
0 OK
0 OK
0 OK
0 OK
0 OK
0 OK
0 OK
BPV
0
0
EXZ
0
0
LCV
0
0
PCV
0
0
CS
0
0
CRC
0
0
LES
0
ES
0
SES
0
SEFS
0
BES
0
UAS
0
SAToP configuration:
Payload size: 192
Idle pattern: 0xFF
Octet aligned: Disabled
SONET alarms
: None
SONET defects : AIS-V, RDI-V
SONET vt:
BIP-BIP2
0
0
REI-V
0
0
LOP-V
0
0 OK
AIS-V
2
0 Defect Active
RDI-V
2
0 Defect Active
UNEQ-V
0
0 OK
PLM-V
0
0 OK
ES-V
0
SES-V
0
UAS-V
2
ES-VFE
0
SES-VFE
0
UAS-VFE
0
V5
: 0x07
V5(cmp) : 0x02
V5
: 0x02
Destination slot: 1
CoS information:
Direction : Output
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
Logical interface t1-1/0/0:1:1.0 (Index 69) (SNMP ifIndex 580) (Generation 525)
Flags: Device-Down Point-To-Point SNMP-Traps Encapsulation: TDM-CCC-SATOP
CE info
Packets
Bytes Count
CE Tx
1005
192960
CE Rx
1004
192768
CE Rx Forwarded
0
723
CE Strayed
0
CE Lost
0
CE Malformed
0
CE Misinserted
0
CE AIS dropped
0
CE Dropped
1005
192960
CE Overrun Events
0
CE Underrun Events
0
Flags: Is-Primary
show interfaces
extensive (DS,
TDM-CCC-CESoPSN)
user@host>show interfaces ds-1/0/0:1:1:1 extensive

Physical interface: ds-1/0/0:1:1:1, Enabled, Physical link is Down
Link-level type: TDM-CCC-CESoPSN, MTU: 1504, Speed: 1536kbps, Loopback: None,
FCS: 16, Parent: ct1-1/0/0:1:1 Interface index 153
Device flags
Interface flags: Hardware-Down Point-To-Point SNMP-Traps Internal: 0x0
Link flags
: None
Hold-times
CoS queues
Last flapped
: 2012-10-29 00:49:03 PDT (00:00:35 ago)
Queue counters:
Dropped packets
0 best-effort
1 expedited-fo
2 assured-forw
3 network-cont
Queue number:
0
best-effort
1
2
assured-forwarding
3
network-control
CESoPSN configuration:
Packetization latency: 1000 us
Idle pattern: 0xFF
Destination slot: 1
CoS information:
Direction : Output
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
Logical interface ds-1/0/0:1:1:1.0 (Index 69) (SNMP ifIndex 598) (Generation
549)
724
Flags: Device-Down Point-To-Point SNMP-Traps Encapsulation: TDM-CCC-CESoPSN

CE info
Packets
Bytes Count
CE Tx
0
0
CE Rx
35712
6856704
CE Rx Forwarded
0
CE Strayed
0
CE Lost
0
CE Malformed
0
CE Misinserted
0
CE AIS dropped
0
CE Dropped
0
0
CE Overrun Events
0
CE Underrun Events
1
Flags: Is-Primary
725
show interfaces statistics

Syntax
Release Information
Description
Options
show interfaces statistics interface-name

<detail>

Display static interface statistics, such as errors.
interface-nameName of an interface.
detail(Optional) Display detail output.
Required Privilege
Level
Related
Documentation
Output Fields
726
view
clear interfaces statistics
show interfaces statistics (Fast Ethernet) on page 727

show interfaces statistics (Gigabit Ethernet PICEgress) on page 727
show interfaces statistics detail (Aggregated Ethernet) on page 729
show interfaces statistics detail (Aggregated EthernetIngress) on page 730
show interfaces statistics detail (Aggregated EthernetEgress) on page 732
show interfaces statistics (SONET/SDH) on page 734
show interfaces statistics (Aggregated SONET/SDHIngress) on page 735
show interfaces statistics (Aggregated SONET/SDHEgress) on page 736
show interfaces statistics (PTX Series Packet Transport Switches) on page 737
show interfaces statistics (ACX Series routers) on page 738
Output from both the show interfaces interface-name detail and the show interfaces
interface-name extensive commands include all the information displayed in the output
from the show interfaces statistics command. For more information, see the particular
interface type in which you are interested. For information about destination class and
source class statistics, see the Destination Class Field section and the Source Class
Field section under Common Output Fields Description. For information about the input
errors and output errors, see Fast Ethernet and Gigabit Ethernet Counters.
Sample Output
show interfaces
statistics
(Fast Ethernet)
user@host> show interfaces fe-1/3/1 statistics

Physical interface: fe-1/3/1, Enabled, Physical link is Up
Description: ford fe-1/3/1
Source filtering: Disabled, Flow control: Enabled
Device flags
: Present Running
CoS queues
Current address: 00:90:69:93:04:dc, Hardware address: 00:90:69:93:04:dc
Last flapped
: 2006-04-18 03:08:59 PDT (00:01:24 ago)
Input rate
: 0 bps (0 pps)
Output rate
: 0 bps (0 pps)
Input errors: 0, Output errors: 0
Active alarms : None
Logical interface fe-1/3/1.0 (Index 69) (SNMP ifIndex 50)
Flags: SNMP-Traps Encapsulation: ENET2
Flags: Is-Primary, DCU, SCU-in
Packets
Bytes
Destination class
(packet-per-second)
(bits-per-second)
silver1
0
0
(
0) (
0)
silver2
0
0
(
0) (
0)
silver3
0
0
(
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
Flags: Is-Primary
show interfaces
statistics
user@host> show interfaces ge-5/2/0 statistics detail

727
(Gigabit Ethernet
PICEgress)
Link-level type: Ethernet, MTU: 1514, Speed: 1000mbps, BPDU Error: None,
MAC-REWRITE Error: None, Loopback: Disabled,
Device flags
: Present Running
Link flags
: None
CoS queues
Hold-times
Current address: 00:1d:b5:61:d9:74, Hardware address: 00:1d:b5:61:d9:74
Last flapped
: 2009-11-11 11:24:00 PST (09:23:08 ago)
Statistics last cleared: 2009-11-11 17:50:58 PST (02:56:10 ago)
Traffic statistics:
Input bytes :
271524
0 bps
Output bytes :
37769598
352 bps
Input packets:
3664
0 pps
Output packets:
885790
0 pps
Input bytes :
0
Output bytes :
16681118
Input packets:
0
Output packets:
362633
Multicast statistics:
IPV4 multicast statistics:
Input bytes :
112048
0 bps
Output bytes :
20779920
0 bps
Input packets:
1801
0 pps
Output packets:
519498
0 pps
Input bytes :
156500
0 bps
Output bytes :
16681118
0 bps
Input packets:
1818
0 pps
Output packets:
362633
0 pps
Input errors:
Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Policed discards: 0, L3
incompletes: 0, L2 channel errors: 0,
L2 mismatch timeouts: 0, FIFO errors: 0, Resource errors: 0
Output errors:
Carrier transitions: 0, Errors: 0, Drops: 0, Collisions: 0, Aged packets: 0,
FIFO errors: 0, HS link CRC errors: 0, MTU errors: 0,
Resource errors: 0
Queue counters:
Dropped packets
0 best-effort
882558
882558
1 expedited-fo
2 assured-forw
3 network-cont
3232
3232
Active alarms : None

Flags: SNMP-Traps 0x4000 Encapsulation: ENET2
Traffic statistics:
Input bytes :
271524
Output bytes :
37769598
Input packets:
3664
728
Output packets:
885790
Input bytes :
0
Output bytes :
16681118
Input packets:
0
Output packets:
362633
Local statistics:
Input bytes :
271524
Output bytes :
308560
Input packets:
3664
Output packets:
3659
Transit statistics:
Input bytes :
0
0 bps
Output bytes :
37461038
0 bps
Input packets:
0
0 pps
Output packets:
882131
0 pps
Input bytes :
0
Output bytes :
16681118
Input packets:
0
Output packets:
362633
Multicast statistics:
Input bytes :
112048
0 bps
Output bytes :
20779920
0 bps
Input packets:
1801
0 pps
Output packets:
519498
0 pps
Input bytes :
156500
0 bps
Output bytes :
16681118
0 bps
Input packets:
1818
0 pps
Output packets:
362633
0 pps
Destination: 40.40.40.0/30, Local: 40.40.40.2, Broadcast: 40.40.40.3,
Generation: 167
Protocol inet6, MTU: 1500, Generation: 152, Route table: 0
Destination: ::40.40.40.0/126, Local: ::40.40.40.2
Generation: 169
Addresses, Flags: Is-Preferred
Destination: fe80::/64, Local: fe80::21d:b5ff:fe61:d974
Protocol multiservice, MTU: Unlimited, Generation: 171
Generation: 153, Route table: 0
Policer: Input: __default_arp_policer__
show interfaces
statistics detail
(Aggregated Ethernet)
user@host> show interfaces ae0 detail

Physical interface: ae0, Enabled, Physical link is Up
Source filtering: Disabled, Flow control: Disabled, Minimum links needed: 1,
Minimum bandwidth needed: 0
Device flags
: Present Running
Current address: 00:90:69:0b:2f:f0, Hardware address: 00:90:69:0b:2f:f0
Last flapped
: Never
Traffic statistics:
Input bytes :
28544
0 bps
Output bytes :
39770
0 bps
729
Input packets:
508
0 pps
Output packets:
509
0 pps
Input bytes :
IPv6 28544
Output bytes :
IPv6 0
Input packets:
IPv6 508
Output packets:
IPv6 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 ae0.0 (Index 67) (SNMP ifIndex 139) (Generation 145)
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
Queue counters:
Dropped packets
0 best-effort
1 expedited-fo
2 assured-forw
3 network-cont

Flags: None
Generation: 159
Flags: Is-Primary
Destination: fe80::/64, Local: fe80::206:5bff:fe05:c321,
Broadcast: Unspecified, Generation: 161
show interfaces
statistics detail
730
user@host> show interfaces statistics detail ae0 | no-more

(Aggregated
EthernetIngress)
Link-level type: Ethernet, MTU: 1514, Speed: 1Gbps, BPDU Error: None, MAC-REWRITE
Error: None, Loopback: Disabled,
Device flags
: Present Running
Current address: 00:1d:b5:61:db:f0, Hardware address: 00:1d:b5:61:db:f0
Last flapped
: 2009-11-09 03:30:23 PST (00:01:28 ago)
Traffic statistics:
Input bytes :
544009602
54761856 bps
Output bytes :
3396
0 bps
Input packets:
11826292
148809 pps
Output packets:
42
0 pps
Input bytes :
350818604
Output bytes :
0
Input packets:
7626488
Output packets:
0
Input errors:
Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Giants: 0, Policed discards:
Output errors:
Carrier transitions: 0, Errors: 0, Drops: 0, MTU errors: 0, Resource errors:
0
Queue counters:
Dropped packets
0 best-effort
1 expedited-fo
2 assured-forw
3 network-cont

Queue counters:
Queued packets
Transmitted packets
Dropped packets
21
21
1 expedited-fo
2 assured-forw
3 network-cont
451
451
0 best-effort
Statistics
Packets
pps
Bytes
bps
Bundle:
Input :
11826292
148809
544009602
54761856
Output:
42
0
3396
0
Link:
ge-5/2/0.0
Input :
11826292
148809
544009602
54761856
Output:
42
0
3396
0
Marker Statistics:
Marker Rx
Resp Tx
Unknown Rx
Illegal Rx
ge-5/2/0.0
0
0
0
0
731

Generation: 310
Generation: 312
Destination: fe80::/64, Local: fe80::21d:b5ff:fe61:dbf0
show interfaces
statistics detail
732
user@host> show interfaces statistics detail ae0 | no-more

(Aggregated
EthernetEgress)
Link-level type: Ethernet, MTU: 1514, Speed: 1Gbps, BPDU Error: None, MAC-REWRITE
Error: None, Loopback: Disabled,
Device flags
: Present Running
Current address: 00:1f:12:c2:37:f0, Hardware address: 00:1f:12:c2:37:f0
Last flapped
: 2009-11-09 03:30:24 PST (00:02:42 ago)
Traffic statistics:
Input bytes :
440
0 bps
Output bytes :
1047338120
54635848 bps
Input packets:
7
0 pps
Output packets:
22768200
148466 pps
Input bytes :
288
Output bytes :
723202616
Input packets:
4
Output packets:
15721796
Input errors:
Output errors:
0
Queue counters:
Dropped packets
0 best-effort
1 expedited-fo
2 assured-forw
3 network-cont

Queue counters:
Queued packets
Transmitted packets
Dropped packets
201985796
201985796
1 expedited-fo
2 assured-forw
3 network-cont
65
65
0 best-effort
Statistics
Packets
pps
Bytes
bps
Bundle:
Input :
7
0
440
0
Output:
22768200
148466
1047338120
54635848
Link:
ge-2/1/6.0
Input :
7
0
440
0
Output:
22768200
148466
1047338120
54635848
Marker Statistics:
Marker Rx
Resp Tx
Unknown Rx
Illegal Rx
ge-2/1/6.0
0
0
0
0
733

Generation: 420
Destination: ::/26, Local: ::30.30.30.1
Generation: 422
Destination: fe80::/64, Local: fe80::21f:12ff:fec2:37f0
show interfaces
statistics
(SONET/SDH)
user@host> show interfaces statistics detail so-3/0/0 | no-more

Physical interface: so-3/0/0, Enabled, Physical link is Up
Link-level type: PPP, MTU: 4474, Clocking: Internal, SONET mode, Speed: OC192,
Loopback: None, FCS: 16, Payload scrambler: Enabled
Device flags
: Present Running
Link flags
: Keepalives
Hold-times
Input : 13 (last seen 00:00:04 ago)
LCP state: Opened
NCP state: inet: Opened, inet6: Opened, iso: Not-configured, mpls: Not-configured
CHAP state: Closed
PAP state: Closed
CoS queues
Last flapped
: 2009-11-09 02:52:34 PST (01:12:39 ago)
Traffic statistics:
Input bytes :
2559160294
54761720 bps
Output bytes :
10640
48 bps
Input packets:
55633975
148809 pps
Output packets:
216
0 pps
Input bytes :
647922328
Output bytes :
0
Input packets:
14085269
Output packets:
0
Input errors:
Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Giants: 0, Bucket drops:
0, Policed discards: 0, L3 incompletes: 0,
L2 channel errors: 0, L2 mismatch timeouts: 0, HS link CRC errors: 0, HS link
FIFO overflows: 0
Output errors:
Carrier transitions: 0, Errors: 0, Drops: 0, Aged packets: 0, HS link FIFO
underflows: 0, MTU errors: 0
Queue counters:
Dropped packets
734
0 best-effort
1 expedited-fo
2 assured-forw
3 network-cont
SONET alarms
SONET defects
213
213
: None
: None
Logical interface so-3/0/0.0 (Index 72) (SNMP ifIndex 578) (Generation 182)
Flags: Point-To-Point SNMP-Traps 0x4000 Encapsulation: PPP
Generation: 322
Generation: 324
Destination: fe80::/64, Local: fe80::2a0:a5ff:fe61:9264
Generation: 326
show interfaces
statistics (Aggregated
SONET/SDHIngress)
user@host> show interfaces statistics detail as0 | no-more

Physical interface: as0, Enabled, Physical link is Up
Link-level type: PPP, MTU: 4474, Speed: OC192, Minimum links needed: 1, Minimum
bandwidth needed: 0
Device flags
: Present Running
Link flags
: Keepalives
Last flapped
: 2009-11-09 03:45:53 PST (00:09:38 ago)
Traffic statistics:
Input bytes :
2969786332
54761688 bps
Output bytes :
11601
0 bps
Input packets:
64560636
148808 pps
Output packets:
225
0 pps
Input bytes :
2086013152
Output bytes :
0
Input packets:
45348114
Output packets:
0
Input errors:
Output errors:
0
Queue counters:
Dropped packets
0 best-effort
1 expedited-fo
2 assured-forw
3 network-cont
222
222
Logical interface as0.0 (Index 71) (SNMP ifIndex 576) (Generation 179)
Statistics
Packets
pps
Bytes
bps
735
Bundle:
Input :
64560550
148808
2969785300
54761688
Output:
139
0
10344
0
Link:
so-3/0/0.0
Input :
64560550
148808
2969785300
54761688
Output:
139
0
10344
0
Generation: 316
Generation: 318
Destination: fe80::/64, Local: fe80::2a0:a5ff:fe61:9264
Generation: 320
show interfaces
statistics (Aggregated
SONET/SDHEgress)
user@host> show interfaces statistics detail as0 | no-more

Physical interface: as0, Enabled, Physical link is Up
Link-level type: PPP, MTU: 4474, Speed: OC192, Minimum links needed: 1, Minimum
bandwidth needed: 0
Device flags
: Present Running
Link flags
: Keepalives
Last flapped
: 2009-11-09 03:43:37 PST (00:12:48 ago)
Traffic statistics:
Input bytes :
11198
392 bps
Output bytes :
3101452132
54783448 bps
Input packets:
234
0 pps
Output packets:
67422937
148868 pps
Input bytes :
5780
Output bytes :
2171015678
Input packets:
72
Output packets:
47195993
Input errors:
Output errors:
0
Queue counters:
Dropped packets
0 best-effort
67422830
67422830
1 expedited-fo
2 assured-forw
3 network-cont
90
90
Logical interface as0.0 (Index 71) (SNMP ifIndex 548) (Generation 206)
Statistics
Packets
pps
Bytes
bps
736
Bundle:
Input :
144
0
10118
392
Output:
67422847
148868
3101450962
54783448
Link:
so-0/1/0.0
Input :
144
0
10118
392
Output:
67422847
148868
3101450962
54783448
Generation: 426
Destination: ::/26, Local: ::30.30.30.1
Generation: 428
Destination: fe80::/64, Local: fe80::2a0:a5ff:fe63:1d0a
Generation: 429
show interfaces
statistics (PTX Series
user@host> show interfaces statistics em0

Physical interface: em0, Enabled, Physical link is Up
737
Packet Transport
Switches)
Type: Ethernet, Link-level type: Ethernet, MTU: 1514, Speed: 1000mbps

Device flags
: Present Running
Interface flags: SNMP-Traps
Link type
: Full-Duplex
Current address: 00:80:f9:25:00:1b, Hardware address: 00:80:f9:25:00:1b
Last flapped
: Never
Input packets : 212620
Output packets: 71
Logical interface em0.0 (Index 3) (SNMP ifIndex 0)
Input packets : 212590
Output packets: 71
Flags: Is-Primary
Addresses, Flags: Is-Default Is-Preferred Is-Primary
Destination: 192.168.3/24, Local: 192.168.3.30,
Broadcast: 192.168.3.255
show interfaces
statistics (ACX Series
routers)
user@host> show interfaces statistics ge-0/1/7

Physical interface: ge-0/1/7, Enabled, Physical link is Down
Link-level type: Ethernet, Media type: Copper, MTU: 1514, Link-mode: Full-duplex,
Speed: 1000mbps, BPDU Error: None, MAC-REWRITE Error: None, Loopback: Disabled,
Device flags
Interface flags: Hardware-Down SNMP-Traps Internal: 0x0
Link flags
: None
CoS queues
Current address: 84:18:88:c1:49:a3, Hardware address: 84:18:88:c1:49:a3
Last flapped
: 2012-05-11 04:25:28 PDT (2d 20:23 ago)
Input rate
: 0 bps (0 pps)
Output rate
: 0 bps (0 pps)
Active alarms : LINK
Active defects : LINK
Interface transmit statistics: Disabled
738
show isis database

Syntax
Syntax (EX Series

Switches and QFX
Series)
Release Information
Description
Options
show isis database

<system-id>
<brief | detail | extensive>
<level (1 | 2)>
show isis database
<system-id>
<level (1 | 2)>

Display the entries in the IS-IS link-state database, which contains data about PDU
packets.
noneDisplay standard information about IS-IS link-state database entries for all routing
instances.
system id(Optional) Display IS-IS link-state database entries for the specified
intermediate system.
brief | detail | extensive(Optional) Display the specified level of output.
instance instance-name(Optional) Display IS-IS link-state database entries for the
specified routing instance.

level (1 | 2)(Optional) Display IS-IS link-state database entries for the specified IS-IS
level.
logical-system (all | logical-system-name)(Optional) Display standard information
about IS-IS link-state database entries for all logical systems or for a particular
logical system.
Required Privilege
Level
Related
Documentation
view
clear isis database
show isis database on page 742

show isis database brief on page 742
show isis database detail on page 742
show isis database extensive on page 743
739
Output Fields
Table 51 on page 740 describes the output fields for the show isis database command.
Output fields are listed in the approximate order in which they appear. Fields that contain
internal IS-IS information useful only in troubleshooting obscure problems are not
described in the table. For more details about these fields, contact your customer support
representative.
Table 51: show isis database Output Fields

Field Name
Field Description
Level of Output
Interface name
Name of the interface on which the link-state PDU has been received; always
IS-IS for this command.
All levels
level
Level of intermediate system:
All levels
1Intermediate system routes within an area; when the destination is outside
an area, it routes toward a Level 2 system.
2Intermediate system routes between areas and toward other ASs.
LSP ID
Link-state PDU identifier.
All levels
Sequence
Sequence number of the link-state PDU.
All levels
Checksum
Checksum value of the link-state PDU.
All levels
Lifetime (secs)
Remaining lifetime of the link-state PDU, in seconds.
All levels
Attributes
Attributes of the specified database: L1, L2, Overload, or Attached (L1 only).
none brief
# LSPs
Total number of link-state PDUs in the specified link-state database.
none brief
IP prefix
Prefix advertised by this link-state PDU.
detail extensive
IS neighbor
IS-IS neighbor of the advertising system.
detail extensive
ES neighbor
(J Series routers only) An ES-IS neighbor of the advertising system.
detail extensive
IP prefix
IPv4 prefix advertised by this link-state PDU.
detail extensive
V6 prefix
IPv6 prefix advertised by this link-state PDU.
detail extensive
Metric
Metric of the prefix or neighbor.
detail extensive
Header
LSP IDLink state PDU identifier of the header.
extensive
LengthHeader length.
Allocated LengthAmount of length available for the header.
Router IDAddress of the local routing device.
Remaining LifetimeRemaining lifetime of the link-state PDU, in seconds.
740
Table 51: show isis database Output Fields (continued)

Field Name
Field Description
Level of Output
Packet
LSP IDThe identifier for the link-state PDU.
extensive
LengthPacket length.
LifetimeRemaining lifetime, in seconds.
ChecksumThe checksum of the link-state PDU.
SequenceThe sequence number of the link-state PDU. Every time the
link-state PDU is updated, this number increments.
TLVs
AttributesPacket attributes.
NLPIDNetwork layer protocol identifier.
Fixed lengthSpecifies the set length for the packet.
Area AddressArea addresses that the routing device can reach.
SpeaksSupported routing protocols.
IP router idID of the routing device (usually the IP address).
IP addressIPv4 address.
HostnameAssigned name of the routing device.
IP prefixIP prefix of the routing device.
MetricIS-IS metric that measures the cost of the adjacency between the
extensive
originating routing device and the advertised routing device.
IP extended prefixExtended IP prefix of the routing device.
IS neighborDirectly attached neighbors name and metric.
IS extended neighborDirectly attached neighbors name, metric, and IP
address.
741
Sample Output
show isis database
user@host> show isis database

IS-IS level 1 link-state database:
LSP ID
Sequence Checksum Lifetime Attributes
kobuk.00-00
0x3
0x3167
1057 L1 L2
camaro.00-00
0x5
0x770e
1091 L1 L2
ranier.00-00
0x4
0xaa95
1091 L1 L2
glacier.00-00
0x4
0x206f
1089 L1 L2
glacier.02-00
0x1
0xd141
1089 L1 L2
badlands.00-00
0x3
0x87a2
1093 L1 L2
6 LSPs
LSP ID
Sequence Checksum Lifetime Attributes
kobuk.00-00
0x6
0x8d6b
1096 L1 L2
camaro.00-00
0x9
0x877b
1101 L1 L2
ranier.00-00
0x8
0x855d
1103 L1 L2
glacier.00-00
0x7
0xf892
1098 L1 L2
glacier.02-00
0x1
0xd141
1089 L1 L2
badlands.00-00
0x6
0x562
1105 L1 L2
6 LSPs
show isis database

brief
The output for the show isis database brief command is identical to that for the show isis
database command. For sample output, see show isis database on page 742.
show isis database

detail
user@host> show isis database logical-system CE3 sisira.00-00 detail

sisira.00-00 Sequence: 0x11, Checksum: 0x10fc, Lifetime: 975 secs
IS neighbor: hemantha-CE3.02
Metric:
10
ES neighbor: 0015.0015.0015
Metric:
10 Down
ES neighbor: 0025.0025.0025
Metric:
10 Down
ES neighbor: 0030.0030.0030
Metric:
10 Down
ES neighbor: 0040.0040.0040
Metric:
10 Down
ES neighbor: sisira
Metric:
0
IP prefix: 1.0.0.0/24
Metric:
10 External
IP prefix: 3.0.0.0/24
Metric:
10 External
IP prefix: 4.0.0.0/24
Metric:
10 External
IP prefix: 5.0.0.0/24
Metric:
10 Internal
IP prefix: 15.15.15.15/32
Metric:
10 External
IP prefix: 25.25.25.25/32
Metric:
10 External
IP prefix: 30.30.30.30/32
Metric:
10 External
IP prefix: 40.40.40.40/32
Metric:
10 External
IP prefix: 60.60.60.60/32
Metric:
0 Internal
Down
Down
Down
Up
Down
Down
Down
Down
Up

sisira.00-00 Sequence: 0x13, Checksum: 0x69ac, Lifetime: 993 secs
Metric:
10
IP prefix: 1.0.0.0/24
Metric:
10 External Down
IP prefix: 3.0.0.0/24
Metric:
10 External Down
IP prefix: 4.0.0.0/24
Metric:
10 External Down
IP prefix: 5.0.0.0/24
Metric:
10 Internal Up
IP prefix: 15.15.15.15/32
Metric:
10 External Down
IP prefix: 25.25.25.25/32
Metric:
10 External Down
IP prefix: 30.30.30.30/32
Metric:
10 External Down
742
IP prefix: 40.40.40.40/32
Metric:
10 External
IP prefix: 50.50.50.50/32
Metric:
10 Internal
IP prefix: 60.60.60.60/32
Metric:
0 Internal
ISO prefix: 60.0006.80ff.f800.0000.0108.0001.0015.0015.0015/152
Metric:
10 External
ISO prefix: 60.0006.80ff.f800.0000.0108.0001.0025.0025.0025/152
Metric:
10 External
ISO prefix: 60.0006.80ff.f800.0000.0108.0001.0030.0030.0030/152
Metric:
10 External
ISO prefix: 60.0006.80ff.f800.0000.0108.0001.0040.0040.0040/152
Metric:
10 External
ISO prefix: 60.0006.80ff.f800.0000.0108.0001.0060.0060.0060/152
Metric:
0 Internal
show isis database

extensive
Down
Up
Up
Down
Down
Down
Down
Up
user@host> show isis database logical-system CE3 sisira.00-00 extensive

sisira.00-00 Sequence: 0x11, Checksum: 0x10fc, Lifetime: 970 secs
Metric:
10
Two-way fragment: hemantha-CE3.02-00, Two-way first fragment:
hemantha-CE3.02-00
ES neighbor: 0015.0015.0015
Metric:
10 Down
ES neighbor: 0025.0025.0025
Metric:
10 Down
ES neighbor: 0030.0030.0030
Metric:
10 Down
ES neighbor: 0040.0040.0040
Metric:
10 Down
ES neighbor: sisira
Metric:
0
IP prefix: 1.0.0.0/24
Metric:
10 External
IP prefix: 3.0.0.0/24
Metric:
10 External
IP prefix: 4.0.0.0/24
Metric:
10 External
IP prefix: 5.0.0.0/24
Metric:
10 Internal
IP prefix: 15.15.15.15/32
Metric:
10 External
IP prefix: 25.25.25.25/32
Metric:
10 External
IP prefix: 30.30.30.30/32
Metric:
10 External
IP prefix: 40.40.40.40/32
Metric:
10 External
IP prefix: 60.60.60.60/32
Metric:
0 Internal
Down
Down
Down
Up
Down
Down
Down
Down
Up
Header: LSP ID: sisira.00-00, Length: 336 bytes

Allocated length: 336 bytes, Router ID: 0.0.0.0
Remaining lifetime: 970 secs, Level: 1, Interface: 333
Estimated free bytes: 144, Actual free bytes: 0
Aging timer expires in: 970 secs
Protocols: IP, IPv6, CLNS
Packet: LSP ID: sisira.00-00, Length: 336 bytes, Lifetime : 1198 secs
Checksum: 0x10fc, Sequence: 0x11, Attributes: 0xb L1 L2 Attached
NLPID: 0x83, Fixed length: 27 bytes, Version: 1, Sysid length: 0 bytes
Packet type: 18, Packet version: 1, Max area: 0
TLVs:
Area address: 60.0006.80ff.f800.0000.0108.0001 (13)
Speaks: IP
Speaks: IPV6
Speaks: CLNP
Hostname: sisira
ES neighbor TLV: Internal, Metric: default 0, Up
ES: sisira
IS neighbor: hemantha-CE3.02, Internal, Metric: default 10
IS extended neighbor: hemantha-CE3.02, Metric: default 10
ES neighbor TLV: External, Metric: default 10, Down
ES: 0040.0040.0040
743

ES: 0025.0025.0025
ES: 0015.0015.0015
ES: 0030.0030.0030
IP external prefix: 3.0.0.0/24, Internal, Metric: default 10,
IP external prefix: 40.40.40.40/32, Internal, Metric: default
IP extended prefix: 3.0.0.0/24 metric 10 down
IP prefix: 60.60.60.60/32, Internal, Metric: default 0, Up
IP extended prefix: 60.60.60.60/32 metric 0 up
No queued transmissions
Down
10, Down
Down
10, Down
10, Down
Down
10, Down

sisira.00-00 Sequence: 0x13, Checksum: 0x69ac, Lifetime: 988 secs
Metric:
10
Two-way fragment: hemantha-CE3.02-00, Two-way first fragment:
hemantha-CE3.02-00
IP prefix: 1.0.0.0/24
Metric:
10 External
IP prefix: 3.0.0.0/24
Metric:
10 External
IP prefix: 4.0.0.0/24
Metric:
10 External
IP prefix: 5.0.0.0/24
Metric:
10 Internal
IP prefix: 15.15.15.15/32
Metric:
10 External
IP prefix: 25.25.25.25/32
Metric:
10 External
IP prefix: 30.30.30.30/32
Metric:
10 External
IP prefix: 40.40.40.40/32
Metric:
10 External
IP prefix: 50.50.50.50/32
Metric:
10 Internal
IP prefix: 60.60.60.60/32
Metric:
0 Internal
ISO prefix: 60.0006.80ff.f800.0000.0108.0001.0015.0015.0015/152
Metric:
10 External
ISO prefix: 60.0006.80ff.f800.0000.0108.0001.0025.0025.0025/152
Metric:
10 External
ISO prefix: 60.0006.80ff.f800.0000.0108.0001.0030.0030.0030/152
Metric:
10 External
ISO prefix: 60.0006.80ff.f800.0000.0108.0001.0040.0040.0040/152
Metric:
10 External
ISO prefix: 60.0006.80ff.f800.0000.0108.0001.0060.0060.0060/152
Metric:
0 Internal
Down
Down
Down
Up
Down
Down
Down
Down
Up
Up
Down
Down
Down
Down
Up
Header: LSP ID: sisira.00-00, Length: 427 bytes

Allocated length: 427 bytes, Router ID: 0.0.0.0
Remaining lifetime: 988 secs, Level: 2, Interface: 333
Estimated free bytes: 130, Actual free bytes: 0
Aging timer expires in: 988 secs
Protocols: IP, IPv6, CLNS
Packet: LSP ID: sisira.00-00, Length: 427 bytes, Lifetime : 1198 secs
744
Checksum: 0x69ac, Sequence: 0x13, Attributes: 0x3 L1 L2

NLPID: 0x83, Fixed length: 27 bytes, Version: 1, Sysid length: 0 bytes
Packet type: 20, Packet version: 1, Max area: 0
TLVs:
Area address: 60.0006.80ff.f800.0000.0108.0001 (13)
Speaks: IP
Speaks: IPV6
Speaks: CLNP
Hostname: sisira
IS neighbor: hemantha-CE3.02, Internal, Metric: default 10
IS extended neighbor: hemantha-CE3.02, Metric: default 10
IP external prefix: 3.0.0.0/24, Internal, Metric: default 10, Down
ISO prefix-neighbor TLV: Internal, Metric: default 0, Up
Prefix : 60.0006.80ff.f800.0000.0108.0001.0060.0060.0060/152
ISO prefix-neighbor TLV: External, Metric: default 10, Down
Prefix : 60.0006.80ff.f800.0000.0108.0001.0040.0040.0040/152
Prefix : 60.0006.80ff.f800.0000.0108.0001.0025.0025.0025/152
Prefix : 60.0006.80ff.f800.0000.0108.0001.0015.0015.0015/152
Prefix : 60.0006.80ff.f800.0000.0108.0001.0030.0030.0030/152
No queued transmissions
745
show isis hostname

Syntax
Syntax (EX Series

Switches and QFX
Series)
Release Information
Description
Options
show isis hostname

show isis hostname

Display IS-IS hostname database information.
noneDisplay IS-IS hostname database information.

Required Privilege
Level
Output Fields
view
show isis hostname on page 746

Table 52 on page 746 describes the output fields for the show isis hostname command.
Table 52: show isis hostname Output Fields

Field Name
Field Description
System Id
System identifier mapped to the hostname.
Hostname
Hostname mapped to the system identifier.
Type
Type of mapping between system identifier and hostname.
DynamicHostname mapping determined as described in
RFC 2763, Dynamic Hostname Exchange Mechanism for IS-IS.
StaticHostname mapping configured by user.
Sample Output
show isis hostname
746
user@host> show isis hostname

IS-IS hostname database:
System Id
Hostname
1921.6800.4201 isis1
1921.6800.4202 isis2
1921.6800.4203 isis3
Type
Dynamic
Static
Dynamic
show isis interface

Syntax
Syntax (EX Series

Switches and QFX
Series)
Release Information
Description
show isis interface

<interface-name>
show isis interface
<interface-name>

Display status information about IS-IS-enabled interfaces.
NOTE: If the configured metric for an IS-IS level is above 63, and the
wide-metrics-only statement is not configured, the show isis interface detail
command and the show isis interface extensive command display 63 as the
metric value for that level. Configure the wide-metrics-only statement to
generate metric values greater than 63 on a per IS-IS level basis.
The show isis interface command displays the configured metric value for an
IS-IS level irrespective of whether is configured or not.
Options
noneDisplay standard information about all IS-IS-enabled interfaces.

interface-name(Optional) Display information about the specified interface only.

Required Privilege
Level
Related
Documentation
Output Fields
view
Example: Enabling Wide IS-IS Metrics for Traffic Engineering
show isis interface on page 750

show isis interface brief on page 750
show isis interface detail on page 750
show isis interface extensive on page 750
show isis interface extensive (With LDP) on page 750
Table 53 on page 748 describes the output fields for the show isis interface command.
747
Table 53: show isis interface Output Fields

Field Name
Field Description
Level of Output
interface-name
Name of the interface.
detail
Designated router
Routing device selected by other routers that is responsible for sending link-state
advertisements that describe the network. Used only on broadcast networks.
detail
Index
Interface index assigned by the Junos OS kernel.
detail
State
Internal implementation information.
detail
Circuit id
Circuit identifier.
detail
Circuit type
Circuit type:
detail
1Level 1 only
2Level 2 only
3Level 1 and Level 2
LSP interval
Interval between link-state PDUs sent from the interface.
detail
CSNP interval
Interval between complete sequence number PDUs sent from the interface.
detail extensive
Sysid
System identifier.
detail
Interface
Interface through which the adjacency is made.
none brief
L or Level
Level:
All levels
1Level 1 only
2Level 2 only
CirID
Circuit identifier.
none brief
Level 1 DR
Level 1 designated intermediate system.
none brief
Level 2 DR
Level 2 designated intermediate system.
none brief
L1/L2 Metric
Interface's metric for Level 1 and Level 2. If there is no information, the metric
is 0.
none brief
Adjacency
advertisement:
Advertise
This routing device has signaled to advertise this interface to its neighbors in
their label-switched paths (LSPs).
detail extensive
Adjacency
advertisement:
Suppress
This neighbor has signaled not to advertise this interface in the routing devices
outbound LSPs.
detail extensive
Adjacencies
Number of adjacencies established on this interface.
detail
748
Table 53: show isis interface Output Fields (continued)

Field Name
Field Description
Level of Output
Priority
Priority value for this interface.
detail
Metric
Metric value for this interface.
detail
Hello(s) / Hello
Interval
Interface's hello interval.
detail extensive
Hold(s) / Hold Time
Interface's hold time.
detail extensive
Designated Router
Router responsible for sending network link-state advertisements, which describe

all the routers attached to the network.
detail
Hello padding
Type of hello padding:
extensive
AdaptiveOn point-to-point connections, the hello packets are padded from
the initial detection of a new neighbor until the neighbor verifies the adjacency
as Up in the adjacency state TLV. If the neighbor does not support the
adjacency state TLV, then padding continues. On LAN connections, padding
starts from the initial detection of a new neighbor until there is at least one
active adjacency on the interface.
Loose(Default) The hello packet is padded from the initial detection of a
new neighbor until the adjacency transitions to the Up state.
StrictPadding is performed on all interface types and for all adjacency
states, and is continuous.

LDP sync state
Current LDP synchronization state: in sync, in holddown, or not supported.
extensive
reason
Reason for being in the LDP sync state.
extensive
config holdtime
Configured value of the hold timer.
extensive
remaining
If the state is not in sync and the hold time is not infinity, then this field displays
the remaining hold time in seconds.
extensive
749
Sample Output
show isis interface
user@host> show isis interface

IS-IS interface database:
Interface
L CirID Level 1 DR
at-2/3/0.0
3
0x1 Point to Point
lo0.0
0
0x1 Passive
Level 2 DR
Point to Point
Passive
L1/L2 Metric
10/10
0/0
show isis interface

brief
The output for the show isis interface brief command is identical to that for the show isis
interface command. For sample output, see show isis interface on page 750.
show isis interface

detail
user@host> show isis interface detail

at-2/3/0.0
Index: 66, State: 0x6, Circuit id: 0x1, Circuit type: 3
LSP interval: 100 ms, CSNP interval: 5 s
Level Adjacencies Priority Metric Hello (s) Hold (s) Designated Router
1
1
64
10
9.000
27
2
1
64
10
9.000
27
lo0.0
LSP interval: 100 ms, CSNP interval: disabled
Level Adjacencies Priority Metric Hello (s) Hold (s) Designated Router
1
0
64
0 Passive
2
0
64
0 Passive
show isis interface

extensive
user@host> show isis interface extensive

at-2/3/0.0
LSP interval: 100 ms, CSNP interval: 5 s, Loose Hello padding
Level 1
Adjacencies: 1, Priority: 64, Metric: 10
Hello Interval: 9.000 s, Hold Time: 27 s
Level 2
lo0.0
LSP interval: 100 ms, CSNP interval: disabled, Loose Hello padding
Level 1
Passive
Level 2
Passive
show isis interface

extensive (With LDP)
user@host> show isis interface extensive

so-1/1/2.0
LSP interval: 100 ms, CSNP interval: 20 s, Loose Hello padding
Adjacency advertisement: Advertise
LDP sync state: in sync, for: 00:01:28, reason: LDP up during config
config holdtime: 20 seconds
750
Level 2
IPV4 MulticastMetric: 10
IPV6 UnicastMetric: 10
751
show isis overview

Syntax
Syntax (EX Series

Switches and QFX
Series)
Release Information
Description
Options
show isis overview

show isis overview

Display IS-IS overview information.
noneDisplay standard overview information about IS-IS for all routing instances.
instance instance-name(Optional) Display overview information for the specified routing
instance.

Required Privilege
Level
Output Fields
view
show isis overview on page 754

Table 54 on page 752 lists the output fields for the show isis overview command. Output
Table 54: show isis overview Output Fields

Field Name
Field Description
Instance
IS-IS routing intance.
Router ID
Router ID of the routing device.
Adjacency holddown
Adjacency holddown capability: enabled or disabled.
Maximum Areas
Maximum number of IS-IS areas advertised by the routing device.
LSP life time
Lifetime of the link-state PDU, in seconds.
Attached bit evaluation
Attached bit capability: enabled or disabled.
SPF delay
Delay before performing consecutive shortest-path-first (SPF) calculations.
SPF holddown
Delay before performing additional SPF calculations after the maximum number of consecutive SPF
calculations is reached.
752
Table 54: show isis overview Output Fields (continued)

Field Name
Field Description
SPF rapid runs
Maximum number of SPF calculations that can be performed in succession before the holddown timer
begins.
Overload bit at startup

is set
Overload bit capability is enabled.
Overload high metrics
Overload high metrics capability: enabled or disabled.
Overload timeout
Time period after which overload is reset and the time that remains before the timer is set to expire.
Traffic engineering
Traffic engineering capability: enabled or disabled.
Restart
Graceful restart capability: enabled or disabled.
Restart duration
Time period for complete reacquisition of IS-IS neighbors.
Helper mode
Graceful restart helper capability: enabled or disabled.
Level
IS-IS level:
1Level 1 information
2Level 2 information
IPv4 is enabled
IP Protocol version 4 capability is enabled.
IPv6 is enabled
IP Protocol version 6 capability is enabled.
CLNS is enabled
(J Series routers only) OSI CLNP capability is enabled.
Internal route
preference
Preference value of internal routes.
External route
preference
Preference value of external routes.
Wide area metrics are

enabled
Wide area metrics capability is enabled.
Narrow metrics are

enabled
Narrow metrics capability is enabled.
753
Sample Output
show isis overview
754
user@host> show isis overview

Instance: master
Router ID: 192.168.1.220
Adjacency holddown: enabled
Maximum Areas: 3
LSP life time: 65535
Attached bit evaluation: enabled
SPF delay: 200 msec, SPF holddown: 5000 msec, SPF rapid runs: 3
Overload bit at startup is set
Overload high metrics: disabled
Overload timeout: 300 sec, expires in 295 seconds
IPv4 is enabled, IPv6 is enabled
Traffic engineering: enabled
Restart: Enabled
Restart duration: 210 sec
Helper mode: Enabled
Level 1
Internal route preference: 15
External route preference: 160
Wide metrics are enabled, Narrow metrics are enabled
Level 2
Internal route preference: 18
External route preference: 165
Wide metrics are enabled
show isis route

Syntax
show isis route

<destination>
<inet | inet6>
<topology (ipv4-multicast | ipv6-multicast | ipv6-unicast | unicast)>
Syntax (EX Series

Switches and QFX
Series)
show isis route

<destination>
<inet | inet6>
Release Information
Description
Options

Display the routes in the IS-IS routing table.
noneDisplay all routes in the IS-IS routing table for all supported address families for
all routing instances.

destination(Optional) Destination address for the route.
inet | inet6(Optional) Display inet (IPv4) or inet6 (IPv6) routes, respectively.
instance instance-name(Optional) Display routes for the specified routing instance only.

topology (ipv4-multicast | ipv6-multicast | ipv6-unicast | unicast)(Optional) Display
routes for the specified topology only, or use unicast to display information, if
available, for both IPv4 and IPv6 unicast topologies.
Required Privilege
Level
Output Fields
view
show isis route logical-system on page 757

show isis route (CLNS) on page 757
show isis route on page 757
Table 55 on page 755 describes the output fields for the show isis route command. Output
Table 55: show isis route Output Fields

Field Name
Field Description
Current version
Number of the current version of the IS-IS routing table.
755
Table 55: show isis route Output Fields (continued)
756
Field Name
Field Description
L1
Version of Level 1 SPF that was run.
L2
Version of Level 2 SPF that was run.
Prefix
Destination of the route.
IS-IS level:
1Level 1 only
2Level 2 only
Version
Version of SPF that generated the route.
Metric
Metric value associated with the route.
Type
Metric type: int (internal) or ext (external).
Interface
Interface to the next hop.
Via
System identifier of the next hop, displayed as a name if possible.
ISO Routes
ISO routing table entries.
snpa
MAC address.
Sample Output
show isis route
logical-system
user@host> show isis route logical-system ls1

IS-IS routing table
Current version: L1: 8 L2: 11
Prefix
L Version Metric Type Interface
Via
10.9.7.0/30
2
11
20 int gr-0/2/0.0
h
10.9.201.1/32
2
11
60 int gr-0/2/0.0
h
IPV6 Unicast IS-IS routing table
Prefix
L Version Metric Type Interface
Via
8009:3::a09:3200/126 2
11
20 int gr-0/2/0.0 h
show isis route (CLNS)
user@host> show isis route

IS-IS routing table
IPv4/IPv6 Routes
Prefix
L Version
Metric Type Interface
Via
0.0.0.0/0
1
10
10 int fe-0/0/1.0
ISIS.0
ISO Routes
Prefix L
Version
Via
snpa
0/0
1
10
10 int fe-0/0/1.0
isis.0 0:12:0:34:0:56
47.0005.80ff.f800.0000.0108.0001/104
1
10
0 int
47.0005.80ff.f800.0000.0108.0001.1921.6800.4001/152
1
10
10 int fe-0/0/1.0 isis.0 0:12:0:34:0:56
47.0005.80ff.f800.0000.0108.0001.1921.6800.4002/152
1
10
20 int fe-0/0/1.0 isis.0 0:12:0:34:0:56
47.0005.80ff.f800.0000.0108.0002/104
1
10
0 int
47.0005.80ff.f800.0000.0108.0002.1921.6800.4001/152
1
10
10 int fe-0/0/1.0 isis.0 0:12:0:34:0:56
show isis route
user@host> show isis route

IS-IS routing table
IPv4/IPv6 Routes
---------------Prefix
10.255.71.52/32
L
2
Version
13
10.255.71.238/32
13
10.255.71.239/32
13

10
int ae0.0
20
20
int
int
NH
Via
IPV4 camaro
so-6/0/0.0
IPV4 olympic
as0.0
IPV4 glacier
so-6/0/0.0
IPV4 olympic
ae0.0
IPV4 camaro
10.255.71.242/32
13
10
int
as0.0
IPV4 glacier
10.255.71.243/32
13
10
int
so-6/0/0.0
IPV4 olympic
12.13.0.0/30
13
20
int
so-6/0/0.0
IPV4 olympic
12.15.0.0/30
13
20
int
so-6/0/0.0
IPV4 olympic
13.15.0.0/30
13
30
int
ae0.0
IPV4 camaro
so-6/0/0.0
IPV4 olympic
757
IPV4 glacier
13.16.0.0/30
13
25
int
as0.0
IPV4 glacier
14.15.0.0/30
13
20
int
ae0.0
IPV4 camaro
192.2.1.0/30
13
30
int
so-6/0/0.0
IPV4 olympic
as0.0
IPV4 glacier
so-6/0/0.0
IPV6 olympic
as0.0
IPV6 glacier
1eee::/64
13
30
int
abcd::10:255:71:52/128
13
10
int
ae0.0
IPV6 camaro
abcd::10:255:71:238/128
13
20
int
so-6/0/0.0
IPV6 olympic
as0.0
IPV6 glacier
so-6/0/0.0
IPV6 olympic
ae0.0
IPV6 camaro
abcd::10:255:71:239/128
758
as0.0
13
20
int
abcd::10:255:71:242/128
13
10
int
as0.0
IPV6 glacier
abcd::10:255:71:243/128
13
10
int
so-6/0/0.0
IPV6 olympic
show isis spf

Syntax
show isis spf (brief | log | results)

<level (1 | 2)>
Syntax (EX Series

Switches)
show isis spf (brief | log | results)

<level (1 | 2)>
Release Information
Description
Options

Display information about IS-IS shortest-path-first (SPF) calculations.
briefDisplay an overview of SPF calculations.
instance instance instance-name(Optional) Display SPF calculations for the specified
routing instance.
level (1 | 2)(Optional) Display SPF calculations for the specified IS-IS level.
logDisplay the log of SPF calculations.

resultsDisplay the results of SPF calculations.
topology (ipv4-multicast | ipv6-multicast | ipv6-unicast | unicast)(Optional) Display
SPF calculations for the specified topology only.

Required Privilege
Level
Output Fields
view
show isis spf log on page 761

show isis spf results logical-system on page 761
show isis spf results (CLNS) on page 763
Table 56 on page 759 describes the output fields for the show isis spf command. Output
Table 56: show isis spf Output Fields

Field Name
Field Description
Node
System ID of a node.
Metric
Metric to the node.
759
Table 56: show isis spf Output Fields (continued)
760
Field Name
Field Description
Interface
Interface of the next hop.
Via
System ID of the next hop.
SNPA
Subnetwork point of attachment (MAC address of the next hop).
Start time
(log option only) Time that the SPF computation started.
Elapsed (secs)
(log option only) Length of time, in seconds, required to complete

the SPF computation.
Count
(log option only) Number of times the SPF was triggered.
Reason
(log option only) Reason that the SPF computation was completed.
Sample Output
show isis spf log
show isis spf results
user@host> show isis spf log logical-system lsl

IS-IS level 1 SPF log:
Start time
Elapsed (secs) Count
Fri Oct 31 12:41:18
0.000069
1
Fri Oct 31 12:41:18
0.000107
3
Fri Oct 31 12:41:18
0.000050
3
Fri Oct 31 12:41:23
0.000033
1
Fri Oct 31 12:41:28
0.000178
5
Fri Oct 31 12:41:59
0.000060
1
Fri Oct 31 12:42:30
0.000161
2
Fri Oct 31 12:56:58
0.000198
1
Fri Oct 31 13:10:29
0.000209
1
IS-IS level 2 SPF log:
Reason
Reconfig
Updated LSP fix.00-00
Address change on so-1/2/2.0
New adjacency scat on ge-1/1/0.0
Multi area attachment change
Periodic SPF
Periodic SPF
Start time
Fri Oct 31 12:41:18
0.000035
1
Fri Oct 31 12:41:18
0.000047
2
Fri Oct 31 12:41:18
0.000043
5
Fri Oct 31 12:41:23
0.000022
1
Fri Oct 31 12:41:59
0.000144
3
Fri Oct 31 12:42:30
0.000257
3
Fri Oct 31 12:54:37
0.000195
1
Fri Oct 31 12:55:50
0.000178
1
Fri Oct 31 12:55:55
0.000174
1
Fri Oct 31 12:55:58
0.000176
1
Fri Oct 31 13:08:14
0.000198
1
IPV6 Unicast IS-IS level 1 SPF log:
Reason
Reconfig
Address change on gr-0/2/0.0
New adjacency h on gr-0/2/0.0
New LSP skag.00-00
Periodic SPF
Updated LSP h.00-00
Updated LSP skag.00-00
Periodic SPF
Start time
Fri Oct 31 12:41:18
0.000028
1
Fri Oct 31 12:41:18
0.000043
3
Fri Oct 31 12:41:18
0.000112
4
Fri Oct 31 12:41:23
0.000059
1
Fri Oct 31 12:41:25
0.000041
1
Fri Oct 31 12:41:28
0.000103
5
Fri Oct 31 12:41:59
0.000040
1
Fri Oct 31 12:42:30
0.000118
2
Fri Oct 31 12:56:08
0.000289
1
Fri Oct 31 13:11:07
0.000214
1
IPV6 Unicast IS-IS level 2 SPF log:
Reason
Reconfig
New adjacency scat on ge-1/1/0.0
Multi area attachment change
Periodic SPF
Periodic SPF
Start time
Fri Oct 31
Fri Oct 31
Fri Oct 31
Fri Oct 31
Fri Oct 31
Fri Oct 31
Fri Oct 31
Fri Oct 31
Fri Oct 31
Fri Oct 31
Fri Oct 31
...
Reason
Reconfig
New adjacency h on gr-0/2/0.0
New LSP skag.00-00
Updated LSP h.00-00
Updated LSP skag.00-00
Periodic SPF
12:41:18
12:41:18
12:41:18
12:41:23
12:41:25
12:41:59
12:42:30
12:55:50
12:55:55
12:55:58
13:09:46

0.000027
1
0.000039
2
0.000049
6
0.000025
1
0.000023
1
0.000087
3
0.000123
3
0.000121
1
0.000121
1
0.000121
1
0.000201
1
user@host> show isis spf results logical-system ls1

IS-IS level 1 SPF results:
761
logical-system
Node
scat.00
fix.02
fix.00
Metric
10
20
10
0
10
10
10
20
60
Interface
ge-1/1/0.0
10.9.1.0/30
Via
scat
SNPA
0:90:69:a6:48:9d
10.9.1.0/30
10.9.5.0/30
10.9.6.0/30
10.9.7.0/30
10.9.201.1/32
3 nodes
Node
Metric
skag.00
20
30
skag.02
20
h.00
10
20
20
60
fix.00
0
10
10
10
4 nodes
Interface
gr-0/2/0.0
10.9.7.0/30
gr-0/2/0.0
gr-0/2/0.0
10.9.6.0/30
10.9.7.0/30
10.9.201.1/32
Via
h
h
10.9.1.0/30
10.9.5.0/30
10.9.6.0/30
IPV6 Unicast IS-IS level 1 SPF results:

Node
Metric
Interface
Via
scat.00
10
ge-1/1/0.0
scat
ge-1/1/0.0
scat
20
8009:1::a09:1400/126
fix.02
10
fix.00
0
10
8009:1::a09:1400/126
10
8009:2::a09:1e00/126
20
8009:3::a09:3200/126
10
8009:4::a09:2800/126
3 nodes
IPV6 Unicast IS-IS level 2 SPF results:
Node
Metric
Interface
Via
skag.00
20
gr-0/2/0.0
h
gr-0/2/0.0
h
30
8009:3::a09:3200/126
skag.02
20
gr-0/2/0.0
h
gr-0/2/0.0
h
h.00
10
gr-0/2/0.0
h
gr-0/2/0.0
h
20
8009:3::a09:3200/126
20
8009:4::a09:2800/126
fix.00
0
10
8009:1::a09:1400/126
10
8009:2::a09:1e00/126
10
8009:4::a09:2800/126
4 nodes
Multicast IS-IS level 1 SPF results:
Node
Metric
Interface
scat.00
10
ge-1/1/0.0
fix.02
10
762
SNPA
Via
scat
SNPA
0:90:69:a6:48:9d
0:90:69:a6:48:9d
SNPA
SNPA
0:90:69:a6:48:9d
fix.00
3 nodes
Multicast IS-IS level 2 SPF results:

Node
Metric
Interface
skag.00
20
gr-0/2/0.0
skag.02
20
gr-0/2/0.0
h.00
10
gr-0/2/0.0
fix.00
0
4 nodes
...
show isis spf results

(CLNS)
Via
user@host> show isis spf results

Node
Metric
Interface
Via
skag.00 10
fe-0/0/1.0
toothache
fe-0/0/1.0
toothache
20
192.168.37.64/29
10
1921.6800.4001
20
1921.6800.4002
pro1-a.02
10
pro1-a.00
0
0
10.255.245.1/32
10
192.168.37.64/29
0
1921.6800.4211
3 nodes
Node
Metric
skag.00 10
pro1-a.02
pro1-a.00
20
20
20
10
0
0
10
SNPA
h
h
h
SNPA
0:12:0:34:0:56
0:12:0:34:0:56
Interface
Via
SNPA
fe-0/0/1.0
toothache
0:12:0:34:0:56
fe-0/0/1.0
toothache
0:12:0:34:0:56
10.255.245.1/32
192.168.37.64/29
47.0005.80ff.f800.0000.0109.0010/104
10.255.245.1/32
192.168.37.64/29
3 nodes
763
show isis statistics

Syntax
Syntax (EX Series

Switches and QFX
Series)
Release Information
Description
Options


Display statistics about IS-IS traffic.
noneDisplay IS-IS traffic statistics for all routing instances.
instance instance-name(Optional) Display statistics for the specified routing instance.

Required Privilege
Level
Related
Documentation
Output Fields
764
view
clear isis statistics
show isis statistics on page 766

Table 57 on page 765 describes the output fields for the show isis statistics command.
Table 57: show isis statistics Output Fields

Field Name
Field Description
PDU type
PDU type:
CSNPComplete sequence number PDUs contain a complete list of all link-state PDUs in the IS-IS
database. CSNPs are sent periodically on all links, and the receiving systems use the information
in the CSNP to update and synchronize their link-state PDU databases. The designated router
multicasts CSNPs on broadcast links in place of sending explicit acknowledgments for each
link-state PDU.
IIHIS-IS hello packets are broadcast to discover the identity of neighboring IS-IS systems and to
determine whether the neighbors are Level 1 or Level 2 intermediate systems.
LSPLink-state PDUs contain information about the state of adjacencies to neighboring IS-IS
systems. Link-state PDUs are flooded periodically throughout an area.
PSNPPartial sequence number PDUs are sent multicast by a receiver when it detects that it is
missing a link-state PDU (when its link-state PDU database is out of date). The receiver sends a
PSNP to the system that transmitted the CSNP, effectively requesting that the missing link-state
PDU be transmitted. That routing device, in turn, forwards the missing link-state PDU to the
requesting routing device.
UnknownThe PDU type is unknown.
Received
Number of PDUs received since IS-IS started or since the statistics were set to zero.
Processed
Number of PDUs received less the number dropped.
Drops
Number of PDUs dropped.
Sent
Number of PDUs transmitted since IS-IS started or since the statistics were set to zero.
Rexmit
Number of PDUs retransmitted since IS-IS started or since the statistics were set to zero.
Total packets
received/sent
Total number of PDUs received and transmitted since IS-IS started or since the statistics were set to
zero.
SNP queue length
Number of CSPN and PSNP packets currently waiting in the queue for processing. This value is almost
always 0.
LSP queue length
Number of link-state PDUs waiting in the queue for processing. This value is almost always 0.
SPF runs
Number of shortest-path-first (SPF) calculations that have been performed. If this number is
incrementing rapidly, it indicates that the network is unstable.
Fragments rebuilt
Number of link-state PDU fragments that the local system has computed.
LSP regenerations
Number of link-state PDUs that have been regenerated. A link-state PDU is regenerated when it is
nearing the end of its lifetime and it has not changed.
Purges initiated
Number of purges that the system initiated. A purge is initiated if the software decides that a link-state
PDU must be removed from the network.
765
Sample Output
user@host> show isis statistics

IS-IS statistics for merino:
PDU type
LSP
IIH
CSNP
PSNP
Unknown
Totals
Received
12227
113808
198868
6985
0
331888
Processed
12227
113808
198868
6979
0
331882
Drops
0
0
0
6
0
6
Sent
8184
115817
198934
8274
0
331209
Rexmit
683
0
0
0
0
683
Total packets received: 331888 Sent: 331892

SNP queue length:
LSP queue length:
SPF runs:
Fragments rebuilt:
LSP regenerations:
Purges initiated:
766
0 Drops:
0 Drops:
0
0
1014
1038
425
0
show oam ethernet connectivity-fault-management interfaces

Syntax
Release Information
Description
show oam ethernet connectivity-fault-management interfaces

<ethernet-interface-name>
<level md-level>

Support for ITU-T Y.1731 frame delay measurement added in Junos OS Release 9.5.
Support for ITU-T Y.1731 Ethernet synthetic frame loss measurement (ETH-SLM) added
in Junos OS Release 12.3 for ACX Series and MX Series routers.
On M7i and M10i routers with Enhanced CFEB (CFEB-E), and on M320, MX Series, ACX
Series, T320, and T640 routers, display IEEE 802.1ag Operation, Administration, and
Management (OAM) connectivity fault management (CFM) database information for
Ethernet interfaces.
In addition, for Ethernet interfaces on MX Series routers , also display any ITU-T Y.1731
frame delay measurement (ETH-DM) frame counts when detail or extensive mode is
specified.
For Ethernet interfaces on ACX Series and MX Series routers, display any ITU-T Y.1731
synthetic frame loss measurement (ETH-SLM) statistics and frame counts.
Options
brief | detail | extensive(Optional) Specified level of output.

ethernet-interface-name(Optional) CFM information only for CFM entities attached to
the specified Ethernet interface.

level md-level(Optional) CFM information for CFM identities enclosed within a
maintenance domain of the specified level.

Required Privilege
Level
Related
Documentation
view
clear oam ethernet connectivity-fault-management statistics
show oam ethernet connectivity-fault-management delay-statistics
show oam ethernet connectivity-fault-management interfaces on page 773

show oam ethernet connectivity-fault-management interfaces detail on page 773
show oam ethernet connectivity-fault-management interfaces detail (One-Way
ETH-DM) on page 774
show oam ethernet connectivity-fault-management interfaces detail(Connection
Protection TLV Configured) on page 774
show oam ethernet connectivity-fault-management interfacesextensive on page 776
show oam ethernet connectivity-fault-management interfaces level on page 776
767
show oam ethernet connectivity-fault-management interfaces (trunk ports) on page 776

Output Fields
Table 58 on page 768 lists the output fields for the show oam ethernet
connectivity-fault-management interfaces command. Output fields are listed in the
approximate order in which they appear.
Table 58: show oam ethernet connectivity-fault-management interfaces Output Fields

Field Name
Field Description
Level of Output
Interface
Interface identifier.
All levels
Interface status
Local interface status.
All levels
Link status
Local link status. Up, down, or oam-down.
All levels
Maintenance
domain name
Maintenance domain name.
detail extensive
Format
(Maintenance
domain)
Maintenance domain name format configured.
detail extensive
Level
Maintenance domain level configured.
All levels
Maintenance
association name
Maintenance association name.
detail extensive
Format
(Maintenance
association)
Maintenance association name format configured.
detail extensive
Continuity-check
status
Continuity-check status.
detail extensive
Interval
Continuity-check message interval.
detail extensive
Loss-threshold
Lost continuity-check message threshold.
detail extensive
Interface status
TLV
Status of the interface status TLV, if configured on the MEP interface: none, up,
down, testing, unknown, dormant, notPresent, lowerLayerDown
detail extensive
Port status TLV
Status of the port status TLV, if configured on the MEP interface: none, no, yes
detail extensive
Connection
Protection TLV
Status of the connection protection TLV if configured on the MEP interface: no,
detail extensive
yes
If yes, then the transmitted connection protection TLV is decoded and the
following three fields are displayed: Prefer me, Protection in use, FRR Flag
768

Fields (continued)
Field Name
Field Description
Level of Output
Prefer me
If set to yes, the path through which CCM was transmitted is preferred (unless
the path fails). It is used for signaling a manual-switch command to the remote
side.
detail extensive
Its value can be yes or no.

Protection in use
Used for protection decision coordination. Its value is set to yes if the endpoint
transmitting the CCM is currently transmitting the user traffic to protection path.
detail extensive

FRR Flag
LSR/LER forwarding the CCM Frame into a bypass tunnel is set.
detail extensive

MEP identifier
Maintenance association end point (MEP) identifier.
All levels
Neighbors
Number of MEP neighbors.
All levels
Direction
MEP direction configured.
detail extensive
MAC address
MAC address configured for the MEP.
detail extensive
MEP status
Indicates the status of the connectivity fault management (CFM) protocol

running on the MEP: Running, inactive, disabled, or unsupported.
detail extensive
Remote MEP not

receiving CCM
Whether the remote MEP is not receiving connectivity check messages (CCMs).
detail extensive
Erroneous CCM
received
Whether erroneous CCMs have been received.
detail extensive
Cross-connect CCM
received
Whether cross-connect CCMs have been received.
detail extensive
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.
detail extensive
CCMs sent
Number of CCMs transmitted.
detail extensive
CCMs received out

of sequence
Number of CCMs received out of sequence.
detail extensive
LBMs sent
Number of loopback request messages (LBMs) sent.
detail extensive
Valid in-order LBRs

received
Number of loopback response messages (LBRs) received that were valid

messages and in sequence.
detail extensive
769

Fields (continued)
Field Name
Field Description
Level of Output
Valid out-of-order
LBRs received
Number of LBRs received that were valid messages and not in sequence.
detail extensive
LBRs received with

corrupted data
Number of LBRs received that were corrupted.
detail extensive
LBRs sent
Number of LBRs transmitted.
detail extensive
LTMs sent
Linktrace messages (LTMs) transmitted.
detail extensive
LTMs received
Linktrace messages received.
detail extensive
LTRs sent
Linktrace responses (LTRs) transmitted.
detail extensive
LTRs received
Linktrace responses received.
detail extensive
Sequence number
of next LTM request
Sequence number of next LTM request to be transmitted.
detail extensive
1DMs sent
If the interface is attached to an initiator MEP for a one-way ETH-DM session:

Number of one-way delay measurement (1DM) PDU frames sent to the peer
MEP in this session.
detail extensive
For all other cases, this field displays 0.

Valid 1DMs received
If the interface is attached to a receiver MEP for a one-way ETH-DM session:

Number of valid 1DM frames received.
detail extensive

Invalid 1DMs
received

Number of invalid 1DM frames received.
detail extensive

Out of sync 1DMs
received

Number of out-of-sync one-way delay measurement request packets received.
detail extensive
DMMs sent
If the interface is attached to an initiator MEP for a two-way ETH-DM session:

Number of Delay Measurement Message (DMM) PDU frames sent to the peer
detail extensive

Valid DMMs
received

Number of valid two-way delay measurement request packets received.
detail extensive
Invalid DMMs
received

Number of invalid two-way delay measurement request packets received.
detail extensive
770

Fields (continued)
Field Name
Field Description
Level of Output
DMRs sent
If the interface is attached to a responder MEP for a two-way ETH-DM session:

Number of delay measurement reply (DMR) frames sent.
detail extensive

Valid DMRs
received

Number of valid DMRs received.
detail extensive

Invalid DMRs
received

Number of invalid DMRs received.
detail extensive

LMM sent
If the interface is attached to an initiator MEP for a ETH-LM session: Number

of loss measurement message (LMM) PDU frames sent to the peer MEP in this
session.
detail extensive
Valid LMM received

of valid loss measurement request packets received.
detail extensive
Invalid LMM
received

of invalid loss measurement request packets received.
detail extensive
LMR sent
If the interface is attached to a responder MEP for a ETH-LM session: Number

of loss measurement reply (LMR) frames sent.
detail extensive
Valid LMR received

of valid LMR frames received.
detail extensive
Invalid LMR
received

of invalid LMR frames received.
detail extensive
SLM sent
If the interface is attached to an initiator MEP for a ETH-SLM session: Number

of synthetic loss measurement (SLM) request packets transmitted from the
source MEP to the remote or destination MEP in this session.
detail extensive
Valid SLM received
If the interface is attached to a responder MEP for a ETH-SLM session: Number

of valid SLM PDUs transmitted from the source MEP to the remote or destination
MEP.
detail extensive
Invalid SLM
received

of invalid SLM PDUs transmitted from the source MEP to the remote or
destination MEP.
detail extensive
SLR sent

detail extensive of synthetic loss reply (SLR) frames sent.
detail extensive
771

Fields (continued)
Field Name
Field Description
Level of Output
Valid SLR received

of valid SLR PDUs that the source MEP received from the remote or destination
MEP.
detail extensive
Invalid SLR received

of invalid SLR PDUs that the source MEP received from the remote or destination
MEP.
detail extensive
Remote MEP count
Number of remote MEPs.
extensive
Identifier (remote
MEP identifier of the remote MEP.
extensive
MAC address of the remote MEP.
extensive
State of the remote MEP.
extensive
Interface of the remote MEP.
extensive
MEP)
MAC address
(remote MEP)
State (remote
MEP)
Interface (remote
MEP)
772
Sample Output
show oam ethernet
interfaces
user@host> show oam ethernet connectivity-fault-management interfaces

Interface
Link
Status
Level
MEP
Identifier
ge-1/1/0.0
Up
Active
0
2
ge-1/1/0.1
Up
Active
0
2
ge-1/1/0.10
Up
Active
0
2
ge-1/1/0.100
Up
Active
0
2
ge-1/1/0.101
Up
Active
0
2
ge-1/1/0.102
Up
Active
0
2
ge-1/1/0.103
Up
Active
0
2
ge-1/1/0.104
Up
Active
0
2
ge-1/1/0.105
Up
Active
0
2
ge-1/1/0.106
Up
Active
0
2
Neighbors
1
1
1
1
1
1
1
1
1
1
...
show oam ethernet

interfaces detail
user@host> show oam ethernet connectivity-fault-management interfaces detail

Interface name: ge-5/2/9.0, Interface status: Active, Link status: Up
Maintenance domain name: md0, Format: string, Level: 5
Maintenance association name: ma1, Format: string
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
LBMs sent
: 0
Valid in-order LBRs received
: 0
Valid out-of-order LBRs received
: 0
LBRs received with corrupted data
: 0
LBRs sent
: 0
LTMs sent
: 0
LTMs received
: 0
LTRs sent
: 0
LTRs received
: 0
Sequence number of next LTM request
: 0
1DMs sent
: 0
Valid 1DMs received
: 0
Invalid 1DMs received
: 0
DMMs sent
: 0
DMRs sent
: 0
Valid DMRs received
: 0
Invalid DMRs received
: 0
LMM sent
: 10
Valid LMM received
: 20
Invalid LMM received
: 0
LMR sent
: 20
Valid LMR received
: 10
Invalid LMR received
: 0
SLM sent
: 10
Valid SLM received
: 20
Invalid SLM received
: 0
773
SLR sent
Valid SLR received
Remote MEP count: 2
Identifier
MAC address
2001
00:90:69:0b:7f:71
4001
00:90:69:0b:09:c5
: 20
: 10
: 0
State
ok
ok
Interface
ge-5/2/9.0
ge-5/2/9.0
show oam ethernet

interfaces detail
(One-Way ETH-DM)
user@host show oam ethernet connectivity-fault-management interfaces detail

MEP identifier: 101, Direction: down, MAC address: 00:90:69:0a:48:57
MEP status: running
Defects:
: no
: no
: no
: no
Statistics:
CCMs sent
: 1590
: 0
LBMs sent
: 0
: 0
: 0
: 0
LBRs sent
: 0
LTMs sent
: 0
LTMs received
: 0
LTRs sent
: 0
LTRs received
: 0
: 0
1DMs sent
: 10
Valid 1DMs received
: 0
: 0
DMMs sent
: 0
DMRs sent
: 0
Valid DMRs received
: 0
: 0
Remote MEP count: 1
Identifier
MAC address
State
Interface
201
00:90:69:0a:43:94
ok
ge-0/2/5.0
show oam ethernet

interfaces detail
(Connection
Protection TLV
Configured)
user@hostshow oam ethernet connectivity-fault-management interfaces detail
774
Interface name: xe-6/2/0.0 , Interface status: Active, Link status: Up

Continuity-check status: enabled, Interval: 1s, Loss-threshold: 3 frames
Interface status TLV: none, Port status TLV: none
Connection Protection TLV: yes
Prefer me: no, Protection in use: no, FRR Flag: no
MEP identifier: 1, Direction: down, MAC address: 00:19:e2:b1:14:30
MEP status: running
Defects:
: no
: no
: no
: no
Some remote MEP's MAC in error state

Statistics:
CCMs sent
LBMs sent
LBRs sent
LTMs sent
LTMs received
LTRs sent
LTRs received
1DMs sent
Valid 1DMs received
Out of sync 1DMs received
DMMs sent
Valid DMMs received
Invalid DMMs received
DMRs sent
Valid DMRs received
LMMs sent
Valid LMMs received
Invalid LMMs received
LMRs sent
Valid LMRs received
Invalid LMRs received
Remote MEP count: 1
Identifier
MAC address
State
2
00:90:69:7f:e4:30
: no
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
225
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Interface
775
show oam ethernet

interfaces
extensive
user@host> show oam ethernet connectivity-fault-management interfaces extensive

Connection Protection TLV: no
MEP identifier: 1, Direction: down, MAC address: 00:90:69:0b:4b:94
MEP status: running
Defects:
: no
: yes
: no
: yes
Statistics:
CCMs sent
: 76
: 0
LBMs sent
: 0
: 0
: 0
: 0
LBRs sent
: 0
LTMs sent
: 0
LTMs received
: 0
LTRs sent
: 0
LTRs received
: 0
: 0
1DMs sent
: 0
Valid 1DMs received
: 0
: 0
DMMs sent
: 0
DMRs sent
: 0
Valid DMRs received
: 0
: 0
SLM sent
: 10
Valid SLM received
: 20
: 0
SLR sent
: 20
Valid SLR received
: 10
: 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

interfaces level
user@host> show oam ethernet connectivity-fault-management interfaces level 7

Interface
Link
Status
Level
MEP
Neighbors
Identifier
ge-3/0/0.0
Up
Active
7
201
0
xe-0/0/0.0
Up
Active
7
203
1
show oam ethernet

interfaces (trunk
ports)
user@host> show oam ethernet connectivity-fault-management interfaces
776
Interface
Link
Status
Level
ge-4/0/1.0, vlan 100

ge-10/3/10.4091, vlan 4091
ge-4/0/0.0
Up
Down
Up
Active
Inactive
Active
5
4
6
MEP
Identifier
100
400
200
Neighbors
0
0
0
user@host> show oam ethernet connectivity-fault-management interfaces ge-4/0/0.0

Interface
Link
Status
Level
ge-4/0/0.0
Up
Active
MEP
Identifier
200
Neighbors
0
user@host> show oam ethernet connectivity-fault-management interfaces ge-4/0/1.0 vlan 100

Interface
Link
Status
Level
ge-4/0/1.0, vlan 100
Up
Active
MEP
Identifier
100
Neighbors
0
user@host> show oam ethernet connectivity-fault-management interfaces ge-10/3/10.4091

vlan 4091
Interface
Link
Status
Level
ge-10/3/10.4091, vlan 4091
Down
Inactive
MEP
Identifier
400
Neighbors
0
777

Syntax
Release Information
Description

<mep mep-id>
<count entry-count>

Support for ITU-T Y.1731 Ethernet synthetic frame loss measurement (ETH-SLM) added
in Junos OS Release 12.3 for ACX Series and MX Series routers.
On MX Series and ACX Series routers and EX Series switches with Ethernet interfaces,
display ETH-DM statistics and ETH-DM frame counts.
Options

mep mep-id(Optional) Numeric identifier of the local MEP. The range of values is 1
through 8192. On EX Series switches, the range of values is 1 through 8191.

remote-mep remote-mep-id(Optional) Numeric identifier of the remote MEP. The range
of values is 1 through 8192. On EX Series switches, the range of values is 1 through

8191.
count entry-count(Optional) Number of entries to display from the statistics table. The
range of values is 1 through 100. The default value is 100 entries.

Required Privilege
Level
Related
Documentation
778
view
show oam ethernet connectivity-fault-management mep-statistics (CIR counters

only) on page 781
show oam ethernet connectivity-fault-management mep-statistics (CIR and EIR
counters enabled) on page 782
show oam ethernet connectivity-fault-management mep-statistics remote-mep (CIR
counters only) on page 784
show oam ethernet connectivity-fault-management mep-statistics remote-mep (CIR

and EIR counters enabled) on page 786
remote-mep on page 789
Output Fields
connectivity-fault-management mep-statistics command. Output fields are listed in the
Table 59: show oam ethernet connectivity-fault-management delay-statistics and

mep-statistics Output Fields
Output Field Name
Field Description
MEP identifier
Maintenance association end point (MEP) numeric identifier.
MAC address
Unicast MAC address configured for the MEP.
Remote MEP count
Number of remote MEPs (unless you specify the remote-mep option).
Remote MEP identifier
Numeric identifier of the remote MEP.
Remote MAC address
Unicast MAC address of the remote MEP.
Index
Index number that corresponds to the ETH-DM entry in the CFM database.
One-way delay (usec)
For a one-way ETH-DM session, the frame delay time, in microseconds, measured
at the receiver MEP.
For a detailed description of one-way Ethernet frame delay measurement, see
the ITU-T Y.1731 Ethernet Service OAM topics in the Junos OS Network Interfaces.
Two-way delay (usec)
For a two-way ETH-DM session, the frame delay time, in microseconds, measured
at the initiator MEP.
For a detailed description of two-way Ethernet frame delay measurement, see
the ITU-T Y.1731 Ethernet Service OAM topics in the Junos OS Network Interfaces.
Average one-way delay
Average one-way frame delay for the statistics displayed.
Average one-way delay variation
Average one-way frame jitter for the statistics displayed.
Best-case one-way delay
Lowest one-way frame delay for the statistics displayed.
Worst-case one-way delay
Highest one-way frame delay for the statistics displayed.
Average two-way delay
Average two-way frame delay for the statistics displayed.
Average two-way delay variation
Average two-way frame jitter for the statistics displayed.
Best-case two-way delay
Lowest two-way frame delay for the statistics displayed.
779
Table 59: show oam ethernet connectivity-fault-management delay-statistics and

mep-statistics Output Fields (continued)
Output Field Name
Field Description
Worst-case two-way delay
Highest two-way frame delay calculated in this session.
SLM packets sent
Total number of synthetic loss message (SLM) PDU frames sent from the source
MEP to the remote MEP during this ETH-SLM session.
SLM packets received
Total number of synthetic loss message (SLM) PDU frames that the remote
MEP received from the source MEP during this ETH-SLM session.
SLR packets sent
Total number of synthetic loss reply (SLR) PDU frames that the remote MEP
sent to the source MEP during this measurement session.
Total number of synthetic loss reply (SLR) PDU frames that the source MEP
received from the remote MEP during this measurement session.
Local TXFC1 value
Number of synthetic frames transmitted to the peer MEP for a test ID. A test ID
is used to distinguish each synthetic loss measurement because multiple
measurements can be simultaneously activated also on a given CoS and MEP
pair. It must be unique at least within the context of any SLM for the MEG and
initiating MEP.
Local RXFC1 value
Number of synthetic frames received from the peer MEP for a test ID. The MEP
generates a unique Test ID for the session, adds the source MEP ID, and initializes
the local counters for the session before SLM initiation. For each SLM PDU
transmitted for the session (test ID), the local counter TXFC1 is sent in the packet.
Last Received SLR frame TXFCb(t
780
Sample Output
show oam ethernet
mep-statistics (CIR
counters only)

maintenance-domain md1 maintenance-association ma-1 local-mep 3 remote-mep 103 count 3
MEP identifier: 100, MAC address: 00:05:85:73:7b:39
Remote MEP count
: 1
CCMs sent
: 6550
: 0
LBMs sent
: 0
: 0
: 0
: 0
LBRs sent
: 0
LTMs sent
: 0
LTMs received
: 0
LTRs sent
: 0
LTRs received
: 0
Sequence number of next LTM request : 0
1DMs sent
: 5
Valid 1DMs received
: 0
: 0
DMMs sent
: 5
DMRs sent
: 0
Valid DMRs received
: 5
: 0
LMM sent
: 5
Valid LMM received
: 5
: 0
LMR sent
: 0
Valid LMR received
: 5
: 0
: 101
Remote MAC address
: 00:05:85:73:39:4a
Delay measurement statistics:
Index
One-way delay
(usec)
1
259
2
273
3
287
4
299
5
313
Best case one-way delay
Best case two-way delay
Worst case two-way delay
Loss measurement statistics:
Index
Near-end
Far-end
Frame loss
Frame loss
(CIR)
(CIR)
1
9
9
2
3
5
3
7
5
4
9
6
5
3
6
Two-way delay
(usec)
519
550
571
610
650
:
:
:
:
:
:
:
286 usec
62 usec
259 usec
580 usec
26 usec
519 usec
650 usec
Near-end
Frame loss
(EIR)
Far-end
Frame loss
(EIR)
781
Average near-end loss (CIR)

Average near-end loss ratio (CIR)
Average far-end loss (CIR)
Average far-end loss ratio (CIR)
Near-end best case loss (CIR)
Near-end best case loss ratio (CIR)
Near-end worst case loss (CIR)
Near-end worst case loss ratio (CIR)
Far-end best case loss (CIR)
Far-end best case loss ratio (CIR)
Far-end worst case loss (CIR)
Far-end worst case loss ratio (CIR)
show oam ethernet

mep-statistics (CIR
782
:
:
:
:
:
:
:
:
:
:
:
:
6.2
6.2%
6.2
6.2%
3
3%
9
9%
5
5%
9
9%

Remote MEP count
: 1
CCMs sent
: 6550
and EIR counters

enabled)

LBMs sent
LBRs sent
LTMs sent
LTMs received
LTRs sent
LTRs received
1DMs sent
Valid 1DMs received
DMMs sent
DMRs sent
Valid DMRs received
LMM sent
alid LMM received
LMR sent
Valid LMR received
Remote MAC address
Index
One-way delay
(usec)
1
259
2
273
3
287
4
299
5
313
0
0
0
0
0
0
0
0
0
0
0
5
0
0
5
0
5
0
5
5
0
0
5
0
101
00:05:85:73:39:4a
Two-way delay
(usec)
519
550
571
610
650

Index
Near-end
Far-end
Frame loss
Frame loss
(CIR)
(CIR)
1
9
9
2
3
5
3
7
5
4
9
6
5
3
6
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
286 usec
62 usec
259 usec
580 usec
26 usec
519 usec
650 usec
Near-end
Frame loss
(EIR)
2
4
0
8
6
:
:
:
:
:
:
:
Far-end
Frame loss
(EIR)
4
6
2
2
4
6.2
6.2%
6.2
6.2%
3
3%
9
783

Average near-end loss (EIR)
Average near-end loss ratio (EIR)
Average far-end loss (EIR)
Average far-end loss ratio (EIR)
Near-end best case loss (EIR)
Near-end best case loss ratio (EIR)
Near-end worst case loss (EIR)
Near-end worst case loss ratio (EIR)
Far-end best case loss (EIR)
Far-end best case loss ratio (EIR)
Far-end worst case loss (EIR)
Far-end worst case loss ratio (EIR)
show oam ethernet

mep-statistics
784
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
9%
5
5%
9
9%
4
4%
3.4
3.4%
0
0%
8
8%
2
2%
6
6%

remote-mep 101
CCMs sent
: 7762
remote-mep (CIR
counters only)

LBMs sent
LBRs sent
LTMs sent
LTMs received
LTRs sent
LTRs received
1DMs sent
Valid 1DMs received
DMMs sent
DMRs sent
Valid DMRs received
LMM sent
Valid LMM received
LMR sent
Valid LMR received
Remote MAC address
Index
One-way delay
(usec)
1
259
2
273
3
287
4
299
5
313
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
0
0
0
0
0
0
0
0
0
0
0
5
0
0
5
0
5
0
5
5
0
0
5
0
101
00:05:85:73:39:4a
Two-way delay
(usec)
519
550
571
610
650
:
:
:
:
:
:
:
286 usec
62 usec
259 usec
580 usec
26 usec
519 usec
650 usec

Index
Near-end
Far-end
Near-end
Frame loss
Frame loss
Frame loss
(CIR)
(CIR)
(EIR)
1
9
9
2
3
5
3
7
5
4
9
6
5
3
6
: 6.2
: 6.2%
: 6.2
: 6.2%
: 3
: 3%
: 9
: 9%
Far-end
Frame loss
(EIR)
785

show oam ethernet

mep-statistics
786
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
5
5%
9
9%
4
4%
3.4
3.4%
0
0%
8
8%
2
2%
6
6%

remote-mep 101
CCMs sent
:7762
remote-mep (CIR and

EIR counters enabled)

LBMs sent
LBRs sent
LTMs sent
LTMs received
LTRs sent
LTRs received
1DMs sent
Valid 1DMs received
DMMs sent
DMRs sent
Valid DMRs received
LMM sent
Valid LMM received
LMR sent
Valid LMR received
Remote MAC address
Index
One-way delay
(usec)
1
259
2
273
3
287
4
299
5
313
0
0
0
0
0
0
0
0
0
0
0
5
0
0
5
0
5
0
5
5
0
0
5
0
101
00:05:85:73:39:4a
Two-way delay
(usec)
519
550
571
610
650

Index
Near-end
Far-end
Frame loss
Frame loss
(CIR)
(CIR)
1
10
8
2
12
7
3
7
5
4
9
6
5
3
6
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
286 usec
62 usec
259 usec
580 usec
26 usec
519 usec
650 usec
Near-end
Frame loss
(EIR)
5
6
0
8
6
:
:
:
:
:
:
:
Far-end
Frame loss
(EIR)
12
16
2
2
4
6.2
6.2%
6.2
6.2%
3
3%
9
787

show oam ethernet

mep-statistics
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
9%
5
5%
9
9%
4
4%
3.4
3.4%
0
0%
8
8%
2
2%
6
6%

maintenance-domain md1 maintenance-association ma-1
Remote MEP count: 1
CCMs sent
: 6550
: 0
LBMs sent
: 0
: 0
: 0
: 0
LBRs sent
: 0
LTMs sent
: 0
LTMs received
: 0
LTRs sent
: 0
LTRs received
: 0
: 0
1DMs sent
: 5
Valid 1DMs received
: 0
: 0
DMMs sent
: 5
DMRs sent
: 0
Valid DMRs received
: 5
: 0
SLM sent
: 10
Valid SLM received
: 20
: 0
SLR sent
: 20
Valid SLR received
: 10
: 0
Remote MEP identifier: 101
Remote MAC address: 00:05:85:73:39:4a
Index One-way delay Two-way delay
(usec)
(usec)
1
259
519
2
273
550
3
287
571
4
299
610
5
313
650
: 286 usec
Average one-way delay variation: 62 usec
: 259 usec
788
Worst case one-way delay

: 313 usec
: 580 usec
Average two-way delay variation: 26 usec
: 519 usec
: 650 usec
SLM packets sent
SLR packets sent
Local TXFC1 value
Local RXFC1 value
Last Received SLR frame TXFCftc
Last Received SLR frame TXFCbtc
SLM Frame Loss:
show oam ethernet

mep-statistics
remote-mep
:
:
:
:
100
0
100
0
:
:
:
:
100
100
100
100
: 0 (0.00 %)
: 0 (0.00 %)

CCMs sent
: 7762
: 0
LBMs sent
: 0
: 0
: 0
: 0
LBRs sent
: 0
LTMs sent
: 0
LTMs received
: 0
LTRs sent
: 0
LTRs received
: 0
: 0
1DMs sent
: 5
Valid 1DMs received
: 0
: 0
DMMs sent
: 5
DMRs sent
: 0
Valid DMRs received
: 5
: 0
SLM sent
: 10
Valid SLM received
: 20
: 0
SLR sent
: 20
Valid SLR received
: 10
: 0
Index One-way delay Two-way delay
(usec)
(usec)
1
259
519
2
273
550
3
287
571
4
299
610
5
313
650
: 286 usec
Average one-way delay variation: 62 usec
: 259 usec
789
Worst case one-way delay

: 313 usec
: 580 usec
Average two-way delay variation: 26 usec
: 519 usec
: 650 usec
SLM packets sent
SLR packets sent
Local TXFC1 value
Local RXFC1 value
SLM Frame Loss:
790
:
:
:
:
100
0
100
0
:
:
:
:
100
100
100
100
: 0 (0.00 %)
: 0 (0.00 %)

Syntax
Release Information
Description

maintenance-domain domain-name

Support for ITU-T Y.1731 frame delay measurement added in Junos OS Release 9.5.
Support for ITU-T Y.1731 synthetic frame loss measurement added in Junos OS Release
12.3 for ACX Series and MX Series routers.
On M7i and M10i routers with Enhanced CFEB (CFEB-E), and on M320, M120, MX Series,
ACX Series, T320, and T640 routers, display IEEE 802.1ag Operation, Administration,
and Management (OAM) connectivity fault management (CFM) database information
for CFM maintenance association end points (MEPs) in a CFM session.
In addition, on M120, M320, and MX series routers, also display port status TLV, interface
status TLV, and action profile information.
In addition, for Ethernet interfaces on MX Series routers , also display any ITU-T Y.1731
frame delay measurement (ETH-DM) frame counts.
Options
maintenance-association ma-nameName of the maintenance association.

maintenance-domain domain-nameName of the maintenance domain.
local-mep-id(Optional) Numeric identifier of local MEP.
remote-mep-id(Optional) Numeric identifier of the remote MEP.
Required Privilege
Level
Related
Documentation
view

show oam ethernet connectivity-fault-management mep-database (One-Way
ETH-DM) on page 797
show oam ethernet connectivity-fault-management mep-database local-mep
remote-mep on page 798
791
show oam ethernet connectivity-fault-management mep-database remote-mep

(Action Profile Event) on page 798
show oam ethernet connectivity-fault-management mep-database (Connection
Protection TLV Configured) on page 798
show oam ethernet connectivity-fault-management mep-database (enhanced
continuity measurement) on page 800
Output Fields
connectivity-fault-management mep-database command. Output fields are listed in the
Table 60: show oam ethernet connectivity-fault-management mep-database Output Fields

Field Name
Field Description
Maintenance domain
name
Maintenance domain name.
Format (Maintenance
domain)
Maintenance domain name format configured.
Level
Maintenance domain level configured.
Maintenance
association name
Maintenance association name.
Format (Maintenance
association)
Maintenance association name format configured.
Continuity-check status
Continuity-check status.
Interval
Continuity-check message interval.
Loss-threshold
Lost continuity-check message threshold.
Connection Protection
TLV
Status of the connection protection TLV, if configured on the MEP interface: no, yes
If yes, then the transmitted connection protection TLV is decoded and the following three fields are
displayed: Prefer me, Protection in use, FRR Flag
Prefer me
If set to yes, the path through which CCM was transmitted is preferred (unless the path fails). It is
used for signaling a manual-switch command to remote side.
Protection in use
Used for protection decision coordination. Its value is set to yes if the endpoint transmitting the CCM
is currently transmitting the user traffic to protection path.
FRR Flag
LSR/LER forwarding the CCM Frame into a bypass tunnel is set.

792
Table 60: show oam ethernet connectivity-fault-management mep-database Output

Fields (continued)
Field Name
Field Description
MEP identifier
Maintenance association end point (MEP) identifier.
Direction
MEP direction configured.
MAC address
MAC address configured for the MEP.
Auto-discovery
Whether automatic discovery is enabled or disabled.
Priority
Priority used for CCMs and linktrace messages transmitted by the MEP.
Interface name
Interface identifier.
Interface status
Local interface status.
Link status
Local link status.
Remote MEP not

receiving CCM
Whether the remote MEP is not receiving CCMs.
Whether erroneous CCMs have been received.
Cross-connect CCM
received
Whether cross-connect CCMs have been received.
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.
CCMs sent
Number of CCMs transmitted.
CCMs received out of

sequence
Number of CCMs received out of sequence.
LBMs sent
Number of loopback messages (LBMs) sent.
Valid in-order LBRs

received
Number of loopback response messages (LBRs) received that were valid messages and in sequence.
1DMs sent
If the MEP is an initiator for a one-way ETH-DM session: Number of one-way delay measurement
(1DM) PDU frames sent to the peer MEP in this session.
Valid 1DMs received
If the MEP is a receiver for a one-way ETH-DM session: Number of valid 1DM frames received.
793

Fields (continued)
Field Name
Field Description
If the MEP is a receiver for a one-way ETH-DM session: Number of invalid 1DM frames received.
Out of sync 1DMs

received
If the MEP is a receiver for a one-way ETH-DM session: Number of out-of-sync one-way delay
measurement request packets received.
DMMs sent
If the MEP is an initiator for a two-way ETH-DM session: Number of Delay Measurement Message
(DMM) PDU frames sent to the peer MEP in this session.
Valid DMMs received
If the MEP is an initiator for a two-way ETH-DM session: Number of valid two-way delay measurement
packets received.
If the MEP is an initiator for a two-way ETH-DM session: Number of invalid two-way delay measurement
packets received.
DMRs sent
If the MEP is a responder for a ETH-DM session: Number of Delay Measurement Reply (DMR) frames
sent.
Valid DMRs received
If the MEP is an initiator for a two-way ETH-DM session: Number of valid DMRs received.
If the MEP is an initiator for a two-way ETH-DM session: Number of invalid DMRs received.
Valid out-of-order LBRs

received
Number of LBRs received that were valid messages and not in sequence.
LBRs received with

corrupted data
Number of LBRs received that were corrupted.
LBRs sent
Number of LBRs transmitted.
LTMs sent
Linktrace messages (LTMs) transmitted.
LTMs received
Linktrace messages received.
LTRs sent
Linktrace responses (LTRs) transmitted.
LTRs received
Linktrace responses received.
Sequence number of
next LTM request
Sequence number of the next linktrace message request to be transmitted.
794

Fields (continued)
Field Name
Field Description
LMM sent
If the interface is attached to an initiator MEP for a ETH-LM session: Number of loss measurement
message (LMM) PDU frames sent to the peer MEP in this session.
Valid LMM received
If the interface is attached to an initiator MEP for a ETH-LM session: Number of valid loss measurement
request packets received.
If the interface is attached to an initiator MEP for a ETH LM session: Number of invalid loss
measurement request packets received.
LMR sent
If the interface is attached to a responder MEP for a ETH-LM session: Number of loss measurement
reply (LMR) frames sent.
Valid LMR received
If the interface is attached to an initiator MEP for a ETH LM session: Number of valid LMR frames
received.
If the interface is attached to an initiator MEP for a ETH-LM session: Number of invalid LMR frames
received.
SLM sent
If the interface is attached to an initiator MEP for a ETH-SLM session: Number of synthetic loss
measurement (SLM) request packets transmitted from the source MEP to the remote or destination
Valid SLM received
If the interface is attached to a responder MEP for a ETH-SLM session: Number of valid SLM PDUs
transmitted from the source MEP to the remote or destination MEP.
If the interface is attached to a responder MEP for a ETH-SLM session: Number of invalid SLM PDUs
transmitted from the source MEP to the remote or destination MEP.
SLR sent
If the interface is attached to a responder MEP for a ETH-SLM session: Number detail extensive of
synthetic loss reply (SLR) frames sent.
Valid SLR received
If the interface is attached to an initiator MEP for a ETH-SLM session: Number of valid SLR PDUs that
the source MEP received from the remote or destination MEP.
If the interface is attached to an initiator MEP for a ETH-SLM session: Number of invalid SLR PDUs
that the source MEP received from the remote or destination MEP.
MEP identifier of the remote MEP.
State (remote MEP)
State of the remote MEP: idle, start, ok, or failed.
MAC address
MAC address of the remote MEP.
Type
Whether the remote MEP MAC address was learned using automatic discovery or configured.
Interface
Interface of the remote MEP. A seven-digit number is appended if CFM is configured to run on a routing
instance of type VPLS.
795

Fields (continued)
Field Name
Field Description
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
indication
Whether the remote defect indication (RDI) bit is set in messages that have been received or
transmitted.
Port status TLV
In the Maintenance domain section, displays the last transmitted port status TLV value.
In the Remote MEP section, displays the last value of port status TLV received from the remote
MEP.
In the Action profile section, displays, the last occurred event port-status-tlv blocked event. This
event occurred due to the reception of blocked value in the port status TLV from remote MEP.
Interface status TLV
In the Maintenance domain section, displays the last transmitted interface status TLV value.
In the Remote MEP section, displays the last value of interface status TLV received from the remote
MEP.
In the Action profile section, if displays, the last occurred event interface-status-tlv event ( either
lower-layer-down or down). This event occurred due to the reception of either lower or down value
in the interface status TLV from remote MEP.
Action profile
Name of the action profile occurrence associated with a remote MEP.
Last event
When an action profile occurs, displays the last event that triggered it.
Last event cleared
When all the configured and occurred events (under action profile) are cleared, then the action taken
gets reverted (such as down interface is made up) and the corresponding time is noted and displayed.
Action
Action taken and the corresponding time of the action occurrence.
796
Sample Output
show oam ethernet
mep-database

maintenance-domain vpls-vlan2000 maintenance-association vpls-vlan200
Maintenance domain name: vpls-vlan2000, Format: string, Level: 5
Maintenance association name: vpls-vlan200, Format: string
MEP identifier: 200, Direction: up, MAC address: 00:19:e2:b0:74:01
Auto-discovery: enabled, Priority: 0
Connection Protection TLV: no Interface name: ge-0/0/1.0, Interface status:
Active, Link status: Up
Defects:
: no
: no
: no
: no
Statistics:
CCMs sent
: 1476
: 0
LBMs sent
: 85
: 78
: 0
: 0
LBRs sent
: 0
LTMs sent
: 1
LTMs received
: 0
LTRs sent
: 0
LTRs received
: 1
: 1
1DMs sent
: 0
Valid 1DMs received
: 0
: 0
DMMs sent
: 0
DMRs sent
: 0
Valid DMRs received
: 0
: 0
Remote MEP count: 1
Identifier
MAC address
State
Interface
100
00:19:e2:b2:81:4b
ok vt-0/1/10.1049088
show oam ethernet

mep-database
(One-Way ETH-DM)

maintenance-domain md6 maintenance-domain ma6
MEP identifier: 101, Direction: down, MAC address: 00:90:69:0a:48:57
Defects:
: no
: no
: no
: no
Statistics:
CCMs sent
: 1590
: 0
LBMs sent
: 0
: 0
797

LBRs sent
LTMs sent
LTMs received
LTRs sent
LTRs received
1DMs sent
Valid 1DMs received
DMMs sent
DMRs sent
Valid DMRs received
Remote MEP count: 1
Identifier
MAC address
State
201
00:90:69:0a:43:94
ok
show oam ethernet

mep-database
local-mep remote-mep
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
0
0
0
0
0
0
0
0
10
0
0
0
0
0
0
Interface
ge-0/2/5.0

maintenance-domain vpls-vlan2000 maintenance-association vpls-vlan200 local-mep 200
remote-mep 100
Maintenance domain name: vpls-vlan2000, Format: string, Level: 5
Maintenance association name: vpls-vlan200, Format: string
MEP identifier: 200, Direction: up, MAC address: 00:19:e2:b0:74:01
Remote MEP identifier: 100, State: ok
MAC address: 00:19:e2:b2:81:4b, Type: Learned
Interface: vt-0/1/10.1049088
Last flapped: Never
Remote defect indication: false
Port status TLV: none
Interface status TLV: none
show oam ethernet

mep-database
remote-mep
(Action Profile Event)

MEP identifier: 100, Direction: down, MAC address: 00:05:85:73:e8:ad
MAC address: 00:05:85:73:96:1f, Type: Configured
Interface: ge-1/0/8.0
Last flapped: Never
Interface status TLV: lower-layer-down
Action profile: juniper
Last event: Interface-status-tlv lower-layer-down
Action: Interface-down, Time: 2009-03-27 14:25:10 PDT (00:00:02 ago)
user@host>show oam ethernet connectivity-fault-management mep-database
798
show oam ethernet

mep-database
(Connection
Protection TLV
Configured)
If connection-protection is not enabled on down MEPs, but connection-protection TLV

is used, MX always sets the protection-in-use flag in connection-protection tlv, while
CCMs are sent out. During reversion, this is an indicator to the receiver that protect-path
is in use, otherwise the peer (receiver) assumes working is active and reversion does not
work as expected. Setting this bit does not affect protection-switching/traffic-loss.
MEP identifier: 1, Direction: down, MAC address: 00:19:e2:b1:14:30
Connection Protection TLV: yes
Prefer me: no, Protection in use: no, FRR Flag: no
Interface name: xe-6/2/0.0, Interface status: Active, Link status: Up
Defects:
: no
: no
: no
: no
Some remote MEP's MAC in error state
: no
Statistics:
CCMs sent
: 251
: 0
LBMs sent
: 0
: 0
: 0
: 0
LBRs sent
: 0
LTMs sent
: 0
LTMs received
: 0
LTRs sent
: 0
LTRs received
: 0
: 0
1DMs sent
: 0
Valid 1DMs received
: 0
: 0
Out of sync 1DMs received
: 0
DMMs sent
: 0
Valid DMMs received
: 0
: 0
DMRs sent
: 0
Valid DMRs received
: 0
: 0
LMMs sent
: 0
Valid LMMs received
: 0
Invalid LMMs received
: 0
LMRs sent
: 0
Valid LMRs received
: 0
Invalid LMRs received
: 0
Remote MEP count: 1
Identifier
MAC address
State
Interface
2
00:90:69:7f:e4:30
show oam ethernet

mep-database

MEP identifier: 1, Direction: down, MAC address: 00:14:f6:b6:01:fe
799

Defects:
Statistics:
CCMs sent
LBMs sent
LBRs sent
LTMs sent
LTMs received
LTRs sent
LTRs received
1DMs sent
Valid 1DMs received
DMMs sent
DMRs sent
Valid DMRs received
LMM sent
Valid LMM received
LMR sent
Valid LMR received
SLM sent
Valid SLM received
SLR sent
Valid SLR received
Remote MEP count
Identifier
2
show oam ethernet

mep-database
800
MAC address
00:12:1e:fb:ea:7d
:
:
:
:
no
no
no
no
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
328703
0
85
78
0
0
0
0
0
0
0
0
10
10
0
20
0
10
0
10
20
0
20
10
0
:
:
:
:
:
:
10
20
0
20
10
0
: 1
State
ok
Interface
ge-1/0/0.0

maintenance-domain md5 maintenance-association ma5 local-mep 2001 remote-mep 1001
(enhanced continuity
measurement)
MEP identifier: 2001, Direction: down, MAC address: 00:19:e2:b2:81:4a

Interface status TLV: up, Port status TLV: up
MAC address : 00:19:e2:b0:74:00, Type: Learned
Interface
: ge-2/0/0.0
Last flapped : Never
+ Continuity : 91%, Admin-enable duration: 2100sec, Oper-down duration: 100sec
Interface status TLV: none
801
show oam ethernet connectivity-fault-management sla-iterator-statistics

Syntax
Release Information
Description
Options
show oam ethernet connectivity-fault-management sla-iterator-statistics

sla-iterator sla-iterator

Display the Ethernet Operation, Administration, and Maintenance (OAM) service-level
agreement (SLA) iterator statistics.
maintenance-domain md-nameName of an existing connectivity fault management
(CFM) maintenance domain.

sla-iterator sla-iterator Name of the iterator profile.
local-mep local-mep-id(Optional) Numeric identifier of the local MEP. The range of
values is 1 through 8191.

of values is 1 through 8192.

Required Privilege
Level
Related
Documentation
view
Configuring an Iterator Profile on a Switch (CLI Procedure)
clear oam ethernet connectivity-fault-management sla-iterator-statistics on page 326
show oam ethernet connectivity-fault-management sla-iterator-statistics on page 805

show oam ethernet connectivity-fault-management sla-iterator-statistics (MX Series
and ACX Series Routers with Ethernet synthetic loss measurement
configured) on page 805
Output Fields
connectivity-fault-management sla-iterator-statistics command. Output fields are listed
in the approximate order in which they appear.
Table 61: show oam ethernet connectivity-fault-management sla-iterator-statistics Output

Fields
Output Field Name
Maintenance domain
Name of the maintenance domain.
802

Fields (continued)
Output Field Name
Level
Level of the maintenance domain level configured.
Maintenance association
Name of the maintenance association.
Local MEP id
Numeric identifier of the local MEP.
Remote MEP id
Remote MAC address
Iterator name
Name of iterator.
Iterator Id
Numeric identifier of the iterator.
Iterator cycle time
Number of cycles (in milliseconds) taken between back-to-back transmission of SLA frames for
this connection
Iteration period
Maximum number of cycles per iteration
Iterator status
Current status of iterator whether running or stopped.
Infinite iterations
Status of iteration as infinite or finite.
Counter reset time
Date and time when the counter was reset.
Reset reason
Reason to reset counter.
Delay weight
Calculation weight of delay.
Delay variation weight
Calculation weight of delay variation.
DMM sent
Delay measurement message (DMM) PDU frames sent to the peer MEP in this session.
DMM skipped for threshold

hit
Number of DMM frames sent to the peer MEP in this session skipped during threshold hit.
DMM skipped for threshold

hit window
Number of DMM frames sent to the peer MEP in this session skipped during the last threshold hit
window.
DMR received
Number of delay measurement reply (DMR) frames received.
DMR out of sequence
Total number of DMR out of sequence packets received.
DMR received with invalid

time stamps
Total number of DMR frames received with invalid timestamps.
803

Fields (continued)
Output Field Name
Average two-way frame delay for the statistics displayed.

variation
Average two-way frame jitter for the statistics displayed.
Average one-way forward

delay variation
Average one-way forward delay variation for the statistics displayed in microseconds.
Average one-way backward

delay variation
Average one-way backward delay variation for the statistics displayed in microseconds.
Weighted average two-way

delay
Weighted average two-way delay for the statistics displayed in microseconds.
Weighted average two-way

delay variation
Weighted average two-way delay variation for the statistics displayed in microseconds.
Weighted average one-way

forward delay variation
Weighted average one-way forward delay variation for the statistics displayed in microseconds.
Weighted average one-way

backward delay variation
Weighted average one-way backward delay variation for the statistics displayed in microseconds.
SLM packets sent
Total number of synthetic loss message (SLM) PDU frames sent from the source MEP to the
remote MEP during this ETH-SLM session.
Total number of synthetic loss message (SLM) PDU frames that the remote MEP received from
the source MEP during this ETH-SLM session.
SLR packets sent
Total number of synthetic loss reply (SLR) PDU frames that the remote MEP sent to the source
MEP during this measurement session.
Total number of synthetic loss reply (SLR) PDU frames that the source MEP received from the
remote MEP during this measurement session.
Local TXFC1 value
Number of synthetic frames transmitted to the peer MEP for a test ID. A test ID is used to distinguish
each synthetic loss measurement because multiple measurements can be simultaneously activated
also on a given CoS and MEP pair. It must be unique at least within the context of any SLM for the
MEG and initiating MEP.
Local RXFC1 value
Number of synthetic frames received from the peer MEP for a test ID. The MEP generates a unique
Test ID for the session, adds the source MEP ID, and initializes the local counters for the session
before SLM initiation. For each SLM PDU transmitted for the session (test ID), the local counter
TXFC1 is sent in the packet.

TXFCf(tc)
804

Fields (continued)
Output Field Name

TXFCb(t
Sample Output
show oam ethernet
connectivity-fault
-management
sla-iterator-statistics
user@switch> show oam ethernet connectivity-fault-management sla-iterator-statistics

remote-mep 2
Iterator statistics:
Maintenance domain: md6, Level: 6
Maintenance association: ma6, Local MEP id: 1000
Remote MEP id: 103, Remote MAC address: 00:90:69:0a:43:92
Iterator name: i1, Iterator Id: 1
Iterator cycle time: 10ms, Iteration period: 1 cycles
Iterator status: running, Infinite iterations: true
Counter reset time: 2010-03-19 20:42:39 PDT (2d 18:24 ago)
Reset reason: Adjacency flap
Iterator delay measurement statistics:
Delay weight: 1, Delay variation weight: 1
DMM sent
DMM skipped for threshold hit
DMM skipped for threshold hit window
DMR received
DMR out of sequence
DMR received with invalid time stamps
Average one-way forward delay variation
Average one-way backward delay variation
Weighted average two-way delay
Weighted average two-way delay variation
Weighted average one-way forward delay variation
Weighted average one-way backward delay variation
:
:
:
:
:
:
:
:
:
:
:
:
:
:
23898520
11000
0
23851165
1142
36540
129 usec
15 usec
22 usec
22 usec
134 usec
8 usec
6 usec
2 usec
Sample Output
show oam ethernet
connectivity-fault
-management
sla-iterator-statistics
(MX Series and ACX
Series Routers with
Ethernet synthetic loss
user@switch> show oam ethernet connectivity-fault-management sla-iterator-statistics

remote-mep 2
Iterator statistics:
Maintenance domain: md6, Level: 6
Maintenance association: ma6, Local MEP id: 1000
Remote MEP id: 103, Remote MAC address: 00:90:69:0a:43:92
Iterator name: i1, Iterator Id: 1
Iterator cycle time: 10ms, Iteration period: 1 cycles
805
measurement
configured)
Iterator status: running, Infinite iterations: true

Counter reset time: 2010-03-19 20:42:39 PDT (2d 18:24 ago)
Reset reason: Adjacency flap
Iterator delay measurement statistics:
Delay weight: 1, Delay variation weight: 1
DMM sent
DMM skipped for threshold hit
DMM skipped for threshold hit window
DMR received
DMR out of sequence
DMR received with invalid time stamps
Average one-way forward delay variation
Average one-way backward delay variation
Weighted average two-way delay
Weighted average two-way delay variation
Weighted average one-way forward delay variation
Weighted average one-way backward delay variation
:
:
:
:
:
:
:
:
:
:
:
:
:
:
23898520
11000
0
23851165
1142
36540
129 usec
15 usec
22 usec
22 usec
134 usec
8 usec
6 usec
2 usec
Iterator Synthetic Loss measurement statistics:

SLM packets sent
: 100
: 0
SLR packets sent
: 100
: 0
Local TXFC1 value
: 100
Local RXFC1 value
: 100
Last Received SLR frame TXFCf
: 100
Last Received SLR frame TXFCb
: 100
SLM Frame Loss:
: 0 (0.00 %)
: 0 (0.00 %)
806
show oam ethernet connectivity-fault-management synthetic-loss-statistics

Syntax
Release Information
Description
Options
show oam ethernet connectivity-fault-management synthetic-loss-statistics

<count entry-count>

On ACX Series routers with Ethernet interfaces, display the on-demand ETH-SLM
statistics.
count entry-count(Optional) Number of entries to display from the statistics table. The
range of values is from 1 through 100. The default value is 100.

local-mep local-mep-id(Optional) Numeric identifier of the local MEP. The range of
values is from 1 through 8192.

maintenance-domain md-nameName of an existing connectivity fault management
(CFM) maintenance domain.

of values is from 1 through 8192.

Required Privilege
Level
Related
Documentation
Output Fields
view

on page 327

synthetic-loss-statistics on page 809
connectivity-fault-management synthetic-loss-statistics command. Output fields are
listed in the approximate order in which they appear.
807
Table 62: show oam ethernet connectivity-fault-management synthetic-loss-statistics Output

Fields
Output Field Name
Field Description
MEP identifier
Maintenance association end point (MEP) numeric identifier.
MAC address
Unicast MAC address configured for the MEP.
Remote MEP count
Number of remote MEPs (unless you specify the remote-mep option).
Remote MAC address
SLM packets sent
Total number of synthetic loss message (SLM) PDU frames sent from the source
MEP to the remote MEP during this ETH-SLM session.
Total number of synthetic loss message (SLM) PDU frames that the remote
MEP received from the source MEP during this ETH-SLM session.
SLR packets sent
Total number of synthetic loss reply (SLR) PDU frames that the remote MEP
sent to the source MEP during this measurement session.
Total number of synthetic loss reply (SLR) PDU frames that the source MEP
received from the remote MEP during this measurement session.
Local TXFC1 value
Number of synthetic frames transmitted to the peer MEP for a test ID. A test ID
is used to distinguish each synthetic loss measurement because multiple
measurements can be simultaneously activated also on a given CoS and MEP
pair. It must be unique at least within the context of any SLM for the MEG and
initiating MEP.
Local RXFC1 value
Number of synthetic frames received from the peer MEP for a test ID. The MEP
generates a unique Test ID for the session, adds the source MEP ID, and initializes
the local counters for the session before SLM initiation. For each SLM PDU
transmitted for the session (test ID), the local counter TxFC1 is sent in the packet.
Last Received SLR frame TXFCb(t
808
Sample Output
show oam ethernet
synthetic-loss-statistics
user@switch> show oam ethernet connectivity-fault-management synthetic-loss-statistics

Remote MEP count: 2
SLM packets sent
: 100
: 0
SLR packets sent
: 100
: 0
Local TXFC1 value
: 100
Local RXFC1 value
: 100
: 100
: 100
SLM Frame Loss:
: 0 (0.00 %)
: 0 (0.00 %)
809
show ospf database

Syntax
Syntax (EX Series

Switches and QFX
Series)
Release Information
show ospf database

<brief | detail | extensive | summary>
<advertising-router (address | self)>
<area area-id>
<asbrsummary>
<external>
<link-local>
<lsa-id lsa-id>
<netsummary>
<network>
<nssa>
<opaque-area>
<router>
show ospf database
<area area-id>
<asbrsummary>
<external>
<link-local>
<lsa-id lsa-id>
<netsummary>
<network>
<nssa>
<opaque-area>
<router>

advertising-router self (address | self) option introduced in Junos OS Release 9.5.
advertising-router self (address | self) option introduced in Junos OS Release 9.5 for EX
Series switches.
Description
Display the entries in the OSPF version 2 (OSPFv2) link-state database, which contains
data about link-state advertisement (LSA) packets.
Options
noneDisplay standard information about entries in the OSPFv2 link-state database for
all routing instances.

brief | detail | extensive | summary(Optional) Display the specified level of output.
advertising-router (address | self)(Optional) Display the LSAs advertised either by a
particular routing device or by this routing device.

area area-id(Optional) Display the LSAs in a particular area.
810
asbrsummary(Optional) Display summary AS boundary router LSA entries.

external(Optional) Display external LSAs.
instance instance-name(Optional) Display all OSPF database information under the
named routing instance.

link-local(Optional) Display information about link-local LSAs.

lsa-id lsa-id(Optional) Display the LSA with the specified LSA identifier.
netsummary(Optional) Display summary network LSAs.
network(Optional) Display information about network LSAs.
nssa(Optional) Display information about not-so-stubby area (NSSA) LSAs.
opaque-area(Optional) Display opaque area-scope LSAs.
router(Optional) Display information about router LSAs.
Required Privilege
Level
Related
Documentation
Output Fields
view
clear (ospf | ospf3) database
show ospf database on page 814

show ospf database brief on page 814
show ospf database detail on page 814
show ospf database extensive on page 815
show ospf database summary on page 818
Table 63 on page 811 describes the output fields for the show ospf database command.
Table 63: show ospf database Output Fields

Field Name
Field Description
Level of Output
area
Area number. Area 0.0.0.0 is the backbone area.
All levels
Type
Type of link advertisement: ASBRSum, Extern, Network, NSSA, OpaqArea, Router,

or Summary.
All levels
ID
LSA identifier included in the advertisement. An asterisk preceding the identifier

marks database entries that originated from the local routing device.
All levels
Adv Rtr
Address of the routing device that sent the advertisement.
All levels
Seq
Link sequence number of the advertisement.
All levels
811
Table 63: show ospf database Output Fields (continued)

Field Name
Field Description
Level of Output
Age
Time elapsed since the LSA was originated, in seconds.
All levels
Opt
Optional OSPF capabilities associated with the LSA.
All levels
Cksum
Checksum value of the LSA.
All levels
Len
Length of the advertisement, in bytes.
All levels
Router
Router link-state advertisement information:
detail extensive
bitsFlags describing the routing device that generated the LSP.
link countNumber of links in the advertisement.
idID of a routing device or subnet on the link.
dataFor stub networks, the subnet mask. Otherwise, the IP address of the
routing device that generated the LSP.
Network
Summary
typeType of link. It can be PointToPoint, Transit, Stub, or Virtual.
TOS countNumber of type-of-service (ToS) entries in the advertisement.
TOS 0 metricMetric for ToS 0.
TOSType-of-service (ToS) value.
metricMetric for the ToS.
Network link-state advertisement information:
maskNetwork mask.
attached routerID of the attached neighbor.
Summary link-state advertisement information:
maskNetwork mask.
TOSType-of-service (ToS) value.
metricMetric for the ToS.
detail extensive
detail extensive
Gen timer
How long until the LSA is regenerated.
extensive
Aging timer
How long until the LSA expires.
extensive
Installed hh:mm:ss
ago
How long ago the route was installed.
extensive
expires in hh:mm:ss
How long until the route expires.
extensive
sent hh:mm:ss ago
How long ago the LSA was sent.
extensive
Last changed
hh:mm:ss ago
How long ago the route was changed.
extensive
Change count
Number of times the route has changed.
extensive
812
Table 63: show ospf database Output Fields (continued)

Field Name
Field Description
Level of Output
Ours
Indicates that this is a local advertisement.
extensive
Router LSAs
Number of router link-state advertisements in the link-state database.
summary
Network LSAs
Number of network link-state advertisements in the link-state database.
summary
Summary LSAs
Number of summary link-state advertisements in the link-state database.
summary
NSSA LSAs
Number of not-so-stubby area link-state advertisements in the link-state

database.
summary
813
Sample Output
show ospf database
user@host> show ospf database

OSPF link state database, Area 0.0.0.1
Type
ID
Adv Rtr
Router
10.255.70.103
10.255.70.103
Router *10.255.71.242
10.255.71.242
Summary *23.1.1.0
10.255.71.242
Summary *24.1.1.0
10.255.71.242
NSSA
*33.1.1.1
10.255.71.242
Seq
0x80000002
0x80000002
0x80000002
0x80000002
0x80000002
Age
215
214
172
177
217
Opt
0x20
0x20
0x20
0x20
0x28
Cksum Len
0x4112 48
0x11b1 48
0x6d72 28
0x607e 28
0x73bd 36

Type
ID
Adv Rtr
Router
10.255.71.52
10.255.71.52
Router *10.255.71.242
10.255.71.242
Network *23.1.1.1
10.255.71.242
Summary *12.1.1.0
10.255.71.242
Summary *24.1.1.0
10.255.71.242
NSSA
*33.1.1.1
10.255.71.242
Seq
0x80000004
0x80000003
0x80000002
0x80000001
0x80000002
0x80000001
Age
174
173
173
217
177
222
Opt
0x20
0x20
0x20
0x20
0x20
0x28
Cksum Len
0xd021 36
0xe191 36
0x9c76 32
0xfeec 28
0x607e 28
0xe047 36

Type
ID
Adv Rtr
Router
10.255.71.238
10.255.71.238
Router *10.255.71.242
10.255.71.242
Network *24.1.1.1
10.255.71.242
Summary *12.1.1.0
10.255.71.242
Summary *23.1.1.0
10.255.71.242
NSSA
*33.1.1.1
10.255.71.242
Seq
0x80000003
0x80000003
0x80000002
0x80000001
0x80000002
0x80000001
Age
179
177
177
217
172
222
Opt
0x20
0x20
0x20
0x20
0x20
0x28
Cksum Len
0x3942 36
0xf37d 36
0xc591 32
0xfeec 28
0x6d72 28
0xeb3b 36
show ospf database

brief
The output for the show ospf database brief command is identical to that for the show
ospf database command. For sample output, see show ospf database on page 814.
show ospf database

detail
user@host> show ospf database detail

Type
ID
Adv Rtr
Seq
Age
Router
10.255.70.103
10.255.70.103
0x80000002
261
bits 0x0, link count 2
id 10.255.71.242, data 12.1.1.1, Type PointToPoint (1)
TOS count 0, TOS 0 metric 1
id 12.1.1.0, data 255.255.255.0, Type Stub (3)
Router *10.255.71.242
10.255.71.242
0x80000002
260
id 12.1.1.0, data 255.255.255.0, Type Stub (3)
Summary *23.1.1.0
10.255.71.242
0x80000002
218
mask 255.255.255.0
TOS 0x0, metric 1
Summary *24.1.1.0
10.255.71.242
0x80000002
223
mask 255.255.255.0
TOS 0x0, metric 1
NSSA
*33.1.1.1
10.255.71.242
0x80000002
263
mask 255.255.255.255
Type 2, TOS 0x0, metric 0, fwd addr 12.1.1.2, tag 0.0.0.0
Opt Cksum Len

0x20 0x4112 48
0x20 0x11b1
48
0x20 0x6d72
28
0x20 0x607e
28
0x28 0x73bd
36
814
Type
ID
Adv Rtr
Seq
Age
Router
10.255.71.52
10.255.71.52
0x80000004
220
id 23.1.1.1, data 23.1.1.2, Type Transit (2)
Router *10.255.71.242
10.255.71.242
0x80000003
219
Network *23.1.1.1
10.255.71.242
0x80000002
219
mask 255.255.255.0
attached router 10.255.71.242
Summary *12.1.1.0
10.255.71.242
0x80000001
263
mask 255.255.255.0
TOS 0x0, metric 1
Summary *24.1.1.0
10.255.71.242
0x80000002
223
mask 255.255.255.0
TOS 0x0, metric 1
NSSA
*33.1.1.1
10.255.71.242
0x80000001
268
mask 255.255.255.255
Type
ID
Adv Rtr
Seq
Age
Router
10.255.71.238
10.255.71.238
0x80000003
225
Router *10.255.71.242
10.255.71.242
0x80000003
223
Network *24.1.1.1
10.255.71.242
0x80000002
223
mask 255.255.255.0
Summary *12.1.1.0
10.255.71.242
0x80000001
263
mask 255.255.255.0
TOS 0x0, metric 1
Summary *23.1.1.0
10.255.71.242
0x80000002
218
mask 255.255.255.0
TOS 0x0, metric 1
NSSA
*33.1.1.1
10.255.71.242
0x80000001
268
mask 255.255.255.255
show ospf database

extensive
user@host> show ospf database extensive

Type
ID
Adv Rtr
Seq
Age
Router
10.255.70.103
10.255.70.103
0x80000002
286
id 12.1.1.0, data 255.255.255.0, Type Stub (3)
Aging timer 00:55:14
Installed 00:04:43 ago, expires in 00:55:14
Last changed 00:04:43 ago, Change count: 2
Router *10.255.71.242
10.255.71.242
0x80000002
285
Opt Cksum Len

0x20 0xd021 36
0x20 0xe191
36
0x20 0x9c76
32
0x20 0xfeec
28
0x20 0x607e
28
0x28 0xe047
36
Opt Cksum Len

0x20 0x3942 36
0x20 0xf37d
36
0x20 0xc591
32
0x20 0xfeec
28
0x20 0x6d72
28
0x28 0xeb3b
36
Opt Cksum Len

0x20 0x4112 48
0x20 0x11b1
48
815

id 12.1.1.0, data 255.255.255.0, Type Stub (3)
Gen timer 00:45:15
Installed 00:04:45 ago, expires in 00:55:15, sent 00:04:43
Last changed 00:04:45 ago, Change count: 2, Ours
Summary *23.1.1.0
10.255.71.242
0x80000002
243
mask 255.255.255.0
TOS 0x0, metric 1
Gen timer 00:45:57
Summary *24.1.1.0
10.255.71.242
0x80000002
248
mask 255.255.255.0
TOS 0x0, metric 1
Gen timer 00:45:52
NSSA
*33.1.1.1
10.255.71.242
0x80000002
288
mask 255.255.255.255
Gen timer 00:45:12
Type
ID
Adv Rtr
Seq
Age
Router
10.255.71.52
10.255.71.52
0x80000004
245
Router *10.255.71.242
10.255.71.242
0x80000003
244
Gen timer 00:45:56
Network *23.1.1.1
10.255.71.242
0x80000002
244
mask 255.255.255.0
Gen timer 00:45:56
Summary *12.1.1.0
10.255.71.242
0x80000001
288
mask 255.255.255.0
TOS 0x0, metric 1
Gen timer 00:45:12
816
ago
0x20 0x6d72
28
ago
0x20 0x607e
28
ago
0x28 0x73bd
36
ago
Opt Cksum Len

0x20 0xd021 36
0x20 0xe191
36
ago
0x20 0x9c76
32
ago
0x20 0xfeec
28
ago

Summary *24.1.1.0
10.255.71.242
0x80000002
248
mask 255.255.255.0
TOS 0x0, metric 1
Gen timer 00:45:52
NSSA
*33.1.1.1
10.255.71.242
0x80000001
293
mask 255.255.255.255
Gen timer 00:45:07
Type
ID
Adv Rtr
Seq
Age
Router
10.255.71.238
10.255.71.238
0x80000003
250
Router *10.255.71.242
10.255.71.242
0x80000003
248
Gen timer 00:45:52
Network *24.1.1.1
10.255.71.242
0x80000002
248
mask 255.255.255.0
Gen timer 00:45:52
Summary *12.1.1.0
10.255.71.242
0x80000001
288
mask 255.255.255.0
TOS 0x0, metric 1
Gen timer 00:45:12
Summary *23.1.1.0
10.255.71.242
0x80000002
243
mask 255.255.255.0
TOS 0x0, metric 1
Gen timer 00:45:57
NSSA
*33.1.1.1
10.255.71.242
0x80000001
293
mask 255.255.255.255
Gen timer 00:45:07
0x20 0x607e
28
ago
0x28 0xe047
36
ago
Opt Cksum Len

0x20 0x3942 36
0x20 0xf37d
36
ago
0x20 0xc591
32
ago
0x20 0xfeec
28
ago
0x20 0x6d72
28
ago
0x28 0xeb3b
36
ago
817
show ospf database

summary
818
user@host> show ospf database summary

Area 0.0.0.1:
2 Router LSAs
2 Summary LSAs
1 NSSA LSAs
Area 0.0.0.2:
2 Router LSAs
1 Network LSAs
2 Summary LSAs
1 NSSA LSAs
Area 0.0.0.3:
2 Router LSAs
1 Network LSAs
2 Summary LSAs
1 NSSA LSAs
Externals:
Interface fe-2/2/1.0:
Interface ge-0/3/2.0:
Interface so-0/1/2.0:
show ospf3 database

Syntax
Syntax (EX Series

Switches and QFX
Series)
show ospf3 database

<area area-id>
<external>
<inter-area-prefix>
<inter-area-router>
<intra-area-prefix>
<link>
<link-local>
<lsa-id lsa-id>
<network>
<nssa>
<realm (ipv4-multicast | ipv4-unicast | ipv6-multicast)>
<router>
show ospf3 database
<area area-id>
<external>
<inter-area-prefix>
<inter-area-router>
<intra-area-prefix>
<link>
<link-local>
<lsa-id lsa-id>
<network>
<nssa>
<router>
Release Information

realm option introduced in Junos OS Release 9.2.
advertising-router (address | self) option introduced in Junos Relase 9.5.
advertising-router (address | self) option introduced in Junos OS Release 9.5 for EX Series
switches.
Description
Display the entries in the OSPF version 3 (OSPFv3) link-state database, which contains
data about link-state advertisement (LSA) packets.
Options
noneDisplay standard information about all entries in the OSPFv3 link-state database.
brief | detail | extensive | summary(Optional) Display the specified level of output.
advertising-router (address | self)(Optional) Display the LSAs advertised either by a
particular routing device or by this routing device.
819
area area-id(Optional) Display the LSAs in a particular area.

external(Optional) Display external LSAs.
instance instance-name(Optional) Display all OSPF database information under the
named routing instance.

inter-area-prefix(Optional) Display information about interarea-prefix LSAs.
inter-area-router(Optional) Display information about interarea-router LSAs.
intra-area-prefix(Optional) Display information about intra-area-prefix LSAs.
link(Optional) Display information about link LSAs.
link-local(Optional) Display information about link-local LSAs.

lsa-id lsa-id(Optional) Display the LSA with the specified LSA identifier.
network(Optional) Display information about network LSAs.
nssa(Optional) Display information about not-so-stubby area (NSSA) LSAs.
realm (ipv4-multicast | ipv4-unicast | ipv6-multicast)(Optional) Display information
about the specified OSPFv3 realm, or address family. Use the realm option to specify
an address family other than IPv6 unicast, which is the default.
router(Optional) Display information about router LSAs.
Required Privilege
Level
Related
Documentation
Output Fields
view
clear (ospf | ospf3) database
show ospf3 database brief on page 826

show ospf3 database extensive on page 826
show ospf3 database summary on page 829
Table 64 on page 820 lists the output fields for the show ospf3 database command. Output
Table 64: show ospf3 database Output Fields

Field Name
Field Description
Level of Output
OSPF link state

database, area
area-number
Entries in the link-state database for this area.
brief detail extensive
OSPF AS SCOPE
link state database
Entries in the AS scope link-state database.
820
Table 64: show ospf3 database Output Fields (continued)

Field Name
Field Description
Level of Output
OSPF Link-Local
link state database,
interface
interface-name
Entries in the link-local link-state database for this interface.
area
All levels
Type
Type of link advertisement: Extern, InterArPfx, InterArRtr, IntraArPrx , Link, Network,

NSSA, or Router.
ID
Link identifier included in the advertisement. An asterisk (*) preceding the

identifier marks database entries that originated from the local routing device.
Adv Rtr
Address of the routing device that sent the advertisement.
Seq
Link sequence number of the advertisement.
Age
Time elapsed since the LSA was originated, in seconds.
Cksum
Checksum value of the LSA.
Len
Length of the advertisement, in bytes.
Router (Router Link-State Advertisements)

bits
Flags describing the routing device that generated the LSP.
detail extensive
Options
Option bits carried in the router LSA.
detail extensive
For Each Router Link

Type
Type of interface. The value of all other output fields describing a routing device
interface depends on the interfaces type:
PointToPoint (1)Point-to-point connection to another routing device.
Transit (2)Connection to a transit network.
Virtual (4)Virtual link.
detail extensive
Loc-if-id
Local interface ID assigned to the interface that uniquely identifies the interface
with the routing device.
detail extensive
Nbr-if-id
Interface ID of the neighbor's interface for this routing device link.
detail extensive
Nbr-rtr-id
Router ID of the neighbor routing device (for type 2 interfaces, the attached
links designated router).
detail extensive
Metric
Cost of the router link.
detail extensive
Gen timer
How long until the LSA is regenerated, in the format hours:minutes:seconds.
extensive
821

Field Name
Field Description
Level of Output
Aging timer
How long until the LSA expires, in the format hours:minutes:seconds.
extensive
Installed nn:nn:nn
ago
How long ago the route was installed, in the format hours:minutes:seconds.
extensive
expires in nn:nn:nn
How long until the route expires, in the format hours:minutes:seconds.
extensive
sent nn:nn:nn ago
Time elapsed since the LSA was last transmitted or flooded to an adjacency
or an interface, respectively, in the format hours:minutes:seconds.
extensive
Ours
extensive
Network (Network Link-State Advertisements)

Options
Option bits carried in the network LSA.
detail extensive
Attached Router
Router IDs of each of the routing devices attached to the link. Only routing
devices that are fully adjacent to the designated router are listed. The designated
router includes itself in this list.
detail extensive
InterArPfx (Interarea-Prefix Link-State Advertisements)

Prefix
IPv6 address prefix.
detail extensive
Prefix-options
Option bit associated with the prefix.
detail extensive
Metric
Cost of this route. Expressed in the same units as the interface costs in the router
LSAs. When the interarea-prefix LSA is describing a route to a range of addresses,
the cost is set to the maximum cost to any reachable component of the address
range.
detail extensive
Gen timer
extensive
Aging timer
extensive
Installed nn:nn:nn
ago
extensive
expires in nn:nn:nn
extensive
sent nn:nn:nn ago
extensive
Ours
extensive
InterArRtr (Interarea-Router Link-State Advertisements)

Dest-router-id
Router ID of the routing device described by the LSA.
detail extensive
options
Optional capabilities supported by the routing device.
detail extensive
822

Field Name
Field Description
Level of Output
Metric
Cost of this route. Expressed in the same units as the interface costs in the router
LSAs. When the interarea-prefix LSA is describing a route to a range of addresses,
the cost is set to the maximum cost to any reachable component of the address
range.
detail extensive
Prefix
extensive
Prefix-options
extensive
Extern (External Link-State Advertisements)

Prefix
detail extensive
Prefix-options
detail extensive
Metric
Cost of the route, which depends on the value of Type.
detail extensive
Type n
Type of external metric: Type 1 or Type 2.
detail extensive
Aging timer
extensive
Installed nn:nn:nn
ago
extensive
expires in nn:nn:nn
extensive
sent nn:nn:nn ago
extensive
Link (Link-State Advertisements)

IPv6-Address
IPv6 link-local address on the link for which this link LSA originated.
detail extensive
Options
Option bits carried in the link LSA.
detail extensive
priority
Router priority of the interface attaching the originating routing device to the
link.
detail extensive
Prefix-count
Number of IPv6 address prefixes contained in the LSA. The rest of the link LSA
contains a list of IPv6 prefixes to be associated with the link.
detail extensive
Prefix
detail extensive
Prefix-options
detail extensive
Gen timer
extensive
Aging timer
extensive
823

Field Name
Field Description
Level of Output
Installed nn:nn:nn
ago
extensive
expires in nn:nn:nn
extensive
sent nn:nn:nn ago
extensive
Ours
extensive
IntraArPfx (Intra-Area-Prefix Link-State Advertisements)

Ref-lsa-type
LSA type of the referenced LSA.
RouterAddress prefixes are associated with a router LSA.
NetworkAddress prefixes are associated with a network LSA.
detail extensive
Ref-lsa-id
Link-state ID of the referenced LSA.
detail extensive
Ref-router-id
Advertising router ID of the referenced LSA.
detail extensive
Prefix-count
Number of IPv6 address prefixes contained in the LSA. The rest of the link LSA
contains a list of IPv6 prefixes to be associated with the link.
detail extensive
Prefix
detail extensive
Prefix-options
detail extensive
Metric
Cost of this prefix. Expressed in the same units as the interface costs in the
router LSAs.
detail extensive
Gen timer
extensive
Aging timer
extensive
Installed hh:mm:ss
ago
extensive
expires in hh:mm:ss
extensive
sent hh:mm:ss ago
extensive
n Router LSAs
Number of router LSAs in the link-state database.
summary
n Network LSAs
Number of network LSAs in the link-state database.
summary
n InterArPfx LSAs
Number of interarea-prefix LSAs in the link-state database.
summary
824

Field Name
Field Description
Level of Output
n InterArRtr LSAs
Number of interarea-router LSAs in the link-state database.
summary
n IntraArPfx LSAs
Number of intra-area-prefix LSAs in the link-state database.
summary
Externals
Display of the external LSA database.
summary
n Extern LSAs
Number of external LSAs in the link-state database.
summary
Interface
interface-name
Name of the interface for which link-local LSA information is displayed.
summary
n Link LSAs
Number of link LSAs in the link-state database.
summary
825
Sample Output
show ospf3 database
brief
show ospf3 database

extensive
826
user@host> show ospf3 database brief

OSPF3 link state database, area 0.0.0.0
Type
ID
Adv Rtr
Router
0.0.0.1
10.255.4.85
Router
*0.0.0.1
10.255.4.93
InterArPfx *0.0.0.2
10.255.4.93
InterArRtr *0.0.0.1
10.255.4.93
IntraArPfx *0.0.0.1
10.255.4.93
Seq
0x80000003
0x80000002
0x80000001
0x80000001
0x80000002
Age
885
953
910
910
432
Cksum Len
0xa697 40
0xc677 40
0xb96f 44
0xe159 32
0x788f 72

Type
ID
Adv Rtr
Router
*0.0.0.1
10.255.4.93
Router
0.0.0.1
10.255.4.97
Network
0.0.0.2
10.255.4.97
InterArPfx *0.0.0.1
10.255.4.93
InterArPfx *0.0.0.2
10.255.4.93
NSSA
0.0.0.1
10.255.4.97
IntraArPfx 0.0.0.1
10.255.4.97
Seq
0x80000003
0x80000006
0x80000002
0x80000002
0x80000002
0x80000002
0x80000006
Age
916
851
916
117
62
362
851
Cksum Len
0xea40 40
0xc95b 40
0x4598 32
0xa980 44
0xd47e 44
0x45ee 44
0x2f77 52
OSPF3 AS SCOPE link state database

Type
ID
Adv Rtr
Extern
0.0.0.1
10.255.4.85
Extern
*0.0.0.1
10.255.4.93
Seq
0x80000002
0x80000001
Age
63
910
Cksum Len
0x9b86 44
0x59c9 44
OSPF3 Link-Local link state database, interface ge-1/3/0.0

Type
ID
Adv Rtr
Seq
Age
Link
*0.0.0.2
10.255.4.93
0x80000003
916
Cksum Len
0x4dab 64
user@host> show ospf3 database extensive

Type
ID
Adv Rtr
Seq
Age Cksum Len
Router
0.0.0.1
10.255.4.85
0x80000003 1028 0xa697 40
bits 0x2, Options 0x13
Type PointToPoint (1), Metric 10
Loc-If-Id 2, Nbr-If-Id 3, Nbr-Rtr-Id 10.255.4.93
Installed 00:17:05 ago, expires in 00:42:52, sent 02:37:54 ago
Router
*0.0.0.1
10.255.4.93
0x80000002 1096 0xc677 40
Type PointToPoint (1), Metric 10
Gen timer 00:00:40
Ours
InterArPfx *0.0.0.2
10.255.4.93
0x80000001 1053 0xb96f 44
Prefix feee::10:10:2:0/126
Prefix-options 0x0, Metric 10
Gen timer 00:17:02
Ours
InterArPfx *0.0.0.3
10.255.4.93
0x80000001 1053 0x71d3 44
Prefix feee::10:255:4:97/128
Gen timer 00:21:07

Ours
InterArRtr *0.0.0.1
10.255.4.93
0x80000001 1053 0xe159 32
Dest-router-id 10.255.4.97, Options 0x19, Metric 10
Gen timer 00:29:18
Ours
IntraArPfx 0.0.0.1
10.255.4.85
0x80000002 1028 0x2403 72
Ref-lsa-type Router, Ref-lsa-id 0.0.0.0, Ref-router-id 10.255.4.85
Prefix-count 2
Prefix feee::10:255:4:85/128
Prefix feee::10:10:1:0/126
IntraArPfx *0.0.0.1
10.255.4.93
0x80000002
575 0x788f 72
Prefix-count 2
Prefix feee::10:255:4:93/128
Prefix feee::10:10:1:0/126
Gen timer 00:33:23
Type
ID
Adv Rtr
Seq
Age Cksum Len
Router
*0.0.0.1
10.255.4.93
0x80000003 1059 0xea40 40
Type Transit (2), Metric 10
Gen timer 00:08:51
Router
0.0.0.1
10.255.4.97
0x80000006
994 0xc95b 40
Type Transit (2), Metric 10
Network
0.0.0.2
10.255.4.97
0x80000002 1059 0x4598 32
Options 0x11
Attached router 10.255.4.97
Attached router 10.255.4.93
InterArPfx *0.0.0.1
10.255.4.93
0x80000002
260 0xa980 44
Prefix feee::10:10:1:0/126
Gen timer 00:45:39
Ours
InterArPfx *0.0.0.2
10.255.4.93
0x80000002
205 0xd47e 44
Prefix feee::10:255:4:93/128
Gen timer 00:46:35
827
Ours
InterArPfx *0.0.0.3
10.255.4.93
0x80000001 1089 0x9bbb 44
Prefix feee::10:255:4:85/128
Gen timer 00:04:46
Ours
NSSA
0.0.0.1
10.255.4.97
0x80000002
505 0x45ee 44
Prefix feee::200:200:1:0/124
Prefix-options 0x8, Metric 10, Type 2,
IntraArPfx 0.0.0.1
10.255.4.97
0x80000006
994 0x2f77 52
Prefix-count 1
Prefix feee::10:255:4:97/128
IntraArPfx 0.0.0.3
10.255.4.97
0x80000002 1059 0x4446 52
Ref-lsa-type Network, Ref-lsa-id 0.0.0.2, Ref-router-id 10.255.4.97
Prefix-count 1
Prefix feee::10:10:2:0/126
OSPF3 AS SCOPE link state database
Type
ID
Adv Rtr
Seq
Age Cksum Len
Extern
0.0.0.1
10.255.4.85
0x80000002
206 0x9b86 44
Prefix feee::100:100:1:0/124
Extern
*0.0.0.1
10.255.4.93
0x80000001 1053 0x59c9 44
Prefix feee::200:200:1:0/124
Gen timer 00:25:12
OSPF3 Link-Local link state database, interface ge-1/3/0.0
Type
ID
Adv Rtr
Seq
Age Cksum Len
Link
*0.0.0.2
10.255.4.93
0x80000003 1059 0x4dab 64
fe80::290:69ff:fe39:1cdb
Options 0x11, priority 128
Prefix-count 1
Prefix feee::10:10:2:0/126 Prefix-options 0x0
Gen timer 00:12:56
Link
0.0.0.2
10.255.4.97
0x80000003
205 0xa87d 64
fe80::290:69ff:fe38:883e
Prefix-count 1
OSPF3 Link-Local link state database, interface so-2/2/0.0
Type
ID
Adv Rtr
Seq
Age
828
Cksum
Len
Link
0.0.0.2
10.255.4.85
0x80000002
506 0x42bb
fe80::280:42ff:fe10:f169
Prefix-count 1
Link
*0.0.0.3
10.255.4.93
0x80000002
505 0x6b7a
fe80::280:42ff:fe10:f177
Prefix-count 1
Gen timer 00:37:28
Ours
show ospf3 database

summary
64
64
user@host> show ospf3 database summary

Area 0.0.0.0:
2 Router LSAs
1 InterArPfx LSAs
1 InterArRtr LSAs
1 IntraArPfx LSAs
Area 0.0.0.1:
2 Router LSAs
1 Network LSAs
2 InterArPfx LSAs
1 NSSA LSAs
1 IntraArPfx LSAs
Externals:
2 Extern LSAs
Interface ge-1/3/0.0:
1 Link LSAs
Interface lo0.0:
1 Link LSAs
829
show (ospf | ospf3) interface

Syntax
Syntax (EX Series

Switches and QFX
Series)
Release Information
Description
Options

<area area-id>
<interface-name>
<realm (ip4-multicast | ipv4-unicast | ipv6-multicast)>
<area area-id>
<interface-name>

area option introduced in Junos OS Release 9.2.
area option introduced in Junos OS Release 9.2 for EX Series switches.
Display the status of OSPF interfaces.
noneDisplay standard information about the status of all OSPF interfaces for all routing
instances
area area-id(Optional) Display information about the interfaces that belong to the
specified area.
interface-name(Optional) Display information for the specified interface.
instance instance-name(Optional) Display all OSPF interfaces under the named routing
instance.

realm (ipv4-multicast | ipv4-unicast | ipv6-multicast)(OSPFv3 only) (Optional) Display
information about the interfaces for the specified OSPFv3 realm, or address family.
Use the realm option to specify an address family for OSPFv3 other than IPv6 unicast,
which is the default.
Required Privilege
Level
830
view
show ospf interface brief on page 833

show ospf interface detail on page 833
show ospf3 interface detail on page 833
show ospf interface detail(When Multiarea Adjacency Is Configured) on page 833

show ospf interface area area-id on page 834
show ospf interface extensive (When Flooding Reduction Is Enabled) on page 834
show ospf interface extensive (When LDP Synchronization Is Configured) on page 835
Output Fields
Table 65 on page 831 lists the output fields for the show (ospf | ospf3) interface command.
Table 65: show (ospf | ospf3) interface Output Fields

Field Name
Field Description
Level of Output
Interface
Name of the interface running OSPF version 2 or OSPF version 3.
All levels
State
State of the interface: BDR, Down, DR, DRother, Loop, PtToPt, or Waiting.
All levels
Area
Number of the area that the interface is in.
All levels
DR ID
Address of the area's designated router.
All levels
BDR ID
Backup designated router for a particular subnet.
All levels
Nbrs
Number of neighbors on this interface.
All levels
Type
Type of interface: LAN, NBMA, P2MP, P2P, or Virtual.
detail extensive
Address
IP address of the neighbor.
detail extensive
Mask
Netmask of the neighbor.
detail extensive
Prefix-length
(OSPFv3) IPv6 prefix length, in bits.
detail extensive
OSPF3-Intf-Index
(OSPFv3) OSPF version 3 interface index.
detail extensive
MTU
Interface maximum transmission unit (MTU).
detail extensive
Cost
Interface cost (metric).
detail extensive
DR addr
Address of the designated router.
detail extensive
BDR addr
Address of the backup designated router.
detail extensive
Adj count
Number of adjacent neighbors.
detail extensive
Secondary
Indicates that this interface is configured as a secondary interface for this area.
This interface can belong to more than one area, but can be designated as a
primary interface for only one area.
detail extensive
Flood Reduction
Indicates that this interface is configured with flooding reduction. All

self-originated LSAs from this interface are initially sent with the DoNotAge bit
set. As a result, LSAs are refreshed only when a change occurs.
extensive
831
Table 65: show (ospf | ospf3) interface Output Fields (continued)

Field Name
Field Description
Level of Output
Priority
Router priority used in designated router (DR) election on this interface.
detail extensive
Flood list
List of link-state advertisements (LSAs) that might be about to flood this

interface.
extensive
Ack list
Acknowledgment list. List of pending acknowledgments on this interface.
extensive
Descriptor list
List of packet descriptors.
extensive
Hello
Configured value for the hello timer.
detail extensive
Dead
Configured value for the dead timer.
detail extensive
Auth type
(OSPFv2) Authentication mechanism for sending and receiving OSPF protocol

packets:
detail extensive
MD5The MD5 mechanism is configured in accordance with RFC 2328.
NoneNo authentication method is configured.
PasswordA simple password (RFC 2328) is configured.
Topology
(Multiarea adjacency) Name of topology: default or name.
LDP sync state
(OSPFv2 and LDP synchronization) Current state of LDP synchronization: in

sync, in holddown, and not supported.
extensive
reason
(OSPFv2 and LDP synchronization) Reason for the current state of LDP
synchronization. The LDP session might be up or down, or adjacency might be
up or down.
extensive
config holdtime
(OSPFv2 and LDP synchronization) Configured value of the hold timer.
extensive
If the state is not synchronized, and the hold time is not infinity, the remaining
field displays the number of seconds that remain until the configured hold timer
expires.
IPSec SA name
(OSPFv2) Name of the IPSec security association name.
detail extensive
Active key ID
(OSPFv2 and MD5) Number from 0 to 255 that uniquely identifies an MD5 key.
detail extensive
Start time
(OSPFv2 and MD5) Time at which the routing device starts using an MD5 key
to authenticate OSPF packets transmitted on the interface on which this key
is configured. To authenticate received OSPF protocol packets, the key becomes
effective immediately after the configuration is committed. If the start time
option is not configured, the key is effective immediately for send and receive
and is displayed as Start time 1970 Jan 01 00:00:00 PST.
detail extensive
ReXmit
Configured value for the Retransmit timer.
detail extensive
Stub, Not Stub, or

Stub NSSA
Type of area.
detail extensive
832
Sample Output
show ospf interface
brief
user@host> show ospf interface brief

Intf
State
Area
at-5/1/0.0
PtToPt
0.0.0.0
ge-2/3/0.0
DR
0.0.0.0
lo0.0
DR
0.0.0.0
so-0/0/0.0
Down
0.0.0.0
so-6/0/1.0
PtToPt
0.0.0.0
so-6/0/2.0
Down
0.0.0.0
so-6/0/3.0
PtToPt
0.0.0.0
show ospf interface

detail
user@host> show ospf interface detail

Interface
State
Area
DR ID
BDR ID Nbrs
fe-0/0/1.0
BDR
0.0.0.0
192.168.37.12
10.255.245.215 1
Type LAN, address 192.168.37.11, Mask 255.255.255.248, MTU 4460, Cost 40
DR addr 192.168.37.12, BDR addr 192.168.37.11, Adj count 1, Priority 128
Hello 10, Dead 40, ReXmit 5, Not Stub
t1-0/2/1.0
PtToPt
0.0.0.0
0.0.0.0
0.0.0.0 0
Type P2P, Address 0.0.0.0, Mask 0.0.0.0, MTU 1500, Cost 2604
Adj count 0
Auth type: MD5, Active key ID 3, Start time 2002 Nov 19 10:00:00 PST
IPsec SA Name: sa
show ospf3 interface

detail
user@host> show ospf3 interface so-0/0/3.0 detail

Interface
State
Area
DR-ID
BDR-ID
so-0/0/3.0
PtToPt
0.0.0.0
0.0.0.0
0.0.0.0
Address fe80::2a0:a5ff:fe28:1dfc, Prefix-length 64
OSPF3-Intf-index 1, Type P2P, MTU 4470, Cost 12, Adj-count 1
show ospf interface

detail
(When Multiarea
Adjacency Is
Configured)
user@host> show ospf interface detail

regress@router> show ospf interface detail
Interface
State
Area
lo0.0
DR
0.0.0.0
DR ID
0.0.0.0
192.168.4.16
192.168.4.16
0.0.0.0
0.0.0.0
0.0.0.0
0.0.0.0
DR ID
10.255.245.2
BDR ID
0.0.0.0
192.168.4.15
0.0.0.0
0.0.0.0
0.0.0.0
0.0.0.0
0.0.0.0
Nbrs
1
1
0
0
1
0
1
Nbrs
1
BDR ID
0.0.0.0
Type: LAN, Address: 127.0.0.1, Mask: 255.255.255.255, MTU: 65535, Cost: 0

DR addr: 127.0.0.1, Adj count: 0, Priority: 128
Hello: 10, Dead: 40, ReXmit: 5, Not Stub
Auth type: None
Topology default (ID 0) -> Cost: 0
lo0.0
DR
0.0.0.0
10.255.245.2
0.0.0.0
Nbrs
0
Type: LAN, Address: 10.255.245.2, Mask: 255.255.255.255, MTU: 65535, Cost: 0

DR addr: 10.255.245.2, Adj count: 0, Priority: 128
Auth type: None
so-0/0/0.0
PtToPt 0.0.0.0
0.0.0.0
0.0.0.0
1
Type: P2P, Address: 0.0.0.0, Mask: 0.0.0.0, MTU: 4470, Cost: 1
Adj count: 1
Auth type: None
so-0/0/0.0
PtToPt 0.0.0.0
0.0.0.0
0.0.0.0
833

Adj count: 0, , Passive
Auth type: None
Topology default (ID 0) -> Passive, Cost: 1
so-1/0/0.0
PtToPt 0.0.0.0
0.0.0.0
0.0.0.0
1
Adj count: 1
Auth type: None
so-1/0/0.0
PtToPt 0.0.0.0
0.0.0.0
0.0.0.0

Adj count: 0, , Passive
Auth type: None
Topology default (ID 0) -> Passive, Cost: 1
so-0/0/0.0
PtToPt 1.1.1.1
0.0.0.0
0.0.0.0
1
Adj count: 1, Secondary
Auth type: None
so-1/0/0.0
PtToPt 1.1.1.1
0.0.0.0
0.0.0.0

Auth type: None
so-0/0/0.0
PtToPt 2.2.2.2
0.0.0.0
0.0.0.0

Auth type: None
so-1/0/0.0
PtToPt 2.2.2.2
0.0.0.0
0.0.0.0

Auth type: None
show ospf interface

area area-id
user@host> show ospf interface area 1.1.1.1

Interface
State
Area
so-0/0/0.0
PtToPt 1.1.1.1
so-1/0/0.0
PtToPt 1.1.1.1
DR ID
0.0.0.0
0.0.0.0
BDR ID
0.0.0.0
0.0.0.0
Nbrs
1
1
show ospf interface

extensive
(When Flooding
Reduction Is Enabled)
user@host> show ospf interface extensive

Interface
State
Area
fe-0/0/0.0
PtToPt 0.0.0.0
DR ID
0.0.0.0
BDR ID
0.0.0.0
Nbrs
0

Adj count: 0
834
Secondary, Flood Reduction

Auth type: None
show ospf interface

extensive
(When LDP
Synchronization Is
Configured)
user@host> show ospf interface extensive

Interface
State
Area
DR ID
BDR ID
Nbrs
so-1/0/3.0
Down
0.0.0.0
0.0.0.0
0.0.0.0
0
Adj count: 0
Auth type: None
LDP sync state: in holddown, for: 00:00:08, reason: LDP down during config
config holdtime: 10 seconds, remaining: 1
835
show (ospf | ospf3) io-statistics

Syntax
Syntax (EX Series

Switch and QFX
Series)
Release Information
Description
Options


Display Open Shortest Path First (OSPF) input and output statistics.
noneDisplay OSPF input and output statistics.

Required Privilege
Level
Related
Documentation
Output Fields
view
clear (ospf | ospf3) statistics
show ospf io-statistics on page 837

Table 66 on page 836 lists the output fields for the show ospf io-statistics command.
Table 66: show (ospf | ospf3) io-statistics Output Fields
836
Field Name
Field Description
Packets read
Number of OSPF packets read since the last time the routing
protocol was started.
average per run
Total number of packets divided by the total number of times the

OSPF read operation is scheduled to run.
max run
Maximum number of packets for a given run among all scheduled

runs.
Receive errors
Number of faulty packets received with errors.
Sample Output
show ospf io-statistics
user@host> show ospf io-statistics

Packets read: 7361, average per run: 1.00, max run: 1
Receive errors:
None
837
show (ospf | ospf3) log

Syntax
Syntax (EX Series

Switch and QFX
Series)
Release Information
show (ospf | osfp3) log

<topology topology-name>
show (ospf | osfp3) log
<topology topology-name>

topology option introduced in Junos OS Release 9.0.
topology option introduced in Junos OS Release 9.0 for EX Series switches.
Description
Display the entries in the Open Shortest Path First (OSPF) log of SPF calculations.
Options
noneDisplay entries in the OSPF log of SPF calculations for all routing instances.
instance instance-name(Optional) Display entries for the specified routing instance.

topology topology-name(Optional) (OSPFv2 only) Display entries for the specified
topology.
entries for the specified OSPFv3 realm, or address family. Use the realm option to
specify an address family for OSPFv3 other than IPv6 unicast, which is the default.
Required Privilege
Level
Output Fields
view
show ospf log on page 840

show ospf log topology voice on page 840
Table 67 on page 838 lists the output fields for the show (ospf | ospf3) log command.
Table 67: show (ospf | ospf3) log Output Fields
838
Field Name
Field Description
When
Time, in weeks (w) and days (d), since the SPF calculation was
made.
Table 67: show (ospf | ospf3) log Output Fields (continued)

Field Name
Field Description
Type
Type of calculation: Cleanup, External, Interarea, NSSA, Redist, SPF,

Stub, Total, or Virtuallink.
Elapsed
Amount of time, in seconds, that elapsed during the operation, or

the time required to complete the SPF calculation. The start time
is the time displayed in the When field.
839
Sample Output
show ospf log
user@host> show ospf log

When
Type
1w4d
1w4d
1w4d
1w4d
1w4d
1w4d
1w4d
1w4d
1w4d
1w4d
1w4d
1w4d
1w4d
1w4d
1w4d
...
show ospf log topology

voice
17:25:58
17:25:58
17:25:58
17:25:58
17:25:58
17:25:58
17:25:58
17:24:48
17:24:48
17:24:48
17:24:48
17:24:48
17:24:48
17:24:48
17:24:48
Stub
SPF
Stub
Interarea
External
Cleanup
Total
SPF
Stub
SPF
Stub
Interarea
External
Cleanup
Total
Elapsed
0.000017
0.000070
0.000019
0.000054
0.000005
0.000203
0.000537
0.000125
0.000017
0.000100
0.000016
0.000056
0.000005
0.000238
0.000600
user@host> show ospf log topology voice

Topology voice SPF log:
Last instance of each event type
When
Type
Elapsed
00:06:11
SPF
0.000116
00:06:11
Stub
0.000114
00:06:11
Interarea
0.000126
00:06:11
External
0.000067
00:06:11
NSSA
0.000037
00:06:11
Cleanup
0.000186
Maximum length of each event type
When
Type
Elapsed
00:13:43
SPF
0.000140
00:13:33
Stub
0.000116
00:13:43
Interarea
0.000128
00:13:33
External
0.000075
00:13:38
NSSA
0.000039
00:13:53
Cleanup
0.000657
Last 100 events
When
Type
00:13:53
00:13:53
00:13:53
00:13:53
00:13:53
00:13:53
00:13:53
.
.
00:06:11
00:06:11
00:06:11
00:06:11
840
Elapsed
SPF
Stub
Interarea
External
NSSA
Cleanup
Total
0.000090
0.000041
0.000123
0.000040
0.000038
0.000657
0.001252
SPF
Stub
Interarea
External
0.000116
0.000114
0.000126
0.000067
00:06:11
00:06:11
00:06:11
NSSA
Cleanup
Total
0.000037
0.000186
0.000818
841
show (ospf | ospf3) neighbor

Syntax
Syntax (EX Series

Switches and QFX
Series)
Release Information
Description

<area area-id>
<instance (all | instance-name)>
<neighbor>
<area area-id>
<instance (all | instance-name)>
<neighbor>

instance all option introduced in Junos OS Release 9.1.
instance all option introduced in Junos OS Release 9.1 for EX Series switches.
area, interface, and realm options introduced in Junos OS Release 9.2.
area and interface options introduced in Junos OS Release 9.2 for EX Series switches.
Display information about OSPF neighbors.
CPU utilization might increase while the device learns its OSPF neighbors. We recommend
that you use the show (ospf | ospf3) neighbor command after the device learns and
establishes OSPF neighbor adjacencies. Depending on the size of your network, this might
take several minutes. If you receive a timeout communicating with routing daemon
error when using the show (ospf | ospf3) neighbor command, wait several minutes before
attempting to use the command again. This is not a critical system error, but you might
experience a delay in using the CLI.
Options
noneDisplay standard information about all OSPF neighbors for all routing instances.
area area-id(Optional) Display information about the OSPF neighbors for the specified
area.
instance (all | instance-name)(Optional) Display all OSPF interfaces for all routing
instances or under the named routing instance.

interface interface-name(Optional) Display information about OSPF neighbors for the
specified logical interface.

842
neighbor(Optional) Display information about the specified OSPF neighbor.

information about the OSPF neighbors for the specified OSPFv3 realm, or address
family. Use the realm option to specify an address family for OSPFv3 other than IPv6
unicast, which is the default.
Required Privilege
Level
Related
Documentation
Output Fields
view
clear (ospf | ospf3) neighbor
show ospf neighbor brief on page 846

show ospf neighbor detail on page 846
show ospf neighbor extensive on page 846
show ospf3 neighbor detail on page 847
show ospf neighbor area area-id on page 847
show ospf neighbor interface interface-name on page 847
show ospf3 neighbor instance all (OSPFv3 Multiple Family Address Support
Enabled) on page 848
Table 68 on page 843 lists the output fields for the show (ospf | ospf3) neighbor command.
Table 68: show (ospf | ospf3) neighbor Output Fields

Field Name
Field Description
Level of Output
Address
Address of the neighbor.
All levels
Interface
Interface through which the neighbor is reachable.
All levels
843
Table 68: show (ospf | ospf3) neighbor Output Fields (continued)

Field Name
Field Description
Level of Output
State
State of the neighbor:
All levels
AttemptValid only for neighbors attached to nonbroadcast networks. It
indicates that no recent information has been received from the neighbor,
but that a more concerted effort must be made to contact the neighbor.
DownInitial state of a neighbor conversation. It indicates that no recent
information has been received from the neighbor. Hello packets might
continue to be sent to neighbors in the Down state, although at a reduced
frequency.
ExchangeRouting device is describing its entire link-state database by
sending database description packets to the neighbor. Each packet has a

sequence number and is explicitly acknowledged.
ExStartFirst step in creating an adjacency between the two neighboring
routing devices. The goal of this step is to determine which routing device is
the master, and to determine the initial sequence number.
FullNeighboring routing devices are fully adjacent. These adjacencies appear
in router link and network link advertisements.
InitA hello packet has recently been sent by the neighbor. However,
bidirectional communication has not yet been established with the neighbor.
This state might occur, for example, because the routing device itself did not
appear in the neighbor's hello packet.
LoadingLink-state request packets are sent to the neighbor to acquire more
recent advertisements that have been discovered (but not yet received) in
the Exchange state.
2WayCommunication between the two routing devices is bidirectional. This
state has been ensured by the operation of the Hello Protocol. This is the
most advanced state short of beginning adjacency establishment. The
(backup) designated router is selected from the set of neighbors in state
2Way or greater.
ID
Router ID of the neighbor.
All levels
Pri
Priority of the neighbor to become the designated router.
All levels
Dead
Number of seconds until the neighbor becomes unreachable.
All levels
Link state
acknowledgment
list
Number of link-state acknowledgments received.
extensive
Link state
retransmission list
Total number of link-state advertisements retransmitted. For extensive output

only, the following information is also displayed:
detail extensive
TypeType of link advertisement: ASBR, Sum, Extern, Network, NSSA,

OpaqArea, Router, or Summary.
LSA IDLSA identifier included in the advertisement. An asterisk preceding
the identifier marks database entries that originated from the local routing
device.
844
Adv rtrAddress of the routing device that sent the advertisement.
SeqLink sequence number of the advertisement.
Table 68: show (ospf | ospf3) neighbor Output Fields (continued)

Field Name
Field Description
Level of Output
Neighbor-address
(OSPFv3 only) If the neighbor uses virtual links, the Neighbor-address is the
site-local, local, or global address. If the neighbor uses a physical interface, the
Neighbor-address is an IPv6 link-local address.
detail extensive
area
Area that the neighbor is in.
detail extensive
OSPF3-Intf-Index
(OSPFv3 only) Displays the OSPFv3 interface index.
detail extensive
opt
Option bits received in the hello packets from the neighbor.
detail extensive
DR or DR-ID
Address of the designated router.
detail extensive
BDR or BDR-ID
Address of the backup designated router.
detail extensive
Up
Length of time since the neighbor came up.
detail extensive
adjacent
Length of time since the adjacency with the neighbor was established.
detail extensive
845
Sample Output
show ospf neighbor
brief
user@host> show ospf neighbor brief

Address
Intf
192.168.254.225 fxp3.0
192.168.254.230 fxp3.0
192.168.254.229 fxp3.0
10.1.1.129
fxp2.0
10.1.1.131
fxp2.0
10.1.2.1
fxp1.0
10.1.2.81
fxp0.0
show ospf neighbor

detail
user@host> show ospf neighbor detail

Address
Interface
State
ID
10.5.1.2
ge-1/2/0.1
Full
10.5.1.2
area 0.0.0.1, opt 0x42, DR 10.5.1.2, BDR 10.5.1.1
Up 06:09:28, adjacent 05:17:36
Link state acknowledgment list: 3 entries
State
2Way
Full
Full
Full
Full
Full
Full
Dead
36
38
33
37
38
32
33
Dead
37
10.5.10.2
ge-1/2/0.10
ExStart
10.5.1.38
area 0.0.0.1, opt 0x42, DR 10.5.10.2, BDR 10.5.10.1
Up 06:09:28
master, seq 0xac1530f8, rexmit DBD in 3 sec
rexmit LSREQ in 0 sec
10.5.11.2
ge-1/2/0.11
Full
10.5.1.42
area 0.0.0.1, opt 0x42, DR 10.5.11.2, BDR 10.5.11.1
Up 06:09:28, adjacent 05:26:46
Link state retransmission list: 1 entries
128
34
128
38
10.5.12.2
ge-1/2/0.12
ExStart
10.5.1.46
area 0.0.0.1, opt 0x42, DR 10.5.12.2, BDR 10.5.12.1
Up 06:09:28
master, seq 0xac188a68, rexmit DBD in 2 sec
128
33
Pri
128
Dead
33
9 entries
user@host> show ospf neighbor extensive

Address
Interface
State
ID
10.5.1.2
ge-1/2/0.1
Full
10.5.1.2
area 0.0.0.1, opt 0x42, DR 10.5.1.2, BDR 10.5.1.1
Up 06:09:42, adjacent 05:17:50
Link state retransmission list:
Type
846
Pri
128
128
128
128
128
128
128
Pri
128
show ospf neighbor

extensive
ID
10.250.240.32
10.250.240.8
10.250.240.35
10.250.240.12
10.250.240.11
10.250.240.9
10.250.240.10
LSA ID
Adv rtr
Seq
Summary
10.8.56.0
172.25.27.82
0x8000004d
Router
10.5.1.94
10.5.1.94
0x8000005c
Network
10.5.24.2
10.5.1.94
0x80000036
Summary
10.8.57.0
172.25.27.82
0x80000024
Extern
1.10.90.0
10.8.1.2
0x80000041
Extern
1.4.109.0
10.6.1.2
0x80000041
Router
10.5.1.190
10.5.1.190
0x8000005f
Network
10.5.48.2
10.5.1.190
0x8000003d
Summary
10.8.58.0
172.25.27.82
0x8000004d
Extern
1.10.91.0
10.8.1.2
0x80000041
Extern
1.4.110.0
10.6.1.2
0x80000041
Router
10.5.1.18
10.5.1.18
0x8000005f
Network
10.5.5.2
10.5.1.18
0x80000033
Summary
10.8.59.0
172.25.27.82
0x8000003a
Summary
10.8.62.0
172.25.27.82
0x80000025
10.5.10.2
ge-1/2/0.10
ExStart
10.5.1.38
area 0.0.0.1, opt 0x42, DR 10.5.10.2, BDR 10.5.10.1
Up 06:09:42
master, seq 0xac1530f8, rexmit DBD in 2 sec
10.5.11.2
ge-1/2/0.11
Full
10.5.1.42
area 0.0.0.1, opt 0x42, DR 10.5.11.2, BDR 10.5.11.1
Up 06:09:42, adjacent 05:27:00
Type
LSA ID
Adv rtr
38
128
33
Seq
Summary
10.8.58.0
172.25.27.82
0x8000004d
Extern
1.10.91.0
10.8.1.2
0x80000041
Extern
1.1.247.0
10.5.1.2
0x8000003f
Extern
1.4.110.0
10.6.1.2
0x80000041
Router
10.5.1.18
10.5.1.18
0x8000005f
Network
10.5.5.2
10.5.1.18
0x80000033
Summary
10.8.59.0
172.25.27.82
0x8000003a
show ospf3 neighbor

detail
user@host> show ospf3 neighbor detail

ID
Interface
State
10.255.71.13
fe-0/0/2.0
Full
Neighbor-address fe80::290:69ff:fe9b:e002
area 0.0.0.0, opt 0x13, OSPF3-Intf-Index 2
DR-ID 10.255.71.13, BDR-ID 10.255.71.12
Up 02:51:43, adjacent 02:51:43
show ospf neighbor

area area-id
user@host >show ospf neighbor area 1.1.1.1

Address
Interface
192.168.37.47
so-0/0/0.0
Area 1.1.1.1
192.168.37.55
so-1/0/0.0
Area 1.1.1.1
128
Pri
128
Dead
30
State
Full
ID
10.255.245.4
Pri
128
Dead
33
Full
10.255.245.5
128
37
847
show ospf neighbor

interface
interface-name
show ospf3 neighbor

instance all (OSPFv3
Multiple Family
Address Support
Enabled)
848
user@host >show ospf neighbor interface so-0/0/0.0

Address
Interface
State
192.168.37.47
so-0/0/0.0
Full
Area 0.0.0.0
192.168.37.47
so-0/0/0.0
Full
Area 1.1.1.1
192.168.37.47
so-0/0/0.0
Full
Area 2.2.2.2
user @host > show ospf3 neighbor instance all

Instance: ina
Realm: ipv6-unicast
ID
Interface
State
100.1.1.1
fe-0/0/2.0
Full
Neighbor-address fe80::217:cb00:c87c:8c03
Instance: inb
Realm: ipv4-unicast
ID
Interface
State
100.1.2.1
fe-0/0/2.1
Full
Neighbor-address fe80::217:cb00:c97c:8c03
ID
10.255.245.4
Pri
128
Dead
37
10.255.245.4
128
33
10.255.245.4
128
32
Pri
128
Pri
128
Dead
37
Dead
33
show (ospf | ospf3) overview

Syntax
Syntax (EX Series

Switch and QFX
Series)
Release Information
Description
Options

<brief | extensive>
<brief | extensive>

Database protection introduced in Junos 10.2.
Display Open Shortest Path First (OSPF) overview information.
noneDisplay standard information about all OSPF neighbors for all routing instances.
brief | extensive(Optional) Display the specified level of output.
instance instance-name(Optional) Display all OSPF interfaces under the named routing
instance.

realm (ipv4-multicast | ipv4-unicast | ipv6-multicast)(Optional) (OSPFv3 only) Display
information about the specified OSPFv3 realm, or address family. Use the realm
option to specify an address family for OSPFv3 other than IPv6 unicast, which is the
default.
Required Privilege
Level
Output Fields
view
show ospf overview on page 852

show ospf overview (With Database Protection) on page 852
show ospf3 overview (With Database Protection) on page 852
show ospf overview extensive on page 853
Table 69 on page 849 lists the output fields for the show ospf overview command. Output
Table 69: show ospf overview Output Fields

Field name
Field Description
Level of Output
Instance
OSPF routing instance.
All levels
849
Table 69: show ospf overview Output Fields (continued)

Field name
Field Description
Level of Output
Router ID
Router ID of the routing device.
All levels
Route table index
Route table index.
All levels
Configured
overload
Overload capability is enabled. If the overload timer is also configured, display

the time that remains before it is set to expire. This field is not displayed after
the timer expires.
All levels
Toplogy
Topology identifier.
All levels
Prefix export count
Number of prefixes exported into OSPF.
All levels
Full SPF runs
Number of complete Shortest Path First calculations.
All levels
SPF delay
Delay before performing consecutive Shortest Path First calculations.
All levels
SPF holddown
Delay before performing additional Shortest Path First (SPF) calculations after
the maximum number of consecutive SPF calculations is reached.
All levels
SPF rapid runs
Maximum number of Shortest Path First calculations that can be performed in

succession before the hold-down timer begins.
All levels
LSA refresh time
Refresh period for link-state advertisement (in minutes).
All levels
Database
protection state
Current state of database protection.
All levels
Warning threshold
Threshold at which a warning message is logged (percentage of maximum LSA

count).
All levels
Non self-generated
LSAs
Number of LSAs whose router ID is not equal to the local router ID: Current,
Warning (threshold), and Allowed.
All levels
Ignore time
How long the database has been in the ignore state.
All levels
Reset time
How long the database must stay out of the ignore or isolated state before it
returns to normal operations.
All levels
Ignore count
Number of times the database has been in the ignore state: Current and Allowed.
All levels
Restart
Graceful restart capability: enabled or disabled.
All levels
Restart duration
Time period for complete reacquisition of OSPF neighbors.
All levels
Restart grace
period
Time period for which the neighbors should consider the restarting routing device
as part of the topology.
All levels
850
Table 69: show ospf overview Output Fields (continued)

Field name
Field Description
Level of Output
Graceful restart
helper mode
(OSPFv2) Standard graceful restart helper capability (based on RFC 3623):

enabled or disabled.
All levels
Restart-signaling
helper mode
(OSPFv2) Restart signaling-based graceful restart helper capability (based on

RFC 4811, RFC 4812, and RFC 4813): enabled or disabled.
All levels
Helper mode
(OSPFv3) Graceful restart helper capability: enabled or disabled.
All levels
Trace options
OSPF-specific trace options.
extensive
Trace file
Name of the file to receive the output of the tracing operation.
extensive
Area
All levels
Stub type
Stub type of area: Normal Stub, Not Stub, or Not so Stubby Stub.
All levels
Authentication
Type
Type of authentication: None, Password, or MD5.
All levels
NOTE: The Authentication Type field refers to the authentication configured at

the [edit protocols ospf area area-id] level. Any authentication configured for an
interface in this area will not affect the value of this field.
Area border routers
Number of area border routers.
All levels
Neighbors
Number of autonomous system boundary routers.
All levels
851
Sample Output
show ospf overview
user@host> show ospf overview

Instance: master
Router ID: 10.255.245.6
Route table index: 0
Configured overload, expires in 118 seconds
LSA refresh time: 50 minutes
Restart: Enabled
Restart grace period: 40 sec
Helper mode: enabled
Area: 0.0.0.0
Stub type: Not Stub
Authentication Type: None
Area border routers: 0, AS boundary routers: 0
Neighbors
Up (in full state): 0
Topology: default (ID 0)
Prefix export count: 0
Full SPF runs: 1
SPF delay: 0.200000 sec, SPF holddown: 5 sec, SPF rapid runs: 3
show ospf overview

(With Database
Protection)
user@host> show ospf overview

Instance: master
Router ID: 10.255.112.218
Traffic engineering
Restart: Enabled
Restart grace period: 210 sec
Graceful restart helper mode: Enabled
Restart-signaling helper mode: Enabled
Database protection state: Normal
Warning threshold: 70 percent
Non self-generated LSAs: Current 582, Warning 700, Allowed 1000
Ignore time: 30, Reset time: 60
Ignore count: Current 0, Allowed 1
Area: 0.0.0.0
Stub type: Not Stub
Neighbors
Full SPF runs: 70
Backup SPF: Not Needed
show ospf3 overview

(With Database
Protection)
user@host> show ospf3 overview

Instance: master
Router ID: 10.255.112.128
Database protection state: Normal
852
Warning threshold: 80 percent

Non self-generated LSAs: Current 3, Warning 8, Allowed 10
Ignore time: 30, Reset time: 60
Ignore count: Current 0, Allowed 2
Area: 0.0.0.0
Stub type: Not Stub
Neighbors
Full SPF runs: 7
Backup SPF: Not Needed
show ospf overview

extensive
user@host> show ospf overview extensive

Instance: master
Router ID: 1.1.1.103
Full SPF runs: 13, SPF delay: 0.200000 sec
Restart: Disabled
Trace options: lsa
Trace file: /var/log/ospf size 131072 files 10
Area: 0.0.0.0
Stub type: Not Stub
Neighbors
853
show (ospf | ospf3) route

Syntax
Syntax (EX Series

Switch and QFX
Series)
Release Information
Description
Options

<abr | asbr | extern | inter | intra>
<destination>
<instance (default | ipv4-multicast | instance-name)>
<logical-system (default | ipv4-multicast | logical-system-name)>
<network>
<no-backup-coverage>
<router>
<topology (default | ipv4-multicast | topology-name)>
<transit>
<abr | asbr | extern | inter | intra>
<destination>
<instance instance-name
<network>
<no-backup-coverage>
<router>
<topology (default | ipv4-multicast | topology-name)>
<transit>

topology option introduced in Junos OS Release 9.0.
Display the entries in the Open Shortest Path First (OSPF) routing table.
noneDisplay standard information about all entries in the OSPF routing table for all
routing instances and all topologies.

destinationDisplay routes to the specified IP address (with optional destination prefix
length).
abr(Optional) Display routes to area border routers.
asbr(Optional) Display routes to autonomous system border routers.
extern(Optional) Display external routes.
inter(Optional) Display interarea routes.
intra(Optional) Display intra-area routes.
854
instance (default | ipv4-multicast | instance-name)(Optional) Display entries for the
default routing instance, the IPv4 multicast routing instance, or for the specified
routing instance.
logical-system (default | ipv4-multicast | logical-system-name)(Optional) Perform this
operation on the default logical system, the IPv4 multicast logical system, or on a
particular logical system.
network(Optional) Display routes to networks.
no-backup-coverage(Optional) Display routes with no backup coverage.
entries in the routing table for the specified OSPFv3 realm, or address family. Use
the realm option to specify an address family for OSPFv3 other than IPv6 unicast,
which is the default.
router(Optional) Display routes to all routers.
topology (default | ipv4-multicast | topology-name)(OSPFv2 only) (Optional) Display
routes for the default OSPF topology, IPv4 multicast topology, or for a particular
topology.
transit(Optional) (OSPFv3 only) Display OSPFv3 routes to pseudonodes.
Required Privilege
Level
Output Fields
view
show ospf route on page 858

show ospf route detail on page 858
show ospf3 route on page 858
show ospf3 route detail on page 858
show ospf route topology voice on page 859
Table 70 on page 855 list the output fields for the show (ospf | ospf3) route command.
Table 70: show (ospf | ospf3) route Output Fields

Field Name
Field Description
Output Level
Topology
Name of the topology.
All levels
Prefix
All levels
Path type
How the route was learned:
All levels
InterInterarea route
Ext1External type 1 route
Ext2External type 2 route
IntraIntra-area route
855
Table 70: show (ospf | ospf3) route Output Fields (continued)

Field Name
Field Description
Output Level
Route type
The type of routing device from which the route was learned:
All levels
AS BRRoute to AS border router.
Area BRRoute to area border router.
Area/AS BRRoute to router that is both an Area BR and AS BR.
NetworkNetwork router.
RouterRoute to a router that is neither an Area BR nor an AS BR.
Transit(OSPFv3 only) Route to a pseudonode representing a transit network,
LAN, or nonbroadcast multiaccess (NBMA) link.
DiscardRoute to a summary discard.
NH Type
Next-hop type: LSP or IP.
All levels
Metric
Route's metric value.
All levels
NH-interface
(OSPFv3 only) Interface through which the route's next hop is reachable.
All levels
NH-addr
(OSPFv3 only) IPv6 address of the next hop.
All levels
NextHop Interface
(OSPFv2 only) Interface through which the route's next hop is reachable.
All levels
Nexthop addr/label
(OSPFv2 only) If the NH Type is IP, then it is the address of the next hop. If the
NH Type is LSP, then it is the name of the label-switched path.
All levels
Area
Area ID of the route.
detail
Origin
Router from which the route was learned.
detail
Type 7
Route was learned through a not-so-stubby area (NSSA) link-state

advertisement (LSA).
detail
P-bit
Route was learned through NSSA LSA and the propagate bit was set.
detail
Fwd NZ
Forwarding address is nonzero. Fwd NZ is only displayed if the route is learned

through an NSSA LSA.
detail
optional-capability
Optional capabilities propagated in the router LSA. This field is in the output for
intra-area router routes only (when Route Type is Area BR, AS BR, Area/AS BR,
or Router), not for interarea router routes or network routes. Three bits in this
field are defined as follows:
detail
856
0x4 (V)Routing device is at the end of a virtual active link.
0x2 (E)Routing device is an autonomous system boundary router.
0x1 (B)Routing device is an area border router.
Table 70: show (ospf | ospf3) route Output Fields (continued)

Field Name
Field Description
Output Level
priority
The priority assigned to the prefix:
detail
high
medium
low
NOTE: The priority field applies only to routes of type Network.
857
Sample Output
show ospf route
show ospf route detail
user@host> show ospf route

Prefix
Path
Type
10.255.71.12
Intra
10.255.71.13/32
Intra
192.168.222.84/30
Intra
NH
Type
IP
IP
LSP
Metric
1
0
1
NextHop
Interface
fe-0/0/2.0
lo0.0
fe-0/0/2.0
Nexthop
addr/label
192.16.22.86
lsp-ab
user@host> show ospf route detail

Topology default Route Table:
Prefix
10.255.14.174
area 0.0.0.2,
10.255.14.178
area 0.0.0.2,
10.210.1.0/30
area 0.0.0.2,
100.1.1.1/32
area 0.0.0.2,
112.3.1.0/24
area 0.0.0.0,
200.3.3.0/30
area 0.0.0.2,
show ospf3 route
Route
Type
Router
Network
Network
Path
Route
NH
Metric NextHop
Type
Type
Type
Interface
Inter AS BR
IP
210 t1-3/0/1.0
origin 10.255.14.185
Intra Router
IP
200 t3-3/1/3.0
origin 10.255.14.178, optional-capability 0x0
Intra Network
IP
10 t3-3/1/2.0
origin 10.255.14.172, priority medium
Inter Network
IP
210 t1-3/0/1.0
origin 10.255.14.185, priority low
Ext2
Network
IP
0 t1-3/0/1.0
origin 10.255.14.174, priority high
Inter Network
IP
220 t1-3/0/1.0
origin 10.255.14.185, priority high
user@host> show ospf3 route

Prefix
Path
Route
NH
Metric
NextHop
Nexthop
addr/label
Nexthop
Type
Type
Type
Interface
10.255.71.13
Intra Router
IP
1
NH-interface fe-0/0/2.0, NH-addr fe80::290:69ff:fe9b:e002
10.255.71.13;0.0.0.2
10.255.245.1
Intra Router
IP
40 fxp1.1
addr/label
192.168.36.17
area 0.0.0.0, origin 10.255.245.1 optional-capability 0x0,

10.255.245.3
Intra AS BR
IP
1 fxp2.3
192.168.36.34
area 0.0.0.0, origin 10.255.245.3 optional-capability 0x0,

10.255.245.1/32
Intra Network
IP
40 fxp1.1
192.168.36.17
area 0.0.0.0, origin 10.255.245.1, priority high

10.255.245.2/32
Intra Network
IP
0 lo0.0
area 0.0.0.0, origin 10.255.245.2, priority medium
10.255.245.3/32
Intra Network
IP
1 fxp2.3
192.168.36.34
area 0.0.0.0, origin 10.255.245.3, priority low

Intra Transit
IP
1
NH-interface fe-0/0/2.0
192::168:222:84/126 Intra Network
IP
1
NH-interface fe-0/0/2.0
abcd::71:12/128
Intra Network
IP
0
NH-interface lo0.0
abcd::71:13/128
Intra Network
LSP
1
NH-interface fe-0/0/2.0, NH-addr lsp-cd
858
show ospf3 route

detail
user@host> show ospf3 route detail

Prefix
10.255.14.174
NH-interface so-1/2/2.0
Area 0.0.0.0, Origin 10.255.14.174,
10.255.14.178
NH-interface t3-3/1/3.0
Area 0.0.0.0, Origin 10.255.14.178,
10.255.14.185;0.0.0.2
NH-interface t1-3/0/1.0
Area 0.0.0.0, Origin 10.255.14.185
1000:1:1::1/128
Area 0.0.0.0, Origin 10.255.14.174,
1001:2:1::/48
Area 0.0.0.0, Origin 10.255.14.174,
1002:1:7::/48
Area 0.0.0.0, Origin 10.255.14.174,
1002:3:4::/48
Area 0.0.0.0, Origin 10.255.14.174,
abcd::10:255:14:172/128
NH-interface lo0.0
Area 0.0.0.0, Origin 10.255.14.172,
Path
type
Intra
show ospf route

topology voice
user@host show ospf route topology voice

Topology voice Route Table:
Prefix
Path
Route
Type
Type
10.255.8.2
Intra Router
10.255.8.3
Intra Router
10.255.8.1/32
Intra Network
10.255.8.2/32
Intra Network
10.255.8.3/32
Intra Network
192.168.8.0/29
Intra Network
192.168.8.44/30
Intra Network
192.168.8.46/32
Intra Network
192.168.8.48/30
Intra Network
192.168.8.52/30
Intra Network
192.168.9.44/30
Intra Network
192.168.9.45/32
Intra Network
NH
type
IP
Metric
Optional-capability 0x3
Intra Router
IP
200
Optional-capability 0x0
Intra Transit
IP
200
Network
IP
110
Priority low
Ext1
Network
IP
110
Fwd NZ, Priority medium

Ext2
Network
IP
Fwd NZ, Priority low

Ext2
Network
IP
Fwd NZ, Priority high

Intra Network
IP
Inter
Route
type
Area/AS BR
110
Priority low
NH
Metric
Type
IP
1
IP
2
IP
0
IP
1
IP
2
IP
2
IP
2
IP
1
IP
1
IP
2
IP
1
IP
2
NextHop
Interface
so-0/2/0.0
so-0/2/0.0
lo0.0
so-0/2/0.0
so-0/2/0.0
so-0/2/0.0
so-0/2/0.0
so-0/2/0.0
so-0/2/1.0
so-0/2/0.0
so-0/2/0.0
so-0/2/0.0
Nexthop
addr/label
859
show (ospf | ospf3) statistics

Syntax
Syntax (EX Series

Switch and QFX
Series)
Release Information
Description
Options


Display OSPF statistics.
noneDisplay OSPF statistics for all routing instances.
instance instance-name(Optional) Display all statistics for the specified routing instance.

realm (ipv4-multicast | ipv4-unicast | ipv6-multicast)(Optional) (OSPFv3 only) Display
all statistics for the specified OSPFv3 realm, or address family. Use the realm option
to specify an address family for OSPFv3 other than IPv6 unicast, which is the default.
Required Privilege
Level
Related
Documentation
Output Fields
view
clear (ospf | ospf3) statistics
show ospf statistics on page 862

show ospf statistics logical-system all on page 862
show ospf3 statistics on page 863
Table 71 on page 860 lists the output fields for the show (ospf | ospf3) statistics command.
Table 71: show (ospf | ospf3) statistics Output Fields
860
Field Name
Field Description
Packet type
Type of OSPF packet.
Total Sent/Total Received
Total number of packets sent and received.
Last 5 seconds Sent/Last 5

seconds Received
Total number of packets sent and received in the last 5 seconds.
Table 71: show (ospf | ospf3) statistics Output Fields (continued)

Field Name
Field Description
DBDs retransmitted
Total number of database description packets retransmitted, and

number retransmitted in the last 5 seconds.
LSAs flooded
Total number of link-state advertisements flooded, and number

flooded in the last 5 seconds.
LSAs flooded high-prio
Total number of high priority link-state advertisements flooded,

and number flooded in the last 5 seconds.
A link-state advertisement is deemed a high priority if it has changed
since it was last sent.
LSAs retransmitted
Total number of link-state advertisements retransmitted, and

number retransmitted in the last 5 seconds.
LSAs transmitted to nbr
Total number of link-state advertisements transmitted to a neighbor,

and number transmitted in the last 5 seconds.
LSAs requested
Total number of link-state advertisements requested by neighboring

devices, and number requested in the last 5 seconds.
LSAs acknowledged
Total number of link-state advertisements acknowledged, and

number acknowledged in the last 5 seconds.
Flood queue depth
Total number of entries in the extended queue.
Total rexmit entries
Total number of retransmission entries waiting to be sent from the

OSPF routing instance.
db summaries
Total number of database description summaries waiting to be sent

from the OSPF routing instance.
lsreq entries
Total number of link-state request entries waiting to be sent from

the OSPF routing instance.
Receive errors
Number and type of receive errors. Some sample receive errors

include:
mtu mismatches
no interface found
no virtual link found
nssa mismatches
stub area mismatches
subnet mismatches
If there are no receive errors, the output displays none.
861
Sample Output
show ospf statistics
user@host> show ospf statistics

Packet type
Total
Sent
Received
Hello
31
14
DbD
9
10
LSReq
2
2
LSUpdate
8
16
LSAck
9
9
DBDs
LSAs
LSAs
LSAs
LSAs
LSAs
LSAs
Last 5 seconds
Sent
Received
2
2
0
0
0
0
0
0
0
0
retransmitted
:
flooded
:
flooded high-prio :
retransmitted
:
transmitted to nbr:
requested
:
acknowledged
:
Flood queue depth

db summaries
lsreq entries
3,
12,
0,
0,
3,
5,
19,
:
:
:
:
last
last
last
last
last
last
last
5
5
5
5
5
5
5
seconds
seconds
seconds
seconds
seconds
seconds
seconds
:
:
:
:
:
:
:
0
0
0
0
0
0
0
0
0
0
0
Receive errors:
862 no interface found
115923 no virtual link found
show ospf statistics

logical-system all
user@host> show ospf statistics logical-system all

logical-system: C
OSPF instance is not running
----logical-system: B
Packet type
Hello
DbD
LSReq
LSUpdate
LSAck
DBDs
LSAs
LSAs
LSAs
LSAs
LSAs
LSAs
Total
Sent
313740
3
1
2752
1821
Last 5 seconds
Sent
Received
1
0
0
0
0
0
0
0
0
0
Received
313653
2
1
1825
2747
retransmitted
:
flooded
:
flooded high-prio :
retransmitted
:
transmitted to nbr:
requested
:
acknowledged
:
Flood queue depth

db summaries
lsreq entries
:
:
:
:
0,
2741,
10,
0,
2,
1,
1831,
last
last
last
last
last
last
last
5
5
5
5
5
5
5
seconds
seconds
seconds
seconds
seconds
seconds
seconds
:
:
:
:
:
:
:
0
0
0
0
0
0
0
0
0
0
0
Receive errors:
None
-----
862
logical-system: A
Packet type
Hello
DbD
LSReq
LSUpdate
LSAck
DBDs
LSAs
LSAs
LSAs
LSAs
LSAs
LSAs
Total
Sent
313698
2
1
1825
2747
Last 5 seconds
Sent
Received
0
0
0
0
0
0
0
0
0
0
Received
313695
3
1
2752
1821
retransmitted
:
flooded
:
flooded high-prio :
retransmitted
:
transmitted to nbr:
requested
:
acknowledged
:
Flood queue depth

db summaries
lsreq entries
:
:
:
:
0,
1825,
10,
0,
1,
2,
2748,
last
last
last
last
last
last
last
5
5
5
5
5
5
5
seconds
seconds
seconds
seconds
seconds
seconds
seconds
:
:
:
:
:
:
:
0
0
0
0
0
0
0
0
0
0
0
Receive errors:
None
-----
show ospf3 statistics
user@host> show ospf3 statistics

Packet type
Total
Sent
Received
Hello
0
0
DbD
0
0
LSReq
0
0
LSUpdate
0
0
LSAck
0
0
DBDs
LSAs
LSAs
LSAs
LSAs
LSAs
LSAs
Last 5 seconds
Sent
Received
0
0
0
0
0
0
0
0
0
0
retransmitted
:
flooded
:
flooded high-prio :
retransmitted
:
transmitted to nbr:
requested
:
acknowledged
:
Flood queue depth

db summaries
lsreq entries
:
:
:
:
0,
0,
0,
0,
0,
0,
0,
last
last
last
last
last
last
last
5
5
5
5
5
5
5
seconds
seconds
seconds
seconds
seconds
seconds
seconds
:
:
:
:
:
:
:
0
0
0
0
0
0
0
0
0
0
0
Receive errors:
None
863
show poe controller

Syntax
Release Information
Description
Required Privilege
Level
Related
Documentation
Output Fields
show poe controller

Command introduced in Junos OS Release 12.2 for ACX2000 routers.
Display configuration and status of the PoE controllers.
view
show poe interface
request system firmware upgrade poe
Verifying PoE Configuration and Status (CLI Procedure)
Monitoring PoE Power Consumption (CLI Procedure)
Upgrading the PoE Controller Software
show poe controller (EX3200 Switch) on page 866

show poe controller (EX8200 Switch) on page 866
show poe controller (Controller Software Upgrade in Progress) on page 866
show poe controller (ACX2000 Router) on page 866
Table 72 on page 864 lists the output fields for the show poe controller command. Output
Table 72: show poe controller Output Fields
864
Field Name
Field Description
Controller index
PoE controller number:
0 for EX2200, EX3200, standalone EX3300, standalone EX4200 switches,

and ACX2000 routers.
Member ID for switches in an EX3300 Virtual Chassis, EX4200 Virtual Chassis,

or a mixed EX4200 and EX4500 Virtual Chassis.
Slot number for line cards with a PoE controller in an EX6200 or EX8200
switch.
Maximum power
The PoE power budget for the switch or line card. The PoE controller allocates
power to the PoE ports from this budget.
Power consumption
Total amount of power being used by the PoE ports at the time the command
is executed.
Guard Band
Amount of power that has been placed in reserve for power demand spikes and
that cannot be allocated to a PoE interface.
Table 72: show poe controller Output Fields (continued)

Field Name
Field Description
Management
Power management mode: either Class or Static or high-power.

NOTE: The mode high-power is available on only ACX2000 routers.
Status
Status of the PoE controller:
AF_ENHANCEController supports enhanced PoE. The maximum power per
PoE port is 18.6 W in static mode (15.4 W in class mode).
DEVICE FAILSoftware download to the controller has failed or the PoE
controller is not initialized because of a hardware failure.
DOWNLOAD_INITSoftware download to the controller is in the initial phase.
AF_MODEController supports standard IEEE 802.3af. The maximum power
per PoE port is 15.4 W.
AT/AF COMBOController supports a mix of standard IEEE 802.3af and IEEE
802.3at (PoE+) ports. The maximum power per port is 30 W for IEEE 802.3at
(PoE+) ports and 15.4 W for the IEEE 802.3af ports.
AT_MODEController supports IEEE 802.3at (PoE+). The maximum power
per PoE port is 30 W.
Lldp Priority
SW_DOWNLOAD (n%)Software download to the controller is in progress.
Link Layer Discovery Protocol (LLDP) priority operating state. The state can be
Enabled or Disabled.
LLDP priority allows the PoE controller to assign interfaces the power priority
provided by the connected powered device by using LLDP power negotiation
rather than the power priority configured on the switch interface.
865
Sample Output
show poe controller
(EX3200 Switch)
show poe controller

(EX8200 Switch)
show poe controller

(Controller Software
Upgrade in Progress)
user@switch> show poe controller

Controller Maximum
Power
index
power
consumption
0
130.00W
81.20W
Guard
band
10W
Management
Status
Static
AF_ENHANCE

Controller Maximum
Power
index
power
consumption
0
792.00W
603.50W
4
915.00W
781.00W
7
915.00W
0.00W
Guard
band
0W
0W
0W
Management
Status
Class
Class
Class
AT/AF COMBO
AT/AF COMBO
AT/AF COMBO

Controller Maximum
Power
index
power
consumption
Guard
band
Management
Status
Lldp
Priority
Disabled
Lldp
Priority
Disabled
Disabled
Disabled
Lldp
Priority
130.00W
0.00W
0W
Static
AF_ENHANCE
Disabled
8**
130.00W
0.00W
0W
Static
SW_DOWNLOAD(10%)
Disabled
**New PoE software upgrade available.

Use 'request system firmware upgrade poe fpc-slot <slot>'
This procedure will take around 10 minutes (recommended to be performed during
maintenance)
show poe controller

(ACX2000 Router)
user@host> show poe controller

Controller
index
0
866
Maximum
power
Power
consumption
130.0 W
14.2 W
Guard
band
0 W
Management
high-power
Status
Lldp
Priority
UP
show poe telemetries interface (ACX2000 Routers)

Syntax
Release Information
Description
show poe telemetries interface interface-name (entries | all)
Command introduced in Junos OS Release 12.2 for ACX2000 Series Universal Access
Routers.
Display the history of power consumption on the specified interface.
Telemetries must be enabled on the interface before you can display the history of power
consumption.
Options
interface interface-nameDisplay power consumption records for the specified PoE
interface.
(entries | all)Specify the number of power consumption records to display. The most
recent records are displayed.

Required Privilege
Level
Related
Documentation
Output Fields
view
show poe interface
show poe controller on page 864
Troubleshooting PoE Interfaces
show poe telemetries interface ge-0/1/7 all on page 868

show poe telemetries interface ge-0/1/7 2 on page 868
Table 73 on page 867 lists the output fields for the show poe telemetries interface command.
Table 73: show poe telemetries interface Output Fields

Field Name
Field Description
Interface
Name of the interface.
S1 No
Number of the record for the specified interface. Record number 1 is the most
recent.
Timestamp
Date and time when the power-consumption data was gathered.
Power
Amount of power provided by the specified interface at the time the data was
gathered.
Voltage
Maximum voltage provided by the specified interface at the time the data was
gathered.
867
Sample Output
show poe telemetries
interface ge-0/1/7 all
user@switch> show poe telemetries interface ge-0/1/7 all

Interface Sl No
Timestamp
Power
1
Mon May 14 00:45:05 2012 14.2 W
2
Mon May 14 00:44:04 2012 14.2 W
3
Mon May 14 00:43:03 2012 14.2 W
Voltage
53.9 V
53.9 V
53.9 V
show poe telemetries

interface ge-0/1/7 2
user@switch> show poe telemetries interface ge-0/1/7 2

Interface Sl No
Timestamp
Power
1
Mon May 14 00:46:05 2012 14.2 W
2
Mon May 14 00:47:04 2012 14.2 W
Voltage
53.9 V
53.9 V
868
show ptp clock

Syntax
Release Information
Description
Options
Required Privilege
Level
Related
Documentation
Output Fields
show ptp clock

(ACX Series, MX80, MX240, MX480, and MX960 routers) Display the details of the clock
configured on the node.
view
on page 28
show ptp clock on page 871

show ptp clock (ACX Series Routers) on page 871
Table 74 on page 869 lists the output fields for the show ptp clock command. Output fields
are listed in the approximate order in which they appear.
Table 74: show ptp clock Output Fields

Field Name
Field Description
Slot Number
Number of the FPC or MIC slot.
Two-step Clock
Whether the clock provides time information which is a combination of an event message and a
subsequent general message: True or False.
Clock Identity
Clock identity of the slave or client as defined in IEEE 1588.
Total Ports on Device
Total number of PTP ports on the router.
Clock Class
Attribute of an ordinary or boundary clock that denotes the traceability of the time or frequency
distributed by the grandmaster clock.
Clock Accuracy
Indicates the expected accuracy of a clock when it is the grandmaster, or in the event it becomes the
grandmaster.
Log Variance
Represents an estimate of the variations of the local clock when it is not synchronized via PTP to
another clock.
Clock Priority1
Priority value of the clock. Lower value takes precedence.
869
Table 74: show ptp clock Output Fields (continued)

Field Name
Field Description
Clock Priority2
Prioritize the masters to avoid confusion when the Clock Priority1 value is the same for different masters
in a network.
UTC Offset
Offset between International Atomic Time (TAI ) and Coordinated Universal Time (UTC) times. The
value is 34 seconds as of January 2012.
Leap59
When TRUE, the last minute of the current UTC day has only 59 seconds (instead of the 60 SI seconds).
Leap61
When TRUE, the last minute of the current UTC day has 61 seconds (instead of the 60 SI seconds).
Time Traceable
When TRUE, the timescale and the UTC offset are traceable to a primary reference.
Frequency Traceable
When TRUE, frequency determining the timescale is traceable to a primary reference.
Time Source
Time source external to the Precision Time Protocol (PTP), which provides time and/or frequency as
appropriate. The time source is traceable to the international standards laboratories maintaining
clocks that form the basis for the International Atomic Time (TAI) and Universal Coordinated Time
(UTC) timescales. Examples of these are Global Positioning System (GPS), NTP, and National Institute
of Standards and Technology (NIST) timeservers.
Delay Req Sending Time
Interval in seconds between the delay-request messages sent by the slave to the master.
Steps Removed
Number of boundary clocks between the local clock and the foreign master clock.
Slave-only
Set to TRUE, when the system is used in ordinary slave clock mode; otherwise, FALSE.
Parent Id
EUI-64 clock identifier of the immediate upstream master clock.
GMC Id
EUI-64 clock identifier of the grandmaster clock.
GMC Class
Denotes the grandmaster clocks traceability of the distributed time or frequency.
GMC Accuracy
Indicates the expected accuracy of the grandmaster clock.
GMC Variance
Represents an estimate of the variations of the grandmaster clock.
GMC Priority1
Priority1-value of the grandmaster clock.
GMC Priority2
Priority2-value of the grandmaster clock.
870
Sample Output
show ptp clock
user@host> run show ptp clock

Clock Details:
Slot Number
:
Default Data:
Two-step Clock
:
00:05:85:ff:fe:73:ef:d0
Total Ports on Device :
Clock Accuracy
:
Clock Priority1
:
UTC Offset
:
Leap61
:
Frequency Traceable
:
Delay Req Sending Time:
Slave-only
:
Parent Data:
Parent Id
:
GMC Id
:
GMC Accuracy
:
GMC Priority1
:
Global Data:
UTC Offset
:
Leap-61
:
Freq Traceable
:
Time master
:
show ptp clock (ACX

Series Routers)
7
FALSE
Clock Identity :
0
49
128
33
FALSE
FALSE
0
NA
Clock Class
: 255
Log Variance
: -12944
Clock Priority2: 128
Leap59
: FALSE
Time Traceable : FALSE
Time master
: 0
Steps Removed : 1
00:18:0b:ff:ff:20:01:62
00:18:0b:ff:ff:20:01:62
254
0
34
FALSE
FALSE
160
user@host> run show ptp clock

Clock Details:
Slot Number
: 0
Default Data:
Two-step Clock
: FALSE
84:18:88:ff:fe:c0:7a:00
Total Ports on Device : 0
Clock Accuracy
: 34
Clock Priority1
: 128
UTC Offset
: 0
Leap61
: FALSE
Frequency Traceable
: FALSE
Delay Req Sending Time: 0
Slave-only
: NA
Parent Data:
Parent Id
: 00:00:64:ff:fe:01:01:02
GMC Id
: 00:00:64:ff:fe:01:01:02
GMC Accuracy
: 35
GMC Priority1
: 128
Global Data:
UTC Offset
: 0
Leap-61
: FALSE
Freq Traceable
: FALSE
Time source
: 16
GMC Class
GMC Variance
GMC Priority2
: 52
: 11952
: 0
Leap-59
Time traceable
Time Scale
: FALSE
: FALSE
: FALSE
Clock Identity :
Clock Class
:
Log Variance
:
Clock Priority2:
Leap59
:
Time Traceable :
Time Source
:
Steps Removed :
255
15353
128
FALSE
FALSE
0
0
GMC Class
GMC Variance
GMC Priority2
: 80
: 0
: 128
Leap-59
Time tracable
Time Scale
: FALSE
: FALSE
: FALSE
871
show ptp global-information

Syntax
Release Information
Description
Options
Required Privilege
Level
Related
Documentation

Output Fields
show ptp global-information

Show Precision Time Protocol (PTP)related global information.
view
on page 28
show ptp global-information on page 874

Table 75 on page 872 lists the output fields for the show ptp global-information command.
Table 75: show ptp global-information Output Fields

Field Name
Field Description
PTP Global Configuration
Configured PTP, master, and slave parameters.
Domain Number
PTP domain with values from 0 through 127. The default value is 0. Only one PTP domain is supported
at any given point in time.
Transport Encapsulation
Name of the encapsulation type:.
IPv4IPv4 is configured for transmission of PTP packets.
802.3 and IPv4Both IPv4 and Ethernet encapsulation are configured for transmission of PTP
packets.
802.3Ethernet encapsulation is configured for transmission of PTP packets.
Clock mode
Clock mode is either boundary or ordinary.
Priority Level1
Priority value of the clock: 0 through 255. The default is 128. The lower value takes precedence.
Priority Level2
Priority value of the clock: 0 through 255. The default is 128. This value is used to differentiate and
prioritize the master clocks when the priority1-value is the same for different master clocks in a network.
The lower value takes precedence.
Unicast Negotiation
Method by which the announce, synchronization, and delay-response packet rates are negotiated
between the master and the slave or client before a PTP session is established. Unicast negotiation
is enabled or disabled.
ESMC QL From Clock Class
Denotes whether the conversion from clock class to QL is enabled or disabled.
872
Table 75: show ptp global-information Output Fields (continued)

Field Name
Field Description
Clock Class/ESMC QLl
Denotes the user defined clock class to QL conversion.
Slave Parameters
Parameters configured on the slave clock:
Sync IntervalLog mean interval between synchronization messages requested during unicast
negotiation.
Delay Request IntervalLog mean interval between delay-response messages requested during
unicast negotiation.
Announce IntervalLog mean interval between announce messages requested during unicast
negotiation.
Announce TimeoutNumber of announce messages missed and detected by the slave, resulting
in the slave identifying the master as unreachable.
Master Parameters
Grant DurationLength of time a unicast grant is assigned for unicast negotiation.
Parameters configured on the master clock:
Sync IntervalLog mean interval between synchronization messages sent to a configured manual
slave.
Announce IntervalLog mean interval between announce messages sent to a configured manual
slave.
The minimum and maximum parameters below are the minimum and maximum values accepted
during unicast negotiation from remote clients:
Min Announce IntervalLog value, which means that announce messages are sent once every
2
eight seconds.
Max Announce IntervalMaximum acceptable interval between announce messages
Min Sync IntervalMinimum acceptable interval between synchronization messages.
Max Sync IntervalLog value, which means that the maximum synchronization rate is 128
messages per second.
Min Delay Response IntervalMinimum acceptable interval between delay-response messages.
Max Delay Response IntervalMaximum acceptable interval between delay-response messages.
Clock StepSynchronous timing message: one-step or two-step. With two-step, a subsequent
follow-up message is received after the first synchronous message.

Number of Slaves
Number of slaves configured on the router.
Number of Masters
Number of masters configured on the router.
Stateful Ports
Total number of interfaces that are enabled to be stateful or dynamic. A stateful port functions as
both a master port and a slave port.
873
Sample Output
show ptp
global-information
user@host> show ptp global-information

PTP Global Configuration:
Domain number
: 0
Transport Encapsulation : IPv4
Clock mode
: Boundary
Priority Level1
: 128
Priority Level2
: 128
Unicast Negotiation
: Disabled
ESMC QL From Clock Class: Disabled
Clock Class/ESMC QL
: Slave Parameters:
Sync Interval
: not applicable
Delay Request Interval: -6 (64 packets per second)
Announce Interval
: not applicable
Announce Timeout
: 3
Grant Duration
: not applicable
Master Parameters:
Sync Interval
: -6 (64 packets per second)
Announce Interval
: 1 (1 packet every 2 seconds)
Min Announce Interval
: 3 (1 packet every 8 seconds)
Max Announce Interval
: 0 (1 packet per second)
Min Sync Interval
: 0 (1 packet per second)
Max Sync Interval
: -7 (128 packets per second)
Min Delay Response Interval : 0 (1 packet per second)
Max Delay Response Interval : -7 (128 packets per second)
Clock Step
: one-step
Number of Slaves
Number of Masters
Stateful Ports
874
: 1
: 1
: 2
show ptp lock-status

Syntax
Release Information
Description
(ACX Series, MX80, MX240, MX480, and MX960 routers) Display information about the
lock status of the slave clock. The output verifies whether the slave clock is aligned to
the grandmaster (master clock) or not.
Options
detailDisplay detailed information about the lock status of the slave clock.
Required Privilege
Level
view
Related
Documentation
on page 28
show ptp lock-status on page 876

show ptp lock-status (ACX Series Routers) on page 876
show ptp lock-status detail (ACX Series Routers) on page 876
Output Fields
Table 76 on page 875 lists the output fields for the show ptp lock-status command. Output
Table 76: show ptp lock-status Output Fields

Field Name
Field Description
Lock State
State of the slave clock with respect to its master clock:
Freerun
Holdover
Phase Aligned
Acquiring
Initializing
Freq locked
Phase offset
Time offset information of a slave clock with respect to its master clock. Precision of this time offset
is 1 nanosecond.
Selected Master Details
Details include the following:
Upstream Master addressThe address of the remote master from which the slave acquires the
clock. On ACX Series routers, this field is displayed only in Junos OS Release 12.3 and earlier.
Master Source PortThe address of the master clock when PTP over IPv4 is configured and the
multicast MAC address of the source when PTP over Ethernet is configured. This field is displayed
for ACX Series routers instead of the Upstream Master address field starting with Junos OS Release
12.3X51.
Slave interfaceThe slave interface on this router corresponding to the master clock above.
875
Sample Output
user@host> run show ptp lock-status

Lock Status:
Lock State
Phase offset

(ACX Series Routers)
user@host> show ptp lock-status

Lock Status:
Lock State
Phase offset

detail (ACX Series
Routers)
: 5 (PHASE ALIGNED)
: 0.000000001 sec
: 1 (FREERUN)
: 0.000000869 sec
user@host> show ptp lock-status detail

Lock Status:
Lock State
Phase offset
: 5 (PHASE ALIGNED)
: 0.000000030 sec
Selected Master Details:

Master Source Port : 8d:25:98:ce:5f:37:11:91:00:01
Slave interface
: ge-0/1/5.0
876
show ptp statistics

Syntax
Release Information
Description
Options
show ptp statistics

<brief | detail>

Display information about Precision Time Protocol (PTP) statistics.
briefDisplay brief statistics about the operation of configured PTP clocks.
detailDisplay detailed statistics about the operation of configured PTP clocks.
Required Privilege
Level
Related
Documentation
Output Fields
view
on page 28
show ptp statistics on page 878

show ptp statistics detail on page 878
Table 77 on page 877 lists the output fields for the show ptp statistics command. Output
Table 77: show ptp statistics Output Fields

Field Name
Field Description
Local Address
IP address of the local PTP master and slave interfaces. This field is displayed on ACX Series routers
running Junos OS Release 12.3 and earlier, and on MX Series routers only.
Local Clock
Interface name on which the local PTP master and slave are configured. This field is displayed on
ACX Series routers running Junos OS Release 12.3X51 and later.
Remote Address
IP address of the remote PTP master and slave interfaces. This field is displayed on ACX Series routers
running Junos OS Release 12.3 and earlier, and on MX Series routers only.
Remote Clock
MAC address of the remote PTP master and slave interfaces. This field is displayed on ACX Series
routers running Junos OS Release 12.3X51 and later.
Role
Function performed by an Ethernet interface configured as a slave or master.
Stream
Stream ID uniquely identifies the connection between one master and one slave.
Received
1588v2 packets received by the master or slave interface.
Transmitted
1588v2 packets transmitted by the master or slave interface.
877
Table 77: show ptp statistics Output Fields (continued)

Field Name
Field Description
Signalling
Packet count for signalling messages:
Announce
Sync
Delay
Error
RxNumber of packets received.
TxNumber of packets transmitted.
Packet count for announce messages:
Packet count for synchronization messages:
Packet count for delay request or response messages:
Packet count for signal loss errors:
RxNumber of packets received with errors.
TxNumber of packets transmitted with errors.
Sample Output
show ptp statistics
show ptp statistics

detail
878
user@host> show ptp statistics

Local Clock
Remote Clock
Role
ge-0/1/0.7
01:1B:19:00:00:00
S
ge-2/1/3.4
01:80:C2:00:00:0E
M
user@host> show ptp statistics detail

Local Address
Remote Address
10.10.20.58
10.10.20.50
Signalling
Announce
Rx:
804
11977
Tx:
808
0
Local Address
Remote Address
50.50.50.58
50.50.50.59
Signalling
Announce
Rx:
0
0
Tx:
0
0
Stream
0
4
Received
120974887
0
Transmitted
60257569
0
Role Stream
Received Transmitted
Slave
0
120974887
60257569
Sync
Delay
Error
60252158
60252000
0
0
60257029
0
Role Stream
Received Transmitted
Master
4
0
0
Sync
Delay
Error
0
3166732
0
0
3166732
0
show route
Syntax
Syntax (EX Series

Switches)
Release Information
Description
Options
show route
<all>
<destination-prefix>
<private>
show route
<all>
<private>

Option private introduced in Junos OS Release 9.5.
Option private introduced in Junos OS Release 9.5 for EX Series switches.
Display the active entries in the routing tables.
noneDisplay brief information about all active entries in the routing tables.
all(Optional) Display information about all routing tables, including private, or internal,
routing tables.
destination-prefix(Optional) Display active entries for the specified address or range
of addresses.

private(Optional) Display information only about all private, or internal, routing tables.
Required Privilege
Level
Related
Documentation
view
Example: Configuring RIP
Example: Configuring RIPng
Example: Configuring IS-IS
Examples: Configuring Internal BGP Peering
Examples: Configuring External BGP Peering
Examples: Configuring OSPF Routing Policy
show route on page 883

show route destination-prefix on page 883
show route extensive on page 883
879
Output Fields
Table 78 on page 880 describes the output fields for the show route command. Output
Table 78: show route Output Fields

Field Name
Field Description
routing-table-name
Name of the routing table (for example, inet.0).
number destinations
Number of destinations for which there are routes in the routing table.
number routes
Number of routes in the routing table and total number of routes in the following states:
active (routes that are active).
holddown (routes that are in the pending state before being declared inactive). A holddown route
was once the active route and is no longer the active route. The route is in the holddown state
because a protocol still has interest in the route, meaning that the interest bit is set. A protocol
might have its interest bit set on the previously active route because the protocol is still advertising
the route. The route will be deleted after all protocols withdraw their advertisement of the route
and remove their interest bit. A persistent holddown state often means that the interested protocol
is not releasing its interest bit properly.
However, if you have configured advertisement of multiple routes (with the add-path or
advertise-inactive statement), the holddown bit is most likely set because BGP is advertising the
route as an active route. In this case, you can ignore the holddown state because nothing is wrong.
destination-prefix
hidden (routes that are not used because of a routing policy).
Route destination (for example:10.0.0.1/24). Sometimes the route information is presented in another
format, such as:
MPLS-label (for example, 80001).
interface-name (for example, ge-1/0/2).
neighbor-address:control-word-status:encapsulation type:vc-id :source (Layer 2 circuit only. For example,
10.1.1.195:NoCtrlWord:1:1:Local/96):
neighbor-addressAddress of the neighbor.
control-word-statusWhether the use of the control word has been negotiated for this virtual
circuit: NoCtrlWord or CtrlWord.
encapsulation typeType of encapsulation, represented by a number: (1) Frame Relay DLCI, (2)
ATM AAL5 VCC transport, (3) ATM transparent cell transport, (4) Ethernet, (5) VLAN Ethernet,
(6) HDLC, (7) PPP, (8) ATM VCC cell transport, (10) ATM VPC cell transport.
[ protocol, preference ]
vc-idVirtual circuit identifier.
sourceSource of the advertisement: Local or Remote.
Protocol from which the route was learned and the preference value for the route.
+A plus sign indicates the active route, which is the route installed from the routing table into the
forwarding table.
- A hyphen indicates the last active route.
*An asterisk indicates that the route is both the active and the last active route. An asterisk before
a to line indicates the best subpath to the route.
In every routing metric except for the BGP LocalPref attribute, a lesser value is preferred. In order to
use common comparison routines, Junos OS stores the 1's complement of the LocalPref value in the
Preference2 field. For example, if the LocalPref value for Route 1 is 100, the Preference2 value is -101.
If the LocalPref value for Route 2 is 155, the Preference2 value is -156. Route 2 is preferred because it
has a higher LocalPref value and a lower Preference2 value.
880
Table 78: show route Output Fields (continued)

Field Name
Field Description
weeks:days
hours:minutes:seconds
How long the route been known (for example, 2w4d 13:11:14, or 2 weeks, 4 days, 13 hours, 11 minutes,
and 14 seconds).
metric
Cost value of the indicated route. For routes within an AS, the cost is determined by the IGP and the
individual protocol metrics. For external routes, destinations, or routing domains, the cost is determined
by a preference value.
localpref
Local preference value included in the route.
from
Interface from which the route was received.
AS path
AS path through which the route was learned. The letters at the end of the AS path indicate the path
origin, providing an indication of the state of the route at the point at which the AS path originated:
IIGP.
EEGP.
?Incomplete; typically, the AS path was aggregated.
When AS path numbers are included in the route, the format is as follows:
[ ]Brackets enclose the local AS number associated with the AS path if more than one AS number
is configured on the routing device, or if AS path prepending is configured.
{ }Braces enclose AS sets, which are groups of AS numbers in which the order does not matter.
A set commonly results from route aggregation. The numbers in each AS set are displayed in
ascending order.
( )Parentheses enclose a confederation.
( [ ] )Parentheses and brackets enclose a confederation set.
NOTE: In Junos OS Release 10.3 and later, the AS path field displays an unrecognized attribute and
associated hexadecimal value if BGP receives attribute 128 (attribute set) and you have not configured
an independent domain in any routing instance.
validation-state
(BGP-learned routes) Validation status of the route:
InvalidIndicates that the prefix is found, but either the corresponding AS received from the EBGP
peer is not the AS that appears in the database, or the prefix length in the BGP update message is
longer than the maximum length permitted in the database.
to
UnknownIndicates that the prefix is not among the prefixes or prefix ranges in the database.
ValidIndicates that the prefix and autonomous system pair are found in the database.
Next hop to the destination. An angle bracket (>) indicates that the route is the selected route.
If the destination is Discard, traffic is dropped.
881
Table 78: show route Output Fields (continued)

Field Name
Field Description
via
Interface used to reach the next hop. If there is more than one interface available to the next hop, the
interface that is actually used is followed by the word Selected. This field can also contain the following
information:
WeightValue used to distinguish primary, secondary, and fast reroute backup routes. Weight
information is available when MPLS label-switched path (LSP) link protection, node-link protection,
or fast reroute is enabled, or when the standby state is enabled for secondary paths. A lower weight
value is preferred. Among routes with the same weight value, load balancing is possible.
BalanceBalance coefficient indicating how traffic of unequal cost is distributed among next hops
when a routing device is performing unequal-cost load balancing. This information is available
when you enable BGP multipath load balancing.
882
lsp-path-nameName of the LSP used to reach the next hop.
label-actionMPLS label and operation occurring at the next hop. The operation can be pop (where
a label is removed from the top of the stack), push (where another label is added to the label stack),
or swap (where a label is replaced by another label).
Sample Output
show route
user@host> show route

inet.0: 11 destinations, 12 routes (11 active, 0 holddown, 0 hidden)
1:65500:1:10.0.0.20/240
*[MVPN/70] 19:53:41, metric2 1
Indirect
1:65500:1:10.0.0.40/240
*[BGP/170] 19:53:29, localpref 100, from 10.0.0.30
AS path: I
> to 10.0.24.4 via lt-0/3/0.24, label-switched-path
[BGP/170] 19:53:26, localpref 100, from 10.0.0.33
AS path: I
1:65500:1:10.0.0.60/240
AS path: I
AS path: I
show route
destination-prefix
toD
toD
toF
toF
user@host> show route 172.16.0.0/12

172.16.0.0/12
show route extensive
*[Static/5] 2w4d 12:54:27

> to 192.168.167.254 via fxp0.0
user@host> show route extensive

v1.mvpn.0: 5 destinations, 8 routes (5 active, 1 holddown, 0 hidden)
1:65500:1:10.0.0.40/240 (1 entry, 1 announced)
*BGP
Preference: 170/-101
PMSI: Flags 0x0: Label[0:0:0]: PIM-SM: Sender 10.0.0.40 Group 225.1.1.1
Next hop type: Indirect
Address: 0x92455b8
Next-hop reference count: 2
Source: 10.0.0.30
Protocol next hop: 10.0.0.40
Indirect next hop: 2 no-forward
State: <Active Int Ext>
Local AS: 65500 Peer AS: 65500
Age: 3 Metric2: 1
Task: BGP_65500.10.0.0.30+179
Announcement bits (2): 0-PIM.v1 1-mvpn global task
AS path: I (Originator) Cluster list: 10.0.0.30
AS path: Originator ID: 10.0.0.40
Communities: target:65520:100
Import Accepted
Localpref: 100
Router ID: 10.0.0.30
Primary Routing Table bgp.mvpn.0
Indirect next hops: 1
Protocol next hop: 10.0.0.40 Metric: 1
883

Indirect path forwarding next hops: 1
Next hop type: Router
Next hop: 10.0.24.4 via lt-0/3/0.24 weight 0x1
10.0.0.40/32 Originating RIB: inet.3
Metric: 1
Node path count: 1
Forwarding nexthops: 1
Nexthop: 10.0.24.4 via lt-0/3/0.24
884
show route active-path

Syntax
Syntax (EX Series

Switches)
Release Information
Description
Options


Display all active routes for destinations. An active route is a route that is selected as the
best path. Inactive routes are not displayed.
noneDisplay all active routes.
brief | detail | extensive | terse(Optional) Display the specified level of output. If you do
not specify a level of output, the system defaults to brief.


Required Privilege
Level
Output Fields
view
show route active-path on page 886

show route active-path brief on page 886
show route active-path detail on page 886
show route active-path extensive on page 887
show route active-path terse on page 889
For information about output fields, see the output field tables for the show route
command, the show route detail command, the show route extensive command, or the
show route terse command.
885
Sample Output
user@host> show route active-path

10.255.70.19/32
10.255.71.50/32
*[Direct/0] 21:33:52
> via lo0.0
*[IS-IS/15] 00:18:13, metric 10
> to 100.1.2.1 via so-2/1/3.0
*[Direct/0] 00:18:36
> via so-2/1/3.0
*[Local/0] 00:18:41
Local via so-2/1/3.0
*[Direct/0] 21:33:52
> via fxp0.0
*[Local/0] 21:33:52
Local via fxp0.0
100.1.2.0/24
100.1.2.2/32
192.168.64.0/21
192.168.70.19/32

brief
The output for the show route active-path brief command is identical to that for the show
route active-path command. For sample output, see show route active-path on page 886.

detail
user@host> show route active-path detail

10.255.70.19/32 (1 entry, 1 announced)
*Direct Preference: 0
Next hop type: Interface
Next hop: via lo0.0, selected
State: Active Int
Local AS:
200
Age: 21:37:10
Task: IF
Announcement bits (3): 2-IS-IS 5-Resolve tree 2 6-Resolve tree 3
AS path: I
10.255.71.50/32 (1 entry, 1 announced)
*IS-IS Preference: 15
Level: 1
Next hop type: Router, Next hop index: 397
Next hop: 100.1.2.1 via so-2/1/3.0, selected
State: Active Int
Local AS:
200
Age: 21:31
Metric: 10
Task: IS-IS
Announcement bits (4): 0-KRT 2-IS-IS 5-Resolve tree 2 6-Resolve
tree 3
AS path: I
100.1.2.0/24 (1 entry, 1 announced)
886
Next hop: via so-2/1/3.0, selected

State: Active Int
Local AS:
200
Age: 21:54
Task: IF
AS path: I
*Local Preference: 0
Next hop type: Local
Interface: so-2/1/3.0
State: Active NoReadvrt Int
Local AS:
200
Age: 21:59
Task: IF
Announcement bits (2): 5-Resolve tree 2 6-Resolve tree 3
AS path: I
192.168.64.0/21 (1 entry, 1 announced)
Next hop: via fxp0.0, selected
State: Active Int
Local AS:
200
Age: 21:37:10
Task: IF
AS path: I
192.168.70.19/32 (1 entry, 1 announced)
Interface: fxp0.0
Local AS:
200
Age: 21:37:10
Task: IF
AS path: I

extensive
user@host> show route active-path extensive

10.255.70.19/32 (1 entry, 1 announced)
TSI:
IS-IS level 1, LSP fragment 0
State: Active Int
Local AS:
200
Age: 21:39:47
Task: IF
887
AS path: I
10.255.71.50/32 (1 entry, 1 announced)
TSI:
KRT in-kernel 10.255.71.50/32 -> {100.1.2.1}
*IS-IS Preference: 15
Level: 1
State: Active Int
Local AS:
200
Age: 24:08
Metric: 10
Task: IS-IS
Announcement bits (4): 0-KRT 2-IS-IS 5-Resolve tree 2 6-Resolve
tree 3
AS path: I
TSI:
State: Active Int
Local AS:
200
Age: 24:31
Task: IF
AS path: I
Local AS:
200
Age: 24:36
Task: IF
AS path: I
192.168.64.0/21 (1 entry, 1 announced)
State: Active Int
Local AS:
200
Age: 21:39:47
Task: IF
AS path: I
192.168.70.19/32 (1 entry, 1 announced)
888
*Local

terse
Preference: 0
Interface: fxp0.0
Local AS:
200
Age: 21:39:47
Task: IF
AS path: I
user@host> show route active-path terse

A
*
*
*
*
*
*
Destination
10.255.70.19/32
10.255.71.50/32
100.1.2.0/24
100.1.2.2/32
192.168.64.0/21
192.168.70.19/32
P Prf
D
0
I 15
D
0
L
0
D
0
L
0
Metric 1
10
Metric 2
Next hop
>lo0.0
>100.1.2.1
>so-2/1/3.0
Local
>fxp0.0
Local
AS path
889
show route advertising-protocol

Syntax
Release Information
Description
Options
show route advertising-protocol protocol neighbor-address


Display the routing information as it has been prepared for advertisement to a particular
neighbor of a particular dynamic routing protocol.

neighbor-addressAddress of the neighboring router to which the route entry is being
transmitted.
protocolProtocol transmitting the route:
Required Privilege
Level
Related
Documentation
Output Fields
890
bgpBorder Gateway Protocol
dvmrpDistance Vector Multicast Routing Protocol
msdpMulticast Source Discovery Protocol
pimProtocol Independent Multicast
ripRouting Information Protocol
ripngRouting Information Protocol next generation
Routes displayed are routes that the routing table has exported into the routing protocol
and that have been filtered by the associated protocol's export routing policy statements.
view
Example: Configuring the MED Attribute Directly
show route advertising-protocol bgp (Layer 3 VPN) on page 893

show route advertising-protocol bgp detail on page 893
show route advertising-protocol bgp detail (Layer 2 VPN) on page 893
show route advertising-protocol bgp detail (Layer 3 VPN) on page 893
show route advertising-protocol bgp extensive all (Next Hop Self with RIB-out IP
Address) on page 894
Table 79 on page 891 lists the output fields for the show route advertising-protocol
Table 79: show route advertising-protocol Output Fields

Field Name
Field Description
Level of Output
routing-table-name
Name of the routing tablefor example, inet.0.
All levels
number
destinations
All levels
number routes
Number of routes in the routing table and total number of routes in the following
states:
All levels
active (routes that are active)
holddown (routes that are in the pending state before being declared inactive)
hidden (routes that are not used because of a routing policy)
Prefix
Destination prefix.
brief none
destination-prefix
(entry , announced)
Destination prefix. The entry value is the number of routes for this destination,
and the announced value is the number of routes being announced for this
destination.
detail extensive
BGP group and type
BGP group name and type (Internal or External).
detail extensive
Route Distinguisher
Unique 64-bit prefix augmenting each IP subnet.
detail extensive
Advertised Label
Incoming label advertised by the LDP. When an IP packet enters a label-switched

path (LSP), the ingress router examines the packet and assigns it a label based
on its destination, placing the label in the packet's header. The label transforms
the packet from one that is forwarded based on its IP routing information to
one that is forwarded based on information associated with the label.
detail extensive
Label-Base, range
First label in a block of labels and label block size. A remote PE router uses this
first label when sending traffic toward the advertising PE router.
detail extensive
VPN Label
Virtual private network (VPN) label. Packets are sent between CE and PE routers
by advertising VPN labels. VPN labels transit over either an RSVP or an LDP
LSP tunnel.
detail extensive
Nexthop
Next hop to the destination. An angle bracket (>) indicates that the route is the
selected route.
All levels
If the next-hop advertisement to the peer is Self, and the RIB-out next hop is a
specific IP address, the RIB-out IP address is included in the extensive output.
See show route advertising-protocol bgp extensive all (Next Hop Self with RIB-out
IP Address) on page 894.
MED
Multiple exit discriminator value included in the route.
brief
Lclpref or Localpref
All levels
891
Table 79: show route advertising-protocol Output Fields (continued)

Field Name
Field Description
Level of Output
AS path
AS path through which the route was learned. The letters at the end of the AS
path indicate the path origin, providing an indication of the state of the route at
the point at which the AS path originated:
All levels
IIGP.
EEGP.
[ ]Brackets enclose the local AS number associated with the AS path if
configured on the router, or if AS path prepending is configured.
{ }Braces enclose AS sets, which are groups of AS numbers in which the
order does not matter. A set commonly results from route aggregation. The
numbers in each AS set are displayed in ascending order.
NOTE: In Junos OS Release 10.3 and later, the AS path field displays an
unrecognized attribute and associated hexadecimal value if BGP receives
attribute 128 (attribute set) and you have not configured an independent domain
in any routing instance.
Communities
Community path attribute for the route. See the output field table for the show
route detail command for all possible values for this field.
detail extensive
AIGP
Accumulated interior gateway protocol (AIGP) BGP attribute.
detail extensive
Attrset AS
Number, local preference, and path of the autonomous system (AS) that
originated the route. These values are stored in the Attrset attribute at the
originating router.
detail extensive
Layer2-info: encaps
Layer 2 encapsulation (for example, VPLS).
detail extensive
control flags
Control flags: none or Site Down.
detail extensive
mtu
Maximum transmission unit (MTU) of the Layer 2 circuit.
detail extensive
892
Sample Output
show route
advertising-protocol
bgp (Layer 3 VPN)
user@host> show route advertising-protocol bgp 10.255.14.171

VPN-A.inet.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)
Prefix
Nexthop
MED
Lclpref AS path
10.255.14.172/32
Self
1
100 I
VPN-B.inet.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)
Prefix
Nexthop
MED
Lclpref AS path
10.255.14.181/32
Self
2
100 I
show route
bgp detail
user@host> show route advertising-protocol bgp 111.222.1.3 detail

bgp20.inet.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden)
111.222.1.11/32 (1 entry, 1 announced)
BGP group pe-pe type Internal
Route Distinguisher: 111.255.14.11:69
Advertised Label: 100000
next hop: Self
Localpref: 100
AS path: 2 I
AIGP 210
BGP group pe-pe type Internal
Advertised Label: 100000
Next hop: Self
Localpref: 100
AS path: 2 I
AIGP 210
show route
bgp detail (Layer 2
VPN)

vpn-a.l2vpn.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
192.168.16.1:1:1:1/96 (1 entry, 1 announced)
BGP group int type Internal
Label-base : 32768, range : 3
Nexthop: Self
Localpref: 100
AS path: I
AIGP 210
Layer2-info: encaps:VLAN, control flags:, mtu:
show route

vpna.inet.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)
* 10.49.0.0/30 (1 entry, 1 announced)
893
bgp detail (Layer 3

VPN)
BGP group ibgp type Internal

VPN Label: 101264
Nexthop: Self
Localpref: 100
AS path: I
AIGP 210
AttrSet AS: 100
Localpref: 100
AS path: I
...
show route
bgp extensive all (Next
Hop Self with RIB-out
IP Address)
user@host> show route advertising-protocol bgp 200.0.0.2 170.0.1.0/24 extensive all

170.0.1.0/24 (2 entries, 1 announced)
BGP group eBGP-INTEROP type External
Nexthop: Self (rib-out 10.100.3.2)
AS path: [4713] 200 I
...
894
show route all

Syntax
Syntax (EX Series

Switches)
Release Information
Description
Options
show route all

show route all

Display information about all routes in all routing tables, including private, or internal,
tables.
noneDisplay information about all routes in all routing tables, including private, or
internal, tables.

Required Privilege
Level
Output Fields
view
show route all on page 896

In Junos OS Release 9.5 and later, only the output fields for the show route all command
display all routing tables, including private, or hidden, routing tables. The output field
table of the show route command does not display entries for private, or hidden, routing
tables in Junos OS Release 9.5 and later.
895
Sample Output
show route all
The following example displays a snippet of output from the show route command and
then displays the same snippet of output from the show route all command:
user@host> show route
mpls.0: 7 destinations, 7 routes (5 active, 0 holddown, 2 hidden)
Restart Complete
0
*[MPLS/0] 2d 02:24:39, metric 1
Receive
1
*[MPLS/0] 2d 02:24:39, metric 1
Receive
2
*[MPLS/0] 2d 02:24:39, metric 1
Receive
800017
*[VPLS/7] 1d 14:00:16
> via vt-3/2/0.32769, Pop
800018
*[VPLS/7] 1d 14:00:26
> via vt-3/2/0.32772, Pop
user@host> show route all
Restart Complete
0
*[MPLS/0] 2d 02:19:12, metric 1
Receive
1
*[MPLS/0] 2d 02:19:12, metric 1
Receive
2
*[MPLS/0] 2d 02:19:12, metric 1
Receive
800017
*[VPLS/7] 1d 13:54:49
> via vt-3/2/0.32769, Pop
800018
*[VPLS/7] 1d 13:54:59
> via vt-3/2/0.32772, Pop
vt-3/2/0.32769
[VPLS/7] 1d 13:54:49
Unusable
vt-3/2/0.32772
[VPLS/7] 1d 13:54:59
Unusable
896
show route aspath-regex

Syntax
Syntax (EX Series

Switches)
Release Information
Description
Options
show route aspath-regex regular-expression

show route aspath-regex regular-expression

Display the entries in the routing table that match the specified autonomous system
(AS) path regular expression.
regular-expressionRegular expression that matches an entire AS path.

You can specify a regular expression as:
An individual AS number
A period wildcard used in place of an AS number
An AS path regular expression that is enclosed in parentheses
You also can include the operators described in the table of AS path regular expression
operators in the Junos Policy Framework Configuration Guide. The following list summarizes
these operators:
{m,n}At least m and at most n repetitions of the AS path term.
{m}Exactly m repetitions of the AS path term.
{m,}m or more repetitions of the AS path term.
*Zero or more repetitions of an AS path term.
+One or more repetitions of an AS path term.
?Zero or one repetition of an AS path term.
aspath_term | aspath_termMatch one of the two AS path terms.
When you specify more than one AS number or path term, or when you include an
operator in the regular expression, enclose the entire regular expression in quotation
marks. For example, to match any path that contains AS number 234, specify the
following command:
show route aspath-regex ".* 234 .*"
Required Privilege
Level
view
897
Output Fields
show route aspath-regex (Matching a Specific AS Number) on page 898

show route aspath-regex (Matching Any Path with Two AS Numbers) on page 898
For information about output fields, see the output field table for the show route
command.
Sample Output
show route
aspath-regex
(Matching a Specific
AS Number)
user@host> show route aspath-regex 65477

111.222.1.0/25
111.222.1.128/25

AS Path: [65477] ({65488 65535}) IGP
to 111.222.18.225 via fpa0.0(111.222.18.233)
*[IS-IS/15] 09:15:37, metric 37, tag 1
to 111.222.18.225 via fpa0.0(111.222.18.233)
AS Path: [65477] ({65488 65535}) IGP
to 111.222.18.225 via fpa0.0(111.222.18.233)
...
show route
aspath-regex
(Matching Any Path
with Two AS Numbers)
user@host> show route aspath-regex ?.* 234 3561 .*?

9.20.0.0/17
12.10.231.0/24
24.64.32.0/19

AS Path: [666] 234 3561 2685 2686 Incomplete
to 192.156.169.1 via 192.156.169.14(so-0/0/0)
AS Path: [666] 234 3561 5696 7369 IGP
to 192.156.169.1 via 192.156.169.14(so-0/0/0)
AS Path: [666] 234 3561 6327 IGP
to 192.156.169.1 via 192.156.169.14(so-0/0/0)
...
898
show route best

Syntax
Syntax (EX Series

Switches)
Release Information
Description
Options
show route best destination-prefix

show route best destination-prefix

Display the route in the routing table that is the best route to the specified address or
range of addresses. The best route is the longest matching route.

destination-prefixAddress or range of addresses.

Required Privilege
Level
Output Fields
view
show route best on page 900

show route best detail on page 900
show route best extensive on page 901
show route best terse on page 901
899
Sample Output
show route best
user@host> show route best 10.255.70.103

Restart Complete
10.255.70.103/32
*[OSPF/10] 1d 13:19:20, metric 2
> to 10.31.1.6 via ge-3/1/0.0
via so-0/3/0.0
Restart Complete
10.255.70.103/32
*[RSVP/7] 1d 13:20:13, metric 2
> via so-0/3/0.0, label-switched-path green-r1-r3
private1__.inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0 hidden)
10.0.0.0/8
*[Direct/0] 2d 01:43:34
> via fxp2.0
[Direct/0] 2d 01:43:34
> via fxp1.0
show route best detail
user@host> show route best 10.255.70.103 detail

Restart Complete
10.255.70.103/32 (1 entry, 1 announced)
*OSPF
Preference: 10
Next hop: 10.31.1.6 via ge-3/1/0.0, selected
Next hop: via so-0/3/0.0
State: <Active Int>
Local AS:
69
Age: 1d 13:20:06
Metric: 2
Area: 0.0.0.0
Task: OSPF
Announcement bits (2): 0-KRT 3-Resolve tree 2
AS path: I
Restart Complete
10.255.70.103/32 (1 entry, 1 announced)
State: <FlashAll>
*RSVP
Preference: 7
Next hop: via so-0/3/0.0 weight 0x1, selected
Label-switched-path green-r1-r3
Label operation: Push 100016
State: <Active Int>
Local AS:
69
Age: 1d 13:20:59
Metric: 2
Task: RSVP
Announcement bits (1): 1-Resolve tree 2
AS path: I
private1__inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0 hidden)
900

State: <Active Int>
Age: 2d 1:44:20
Task: IF
AS path: I
Direct Preference: 0
State: <NotBest Int>
Inactive reason: No difference
Age: 2d 1:44:20
Task: IF
AS path: I
show route best

extensive
The output for the show route best extensive command is identical to that for the show
route best detail command. For sample output, see show route best detail on page 900.
show route best terse
user@host> show route best 10.255.70.103 terse

Restart Complete
A Destination
* 10.255.70.103/32
P Prf
O 10
Metric 1
2
Metric 2
Next hop
>10.31.1.6
so-0/3/0.0
AS path

Restart Complete
A Destination
* 10.255.70.103/32
P Prf
R
7
Metric 1
2
Metric 2
Next hop
>so-0/3/0.0
AS path

A Destination
* 10.0.0.0/8
P Prf
D
0
D
0
Metric 1
Metric 2
Next hop
>fxp2.0
>fxp1.0
AS path
901
show route brief

Syntax
Syntax (EX Series

Switches)
show route brief

show route brief
Release Information

Description
Display brief information about the active entries in the routing tables.
Options
noneDisplay all active entries in the routing table.

of addresses.

Required Privilege
Level
Output Fields
902
view
show route brief on page 903

For information about output fields, see the Output Field table of the show route
command.
Sample Output
show route brief
user@host> show route brief

0.0.0.0/0
*[Static/5] 1w5d 20:30:29

Discard
10.255.245.51/32
*[Direct/0] 2w4d 13:11:14
> via lo0.0
172.16.0.0/12
*[Static/5] 2w4d 13:11:14
> to 192.168.167.254 via fxp0.0
192.168.0.0/18
*[Static/5] 1w5d 20:30:29
> to 192.168.167.254 via fxp0.0
192.168.40.0/22
*[Static/5] 2w4d 13:11:14
> to 192.168.167.254 via fxp0.0
192.168.64.0/18
*[Static/5] 2w4d 13:11:14
> to 192.168.167.254 via fxp0.0
192.168.164.0/22
*[Direct/0] 2w4d 13:11:14
> via fxp0.0
192.168.164.51/32 *[Local/0] 2w4d 13:11:14
Local via fxp0.0
207.17.136.192/32 *[Static/5] 2w4d 13:11:14
> to 192.168.167.254 via fxp0.0
green.inet.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
100.101.0.0/16
*[Direct/0] 1w5d 20:30:28
> via fe-0/0/3.0
100.101.2.3/32
*[Local/0] 1w5d 20:30:28
Local via fe-0/0/3.0
224.0.0.5/32
*[OSPF/10] 1w5d 20:30:29, metric 1
MultiRecv
903
show route community

Syntax
show route community as-number:community-value

Syntax (EX Series

Switches)
show route community as-number:community-value

Release Information

Description
Display the route entries in each routing table that are members of a Border Gateway
Protocol (BGP) community.
Options
as-number:community-valueOne or more community identifiers. as-number is the AS
number, and community-value is the community identifier. When you specify more
than one community identifier, enclose the identifiers in double quotation marks.
Community identifiers can include wildcards.

Required Privilege
Level
Related
Documentation
Output Fields
904
Specifying the community option displays all routes matching the community found
within the routing table. The community option does not limit the output to only the
routes being advertised to the neighbor after any egress routing policy.
view
show route detail on page 914
show route community on page 905

command, the show route detail command, the show route extensive command, or
the show route terse command.
Sample Output
show route community
user@host> show route community 234:80

4.0.0.0/8
6.0.0.0/8
9.2.0.0/16

AS Path: {666} 234 2548 1 IGP
to 192.156.169.1 via 192.156.169.14(so-0/0/0)
AS Path: {666} 234 2548 568 721 Incomplete
to 192.156.169.1 via 192.156.169.14(so-0/0/0)
AS Path: {666} 234 2548 1673 1675 1747 IGP
to 192.156.169.1 via 192.156.169.14(so-0/0/0)
905
show route community-name

Syntax
show route community-name community-name

Syntax (EX Series

Switches)
show route community-name community-name

Release Information
Description
Options

Display the route entries in each routing table that are members of a Border Gateway
Protocol (BGP) community, specified by a community name.
community-nameName of the community.

Required Privilege
Level
Output Fields
906
view
show route community-name on page 907

Sample Output
show route
community-name
user@host> show route community-name red-com

instance1.inet.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
red.inet.0: 11 destinations, 11 routes (11 active, 0 holddown, 0 hidden)
10.255.245.212/32
20.20.20.20/32
100.1.4.0/24

AS path: 300 I
> to 100.1.2.2 via ge-1/1/0.0, label-switched-path to_fix
AS path: I
AS path: I
iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)

bgp.l3vpn.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
10.255.245.204:10:10.255.245.212/32
AS path: 300 I
10.255.245.204:10:20.20.20.20/32
AS path: I
10.255.245.204:10:100.1.4.0/24
AS path: I
inet6.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
instance1.inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
907
show route damping

Syntax
show route damping (decayed | history | suppressed)

Syntax (EX Series

Switch and QFX
Series)
show route damping (decayed | history | suppressed)

Release Information
Description
Options

Display the BGP routes for which updates might have been reduced because of route
flap damping.

decayedDisplay route damping entries that might no longer be valid, but are not
suppressed.
historyDisplay entries that have already been withdrawn, but have been logged.

suppressedDisplay entries that have been suppressed and are no longer being installed
into the forwarding table or exported by routing protocols.

Required Privilege
Level
Related
Documentation
Output Fields
view
clear bgp damping
show policy damping
show route damping decayed detail on page 912

show route damping history on page 912
show route damping history detail on page 912
Table 80 on page 908 lists the output fields for the show route damping command. Output
Table 80: show route damping Output Fields

Field Name
Field Description
Level of Output
routing-table-name
All levels
destinations
All levels
908
Table 80: show route damping Output Fields (continued)

Field Name
Field Description
Level of Output
number routes
states:
All levels
active
holddown (routes that are in a pending state before being declared inactive)
hidden (the routes are not used because of a routing policy)
destination-prefix
(entry, announced)
destination.
detail extensive
[protocol,
preference]
Protocol from which the route was learned and the preference value for the
route.
All levels
+A plus sign indicates the active route, which is the route installed from the
routing table into the forwarding table.
*An asterisk indicates that the route is both the active and the last active
route. An asterisk before a to line indicates the best subpath to the route.
In every routing metric except for the BGP LocalPref attribute, a lesser value is
preferred. In order to use common comparison routines, Junos OS stores the 1's
complement of the LocalPref value in the Preference2 field. For example, if the
LocalPref value for Route 1 is 100, the Preference2 value is -101. If the LocalPref
value for Route 2 is 155, the Preference2 value is -156. Route 2 is preferred
because it has a higher LocalPref value and a lower Preference2 value.
Next-hop reference
count
Number of references made to the next hop.
detail extensive
Source
IP address of the route source.
detail extensive
Next hop
Network layer address of the directly reachable neighboring system.
detail extensive
via
Interface used to reach the next hop. If there is more than one interface available
to the next hop, the interface that is actually used is followed by the word
Selected.
detail extensive
Protocol next hop
Network layer address of the remote routing device that advertised the prefix.
This address is used to derive a forwarding next hop.
detail extensive
Indirect next hop
Index designation used to specify the mapping between protocol next hops,
tags, kernel export policy, and the forwarding next hops.
detail extensive
State
Flags for this route. For a description of possible values for this field, see the
output field table for the show route detail command.
detail extensive
Local AS
AS number of the local routing device.
detail extensive
Peer AS
AS number of the peer routing device.
detail extensive
909

Field Name
Field Description
Level of Output
Age
How long the route has been known.
detail extensive
Metric
Metric for the route.
detail extensive
Task
Name of the protocol that has added the route.
detail extensive
Announcement bits
List of protocols that announce this route. n-Resolve inet indicates that the route
is used for route resolution for next hops found in the routing table. n is an index
used by Juniper Networks customer support only.
detail extensive
AS path
AS path through which the route was learned. The letters at the end of the AS
path indicate the path origin, providing an indication of the state of the route at
the point at which the AS path originated:
All levels
IIGP.
EEGP.
[ ]Brackets enclose the local AS number associated with the AS path if
more than one AS number is configured on the routing device or if AS path

prepending is configured.
to
selected route.
brief none
via
Interface used to reach the next hop. If there is more than one interface available
to the next hop, the interface that is actually used is followed by the word
Selected.
brief none
Communities
Community path attribute for the route. See the output field table for the show
route detail command.
detail extensive
Localpref
All levels
Router ID
BGP router ID as advertised by the neighbor in the open message.
detail extensive
Merit (last
update/now)
Last updated and current figure-of-merit value.
detail extensive
910

Field Name
Field Description
Level of Output
damping-parameters
Name that identifies the damping parameters used, which is defined in the
damping statement at the [edit policy-options] hierarchy level.
detail extensive
Last update
Time of most recent change in path attributes.
detail extensive
First update
Time of first change in path attributes, which started the route damping process.
detail extensive
Flaps
Number of times the route has gone up or down or its path attributes have
changed.
detail extensive
Suppressed
(suppressed keyword only) This route is currently suppressed. A suppressed

route does not appear in the forwarding table and routing protocols do not
export it.
All levels
Reusable in
(suppressed keyword only) Time when a suppressed route will again be available.
All levels
Preference will be
(suppressed keyword only) Preference value that will be applied to the route
when it is again active.
All levels
911
Sample Output
show route damping
decayed detail
user@host> show route damping decayed detail

inet.0: 173319 destinations, 1533668 routes (172625 active, 4 holddown, 108083
hidden)
*BGP
Source: 172.23.2.129
Indirect next hop: 89a1a00 264185
State: <Active Ext>
Local AS: 65000 Peer AS:
65490
Age: 3:28
Metric2: 0
Task: BGP_65490.172.23.2.129+179
Announcement bits (6): 0-KRT 1-RT 4-KRT 5-BGP.0.0.0.0+179
6-Resolve tree 2 7-Resolve tree 3
AS path: 65490 65520 65525 65525 65525 65525 I ()
Communities: 65501:390 65501:2000 65501:3000 65504:701
Localpref: 100
Router ID: 172.23.2.129
Merit (last update/now): 1934/1790
damping-parameters: damping-high
Last update:
00:03:28 First update:
00:06:40
Flaps: 2
show route damping

history
user@host> show route damping history

hidden)
10.108.0.0/15
show route damping

history detail
912
[BGP ] 2d 22:47:58, localpref 100

AS path: 65220 65501 65502 I
> to 192.168.60.85 via so-3/1/0.0
user@host> show route damping history detail

hidden)
BGP
/-101
Source: 192.168.60.85
State: <Hidden Ext>
Inactive reason: Unusable path
Age: 2d 22:48:10
Task: BGP_65220.192.168.60.85+179
AS path: 65220 65501 65502 I ()
Communities: 65501:390 65501:2000 65501:3000 65504:3561
Localpref: 100
Router ID: 192.168.80.25
Merit (last update/now): 1000/932
damping-parameters: set-normal
Last update:
Flaps: 1
00:01:05 First update:
00:01:05
913
show route detail

Syntax
show route detail

Syntax (EX Series

Switches)
show route detail

Release Information

Description
Display detailed information about the active entries in the routing tables.
Options
noneDisplay all active entries in the routing table on all systems.

of addresses.

Required Privilege
Level
view
show route detail on page 923

show route detail (with BGP Multipath) on page 928
Output Fields
Table 81 on page 914 describes the output fields for the show route detail command.
Table 81: show route detail Output Fields

Field Name
Field Description
routing-table-name
number destinations
number routes
914
Table 81: show route detail Output Fields (continued)

Field Name
Field Description
route-destination
(entry, announced)
Route destination (for example:10.0.0.1/24). The entry value is the number of routes for this destination,
and the announced value is the number of routes being announced for this destination. Sometimes
the route destination is presented in another format, such as:
MPLS-label (for example, 80001).
neighbor-address:control-word-status:encapsulation type:vc-id:source (Layer 2 circuit only; for example,
10.1.1.195:NoCtrlWord:1:1:Local/96).
label stacking
(Next-to-the-last-hop routing device for MPLS only) Depth of the MPLS label stack, where the
label-popping operation is needed to remove one or more labels from the top of the stack. A pair of
routes is displayed, because the pop operation is performed only when the stack depth is two or more
labels.
S=0 route indicates that a packet with an incoming label stack depth of 2 or more exits this routing
device with one fewer label (the label-popping operation is performed).
[protocol, preference]
If there is no S= information, the route is a normal MPLS route, which has a stack depth of 1 (the
label-popping operation is not performed).
forwarding table.
Level
(IS-IS only). In IS-IS, a single AS can be divided into smaller groups called areas. Routing between
areas is organized hierarchically, allowing a domain to be administratively divided into smaller areas.
This organization is accomplished by configuring Level 1 and Level 2 intermediate systems. Level 1
systems route within an area. When the destination is outside an area, they route toward a Level 2
system. Level 2 intermediate systems route between areas and toward other ASs.
Route Distinguisher
IP subnet augmented with a 64-bit prefix.
Next-hop type
Type of next hop. For a description of possible values for this field, see Table 82 on page 918.
915

Field Name
Field Description
Next-hop reference
count
Flood nexthop branches

exceed maximum
Indicates that the number of flood next-hop branches exceeded the system limit of 32 branches, and
only a subset of the flood next-hop branches were installed in the kernel.
message
Source
Next hop
via
name of the interface that is actually used is followed by the word Selected. This field can also contain
the following information:
Label-switched-path
lsp-path-name
Name of the LSP used to reach the next hop.
Label operation
MPLS label and operation occurring at this routing device. The operation can be pop (where a label
is removed from the top of the stack), push (where another label is added to the label stack), or swap
(where a label is replaced by another label).
Interface
(Local only) Local interface name.
Protocol next hop
Network layer address of the remote routing device that advertised the prefix. This address is used
to derive a forwarding next hop.
Indirect next hop
Index designation used to specify the mapping between protocol next hops, tags, kernel export policy,
and the forwarding next hops.
State
State of the route (a route can be in more than one state). See Table 83 on page 920.
Local AS
AS number of the local routing device.
Age
AIGP
Metricn
Cost value of the indicated route. For routes within an AS, the cost is determined by IGP and the
916

Field Name
Field Description
MED-plus-IGP
Metric value for BGP path selection to which the IGP cost to the next-hop destination has been added.
TTL-Action
For MPLS LSPs, state of the TTL propagation attribute. Can be enabled or disabled for all
RSVP-signaled and LDP-signaled LSPs or for specific VRF routing instances.
For sample output, see show route table.
Task
Announcement bits
List of protocols that announce this route. n-Resolve inet indicates that the route is used for route
resolution for next hops found in the routing table. n is an index used by Juniper Networks customer
support only.
AS path
IIGP.
EEGP.
RecordedThe AS path is recorded by the sample process (sampled).
[ ]Brackets enclose the number that precedes the AS path. This number represents the number
of ASs present in the AS path, when calculated as defined in RFC 4271. This value is used in the
AS-path merge process, as defined in RFC 4893.
[ ]If more than one AS number is configured on the routing device, or if AS path prepending is
configured, brackets enclose the local AS number associated with the AS path.
ascending order.
VC Label
MPLS label assigned to the Layer 2 circuit virtual connection.
MTU
VLAN ID
VLAN identifier of the Layer 2 circuit.
Prefixes bound to route
Forwarding equivalent class (FEC) bound to this route. Applicable only to routes installed by LDP.
Communities
Community path attribute for the route. See Table 84 on page 922 for all possible values for this field.
Layer2-info: encaps
917

Field Name
Field Description
control flags
mtu
Maximum transmission unit (MTU) information.
Label-Base, range
First label in a block of labels and label block size. A remote PE routing device uses this first label
when sending traffic toward the advertising PE routing device.
status vector
Layer 2 VPN and VPLS network layer reachability information (NLRI).
Accepted Multipath
Current active path when BGP multipath is configured.
Accepted
MultipathContrib
Path currently contributing to BGP multipath.
Localpref
Router ID
Primary Routing Table
In a routing table group, the name of the primary routing table in which the route resides.
Secondary Tables
In a routing table group, the name of one or more secondary tables in which the route resides.
Table 82 on page 918 describes all possible values for the Next-hop Types output field.
Table 82: Next-hop Types Output Field Values
918
Next-Hop Type
Description
Broadcast (bcast)
Broadcast next hop.
Deny
Deny next hop.
Discard
Discard next hop.
Flood
Flood next hop. Consists of components called branches,

up to a maximum of 32 branches. Each flood next-hop
branch sends a copy of the traffic to the forwarding
interface. Used by point-to-multipoint RSVP,
point-to-multipoint LDP, point-to-multipoint CCC, and
multicast.
Hold
Next hop is waiting to be resolved into a unicast or

multicast type.
Indexed (idxd)
Indexed next hop.
Table 82: Next-hop Types Output Field Values (continued)

Next-Hop Type
Description
Indirect (indr)
Used with applications that have a protocol next hop

address that is remote. You are likely to see this next-hop
type for internal BGP (IBGP) routes when the BGP next
hop is a BGP neighbor that is not directly connected.
Interface
Used for a network address assigned to an interface. Unlike

the router next hop, the interface next hop does not
reference any specific node on the network.
Local (locl)
Local address on an interface. This next-hop type causes

packets with this destination address to be received locally.
Multicast (mcst)
Wire multicast next hop (limited to the LAN).
Multicast discard (mdsc)
Multicast discard.
Multicast group (mgrp)
Multicast group member.
Receive (recv)
Receive.
Reject (rjct)
Discard. An ICMP unreachable message was sent.
Resolve (rslv)
Resolving next hop.
Routed multicast (mcrt)
Regular multicast next hop.
Router
A specific node or set of nodes to which the routing device

forwards packets that match the route prefix.
To qualify as next-hop type router, the route must meet
the following criteria:
Must not be a direct or local subnet for the routing

device.
Must have a next hop that is directly connected to the

routing device.
Table
Routing table next hop.
Unicast (ucst)
Unicast.
Unilist (ulst)
List of unicast next hops. A packet sent to this next hop

goes to any next hop in the list.
Table 83 on page 920 describes all possible values for the State output field. A route can
be in more than one state (for example, <Active NoReadvrt Int Ext>).
919
Table 83: State Output Field Values
920
Value
Description
Accounting
Route needs accounting.
Active
Route is active.
Always Compare MED
Path with a lower multiple exit discriminator (MED) is

available.
AS path
Shorter AS path is available.
Cisco Non-deterministic MED

selection
Cisco nondeterministic MED is enabled, and a path with a

lower MED is available.
Clone
Route is a clone.
Cluster list length
Length of cluster list sent by the route reflector.
Delete
Route has been deleted.
Ex
Exterior route.
Ext
BGP route received from an external BGP neighbor.
FlashAll
Forces all protocols to be notified of a change to any route,

active or inactive, for a prefix. When not set, protocols are
informed of a prefix only when the active route changes.
Hidden
Route not used because of routing policy.
IfCheck
Route needs forwarding RPF check.
IGP metric
Path through next hop with lower IGP metric is available.
Inactive reason
Flags for this route, which was not selected as best for a
particular destination.
Initial
Route being added.
Int
Interior route.
Int Ext
BGP route received from an internal BGP peer or a BGP

confederation peer.
Interior > Exterior > Exterior via

Interior
Direct, static, IGP, or EBGP path is available.
Local Preference
Path with a higher local preference value is available.
Martian
Route is a martian (ignored because it is obviously invalid).
Table 83: State Output Field Values (continued)

Value
Description
MartianOK
Route exempt from martian filtering.
Next hop address
Path with lower metric next hop is available.
No difference
Path from neighbor with lower IP address is available.
NoReadvrt
Route not to be advertised.
NotBest
Route not chosen because it does not have the lowest MED.
Not Best in its group
Incoming BGP AS is not the best of a group (only one AS can

be the best).
NotInstall
Route not to be installed in the forwarding table.
Number of gateways
Path with a greater number of next hops is available.
Origin
Path with a lower origin code is available.
Pending
Route pending because of a hold-down configured on another

route.
Release
Route scheduled for release.
RIB preference
Route from a higher-numbered routing table is available.
Route Distinguisher
64-bit prefix added to IP subnets to make them unique.
Route Metric or MED comparison
Route with a lower metric or MED is available.
Route Preference
Route with lower preference value is available
Router ID
Path through a neighbor with lower ID is available.
Secondary
Route not a primary route.
Unusable path
Path is not usable because of one of the following conditions:
Update source
The route is damped.
The route is rejected by an import policy.
The route is unresolved.
Last tiebreaker is the lowest IP address value.
Table 84 on page 922 describes the possible values for the Communities output field.
921
Table 84: Communities Output Field Values

Value
Description
area-number
4 bytes, encoding a 32-bit area number. For AS-external routes, the value is 0. A nonzero value
identifies the route as internal to the OSPF domain, and as within the identified area. Area
numbers are relative to a particular OSPF domain.
bandwidth: local AS
number:link-bandwidth-number
Link-bandwidth community value used for unequal-cost load balancing. When BGP has
several candidate paths available for multipath purposes, it does not perform unequal-cost
load balancing according to the link-bandwidth community unless all candidate paths have
this attribute.
domain-id
Unique configurable number that identifies the OSPF domain.
domain-id-vendor
Unique configurable number that further identifies the OSPF domain.
link-bandwidth-number
Link-bandwidth number: from 0 through 4,294,967,295 (bytes per second).
local AS number
Local AS number: from 1 through 65,535.
options
1 byte. Currently this is only used if the route type is 5 or 7. Setting the least significant bit in
the field indicates that the route carries a type 2 metric.
origin
(Used with VPNs) Identifies where the route came from.
ospf-route-type
1 byte, encoded as 1 or 2 for intra-area routes (depending on whether the route came from a
type 1 or a type 2 LSA); 3 for summary routes; 5 for external routes (area number must be0);
7 for NSSA routes; or 129 for sham link endpoint addresses.
route-type-vendor
Displays the area number, OSPF route type, and option of the route. This is configured using
the BGP extended community attribute 0x8000. The format is
area-number:ospf-route-type:options.
rte-type
Displays the area number, OSPF route type, and option of the route. This is configured using
the BGP extended community attribute 0x0306. The format is
area-number:ospf-route-type:options.
target
Defines which VPN the route participates in; target has the format 32-bit IP address:16-bit
number. For example, 10.19.0.0:100.
unknown IANA
Incoming IANA codes with a value between 0x1 and 0x7fff. This code of the BGP extended
community attribute is accepted, but it is not recognized.
unknown OSPF vendor

community
Incoming IANA codes with a value above 0x8000. This code of the BGP extended community
attribute is accepted, but it is not recognized.
922
Sample Output
show route detail
user@host> show route detail

*Static Preference: 5
Next hop: 192.168.71.254 via fxp0.0, selected
State: <Active NoReadvrt Int Ext>
Local AS:
69
Age: 1:31:43
Task: RT
AS path: I
State: <Active Int>
Local AS:
69
Age: 1:30:17
Task: IF
AS path: I
OSPF
Preference: 10
State: <Int>
Inactive reason: Route Preference
Local AS:
69
Age: 1:30:17
Metric: 1
Area: 0.0.0.0
Task: OSPF
AS path: I
State: <Active NoReadvrt Int>
Local AS:
69
Age: 1:30:20
Task: IF
AS path: I
...
*OSPF
Preference: 10
State: <Active Int>
Local AS:
69
Age: 1:29:56
Metric: 2
923
Area: 0.0.0.0
Task: OSPF
AS path: I
...
*PIM
Preference: 0
Local AS:
69
Age: 1:31:45
Task: PIM Recv
AS path: I
...
224.0.0.22/32 (1 entry, 1 announced)
*IGMP
Preference: 0
Local AS:
69
Age: 1:31:43
Task: IGMP
AS path: I
10.255.70.103/32 (1 entry, 1 announced)
State: <FlashAll>
*RSVP
Preference: 7
Next hop: 10.31.1.6 via ge-3/1/0.0 weight 0x1, selected
State: <Active Int>
Local AS:
69
Age: 1:25:49
Metric: 2
Task: RSVP
AS path: I
10.255.71.238/32 (1 entry, 1 announced)
State: <FlashAll>
*RSVP
Preference: 7
State: <Active Int>
Local AS:
69
Age: 1:25:49
Metric: 1
Task: RSVP
AS path: I
private__.inet.0: 2 destinations, 3 routes (2 active, 0 holddown, 0 hidden)
924
47.0005.80ff.f800.0000.0108.0001.0102.5507.1052/152 (1 entry, 0 announced)

State: <Active Int>
Local AS:
69
Age: 1:31:44
Task: IF
AS path: I
0
(1 entry, 1 announced)
*MPLS
Preference: 0
Next hop type: Receive
State: <Active Int>
Local AS:
69
Age: 1:31:45
Metric: 1
Task: MPLS
Announcement bits (1): 0-KRT
AS path: I
...
299776 (1 entry, 1 announced)
TSI:
KRT in-kernel 299776 /52 -> {Flood}
*RSVP
Preference: 7
Next hop type: Flood
Flood nexthop branches exceed maximum
Address: 0x8ea65d0
...
*VPLS
Preference: 7
Next hop: via vt-3/2/0.32769, selected
Label operation: Pop
State: <Active Int>
Age: 1:29:30
Task: Common L2 VC
AS path: I
vt-3/2/0.32769 (1 entry, 1 announced)
*VPLS
Preference: 7
Label operation: Push 800012, Push 100096(top)
Push 800012
Indirect next hop: 87272e4 1048574
State: <Active Int>
Age: 1:29:30
Metric2: 2
Task: Common L2 VC
Announcement bits (2): 0-KRT 1-Common L2 VC
925
AS path: I
Communities: target:11111:1 Layer2-info: encaps:VPLS,
control flags:, mtu: 0
abcd::10:255:71:52/128 (1 entry, 0 announced)
State: <Active Int>
Local AS:
69
Age: 1:31:44
Task: IF
AS path: I
fe80::280:42ff:fe10:f179/128 (1 entry, 0 announced)
Local AS:
69
Age: 1:31:44
Task: IF
AS path: I
ff02::2/128 (1 entry, 1 announced)
*PIM
Preference: 0
Local AS:
69
Age: 1:31:45
Task: PIM Recv6
AS path: I
ff02::d/128 (1 entry, 1 announced)
*PIM
Preference: 0
Local AS:
69
Age: 1:31:45
Task: PIM Recv6
AS path: I
*MLD
Preference: 0
Local AS:
69
Age: 1:31:43
Task: MLD
AS path: I
private.inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
926
Age: 1:31:44
Task: IF
AS path: I
green.l2vpn.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden)
10.255.70.103:1:3:1/96 (1 entry, 1 announced)
*BGP
Source: 10.255.70.103
State: <Secondary Active Int Ext>
Local AS:
69 Peer AS:
69
Age: 1:25:49
Metric2: 1
AIGP 210
Task: BGP_69.10.255.70.103+179
Announcement bits (1): 0-green-l2vpn
AS path: I
Label-base: 800008, range: 8
Localpref: 100
Router ID: 10.255.70.103
Primary Routing Table bgp.l2vpn.0
10.255.71.52:1:1:1/96 (1 entry, 1 announced)
*L2VPN Preference: 170/-1
Indirect next hop: 0 State: <Active Int Ext>
Age: 1:31:40
Metric2: 1
Task: green-l2vpn
Announcement bits (1): 1-BGP.0.0.0.0+179
AS path: I
Communities: Layer2-info: encaps:VPLS, control flags:Site-Down,
mtu: 0
Label-base: 800016, range: 8, status-vector: 0x9F
10.255.71.52:1:5:1/96 (1 entry, 1 announced)
Age: 1:31:40
Metric2: 1
Task: green-l2vpn
AS path: I
Communities: Layer2-info: encaps:VPLS, control flags:, mtu: 0
...
927
l2circuit.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)

10.245.255.63:CtrlWord:4:3:Local/96 (1 entry, 1 announced)
*L2CKT Preference: 7
Next hop: via so-1/1/2.0 weight 1, selected
Label-switched-path my-lsp
Label operation: Push 100000[0]
Protocol next hop: 10.245.255.63 Indirect next hop: 86af000 296
State: <Active Int>
Local AS:
99
Age: 10:21
Task: l2 circuit
Announcement bits (1): 0-LDP
AS path: I
VC Label 100000, MTU 1500, VLAN ID 512
show route detail (with

BGP Multipath)
user@host> show route detail

*BGP
Address: 0x901a010
Source: 10.1.1.2
Next hop: 10.1.1.6 via ge-0/3/0.5
State: <Active Ext>
Local AS:
1 Peer AS:
2
Age: 5:04:43
Task: BGP_2.10.1.1.2+59955
AS path: 2 I
Accepted Multipath
Localpref: 100
Router ID: 1.1.1.2
BGP
Address: 0x8f97520
Source: 10.1.1.6
State: <NotBest Ext>
Inactive reason: Not Best in its group - Active preferred
Local AS:
1 Peer AS:
2
Age: 5:04:43
Task: BGP_2.10.1.1.6+58198
AS path: 2 I
Accepted MultipathContrib
Localpref: 100
Router ID: 1.1.1.3
928
show route exact

Syntax
Syntax (EX Series

Switches)
Release Information
Description
Options
show route exact destination-prefix

show route exact destination-prefix

Display only the routes that exactly match the specified address or range of addresses.

destination-prefixAddress or range of addresses.

Required Privilege
Level
Output Fields
view
show route exact on page 930

show route exact detail on page 930
show route exact extensive on page 930
show route exact terse on page 930
929
Sample Output
show route exact
user@host> show route exact 207.17.136.0/24

Restart Complete
207.17.136.0/24
*[Static/5] 2d 03:30:22
> to 192.168.71.254 via fxp0.0
show route exact detail
user@host> show route exact 207.17.136.0/24 detail

Restart Complete
207.17.136.0/24 (1 entry, 1 announced)
Local AS:
69
Age: 2d 3:30:26
Task: RT
AS path: I
show route exact

extensive
user@host> show route exact 207.17.136.0/24 extensive

207.17.136.0/24 (1 entry, 1 announced)
TSI:
KRT in-kernel 207.17.136.0/24 -> {192.168.71.254}
Local AS:
69
Age: 1:25:18
Task: RT
AS path: I
show route exact terse
user@host> show route exact 207.17.136.0/24 terse

A Destination
P Prf
Metric 1
Metric 2 Next hop
AS path
* 207.17.136.0/24
S
5
>192.168.71.254
930
show route export

Syntax
show route export

<brief | detail>
<instance <instance-name> | routing-table-name>
Syntax (EX Series

Switches)
show route export

<brief | detail>
<instance <instance-name> | routing-table-name>
Release Information
Description
Options

Display policy-based route export information. Policy-based export simplifies the process
of exchanging route information between routing instances.
none(Same as brief.) Display standard information about policy-based export for all
instances and routing tables on all systems.

brief | detail(Optional) Display the specified level of output.
instance <instance-name>(Optional) Display a particular routing instance for which
policy-based export is currently enabled.


routing-table-name(Optional) Display information about policy-based export for all
routing tables whose name begins with this string (for example, inet.0 and inet6.0
are both displayed when you run the show route export inet command).
Required Privilege
Level
Output Fields
view
show route export on page 932

show route export detail on page 932
show route export instance detail on page 932
Table 85 on page 931 lists the output fields for the show route export command. Output
Table 85: show route export Output Fields

Field Name
Field Description
Level of Output
Table or table-name
Name of the routing tables that either import or export routes.
All levels
Routes
Number of routes exported from this table into other tables. If a particular route is
exported to different tables, the counter will only increment by one.
brief none
Export
Whether the table is currently exporting routes to other tables: Y or N (Yes or No).
brief none
931
Table 85: show route export Output Fields (continued)

Field Name
Field Description
Level of Output
Import
Tables currently importing routes from the originator table. (Not displayed for
tables that are not exporting any routes.)
detail
Flags
(instance keyword only) Flags for this feature on this instance:
detail
config auto-policyThe policy was deduced from the configured IGP export
policies.
Options
cleanupConfiguration information for this instance is no longer valid.
configThe instance was explicitly configured.
(instance keyword only) Configured option displays the type of routing tables the
feature handles:
unicastIndicates instance.inet.0.
multicastIndicates instance.inet.2.
unicast multicastIndicates instance.inet.0 and instance.inet.2.
detail
Import policy
(instance keyword only) Policy that route export uses to construct the import-export
matrix. Not displayed if the instance type is vrf.
detail
Instance
(instance keyword only) Name of the routing instance.
detail
Type
(instance keyword only) Type of routing instance: forwarding, non-forwarding, or

vrf.
detail
Sample Output
show route export
show route export

detail
show route export

instance detail
932
user@host> show route export

Table
inet.0
black.inet.0
red.inet.0
user@host> show route export detail

inet.0
black.inet.0
Import: [ inet.0 ]
red.inet.0
Import: [ inet.0 ]
Export
N
Y
Y
Routes
0
3
4
Routes:
Routes:
0
3
Routes:
user@host> show route export instance detail

Instance: master
Type: forwarding
Flags: <config auto-policy> Options: <unicast multicast>
Import policy: [ (ospf-master-from-red || isis-master-from-black) ]
Instance: black
Type: non-forwarding
Instance: red
Type: non-forwarding

Syntax

Syntax (EX Series

Switches)

Release Information

Description
Display extensive information about the active entries in the routing tables.
Options
noneDisplay all active entries in the routing table.

of addresses.

Required Privilege
Level
view
show route extensive on page 939

show route extensive (Access Route) on page 945
show route extensive (Route Reflector) on page 945
show route extensive (FRR and LFA) on page 945
show route extensive (FRR and LFA) on page 946
Output Fields
Table 86 on page 933 describes the output fields for the show route extensive command.
Table 86: show route extensive Output Fields

Field Name
Field Description
routing-table-name
number destinations
number routes
active (routes that are active).
holddown (routes that are in the pending state before being declared inactive).
hidden (routes that are not used because of a routing policy).
933
Table 86: show route extensive Output Fields (continued)

Field Name
Field Description
route-destination
(entry, announced)
Route destination (for example: 10.0.0.1/24). The entry value is the number of route for this destination,
and the announced value is the number of routes being announced for this destination. Sometimes
the route destination is presented in another format, such as:
MPLS-label (for example, 80001 ).
neighbor-address:control-word-status:encapsulation type:vc-id:source (Layer 2 circuit only; for example,
10.1.1.195:NoCtrlWord:1:1:Local/96).
TSI
Protocol header information.
label stacking
(Next-to-the-last-hop routing device for MPLS only) Depth of the MPLS label stack, where the
label-popping operation is needed to remove one or more labels from the top of the stack. A pair of
routes is displayed, because the pop operation is performed only when the stack depth is two or more
labels.
S=0 route indicates that a packet with an incoming label stack depth of two or more exits this router
with one fewer label (the label-popping operation is performed).
[protocol, preference]
If there is no S= information, the route is a normal MPLS route, which has a stack depth of 1 (the
label-popping operation is not performed).
forwarding table.
Level
(IS-IS only). In IS-IS, a single autonomous system (AS) can be divided into smaller groups called
areas. Routing between areas is organized hierarchically, allowing a domain to be administratively
divided into smaller areas. This organization is accomplished by configuring Level 1 and Level 2
intermediate systems. Level 1 systems route within an area. When the destination is outside an area,
they route toward a Level 2 system. Level 2 intermediate systems route between areas and toward
other ASs.
Route Distinguisher
IP subnet augmented with a 64-bit prefix.
934

Field Name
Field Description
Next-hop type
Type of next hop. For a description of possible values for this field, see the Output Field table in the
show route detail command.
Next-hop reference
count
Flood nexthop branches

exceed maximum
Indicates that the number of flood next-hop branches exceeded the system limit of 32 branches, and
only a subset of the flood next-hop branches were installed in the kernel.
message
Source
Next hop
via
name of the interface that is actually used is followed by the word Selected. This field can also contain
the following information:
Label-switched-path
lsp-path-name
Name of the LSP used to reach the next hop.
Label operation
Offset
Whether the metric has been increased or decreased by an offset value.
Interface
(Local only) Local interface name.
Protocol next hop
Network layer address of the remote routing device that advertised the prefix. This address is used
to recursively derive a forwarding next hop.
label-operation
Indirect next hops
When present, a list of nodes that are used to resolve the path to the next-hop destination, in the
order that they are resolved.
State
State of the route (a route can be in more than one state). See the Output Field table in the show
route detail command.
935

Field Name
Field Description
Session ID
The BFD session ID number that represents the protection using MPLS fast reroute (FRR) and loop-free
alternate (LFA).
Inactive reason
If the route is inactive, the reason for its current state is indicated. Typical reasons include:
Active preferredCurrently active route was selected over this route.
Always compare MEDPath with a lower multiple exit discriminator (MED) is available.
AS pathShorter AS path is available.
Cisco Non-deterministic MED selectionCisco nondeterministic MED is enabled and a path with a
lower MED is available.
Cluster list lengthPath with a shorter cluster list length is available.
Forwarding use onlyPath is only available for forwarding purposes.
IGP metricPath through the next hop with a lower IGP metric is available.
IGP metric typePath with a lower OSPF link-state advertisement type is available.
Interior > Exterior > Exterior via InteriorDirect, static, IGP, or EBGP path is available.
Local preferencePath with a higher local preference value is available.
Next hop addressPath with a lower metric next hop is available.
No differencePath from a neighbor with a lower IP address is available.
Not Best in its groupOccurs when multiple peers of the same external AS advertise the same
prefix and are grouped together in the selection process. When this reason is displayed, an additional
reason is provided (typically one of the other reasons listed).
Number of gatewaysPath with a higher number of next hops is available.
OriginPath with a lower origin code is available.
OSPF versionPath does not support the indicated OSPF version.
RIB preferenceRoute from a higher-numbered routing table is available.
Route destinguisher64-bit prefix added to IP subnets to make them unique.
Route metric or MED comparisonRoute with a lower metric or MED is available.
Route preferenceRoute with a lower preference value is available.
Router IDPath through a neighbor with a lower ID is available.
Unusable pathPath is not usable because of one of the following conditions: the route is damped,
the route is rejected by an import policy, or the route is unresolved.
Update sourceLast tiebreaker is the lowest IP address value.
Local AS
Autonomous system (AS) number of the local routing device.
Age
AIGP
Metric
Cost value of the indicated route. For routes within an AS, the cost is determined by IGP and the
MED-plus-IGP
Metric value for BGP path selection to which the IGP cost to the next-hop destination has been added.
936

Field Name
Field Description
TTL-Action
For MPLS LSPs, state of the TTL propagation attribute. Can be enabled or disabled for all
RSVP-signaled and LDP-signaled LSPs or for specific VRF routing instances.
For sample output, see show route table.
Task
Announcement bits
List of protocols that announce this route. n-Resolve inet indicates that the route is used for route
resolution for next hops found in the routing table. n is an index used by Juniper Networks customer
support only.
AS path
IIGP.
EEGP.
RecordedThe AS path is recorded by the sample process (sampled).
[ ]Brackets enclose the local AS number associated with the AS path if more than one AS number
is configured on the routing device, or if AS path prepending is configured.
ascending order.
AS path: I <Originator>
(For route reflected output only) Originator ID attribute set by the route reflector.
VC Label
MPLS label assigned to the Layer 2 circuit virtual connection.
MTU
VLAN ID
VLAN identifier of the Layer 2 circuit.
Cluster list
(For route reflected output only) Cluster ID sent by the route reflector.
Originator ID
(For route reflected output only) Address of router that originally sent the route to the route reflector.
Prefixes bound to route
Forwarding equivalent class (FEC) bound to this route. Applicable only to routes installed by LDP.
Communities
Community path attribute for the route. See the Output Field table in the show route detail command
for all possible values for this field.
937

Field Name
Field Description
Layer2-info: encaps
control flags
mtu
Maximum transmission unit (MTU) information.
Label-Base, range
First label in a block of labels and label block size. A remote PE routing device uses this first label
when sending traffic toward the advertising PE routing device.
status vector
Layer 2 VPN and VPLS network layer reachability information (NLRI).
Localpref
Router ID
Primary Routing Table
In a routing table group, the name of the primary routing table in which the route resides.
Secondary Tables
In a routing table group, the name of one or more secondary tables in which the route resides.
Originating RIB
Name of the routing table whose active route was used to determine the forwarding next-hop entry
in the resolution database. For example, in the case of inet.0 resolving through inet.0 and inet.3, this
field indicates which routing table, inet.0 or inet.3, provided the best path for a particular prefix.
Node path count
Number of nodes in the path.
Forwarding nexthops
Number of forwarding next hops. The forwarding next hop is the network layer address of the directly
reachable neighboring system (if applicable) and the interface used to reach it.
938
Sample Output

TSI:
KRT in-kernel 10.10.0.0/16 -> {192.168.71.254}
Local AS:
69
Age: 1:34:06
Task: RT
AS path: I
State: <Active Int>
Local AS:
69
Age: 1:32:40
Task: IF
AS path: I
OSPF
Preference: 10
State: <Int>
Local AS:
69
Age: 1:32:40
Metric: 1
Area: 0.0.0.0
Task: OSPF
AS path: I
Local AS:
69
Age: 1:32:43
Task: IF
AS path: I
...
TSI:
KRT in-kernel 10.31.2.0/30 -> {10.31.1.6}
*OSPF
Preference: 10
939
State: <Active Int>

Local AS:
69
Age: 1:32:19
Metric: 2
Area: 0.0.0.0
Task: OSPF
AS path: I
...
TSI:
KRT in-kernel 224.0.0.2/32 -> {}
*PIM
Preference: 0
Local AS:
69
Age: 1:34:08
Task: PIM Recv
AS path: I
...
224.0.0.22/32 (1 entry, 1 announced)
TSI:
KRT in-kernel 224.0.0.22/32 -> {}
*IGMP
Preference: 0
Local AS:
69
Age: 1:34:06
Task: IGMP
AS path: I
10.255.70.103/32 (1 entry, 1 announced)
State: <FlashAll>
*RSVP
Preference: 7
State: <Active Int>
Local AS:
69
Age: 1:28:12
Metric: 2
Task: RSVP
AS path: I
10.255.71.238/32 (1 entry, 1 announced)
State: <FlashAll>
*RSVP
Preference: 7
State: <Active Int>
Local AS:
69
Age: 1:28:12
Metric: 1
940
Task: RSVP
AS path: I
...
47.0005.80ff.f800.0000.0108.0001.0102.5507.1052/152 (1 entry, 0 announced)
State: <Active Int>
Local AS:
69
Age: 1:34:07
Task: IF
AS path: I
0
(1 entry, 1 announced)
TSI:
KRT in-kernel 0
/36 -> {}
*MPLS
Preference: 0
Next hop type: Receive
State: <Active Int>
Local AS:
69
Age: 1:34:08
Metric: 1
Task: MPLS
AS path: I
...
TSI:
KRT in-kernel 299776 /52 -> {Flood}
*RSVP
Preference: 7
Next hop type: Flood
Flood nexthop branches exceed maximum
Address: 0x8ea65d0
...
TSI:
KRT in-kernel 800010 /36 -> {vt-3/2/0.32769}
*VPLS
Preference: 7
Next hop: via vt-3/2/0.32769, selected
State: <Active Int>
Age: 1:31:53
Task: Common L2 VC
941
AS path: I
vt-3/2/0.32769 (1 entry, 1 announced)
TSI:
KRT in-kernel vt-3/2/0.32769.0
/16 -> {indirect(1048574)}
*VPLS
Preference: 7
Push 800012
State: <Active Int>
Age: 1:31:53
Metric2: 2
Task: Common L2 VC
AS path: I
Push 800012
Next hop: 10.31.1.6 via ge-3/1/0.0 weight 0x1
Metric: 2
Node path count: 1
Nexthop: 10.31.1.6 via ge-3/1/0.0
abcd::10:255:71:52/128 (1 entry, 0 announced)
State: <Active Int>
Local AS:
69
Age: 1:34:07
Task: IF
AS path: I
Local AS:
69
Age: 1:34:07
Task: IF
AS path: I
TSI:
KRT in-kernel ff02::2/128 -> {}
*PIM
Preference: 0
942
Local AS:
69
Age: 1:34:08
Task: PIM Recv6
AS path: I
ff02::d/128 (1 entry, 1 announced)
TSI:
KRT in-kernel ff02::d/128 -> {}
*PIM
Preference: 0
Local AS:
69
Age: 1:34:08
Task: PIM Recv6
AS path: I
TSI:
KRT in-kernel ff02::16/128 -> {}
*MLD
Preference: 0
Local AS:
69
Age: 1:34:06
Task: MLD
AS path: I
private.inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
Age: 1:34:07
Task: IF
AS path: I
10.255.70.103:1:3:1/96 (1 entry, 1 announced)
*BGP
Source: 10.255.70.103
State: <Secondary Active Int Ext>
Local AS:
69 Peer AS:
69
Age: 1:28:12
Metric2: 1
Task: BGP_69.10.255.70.103+179
Announcement bits (1): 0-green-l2vpn
AS path: I
Label-base: 800008, range: 8
Localpref: 100
943
Router ID: 10.255.70.103

10.255.71.52:1:1:1/96 (1 entry, 1 announced)
TSI:
Page 0 idx 0 Type 1 val 8699540
Age: 1:34:03
Metric2: 1
Task: green-l2vpn
AS path: I
Communities: Layer2-info: encaps:VPLS, control flags:Site-Down,
mtu: 0
10.255.71.52:1:5:1/96 (1 entry, 1 announced)
TSI:
Page 0 idx 0 Type 1 val 8699528
Age: 1:34:03
Metric2: 1
Task: green-l2vpn
AS path: I
Communities: Layer2-info: encaps:VPLS, control flags:, mtu: 0
...
TSI:
State: <Active Int>
Local AS:
99
Age: 10:21
Task: l2 circuit
AS path: I

TSI:
KRT queued (pending) add
55.0.0.0/24 -> {Push 300112}
*BGP
944
Address: 0x925c208
Source: 10.0.0.9
Label TTL action: prop-ttl
State: <Active Ext>
Age: 1w0d 23:06:56
AIGP: 25
Task: BGP_13979.10.0.0.9+56732
AS path: 13979 7018 I
Accepted
Route Label: 300112
Localpref: 100
Router ID: 10.9.9.1

(Access Route)
user@host> show route 13.160.0.102 extensive

13.160.0.102/32 (1 entry, 1 announced)
TSI:
KRT in-kernel 13.160.0.102/32 -> {13.160.0.2}
OSPF area : 0.0.0.0, LSA ID : 13.160.0.102, LSA type : Extern
*Access Preference: 13
Next hop: 13.160.0.2 via fe-0/0/0.0, selected
State: <Active Int>
Age: 12
Task: RPD Unix Domain Server./var/run/rpd_serv.local
Announcement bits (2): 0-KRT 1-OSPFv2
AS path: I

(Route Reflector)

TSI:
KRT in-kernel 1.0.0.0/8 -> {indirect(40)}
*BGP
Source: 192.168.4.214
Protocol next hop: 207.17.136.192 Indirect next hop: 84ac908 40
Age: 3:09
Metric: 0
Metric2: 0
Task: BGP_10458.192.168.4.214+1033
Announcement bits (2): 0-KRT 4-Resolve inet.0
AS path: 3944 7777 I <Originator>
Cluster list: 1.1.1.1
Originator ID: 10.255.245.88
Communities: 7777:7777
Localpref: 100
Router ID: 4.4.4.4
Indirect next hop: 84ac908 40
Next hop type: Discard
user@host> show route 20:31:2:0 extensive
945

(FRR and LFA)

State: FlashAll
TSI:
KRT in-kernel 20.31.2.0/24 -> {Push 299776, Push 299792}
*RSVP
Preference: 7/1
Address: 0xbbbc010
Label-switched-path europa-d-to-europa-e
Session Id: 0x201
Session Id: 0x202
State: Active Int
Local AS:
100
Age: 5:31 Metric: 2
Task: RSVP
AS path: I
OSPF
Preference: 10
Address: 0xb9d78c4
Session Id: 0x201
State: Int
Local AS:
100
Age: 5:35 Metric: 3
Area: 0.0.0.0
Task: OSPF
AS path: I

(FRR and LFA)
user@host> show route 20:31:2:0 extensive

State: FlashAll
TSI:
KRT in-kernel 20.31.2.0/24 -> {Push 299776, Push 299792}
*RSVP
Preference: 7/1
Address: 0xbbbc010
Session Id: 0x201
Session Id: 0x202
State: Active Int
Local AS:
100
946
OSPF
Age: 5:31 Metric: 2

Task: RSVP
AS path: I
Preference: 10
Address: 0xb9d78c4
Session Id: 0x201
State: Int
Local AS:
100
Age: 5:35 Metric: 3
Area: 0.0.0.0
Task: OSPF
AS path: I
947
show route flow validation

Syntax
Syntax (EX Series

Switches)
Release Information
Description
Options

<brief | detail>
<ip-prefix>
<table table-name>
<brief | detail>
<ip-prefix>
<table table-name>

Display flow route information.
noneDisplay flow route information.
brief | detail(Optional) Display the specified level of output. If you do not specify a level
of output, the system defaults to brief.

ip-prefix(Optional) IP address for the flow route.

table table-name(Optional) Display flow route information for all routing tables whose
name begins with this string (for example, inet.0 and inet6.0 are both displayed when
you run the show route flow validation inet command).
Required Privilege
Level
Output Fields
view
show route flow validation on page 949

Table 87 on page 948 lists the output fields for the show route flow validation command.
Table 87: show route flow validation Output Fields

Field Name
Field Description
Level of Output
routing-table-name
All levels
prefix
Route address.
All levels
Active unicast route
Active route in the routing table.
All levels
Dependent flow
destinations
Number of flows for which there are routes in the routing table.
All levels
948
Table 87: show route flow validation Output Fields (continued)

Field Name
Field Description
Level of Output
Origin
Source of the route flow.
All levels
Neighbor AS
Autonomous system identifier of the neighbor.
All levels
Flow destination
Number of entries and number of destinations that match the route flow.
All levels
Unicast best match
Destination that is the best match for the route flow.
All levels
Flags
Information about the route flow.
All levels
Sample Output
show route flow
validation
user@host> show route flow validation

inet.0:
10.0.5.0/24Active unicast route
Dependent flow destinations: 1
Origin: 192.168.224.218, Neighbor AS: 65001
Flow destination (3 entries, 1 match origin)
Unicast best match: 10.0.5.0/24
Flags: SubtreeApex Consistent
949
show route forwarding-table

Syntax

<detail | extensive | summary>
<all>
<ccc interface-name>
<destination destination-prefix>
<family family | matching matching>
<interface-name interface-name>
<label name>
<matching matching>
<multicast>
<table (default | logical-system-name/routing-instance-name | routing-instance-name)>
<vlan (all | vlan-name)>
<vpn vpn>
Syntax (MX Series

Routers)

<all>
<bridge-domain (all | domain-name)>
<label name>
<learning-vlan-id learning-vlan-id>
<matching matching>
<multicast>
<table (default | logical-system-name/routing-instance-name | routing-instance-name)>
<vlan (all | vlan-name)>
<vpn vpn>
Syntax (Routing
Matrix)
Release Information
950

<all>
<matching matching>
<label name>
<lcc number>
<multicast>
<table routing-instance-name>
<vpn vpn>

Option bridge-domain introduced in Junos OS Release 7.5
Option learning-vlan-id introduced in Junos OS Release 8.4
Options all and vlan introduced in Junos OS Release 9.6.
Description
Display the Routing Engine's forwarding table, including the network-layer prefixes and
their next hops. This command is used to help verify that the routing protocol process
has relayed the correction information to the forwarding table. The Routing Engine
constructs and maintains one or more routing tables. From the routing tables, the Routing
Engine derives a table of active routes, called the forwarding table.
NOTE: The Routing Engine copies the forwarding table to the Packet
Forwarding Engine, the part of the router that is responsible for forwarding
packets. To display the entries in the Packet Forwarding Engine's forwarding
table, use the show pfe route command.
Options
noneDisplay the routes in the forwarding tables. By default, the show route
forwarding-table command does not display information about private, or internal,
forwarding tables.
detail | extensive | summary(Optional) Display the specified level of output.
all(Optional) Display routing table entries for all forwarding tables, including private,
or internal, tables.
bridge-domain (all | bridge-domain-name)(MX Series routers only) (Optional) Display
route entries for all bridge domains or the specified bridge domain.
ccc interface-name(Optional) Display route entries for the specified circuit cross-connect
interface.
destination destination-prefix(Optional) Destination prefix.
family family(Optional) Display routing table entries for the specified family:
fibre-channel, fmembers, inet, inet6, iso, mpls, tnp, unix, vpls, or vlan-classification.
interface-name interface-name(Optional) Display routing table entries for the specified
interface.
label name(Optional) Display route entries for the specified label.
lcc number(Routing Matrix only) (Optional) On a routing matrix composed of a TX
Matrix Plus router and T640 routers configured in the routing matrix, display
information for the specified T640 router (or line-card chassis) connected to the
TX Matrix router. On a routing matrix composed of the TX Matrix Plus router and
T1600 routers configured in the routing matrix, display information for the specified
T1600 router (or line-card chassis) connected to the TX Matrix Plus router. Replace
number with a value from 0 through 3.
learning-vlan-id learning-vlan-id(MX Series routers only) (Optional) Display learned
information for all VLANs or for the specified VLAN.

matching matching(Optional) Display routing table entries matching the specified prefix
or prefix length.
951
multicast(Optional) Display routing table entries for multicast routes.

table (default | logical-system-name/routing-instance-name |
routing-instance-name)(Optional) Display route entries for all the routing tables in
the main routing instance or for the specified routing instance. If your device supports
logical systems, you can also display route entries for the specified logical system
and routing instance. To view the routing instances on your device, use the show
route instance command.
vlan (all | vlan-name)(Optional) Display information for all VLANs or for the specified
VLAN.
vpn vpn(Optional) Display routing table entries for a specified VPN.
Required Privilege
Level
view
show route forwarding-table on page 955

show route forwarding-table detail on page 955
show route forwarding-table destination extensive (Weights and Balances) on page 956
show route forwarding-table extensive on page 957
show route forwarding-table extensive (RPF) on page 958
show route forwarding-table family mpls on page 960
show route forwarding-table family vpls on page 960
show route forwarding-table family vpls extensive on page 960
show route forwarding-table table default on page 961
show route forwarding-table table
logical-system-name/routing-instance-name on page 962
show route forwarding-table vpn on page 963
Output Fields
Table 88 on page 952 lists the output fields for the show route forwarding-table command.
Output fields are listed in the approximate order in which they appear. Field names might
be abbreviated (as shown in parentheses) when no level of output is specified, or when
the detail keyword is used instead of the extensive keyword.
Table 88: show route forwarding-table Output Fields

Field Name
Field Description
Level of Output
Logical system
Name of the logical system. This field is displayed if you specify the table
logical-system-name/routing-instance-name option on a device that is configured
for and supports logical systems.
All levels
Routing table
Name of the routing table (for example, inet, inet6, mpls).
All levels
Address family
Address family (for example, IP, IPv6, ISO, MPLS, and VPLS).
All levels
Destination
detail extensive
952
Table 88: show route forwarding-table Output Fields (continued)

Field Name
Field Description
Level of Output
Route Type (Type)
How the route was placed into the forwarding table. When the detail keyword
is used, the route type might be abbreviated (as shown in parentheses):
All levels
cloned (clon)(TCP or multicast only) Cloned route.
destination (dest)Remote addresses directly reachable through an interface.
destination down (iddn)Destination route for which the interface is
unreachable.
interface cloned (ifcl)Cloned route for which the interface is unreachable.
route down (ifdn)Interface route for which the interface is unreachable.
ignore (ignr)Ignore this route.
interface (intf)Installed as a result of configuring an interface.
permanent (perm)Routes installed by the kernel when the routing table is
initialized.
userRoutes installed by the routing protocol process or as a result of the
configuration.
Route Reference
(RtRef)
Number of routes to reference.
detail extensive
Flags
Route type flags:
extensive
noneNo flags are enabled.
accountingRoute has accounting enabled.
cachedCache route.
incoming-iface interface-numberCheck against incoming interface.
prefix load balanceLoad balancing is enabled for this prefix.
rt nh decoupledRoute has been decoupled from the next hop to the
destination.
Next hop
sent to PFERoute has been sent to the Packet Forwarding Engine.
staticStatic route.
IP address of the next hop to the destination.
detail extensive
953
Table 88: show route forwarding-table Output Fields (continued)

Field Name
Field Description
Level of Output
Next hop Type

(Type)
Next-hop type. When the detail keyword is used, the next-hop type might be
abbreviated (as indicated in parentheses):
detail extensive
broadcast (bcst)Broadcast.
denyDeny.
discard (dscd) Discard.
holdNext hop is waiting to be resolved into a unicast or multicast type.
indexed (idxd)Indexed next hop.
indirect (indr)Indirect next hop.
local (locl)Local address on an interface.
routed multicast (mcrt)Regular multicast next hop.
multicast (mcst)Wire multicast next hop (limited to the LAN).
multicast discard (mdsc)Multicast discard.
multicast group (mgrp)Multicast group member.
receive (recv)Receive.
reject (rjct)Discard. An ICMP unreachable message was sent.
resolve (rslv)Resolving the next hop.
unicast (ucst)Unicast.
unilist (ulst)List of unicast next hops. A packet sent to this next hop goes
to any next hop in the list.

Index
Software index of the next hop that is used to route the traffic for a given prefix.
Route
interface-index
Logical interface index from which the route is learned. For example, for interface
routes, this is the logical interface index of the route itself. For static routes, this
field is zero. For routes learned through routing protocols, this is the logical
interface index from which the route is learned.
extensive
Reference (NhRef)
Number of routes that refer to this next hop.
Next-hop interface
(Netif)
Interface used to reach the next hop.
Weight
Value used to distinguish primary, secondary, and fast reroute backup routes.
Weight information is available when MPLS label-switched path (LSP) link
protection, node-link protection, or fast reroute is enabled, or when the standby
state is enabled for secondary paths. A lower weight value is preferred. Among
routes with the same weight value, load balancing is possible (see the Balance
field description).
extensive
Balance
Balance coefficient indicating how traffic of unequal cost is distributed among

next hops when a router is performing unequal-cost load balancing. This
information is available when you enable BGP multipath load balancing.
extensive
RPF interface
List of interfaces from which the prefix can be accepted. Reverse path forwarding
(RPF) information is displayed only when rpf-check is configured on the interface.
extensive
954
Sample Output
show route
forwarding-table
user@host> show route forwarding-table

Routing table: default.inet
Internet:
Destination
Type RtRef Next hop
default
perm
0
0.0.0.0/32
perm
0
1.1.1.0/24
ifdn
0
1.1.1.0/32
iddn
0 1.1.1.0
1.1.1.1/32
user
0
1.1.1.1/32
intf
0 1.1.1.1
1.1.1.1/32
iddn
0 1.1.1.1
1.1.1.255/32
iddn
0 ff:ff:ff:ff:ff:ff
10.0.0.0/24
intf
0
10.0.0.0/32
dest
0 10.0.0.0
10.0.0.1/32
intf
0 10.0.0.1
10.0.0.1/32
dest
0 10.0.0.1
10.0.0.255/32
dest
0 10.0.0.255
10.1.1.0/24
ifdn
0
10.1.1.0/32
iddn
0 10.1.1.0
10.1.1.1/32
user
0
10.1.1.1/32
intf
0 10.1.1.1
10.1.1.1/32
iddn
0 10.1.1.1
10.1.1.255/32
iddn
0 ff:ff:ff:ff:ff:ff
10.206.0.0/16
user
0 10.209.63.254
10.209.0.0/16
user
1 0:12:1e:ca:98:0
10.209.0.0/18
intf
0
10.209.0.0/32
dest
0 10.209.0.0
10.209.2.131/32
intf
0 10.209.2.131
10.209.2.131/32
dest
0 10.209.2.131
10.209.17.55/32
dest
0 0:30:48:5b:78:d2
10.209.63.42/32
dest
0 0:23:7d:58:92:ca
10.209.63.254/32
dest
0 0:12:1e:ca:98:0
10.209.63.255/32
dest
0 10.209.63.255
10.227.0.0/16
user
0 10.209.63.254
Type Index NhRef Netif

rjct
46
4
dscd
44
1
rslv
608
1 ge-2/0/1.0
recv
606
1 ge-2/0/1.0
rjct
46
4
locl
607
2
locl
607
2
bcst
605
1 ge-2/0/1.0
rslv
616
1 ge-2/0/0.0
recv
614
1 ge-2/0/0.0
locl
615
2
locl
615
2
bcst
613
1 ge-2/0/0.0
rslv
612
1 ge-2/0/1.0
recv
610
1 ge-2/0/1.0
rjct
46
4
locl
611
2
locl
611
2
bcst
609
1 ge-2/0/1.0
ucst
419
20 fxp0.0
ucst
419
20 fxp0.0
rslv
418
1 fxp0.0
recv
416
1 fxp0.0
locl
417
2
locl
417
2
ucst
435
1 fxp0.0
ucst
434
1 fxp0.0
ucst
419
20 fxp0.0
bcst
415
1 fxp0.0
ucst
419
20 fxp0.0
...
Routing table: iso
ISO:
Destination
Type RtRef Next hop
default
perm
0
rjct
27
1
47.0005.80ff.f800.0000.0108.0003.0102.5524.5220.00
intf
0
locl
28
1
Routing table: inet6
Internet6:
Destination
Type RtRef Next hop
default
perm
0
ff00::/8
perm
0
ff02::1/128
perm
0 ff02::1
Routing table: ccc
MPLS:
Interface.Label
Type RtRef Next hop
default
perm
0
100004(top)fe-0/0/1.0

rjct
6
1
mdsc
4
1
mcst
3
1

rjct 16
1
955
show route
forwarding-table detail
user@host> show route forwarding-table detail

Routing table: inet
Internet:
Destination
Type RtRef Next hop
default
user
2 0:90:69:8e:b1:1b
default
perm
0
10.1.1.0/24
intf
0 ff.3.0.21
10.1.1.0/32
dest
0 10.1.1.0
10.1.1.1/32
intf
0 10.1.1.1
10.1.1.255/32
dest
0 10.1.1.255
10.21.21.0/24
intf
0 ff.3.0.21
10.21.21.0/32
dest
0 10.21.21.0
10.21.21.1/32
intf
0 10.21.21.1
10.21.21.255/32
dest
0 10.21.21.255
127.0.0.1/32
intf
0 127.0.0.1
172.17.28.19/32
clon
1 192.168.4.254
172.17.28.44/32
clon
1 192.168.4.254

ucst
132
4 fxp0.0
rjct
14
1
ucst
322
1 so-5/3/0.0
recv
324
1 so-5/3/0.0
locl
321
1
bcst
323
1 so-5/3/0.0
ucst
326
1 so-5/3/0.0
recv
328
1 so-5/3/0.0
locl
325
1
bcst
327
1 so-5/3/0.0
locl
320
1
ucst
132
4 fxp0.0
ucst
132
4 fxp0.0
...
Routing table: private1__.inet
Internet:
Destination
Type RtRef Next hop
default
perm
0
10.0.0.0/8
intf
0
10.0.0.0/32
dest
0 10.0.0.0
10.0.0.4/32
intf
0 10.0.0.4
10.0.0.4/32
dest
0 10.0.0.4

rjct
46
1
rslv
136
1 fxp1.0
recv
134
1 fxp1.0
locl
135
2
locl
135
2
...
Routing table: iso
ISO:
Destination
Type RtRef Next hop
default
perm
0

rjct
38
1
Routing table: inet6

Internet6:
Destination
Type RtRef Next hop
default
perm
0
ff00::/8
perm
0
ff02::1/128
perm
0 ff02::1

rjct
22
1
mdsc
21
1
mcst
17
1
...
Routing table: mpls
MPLS:
Destination
Type RtRef Next hop
default
perm
0
show route
forwarding-table
destination extensive
956

rjct 28
1
user@host> show route forwarding-table destination 3.4.2.1 extensive

Routing table: inet [Index 0]
Internet:
(Weights and
Balances)
show route
forwarding-table
extensive
Destination: 3.4.2.1/32
Route type: user
Route reference: 0
Flags: sent to PFE
Next-hop type: unilist
Nexthop: 4.4.4.4
Next-hop type: unicast
Next-hop interface: so-1/1/0.0
Nexthop: 145.12.1.2
Route interface-index: 0
Index: 262143
Reference: 1
Index: 335
Weight: 22
Reference: 2
Balance: 3
Index: 337
Weight: 33
Reference: 2
Balance: 33
user@host> show route forwarding-table extensive

Internet:
Destination: default
Route type: user
Route reference: 2
Flags: sent to PFE
Nexthop: 0:90:69:8e:b1:1b
Next-hop interface: fxp0.0
Route type: permanent
Route reference: 0
Flags: none
Next-hop type: reject
Route type: interface
Route reference: 0
Flags: sent to PFE
Nexthop: 127.0.0.1
Next-hop type: local
Index: 132
Reference: 4
Index: 14
Reference: 1
Index: 320
Reference: 1
...
Routing table: private1__.inet [Index 1]
Internet:
Route reference: 0
Flags: sent to PFE
Route reference: 0
Flags: sent to PFE
Next-hop type: resolve
Next-hop interface: fxp1.0
Index: 46
Reference: 1
Index: 136
Reference: 1
...
Routing table: iso [Index 0]
ISO:
Destination:
default
957

Route reference: 0
Flags: sent to PFE
Index: 38
Reference: 1
Routing table: inet6 [Index 0]

Internet6:
Route reference: 0
Flags: sent to PFE
Destination: ff00::/8
Route reference: 0
Flags: sent to PFE
Next-hop type: multicast discard
Index: 22
Index: 21
Reference: 1
Reference: 1
...
Routing table: private1__.inet6 [Index 1]
Internet6:
Route reference: 0
Flags: sent to PFE
Index: 54
Reference: 1
Destination: fe80::2a0:a5ff:fe3d:375/128
Route reference: 0
Flags: sent to PFE
Nexthop: fe80::2a0:a5ff:fe3d:375
Next-hop type: local
Index: 75
Reference: 1
...
show route
forwarding-table
extensive (RPF)
The next example is based on the following configuration, which enables an RPF check
on all routes that are learned from this interface, including the interface route:
so-1/1/0 {
unit 0 {
family inet {
rpf-check;
address 15.95.1.2/30;
}
}
}
user@host> show route forwarding-table extensive
Internet:
...
...
Route type: destination
Route reference: 0
958
Flags: sent to PFE

Nexthop: 15.95.1.3
Next-hop type: broadcast
RPF interface: so-1/1/0.0
Index: 328
Reference: 1
959
show route
forwarding-table
family mpls
user@host> show route forwarding-table family mpls

Routing table: mpls
MPLS:
Destination
Type RtRef Next hop
default
perm
0
0
user
0
1
user
0
2
user
0
100000
user
0 10.31.1.6
800002
user
0
vt-0/3/0.32770 (VPLS)
user

rjct
19
1
recv
18
3
recv
18
3
recv
18
3
swap 100001
fe-1/1/0.0
Pop
vt-0/3/0.32770
indr
351
4
Push 800000, Push 100002(top)
so-0/0/0.0
show route
forwarding-table
family vpls
user@host> show route forwarding-table family vpls

Routing table: green.vpls
VPLS:
Destination
Type RtRef Next hop
default
dynm
0
flood
353
1
default
perm
0
rjct
298
1
fe-0/1/0.0
dynm
0
flood
355
1
00:90:69:0c:20:1f/48
<<<<<Remote CE
dynm
so-0/0/0.0
00:90:69:85:b0:1f/48
<<<<<<Local CE
dynm
show route
forwarding-table
family vpls extensive
ucst
354
2 fe-0/1/0.0
user@host> show route forwarding-table family vpls extensive

Routing table: green.vpls [Index 2]
VPLS:
Route type: dynamic
Route reference: 0
Flags: sent to PFE
Next-hop type: flood
Next-hop interface: fe-0/1/3.0
Route reference: 0
Flags: none
Next-hop type: discard
Destination: fe-0/1/2.0
Route type: dynamic
Route reference: 0
Flags: sent to PFE
Next-hop type: indirect
Next-hop type: Push 800016
960
indr
351
4
Push 800000, Push 100002(top)
Index: 289
Index: 291
Reference: 1
Reference: 3
Index: 290
Reference: 3
Index: 341
Reference: 1
Index: 293
Index: 363
Reference: 1
Reference: 4
Next-hop interface: at-1/0/1.0

Next hop: 10.31.3.2
Destination: fe-0/1/3.0
Route type: dynamic
Route reference: 0
Flags: sent to PFE
Next-hop interface: at-1/0/1.0
Next hop: 10.31.3.2
Index: 301
Reference: 5
Index: 291
Reference: 3
Index: 292
Index: 363
Reference: 1
Reference: 4
Index: 301
Reference: 5
Index: 290
Reference: 3
Destination: 10:00:00:01:01:01/48
Route type: dynamic
Route reference: 0
Flags: sent to PFE, prefix load balance
Index: 291
Reference: 3
Route used as destination:
Packet count:
6640
Byte count:
675786
Route used as source
Packet count:
6894
Byte count:
696424
Destination: 10:00:00:01:01:04/48
Route type: dynamic
Route reference: 0
Index: 290
Reference: 3
Route used as destination:
Packet count:
96
Byte count:
8079
Route used as source:
Packet count:
296
Byte count:
24955
Destination: 10:00:00:01:03:05/48
Route type: dynamic
Route reference: 0
Index: 301
Reference: 5
Next hop: 10.31.3.2
show route
forwarding-table table
default
user@host> show route forwarding-table table default

Routing table: default.inet
Internet:
Destination
Type RtRef Next hop
default
perm
0
0.0.0.0/32
perm
0
10.0.60.0/30
user
0 10.0.60.13

rjct
36
2
dscd
34
1
ucst
713
5 fe-0/1/3.0
961
10.0.60.12/30
10.0.60.12/32
10.0.60.13/32
10.0.60.14/32
10.0.60.14/32
10.0.60.15/32
10.0.67.12/30
10.0.80.0/30
10.0.80.0/32
10.0.80.2/32
10.0.80.2/32
10.0.80.3/32
10.0.90.12/30
10.0.90.12/32
10.0.90.14/32
10.0.90.14/32
10.0.90.15/32
10.5.0.0/16
10.10.0.0/16
10.13.10.0/23
10.84.0.0/16
10.150.0.0/16
10.157.64.0/19
10.209.0.0/16
intf
dest
dest
intf
dest
dest
user
ifdn
dest
user
intf
dest
intf
dest
intf
dest
dest
user
user
user
user
user
user
user
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
10.0.60.12
0:5:85:8b:bc:22
10.0.60.14
10.0.60.14
10.0.60.15
10.0.60.13
ff.3.0.21
10.0.80.0
10.0.80.2
10.0.80.3
10.0.90.12
10.0.90.14
10.0.90.14
10.0.90.15
192.168.187.126
192.168.187.126
192.168.187.126
192.168.187.126
192.168.187.126
192.168.187.126
192.168.187.126
rslv
recv
ucst
locl
locl
bcst
ucst
ucst
recv
rjct
locl
bcst
rslv
recv
locl
locl
bcst
ucst
ucst
ucst
ucst
ucst
ucst
ucst
688
686
713
687
687
685
713
676
678
36
675
677
684
682
683
683
681
324
324
324
324
324
324
324
1
1
5
2
2
1
5
1
1
2
1
1
1
1
2
2
1
15
15
15
15
15
15
15
fe-0/1/3.0
fe-0/1/3.0
fe-0/1/3.0
fe-0/1/3.0
fe-0/1/3.0
so-0/0/1.0
so-0/0/1.0
so-0/0/1.0
fe-0/1/0.0
fe-0/1/0.0
fe-0/1/0.0
fxp0.0
fxp0.0
fxp0.0
fxp0.0
fxp0.0
fxp0.0
fxp0.0
...
show route
forwarding-table table
logc
ial-system-name/routn
i g-n
i stance-name
962
Routing table: default.iso

ISO:
Destination
Type RtRef Next hop
default
perm
0

rjct
60
1
Routing table: default.inet6

Internet6:
Destination
Type RtRef Next hop
default
perm
0
::/128
perm
0
ff00::/8
perm
0
ff02::1/128
perm
0 ff02::1

rjct
44
1
dscd
42
1
mdsc
43
1
mcst
39
1
Routing table: default.mpls

MPLS:
Destination
Type RtRef Next hop
default
perm
0

dscd
50
1
user@host> show route forwarding-table table R4/vpn-red

Logical system: R4
Routing table: vpn-red.inet
Internet:
Destination
Type RtRef Next hop
default
perm
0
rjct
563
1
0.0.0.0/32
perm
0
dscd
561
2
1.0.0.1/32
user
0
dscd
561
2
2.0.2.0/24
intf
0
rslv
771
1 ge-1/2/0.3
2.0.2.0/32
dest
0 2.0.2.0
recv
769
1 ge-1/2/0.3
2.0.2.1/32
intf
0 2.0.2.1
locl
770
2
2.0.2.1/32
dest
0 2.0.2.1
locl
770
2
2.0.2.2/32
dest
0 0.4.80.3.0.1b.c0.d5.e4.bd.0.1b.c0.d5.e4.bc.8.0
ucst
789
1 ge-1/2/0.3
2.0.2.255/32
dest
0 2.0.2.255
bcst
768
1 ge-1/2/0.3
224.0.0.0/4
perm
1
mdsc
562
1
224.0.0.1/32
perm
255.255.255.255/32 perm
show route
forwarding-table vpn
0 224.0.0.1
0
mcst
bcst
558
559
1
1
Logical system: R4
Routing table: vpn-red.iso
ISO:
Destination
Type RtRef Next hop
default
perm
0

rjct
608
1
Logical system: R4
Routing table: vpn-red.inet6
Internet6:
Destination
Type RtRef Next hop
default
perm
0
::/128
perm
0
ff00::/8
perm
0
ff02::1/128
perm
0 ff02::1

rjct
708
1
dscd
706
1
mdsc
707
1
mcst
704
1
Logical system: R4
Routing table: vpn-red.mpls
MPLS:
Destination
Type RtRef Next hop
default
perm
0

dscd
638
user@host> show route forwarding-table vpn VPN-A

Routing table:: VPN-A.inet
Internet:
Destination
Type RtRef Nexthop
default
perm
0
10.39.10.20/30
intf
0 ff.3.0.21
so-0/0/0.0
10.39.10.21/32
intf
0 10.39.10.21
10.255.14.172/32
user
0
so-0/0/0.0
10.255.14.175/32
user
0
100004(top) so-1/0/0.0
224.0.0.0/4
perm
224.0.0.1/32
perm
224.0.0.5/32
user
255.255.255.255/32 perm
2
0 224.0.0.1
1 224.0.0.5
0

rjct
4
4
ucst
40
1
locl
ucst
36
69
1
2
indr
81
3
Push 100004, Push
mdsc
mcst
mcst
bcst
5
1
1
2
3
8
8
3
963
show route hidden

Syntax
Release Information
Description
Options
show route hidden


Display only hidden route information. A hidden route is unusable, even if it is the best
path.


Required Privilege
Level
Output Fields
964
view
show route hidden on page 965

show route hidden detail on page 965
show route hidden extensive on page 966
show route hidden terse on page 966
For information about output fields, see the output field table for the show route
Sample Output
show route hidden
user@host> show route hidden

Restart Complete
127.0.0.1/32
[Direct/0] 04:26:38
> via lo0.0
red.inet.0: 6 destinations, 8 routes (4 active, 0
Restart Complete
10.5.5.5/32
[BGP/170] 03:44:10, localpref
AS path: 100 I
Unusable
10.12.1.0/24
AS path: 100 I
Unusable
10.12.80.4/30
AS path: I
Unusable
...
show route hidden

detail
holddown, 3 hidden)
100, from 10.4.4.4
100, from 10.4.4.4
100, from 10.4.4.4
user@host> show route hidden detail

Restart Complete
State: <Hidden Martian Int>
Local AS:
1
Age: 4:27:37
Task: IF
AS path: I
Restart Complete
BGP
Next hop type: Unusable
State: <Secondary Hidden Int Ext>
Local AS:
1 Peer AS:
1
Age: 3:45:09
Task: BGP_1.10.4.4.4+2493
AS path: 100 I
VPN Label: 100064
Localpref: 100
Router ID: 10.4.4.4
965

...
show route hidden

extensive
The output for the show route hidden extensive command is identical to that of the show
route hidden detail command. For sample output, see show route hidden detail on
page 965.
show route hidden

terse
user@host> show route hidden terse

Restart Complete
A Destination
127.0.0.1/32
P Prf
D
0
Metric 1
Metric 2
Next hop
>lo0.0
AS path

Restart Complete
A Destination
10.5.5.5/32
10.12.1.0/24
10.12.80.4/30
P
B
B
B
Prf
170
170
170
Metric 1
100
100
100
Metric 2
Next hop
Unusable
Unusable
Unusable
AS path
100 I
100 I
I

Restart Complete
Restart Complete
Restart Complete
A Destination
P Prf
10.4.4.4:4:10.5.5.5/32
B 170
10.4.4.4:4:10.12.1.0/24
B 170
10.4.4.4:4:10.12.80.4/30
B 170
Metric 1
Metric 2
Next hop
AS path
100
Unusable
100 I
100
Unusable
100 I
100
Unusable

Restart Complete
private1__.inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
966
show route inactive-path

Syntax
Syntax (EX Series

Switches)
Release Information
Description
Options


Display routes for destinations that have no active route. An inactive route is a route that
was not selected as the best path.
noneDisplay all inactive routes.


Required Privilege
Level
Output Fields
view
show route inactive-path on page 968

show route inactive-path detail on page 968
show route inactive-path extensive on page 969
show route inactive-path terse on page 969
967
Sample Output
show route
inactive-path
user@host> show route inactive-path

Restart Complete
10.12.100.12/30
[OSPF/10] 03:57:28, metric 1

> via so-0/3/0.0

10.0.0.0/8
[Direct/0] 04:39:56
> via fxp1.0

Restart Complete
10.12.80.0/30
[BGP/170] 04:38:17, localpref 100

AS path: 100 I
> to 10.12.80.1 via ge-6/3/2.0

Restart Complete
Restart Complete
Restart Complete
Restart Complete
show route
inactive-path detail
user@host> show route inactive-path detail

Restart Complete
OSPF
Preference: 10
State: <Int>
Local AS:
1
Age: 3:58:24
Metric: 1
Area: 0.0.0.0
Task: OSPF
AS path: I
968
State: <NotBest Int>
Inactive reason: No difference
Age: 4:40:52
Task: IF
AS path: I
Restart Complete
BGP
Source: 10.12.80.1
State: <Ext>
Peer AS:
100
Age: 4:39:13
Task: BGP_100.10.12.80.1+179
AS path: 100 I
Localpref: 100
Router ID: 10.0.0.0
show route
inactive-path
extensive
The output for the show route inactive-path extensive command is identical to that of
the show route inactive-path detail command. For sample output, see show route
inactive-path detail on page 968.
show route
inactive-path terse
user@host> show route inactive-path terse

Restart Complete
A Destination
10.12.100.12/30
P Prf
O 10
Metric 1
1
Metric 2
Next hop
>so-0/3/0.0
AS path

A Destination
10.0.0.0/8
P Prf
D
0
Metric 1
Metric 2
Next hop
>fxp1.0
AS path

Restart Complete
A Destination
10.12.80.0/30
P Prf
B 170
Metric 1
100
Metric 2
Next hop
>10.12.80.1
AS path
100 I

Restart Complete
Restart Complete
969

Restart Complete
Restart Complete
970
show route inactive-prefix

Syntax
Syntax (EX Series

Switches)
Release Information
Description
Options


Display inactive route destinations in each routing table.
noneDisplay all inactive route destination.


Required Privilege
Level
Output Fields
view
show route inactive-prefix on page 972

show route inactive-prefix detail on page 972
show route inactive-prefix extensive on page 972
show route inactive-prefix terse on page 972
971
Sample Output
show route
inactive-prefix
user@host> show route inactive-prefix

127.0.0.1/32
show route
inactive-prefix detail
[Direct/0] 00:04:54
> via lo0.0
user@host> show route inactive-prefix detail

State: <Hidden Martian Int>
Age: 4:51
Task: IF
AS path: I00:04:54
> via lo0.0
show route
inactive-prefix
extensive
The output for the show route inactive-prefix extensive command is identical to that of
the show route inactive-path detail command. For sample output, see show route
inactive-prefix detail on page 972.
show route
inactive-prefix terse
user@host> show route inactive-prefix terse

A Destination
127.0.0.1/32
972
P Prf
D
0
Metric 1
Metric 2
Next hop
>lo0.0
AS path
show route instance

Syntax
Syntax (EX Series

Switches and QFX
Series)
Release Information
Description
Options
show route instance

<brief | detail | summary>
<instance-name>
<operational>
show route instance
<brief | detail | summary>
<instance-name>
<operational>

Display routing instance information.
none(Same as brief) Display standard information about all routing instances.
brief | detail | summary(Optional) Display the specified level of output. If you do not
specify a level of output, the system defaults to brief. (These options are not available
with the operational keyword.)
instance-name(Optional) Display information for all routing instances whose name
begins with this string (for example, cust1, cust11, and cust111 are all displayed when
you run the show route instance cust1 command).

operational(Optional) Display operational routing instances.
Required Privilege
Level
Output Fields
view
show route instance on page 975

show route instance detail (Graceful Restart Complete) on page 975
show route instance detail (Graceful Restart Incomplete) on page 977
show route instance detail (VPLS Routing Instance) on page 978
show route instance operational on page 979
show route instance summary on page 979
Table 89 on page 973 lists the output fields for the show route instance command. Output
Table 89: show route instance Output Fields

Field Name
Field Description
Level of Output
Instance or instance-name
Name of the routing instance.
All levels
973
Table 89: show route instance Output Fields (continued)

Field Name
Field Description
Level of Output
Operational Routing Instances
(operational keyword only) Names of all operational routing instances.
Type
Type of routing instance: forwarding, l2vpn, no-forwarding, vpls,

virtual-router, or vrf.
All levels
State
State of the routing instance: active or inactive.
brief detail none
Interfaces
Name of interfaces belonging to this routing instance.
brief detail none
Restart State
Status of graceful restart for this instance: Pending or Complete.
detail
Path selection timeout
Maximum amount of time, in seconds, remaining until graceful restart

is declared complete. The default is 300.
detail
Tables
Tables (and number of routes) associated with this routing instance.
brief detail none
Route-distinguisher
Unique route distinguisher associated with this routing instance.
detail
Vrf-import
VPN routing and forwarding instance import policy name.
detail
Vrf-export
VPN routing and forwarding instance export policy name.
detail
Vrf-import-target
VPN routing and forwarding instance import target community name.
detail
Vrf-export-target
VPN routing and forwarding instance export target community name.
detail
Fast-reroute-priority
Fast reroute priority setting for a VPLS routing instance: high, medium,
or low. The default is low.
detail
Restart State
Restart state:
detail
Pending:protocol-nameList of protocols that have not yet
completed graceful restart for this routing table.
CompleteAll protocols have restarted for this routing table.
Primary rib
Primary table for this routing instance.
brief none summary
Active/holddown/hidden
Number of active, hold-down, and hidden routes.
All levels
974
Sample Output
show route instance
show route instance

detail (Graceful
Restart Complete)
user@host> show route instance

Instance
Type
Primary RIB
master
forwarding
inet.0
iso.0
mpls.0
inet6.0
l2circuit.0
__juniper_private1__ forwarding
__juniper_private1__.inet.0
__juniper_private1__.inet6.0
16/0/1
1/0/0
0/0/0
2/0/0
0/0/0
12/0/0
1/0/0
user@host> show route instance detail

master:
Router ID: 10.255.14.176
Type: forwarding
State: Active
Restart State: Complete Path selection timeout: 300
Tables:
inet.0
: 17 routes (15 active, 0 holddown,
Restart Complete
inet.3
: 2 routes (2 active, 0 holddown, 0
Restart Complete
iso.0
Restart Complete
mpls.0
Restart Complete
bgp.l3vpn.0
Restart Complete
inet6.0
Restart Complete
bgp.l2vpn.0
Restart Complete
BGP-INET:
Router ID: 10.69.103.1
Type: vrf
State: Active
Interfaces:
t3-0/0/0.103
Route-distinguisher: 10.255.14.176:103
Vrf-import: [ BGP-INET-import ]
Vrf-export: [ BGP-INET-export ]
Tables:
BGP-INET.inet.0
Restart Complete
BGP-L:
Router ID: 10.69.104.1
Type: vrf
State: Active
Interfaces:
t3-0/0/0.104
Vrf-import: [ BGP-L-import ]
Vrf-export: [ BGP-L-export ]
Tables:
BGP-L.inet.0
Restart Complete
1 hidden)
hidden)
hidden)
0 hidden)
0 hidden)
hidden)
hidden)
hidden)
hidden)
975
BGP-L.mpls.0
: 3 routes (3
Restart Complete
L2VPN:
Router ID: 0.0.0.0
Type: l2vpn
State: Active
Restart State: Complete Path selection
Interfaces:
t3-0/0/0.512
Vrf-import: [ L2VPN-import ]
Vrf-export: [ L2VPN-export ]
Tables:
L2VPN.l2vpn.0
: 2 routes (2
Restart Complete
LDP:
Router ID: 10.69.105.1
Type: vrf
State: Active
Interfaces:
t3-0/0/0.105
Vrf-import: [ LDP-import ]
Vrf-export: [ LDP-export ]
Tables:
LDP.inet.0
: 5 routes (4
Restart Complete
OSPF:
Router ID: 10.69.101.1
Type: vrf
State: Active
Interfaces:
t3-0/0/0.101
Vrf-import: [ OSPF-import ]
Vrf-export: [ OSPF-export ]
Vrf-import-target: [ target:11111
Tables:
OSPF.inet.0
: 8 routes (7
Restart Complete
RIP:
Router ID: 10.69.102.1
Type: vrf
State: Active
Interfaces:
t3-0/0/0.102
Vrf-import: [ RIP-import ]
Vrf-export: [ RIP-export ]
Tables:
RIP.inet.0
: 6 routes (6
Restart Complete
STATIC:
Router ID: 10.69.100.1
Type: vrf
State: Active
Interfaces:
t3-0/0/0.100
Vrf-import: [ STATIC-import ]
Vrf-export: [ STATIC-export ]
Tables:
976
active, 0 holddown, 0 hidden)
timeout: 300
timeout: 300
timeout: 300
timeout: 300
timeout: 300
STATIC.inet.0
Restart Complete
show route instance

detail (Graceful
Restart Incomplete)
: 4 routes (4 active, 0 holddown, 0 hidden)
user@host> show route instance detail

master:
Router ID: 10.255.14.176
Type: forwarding
State: Active
Restart State: Pending Path selection timeout: 300
Tables:
inet.0
Restart Pending: OSPF LDP
inet.3
Restart Pending: OSPF LDP
iso.0
Restart Complete
mpls.0
Restart Pending: LDP VPN
bgp.l3vpn.0
Restart Pending: BGP VPN
inet6.0
Restart Complete
bgp.l2vpn.0
Restart Pending: BGP VPN
BGP-INET:
Router ID: 10.69.103.1
Type: vrf
State: Active
Interfaces:
t3-0/0/0.103
Vrf-import: [ BGP-INET-import ]
Vrf-export: [ BGP-INET-export ]
Tables:
BGP-INET.inet.0
Restart Pending: VPN
BGP-L:
Router ID: 10.69.104.1
Type: vrf
State: Active
Interfaces:
t3-0/0/0.104
Vrf-import: [ BGP-L-import ]
Vrf-export: [ BGP-L-export ]
Tables:
BGP-L.inet.0
BGP-L.mpls.0
L2VPN:
Router ID: 0.0.0.0
Type: l2vpn
State: Active
Interfaces:
t3-0/0/0.512
Vrf-import: [ L2VPN-import ]
Vrf-export: [ L2VPN-export ]
Tables:
L2VPN.l2vpn.0
Restart Pending: VPN L2VPN
1 hidden)
hidden)
hidden)
0 hidden)
0 hidden)
hidden)
hidden)
hidden)
hidden)
hidden)
hidden)
977
LDP:
Router ID: 10.69.105.1
Type: vrf
State: Active
Restart State: Pending Path selection
Interfaces:
t3-0/0/0.105
Vrf-import: [ LDP-import ]
Vrf-export: [ LDP-export ]
Tables:
LDP.inet.0
: 5 routes (4
Restart Pending: OSPF LDP VPN
OSPF:
Router ID: 10.69.101.1
Type: vrf
State: Active
Interfaces:
t3-0/0/0.101
Vrf-import: [ OSPF-import ]
Vrf-export: [ OSPF-export ]
Tables:
OSPF.inet.0
: 8 routes (7
Restart Pending: OSPF VPN
RIP:
Router ID: 10.69.102.1
Type: vrf
State: Active
Interfaces:
t3-0/0/0.102
Vrf-import: [ RIP-import ]
Vrf-export: [ RIP-export ]
Tables:
RIP.inet.0
: 8 routes (6
Restart Pending: RIP VPN
STATIC:
Router ID: 10.69.100.1
Type: vrf
State: Active
Interfaces:
t3-0/0/0.100
Vrf-import: [ STATIC-import ]
Vrf-export: [ STATIC-export ]
Tables:
STATIC.inet.0
: 4 routes (4
show route instance

detail (VPLS Routing
Instance)
978
timeout: 300
timeout: 300
timeout: 300
timeout: 300
user@host> show route instance detail test-vpls

test-vpls:
Router ID: 0.0.0.0
Type: vpls
State: Active
Interfaces:
lsi.1048833
lsi.1048832
fe-0/1/0.513
Vrf-import: [ __vrf-import-test-vpls-internal__ ]
Vrf-export: [ __vrf-export-test-vpls-internal__ ]
Vrf-import-target: [ target:300:1 ]
Vrf-export-target: [ target:300:1 ]
Fast-reroute-priority: high
Tables:
test-vpls.l2vpn.0
: 3 routes (3 active, 0 holddown, 0 hidden)
show route instance

operational
user@host> show route instance operational

Operational Routing Instances:
master
default
show route instance

summary
user@host> show route instance summary

Instance
Type
Primary rib
master
forwarding
inet.0
iso.0
mpls.0
l3vpn.0
inet6.0
l2vpn.0
l2circuit.0
BGP-INET
vrf
BGP-INET.inet.0
BGP-INET.iso.0
BGP-INET.inet6.0
BGP-L
vrf
BGP-L.inet.0
BGP-L.iso.0
BGP-L.mpls.0
BGP-L.inet6.0
L2VPN
l2vpn
L2VPN.inet.0
L2VPN.iso.0
L2VPN.inet6.0
L2VPN.l2vpn.0
LDP
vrf
LDP.inet.0
LDP.iso.0
LDP.mpls.0
LDP.inet6.0
LDP.l2circuit.0
OSPF
vrf
OSPF.inet.0
OSPF.iso.0
OSPF.inet6.0
RIP
vrf
RIP.inet.0
RIP.iso.0
RIP.inet6.0
STATIC
vrf
STATIC.inet.0
STATIC.iso.0
STATIC.inet6.0
15/0/1
1/0/0
35/0/0
0/0/0
2/0/0
0/0/0
0/0/0
5/0/0
0/0/0
0/0/0
5/0/0
0/0/0
4/0/0
0/0/0
0/0/0
0/0/0
0/0/0
2/0/0
4/0/0
0/0/0
0/0/0
0/0/0
0/0/0
7/0/0
0/0/0
0/0/0
6/0/0
0/0/0
0/0/0
4/0/0
0/0/0
0/0/0
979
show route next-hop

Syntax
Syntax (EX Series

Switches)
Release Information
Description
Options
show route next-hop next-hop

show route next-hop next-hop

Display the entries in the routing table that are being sent to the specified next-hop
address.
brief | detail | extensive | terse(Optional) Display the specified level of ouput.

next-hopNext-hop address.
Required Privilege
Level
Output Fields
980
view
show route next-hop on page 981

show route next-hop detail on page 981
show route next-hop extensive on page 983
show route next-hop terse on page 985
Sample Output
show route next-hop
user@host> show route next-hop 192.168.71.254

Restart Complete
10.10.0.0/16
10.209.0.0/16
172.16.0.0/12
192.168.0.0/16
192.168.102.0/23
207.17.136.0/24
207.17.136.192/32
*[Static/5] 06:26:25
> to 192.168.71.254
*[Static/5] 06:26:25
> to 192.168.71.254
*[Static/5] 06:26:25
> to 192.168.71.254
*[Static/5] 06:26:25
> to 192.168.71.254
*[Static/5] 06:26:25
> to 192.168.71.254
*[Static/5] 06:26:25
> to 192.168.71.254
*[Static/5] 06:26:25
> to 192.168.71.254
via fxp0.0
via fxp0.0
via fxp0.0
via fxp0.0
via fxp0.0
via fxp0.0
via fxp0.0

Restart Complete
Restart Complete
Restart Complete
Restart Complete
show route next-hop

detail
user@host> show route next-hop 192.168.71.254 detail

Restart Complete
Local AS:
1
Age: 6:27:41
Task: RT
Announcement bits (3): 0-KRT 3-Resolve tree 1 5-Resolve tree 2
AS path: I
10.209.0.0/16 (1 entry, 1 announced)
981
Local AS:
1
Age: 6:27:41
Task: RT
AS path: I
172.16.0.0/12 (1 entry, 1 announced)
Local AS:
1
Age: 6:27:41
Task: RT
AS path: I
192.168.0.0/16 (1 entry, 1 announced)
Local AS:
1
Age: 6:27:41
Task: RT
AS path: I
192.168.102.0/23 (1 entry, 1 announced)
Local AS:
1
Age: 6:27:41
Task: RT
AS path: I
207.17.136.0/24 (1 entry, 1 announced)
Local AS:
1
Age: 6:27:41
Task: RT
AS path: I
207.17.136.192/32 (1 entry, 1 announced)
Local AS:
1
Age: 6:27:41
Task: RT
AS path: I
982

Restart Complete
Restart Complete
Restart Complete
Restart Complete
show route next-hop

extensive
user@host> show route next-hop 192.168.71.254 extensive

TSI:
KRT in-kernel 10.10.0.0/16 -> {192.168.71.254}
Local AS:
69
Age: 2:02:28
Task: RT
AS path: I
10.209.0.0/16 (1 entry, 1 announced)
TSI:
KRT in-kernel 10.209.0.0/16 -> {192.168.71.254}
Local AS:
69
Age: 2:02:28
Task: RT
AS path: I
172.16.0.0/12 (1 entry, 1 announced)
TSI:
KRT in-kernel 172.16.0.0/12 -> {192.168.71.254}
Local AS:
69
Age: 2:02:28
Task: RT
AS path: I
192.168.0.0/16 (1 entry, 1 announced)
TSI:
KRT in-kernel 192.168.0.0/16 -> {192.168.71.254}
983
Local AS:
69
Age: 2:02:28
Task: RT
AS path: I
192.168.102.0/23 (1 entry, 1 announced)
TSI:
KRT in-kernel 192.168.102.0/23 -> {192.168.71.254}
Local AS:
69
Age: 2:02:28
Task: RT
AS path: I
207.17.136.0/24 (1 entry, 1 announced)
TSI:
KRT in-kernel 207.17.136.0/24 -> {192.168.71.254}
Local AS:
69
Age: 2:02:28
Task: RT
AS path: I
207.17.136.192/32 (1 entry, 1 announced)
TSI:
KRT in-kernel 207.17.136.192/32 -> {192.168.71.254}
Local AS:
69
Age: 2:02:28
Task: RT
AS path: I
984
red.l2vpn.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
show route next-hop

terse
user@host> show route next-hop 192.168.71.254 terse

Restart Complete
A
*
*
*
*
*
*
*
Destination
10.10.0.0/16
10.209.0.0/16
172.16.0.0/12
192.168.0.0/16
192.168.102.0/23
207.17.136.0/24
207.17.136.192/32
P Prf
S
5
S
5
S
5
S
5
S
5
S
5
S
5
Metric 1
Metric 2
Next hop
>192.168.71.254
>192.168.71.254
>192.168.71.254
>192.168.71.254
>192.168.71.254
>192.168.71.254
>192.168.71.254
AS path

Restart Complete
Restart Complete
Restart Complete
Restart Complete
985
show route no-community

Syntax
Syntax (EX Series

Switches)
Release Information
Description
Options


Display the route entries in each routing table that are not associated with any community.
none(Same as brief) Display the route entries in each routing table that are not
associated with any community.


Required Privilege
Level
Output Fields
986
view
show route no-community on page 987

show route no-community detail on page 987
show route no-community extensive on page 987
show route no-community terse on page 988
Sample Output
show route
no-community
user@host> show route no-community

10.10.0.0/16
10.209.0.0/16
10.255.71.52/32
10.255.71.63/32
10.255.71.64/32
10.255.71.240/32
10.255.71.241/32
10.255.71.242/32
12.1.1.0/24
14.1.1.0/24
16.1.1.0/24
*[Static/5] 00:36:27
> to 192.168.71.254 via fxp0.0
*[Static/5] 00:36:27
> to 192.168.71.254 via fxp0.0
*[Direct/0] 00:36:27
> via lo0.0
*[OSPF/10] 00:04:39, metric 1
> to 35.1.1.2 via ge-3/1/0.0
*[OSPF/10] 00:00:08, metric 2
> to 35.1.1.2 via ge-3/1/0.0
*[OSPF/10] 00:05:04, metric 2
via so-0/1/2.0
> via so-0/3/2.0
*[OSPF/10] 00:05:14, metric 1
> via so-0/1/2.0
*[OSPF/10] 00:05:19, metric 1
> via so-0/3/2.0
*[OSPF/10] 00:05:14, metric 2
> via so-0/3/2.0
*[OSPF/10] 00:00:08, metric 3
> to 35.1.1.2 via ge-3/1/0.0
via so-0/1/2.0
via so-0/3/2.0
*[OSPF/10] 00:05:14, metric 2
> via so-0/1/2.0
.....
show route
no-community detail
user@host> show route no-community detail

Age: 38:08
Task: RT
AS path: I
10.209.0.0/16 (1 entry, 1 announced)
Age: 38:08
Task: RT
AS path: I
....
user@host> show route no-community extensive
987
show route
no-community
extensive

TSI:
KRT in-kernel 10.10.0.0/16 -> {192.168.71.254}
Local AS:
69
Age: 2:03:33
Task: RT
AS path: I
10.209.0.0/16 (1 entry, 1 announced)
TSI:
KRT in-kernel 10.209.0.0/16 -> {192.168.71.254}
Local AS:
69
Age: 2:03:33
Task: RT
AS path: I
show route
no-community terse
user@host> show route no-community terse

A
*
*
*
*
*
*
Destination
10.10.0.0/16
10.209.0.0/16
10.255.71.52/32
10.255.71.63/32
10.255.71.64/32
10.255.71.240/32
P Prf
S
5
S
5
D
0
O 10
O 10
O 10
*
*
*
*
10.255.71.241/32
10.255.71.242/32
12.1.1.0/24
14.1.1.0/24
O
O
O
O
10
10
10
10
1
1
2
3
10
* 16.1.1.0/24
...
988
Metric 1
1
2
2
Metric 2
Next hop
>192.168.71.254
>192.168.71.254
>lo0.0
>35.1.1.2
>35.1.1.2
so-0/1/2.0
>so-0/3/2.0
>so-0/1/2.0
>so-0/3/2.0
>so-0/3/2.0
>35.1.1.2
so-0/1/2.0
so-0/3/2.0
>so-0/1/2.0
AS path
show route output

Syntax
show route output (address ip-address | interface interface-name)

Syntax (EX Series

Switches)
show route output (address ip-address | interface interface-name)

Release Information
Description

Display the entries in the routing table learned through static routes and interior gateway
protocols that are to be sent out the interface with either the specified IP address or
specified name.
To view routes advertised to a neighbor or received from a neighbor for the BGP protocol,
use the show route advertising-protocol bgp and show route receive-protocol bgp
commands instead.
Options
address ip-addressDisplay entries in the routing table that are to be sent out the interface
with the specified IP address.


interface interface-nameDisplay entries in the routing table that are to be sent out the
interface with the specified name.


Required Privilege
Level
Output Fields
view
show route output address on page 990

show route output address detail on page 990
show route output address extensive on page 990
show route output address terse on page 990
show route output interface on page 991
show route output interface detail on page 991
show route output interface extensive on page 992
show route output interface terse on page 992
989
Sample Output
show route output
address
user@host> show route output address 36.1.1.1/24

36.1.1.0/24
*[Direct/0] 00:19:56
> via so-0/1/2.0
[OSPF/10] 00:19:55, metric 1
> via so-0/1/2.0

show route output

address detail
user@host> show route output address 36.1.1.1 detail

State: <Active Int>
Age: 23:00
Task: IF
AS path: I
OSPF
Preference: 10
State: <Int>
Age: 22:59
Metric: 1
Area: 0.0.0.0
Task: OSPF
AS path: I
show route output

address extensive
990
The output for the show route output address extensive command is identical to that of
the show route output address detail command. For sample output, see show route
output address detail on page 990.
show route output

address terse
user@host> show route output address 36.1.1.1 terse

A Destination
* 36.1.1.0/24
P Prf
D
0
O 10
Metric 1
Metric 2
Next hop
>so-0/1/2.0
>so-0/1/2.0
AS path

show route output

interface
user@host> show route output interface so-0/1/2.0

10.255.71.240/32
10.255.71.241/32
14.1.1.0/24
16.1.1.0/24
36.1.1.0/24
*[OSPF/10] 00:13:00, metric 2

via so-0/1/2.0
> via so-0/3/2.0
*[OSPF/10] 00:13:10, metric 1
> via so-0/1/2.0
*[OSPF/10] 00:05:11, metric 3
to 35.1.1.2 via ge-3/1/0.0
> via so-0/1/2.0
via so-0/3/2.0
*[OSPF/10] 00:13:10, metric 2
> via so-0/1/2.0
*[Direct/0] 00:13:21
> via so-0/1/2.0
[OSPF/10] 00:13:20, metric 1
> via so-0/1/2.0

show route output

interface detail
user@host> show route output interface so-0/1/2.0 detail

10.255.71.240/32 (1 entry, 1 announced)
*OSPF
Preference: 10
State: <Active Int>
Age: 14:52
Metric: 2
991
Area: 0.0.0.0
Task: OSPF
AS path: I
10.255.71.241/32 (1 entry, 1 announced)
*OSPF
Preference: 10
State: <Active Int>
Age: 15:02
Metric: 1
Area: 0.0.0.0
Task: OSPF
AS path: I
...
show route output

interface extensive
The output for the show route output interface extensive command is identical to that of
the show route output interface detail command. For sample output, see show route
output interface detail on page 991.
show route output

interface terse
user@host> show route output interface so-0/1/2.0 terse

A Destination
* 10.255.71.240/32
P Prf
O 10
Metric 1
2
* 10.255.71.241/32
* 14.1.1.0/24
O
O
10
10
1
3
* 16.1.1.0/24
* 36.1.1.0/24
O
D
O
10
0
10
2
1
Metric 2
Next hop
so-0/1/2.0
>so-0/3/2.0
>so-0/1/2.0
35.1.1.2
>so-0/1/2.0
so-0/3/2.0
>so-0/1/2.0
>so-0/1/2.0
>so-0/1/2.0
AS path

992
show route protocol

Syntax
Syntax (EX Series

Switches)
Release Information
show route protocol protocol

show route protocol protocol

opsf2 and ospf3 options introduced in Junos OS Release 9.2.
opsf2 and ospf3 options introduced in Junos OS Release 9.2 for EX Series switches.
flow option introduced in Junos OS Release 10.0.
flow option introduced in Junos OS Release 10.0 for EX Series switches.
Description
Display the route entries in the routing table that were learned from a particular protocol.
Options


protocolProtocol from which the route was learned:
accessAccess route for use by DHCP application
access-internalAccess-internal route for use by DHCP application
aggregateLocally generated aggregate route
arpRoute learned through the Address Resolution Protocol
atmvpnAsynchronous Transfer Mode virtual private network
bgpBorder Gateway Protocol
cccCircuit cross-connect
directDirectly connected route
dvmrpDistance Vector Multicast Routing Protocol
esisEnd System-to-Intermediate System
flowLocally defined flow-specification route
frrPrecomputed protection route or backup route used when a link goes down
isisIntermediate System-to-Intermediate System
ldpLabel Distribution Protocol
l2circuitLayer 2 circuit
l2vpnLayer 2 virtual private network
993
localLocal address
mplsMultiprotocol Label Switching
msdpMulticast Source Discovery Protocol
ospfOpen Shortest Path First versions 2 and 3
ospf2Open Shortest Path First versions 2 only
ospf3Open Shortest Path First version 3 only
pimProtocol Independent Multicast
ripRouting Information Protocol
ripngRouting Information Protocol next generation
rsvpResource Reservation Protocol
rtargetLocal route target virtual private network
staticStatically defined route
tunnelDynamic tunnel
vpnVirtual private network
NOTE: EX Series switches run a subset of these protocols. See the switch
CLI for details.
Required Privilege
Level
994
view
show route protocol access on page 996

show route protocol access-internal extensive on page 996
show route protocol arp on page 996
show route protocol bgp on page 997
show route protocol bgp detail on page 997
show route protocol bgp extensive on page 997
show route protocol bgp terse on page 998
show route protocol direct on page 998
show route protocol frr on page 998
show route protocol l2circuit detail on page 999
show route protocol l2vpn extensive on page 1000
show route protocol ldp on page 1000
show route protocol ldp extensive on page 1001
show route protocol ospf (Layer 3 VPN) on page 1002
show route protocol ospf detail on page 1002
show route protocol rip on page 1003
show route protocol rip detail on page 1003
show route protocol ripng table inet6 on page 1003
show route protocol static detail on page 1003
Output Fields
995
Sample Output
show route protocol
access
user@host> show route protocol access

13.160.0.3/32
13.160.0.4/32
13.160.0.5/32
*[Access/13] 00:00:09
> to 13.160.0.2 via fe-0/0/0.0
*[Access/13] 00:00:09
> to 13.160.0.2 via fe-0/0/0.0
*[Access/13] 00:00:09
> to 13.160.0.2 via fe-0/0/0.0
show route protocol

access-internal
extensive
user@host> show route protocol access-internal 13.160.0.19 extensive

13.160.0.19/32 (1 entry, 1 announced)
TSI:
KRT in-kernel 13.160.0.19/32 -> {13.160.0.2}
*Access-internal Preference: 12
State: <Active Int>
Age: 36
Task: RPD Unix Domain Server./var/run/rpd_serv.local
AS path: I
show route protocol

arp
user@host> show route protocol arp

cust1.inet.0: 1033 destinations, 2043 routes (1033 active, 0 holddown, 0 hidden)
20.20.1.3/32
20.20.1.4/32
20.20.1.5/32
20.20.1.6/32
20.20.1.7/32
20.20.1.8/32
20.20.1.9/32
20.20.1.10/32
20.20.1.11/32
20.20.1.12/32
20.20.1.13/32
[ARP/4294967293]
Unusable
[ARP/4294967293]
Unusable
[ARP/4294967293]
Unusable
[ARP/4294967293]
Unusable
[ARP/4294967293]
Unusable
[ARP/4294967293]
Unusable
[ARP/4294967293]
Unusable
[ARP/4294967293]
Unusable
[ARP/4294967293]
Unusable
[ARP/4294967293]
Unusable
[ARP/4294967293]
Unusable
00:04:35, from 20.20.1.1

00:04:35, from 20.20.1.1
00:04:32, from 20.20.1.1
00:04:34, from 20.20.1.1
00:04:35, from 20.20.1.1
00:04:35, from 20.20.1.1
00:04:35, from 20.20.1.1
00:04:35, from 20.20.1.1
00:04:33, from 20.20.1.1
00:04:33, from 20.20.1.1
00:04:33, from 20.20.1.1
...
996
show route protocol

bgp
user@host> show route protocol bgp 192.168.64.0/21

192.168.64.0/21
*[BGP/170] 6d 10:41:16, localpref 100, from 192.168.69.71

AS path: 10458 14203 2914 4788 4788 I
> to 192.168.167.254 via fxp0.0
show route protocol

bgp detail
user@host> show route protocol bgp 66.117.63.0/24 detail

66.117.63.0/24 (1 entry, 1 announced)
*BGP
Source: 192.168.69.71
Indirect next hop: 8e166c0 342
State: <Active Ext>
Local AS:
69 Peer AS: 10458
Age: 6d 10:42:42
Metric2: 0
Task: BGP_10458.192.168.69.71+179
Announcement bits (3): 0-KRT 2-BGP RT Background 3-Resolve tree
1
AS path: 10458 14203 2914 4788 4788 I
Communities: 2914:410 2914:2403 2914:3400
Accepted
Localpref: 100
Router ID: 207.17.136.192
show route protocol

bgp extensive
user@host> show route protocol bgp 192.168.64.0/21 extensive

192.168.64.0/21 (1 entry, 1 announced)
TSI:
KRT in-kernel 1.9.0.0/16 -> {indirect(342)}
Page 0 idx 1 Type 1 val db31a80
Nexthop: Self
AS path: [69] 10458 14203 2914 4788 4788 I
Communities: 2914:410 2914:2403 2914:3400
Path 1.9.0.0 from 192.168.69.71 Vector len 4. Val: 1
*BGP
Source: 192.168.69.71
State: <Active Ext>
Local AS:
69 Peer AS: 10458
Age: 6d 10:44:45
Metric2: 0
Task: BGP_10458.192.168.69.71+179
Announcement bits (3): 0-KRT 2-BGP RT Background 3-Resolve tree
1
AS path: 10458 14203 2914 4788 4788 I
Communities: 2914:410 2914:2403 2914:3400
997
Accepted
Localpref: 100
Router ID: 207.17.136.192
Next hop: 192.168.167.254 via fxp0.0
Node path count: 1
Nexthop: 192.168.167.254 via fxp0.0
show route protocol

bgp terse
user@host> show route protocol bgp 192.168.64.0/21 terse

A Destination
192.168.64.0/21
show route protocol

direct
P Prf
B 170
Metric 1
100
Metric 2
Next hop
>100.1.3.2
AS path
10023 21 I
user@host> show route protocol direct

8.8.8.0/24
10.255.165.1/32
30.30.30.0/24
192.168.164.0/22
*[Direct/0] 17w0d
> via fe-1/3/1.0
*[Direct/0] 25w4d
> via lo0.0
*[Direct/0] 17w0d
> via fe-1/3/2.0
*[Direct/0] 25w4d
> via fxp0.0
10:31:49
04:13:18
23:06:26
04:13:20

47.0005.80ff.f800.0000.0108.0001.0102.5516.5001/152
*[Direct/0] 25w4d 04:13:21
> via lo0.0
abcd::10:255:165:1/128
*[Direct/0] 25w4d 04:13:21
> via lo0.0
fe80::2a0:a5ff:fe12:ad7/128
*[Direct/0] 25w4d 04:13:21
> via lo0.0
show route protocol frr
user@host> show route protocol frr

cust1.inet.0: 1033 destinations, 2043 routes (1033 active, 0 holddown, 0 hidden)
998

20.20.1.3/32
20.20.1.4/32
20.20.1.5/32
20.20.1.6/32
20.20.1.7/32
20.20.1.8/32
20.20.1.9/32
20.20.1.10/32
...
show route protocol

l2circuit detail
*[FRR/200] 00:05:38, from 20.20.1.1

> to 20.20.1.3 via ge-4/1/0.0
to 10.10.15.1 via ge-0/2/4.0, Push
*[FRR/200] 00:05:38, from 20.20.1.1
> to 20.20.1.4 via ge-4/1/0.0
to 10.10.15.1 via ge-0/2/4.0, Push
*[FRR/200] 00:05:35, from 20.20.1.1
> to 20.20.1.5 via ge-4/1/0.0
to 10.10.15.1 via ge-0/2/4.0, Push
*[FRR/200] 00:05:37, from 20.20.1.1
> to 20.20.1.6 via ge-4/1/0.0
to 10.10.15.1 via ge-0/2/4.0, Push
*[FRR/200] 00:05:38, from 20.20.1.1
> to 20.20.1.7 via ge-4/1/0.0
to 10.10.15.1 via ge-0/2/4.0, Push
*[FRR/200] 00:05:38, from 20.20.1.1
> to 20.20.1.8 via ge-4/1/0.0
to 10.10.15.1 via ge-0/2/4.0, Push
*[FRR/200] 00:05:38, from 20.20.1.1
> to 20.20.1.9 via ge-4/1/0.0
to 10.10.15.1 via ge-0/2/4.0, Push
*[FRR/200] 00:05:38, from 20.20.1.1
16, Push 299792(top)
16, Push 299792(top)
16, Push 299792(top)
16, Push 299792(top)
16, Push 299792(top)
16, Push 299792(top)
16, Push 299792(top)
user@host> show route protocol l2circuit detail

Next hop: via ge-2/0/0.0, selected
Offset: 4
State: <Active Int>
Local AS:
99
Age: 9:52
Task: Common L2 VC
AS path: I
ge-2/0/0.0 (1 entry, 1 announced)
Label operation: Push 100000, Push 100000(top)[0] Offset: -4
Push 100000 Offset: -4
Indirect next hop: 86af0c0 298
State: <Active Int>
Local AS:
99
Age: 9:52
Task: Common L2 VC
AS path: I
999

State: <Active Int>
Local AS:
99
Age: 10:21
Task: l2 circuit
AS path: I
show route protocol

l2vpn extensive
user@host> show route protocol l2vpn extensive

TSI:
KRT in-kernel 800001 /36 -> {so-0/0/0.0}
*L2VPN Preference: 7
Next hop: via so-0/0/0.0 weight 49087 balance 97%, selected
Offset: 4
State: <Active Int>
Local AS:
69
Age: 7:48
Task: Common L2 VC
AS path: I
so-0/0/0.0 (1 entry, 1 announced)
TSI:
KRT in-kernel so-0/0/0.0.0
/16 -> {indirect(288)}
*L2VPN Preference: 7
Label operation: Push 800000 Offset: -4
Push 800000 Offset: -4
Indirect next hop: 85142a0 288
State: <Active Int>
Local AS:
69
Age: 7:48
Task: Common L2 VC
AS path: I
Communities: target:69:1 Layer2-info: encaps:PPP,
control flags:2, mtu: 0
show route protocol

ldp
user@host> show route protocol ldp

192.168.16.1/32
192.168.17.1/32
1000
*[LDP/9] 1d 23:03:35, metric 1

> via t1-4/0/0.0, Push 100000
*[LDP/9] 1d 23:03:35, metric 1
> via t1-4/0/0.0

100064
100064(S=0)
100080
show route protocol

ldp extensive
*[LDP/9] 1d 23:03:35, metric 1

> via t1-4/0/0.0, Pop
*[LDP/9] 1d 23:03:35, metric 1
> via t1-4/0/0.0, Pop
*[LDP/9] 1d 23:03:35, metric 1
> via t1-4/0/0.0, Swap 100000
user@host> show route protocol ldp extensive

192.168.16.1/32 (1 entry, 1 announced)
State: <FlashAll>
*LDP
Preference: 9
Next hop: via t1-4/0/0.0, selected
State: <Active Int>
Local AS: 65500
Age: 1d 23:03:58
Metric: 1
Task: LDP
AS path: I
192.168.17.1/32 (1 entry, 1 announced)
State: <FlashAll>
*LDP
Preference: 9
State: <Active Int>
Local AS: 65500
Age: 1d 23:03:58
Metric: 1
Task: LDP
AS path: I
TSI:
KRT in-kernel 100064 /36 -> {t1-4/0/0.0}
*LDP
Preference: 9
State: <Active Int>
Local AS: 65500
Age: 1d 23:03:58
Metric: 1
Task: LDP
AS path: I
Prefixes bound to route: 192.168.17.1/32
100064(S=0) (1 entry, 1 announced)
TSI:
KRT in-kernel 100064 /40 -> {t1-4/0/0.0}
*LDP
Preference: 9
1001

State: <Active Int>
Local AS: 65500
Age: 1d 23:03:58
Metric: 1
Task: LDP
AS path: I
TSI:
KRT in-kernel 100080 /36 -> {t1-4/0/0.0}
*LDP
Preference: 9
Label operation: Swap 100000
State: <Active Int>
Local AS: 65500
Age: 1d 23:03:58
Metric: 1
Task: LDP
AS path: I
show route protocol

ospf (Layer 3 VPN)
user@host> show route protocol ospf

10.39.1.4/30
10.39.1.8/30
10.255.14.171/32
10.255.14.179/32
224.0.0.5/32
*[OSPF/10] 00:05:18,
> via t3-3/2/0.0
[OSPF/10] 00:05:18,
> via t3-3/2/0.0
*[OSPF/10] 00:05:18,
> via t3-3/2/0.0
*[OSPF/10] 00:05:18,
> via t3-3/2/0.0
*[OSPF/10] 20:25:55,
metric 4
metric 2
metric 4
metric 2
metric 1
VPN-AB.inet.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)

10.39.1.16/30
10.255.14.173/32
224.0.0.5/32
show route protocol

ospf detail
[OSPF/10] 00:05:43, metric 1

> via so-0/2/2.0
*[OSPF/10] 00:05:43, metric 1
> via so-0/2/2.0
*[OSPF/10] 20:26:20, metric 1
user@host> show route protocol ospf detail

OSPF
Preference: 10
Nexthop: via so-0/2/2.0, selected
State: <Int>
Age: 6:25
Metric: 1
Area: 0.0.0.0
Task: VPN-AB-OSPF
1002
AS path: I
Communities: Route-Type:0.0.0.0:1:0
...
show route protocol rip
user@host> show route protocol rip

10.255.14.177/32
*[RIP/100] 20:24:34, metric 2
> to 10.39.1.22 via t3-0/2/2.0
224.0.0.9/32
*[RIP/100] 00:03:59, metric 1
show route protocol rip

detail
user@host> show route protocol rip detail

10.255.14.177/32 (1 entry, 1 announced)
*RIP
Preference: 100
Nexthop: 10.39.1.22 via t3-0/2/2.0, selected
State: <Active Int>
Age: 20:25:02
Metric: 2
Task: VPN-AB-RIPv2
Announcement bits (2): 0-KRT 2-BGP.0.0.0.0+179
AS path: I
Route learned from 10.39.1.22 expires in 96 seconds
show route protocol

ripng table inet6
user@host> show route protocol ripng table inet6

1111::1/128
1111::2/128
1111::3/128
1111::4/128
1111::5/128
1111::6/128
show route protocol

static detail
*[RIPng/100] 02:13:33, metric 2

> to fe80::2a0:a5ff:fe3d:56 via
*[RIPng/100] 02:13:33, metric 2
*[RIPng/100] 02:13:33, metric 2
*[RIPng/100] 02:13:33, metric 2
*[RIPng/100] 02:13:33, metric 2
*[RIPng/100] 02:13:33, metric 2
t3-0/2/0.0
t3-0/2/0.0
t3-0/2/0.0
t3-0/2/0.0
t3-0/2/0.0
t3-0/2/0.0
user@host> show route protocol static detail

Address: 0x9274010
Session Id: 0x0
1003
Age: 7w3d 21:24:25

Validation State: unverified
Task: RT
AS path: I
Address: 0x9274010
Session Id: 0x0
Age: 7w3d 21:24:25
Task: RT
AS path: I
10.13.10.0/23 (1 entry, 1 announced)
Address: 0x9274010
Session Id: 0x0
Age: 7w3d 21:24:25
Task: RT
AS path: I
1004
show route receive-protocol

Syntax
show route receive-protocol protocol neighbor-address

<logical-system (all | logical-system-name)
Syntax (EX Series

Switches)
show route receive-protocol protocol neighbor-address

Release Information
Description
Options

Display the routing information as it was received through a particular neighbor using a
particular dynamic routing protocol.

protocol neighbor-addressProtocol transmitting the route (bgp, dvmrp, msdp, pim, rip,
or ripng) and address of the neighboring router from which the route entry was
received.
Required Privilege
Level
Output Fields
The output displays the selected routes and the attributes with which they were received,
but does not show the effects of import policy on the routing attributes.
view
show route receive-protocol bgp on page 1008

show route receive-protocol bgp extensive on page 1008
show route receive-protocol bgp table extensive on page 1008
show route receive-protocol bgp logical-system extensive on page 1008
show route receive-protocol bgp detail (Layer 2 VPN) on page 1009
show route receive-protocol bgp extensive (Layer 2 VPN) on page 1010
show route receive-protocol bgp (Layer 3 VPN) on page 1011
show route receive-protocol bgp detail (Layer 3 VPN) on page 1011
show route receive-protocol bgp extensive (Layer 3 VPN) on page 1012
Table 90 on page 1005 describes the output fields for the show route receive-protocol
Table 90: show route receive-protocol Output Fields

Field Name
Field Description
Level of Output
routing-table-name
All levels
number
destinations
All levels
1005
Table 90: show route receive-protocol Output Fields (continued)

Field Name
Field Description
Level of Output
number routes
states:
All levels
active
holddown (routes that are in pending state before being declared inactive)
Prefix
Destination prefix.
none brief
MED
Multiple exit discriminator value included in the route.
none brief
destination-prefix
(entry, announced)
destination.
detail extensive
Route Distinguisher
64-bit prefix added to IP subnets to make them unique.
detail extensive
Label-Base, range
First label in a block of labels and label block size. A remote PE routing device
uses this first label when sending traffic toward the advertising PE routing device.
detail extensive
VPN Label
Virtual private network (VPN) label. Packets are sent between CE and PE routing
devices by advertising VPN labels. VPN labels transit over either an RSVP or an
LDP label-switched path (LSP) tunnel.
detail extensive
Next hop
selected route.
All levels
Localpref or Lclpref
All levels
1006
Table 90: show route receive-protocol Output Fields (continued)

Field Name
Field Description
Level of Output
AS path
Autonomous system (AS) path through which the route was learned. The letters
at the end of the AS path indicate the path origin, providing an indication of the
state of the route at the point at which the AS path originated:
All levels
IIGP.
EEGP.
[ ]Brackets enclose the number that precedes the AS path. This number
represents the number of ASs present in the AS path, when calculated as

defined in RFC 4271. This value is used the AS-path merge process, as defined
in RFC 4893.
[ ]If more than one AS number is configured on the router, or if AS path
prepending is configured, brackets enclose the local AS number associated

with the AS path.
Cluster list
(For route reflected output only) Cluster ID sent by the route reflector.
detail extensive
Originator ID
(For route reflected output only) Address of routing device that originally sent
the route to the route reflector.
detail extensive
Communities
Community path attribute for the route. See the Output Field table in the show
route detail command for all possible values for this field.
detail extensive
AIGP
detail extensive
Attrset AS
Number, local preference, and path of the AS that originated the route. These
values are stored in the Attrset attribute at the originating routing device.
detail extensive
Layer2-info: encaps
detail extensive
control flags
detail extensive
mtu
detail extensive
1007
Sample Output
show route
receive-protocol bgp
user@host> show route receive-protocol bgp 10.255.245.215

inet.0: 28 destinations,
Prefix
10.22.1.0/24
10.22.2.0/24
33 routes (27 active, 0 holddown, 1 hidden)

Next hop
MED
Lclpref
AS path
10.255.245.215
0
100
I
10.255.245.215
0
100
I
show route
extensive
user@host> show route receive-protocol bgp 10.255.245.63 extensive

Prefix
Next hop
MED
Lclpref AS path
Next hop: 10.0.50.3
Localpref: 100
AS path: I <Orginator>
Next hop: 111.222.5.254
Localpref: 100
Next hop: 111.222.5.254
Localpref: 100
Next hop: 111.222.5.254
Localpref: 100
Prefix
Next hop
MED
Lclpref AS path
Prefix
Next hop
MED
Lclpref AS path
Prefix
Next hop
MED
Lclpref AS path
show route
table extensive
user@host> show route receive-protocol bgp 207.17.136.192 table inet.0 66.117.68.0/24 extensive
* 66.117.63.0/24 (1 entry, 1 announced)
Nexthop: 207.17.136.29
Localpref: 100
AS path: AS2 PA[6]: 14203 2914 3356 29748 33437 AS_TRANS
AS path: AS4 PA[2]: 33437 393219
AS path: Merged[6]: 14203 2914 3356 29748 33437 393219 I
Communities: 2914:420
show route
user@host> show route receive-protocol bgp 10.0.0.9 logical-system PE4 extensive

* 10.0.0.0/30 (1 entry, 1 announced)
1008
logical-system
extensive
Accepted
Route Label: 3
Nexthop: 10.0.0.9
AS path: 13979 I
* 10.0.0.4/30 (1 entry, 1 announced)
Accepted
Route Label: 3
Nexthop: 10.0.0.9
AS path: 13979 I
Accepted
Route Label: 3
Nexthop: 10.0.0.9
AS path: 13979 I
* 10.9.9.1/32 (1 entry, 1 announced)
Accepted
Route Label: 3
Nexthop: 10.0.0.9
AS path: 13979 I
* 10.100.1.1/32 (1 entry, 1 announced)
Accepted
Route Label: 3
Nexthop: 10.0.0.9
AS path: 13979 I
* 44.0.0.0/24 (1 entry, 1 announced)
Accepted
Route Label: 300096
Nexthop: 10.0.0.9
AS path: 13979 I
AIGP: 203
* 55.0.0.0/24 (1 entry, 1 announced)
Accepted
Route Label: 300112
Nexthop: 10.0.0.9
AS path: 13979 7018 I
AIGP: 25
* 66.0.0.0/24 (1 entry, 1 announced)
Accepted
Route Label: 300144
Nexthop: 10.0.0.9
AS path: 13979 7018 I
* 99.0.0.0/24 (1 entry, 1 announced)
Accepted
Route Label: 300160
Nexthop: 10.0.0.9
AS path: 13979 7018 I
show route
detail (Layer 2 VPN)
user@host> show route receive-protocol bgp 10.255.14.171 detail

Prefix
Nexthop
MED
Lclpref AS path
Prefix
Nexthop
MED
Lclpref AS path
1009
Prefix
Nexthop
MED
Lclpref AS path
Prefix
Nexthop
MED
Lclpref AS path
frame-vpn.l2vpn.0: 2 destinations, 2 routes (2 active, 0 holddown, 0
hidden)
Prefix
Nexthop
MED
Lclpref AS path
10.255.245.35:1:5:1/96 (1 entry, 1 announced)
Label-base : 800000, range : 4, status-vector : 0x0
Nexthop: 10.255.245.35
Localpref: 100
AS path: I
Communities: target:65299:100 Layer2-info: encaps:FRAME RELAY,
control flags: 0, mtu: 0
Prefix
Nexthop
MED
Lclpref AS path
10.255.245.35:1:5:1/96 (1 entry, 0 announced)
Nexthop: 10.255.245.35
Localpref: 100
AS path: I
show route
1010

Prefix
Nexthop
MED
Lclpref AS path
extensive (Layer 2
VPN)

Prefix
Nexthop
MED
Lclpref AS path
Prefix
Nexthop
MED
Lclpref AS path
Prefix
Nexthop
MED
Lclpref AS path
frame-vpn.l2vpn.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
Prefix
Nexthop
MED
Lclpref AS path
10.255.245.35:1:5:1/96 (1 entry, 1 announced)
Nexthop: 10.255.245.35
Localpref: 100
AS path: I
Prefix
Nexthop
MED
Lclpref AS path
10.255.245.35:1:5:1/96 (1 entry, 0 announced)
Nexthop: 10.255.245.35
Localpref: 100
AS path: I
show route
(Layer 3 VPN)
user@host> show route receive-protocol bgp 10.255.14.171

Prefix
Nexthop
MED
Lclpref AS path
Prefix
Nexthop
MED
Lclpref AS path
VPN-A.inet.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)
Prefix
Nexthop
MED
Lclpref AS path
10.255.14.175/32
10.255.14.171
100 2 I
10.255.14.179/32
10.255.14.171
2
100 I
VPN-B.inet.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)
Prefix
Nexthop
MED
Lclpref AS path
10.255.14.175/32
10.255.14.171
100 2 I
10.255.14.177/32
10.255.14.171
100 I
Prefix
Nexthop
MED
Lclpref AS path
Prefix
Nexthop
MED
Lclpref AS path
Prefix
Nexthop
MED
Lclpref AS path
10.255.14.171:300:10.255.14.177/32
10.255.14.171
100 I
10.255.14.171:100:10.255.14.179/32
10.255.14.171
2
100 I
10.255.14.171:200:10.255.14.175/32
10.255.14.171
100 2 I
show route
detail (Layer 3 VPN)
user@host> show route receive-protocol bgp 10.255.14.174 detail

vpna.inet.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)
* 10.49.0.0/30 (1 entry, 1 announced)
VPN Label: 101264
1011
Nexthop: 10.255.14.174
Localpref: 100
AS path: I
AttrSet AS: 100
Localpref: 100
AS path: I
* 10.255.14.172/32 (1 entry, 1 announced)
VPN Label: 101280
Nexthop: 10.255.14.174
Localpref: 100
AS path: I
AttrSet AS: 100
Localpref: 100
AS path: I
* 10.255.14.174:2:10.49.0.0/30 (1 entry, 0 announced)
VPN Label: 101264
Nexthop: 10.255.14.174
Localpref: 100
AS path: I
AttrSet AS: 100
Localpref: 100
AS path: I
* 10.255.14.174:2:10.255.14.172/32 (1 entry, 0 announced)
VPN Label: 101280
Nexthop: 10.255.14.174
Localpref: 100
AS path: I
AttrSet AS: 100
Localpref: 100
AS path: I
show route
1012

Prefix
Nexthop
MED
Lclpref AS path
extensive (Layer 3
VPN)

Nexthop: 10.0.50.3
Localpref: 100
Nexthop: 111.222.5.254
Localpref: 100
Nexthop: 111.222.5.254
Localpref: 100
Nexthop: 111.222.5.254
Localpref: 100
Prefix
Nexthop
MED
Lclpref AS path
Prefix
Nexthop
MED
Lclpref AS path
Prefix
Nexthop
MED
Lclpref AS path
1013
show route table

Syntax
Syntax (EX Series

Switches)
Release Information
Description
Options
show route table routing-table-name

show route table routing-table-name

Display the route entries in a particular routing table.

routing-table-nameDisplay route entries for all routing tables whose name begins with
this string (for example, inet.0 and inet6.0 are both displayed when you run the show
route table inet command).
Required Privilege
Level
Related
Documentation
1014
view
show route summary
show route table bgp.l2.vpn on page 1016

show route table bgp.l3vpn.0 on page 1016
show route table bgp.l3vpn.0 detail on page 1016
show route table bgp.rtarget.0 (When Proxy BGP Route Target Filtering Is
Configured) on page 1017
show route table inet.0 on page 1018
show route table inet6.0 on page 1018
show route table inet6.3 on page 1018
show route table inetflow detail on page 1018
show route table l2circuit.0 on page 1019
show route table mpls on page 1019
show route table mpls extensive on page 1020
show route table mpls.0 on page 1020
show route table mpls.0 (RSVP RouteTransit LSP) on page 1020
show route table vpls_1 detail on page 1021
show route table vpn-a on page 1021
show route table vpn-a.mdt.0 on page 1021
show route table VPN-A detail on page 1022
show route table VPN-AB.inet.0 on page 1022
show route table VPN_blue.mvpn-inet6.0 on page 1022
show route table VPN-A detail on page 1023
show route table inetflow detail on page 1023

Output Fields
1015
Sample Output
show route table
bgp.l2.vpn
user@host> show route table bgp.l2.vpn

192.168.24.1:1:4:1/96
AS path: I
> to 10.0.16.2 via fe-0/0/1.0, label-switched-path am
show route table

bgp.l3vpn.0
user@host> show route table bgp.l3vpn.0

10.255.71.15:100:10.255.71.17/32
*[BGP/170] 00:03:59, MED 1, localpref 100, from
10.255.71.15
AS path: I
> via so-2/1/0.0, Push 100020, Push 100011(top)
10.255.71.15:200:10.255.71.18/32
10.255.71.15
AS path: I
show route table

bgp.l3vpn.0 detail
user@host> show route table bgp.l3vpn.0 detail

10.255.245.12:1:4.0.0.0/8 (1 entry, 1 announced)
*BGP
Source: 10.255.245.12
Push 182449
Indirect next hop: 863a630 297
Local AS:
35 Peer AS:
35
Age: 12:19
Metric2: 1
Task: BGP_35.10.255.245.12+179
AS path: 30 10458 14203 2914 3356 I (Atomic) Aggregator: 3356 4.68.0.11
Communities: 2914:420 target:11111:1 origin:56:78
VPN Label: 182449
Localpref: 100
Router ID: 10.255.245.12
10.255.245.12:1:4.17.225.0/24 (1 entry, 1 announced)
*BGP
Source: 10.255.245.12
Push 182465
1016
Indirect next hop: 863a8f0 305

Local AS:
35 Peer AS:
35
Age: 12:19
Metric2: 1
Task: BGP_35.10.255.245.12+179
AS path: 30 10458 14203 2914 11853 11853 11853 6496 6496 6496 6496 6496 6496 I
Communities: 2914:410 target:12:34 target:11111:1 origin:12:34
VPN Label: 182465
Localpref: 100
Router ID: 10.255.245.12
10.255.245.12:1:4.17.226.0/23 (1 entry, 1 announced)
*BGP
Source: 10.255.245.12
Push 182465
Indirect next hop: 86bd210 330
Local AS:
35 Peer AS:
35
Age: 12:19
Metric2: 1
Task: BGP_35.10.255.245.12+179
AS path: 30 10458 14203 2914 11853 11853 11853 6496 6496 6496 6496 6496
6496 I
VPN Label: 182465
Localpref: 100
Router ID: 10.255.245.12
10.255.245.12:1:4.17.251.0/24 (1 entry, 1 announced)
*BGP
Source: 10.255.245.12
Push 182465
Indirect next hop: 86bd210 330
Local AS:
35 Peer AS:
35
Age: 12:19
Metric2: 1
Task: BGP_35.10.255.245.12+179
AS path: 30 10458 14203 2914 11853 11853 11853 6496 6496 6496 6496 6496
6496 I
VPN Label: 182465
Localpref: 100
show route table

bgp.rtarget.0 (When
Proxy BGP Route
user@host> show route table bgp.rtarget.o

bgp.rtarget.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
1017
Target Filtering Is
Configured)
100:100:100/96
show route table inet.0
user@host> show route table inet.0

*[RTarget/5] 00:03:14
Type Proxy
for 10.255.165.103
for 10.255.166.124
Local
0.0.0.0/0
1.0.0.1/32
1.0.0.2/32
12.12.12.21/32
13.13.13.13/32
13.13.13.14/32
13.13.13.21/32
13.13.13.22/32
127.0.0.1/32
111.222.5.0/24
111.222.5.81/32
show route table

inet6.0
*[Static/5] 00:51:57
> to 111.222.5.254 via fxp0.0
*[Direct/0] 00:51:58
> via at-5/3/0.0
*[Local/0] 00:51:58
Local
*[Local/0] 00:51:57
Reject
*[Direct/0] 00:51:58
> via t3-5/2/1.0
*[Local/0] 00:51:58
Local
*[Local/0] 00:51:58
Local
*[Direct/0] 00:33:59
> via t3-5/2/0.0
[Direct/0] 00:51:58
> via lo0.0
*[Direct/0] 00:51:58
> via fxp0.0
*[Local/0] 00:51:58
Local
user@host> show route table inet6.0

+ = Active Route, - = Last Route, * = Both
fec0:0:0:3::/64 *[Direct/0] 00:01:34
>via fe-0/1/0.0
fec0:0:0:3::/128 *[Local/0] 00:01:34
>Local
fec0:0:0:4::/64 *[Static/5] 00:01:34
>to fec0:0:0:3::ffff via fe-0/1/0.0
show route table

inet6.3

::10.255.245.195/128
*[LDP/9] 00:00:22, metric 1
> via so-1/0/0.0
::10.255.245.196/128
*[LDP/9] 00:00:08, metric 1
> via so-1/0/0.0, Push 100008
1018
show route table

inetflow detail
user@host> show route table inetflow detail

inetflow.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
10.12.44.1,*/48 (1 entry, 1 announced)
*BGP
State: **Active Ext>
Age: 4
Task: BGP_65000.10.12.99.5+3792
Announcement bits (1): 0-Flow
AS path: 65000 I
Communities: traffic-rate:0:0
Validation state: Accept, Originator: 10.12.99.5
Via: 10.12.44.0/24, Active
Localpref: 100
Router ID: 10.255.71.161
10.12.56.1,*/48 (1 entry, 1 announced)
*Flow
Preference: 5
State: **Active>
Local AS: 65002
Age: 6:30
Task: RT Flow
Announcement bits (2): 0-Flow 1-BGP.0.0.0.0+179
AS path: I
Communities: 1:1
show route table

l2circuit.0
user@host> show route table l2circuit.0

10.1.1.195:NoCtrlWord:1:1:Local/96
*[L2CKT/7] 00:50:47
> via so-0/1/2.0, Push
via so-0/1/3.0, Push
10.1.1.195:NoCtrlWord:1:1:Remote/96
*[LDP/9] 00:50:14
Discard
10.1.1.195:CtrlWord:1:2:Local/96
*[L2CKT/7] 00:50:47
> via so-0/1/2.0, Push
via so-0/1/3.0, Push
10.1.1.195:CtrlWord:1:2:Remote/96
*[LDP/9] 00:50:14
Discard
show route table mpls
100049
100049
100049
100049
user@host> show route table mpls

0
1
2
1024
*[MPLS/0] 00:13:55, metric 1

Receive
*[MPLS/0] 00:13:55, metric 1
Receive
*[MPLS/0] 00:13:55, metric 1
Receive
*[VPN/0] 00:04:18
to table red.inet.0, Pop
1019
show route table mpls

extensive
user@host> show route table mpls extensive

TSI:
KRT in-kernel 100000 /36 -> {so-1/0/0.0}
*LDP
Preference:
9
Pop
State: <Active Int>
Age: 29:50
Metric: 1
Task: LDP
AS path: I
show route table

mpls.0
user@host> show route table mpls.0

0
1
2
100000
100001
100002
100002(S=0)
100003
100004
so-0/1/0.1
so-0/1/0.2
show route table

mpls.0 (RSVP
RouteTransit LSP)
100049(top)
100049(top)
100049(top) Offset: -4
100049(top) Offset: -4
user@host> show route table mpls.0

0
1
2
1020
*[MPLS/0] 00:45:09, metric 1

Receive
*[MPLS/0] 00:45:09, metric 1
Receive
*[MPLS/0] 00:45:09, metric 1
Receive
*[L2VPN/7] 00:43:04
> via so-0/1/0.1, Pop
*[L2VPN/7] 00:43:03
> via so-0/1/0.2, Pop
Offset:
*[LDP/9] 00:43:22, metric 1
via so-0/1/2.0, Pop
> via so-0/1/3.0, Pop
*[LDP/9] 00:43:22, metric 1
via so-0/1/2.0, Pop
> via so-0/1/3.0, Pop
*[LDP/9] 00:43:22, metric 1
> via so-0/1/2.0, Swap 100002
via so-0/1/3.0, Swap 100002
*[LDP/9] 00:43:16, metric 1
via so-0/1/2.0, Swap 100049
> via so-0/1/3.0, Swap 100049
*[L2VPN/7] 00:43:04
> via so-0/1/2.0, Push 100001, Push
via so-0/1/3.0, Push 100001, Push
*[L2VPN/7] 00:43:03
via so-0/1/2.0, Push 100000, Push
> via so-0/1/3.0, Push 100000, Push
*[MPLS/0] 00:37:31, metric 1

Receive
*[MPLS/0] 00:37:31, metric 1
Receive
*[MPLS/0] 00:37:31, metric 1
Receive
13
300352
300352(S=0)
300384
300384(S=0)
show route table vpls_1

detail
*[MPLS/0] 00:37:31, metric 1

Receive
*[RSVP/7/1] 00:08:00, metric 1
> to 8.64.0.106 via ge-1/0/1.0,
*[RSVP/7/1] 00:08:00, metric 1
> to 8.64.0.106 via ge-1/0/1.0,
*[RSVP/7/2] 00:05:20, metric 1
> to 8.64.1.106 via ge-1/0/0.0,
*[RSVP/7/2] 00:05:20, metric 1
> to 8.64.1.106 via ge-1/0/0.0,
label-switched-path lsp1_p2p
label-switched-path lsp1_p2p
Pop
Pop
user@host> show route table vpls_1 detail

vpls_1.l2vpn.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
Restart Complete
1.1.1.11:1000:1:1/96 (1 entry, 1 announced)
Receive table: vpls_1.l2vpn.0
Age: 4:29:47 Metric2: 1
Task: vpls_1-l2vpn
AS path: I
Communities: Layer2-info: encaps:VPLS, control flags:Site-Down
Label-base: 800000, range: 8, status-vector: 0xFF
show route table vpn-a
user@host> show route table vpn-a

vpn-a.l2vpn.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
192.168.16.1:1:1:1/96
*[VPN/7] 05:48:27
Discard
192.168.24.1:1:2:1/96
AS path: I
192.168.24.1:1:3:1/96
AS path: I
show route table

vpn-a.mdt.0
user@host> show route table vpn-a.mdt.0

vpn-a.mdt.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
1:1:0:10.255.14.216:232.1.1.1/144
*[MVPN/70] 01:23:05, metric2 1
Indirect
1:1:1:10.255.14.218:232.1.1.1/144
AS path: I
> via so-0/0/0.0, label-switched-path r0e-to-r1
1:1:2:10.255.14.217:232.1.1.1/144
AS path: I
> via so-0/0/1.0, label-switched-path r0-to-r2
1021
show route table

VPN-A detail
user@host> show route table VPN-A detail

10.255.179.9/32 (1 entry, 1 announced)
*BGP
Source: 10.255.179.13
Push 299824
Indirect next hop: 8f275a0 1048574
State: (Secondary Active Int Ext)
Age: 3:41:06 Metric: 1 Metric2: 1
Task: BGP_1.10.255.179.13+64309
Announcement bits (2): 0-KRT 1-BGP RT Background
AS path: I
Communities: target:1:200 rte-type:0.0.0.0:1:0
Import Accepted
VPN Label: 299824 TTL Action: vrf-ttl-propagate
Localpref: 100
Router ID: 10.255.179.13
show route table

VPN-AB.inet.0
user@host> show route table VPN-AB.inet.0

10.39.1.0/30
10.39.1.4/30
10.39.1.6/32
10.255.71.16/32
10.255.71.17/32
10.255.71.15
10.255.71.18/32
10.255.71.15
10.255.245.245/32
10.255.245.246/32
show route table

VPN_blue.mvpn-inet6.0
*[OSPF/10] 00:07:24, metric 1

> via so-7/3/1.0
*[Direct/0] 00:08:42
> via so-5/1/0.0
*[Local/0] 00:08:46
Local
*[Static/5] 00:07:24
> via so-2/0/0.0
AS path: I
AS path: I
*[BGP/170] 00:08:35, localpref 100
AS path: 2 I
> to 10.39.1.5 via so-5/1/0.0
*[OSPF/10] 00:07:24, metric 1
> via so-7/3/1.0
user@host> show route table VPN_blue.mvpn-inet6.0

vpn_blue.mvpn-inet6.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)
1:10.255.2.202:65535:10.255.2.202/432
1022

AS path: I
> via so-0/1/3.0
1:10.255.2.203:65535:10.255.2.203/432
AS path: I
> via so-0/1/0.0
1:10.255.2.204:65535:10.255.2.204/432
*[MVPN/70] 00:57:23, metric2 1
Indirect
5:10.255.2.202:65535:128:::192.168.90.2:128:ffff::1/432
AS path: I
> via so-0/1/3.0
6:10.255.2.203:65535:65000:128:::10.12.53.12:128:ffff::1/432
*[PIM/105] 00:02:37
Multicast (IPv6)
7:10.255.2.202:65535:65000:128:::192.168.90.2:128:ffff::1/432
*[MVPN/70] 00:02:37, metric2 1
Indirect
show route table

VPN-A detail
user@host> show route table VPN-A detail

10.255.179.9/32 (1 entry, 1 announced)
*BGP
Source: 10.255.179.13
Push 299824
Indirect next hop: 8f275a0 1048574
State: (Secondary Active Int Ext)
Age: 3:41:06 Metric: 1 Metric2: 1
Task: BGP_1.10.255.179.13+64309
Announcement bits (2): 0-KRT 1-BGP RT Background
AS path: I
Communities: target:1:200 rte-type:0.0.0.0:1:0
Import Accepted
VPN Label: 299824 TTL Action: vrf-ttl-propagate
Localpref: 100
Router ID: 10.255.179.13
show route table

inetflow detail
user@host> show route table inetflow detail

inetflow.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
10.12.44.1,*/48 (1 entry, 1 announced)
*BGP
State: **Active Ext>
Age: 4
Task: BGP_65000.10.12.99.5+3792
Announcement bits (1): 0-Flow
AS path: 65000 I
Communities: traffic-rate:0:0
1023
Validation state: Accept, Originator: 10.12.99.5

Via: 10.12.44.0/24, Active
Localpref: 100
Router ID: 10.255.71.161
10.12.56.1,*/48 (1 entry, 1 announced)
*Flow
Preference: 5
State: **Active>
Local AS: 65002
Age: 6:30
Task: RT Flow
Announcement bits (2): 0-Flow 1-BGP.0.0.0.0+179
AS path: I
Communities: 1:1
user@PE1> show route table green.l2vpn.0 (VPLS Multihoming with FEC 129)
1.1.1.2:100:1.1.1.2/96 AD
*[VPLS/170] 1d 03:11:03, metric2 1
Indirect
1.1.1.4:100:1.1.1.4/96 AD
AS path: I, validation-state: unverified
>
via ge-1/2/1.5
1.1.1.2:100:1:0/96 MH
*[VPLS/170] 1d 03:11:03, metric2 1
Indirect
1.1.1.4:100:1:0/96 MH
AS path: I, validation-state: unverified
>
via ge-1/2/1.5
1.1.1.4:NoCtrlWord:5:100:100:1.1.1.2:1.1.1.4/176
*[VPLS/7] 1d 03:11:02, metric2 1
>
via ge-1/2/1.5
1.1.1.4:NoCtrlWord:5:100:100:1.1.1.4:1.1.1.2/176
*[LDP/9] 1d 03:11:02
Discard
1024
show route terse

Syntax
show route terse

Syntax (EX Series

Switches)
show route terse
Release Information

Description
Display a high-level summary of the routes in the routing table.
NOTE: For BGP routes, the show route terse command displays the local
preference attribute and MED instead of the metric1 and metric2 values. This
is mostly due to historical reasons.
To display the metric1 and metric2 value of a BGP route, use the show route
extensive command.
Options
noneDisplay a high-level summary of the routes in the routing table.


Required Privilege
Level
view
show route terse on page 1027
Output Fields
Table 91 on page 1025 describes the output fields for the show route terse command. Output
Table 91: show route terse Output Fields

Field Name
Field Description
routing-table-name
number destinations
number routes
1025
Table 91: show route terse Output Fields (continued)

Field Name
Field Description
route key
Key for the state of the route:
forwarding table.
Active route. An asterisk (*) indicates this is the active route.
Validation status of the route:
?Not evaluated. Indicates that the route was not learned through BGP.
IInvalid. Indicates that the prefix is found, but either the corresponding AS received from the EBGP
peer is not the AS that appears in the database, or the prefix length in the BGP update message is
longer than the maximum length permitted in the database.
NUnknown. Indicates that the prefix is not among the prefixes or prefix ranges in the database.
VValid. Indicates that the prefix and autonomous system pair are found in the database.
Destination
Protocol through which the route was learned:
AAggregate
BBGP
CCCC
DDirect
GGMPLS
IIS-IS
LL2CKT, L2VPN, LDP, Local
KKernel
MMPLS, MSDP
OOSPF
PPIM
RRIP, RIPng
SStatic
TTunnel
Prf
Preference value of the route. In every routing metric except for the BGP LocalPref attribute, a lesser
value is preferred. In order to use common comparison routines, Junos OS stores the 1's complement
of the LocalPref value in the Preference2 field. For example, if the LocalPref value for Route 1 is 100,
the Preference2 value is -101. If the LocalPref value for Route 2 is 155, the Preference2 value is -156.
Route 2 is preferred because it has a higher LocalPref value and a lower Preference2 value.
Metric 1
First metric value in the route. For routes learned from BGP, this is the MED metric.
Metric 2
Second metric value in the route. For routes learned from BGP, this is the IGP metric.
1026
Table 91: show route terse Output Fields (continued)

Field Name
Field Description
Next hop
Next hop to the destination. An angle bracket (>) indicates that the route is the selected route.
AS path
IIGP.
EEGP.
Sample Output
show route terse
user@host> show route terse

A V Destination
* ? 1.0.1.1/32
?
unverified
* ? 1.1.1.1/32
* V 2.2.0.2/32
valid
* ? 10.0.0.0/30
?
unverified
* ? 10.0.0.1/32
* ? 10.0.0.4/30
unverified
* ? 10.0.0.8/30
unverified
* I 172.16.1.1/32
invalid
* N 192.168.2.3/32
unknown
* ? 224.0.0.5/32
P Prf
O 10
B 170
D
0
B 170
D
0
B 170
L
0
B 170
Metric 1
1
100
Metric 2
Next hop
>10.0.0.2
AS path
I
>10.0.0.2
>lo0.2
110
200 I
>10.0.0.2
>lt-1/2/0.1
100
I
>10.0.0.2
Local
100
I
>10.0.0.2
B 170
100
I
>10.0.0.2
B 170
90
200 I
>10.0.0.2
B 170
O
10
100
1
200 I
>10.0.0.2
MultiRecv
1027
show system autoinstallation status

Syntax
Release Information

Command supported in Junos OS Release 12.2 for ACX Series Universal Access Routers.
Description
(ACX Series routers, J Series routers, and EX Series switches only) Display autoinstallation
status information.
Options
Required Privilege
Level
view
Related
Documentation
autoinstallation
Output Fields
Table 92 on page 1028 describes the output fields for the show system autoinstallation
status command. Output fields are listed in the approximate order in which they appear.
Table 92: show system autoinstallation status Output Fields

Field Name
Field Description
Autoinstallation status
Display autoinstallation status information:
Last committed fileFile last committed for autoinstallation configuration.
Configuration server of last committed fileIP address or URL of the server configured to retrieve
configuration information for the last committed configuration file.
1028
InterfaceInterface configured for autoinstallation.
NameName of the interface.
StateInterface state.
Address acquisitionDisplay IP address acquired and protocol used for acquisition upon startup.
ProtocolProtocol used for acquisition: BOOTP/DHCP or RARP.
Acquired addressIP address acquired from the DHCPserver.
Sample Output
show system
autoinstallation status
user@host> show system autoinstallation status

Autoinstallation status:
Master state: Active
Last committed file: None
Configuration server of last committed file: 0.0.0.0
Interface:
Name: ge-0/0/1
State: None
1029
show validation database

Syntax
Release Information
Description
Options
show validation database

<brief | detail>
<mismatch>
<origin-autonomous-system as-number>
<record ip-prefix>
<session ip-address>

Display information about the route validation database when resource public key
infrastructure (RPKI) BGP route validation is configured. You can query all route validation
records that match a given prefix or origin-autonomous-system. In addition, you can filter
the output by a specific RPKI cache session.
noneDisplay all route validation database entries.
instance instance-name(Optional) Display information about route validation database
entries for the specified routing instance. The instance name can be master for the
main instance, or any valid configured instance name or its prefix.
logical-system logical-system-name(Optional) Perform this operation on a particular
logical system.
mismatch(Optional) Filter the output by mismatched origin autonomous systems.
origin-autonomous-system as-number(Optional) Filter the output by mismatched origin
autonomous systems. The mismatch qualifier is useful for finding conflicting

origin-autonomous-system information between RPKI caches. Mismatches might
occur during cache reconfiguration.
record ip-prefix(Optional) Filter the output by route validation records that match a
given prefix.
session ip-address(Optional) Filter the output by a specific RPKI cache session.
Required Privilege
Level
Related
Documentation
Output Fields
1030
view
Example: Configuring Origin Validation for BGP
show validation database on page 1031

Table 93 on page 1031 describes the output fields for the show validation database
Table 93: show validation database Output Fields

Field Name
Field Description
Level of
Output
Prefix
Route validation (RV) record prefix.
All levels
RV records are received from the cache server and can also be
configured statically at the [edit routing-options validation static]
hierarchy level .
Origin-AS
Legitimate originator autonomous system (AS).
All levels
Session
IP address of the RPKI cache server.
All levels
State
State of the route validation records. The state can be valid, invalid
or unknown.
All levels
Mismatch
Conflicting origin-autonomous-system information between RPKI

caches when nonstop active routing (NSR) is configured.
All levels
IPv4 records
Number of IPv4 route validation records.
All levels
IPv6 records
All levels
Sample Output
show validation
database
user@host> show validation database

RV database for instance master
Prefix
1.0.1.0/24-32
1.0.2.0/24-32
1.0.3.0/24-32
1.0.4.0/24-32
1.0.5.0/24-32
1.0.6.0/24-32
1.0.7.0/24-32
1.0.8.0/24-32
72.9.224.0/19-24
72.9.224.0/19-24
10.0.0.0/8-32
Origin-AS
1
2
3
4
5
6
7
8
26234
3320
0
Session
10.0.77.1
10.0.77.1
10.0.77.1
10.0.77.1
10.0.77.1
10.0.77.1
10.0.77.1
10.0.77.1
192.168.1.100
192.168.1.200
internal
State
Mismatch
valid
valid
valid
valid
valid
valid
valid
valid
valid
*
invalid *
valid
IPv4 records: 14
IPv6 records: 0
1031
show validation group

Syntax
Release Information
Description
Options


Display information about route validation redundancy groups.
noneDisplay information about all route validation groups.
instance instance-name(Optional) Display information about route validation groups
for the specified routing instance. The instance name can be master for the main
instance, or any valid configured instance name or its prefix.
logical system.
Required Privilege
Level
Related
Documentation
Output Fields
view
show validation group on page 1033

Table 94 on page 1032 describes the output fields for the show validation group command.
Table 94: show validation group Output Fields

Field Name
Field Description
Group
Group name.
Maximum sessions
Number of concurrent sessions for each group. The default is 2. The number
is configurable with the max-sessions statement.
Session
Resource public key infrastructure (RPKI) cache session IP address.
State
State of the connection between the routing device and the cache server. Up
means that the connection is established. Connect means that the connection
is not established.
Preference
Each cache server has a preference. Higher preferences are preferred. During
a session start or restart, the routing device attempts to start a session with
the cache server that has the numerically highest preference. The routing
device connects to multiple cache servers in preference order.
The default preference is 100. The preference is configurable with the
preference statement.
1032
Sample Output
user@host> show validation group

master
Group: test, Maximum sessions: 3
Session 10.255.255.11, State: Up, Preference: 100
Session 10.255.255.12, State: Up, Preference: 100
Group: test2, Maximum sessions: 2
Session 10.255.255.13, State: Connect, Preference: 100
1033
show validation replication database

Syntax
Release Information
Description
Options

<brief | detail>
<origin-autonomous-system as-number>
<record ip-prefix>
<session ip-address>

Display the state of the nonstop active routing (NSR) records. The output is the same
as the output of the show validation database command, except for the Mismatch column.
noneDisplay all route validation database entries.
instance instance-name(Optional) Display information about route validation database
entries for the specified routing instance. The instance name can be master for the
main instance, or any valid configured instance name or its prefix.
logical system.
origin-autonomous-system as-number(Optional) Filter the output by mismatched origin
autonomous systems. The mismatch qualifier is useful for finding conflicting

origin-autonomous-system information between resource public key infrastructure
(RPKI) caches. Mismatches might occur during cache reconfiguration.
record ip-prefix(Optional) Filter the output by route validation records that match a
given prefix.
session ip-address(Optional) Filter the output by a specific RPKI cache session.
Required Privilege
Level
Related
Documentation
Output Fields
1034
view
show validation replication database on page 1035

Table 95 on page 1035 describes the output fields for the show validation replication
database command. Output fields are listed in the approximate order in which they
appear.
Table 95: show validation replication database Output Fields

Field Name
Field Description
Level of
Output
Prefix
Route validation (RV) record prefix.
All levels
RV records are received from the cache server and can also be
configured statically at the [edit routing-options validation static]
hierarchy level.
Origin-AS
Legitimate originator autonomous system (AS).
All levels
Session
All levels
State
State of the route validation records. The state can be valid or invalid.
All levels
IPv4 records
All levels
IPv6 records
All levels
Sample Output
show validation
replication database
user@host> show validation replication database

RV database for instance master
Prefix
1.0.1.0/24-32
1.0.2.0/24-32
1.0.3.0/24-32
1.0.4.0/24-32
1.0.5.0/24-32
1.0.6.0/24-32
1.0.7.0/24-32
1.0.8.0/24-32
72.9.224.0/19-24
72.9.224.0/19-24
10.0.0.0/8-32
Origin-AS
1
2
3
4
5
6
7
8
26234
3320
0
Session
10.0.77.1
10.0.77.1
10.0.77.1
10.0.77.1
10.0.77.1
10.0.77.1
10.0.77.1
10.0.77.1
192.168.1.100
192.168.1.200
internal
State
valid
valid
valid
valid
valid
valid
valid
valid
valid
invalid
valid
IPv4 records: 14
IPv6 records: 0
1035
show validation session

Syntax
Release Information
Description
Options
show validation session

<brief | detail>
<destination>

Display information about all sessions or a specific session with a resource public key
infrastructure (RPKI) cache server.
noneDisplay information about all sessions.
destination(Optional) Display information about a specific session.
instance instance-name(Optional) Display information about sessions for the specified
routing instance. The instance name can be master for the main instance, or any
valid configured instance name or its prefix.
logical system.
Required Privilege
Level
Related
Documentation
Output Fields
view
show validation session brief on page 1038

show validation session detail on page 1038
Table 96 on page 1036 describes the output fields for the show validation session command.
Table 96: show validation session Output Fields

Field Name
Field Description
Level of
Output
Session
All levels
State
State of the connection between the routing device and the cache
server. Up means that the connection is established. Connect means
that the connection is not established.
All levels
Flaps
Number of attempts to establish a session.
None and
brief
1036
Table 96: show validation session Output Fields (continued)

Field Name
Field Description
Level of
Output
Uptime
Length of time that the session has remained establshed.
None and
brief
#IPv4/IPv6 records
Number of IPv4 and IPv6 route validation records.
None and
brief
Session index
Every session has an index number.
detail
Group
Name of the group to which the session belongs
detail
Preference
Each cache server has a preference. Higher preferences are preferred.

During a session start or restart, the routing device attempts to start
a session with the cache server that has the numerically highest
preference. The routing device connects to multiple cache servers
in preference order.
detail
The default preference is 100. The preference is configurable with

the preference statement.
Port
TCP port number for the outgoing connection with the cache server.
The well-known RPKI port is TCP port 2222. For a given deployment,
an RPKI cache server might listen on some other TCP port number.
If so, you can configure the alternative port number with the port
statement.
detail
Refresh time
Liveliness check interval for an RPKI cache server. Every refresh-time

(seconds), a serial query protocol data unit (PDU) with the last
known serial number is transmitted. The hold-time must be at least
2 x the refresh-time.
detail
Hold time
Length of time in seconds that the session between the routing

device and the cache server is considered operational without any
activity. After the hold time expires, the session is dropped.
detail
Reception of any PDU from the cache server resets the hold timer.
The hold-time is 600 seconds, by default, and must be least 2 x the
refresh-time. If the hold time expires, the session is considered to be
down. This, in turn, triggers a session restart event. During a session
restart, the routing device attempts to start a session with the cache
server that has the numerically highest preference.
Record Life time
Amount of time that route validation (RV) records learned from a

cache server are valid. RV records expire if the session to the cache
server goes down and remains down for the record-lifetime
(seconds).
detail
Serial (Full Update)
Number of full serial updates.
detail
Serial (Incremental Update)
Number of incremental serial updates.
detail
Session flaps
Number of attempts to establish a session.
detail
1037
Table 96: show validation session Output Fields (continued)

Field Name
Field Description
Level of
Output
Session uptime
Length of time that the session has remained establshed.
detail
Last PDU received
Time when the most recent PDU was received.
detail
IPv4 prefix count
Number of IPv4 sessions.
detail
IPv6 prefix count
Number of IPv6 sessions.
detail
Sample Output
show validation
session brief
show validation
session detail
1038
user@host> show validation session brief

Session
records
1.3.0.2
10.255.255.11
10.255.255.12
State
Flaps
up
up
connect
Uptime #IPv4/IPv6
2
3
2
00:01:37 13/0
00:00:01 1/0
64/68
user@host> show validation session detail

Session 10.0.77.1, State: up
Group: test, Preference: 100
Local IPv4 address: 10.0.77.2, Port: 2222
Refresh time: 300s
Session flaps: 14, Last Session flap: 5h13m18s ago
Hold time: 900s
Record Life time: 3600s
Serial (Full Update): 0
Serial (Incremental Update): 0
Session flaps 2
Session uptime: 00:48:35
Last PDU received: 00:03:35
IPv4 prefix count: 71234
IPv6 prefix count: 345
show validation statistics

Syntax
Release Information
Description
Options
show validation statistics


Display route validation statistics.
noneDisplay statistics for all routing instances.
instance instance-name(Optional) Display information for the specified routing instance.
The instance name can be master for the main instance, or any valid configured
instance name or its prefix.
logical system.
Required Privilege
Level
Related
Documentation
Output Fields
view
show validation statistics on page 1040

Table 97 on page 1039 describes the output fields for the show validation statistics
Table 97: show validation statistics Output Fields

Field Name
Field Description
Total RV records
Group name.
Total Replication RV records
Number of concurrent sessions for each group. The default is 2. The number
is configurable with the max-sessions statement.
Prefix entries
Resource public key infrastructure (RPKI) cache session IP address.
Origin-AS entries
State of the connection between the routing device and the cache server. Up
means that the connection is up. Connect means that the connection is not
up.
Memory utilization
Each cache server has a preference. Higher preferences are preferred. During
a session start or restart, the routing device attempts to start a session with
the cache server that has the numerically highest preference. The routing
device connects to multiple cache servers in preference order.
The default preference is 100. The preference is configurable with the
preference statement.
1039
Table 97: show validation statistics Output Fields (continued)

Field Name
Field Description
Policy origin-validation requests
Number of queries for validation state of a given instance and prefix.
Valid
Number of valid prefixes reported by the validation query.
Invalid
Number of invalid prefixes reported by the validation query.
Unknown
Number of unknown prefixes reported by the validation query. This means

that the prefix is not found in the database.
BGP import policy reevaluation notifications
A change, addition, or deletion of a route validation record triggers a BGP

import reevaluation for all exact matching and more specific prefixes.
inet.0
Number of IPv4 route validation records that have been added, deleted, or
changed.
inet6.0
Number of IPv6 route validation records that have been added, deleted, or
changed.
Sample Output
show validation
statistics
1040
user@host> show validation statistics

Total RV records:
453455
Total Replication RV records: 453455
Prefix entries:
35432
Origin-AS entries:
124400
Memory utilization: 16.31MB
Policy origin-validation requests: 234995
valid:
23445
invalid:
14666
unknown:
34567
BGP import policy reevaluation notifications: 460268
inet.0:
435345
inet6.0:
3454
test interface e1-bert-start

Syntax
test interface e1-bert-start interface-name
Release Information
Description
Start a bit error rate test (BERT) on an E1 interface.
Options
Required Privilege
Level
Related
Documentation

Output Fields
interface-nameInterface name: e1-fpc/pic/port or ce1-fpc/pic/port <:channel>
Before starting a BERT, you must disable the interface. To do this, include the disable
statement at the [edit interfaces interface-name] hierarchy level. You can run a BERT on
only one interface per PIC at a time.
view
test interface e1-bert-stop on page 1042
test interface t1-bert-start on page 1043
test interface t1-bert-stop on page 1044
test interface e1-bert-start on page 1041

To display the results of the BERT, use the show interfaces extensive command.
Sample Output
test interface
e1-bert-start
user@host> test interface e1-bert-start e1-1/0/0
1041
test interface e1-bert-stop

Syntax
Release Information
Description
Options
Required Privilege
Level
Related
Documentation

Output Fields
test interface e1-bert-stop interface-name

Stop a bit error rate test (BERT) on an E1 interface.
interface-nameInterface name: e1-fpc/pic/port or ce1-fpc/pic/port <:channel>.
view

Sample Output
test interface
e1-bert-stop
1042
user@host> test interface e1-bert-stop e1-1/0/0
test interface t1-bert-start

Syntax
Release Information
Description
Options
Required Privilege
Level
Related
Documentation

Output Fields
test interface t1-bert-start interface-name

Start a bit error rate test (BERT) on a T1 interface.
interface-nameInterface name: t1-fpc/pic/port or ct1-fpc/pic/port <:channel>.
Before starting a BERT, you must disable the interface. To do so, include the disable
statement at the [edit interfaces interface-name] hierarchy level. You can run a BERT on
only one interface per PIC at a time.
view

Sample Output
test interface
t1-bert-start
user@host> test interface t1-bert-start t1-1/0/0
1043
test interface t1-bert-stop

Syntax
Release Information
Description
Options
test interface t1-bert-stop interface-name

Stop a bit error rate test (BERT) on a T1 interface.
interface-nameInterface name: t1-interface-name fpc/pic/port or ct1-fpc/pic/port
<:channel>
Required Privilege
Level
Related
Documentation

Output Fields
view

Sample Output
test interface
t1-bert-stop
1044
user@host> test interface t1-bert-stop t1-1/0/0
PART 4
Troubleshooting
Troubleshooting Procedures on page 1047
1045
1046
CHAPTER 18
Troubleshooting Procedures
CT1 and CE1 Interfaces Alarms, Errors, and Defects on page 1047
Troubleshooting PoE Interfaces on ACX2000 Universal Access Routers on page 1048
CT1 and CE1 Interfaces Alarms, Errors, and Defects

Table 98 on page 1047 lists the ct1 and ce1 media-specific alarms or defects that can render
the interface on ACX Series routers unable to pass packets.
Table 98: CT1 and CE1 Interface Alarms and Error Definitions
Alarm or Error
Definitions
Structure-Agnostic Interface Type
Structure-Aware
AIS
Alarm indication signal (blue alarm)
ct1 and ce1 interfaces
ct1 and ce1 interfac
BEE
Block error event
N/A
BES
Bursty errored seconds
N/A
BPV
Bipolar violation
N/A
N/A
CRC
Cyclic redundancy check (CRC)
N/A
ce1 interfaces
CRC Major
Major alarm error threshold
N/A
ce1 interfaces
CRC Minor
Minor alarm error threshold
N/A
ce1 interfaces
CS
Controlled slip
N/A
N/A
ES
Errored seconds
EXZ
Excessive zeros
N/A
N/A
FEBE
Far-end block error
N/A
LCV
Line code violation
LES
Line errored seconds
1047
Table 98: CT1 and CE1 Interface Alarms and Error Definitions (continued)
Alarm or Error
Definitions
Structure-Agnostic Interface Type
Structure-Aware
LOF
Loss of frame
ce1 interfaces
LOS
Loss of signal
PCV
Path code violation
N/A
SEF
Severely errored frame
N/A
SEFS
Severely errored frame seconds
N/A
SES
Severely errored seconds
UAS
Unavailable seconds
YLW
Yellow alarm
N/A
Troubleshooting PoE Interfaces on ACX2000 Universal Access Routers

Problem
A Power over Ethernet (PoE) interface is not supplying power to the powered device.
Solution
Check for the items shown in Table 99 on page 1048.
Table 99: Troubleshooting a PoE Interface
Related
Documentation
1048
Items to Check
Explanation
Is interface PoE enabled?
Only interfaces ge-0/1/3 and ge-0/1/7 can

function as PoE ports.
Has PoE capability been disabled for that

interface?
Use the show poe interface command to check

PoE interface status.
Is the cable properly seated in the port socket?
Check the hardware.
Does the powered device require more power

than is available on the interface?
Use the show poe interface command to check

the maximum power provided by the interface.
If the telemetries option has been enabled for

the interface, check the history of power
consumption.
Use the show poe telemetries command to

display the history of power consumption.
PART 5
Index
Index on page 1051
1049
1050
Index
Symbols
#, comments in configuration statements..................xxii
( ), in syntax descriptions...................................................xxii
802.1Q/Ethernet 802.3 encapsulation
encapsulation overhead..............................................97
802.1Q/Ethernet SNAP encapsulation
< >, in syntax descriptions..................................................xxii
[ ], in configuration statements.......................................xxii
{ }, in configuration statements.......................................xxii
| (pipe), in syntax descriptions.........................................xxii
A
actions, nonterminating
for standard stateless firewall filters.....................88
actions, terminating
for standard stateless firewall filters.....................86
ACX Series
recover of primary image..........................................293
ACX Series clock sources
overview..........................................................................239
ACX Series routers
installing software
with CLI..................................................................296
Junos OS Release 12.2
upgrading with dual-root................................294
show system storage ................................................299
ACX Series Universal Access router
dual-root partitioning.................................................291
address class, source or destination
stateless firewall filter match conditions
IPv4 traffic...............................................................83
address, source or destination
IPv4 traffic...............................................................83
advertisements, displaying .............................................890
alarm conditions...................................................................104
alarms, displaying
chassis.............................................................................364
AS paths
matching regular expressions, displaying..........897
ASN
BGP community routes, displaying.....................904
Asynchronous Transfer Mode See ATM
ATM
pseudowire.....................................................................129
ATM cell-relay encapsulation
ATM encapsulation
ATM PVC encapsulation..............................................97
ATM IMA
ACX Series........................................................................99
ATM interfaces
CoS and.............................................................................54
status information, displaying...............................666
ATM PVC encapsulation.......................................................97
atm-options statement
usage guidelines.............................................................54
autoinstallation
automatic configuration.....................................47, 291
default configuration file....................................46, 291
host-specific configuration file........................46, 291
requirements....................................................................47
router........................................................................46, 290
TFTP server...........................................................46, 290
autoinstallation, displaying the status of.................1028
autonomous system number See ASN
B
backing up partitions......................................308, 309, 341
backup-neighbor statement
usage guidelines............................................................123
bert
ce1........................................................................................93
ct1.........................................................................................93
BERT
E1 test
starting..................................................................1041
stopping...............................................................1042
T1 test
starting.................................................................1043
stopping...............................................................1044
bert-algorithm statement
best routes, displaying.......................................................899
BGP
community ASN, displaying routes......................904
community name, displaying routes...................906
damping routes, displaying....................................908
1051
neighbors
displaying...............................................................343
route validation
information,
displaying........1030, 1032, 1034, 1036, 1039
summary information, displaying.........................359
binding state of DHCP client
clearing.............................................................................331
displaying........................................................................661
BITS interfaces
G.703 signal type.........................................................259
boot sequence
ACX Series routers......................................................302
boundary clock, overview....................................................26
boundary clock, with unicast-negotiation..................275
boundary clock, without unicast-negotiation............273
braces, in configuration statements...............................xxii
brackets
angle, in syntax descriptions....................................xxii
square, in configuration statements......................xxii
C
CE interfaces
interface-type................................................................216
partition............................................................................216
timeslots..........................................................................216
ce1
bert......................................................................................93
CE1 interfaces
alarms and errors
definitions, table................................................1047
CESoPSN encapsulation
DS interfaces..................................................................215
CFM
Ethernet overview........................................................183
CFM statistics
displaying for CFM interfaces...................................791
displaying for interfaces.............................................767
chassis
alarm conditions, displaying...................................364
configuration
alarm conditions.................................................104
craft interface display messages
displaying through the CLI...............................377
environmental information, displaying...............390
firmware version, displaying...................................446
installed hardware, displaying...............................484
MAC addresses, displaying.....................................588
1052
serial numbers, displaying.......................................484

synchronization source information,
displaying...................................................................627
checklist for monitoring
Fast Ethernet interfaces..............................................94
Gigabit Ethernet interfaces........................................94
T1 interfaces.....................................................................95
Cisco HDLC encapsulation
classification and rewrite
at global and physical interface levels, example
configuration...............................................................63
at global and physical interface levels,
overview........................................................................23
clear dhcp relay binding command................................331
clear dhcp relay statistics command...........................328
sla-iterator-statistics command................................326
synthetic-loss-measurement command................327
cli terminology................................................................11, 14, 17
client, clock, PTP boundary overview.............................26
clock ptp master, configuring................................254, 256
clock ptp slave interface, configuring...........................259
clock ptp slave, configuring...............................................257
clock sources
ACX Series......................................................................239
clock, PTP boundary overview..........................................26
clock-client, PTP boundary overview.............................26
clocking, PTP configuring..................................................253
comments, in configuration statements......................xxii
community ASN, displaying routes..............................904
community name, displaying routes............................906
community statement
Layer 2 circuits
usage guidelines..................................................109
control-word statement
Layer 2 circuits..............................................................109
conventions
text and syntax...............................................................xxi
CoS
ATM interfaces................................................................54
classifiers configured under system defaults,
displaying...................................................................657
interfaces, displaying..................................................631
policer actions, overview.............................................37
craft interface display messages
displaying
through the CLI.....................................................377
Index
ct1
bert......................................................................................93
CT1 interfaces
alarms and errors
definitions, table................................................1047
curly braces, in configuration statements....................xxii
customer support.................................................................xxiii
contacting JTAC............................................................xxiii
D
damping routes, BGP
displaying.......................................................................908
default configuration file, for
autoinstallation..........................................................46, 291
destination statement
usage guidelines.............................................................54
DHCP
relay binding
clearing....................................................................331
relay binding state
displaying...............................................................661
relay statistics
clearing...................................................................328
displaying..............................................................658
DHCP client
binding state
clearing....................................................................331
displaying...............................................................661
statistics
clearing...................................................................328
disk-on-key configuration
requirements...................................................................50
Disk-on-Key configuration
procedure..........................................................................50
documentation
comments on................................................................xxiii
downloading configuration, with
DS interfaces
CESoPSN encapsulation...........................................215
status information, displaying.................................701
DSCP code point
stateless firewall filter match condition
IPv4 traffic...............................................................83
dual-root partitioning scheme.........................................291
E
E-LMI..........................................................................................169
E1 interfaces
E1/T1 interfaces
SAToP emulation..................................................102, 217
emulation
SAToP on T1/E1 interfaces................................102, 217
encapsulation
CESoPSN on DS interfaces.......................................215
Ethernet 802.3................................................................97
overheads..........................................................................97
encapsulation mismatch
Layer 2 circuits................................................................114
encapsulation-type statement
Layer 2 circuits
usage guidelines...................................................110
environmental information
chassis, displaying.......................................................391
EPW (Electronic Preinstallation Worksheet)
configuration
procedure..........................................................................50
ETH-DM
overview............................................................................177
ETH-DM frame counts (with CFM statistics)
displaying for MEPs by enclosing CFM.................791
displaying for MEPs by interface or domain
level...............................................................................767
ETH-DM statistics and frame counts
displaying........................................................................778
ETH-LM
overview...........................................................................182
ETH-SLM See monitor ethernet
synthetic-loss-measurement command
configuration scenarios..............................................195
displaying statistics and frame counts................197
format of PDUs or messages...................................192
guidelines to configure...............................................194
overview...........................................................................189
transmission of PDUs or messages......................190
ETH-SLM frame counts (with CFM statistics)
displaying for MEPs by enclosing CFM.................791
level...............................................................................767
ETH-SLM statistics (only)
displaying.......................................................................807
ETH-SLM statistics and frame counts
displaying........................................................................778
Ethernet
CFM overview.................................................................183
pseudowire......................................................................133
1053
Ethernet CCC encapsulation

Ethernet frame
synthetic loss measurement (ETH-SLM),
displaying...................................................................333
Ethernet frame delay measurement
overview............................................................................177
Ethernet frame loss measurement
overview...........................................................................182
Ethernet interfaces
CFM statistics
displaying for CFM interfaces..........................791
displaying for interfaces....................................767
ETH-DM frame counts (with CFM statistics)
displaying for MEPs by enclosing
CFM.......................................................................791
level......................................................................767
ETH-DM statistics and frame counts
displaying...............................................................778
ETH-SLM frame counts (with CFM statistics)
displaying for MEPs by enclosing
CFM.......................................................................791
level......................................................................767
ETH-SLM statistics (only)
displaying..............................................................807
ETH-SLM statistics and frame counts
displaying...............................................................778
Ethernet Local Management Interface See E-LMI
Ethernet over ATM encapsulation
Ethernet SNAP encapsulation
Ethernet synthetic loss measurement
displaying statistics and frame counts................197
format of PDUs or messages...................................192
guidelines to configure...............................................194
overview...........................................................................189
scenarios for deployment.........................................195
transmission of PDUs or messages......................190
Ethernet TCC
encapsulation
encapsulation overhead.....................................97
export route information, displaying..............................931
1054
extended VLAN
CCC
encapsulation overhead....................................98
TCC
encapsulation overhead....................................98
external clock synchronization interface
guidelines
ACX Series...................................................240, 242
F
family statement
ATM interfaces
usage guidelines....................................................54
Fast Ethernet interfaces
monitor checklist...........................................................94
FEB
status, displaying.........................................................442
file systems
partitions, backing up............................308, 309, 341
firmware
chassis, displaying......................................................446
font conventions.....................................................................xxi
forwarding class
policer actions
overview....................................................................37
IPv4 traffic...............................................................83
forwarding options
DHCP relay agent............................328, 331, 658, 661
forwarding table
route entries, displaying...........................................950
FPC
installed, displaying list.............................................485
status, displaying........................................................458
frame delay, Ethernet See Ethernet frame delay
measurement
frame loss, Ethernet See Ethernet frame loss
measurement
Frame Relay encapsulation
encapsulation overhead.............................................98
G
G.703 signal type
BITS interfaces.............................................................259
Gigabit Ethernet interfaces
Index
GPS
ACX Series......................................................................248
H
hard disk..................................................................................302
hardware
descriptions in the CLI........................................11, 14, 17
hardware architecture
ACX Series, M Series, MX Series, T Series, and
TX Matrix routers....................................................300
hardware components..........................................................19
hardware, installed, displaying.......................................484
hidden routes, displaying..................................................964
host-specific configuration file, for
hostname.conf file, for autoinstallation................47, 291
hostnames
IS-IS, displaying............................................................746
routes, displaying.........................................................755
SPF calculations, displaying....................................759
traffic statistics
displaying...............................................................764
Iterator profile
configuration.................................................................202
ITU-T standards
Y.1731 ETH-DM................................................................177
Y.1731 ETH-LM................................................................182
J
jitter, Ethernet frame See Ethernet frame delay
measurement
Junos OS
autoinstallation status, displaying......................1028
installation
current configuration, confirming................308
storage media...............................................................302
device names.......................................................303
I
IEEE 1588v2
ACX Series........................................................................28
ignore-encapsulation-mismatch statement
ignore-mtu-mismatch statement
IMA
ACX Series........................................................................99
installation
memory requirements
M Series, MX Series, PTX Series, T Series,
TX Matrix, and TX Matrix Plus
routers.................................................................301
software upgrades, from a remote server.........296
interface statement
Layer 2 circuits..............................................................108
interface-type
CE interfaces..................................................................216
interfaces
ACX Series........................................................................99
ATM, VC tunnel CoS......................................................54
IPv4 traffic
match conditions
standard stateless firewall filters...................83
IS-IS
hostname database, displaying.............................746
interfaces, displaying..................................................747
link-state database entries
displaying...............................................................739
L
Layer 2 circuits
redundant pseudowires.............................................123
Layer 2 circuit
MTU....................................................................................114
Layer 2 circuits
encapsulation mismatch............................................114
loopback capability
E1 interfaces
example configuration......................................233
loss priority
IPv4 traffic...............................................................83
M
MAC addresses
displaying.......................................................................588
manuals
comments on................................................................xxiii
master ptp clock, configuring................................254, 256
match conditions for standard stateless firewall
filters
IPv4 traffic........................................................................83
MPLS traffic.....................................................................86
maximum transmission unit See MTU
media MTUs.............................................................................96
See also MTU
1055
memory requirements
M Series, MX Series, PTX Series, T Series, TX
Matrix, and TX Matrix Plus routers....................301
MIBs
Multicast.................................................................146, 155
OSPF.................................................................................143
PPP....................................................................................142
command............................................................................333
MPLS traffic
match conditions
MTU
Layer 2 circuit..................................................................114
physical interfaces........................................................96
mtu statement
usage guidelines......................................................96, 111
Multicast MIB.................................................................146, 155
MX Series
Ethernet CFM.................................................................183
N
network.conf file, default for
autoinstallation..................................................46, 48, 291
next hops
routes sent to, displaying.........................................980
no-control-word statement
Layer 2 circuits..............................................................109
O
OAM
E-LMI.................................................................................169
OSPF
interfaces, displaying.................................................830
link-state database entries, displaying
version 2..................................................................810
version 3..................................................................819
neighbors
displaying..............................................................842
overview
displaying..............................................................849
routing table entries, displaying............................854
SPF calculations, displaying...................................838
statistics, general
displaying..............................................................860
statistics, I/O
displaying..............................................................836
OSPF MIB.................................................................................143
1056
P
packet loss priority
policer actions
overview....................................................................37
parentheses, in syntax descriptions...............................xxii
partition
CE interfaces..................................................................216
partitions, backing up.....................................308, 309, 341
physical interfaces
media MTU size..............................................................96
PICs
installed, displaying list.............................................485
status
displaying for a specific PIC...........................594
displaying FPCs and PICs................................457
PoE
Specifications
ACX2000 Universal Access Routers..............41
poe
controller........................................................................864
Point-to-Point Protocol encapsulation
policer
overview.............................................................................37
policer actions
forwarding class
overview....................................................................37
packet loss-priority
overview....................................................................37
port number (TCP or UDP), source or destination
IPv4 traffic...............................................................83
PPP MIB....................................................................................142
processes
restarting.........................................................................337
protocol MTUs.........................................................................96
See also MTU
pseudowire
ATM....................................................................................129
Ethernet............................................................................133
TDM...................................................................................125
pseudowire redundancy
failure detection............................................................122
psn-tunnel-endpoint statement
PTP
ACX Series........................................................................28
PTP boundary clock, overview..........................................26
PTP clocking, configuring..................................................253
Index
ptp master clock, configuring................................254, 256

PTP over Ethernet
guidelines for configuring.........................................250
master ports, configuring
for multicast PTP transmission....................260
multicast transport, configuring
master boundary clock interface.................260
master boundary clock parameters............260
slave clock interface..........................................260
slave clock parameters....................................260
stateful interfaces or ports.............................265
overview..........................................................................248
slave ports, configuring
stateful ports, configuring
working of, benefits....................................................248
PTP over IEEE 802.3 See PTP over Ethernet
ptp slave clock interface, configuring...........................259
ptp slave clock, configuring...............................................257
R
real-time monitoring
Ethernet synthetic frame loss measurement
(ETH-SLM)................................................................333
real-time performance monitoring................................139
red alarm conditions............................................................104
redundant pseudowires
configuration..................................................................123
overview............................................................................121
revert time.......................................................................124
regular expressions
AS paths, displaying matching routes.................897
remote server, upgrading from.......................................296
replication
of BGP configuration..................................................357
request system snapshot command
ACX Series..................................................308, 309, 341
resource public key infrastructure See RPKI
restart command..................................................................337
restarting
software processes.....................................................337
revert time
revert-time statement
usage guidelines...........................................................124
route advertisements, displaying..................................890
route, displaying
next-hop........................................................................980
routers
boot sequence
ACX Series routers.............................................302
hardware components.................................................19
storage media...............................................................302
routes, displaying
active................................................................................879
active path.....................................................................885
advertising protocol...................................................890
all......................................................................................895
AS paths
regular expressions, matching.......................897
best..................................................................................899
brief information..........................................................902
community ASN..........................................................904
community name.......................................................906
damping, BGP..............................................................908
detailed information...................................................914
extensive information................................................933
flow validation.............................................................948
hidden.............................................................................964
in a specific routing table........................................1014
in the forwarding table.............................................950
inactive path..................................................................967
inactive prefix.................................................................971
instances.........................................................................973
learned from a specific protocol...........................993
matching the specified address............................929
not associated with a community........................986
policy-based route export.........................................931
received through a neighbor.................................1005
sent to a specific interface......................................989
terse information.......................................................1025
Routing Engines
illustrations.....................................................................301
status, displaying.........................................................607
storage media
ACX Series, M Series, MX Series, T Series,
TX Matrix, TX Matrix Plus, and JCS
routers................................................................303
RPKI
information,
displaying.................1030, 1032, 1034, 1036, 1039
RPM See real-time performance monitoring
S
SAToP
emulation on T1/E1 interfaces.........................102, 217
1057
SCB
serial numbers, displaying................................................484
SFM
shortest path first.................................................................759
show (ospf | ospf3) interface command...................830
show (ospf | ospf3) io-statistics command.............836
show (ospf | ospf3) log command...............................838
show (ospf | ospf3) neighbor command....................842
show (ospf | ospf3) overview command...................849
show (ospf | ospf3) route command...........................854
show (ospf | ospf3) statistics command...................860
show bgp neighbor command........................................343
show bgp replication command.....................................357
show bgp summary command......................................359
show chassis alarms command....................................364
show chassis craft-interface command......................377
show chassis environment command........................390
show chassis feb command............................................442
show chassis firmware command................................446
show chassis fpc command.............................................457
show chassis hardware command...............................484
show chassis mac-addresses command..................588
show chassis pic command............................................594
show chassis routing-engine............................................301
show chassis routing-engine command.....................607
show chassis synchronization command...................627
show class-of-service interface command................631
command............................................................................657
show dhcp relay binding command..............................661
show dhcp relay statistics command..........................658
show interfaces (ATM) command................................666
show interfaces (T1, E1, or DS) command...................701
show interfaces statistics command............................726
show isis database command........................................739
show isis hostname command.......................................746
show isis interface command..........................................747
show isis overview command..........................................752
show isis route command.................................................755
show isis spf command.....................................................759
show isis statistics command.........................................764
interfaces command.......................................................767
mep-database command.............................................791
mep-statistics command.............................................778
1058

sla-iterator-statistics command...............................802
synthetic-loss-statistics command.........................807
show ospf database command......................................810
show ospf3 database command...................................819
show poe controller command......................................864
show poe telemetries interface command................867
show ptp global-information command.....................872
show ptp statistics command.........................................877
show route active-path command...............................885
show route advertising-protocol command.............890
show route all command..................................................895
show route aspath-regex command............................897
show route best command.............................................899
show route brief command.............................................902
show route command........................................................879
show route community command...............................904
show route community-name command.................906
show route damping command....................................908
show route detail command............................................914
show route exact command............................................929
show route export command...........................................931
show route extensive command....................................933
show route flow validation command........................948
show route forwarding-table command....................950
show route hidden command........................................964
show route inactive-path command............................967
show route inactive-prefix command...........................971
show route instance command......................................973
show route next-hop command...................................980
show route no-community command........................986
show route output command........................................989
show route protocol command......................................993
show route receive-protocol command...................1005
show route table command............................................1014
show route terse command...........................................1025
command.........................................................................1028
show system storage..........................................................304
show validation database command........................1030
show validation group command................................1032
command.........................................................................1034
show validation session command............................1036
show validation statistics command.........................1039
slave clock
unicast-negotiation............................................279, 281
slave ptp clock interface, configuring...........................259
Index
slave ptp clock, configuring...............................................257

slave, PTP boundary overview...........................................26
SNMP
standards documents................................................140
software packages
upgrading individual...................................................305
SPF calculations, displaying............................................838
SSB
standard stateless firewall filters
actions
nonterminating......................................................88
terminating..............................................................86
standards documents
SNMP and MIBs.............................................................141
stateless firewall filters
actions, nonterminating
actions, terminating
statistics
interfaces
displaying...............................................................726
storage media........................................................................302
device names
ACX Series, M Series, MX Series, T Series,
TX Matrix, TX Matrix Plus, and JCS
routers................................................................303
M Series, MX Series, T Series, TX Series, and TX
Matrix Plus routers..................................................302
support, technical See technical support
switchover-delay statement
usage guidelines...........................................................124
synchronization source, displaying................................627
synchronization statement
ACX Series............................................................240, 242
synchronous Ethernet
ACX Series........................................................................34
Synchronous Ethernet
ACX Series............................................................240, 242
syntax conventions................................................................xxi
System Control Board See SCB
system memory
M Series, MX Series, T Series, TX series, and TX
Matrix Plus routers..................................................301
T
T1 interfaces
T1/E1 BITS interface
ACX Series........................................................................99
T1/E1 interfaces
SAToP emulation..................................................102, 217
TDM
pseudowire......................................................................125
technical support
contacting JTAC............................................................xxiii
test interface e1-bert-start command........................1041
test interface e1-bert-stop command........................1042
test interface t1-bert-start command........................1043
test interface t1-bert-stop command........................1044
TFTP, for autoinstallation.........................................46, 290
timeslots
CE interfaces..................................................................216
Trivial File Transfer Protocol (TFTP), for
autoinstallation........................................................46, 290
U
unicast-negotiation, boundary clock............................275
upgrades
installing from remote server.................................296
upgrading or downgrading Junos OS...........................305
V
validating software compatibility.................................308
VC tunnel CoS
ATM interfaces................................................................54
version
firmware, displaying...................................................446
VLAN CCC encapsulation
VPLS
1059
1060

Acx Series

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Acx Series

Încărcat de

Drepturi de autor:

Formate disponibile

Junos OS

ACX Series Universal Access Router Configuration

Copyright 2013, Juniper Networks, Inc.

Juniper Networks, Inc.

Junos OS ACX Series Universal Access Router Configuration Guide

END USER LICENSE AGREEMENT

Copyright 2013, Juniper Networks, Inc.

Copyright 2013, Juniper Networks, Inc.

ACX Series Universal Access Router Configuration Guide

Copyright 2013, Juniper Networks, Inc.

Configuring Shaping on an ATM IMA Pseudowire . . . . . . . . . . . . . . . . . . . . . . . . . 68

Interfaces and Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Layer 2 and Layer 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Copyright 2013, Juniper Networks, Inc.

ACX Series Universal Access Router Configuration Guide

Configuring the MTU Advertised for a Layer 2 Circuit . . . . . . . . . . . . . . . . . . . . . . . 111

MPLS, VPNs, and Pseudowires . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Network Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Operations, Administration, and Management (OAM) . . . . . . . . . . . . . . . . 167

Copyright 2013, Juniper Networks, Inc.

Configuring Two UNIs Sharing the Same EVC . . . . . . . . . . . . . . . . . . . . . 176

Copyright 2013, Juniper Networks, Inc.

ACX Series Universal Access Router Configuration Guide

Associating the Iterator Profile with MEPs for ETH-SLM . . . . . . . . . . . . . . . 203

Routing Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

Time Division Multiplexing (TDM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

Timing and Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

Copyright 2013, Juniper Networks, Inc.

Configuring PTP Multicast Master and Slave Ports for Ethernet

Upgrade and Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289

Junos Configuration Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313

Configuration Statement Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321

Copyright 2013, Juniper Networks, Inc.

ACX Series Universal Access Router Configuration Guide

Monitoring Commands for the ACX Universal Access Router . . . . . . . . . . 325

Copyright 2013, Juniper Networks, Inc.

show (ospf | ospf3) io-statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 836

Copyright 2013, Juniper Networks, Inc.

ACX Series Universal Access Router Configuration Guide

Troubleshooting Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1047

Copyright 2013, Juniper Networks, Inc.

Interfaces and Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

MPLS, VPNs, and Pseudowires . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Operations, Administration, and Management (OAM) . . . . . . . . . . . . . . . . 167

Time Division Multiplexing (TDM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

Upgrade and Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289

Copyright 2013, Juniper Networks, Inc.

ACX Series Universal Access Router Configuration Guide

Copyright 2013, Juniper Networks, Inc.

Interfaces and Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Copyright 2013, Juniper Networks, Inc.

ACX Series Universal Access Router Configuration Guide

Table 19: Platform Support for Channelized OC3/STM1 (Multi-Rate) Circuit

Network Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Timing and Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

Upgrade and Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289

Monitoring Commands for the ACX Universal Access Router . . . . . . . . . . 325

Copyright 2013, Juniper Networks, Inc.

Table 56: show isis spf Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 759

Copyright 2013, Juniper Networks, Inc.

ACX Series Universal Access Router Configuration Guide

Troubleshooting Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1047

Copyright 2013, Juniper Networks, Inc.

About the Documentation