Juniper MX104 Hardware Guide
MX104 Universal Routing Platform
Published
2020-11-11
Hardware Guide
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.
MX104 Universal Routing Platform Hardware Guide
Copyright © 2020 Juniper Networks, Inc. All rights reserved.
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
MX104 Universal Routing Platform Overview | 20
Benefits of MX104 Router | 20
System Overview | 21
MX104 Chassis | 22
MX104 Chassis Overview | 22
MX104 Hardware and CLI Terminology Mapping | 24
MX104 Component Redundancy | 26
MX104 Alarm Contact Port Overview | 26
MX104 LEDs Overview | 28
Alarm LEDs on the Front Panel | 28
System LED on the Front Panel | 29
MIC LEDs | 30
Power Supply LED | 30
Routing Engine LEDs | 30
MX104 Cooling System and Airflow Overview | 31
MX104 Power System | 32
MX104 Power Overview | 33
AC Power Supplies | 33
DC Power Supplies | 34
Power Supply LEDs | 35
MX104 Power Consumption | 35
MX104 AC Power Specifications | 36
MX104 AC Power Cord Specifications | 37
MX104 DC Power Specifications | 39
MX104 DC Power Cable and Lug Specifications | 40
DC Power Cable Lug Specifications | 41
iv
DC Power Cable Specifications | 41
MX104 Host Subsystem | 42
MX104 Routing Engine Overview | 42
MX104 Routing Engine Components | 43
MX104 Routing Engine Buttons | 44
MX104 Routing Engine LEDs | 44
MX104 Boot Sequence | 45
MX104 Routing Engine and its Specifications | 45
MX104 Interface Modules | 46
MX104 Modular Interface Card (MIC) Overview | 46
Front-Pluggable MICs | 47
Built-in 10-Gigabit Ethernet MIC | 47
MIC LEDs | 48
MX104 Port and Interface Numbering | 49
Identifying Interface Numbers on the Hardware | 49
Identifying Interface Numbers in the CLI | 51
Site Planning, Preparation, and Specifications
2
Preparing the Site for the MX104 Router Overview | 57
MX104 Site Guidelines and Requirements | 58
MX104 Router Physical Specifications | 58
MX104 Router Environmental Specifications | 59
MX104 Chassis Grounding Cable and Lug Specifications | 60
Grounding Points Specifications | 61
Grounding Cable Lug Specifications | 62
Grounding Cable Specifications | 63
Rack Requirements for MX104 Routers | 64
Cabinet Requirements for MX104 Routers | 65
Clearance Requirements for Airflow and Hardware Maintenance on MX104 Routers | 67
v
MX104 Network Cable and Transceiver Planning | 68
Calculating Power Budget and Power Margin for Fiber-Optic Cables | 68
How to Calculate Power Budget for Fiber-Optic Cable | 68
How to Calculate Power Margin for Fiber-Optic Cable | 69
Fiber-Optic Cable Signal Loss, Attenuation, and Dispersion | 70
Signal Loss in Multimode and Single-Mode Fiber-Optic Cable | 70
Attenuation and Dispersion in Fiber-Optic Cable | 71
MX104 Management and Console Port Specifications and Pinouts | 72
MX104 Clocking and Timing Ports Overview | 72
MX104 Routing Engine Ethernet Port Specifications | 73
Cable Specifications | 73
Pinouts | 74
MX104 Routing Engine Auxiliary and Console Ports Specifications | 74
Cable Specifications | 75
Pinouts | 75
MX104 Routing Engine USB Port Specifications | 76
MX104 Alarm Contact Port Specifications | 77
Cable Specifications | 77
Port Pinouts | 77
MX104 BITS Port Specifications | 79
3
Cable Specifications | 79
Port Pinouts | 80
MX104 1-PPS and 10-MHz GPS Port Specifications | 81
MX104 Time of Day Port Specifications | 81
Cable Specifications | 82
Port Pinouts | 82
Initial Installation and Configuration
MX104 Installation Overview | 85
Unpacking the MX104 | 86
Unpacking an MX104 Router | 86
Parts Inventory (Packing List) for an MX104 Router | 87
vi
Installing the MX104 | 89
Connecting the MX104 to Power | 91
Connecting the MX104 Router to Earth Ground | 92
Connecting AC Power Cords to the MX104 Router | 94
Connecting DC Power Cables to the MX104 Router | 95
Connecting the MX104 to the Network | 99
Connecting the MX104 Router to Management Devices | 99
Connecting the Router to a Network for Out-of-Band Management | 99
Connecting the Router to a Management Console Device | 100
Connecting the MX104 Router to External Clocking and Timing Devices | 101
Connecting 1-PPS and 10-MHz Timing Devices to the MX104 Router | 102
Connecting a T1 or E1 External Clocking Device to the MX104 Router | 102
Connecting a Time-of-Day Device to the MX104 Router | 102
Connecting Interface Cables to MX104 Routers | 103
Initially Configuring the MX104 Router | 105
Maintaining Components
4
Maintaining MX104 Components | 111
MX104 Field-Replaceable Units (FRUs) | 111
Routine Maintenance Procedures for the MX104 Router | 112
Replacing an MX104 Console or Auxiliary Cable | 112
Removing an MX104 Console or Auxiliary Cable | 112
Installing an MX104 Console or Auxiliary Cable | 113
Replacing an MX104 Management Ethernet Cable | 113
Removing an MX104 Management Ethernet Cable | 114
Installing an MX104 Management Ethernet Cable | 114
Replacing an MX104 Fiber-Optic Cable | 114
Disconnecting an MX104 Fiber-Optic Cable | 115
Connecting an MX104 Fiber-Optic Cable | 115
vii
Replacing an MX104 Alarm Cable | 117
Disconnecting the Router from an External Alarm-Reporting Device | 117
Connecting the MX104 Router to an External Alarm-Reporting Device | 117
Maintaining MX104 Cooling System Components | 119
Maintaining the MX104 Cooling System | 119
Replacing an MX104 Fan Tray | 120
Removing an MX104 Fan Tray | 121
Installing an MX104 Fan Tray | 122
Maintaining the MX104 Air Filter | 122
Replacing an MX104 Air Filter | 123
Removing an MX104 Air Filter | 123
Installing an MX104 Air Filter | 124
Maintaining MX104 Host Subsystem Components | 125
Maintaining the MX104 Routing Engines | 126
Replacing an MX104 Routing Engine | 128
Effect of Taking the MX104 Routing Engine Offline | 128
Taking an MX104 Routing Engine Offline | 130
Removing an MX104 Routing Engine | 131
Installing an MX104 Routing Engine | 133
Maintaining MX104 Interface Modules | 135
5
6
Maintaining the MX104 MICs and Network Ports | 135
Replacing an MX104 MIC | 136
Removing an MX104 MIC | 136
Installing an MX104 MIC | 138
Replacing an MX104 Transceiver | 140
Removing an MX104 Transceiver | 140
Installing an MX104 Transceiver | 142
Maintaining Cables That Connect to MX104 Network Ports | 143
Maintaining MX104 Power System Components | 144
Replacing an MX104 AC Power Supply | 144
Removing an MX104 AC Power Supply | 145
Installing an MX104 AC Power Supply | 147
viii
Replacing an MX104 DC Power Supply | 148
Removing an MX104 DC Power Supply | 148
Installing an MX104 DC Power Supply | 151
Troubleshooting Hardware
Troubleshooting the MX104 | 156
Troubleshooting Resources for MX104 Routers | 156
Command-Line Interface | 156
Front Panel LEDs | 156
Alarm Devices and Messages | 157
Understanding Alarm Types and Severity Classes on MX104 Routers | 157
Alarm Severity Classes | 158
Verifying Active Alarms on MX104 Routers | 158
Monitoring System Log Messages on MX104 Routers | 159
Contacting Customer Support and Returning the Chassis or Components
Contacting Customer Support and Returning the Chassis or Components | 161
Contacting Customer Support | 161
How to Return a Hardware Component to Juniper Networks, Inc. | 162
Locating the MX104 Components and Serial Numbers | 163
MX104 Chassis Serial Number Label | 164
MX104 Fan Tray Serial Number Label | 164
7
MX104 MIC Serial Number Label | 165
MX104 Power Supply Serial Number Label | 166
MX104 Routing Engine Serial Number Label | 166
Guidelines for Packing Hardware Components for Shipment | 167
Packing the MX104 Router for Shipment | 167
Safety and Compliance Information
Definition of Safety Warning Levels | 171
General Safety Guidelines for Juniper Networks Devices | 174
General Safety Warnings for Juniper Networks Devices | 175
Qualified Personnel Warning | 176
Restricted-Access Area Warning | 177
ix
Preventing Electrostatic Discharge Damage to an MX104 Router | 179
Installation Safety Warnings for Juniper Networks Devices | 181
Intrabuilding Ports Warning | 181
Installation Instructions Warning | 182
Rack-Mounting Requirements and Warnings | 182
Ramp Warning | 187
General Laser Safety Guidelines for Juniper Networks Devices | 188
Laser Safety Warnings for Juniper Networks Devices | 189
Class 1 Laser Product Warning | 189
Class 1 LED Product Warning | 190
Laser Beam Warning | 191
Radiation from Open Port Apertures Warning | 192
Maintenance and Operational Safety Warnings for MX104 Routers | 193
Battery Handling Warning | 194
Jewelry Removal Warning | 195
Lightning Activity Warning | 197
Operating Temperature Warning | 198
Product Disposal Warning | 200
In Case of an Electrical Accident | 201
General Electrical Safety Warnings for Juniper Networks Devices | 201
Grounded Equipment Warning | 202
Grounding Requirements and Warning | 202
Midplane Energy Hazard Warning | 203
Multiple Power Supplies Disconnection Warning | 204
Power Disconnection Warning | 205
General Electrical Safety Guidelines and Electrical Codes for Juniper Networks
Devices | 206
MX104 AC Power Electrical Safety Guidelines and Warnings | 207
MX104 DC Power Electrical Safety Guidelines | 208
DC Power Electrical Safety Warnings for Juniper Networks Devices | 209
x
DC Power Copper Conductors Warning | 210
DC Power Disconnection Warning | 211
DC Power Wiring Terminations Warning | 214
Site Electrical Wiring Guidelines for MX104 Routers | 216
Distance Limitations for Signaling | 216
Radio Frequency Interference | 216
Electromagnetic Compatibility | 217
Agency Approvals for MX104 Routers | 218
Compliance Statements for NEBS for MX104 Routers | 219
Compliance Statements for EMC Requirements for MX104 Routers | 220
Canada | 220
European Community | 220
Israel | 221
Japan | 221
United States | 221
Compliance Statements for Environmental Requirements | 222
Compliance Statements for Acoustic Noise for MX104 Routers | 222
Statements of Volatility for Juniper Network Devices | 222
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 MX104 Universal Routing Platform. 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:
[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]
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.
Product warranties—For product warranty information, visit https://www.juniper.net/support/warranty/.
•
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:
Find CSC offerings: https://www.juniper.net/customers/support/
•
Search for known bugs: https://prsearch.juniper.net/
•
xviii
Find product documentation: https://www.juniper.net/documentation/
•
Find solutions and answer questions using our Knowledge Base: https://kb.juniper.net/
•
Download the latest versions of software and review release notes:
•
https://www.juniper.net/customers/csc/software/
Search technical bulletins for relevant hardware and software notifications:
•
https://kb.juniper.net/InfoCenter/
Join and participate in the Juniper Networks Community Forum:
•
https://www.juniper.net/company/communities/
Create a service request online: https://myjuniper.juniper.net
•
To verify service entitlement by product serial number, use our Serial Number Entitlement (SNE) Tool:
https://entitlementsearch.juniper.net/entitlementsearch/
Creating a Service Request with JTAC
You can create a service request with JTAC on the Web or by telephone.
Visit https://myjuniper.juniper.net.
•
Call 1-888-314-JTAC (1-888-314-5822 toll-free in the USA, Canada, and Mexico).
•
For international or direct-dial options in countries without toll-free numbers, see
https://support.juniper.net/support/requesting-support/.
1
CHAPTER
Overview
MX104 Universal Routing Platform Overview | 20
MX104 Chassis | 22
MX104 Cooling System and Airflow Overview | 31
MX104 Power System | 32
MX104 Host Subsystem | 42
MX104 Interface Modules | 46
MX104 Universal Routing Platform Overview
The Juniper Networks MX104 Universal Routing Platform is optimized for aggregating mobile, enterprise
WAN, business, and residential access services. The MX104 router is designed for high-density access
and pre-aggregation and is environmentally hardened to allow outside deployments in cabinets and remote
terminals. The router is a high-performance router functioning as a universal aggregation platform for
mobile broadband and metro Ethernet applications. It also acts as a universal edge platform supporting all
types of private WAN, data center interconnect, Internet edge, business edge, and residential edge services.
The router is powered by the Junos Trio chipset and runs the Junos®operating system (Junos OS) for
high-performance routing and switching. For a list of related Junos OS documentation, see
https://www.juniper.net/documentation/software/junos/.
Benefits of MX104 Router
20
System Capacity—MX104 provides 80 Gbps of throughput. MX104 has four Modular Interface Card
•
(MIC) slots and supports redundant fixed 10-Gigabit Ethernet interfaces for flexible network connectivity.
The 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.
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.
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,
g007600
and buffer occupancy.
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.
System Overview
The chassis is a rigid sheet metal structure that houses all the other router components (see
Figure 1 on page 21 and Figure 2 on page 22). The hardware system provides resiliency and redundancy,
including power supplies and Routing Engines. The chassis also has four built-in 10-Gigabit Ethernet SFP+
ports and four slots that accept Modular Interface Cards (MICs). For a list of the supported MICs, see the
MX Series Interface Module Reference.
21
The router is environmentally hardened and is 3.5 rack units (U; that is, 6.125 in., or 15.55 cm) tall. Several
routers can be stacked in a single floor-to-ceiling rack, for increased port density per unit of floor space.
The chassis is installed in standard 11.81 in. (30 cm)-deep (or larger) enclosed cabinets, 19-in. equipment
racks, or telco open-frame racks.
Figure 1: Front Panel of the MX104 Router
Figure 2: Rear View of the MX104 Router
RELATED DOCUMENTATION
MX104 Port and Interface Numbering | 49
22
MX104 Chassis
IN THIS SECTION
MX104 Chassis Overview | 22
MX104 Hardware and CLI Terminology Mapping | 24
MX104 Component Redundancy | 26
MX104 Alarm Contact Port Overview | 26
MX104 LEDs Overview | 28
MX104 Chassis Overview
The MX104 router contains a front panel with slots in which you can install field-replaceable units (FRUs).
From the front of the chassis, you can see the following components (see Figure 3 on page 24):
Alarm console port labeled ALARM, which accepts a DE-15 alarm cable.
•
Alarm LEDs that indicate major or minor alarms.
•
Built-in 10-Gigabit Ethernet MIC with four ports that accept 10-Gigabit Ethernet SFP+ transceivers.
•
ONLINE/OFFLINE button.
•
Chassis status LED labeled SYS OK
•
External building integrated timing system (BITS) port labeled EXT REF CLOCK
•
Time-of-day (TOD) port
•
External clocking ports supporting 1-PPS and 10-MHz input and output
•
ESD point
•
Fan tray, which contains five fans and an air filter
•
Four slots for installing MICs
•
NOTE: For a detailed description of the MX104 port and interface numbering see “MX104
Port and Interface Numbering” on page 49.
Two slots for installing either AC or DC power supplies, labeled PS 0 and PS 1
•
23
Two slots for installing Routing Engines, labeled RE 0 and RE 1
•
Figure 3: Front View of the MX104 Router
g007602
17 16 15 1314 12
31 54 10 1198762
24
10—1— Grounding terminalsAlarm input and output contacts
11—2— Fan trayAlarm LEDs
12—3— MIC slots 0/1 and 1/110-Gigabit Ethernet SFP+ ports
13—4— Routing Engine slot 1Online/offline button
14—5— Routing Engine slot 0System status LED
15—6— Power supply slot 1External reference clocking port
16—7— Power supply slot 0Time-of-day (ToD) port
17—8— MIC slots 0/0 and 1/01-PPS and 10-MHz GPS input and output ports
9—ESD point
MX104 Hardware and CLI Terminology Mapping
The MX104 router supports the components in Table 3 on page 24, listed in alphabetic order.
Table 3: MX104 Routers Hardware Components and CLI Terminology
Hardware
Model
NumberComponent
DescriptionCLI Name
“MX104 Universal Routing Platform Overview” on page 20MX104N/AChassis
Table 3: MX104 Routers Hardware Components and CLI Terminology (continued)
Hardware
Model
NumberComponent
filters
N/AFLTR-KIT-MX104Air filter kit
Fan TrayFANTRAY-MX104Fan tray
N/APWR-BLANK-MX104Power blank
cover
DescriptionCLI Name
“MX104 Cooling System and Airflow Overview” on page 31Cooling system, including fan trays and air
“MX104 Power Overview” on page 33Power system components
25
Power
supply
MIC
MPC
Engine
Transceiver
AC:
•
PWR-MX104-AC
DC:
•
PWR-MX104-DC
N/A
(built-in)
Module Reference.
(built-in)
RE-S-MX104Routing
Series
Interface
Module
Reference.
PEM
10GE(LAN)
SFP+
Engine
“MX104 Modular Interface Card (MIC) Overview” on page 464x
“MX104 Modular Interface Card (MIC) Overview” on page 46See MX Series Interface
“MX104 Modular Interface Card (MIC) Overview” on page 46FPCN/A
“MX104 Routing Engine Overview” on page 42Routing
“MX104 Modular Interface Card (MIC) Overview” on page 46XcvrSee MX
SEE ALSO
MX104 Port and Interface Numbering | 49
MX104 Component Redundancy
The MX104 chassis provides redundancy and resiliency. The hardware system is fully redundant, including
power supplies, Routing Engines, and cooling system.
A fully configured router is designed so that no single point of failure can cause the entire system to fail.
Only a fully configured router provides complete redundancy. All other configurations provide partial
redundancy. The following major hardware components are redundant:
Power supplies—In a redundant configuration, the router contains either two AC or DC power supplies
•
that install into the front of the chassis. The slots are labeled PS 0 and PS 1 (left to right). Each power
supply provides power to all components in the router. When two power supplies are present, they
share power almost equally within a fully populated system. If one power supply in a redundant
configuration fails or is removed, the remaining power supplies assume the entire electrical load without
interruption. Two power supplies provide the maximum configuration with full power for as long as the
router is operational.
26
Routing Engine—If two Routing Engines are installed, one functions as the primary and the other functions
•
as the backup. If the primary Routing Engine fails, the backup can take over as the primary.
Cooling system—The cooling system has redundant components, which are controlled by the host
•
subsystem. If one of the fans fails, the host subsystem increases the speed of the remaining fans to
provide sufficient cooling for the router indefinitely.
MX104 Alarm Contact Port Overview
The MX104 router has four external alarm contacts (also known as potential free contacts) for connecting
the router to external alarm devices. The port labeled ALARM uses a 15-pin D-type connector. The external
alarm contact has 15 pins that accept a single core wire from external alarm devices. A DE-15 alarm cable
is required to connect the MX104 router to external alarm devices. Use the gauge wire appropriate for
the external device that you are connecting.
Whenever a system condition triggers an alarm, the alarm relay contacts are activated, which in turn
activates the external alarm devices. The alarm setting is open or closed.
You can connect and configure two output alarms and four input alarms. Two additional output alarms
are reserved and are used to indicate major and minor system alarms. Each output and input alarm has
two contacts for connecting the router to external alarm devices. Contact 1 of each alarm can be configured
as Normally Open [NO] or Normally Closed [NC] through the CLI. Contact 2 of each alarm functions as a
reference [REF] or negative potential terminal for Contact 1 of the corresponding alarm and provides a
current path for external alarm devices. Table 4 on page 27 describes the functions of the alarm contacts.
Table 4: Alarm Relay Contact Functions
FunctionContact NameContact Name
27
Normally Open [NO]Contact 1
Normally Closed [NC]
Reference [REF]Contact 2
Current is not flowing through Contact 1 and Contact 2 [REF] when
operating normally. When the current flows, the closed alarm is
generated.
Current is flowing through Contact 1 and Contact 2 [REF] when
operating normally. When the current stops flowing, the open alarm
is generated.
Provides the current path for the external alarm-reporting device
and functions as a reference or negative potential terminal for
Contact 1.
Figure 4 on page 27 shows an example of a wiring diagram for a simple output alarm-reporting device. In
this case, the device is a light bulb that illuminates when the device encounters a condition that activates
the red alarm LED and relay contacts. The alarm relay contacts can also be used to activate other devices
such as bells or buzzers.
Figure 4: Sample Output Alarm-Reporting Device
Figure 5 on page 28 shows an example of a wiring diagram for a simple input alarm-reporting device. In
this case, the push button switch is an alarm sensor that triggers an input alarm when a door-open condition
occurs.
Figure 5: Sample Input Alarm-Reporting Device
SEE ALSO
MX104 Alarm Contact Port Specifications | 77
28
MX104 LEDs Overview
IN THIS SECTION
Alarm LEDs on the Front Panel | 28
System LED on the Front Panel | 29
MIC LEDs | 30
Power Supply LED | 30
Routing Engine LEDs | 30
Alarm LEDs on the Front Panel
Two LEDs, located to the right of the alarm contact port indicates major and minor alarms for the router
(see Figure 6 on page 29).
Figure 6: Alarm LEDs on the MX104 Router
g007638
Table 5 on page 29 describes the alarm LED in more detail.
29
Table 5: Alarm LEDs on the Front Panel
Red
steadily
Yellow
steadily
LED Control
NameStateColorShape
Critical alarmOn
Warning alarmOn
Description
Indicates a critical
condition that can cause
the router to stop
functioning. Possible
causes include component
removal, failure, or
overheating.
Indicates a serious but
nonfatal error condition,
such as a maintenance
alert or a significant
increase in component
temperature.
System LED on the Front Panel
One bicolor LED labeled SYS OK indicates the status of the router. Table 6 on page 30 describes the
system LED in more detail.
Table 6: System LED on the Front Panel
DescriptionStateColorLabel
Router has no primary Routing Engine.BlinkingGreenSYS OK
Router is functioning normally.On
steadily
30
Yellow
steadily
Red
steadily
Router has reported a minor alarm.On
Router has failed.On
MIC LEDs
Each hot-removable and hot-insertable MIC has LEDs located on the faceplate. For more information
about LEDs on the MIC faceplate, see the “LEDs” section for each MIC in the MX Series Interface Module
Reference.
For information about the built-in MIC LEDs, see “MX104 Modular Interface Card (MIC) Overview” on
page 46.
Power Supply LED
One LED labeled PS STATUS indicates the status of the power supply. For more information, see “MX104
Power Overview” on page 33.
Routing Engine LEDs
Three LEDs indicate the status of the Routing Engine. For more information, see “MX104 Routing Engine
Overview” on page 42.
SEE ALSO
Troubleshooting Resources for MX104 Routers | 156
Loading...