Juniper Networks, Inc.
1133 Innovation Way
Sunnyvale, California 94089
USA
408-745-2000
www.juniper.net
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.
MX5, MX10, MX40, and MX80 Universal Routing Platforms Hardware Guide
The information in this document is current as of the date on the title page.
ii
YEAR 2000 NOTICE
Juniper Networks hardware and software products are Year 2000 compliant. Junos OS has no known time-related
limitations through the year 2038. However, the NTP application is known to have some difficulty in the year 2036.
END USER LICENSE AGREEMENT
The Juniper Networks product that is the subject of this technical documentation consists of (or is intended for use with)
Juniper Networks software. Use of such software is subject to the terms and conditions of the End User License Agreement
(“EULA”) posted at https://support.juniper.net/support/eula/. By downloading, installing or using such software, you
agree to the terms and conditions of that EULA.
Table of Contents
1
About the Documentation | xii
Documentation and Release Notes | xii
Using the Examples in This Manual | xii
Merging a Full Example | xiii
Merging a Snippet | xiv
Documentation Conventions | xiv
Documentation Feedback | xvii
Requesting Technical Support | xvii
Self-Help Online Tools and Resources | xviii
Creating a Service Request with JTAC | xviii
iii
Overview
System Overview | 20
MX5, MX10, MX40, and MX80 Router Overview | 20
Benefits of the MX5, MX10, MX40, and MX80 Router | 20
MX5, MX10, MX40, and MX80 Hardware Overview | 21
MX5, MX10, MX40, and MX80 Router Models | 23
MX5, MX10, MX40, and MX80 Hardware Components and CLI Terminology | 25
MX5, MX10, MX40, and MX80 Chassis | 26
MX5, MX10, MX40, and MX80 Chassis Description | 27
MX5, MX10, MX40, and MX80 Baseboard Description | 29
MX5, MX10, MX40, and MX80 Site Preparation Checklist | 69
MX5, MX10, MX40, and MX80 Site Guidelines and Requirements | 71
MX5, MX10, MX40, and MX80 Routers Physical Specifications | 71
MX5, MX10, MX40, and MX80 Router Environmental Specifications | 72
MX5, MX10, MX40, and MX80 Router Grounding Specifications | 73
Grounding Points Specifications | 73
Grounding Cable Lug Specifications | 74
Grounding Cable Specifications | 75
MX5, MX10, MX40, and MX80 Rack Requirements | 75
MX5, MX10, MX40, and MX80 Routers Clearance Requirements for Airflow and Hardware
Maintenance | 77
MX5, MX10, MX40, and MX80 Routers Cabinet Requirements and Specifications | 78
v
MX5, MX10, MX40, and MX80 Network Cable and Transceiver Planning | 80
Determining Transceiver Support and Specifications for M Series and T Series Routers | 80
Fiber-Optic Cable Signal Loss, Attenuation, and Dispersion | 81
Signal Loss in Multimode and Single-Mode Fiber-Optic Cable | 81
Attenuation and Dispersion in Fiber-Optic Cable | 81
Calculating Power Budget and Power Margin for Fiber-Optic Cables | 82
How to Calculate Power Budget for Fiber-Optic Cable | 83
How to Calculate Power Margin for Fiber-Optic Cable | 83
Routing Engine Interface Cable Specifications for MX5, MX10, MX40, and MX80 Routers | 85
MX5, MX10, MX40, and MX80 Management, and Console Port Specifications and
Pinouts | 85
RJ-45 Connector Pinouts for the AUX and CONSOLE Ports on MX5, MX10, MX40, and MX80
Routers | 86
RJ-45 Connector Pinouts for the ETHERNET Port on MX5, MX10, MX40, and MX80
Routers | 86
Initial Installation and Configuration
3
MX5, MX10, MX40, and MX80 Installation Summary | 89
Unpacking and Mounting the MX5, MX10, MX40, and MX80 | 90
Tools and Parts Required to Unpack MX5, MX10, MX40, and MX80 Routers | 90
Unpacking MX5, MX10, MX40, and MX80 Routers | 90
Verifying the MX5, MX10, MX40, and MX80 Routers Parts Received | 91
Installing the MX5, MX10, MX40, and MX80 Cable Management Bracket | 93
Moving the Mounting Brackets for Center-Mounting MX5, MX10, MX40, and MX80
Routers | 94
Tools Required to Install MX5, MX10, MX40, and MX80 Chassis in the Rack | 95
Installing MX5, MX10, MX40, and MX80 Chassis in the Rack | 96
Connecting the MX5, MX10, MX40, and MX80 Routers to Power | 98
vi
Tools and Parts Required for MX5, MX10, MX40, and MX80 Router Grounding and Power
Connections | 98
Grounding MX5, MX10, MX40, and MX80 Routers | 99
Connecting Power to an AC-Powered MX5, MX10, MX40, and MX80 Router | 100
Powering On an AC-Powered MX5, MX10, MX40, and MX80 Router | 101
Connecting Power to a DC-Powered MX5, MX10, MX40, and MX80 Router | 102
Powering On a DC-Powered MX5, MX10, MX40, and MX80 Router | 105
Powering Off MX5, MX10, MX40, and MX80 Routers | 107
Connecting MX5, MX10, MX40, and MX80 Routers to Management Devices | 108
Connecting the Router to a Network for Out-of-Band Management | 108
Connecting the Router to a Management Console or Auxiliary Device | 109
Initially Configuring MX5, MX10, MX40, and MX80 Routers | 110
Maintaining Components
4
Maintaining MX5, MX10, MX40, and MX80 Components | 116
Tools and Parts Required to Maintain MX5, MX10, MX40, and MX80 Routers | 116
Routine Maintenance Procedures for MX5, MX10, MX40, and MX80 Routers | 116
Maintaining the MX5, MX10, MX40, and MX80 Routing Engine | 116
Maintaining the MX5, MX10, MX40, and MX80 Air Filter | 118
Maintaining the MX5, MX10, MX40, and MX80 Air Filter | 118
Replacing an MX5, MX10, MX40, and MX80 Air Filter | 119
Removing an MX5, MX10, MX40, and MX80 Air Filter | 119
Installing an MX5, MX10, MX40, and MX80 Air Filter | 120
Maintaining the MX5, MX10, MX40, and MX80 Fan Tray | 122
Maintaining the MX5, MX10, MX40, and MX80 Fan Tray | 122
vii
Replacing an MX5, MX10, MX40, and MX80 Fan Tray | 123
Removing an MX5, MX10, MX40, and MX80 Fan Tray | 124
Installing an MX5, MX10, MX40, and MX80 Fan Tray | 125
Maintaining the MX5, MX10, MX40, and MX80 MICs and Transceivers | 126
Maintaining the MX5, MX10, MX40, and MX80 MICs | 126
Replacing an MX5, MX10, MX40, and MX80 MIC | 127
Removing an MX5, MX10, MX40, and MX80 MIC | 127
Installing an MX5, MX10, MX40, and MX80 MIC | 129
Installing an MX10, MX40, MX80, and MX104 Dual-Wide MIC | 132
Replacing an MX5, MX10, MX40, and MX80 SFP or XFP Transceiver | 135
Removing an MX5, MX10, MX40, and MX80 Transceiver | 135
Installing an MX5, MX10, MX40, and MX80 Transceiver | 136
Maintaining Cables That Connect to MX5, MX10, MX40, and MX80 MICs | 137
Maintaining the MX5, MX10, MX40, and MX80 Power Supplies and Cables | 138
5
6
Maintaining the MX5, MX10, MX40, and MX80 Power Supplies | 139
Replacing an MX5, MX10, MX40, and MX80 AC Power Supply | 140
Removing an MX5, MX10, MX40, and MX80 AC Power Supply | 140
Installing an MX5, MX10, MX40, and MX80 AC Power Supply | 142
Replacing an MX5, MX10, MX40, and MX80 AC Power Supply Cord | 143
Disconnecting an MX5, MX10, MX40, and MX80 AC Power Supply Cord | 143
Connecting an MX5, MX10, MX40, and MX80 AC Power Supply Cord | 143
Replacing an MX5, MX10, MX40, and MX80 DC Power Supply | 144
Removing an MX5, MX10, MX40, and MX80 DC Power Supply | 144
Installing an MX5, MX10, MX40, and MX80 DC Power Supply | 146
Replacing an MX5, MX10, MX40, and MX80 DC Power Supply Cable | 148
Disconnecting an MX5, MX10, MX40, and MX80 DC Power Supply Cable | 149
Connecting an MX5, MX10, MX40, and MX80 DC Power Supply Cable | 150
viii
Troubleshooting Hardware
Troubleshooting the MX5, MX10, MX40, and MX80 | 154
Troubleshooting Resources for MX5, MX10, MX40, and MX80 Routers | 154
Command-Line Interface | 154
Chassis and Interface Alarm Messages | 155
Front Panel LEDs | 155
Component LEDs | 155
Troubleshooting the MX5, MX10, MX40, and MX80 Fan Tray | 156
Troubleshooting the MX5, MX10, MX40, and MX80 MICs | 157
Troubleshooting the MX5, MX10, MX40, and MX80 Power Supplies | 158
Contacting Customer Support and Returning the Chassis or Components
Contacting Customer Support and Returning the Chassis or Components | 162
How to Return a Hardware Component to Juniper Networks, Inc. | 162
Displaying MX5, MX10, MX40, and MX80 Components and Serial Numbers | 163
MX5, MX10, MX40, and MX80 Chassis Serial Number Label | 164
MX5, MX10, MX40, and MX80 Fan Tray Serial Number Label | 165
MX5, MX10, MX40, and MX80 MIC Serial Number Label | 166
MX5, MX10, MX40, and MX80 Power Supply Serial Number Label | 167
Contact Customer Support to Obtain Return Material Authorization | 168
Guidelines for Packing Hardware Components for Shipment | 169
7
Packing MX5, MX10, MX40, and MX80 Routers for Shipment | 169
Safety and Compliance Information
Definition of Safety Warning Levels | 173
General Safety Guidelines for Juniper Networks Devices | 176
General Safety Warnings for Juniper Networks Devices | 177
Qualified Personnel Warning | 178
Restricted-Access Area Warning | 179
Preventing Electrostatic Discharge Damage to an MX5, MX10, MX40, and MX80
Router | 181
Fire Safety Requirements for Juniper Networks Devices | 183
General Fire Safety Requirements | 183
ix
Fire Suppression | 183
Fire Suppression Equipment | 183
MX5, MX10, MX40 and MX80 Chassis Lifting Guidelines | 184
Installation Safety Warnings for Juniper Networks Devices | 185
Intrabuilding Ports Warning | 186
Installation Instructions Warning | 186
Rack-Mounting Requirements and Warnings | 187
Ramp Warning | 192
General Laser Safety Guidelines for Juniper Networks Devices | 193
Laser Safety Warnings for Juniper Networks Devices | 194
Class 1 Laser Product Warning | 194
Class 1 LED Product Warning | 195
Laser Beam Warning | 196
Radiation from Open Port Apertures Warning | 197
Maintenance and Operational Safety Warnings for Juniper Networks Devices | 198
Battery Handling Warning | 199
Jewelry Removal Warning | 200
Lightning Activity Warning | 202
Operating Temperature Warning | 203
Product Disposal Warning | 205
In Case of an Electrical Accident | 206
General Electrical Safety Warnings for Juniper Networks Devices | 206
Grounded Equipment Warning | 207
Grounding Requirements and Warning | 207
Midplane Energy Hazard Warning | 208
Multiple Power Supplies Disconnection Warning | 209
Power Disconnection Warning | 210
General Electrical Safety Guidelines and Electrical Codes for Juniper Networks
Devices | 211
AC Power Electrical Safety Guidelines and Warnings for MX5, MX10, MX40, and MX80
Routers | 212
x
DC Power Electrical Safety Warnings for Juniper Networks Devices | 213
DC Power Copper Conductors Warning | 213
DC Power Disconnection Warning | 214
DC Power Wiring Terminations Warning | 217
MX5, MX10, MX40, and MX80 DC Power Electrical Safety Guidelines | 219
Site Electrical Wiring Guidelines for MX Series Routers | 220
Distance Limitations for Signaling | 220
Radio Frequency Interference | 221
Electromagnetic Compatibility | 221
Agency Approvals and Compliance Statements | 221
Agency Approvals for MX5, MX10, MX40, and MX80 Routers | 222
Compliance Statements for NEBS for MX5, MX10, MX40, and MX80 Routers | 223
Compliance Statements for EMC Requirements for MX5, MX10, MX40, and MX80 Routers | 223
Canada | 223
European Community | 223
Israel | 224
Japan | 224
United States | 224
Compliance Statements for Environmental Requirements | 224
Compliance Statements for Acoustic Noise for MX5, MX10, MX40, and MX80 Routers | 225
Statements of Volatility for Juniper Network Devices | 225
xi
About the Documentation
IN THIS SECTION
Documentation and Release Notes | xii
Using the Examples in This Manual | xii
Documentation Conventions | xiv
Documentation Feedback | xvii
Requesting Technical Support | xvii
Use this guide to install hardware and perform initial software configuration, routine maintenance, and
troubleshooting for the MX5, MX10, MX40, and MX80 Universal Routing Platforms. After completing the
installation and basic configuration procedures covered in this guide, refer to the Junos OS documentation
for information about further software configuration.
xii
Documentation and Release Notes
To obtain the most current version of all Juniper Networks®technical documentation, see the product
documentation page on the Juniper Networks website at https://www.juniper.net/documentation/.
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.
Using the Examples in This Manual
If you want to use the examples in this manual, you can use the load merge or the load merge relative
command. These commands cause the software to merge the incoming configuration into the current
candidate configuration. The example does not become active until you commit the candidate configuration.
If the example configuration contains the top level of the hierarchy (or multiple hierarchies), the example
is a full example. In this case, use the load merge command.
If the example configuration does not start at the top level of the hierarchy, the example is a snippet. In
this case, use the load merge relative command. These procedures are described in the following sections.
Merging a Full Example
To merge a full example, follow these steps:
1. From the HTML or PDF version of the manual, copy a configuration example into a text file, save the
file with a name, and copy the file to a directory on your routing platform.
For example, copy the following configuration to a file and name the file ex-script.conf. Copy the
ex-script.conf file to the /var/tmp directory on your routing platform.
system {
scripts {
commit {
file ex-script.xsl;
}
}
}
interfaces {
fxp0 {
disable;
unit 0 {
family inet {
address 10.0.0.1/24;
}
}
}
}
xiii
2. Merge the contents of the file into your routing platform configuration by issuing the load merge
configuration mode command:
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]
xiv
3. Merge the contents of the file into your routing platform configuration by issuing the load merge
relative configuration mode command:
[edit system scripts]
user@host# load merge relative /var/tmp/ex-script-snippet.conf
load complete
For more information about the load command, see CLI Explorer.
Documentation Conventions
Table 1 on page xv defines notice icons used in this guide.
Table 1: Notice Icons
xv
DescriptionMeaningIcon
Indicates important features or instructions.Informational note
Caution
Indicates a situation that might result in loss of data or hardware
damage.
Alerts you to the risk of personal injury or death.Warning
Alerts you to the risk of personal injury from a laser.Laser warning
Indicates helpful information.Tip
Alerts you to a recommended use or implementation.Best practice
Table 2 on page xv defines the text and syntax conventions used in this guide.
Table 2: Text and Syntax Conventions
ExamplesDescriptionConvention
Fixed-width text like this
Italic text like this
Represents text that you type.Bold text like this
Represents output that appears on
the terminal screen.
Introduces or emphasizes important
•
new terms.
Identifies guide names.
•
Identifies RFC and Internet draft
•
titles.
To enter configuration mode, type
the configure command:
user@host> configure
user@host> show chassis alarms
No alarms currently active
A policy term is a named structure
•
that defines match conditions and
actions.
Junos OS CLI User Guide
•
RFC 1997, BGP Communities
•
Attribute
Table 2: Text and Syntax Conventions (continued)
xvi
ExamplesDescriptionConvention
Italic text like this
Text like this
< > (angle brackets)
| (pipe symbol)
Represents variables (options for
which you substitute a value) in
commands or configuration
statements.
Represents names of configuration
statements, commands, files, and
directories; configuration hierarchy
levels; or labels on routing platform
components.
variables.
Indicates a choice between the
mutually exclusive keywords or
variables on either side of the symbol.
The set of choices is often enclosed
in parentheses for clarity.
Configure the machine’s domain
name:
[edit]
root@# set system domain-name
domain-name
To configure a stub area, include
•
the stub statement at the [edit
protocols ospf area area-id]
hierarchy level.
The console port is labeled
•
CONSOLE.
stub <default-metric metric>;Encloses optional keywords or
broadcast | multicast
(string1 | string2 | string3)
# (pound sign)
[ ] (square brackets)
Indention and braces ( { } )
; (semicolon)
GUI Conventions
Indicates a comment specified on the
same line as the configuration
statement to which it applies.
Encloses a variable for which you can
substitute one or more values.
Identifies a level in the configuration
hierarchy.
Identifies a leaf statement at a
configuration hierarchy level.
rsvp { # Required for dynamic MPLS
only
community name members [
community-ids ]
[edit]
routing-options {
static {
route default {
nexthop address;
retain;
}
}
}
Table 2: Text and Syntax Conventions (continued)
xvii
ExamplesDescriptionConvention
Bold text like this
> (bold right angle bracket)
Represents graphical user interface
(GUI) items you click or select.
Separates levels in a hierarchy of
menu selections.
In the Logical Interfaces box, select
•
All Interfaces.
To cancel the configuration, click
•
Cancel.
In the configuration editor hierarchy,
select Protocols>Ospf.
Documentation Feedback
We encourage you to provide feedback 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.
E-mail—Send your comments to techpubs-comments@juniper.net. Include the document or topic name,
•
URL or page number, and software version (if applicable).
Requesting Technical Support
Technical product support is available through the Juniper Networks Technical Assistance Center (JTAC).
If you are a customer with an active 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 policies—For a complete understanding of our JTAC procedures and policies, review the JTAC User
•
Guide located at https://www.juniper.net/us/en/local/pdf/resource-guides/7100059-en.pdf.
JTAC hours of operation—The JTAC centers have resources available 24 hours a day, 7 days a week,
•
365 days a year.
Self-Help Online Tools and Resources
For quick and easy problem resolution, Juniper Networks has designed an online self-service portal called
the Customer Support Center (CSC) that provides you with the following features:
MX5, MX10, MX40, and MX80 Hardware Components and CLI Terminology | 25
MX5, MX10, MX40, and MX80 Router Overview
20
IN THIS SECTION
Benefits of the MX5, MX10, MX40, and MX80 Router | 20
MX5, MX10, MX40, and MX80 Hardware Overview | 21
The Juniper Networks MX5, MX10, MX40, and MX80 Universal Routing Platforms are Ethernet-optimized
edge routers that provide both switching and carrier-class Ethernet routing. The MX5, MX10, MX40, and
MX80 routers run Junos operating system (Junos OS), enabling a wide range of business and residential
applications and services, including high-speed transport and virtual private network (VPN) services,
next-generation broadband multiplay services, and high-volume Internet data center internetworking.
Each router provides full duplex, high-density Ethernet interfaces and high- capacity switching throughput
and uses the Junos Trio chipset for increased scalability of L2/L3 packet forwarding, buffering, and queuing.
Benefits of the MX5, MX10, MX40, and MX80 Router
System Capacity—The MX80, MX40, MX10, and MX5 routers are software upgradeable from 20 Gbps
•
to 80 Gbps. These platforms have up to four Modular Interface Card (MIC) slots and two fixed 10-Gigabit
Ethernet interfaces for connecting to the network.
Always-on infrastructure base—MX Series routers ensure network and service availability with a broad
•
set of multilayered physical, logical, and protocol-level resiliency aspects. Junos OS Virtual Chassis
technology on MX Series routers supports chassis-level redundancy and enables you to manage two
routers as a single element. Multichassis link aggregation group (MC-LAG) implementation supports
stateful chassis, card, and port redundancy.
Application-Aware Networking—On MX Series routers you can use deep packet inspection to detect
•
applications, and by using the user-defined policies, you can determine traffic treatment for each
application. This feature enables highly customized and differentiated services at scale.
Programmable Chipset—The chipset implemented in the MX Series routers has a programmable
•
forwarding data structure that allows fast microcode changes in the hardware itself, and a programmable
lookup engine that allows inline service processing. the chip’s programmable QoS engine supports coarse
and fine-grained queuing to address the requirements of core, edge, and aggregation use cases.
Junos Continuity and Unified In-Service Software Upgrade (Unified ISSU)—With the Junos continuity
•
plug-in package, you can perform a smooth upgrade when new hardware is installed in your MX Series
router.
Unified in-service software upgrade (unified ISSU) enables software upgrades and changes without
disrupting network traffic.
Junos Telemetry Interface—Using the Junos telemetry interface data, you can stream component-level
•
data to monitor, analyze, and enhance the performance of the network. Analytics derived from this
streaming telemetry can identify current and trending congestion, resource utilization, traffic volume,
and buffer occupancy.
21
Integrated Hardware-Based Timing—You do not need to use external clocks because MX Series routers
•
support highly scalable and reliable hardware-based timing, including Synchronous Ethernet for frequency,
and the Precision Time Protocol (PTP) for frequency and phase synchronization. Synchronous Ethernet
and PTP can be combined in a hybrid mode to achieve a high level of frequency (10 ppb) and phase (<1.5
uS) accuracy.
MX5, MX10, MX40, and MX80 Hardware Overview
The routers each contain a built-in Routing Engine and one Packet Forwarding Engine. The Packet
Forwarding Engine has two “pseudo” Flexible PIC Concentrators (FPC 0 and FPC1). Because there is no
switching fabric, the single Packet Forwarding Engine takes care of both ingress and egress packet
forwarding.
The routers are compact and two rack units (U) tall. Several routers can be stacked in a single floor-to-ceiling
rack for increased port density per unit of floor space.
For scalable configuration options you can install a variety of Modular Interface Cards (MICs) in the two
front slots of the router, and the optional Multiservices MIC can be installed in the rear slot. Software
licenses allow you to upgrade from one router to another without a hardware upgrade. The ports are
restricted based on the router’s associated license as follows:
MX5 router: Allows usage of the MIC slot labeled 1/MIC 0, which comes prepopulated with the Gigabit
g017585
MX5-T
SYSOK
ONLINE
OFFLINE
RE
CONSOLE
ETHERNET
A
B
AUX
USB
EXTCLK
FAN
0/MIC0
PS1
0
1
2
3
LINK
LINK
LINK
LINK
20-portGigabitEthernetMIC
g017586
SYSOK
ONLINE
OFFLINE
RE
CONSOLE
ETHERNET
A
B
AUX
USB
EXTCLK
FAN
0/MIC0
PS1
0
1
2
3
LINK
LINK
LINK
LINK
MX10-T
20-portGigabitEthernetMIC
MICinstalledinslot1/MIC1
•
Ethernet MIC with SFP.
Figure 1: MX5 Router
MX10 router: Allows usage of the MIC slot labeled 1/MIC 0, which comes prepopulated with the Gigabit
•
Ethernet MIC with SFP and the second MIC slot labeled 1/MIC 1.
22
Figure 2: MX10 Router
MX40 router: Allows usage of the front MIC slots and ports 0 and 1 of the built-in 10-Gigabit Ethernet
•
MIC (labeled 0/MIC 0).
Figure 3: MX40 Router
g017587
SYSOK
ONLINE
OFFLINE
RE
CONSOLE
ETHERNET
A
B
AUX
USB
EXTCLK
FAN
0/MIC0
PS1
0
1
2
3
LINK
LINK
LINK
LINK
MX40-T
20-portGigabitEthernetMIC
MICinstalledinslot1/MIC1
Ports0and1onthebuilt-in10-GigabitEthernetMIC
g017596
SYSOK
ONLINE
OFFLINE
RE
CONSOLE
ETHERNET
A
B
AUX
USB
EXTCLK
FAN
0/MIC0
PS1
0
1
2
3
LINK
LINK
LINK
LINK
MX80-T
MICinstalledinslot1/MIC0
MICinstalledinslot1/MIC1
Ports0-3onthebuilt-in10-GigabitEthernetMIC
MX80 router: Allows usage of all MIC slots (front and back) and all four ports of the built-in 10-Gigabit
•
Ethernet MIC (labeled 0/MIC 0).
Figure 4: MX80 Router
23
A fixed version of the MX80 router (model number: MX80-48T) has 48 fixed 10/100/1000Base-T RJ45
ports in place of the MIC slots.
For a list of MICs supported on the MX5, MX10, MX40, and modular MX80 routers, see “MICs Supported
by MX Series Routers” on page 53 in the MX Series Interface Module Reference.
MX5, MX10, MX40, and MX80 Router Models
“MX5, MX10, MX40, and MX80 Routers Physical Specifications” on page 71
The MX5, MX10, MX40, and MX80 routers are available in different models. The tables below list the
various MX5, MX10, MX40 and MX80 router models available and provide a brief description of each
base units.
Table 3 on page 24 lists the different MX5 router models available.
Table 3: MX5 Router Models
DescriptionModel Number
DC chassisMX5-T-DC
AC chassisMX5-T-AC
Table 4 on page 24 lists the different MX10 router models available.
Table 4: MX10 Router Models
DescriptionModel Number
DC chassisMX10-T-DC
AC chassisMX10-T-AC
24
Table 5 on page 24 lists the different MX40 router models available.
Table 5: MX40 Router Models
DescriptionModel Number
DC chassisMX40-T-DC
AC chassisMX40-T-AC
Table 6 on page 24 lists the different MX80 router models available.
Table 6: MX80 Router Models
DescriptionModel Number
MX80 AC chassisMX80-AC
MX80 DC chassisMX80-DC
MX80 AC chassis with timing supportMX80-T-AC
MX80 DC chassis with timing supportMX80-T-DC
MX80 AC chassis with PTP (IEEE 1588v2) supportMX80-P-AC
MX80 DC chassis with PTP (IEEE 1588v2) supportMX80-P-DC
Table 6: MX80 Router Models (continued)
DescriptionModel Number
MX80 fixed 48 GE port AC chassisMX80-48T-AC
MX80 fixed 48 GE port DC chassisMX80-48T-DC
MX80 fixed 48 GE port AC chassis with timing supportMX80-T-48T-AC
MX80 fixed 48 GE port DC chassis with timing supportMX80-T-48T-DC
MX5, MX10, MX40, and MX80 Hardware Components and CLI Terminology
The MX5, MX10, MX40, and MX80 routers support the components in Table 7 on page 25, listed in
alphabetic order.
25
Table 7: MX5, MX10, MX40, and MX80 Routers Hardware Components and CLI Terminology
Hardware Model
NumberComponent
N/AChassis
Cooling system, including fan trays and air filters
MX5
•
MX10
•
MX40
•
MX80
•
MX80–P
•
MX80–T
•
MX80–48T
•
N/AFLTR-KIT-MX80Air filter kit
Fan TrayFANTRAY-MX80Fan tray
DescriptionCLI Name
“MX5, MX10, MX40, and MX80
Chassis Description” on page 27
MX5, MX10, MX40, and MX80
Cooling System Description
Table 7: MX5, MX10, MX40, and MX80 Routers Hardware Components and CLI Terminology (continued)
Hardware Model
NumberComponent
DescriptionCLI Name
26
Power system components
Power supply
Transceiver
AC: PWR-MX80-AC
•
DC: PWR-MX80-DC
•
See MX Series Interface Module Reference.MIC
Module Reference.
N/APWR-BLANK-MX80Power blank cover
PEM
FPCN/A (built-in)MPC
Routing EngineN/A (built-in)Routing Engine
XcvrSee MX Series Interface
“MX5, MX10, MX40, and MX80
Power System Description” on
page 36
“MX5, MX10, MX40, and MX80
Modular Interface Card
Description” on page 50
“MX5, MX10, MX40, and MX80
Modular Interface Card
Description” on page 50
“MX5, MX10, MX40, and MX80
Routing Engine Description” on
page 49
MX5, MX10, MX40, and MX80 Chassis
IN THIS SECTION
MX5, MX10, MX40, and MX80 Chassis Description | 27
MX5, MX10, MX40, and MX80 Baseboard Description | 29
MX5, MX10, MX40, and MX80 Front Panel Description | 31
Alarm LEDs on the MX5, MX10, MX40, and MX80 Front Panel | 33
Component LEDs on the MX5, MX10, MX40, and MX80 Front Panel | 34
MX5, MX10, MX40, and MX80 Chassis Description
g017582
FrontpanelFan
MICslots
ACpowersupplies
ESDpoint
MX5-T
SYSOK
ONLINE
OFFLINE
RE
CONSOLE
ETHERNET
A
B
AUX
USB
EXTCLK
FAN
0/MIC0
PS1
0
1
2
3
LINK
LINK
LINK
LINK
g017583
FrontpanelFan
MICslots
ACpowersupplies
ESDpoint
SYSOK
ONLINE
OFFLINE
RE
CONSOLE
ETHERNET
A
B
AUX
USB
EXTCLK
FAN
0/MIC0
PS1
0
1
2
3
LINK
LINK
LINK
LINK
MX10-T
The router chassis is a rigid sheet metal structure that houses all the other router components (see
Figure 5 on page 27, Figure 6 on page 27, Figure 7 on page 28, Figure 8 on page 28, Figure 9 on page 28,
and Figure 10 on page 29). The chassis measures 3.5 in. (8.9 cm) high, 17.5 in. (44.5 cm) wide, and 23.46 in.
(59.6 cm) deep. The chassis installs in standard 600-mm deep (or larger) enclosed cabinets, 19-in. equipment
racks, or telco open-frame racks.
Figure 5: Front View of the MX5 Router
27
Figure 6: Front View of the MX10 Router
Figure 7: Front View of the MX40 Router
g017584
FrontpanelFan
MICslots
ACpowersupplies
ESDpoint
SYSOK
ONLINE
OFFLINE
RE
CONSOLE
ETHERNET
A
B
AUX
USB
EXTCLK
FAN
0/MIC0
PS1
0
1
2
3
LINK
LINK
LINK
LINK
MX40-T
g005001
FrontpanelFantray(andairfilter)ACpowersupplies
Networkports
g005000
FrontpanelFan
MICslots
ACpowersupplies
ESDpoint
Figure 8: Front View of the MX80 Router (Fixed Chassis)
28
Figure 9: Front View of the MX80 Router (Modular Chassis)
Figure 10: Rear View of the MX5, MX10, MX40, and MX80 Routers
g005002
CLOCK
SYNC
Clockport
MICslot
Syncport
ESDpoint
Protectiveearthingterminal
NOTE: The port labeled CLOCK provides 10 Mhz output. The port labeled SYNC provides 1
PPS output.
29
SEE ALSO
MX5, MX10, MX40, and MX80 Router Overview | 20
MX5, MX10, MX40, and MX80 Router Models | 23
MX5, MX10, MX40, and MX80 Routers Physical Specifications | 71
MX5, MX10, MX40, and MX80 Baseboard Description
The baseboard is located in the center of the chassis and forms the rear of the MIC card cage. The baseboard
is not replaceable. The MICs and power supplies install into the baseboard from the front of the chassis.
Data packets are transferred across the baseboard from the MIC to the Packet Forwarding Engine, and
from the Packet Forwarding Engine across the baseboard to the destination MIC.
The baseboard provides the following functions:
Powers on and powers off MICs
•
Controls clocking, system resets, and booting
•
Monitors and controls system functions, including fan speed, board power status, PDM status and
•
control, and the front panel
Provides interconnections to all the MICs within the chassis
•
Baseboard Components
The baseboard consists of the following components:
Junos Trio chipset—Manages packet data memory, queuing systems, and performs packet lookup and
•
encapsulation.
MIC connectors for both built-in and replaceable MICs including a WAN interface for the built-in
•
10-Gigabit Ethernet MIC.
Intake and exhaust temperature sensors.
•
Circuits for chassis management and control.
•
Power circuits for the system components and Ethernet interfaces.
•
Routing Engine processor, which includes a 1.33-GHz CPU, and 2 GB of SDRAM.
•
2 4-GB NAND flash storage devices.
•
Packet Forwarding Engine processor, which includes a 1-GHz CPU, a system controller, and 1 GB of
•
SDRAM. Connects to the Routing Engine through a Gigabit Ethernet link.
30
Clock logic.
•
SEE ALSO
MX5, MX10, MX40, and MX80 Router Overview | 20
MX5, MX10, MX40, and MX80 Chassis Description | 27
MX5, MX10, MX40, and MX80 Routing Engine Description | 49
MX5, MX10, MX40, and MX80 Cable Management Bracket Description
The cable management bracket (see Figure 11 on page 31) consists of plastic dividers and installs on the
left side of the chassis. The cable management bracket allows you to route the cables outside the router
and away from the MICs.
Loading...
+ 197 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.