Juniper MX10016 Hardware Manual
MX10016 Universal Routing Platform
Published
2019-10-15
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.
MX10016 Universal Routing Platform Hardware Guide
Copyright © 2019 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 | xi
Documentation and Release Notes | xi
Using the Examples in This Manual | xi
Merging a Full Example | xii
Merging a Snippet | xiii
Documentation Conventions | xiii
Documentation Feedback | xvi
Requesting Technical Support | xvi
Self-Help Online Tools and Resources | xvii
Creating a Service Request with JTAC | xvii
iii
Overview
MX10016 System Overview | 21
MX10016 Hardware Overview | 21
Benefits of the MX10016 Router | 22
Chassis Description | 23
Routing and Control Board | 25
Line Card (MX10K-LC2101) | 26
Switch Fabric Boards | 26
Cooling System | 27
Power Supplies | 28
Software on MX10016 | 31
MX10016 Components and Configurations | 31
MX10016 Component Redundancy | 33
MX10016 Hardware and CLI Terminology Mapping | 33
MX10016 Chassis | 35
MX10016 Chassis Physical Specifications | 35
MX10016 Field-Replaceable Units | 38
MX10016 Status Panel LEDs | 39
MX10016 Optional Equipment | 42
MX10016 Cooling System | 44
2
MX10016 Cooling System and Airflow | 45
MX10016 Fan Trays | 46
MX10016 Fan Tray Controllers | 47
Airflow Direction in an MX10016 | 49
MX10016 Fan Tray LEDs and Fan Tray Controller LEDs | 50
MX10016 Fan Tray LEDs | 50
MX10016 Fan Tray Controller LEDs | 55
MX10016 Power System | 57
JNP10K-PWR-AC Power Supply | 58
JNP10K-PWR-AC2 Power Supply | 61
JNP10K-PWR-DC Power Supply | 62
JNP10K-PWR-DC2 Power Supply | 66
iv
JNP10K-PWR-AC Power Supply LEDs | 68
JNP10K-PWR-AC2 Power Supply LEDs | 69
JNP10K-PWR-DC Power Supply LEDs | 71
JNP10K-PWR-DC2 Power Supply LEDs | 73
MX10016 Routing and Control Board | 75
MX10016 Routing and Control Board Description | 75
Routing and Control Board Functions | 76
Routing and Control Board Components | 76
MX10016 Routing and Control Board LEDs | 78
MX10016 Switch Fabric Board | 80
MX10016 Switch Fabric Board Description | 81
Switch Fabric Board LEDs | 83
Line card (MX10K-LC2101) | 84
Site Planning, Preparation, and Specifications
MX10016 Site Preparation Overview | 89
Site Preparation Checklist | 89
Environmental Requirements and Specifications | 90
General Site Guidelines | 91
Site Electrical Wiring Guidelines | 92
MX10016 Rack Requirements | 93
Clearance Requirements for Airflow and Hardware Maintenance for an MX10016 | 95
MX10016 Power Planning | 96
Power Requirements for MX10016 Components | 97
Calculating Power Requirements for an MX10016 | 97
How to Calculate the Power Consumption of Your MX10016 Configuration | 98
How to Calculate the Number of Power Supplies Required for Your MX10016
Configuration | 100
JNP10K-PWR-AC Power Specifications | 102
JNP10K-PWR-AC2 Power Specifications | 103
MX10016 Power Cord Specifications | 104
JNP10K-PWR-AC Power Cable Specifications | 105
JNP10K-PWR-AC2 Power Cable Specifications | 107
v
JNP10K-PWR-AC2 Power Cable Specifications for 30-A Input | 110
JNP10K-PWR-DC Power Specifications | 112
JNP10K-PWR-DC2 Power Specifications | 112
MX10016 Grounding Cable and Lug Specifications | 113
MX10016 Transceiver and Cable Specifications | 115
Optical Transceiver and Cable Support | 115
Cable Specifications for Console and Management Connections | 116
Understanding Fiber-Optic Cable Signal Loss, Attenuation, and Dispersion | 116
Signal Loss in Multimode and Single-Mode Fiber-Optic Cables | 117
Attenuation and Dispersion in Fiber-Optic Cable | 117
Calculating the Fiber-Optic Cable Power Budget for an MX10016 | 118
Calculating the Fiber-Optic Cable Power Margin for an MX10016 | 118
MX10016 Alarm and Management Cable Specifications and Pinouts | 120
Console Port Connector Pinouts for an MX10016 Router | 120
USB Port Specifications for an MX10016 | 121
Management Port Connector Pinouts for an MX10016 | 122
Initial Installation and Configuration
3
4
MX10016 Installation Overview | 127
Unpacking an MX10016 Router and Components | 128
Unpacking an MX10016 | 128
Unpacking Line Cards, Routing and Control Boards, and Switch Fabric Boards | 131
Comparing the MX10016 Order to the Packing List | 132
Installing the Mounting Hardware | 136
Installing an MX10016 into a Four-Post Rack | 139
Mounting an MX10016 in a Four-Post Rack Using a Mechanical Lift | 139
Installing the Front Panel on an MX10016 | 142
Connecting an MX10016 to Power | 145
vi
Connecting an MX10016 to Earth Ground | 146
Connecting AC Power to an MX10016 | 148
Connecting DC Power to an MX10016 | 149
Connecting an MX10016 to External Devices | 150
Connecting an MX10016 to a Network for Out-of-Band Management | 150
Connecting an MX10016 Router to a Management Console | 151
Configuring an MX10016 Router | 152
Maintaining Components
Field-Replaceable Units in an MX10016 | 157
Removing and Installing Routing and Control Boards | 158
Removing a Routing and Control Board | 159
Installing a Routing and Control Board | 160
Removing and Installing MX10016 Cooling System Components | 162
Removing an MX10016 Fan Tray | 163
Installing an MX10016 Fan Tray | 166
Removing an MX10016 Fan Tray Controller | 168
Installing an MX10016 Fan Tray Controller | 170
Removing and Installing MX10016 Power System Components | 172
How to Remove a JNP10K-PWR-AC Power Supply | 172
How to Install a JNP10K-PWR-AC Power Supply | 175
How to Remove a JNP10K-PWR-AC2 Power Supply | 179
How to Install a JNP10K-PWR-AC2 Power Supply | 183
How to Remove a JNP10K-PWR-DC Power Supply | 187
How to Install a JNP10K-PWR-DC Power Supply | 190
How to Remove a JNP10K-PWR-DC2 Power Supply | 197
How to Install a JNP10K-PWR-DC2 Power Supply | 200
Removing and Installing MX10016 Switch Fabric Boards | 208
Handling and Storing MX10016 Line Cards, RCBs, and SFBs | 209
Handling Line Cards and Routing and Control Boards | 209
Handling Switch Fabric Boards | 211
vii
Storing Line Cards, RCBs, and SFBs | 212
Removing an MX10016 Switch Fabric Board | 212
Installing an MX10016 Switch Fabric Board | 217
Replacing an MPC | 222
Removing an MPC | 222
Installing an MPC | 225
Installing the Cable Management System | 227
Removing and Installing Transceivers and Fiber-Optic Cables | 230
Removing a Transceiver | 231
Installing a Transceiver | 233
Disconnecting a Fiber-Optic Cable from a Router | 235
Connecting a Fiber-Optic Cable to a Router | 236
Maintaining Fiber-Optic Cables in a Router | 237
Removing an MX10016 Router | 238
Powering Off an MX10016 Router | 238
Removing an MX10016 Router From a Four-Post Rack Using a Mechanical Lift | 240
Troubleshooting Hardware
5
6
7
Restoring Junos OS | 245
Creating an Emergency Boot Device | 245
Performing a Recovery Installation Using an Emergency Boot Device | 247
Alarm Messages | 249
Understanding Alarms | 249
Interface Alarm Messages | 250
Contacting Customer Support and Returning the Chassis or Components
Contacting Customer Support | 253
Returning the MX10016 Chassis or Components | 253
Returning an MX10016 Router or Component for Repair or Replacement | 254
Locating the Serial Number on an MX10016 Router or Component | 255
viii
Listing the Chassis and Component Details Using the CLI | 255
Locating the Chassis Serial Number ID Label on an MX10016 | 258
Locating the Serial Number ID Labels on the Power Supplies | 259
Locating the Serial Number ID Labels on Fan Trays and Fan Tray Controllers | 261
Locating the Serial Number ID Labels on Routing and Control Boards | 261
Locating the Serial Number ID Labels on a Line Card | 262
Locating the Serial Number ID Labels on a Switch Fabric Board (SFB) | 262
Contacting Customer Support to Obtain a Return Materials Authorization for an MX10016
Router or Component | 263
Packing an MX10016 Router or Component for Shipping | 264
Packing an MX10016 Chassis for Shipping | 265
Packing MX10016 Components for Shipping | 268
Safety and Compliance Information
General Safety Guidelines and Warnings | 273
Definitions of Safety Warning Levels | 274
Qualified Personnel Warning | 276
Warning Statement for Norway and Sweden | 277
Fire Safety Requirements | 277
Fire Suppression | 277
Fire Suppression Equipment | 277
Installation Instructions Warning | 279
MX10016 Chassis Lifting Guidelines | 279
Restricted Access Warning | 281
Ramp Warning | 283
Rack-Mounting and Cabinet-Mounting Warnings | 283
Grounded Equipment Warning | 288
Radiation from Open Port Apertures Warning | 289
Laser and LED Safety Guidelines and Warnings | 290
ix
General Laser Safety Guidelines | 290
Class 1 Laser Product Warning | 291
Class 1 LED Product Warning | 292
Laser Beam Warning | 293
Maintenance and Operational Safety Guidelines and Warnings | 293
Battery Handling Warning | 295
Jewelry Removal Warning | 296
Lightning Activity Warning | 298
Operating Temperature Warning | 299
Product Disposal Warning | 301
General Electrical Safety Guidelines and Warnings | 302
Action to Take After an Electrical Accident | 303
Prevention of Electrostatic Discharge Damage | 303
AC Power Electrical Safety Guidelines | 305
AC Power Disconnection Warning | 306
DC Power Electrical Safety Guidelines for MX10016 Router | 306
DC Power Disconnection Warning | 308
DC Power Grounding Requirements and Warning | 310
DC Power Wiring Sequence Warning | 312
DC Power Wiring Terminations Warning | 315
Multiple Power Supplies Disconnection Warning | 318
TN Power Warning | 319
Agency Approvals and Compliance Statements | 319
Agency Approvals for the Router | 319
Compliance Statements for EMC Requirements for the Router | 320
Canada | 321
European Community | 321
Israel | 321
Japan | 322
x
Korea | 322
United States | 322
Nonregulatory Environmental Standards | 322
Compliance Statements for Environmental Requirements | 323
MX10008 Compliance Statements for Acoustic Noise | 323
MX10016 Compliance Statements for Acoustic Noise | 323
About the Documentation
IN THIS SECTION
Documentation and Release Notes | xi
Using the Examples in This Manual | xi
Documentation Conventions | xiii
Documentation Feedback | xvi
Requesting Technical Support | xvi
Use this guide to install hardware and perform initial software configuration, routine maintenance, and
troubleshooting for the MX10016 Universal Routing Platform.
xi
After completing the installation and basic configuration procedures covered in this guide, refer to the
Junos OS documentation for information about further software configuration.
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;
}
}
}
}
xii
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]
xiii
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 xiv defines notice icons used in this guide.
Table 1: Notice Icons
xiv
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 xiv 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)
xv
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)
xvi
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/
•
xvii
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
MX10016 System Overview | 21
MX10016 Chassis | 35
MX10016 Cooling System | 44
MX10016 Power System | 57
MX10016 Routing and Control Board | 75
MX10016 Switch Fabric Board | 80
Line card (MX10K-LC2101) | 84
MX10016 System Overview
IN THIS SECTION
MX10016 Hardware Overview | 21
MX10016 Components and Configurations | 31
MX10016 Component Redundancy | 33
MX10016 Hardware and CLI Terminology Mapping | 33
The MX10000 line of 5G Universal Routing Platforms—including the MX10008 and MX10016 give cloud
and service providers the performance and scalability needed to outpace increased traffic demands.
MX10016 router provides 10-Gigabit Ethernet, 40-Gigabit Ethernet, and 100-Gigabit Ethernet modular
solutions that support up to 2.4 Tbps per slot. The MX10016 router provides redundancy and resiliency.
All major hardware components including the power system, the cooling system, the control board and
the switch fabrics are fully redundant.
21
MX10016 Hardware Overview
IN THIS SECTION
Benefits of the MX10016 Router | 22
Chassis Description | 23
Routing and Control Board | 25
Line Card (MX10K-LC2101) | 26
Switch Fabric Boards | 26
Cooling System | 27
Power Supplies | 28
Software on MX10016 | 31
Juniper Networks MX10016 Universal Routing Platform enables cloud and data center operators to
transition from 10-Gigabit Ethernet and 40-Gigabit Ethernet networks to 100-Gigabit Ethernet
high-performance networks. The 21 rack unit (21 U) modular chassis can provide 38.4 Tbps of throughput.
The MX10016 router has 16 slots for the line cards that can support a maximum of 1536 10-Gigabit
Ethernet ports, 384 40-Gigabit Ethernet ports, or 384 100-Gigabit Ethernet ports.
The MX10016 universal router provides 2.4 Tbps per slot fabric capacity for the service providers and
cloud operators. You can deploy the MX10016 router in an IP edge network using an MX10K-LC2101
line card (ordering model number is JNP10K-LC2101).
You can deploy MX10016 in the edge of the network for the following functions:
Layer 3 peering
•
Data center gateway
•
VPLS aggregation
•
Layer 3 aggregation
•
Video distribution
•
The MX10016 router is available in both base and redundant configurations for both AC and DC operation.
MX10016 features front-to-back airflow (also known as airflow out or AFO).
22
Benefits of the MX10016 Router
System capacity— MX10016 scales to 38.4 Tbps (76.8 Tbps half- duplex) in a single chassis, with support
•
for up to 1536 10-Gigabit Ethernet, 384 40-Gigabit Ethernet, and 384 100-Gigabit Ethernet interfaces.
Full-scale IP and MPLS routing—The MX10016 delivers a distributed peering scale of 8.6 million entries
•
in the forwarding information bases (FIBs, also known as forwarding tables) and 80 million entries in the
routing information bases (RIBs also known as routing tables).
Source Packet Routing in Networking (SPRING)—SPRING on the MX10016 provides additional flexibility
•
per packet source. SPRING provides features such as network path and node protection to support
MPLS fast reroute (FRR) mechanisms, enhanced network programmability, OAM functionality, simplified
network signaling, load balancing, and traffic engineering functions.
Always-on infrastructure base—The MX10016 is engineered with full hardware redundancy for cooling,
•
switch fabric, and host subsystems—Routing and Control Boards (RCBs)—allowing service providers to
meet stringent service-level agreements across the core.
Nondisruptive software upgrades—The Junos operating system on MX10016 supports high availability
•
(HA) features such as graceful Routing Engine switchover (GRES), nonstop active routing (NSR), and
unified in-service software upgrade (unified ISSU), providing software upgrades and changes without
disrupting network traffic.
Chassis Description
g100420
1
2
3
5
4
4
4
The MX10016 is 21 U tall. Two MX10016 chassis can fit in a standard 42 U rack when there is adequate
cooling and power. All key MX10016 components are field-replaceable units (FRUs).
Figure 1 on page 23 illustrates the components visible from the front of the chassis.
Figure 1: MX10016 Chassis Front
23
4—1— Installation holes for the front panelRouting and Control Boards
5—2— Line card slots 0-15 (numbered top to bottom)Status LED panel
3—Handle
Some chassis ship with an enhanced power bus to support the power needs of higher wattage line cards.
Chassis with the enhanced power bus have a modified Status Panel (see “MX10016 Status Panel LEDs”
on page 39).
Figure 2 on page 24 illustrates the components that are visible from the rear of the chassis.
Figure 2: MX10016 Chassis Rear
24
3—1— ESD pointAC or DC power supplies
4—2— Protective earthing terminalFan trays with redundant fans
Figure 3 on page 25 illustrates the components that are internal to the chassis.
Figure 3: MX10016 Chassis Internal Components
25
2—1— Switch Fabric Boards (SFBs)Fan tray controllers
See “MX10016 Chassis Physical Specifications” on page 35.
Routing and Control Board
The Routing and Control Board (RCB) (see Figure 4 on page 26) contains a Routing Engine and is responsible
for the system management and control in the MX10016. See “MX10016 Routing and Control Board” on
page 75. RCBs are FRUs that are installed in the front of the chassis in the slots labeled CB0 and CB1. The
base configuration has a single RCB while the fully redundant configuration has two RCBs. The RCB also
contains Precision Time Protocol ports and two Media Access Control Security (MACsec) capable ports
(see “MX10016 Components and Configurations” on page 31).
Figure 4: MX10016 Routing and Control Board
g100066
g100087
JNP10K-LC2101
1 2 3 4
Line Card (MX10K-LC2101)
The MX10016 has 16 horizontal line card slots and supports line rates for each line card. The line cards
include a Packet Forwarding Engine and Ethernet interfaces enclosed in a single assembly. The MX10016
line card architecture is based on a number of identical, independent Packet Forwarding Engine slices,
each with 400 Gbps full-duplex throughput. Line cards are FRUs that can be installed in the line card slots
labeled 0 through 15 (top to bottom) on the front of the chassis. All line cards are hot-removable and
hot-insertable. After the hot insertion, the line card comes online automatically.
26
The MX10K-LC2101 line card is available for the MX10016. The MX10K-LC2101 line card can support
24 100-Gigabit Ethernet ports with a 28-Gbps quad smallform-factor pluggable (QSFP28) transceiver, or
24 40-Gigabit Ethernet ports with a QSFP transceiver. The MX10K-LC2101 line cards also support
10-Gigabit Ethernet interfaces. For 10-Gigabit Ethernet, you must configure the port using the channelization
command. Because there is no port-groups option for the 100-Gigabit Ethernet line card, you must use
individual port channelization commands.
Figure 5 on page 26 shows the MX10K-LC2101 line card.
Figure 5: MX10K-LC2101 Line Card
3—1— Lane LEDsOFFLINE button
4—2— Port LEDsOK/FAIL LED
Switch Fabric Boards
Five Switch Fabric Boards (SFBs) provide the necessary switching functionality to an MX10016 router. A
sixth SFB is available in the redundant configuration to provide n+1 redundancy. SFBs are installed between
the line cards and the fan trays inside the chassis (see Figure 6 on page 27). Each MX10016 SFB has sixteen
connectors that match to a line card slot, eliminating the need for a backplane. When all the SFBs are
installed, the MX10016 router has a net switching capacity of 2.4 terabytes per second (bidirectional). See
“MX10016 Switch Fabric Board” on page 80.
Figure 6: MX10016 SFB
27
Cooling System
The cooling system in the MX10016 consists of two hot-removable and hot-insertable FRU fan trays (see
Figure 7 on page 28) and two fan tray controllers (see Figure 8 on page 28).
Two fan tray models and their associated fan tray controllers are available. Both models of fan tray contain
11 fans. The fan trays install vertically on the rear of the chassis and provide front to back chassis cooling.
For model differences, see “MX10016 Cooling System and Airflow” on page 45.
Figure 7: Fan Tray JNP10008-FAN
28
Figure 8: Fan Tray Controller JNP10008-FAN-CTRL
Power Supplies
Power supplies for the MX10016 router are fully redundant, load-sharing, and hot-removable and
hot-insertable FRUs. Each MX10016 router with a base configuration has five power supplies; redundant
configurations hold a maximum of ten AC or DC power supplies. Each power supply has an internal fan
for cooling. See Figure 9 on page 29 through Figure 12 on page 30.
CAUTION: Do not mix AC and DC power supplies in the same chassis.
g100585
Figure 9: JNP10K-PWR-AC Power Supply
29
Figure 10: JNP10K-PWR-AC2 Power Supply
Figure 11: JNP10K-PWR-DC Power Supply
g050571
g100595
Figure 12: JNP10K-PWR-DC2 Power Supply
30
Table 3 on page 30 provides an overview of the differences among the power supplies.
Table 3: Power Supply Overview
Power BusWattageInput TypePower Supply Model
Standard or enhanced2700 WAC onlyJNP10K-PWR AC
AC, HVAC, or HVDCJNP10K-PWR-AC2
dual feed
DC onlyJNP10K-PWR-DC2
dual feed
Enhanced5000 W, single feed; 5500 W,
Standard or enhanced2500 WDC onlyJNP10K-PWR DC
Enhanced2750 W, single feed; 5500 W,
Software on MX10016
The MX10016 router runs Junos OS, which provides Layer 3 routing services. The same Junos OS code
base that runs on the MX10016 router also runs on all Juniper Networks M Series, MX Series, and T Series
routers and SRX Series Services Gateways.
MX10016 Components and Configurations
Table 4 on page 31 lists the four hardware configurations for an MX10016 modular chassis—base (AC
version), and redundant (AC and DC versions)—and the components included in each configuration.
Table 4: MX10016 Hardware Configurations
Configuration ComponentsRouter Configuration
31
Base AC configuration
MX10016-BASE
Base DC configuration
MX10016-BASE
Chassis, including power bus
•
One Routing and Control Board
•
One control board cover panel
•
Two fan tray controllers
•
Two fan trays
•
Five 2700 W AC power supplies
•
Five power supply cover panels
•
Five Switch Fabric Boards (SFBs)
•
One SFB cover panel
•
Sixteen line card cover panels
•
Chassis, including power bus
•
One Routing and Control Board
•
One control board cover panel
•
Two fan tray controllers
•
Two fan trays
•
Five 2500 W DC power supplies
•
Five power supply cover panels
•
Five Switch Fabric Boards (SFBs)
•
One SFB cover panel
•
Sixteen line card cover panels
•
Loading...