Junos Fusion PDF
Junos Fusion PDF
Junos Fusion PDF
Modified: 2019-09-24
Juniper Networks, the Juniper Networks logo, Juniper, and Junos are registered trademarks of Juniper Networks, Inc. in the United States
and other countries. All other trademarks, service marks, registered marks, 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.
The information in this document is current as of the date on the title page.
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.
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
https://support.juniper.net/support/eula/. By downloading, installing or using such software, you agree to the terms and conditions of
that EULA.
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 https://www.juniper.net/books.
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.
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.
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:
[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:
For more information about the load command, see CLI Explorer.
Documentation Conventions
Caution Indicates a situation that might result in loss of data or hardware damage.
Laser warning Alerts you to the risk of personal injury from a laser.
Table 2 on page xviii defines the text and syntax conventions used in this guide.
Bold text like this Represents text that you type. To enter configuration mode, type the
configure command:
user@host> configure
Fixed-width text like this Represents output that appears on the user@host> show chassis alarms
terminal screen.
No alarms currently active
Italic text like this • Introduces or emphasizes important • A policy term is a named structure
new terms. that defines match conditions and
• Identifies guide names. actions.
Italic text like this Represents variables (options for which Configure the machine’s domain name:
you substitute a value) in commands or
configuration statements. [edit]
root@# set system domain-name
domain-name
Text like this Represents names of configuration • To configure a stub area, include the
statements, commands, files, and stub statement at the [edit protocols
directories; configuration hierarchy levels; ospf area area-id] hierarchy level.
or labels on routing platform • The console port is labeled CONSOLE.
components.
< > (angle brackets) Encloses optional keywords or variables. stub <default-metric metric>;
# (pound sign) Indicates a comment specified on the rsvp { # Required for dynamic MPLS only
same line as the configuration statement
to which it applies.
[ ] (square brackets) Encloses a variable for which you can community name members [
substitute one or more values. community-ids ]
GUI Conventions
Bold text like this Represents graphical user interface (GUI) • In the Logical Interfaces box, select
items you click or select. All Interfaces.
• To cancel the configuration, click
Cancel.
> (bold right angle bracket) Separates levels in a hierarchy of menu In the configuration editor hierarchy,
selections. select Protocols>Ospf.
Documentation Feedback
We encourage you to provide feedback so that we can improve our documentation. You
can use either of the following methods:
• Online feedback system—Click TechLibrary Feedback, on the lower right of any page
on the Juniper Networks TechLibrary site, and do one of the following:
• Click the thumbs-up icon if the information on the page was helpful to you.
• Click the thumbs-down icon if the information on the page was not helpful to you
or if you have suggestions for improvement, and use the pop-up form to provide
feedback.
Technical product support is available through the Juniper Networks Technical Assistance
Center (JTAC). If you are a customer with an active Juniper Care or Partner Support
Services 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 hours of operation—The JTAC centers have resources available 24 hours a day,
7 days a week, 365 days a year.
• Find solutions and answer questions using our Knowledge Base: https://kb.juniper.net/
To verify service entitlement by product serial number, use our Serial Number Entitlement
(SNE) Tool: https://entitlementsearch.juniper.net/entitlementsearch/
• Visit https://myjuniper.juniper.net.
Junos Fusion Provider Edge brings the Junos Fusion technology to the service provider
edge. In a Junos Fusion Provider Edge, MX Series 5G Universal Routing Platforms act as
aggregation devices while EX4300 Series and QFX5100, QFX 5110, or QFX5200 Series
switches act as satellite devices.
In a Junos Fusion Provider Edge topology, each satellite device has at least one connection
to the aggregation device. The aggregation device acts as the single point of management
for all devices in the Junos Fusion Provider Edge. The satellite devices provide network
interfaces that send and receive network traffic.
Figure 1 on page 4 provides an illustration of a basic Junos Fusion Provider Edge topology.
The MX Series 5G Universal Routing Platform acting as the aggregation device in Junos
Fusion Provider Edge is responsible for almost all management tasks, including interface
configuration for every satellite device interface in the topology. The aggregation device
runs Junos OS software for the entire Junos Fusion Provider Edge, and the network-facing
interfaces on the satellite devices—extended ports—are configured from the aggregation
device and support features that are supported by the version of Junos OS running on
the aggregation device.
The satellite devices and the aggregation device maintain the control plane for the Junos
Fusion Provider Edge using multiple internal satellite management protocols. Network
traffic can be forwarded between satellite devices through the aggregation device. Junos
Fusion Provider Edge supports the IEEE 802.1BR standard.
• Simplified network topology—You can combine multiple devices into a topology that
appears to the larger network as a single device, and then manage the device from a
single IP address.
• Manageability—You can manage a Junos Fusion Provider Edge that supports a large
number of network-facing interfaces from a single point. The single point of
management, the aggregation device, runs Junos OS software for the entire Junos
Fusion Provider Edge.
• Flexibility—You can easily expand the size of your Junos Fusion Provider Edge by adding
satellite devices to it as your networking needs grow.
The satellite devices and the aggregation device maintain the control plane for the Junos
Fusion using multiple internal satellite management protocols. Junos Fusion supports
the IEEE 802.1BR standard.
The aggregation device acts as the single point of management for all devices in the
Junos Fusion. All Junos Fusion management responsibilities, including interface
configuration for every satellite device interface in the Junos Fusion, are handled by the
aggregation device. The aggregation device runs Junos OS software for the entire Junos
Fusion, and the interfaces on the satellite devices are configured from the aggregation
device and support features that are supported by the version of Junos OS running on
the aggregation device.
Aggregation Devices
An aggregation device:
• is an MX5, MX10, MX40, MX80, MX104, MX204, MX240, MX480, MX960, MX2010,
MX2020, or MX10003 Universal Routing Platform in a Junos Fusion Provider Edge.
• Manages the entire Junos Fusion. All Junos Fusion configuration management is handled
on the aggregation device, including interface configuration of the satellite device
interfaces.
The hardware specifications for aggregation devices in a Junos Fusion Provider Edge are
discussed in greater detail in Understanding Junos Fusion Provider Edge Software and
Hardware Requirements.
Satellite Devices
A satellite device:
• Is an EX4300, QFX 5100, QFX5110, or QFX5200 switch in a Junos Fusion Provider Edge.
• Runs a version of satellite software after being converted into a satellite device.
• Provides network interfaces to send and receive traffic for the Junos Fusion.
The hardware specifications for satellite devices in a Junos Fusion Provider Edge are
discussed in greater detail in Understanding Junos Fusion Provider Edge Software and
Hardware Requirements.
Cascade Ports
A cascade port is a port on an aggregation device that sends and receives control and
network traffic from an attached satellite device. All traffic passed between a satellite
device and the aggregation device in a Junos Fusion traverses the cascade port.
The link that connects an aggregation device to a satellite device has an interface on
each end of the link. The interface on the aggregation device end of the link is a cascade
port. The interface on the satellite device end of the link is an uplink port.
Satellite devices are added to a Junos Fusion by configuring the interface on the
aggregation device end of a link into a satellite device.
A cascade port is typically a 10-Gbps SFP+ interface or a 40-Gbps QSFP+ interface, but
any interface on the aggregation device that connects to the satellite device can be
converted into a cascade port.
The location of the cascade ports in a Junos Fusion are illustrated in Figure 3 on page 7.
The hardware specifications for cascade ports in a Junos Fusion Provider Edge are
discussed in greater detail in Understanding Junos Fusion Provider Edge Software and
Hardware Requirements.
Uplink Ports
An uplink port is a physical interface on a satellite device that provides a connection to
an aggregation device. All network and control traffic on a satellite device that is
transported to an aggregation device is sent or received on the satellite device’s uplink
port.
The link that connects an aggregation device to a satellite device has an interface on
each end of the link. The interface on the aggregation device end of the link is a cascade
port. The interface on the satellite device end of the link is an uplink port.
Uplink ports are automatically created when a cascade port is configured on the
aggregation device end of the link.
An uplink port is typically a 10-Gbps SFP+ interface or a 40-Gbps QSFP+ interface, but
any 1-Gbps interface on the aggregation device that connects to the satellite device can
also be converted into a cascade port.
Extended Ports
An extended port is a network-facing port on a satellite device that transmits and receives
network traffic for the Junos Fusion.
Each network-facing port on a satellite device in a Junos Fusion is also an extended port.
A single cascade port is associated with multiple extended ports.
The FPC ID is used for Junos Fusion configuration, monitoring, and maintenance. Interface
names—which are identified using the type-fpc / pic / port format—use the FPC ID as the
fpc variable when the satellite device is participating in a Junos Fusion. For instance,
built-in port 2 on PIC 0 of a satellite device—a gigabit Ethernet interface on a satellite
device that is using 101 as it’s FPC ID— uses ge-101/0/2 as it’s interface name. The valid
range for the FPC ID is 100 -255 in Junos OS Release 14.2 and 65 to 254 in Junos OS
Release 16.1 and later.
In unique-ID based FPC identification, the FPC ID is mapped to the serial number or MAC
address of the satellite device. For instance, if a satellite device whose serial number was
ABCDEFGHIJKL was assigned to FPC ID 110 using unique-ID based FPC identification,
the satellite device with the serial number ABCDEFGHIJKL will always be associated
with FPC ID 110 in the Junos Fusion. If the satellite device with the serial number
ABCDEFGHIJKL connects to the aggregation device using a different cascade port, the
FPC ID for the satellite device remains 110.
In connectivity-based FPC identification, the FPC ID is mapped to the cascade port. For
instance, connectivity-based FPC identification can be used to assign FPC ID 120 to the
satellite device that connects to the aggregation device using cascade port xe-0/0/2.
If the existing satellite device that connects to cascade port xe-0/0/2 is replaced by a
new satellite device, the new satellite device connected to the cascade port assumes
FPC ID 120.
an FPC ID is associated with it. The show chassis satellite unprovision output includes
a list of satellite devices that are not participating in a Junos Fusion due to an FPC ID
association issue.
The satellite devices, meanwhile, run satellite software that has the built-in intelligence
to extend the feature set on the Junos OS software onto the satellite device.
The role of Junos OS and satellite software is discussed in greater detail in “Understanding
Software in a Junos Fusion Provider Edge” on page 18.
The software specifications for a Junos Fusion Provider Edge are discussed in greater
detail in Understanding Junos Fusion Provider Edge Software and Hardware Requirements.
In a Junos Fusion, the interface names on the satellite devices follow this naming
convention, where:
• The type does not change for the interface when it becomes part of a Junos Fusion.
The type for an xe interface, for instance, remains xe regardless of whether the interface
is or isn’t in a Junos Fusion.
You will see internally created sd interfaces in a Junos Fusion. The sd interfaces map
to uplink ports, and are used internally by the Junos Fusion to process some types of
traffic.
• The fpc identifier in a Junos Fusion, which is user-configurable, is the FPC slot identifier.
See “Understanding FPC Identifiers and Assignment in a Junos Fusion Fabric” on page 8.
For instance, built-in port 2 on PIC 0—a gigabit Ethernet interface that is acting as an
extended port—on an EX4300 switch that is acting as FPC slot 101 would be identified
as:
ge-101/0/2
Satellite device clustering is particularly useful in scenarios where optical cabling options
between buildings are limited and in scenarios where you want to preserve optical
interfaces for other purposes. If you have, for instance, two buildings that have limited
optical interfaces between each other and you want to put an aggregation device in one
building and ten satellite devices in the other building, you can group the ten satellite
devices into a cluster and connect the cluster to the aggregation device with a single
cable.
Aggregation
Device
g043014
The cluster name and ID are used by the aggregation device to identify a cluster for
configuration, monitoring, and troubleshooting purposes.
The cluster name and ID are set using the set chassis satellite-management cluster
cluster-name cluster-id cluster-id-number statement.
In a dual aggregation device topology using satellite device clustering, each satellite
device cluster must have at least one uplink interface connection to both aggregation
devices. The uplink interfaces to the aggregation devices can be on any member satellite
devices in each satellite device cluster.
NOTE: Junos Fusion Provider Edge supports only one aggregation device.
A satellite device cluster supports multiple uplink interfaces. The uplink interfaces can
be on any satellite devices that are members of the satellite device cluster. The
advantages of configuring multiple uplink interfaces for a satellite device cluster is
resiliency—all traffic can be forwarded to another uplink interface if an uplink interface
fails—and efficiency—multiple uplink interfaces can reduce the number of hops that
traffic takes across a cluster before it is forwarded to an aggregation device.
Cluster Interfaces
Clustering ports are interfaces that interconnect satellite devices in the same satellite
device cluster.
Traffic originating from an access device connected to an extended port travels over
cluster interfaces to get to an uplink port. Traffic from an aggregation device travels to
a satellite device uplink port then over cluster interfaces before it is delivered to an access
device connected to an extended port.
Cluster interfaces are typically 10-Gbps SFP+ interfaces. 10-Gbps SFP+ and 40-Gbps
QSFP+ interfaces can be used as cluster interfaces. Other interfaces cannot be used as
cluster interfaces by default. To use other interfaces as cluster interfaces, you must
configure a candidate uplink port policy.
See Configuring Uplink Port Policies on a Junos Fusion for additional information on
candidate uplink port policies.
See Understanding Junos Fusion Enterprise Software and Hardware Requirements for
information on software requirements for satellite devices in a satellite device cluster.
For this reason, all interface naming for satellite device cluster member switches is not
impacted by cluster membership. If a switch is assigned FPC ID 103, for instance, the
aggregation device views the satellite device as FPC 103 regardless of whether it is or is
not part of a satellite device cluster.
The FPC ID is used in the FPC slot name for an extended port interface; for instance,
ge-103/0/2. An extended port is any network-facing interface on a satellite device. As
with FPC ID naming, extended port interface names are not impacted by satellite device
cluster membership status.
NOTE: Satellite devices in a cluster are configured using the unique ID-based
FPC identification method of FPC identifier assignment. For more information,
see Understanding FPC Identifiers and Assignment in a Junos Fusion in
Understanding Junos Fusion Enterprise Components.
Understanding 40-Gbps Interfaces with QSFP+ Transceiver Roles for Satellite Devices in a
Satellite Device Cluster
40-Gbps QSFP+ interfaces on satellite devices in a satellite device cluster can be used
as clustering ports to cable to other satellite devices in the cluster or as uplink ports to
cable the satellite device cluster to the aggregation device.
40-Gbps QSFP+ interfaces on EX2300, EX3400, EX4300 and QFX5100 satellite devices
are default uplink ports. Please see Table 3 on page 12for the default uplink ports for
satellite devices. When these devices are part of a satellite device cluster, the default
uplink ports cannot be configured as extended ports to pass network traffic unless they
have a direct connection to the aggregation device or if there is an uplink port policy
configured that excludes them from acting as uplink ports.
Table 3: Default Uplink Interfaces for Junos Fusion Enterprise Satellite Devices
EX3400 (4 ports each on PIC1 and PIC2) 1/0 through 1/3 and 2/0 through 2/3
EX4300-24T (4 ports each on PIC1 and PIC2) 1/0 through 1/3 and 2/0 through 2/3
Table 3: Default Uplink Interfaces for Junos Fusion Enterprise Satellite Devices (continued)
EX4300-32F (4 ports on PIC 0, 2 ports on PIC 1 and 8 ports on PIC 0/32 through 0/35
2)
1/0 through 1/1
EX4300-48T (4 ports each on PIC1 and PIC2) 1/0 through 1/3 and 2/0 through 2/3
EX4300-48T-BF (4 ports each on PIC1 and PIC2) 1/0 through 1/3 and 2/0 through 2/3
EX4300-48T-DC (4 ports each on PIC1 and PIC2) 1/0 through 1/3 and 2/0 through 2/3
EX4300-48T-DC-BF (4 ports each on PIC1 and PIC2) 1/0 through 1/3 and 2/0 through 2/3
In a Junos Fusion topology, cascade, uplink, and extended ports are components that
play key roles. Figure 5 on page 14 and Figure 6 on page 15 show sample Junos Fusion
topologies, which serve as points of reference for this discussion of cascade, uplink, and
extended ports.
In the Junos Fusion topology shown in Figure 5 on page 14, two aggregation devices and
two satellite devices are deployed. The aggregation devices are connected to each other
through a multichassis link aggregation group (MC-LAG). Each satellite device is
connected to its respective aggregation device through one or two links.
In the Junos Fusion Data Center topology shown in Figure 6 on page 15, four aggregation
devices and four satellite devices are deployed. The four aggregation devices form an
EVPN core fabric wherein each satellite device is multihomed to each aggregation device.
Also, in this topology, some hosts are single-homed to a satellite device, and other hosts
are multihomed to two satellite devices.
On the aggregation devices in each illustration, each link is connected to a cascade port
(for example, CP1 on Aggregation device 1), while on the satellite devices, each link is
connected to an uplink port (for example, UP1 on Satellite device 1). Hosts 1 through 4
are connected to Satellite device 1 through extended ports EP1 through EP4, and so on.
Figure 5: Cascade, Uplink, and Extended Ports in a Junos Fusion Topology With Two
Aggregation Devices and MC-LAG
Figure 6: Cascade, Uplink, and Extended Ports in a Junos Fusion Data Center Topology
With Four Aggregation Devices and EVPN
On an aggregation device, you can set up one or more cascade port connections with a
satellite device. For example, in the Junos Fusion topology shown in Figure 5 on page 14,
Aggregation device 1 has one cascade port connection (CP1) to Satellite device 1, and
Aggregation device 2 has two cascade port connections (CP2 and CP3) to Satellite device
2. In the Junos Fusion Data Center in Figure 6 on page 15, where EVPN multihoming is
implemented, each aggregation device is connected to each satellite device through one
cascade port. For example, on Aggregation device 1, cascade port CP1 is connected to
the leftmost satellite device, cascade port CP2 is connected to the next satellite device,
and so on.
When there are multiple cascade port connections to a satellite device, as shown in
Figure 5 on page 14, the traffic handled by the ports is automatically load-balanced. For
a packet destined for a satellite device, the cascade port over which to forward the packet
is chosen based on a per-packet hash that is computed using key fields in the packet.
To select the key fields to be used, you can specify the hash-key statement in the [edit
forwarding-options] hierarchy or the enhanced-hash-key statement in the [edit
forwarding-options], [edit logical-systems logical-system-name routing-instances
instance-name forwarding-options], and [edit routing-instances instance-name
forwarding-options] hierarchies.
In addition, a cascade port can handle the traffic for all extended ports on a particular
satellite device. However, you cannot specify that a particular cascade port handle the
traffic for a particular extended port.
After you configure an interface as a cascade port (for example, by issuing set interfaces
xe-0/0/1 cascade-port), you cannot configure the interface as a Layer 2 interface (for
example, by issuing set interfaces xe-0/0/1 unit 0 family bridge) or a Layer 3 interface (for
example, set interfaces xe-0/0/1 unit 0 family inet). If you try to configure a cascade port
as a Layer 2 or Layer 3 interface, you receive an error message.
After a cascade port is configured on the aggregation device end of a link, a corresponding
uplink port is automatically created on the satellite device. From the aggregation device,
you can monitor port and queue statistics for uplink ports. However, we do not recommend
that you configure Layer 2 or Layer 3 forwarding features on uplink ports.
On a satellite device, you can set up one or more uplink port connections to an aggregation
device. For example, in the Junos Fusion topology shown in Figure 5 on page 14, Satellite
device 1 has one uplink port (UP1) to Aggregation device 1, and Satellite device 2 has two
uplink ports (UP2 and UP3) to Aggregation device 2. In the Junos Fusion Data Center in
Figure 6 on page 15, where EVPN multihoming is implemented, each satellite device is
connected to each aggregation device through an uplink port. For example, on the leftmost
satellite device, uplink port UP1 is connected to Aggregation device 1, uplink port UP2 is
connected to Aggregation device 2, and so on.
When a satellite device has multiple uplink ports to an aggregation device, the traffic
from the extended ports is automatically load-balanced among the uplink ports. For
example, in the Junos Fusion topology shown in Figure 5 on page 14, the traffic from
extended ports EP5 through EP8 is load balanced between uplink ports UP2 and UP3 to
reach Aggregation device 2. In this situation, each packet is examined, and if an IPv4 or
IPv6 header is found, a load-balancing algorithm chooses the uplink port based on the
header (source and destination IP addresses, and source and destination TCP/UDP
ports). If an IPv4 or IPv6 header is not found, the load-balancing algorithm chooses the
uplink port based on the Layer 2 header (destination and source MAC addresses,
Ethertype, and outer VLAN ID) of the packet.
On aggregation devices, you can configure extended ports by using the same Junos OS
CLI and naming convention used for Junos OS interfaces on standalone routers and
switches. The only difference is that when you specify an extended port name, the FPC
slot number must be in the range of 100 through 254 in Junos OS Release 14.2 and in the
range of 65 through 254 in Junos OS Release 16.1 and later.
For example, for the four extended ports shown on Satellite device 1 in Figure 5 on page 14
and the leftmost satellite device in Figure 6 on page 15, the FPC slot number could be
100, the PIC slot number could be 0, the first extended port could be 1, the second
extended port could be 2, the third extended port could be 3, and the fourth extended
port could be 4. The complete 10-Gigabit Ethernet extended port names could be as
follows:
xe-100/0/1
xe-100/0/2
xe-100/0/3
xe-100/0/4
• Firewall filters
• CoS policies
Related • Understanding the Flow of Data Packets in a Junos Fusion Topology on page 26
Documentation
• hash-key
• enhanced-hash-key
Junos fusion also supports central Web authentication. Central Web authentication
redirects Web browser requests to a central Web authentication server that manages
the authentication and authorization process. Upon successful authorization, the user is
allowed access to the network. For more information on central Web authentication, see
Understanding Central Web Authentication.
This topic discusses the role of software in a Junos Fusion Provider Edge. It covers:
Fusion, therefore, support features that are supported by the version of Junos OS running
on the aggregation device.
An aggregation device in a Junos Fusion runs the same Junos OS software regardless of
whether it is or is not part of a Junos Fusion. Hence, Junos OS software is acquired,
installed, and managed on an aggregation device in a Junos Fusion in the same manner
that it is acquired, installed, and managed on a standalone device that is not part of a
Junos Fusion.
All satellite devices in a Junos Fusion must run the satellite software. The satellite
software, notably, applies features from the Junos OS software on the aggregation device
onto the satellite device. The satellite software allows the satellite device to participate
in the Junos Fusion, but does not provide any other software features for the satellite
device.
You can run the same version of satellite software on satellite devices that are different
hardware platforms. For instance, if your Junos Fusion included EX4300 and QFX5100
switches as satellite devices, the EX4300 and QFX5100 switches acting as satellite
devices could install the satellite software from the same satellite software package.
Different satellite devices can run different versions of satellite software within the same
Junos Fusion.
You can download satellite software from the software center for any satellite device.
Additionally, you have the option to order some switches with the satellite software
pre-installed from the factory.
The satellite software packages are stored on the aggregation device after a satellite
software package installation—which is typically managed from the aggregation
device—has been executed. The satellite software packages remain in the file system
even if the Junos OS software on the aggregation device is upgraded. The satellite
software packages on an individual satellite device can be updated manually using CLI
commands on the aggregation device but are typically installed using software upgrade
groups, which are discussed in more detail in this document.
A device cannot simultaneously run Junos OS and the satellite software. If you remove
a satellite device from a Junos Fusion, you have to install Junos OS onto the device before
you can use it in your network as a standalone switch.
The satellite software requirements for a Junos Fusion Provider Edge are discussed in
Understanding Junos Fusion Provider Edge Software and Hardware Requirements.
Understanding the Preboot eXecution Environment (PXE) Junos OS Software Package for
QFX5100 Switches in a Junos Fusion
The Preboot eXecution Environment (PXE) software is a version of Junos OS that must
be used to convert a QFX5100 switch that is running satellite software as a satellite
device into a standalone switch that is running Junos OS software.
The first version of PXE software that can be used to convert a QFX5100 switch from a
satellite device to a standalone switch is introduced at Junos OS Release 14.1X53-D16.
The PXE version of Junos OS software supports the same feature set as the other Junos
OS software packages for a release, but is specifically engineered to install Junos OS
onto a device running satellite software.
The PXE version of Junos OS software is required for QFX5100 switches only. Standard
Junos OS software can be used to convert the other devices acting as satellite devices
into standalone devices.
The PXE version of Junos OS software can be downloaded from the Software Center
with the other QFX5100 switch software packages. For more information on PXE software
images, see the Junos OS Release Notes for your software release. For information on
using the PXE version of Junos OS software to convert a QFX5100 device into a standalone
device, see “Converting a Satellite Device in a Junos Fusion to a Standalone Device” on
page 100.
• Must be running Junos OS Release 14.2R3, or a later version of Junos OS Release 14.2.
NOTE: Junos Fusion is not supported in any Junos OS Release 15.1 release.
A satellite device:
• Must be running Junos OS Release 14.1X53-D16 or later prior to being converted into a
satellite device.
For more detailed information about satellite software support, see the Junos OS release
notes for the version of Junos OS running on your aggregation device.
When a satellite device is added to a Junos Fusion, the aggregation device checks if the
satellite device is using an FPC ID that is included in a satellite software upgrade group.
If the device is connected to a satellite device that is using an FPC ID that is part of a
satellite software upgrade group, the device—unless it is already running the same version
of satellite software—upgrades its satellite software using the satellite software
associated with the satellite software upgrade group.
When the satellite software package associated with an existing satellite software group
is changed, the satellite software for all member satellite devices is upgraded using a
throttled upgrade. The throttled upgrade ensures that only a few satellite devices are
updated at a time to minimize the effects of a traffic disruption due to too many satellite
devices upgrading software simultaneously.
Software upgrade groups are configured and managed on the aggregation device.
This topic describes the software and hardware requirements for a Junos Fusion Provider
Edge.
It covers:
Aggregation Devices
This section details the hardware and software requirements for an aggregation device
in a Junos Fusion Provider Edge.
Table 4 on page 22 lists the hardware platforms that are supported as aggregation
devices, and the Junos OS release that introduced aggregation device support to Junos
Fusion Provider Edge for the hardware.
Starting in Junos OS Release 18.1R1, you can configure an aggregation device on a guest
network fusion (GNF) on an MX 960, MX2010, and MX2020 series router. Using Junos
Node Slicing, you can create multiple partitions on a single MX router. These partitions
are referred to as a guest network functions (GNFs). Each MX series router supports a
maximum of 10 GNFs with each GNF supporting a separate aggregation device. The
aggregation device on each GNF supports a maximum of 10 satellite devices.
For more information on Junos Node Slicing, see Junos Node Slicing Overview.
NOTE: In a Junos Fusion Provider Edge topology that has a GNF configured
as the aggregation device, you can only use EX4300 switches as satellite
devices.
NOTE: In the GNF, you should use the following line cards to support the
cascade port on the aggregation device:
• MPC7
• MPC8
• MPC9
Cascade Ports
A cascade port is a port on an aggregation device that sends and receives control and
network traffic from an attached satellite device.
Table 5: MX Series 5G Universal Routing Platform Line Card Cascade Port Support
MPC1 Q 14.2R3
MPC1E Q 14.2R3
MPC2 Q 14.2R3
MPC2E Q 14.2R3
MPC2 EQ 14.2R3
MPC2E EQ 14.2R3
MPC2E NG 14.2R6
MPC2E NG Q 14.2R6
MPC3E 14.2R3
MPC3E NG 14.2R6
MPC3E NG Q 14.2R6
MPC4E 14.2R3
MPC5E 14.2R3
MPC5EQ 14.2R3
MPC6E 14.2R3
MPC7E 16.1R1
MPC8E 16.1R1
MPC9E 16.1R1
Satellite Devices
This section details the hardware and software requirements for a satellite device in a
Junos Fusion Provider Edge.
Table 6 on page 25 lists the hardware platforms that are supported as satellite devices,
as well as the minimum Junos OS release that must be running on the satellite device
before it can be converted from a standalone switch to a satellite device.
When you upgrade the satellite software version to a release later than the recommend
versions listed in the Junos Fusion Hardware and Software Compatibility Matrices, your
Junos Fusion system will only benefit from the satellite software fixes. To acquire the full
benefits of a satellite software release, including satellite software fixes and new features,
we recommend you upgrade both the aggregation device software and its compatible
satellite device software for a complete upgrade.
A satellite device that supports Power over Ethernet (PoE) must be running the minimum
PoE controller software version. The EX4300 series switches must be running PoE
controller software version 2.6.3.9.2.1 or higher.
To check the PoE controller software version, enter the show chassis firmware detail
command and view the PoE firmware output.
For information on checking and upgrading the PoE controller software, see Upgrading
the PoE Controller Software.
Junos Fusion Provider Edge supports up to eighteen satellite devices on the MX5, MX10,
MX40, MX80, and MX104 Universal Routing Platform. For all other MX Series routers,
Junos Fusion Provider Edge supports up to sixty-four satellite devices.
18.1R1 Starting in Junos OS Release 18.1R1, you can configure an aggregation device
on a guest network fusion (GNF) on an MX 960, MX2010, and MX2020
series router.
All Ethernet data packets that are exchanged between aggregation devices and satellite
devices in a Junos Fusion topology include an E-channel tag (ETAG) header that carries
an E-channel identifier (ECID) value. The ECID value, which is assigned by the aggregation
device, identifies the source or destination extended port on one of the connected satellite
devices.
• Scenario 1—A host on one satellite device sends a packet to another host on the same
satellite device. For example, Host 2 sends a unicast packet to Host 4. Both hosts are
connected to Satellite device 1. (See Figure 7 on page 27.)
• Scenario 2—A host on one satellite device sends a packet to another host on the other
satellite device. For example, Host 2, which is connected to Satellite device 1, sends a
unicast packet to Host 7, which is connected to Satellite device 2. (See
Figure 8 on page 28.).
Figure 7: Layer 2 Unicast Data Packet Flow Through a Junos Fusion Topology—Scenario
1
Figure 8: Layer 2 Unicast Data Packet Flow Through a Junos Fusion Topology—Scenario
2
In scenario 1, where Host 2 sends a unicast data packet to Host 4, the following events
occur:
NOTE: Only the events that are performed by Junos Fusion components are
listed. Events handled by components that are not specific to the Junos Fusion
topology are excluded.
1. Extended port EP2 on Satellite device 1 receives the packet from Host 2.
2. Satellite device 1 inserts an ETAG header in the packet. The ETAG header carries the
ECID value (ECID 2), which is assigned by Aggregation device 1 to extended port EP2.
3. On Satellite device 1, two uplink ports (UP1 and UP2) are connected to Aggregation
device 1. As a result, traffic between the devices can be load-balanced. In this case,
uplink port UP1 is chosen to forward the packet to cascade port CP1 on Aggregation
device 1.
4. On receiving the packet, Aggregation device 1 extracts the ECID value (ECID 2) from
the ETAG header of the packet and learns that the packet is from extended port EP2
on Satellite device 1. Aggregation device 1 then removes the ETAG header from the
packet.
5. Aggregation device 1 performs a lookup for Host 4. The result of the lookup is extended
port EP4 on Satellite device 1.
6. On Aggregation device 1, two cascade ports (CP1 and CP2) are connected to Satellite
device 1. As a result, traffic between the devices can be load-balanced. In this case,
cascade port CP2 is chosen to forward the packet to uplink port UP2 on Satellite
device 1.
7. The packet is forwarded to cascade port CP2, where a new ETAG header and ECID
value (ECID 4), which is assigned by Aggregation device 1 to extended port EP4, is
added.
9. Satellite device 1 extracts the ECID value (ECID 4) from the ETAG header of the packet,
then maps ECID 4 to extended port EP4.
In scenario 2, where Host 2 sends a unicast data packet to Host 7, the events that occur
are the same as for scenario 1 except for the following:
• Event 5—Aggregation device 1 performs a lookup for Host 7. The result of the lookup
is extended port EP7 on Satellite device 2.
• Event 6—On Aggregation device 1, two cascade ports (CP3 and CP4) are connected
to Satellite device 2. As a result, traffic between the devices can be load-balanced. In
this case, cascade port CP4 is chosen to forward the packet to uplink port UP4 on
Satellite device 2.
• Event 7—The packet is forwarded to cascade port CP4, where a new ETAG header and
ECID value (ECID 7), which is assigned by Aggregation device 1 to extended port EP7,
is added.
• Event 9—Satellite device 2 extracts the ECID value (ECID 7) from the ETAG header of
the packet, and then maps ECID 7 to extended port EP7.
Environment monitoring of the satellite devices, uplink failure detection for satellite
device uplink ports, and remapping uplinks—with port pinning, uplink selection, and local
port mirroring—are configured using satellite policies. See “Understanding Environment
Monitoring Satellite Policies” on page 31, “Understanding Uplink Failure Detection Satellite
Policies” on page 31, and “Understanding Satellite Policies for Remapping Uplink Traffic
Flows on a Junos Fusion Data Center” on page 31.
Satellite policies are configured as independent policies on the aggregation device, and
then associated with the Junos Fusion configuration.
In the environment monitoring satellite policy, you define how you want a link-down
alarm from a satellite device to be handled by the Junos Fusion. The Junos Fusion can
treat the link-down alarm as a yellow or red alarm, or it can be configured to ignore the
alarm.
The environment monitoring policy provides the flexibility to define different alarm
handling based on user preference. You can, for instance, assign environment monitoring
policies to individual satellite devices based on FPC ID. You can also configure environment
monitoring policies based on the product model of the satellite devices, if desired. You
can, for instance, specify that all link-down alarms from EX4300 switches acting as
satellite devices are treated as yellow alarms, while all link-down alarms from QFX5100
switches acting as satellite devices are treated as red alarms.
An environment monitoring policy is applied for a single satellite device in a Junos Fusion
using the environment-monitoring-policy statement in the [edit chassis
satellite-management] or the [edit chassis satellite-management fpc slot-id] hierarchy
levels.
You can configure a different environment monitoring policy for a single satellite device
in the fpc slot-id when an environment monitoring policy for all satellite devices is
configured. The environment monitoring policy for the FPC is enabled in cases when both
an individual and global environment monitoring policy is configured.
NOTE: Uplink failure detection is supported only on Junos Fusion Data Center.
For information on uplink failure detection within a Junos Fusion, see “Overview of Uplink
Failure Detection on a Junos Fusion” on page 603.
Understanding Satellite Policies for Remapping Uplink Traffic Flows on a Junos Fusion Data
Center
Satellite policies are used to configure the remapping of uplink traffic flows within a Junos
Fusion Data Center. You can configure uplink port pinning and flow-based uplink selection
to improve load-balancing of traffic flows across uplink ports. You can use local port
mirroring to troubleshoot and monitor applications.
See Understanding Remapping Uplink Traffic Flows on a Junos Fusion Data Center.
Junos Fusion Provider Edge expands the number of available network interfaces on an
aggregation device by connecting satellite devices that act as extensions of the
aggregation device. The entire system—the interconnected aggregation device and
satellite devices—is called a Junos Fusion. Junos Fusion Provider Edge simplifies network
aggregation device administration because the aggregation device acts as a single,
port-dense device, managed using one IP address.
• BGP
• IS-IS
• OSPF
• OSPF version 3
You can configure the following Layer 3 routing protocols on satellite device extended
ports that are included in link aggregation groups (LAGs):
• BGP
• IS-IS
• OSPF
Bidirectional Forwarding Detection (BFD) is a protocol used to detect failure in the data
path. Hello packets are sent at a specified, regular interval. A neighbor failure is detected
when the routing device stops receiving a reply after a specified interval. BFD works with
a wide variety of network environments and topologies.
Open Shortest Path First (OSPF) is a routing protocol for IP networks using a link state
routing algorithm. This interior routing protocol operates within a single autonomous
system. For more information, see the OSPF Feature Guide and the CLI statements ospf
and ospf3.
• PIM
• IGMP
• MLD
sparse Mode (default), PIM dense Mode, bidirectional PIM, and PIM source-specific
multicast.For more information, see the PIM Overview and the CLI statement pim.
Junos Fusion supports multicast and broadcast packet replication on the aggregation
device and the satellite devices. For more information on multicast replication, see
“Understanding Multicast Replication in a Junos Fusion” on page 637.
• Layer 2 Circuits
• Layer 2 VPNs
• Layer 3 VPNs
• VPLS
You can configure a local switching interface to ignore the MTU configuration set for an
associated physical interface. This enables you to bring up a circuit between two logical
interfaces that are defined on physical interfaces with different MTU values. For more
information, see the Configuring Interfaces for Layer 2 Circuits Overview.
Layer 3 traffic, while the service provider needs to know only how much traffic the Layer 2
VPN needs to carry. For more information, see the Layer 2 VPNs and VPLS Feature Guide
for Routing Devices.
Layer 3 VPNs also provide communication between a provider network and a customer
network. However, in a Layer 3 VPN, routing occurs on the service provider’s router.
Therefore, Layer 3 VPNs require more configuration on the part of the service provider,
because the service provider’s PE routers must store and process the customer’s routes.
For more information, see the Layer 3 VPNs Feature Guide for Routing Devices.
You can configure ports on the satellite devices managed by MX Series routers to support
Ethernet VPNs (EVPNs) with Virtual Extensible LAN (VXLAN) encapsulation. EVPN
provides layer 2 VPN services with advance multi-homing capabilities by using the BGP
control plane to distribute routes over IP or IP/MPLS backbone. VXLAN is a tunneling
scheme that overlays layer 2 ethernet frames on top of layer 3 UDP packets. EVPN with
VXLAN encapsulation allows you to create a logical network for hosts that span across
a physical network and supports up to 16 million VXLAN segments. For more information
on EVPN and VXLAN, see Understanding EVPN with VXLAN Data Plane Encapsulation
Related • Understanding the Flow of Data Packets in a Junos Fusion Topology on page 26
Documentation
• Junos Fusion Provider Edge Overview on page 3
Junos Fusion supports packet forwarding both on the aggregation device and on satellite
devices. The default behavior is to forward the packets received on the extended port to
the aggregation device. The satellite device does not perform any processing on the
incoming traffic. The aggregation device processes and directs the data traffic.
Local switching in Junos Fusion reduces the traffic that is exchanged between satellite
devices and the aggregation device by handling some of the local switching. When you
enable local switching, the satellite device handles the bridging traffic locally on the
satellite device. The satellite device maintains a bridge forwarding table with the local
MAC addresses for devices that are connected directly to the satellite device and forwards
the data packets with local MAC addresses. Packets with unknown MAC addresses are
sent to the aggregate device. Local switching applies to all the ports on the satellite
device.
[edit forwarding-options]
satellite {
fpc slot {
local-switching;
}
}
[edit forwarding-options]
satellite {
fpc slot {
selective-vlan-switching {
routing-instance routing-instance-name;
}
}
}
When you have digital subscriber line access multiplexer (DSLAM) ports and broadband
network gateway (BNG) ports on a satellite device, you should configure the satellite
device to switch traffic locally from the DSLAM ports to the BNG port while restricting
the traffic between two DSLAM ports. Configure the satellite device to switch traffic
locally from a DSLAM port to a BNG port by including the core-facing keyword in all BNG
port interfaces. Restrict switched traffic between DSLAM ports by including the no-local
switching keyword in the bridge domain.
Policer
Traffic policing enables you to control the maximum rate of traffic that will be sent or
received on an interface. A policer defines a set of traffic rate limits and sets the action
for traffic that does not conform to the configured limits. Packets in a traffic flow that
do not conform to traffic limits are either discarded or are marked with a different
forwarding class or packet loss priority (PLP) level.
You can limit the flow of Layer 2 traffic that is sent to the aggregation device by applying
an ingress policer at the satellite device. You configure the Layer 2 ingress policer by using
the input-policer statement at the [edit interfaces interface-name layer2-policer] hierarchy
level. Because the satellite device is only aware of locally switched logical interface, the
ingress policer is applied to Layer 2 input traffic at the satellite device ports.
• VLANs 101, 102, 103, and 104 are enabled for selective VLAN local switching.
interfaces {
xe-100/0/0 {
unit 0 {
family bridge {
interface-mode trunk;
vlan-id-list [100-110];
core-facing;
}
}
}
xe-100/0/1 {
layer2-policer {
input-policer SD-policer-A;
}
unit 0 {
family bridge {
interface-mode trunk;
vlan-id-list [100-110];
}
}
}
xe-100/0/2 {
layer2-policer {
input-policer SD-policer-A;
}
unit 0 {
family bridge {
interface-mode trunk;
vlan-id-list [100-110];
}
}
}
}
routing-instances {
vs-1 {
instance-type virtual-switch;
interface xe-100/0/0.0;
interface xe-100/0/2.0;
interface xe-100/0/2.0;
bridge-domains {
bd-1 {
vlan-id 101;
no-local-switching;
}
bd-2 {
vlan-id 102;
no-local-switching;
}
bd-3 {
vlan-id 103;
}
bd-4 {
vlan-id 104;
}
}
}
forwarding-options {
satellite {
fpc 100 {
sd-vlan-switching {
routing-instance vs-1;
}
}
}
}
}
Starting in Junos OS Release 18.4R1, Junos Fusion Provider Edge supports Broadband
Edge Subscriber Management. The aggregation device in Junos Fusion functions as
Broadband Network Gateway (BNG) while the extended ports on the satellite devices
function as ports on the BNG. From the standpoint of a broadband network, the extended
ports appear to be local physical ports and follow the Junos Fusion naming convention
for port interfaces. The Satellite device is identified with a Flexible PIC Concentrator
(FPC) ID and the extended ports use the FPC ID as part of the interface name.
CORE / INTERNET
Aggregation Device
Satellite Devices
SD1 SD2 SD190
FPC 65 FPC 66 FPC 254
Subscribers
Cascade Ports
g300095
Uplink Ports
Extended Ports
NOTE:
BNG on Junos Fusion Provider Edge is supported only with a MX240, MX480,
MX960, MX2010, MX2020, or MX10003 Universal Routing Platform as an
aggregation device with EX4300, QFX5100, QFX5110, or QFX5200 switches
as satellite devices.
• Non-Fusion broadband subscribers are also supported on the aggregation device. This
means that the customer premise equipment can connect directly to the MX router.
• Lawful-intercept.
• Support for satellite Devices with only a single connection to a cascade port on
aggregation device.
• The line rate of the cascade port limits the number of extended ports that can be
provisioned. To prevent oversubscription on a Junos Fusion, we recommend that you
do not provision the sum of the bandwidth for the ports on the satellite device to exceed
the bandwidth of the cascade port.
Related • Understanding CoS on an MX Series Aggregation Device in Junos Fusion Provider Edge
Documentation on page 685
This topic provides the instructions needed to configure a Junos Fusion Provider Edge.
The instructions in this topic can also be used to add a new satellite device to a Junos
Fusion Provider Edge after initial installation. It covers:
This section does not discuss the cascade port, FPC slot identification, or the software
upgrade group configuration, which are important elements of preparing your aggregation
device for a Junos Fusion Provider Edge installation and are discussed in “Configuring the
Cascade Ports on the Aggregation Device” on page 43, “Configuring the FPC Slot
Identifiers” on page 43, and “Configuring Software Upgrade Groups on the Aggregation
Device” on page 45. The instructions for adding satellite devices to the Junos Fusion
Provider Edge are also provided later in this topic.
[edit]
user@aggregation-device# set chassis network-services enhanced-ip
[edit]
user@aggregation-device# set chassis satellite-management single-home satellite all
NOTE: Configuring the Junos Fusion into single home mode using this step
is optional when the aggregation device is running Junos OS Release 14.2R5
or later.
Configuring the Junos Fusion into single home mode is required when the
aggregation device is running Junos OS Release 14.2R3 or 14.2R4.
[edit]
user@aggregation-device# commit synchronize
[edit]
user@aggregation-device# commit
Reboot the other Routing Engine at a later time to ensure it is ready to manage the
Junos Fusion in the event of a Routing Engine switchover.
A cascade port must be configured before a satellite device is recognized by the Junos
Fusion Provider Edge. Cascade port configuration, therefore, is always a required step
for configuring a Junos Fusion Provider Edge.
2. Configure the interface on the aggregation device side of the link into a cascade port:
[edit]
user@aggregation-device# set interfaces interface-name cascade-port
For example, to configure interface xe-0/0/1 on the aggregation device into a cascade
port:
[edit]
user@aggregation-device# set interfaces xe-0/0/1 cascade-port
[edit]
user@aggregation-device# commit
[edit]
user@aggregation-device# commit synchronize
FPC ID— uses ge-101/0/2 as it’s interface name. The range for the FPC ID is 100 -255 in
Junos OS Release 14.2 and 65 to 254 in Junos OS Release 16.1 and later.
A Junos Fusion Provider Edge provides two methods of assigning an FPC identifier:
Unique-ID based FPC identification and connectivity-based FPC identification. Unique-ID
based FPC identification maps an FPC slot ID to a satellite device’s MAC address or serial
number, while Unique-ID based FPC identification maps an FPC slot ID to a cascade port.
Both options are discussed in “Understanding Junos Fusion Provider Edge Components”
on page 5.
[edit]
user@aggregation-device# set chassis satellite-management fpc slot-id cascade-ports
interface-name
where slot-id becomes the FPC slot ID of the satellite device, and interface-name is
the name of the interface.
For example, to configure the FPC slot ID of the satellite device that is connected to
xe-0/0/1 to 101:
[edit]
user@aggregation-device# set chassis satellite-management fpc 101 cascade-ports xe-0/0/1
• To configure the FPC slot ID using unique-ID based FPC identification, use one of the
following options:
[edit]
user@aggregation-device# set chassis satellite-management fpc slot-id serial-number
serial-number
where slot-id becomes the FPC slot ID of the satellite device and serial-number is
the satellite device’s serial number. The FPC slot ID functions as the FPC slot identifier.
For instance, to map FPC slot ID 101 to the satellite device using the serial number
ABCDEFGHIJKL:
[edit]
user@aggregation-device# set chassis satellite-management fpc 101 serial-number
ABCDEFGHIJKL
[edit]
user@aggregation-device# set chassis satellite-management fpc slot-id system-id
mac-address
where slot-id becomes the FPC slot ID of the satellite device and mac-address is the
satellite device’s MAC address. The FPC slot ID functions as the FPC slot identifier.
For example, to map FPC slot ID to the satellite device using MAC address
12:34:56:AB:CD:EF:
[edit]
user@aggregation-device# set chassis satellite-management fpc 110 system-id
12:34:56:AB:CD:EF
When a satellite device is added to a Junos Fusion, the aggregation device checks if the
satellite device is using an FPC ID that is included in a satellite software upgrade group.
If the device is connected to a satellite device that is using an FPC ID that is part of a
satellite software upgrade group, the device—unless it is already running the same version
of satellite software—upgrades its satellite software using the satellite software
associated with the satellite software upgrade group.
When the satellite software package associated with an existing satellite software group
is changed, the satellite software for all member satellite devices is upgraded using a
throttled upgrade. The throttled upgrade ensures that only a few satellite devices are
updated at a time to minimize the effects of a traffic disruption due to too many satellite
devices upgrading software simultaneously.
The two most common methods of installing satellite software onto an aggregation
device—autoconverting a device into a satellite device when it is cabled into an
aggregation device and manually converting a device that is cabled into an aggregation
device into a satellite device—require that a satellite software upgrade group is configured.
Software upgrade groups are configured and managed from the aggregation device.
2. Create the software upgrade group, and add the satellite devices to the group.
[edit]
user@aggregation-device# set chassis satellite-management upgrade-groups
upgrade-group-name satellite slot-id-number-or-range
group name as the upgrade-group-name, you add new satellite devices to the existing
software upgrade group.
For example, to create a software upgrade group named group1 that includes all
satellite devices numbered 101 through 120:
[edit]
user@aggregation-device# set chassis satellite-management upgrade-groups group1
satellite 101-120
[edit]
user@aggregation-device# commit synchronize
If you are using an aggregation device with a single Routing Engine or want to commit
the configuration to a single Routing Engine only:
[edit]
user@aggregation-device# commit
Associating a satellite software image to a new satellite software package can trigger
a satellite software upgrade. A throttled satellite software upgrade might begin after
entering the request system software add command to associate a satellite software
package with a satellite software upgrade group. A satellite software upgrade might
also be triggered when a configuration that uses the satellite software upgrade group
is committed.
These instructions assume your device is already running Junos OS Release 14.1X53-D16
or later.
[edit]
user@satellite-device# request system zeroize
NOTE: The device reboots to complete the procedure for zeroizing the
device.
If you are not logged in to the device using the console port connection, your connection
to the device is lost after entering the request system zeroize command.
If you lose your connection to the device, login using the console port.
3. (EX4300 switches only) After the reboot is complete, convert the built-in 40-Gbps
QSFP+ interfaces from Virtual Chassis ports (VCPs) into network ports:
For example, to convert all four built-in 40-Gbps QSFP+ interfaces on an EX4300-24P
switch into network ports:
This step is required for the 40-Gbps QSFP+ interfaces that will be used as uplink
interfaces in a Junos Fusion.
This step is needed because the built-in 40-Gbps QSFP+ interfaces on EX4300
switches are configured into VCPs by default, and the default settings are restored
after the device is zeroized.
The number of built-in 40-Gbps QSFP+ interfaces varies by EX4300 switch model.
See EX4300 Switches Hardware Overview.
A switch must be running the satellite software to operate as a satellite device. The
instructions in this procedure include the required steps to install the satellite software
onto your satellite device.
You can add satellite devices to your Junos Fusion Provider Edge using one of the following
procedures:
Use this procedure to automatically configure a switch into a satellite device when it is
cabled into the aggregation device.
You can use the autoconversion procedure to add one or more satellite devices to your
Junos Fusion topology. The autoconversion procedure is especially useful when you are
adding multiple satellite devices to your Junos Fusion, because it allows you to easily
configure the entire topology before or after cabling the satellite devices to the aggregation
devices.
• Ensure that your aggregation device is running Junos OS Release 14.2R3 or later, and
that the satellite devices are running Junos OS Release 14.1X53-D16 or later.
• Ensure that you have prepared your satellite device for the installation, following the
instructions in “Preparing the Satellite Device” on page 47.
1. Cable a link between the aggregation device and the satellite device, if desired.
NOTE: You can cable the aggregation device to the satellite device at any
point in this procedure.
When the aggregation device is cabled to the satellite device during this
procedure, the process for converting a switch into a satellite device to
finalize this process occurs immediately.
If the aggregation device is not cabled to the satellite device, the process
for converting a switch into a satellite device to finalize this process starts
when the satellite device is cabled to the aggregation device.
3. Configure the cascade ports. See “Configuring the Cascade Ports on the Aggregation
Device” on page 43.
For example, to configure interface xe-0/0/1 on the aggregation device into a cascade
port:
[edit]
user@aggregation-device# set interfaces xe-0/0/1 cascade-port
There are multiple methods of assigning FPC slot IDs. See “Configuring the FPC Slot
Identifiers” on page 43.
Examples:
• To configure the FPC slot ID of the satellite device that is connected to xe-0/0/1 to
101:
[edit]
user@aggregation-device# set chassis satellite-management fpc 101 cascade-ports
xe-0/0/1
• To map FPC slot ID 101 to the satellite device using the serial number ABCDEFGHIJKL:
[edit]
user@aggregation-device# set chassis satellite-management fpc 101 serial-number
ABCDEFGHIJKL
• To map FPC slot ID to the satellite device using MAC address 12:34:56:AB:CD:EF:
[edit]
user@aggregation-device# set chassis satellite-management fpc 110 system-id
12:34:56:AB:CD:EF
[edit]
user@aggregation-device# set chassis satellite-management fpc slot-id alias alias-name
where slot-id is the FPC slot ID of the satellite device defined in the previous step, and
alias-name is the alias.
[edit]
user@aggregation-device# set chassis satellite-management fpc 101 alias qfx5100-48s-1
6. Configure an FPC slot ID into a software upgrade group. See “Configuring Software
Upgrade Groups on the Aggregation Device” on page 45.
For example, to add the satellite device using FPC slot ID 101 to an existing software
group named group1, or create a software upgrade group named group1 and add the
satellite device using FPC slot 101 to the software upgrade group:
[edit]
user@aggregation-device# set chassis satellite-management upgrade-group group1 satellite
101
If you are creating a new software upgrade group in this step, you also need to associate
the group with a satellite software image. You can skip this final step if the software
upgrade group has already been created and a satellite software package association
exists.
The configuration with the satellite software upgrade group must be committed
before a satellite software image is associated with a satellite software upgrade
group:
[edit]
user@aggregation-device# commit synchronize
[edit]
user@aggregation-device# set chassis satellite-management auto-satellite-conversion
satellite slot-id
[edit]
user@aggregation-device# set chassis satellite-management auto-satellite-conversion
satellite 101
[edit]
user@aggregation-device# commit
[edit]
user@aggregation-device# commit synchronize
The satellite software upgrade on the satellite device begins after this final step is
completed, or after you cable the satellite device to a cascade port using automatic
satellite conversion if you have not already cabled the satellite device to the
aggregation device.
After the satellite software update, the switch operates as a satellite device in the
Junos Fusion.
Use this procedure to manually convert a switch into a satellite device after cabling it
into the Junos Fusion Provider Edge.
This procedure should be used to convert a switch that is not currently acting as a satellite
device into a satellite device. A switch might not be recognized as a satellite device for
several reasons, including that the device was not previously autoconverted into a satellite
device or that the switch had previously been reverted from a satellite device to a
standalone switch.
• Ensure that your aggregation device is running Junos OS Release 14.2R3 or later, and
that the switches that will become satellite devices are running Junos OS Release
14.1X53-D16 or later.
• Ensure that you have prepared your switches that will become satellite devices for the
installation, following the instructions in the “Preparing the Satellite Device” on page 47
section.
1. Cable a link between the aggregation device and the satellite device.
3. Configure the link on the aggregation device into a cascade port, if you have not done
so already. See “Configuring the Cascade Ports on the Aggregation Device” on page 43.
For example, to configure interface xe-0/0/1 on the aggregation device into a cascade
port:
[edit]
user@aggregation-device# set interfaces xe-0/0/1 cascade-port
There are multiple methods of assigning FPC slot IDs. See “Configuring the FPC Slot
Identifiers” on page 43.
Examples:
• To configure the FPC slot ID of the satellite device that is connected to xe-0/0/1 to
101:
[edit]
user@aggregation-device# set chassis satellite-management fpc 101 cascade-ports
xe-0/0/1
• To map FPC slot ID 101 to the satellite device using the serial number ABCDEFGHIJKL:
[edit]
• To map FPC slot ID to the satellite device using MAC address 12:34:56:AB:CD:EF:
[edit]
user@aggregation-device# set chassis satellite-management fpc 110 system-id
12:34:56:AB:CD:EF
5. Configure the interface on the aggregation device into a software upgrade group. See
“Configuring Software Upgrade Groups on the Aggregation Device” on page 45.
For example, to add the satellite device using FPC slot ID 101 to an existing software
group named group1, or create a software upgrade group named group1 and add the
satellite device using FPC slot 101 to the software upgrade group:
[edit]
user@aggregation-device# set chassis satellite-management upgrade-group group1 satellite
101
If you are creating a new software upgrade group in this step, you also need to associate
the group with a satellite software image. You can skip this final step if the software
upgrade group has already been created and a satellite software package association
exists.
The configuration with the satellite software upgrade group must be committed
before a satellite software image is associated with the satellite software upgrade
group:
[edit]
user@aggregation-device# commit synchronize
[edit]
user@aggregation-device# commit
[edit]
user@aggregation-device# commit synchronize
For example, to manually configure the switch that is connecting the satellite device
to interface xe-0/0/1 on the aggregation device into a satellite device:
The satellite software upgrade on the satellite device begins after this final step is
completed.
After the satellite software update, the switch operates as a satellite device in the
Junos Fusion Provider Edge.
Use this procedure to install the satellite software onto a switch before interconnecting
it into the Junos Fusion Provider Edge as a satellite device. Installing the satellite software
on a switch before interconnecting it into the Junos Fusion Provider Edge allows you to
more immediately deploy the switch as a satellite device by avoiding the downtime
associated with the satellite software installation procedure in the Junos Fusion Provider
Edge.
• Ensure that your switch that will become a satellite device is running Junos OS Release
14.1X53-D16 or later. See Installing Software Packages on QFX Series Devices for
information on upgrading Junos OS on your device.
• Ensure that you have copied the satellite software onto the device that will become
a satellite device.
You can manually install the satellite software onto a switch by entering the following
command:
After the satellite software is installed, follow this procedure to connect the switch into
the Junos Fusion Provider Edge:
2. Configure the link on the aggregation device into a cascade port, if you have not done
so already. See “Configuring the Cascade Ports on the Aggregation Device” on page 43.
For example, to configure interface xe-0/0/1 on the aggregation device into a cascade
port:
[edit]
user@aggregation-device# set interfaces xe-0/0/1 cascade-port
There are multiple methods of assigning FPC slot IDs. See “Configuring the FPC Slot
Identifiers” on page 43.
Examples:
• To configure the FPC slot ID of the satellite device that is connected to xe-0/0/1 to
101:
[edit]
user@aggregation-device# set chassis satellite-management fpc 101 cascade-ports
xe-0/0/1
• To map FPC slot ID 101 to the satellite device using the serial number ABCDEFGHIJKL:
[edit]
user@aggregation-device# set chassis satellite-management fpc 101 serial-number
ABCDEFGHIJKL
• To map FPC slot ID to the satellite device using MAC address 12:34:56:AB:CD:EF:
[edit]
user@aggregation-device# set chassis satellite-management fpc 110 system-id
12:34:56:AB:CD:EF
4. Configure the satellite switch into a satellite software upgrade group that is using the
same version of satellite software that was manually installed onto the switch. See
“Configuring Software Upgrade Groups on the Aggregation Device” on page 45.
This step is advisable, but not always required. Completing this step ensures that the
satellite software on your device is not upgraded to the version of satellite software
associated with the satellite software upgrade group upon installation.
[edit]
user@aggregation-device# commit synchronize
[edit]
user@aggregation-device# commit
6. Cable a link between the aggregation device and the satellite device.
Related • Verifying Connectivity, Device States, Satellite Software Versions, and Operations in
Documentation a Junos Fusion on page 89
This topic shows how to configure the alarm levels for link-down events on a satellite
device in a Junos Fusion.
[edit]
user@aggregation-device# set policy-options satellite-policies
environment-monitoring-policy policy-name
[edit]
user@aggregation-device# set policy-options satellite-policies
environment-monitoring-policy linkdown-alarm-monitoring-1
3. Configure the link-down alarm behavior for the Junos Fusion using one or both of the
following methods:
• Set the default link-down alarm to one setting whenever it is experienced in a Junos
Fusion:
• Set the link-down alarm behavior for a specific satellite device hardware model
using terms:
where term-name is the user-defined name of the term, and model-name defines
the product model of the satellite device that uses the satellite policy.
You can apply environment monitoring satellite policies individually or globally. You
can, therefore, create multiple policies using the instructions in this step and apply
them to different satellite devices in your Junos Fusion, when needed.
You can use multiple terms in the same environment monitoring satellite policy.
For example, if you wanted to configure EX4300 switches acting as satellite devices
to send yellow alarms when link-down errors occur while QFX5100 switches acting
as satellite devices send red alarms for the same condition:
4. Associate the environment monitoring satellite policy with a Junos Fusion configuration.
• To associate an environment monitoring satellite policy for select FPC IDs in a Junos
Fusion:
You can configure a different environment monitoring policy for a single satellite device
using the fpc slot-id when an environment monitoring policy for all satellite devices
is configured. The environment monitoring policy for the FPC is enabled in cases when
both an individual and global environment monitoring policy are configured.
[edit]
user@aggregation-device# commit synchronize
If you want to commit the configuration to the active Routing Engine only:
[edit]
user@aggregation-device# commit
Release Information Statement introduced in Junos OS Release 14.2R3 for Junos Fusion Provider Edge.
Statement introduced in Junos OS Release 17.2R1 for Junos Fusion Data Center.
Description Configure the aging timer on the aggregation device in a Junos Fusion.
The aging timer is used on the aggregation device to specify the amount of time, in
minutes, to maintain the device state of an unreachable satellite device before deleting
the satellite device from the Junos Fusion.
If the unreachable satellite device is discovered before the aging timer expires, the satellite
device is reactivated in the Junos Fusion without having to restore its device state.
Syntax alarm {
linkdown [ignore | red | yellow]
}
Release Information Statement introduced in Junos OS Release 14.2R3 for Junos Fusion Provider Edge.
Statement introduced in Junos OS Release 16.1R1 for Junos Fusion Enterprise.
Statement introduced in Junos OS Release 17.2R1 for Junos Fusion Data Center.
Description Configure the link down alarm that is sent within the Junos Fusion whenever a satellite
device experiences a link-down error.
Default Link-down alarms are not sent on satellite devices in a Junos Fusion until an environment
monitoring policy is configured.
Related • Configuring Satellite Device Alarm Handling Using an Environment Monitoring Satellite
Documentation Policy in a Junos Fusion on page 56
Release Information Statement introduced in Junos OS Release 14.2R3 for Junos Fusion Provider Edge.
Statement introduced in Junos OS Release 16.1R1 for Junos Fusion Enterprise.
Statement introduced in Junos OS Release 17.2R1 for Junos Fusion Data Center.
Syntax auto-satellite-conversion {
satellite [slot-id | range | all];
}
Release Information Statement introduced in Junos OS Release 14.2R3 for Junos Fusion Provider Edge.
Statement introduced in Junos OS Release 16.1R1 for Junos Fusion Enterprise.
Statement introduced in Junos OS Release 17.2R1 for Junos Fusion Data Center.
Additional configuration steps are required to add satellite devices to a Junos Fusion
using automatic satellite conversion. See “Configuring Junos Fusion Provider Edge” on
page 41 or Configuring or Expanding a Junos Fusion Enterprise.
cascade-port
Syntax cascade-port;
Release Information Statement introduced in Junos OS Release 14.2R3 for Junos Fusion Provider Edge.
Statement introduced in Junos OS Release 16.1R1 for Junos Fusion Enterprise.
Statement introduced in Junos OS Release 17.2R1 for Junos Fusion Data Center.
Description Configure the specified interface on the aggregation device in a Junos Fusion into a
cascade port.
cascade-ports
Release Information Statement introduced in Junos OS Release 14.2R3 for Junos Fusion Provider Edge.
Statement introduced in Junos OS Release 16.1R1 for Junos Fusion Enterprise.
Statement introduced in Junos OS Release 17.2R1 for Junos Fusion Data Center.
Description Associate a cascade port with an FPC slot ID number in a Junos Fusion.
The FPC slot ID of the satellite device is determined by the value entered as the FPC
slot-id. For instance, if the set chassis satellite-management fpc 105 cascade-ports
xe-0/0/1 statement is used to configure interface xe-0/0/1 into a cascade port, the
satellite device that connects to interface xe-0/0/1 has an FPC slot ID of 105 in the Junos
Fusion.
A Junos Fusion provides two methods of assigning an FPC identifier: Unique ID-based
FPC identification and connectivity-based FPC identification. Unique ID-based FPC
identification maps an FPC slot ID to a satellite device’s MAC address or serial number,
while connectivity-based FPC identification maps an FPC slot ID to a cascade port. This
statement is used to assign an FPC ID using connectivity-based FPC identification by
mapping an FPC slot ID to a cascade port.
In a Junos Fusion, each satellite device must be mapped to an FPC identifier (FPC ID).
The FPC ID is used for Junos Fusion configuration, monitoring, and maintenance. Interface
names—which are identified using the type-fpc / pic / port format—use the FPC ID as the
fpc variable when the satellite device is participating in a Junos Fusion. For instance,
built-in port 2—a Gigabit Ethernet interface on a satellite device that is using 101 as it’s
FPC ID— uses ge-101/0/2 as its interface name.
For additional information on the role of FPC slot IDs in a Junos Fusion, see “Understanding
Junos Fusion Provider Edge Components” on page 5 or Understanding Junos Fusion
Enterprise Components.
Default No FPC slot IDs are associated with satellite devices, by default.
Release Information Statement introduced in Junos OS Release 14.2R3 for Junos Fusion Provider Edge.
Statement introduced in Junos OS Release 16.1R1 for Junos Fusion Enterprise.
Statement introduced in Junos OS Release 17.2R1 for Junos Fusion Data Center.
environment-monitoring-policy (satellite-management)
Release Information Statement introduced in Junos OS Release 14.2R3 for Junos Fusion Provider Edge.
Statement introduced in Junos OS Release 16.1R1 for Junos Fusion Enterprise.
Statement introduced in Junos OS Release 17.2R1 for Junos Fusion Data Center.
You configure environment monitoring policies for a Junos Fusion in the [edit policy-options
environment-monitoring-policy policy-name] hierarchy.
You can configure an environment monitoring policy in a Junos Fusion for a single satellite
device using the fpc slot-id option, or for all satellite devices in the Junos Fusion by not
specifying the fpc slot-id option.
You can configure a different environment monitoring policy for a single satellite device
using the fpc slot-id when an environment monitoring policy for all satellite devices is
configured. The environment monitoring policy for the FPC is enabled in cases when both
an individual and global environment monitoring policy are configured.
Default No environment monitoring policies for the Junos Fusion are present.
If you enable an environment monitoring policy in a Junos Fusion without specifying the
fpc slot-id option, the environment monitoring policy is applied for all satellite devices
in the Junos Fusion.
Related • Configuring Satellite Device Alarm Handling Using an Environment Monitoring Satellite
Documentation Policy in a Junos Fusion on page 56
environment-monitoring-policy (satellite-policies)
Release Information Statement introduced in Junos OS Release 14.2R3 for Junos Fusion Provider Edge.
Statement introduced in Junos OS Release 16.1R1 for Junos Fusion Enterprise.
Statement introduced in Junos OS Release 17.2R1 for Junos Fusion Data Center.
Description Configure an environment monitoring satellite policy for a device or devices in a Junos
Fusion.
Related • Configuring Satellite Device Alarm Handling Using an Environment Monitoring Satellite
Documentation Policy in a Junos Fusion on page 56
Release Information Statement introduced in Junos OS Release 14.2R3 for Junos Fusion Provider Edge.
Statement introduced in Junos OS Release 16.1R1 for Junos Fusion Enterprise.
Statement introduced in Junos OS Release 17.2R1 for Junos Fusion Data Center.
local-switching and selective-vlan-switching introduced in Junos OS Release 17.2R1 for
Junos Fusion Provider Edge.
Description Configure an FPC identifier for a satellite device within a Junos Fusion, or modify the
configuration of an existing satellite device in a Junos Fusion.
Options slot-id—Specifies the FPC identifier of the device and functions as the FPC identifier in
the interface name when configuring satellite device interfaces.
In a Junos Fusion Data Center, the slot-id must have a value in the range of 65 to
254.
In a Junos Fusion Enterprise or Junos Fusion Provider Edge, the slot-id must have a
value of 34 or greater.
local switching—Enables local-switching for all the ports on the satellite device.
Release Information Statement introduced in Junos OS Release 14.2R3 for Junos Fusion Provider Edge.
Statement introduced in Junos OS Release 16.1R1 for Junos Fusion Enterprise.
Statement introduced in Junos OS Release 17.2R1 for Junos Fusion Data Center.
Description Configure the alarm behavior when an Ethernet link goes down on a satellite device in a
Junos Fusion.
The configured alarm behavior can be applied to any satellite device in the Junos Fusion.
The alarm behavior is applied to satellite devices using environment monitoring policies.
Options ignore—Do not signal an alarm when an Ethernet link-down event occurs.
Related • Configuring Satellite Device Alarm Handling Using an Environment Monitoring Satellite
Documentation Policy in a Junos Fusion on page 56
network-services
Description Set the router’s network services to a specific mode of operation. On MX240, MX480,
and MX960 routers, MPC5E and MPC7E power on only if the network services mode
configured is enhanced-ip or enhanced-ethernet.
MX2010 and MX2020 support only enhanced-ip and enhanced-ethernet network services
modes.
Options ethernet—Set the router’s network services to Ethernet and use standard, compiled
firewall filter format.
ip—Set the router’s network services to Internet Protocol and use standard, compiled
firewall filter format.
enhanced-ip—Set the router’s network services to enhanced Internet Protocol and use
enhanced mode capabilities. Only MPCs and MS-DPCs are powered on in the chassis.
Non-service DPCs do not work with enhanced network services mode options. This
feature is enabled by default on MX80, MX104, MX2010, and MX2020 Universal
Routing Platforms.
lan—Set the router’s network services to LAN and use standard, compiled firewall filter
format. Reboot the system after setting the router’s network services to LAN.
• Limiting the Maximum Number of Logical Interfaces on MX Series Routers With MS-DPCs
in Enhanced IP Network Services Mode
Release Information Statement introduced in Junos OS Release 14.2R3 for Junos Fusion Provider Edge.
Statement introduced in Junos OS Release 16.1R1 for Junos Fusion Enterprise.
Statement introduced in Junos OS Release 17.2R1 for Junos Fusion Data Center.
Description Specify the interface to enable automatic software conversion in a Junos Fusion.
The device that is cabled to the slot specified in this command is automatically converted
into a satellite device.
Additional configuration steps are required to add satellite devices to a Junos Fusion
using automatic satellite conversion. See Configuring or Expanding a Junos Fusion Enterprise
or “Configuring Junos Fusion Provider Edge” on page 41.
Options slot-id—Specifies the FPC slot identifier of the device that will be automatically converted
into a satellite device.
The FPC identifier must be mapped to a cascade port interface before this command
is operational. See Configuring or Expanding a Junos Fusion Enterprise or “Configuring
Junos Fusion Provider Edge” on page 41.
range—Specifies a range of FPC slot identifiers that will automatically be converted into
satellite devices. For instance, to specify that FPC IDs 103, 104, and 105 should be
automatically converted into satellite devices, enter a range of 103-105.
all—Specifies that all FPC slot identifiers in the Junos Fusion will automatically be
converted into satellite devices.
Release Information Statement introduced in Junos OS Release 14.2R3 for Junos Fusion Provider Edge.
Statement introduced in Junos OS Release 16.1R1 for Junos Fusion Enterprise.
Statement introduced in Junos OS Release 17.2R1 for Junos Fusion Data Center.
Description Specify the satellite device to add to the satellite software upgrade group.
Options slot-id—Specifies the FPC slot identification number of the satellite device that is being
added to the satellite software upgrade group.
range—Specifies a range of FPC slot identifiers to add to the satellite software upgrade
group. For instance, to specify that FPC IDs 103, 104, and 105 should be automatically
converted into satellite devices, enter a range of 103-105.
all—Specifies that all FPC slot identifiers in the Junos Fusion are added to the satellite
software upgrade group.
Syntax satellite-management {
aging-timer aging-timer;
auto-satellite-conversion {
satellite [slot-id | range | all];
}
cluster cluster-name{
cascade-ports interface-name;
cluster-id cluster-id-number;
fpc slot-id{
alias alias;
description description;
member-id member-id-number;
system-id mac-address;
}
}
designated-event-forwarding
environment-monitoring-policy policy;
firewall
family family-name {
filter filter-name {
term term-name {
from {
match-conditions;
}
then {
action;
action-modifiers;
}
}
}
}
fpc slot-id{
alias alias;
cascade-ports interface-name;
description description;
environment-monitoring-policy policy;
serial-numberserial-number;
system-id mac-address;
uplink-failure-detection {
candidate-uplink-policy policy;
}
}
psu {
redundancy {
n-plus-n;
}
}
redundancy-groups {
chassis-id number;
redundancy-group-name {
redundancy-group-id redundancy-group-id-number;
peer-chassis-id peer-chassis-id-number {
inter-chassis-link interface-name;
no-auto-iccp-provisioning;
no-auto-vlan-provisioning;
satellite satellite-device-fpc-IDs;
}
}
}
single-home {
satellite [slot-id |slot-id-range | all];
}
upgrade-groups upgrade-group-name {
satellite [slot-id | range | all];
}
uplink-failure-detection {
candidate-uplink-policy policy;
}
}
Release Information Statement introduced in Junos OS Release 14.2R3 for Junos Fusion Provider Edge.
Statement introduced in Junos OS Release 16.1R1 for Junos Fusion Enterprise.
Statement introduced in Junos OS Release 17.2R1 for Junos Fusion Data Center.
If you enter the delete chassis satellite-management command to delete a Junos Fusion
configuration, we recommend also rebooting the Routing Engines on your device to
maximize device performance.
Release Information Statement introduced in Junos OS Release 14.2R3 for Junos Fusion Provider Edge.
Statement introdcued in Junos OS Release 16.1R1 for Junos Fusion Enterprise.
Statement introdcued in Junos OS Release 17.2R1 for Junos Fusion Data Center.
Description Bind the specified FPC slot ID to a satellite device based on the serial number.
A Junos Fusion provides two methods of assigning an FPC identifier: Unique ID-based
FPC identification and connectivity-based FPC identification. Unique ID-based FPC
identification maps an FPC slot ID to a satellite device’s MAC address or serial number,
while unique ID-based FPC identification maps an FPC slot ID to a cascade port. This
statement is used to assign an FPC ID using unique ID-based FPC identification by mapping
the FPC slot ID to the satellite device’s serial number.
In a Junos Fusion, each satellite device must be mapped to an FPC identifier (FPC ID).
The FPC ID is used for Junos Fusion configuration, monitoring, and maintenance. Interface
names—which are identified using the type-fpc / pic / port format—use the FPC ID as the
fpc variable when the satellite device is participating in a Junos Fusion. For instance,
built-in port 2—a Gigabit Ethernet interface on a satellite device that is using 101 as its
FPC ID—uses ge-101/0/2 as its interface name.
For additional information on the role of FPC slot IDs in a Junos Fusion, see Understanding
Junos Fusion Enterprise Components or “Understanding Junos Fusion Provider Edge
Components” on page 5.
If the serial number that is configured using this statement does not match the serial
number of the satellite device, the device is not converted into a satellite device.
Default No FPC slot IDs are associated with satellite devices, by default.
selective-vlan-switching
Syntax selective-vlan-switching {
routing-instance routing-instance;
}
Release Information Statement introduced in Junos OS Release 17.2R1 for Junos Fusion Provider Edge..
Description Enables local switching for only a select number of VLANs on the satellite device.
Syntax single-home {
satellite [slot-id |slot-id-range | all];
}
Release Information Statement introduced in Junos OS Release 14.2R3 for Junos Fusion Provider Edge.
Statement introdcued in Junos OS Release 16.1R1 for Junos Fusion Enterprise.
Statement introdcued in Junos OS Release 17.2R1 for Junos Fusion Data Center.
Description Specify that the links connecting the satellite device to the aggregation device are
connected to the aggregation device only.
Release Information Statement introduced in Junos OS Release 14.2R3 for Junos Fusion Provider Edge.
Statement introdcued in Junos OS Release 16.1R1 for Junos Fusion Enterprise.
Statement introdcued in Junos OS Release 17.2R1 for Junos Fusion Data Center.
Description Assign the specified FPC identifier to the satellite device based on the satellite device’s
MAC address.
For instance, if you wanted the satellite device using MAC address 01:02:03:AA:BB:CC
to be assigned FPC identifier 101, enter the set chassis satellite-management fpc 101
system-id 01:02:03:AA:BB:CC statement.
A Junos Fusion provides two methods of assigning an FPC identifier: Unique ID-based
FPC identification and connectivity-based FPC identification. Unique ID-based FPC
identification maps an FPC slot ID to a satellite device’s MAC address or serial number,
while connectivity-based FPC identification maps an FPC slot ID to a cascade port. This
statement is used to assign an FPC ID using unique ID-based FPC identification by mapping
the FPC slot ID to the satellite device’s MAC address.
In a Junos Fusion, each satellite device must be mapped to an FPC identifier (FPC ID).
The FPC ID is used for Junos Fusion configuration, monitoring, and maintenance. Interface
names—which are identified using the type-fpc / pic / port format—use the FPC ID as the
fpc variable when the satellite device is participating in a Junos Fusion. For instance,
built-in port 2—a gigabit Ethernet interface on a satellite device that is using 101 as its
FPC ID— uses ge-101/0/2 as its interface name.
For additional information on the role of FPC slot IDs in a Junos Fusion, see “Understanding
Junos Fusion Provider Edge Components” on page 5 or Understanding Junos Fusion
Enterprise Components.
If the serial number that is configured using this statement does not match the serial
number of the satellite device, the device is not converted into a satellite device.
If the MAC address that is configured using this statement does not match the MAC
address of the satellite device, the device is not converted into a satellite device.
Default No FPC slot IDs are associated with satellite devices, by default.
term (satellite-policies)
Release Information Statement introduced in Junos OS Release 14.2R3 for Junos Fusion Provider Edge.
Statement introduced in Junos OS Release 16.1R1 for Junos Fusion Enterprise.
Statement introduced in Junos OS Release 17.2R1 for Junos Fusion Data Center.
Description Create and configure a term in a candidate uplink satellite policy, an environment
monitoring satellite policy, or a forwarding policy satellite policy, within a satellite policy.
A term is a named structure in which match conditions and actions are defined. A
candidate uplink policy or environment monitoring policy can contain multiple terms.
The term name can contain letters, numbers, and hyphens (-) and can be up to 255
characters long. To include spaces in the name, enclose the entire name in double
quotation marks.
The only match criteria available for a satellite policy is the product model.
If you omit the from option, the satellite policy is applied globally.
If you want the satellite policy to apply to all EX4300 switches in the satellite device
role, enter EX4300* as the model-name.
If you want the satellite policy to apply to all QFX5100 switches in the satellite device
role, enter QFX5100* as the model-name.
Related • Configuring Satellite Device Alarm Handling Using an Environment Monitoring Satellite
Documentation Policy in a Junos Fusion on page 56
• Configuring Uplink Port Pinning for Satellite Devices on a Junos Fusion Data Center
Release Information Statement introduced in Junos OS Release 14.2R3 for Junos Fusion Provider Edge.
Statement introdcued in Junos OS Release 16.1R1 for Junos Fusion Enterprise.
Statement introdcued in Junos OS Release 17.2R1 for Junos Fusion Data Center.
Description Create and name a satellite software upgrade group for a Junos Fusion, or specify an
existing satellite software upgrade group to configure.
A satellite software upgrade group is a group of satellite devices that are designated to
upgrade to the same satellite software version using the same satellite software package.
One Junos Fusion can contain multiple software upgrade groups, and multiple software
upgrade groups should be configured in most Junos Fusions to avoid network downtimes
during satellite software installations.
Software upgrade groups are configured and managed from the aggregation device.
To associate a satellite software package with a satellite software upgrade group, use
the request system software add package-name upgrade-group upgrade-group-name
command.
The software upgrade group configurations must match exactly—including the same
package-name and upgrade-group-name—in every Junos Fusion with dual aggregation
devices to avoid satellite device downtime.
All satellite devices in a satellite device cluster are associated with a single satellite
software upgrade group, which is automatically created when a satellite device cluster
becomes part of a Junos Fusion. The satellite software upgrade group is named after the
satellite device cluster name, and ensures that all satellite devices in the cluster run the
same version of satellite software. See Understanding Software in a Junos Fusion Enterprise
for additional information on software management for a satellite device cluster.
A satellite software upgrade group with the name of the satellite device cluster is created
automatically when a satellite device cluster is created.
Options upgrade-group-name—Specifies the user-defined name for the satellite software upgrade
group.
This topic discusses maintaining satellite software upgrade groups in a Junos Fusion. For
more information on the process for creating a satellite software upgrade group, see
“Configuring Junos Fusion Provider Edge” on page 41 or Configuring or Expanding a Junos
Fusion Enterprise.
A satellite software upgrade group is a group of satellite devices that are designated to
upgrade to the same satellite software version using the same satellite software package.
One Junos Fusion can contain multiple software upgrade groups, and multiple software
upgrade groups should be configured in most Junos Fusions to avoid network downtimes
during satellite software installations.
When a satellite device is added to a Junos Fusion, the aggregation device checks if the
satellite device is using an FPC ID that is included in a satellite software upgrade group.
If the satellite device is using an FPC ID that is part of a satellite software upgrade group,
the device upgrades its satellite software to the version of software associated with the
satellite software upgrade group - unless it is already running the defined version.
When the satellite software package associated with an existing satellite software group
is changed, the satellite software for all member satellite devices is upgraded using a
throttled upgrade. The throttled upgrade ensures that the aggregation device is not
overwhelmed with providing satellite software simultaneously to many satellite devices.
Software upgrade groups are configured and managed from the aggregation device. All
satellite devices in a satellite device cluster are part of the same software upgrade group,
and a software upgrade group with the name of the satellite device cluster is automatically
created when the satellite device cluster is created.
For information on creating a satellite software upgrade group for a satellite device that
is not part of a satellite device cluster, see “Configuring Junos Fusion Provider Edge” on
page 41 or Configuring or Expanding a Junos Fusion Enterprise.
[edit]
user@aggregation-device# set chassis satellite-management upgrade-groups
upgrade-group-name satellite slot-id-or-range
where upgrade-group-name is the name of the existing satellite software upgrade group,
and the slot-id-or-range is the FPC slot ID or range of FPC slot IDs of the satellite devices
that are being added to the upgrade group.
For example, to add FPC slot IDs 121, 122, and 123 to a satellite software upgrade group
named group1:
[edit]
user@aggregation-device# set chassis satellite-management upgrade-groups group1 satellite
121-123
Additionally, you can use the all statement as your slot-id-or-range to include all satellite
devices in the Junos Fusion in the satellite software upgrade group.
For example, to add all satellite devices in the Junos Fusion to a satellite software upgrade
group named group1:
[edit]
user@aggregation-device# set chassis satellite-management upgrade-groups group1 satellite
all
[edit]
user@aggregation-device# delete chassis satellite-management upgrade-groups
upgrade-group-name satellite slot-id-or-range
where upgrade-group-name is the name of the existing satellite software upgrade group,
and the slot-id-or-range is the FPC slot ID or range of FPC slot IDs of the satellite devices
that are being added to the upgrade group.
In cases where you want to remove some FPC slot IDs that were configured within a
range of FPC slot IDs, you might consider re-creating the satellite software group by first
deleting it, then re-creating it. To delete the satellite software upgrade group:
[edit]
user@aggregation-device# delete chassis satellite-management upgrade-groups
upgrade-group-name
You can then re-create the satellite software upgrade group and add satellite devices
using the set chassis satellite-management upgrade-groups upgrade-group-name satellite
slot-id-or-range statement:
[edit]
user@aggregation-device# set chassis satellite-management upgrade-groups
upgrade-group-name satellite slot-id-or-range
For more information on the satellite software upgrade group creation process, see
“Configuring Junos Fusion Provider Edge” on page 41 or Configuring or Expanding a Junos
Fusion Enterprise.
• Ensure that a satellite software package is downloaded to the location where you will
use it to install the satellite software.
To associate a satellite software package that was previously installed on the aggregation
device with a software upgrade group:
For instance:
The satellite software upgrade group is associated with the software package after either
of these commands are entered.
If the group was already associated with a satellite software upgrade group, the previous
satellite software package associated with the software group remains the second option
for updating satellite software for the satellite software upgrade group. You can
disassociate any satellite software package from a satellite software upgrade group
using the instructions in the next section.
This procedure is always optional. You can always update the satellite software
associated with a satellite software upgrade group using the procedure in the previous
section, without deleting the satellite software from the satellite software upgrade group.
When a new satellite software package is associated with a satellite software upgrade,
the previous satellite software package remains associated with the upgrade group as
a backup option. The satellite software upgrade group can be associated with up to two
satellite software packages, so no other satellite software packages can be associated
with the satellite software upgrade group.
This process disassociates the specified satellite software package from the list of
potential packages used by a satellite software upgrade group. It is useful for maintenance
purposes only, like if you wanted to ensure a satellite software upgrade group was never
associated with a specific satellite software package.
where the upgrade-group-name is the name of the upgrade group that was assigned by
the user.
For example, to delete the current satellite software image association to the upgrade
group named group1:
For example:
Purpose Verify that a device is recognized as a satellite device by the aggregation device.
Action Enter the show chassis satellite command and review the output.
Meaning Use the output of show chassis satellite to confirm the following connections in a Junos
Fusion:
• Whether a satellite device is recognized at all by the aggregation device. If the satellite
device does not appear in the show chassis satellite output, then it is not recognized
by the aggregation device as a satellite device.
• The state of a particular satellite device, via the Device State output.
• The state of the cascade port connection, via the Cascade State output.
Purpose Verify that all satellite devices are recognized by the aggregation device, and that all
cascade and extended ports are recognized.
Action Enter the show chassis satellite command on the aggregation device.
• Each listed satellite device—the satellite devices are listed by alias-name in the Alias
column or by FPC slot ID in the Slot column—is recognized by the aggregation device,
because the Device State output is Online for every listed satellite device.
• Each cascade port is operational, because Port State is online for every cascade port.
The cascade port is the port on the aggregation device that connects to the satellite
device.
• The number of available and active extended ports for each satellite device, using the
Extended Ports total and Extended Ports up outputs. The number of extended ports
varies by satellite devices, and in this output the total number of extended ports includes
both network-facing extended ports as well as uplink ports.
Purpose Verify the hardware model of each satellite device in the Junos Fusion.
Action Enter the show chassis satellite terse command on the aggregation device.
Meaning The output shows the device model of each satellite device in the Device Model output,
which are listed by FPC slot identification number using the Slot output.
This command is also useful for verifying the version satellite software running on each
satellite device, as the version is listed in the Version output.
Purpose Verify that the cascade port and uplink port interfaces are up.
lo0 Up Loopback
sd-101/0/0 Up Satellite
sd-102/0/0 Up Satellite
sd-103/0/0 Up Satellite
sd-104/0/0 Up Satellite
sd-105/0/0 Up Satellite
sd-106/0/0 Up Satellite
sd-107/0/0 Up Satellite
sd-108/0/0 Up Satellite
sd-109/0/0 Up Satellite
sd-110/0/0 Up Satellite
sd-111/0/0 Up Satellite
sd-112/0/0 Up Satellite
sd-113/0/0 Up Satellite
sd-114/0/0 Up Satellite
xe-0/0/1 Up Cascade
xe-0/0/2 Up Cascade
xe-0/0/3 Up Cascade
xe-0/0/4 Up Cascade
xe-0/0/5 Up Cascade
xe-0/0/6 Up Cascade
xe-0/0/7 Up Cascade
xe-0/0/8 Up Cascade
xe-0/0/9 Up Cascade
xe-0/2/0 Up Cascade
xe-0/2/1 Up Cascade
xe-0/2/2 Up Cascade
xe-0/2/3 Up Cascade
xe-0/2/4 Up Cascade
xe-0/2/5 Up Cascade
xe-0/2/6 Up Cascade
xe-0/2/7 Up Cascade
xe-1/0/1 Up Cascade
xe-1/0/2 Up Cascade
xe-1/0/3 Up Cascade
xe-1/2/1 Up Cascade
xe-1/2/2 Up Cascade
xe-1/2/3 Up Cascade
xe-2/0/0 Up Cascade
xe-2/0/1 Up Cascade
xe-2/0/2 Up Cascade
xe-2/0/3 Up Cascade
xe-2/0/4 Up Cascade
xe-2/0/5 Up Cascade
xe-2/0/6 Up Cascade
xe-2/0/7 Up Cascade
xe-2/1/0 Up Cascade
xe-2/1/1 Up Cascade
xe-2/1/2 Up Cascade
xe-2/1/3 Up Cascade
xe-2/1/4 Up Cascade
xe-2/1/5 Up Cascade
xe-2/1/6 Up Cascade
xe-2/1/7 Up Cascade
xe-2/2/0 Up Cascade
xe-2/2/1 Up Cascade
xe-2/2/2 Up Cascade
xe-2/2/3 Up Cascade
xe-2/2/4 Up Cascade
xe-2/2/5 Up Cascade
xe-2/2/6 Up Cascade
xe-2/2/7 Up Cascade
xe-2/3/0 Up Cascade
xe-2/3/3 Dn Cascade
xe-2/3/4 Up Cascade
xe-2/3/5 Up Cascade
xe-2/3/6 Up Cascade
xe-2/3/7 Up Cascade
• Whether the recognized port is up or down, using the State column output. The State
column output is Up when the interface is up and Dn when the interface is down.
Purpose Verify that a cascade port on an aggregation device recognizes a satellite device in the
Junos Fusion. This procedure also provides a method of verifying the hardware and
software information for each satellite device in the Junos Fusion.
• The cascade ports on the aggregation device that are recognized by the Junos Fusion.
All recognized cascade port interfaces are listed in the Interface output.
• The uplink ports on the satellite devices that are connected to the cascade ports. The
cascade port on each satellite device is identified in the Port Info column, and the
satellite device itself is identified in the System Name output.
• Whether the cascade port to uplink port connection has initialized, using the State
output. The State output is Two-Way when the satellite device is properly initialized,
and traffic can be passed between the aggregation device and the satellite device over
the link.
• The hardware model of each satellite device in the Model column, and the satellite
software running on each satellite device in the SW Version output.
Purpose Verify that a specific extended port is recognized by the aggregation device, and is
operational.
Action Enter the show chassis satellite extended-port command on the aggregation device:
• That an extended port is recognized by the aggregation device. All extended ports are
listed in the Name column of the output.
• That the listed extended ports have been added to the Junos Fusion, as shown by the
AddComplete output in the State column.
• The administrative and operational state of each extended port. An extended port is
operating correctly when the Admin State and Op State outputs are both in the Up
state.
Purpose Verify the satellite software versions available on the aggregation device in a Junos Fusion.
Action Enter the show chassis satellite software command on the aggregation device.
For more detailed output, you can also enter the show chassis satellite software detail
on the aggregation device.
Meaning The version of satellite software installed is displayed in the Version or Software package
version column, and the satellite software upgrade group associated with each version
of satellite software is listed in the Group or Current Groups output.
Verifying the Devices and Software Used in a Satellite Software Upgrade Group
Purpose Verify the satellite software upgrade groups in the Junos Fusion, and which satellite
devices are part of which satellite software upgrade groups.
A satellite software upgrade group can be a user configured group or the name of a
satellite device cluster.
Action Enter the show chassis satellite upgrade-group command on the aggregation device.
Group Device
Group Sw-Version State Slot State
__ungrouped__
group1 3.0R1.1 in-sync 107 version-in-sync
108 version-in-sync
109 version-in-sync
110 version-in-sync
111 version-in-sync
112 version-in-sync
113 version-in-sync
group2 3.0R1.1 in-sync 102 version-in-sync
103 version-in-sync
104 version-in-sync
105 version-in-sync
106 version-in-sync
114 version-in-sync
Meaning The output shows that two satellite software upgrade groups—ex4300 and qfx—have
been created, and that both are using satellite software version 1.0R1.1. The Group Slot
output shows which satellite devices—listed by FPC slot ID number—are in which software
group, and the Device State output showing version-in-sync confirms that the satellite
devices are running the satellite software that is associated with the satellite software
upgrade group.
In the event that you need to convert a satellite device to a standalone device, you will
need to download and install a new Junos OS software package on the satellite device.
The satellite device stops participating in the Junos Fusion topology once the software
installation starts.
The following steps explain how to convert a satellite device that is participating in a
Junos Fusion to a standalone device running Junos OS. If you have a standalone switch
that is not part of a Junos Fusion but is running satellite software, and you want the switch
to run Junos OS software, see “Installing Junos OS Software on a Standalone Device
Running Satellite Software” on page 105.
• If the satellite device is a QFX5110, QFX5200 or EX4300 switch, you install a standard,
signed jinstall version of Junos OS.
• If the satellite device is a QFX5100 switch that can be converted to a standalone device,
you must install a Preboot eXecution Environment (PXE) version of Junos OS. The PXE
version of Junos OS software supports the same feature set as the other Junos OS
software packages for a release, but is specially engineered to install Junos OS onto
a device running satellite software. The PXE Junos OS package name uses the format
install-media-pxe-qfx-5-version-domestic.tgz.
• For Junos Fusion systems running Junos OS Release 17.2R1 and later, if the satellite
device is a QFX5100 switch that can be converted to a standalone device, you must
install a signed PXE version of Junos OS to convert the satellite device running satellite
software to a standalone device running Junos OS software. The signed PXE Junos OS
package name uses the format install-media-pxe-qfx-5-version-domestic-signed.tgz.
To download the version of Junos OS that you want to run on the satellite device after
removing it from the Junos Fusion:
1. Using a Web browser, navigate to the Junos OS software download URL on the Juniper
Networks webpage:
https://www.juniper.net/support/downloads
2. Log in to the Juniper Networks authentication system using the username (generally
your e-mail address) and password supplied by Juniper Networks representatives.
3. Select By Technology > Junos Platform > Junos Fusion from the drop-down list and
select the switch platform series and model for your satellite device.
4. Select the version of Junos OS that you want to run on the satellite device after
removing it from the Junos Fusion.
7. Copy the software to the routing platform or to your internal software distribution
site.
[edit]
user@aggregation-device> request chassis satellite install fpc-slot 103
/var/tmp/jinstall-ex-4300-14.1X53-D43.7-domestic-signed.tgz
Convert satellite device to Junos standalone device? [yes,no] (no) yes
You can check the automatic satellite conversion configuration by entering the show
statement at the [edit chassis satellite-management auto-satellite-conversion] hierarchy
level.
1. If automatic satellite conversion is enabled for the satellite device’s FPC slot ID, remove
the FPC slot ID from the automatic satellite conversion configuration.
[edit]
For example, to remove FPC slot ID 103 from the Junos Fusion.
[edit]
user@aggregation-device# delete chassis satellite-management auto-satellite-conversion
satellite 103
[edit]
user@aggregation-device# commit
[edit]
user@aggregation-device# commit synchronize
[edit]
user@aggregation-device> request chassis satellite install fpc-slot slot-id
URL-to-software-package
For example, to install a software package stored in the var/tmp folder on the
aggregation device onto an EX4300 switch acting as the satellite device using FPC
slot 103:
[edit]
user@aggregation-device> request chassis satellite install fpc-slot 103
/var/tmp/jinstall-ex-4300-14.1X53-D43.7-domestic-signed.tgz
Convert satellite device to Junos standalone device? [yes,no] (no) yes
NOTE: If you are converting a QFX5100 switch and the Junos Fusion is
running a Junos OS release earlier than 17.2R1, you must install the unsigned
PXE software package on the QFX5100 switch:
[edit]
user@aggregation-device> request chassis satellite install fpc-slot 103
/var/tmp/install-media-pxe-qfx-5-14.1X53-D43.7-domestic.tgz
The satellite device stops participating in the Junos Fusion topology once the software
installation starts. The software upgrade starts after this command is entered.
2. To check the progress of the conversion, issue the show chassis satellite fpc-slot
command:
[edit]
user@aggregation-device> show chassis satellite fpc-slot 103 extensive
3. Wait for the reboot that accompanies the software installation to complete.
4. When you are prompted to log back into your device, uncable the device from the
Junos Fusion topology. See Removing a Transceiver. Your device has been removed
from Junos Fusion.
17.2R1 For Junos Fusion systems running Junos OS Release 17.2R1 and later, if the satellite
device is a QFX5100 switch that can be converted to a standalone device, you
must install a signed PXE version of Junos OS to convert the satellite device
running satellite software to a standalone device running Junos OS software.
This process should be used when you have a standalone switch running satellite software
and you want the switch to run Junos OS software. A standalone device is running satellite
software for one of the following reasons:
• It was removed from a Junos Fusion without following the instructions in “Converting
a Satellite Device in a Junos Fusion to a Standalone Device” on page 100, which include
a Junos OS installation.
• Satellite software was installed on the device but the device was never provisioned
into a Junos Fusion.
NOTE: If you are removing a satellite device from a Junos Fusion, you must
first make sure that automatic satellite conversion is disabled for the satellite
device’s FPC slot ID. See “Converting a Satellite Device in a Junos Fusion to
a Standalone Device” on page 100.
• Select a Junos OS image that meets the satellite software to Junos OS conversion
requirements. See Junos Fusion Hardware and Software Compatibility Matrices for
satellite software to Junos OS conversion requirements.
• Copy the Junos OS image onto a USB flash drive and use the USB flash drive to install
the Junos OS. See Performing a Recovery Installation Using an Emergency Boot Device.
3. While the switch is powering back on, enter the UBoot prompt (=>) by pressing Ctrl+C
on your keyboard.
4. From the Uboot prompt, set the operating system environment mode on the switch
to Junos. Save the configuration and reset the kernel:
After the reset operation completes, the loader prompt (loader>) appears.
5. Install Junos OS using a USB flash drive from the loader prompt. See Booting an EX
Series Switch Using a Software Package Stored on a USB Flash Drive.
• Log in to the satellite software (SNOS) on the switch to be converted back to Junos
OS and use the following sequence of commands to install the Junos package:
#######################################
dd bs=512 count=1 if=/dev/zero of=/dev/sda
echo -e "o\nn\np\n1\n\n\nw" | fdisk /dev/sda
mkfs.vfat /dev/sda1
fw_setenv target_os
reboot
##################################
>>Get to the loader prompt
##################################
loader> install --format tftp://<tftp server>/<Junos package name>
Description Manually install satellite software onto a switch before interconnecting the switch as a
satellite device into a Junos Fusion.
There are other methods of installing satellite software onto a satellite device, and each
Junos Fusion has individual requirements for manually installing satellite software. See
“Configuring Junos Fusion Provider Edge” on page 41 or Configuring or Expanding a Junos
Fusion Enterprise before manually installing satellite software.
This command is entered from a standalone device before it is configured into a satellite
device in a Junos Fusion.
List of Sample Output request chassis device-mode satellite /var/tmp/satellite-3.0R1.1-signed.tgz on page 111
Sample Output
Release Information Command introduced in Junos OS Release 14.2R3 for Junos Fusion Provider Edge.
Command introduced in Junos OS Release 16.1R1 for Junos Fusion Enterprise.
Command introduced in Junos OS Release 17.2R1 for Junos Fusion Data Center.
Description Disable the specified satellite device from the Junos Fusion.
When a satellite device is disabled from a Junos Fusion, all extended ports are immediately
placed in the down state. The satellite device cannot send or receive traffic for the Junos
Fusion until it is reenabled.
This command is useful whenever you need to disable a satellite device from a Junos
Fusion, such as for troubleshooting scenarios. If you are removing a satellite device from
a Junos Fusion to use the device elsewhere on the network, use the request chassis
satellite install command to install Junos OS onto your satellite device before removing
it from the Junos Fusion. See Removing a Satellite Device from a Junos Fusion.
You can reenable a satellite device that was disabled using this command using the
request chassis satellite enable command.
Options device-alias alias-name—Disable the satellite device with the specified alias name from
the Junos Fusion.
fpc fpc-slot—Disable the satellite device with the specified FPC slot identifier from the
Junos Fusion.
List of Sample Output request chassis satellite disable device-alias satellite-01 on page 112
request chassis satellite disable fpc-slot 101 on page 113
Sample Output
Sample Output
Release Information Command introduced in Junos OS Release 14.2R3 for Junos Fusion Provider Edge.
Command introduced in Junos OS Release 16.1R1 for Junos Fusion Enterprise.
Command introduced in Junos OS Release 17.2R1 for Junos Fusion Data Center.
This command is typically not used in any standard Junos Fusion initial configuration
procedure. This command is typically needed in cases where the satellite device or
cascade port has been disabled and needs to be re-enabled.
Options device-alias alias-name—Enable the satellite device with the specified alias name in the
Junos Fusion.
fpc fpc-slot—Enable the device with the specified FPC slot ID as a satellite device in the
Junos Fusion.
List of Sample Output request chassis satellite enable device-alias satellite-01 on page 114
request chassis satellite enable fpc-slot 101 on page 114
Sample Output
Sample Output
Release Information Command introduced in Junos OS Release 14.2R3 for Junos Fusion Provider Edge.
Command introduced in Junos OS Release 16.1R1 for Junos Fusion Enterprise.
Command introduced in Junos OS Release 17.2R1 for Junos Fusion Data Center.
Description Copy a file between a satellite device and an aggregation device in a Junos Fusion.
Options local—Indicate that the file-copy from satellite-device has been initiated by a local user.
remote—Indicate that the file-copy from satellite-device has been initiated by a remote
user.
If no device is specified as the source-URL, the file is copied from the aggregation
device.
If no device is specified as the destination-URL, the file is copied into the aggregation
device.
Sample Output
Release Information Command introduced in Junos OS Release 14.2R3 for Junos Fusion Provider Edge.
Command introduced in Junos OS Release 16.1R1 for Junos Fusion Enterprise.
Command introduced in Junos OS Release 17.2R1 for Junos Fusion Data Center.
Description Install a version of Junos OS software onto a satellite device in a Junos Fusion.
Any device operating as a satellite device in a Junos Fusion is running satellite software.
A device running satellite software cannot operate as a standalone network device until
it is running a version of Junos OS software.
You would typically enter this command to install Junos OS onto a satellite device before
removing the satellite device from a Junos Fusion. Installing the Junos OS software onto
the satellite device before removing it from the Junos Fusion allows you to more easily
install the device elsewhere in your network.
If you are using the automatic satellite conversion feature to convert devices into satellite
devices in your Junos Fusion, remove the FPC slot ID to the satellite device from the
automatic satellite conversion configuration before using this command to install the
Junos OS software. You can update the automatic satellite conversion feature using the
set chassis satellite-management auto-satellite-conversion satellite slot-id configuration
statement.
You must install a PXE version of compatible Junos OS to convert the satellite device
running satellite software to a standalone device running Junos OS software on QFX5100
switches acting as satellite devices. The PXE version of Junos OS is the software that
includes pxe in the Junos OS package name when it is downloaded from the Software
Center—for example, the PXE image for Junos OS Release 14.1X53-D16 is named
install-media-pxe-qfx-5-14.1X53-D16.2.tgz.
For Junos Fusion systems running Junos OS Release 17.2R1 and later, you must install a
signed PXE version of Junos OS to convert the satellite device running satellite software
to a standalone device running Junos OS software. The signed PXE Junos OS package
name uses the format install-media-pxe-qfx-5-version-domestic-signed.tgz.
The device uses a factory-default configuration after the Junos OS installation is complete.
No Junos OS configuration is modified and the previous Junos OS configuration is not
restored after the Junos OS software installation.
Options package-name—Specify the URL to the Junos OS image to install onto the satellite
device.
fpc fpc-slot—Install the Junos OS software onto the satellite device with the specified
FPC slot ID in the Junos Fusion.
device-alias device-alias—Install the Junos OS software onto the satellite device with
the alias name in the Junos Fusion.
Sample Output
Release Information Command introduced in Junos OS Release 14.2R3 for Junos Fusion Provider Edge.
Command introduced in Junos OS Release 16.1R1 for Junos Fusion Enterprise.
Command introduced in Junos OS Release 17.2R1 for Junos Fusion Data Center.
This command is used to change a device into a satellite device for a Junos Fusion. After
interconnecting a device to an aggregation device in a Junos Fusion, enter this command
from the aggregation device to begin the manual satellite device conversion procedure.
Other configuration steps, such as configuring the cascade port and creating a satellite
software upgrade group, must be completed before this command can be used to convert
a device into a satellite device. See “Configuring Junos Fusion Provider Edge” on page 41
or Configuring or Expanding a Junos Fusion Enterprise.
Options interface-name—Specify the name of the cascade port interface on the aggregation
device that connects to the device that will be converted into a satellite device.
List of Sample Output request chassis satellite interface xe-0/0/1 device-mode satellite on page 119
Sample Output
Release Information Command introduced in Junos OS Release 14.2R3 for Junos Fusion Provider Edge.
Command introduced in Junos OS Release 16.1R1 for Junos Fusion Enterprise.
Command introduced in Junos OS Release 17.2R1 for Junos Fusion Data Center.
This command is typically used to log in to the satellite device by expert users for
debugging purposes. You can perform all configuration and administration tasks in a
Junos Fusion from the aggregation device.
Options fpc fpc-slot—Log in to the satellite device with the specified FPC slot ID.
List of Sample Output request chassis satellite login fpc-slot 101 on page 120
Sample Output
Release Information Command introduced in Junos OS Release 14.2R3 for Junos Fusion Provider Edge.
Command introduced in Junos OS Release 16.1R1 for Junos Fusion Enterprise.
Command introduced in Junos OS Release 17.2R1 for Junos Fusion Data Center.
Description Reboot the satellite device or devices from the aggregation device in a Junos Fusion.
Options fpc fpc-slot—Reboot the satellite device with the specified FPC slot identifier.
For instance, you can reboot the satellite devices using FPC slot identifiers 101, 102,
and 103 by entering a range of 101-103.
List of Sample Output request chassis satellite reboot fpc 101 on page 121
request chassis satellite reboot range 101-103 on page 121
Sample Output
Sample Output
Release Information Command introduced in Junos OS Release 14.2R3 for Junos Fusion Provider Edge.
Command introduced in Junos OS Release 16.1R1 for Junos Fusion Enterprise.
Command introduced in Junos OS Release 17.2R1 for Junos Fusion Data Center.
Description Restart a process on a satellite device or devices from the aggregation device in a Junos
Fusion.
You would typically restart a process in a Junos Fusion for troubleshooting or debugging
purposes.
This command is intended for use by expert users for debugging purposes.
Options fpc fpc-slot—Restart the specified process on the satellite device in the specified FPC
slot ID only.
range—Restart the process on the satellite devices in the specified range of FPC slot IDs
only.
For instance, if you want to reboot the satellite devices using FPC slot IDs 101, 102,
and 103, you can enter a range of 101-103.
Release Information Command introduced in Junos OS Release 14.2R3 for Junos Fusion Provider Edge.
Command introduced in Junos OS Release 16.1R1 for Junos Fusion Enterprise.
Command introduced in Junos OS Release 17.2R1 for Junos Fusion Data Center.
Description Run a UNIX shell command for a satellite device from the aggregation device in a Junos
Fusion.
Options fpc fpc-slot—Run the shell command on the satellite device using the specified FPC slot
identifier only.
range—Run the shell command on the satellite devices in the specified range of FPC slot
identifiers only.
For instance, you can run the shell command on the satellite devices in FPC slot
identifiers 101, 102, and 103 by entering a range of 101-103.
<no-validate>
<re0 | re1>
<reboot>
<set [package-name1 package-name2]>
<unlink>
<upgrade-with-config>
<validate>
<validate-on-host hostname>
<validate-on-routing-engine routing-engine>
<force>
<force-host>
<no-copy>
<partition>
<reboot>
<unlink>
<upgrade-with-config>
Description For Junos OS Evolved, the request system software add command has a built-in feature
not to start the upgrade if a reboot is pending after an upgrade or rollback.
For information on valid filename and URL formats, see Format for Specifying Filenames
and URLs in Junos OS CLI Commands.
NOTE: Starting with Junos OS Release 15.1F3, the statement request system
software add installs a software package for the guest OS only for the
PTX5000 router with RE-DUO-C2600-16G, and for MX240, MX480, and
MX960 routers with RE-S-1800X4-32G-S.
Starting with Junos OS Release 15.1F5, the statement request system software
add installs a software package for the guest OS only for the MX2010 and
MX2020 routers with REMX2K-1800-32G-S.
On these routers, in order to install both Junos software and host software
packages, use the request vmhost software add command.
For example:
NOTE:
• The pathname in the protocol is the relative path to the user’s home
directory on the remote system and not the root directory.
• Do not use the scp protocol in the request system software add
command to download and install a software package or bundle from
a remote location. The previous statement does not apply to the
QFabric switch. The software upgrade is handled by the management
process (mgd), which does not support scp.
Use the file copy command to copy the software package or bundle
from the remote location to the /var/tmp directory on the hard disk:
file copy scp://source/package-name /var/tmp
Then install the software package or bundle using the request system
software add command:
request system software add /var/tmp/package-name
component all—(QFabric systems only) (Optional) Install the software package on all
of the QFabric components.
force—(Optional) Force the addition of the software package or bundle (ignore warnings).
lcc number —(TX Matrix routers and TX Matrix Plus routers only) (Optional) In a routing
matrix based on the TX Matrix router, install a software package or bundle on a T640
router that is connected to the TX Matrix router. In a routing matrix based on the TX
Matrix Plus router, install a software package or bundle on a router that is connected
to the TX Matrix Plus router.
Replace number with the following values depending on the LCC configuration:
• 0 through 7, when T1600 routers are connected to a TX Matrix Plus router with 3D
SIBs in a routing matrix.
partition —(QFX3500 switches only) (Optional) Format and repartition the media before
installation.
satellite slot-id—(Junos Fusion only) (Optional) Install the satellite software package
onto the specified satellite device using the satellite devices FPC slot identifier.
scc—(TX Matrix routers only) (Optional) Install a software package or bundle on a Routing
Engine on a TX Matrix router (or switch-card chassis).
sfc number—(TX Matrix Plus routers only) (Optional) Install a software package or bundle
on a Routing Engine on a TX Matrix Plus router. Replace number with 0.
no-copy—(Optional) Install a software package or bundle, but do not save copies of the
package or bundle files.
reboot—(Optional) After adding the software package or bundle, reboot the system. On
a QFabric switch, the software installation is not complete until you reboot the
component for which you have installed the software.
restart—(Optional) (For Junos OS Evolved only) This option allows you to upgrade the
system using an application-level restart, that is, no system reboot. First the system
determines how many applications need to restart (start with a new version), and
then, after sending output to the CLI session, it restarts those applications. Restarted
applications resync their state from the system. You can perform a dry run by using
the request system software validate-restart command before using the request
system software add restart command.
• In the case of mixed EX4200 and EX4500 Virtual Chassis, install two software
packages—a package for an EX4200 switch and the same release of the package
for an EX4500 switch—to upgrade all member switches in a mixed EX4200 and
EX4500 Virtual Chassis.
• In the case of M Series, MX Series, and T Series routers, install multiple (two or
more) software packages and software add-on packages at the same time. The
variable package-name can either be a list of installation packages, each separated
by a blank space, or 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.
unlink—(Optional) On M Series, T Series, and MX Series routers, use the unlink option to
remove the software package from this directory after a successful upgrade is
completed.
NOTE: Configuration files specified with this option must have the
extension .text or .xml and have the extension specified. Using the
extension .txt will not work.
NOTE: The validate option only works on systems that do not have
graceful-switchover (GRES) enabled. To use the validate option on a
system with GRES, either disable GRES for the duration of the installation,
or install using the command request system software in-service-upgrade,
which requires nonstop active routing (NSR) to be enabled when using
GRES.
Additional Information Before upgrading the software on the router or switch, when you have a known stable
system, issue the request system snapshot command to back up the software, including
the configuration, to the /altroot and /altconfig file systems. After you have upgraded
the software on the router or switch and are satisfied that the new package or bundle is
successfully installed and running, issue the request system snapshot command again
to back up the new software to the /altroot and /altconfig file systems.
After you run the request system snapshot command, you cannot return to the previous
version of the software because the running and backup copies of the software are
identical.
If you are upgrading more than one package at the same time, delete the operating
system package, jkernel, last. Add the operating system package, jkernel, first and the
routing software package, jroute, last. If you are upgrading all packages at once, delete
and add them in the following order:
By default, when you issue the request system software add package-name command on
a TX Matrix master Routing Engine, all the T640 master Routing Engines that are
connected to it are upgraded to the same version of software. If you issue the same
command on the TX Matrix backup Routing Engine, all the T640 backup Routing Engines
that are connected to it are upgraded to the same version of software.
Likewise, when you issue the request system software add package-name command on
a TX Matrix Plus master Routing Engine, all the T1600 or T4000 master Routing Engines
that are connected to it are upgraded to the same version of software. If you issue the
same command on the TX Matrix Plus backup Routing Engine, all the T1600 or T4000
backup Routing Engines that are connected to it are upgraded to the same version of
software.
Before installing software on a device that has one or more custom YANG data models
added to it, back up and remove the configuration data corresponding to the custom
YANG data models from the active configuration. For more information see Managing
YANG Packages and Configurations During a Software Upgrade or Downgrade.
Related • Format for Specifying Filenames and URLs in Junos OS CLI Commands
Documentation
• request system software delete on page 141
List of Sample Output request system software add validate on page 134
request system software add /var/tmp/ no-validate on page 135
request system software add no-copy no-validate reboot on page 135
request system software add validate-on-host on page 136
request system software add (Mixed EX4200 and EX4500 Virtual Chassis) on page 137
request system software add component all (QFabric Systems) on page 137
request system software add upgrade-group (Junos Fusion) on page 137
request system software add restart (Junos OS Evolved) on page 137
Output Fields When you enter this command, you are provided feedback on the status of your request.
Sample Output
request system software add (Mixed EX4200 and EX4500 Virtual Chassis)
user@switch> request system software add set
[/var/tmp/jinstall-ex-4200-11.1R1.1-domestic-signed.tgz
/var/tmp/jinstall-ex-4500-11.1R1.1-domestic-signed.tgz]
...
...
Adding software images. This process can take several minutes. Please be patient...
Download and Validate in Progress
re0: Starting upgrade : /var/tmp/qfx-ms-fixed-1-target1-ifmanarpcos.iso
re0: Single RE upgrade detected.
re0: Installing IMA keys of the incoming ISO image...
re0: Validating existing configs. See /var/log/validation_config.log for config
validation logs.
re0: Validation Passed. Going ahead with Installation
re0: Starting the installation...
re0: Copying files to
//soft/junos-evo-install-qfx-ms-fixed-x86-64-19.2R1-20190522.4-EVOI20190523235333-1...
re0: Running post install commands...
re0: Post install sequence was successful.
re0: Installation of image
junos-evo-install-qfx-ms-fixed-x86-64-19.2R1-20190522.4-EVOI20190523235333-1 done.
re0: Boot version is now
'junos-evo-install-qfx-ms-fixed-x86-64-19.2R1-20190522.4-EVOI20190523235333-1'
Image validation and installation succeeded. Restarting Applications.
Adding software images. This process can take several minutes. Please be patient...
Download and Validate in Progress
re0: Starting upgrade : /var/tmp/qfx-ms-fixed-1-target2-ifmanarpcossysman.iso
re0: Single RE upgrade detected.
re0: Installing IMA keys of the incoming ISO image...
re0: Validating existing configs. See /var/log/validation_config.log for config
validation logs.
re0: Validation Passed. Going ahead with Installation
re0: Starting the installation...
re0: Copying files to
//soft/junos-evo-install-qfx-ms-fixed-x86-64-19.2R1-20190522.4-EVOI20190523235731-1...
re0: Running post install commands...
re0: Post install sequence was successful.
re0: Installation of image
junos-evo-install-qfx-ms-fixed-x86-64-19.2R1-20190522.4-EVOI20190523235731-1 done.
re0: Boot version is now
'junos-evo-install-qfx-ms-fixed-x86-64-19.2R1-20190522.4-EVOI20190523235731-1'
Image validation and installation succeeded. Restarting Applications.
ifmanarpcossysmanimgdor
Adding software images. This process can take several minutes. Please be patient...
Download and Validate in Progress
re0: Starting upgrade :
/var/tmp/qfx-ms-fixed-1-target3-ifmanarpcossysmanimgdorchd.iso
re0: Single RE upgrade detected.
re0: Installing IMA keys of the incoming ISO image...
re0: Validating existing configs. See /var/log/validation_config.log for config
validation logs.
re0: Validation Passed. Going ahead with Installation
re0: Starting the installation...
re0: Copying files to
//soft/junos-evo-install-qfx-ms-fixed-x86-64-19.2R1-20190522.4-EVOI20190524000025...
re0: Running post install commands...
re0: Post install sequence was successful.
re0: Installation of image
junos-evo-install-qfx-ms-fixed-x86-64-19.2R1-20190522.4-EVOI20190524000025-gsanka-1
done.
re0: Boot version is now
'junos-evo-install-qfx-ms-fixed-x86-64-19.2R1-20190522.4-EVOI20190524000025'
Image validation and installation succeeded. Restarting Applications.
Options package-name—(Only for Junos OS Evolved) Name of the Junos OS Evolved package
running on the device. You can see this package name by using the request system
software list command. Type the package-name explicitly and do not use the tab
key to auto-complete the command.
You can delete any or all of the following software bundles or packages:
lcc number—(TX Matrix routers and TX Matrix Plus routers only) (Optional) In a routing
matrix, delete a software package or bundle on a T640 router indicated by lcc number
that is connected to the TX Matrix router. In a routing matrix, delete a software
package or bundle on a router indicated by lcc number that is connected to the TX
Matrix Plus router.
Replace number with the following values depending on the LCC configuration:
• 0 through 7, when T1600 routers are connected to a TX Matrix Plus router with 3D
SIBs in a routing matrix.
reboot—As of Junos OS 12.3 and greater, automatically reboot upon completing the
request system software delete command.
scc—(TX Matrix routers only) (Optional) Remove an extension or upgrade package from
the TX Matrix router (or switch-card chassis).
sfc number—(TX Matrix Plus routers only) (Optional) Remove an extension or upgrade
package from the TX Matrix Plus router. Replace number with 0.
A satellite software upgrade group is a group of satellite devices in the same Junos
Fusion that are designated to upgrade to the same satellite software version using
the same satellite software package.
Additional Information Before upgrading the software on the router or switch, when you have a known stable
system, issue the request system snapshot command to back up the software, including
the configuration, to the /altroot and /altconfig file systems (on routers) or the /, /altroot,
/config, /var, and /var/tmp file systems (on switches). After you have upgraded the
software on the router or switch and are satisfied that the new packages are successfully
installed and running, issue the request system snapshot command again to back up the
new software to the /altroot and /altconfig file systems (on routers) or the /, /altroot,
/config, /var, and /var/tmp file systems (on switches). After you run the request system
snapshot command, you cannot return to the previous version of the software, because
the running and backup copies of the software are identical.
List of Sample Output request system software delete jdocs on page 144
request system software delete (Junos OS Evolved) on page 145
Output Fields When you enter this command, you are provided feedback on the status of your request.
Sample Output
The following example displays the system software packages before and after the jdocs
package is deleted through the request system software delete command:
Comment:
JUNOS Base OS Software Suite [7.2R1.7]
Comment:
JUNOS Crypto Software Suite [7.2R1.7]
Comment:
JUNOS Online Documentation [7.2R1.7]
Comment:
JUNOS Kernel Software Suite [7.2R1.7]
...
Comment:
JUNOS Base OS Software Suite [7.2R1.7]
Comment:
JUNOS Crypto Software Suite [7.2R1.7]
Comment:
JUNOS Kernel Software Suite [7.2R1.7]
...
validate and no-validate options introduced for Junos OS Evolved Release 18.3R1.
package-name version option introduced for Junos OS Evolved Release 18.3R1.
with-old-snapshot-config option introduced for Junos OS Evolved Release 18.3R1.
Description This command reverts to the last successfully installed package before the request
system software (add | delete) command. It uses the copy stored in the /var/sw/pkg
directory.
Additional Information
• On Junos Fusion, the request system software rollback command can be used to roll
back the version of satellite software associated with a satellite software upgrade
group. Rolling back the version of satellite software associated with a satellite software
upgrade group triggers a satellite software upgrade.
• On M Series and T Series routers, if request system software add <jinstall> reboot was
used for the previous installation, then request system software rollback has no effect.
In this case, use jinstall to reinstall the required package.
• On M Series and T Series routers, if request system software add <sdk1> was used for
the previous installation, then request system software rollback removes the last
installed SDK package (sdk1 in this example).
• On SRX Series devices with dual root systems, when request system software rollback
is run, the system switches to the alternate root. Each root can have a different version
of Junos OS. Roll back takes each root back to the previously installed image.
• On QFX3500 and QFX3600 devices in a mixed Virtual Chassis, when the request system
software rollback command is issued, the system does not rollback to the image stored
in the alternate partition.
• On QFX5100 switches, the reboot option has been removed. To reboot the switch after
a software rollback, issue the request system reboot command as a separate, secondary
command.
• On Junos OS Evolved, the reboot command is required in order to complete the rollback.
lcc number—(TX Matrix routers and TX Matrix Plus routers only) (Optional) On a TX
Matrix router, attempt to roll back to the previous set of packages on a T640 router
connected to the TX Matrix router. On a TX Matrix Plus router, attempt to roll back
to the previous set of packages on a connected router connected to the TX Matrix
Plus router.
Replace number with the following values depending on the LCC configuration:
• 0 through 7, when T1600 routers are connected to a TX Matrix Plus router with 3D
SIBs in a routing matrix.
local—(EX4200 switches and MX Series routers only) (Optional) Attempt to roll back
to the previous set of packages on the local Virtual Chassis member.
none—For all versions of Junos OS up to and including Junos OS 11.4, revert to the set of
software as of the last successful request system software add. As of Junos OS 12.1
and later, revert to the last known good state before the most recent request system
software (add | delete) command.
package-name version—(Junos OS Evolved only) Select any installed version for the
rollback. The request system software rollback command uses the version instead
of the package-name. you can see the available versions by using the show system
software list command. If a version is not specified, the system rolls back to the
default rollback version (the one with the '<' before it on the show system software
list command output). You can specify any previous Junos OS Evolved release as
long as it is not the one that is currently running or the rollback version.
reboot—(Optional) For Junos OS 12.3 and later, the system reboots automatically to
complete the rollback. However, for Junos OS Evolved, you must explicitly specify
the reboot option to complete the rollback.
satellite slot-id—(Junos Fusion only) (Optional) Roll back the satellite software package
onto the specified satellite device using the satellite devices FPC slot identifier.
scc—(TX Matrix routers only) (Optional) Attempt to roll back to the previous set of
packages on the TX Matrix router (or switch-card chassis).
sfc number—(TX Matrix Plus routers only) (Optional) Attempt to roll back to the previous
set of packages on the TX Matrix Plus router. Replace number with 0.
Output Fields When you enter this command, you are provided feedback on the status of your request.
Sample Output
<dry-run>
<no-confirm>
<re0 | re1 | routing-engine (backup | both | local | master | other)>
Description Free storage space on the router or switch by rotating log files and proposing a list of files
for deletion. User input is required for file deletion. On a QFabric system, you can delete
debug files located on individual devices or on the entire QFabric system.
The Junos OS Evolved implementation of the request system storage cleanup command
is slightly different from the implementation on Junos OS:
Please check the list of files to be deleted using the dry-run option.
Continue anyway without checking? [yes,no] (yes)
The command cleans up any ISO files on the system, rotates syslogs, and clears trace
files. It does not remove user-created files.
• In Junos OS Evolved, the system computes the available space and emits o/p on
console for reference.
• When request system storage cleanup is executed, Junos OS Evolved displays the types
of files that are being deleted. See the Sample Output section below for an example.
NOTE: The request system storage cleanup | display xml rpc command displays
different XML tags for different file types. In Junos OS, only the file tag is
displayed for all types of files. For more information about the differences
between Junos OS and Junos OS Evolved, see How Junos OS Evolved Differs
from Junos OS.
Options all-members—(EX4200 switches and MX Series routers only) (Optional) Delete files
on the Virtual Chassis master Routing Engine only.
component (UUID | serial number | all)—(QFabric systems only) (Optional) Delete files
located on individual QFabric system devices or on the entire QFabric system.
force-deep—(Junos OS Evolved only) Deep clean all temporary files and rotate logs.
This option cleans up all the user-created files under /tmp and /var/tmp directories.
infrastructure name—(QFabric systems only) (Optional) Delete files on the fabric control
Routing Engine and fabric manager Routing Engine.
local—(EX4200 switches and MX Series routers only) (Optional) Delete files on the local
Virtual Chassis member.
name-tag name-tag—(QFabric systems only) (Optional) Delete debug files that match
a specific regular expression.
node-group name—(QFabric systems only) (Optional) Delete files on the Node group.
prune—(QFabric systems only) (Optional) Delete debug files located in either the core
or log debug repositories of a QFabric system device.
qfabric component name—(QFabric systems only) (Optional) Delete debug files located
in the debug repositories of a QFabric system device.
When Routing Engine is specified, the below message is shown before listing the
files and deleting them.
Please check the list of files to be deleted using the dry-run option. i.e.
request system storage cleanup dry-run
Do you want to proceed ? [yes,no] (no)
repository (core | log)—(QFabric systems only) (Optional) Specify the repository on the
QFabric system device for which you want to delete debug files.
Additional Information If logging is configured and being used, the dry-run option rotates the log files. In that
case, the output displays the message “Currently rotating log files, please wait.” If no
logging is currently under way, the output displays only a list of files to delete.
List of Sample Output request system storage cleanup dry-run on page 155
request system storage cleanup on page 155
request system storage cleanup (Junos OS Evolved) on page 156
request system storage cleanup dry-run (Junos OS Evolved) on page 157
request system storage cleanup force-deep (Junos OS Evolved) on page 159
request system storage cleanup director-group (QFabric Systems) on page 160
request system storage cleanup infrastructure device-name (QFabric
Systems) on page 162
request system storage cleanup interconnect-device device-name (QFabric
Systems) on page 163
request system storage cleanup node-group group-name (QFabric Systems) on page 164
request system storage cleanup qfabric component device-name (QFabric
Systems) on page 165
request system storage cleanup qfabric component device-name repository core
(QFabric Systems) on page 166
request system storage cleanup qfabric component all (QFabric Systems) on page 166
Output Fields Table 7 on page 154 describes the output fields for the request system storage cleanup
command. Output fields are listed in the approximate order in which they appear.
Repository scope: Repository where core-dump files and log files are stored. The
core-dump files are located in the core repository, and the log files
are located in the log repository. The default Repository scope is
shared since both the core and log repositories are shared by all of
the QFabric system devices.
Sample Output
Please check the list of files to be deleted using the dry-run option.
Continue anyway without checking? [yes,no] (no) yes
-------------------------------
node: RE0
-------------------------------
Clearing all core files
Clearing all local host core files and files from /var/log/watchdog
Clearing SI traces
-------------------------------
node: re0
-------------------------------
=== Other candidate logs, traces, core files which would be removed ===
total 0
-rw-r--r-- 1 root root 0 Jun 14 11:38 /var/log/access.log
-rw-r--r-- 1 root root 1243 Jun 14 11:55 /var/log/agentd-trace.log
-rw-r--r-- 1 root root 638 Jun 14 11:54 /var/log/alarm-mgmtd-trace.log
-rw-r--r-- 1 root root 3319611 Jun 14 13:40 /var/log/alarm-mgmtd.log
-rw-r--r-- 1 root root 620 Jun 14 11:55 /var/log/alarmd-trace.log
/var/log/journal:
total 4
drwxr-xr-x 2 root root 4096 Jun 14 11:37 ecd9ed14512f11e7953f0050569fd61f
/var/log/junosvm:
total 0
/var/log/lttng-traces:
total 8
drwxr-x--- 3 root root 4096 Jun 14 11:54 re0
drwxr-x--- 3 root root 4096 Jun 14 11:54 re1
/var/log/lttng-traces-re1:
total 8
drwxr-x--- 3 root root 4096 Jun 14 11:39 re0
drwxr-x--- 3 root root 4096 Jun 14 11:39 re1
/var/log/traces:
total 26472
drwxr-xr-x 2 root root 4096 Jun 14 11:43 fpc0.ccdpfe-t1.0
drwxr-xr-x 2 root root 4096 Jun 14 11:59 fpc0.ccdpfe-t1.1
drwxr-xr-x 2 root root 4096 Jun 14 11:59 fpc0.ccdpfe-t1.10
drwxr-xr-x 2 root root 4096 Jun 14 11:59 fpc0.ccdpfe-t1.11
drwxr-xr-x 2 root root 4096 Jun 14 11:59 fpc0.ccdpfe-t1.12
drwxr-xr-x 2 root root 4096 Jun 14 11:59 fpc0.ccdpfe-t1.13
drwxr-xr-x 2 root root 4096 Jun 14 11:59 fpc0.ccdpfe-t1.14
. . .
drwxr-xr-x 2 root root 4096 Jun 14 18:42 re1.trace_client.2
drwxr-xr-x 2 root root 4096 Jun 15 01:31 re1.trace_client.3
drwxr-xr-x 2 root root 4096 Jun 15 08:21 re1.trace_client.4
drwxr-xr-x 2 root root 4096 Jun 14 11:39 re1.trace_conf.0
drwxr-xr-x 2 root root 4096 Jun 14 11:54 re1.trace_conf.1
drwxr-xr-x 2 root root 4096 Jun 14 11:39 re1.trace_server.0
drwxr-xr-x 2 root root 4096 Jun 14 11:54 re1.trace_server.1
drwxr-xr-x 2 root root 4096 Jun 14 20:59 re1.trace_server.2
drwxr-xr-x 2 root root 4096 Jun 15 06:06 re1.trace_server.3
/var/log/watchdog:
total 0
=== Removes any ISO files in /data partition ===
find: '/var/lib/ftp/in/*': No such file or directory
=== Current list of software versions installed ===
=== Software versions except current and rollback would be removed ===
List of installed version(s) :
Please check the list of files to be deleted using the dry-run option.
Continue anyway without checking? [yes,no] (no) yes
-------------------------------
node: re0
-------------------------------
........
========= Start cleanup now ==========
=== Start removing other logs, traces, core files ===
Clearing core files
Clearing FPC logs
Clearing logical-systems logs
=== Clearing journal logs ===
Clearing log: /var/log/RE_journal.log
Clearing log: /var/log/RE_journal_boot.log
Clearing log: /var/log/alarm-mgmtd
Clearing log: /var/log/appDemo_stdout
Clearing log: /var/log/charonctl_trace.log
Clearing log: /var/log/configd-streamer.log
Clearing log: /var/log/core_mgr.log
Clearing log: /var/log/cscript.log
Clearing log: /var/log/eth_linkmon.log
Clearing log: /var/log/evo-cda-zx.log
Clearing log: /var/log/evoinit.log
Clearing log: /var/log/fibd-proxy.log
Clearing log: /var/log/i2ctrace.log
Clearing log: /var/log/i2ctrace_spmb0.log
Clearing log: /var/log/i2ctrace_spmb1.log
Clearing log: /var/log/icmpd.log
Clearing log: /var/log/ifinfo.log
Clearing log: /var/log/imgd_svr.log
Clearing log: /var/log/install
Clearing log: /var/log/interactive-commands
Clearing log: /var/log/jsd
Clearing log: /var/log/lastlog
Clearing log: /var/log/mcelog.log
Clearing log: /var/log/messages
Clearing log: /var/log/mgd-api
Clearing log: /var/log/mgmt-ethd-helper.log
Clearing log: /var/log/mib2d
Clearing log: /var/log/na-grpcd
Directory to delete:
45M 2011-11-08 10:57:43 /tmp/sfc-captures
Directory to delete:
49M 2011-11-08 10:45:20 /tmp/sfc-captures
re0:
--------------------------------------------------------------------------
re1:
--------------------------------------------------------------------------
re0:
--------------------------------------------------------------------------
BBAK0372:
--------------------------------------------------------------------------
EE3093:
--------------------------------------------------------------------------
request system storage cleanup qfabric component device-name repository core (QFabric Systems)
user@switch> request system storage cleanup qfabric component Test repository core
Command introduced in Junos OS Release 12.1 for the PTX Series Packet Transport
Routers.
Command introduced in Junos OS Release 12.2 for the ACX Series Universal Metro Routers.
Command introduced in Junos OS Release 12.3 for MX 2010 and MX2020 Universal
Routing Platforms.
Command introduced in Junos OS Release 13.2 for MX104 Universal Routing Platforms.
Command introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
satellite option introduced in Junos OS Release 14.2R3 for Junos Fusion.
Command introduced in Junos OS Release 17.2 for MX2008 and PTX10008 Routers.
Command introduced in Junos OS Release 17.3 for MX150 Router Appliance and MX10003
Universal Routing Platforms.
Command introduced in Junos OS Release 17.4 for MX204 Universal Routing Platforms.
Command introduced in Junos OS Release 18.1R1 for EX9251 Switches.
Command introduced in Junos OS Release 18.2R1 for EX9253 Switches and MX10008
Universal Routing Platforms.
Description Display information about the conditions that have been configured to trigger alarms.
Options none—Display information about the conditions that have been configured to trigger
alarms.
lcc number—(TX Matrix router and TX Matrix Plus router only) (Optional) Line-card
chassis number.
Replace number with the following values depending on the LCC configuration:
• 0 through 7, when T1600 routers are connected to a TX Matrix Plus router with 3D
SIBs in a routing matrix.
local—(MX Series routers only) (Optional) Display information about alarm conditions
for the local Virtual Chassis member.
scc—(TX Matrix router only) (Optional) Show information about the TX Matrix router
(switch-card chassis).
sfc number—(TX Matrix Plus router only) (Optional) Show information about the
respective TX Matrix Plus router, which is the switch-fabric chassis. Replace number
variable with 0.
Additional Information Chassis alarms are preset. You cannot modify them.
You cannot clear the alarms for chassis components. Instead, you must remedy the
cause of the alarm. When a chassis alarm LED 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
SONET 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
Apr 12 08:04:19 send: red alarm set, device FPC 1, reason FPC 1 Major Errors
- Error code: 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:
0 Minor (0)
According to the table above, 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:
Apr 12 08:04:10 send: red alarm set, device FPC 1, reason FPC 1 Major Errors
- Error code: 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:
CMALARM_LCHIP_LOUT_DESRD_PARITY_ERR 1
CMALARM_LCHIP_LOUT_DESRD_UNINIT_ERR 2
CMALARM_LCHIP_LOUT_DESRD_ILLEGALLINK_ERR 3
CMALARM_LCHIP_LOUT_DESRD_ILLEGALSIZE_ERR 4
CMALARM_LCHIP_LOUT_HDRF_TOERR_ERR 5
CMALARM_LCHIP_LOUT_HDRF_PARITY_ERR 6
CMALARM_LCHIP_LOUT_HDRF_UCERR_ERR 7
CMALARM_LCHIP_LOUT_NLIF_CRCDROP_ERR 8
CMALARM_LCHIP_LOUT_NLIF_CRCERR_ERR 9
CMALARM_LCHIP_UCODE_TIMEOUT_ERR 10
CMALARM_LCHIP_LIN_SRCTL_ACCT_DROP_ERR 11
CMALARM_LCHIP_LIN_SRCTL_ACCT_ADDR_SIZE_ERR 12
CMALARM_LCHIP_SRAM_PARITY_ERR 13
CMALARM_LCHIP_UCODE_OVFLW_ERR 14
CMALARM_LCHIP_LOUT_HDRF_MTU_ERR 15
CMALARM_MCHIP_ECC_UNCORRECT_ERR 128
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
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
CMALARM_RCHIP_SRAM_PARITY_ERR 512
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
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
List of Sample Output show chassis alarms (Alarms Active) on page 175
show chassis alarms (No Alarms Active) on page 175
show chassis alarms (Fan Tray) on page 175
show chassis alarms (MX150) on page 175
show chassis alarms (MX104 Router) on page 175
show chassis alarms (MX2010 Router) on page 175
show chassis alarms (MX2020 Router) on page 176
show chassis alarms (MX10003 Router) on page 176
show chassis alarms (MX204 Router) on page 176
show chassis alarms (MX2008 Router) on page 176
show chassis alarms (MX960, MX480, and MX240 Routers showing Major CB
Failure) on page 176
show chassis alarms (PTX10008 Router) on page 177
show chassis alarms (T4000 Router) on page 177
Output Fields Table 8 on page 174 lists the output fields for the show chassis alarms command. Output
fields are listed in the approximate order in which they appear.
Alarm time Date and time the alarm was first recorded.
Sample Output
Starting in Junos OS Release 19.2R1, the MX10003 routers do not raise an alarm if a Power
Entry Module (PEM) slot is empty. However, when the number of operational PEMs goes
below 2, the router raises a major alarm. This alarm is cleared when the required number
of PEMs are made available.
show chassis alarms (MX960, MX480, and MX240 Routers showing Major CB Failure)
A major CB 0 failure alarm occurs in the event of a bad CB (unknown or mismatched CBs
do not trigger this alarm in Junos Release OS 12.3R9 and later). Following GRES or
recovery, if the hardware issue persists, the traffic moves to the good CB and continues.
If the alarm was triggered by something transient like a power zone budget on GRES,
bringing the CB back online can clear the alarm. Otherwise, replace the bad CB. Note
that fabric link speed is not impacted by an offline SCB. The alarm migh be raised on
CB0, CB1, and CB2.
show chassis alarms (FPC Offline Due to Unreachable Destinations on a T Series Router)
user@host> show chassis alarms
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:52 PDT Major SIB 1 Absent
2004-08-05 18:43:52 PDT Major SIB 0 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:
--------------------------------------------------------------------------
5 alarms currently active
Alarm time Class Description
2004-08-05 18:43:53 PDT Minor SIB 3 Not Online
2004-08-05 18:43:49 PDT Major SIB 2 Absent
2004-08-05 18:43:49 PDT Major SIB 1 Absent
2004-08-05 18:43:49 PDT Major SIB 0 Absent
2004-08-05 18:43:28 PDT Major PEM 0 Not OK
lcc2-re0:
--------------------------------------------------------------------------
5 alarms currently active
Alarm time Class Description
2004-08-05 18:43:35 PDT Minor SIB 3 Not Online
2004-08-05 18:43:33 PDT Major SIB 2 Absent
sfc0-re0:
--------------------------------------------------------------------------
Alarm time Class Description
lcc0-re0:
--------------------------------------------------------------------------
12 alarms currently active
Alarm time Class Description
2014-04-08 14:36:08 IST Minor CB 1 M/S Switch Changed
2014-04-08 14:36:08 IST Minor CB 1 CHASSIS ID Changed
2014-04-08 14:35:43 IST Minor CB 0 M/S Switch Changed
2014-04-08 14:35:43 IST Minor CB 0 CHASSIS ID Changed
2014-04-08 14:29:30 IST Minor SIB 4 Not Online
2014-04-08 14:29:30 IST Minor SIB 3 Not Online
2014-04-08 14:29:30 IST Minor SIB 2 Not Online
2014-04-08 14:29:24 IST Major Rear Fan Tray Failure
2014-04-08 14:29:24 IST Major Front Bottom Fan Tray Improper for Platform
2014-04-08 14:29:24 IST Major Front Top Fan Tray Improper for Platform
2014-04-08 14:28:37 IST Major SIB 4 Absent
2014-04-08 14:28:37 IST Major SIB 3 Absent
lcc2-re0:
--------------------------------------------------------------------------
12 alarms currently active
Alarm time Class Description
2014-04-08 14:36:02 IST Minor CB 1 M/S Switch Changed
2014-04-08 14:36:02 IST Minor CB 1 CHASSIS ID Changed
2014-04-08 14:35:42 IST Minor CB 0 M/S Switch Changed
2014-04-08 14:34:42 IST Minor CB 0 CHASSIS ID Changed
2014-04-08 14:29:29 IST Minor SIB 0 CXP 7 Unsupported Optics
2014-04-08 14:29:27 IST Major Front Bottom Fan Tray Improper for Platform
2014-04-08 14:29:27 IST Major Front Top Fan Tray Improper for Platform
2014-04-08 14:29:25 IST Minor SIB 4 Not Online
2014-04-08 14:29:25 IST Minor SIB 3 Not Online
2014-04-08 14:28:47 IST Major PEM 0 Not OK
2014-04-08 14:28:36 IST Major SIB 2 Absent
2014-04-08 14:28:36 IST Minor Host 0 Boot from alternate media
lcc6-re0:
--------------------------------------------------------------------------
2 alarms currently active
Alarm time Class Description
2013-11-06 04:03:56 PST Minor SIB 1 CXP 0 XC HSL Link Error
2013-11-06 03:49:32 PST Major PEM 1 Not OK
show chassis alarms (Alarms on a T4000 Router After the enhanced-mode Statement is Enabled)
To enable improved virtual private LAN service (VPLS) MAC address learning on T4000
routers, you must include the enhanced-mode statement at the [edit chassis
network-services] hierarchy level and reboot the router. When router reboots, only the
T4000 Type 5 FPCs are required to be present on the router. If there are any other FPCs
(apart from T4000 Type 5 FPCs) on the T4000 router, such FPCs become 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
of the alarms.
show chassis alarms (Alarms Active on the QFX Series and OCX Series Switches)
user@switch> show chassis alarms
node-device ED3694
3 alarms currently active
Alarm time Class Description
2011-08-24 16:04:15 UTC Major Test:fte-0/1/2: Link down
2011-08-24 16:04:14 UTC Major Test:fte-0/1/0: Link down
2011-08-24 14:21:14 UTC Major Test PEM 0 is not supported/powered
IC-1:
--------------------------------------------------------------------------
1 alarms currently active
Test:
--------------------------------------------------------------------------
3 alarms currently active
Alarm time Class Description
2011-08-24 16:04:15 UTC Major Test:fte-0/1/2: Link down
2011-08-24 16:04:14 UTC Major Test:fte-0/1/0: Link down
2011-08-24 14:21:14 UTC Major Test PEM 0 is not supported/powered
SNG-0:
--------------------------------------------------------------------------
NW-NG-0:
--------------------------------------------------------------------------
1 alarms currently active
Alarm time Class Description
2011-08-24 15:49:27 UTC Major Test PEM 0 is not supported/powered
show chassis alarms (Mix of PDUs Alarm on a PTX5000 Packet Transport Router with FPC2-PTX-P1A)
All PDUs installed on a PTX5000 router must be of the same type. The Mix of PDUs or
Power Manager Non Operational alarm is raised when different types of PDUs are installed
on a PTX5000 router.
show chassis alarms (PDU Converter Failed Alarm on a PTX5000 Packet Transport Router with FPC2-PTX-P1A)
The PDU Converter Failed alarm is raised when one or more 36 V booster converter of a
DC PDU fails. If two or more 36 V booster converter fails, fan trays fail and the router
might get over heated. Therefore, when this alarm is raised, check the PDU and replace
it, if required.
show chassis alarms (No Power for System Alarm on a PTX5000 Packet Transport Router with FPC2-PTX-P1A)
user@host> show chassis alarms
show chassis alarms (Active Alarm to Indicate Status of the Bad SCB Clock on MX Series)
user@host> show chassis alarms
If LCMD is down on the backup RE, then the following alarm is seen on the Master.
If the LCMD process is crashing on the master, the system will switchover after one minute
provided the backup RE LCMD connection is stable. The system will not switchover under
the following conditions: if the backup RE LCMD connection is unstable or if the current
master just gained mastership. When the master has just gained mastership, the
switchover happens only after four minutes.
The LCM peer connection un-stable alarm is raised when the LCMD-CHASD IPC
communication flaps three times within a small interval of two to three minutes. Once
LCM peer connection un-stable alarm is raised, the connection status is monitored for
two minutes.
If there are no more connection flaps within this two minutes time interval, the LCM peer
connection un-stable alarm is cleared.
A major alarm is raised even if there is on one PLL lock error, and this alarm can be cleared
only through an FPC restart.
List of Syntax Syntax (T320, T640, T1600, and T4000 Routers) on page 187
Syntax (TX Matrix Routers) on page 187
Syntax (TX Matrix Plus Routers) on page 187
Syntax (MX Series Routers) on page 187
Syntax (MX104 Universal Routing Platforms) on page 188
Syntax (MX150 Router Appliance) on page 188
Syntax (MX2010, MX2020, and MX2008 Universal Routing Platforms) on page 188
Syntax (MX10003 and MX204 Universal Routing Platforms) on page 188
Syntax (EX8200 Switches) on page 188
Syntax (EX Series Switches except EX8200) on page 188
Syntax (QFX Series) on page 189
Syntax (OCX Series) on page 189
Syntax (PTX Series Packet Transport Routers) on page 189
Syntax (ACX Series Universal Metro Routers) on page 189
Syntax (ACX5048 and ACX5096 Routers) on page 189
Syntax (ACX500 Routers) on page 189
Command introduced in Junos OS Release 12.3 for MX 2020 and MX2010 Universal
Routing Platforms.
pem option introduced in Junos OS Release 12.3 for ACX4000 Universal Metro Routers.
satellite option introduced in Junos OS Release 14.2R3.
all-members, local, and member member-id options introduced in Junos OS Release 15.1
for MX2010 and MX2020 routers.
Command introduced in Junos OS Release 15.1X54-D20 for ACX5048 and ACX5096
Routers.
Command introduced in Junos OS Release 17.2 for MX2008 Universal Routing Platforms
and PTX10008 Routers.
Command introduced in Junos OS Release 17.3 for MX150 Router Appliance and MX10003
Universal Routing Platforms.
Command introduced in Junos OS Release 17.4 for MX204 Universal Routing Platforms.
Command introduced in Junos OS Release 18.1R1 for EX9251 Switches.
Command introduced in Junos OS Release 18.2R1 for EX9253 Switches and MX10008
Routers.
Description Display environmental information about the router or switch chassis, including the
temperature and information about the fans, power supplies, and Routing Engine.
Starting with Junos OS Release 14.1, the show chassis environment cb cb-slot-number |
ccg ccg-slot-number | fpc fpc-slot-number | fpm | monitored | pdu pdu-slot-number |
routing-engine re-slot-number | sib sib-slot-number operational mode command output
displays environmental information for the new DC power supply module (PSM) and
power distribution unit (PDU) that are added to provide power to the high-density FPC
(FPC2-PTX-P1A) and other components in a PTX5000 Packet Transport Router.
all-members—(MX Series routers and EX Series switches only) (Optional) Display chassis
environmental information for all the members of the Virtual Chassis configuration.
fpc fpc-slot—(EX Series switches, M120, M320, and M40e routers, MX Series routers,
MX2010 routers, MX2020 routers, MX2008 routers, PTX Series Packet Transport
Routers, QFX Series, QFX3500 switches, QFabric systems, T Series routers, and TX
Matrix Plus routers) (Optional) Display chassis environmental information for a
specified Flexible PIC Concentrator. For MX2010 and MX2008 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 the hardware documentation for your switch for information on
FPC numbering. On a TX Matrix Plus router with 3D SIBs replace fpc-slot with a value
from 0 through 63.
fpm—(M120, M320, and M40e routers, MX2010 routers, MX2020 routers, MX2008 routers,
PTX Series, Packet Transport Routers, T Series routers, and TX Matrix Plus routers
only) (Optional) Display chassis environmental information for the craft interface
(FPM).
lcc number—(TX Matrix routers and TX Matrix Plus routers only) (Optional) Line-card
chassis number.
Replace number with the following values depending on the LCC configuration:
• 0 through 7, when T1600 routers are connected to a TX Matrix Plus router with 3D
SIBs in a routing matrix.
local—(MX Series routers and EX Series switches only) (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.
monitored—(MX2020 routers and PTX Series Packet Transport Routers only) (Optional)
Display chassis environmental information for monitored temperatures only.
Temperatures that are not included in temperature alarm computations are not
displayed.
pem pem-slot-number—(ACX Series Universal Metro Routers, M120, M320, and M40e
routers, MX Series routers, MX104 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.
scg—(T Series routers only) (Optional) Display chassis environmental information about
the SONET Clock Generator.
sfc number—(TX Matrix Plus routers only) (Optional) Display chassis environmental
information about the respective TX Matrix Plus router ( switch-fabric chassis).
Replace number variable with 0.
sib sib-slot-number—(M320 routers, PTX Series Packet Transport Routers, 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.
List of Sample Output show chassis environment (M5 Router) on page 196
Output Fields Table 9 on page 195 lists the output fields for the show chassis environment command.
Output fields are listed in the approximate order in which they appear.
• Temp: Temperature of air flowing through the chassis in degrees Celsius (C) and Fahrenheit (F).
• On PTX Series Packet Transport Routers and MX2010, MX2020, and MX2008 Routers, multiple
cooling zones are supported. FRU temperatures in each zone are coordinated with the fan speed
of fan trays in those zones.
• EX2200 switches have a side-to-rear cooling system. The Local Intake temperature is measured
by the sensor on the right side of the chassis, and the Remote Intake temperature is measured
by the sensor on the left side of the chassis.
• 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 Routers and MX2010, MX2020, and MX2008 Routers, multiple
fan trays are supported. Fan status is reported in Fan Tray or Fan combinations. Measurement
indicates actual fan RPM (PTX and MX2010, MX2020, and MX2008 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 Routers, 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, MX2020, and MX2008 Routers) Information about the chassis component: Routing Engines,
Controls Boards (CBs), Switch Fabric Boards (SFBs), PICs, Flexible PIC Concentrators (FPCs), and
Adapter Cards (ADCs).
(MX104 Routers) Information about the chassis components: Routing Engines, Control Board (CB),
Power Entry Module (PEM), and Compact Forwarding Engine Board (AFEB).
(QFabric Systems) Information about the chassis component: Control Boards, Routing Engines,
Flexible PIC Concentrators (FPCs), and Power Entry Modules (PEMs), Node Devices, and Interconnect
Devices.
(QFX Series) Information about the chassis component: Flexible PIC Concentrators (FPCs), and
Power Entry Modules (PEMs).
Status (MX104, MX2010, MX2020, and MX2008 Routers) Status of the specified chassis component. For
example, if the Class is Fan, the fan status can be:
Measurement (MX104, MX2010, MX2020, and MX2008 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.
Sample Output
PEM 3 Check
PEM 4 Check
PEM 5 Check
Fans Fan Tray 0 Fan 0 OK Spinning at normal speed
Fan Tray 0 Fan 1 OK Spinning at normal speed
Fan Tray 0 Fan 2 OK Spinning at normal speed
Fan Tray 0 Fan 3 OK Spinning at normal speed
Fan Tray 0 Fan 4 Failed
Fan Tray 0 Fan 5 Failed
Fan Tray 0 Fan 6 OK Spinning at normal speed
Fan Tray 0 Fan 7 OK Spinning at normal speed
Fan Tray 0 Fan 8 OK Spinning at normal speed
Fan Tray 0 Fan 9 OK Spinning at normal speed
Fan Tray 0 Fan 10 OK Spinning at normal speed
Fan Tray 1 Fan 0 OK Spinning at normal speed
Fan Tray 1 Fan 1 OK Spinning at normal speed
Fan Tray 1 Fan 2 OK Spinning at normal speed
Fan Tray 1 Fan 3 OK Spinning at normal speed
Fan Tray 1 Fan 4 OK Spinning at normal speed
Fan Tray 1 Fan 5 OK Spinning at normal speed
Fan Tray 1 Fan 6 OK Spinning at normal speed
Fan Tray 1 Fan 7 OK Spinning at normal speed
Fan Tray 1 Fan 8 OK Spinning at normal speed
Fan Tray 1 Fan 9 OK Spinning at normal speed
Fan Tray 1 Fan 10 OK Spinning at normal speed
SFB 0 Intake-A OK 32 degrees C / 89 degrees F
SFB 0 Intake-B OK 21 degrees C / 69 degrees F
SFB 0 Exhaust-A OK 27 degrees C / 80 degrees F
SFB 0 Exhaust-B OK 32 degrees C / 89 degrees F
SFB 0 PF0 OK 39 degrees C / 102 degrees F
SFB 0 PF1 OK 29 degrees C / 84 degrees F
SFB 1 Intake-A OK 43 degrees C / 109 degrees F
SFB 1 Intake-B OK 20 degrees C / 68 degrees F
SFB 1 Exhaust-A OK 25 degrees C / 77 degrees F
SFB 1 Exhaust-B OK 44 degrees C / 111 degrees F
SFB 1 PF0 OK 50 degrees C / 122 degrees F
SFB 1 PF1 OK 29 degrees C / 84 degrees F
SFB 2 Intake-A OK 39 degrees C / 102 degrees F
SFB 2 Intake-B OK 20 degrees C / 68 degrees F
SFB 2 Exhaust-A OK 25 degrees C / 77 degrees F
SFB 2 Exhaust-B OK 38 degrees C / 100 degrees F
SFB 2 PF0 OK 45 degrees C / 113 degrees F
SFB 2 PF1 OK 30 degrees C / 86 degrees F
SFB 3 Intake-A OK 36 degrees C / 96 degrees F
SFB 3 Intake-B OK 20 degrees C / 68 degrees F
SFB 3 Exhaust-A OK 25 degrees C / 77 degrees F
SFB 3 Exhaust-B OK 35 degrees C / 95 degrees F
SFB 3 PF0 OK 42 degrees C / 107 degrees F
SFB 3 PF1 OK 29 degrees C / 84 degrees F
SFB 4 Intake-A OK 30 degrees C / 86 degrees F
SFB 4 Intake-B OK 20 degrees C / 68 degrees F
SFB 4 Exhaust-A OK 25 degrees C / 77 degrees F
SFB 4 Exhaust-B OK 31 degrees C / 87 degrees F
SFB 4 PF0 OK 41 degrees C / 105 degrees F
SFB 4 PF1 OK 29 degrees C / 84 degrees F
SFB 5 Intake-A OK 30 degrees C / 86 degrees F
SFB 5 Intake-B OK 21 degrees C / 69 degrees F
SFB 5 Exhaust-A OK 25 degrees C / 77 degrees F
SFB 5 Exhaust-B OK 30 degrees C / 86 degrees F
SPMB 0 OK
SPMB 1 OK
--------------------------------------------------------------------------
Class Item Status Measurement
Temp PEM 0 Absent
PEM 1 OK 29 degrees C / 84 degrees F
Routing Engine 0 OK 34 degrees C / 93 degrees F
Routing Engine 1 OK 34 degrees C / 93 degrees F
CB 0 OK 32 degrees C / 89 degrees F
CB 1 OK 32 degrees C / 89 degrees F
SIB 0 OK 44 degrees C / 111 degrees F
SIB 0 (B) OK 44 degrees C / 111 degrees F
FPM GBUS OK 27 degrees C / 80 degrees F
FPM Display OK 32 degrees C / 89 degrees F
Fans Top Left Front fan OK Spinning at normal speed
Top Left Middle fan OK Spinning at normal speed
Top Left Rear fan OK Spinning at normal speed
Top Right Front fan OK Spinning at normal speed
Top Right Middle fan OK Spinning at normal speed
Top Right Rear fan OK Spinning at normal speed
Bottom Left Front fan OK Spinning at normal speed
Bottom Left Middle fan OK Spinning at normal speed
Bottom Left Rear fan OK Spinning at normal speed
Bottom Right Front fan OK Spinning at normal speed
Bottom Right Middle fan OK Spinning at normal speed
Bottom Right Rear fan OK Spinning at normal speed
Rear Tray Top fan OK Spinning at normal speed
Rear Tray Second fan OK Spinning at normal speed
Rear Tray Third fan OK Spinning at normal speed
Rear Tray Fourth fan OK Spinning at normal speed
Rear Tray Fifth fan OK Spinning at normal speed
Rear Tray Sixth fan OK Spinning at normal speed
Rear Tray Seventh fan OK Spinning at normal speed
Rear Tray Bottom fan OK Spinning at normal speed
Misc CIP 0 OK
CIP 1 OK
SPMB 0 OK
SPMB 1 OK
lcc0-re0:
--------------------------------------------------------------------------
Class Item Status Measurement
Temp PEM 0 OK 29 degrees C / 84 degrees F
PEM 1 Absent
SCG 0 OK 35 degrees C / 95 degrees F
SCG 1 Absent
Routing Engine 0 OK 39 degrees C / 102 degrees F
Routing Engine 1 OK 36 degrees C / 96 degrees F
CB 0 OK 32 degrees C / 89 degrees F
CB 1 OK 32 degrees C / 89 degrees F
SIB 0 OK 40 degrees C / 104 degrees F
SIB 0 (B) OK 51 degrees C / 123 degrees F
FPC 0 Top OK 45 degrees C / 113 degrees F
FPC 0 Bottom OK 31 degrees C / 87 degrees F
lcc2-re0:
--------------------------------------------------------------------------
Class Item Status Measurement
Temp PEM 0 OK 29 degrees C / 84 degrees F
PEM 1 Absent
SCG 0 OK 32 degrees C / 89 degrees F
SCG 1 Absent
Routing Engine 0 OK 31 degrees C / 87 degrees F
Routing Engine 1 OK 32 degrees C / 89 degrees F
CB 0 OK 30 degrees C / 86 degrees F
SIB 0 OK 38 degrees C / 100 degrees F
SIB 0 (B) OK 49 degrees C / 120 degrees F
FPC 0 Top OK 45 degrees C / 113 degrees F
FPC 0 Bottom OK 33 degrees C / 91 degrees F
FPC 1 Top OK 37 degrees C / 98 degrees F
FPC 1 Bottom OK 33 degrees C / 91 degrees F
FPM GBUS OK 30 degrees C / 86 degrees F
FPM Display OK 34 degrees C / 93 degrees F
Fans Top Left Front fan OK Spinning at normal speed
Top Left Middle fan OK Spinning at normal speed
...
--------------------------------------------------------------------------
Class Item Status Measurement
Temp PEM 0 OK 28 degrees C / 82 degrees F
PEM 1 Absent
Routing Engine 0 OK 27 degrees C / 80 degrees F
Routing Engine 1 OK 29 degrees C / 84 degrees F
CB 0 Intake OK 26 degrees C / 78 degrees F
CB 0 Exhaust A OK 25 degrees C / 77 degrees F
CB 0 Exhaust B OK 25 degrees C / 77 degrees F
CB 1 Intake OK 26 degrees C / 78 degrees F
CB 1 Exhaust A OK 26 degrees C / 78 degrees F
CB 1 Exhaust B OK 26 degrees C / 78 degrees F
lcc0-re0:
--------------------------------------------------------------------------
Class Item Status Measurement
Temp PEM 0 OK 27 degrees C / 80 degrees F
PEM 1 Absent
SCG 0 OK 31 degrees C / 87 degrees F
SCG 1 OK 35 degrees C / 95 degrees F
Routing Engine 0 OK 30 degrees C / 86 degrees F
Routing Engine 1 OK 30 degrees C / 86 degrees F
CB 0 OK 31 degrees C / 87 degrees F
CB 1 OK 31 degrees C / 87 degrees F
SIB 0 OK 41 degrees C / 105 degrees F
SIB 0 (B) OK 34 degrees C / 93 degrees F
SIB 1 OK 0 degrees C / 32 degrees F
SIB 1 (B) OK 0 degrees C / 32 degrees F
SIB 2 OK 0 degrees C / 32 degrees F
SIB 2 (B) OK 0 degrees C / 32 degrees F
SIB 3 OK 0 degrees C / 32 degrees F
SIB 3 (B) OK 0 degrees C / 32 degrees F
SIB 4 OK 0 degrees C / 32 degrees F
SIB 4 (B) OK 0 degrees C / 32 degrees F
FPC 0 Top OK 49 degrees C / 120 degrees F
FPC 0 Bottom OK 50 degrees C / 122 degrees F
FPC 1 Top OK 48 degrees C / 118 degrees F
FPC 1 Bottom OK 49 degrees C / 120 degrees F
FPM GBUS OK 27 degrees C / 80 degrees F
FPM Display OK 30 degrees C / 86 degrees F
Fans Top Left Front fan OK Spinning at normal speed
Top Left Middle fan OK Spinning at normal speed
Top Left Rear fan OK Spinning at normal speed
Top Right Front fan OK Spinning at normal speed
Top Right Middle fan OK Spinning at normal speed
Top Right Rear fan OK Spinning at normal speed
Bottom Left Front fan OK Spinning at normal speed
Bottom Left Middle fan OK Spinning at normal speed
Bottom Left Rear fan OK Spinning at normal speed
Bottom Right Front fan OK Spinning at normal speed
Bottom Right Middle fan OK Spinning at normal speed
Bottom Right Rear fan OK Spinning at normal speed
Rear Tray Top fan OK Spinning at normal speed
Rear Tray Second fan OK Spinning at normal speed
Rear Tray Third fan OK Spinning at normal speed
Rear Tray Fourth fan OK Spinning at normal speed
Rear Tray Fifth fan OK Spinning at normal speed
Rear Tray Sixth fan OK Spinning at normal speed
Rear Tray Seventh fan OK Spinning at normal speed
Rear Tray Bottom fan OK Spinning at normal speed
Misc CIP OK
SPMB 0 OK
SPMB 1 OK
--------------------------------------------------------------------------
Class Item Status Measurement
Temp PEM 0 Check 30 degrees C / 86 degrees F
PEM 1 OK 33 degrees C / 91 degrees F
Routing Engine 0 OK 28 degrees C / 82 degrees F
Routing Engine 0 CPU OK 42 degrees C / 107 degrees F
Routing Engine 1 OK 29 degrees C / 84 degrees F
Routing Engine 1 CPU OK 44 degrees C / 111 degrees F
CB 0 Intake OK 30 degrees C / 86 degrees F
CB 0 Exhaust A OK 28 degrees C / 82 degrees F
CB 0 Exhaust B OK 30 degrees C / 86 degrees F
CB 1 Intake OK 31 degrees C / 87 degrees F
CB 1 Exhaust A OK 27 degrees C / 80 degrees F
CB 1 Exhaust B OK 31 degrees C / 87 degrees F
SIB F13 0 Board OK 44 degrees C / 111 degrees F
SIB F13 0 XF Junction OK 62 degrees C / 143 degrees F
SIB F13 3 Board OK 45 degrees C / 113 degrees F
SIB F13 3 XF Junction OK 60 degrees C / 140 degrees F
SIB F13 6 Board OK 47 degrees C / 116 degrees F
SIB F13 6 XF Junction OK 62 degrees C / 143 degrees F
SIB F2S 0/0 Board OK 32 degrees C / 89 degrees F
SIB F2S 0/0 XF Junction OK 42 degrees C / 107 degrees F
SIB F2S 0/2 Board OK 31 degrees C / 87 degrees F
SIB F2S 0/2 XF Junction OK 41 degrees C / 105 degrees F
SIB F2S 0/4 Board OK 31 degrees C / 87 degrees F
SIB F2S 0/4 XF Junction OK 42 degrees C / 107 degrees F
SIB F2S 0/6 Board OK 31 degrees C / 87 degrees F
SIB F2S 0/6 XF Junction OK 41 degrees C / 105 degrees F
SIB F2S 1/0 Board OK 31 degrees C / 87 degrees F
SIB F2S 1/0 XF Junction OK 41 degrees C / 105 degrees F
SIB F2S 1/2 Board OK 29 degrees C / 84 degrees F
SIB F2S 1/2 XF Junction OK 39 degrees C / 102 degrees F
SIB F2S 1/4 Board OK 29 degrees C / 84 degrees F
SIB F2S 1/4 XF Junction OK 35 degrees C / 95 degrees F
SIB F2S 1/6 Board OK 30 degrees C / 86 degrees F
SIB F2S 1/6 XF Junction OK 41 degrees C / 105 degrees F
SIB F2S 2/0 Board OK 30 degrees C / 86 degrees F
SIB F2S 2/0 XF Junction OK 42 degrees C / 107 degrees F
SIB F2S 2/2 Board OK 28 degrees C / 82 degrees F
SIB F2S 2/2 XF Junction OK 39 degrees C / 102 degrees F
SIB F2S 2/4 Board OK 29 degrees C / 84 degrees F
SIB F2S 2/4 XF Junction OK 42 degrees C / 107 degrees F
SIB F2S 2/6 Board OK 29 degrees C / 84 degrees F
SIB F2S 2/6 XF Junction OK 41 degrees C / 105 degrees F
CIP 0 Intake OK 25 degrees C / 77 degrees F
CIP 0 Exhaust A OK 26 degrees C / 78 degrees F
CIP 0 Exhaust B OK 26 degrees C / 78 degrees F
CIP 1 Intake OK 26 degrees C / 78 degrees F
CIP 1 Exhaust A OK 27 degrees C / 80 degrees F
CIP 1 Exhaust B OK 27 degrees C / 80 degrees F
Fans Fan Tray 0 Fan 1 OK Spinning at normal speed
Fan Tray 0 Fan 2 OK Spinning at normal speed
lcc0-re0:
--------------------------------------------------------------------------
Class Item Status Measurement
Temp PEM 0 OK 29 degrees C / 84 degrees F
PEM 1 Check 29 degrees C / 84 degrees F
SCG 0 OK 32 degrees C / 89 degrees F
SCG 1 OK 33 degrees C / 91 degrees F
Routing Engine 0 OK 32 degrees C / 89 degrees F
Routing Engine 0 CPU OK 51 degrees C / 123 degrees F
Routing Engine 1 OK 32 degrees C / 89 degrees F
Routing Engine 1 CPU OK 49 degrees C / 120 degrees F
CB 0 OK 34 degrees C / 93 degrees F
CB 1 OK 34 degrees C / 93 degrees F
SIB 0 OK 39 degrees C / 102 degrees F
SIB 0 (B) Absent
SIB 1 OK 39 degrees C / 102 degrees F
SIB 1 (B) Absent
SIB 2 OK 39 degrees C / 102 degrees F
SIB 2 (B) Absent
FPC 4 Top OK 43 degrees C / 109 degrees F
FPC 4 Bottom OK 43 degrees C / 109 degrees F
FPC 7 Fan Intake OK 35 degrees C / 95 degrees F
FPC 7 Fan Exhaust OK 50 degrees C / 122 degrees F
FPC 7 PMB OK 50 degrees C / 122 degrees F
FPC 7 LMB0 OK 55 degrees C / 131 degrees F
FPC 7 LMB1 OK 49 degrees C / 120 degrees F
FPC 7 LMB2 OK 39 degrees C / 102 degrees F
FPC 7 PFE1 LU2 OK 55 degrees C / 131 degrees F
FPC 7 PFE1 LU0 OK 45 degrees C / 113 degrees F
FPC 7 PFE0 LU0 OK 62 degrees C / 143 degrees F
FPC 7 XF1 OK 52 degrees C / 125 degrees F
FPC 7 XF0 OK 61 degrees C / 141 degrees F
FPC 7 XM1 OK 39 degrees C / 102 degrees F
FPC 7 XM0 OK 56 degrees C / 132 degrees F
FPC 7 PFE0 LU1 OK 60 degrees C / 140 degrees F
FPC 7 PFE0 LU2 OK 55 degrees C / 131 degrees F
FPC 7 PFE1 LU1 OK 41 degrees C / 105 degrees F
FPM GBUS OK 24 degrees C / 75 degrees F
FPM Display OK 28 degrees C / 82 degrees F
Fans Top Left Front fan OK Spinning at normal speed
Top Left Middle fan OK Spinning at normal speed
Top Left Rear fan OK Spinning at normal speed
Top Right Front fan OK Spinning at normal speed
Top Right Middle fan OK Spinning at normal speed
Top Right Rear fan OK Spinning at normal speed
Bottom Left Front fan OK Spinning at normal speed
Bottom Left Middle fan OK Spinning at normal speed
Bottom Left Rear fan OK Spinning at normal speed
Bottom Right Front fan OK Spinning at normal speed
Bottom Right Middle fan OK Spinning at normal speed
Bottom Right Rear fan OK Spinning at normal speed
Rear Tray fan 1 (Top) OK Spinning at normal speed
Rear Tray fan 2 OK Spinning at normal speed
Rear Tray fan 3 OK Spinning at normal speed
Rear Tray fan 4 OK Spinning at normal speed
Rear Tray fan 5 OK Spinning at normal speed
Rear Tray fan 6 OK Spinning at normal speed
Rear Tray fan 7 OK Spinning at normal speed
Rear Tray fan 8 OK Spinning at normal speed
Rear Tray fan 9 OK Spinning at normal speed
Rear Tray fan 10 OK Spinning at normal speed
Rear Tray fan 11 OK Spinning at normal speed
Rear Tray fan 12 OK Spinning at normal speed
Rear Tray fan 13 OK Spinning at normal speed
Rear Tray fan 14 OK Spinning at normal speed
Rear Tray fan 15 OK Spinning at normal speed
Rear Tray fan 16 (Bottom) OK Spinning at normal speed
Misc CIP OK
SPMB 0 OK
SPMB 1 OK
[...Output truncated...]
PDU 1 Absent
CCG 0 OK 44 degrees C / 111 degrees F
CCG 1 OK 44 degrees C / 111 degrees F
Routing Engine 0 OK 62 degrees C / 143 degrees F
Routing Engine 0 CPU OK 75 degrees C / 167 degrees F
Routing Engine 1 OK 51 degrees C / 123 degrees F
Routing Engine 1 CPU OK 64 degrees C / 147 degrees F
CB 0 Intake OK 38 degrees C / 100 degrees F
CB 0 Exhaust A OK 46 degrees C / 114 degrees F
CB 0 Exhaust B OK 42 degrees C / 107 degrees F
CB 1 Intake OK 35 degrees C / 95 degrees F
CB 1 Exhaust A OK 39 degrees C / 102 degrees F
CB 1 Exhaust B OK 36 degrees C / 96 degrees F
SIB 0 Exhaust OK 47 degrees C / 116 degrees F
SIB 0 Junction OK 45 degrees C / 113 degrees F
SIB 1 Exhaust OK 44 degrees C / 111 degrees F
SIB 1 Junction OK 43 degrees C / 109 degrees F
SIB 2 Exhaust OK 47 degrees C / 116 degrees F
SIB 2 Junction OK 42 degrees C / 107 degrees F
SIB 3 Exhaust OK 43 degrees C / 109 degrees F
SIB 3 Junction OK 43 degrees C / 109 degrees F
SIB 4 Exhaust OK 47 degrees C / 116 degrees F
SIB 4 Junction OK 42 degrees C / 107 degrees F
SIB 5 Exhaust OK 42 degrees C / 107 degrees F
SIB 5 Junction OK 40 degrees C / 104 degrees F
SIB 6 Exhaust OK 46 degrees C / 114 degrees F
SIB 6 Junction OK 42 degrees C / 107 degrees F
SIB 7 Exhaust OK 43 degrees C / 109 degrees F
SIB 7 Junction OK 39 degrees C / 102 degrees F
SIB 8 Exhaust OK 44 degrees C / 111 degrees F
SIB 8 Junction OK 41 degrees C / 105 degrees F
FPC 0 PMB OK 35 degrees C / 95 degrees F
FPC 0 Intake OK 33 degrees C / 91 degrees F
FPC 0 Exhaust A OK 51 degrees C / 123 degrees F
FPC 0 Exhaust B OK 43 degrees C / 109 degrees F
FPC 0 TL0 OK 48 degrees C / 118 degrees F
FPC 0 TQ0 OK 53 degrees C / 127 degrees F
FPC 0 TL1 OK 56 degrees C / 132 degrees F
FPC 0 TQ1 OK 58 degrees C / 136 degrees F
FPC 0 TL2 OK 55 degrees C / 131 degrees F
FPC 0 TQ2 OK 56 degrees C / 132 degrees F
FPC 0 TL3 OK 59 degrees C / 138 degrees F
FPC 0 TQ3 OK 59 degrees C / 138 degrees F
FPC 2 PMB OK 35 degrees C / 95 degrees F
FPC 2 Intake OK 34 degrees C / 93 degrees F
FPC 2 Exhaust A OK 51 degrees C / 123 degrees F
FPC 2 Exhaust B OK 52 degrees C / 125 degrees F
FPC 2 TL0 OK 53 degrees C / 127 degrees F
FPC 2 TQ0 OK 53 degrees C / 127 degrees F
FPC 2 TL1 OK 57 degrees C / 134 degrees F
FPC 2 TQ1 OK 58 degrees C / 136 degrees F
FPC 2 TL2 OK 54 degrees C / 129 degrees F
FPC 2 TQ2 OK 59 degrees C / 138 degrees F
FPC 2 TL3 OK 60 degrees C / 140 degrees F
FPC 2 TQ3 OK 64 degrees C / 147 degrees F
PIC 2/0 Ambient OK 49 degrees C / 120 degrees F
FPC 3 PMB OK 34 degrees C / 93 degrees F
FPC 3 Intake OK 35 degrees C / 95 degrees F
FPC 3 Exhaust A OK 54 degrees C / 129 degrees F
FPC 3 Exhaust B OK 49 degrees C / 120 degrees F
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.
Description (M40e, M120, M160, M320, MX Series, T Series routers, EX Series, QFX Series, and PTX
Series routers only) Display environmental information about Flexible PIC Concentrators
(FPCs).
Options none—Display environmental information about all FPCs. On a TX Matrix router, display
environmental information about all FPCs on the TX Matrix router and its attached
T640 routers. On a TX Matrix Plus router, display environmental information about
all FPCs on the TX Matrix Plus router and its attached routers.
lcc number—(TX Matrix router and TX Matrix Plus router only) (Optional) Line-card
chassis number.
Replace number with the following values depending on the LCC configuration:
• 0 through 7, when T1600 routers are connected to a TX Matrix Plus router with 3D
SIBs in a routing matrix.
local—(MX Series routers only) (Optional) Display environmental information for the
FPCs in the local Virtual Chassis member.
• (TX Matrix and TX Matrix Plus routers only) On a TX Matrix router, if you specify
the number of the T640 router by using only the lcc number option (the
recommended method), replace slot with a value from 0 through 7. Similarly, on
a TX Matrix Plus router, if you specify the number of the router by using only the
lcc number option (the recommended method), replace slot with a value from 0
through 7. Otherwise, replace slot with a value from 0 through 31. For example, the
following commands have the same result:
• EX Series switches:
• EX6210 switches–Replace slot with a value from 0 through 3 (line card only),
4 or 5 (line card or Switch Fabric and Rotuing Engine (SRE) module), or 6 through
9 (line card only).
• Resynchronizing FPC Sequence Numbers with Active FPCs when an FPC Comes Online
List of Sample Output show chassis environment fpc (M120 Router) on page 276
show chassis environment fpc (M160 Router) on page 277
show chassis environment fpc (M320 Router) on page 277
show chassis environment fpc (MX2020 Router) on page 278
show chassis environment fpc (MX2010 Router) on page 281
show chassis environment fpc (MX2008 Router) on page 283
show chassis environment fpc (MX240 Router) on page 287
show chassis environment fpc (MX480 Router) on page 288
show chassis environment fpc (MX960 Router MPC10E-15C-MRATE) on page 289
show chassis environment fpc (MX960 Router) on page 292
show chassis environment fpc (MX480 Router with 100-Gigabit Ethernet
CFP) on page 293
show chassis environment fpc (MX240, MX480, MX960 with Application Services
Modular Line Card on page 294
show chassis environment fpc (MX10003 Router) on page 295
show chassis environment fpc (MX204 Router) on page 298
show chassis environment fpc (MX10008 Router) on page 298
show chassis environment fpc (T320, T640, and T1600 Routers) on page 306
show chassis environment fpc (T4000 Router) on page 306
show chassis environment fpc lcc (TX Matrix Router) on page 311
show chassis environment fpc lcc (TX Matrix Plus Router) on page 312
show chassis environment fpc (QFX Series and OCX Series) on page 313
show chassis environment fpc interconnect-device (QFabric Systems) on page 313
show chassis environment fpc 5(PTX3000 Packet Transport Router) on page 313
show chassis environment fpc 0 (PTX5000 Packet Transport Router) on page 314
show chassis environment fpc 07 (PTX5000 Packet Transport Router with
FPC2-PTX-P1A) on page 315
show chassis environment fpc (PTX10008 router) on page 316
show chassis environment fpc (PTX10016 router) on page 319
show chassis environment FPC 1 (MX Routers with Media Services Blade
[MSB]) on page 323
show chassis environment FPC (Junos OS Evolved) on page 323
Output Fields Table 10 on page 275 lists the output fields for the show chassis environment fpc command.
Output fields are listed in the approximate order in which they appear.
Temperature (M40e and M160 routers and QFX Series only) Temperature of the air flowing past the FPC.
PMB Temperature (PTX Series only) Temperature of the air flowing past the PMB (bottom of the FPC).
The PTX5000 Packet Transport Router with FPC2-PTX-P1A include multiple temperatures for PMB
(TEMP0 and TEMP1).
PMB CPU Temperature (PTX5000 Packet Transport Router with FPC2-PTX-P1A only) Temperature of the air flowing past
the PMB CPU.
Temperature Intake (M320 routers, MX2010 routers, MX2020 routers, MX2008 routers, and PTX Series only) Temperature
of the air flowing into the chassis.
Temperature Top (T Series routers only) Temperature of the air flowing past the top of the FPC.
Temperature Exhaust (M120 and M320 routers, MX2010 routers, MX2020 routers, MX2008 routers, and PTX Series only)
Temperature of the air flowing out of the chassis.
The PTX Series Packet Transport Routers, and the MX2010, MX2020, and MX2008 routers include
exhaust temperatures for multiple zones (Exhaust A and Exhaust B).
Temperature Bottom (T Series routers only) Temperature of the air flowing past the bottom of the FPC.
TL n Temperature (PTX Series only) Temperature of the air flowing past the specified TL area of the packet forwarding
engine (PFE) on the FPC.
TQ n Temperature (PTX Series only) Temperature of the air flowing past the specified TQ area of the packet forwarding
engine (PFE) on the FPC.
Temperature MMBO (T640 router only) Temperature of the air flowing past the type 3 FPC.
Temperature MMB1 (M320 and T Series routers only) Temperature of the air flowing past the type 1, type 2, and type 3
FPC.
Power Information about the voltage supplied to the FPC. The left column displays the required power, in
volts. The right column displays the measured power, in millivolts.
CMB Revision or BUS Revision level of the chassis management bus device (M Series router) or bus (T Series routers).
revision
Sample Output
FPC 2 status:
State Online
Temperature Exhaust A 32 degrees C / 89 degrees F
Temperature Exhaust B 31 degrees C / 87 degrees F
Power A-Board
1.2 V 1202 mV
1.5 V 1508 mV
1.8 V 1798 mV
2.5 V 2507 mV
3.3 V 3351 mV
5.0 V 4995 mV
3.3 V bias 3296 mV
1.2 V Rocket IO 1205 mV
1.5 V Rocket IO 1501 mV
I2C Slave Revision 12
FPC 3 status:
State Online
Temperature Exhaust A 31 degrees C / 87 degrees F
Temperature Exhaust B 33 degrees C / 91 degrees F
Power A-Board
1.2 V 1211 mV
1.5 V 1501 mV
1.8 V 1798 mV
2.5 V 2471 mV
3.3 V 3293 mV
5.0 V 4930 mV
3.3 V bias 3296 mV
1.2 V Rocket IO 1205 mV
1.5 V Rocket IO 1501 mV
Power B-Board
1.2 V 1214 mV
1.5 V 1501 mV
2.5 V 2471 mV
3.3 V 3300 mV
5.0 V 4943 mV
3.3 V bias 3296 mV
1.2 V Rocket IO 1205 mV
1.5 V Rocket IO 1501 mV
I2C Slave Revision 12
FPC 4 status:
State Online
Temperature Exhaust A 32 degrees C / 89 degrees F
Temperature Exhaust B 30 degrees C / 86 degrees F
Power A-Board
1.2 V 1195 mV
1.5 V 1504 mV
1.8 V 1801 mV
2.5 V 2504 mV
3.3 V 3293 mV
5.0 V 4917 mV
3.3 V bias 3296 mV
1.2 V Rocket IO 1202 mV
1.5 V Rocket IO 1492 mV
I2C Slave Revision 12
FPC 0 status:
State Online
Temperature 42 degrees C / 107 degrees F
Power:
1.5 V 1500 mV
2.5 V 2509 mV
3.3 V 3308 mV
5.0 V 4991 mV
5.0 V bias 4952 mV
8.0 V bias 8307 mV
CMB Revision 12
FPC 1 status:
State Online
Temperature 45 degrees C / 113 degrees F
Power:
1.5 V 1498 mV
2.5 V 2501 mV
3.3 V 3319 mV
5.0 V 5020 mV
5.0 V bias 5025 mV
8.0 V bias 8307 mV
CMB Revision 12
FPC 0 status:
State Online
Temperature Intake 27 degrees C / 80 degrees F
Temperature Exhaust 38 degrees C / 100 degrees F
Temperature MMB1 31 degrees C / 87 degrees F
Power:
1.5 V 1487 mV
1.5 V * 1494 mV
1.8 V 1821 mV
2.5 V 2533 mV
3.3 V 3323 mV
5.0 V 5028 mV
3.3 V bias 3296 mV
5.0 V bias 4984 mV
CMB Revision 16
FPC 1 status:
State Online
Temperature Intake 27 degrees C / 80 degrees F
Temperature Exhaust 37 degrees C / 98 degrees F
FPC 0 status:
State Online
Temperature Intake 41 degrees C / 105 degrees F
Temperature Exhaust A 48 degrees C / 118 degrees F
Temperature Exhaust B 60 degrees C / 140 degrees F
Temperature LU 0 TSen 56 degrees C / 132 degrees F
Temperature LU 0 Chip 59 degrees C / 138 degrees F
Temperature LU 1 TSen 56 degrees C / 132 degrees F
Temperature LU 1 Chip 61 degrees C / 141 degrees F
Temperature LU 2 TSen 56 degrees C / 132 degrees F
Temperature LU 2 Chip 52 degrees C / 125 degrees F
Temperature LU 3 TSen 56 degrees C / 132 degrees F
Temperature LU 3 Chip 52 degrees C / 125 degrees F
Temperature MQ 0 TSen 49 degrees C / 120 degrees F
Temperature MQ 0 Chip 49 degrees C / 120 degrees F
Temperature MQ 1 TSen 49 degrees C / 120 degrees F
Temperature MQ 1 Chip 52 degrees C / 125 degrees F
Temperature MQ 2 TSen 49 degrees C / 120 degrees F
Temperature MQ 2 Chip 45 degrees C / 113 degrees F
Temperature MQ 3 TSen 49 degrees C / 120 degrees F
Temperature MQ 3 Chip 46 degrees C / 114 degrees F
Power
AS-BIAS3V3-zl2105 3299 mV
AS-VDD1V8-zl2006 1807 mV
AS-VDD2V5-zl2006 2512 mV
AS-AVDD1V0-zl2004 997 mV
AS-PCIE_1V0-zl2004 996 mV
AS-VDD3V3-zl2004 3294 mV
AS-VDD_1V5A-zl2004 1501 mV
AS-VDD_1V5B-zl2004 1498 mV
AS-LU0_1V0-zl2004 998 mV
AS-LU1_1V0-zl2004 1002 mV
AS-MQ0_1V0-zl2004 999 mV
AS-MQ1_1V0-zl2004 994 mV
AS-LU2_1V0-zl2004 1000 mV
AS-LU3_1V0-zl2004 998 mV
AS-MQ2_1V0-zl2004 1002 mV
AS-MQ3_1V0-zl2004 999 mV
AS-PMB_1V1-zl2006 1096 mV
I2C Slave Revision 68
FPC 1 status:
State Online
Temperature Intake 39 degrees C / 102 degrees F
Temperature Exhaust A 48 degrees C / 118 degrees F
Temperature Exhaust B 55 degrees C / 131 degrees F
Temperature LU 0 TSen 52 degrees C / 125 degrees F
Temperature LU 0 Chip 54 degrees C / 129 degrees F
Temperature LU 1 TSen 52 degrees C / 125 degrees F
Temperature LU 1 Chip 56 degrees C / 132 degrees F
Temperature LU 2 TSen 52 degrees C / 125 degrees F
Temperature LU 2 Chip 49 degrees C / 120 degrees F
Temperature LU 3 TSen 52 degrees C / 125 degrees F
Temperature LU 3 Chip 50 degrees C / 122 degrees F
Temperature MQ 0 TSen 48 degrees C / 118 degrees F
Temperature MQ 0 Chip 48 degrees C / 118 degrees F
Temperature MQ 1 TSen 48 degrees C / 118 degrees F
Temperature MQ 1 Chip 51 degrees C / 123 degrees F
Temperature MQ 2 TSen 48 degrees C / 118 degrees F
Temperature MQ 2 Chip 45 degrees C / 113 degrees F
Temperature MQ 3 TSen 48 degrees C / 118 degrees F
Temperature MQ 3 Chip 45 degrees C / 113 degrees F
Power
AS-BIAS3V3-zl2105 3291 mV
AS-VDD1V8-zl2006 1786 mV
AS-VDD2V5-zl2006 2496 mV
AS-AVDD1V0-zl2004 1000 mV
AS-PCIE_1V0-zl2004 1000 mV
AS-VDD3V3-zl2004 3294 mV
AS-VDD_1V5A-zl2004 1500 mV
AS-VDD_1V5B-zl2004 1498 mV
AS-LU0_1V0-zl2004 1003 mV
AS-LU1_1V0-zl2004 1000 mV
AS-MQ0_1V0-zl2004 1000 mV
AS-MQ1_1V0-zl2004 995 mV
AS-LU2_1V0-zl2004 1002 mV
AS-LU3_1V0-zl2004 997 mV
AS-MQ2_1V0-zl2004 1000 mV
AS-MQ3_1V0-zl2004 998 mV
AS-PMB_1V1-zl2006 1096 mV
I2C Slave Revision 68
FPC 2 status:
State Online
Temperature Intake 39 degrees C / 102 degrees F
Temperature Exhaust A 48 degrees C / 118 degrees F
Temperature Exhaust B 58 degrees C / 136 degrees F
Temperature LU 0 TSen 55 degrees C / 131 degrees F
Temperature LU 0 Chip 57 degrees C / 134 degrees F
AS-VDD3V3-zl2004 3294 mV
AS-VDD_1V5A-zl2004 1500 mV
AS-VDD_1V5B-zl2004 1498 mV
AS-LU0_1V0-zl2004 998 mV
AS-LU1_1V0-zl2004 998 mV
AS-MQ0_1V0-zl2004 999 mV
AS-MQ1_1V0-zl2004 998 mV
AS-LU2_1V0-zl2004 1000 mV
AS-LU3_1V0-zl2004 1001 mV
AS-MQ2_1V0-zl2004 996 mV
AS-MQ3_1V0-zl2004 998 mV
AS-PMB_1V1-zl2006 1098 mV
I2C Slave Revision 68
FPC 4 status:
...
FPC 0 status:
State Online
Temperature Intake 36 degrees C / 96 degrees F
Temperature Exhaust A 42 degrees C / 107 degrees F
Temperature Exhaust B 51 degrees C / 123 degrees F
Temperature LU 0 TSen 49 degrees C / 120 degrees F
Temperature LU 0 Chip 50 degrees C / 122 degrees F
Temperature LU 1 TSen 49 degrees C / 120 degrees F
Temperature LU 1 Chip 54 degrees C / 129 degrees F
Temperature LU 2 TSen 49 degrees C / 120 degrees F
Temperature LU 2 Chip 45 degrees C / 113 degrees F
Temperature LU 3 TSen 49 degrees C / 120 degrees F
Temperature LU 3 Chip 46 degrees C / 114 degrees F
Temperature MQ 0 TSen 40 degrees C / 104 degrees F
Temperature MQ 0 Chip 41 degrees C / 105 degrees F
Temperature MQ 1 TSen 40 degrees C / 104 degrees F
Temperature MQ 1 Chip 44 degrees C / 111 degrees F
Temperature MQ 2 TSen 40 degrees C / 104 degrees F
Temperature MQ 2 Chip 38 degrees C / 100 degrees F
Temperature MQ 3 TSen 40 degrees C / 104 degrees F
Temperature MQ 3 Chip 41 degrees C / 105 degrees F
Power
AS-BIAS3V3-zl2105 3300 mV
AS-VDD1V8-zl2006 1805 mV
AS-VDD2V5-zl2006 2505 mV
AS-AVDD1V0-zl2004 998 mV
AS-PCIE_1V0-zl2004 999 mV
AS-VDD3V3-zl2004 3303 mV
AS-VDD_1V5A-zl2004 1497 mV
AS-VDD_1V5B-zl2004 1497 mV
AS-LU0_1V0-zl2004 998 mV
AS-LU1_1V0-zl2004 1003 mV
AS-MQ0_1V0-zl2004 998 mV
AS-MQ1_1V0-zl2004 998 mV
AS-LU2_1V0-zl2004 997 mV
AS-LU3_1V0-zl2004 1001 mV
AS-MQ2_1V0-zl2004 996 mV
AS-MQ3_1V0-zl2004 994 mV
AS-PMB_1V1-zl2006 1097 mV
I2C Slave Revision 68
FPC 1 status:
State Online
Temperature Intake 34 degrees C / 93 degrees F
Temperature Exhaust A 46 degrees C / 114 degrees F
Temperature Exhaust B 54 degrees C / 129 degrees F
Temperature LU 0 TSen 45 degrees C / 113 degrees F
Temperature LU 0 Chip 55 degrees C / 131 degrees F
Temperature LU 1 TSen 45 degrees C / 113 degrees F
Temperature LU 1 Chip 44 degrees C / 111 degrees F
Temperature LU 2 TSen 45 degrees C / 113 degrees F
Temperature LU 2 Chip 50 degrees C / 122 degrees F
Temperature LU 3 TSen 45 degrees C / 113 degrees F
Temperature LU 3 Chip 58 degrees C / 136 degrees F
Temperature XM 0 TSen 45 degrees C / 113 degrees F
Temperature XM 0 Chip 51 degrees C / 123 degrees F
Temperature XF 0 TSen 45 degrees C / 113 degrees F
Temperature XF 0 Chip 63 degrees C / 145 degrees F
Temperature PLX Switch TSen45 degrees C / 113 degrees F
Temperature PLX Switch Chip47 degrees C / 116 degrees F
Power
MPC-BIAS3V3-zl2105 3300 mV
MPC-VDD3V3-zl6100 3294 mV
MPC-VDD2V5-zl6100 2505 mV
MPC-VDD1V8-zl2004 1796 mV
MPC-AVDD1V0-zl2004 991 mV
MPC-VDD1V2-zl6100 1196 mV
MPC-VDD1V5A-zl2004 1491 mV
MPC-VDD1V5B-zl2004 1492 mV
MPC-XF_0V9-zl2004 996 mV
MPC-PCIE_1V0-zl6100 1003 mV
MPC-LU0_1V0-zl2004 996 mV
MPC-LU1_1V0-zl2004 996 mV
MPC-LU2_1V0-zl2004 998 mV
MPC-LU3_1V0-zl2004 994 mV
MPC-12VA-BMR453 12031 mV
MPC-12VB-BMR453 12003 mV
MPC-PMB_1V1-zl2006 1104 mV
MPC-PMB_1V2-zl2106 1194 mV
MPC-XM_0V9-vt273m 911 mV
I2C Slave Revision 110
FPC 8 status:
State Online
Temperature Intake 32 degrees C / 89 degrees F
Temperature Exhaust A 44 degrees C / 111 degrees F
Temperature Exhaust B 37 degrees C / 98 degrees F
Temperature LU 0 TCAM TSen 41 degrees C / 105 degrees F
Temperature LU 0 TCAM Chip 49 degrees C / 120 degrees F
Temperature LU 0 TSen 41 degrees C / 105 degrees F
Temperature LU 0 Chip 52 degrees C / 125 degrees F
Temperature MQ 0 TSen 41 degrees C / 105 degrees F
Temperature MQ 0 Chip 47 degrees C / 116 degrees F
Temperature LU 1 TCAM TSen 39 degrees C / 102 degrees F
Temperature LU 1 TCAM Chip 42 degrees C / 107 degrees F
Temperature LU 1 TSen 39 degrees C / 102 degrees F
Temperature LU 1 Chip 46 degrees C / 114 degrees F
Temperature MQ 1 TSen 39 degrees C / 102 degrees F
Temperature MQ 1 Chip 45 degrees C / 113 degrees F
Power
MPC-BIAS3V3-zl2105 3296 mV
MPC-VDD3V3-zl2006 3298 mV
MPC-VDD2V5-zl2006 2505 mV
MPC-TCAM_1V0-zl2004 997 mV
MPC-AVDD1V0-zl2006 1007 mV
MPC-VDD1V8-zl2006 1803 mV
MPC-PCIE_1V0-zl2006 1004 mV
MPC-LU0_1V0-zl2004 1000 mV
MPC-MQ0_1V0-zl2004 999 mV
MPC-VDD_1V5-zl2004 1498 mV
MPC-PMB_1V1-zl2006 1102 mV
MPC-9VA-BMR453 9009 mV
MPC-9VB-BMR453 8960 mV
MPC-PMB_1V2-zl2105 1202 mV
MPC-LU1_1V0-zl2004 1005 mV
MPC-MQ1_1V0-zl2004 1000 mV
I2C Slave Revision 70
FPC 9 status:
State Online
Temperature Intake 34 degrees C / 93 degrees F
Temperature Exhaust A 41 degrees C / 105 degrees F
Temperature Exhaust B 54 degrees C / 129 degrees F
Temperature LU 0 TSen 51 degrees C / 123 degrees F
Temperature LU 0 Chip 52 degrees C / 125 degrees F
Temperature LU 1 TSen 51 degrees C / 123 degrees F
Temperature LU 1 Chip 55 degrees C / 131 degrees F
Temperature LU 2 TSen 51 degrees C / 123 degrees F
Temperature LU 2 Chip 47 degrees C / 116 degrees F
Temperature LU 3 TSen 51 degrees C / 123 degrees F
Temperature LU 3 Chip 47 degrees C / 116 degrees F
Temperature MQ 0 TSen 40 degrees C / 104 degrees F
Temperature MQ 0 Chip 42 degrees C / 107 degrees F
Temperature MQ 1 TSen 40 degrees C / 104 degrees F
Temperature MQ 1 Chip 44 degrees C / 111 degrees F
Temperature MQ 2 TSen 40 degrees C / 104 degrees F
Temperature MQ 2 Chip 38 degrees C / 100 degrees F
Temperature MQ 3 TSen 40 degrees C / 104 degrees F
Temperature MQ 3 Chip 40 degrees C / 104 degrees F
Power
AS-BIAS3V3-zl2105 3302 mV
AS-VDD1V8-zl2006 1808 mV
AS-VDD2V5-zl2006 2513 mV
AS-AVDD1V0-zl2004 997 mV
AS-PCIE_1V0-zl2004 999 mV
AS-VDD3V3-zl2004 3294 mV
AS-VDD_1V5A-zl2004 1503 mV
AS-VDD_1V5B-zl2004 1502 mV
AS-LU0_1V0-zl2004 996 mV
AS-LU1_1V0-zl2004 999 mV
AS-MQ0_1V0-zl2004 997 mV
AS-MQ1_1V0-zl2004 999 mV
AS-LU2_1V0-zl2004 997 mV
AS-LU3_1V0-zl2004 998 mV
AS-MQ2_1V0-zl2004 1000 mV
AS-MQ3_1V0-zl2004 1000 mV
AS-PMB_1V1-zl2006 1102 mV
I2C Slave Revision 68
FPC 0 status:
State Online
Temperature Intake 29 degrees C / 84 degrees F
Temperature Exhaust A 43 degrees C / 109 degrees F
Temperature Exhaust B 42 degrees C / 107 degrees F
Temperature XL 0 TSen 38 degrees C / 100 degrees F
Temperature XL 0 Chip 53 degrees C / 127 degrees F
Temperature XL 0 XR2 0 TSen38 degrees C / 100 degrees F
Temperature XL 0 XR2 0 Chip60 degrees C / 140 degrees F
Temperature XL 0 XR2 1 TSen38 degrees C / 100 degrees F
Temperature XL 0 XR2 1 Chip60 degrees C / 140 degrees F
Temperature XL 1 TSen 30 degrees C / 86 degrees F
Temperature XL 1 Chip 43 degrees C / 109 degrees F
Temperature XL 1 XR2 0 TSen30 degrees C / 86 degrees F
Temperature XL 1 XR2 0 Chip50 degrees C / 122 degrees F
Temperature XL 1 XR2 1 TSen30 degrees C / 86 degrees F
Temperature XL 1 XR2 1 Chip50 degrees C / 122 degrees F
Temperature XM 0 TSen 42 degrees C / 107 degrees F
Temperature XM 0 Chip 49 degrees C / 120 degrees F
Temperature XM 1 TSen 42 degrees C / 107 degrees F
Temperature XM 1 Chip 42 degrees C / 107 degrees F
Temperature XM 2 TSen 42 degrees C / 107 degrees F
Temperature XM 2 Chip 42 degrees C / 107 degrees F
Temperature XM 3 TSen 42 degrees C / 107 degrees F
Temperature XM 3 Chip 40 degrees C / 104 degrees F
Temperature PCIe Switch TSen42 degrees C / 107 degrees F
Temperature PCIe Switch Chip22 degrees C / 71 degrees F
Power
MPC-VDD_3V3-vt273m 3304 mV
MPC-VDD_2V5-vt273m 2503 mV
MPC-VDD_1V5-vt273m 1499 mV
MPC-PCIE_0V9-vt273m 900 mV
MPC-VDD_1V8-vt273m 1799 mV
MPC-VDD_1V2-vt273m 1203 mV
MPC-XM01_AVDD_1V0-vt273 1001 mV
MPC-XM23_AVDD_1V0-vt273 1001 mV
MPC-XM0_0V9-vt273m 900 mV
MPC-XM1_0V9-vt273m 901 mV
MPC-XM2_0V9-vt273m 903 mV
MPC-XM3_0V9-vt273m 899 mV
MPC-XL0_XR0_0V9-vt273m 899 mV
MPC-XL0_XR1_0V9-vt273m 903 mV
MPC-XL0_0V9-vt273m 899 mV
MPC-XL0_AVDD_1V0-vt273m 1000 mV
MPC-XL0_VDD_1V5-vt273m 1498 mV
MPC-XL0_XR_1V2-vt273m 1200 mV
MPC-XL1_XR0_0V9-vt273m 899 mV
MPC-XL1_XR1_0V9-vt273m 899 mV
MPC-XL1_0V9-vt273m 900 mV
MPC-XL1_AVDD_1V0-vt273m 1000 mV
MPC-XL1_VDD_1V5-vt273m 1501 mV
MPC-XL1_XR_1V2-vt273m 1199 mV
MPC-PMB-1V05-ltc2978 1049 mV
MPC-PMB-1V5-ltc2978 1500 mV
MPC-PMB-2V5-ltc2978 2500 mV
MPC-PMB-3V3-ltc2978 3298 mV
I2C Slave Revision 20
FPC 1 status:
State Online
Temperature Intake 29 degrees C / 84 degrees F
MAX20731-EA0-1V2 1189 mV
MAX20731-EA0-HMC-1V2 1182 mV
MAX20731-EA0-0V906 899 mV
MAX20731-EA0-HMC-0V9 891 mV
MAX20751-EA1-AVDD1V0 1000 mV
MAX20731-EA1-1V2 1189 mV
MAX20731-EA1-HMC-1V2 1182 mV
MAX20731-EA1-0V906 899 mV
MAX20731-EA1-HMC-0V9 889 mV
MAX20751-EA2-AVDD1V0 1000 mV
MAX20731-EA2-1V2 1186 mV
MAX20731-EA2-HMC-1V2 1193 mV
MAX20731-EA2-0V906 899 mV
MAX20731-EA2-HMC-0V9 889 mV
MAX20751-EA3-AVDD1V0 1000 mV
MAX20731-EA3-1V2 1186 mV
MAX20731-EA3-HMC-1V2 1193 mV
MAX20731-EA3-0V906 897 mV
MAX20731-EA3-HMC-0V9 894 mV
MAX20731-3V3 3268 mV
UCD9090_0-CH_1-EA0_PLL_ 1010 mV
UCD9090_0-CH_2-EA0_1V04 1038 mV
UCD9090_0-CH_3-EA0_2V5 2499 mV
UCD9090_0-CH_4-EA0_1V5 1494 mV
UCD9090_0-CH_5-EA1_PLL_ 1012 mV
UCD9090_0-CH_6-EA1_1V04 1038 mV
UCD9090_0-CH_7-EA1_2V5 2497 mV
UCD9090_0-CH_8-EA1_1V5 1498 mV
UCD9090_0-CH_9-VDD_1V8 1804 mV
UCD9090_0-CH_10-VDD_2V5 2499 mV
UCD9090_1-CH_1-EA2_PLL_ 1017 mV
UCD9090_1-CH_2-EA2_1V04 1041 mV
UCD9090_1-CH_3-EA2_2V5 2499 mV
UCD9090_1-CH_4-EA2_1V5 1503 mV
UCD9090_1-CH_5-EA3_PLL_ 1015 mV
UCD9090_1-CH_6-EA3_1V04 1048 mV
UCD9090_1-CH_7-EA3_2V5 2499 mV
UCD9090_1-CH_8-EA3_1V5 1500 mV
UCD9090_1-CH_9-VDD_1V5 1497 mV
UCD9090_1-CH_10-VDD_1V2 1216 mV
PMB PVCC 0.7V - 1.05V 802 mV
PMB PVNN 0V - 1.02V 976 mV
PMB 1.0V 1002 mV
PMB 1.1V 1076 mV
PMB 1.35V 1347 mV
PMB VDDQ 1.5V 1504 mV
PMB 1.8V 1804 mV
PMB VDD 3.3V 3292 mV
PMB BIAS 5.0V 5008 mV
PMB USB 5.0V 5000 mV
PMB 12V 10866 mV
I2C Slave Revision 112
FPC 7 status:
State Online
Temperature Intake 31 degrees C / 87 degrees F
Temperature Exhaust A 46 degrees C / 114 degrees F
Temperature Exhaust B 38 degrees C / 100 degrees F
Temperature QX 0 TSen 49 degrees C / 120 degrees F
Temperature QX 0 Chip 52 degrees C / 125 degrees F
Temperature LU 0 TCAM TSen 49 degrees C / 120 degrees F
FPC 1 status:
State Online
Temperature Intake 34 degrees C / 93 degrees F
Temperature Exhaust A 39 degrees C / 102 degrees F
Temperature Exhaust B 53 degrees C / 127 degrees F
Temperature I3 0 TSensor 51 degrees C / 123 degrees F
Temperature I3 0 Chip 54 degrees C / 129 degrees F
Temperature I3 1 TSensor 50 degrees C / 122 degrees F
Temperature I3 1 Chip 53 degrees C / 127 degrees F
Temperature I3 2 TSensor 48 degrees C / 118 degrees F
Temperature I3 2 Chip 51 degrees C / 123 degrees F
Temperature I3 3 TSensor 45 degrees C / 113 degrees F
Temperature I3 3 Chip 48 degrees C / 118 degrees F
Temperature IA 0 TSensor 45 degrees C / 113 degrees F
Temperature IA 0 Chip 45 degrees C / 113 degrees F
Temperature IA 1 TSensor 45 degrees C / 113 degrees F
Temperature IA 1 Chip 49 degrees C / 120 degrees F
Power
1.5 V 1492 mV
2.5 V 2507 mV
3.3 V 3306 mV
1.8 V PFE 0 1801 mV
FPC 1 status:
State Online
Temperature Intake 36 degrees C / 96 degrees F
Temperature Exhaust A 41 degrees C / 105 degrees F
Temperature Exhaust B 55 degrees C / 131 degrees F
Temperature I3 0 TSensor 55 degrees C / 131 degrees F
Temperature I3 0 Chip 57 degrees C / 134 degrees F
Temperature I3 1 TSensor 53 degrees C / 127 degrees F
Temperature I3 1 Chip 53 degrees C / 127 degrees F
Temperature I3 2 TSensor 52 degrees C / 125 degrees F
Temperature I3 2 Chip 49 degrees C / 120 degrees F
Temperature I3 3 TSensor 47 degrees C / 116 degrees F
Temperature I3 3 Chip 47 degrees C / 116 degrees F
Temperature IA 0 TSensor 54 degrees C / 129 degrees F
Temperature IA 0 Chip 58 degrees C / 136 degrees F
Temperature IA 1 TSensor 48 degrees C / 118 degrees F
Temperature IA 1 Chip 53 degrees C / 127 degrees F
Power
1.5 V 1479 mV
2.5 V 2542 mV
3.3 V 3319 mV
1.8 V PFE 0 1811 mV
1.8 V PFE 1 1804 mV
1.8 V PFE 2 1804 mV
1.8 V PFE 3 1814 mV
1.2 V PFE 0 1192 mV
1.2 V PFE 1 1202 mV
1.2 V PFE 2 1205 mV
1.2 V PFE 3 1189 mV
I2C Slave Revision 40
FPC 8 status:
State Online
Temperature Intake 37 degrees C / 98 degrees F
Power
PIM4820 56967 mV
BMR456-12V-BRICK-A 12016 mV
BMR456-12V-BRICK-B 12039 mV
MAX20743-RT01-DVDD 724 mV
MAX20743-RT234-DVDD 724 mV
MAX20743-RT567-DVDD 724 mV
MAX20754-ZT0-VDD 750 mV
MAX20754-ZT0-VDDM 799 mV
MAX20743-ZT0-AVDD 904 mV
MAX20730-ZT0-AVDDH 1103 mV
MAX20730-ZT0-HBM-VDDQ 1198 mV
MAX20730-ZT0-HBM-VDDC 1202 mV
MAX20730-VDD-1V25 1246 mV
MAX20754-ZT1-VDD 724 mV
MAX20754-ZT1-VDDM 800 mV
MAX20743-ZT1-AVDD 904 mV
MAX20730-ZT1-AVDDH 1103 mV
MAX20730-ZT1-HBM-VDDQ 1202 mV
MAX20730-ZT1-HBM-VDDC 1198 mV
MAX20730-PCIE-0V9 901 mV
MAX20754-ZT2-VDD 724 mV
MAX20754-ZT2-VDDM 799 mV
MAX20743-ZT2-AVDD 904 mV
MAX20730-ZT2-AVDDH 1103 mV
MAX20730-ZT2-HBM-VDDQ 1198 mV
MAX20730-ZT2-HBM-VDDC 1198 mV
MAX20730-VDD3V3 3308 mV
MAX20754-WAN-VDD3V3 3301 mV
MAX20754-WAN-DVDD0V8 799 mV
MAX20743-WAN-VDD1V0A 1003 mV
MAX20743-WAN-AVDD0V8 800 mV
MAX20743-WAN-VDD1V0C 1003 mV
TPS53631-1V2-VDDQ-PMB 1225 mV
TPS53641-VCCIN-PMB 1770 mV
TPS53641-VCCSBUS-PMB 1040 mV
MAX20730-BIAS3P30-PMB 3308 mV
MAX20730-BIAS5P0-PMB 5063 mV
MAX20730-VPP-V2P5-PMB 2503 mV
MAX20730-VDD1V2 1195 mV
MAX20730-VDD1V5 1496 mV
MAX20730-VDD1V8 1799 mV
MAX20730-VDD2V5 2511 mV
MAX20754-RT-AVDD-0V8 800 mV
MAX20743-XGE-VDD-AVS 1012 mV
PMB VCC1P05_PCH_SW 1048 mV
PMB VCC1P3 1294 mV
PMB VCC1P5 1485 mV
PMB VCC1P7 1705 mV
PMB DDR4_VPP 2519 mV
PMB VCC3P3 3336 mV
PMB VCC3P3_PCH 3332 mV
I2C Slave Revision 124
FPC 5 status:
State Online
Temperature Intake 27 degrees C / 80 degrees F
Temperature Exhaust A 34 degrees C / 93 degrees F
Temperature Exhaust B 40 degrees C / 104 degrees F
Temperature I3 0 TSensor 39 degrees C / 102 degrees F
Temperature I3 0 Chip 41 degrees C / 105 degrees F
Temperature I3 1 TSensor 38 degrees C / 100 degrees F
Temperature I3 1 Chip 37 degrees C / 98 degrees F
Temperature I3 2 TSensor 37 degrees C / 98 degrees F
Temperature I3 2 Chip 34 degrees C / 93 degrees F
Temperature I3 3 TSensor 32 degrees C / 89 degrees F
Temperature I3 3 Chip 33 degrees C / 91 degrees F
Temperature IA 0 TSensor 39 degrees C / 102 degrees F
Temperature IA 0 Chip 44 degrees C / 111 degrees F
Temperature IA 1 TSensor 36 degrees C / 96 degrees F
Temperature IA 1 Chip 44 degrees C / 111 degrees F
Power
1.5 V 1479 mV
2.5 V 2523 mV
3.3 V 3254 mV
1.8 V PFE 0 1798 mV
1.8 V PFE 1 1798 mV
1.8 V PFE 2 1807 mV
1.8 V PFE 3 1791 mV
1.2 V PFE 0 1173 mV
1.2 V PFE 1 1179 mV
show chassis environment fpc (MX480 Router with 100-Gigabit Ethernet CFP)
user@host> show chassis environment fpc
FPC 0 status:
State Online
Temperature Intake 32 degrees C / 89 degrees F
Temperature Exhaust A 39 degrees C / 102 degrees F
Temperature Exhaust B 37 degrees C / 98 degrees F
Temperature QX 0 TSen 44 degrees C / 111 degrees F
Temperature QX 0 Chip 48 degrees C / 118 degrees F
Temperature LU 0 TCAM TSen 44 degrees C / 111 degrees F
Temperature LU 0 TCAM Chip 47 degrees C / 116 degrees F
Temperature LU 0 TSen 44 degrees C / 111 degrees F
Temperature LU 0 Chip 48 degrees C / 118 degrees F
Temperature MQ 0 TSen 44 degrees C / 111 degrees F
Temperature MQ 0 Chip 47 degrees C / 116 degrees F
Power
MPC-BIAS3V3-zl2105 3297 mV
MPC-VDD3V3-zl2105 3306 mV
MPC-VDD2V5-zl2105 2498 mV
MPC-TCAM_1V0-zl2004 999 mV
MPC-AVDD1V0-zl2006 999 mV
MPC-VDD1V8-zl2006 1796 mV
MPC-PCIE_1V0-zl2006 1002 mV
MPC-LU0_1V0-zl2004 997 mV
MPC-MQ0_1V0-zl2004 995 mV
MPC-VDD_1V5-zl2004 1496 mV
MPC-PMB_1V1-zl2006 1094 mV
MPC-9VA-BMR453 9054 mV
MPC-9VB-BMR453 9037 mV
MPC-PMB_1V2-zl2106 1191 mV
MPC-QXM0_1V0-zl2006 1000 mV
I2C Slave Revision 66
FPC 1 status:
State Online
Temperature Intake 35 degrees C / 95 degrees F
Temperature Exhaust A 50 degrees C / 122 degrees F
Temperature Exhaust B 56 degrees C / 132 degrees F
Temperature LU 0 TSen 46 degrees C / 114 degrees F
Temperature LU 0 Chip 59 degrees C / 138 degrees F
Temperature LU 1 TSen 46 degrees C / 114 degrees F
Temperature LU 1 Chip 45 degrees C / 113 degrees F
Temperature LU 2 TSen 46 degrees C / 114 degrees F
Temperature LU 2 Chip 60 degrees C / 140 degrees F
Temperature LU 3 TSen 46 degrees C / 114 degrees F
Temperature LU 3 Chip 71 degrees C / 159 degrees F
Temperature XM 0 TSen 46 degrees C / 114 degrees F
Temperature XM 0 Chip -18 degrees C / 0 degrees F
Temperature XF 0 TSen 46 degrees C / 114 degrees F
Temperature XF 0 Chip 76 degrees C / 168 degrees F
Power
MPC-BIAS3V3-zl2105 3292 mV
MPC-VDD3V3-zl6100 3303 mV
MPC-VDD2V5-zl6100 2501 mV
MPC-VDD1V8-zl2004 1801 mV
MPC-AVDD1V0-zl2006 996 mV
MPC-VDD1V2-zl6100 1199 mV
MPC-VDD1V5A-zl2004 1493 mV
MPC-VDD1V5B-zl2004 1498 mV
MPC-XF_0V9-zl2006 996 mV
MPC-PCIE_1V0-zl6100 1000 mV
MPC-LU0_1V0-zl2004 994 mV
MPC-LU1_1V0-zl2004 994 mV
MPC-LU2_1V0-zl2004 992 mV
MPC-LU3_1V0-zl2004 993 mV
MPC-12VA-BMR453 12003 mV
MPC-12VB-BMR453 12043 mV
MPC-PMB_1V1-zl2006 1091 mV
MPC-PMB_1V2-zl2106 1196 mV
MPC-XM_0V9-vt273m 899 mV
I2C Slave Revision 106
show chassis environment fpc (MX240, MX480, MX960 with Application Services Modular Line Card
user@host>show chassis environment fpc 1
FPC 1 status:
State Online
Temperature Intake 36 degrees C / 96 degrees F
Temperature Exhaust A 39 degrees C / 102 degrees F
Temperature LU TSen 52 degrees C / 125 degrees F
Temperature LU Chip 54 degrees C / 129 degrees F
Temperature XM TSen 52 degrees C / 125 degrees F
Temperature XM Chip 60 degrees C / 140 degrees F
Temperature PCIe TSen 52 degrees C / 125 degrees F
FPC 0 status:
State Online
FPC 0 Intake Temp Sensor 29 degrees C / 84 degrees F
FPC 0 Exhaust-A Temp Sensor56 degrees C / 132 degrees F
FPC 0 Exhaust-B Temp Sensor44 degrees C / 111 degrees F
FPC 0 EA0 Chip 58 degrees C / 136 degrees F
FPC 0 EA0-XR0 Chip 61 degrees C / 141 degrees F
FPC 0 EA0-XR1 Chip 62 degrees C / 143 degrees F
FPC 0 EA1 Chip 67 degrees C / 152 degrees F
FPC 0 EA1-XR0 Chip 72 degrees C / 161 degrees F
FPC 0 EA1-XR1 Chip 72 degrees C / 161 degrees F
FPC 0 PEX Chip 77 degrees C / 170 degrees F
FPC 0 EA2 Chip 48 degrees C / 118 degrees F
FPC 0 EA2-XR0 Chip 54 degrees C / 129 degrees F
FPC 0 EA2-XR1 Chip 56 degrees C / 132 degrees F
FPC 0 PF Chip 68 degrees C / 154 degrees F
FPC 0 EA0_HMC0 Logic die 72 degrees C / 161 degrees F
FPC 0 EA0_HMC0 DRAM botm 69 degrees C / 156 degrees F
FPC 0 EA0_HMC1 Logic die 71 degrees C / 159 degrees F
FPC 0 EA0_HMC1 DRAM botm 68 degrees C / 154 degrees F
FPC 0 EA0_HMC2 Logic die 75 degrees C / 167 degrees F
FPC 0 EA0_HMC2 DRAM botm 72 degrees C / 161 degrees F
FPC 0 EA1_HMC0 Logic die 81 degrees C / 177 degrees F
FPC 0 EA1_HMC0 DRAM botm 78 degrees C / 172 degrees F
FPC 0 EA1_HMC1 Logic die 80 degrees C / 176 degrees F
FPC 0 EA1_HMC1 DRAM botm 77 degrees C / 170 degrees F
FPC 0 EA1_HMC2 Logic die 82 degrees C / 179 degrees F
FPC 0 EA1_HMC2 DRAM botm 79 degrees C / 174 degrees F
FPC 0 EA2_HMC0 Logic die 60 degrees C / 140 degrees F
FPC 0 EA2_HMC0 DRAM botm 57 degrees C / 134 degrees F
FPC 0 EA2_HMC1 Logic die 61 degrees C / 141 degrees F
FPC 0 EA2_HMC1 DRAM botm 58 degrees C / 136 degrees F
FPC 0 EA2_HMC2 Logic die 63 degrees C / 145 degrees F
FPC 0 EA2_HMC2 DRAM botm 60 degrees C / 140 degrees F
Power
LTC3887-PF-VDD0V9-RAIL 898 mV
LTC3887-PF-VDD0V9-DEV0- 898 mV
LTC3887-PF-VDD0V9-DEV0- 900 mV
LTC3887-PF-VDD0V9-DEV1- 899 mV
LTC3887-PF-VDD0V9-DEV1- 901 mV
LTC3887-PF-AVDD1V0-RAIL 998 mV
LTC3887-PF-AVDD1V0-CH0 998 mV
LTC3887-PF-AVDD1V0-CH1 999 mV
LTC3887-ETHSW-VDD1V0 1000 mV
LTC3887-VDD2V5 2499 mV
LTC3887-PCIE-VDD0V9 899 mV
LTC3887-V1P0 999 mV
LTC3887-PHY-VDD1V0-A 999 mV
LTC3887-3V3 3300 mV
LTC3887-VDD1V8 1799 mV
UCD9090_0-CH_1-EA0_PLL_ 1005 mV
UCD9090_0-CH_2-EA0_1V4 1049 mV
UCD9090_0-CH_3-EA0_2V5 2499 mV
UCD9090_0-CH_4-EA0_1V5 1499 mV
UCD9090_0-CH_5-EA1_PLL_ 999 mV
UCD9090_0-CH_6-EA1_1V4 1037 mV
UCD9090_0-CH_7-EA1_2V5 2499 mV
UCD9090_0-CH_8-EA1_1V5 1510 mV
UCD9090_0-CH_9-PVCC 797 mV
UCD9090_0-CH_10-PVNN 991 mV
UCD9090_1-CH_1-EA2_PLL_ 1008 mV
UCD9090_1-CH_2-EA2_1V4 1009 mV
UCD9090_1-CH_3-EA2_2V5 2499 mV
UCD9090_1-CH_4-EA2_1V5 1513 mV
UCD9090_1-CH_5-1V0_PFPL 1009 mV
UCD9090_1-CH_6-V1P1 1075 mV
UCD9090_1-CH_7-V1P5 1531 mV
UCD9090_1-CH_8-V1P35 1359 mV
UCD9090_1-CH_9-VDD1V5 1511 mV
UCD9090_1-CH_10-VDD1V2 1210 mV
LTC3887-EA0-VDD0V9-RAIL 949 mV
LTC3887-EA0-VDD0V9-DEV0 949 mV
LTC3887-EA0-VDD0V9-DEV0 951 mV
LTC3887-EA0-VDD0V9-DEV1 949 mV
LTC3887-EA0-VDD0V9-DEV1 951 mV
LTC3887-EA0-VDD0V9R2-RA 947 mV
LTC3887-EA0-VDD0V9R2-CH 947 mV
LTC3887-EA0-VDD0V9R2-CH 949 mV
LTC3887-EA0-VDD1V0-RAIL 999 mV
LTC3887-EA0-VDD1V0-CH0 999 mV
LTC3887-EA0-VDD1V0-CH1 1001 mV
LTC3887-EA0-XR-VDD0V9 900 mV
LTC3887-EA0-XR-VDD1V2 1199 mV
LTC3887-EA0-HM1-VDD0V9 899 mV
LTC3887-EA0-HM-VDD1V2 1200 mV
LTC3887-EA0-HM-VDDM1V2 1199 mV
LTC3887-EA1-VDD0V9-RAIL 949 mV
LTC3887-EA1-VDD0V9-DEV0 952 mV
LTC3887-EA1-VDD0V9-DEV0 952 mV
LTC3887-EA1-VDD0V9-DEV1 951 mV
LTC3887-EA1-VDD0V9-DEV1 951 mV
LTC3887-EA1-VDD0V9R2-RA 948 mV
LTC3887-EA1-VDD0V9R2-CH 948 mV
LTC3887-EA1-VDD0V9R2-CH 950 mV
LTC3887-EA1-VDD1V0-RAIL 1000 mV
LTC3887-EA1-VDD1V0-CH0 1000 mV
LTC3887-EA1-VDD1V0-CH1 1001 mV
I2C Slave Revision 13
FPC 1 status:
State Online
FPC 1 Intake Temp Sensor 27 degrees C / 80 degrees F
FPC 1 Exhaust-A Temp Sensor60 degrees C / 140 degrees F
UCD9090_1-CH_5-1V0_PFPL 1000 mV
UCD9090_1-CH_6-V1P1 1037 mV
UCD9090_1-CH_7-V1P5 1530 mV
UCD9090_1-CH_8-V1P35 1360 mV
UCD9090_1-CH_9-VDD1V5 1513 mV
UCD9090_1-CH_10-VDD1V2 1217 mV
LTC3887-EA0-VDD0V9-RAIL 949 mV
LTC3887-EA0-VDD0V9-DEV0 949 mV
LTC3887-EA0-VDD0V9-DEV0 951 mV
LTC3887-EA0-VDD0V9-DEV1 949 mV
LTC3887-EA0-VDD0V9-DEV1 952 mV
LTC3887-EA0-VDD0V9R2-RA 947 mV
LTC3887-EA0-VDD0V9R2-CH 947 mV
LTC3887-EA0-VDD0V9R2-CH 949 mV
LTC3887-EA0-VDD1V0-RAIL 1000 mV
LTC3887-EA0-VDD1V0-CH0 1000 mV
LTC3887-EA0-VDD1V0-CH1 1001 mV
LTC3887-EA0-XR-VDD0V9 899 mV
LTC3887-EA0-XR-VDD1V2 1200 mV
LTC3887-EA0-HM1-VDD0V9 899 mV
LTC3887-EA0-HM-VDD1V2 1199 mV
LTC3887-EA0-HM-VDDM1V2 1199 mV
LTC3887-EA1-VDD0V9-RAIL 948 mV
LTC3887-EA1-VDD0V9-DEV0 950 mV
LTC3887-EA1-VDD0V9-DEV0 950 mV
LTC3887-EA1-VDD0V9-DEV1 951 mV
LTC3887-EA1-VDD0V9-DEV1 951 mV
LTC3887-EA1-VDD0V9R2-RA 947 mV
LTC3887-EA1-VDD0V9R2-CH 947 mV
LTC3887-EA1-VDD0V9R2-CH 949 mV
LTC3887-EA1-VDD1V0-RAIL 1000 mV
LTC3887-EA1-VDD1V0-CH0 1000 mV
LTC3887-EA1-VDD1V0-CH1 1002 mV
I2C Slave Revision 99
FPC 0 status:
State Online
FPC 0 EA0_HMC0 Logic die 77 degrees C / 170 degrees F
FPC 0 EA0_HMC0 DRAM botm 74 degrees C / 165 degrees F
FPC 0 EA0_HMC1 Logic die 80 degrees C / 176 degrees F
FPC 0 EA0_HMC1 DRAM botm 77 degrees C / 170 degrees F
FPC 0 EA0 Chip 93 degrees C / 199 degrees F
FPC 0 EA0-XR0 Chip 63 degrees C / 145 degrees F
FPC 0 EA0-XR1 Chip 64 degrees C / 147 degrees F
Power
I2C Slave Revision 0
FPC 0 status:
State Online
VDD12V0 12212 mV 0 mA 0 mW
EA0 Core 0.9V 900 mV 38125 mA 34327 mW
EA0 AVDD 1.0V 999 mV 31125 mA 31094 mW
EA0 HMC Core 0.9V 897 mV 9500 mA 8522 mW
EA0 1.2V 1193 mV 15430 mA 18416 mW
EA01_HMC_VDDM 1.2V 1193 mV 313 mA 374 mW
EA0_XR 0.906V 913 mV 14965 mA 13671 mW
EA1 Core 0.9V 900 mV 39750 mA 35790 mW
EA1 AVDD 1.0V 1000 mV 26000 mA 26000 mW
EA1 HMC Core 0.9V 897 mV 8918 mA 8001 mW
EA1 1.2V 1200 mV 15779 mA 18946 mW
EA0_PLL_1V0 1003 mV 0 mA 0 mW
EA0_1V04 1019 mV 0 mA 0 mW
EA0_2V5 2448 mV 0 mA 0 mW
EA0_1V5 1470 mV 0 mA 0 mW
EA1_PLL_1V0 1016 mV 0 mA 0 mW
EA1_1V04 1035 mV 0 mA 0 mW
EA1_2V5 2506 mV 0 mA 0 mW
EA1_1V5 1483 mV 0 mA 0 mW
EA1_XR 0.906V 908 mV 13918 mA 12639 mW
EA2 Core 0.9V 900 mV 38625 mA 34777 mW
EA2 AVDD 1.0V 1000 mV 26375 mA 26400 mW
EA2 HMC Core 0.9V 897 mV 9383 mA 8418 mW
EA2 1.2V 1200 mV 15779 mA 18946 mW
EA23_HMC_VDDM 1.2V 1193 mV 81 mA 97 mW
EA2_XR 0.906V 908 mV 13918 mA 12639 mW
EA3 Core 0.9V 899 mV 40250 mA 36201 mW
EA3 AVDD 1.0V 1000 mV 26750 mA 26776 mW
EA3 HMC Core 0.9V 894 mV 9267 mA 8289 mW
EA3 1.2V 1197 mV 16127 mA 19306 mW
EA2_PLL_1V0 993 mV 0 mA 0 mW
EA2_1V04 1045 mV 0 mA 0 mW
EA2_2V5 2474 mV 0 mA 0 mW
EA2_1V5 1490 mV 0 mA 0 mW
EA3_PLL_1V0 980 mV 0 mA 0 mW
EA3_1V04 1032 mV 0 mA 0 mW
EA3_2V5 2506 mV 0 mA 0 mW
EA3_1V5 1474 mV 0 mA 0 mW
EA3_XR 0.906V 910 mV 14732 mA 13419 mW
EA4 Core 0.9V 900 mV 42500 mA 38266 mW
EA4 AVDD 1.0V 1000 mV 32250 mA 32281 mW
EA4 HMC Core 0.9V 899 mV 10081 mA 9071 mW
EA4 1.2V 1193 mV 16360 mA 19526 mW
EA45_HMC_VDDM 1.2V 1193 mV 662 mA 791 mW
EA4_XR 0.906V 908 mV 15430 mA 14012 mW
EA5 Core 0.9V 899 mV 37000 mA 33278 mW
EA5 AVDD 1.0V 1000 mV 26125 mA 26150 mW
EA5 HMC Core 0.9V 897 mV 9267 mA 8314 mW
EA5 1.2V 1197 mV 15662 mA 18750 mW
EA4_PLL_1V0 1000 mV 0 mA 0 mW
EA4_1V04 1029 mV 0 mA 0 mW
EA4_2V5 2487 mV 0 mA 0 mW
EA4_1V5 1496 mV 0 mA 0 mW
EA5_PLL_1V0 1009 mV 0 mA 0 mW
EA5_1V04 1032 mV 0 mA 0 mW
EA5_2V5 2503 mV 0 mA 0 mW
EA5_1V5 1496 mV 0 mA 0 mW
VDD2V5 2483 mV 0 mA 0 mW
VDD1V5 1470 mV 0 mA 0 mW
VDD1V2 1203 mV 0 mA 0 mW
EA5_XR 0.906V 908 mV 14500 mA 13167 mW
FPC 0 status:
State Online
Temperature Top 42 degrees C / 107 degrees F
Temperature Bottom 36 degrees C / 96 degrees F
Temperature MMB1 39 degrees C / 102 degrees F
Power:
1.8 V 1959 mV
2.5 V 2495 mV
3.3 V 3344 mV
5.0 V 5047 mV
1.8 V bias 1787 mV
3.3 V bias 3291 mV
5.0 V bias 4998 mV
8.0 V bias 7343 mV
BUS Revision 40
FPC 1 status:
State Online
Temperature Top 42 degrees C / 107 degrees F
Temperature Bottom 39 degrees C / 102 degrees F
Temperature MMB1 40 degrees C / 104 degrees F
Power:
1.8 V 1956 mV
2.5 V 2498 mV
3.3 V 3340 mV
5.0 V 5023 mV
1.8 V bias 1782 mV
3.3 V bias 3277 mV
5.0 V bias 4989 mV
8.0 V bias 7289 mV
BUS Revision 40
FPC 2 status:
State Online
Temperature Top 43 degrees C / 109 degrees F
Temperature Bottom 39 degrees C / 102 degrees F
Temperature MMB1 41 degrees C / 105 degrees F
Power:
1.8 V 1963 mV
2.5 V 2503 mV
3.3 V 3340 mV
5.0 V 5042 mV
1.8 V bias 1797 mV
3.3 V bias 3311 mV
5.0 V bias 5013 mV
8.0 V bias 7221 mV
BUS Revision 40
FPC 0 status:
State Online
12.0 V 11604 mV
Power 4
1.0 V PFE0 LU0 1003 mV
1.0 V PFE1 LU0 1004 mV
1.0 V PFE1 LU2 1003 mV
1.0 V PFE0 LU0 * 1000 mV
1.0 V PFE1 LU0 * 1001 mV
1.0 V PFE1 LU2 * 1003 mV
12.0 V 11653 mV
12.0 V C 11672 mV
Power (Base/PMB/MMB)
LMB0 VDD2V5 2512 mV
LMB0 VDD1V8 1790 mV
LMB0 VDD1V5 1500 mV
LMB0 PFE0 LU0 AVDD1V0 1004 mV
LMB0 PFE0 LU0 VDD1V0 1002 mV
LMB0 VDD12V0 10608 mV
LMB1 VDD2V5 2472 mV
LMB1 VDD1V8 1788 mV
LMB1 VDD1V5 1480 mV
LMB1 PFE0 LU2 AVDD1V0 1000 mV
LMB1 PFE0 LU2 VDD1V0 1004 mV
LMB1 VDD12V0 10672 mV
LMB2 VDD2V5 2488 mV
LMB2 VDD1V8 1798 mV
LMB2 VDD1V5 1494 mV
LMB2 PFE1 LU1 AVDD1V0 1000 mV
LMB2 PFE1 LU1 VDD1V0 1004 mV
LMB2 VDD12V0 10528 mV
PMB 1.05v 1050 mV
PMB 1.5v 1500 mV
PMB 2.5v 2499 mV
PMB 3.3v 3299 mV
Bus Revision 113
FPC 5 status:
State Online
Temperature Top 39 degrees C / 102 degrees F
Temperature Bottom 38 degrees C / 100 degrees F
Power
1.8 V 1804 mV
1.8 V bias 1802 mV
3.3 V 3294 mV
3.3 V bias 3277 mV
5.0 V bias 5008 mV
5.0 V TOP 5067 mV
8.0 V bias 6642 mV
Power (Base/PMB/MMB)
1.2 V 1202 mV
1.5 V 1504 mV
5.0 V BOT 5079 mV
12.0 V TOP Base 11848 mV
12.0 V BOT Base 11780 mV
1.1 V PMB 1111 mV
1.2 V PMB 1189 mV
1.5 V PMB 1494 mV
1.8 V PMB 1819 mV
2.5 V PMB 2503 mV
3.3 V PMB 3294 mV
5.0 V PMB 5035 mV
12.0 V PMB 11788 mV
lcc0-re0:
--------------------------------------------------------------------------
FPC 1 status:
State Online
Temperature Top 30 degrees C / 86 degrees F
Temperature Bottom 25 degrees C / 77 degrees F
Temperature MMB0 Absent
Temperature MMB1 27 degrees C / 80 degrees F
Power:
1.8 V 1813 mV
2.5 V 2504 mV
3.3 V 3338 mV
5.0 V 5037 mV
1.8 V bias 1797 mV
3.3 V bias 3301 mV
5.0 V bias 5013 mV
8.0 V bias 7345 mV
BUS Revision 40
FPC 2 status:
State Online
Temperature Top 37 degrees C / 98 degrees F
Temperature Bottom 26 degrees C / 78 degrees F
Temperature MMB0 32 degrees C / 89 degrees F
Temperature MMB1 27 degrees C / 80 degrees F
Power:
1.8 V 1791 mV
2.5 V 2517 mV
3.3 V 3308 mV
5.0 V 5052 mV
1.8 V bias 1797 mV
3.3 V bias 3289 mV
5.0 V bias 4991 mV
8.0 V bias 7477 mV
BUS Revision 40
lcc0-re0:
--------------------------------------------------------------------------
FPC 1 status:
State Online
Temperature Top 46 degrees C / 114 degrees F
Temperature Bottom 47 degrees C / 116 degrees F
Power
1.8 V 1788 mV
1.8 V bias 1787 mV
3.3 V 3321 mV
3.3 V bias 3306 mV
5.0 V bias 5018 mV
5.0 V TOP 5037 mV
8.0 V bias 7223 mV
Power (Base/PMB/MMB)
1.2 V 1205 mV
1.5 V 1503 mV
5.0 V BOT 5084 mV
12.0 V TOP Base 11775 mV
12.0 V BOT Base 11794 mV
1.1 V PMB 1108 mV
1.2 V PMB 1196 mV
1.5 V PMB 1499 mV
1.8 V PMB 1811 mV
2.5 V PMB 2515 mV
3.3 V PMB 3318 mV
5.0 V PMB 5030 mV
12.0 V PMB 11832 mV
0.75 MMB TOP 752 mV
1.5 V MMB TOP 1489 mV
1.8 V MMB TOP 1782 mV
2.5 V MMB TOP 2498 mV
1.2 V MMB TOP 1155 mV
FPC 0 status:
State Online
Temperature 42 degrees C / 107 degrees F
FC 0 FPC 0 status:
State Online
Left Intake Temperature 24 degrees C / 75 degrees F
Right Intake Temperature 24 degrees C / 75 degrees F
Left Exhaust Temperature 27 degrees C / 80 degrees F
Right Exhaust Temperature 27 degrees C / 80 degrees F
Power
BIAS 3V3 3330 mV
VDD 3V3 3300 mV
VDD 2V5 2502 mV
VDD 1V5 1496 mV
VDD 1V2 1194 mV
VDD 1V0 1000 mV
SW0 VDD 1V0 1020 mV
SW0 CVDD 1V025 1032 mV
SW1 VDD 1V0 1022 mV
SW1 CVDD 1V025 1030 mV
VDD 12V0 DIV3_33 3414 mV
FPC 5 status:
State Online
Intake Temperature 31 degrees C / 87 degrees F
FPC 0 status:
State Online
PMB Temperature 35 degrees C / 95 degrees F
Intake Temperature 33 degrees C / 91 degrees F
Exhaust A Temperature 51 degrees C / 123 degrees F
Exhaust B Temperature 43 degrees C / 109 degrees F
TL0 Temperature 48 degrees C / 118 degrees F
TQ0 Temperature 53 degrees C / 127 degrees F
TL1 Temperature 56 degrees C / 132 degrees F
TQ1 Temperature 58 degrees C / 136 degrees F
TL2 Temperature 55 degrees C / 131 degrees F
TQ2 Temperature 57 degrees C / 134 degrees F
TL3 Temperature 59 degrees C / 138 degrees F
TQ3 Temperature 59 degrees C / 138 degrees F
Power
PMB 1.05v 1049 mV
PMB 1.5v 1500 mV
PMB 2.5v 2500 mV
PMB 3.3v 3299 mV
PFE0 1.5v 1500 mV
PFE0 1.0v 999 mV
TQ0 0.9v 900 mV
TL0 0.9v 900 mV
PFE1 1.5v 1499 mV
PFE1 1.0v 999 mV
TQ1 0.9v 899 mV
TL1 0.9v 900 mV
PFE2 1.5v 1500 mV
PFE2 1.0v 1000 mV
TQ2 0.9v 900 mV
TL2 0.9v 900 mV
PFE3 1.5v 1499 mV
PFE3 1.0v 1000 mV
TQ3 0.9v 900 mV
TL3 0.9v 900 mV
Bias 3.3v 3327 mV
FPC 3.3v 3300 mV
FPC 2.5v 2500 mV
SAM 0.9v 900 mV
A 12.0v 2014 mV
B 12.0v 2030 mV
show chassis environment fpc 07 (PTX5000 Packet Transport Router with FPC2-PTX-P1A)
user@host> show chassis environment fpc 07
FPC 7 status:
State Online
PMB TEMP0 Temperature 32 degrees C / 89 degrees F
PMB TEMP1 Temperature 28 degrees C / 82 degrees F
PMB CPU Temperature 46 degrees C / 114 degrees F
Intake Temperature 35 degrees C / 95 degrees F
Exhaust A Temperature 55 degrees C / 131 degrees F
Exhaust B Temperature 54 degrees C / 129 degrees F
TL5 Temperature 59 degrees C / 138 degrees F
TQ5 Temperature 57 degrees C / 134 degrees F
TL6 Temperature 57 degrees C / 134 degrees F
TQ6 Temperature 51 degrees C / 123 degrees F
TL1 Temperature 76 degrees C / 168 degrees F
TQ1 Temperature 58 degrees C / 136 degrees F
TL2 Temperature 75 degrees C / 167 degrees F
TQ2 Temperature 57 degrees C / 134 degrees F
TL4 Temperature 52 degrees C / 125 degrees F
TQ4 Temperature 66 degrees C / 150 degrees F
TL7 Temperature 52 degrees C / 125 degrees F
TQ7 Temperature 60 degrees C / 140 degrees F
TL0 Temperature 72 degrees C / 161 degrees F
TQ0 Temperature 73 degrees C / 163 degrees F
TL3 Temperature 64 degrees C / 147 degrees F
TQ3 Temperature 70 degrees C / 158 degrees F
Power
PMB 1.05v 1049 mV
PMB 3.3v 3299 mV
PMB 1.1v-a 1100 mV
PMB 1.5v 1499 mV
PMB 1.1v-b 1100 mV
Base 3.3v 3300 mV
FPC Base 2.5v 2499 mV
TL1 0.9v 897 mV
TQ1 0.9v 897 mV
PFE1 1.0v 999 mV
PFE1 1.5v 1499 mV
TL2 0.9v 897 mV
TQ2 0.9v 897 mV
PFE2 1.0v 999 mV
PFE2 1.5v 1499 mV
FPC Base 1.0v 1000 mV
FPC Base 1.2v 1199 mV
TL5 0.9v 898 mV
TQ5 0.9v 898 mV
PFE5 1.0v 1000 mV
PFE5 1.5v 1500 mV
TL6 0.9v 897 mV
TQ6 0.9v 897 mV
PFE6 1.0v 1000 mV
PFE6 1.5v 1499 mV
Mezz Base 2.5v 2500 mV
TL0 0.9v 896 mV
TQ0 0.9v 896 mV
FPC 0 status:
State Online
FPC 0 Intake-A Temp Sensor 37 degrees C / 98 degrees F
FPC 0 Intake-B Temp Sensor 34 degrees C / 93 degrees F
FPC 0 Exhaust-A Temp Sensor37 degrees C / 98 degrees F
FPC 0 Exhaust-B Temp Sensor38 degrees C / 100 degrees F
FPC 0 Exhaust-C Temp Sensor40 degrees C / 104 degrees F
FPC 0 PE0 Temp Sensor 41 degrees C / 105 degrees F
FPC 0 PE1 Temp Sensor 42 degrees C / 107 degrees F
FPC 0 PE2 Temp Sensor 44 degrees C / 111 degrees F
FPC 0 LCPU Temp Sensor 40 degrees C / 104 degrees F
Power
PE0 Core 0.9V 872 mV 28777 mA 25146 mW
PE0 HMC0 Core 0.9V 899 mV 10359 mA 9328 mW
PE1 Core 0.9V 896 mV 29476 mA 26414 mW
PE1 HMC0 Core 0.9V 899 mV 10218 mA 9187 mW
PE2 Core 0.9V 872 mV 28839 mA 25199 mW
PE2 HMC0 Core 0.9V 900 mV 10296 mA 9265 mW
PE0 Serdes 1.0V 1020 mV 29000 mA 29593 mW
PE1 Serdes 1.0V 1019 mV 29109 mA 29718 mW
PE2 Serdes 1.0V 1019 mV 28484 mA 29078 mW
LCPU Platform 1.1V 1099 mV 3515 mA 3867 mW
LCPU Core 1.0V 1000 mV 8750 mA 8703 mW
PHY VDD B 1.0V 1000 mV 17062 mA 17031 mW
PHY VDD A 1.0V 999 mV 15640 mA 15625 mW
BCM Core 1.0V 999 mV 7054 mA 7054 mW
BCM PEX 1.0V 999 mV 3562 mA 3558 mW
HMC Core 1.2V 1199 mV 1280 mA 1513 mW
HMC Serdes 1.2V 1199 mV 32937 mA 39500 mW
VDD 1.5V 1500 mV 2824 mA 4234 mW
VDD 2.5V 2449 mV 3812 mA 9343 mW
VDD 3.3V 3299 mV 5085 mA 16796 mW
12V 12259 mV 29609 mA 368196 mW
FPC 1 status:
State Online
FPC 1 Intake-A Temp Sensor 37 degrees C / 98 degrees F
FPC 1 Intake-B Temp Sensor 34 degrees C / 93 degrees F
FPC 1 Exhaust-A Temp Sensor38 degrees C / 100 degrees F
FPC 1 Exhaust-B Temp Sensor38 degrees C / 100 degrees F
FPC 1 Exhaust-C Temp Sensor40 degrees C / 104 degrees F
FPC 1 PE0 Temp Sensor 41 degrees C / 105 degrees F
FPC 1 PE1 Temp Sensor 42 degrees C / 107 degrees F
FPC 1 PE2 Temp Sensor 44 degrees C / 111 degrees F
FPC 1 LCPU Temp Sensor 39 degrees C / 102 degrees F
Power
PE0 Core 0.9V 898 mV 29351 mA 26421 mW
PE0 HMC0 Core 0.9V 899 mV 9734 mA 8750 mW
PE1 Core 0.9V 873 mV 28539 mA 24933 mW
PE1 HMC0 Core 0.9V 899 mV 9937 mA 8937 mW
PE2 Core 0.9V 875 mV 28906 mA 25316 mW
PE2 HMC0 Core 0.9V 899 mV 10140 mA 9125 mW
PE0 Serdes 1.0V 1019 mV 28312 mA 28890 mW
PE1 Serdes 1.0V 1020 mV 28656 mA 29234 mW
FPC 3 status:
State Online
FPC 3 Intake-A Temp Sensor 43 degrees C / 109 degrees F
FPC 3 Intake-B Temp Sensor 30 degrees C / 86 degrees F
FPC 3 Exhaust-A Temp Sensor48 degrees C / 118 degrees F
FPC 3 Exhaust-B Temp Sensor49 degrees C / 120 degrees F
FPC 3 Exhaust-C Temp Sensor47 degrees C / 116 degrees F
FPC 3 PE0 Temp Sensor 48 degrees C / 118 degrees F
FPC 3 PE1 Temp Sensor 55 degrees C / 131 degrees F
FPC 3 PE2 Temp Sensor 47 degrees C / 116 degrees F
FPC 3 PE3 Temp Sensor 54 degrees C / 129 degrees F
FPC 3 PE4 Temp Sensor 48 degrees C / 118 degrees F
FPC 3 PE5 Temp Sensor 58 degrees C / 136 degrees F
FPC 3 LCPU Temp Sensor 46 degrees C / 114 degrees F
Power
PE0 Core 0.9V 899 mV 29695 mA 26718 mW
PE1 Core 0.9V 899 mV 29695 mA 26710 mW
PE0 Serdes 1.0V 1020 mV 40156 mA 40906 mW
PE1 Serdes 1.0V 1020 mV 35281 mA 35968 mW
PE0 HMC Core 0.9V 900 mV 7492 mA 6742 mW
PE0,1 HMC Memory 1.2V 1199 mV 569 mA 683 mW
PE1 HMC Core 0.9V 899 mV 7570 mA 6812 mW
PE0,1 HMC Serdes 1.2V 1199 mV 20562 mA 24656 mW
PE2 Core 0.9V 899 mV 29734 mA 26765 mW
PE3 Core 0.9V 900 mV 29960 mA 26968 mW
PE2 Serdes 1.0V 1019 mV 37718 mA 38500 mW
PE3 Serdes 1.0V 1020 mV 35250 mA 35937 mW
PE2 HMC Core 0.9V 899 mV 7750 mA 6976 mW
PE2,3 HMC Memory 1.2V 1200 mV 546 mA 656 mW
PE3 HMC Core 0.9V 899 mV 7718 mA 6945 mW
PE2,3 HMC Serdes 1.2V 1199 mV 20625 mA 24750 mW
VDD 3.3V 3299 mV 5917 mA 19515 mW
VDD 1.5V 1499 mV 4015 mA 6015 mW
VDD 2.5V 2449 mV 4335 mA 10625 mW
PE4 Core 0.9V 899 mV 29835 mA 26875 mW
PE5 Core 0.9V 924 mV 30554 mA 28277 mW
PE4 Serdes 1.0V 1019 mV 43281 mA 44187 mW
PE5 Serdes 1.0V 1020 mV 27140 mA 27703 mW
PE4 HMC Core 0.9V 899 mV 7476 mA 6726 mW
PE4,5 HMC Memory 1.2V 1199 mV 531 mA 637 mW
PE5 HMC Core 0.9V 899 mV 7539 mA 6781 mW
PE4,5 HMC Serdes 1.2V 1199 mV 20375 mA 24468 mW
LCPU platform 1.1V 1099 mV 3453 mA 3796 mW
LCPU core 1.0V 999 mV 8984 mA 8984 mW
BCM core 1.0V 999 mV 7929 mA 7921 mW
BCM & PEX Serdes 1.0V 1000 mV 4046 mA 4046 mW
12V 12351 mV 51918 mA 644880 mW
FPC 5 status:
State Online
FPC 5 Intake-A Temp Sensor Failed
FPC 5 Intake-B Temp Sensor Failed
FPC 5 Exhaust-A Temp Sensor41 degrees C / 105 degrees F
FPC 5 Exhaust-B Temp Sensor41 degrees C / 105 degrees F
FPC 5 Exhaust-C Temp Sensor42 degrees C / 107 degrees F
FPC 5 PE0 Temp Sensor 47 degrees C / 116 degrees F
FPC 5 PE1 Temp Sensor 49 degrees C / 120 degrees F
FPC 5 PE2 Temp Sensor 53 degrees C / 127 degrees F
FPC 5 LCPU Temp Sensor Failed
Power
PE0 Core 0.9V 923 mV 30976 mA 28578 mW
FPC 1 status:
State Online
show chassis environment FPC 1 (MX Routers with Media Services Blade [MSB])
user@switch> show chassis environment fpc 1
FPC 1 status:
State Online
Temperature Intake 36 degrees C / 96 degrees F
Temperature Exhaust A 39 degrees C / 102 degrees F
Temperature LU TSen 52 degrees C / 125 degrees F
Temperature LU Chip 54 degrees C / 129 degrees F
Temperature XM TSen 52 degrees C / 125 degrees F
Temperature XM Chip 60 degrees C / 140 degrees F
Temperature PCIe TSen 52 degrees C / 125 degrees F
Temperature PCIe Chip 69 degrees C / 156 degrees F
Power
MPC-BIAS3V3-zl2106 3302 mV
MPC-VDD3V3-zl6100 3325 mV
MPC-AVDD1V0-zl6100 1007 mV
MPC-PCIE_1V0-zl6100 904 mV
MPC-LU0_1V0-zl2004 996 mV
MPC-VDD_1V5-zl2004 1498 mV
MPC-12VA-BMR453 11733 mV
MPC-12VB-BMR453 11728 mV
MPC-XM_0V9-vt273m 900 mV
I2C Slave Revision 81
FPC 0 status:
State Online
Intake Temperature 32 degrees C / 89 degrees F
Exhaust-A Temperature 43 degrees C / 109 degrees F
Exhaust-B Temperature 32 degrees C / 89 degrees F
PE0 Temperature 34 degrees C / 93 degrees F
PE1 Temperature 38 degrees C / 100 degrees F
PE2 Temperature 38 degrees C / 100 degrees F
PE3 Temperature 36 degrees C / 96 degrees F
PE4 Temperature 35 degrees C / 95 degrees F
PE5 Temperature 35 degrees C / 95 degrees F
Power 1
RT_1 1.0v 1018 mV
RT_2 1.0v 1018 mV
Power 2
FPC 1 1.0v 999 mV
FPC 2 1.0v 998 mV
Power 3
FPC 2.5v 2499 mV
FPC 3.3v 3299 mV
Power 4
FPC 0.9v 899 mV
FPC 1.5v 1499 mV
Power 5
PE0 1 1.0v 1039 mV
PE0 2 1.0v 1039 mV
Power 6
PE0 1 0.9v 900 mV
PE0 2 0.9v 900 mV
Power 7
PE0 3 0.9v 902 mV
PE0 4 0.9v 902 mV
Power 8
PE0 H 0.9v 899 mV
PE0 H 1.2v 1199 mV
Power 9
PE1 1 1.0v 1040 mV
PE1 2 1.0v 1039 mV
Power 10
PE1 1 0.9v 901 mV
PE1 2 0.9v 901 mV
Power 11
PE1 3 0.9v 900 mV
PE1 4 0.9v 900 mV
Power 12
PE1 H 0.9v 899 mV
PE1 H 1.2v 1199 mV
Power 13
PE2 1 1.0v 1039 mV
PE2 2 1.0v 1039 mV
Power 14
PE2 1 0.9v 900 mV
PE2 2 0.9v 900 mV
Power 15
PE2 3 0.9v 900 mV
PE2 4 0.9v 900 mV
Power 16
PE2 H 0.9v 899 mV
PE2 H 1.2v 1199 mV
Power 17
PE3 1 1.0v 1039 mV
PE3 2 1.0v 1039 mV
Power 18
PE3 1 0.9v 899 mV
PE3 2 0.9v 900 mV
Power 19
PE3 3 0.9v 899 mV
PE3 4 0.9v 900 mV
Power 20
PE3 H 0.9v 899 mV
PE3 H 1.2v 1199 mV
Power 21
PE4 1 1.0v 1039 mV
PE4 2 1.0v 1039 mV
Power 22
PE4 1 0.9v 900 mV
PE4 2 0.9v 900 mV
Power 23
PE4 3 0.9v 901 mV
PE4 4 0.9v 901 mV
Power 24
PE4 H 0.9v 899 mV
PE4 H 1.2v 1199 mV
Power 25
PE5 1 1.0v 1040 mV
PE5 2 1.0v 1039 mV
Power 26
PE5 1 0.9v 901 mV
PE5 2 0.9v 901 mV
Power 27
PE5 3 0.9v 901 mV
PE5 4 0.9v 901 mV
Power 28
PE5 H 0.9v 899 mV
PE5 H 1.2v 1199 mV
Power 29
PIC0 12.0v 12342 mV
Power 30
PIC1 12.0v 12342 mV
Power 31
A 12.0v 12375 mV
B 12.0v 1008 mV
Bus Revision 115
FPC 1 status:
State Online
Intake Temperature 33 degrees C / 91 degrees F
Exhaust-A Temperature 44 degrees C / 111 degrees F
Exhaust-B Temperature 33 degrees C / 91 degrees F
PE0 Temperature 34 degrees C / 93 degrees F
PE1 Temperature 38 degrees C / 100 degrees F
PE2 Temperature 37 degrees C / 98 degrees F
PE3 Temperature 36 degrees C / 96 degrees F
PE4 Temperature 34 degrees C / 93 degrees F
PE5 Temperature 36 degrees C / 96 degrees F
Power 1
RT_1 1.0v 1018 mV
RT_2 1.0v 1018 mV
Power 2
FPC 1 1.0v 999 mV
FPC 2 1.0v 999 mV
Power 3
FPC 2.5v 2499 mV
FPC 3.3v 3300 mV
Power 4
FPC 0.9v 899 mV
FPC 1.5v 1500 mV
Power 5
PE0 1 1.0v 1039 mV
PE0 2 1.0v 1039 mV
Power 6
PE0 1 0.9v 925 mV
PE0 2 0.9v 925 mV
Power 7
PE0 3 0.9v 925 mV
PE0 4 0.9v 926 mV
Power 8
PE0 H 0.9v 899 mV
PE0 H 1.2v 1199 mV
Power 9
PE1 1 1.0v 1040 mV
PE1 2 1.0v 1039 mV
Power 10
PE1 1 0.9v 900 mV
PE1 2 0.9v 901 mV
Power 11
PE1 3 0.9v 899 mV
PE1 4 0.9v 900 mV
Power 12
PE1 H 0.9v 899 mV
Power 19
PE3 3 0.9v 875 mV
PE3 4 0.9v 875 mV
Power 20
PE3 H 0.9v 899 mV
PE3 H 1.2v 1200 mV
Power 21
PIC0 12.0v 12281 mV
Power 22
PIC1 12.0v 0 mV
Power 23
A 12.0v 12406 mV
B 12.0v 1006 mV
Bus Revision 115
FPC 3 status:
State Online
Intake Temperature 33 degrees C / 91 degrees F
Exhaust-A Temperature 44 degrees C / 111 degrees F
Exhaust-B Temperature 30 degrees C / 86 degrees F
PE0 Temperature 33 degrees C / 91 degrees F
PE1 Temperature 37 degrees C / 98 degrees F
PE2 Temperature 38 degrees C / 100 degrees F
PE3 Temperature 34 degrees C / 93 degrees F
PE4 Temperature 33 degrees C / 91 degrees F
PE5 Temperature 36 degrees C / 96 degrees F
Power 1
RT_1 1.0v 1018 mV
RT_2 1.0v 1018 mV
Power 2
FPC 1 1.0v 999 mV
FPC 2 1.0v 999 mV
Power 3
FPC 2.5v 2500 mV
FPC 3.3v 3299 mV
Power 4
FPC 0.9v 899 mV
FPC 1.5v 1500 mV
Power 5
PE0 1 1.0v 1039 mV
PE0 2 1.0v 1039 mV
Power 6
PE0 1 0.9v 900 mV
PE0 2 0.9v 900 mV
Power 7
PE0 3 0.9v 898 mV
PE0 4 0.9v 899 mV
Power 8
PE0 H 0.9v 899 mV
PE0 H 1.2v 1199 mV
Power 9
PE1 1 1.0v 1040 mV
PE1 2 1.0v 1039 mV
Power 10
PE1 1 0.9v 926 mV
PE1 2 0.9v 926 mV
Power 11
PE1 3 0.9v 925 mV
PE1 4 0.9v 925 mV
Power 12
PE1 H 0.9v 900 mV
Options none—Display environmental information about both PEMs. For the TX Matrix router,
display environmental information about the PEMs, the TX Matrix router, and its
attached T640 routers. For the TX Matrix Plus router, display environmental
information about the PEMs, the TX Matrix Plus router, and its attached routers.
lcc number—(TX Matrix router and TX Matrix Plus router only) (Optional) Line-card
chassis number.
Replace number with the following values depending on the LCC configuration:
• 0 through 7, when T1600 routers are connected to a TX Matrix Plus router with 3D
SIBs in a routing matrix.
local—(MX Series routers only) (Optional) Display environmental information about the
PEM in the local Virtual Chassis member.
scc—(TX Matrix routers only) (Optional) Display environmental information about the
PEM in the TX Matrix router (or switch-card chassis).
sfc—(TX Matrix Plus routers only) (Optional) Display environmental information about
the PEM in the TX Matrix Plus router (or switch-fabric chassis).
List of Sample Output show chassis environment pem (M40e Router) on page 335
show chassis environment pem (M120 Router) on page 335
show chassis environment pem (M160 Router) on page 335
show chassis environment pem (M320 Router) on page 336
show chassis environment pem (MX150) on page 336
show chassis environment pem (MX104 Router) on page 336
show chassis environment pem (MX240 Router) on page 337
Output Fields Table 11 on page 334 lists the output fields for the show chassis environment pem command.
Output fields are listed in the approximate order in which they appear.
Load (Not available on M40e or M160 routers) Information about the load on supply, in percentage of rated
current being used.
Voltage (M120, M160, M320, T640, T1600, TX Matrix, and TX Matrix Plus routers only) Information about
voltage supplied to the PEM.
(MX104 routers only) Information about voltage supplied by the PEM to the system.
Current (T640, T1600, TX Matrix, and TX Matrix Plus routers only) Information about the PEM current.
Power (T640, T1600, TX Matrix, and TX Matrix Plus routers only) Information about the PEM power.
SCG/CB/SIB (T640, T1600, TX Matrix, and TX Matrix Plus routers only) SONET Clock Generator/Control
Board/Switch Interface Board.
FAN (T640, T1600, and T4000 routers with six-input DC power supply only) Information about the DC
output to the fan.
Sample Output
PEM 0 status:
State Online
Temperature OK
AC input OK
DC output OK
PEM 0 status:
State Online
Temperature OK
DC Input: OK
DC Output: OK
Load Less than 20 percent
Voltage:
48.0 V input 52864 mV
48.0 V fan supply 41655 mV
3.3 V 3399 mV
PEM 1 status:
State Online
Temperature OK
DC Input: OK
DC Output: OK
Load Less than 20 percent
Voltage:
48.0 V input 54537 mV
48.0 V fan supply 42910 mV
3.3 V 3506 mV
PEM 0 status:
State Online
Temperature OK
DC input OK
DC output OK
Load Less than 20 percent
Voltage:
48.0 V input 54833 mV
48.0 V fan supply 50549 mV
8.0 V bias 8239 mV
5.0 V bias 5006 mV
PEM 2 status:
State Online
Temperature OK
DC input OK
Load Less than 40 percent
48.0 V input 51853 mV
48.0 V fan supply 48877 mV
8.0 V bias 8449 mV
5.0 V bias 4998 mV
PEM 3 status:
State Online
Temperature OK
DC input OK
Load Less than 40 percent
48.0 V input 51717 mV
48.0 V fan supply 49076 mV
8.0 V bias 8442 mV
5.0 V bias 4998 mV
PEM 0 status:
State Online
Temperature OK
DC Output: OK
Voltage:
12.0 V output 12281 mV
3.3 V output 3353 mV
PEM 1 status:
State Empty
PEM 0 status:
State Online
Temperature OK
DC Output: OK
PEM 1 status:
State Online
Temperature OK
DC Output: OK
PEM 0 status:
State Online
Temperature OK
DC Input: OK
DC Output: OK
Voltage:
PEM 1 status:
State Online
Temperature OK
DC Input: OK
DC Output: OK
Voltage:
PEM 2 status:
State Present
PEM 3 status:
State Online
Temperature OK
DC Output: OK
PEM 0 status:
State Online
Airflow Front to Back
Temperature OK 34 degrees C / 93 degrees F
Temperature OK 26 degrees C / 78 degrees F
Temperature OK 24 degrees C / 75 degrees F
Firmware version 0x22
Cooling Fan 8752 RPM
DC Output Voltage(V) Current(A) Power(W) Load(%)
12.00 26 312 10
PEM 1 status:
State Online
Airflow Front to Back
Temperature OK 35 degrees C / 95 degrees F
PEM 0 status:
State Empty
PEM 1 status:
State Online
Airflow Front to Back
Temperature OK 48 degrees C / 118 degrees F
Temperature OK 51 degrees C / 123 degrees F
Fan Sensor 5400 RPM
DC Output Voltage(V) Current(A) Power(W) Load(%)
11.94 16 191 29
PEM 0 status:
State Online
Airflow Front to Back
Temperature OK 29 degrees C / 84 degrees F
Firmware version 0x36
Fan 0 5880 RPM
DC Output Voltage(V) Current(A) Power(W) Load(%)
12.00 104 1248 46
PEM 1 status:
State Online
Airflow Front to Back
Temperature OK 27 degrees C / 80 degrees F
Firmware version 0x36
Fan 0 5940 RPM
DC Output Voltage(V) Current(A) Power(W) Load(%)
12.00 104 1248 46
PEM 2 status:
State Online
Airflow Front to Back
Temperature OK 30 degrees C / 86 degrees F
Firmware version 0x36
Fan 0 5940 RPM
DC Output Voltage(V) Current(A) Power(W) Load(%)
12.00 105 1260 46
PEM 3 status:
State Present
PEM 4 status:
State Present
PEM 5 status:
State Present
PEM 0 status:
State Online
Airflow Front to Back
Temperature OK 21 degrees C / 69 degrees F
Firmware version 0x36
Fan 0 5760 RPM
DC Output Voltage(V) Current(A) Power(W) Load(%)
12.00 51 612 22
PEM 1 status:
State Online
Airflow Front to Back
Temperature OK 23 degrees C / 73 degrees F
Firmware version 0x36
Fan 0 5760 RPM
DC Output Voltage(V) Current(A) Power(W) Load(%)
12.00 52 624 23
PEM 2 status:
State Online
Airflow Front to Back
Temperature OK 23 degrees C / 73 degrees F
Firmware version 0x36
Fan 0 5760 RPM
DC Output Voltage(V) Current(A) Power(W) Load(%)
12.00 51 612 22
PEM 3 status:
State Online
Airflow Front to Back
Temperature OK 21 degrees C / 69 degrees F
Firmware version 0x36
Fan 0 5760 RPM
DC Output Voltage(V) Current(A) Power(W) Load(%)
12.00 51 612 22
PEM 4 status:
State Online
Airflow Front to Back
Temperature OK 22 degrees C / 71 degrees F
Firmware version 0x36
Fan 0 5760 RPM
DC Output Voltage(V) Current(A) Power(W) Load(%)
12.00 52 624 23
PEM 5 status:
State Online
Airflow Front to Back
Temperature OK 24 degrees C / 75 degrees F
Firmware version 0x36
Fan 0 5700 RPM
DC Output Voltage(V) Current(A) Power(W) Load(%)
12.00 51 612 22
PEM 6 status:
State Online
Airflow Front to Back
Temperature OK 21 degrees C / 69 degrees F
Firmware version 0x36
Fan 0 5700 RPM
DC Output Voltage(V) Current(A) Power(W) Load(%)
12.00 50 600 22
PEM 0 status:
State Online
Temperature OK
DC input: OK
PEM 0 status:
State Online
Temperature 22 degrees C / 71 degrees F
AC input: OK
DC output: Voltage Current Power Load
FPC 0 56875 606 34 4
FPC 1 57016 525 29 3
FPC 2 0 0 0 0
FPC 3 0 0 0 0
FPC 4 0 0 0 0
FPC 5 0 0 0 0
FPC 6 57158 1581 90 12
FPC 7 0 0 0 0
SCG/CB/SIB 56750 1125 63 5
PEM 0 status:
State Online
Temperature 33 degrees C / 91 degrees F
DC Input: OK
Voltage(V) Current(A) Power(W) Load(%)
INPUT 0 54.625 9.812 535 22
INPUT 1 54.625 10.250 559 23
INPUT 2 55.125 0.125 6 0
INPUT 3 54.500 10.062 548 22
INPUT 4 54.750 9.375 513 21
INPUT 5 54.750 10.187 557 23
DC Output Voltage(V) Current(A) Power(W) Load(%)
FPC 0 55.750 10.125 564 37
FPC 1 51.625 0.000 0 0
FPC 2 52.000 0.000 0 0
FPC 3 55.062 10.437 574 38
FPC 4 52.125 0.000 0 0
FPC 5 55.000 9.375 515 34
FPC 6 55.187 9.687 534 35
FPC 7 51.437 0.000 0 0
SCG/CB/SIB 55.375 15.750 872 35
FAN 54.562 14.750 804 42
show chassis environment pem (T640/T1600/T4000 Routers With Six-Input DC Power Supply)
user@host> show chassis environment pem
PEM 1 status:
State Online
Temperature 36 degrees C / 96 degrees F
DC Input: OK
Voltage(V) Current(A) Power(W) Load(%)
INPUT 0 0.000 0.000 0 0
INPUT 1 54.875 3.812 209 27
INPUT 2 55.375 3.937 218 29
INPUT 3 54.625 3.750 204 27
INPUT 4 55.125 3.375 186 24
INPUT 5 55.125 3.375 186 24
DC Output Voltage(V) Current(A) Power(W) Load(%)
FPC 0 52.312 0.000 0 0
FPC 1 52.687 0.000 0 0
FPC 2 52.812 0.000 0 0
FPC 3 55.812 7.062 394 52
FPC 4 52.625 0.000 0 0
FPC 5 52.625 0.000 0 0
FPC 6 52.750 0.000 0 0
FPC 7 52.750 0.000 0 0
SCG/CB/SIB 55.937 11.937 667 55
FAN 55.812 4.937 275 36
lcc0-re0:
--------------------------------------------------------------------------
PEM 0 status:
State Present
Temperature 27 degrees C / 80 degrees F
DC input: Check
DC output: Voltage Current Power Load
FPC 0 0 0 0 0
FPC 1 0 0 0 0
FPC 2 0 0 0 0
FPC 3 0 0 0 0
FPC 4 0 0 0 0
FPC 5 0 0 0 0
FPC 6 0 0 0 0
FPC 7 0 0 0 0
SCG/CB/SIB 0 0 0 0
scc-re0:
--------------------------------------------------------------------------
PEM 1 status:
State Online
Temperature 24 degrees C / 75 degrees F
DC input: OK
DC output: Voltage Current Power Load
SIB 0 0 0 0 0
SIB 1 0 0 0 0
SIB 2 0 0 0 0
SIB 3 56550 0 0 0
SIB 4 55958 6912 386 51
show chassis environment pem sfc (TX Matrix Plus Routing Matrix)
user@host> show chassis environment pem sfc 0
sfc0-re0:
--------------------------------------------------------------------------
PEM 0 status:
State Online
Temperature 35 degrees C / 95 degrees F
DC Input: OK
DC Output Voltage Current Power Load
Channel 0 53820 14140 761 59
Channel 1 53550 12720 681 53
Channel 2 53840 12930 696 54
Channel 3 53690 14990 804 63
Channel 4 53620 15070 808 63
Channel 5 53900 14820 798 62
Channel 6 54120 5020 271 21
show chassis environment pem lcc (TX Matrix Plus Routing Matrix)
user@host> show chassis environment lcc 0
lcc0-re1:
--------------------------------------------------------------------------
PEM 0 status:
State Online
Temperature 38 degrees C / 100 degrees F
DC Input: OK
DC Output Voltage Current Power Load
FPC 0 0 0 0 0
FPC 1 0 0 0 0
FPC 2 0 0 0 0
FPC 3 0 0 0 0
FPC 4 56408 7575 427 56
FPC 5 0 0 0 0
FPC 6 56266 7956 447 59
FPC 7 56283 6100 343 45
SCG/CB/SIB 55916 8950 500 41
PEM 1 status:
State Present
Temperature 35 degrees C / 95 degrees F
DC Input: Check
DC Output Voltage Current Power Load
FPC 0 0 0 0 0
FPC 1 0 0 0 0
FPC 2 0 0 0 0
FPC 3 0 0 0 0
FPC 4 0 0 0 0
FPC 5 0 0 0 0
FPC 6 0 0 0 0
FPC 7 0 0 0 0
SCG/CB/SIB 0 0 0 0
PEM 1 status:
State Present
Input Voltage(V) Current(A) Power(W)
INP 1 229.9 0.4 96.6
INP 2 233.7 0.4 98.2
Health check Information:
Status: Scheduled
Last Result: Pass
Last Execution: 2019-04-23 15:09:54
Next Scheduled Run: 2019-04-23 15:32:59
PEM 0 status:
State Present
PEM 1 status:
State Online
Airflow Front to Back
Temperature OK 36 degrees C / 96 degrees F
Temperature OK 35 degrees C / 95 degrees F
Fan Sensor 5940 RPM
DC Output Voltage(V) Current(A) Power(W) Load(%)
11.85 17 201 30
PEM 0 status:
State Online
Airflow Front to Back
Temperature OK 56 degrees C / 132 degrees F
Temperature OK 46 degrees C / 114 degrees F
Temperature OK 28 degrees C / 82 degrees F
Firmware version 04.10
Cooling Fan 9056 RPM
DC Output Voltage(V) Current(A) Power(W) Load(%)
12.00 47 564 19
PEM 1 status:
State Present
PEM 2 status:
State Empty
PEM 3 status:
State Empty
PEM 4 status:
State Present
PEM 5 status:
State Online
Airflow Front to Back
Temperature OK 61 degrees C / 141 degrees F
Temperature OK 49 degrees C / 120 degrees F
Temperature OK 28 degrees C / 82 degrees F
Firmware version 04.10
Cooling Fan 8656 RPM
DC Output Voltage(V) Current(A) Power(W) Load(%)
12.00 51 612 21
PEM 0 status:
State Online
Airflow Front to Back
Temp Sensor 0 OK 22 degrees C / 71 degrees F
Temp Sensor 1 OK 23 degrees C / 73 degrees F
Fan 0 9184 RPM
Fan 1 7936 RPM
DC Output Voltage(V) Current(A) Power(W) Load(%)
12 24 288 18
PEM 2 status:
State Online
Airflow Front to Back
Temp Sensor 0 OK 22 degrees C / 71 degrees F
Temp Sensor 1 OK 26 degrees C / 78 degrees F
Fan 0 9056 RPM
Fan 1 7808 RPM
DC Output Voltage(V) Current(A) Power(W) Load(%)
12 24 288 18
On PTX1000 Packet Transport Routers, you cannot view the show chassis environment
pem output at the PEM slot level, by using the command show chassis environment pem
slot.
Options none—Display environmental information about all Routing Engines. For a TX Matrix
router, display environmental information about all Routing Engines on the TX Matrix
router and its attached T640 routers. For a TX Matrix Plus router, display
environmental information about all Routing Engines on the TX Matrix Plus router
and its attached routers.
lcc number——(TX Matrix router and TX Matrix Plus router only) (Optional) Line-card
chassis number.
Replace number with the following values depending on the LCC configuration:
• 0 through 7, when T1600 routers are connected to a TX Matrix Plus router with 3D
SIBs in a routing matrix.
local—(MX Series routers only) (Optional) Display environmental information about the
Routing Engines in the local Virtual Chassis member.
scc—(TX Matrix router only) (Optional) Display environmental information about the
Routing Engine in the TX Matrix router (switch-card chassis).
sfc—(TX Matrix Plus router only) (Optional) Display environmental information about
the Routing Engine in the TX Matrix Plus router (or switch-fabric chassis).
List of Sample Output show chassis environment routing-engine (Nonredundant) on page 349
show chassis environment routing-engine (Redundant) on page 349
show chassis enviroenment routing-engine (MX150) on page 350
show chassis environment routing-engine (MX104 Router) on page 350
show chassis environment routing-engine (MX2010 Router) on page 350
show chassis environment routing-engine (MX2020 Router) on page 350
show chassis environment routing-engine (MX2008 Router) on page 350
show chassis environment routing-engine (TX Matrix Plus Router) on page 351
show chassis environment routing-engine (T4000 Core Router) on page 351
show chassis environment routing-engine (QFX Series and OCX Series) on page 351
show chassis environment routing-engine interconnect-device (QFabric
System) on page 351
show chassis environment routing-engine (PTX5000 Packet Transport
Router) on page 351
show chassis environment routing-engine (PTX10008 Router) on page 352
show chassis environment routing-engine (PTX10016 Router) on page 352
Output Fields Table 12 on page 349 lists the output fields for the show chassis environment routing-engine
command. Output fields are listed in the approximate order in which they appear.
CPU Temperature (PTX Series and T4000 Core Routers only) Temperature of the air
flowing past the Routing Engine CPU.
Sample Output
sfc0-re0:
--------------------------------------------------------------------------
Routing Engine 0 status:
State Online Master
Temperature 26 degrees C / 78 degrees F
Routing Engine 1 status:
State Online Standby
Temperature 28 degrees C / 82 degrees F
lcc0-re0:
--------------------------------------------------------------------------
Routing Engine 0 status:
State Online Master
Temperature 30 degrees C / 86 degrees F
Routing Engine 1 status:
State Online Standby
Temperature 29 degrees C / 84 degrees F
Sample Output
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).
On EX2200, EX3200, EX4200, QFX Series, and OCX Series switches, 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 none—Display 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 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.
lcc number—(TX Matrix and TX Matrix Plus routers only) (Optional) On a TX Matrix router,
display version levels for the firmware on a specified T640 router (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 router (line-card chassis) that is
connected to the TX Matrix Plus router.
Replace number with the following values depending on the LCC configuration:
• 0 through 7, when T1600 routers are connected to a TX Matrix Plus router with 3D
SIBs in a routing matrix.
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 (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.
List of Sample Output show chassis firmware (M10 Router) on page 358
show chassis firmware (M20 Router) on page 358
show chassis firmware (M40 Router) on page 358
show chassis firmware (M160 Router) on page 359
show chassis firmware (MX150) on page 359
Output Fields Table 13 on page 357 lists the output fields for the show chassis firmware command.
Output fields are listed in the approximate order in which they appear.
Part (MX Series, MX2010, MX2020, and MX2008 routers) Chassis part
name.
PFE-<number> (detail option only) Version of the Packet Forwarding Engine 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.
Sample Output
show chassis firmware (MX240, MX480, MX960 Router with Application Services Modular Line Card)
user@host> show chassis firmware
lcc0-re0:
--------------------------------------------------------------------------
Part Type Version
FPC 1 ROM Juniper ROM Monitor Version 6.4b18
O/S Version 7.0-20040804.0 by userb on 2004-0
FPC 2 ROM Juniper ROM Monitor Version 6.4b20
O/S Version 7.0-20040804.0 by userb on 2004-0
SPMB 0 ROM Juniper ROM Monitor Version 6.4b18
O/S Version 7.0-20040804.0 by userb on 2004-0
scc-re0:
--------------------------------------------------------------------------
Part Type Version
SPMB 0 ROM Juniper ROM Monitor Version 6.4b18
O/S Version 7.0-20040804.0 by userb on 2004-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 Juniper ROM Monitor Version 9.5b1
O/S Version 9.6-20090507.0 by userb on 2009-0
SPMB 1 ROM Juniper ROM Monitor Version 9.5b1
O/S Version 9.6-20090507.0 by userb on 2009-0
lcc0-re1:
--------------------------------------------------------------------------
Part Type Version
FPC 4 ROM Juniper ROM Monitor Version 9.0b2
O/S Version 9.6-20090507.0 by userb on 2009-0
FPC 6 ROM Juniper ROM Monitor Version 9.0b2
O/S Version 9.6-20090507.0 by userb on 2009-0
FPC 7 ROM Juniper ROM Monitor Version 9.0b2
O/S Version 9.6-20090507.0 by userb on 2009-0
SPMB 0 ROM Juniper ROM Monitor Version 9.5b1
O/S Version 9.6-20090507.0 by userb on 2009-0
SPMB 1 ROM Juniper ROM Monitor Version 9.5b1
O/S Version 9.6-20090507.0 by userb on 2009-0
lcc1-re1:
--------------------------------------------------------------------------
Part Type Version
FPC 4 ROM Juniper ROM Monitor Version 9.0b2
O/S Version 9.6-20090507.0 by userb on 2009-0
FPC 6 ROM Juniper ROM Monitor Version 9.0b2
O/S Version 9.6-20090507.0 by userb on 2009-0
FPC 7 ROM Juniper ROM Monitor Version 9.0b2
O/S Version 9.6-20090507.0 by userb on 2009-0
SPMB 0 ROM Juniper ROM Monitor Version 9.5b1
O/S Version 9.6-20090507.0 by userb on 2009-0
SPMB 1 ROM Juniper ROM Monitor Version 9.5b1
O/S Version 9.6-20090507.0 by userb on 2009-0
lcc2-re1:
--------------------------------------------------------------------------
Part Type Version
FPC 4 ROM Juniper ROM Monitor Version 9.0b2
O/S Version 9.6-20090507.0 by userb on 2009-0
FPC 5 ROM Juniper ROM Monitor Version 9.0b2
O/S Version 9.6-20090507.0 by userb on 2009-0
FPC 6 ROM Juniper ROM Monitor Version 9.0b2
O/S Version 9.6-20090507.0 by userb on 2009-0
FPC 7 ROM Juniper ROM Monitor Version 7.5b4
O/S Version 9.6-20090507.0 by userb on 2009-0
SPMB 0 ROM Juniper ROM Monitor Version 9.5b1
lcc3-re1:
--------------------------------------------------------------------------
Part Type Version
FPC 0 ROM Juniper ROM Monitor Version 9.0b2
O/S Version 9.6-20090507.0 by userb on 2009-0
FPC 1 ROM Juniper ROM Monitor Version 9.0b2
O/S Version 9.6-20090507.0 by userb on 2009-0
FPC 2 ROM Juniper ROM Monitor Version 9.0b2
O/S Version 9.6-20090507.0 by userb on 2009-0
FPC 4 ROM Juniper ROM Monitor Version 7.5b4
O/S Version 9.6-20090507.0 by userb on 2009-0
FPC 5 ROM Juniper ROM Monitor Version 9.0b2
O/S Version 9.6-20090507.0 by userb on 2009-0
FPC 7 ROM Juniper ROM Monitor Version 9.0b2
O/S Version 9.6-20090507.0 by userb on 2009-0
SPMB 0 ROM Juniper ROM Monitor Version 9.5b1
O/S Version 9.6-20090507.0 by userb on 2009-0
SPMB 1 ROM Juniper ROM Monitor Version 9.5b1
O/S Version 9.6-20090507.0 by userb on 2009-0
lcc0-re1:
--------------------------------------------------------------------------
Part Type Version
FPC 4 ROM Juniper ROM Monitor Version 9.0b2
O/S Version 9.6-20090507.0 by userb on 2009-0
FPC 6 ROM Juniper ROM Monitor Version 9.0b2
O/S Version 9.6-20090507.0 by userb on 2009-0
FPC 7 ROM Juniper ROM Monitor Version 9.0b2
O/S Version 9.6-20090507.0 by userb on 2009-0
SPMB 0 ROM Juniper ROM Monitor Version 9.5b1
O/S Version 9.6-20090507.0 by userb on 2009-0
SPMB 1 ROM Juniper ROM Monitor Version 9.5b1
O/S Version 9.6-20090507.0 by userb on 2009-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 Juniper ROM Monitor Version 9.5b1
O/S Version 9.6-20090507.0 by userb on 2009-0
SPMB 1 ROM Juniper ROM Monitor Version 9.5b1
O/S Version 9.6-20090507.0 by userb on 2009-0
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) 1.0.0
loader FreeBSD/arm U-Boot loader 1.0
show chassis firmware (MX Routers with Media Services Blade [MSB])
user@switch> show chassis firmware
MRE 7.5
Power CPLD 4.1
Release Information Command introduced in Junos OS Release 10.0 on MX Series 5G Universal Routing
Platforms, M120 routers, and M320 routers, T320 routers, T640 routers, T1600 routers,
TX Matrix Routers, and TX Matrix Plus routers.
Command introduced in Junos OS Release 11.1 for the QFX Series.
Command introduced in Junos OS Release 11.4 for EX Series switches.
Command introduced in Junos OS Release 12.1 for T4000 routers.
Command introduced in Junos OS Release 12.3 for MX2010 and MX2020 Universal Routing
Platforms, PTX5000 Packet Transport Routers, and ACX Series Routers.
Command introduced in Junos OS Release 13.2 for MX104 Universal Routing Platforms.
Command introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
Description (T Series routers, TX Matrix routers, TX Matrix Plus routers, M120 routers, M320 routers,
MX104 routers, MX2010 routers, MX2020 routers, MX2008 routers, MX Series 5G Universal
Routing Platforms, QFX3008-I Interconnect devices, QFX Series, OCX Series, EX Series
switches, and PTX Series Packet Transport Routers only) Show information about the
fan tray and fans.
Options all-members—(MX Series routers only) (Optional) Display information about the fan
tray and fans for all members of the Virtual Chassis configuration.
local—(MX Series routers only) (Optional) Display information about the fan tray and
fans for the local Virtual Chassis member.
member member-id—(MX Series routers only) (Optional) Display information about the
fan tray and fans for the specified member of the Virtual Chassis configuration. For
an MX Series Virtual Chassis, replace member-id variable with a value 0 or 1.
lcc number—(TX Matrix and TX Matrix Plus routers only) (Optional) On a TX Matrix router,
display information about the fan tray and fans for the specified T640 router
(line-card chassis) that is connected to a TX Matrix router. On a TX Matrix Plus router,
display information about the fan tray and fans for the specified router (line-card
chassis) that is connected to a TX Matrix Plus router.
Replace number with the following values depending on the LCC configuration:
• 0 through 7, when T1600 routers are connected to a TX Matrix Plus router with 3D
SIBs in a routing matrix.
scc —(TX Matrix routers only) (Optional) Display information about the fan tray and fans
for the TX Matrix router (switch-card chassis).
sfc number—(TX Matrix Plus routers only) (Optional) Display information about the fan
tray and fans for the TX Matrix Plus router (switch-fabric chassis). Replace number
variable with 0.
Output Fields Table 14 on page 371 lists the output fields for the show chassis fan command. Output
fields are listed in the approximate order in which they appear.
Sample Output
scc-re0:
--------------------------------------------------------------------------
Item Status RPM Measurement
Top Left Front fan OK 3420 Spinning at normal speed
Top Left Middle fan OK 3390 Spinning at normal speed
Top Left Rear fan OK 3420 Spinning at normal speed
Top Right Front fan OK 3390 Spinning at normal speed
Top Right Middle fan OK 3420 Spinning at normal speed
Top Right Rear fan OK 3390 Spinning at normal speed
Bottom Left Front fan OK 3420 Spinning at normal speed
Bottom Left Middle fan OK 3450 Spinning at normal speed
Bottom Left Rear fan OK 3420 Spinning at normal speed
Bottom Right Front fan OK 3420 Spinning at normal speed
Bottom Right Middle fan OK 3420 Spinning at normal speed
Bottom Right Rear fan OK 3420 Spinning at normal speed
Rear Tray Top fan OK 3420 Spinning at normal speed
Rear Tray Second fan OK 5190 Spinning at normal speed
Rear Tray Third fan OK 5190 Spinning at normal speed
Rear Tray Fourth fan OK 5190 Spinning at normal speed
Rear Tray Fifth fan OK 3420 Spinning at normal speed
Rear Tray Sixth fan OK 3420 Spinning at normal speed
Rear Tray Seventh fan OK 3420 Spinning at normal speed
Rear Tray Bottom fan OK 3420 Spinning at normal speed
lcc2-re0:
--------------------------------------------------------------------------
Item Status RPM Measurement
Top Left Front fan OK 3420 Spinning at normal speed
Top Left Middle fan OK 3420 Spinning at normal speed
Top Left Rear fan OK 3450 Spinning at normal speed
Top Right Front fan OK 3420 Spinning at normal speed
Top Right Middle fan OK 3450 Spinning at normal speed
Top Right Rear fan OK 3360 Spinning at normal speed
Bottom Left Front fan OK 3420 Spinning at normal speed
Bottom Left Middle fan OK 3480 Spinning at normal speed
Bottom Left Rear fan OK 3420 Spinning at normal speed
Bottom Right Front fan OK 3420 Spinning at normal speed
Bottom Right Middle fan OK 3390 Spinning at normal speed
Bottom Right Rear fan OK 3420 Spinning at normal speed
Rear Tray Top fan OK 3420 Spinning at normal speed
Rear Tray Second fan OK 3420 Spinning at normal speed
Rear Tray Third fan OK 3420 Spinning at normal speed
Rear Tray Fourth fan OK 3420 Spinning at normal speed
Rear Tray Fifth fan OK 3420 Spinning at normal speed
Rear Tray Sixth fan OK 3420 Spinning at normal speed
Rear Tray Seventh fan OK 3420 Spinning at normal speed
Rear Tray Bottom fan OK 3420 Spinning at normal speed
sfc0-re0:
--------------------------------------------------------------------------
Item Status RPM Measurement
Fan Tray 0 Fan 1 OK 4350 Spinning at normal speed
lcc0-re0:
--------------------------------------------------------------------------
Item Status RPM Measurement
Top Left Front fan OK 3420 Spinning at normal speed
Top Left Middle fan OK 3420 Spinning at normal speed
Top Left Rear fan OK 3420 Spinning at normal speed
Top Right Front fan OK 3450 Spinning at normal speed
Top Right Middle fan OK 3420 Spinning at normal speed
Top Right Rear fan OK 3420 Spinning at normal speed
Bottom Left Front fan OK 3420 Spinning at normal speed
Bottom Left Middle fan OK 3420 Spinning at normal speed
Bottom Left Rear fan OK 3390 Spinning at normal speed
sfc0-re0:
--------------------------------------------------------------------------
Item Status RPM Measurement
Fan Tray 0 Fan 1 OK 4830 Spinning at normal speed
Fan Tray 0 Fan 2 OK 4860 Spinning at normal speed
Fan Tray 0 Fan 3 OK 4830 Spinning at normal speed
Fan Tray 0 Fan 4 OK 4800 Spinning at normal speed
Fan Tray 0 Fan 5 OK 4830 Spinning at normal speed
Fan Tray 0 Fan 6 OK 4770 Spinning at normal speed
Fan Tray 1 Fan 1 OK 4800 Spinning at normal speed
Fan Tray 1 Fan 2 OK 4770 Spinning at normal speed
Fan Tray 1 Fan 3 OK 4800 Spinning at normal speed
Fan Tray 1 Fan 4 OK 4770 Spinning at normal speed
Fan Tray 1 Fan 5 OK 4770 Spinning at normal speed
Fan Tray 1 Fan 6 OK 4800 Spinning at normal speed
Fan Tray 2 Fan 1 OK 4800 Spinning at normal speed
Fan Tray 2 Fan 2 OK 4800 Spinning at normal speed
Fan Tray 2 Fan 3 OK 4830 Spinning at normal speed
Fan Tray 2 Fan 4 OK 4830 Spinning at normal speed
Fan Tray 2 Fan 5 OK 4830 Spinning at normal speed
Fan Tray 2 Fan 6 OK 4830 Spinning at normal speed
Fan Tray 2 Fan 7 OK 4800 Spinning at normal speed
Fan Tray 2 Fan 8 OK 4830 Spinning at normal speed
Fan Tray 2 Fan 9 OK 4800 Spinning at normal speed
Fan Tray 3 Fan 1 OK 4860 Spinning at normal speed
Fan Tray 3 Fan 2 OK 4860 Spinning at normal speed
Fan Tray 3 Fan 3 OK 4800 Spinning at normal speed
Fan Tray 3 Fan 4 OK 4830 Spinning at normal speed
Fan Tray 3 Fan 5 OK 4830 Spinning at normal speed
Fan Tray 3 Fan 6 OK 4830 Spinning at normal speed
Fan Tray 3 Fan 7 OK 4830 Spinning at normal speed
Fan Tray 3 Fan 8 OK 4800 Spinning at normal speed
Fan Tray 3 Fan 9 OK 4800 Spinning at normal speed
Fan Tray 4 Fan 1 OK 4830 Spinning at normal speed
Fan Tray 4 Fan 2 OK 4830 Spinning at normal speed
Fan Tray 4 Fan 3 OK 4830 Spinning at normal speed
Fan Tray 4 Fan 4 OK 4830 Spinning at normal speed
Fan Tray 4 Fan 5 OK 4830 Spinning at normal speed
Fan Tray 4 Fan 6 OK 4860 Spinning at normal speed
Fan Tray 4 Fan 7 OK 4800 Spinning at normal speed
Fan Tray 4 Fan 8 OK 4860 Spinning at normal speed
Fan Tray 4 Fan 9 OK 4770 Spinning at normal speed
Fan Tray 5 Fan 1 OK 4830 Spinning at normal speed
Fan Tray 5 Fan 2 OK 4830 Spinning at normal speed
lcc0-re0:
--------------------------------------------------------------------------
Item Status RPM Measurement
Top Left Front fan OK 3420 Spinning at normal speed
Top Left Middle fan OK 3390 Spinning at normal speed
Top Left Rear fan OK 3390 Spinning at normal speed
Top Right Front fan OK 3420 Spinning at normal speed
Top Right Middle fan OK 3420 Spinning at normal speed
Top Right Rear fan OK 3450 Spinning at normal speed
Bottom Left Front fan OK 3420 Spinning at normal speed
Bottom Left Middle fan OK 3390 Spinning at normal speed
Bottom Left Rear fan OK 3420 Spinning at normal speed
Bottom Right Front fan OK 3420 Spinning at normal speed
Bottom Right Middle fan OK 3390 Spinning at normal speed
Bottom Right Rear fan OK 3420 Spinning at normal speed
Rear Tray fan 1 (Top) OK 7740 Spinning at normal speed
Rear Tray fan 2 OK 7740 Spinning at normal speed
Rear Tray fan 3 OK 7740 Spinning at normal speed
Rear Tray fan 4 OK 7740 Spinning at normal speed
Rear Tray fan 5 OK 7740 Spinning at normal speed
Rear Tray fan 6 OK 7740 Spinning at normal speed
Rear Tray fan 7 OK 7740 Spinning at normal speed
Rear Tray fan 8 OK 7740 Spinning at normal speed
Rear Tray fan 9 OK 7740 Spinning at normal speed
Rear Tray fan 10 OK 7740 Spinning at normal speed
Rear Tray fan 11 OK 7740 Spinning at normal speed
Rear Tray fan 12 OK 7740 Spinning at normal speed
Rear Tray fan 13 OK 7740 Spinning at normal speed
Rear Tray fan 14 OK 7740 Spinning at normal speed
Rear Tray fan 15 OK 7740 Spinning at normal speed
Rear Tray fan 16 (Bottom) OK 7740 Spinning at normal speed
lcc2-re0:
--------------------------------------------------------------------------
Item Status RPM Measurement
Top Left Front fan OK 3420 Spinning at normal speed
Top Left Middle fan OK 3390 Spinning at normal speed
Top Left Rear fan OK 3420 Spinning at normal speed
Top Right Front fan OK 3420 Spinning at normal speed
Top Right Middle fan OK 3420 Spinning at normal speed
Top Right Rear fan OK 3450 Spinning at normal speed
Bottom Left Front fan OK 3420 Spinning at normal speed
Bottom Left Middle fan OK 3390 Spinning at normal speed
Bottom Left Rear fan OK 3420 Spinning at normal speed
Bottom Right Front fan OK 3420 Spinning at normal speed
Bottom Right Middle fan OK 3390 Spinning at normal speed
Bottom Right Rear fan OK 3420 Spinning at normal speed
Rear Tray fan 1 (Top) OK 7740 Spinning at normal speed
Rear Tray fan 2 OK 7740 Spinning at normal speed
Rear Tray fan 3 OK 7740 Spinning at normal speed
Rear Tray fan 4 OK 7740 Spinning at normal speed
Rear Tray fan 5 OK 7740 Spinning at normal speed
<interconnect-device name>
<node-device name>
<models>
NOTE: Routers and routing platforms use the basic syntax, unless otherwise
listed. For example, the EX Series has an additional satellite parameter
available.
Description 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.
• On EX8208 and EX8216 switches—Refers to a line card; FPC number equals the slot
number for the line card.
On QFX3500, QFX5100, and OCX Series standalone switches, and PTX1000 routers
both the FPC and FPC number are always 0.
On T4000 Type 5 FPCs, there are no top temperature sensor or bottom temperature
sensor parameters. Instead, fan intake temperature sensor and fan exhaust temperature
sensors parameters are displayed.
Starting from Junos OS Release 11.4, the output of the show chassis hardware models
operational mode command displays the enhanced midplanes FRU model numbers
(CHAS-BP3-MX240-S, CHAS-BP3-MX480-S or CHAS-BP3-MX960-S) based on the
router. Prior to release 11.4, the FRU model numbers are left blank when the router has
enhanced midplanes. Note that the enhanced midplanes are introduced through the
Junos OS Release 13.3, but can be supported on all Junos OS releases.
Starting with Junos OS Release 14.1, the output of the show chassis hardware detail |
extensive | clei-models | models operational mode command displays the new DC power
supply module (PSM) and power distribution unit (PDU) that are added to provide power
to the high-density FPC (FPC2-PTX-P1A) and other components in a PTX5000 Packet
Transport Router.
Options none—Display 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 routers.
lcc number—(TX Matrix routers and TX Matrix Plus router only) (Optional) On a TX Matrix
router, display hardware information for a specified T640 router (line-card chassis)
that is connected to the TX Matrix router. On a TX Matrix Plus router, display hardware
information for a specified router (line-card chassis) that is connected to the
TX Matrix Plus router.
Replace number with the following values depending on the LCC configuration:
• 0 through 7, when T1600 routers are connected to a TX Matrix Plus router with 3D
SIBs in a routing matrix.
local—(MX Series routers only) (Optional) Display hardware-specific information for the
local Virtual Chassis members.
models—(Optional) Display model numbers and part numbers for orderable FRUs and,
for components that use ID EEPROM format v2, the CLEI code.
scc—(TX Matrix router only) (Optional) Display hardware information for the TX Matrix
router (switch-card chassis).
sfc number—(TX Matrix Plus router only) (Optional) Display hardware information for
the TX Matrix Plus router (switch-fabric chassis). Replace number variable with 0.
Additional Information The show chassis hardware detail command now displays DIMM information for the
following Routing Engines, as shown in Table 15 on page 385.
In Junos OS Release 11.4 and later, the output for the show chassis hardware models
operational mode command for MX Series routers display the enhanced midplanes FRU
model numbers—CHAS-BP3-MX240-S, CHAS-BP3-MX480-S, or
CHAS-BP3-MX960-S—based on the router. In releases before Junos OS Release 11.4,
the FRU model numbers are left blank when the router has enhanced midplanes. Note
that the enhanced midplanes are introduced through Junos OS Release 13.3, but can be
supported on all Junos OS releases.
Starting with Junos OS Release 17.3R1, the output of the show chassis hardware command
displays the mode in which vMX is running (performance mode or lite mode) in the part
number field for the FPC. RIOT-PERF indicates performance mode and RIOT-LITE indicates
lite mode.
List of Sample Output show chassis hardware (MX10008 Router) on page 390
show chassis hardware clei-models (PTX10016 Routers) on page 390
show chassis hardware detail (EX9251 Switch) on page 391
show chassis hardware extensive (T640 Router) on page 392
show chassis hardware interconnect-device (QFabric Systems) on page 393
show chassis hardware lcc (TX Matrix Router) on page 393
show chassis hardware models (MX2010 Router) on page 394
show chassis hardware node-device (QFabric Systems) on page 394
show chassis hardware scc (TX Matrix Router) on page 395
show chassis hardware sfc (TX Matrix Plus Router) on page 395
Output Fields Table 16 on page 387 lists the output fields for the show chassis hardware command.
Output fields are listed in the approximate order in which they appear.
Serial number Serial number of the chassis component. The serial number of the backplane All levels
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.
Assb ID or (extensive keyword only) Identification number that describes the FRU hardware. extensive
Assembly ID
Assembly Version (extensive keyword only) Version number of the FRU hardware. extensive
FRU model number (clei-models, extensive, and models keyword only) Model number of the FRU none specified
hardware component.
CLEI code (clei-models and extensive keyword only) Common Language Equipment none specified
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.
EEPROM Version ID EEPROM version used by the hardware component: 0x00 (version 0), 0x01 extensive
(version 1), or 0x02 (version 2).
• 1x ADSL Annex B—ADSL 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)
• 1x TGM550—TGM550 Telephony Gateway Module (Avaya VoIP gateway
module with one console port, two analog LINE ports, and two analog
TRUNK ports)
• 1x DS1 TIM510—TIM510 E1/T1 Telephony Interface Module (Avaya VoIP
media module with one E1 or T1 trunk termination port and ISDN PRI
backup)
• 4x FXS, 4xFX0, TIM514—TIM514 Analog Telephony Interface Module (Avaya
VoIP media module with four analog LINE ports and four analog TRUNK
ports)
• 4x BRI TIM521—TIM521 BRI Telephony Interface Module (Avaya VoIP media
module with four ISDN BRI ports)
• Crypto Accelerator Module—For enhanced performance of cryptographic
algorithms used in IP Security (IPsec) services
Sample Output
Hardware inventory:
Item Version Part number Serial number Description
Chassis DE487 JNP10008 [MX10008]
Midplane REV 27 750-054097 ACPD4307 Midplane 8
Routing Engine 0 BUILTIN BUILTIN RE X10 LT
Routing Engine 1 BUILTIN BUILTIN RE X10
CB 0 REV 02 750-079563 CAFF4580 Control Board
CB 1 REV 04 750-079563 CAGL8034 Control Board
..
...
..
4
FPC 3 REV 04 750-084779 CAKR7019 JNP10K-LC2101
CPU REV 05 750-073391 CAKJ2854 LC 2101 PMB
PIC 0 BUILTIN BUILTIN 4xQSFP28 SYNCE
Xcvr 0 REV 01 740-058734 1ACQ104300K QSFP-100GBASE-SR4
PIC 1 BUILTIN BUILTIN 4xQSFP28 SYNCE
Xcvr 0 REV 01 740-061405 1ACQ12110AN QSFP-100GBASE-SR4
PIC 2 BUILTIN BUILTIN 4xQSFP28 SYNCE
Xcvr 0 REV 01 740-046565 QG1105B2 QSFP+-40G-SR4
PIC 3 BUILTIN BUILTIN 4xQSFP28 SYNCE
Xcvr 0 REV 01 740-045627 QH08036X 40GBASE eSR4
PIC 4 BUILTIN BUILTIN 4xQSFP28 SYNCE
Xcvr 0 REV 01 740-067443 XWR0RY7 QSFP+-40G-SR4
Xcvr 1 REV 01 740-067443 XWR0RYH QSFP+-40G-SR4
Xcvr 2 REV 01 740-067443 XWR0RYP QSFP+-40G-SR4
Xcvr 3 REV 01 740-067443 XWS028S QSFP+-40G-SR4
PIC 5 BUILTIN BUILTIN 4xQSFP28 SYNCE
Xcvr 3 REV 01 740-058734 1ACQ113406C QSFP-100GBASE-SR4
FPD Board REV 07 711-054687 ACPC7142 Front Panel Display
PEM 0 REV 02 740-049388 1EDL62102N9 Power Supply AC
PEM 1 REV 02 740-049388 1EDL60300KX Power Supply AC
PEM 2 REV 02 740-049388 1EDL60300DL Power Supply AC
PEM 3 REV 02 740-049388 1EDL61701BT Power Supply AC
PEM 4 REV 02 740-049388 1EDL62102P7 Power Supply AC
PEM 5 REV 02 740-049388 1EDL62102PP Power Supply AC
FTC 0 REV 14 750-050108 ACPE4038 Fan Controller 8
FTC 1 REV 14 750-050108 ACPE4032 Fan Controller 8
Fan Tray 0 REV 09 760-054372 ACPD6799 Fan Tray 8
Fan Tray 1 REV 09 760-054372 ACNZ3584 Fan Tray 8
SFB 0 REV 24 750-050058 ACPD4587 Switch Fabric (SIB) 8
SFB 1 REV 24 750-050058 ACNZ0635 Switch Fabric (SIB) 8
SFB 2 REV 24 750-050058 ACPD4908 Switch Fabric (SIB) 8
SFB 3 REV 24 750-050058 ACNZ0617 Switch Fabric (SIB) 8
SFB 4 REV 24 750-050058 ACNZ0527 Switch Fabric (SIB) 8
SFB 5 REV 23 750-050058 ACNX6980 Switch Fabric (SIB) 8
Hardware inventory:
Item Version Part number CLEI code FRU model number
Midplane REV 24 750-077138 CMMUN00ARA JNP10016
Hardware inventory:
Item Version Part number Serial number Description
Chassis BLANK EX9251
Routing Engine 0 BUILTIN BUILTIN RE-S-2X00x6
CB 0 REV 05 750-069579 CAGT1382 EX9251
FPC 0 BUILTIN BUILTIN MPC
PIC 0 BUILTIN BUILTIN 4XQSFP28 PIC
Xcvr 0 REV 01 740-044512 APF14500007NHC QSFP+-40G-CU50CM
Xcvr 2 REV 01 740-046565 QH21035H QSFP+-40G-SR4
PIC 1 BUILTIN BUILTIN 8XSFPP PIC
Xcvr 0 REV 01 740-031980 AA15393URH7 SFP+-10G-SR
Xcvr 1 REV 01 740-031980 AA162832LVG SFP+-10G-SR
Hardware inventory:
Item Version Part number Serial number Description
Chassis T640
Jedec Code: 0x7fb0 EEPROM Version: 0x01
P/N: ........... S/N: ...........
Assembly ID: 0x0507 Assembly Version: 00.00
Date: 00-00-0000 Assembly Flags: 0x00
Version: ...........
ID: Gibson LCC Chassis
Board Information Record:
Address 0x00: 00 00 00 00 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 00 00 00 00
Address 0x10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x20: ff ff ff ff ff ff ff ff ff ff ff ff 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
Midplane REV 04 710-002726 AX5633
Jedec Code: 0x7fb0 EEPROM Version: 0x01
P/N: 710-002726. S/N: AX5633.
Assembly ID: 0x0127 Assembly Version: 01.04
Date: 06-27-2001 Assembly Flags: 0x00
Version: REV 04.....
ID: Gibson Backplane
Board Information Record:
Address 0x00: ad 01 08 00 00 90 69 0e f8 00 ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 01 ff 01 27 01 04 52 45 56 20 30 34 00 00
Address 0x10: 00 00 00 00 37 31 30 2d 30 30 32 37 32 36 00 00
Address 0x20: 53 2f 4e 20 41 58 35 36 33 33 00 00 00 1b 06 07
Address 0x30: d1 ff ff ff ad 01 08 00 00 90 69 0e f8 00 ff ff
Address 0x40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
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 Power Entry Module
...
SCG 0 REV 04 710-003423 HF6023
...
SCG 1 REV 04 710-003423 HF6061
...
Routing Engine 0 REV 01 740-005022 210865700292 RE-3.0
...
CB 0 REV 06 710-002728 HE3614
...
FPC 1 REV 01 710-002385 HE3009 FPC Type 1
... REV 06 710-001726 HC0010
Hardware inventory:
Item Version Part number Serial number Description
Chassis REV 07 QFX_olive
Midplane REV 07 750-021261 BH0208188289 QFX Midplane
CB 0 REV 07 750-021261 BH0208188289 QFXIC08-CB4S
lcc0-re0:
--------------------------------------------------------------------------
Hardware inventory:
Item Version Part number Serial number 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 T640 Sonet Clock Gen.
Routing Engine 0 REV 13 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 4x OC-12 SONET, SMIR
PIC 3 REV 09 750-008155 HS3012 2x G/E IQ, 1000 BASE
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 4x OC-48 SONET, SMSR
PIC 2 REV 01 750-004535 HC0235 1x OC-192 SM SR1
PIC 3 REV 07 750-007141 HX1699 10x 1GE(LAN), 1000 BASE
Hardware inventory:
Item Version Part number Serial number FRU model number
FPM Board REV 06 711-032349 ZX8744 711-032349
PSM 4 REV 0C 740-033727 VK00254 00000000000000000000000
PSM 5 REV 0B 740-033727 VG00015 00000000000000000000000
PSM 6 REV 0B 740-033727 VH00097 00000000000000000000000
PSM 7 REV 0C 740-033727 VJ00151 00000000000000000000000
PSM 8 REV 0C 740-033727 VJ00149 00000000000000000000000
PDM 0 REV 0B 740-038109 WA00008
PDM 1 REV 0B 740-038109 WA00014
Routing Engine 0 REV 02 740-041821 9009094134 RE-S-1800X4-16G-S
Routing Engine 1 REV 02 740-041821 9009094141 RE-S-1800X4-16G-S
CB 0 REV 08 750-040257 CAAB3491 750-040257
CB 1 REV 08 750-040257 CAAB3489 750-040257
SFB 0 REV 06 711-032385 ZV1828 711-032385
SFB 1 REV 07 711-032385 ZZ2568 711-032385
SFB 2 REV 07 711-032385 ZZ2563 711-032385
SFB 3 REV 07 711-032385 ZZ2564 711-032385
SFB 4 REV 07 711-032385 ZZ2580 711-032385
SFB 5 REV 07 711-032385 ZZ2579 711-0323856
SFB 6 REV 07 711-032385 CAAB4882 711-044170
SFB 7 REV 07 711-032385 CAAB4898 711-044170
FPC 0 REV 33 750-028467 CAAB1919 MPC-3D-16XGE-SFPP
FPC 1 REV 21 750-033205 ZG5027 MX-MPC3-3D
MIC 0 REV 03 750-033307 ZV6299 MIC3-3D-10XGE-SFPP
MIC 1 REV 03 750-033307 ZV6268 MIC3-3D-10XGE-SFPP
FPC 8 REV 22 750-031089 ZT9746 MX-MPC2-3D
MIC 0 REV 26 750-028392 ABBS1150 MIC-3D-20GE-SFP
MIC 1 REV 26 750-028387 ABBR9582 MIC-3D-4XGE-XFP
FPC 9 REV 11 750-036284 ZL3591 MPCE-3D-16XGE-SFPP
ADC 0 REV 05 750-043596 CAAC2073 750-043596
ADC 1 REV 01 750-043596 ZV4117 750-043596
ADC 8 REV 01 750-043596 ZV4107 750-043596
ADC 9 REV 02 750-043596 ZW1555 750-043596
Fan Tray 0 REV 2A 760-046960 ACAY0015
Fan Tray 1 REV 2A 760-046960 ACAY0019
Fan Tray 2 REV 2A 760-046960 ACAY0020
Fan Tray 3 REV 2A 760-046960 ACAY0021
scc-re0:
--------------------------------------------------------------------------
Hardware inventory:
Item Version Part number Serial number 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
Routing Engine 0 REV 05 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)
sfc0-re0:
--------------------------------------------------------------------------
Hardware inventory:
Item Version Part number Serial number 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
Routing Engine 0 REV 01 740-026942 737A-1064 SFC RE
Routing Engine 1 REV 01 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
SIB F13 7 REV 04 750-024564 DW5758 F13 SIB
B Board REV 03 710-023431 DW9047 F13 SIB
SIB F13 8 REV 04 750-024564 DW5761 F13 SIB
B Board REV 03 710-023431 DW9043 F13 SIB Mezz
SIB F13 9 REV 04 750-024564 DW5754 F13 SIB
B Board REV 03 710-023431 DW9078 F13 SIB Mezz
SIB F13 11 REV 04 710-022600 DX0826 F13 SIB
B Board REV 03 710-023431 DX0967 F13 SIB Mezz
Release Information Command introduced in Junos OS Release 14.2R3 for Junos Fusion Provider Edge.
Command introduced in Junos OS Release 16.1R1 for Junos Fusion Enterprise.
Description Display the status and colors of the chassis LEDs of the satellite devices in a Junos Fusion.
A major alarm (red) indicates a critical error condition that requires immediate action. A
minor alarm (yellow) indicates a noncritical condition that requires monitoring or
maintenance. A minor alarm that is left unchecked might cause interruption in service or
performance degradation.
Options none—Display the status of the chassis status LEDs of every satellite device in the Junos
Fusion.
slot-id slot-id—(Optional) Display the status of the chassis status LEDs of the satellite
device using the specified FPC slot identifier in the Junos Fusion. The slot-id is the
FPC slot ID number.
Related • Configuring Satellite Device Alarm Handling Using an Environment Monitoring Satellite
Documentation Policy in a Junos Fusion on page 56
Output Fields Table 17 on page 398 lists the output fields for the show chassis led satellite command.
Output fields are listed in the approximate order in which they appear.
Beacon LED (Applies when QFX5100, QFX5110, and QFX5200 switches are in an satellite
device role only) Indicates if the beacon feature is on or off. The beacon feature
is always off in a Junos Fusion.
System LED Indicates the state of the System (SYS) LED on the satellite device.
Master LED Indicates the state of the Master (MST) LED on the satellite device.
Alarm LED Indicates the state of the Alarm (ALM) LED on the satellite device.
Mgmt Port0 LED (Applies when QFX5100, QFX5110, and QFX5200 switches are in an satellite
device role only) Indicates the state of the management port 0 (em0) LED
status on the satellite device.
Mgmt Port1 LED (Applies when QFX5100, QFX5110, and QFX5200 switches are in an satellite
device role only) Indicates the state of the management port 1(em0) LED status
on the satellite device.
Status LED The state of the Status LED for the particular interface on the satellite device.
• Network Port, Built-In QSFP+ Port, Uplink Port, and Uplink Module Port LEDs
on EX4300 Switches
• Access Port and Uplink Port LEDs on a QFX5100 Device
• QFX5110 Network Port LEDs
• QFX5200 Access Port and Uplink Port LEDs
Link/Activity LED The state of the Link/Activity LED for the particular interface on the satellite
device.
• Network Port, Built-In QSFP+ Port, Uplink Port, and Uplink Module Port LEDs
on EX4300 Switches
• Access Port and Uplink Port LEDs on a QFX5100 Device
• QFX5110 Network Port LEDs
• QFX5200 Access Port and Uplink Port LEDs
Sample Output
<bios | slot>
<lcc number | scc>
Options none—Display 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 routers.
lcc number—(TX Matrix and TX Matrix Plus routers only) (Optional) On a TX Matrix router,
display Routing Engine information for a specified T640 router (line-card chassis)
that is connected to the TX Matrix router. On a TX Matrix Plus router, display Routing
Engine information for a specified router (line-card chassis) that is connected to the
TX Matrix Plus router.
Replace number with the following values depending on the LCC configuration:
• 0 through 7, when T1600 routers are connected to a TX Matrix Plus router with 3D
SIBs in a routing matrix.
local—(MX Series routers only) (Optional) Display Routing Engine information for the
local Virtual Chassis member.
scc—(TX Matrix routers only) (Optional) Display Routing Engine information for the TX
Matrix router (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.
• Switching the Global Master and Backup Roles in a Virtual Chassis Configuration
List of Sample Output show chassis routing-engine (M5 Router) on page 407
show chassis routing-engine (M20 Router) on page 407
show chassis routing-engine (MX104 Router) on page 408
show chassis routing-engine (MX240 Router) on page 409
show chassis routing-engine (MX960 Router) on page 409
show chassis routing-engine (T320 Router) on page 410
show chassis routing-engine (T4000 Router) on page 411
show chassis routing-engine (TX Matrix Router) on page 412
show chassis routing-engine lcc (TX Matrix Router) on page 413
show chassis routing-engine bios (TX Matrix Router) on page 414
show chassis routing-engine (TX Matrix Plus Router) on page 414
show chassis routing-engine lcc (TX Matrix Plus Router) on page 415
show chassis routing-engine bios (TX Matrix Plus Router) on page 416
show chassis routing-engine (QFX Series) on page 416
show chassis routing-engine (OCX Series) on page 417
show chassis routing engine interconnect-device (QFabric Systems) on page 417
show chassis routing-engine (PTX Series Packet Transport Router) on page 418
show chassis routing-engine (EX9200 Switch) on page 419
show chassis routing-engine (EX9251 Switch) on page 419
show chassis routing-engine (ACX2000 Universal Metro Router) on page 420
show chassis routing-engine (ACX1000 Universal Metro Router) on page 420
show chassis routing-engine (Displaying the guest reboot reason on PTX5000,MX240,
MX480, MX960< MX2010, and MX2020) on page 421
Output Fields Table 18 on page 404 lists the output fields for the show chassis routing-engine command.
Output fields are listed in the approximate order in which they appear.
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.
NOTE: When the chassis has two Routing Engines, the amount of DRAM should be the same on both.
A DRAM size mismatch error can result when the Routing Engines have different amounts of DRAM.
Starting with Junos OS Release 12.3R1, the DRAM field displays both available memory and installed
memory.
NOTE: For platforms running Junos OS with upgraded FreeBSD, the way memory utilization is
calculated has changed. Starting in Junos OS Release 15.1R1, inactive memory is no longer included
in the calculation for memory utilization. Inactive memory is now considered as free. That is, the value
for used memory decreases and results in more memory to be available for other processes. For
platforms that run Junos OS with upgraded FreeBSD, see Release Information for Junos OS with
Upgraded FreeBSD.
5 sec CPU Utilization Information about the Routing Engine's CPU utilization in the past 5 seconds:
1 min CPU Utilization Information about the Routing Engine's CPU utilization in the past 1 minute:
5 min CPU Utilization Information about the Routing Engine's CPU utilization in the past 5 minutes:
15 min CPU Utilization Information about the Routing Engine's CPU utilization in the past 15 minutes:
Serial ID (Systems with multiple Routing Engines) Identification number of the Routing Engine in this slot.
Routing Engine BIOS BIOS version being run by the Routing Engine.
Version
• power cycle/failure—Halt 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.
• watchdog—Reboot 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 EX Series switch) Reboot due to pressing of the reset
button on the Routing Engine.
• power-button hard power off—Reboot 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 reason—Reboot due to miscellaneous hardware reasons.
• thermal shutdown—Reboot due to the router or switch reaching a critical temperature at which
point it is unsafe to continue operations.
• hard disk failure—Reboot due to a hard disk or solid-state drive (SSD) failure.
• reset from debugger—Reboot due to reset from the debugger.
• chassis control reset—Restart 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 reset—Reboot due to a BIOS auto-recovery reset.
• could not be determined—Reboot due to an undetermined reason.
• Router rebooted after a normal shutdown—Reboot due to a normal shutdown. 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.
• Hypervisor reboot—When both Linux host and Junos OS is rebooted using the request vmhost reboot
command.
• VJUNOS Reboot—When Junos OS is rebooted using the request system reboot command.
Load averages Routing Engine load averages for the last 1, 5, and 15 minutes.
Sample Output
DRAM 768 MB
Memory utilization 0 percent
CPU utilization:
User 0 percent
Background 0 percent
Kernel 1 percent
Interrupt 0 percent
Idle 99 percent
Model RE-2.0
Serial ID d800000734745701
Start time 2003-06-17 16:37:33 PDT
Uptime 195 days, 18 hours, 47 minutes, 9 seconds
Last reboot reason Router rebooted after a normal shutdown
Slot 0:
Current state Master
Election priority Master (default)
scc-re0:
--------------------------------------------------------------------------
Routing Engine status:
Slot 0:
Current state Master
Election priority Master (default)
Temperature 34 degrees C / 93 degrees F
CPU temperature 33 degrees C / 91 degrees F
DRAM 2048 MB
Memory utilization 12 percent
CPU utilization:
User 0 percent
Background 0 percent
Kernel 2 percent
Interrupt 0 percent
Idle 98 percent
Model RE-4.0
Serial ID P11123900153
Start time 2004-08-05 18:42:05 PDT
Uptime 9 days, 22 hours, 49 minutes, 50 seconds
Last reboot reason Router rebooted after a normal shutdown
Load averages: 1 minute 5 minute 15 minute
0.00 0.08 0.07
lcc0-re0:
--------------------------------------------------------------------------
Routing Engine status:
Slot 0:
Current state Master
Election priority Master (default)
Temperature 33 degrees C / 91 degrees F
CPU temperature 30 degrees C / 86 degrees F
DRAM 2048 MB
Memory utilization 12 percent
CPU utilization:
User 0 percent
Background 0 percent
Kernel 1 percent
Interrupt 0 percent
Idle 98 percent
Model RE-3.0
Serial ID 210865700363
Start time 2004-08-05 18:42:05 PDT
Uptime 9 days, 22 hours, 48 minutes, 20 seconds
Last reboot reason Router rebooted after a normal shutdown
Load averages: 1 minute 5 minute 15 minute
0.00 0.02 0.00
lcc2-re0:
--------------------------------------------------------------------------
Routing Engine status:
Slot 0:
Current state Master
Election priority Master (default)
Temperature 34 degrees C / 93 degrees F
CPU temperature 35 degrees C / 95 degrees F
DRAM 2048 MB
Memory utilization 12 percent
CPU utilization:
User 0 percent
Background 0 percent
Kernel 2 percent
Interrupt 0 percent
Idle 98 percent
Model RE-4.0
Serial ID P11123900126
Start time 2004-08-05 18:42:05 PDT
Uptime 9 days, 22 hours, 49 minutes, 4 seconds
Last reboot reason Router rebooted after a normal shutdown
Load averages: 1 minute 5 minute 15 minute
0.01 0.01 0.0
lcc0-re0:
--------------------------------------------------------------------------------
Routing Engine status:
Slot 0:
Current state Master
Election priority Master (default)
Temperature 33 degrees C / 91 degrees F
CPU temperature 30 degrees C / 86 degrees F
DRAM 2048 MB
Memory utilization 12 percent
CPU utilization:
User 0 percent
Background 0 percent
Kernel 1 percent
Interrupt 0 percent
Idle 98 percent
Model RE-3.0
Serial ID 210865700363
scc-re0:
--------------------------------------------------------------------------
Routing Engine BIOS Version: V1.0.0
lcc0-re0:
--------------------------------------------------------------------------
Routing Engine BIOS Version: V1.0.17
lcc2-re0:
--------------------------------------------------------------------------
Routing Engine BIOS Version: V1.0.0
sfc0-re0:
--------------------------------------------------------------------------
Routing Engine status:
Slot 0:
Current state Master
Election priority Master (default)
Temperature 27 degrees C / 80 degrees F
CPU temperature 42 degrees C / 107 degrees F
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 3 hours, 45 minutes, 25 seconds
Last reboot reason Router rebooted after a normal shutdown.
Load averages: 1 minute 5 minute 15 minute
0.00 0.00 0.00
Routing Engine status:
Slot 1:
Current state Backup
Election priority Backup (default)
Temperature 29 degrees C / 84 degrees F
CPU temperature 43 degrees C / 109 degrees F
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 4 hours, 16 minutes, 52 seconds
Last reboot reason 0x1:power cycle/failure
lcc0-re0:
--------------------------------------------------------------------------
Routing Engine status:
Slot 0:
Current state Master
Election priority Master (default)
Temperature 30 degrees C / 86 degrees F
CPU temperature 43 degrees C / 109 degrees F
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 3 hours, 44 minutes, 51 seconds
Last reboot reason Router rebooted after a normal shutdown.
Load averages: 1 minute 5 minute 15 minute
0.00 0.00 0.00
Routing Engine status:
Slot 1:
Current state Backup
Election priority Backup (default)
Temperature 30 degrees C / 86 degrees F
CPU temperature 43 degrees C / 109 degrees F
DRAM 3327 MB
Memory utilization 9 percent
CPU utilization:
User 0 percent
Background 0 percent
Kernel 0 percent
Interrupt 0 percent
Idle 100 percent
Model RE-TXP-LCC
Serial ID 737F-1024
Start time 2009-05-06 17:31:32 PDT
Uptime 5 days, 3 hours, 54 minutes, 19 seconds
Last reboot reason Router rebooted after a normal shutdown.
lcc0-re0:
--------------------------------------------------------------------------
Routing Engine status:
Slot 0:
Current state Master
sfc0-re0:
--------------------------------------------------------------------------
Routing Engine BIOS Version: V0.0.Z
lcc0-re0:
--------------------------------------------------------------------------
Routing Engine BIOS Version: V0.0.N
Idle 99 percent
Model RE-DUO-2600
Serial ID P737A-002438
Start time 2011-12-21 16:52:26 PST
Uptime 27 minutes, 49 seconds
Last reboot reason Router rebooted after a normal shutdown.
[...Output truncasted...]
Interrupt 0 percent
Idle 79 percent
5 min CPU utilization:
User 2 percent
Background 0 percent
Kernel 19 percent
Interrupt 0 percent
Idle 79 percent
15 min CPU utilization:
User 2 percent
Background 0 percent
Kernel 19 percent
Interrupt 0 percent
Idle 79 percent
Model RE-S-2X00x6
Start time 2018-03-08 05:11:33 PST
Uptime 10 days, 18 hours, 59 minutes, 15 seconds
Last reboot reason 0x4000:VJUNOS reboot
Load averages: 1 minute 5 minute 15 minute
1.06 1.09 1.08
show chassis routing-engine (Displaying the guest reboot reason on PTX5000,MX240, MX480, MX960<
MX2010, and MX2020)
user@host> show chassis routing-engine re0 | match "Last reboot reason"
Release Information Command introduced in Junos OS Release 14.2R3 for Junos Fusion Provider Edge.
Command introduced in Junos OS Release 16.1R1 for Junos Fusion Enterprise.
Command introduced in Junos OS Release 17.2R1 for Junos Fusion Data Center.
Description Display the status of the satellite device connections in a Junos Fusion.
since time—(Optional) Display the satellite devices that have been added to the Junos
Fusion on or after a certain date or time, in YYYY-MM-DD.HH:MM:SS format.
To display all satellite devices added since a specified date, enter the specific date.
For instance, to display all satellite devices added on or after December 22nd, 2015,
enter 2015-12-22 as the time.
To display all satellite devices added since a specified time, enter the specific date
and time. For instance, to display all satellite devices added on or after 11:01AM on
December 22nd, 2015, enter 2015-12-22.11:01:00 as the time.
Output Fields Table 19 on page 423 lists the output fields for the show chassis satellite command. Output
fields are listed in the approximate order in which they appear.
Device State The state of the satellite device within the Junos Fusion. brief
terse
The most common device states: extensive
none
• Online—the satellite device is online and active. This is the
satellite device state during normal operating procedure.
• Offline—the satellite device is offline and not detected. This
state is typically seen when the satellite device has been
disconnected from the aggregation device, or when all
cascade or uplink ports connecting the satellite device to
the aggregation device are down.
• Present—the satellite device is recognized by the
aggregation device, but is not online. This state is typically
seen before a satellite device goes online, or while satellite
device configuration is in progress or finalizing.
• Rebooting—the satellite device is rebooting.
• Disable—the satellite device has been disabled.
• Misconfig—the satellite device is not properly configured.
This state is typically seen when the system ID, cascade
port, or FPC slot ID defined for the satellite device has a
misconfiguration.
• Miswire—the satellite device is miswired. This state is
typically seen when a satellite device is wired to two
aggregation devices but is not configured for multihoming.
Use show chassis satellite detail to gather more information
on the issue when the device state is Miswire.
Port State The state of the cascade port on the aggregation device. brief
extensive
Port states include: none
Extended Ports The total number of extended ports on the satellite device. brief
Total none
An extended port is a network-facing port on the satellite terse
device that sends and receives network traffic for the Junos
Fusion.
Version The version of satellite device software running on the satellite terse
device.
FPC slot The FPC slot number of the satellite device. detail
System ID The system ID of the satellite device. The system ID is also the detail
satellite device’s MAC address.
Software The satellite software version running on the satellite device. detail
package
version
Host software The host operating system software version running on the detail
version satellite device.
Minimum link Uplink failure detection minimum active uplink port setting. detail
Extended Ports The number of extended ports for the satellite device. The extensive
number on the left is the total number of extended ports, and
the number on the right is the total number of extended ports
currently in the up state.
Uplink Interface The name of the uplink interface on the satellite device. detail
Adjacency The adjacency state of the cascade to uplink interface link. detail
state
Last transition The amount of time that has passed since the last transition detail
of the cascade to uplink interface link.
Adjacency The number of times the cascade to uplink interface link has detail
down count gone into the down state.
(Interface
Name)
Last received The amount of time that has passed since the last packet was detail
packet received on the cascade interface.
Peer adjacency The amount of time that has passed since the last peer detail
information adjacency transition.
Adjacency The number of times the cascade to uplink interface link has detail
down count gone into the down state.
(Peer
adjacency
information)
SDPD restart The number of times that the satellite device protocol process detail
detected has restarted.
Uptime The amount of time that the process has been running. detail
Sample Output
Sample Output
Sample Output
Sample Output
Release Information Command introduced in Junos OS Release 14.2R3 for Junos Fusion Provider Edge.
Command introduced in Junos OS Release 16.1R1 for Junos Fusion Enterprise.
Command introduced in Junos OS Release 17.2R1 for Junos Fusion Data Center.
Description Display the status of the extended ports on the satellite devices in a Junos Fusion.
The extended ports are the network-facing ports on satellite devices that send and
receive network traffic for a Junos Fusion.
Options none—(Same as brief and terse) Display extended port status information.
fpc fpc-slot—Display extended port status information for the specified FPC slot only.
In a Junos Fusion, one FPC slot ID is assigned to each satellite device, so you can use
this option to display extended port status information for all extended ports on one
satellite device.
since time—(Optional) Display extended port status information for the satellite devices
that have been added to the Junos Fusion on or after a certain date or time, which
is entered in the YYYY-MM-DD.HH:MM:SS format.
To display extended port status information for all satellite devices added since a
specified date, enter the specific date as the time as the time. For instance,
2015-12-22.
To display extended port status information for all satellite devices added since a
specified time, enter the specific date and time as the time. For instance,
2015-12-22.11:01:00.
Output Fields Table 20 on page 434 lists the output fields for the show chassis satellite extended-port
command. Output fields are listed in the approximate order in which they appear.
Rx Request State The receive request state of the extended port. brief
terse
detail
extensive
none
Tx Request State The transmit request state of the extended port. brief
terse
detail
extensive
none
Sample Output
Release Information Command introduced in Junos OS Release 14.2R3 for Junos Fusion Provider Edge.
Command introduced in Junos OS Release 16.1R1 for Junos Fusion Enterprise.
Command introduced in Junos OS Release 17.2R1 for Junos Fusion Data Center.
Description Display the status of the cascade ports as well as the internal satellite interfaces in a
Junos Fusion.
You might see sd interfaces in the output of this command. These are internal interfaces
for the Junos Fusion.
since time—(Optional) Display interface status information for the satellite devices that
have been added to the Junos Fusion on or after a certain date or time, which is
entered in the YYYY-MM-DD.HH:MM:SS format.
To display extended port status information for all satellite devices added since a
specified date, enter the specific date as the time as the time. For instance,
2015-12-22.
To display extended port status information for all satellite devices added since a
specified time, enter the specific date and time as the time. For instance,
2015-12-22.11:01:00.
Output Fields Table 21 on page 438 lists the output fields for the show chassis satellite interface command.
Output fields are listed in the approximate order in which they appear.
Sample Output
sd-101/0/0 Up Satellite
sd-102/0/0 Up Satellite
sd-103/0/0 Up Satellite
sd-104/0/0 Up Satellite
sd-105/0/0 Up Satellite
sd-106/0/0 Up Satellite
sd-107/0/0 Up Satellite
sd-108/0/0 Up Satellite
sd-109/0/0 Up Satellite
sd-110/0/0 Up Satellite
sd-111/0/0 Up Satellite
sd-112/0/0 Up Satellite
sd-113/0/0 Up Satellite
sd-114/0/0 Up Satellite
xe-0/0/1 Up Cascade
xe-0/0/2 Up Cascade
xe-0/0/3 Up Cascade
xe-0/0/4 Up Cascade
xe-0/0/5 Up Cascade
xe-0/0/6 Up Cascade
xe-0/0/7 Up Cascade
xe-0/0/8 Up Cascade
xe-0/0/9 Up Cascade
xe-0/2/0 Up Cascade
xe-0/2/1 Up Cascade
xe-0/2/2 Up Cascade
xe-0/2/3 Up Cascade
xe-0/2/4 Up Cascade
xe-0/2/5 Up Cascade
xe-0/2/6 Up Cascade
xe-0/2/7 Up Cascade
xe-1/0/1 Up Cascade
xe-1/0/2 Up Cascade
xe-1/0/3 Up Cascade
xe-1/2/1 Up Cascade
xe-1/2/2 Up Cascade
xe-1/2/3 Up Cascade
xe-2/0/0 Up Cascade
xe-2/0/1 Up Cascade
xe-2/0/2 Up Cascade
xe-2/0/3 Up Cascade
xe-2/0/4 Up Cascade
xe-2/0/5 Up Cascade
xe-2/0/6 Up Cascade
xe-2/0/7 Up Cascade
xe-2/1/0 Up Cascade
xe-2/1/1 Up Cascade
xe-2/1/2 Up Cascade
xe-2/1/3 Up Cascade
xe-2/1/4 Up Cascade
xe-2/1/5 Up Cascade
xe-2/1/6 Up Cascade
xe-2/1/7 Up Cascade
xe-2/2/0 Up Cascade
xe-2/2/1 Up Cascade
xe-2/2/2 Up Cascade
xe-2/2/3 Up Cascade
xe-2/2/4 Up Cascade
xe-2/2/5 Up Cascade
xe-2/2/6 Up Cascade
xe-2/2/7 Up Cascade
xe-2/3/0 Up Cascade
xe-2/3/3 Dn Cascade
xe-2/3/4 Up Cascade
xe-2/3/5 Up Cascade
xe-2/3/6 Up Cascade
xe-2/3/7 Up Cascade
Sample Output
show chassis satellite interface (Junos Fusion Data Center with EVPN-VXLAN)
user@aggregation-device> show chassis satellite interface
sd-103/0/0 Up Satellite DF
xe-0/0/1 Up Cascade NA
xe-0/0/2 Up Cascade NA
xe-0/0/3 Up Cascade NA
xe-0/0/4 Up Cascade NA
xe-0/0/5 Up Cascade NA
Release Information Command introduced in Junos OS Release 14.2R3 for Junos Fusion Provider Edge.
Command introduced in Junos OS Release 16.1R1 for Junos Fusion Enterprise.
Command introduced in Junos OS Release 17.2R1 for Junos Fusion Data Center.
Description Display the status of the satellite device to aggregation device links in a Junos Fusion.
Options interface-name—Specify the name of the cascade port on the aggregation device.
since time—(Optional) Display satellite device connection information for the satellite
devices that have been added to the Junos Fusion on or after a certain date or time,
which is entered in the YYYY-MM-DD.HH:MM:SS format.
To display satellite device connection information for all satellite devices added
since a specified date, enter the specific date as the time as the time. For instance,
2015-12-22.
To display satellite device connection information for all satellite devices added
since a specified time, enter the specific date and time as the time. For instance,
2015-12-22.11:01:00.
Output Fields Table 22 on page 442 lists the output fields for the show chassis satellite neighbor
command. Output fields are listed in the approximate order in which they appear.
Port Info The uplink port interface on the satellite device. brief
terse
An uplink port interface on a satellite device detail
connects the satellite device to an aggregation extensive
device in a Junos Fusion. none
System Name The system name, or alias, of the satellite device. brief
terse
The satellite device’s alias is configured using the detail
set chassis satellite-management fpc slot-id alias extensive
alias statement. none
Adjacency up-down The number of times that the adjacency has brief
transition count transitioned between up and down. detail
extensive
Build date The date and time that the satellite software was brief
built. detail
extensive
Cause (Adjacency The cause of the last adjacency down event. brief
Down History) detail
extensive
Timestamp The date and time of the last adjacency down brief
(Adjacency Down event. detail
History) extensive
Sample Output
27_dc-builder
xe-1/2/2 Two-Way xe-0/2/0 ex4300-31 EX4300-48T 0.1I20150224_182
7_dc-builder
xe-1/2/1 Two-Way xe-0/2/0 ex4300-30 EX4300-48T 0.1I20150224_182
7_dc-builder
xe-1/0/3 Two-Way xe-0/2/0 ex4300-29 EX4300-48T 0.1I20150224_182
7_dc-builder
xe-1/0/2 Two-Way xe-0/2/0 ex4300-28 EX4300-48T 0.1I20150224_182
7_dc-builder
xe-1/0/1 Two-Way xe-0/2/0 ex4300-27 EX4300-48T 0.1I20150224_182
7_dc-builder
xe-0/2/7 Two-Way xe-0/0/0:1 qfx5100-24q-09 QFX5100-24Q-2P 0.1I20150224_18
27_dc-builder
xe-0/2/6 Init
xe-0/2/5 Init
xe-0/2/4 Two-Way xe-0/0/48:1 qfx5100-48s-05 QFX5100-48S-6Q 0.1I20150224_18
27_dc-builder
xe-0/2/3 Two-Way xe-0/0/48:1 qfx5100-48s-04 QFX5100-48S-6Q 0.1I20150224_18
27_dc-builder
xe-0/2/2 Two-Way xe-0/0/48:1 qfx5100-48s-03 QFX5100-48S-6Q 0.1I20150224_18
27_dc-builder
xe-0/2/1 Init
xe-0/2/0 Init
xe-0/0/9 Two-Way xe-0/2/0 ex4300-26 EX4300-48T 0.1I20150224_182
7_dc-builder
xe-0/0/8 Two-Way xe-0/2/0 ex4300-25 EX4300-48T 0.1I20150224_182
7_dc-builder
xe-0/0/7 Two-Way xe-0/0/48:0 qfx5100-48s-07 QFX5100-48S-6Q 0.1I20150224_18
27_dc-builder
xe-0/0/6 Two-Way xe-0/0/48:0 qfx5100-48s-06 QFX5100-48S-6Q 0.1I20150224_18
27_dc-builder
xe-0/0/5 Two-Way xe-0/0/48:0 qfx5100-48s-05 QFX5100-48S-6Q 0.1I20150224_18
27_dc-builder
xe-0/0/4 Two-Way xe-0/0/48:0 qfx5100-48s-04 QFX5100-48S-6Q 0.1I20150224_18
27_dc-builder
xe-0/0/3 Two-Way xe-0/0/48:0 qfx5100-48s-03 QFX5100-48S-6Q 0.1I20150224_18
27_dc-builder
xe-0/0/2 Two-Way xe-0/0/48:0 qfx5100-48s-02 QFX5100-48S-6Q 0.1I20150224_18
27_dc-builder
xe-0/0/1 Init
Release Information Command introduced in Junos OS Release 14.2R3 for Junos Fusion Provider Edge.
Command introduced in Junos OS Release 16.1R1 for Junos Fusion Enterprise.
Command introduced in Junos OS Release 17.2R1 for Junos Fusion Data Center.
Description Display information related to the satellite software in the Junos Fusion.
Output Fields Table 23 on page 447 lists the output fields for the show chassis satellite neighbor
command. Output fields are listed in the approximate order in which they appear.
Host Version The host version of software for the platform. detail
Current Groups The name or names of the satellite software upgrade detail
groups that are using the software package.
Former Groups The name or names of satellite software upgrade groups detail
that were previously using the software package.
Sample Output
Sample Output
group2
group3
group4
group5
Release Information Command introduced in Junos OS Release 14.2R3 for Junos Fusion Provider Edge.
Command introduced in Junos OS Release 16.1R1 for Junos Fusion Enterprise.
Command introduced in Junos OS Release 17.2R1 for Junos Fusion Data Center.
Options device-alias—Display output for the specified satellite device, which is identified by the
device alias, only.
fpc-slot —Display output for the specified satellite device, which is identified by the FPC
slot ID, only.
cluster-name—Display output for the satellite devices in the specified satellite device
cluster only.
Output Fields Table 24 on page 450 lists the output fields for the show chassis satellite statistics
command. Output fields are listed in the approximate order in which they appear.
CSP down transition count The number of times that the Control and Status Protocol (CSP) session has gone
down.
Last transition (CSP down transition The last time that the Control and Status Protocol (CSP) session transitioned.
count)
Reachability down transition count The number of times the satellite device has been in the reachability down state.
Reachability change transition count The number of times that the satellite device’s reachability state has transitioned.
(Reachability down transition count)
S/W image update count The number of times that the satellite software has been updated on the satellite
device.
Extended Port add/delete/up/down The number of times an extended port—a network-facing port on the satellite
request/response device—has been added, deleted, placed in the up position, received a down request,
or received a response.
Extended Port Params change request The number of times that an extended port—a network-facing port on the satellite
device—has had a change request.
Extended Port up/down operational The number of times that an extended port—a network-facing port on the satellite
state transition device—has had an operational state transition to up or down.
Rx sync complete The number of times the receive synchronization state has been completed.
Uplink ready rx count The number of times the uplink port—the port on the satellite device that connects to
the aggregation device—has been placed in the ready-to-receive state.
Uplink ready tx count The number of times the uplink port—the port on the satellite device that connects to
the aggregation device—has been placed in the ready-to-transmit state.
Sample Output
Sample Output
Sample Output
Release Information Command introduced in Junos OS Release 14.2R3 for Junos Fusion Provider Edge.
Command introduced in Junos OS Release 16.1R1 for Junos Fusion Enterprise.
Command introduced in Junos OS Release 17.2R1 for Junos Fusion Data Center.
No output appears when this command is entered when a Junos Fusion contains no
unprovisioned satellite devices.
This command is helpful in identifying satellite devices that are not participating in a
Junos Fusion due to configuration issues. Notably, a satellite device that has not been
associated with an FPC ID in a Junos Fusion becomes an unprovisioned satellite device.
See “Configuring Junos Fusion Provider Edge” on page 41 or Configuring or Expanding a
Junos Fusion Enterprise for information on associating an FPC ID with a Junos Fusion.
since time—(Optional) Display unprovisioned satellite device information for the satellite
devices that have been unprovisioned from a Junos Fusion on or after a certain date
or time, which is entered in the YYYY-MM-DD.HH:MM:SS format.
To display unprovisioned satellite device information for all satellite devices added
since a specified time, enter the specific date and time as the time. For instance,
2015-12-22.11:01:00.
Output Fields Table 25 on page 456 lists the output fields for the show chassis satellite unprovision
command. Output fields are listed in the approximate order in which they appear.
Device State The device state of the unprovisioned satellite device. brief
extensive
none
Cascade Ports The cascade ports on the aggregation device that are connected brief
to the satellite device. extensive
none
Software package The satellite software package version running on the satellite detail
version device.
Uplink Interface The uplink interface name. The uplink interface is the interface on detail
the satellite device that connects to the aggregation device.
Adjacency State The adjacency state of the uplink interface to cascade port link. detail
Last transition The amount of time that has passed since the last link transition. detail
Adjacency down The number of times that the uplink interface to cascade port link detail
count has gone into the adjacency down count.
Last received packet The amount of time that has passed since the last received packet. detail
Peer adjacency The amount of time that the adjacency has been active. detail
information
Last down cause The cause of the last time the adjacency went down. detail
SDPD restart The number of times that the SDPD has restarted. detail
detected
Number of restart The number of times that the process has restarted. detail
detected
Uptime The amount of time that the process has been active. detail
Sample Output
Sample Output
Release Information Command introduced in Junos OS Release 14.2R3 for Junos Fusion Provider Edge.
Command introduced in Junos OS Release 16.1R1 for Junos Fusion Enterprise.
Command introduced in Junos OS Release 17.2R1 for Junos Fusion Data Center.
Description Display information about the satellite software upgrade groups for the Junos Fusion.
A satellite software upgrade group is a group of satellite devices that are updated at the
same time to the same version of the satellite software. One Junos Fusion can contain
multiple software upgrade groups, and multiple software upgrade groups should be
configured in most Junos Fusions to avoid network downtimes during satellite software
installations.
A satellite software upgrade group that contains all satellite devices in a satellite device
cluster is automatically created when a satellite device cluster is configured. The software
upgrade group name for these automatically created software upgrade groups is the
cluster name.
Options none—(Same as brief and terse) Display satellite software upgrade group information
for all satellite software upgrade groups.
The satellite software upgrade group name is set using the set chassis
satellite-management upgrade-groups upgrade-group-name statement for
standalone satellite devices and is the cluster name for satellite device clusters.
Output Fields Table 26 on page 461 lists the output fields for the show chassis satellite upgrade-group
command. Output fields are listed in the approximate order in which they appear.
The satellite software upgrade group name is set using the set
chassis satellite-management upgrade-groups
upgrade-group-name statement for standalone satellite devices.
Sw-Version The version of satellite software associated with the satellite brief
software upgrade group. terse
extensive
none
Group State The state of the satellite software upgrade group. brief
terse
extensive
none
Slot The FPC slot identification number of the satellite device that is a brief
member of the satellite software upgrade group. terse
detail
extensive
none
Device State The state of the satellite software for the specified member of the brief
satellite software upgrade group. terse
detail
The version-in-sync output appears when the satellite device is extensive
running the satellite software version that is associated with the none
satellite software upgrade group.
Software upgrade The name of the satellite software upgrade group. detail
group
Software package The satellite software package associated with the satellite detail
version software upgrade group.
Previous software The satellite software package that was previously associated with detail
package version the satellite software upgrade group.
Sample Output
Group Device
Group Sw-Version State Slot State
__ungrouped__
ex4300 3.0R1.0 in-sync 107 version-in-sync
108 version-in-sync
109 version-in-sync
110 version-in-sync
111 version-in-sync
112 version-in-sync
113 version-in-sync
qfx 3.0R1.0 in-sync 102 version-in-sync
103 version-in-sync
104 version-in-sync
105 version-in-sync
106 version-in-sync
114 version-in-sync
Sample Output
106 version-in-sync
114 version-in-sync
Command introduced in Junos OS Release 18.2R1 for MX10008 Routers and EX9253
Switches.
lcc number—(TX Matrix and TX Matrix Plus routers only) (Optional) On a TX Matrix router,
display the temperature threshold details of a specified T640 router (line-card
chassis) that is connected to a TX Matrix router. On a TX Matrix Plus router, display
the temperature threshold details of a specified router (line-card chassis) that is
connected to a TX Matrix Plus router.
Replace number with the following values depending on the LCC configuration:
• 0 through 7, when T1600 routers are connected to a TX Matrix Plus router with 3D
SIBs in a routing matrix.
local—(MX Series routers only) (Optional) Display the chassis temperature threshold
settings of the local Virtual Chassis member.
member member-id—(MX Series routers only) (Optional) Display the chassis temperature
threshold settings of the specified member of the Virtual Chassis configuration.
Replace member-id with a value of 0 or 1.
scc—(TX Matrix routers only) (Optional) Display the temperature threshold details of
the TX Matrix router (switch-card chassis).
sfc number—(TX Matrix Plus routers only) (Optional) On TX Matrix Plus routers, display
the temperature threshold details of the TX Matrix Plus router, which is the
switch-fabric chassis. Replace number with 0.
Output Fields Table 27 on page 466 lists the output fields for the show chassis temperature-thresholds
command. Output fields are listed in the approximate order in which they appear.
Item Chassis component. If per FRU per slot thresholds are configured, the components about which
information is displayed include the chassis, the Routing Engines, FPCs, and FEBs. If per FRU per slot
thresholds are not configured, the components about which information is displayed include the
chassis and the Routing Engines.
Fan speed NOTE: On the QFX3500 switch and QFX3600 switch, there are four fan speeds: low, medium-low,
medium-high, and high. The fan speed changes at the threshold when going from a low speed to a
higher speed. When the fan speed changes from a higher speed to a lower speed, the temperature
changes two degrees below the threshold.
Temperature threshold settings, in degrees Celsius, for the fans to operate at normal and high speeds.
• Normal—The fans operate at normal speed if the component is at or below this temperature and
all the fans are present and functioning normally.
NOTE: On a TX Matrix Plus router with 3D SIBs, the threshold temperature at the XF junction is set
to 70°C for Normal fan speed, which is less than or equal to 4800 RPM.
• High—The fans operate at high speed if the component has exceeded this temperature or a fan
has failed or is missing.
NOTE: On a TX Matrix Plus router with 3D SIBs, the threshold temperature at the XF junction is set
to 75°C for High fan speed, which is greater than or equal to 5000 RPM.
NOTE: For MX480 Routers, there are three fan speeds: Low, Medium, and High.
An alarm is not triggered until the temperature exceeds the threshold settings for a yellow alarm or
a red alarm.
Yellow alarm Temperature threshold settings, in degrees Celsius, that trigger a yellow alarm.
• Normal—The temperature that must be exceeded on the component to trigger a yellow alarm
when the fans are running at full speed.
• Bad fan—The temperature that must be exceeded on the component to trigger a yellow alarm
when one or more fans have failed or are missing.
Red alarm Temperature threshold settings, in degrees Celsius, that trigger a red alarm.
• Normal—The temperature that must be exceeded on the component to trigger a red alarm when
the fans are running at full speed.
• Bad fan—The temperature that must be exceeded on the component to trigger a red alarm when
one or more fans have failed or are missing.
Fire Shutdown (T4000 routers, TX Matrix Plus router with 3D SIBs, and PTX Series Packet Transport Routers
only)—Temperature threshold settings, in degrees Celsius, for the network device to shut down.
Sample Output
FPC 0 55 60 75 65 90 80
FPC 1 55 60 75 65 90 80
FPC 2 55 60 75 65 90 80
FPC 3 55 60 75 65 90 80
FPC 4 55 60 75 65 90 80
FPC 5 55 60 75 65 90 80
FPC 6 55 60 75 65 90 80
FPC 7 55 60 75 65 90 80
FPC 8 55 60 75 65 90 80
FPC 9 55 60 75 65 90 80
FPC 10 55 60 75 65 90 80
FPC 11 55 60 75 65 90 80
show chassis temperature-thresholds (MX240, MX480, MX960 Routers with Application Services Modular
Line Card)
user@host> show chassis temperature-thresholds
FPC 0 55 60 75 65 90 80
95
FPC 1 55 60 75 65 90 80
95
FPC 2 55 60 75 65 90 80
95
FPC 4 55 60 75 65 90 80
95
FPC 5 55 60 75 65 90 80
95
show chassis temperature-thresholds (MX2010 Router with MPC7E, MPC8E, and MPC9E)
user@ host> show chassis temperature-thresholds
FPC 3 Intake 53 59 72 67 80
75 85
FPC 3 Exhaust A 77 85 98 93 103
98 108
FPC 3 Exhaust B 54 62 80 75 103
98 108
FPC 3 EA0 Chip 64 72 90 90 100
100 105
FPC 3 EA0_XR0 Chip 79 87 102 102 106
106 108
FPC 3 EA0_XR1 Chip 79 87 102 102 106
106 108
FPC 3 EA1 Chip 64 72 90 90 100
100 105
FPC 3 EA1_XR0 Chip 79 87 102 102 106
106 108
FPC 3 EA1_XR1 Chip 79 87 102 102 106
106 108
FPC 3 PEX Chip 74 82 100 100 105
105 110
FPC 3 EA2 Chip 64 72 90 90 100
100 105
FPC 3 EA2_XR0 Chip 79 87 102 102 106
106 108
FPC 3 EA2_XR1 Chip 79 87 102 102 106
106 108
FPC 3 EA3 Chip 64 72 90 90 100
100 105
FPC 3 EA3_XR0 Chip 79 87 102 102 106
106 108
FPC 3 EA3_XR1 Chip 79 87 102 102 106
106 108
FPC 3 EA0_HMC0 Logic die 81 89 103 103 107
107 111
FPC 3 EA0_HMC0 DRAM botm 76 84 98 98 102
102 106
FPC 3 EA0_HMC1 Logic die 81 89 103 103 107
107 111
FPC 3 EA0_HMC1 DRAM botm 76 84 98 98 102
102 106
FPC 3 EA0_HMC2 Logic die 81 89 103 103 107
107 111
FPC 3 EA0_HMC2 DRAM botm 76 84 98 98 102
102 106
FPC 3 EA1_HMC0 Logic die 81 89 103 103 107
107 111
FPC 3 EA1_HMC0 DRAM botm 76 84 98 98 102
102 106
FPC 3 EA1_HMC1 Logic die 81 89 103 103 107
107 111
FPC 3 EA1_HMC1 DRAM botm 76 84 98 98 102
102 106
FPC 3 EA1_HMC2 Logic die 81 89 103 103 107
107 111
FPC 3 EA1_HMC2 DRAM botm 76 84 98 98 102
102 106
FPC 3 EA2_HMC0 Logic die 81 89 103 103 107
107 111
FPC 3 EA2_HMC0 DRAM botm 76 84 98 98 102
102 106
FPC 3 EA2_HMC1 Logic die 81 89 103 103 107
107 111
FPC 3 EA2_HMC1 DRAM botm 76 84 98 98 102
102 106
FPC 3 EA2_HMC2 Logic die 81 89 103 103 107
107 111
FPC 3 EA2_HMC2 DRAM botm 76 84 98 98 102
102 106
FPC 3 EA3_HMC0 Logic die 81 89 103 103 107
107 111
FPC 3 EA3_HMC0 DRAM botm 76 84 98 98 102
102 106
FPC 3 EA3_HMC1 Logic die 81 89 103 103 107
107 111
FPC 3 EA3_HMC1 DRAM botm 76 84 98 98 102
102 106
FPC 3 EA3_HMC2 Logic die 81 89 103 103 107
107 111
FPC 3 EA3_HMC2 DRAM botm 76 84 98 98 102
102 106
FPC 4 Intake 46 55 65 60 81
76 90
FPC 4 Exhaust A 61 70 80 75 100
95 110
FPC 4 Exhaust B 61 70 80 75 95
90 105
FPC 4 EA0 Chip 86 95 105 100 117
112 123
FPC 4 EA0_XR0 Chip 86 95 105 100 110
105 116
FPC 4 EA0_XR1 Chip 86 95 105 100 115
110 121
FPC 4 EA1 Chip 86 95 105 100 117
112 123
FPC 4 EA1_XR0 Chip 86 95 105 100 110
105 116
FPC 4 EA1_XR1 Chip 86 95 105 100 115
110 121
FPC 4 PCIE_SW Chip 81 90 105 100 115
110 121
FPC 4 EA0_HMC0 DRAM botm 86 95 105 100 115
110 121
FPC 4 EA0_HMC1 DRAM botm 86 95 105 100 115
110 121
FPC 4 EA1_HMC0 DRAM botm 86 95 105 100 115
110 121
FPC 4 EA1_HMC1 DRAM botm 86 95 105 100 115
110 121
FPC 7 Intake 53 59 72 67 80
75 85
FPC 7 Exhaust A 77 85 98 93 103
98 108
FPC 7 Exhaust B 54 62 80 75 103
98 108
FPC 7 EA0 Chip 64 72 90 90 100
100 105
FPC 7 EA0_XR0 Chip 79 87 102 102 106
106 108
FPC 7 EA0_XR1 Chip 79 87 102 102 106
106 108
FPC 7 EA1 Chip 64 72 90 90 100
100 105
FPC 7 EA1_XR0 Chip 79 87 102 102 106
106 108
FPC 7 EA1_XR1 Chip 79 87 102 102 106
106 108
FPC 7 PEX Chip 74 82 100 100 105
105 110
FPC 7 EA2 Chip 64 72 90 90 100
100 105
FPC 7 EA2_XR0 Chip 79 87 102 102 106
106 108
FPC 7 EA2_XR1 Chip 79 87 102 102 106
106 108
FPC 7 EA3 Chip 64 72 90 90 100
100 105
FPC 7 EA3_XR0 Chip 79 87 102 102 106
106 108
FPC 7 EA3_XR1 Chip 79 87 102 102 106
106 108
FPC 7 EA0_HMC0 Logic die 81 89 103 103 107
107 111
FPC 7 EA0_HMC0 DRAM botm 76 84 98 98 102
102 106
FPC 7 EA0_HMC1 Logic die 81 89 103 103 107
107 111
FPC 7 EA0_HMC1 DRAM botm 76 84 98 98 102
102 106
FPC 7 EA0_HMC2 Logic die 81 89 103 103 107
107 111
FPC 7 EA0_HMC2 DRAM botm 76 84 98 98 102
102 106
FPC 7 EA1_HMC0 Logic die 81 89 103 103 107
107 111
FPC 7 EA1_HMC0 DRAM botm 76 84 98 98 102
102 106
FPC 7 EA1_HMC1 Logic die 81 89 103 103 107
107 111
FPC 7 EA1_HMC1 DRAM botm 76 84 98 98 102
102 106
FPC 7 EA1_HMC2 Logic die 81 89 103 103 107
107 111
FPC 7 EA1_HMC2 DRAM botm 76 84 98 98 102
102 106
FPC 7 EA2_HMC0 Logic die 81 89 103 103 107
107 111
FPC 7 EA2_HMC0 DRAM botm 76 84 98 98 102
102 106
FPC 7 EA2_HMC1 Logic die 81 89 103 103 107
107 111
FPC 7 EA2_HMC1 DRAM botm 76 84 98 98 102
102 106
FPC 7 EA2_HMC2 Logic die 81 89 103 103 107
107 111
FPC 7 EA2_HMC2 DRAM botm 76 84 98 98 102
102 106
FPC 7 EA3_HMC0 Logic die 81 89 103 103 107
107 111
FPC 7 EA3_HMC0 DRAM botm 76 84 98 98 102
102 106
FPC 7 EA3_HMC1 Logic die 81 89 103 103 107
107 111
FPC 7 EA3_HMC1 DRAM botm 76 84 98 98 102
102 106
FPC 7 EA3_HMC2 Logic die 81 89 103 103 107
107 111
FPC 7 EA3_HMC2 DRAM botm 76 84 98 98 102
102 106
As per the above output, the MPC7E, MPC8E, and MPC9E are installed in the FPC slots
4, 7, and 3, respectively.
(degrees C)
Item Normal High Normal Bad fan Normal Bad fan
Normal
Routing Engine 0 CPU 58 63 78 75 93 90
98
Routing Engine 1 CPU 58 63 78 75 93 90
98
CB 0 Inlet1 55 60 65 62 75 72
85
CB 0 Inlet2 45 50 61 58 80 77
90
CB 0 Inlet3 57 62 68 65 80 77
90
CB 0 Inlet4 55 60 80 77 90 87
95
CB 0 Exhaust1 55 60 65 62 75 72
85
CB 0 Exhaust2 50 55 60 57 80 77
90
CB 0 Exhaust3 70 75 81 78 91 88
96
CB 0 Exhaust4 75 80 90 87 100 97
105
CB 1 Inlet1 55 60 65 62 75 72
85
CB 1 Inlet2 45 50 61 58 80 77
90
CB 1 Inlet3 57 62 68 65 80 77
90
CB 1 Inlet4 55 60 80 77 90 87
95
CB 1 Exhaust1 55 60 65 62 75 72
85
CB 1 Exhaust2 50 55 60 57 80 77
90
CB 1 Exhaust3 70 75 81 78 91 88
96
CB 1 Exhaust4 75 80 90 87 100 97
105
SFB 0 Inlet1 49 54 62 59 76 73
81
SFB 0 Inlet2 65 70 71 68 83 80
88
SFB 0 Exhaust1 45 50 61 58 75 72
80
SFB 0 Exhaust2 60 65 69 66 80 77
85
SFB 0 SFB2-PF-local 65 70 75 72 95 92
100
SFB 0 SFB2-PF-die 88 93 98 95 118 115
120
SFB 1 Inlet1 49 54 62 59 76 73
81
SFB 1 Inlet2 65 70 71 68 83 80
88
SFB 1 Exhaust1 45 50 61 58 75 72
80
SFB 1 Exhaust2 60 65 69 66 80 77
85
SFB 1 SFB2-PF-local 65 70 75 72 95 92
100
SFB 1 SFB2-PF-die 88 93 98 95 118 115
120
SFB 2 Inlet1 49 54 62 59 76 73
81
SFB 2 Inlet2 65 70 71 68 83 80
88
SFB 2 Exhaust1 45 50 61 58 75 72
80
SFB 2 Exhaust2 60 65 69 66 80 77
85
SFB 2 SFB2-PF-local 65 70 75 72 95 92
100
SFB 2 SFB2-PF-die 88 93 98 95 118 115
120
SFB 3 Inlet1 49 54 62 59 76 73
81
SFB 3 Inlet2 65 70 71 68 83 80
88
SFB 3 Exhaust1 45 50 61 58 75 72
80
SFB 3 Exhaust2 60 65 69 66 80 77
85
SFB 3 SFB2-PF-local 65 70 75 72 95 92
100
SFB 3 SFB2-PF-die 88 93 98 95 118 115
120
SFB 4 Inlet1 49 54 62 59 76 73
81
SFB 4 Inlet2 65 70 71 68 83 80
88
SFB 4 Exhaust1 45 50 61 58 75 72
80
SFB 4 Exhaust2 60 65 69 66 80 77
85
SFB 4 SFB2-PF-local 65 70 75 72 95 92
100
SFB 4 SFB2-PF-die 88 93 98 95 118 115
120
SFB 5 Inlet1 49 54 62 59 76 73
81
SFB 5 Inlet2 65 70 71 68 83 80
88
SFB 5 Exhaust1 45 50 61 58 75 72
80
SFB 5 Exhaust2 60 65 69 66 80 77
85
SFB 5 SFB2-PF-local 65 70 75 72 95 92
100
SFB 5 SFB2-PF-die 88 93 98 95 118 115
120
SFB 6 Inlet1 49 54 62 59 76 73
81
SFB 6 Inlet2 65 70 71 68 83 80
88
SFB 6 Exhaust1 45 50 61 58 75 72
80
SFB 6 Exhaust2 60 65 69 66 80 77
85
SFB 6 SFB2-PF-local 65 70 75 72 95 92
100
SFB 6 SFB2-PF-die 88 93 98 95 118 115
120
SFB 7 Inlet1 49 54 62 59 76 73
81
SFB 7 Inlet2 65 70 71 68 83 80
88
SFB 7 Exhaust1 45 50 61 58 75 72
80
SFB 7 Exhaust2 60 65 69 66 80 77
85
SFB 7 SFB2-PF-local 65 70 75 72 95 92
100
SFB 7 SFB2-PF-die 88 93 98 95 118 115
120
FPC 0 55 60 75 65 90 80
95
FPC 3 55 60 75 65 105 80
110
FPC 5 55 60 75 65 105 80
110
FPC 7 55 60 75 65 90 80
95
FPC 9 Intake 60 65 75 75 85 85
95
FPC 9 Exhaust A 60 65 75 75 85 85
95
FPC 9 Exhaust B 60 65 75 75 85 85
95
FPC 9 XL 0 Chip 70 75 85 85 102 102
110
FPC 9 XL 0 XR2 0 Chip 75 80 90 90 105 105
115
FPC 9 XL 0 XR2 1 Chip 75 80 90 90 105 105
115
FPC 9 XL 1 Chip 70 75 85 85 102 102
110
FPC 9 XL 1 XR2 0 Chip 75 80 90 90 105 105
115
FPC 9 XL 1 XR2 1 Chip 75 80 90 90 105 105
115
FPC 9 XM 0 Chip 70 75 85 85 100 100
110
FPC 9 XM 1 Chip 70 75 85 85 100 100
110
FPC 9 XM 2 Chip 70 75 85 85 100 100
110
FPC 9 XM 3 Chip 70 75 85 85 100 100
110
FPC 9 PCIe Switch Chip 80 85 95 95 105 105
120
ADC 0 Intake 50 55 65 65 75 75
80
ADC 0 Exhaust 50 55 65 65 75 75
80
ADC 0 ADC-XF1 70 75 90 85 95 90
100
ADC 0 ADC-XF0 70 75 90 85 95 90
100
ADC 3 Intake 50 55 65 65 75 75
80
ADC 3 Exhaust 50 55 65 65 75 75
80
ADC 3 ADC-XF1 70 75 90 85 95 90
100
ADC 3 ADC-XF0 70 75 90 85 95 90
100
ADC 5 Intake 50 55 65 65 75 75
80
ADC 5 Exhaust 50 55 65 65 75 75
80
ADC 5 ADC-XF1 70 75 90 85 95 90
100
ADC 5 ADC-XF0 70 75 90 85 95 90
100
ADC 7 Intake 50 55 65 65 75 75
80
ADC 7 Exhaust 50 55 65 65 75 75
80
ADC 7 ADC-XF1 70 75 90 85 95 90
100
ADC 7 ADC-XF0 70 75 90 85 95 90
100
90 100
FPC EA0_HMC0 Logic die 85 90 95 95 105
105 110
FPC EA0_HMC0 DRAM botm 80 85 90 90 105
105 110
FPC EA0_HMC1 Logic die 85 90 95 95 105
105 110
FPC EA0_HMC1 DRAM botm 80 85 90 90 105
105 110
FPC EA0 Chip 92 97 103 103 109
109 115
FPC EA0-XR0 Chip 85 90 98 98 103
103 110
FPC EA0-XR1 Chip 85 90 98 98 103
103 110
sfc0-re0:
--------------------------------------------------------------------------
Fan speed Yellow alarm Red alarm
(degrees C) (degrees C) (degrees C)
Item Normal High Normal Bad fan Normal Bad fan
Chassis default 48 54 65 55 75 65
Routing Engine 0 55 65 85 85 100 100
Routing Engine 1 55 65 85 85 100 100
SIB F13 0 64 70 76 72 90 84
SIB F13 3 64 70 76 72 90 84
SIB F13 6 64 70 76 72 90 84
SIB F13 8 64 70 76 72 90 84
SIB F13 11 64 70 76 72 90 84
SIB F13 12 64 70 76 72 90 84
SIB F2S 16 64 70 76 72 90 84
SIB F2S 17 64 70 76 72 90 84
SIB F2S 18 64 70 76 72 90 84
SIB F2S 19 64 70 76 72 90 84
SIB F2S 20 64 70 76 72 90 84
SIB F2S 21 64 70 76 72 90 84
SIB F2S 22 64 70 76 72 90 84
SIB F2S 23 64 70 76 72 90 84
SIB F2S 24 64 70 76 72 90 84
SIB F2S 25 64 70 76 72 90 84
SIB F2S 26 64 70 76 72 90 84
SIB F2S 27 64 70 76 72 90 84
SIB F2S 28 64 70 76 72 90 84
SIB F2S 29 64 70 76 72 90 84
SIB F2S 30 64 70 76 72 90 84
SIB F2S 31 64 70 76 72 90 84
SIB F2S 32 64 70 76 72 90 84
SIB F2S 33 64 70 76 72 90 84
SIB F2S 34 64 70 76 72 90 84
SIB F2S 35 64 70 76 72 90 84
lcc0-re0:
--------------------------------------------------------------------------
Fan speed Yellow alarm Red alarm
(degrees C) (degrees C) (degrees C)
Item Normal High Normal Bad fan Normal Bad fan
Chassis default 48 54 65 55 75 65
Routing Engine 0 55 65 85 85 100 100
Routing Engine 1 55 65 85 85 100 100
FPC 1 56 62 75 63 83 76
FPC 3 56 62 75 63 83 76
FPC 4 56 62 75 63 83 76
FPC 6 56 62 75 63 83 76
FPC 7 56 62 75 63 83 76
SIB 0 48 54 65 60 80 75
SIB 1 48 54 65 60 80 75
SIB 2 48 54 65 60 80 75
SIB 3 48 54 65 60 80 75
SIB 4 48 54 65 60 80 75
lcc1-re0:
--------------------------------------------------------------------------
Fan speed Yellow alarm Red alarm
(degrees C) (degrees C) (degrees C)
Item Normal High Normal Bad fan Normal Bad fan
Chassis default 48 54 65 55 75 65
Routing Engine 0 55 65 85 85 100 100
Routing Engine 1 55 65 85 85 100 100
FPC 1 56 62 75 63 83 76
FPC 3 56 62 75 63 83 76
FPC 4 56 62 75 63 83 76
FPC 6 56 62 75 63 83 76
...
lcc1-re0:
--------------------------------------------------------------------------
Fan speed Yellow alarm Red alarm
(degrees C) (degrees C) (degrees C)
Item Normal High Normal Bad fan Normal Bad fan
Chassis default 48 54 65 55 75 65
Routing Engine 0 55 65 85 85 100 100
Routing Engine 1 55 65 85 85 100 100
FPC 1 56 62 75 63 83 76
FPC 3 56 62 75 63 83 76
FPC 4 56 62 75 63 83 76
FPC 6 56 62 75 63 83 76
SIB 0 48 54 65 60 80 75
SIB 1 48 54 65 60 80 75
SIB 2 48 54 65 60 80 75
SIB 3 48 54 65 60 80 75
SIB 4 48 54 65 60 80 75
sfc0-re0:
--------------------------------------------------------------------------
Fan speed Yellow alarm Red alarm
(degrees C) (degrees C) (degrees C)
Item Normal High Normal Bad fan Normal Bad fan
Chassis default 48 54 65 55 75 65
Routing Engine 0 55 65 85 85 100 100
Routing Engine 1 55 65 85 85 100 100
SIB F13 0 64 70 76 72 90 84
SIB F13 3 64 70 76 72 90 84
SIB F13 6 64 70 76 72 90 84
SIB F13 8 64 70 76 72 90 84
SIB F13 11 64 70 76 72 90 84
SIB F13 12 64 70 76 72 90 84
SIB F2S 16 64 70 76 72 90 84
SIB F2S 17 64 70 76 72 90 84
SIB F2S 18 64 70 76 72 90 84
SIB F2S 19 64 70 76 72 90 84
SIB F2S 20 64 70 76 72 90 84
SIB F2S 21 64 70 76 72 90 84
SIB F2S 22 64 70 76 72 90 84
SIB F2S 23 64 70 76 72 90 84
SIB F2S 24 64 70 76 72 90 84
SIB F2S 25 64 70 76 72 90 84
SIB F2S 26 64 70 76 72 90 84
SIB F2S 27 64 70 76 72 90 84
SIB F2S 28 64 70 76 72 90 84
SIB F2S 29 64 70 76 72 90 84
SIB F2S 30 64 70 76 72 90 84
SIB F2S 31 64 70 76 72 90 84
SIB F2S 32 64 70 76 72 90 84
SIB F2S 33 64 70 76 72 90 84
SIB F2S 34 64 70 76 72 90 84
SIB F2S 35 64 70 76 72 90 84
sfc0-re0:
--------------------------------------------------------------------------
Fan speed Yellow alarm Red alarm Fire
Shutdown
(degrees C) (degrees C) (degrees C)
(degrees C)
lcc0-re0:
--------------------------------------------------------------------------
Fan speed Yellow alarm Red alarm Fire
Shutdown
(degrees C) (degrees C) (degrees C)
(degrees C)
Item Normal High Normal Bad fan Normal Bad fan
Normal
Chassis default 48 54 65 55 75 65
100
Routing Engine 0 55 65 85 85 100 100
102
FPC 0 63 68 75 70 90 83
95
FPC 1 56 62 75 63 83 76
95
FPC 7 56 62 75 63 83 76
95
SIB 0 64 70 76 72 87 84
95
SIB 0 ASIC Junction 63 68 75 70 105 100
107
SIB 2 64 70 76 72 87 84
95
SIB 2 ASIC Junction 63 68 75 70 105 100
107
SIB 3 64 70 76 72 87 84
95
SIB 3 ASIC Junction 63 68 75 70 105 100
107
SIB 2 Exhaust 60 65 78 75 85 80
95
SIB 2 Junction 75 80 90 85 105 95
115
SIB 3 Exhaust 60 65 78 75 85 80
95
SIB 3 Junction 75 80 90 85 105 95
115
SIB 4 Exhaust 60 65 78 75 85 80
95
SIB 4 Junction 75 80 90 85 105 95
115
SIB 5 Exhaust 60 65 78 75 85 80
95
SIB 5 Junction 75 80 90 85 105 95
115
SIB 6 Exhaust 60 65 78 75 85 80
95
SIB 6 Junction 75 80 90 85 105 95
115
SIB 7 Exhaust 60 65 78 75 85 80
95
SIB 7 Junction 75 80 90 85 105 95
115
SIB 8 Exhaust 60 65 78 75 85 80
95
SIB 8 Junction 75 80 90 85 105 95
115
show chassis temperature-thresholds (MX Routers with Media Services Blade [MSB])
user@switch> show chassis temperature-thresholds
85 95
CB CPU Core-0 Temp 65 70 80 80 90
90 100
CB CPU Core-1 Temp 65 70 80 80 90
90 100
CB CPU Core-2 Temp 65 70 80 80 90
90 100
CB CPU Core-3 Temp 65 70 80 80 90
90 100
CB CPU Core-4 Temp 65 70 80 80 90
90 100
CB CPU Core-5 Temp 65 70 80 80 90
90 100
CB CPU Core-6 Temp 65 70 80 80 90
90 100
CB CPU Core-7 Temp 65 70 80 80 90
90 100
FPC EA0_HMC0 Logic die 85 90 95 95 105
105 110
FPC EA0_HMC0 DRAM botm 80 85 90 90 105
105 110
FPC EA0_HMC1 Logic die 85 90 95 95 105
105 110
FPC EA0_HMC1 DRAM botm 80 85 90 90 105
105 110
FPC EA0 Chip 92 97 103 103 109
109 115
FPC EA0-XR0 Chip 85 90 98 98 103
103 110
FPC EA0-XR1 Chip 85 90 98 98 103
103 110
90 100
FPC 0 Exhaust-B Temp Sensor 55 60 85 80 90
90 100
FPC 0 EA0 Chip 87 92 97 97 105
105 110
FPC 0 EA0-XR0 Chip 88 93 98 98 120
120 125
FPC 0 EA0-XR1 Chip 88 93 98 98 120
120 125
FPC 0 EA1 Chip 87 92 97 97 105
105 110
FPC 0 EA1-XR0 Chip 88 93 98 98 120
120 125
FPC 0 EA1-XR1 Chip 88 93 98 98 120
120 125
FPC 0 EA2 Chip 87 92 97 97 105
105 110
FPC 0 EA2-XR0 Chip 88 93 98 98 120
120 125
FPC 0 EA2-XR1 Chip 88 93 98 98 120
120 125
FPC 0 PF Chip 89 94 104 104 120
120 120
FPC 0 EA0_HMC0 Logic die 88 93 103 103 120
120 125
FPC 0 EA0_HMC0 DRAM botm 83 88 98 98 120
120 125
FPC 0 EA0_HMC1 Logic die 88 93 103 103 120
120 125
FPC 0 EA0_HMC1 DRAM botm 83 88 98 98 120
120 125
FPC 0 EA0_HMC2 Logic die 88 93 103 103 120
120 125
FPC 0 EA0_HMC2 DRAM botm 83 88 98 98 120
120 125
FPC 0 EA1_HMC0 Logic die 88 93 103 103 120
120 125
FPC 0 EA1_HMC0 DRAM botm 83 88 98 98 120
120 125
FPC 0 EA1_HMC1 Logic die 88 93 103 103 120
120 125
FPC 0 EA1_HMC1 DRAM botm 83 88 98 98 120
120 125
FPC 0 EA1_HMC2 Logic die 88 93 103 103 120
120 125
FPC 0 EA1_HMC2 DRAM botm 83 88 98 98 120
120 125
FPC 0 EA2_HMC0 Logic die 88 93 103 103 120
120 125
FPC 0 EA2_HMC0 DRAM botm 83 88 98 98 120
120 125
FPC 0 EA2_HMC1 Logic die 88 93 103 103 120
120 125
FPC 0 EA2_HMC1 DRAM botm 83 88 98 98 120
120 125
FPC 0 EA2_HMC2 Logic die 88 93 103 103 120
120 125
FPC 0 EA2_HMC2 DRAM botm 83 88 98 98 120
120 125
FPC 1 Intake Temp Sensor 40 45 75 70 85
80 95
FPC 1 Exhaust-A Temp Sensor 55 60 85 80 90
90 100
FPC 1 Exhaust-B Temp Sensor 55 60 85 80 90
90 100
FPC 1 EA0 Chip 87 92 97 97 105
105 110
FPC 1 EA0-XR0 Chip 88 93 98 98 120
120 125
FPC 1 EA0-XR1 Chip 88 93 98 98 120
120 125
FPC 1 EA1 Chip 87 92 97 97 105
105 110
FPC 1 EA1-XR0 Chip 88 93 98 98 120
120 125
FPC 1 EA1-XR1 Chip 88 93 98 98 120
120 125
FPC 1 EA2 Chip 87 92 97 97 105
105 110
FPC 1 EA2-XR0 Chip 88 93 98 98 120
120 125
FPC 1 EA2-XR1 Chip 88 93 98 98 120
120 125
FPC 1 PF Chip 89 94 104 104 120
120 120
FPC 1 EA0_HMC0 Logic die 88 93 103 103 120
120 125
FPC 1 EA0_HMC0 DRAM botm 83 88 98 98 120
120 125
FPC 1 EA0_HMC1 Logic die 88 93 103 103 120
120 125
FPC 1 EA0_HMC1 DRAM botm 83 88 98 98 120
120 125
FPC 1 EA0_HMC2 Logic die 88 93 103 103 120
120 125
FPC 1 EA0_HMC2 DRAM botm 83 88 98 98 120
120 125
FPC 1 EA1_HMC0 Logic die 88 93 103 103 120
120 125
FPC 1 EA1_HMC0 DRAM botm 83 88 98 98 120
120 125
FPC 1 EA1_HMC1 Logic die 88 93 103 103 120
120 125
FPC 1 EA1_HMC1 DRAM botm 83 88 98 98 120
120 125
FPC 1 EA1_HMC2 Logic die 88 93 103 103 120
120 125
FPC 1 EA1_HMC2 DRAM botm 83 88 98 98 120
120 125
FPC 1 EA2_HMC0 Logic die 88 93 103 103 120
120 125
FPC 1 EA2_HMC0 DRAM botm 83 88 98 98 120
120 125
FPC 1 EA2_HMC1 Logic die 88 93 103 103 120
120 125
FPC 1 EA2_HMC1 DRAM botm 83 88 98 98 120
120 125
FPC 1 EA2_HMC2 Logic die 88 93 103 103 120
120 125
Release Information Command introduced in Junos OS Release 14.2R3 for Junos Fusion Provider Edge.
Command introduced in Junos OS Release 16.1R1 for Junos Fusion Enterprise.
Command introduced in Junos OS Release 17.2R1 for Junos Fusion Enterprise.
Options device-alias device-alias—Display extended port information for the satellite device
using the specified device alias only.
all—Display information for all extended ports and aggregated Ethernet interfaces with
extended ports as members configured on all of the satellite devices.
List of Sample Output show interfaces extensive satellite-device all on page 499
Output Fields Table 28 on page 493 lists the output fields for the show interfaces extensive satellite-device
command. Output fields are listed in the approximate order in which they appear.
Physical Interface
Physical interface Name of the physical interface. All levels
Interface index Index number of the physical interface, which reflects its initialization sequence. detail extensive none
NOTE: This field is only displayed if asymmetric flow control is not configured.
Last flapped Date, time, and how long ago the interface went from down to up. The format detail extensive none
is Last flapped: year-month-day hour: :minute:second:timezone (hour:minute:second
ago). For example, Last flapped: 2008–01–16 10:52:40 UTC (3d 22:58 ago).
Statistics last Time when the statistics for the interface were last set to zero. detail extensive
cleared
Traffic statistics Number and rate of bytes and packets received and transmitted on the physical detail extensive
interface.
IPv6 transit Number and rate of bytes and packets received and transmitted on the physical detail extensive
statistics interface.
Input errors Input errors on the interface. The following paragraphs explain the counters extensive
whose meaning might not be obvious:
Output errors Output errors on the interface. The following paragraphs explain the counters extensive
whose meaning might not be obvious:
• Carrier transitions—Number of times the interface has gone from down to up.
This number does not normally increment quickly, increasing only when the
cable is unplugged, the far-end system is powered down and then up, or
another problem occurs. If the number of carrier transitions increments quickly
(perhaps once every 10 seconds), the cable, the far-end system, or the PIC
or PIM is malfunctioning.
• Errors—Sum of the outgoing frame aborts and FCS errors.
• Drops—Number of packets dropped by the output queue of the I/O Manager
ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.
• MTU errors—Number of packets whose size exceeded the MTU of the interface.
• Resource errors—Sum of transmit drops.
Egress queues Total number of egress queues supported on the specified interface. detail extensive
Queue counters CoS queue number and its associated user-configured forwarding class name. detail extensive
Queue Number The CoS queue number and the forwarding classes mapped to the queue detail extensive
number. The Mapped forwarding class column lists the forwarding classes
mapped to each CoS queue.
Active alarms and Ethernet-specific defects that can prevent the interface from passing packets. detail extensive none
Active defects When a defect persists for a certain amount of time, it is promoted to an alarm.
Based on the switch configuration, an alarm can ring the red or yellow alarm
bell on the switch, or turn on the red or yellow alarm LED on the craft interface.
These fields can contain the value None or Link.
MAC statistics Receive and Transmit statistics reported by the PIC's MAC subsystem. extensive
• Total octets and total packets—Total number of octets and packets. For
Gigabit Ethernet IQ PICs, the received octets count varies by interface type.
• Unicast packets, Broadcast packets, and Multicast packets—Number of unicast,
broadcast, and multicast packets.
• CRC/Align errors—Total number of packets received that had a length
(excluding framing bits, but including FCS octets) of between 64 and 1518
octets, inclusive, and had either a bad FCS with an integral number of octets
(FCS Error) or a bad FCS with a nonintegral number of octets (Alignment
Error).
• FIFO error—Number of FIFO errors that are reported by the ASIC on the PIC.
If this value is ever nonzero, the PIC is probably malfunctioning.
• MAC control frames—Number of MAC control frames.
• MAC pause frames—Number of MAC control frames with pause operational
code.
• Oversized frames—Number of packets that exceeds the configured MTU.
• Jabber frames—Number of frames that were longer than 1518 octets (excluding
framing bits, but including FCS octets), and had either an FCS error or an
alignment error. This definition of jabber is different from the definition in
IEEE-802.3 section 8.2.1.5 (10BASE5) and section 10.3.1.4 (10BASE2). These
documents define jabber as the condition in which any packet exceeds 20
ms. The allowed range to detect jabber is from 20 ms to 150 ms.
• Fragment frames—Total number of packets that were less than 64 octets in
length (excluding framing bits, but including FCS octets), and had either an
FCS error or an alignment error. Fragment frames normally increment because
both runts (which are normal occurrences caused by collisions) and noise
hits are counted.
• VLAN tagged frames—Number of frames that are VLAN tagged. The system
uses the TPID of 0x8100 in the frame to determine whether a frame is tagged
or not. This counter is not supported on EX Series switches and is always
displayed as 0.
• Code violations—Number of times an event caused the PHY to indicate “Data
reception error” or “invalid data symbol error.”
Filter statistics Receive and Transmit statistics reported by the PIC's MAC address filter extensive
subsystem.
Packet Forwarding Information about the configuration of the Packet Forwarding Engine: extensive
Engine
configuration • Destination slot—FPC slot number.
• CoS transmit queue—Queue number and its associated user-configured
forwarding class name.
Logical Interface
Logical interface Name of the logical interface. All levels
Index Index number of the logical interface, which reflects its initialization sequence. detail extensive none
SNMP ifIndex SNMP interface index number for the logical interface. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Bundle Provide information for each active bundle link. All levels
• Input
• Packets—
• pps
• Bytes
• bps
• Output
• Packets—
• pps
• Bytes
• bps
LACP info LACP state information for each aggregated interface: All levels
LACP Statistics LACP statistics are returned when the extensive option is used and provides the All levels
following information:
• LACP Rx—LACP received counter that increments for each normal hello.
• LACP Tx—Number of LACP transmit packet errors logged.
• Unknown Rx—Number of unrecognized packet errors logged.
• Illegal Rx—Number of invalid packets received.
Marker statistics Marker statistics are returned when the extensive option is used and provides All levels
the following information:
• Marker Rx—Marker received counter that increments for each normal hello.
• Resp Tx—Number of RESP transmit packet errors logged.
• Unknown Rx—Number of unrecognized packet errors logged.
• Illegal Rx—Number of invalid packets received.
MTU MTU size on the logical interface. If the MTU value is negotiated down to meet All levels
the MRRU requirement on the remote side, this value is marked Adjusted.
Generation Unique number for use by Juniper Networks technical support only. All levels
Route table Routing table in which this address exists. For example, Route table:0 refers to All levels
inet.0.
Sample Output
0 0 95867 0
1 0 0 0
2 0 0 0
3 0 0 0
4 0 0 0
5 0 0 0
7 0 0 0
7 be-2
Logical interface ae0.0 (Index 337) (SNMP ifIndex 575) (Generation 1194)
Flags: Up SNMP-Traps 0x24024000 Encapsulation: Ethernet-Bridge
Statistics Packets pps Bytes bps
Bundle:
Input : 1729 0 601692 0
Output: 0 0 0 0
Adaptive Statistics:
Adaptive Adjusts: 0
Adaptive Scans : 0
Adaptive Updates: 0
Link:
ge-104/0/24.0
Input : 0 0 0 0
Output: 0 0 0 0
ge-103/0/0.0
Input : 1729 0 601692 0
Output: 0 0 0 0
LACP info: Role System System Port Port Port
Output bytes : 0
Input packets: 0
Output packets: 0
Input errors:
Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Giants: 0, Policed discards:
0, Resource errors: 0
Output errors:
Carrier transitions: 0, Errors: 0, Drops: 0, MTU errors: 0, Resource errors:
0
Egress queues: 8 supported, 7 in use
Queue counters: Queued packets Transmitted packets Dropped packets
0 0 94909 0
1 0 0 0
2 0 0 0
3 0 0 0
4 0 0 0
5 0 0 0
7 0 0 0
Logical interface ae1.0 (Index 338) (SNMP ifIndex 1216) (Generation 1195)
Flags: Up SNMP-Traps 0x24024000 Encapsulation: Ethernet-Bridge
Statistics Packets pps Bytes bps
Bundle:
Input : 2785 0 688380 0
Output: 0 0 0 0
Adaptive Statistics:
Adaptive Adjusts: 0
Adaptive Scans : 0
Adaptive Updates: 0
Link:
ge-104/0/25.0
Input : 10 0 600 0
Output: 0 0 0 0
ge-103/0/1.0
Input : 2775 0 687780 0
Output: 0 0 0 0
LACP info: Role System System Port Port Port
0 0 95867 0
1 0 0 0
2 0 0 0
3 0 0 0
4 0 0 0
5 0 0 0
7 0 0 0
0 FC0
1 FC1
2 FC2
3 FC3
4 FC4
5 FC5, be-3
7 be-2
Logical interface ae0.0 (Index 337) (SNMP ifIndex 575) (Generation 1194)
Flags: Up SNMP-Traps 0x24024000 Encapsulation: Ethernet-Bridge
Statistics Packets pps Bytes bps
Bundle:
Input : 1729 0 601692 0
Output: 0 0 0 0
Adaptive Statistics:
Adaptive Adjusts: 0
Adaptive Scans : 0
Adaptive Updates: 0
Link:
ge-104/0/24.0
Input : 0 0 0 0
Output: 0 0 0 0
ge-103/0/0.0
Input : 1729 0 601692 0
Output: 0 0 0 0
LACP info: Role System System Port Port Port
0 0 94909 0
1 0 0 0
2 0 0 0
3 0 0 0
4 0 0 0
5 0 0 0
7 0 0 0
Logical interface ae1.0 (Index 338) (SNMP ifIndex 1216) (Generation 1195)
Flags: Up SNMP-Traps 0x24024000 Encapsulation: Ethernet-Bridge
Statistics Packets pps Bytes bps
Bundle:
Input : 2785 0 688380 0
Output: 0 0 0 0
Adaptive Statistics:
Adaptive Adjusts: 0
Adaptive Scans : 0
Adaptive Updates: 0
Link:
ge-104/0/25.0
Input : 10 0 600 0
Output: 0 0 0 0
ge-103/0/1.0
Input : 2775 0 687780 0
Output: 0 0 0 0
LACP info: Role System System Port Port Port
0 0 95867 0
1 0 0 0
2 0 0 0
3 0 0 0
4 0 0 0
5 0 0 0
7 0 0 0
Logical interface ae0.0 (Index 337) (SNMP ifIndex 575) (Generation 1194)
Flags: Up SNMP-Traps 0x24024000 Encapsulation: Ethernet-Bridge
Statistics Packets pps Bytes bps
Bundle:
Input : 1729 0 601692 0
Output: 0 0 0 0
Adaptive Statistics:
Adaptive Adjusts: 0
Adaptive Scans : 0
Adaptive Updates: 0
Link:
ge-104/0/24.0
Input : 0 0 0 0
Output: 0 0 0 0
ge-103/0/0.0
Input : 1729 0 601692 0
Output: 0 0 0 0
LACP info: Role System System Port Port Port
0 0 94909 0
1 0 0 0
2 0 0 0
3 0 0 0
4 0 0 0
5 0 0 0
7 0 0 0
Logical interface ae1.0 (Index 338) (SNMP ifIndex 1216) (Generation 1195)
Flags: Up SNMP-Traps 0x24024000 Encapsulation: Ethernet-Bridge
Statistics Packets pps Bytes bps
Bundle:
Input : 2785 0 688380 0
Output: 0 0 0 0
Adaptive Statistics:
Adaptive Adjusts: 0
Adaptive Scans : 0
Adaptive Updates: 0
Link:
ge-104/0/25.0
Input : 10 0 600 0
Output: 0 0 0 0
ge-103/0/1.0
Input : 2775 0 687780 0
Output: 0 0 0 0
LACP info: Role System System Port Port Port
0 0 0 0
1 0 0 0
2 0 0 0
3 0 0 0
4 0 0 0
5 0 0 0
7 0 0 0
0 0 0 0
1 0 0 0
2 0 0 0
3 0 0 0
4 0 0 0
5 0 0 0
7 0 0 0
Release Information Command introduced in Junos OS Release 14.2R3 for Junos Fusion Provider Edge.
Command introduced in Junos OS Release 16.1R1 for Junos Fusion Enterprise.
Command introduced in Junos OS Release 17.2R1 for Junos Fusion Data Center.
Options device-alias device-alias—Display extended port information for the satellite device
using the specified device alias only.
all—Display information for all extended ports and aggregated Ethernet interfaces with
extended ports as members configured on all of the satellite devices.
Output Fields Table 29 on page 512 lists the output fields for the show interfaces satellite-device
command. Output fields are listed in the approximate order in which they appear.
Physical Interface
Physical interface Name of the physical interface. All levels
Interface index Index number of the physical interface, which reflects its initialization sequence. detail extensive none
Link-level type Encapsulation being used on the physical interface. All levels
NOTE: This field is only displayed if asymmetric flow control is not configured.
Last flapped Date, time, and how long ago the interface went from down to up. The format detail extensive none
is Last flapped: year-month-day hour: :minute:second:timezone (hour:minute:second
ago). For example, Last flapped: 2008–01–16 10:52:40 UTC (3d 22:58 ago).
Input rate Input rate in bits per second (bps) and packets per second (pps). The value in All levels
this field also includes the Layer 2 overhead bytes for ingress traffic on Ethernet
interfaces if you enable accounting of Layer 2 overhead at the PIC level or the
logical interface level.
Output rate Output rate in bps and pps. The value in this field also includes the Layer 2 All levels
overhead bytes for egress traffic on Ethernet interfaces if you enable accounting
of Layer 2 overhead at the PIC level or the logical interface level.
Active alarms and Ethernet-specific defects that can prevent the interface from passing packets. detail extensive none
Active defects When a defect persists for a certain amount of time, it is promoted to an alarm.
Based on the switch configuration, an alarm can ring the red or yellow alarm
bell on the switch, or turn on the red or yellow alarm LED on the craft interface.
These fields can contain the value None or Link.
Logical Interface
Logical interface Name of the logical interface. All levels
Index Index number of the logical interface, which reflects its initialization sequence. detail extensive none
SNMP ifIndex SNMP interface index number for the logical interface. detail extensive none
Generation Unique number for use by Juniper Networks technical support only. detail extensive
Bundle Provides information for each active bundle link. All levels
• Input
• Packets
• pps
• Bytes
• bps
• Output
• Packets—
• pps
• Bytes
• bps
Sample Output
Sample Output
• Total statistics (sum of transit and local statistics) at the physical interface
level
List of Sample Output show interfaces statistics (Fast Ethernet) on page 518
show interfaces statistics (Gigabit Ethernet PIC—Egress) on page 519
Output Fields 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
Broadcast: 10.27.245.255
Protocol iso, MTU: 1497
Flags: Is-Primary
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
Logical interface ge-5/2/0.0 (Index 71) (SNMP ifIndex 573) (Generation 135)
Flags: SNMP-Traps 0x4000 Encapsulation: ENET2
Egress account overhead: 100
Ingress account overhead: 90
Traffic statistics:
Input bytes : 271524
Output bytes : 37769598
Input packets: 3664
Output packets: 885790
IPv6 transit statistics:
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
IPv6 transit statistics:
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
IPV6 multicast statistics:
Input bytes : 156500 0 bps
Output bytes : 16681118 0 bps
Input packets: 1818 0 pps
Output packets: 362633 0 pps
Protocol inet, MTU: 1500, Generation: 151, Route table: 0
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.40.40.0/30, Local: 10.40.40.2, Broadcast: 10.40.40.3,
Generation: 167
Protocol inet6, MTU: 1500, Generation: 152, Route table: 0
Addresses, Flags: Is-Preferred Is-Primary
Destination: ::10.40.40.0/126, Local: ::10.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__
Logical interface ae0.0 (Index 67) (SNMP ifIndex 139) (Generation 145)
Flags: SNMP-Traps Encapsulation: ENET2
Statistics Packets pps Bytes bps
Bundle:
Input : 508 0 28544 0
Output: 509 0 35698 0
Link:
ge-3/3/8.0
Input : 508 0 28544 0
Output: 0 0 0 0
ge-3/3/9.0
Input : 0 0 0 0
Output: 0 0 0 0
Marker Statistics: Marker Rx Resp Tx Unknown Rx Illegal Rx
ge-3/3/8.0 0 0 0 0
ge-3/3/9.0 0 0 0 0
Egress queues: 8 supported, 8 in use
Queue counters: Queued packets Transmitted packets Dropped packets
0 best-effort 0 0 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
3 network-cont 0 0 0
0 best-effort 0 0 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
3 network-cont 0 0 0
0 best-effort 21 21 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
Logical interface ae0.0 (Index 70) (SNMP ifIndex 574) (Generation 177)
Flags: SNMP-Traps 0x4000 Encapsulation: ENET2
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
Protocol inet, MTU: 1500, Generation: 236, Route table: 0
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.30.30.0/30, Local: 10.30.30.2, Broadcast: 10.30.30.3,
Generation: 310
Protocol inet6, MTU: 1500, Generation: 237, Route table: 0
Addresses, Flags: Is-Preferred Is-Primary
Destination: ::10.30.30.0/126, Local: ::10.30.30.2
Generation: 312
Addresses, Flags: Is-Preferred
Destination: fe80::/64, Local: fe80::21d:b5ff:fe61:dbf0
Protocol multiservice, MTU: Unlimited, Generation: 314
Generation: 238, Route table: 0
Policer: Input: __default_arp_policer__
0 best-effort 0 0 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
3 network-cont 0 0 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
3 network-cont 65 65 0
Logical interface ae0.0 (Index 72) (SNMP ifIndex 505) (Generation 204)
Flags: SNMP-Traps 0x4000 Encapsulation: ENET2
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
Protocol inet, MTU: 1500, Generation: 291, Route table: 0
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.30.30.0/30, Local: 10.30.30.1, Broadcast: 10.30.30.3,
Generation: 420
Protocol inet6, MTU: 1500, Generation: 292, Route table: 0
Addresses, Flags: Is-Preferred Is-Primary
Destination: ::/26, Local: ::10.30.30.1
Generation: 422
Addresses, Flags: Is-Preferred
Destination: fe80::/64, Local: fe80::21f:12ff:fec2:37f0
Protocol multiservice, MTU: Unlimited, Generation: 424
Generation: 293, Route table: 0
Policer: Input: __default_arp_policer__
0 best-effort 4 4 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
Logical interface so-3/0/0.0 (Index 72) (SNMP ifIndex 578) (Generation 182)
Flags: Point-To-Point SNMP-Traps 0x4000 Encapsulation: PPP
Protocol inet, MTU: 4470, Generation: 244, Route table: 0
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.30.30.0/30, Local: 10.30.30.2, Broadcast: 10.30.30.3,
Generation: 322
Protocol inet6, MTU: 4470, Generation: 245, Route table: 0
Addresses, Flags: Is-Preferred Is-Primary
Destination: ::10.30.30.0/126, Local: ::10.30.30.2
Generation: 324
Addresses, Flags: Is-Preferred
Destination: fe80::/64, Local: fe80::2a0:a5ff:fe61:9264
Generation: 326
0 best-effort 3 3 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
Logical interface as0.0 (Index 71) (SNMP ifIndex 576) (Generation 179)
Flags: Point-To-Point SNMP-Traps 0x4000 Encapsulation: PPP
Statistics Packets pps Bytes bps
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
Protocol inet, MTU: 4470, Generation: 240, Route table: 0
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.30.30.0/30, Local: 10.30.30.2, Broadcast: 10.30.30.3,
Generation: 316
Protocol inet6, MTU: 4470, Generation: 241, Route table: 0
Addresses, Flags: Is-Preferred Is-Primary
Destination: ::10.30.30.0/126, Local: ::10.30.30.2
Generation: 318
Addresses, Flags: Is-Preferred
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
3 network-cont 90 90 0
Logical interface as0.0 (Index 71) (SNMP ifIndex 548) (Generation 206)
Flags: Point-To-Point SNMP-Traps 0x4000 Encapsulation: PPP
Statistics Packets pps Bytes bps
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
Protocol inet, MTU: 4470, Generation: 295, Route table: 0
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.30.30.0/30, Local: 10.30.30.1, Broadcast: 10.30.30.3,
Generation: 426
Protocol inet6, MTU: 4470, Generation: 296, Route table: 0
show interfaces statistics (MX Series Routers: Dynamic Interfaces with RPF Check Detail)
user@host> show interfaces statistics pp0.3221225475 detail
Release Information Command introduced in Junos OS Release 14.2R3 for Junos Fusion Provider Edge.
Command introduced in Junos OS Release 16.1R1 for Junos Fusion Enterprise.
Command introduced in Junos OS Release 17.2R1 for Junos Fusion Data Center.
Options device-alias device-alias—Display extended port information for the satellite device
using the specified device alias only.
all—Display information for all extended ports and aggregated Ethernet interfaces with
extended ports as members configured on all of the satellite devices.
List of Sample Output show interfaces terse satellite-device device-alias on page 532
show interfaces terse satellite-device all on page 532
Output Fields Table 30 on page 531 lists the output fields for the show interfaces terse satellite-device
command. Output fields are listed in the approximate order in which they appear.
Sample Output
Sample Output
xe-101/0/15 up up
xe-101/0/16 up up
xe-101/0/17 up up
xe-101/0/24 up up
xe-101/0/25 up up
xe-101/0/31 up up
xe-101/0/31.0 up up bridge
xe-101/0/32 up down
xe-101/0/32.0 up down bridge
xe-101/0/33 up down
xe-101/0/33.0 up down bridge
ge-101/0/36 up down
et-101/0/48 up down
xe-101/0/50:0 up up
xe-101/0/50:0.0 up up bridge
xe-101/0/50:1 up up
xe-101/0/50:2 up up
xe-101/0/50:2.0 up up bridge
xe-101/0/50:3 up up
xe-102/0/10 up up
xe-102/0/11 up up
xe-102/0/12 up down
xe-102/0/13 up up
xe-102/0/14 up up
xe-102/0/15 up up
xe-102/0/16 up up
xe-102/0/17 up up
xe-102/0/24 up up
xe-102/0/25 up up
xe-102/0/31 up up
xe-102/0/31.0 up up bridge
xe-102/0/32 up up
xe-102/0/32.0 up up bridge
xe-102/0/33 up up
xe-102/0/45 up down
ge-102/0/46 up down
xe-102/0/47 up down
et-102/0/48 up down
et-102/0/49 up down
et-102/0/50 up down
et-102/0/51 up down
et-102/0/52 up down
et-102/0/53 up down
ge-103/0/0 up up
ge-103/0/0.0 up up aenet --> ae0.0
ge-103/0/1 up down
ge-103/0/1.0 up down aenet --> ae1.0
ge-103/0/2 up up
ge-103/0/2.0 up up aenet --> ae2.0
ge-103/0/3 up up
re0, re1, and routing-engine options introduced for dual Routing Engines in Junos OS
Release 13.1.
Command introduced in Junos OS Release 14.1X53-D20 for the OCX Series.
satellite option introduced in Junos OS Release 14.2R3.
core-file-info option is deprecated in Junos OS Release 16.1R3.
Description Show core files on all routers or switches running Junos OS. You can use the show system
core-dumps command to show a list of system core files created when the router or
switch has failed. This command can be useful for diagnostic purposes. Each list item
includes the file permissions, number of links, owner, group, size, modification date, and
path and filename. If dual Routing Engines are present, you can view core-dump files for
either routing engine or both routing engines together. On a QFabric system, you can view
core-dump files on individual QFabric system devices as well as on the entire QFabric
system.
For Junos OS, all cores files are stored at /var/core/re. For Junos OS Evolved, a core file
created during early bootup is stored in /var/core/re. But a core file created later in the
bootup, for example, after the Routing Engine slot number can be determined, is stored
in /var/core/re0 or /var/core/re1. The command show system core-dumps continues to
show all cores generated.
The core files are placed in the /var/tmp/corefiles on the SPC3 cards. Each PIC of the
SPC3 card has five core files quota on the RE. When no more than five core files from
one SPC3 PIC are on the RE, and the RE hard drive has more than 5 GB capacity, core file
from the specific PIC is saved at the time it arrives. When there are already five core files
from one SPC3 PIC on the RE, the newly arrived core file from the specific PIC replaces
the last core file created by that PIC on the RE. When 5 GB capacity limit is reached, core
file is not copied onto the RE. Only a zero sized shadow file with the same file name
suffixed by “.shadow” is created. The core file is reached on the specific SPC3 PIC.
NOTE: If dual Routing Engines are present, then only the core-dump files
for the active Routing Engine are listed. For Junos OS Evolved, core-dump
files for all Routing Engines are listed.
all-chassis—(TX Matrix and TX Matrix Plus routers only) (Optional) On a routing matrix
based on a TX Matrix router, display system core files for the TX Matrix router
switch-card chassis [SCC] and all the T640 routers [LCCs] connected to the TX
Matrix router.
On a routing matrix based on a TX Matrix Plus router, display system core files for
the TX Matrix Plus router (switch-fabric chassis [SFC]) and all the T1600 routers
[LCCs] connected to the TX Matrix Plus router.
<all-lcc | lcc number>—(TX Matrix and TX Matrix Plus routers only) (Optional) On a
routing matrix based on the TX Matrix router, display core dump files for all T640
routers (line-card chassis [LCCs]) or a specific T640 router [LCC] connected to the
TX Matrix router.
On a routing matrix based on the TX Matrix Plus router, display logging information
for all T1600 routers (line-card chassis [LCCs]) or a specific T1600 router (LCC)
connected to the TX Matrix Plus router. When using the lcc number option, replace
number with a value from 0 through 3.
NOTE: The all-chassis option displays system core files for the SCC or
SFC and the LCCs connected to the SCC or SFC in the routing matrix
while the all-lcc option only displays system core files for the LCCs in the
routing matrix.
local—(EX4200 switches only) (Optional) Display system core files on the local Virtual
Chassis member.
node node-name—(Optional) (Junos OS Evolved only) Display system core files generated
on the specified node.
repository (core | log)—(QFabric systems only) (Optional) Specify either the core or log
repository in which to view core-dump files.
scc—(TX Matrix routers only) (Optional) Display system core files on the TX Matrix router
(or switch-card chassis).
sfc—(TX Matrix Plus routers only) (Optional) Display system core files on the TX Matrix
Plus router (or switch-fabric chassis).
Output Fields Table 31 on page 537 describes the output fields for the show system core-dumps command.
Output fields are listed in the approximate order in which they appear.
Path/filename File path where the file resides and the filename.
(MX Series routers only) When you display the core files for an
MX Series Virtual Chassis, the show system core-dumps command
does not display information about files pertaining to the relayd
process.
Repository scope: Repository where core-dump files and log files are stored. The
core-dump files are located in the core repository, and the log files
are located in the log repository. The default Repository scope is
shared since both the core and log repositories are shared by all of
the QFabric system devices.
List of nodes for core List of core-dump files associated with a particular QFabric system
repository: device located in the core repository.
Total usage of core Total usage of core-dump files associated with a particular QFabric
repository: system device located in the core repository. Usage is specified in
megabytes and as a percentage.
Total usage of log Total usage of log files associated with a particular QFabric system
repository: device located in the log repository. Usage is specified in megabytes
and as a percentage.
List of nodes for core List of core-dump files associated with a particular QFabric system
repository: device located in the core repository.
List of nodes for log List of log files associated with a particular QFabric system device
repository: located in the log repository.
Process name Name of the process that is generating a core-dump file or log file.
Sample Output
This example shows the command output if core files do not exist.
This example shows the command output if dual Routing Engines are present.
re0:
--------------------------------------------------------------------------
/var/crash/*core*: No such file or directory
/var/tmp/pics/*core*: No such file or directory
/var/crash/kernel.*: No such file or directory
/var/tmp/cores:
total blocks: 496776
re1:
--------------------------------------------------------------------------
/var/crash/*core*: No such file or directory
/var/tmp/pics/*core*: No such file or directory
/var/crash/kernel.*: No such file or directory
/var/tmp/cores:
total blocks: 3178420
-rw-rw---- 1 root field 19039721 Nov 8 14:29
chassisd.core.0.201311081429.3485600.gz
-rw-rw---- 1 root field 19039793 Nov 8 14:37
chassisd.core.1.201311081437.3485599.gz
..
sfc0-re0:
--------------------------------------------------------------------------
/var/crash/kernel.*: No such file or directory
/tftpboot/corefiles/*core*: No such file or directory
/var/crash/cores:
total 8
/var/tmp/cores:
total 1627592
-rw-r--r-- 1 root field 535346090 May 15 07:36
rpd.core-tarball.0.090515.0736.tgz
-rw-r--r-- 1 root field 105632057 May 15 07:37
rpd.core-tarball.1.090515.0737.tgz
-rw-r--r-- 1 root field 101981681 May 15 07:38
rpd.core-tarball.2.090515.0738.tgz
-rw-r--r-- 1 root field 85854573 May 15 07:40
rpd.core-tarball.3.090515.0740.tgz
-rw-r--r-- 1 root field 4157845 May 15 08:18
rpd.core-tarball.4.090515.0818.tgz
lcc0-re0:
--------------------------------------------------------------------------
/var/crash/kernel.*: No such file or directory
/tftpboot/corefiles/*core*: No such file or directory
/var/crash/cores:
total 8
/var/tmp/cores:
total 12
lcc1-re0:
--------------------------------------------------------------------------
/var/crash/kernel.*: No such file or directory
/tftpboot/corefiles/*core*: No such file or directory
/var/crash/cores:
total 8
/var/tmp/cores:
total 10024
-rw-r--r-- 1 root field 1875794 Apr 22 15:47
chassisd.core-tarball.0.090422.1547.tgz
-rw-r--r-- 1 root field 1894183 Apr 22 19:02
chassisd.core-tarball.0.090422.1902.tgz
-rw-r--r-- 1 root field 1290240 Apr 26 16:01 ksyncd_1558.core.0.090426.1601
lcc2-re0:
--------------------------------------------------------------------------
/var/crash/kernel.*: No such file or directory
/tftpboot/corefiles/*core*: No such file or directory
/var/crash/cores:
total 21124008
-rw-r--r-- 1 root wheel 1022376528 May 2 06:43
core-LCC2-EGFPC7.core.0.090502.0643
-rw-r--r-- 1 root wheel 1022376528 May 2 08:13
core-LCC2-EGFPC7.core.0.090502.0813
-rw-r--r-- 1 root wheel 1022376544 May 5 06:15
core-LCC2-EGFPC7.core.0.090505.0615
-rw-r--r-- 1 root wheel 1022376544 May 6 10:59
core-LCC2-EGFPC7.core.0.090506.1059
-rw-r--r-- 1 root wheel 1022376528 May 2 06:58
core-LCC2-EGFPC7.core.1.090502.0658
-rw-r--r-- 1 root wheel 754271232 May 5 06:33
core-LCC2-EGFPC7.core.1.090505.0633
-rw-r--r-- 1 root wheel 264897536 May 6 11:12
core-LCC2-EGFPC7.core.1.090506.1112
-rw-r--r-- 1 root wheel 1022376528 May 2 07:22
core-LCC2-EGFPC7.core.2.090502.0722
-rw-r--r-- 1 root wheel 163633152 May 5 06:52
core-LCC2-EGFPC7.core.2.090505.0652
-rw-r--r-- 1 root wheel 171312128 May 6 12:13
core-LCC2-EGFPC7.core.2.090506.1213
-rw-r--r-- 1 root wheel 1022376528 May 2 07:39
core-LCC2-EGFPC7.core.3.090502.0739
-rw-r--r-- 1 root wheel 1022376528 May 2 07:55
core-LCC2-EGFPC7.core.4.090502.0755
-rw-r--r-- 1 root wheel 427277312 May 7 04:47
core-LCC2-STFPC4.core.0.090507.0447
-rw-r--r-- 1 root wheel 419609600 May 7 04:47
core-LCC2-STFPC5.core.0.090507.0447
-rw-r--r-- 1 root wheel 432356352 May 7 04:47
core-LCC2-STFPC6.core.0.090507.0447
/var/tmp/cores:
total 2568
-rw-r--r-- 1 root field 1290240 May 14 14:26 ksyncd_1540.core.0.090514.1426
...
show system core-dumps component serial number display-order alphanumeric-sort repository core (QFabric
Systems)
user@switch> show system core-dumps component BBAK8891 display-order alphanumeric-sort
repository core
Component: cedb7b0e-0025-11e1-9a5f-00e081c52990
Filename Size Date
Node: A0001/YA0197
Processor 0:
restoreintr+0x14 (1,81bca820,3,0) ra 806cdc3c sz 0
spinlock_exit+0x30 (1,81bca820,3,0) ra 8025d354 sz 24
sleepq_release+0x64 (1,81bca820,3,0) ra 8025e670 sz 24
sleepq_timeout+0x224 (1,81bca820,3,0) ra 80240294 sz 48
softclock+0x434 (1,81bca820,3,0) ra 802067f8 sz 80
ithread_loop+0x244 (1,81bca820,3,0) ra 80200e28 sz 64 fork_exit+0xc0
(1,81bca820,3,0) ra 80897c28 sz 48
MipsNMIException+0x34 (1,81bca820,3,0) ra 0 sz 0
pid 82340, process: sysctl
Processor 2:
cpu_idle+0x20 (80960000,51bbc,2031df,81bca1b8) ra 80204948 sz 24 idle_proc+0x130
(80960000,51bbc,2031df,81bca1b8) ra 80200e28 sz 56 fork_exit+0xc0
(80960000,51bbc,2031df,81bca1b8) ra 80897c28 sz 48
MipsNMIException+0x34 (80960000,51bbc,2031df,81bca1b8) ra 0 sz 0
pid 82340, process: sysctl
Processor 3:
cpu_idle+0x20 (80960000,51bbc,2038df,81bca300) ra 80204948 sz 24 idle_proc+0x130
(80960000,51bbc,2038df,81bca300) ra 80200e28 sz 56 fork_exit+0xc0
(80960000,51bbc,2038df,81bca300) ra 80897c28 sz 48
MipsNMIException+0x34 (80960000,51bbc,2038df,81bca300) ra 0 sz 0
pid 82340, process: sysctl
Processor 4:
cpu_idle+0x20 (80960000,51bbc,2037df,81bca448) ra 80204948 sz 24 idle_proc+0x130
(80960000,51bbc,2037df,81bca448) ra 80200e28 sz 56 fork_exit+0xc0
(80960000,51bbc,2037df,81bca448) ra 80897c28 sz 48
MipsNMIException+0x34 (80960000,51bbc,2037df,81bca448) ra 0 sz 0
pid 82340, process: sysctl
Processor 5:
restoreintr+0x14 (1,51bbc,203edf,81bca590) ra 806cdc3c sz 0
spinlock_exit+0x30 (1,51bbc,203edf,81bca590) ra 80204a34 sz 24 idle_proc+0x21c
(1,51bbc,203edf,81bca590) ra 80200e28 sz 56 fork_exit+0xc0
(1,51bbc,203edf,81bca590) ra 80897c28 sz 48
MipsNMIException+0x34 (1,51bbc,203edf,81bca590) ra 0 sz 0
Processor 6:
cpu_idle+0x20 (80960000,51bbc,205cdf,81bca6d8) ra 80204948 sz 24 idle_proc+0x130
(80960000,51bbc,205cdf,81bca6d8) ra 80200e28 sz 56 fork_exit+0xc0
(80960000,51bbc,205cdf,81bca6d8) ra 80897c28 sz 48
MipsNMIException+0x34 (80960000,51bbc,205cdf,81bca6d8) ra 0 sz 0
pid 82340, process: sysctl
Processor 7:
lockmgr+0x5ac (c97e8484,c8dd9800,0,c8dd9800) ra 8c11c81c sz 48
sal_sem_take+0x134 (c97e8484,c8dd9800,0,c8dd9800) ra 8c351108 sz 56
_bcm_esw_linkscan_thread+0x45c (c97e8484,c8dd9800,0,c8dd9800) ra 8c11cdb4 sz 104
sal_thread_start_wrap+0x74 (c97e8484,c8dd9800,0,c8dd9800) ra 80200e28 sz 32
fork_exit+0xc0 (c97e8484,c8dd9800,0,c8dd9800) ra 80897c28 sz 48
MipsNMIException+0x34 (c97e8484,c8dd9800,0,c8dd9800) ra 0 sz 0
pid 82340, process: sysctl
-- End of stacktrace --
Options none—Display the storage usage for all listed satellite devices.
Output Fields Table 32 on page 549 describes the output fields for the show system storage command.
Output fields are listed in the approximate order in which they appear.
Sample Output
Slot-ID: 125
Filesystem Size Used Avail Use% Mounted on
rootfs 665M 287M 330M 47% /
udev 896M 24K 896M 1% /dev
none 896M 24K 896M 1% /dev
tmpfs 936M 812K 935M 1% /run
/dev/sda3 665M 287M 330M 47% /
/dev/sda5 327M 99M 207M 33% /var
tmpfs 936M 812K 935M 1% /run
tmpfs 936M 14M 923M 2% /var/volatile
/dev/sda1 481M 254M 228M 53% /boot
/dev/sda2 259M 2.1M 240M 1% /app_disk
tmpfs 936M 812K 935M 1% /run/named-chroot/var/run/named
tmpfs 936M 812K 935M 1% /run/named-chroot/var/run/bind
none 896M 24K 896M 1% /run/named-chroot/dev/random
none 896M 24K 896M 1% /run/named-chroot/dev/zero
none 896M 24K 896M 1% /run/named-chroot/dev/null
Slot-ID: 134
Filesystem Size Used Avail Use% Mounted on
rootfs 665M 287M 330M 47% /
udev 896M 24K 896M 1% /dev
none 896M 24K 896M 1% /dev
tmpfs 936M 812K 935M 1% /run
/dev/sda3 665M 287M 330M 47% /
/dev/sda5 327M 97M 209M 32% /var
tmpfs 936M 812K 935M 1% /run
tmpfs 936M 13M 924M 2% /var/volatile
/dev/sda1 481M 254M 228M 53% /boot
/dev/sda2 259M 2.1M 240M 1% /app_disk
tmpfs 936M 812K 935M 1% /run/named-chroot/var/run/named
tmpfs 936M 812K 935M 1% /run/named-chroot/var/run/bind
none 896M 24K 896M 1% /run/named-chroot/dev/random
none 896M 24K 896M 1% /run/named-chroot/dev/zero
none 896M 24K 896M 1% /run/named-chroot/dev/null
In a Junos Fusion, PoE is used to carry electric power from an extended port on a satellite
device to a connected device. An extended port is any network-facing port on a satellite
device in a Junos Fusion.
Many PoE concepts for standalone switches also apply to PoE on Junos Fusion. See
Understanding PoE on EX Series Switches for a detailed overview of PoE on standalone
EX Series switches.
Understanding the Role of the Aggregation Devices for PoE Support in a Junos Fusion
An aggregation device is responsible for configuring, monitoring, and maintaining all
configurations for all extended ports in a Junos Fusion, including PoE. Therefore, all
commands used to configure, monitor, and maintain PoE in a Junos Fusion are entered
from the aggregation device.
An extended port on the satellite device must support PoE to enable PoE in a Junos
Fusion. No hardware limitations for PoE support are introduced by the aggregation device
in a Junos Fusion.
NOTE: PoE is supported in a Junos Fusion Provide Edge and a Junos Fusion
Enterprise despite not being supported in MX series routers or standalone
EX9200 switches. All MX series routers and EX9200 switch models, when
configured into the aggregation device role in a Junos Fusion , can enable PoE
Junos Fusion because the PoE hardware support is supported on the satellite
devices.
Understanding the Role of the Satellite Devices for PoE Support in a Junos Fusion
A satellite device in a Junos Fusion provides PoE hardware support in a Junos Fusion.
Each satellite device in a Junos Fusion that supports PoE has its own PoE controller. The
PoE controller keeps track of the PoE power consumption on the satellite device and
allocates power to PoE extended ports. The maximum PoE power consumption for a
satellite device—the total amount of power available for the satellite device’s PoE
controller to allocate to all of the satellite device’s PoE interfaces—is determined
individually by the switch model of the satellite devices and by the power supply or
supplies installed in that satellite device.
In allocating power, the satellite device’s PoE controller cannot exceed the satellite
device’s maximum PoE power availability.
The maximum PoE power consumption varies by satellite device in a Junos Fusion ,
because the hardware specifications of the satellite devices determine the maximum
PoE power availability.
See Understanding PoE on EX Series Switches for a listing of the PoE power consumption
limit for each EX Series switch model and power supply configuration.
In dual aggregation device topologies, the PoE configurations should match identically
on both aggregation devices.
PoE in a Junos Fusion works by periodically checking the PoE configuration on each
aggregation device, and updating the configuration when a PoE change is identified. If
the aggregation devices have different PoE configurations, the PoE configurations for
the Junos Fusion will continually change because the Junos Fusion always uses the PoE
configuration of the last aggregation device that was checked.
All extended ports that support PoE on satellite devices in a Junos Fusion support the
IEEE 802.3at PoE+ standard. The IEEE 802.3at PoE+ standard allows an extended port
that supports PoE to provide up to 30 W of power to a connected device.
Maximum PoE power budgets for a satellite device vary by the switch model and power
supply configuration of the satellite device.
To learn the maximum PoE power supply budget for a satellite device:
• See Understanding PoE on EX Series Switches for a table of maximum power supply
budgets by switch device model.
• Enter the show poe controller command from your aggregation device and view the
Maximum Power output.
PoE controller software is bundled with Junos OS. PoE controller software should be
updated before installing a switch as a satellite device in a Junos Fusion.
For information on PoE controller software requirements in a Junos Fusion Provider Edge,
see “Understanding Junos Fusion Provider Edge Software and Hardware Requirements”
on page 21
For information on checking or upgrading the PoE controller software version, see
Upgrading the PoE Controller Software.
The PoE power allocation options are discussed in greater detail in Understanding PoE
on EX Series Switches.
This topic describes Link Layer Discovery Protocol (LLDP) and Link Layer Discovery
Protocol–Media Endpoint Discovery (LLDP-MED) in a Junos Fusion.
LLDP-capable devices transmit information in type, length, and value (TLV) messages
to neighbor devices. Device information can include information such as chassis and port
identification and system name and system capabilities. The TLVs leverage this
information from parameters that have already been configured in the Junos operating
system (Junos OS).
Many LLDP and LLDP-MED concepts for standalone EX Series switches that support the
features also apply to LLDP and LLDP-MED on Junos Fusion . See Understanding LLDP
and LLDP-MED on EX Series Switches for a detailed overview of LLDP and LLDP-MED on
standalone EX Series switches.
NOTE: LLDP-MED goes one step further than LLDP, exchanging IP-telephony
messages between the switch and the IP telephone. LLDP-MED is an
important access layer switch feature that is supported in a Junos Fusion
despite not being supported on a standalone EX9200 switch.
Understanding LLDP and LLDP-MED Configuration and Traffic Handling in a Junos Fusion
LLDP and LLDP-MED traffic is generally handled the same in a Junos Fusion or a
standalone series switch. LLDP and LLDP-MED configuration on an extended port in a
Junos Fusion is identical for a standalone EX Series switch. See Configuring LLDP (CLI
Procedure) or Configuring LLDP-MED (CLI Procedure).
The following specifications apply to the device information transmitted by LLDP and
LLDP-MED in a Junos Fusion topology with two or more aggregation devices:
• Management address TLVs are merged into a single packet in such a way that the
packet contains two or more management address TLVs.
• The SNMP index used as the port ID TLV is derived so that all aggregation devices
receive the same index value for port IDs of extended ports.
• The system name for extended ports is the configured redundancy group name. A
redundancy group has to be configured in order to enable a topology with two or more
aggregation devices.
• The chassis ID is the same for all aggregation devices. If a system MAC address is
defined for the redundancy group, is it used as the chassis ID. The system MAC address
is configured using the set chassis satellite-management redundancy-groups
redundancy-group-name system-mac-address system-mac-address command. If the
system MAC is not configured, the chassis ID is the default MAC address, which is
00:00:00:00:00:01.
Some PoE options can be configured globally and per interface. In cases where a PoE
interface setting is different from a global PoE setting, the PoE interface setting is
configured on the interface.
disable (Power over Not included in default Disables PoE on the interface if PoE was enabled. The interface maintains
Ethernet) configuration. network connectivity but no longer supplies power to a connected
powered device. Power is not allocated to the interface.
NOTE: PoE ports are
disabled by default in a
Junos Fusion.
guard-band 0W Reserves a specified amount of power from the PoE power budget for
possible spikes in PoE power consumption.
management class Sets the PoE power management mode for the extended port. The
power management mode determines how power to a PoE extended
port is allocated:
maximum-power 30.0 W (PoE+, IEEE Sets the maximum power that can be delivered by a PoE interface when
(Interface) 802.3at) the power management mode is static.
priority (Power over low Sets an interface’s power priority to either low or high. If power is
Ethernet) 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.
Enabling PoE
PoE is disabled by default for all extended ports in a Junos Fusion.
[edit]
user@aggregation-device# set poe interface all-extended
[edit]
user@aggregation-device# set poe interface interface-name
[edit]
user@aggregation-device# set poe interface ge-100/0/24
Disabling PoE
PoE is disabled by default in a Junos Fusion. Use this procedure to disable PoE in a Junos
Fusion that has PoE previously enabled.
If PoE is enabled globally but disabled on a specific interface, PoE is disabled on the
specified interface. This procedure can, therefore, be used to individually disable ports
in cases where PoE is globally enabled.
If you want to disable PoE on all extended port interfaces in a Junos Fusion:
[edit]
user@aggregation-device# set poe interface all-extended disable
[edit]
user@aggregation-device# set poe interface interface-name disable
[edit]
user@aggregation-device# set poe interface 101/0/1 disable
If you want to enable PoE on all PoE-supported extended ports in a Junos Fusion except
101/0/10, enter the following commands:
[edit]
user@aggregation-device# set poe interface all-extendeduser@aggregation-device# set
poe interface 101/0/10 disable
To set the power management mode to static for all PoE extended ports:
[edit]
user@aggregation-device# set poe management static
To set the power management mode back to class for all PoE extended ports:
[edit]
user@aggregation-device# set poe management class
Setting the Maximum Power That Can Be Delivered from a PoE Interface
To set the maximum power that can be delivered to a connected device using PoE when
the power management mode is set to static:
[edit]
user@aggregation-device# set poe interface interface-name maximum-power watts
To configure all extended port interfaces to the same maximum power, enter all-extended
as the interface-name.
For instance, to change the maximum power for all PoE extended ports configured in
static power management mode to 25 watts:
[edit]
user@aggregation-device# set poe interface all-extended maximum-power 25
[edit]
user@aggregation-device# set poe interface 101/0/1 maximum-power 25
To set the guard band for all extended ports in a Junos Fusion:
[edit]
user@aggregation-device# set poe guard-band watts
For instance, to set the guard-band to 19 watts for all PoE extended ports:
[edit]
user@aggregation-device# set poe guard-band 19
[edit]
user@aggregation-device# set poe interface interface-name priority high
[edit]
[edit]
user@aggregation-device# set poe interface interface-name priority low
[edit]
user@aggregation-device# set poe interface 102/0/1 priority low
Related • Verifying PoE Configuration and Status for a Junos Fusion (CLI Procedure) on page 559
Documentation
• Understanding Power over Ethernet in a Junos Fusion on page 551
Verifying PoE Configuration and Status for a Junos Fusion (CLI Procedure)
You can verify the Power over Ethernet (PoE) configuration and status on Junos Fusion.
• PoE Power Budgets, Consumption, and Mode on Satellite Devices on page 559
• PoE Interface Configuration and Status on page 560
Purpose Verify the PoE configuration and status, such as the PoE power budget, total PoE power
consumption, power management mode, and the supported PoE standard.
Meaning • Satellite device 100 has a PoE power budget of 925 W, of which 0 W were being used
by the PoE extended ports at the time the command was executed. The Guard band
field shows that 19 W of power is reserved out of the PoE power budget to protect
against spikes in power demand. The power management mode is class. The PoE ports
on the switch support PoE+ (IEEE 802.3at).
• Satellite device 120 has a PoE power budget of 125 W, of which 6.08 W were being
used by the PoE extended ports at the time the command was executed. The Guard
band field shows that 19 W of power is reserved out of the PoE power budget to protect
against spikes in power demand. The power management mode is class. The PoE ports
on the switch support PoE+ (IEEE 802.3at).
Purpose Verify that PoE interfaces are enabled and set to the correct maximum power and priority
settings. Also verify current operational status and power consumption.
Action To view configuration and status for all PoE interfaces, enter:
not-applicable
ge-120/0/6 Enabled ON 16.0W Low 0.0W 4
ge-120/0/7 Enabled OFF 0.0W Low 0.0W
not-applicable
ge-120/0/8 Enabled OFF 0.0W Low 0.0W
not-applicable
ge-120/0/9 Enabled OFF 0.0W Low 0.0W
not-applicable
ge-120/0/10 Enabled OFF 0.0W Low 0.0W
not-applicable
ge-120/0/11 Enabled OFF 0.0W Low 0.0W
not-applicable
<additional output removed for brevity>
Meaning The command output shows the status and configuration of interfaces. For example,
the interface 120/0/0 is administratively enabled. Its operational status is ON; that is,
the interface is currently delivering power to a connected powered device. The maximum
power allocated to the interface is 7.0 W. The interface has a low PoE power priority. At
the time the command was executed, the powered device was consuming 3.9 W. The
class of the powered device is class 2. If the PoE power management mode is class, the
class of the powered device determines the maximum power allocated to the interface,
which is 7 W in the case of class 2 devices.
The PoE Mode field indicates that the interface supports IEEE 802.3at (PoE+).
Syntax disable;
Release Information Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 12.2 for ACX2000 Universal Metro Routers.
all-extended option introduced in Junos OS Release 16.1R1.
Statement introduced in Junos OS Release 17.2R1 for a Junos Fusion Provider Edge.
Description Disable a PoE interface, disable the collection of power consumption data for a PoE
interface, or disable the generation of the PoE SNMP traps. The action of the disable
statement depends on which statement it is used with:
• When used with interface—Disable the PoE capability of this interface. The interface
operates as a standard network access interface, and power is no longer allocated to
it from the PoE power budget. Although the PoE capability is disabled, the PoE
configuration for the interface is retained. To reenable the PoE capability of this
interface, delete the disable statement from the interface entry in the configuration.
• When used with telemetries—Disable the collection of PoE power consumption records
for this interface. Any previously collected records are deleted. However, the telemetries
configuration is retained, including the values for interval and duration. To reenable
record collection, delete the disable statement from the telemetries entry in the
configuration.
Related • Example: Configuring PoE Interfaces with Different Priorities on an EX Series Switch
Documentation
• Configuring PoE on EX Series Switches (CLI Procedure)
guard-band
Release Information Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 12.2 for ACX2000 Universal Metro Routers.
Statement introduced in Junos OS Release 17.2R1 for a Junos Fusion Provider Edge.
Description Reserve a specified amount of power from the PoE power budget for the switch, line
card, or satellite device in case of a spike in PoE consumption.
Release Information Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 17.2R1 for a Junos Fusion Provider Edge.
Options all—All PoE interfaces on the switch that have not been individually configured for PoE.
If a PoE interface has been individually configured, that configuration overrides any
settings specified with all.
all-extended—(Junos Fusion only) All PoE extended port interfaces in a Junos Fusion
that have not been individually configured for PoE. If a PoE interface has been
individually configured, that configuration overrides any settings specified with
all-extended.
If you use the interface statement without any substatements, default values are used
for the remaining statements.
Related • Example: Configuring PoE Interfaces with Different Priorities on an EX Series Switch
Documentation
• Configuring PoE on EX Series Switches (CLI Procedure)
management
Release Information Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 12.2 for ACX2000 Universal Metro Routers.
Statement introduced in Junos OS Release 17.2R1 for a Junos Fusion Provider Edge.
Description Designate how the PoE controller allocates power to the PoE interfaces.
Default class
Options • class—The amount of power allocated to the interface is based on the class of the
connected powered device. If LLDP power negotiation is enabled, the powered device
can request more or less power. LLDP power negotiation is enabled by default in class
management mode.
If LLDP power negotiation is disabled, the power allocation is determined solely by the
class of the connected powered device. If there is no powered device connected,
standard 15.4W power is allocated on the interface. For more information about power
allocation, see Understanding PoE on EX Series Switches.
maximum-power (Interface)
Release Information Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 12.2 for ACX2000 routers.
Statement introduced in Junos OS Release 17.2R1 for a Junos Fusion Provider Edge.
Description Configure the maximum amount of power that the switch can supply to the PoE port.
The maximum power configuration is valid when the PoE power management is in static
mode. If PoE power management is in class mode, which is the default, the maximum
power configuration will have no effect on the power allocation. For more information
on power management configuration options, see management.
NOTE: A standalone switch’s default setting and range for maximum power
does not change if the switch is configured as a satellite device in a Junos
Fusion. For instance, an EX4300 switch has a 30W default and a range of
0.0 through 30.0 W when configured as a standalone switch and when it is
configured into a satellite device in a Junos Fusion.
Options watts—The maximum power in watts that can be supplied to the ports.
For EX2200, EX3300, EX4200, EX4300, EX4600, EX6200, and EX8200 switches:
Range: 0.0 through 30.0
Default: 15.4 W for ports that support IEEE 802.3af and 30 W for ports that support IEEE
802.3at
NOTE: EX4600 switches support PoE only when operating in a mixed Virtual
Chassis with EX4300 switches.
If you use the all option to set maximum-power to a value greater than 15.4 W
on all interfaces on an EX8200 line card, the maximum power allocated to
all ports is 15.4 W.
NOTE: Support for a maximum of 18.6 W per port instead of 15.4 W per port
on EX3200 switches and P and T models of EX4200 switch requires Junos
OS Release 11.1 or later. In addition to requiring an upgrade of Junos OS to
Release 11.1 or later, switches that are running an earlier release of Junos OS
release require the PoE controller software be upgraded as described in
Upgrading the PoE Controller Software. If the controller software is not
upgraded and you set maximum-power to a value greater than 15.4 W, the
configuration is accepted when you commit it, but the actual power allocated
to the port will be 15.4 W.
n-plus-n (satellite-management)
Syntax n-plus-n
Release Information Statement introduced in Junos OS Release 16.1R1 for Junos Fusion Enterprise.
Statement introduced in Junos OS Release 17.2R1 for a Junos Fusion Provider Edge.
Description Configure N+N power supply redundancy for the satellite devices in a Junos Fusion.
poe
poe {
guard-band watts;
interface (all | interface-name) {
disable;
maximum-power watts;
priority (high | low);
telemetries {
disable;
duration hours;
interval minutes;
}
}
lldp-priority;
management (class | static);
notification-control {
fpc slot-number {
disable;
}
}
}
poe {
guard-band watts;
interface (all-extended | interface-name) {
disable;
maximum-power watts;
priority (high | low);
}
management (class | static);
}
poe {
fpc ( all | slot-number) {
guard-band watts;
lldp-priority;
management (class | static);
maximum-power watts;
}
interface (all | interface-name) {
af-mode;
disable;
maximum-power watts;
priority (high | low);
telemetries {
disable;
duration hours;
interval minutes;
}
}
notification-control {
fpc slot-number {
disable;
}
}
}
Release Information Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 17.2R1 for a Junos Fusion Provider Edge.
Description Configure PoE options. PoE ports on Juniper network switches provide power to
PoE-enabled devices only when straight-through cables are used. Power is not provided
when crossover cables are used.
Related • Example: Configuring PoE Interfaces with Different Priorities on an EX Series Switch
Documentation
• Example: Configuring PoE on an EX6200 or EX8200 Switch
Release Information Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 17.2R1 for a Junos Fusion Provider Edge.
Description Set the power priority for individual interfaces when there is insufficient power for all PoE
interfaces. If the switch needs to shut down powered devices because PoE demand
exceeds the PoE budget, low-priority devices are shut down before high-priority devices.
Among interfaces that have the same assigned priority, priority is determined by port
number, with lower-numbered ports having higher priority.
Default low
Related • Example: Configuring PoE Interfaces with Different Priorities on an EX Series Switch
Documentation
• Configuring PoE on EX Series Switches (CLI Procedure)
psu (satellite-management)
Syntax psu {
redundancy {
n-plus-n;
}
}
Release Information Statement introduced in Junos OS Release 16.1R1 for a Junos Fusion Enterprise.
Statement introduced in Junos OS Release 17.2R1 for a Junos Fusion Provider Edge.
Description Configure N+N power supply redundancy for the satellite devices in a Junos Fusion.
redundancy (satellite-management)
Syntax redundancy {
n-plus-n;
}
Release Information Statement introduced in Junos OS Release 16.1R1 for a Junos Fusion Enterprise.
Statement introduced in Junos OS Release 17.2R1 for a Junos Fusion Provider Edge.
Description Configure N+N power supply redundancy for the satellite devices in a Junos Fusion.
Default N+1 power supply redundancy is configured on each satellite device by default.
Release Information Command introduced in Junos OS Release 16.1R1 for a Junos Fusion Enterprise.
Statement introduced in Junos OS Release 17.2R1 for a Junos Fusion Provider Edge.
Description Display the power budget statistics of a satellite device or devices in a Junos Fusion.
Options none—Display power budget statistics for all satellite devices in the Junos Fusion.
slot-id slot-id-number—Display power budget statistics for the specified satellite device
only. The slot-id-number and the FPC ID are the same number in a Junos Fusion.
Output Fields Table 34 on page 578 lists the output fields for the show chassis satellite-management
power-budget-statistics command. Output fields are listed in the approximate order in
which they appear.
FPC n The FPC slot ID number in the Junos Fusion, where n Is the FPC
slot ID. The FPC slot ID and the satellite device number are the
same thing in a Junos Fusion.
PSU n (supply type) Capacity rating of the power supply and whether the power
supply is currently operating (Online) or not (Offline). If a power
supply is offline, the capacity is shown as 0 W.
Total Power supplied by all Online PSUs Total number of watts supplied by all currently operating power
supplies for the satellite device.
Power Redundancy Configuration Configured power redundancy setting, either N+1 or N+N.
Base power reserved Total number of watts reserved for the satellite device.
Non-PoE power being consumed The amount of power, in W, currently being consumed for
functions other than PoE by the satellite device.
Total Power allocated for PoE The total of the PoE power budgets allocated to the satellite
device.
Total PoE power consumed The amount of power that has been consumed by PoE by the
satellite device.
Total PoE power remaining The amount of available power remaining that can be used
for PoE on the satellite device.
Sample Output
Release Information Command introduced in Junos OS Release 9.0 for EX Series switches.
Command introduced in Junos OS Release 12.2 for ACX2000 routers.
Statement introduced in Junos OS Release 17.2R1 for a Junos Fusion Provider Edge.
• Verifying PoE Configuration and Status for a Junos Fusion (CLI Procedure) on page 559
List of Sample Output show poe controller (EX3200 Switch) on page 582
show poe controller (EX8200 Switch) on page 582
show poe controller (Controller Software Upgrade in Progress) on page 583
show poe controller (ACX2000 Router) on page 583
Output Fields Table 35 on page 581 lists the output fields for the show poe controller command. Output
fields are listed in the approximate order in which they appear.
Maximum power The maximum PoE power consumption for the switch or line card. This is the
total amount of power available to the PoE controller to allocate to the PoE
ports.
Power consumption Total amount of power being consumed by the PoE ports at the time the
command is executed. This value, which represents actual power consumption,
cannot exceed the value for Maximum power.
Guard Band Amount of power that has been placed in reserve for power demand spikes and
that cannot be allocated to a PoE interface.
Lldp Priority Link Layer Discovery Protocol (LLDP) priority operating state. The state can be
Enabled or Disabled.
LLDP priority enables 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.
Sample Output
Release Information Command introduced in Junos OS Release 9.0 for EX Series switches.
Command introduced in Junos OS Release 12.2 for ACX2000 routers.
Statement introduced in Junos OS Release 17.2R1 for a Junos Fusion Provider Edge.
Output Fields Table 36 on page 585 lists the output fields for the show poe interface command. Output
fields are listed in the approximate order in which they appear.
Admin status Administrative Administrative state of the PoE interface: Enabled or Disabled. If the PoE interface is
status disabled, it can provide network connectivity, but it cannot provide power to connected
devices.
Operational status Additional information for troubleshooting the operational state of the PoE interface:
detail
• Admin up but disabled on hardware—The interface is disabled due to power budget
unavailability.
• Overload—Interface is in the fault condition.
• IEEE PD Detected—The interface is providing power to the powered device.
• Detection In Progress—Detection of the powered device is ongoing.
FourPair status Status of high-power mode of power delivery over all four pairs of the Ethernet cable:
Pair/Mode status Shows the mode of power delivery configured on the interface.
Max power Power limit on the Maximum power that can be provided by the interface.
interface
An (L) next to the value indicates that the value on the port was negotiated by LLDP.
An (L) next to the value indicates that the value on the port was negotiated by LLDP.
Power Power consumed Amount of power being used by the interface at the time the command is executed.
consumption
Class Class of power IEEE PoE class of the powered device. Class 0 is the default class and is used when
device the class of the powered device is unknown. If no powered device is connected, this
field contains not applicable.
PoE-bt supports power devices with dual signatures. For dual-signature devices, the
output value contains both the class values, e.g. 5/5. For single-signature devices,
the output value is formatted as 5/-.
PoE Mode IEEE PoE standard supported by the interface—either 802.3af, or 802.3at, ultra-poe,
or 802.3bt.
Sample Output
Junos Fusion Provider Edge supports CFM sessions on the extended ports of the satellite
devices via the cascade port on the aggregation device. The aggregation device handles
and processes the transmission and reception of the CFM messages. From a CFM
perspective, the satellite devices operate in a transparent mode.
CFM selects the cascade port that is associated with a satellite device as the anchor for
the CFM sessions that are configured on the extended ports of the satellite device and
it processes the sessions in the PFE that is associated with the cascade port. When a
satellite device is connected to multiple cascade ports on the aggregation device, CFM
selects the first available cascade port as the anchor. If the anchor cascade port fails,
the next available cascade port is selected as anchor and the CFM sessions processing
is moved to the PFE of newly selected anchor. The CFM sessions can flap when the
sessions are re-anchored. During the switchover, the measurement interval in the CFM
session restarts.
For more information on configuring CFM, see IEEE 802.1ag OAM Connectivity Fault
Management Overview
NOTE: Junos Fusion Provider Edge only supports enhanced CFM mode.
The Chassis MIB has been enhanced to enable satellite devices to be represented in the
chassis MIB. Satellite devices are represented as FPCs/slots (100, 101,102,..) in the
aggregation device. The support is enabled using a separate range of container indices
(CIDX), which allows the SNMP process to redirect relevant SNMP requests to the satellite
device management process.
The CIDX for representing satellite device hardware components in Junos Fusion are
offset by 100 from indices for hardware components on Junos devices; for example a
regular CIDX 2 (Power Supply) is 102 for the power supply of the satellite device. Using
these indices you can distinguish the satellite device hardware from the aggregate device.
The L1 index for satellite device entries refers to their FPC slot identifiers. As per the
chassis MIB convention, identifiers are 1-based. For example, satellite device 100 will
have an L1 index of 101, satellite device 101 will have an L1 index of 102, and so on.
104 Fan
107 FPC
108 PIC
The following tables have been enhanced to include object IDs for satellite devices:
• jnxContainersTable
• jnxContentsTable
• jnxFilledTable
• jnxOperatingTable
• jnxFRUTable
jnxContainersType.102 = jnxSatelliteDeviceSlotPower.0
jnxContainersType.104 = jnxSatelliteDeviceSlotFan.0
jnxContainersType.107 = jnxSatelliteDeviceSlotFPC.0
jnxContainersType.108 = jnxSatelliteDeviceMediaCardSpacePIC.0
…
…
jnxContainersDescr.102 = SD PEM slot
jnxContainersDescr.104 = SD FAN slot
jnxContainersDescr.107 = SD FPC slot
jnxContainersDescr.108 = SD PIC slot
jnxContentsType.102.102.1.0 = jnxSatelliteDeviceSlotPower
jnxContentsType.102.102.2.0 = jnxSatelliteDeviceSlotPower
jnxContentsType.104.102.1.0 = jnxSatelliteDeviceSlotFan
jnxContentsType.104.102.2.0 = jnxSatelliteDeviceSlotFan
jnxContentsType.104.102.3.0 = jnxSatelliteDeviceSlotFan
jnxContentsType.104.102.4.0 = jnxSatelliteDeviceSlotFan
jnxContentsType.104.102.5.0 = jnxSatelliteDeviceSlotFan
jnxContentsType.107.102.0.0 = jnxSatelliteDeviceSlotFPC
jnxContentsType.108.102.1.0 = jnxSatelliteDeviceMediaCardSpacePIC
…
jnxContentsDescr.102.102.1.0 = SD101 PEM 0
jnxContentsDescr.102.102.2.0 = SD101 PEM 1
jnxContentsDescr.104.102.1.0 = SD101 Fan Tray 0
jnxContentsDescr.104.102.2.0 = SD101 Fan Tray 1
jnxContentsDescr.104.102.3.0 = SD101 Fan Tray 2
jnxContentsDescr.104.102.4.0 = SD101 Fan Tray 3
jnxContentsDescr.104.102.5.0 = SD101 Fan Tray 4
jnxContentsDescr.107.102.0.0 = SD101 FPC: QFX5100-48S-6Q @ 101/*/*
jnxContentsDescr.108.102.1.0 = SD101 PIC: 48x10G-6x40G @ 101/0/*
The following SNMP traps are generated for Satellite Devices, which are also logged as
syslog messages:
Table 38 on page 593 shows the SNMP traps that can be generated for satellite devices.
Trap Condition
jnxFruRemoval Sent when the specified FRU (FAN/PSU) has been removed from the chassis, or the satellite
device has been removed from the aggregation device's database
jnxFruInsertion Sent when the specified FRU (FAN/PSU) has been inserted into the satellite device
jnxFruPowerOff Sent when the specified FRU (FAN/PSU) has been powered off in the satellite device
jnxFruPowerOn Sent when the specified FRU (FAN/PSU) has been powered on in the satellite device
jnxFruFailed Sent when the specified FRU (FAN/PSU) has failed in the satellite device. Typically, this is
due to the FRU not powering up or being unable to load software. FRU replacement might
be required
jnxFruOK
jnxFruOffline Sent when FPC's new reported state is not online or PSU/FAN/PIC is not present due to
satellite device removal
jnxFruOnline Sent when specified FRU (FPC,PIC,PSU,FAN) gets added in the aggregation device database
jnxFruCheck Sent when the specified FRU (FAN/PSU) has encountered operational errors
Ethernet links to actively transmit protocol data units (PDUs), or you can configure the
links to passively transmit them, sending out LACP PDUs only when they receive them
from another link. You can configure both VLAN-tagged and untagged aggregated
Ethernet interfaces without LACP enabled. LACP is defined in IEEE 802.3ad, Aggregation
of Multiple Link Segments.
• Automatic addition and deletion of individual links to the LAG without user intervention.
• Link monitoring to check whether both ends of the bundle are connected to the correct
group.
The satellite devices provide network interfaces that send and receive network traffic
and process the periodic transmission of LACP packets. You can include extended ports
(physical interface on a satellite device that provides a connection to servers or endpoints)
or local ports in LAGs and MC-LAGs, but not both.
When a dual-homed end device is deployed with Junos Fusion, the network interface
cards form a LAG with the Junos Fusion. During a Junos Fusion upgrade, the end device
may not be able to exchange LACP PDUs. In such a situation you can configure an interface
to be in the up state even if no PDUs are exchanged. Use the force-up statement to
configure an interface when the peer has limited LACP capability. The interface selects
the associated LAG by default, whether the LACP mode is active or passive. When there
are no received PDUs, the partner is considered to be working in the passive mode.
Therefore, LACP PDU transmissions are controlled by the transmitting link.
In Junos Fusion with EVPN, all aggregation devices have knowledge of any extended
ports in a LAG because each LAG is assigned a unique Ethernet Segment Identifier (ESI).
The ESI is based on the redundancy group configuration and global LAG interface ID.
2. Define the parameters associated with the logical aggregated Ethernet interface, such
as a logical unit, interface properties, and Link Aggregation Control Protocol (LACP).
3. Define the member links to be contained within the aggregated Ethernet interface—for
example, two local 10-Gigabit Ethernet interfaces on the aggregation device or two
extended ports on the aggregation device.
• LAGs and MC-LAGs cannot include a mix of extended ports and local ports on the
aggregation device.
• LAGs can span across multiple satellite devices in Junos Fusion Provider Edge and
Junos Fusion Data Center.
• Existing restrictions that apply to LAGs and MC-LAGs also apply to LAGs and
MC-LAGs that include extended ports.
Software and Hardware Guidelines when Configuring Link Aggregation and LACP in Junos
Fusion
Keep in mind these hardware and software guidelines:
• Up to 1750 LAGs are supported in Junos Fusion Provider Edge, Junos Fusion Enterprise,
and Junos Fusion Data Center, and the LAGs are numbered from ae0 through ae4091.
• Up to 16 members are supported in a LAG in Junos Fusion Provider Edge, Junos Fusion
Enterprise, and Junos Fusion Data Center.
• The interfaces on either side of the link must be set to the same speed and be in
full-duplex mode.
• Configure LACP for dual-homed extended ports identically on both of the aggregation
devices; otherwise LACP will not be in a forwarding state.
On Fast Ethernet, Tri-Rate Ethernet copper, Gigabit Ethernet, and 10-Gigabit Ethernet
interfaces on M Series and T Series routers, you can associate a physical interface with
an aggregated Ethernet interface.
NOTE: On a Junos Fusion, you can include extended ports (physical interface
on a satellite device that provides a connection to servers or endpoints) or
local ports in link aggregation groups (LAGs) and MC-LAGs, but not both. For
information on extended ports, see “Understanding Junos Fusion Ports” on
page 13.
1. Specify that you want to configure the link aggregation group interface.
You specify the interface instance number x to complete the link association; x can be
from 0 through 127, for a total of 128 aggregated interfaces on M Series and T Series
routers and can be from 1 through 480, for a total of 480 aggregated interfaces on MX
Series routers. For MX Series routers running Junos release 14.2R3 and later you can
configure a maximum of 1000 aggregated interfaces. Aggregated interfaces are numbered
from ae0 through ae4092.
You must also include a statement defining aex at the [edit interfaces] hierarchy level.
You can optionally specify other physical properties that apply specifically to the
aggregated Ethernet interfaces; for details, see Ethernet Interfaces Overview, and for a
sample configuration, see Example: Configuring Aggregated Ethernet Interfaces.
Gigabit Ethernet IQ and SFP interfaces can be member links, but IQ- and
SFP-specific features are not supported on the aggregated Ethernet bundle
even if all the member links individually support those features.
You need to configure the correct link speed for the aggregated Ethernet
interface to eliminate any warning message.
Junos OS supports the aggregation of physical devices into defined virtual links, such as
the link aggregation of Ethernet interfaces defined by the IEEE 802.3ad standard.
[edit chassis]
aggregated-devices {
ethernet {
device-count number;
}
sonet {
device-count number;
}
}
The aggregated interfaces are numbered from ae0 through ae4091. The maximum number
of aggregated interfaces supported by different routers is listed below:
• For PTX Series routers, you can configure a maximum of 128 aggregated interfaces.
• For M Series and T Series routers, you can configure a maximum of 128 aggregated
interfaces (LAG bundles).
• In Junos release 14.2R2 and earlier, you can configure a maximum of 480 aggregated
interfaces on MX Series routers.
• In Junos release 14.2R3 and later, you can configure a maximum of 1000 aggregated
interfaces on MX240, MX480, and MX960 routers.
• In Junos release 14.2R3 and later, you can configure a maximum of 800 aggregated
interfaces on MX2010 and MX2020 routers.
• In Junos OS 15.1F5 and 15.1F6 releases, you can configure a maximum of 480 aggregated
interfaces on MX240, MX480, and MX960 routers.
• In Junos OS 15.1F5 and 15.1F6 releases, you can configure a maximum of 800 aggregated
interfaces on MX2010 and MX2020 routers.
For SONET/SDH, starting with Junos OS Release 13.2, the maximum number of logical
interfaces is 64, numbered from as0 through as63. In releases before Junos OS Release
13.2, the maximum was 16.
LACP link protection enables you to force active and standby links within an aggregated
Ethernet. You configure LACP link protection by using the link-protection and
system-priority statements at either the chassis or interface level and by configuring port
priority at the interface level using the system-priority statement. Configuring LACP
parameters at the chassis level results in all aggregated Ethernet interfaces using the
defined values unless overridden by the LACP configuration on a specific interface.
[edit chassis]
aggregated-devices {
ethernet {
lacp {
link-protection {
non-revertive;
}
system-priority priority;
}
}
}
NOTE: LACP link protection also uses port priority. You can configure port
priority at the Ethernet interface [gigether-options] hierarchy level using the
port-priority statement. If you choose not to configure port priority, LACP link
protection uses the default value for port priority (127).
See Also
Using the non-revertive statement for this purpose is not effective if both the
primary and secondary interfaces are on the MIC that reboots.
The system priority is a 2-octet binary value that is part of the LACP system ID. The LACP
system ID consists of the system priority as the two most-significant octets and the
interface MAC address as the six least-significant octets. The system with the numerically
lower value for system priority has the higher priority. By default, system priority is 127,
with a range of 0 through 65,535.
Starting in Junos OS Release 14.2R4, the timer values that ensure proper link aggregation
and STP functions are configured by default if you use Junos Fusion with Junos OS.
15.1F5 In Junos OS 15.1F5 and 15.1F6 releases, you can configure a maximum of 480
aggregated interfaces on MX240, MX480, and MX960 routers.
15.1F5 In Junos OS 15.1F5 and 15.1F6 releases, you can configure a maximum of 800
aggregated interfaces on MX2010 and MX2020 routers.
14.2R4 Starting in Junos OS Release 14.2R4, the timer values that ensure proper link
aggregation and STP functions are configured by default if you use Junos Fusion
with Junos OS.
14.2R3 In Junos release 14.2R3 and later, you can configure a maximum of 1000
aggregated interfaces on MX240, MX480, and MX960 routers.
14.2R3 In Junos release 14.2R3 and later, you can configure a maximum of 800
aggregated interfaces on MX2010 and MX2020 routers.
14.2R3 If you use Junos Fusion with Junos OS Release 14.2R3, you need to ensure that
link aggregation (and STP) work properly by configuring timers for the periodic
packet management (PPM) daemons on the aggregation and satellite devices.
14.2R2 In Junos release 14.2R2 and earlier, you can configure a maximum of 480
aggregated interfaces on MX Series routers.
13.2 For SONET/SDH, starting with Junos OS Release 13.2, the maximum number of
logical interfaces is 64, numbered from as0 through as63.
The uplink failure detection feature on a Junos Fusion enables satellite devices to detect
link failures on the uplink interfaces used to connect to aggregation devices. When uplink
failure detection detects uplink failure on a satellite device, all of the device’s extended
ports (which connect to host devices) are shut down. Shutting down the extended ports
allows downstream host devices to more quickly identify and adapt to the outage. For
example, when a host device is connected to two satellite devices, and uplink failure
detection shuts down the extended ports on one satellite device, the host device can
more quickly recognize the uplink failure and redirect traffic through the other, active
satellite device.
You can configure uplink failure detection globally, for all satellite devices of a Junos
Fusion, and for individual satellite devices. Uplink failure detection configuration at the
satellite device level overrides the global uplink failure detection configuration.
• The minimum number of active uplink ports a satellite device must have to remain
active. The default is one active uplink port. You can use this option to specify more
minimum active ports.
• The amount of time uplink failure detection waits to try to re-enable disabled extended
ports. This wait time is called a hold-down period. It is intended to avoid port flapping
on the extended ports when uplink port connectivity is unstable. The default hold-down
period is six seconds.
Uplink failure detection must know which ports on a satellite device can be used as uplink
ports. These are called candidate uplink ports. Table 39 on page 604 shows the default
set of candidate uplink ports that uplink failure detection selects for failure detection. If
you choose not to use the default uplink ports for your satellite devices, you need to
specify which uplink ports you want to use for uplink failure detection by creating a
candidate uplink port profile and applying it to the satellite device’s uplink failure detection
configuration.
EX4300-24T (4 ports each on PIC1 and PIC2) 1/0 through 1/3 and 2/0 through 2/3
EX4300-32F (4 ports on PIC 0, 2 ports on PIC 1 and 8 ports on PIC 0/32 through 0/35
2)
1/0 through 1/1
EX4300-48T (4 ports each on PIC1 and PIC2) 1/0 through 1/3 and 2/0 through 2/3
EX4300-48T-BF (4 ports each on PIC1 and PIC2) 1/0 through 1/3 and 2/0 through 2/3
The uplink failure detection feature on a Junos Fusion enables satellite devices to detect
link failures on the uplink interfaces used to connect to aggregation devices. When uplink
failure detection detects uplink failure on a satellite device, all of the device’s extended
ports (which connect to host devices) are shut down.
The following topics describe how to configure uplink failure detection on a Junos Fusion:
• To enable uplink failure detection globally, for all satellite devices in the Junos Fusion,
include the uplink failure detection configuration at the [edit chassis
satellite-management] level.
• To enable uplink failure detection on a specific satellite device, include the uplink failure
detection configuration at the [edit chassis satellite-management fpc slot-id] level.
Uplink failure detection configuration applied to a satellite device overrides the global
uplink failure detection configuration.
Uplink failure detection configuration syntax is the same at all hierarchy levels. This topic
shows how to configure uplink failure detection at the global level, but you can also apply
uplink failure detection configuration at the satellite device level.
To enable uplink failure detection on a Junos Fusion, do the following on the fabric’s
aggregation device:
Table 40: Junos Fusion Uplink Failure Detection Default Configuration (continued)
uplink-port-group Defines a set of candidate uplink ports Each satellite device model has a set of
to assign to satellite devices. default uplink ports. You only need to
assign uplink ports if you do not want to
use the default ports. See Table 39 on
page 604 for the default uplink ports by
device.
You can enter configuration statements in a candidate uplink port policy at these levels
of the hierarchy:
• Create terms within the candidate uplink port policy at the level [edit policy-options
satellite-policies candidate-uplink-port-policy policy-name term term-name]. Use terms
to apply different uplink failure detection configurations to certain satellite devices,
based on their product model. Each term contains match criteria that is compared
against the model name of each satellite device to which the policy is applied. If the
criteria matches the device model, the configuration specified in the term is applied
to the device. Terms are evaluated in the order they appear in the configuration. The
first term that matches a satellite device is applied to the device.
Uplink failure detection has the following default configuration parameters that apply if
you enable uplink failure detection with no additional configuration:
• The default uplink ports that are assigned to each satellite device type are described
in “Overview of Uplink Failure Detection on a Junos Fusion” on page 603.
A candidate uplink port policy can contain configuration statements that override the
defaults if the policy is applied to a satellite device that does not match a product-model
statement in any term in the policy.
1. (Optional) Specify the interval of time uplink failure detection waits before trying to
re-enable a satellite device’s extended ports after shutting them down due to an
uplink port failure:
2. (Optional) Specify the minimum number of active uplink ports a satellite device must
have. If a satellite device has fewer than this number of active uplink ports, uplink
failure detection shuts down its extended ports:
For information about configuring an uplink port group, see “Configuring an Uplink
Port Group” on page 608.
You can configure terms in a candidate uplink port policy to apply uplink failure detection
configuration to certain satellite devices, based on their device model. For example, you
can create a term that matches all QFX 5100 Series switches. When the policy is applied
to a QFX 5100 Series switch, the other configuration statements in the term are applied
to the switch. If the policy is applied to satellite devices that are not QFX 5100 Series
switches, the configuration statements in the term are not applied. When a candidate
uplink port policy has multiple terms, the terms are evaluated in the order they appear
in the configuration. The first term that matches a satellite device is applied to that
satellite device.
The other configuration statements in the term are only applied to satellite devices
whose device model matches the match term model-name.
The match term model-name can be a complete device model name, to match that
device model exactly. You can also use the wildcard character (*) in the match term
to match zero or more of any character.
• To apply the satellite policy to all EX 4300 Series switches in the satellite device
role, enter EX4300* as the model-name.
• To apply the satellite policy to all QFX 5100 Series switches in the satellite device
role, enter QFX5100* as the model-name.
• To apply the satellite policy to QFX 5100 Series switches with model names that
start with QFX5100-96, enter QFX5100-96* as the model-name.
2. (Optional) Specify the interval of time uplink failure detection waits to re-enable a
satellite device’s extended ports after shutting them down due to an uplink port failure:
3. (Optional) Specify the minimum number of active uplink ports a satellite device must
have. If a satellite device has fewer than this number of active uplink ports, uplink
failure detection shuts down its extended ports:
For information about configuring an uplink port group, see “Configuring an Uplink
Port Group” on page 608.
in “Overview of Uplink Failure Detection on a Junos Fusion” on page 603. You do not need
to create uplink ports groups if you want to use the default candidate uplink ports on
satellite devices.
2. Configure the PICs that will contain ports to be identified as candidate uplink ports:
3. Configure the ports on the PICs that will be identified as candidate uplink ports:
candidate-uplink-port-policy (satellite-policies)
Description Configures a candidate uplink port profile, which contains uplink failure detection feature
configuration that can be applied to satellite devices in a Junos Fusion.
holddown (candidate-uplink-port-profile)
Description Configures the interval of time uplink failure detection waits before trying to try re-enable
a satellite device’s extended ports after shutting them down due to an uplink port failure.
It is intended to avoid port flapping on the extended ports when uplink port connectivity
is unstable.
Options interval—The holddown interval, in seconds. Valid values are 1-600 seconds.
minimum-links (candidate-uplink-port-profile)
Description Configures the minimum number of active uplink ports a satellite device must have. If a
satellite device has fewer than this number of active uplink ports, uplink failure detection
shuts down its extended ports.
Options link-count—Specifies the minimum number of active uplink ports a satellite device must
have. Valid values are 1-32 links.
Description Specify the PIC number to apply a port group alias for satellite policies in a Junos Fusion.
You must also specify the ports on the PIC when you use this statement.
Description Specify the port or ports to apply a port group alias for satellite policies in a Junos Fusion.
You must also specify the PIC when you use this statement.
port-group-alias (satellite-policies)
Description Configure a port group alias for satellite policies in a Junos Fusion.
A port group alias is used to define the candidate uplink ports on satellite devices that
use the satellite policy.
A port group alias is associated with a satellite policy using the set uplink-port-group
uplink-port-group-name statement in the [edit policy-options satellite-policies
candidate-uplink-policy policy-name] hierarchy.
Default Each satellite device model has a set of default uplink ports (see “Overview of Uplink
Failure Detection on a Junos Fusion” on page 603). You only need to assign an uplink port
group to a satellite device if you do not want to use the default uplink ports.
Description Define the satellite device product models that will use the candidate uplink port policy
defined in the from statement.
The other statements in the same from statement are applied to satellite devices that
match the product-model model-name definition. Those configuration statements are
not applied to satellite devices that do not match the definition.
Options model-name—Defines the satellite device product models that will use the candidate
uplink port policy. It can be a complete device model name, to match that device
model exactly. You can also use the wildcard character (*) in the match term to
match zero or more of any character.
• To apply the satellite policy to all EX4300 switches in the satellite device role,
enter EX4300* as the model-name.
• To apply the satellite policy to all QFX5100 switches in the satellite device role,
enter QFX5100* as the model-name.
• To apply the satellite policy to QFX5100 switches with model names that start
with QFX5100-96, enter QFX5100-96* as the model-name.
satellite-policies
Syntax satellite-policies {
<candidate-uplink-port-profile policy-name> {
<holddownholddown-time>;
<minimum-linksnumber-of-links>;
<uplink-port-group uplink-port-group-name>;
term term-name {
from {
product-model model-name;
<holddown holddown-time>;
<minimum-links number-of-links>;
<uplink-port-group uplink-port-group-name>;
}
}
}
environment-monitoring-policy policy-name {
<alarm <linkdown>
term term-name {
from {
product-model model-name;
}
}
}
forwarding-policy {
policy-name {
port-group-extended name;
filter filter-name;
mirror-egress port-group-mirror port-group-mirror;
mirror-ingress port-group-mirror port-group-mirror,
port-group-uplink port-group-uplnk-name
holddowntime;
minimum-links number;
term term-name {
from {
port-group-extended name;
filter filter-name;
mirror-egress port-group-mirror port-group-mirror;
mirror-ingress port-group-mirror port-group-mirror,
port-group-uplink port-group-uplnk-name
holddowntime;
minimum-links number;
product-model model-name;
port-group-extended port-group-alias-name {
port-group-uplink port-group-alias-name;
}
}
}
}
}
port-group-alias port-group-alias-name {
pic pic-number {
port [port-number | port-number-range | all];
}
}
Release Information Statement introduced in Junos OS Release 14.2R3 for Junos Fusion.
term (candidate-uplink-policy)
Description Create and configure a term in a candidate uplink satellite policy within a Junos Fusion.
A term in a candidate uplink port policy in a Junos Fusion is used to apply an uplink failure
detection configuration to certain satellite devices, based on their product model only.
The more complex options that are available for other policies in Junos OS—such as the
terms available for routing policies—are not available for candidate uplink port policies.
from—The statements under the from statement define the satellite device model match
criteria and uplink failure detection configuration for the term. Each term can contain
only one from statement.
Syntax uplink-failure-detection {
<candidate-uplink-policy policy-name>;
}
The uplink failure detection feature on a Junos Fusion enables satellite devices to detect
link failures on the uplink interfaces used to connect to aggregation devices. When uplink
failure detection detects uplink failure on a satellite device, all of the device’s extended
ports (which connect to host devices) are shut down. Shutting down the extended ports
allows downstream host devices to more quickly identify and adapt to the outage. For
example, when a host device is connected to two satellite devices, and uplink failure
detection shuts down the extended ports on one satellite device, the host device can
more quickly recognize the uplink failure and redirect traffic through the other, active
satellite device.
You can configure uplink failure detection in a Junos Fusion for a single satellite device
using the fpc slot-id option. If uplink failure detection is enabled without specifying the
fpc slot-id option, uplink failure detection is enabled for all cascade ports on the
aggregation device.
Description In Junos Fusion configuration, assign an uplink port group to a candidate uplink port policy.
An uplink port group defines a set of candidate uplink ports that are assigned to satellite
devices to which the candidate uplink port group is assigned.
Uplink port groups are defined under [edit policy-options satellite-policies port-group-alias].
Default Each satellite device model has a set of default uplink ports (see “Overview of Uplink
Failure Detection on a Junos Fusion” on page 603). You only need to assign an uplink port
group to a satellite device if you do not want to use the default uplink ports.
Release Information Command introduced in Junos OS Release 14.2R3 for Junos Fusion Provider Edge.
Command introduced in Junos OS Release 16.1R1 for Junos Fusion Enterprise.
Command introduced in Junos OS Release 17.2R1 for Junos Fusion Data Center.
Description Display the status of the satellite device connections in a Junos Fusion.
since time—(Optional) Display the satellite devices that have been added to the Junos
Fusion on or after a certain date or time, in YYYY-MM-DD.HH:MM:SS format.
To display all satellite devices added since a specified date, enter the specific date.
For instance, to display all satellite devices added on or after December 22nd, 2015,
enter 2015-12-22 as the time.
To display all satellite devices added since a specified time, enter the specific date
and time. For instance, to display all satellite devices added on or after 11:01AM on
December 22nd, 2015, enter 2015-12-22.11:01:00 as the time.
Output Fields Table 19 on page 423 lists the output fields for the show chassis satellite command. Output
fields are listed in the approximate order in which they appear.
Device State The state of the satellite device within the Junos Fusion. brief
terse
The most common device states: extensive
none
• Online—the satellite device is online and active. This is the
satellite device state during normal operating procedure.
• Offline—the satellite device is offline and not detected. This
state is typically seen when the satellite device has been
disconnected from the aggregation device, or when all
cascade or uplink ports connecting the satellite device to
the aggregation device are down.
• Present—the satellite device is recognized by the
aggregation device, but is not online. This state is typically
seen before a satellite device goes online, or while satellite
device configuration is in progress or finalizing.
• Rebooting—the satellite device is rebooting.
• Disable—the satellite device has been disabled.
• Misconfig—the satellite device is not properly configured.
This state is typically seen when the system ID, cascade
port, or FPC slot ID defined for the satellite device has a
misconfiguration.
• Miswire—the satellite device is miswired. This state is
typically seen when a satellite device is wired to two
aggregation devices but is not configured for multihoming.
Use show chassis satellite detail to gather more information
on the issue when the device state is Miswire.
Port State The state of the cascade port on the aggregation device. brief
extensive
Port states include: none
Extended Ports The total number of extended ports on the satellite device. brief
Total none
An extended port is a network-facing port on the satellite terse
device that sends and receives network traffic for the Junos
Fusion.
Version The version of satellite device software running on the satellite terse
device.
FPC slot The FPC slot number of the satellite device. detail
System ID The system ID of the satellite device. The system ID is also the detail
satellite device’s MAC address.
Software The satellite software version running on the satellite device. detail
package
version
Host software The host operating system software version running on the detail
version satellite device.
Minimum link Uplink failure detection minimum active uplink port setting. detail
Extended Ports The number of extended ports for the satellite device. The extensive
number on the left is the total number of extended ports, and
the number on the right is the total number of extended ports
currently in the up state.
Uplink Interface The name of the uplink interface on the satellite device. detail
Adjacency The adjacency state of the cascade to uplink interface link. detail
state
Last transition The amount of time that has passed since the last transition detail
of the cascade to uplink interface link.
Adjacency The number of times the cascade to uplink interface link has detail
down count gone into the down state.
(Interface
Name)
Last received The amount of time that has passed since the last packet was detail
packet received on the cascade interface.
Peer adjacency The amount of time that has passed since the last peer detail
information adjacency transition.
Adjacency The number of times the cascade to uplink interface link has detail
down count gone into the down state.
(Peer
adjacency
information)
SDPD restart The number of times that the satellite device protocol process detail
detected has restarted.
Uptime The amount of time that the process has been running. detail
Sample Output
Sample Output
Sample Output
Sample Output
This topic introduces how multicast packets are replicated in a Junos Fusion and
forwarded to multicast subscribers on satellite device extended ports.
Multicast source packets might be received through a network port on the aggregation
device or an extended port on a satellite device. When a multicast source packet ingresses
at a satellite device, the satellite device sends the source packet on an uplink port to the
aggregation device in one of the following ways:
• In a Junos Fusion Data Center with MC-LAG, the satellite device load-balances source
traffic over the available uplink ports to either of the two available aggregation devices.
For example, see Figure 10 on page 638, where the source traffic from Host 1 on Satellite
Device 1 is load-balanced between Aggregation Device 1 and Aggregation Device 2.
Figure 10: Multicast Replication in a Junos Fusion Data Center with MC-LAG
Multicast Source
LAYER 2 /
LAYER 3
NETWORK
Multicast
Subscriber
CP5
CP1 CP2 CP3
UP4 CP4
UP3 UP5
UP1 UP2
Satellite Device 1 Satellite Device 2
Egress Replication on Satellite Devices Egress Replication on Satellite Devices
Multicast Subscriber
Multicast Source
Possible Ingress Multicast Source Packet Flow
Multicast Destination Packet Flow
Cascade Ports
Uplink Ports
g200021
Extended Ports
Aggregation Device Network Port
• In a Junos Fusion Data Center with EVPN, extended ports on the satellite devices are
multihomed to all aggregation devices, and each is modeled as an EVPN Ethernet
Segment (ES). One aggregation device is elected as the designated forwarder (DF)
for each ES. A satellite device receiving multicast source traffic hashes among the
uplink ports and forwards the traffic to one of its available aggregation devices. For
example, see Figure 11 on page 639, where Satellite Device 1 is multihomed to four
aggregation devices, and the source traffic from Host 1 on Satellite Device 1 is hashed
to Aggregation Device 2.
Figure 11: Multicast Replication in a Junos Fusion Data Center with EVPN
LAYER 2 / LAYER 3
NETWORK
EVPN
IGMP State synchronized to all ADs
(VLAN 100, 233.252.0.1) ->
(SD1 [ECIDx], SD2 [ECIDy])
Local Bias Check Local Bias Local Bias Check Local Bias Check
Do Not Forward Forwarding Do Not Forward Do Not Forward
Egress
ECIDy
VLAN 100
Multicast Group 233.252.0.1
g300102
Uplink Ports
Extended Ports
The aggregation device that initially receives the source traffic to be forwarded is referred
to as the ingress aggregation device. All multicast destination resolution is done on the
aggregation devices. In Junos Fusion architectures with multiple aggregation devices,
the ingress aggregation device also forwards the multicast traffic to the other aggregation
device or devices to reach multicast subscribers that are only accessible through those
other devices, or to support the forwarding behavior of a particular Junos Fusion
architecture.
• For Junos Fusion Data Center with MC-LAG, traffic is forwarded between aggregation
devices using the inter-chassis link (ICL).
• For Junos Fusion Data Center with EVPN, the traffic is flooded in the EVPN core to the
other aggregation devices to reach destinations that might only be available through
those devices.
By default, the ingress aggregation device replicates multicast and broadcast packets
to forward to each destination extended port. This behavior is referred to as ingress
multicast replication. The aggregation device sends multiple copies of the packet to each
satellite device, one copy for each destination extended port on that satellite device,
identified by the extended port’s unicast ECID. See “Ingress Replication at the Aggregation
Device to Satellite Devices” on page 643 for more information.
Starting in Junos OS Release 16.1, Junos Fusion supports enabling egress multicast
replication, also referred to as local replication, where satellite devices replicate the
multicast and broadcast packets destined for their local ports. Starting in Junos OS
Release 17.2R1, local replication is supported in Junos Fusion Data Center with MC-LAG
architectures. In Junos OS Release 18.1R2-S2, local replication is supported in Junos Fusion
Data Center with EVPN architectures. Egress or local replication uses special multicast
ECIDs corresponding to one or more extended ports to which a satellite device should
forward the traffic. (See “ECIDs for Multicast Traffic” on page 641.) Local replication helps
to distribute most of the replication load from aggregation devices to the satellite devices
where the traffic egresses, and reduces traffic on cascade ports. When enabled, local
replication applies to all satellite devices in the Junos Fusion; you cannot enable it only
for individual satellite devices.
Local replication behavior differs slightly for different types of multicast and broadcast
traffic, and for different Junos Fusion architectures. See “Egress (Local) Replication on
the Satellite Devices” on page 646 for details.
To avoid creating loops and broadcast storms, for both ingress and egress multicast
replication, both the aggregation devices and satellite devices maintain split-horizon
next-hop information to prevent resending multicast or broadcast packets back out of
the ingress port.
When local replication is disabled, similar to unicast packet flow (see “Understanding
the Flow of Data Packets in a Junos Fusion Topology” on page 26), the aggregation device
assigns a unicast ECID value for each destination extended port on a satellite device for
both unicast traffic and multicast traffic. The aggregation device replicates multicast
packets, tags them with the assigned ECID for the destination, and sends a copy to each
destination extended port by way of the corresponding satellite device interface.
When local replication is enabled, Junos Fusion uses ECID values greater than 4095 to
identify multicast traffic and associate one or more extended ports on a satellite device
as the multicast destination. Junos Fusion dynamically assigns multicast ECID values.
When the aggregation device requires a new multicast ECID value for a group of ports
or if it needs to add a port to an existing ECID, the process is as follows:
1. The aggregation device sends a request to the satellite device to assign an ECID value
(or update an existing ECID mapping when multicast group or VLAN membership
changes).
2. The satellite device assigns an ECID value and adds an entry to its ECID table to map
the ECID value to the corresponding extended ports.
3. The satellite device sends a message back to the aggregation device with the ECID
value that satisfies the request for the corresponding extended ports.
4. The aggregation device adds this information to its ECID table. It uses the sd virtual
interface as the next-hop interface to send multicast traffic for those extended ports
on the satellite device.
When the satellite device receives a data packet from the aggregation device with a
multicast ECID value, the satellite device begins to replicate and forward packets to the
extended ports associated with that ECID. Satellite devices do not do multicast lookups;
they only maintain ECID tables to determine the port or ports corresponding to an ECID
in a packet received from the aggregation device. The aggregation devices perform all
multicast route maintenance and forwarding path resolution.
NOTE: In Junos Fusion Data Center with EVPN, if multicast source traffic
ingresses on a link aggregation group (LAG) of extended ports that spans
satellite devices, the 802.1BR header carries the source (ingress) extended
port LAG ECID. The ingress aggregation device includes this header when
forwarding the traffic to other aggregation devices in the EVPN core. The
ingress aggregation device and any other DF aggregation devices that must
forward traffic to destination ESs include the source extended port LAG ECID
when sending the traffic to the satellite devices, so the satellite devices with
extended ports in the LAG can make spit-horizon decisions.
An ECID value is only unique locally on the satellite device. Another satellite device can
use the same ECID value for its own extended ports. The aggregation device maintains
a composite mapping of ECID values to the different satellite devices and the
corresponding extended ports on those satellite devices.
You might choose not to enable local replication because egress multicast replication
is incompatible with some Junos OS protocol and traffic management features
programmed on individual extended ports. The following features do not work when
egress multicast replication is enabled; if you want to use these features, you cannot
take advantage of egress replication optimizations:
• VLAN tag manipulations, such as VLAN tag translations, VLAN tag stacking, and VLAN
per-port policies. Using egress multicast replication with this feature can cause dropped
packets due to unexpected VLAN tags.
• Multicast support for the extended ports on the edge side of Pseudowire connection
in a VPLS network.
• Multicast support for the extended ports on the edge side of EVPNs.
• Features that perform egress actions on individual extended ports, such as egress
local-port mirroring (port mirroring on endpoints connected to satellite device extended
ports).
16.1 Starting in Junos OS Release 16.1, Junos Fusion supports enabling egress
multicast replication, also referred to as local replication, where satellite devices
replicate the multicast and broadcast packets destined for their local ports.
Related • Ingress Replication at the Aggregation Device to Satellite Devices on page 643
Documentation
• Egress (Local) Replication on the Satellite Devices on page 646
By default, Junos Fusion uses ingress replication on the aggregation devices to replicate
and forward copies of packets to multicast destinations.
In ingress replication mode, the ingress aggregation device replicates the multicast
packets and forwards them to every destination extended port. The data packet flow is
similar to unicast data packet flow from the multicast source to each destination.
Figure 12 on page 644 shows multicast source data packets received from a multicast
source on an extended port, EP1, with traffic destined for endpoints connected to extended
ports EP2 through EP5. Each extended port has an associated E-channel Identifier (ECID)
value that the aggregation device uses to forward the data packet to each destination
extended port. The aggregation device replicates the data packets for all multicast
destination extended ports on all attached satellite devices, as follows:
Aggregation
Device
ECID2 ECID5
ECID3 ECID4
g043466
Uplink Ports
Extended Ports
The aggregation device sends each packet on the respective cascade ports to the satellite
devices with destination extended ports. Multicast traffic destined for EP2 is tagged with
ECID2, traffic destined for EP3 is tagged with ECID3, and so on for all the destination
extended ports on both satellite devices. The satellite devices receive and forward the
packets to their respective extended ports.
The aggregation device maintains multicast routing information and next-hop tables,
including ECID label mappings to satellite devices and the corresponding extended ports.
For a multicast destination on a satellite device, the aggregation device resolves the
next-hop path through a corresponding cascade port that reaches the satellite device.
When there are multiple cascade port links to a satellite device, the aggregation device
load-balances the traffic to choose which cascade port to use.
Each receiving satellite device maintains tables that map the assigned ECIDs to the
corresponding extended ports, and simply forwards outgoing multicast packets to the
destination extended ports. The satellite devices do not maintain multicast routing
information.
Other multicast destinations might be reached through local ports on the aggregation
device, rather than through extended ports. For these destinations, the aggregation device
creates and sends copies to those local ports directly.
In Junos Fusion Data Center with MC-LAG topologies, which have dual aggregation
devices, for multicast subscribers on ports on the other aggregation device, the ingress
aggregation device creates copies for those ports, and sends them over the ICL link to
the other aggregation device to forward to its local destination ports.
In a Junos Fusion Data Center with EVPN, the ingress aggregation device floods the traffic
in the EVPN core to all other aggregation devices, and uses local bias forwarding whenever
possible to send a copy of the multicast stream to all locally-reachable destination
extended port Ethernet Segments (ESs). See Figure 13 on page 645. Other aggregation
devices that are designated forwarders (DFs) for multihomed destination ESs perform
a local bias check, and only forward traffic to their designated ESs that the ingress
aggregation device could not reach. In either the local bias or DF forwarding case with
ingress replication, the forwarding aggregation device sends one copy of the multicast
stream to every destination ES using the extended port ECID, similar to
Figure 12 on page 644.
Figure 13: Ingress Replication to the Satellite Devices in a Junos Fusion with EVPN
LAYER 2 / LAYER 3
NETWORK
EVPN
Aggregation Aggregation Aggregation Aggregation
Device 1 Device 2 Device 3 Device 4
EVPN-VXLAN
Ingress Replication
in EVPN Core
Local Bias Check Local Bias Local Bias Check Local Bias Check
Do Not Forward Forwarding Do Not Forward Do Not Forward RCVR
Ingress Replication
to Extended Ports Forward to
on Satellite Devices Local-only
Receiver
Egress
ECID[EP3]
Egress Egress
ECID[EP6] ECID[EP7]
EP1 EP2 EP3 LAG EP6 EP7 LAG EP10 EP11 LAG EP14 EP15 EP16
g300101
Uplink Ports
Extended Ports
Multicast support using ingress replication does not scale well for a large number of
multicast destinations or higher bandwidth multicast traffic. Ingress replication increases
aggregation device Packet Forwarding Engine processing load and consumes bandwidth
on the links between cascade ports and uplink ports, potentially resulting in link
oversubscription and latency among multicast recipients.
You can alternatively enable egress multicast replication, also referred to as local
replication. Local replication optimizes multicast replication by distributing the replication
load between the aggregation devices and the satellite devices that have multicast
destination ports. However, local replication requires more control plane processing than
ingress replication, which results in a slight increase in multicast group join and leave
latency. See “Egress (Local) Replication on the Satellite Devices” on page 646 for more
information on how local replication works for different types of multicast or broadcast
traffic.
Local replication is performed at Layer 2. Each receiving satellite device maintains tables
that map the assigned ECIDs to corresponding destination extended ports, and simply
forward outgoing multicast or broadcast packets to local extended ports. For Layer 3
multicast traffic, such as when forwarding packets between VLANs, the aggregation
device performs replication to resolve Layer 3 information not maintained by satellite
devices.
This topic describes local replication behavior for multicast traffic forwarded to the
access side both within and across VLANs and when flooding traffic within a VLAN.
• Local Replication for Layer 2 Multicast Traffic with IGMP Snooping on page 646
• Local Replication for VLAN Flooding on page 649
• Local Replication for Layer 3 Multicast Traffic Over IRB Interfaces on page 650
Figure 14: Local Replication with Layer 2 Multicast and IGMP Snooping in Junos Fusion
Aggregation
Device
ECID4096 ECID4097
Multicast Subscriber
Multicast Source
Multicast Source Packet Flow
Host Host Host Host Host Multicast Destination Packet Flow
1 2 3 4 5
Cascade Ports
g043467
Uplink Ports
Extended Ports
A data packet is received from a multicast source on an extended port, EP1, with traffic
destined for endpoints connected to extended ports EP2 through EP5. The aggregation
device acquires multicast ECIDs from the satellite devices, which represent a set of
multicast destination extended ports on each satellite device. The diagram shows ECID
value ECID4096 is assigned to the multicast subscribers behind extended ports EP2 and
EP3 on satellite device 1, and ECID4097 is assigned to the multicast subscribers behind
extended ports EP4 and EP5 on satellite device 2. The aggregation device creates only
one copy of the source packet for each satellite device that has multicast destination
extended ports, inserts the corresponding satellite device multicast ECID value in the
IEEE 802.1BR ETAG header of each copy, and forwards the copies to those satellite
devices.
In this case, the aggregation device creates two copies, forwards one with ECID4096 to
satellite device 1, and forwards the other with ECID4097 to satellite device 2. Each satellite
device receives its copy and uses the multicast ECID value to determine which of its
extended ports should receive the multicast traffic. Satellite device 1 replicates the packet
and forwards copies to EP2 and EP3; satellite device 2 replicates the packet and forwards
copies to EP4 and EP5.
When forwarding replicated multicast packets to satellite devices, the aggregation device
resolves the next-hop path through a corresponding cascade port that reaches the
satellite device. When there are multiple cascade port links to a satellite device, the
aggregation device load-balances the traffic when choosing which cascade port to use.
Other multicast destinations might be reached through ports on the aggregation devices,
rather than through extended ports. For these destinations, the aggregation device creates
and sends copies to those local ports directly.
In Junos Fusion Data Center with MC-LAG topologies, which have dual aggregation
devices, for multicast subscribers behind ports on the other aggregation device, the
ingress aggregation device creates copies for those ports, and sends them over the ICL
link to the other aggregation device to forward to its local destination ports. This behavior
is the same for ingress or egress multicast replication.
In a Junos Fusion Data Center with EVPN, when local replication is enabled, multicast
traffic follows the same behavior shown in Figure 14 on page 647 using multicast ECIDs
between the forwarding aggregation device and the destination extended ports’ satellite
devices. See Figure 15 on page 648.
Figure 15: Local Replication with Layer 2 Multicast and IGMP Snooping in Junos Fusion
Data Center with EVPN
LAYER 2 / LAYER 3
NETWORK
EVPN
IGMP State synchronized to all ADs
(VLAN 100, 233.252.0.1) ->
(SD1 [ECIDx], SD2 [ECIDy])
Local Bias Check Local Bias Local Bias Check Local Bias Check
Do Not Forward Forwarding Do Not Forward Do Not Forward
Egress
ECIDy
VLAN 100
Multicast Group 233.252.0.1
g300102
Uplink Ports
Extended Ports
In a Junos Fusion Data Center with EVPN, the forwarding aggregation device might be
the ingress aggregation device employing local bias forwarding to any reachable
destination extended port Ethernet Segments (ESs), or the designated forwarder (DF)
for a destination extended port ES that the ingress aggregation device could not reach.
In either the local bias or DF forwarding case, with local replication enabled, the forwarding
aggregation device sends only one copy of the multicast stream to each satellite device
that has one or more multicast destination extended port ESs. The ingress aggregation
device also floods the traffic toward the EVPN core so other aggregation devices can
forward the traffic to ESs that the ingress aggregation device cannot reach using local
bias forwarding. See Multicast Forwarding at Layer 2 in a Junos Fusion Data Center with
EVPN for details.
Figure 16 on page 649 illustrates the packet flow for VLAN flooding when local replication
is enabled.
Aggregation
Device
ECID4096 ECID4097
g200020
Uplink Ports
Extended Ports
In this example, a multicast source packet for VLAN 100 ingresses on EP1, and satellite
device 1 forwards the packet to the aggregation device. The aggregation device cannot
resolve the destination MAC address, and decides to flood the packet to all extended
port destinations in VLAN 100.
NOTE: When a source packet ingresses at a satellite device with uplink ports
to dual aggregation devices, the satellite device load-balances forwarding
the ingress traffic among the available uplink ports, so either aggregation
device might receive the source packet and manage flooding the packet to
destination VLAN members.
for the flooded traffic. The aggregation device creates one copy of the packet tagged
with ECID4096 and sends it to satellite device 1, and sends one copy tagged with
ECID4097 to satellite device 2. Satellite device 1 replicates and forwards the packet for
its own destination ports in VLAN 100, EP2 and EP3. (The ingress ECID split-horizon
mechanism prevents forwarding traffic to the ingress port, EP1.) Satellite device 2
replicates and forwards the packet for EP4 and EP5, its local destination ports in VLAN
100. The extended port mapping for ECID4097 does not include EP6, so satellite device
2 does not forward the packet to that port.
When there are multiple cascade port links to a satellite device, the aggregation device
load-balances the traffic when choosing which cascade port to use.
For destination VLAN members reachable through aggregation device ports (rather than
extended ports), the aggregation device creates and sends copies to those local ports
directly.
In Junos Fusion Data Center with MC-LAG topologies, which have dual aggregation
devices, when there are VLAN members behind ports on the other aggregation device,
the ingress aggregation device creates copies for those ports, and sends them over the
ICL link to the other aggregation device to forward to its local destination ports. This
behavior is the same for ingress or egress multicast replication.
In a Junos Fusion Data Center with EVPN, the aggregation devices handle VLAN flooding
in the same way as multicast traffic forwarding. See Figure 15 on page 648. The ingress
aggregation device (Aggregation Device 2 in the figure) floods the traffic in the EVPN
core to all other aggregation devices, and uses local bias forwarding whenever possible
to send a copy of the multicast stream to all locally-reachable extended port Ethernet
Segments (ESs) in the VLAN (EP2 on Satellite Device 1 and EP3 and EP4 on Satellite
Device 2 in Figure 15 on page 648). The other aggregation devices that are designated
forwarders (DFs) for multihomed ESs in the VLAN perform a local bias check, and only
forward traffic to their designated ESs that the ingress aggregation device could not
reach. In either the local bias or DF forwarding case with local replication enabled, the
forwarding aggregation device sends only one copy of the traffic stream to each satellite
device that has one or more extended port ESs in the VLAN. See Multicast Forwarding at
Layer 2 in a Junos Fusion Data Center with EVPN for details.
In Junos Fusion Enterprise or Junos Fusion Provider Edge architectures, the aggregation
device forwarding the traffic replicates the multicast source packet for each IRB interface
in the Layer 3 replication list for a multicast group, and performs a VLAN tag rewrite for
each corresponding VLAN. When there are extended ports in multiple VLANs on a satellite
device that are receivers in the same multicast group, the aggregation device sends copies
to each IRB with its corresponding VLAN ID to that satellite device. If an IRB interface
(VLAN membership) spans multiple satellite devices, the aggregation device creates
and sends one copy to each satellite device that has multicast receivers that are members
of that VLAN. Each satellite device then replicates and forwards copies of the received
packet for its local multicast destination extended ports.
Figure 17 on page 651 shows an example of Layer 3 multicast replication for VLANs over
IRB interfaces in a Junos Fusion. In this case, two VLANs with corresponding IRB interfaces
are configured on the aggregation device. In this case, multicast source packets ingress
on an aggregation device port, and multicast subscribers are connected to extended
ports EP1 through EP5, where extended ports EP1 and EP2 are in VLAN 100 and EP3
through EP5 are in VLAN 200.
Aggregation
Multicast Source Device
Network
Multicast Subscriber
Multicast Source
Host Host Host Host Host Multicast Source Packet Flow
1 2 3 4 5
Multicast Destination Packet Flow
VLAN 100 VLAN 200 Cascade Ports
Uplink Ports
g043468
Extended Ports
Aggregation Device Network Port
When the aggregation device receives a packet from the multicast source, it manages
the Layer 3 replication by acquiring multicast ECIDs representing the destination extended
ports in each VLAN on each satellite device, and creating, tagging, and forwarding copies
on each VLAN’s IRB interface to the satellite devices that have destination extended
ports. As the figure shows, the aggregation device creates 3 copies of the source packet,
as follows:
• Multicast ECID4096 represents EP1 and EP2 in VLAN 100 on satellite device 1. The
aggregation device forwards one copy tagged with ECID4096 to satellite device 1 for
the VLAN 100 IRB interface.
• Multicast ECID4097 represents EP3 in VLAN 200 on satellite device 1. The aggregation
device forwards a second copy tagged with ECID4097 to satellite device 1 for the VLAN
200 IRB interface.
• Multicast ECID4098 represents EP4 and EP5 in VLAN 200 on satellite device 2. The
aggregation device forwards a third copy tagged with ECID4098 for the VLAN 200 IRB
interface to satellite device 2.
Each satellite device manages the Layer 2 processing by replicating the packets received
from the aggregation device for the multicast subscribers behind its extended ports in
each VLAN, as follows:
• Satellite device 1 replicates and forwards packets tagged with ECID4096 to extended
ports EP1 and EP2, and forwards packets tagged with ECID4097 to EP3.
• Satellite device 2 replicates and forwards the packets tagged with ECID4096 to
extended ports EP4 and EP5.
When there are multiple cascade port links to a satellite device, the aggregation device
load-balances the traffic when choosing which cascade port to use.
For multicast destination VLAN members reachable through aggregation device ports
(rather than extended ports), the aggregation device creates and sends copies to those
local ports using the corresponding IRB interfaces.
In a Junos Fusion Data Center with MC-LAG, which has dual aggregation devices, when
there are multicast subscribers behind ports on the other aggregation device, the ingress
aggregation device creates copies for those ports, and sends them over the ICL link to
the other aggregation device to forward to its local destination ports. This behavior is the
same for ingress or egress multicast replication.
For details on multicast traffic routing at Layer 3 in a Junos Fusion Data Center with EVPN,
which uses an external gateway device to route traffic between VLANs, see Multicast
Forwarding at Layer 3 in a Junos Fusion Data Center with EVPN.
By default, egress replication (also called local replication) for multi-destination traffic
is disabled, and Junos Fusion uses ingress replication on the access side. When you enable
local replication, the feature is activated for all satellite devices that are connected to
the aggregation device. You cannot enable local replication for just a few selected satellite
devices, specific bridge domains, or specific route prefixes.
The show multicast summary satellite operational command displays Egress replication:
Enabled when this feature is configured.
See “Understanding Multicast Replication in a Junos Fusion” on page 637 for an overview
of Junos Fusion multicast replication and the limitations to enabling this feature. Some
Junos OS protocol and traffic management features are not supported with egress
replication, and you should not plan to configure local replication if you want to use those
features.
For full details on how multicast traffic is forwarded in a Junos Fusion Data Center with
EVPN, which uses 802.1BR ECIDs in conjunction with multidestination traffic forwarding
elements of EVPN networks, see Multicast Forwarding at Layer 2 in a Junos Fusion Data
Center with EVPN.
Related • Ingress Replication at the Aggregation Device to Satellite Devices on page 643
Documentation
• Egress (Local) Replication on the Satellite Devices on page 646
• Monitoring Layer 2 Multicast Forwarding in a Junos Fusion Data Center with EVPN
local-replication
Syntax local-replication
Description Enables multicast replication on all the satellite devices that are connected to the
aggregation device. You cannot selectively enable local replication for specific satellite
devices, bridge domains, or route prefixes.
Description Display bridge domain flood next hop information for satellite device destinations.
• View the current list of all flood traffic composite next hops.
The aggregation device allocates ECID tags that represent multicast or broadcast
destinations behind satellite device extended ports, associates them with the
corresponding satellite device virtual interfaces (sd-fpc-id/0/0), and updates flood
next-hop table entries accordingly. More detailed output from this command shows
events that result in next-hop table updates.
Options brief | detail | extensive—(Optional) Display the specified level of output. The default
output level is brief.
nexthop-id nexthop-id—Display more detailed bridge flooding next hop information only
for the specified next hop.
List of Sample Output show bridge flood next hops on page 658
Output Fields Table 42 on page 657 lists the output fields for the show bridge flood next-hops satellite
command. Output fields are listed in the approximate order in which they appear.
Table 42: show bridge flood next-hops satellite Command Output Fields
Table 42: show bridge flood next-hops satellite Command Output Fields (continued)
Table Name of next-hop routing or forwarding table for the listed All
entry.
satellite-device-id Satellite device ID with the next-hop IDs and interface names detail
id to reach extended ports that are flood destinations on the
listed satellite device. extensive
When Elapsed time since an event related to a flood next-hop entry extensive
change.
Event Brief description of the event related to a flood next-hop entry extensive
change.
Action Brief description of actions that resulted from the event. extensive
Sample Output
Description Display bridge flood routing information for the satellite devices in Junos Fusion Provider
Edge.
This command lists flood routes by route prefix for each bridge domain. Each flood route
prefix entry lists the ingress replication next-hop ID (NhIndex). When egress (local)
replication is enabled and the bridge domain has multiple destination extended ports on
a satellite device, the aggregation device:
• Creates a satellite device next-hop chain to reach those destinations through their
corresponding satellite devices.
• Updates the flood route entry with a satellite next-hop chain ID (Satellite-Nh).
When a flood route does not have a satellite next-hop chain, the value 0 is displayed in
the Satellite-Nh column. When the Satellite-Nh value is non-zero, the aggregation device
uses the satellite next-hop chain instead of the original ingress replication next-hop
(NhIndex). You can see satellite device flood next-hop chain details, including the ECIDs
assigned to satellite device flood destination extended ports, using the detail option and
the bridge-domain-name option for a specific bridge domain.
Output Fields Table 43 on page 661 lists the output fields for the show bridge flood satellite command.
Output fields are listed in the approximate order in which they appear, although the
display order varies between the different levels of output.
NhIndex The ingress replication next-hop for the flood route. All
Next-hop Details for each next hop, listed by next-hop or satellite detail
information next-hop iID.
extensive
aggregation-device Next-hop interfaces for ports that are flood destinations on detail
the aggregation device, listed by next-hop ID.
extensive
satellite-device-id Next-hop interfaces for extended ports that are flood detail
id destinations on satellite devices, listed by satellite next-hop
ID. extensive
extensive
When Elaspsed time since an event related to a flood route entry extensive
change.
Event Brief description of the event related to a flood route entry extensive
change.
Action Brief description of actions that resulted from the event. extensive
Sample Output
Description Display status and control information for all satellite devices or a specified satellite
device.
Options brief | detail—(Optional) Display the specified level of output. The default output level
is brief.
Output Fields Table 44 on page 663 lists the output fields for the show bridge satellite device command.
Output fields are listed in the approximate order in which they appear, although the
display order varies between the different levels of output.
Device (detail
view)
Interface Index Internal ID for the satellite device virtual interface. All
Device
Interface Index
(detail view)
Interface Name Satellite device virtual interface name (sd-fpc-id/0/0, where All
fpc-id is the satellite device ID).
Device
Interface Name
(detail view)
Table 44: show bridge satellite device Command Output Fields (continued)
State State of the satellite device virtual interface. If the interface All
is created and active, possible values include Up or Down.
Device
Interface State
(detail view)
Requests Number of request messages sent to the listed satellite device All
aggregation device to allocate or update ECID mappings.
Echo packets Number of keep-alive packets sent to the satellite device detail
sent from the aggregation device.
Multicast IPC Number of inter-process control (IPC) messages sent from detail
stats the aggregation device to the satellite device related to
multicast functions on the satellite device. This value is
displayed for active satellite device connections.
Bridge IPC stats Number of IPC messages sent from the aggregation device detail
to the satellite device related to Layer 2 bridging functions
on the satellite device. This value is displayed for active
satellite device connections.
Sample Output
ECID database entries map a group of extended ports to an ECID value for the satellite
devices in a Junos Fusion. Each entry also records the next hop to reach the corresponding
destination extended ports.
device-id device-ID—Display information from the ECID database for a specified satellite
device ID.
ecid ecid—Display information from the ECID database for a specified ECID.
reference-id reference ID—Display information from the ECID database for a specified
internally-assigned reference ID related to the ECID request messages exchanged
during ECID allocation (used for troubleshooting issues with ECID allocation).
Output Fields Table 45 on page 666 lists the output fields for the show multicast ecid-mapping satellite
command. Output fields are listed in the approximate order in which they appear.
Table 45: show multicast ecid-mapping satellite Command Output Fields (continued)
State Status of requesting and allocating the ECID. Values include: All
Reference ID Internal reference ID assigned to an ECID request message, All (with specified device-id or ecid)
used for troubleshooting ECID communication with satellite
devices.
Sample Output
xe-103/0/7.0
xe-103/0/8.0
103 4105 Ready [nhid=1069] 0x0
xe-103/0/10.0
xe-103/0/9.0
103 4106 Ready [nhid=1070] 0x0
xe-103/0/11.0
xe-103/0/12.0
103 4107 Ready [nhid=1071] 0x0
xe-103/0/13.0
xe-103/0/14.0
103 4109 Ready [nhid=1097] 0x0
xe-103/0/15.0
xe-103/0/16.0
103 4110 Ready [nhid=1074] 0x0
xe-103/0/17.0
xe-103/0/18.0
103 4111 Ready [nhid=1075] 0x0
xe-103/0/19.0
xe-103/0/20.0
103 4112 Ready [nhid=1076] 0x0
xe-103/0/21.0
xe-103/0/22.0
show multicast ecid-mapping satellite (for specified satellite device-id and ECID)
user@host> show multicast ecid-mapping satellite device-id 100 ecid 4101
The output lists next-hops for all interfaces in the VPLS address family used in multicast
replication.
Options brief | detail—(Optional) Output level is the same when either option or no option is
specified.
Output Fields Table 46 on page 669 lists the output fields for the show multicast next-hops satellite
command. Output fields are listed in the approximate order in which they appear, although
the display order varies between the different levels of output.
Interface Name Interface name for configured interfaces in the Junos Fusion. All
Table 46: show multicast next-hops satellite Command Output Fields (continued)
Sample Output
Description Display detailed multicast next-hop information for satellite device destinations.
The aggregation device allocates ECID tags that represent multicast or broadcast
destinations behind satellite device extended ports, associates them with the
corresponding satellite device virtual interfaces (sd-fpc-id/0/0), and updates multicast
next-hop table entries accordingly. More detailed output from this command shows
events that result in next-hop table updates.
Options brief | detail | extensive—(Optional) Display the specified level of output. The default
output level is brief.
• Monitoring Layer 2 Multicast Forwarding in a Junos Fusion Data Center with EVPN
List of Sample Output show multicast snooping next-hops satellite on page 674
show multicast snooping next-hops satellite nexthop-id (detail view for a specified
next-hop ID) on page 674
show multicast snooping next-hops satellite nexthop-id (detail view for a specified
next-hop ID on Junos Fusion Data Center with EVPN-VXLAN) on page 675
show multicast snooping next-hops satellite nexthop-id (extensive view for a specified
next-hop ID) on page 675
Output Fields Table 47 on page 673 lists the output fields for the show ethernet-switching flood next-hops
satellite command. Output fields are listed in the approximate order in which they appear.
Table 47: show multicast snooping next-hops satellite Command Output Fields
Next-hop ID Multicast next-hop ID (original multicast next hop used with All
ingress multicast replication).
Table Name of routing or forwarding table for the listed entry. All
EVPN VXLAN (Junos Fusion Data Center with EVPN-VXLAN) Ingress detail
Core replication next-hop chain list for VXLAN remote VTEPs
(RVTEPs) extensive
Mrouter Next-hop list for multicast routers connected to the bridge detail
domain or VLAN.
extensive
aggregation-device Next-hop IDs and corresponding interfaces for the composite detail
next hop to reach local multicast destination ports on the
aggregation device. extensive
satellite-device-id Satellite device ID with the next-hop IDs and corresponding detail
id interface names for the composite next-hop chain to reach
extended ports that are multicast destinations on that satellite extensive
device.
Table 47: show multicast snooping next-hops satellite Command Output Fields (continued)
Linked Multicast satellite next-hop ID (next hop used with egress detail
Next-hop multicast replication).
extensive
Action Brief description of actions that resulted from the event. extensive
Sample Output
show multicast snooping next-hops satellite nexthop-id (detail view for a specified next-hop ID)
user@host> show multicast snooping next-hops satellite nexthop-id 524296 detail
show multicast snooping next-hops satellite nexthop-id (detail view for a specified next-hop ID on Junos Fusion
Data Center with EVPN-VXLAN)
user@host> show multicast snooping next-hops satellite nexthop-id 524296 detail
show multicast snooping next-hops satellite nexthop-id (extensive view for a specified next-hop ID)
user@host> show multicast snooping next-hops satellite nexthop-id 1048576 extensive
Description Display Layer 2 multicast routing information (with IGMP snooping) for destination ports
on satellite devices.
This command lists multicast routing entries by route prefix and bridge domain name
(Junos Fusion Provider Edge) or VLAN name (Junos Fusion Data Center). Each route
entry lists the next-hop ID (NH Index) used when the aggregation device performs ingress
multicast replication. When local replication is enabled and the VLAN has multicast
destination extended ports on a satellite device, the aggregation device:
• Creates a satellite device next-hop chain to those multicast destinations through their
corresponding satellite device.
• Updates the multicast route entry with a link to the satellite next-hop chain (Linked
NH Index).
If a multicast route does not have a satellite next-hop chain, Linked NH Index is 0. When
the Linked NH Index value is non-zero, NH Index refers to the original next-hop information,
but the aggregation device uses the satellite next-hop chain (Linked NH Index) for routing
multicast traffic to satellite device extended ports. Use the detail or extensive option to
expand the output to include details about the original next-hop and satellite next-hop
chains.
Options brief | detail | extensive—(Optional) Display the specified level of output. The default
output level is brief. The detail output level expands the original and satellite device
next-hop chains for each route displayed. The extensive output level includes details
about multicast next-hop entry update events used mainly for troubleshooting.
vlan-name vlan-name—(Junos Fusion Data Center only) Filter output to display VLAN
flooding information only for the specified VLAN name.
group group-address—Filter output to display flooding information only for the specified
multicast group.
source source-address—Filter output to display flooding information only for the specified
multicast source.
• Monitoring Layer 2 Multicast Forwarding in a Junos Fusion Data Center with EVPN
List of Sample Output show multicast snooping route satellite on page 679
show multicast snooping route satellite detail on page 680
show multicast snooping route satellite group on page 681
show multicast snooping route satellite vlan-name (for specific VLAN on Junos Fusion
Data Center) on page 681
show multicast snooping route satellite group address vlan-name (detail for specific
VLAN on Junos Fusion Data Center) on page 681
show multicast snooping route satellite bridge-domain-name (for specific bridge
domain with detail view on Junos Fusion Provider Edge) on page 682
Output Fields Table 48 on page 678 lists the output fields for the show multicast snooping route satellite
command. Output fields are listed in the approximate order in which they appear.
Table 48: show multicast snooping route satellite Command Output Fields
Route Multicast route information listed by route prefix under this All
heading.
NH Index Multicast next-hop ID (original multicast next hop used with brief
ingress multicast replication).
Linked NH Multicast satellite next-hop ID (next hop used with egress brief
Index multicast replication).
Next-hop Detailed list of next-hop chain information for the original and detail
information satellite next-hop chains, listed by original next-hop index (NH
Index) and satellite next-hop chain index (Linked NH Index) extensive
output field values.
Table 48: show multicast snooping route satellite Command Output Fields (continued)
EVPN VXLAN (Junos Fusion Data Center with EVPN-VXLAN) Ingress detail
Core replication next-hop chain list for VXLAN remote VTEPs
(RVTEPs) extensive
Mrouter Next-hop chain list for multicast routers connected to the detail
bridge domain or VLAN.
extensive
aggregation-device Next-hop IDs and corresponding interfaces for the composite detail
next hop to reach local multicast destination ports on the
aggregation device. extensive
satellite-device-id Satellite device ID with the next-hop IDs and corresponding detail
id interface names for the composite next-hop chain to reach
extended ports that are multicast destinations on that satellite extensive
device.
Action Brief description of actions that resulted from the event. extensive
Sample Output
524293
aggregation-device:
->1708 et-0/0/30.0
->1826 xe-0/0/28:1.0
satellite-device-id 100:
->1845 sd-100/0/0.32770 label=4101
satellite-device-id 106:
->1847 sd-106/0/0.32770 label=4103
show multicast snooping route satellite vlan-name (for specific VLAN on Junos Fusion Data Center)
user@host> show multicast snooping route satellite vlan-name VLAN800 group 233.252.0.1
show multicast snooping route satellite group address vlan-name (detail for specific VLAN on Junos Fusion
Data Center)
user@host> show multicast snooping route satellite group 233.252.0.1 vlan-name v1 detail
aggregation-device:
->1767 xe-0/0/12:2.0
satellite-device-id 101:
->7555 sd-101/0/0.32770 label=4097
EVPN VXLAN Core:
2097156
->4808 VXLAN RVTEP: 10.4.4.4
->4812 VXLAN RVTEP: 10.3.3.3
->9813 VXLAN RVTEP: 10.1.1.1
MRouter:
2099159
aggregation-device:
->1766 xe-0/0/12:1.0
show multicast snooping route satellite bridge-domain-name (for specific bridge domain with detail view on
Junos Fusion Provider Edge)
user@host> show multicast snooping route satellite bridge-domain-name bd100 group 233.252.0.1
detail
Description Display statistics about multicast satellite routing tables and ECID management.
Options brief | detail—(Optional) Display the specified level of output. The default output level
is brief.
Sample Output
Multicast Statistics:
Number of flood route entries: 8000
Number of satellite flood route entries: 8000
Number of MCINET route entries: 44000
Number of satellite MCINET route entries: 36000
Unicast VPLS next-hops(non-satellite): 32
Number of satellite ECID next-hops: 12
Number of VPLS composite next-hops: 12000
Number of satellite composite next-hops: 12000
Number of Indirect next-hops: 28002
Number of Satellite Indirect next-hops: 28001
Number of ECIDs requested: 14
Number of ECID responses received: 14
Number of ECID delete messages: 2
Number of ECID mapping entries in DB: 12
Number of ECID mapping entries ready: 12
This command displays whether or not egress multicast replication (also called local
replication) is enabled. When local replication is configured, this command displays
Egress replication: Enabled, and Egress replication: Disabled otherwise.
This command also displays the graceful restart state of the satellite management
control plane processes for local replication when these processes are first activated or
have been restarted. The Restart phase output field value indicates the phase where the
restart process stalled or failed, or displays a Complete message if the restart process
completed successfully.
Sample Output
Multicast:
Restart phase: Complete (11/11)
Egress replication: Enabled
See Figure 18 on page 685 for an illustration of the Junos Fusion topology.
This topic describes class of service (CoS) on the different types of ports in Junos Fusion.
All configuration for CoS policies for Junos Fusion is done on the aggregation device. For
CoS policies that you define for extended ports, however, different portions of that policy
are applied at different points in a packet’s path through Junos Fusion. From
Figure 19 on page 686:
2. As that packet exits the uplink port, you can apply schedulers or enhanced transmission
selection (ETS) based on the port-level BA classifier assigned at the ingress extended
port.
3. As the packet enters the aggregation device at the cascade port, any multifield
classifiers, policers, or logical interface-level BA classifiers you define for the ingress
extended port are applied.
4. As the packet exits the aggregation device at the cascade port, any rewrite rules you
define for the egress extended port, as well as any schedulers you define for the
cascade port, are applied, unless the rewrite rule is associated with an extended port
logical interface. Also, the forwarding class determined in the previous step is carried
in the 801.2BR header to the satellite device and used to select the output queue at
the egress extended port.
5. Finally, as the packet exits an extended port, any schedulers or ETS you define for
that port are applied based on the forwarding class determined by the multifield
classifiers, policers, or logical interface-level BA classifiers defined for the ingress
extended port.
The following sections provide further information about implementing CoS on each port
type in Junos Fusion.
• Multifield classifiers
• Forwarding classes
NOTE: Configuring CoS policies on satellite devices (on both extended and
uplink ports) has the following restrictions:
While CoS features for satellite device ports are configured on the aggregation device,
the actual classification, queueing, and scheduling is performed on the satellite devices.
Information on actual traffic shaping is not passed back to the aggregation device. Logical
interface statistics for the show interfaces command are collected on the aggregate
device and do not include shaping rate data. For actual traffic statistics gathered on
satellite device interfaces, use the statistics for the physical interface and not the logical
interface.
NOTE: You cannot retrieve CoS statistics on extended ports through an SNMP
query. To see CoS statistics on an extended port, use the show interfaces
queue interface-name extended-port-interface-name and show interfaces
extended-port-interface-name extensive commands.
Junos Fusion treats the cascade ports connecting the aggregation device to the satellite
device as aggregated Ethernet ports with aggregation done automatically without
configuration. By default the Junos Fusion implementation of hierarchical CoS applies
the scheduler parameters across all cascade ports in scale mode. Because scale mode
divides the configured shaper equally across the cascade ports, traffic drops can start
before a customer reaches its committed rate for a particular flow. Starting with Junos
OS Release 18.1R1, you can set all cascade ports on an aggregation device to be in replicate
mode, thereby copying scheduler parameters to each level of the aggregated interface
member links, and automatically target all of an extended port’s traffic to a specific
cascade port. To do this, simply enable target-mode for the satellite device at the [edit
chassis satellite-management fpc fpc-number] hierarchy level. For example:
[edit]
user@host# show chassis satellite-management
fpc 100 {
target-mode;
cascade-ports [ xe-0/0/1:0 xe-1/0/0:1 xe-1/0/0:2 xe-1/0/1:1 ];
}
BNG on Junos Fusion Provider Edge supports the following CoS scheduling hierarchies:
In the above sample output, ge-100/0/0 is the extended port and xe-2/0/5 is the cascade
port.
18.4R1 Starting in Junos OS Release 18.4R1, Junos Fusion Provider Edge supports
Broadband Edge Subscriber Management, including standard CoS
functionality for Broadband Edge Subscriber Management.
CoS Hierarchical Port Scheduling with Enhanced Transmission Selection in Junos Fusion
In Junos Fusion, the satellite device can be either a QFX5100 or an EX4300 device. The
QFX5100 supports enhanced transmission selection (ETS), which is described in IEEE
802.1Qaz. Configuration support for ETS has been added to the MX Series device only
for satellite device ports that support this feature. If ETS is configured on the MX Series
aggregation device for a satellite device port that does not support ETS, the satellite
devices converts the ETS configuration to port scheduler.
NOTE: Local ports on the MX Series aggregation device do not support ETS.
• One in-band management logical interface (assigned unit 32769) for traffic that only
flows between the aggregation device and the satellite devices, such as keepalives,
for provisioning information, and for software updates.
• One for data logical interface (assigned unit 32770) for regular traffic that flows into
and out of Junos Fusion.
50 Mbps of bandwidth is reserved for the management logical interface. The remaining
bandwidth is available to the data logical interface. A shaping rate of 10 percent is also
applied to the management logical interface, which means it can use up to 10 percent
of the full interface bandwidth, if available.
The default scheduling policy is applied to the data logical interface. This reserves 95
percent of the available bandwidth and buffer space for the best effort forwarding class
(mapped to queue 0) and 5 percent for the network control forwarding class (mapped
to queue 3). You can create custom forwarding classes and schedulers by applying a
custom scheduler map to this logical interface.
18.4R1 Starting in Junos OS Release 18.4R1, Junos Fusion Provider Edge supports
Broadband Edge Subscriber Management, including standard CoS functionality
for Broadband Edge Subscriber Management.
18.1R1 Starting with Junos OS Release 18.1R1, you can set all cascade ports on an
aggregation device to be in replicate mode, thereby copying scheduler
parameters to each level of the aggregated interface member links, and
automatically target all of an extended port’s traffic to a specific cascade port.
17.2R1 Beginning with Junos OS 17.2R1, Junos Fusion Provider Edge supports per-unit
and hierarchical schedulers on extended ports.
This topic describes how to configure CoS on the different types of ports in Junos Fusion.
also factor in determining the forwarding class of the traffic. When the aggregation
devices sends the traffic out to the satellite device, the forwarding class is carried in the
801.2BR header. The satellite device then uses the forwarding class to select the output
queue at the egress extended port.
You can also apply a BA classifier at the physical interface level of an extended port. This
classifier is used to determine the output queue at the uplink port of the satellite device.
To add a behavior aggregate classifier to the physical interface level of a satellite device
extended port in Junos Fusion:
[edit class-of-service]
user@mx-agg-device#set classifiers dscp dscp-1 forwarding-class best-effort-3
loss-priority low code-points 001010
[edit class-of-service]
user@mx-agg-device#set interfaces xe-100/0/33 classifiers dscp dscp-1
[edit class-of-service]
user@mx-agg-device# show
classifiers {
dscp dscp-1 {
forwarding-class best-effort-3 {
loss-priority low code-points 001010;
}
}
}
interfaces {
xe-100/0/33 {
classifiers {
dscp dscp-1;
}
}
}
In the above configuration example, packets entering port xe-100/0/33 with a DSCP
value of 001010 will be assigned a forwarding class of best-effort-3 to select the output
queue at the uplink port as the packet travels from the satellite device to the aggregation
device.
• Overview of Assigning Service Levels to Packets Based on Multiple Packet Header Fields
[edit class-of-service]
user@mx-agg-device#set rewrite-rules ieee-802.1 rewrite1p forwarding-class
best-effort loss-priority low code-point 010
[edit class-of-service]
user@mx-agg-device#set interfaces xe-108/0/47 unit 0 rewrite-rules ieee-802.1
rewrite1p
[edit class-of-service]
user@mx-agg-device# show
rewrite-rules {
ieee-802.1 rewrite1p {
forwarding-class best-effort {
loss-priority low code-point 010;
}
}
}
interfaces {
xe-108/0/47 {
unit 0 {
rewrite-rules {
ieee-802.1 rewrite-1p;
}
}
}
}
In Junos OS, rewrite rules only look at the forwarding class and packet loss priority of the
packet (as assigned by a behavior aggregate or multifield classifier at ingress), not at
the incoming CoS value, to determine the CoS value to write to the packet header at
egress. The above configuration means that, for any packet exiting the xe-108/0/47.0
interface that has a forwarding class of best-effort and a packet loss priority of low, the
ieee-802.1 CoS value will be rewritten to 010.
Configuring CoS Hierarchical Port Scheduling with Enhanced Transmission Selection on Satellite
Device Ports
You can configure enhanced transmision selection (ETS) for both extended ports and
uplink ports on satellite devices. The configuration is done on the aggregation device. To
configure ETS for a satellite device port in Junos Fusion:
[edit class-of-service]
user@mx-agg-device#set traffic-control-profiles be-tcp-1 scheduler-map be-map-1
user@mx-agg-device#set traffic-control-profiles be-tcp-1 shaping-rate percent 80
user@mx-agg-device#set traffic-control-profiles be-tcp-1 guaranteed-rate 4g
user@mx-agg-device#set traffic-control-profiles be-tcp-3 scheduler-map be-map-3
user@mx-agg-device#set traffic-control-profiles be-tcp-3 shaping-rate percent 80
user@mx-agg-device#set traffic-control-profiles be-tcp-3 guaranteed-rate 6g
[edit class-of-service]
user@mx-agg-device#set forwarding-class-sets FC-1 class best-effort-1
user@mx-agg-device#set forwarding-class-sets FC-1 class best-effort-2
user@mx-agg-device#set forwarding-class-sets FC-3 class best-effort-3
[edit class-of-service]
user@mx-agg-device#set interfaces xe-100/0/26 forwarding-class-set FC-1
output-traffic-control-profile be-tcp-1
user@mx-agg-device#set interfaces xe-100/0/26 forwarding-class-set FC-3
output-traffic-control-profile be-tcp-3
[edit class-of-service]
user@mx-agg-device# show
traffic-control-profiles {
be-tcp-1 {
scheduler-map be-map-1;
shaping-rate percent 80;
guaranteed-rate 4g;
}
be-tcp-3 {
scheduler-map be-map-3;
shaping-rate percent 80;
guaranteed-rate 6g;
}
}
forwarding-class-sets {
FC-1 {
class best-effort-1;
class best-effort-2;
}
FC-3 {
class best-effort-3;
}
}
interfaces {
xe-100/0/26 {
forwarding-class-set {
FC-1 {
output-traffic-control-profile be-tcp-1;
}
FC-3 {
output-traffic-control-profile be-tcp-3;
}
}
}
5. Run show interfaces queue egress interface name to show the statistics of transmitted
and dropped packets for each queue on the satellite device port.
NOTE: Queued statistics for each queue are not available for satellite
device ports and will always show 0.
• CoS on Virtual Chassis Fabric (VCF) EX4300 Leaf Devices (Mixed Mode)
• One in-band management logical interface (assigned unit 32769) for traffic that only
flows between the aggregation device and the satellite devices, such as keepalives,
for provisioning information, and for software updates.
• One for data logical interface (assigned unit 32770) for regular traffic that flows into
and out of Junos Fusion.
Let’s say, for example, that interface xe-0/0/1 is configured as a cascade port. The
command show interfaces xe-0/0/1 terse produces output similar to the following:
The control logical interface (unit 32769) is automatically assigned an internal traffic
control profile (__cp_control_tc_prof) that guarantees 50 Mbps of bandwidth for the
logical interface, a 10 percent shaping rate, and the default scheduling policy. The default
scheduling policy is applied to the data logical interface. For example:
and:
You can create custom forwarding classes and schedulers for the data logical interface
by applying a customer scheduler map to that logical interface. For example, to apply a
customer scheduler policy to the data logical interface:
[edit class-of-service]
user@mx-agg-device#set schedulers AF_SCH_CORE transmit-rate percent 40
user@mx-agg-device#set schedulers AF_SCH_CORE buffer-size percent 40
[edit class-of-service]
user@mx-agg-device#set scheduler-maps CORE_SCHED_MAP forwarding-class BE
scheduler BE_SCH_CORE
user@mx-agg-device#set scheduler-maps CORE_SCHED_MAP forwarding-class EF
scheduler EF_SCH_CORE
user@mx-agg-device#set scheduler-maps CORE_SCHED_MAP forwarding-class AF
scheduler AF_SCH_CORE
user@mx-agg-device#set scheduler-maps CORE_SCHED_MAP forwarding-class NC
scheduler NC_SCH_CORE
[edit class-of-service]
user@mx-agg-device#set interfaces xe-0/0/1 unit 32770 scheduler-map
CORE_SCHED_MAP
[edit class-of-service]
user@mx-agg-device# show
interfaces {
xe-0/0/1 {
unit 32770 {
scheduler-map CORE_SCHED_MAP;
}
}
}
scheduler-maps {
CORE_SCHED_MAP {
forwarding-class BE scheduler BE_SCH_CORE;
forwarding-class EF scheduler EF_SCH_CORE;
forwarding-class AF scheduler AF_SCH_CORE;
forwarding-class NC scheduler NC_SCH_CORE;
}
}
schedulers {
BE_SCH_CORE {
transmit-rate percent 10;
buffer-size percent 10;
priority low;
}
EF_SCH_CORE {
transmit-rate percent 40;
buffer-size percent 40;
priority medium-low;
}
AF_SCH_CORE {
transmit-rate percent 40;
buffer-size percent 40;
priority medium-high;
}
NC_SCH_CORE {
transmit-rate percent 10;
buffer-size percent 10;
priority high;
}
}
and:
xe-0/0/1.32770 10000000 0 1
1
BE 10000000 0 Low Low 12
EF 10000000 0 Medium Low 50
AF 10000000 0 Medium Low 50
NC 10000000 0 High High 12
xe-0/0/1.32769 1000000 50000 62
62
BE 1000000 47500 Low Low 118
NC 1000000 2500 Low Low 6
Related • Understanding CoS on an MX Series Aggregation Device in Junos Fusion Provider Edge
Documentation on page 685