Juniper MX480 Hardware Guide
MX480 Universal Routing Platform
Published
2020-11-21
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.
MX480 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 | xvii
Documentation and Release Notes | xvii
Using the Examples in This Manual | xvii
Merging a Full Example | xviii
Merging a Snippet | xix
Documentation Conventions | xix
Documentation Feedback | xxii
Requesting Technical Support | xxii
Self-Help Online Tools and Resources | xxiii
Creating a Service Request with JTAC | xxiii
iii
Overview
MX480 Router Description | 25
Benefits of the MX480 Router | 25
MX480 Hardware Overview | 26
MX480 Chassis | 28
MX480 Chassis Description | 28
MX480 Component Redundancy | 30
MX480 Router Hardware and CLI Terminology Mapping | 31
MX480 Craft Interface Description | 34
Alarm Relay Contacts on the MX480 Craft Interface | 35
Alarm LEDs and Alarm Cutoff/Lamp Test Button on the MX480 Craft Interface | 35
MX480 Component LEDs on the Craft Interface | 36
Host Subsystem LEDs on the MX480 Craft Interface | 36
Power Supply LEDs on the MX480 Craft Interface | 37
DPC and MPC LEDs on the MX480 Craft Interface | 37
FPC LEDs on the MX480 Craft Interface | 38
SCB LEDs on the MX480 Craft Interface | 38
Fan LEDs on the MX480 Craft Interface | 39
MX480 Cable Management Brackets | 39
MX480 Cooling System | 41
MX480 Cooling System Description | 41
MX480 Fan LED | 43
MX480 Power System Description | 43
MX480 AC Power System | 44
MX480 AC Power Supply Description | 44
AC Power Supply Configurations | 46
MX480 AC Power Supply LEDs | 46
AC Electrical Specifications for the MX480 Router | 47
AC Power Circuit Breaker Requirements for the MX480 Router | 49
AC Power Cord Specifications for the MX480 Router | 49
iv
Outstanding Issues with the MX480 Router | 52
Errata with the MX480 Router Documentation | 53
MX480 DC Power System | 54
MX480 DC Power Supply Description | 54
DC Power Supply Configurations | 55
MX480 DC Power Supply LEDs | 56
DC Power Supply Electrical Specifications for the MX480 Router | 56
DC Power Circuit Breaker Requirements for the MX480 Router | 58
DC Power Source Cabling for the MX480 Router | 58
DC Power Cable Specifications for the MX480 Router | 60
MX480 Host Subsystem | 61
MX480 Host Subsystem Description | 61
MX480 Host Subsystem LEDs | 62
MX480 Midplane Description | 62
MX480 Routing Engine Description | 63
Routing Engine Components | 65
Routing Engine Interface Ports | 65
Routing Engine Boot Sequence | 66
MX480 Routing Engine LEDs | 66
Routing Engine LEDs (RE-S-X6-64G) | 68
RE-S-1800 Routing Engine Description | 69
RE-S-1800 Routing Engine Components | 69
RE-S-1800 Routing Engine LEDs | 70
RE-S-1800 Routing Engine Boot Sequence | 71
RE-S-1800 Routing Engine LEDs | 71
RE-S-X6-64G Routing Engine Description | 72
RE-S-X6-64G Routing Engine Components | 73
RE-S-X6-64G Routing Engine Boot Sequence | 74
RE-S-X6-64G Routing Engine LEDs | 74
RE-S-X6-128G Routing Engine Description | 76
RE-S-X6-128G Routing Engine Components | 76
RE-S-X6-128G Routing Engine LEDs | 77
RE-S-X6-128G Routing Engine Boot Sequence | 79
Routing Engine Specifications | 79
v
Supported Routing Engines by Router | 86
M7i Routing Engines | 87
M10i Routing Engines | 87
M40e Routing Engines | 88
M120 Routing Engines | 88
M320 Routing Engines | 89
MX5, MX10, MX40, and MX80 Routing Engine | 90
MX104 Routing Engines | 90
MX204 Routing Engine | 91
MX240 Routing Engines | 91
MX480 Routing Engines | 92
MX960 Routing Engines | 94
MX2008 Routing Engines | 95
MX2010 Routing Engines | 95
MX2020 Supported Routing Engines | 96
MX10003 Routing Engines | 97
MX10008 Routing Engines | 97
PTX1000 Routing Engines | 98
PTX3000 Routing Engines | 98
PTX5000 Routing Engines | 99
PTX10008 and PTX10016 Routing Engines | 100
T320 Routing Engines | 100
T640 Routing Engines | 101
T1600 Routing Engines | 102
T4000 Routing Engines | 103
TX Matrix Routing Engines | 104
TX Matrix Plus Routing Engines | 105
TX Matrix Plus (with 3D SIBs) Routing Engines | 105
MX480 Interface Modules—DPCs | 106
MX480 Dense Port Concentrator (DPC) Description | 106
DPC Components | 108
MX480 DPC Port and Interface Numbering | 109
MX480 Dense Port Concentrator (DPC) LEDs | 112
vi
DPCs Supported on MX240, MX480, and MX960 Routers | 113
MX480 Interface Modules—FPCs and PICs | 116
MX480 Flexible PIC Concentrator (FPC) Description | 116
FPC Components | 118
MX480 Flexible PIC Concentrator (FPC) LEDs | 118
FPCs Supported by MX240, MX480, and MX960 Routers | 119
MX480 PIC Description | 119
MX480 PIC Port and Interface Numbering | 120
MX480 PIC LEDs | 122
PICs Supported by MX240, MX480, and MX960 Routers | 122
MX480 Interface Modules—MPCs and MICs | 124
MIC/MPC Compatibility | 124
MX480 Modular Interface Card (MIC) Description | 133
MX480 MIC Port and Interface Numbering | 134
MX480 Modular Interface Card (MIC) LEDs | 137
MICs Supported by MX Series Routers | 138
MX480 Modular Port Concentrator (MPC) Description | 148
MPC Components | 150
MX480 Modular Port Concentrator (MPC) LEDs | 150
MPCs Supported by MX Series Routers | 151
MX480 Application Services Modular Line Card Description | 155
2
MX480 AS MLC Function | 156
AS MLC Components | 157
MX480 SCB, Power Supply, and Cooling System Requirements for AS MLC | 157
MX480 Application Services Modular Storage Card Description | 158
MX480 Application Services Modular Processing Card Description | 159
MX480 AS MSC LEDs | 160
MX480 AS MXC LEDs | 161
Services Processing Card—MX-SPC3 Services Card | 162
MX-SPC3 Services Card Overview and Support on MX240, MX480, and MX960 Routers | 162
MX-SPC3 Services Card | 163
MX-Series Switch Control Board (SCB) Description | 168
CLI Identification | 170
vii
Power Requirements for Switch Control Boards | 172
Site Planning, Preparation, and Specifications
MX480 Site Preparation Checklist | 174
MX480 Site Guidelines and Requirements | 175
MX480 Router Physical Specifications | 175
MX480 Router Environmental Specifications | 177
MX480 Chassis Grounding Specifications | 179
MX480 Chassis Grounding Points Specifications | 179
MX480 Router Grounding Cable Lug Specifications | 180
MX480 Router Grounding Cable Specifications | 181
MX480 Router Rack Requirements | 182
Rack Size and Strength | 182
Spacing of Mounting Bracket Holes | 183
Connection to Building Structure | 183
MX480 Router Clearance Requirements for Airflow and Hardware Maintenance | 184
MX480 Router Cabinet Size and Clearance Requirements | 185
MX480 Router Cabinet Airflow Requirements | 185
3
MX480 Power Planning | 186
Power Requirements for an MX480 Router | 186
Calculating Power Requirements for MX480 Routers | 196
MX480 Network Cable and Transceiver Planning | 202
Calculating Power Budget and Power Margin for Fiber-Optic Cables | 202
How to Calculate Power Budget for Fiber-Optic Cable | 202
How to Calculate Power Margin for Fiber-Optic Cable | 203
Understanding Fiber-Optic Cable Signal Loss, Attenuation, and Dispersion | 204
Signal Loss in Multimode and Single-Mode Fiber-Optic Cables | 204
Attenuation and Dispersion in Fiber-Optic Cable | 205
Routing Engine Interface Cable and Wire Specifications for MX Series Routers | 206
MX480 Management, and Console Port Specifications and Pinouts | 207
viii
RJ-45 Connector Pinouts for an MX Series Routing Engine ETHERNET Port | 207
RJ-45 Connector Pinouts for MX Series Routing Engine AUX and CONSOLE Ports | 208
Initial Installation and Configuration
Installing an MX480 Router Overview | 210
Unpacking the MX480 | 211
Tools and Parts Required to Unpack the MX480 Router | 211
Unpacking the MX480 Router | 211
Verifying the MX480 Router Parts Received | 213
Installing the MX480 | 215
Installing the MX480 Router Mounting Hardware for a Rack or Cabinet | 215
Moving the Mounting Brackets for Center-Mounting the MX480 Router | 218
Tools Required to Install the MX480 Router with a Mechanical Lift | 219
Removing Components from the MX480 Router Before Installing It with a Lift | 219
Removing the Power Supplies Before Installing the MX480 Router with a Lift | 220
Removing the Fan Tray Before Installing the MX480 Router with a Lift | 220
Removing the SCBs Before Installing the MX480 Router with a Lift | 221
Removing the DPCs Before Installing the MX480 Router with a Lift | 222
Removing the FPCs Before Installing the MX480 Router with a Lift | 223
Installing the MX480 Router Using a Mechanical Lift | 224
Reinstalling Components in the MX480 Router After Installing It with a Lift | 227
Reinstalling the Power Supplies After Installing the MX480 Router with a Lift | 227
Reinstalling the Fan Tray After Installing the MX480 Router with a Lift | 228
Reinstalling the SCBs After Installing the MX480 Router with a Lift | 229
Reinstalling the DPCs After Installing the MX480 Router with a Lift | 230
Reinstalling the FPCs After Installing the MX480 Router with a Lift | 231
Tools Required to Install the MX480 Router Without a Mechanical Lift | 232
Removing Components from the MX480 Router Before Installing It Without a Lift | 232
Removing the Power Supplies Before Installing the MX480 Router Without a Lift | 233
Removing the Fan Tray Before Installing the MX480 Router Without a Lift | 234
Removing the SCBs Before Installing the MX480 Router Without a Lift | 235
Removing the DPCs Before Installing the MX480 Router Without a Lift | 236
Removing the FPCs Before Installing the MX480 Router Without a Lift | 237
ix
Installing the MX480 Chassis in the Rack Manually | 239
Reinstalling Components in the MX480 Router After Installing It Without a Lift | 241
Reinstalling the Power Supplies After Installing the MX480 Router Without a Lift | 241
Reinstalling the Fan Tray After Installing the MX480 Router Without a Lift | 242
Reinstalling the SCBs After Installing the MX480 Router Without a Lift | 243
Reinstalling the DPCs After Installing the MX480 Router Without a Lift | 244
Reinstalling the FPCs After Installing the MX480 Router Without a Lift | 245
Installing the MX480 Router Cable Management Bracket | 246
Connecting the MX480 to Power | 247
Tools and Parts Required for MX480 Router Grounding and Power Connections | 248
Grounding the MX480 Router | 248
Connecting Power to an AC-Powered MX480 Router with Normal-Capacity Power
Supplies | 249
Powering On an AC-Powered MX480 Router | 251
Connecting Power to a DC-Powered MX480 Router with Normal Capacity Power Supplies | 252
Powering On a DC-Powered MX480 Router with Normal Capacity Power Supplies | 254
Powering Off the MX480 Router | 256
Connecting an MX480 AC Power Supply Cord | 257
Connecting an MX480 DC Power Supply Cable | 258
Connecting the MX480 to the Network | 260
4
Tools and Parts Required for MX480 Router Connections | 260
Connecting the MX480 Router to a Network for Out-of-Band Management | 260
Connecting the MX480 Router to a Management Console or Auxiliary Device | 261
Connecting the MX480 Router to an External Alarm-Reporting Device | 262
Connecting DPC, MPC, MIC, or PIC Cables to the MX480 Router | 263
Connecting the Alarm Relay Wires to the MX480 Craft Interface | 265
Initially Configuring the MX480 Router | 266
Maintaining Components
Maintaining MX480 Components | 272
Routine Maintenance Procedures for the MX480 Router | 272
MX480 Field-Replaceable Units (FRUs) | 273
x
Tools and Parts Required to Replace MX480 Hardware Components | 274
Replacing the MX480 Craft Interface | 275
Disconnecting the Alarm Relay Wires from the MX480 Craft Interface | 276
Removing the MX480 Craft Interface | 276
Installing the MX480 Craft Interface | 277
Connecting the Alarm Relay Wires to the MX480 Craft Interface | 278
Replacing the MX480 Cable Management Brackets | 279
Replacing the Management Ethernet Cable on an MX Series Router | 280
Replacing the Console or Auxiliary Cable on an MX480 Router | 281
Maintaining MX480 Cooling System Components | 281
Maintaining the MX480 Air Filter | 282
Replacing the MX480 Air Filter | 282
Removing the MX480 Air Filter | 282
Installing the MX480 Air Filter | 284
Maintaining the MX480 Fan Tray | 284
Replacing the MX480 Fan Tray | 287
Removing the MX480 Fan Tray | 287
Installing the MX480 Fan Tray | 288
Maintaining MX480 Host Subsystem Components | 289
Maintaining the MX480 Host Subsystem | 290
Replacing an MX480 Routing Engine | 293
Removing an MX480 Routing Engine | 293
Installing an MX480 Routing Engine | 295
Replacing an SSD Drive on an RE-S-1800 | 297
Replacing an SSD Drive on an RE-S-X6-64G | 299
Replacing Connections to MX480 Routing Engine Interface Ports | 305
Replacing the Management Ethernet Cable on an MX Series Router | 305
Replacing the Console or Auxiliary Cable on an MX480 Router | 306
Upgrading to the RE-S-X6-64G Routing Engine in a Redundant Host Subsystem | 307
Removing the Routing Engine | 307
Installing the Routing Engine RE-S-X6-64G | 310
Verifying and Configuring the Upgraded Routing Engine as the Primary | 312
xi
Verifying and Configuring the Upgraded Routing Engine as the Backup | 313
Upgrading to the RE-S-X6-64G Routing Engine in a Nonredundant Host Subsystem | 313
Removing the Routing Engine | 314
Installing the Routing Engine RE-S-X6-64G | 314
Maintaining MX480 Interface Modules | 316
Maintaining MX480 DPCs | 316
Holding an MX480 DPC | 319
Storing an MX480 DPC | 321
Replacing an MX480 DPC | 322
Removing an MX480 DPC | 322
Installing an MX480 DPC | 324
Replacing a Cable on an MX480 DPC, MPC, MIC, or PIC | 327
Removing a Cable on an MX480 DPC, MPC, MIC, or PIC | 327
Installing a Cable on an MX480 DPC, MPC, MIC, or PIC | 329
Maintaining MX480 FPCs | 331
Holding an MX480 FPC | 333
Storing an MX480 FPC | 337
Replacing an MX480 FPC | 338
Removing an MX480 FPC | 339
Installing an MX480 FPC | 341
Maintaining MX480 MICs | 344
Replacing an MX480 MIC | 345
Removing an MX480 MIC | 346
Installing an MX480 MIC | 348
Installing an MX480 Dual-Wide MIC | 350
Maintaining MX480 MPCs | 353
Replacing an MX480 MPC | 356
Removing an MX480 MPC | 356
Installing an MX480 MPC | 359
Maintaining MX480 PICs | 361
Replacing an MX480 PIC | 362
xii
Removing an MX480 PIC | 363
Installing an MX480 PIC | 365
Replacing an MX480 AS MLC | 367
Removing an MX480 AS MLC | 367
Installing an MX480 AS MLC | 370
Replacing an MX480 AS MSC | 371
Removing an MX480 AS MSC | 372
Installing an MX480 AS MSC | 373
Replacing an MX480 AS MXC | 375
Removing an MX480 AS MXC | 375
Installing an MX480 AS MXC | 376
Maintaining Cables That Connect to MX480 DPCs, MPCs, MICs, or PICs | 377
Maintaining MX-SPC3 Services Card | 379
Maintaining MX-SPC3 Services Card | 379
Replacing an MX-SPC3 | 380
Removing an MX-SPC3 | 380
Installing an MX-SPC3 | 382
Maintaining MX480 Power System Components | 384
Maintaining the MX480 Power Supplies | 384
Replacing an MX480 AC Power Supply | 385
Removing an MX480 AC Power Supply | 385
Installing an MX480 AC Power Supply | 387
Replacing an MX480 AC Power Supply Cord | 388
Disconnecting an MX480 AC Power Supply Cord | 388
Connecting an MX480 AC Power Supply Cord | 389
Replacing an MX480 DC Power Supply | 389
Removing an MX480 DC Power Supply | 389
Installing an MX480 DC Power Supply | 391
Replacing an MX480 DC Power Supply Cable | 395
Disconnecting an MX480 DC Power Supply Cable | 395
Connecting an MX480 DC Power Supply Cable | 396
xiii
Maintaining MX480 SFP and XFP Transceivers | 398
Replacing an SFP or XFP Transceiver on an MX480 DPC, MPC, MIC, or PIC | 398
Removing an SFP or XFP Transceiver from an MX480 DPC, MPC, MIC, or PIC | 398
Installing an SFP or XFP Transceiver into an MX480 DPC, MPC, MIC, or PIC | 400
Maintaining MX480 Switch Control Boards | 401
Replacing an MX480 Switch Control Board | 401
Removing an MX480 SCB-MX | 401
Installing an MX480 Switch Control Board | 402
Upgrading an MX480 to Use the SCBE-MX | 404
Prepare for the Upgrade | 405
Upgrade the SCB-MX in the Backup Routing Engine | 407
Upgrade the MX480 SCB-MX in the Primary Routing Engine | 409
Complete the SCBE-MX Upgrade | 412
Upgrading an MX480 to Use the SCBE2-MX | 415
Prepare the MX480 Router for the SCBE2-MX Upgrade | 416
Power Off the MX480 Router | 416
Remove the MX480 Routing Engine | 417
Install the MX480 Routing Engine into the SCBE2-MX | 417
Power On the MX480 Router | 418
Complete the SCBE2-MX Upgrade | 419
5
6
Upgrading an MX240, MX480, or MX960 Router to Use the SCBE3-MX | 420
Upgrade the Routing Engine | 421
Install the Routing Engine into the SCBE3-MX | 421
Install the SCBE3-MX into the Router Chassis | 422
Complete the SCBE3-MX Upgrade | 422
Troubleshooting Hardware
Troubleshooting the MX480 | 425
Troubleshooting Resources for MX480 Routers | 425
Command-Line Interface | 425
Chassis and Interface Alarm Messages | 426
Alarm Relay Contacts | 426
Craft Interface LEDs | 426
xiv
Component LEDs | 427
Juniper Networks Technical Assistance Center | 427
Troubleshooting the MX480 Cooling System | 428
Troubleshooting the MX480 DPCs | 428
Troubleshooting the MX480 FPCs | 430
Troubleshooting the MX480 MICs | 433
Troubleshooting the MX480 MPCs | 434
Troubleshooting the MX480 PICs | 436
Troubleshooting the MX480 Power System | 437
Contacting Customer Support and Returning the Chassis or Components
Contacting Customer Support and Returning the Chassis or Components | 442
Displaying MX480 Router Components and Serial Numbers | 442
MX480 Chassis Serial Number Label | 445
MX480 SCB Serial Number Label | 445
MX480 DPC Serial Number Label | 446
MX480 FPC Serial Number Label | 447
MX480 MIC Serial Number Label | 448
MX480 MPC Serial Number Label | 449
MX480 PIC Serial Number Label | 450
MX480 Power Supply Serial Number Label | 451
MX480 Routing Engine Serial Number Label | 453
7
Contact Customer Support to Obtain Return Material Authorization | 454
Guidelines for Packing Hardware Components for Shipment | 455
How to Return a Hardware Component to Juniper Networks, Inc. | 455
Packing the MX480 Router for Shipment | 456
Safety and Compliance Information
General Safety Guidelines and Warnings | 460
Definitions of Safety Warning Levels | 461
Qualified Personnel Warning | 464
Fire Safety Requirements | 465
Fire Suppression | 465
Fire Suppression Equipment | 465
xv
Warning Statement for Norway and Sweden | 466
Preventing Electrostatic Discharge Damage to an MX480 Router | 466
Installation Instructions Warning | 468
MX480 Chassis Lifting Guidelines | 468
Ramp Warning | 470
Rack-Mounting and Cabinet-Mounting Warnings | 470
Grounded Equipment Warning | 476
Laser and LED Safety Guidelines and Warnings | 477
General Laser Safety Guidelines | 477
Class 1 Laser Product Warning | 478
Class 1 LED Product Warning | 479
Laser Beam Warning | 480
Radiation from Open Port Apertures Warning | 481
Maintenance and Operational Safety Guidelines and Warnings | 482
Battery Handling Warning | 483
Jewelry Removal Warning | 484
Lightning Activity Warning | 486
Operating Temperature Warning | 487
Product Disposal Warning | 489
General Electrical Safety Guidelines and Warnings | 490
Prevention of Electrostatic Discharge Damage | 491
AC Power Electrical Safety Guidelines | 492
AC Power Disconnection Warning | 494
DC Power Copper Conductors Warning | 495
DC Power Disconnection Warning | 496
DC Power Grounding Requirements and Warning | 498
DC Power Wiring Sequence Warning | 500
xvi
DC Power Wiring Terminations Warning | 503
Midplane Energy Hazard Warning | 505
Multiple Power Supplies Disconnection Warning | 506
Action to Take After an Electrical Accident | 507
MX480 Agency Approvals and Compliance Statements | 507
Agency Approvals for MX480 Routers | 507
Compliance Statements for EMC Requirements | 508
Canada | 509
European Community | 509
Israel | 509
Japan | 509
United States | 510
Compliance Statements for Environmental Requirements | 510
Compliance Statements for NEBS | 510
Compliance Statements for Acoustic Noise for the MX480 Router | 510
Statements of Volatility for Juniper Network Devices | 511
About the Documentation
IN THIS SECTION
Documentation and Release Notes | xvii
Using the Examples in This Manual | xvii
Documentation Conventions | xix
Documentation Feedback | xxii
Requesting Technical Support | xxii
Use this guide to install hardware and perform initial software configuration, routine maintenance, and
troubleshooting for the MX480 5G 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.
xvii
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;
}
}
}
}
xviii
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]
xix
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 xx defines notice icons used in this guide.
Table 1: Notice Icons
xx
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 xx 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)
xxi
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)
xxii
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/
•
xxiii
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
MX480 Router Description | 25
MX480 Chassis | 28
MX480 Cooling System | 41
MX480 Power System Description | 43
MX480 AC Power System | 44
MX480 DC Power System | 54
MX480 Host Subsystem | 61
MX480 Interface Modules—DPCs | 106
MX480 Interface Modules—FPCs and PICs | 116
MX480 Interface Modules—MPCs and MICs | 124
Services Processing Card—MX-SPC3 Services Card | 162
MX-Series Switch Control Board (SCB) Description | 168
MX480 Router Description
IN THIS SECTION
Benefits of the MX480 Router | 25
MX480 Hardware Overview | 26
The MX480 5G Universal Routing Platform is an Ethernet-optimized edge router that provides both
switching and carrier-class Ethernet routing. The MX480 router enables a wide range of business and
residential applications and services, including high-speed transport and VPN services, next-generation
broadband multiplay services, high-speed Internet and data center internetworking.
25
Benefits of the MX480 Router
System Capacity—MX480 provides 9 Tbps of system capacity for a wide range of cloud, campus,
•
enterprise, data center, service provider, cable, and mobile service core applications.
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.
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.
MX480 Hardware Overview
The MX480 chassis provides redundancy and resiliency. The hardware system is fully redundant, including
power supplies, Routing Engines, and Switch Control Boards (SCBs).
26
The MX480 router is eight rack units (U) tall. Five routers can be stacked in a single floor-to-ceiling rack,
for increased port density per unit of floor space. The router provides eight slots that can be populated
with up to six Dense Port Concentrators (DPCs) or Modular Port Concentrators (MPCs), three Flexible PIC
Concentrators (FPCs), and two SCBs. Each FPC holds up to two PICs and each MPC holds up to two
Modular Interface Cards (MICs).
Fully populated, the MX480 router provides an aggregate switch fabric capacity of up to 5.76 Tbps and
line-rate throughput for up to 240 10-Gigabit Ethernet ports, or 24 100-Gigabit Ethernet, or 72 40-Gigabit
Ethernet ports.
Table 3 on page 26 lists the MX480 router capacity.
Table 3: MX480 Router Capacity
CapacityDescription
5.76 Tbps half duplexSystem capacity
480 GbpsSwitch fabric capacity per slot
6MPCs and DPCs per chassis
6Chassis per rack
Each DPC includes either two or four Packet Forwarding Engines. Each Packet Forwarding Engine enables
a throughput of 10 Gbps. Many types of DPCs are available. For a list of the DPCs supported, see the MX
Series Interface Module Reference.
The MX480 supports up to 3 FPCs containing up to 6 PICs or up to 6 MPCs containing up to 12 MICs.
For a list of the supported line cards, see the MX Series Interface Module Reference.
Four SCBs are available for the MX480 routers—SCB, SCBE, SCBE2, and SCBE3.
Table 4 on page 27 compares the fabric bandwidth capacities of SCBs per MX-series router.
Table 4: Switch Control Board Capacities for MX Series 5G Universal Routing Platforms (Full-Duplex)
27
Enhanced MX Switch
Control Board (model
SCBE3-MX)
Enhanced MX Switch
Control Board
(SCBE2-MX)
Enhanced MX Switch
Control Board
(SCBE-MX)
Switch Control Board
(SCB-MX)
fabric configuration with
MPC10E line cards); 1 Tbps
(redundant fabric configuration
with MPC10E line cards)
(non-redundant fabric
configuration); 340 Gbps
(redundant fabric configuration)
(non-redundant fabric
configuration); 160 Gbps
(redundant fabric configuration)
(non-redundant fabric
configuration); 120 Gbps
(redundant fabric configuration)
MX240 Fabric
BandwidthFabric Bandwidth Per SlotDescription
MX480 Fabric
Bandwidth
MX960 Fabric
Bandwidth
Up to 33 TbpsUp to 18 TbpsUp to 6 TbpsUp to 1.5 Tbps (non-redundant
Up to 10.56 TbpsUp to 5.76 TbpsUp to 1.92 TbpsUp to 480 Gbps
Up to 5.25 TbpsUp to 2.79 TbpsUp to 930 GbpsUp to 240 Gbps
Up to 2.6 TbpsUp to 1.39 TbpsUp to 465 GbpsUp to 240 Gbps
The connections between DPCs, FPCs, MPCs, and SCBs are organized in three groups:
Switch fabric—Connects the interface cards and provides for packet transport between DPCs, FPCs,
•
and MPCs.
Control plane—Gigabit Ethernet links between the combined SCBs/Routing Engines and each DPC, FPC,
•
or MPC. All board-to-board information is passed over Ethernet except for low-level status and commands.
Management signals—Provide for low-level status diagnostic support.
•
MX480 Chassis
IN THIS SECTION
MX480 Chassis Description | 28
MX480 Component Redundancy | 30
MX480 Router Hardware and CLI Terminology Mapping | 31
MX480 Craft Interface Description | 34
Alarm Relay Contacts on the MX480 Craft Interface | 35
Alarm LEDs and Alarm Cutoff/Lamp Test Button on the MX480 Craft Interface | 35
MX480 Component LEDs on the Craft Interface | 36
MX480 Cable Management Brackets | 39
28
MX480 Chassis Description
The router chassis is a rigid sheet metal structure that houses all the other router components (see
Figure 1 on page 29, Figure 2 on page 29, and Figure 3 on page 30). The chassis measures 14.0 in. (35.6 cm)
high, 17.45 in. (44.3 cm) wide, and 24.5 in. (62.2 cm) deep (from the front to the rear of the chassis). The
chassis installs in standard 800-mm (or larger) enclosed cabinets, 19-in. equipment racks, or telco open-frame
racks. Up to five routers can be installed in one standard 48-U rack if the rack can handle their combined
weight, which can be greater than 818 lb (371.0 kg).
Figure 1: Front View of a Fully Configured Router Chassis
OK
MASTER
FAN
ONLINE
OFFLINE
0
1
1
0
FAIL
FAIL
PEM
FAIL
FAIL
FAIL
FAIL
FAIL
FAIL
ESD
OK
OK
OK
OK
OK
OK
OK
2
3
4
5
ACO/LT
NC
NO
C
NC
NO
C
g004200
Front-mounting
flange
SCB1
DPC5
RE1
RE0
SCB0
ESD point Craft interface panel
Air intake
DPC4
DPC3
DPC2
DPC1
DPC0
29
Figure 2: Rear View of a Fully Configured AC-Powered Router Chassis
Figure 3: Rear View of a Fully Configured DC-Powered Router Chassis
30
SEE ALSO
MX480 Router Physical Specifications | 175
MX480 Component Redundancy
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:
Host subsystem—The host subsystem consists of a Routing Engine functioning together with an SCB.
•
The router can have one or two host subsystems. If two host subsystems are installed, one functions as
the primary and the other functions as the backup. If the primary host subsystem (or either of its
components) fails, the backup can take over as the primary. To operate, each host subsystem requires
a Routing Engine installed directly into in an SCB.
If the Routing Engines are configured for graceful switchover, the backup Routing Engine automatically
synchronizes its configuration and state with the primary Routing Engine. Any update to the primary
Routing Engine state is replicated on the backup Routing Engine. If the backup Routing Engine assumes
primary role, packet forwarding continues through the router without interruption. For more information
about graceful switchover, see the Junos OS Administration Library.
Loading...