MX Series Interface Module Reference

Modified: 2018-04-30

Copyright © 2018, Juniper Networks, Inc.

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. and/or its affiliates in
the United States and other countries. All other trademarks may be 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.

MX Series Interface Module Reference

Copyright © 2018 Juniper Networks, Inc. All rights reserved.

The information in this document is current as of the date on the title page.

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://www.juniper.net/support/eula/. By downloading, installing or using such software, you agree to the terms and conditions of that
EULA.

ii Copyright © 2018, Juniper Networks, Inc.

Table of Contents
About the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
Documentation and Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
Requesting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii
Self-Help Online Tools and Resources . . . . . . . . . . . . . . . . . . . . . . . . . . xviii
Opening a Case with JTAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii

Part 1 Overview
Chapter 1 Interface Module Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
MX Series Interface Module Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Chapter 2 DPCs Supported on MX Series Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
MX Series DPC Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
DPCs Supported on MX240, MX480, and MX960 Routers . . . . . . . . . . . . . . . . . . . 8
Chapter 3 MPCs Supported on MX Series Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
MX Series MPC Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
MPCs Supported by MX Series Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Chapter 4 MICs Supported on MX Series Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
MX Series MIC Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
MICs Supported by MX Series Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
MIC/MPC Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Chapter 5 FPCs and PICs Supported on MX Series Routers . . . . . . . . . . . . . . . . . . . . . . 35
MX Series FPC and PIC Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
High Availability Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
FPCs Supported by MX240, MX480, and MX960 Routers . . . . . . . . . . . . . . . . . . 36
PICs Supported by MX240, MX480, and MX960 Routers . . . . . . . . . . . . . . . . . . . 37
Chapter 6 Network Interface Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Determining Transceiver Support and Specifications . . . . . . . . . . . . . . . . . . . . . . 39
Cable and Connector Specifications for MX Series and PTX Series Devices . . . . 40
12-Fiber MPO Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
12-Fiber Ribbon Patch Cables with MPO Connectors . . . . . . . . . . . . . . . . 41
12-Fiber Ribbon Breakout Cables with MPO-to-LC Duplex
Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
12-Ribbon Patch and Breakout Cables Available from Juniper
Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
24-Fiber MPO Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Copyright © 2018, Juniper Networks, Inc. iii

MX Series Interface Module Reference

LC Duplex Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Part 2 DPC, MPC, MIC, and PIC Descriptions

Chapter 7 MX Series DPC Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Gigabit Ethernet DPC with SFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Gigabit Ethernet Enhanced DPC with SFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Gigabit Ethernet Enhanced Ethernet Services DPC with SFP . . . . . . . . . . . . . . . . 54
Gigabit Ethernet Enhanced Queuing Ethernet Services DPC with SFP . . . . . . . . . 56
Gigabit Ethernet Enhanced Queuing IP Services DPCs with SFP . . . . . . . . . . . . . 58
10-Gigabit Ethernet DPC with XFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
10-Gigabit Ethernet Enhanced DPCs with XFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
10-Gigabit Ethernet Enhanced Ethernet Services DPC with XFP . . . . . . . . . . . . . 65
10-Gigabit Ethernet Enhanced Queuing Ethernet Services DPC with XFP . . . . . . 67
10-Gigabit Ethernet Enhanced Queuing IP Services DPC with XFP . . . . . . . . . . . . 69
Multi-Rate Ethernet Enhanced DPC with SFP and XFP . . . . . . . . . . . . . . . . . . . . . . 71
Multi-Rate Ethernet Enhanced Ethernet Services DPC with SFP and XFP . . . . . . 73
Multi-Rate Ethernet Enhanced Queuing IP Services DPC with SFP and XFP . . . . 75
Multiservices DPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Tri-Rate Enhanced DPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Tri-Rate Enhanced Ethernet Services DPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Chapter 8 MX Series MPC Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
16x10GE MPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Multiservices MPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
MPC1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
MPC1E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
MPC1 Q . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
MPC1E Q . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
MPC2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
MPC2E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
MPC2 Q . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
MPC2E Q . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
MPC2 EQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
MPC2E EQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
MPC2E P . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
MPC2E NG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
MPC2E NG Q . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
MPC3E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
MPC3E NG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
MPC3E NG Q . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
32x10GE MPC4E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
2x100GE + 8x10GE MPC4E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
6x40GE + 24x10GE MPC5E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
6x40GE + 24x10GE MPC5EQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
2x100GE + 4x10GE MPC5E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
2x100GE + 4x10GE MPC5EQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
MPC6E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
MPC7E (Multi-Rate) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
MPC7E 10G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

iv Copyright © 2018, Juniper Networks, Inc.

 Table of Contents

MPC8E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
MPC9E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
MX10003 MPC (Multi-Rate) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Chapter 9 MX Series MIC Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
ATM MIC with SFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
DS3/E3 MIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Gigabit Ethernet MIC with SFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Port Numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Gigabit Ethernet MIC with SFP (E) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Gigabit Ethernet MIC with SFP (EH) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
10-Gigabit Ethernet MICs with XFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
10-Gigabit Ethernet MIC with SFP+ (10 Ports) . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
10-Gigabit Ethernet MIC with SFP+ (24 Ports) . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
10-Gigabit Ethernet OTN MIC with SFP+ (24 Ports) . . . . . . . . . . . . . . . . . . . . . . 160
40-Gigabit Ethernet MIC with QSFP+ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
100-Gigabit Ethernet MIC with CFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
100-Gigabit Ethernet MIC with CXP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
100-Gigabit Ethernet MIC with CXP (4 Ports) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
100-Gigabit Ethernet MIC with CFP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
100-Gigabit DWDM OTN MIC with CFP2-ACO . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Channelized SONET/SDH OC3/STM1 (Multi-Rate) MICs with SFP . . . . . . . . . . . 178
Channelized OC3/STM1 (Multi-Rate) Circuit Emulation MIC with SFP . . . . . . . . 183
Channelized OC3/STM1 (Multi-Rate) Circuit Emulation MIC with SFP (H) . . . . . 185
Channelized E1/T1 Circuit Emulation MIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Channelized E1/T1 Circuit Emulation MIC (H) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Tri-Rate MIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
MIC MRATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Multiservices MIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
SONET/SDH OC3/STM1 (Multi-Rate) MICs with SFP . . . . . . . . . . . . . . . . . . . . . 202
Multi-Rate Ethernet MIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
SONET/SDH OC192/STM64 MIC with XFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Chapter 10 MX Series PIC Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Channelized OC12/STM4 Enhanced IQ (IQE) PIC with SFP . . . . . . . . . . . . . . . . . 213
Channelized OC48/STM16 Enhanced IQ (IQE) PIC with SFP . . . . . . . . . . . . . . . . 214
SONET/SDH OC3/STM1 (Multi-Rate) PIC with SFP . . . . . . . . . . . . . . . . . . . . . . 220
SONET/SDH OC12/STM4 (Multi-Rate) PIC with SFP . . . . . . . . . . . . . . . . . . . . . 223
SONET/SDH OC48/STM16 Enhanced IQ (IQE) PIC with SFP . . . . . . . . . . . . . . . 226
SONET/SDH OC48/STM16 (Multi-Rate) PIC with SFP . . . . . . . . . . . . . . . . . . . . 230
SONET/SDH OC48/STM16 PIC with SFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
SONET/SDH OC192c/STM64 PIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
SONET/SDH OC192c/STM64 PIC with XFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

Part 3 SFB, SCB, ADC, and CB-RE Descriptions

Chapter 11 SFB and SFB2 Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
MX2000 Switch Fabric Board (SFB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
MX2000 Enhanced Switch Fabric Board (SFB2) . . . . . . . . . . . . . . . . . . . . . . . . . 248

Copyright © 2018, Juniper Networks, Inc. v

MX Series Interface Module Reference

Chapter 12 SCBs, SCBEs, and SCBE2 Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

MX-Series Switch Control Board (SCB) Overview . . . . . . . . . . . . . . . . . . . . . . . . 252
CLI Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
SCBE2-MX Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
SCBE2 Interoperability with Existing Hardware . . . . . . . . . . . . . . . . . . . . . . . 256
MX SCBE Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
MX SCBE Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
MX SCBE Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
MX SCBE Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
Supported Routing Engines and MPCs for the SCBE . . . . . . . . . . . . . . . . . . 259
MX480 SCBE Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
MX SCBE Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
MX SCBE Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
MX SCBE Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
MX240 SCBE Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
MX SCBE Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
MX SCBE Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
MX SCBE Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
MX960 SCB Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
SCB Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
SCB Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
SCB Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Supported Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
MX480 SCB Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
SCB Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
SCB Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
SCB Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
MX240 SCB Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
SCB Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
SCB Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
SCB Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
Chapter 13 ADC Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
MX2020 Adapter Card (ADC) Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
MX2010 Adapter Card (ADC) Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
Chapter 14 RE, CB-RE, and RCB Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
MX2000 Host Subsystem CB-RE Description . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
MX960 Routing Engine Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
Supported Routing Engines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
Routing Engine Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Routing Engine Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Routing Engine Interface Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
MX480 Routing Engine Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Routing Engine Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Routing Engine Interface Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Routing Engine Boot Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

vi Copyright © 2018, Juniper Networks, Inc.

 Table of Contents

MX240 Routing Engine Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280

RE-S-X6-64G and RE-S-X6-64G-LT Routing Engine Components . . . . . . 282
Routing Engine Interface Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
RE-S-X6-64G and RE-S-X6-64G-LT Routing Engine Interface Ports . . . . . 283
Routing Engine Boot Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
MX5, MX10, MX40, and MX80 Routing Engine Description . . . . . . . . . . . . . . . . . 284
MX2008 Routing and Control Board (MX2008 RCB) Description . . . . . . . . . . . 284
Supported RCB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
RCB Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
RCB Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
RCB Front Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
RCB Interface Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
MX10003 Routing and Control Board (RCB) Description . . . . . . . . . . . . . . . . . . 288
Routing and Control Board Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
Routing and Control Board Components . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
RCB Front Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
RCB Interface Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
Routing Engine Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291

Part 4 Protocol and Application Support

Chapter 15 DPC Protocol and Application Support for MX240, MX480, and
MX960 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
Protocols and Applications Supported by DPCs and Enhanced DPCs (DPC and
DPCE-R) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
Protocols and Applications Supported by Enhanced Ethernet Services DPCs
(DPCE-X) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
Protocols and Applications Supported by Enhanced Queuing IP Services DPCs
(DPCE-R-Q) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Protocols and Applications Supported by Enhanced Queuing Ethernet Services
DPCs (DPCE-X-Q) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
Protocols and Applications Supported by the Multiservices DPC (MS-DPC) . . . 317
Chapter 16 MPC Protocol and Application Support for MX240, MX480, MX960,
MX2010, MX2020, and MX10003 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
Protocols and Applications Supported on MPCs for MX Series Routers . . . . . . . 319
Protocols and Applications Supported on the MPC1E for MX Series Routers . . . 328
Protocols and Applications Supported by the MX240, MX480, MX960, MX2010,
and MX2020 MPC2E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
Protocols and Applications Supported by the MPC3E on MX Series Routers . . . 343
Protocols and Applications Supported on the MPC4E for MX Series Routers . . . 351
Protocols and Applications Supported by the MPC5E for MX Series Routers . . 359
Protocols and Applications Supported by the MPC6E for MX2000 Routers . . . 366
Protocols and Applications Supported by the MPC7E for MX Series Routers . . . 373
Protocols and Applications Supported by the MPC8E and MPC9E on the MX2010
and MX2020 Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
Protocols and Applications Supported by the MS-MIC and MS-MPC . . . . . . . . 389
Protocols and Applications Supported by the MX10003 MPC (Multi-Rate) on
the MX10003 Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391

Copyright © 2018, Juniper Networks, Inc. vii

MX Series Interface Module Reference

viii Copyright © 2018, Juniper Networks, Inc.

List of Figures
Part 1 Overview
Chapter 6 Network Interface Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Figure 1: 24-Fiber MPO Optical Lane Assignments . . . . . . . . . . . . . . . . . . . . . . . . . 44
Figure 2: LC Duplex Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Part 2 DPC, MPC, MIC, and PIC Descriptions

Chapter 7 MX Series DPC Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Figure 3: 20-Port Gigabit Ethernet Enhanced Queuing IP Services DPC with
SFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Figure 4: 40-Port Gigabit Ethernet Enhanced Queuing IP Services DPC with
SFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Figure 5: 2-Port 10-Gigabit Ethernet Enhanced DPC with XFP . . . . . . . . . . . . . . . 63
Figure 6: 4-Port 10-Gigabit Ethernet Enhanced DPC with XFP . . . . . . . . . . . . . . . 63
Chapter 8 MX Series MPC Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Figure 7: Multiservices MPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Chapter 9 MX Series MIC Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Figure 8: 8-Port ATM MIC with SFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Figure 9: DS3/E3 MIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Figure 10: 20-Port Gigabit Ethernet MIC with SFP . . . . . . . . . . . . . . . . . . . . . . . . . 147
Figure 11: Port Numbering for the Gigabit Ethernet MIC with SFP (MX960) . . . . 148
Figure 12: Port Numbering for the Gigabit Ethernet MIC with SFP (MX480) . . . . 149
Figure 13: Port Numbering for Gigabit Ethernet MIC with SFP (MX240) . . . . . . . 149
Figure 14: 20-Port Gigabit Ethernet MIC with SFP (E) . . . . . . . . . . . . . . . . . . . . . 150
Figure 15: Port Numbering for the MIC-3D-20GE-SFP-E (MX960) . . . . . . . . . . . 152
Figure 16: Port Numbering for the MIC-3D-20GE-SFP-E (MX480) . . . . . . . . . . . 153
Figure 17: Port Numbering for the MIC-3D-20GE-SFP-E (MX240) . . . . . . . . . . . . 153
Figure 18: 20-Port Gigabit Ethernet MIC with SFP (EH) . . . . . . . . . . . . . . . . . . . . 154
Figure 19: 2-Port 10-Gigabit Ethernet MIC with XFP . . . . . . . . . . . . . . . . . . . . . . . 155
Figure 20: 4-Port 10-Gigabit Ethernet MIC with XFP . . . . . . . . . . . . . . . . . . . . . . . 156
Figure 21: 10-Gigabit Ethernet MIC with SFP+ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Figure 22: 40-Gigabit Ethernet MIC with QSFP+ . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Figure 23: 1-Port 100 Gigabit Ethernet MIC with CFP . . . . . . . . . . . . . . . . . . . . . . 163
Figure 24: 100-Gigabit Ethernet MIC with CXP . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Figure 25: 4-Port Channelized SONET/SDH OC3/STM1 (Multi-Rate) MIC with
SFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Figure 26: 8-Port Channelized SONET/SDH OC3/STM1 (Multi-Rate) MIC with
SFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Copyright © 2018, Juniper Networks, Inc. ix

MX Series Interface Module Reference

Figure 27: Channelized OC3/STM1 (Multi-Rate) Circuit Emulation MIC with

SFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Figure 28: Channelized OC3/STM1 (Multi-Rate) Circuit Emulation MIC with SFP
(H) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Figure 29: Channelized E1/T1 Circuit Emulation MIC . . . . . . . . . . . . . . . . . . . . . . . 188
Figure 30: Channelized E1/T1 Circuit Emulation MIC (H) . . . . . . . . . . . . . . . . . . . . 191
Figure 31: 40-Port Tri-Rate MIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Figure 32: Port Numbering for the Tri-Rate MIC (MX960) . . . . . . . . . . . . . . . . . . 196
Figure 33: Port Numbering for the Tri-Rate MIC (MX480) . . . . . . . . . . . . . . . . . . 197
Figure 34: Port Numbering for the Tri-Rate MIC (MX240) . . . . . . . . . . . . . . . . . . . 197
Figure 35: 12-Port Multi-Rate MIC with QSFP+ . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Figure 36: MS-MIC-16G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Figure 37: 4-Port SONET/SDH OC3/STM1 (Multi-Rate) MIC with SFP . . . . . . . . 202
Figure 38: 8-Port SONET/SDH OC3/STM1 (Multi-Rate) MIC with SFP . . . . . . . . 202
Figure 39: Multi-Rate MIC with QSFP+ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Figure 40: Multi-Rate MACsec MIC with QSFP+ . . . . . . . . . . . . . . . . . . . . . . . . . 206
Figure 41: Multi-Rate MACsec MIC with QSFP+ . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Figure 42: SONET/SDH OC192/STM64 MIC with XFP . . . . . . . . . . . . . . . . . . . . . 209

Part 3 SFB, SCB, ADC, and CB-RE Descriptions

Chapter 11 SFB and SFB2 Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Figure 43: Switch Fabric Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Figure 44: Enhanced Switch Fabric Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
Chapter 12 SCBs, SCBEs, and SCBE2 Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Figure 45: SCBE2-MX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Figure 46: MX SCBE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
Figure 47: MX SCBE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
Figure 48: MX SCBE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
Figure 49: SCB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
Figure 50: SCB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Figure 51: SCB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
Chapter 13 ADC Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Figure 52: ADC for the MX2010 and MX2020 Routers . . . . . . . . . . . . . . . . . . . . . 272
Figure 53: ADC for the MX2010 and MX2020 Routers . . . . . . . . . . . . . . . . . . . . . 273
Chapter 14 RE, CB-RE, and RCB Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Figure 54: RE-S-1800 Routing Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Figure 55: RE-S-X6-64G Routing Engine Front View . . . . . . . . . . . . . . . . . . . . . . 278
Figure 56: RE-S-X6-64G-LT Routing Engine Front View . . . . . . . . . . . . . . . . . . . 279
Figure 57: RE-S-2000 Routing Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Figure 58: RE-S-1800 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Figure 59: RE-S-X6-64G Routing Engine Front View . . . . . . . . . . . . . . . . . . . . . . 281
Figure 60: RE-S-X6-64G-LT Routing Engine Front View . . . . . . . . . . . . . . . . . . . 282
Figure 61: RCB Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
Figure 62: Routing and Control Board (RCB) Ports . . . . . . . . . . . . . . . . . . . . . . . 289

x Copyright © 2018, Juniper Networks, Inc.

List of Tables
About the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
Table 1: Notice Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi
Table 2: Text and Syntax Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi

Part 1 Overview
Chapter 2 DPCs Supported on MX Series Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Table 3: DPCs Supported in MX240, MX480, and MX960 Routers . . . . . . . . . . . . . 8
Chapter 3 MPCs Supported on MX Series Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Table 4: MPCs Supported by MX240, MX480, MX960, MX2008, MX2010,
MX2020, and MX10003 Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Chapter 4 MICs Supported on MX Series Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Table 5: MICs Supported by MX240, MX480, MX960 and MX2008 Routers . . . . 18
Table 6: MICs Supported by MX2010 and MX2020 Routers . . . . . . . . . . . . . . . . . 20
Table 7: MICs Supported by MX5, MX10, and MX40 Routers . . . . . . . . . . . . . . . . . 22
Table 8: MICs Supported by MX80 and MX104 Routers . . . . . . . . . . . . . . . . . . . . 24
Table 9: MICs Supported by MX10003 Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Table 10: MIC/MPC1 Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Table 11: MIC/MPC2 Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Table 12: MIC/MPC3 Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Table 13: MIC/MPC6 Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Table 14: MIC/MPC8 Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Table 15: MIC/MPC9 Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Table 16: MIC/MPC10003 Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Chapter 5 FPCs and PICs Supported on MX Series Routers . . . . . . . . . . . . . . . . . . . . . . 35
Table 17: FPCs Supported by MX Series Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Table 18: PICs Supported by MX240, MX480, and MX960 Routers . . . . . . . . . . . 37
Chapter 6 Network Interface Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Table 19: Cable Signals for 12-Fiber Ribbon Patch Cables . . . . . . . . . . . . . . . . . . . . 41
Table 20: Cable Pinouts for 12-Fiber Ribbon Patch Cables . . . . . . . . . . . . . . . . . . . 41
Table 21: Cable Pinouts for 12-Fiber Ribbon Breakout Cables . . . . . . . . . . . . . . . . 42
Table 22: 12-Ribbon Patch and Breakout Cables Available from Juniper
Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Part 2 DPC, MPC, MIC, and PIC Descriptions

Chapter 8 MX Series MPC Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Table 23: MX10003 MPC (Multi-Rate) Port Speed . . . . . . . . . . . . . . . . . . . . . . . . 138

Copyright © 2018, Juniper Networks, Inc. xi

MX Series Interface Module Reference

Chapter 9 MX Series MIC Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Table 24: OTN Alarms and Defects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Table 25: MIC MRATE Gigabit Ethernet Port Speed Capabilities . . . . . . . . . . . . . 199
Table 26: Multi Rate Ethernet MIC Port Speed Capabilities for JNP-MIC1 and
JNP-MIC1-MACSEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Table 27: Multi Rate Ethernet MIC Port Speed Capabilities for
MIC-MACSEC-MRATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

Part 3 SFB, SCB, ADC, and CB-RE Descriptions

Chapter 12 SCBs, SCBEs, and SCBE2 Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Table 28: Switch Control Board Capacities and Supported REs . . . . . . . . . . . . . 252
Table 29: SCB Slot Mapping and Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . 264
Chapter 14 RE, CB-RE, and RCB Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Table 30: Components on the RCB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
Table 31: Routing Engine Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Table 32: End-of-Life Routing Engine Specifications . . . . . . . . . . . . . . . . . . . . . . 293

Part 4 Protocol and Application Support

Chapter 15 DPC Protocol and Application Support for MX240, MX480, and
MX960 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
Table 33: Protocols and Applications Supported by the DPCs and Enhanced
DPCs (DPC and DPCE-R) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
Table 34: Protocols and Applications Supported by the Enhanced Ethernet
Services DPCs (DPCE-X) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
Table 35: Protocols and Applications Supported by the Enhanced Queuing IP
Services DPCs (DPCE-R-Q) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
Table 36: Protocols and Applications Supported by the Enhanced Queuing
Ethernet Services DPCs (DPCE-X-Q) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
Table 37: Protocols and Applications Supported by the Multiservices DPC
(MS-DPC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
Chapter 16 MPC Protocol and Application Support for MX240, MX480, MX960,
MX2010, MX2020, and MX10003 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
Table 38: Protocols and Applications Supported by the MX240, MX480, MX960,
MX2010, and MX2020 MPCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
Table 39: Protocols and Applications Supported by the MX240, MX480, MX960,
MX2010, and MX2020 Enhanced MPCs (MPC1Es) . . . . . . . . . . . . . . . . . . . . 328
Table 40: Protocols and Applications Supported by the MX240, MX480, MX960,
MX2010, and MX2020 MPC2E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
Table 41: Protocols and Applications Supported by MPC3E Cards for MX Series
Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
Table 42: Protocols and Applications Supported by the MX Series MPC4E . . . . . 351
Table 43: Protocols and Applications Supported by the MX240, MX480, MX960,
MX2010, and MX2020 MPC5E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
Table 44: Protocols and Applications Supported by the MX2010 and MX2020
MPC6E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366

xii Copyright © 2018, Juniper Networks, Inc.

 List of Tables

Table 45: Protocols and Applications Supported by MPC7Es in the MX240,

MX480, MX960, MX2010, and MX2020 Routers . . . . . . . . . . . . . . . . . . . . . 373
Table 46: Protocols and Applications Supported by MPC8E and MPC9E on the
MX2010 and MX2020 Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
Table 47: Protocols and Applications Supported by the MS-MIC and
MS-MPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
Table 48: Protocols and Applications Supported by MX10003MPC on the
MX10003 Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391

Copyright © 2018, Juniper Networks, Inc. xiii

MX Series Interface Module Reference

xiv Copyright © 2018, Juniper Networks, Inc.

About the Documentation

• Documentation and Release Notes on page xv

• Supported Platforms on page xv
• Documentation Conventions on page xv
• Documentation Feedback on page xvii
• Requesting Technical Support on page xviii

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.

Supported Platforms

For the features described in this document, the following platforms are supported:

• MX Series

Documentation Conventions

Table 1 on page xvi defines notice icons used in this guide.

Copyright © 2018, Juniper Networks, Inc. xv

MX Series Interface Module Reference

Table 1: Notice Icons

Icon Meaning Description

Informational note Indicates important features or instructions.

Caution Indicates a situation that might result in loss of data or hardware damage.

Warning Alerts you to the risk of personal injury or death.

Laser warning Alerts you to the risk of personal injury from a laser.

Tip Indicates helpful information.

Best practice Alerts you to a recommended use or implementation.

Table 2 on page xvi defines the text and syntax conventions used in this guide.

Table 2: Text and Syntax Conventions

Convention Description Examples

Bold text like this Represents text that you type. To enter configuration mode, type the
configure command:

user@host> configure

Fixed-width text like this Represents output that appears on the user@host> show chassis alarms
terminal screen.
No alarms currently active

Italic text like this • Introduces or emphasizes important • A policy term is a named structure
new terms. that defines match conditions and
• Identifies guide names. actions.
• Junos OS CLI User Guide
• Identifies RFC and Internet draft titles.
• RFC 1997, BGP Communities Attribute

Italic text like this Represents variables (options for which Configure the machine’s domain name:
you substitute a value) in commands or
configuration statements. [edit]
root@# set system domain-name
domain-name

xvi Copyright © 2018, Juniper Networks, Inc.

 About the Documentation

Table 2: Text and Syntax Conventions (continued)

Convention Description Examples

Text like this Represents names of configuration • To configure a stub area, include the
statements, commands, files, and stub statement at the [edit protocols
directories; configuration hierarchy levels; ospf area area-id] hierarchy level.
or labels on routing platform • The console port is labeled CONSOLE.
components.

< > (angle brackets) Encloses optional keywords or variables. stub <default-metric metric>;

| (pipe symbol) Indicates a choice between the mutually broadcast | multicast

exclusive keywords or variables on either
side of the symbol. The set of choices is (string1 | string2 | string3)
often enclosed in parentheses for clarity.

# (pound sign) Indicates a comment specified on the rsvp { # Required for dynamic MPLS only
same line as the configuration statement
to which it applies.

[ ] (square brackets) Encloses a variable for which you can community name members [
substitute one or more values. community-ids ]

Indention and braces ( { } ) Identifies a level in the configuration [edit]

hierarchy. routing-options {
static {
route default {
; (semicolon) Identifies a leaf statement at a
nexthop address;
configuration hierarchy level.
retain;
}
}
}

GUI Conventions
Bold text like this Represents graphical user interface (GUI) • In the Logical Interfaces box, select
items you click or select. All Interfaces.
• To cancel the configuration, click
Cancel.

> (bold right angle bracket) Separates levels in a hierarchy of menu In the configuration editor hierarchy,
selections. select Protocols>Ospf.

Documentation Feedback

We encourage you to provide feedback, comments, and suggestions so that we can

improve the documentation. You can provide feedback by using either of the following
methods:

• Online feedback rating system—On any page of the Juniper Networks TechLibrary site
at https://www.juniper.net/documentation/index.html, simply click the stars to rate the
content, and use the pop-up form to provide us with information about your experience.
Alternately, you can use the online feedback form at
https://www.juniper.net/documentation/feedback/.

Copyright © 2018, Juniper Networks, Inc. xvii

MX Series Interface Module Reference

• E-mail—Send your comments to [email protected]. 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 J-Care or Partner Support Service
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/

• 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/

• Open a case online in the CSC Case Management tool: https://www.juniper.net/cm/

To verify service entitlement by product serial number, use our Serial Number Entitlement
(SNE) Tool: https://entitlementsearch.juniper.net/entitlementsearch/

Opening a Case with JTAC

You can open a case with JTAC on the Web or by telephone.

• Use the Case Management tool in the CSC at https://www.juniper.net/cm/.

• Call 1-888-314-JTAC (1-888-314-5822 toll-free in the USA, Canada, and Mexico).

xviii Copyright © 2018, Juniper Networks, Inc.

 About the Documentation

For international or direct-dial options in countries without toll-free numbers, see

https://www.juniper.net/support/requesting-support.html.

Copyright © 2018, Juniper Networks, Inc. xix

MX Series Interface Module Reference

xx Copyright © 2018, Juniper Networks, Inc.

PART 1

Overview
• Interface Module Overview on page 3
• DPCs Supported on MX Series Routers on page 7
• MPCs Supported on MX Series Routers on page 11
• MICs Supported on MX Series Routers on page 17
• FPCs and PICs Supported on MX Series Routers on page 35
• Network Interface Specifications on page 39

Copyright © 2018, Juniper Networks, Inc. 1

MX Series Interface Module Reference

2 Copyright © 2018, Juniper Networks, Inc.

CHAPTER 1

Interface Module Overview

• MX Series Interface Module Overview on page 3

MX Series Interface Module Overview

Juniper Networks MX Series 3D Universal Edge Routers process incoming and outgoing
packets on several different types of interface modules (also known as line cards),
including Dense Port Concentrators (DPCs), Flexible Port Concentrators (FPCs) with
associated Physical Interface Cards (PICs), Trio Modular Port Concentrators (MPCs)
with associated Modular Interface Cards (MICs). FPCs are populated with PICs for various
interface types. DPCs and MPCs combine the functions of FPCs and the PICs, and with
associated physical interfaces support a variety of interface types. The configuration
syntax for each type of line card is the same: type-fpc/pic/port.

Switch Control Boards (MX-SCBs, MX-SCBEs, MX-SCBE2s) provide full line-rate

performance and redundancy without a loss of bandwidth for all MX series routers. Switch
Fabric Boards (SFBs) provide increased fabric bandwidth per slot for MX2000 routers.
Routing Engines (REs) and Control Boards with Routing Engines (CB-REs) provide the
software processes that run Junos OS.

• Dense Port Concentrators (DPCs)—A DPC provides multiple physical interfaces and
Packet Forwarding Engines on a single board that installs into a slot within the MX240,
MX480, and MX960 routers. See the following topics for more information about DPCs:

• MX Series DPC Overview on page 7

• DPCs Supported on MX240, MX480, and MX960 Routers on page 8

• Modular Port Concentrators (MPCs) provide packet forwarding services. The MPCs
are inserted into a slot in an MX240, MX480, MX960, MX2008, MX2010, and MX2020
router. MPCs for MX5, MX10, MX40, MX80, and MX104 routers install directly into the
router chassis. Modular Interface Cards (MICs) provide the physical interfaces and
install into the MPCs. You can install up to two MICs of different media types in the
same MPC as long as the MPC supports those MICs. See the following topics for
information about MPCs:

• MX Series MPC Overview on page 11

• MPCs Supported by MX Series Routers on page 12

• MIC/MPC Compatibility on page 26

Copyright © 2018, Juniper Networks, Inc. 3

MX Series Interface Module Reference

• Protocols and Applications Supported on MPCs for MX Series Routers on page 319

• Protocols and Applications Supported by the MPC3E on MX Series Routers on page 343

• Protocols and Applications Supported on the MPC4E for MX Series Routers on

page 351

• Protocols and Applications Supported by the MPC5E for MX Series Routers on

page 359

• Protocols and Applications Supported by the MPC6E for MX2000 Routers on page 366

• Protocols and Applications Supported by the MPC7E for MX Series Routers on page 373

• Protocols and Applications Supported by the MPC8E and MPC9E on the MX2010
and MX2020 Routers on page 382

• Protocols and Applications Supported by the MS-MIC and MS-MPC on page 389

• Protocols and Applications Supported by the MX10003 MPC (Multi-Rate) on the

MX10003 Router on page 391

• Modular Interface Cards (MICs) provide physical interfaces for the router. MICs install
into Modular Port Concentrators (MPCs) which provide packet forwarding services.
MICs and MPCs function similarly to PICs and FPCs. MPCs install vertically in the
MX2020, MX2010, MX2008, and MX960 router chassis, and horizontally in the MX480
and MX240 router chassis. On MX5, MX10, MX40, MX80, and MX104 routers, MICs
install directly into the router chassis. There are also fixed-configuration MPCs, with
built-in network ports or services functionality, that do not accept MICs. The maximum
number of supported MPCs varies per router and hardware configuration. See the
following topics for information about MICs:

• MX Series MIC Overview on page 17

• MICs Supported by MX Series Routers on page 18

• MIC/MPC Compatibility on page 26

• Flexible PIC Concentrators (FPCs) and Physical Interface Cards (PICs) function similarly
to MICs and MPCs. PICs provide physical interfaces for the router, and install into FPCs,
which provide packet forwarding services. FPCs are installed into a slot in an MX240,
MX480, and MX960 router. See the following topics for information about PICs and
FPCs:

• MX Series FPC and PIC Overview on page 35

• High Availability Features on page 36

• FPCs Supported by MX240, MX480, and MX960 Routers on page 36

• PICs Supported by MX240, MX480, and MX960 Routers on page 37

• Switch Fabric Boards (SFBs) provide increased fabric bandwidth per slot. The MX2000
line of routers can support eight Switch Fabric Boards (SFB) and eight Enhanced Switch
Fabric Boards (SFB2) but not both at the same time. The SFB is supported on MX2010
and MX2020 routers. See the following topics for information about SFBs:

• MX2000 Switch Fabric Board (SFB) on page 245

4 Copyright © 2018, Juniper Networks, Inc.

 Chapter 1: Interface Module Overview

• MX2000 Enhanced Switch Fabric Board (SFB2) on page 248

• MX Switch Control Boards (MX-SCBs, MX-SCBEs, MX-SCBE2s) provide full line-rate

performance and redundancy without a loss of bandwidth. The MX-SCB is the
first-generation SCB and was designed to work with the first-generation DPC line cards.
The MX-SCBE was designed specifically for use with the MPC3e line cards. The
MX-SCBE2 provides improved fabric performance for high-capacity line cards using
the third generation fabric XF2 chip (MPC4e, MPC5e, MPC2/3 NG, and MPC7e). See
the following topics for information about MX-SCBs, MX-SCBEs, and MX-SCBE2s:

• MX-Series Switch Control Board (SCB) Overview on page 252

• SCBE2-MX Description on page 253

• MX SCBE Description on page 257

• MX480 SCBE Description on page 259

• MX240 SCBE Description on page 261

• MX960 SCB Description on page 263

• MX480 SCB Description on page 266

• MX240 SCB Description on page 267

• MX240 SCBE Description on page 261

• MX960 SCB Description on page 263

• MX480 SCB Description on page 266

• MX240 SCB Description on page 267

• MX-ADC is a special line card adapter (ADC) for line cards that were designed to work
with the MX-SCB and MX-SCBE line cards (MPC1E, MPC2E, and MPC3E). It is supported
only for MX2010 and MX2020 routers. The ADC is a hardware casing that fits into a
line card slot. The MPCs attach to the ADCs which in turn attach to the backplane. See
the following topics for more information about the MX-ADC:

• MX2020 Adapter Card (ADC) Description on page 271

• MX2010 Adapter Card (ADC) Description on page 272

• Routing Engines (REs) and Control Boards with Routing Engines (CB-REs) provide the
software processes that run Junos OS. The routing engine maintains the routing tables,
manages the routing protocols used on the router, controls the router interfaces,
controls some chassis components, and provides the interface for system management
and user access to the router. Each CB-RE is a combined Routing Engine and Switch
Control Board in one unit. See the following topics for information about REs and
CB-REs for MX routers:

• MX2000 Host Subsystem CB-RE Description on page 275

• MX960 Routing Engine Description on page 276

• MX480 Routing Engine Description on page 278

• MX240 Routing Engine Description on page 280

Copyright © 2018, Juniper Networks, Inc. 5

MX Series Interface Module Reference

• MX5, MX10, MX40, and MX80 Routing Engine Description on page 284

• RE-S-X6-64G Routing Engine Description

• RE-MX2000-1800x4 CB-RE Description

• REMX2K-X8-64G and REMX2K-X8-64G-LT CB-RE Description

• Routing Engine Specifications on page 291

6 Copyright © 2018, Juniper Networks, Inc.

CHAPTER 2

DPCs Supported on MX Series Routers

• MX Series DPC Overview on page 7

• DPCs Supported on MX240, MX480, and MX960 Routers on page 8

MX Series DPC Overview

A Dense Port Concentrator (DPC) provides multiple physical interfaces and Packet
Forwarding Engines (PFEs) on a single board that installs into a slot within the MX240,
MX480, and MX9603D Universal Edge Routers. A DPC receives incoming packets from
the network and sends outgoing packets to the network. The PFEs on a DPC are equipped
with purpose-built ASICs that perform packet processing and forwarding.

In addition to Layer 3 routing capabilities, the DPCs also have many Layer 2 functions
that allow MX Series routers to be used for many virtual LAN (VLAN) and other Layer 2
network applications.

NOTE: In the Junos OS CLI, you use the FPC syntax to configure or display
information about DPCs, and you use the PIC syntax to configure or display
information about Packet Forwarding Engines on the DPCs.

DPCs install vertically in the MX960 router chassis and horizontally in the MX480 and
MX240 router chassis. The maximum number of supported DPCs varies per router:

• MX960 router—up to 12 DPCs

• MX480 router—up to 6 DPCs

• MX240 router—up to 3 DPCs

When a slot is not occupied by a DPC, you must insert a blank DPC to fill the empty slot
and ensure proper cooling of the system. For complete information about installing and
handling DPCs, see the hardware guide for your router.

Related • DPCs Supported on MX240, MX480, and MX960 Routers on page 8

Documentation
• Protocols and Applications Supported by DPCs and Enhanced DPCs (DPC and DPCE-R)
on page 297

Copyright © 2018, Juniper Networks, Inc. 7

MX Series Interface Module Reference

• Protocols and Applications Supported by Enhanced Ethernet Services DPCs (DPCE-X)

on page 303

• Protocols and Applications Supported by Enhanced Queuing IP Services DPCs

(DPCE-R-Q) on page 307

• Protocols and Applications Supported by Enhanced Queuing Ethernet Services DPCs

(DPCE-X-Q) on page 312

• Protocols and Applications Supported by the Multiservices DPC (MS-DPC) on page 317

DPCs Supported on MX240, MX480, and MX960 Routers

NOTE: These DPCs have all been announced as End of Life (EOL). The End
of Support (EOS) milestone dates for each model are published at
https://www.juniper.net/support/eol/mseries_hw.html.

Table 3 on page 8 lists the DPCs supported by the MX240, MX480, and MX960 routers.

Table 3: DPCs Supported in MX240, MX480, and MX960 Routers

Maximum
DPC Model Throughput First Junos
DPC Name Number Ports per DPC OS Release

Gigabit Ethernet
“Gigabit Ethernet DPC with SFP” on page 50 DPC-R-40GE-SFP 40 40 Gbps 8.2

EOL (see
PSN-2009-06-400)

“Gigabit Ethernet Enhanced DPC with SFP” on page 52 DPCE-R-40GE-SFP 40 40 Gbps 8.4

EOL (see
PSN-TSB16810)

“Gigabit Ethernet Enhanced Ethernet Services DPC with DPCE-X-40GE-SFP 40 40 Gbps 8.4
SFP” on page 54
EOL (see
PSN-TSB16810)

“Gigabit Ethernet Enhanced Queuing Ethernet Services DPCE-X-Q-40GE-SFP 40 40 Gbps 8.5

DPC with SFP” on page 56
EOL (see
PSN-2013-02-851)

“Gigabit Ethernet Enhanced Queuing IP Services DPCs DPCE-R-Q-20GE-SFP 20 20 Gbps 9.1

with SFP” on page 58
EOL (see
PSN-2013-02-851)

8 Copyright © 2018, Juniper Networks, Inc.

 Chapter 2: DPCs Supported on MX Series Routers

Table 3: DPCs Supported in MX240, MX480, and MX960 Routers (continued)

Maximum
DPC Model Throughput First Junos
DPC Name Number Ports per DPC OS Release

“Gigabit Ethernet Enhanced Queuing IP Services DPCs DPCE-R-Q-40GE-SFP 40 40 Gbps 8.5

with SFP” on page 58
EOL (see
PSN-2011-07-314)

“10-Gigabit Ethernet DPC with XFP” on page 61 DPC-R-4XGE-XFP 4 40 Gbps 8.2

EOL (see
PSN-2009-06-400)

10-Gigabit Ethernet
“10-Gigabit Ethernet Enhanced DPCs with XFP” on DPCE-R-2XGE-XFP 2 20 Gbps 9.1
page 63
EOL (see
PSN-2011-02-314)

“10-Gigabit Ethernet Enhanced DPCs with XFP” on DPCE-R-4XGE-XFP 4 40 Gbps 8.4

page 63
EOL (see
PSN-TSB16810)

“10-Gigabit Ethernet Enhanced Ethernet Services DPC DPCE-X-4XGE-XFP 4 40 Gbps 8.4

with XFP” on page 65
EOL (see
PSN-TSB16810)

“10-Gigabit Ethernet Enhanced Queuing Ethernet Services DPCE-X-Q-4XGE-XFP 4 40 Gbps 8.5

DPC with XFP” on page 67
EOL (see
PSN-2013-02-851)

“10-Gigabit Ethernet Enhanced Queuing IP Services DPC DPCE-R-Q-4XGE-XFP 4 40 Gbps 8.5

with XFP” on page 69
EOL (see
PSN-2011-02-314)

Mulit-Rate Ethernet
“Multi-Rate Ethernet Enhanced DPC with SFP and XFP” DPCE-R-20GE-2XGE 22 40 Gbps 9.2
on page 71
EOL (see
PSN-TSB16810)

“Multi-Rate Ethernet Enhanced Ethernet Services DPC DPCE-X-20GE-2XGE 22 40 Gbps 9.2

with SFP and XFP” on page 73
EOL (see
PSN-2011-02-314)

Copyright © 2018, Juniper Networks, Inc. 9

MX Series Interface Module Reference

Table 3: DPCs Supported in MX240, MX480, and MX960 Routers (continued)

Maximum
DPC Model Throughput First Junos
DPC Name Number Ports per DPC OS Release

“Multi-Rate Ethernet Enhanced Queuing IP Services DPC DPCE-R-Q-20GE-2XGE 22 40 Gbps 9.3

with SFP and XFP” on page 75
EOL (see
PSN-TSB16810)

Tri-Rate Ethernet
“Tri-Rate Enhanced DPC” on page 79 DPCE-R-40GE-TX 40 40 Gbps 9.1

EOL (see
PSN-2013-02-851)

“Tri-Rate Enhanced Ethernet Services DPC” on page 81 DPCE-X-40GE-TX 40 40 Gbps 9.1

EOL (see
PSN-2011-07-315.)

Services
“Multiservices DPC” on page 77 MS-DPC 2 (Not – 9.3
supported)
EOL (see
PSN-TSB16812)

Related • MX Series DPC Overview on page 7

Documentation
• Protocols and Applications Supported by DPCs and Enhanced DPCs (DPC and DPCE-R)
on page 297

• Protocols and Applications Supported by Enhanced Ethernet Services DPCs (DPCE-X)

on page 303

• Protocols and Applications Supported by Enhanced Queuing IP Services DPCs

(DPCE-R-Q) on page 307

• Protocols and Applications Supported by Enhanced Queuing Ethernet Services DPCs

(DPCE-X-Q) on page 312

• Protocols and Applications Supported by the Multiservices DPC (MS-DPC) on page 317

10 Copyright © 2018, Juniper Networks, Inc.

CHAPTER 3

MPCs Supported on MX Series Routers

• MX Series MPC Overview on page 11

• MPCs Supported by MX Series Routers on page 12

MX Series MPC Overview

Modular Port Concentrators (MPCs) provide packet forwarding services. The MPCs are
inserted into a slot in an MX240, MX480, MX960, MX2008, MX2010, MX2020, and
MX10003 router. MPCs for MX5, MX10, MX40, MX80, and MX104 routers install directly
into the router chassis. Modular Interface Cards (MICs) provide the physical interfaces
and install into the MPCs. You can install up to two MICs of different media types in the
same MPC as long as the MPC supports those MICs.

A specialized fixed configuration MPC provides higher port density over MICs and combines
packet forwarding and Ethernet interfaces onto a single line card. The fixed configuration
MPC is inserted into a slot in a router and contains no slots for MICs.

MICs receive incoming packets from the network and transmit outgoing packets to the
network. During this process, each MIC performs framing and high-speed signaling for
its media type. Before transmitting outgoing data packets through the MIC interfaces,
the MPCs encapsulate the packets received. Each MPC is equipped with up to four Junos
Trio chipsets, which perform control functions tailored to the MPC’s media type.

You must install a high-capacity fan tray to use an MPC. When a slot is not occupied by
an MPC, you must insert a blank DPC to fill the empty slot and ensure proper cooling of
the system. For complete information about installing and handling MPCs, see the
hardware guide for your router.

The maximum number of supported MPCs varies per router and hardware configuration:

• MX2020 router—Up to 20 MPCs (For power requirements, see Calculating AC Power

Requirements for MX2020 Routers and Calculating DC Power Requirements for MX2020
Routers).

• MX2010 router—Up to 10 MPCs (For power requirements, see Calculating AC Power

Requirements for MX2010 Routers and Calculating DC Power Requirements for MX2010
Routers.)

• MX960 router—Up to 12 MPCs (For power requirements, see Calculating Power

Requirements for MX960 Routers.)

Copyright © 2018, Juniper Networks, Inc. 11

MX Series Interface Module Reference

• MX480 router—Up to 6 MPCs (For power requirements, seeCalculating Power

Requirements for MX480 Routers.)

• MX240 router—Up to 3 MPCs (For power requirements, see Calculating Power

Requirements for MX240 Routers.)

MX80 router—One fixed 10-Gigabit Ethernet MIC with four ports for uplink connections.

NOTE: The MX80 router is available as a modular (MX80) or fixed

(MX80-48T) chassis. Both chassis have a fixed Modular Interface Card (MIC)
that has 3 10-Gigabit Ethernet ports. The fixed MX80 router has an additional
48 10/100/1000Base-T RJ45 ports. The modular chassis has two dedicated
slots for MICs.

Related • MPCs Supported by MX Series Routers on page 12

Documentation
• Protocols and Applications Supported on MPCs for MX Series Routers on page 319

• Protocols and Applications Supported by the MPC3E on MX Series Routers on page 343

• Protocols and Applications Supported on the MPC4E for MX Series Routers on page 351

• Protocols and Applications Supported by the MPC5E for MX Series Routers on page 359

• Protocols and Applications Supported by the MPC6E for MX2000 Routers on page 366

• MX Series MIC Overview on page 17

• MICs Supported by MX Series Routers on page 18

MPCs Supported by MX Series Routers

Table 4 on page 12 lists the MPCs and their first supported Junos OS release on MX240,
MX480, MX960, MX2008, MX2010, MX2020, and MX10003 routers.

Table 4: MPCs Supported by MX240, MX480, MX960, MX2008, MX2010, MX2020, and MX10003 Routers

First Junos OS
Release on First Junos OS First Junos OS First Junos OS First Junos OS
MPC MX240, Release on Release on Release on Release on
MPC Model MX480, and MX2008 MX2010 MX2020 MX10003
Name Number MX960 Routers Routers Routers Routers Routers

Fixed Configuration MPCs

“16x10GE MPC-3D- 10.0R2 15.1F7 12.3 12.3 –
MPC” on
page 84 16XGE-SFP

“Multiservices MS-MPC 13.2R4 15.1F7 15.1 15.1 –

MPC” on
page 86

12 Copyright © 2018, Juniper Networks, Inc.

 Chapter 3: MPCs Supported on MX Series Routers

Table 4: MPCs Supported by MX240, MX480, MX960, MX2008, MX2010, MX2020, and MX10003
Routers (continued)

First Junos OS
Release on First Junos OS First Junos OS First Junos OS First Junos OS
MPC MX240, Release on Release on Release on Release on
MPC Model MX480, and MX2008 MX2010 MX2020 MX10003
Name Number MX960 Routers Routers Routers Routers Routers

“32x10GE MPC4E-3D- 12.3R2 15.1F7 12.3R2 12.3R2 –

MPC4E” on
page 119 32XGE-SFPP

“2x100GE + MPC4E-3D- 12.3R2 15.1F7 12.3R2 12.3R2 –

8x10GE
MPC4E” on 2CGE-8XGE
page 120

“6x40GE + MPC5E-40G10G 13.3R2 15.1F7 13.3R2 13.3R2 –

24x10GE
MPC5E” on
page 122

“6x40GE + MPC5EQ-40G10G 13.3R2 15.1F7 13.3R2 13.3R2 –

24x10GE
MPC5EQ”
on page 124

“2x100GE + MPC5E-100G10G 13.3R3 15.1F7 13.3R3 13.3R3 –

4x10GE
MPC5E” on
page 125

“2x100GE + MPC5EQ-100G10G 13.3R3 15.1F7 13.3R3 13.3R3 –

4x10GE
MPC5EQ”
on page 127

“MPC7E MPC7E-MRATE • 15.1F4 with 15.1F7 • 15.1F4 with • 15.1F4 with –

(Multi-Rate)” Junos Junos Junos
on page 130 Continuity Continuity Continuity
• 16.1R1 and • 16.1R1 and • 16.1R1 and later
later later

“MPC7E MPC7E-10G • 15.1F5 with 15.1F7 • 15.1F5 with • 15.1F5 with –

10G” on Junos Junos Junos
page 132 Continuity Continuity Continuity
• 16.1R1 and • 16.1R1 and • 16.1R1 and later
later later

MPCs
“MPC1” on MX-MPC1-3D 10.2 15.1F7 12.3 12.3 –
page 88

“MPC1E” on MX-MPC1E-3D 11.2R4 15.1F7 12.3 12.3 –

page 89

Copyright © 2018, Juniper Networks, Inc. 13

MX Series Interface Module Reference

Table 4: MPCs Supported by MX240, MX480, MX960, MX2008, MX2010, MX2020, and MX10003
Routers (continued)

First Junos OS
Release on First Junos OS First Junos OS First Junos OS First Junos OS
MPC MX240, Release on Release on Release on Release on
MPC Model MX480, and MX2008 MX2010 MX2020 MX10003
Name Number MX960 Routers Routers Routers Routers Routers

“MPC1 Q” MX-MPC1-3D-Q 10.2 15.1F7 12.3 12.3 –

on page 91

“MPC1E Q” MX-MPC1E-3D-Q 11.2R4 15.1F7 12.3 12.3 –

on page 93

“MPC2” on MX-MPC2-3D 10.1 15.1F7 12.3 12.3 –

page 95

“MPC2E” on MX-MPC2E-3D 11.2R4 15.1F7 12.3 12.3 –

page 97

“MPC2 Q” MX-MPC2-3D-Q 10.1 15.1F7 12.3 12.3 –

on page 99

“MPC2E Q” MX-MPC2E-3D-Q 11.2R4 15.1F7 12.3 12.3 –

on page 101

“MPC2 EQ” MX-MPC2-3D-EQ 10.1 15.1F7 12.3 12.3 –

on page 103

“MPC2E MX-MPC2E-3D-EQ 11.2R4 15.1F7 12.3 12.3 –

EQ” on
page 105

“MPC2E P” MX-MPC2E-3D-P 12.2 15.1F7 12.3 12.3 –

on page 107

“MPC2E MX-MPC2E-3D-NG 14.1R4, 14.2R3 15.1F7 14.1R4, 14.2R3 14.1R4, 14.2R3 and –
NG” on and Junos and Junos Junos Continuity
page 109 Continuity Continuity
15.1
15.1 15.1

“MPC2E NG MX-MPC2E-3D-NG-Q 14.1R4, 14.2R3 15.1F7 14.1R4, 14.2R3 14.1R4, 14.2R3 and –
Q” on and Junos and Junos Junos Continuity
page 111 Continuity Continuity
15.1
15.1 15.1

“MPC3E” on MX-MPC3E-3D 12.1 15.1F7 12.3 12.3 –

page 113

14 Copyright © 2018, Juniper Networks, Inc.

 Chapter 3: MPCs Supported on MX Series Routers

Table 4: MPCs Supported by MX240, MX480, MX960, MX2008, MX2010, MX2020, and MX10003
Routers (continued)

First Junos OS
Release on First Junos OS First Junos OS First Junos OS First Junos OS
MPC MX240, Release on Release on Release on Release on
MPC Model MX480, and MX2008 MX2010 MX2020 MX10003
Name Number MX960 Routers Routers Routers Routers Routers

“MPC3E MX-MPC3E-3D-NG 14.1R4, 14.2R3 15.1F7 14.1R4, 14.2R3 14.1R4, 14.2R3 and –
NG” on and Junos and Junos Junos Continuity
page 115 Continuity Continuity
15.1
15.1 15.1

“MPC3E NG MX-MPC3E-3D-NG-Q 14.1R4, 14.2R3 15.1F7 14.1R4, 14.2R3 14.1R4, 14.2R3 and –
Q” on and Junos and Junos Junos Continuity
page 117 Continuity Continuity
15.1
15.1 15.1

“MPC6E” MX2K-MPC6E – 15.1F7 13.3R2 13.3R2 –

on page 129

“MPC8E” MX2K-MPC8E – 15.1F7 • 15.1F5 with • 15.1F5 with –

on page 134 Junos Junos
Continuity Continuity
• 16.1R1 and • 16.1R1 and later
later

“MPC9E” MX2K-MPC9E – 15.1F7 • 15.1F5 with • 15.1F5 with –

on page 135 Junos Junos
Continuity Continuity
• 16.1R1 and • 16.1R1 and later
later

“MX10003 MX10003-LC2103 – – – – 17.3

MPC
(Multi-Rate)”
on page 136

Related • MX Series MPC Overview on page 11

Documentation
• MIC/MPC Compatibility on page 26

• MX Series MIC Overview on page 17

• MICs Supported by MX Series Routers on page 18

• Junos Continuity Software Overview

• Pathfinder: Hardware Supported by Junos Continuity Software

Copyright © 2018, Juniper Networks, Inc. 15

MX Series Interface Module Reference

16 Copyright © 2018, Juniper Networks, Inc.

CHAPTER 4

MICs Supported on MX Series Routers

• MX Series MIC Overview on page 17

• MICs Supported by MX Series Routers on page 18
• MIC/MPC Compatibility on page 26

MX Series MIC Overview

MICs provide the physical connections to various network media types. MICs allow
different physical interfaces to be supported on a single line card. You can install MICs
of different media types on the same router as long as the router supports those MICs.

MICs receive incoming packets from the network and transmit outgoing packets to the
network. During this process, each MIC performs framing and high-speed signaling for
its media type. MICs install into Modular Port Concentrators (MPCs) which provide packet
forwarding services. Before transmitting outgoing data packets through the MIC interfaces,
the Modular Port Concentrator (MPCs) encapsulate the packets received. Each MPC is
equipped with up to four Junos Trio chipsets, which perform control functions tailored
to the MPC’s media type.

MICs and MPCs function similarly to PICs and FPCs. MICs are hot-removable and
hot-insertable. You can install up to two MICs of different media types in the same MPC
as long as the MPC supports those MICs. Depending on the MX router chassis, the MICs
install vertically or horizontally into MPCs, or directly into the MX router chassis as follows:

• Vertically into MPCs— MX960, MX2008, MX2010, and MX2020 routers

• Horizontally into MPCs—MX10003, MX480, and MX240 routers

• Directly into the router chassis—MX5, MX10, MX40, MX80, and MX104 routers

NOTE: The MX80 router is available as a modular (MX80) or fixed

(MX80-48T) chassis. Both chassis have a fixed Modular Interface Card (MIC)
that has 3 10-Gigabit Ethernet ports. The fixed MX80 router has an additional
48 10/100/1000Base-T RJ45 ports. The modular chassis has two dedicated
slots for MICs.

Copyright © 2018, Juniper Networks, Inc. 17

MX Series Interface Module Reference

Related • MX Series MPC Overview on page 11

Documentation
• MICs Supported by MX Series Routers on page 18

• MIC/MPC Compatibility on page 26

• MPCs Supported by MX Series Routers on page 12

MICs Supported by MX Series Routers

The following tables list the first supported Junos OS release for the MX Series.

• Table 5 on page 18 lists the first supported Junos OS release for MICs on MX240,
MX480, MX960, and MX2008 routers.

• Table 6 on page 20 lists the first supported Junos OS release for MICs on MX2010 and
MX2020 routers.

• Table 7 on page 22 list the first supported Junos OS release for MICs on MX5, MX10,
and MX40 routers.

• Table 8 on page 24 lists the first supported Junos OS release for MICs on MX80 and
MX104 routers.

• Table 9 on page 26 lists the first supported Junos OS release for MICs on MX10003
router.

Table 5: MICs Supported by MX240, MX480, MX960 and MX2008 Routers

MX240, MX480,
and MX960
MIC Name MIC Model Number Ports Routers MX2008 Routers

ATM
“ATM MIC with SFP” on page 140 MIC-3D-8OC3-2OC12-ATM 8 12.1 15.1F7

DS3/E3
“DS3/E3 MIC” on page 143 MIC-3D-8DS3-E3, 8 11.4 15.1F7

MIC-3D-8CHDS3-E3-B

Circuit Emulation
“Channelized E1/T1 Circuit MIC-3D-16CHE1-T1-CE 16 12.3 15.1F7
Emulation MIC” on page 188

Gigabit Ethernet
“Gigabit Ethernet MIC with SFP” MIC-3D-20GE-SFP 20 10.1 15.1F7
on page 147

“Gigabit Ethernet MIC with SFP MIC-3D-20GE-SFP-E 20 13.3 15.1F7

(E)” on page 150

18 Copyright © 2018, Juniper Networks, Inc.

 Chapter 4: MICs Supported on MX Series Routers

Table 5: MICs Supported by MX240, MX480, MX960 and MX2008 Routers (continued)

MX240, MX480,
and MX960
MIC Name MIC Model Number Ports Routers MX2008 Routers

10-Gigabit Ethernet
“10-Gigabit Ethernet MICs with MIC-3D-2XGE-XFP 2 10.2 15.1F7
XFP” on page 155

“10-Gigabit Ethernet MICs with MIC-3D-4XGE-XFP 4 10.1 15.1F7

XFP” on page 155

“10-Gigabit Ethernet MIC with MIC3-3D-10XGE-SFPP 10 12.3 15.1F7

SFP+ (10 Ports)” on page 157

“10-Gigabit Ethernet MIC with MIC6-10G 24 - 15.1F7

SFP+ (24 Ports)” on page 159

“10-Gigabit Ethernet OTN MIC MIC6-10G-OTN 24 - 15.1F7

with SFP+ (24 Ports)” on
page 160

40-Gigabit Ethernet
“40-Gigabit Ethernet MIC with MIC3-3D-2X40GE-QSFPP 2 12.2 15.1F7
QSFP+” on page 162

100-Gigabit Ethernet
“100-Gigabit Ethernet MIC with MIC3-3D-1X100GE-CFP 1 12.1 15.1F7
CFP” on page 163

“100-Gigabit Ethernet MIC with MIC3-3D-1X100GE-CXP 1 12.2 15.1F7

CXP” on page 165

“100-Gigabit Ethernet MIC with MIC6-100G-CXP 4 - 15.1F7

CXP (4 Ports)” on page 166

“100-Gigabit Ethernet MIC with MIC6-100G-CFP2 2 - 15.1F7

CFP2” on page 167

100-Gigabit DWDM OTN

“100-Gigabit DWDM OTN MIC MIC3-100G-DWDM 1 15.1F5 15.1F7
with CFP2-ACO” on page 169 15.1F6
17.1R1

Multi-Rate
“SONET/SDH OC3/STM1 MIC-3D-4OC3OC12-1OC48 4 11.2 15.1F7
(Multi-Rate) MICs with SFP” on
page 202

Copyright © 2018, Juniper Networks, Inc. 19

MX Series Interface Module Reference

Table 5: MICs Supported by MX240, MX480, MX960 and MX2008 Routers (continued)

MX240, MX480,
and MX960
MIC Name MIC Model Number Ports Routers MX2008 Routers

“SONET/SDH OC3/STM1 MIC-3D-8OC3OC12-4OC48 8 11.2 15.1F7

(Multi-Rate) MICs with SFP” on
page 202

“Channelized SONET/SDH MIC-3D-4CHOC3-2CHOC12 4 11.4 15.1F7

OC3/STM1 (Multi-Rate) MICs
with SFP” on page 178

“Channelized SONET/SDH MIC-3D-8CHOC3-4CHOC12 8 11.4 15.1F7

OC3/STM1 (Multi-Rate) MICs
with SFP” on page 178

“Channelized OC3/STM1 MIC-3D-4COC3-1COC12-CE 4 12.2 15.1F7

(Multi-Rate) Circuit Emulation
MIC with SFP” on page 183

“MIC MRATE” on page 198 MIC-MRATE 12 - 15.1F7

(12-Port Multi-Rate MIC with
QSFP+)

“Multi-Rate Ethernet MIC” on MIC-MACSEC-MRATE 12 17.4

page 206 (12-Port Multi-Rate
MACsec MIC with QSFP+)

Tri-Rate
“Tri-Rate MIC” on page 194 MIC-3D-40GE-TX 40 10.2 15.1F7

Services
“Multiservices MIC” on page 200 MS-MIC-16G 0 13.2 15.1F7

SONET/SDH
“SONET/SDH OC192/STM64 MIC-3D-1OC192-XFP 1 12.2 15.1F7
MIC with XFP” on page 209

Table 6: MICs Supported by MX2010 and MX2020 Routers

MIC Name MIC Model Number Ports MX2010 Routers MX2020 Routers

ATM
“ATM MIC with SFP” on page 140 MIC-3D-8OC3-2OC12-ATM 8 12.3 12.3

DS3/E3
“DS3/E3 MIC” on page 143 MIC-3D-8DS3-E3, 8 12.3 12.3

MIC-3D-8CHDS3-E3-B

20 Copyright © 2018, Juniper Networks, Inc.

 Chapter 4: MICs Supported on MX Series Routers

Table 6: MICs Supported by MX2010 and MX2020 Routers (continued)

MIC Name MIC Model Number Ports MX2010 Routers MX2020 Routers

Circuit Emulation
“Channelized E1/T1 Circuit MIC-3D-16CHE1-T1-CE 16 – –
Emulation MIC” on page 188

Gigabit Ethernet
“Gigabit Ethernet MIC with SFP” MIC-3D-20GE-SFP 20 12.3 12.3
on page 147

“Gigabit Ethernet MIC with SFP MIC-3D-20GE-SFP-E 20 13.3 13.3

(E)” on page 150

10-Gigabit Ethernet
“10-Gigabit Ethernet MICs with MIC-3D-2XGE-XFP 2 12.3 12.3
XFP” on page 155

“10-Gigabit Ethernet MICs with MIC-3D-4XGE-XFP 4 12.3 12.3

XFP” on page 155

“10-Gigabit Ethernet MIC with MIC3-3D-10XGE-SFPP 10 12.3 12.3

SFP+ (10 Ports)” on page 157

“10-Gigabit Ethernet MIC with MIC6-10G 24 13.3R2 13.3R2

SFP+ (24 Ports)” on page 159

“10-Gigabit Ethernet OTN MIC MIC6-10G-OTN 24 13.3R3 13.3R3

with SFP+ (24 Ports)” on
page 160

40-Gigabit Ethernet
“40-Gigabit Ethernet MIC with MIC3-3D-2X40GE-QSFPP 2 12.3 12.3
QSFP+” on page 162

100-Gigabit Ethernet
“100-Gigabit Ethernet MIC with MIC3-3D-1X100GE-CFP 1 12.3 12.3
CFP” on page 163

“100-Gigabit Ethernet MIC with MIC3-3D-1X100GE-CXP 1 12.3 12.3

CXP” on page 165

“100-Gigabit Ethernet MIC with MIC6-100G-CXP 4 13.3R2 13.3R2

CXP (4 Ports)” on page 166

“100-Gigabit Ethernet MIC with MIC6-100G-CFP2 2 13.3R3 13.3R3

CFP2” on page 167

100-Gigabit DWDM OTN

Copyright © 2018, Juniper Networks, Inc. 21

MX Series Interface Module Reference

Table 6: MICs Supported by MX2010 and MX2020 Routers (continued)

MIC Name MIC Model Number Ports MX2010 Routers MX2020 Routers

“100-Gigabit DWDM OTN MIC MIC3-100G-DWDM 1 15.1F5 15.1F5

with CFP2-ACO” on page 169 15.1F6 15.1F6
17.1R1 17.1R1

Multi-Rate
“SONET/SDH OC3/STM1 MIC-3D-4OC3OC12-1OC48 4 12.3 12.3
(Multi-Rate) MICs with SFP” on
page 202

“SONET/SDH OC3/STM1 MIC-3D-8OC3OC12-4OC48 8 12.3 12.3

(Multi-Rate) MICs with SFP” on
page 202

“Channelized SONET/SDH MIC-3D-4CHOC3-2CHOC12 4 12.3 12.3

OC3/STM1 (Multi-Rate) MICs
with SFP” on page 178

“Channelized SONET/SDH MIC-3D-8CHOC3-4CHOC12 8 12.3 12.3

OC3/STM1 (Multi-Rate) MICs
with SFP” on page 178

“Channelized OC3/STM1 MIC-3D-4COC3-1COC12-CE 4 12.3 12.3

(Multi-Rate) Circuit Emulation
MIC with SFP” on page 183

“MIC MRATE” on page 198 MIC-MRATE 12 • 15.1F5 with Junos • 15.1F5 with Junos
(12-Port Multi-Rate MIC with Continuity Continuity
QSFP+) • 16.1R1 and later • 16.1R1 and later

“Multi-Rate Ethernet MIC” on MIC-MACSEC-MRATE 12 17.4 17.4

page 206 (12-Port Multi-Rate
MACsec MIC with QSFP+)

Tri-Rate
“Tri-Rate MIC” on page 194 MIC-3D-40GE-TX 40 12.3 12.3

Services
“Multiservices MIC” on page 200 MS-MIC-16G 0 13.2 13.2

SONET/SDH
“SONET/SDH OC192/STM64 MIC-3D-1OC192-XFP 1 12.3 12.3
MIC with XFP” on page 209

Table 7: MICs Supported by MX5, MX10, and MX40 Routers

MIC Name MIC Model Number Ports MX5 MX10 MX40

ATM

22 Copyright © 2018, Juniper Networks, Inc.

 Chapter 4: MICs Supported on MX Series Routers

Table 7: MICs Supported by MX5, MX10, and MX40 Routers (continued)

MIC Name MIC Model Number Ports MX5 MX10 MX40

“ATM MIC with SFP” on page 140 MIC-3D-8OC3-2OC12-ATM 8 12.1 12.1 12.1

DS3/E3
“DS3/E3 MIC” on page 143 MIC-3D-8DS3-E3, 8 11.4 11.4 11.4

MIC-3D-8CHDS3-E3-B

Circuit Emulation
“Channelized E1/T1 Circuit MIC-3D-16CHE1-T1-CE 16 13.2R2 13.2R2 13.2R2
Emulation MIC” on page 188

“Channelized E1/T1 Circuit MIC-3D-16CHE1-T1-CE-H 16 – – –

Emulation MIC (H)” on page 191

Gigabit Ethernet
“Gigabit Ethernet MIC with SFP” MIC-3D-20GE-SFP 20 11.2R4 11.2R4 11.2R4
on page 147

“Gigabit Ethernet MIC with SFP MIC-3D-20GE-SFP-E 20 13.2R2 13.2R2 13.2R2

(E)” on page 150

“Gigabit Ethernet MIC with SFP MIC-3D-20GE-SFP-EH 20 – – –

(EH)” on page 154

10-Gigabit Ethernet
“10-Gigabit Ethernet MICs with MIC-3D-2XGE-XFP 2 11.2R4 11.2R4 11.2R4
XFP” on page 155

Multi-Rate
“SONET/SDH OC3/STM1 MIC-3D-4OC3OC12-1OC48 4 11.2R4 11.2R4 11.2R4
(Multi-Rate) MICs with SFP” on
page 202

“SONET/SDH OC3/STM1 MIC-3D-8OC3OC12-4OC48 8 11.2R4 11.2R4 11.2R4

(Multi-Rate) MICs with SFP” on
page 202

“Channelized SONET/SDH MIC-3D-4CHOC3-2CHOC12 4 11.4 11.4 11.4

OC3/STM1 (Multi-Rate) MICs
with SFP” on page 178

“Channelized SONET/SDH MIC-3D-8CHOC3-4CHOC12 8 11.4 11.4 11.4

OC3/STM1 (Multi-Rate) MICs
with SFP” on page 178

“Channelized OC3/STM1 MIC-3D-4COC3-1COC12-CE 4 12.2 12.2 12.2

(Multi-Rate) Circuit Emulation
MIC with SFP” on page 183

Copyright © 2018, Juniper Networks, Inc. 23

MX Series Interface Module Reference

Table 7: MICs Supported by MX5, MX10, and MX40 Routers (continued)

MIC Name MIC Model Number Ports MX5 MX10 MX40

“Channelized OC3/STM1 MIC-4COC3-1COC12-CE-H - - - -

(Multi-Rate) Circuit Emulation
MIC with SFP (H)” on page 185

Tri-Rate
“Tri-Rate MIC” on page 194 MIC-3D-40GE-TX 40 – 11.2R4 11.2R4

Services
“Multiservices MIC” on page 200 MS-MIC-16G 0 13.2 13.2 13.2

Rear slot only. Rear slot Rear slot

only. only.

SONET/SDH
“SONET/SDH OC192/STM64 MIC-3D-1OC192-XFP 1 12.2 12.2 12.2
MIC with XFP” on page 209

Table 8: MICs Supported by MX80 and MX104 Routers

MIC Name MIC Model Number Ports MX80 MX104

ATM
“ATM MIC with SFP” on page 140 MIC-3D-8OC3-2OC12-ATM 8 12.1 13.3

DS3/E3
“DS3/E3 MIC” on page 143 MIC-3D-8DS3-E3, 8 11.4 13.3

MIC-3D-8CHDS3-E3-B

Circuit Emulation
“Channelized E1/T1 Circuit MIC-3D-16CHE1-T1-CE 16 13.2R2 13.2R2
Emulation MIC” on page 188

“Channelized E1/T1 Circuit MIC-3D-16CHE1-T1-CE-H 16 – 13.2R2

Emulation MIC (H)” on page 191

Gigabit Ethernet
“Gigabit Ethernet MIC with SFP” MIC-3D-20GE-SFP 20 10.2 13.2R2
on page 147

“Gigabit Ethernet MIC with SFP MIC-3D-20GE-SFP-E 20 13.2R2 13.2R2

(E)” on page 150

“Gigabit Ethernet MIC with SFP MIC-3D-20GE-SFP-EH 20 – 13.2R2

(EH)” on page 154

10-Gigabit Ethernet

24 Copyright © 2018, Juniper Networks, Inc.

 Chapter 4: MICs Supported on MX Series Routers

Table 8: MICs Supported by MX80 and MX104 Routers (continued)

MIC Name MIC Model Number Ports MX80 MX104

“10-Gigabit Ethernet MICs with MIC-3D-2XGE-XFP 2 10.2 13.2R2

XFP” on page 155

Multi-Rate
“SONET/SDH OC3/STM1 MIC-3D-4OC3OC12-1OC48 4 11.2 13.3
(Multi-Rate) MICs with SFP” on
page 202

“SONET/SDH OC3/STM1 MIC-3D-8OC3OC12-4OC48 8 11.2 13.3

(Multi-Rate) MICs with SFP” on
page 202

“Channelized SONET/SDH MIC-3D-4CHOC3-2CHOC12 4 11.4 13.3

OC3/STM1 (Multi-Rate) MICs
with SFP” on page 178

“Channelized SONET/SDH MIC-3D-8CHOC3-4CHOC12 8 11.4 13.3

OC3/STM1 (Multi-Rate) MICs
with SFP” on page 178

“Channelized OC3/STM1 MIC-3D-4COC3-1COC12-CE 4 12.2 13.2R2

(Multi-Rate) Circuit Emulation
MIC with SFP” on page 183

“Channelized OC3/STM1 MIC-4COC3-1COC12-CE-H - - 13.2R2

(Multi-Rate) Circuit Emulation
MIC with SFP (H)” on page 185

Tri-Rate
“Tri-Rate MIC” on page 194 MIC-3D-40GE-TX 40 10.2 13.2R2

Services
“Multiservices MIC” on page 200 MS-MIC-16G 0 13.2 13.3R2

Rear slot only. Supported on NOTE: Starting

the modular MX80 and fixed From Junos
MX80-48T OS 13.3R3,
14.1R2, and
14.2R1,
MX104
supports
only two
Multiservices
MICs.

SONET/SDH
“SONET/SDH OC192/STM64 MIC-3D-1OC192-XFP 1 12.2 13.3
MIC with XFP” on page 209

Copyright © 2018, Juniper Networks, Inc. 25

MX Series Interface Module Reference

Table 9: MICs Supported by MX10003 Router

MIC Name MIC Model Number Ports MX10003

Multi-Rate
“Multi-Rate Ethernet MIC” on JNP-MIC1 12 17.3
page 206 (12-Port Multi-Rate MIC
with QSFP+)

“Multi-Rate Ethernet MIC” on JNP-MIC1-MACSEC 12 17.3R2

page 206 (12-Port Multi-Rate
MACsec MIC with QSFP+)

Related • MX Series MIC Overview on page 17

Documentation
• MIC/MPC Compatibility on page 26

MIC/MPC Compatibility

The following tables provide a compatibility matrix for the MICs currently supported by
MPC1, MPC2, MPC3, MPC6, MPC8, and MPC9 on MX240, MX480, MX960, MX2008,
MX2010, MX2020, and MX10003 routers. Each table lists the first Junos OS release in
which the MPC supports the MIC. For example, Junos OS Release 10.2 is the first release
in which the MX-MPC1-3D supports the Gigabit Ethernet MIC with SFP. An en dash
indicates that the MIC is not supported.

Table 10: MIC/MPC1 Compatibility

MIC Name MPC1 MPC1E MPC1 Q MPC1E Q

MIC-3D-8OC3-2OC12-ATM — — 12.1 12.1R4

(“ATM MIC with SFP”

on page 140)

MIC-3D-20GE-SFP 10.2 11.2R4 10.2 11.2R4

(“Gigabit Ethernet MIC

with SFP” on page 147)

MIC-3D-20GE-SFP-E 13.2R2 13.2R2 13.2R2 13.2R2

(“Gigabit Ethernet MIC

with SFP (E)” on
page 150)

MIC-3D-2XGE-XFP 10.2 11.2R4 10.2 11.2R4

(“10-Gigabit Ethernet
MICs with XFP” on
page 155)

26 Copyright © 2018, Juniper Networks, Inc.

 Chapter 4: MICs Supported on MX Series Routers

Table 10: MIC/MPC1 Compatibility (continued)

MIC Name MPC1 MPC1E MPC1 Q MPC1E Q

MIC-3D-4XGE-XFP — — — —

(“10-Gigabit Ethernet
MICs with XFP” on
page 155)

MIC-3D-40GE-TX 10.2 11.2R4 10.2 11.2R4

(“Tri-Rate MIC” on
page 194)

MIC-3D-4OC3OC12-1OC48, 11.2 11.2R4 11.2 11.2R4

MIC-3D-8OC3OC12-4OC48

(“SONET/SDH
OC3/STM1
(Multi-Rate) MICs with
SFP” on page 202)

MIC-3D-4COC3-1COC12-CE — — 12.2 12.2

(“Channelized
OC3/STM1
(Multi-Rate) Circuit
Emulation MIC with
SFP” on page 183)

MIC-3D-1OC192-XFP 12.2 12.2 12.2 12.2

(“SONET/SDH
OC192/STM64 MIC
with XFP” on page 209)

MIC-3D-4CHOC3-2CHOC12, — — 11.4 11.4

MIC-3D-8CHOC3-4CHOC12

MIC-4COC3-2COC12-G,
MIC-8COC3-4COC12-G

(“Channelized
SONET/SDH
OC3/STM1
(Multi-Rate) MICs with
SFP” on page 178)

MIC-3D-16CHE1-T1-CE 13.2 13.2 12.3 12.3

(“Channelized E1/T1 NOTE: Support for NOTE: Support for

Circuit Emulation MIC” Non-Channelized MIC Non-Channelized MIC
on page 188) only. only.

Copyright © 2018, Juniper Networks, Inc. 27

MX Series Interface Module Reference

Table 10: MIC/MPC1 Compatibility (continued)

MIC Name MPC1 MPC1E MPC1 Q MPC1E Q

MIC-3D-8DS3-E3, 11.4 11.4 11.4 11.4

MIC-3D-8CHDS3-E3-B

(“DS3/E3 MIC” on
page 143)

NOTE: You cannot run

Channelized DS3
(MIC-3D-8CHDS3-E3)
on non-Q MPCs.
Channelized DS3 is
supported only on Q
and EQ-based MPCs.

MS-MIC-16G 13.2 13.2 13.2 13.2

(“Multiservices MIC” on
page 200)

Table 11: MIC/MPC2 Compatibility

MIC MPC2E MPC2E MPC2E

Name MPC2 MPC2E NG MPC2 Q MPC2E Q MPC2 EQ EQ MPC2E P NG Q

M
CI-3D-8OC3-2OC2
1-A
TM — — 14.1R4, 12.1 12.1R4 12.1 12.1R4 — 14.1R4,
14.2R3 with 14.2R3 with
(“ATM Junos Junos
MIC with Continuity Continuity
SFP” on
page 140) 15.1 15.1

MC
I -3D-20GE-SFP 10.1 11.2R4 14.1R4, 10.1 11.2R4 10.1 11.2R4 12.2 14.1R4,
14.2R3 with 14.2R3 with
(“Gigabit Junos Junos
Ethernet Continuity Continuity
MIC with
SFP” on 15.1 15.1
page 147)

MC
I-3D-20GE-SFP-E 13.2R2 13.2R2 14.1R4, 13.2R2 13.2R2 13.2R2 13.2R2 13.2R2 14.1R4,
14.2R3 with 14.2R3 with
(“Gigabit Junos Junos
Ethernet Continuity Continuity
MIC with
SFP (E)” 15.1 15.1
on
page 150)

28 Copyright © 2018, Juniper Networks, Inc.

 Chapter 4: MICs Supported on MX Series Routers

Table 11: MIC/MPC2 Compatibility (continued)

MIC MPC2E MPC2E MPC2E

Name MPC2 MPC2E NG MPC2 Q MPC2E Q MPC2 EQ EQ MPC2E P NG Q

MC
I -3D-2XGE-XFP 10.2 11.2R4 14.1R4, 10.2 11.2R4 10.2 11.2R4 12.2 14.1R4,
14.2R3 with 14.2R3 with
(“10-Gigabit Junos Junos
Ethernet Continuity Continuity
MIC with
XFP” on 15.1 15.1
page 155)

MC
I -3D-4XGE-XFP 10.1 11.2R4 14.1R4, 10.1 11.2R4 10.1 11.2R4 12.2 14.1R4,
14.2R3 with 14.2R3 with
(“10-Gigabit Junos Junos
Ethernet Continuity Continuity
MICs with
XFP” on 15.1 15.1
page 155)

MC
I -3D-40GE-TX 10.2 11.2R4 14.1R4, 10.2 11.2R4 10.2 11.2R4 12.2 14.1R4,
14.2R3 with 14.2R3 with
(“Tri-Rate Junos Junos
MIC” on Continuity Continuity
page 194)
15.1 15.1

M
CI-3D-4OC3OC2 1O
-1C48, 11.4 11.4 14.1R4, 11.4 11.4 11.4 11.4 - 14.1R4,
M
CI-3D-8OC3OC
2
1-4OC48 14.2R3 with 14.2R3 with
Junos Junos
(“SONET/SDH Continuity Continuity
OC3/STM1
(Multi-Rate) 15.1 15.1
MICs with
SFP” on
page 202)

M
CI-3D-4COC3C
-1OC2
1-CE — — — 12.2 12.2 12.2 12.2 12.2 14.1R4,
14.2R3 with
(“Channelized Junos
OC3/STM1 Continuity
(Multi-Rate)
Circuit 15.1
Emulation
MIC with
SFP” on
page 183)

MC
I -3D-1OC192-XFP 12.2 12.2 14.1R4, 12.2 12.2 12.2 12.2 12.2 14.1R4,
14.2R3 with 14.2R3 with
(“SONET/SDH Junos Junos
OC192/STM64 Continuity Continuity
MIC with
XFP” on 15.1 15.1
page209)

Copyright © 2018, Juniper Networks, Inc. 29

MX Series Interface Module Reference

Table 11: MIC/MPC2 Compatibility (continued)

MIC MPC2E MPC2E MPC2E

Name MPC2 MPC2E NG MPC2 Q MPC2E Q MPC2 EQ EQ MPC2E P NG Q

M
CI-3D-4CHOC3-2CHOC2
1, — — 15.1 with 11.4 11.4 11.4 11.4 — 15.1
M
CI-3D-8CHOC3-4CHOC
2
1 flexible
queuing 14.1R4,
MC
I-4COC3-2COC21-G, option 14.2R3 with
MC
I-8COC3-4COC2
1-G Junos
Continuity
(“Channelized
SONET/SDH
OC3/STM1
(Multi-Rate)
MICs with
SFP” on
page 178)

MC
I-3D-16CHE1-T1-CE 13.2 13.2 15.1 with 12.3 12.3 12.3 12.3 — 14.1R4,
flexible 14.2R3 with
(“Channelized NOTE:Suppo tr NOTE:Suppotr queuing Junos
E1/T1 for for option Continuity
Circuit Non-Channze
id
l Non-Channze
ild
Emulation MIC MIC 15.1
MIC” on only. only.
page 188)

MC
I -3D-8DS3-E3, 11.4 11.4 14.1R4, 11.4 11.4 11.4 11.4 12.2 14.1R4,
MC
I-3D-8CHDS3-E3-B 14.2R3 with 14.2R3 with
Junos Junos
(“DS3/E3 Continuity Continuity
MIC” on
page 143) 15.1 15.1

NOTE: You
cannot
run
Channelized
DS3
(MC
I-3D-8CHDS3-E3)
on non-Q
MPCs.
Channelized
DS3 is
supported
only on Q
and
EQ-based
MPCs.

30 Copyright © 2018, Juniper Networks, Inc.

 Chapter 4: MICs Supported on MX Series Routers

Table 11: MIC/MPC2 Compatibility (continued)

MIC MPC2E MPC2E MPC2E

Name MPC2 MPC2E NG MPC2 Q MPC2E Q MPC2 EQ EQ MPC2E P NG Q

MS-MIC-16G 13.2 13.2 14.1R4, 13.2 13.2 13.2 13.2 13.2 14.1R4,
14.2R3 with 14.2R3 with
(“Multiservices Junos Junos
MIC” on Continuity Continuity
page200)
15.1 15.1
NOTE: Only
one
MS-MIC-16G
can be
installed
into any
MPC.

Table 12: MIC/MPC3 Compatibility

MIC Name MPC3E MPC3E NG MPC3E NG Q

MIC-3D-8OC3-2OC12-ATM — 14.1R4, 14.2R3 with Junos 14.1R4, 14.2R3 with Junos

Continuity Continuity
(“ATM MIC with SFP” on page 140)
15.1 15.1

MIC-3D-20GE-SFP 12.1 14.1R4, 14.2R3 with Junos 14.1R4, 14.2R3 with Junos
Continuity Continuity
(“Gigabit Ethernet MIC with SFP” on page 147)
15.1 15.1

MIC-3D-20GE-SFP-E 13.2R2 14.1R4, 14.2R3 with Junos 14.1R4, 14.2R3 with Junos
Continuity Continuity
(“Gigabit Ethernet MIC with SFP (E)” on page 150)
15.1 15.1

MIC3-3D-1X100GE-CFP 12.1 14.1R4, 14.2R3 with Junos 14.1R4, 14.2R3 with Junos
Continuity Continuity
(“100-Gigabit Ethernet MIC with CFP” on page 163)
15.1 15.1

MIC-3D-2XGE-XFP 12.2 14.1R4, 14.2R3 with Junos 14.1R4, 14.2R3 with Junos
Continuity Continuity
(“10-Gigabit Ethernet MICs with XFP” on page 155)
15.1 15.1

MIC-3D-4XGE-XFP — 14.1R4, 14.2R3 with Junos 14.1R4, 14.2R3 with Junos

Continuity Continuity
(“10-Gigabit Ethernet MICs with XFP” on page 155)
15.1 15.1

MIC3-3D-10XGE-SFPP 12.3 14.1R4, 14.2 R3 and Junos 14.1R4, 14.2R3 with Junos
Continuity Continuity
(“10-Gigabit Ethernet MIC with SFP+ (10 Ports)” on
page 157) 15.1 15.1

Copyright © 2018, Juniper Networks, Inc. 31

MX Series Interface Module Reference

Table 12: MIC/MPC3 Compatibility (continued)

MIC Name MPC3E MPC3E NG MPC3E NG Q

MIC3-3D-2X40GE-QSFPP 12.2 14.1R4, 14.2R3 with Junos 14.1R4, 14.2R3 with Junos
Continuity Continuity
(“40-Gigabit Ethernet MIC with QSFP+” on page 162)
15.1 15.1

MIC3-3D-1X100GE-CXP 12.2 14.1R4, 14.2R3 with Junos 14.1R4, 14.2R3 with Junos
Continuity Continuity
(“100-Gigabit Ethernet MIC with CXP” on page 165)
15.1 15.1

MIC3-100G-DWDM 15.1F5 15.1F5 15.1F5

15.1F6 15.1F6 15.1F6
(“100-Gigabit DWDM OTN MIC with CFP2-ACO” on 17.1R1 17.1R1 17.1R1
page 169)

MIC-3D-4OC3OC12-1OC48 13.3 14.1R4, 14.2R3 with Junos 14.1R4, 14.2R3 with Junos
Continuity Continuity
MIC-3D-8OC3OC12-4OC48
15.1 15.1
(“SONET/SDH OC3/STM1 (Multi-Rate) MICs with
SFP” on page 202)

MIC-3D-1OC192-XFP 13.3 14.1R4, 14.2R3 with Junos 14.1R4, 14.2R3 with Junos
Continuity Continuity
(“SONET/SDH OC192/STM64 MIC with XFP” on
page 209) 15.1 15.1

MIC-3D-4COC3-1COC12-CE — — 14.1R4, 14.2R3 with Junos

Continuity
(“Channelized OC3/STM1 (Multi-Rate) Circuit
Emulation MIC with SFP” on page 183) 15.1

MIC-3D-16CHE1-T1-CE — 15.1 with flexible queuing 15.1

option
(“Channelized E1/T1 Circuit Emulation MIC” on
page 188)

MS-MIC-16G 13.2R2 14.1R4, 14.2R3 with Junos 14.1R4, 14.2R3 with Junos
Continuity Continuity
(“Multiservices MIC” on page 200)
15.1 15.1
NOTE: On MPC3E, the installation of the
Multiservices MIC (MS-MIC-16G) with
MIC3-3D-2X40GE-QSFPP, MIC3-3D-10XGE-SFPP,
or MIC3-3D-1X100GE-CFP does not meet the NEBS
criteria.

NOTE: Only one MS-MIC-16G can be installed into

any MPC.

MIC-3D-40GE-TX — 14.1R4, 14.2R3 with Junos 14.1R4, 14.2R3 with Junos

“Tri-Rate MIC” on page 194 Continuity Continuity

15.1 15.1

32 Copyright © 2018, Juniper Networks, Inc.

 Chapter 4: MICs Supported on MX Series Routers

Table 12: MIC/MPC3 Compatibility (continued)

MIC Name MPC3E MPC3E NG MPC3E NG Q

MIC-3D-4OC3OC12-1OC48, 12.1 14.1R4, 14.2R3 with Junos 14.1R4, 14.2R3 with Junos
MIC-3D-8OC3OC12-4OC48 Continuity Continuity
“SONET/SDH OC3/STM1 (Multi-Rate) MICs with
SFP” on page 202 15.1 15.1

MIC-3D-4CHOC3-2CHOC12, — 15.1 with flexible queuing 14.1R4, 14.2R3 with Junos

MIC-3D-8CHOC3-4CHOC12 option Continuity
MIC-4COC3-2COC12-G, MIC-8COC3-4COC12-G
“Channelized SONET/SDH OC3/STM1 (Multi-Rate) 15.1
MICs with SFP” on page 178

MIC-3D-8DS3-E3, MIC-3D-8CHDS3-E3-B 12.1 14.1R4, 14.2R3 with Junos 14.1R4, 14.2R3 with Junos
“DS3/E3 MIC” on page 143 Continuity Continuity

NOTE: You cannot run Channelized DS3 15.1 15.1

(MIC-3D-8CHDS3-E3) on non-Q MPCs. Channelized
DS3 is supported only on Q and EQ-based MPCs.

Table 13: MIC/MPC6 Compatibility

MIC Name MPC6E

MIC6-10G 13.3R2

“10-Gigabit Ethernet MIC with SFP+ (24 Ports)” on page 159

MIC6-10G-OTN 13.3R3

“10-Gigabit Ethernet OTN MIC with SFP+ (24 Ports)” on page 160

MIC6-100G-CXP 13.3R2

“100-Gigabit Ethernet MIC with CXP (4 Ports)” on page 166

MIC6-100G-CFP2 13.3R3

“100-Gigabit Ethernet MIC with CFP2” on page 167

Table 14: MIC/MPC8 Compatibility

MIC Name MPC8E

MIC-MRATE • 15.1F5 with Junos Continuity

• 16.1R1
“MIC MRATE” on page 198

MIC-MACSEC-MRATE 17.4

“Multi-Rate Ethernet MIC” on page 206

Copyright © 2018, Juniper Networks, Inc. 33

MX Series Interface Module Reference

Table 15: MIC/MPC9 Compatibility

MIC Name MPC9E

MIC-MRATE • 15.1F5 with Junos Continuity

• 16.1R1
“MIC MRATE” on page 198

MIC-MACSEC-MRATE 17.4

“Multi-Rate Ethernet MIC” on page 206

Table 16: MIC/MPC10003 Compatibility

MIC Name MPC10003

JNP-MIC1 17.3

“Multi-Rate Ethernet MIC” on page 206

JNP-MIC1-MACSEC 17.3R2

“Multi-Rate Ethernet MIC” on page 206

Related • MICs Supported by MX Series Routers on page 18

Documentation
• Junos Continuity Software User Guide (Junos OS Release 14.1R4 and Later Releases)

34 Copyright © 2018, Juniper Networks, Inc.

CHAPTER 5

FPCs and PICs Supported on MX Series

Routers

• MX Series FPC and PIC Overview on page 35

• High Availability Features on page 36
• FPCs Supported by MX240, MX480, and MX960 Routers on page 36
• PICs Supported by MX240, MX480, and MX960 Routers on page 37

MX Series FPC and PIC Overview

Flexible PIC Concentrators (FPCs) and Physical Interface Cards (PICs) function similarly
to MICs and MPCs. PICs provide physical interfaces for the router and install into FPCs
which provide packet forwarding services. Each FPC supports up to two Physical Interface
Cards (PICs). You can install PICs of different media types on the same router as long
as the router supports those PICs.

PICs receive incoming packets from the network and transmit outgoing packets to the
network. During this process, each PIC performs framing and high-speed signaling for its
media type. Before transmitting outgoing data packets, the PICs encapsulate the packets
received. Each PIC is equipped with a media-specific ASIC that performs control functions
tailored to the PIC's media type.

An FPC occupies two Dense Port Concentrator (DPC) slots on an MX Series router. FPCs
install vertically in the MX960 router chassis, and horizontally in the MX480 and MX240
router chassis. The maximum number of supported FPCs varies per router:

• MX960 router—6 FPCs

• MX480 router—3 FPCs

• MX240 router—1 FPC

MX240, MX480, and MX960 3D Universal Edge Routers support 2 PICs per FPC. The
maximum number of supported PICs varies per router:

• MX960 router—12 PICs

• MX480 router—6 PICs

• MX240 router—2 PICs

Copyright © 2018, Juniper Networks, Inc. 35

MX Series Interface Module Reference

Blank PICs resemble other PICs but do not provide any physical connection or activity.
When a slot is not occupied by a PIC, you must insert a blank PIC to fill the empty slot
and ensure proper cooling of the system.

Related • High Availability Features on page 36

Documentation
• FPCs Supported by MX240, MX480, and MX960 Routers on page 36

• PICs Supported by MX240, MX480, and MX960 Routers on page 37

High Availability Features

High availability features include Routing Engine redundancy, graceful Routing Engine
switchover (GRES), nonstop bridging, nonstop active routing, graceful restart for routing
protocols, Virtual Router Redundancy Protocol (VRRP), and unified in-service software
upgrade (ISSU). Some high availability features are not supported by all platforms and
all PICs. For more information, see theUnified ISSU System Requirements in the Junos OS
High Availability Library for Routing Devices.

Related • MX Series FPC and PIC Overview on page 35

Documentation
• FPCs Supported by MX240, MX480, and MX960 Routers on page 36

• PICs Supported by MX240, MX480, and MX960 Routers on page 37

FPCs Supported by MX240, MX480, and MX960 Routers

An FPC occupies two slots when installed in an MX240, MX480, or MX960 router. The
maximum number of supported FPCs varies per router:

• MX960 router—6 FPCs

• MX480 router—3 FPCs

• MX240 router—1 FPC

Table 17 on page 36 lists FPCs supported by MX Series routers.

Table 17: FPCs Supported by MX Series Routers

Maximum Maximum
Number of PICs Throughput per FPC First Junos OS
FPC Type FPC Name FPC Model Number Supported (Full-duplex) Release

3 FPC3 MX-FPC3 2 20 Gbps 9.4

2 FPC2 MX-FPC2 2 10 Gbps 9.5

Related • MX Series FPC and PIC Overview on page 35

Documentation
• PICs Supported by MX240, MX480, and MX960 Routers on page 37

36 Copyright © 2018, Juniper Networks, Inc.

 Chapter 5: FPCs and PICs Supported on MX Series Routers

• High Availability Features on page 36

PICs Supported by MX240, MX480, and MX960 Routers

Table 18 on page 37 lists the PICs supported by MX240, MX480, and MX960 routers.

Table 18: PICs Supported by MX240, MX480, and MX960 Routers

PIC Name PIC Model Number Ports Type First Junos OS Release

Channelized IQ PICs
“Channelized OC12/STM4 Enhanced PB-4CHOC12-STM4-IQE-SFP 4 2 9.5
IQ (IQE) PIC with SFP” on page 213

“Channelized OC48/STM16 PB-1CHOC48-STM16-IQE 1 2 9.5

Enhanced IQ (IQE) PIC with SFP” on
page 214

SONET/SDH PICs
“SONET/SDH OC3/STM1 PB-4OC3-1OC12-SON2-SFP 4 2 9.5
(Multi-Rate) PIC with SFP” on
page 220

“SONET/SDH OC12/STM4 PB-4OC3-4OC12-SON-SFP 4 2 9.5

(Multi-Rate) PIC with SFP” on
page 223

“SONET/SDH OC48/STM16 PC-4OC48-STM16-IQE-SFP 4 3 10.4R2

Enhanced IQ (IQE) PIC with SFP” on
page 226

“SONET/SDH OC48/STM16 PB-1OC48-SON-B-SFP 1 2 9.5

(Multi-Rate) PIC with SFP” on
page 230

“SONET/SDH OC48/STM16 PIC with PC-4OC48-SON-SFP 4 3 9.4

SFP” on page 233

“SONET/SDH OC192c/STM64 PIC” PC-1OC192-SON-VSR 1 3 9.4

on page 236

“SONET/SDH OC192c/STM64 PIC PC-1OC192-SON-XFP 1 3 9.4

with XFP” on page 239

Related • MX Series FPC and PIC Overview on page 35

Documentation
• FPCs Supported by MX240, MX480, and MX960 Routers on page 36

• High Availability Features on page 36

Copyright © 2018, Juniper Networks, Inc. 37

MX Series Interface Module Reference

38 Copyright © 2018, Juniper Networks, Inc.

CHAPTER 6

Network Interface Specifications

• Determining Transceiver Support and Specifications on page 39

• Cable and Connector Specifications for MX Series and PTX Series Devices on page 40

Determining Transceiver Support and Specifications

You can find information about the pluggable transceivers supported on your Juniper
Networks device by using the Hardware Compatibility Tool. In addition to transceiver
and connector type, the optical and cable characteristics—where applicable—are
documented for each transceiver. The Hardware Compatibility Tool allows you to search
by product, displaying all the transceivers supported on that device, or category, displaying
all the transceivers by interface speed or type. The Hardware Compatibility Tool is located
at https://pathfinder.juniper.net/hct/.

Some transceivers support additional monitoring using the operational mode CLI
command show interfaces diagnostics optics. Use the Hardware Compatibility Tool to
determine if your transceiver supports monitoring. See the Junos OS documentation for
your device for a description of the monitoring fields.

CAUTION: If you face a problem running a Juniper Networks device that uses
a third-party optic or cable, the Juniper Networks Technical Assistance Center
(JTAC) can help you diagnose the source of the problem. Your JTAC engineer
might recommend that you check the third-party optic or cable and potentially
replace it with an equivalent Juniper Networks optic or cable that is qualified
for the device.

Related • show interfaces diagnostics optics (Gigabit Ethernet, 10-Gigabit Ethernet, 40-Gigabit
Documentation Ethernet, 100-Gigabit Ethernet, and Virtual Chassis Port)

• show interfaces diagnostics optics (SONET)

• show interfaces diagnostics optics

• show interfaces diagnostics optics

• show interfaces diagnostics optics

Copyright © 2018, Juniper Networks, Inc. 39

MX Series Interface Module Reference

Cable and Connector Specifications for MX Series and PTX Series Devices

The transceivers that are supported on MX Series and PTX Series devices use fiber-optic
cables and connectors. The type of connector and the type of fiber depends on the
transceiver type.

You can determine the type of cable and connector required for your specific transceiver
by using the Hardware Compatibility Tool.

CAUTION: To maintain agency approvals, use only a properly constructed,

shielded cable.

NOTE: The terms multifiber push-on (MPO) and multifiber termination

push-on (MTP) describe the same connector type. The rest of this topic uses
MPO to mean MPO or MTP.

The following sections provide details about different cable and connector types:

• 12-Fiber MPO Connectors on page 40

• 24-Fiber MPO Connectors on page 44
• LC Duplex Connectors on page 45

12-Fiber MPO Connectors

There are two types of cables used with 12-fiber MPO connectors on Juniper Networks
devices—patch cables with MPO connectors on both ends, and breakout cables with an
MPO connector on one end and four LC duplex connectors on the opposite end. Depending
on the application, the cables might use single-mode fiber (SMF) or multimode fiber
(MMF). Juniper Networks sells cables that meet the supported transceiver requirements,
but it is not required to purchase cables from Juniper Networks.

Ensure that you order cables with the correct polarity. Vendors refer to these crossover
cables as key up to key up, latch up to latch up, Type B, or Method B. If you are using patch
panels between two transceivers, ensure that the proper polarity is maintained through
the cable plant.

Also, ensure that the fiber end in the connector is finished correctly. Physical contact
(PC) refers to fiber that has been polished flat. Angled physical contact (APC) refers to
fiber that has been polished at an angle. Ultra physical contact (UPC) refers to fiber that
has been polished flat, to a finer finish. The required fiber end is listed with the connector
type in the Hardware Compatibility Tool.

• 12-Fiber Ribbon Patch Cables with MPO Connectors on page 41

• 12-Fiber Ribbon Breakout Cables with MPO-to-LC Duplex Connectors on page 42
• 12-Ribbon Patch and Breakout Cables Available from Juniper Networks on page 43

40 Copyright © 2018, Juniper Networks, Inc.

 Chapter 6: Network Interface Specifications

12-Fiber Ribbon Patch Cables with MPO Connectors

You can use 12-ribbon patch cables with female MPO connectors to connect two
transceivers of the same type—for example, 40GBASE-SR4-to-40GBASESR4 or
100GBASE-SR4-to-100GBASE-SR4. You can also connect 4x10GBASE-LR or
4x10GBASE-SR transceivers by using patch cables—for example,
4x10GBASE-LR-to-4x10GBASE-LR or 4x10GBASE-SR-to-4x10GBASE-SR—instead of
breaking the signal out into four separate signals.

Table 19 on page 41 describes the signals on each fiber. Table 20 on page 41 shows the
pin-to-pin connections for proper polarity.

Table 19: Cable Signals for 12-Fiber Ribbon Patch Cables

Fiber Signal

1 Tx0 (Transmit)

2 Tx1 (Transmit)

3 Tx2 (Transmit)

4 Tx3 (Transmit)

5 Unused

6 Unused

7 Unused

8 Unused

9 Rx3 (Receive)

10 Rx2 (Receive)

11 Rx1 (Receive)

12 Rx0 (Receive)

Table 20: Cable Pinouts for 12-Fiber Ribbon Patch Cables

MPO Pin MPO Pin

1 12

2 11

3 10

Copyright © 2018, Juniper Networks, Inc. 41

MX Series Interface Module Reference

Table 20: Cable Pinouts for 12-Fiber Ribbon Patch Cables (continued)

MPO Pin MPO Pin

4 9

5 8

6 7

7 6

8 5

9 4

10 3

11 2

12 1

12-Fiber Ribbon Breakout Cables with MPO-to-LC Duplex Connectors

You can use 12-fiber ribbon breakout cables with MPO-to-LC duplex connectors to
connect a QSFP+ transceiver to four separate SFP+ transceivers—for example,
4x10GBASE-LR-to-10GBASE-LR or 4x10GBASE-SR-to-10GBASE-SR SFP+ transceivers.
The breakout cable is constructed out of a 12-fiber ribbon fiber-optic cable. The ribbon
cable splits from a single cable with a female MPO connector on one end, into four cable
pairs with four LC duplex connectors on the opposite end.

Table 21 on page 42 describes the way the fibers are connected between the MPO and
LC duplex connectors. The cable signals are the same as those described in
Table 19 on page 41.

Table 21: Cable Pinouts for 12-Fiber Ribbon Breakout Cables

MPO Connector Pin LC Duplex Connector Pin

1 Tx on LC Duplex 1

2 Tx on LC Duplex 2

3 Tx on LC Duplex 3

4 Tx on LC Duplex 4

5 Unused

6 Unused

42 Copyright © 2018, Juniper Networks, Inc.

 Chapter 6: Network Interface Specifications

Table 21: Cable Pinouts for 12-Fiber Ribbon Breakout Cables (continued)

MPO Connector Pin LC Duplex Connector Pin

7 Unused

8 Unused

9 Rx on LC Duplex 4

10 Rx on LC Duplex 3

11 Rx on LC Duplex 2

12 Rx on LC Duplex 1

12-Ribbon Patch and Breakout Cables Available from Juniper Networks

Juniper Networks sells 12-ribbon patch and breakout cables with MPO connectors that
meet the requirements described above. It is not required to purchase cables from Juniper
Networks. Table 22 on page 43 describes the available cables.

Table 22: 12-Ribbon Patch and Breakout Cables Available from Juniper Networks

Cable Fiber
Type Connector Type Type Cable Length Juniper Model Number

12-ribbon Female MPO/PC to MMF 1m MTP12-FF-M1M

patch female MPO/PC, key (OM3)
up to key up
3m MTP12-FF-M3M

5m MTP12-FF-M5M

10 m MTP12-FF-M10M

Female MPO/APC to SMF 1m MTP12-FF-S1M

female MPO/APC, key
up to key up
3m MTP12-FF-S3M

5m MTP12-FF-S5M

10 m MTP12-FF-S10M

Copyright © 2018, Juniper Networks, Inc. 43

MX Series Interface Module Reference

Table 22: 12-Ribbon Patch and Breakout Cables Available from Juniper Networks (continued)

Cable Fiber
Type Connector Type Type Cable Length Juniper Model Number

12-ribbon Female MPO/PC, key MMF 1m MTP-4LC-M1M

breakout up, to four LC/UPC (OM3)
duplex
3m MTP-4LC-M3M

5m MTP-4LC-M5M

10 m MTP-4LC-M10M

Female MPO/APC, key SMF 1m MTP-4LC-S1M

up, to four LC/UPC
duplex
3m MTP-4LC-S3M

5m MTP-4LC-S5M

10 m MTP-4LC-S10M

24-Fiber MPO Connectors

You can use patch cables with 24-fiber MPO connectors to connect two supported
transceivers of the same type—for example, 100GBASE-SR10-to-100GBASE-SR10.

Figure 1 on page 44 shows the 24-fiber MPO optical lane assignments.

Figure 1: 24-Fiber MPO Optical Lane Assignments

NOTE: Ensure that you order cables with the correct polarity. Vendors refer
to these crossover cables as key up to key up, latch up to latch up, Type B, or
Method B. If you are using patch panels between two transceivers, ensure
that the proper polarity is maintained through the cable plant.

The MPO optical connector for the CFP2-100G-SR10-D3 is defined in Section 5.6 of the
CFP2 Hardware Specification and Section 88.10.3 of IEEE STD 802.3-2012. These
specifications include the following requirements:

• Recommended Option A in IEEE STD 802.3-2012 is required.

• The transceiver receptacle is male. A patch cable with female connector is required
to mate with the module.

44 Copyright © 2018, Juniper Networks, Inc.

 Chapter 6: Network Interface Specifications

• Ferrule finish shall be flat polished interface that is compliant with IEC 61754-7.

• Alignment key is key up.

The optical interface must meet the requirement FT-1435-CORE in Generic Requirements
for Multi-Fiber Optical Connectors. The module must pass wiggle test defined by IEC
62150-3.

LC Duplex Connectors
You can use patch cables with LC duplex connectors to connect two supported
transceivers of the same type—for example, 40GBASE-LR4-to-40GBASE-LR4 or
100GBASE-LR4-to100GBASE-LR4. The patch cable is one fiber pair with two LC duplex
connectors at opposite ends. LC duplex connectors are also used with 12-fiber ribbon
breakout cables, as described in “12-Fiber Ribbon Breakout Cables with MPO-to-LC
Duplex Connectors” on page 42.

Figure 2 on page 45 shows an LC duplex connector being installed in a transceiver.

Figure 2: LC Duplex Connector

Transceiver
g027016

Fiber-optic cable

Copyright © 2018, Juniper Networks, Inc. 45

MX Series Interface Module Reference

46 Copyright © 2018, Juniper Networks, Inc.

PART 2

DPC, MPC, MIC, and PIC Descriptions

• MX Series DPC Descriptions on page 49
• MX Series MPC Descriptions on page 83
• MX Series MIC Descriptions on page 139
• MX Series PIC Descriptions on page 213

Copyright © 2018, Juniper Networks, Inc. 47

MX Series Interface Module Reference

48 Copyright © 2018, Juniper Networks, Inc.

CHAPTER 7

MX Series DPC Descriptions

• Gigabit Ethernet DPC with SFP on page 50

• Gigabit Ethernet Enhanced DPC with SFP on page 52
• Gigabit Ethernet Enhanced Ethernet Services DPC with SFP on page 54
• Gigabit Ethernet Enhanced Queuing Ethernet Services DPC with SFP on page 56
• Gigabit Ethernet Enhanced Queuing IP Services DPCs with SFP on page 58
• 10-Gigabit Ethernet DPC with XFP on page 61
• 10-Gigabit Ethernet Enhanced DPCs with XFP on page 63
• 10-Gigabit Ethernet Enhanced Ethernet Services DPC with XFP on page 65
• 10-Gigabit Ethernet Enhanced Queuing Ethernet Services DPC with XFP on page 67
• 10-Gigabit Ethernet Enhanced Queuing IP Services DPC with XFP on page 69
• Multi-Rate Ethernet Enhanced DPC with SFP and XFP on page 71
• Multi-Rate Ethernet Enhanced Ethernet Services DPC with SFP and XFP on page 73
• Multi-Rate Ethernet Enhanced Queuing IP Services DPC with SFP and XFP on page 75
• Multiservices DPC on page 77
• Tri-Rate Enhanced DPC on page 79
• Tri-Rate Enhanced Ethernet Services DPC on page 81

Copyright © 2018, Juniper Networks, Inc. 49

MX Series Interface Module Reference

Gigabit Ethernet DPC with SFP

Software release • Junos OS Release 8.2 and later

• End-of-life (see notification PSN-2009-06-400)

Description • 40 Gigabit Ethernet ports

• Power requirement: 6.98 A @ 48 V (335 W)
• Weight: 13.1 lb (5.9 kg)
• Supports large Ethernet frame sizes for more efficient throughput across the intra-POP network
• Model number: DPC-R-40GE-SFP
• Name in the CLI: DPC 40x 1GE R

Hardware features • High-performance throughput on each port at speeds up to 1 Gbps

• Autonegotiation between Gigabit Ethernet circuit partners
• Full-duplex mode
• Maximum transmission units (MTUs) of up to 9192 bytes

Software features • Optical diagnostics and related alarms

• See “Protocols and Applications Supported by DPCs and Enhanced DPCs (DPC and DPCE-R)”
on page 297 for information about the protocols and applications that this DPC supports.

Interfaces Syntax: ge-fpc/pic/port where:

• fpc: Slot in the router where the DPC is installed

• pic: 0 (bottom left row of 10 ports), 1 (bottom right row of 10 ports), 2 (top left row of 10 ports),
or 3 (top right row of 10 ports)
• port: 0 through 9

For example, ge-1/3/0 is the interface for port 0 in the top right row of 10 ports on a DPC installed
in slot 1.

50 Copyright © 2018, Juniper Networks, Inc.

 Chapter 7: MX Series DPC Descriptions

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

You can install any transceiver supported by the DPC. For information about installing and removing
transceivers, see the hardware guide for your router.

NOTE: Do not install Gigabit Ethernet SFPs in the SONET/SDH port. The port will not recognize
the SFP.

LEDs OK/FAIL LED, one bicolor:

• Steady green—DPC is functioning normally.

• Blinking green—DPC is transitioning online or offline.
• Red—DPC has failed.

Link LED, one green per port:

• Off—No link.
• On steadily—Link is active.

The Link LEDs are labeled in groups of five:

• 0/0 for 0/0 through 0/4

• 0/5 for 0/5 through 0/9
• 1/0 for 1/0 through 1/4
• 1/5 for 1/5 through 1/9
• 2/0 for 2/0 through 2/4
• 2/5 for 2/5 through 2/9
• 3/0 for 3/0 through 3/4
• 3/5 for 3/5 through 3/9

Related • MX Series DPC Overview on page 7

Documentation
• DPCs Supported on MX240, MX480, and MX960 Routers on page 8

Copyright © 2018, Juniper Networks, Inc. 51

MX Series Interface Module Reference

Gigabit Ethernet Enhanced DPC with SFP

Software release • Junos OS Release 8.4 and later

Description • 40 Gigabit Ethernet ports

• Power requirement: 6.98 A @ 48 V (335 W)
• Weight: 13.1 lb (5.9 kg)
• Supports large Ethernet frame sizes for more efficient throughput across the intra-POP network
• Model number: DPCE-R-40GE-SFP
• Name in the CLI: DPCE 40x 1GE R

Hardware features • High-performance throughput on each port at speeds up to 1 Gbps

• Autonegotiation between Gigabit Ethernet circuit partners
• Full-duplex mode
• Maximum transmission units (MTUs) of up to 9192 bytes
• Enhanced ASICs for increased performance and scalability of Layer 2 features

Software features • Optical diagnostics and related alarms

• See “Protocols and Applications Supported by DPCs and Enhanced DPCs (DPC and DPCE-R)”
on page 297 for information about the protocols and applications that this DPC supports.

52 Copyright © 2018, Juniper Networks, Inc.

 Chapter 7: MX Series DPC Descriptions

Interfaces Syntax: ge-fpc/pic/port where:

• fpc: Slot in the router where the DPC is installed

• pic: 0 (bottom left row of 10 ports), 1 (bottom right row of 10 ports), 2 (top left row of 10 ports),
or 3 (top right row of 10 ports) when installed horizontally
• port: 0 through 9

For example, ge-1/3/0 is the interface for port 0 in the top right row of 10 ports on a DPC installed
in slot 1.

For information on the interface numbering, see the DPC Port and Interface Numbering topic for
the respective MX router.

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

You can install any transceiver supported by the DPC. For information about installing and removing
transceivers, see the hardware guide for your router.

NOTE: Do not install Gigabit Ethernet SFPs in the SONET/SDH port. The port will not recognize
the SFP.

LEDs OK/FAIL LED, one bicolor:

• Steady green—DPC is functioning normally.

• Blinking green—DPC is transitioning online or offline.
• Red—DPC has failed.

Link LED, one green per port:

• Off—No link.
• On steadily—Link is active.

The Link LEDs are labeled in groups of five:

• 0/0 for 0/0 through 0/4

• 0/5 for 0/5 through 0/9
• 1/0 for 1/0 through 1/4
• 1/5 for 1/5 through 1/9
• 2/0 for 2/0 through 2/4
• 2/5 for 2/5 through 2/9
• 3/0 for 3/0 through 3/4
• 3/5 for 3/5 through 3/9

Related • MX Series DPC Overview on page 7

Documentation
• DPCs Supported on MX240, MX480, and MX960 Routers on page 8

Copyright © 2018, Juniper Networks, Inc. 53

MX Series Interface Module Reference

Gigabit Ethernet Enhanced Ethernet Services DPC with SFP

Software release • Junos OS Release 8.4 and later

Description • 40 Gigabit Ethernet ports

• Power requirement: 6.98 A @ 48 V (335 W)
• Weight: 13.1 lb (5.9 kg)
• Supports large Ethernet frame sizes for more efficient throughput across the intra-POP network
• Model number: DPCE-X-40GE-SFP
• Name in the CLI: DPCE 40x 1GE X

Hardware features • High-performance throughput on each port at speeds up to 1 Gbps

• Autonegotiation between Gigabit Ethernet circuit partners
• Full-duplex mode
• Maximum transmission units (MTUs) of up to 9192 bytes
• Enhanced ASICs for increased performance and scalability of Layer 2 features

Software features • Optical diagnostics and related alarms

• See “Protocols and Applications Supported by Enhanced Ethernet Services DPCs (DPCE-X)”
on page 303 for information about the protocols and applications that this DPC supports.

NOTE: The routing table is limited to 32,000 IP routes. This limitation applies to any manner in
which the routes are learned, such as OSPF, RIP, and so on. The DPC supports BGP for L2 VPNs
only.

54 Copyright © 2018, Juniper Networks, Inc.

 Chapter 7: MX Series DPC Descriptions

Interfaces Syntax: ge-fpc/pic/port where:

• fpc: Slot in the router where the DPC is installed

• pic: 0 (bottom left row of 10 ports), 1 (bottom right row of 10 ports), 2 (top left row of 10 ports),
or 3 (top right row of 10 ports)
• port: 0 through 9

For example, ge-1/3/0 is the interface for port 0 in the top right row of 10 ports on a DPC installed
in slot 1.

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

You can install any transceiver supported by the DPC. For information about installing and removing
transceivers, see the hardware guide for your router.

NOTE: Do not install Gigabit Ethernet SFPs in the SONET/SDH port. The port will not recognize
the SFP.

LEDs OK/FAIL LED, one bicolor:

• Steady green—DPC is functioning normally.

• Blinking green—DPC is transitioning online or offline.
• Red—DPC has failed.

Link LED, one green per port:

• Off—No link.
• On steadily—Link is active.

The Link LEDs are labeled in groups of five:

• 0/0 for 0/0 through 0/4

• 0/5 for 0/5 through 0/9
• 1/0 for 1/0 through 1/4
• 1/5 for 1/5 through 1/9
• 2/0 for 2/0 through 2/4
• 2/5 for 2/5 through 2/9
• 3/0 for 3/0 through 3/4
• 3/5 for 3/5 through 3/9

Related • MX Series DPC Overview on page 7

Documentation
• DPCs Supported on MX240, MX480, and MX960 Routers on page 8

Copyright © 2018, Juniper Networks, Inc. 55

MX Series Interface Module Reference

Gigabit Ethernet Enhanced Queuing Ethernet Services DPC with SFP

Software release • Junos OS Release 8.5 and later

Description • 40 Gigabit Ethernet ports

• Power requirement: 7.6 A @ 48 V (365 W)
• Weight: 13.1 lb (5.9 kg)
• Supports large Ethernet frame sizes for more efficient throughput across the intra-POP network
• Model number: DPCE-X-Q-40GE-SFP
• Name in the CLI: DPCE 40x 1GE X EQ

Hardware features • High-performance throughput on each port at speeds up to 1 Gbps

• Autonegotiation between Gigabit Ethernet circuit partners
• Full-duplex mode
• Maximum transmission units (MTUs) of up to 9192 bytes
• Enhanced ASICs for increased performance and scalability of Layer 2 features

Software features • Optical diagnostics and related alarms

• See “Protocols and Applications Supported by Enhanced Queuing Ethernet Services DPCs
(DPCE-X-Q)” on page 312 for information about the protocols and applications that this DPC
supports.

NOTE: The routing table is limited to 32,000 IP routes. This limitation applies to any manner in
which the routes are learned, such as OSPF, RIP, and so on. The DPC supports BGP for L2 VPNs
only.

56 Copyright © 2018, Juniper Networks, Inc.

 Chapter 7: MX Series DPC Descriptions

Interfaces Syntax: ge-fpc/pic/port where:

• fpc: Slot in the router where the DPC is installed

• pic: 0 (bottom left row of 10 ports), 1 (bottom right row of 10 ports), 2 (top left row of 10 ports),
or 3 (top right row of 10 ports)
• port: 0 through 9

For example, ge-1/3/0 is the interface for port 0 in the top right row of 10 ports on a DPC installed
in slot 1.

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

You can install any transceiver supported by the DPC. For information about installing and removing
transceivers, see the hardware guide for your router.

NOTE: Do not install Gigabit Ethernet SFPs in the SONET/SDH port. The port will not recognize
the SFP.

LEDs OK/FAIL LED, one bicolor:

• Steady green—DPC is functioning normally.

• Blinking green—DPC is transitioning online or offline.
• Red—DPC has failed.

Link LED, one green per port:

• Off—No link.
• On steadily—Link is active.

The Link LEDs are labeled in groups of five:

• 0/0 for 0/0 through 0/4

• 0/5 for 0/5 through 0/9
• 1/0 for 1/0 through 1/4
• 1/5 for 1/5 through 1/9
• 2/0 for 2/0 through 2/4
• 2/5 for 2/5 through 2/9
• 3/0 for 3/0 through 3/4
• 3/5 for 3/5 through 3/9

Related • MX Series DPC Overview on page 7

Documentation
• DPCs Supported on MX240, MX480, and MX960 Routers on page 8

Copyright © 2018, Juniper Networks, Inc. 57

MX Series Interface Module Reference

Gigabit Ethernet Enhanced Queuing IP Services DPCs with SFP

Figure 3: 20-Port Gigabit Ethernet Enhanced Queuing Figure 4: 40-Port Gigabit Ethernet Enhanced Queuing
IP Services DPC with SFP IP Services DPC with SFP

1/0

Software release • 20-port: Junos OS Release 9.1 and later

• 40-port: Junos OS Release 8.5 and later
End-of-life (see notification PSN-2011-07-314)

Description 20-port:

• 20 Gigabit Ethernet ports

• Power requirement: 4.2 A @ 48 V (200 W)
• Weight: 13 lb (5.9 kg)
• Model number: DPCE-R-Q-20GE-SFP
• Name in the CLI: DPCE 20x 1GE R EQ

40-port:

• 40 Gigabit Ethernet ports

• Power requirement: 7.6 A @ 48 V (365 W)
• Weight: 13.1 lb (5.9 kg)
• Model number: DPCE-R-Q-40GE-SFP
• Name in the CLI: DPCE 40x 1GE R EQ

Hardware features • High-performance throughput on each port at speeds up to 1 Gbps

• Autonegotiation between Gigabit Ethernet circuit partners
• Full-duplex mode
• Maximum transmission units (MTUs) of up to 9192 bytes
• Enhanced ASICs for increased performance and scalability of Layer 2 features

58 Copyright © 2018, Juniper Networks, Inc.

 Chapter 7: MX Series DPC Descriptions

Software features • Optical diagnostics and related alarms

• See “Protocols and Applications Supported by Enhanced Queuing IP Services DPCs (DPCE-R-Q)”
on page 307 for information about the protocols and applications that this DPC supports.

Interfaces Syntax: ge-fpc/pic/port where:

• fpc: Slot in the router where the DPC is installed

• pic:
• 20-port: 0 (left row of 10 ports), or 1 (right row of 10 ports)
• 40-port: 0 (bottom left row of 10 ports), 1 (bottom right row of 10 ports), 2 (top left row of
10 ports), or 3 (top right row of 10 ports)

• port: 0 through 9

For example, ge-1/1/0 is the interface for port 0 in the (top for 40-port) right row of 10 ports on a
DPC installed in slot 1.

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

You can install any transceiver supported by the DPC. For information about installing and removing
transceivers, see the hardware guide for your router.

NOTE: Do not install Gigabit Ethernet SFPs in the SONET/SDH port. The port will not recognize
the SFP.

Copyright © 2018, Juniper Networks, Inc. 59

MX Series Interface Module Reference

LEDs OK/FAIL LED, one bicolor:

• Steady green—DPC is functioning normally.

• Blinking green—DPC is transitioning online or offline.
• Red—DPC has failed.

Link LED, one green per port:

• Off—No link.
• On steadily—Link is active.

The Link LEDs are labeled in groups of five:

• 20-port:
• 0/0 for 0/0 through 0/4
• 0/5 for 0/5 through 0/9
• 1/0 for 1/0 through 1/4
• 1/5 for 1/5 through 1/9

• 40-port:
• 0/0 for 0/0 through 0/4
• 0/5 for 0/5 through 0/9
• 1/0 for 1/0 through 1/4
• 1/5 for 1/5 through 1/9
• 2/0 for 2/0 through 2/4
• 2/5 for 2/5 through 2/9
• 3/0 for 3/0 through 3/4
• 3/5 for 3/5 through 3/9

60 Copyright © 2018, Juniper Networks, Inc.

 Chapter 7: MX Series DPC Descriptions

Related • MX Series DPC Overview on page 7

Documentation
• DPCs Supported on MX240, MX480, and MX960 Routers on page 8

10-Gigabit Ethernet DPC with XFP

Software release • Junos OS Release 8.2 and later

• End-of-life (see notification PSN-2009-06-400)

Description • Four 10-Gigabit Ethernet ports

• Power requirement: 6.46 A @ 48 V (310 W)
• Weight: 13.1 lb (5.9 kg)
• Model number: DPC-R-4XGE-XFP
• Name in the CLI: DPC 4x 10GE R

Hardware features • High-performance throughput on each port at speeds up to 10 Gbps

• WAN-PHY mode at 9.953 Gbps
• LAN-PHY mode at 10.3125 Gbps
• Full-duplex mode
• Maximum transmission units (MTUs) of up to 9192 bytes

Software features • Configurable WAN-PHY mode options

• See “Protocols and Applications Supported by DPCs and Enhanced DPCs (DPC and DPCE-R)”
on page 297 for information about the protocols and applications that this DPC supports.

Copyright © 2018, Juniper Networks, Inc. 61

MX Series Interface Module Reference

Interfaces Syntax: xe-fpc/pic/port where:

• fpc: Slot in the router where the DPC is installed

• pic: 0 through 3
• port: 0

For example, xe-1/3/0 is the interface for the last port on a DPC installed in slot 1.

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

You can install any transceiver supported by the DPC. For information about installing and removing
transceivers, see the hardware guide for your router.

LEDs OK/FAIL LED, one bicolor:

• Steady green—DPC is functioning normally.

• Blinking green—DPC is transitioning online or offline.
• Red—DPC has failed.

TUNNEL LED, one green per port:

• Off—Normal operating mode.

• On steadily—Port configured in tunnel mode.

LINK LED, one green per port:

• Off—No link.
• On steadily—Link is active.

The TUNNEL and LINK LEDs are labeled top to bottom 0/0 through 3/0.

Related • MX Series DPC Overview on page 7

Documentation
• DPCs Supported on MX240, MX480, and MX960 Routers on page 8

62 Copyright © 2018, Juniper Networks, Inc.

 Chapter 7: MX Series DPC Descriptions

10-Gigabit Ethernet Enhanced DPCs with XFP

Figure 5: 2-Port 10-Gigabit Ethernet Enhanced DPC Figure 6: 4-Port 10-Gigabit Ethernet Enhanced DPC
with XFP with XFP

Software release • 2-port: Junos OS Release 9.1 and later

End-of-life (see notification PSN-2011-02-314)
• 4-port: Junos OS Release 8.4 and later

Description 2-port:

• Two 10-Gigabit Ethernet ports

• Power requirement: 3.65 A @ 48 V (175 W)
• Weight: 12 lb (5.4 kg)
• Model number: DPCE-R-2XGE-XFP
• Name in the CLI: DPCE 2x 10GE R

4-port:

• Four 10-Gigabit Ethernet ports

• Power requirement: 6.46 A @ 48 V (310 W)
• Weight: 13.1 lb (5.9 kg)
• Model number: DPCE-R-4XGE-XFP
• Name in the CLI: DPCE 4x 10GE R

Copyright © 2018, Juniper Networks, Inc. 63

MX Series Interface Module Reference

Hardware features • High-performance throughput on each port at speeds up to 10 Gbps

• WAN-PHY mode at 9.953 Gbps
• LAN-PHY mode at 10.3125 Gbps
• Full-duplex mode
• Maximum transmission units (MTUs) of up to 9192 bytes
• Enhanced ASICs for increased performance and scalability of Layer 2 features

Software features • Configurable WAN-PHY mode options

• See “Protocols and Applications Supported by DPCs and Enhanced DPCs (DPC and DPCE-R)”
on page 297 for information about the protocols and applications that these DPCs support.

Interfaces Syntax: xe-fpc/pic/port where:

• fpc: Slot in the router where the DPC is installed

• pic:
• 2-port: 0 or 1
• 4-port: 0 through 3

• port: 0

For example, xe-1/0/0 is the interface for the first port on a DPC installed in slot 1.

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

You can install any transceiver supported by the DPC. For information about installing and removing
transceivers, see the hardware guide for your router.

LEDs OK/FAIL LED, one bicolor:

• Steady green—DPC is functioning normally.

• Blinking green—DPC is transitioning online or offline.
• Red—DPC has failed.

TUNNEL LED, one green per port:

• Off—Normal operating mode.

• On steadily—Port configured in tunnel mode.

LINK LED, one green per port:

• Off—No link.
• On steadily—Link is active.

The TUNNEL and LINK LEDs are labeled top to bottom:

• 2-port: 0/0 through 1/0

• 4-port: 0/0 through 3/0

Related • MX Series DPC Overview on page 7

Documentation
• DPCs Supported on MX240, MX480, and MX960 Routers on page 8

64 Copyright © 2018, Juniper Networks, Inc.

 Chapter 7: MX Series DPC Descriptions

10-Gigabit Ethernet Enhanced Ethernet Services DPC with XFP

Software release • Junos OS Release 8.4 and later

Description • Four 10-Gigabit Ethernet ports

• Power requirement: 6.46 A @ 48 V (310 W)
• Weight: 13.1 lb (5.9 kg)
• Model number: DPCE-X-4XGE-XFP
• Name in the CLI: DPCE 4x 10GE X

Hardware features • High-performance throughput on each port at speeds up to 10 Gbps

• WAN-PHY mode at 9.953 Gbps
• LAN-PHY mode at 10.3125 Gbps
• Full-duplex mode
• Maximum transmission units (MTUs) of up to 9192 bytes
• Enhanced ASICs for increased performance and scalability of Layer 2 features

Software features • Configurable WAN-PHY mode options

• See “Protocols and Applications Supported by Enhanced Ethernet Services DPCs (DPCE-X)”
on page 303 for information about the protocols and applications that this DPC supports.

NOTE: The routing table is limited to 32,000 IP routes. This limitation applies to any manner in
which the routes are learned, such as OSPF, RIP, and so on. The DPC supports BGP for L2 VPNs
only.

Copyright © 2018, Juniper Networks, Inc. 65

MX Series Interface Module Reference

Interfaces Syntax: xe-fpc/pic/port where:

• fpc: Slot in the router where the DPC is installed

• pic: 0 through 3
• port: 0

For example, xe-1/0/0 is the interface for the first port on a DPC installed in slot 1.

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

You can install any transceiver supported by the DPC. For information about installing and removing
transceivers, see the hardware guide for your router.

LEDs OK/FAIL LED, one bicolor:

• Steady green—DPC is functioning normally.

• Blinking green—DPC is transitioning online or offline.
• Red—DPC has failed.

TUNNEL LED, one green per port:

• Off—Normal operating mode.

• On steadily—Port configured in tunnel mode.

LINK LED, one green per port:

• Off—No link.
• On steadily—Link is active.

The TUNNEL and LINK LEDs are labeled top to bottom 0/0 through 3/0.

Related • MX Series DPC Overview on page 7

Documentation
• DPCs Supported on MX240, MX480, and MX960 Routers on page 8

66 Copyright © 2018, Juniper Networks, Inc.

 Chapter 7: MX Series DPC Descriptions

10-Gigabit Ethernet Enhanced Queuing Ethernet Services DPC with XFP

Software release • Junos OS Release 8.5 and later

Description • Four 10-Gigabit Ethernet ports

• Power requirement: 6.87 A @ 48 V (330 W)
• Weight: 13.1 lb (5.9 kg)
• Model number: DPCE-X-Q-4XGE-XFP
• Name in the CLI: DPCE 4x 10GE X EQ

Hardware features • High-performance throughput on each port at speeds up to 10 Gbps

• WAN-PHY mode at 9.953 Gbps
• LAN-PHY mode at 10.3125 Gbps
• Full-duplex mode
• Maximum transmission units (MTUs) of up to 9192 bytes
• Enhanced ASICs for increased performance and scalability of Layer 2 features

Software features • Configurable WAN-PHY mode options

• See “Protocols and Applications Supported by Enhanced Queuing Ethernet Services DPCs
(DPCE-X-Q)” on page 312 for information about the protocols and applications that this DPC
supports.

NOTE: The routing table is limited to 32,000 IP routes. This limitation applies to any manner in
which the routes are learned, such as OSPF, RIP, and so on. The DPC supports BGP for L2 VPNs
only.

Copyright © 2018, Juniper Networks, Inc. 67

MX Series Interface Module Reference

Interfaces Syntax: xe-fpc/pic/port where:

• fpc: Slot in the router where the DPC is installed

• pic: 0 through 3
• port: 0

For example, xe-1/0/0 is the interface for the first port on a DPC installed in slot 1.

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

You can install any transceiver supported by the DPC. For information about installing and removing
transceivers, see the hardware guide for your router.

LEDs OK/FAIL LED, one bicolor:

• Steady green—DPC is functioning normally.

• Blinking green—DPC is transitioning online or offline.
• Red—DPC has failed.

TUNNEL LED, one green per port:

• Off—Normal operating mode.

• On steadily—Port configured in tunnel mode.

LINK LED, one green per port:

• Off—No link.
• On steadily—Link is active.

The TUNNEL and LINK LEDs are labeled top to bottom 0/0 through 3/0.

Related • MX Series DPC Overview on page 7

Documentation
• DPCs Supported on MX240, MX480, and MX960 Routers on page 8

68 Copyright © 2018, Juniper Networks, Inc.

 Chapter 7: MX Series DPC Descriptions

10-Gigabit Ethernet Enhanced Queuing IP Services DPC with XFP

Software release • Junos OS Release 8.5 and later

• End-of-life (see notification PSN-2011-07-314)

Description • Four 10-Gigabit Ethernet ports

• Power requirement: 6.87 A @ 48 V (330 W)
• Weight: 13.1 lb (5.9 kg)
• Model number: DPCE-R-Q-4XGE-XFP
• Name in the CLI: DPCE 4x 10GE R EQ

Hardware features • High-performance throughput on each port at speeds up to 10 Gbps

• WAN-PHY mode at 9.953 Gbps
• LAN-PHY mode at 10.3125 Gbps
• Full-duplex mode
• Maximum transmission units (MTUs) of up to 9192 bytes
• Enhanced ASICs for increased performance and scalability of Layer 2 features

Software features • Configurable WAN-PHY mode options

• See “Protocols and Applications Supported by Enhanced Queuing IP Services DPCs (DPCE-R-Q)”
on page 307 for information about the protocols and applications that this DPC supports.

Interfaces Syntax: xe-fpc/pic/port where:

• fpc: Slot in the router where the DPC is installed

• pic: 0 through 3
• port: 0

For example, xe-1/0/0 is the interface for the first port on a DPC installed in slot 1.

Copyright © 2018, Juniper Networks, Inc. 69

MX Series Interface Module Reference

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

You can install any transceiver supported by the DPC. For information about installing and removing
transceivers, see the hardware guide for your router.

LEDs OK/FAIL LED, one bicolor:

• Steady green—DPC is functioning normally.

• Blinking green—DPC is transitioning online or offline.
• Red—DPC has failed.

TUNNEL LED, one green per port:

• Off—Normal operating mode.

• On steadily—Port configured in tunnel mode.

LINK LED, one green per port:

• Off—No link.
• On steadily—Link is active.

The TUNNEL and LINK LEDs are labeled top to bottom 0/0 through 3/0.

Related • MX Series DPC Overview on page 7

Documentation
• DPCs Supported on MX240, MX480, and MX960 Routers on page 8

70 Copyright © 2018, Juniper Networks, Inc.

 Chapter 7: MX Series DPC Descriptions

Multi-Rate Ethernet Enhanced DPC with SFP and XFP

Software release • Junos OS Release 9.2 and later

Description • 20 Gigabit Ethernet ports

• 2 10-Gigabit Ethernet ports
• Power requirement: 6.94 A @ 48 V (333 W)
• Weight: 13.1 lb (5.9 kg)
• Supports large Ethernet frame sizes for more efficient throughput across the intra-POP network
• Model number: DPCE-R-20GE-2XGE
• Name in the CLI: DPCE 20x 1GE + 2x 10GE R

Hardware features • SFP ports:

• High-performance throughput on each port at speeds up to 1 Gbps

• XFP ports:
• High-performance throughput on each port at speeds up to 10 Gbps
• WAN-PHY mode at 9.953 Gbps
• LAN-PHY mode at 10.3125 Gbps

• Autonegotiation between Gigabit Ethernet circuit partners

• Full-duplex mode
• Maximum transmission units (MTUs) of up to 9192 bytes
• Enhanced ASICs for increased performance and scalability of Layer 2 features

Software features • Configurable WAN-PHY mode options

• Optical diagnostics and related alarms
• See “Protocols and Applications Supported by DPCs and Enhanced DPCs (DPC and DPCE-R)”
on page 297 for information about the protocols and applications that this DPC supports.

Copyright © 2018, Juniper Networks, Inc. 71

MX Series Interface Module Reference

Interfaces Syntax: mediatype-fpc/pic/port where:

• mediatype: ge or xe
• fpc: Slot in the router where the DPC is installed
• pic:
• ge: 0 or 1
• xe: 2 or 3

• port:
• ge: 0 through 9
• xe: 0

For example, xe-1/3/0 is the interface for the port labeled PORT 3/0 on a DPC installed in slot 1.

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

You can install any transceiver supported by the DPC. For information about installing and removing
transceivers, see the hardware guide for your router.

LEDs OK/FAIL LED, one bicolor:

• Steady green—DPC is functioning normally.

• Blinking green—DPC is transitioning online or offline.
• Red—DPC has failed.

LINK LED, one green per port:

• Off—No link.
• On steadily—Link is active.

TUNNEL LED, one green per XFP port:

• Off—Normal operating mode.

• On steadily—Port configured in tunnel mode.

The SFP Link LEDs are labeled in groups of five:

• 0/0 for 0/0 through 0/4

• 0/5 for 0/5 through 0/9
• 1/0 for 1/0 through 1/4
• 1/5 for 1/5 through 1/9

The XFP ports are labeled top to bottom 2/0 and 3/0.

Related • MX Series DPC Overview on page 7

Documentation
• DPCs Supported on MX240, MX480, and MX960 Routers on page 8

72 Copyright © 2018, Juniper Networks, Inc.

 Chapter 7: MX Series DPC Descriptions

Multi-Rate Ethernet Enhanced Ethernet Services DPC with SFP and XFP

Software release • Junos OS Release 9.2 and later

• End-of-life (see notification PSN-2011-07-314)

Description • 20 Gigabit Ethernet ports

• 2 10-Gigabit Ethernet ports
• Power requirement: 6.94 A @ 48 V (333 W)
• Weight: 13.1 lb (5.9 kg)
• Supports large Ethernet frame sizes for more efficient throughput across the intra-POP network
• Model number: DPCE-X-20GE-2XGE
• Name in the CLI: DPCE 20x 1GE + 2x 10GE X

Hardware features • SFP ports:

• High-performance throughput on each port at speeds up to 1 Gbps

• XFP ports:
• High-performance throughput on each port at speeds up to 10 Gbps
• WAN-PHY mode at 9.953 Gbps
• LAN-PHY mode at 10.3125 Gbps

• Full-duplex mode
• Maximum transmission units (MTUs) of up to 9192 bytes
• Enhanced ASICs for increased performance and scalability of Layer 2 features

Software features • Configurable WAN-PHY mode options

• Optical diagnostics and related alarms
• See “Protocols and Applications Supported by Enhanced Ethernet Services DPCs (DPCE-X)”
on page 303 for information about the protocols and applications that this DPC supports.

Copyright © 2018, Juniper Networks, Inc. 73

MX Series Interface Module Reference

Interfaces Syntax: mediatype-fpc/pic/port where:

• mediatype: ge or xe
• fpc: Slot in the router where the DPC is installed
• pic:
• ge: 0 or 1
• xe: 2 or 3

• port:
• ge: 0 through 9
• xe: 0

For example, xe-1/3/0 is the interface for the port labeled PORT 3/0 on a DPC installed in slot 1.

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

You can install any transceiver supported by the DPC. For information about installing and removing
transceivers, see the hardware guide for your router.

LEDs OK/FAIL LED, one bicolor:

• Steady green—DPC is functioning normally.

• Blinking green—DPC is transitioning online or offline.
• Red—DPC has failed.

LINK LED, one green per port:

• Off—No link.
• On steadily—Link is active.

TUNNEL LED, one green per XFP port:

• Off—Normal operating mode.

• On steadily—Port configured in tunnel mode.

The SFP Link LEDs are labeled in groups of five:

• 0/0 for 0/0 through 0/4

• 0/5 for 0/5 through 0/9
• 1/0 for 1/0 through 1/4
• 1/5 for 1/5 through 1/9

The XFP ports are labeled top to bottom 2/0 and 3/0.

Related • MX Series DPC Overview on page 7

Documentation
• DPCs Supported on MX240, MX480, and MX960 Routers on page 8

74 Copyright © 2018, Juniper Networks, Inc.

 Chapter 7: MX Series DPC Descriptions

Multi-Rate Ethernet Enhanced Queuing IP Services DPC with SFP and XFP

Software release • Junos OS Release 9.3 and later

Description • 20 Gigabit Ethernet ports

• 2 10-Gigabit Ethernet ports
• Power requirement: 6.98 A @ 48 V (335 W)
• Weight: 13.1 lb (5.9 kg)
• Supports large Ethernet frame sizes for more efficient throughput across the intra-POP network
• Model number: DPCE-R-Q-20GE-2XGE
• Name in the CLI: DPCE 20x 1GE + 2x 10GE R EQ

Hardware features • SFP ports:

• High-performance throughput on each port at speeds up to 1 Gbps

• XFP ports:
• High-performance throughput on each port at speeds up to 10 Gbps
• WAN-PHY mode at 9.953 Gbps
• LAN-PHY mode at 10.3125 Gbps

• Full-duplex mode
• Maximum transmission units (MTUs) of up to 9192 bytes
• Enhanced ASICs for increased performance and scalability of Layer 2 features

Software features • Configurable WAN-PHY mode options

• Optical diagnostics and related alarms
• See “Protocols and Applications Supported by Enhanced Queuing IP Services DPCs (DPCE-R-Q)”
on page 307 for information about the protocols and applications that this DPC supports.

Copyright © 2018, Juniper Networks, Inc. 75

MX Series Interface Module Reference

Interfaces Syntax: mediatype-fpc/pic/port where:

• mediatype: ge or xe
• fpc: Slot in the router where the DPC is installed
• pic:
• ge: 0 or 1
• xe: 2 or 3

• port:
• ge: 0 through 9
• xe: 0

For example, xe-1/3/0 is the interface for the port labeled PORT 3/0 on a DPC installed in slot 1.

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

You can install any transceiver supported by the DPC. For information about installing and removing
transceivers, see the hardware guide for your router.

LEDs OK/FAIL LED, one bicolor:

• Steady green—DPC is functioning normally.

• Blinking green—DPC is transitioning online or offline.
• Red—DPC has failed.

LINK LED, one green per port:

• Off—No link.
• On steadily—Link is active.

TUNNEL LED, one green per XFP port:

• Off—Normal operating mode.

• On steadily—Port configured in tunnel mode.

The SFP Link LEDs are labeled in groups of five:

• 0/0 for 0/0 through 0/4

• 0/5 for 0/5 through 0/9
• 1/0 for 1/0 through 1/4
• 1/5 for 1/5 through 1/9

The XFP ports are labeled top to bottom 2/0 and 3/0.

Related • MX Series DPC Overview on page 7

Documentation
• DPCs Supported on MX240, MX480, and MX960 Routers on page 8

76 Copyright © 2018, Juniper Networks, Inc.

 Chapter 7: MX Series DPC Descriptions

Multiservices DPC

Software release • Junos OS Release 9.3 and later

Description • Power requirement: 5.52 A @ 48 V (265 W)

• Weight: 14.7 lb (6.7 kg)
• Supports tunnel services. This feature is included with the DPC and does not require an individual
license.
• Individual licenses must be purchased for additional services.
• Supports large Ethernet frame sizes for more efficient throughput across the intra-POP network
• The maximum number of supported MS-DPCs is as follows except where noted in “Protocols
and Applications Supported by the Multiservices DPC (MS-DPC)” on page 317:
• MX240 router: 2
• MX480 router: 4
• MX960 router: 6

• Model number: MS-DPC

Hardware features • Active monitoring on up to 10 million flows

• Maximum transmission units (MTUs) of up to 9192 bytes
• Two Multiservices Processing Units (MSPUs) per DPC, which include two 1.1Ghz multicore
CPUs, each with 4GB of memory for processing integrated services

Software features • Support for up to 12,000 service sets

• See “Protocols and Applications Supported by the Multiservices DPC (MS-DPC)” on page 317
for information about the protocols and applications that this DPC supports.

Copyright © 2018, Juniper Networks, Inc. 77

MX Series Interface Module Reference

Interfaces Syntax: mediatype-fpc/pic/port where:

• mediatype: gr, pc, pd, etc

• fpc: Slot in the router where the MPC is installed
• pic: 0 or 1
• port: 0

NOTE: Port number reflects the internal interface and is not a physical port.

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

• SFPs are not supported.

LEDs OK/FAIL LED, one bicolor:

• Steady green—DPC is functioning normally.

• Blinking green—DPC is transitioning online or offline.
• Red—DPC has failed.

STATUS LED, one tricolor per MSPU:

• Off—MSPU is offline. If both MSPUs are offline it is safe to remove the DPC from the chassis.
• Green—MSPU is operating normally.
• Yellow—MSPU is initializing.
• Red—MSPU has an error or failure.

Application (APP) LED, one tricolor per MSPU:

• Off—Service is not running on the MSPU.

• Green—Service is running on the MSPU under acceptable load.
• Yellow—Service on the MSPU is overloaded.

Related • MX Series DPC Overview on page 7

Documentation
• DPCs Supported on MX240, MX480, and MX960 Routers on page 8

78 Copyright © 2018, Juniper Networks, Inc.

 Chapter 7: MX Series DPC Descriptions

Tri-Rate Enhanced DPC

DPCE-R-40GE-TX
OK/FAIL
0/0 0/1

OK/FAIL
0/2
0/4 0/3 0/5

0/6
0/8 0/7 0/9

DPCE-R-40GE-TX
1/0
1/2 1/1
1/3

Port LEDs 1/4

1/6 1/5 1/7

1/8
2/0 1/9
2/1

2/2
2/4 2/3
2/5

2/6
2/8 2/7
2/9

g003919
3/0
3/2 3/1
3/3

3/4
3/6 3/5
3/7

3/8
SPD: 3/9
G=10
00, Y=10
/100

Software release • Junos OS Release 9.1 and later

Description • 40 autonegotiating 10BASE-T, 100BASE-TX, or 1000BASE-T Megabit Ethernet ports

• Power requirement: 6.67 A @ 48 V (320 W)
• Weight: 14.5 lb (6.6 kg)
• Supports large Ethernet frame sizes for more efficient throughput across the intra-POP network
• Model number: DPCE-R-40GE-TX
• Name in the CLI: DPCE 40x 1GE R TX

Hardware features • High-performance throughput on each port at speeds of 10 Mbps, 100 Mbps, or 1000 Mbps
• Autonegotiation between Gigabit Ethernet circuit partners
• Full-duplex mode
• Maximum transmission units (MTUs) of up to 9192 bytes
• Enhanced ASICs for increased performance and scalability of Layer 2 features
• There are four sets of 10 ports labeled:
• 0/0 through 0/9
• 1/0 through 1/9
• 2/0 through 2/9
• 3/0 through 3/9

Software features • See “Protocols and Applications Supported by DPCs and Enhanced DPCs (DPC and DPCE-R)”
on page 297 for information about the protocols and applications that this DPC supports.

Copyright © 2018, Juniper Networks, Inc. 79

MX Series Interface Module Reference

Interfaces Syntax: ge-fpc/pic/port where:

• fpc: Slot in the router where the DPC is installed

• pic: Grouping of 10-ports, numbered 0 through 3
• port: 0 through 9

For example, ge-1/3/0 is the interface for port 0 (labeled 3/0) in the right-most grouping of ports
on a DPC installed in slot 1.

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

• Connector: Four-pair, Category 5 shielded twisted-pair connectivity through an RJ-45 connector

• Pinout:
• Junos OS Release 9.1: MDI
• Junos OS Release 9.2 and later: MDI, MDI crossover

• Maximum distance: 328 ft/100 m

CAUTION: Do not use RJ-45 cables with strain-relief boots exceeding 1.5 mm from the bottom
of the connector. Cable boots that exceed this measurement can damage the port.

LEDs OK/FAIL LED, one bicolor:

• Steady green—DPC is functioning normally.

• Blinking green—DPC is transitioning online or offline.
• Red—DPC has failed.

ACT LED, one green per port:

• Off—No active traffic.

• Blinking—Link is active.

SPD LED, one bicolor:

• Green—DPC is functioning in 1000BASE-T mode.

• Yellow—DPC is functioning in 10BASE-T or 100BASE-TX mode.
• Off—No link.

The ACT and SPD LEDs are located on either side of the ports labeled horizontally and top to
bottom 0/0 through 3/9.

Related • MX Series DPC Overview on page 7

Documentation
• DPCs Supported on MX240, MX480, and MX960 Routers on page 8

80 Copyright © 2018, Juniper Networks, Inc.

 Chapter 7: MX Series DPC Descriptions

Tri-Rate Enhanced Ethernet Services DPC

DPCE-X-40GE-TX
OK/F
AIL
0/0 0/1

OK/FAIL
0/2
0/4 0/3 0/5

0/6
0/8 0/7 0/9

DPCE-X-40GE-TX
1/0
1/2 1/1
1/3

Port LEDs 1/4

1/6 1/5 1/7

1/8
2/0 1/9
2/1

2/2
2/4 2/3
2/5

2/6
2/8 2/7
2/9

g003920
3/0
3/2 3/1
3/3

3/4
3/6 3/5
3/7

3/8
SPD: 3/9
G=10
00,
Y=10
/100

Software release • Junos OS Release 9.1 and later

• EOL (see PSN-2009-06-400)

Description • 40 autonegotiating 10BASE-T, 100.BASE-TX, or 1000BASE-T Megabit Ethernet ports

• Power requirement: 6.67 A @ 48 V (320 W)
• Weight: 14.5 lb (6.6 kg)
• Supports large Ethernet frame sizes for more efficient throughput across the intra-POP network
• Model number: DPCE-X-40GE-TX
• Name in the CLI:

Hardware features • High-performance throughput on each port at speeds of 10 Mbps, 100 Mbps, or 1000 Mbps
• Autonegotiation between Gigabit Ethernet circuit partners
• Full-duplex mode
• Maximum transmission units (MTUs) of up to 9192 bytes
• Enhanced ASICs for increased performance and scalability of Layer 2 features

Software features • See “Protocols and Applications Supported by Enhanced Ethernet Services DPCs (DPCE-X)”
on page 303 for information about the protocols and applications that this DPC supports.

Interfaces Syntax: ge-fpc/pic/port where:

• fpc: Slot in the router where the DPC is installed

• pic: Grouping of 10-ports, numbered 0 through 3
• port: 0 through 9

For example, ge-1/3/0 is the interface for port 0 (labeled 3/0) in the right-most grouping of ports
on a DPC installed in slot 1.

Copyright © 2018, Juniper Networks, Inc. 81

MX Series Interface Module Reference

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

• Connector: Four-pair, Category 5 shielded twisted-pair connectivity through an RJ-45 connector

• Pinout:
• Junos OS Release 9.1: MDI
• Junos OS Release 9.2 and later: MDI, MDI crossover

• Maximum distance: 328 ft/100 m

CAUTION: Do not use RJ-45 cables with strain-relief boots exceeding 1.5 mm from the bottom
of the connector. Cable boots that exceed this measurement can damage the port.

LEDs OK/FAIL LED, one bicolor:

• Steady green—DPC is functioning normally.

• Blinking green—DPC is transitioning online or offline.
• Red—DPC has failed.

ACT LED, one green per port:

• Off—No active traffic.

• Blinking—Link is active.

SPD LED, one bicolor:

• Green—DPC is functioning in 1000BASE-T mode.

• Yellow—DPC is functioning in 10BASE-T or 100BASE-TX mode.
• Off—No link.

The ACT and SPD LEDs are located on either side of the ports labeled horizontally and top to
bottom 0/0 through 3/9.

Related • MX Series DPC Overview on page 7

Documentation
• DPCs Supported on MX240, MX480, and MX960 Routers on page 8

82 Copyright © 2018, Juniper Networks, Inc.

CHAPTER 8

MX Series MPC Descriptions

• 16x10GE MPC on page 84

• Multiservices MPC on page 86
• MPC1 on page 88
• MPC1E on page 89
• MPC1 Q on page 91
• MPC1E Q on page 93
• MPC2 on page 95
• MPC2E on page 97
• MPC2 Q on page 99
• MPC2E Q on page 101
• MPC2 EQ on page 103
• MPC2E EQ on page 105
• MPC2E P on page 107
• MPC2E NG on page 109
• MPC2E NG Q on page 111
• MPC3E on page 113
• MPC3E NG on page 115
• MPC3E NG Q on page 117
• 32x10GE MPC4E on page 119
• 2x100GE + 8x10GE MPC4E on page 120
• 6x40GE + 24x10GE MPC5E on page 122
• 6x40GE + 24x10GE MPC5EQ on page 124
• 2x100GE + 4x10GE MPC5E on page 125
• 2x100GE + 4x10GE MPC5EQ on page 127
• MPC6E on page 129
• MPC7E (Multi-Rate) on page 130
• MPC7E 10G on page 132
• MPC8E on page 134

Copyright © 2018, Juniper Networks, Inc. 83

MX Series Interface Module Reference

• MPC9E on page 135

• MX10003 MPC (Multi-Rate) on page 136

16x10GE MPC

DPCE-X-40GE
OK/FAIL
OK/FAIL

MPC-3D-16XGE-SFPP LINK

0/0

LINK

0/1

LINK

0/2

LINK

0/3

LINK

1/0

LINK

1/1

LINK

1/2

LINK

1/3

LINK

2/0

LINK

2/1

LINK

2/2

LINK

2/3

LINK

g004435
3/0

LINK

3/1

LINK

3/2

LINK

3/3

Software release • MX240, MX480, and MX960 routers : Junos OS Release 10.0R2 and later
• MX2010 and MX2020 router: Junos OS Release 12.3 and later

Description • Fixed configuration MPC with sixteen 10-Gigabit Ethernet ports

• Power requirement: 9.17 A @ 48 V (440 W)
• Weight: 18.35 lb (8.3 kg)
• Model numbers:
• MPC-3D-16XGE-SFPP
• MPC-3D-16XGE-SFPP-R-B

• Name in the CLI:

• MPC 3D 16x10GE
• MPC 3D 16x10GE EM

Hardware features • High-performance throughput on each port at speeds up to 10 Gbps

• Four fully programmable Junos Trio chipsets for increased scaling for bandwidth, subscribers,
and services
• One Junos Trio chipset per set of four ports
• LAN-PHY mode at 10.3125 Gbps

NOTE: The 16x10GE 3D MPC does not support WAN-PHY mode.

84 Copyright © 2018, Juniper Networks, Inc.

 Chapter 8: MX Series MPC Descriptions

Software features • Optical diagnostics and related alarms

• See “Protocols and Applications Supported on MPCs for MX Series Routers” on page 319 for
information about the protocols and applications that this MPC supports.

Interfaces Syntax: xe-fpc/pic/port where:

• fpc: Slot in the router where the MPC is installed

• pic: Grouping of 4 ports, numbered 0 through 3
• port: 0 through 3

For example, xe-1/3/3 is the interface for the last port (labeled 3/3) on an MPC installed in slot 1.

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

NOTE: The 16x10GE 3D MPC does not support WAN-PHY mode.

NOTE: SFPP-10G-CT50-ZR is not NEBS compliant when plugged into the MPC-3D-16XGE-SFPP.
If the ambient air temperature exceeds 40 degrees C, Junos OS disables the transmitter, which
takes the optical transceiver offline.

LEDs OK/FAIL LED, one bicolor:

• Steady green—MPC is functioning normally.

• Blinking green—MPC is transitioning online or offline.
• Red—MPC has failed.

Enable/disable LED, one bicolor per port:

• Green—Port is enabled.
• Yellow—Port is not functioning normally.
• Off—Port is disabled.

The enable/disable LEDs are labeled in groups of four:

• 0/0 through 0/3

• 1/0 through 1/3
• 2/0 through 2/3
• 3/0 through 3/3

Related • MX Series MPC Overview on page 11

Documentation
• MPCs Supported by MX Series Routers on page 12

Copyright © 2018, Juniper Networks, Inc. 85

MX Series Interface Module Reference

Multiservices MPC

Figure 7: Multiservices MPC

MS-MPC

g006605
1 2 3 4 5 4

1— OK/Fail LED 4— Link/Act and Enable LEDs

2— MSPU Status and APP LEDs 5— Control 0 and Control 1 ports

3—IC LED

Software release • Junos OS Release 13.2R4 and later

For information on which MPCs are supported on MX Series routers, see “MPCs Supported by MX
Series Routers” on page 12.

Description • Power requirement: 12.2 Amps @ 48 V (590W)

• Weight: 14 lbs.
• Model number: MS-MPC
• Name in the CLI: MS-MPC

Hardware features • One Junos Trio chipset for increased scaling for bandwidth, subscribers, and services.
• Enhanced memory with 128 GB of memory (32 GB per NPU) and processing capabilities.
• NPU CPU Clock Cycle of 1.2GHz.
• Four NPUs per MPC.
• Works with SCBs and SCBEs.
• Interoperable with MS-DPCs. Both MS-MPCs and MS-DPCs can co-exist in the same chassis.

Software features • Active flow monitoring and export of flow monitoring version 9 records based on RFC 3954
• IP Security (IPsec) encryption
• Network Address Translation (NAT) for IP addresses
• Port Address Translation (PAT) for port numbers
• Traffic sampling
• Stateful firewall with packet inspection—detects SYN attacks, ICMP and UDP floods, and
ping-of-death attacks
• Network Attack Protection (NAP)
• Support for up to 6000 service sets
• Support for MTUs up to 9192 bytes.
• Multiple services can be supported. See Junos OS Services Interfaces Library for Routing Devices
for more information.
• See “Protocols and Applications Supported by the MS-MIC and MS-MPC” on page 389 for
information about the protocols and applications that this MIC supports.

86 Copyright © 2018, Juniper Networks, Inc.

 Chapter 8: MX Series MPC Descriptions

LEDs OK/FAIL LED, one bicolor:

• Steady green—MPC is functioning normally.

• Blinking green—MPC is transitioning online or offline.
• Red—MPC has failed.

IC LED—Reserved for future use.

STATUS LED, one tricolor per MSPU:

• Off—MSPU is offline. If both MSPUs are offline it is safe to remove the DPC from the chassis.
• Green—MSPU is operating normally.
• Yellow—MSPU is initializing.
• Red—MSPU has an error or failure.

Application (APP) LED, one tricolor per MSPU:

• Off—Service is not running on the MSPU.

• Green—Service is running on the MSPU under acceptable load.
• Yellow—Service on the MSPU is reconfiguring.
• Red—Service on the MSPU has failed.

Activity (LINK/ACT) LED, one per control port:

• Off—No link.
• Green—Chassis cluster control port link is active.

ENABLE LED, one per control port:

• Off—Chassis cluster control port is disabled.

• Green—Chassis cluster control port is enabled.

Related • MX Series MPC Overview on page 11

Documentation
• Multiservices MIC and Multiservices MPC (MS-MIC and MS-MPC) Overview

• Multiservices MIC on page 200

Copyright © 2018, Juniper Networks, Inc. 87

MX Series Interface Module Reference

MPC1

MX-MPC1-3D

MX-MPC1-3D
OK/Fail

0/1
PIC

g004903
Software release • MX240, MX480, and MX960 routers: Junos OS Release 10.2 and later
• MX2010 and MX2020 router: Junos OS Release 12.3 and later

For information on which MICs are supported on this MPC, “MIC/MPC Compatibility” on page 26.

Description • Power requirement: 3.4 A @ 48 V (165 W)

• Weight: 13.8 lb (6.3 kg)
• Model number: MX-MPC1-3D
• Name in the CLI: MPC Type 1 3D

Hardware features • Two slots for MICs labeled PIC 0/1 and PIC 2/3
• One Junos Trio chipset for increased scaling for bandwidth, subscribers, and services
• LAN-PHY mode at 10.3125 Gbps
• WAN-PHY mode at 9.953 Gbps

Software features • See “Protocols and Applications Supported on MPCs for MX Series Routers” on page 319 for
information about the protocols and applications that this MPC supports.

LEDs OK/FAIL LED, one bicolor:

• Steady green—MPC is functioning normally.

• Blinking green—MPC is transitioning online or offline.
• Red—MPC has failed.

88 Copyright © 2018, Juniper Networks, Inc.

 Chapter 8: MX Series MPC Descriptions

Related • MX Series MPC Overview on page 11

Documentation
• MPCs Supported by MX Series Routers on page 12

MPC1E

MX-MPC1E-3D

MX-MPC1E-3D

MX-MPC1E-3D
OK/Fail

0/1
PIC

OK/Fail

g006576

Software release • MX240, MX480, and MX960 routers: Junos OS Release 11.2R4 and later
• MX2010 and MX2020 router: Junos OS Release 12.3 and later

For information on which MICs are supported on this MPC, “MIC/MPC Compatibility” on page 26.

Description • Power requirement: 3.4 A @ 48 V (165 W)

• Weight: 13.8 lb (6.3 kg)
• Model number: MX-MPC1E-3D
• Name in the CLI: MPCE Type 1 3D

Hardware features • Two slots for MICs labeled PIC 0/1 and PIC 2/3
• One Junos Trio chipset for increased scaling for bandwidth, subscribers, and services
• LAN-PHY mode at 10.3125 Gbps
• WAN-PHY mode at 9.953 Gbps

Software features • See “Protocols and Applications Supported on the MPC1E for MX Series Routers” on page 328
for information about the protocols and applications that this MPC supports.

Copyright © 2018, Juniper Networks, Inc. 89

MX Series Interface Module Reference

LEDs OK/FAIL LED, one bicolor:

• Steady green—MPC is functioning normally.

• Blinking green—MPC is transitioning online or offline.
• Red—MPC has failed.

90 Copyright © 2018, Juniper Networks, Inc.

 Chapter 8: MX Series MPC Descriptions

Related • MX Series MPC Overview on page 11

Documentation
• MPCs Supported by MX Series Routers on page 12

MPC1 Q

MX-MPC1-3D-Q

MX-MPC1-3D-Q

MX-MPC1-3D-Q
OK/Fail

0/1
PIC

OK/Fail

g004904

Software release • MX240, MX480, and MX960 routers: Junos OS Release 10.2 and later
• MX2010 and MX2020 router: Junos OS Release 12.3 and later

For information on which MICs are supported on this MPC, “MIC/MPC Compatibility” on page 26.

Description • Power requirement: 3.65 A @ 48 V (175 W)

• Weight: 13.8 lb (6.3 kg)
• Model number: MX-MPC1-3D-Q
• Name in the CLI: MPC Type 1 3D Q

Hardware features • Two slots for MICs labeled PIC 0/1 and PIC 2/3
• One Junos Trio chipset for increased scaling for bandwidth, subscribers, and services
• LAN-PHY mode at 10.3125 Gbps
• WAN-PHY mode at 9.953 Gbps

Software features • See “Protocols and Applications Supported on MPCs for MX Series Routers” on page 319 for
information about the protocols and applications that this MPC supports.

Copyright © 2018, Juniper Networks, Inc. 91

MX Series Interface Module Reference

LEDs OK/FAIL LED, one bicolor:

• Steady green—MPC is functioning normally.

• Blinking green—MPC is transitioning online or offline.
• Red—MPC has failed.

92 Copyright © 2018, Juniper Networks, Inc.

 Chapter 8: MX Series MPC Descriptions

Related • MX Series MPC Overview on page 11

Documentation
• MPCs Supported by MX Series Routers on page 12

MPC1E Q

MX-MPC1E-3D-Q

MX-MPC1E-3D-Q

MX-MPC1E-3D-Q
OK/Fail

0/1
PIC

OK/Fail

g006577

Software release • MX240, MX480, and MX960 routers: Junos OS Release 11.2R4 and later
• MX2010 and MX2020 router: Junos OS Release 12.3 and later

For information on which MICs are supported on this MPC, “MIC/MPC Compatibility” on page 26.

Description • Power requirement: 3.65 A @ 48 V (175 W)

• Weight: 13.8 lb (6.3 kg)
• Model number: MX-MPC1E-3D-Q
• Name in the CLI: MPCE Type 1 3D Q

Hardware features • Two slots for MICs labeled PIC 0/1 and PIC 2/3
• One Junos Trio chipset for increased scaling for bandwidth, subscribers, and services
• LAN-PHY mode at 10.3125 Gbps
• WAN-PHY mode at 9.953 Gbps

Software features • See “Protocols and Applications Supported on the MPC1E for MX Series Routers” on page 328
for information about the protocols and applications that this MPC supports.

Copyright © 2018, Juniper Networks, Inc. 93

MX Series Interface Module Reference

LEDs OK/FAIL LED, one bicolor:

• Steady green—MPC is functioning normally.

• Blinking green—MPC is transitioning online or offline.
• Red—MPC has failed.

94 Copyright © 2018, Juniper Networks, Inc.

 Chapter 8: MX Series MPC Descriptions

Related • MX Series MPC Overview on page 11

Documentation
• MPCs Supported by MX Series Routers on page 12

MPC2

MX-MPC2-3D

MX-MPC2-3D

MX-MPC2-3D
OK/Fail

0/1
PIC

OK/Fail

g004905

Software release • MX240, MX480, and MX960 routers : Junos OS Release 10.1 and later
• MX2010 and MX2020 router: Junos OS Release 12.3 and later

For information on which MICs are supported on this MPC, “MIC/MPC Compatibility” on page 26.

Description • Power requirement: 5.7 A @ 48 V (274 W)

• Weight: 14 lb (6.4 kg)
• Model number: MX-MPC2-3D
• Name in the CLI: MPC Type 2 3D

Hardware features • Two slots for MICs labeled PIC 0/1 and PIC 2/3
• Two Junos Trio chipsets for increased scaling for bandwidth, subscribers, and services
• LAN-PHY mode at 10.3125 Gbps
• WAN-PHY mode at 9.953 Gbps

Software features • See “Protocols and Applications Supported on MPCs for MX Series Routers” on page 319 for
information about the protocols and applications that this MPC supports.

Copyright © 2018, Juniper Networks, Inc. 95

MX Series Interface Module Reference

LEDs OK/FAIL LED, one bicolor:

• Steady green—MPC is functioning normally.

• Blinking green—MPC is transitioning online or offline.
• Red—MPC has failed.

96 Copyright © 2018, Juniper Networks, Inc.

 Chapter 8: MX Series MPC Descriptions

Related • MX Series MPC Overview on page 11

Documentation
• MPCs Supported by MX Series Routers on page 12

MPC2E

MX-MPC2E-3D

MX-MPC2E-3D

MX-MPC2E-3D
OK/Fail

0/1
PIC

OK/Fail

g006578

Software release • MX240, MX480, and MX960 routers : Junos OS Release 11.2R4 and later
• MX2010 and MX2020 router: Junos OS Release 12.3 and later

For information on which MICs are supported on this MPC, “MIC/MPC Compatibility” on page 26.

Description • Power requirement: 5.7 A @ 48 V (274 W)

• Weight: 14 lb (6.4 kg)
• Model number: MX-MPC2E-3D
• Name in the CLI: MPCE Type 2 3D

Hardware features • Two slots for MICs labeled PIC 0/1 and PIC 2/3
• Two Junos Trio chipsets for increased scaling for bandwidth, subscribers, and services
• LAN-PHY mode at 10.3125 Gbps
• WAN-PHY mode at 9.953 Gbps

Software features • See “Protocols and Applications Supported on the MPC1E for MX Series Routers” on page 328
for information about the protocols and applications that this MPC supports.

Copyright © 2018, Juniper Networks, Inc. 97

MX Series Interface Module Reference

LEDs OK/FAIL LED, one bicolor:

• Steady green—MPC is functioning normally.

• Blinking green—MPC is transitioning online or offline.
• Red—MPC has failed.

98 Copyright © 2018, Juniper Networks, Inc.

 Chapter 8: MX Series MPC Descriptions

Related • MX Series MPC Overview on page 11

Documentation
• MPCs Supported by MX Series Routers on page 12

MPC2 Q

MX-MPC2-3D-Q

MX-MPC2-3D-Q

MX-MPC2-3D-Q
OK/Fail

0/1
PIC

OK/Fail

g004906

Software release • MX240, MX480, and MX960 routers : Junos OS Release 10.1 and later
• MX2010 and MX2020 router: Junos OS Release 12.3 and later

For information on which MICs are supported on this MPC, “MIC/MPC Compatibility” on page 26.

Description • Power requirement: 6.13 A @ 48 V (294 W)

• Weight: 14 lb (6.4 kg)
• Model number: MX-MPC2-3D-Q
• Name in the CLI: MPC Type 2 3D Q

Hardware features • Two slots for MICs labeled PIC 0/1 and PIC 2/3
• Two Junos Trio chipsets for increased scaling for bandwidth, subscribers, and services
• LAN-PHY mode at 10.3125 Gbps
• WAN-PHY mode at 9.953 Gbps

Software features • See “Protocols and Applications Supported on MPCs for MX Series Routers” on page 319 for
information about the protocols and applications that this MPC supports.

Copyright © 2018, Juniper Networks, Inc. 99

MX Series Interface Module Reference

LEDs OK/FAIL LED, one bicolor:

• Steady green—MPC is functioning normally.

• Blinking green—MPC is transitioning online or offline.
• Red—MPC has failed.

100 Copyright © 2018, Juniper Networks, Inc.

 Chapter 8: MX Series MPC Descriptions

Related • MX Series MPC Overview on page 11

Documentation
• MPCs Supported by MX Series Routers on page 12

MPC2E Q

MX-MPC2E-3D-Q

MX-MPC2E-3D-Q

MX-MPC2E-3D-Q
OK/Fail

0/1
PIC

OK/Fail

g006579

Software release • MX240, MX480, and MX960 routers : Junos OS Release 11.2R4 and later
• MX2010 and MX2020 router: Junos OS Release 12.3 and later

For information on which MICs are supported on this MPC, “MIC/MPC Compatibility” on page 26.

Description • Power requirement: 6.13 A @ 48 V (294 W)

• Weight: 14 lb (6.4 kg)
• Model number: MX-MPC2E-3D-Q
• Name in the CLI: MPCE Type 2 3D Q

Hardware features • Two slots for MICs labeled PIC 0/1 and PIC 2/3
• Two Junos Trio chipsets for increased scaling for bandwidth, subscribers, and services
• LAN-PHY mode at 10.3125 Gbps
• WAN-PHY mode at 9.953 Gbps

Software features • See “Protocols and Applications Supported on the MPC1E for MX Series Routers” on page 328
for information about the protocols and applications that this MPC supports.

Copyright © 2018, Juniper Networks, Inc. 101

MX Series Interface Module Reference

LEDs OK/FAIL LED, one bicolor:

• Steady green—MPC is functioning normally.

• Blinking green—MPC is transitioning online or offline.
• Red—MPC has failed.

102 Copyright © 2018, Juniper Networks, Inc.

 Chapter 8: MX Series MPC Descriptions

Related • MX Series MPC Overview on page 11

Documentation
• MPCs Supported by MX Series Routers on page 12

MPC2 EQ

MX-MPC2-3D-EQ

MX-MPC2-3D-EQ

MX-MPC2-3D-EQ
OK/Fail

0/1
PIC

OK/Fail

g004907

Software release • MX240, MX480, and MX960 routers : Junos OS Release 10.1 and later
• MX2010 and MX2020 router: Junos OS Release 12.3 and later

For information on which MICs are supported on this MPC, “MIC/MPC Compatibility” on page 26.

Description • Power requirement: 6.13 A @ 48 V (294 W)

• Weight: 14 lb (6.4 kg)
• Model number: MX-MPC2-3D-EQ
• Name in the CLI: MPC Type 2 3D EQ

Hardware features • Two slots for MICs labeled PIC 0/1 and PIC 2/3
• Two Junos Trio chipsets for increased scaling for bandwidth, subscribers, and services
• LAN-PHY mode at 10.3125 Gbps
• WAN-PHY mode at 9.953 Gbps

Software features • See “Protocols and Applications Supported on MPCs for MX Series Routers” on page 319 for
information about the protocols and applications that this MPC supports.

Copyright © 2018, Juniper Networks, Inc. 103

MX Series Interface Module Reference

LEDs OK/FAIL LED, one bicolor:

• Steady green—MPC is functioning normally.

• Blinking green—MPC is transitioning online or offline.
• Red—MPC has failed.

104 Copyright © 2018, Juniper Networks, Inc.

 Chapter 8: MX Series MPC Descriptions

Related • MX Series MPC Overview on page 11

Documentation
• MPCs Supported by MX Series Routers on page 12

MPC2E EQ

MX-MPC2E-3D-EQ

MX-MPC2E-3D-EQ

MX-MPC2E-3D-EQ
OK/Fail

0/1
PIC

OK/Fail

g006580

Software release • MX240, MX480, and MX960 routers : Junos OS Release 11.2R4 and later
• MX2010 and MX2020 router: Junos OS Release 12.3 and later

For information on which MICs are supported on this MPC, “MIC/MPC Compatibility” on page 26.

Description • Power requirement: 6.13 A @ 48 V (294 W)

• Weight: 14 lb (6.4 kg)
• Model number: MX-MPC2E-3D-EQ
• Name in the CLI: MPCE Type 2 3D EQ

Hardware features • Two slots for MICs labeled PIC 0/1 and PIC 2/3
• Two Junos Trio chipsets for increased scaling for bandwidth, subscribers, and services
• LAN-PHY mode at 10.3125 Gbps
• WAN-PHY mode at 9.953 Gbps

Software features • See “Protocols and Applications Supported on the MPC1E for MX Series Routers” on page 328
for information about the protocols and applications that this MPC supports.

Copyright © 2018, Juniper Networks, Inc. 105

MX Series Interface Module Reference

LEDs OK/FAIL LED, one bicolor:

• Steady green—MPC is functioning normally.

• Blinking green—MPC is transitioning online or offline.
• Red—MPC has failed.

106 Copyright © 2018, Juniper Networks, Inc.

 Chapter 8: MX Series MPC Descriptions

Related • MX Series MPC Overview on page 11

Documentation
• MPCs Supported by MX Series Routers on page 12

MPC2E P

MX-MPC2E-3D-P

MX-MPC2E-3D-P

MX-MPC2E-3D-EQ
OK/Fail

0/1
PIC

OK/Fail

g006586

Software release • MX240, MX480, and MX960 routers : Junos OS Release 12.2 and later
• MX2010 and MX2020 router: Junos OS Release 12.3 and later

For information on which MICs are supported on this MPC, “MIC/MPC Compatibility” on page 26.

Description • Power requirement: 6.13 A @ 48 V (294 W)

• Weight: 14 lb (6.4 kg)
• Model number: MX-MPC2E-3D-P
• Name in the CLI: MPCE Type 2 3D P

Hardware features • Two slots for MICs labeled PIC 0/1 and PIC 2/3
• Two Junos Trio chipsets for increased scaling for bandwidth, subscribers, and services
• LAN-PHY mode at 10.3125 Gbps
• WAN-PHY mode at 9.953 Gbps

Software features • See “Protocols and Applications Supported on the MPC1E for MX Series Routers” on page 328
for information about the protocols and applications that this MPC supports.

Copyright © 2018, Juniper Networks, Inc. 107

MX Series Interface Module Reference

LEDs OK/FAIL LED, one bicolor:

• Steady green—MPC is functioning normally.

• Blinking green—MPC is transitioning online or offline.
• Red—MPC has failed.

108 Copyright © 2018, Juniper Networks, Inc.

 Chapter 8: MX Series MPC Descriptions

Related • MX Series MPC Overview on page 11

Documentation
• MPCs Supported by MX Series Routers on page 12

MPC2E NG

Software release • Junos OS releases 14.1R4, 14.2R3 and Junos Continuity, Junos OS release 15.1 and later.
• Refer to “MIC/MPC Compatibility” on page 26 for information about which MICs are supported
on this MPC.
• Refer to the JTAC Knowledgebase article https://kb.juniper.net/KB21476 for recommended
software releases.

Description • 80 Gbps capacity without hierarchical quality of service (HQoS)

• Requires high-capacity fan trays and high-capacity filter trays
• Weight: 15.96 lb (7.26 kg)
• Model numbers: MPC2E-3D-NG
• Name in the CLI: MPC2E NG PQ & Flex Q
• Add-on license provides limited additional flexible queuing.

NOTE: MPC2E-3D-NG is not compatible with SCB, you must use either SCBE-MX or SCBE2-MX
for the switch fabric interface.

NOTE: To power on an MPC on MX240, MX480, and MX960 routers, you must configure the
network-services enhanced-ip or network-services enhanced-ethernet statement. With this
configuration, the router functions in Enhanced-IP/Enhanced-Ethernet network services mode and
powers on MPCs and MS-DPCs only. The MPC does not come online if this statement is not
configured. On MX2010, and MX2020 routers, network-services enhanced-ip is configured by
default.

Hardware features • Line-rate throughput of up to 80 Gbps

• Supports WAN-PHY mode at 9.95 Gbps and LAN-PHY mode at 10.31 Gbps
• Two slots for MICs
• Junos Trio chipsets for increased scaling for bandwidth, subscribers, and services.

NOTE: MPC2E-3D-NG is not compatible with SCB, you must use either SCBE-MX or SCBE2-MX
for the switch fabric interface.

NOTE: MPC2E-3D-NG does not support MIC3-3D-10XGE-SFPP, MIC3-3D-1X100GE-CFP,

MIC3-3D-1X100GE-CXP, and MIC3-3D-2X40GE-QSFPP.

NOTE: The non-HQOS MPC3E NG and MPC2E NG MPCs support MIC-3D-8CHOC3-4CHOC12

and MIC-3D-4CHOC3-2CHOC12 only with a limited queuing license.

Copyright © 2018, Juniper Networks, Inc. 109

MX Series Interface Module Reference

Software features • Chained composite next hops

• Layer 3 VPN localization
• Detection of Layer 2 loops
• Entropy label support in mixed mode
• SNMP and CLI support for Routing Engine memory monitoring
• Mixed-mode LAG support on core interfaces
• Dynamic power management for MICs
• Support for flexible-queuing

• See “Protocols and Applications Supported by the MX240, MX480, MX960, MX2010, and
MX2020 MPC2E” on page 334 for information about the protocols and applications that this
MPC supports.

Power requirement Maximum with highest-power MICs at 55° C: 9.88 A @ 48 V (474 W)

At different temperatures:

• 55° C: 474 W
• 40° C: 417 W
• 25° C: 400 W

LEDs OK/FAIL LED, one bicolor:

• Steady green—MPC is functioning normally.

• Blinking green—MPC is transitioning online or offline.
• Red—MPC has failed.

110 Copyright © 2018, Juniper Networks, Inc.

 Chapter 8: MX Series MPC Descriptions

Related • MX Series MPC Overview on page 11

Documentation
• MPCs Supported by MX Series Routers on page 12

• Junos Continuity Software

MPC2E NG Q

Software release • Junos OS releases 14.1R4, 14.2R3 and Junos Continuity, Junos OS release 15.1 and later.
• Refer to “MIC/MPC Compatibility” on page 26 for information about which MICs are supported
on this MPC.
• Refer to the JTAC Knowledgebase article https://kb.juniper.net/KB21476 for recommended
software releases.

Description • 80 Gbps capacity with hierarchical quality of service (HQoS)

• Requires high-capacity fan trays and high capacity filter trays
• Weight: 15.96 lb (7.26 kg)
• Model number: MPC2E-3D-NG-Q
• Name in the CLI: MPC2E NG HQoS

NOTE: MPC2E-3D-NG-Q is not compatible with SCB, you must use either SCBE-MX or SCBE2-MX
for the switch fabric interface.

NOTE: To power on an MPC on MX240, MX480, and MX960 routers, you must configure the
network-services enhanced-ip or network-services enhanced-ethernet statement. With this
configuration, the router functions in Enhanced-IP/Enhanced-Ethernet network services mode and
powers on MPCs and MS-DPCs only. The MPC does not come online if this statement is not
configured. On MX2010, and MX2020 routers, network-services enhanced-ip is configured by
default.

Hardware features • Line-rate throughput of up to 80 Gbps

• Supports up to 512,000 queues per slot
• Supports WAN-PHY mode at 9.95 Gbps and LAN-PHY mode at 10.31 Gbps
• Two slots for MICs
• Junos Trio chipsets for increased scaling for bandwidth, subscribers, and services.

NOTE: The MPC2E-3D-NG-Q has only one lookup chip (LU).

NOTE: MPC2E-3D-NG-Q does not support MIC3-3D-10XGE-SFPP, MIC3-3D-1X100GE-CFP,

MIC3-3D-1X100GE-CXP, and MIC3-3D-2X40GE-QSFPP.

Copyright © 2018, Juniper Networks, Inc. 111

MX Series Interface Module Reference

Software features • Chained composite next hops

• Layer 3 VPN localization
• Detection of Layer 2 loops
• Entropy label support in mixed mode
• SNMP and CLI support for Routing Engine memory monitoring
• BFD support for inline MLPPP/MLFR
• Mixed Mode LAG support on core interfaces
• Dynamic power management for MICs
• See “Protocols and Applications Supported by the MX240, MX480, MX960, MX2010, and
MX2020 MPC2E” on page 334 for information about the protocols and applications that this
MPC supports.

Power requirement Maximum with highest-power MICs at 55° C: 11.02 A @ 48 V (529 W)

At different temperatures:

• 55° C: 529 W
• 40° C: 460 W
• 25° C: 438 W

LEDs OK/FAIL LED, one bicolor:

• Steady green—MPC is functioning normally.

• Blinking green—MPC is transitioning online or offline.
• Red—MPC has failed.

112 Copyright © 2018, Juniper Networks, Inc.

 Chapter 8: MX Series MPC Descriptions

Related • MX Series MPC Overview on page 11

Documentation
• MPCs Supported by MX Series Routers on page 12

• Junos Continuity Software

MPC3E

MX-MPC3E-3D
MX-MPC3E-3D

MX-MPC3E-3D
OK/Fail

0/1
PIC

OK/Fail

g006100

Software release • MX240, MX480, and MX960 routers : Junos OS Release 12.1 and later
• MX2010 and MX2020 router: Junos OS Release 12.3 and later

For information on which MICs are supported on this MPC, “MIC/MPC Compatibility” on page 26.

Description • Power requirement: 10.83 A @ 48 V (440 W; plus 40 W for each of the two MICs)
• Requires high-capacity fan trays
• Weight: 14.94 lb (6.78 kg)
• Model number: MX-MPC3E-3D
• Name in the CLI: MPCE Type 3 3D

Hardware features • Two slots for MICs

• Chipset for increased scaling for bandwidth, subscribers, and services
• Supports maximum transmission unit (MTU) size of 9,192 bytes for host bound packets. For
Junos OS 16.1R1 and later releases, the MTU size supported is 9,500 bytes.

Software features • See “Protocols and Applications Supported by the MPC3E on MX Series Routers” on page 343
for information about the protocols and applications that this MPC supports.

Copyright © 2018, Juniper Networks, Inc. 113

MX Series Interface Module Reference

LEDs OK/FAIL LED, one bicolor:

• Steady green—MPC is functioning normally.

• Blinking green—MPC is transitioning online or offline.
• Red—MPC has failed.

114 Copyright © 2018, Juniper Networks, Inc.

 Chapter 8: MX Series MPC Descriptions

Related • MX Series MPC Overview on page 11

Documentation
• MPCs Supported by MX Series Routers on page 12

MPC3E NG

Software release • Junos OS releases 14.1R4, 14.2R3 and Junos Continuity, Junos OS release 15.1 and later.
• Refer to “MIC/MPC Compatibility” on page 26 for information about which MICs are supported
on this MPC.
• Refer to the JTAC Knowledgebase article https://kb.juniper.net/KB21476 for recommended
software releases.

Description • 130 Gbps capacity without hierarchical quality of service (HQoS)

• Requires high-capacity fan trays and high-capacity filter trays
• Weight: 15.96 lb (7.26 kg)
• Model number: MPC3E-3D-NG
• Name in the CLI: MPC3E NG PQ & Flex Q
• Add-on license provides limited additional flexible queuing.

NOTE: MPC3E-3D-NG is not compatible with SCB, you must use either SCBE-MX or SCBE2-MX
for the switch fabric interface.

NOTE: To power on an MPC on MX240, MX480, and MX960 routers, you must configure the
network-services enhanced-ip or network-services enhanced-ethernet statement. With this
configuration, the router functions in Enhanced-IP/Enhanced-Ethernet network services mode and
powers on MPCs and MS-DPCs only. The MPC does not come online if this statement is not
configured. On MX2010, and MX2020 routers, network-services enhanced-ip is configured by
default.

Hardware features • Line-rate throughput of up to 130 Gbps

• Supports WAN-PHY mode at 9.95 Gbps and LAN-PHY mode at 10.31 Gbps
• Supports maximum transmission unit (MTU) size of 9,192 bytes for host bound packets. For
Junos OS 16.1R1 and later releases, the MTU size supported is 9,500 bytes.
• Two slots for MICs
• Junos Trio chipsets for increased scaling for bandwidth, subscribers, and services

NOTE: The non-HQOS MPC3E NG and MPC2E NG MPCs support MIC-3D-8CHOC3-4CHOC12

and MIC-3D-4CHOC3-2CHOC12 only with a limited queuing license.

Copyright © 2018, Juniper Networks, Inc. 115

MX Series Interface Module Reference

Software features • Chained composite next hops

• Layer 3 VPN localization
• Detection of Layer 2 loops
• Entropy label support in mixed mode
• SNMP and CLI support for Routing Engine memory monitoring
• Mixed Mode LAG support on core interfaces
• Dynamic power management for MICs
• Support for flexible-queuing
• See “Protocols and Applications Supported by the MPC3E on MX Series Routers” on page 343
for information about the protocols and applications that this MPC supports.

Power requirement Maximum with highest-power MICs at 55° C: 11.13 A @ 48 V (534 W)

At different temperatures:

• 55° C: 534 W
• 40° C: 485 W
• 25° C: 461 W

LEDs OK/FAIL LED, one bicolor:

• Steady green—MPC is functioning normally.

• Blinking green—MPC is transitioning online or offline.
• Red—MPC has failed.

NOTE: On the MX960 router, FPC slot 0 and slot 11 are not NEBS compliant
beyond 104°F (40°C) with MPC3E-3D-NG and MPC3E-3D-NG-Q. This is a
cooling restriction.

116 Copyright © 2018, Juniper Networks, Inc.

 Chapter 8: MX Series MPC Descriptions

Related • MX Series MPC Overview on page 11

Documentation
• MPCs Supported by MX Series Routers on page 12

• Junos Continuity Software

MPC3E NG Q

Software release • Junos OS releases 14.1R4, 14.2R3 and Junos Continuity, Junos OS release 15.1 and later.

• Refer to “MIC/MPC Compatibility” on page 26 for information about which MICs are supported
on this MPC.
• Refer to the JTAC Knowledgebase article https://kb.juniper.net/KB21476 for recommended
software releases.

Description • 130 Gbps capacity with hierarchical quality of service (HQoS)

• Requires high-capacity fan trays and high-capacity filter trays
• Weight: 15.96 lb (7.26 kg)
• Model number: MPC3E-3D-NG-Q
• Name in the CLI: MPC3E NG HQoS

NOTE: MPC3E-3D-NG-Q is not compatible with SCB, you must use either SCBE-MX or SCBE2-MX
for the switch fabric interface.

NOTE: To power on an MPC on MX240, MX480, and MX960 routers, you must configure the
network-services enhanced-ip or network-services enhanced-ethernet statement. With this
configuration, the router functions in Enhanced-IP/Enhanced-Ethernet network services mode and
powers on MPCs and MS-DPCs only. The MPC does not come online if this statement is not
configured. On MX2010, and MX2020 routers, network-services enhanced-ip is configured by
default.

Hardware features • Line-rate throughput of up to 130 Gbps

• Supports up to 512,000 queues per slot
• Supports WAN-PHY mode at 9.95 Gbps and LAN-PHY mode at 10.31 Gbps
• Supports maximum transmission unit (MTU) size of 9,192 bytes for host bound packets. For
Junos OS 16.1R1 and later releases, the MTU size supported is 9,500 bytes.
• Two slots for MICs
• Junos Trio chipsets for increased scaling for bandwidth, subscribers, and services

Copyright © 2018, Juniper Networks, Inc. 117

MX Series Interface Module Reference

Software features • Chained composite next hops

• Layer 3 VPN localization
• Detection of Layer 2 loops
• Entropy label support in mixed mode
• SNMP and CLI support for Routing Engine memory monitoring
• BFD support for inline MLPPP/MLFR
• Mixed Mode LAG support on core interfaces
• Dynamic power management for MICs
• See “Protocols and Applications Supported by the MPC3E on MX Series Routers” on page 343
for information about the protocols and applications that this MPC supports.

Power requirement Maximum with highest-power MICs at 55° C: 12.15 A @ 48 V (583 W)

At different temperatures:

• 55° C: 583 W
• 40° C: 532 W
• 25° C: 503 W

LEDs OK/FAIL LED, one bicolor:

• Steady green—MPC is functioning normally.

• Blinking green—MPC is transitioning online or offline.
• Red—MPC has failed.

NOTE: On the MX960 router, FPC slot 0 and slot 11 are not NEBS compliant
beyond 104°F (40°C) with MPC3E-3D-NG and MPC3E-3D-NG-Q. This is a
cooling restriction.

118 Copyright © 2018, Juniper Networks, Inc.

 Chapter 8: MX Series MPC Descriptions

Related • MX Series MPC Overview on page 11

Documentation
• MPCs Supported by MX Series Routers on page 12

• Junos Continuity Software

32x10GE MPC4E

0/1
0/3
0/5
0/7

1/1
1/3
1/5
1/7

2/1
2/3
2/5
2/7

3/1
3/3
3/5
3/7
OK/FAIL

0/0
0/2
0/4
0/6

1/0
1/2
1/4
1/6

2/0
2/2
2/4
2/6

3/0
3/2
3/4
3/6

g007340
MPC4E-3D-32XGE-SFPP

Software release • Junos OS Release 12.3R2 and later

Description • Fixed configuration MPC with thirty-two 10-Gigabit Ethernet ports

• Power requirement: 12.7 A @ 48 V (610 W)
• Weight: 19.4 lb (8.8 kg)
• Model number: MPC4E-3D-32XGE-SFPP

Hardware features • Line-rate throughput of up to 260 Gbps

• WAN-PHY mode at 10 Gbps on a per-port basis
• Supports maximum transmission unit (MTU) size of 9,192 bytes for host bound packets. For
Junos OS 16.1R1 and later releases, the MTU size supported is 9,500 bytes.
• Supported on MX2020, MX2010, MX960, MX480, and MX240 routers with both normal-capacity
and high-capacity power supplies and fan trays.

Software features • Optical diagnostics and related alarms

• Up to 260 Gbps of full-duplex traffic
• Intelligent oversubscription services
• Configurable LAN-PHY and WAN-PHY mode options per port
• Local loopback
• Configurable to interoperate with routers that use the 100-Gigabit Ethernet PIC (Type 4 PIC
on Type 4 FPC)
• See “Protocols and Applications Supported on the MPC4E for MX Series Routers” on page 351
for information about the protocols and applications that this MPC supports.

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

NOTE: SFPP-10GE-ZR has a commercial temperature rating and is not NEBS compliant when
plugged into the 32x10GE MPC4E with SFP+. If the ambient air temperature exceeds 40°C, Junos
OS disables the transmitter, which takes the optical transceiver offline.

NOTE: SFPP-10G-DT-ZRC2 is not NEBS compliant when plugged into the MPC4E-3D-32XGE-SFPP
MPC. If the ambient air temperature exceeds 40°C, Junos OS disables the transmitter, which
takes the optical transceiver offline.

NOTE: On the MX960 router, FPC slot 0 and FPC slot 11 are not NEBS compliant beyond 104°F
(40°C). This is a cooling restriction.

Copyright © 2018, Juniper Networks, Inc. 119

MX Series Interface Module Reference

LEDs OK/FAIL LED, one bicolor:

• Steady green—MPC is functioning normally.

• Blinking green—MPC is transitioning online or offline.
• Red—MPC has failed.

Enable/disable LED, one bicolor per port:

• Green—Port is enabled.
• Red—Port has failed.
• Off—Port is disabled.

The enable/disable LEDs are arranged in four groups:

• 0/0 through 0/7

• 1/0 through 1/7
• 2/0 through 2/7
• 3/0 through 3/7

Related • MX Series MPC Overview on page 11

Documentation
• MPC4E on MX Series Routers Overview

• MPCs Supported by MX Series Routers on page 12

• Configuring MPC4E (MPC4E-3D-2CGE-8XGE) to Interoperate with 100-Gigabit Ethernet

PICs on Type 4 FPC Using SA Multicast Mode

2x100GE + 8x10GE MPC4E

LINK

LINK

LINK

LINK

LINK

LINK

LINK

LINK
0/0

0/1

0/2

0/3

2/0

2/1

2/2

2/3
PORT 1/0

PORT 3/0
OK/FAIL

LINK

LINK
MPC4E-3D-2CGE-8XGE

Software release • Junos OS Release 12.3R2 and later

Description • Fixed configuration MPC with two 100-Gigabit Ethernet ports and eight 10-Gigabit Ethernet
ports
• Power requirement: 12.7 A @ 48 V (610 W)
• Weight: 19.4 lb (8.8 kg)
• Model number: MPC4E-3D-2CGE-8XGE

120 Copyright © 2018, Juniper Networks, Inc.

 Chapter 8: MX Series MPC Descriptions

Hardware features • Line-rate throughput of up to 260 Gbps

• WAN-PHY mode at 10 Gbps on a per-port basis
• Supported only on the MX960, MX480, and MX240 routers with high-capacity power supplies
and high-capacity fan trays.
• Supports maximum transmission unit (MTU) size of 9,192 bytes for host bound packets. For
Junos OS 16.1R1 and later releases, the MTU size supported is 9,500 bytes.
• The ports are labeled as:
• 10-Gigabit Ethernet ports: 0/0 through 0/3
• 100-Gigabit Ethernet ports: PORT 1/0
• 10-Gigabit Ethernet ports: 2/0 through 2/3
• 100-Gigabit Ethernet ports: PORT 3/0

Software features • Optical diagnostics and related alarms

• Configurable LAN-PHY and WAN-PHY mode options per 10-Gigabit Ethernet port
• Up to 260 Gbps of full-duplex traffic
• Intelligent oversubscription services
• Local loopback
• Configurable to interoperate with routers that use the 100-Gigabit Ethernet PIC (Type 4 PIC
on Type 4 FPC)
• See “Protocols and Applications Supported on the MPC4E for MX Series Routers” on page 351
for information about the protocols and applications that this MPC supports.

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

NOTE: SFPP-10GE-ZR has a commercial temperature rating and is not NEBS compliant when
plugged into the 2x100GE + 8x10GE MPC4E. If the ambient air temperature exceeds 40°C, Junos
OS disables the transmitter, which takes the optical transceiver offline.

NOTE: SFPP-10G-DT-ZRC2 is not NEBS compliant when plugged into the MPC4E-3D-2CGE-8XGE
MPC. If the ambient air temperature exceeds 40°C, Junos OS disables the transmitter, which
takes the optical transceiver offline.

NOTE: CFP-100GBASE-LR4 and CFP-100GBASE-ZR are not NEBS compliant when plugged into
the 2x100GE + 8x10GE MPC4E. If the ambient air temperature exceeds 40°C, the software disables
the transmitter, which takes the optical transceiver offline.

NOTE: On the MX960 router, FPC slot 0 and FPC slot 11 are not NEBS compliant beyond 104°F
(40°C). This is a cooling restriction.

LEDs OK/FAIL LED, one bicolor:

• Steady green—MPC is functioning normally.

• Blinking green—MPC is transitioning online or offline.
• Red—MPC has failed.

LINK LED, one tricolor per port:

• Green—Port is enabled.
• Red—Port has failed.
• Yellow—Port is disabled by configuration.
• Off—Port is disabled.

Copyright © 2018, Juniper Networks, Inc. 121

MX Series Interface Module Reference

Related • MX Series MPC Overview on page 11

Documentation
• MPC4E on MX Series Routers Overview

• MPCs Supported by MX Series Routers on page 12

• Configuring MPC4E (MPC4E-3D-2CGE-8XGE) to Interoperate with 100-Gigabit Ethernet

PICs on Type 4 FPC Using SA Multicast Mode

6x40GE + 24x10GE MPC5E

g007682
MPC5E-40G10G

Software release • Junos OS Release 13.3R2 and later

Description • Fixed-port MPC with six 40-Gigabit Ethernet ports and twenty-four 10-Gigabit Ethernet ports
• Weight: 21 lb (9.52 kg)
• Model number: MPC5E-40G10G
• Name in the CLI: MPC5E 3D 24XGE+6XLGE

Hardware features • Line-rate throughput of up to 240 Gbps

• Supports one of the following port combinations:
• Six 40-Gigabit Ethernet ports
• Twenty-four 10-Gigabit Ethernet ports
• Three 40-Gigabit Ethernet ports and twelve 10-Gigabit Ethernet ports

• Supports up to 32,000 queues per-slot

• LAN-PHY mode at 10.3125 Gbps on a per-port basis
• WAN-PHY mode at 9.95328 Gbps on a per-port basis
• Supports maximum transmission unit (MTU) size of 9,192 bytes for host bound packets. For
Junos OS 16.1R1 and later releases, the MTU size supported is 9,500 bytes.
• The ports are labeled as:
• 10-Gigabit Ethernet ports:
0/0 through 0/11
1/0 through 1/11
• 40-Gigabit Ethernet ports:
2/0 through 2/2
3/0 through 3/2

NOTE: On MX960 routers, all the MPC slots work with the ambient temperature of up to 40° C.
However, when the chassis temperature exceeds 40° C, slots 0 and 11 can work with MPC1s,
MPC2s, and the 16x10GE MPC.

122 Copyright © 2018, Juniper Networks, Inc.

 Chapter 8: MX Series MPC Descriptions

Software features • Optical diagnostics and related alarms

• Support for optical transport network (OTN) on 10-Gigabit Ethernet ports
• Two packet-forwarding engines, PFE0 and PFE1. PFE0 hosts PIC0 and PIC2. PFE1 hosts PIC1
and PIC3.
• Configurable LAN-PHY and WAN-PHY mode options per 10-Gigabit Ethernet port
• See “Protocols and Applications Supported by the MPC5E for MX Series Routers” on page 359
for information about the protocols and applications that this MPC supports.

NOTE: On MX240, MX480, and MX960 routers, MPC5E powers on only if the network-services
mode on the router is configured to either enhanced-ip or enhanced-ethernet. On MX2010 and
MX2020 routers, only enhanced-ip is supported.

NOTE: A maximum of two PICs can be powered on at any one time (PIC0 or PIC2, and PIC1 or
PIC3). The other PICs must be powered off.

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

NOTE: QSFPP-40GE-LX4 is not NEBS compliant on the MX960 router in FPC slot 0 or FPC slot
11.

Power requirements • Typical: 9.68 A @ 48 V (460 W)

• At different temperatures:
55° C: 607 W
40° C: 541 W
25° C: 511 W

LEDs OK/FAIL LED, one bicolor:

• Steady green—MPC is functioning normally.

• Blinking green—MPC is transitioning online or offline.
• Red—MPC has failed.

10-Gigabit Ethernet LINK LED, one green per port:

• Green—Link is up.
• Off—Link is down or disabled.

40-Gigabit Ethernet LINK LED, one bicolor per port:

• Green—Link is up.
• Yellow—Link is disabled.
• Off—Link is down.

Related • MX Series MPC Overview on page 11

Documentation
• MPCs Supported by MX Series Routers on page 12

• MPC5E on MX Series Routers Overview

• 10-Gigabit Ethernet OTN Options Configuration Overview

Copyright © 2018, Juniper Networks, Inc. 123

MX Series Interface Module Reference

6x40GE + 24x10GE MPC5EQ

g007686
MPC5EQ-40G10G

Software release • Junos OS Release 13.3R2 and later

Description • Fixed-configuration MPC with six 40-Gigabit Ethernet ports and twenty-four 10-Gigabit Ethernet
ports
• Weight: 21 lb (9.52 kg)
• Model number: MPC5EQ-40G10G
• Name in the CLI: MPC5E 3D Q 24XGE+6XLGE

Hardware features • Line-rate throughput of up to 240 Gbps

• Supports one of the following port combinations:
• Six 40-Gigabit Ethernet ports
• Twenty-four 10-Gigabit Ethernet ports
• Three 40-Gigabit Ethernet ports and twelve 10-Gigabit Ethernet ports

• Supports up to 1 million queues per-slot

• LAN-PHY mode at 10.3125 Gbps on a per-port basis
• WAN-PHY mode at 9.95328 Gbps on a per-port basis
• Supports maximum transmission unit (MTU) size of 9,192 bytes for host bound packets. For
Junos OS 16.1R1 and later releases, the MTU size supported is 9,500 bytes.
• The ports are labeled as:
• 10-Gigabit Ethernet ports:
0/0 through 0/11
1/0 through 1/11
• 40-Gigabit Ethernet ports:
2/0 through 2/2
3/0 through 3/2

NOTE: On MX960 routers, all the MPC slots work with the ambient temperature of up to 40° C.
However, when the chassis temperature exceeds 40° C, slots 0 and 11 can work with MPC1s,
MPC2s, and the 16x10GE MPC.

Software features • Supports hierarchical QoS (HQoS)

• Optical diagnostics and related alarms
• Support for optical transport network (OTN) on 10-Gigabit Ethernet ports
• Configurable LAN-PHY and WAN-PHY mode options per 10-Gigabit Ethernet port
• Intelligent oversubscription services
• See “Protocols and Applications Supported by the MPC5E for MX Series Routers” on page 359
for information about the protocols and applications that this MPC supports.

NOTE: On MX240, MX480, and MX960 routers, MPC5E powers on only if the network-services
mode on the router is configured to either enhanced-ip or enhanced-ethernet. On MX2010 and
MX2020 routers, only enhanced-ip is supported.

124 Copyright © 2018, Juniper Networks, Inc.

 Chapter 8: MX Series MPC Descriptions

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

NOTE: QSFPP-40GE-LX4 is not NEBS compliant on the MX960 router in FPC slot 0 or FPC slot
11.

Power requirements • Typical: 9.68 A @ 48 V (460 W)

• At different temperatures:
55° C: 607 W
40° C: 541 W
25° C: 511 W

LEDs OK/FAIL LED, one bicolor:

• Steady green—MPC is functioning normally.

• Blinking green—MPC is transitioning online or offline.
• Red—MPC has failed.

10-Gigabit Ethernet LINK LED, one green per port:

• Green—Link is up.
• Off—Link is down or disabled.

40-Gigabit Ethernet LINK LED, one bicolor per port:

• Green—Link is up.
• Yellow—Link is disabled.
• Off—Link is down.

Related • MX Series MPC Overview on page 11

Documentation
• MPCs Supported by MX Series Routers on page 12

• MPC5E on MX Series Routers Overview

• 10-Gigabit Ethernet OTN Options Configuration Overview

2x100GE + 4x10GE MPC5E

Software release • Junos OS Release 13.3R3 and later

Copyright © 2018, Juniper Networks, Inc. 125

 MX Series Interface Module Reference

Description • Fixed-configuration MPC with two 100-Gigabit Ethernet ports and four 10-Gigabit Ethernet ports
• Weight: 21 lb (9.52 kg)
• Model number: MPC5E-100G10G
• Name in the CLI: MPC5E 3D 2CGE+4XGE

Hardware features • Line-rate throughput of up to 240 Gbps

• Supports up to 32,000 queues per-slot
• LAN-PHY mode at 10.3125 Gbps on a per-port basis
• WAN-PHY mode at 9.95328 Gbps on a per-port basis
• Supports maximum transmission unit (MTU) size of 9,192 bytes for host bound packets. For Junos OS 16.1R1 and later
releases, the MTU size supported is 9,500 bytes.
• The ports are labeled as:
• 10-Gigabit Ethernet ports: 0/0, 0/1, 2/0, and 2/1
• 100-Gigabit Ethernet ports: 1/0 and 3/0

NOTE: On MX960 routers, all the MPC slots work with the ambient temperature of up to 40° C. However, when the chassis
temperature exceeds 40° C, slots 0 and 11 can work with MPC1s, MPC2s, and the 16x10GE MPC.

Software features • Configurable LAN-PHY and WAN-PHY mode options per 10-Gigabit Ethernet port
• Optical diagnostics and related alarms
• Intelligent oversubscription services
• See “Protocols and Applications Supported by the MPC5E for MX Series Routers” on page 359 for information about the
protocols and applications that this MPC supports.

NOTE: On MX240, MX480, and MX960 routers, MPC5E powers on only if the network-services mode on the router is configured
to either enhanced-ip or enhanced-ethernet. On MX2010 and MX2020 routers, only enhanced-ip is supported.

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable transceivers supported on your
Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

NOTE:
• CFP2-100G-ER4-D is not NEBS compliant on the MX960 router in FPC slot 0 or FPC slot 11.
• CFP2-DCO-T-WDM-1 is not NEBS compliant on the MX960 router or the MX2020 router in FPC slot 0 or FPC slot 11. Slots
0 and 11 can only work with an ambient temperature of up to 40° C.

Power requirements • Typical: 10.52 A @ 48 V (505 W)

• At different temperatures:
55° C: 607 W
40° C: 541 W
25° C: 511 W

126 Copyright © 2018, Juniper Networks, Inc.

 Chapter 8: MX Series MPC Descriptions

LEDs OK/FAIL LED, one bicolor:

• Steady green—MPC is functioning normally.

• Blinking green—MPC is transitioning online or offline.
• Red—MPC has failed.

10-Gigabit Ethernet LINK LED, one bicolor per port:

• Green—Link is up.
• Yellow—Link is disabled.
• Off—Link is down or disabled.

100-Gigabit Ethernet LINK LED, one bicolor per port:

• Green—Link is up.
• Yellow—Link is disabled.
• Off—Link is down.

Related • MX Series MPC Overview on page 11

Documentation
• MPCs Supported by MX Series Routers on page 12

• MPC5E on MX Series Routers Overview

• 10-Gigabit Ethernet OTN Options Configuration Overview

• 100-Gigabit Ethernet OTN Options Configuration Overview

2x100GE + 4x10GE MPC5EQ

Software release • Junos OS Release 13.3R3 and later

Description • Fixed-configuration MPC with two 100-Gigabit Ethernet ports and four 10-Gigabit Ethernet ports
• Weight: 21 lb (9.52 kg)
• Model number: MPC5EQ-100G10G
• Name in the CLI: MPC5E 3D Q 2CGE+4XGE

Copyright © 2018, Juniper Networks, Inc. 127

 MX Series Interface Module Reference

Hardware features • Line rate throughput of up to 240 Gbps

• Supports up to 1 million queues per-slot
• LAN-PHY mode at 10.3125 Gbps on a per-port basis
• WAN-PHY mode at 9.95328 Gbps on a per-port basis
• Supports maximum transmission unit (MTU) size of 9,192 bytes for host bound packets. For Junos OS 16.1R1 and later
releases, the MTU size supported is 9,500 bytes.
• The ports are labeled as:
• 10-Gigabit Ethernet ports: 0/0, 0/1, 2/0, and 2/1
• 100-Gigabit Ethernet ports: 1/0 and 3/0

NOTE: On MX960 routers, all the MPC slots work with the ambient temperature of up to 40° C. However, when the chassis
temperature exceeds 40° C, slots 0 and 11 can work with MPC1s, MPC2s, and the 16x10GE MPC.

Software features • Supports hierarchical QoS (HQoS)

• Configurable LAN-PHY and WAN-PHY mode options per 10-Gigabit Ethernet port
• Optical diagnostics and related alarms
• Intelligent oversubscription services
• See “Protocols and Applications Supported by the MPC5E for MX Series Routers” on page 359 for information about the
protocols and applications that this MPC supports.

NOTE: On MX240, MX480, and MX960 routers, MPC5E powers on only if the network-services mode on the router is
configured to either enhanced-ip or enhanced-ethernet. On MX2010 and MX2020 routers, only enhanced-ip is supported.

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable transceivers supported on
your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

NOTE:
• CFP2-100G-ER4-D is not NEBS compliant on the MX960 router in FPC slot 0 or FPC slot 11.
• CFP2-DCO-T-WDM-1 is not NEBS compliant on the MX960 router or the MX2020 router in FPC slot 0 or FPC slot 11. Slots
0 and 11 can only work with an ambient temperature of up to 40° C.

Power requirements • Typical: 10.52 A @ 48 V (505 W)

• At different temperatures:
55° C: 607 W
40° C: 541 W
25° C: 511 W

128 Copyright © 2018, Juniper Networks, Inc.

 Chapter 8: MX Series MPC Descriptions

LEDs OK/FAIL LED, one bicolor:

• Steady green—MPC is functioning normally.

• Blinking green—MPC is transitioning online or offline.
• Red—MPC has failed.

10-Gigabit Ethernet LINK LED, one bicolor per port:

• Green—Link is up.
• Yellow—Link is disabled.
• Off—Link is down or disabled.

100-Gigabit Ethernet LINK LED, one bicolor per port:

• Green—Link is up.
• Yellow—Link is disabled.
• Off—Link is down.

Related • MX Series MPC Overview on page 11

Documentation
• MPCs Supported by MX Series Routers on page 12

• MPC5E on MX Series Routers Overview

• 10-Gigabit Ethernet OTN Options Configuration Overview

• 100-Gigabit Ethernet OTN Options Configuration Overview

MPC6E

Software release • Junos OS Release 13.3R2 and later

For information about which MICs are supported on this MPC, “MIC/MPC Compatibility” on page 26.

Description • Two slots for MICs

• Weight: 27.4 lb (12.43 kg) (net weight without blank panels)
• Model number: MX2K-MPC6E
• Name in the CLI: MPC6E 3D

Hardware features • Two slots for MICs

• Line-rate throughput of up to 480 Gbps
• Field-removable septum, to accommodate future full-height MICs
• Supports maximum transmission unit (MTU) size of 9,192 bytes for host bound packets. For
Junos OS 16.1R1 and later releases, the MTU size supported is 9,500 bytes.

Copyright © 2018, Juniper Networks, Inc. 129

 MX Series Interface Module Reference

Maximum Power Power requirement: 20.9 A @ 52 V (880 W; plus 104 W for each MIC)
Requirements
MX2K-MPC6E:

• Typical: 648 W
• 880 W at 55° C
• 834 W at 40° C
• 824 W at 25° C

Software features • Optical diagnostics and related alarms

• Configurable LAN-PHY and WAN-PHY mode options per 10-Gigabit Ethernet port
• Two Packet Forwarding Engines for each MIC slot
• Intelligent oversubscription services
• See “Protocols and Applications Supported by the MPC6E for MX2000 Routers” on page 366
for information about the protocols and applications that this MPC supports.

LEDs OK/FAIL LED, one bicolor:

• Steady green—MPC is functioning normally.

• Blinking green—MPC is transitioning online or offline.
• Red—MPC has failed.

LINK LED, one bicolor per port:

• Green—Link is up.
• Yellow—Link is disabled.
• Off—Link is down.

Related • MX Series MPC Overview on page 11

Documentation
• MPCs Supported by MX Series Routers on page 12

• MPC6E on MX Series Routers Overview

MPC7E (Multi-Rate)

Software release • Junos OS Release 15.1F4 with Junos Continuity.

• Junos OS Release 15.1F6 and later.
• Junos OS release 16.1R1 and later.

Description • Fixed-configuration MPC with 10-Gbps, 40-Gbps, and 100-Gbps port speeds
• Weight: 15.7 lb (7.12 kg)
• Model number: MPC7E-MRATE
• Name in the CLI: MPC7E-MRATE

130 Copyright © 2018, Juniper Networks, Inc.

 Chapter 8: MX Series MPC Descriptions

Hardware features • Line-rate throughput of up to 480 Gbps on MX240, MX480, and MX960 routers.
• Line-rate throughput of up to 400 Gbps on MX2000 routers with SFB, and up to 430 Gbps on MX2000 routers with SFB2.
• Junos Trio chipsets for increased scaling for bandwidth, subscribers, and services
• Twelve Gigabit Ethernet ports that can be configured as 40-Gigabit Ethernet port or as 4 10-Gigabit Ethernet port using a
breakout cable. The ports support quad small-form factor pluggable plus (QSFP+) transceivers.
• Four out of the twelve ports can be configured as 100-Gigabit Ethernet ports. Port numbers 0/2, 0/5, 1/2 and 1/5 are the four
100-Gigabit Ethernet ports.
• You can configure different combination of port speeds as long as the aggregate capacity per group of six ports labeled 0/0
through 0/5 does not exceed 240 Gbps. Similarly, aggregate capacity per group of the other six ports labeled 1/0 through
1/5 should not exceed 240 Gbps.
• Requires high-capacity power supplies, high-capacity fan trays, and SCBE2 on MX240, MX480, and MX960 routers.
• Requires an adapter card to be housed in MX2000 routers.
• The ports are labeled as (with the MPC orientation as shown in the above figure):
• 10-Gigabit Ethernet or 40-Gigabit Ethernet ports:
0/0, 0/1, 0/2 100G, 0/3, 0/4, 0/5 100G, 1/0, 1/1, 1/2 100G, 1/3, 1/4, and 1/5 100G
• 100-Gigabit Ethernet ports:
0/2 100G, 0/5 100G, 1/2 100G and 1/5 100G

NOTE: Only ports marked 100G support 100-Gigabit Ethernet speed using QSFP28 transceivers.

• Supports maximum transmission units (MTUs) from 256 bytes through 16,000 bytes for transit traffic, and from 256 bytes
through 9,500 bytes for host bound packets.

NOTE: On MX960 routers, all the MPC slots can be occupied by MPC7E (Multi-Rate) at an ambient temperature of up to
40° C and at any altitude. All the MPC slots can be occupied by MPC7E (Multi-Rate) at temperatures of up to 55° C and at
sea level. At an ambient temperature of 55° C and above, and at an altitude above sea level, slot 11 cannot host
MPC7E (Multi-Rate).

Software features • Supports rate selectability at the port level.

• By default, the ports are configured as 10-Gigabit Ethernet ports.
• Optical diagnostics and related alarms
• See “Protocols and Applications Supported by the MPC7E for MX Series Routers” on page 373 for information about the
protocols and applications that the MPC7E supports.

NOTE: On MX240, MX480, and MX960 routers, MPC7E powers on only if the network-services mode on the router is configured
as either enhanced-ip or enhanced-ethernet. On MX2000 router no additional configuration is required as by default the
router operates in enhanced-ip mode.

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable transceivers supported on your
Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

Power requirements • At different temperatures:

55° C: 545 W
40° C: 465 W
25° C: 440 W

Copyright © 2018, Juniper Networks, Inc. 131

 MX Series Interface Module Reference

LEDs OK/FAIL LED, one bicolor:

• Steady green—MPC is functioning normally.

• Yellow—MPC has failed.

LINK LED, one green per port (4 per QSFP+ cage):

• Steady green—Link is up.

• Off—Link is down or disabled.

Related • MPC7E (Multi-Rate) on MX Series Routers Overview

Documentation
• MX Series MPC Overview on page 11

• MPCs Supported by MX Series Routers on page 12

• Junos Continuity Software User Guide (Junos OS Release 14.1R4 and Later Releases)

MPC7E 10G

g009054
MPC7E-10G

Software release • Junos OS Release 15.1F5 with Junos Continuity

• Junos OS release 16.1R1 and later

Description • Fixed-configuration MPC with forty 10-Gbps ports

• Weight: 17 lb (7.7 kg)
• Model number: MPC7E-10G
• Name in the CLI: MPC7E 3D 40XGE

Hardware features • Line-rate throughput of up to 400 Gbps on MX240, MX480, and MX960 routers.
• Line-rate throughput of up to 400 Gbps on MX2000 routers.
• Junos Trio chipsets for increased scaling for bandwidth, subscribers, and services.
• Forty 10-Gigabit Ethernet ports. The ports support SFP+ transceivers.
• Requires high-capacity power supplies, high-capacity fan trays, and SCBE2 on MX240, MX480, and MX960 routers.
• Requires an adapter card to be housed in MX2000 routers.
• Supports maximum transmission units (MTUs) from 256 bytes through 16,000 bytes for transit traffic, and from 256 bytes
through 9,500 bytes for host bound packets.
• The ports are labeled as (with the MPC orientation as shown in the figure):
• 0/0 through 0/9
• 0/10 through 0/19
• 1/0 through 1/9
• 1/10 through 1/19 Greg and I were volunteers for Project C

132 Copyright © 2018, Juniper Networks, Inc.

 Chapter 8: MX Series MPC Descriptions

Software features • Supports MACsec using the following encryption algorithms: gcm-aes-128 and gcm-aes-256.
• SupportsHyper mode to speed up packet processing.
• Supports Flexible queuing using an add-on license to support 32,000 queues per line card, including queues on both ingress
and egress interfaces. You can use an additional license to support up to 512,000 queues.
• Optical diagnostics and related alarms
• See “Protocols and Applications Supported by the MPC7E for MX Series Routers” on page 373 for information about the
protocols and applications that MPC7Es support.

NOTE: On MX240, MX480, and MX960 routers, MPC7E powers on only if the network-services mode on the router is configured
as either enhanced-ip or enhanced-ethernet. On MX2000 routers, no additional configuration is required because by default
the router operates in enhanced-ip mode.

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable transceivers supported on your
Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

• 10GBASE-ZR (model number: SFPP-10G-ZR-OTN-XT)

NOTE: MPC7E 10G does not support OTN rates.

• 10GBASE-ZR (model number: SFPP-10G-DT-ZRC2)

NOTE:
• Supported from Junos OS release 16.1R1 and later.

• Supports 40° C ambient temperature operation at any altitude, and 55° C ambient temperature operation at sea level.

Power requirements • Typical: 405 W

• At different temperatures:
55° C: 500 W
40° C: 465 W
25° C: 430 W

NOTE: On MX960 routers, all the MPC slots can be occupied by MPC7E 10G at an ambient temperature of up to 40° C and
at any altitude. All the MPC slots can be occupied by MPC7E 10G at temperatures of up to 55° C and at sea level. At an ambient
temperature of 55° C and above, and at an altitude above sea level, slot 11 cannot host MPC7E 10G.

LEDs OK/FAIL LED, one bicolor:

• Steady green—MPC is functioning normally.

• Yellow—MPC has failed.

Link LED, one green per port:

• Steady green—Link is up.

• Off—Link is down or disabled.

Related • MPC7E 10G on MX Series Routers Overview

Documentation
• MX Series MPC Overview on page 11

• MPCs Supported by MX Series Routers on page 12

• Junos Continuity Software User Guide (Junos OS Release 14.1R4 and Later Releases)

Copyright © 2018, Juniper Networks, Inc. 133

 MX Series Interface Module Reference

MPC8E

Software release • Junos OS Release 15.1F5 with Junos Continuity

• Junos OS release 16.1R1 and later

Description • Weight: 31.4 lb (14.24 kg) (net weight without blank panels)
• Model number: MX2K-MPC8E
• Name in the CLI: MPC8E 3D

Hardware features • Line-rate throughput of up to 960 Gbps on the MX2000 routers.

• Line-rate throughput of up to 1600 Gbps (1.6 Tbps) on the MX2000 routers with software upgrade.

NOTE: Starting from Junos OS Release 16.1R1, you can upgrade MPC8E to provide an increased bandwidth of 1600 Gbps
(1.6 Tbps) by using an add-on license. After you perform the upgrade, MPC8E provides a bandwidth of 1.6 Tbps, which is
equivalent to the bandwidth of “MPC9E” on page 135. However, the MPC continues to be identified as MPC8E.

• Four Packet Forwarding Engines, each providing a maximum bandwidth of 240 Gbps in normal mode and 400 Gbps in
1.6Tbps upgraded mode. A license is required to operate in 1.6 Tbps upgraded mode.
• Supports two MICs. For information about which MICs are supported on this MPC, see “MIC/MPC Compatibility” on page 26.
• Junos Trio chipsets for increased scaling for bandwidth, subscribers, and services.
• Supports the Switch Fabric Boards SFB and SFB2. When MPC8E is used with SFB, the line-rate throughput is limited to
800 Gbps.
• Supports maximum transmission units (MTUs) from 256 bytes through 16,000 bytes for transit traffic, and from 256 bytes
through 9,500 bytes for host bound packets.

Software features • Dynamic power management for effective utilization of available power.
• Inline flow monitoring for higher scalability and performance.
• Flexible queuing using an add-on license to support 32,000 queues per line card, including queues on both ingress and
egress interfaces. You can use an additional license to support up to 512,000 queues per slot or 1,000,000 queues per slot.
• Hyper mode to speed up packet processing.
• Optical diagnostics and related alarms.

For more information about features supported on MPC8E, see “Protocols and Applications Supported by the MPC8E and
MPC9E on the MX2010 and MX2020 Routers” on page 382.

134 Copyright © 2018, Juniper Networks, Inc.

 Chapter 8: MX Series MPC Descriptions

Power requirements Normal mode with line-rate throughput of 960 Gbps:

(without MICs) • Typical: 688 W

• At different temperatures:
55° C: 805 W
40° C: 720 W
25° C: 690 W

Upgrade mode with line-rate throughput of 1.6 Tbps:

• Typical: 838 W
• At different temperatures:
55° C: 1018 W
40° C: 870 W
25° C: 840 W

LEDs OK/FAIL LED, one bicolor:

• Steady green—MPC is functioning normally.

• Yellow—MPC has failed.

Related • MPC8E on MX Series Routers Overview

Documentation
• MX Series MPC Overview on page 11

• MPCs Supported by MX Series Routers on page 12

• Junos Continuity Software User Guide (Junos OS Release 14.1R4 and Later Releases)

• Understanding Rate Selectability

MPC9E

Software release • Junos OS Release 15.1F5 with Junos Continuity

• Junos OS release 16.1R1 and later

Description • Weight: 31.4 lb (14.24 kg) (net weight without blank panels)
• Model number: MX2K-MPC9E
• Name in the CLI: MPC9E 3D

Copyright © 2018, Juniper Networks, Inc. 135

 MX Series Interface Module Reference

Hardware features • Line-rate throughput of up to 1600 Gbps (1.6 Tbps) on MX2000 routers.
• Four Packet Forwarding Engines, each providing a maximum bandwidth of 400 Gbps.
• Supports two MICs. For information about which MICs are supported on this MPC, see “MIC/MPC Compatibility” on page 26.
• Junos Trio chipsets for increased scaling for bandwidth, subscribers, and services
• Supports the Switch Fabric Boards SFB and SFB2. When MPC9E is used with SFB, the line-rate throughput is limited to
800 Gbps.
• Supports maximum transmission units (MTUs) from 256 bytes through 16,000 bytes for transit traffic, and from 256 bytes
through 9,500 bytes for host bound packets.

Software features • Dynamic Power Management for effective utilization of available power.
• Inline Active Flow Monitoring for higher scalability and performance.
• Flexible Queuing Mode using an add-on license to support 32,000 queues per line card, including queues on both ingress
and egress interfaces. You can use an additional license to support up to 512,000 queues per slot or 1,000,000 queues per
slot.
• Hyper Mode to speed up packet processing.
• Optical diagnostics and related alarms.

For more information about features supported on MPC9E, see “Protocols and Applications Supported by the MPC8E and
MPC9E on the MX2010 and MX2020 Routers” on page 382.

Power requirements • Typical: 838 W

• At different temperatures:
(without MICs)
55° C: 1018 W
40° C: 870 W
25° C: 840 W

LEDs OK/FAIL LED, one bicolor:

• Steady green—MPC is functioning normally.

• Yellow—MPC has failed.

Related • MPC9E on MX Series Routers Overview

Documentation
• MX Series MPC Overview on page 11

• MPCs Supported by MX Series Routers on page 12

• Junos Continuity Software User Guide (Junos OS Release 14.1R4 and Later Releases)

• Understanding Rate Selectability

MX10003 MPC (Multi-Rate)

Software release • Junos OS release 17.3R1 and later

136 Copyright © 2018, Juniper Networks, Inc.

 Chapter 8: MX Series MPC Descriptions

Description • Weight: 30 lb (13.61 kg) (net weight without blank panel and without any MIC in slot 1)
• Model number: MX10003-LC2103
• Power requirement:
715 W at 55° C
660 W at 25° C
• Name in the CLI: LC2103

Hardware features • The MX10003 MPC is a 1.2-Terabit capable MPC with three Packet Forwarding Engine complexes (that is, three EA ASICs).
The EA ASIC operates in 400G mode.
• The Packet Forwarding Engine is based on the third generation of the Trio chpiset architecture---namely, the EA (Eagle)
ASIC. The Packet Forwarding Engine offers 400 Gbps of WAN and fabric bandwidth each.
• MX10003 MPC has six built-in QSFP+ optics ports, and one MIC slot.
• Supports Multi-Rate Ethernet Modular Interface Card (MIC) (model numbers: JNP-MIC1 and JNP-MIC1-MACSEC), and the
fixed-port PIC (6xQSFPP). For information about which MICs are supported on this MPC, see “MIC/MPC Compatibility” on
page 26.
• Supports maximum transmission units (MTUs) from 256 bytes through 16,000 bytes for transit traffic, and from 256 bytes
through 9,500 bytes for host bound packets.

Software features • Dynamic Power Management for effective utilization of available power.
• Inline Active Flow Monitoring for higher scalability and performance.
• Flexible Queuing Mode to support 32,000 queues per line card, including queues on both ingress and egress interfaces.
Supports up to 512,000 queues per slot or 768,000 queues per slot.
• Hyper Mode to speed up packet processing.
• Optical diagnostics and related alarms.

For more information about features supported on MPC9E, see “Protocols and Applications Supported by the MX10003 MPC
(Multi-Rate) on the MX10003 Router” on page 391.

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable transceivers supported on your
Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

Power requirements • At different temperatures:

55° C: 715 W
(without MICs)
25° C: 660 W

LEDs OK/FAIL LED, one bicolor:

• Steady green—MPC is functioning normally and the link is up.

• Off—MPC is plugged-in but not powered on.
• Red—MPC has failed.

For information on the lane LEDs (Lo, L1, L2, and L3), see MPC and MIC Lane LED Scheme Overview.

Table 23 on page 138 summarize the port speed capability of MX10003 MPCs.

Copyright © 2018, Juniper Networks, Inc. 137

MX Series Interface Module Reference

Table 23: MX10003 MPC (Multi-Rate) Port Speed

MIC Port Number Port Speed Supported

PIC 0 0-5 40 Gigabit Ethernet

4X10-Gigabit Ethernet

PIC 1 0-11 100 Gigabit Ethernet

40 Gigabit Ethernet

4X10-Gigabit Ethernet

Related • MPC and MIC Lane LED Scheme Overview

Documentation
• Configuring Rate Selectability on MX10003 MPC to Enable Different Port Speeds

• MX10003 MPC Rate-Selectability Overview

• Understanding Interface Naming Conventions for MX10003 MPC

• Understanding Rate Selectability

• MX Series MPC Overview on page 11

• MPCs Supported by MX Series Routers on page 12

• Replacing an MX10003 MIC

138 Copyright © 2018, Juniper Networks, Inc.

CHAPTER 9

MX Series MIC Descriptions

• ATM MIC with SFP on page 140

• DS3/E3 MIC on page 143
• Gigabit Ethernet MIC with SFP on page 147
• Gigabit Ethernet MIC with SFP (E) on page 150
• Gigabit Ethernet MIC with SFP (EH) on page 154
• 10-Gigabit Ethernet MICs with XFP on page 155
• 10-Gigabit Ethernet MIC with SFP+ (10 Ports) on page 157
• 10-Gigabit Ethernet MIC with SFP+ (24 Ports) on page 159
• 10-Gigabit Ethernet OTN MIC with SFP+ (24 Ports) on page 160
• 40-Gigabit Ethernet MIC with QSFP+ on page 162
• 100-Gigabit Ethernet MIC with CFP on page 163
• 100-Gigabit Ethernet MIC with CXP on page 165
• 100-Gigabit Ethernet MIC with CXP (4 Ports) on page 166
• 100-Gigabit Ethernet MIC with CFP2 on page 167
• 100-Gigabit DWDM OTN MIC with CFP2-ACO on page 169
• Channelized SONET/SDH OC3/STM1 (Multi-Rate) MICs with SFP on page 178
• Channelized OC3/STM1 (Multi-Rate) Circuit Emulation MIC with SFP on page 183
• Channelized OC3/STM1 (Multi-Rate) Circuit Emulation MIC with SFP (H) on page 185
• Channelized E1/T1 Circuit Emulation MIC on page 188
• Channelized E1/T1 Circuit Emulation MIC (H) on page 191
• Tri-Rate MIC on page 194
• MIC MRATE on page 198
• Multiservices MIC on page 200
• SONET/SDH OC3/STM1 (Multi-Rate) MICs with SFP on page 202
• Multi-Rate Ethernet MIC on page 206
• SONET/SDH OC192/STM64 MIC with XFP on page 209

Copyright © 2018, Juniper Networks, Inc. 139

MX Series Interface Module Reference

ATM MIC with SFP

Figure 8: 8-Port ATM MIC with SFP

MIC-3D-OCx-ATM

g006584
Software release • Junos 12.1 and later

For information on which MPCs support this MIC, see “MIC/MPC Compatibility” on page 26. For
information on which MICs are supported on MX Series routers, see “MICs Supported by MX Series
Routers” on page 18.

Description • Rate-selectable using one of the following rates:

• 8-port OC3
• 2-port OC12

• Power requirement: 0.73 A @ 48 V (35 W)

• Weight: 1.2 lb (0.54 kg)
• Model number: MIC-3D-8OC3-2OC12-ATM
• Name in the CLI: 3D 80C3 20C12 ATM

Hardware features • High-performance parsing of SONET/SDH frames

• Packet segmentation and reassembly (SAR) management and output port queuing
• Packet buffering, Layer 2 parsing
• Line rate throughput for each port

140 Copyright © 2018, Juniper Networks, Inc.

 Chapter 9: MX Series MIC Descriptions

Software features • Circuit cross-connect (CCC) for leveraging ATM access networks
• User-configurable virtual circuit (VC) and virtual path (VP) support
• Support for idle cell or unassigned cell transmission
• OAM fault management processes alarm indication signal (AIS), remote defect indication
(RDI) cells, and loop cells
• Point-to-point and point-to-multipoint mode Layer 2 counters per VC and per VP
• Local and remote loopback
• Simple Network Management Protocol (SNMP):
• Management Information Base (MIB) 2 (RFC 1213)
• ATM MIB (RFC 1695)
• SONET MIB
• PWE3 MIB (RFC 5603)
• PW-ATM-MIB (RFC 5605)
• PW-FRAME-MIB (RFC 5601)
• MIB for CoS

• Unspecified bit rate (UBR), non-real-time variable bit rate (VBR), and constant bit rate (CBR)
traffic shaping
• Per-VC or per-VP traffic shaping
• Support for F4 OAM cells (AIS, RDI, Loopback, and Continuity Check)
• Support for F5 OAM cells (AIS, RDI, Loopback, and Continuity Check)
• Support for 16 bit VCI range
• Encapsulations:
• atm-ccc-cell-relay (Junos 12.1 and later)
• atm-ccc-vc-mux (Junos 12.1 and later)
• atm-snap (Junos 12.2 and later)
• atm-vc-mux (Junos 12.2 and later)
• atm-tcc-snap (Junos 13.3 and later)
• atm-tcc-vc-mux (Junos 13.3 and later)
• vlan-vci-ccc (Junos 16.1 and later)
• ether-over-atm-llc
• ppp-over-ether-over-atm-llc
• atm-ppp-llc
• atm-ppp-vc-mux

NOTE: Inline MLPPP is not supported on this MIC.

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

Copyright © 2018, Juniper Networks, Inc. 141

MX Series Interface Module Reference

LEDs OK/FAIL LED, one bicolor:

• Green—MIC is functioning normally.

• Red—MIC has failed.

Link LED, one green per port:

• Off—No link.
• On steadily—Link is up.
• Blinking—Online with alarms for remote failures
• Blinking rapidly—Active with a local alarm; router has detected a failure

Alarms, errors, and • Alarm indication signal—line (AIS-L)

events • Alarm indication signal—path (AIS-P)
• Bit error rate—signal degrade (BERR-SD)
• Bit error rate—signal fail (BERR-SF)
• Loss of cell delineation (LOC)
• Loss of frame (LOF)
• Loss of pointer (LOP-P)
• Loss of signal (LOS)
• Payload mismatch (PLM-P)
• Payload unequipped (unequipped STS at path level) (UNEQ-P)
• Remote defect indication—line (RDI-L)
• Remote defect indication—path (RDI-P)
• Error detection:

• Bit interleaved parity errors B1, B2, B3

• Errored seconds (ES-S, ES-L, ES-P)
• Far-end bit errors, remote error indication—line (REI-L), far-end line coding violations (CV-LFE)
• Far-end bit errors, remote error indication—path (REI-P), far-end path coding violations
(CV-PFE)
• Far-end errored seconds (ES-LFE, ES-PFE)
• Far-end severely errored seconds (SES-LFE, SES-PFE)
• Far-end unavailable seconds (UAS-LFE, UAS-PFE)
• Severely errored framing (SEF)
• Severely errored framing seconds (SEFS-S)
• Severely errored seconds (SES-S, SES-L, SES-P)
• Unavailable seconds (UAS-L, UAS-P)

142 Copyright © 2018, Juniper Networks, Inc.

 Chapter 9: MX Series MIC Descriptions

NOTE: MIC-3D-8OC3-2OC12-ATM Revision 8 and Revision 22 are supported

only by the following Junos OS releases:

• Junos OS Release 12.3—12.3R9 and later

• Junos OS Release 13.3—13.3R6 and later

• Junos OS Release 14.1—14.1R4 and later

• Junos OS Release 14.2—14.2R3 and later

• Junos OS Release 15.1 and later

You must upgrade to a supported Junos OS release to use

MIC-3D-8OC3-2OC12-ATM Revision 8 and Revision 22 and later.

Related • MX Series MIC Overview on page 17

Documentation

DS3/E3 MIC

Figure 9: DS3/E3 MIC

MIC-3D-8DS3-E3
MIC-3D-8DS3-E3

Tx0

Tx1

Tx2

Tx3

Tx4

Tx5

Tx6

Tx7
0
1
2
3
4
5
6
7

g006095
Rx0

Rx1

Rx2

Rx3

Rx4

Rx5

Rx6

Rx7

Software release • Junos OS Release 11.4 and later

For information on which MPCs support this MIC, see “MIC/MPC Compatibility” on page 26. For
information on which MICs are supported on MX Series routers, see “MICs Supported by MX Series
Routers” on page 18.

Copyright © 2018, Juniper Networks, Inc. 143

MX Series Interface Module Reference

Description • Eight E3 or DS3 ports

• DS3/E3 MIC ports can be configured as one of the following:
• 8 clear-channel DS3 ports
• 8 channelized DS3 ports
• 8 clear-channel E3 ports

NOTE: You can upgrade the DS3/E3 MIC with the S-MIC-3D-8CHDS3 software license
(purchased separately) to support DS3 channelization. Channelized DS3/E3 MIC is supported
only on queuing MPCs. On the MX80 router, you also need an S-MX80-Q software license.

• DS3 or E3 is configurable on a per-port granularity

• DS3 channelization for the 8-port Channelized DS3/E3 MIC:
• 8 DS3 channels
• 224 DS1 channels
• 2038 DS0 channels

• Power requirement: 4.0 A @ 9 V (36W)

• Weight: 4.4 lb (2 kg)
• Model numbers:
• DS3/E3 MIC: MIC-3D-8DS3-E3
• Channelized DS3/E3 MIC: MIC-3D-8CHDS3-E3-B

Hardware features • Ports are numbered 0 through 7, Tx0 through Tx7 and Rx0 through Rx7

144 Copyright © 2018, Juniper Networks, Inc.

 Chapter 9: MX Series MIC Descriptions

Software features • Maximum transmission units (MTUs) of up to 9192 bytes

• Framing: M13, C-bit parity, framed clear channel
• Subrate and scrambling:

NOTE: Only DS3 interfaces support subrate and scrambling.

• Digital Link/Quick Eagle

• Kentrox
• Larscom
• ADTRAN
• Verilink

• Internal and look clocking

• DS3 far-end alarm and control (FEAC) channel
• Full bit error rate test (BERT) for DS0, DS1, and DS3
• Encapsulations:
• MPLS fast reroute
• MPLS CCC (circuit cross-connection)
• MPLS TCC (translational cross-connection)
• Cisco High-Level Data Link Control (cHDLC)
• Cisco HDLC CCC
• Cisco HDLC TCC
• Point-to-Point Protocol (PPP)
• PPP for CCC
• PPP for TCC
• Flexible Frame Relay
• Frame Relay
• Frame Relay for CCC
• Frame Relay for TCC
• PPP over Frame Relay

NOTE: Ethernet over Frame Relay is not supported.

• Encapsulations available only for Channelized DS3/E3 MIC (Junos OS Release 12.1 and later):
• Multilink Point-to-Point Protocol (MLPPP)
• Multiclass MLPPP
• Multilink Frame Relay (MLFR) end-to-end (FRF.15)
• Multilink Frame Relay (MLFR) UNI NNI (FRF.16, also referred to as MFR)
• Compressed Real-Time Transport Protocol (CRTP)

NOTE: When you configure multilink services on a MIC in an MX Series router, ensure that a
Multiservices DPC is present in the same router.

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

• Coaxial:
Custom 10-ft (3-m) mini-SMB to BNC cable (model number: CBL-DS3-E3-M-S), set of 8
cables (bundled RX and TX)

Copyright © 2018, Juniper Networks, Inc. 145

MX Series Interface Module Reference

LEDs OK/FAIL LED, one bicolor:

• Green—MIC is functioning normally

• Red—MIC has failed

Link LED, one green per port:

• Off—Not enabled
• Green—Online with no alarms or failures
• Yellow—Online with alarms for remote failures
• Red—Active with a local alarm; router has detected a failure

Alarms, errors, and DS3 alarms:

events
• Alarm indication signal (AIS)
• Loss of frame (LOF)
• Loss of signal seconds (LOS)
• Phase lock loop (PLL)

DS3 error detection:

• C-bit code violations (CCV)

• C-bit errored seconds (CES)
• C-bit severely errored seconds (CSES)
• CRC errors
• Excessive zeros (EXZ)
• Far-end block error (FEBE)
• Far-end receive failure (FERF)
• Line errored seconds (LES)
• Parity bit (P-bit) code violations (PCV)
• Parity bit (P-bit) errored seconds (PES)
• Parity bit (P-bit) severely errored framing seconds (PSES)
• Severely errored framing seconds (SEFS)
• Unavailable seconds (UAS)

Related • MX Series MIC Overview on page 17

Documentation

146 Copyright © 2018, Juniper Networks, Inc.

 Chapter 9: MX Series MIC Descriptions

Gigabit Ethernet MIC with SFP

Figure 10: 20-Port Gigabit Ethernet MIC with SFP

MIC-3D-20GE-SFP

g006660
Software release • Junos 10.1 and later

For information on which MPCs support this MIC, see “MIC/MPC Compatibility” on page 26. For
information on which MICs are supported on MX Series routers, see “MICs Supported by MX Series
Routers” on page 18.

Description • 20 Gigabit Ethernet ports

• Power requirement: 0.77 A @ 48 V (37 W)
• Weight: 1.2 lb (0.54 kg)
• Model number: MIC-3D-20GE-SFP
• Name in the CLI: 3D 20GE SFP

Hardware features • High-performance throughput on each port at speeds up to 1 Gbps

• Autonegotiation between Gigabit Ethernet circuit partners
• Up to 20-Gbps of full-duplex traffic
• Maximum transmission units (MTUs) of up to 9192 bytes

Software features • Optical diagnostics and related alarms

• Virtual Router Redundancy Protocol (VRRP) support
• IEEE 802.1Q virtual LANs (VLANs) support
• Remote monitoring (RMON) EtherStats
• Source MAC learning
• MAC accounting and policing—Dynamic local address learning of source MAC addresses
• Flexible Ethernet encapsulation
• Multiple tag protocol identifiers (TPID)

Interfaces Syntax: ge-fpc/pic/port where:

• fpc: Slot in the router where the MPC is installed

• pic: The logical PIC number on the MIC, numbered 0, 1, 2, and 3.
• port: 0 through 9

For example, ge-3/3/0 is the interface for port 0 in PIC 3 on the MPC installed in slot 3.

Figure 11 on page 148, Figure 12 on page 149, and Figure 13 on page 149 show examples of the port
numbering for the Gigabit Ethernet MIC with SFP installed in an MX960, MX480, and MX240,
respectively.

Copyright © 2018, Juniper Networks, Inc. 147

MX Series Interface Module Reference

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

LEDs OK/FAIL LED, one bicolor:

• Green—MIC is functioning normally.

• Red—MIC has failed.

Link LED, one green per port:

• Off—No link.
• On steadily—Link is up.

Port Numbering
Figure 11 on page 148, Figure 12 on page 149, and Figure 13 on page 149 show examples of
the port numbering for the Gigabit Ethernet MIC with SFP on the MX960, MX480, and
MX240, respectively.

Figure 11: Port Numbering for the Gigabit Ethernet MIC with SFP (MX960)

0 1 2 3

0 1 2 3 4 5 0 1 2 6 7 8 9 10 11

148 Copyright © 2018, Juniper Networks, Inc.

 Chapter 9: MX Series MIC Descriptions

Figure 12: Port Numbering for the Gigabit Ethernet MIC with SFP (MX480)

Figure 13: Port Numbering for Gigabit Ethernet MIC with SFP (MX240)

Copyright © 2018, Juniper Networks, Inc. 149

MX Series Interface Module Reference

Related • MX Series MIC Overview on page 17

Documentation

Gigabit Ethernet MIC with SFP (E)

Figure 14: 20-Port Gigabit Ethernet MIC with SFP (E)

Software release • Junos 13.2R2 and later

For information on which MPCs support this MIC, see “MIC/MPC Compatibility” on page 26. For
information on which MICs are supported on MX Series routers, see “MICs Supported by MX Series
Routers” on page 18.

Description • 20 Gigabit Ethernet ports

• Power requirement: 0.77 A @ 48 V (37 W)
• Weight: 1.2 lb (0.54 kg)
• Model number: MIC-3D-20GE-SFP-E
• Name in the CLI: 3D 20x 1GE(LAN)-E,SFP

Hardware features • High-performance throughput on each port at speeds up to 1 Gbps

• Auto-negotiation between Gigabit Ethernet circuit partners
• Up to 20-Gbps of full-duplex traffic
• Maximum transmission units (MTUs) of up to 9192 bytes
• Environmentally hardened for 32° F (0° C) to 131° F (55° C) operating temperatures
• SEC PHY
• Timing PHY

Software features • Optical diagnostics and related alarms

• Virtual Router Redundancy Protocol (VRRP) support
• IEEE 802.1Q virtual LANs (VLANs) support
• Remote monitoring (RMON) EtherStats
• Source MAC learning
• MAC accounting and policing—Dynamic local address learning of source MAC addresses
• Flexible Ethernet encapsulation
• Multiple tag protocol identifiers (TPID)
• Precision Time Protocol (PTP) or IEEE 1588v2
• Media Access Control Security (MACsec)

150 Copyright © 2018, Juniper Networks, Inc.

 Chapter 9: MX Series MIC Descriptions

Interfaces Syntax: ge-fpc/pic/port where:

• fpc: Slot in the router where the MPC is installed. The MPCs are represented in the CLI as FPC0
through FPC19.
• pic: The logical PIC number on the MIC, numbered 0 or 1. Figure 15 on page 152,
Figure 16 on page 153, and Figure 17 on page 153 illustrate the port numbering for the Gigabit
Ethernet MIC with SFP (E) installed in the MX960, MX480, and MX240, respectively.
• port: 0 through 9.

For example, ge-3/1/0 is the interface for port 0 in PIC 1 on the MPC installed in slot 3.

Figure 15 on page 152, Figure 16 on page 153, and Figure 17 on page 153 illustrate the port numbering
for the MIC-3D-20GE-SFP-E installed in an MX960, MX480, and MX280, respectively.

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

LEDs OK/FAIL LED, one bicolor:

• Green—MIC is functioning normally.

• Red—MIC has failed.

Link LED, one green per port:

• Off—No link.
• On steadily—Link is up.

Copyright © 2018, Juniper Networks, Inc. 151

MX Series Interface Module Reference

Figure 15: Port Numbering for the MIC-3D-20GE-SFP-E (MX960)

152 Copyright © 2018, Juniper Networks, Inc.

 Chapter 9: MX Series MIC Descriptions

Figure 16: Port Numbering for the MIC-3D-20GE-SFP-E (MX480)

Figure 17: Port Numbering for the MIC-3D-20GE-SFP-E (MX240)

Copyright © 2018, Juniper Networks, Inc. 153

MX Series Interface Module Reference

Related • MX Series MIC Overview on page 17

Documentation

Gigabit Ethernet MIC with SFP (EH)

Figure 18: 20-Port Gigabit Ethernet MIC with SFP (EH)

Software release • Junos 13.2R2 and later

For information on which MPCs support this MIC, see “MIC/MPC Compatibility” on page 26. For
information on which MICs are supported on MX Series routers, see “MICs Supported by MX Series
Routers” on page 18.

Description • 20 Gigabit Ethernet ports

• Power requirement: 0.77 A @ 48 V (37 W)
• Weight: 1.2 lb (0.54 kg)
• Model number: MIC-3D-20GE-SFP-EH
• Name in the CLI: 3D 20x 1GE(LAN)-EH,SFP

Hardware features • High-performance throughput on each port at speeds up to 1 Gbps

• Autonegotiation between Gigabit Ethernet circuit partners
• Up to 20-Gbps of full-duplex traffic
• Maximum transmission units (MTUs) of up to 9192 bytes
• Environmentally hardened for –40° F (–40° C) to 149° F (65° C) operating temperatures
• SEC PHY
• Timing PHY

Software features • Optical diagnostics and related alarms

• Virtual Router Redundancy Protocol (VRRP) support
• IEEE 802.1Q virtual LANs (VLANs) support
• Remote monitoring (RMON) EtherStats
• Source MAC learning
• MAC accounting and policing—Dynamic local address learning of source MAC addresses
• Flexible Ethernet encapsulation
• Multiple tag protocol identifiers (TPID)
• Precision Time Protocol (PTP) or IEEE 1588v2
• Media Access Control Security (MACsec)

154 Copyright © 2018, Juniper Networks, Inc.

 Chapter 9: MX Series MIC Descriptions

Interfaces Syntax: ge-fpc/pic/port where:

• fpc: Slot in the router where the MPC is installed

• pic: 0 (left grouping of 10 ports) or 1 (right grouping of 10 ports) when installed in MIC slot 0; 2
(left grouping of 10 ports) or 3 (right grouping of 10 ports) when installed in MIC slot 1
• port: 0 through 9

For example, ge-1/3/0 is the interface for port 0 in the right grouping of ports on the MIC installed
in MIC slot 1 on an MPC installed in slot 1.

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

LEDs OK/FAIL LED, one bicolor:

• Green—MIC is functioning normally.

• Red—MIC has failed.

Link LED, one green per port:

• Off—No link.
• On steadily—Link is up.

Related • MX Series MIC Overview on page 17

Documentation

10-Gigabit Ethernet MICs with XFP

Figure 19: 2-Port 10-Gigabit Ethernet MIC with XFP

OK/FAIL

PORT [0/2]0

PORT [1/3]0
LINK

LINK

Copyright © 2018, Juniper Networks, Inc. 155

MX Series Interface Module Reference

Figure 20: 4-Port 10-Gigabit Ethernet MIC with XFP

OK/FAIL

PORT [0/2]0

PORT [0/2]1

PORT [1/3]0

PORT [1/3]1
LINK

LINK

LINK

LINK
Software release • 2-port: Junos 10.2 and later
• 4-port: Junos 10.1 and later

For information on which MPCs support these MICs, see “MIC/MPC Compatibility” on page 26.
For information on which MICs are supported on MX Series routers, see “MICs Supported by MX
Series Routers” on page 18.

Description • Two or four 10-Gigabit Ethernet ports

• Power requirement:
• 2-port: 0.6 A @ 48 V (29 W)
• 4-port: 0.56 A @ 48 V (27 W)

• Weight:
• 2-port: 1 lb (0.45 kg)
• 4-port: 1.1 lb (0.5 kg)

• Model number:
• 2-port: MIC-3D-2XGE-XFP
• 4-port: MIC-3D-4XGE-XFP

• Name in the CLI:

• 2-port: 3D 2X10GE XFP
• 4:-port 3D 4X10GE XFP

Hardware features • High-performance throughput on each port at speeds up to 10 Gbps

• LAN-PHY mode at 10.3125 Gbps
• WAN-PHY mode at 9.953 Gbps
• Maximum transmission units (MTUs) of up to 9192 bytes

Software features • Configurable LAN-PHY and WAN-PHY mode options

• Synchronous Ethernet support
• Optical diagnostics and related alarms
• Virtual Router Redundancy Protocol (VRRP) support
• IEEE 802.1Q virtual LANs (VLANs) support
• Remote monitoring (RMON) EtherStats
• Source MAC learning
• MAC accounting and policing—Dynamic local address learning of source MAC addresses
• Flexible Ethernet encapsulation
• Multiple tag protocol identifiers (TPID)

156 Copyright © 2018, Juniper Networks, Inc.

 Chapter 9: MX Series MIC Descriptions

Interfaces Syntax: xe-fpc/pic/port where:

• fpc: Slot in the router where the MPC is installed

• pic:
• 2-port: 0 when installed in MIC slot 0; 3 when installed in MIC slot 1
• 4-port: 0 or 1 when installed in MIC slot 0; 2 or 3 when installed in MIC slot 1

• port:
• 2-port: 0
• 4-port: 0 or 1

For example, xe-1/3/0 is the interface for port 0 on the MIC installed in MIC slot 1 on an MPC
installed in slot 1.

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

LEDs OK/FAIL LED, one bicolor:

• Green—MIC is functioning normally.

• Red—MIC has failed.

LINK LED, one green per port:

• Off—No link.
• On steadily—Link is up with or without activity.

The ports are labeled:

• 2-port: [0/2]0, [1/3]0

• 4-port: [0/2]0, [0/2]1, [1/3]0, and [1/3]1

Related • MX Series MIC Overview on page 17

Documentation

10-Gigabit Ethernet MIC with SFP+ (10 Ports)

Figure 21: 10-Gigabit Ethernet MIC with SFP+

MIC3-3D-10XGE-SFPP
0

g006683

Software release • Junos 12.3 and later

Copyright © 2018, Juniper Networks, Inc. 157

MX Series Interface Module Reference

Description • Ten 10-Gigabit Ethernet ports

• Power requirement: 0.62 A @ 48 V (29.8 W)
• Weight: 1.54 lb (0.70 kg)
• Model number: MIC3-3D-10XGE-SFPP
• Name in the CLI: 3D 10xGE SFPP

Hardware features • High-performance throughput on each port at speeds up to 10 Gbps

• Supports 10 SFP+ pluggable optic ports
• Voltage Sequencer for local voltage sequence control and monitoring
• LAN-PHY mode at 10.3125 Gbps
• WAN-PHY mode at 9.95328 Gbps
• Maximum transmission units (MTUs) of up to 9192 bytes

Software features • Configurable LAN-PHY and WAN-PHY mode options per port
• Synchronous Ethernet support
• Optical diagnostics and related alarms
• Virtual Router Redundancy Protocol (VRRP) support
• IEEE 802.1Q virtual LANs (VLANs) support
• Remote monitoring (RMON) EtherStats
• Source MAC learning
• MAC accounting and policing—Dynamic local address learning of source MAC addresses
• Flexible Ethernet encapsulation
• Multiple tag protocol identifiers (TPID)

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

NOTE: SFPP-10GE-ZR has a commercial temperature rating and is not NEBS compliant when
plugged into the 10-Gigabit Ethernet MIC with SFP+. If the ambient air temperature exceeds 40
degrees C, the software disables the transmitter, which takes the optical transceiver offline.

NOTE: SFPP-10G-DT-ZRC2 is not NEBS compliant when plugged into the MIC3-3D-10XGE-SFPP
MIC. If the ambient air temperature exceeds 40 degrees C, Junos OS disables the transmitter,
which takes the optical transceiver offline.

LEDs OK/FAIL LED, one bicolor:

• Green—MIC is functioning normally.

• Red—MIC has failed.

LINK LED, one per SFP+ port:

• Off—No link.
• Green—Link is up.
• Yellow—Link is disabled.

The ports are labeled:

• Port [0] to Port [9]

158 Copyright © 2018, Juniper Networks, Inc.

 Chapter 9: MX Series MIC Descriptions

NOTE: The MIC3-3D-10XGE-SFPP MIC has one logical PIC. When the MIC is
installed in slot 0 of an MPC the PIC number is 0, and when the MIC is installed
in slot 1 of an MPC the PIC number is 2. For example, when the MIC is installed
in slot 3 of the MX960 router, in slot 1 of the MPC, the interfaces are numbered
ge-3/2/0 through ge-3/2/9.

Related • MX Series MIC Overview on page 17

Documentation
• MICs Supported by MX Series Routers on page 18

• MIC/MPC Compatibility on page 26

10-Gigabit Ethernet MIC with SFP+ (24 Ports)

MIC6-10G

g007685
Software release • Junos 13.3R2 and later
For information about which MPCs support this MIC, see “MIC/MPC Compatibility” on page 26.
For information about which MICs are supported on MX Series routers, see “MICs Supported
by MX Series Routers” on page 18.

Description • Twenty-four 10-Gigabit Ethernet ports

• Power requirement: 7.1 A @ 10.4 V (74 W)
• Weight: 3.2 lb (1.45 kg)
• Model number: MIC6-10G
• Name in the CLI: 24x10GE SFPP

Hardware features • Supports 24 SFP+ pluggable optic ports

• High-performance throughput on each port at speeds up to 10 Gbps
• LAN-PHY mode at 10.3125 Gbps
• WAN-PHY mode at 9.95328 Gbps
• Supports LOS-squelch, enabling Synchronous Ethernet fast-clock-failover on a port down
event
• Maximum transmission units (MTUs) of up to 9192 bytes

Copyright © 2018, Juniper Networks, Inc. 159

MX Series Interface Module Reference

Software features • Configurable LAN-PHY and WAN-PHY mode options per port
• Compliant to ITU-T specifications
• Optical diagnostics and related alarms
• Virtual Router Redundancy Protocol (VRRP) support
• IEEE 802.1Q virtual LANs (VLANs) support
• IEEE 802.1ad support
• Remote monitoring (RMON) EtherStats
• Source MAC learning
• MAC accounting and policing—Dynamic local address learning of source MAC addresses
• In-service software upgrade (Unified ISSU)

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

LEDs OK/FAIL LED, one bicolor:

• Green—MIC is functioning normally.

• Yellow—MIC is coming online.
• Red—MIC has failed.

LINK LED, one bicolor per SFP+ port:

• Off—No link.
• Green—Link is up.
• Yellow—Link is disabled.

The ports are labeled:

• Port [0] to Port [23]

Related • MX Series MIC Overview on page 17

Documentation

10-Gigabit Ethernet OTN MIC with SFP+ (24 Ports)

MIC6-10G-OTN
g007684

Software release • Junos 13.3R3 and later

For information about which MPCs support this MIC, see “MIC/MPC Compatibility” on page 26.
For information about which MICs are supported on MX Series routers, see “MICs Supported
by MX Series Routers” on page 18.

160 Copyright © 2018, Juniper Networks, Inc.

 Chapter 9: MX Series MIC Descriptions

Description • Twenty-four 10-Gigabit optical transport network (OTN) ports for transport of 10-Gigabit
Ethernet (10GBASE-R) traffic
• Power requirement: 1.5 A @ 52 V (84 W)
• Weight: 3.4 lb (1.54 kg)
• Model number: MIC6-10G-OTN
• Name in the CLI: 24x10GE OTN

Hardware features • High-performance throughput on each port at speeds up to 10 Gbps

• LAN-OTU2e mode (G.Sup43, 7.1) at 11.09 Gbps
• WAN-OTU2 mode (G.Sup43, 6.1) at 10.70 Gbps
• Supports LOS-squelch, enabling Synchronous Ethernet fast-clock-failover on a port-down
event
• Provides IEEE 1588 time-stamping at physical interface for improved accuracy
• Maximum transmission units (MTUs) of up to 9192 bytes

Software features • OTN support for 10-Gigabit Ethernet interface

• Compliant with ITU-T specifications
• Transparent transport of 10-Gigabit Ethernet signals with optical channel transport unit 2
(OTU2/OTU2e) framing
• Optical diagnostics and related alarms
• Configurable LAN-PHY, WAN-PHY, or OTN mode options per port
• Virtual Router Redundancy Protocol (VRRP) support
• IEEE 802.1Q VLAN support
• IEEE 802.1ad support
• Remote monitoring (RMON) EtherStats
• Source MAC learning
• MAC accounting and policing—Dynamic local address learning of source MAC addresses
• In-service software upgrade (Unified ISSU)

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

LEDs OK/FAIL LED, one bicolor:

• Green—MIC is functioning normally.

• Yellow—MIC is coming online.
• Red—MIC has failed.

LINK LED, one bicolor per port:

• Off—No link.
• Green—Link is up.
• Yellow—Link is disabled.

The ports are labeled:

• Port [0] through Port [23]

Copyright © 2018, Juniper Networks, Inc. 161

MX Series Interface Module Reference

Related • MX Series MIC Overview on page 17

Documentation

40-Gigabit Ethernet MIC with QSFP+

Figure 22: 40-Gigabit Ethernet MIC with QSFP+

MIC3-3D-2X40GE-QSFPP

LINK

LINK
PORT0

PORT1

g006104
Software release • 12.2 and later

For information on which MPCs support this MIC, see “MIC/MPC Compatibility” on page 26. For
information on which MICs are supported on MX Series routers, see “MICs Supported by MX Series
Routers” on page 18.

Description • Two 40-Gigabit Ethernet ports

• Power requirement: 0.38 A @ 48 V (18 W)
• Weight: 1.19 lb (0.54 kg)
• Model number: MIC3-3D-2X40GE-QSFPP

Hardware features • High-performance throughput on each port at speeds up to 40 Gbps

• Up to 40-Gbps of full-duplex traffic
• Maximum transmission units (MTUs) of up to 9192 bytes

Software features • Synchronous Ethernet support

• Optical diagnostics and related alarms
• Virtual Router Redundancy Protocol (VRRP) support
• IEEE 802.1Q virtual LANs (VLANs) support
• Remote monitoring (RMON) EtherStats
• Source MAC learning
• MAC accounting and policing—Dynamic local address learning of source MAC addresses
• Flexible Ethernet encapsulation
• Multiple tag protocol identifiers (TPID)

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

162 Copyright © 2018, Juniper Networks, Inc.

 Chapter 9: MX Series MIC Descriptions

LEDs OK/FAIL LED, one bicolor:

• Green—MIC is functioning normally.

• Red—MIC has failed.

LINK LED, one green per port:

• Off—No link.
• On steadily—Link is up with or without activity.
• Yellow—Link is disabled.

The ports are labeled:

• PORT [0] - PORT [1]

Related • MX Series MIC Overview on page 17

Documentation

100-Gigabit Ethernet MIC with CFP

Figure 23: 1-Port 100 Gigabit Ethernet MIC with CFP

MIC3-3D-1X100GE-CFP

g006102
Software release • 12.1 and later

For information about which MPCs support this MIC, see “MIC/MPC Compatibility” on page 26.
For information about which MICs are supported on MX Series routers, see “MICs Supported by
MX Series Routers” on page 18.

Description • One 100-Gigabit Ethernet port

• Power requirement: 0.83 A @ 48 V (40 W)
• Weight: 1.94 lb (0.88 kg)
• Model number: MIC3-3D-1X100GE-CFP
• Name in the CLI: 1X100GE CFP

Hardware features • High-performance throughput on each port at speeds up to 100 Gbps

• Up to 100-Gbps of full-duplex traffic
• Maximum transmission units (MTUs) of up to 9192 bytes
• The port is labeled PORT0

Copyright © 2018, Juniper Networks, Inc. 163

MX Series Interface Module Reference

Software features • Synchronous Ethernet support

• Optical diagnostics and related alarms
• Virtual Router Redundancy Protocol (VRRP) support
• IEEE 802.1Q virtual LANs (VLANs) support
• Remote monitoring (RMON) EtherStats
• Source MAC learning
• MAC accounting and policing—Dynamic local address learning of source MAC addresses
• Flexible Ethernet encapsulation
• Multiple tag protocol identifiers (TPID)

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

NOTE: The CFP-100GBASE-ER4 transceiver is NEBS-compliant in the 100-Gigabit Ethernet MIC

with CFP, but only when the other MIC slot in the MPC3E is empty. If another MIC is present and
the ambient temperature exceeds 40 degrees C, the software converts CFP-100GBASE-ER4 to
low power mode, which takes the transceiver offline.

• Fiber-optic 100-Gigabit C form-factor Plugabble

NOTE: The CFP-100GBASE-ZR transceiver is NEBS compliant in the 100-Gigabit Ethernet MIC
with CFP, but only when the other MIC slot in the MPC3E is empty. If another MIC is present
and the ambient air temperature exceeds 40 degrees C, the software disables the transmitter,
which takes the optical transceiver offline. The other MIC slot must be filled with a blank panel.

LEDs OK/FAIL LED, one bicolor:

• Green—MIC is functioning normally.

• Red—MIC has failed.

LINK LED, one green per port:

• Off—No link.
• On steadily—Link is up.
• Yellow—Link is disabled.

Related • MX Series MIC Overview on page 17

Documentation

164 Copyright © 2018, Juniper Networks, Inc.

 Chapter 9: MX Series MIC Descriptions

100-Gigabit Ethernet MIC with CXP

Figure 24: 100-Gigabit Ethernet MIC with CXP

MIC3-3D-1X100GE-CXP

g006101
Software release • 12.2 and later

For information about which MPCs support this MIC, see “MIC/MPC Compatibility” on page 26.
For information about which MICs are supported on MX Series routers, see “MICs Supported by
MX Series Routers” on page 18.

Description • One 100-gigabit Ethernet port

• Power requirement: 0.42 A @ 48 V (20 W)
• Weight: 1.03 lb (0.47 kg)
• Model number: MIC3-3D-1X100GE-CXP
• Name in the CLI: 3D 1x100GE CXP

Hardware features • High-performance throughput on each port at speeds up to 100 Gbps

• Up to 100-Gbps of full-duplex traffic
• Maximum transmission units (MTUs) of up to 9192 bytes
• The port is labeled PORT0

Software features • Synchronous Ethernet support

• Optical diagnostics and related alarms
• Virtual Router Redundancy Protocol (VRRP) support
• IEEE 802.1Q virtual LANs (VLANs) support
• Remote monitoring (RMON) EtherStats
• Source MAC learning
• MAC accounting and policing—Dynamic local address learning of source MAC addresses
• Flexible Ethernet encapsulation
• Multiple tag protocol identifiers (TPID)

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

Copyright © 2018, Juniper Networks, Inc. 165

MX Series Interface Module Reference

LEDs OK/FAIL LED, one bicolor:

• Green—MIC is functioning normally.

• Red—MIC has failed.

LINK LED, one green per port:

• Off—No link.
• On steadily—Link is up with or without activity.
• Yellow—Link is disabled.

Related • MX Series MIC Overview on page 17

Documentation

100-Gigabit Ethernet MIC with CXP (4 Ports)

PORT 0

Software release • Junos 13.3R2 and later

For information about which MPCs support this MIC, see “MIC/MPC Compatibility” on page 26.
For information about which MICs are supported on MX Series routers, see “MICs Supported
by MX Series Routers” on page 18.

Description • Four 100-Gigabit Ethernet ports

• Power requirement: 5.5 A @ 10.4 V (57 W)
• Weight: 2.7 lb (1.22 kg)
• Model number: MIC6-100G-CXP
• Name in the CLI: 4X100GE CXP

Hardware features • Line-rate throughput of up to 100Gbps per port.

• Supports 100GBASE-SR10 over CXP pluggable optics
• Supports LOS-squelch, enabling Synchronous Ethernet fast-clock-failover on a port down
event
• Maximum transmission units (MTUs) of up to 9192 bytes

166 Copyright © 2018, Juniper Networks, Inc.

 Chapter 9: MX Series MIC Descriptions

Software features • Compliant to ITU-T specifications

• Optical diagnostics and related alarms
• Virtual Router Redundancy Protocol (VRRP) support
• IEEE 802.1Q virtual LANs (VLANs) support
• IEEE 802.1ad support
• Remote monitoring (RMON) EtherStats
• Source MAC learning
• MAC accounting and policing—Dynamic local address learning of source MAC addresses
• In-service software upgrade (Unified ISSU)

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

LEDs OK/FAIL LED, one tricolor:

• Green—MIC is functioning normally.

• Yellow—MIC is coming online.
• Red—MIC has failed.

LINK LED, one bicolor per port:

• Off—No link.
• Green—Link is up.
• Yellow—Link is disabled.

The ports are labeled:

• Port 0 to Port 3

Related • MX Series MIC Overview on page 17

Documentation

100-Gigabit Ethernet MIC with CFP2

Software release • Junos 13.3R3 and later

For information about which MPCs support this MIC, see “MIC/MPC Compatibility” on page 26.
For information about which MICs are supported on MX Series routers, see “MICs Supported
by MX Series Routers” on page 18.

Copyright © 2018, Juniper Networks, Inc. 167

MX Series Interface Module Reference

Description • Two 100-Gigabit Ethernet CFP2 ports

• Power requirement: 2 A @ 52 V (104 W)
• Weight: 2.4 lb (1.09 kg)
• Model number: MIC6-100G-CFP2
• Name in the CLI: 2X100GE CFP2 OTN

Hardware features • Line-rate throughput of up to 100 Gbps per port

• Supports CFP2 pluggable optics
• Supports LAN (103.125 Gbps) and OTN/OTU4 (111.81 Gbps) on a per-port basis
• Provides IEEE 1588 time-stamping at physical interface for improved accuracy
• Maximum transmission units (MTUs) of up to 9192 bytes

Software features • Optical transport network (OTN) support for 100-Gigabit Ethernet interfaces
• Compliant with ITU-T specifications
• Transparent transport of 100-Gigabit Ethernet signals with OTU4 framing
• Optical diagnostics and related alarms
• Configurable 100-Gigabit Ethernet or OTN options per port
• Virtual Router Redundancy Protocol (VRRP) support
• IEEE 802.1Q VLAN support
• IEEE 802.1ad support
• Remote monitoring (RMON) EtherStats
• Source MAC learning
• MAC accounting and policing—Dynamic local address learning of source MAC addresses
• In-service software upgrade (Unified ISSU)

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

NOTE:
• CFP2-100G-ER4-D is not NEBS compliant on the MX960 router in FPC slot 0 or FPC slot 11.
• CFP2-DCO-T-WDM-1 is not NEBS compliant on the MX960 router or the MX2020 router in
FPC slot 0 or FPC slot 11. Slots 0 and 11 can only work with an ambient temperature of up to
40° C.

NOTE: When inserting the CFP2 transceiver, ensure that the transceiver sits tightly in the port.
You will hear a distinct click sound when the latch locks into the corresponding port. The latch
must be fully engaged in the corresponding port for the CFP2 transceiver to function properly.
Failing to do so will result in loss of connection.

To verify that the CFP2 transceiver module is inserted properly, give a gentle pull by grasping the
sides of the module. The module should sit tightly.

168 Copyright © 2018, Juniper Networks, Inc.

 Chapter 9: MX Series MIC Descriptions

LEDs OK/FAIL LED, one tricolor:

• Green—MIC is functioning normally.

• Yellow—MIC is coming online.
• Red—MIC has failed.

LINK LED, one bicolor per port:

• Off—No link.
• Green—Link is up.
• Yellow—Link is disabled.

Port labels:

• Port 0 and Port 1

Related • MX Series MIC Overview on page 17

Documentation

100-Gigabit DWDM OTN MIC with CFP2-ACO

Software release • Junos OS Release 15.1F5 and 15.1F6, Junos OS Release 17.1R1 and later
For information about which MPCs support this MIC, see “MIC/MPC Compatibility” on page 26.
For information about which MICs are supported on MX Series routers, see “MICs Supported
by MX Series Routers” on page 18.

Description • One 100-Gigabit DWDM OTN port

• Power requirements (including transceiver) at different temperatures:
• 55° C: 1.90 A @ 48 V (91 W)
• 25° C: 1.73 A @ 48 V (83 W)

• Weight: 2.3 lb (1.04 kg)

• Model number: MIC3-100G-DWDM
• Name in the CLI: 1X100GE DWDM CFP2-ACO

Copyright © 2018, Juniper Networks, Inc. 169

MX Series Interface Module Reference

Hardware features • Dual-wide MIC that installs into two MIC slots
• Supports CFP2 analog coherent optics (CFP2-ACO)
• Transparent transport of a 100-Gigabit Ethernet signal with OTU4V framing
• ITU-standard OTN performance monitoring and alarm management
• Dual-polarization quadrature phase shift keying (DP-QPSK) modulation
• Supports three types of forward error correction (FEC):

• Soft-decision FEC (SD-FEC)

• High-gain FEC (HG-FEC)
• G.709 FEC (GFEC)

• 100 channels on C-band ITU grid with 50-GHz spacing

• Latency:

• SD-FEC: 14 µs (TX + RX)

• HG-FEC: 22 µs (TX + RX)
• GFEC: 6 µs (TX + RX)

• Interoperable with the CFP-100GBASE-ZR transceiver supported on the 100-Gigabit Ethernet

MIC with CFP (MIC3-3D-1X100GE-CFP) on MX Series routers and the 100-Gigabit Ethernet PIC
with CFP (P1-PTX-2-100GE-CFP) on PTX Series routers.
• Interoperable with the 100-Gigabit DWDM OTN PIC with CFP2 (PTX-5-100G-WDM) on PTX
Series routers when the 100-Gigabit DWDM OTN MIC is configured to use SD-FEC or GFEC.

NOTE: The 1-port 100-Gigabit DWDM OTN MIC is not directly interoperable with the 2-port
100-Gigabit DWDM OTN PIC (P1-PTX-2-100G-WDM), but they can both operate over the same
DWDM line system.

170 Copyright © 2018, Juniper Networks, Inc.

 Chapter 9: MX Series MIC Descriptions

Software features NOTE: For information about configuring the MIC, see Configuring OTN Interfaces on
MIC3-100G-DWDM MIC. For information about upgrading the firmware on the PIC, see Upgrading
Firmware on the 100-Gigabit DWDM OTN MIC (MIC3-100G-DWDM) .

• Compliant with ITU G.709 and G.798

• Provides a transport interface and state model (GR-1093)
• Performance monitoring features such as alarms, threshold-crossing alarms, OTU/ODU error
seconds and FEC and bit error rate (BER) statistics
• SNMP management of the MIC based on RFC 3591, Managed Objects for the Optical Interface
Type, including the following:

• Set functionality
• Black Link MIB
• IFOTN MIB
• Optics MIB
• FRU MIB

• Pre-FEC BER monitoring provides interrupt-driven, BER-based detection of link signal

degradation for MPLS fast reroute.
• User-configurable optics options:

• Transmit (TX) laser enable and disable

• TX output power
• Wavelength
• Receive (RX) LOS warning or alarm thresholds
• Threshold crossing alarms (TCAs)
User-configurable card options:

• FEC mode (SD-FEC, HG-FEC, or GFEC)

• TCAs

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

NOTE: When inserting the C form-factor pluggable 2 (CFP2) transceiver, ensure that the
transceiver sits tightly in the port. You hear a distinct click sound when the latch locks into the
corresponding port. The latch must be fully engaged in the corresponding port for the CFP2
transceiver to function properly. Failing to do so can result in loss of connection.

To verify that the CFP2 transceiver module is inserted properly, give a gentle pull by grasping the
sides of the module. The module should sit tightly.

Copyright © 2018, Juniper Networks, Inc. 171

MX Series Interface Module Reference

LEDs OK/FAIL LED, one bicolor:

• Off—MIC is powered off.

• Green—MIC is initialized and online, functioning normally.
• Amber—MIC is coming online, or is in fault state.

LINK LED, one bicolor per port:

• Off—Port is offline.
• Solid green—Link is up.
• Red—Port failure is detected.

NOTE: The port is labeled Port 0.

Alarms, Errors, and NOTE: For OTN alarms, see Table 24 on page 176.
Events
Chassis and MIC:

• MIC (FRU) inserted or removed

• MIC (FRU) Administrative State: In Service, Out Of Service
• MIC (FRU) Operational State: Unequipped, Init, Normal, Mismatch, Fault, Upgrade
• Mismatch equipment
• Temperature alarm

Port (interface):

• Interface Administrative State: In Service, Out Of Service, Service MA, Out of Service MA
• Interface Operational State: Init, Normal, Fault, Degraded

Optical channel transport unit (OTU) TCAs:

• OTU-TCA-BBE—15-minute background block error TCA

• OTU-TCA-ES—15-minute far-end errored seconds TCA
• OTU-TCA-SES—15-minute severely errored seconds TCA
• OTU-TCA-UAS—15-minute unavailable seconds TCA

Optical channel data unit (ODU) TCAs:

• ODU-TCA-BBE—15-minute background block error TCA

• ODU-TCA-ES—15-minute far-end errored seconds TCA
• ODU-TCA-SES—15-minute severely errored seconds TCA
• ODU-TCA-UAS—15-minute unavailable seconds TCA

TIP: You can view OTU and ODU TCAs by using the show interfaces transport pm otn
operational-mode CLI command.

172 Copyright © 2018, Juniper Networks, Inc.

 Chapter 9: MX Series MIC Descriptions

Copyright © 2018, Juniper Networks, Inc. 173

MX Series Interface Module Reference

NOTE: If you insert an invalid CFP module, the CLI displays unsupported module and a syslog
message is generated.

Optics-related status:

• Module temperature
• Module voltage
• Module temperature alarm:
• High alarm
• Low alarm
• High warning
• Low warning

• Module voltage alarm:

• High alarm
• Low alarm
• High warning
• Low warning

• Module not ready alarm

• Module low power alarm
• Module initialization incomplete alarm
• Module fault alarm
• TX laser disabled alarm
• RX loss of signal alarm
• Modem lock state
• TX output power:
• Current TX output power
• Minimum over PM interval
• Maximum over PM interval
• Average over PM interval

• TX power alarm:
• High alarm
• Low alarm
• High warning
• Low warning

• RX input power (signal)

• RX input power (total):
• Current RX input power (total)
• Minimum over PM interval
• Maximum over PM interval
• Average over PM interval

• RX power alarm:
• High alarm
• Low alarm
• High warning
• Low warning

• RX loss of signal alarm

• Wavelength unlocked alarm

174 Copyright © 2018, Juniper Networks, Inc.

 Chapter 9: MX Series MIC Descriptions

TIP: You can view optics-related status by using the show interfaces transport pm optics and show
interfaces diagnostics optics operational-mode CLI commands.

Network lane receive-related status:

• Chromatic dispersion:
• Current chromatic dispersion
• Minimum over PM interval
• Maximum over PM interval
• Average over PM interval

• Differential group delay:

• Current differential group delay
• Minimum over PM interval
• Maximum over PM interval
• Average over PM interval
2
• Q -factor:
2
• Current Q -factor
• Minimum over PM interval
• Maximum over PM interval
• Average over PM interval

• Carrier frequency offset

• Current carrier frequency offset
• Minimum over PM interval
• Maximum over PM interval
• Average over PM interval

• Signal-to-noise ratio (SNR)

• Current SNR
• Minimum over PM interval
• Maximum over PM interval
• Average over PM interval

TIP: You can view network lane receive-related status by using the show interfaces transport pm
optics operational-mode CLI command.

FEC statistics:

• Corrected Errors—the number of bits received that were in error, but corrected.
• Uncorrected Words—the number of FEC codewords received that were uncorrectable.
• Corrected Error Ratio—the number of corrected bits divided by the number of bits received

TIP: You can view FEC statistics by using the show interfaces interface-name extensive
operational-mode CLI command.

Table 24 on page 176 describes the OTN alarms and defects that can occur on the MIC
and the link status when the alarm or defect occurs.

TIP: You can view OTN alarms and defects by using the show interfaces
interface-name extensive operational-mode CLI command.

Copyright © 2018, Juniper Networks, Inc. 175

MX Series Interface Module Reference

Table 24: OTN Alarms and Defects

Category Alarm Description Link Status

OTN LOS Loss of signal Link down

LOF Loss of frame Link down

LOM Loss of multiframe Link down

OTN FEC FEC Degrade Forward error correction degraded Link down if signal degrade or
(OTU-FEC-DEG) backward FRR thresholds are met

FEC Excessive There are uncorrected words and there are Possible link down
(OTU-FEC-EXE) errors in the frame header

OTN OTU OTU-AIS Alarm indication signal or all ones signal Link down

OTU-BDI Backward defect identification Link down

OTU-IAE Incoming alignment error Warning

OTU-TTIM Destination access point identifier (DAPI), Can cause the link to be down if
source access point identifier (SAPI), or both otu-ttim-act-enable is configured at
mismatch from expected to received the [edit interfaces interface-name
otn-options]hierarchy level

OTU-BIAE Backward incoming alignment error Warning

OTU-TSF OTU trail signal fail Warning

OTU-SSF OTU server signal fail Warning

176 Copyright © 2018, Juniper Networks, Inc.

 Chapter 9: MX Series MIC Descriptions

Table 24: OTN Alarms and Defects (continued)

Category Alarm Description Link Status

OTN ODU ODU-AIS Alarm indication signal or all ones signal Link down

ODU-OCI Open connection error Link down

ODU-LCK ODU lock triggers for path monitoring and TCM Link down
levels 1 through 6

ODU-BDI Backward defect indication Link down

ODU-TTIM DAPI or SAPI mismatch from expected to Can cause the link to be down if
received odu-ttim-act-enable is configured at
the [edit interfaces interface-name
otn-options] hierarchy level

ODU-IAE Incoming alignment error Warning

ODU-LTC Loss of tandem connection Warning

ODU-CSF Client signal failure Warning

ODU-TSF Trail signal fail Warning

ODU-SSF Server signal fail Warning

ODU-PTIM Payload type mismatch Link down

Related • 100-Gigabit DWDM OTN CFP2-ACO Transceiver Wavelengths

Documentation
• MX Series MIC Overview on page 17

• Configuring OTN Interfaces on MIC3-100G-DWDM MIC

• Upgrading Firmware on the 100-Gigabit DWDM OTN MIC (MIC3-100G-DWDM)

• show interfaces extensive

• show interfaces transport pm

• show interfaces diagnostics optics (Gigabit Ethernet, 10-Gigabit Ethernet, 40-Gigabit

Ethernet, 100-Gigabit Ethernet, and Virtual Chassis Port)

Copyright © 2018, Juniper Networks, Inc. 177

MX Series Interface Module Reference

Channelized SONET/SDH OC3/STM1 (Multi-Rate) MICs with SFP

Figure 25: 4-Port Channelized SONET/SDH OC3/STM1 (Multi-Rate) MIC with SFP

MIC-3D-4CHOC3-2CHOC12

MIC-3D-4CHOC3-
2CHOC12

g006094
0 1 2 3

178 Copyright © 2018, Juniper Networks, Inc.

 Chapter 9: MX Series MIC Descriptions

Figure 26: 8-Port Channelized SONET/SDH OC3/STM1 (Multi-Rate) MIC with SFP
MIC-3D-8CHOC3-4CHOC12

MIC-3D-8CHOC3-
4CHOC12

g006093
0 1 2 3 4 5 6 7

Software release • Junos OS Release 11.4 and later

For information on which MPCs support these MICs, see “MIC/MPC Compatibility” on page 26.
For information on which MICs are supported on MX Series routers, see “MICs Supported by MX
Series Routers” on page 18.

Description • 4-port: Rate-selectable using one of the following rates:

• 4-port OC3/STM1
• 2-port OC12/STM4

• 8-port: Rate-selectable using one of the following rates:

• 8-port OC3/STM1
• 4-port OC12/STM4

• Channelization: OC3, DS3, DS1, DS0, E3, E1. For information on channelization numbers, see
Channelized Interfaces Feature Guide for Routing Devices.
• Power requirement:
• 4-port: 4.56 A @ 9 V (41 W)
• 8-port: 5.78 A @ 9 V (52 W)

• Weight:
• 4-port: 4.4 lb (2 kg)
• 8-port: 4.4 lb (2 kg)

• Model number:
• 4-port: MIC-3D-4CHOC3-2CHOC12
• 4-port: MIC-4COC3-2COC12-G
• 8-port: MIC-3D-8CHOC3-4CHOC12
• 4-port: MIC-4COC3-2COC12-G
• 8-port: MIC-3D-8CHOC3-4CHOC12
• 8-port: MIC-8COC3-4COC12-G

NOTE: MIC-4COC3-2COC12-G and MIC-8COC3-4COC12-G are RoHS 6/6 compliant.

Copyright © 2018, Juniper Networks, Inc. 179

MX Series Interface Module Reference

Hardware features • The ports are labeled:

• 4-port: 0-3
• 8-port: 0-7

Software features • Maximum transmission units (MTUs) of up to 9192 bytes

• Per-port SONET/SDH framing
• Local and remote loopback on each port
• Optical diagnostics and monitoring
• Clocking options: internal or external/loop mode
• Encapsulations:
• MPLS fast reroute
• MPLS CCC (circuit cross-connection)
• MPLS TCC (translational cross-connection)
• Cisco High-Level Data Link Control (cHDLC)
• Cisco HDLC CCC
• Cisco HDLC TCC
• Point-to-Point Protocol (PPP)
• PPP for CCC
• PPP for TCC
• Flexible Frame Relay
• Frame Relay
• Frame Relay for CCC
• Frame Relay for TCC
• PPP over Frame Relay
• Multilink-based protocols (Junos OS Release 12.1 and later):
• Multilink Point-to-Point Protocol (MLPPP)

• Multiclass MLPPP
• Multilink Frame Relay (MLFR) end-to-end (FRF.15)
• Multilink Frame Relay (MLFR) UNI NNI (FRF.16, also referred to as MFR)
• Compressed Real-Time Transport Protocol (CRTP)

NOTE: When you configure multilink services on a MIC in an MX Series router, ensure that
a Multiservices DPC is present in the same router.

NOTE: Ethernet over Frame Relay is not supported.

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

180 Copyright © 2018, Juniper Networks, Inc.

 Chapter 9: MX Series MIC Descriptions

LEDs OK/FAIL LED, one bicolor:

• Green—MIC is functioning normally

• Red—MIC has failed

LINK LED, one green per port:

• Off—Not enabled
• Green—Online with no alarms or failures
• Yellow—Online with alarms for remote failures
• Red—Active with a local alarm; router has detected a failure

Alarms, errors, and SONET alarms:

events
• Loss of light (LOL)
• Loss of signal (LOS)
• Loss of frame (LOF)
• Phase lock loop (PLL)
• Severely errored frame (SEF)
• Alarm indicator signal–line (AIS-L)
• Alarm indicator signal–path (AIS-P)
• Remote defect indicator–line (RDI-L)
• Remote defect indicator–path (RDI-P)
• Loss of pointer–path (LOP-P)
• Bit error rate–signal degrade (BERR-SD)
• Bit error rate–signal fail (BERR-SF)
• Payload label mismatch–Path (PLM-P)
• Unequipped–path (UNEQ-P)
• Remote error indicator–path (REI-P)
• Alarm indicator signal–virtual container (V-AIS)
• Loss of pointer–virtual container (V-LOP)
• Remote defect indicator–virtual container (V-RDI)
• Unequipped–virtual container (V-UNEQ)
• Mismatch–virtual container (V-MIS)

SDH alarms:

• Loss of light (LOL)

• Phase lock loop (PLL)
• Loss of frame (LOF)
• Loss of signal (LOS)
• Severely errored frame (SEF)
• Multiplex-section alarm indicator signal (MS-AIS)
• Higher order path–alarm indication signal (HP-AIS)
• Loss of pointer (LOP)
• Bit error rate–signal degrade (BER-SD)
• Bit error rate–signal fail (BER-SF)
• Multiplex section–far end receive failure (MS-FERF)
• Higher order path—far-end receive failure (HP-FERF)
• Higher order path—payload label mismatch (HP-PLM)
• Remote error indicator (REI)

Copyright © 2018, Juniper Networks, Inc. 181

MX Series Interface Module Reference

• Unequipped (UNEQ)
• Tributary unit–alarm indicator signal (TU-AIS)
• Tributary unit–loss of pointer (TU-LOP)
• Tributary unit–remote defect indicator (TU-RDI)
• Tributary unit–unequipped (TU-UNEQ)
• Tributary unit–mismatch (TU-MIS)

DS3 alarms:

• Alarm indication signal (AIS)

• Loss of frame (LOF)
• Loss of signal seconds (LOS)
• Phase lock loop (PLL)

DS3 error detection:

• C-bit code violations (CCV)

• C-bit errored seconds (CES)
• C-bit severely errored seconds (CSES)
• CRC errors
• Excessive zeros (EXZ)
• Far-end block error (FEBE)
• Far-end receive failure (FERF)
• Line errored seconds (LES)
• Parity bit (P-bit) code violations (PCV)
• Parity bit (P-bit) errored seconds (PES)
• Parity bit (P-bit) severely errored framing seconds (PSES)
• Severely errored framing seconds (SEFS)
• Unavailable seconds (UAS)

Related • MX Series MIC Overview on page 17

Documentation

182 Copyright © 2018, Juniper Networks, Inc.

 Chapter 9: MX Series MIC Descriptions

Channelized OC3/STM1 (Multi-Rate) Circuit Emulation MIC with SFP

Figure 27: Channelized OC3/STM1 (Multi-Rate) Circuit Emulation MIC with SFP

MIC-3D-4COC3-1COC12-CE

g006583
0 1 2 3

Software release • Junos OS Release 12.2 and later

For information on which MPCs support this MIC, see “MIC/MPC Compatibility” on page 26. For
information on which MICs are supported on MX Series routers, see “MICs Supported by MX Series
Routers” on page 18.

Description • Four OC3/STM1 ports

• Rate-selectable using one of the following rates:
• 4-port OC3/STM1
• 1-port OC12/STM4

• One channelized OC12/STM4 port (down to DS0)

• SONET or SDH is configurable on a MIC level
• OC3 channelization:
• 4 OC3 channel
• 336 DS1 channels
• 2016 DS0 channels (combination of nxDS0)

• SDH channelization:
• 4 STM1 channel
• 252 E1 channels
• 2016 DS0 channels (combination of nxDS0)

• Power requirement: 2.83 A @ 12 V (33.96 W)

• Weight: 1.63 lb (0.74 kg)
• Model number: MIC-3D-4COC3-1COC12-CE

Hardware features • Ports are numbered 0 through 3

Copyright © 2018, Juniper Networks, Inc. 183

MX Series Interface Module Reference

Software features • Per-MIC SONET/SDH framing

• Internal and loop clocking
• Encapsulations:
• Pseudo Wire Emulation Edge-to-Edge (PWE3) Architecture (RFC 3985)
• Requirements for Pseudo-Wire Emulation Edge-to-Edge (PWE3) (RFC 3916)
• Structure-Agnostic Time Division Multiplexing (TDM) over Packet (SAToP) (RFC 4553)
• Structure-Aware Time Division Multiplexed (TDM) Circuit Emulation Service over Packet
Switched Network (CESoPSN) (RFC 5086)
• Pseudowire Emulation Edge-to-Edge (PWE3) Control Word for Use over an MPLS PSN (RFC
4385)
• L2 Network Interconnections (protocol stitching):
• TDM LDP PWs to BGP L2VPN—see Using the Layer 2 Interworking Interface to Interconnect
a Layer 2 Circuit to a Layer 2 VPN for more information. Note that stitching CESoPSN PW
to BGP L2VPN is not supported.

• Unified in-service software upgrade (unified ISSU)

Interfaces Syntax: mediatype-fpc/pic/port where:

• mediatype: coc3, coc12, cstm1, cstm4, or ds

• fpc: Slot in the router where the MPC is installed
• pic: 0 when installed in MIC slot 0 or 2 when installed in MIC slot 1
• port: 0 through 3

For example, cstm4-1/2/0 is the channelized STM4 interface for port 0 on the MIC installed in
MIC slot 1 on an MPC installed in slot 1.

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

NOTE: To extend the life of the laser, when a MIC is not being actively used with any valid links,
take the MIC offline until you are ready to establish a link to another device. For information about
taking a MIC offline, see the request chassis pic offline command in the Junos OS System Basics
and Services Command Reference.

LEDs OK/FAIL LED, one bicolor:

• Green—MIC is functioning normally

• Red—MIC has failed

LINK LED, one tricolor per port:

• Off—Not enabled
• Green—Online with no alarms or failures
• Yellow—Online with alarms for remote failures
• Red—Active with a local alarm; router has detected a failure

184 Copyright © 2018, Juniper Networks, Inc.

 Chapter 9: MX Series MIC Descriptions

Alarms, errors, and Structure-agnostic alarms for T1 and E1 interface:

events
• Alarm indication signal (AIS)
• Loss of signal (LOS)
• Line code violation (LCV)
• Errored seconds (ES)
• Line-errored seconds (LES)
• Severely errored seconds (SES)
• Unavailable errored seconds (UAS)

Structure aware alarms for T1 and E1 interface:

• Severely errored frame (SEF)

• Block error event (BEE)
• Loss of frame (LOF)
• Yellow alarm (remote alarm indication RAI)
• Path code violation (PCV)
• Severely errored frame seconds (SEFS)
• Bursty errored seconds (BES)

Related • MX Series MIC Overview on page 17

Documentation
• Using the Layer 2 Interworking Interface to Interconnect a Layer 2 Circuit to a Layer 2 VPN

Channelized OC3/STM1 (Multi-Rate) Circuit Emulation MIC with SFP (H)

Figure 28: Channelized OC3/STM1 (Multi-Rate) Circuit Emulation MIC with SFP (H)

0 1 2 3

Software release • Junos OS Release 13.2R2 and later

For information on which MPCs support this MIC, see “MIC/MPC Compatibility” on page 26. For
information on which MICs are supported on MX Series routers, see “MICs Supported by MX
Series Routers” on page 18.

Copyright © 2018, Juniper Networks, Inc. 185

MX Series Interface Module Reference

Description • Four OC3/STM1 ports

• Rate-selectable using one of the following rates:
• 4-port OC3/STM1
• 1-port OC12/STM4

• One channelized OC12/STM4 port (down to DS0)

• SONET or SDH is configurable on a MIC level
• SONET channelization:
• 4 OC3 channel
• 336 DS1 channels
• 2016 DS0 channels (combination of nxDS0)

• SDH channelization:
• 4 STM1 channel
• 252 E1 channels
• 2016 DS0 channels (combination of nxDS0)

• Power requirement: 2.83 A @ 12 V (33.96 W)

• Weight: 1.63 lb (0.74 kg)
• Model number: MIC-4COC3-1COC12-CE-H

Hardware features • Ports are numbered 0 through 3

• Environmentally hardened for –40° F (–40° C) to 149° F (65° C) operating temperatures

Software features • Per-MIC SONET/SDH framing

• Internal and loop clocking
• Encapsulations:
• Pseudo Wire Emulation Edge-to-Edge (PWE3) Architecture (RFC 3985)
• Requirements for Pseudo-Wire Emulation Edge-to-Edge (PWE3) (RFC 3916)
• Structure-Agnostic Time Division Multiplexing (TDM) over Packet (SAToP) (RFC 4553)
• Structure-Aware Time Division Multiplexed (TDM) Circuit Emulation Service over Packet
Switched Network (CESoPSN) (RFC 5086)
• Pseudowire Emulation Edge-to-Edge (PWE3) Control Word for Use over an MPLS PSN
(RFC 4385)

Interfaces Syntax: mediatype-fpc/pic/port where:

• mediatype: coc3, coc12, cstm1, cstm4, or ds

• fpc: Slot in the router where the MPC is installed
• pic: 0 when installed in MIC slot 0 or 2 when installed in MIC slot 1
• port: 0 through 3

For example, cstm4-1/2/0 is the channelized STM4 interface for port 0 on the MIC installed in
MIC slot 1 on an MPC installed in slot 1.

186 Copyright © 2018, Juniper Networks, Inc.

 Chapter 9: MX Series MIC Descriptions

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

NOTE: To extend the life of the laser, when a MIC is not being actively used with any valid links,
take the MIC offline until you are ready to establish a link to another device. For information about
taking a MIC offline, see the request chassis pic offline command in the Junos OS System Basics
and Services Command Reference.

LEDs OK/FAIL LED, one bicolor:

• Green—MIC is functioning normally

• Red—MIC has failed

LINK LED, one tricolor per port:

• Off—Not enabled
• Green—Online with no alarms or failures
• Yellow—Online with alarms for remote failures
• Red—Active with a local alarm; router has detected a failure

Alarms, errors, and Structure-agnostic alarms for T1 and E1 interface:

events
• Alarm indication signal (AIS)
• Loss of signal (LOS)
• Line code violation (LCV)
• Errored seconds (ES)
• Line-errored seconds (LES)
• Severely errored seconds (SES)
• Unavailable errored seconds (UAS)

Structure aware alarms for T1 and E1 interface:

• Severely errored frame (SEF)

• Block error event (BEE)
• Loss of frame (LOF)
• Yellow alarm (remote alarm indication RAI)
• Path code violation (PCV)
• Severely errored frame seconds (SEFS)
• Bursty errored seconds (BES)

Related • MX Series MIC Overview on page 17

Documentation

Copyright © 2018, Juniper Networks, Inc. 187

MX Series Interface Module Reference

Channelized E1/T1 Circuit Emulation MIC

Figure 29: Channelized E1/T1 Circuit Emulation MIC

MIC-3D-16CHE1-T1-CE

15
8

g006681
0

7
Software release • Junos OS Release 12.3 and later

For information on which MPCs support this MIC, see “MIC/MPC Compatibility” on page 26. For
information on which MICs are supported on MX Series routers, see “MICs Supported by MX Series
Routers” on page 18.

Description • Sixteen E1 or T1 ports

• Per-MIC E1/T1 framing
• DS1 channelization per port:
• 1 DS1 channel
• 24 DS0 channels

• E1 channelization per port:

• 1 E1 channel
• 32 DS0 channels

• Internal and loop clocking

• Power requirement: 2.21 A @ 12 V (26.55 W)
• Weight: 1.57 lb (0.71 kg)
• Model number: MIC-3D-16CHE1-T1-CE

Hardware features • Ports are numbered:

• Top row: 8 and 15 from left to right
• Bottom row: 0 and 7 from left to right

188 Copyright © 2018, Juniper Networks, Inc.

 Chapter 9: MX Series MIC Descriptions

Software features • Full bit error rate test (BERT)

• DS1 and E1 interfaces are selectable on a per-port granularity
• Per-port framing is not supported
• You can configure the following framing modes using the CLI:
• T1—SF, ESF, D4/superframe, ESF (extended superframe)
• E1—G704, G704–no-crc4, unframed

• Local, remote, and per-port loopback diagnostics

• Encapsulations:
• Pseudowire Emulation Edge to Edge (PWE3) Architecture (RFC 3985)
• Requirements for Pseudowire Emulation Edge to Edge (PWE3) (RFC 3916)
• Structure-Agnostic Time Division Multiplexing (TDM) over Packet (SAToP) (RFC 4553)
• Structure-Aware Time Division Multiplexed (TDM) Circuit Emulation Service over
Packet-Switched Network (CESoPSN) (RFC 5086)
• Pseudowire Emulation Edge to Edge (PWE3) Control Word for Use over an MPLS PSN (RFC
4385)

• In-service software upgrade (Unified ISSU)

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

• RJ-48 connector

LEDs OK/FAIL LED, one bicolor:

• Green—MIC is functioning normally.

• Red—MIC has failed.

One tricolor per port:

• Off—Not enabled.
• Green—Online with no alarms or failures.
• Yellow—Online with alarms for remote failures.
• Red—Active with a local alarm; router has detected a failure.

Copyright © 2018, Juniper Networks, Inc. 189

MX Series Interface Module Reference

Alarms, errors, and • Structure-agnostic alarms for T1 and E1 interface:

events • Alarm indication signal (AIS)
• Loss of signal (LOS)

• Structure-aware alarms for T1 and E1 interface:

• Loss of signal (LOS)
• Alarm indication signal (AIS)
• Loss of frame (LOF)
• Remote alarm indication signal (RAIS)

• Structure-agnostic error detection for T1 and E1 interface:

• Errored seconds (ES)
• Line code violation (LCV)
• Line errored seconds (LES)
• Severely errored seconds (SES)
• Unavailable seconds (UAS)
• Loss of signal seconds (LOSS)

• Structure-aware error detection for T1 and E1 interface:

• Severely errored frame (SEF)
• Block error event (BEE)
• Line code violation (LCV)
• Path code violation (PCV)
• Line errored seconds (LES)
• Errored seconds (ES)
• Severely errored seconds (SES)
• Severely errored frame seconds (SEFS)
• Bursty errored seconds (BES)
• Unavailable seconds (UAS)
• Loss of signal seconds (LOSS)
• Loss of framing seconds (LOFS)
• Far-end block error (FEBE) (E1 only)
• CRC errors (E1 only)

Related • MX Series MIC Overview on page 17

Documentation

190 Copyright © 2018, Juniper Networks, Inc.

 Chapter 9: MX Series MIC Descriptions

Channelized E1/T1 Circuit Emulation MIC (H)

Figure 30: Channelized E1/T1 Circuit Emulation MIC (H)

15
8
0

7
Software release • Junos OS Release 13.2R2 and later

For information on which MPCs support this MIC, see “MIC/MPC Compatibility” on page 26. For
information on which MICs are supported on MX Series routers, see “MICs Supported by MX Series
Routers” on page 18.

Description • Sixteen E1 or T1 ports

• Per-MIC E1/T1 framing
• DS1 channelization per port:
• 1 DS1 channel
• 24 DS0 channels

• E1 channelization per port:

• 1 E1 channel
• 32 DS0 channels

• Internal and loop clocking

• Power requirement: 2.21 A @ 12 V (26.55 W)
• Weight: 1.57 lb (0.71 kg)
• Model number: MIC-3D-16CHE1-T1-CE-H

Hardware features • Ports are numbered:

• Top row: 8 and 15 from left to right
• Bottom row: 0 and 7 from left to right

• Environmentally hardened for –40° F (–40° C) to 149° F (65° C) operating temperatures

Copyright © 2018, Juniper Networks, Inc. 191

MX Series Interface Module Reference

Software features • Full bit error rate test (BERT)

• DS1 and E1 interfaces are selectable on a per-port granularity
• Per-port framing is not supported
• You can configure the following framing modes using the CLI:
• T1—SF, ESF, D4/superframe, ESF (extended superframe)
• E1—G704, G704–no-crc4, unframed

• Local, remote, and per-port loopback diagnostics

• Encapsulations:
• Pseudowire Emulation Edge to Edge (PWE3) Architecture (RFC 3985)
• Requirements for Pseudowire Emulation Edge to Edge (PWE3) (RFC 3916)
• Structure-Agnostic Time Division Multiplexing (TDM) over Packet (SAToP) (RFC 4553)
• Structure-Aware Time Division Multiplexed (TDM) Circuit Emulation Service over
Packet-Switched Network (CESoPSN) (RFC 5086)
• Pseudowire Emulation Edge to Edge (PWE3) Control Word for Use over an MPLS PSN (RFC
4385)

Interfaces Syntax: media-type-fpc/pic/port where:

• media-type: ct1, ds, t1, or e1

• fpc: Slot in the router where the MPC is installed
• pic: 0 when installed in MIC slot 0 or 2 when installed in MIC slot 1
• port: 0 through 15

For example, t1-2/2/0 is the T1 interface for port 0 on the MIC installed in MIC slot 1 on an MPC
installed in slot 2.

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

• RJ-48 connector

LEDs OK/FAIL LED, one bicolor:

• Green—MIC is functioning normally.

• Red—MIC has failed.

One tricolor per port:

• Off—Not enabled.
• Green—Online with no alarms or failures.
• Yellow—Online with alarms for remote failures.
• Red—Active with a local alarm; router has detected a failure.

192 Copyright © 2018, Juniper Networks, Inc.

 Chapter 9: MX Series MIC Descriptions

Alarms, errors, and • Structure-agnostic alarms for T1 and E1 interface:

events • Alarm indication signal (AIS)
• Loss of signal (LOS)

• Structure-aware alarms for T1 and E1 interface:

• Loss of signal (LOS)
• Alarm indication signal (AIS)
• Loss of frame (LOF)
• Remote alarm indication signal (RAIS)

• Structure-agnostic error detection for T1 and E1 interface:

• Errored seconds (ES)
• Line code violation (LCV)
• Line errored seconds (LES)
• Severely errored seconds (SES)
• Unavailable seconds (UAS)
• Loss of signal seconds (LOSS)

• Structure-aware error detection for T1 and E1 interface:

• Severely errored frame (SEF)
• Block error event (BEE)
• Line code violation (LCV)
• Path code violation (PCV)
• Line errored seconds (LES)
• Errored seconds (ES)
• Severely errored seconds (SES)
• Severely errored frame seconds (SEFS)
• Bursty errored seconds (BES)
• Unavailable seconds (UAS)
• Loss of signal seconds (LOSS)
• Loss of framing seconds (LOFS)
• Far-end block error (FEBE) (E1 only)
• CRC errors (E1 only)

Related • MX Series MIC Overview on page 17

Documentation

Copyright © 2018, Juniper Networks, Inc. 193

MX Series Interface Module Reference

Tri-Rate MIC

Figure 31: 40-Port Tri-Rate MIC

g004922

Software release • Junos 10.2 and later

For information on which MPCs support this MIC, see “MIC/MPC Compatibility” on page 26. For
information on which MICs are supported on MX Series routers, see “MICs Supported by MX Series
Routers” on page 18.

Description • 40 autonegotiating 10BASE-T, 100BASE-TX, or 1000BASE-T Megabit Ethernet ports

• Power requirement: 0.85 A @ 48 V (41 W)
• Weight: 1.9 lb (0.9 kg)
• Model number: MIC-3D-40GE-TX
• Name in the CLI: 3D 40GE TX

Hardware features • Dual-wide MIC that installs into 2 slots.

For information on how to install dual-wide MICs, see the Installing Dual-Wide MIC topic in the
respective MX Series Router Hardware Guide.
• High-performance throughput on each port at speeds of 10 Mbps, 100 Mbps, or 1000 Mbps
• Up to 40-Gbps of full-duplex traffic
• Autonegotiation between Gigabit Ethernet circuit partners
• Maximum transmission units (MTUs) of up to 9192 bytes

194 Copyright © 2018, Juniper Networks, Inc.

 Chapter 9: MX Series MIC Descriptions

Software features • Virtual Router Redundancy Protocol (VRRP) support

• IEEE 802.1Q virtual LANs (VLANs) support
• Remote monitoring (RMON) EtherStats
• Source MAC learning
• MAC accounting and policing—Dynamic local address learning of source MAC addresses
• Flexible Ethernet encapsulation
• Multiple tag protocol identifiers (TPID)

Interfaces Syntax: ge-fpc/pic/port where:

• fpc: Slot in the router where the MPC is installed.

• pic: The ports on the MPC are divided into four logical PICs numbered 0, 1, 2, and 3.
• port: 0 through 9

For example, ge-2/3/0 is the interface for port 0 in logical PIC 3 on the MPC installed in slot 2.

Figure 15 on page 152, Figure 33 on page 197, and Figure 34 on page 197 illustrate the port numbering
for the Tri-Rate MIC installed in the MX960, MX480, and MX240, respectively.

Cables and connectors • Connector: Four-pair, Category 5 shielded twisted-pair connectivity through an RJ-45 connector
• Pinout: MDI, MDI crossover
• Maximum distance: 328 ft (100 m)

CAUTION: Do not use RJ-45 cables with strain-relief boots exceeding 1.5 mm from the bottom
of the connector. Cable boots that exceed this measurement can damage the port.

LEDs OK/fail LED, one bicolor:

• Green—MIC is functioning normally.

• Red—MIC has failed.

Link LED, one green per port:

• Off—No link.
• On steadily—Link is up.

Figure 15 on page 152, Figure 33 on page 197, and Figure 34 on page 197 illustrate the port
numbering for the Tri-Rate MIC installed in the MX960, MX480, and MX240, respectively.

Copyright © 2018, Juniper Networks, Inc. 195

MX Series Interface Module Reference

Figure 32: Port Numbering for the Tri-Rate MIC (MX960)

MIC-3D-40GE-TX

ge-3/0/0 ge-3/0/1
ge-3/0/2 ge-3/0/3
ge-3/0/4 ge-3/0/5
ge-3/0/6 ge-3/0/7
ge-3/0/8 ge-3/0/9

ge-3/1/0 ge-3/1/1
ge-3/1/2 ge-3/1/3
ge-3/1/4 ge-3/1/5 0 1 2 3

0 1 2 3 4 5 0 1 2 6 7 8 9 10 11

ge-3/1/6 ge-3/1/7
ge-3/1/8 ge-3/1/9

ge-3/2/0 ge-3/2/1
ge-3/2/2 ge-3/2/3

ge-3/2/4 ge-3/2/5
ge-3/2/6 ge-3/2/7
ge-3/2/8 ge-3/2/9

ge-3/3/0 ge-3/3/1
ge-3/3/2 ge-3/3/3
ge-3/3/4 ge-3/3/5
ge-3/3/6 ge-3/3/7
ge-3/3/8 ge-3/3/9

g000112

196 Copyright © 2018, Juniper Networks, Inc.

 Documentation
Related
•
ge ge
-2 -3

0
1

1/0
ge /0 ge /0

Copyright © 2018, Juniper Networks, Inc.

-2 /0 -3 /0 ge
ge ge /0
ge /0 -2 -3
-2 /2 -3 /2 ge /0

0
ge /0 ge /0
ge /0/ -2 / 1 -3 / 1
-3 /4

10
-2 4 ge /0 ge /0
ge /0 -2 /3 ge /0 -3 /3
MIC-3D-40GE-TX

1
-3 /6

MIC-3D-40GE-TX
-2 /6 ge /0/ /0 ge /0/
/0

2
-2 5 ge /8 -3 5
ge /8
-2 ge /0/ -3 ge /0/
-2 7 ge / 1/ -3 7
ge / 1/
/ -3 0 /
-2 0 ge 0/ ge 0/
ge / 1/ ge / 1/ -3 9
-2 9 -3 2
-2 2 ge / 1/ /1 ge / 1/
/1 -2 1 -3 1
ge /4 ge /4
ge / 1/ -3 ge / 1/
-2 -3 3
-2 3 ge / 1/ /1
ge / 1/ /1
-2 6 -3 6 ge /5
ge /5
ge / 1/ -2 ge / 1/ -3
-3 8

MX Series MIC Overview on page 17

-2 8 ge / 1/ ge / 1/
ge /2 -2 7 ge /2 -3 7
-2 /0 -3 /0
ge / 1/ /2 ge / 1/
/2 /2 -3 9
ge /2 -2 9 ge
ge /2 -3 ge /2
-2 -3 / 1
ge /2/ -2 / 1 ge /2/ /2
/2 -3 4
-2 4 ge /3 ge /3
ge /2/ -2 ge /2/ -3
-2 6 / -3 6
/ ge /2/
/ ge 2/
-2 5 ge 2/8 -3 5
ge 2/8
-2 ge /2/ -3 ge /2/
-2 7 ge /3/ -3 7
ge /3/ /
Figure 34: Port Numbering for the Tri-Rate MIC (MX240)
Figure 33: Port Numbering for the Tri-Rate MIC (MX480)

-2 0 / -3 0 ge 2/9
ge 2/9 ge /3
ge /3 -2 -3
-2 /2 -3 /2 ge /3
ge /3 ge /3/
ge /3/ -2 / 1 -3 / 1
-2 4 -3 4 ge /3
ge /3
ge /3/ -2 /3 ge /3/ -3 /3
-2 6 -3 6 ge /3/
/3 ge /3/ /3
-2 5 /8 -3 5
/8 ge /3/
ge /3/
-2 7 -3 7
/3 /3
/9 /9

g000935 g000936

197
Chapter 9: MX Series MIC Descriptions
MX Series Interface Module Reference

MIC MRATE

Figure 35: 12-Port Multi-Rate MIC with QSFP+

Software release • Junos OS Release 15.1F5 with Junos Continuity

• Junos OS release 16.1R1 and later

For information about which MPCs support this MIC, see “MIC/MPC Compatibility” on page 26.
For information about which MICs are supported on MX Series routers, see “MICs Supported by
MX Series Routers” on page 18.

Description • Twelve Gigabit Ethernet ports that support quad small form-factor pluggable plus (QSFP+)
transceivers
• Power requirement;
• When installed into MPC8E: 1.250 A @ 48 V (60 W)
• When installed into MPC9E, or into MPC8E operating in 1.6 Tbps upgrade mode (licensed
feature): 1.771 A @ 48 V (85 W)

• Weight: 3.9 lb (1.77 kg)

• Model number: MIC-MRATE
• Name in the CLI: MRATE-12xQSFPP-XGE-XLGE-CGE

Hardware features • The ports are numbered 0 through 11.

• Twelve Gigabit Ethernet QSFP+ ports, each of which can be configured as a 40-Gigabit Ethernet
port or as four 10-Gigabit Ethernet ports by using a breakout cable.
• Eight out of the twelve ports can be configured as 100-Gigabit Ethernet ports. Port numbers 0
through 3, and 6 through 9 are the eight 100-Gigabit Ethernet ports.
• When used in MX2K-MP8CE:
• 4 ports out of the total 12 support 100-Gigabit Ethernet speed
• Maximum aggregate port capacity across ports 0 through 5 should not exceed 240 Gbps
• Maximum aggregate port capacity across ports 6 through 11 should not exceed 240 Gbps

• When used in MX2K-MPC9E:

• 8 ports out of the total 12 support 100-Gigabit Ethernet speed
• Maximum aggregate port capacity across ports 0 through 5 should not exceed 400 Gbps
• Maximum aggregate port capacity across ports 6 through 11 should not exceed 400 Gbps

Table 25 on page 199 lists the configurable Gbps Ethernet port speeds for each port.

Software features • Supports rate selectability at the port level.

• By default, the ports are configured as 10-Gigabit Ethernet ports.
• Supports remote port identification.

198 Copyright © 2018, Juniper Networks, Inc.

 Chapter 9: MX Series MIC Descriptions

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

LEDs • OK/FAIL LED, one bicolor:

• Steady green—MIC is functioning normally.
• Yellow—MIC has failed.

• Link LED, one green per port (4 per QSFP+ cage):

• Steady green—Link is up.
• Off—Link is down or disabled.
Each QSFP+ cage contains four LEDs, logically numbered from 0 through 3. These numbers
help you identify the corresponding cable when a breakout cable (4x10 Gigabit) is connected
to a port. On an installed MRATE MIC, the orientation of these LEDs is as follows: upper left 0,
upper right 1, lower left 2, and lower right 3.

Table 25: MIC MRATE Gigabit Ethernet Port Speed Capabilities

Port # 4x10 Gbps Ethernet 40 Gbps Ethernet 100 Gbps Ethernet

0 yes yes yes

1 yes yes yes

2 yes yes yes

3 yes yes yes

4 yes yes no

5 yes yes no

6 yes yes yes

7 yes yes yes

8 yes yes yes

9 yes yes yes

10 yes yes no

11 yes yes no

Related • Junos Continuity Software User Guide (Junos OS Release 14.1R4 and Later Releases)
Documentation
• Understanding Interface Naming Conventions for MIC-MRATE

• Understanding Rate Selectability

Copyright © 2018, Juniper Networks, Inc. 199

MX Series Interface Module Reference

• Configuring Rate Selectability on MIC-MRATE to Enable Different Port Speeds

Multiservices MIC

Figure 36: MS-MIC-16G

Supported Junos OS • Junos OS Release 13.2 and later

Release • Model number: MS-MIC-16G
• Name in the CLI: MS-MIC-16G

Description The Multiservices Modular Interfaces Card (MS-MIC) provides improved scaling and high performance
for MX series routers. The MS-MIC has enhanced memory (16 GB) and enhanced processing
capabilities.

Software Features • Active flow monitoring and export of flow monitoring version 9 records based on RFC 3954
• IP Security (IPsec) encryption
• Network Address Translation (NAT) for IP addresses

NOTE: The Multiservices MIC does not support Network Address Translation-Traversal (NAT-T).

• Port Address Translation (PAT) for port numbers

• Traffic sampling
• Stateful firewall with packet inspection—detects SYN attacks, ICMP and UDP floods, and
ping-of-death attacks
• Network Attack Protection (NAP)
• Support for up to 6000 service sets
• Support for MTUs up to 9192 bytes.
• Multiple services can be supported. See Junos OS Services Interfaces Library for Routing Devices
for more information.
• See “Protocols and Applications Supported by the MS-MIC and MS-MPC” on page 389 for
information about the protocols and applications that this MIC supports.

Hardware Features and • MICs are hot-removable and hot-insertable

Requirements • MS-MIC CPU Clock Cycle – 800MHz
• Works with SBCs and SBCEs
• Interoperable with MS-DPCs. Both MS-MPCs and MS-DPCs can co-exist in the same chassis
• Chassis requires enhanced fan trays and high-capacity DC or AC power supplies

NOTE: Only one Multiservices MIC is supported in each MPC.

NOTE: Starting in Junos OS Release 13.3R3, 14.1R2, 14.2R1, MX104 routers support only two
Multiservices MICs.

200 Copyright © 2018, Juniper Networks, Inc.

 Chapter 9: MX Series MIC Descriptions

Input/Output Power MS-MIC—6.67 amps @ 9V (60W)

Requirements

Weight and Dimensions Weight: 2 lbs (.91 kg); Height: 0.9 in. (2.26 cm); Width: 6 in. (15.24 cm); Depth: 7 in. (17.78 cm)

MPC Support • Multiservices MPC on page 86

• See “MIC/MPC Compatibility” on page 26 for a list of the MPCs that support the MS-MIC.

LEDs Application activity tricolor LED, labeled APP STATUS:

• Off—Application is not running.

• Red—Application has failed.
• Yellow—Application is reconfiguring.
• Green—Application is running.

MIC activity tricolor LED, labeled MIC STATUS:

• Off—MIC has failed.

• Red—MIC has an error or failure.
• Yellow—MIC is transitioning online or offline.
• Green—MIC is functioning normally.

Related • Multiservices MPC on page 86

Documentation
• MX Series MIC Overview on page 17

• Junos OS Services Interfaces Library for Routing Devices

• Protocols and Applications Supported by the MS-MIC and MS-MPC on page 389

• MIC/MPC Compatibility on page 26

• Example: Inter-Chassis Stateful High Availability for NAT and Stateful Firewall (MS-MIC,
MS-MPC)

• Example: Configuring Flow Monitoring on MS-MIC and MS-MPC

• Inter-Chassis High Availability for MS-MIC and MS-MPC

• Example: Configuring Junos VPN Site Secure on MS-MIC and MS-MPC

• ICMP, Ping, and Traceroute ALGs for MS-MICs and MS-MPCs

• MICs Supported by MX Series Routers on page 18

Copyright © 2018, Juniper Networks, Inc. 201

MX Series Interface Module Reference

SONET/SDH OC3/STM1 (Multi-Rate) MICs with SFP

Figure 37: 4-Port SONET/SDH OC3/STM1 (Multi-Rate) MIC with SFP

MIC-3D-4OC3OC12-
1OC48

LINK

LINK

LINK

LINK
MIC-3D-4OC3OC12-

g006066
1OC48

0 1 2 3

Figure 38: 8-Port SONET/SDH OC3/STM1 (Multi-Rate) MIC with SFP

MIC-3D-8OC3OC12-
4OC48
LINK

LINK

LINK

LINK

LINK

LINK

LINK

LINK
MIC-3D-8OC3OC12-

OK/ FAIL

g006067
4OC48

0 1 2 3 4 5 6 7

Software release • 4-port: Junos OS Release 11.2 and later

• 8-port: Junos OS Release 11.2 and later

For information on which MPCs support these MICs, see “MIC/MPC Compatibility” on page 26.
For information on which MICs are supported on MX Series routers, see “MICs Supported by MX
Series Routers” on page 18.

202 Copyright © 2018, Juniper Networks, Inc.

 Chapter 9: MX Series MIC Descriptions

Description • 4-port: 4 OC3/STM1 or OC12/STM4 ports

• Each port is rate-selectable and supports OC3, OC12, or OC48.
• The ports can be configured to support a combination of OC3, OC12, and OC48 rates. In the
combination, you can configure only one port to support OC48, whereas OC3 or OC12 can
be configured on all four ports.

• 8-port: 8 OC3/STM1 or OC12/STM4 ports

• Each port is rate-selectable and supports OC3, OC12, or OC48.
• The ports can be configured to support a combination of OC3, OC12, and OC48 rates. In the
combination, you can configure only four ports to support OC48, whereas OC3 or OC12 can
be configured on all eight ports.

• Power requirement:
• 4-port: 2.6 A @ 9 V (23.4 W)
• 8-port: 3.1 A @ 9 V (27.9 W)

• Weight:
• 4-port: 1.27 lb (0.58 kg)
• 8-port: 1.47 lb (0.67 kg)

• Model number:
• 4-port: MIC-3D-4OC3OC12-1OC48
• 8-port: MIC-3D-8OC3OC12-4OC48

Hardware features • The ports are labeled:

• 4-port: 0-3
• 8-port: 0-7

• Maximum transmission units (MTUs) of up to 9192 bytes

Software features • Per-port SONET/SDH framing

• Local and remote loopback on each port
• Optical diagnostics and monitoring
• Clocking options: internal or external/loop mode.
• Unified in-service software upgrade (unified ISSU)
• Encapsulations:
• Multiprotocol Label Switching (MPLS) fast reroute
• MPLS CCC (circuit cross-connect)
• MPLS TCC (translational cross-connect)
• Cisco High-Level Data Link Control
• Cisco HDLC CCC
• Cisco HDLC TCC
• Point-to-Point Protocol (PPP)
• PPP for CCC
• PPP for TCC
• Flexible Frame Relay
• Frame Relay
• Frame Relay for CCC
• Frame Relay for TCC
• PPP over Frame Relay

NOTE: Ethernet over Frame Relay is not supported.

Copyright © 2018, Juniper Networks, Inc. 203

MX Series Interface Module Reference

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

LEDs OK/FAIL LED, one bicolor:

• Green—MIC is functioning normally

• Red—MIC has failed

LINK LED, one green per port:

• Off—Not enabled
• Green—Online with no alarms or failures
• Yellow—Online with alarms for remote failures
• Red—Active with a local alarm; router has detected a failure

204 Copyright © 2018, Juniper Networks, Inc.

 Chapter 9: MX Series MIC Descriptions

Alarms, errors, and SONET alarms:

events
• Loss of light (LOL)
• Loss of signal (LOS)
• Loss of frame (LOF)
• Phase lock loop (PLL)
• Severely errored frame (SEF)
• Alarm indicator signal–line (AIS-L)
• Alarm indicator signal–path (AIS-P)
• Remote defect indicator–line (RDI-L)
• Remote defect indicator–path (RDI-P)
• Loss of pointer–path (LOP-P)
• Bit error rate–signal degrade (BERR-SD)
• Bit error rate–signal fail (BERR-SF)
• Payload label mismatch–Path (PLM-P)
• Unequipped–path (UNEQ-P)
• Remote error indicator–path (REI-P)

SDH alarms:

• Loss of light (LOL)

• Phase lock loop (PLL)
• Loss of frame (LOF)
• Loss of signal (LOS)
• Severely errored frame (SEF)
• Multiplex-section alarm indicator signal (MS-AIS)
• H Path alarm indicator signal (HP-AIS)
• Loss of pointer (LOP)
• Bit error rate–signal degrade (BER-SD)
• Bit error rate–signal fail (BER-SF)
• Multiplex section–far end receive failure (MS-FERF)
• High order path–far end receive failure (HP-FERF)
• High order path–payload label mismatch (HP-PLM)
• Remote error indicator (REI)
• Unequipped (UNEQ)

Related • MX Series MIC Overview on page 17

Documentation

Copyright © 2018, Juniper Networks, Inc. 205

MX Series Interface Module Reference

Multi-Rate Ethernet MIC

Figure 39: Multi-Rate MIC with QSFP+

Figure 40: Multi-Rate MACsec MIC with QSFP+

JNP-MIC1-MACSEC

g100068
Figure 41: Multi-Rate MACsec MIC with QSFP+
MIC-MACSEC-MRATE

g100069

Software release • JNP-MIC1:

Junos OS release 17.3R1 and later
• JNP-MIC1-MACSEC:
Junos OS release 17.3R2 and later
• MIC-MACSEC-MRATE:
Junos OS release 17.4R1 and later

For information about which MPCs support this MIC, see “MIC/MPC Compatibility” on page 26.
For information about which MICs are supported on MX Series routers, see “MICs Supported by
MX Series Routers” on page 18.

206 Copyright © 2018, Juniper Networks, Inc.

 Chapter 9: MX Series MIC Descriptions

Description • Weight: 3 lb (1.36 kg)

• Model numbers:
Without MACsec support: JNP-MIC1
With MACsec support: JNP-MIC1-MACSEC
With MACsec support: MIC-MACSEC-MRATE
• Power requirement:
• JNP-MIC1:
85 W at 55° C
80 W at 25° C
• JNP-MIC1-MACSEC:
130 W at 55° C
125 W at 25° C
• MIC-MACSEC-MRATE:
110 W at 45° C
105 W at 25° C

• Name in the CLI:

JNP-MIC1: MIC1
JNP-MIC1-MACSEC: MIC1-MACSEC
MIC-MACSEC-MRATE: MACSEC-12xQSFPP-XGE-XLGE-CGE

Hardware features • JNP-MIC1 and JNP-MIC1-MACSEC:

• Twelve 100-Gigabit Ethernet ports that support quad small form-factor pluggable (QSFP28)
transceivers
• The ports are numbered 0 through 11.
• Each port can be configured as a 100-Gigabit Ethernet port, 40-Gigabit Ethernet port, or as
four 10-Gigabit Ethernet ports (by using a breakout cable).
Table 26 on page 208 lists the configurable Gigabit Ethernet port speeds for each port.
• MIC-MACSEC-MRATE:
• Twelve Gigabit Ethernet QSFP+ ports, each of which can be configured as a 40-Gigabit
Ethernet port or as four 10-Gigabit Ethernet ports (by using a breakout cable).
• The ports are numbered 0 through 11.
• Eight out of the twelve ports can be configured as 100-Gigabit Ethernet ports. Port numbers
0 through 3, and 6 through 9 are the eight 100-Gigabit Ethernet ports.
• When used in MP8CE:
• Four ports out of the total twelve ports support 100-Gigabit Ethernet speed

• Maximum aggregate port capacity across ports 0 through 5 should not exceed 240 Gbps
• Maximum aggregate port capacity across ports 6 through 11 should not exceed 240 Gbps

• When used in MPC9E:

• Eight ports out of the total twelve ports support 100-Gigabit Ethernet speed

• Maximum aggregate port capacity across ports 0 through 5 should not exceed 400 Gbps
• Maximum aggregate port capacity across ports 6 through 11 should not exceed 400 Gbp

Table 27 on page 208 lists the configurable Gigabit Ethernet port speeds for each port.

Software features • Supports rate selectability at the port level.

• By default, the ports are configured as 10-Gigabit Ethernet ports.
• Supports remote port identification.
• MICs with model numbers JNP-MIC1-MACSEC and MIC-MACSEC-MRATE support Media Access
Control Security (MACsec)

Copyright © 2018, Juniper Networks, Inc. 207

MX Series Interface Module Reference

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

LEDs • OK/FAIL LED, one bicolor:

• OFF—MIC is offline or MIC has fault.
• Red—MIC is in power failure state.
• Green—MIC is online.

• Link LED, one green per port:

• Steady green—Link is up.
• Off—Link is down or disabled.

• Like port status LED, each individual lane LED support four states as: OFF, AMBER, GREEN,
RED. See MPC and MIC Lane LED Scheme Overview for more details.

Table 26: Multi Rate Ethernet MIC Port Speed Capabilities for JNP-MIC1 and JNP-MIC1-MACSEC

Port # 4x10-Gigabit Ethernet 40-Gigabit Ethernet 100-Gigabit Ethernet

0 yes yes yes

1 yes yes yes

2 yes yes yes

3 yes yes yes

4 yes yes yes

5 yes yes yes

6 yes yes yes

7 yes yes yes

8 yes yes yes

9 yes yes yes

10 yes yes yes

11 yes yes yes

Table 27: Multi Rate Ethernet MIC Port Speed Capabilities for MIC-MACSEC-MRATE

Port # 4x10-Gigabit Ethernet 40-Gigabit Ethernet 100-Gigabit Ethernet

0 yes yes yes

208 Copyright © 2018, Juniper Networks, Inc.

 Chapter 9: MX Series MIC Descriptions

Table 27: Multi Rate Ethernet MIC Port Speed Capabilities for MIC-MACSEC-MRATE (continued)

Port # 4x10-Gigabit Ethernet 40-Gigabit Ethernet 100-Gigabit Ethernet

1 yes yes yes

2 yes yes yes

3 yes yes yes

4 yes yes no

5 yes yes no

6 yes yes yes

7 yes yes yes

8 yes yes yes

9 yes yes yes

10 yes yes no

11 yes yes no

Related • MPC and MIC Lane LED Scheme Overview

Documentation
• Configuring Rate Selectability on MX10003 MPC to Enable Different Port Speeds

• MX10003 MPC Rate-Selectability Overview

• Understanding Rate Selectability

SONET/SDH OC192/STM64 MIC with XFP

Figure 42: SONET/SDH OC192/STM64 MIC with XFP

MIC-3D-1OC192-XFP
MIC-3D-1OC192-

g006588
XFP

Software release • Junos OS Release 12.2 and later

For information on which MPCs support this MIC, see “MIC/MPC Compatibility” on page 26. For
information on which MICs are supported on MX Series routers, see “MICs Supported by MX Series
Routers” on page 18.

Copyright © 2018, Juniper Networks, Inc. 209

MX Series Interface Module Reference

Description • One OC192 port

• Clear channel functionality
• Power requirement: 4.25 A @ 9 V (38.25 W)
• Weight: 1.34 lb (0.61 kg)
• Model number: MIC-3D-1OC192-XFP

Hardware features • Maximum transmission units (MTUs) of up to 9192 bytes

• MIC bandwidth of up to 10 Gbps

Software features • SONET/SDH framing

• Multiprotocol Label Switching (MPLS) fast reroute
• Ingress behavior aggregate (BA) classification
• Internal and loop clocking
• Encapsulations:
• MPLS fast reroute
• MPLS CCC (circuit cross-connection)
• MPLS TCC (translational cross-connection)
• Cisco High-Level Data Link Control (cHDLC)
• Cisco HDLC CCC
• Cisco HDLC TCC
• Point-to-Point Protocol (PPP)
• PPP for CCC
• PPP for TCC
• Flexible Frame Relay
• Frame Relay
• Frame Relay for CCC
• Frame Relay for TCC
• PPP over Frame Relay

NOTE: Ethernet over Frame Relay is not supported.

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

NOTE: To extend the life of the laser, when a MIC is not being actively used with any valid links,
take the MIC offline until you are ready to establish a link to another device. For information about
taking a MIC offline, see the request chassis pic offline command in the CLI Explorer.

LEDs OK/FAIL LED, one bicolor:

• Green—MIC is functioning normally

• Red—MIC has failed

LINK LED, one tricolor per port:

• Off—Not enabled
• Green—Online with no alarms or failures
• Yellow—Online with alarms for remote failures
• Red—Active with a local alarm; router has detected a failure

210 Copyright © 2018, Juniper Networks, Inc.

 Chapter 9: MX Series MIC Descriptions

Alarms, errors, and SONET alarms:

events
• Loss of light (LOL)
• Phase lock loop (PLL)
• Loss of signal (LOS)
• Loss of frame (LOF)
• Severely errored frame (SEF)
• Alarm indicator signal–line (AIS-L)
• Alarm indicator signal–path (AIS-P)
• Remote defect indicator–line (RDI-L)
• Remote defect indicator–path (RDI-P)
• Loss of pointer–path (LOP-P)
• Bit error rate–signal degrade (BERR-SD)
• Bit error rate–signal fail (BERR-SF)
• Payload label mismatch–Path (PLM-P)
• Unequipped–path (UNEQ-P)
• Remote error indicator–path (REI-P)

SDH alarms:

• Loss of light (LOL)

• Phase lock loop (PLL)
• Loss of frame (LOF)
• Loss of signal (LOS)
• Severely errored frame (SEF)
• Multiplex-section alarm indicator signal (MS-AIS)
• Higher order path–alarm indication signal (HP-AIS)
• Loss of pointer (LOP)
• Bit error rate–signal degrade (BER-SD)
• Bit error rate–signal fail (BER-SF)
• Multiplex section–far end receive failure (MS-FERF)
• Higher order path—far-end receive failure (HP-FERF)
• Higher order path—payload label mismatch (HP-PLM)
• Remote error indicator (REI)
• Unequipped (UNEQ)

Related • MX Series MIC Overview on page 17

Documentation

Copyright © 2018, Juniper Networks, Inc. 211

MX Series Interface Module Reference

212 Copyright © 2018, Juniper Networks, Inc.

CHAPTER 10

MX Series PIC Descriptions

• Channelized OC12/STM4 Enhanced IQ (IQE) PIC with SFP on page 213

• Channelized OC48/STM16 Enhanced IQ (IQE) PIC with SFP on page 214
• SONET/SDH OC3/STM1 (Multi-Rate) PIC with SFP on page 220
• SONET/SDH OC12/STM4 (Multi-Rate) PIC with SFP on page 223
• SONET/SDH OC48/STM16 Enhanced IQ (IQE) PIC with SFP on page 226
• SONET/SDH OC48/STM16 (Multi-Rate) PIC with SFP on page 230
• SONET/SDH OC48/STM16 PIC with SFP on page 233
• SONET/SDH OC192c/STM64 PIC on page 236
• SONET/SDH OC192c/STM64 PIC with XFP on page 239

Channelized OC12/STM4 Enhanced IQ (IQE) PIC with SFP

g004426

Software release • Junos 9.5 and later

Related • MX Series FPC and PIC Overview on page 35

Documentation
• FPCs Supported by MX240, MX480, and MX960 Routers on page 36

Copyright © 2018, Juniper Networks, Inc. 213

MX Series Interface Module Reference

• PICs Supported by MX240, MX480, and MX960 Routers on page 37

• High Availability Features on page 36

Channelized OC48/STM16 Enhanced IQ (IQE) PIC with SFP

Software release • Junos 9.5 and later

Description • One OC48/STM16 port

• SONET or SDH is configurable on a per-port granularity
• SONET channelization:
• 4 OC12 channel
• 16 OC3 channels
• 48 DS3 channels
• 672 DS1 channels
• 975 DS0 channels

• SDH channelization:
• 4 STM4 channel
• 16 STM1 channels
• 48 E3 channels
• 504 E1 channels
• 975 DS0 channels

• Power requirement: 1.10 A @ 48V (53 W)

• Model Number: PB-1CHOC48-STM16-IQE-SFP

Hardware features • Port is numbered 0.

214 Copyright © 2018, Juniper Networks, Inc.

 Chapter 10: MX Series PIC Descriptions

Software features • Quality of service (QoS) per channel: weighted round-robin (WRR), random early detection
(RED), weighted random early detection (WRED)
• Enhanced fine-grained queuing per logical interface. See the Class of Service Feature Guide for
Routing Devices and EX9200 Switches for more information about class of service features.
• Subrate and scrambling:
• Digital Link/Quick Eagle
• Kentrox
• Larscom
• ADTRAN
• Verilink

• Packet buffering, Layer 2 parsing

• M13/C-bit parity encoding
• DS3 far-end alarm and control (FEAC) channel support
• Local line, remote line, and remote payload loopback testing
• Simple Network Management Protocol (SNMP): OC12, OC3 MIB, DS3 MIB, T1 MIB
• Dynamic, arbitrary channel configuration
• Full bit error rate test (BERT)
• Encapsulations:

• Circuit cross-connect (CCC)

• Translational cross-connect (TCC)
• Extended Frame Relay for CCC and TCC
• Flexible Frame Relay
• Frame Relay
• Frame Relay for CCC
• Frame Relay for TCC
• Frame Relay port CCC
• High-Level Data Link Control (HDLC)
• HDLC framing for CCC
• HDLC framing for TCC
• MPLS CCC
• MPLS TCC
• Multilink Frame Relay (MLFR) UNI NNI (MFR FRF.16)
• Point-to-Point Protocol (PPP)
• PPP for CCC
• PPP for TCC

• Encapsulations available only for DS1:

• Multilink Frame Relay end-to-end (MLFR FRF.15)

• Multilink PPP (MLPPP)
• PPP over Frame Relay

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

Copyright © 2018, Juniper Networks, Inc. 215

MX Series Interface Module Reference

LEDs One tricolor per port:

• Off—Not enabled
• Green—Online with no alarms or failures
• Yellow—Online with alarms for remote failures
• Red—Active with a local alarm; router has detected a failure

216 Copyright © 2018, Juniper Networks, Inc.

 Chapter 10: MX Series PIC Descriptions

Alarms, errors, and

events

Copyright © 2018, Juniper Networks, Inc. 217

MX Series Interface Module Reference

SONET alarms:

• Alarm indication signal—line (AIS-L)

• Alarm indication signal—path (AIS-P)
• Bit error rate—signal degrade (BERR-SD)
• Bit error rate—signal fail (BERR-SF)
• Loss of frame (LOF)
• Loss of light (LOL)
• Loss of pointer (LOP)
• Loss of signal (LOS)
• Payload label mismatch (PLM-P)
• Remote defect indication—line (RDI-L)
• Remote defect indication—path (RDI-P)
• Remote error indication (REI)
• Payload unequipped (unequipped STS at path level) (UNEQ-P)
• Virtual container—alarm indication signal (VAIS)
• Virtual container—loss of pointer (VLOP)
• Virtual container—mismatch (VMIS)
• Virtual container—remote defect indication (VRD1)
• Virtual container—unequipped (VUNEQ)
SDH alarms:

• Administrative unit alarm indication signal (AU-AIS)

• Bit error rate—signal degrade (BERR-SD)
• Bit error rate—signal fail (BERR-SF)
• Bit interleaved parity (BIP) error B1, B2, B3
• Higher order path—alarm indication signal (HP-AIS)
• Higher order path—far-end receive failure (HP-FERF)
• Higher order path—payload label mismatch (HP-PLM)
• Higher order path—loss of pointer (HP-LOP)
• Higher order path—remote defect indication (HP-RDI)
• Higher order path—unequipped (HP-UNEQ)
• Loss of frame (LOF)
• Loss of light (LOL)
• Loss of signal (LOS)
• Multiplex section—alarm indication signal (MS-AIS)
• Multiplex section—far-end receive failure (MS-FERF)
• Multiplex section—remote defect indication (MS-RDI)
• Multiplex section—remote error indication (MS-REI)
• Phase lock loop (PLL)
• Remote error indication (REI)
• Severely errored frame (SEF)
• Tributary unit—alarm indication signal (TU-AIS)
• Tributary unit—loss of pointer (TU-LOP)
• Tributary unit—mismatch (TU-MIS)
• Tributary unit—remote defect indication (TU-RD1)
• Tributary unit—unequipped (TU-UNEQ)
DS1 alarms:

218 Copyright © 2018, Juniper Networks, Inc.

 Chapter 10: MX Series PIC Descriptions

• Alarm indication signal (AIS)

• Loss of frame (LOF)
• Remote alarm indication signal (RAIS)
• DS1 error detection:

• Bursty errored seconds (BES)

• CRC errors
• Errored seconds (ES)
• Line errored seconds (LES)
• Loss of framing seconds (LOFS)
• Severely errored seconds (SES)
• Severely errored framing seconds (SEFS)
• Unavailable seconds (UAS)
• DS3 alarms:

• Alarm indication signal (AIS)

• Loss of frame (LOF)
• Yellow alarm

• DS3 error detection:

• C-bit code violations (CCV)

• C-bit errored seconds (CES)
• C-bit severely errored framing seconds (CEFS)
• CRC errors
• Excessive zeros (EXZ)
• Far-end block error (FEBE)
• Far-end receive failure (FERF)
• Line errored seconds (LES)
• Parity bit (P-bit) code violations (PCV)
• Parity bit (P-bit) errored seconds (PES)
• Parity bit (P-bit) severely errored framing seconds (PSES)
• Severely errored framing seconds (SEFS)
• Unavailable seconds (UAS)

Instrumentation • Layer 2 per-queue and per-channel packet and byte counters

(counters)

Related • MX Series FPC and PIC Overview on page 35

Documentation
• FPCs Supported by MX240, MX480, and MX960 Routers on page 36

• PICs Supported by MX240, MX480, and MX960 Routers on page 37

• High Availability Features on page 36

Copyright © 2018, Juniper Networks, Inc. 219

MX Series Interface Module Reference

SONET/SDH OC3/STM1 (Multi-Rate) PIC with SFP

PORT 3

Software release • Junos 9.5 and later

Description • Rate-selectable using one of the following rates:

• 1-port OC12/STM4
• 1-port OC12c/STM4c
• 4-port OC3c/STM1c

• Power requirement: 0.40 A @ 48 V (19 W)

• Model Number: PB-4OC3-1OC12-SON-SFP

Hardware features • Multiplexing and demultiplexing

• Rate policing on input
• Rate shaping on output
• Packet buffering, Layer 2 parsing

Software features • Optical diagnostics and related alarms

• Per-port SONET/SDH framing
• Link aggregation
• Alarm and event counting and detection
• Dual-router automatic protection switching (APS)
• Multiprotocol Label Switching (MPLS) fast reroute
• Encapsulations:
• Circuit cross-connect (CCC)
• Translational cross-connect (TCC)
• Frame Relay
• High-Level Data Link Control (HDLC)
• Point-to-Point Protocol (PPP)

220 Copyright © 2018, Juniper Networks, Inc.

 Chapter 10: MX Series PIC Descriptions

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

NOTE: To extend the life of the laser, when a PIC is not being actively used with any valid links,
take the PIC offline until you are ready to establish a link to another device. For information about
taking a PIC offline, see the request chassis pic offline command in the CLI Explorer.

LEDs One tricolor per port:

• Off—Not enabled
• Green—Online with no alarms or failures
• Yellow—Online with alarms for remote failures
• Red—Active with a local alarm; router has detected a failure

Copyright © 2018, Juniper Networks, Inc. 221

MX Series Interface Module Reference

Alarms, errors, and • SONET alarms:

events • Alarm indication signal—line (AIS-L)
• Alarm indication signal—path (AIS-P)
• Bit error rate—signal degrade (BERR-SD)
• Bit error rate—signal fail (BERR-SF)
• Bit interleaved parity (BIP) error B1, B2, B3
• Far-end bit error: remote error indication—line (REI-L), far-end line coding violations (CV-LFE)
• Far-end bit error: remote error indication—path (REI-P), far-end path coding violations
(CV-PFE)
• Loss of frame (LOF)
• Loss of pointer (LOP-P)
• Loss of signal (LOS)
• Payload label mismatch (PLM-P)
• Payload unequipped (unequipped STS at path level) (UNEQ-P)
• Remote defect indication—line (RDI-L)
• Remote defect indication—path (RDI-P)

• SDH alarms:
• Administrative unit alarm indication signal (AU-AIS)
• Bit error rate signal degrade (BERR-SD)
• Bit error rate signal fail (BERR-SF)
• Bit interleaved parity (BIP) error B1, B2, B3
• Higher order path—payload label mismatch (HP-PLM)
• Higher order path—loss of pointer (HP-LOP)
• Higher order path—remote defect indication (HP-RDI)
• Higher order path—unequipped (HP-UNEQ)
• Loss of frame (LOF)
• Loss of signal (LOS)
• Multiplex section—alarm indication signal (MS-AIS)
• Multiplex section—remote defect indication (MS-RDI)
• Multiplex section—remote error indication (MS-REI)

• Error detection:

• Errored seconds (ES-S, ES-L, ES-P)

• Far-end errored seconds (ES-LFE, ES-PFE)
• Far-end severely errored seconds (SES-LFE, SES-PFE)
• Far-end unavailable seconds (UAS-LFE, UAS-PFE)
• Severely errored frames (SEF)
• Severely errored framing seconds (SEFS-S)
• Severely errored seconds (SES-S, SES-L, SES-P)
• Unavailable seconds (UAS-L, UAS-P)

Related • MX Series FPC and PIC Overview on page 35

Documentation
• FPCs Supported by MX240, MX480, and MX960 Routers on page 36

• PICs Supported by MX240, MX480, and MX960 Routers on page 37

• High Availability Features on page 36

222 Copyright © 2018, Juniper Networks, Inc.

 Chapter 10: MX Series PIC Descriptions

SONET/SDH OC12/STM4 (Multi-Rate) PIC with SFP

Software release • Junos 9.5 and later

Description • Rate-selectable using one of the following rates:

• 1-port OC12
• 1-port OC48
• 1-port OC48c
• 4-port OC3c
• 4-port OC12c

• Power requirement: 0.40 A @ 48 V (19 W)

• Model Number: PB-4OC3-4OC12-SON-SFP

Hardware features • Multiplexing and demultiplexing

• Rate policing on input
• Rate shaping on output
• Packet buffering, Layer 2 parsing

Software features • Optical diagnostics and related alarms

• Per-port SONET/SDH framing
• Link aggregation
• Alarm and event counting and detection
• Dual-router automatic protection switching (APS)
• Multiprotocol Label Switching (MPLS) fast reroute
• Encapsulations:
• Circuit cross-connect (CCC)
• Translational cross-connect (TCC)
• Frame Relay
• High-Level Data Link Control (HDLC)
• Point-to-Point Protocol (PPP)

Copyright © 2018, Juniper Networks, Inc. 223

MX Series Interface Module Reference

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

NOTE: To extend the life of the laser, when a PIC is not being actively used with any valid links,
take the PIC offline until you are ready to establish a link to another device. For information about
taking a PIC offline, see the request chassis pic offline command in the CLI Explorer.

LEDs One tricolor per port:

• Off—Not enabled
• Green—Online with no alarms or failures
• Yellow—Online with alarms for remote failures
• Red—Active with a local alarm; router has detected a failure

224 Copyright © 2018, Juniper Networks, Inc.

 Chapter 10: MX Series PIC Descriptions

Alarms, errors, and • SONET alarms:

events • Alarm indication signal—line (AIS-L)
• Alarm indication signal—path (AIS-P)
• Bit error rate—signal degrade (BERR-SD)
• Bit error rate—signal fail (BERR-SF)
• Bit interleaved parity (BIP) error B1, B2, B3
• Far-end bit error: remote error indication—line (REI-L), far-end line coding violations (CV-LFE)
• Far-end bit error: remote error indication—path (REI-P), far-end path coding violations
(CV-PFE)
• Loss of frame (LOF)
• Loss of pointer (LOP-P)
• Loss of signal (LOS)
• Payload label mismatch (PLM-P)
• Payload unequipped (unequipped STS at path level) (UNEQ-P)
• Remote defect indication—line (RDI-L)
• Remote defect indication—path (RDI-P)

• SDH alarms:
• Administrative unit alarm indication signal (AU-AIS)
• Bit error rate signal degrade (BERR-SD)
• Bit error rate signal fail (BERR-SF)
• Bit interleaved parity (BIP) error B1, B2, B3
• Higher order path—payload label mismatch (HP-PLM)
• Higher order path—loss of pointer (HP-LOP)
• Higher order path—remote defect indication (HP-RDI)
• Higher order path—unequipped (HP-UNEQ)
• Loss of frame (LOF)
• Loss of signal (LOS)
• Multiplex section—alarm indication signal (MS-AIS)
• Multiplex section—remote defect indication (MS-RDI)
• Multiplex section—remote error indication (MS-REI)

• Error detection:

• Errored seconds (ES-S, ES-L, ES-P)

• Far-end errored seconds (ES-LFE, ES-PFE)
• Far-end severely errored seconds (SES-LFE, SES-PFE)
• Far-end unavailable seconds (UAS-LFE, UAS-PFE)
• Severely errored frames (SEF)
• Severely errored framing seconds (SEFS-S)
• Severely errored seconds (SES-S, SES-L, SES-P)
• Unavailable seconds (UAS-L, UAS-P)

Related • MX Series FPC and PIC Overview on page 35

Documentation
• FPCs Supported by MX240, MX480, and MX960 Routers on page 36

• PICs Supported by MX240, MX480, and MX960 Routers on page 37

• High Availability Features on page 36

Copyright © 2018, Juniper Networks, Inc. 225

MX Series Interface Module Reference

SONET/SDH OC48/STM16 Enhanced IQ (IQE) PIC with SFP

Software release • Junos OS Release 10.4R2 and later (Type 3) g006030

Description • Four OC48/STM16 ports

• Clear channel functionality
• SONET and SDH is configured on a per-port granularity
• Power requirement: 1.06 A @ 48 V (51 W)
• Weight: 1.6 lb (0.725 kg)
• Model number: PC-4OC48-STM16-IQE-SFP

Hardware features • Ports are numbered:

• Top row: 0 and 1 from left to right
• Bottom row: 2 and 3 from left to right

• Maximum transmission units (MTUs) of up to 9192 bytes

226 Copyright © 2018, Juniper Networks, Inc.

 Chapter 10: MX Series PIC Descriptions

Software features • Quality of service (QoS) per channel: weighted round-robin (WRR), random early detection
(RED), weighted random early detection (WRED)
• Fine-grained egress queuing per logical interface. See the Class of Service Feature Guide for
Routing Devices and EX9200 Switches for more information about class-of-service features
• Packet buffering
• Local line and remote payload loopback testing
• Optical diagnostics and monitoring
• Clocking options: internal or external/loop mode. Each OC48 transmitter port is configured
either in internal or external mode. The default clocking option is internal mode.
• Encapsulations:
• Extended Frame Relay for circuit cross-connect (CCC) and translational cross-connect
(TCC)
• Flexible Frame Relay
• Frame Relay
• Frame Relay for CCC
• Frame Relay for TCC
• Frame Relay port CCC
• High-Level Data Link Control (HDLC)
• HDLC framing for CCC
• HDLC framing for TCC
• MPLS CCC
• MPLS TCC
• Point-to-Point Protocol (PPP)
• PPP for CCC
• PPP for TCC

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

NOTE: To extend the life of the laser, when a PIC is not being actively used with any valid links,
take the PIC offline until you are ready to establish a link to another device. For information about
taking a PIC offline, see the request chassis pic offline command in the CLI Explorer.

Copyright © 2018, Juniper Networks, Inc. 227

MX Series Interface Module Reference

LEDs OK LED, one tricolor:

• Off—PIC is offline and safe to remove from the router

• Green—PIC is operating normally
• Yellow—PIC is initializing
• Red—PIC has an error or failure

APP LED, one green per port:

• Off—Service is not running

• Green—Service is running under acceptable load

Port LEDs, one tricolor per port:

• Off—Not enabled
• Green—Online with no alarms or failures
• Yellow—Online with alarms for remote failures
• Red—Active with a local alarm; router has detected a failure

228 Copyright © 2018, Juniper Networks, Inc.

 Chapter 10: MX Series PIC Descriptions

Alarms, errors, and SONET alarms:

events
• Loss of light (LOL)
• Phase lock loop (PLL)
• Loss of frame (LOF)
• Loss of signal (LOS)
• Severely errored frame (SEF)
• Alarm indicator signal—line (AIS-L)
• Alarm indicator signal—path (AIS-P)
• Loss of pointer (LOP)
• Bit error rate—signal degrade (BERR-SD)
• Bit error rate—signal fail (BERR-SF)
• Remote defect indicator—line (RDI-L)
• Remote defect indicator—path (RDI-P)
• Remote error indicator (REI)
• Unequipped (UNEQ)
• Payload label mismatch—path (PLM-P)

SDH alarms:

• Loss of light (LOL)

• Phase lock loop (PLL)
• Loss of frame (LOF)
• Loss of signal (LOS)
• Severely errored frame (SEF)
• Multiplex-section alarm indicator signal (MS-AIS)
• H Path alarm indicator signal (HP-AIS)
• Loss of pointer (LOP)
• Bit error rate—signal degrade (BERR-SD)
• Bit error rate—signal fail (BERR-SF)
• Multiplex section—far end receive failure (MS-FERF)
• High order path—far end receive failure (HP-FERF)
• Remote error indicator (REI)
• Unequipped (UNEQ)
• High order path—payload label mismatch - Path (HP-PLM)

Optical diagnostics related alarms:

NOTE: Transceivers from some vendors do not support these fields.

• Temperature high/low alarms and warnings

• Supply voltage high/low alarms and warnings
• Tx bias current high/low alarms and warnings
• Tx output power high/low alarms and warnings
• Rx received power high/low alarms and warnings

Related • MX Series FPC and PIC Overview on page 35

Documentation
• FPCs Supported by MX240, MX480, and MX960 Routers on page 36

• PICs Supported by MX240, MX480, and MX960 Routers on page 37

Copyright © 2018, Juniper Networks, Inc. 229

MX Series Interface Module Reference

• High Availability Features on page 36

SONET/SDH OC48/STM16 (Multi-Rate) PIC with SFP

Software release • Junos 9.5 and later

Description • Rate-selectable using one of the following rates:

• 1-port OC3c/STM1c
• 1-port OC12/STM4
• 1-port OC12c/STM4c
• 1-port OC48/STM16
• 1-port OC48c/STM16c

• Power requirement: 0.20 A @ 48 V (9.5 W)

• Model Number: PB-1OC48-SON-B-SFP

Hardware features • Multiplexing and demultiplexing

• Rate policing on input
• Rate shaping on output
• Packet buffering, Layer 2 parsing

230 Copyright © 2018, Juniper Networks, Inc.

 Chapter 10: MX Series PIC Descriptions

Software features • Optical diagnostics and related alarms

• Per-port SONET/SDH framing
• Link aggregation
• Alarm and event counting and detection
• Dual-router automatic protection switching (APS)
• Multiprotocol Label Switching (MPLS) fast reroute
• Encapsulations:
• Circuit cross-connect (CCC)
• Translational cross-connect (TCC)
• Frame Relay
• High-Level Data Link Control (HDLC)
• Point-to-Point Protocol (PPP)

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

NOTE: To extend the life of the laser, when a PIC is not being actively used with any valid links,
take the PIC offline until you are ready to establish a link to another device. For information about
taking a PIC offline, see the request chassis pic offline command in the CLI Explorer.

LEDs One tricolor per port:

• Off—Not enabled
• Green—Online with no alarms or failures
• Yellow—Online with alarms for remote failures
• Red—Active with a local alarm; router has detected a failure

Copyright © 2018, Juniper Networks, Inc. 231

MX Series Interface Module Reference

Alarms, errors, and • SONET alarms:

events • Alarm indication signal—line (AIS-L)
• Alarm indication signal—path (AIS-P)
• Bit error rate—signal degrade (BERR-SD)
• Bit error rate—signal fail (BERR-SF)
• Bit interleaved parity (BIP) error B1, B2, B3
• Far-end bit error: remote error indication—line (REI-L), far-end line coding violations (CV-LFE)
• Far-end bit error: remote error indication—path (REI-P), far-end path coding violations
(CV-PFE)
• Loss of frame (LOF)
• Loss of pointer (LOP-P)
• Loss of signal (LOS)
• Payload label mismatch (PLM-P)
• Payload unequipped (unequipped STS at path level) (UNEQ-P)
• Remote defect indication—line (RDI-L)
• Remote defect indication—path (RDI-P)

• SDH alarms:
• Administrative unit alarm indication signal (AU-AIS)
• Bit error rate signal degrade (BERR-SD)
• Bit error rate signal fail (BERR-SF)
• Bit interleaved parity (BIP) error B1, B2, B3
• Higher order path—payload label mismatch (HP-PLM)
• Higher order path—loss of pointer (HP-LOP)
• Higher order path—remote defect indication (HP-RDI)
• Higher order path—unequipped (HP-UNEQ)
• Loss of frame (LOF)
• Loss of signal (LOS)
• Multiplex section—alarm indication signal (MS-AIS)
• Multiplex section—remote defect indication (MS-RDI)
• Multiplex section—remote error indication (MS-REI)

• Error detection:

• Errored seconds (ES-S, ES-L, ES-P)

• Far-end errored seconds (ES-LFE, ES-PFE)
• Far-end severely errored seconds (SES-LFE, SES-PFE)
• Far-end unavailable seconds (UAS-LFE, UAS-PFE)
• Severely errored frames (SEF)
• Severely errored framing seconds (SEFS-S)
• Severely errored seconds (SES-S, SES-L, SES-P)
• Unavailable seconds (UAS-L, UAS-P)

Related • MX Series FPC and PIC Overview on page 35

Documentation
• FPCs Supported by MX240, MX480, and MX960 Routers on page 36

• PICs Supported by MX240, MX480, and MX960 Routers on page 37

• High Availability Features on page 36

232 Copyright © 2018, Juniper Networks, Inc.

 Chapter 10: MX Series PIC Descriptions

SONET/SDH OC48/STM16 PIC with SFP

Software release • Junos 9.4 and later

Description • Four OC48 ports

• Power requirement: 0.86 A @ 48 V (41.4 W)
• Model Number: PC-4OC48-SON-SFP

Hardware features • Rate policing on input

• Rate shaping on output
• Packet buffering, Layer 2 parsing

Software features • Optical diagnostics and related alarms

• Configuration of SONET or SDH framing on a per-port basis
• SONET/SDH framing
• Link aggregation
• Alarm and event counting and detection
• Dual-router automatic protection switching (APS)
• Multiprotocol Label Switching (MPLS) fast reroute
• Encapsulations:
• High-Level Data Link Control (HDLC)
• Frame Relay
• Circuit cross-connect (CCC)
• Translational cross-connect (TCC)
• Point-to-Point Protocol (PPP)

Copyright © 2018, Juniper Networks, Inc. 233

MX Series Interface Module Reference

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

NOTE: To extend the life of the laser, when a PIC is not being actively used with any valid links,
take the PIC offline until you are ready to establish a link to another device. For information about
taking a PIC offline, see the request chassis pic offline command in the CLI Explorer.

LEDs One tricolor per port:

• Off—Not enabled
• Green—Online with no alarms or failures
• Yellow—Online with alarms for remote failures
• Red—Active with a local alarm; router has detected a failure

234 Copyright © 2018, Juniper Networks, Inc.

 Chapter 10: MX Series PIC Descriptions

Alarms, errors, and • SONET alarms:

events
• Alarm indication signal—line (AIS-L)
• Alarm indication signal—path (AIS-P)
• Bit error rate—signal degrade (BERR-SD)
• Bit error rate—signal fail (BERR-SF)
• Bit interleaved parity (BIP) error B1, B2, B3
• Far-end bit error: remote error indication—line (REI-L), far-end line coding violations (CV-LFE)
• Far-end bit error: remote error indication—path (REI-P), far-end path coding violations
(CV-PFE)
• Loss of frame (LOF)
• Loss of pointer (LOP-P)
• Loss of signal (LOS)
• Payload label mismatch (PLM-P)
• Payload unequipped (unequipped STS at path level) (UNEQ-P)
• Remote defect indication—line (RDI-L)
• Remote defect indication—path (RDI-P)

• SDH alarms:

• Administrative unit alarm indication signal (AU-AIS)

• Bit error rate signal degrade (BERR-SD)
• Bit error rate signal fail (BERR-SF)
• Bit interleaved parity (BIP) error B1, B2, B3
• Higher order path—payload label mismatch (HP-PLM)
• Higher order path—loss of pointer (HP-LOP)
• Higher order path—remote defect indication (HP-RDI)
• Higher order path—unequipped (HP-UNEQ)
• Loss of frame (LOF)
• Loss of signal (LOS)
• Multiplex section—alarm indication signal (MS-AIS)
• Multiplex section—remote defect indication (MS-RDI)
• Multiplex section—remote error indication (MS-REI)

• Error detection:

• Errored seconds (ES-S, ES-L, ES-P)

• Far-end errored seconds (ES-LFE, ES-PFE)
• Far-end severely errored seconds (SES-LFE, SES-PFE)
• Far-end unavailable seconds (UAS-LFE, UAS-PFE)
• Severely errored framing (SEF)
• Severely errored framing seconds (SEFS-S)
• Severely errored seconds (SES-S, SES-L, SES-P)
• Unavailable seconds (UAS-L, UAS-P)

Related • MX Series FPC and PIC Overview on page 35

Documentation
• FPCs Supported by MX240, MX480, and MX960 Routers on page 36

• PICs Supported by MX240, MX480, and MX960 Routers on page 37

Copyright © 2018, Juniper Networks, Inc. 235

MX Series Interface Module Reference

• High Availability Features on page 36

SONET/SDH OC192c/STM64 PIC

Software release • Junos 9.4 and later

Description • One OC192 port

• Power requirement: 0.45 A @ 48 V (21.6 W)
• Model Number: PC-1OC192-SON-VSR

Hardware features • Multiplexing and demultiplexing

• Rate policing on input
• Rate shaping on output
• Packet buffering, Layer 2 parsing

Software features • SONET/SDH framing

• Link aggregation
• Alarm and event counting and detection
• Dual-router automatic protection switching (APS)
• Multiprotocol Label Switching (MPLS) fast reroute
• Encapsulations:
• High-Level Data Link Control (HDLC)
• Frame Relay
• Circuit cross-connect (CCC)
• Translational cross-connect (TCC)
• Point-to-Point Protocol (PPP)

236 Copyright © 2018, Juniper Networks, Inc.

 Chapter 10: MX Series PIC Descriptions

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

• Very short reach (VSR 1): 12-ribbon multimode fiber with MTP connector (Rx and Tx)
• Fiber-optic 10-gigabit small form-factor pluggable (XFP) transceivers: 10GBASE-S very short
reach (VSR-1) (model number: XFP-10G-S)

NOTE: To extend the life of the laser, when a PIC is not being actively used with any valid links,
take the PIC offline until you are ready to establish a link to another device. For information about
taking a PIC offline, see the request chassis pic offline command in the CLI Explorer.

LEDs One tricolor LED per port:

• Off—Not enabled
• Green—Online with no alarms or failures
• Yellow—Online with alarms for remote failures
• Red—Active with a local alarm; router has detected a failure

Copyright © 2018, Juniper Networks, Inc. 237

MX Series Interface Module Reference

Alarms, errors, and • SONET alarms:

events
• Alarm indication signal—line (AIS-L)
• Alarm indication signal—path (AIS-P)
• Bit error rate—signal degrade (BERR-SD)
• Bit error rate—signal fail (BERR-SF)
• Bit interleaved parity (BIP) error B1, B2, B3
• Far-end bit error: remote error indication—line (REI-L), far-end line coding violations (CV-LFE)
• Far-end bit error: remote error indication—path (REI-P), far-end path coding violations
(CV-PFE)
• Loss of frame (LOF)
• Loss of pointer (LOP-P)
• Loss of signal (LOS)
• Payload label mismatch (PLM-P)
• Payload unequipped (unequipped STS at path level) (UNEQ-P)
• Remote defect indication—line (RDI-L)
• Remote defect indication—path (RDI-P)

• SDH alarms:

• Administrative unit alarm indication signal (AU-AIS)

• Bit error rate signal degrade (BERR-SD)
• Bit error rate signal fail (BERR-SF)
• Bit interleaved parity (BIP) error B1, B2, B3
• Higher order path—payload label mismatch (HP-PLM)
• Higher order path—loss of pointer (HP-LOP)
• Higher order path—remote defect indication (HP-RDI)
• Higher order path—unequipped (HP-UNEQ)
• Loss of frame (LOF)
• Loss of signal (LOS)
• Multiplex section—alarm indication signal (MS-AIS)
• Multiplex section—remote defect indication (MS-RDI)
• Multiplex section—remote error indication (MS-REI)

• Error detection:

• Errored seconds (ES-S, ES-L, ES-P)

• Far-end errored seconds (ES-LFE, ES-PFE)
• Far-end severely errored seconds (SES-LFE, SES-PFE)
• Far-end unavailable seconds (UAS-LFE, UAS-PFE)
• Severely errored framing (SEF)
• Severely errored framing seconds (SEFS-S)
• Severely errored seconds (SES-S, SES-L, SES-P)
• Unavailable seconds (UAS-L, UAS-P)

Related • MX Series FPC and PIC Overview on page 35

Documentation
• FPCs Supported by MX240, MX480, and MX960 Routers on page 36

• PICs Supported by MX240, MX480, and MX960 Routers on page 37

238 Copyright © 2018, Juniper Networks, Inc.

 Chapter 10: MX Series PIC Descriptions

• High Availability Features on page 36

SONET/SDH OC192c/STM64 PIC with XFP

Software release • Junos 9.4 and later

Description • One OC192 port

• Power requirement: 0.52A @ 48 V (25 W)
• Model number: PB-1OC192-SON-XFP

Hardware features • Multiplexing and demultiplexing

• Rate policing on input
• Rate shaping on output
• Packet buffering, Layer 2 parsing

Software features • SONET/SDH framing

• Link aggregation
• Alarm and event counting and detection
• Dual-router automatic protection switching (APS)
• Multiprotocol Label Switching (MPLS) fast reroute
• Encapsulations:
• Circuit cross-connect (CCC)
• Translational cross-connect (TCC)
• Frame Relay
• High-Level Data Link Control (HDLC)
• Point-to-Point Protocol (PPP)

Copyright © 2018, Juniper Networks, Inc. 239

MX Series Interface Module Reference

Cables and connectors TIP: You can use the Hardware Compatibility Tool to find information about the pluggable
transceivers supported on your Juniper Networks device.

The list of supported transceivers for the MX Series is located at

https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.

NOTE: To extend the life of the laser, when a PIC is not being actively used with any valid links,
take the PIC offline until you are ready to establish a link to another device. For information about
taking a PIC offline, see the request chassis pic offline command in the CLI Explorer.

LEDs One tricolor LED per port:

• Off—Not enabled
• Green—Online with no alarms or failures
• Yellow—Online with alarms for remote failures
• Red—Active with a local alarm; router has detected a failure

240 Copyright © 2018, Juniper Networks, Inc.

 Chapter 10: MX Series PIC Descriptions

Alarms, errors, and • SONET alarms:

events
• Alarm indication signal—line (AIS-L)
• Alarm indication signal—path (AIS-P)
• Bit error rate—signal degrade (BERR-SD)
• Bit error rate—signal fail (BERR-SF)
• Bit interleaved parity (BIP) error B1, B2, B3
• Far-end bit error: remote error indication—line (REI-L), far-end line coding violations (CV-LFE)
• Far-end bit error: remote error indication—path (REI-P), far-end path coding violations
(CV-PFE)
• Loss of frame (LOF)
• Loss of pointer (LOP-P)
• Loss of signal (LOS)
• Payload label mismatch (PLM-P)
• Payload unequipped (unequipped STS at path level) (UNEQ-P)
• Remote defect indication—line (RDI-L)
• Remote defect indication—path (RDI-P)

• SDH alarms:

• Administrative unit alarm indication signal (AU-AIS)

• Bit error rate signal degrade (BERR-SD)
• Bit error rate signal fail (BERR-SF)
• Bit interleaved parity (BIP) error B1, B2, B3
• Higher order path—payload label mismatch (HP-PLM)
• Higher order path—loss of pointer (HP-LOP)
• Higher order path—remote defect indication (HP-RDI)
• Higher order path—unequipped (HP-UNEQ)
• Loss of frame (LOF)
• Loss of signal (LOS)
• Multiplex section—alarm indication signal (MS-AIS)
• Multiplex section—remote defect indication (MS-RDI)
• Multiplex section—remote error indication (MS-REI)

• Error detection:

• Errored seconds (ES-S, ES-L, ES-P)

• Far-end errored seconds (ES-LFE, ES-PFE)
• Far-end severely errored seconds (SES-LFE, SES-PFE)
• Far-end unavailable seconds (UAS-LFE, UAS-PFE)
• Severely errored framing (SEF)
• Severely errored framing seconds (SEFS-S)
• Severely errored seconds (SES-S, SES-L, SES-P)
• Unavailable seconds (UAS-L, UAS-P)

Related • MX Series FPC and PIC Overview on page 35

Documentation
• FPCs Supported by MX240, MX480, and MX960 Routers on page 36

• PICs Supported by MX240, MX480, and MX960 Routers on page 37

Copyright © 2018, Juniper Networks, Inc. 241

MX Series Interface Module Reference

• High Availability Features on page 36

242 Copyright © 2018, Juniper Networks, Inc.

PART 3

SFB, SCB, ADC, and CB-RE Descriptions

• SFB and SFB2 Descriptions on page 245
• SCBs, SCBEs, and SCBE2 Descriptions on page 251
• ADC Descriptions on page 271
• RE, CB-RE, and RCB Descriptions on page 275

Copyright © 2018, Juniper Networks, Inc. 243

MX Series Interface Module Reference

244 Copyright © 2018, Juniper Networks, Inc.

CHAPTER 11

SFB and SFB2 Descriptions

• MX2000 Switch Fabric Board (SFB) on page 245

• MX2000 Enhanced Switch Fabric Board (SFB2) on page 248

MX2000 Switch Fabric Board (SFB)

Switch Fabric Boards (SFBs) are the data plane for the subsystems in the MX router
chassis. Switch Fabric Boards (SFBs) create a highly scalable and resilient “all-active”
centralized switch fabric that delivers up to 2 Tbps of full-duplex switching capacity to
each MPC slot in an MX2000 router.

The SFB and Enhanced Switch Fabric Board (SFB2) are the same except that the SFB
has three XF fabric chips per card whereas the SFB2 has two PF fabric chips per card.

Figure 43: Switch Fabric Board

OK/FAIL
g007029

Name in CLI Switch Fabric Board

Copyright © 2018, Juniper Networks, Inc. 245

MX Series Interface Module Reference

Description The MX2000 Switch Fabric Board (SFB; model number: MX2000-SFB-S) provides increased
fabric bandwidth per slot. The MX2000 line of routers can support eight Switch Fabric Boards
(SFB) and eight Enhanced Switch Fabric Boards (SFB2) but not both at the same time. The
MX2000-SFB-S is supported on MX2010 and MX2020 routers. Refer to Figure 43 on page 245.

NOTE: If you decide to upgrade from an SFB to an SFB2, the MX2000 line of routers support both
the SFB and SFB2 at the same time for the duration of the upgrade.

Features and • Powers the device on and off

Components • PCIe control of three XF ASICs
• I2C bus logic interface, used for component management and monitoring of temperature, and
voltage
• Switch fabric—Provides switching functions for the MPCs
• Fabric capacity—Supports 750-Gbps per slot with eight SFBs, and 860-Gbps per slot with
seven SFBs.
• Front panel components—Service ports, system LEDs, and operational buttons

SFB Slots You can install up to eight SFBs in the MX2000 router. The SFBs install vertically into the front
of the chassis in the slots labeled 0 through 7. If any slots are empty, you must install a blank
panel.

CAUTION: If one of the SFBs fails, do not remove the failed SFB until you have a replacement or
blank panel to install.

CAUTION: A blank panel cannot be installed in slot 0. Slot 0 should always have a functioning
SFB. If the slot 0 SFB fails, you must replace it with a functioning SFB from another slot, and then
put a blank panel in place of the SFB that is used to replace the slot 0 SFB.

SFB Redundancy Seven of eight SFBs are required for line rate operation. The system can continue operating with
fewer than seven SFBs, but forwarding performance will be impacted.

Weight and Dimensions • Weight: 12 lb (5.44 kg)

• Width: 1.7 in. (4.31 cm)
• Depth: 23.6 in. (59.94 cm). With ejector handle: 26.14 in. (66.39 cm)
• Height: 16.225 in. (41.21 cm)

Maximum Power MX2020:

Requirements (without
MICs) • Typical: 250 W
• At different temperatures:
295 W at 55° C
280 W at 40° C
270 W at 25° C

MX2010:

• Typical: 220 W
• At different temperatures:
265 W at 55° C
250 W at 40° C
240 W at 25° C

246 Copyright © 2018, Juniper Networks, Inc.

 Chapter 11: SFB and SFB2 Descriptions

LEDs OK/FAIL LED, one bicolor:

• Steady green—SFB is online and functioning normally.

• Slow blinking green—SFB is initializing.
• Fast blinking green—SFB is being identified by software.

NOTE: This is used to guide the operator to correct any action needed on the SFB.

• Red—SFB has failed.

• Off—SFB is offline.

Each SFB also has a set of bicolor LEDs on the craft interface that indicate its status. The SFB
LEDs, labeled 0 through 7, are located along the bottom center of the craft interface. For more
information about the SFB LED on the craft interface, see MX2000 Switch Fabric Board LED.

Related • MX2000 Host Subsystem CB-RE Description on page 275

Documentation
• MX2000 Switch Fabric Board LED

• Replacing an MX2000 SFB

• Installing an MX2000 SFB

• Removing an MX2000 SFB

• Replacing an MX2000 SFB

• Performing a Smooth Upgrade to Enhanced Switch Fabric Board (SFB2) with Minimal
Impact on Traffic

• MX2000 Enhanced Switch Fabric Board (SFB2) on page 248

Copyright © 2018, Juniper Networks, Inc. 247

MX Series Interface Module Reference

MX2000 Enhanced Switch Fabric Board (SFB2)

The MX2000 Switch Fabric Board (SFB) straddles the two backplanes. It has connectors
connecting to both backplanes, (see Figure 43 on page 245). The SFB and SFB2 are exactly
the same except that the SFB2 has two PF fabric chips per card whereas SFB has three
XF fabric chips per card.

Figure 44: Enhanced Switch Fabric Board

OK/FAIL

g007029

Software release • Junos OS Release 11.4 and later

• Name in CLI: Switch Fabric Board

Description The MX2000 Enhanced Switch Fabric Board (SFB2; model number: MX2000-SFB2-S) provides
increased fabric bandwidth per slot. MX2000 line of routers can support eight Switch Fabric
Boards (SFB) and eight Enhanced Switch Fabric Boards (SFB2) but not both at the same time.
The SFB2 is supported on MX2010 and MX2020 routers. Refer to Figure 43 on page 245.

NOTE: During an upgrade from SFB to SFB2, the MX2000 line of routers support both SFB and
SFB2 at the same time for the duration of the upgrade.

SFB2 Features and • PCIe control of two PF ASICs

Components • I2C bus logic interface, used for component management and monitoring of temperature, and
voltage
• Switch fabric—Provides switching functions for the MPCs
• Fabric capacity—Supports 2 Tbps per slot with eight SFB2 and 1.7 Tbps per slot with seven
SFB2
• Circuits for chassis management and control
• Power circuits for the SFB2
• LED—Provides status of the SFB2

248 Copyright © 2018, Juniper Networks, Inc.

 Chapter 11: SFB and SFB2 Descriptions

SFB2 Slots You can install up to eight SFB2s in the MX2000 router. The SFB2s install vertically into the front
of the chassis in the slots labeled 0 through 7. If any slots are empty, you must install a blank
panel.

CAUTION: If one of the SFB2s fails, do not remove the failed SFB2 until you have a replacement
or blank panel to install.

SFB2 Redundancy Seven of eight SFB2s are required for line rate operation. The system can continue operating with
fewer than seven SFB2s, but forwarding performance will be impacted.

Weight and Dimensions • Weight: 16 lb (7.2 kg)

• Width: 1.7 in. (4.31 cm)
• Depth: 23.6 in. (59.94 cm). With ejector handle: 26.14 in. (66.39 cm)
• Height: 16.225 in. (41.21 cm)

Maximum Power MX2020:

Requirements (without
MICs) • Typical: 250 W
• At different temperatures:
295 W at 55° C
280 W at 40° C
270 W at 25° C

MX2010:

• Typical: 220 W
• At different temperatures:
265 W at 55° C
250 W at 40° C
240 W at 25° C

LEDs OK/FAIL LED, one bicolor:

• Steady green—SFB2 is online and functioning normally.

• Slow blinking green—SFB2 is initializing.
• Fast blinking green—SFB2 is being identified by software.

NOTE: This is used to guide the operator to correct any action needed on the SFB2.

• Red—SFB2 has failed.

• Off—SFB2 is offline.

Each SFB2 also has a set of bicolor LEDs on the craft interface that indicate its status. The SFB2
LEDs, labeled 0 through 7, are located along the bottom center of the craft interface. For more
information about the SFB2 LED on the craft interface, see MX2000 Switch Fabric Board LED

Related • MX2000 Switch Fabric Board LED

Documentation
• MX2000 Host Subsystem CB-RE Description on page 275

• Replacing an MX2000 SFB

• Understanding Fabric Fault Handling on Enhanced Switch Fabric Board (SFB2)

Copyright © 2018, Juniper Networks, Inc. 249

MX Series Interface Module Reference

• Performing a Smooth Upgrade to Enhanced Switch Fabric Board (SFB2) with Minimal
Impact on Traffic

250 Copyright © 2018, Juniper Networks, Inc.

CHAPTER 12

SCBs, SCBEs, and SCBE2 Descriptions

• MX-Series Switch Control Board (SCB) Overview on page 252

• SCBE2-MX Description on page 253
• MX SCBE Description on page 257
• MX480 SCBE Description on page 259
• MX240 SCBE Description on page 261
• MX960 SCB Description on page 263
• MX480 SCB Description on page 266
• MX240 SCB Description on page 267

Copyright © 2018, Juniper Networks, Inc. 251

MX Series Interface Module Reference

MX-Series Switch Control Board (SCB) Overview

MX Switch Control Boards (MX-SCB, MX-SCBE, MX-SCBE2) provide full line-rate

performance and redundancy without a loss of bandwidth. MX-series SCBs feature an
integrated switch fabric that connects to all slots in the chassis in a nonblocking
architecture. The SCBs house the Routing Engine (RE), control power to MPCs, monitor
and control system functions such as fan speed and the system front panel, and manage
clocking, resets, and boots. The SCB is a single-slot card and has a carrier for the routing
engine on the front.

The SCB is the first-generation SCB and was designed to work with the first-generation
DPC line cards. The MX-SCBE was designed specifically for use with the MPC3e line
cards. The MX SCBE2 provides improved fabric performance for high-capacity line cards
using the third generation fabric XF2 chip (MPC4e, MPC5e, MPC2/3 NG, and MPC7e).

Table 28 on page 252 compares the capacities of the MX-Series SCBs and lists the
supported REs.

Table 28: Switch Control Board Capacities and Supported REs

Model Number Description Switch Fabric Capacity Supported Routing Engines

SCBE2- MX-BB Enhanced MX Switch Control Board 10.56 Tbps (half-duplex) RE-S-1800
(SCBE2)
RE-S-X6

SCBE-MX-BB Enhanced Switch Control Board 5.12Tbps RE-S-1300

(SCBE)
RE-S-1800

SCB-MX-BB Switch Control Board (SCB) 2.64 Tbps RE-S-1300

RE-S-1800

SCBs install vertically in the MX2020, MX2010, and MX960 chassis, and horizontally in
the MX480 and MX240 chassis. The number of supported SCBs varies per router:

• MX240 and MX480 routers—2 SCBs for 1 + 1 MX SCB redundancy when used with the
DPC line cards

• MX960 router—3 SCBs for 2 + 1 redundancy when used with the DPC line cards

• MX2010 and MX2020 routers—8 switch fabrics/planes

252 Copyright © 2018, Juniper Networks, Inc.

 Chapter 12: SCBs, SCBEs, and SCBE2 Descriptions

CLI Identification
The SCBs are identified in the CLI as SCB, SCBE, and SCBE2.

user@host> show chassis hardware | match SCB

Item Version Part Number Serial Number Description
CB0 REV 07 710-021523 ABBC8281 MX SCB
CB1 REV 07 710-021523 ABBC8323 MX SCB
CB2 REV 07 710-021523 ABBD1410 MX SCB

user@host> show chassis hardware models | match SCBE

Item Version Part Number Serial Number Description
CB0 REV 02 750-031391 YE8505 Enhanced MX SCB
CB1 REV 07 710-031391 YL6769 Enhanced MX SCB
CB2 REV 07 710-031391 YE8492 Enhanced MX SCB

user@host> show chassis hardware models | match SCBE2

Item Version Part Number Serial Number Description
CB0 REV 01 750-062572 CAGN2123 SCBE2-MX-S
CB1 REV 07 750-062572 CAGN2456 SCBE2-MX-S
CB2 REV 07 750-062572 CAGN2789 SCBE2-MX-S

Related • SCBE2-MX Description on page 253

Documentation
• MX SCBE Description on page 257

SCBE2-MX Description

The SCBE2-MX features the third-generation fabric on the MX960, MX480, and MX240
routers. It uses the XF2 ASIC fabric chip, providing support for higher interface density
(slot and capacity scale) as well as improved services. The SCBE2-MX was released with
Junos release 13.3R1.

The SCBE2-MX is installed vertically in the MX960 chassis and horizontally in the MX480
and MX240 chassis. The routing engine is installed directly into a slot on the SCBE2-MX
(see Figure 45 on page 254).

Copyright © 2018, Juniper Networks, Inc. 253

MX Series Interface Module Reference

Figure 45: SCBE2-MX

Software release • Junos OS Release 13.3 R1 and later

• Name in CLI: SCBE2

Requirements For proper cooling, you must install MX-series high-capacity fan trays in the MX chassis.
Additionally, for the MX960, you must install a high-capacity filter tray.

SCBE2-MX Features • Provides improved fabric performance for high-capacity line cards using the third generation
fabric XF2 chip.
• Provides bandwidth of up to 340 Gbps per slot with redundant fabric support and 480 Gbps
per slot without redundant fabric support.
• Provides a central clocking module and a centralized clocking architecture that supports clock
cleanup and distribution. The Stratum 3 clock module performs clock monitoring, filtering, and
holdover at a centralized chassis location.
• Supports dynamic multicast replication.
• Supports GRES.
• Supports MPC line cards. Does not support DPCs.
• Allows you to configure the system such that one SCBE2-MX supports a GPS interface, and
the other SCBE2-MX supports a BITS interface.
• Provides support for cross-coupling of clock input. This requires an enhanced midplane:
• MX960—CHAS-BP3-MX960-S
• MX480—CHAS-BP3-MX480-S
• MX240—CHAS-BP3-MX240-S

254 Copyright © 2018, Juniper Networks, Inc.

 Chapter 12: SCBs, SCBEs, and SCBE2 Descriptions

SCBE2-MX Components • Control Board and Routing Engine (CB-RE) mastership mechanism.
• External clock interface—Allows BITS or GPS clock source input to the centralized timing circuit,
or allows centralized timing to be output to BITS or GPS.
• Switch fabric—Provides switching functions for MPCs.
• 1000Base-T Ethernet controller—Provides a 1-Gbps Ethernet link between the Routing Engines.
• Power circuits for the Routing Engine and the SCBE2-MX.
• LEDs—Provide status of the SCBE2-MX and the clocking interface.

SCBE2-MX Slots For the MX960:

• You can install up to three SCBE2-MX’s in the MX960 router chassis.

• SCBE2-MX’s are installed vertically into the front of the MX960 chassis in the slots labeled 0,
1, and 2. If any slots are empty, you must install a blank panel.
• The two SCBE2-MX’s residing in slot 6 and slot 7 of the MX960 chassis provide both control
and switch fabric features, while the third SCBE2-MX residing in slot 8 of the chassis (hybrid
slot) will only do fabric functions.

For the MX480 and MX240 routers:

• You can install either one or two SCBE2-MX’s in the MX480 and MX240 router chassis.
SCBE2-MX’s are installed horizontally into the front of the MX480 and MX240 chassis in the
slots labeled 0 and 1. If any slots are empty, you must install a blank panel.

SCBE2-MX Fabric For the MX960:

Planes and Redundancy
• Each SCBE2-MX provides two switch fabric planes for packet forwarding among the MPCs in
the MX960.
• The MX960 chassis may contain up to three SCBE2-MX's Therefore, six fabric planes are
available.
• Three SCBE2-MX’s are required for 2 + 1 redundancy.
• In redundant fabric mode, four fabric planes from the first two SCBE2-MX’s will be in Active
mode, and two fabric planes from the third SCBE2-MX will be in Spare mode.
• In an increased fabric bandwidth mode, all six fabric planes will be in Active mode.

For the MX240 and MX480 routers:

• Each SCBE2-MX provides four switch fabric planes for packet forwarding among the MPCs in
the MX480 and MX240 chassis.
• The MX480 and MX240 routers contain a maximum of two SCBE2-MX’s. Therefore, eight
logical planes are available.
• Two SCBE2-MX’s are required for 1 + 1 redundancy.
• In redundant fabric mode, four fabric planes from the first SCBE2-MX will be in Active mode,
and four fabric planes from the second SCBE2-MX will be in Spare mode.
• In an increased fabric bandwidth mode, all eight fabric planes will be in Active mode.
• Each fabric ASIC is configured in virtual plane mode, where two virtual planes exist on one
fabric ASIC.

Weight and Dimensions • Weight: 9.6 lb (4.4 kg) (with Routing Engine installed)
• Width: 17 in (43.2 cm)
• Depth: 22 in (55.9 cm)
• Height: 1.25 in (3.2 cm) height.

Copyright © 2018, Juniper Networks, Inc. 255

MX Series Interface Module Reference

Maximum Power SCBE2-MX (applies to MX240, MX480, and MX960)

Requirements
185 W at 55° C

160 W at 40° C

155 W at 25° C

LEDs • FABRIC ACTIVE, FABRIC ONLY, and OK/FAIL LEDs indicate the status of the SCBE2-MX.
• The BITS, GPS, and UTI LEDs, located next to the EXT CLK port, indicate the status of the
respective clocking interface.
• The LINK LED located next to the two Ethernet ports, indicate the status of the respective SFP+
interface.

For more information about the SCBE2-MX LEDs, see SCBE2-MX LEDs.

SCBE2 Interoperability with Existing Hardware

SCBE2 Operating Mode MX240/480/960 Supported

Mixed Mode Allowed DPC/MS-DPC No

(DPC+MPC in a chassis)
MS-MPC Yes

MPC1 Yes

MPC2 Yes

MPC3 Yes

MPC4 Yes

MPC2-NG Yes

MPC3-NG Yes

16x10GE MPC Yes

Enhanced IP/Enhanced MPC5 Yes

Ethernet Mode Only
MPC6 No

MPC7 (480 Gbps) Yes

MPC8 (960 Gbps) No

MPC9 (1.6 Tbps) No

256 Copyright © 2018, Juniper Networks, Inc.

 Chapter 12: SCBs, SCBEs, and SCBE2 Descriptions

SCBE2 Operating Mode MX240/480/960 Supported

Routing Engines RE-S-1300(EOLed) yes

RE-S-2000 (EOLed) yes

RE-S-1800 yes

RE-S-X6-64G yes

Related • MX-Series Switch Control Board (SCB) Overview on page 252

Documentation
• SCBE2-MX LEDs

MX SCBE Description

The MX SCBE serves the carrier Ethernet services router and carrier Ethernet transport
markets that require higher-capacity traffic support demanding greater interface density
(slot and capacity scale), as well as improved services. The upgraded SCB is supported
on MX960, MX480, and MX240 routers. Some key attributes of the MX SCBE are:

• 160 Gbps/slot bandwidth with redundant fabric support, and improved fabric
performance by using the next-generation fabric (XF) chip

• A central clocking module and a centralized clocking architecture that supports clock
cleanup and distribution. The Stratum 3 clock module performs clock monitoring,
filtering, and holdover in a centralized chassis location

• Full performance with fabric redundancy for higher capacity line cards such as 16x10GE
and MPC3

The Routing Engine installs directly into a slot on the MX SCBE (see Figure 46 on page 258).

Copyright © 2018, Juniper Networks, Inc. 257

MX Series Interface Module Reference

Figure 46: MX SCBE

SCBE-MX

g006589

MX SCBE Slots
You can install up to three MX SCBEs. The MX SCBEs install vertically into the front of
the chassis in the slots labeled 0, 1, and 2. If any slots are empty, you must install a blank
panel.

MX SCBE Redundancy
If three MX SCBEs are installed, the third MX SCBE functions as the backup.

MX SCBE Components
Each MX SCBE consists of the following components:

• I2C bus logic, used for low-level communication with each component

• Component redundancy circuitry

• Control Board/Routing Engine mastership mechanism

• Gigabit Ethernet switch that is connected to the embedded CPU complex on all
components

• External clock interface—Allows BITS or GPS clock source input to the centralized
timing circuit, or allows centralized timing to be output to BITS or GPS

258 Copyright © 2018, Juniper Networks, Inc.

 Chapter 12: SCBs, SCBEs, and SCBE2 Descriptions

• Switch fabric—Provides the switching functions for the DPCs, FPCs, and MPCs

• Control field-programmable gate array (FPGA)—Provides the Peripheral Component

Interconnect (PCI) interface to the Routing Engine

• 1000Base-T Ethernet controller—Provides a 1-Gbps Ethernet link between the Routing

Engines

• Circuits for chassis management and control

• Power circuits for the Routing Engine and SCBE

• LEDs—Provide status of the SCBE and clocking interface

Supported Routing Engines and MPCs for the SCBE

Supported Routing Engines Supported MPCs

RE-S-1300 MPC3e

RE-S-1800 MPC3e

RE-S-2000 MPC3e

Related • MX960 SCB Description on page 263

Documentation
• MX960 SCBE LEDs

• Upgrading an MX960 SCB to SCBE

MX480 SCBE Description

The MX SCBE serves the carrier Ethernet services router and carrier Ethernet transport
markets that require higher-capacity traffic support demanding greater interface density
(slot and capacity scale), as well as improved services. The upgraded SCB is supported
on MX960, MX480, and MX240 routers. Some key attributes of the MX SCBEs are:

• 160 Gbps/slot bandwidth with redundant fabric support, and improved fabric
performance by using the next-generation fabric (XF) chip

• A central clocking module and a centralized clocking architecture that supports clock
cleanup and distribution. The Stratum 3 clock module performs clock monitoring,
filtering, and holdover in a centralized chassis location

• Full performance with fabric redundancy for higher capacity line cards such as 16x10GE
and MPC3

The Routing Engine installs directly into a slot on the MX SCBE (see Figure 47 on page 260).

Copyright © 2018, Juniper Networks, Inc. 259

MX Series Interface Module Reference

Figure 47: MX SCBE

SCBE-MX

g006589

MX SCBE Slots
You can install one or two MX SCBEs. The MX SCBEs install horizontally into the front
of the chassis in the slots labeled 0 and 1. If any slots are empty, you must install a blank
panel.

MX SCBE Redundancy
If two MX SCBEs are installed, one MX SCBE functions as the master MX SCBE and the
other as its backup. If the master fails or is removed, the backup restarts and becomes
the master.

MX SCBE Components
Each MX SCBE consists of the following components:

• I2C bus logic, used for low-level communication with each component

• Component redundancy circuitry

• Control Board/Routing Engine mastership mechanism

• Gigabit Ethernet switch that is connected to the embedded CPU complex on all
components

260 Copyright © 2018, Juniper Networks, Inc.

 Chapter 12: SCBs, SCBEs, and SCBE2 Descriptions

• External clock interface—Allows BITS or GPS clock source input to the centralized
timing circuit, or allows centralized timing to be output to BITS or GPS

• Switch fabric—Provides the switching functions for the DPCs, FPCs, and MPCs

• Control field-programmable gate array (FPGA)—Provides the Peripheral Component

Interconnect (PCI) interface to the Routing Engine

• 1000Base-T Ethernet controller—Provides a 1-Gbps Ethernet link between the Routing

Engines

• Circuits for chassis management and control

• Power circuits for the Routing Engine and SCBE

• LEDs—Provide status of the SCBE and clocking interface

Related • MX480 SCB Description on page 266

Documentation
• MX480 SCBE LEDs

• Upgrading an MX480 SCB

MX240 SCBE Description

The MX SCBE serves the carrier Ethernet services router and carrier Ethernet transport
markets that require higher-capacity traffic support demanding greater interface density
(slot and capacity scale), as well as improved services. The upgraded SCB is supported
on MX960, MX480, and MX240 routers. Some key attributes of the MX SCBs are:

• 160 Gbps/slot bandwidth with redundant fabric support, and improved fabric
performance by using the next-generation fabric (XF) chip

• A central clocking module and a centralized clocking architecture that supports clock
cleanup and distribution. The Stratum 3 clock module performs clock monitoring,
filtering, and holdover in a centralized chassis location

• Full performance with fabric redundancy for higher capacity line cards such as 16x10GE
and MPC3

The Routing Engine installs directly into a slot on the MX SCBE (see Figure 48 on page 262).

Copyright © 2018, Juniper Networks, Inc. 261

MX Series Interface Module Reference

Figure 48: MX SCBE

SCBE-MX

g006589

MX SCBE Slots
You can install one or two MX SCBEs. The MX SCBEs install horizontally into the front
of the chassis in the slots labeled 0 and 1. If any slots are empty, you must install a blank
panel.

MX SCBE Redundancy
If two MX SCBEs are installed, one MX SCBE functions as the master MX SCBE and the
other as its backup. If the master fails or is removed, the backup restarts and becomes
the master.

MX SCBE Components
Each MX SCBE consists of the following components:

• I2C bus logic, used for low-level communication with each component

• Component redundancy circuitry

• Control Board/Routing Engine mastership mechanism

• Gigabit Ethernet switch that is connected to the embedded CPU complex on all
components

262 Copyright © 2018, Juniper Networks, Inc.

 Chapter 12: SCBs, SCBEs, and SCBE2 Descriptions

• External clock interface—Allows BITS or GPS clock source input to the centralized
timing circuit, or allows centralized timing to be output to BITS or GPS

• Switch fabric—Provides the switching functions for the DPCs, FPCs, and MPCs

• Control field-programmable gate array (FPGA)—Provides the Peripheral Component

Interconnect (PCI) interface to the Routing Engine

• 1000Base-T Ethernet controller—Provides a 1-Gbps Ethernet link between the Routing

Engines

• Circuits for chassis management and control

• Power circuits for the Routing Engine and SCBE

• LEDs—Provide status of the SCBE and clocking interface

Related • MX240 SCB Description on page 267

Documentation
• MX240 SCBE LEDs

• Upgrading an MX240 SCB

MX960 SCB Description

The SCB provides the following functions:

• Powers on and powers off DPCs, FPCs, and MPCs

• Controls clocking, system resets, and booting

• Monitors and controls system functions, including fan speed, board power status, PDM
status and control, and the craft interface

• Provides interconnections to all the DPCs, FPCs, and MPCs within the chassis through
the switch fabrics integrated into the SCB

The Routing Engine installs directly into a slot on the SCB (see Figure 49 on page 264).

Copyright © 2018, Juniper Networks, Inc. 263

MX Series Interface Module Reference

Figure 49: SCB

SCB Slots
You can install up to three. The SCBs install vertically into the front of the chassis in the
slots labeled 0, 1, and 2/6. If any slots are empty, you must install a blank panel.

SCB Redundancy
SCBs installed in slots 0 and 1 provide nonredundant fabric connections. An SCB installed
in slot 2/6, in conjunction with SCBs in slots 0 and 1, provides redundant fabrics, but the
Routing Engine installed on it receives no power and provides no additional routing
functions. If no SCB is installed in slot 2/6, you must install a blank panel in the slot (see
Table 29 on page 264).

Table 29: SCB Slot Mapping and Functionality

Functionality Slot 0 Slot 1 Slot 2/6

Full fabric SCB SCB –

Routing Engine

Full fabric and redundant Routing Engine SCB SCB –

Routing Engine Routing Engine

Redundant fabric and Routing Engine SCB SCB SCB

Routing Engine Routing Engine

264 Copyright © 2018, Juniper Networks, Inc.

 Chapter 12: SCBs, SCBEs, and SCBE2 Descriptions

SCB Components
Each SCB consists of the following components:

• Chassis management Ethernet switch

• I2C bus logic, used for low-level communication with each component

• Component redundancy circuitry

• Control Board/Routing Engine mastership mechanism

• Gigabit Ethernet switch that is connected to the embedded CPU complex on all
components

• Switch fabric—Provides the switching functions for the DPCs, FPCs, and MPCs

• Control field-programmable gate array (FPGA)—Provides the Peripheral Component

Interconnect (PCI) interface to the Routing Engine

• 1000Base-T Ethernet controller—Provides a 1-Gbps Ethernet link between the Routing

Engines

• Ethernet switch—Provides 1-Gbps link speeds between the Routing Engine and the
DPCs, FPCs, and MPCs

• Circuits for chassis management and control

• Power circuits for the Routing Engine and SCB

• LEDs—Provide status

Supported Routing Engines

The SCB supports the following routing engines (REs):

• RE-S-1300 Routing Engine Description

• RE-S-2000 Routing Engine Description

• RE-S-1800 Routing Engine Description

Related • MX960 Host Subsystem Description

Documentation
• MX960 Routing Engine Description on page 276

• MX960 Switch Control Board LEDs

• Replacing an MX960 SCB

• MX-Series Switch Control Board (SCB) Overview on page 252

Copyright © 2018, Juniper Networks, Inc. 265

MX Series Interface Module Reference

MX480 SCB Description

The SCB provides the following functions:

• Powers on and powers off DPCs, FPCs, and MPCs

• Controls clocking, system resets, and booting

• Monitors and controls system functions, including fan speed, board power status, PDM
status and control, and the craft interface

• Provides interconnections to all the DPCs, FPCs, and MPCs within the chassis through
the switch fabrics integrated into the SCB

The Routing Engine installs directly into a slot on the SCB (see Figure 49 on page 264).

Figure 50: SCB

SCB Slots
You can install one or two. The SCBs install horizontally into the front of the chassis in
the slots labeled 0 and 1. If any slots are empty, you must install a blank panel.

SCB Redundancy
If two SCBs are installed, one SCB functions as the master SCB and the other as its
backup. If the master fails or is removed, the backup restarts and becomes the master.

266 Copyright © 2018, Juniper Networks, Inc.

 Chapter 12: SCBs, SCBEs, and SCBE2 Descriptions

SCB Components
Each SCB consists of the following components:

• Chassis management Ethernet switch

• I2C bus logic, used for low-level communication with each component

• Component redundancy circuitry

• Control Board/Routing Engine mastership mechanism

• Gigabit Ethernet switch that is connected to the embedded CPU complex on all
components

• Switch fabric—Provides the switching functions for the DPCs, FPCs, and MPCs

• Control field-programmable gate array (FPGA)—Provides the Peripheral Component

Interconnect (PCI) interface to the Routing Engine

• 1000Base-T Ethernet controller—Provides a 1-Gbps Ethernet link between the Routing

Engines

• Ethernet switch—Provides 1-Gbps link speeds between the Routing Engine and the
DPCs, FPCs, and MPCs

• Circuits for chassis management and control

• Power circuits for the Routing Engine and SCB

• LEDs—Provide status

Related • MX480 Host Subsystem Description

Documentation
• MX480 Routing Engine Description on page 278

• SCB-MX LEDs

MX240 SCB Description

The SCB provides the following functions:

• Powers on and powers off DPCs, FPCs, and MPCs

• Controls clocking, system resets, and booting

• Monitors and controls system functions, including fan speed, board power status, PDM
status and control, and the craft interface

• Provides interconnections to all the DPCs, FPCs, and MPCs within the chassis through
the switch fabrics integrated into the SCB

The Routing Engine installs directly into a slot on the SCB (see Figure 49 on page 264).

Copyright © 2018, Juniper Networks, Inc. 267

MX Series Interface Module Reference

Figure 51: SCB

SCB Slots
You can install one or two SCBs. The SCBs install horizontally into the front of the chassis
in the slots labeled 0 and 1/0 (the multifunction slot 1/0 can contain either SCB1, DPC0,
MPC0, or FPC0). If any slots are empty, you must install a blank panel.

SCB Redundancy
If two SCBs are installed, one SCB functions as the master SCB and the other as its
backup. If the master fails or is removed, the backup becomes the master.

SCB Components
Each SCB consists of the following components:

• Chassis management Ethernet switch

• I2C bus logic, used for low-level communication with each component

• Component redundancy circuitry

• Control Board/Routing Engine mastership mechanism

• Gigabit Ethernet switch that is connected to the embedded CPU complex on all
components

• Switch fabric—Provides the switching functions for the DPCs, FPCs, and MPCs

• Control field-programmable gate array (FPGA)—Provides the Peripheral Component

Interconnect (PCI) interface to the Routing Engine

268 Copyright © 2018, Juniper Networks, Inc.

 Chapter 12: SCBs, SCBEs, and SCBE2 Descriptions

• 1000Base-T Ethernet controller—Provides a 1-Gbps Ethernet link between the Routing

Engines

• Ethernet switch—Provides 1-Gbps link speeds between the Routing Engine and the
DPCs, FPCs, and MPCs

• Circuits for chassis management and control

• Power circuits for the Routing Engine and SCB

• LEDs—Provide status

Related • MX240 Host Subsystem Description

Documentation
• MX240 Routing Engine Description on page 280

Copyright © 2018, Juniper Networks, Inc. 269

MX Series Interface Module Reference

270 Copyright © 2018, Juniper Networks, Inc.

CHAPTER 13

ADC Descriptions

• MX2020 Adapter Card (ADC) Description on page 271

• MX2010 Adapter Card (ADC) Description on page 272

MX2020 Adapter Card (ADC) Description

The MX2020 router is compatible with all Trio-based MPC line cards; However, because
the MX2020 router uses a newer-generation Switch Fabric Board (SFB) with faster
bandwidth, line cards that were designed to work with the SCB and SCBE (MPC1E, MPC2E,
and MPC3E) must use a special Line Card Adapter (ADC). The ADC is merely a shell that
accepts MPC1E, MPC2E, and MPC3E line cards in the front and converts power and switch
fabric in the rear. The MX2020 router has 20 dedicated line card slots and can thus
support up to 20 ADCs and 20 MPC1E through MPC3E line cards.

The dedicated line cards slots in the MX2020 router are numbered 0 though 9 (bottom),
and 10 though 19 (top), left to right. ADCs install vertically in the front of the router.

NOTE: When a slot is not occupied by a combined ADC and MPC, you must
insert a blank panel to fill the empty slot and ensure proper cooling of the
system.

ADCs are hot-removable and hot-insertable. Figure 52 on page 272 shows the ADC
supported on the MX2010 and MX2020 routers.

Copyright © 2018, Juniper Networks, Inc. 271

MX Series Interface Module Reference

Figure 52: ADC for the MX2010 and MX2020 Routers

OK/FAI

g007010

Related • Removing an MX2020 MPC with Adapter Card

Documentation
• Maintaining MX2020 Adapter Cards

MX2010 Adapter Card (ADC) Description

The MX2010 router is compatible with all Trio-based MPC line cards. However, because
the MX2010 router uses a newer-generation Switch Fabric Board (SFB) with faster
bandwidth, line cards that were designed to work with the SCB and SCBE (MPC1E, MPC2E,
and MPC3E) must use a special Line Card Adapter (ADC). The ADC is merely a shell that
accepts MPC1E, MPC2E, and MPC3E line cards in the front and converts power and switch
fabric in the rear. The MX2010 router has 10 dedicated line card slots and can thus support
up to 10 ADCs and 10 MPC1E through MPC3E line cards.

The dedicated line cards slots in the MX2010 router are numbered 0 though 9 (left to
right). ADCs install vertically in the front of the router.

NOTE: When a slot is not occupied by a combined ADC and MPC, you must
insert a blank panel to fill the empty slot and ensure proper cooling of the
system.

Adapter cards are hot-removable and hot-insertable. Figure 52 on page 272 shows the
ADC supported by MX2010 and MX2020 routers.

272 Copyright © 2018, Juniper Networks, Inc.

 Chapter 13: ADC Descriptions

Figure 53: ADC for the MX2010 and MX2020 Routers

OK/FAI

g007010

Related • Removing the MPCs with Adapter Card Before Installing an MX2010 Router with a Pallet
Documentation Jack

• Removing an MX2010 MPC with Adapter Card

• Removing the MPCs without an Adapter Card Before Installing an MX2010 Router with
a Pallet Jack

• Reinstalling the MPCs After Installing the MX2010 Router with a Pallet Jack

• Reinstalling the Adapter Card After Installing the MX2010 Router with a Pallet Jack

• Maintaining the MX2010 Adapter Cards

Copyright © 2018, Juniper Networks, Inc. 273

MX Series Interface Module Reference

274 Copyright © 2018, Juniper Networks, Inc.

CHAPTER 14

RE, CB-RE, and RCB Descriptions

• MX2000 Host Subsystem CB-RE Description on page 275

• MX960 Routing Engine Description on page 276
• MX480 Routing Engine Description on page 278
• MX240 Routing Engine Description on page 280
• MX5, MX10, MX40, and MX80 Routing Engine Description on page 284
• MX2008 Routing and Control Board (MX2008 RCB) Description on page 284
• MX10003 Routing and Control Board (RCB) Description on page 288
• Routing Engine Specifications on page 291

MX2000 Host Subsystem CB-RE Description

The host subsystem provides routing protocol processes, as well as software processes
that control the router’s interface, the chassis components, system management, and
user access to the router. These routing processes run on top of a kernel that interacts
with the Packet Forwarding Engine (PFE). You can install one or two host subsystems
on the router. Each host subsystem functions as a unit—the Control Board and Routing
Engine (CB-RE). The MX2000 line of routers supports the following CB-RE’s:

• RE-MX2000-1800x4 CB-RE

• REMX2K-X8-64G-LT CB-RE

The CB-RE is hot-pluggable. You can install one or two CB-REs in the router. Each CB-RE
is a combined Routing Engine and Control Board in one unit. A USB port on the CB-RE
accepts a USB memory device that allows you to load Junos OS. The CB-RE installs into
the front of the chassis in vertical slots labeled 0 and 1. If two CB-REs are installed, one
functions as the master and the other acts as the backup. If the master CB-RE fails or is
removed and the backup is configured appropriately, the backup takes over as the master.
If no CB-RE is installed in a slot, install a blank panel in the slot.

A minimum of one CB-RE must be installed in either slot 0 or slot 1 at all times.

CAUTION: If one of the CB-REs fails, do not remove the failed CB-RE until
you have a replacement or blank panel to install.

Copyright © 2018, Juniper Networks, Inc. 275

MX Series Interface Module Reference

NOTE: REMX2K-X8-64G-LT CB-RE is equipped with limited encryption

support only.

Related • RE-MX2000-1800x4 CB-RE Description

Documentation
• REMX2K-X8-64G and REMX2K-X8-64G-LT CB-RE Description

• Maintaining the MX2010 Host Subsystem

• Maintaining the MX2020 Host Subsystem

• Taking an MX2000 Host Subsystem Offline

• RJ-45 Connector Pinouts for MX Series CB-RE or RCB Auxillary and Console Ports

• RJ-45 Connector Pinouts for an MX Series CB-RE or RCB Management Port

MX960 Routing Engine Description

If the host system is redundant, the backup Routing Engine is hot-removable and
hot-insertable, but the master Routing Engine is hot-pluggable. A Routing Engine that is
not redundant is hot-pluggable.

• Supported Routing Engines on page 276

• Routing Engine Function on page 277
• Routing Engine Slots on page 277
• Routing Engine Interface Ports on page 277

Supported Routing Engines

The MX960 router supports the following Routing Engines:

• RE-S-1300-2048 supported for Junos OS Release 8.2 and later.

• RE-S-2000-4096 supported for Junos OS Release 8.2 and later.

• RE-S-1800x2 supported for Junos OS Release 10.4 and later.

• RE-S-1800x4 supported for Junos OS Release 10.4 and later.

• RE-S-X6-64G supported for Junos OS Release 15.1F4, 16.1 and later.

• RE-S-X6-64G-LT supported for Junos OS Release 17.2R1 and later.

NOTE: The Routing Engine is equipped with limited encryption support

only.

NOTE: If two Routing Engines are installed, they must both be the same
hardware model.

276 Copyright © 2018, Juniper Networks, Inc.

 Chapter 14: RE, CB-RE, and RCB Descriptions

Routing Engine Function

The Routing Engine runs the Junos OS. Software processes that run on the Routing Engine
maintain the routing tables, manage the routing protocols used on the router, control
the router interfaces, control some chassis components, and provide the interface for
system management and user access to the router.

Routing Engine Slots

You can install one or two Routing Engines in the router. Each Routing Engine must be
installed directly into an SCB. A USB port on the Routing Engine accepts a USB memory
device that allows you to load Junos OS. The Routing Engines install into the front of the
chassis in vertical slots directly into the SCBs labeled 0 and 1. If two Routing Engines are
installed, one functions as the master and the other acts as the backup. If the master
Routing Engine fails or is removed and the backup is configured appropriately, the backup
takes over as the master.

On the MX960 router, a Routing Engine installed in SCB slot 2/6 receives no power and
supplies no additional routing functions. If no SCB is installed in slot 2/6, install a blank
panel in the slot.

Routing Engine Interface Ports

Three ports, located on the right side of the routing engine, connect the Routing Engine
to one or more external devices on which system administrators can issue Junos OS
command-line interface (CLI) commands to manage the router.

The ports with the indicated labels function as follows:

• AUX—Connects the Routing Engine to a laptop, modem, or other auxiliary device

through a serial cable with an RJ-45 connector.

• CONSOLE—Connects the Routing Engine to a system console through a serial cable

with an RJ-45 connector.

• ETHERNET or MGMT—Connects the Routing Engine through an Ethernet connection

to a management LAN (or any other device that plugs into an Ethernet connection)
for out-of-band management. The port uses an autosensing RJ-45 connector to support
10-Mbps or 100-Mbps connections. Two small LEDs on the right of the port indicate
the connection in use: the LED flashes yellow or green for a 10-Mbps or 100-Mbps
connection, and the LED is light green when traffic is passing through the port.

Related • RJ-45 Connector Pinouts for MX Series Routing Engine AUX and CONSOLE Ports
Documentation
• RJ-45 Connector Pinouts for an MX Series Routing Engine ETHERNET Port

• Replacing an MX960 Routing Engine

Copyright © 2018, Juniper Networks, Inc. 277

MX Series Interface Module Reference

MX480 Routing Engine Description

The Routing Engine is an Intel-based PC platform that runs Junos OS. Software processes
that run on the Routing Engine maintain the routing tables, manage the routing protocols
used on the router, control the router interfaces, control some chassis components, and
provide the interface for system management and user access to the router.

You can install one or two Routing Engines in the router. The Routing Engines install into
the front of the chassis in horizontal slots in the SCBs labeled 0 and 1. If two Routing
Engines are installed, one functions as the master and the other acts as the backup. If
the master Routing Engine fails or is removed, and the backup is configured appropriately,
the backup takes over as the master.

The Routing Engines are hot-pluggable. Each Routing Engine must be installed directly
into an SCB. A USB port on the Routing Engine accepts a USB memory card that allows
you to load Junos OS. Figure 54 on page 278 shows RE-S-1800 Routing Engine and
Figure 55 on page 278 shows the RE-S-X6-64G Routing Engine.

Figure 54: RE-S-1800 Routing Engine

Figure 55: RE-S-X6-64G Routing Engine Front View

1— Extractor clips 6—ONLINE/OFFLINE Button

2— Auxiliary port (AUX) 7— SSD LEDs—DISK1 and DISK2

3— Console port (Con) 8—Ports—USB1 and USB2

4— Management port (MGMT) 9—RESET Button

5— LEDs—ONLINE, OK/FAIL, and MASTER 10—SSD card slot cover

278 Copyright © 2018, Juniper Networks, Inc.

 Chapter 14: RE, CB-RE, and RCB Descriptions

Figure 56: RE-S-X6-64G-LT Routing Engine Front View

1— Extractor clips 6—ONLINE/OFFLINE Button

2— Auxiliary port (AUX) 7— SSD LEDs—DISK1 and DISK2

3— Console port (Con) 8—Ports—USB1 and USB2

4— Management port (MGMT) 9—RESET Button

5— LEDs—ONLINE, OK/FAIL, and MASTER 10—SSD card slot cover

Routing Engine Components

NOTE: For specific information about Routing Engine components (for

example, the amount of DRAM), issue the show vmhost hardware command.

Routing Engine Interface Ports

Three ports, located on the right side of the Routing Engine, connect the Routing Engine
to one or more external devices on which system administrators can issue Junos OS
command-line interface (CLI) commands to manage the router.

The ports with the indicated labels function as follows:

• AUX—Connects the Routing Engine to a laptop, modem, or other auxiliary device

through a serial cable with an RJ-45 connector.

• CONSOLE—Connects the Routing Engine to a system console through a serial cable

with an RJ-45 connector.

• ETHERNET or MGMT—Connects the Routing Engine through an Ethernet connection

to a management LAN (or any other device that plugs into an Ethernet connection)
for out-of-band management. The port uses an autosensing RJ-45 connector to support
10-Mbps or 100-Mbps connections. Two small LEDs on the right of the port indicate
the connection in use: The LED on the left indicates speed—green for 1000-Mbps,
yellow for 100-Mbps and when the LED is dark, it indicates 10-Mbps speed. The LED
on the right indicates activity—flashing green when packets are passing through the
port.

Routing Engine Boot Sequence

The Routing Engine boots from the storage media in this order: the USB device (if present),
then the CompactFlash card, then the hard disk, then the LAN. The disk from which the
router boots is called the primary boot device, and the other disk is the alternate boot
device.

Copyright © 2018, Juniper Networks, Inc. 279

MX Series Interface Module Reference

NOTE: If the router boots from an alternate boot device, a yellow alarm lights
the LED on the router’s craft interface.

Booting in a RE-S-X6-64G Routing Engine follows this sequence—the USB device, SSD1,
SSD2, and LAN. SSD1 is the primary boot device. Boot sequence is tried twice for SSD1
and SSD2.

If the Routing Engines are configured for graceful switchover, the backup Routing Engine
automatically synchronizes its configuration and state with the master Routing Engine.
Any update to the master Routing Engine state is replicated on the backup Routing Engine.
If the backup Routing Engine assumes mastership, packet forwarding continues through
the router without interruption. For more information about graceful switchover, see the
Junos OS Administration Library.

NOTE: If two Routing Engines are installed, they must both be the same
hardware model.

Related • MX480 Router Description

Documentation
• MX480 Routing Engine LEDs

• MX480 Host Subsystem Description

• MX480 SCB Description on page 266

MX240 Routing Engine Description

The Routing Engine is an Intel-based PC platform that runs Junos OS. Software processes
that run on the Routing Engine maintain the routing tables, manage the routing protocols
used on the router, control the router interfaces, control some chassis components, and
provide the interface for system management and user access to the router.

You can install one or two Routing Engines in the router. The Routing Engines install into
the front of the chassis in horizontal slots in the SCBs labeled 0 and 1/0. Each Routing
Engine must be installed directly into an SCB. A USB port on the Routing Engine accepts
a USB memory card that allows you to load Junos OS.

If two Routing Engines are installed, one functions as the master and the other acts as
the backup. If the master Routing Engine fails or is removed and the backup is configured
appropriately, the backup takes over as the master. The Backup Routing Engine is
hot-insertable and hot-removable.

The MX240 router supports the RE-S-1300-2048, EE-S-2000-4096, RE-S-1800,

RE-S-X6-64G, and RE-S-X6-64G-LT Routing Engines. See Figure 54 on page 278,
Figure 58 on page 281, and Figure 55 on page 278.

280 Copyright © 2018, Juniper Networks, Inc.

 Chapter 14: RE, CB-RE, and RCB Descriptions

NOTE: If two Routing Engines are installed, they must both be the same
hardware model.

The RE-S-X6-64G-LT Routing Engine is equipped with limited encryption

support only.

Figure 57: RE-S-2000 Routing Engine

Figure 58: RE-S-1800

SSD
slot 1 SSD
slot 2

g006038

Extractor clip
USB port
Reset Online/Offline
button button Extractor clip

Figure 59: RE-S-X6-64G Routing Engine Front View

1— Auxiliary port (AUX) 6—LEDs—ONLINE, OK/FAIL, and MASTER

2— Console port (Con) 7— RESET Button

3— Management port (MGMT) 8—SSD LEDs—DISK1 and DISK2

4— ONLINE/OFFLINE Button 9—SSD card slot cover

5—Ports—USB1 and USB2

Copyright © 2018, Juniper Networks, Inc. 281

MX Series Interface Module Reference

Figure 60: RE-S-X6-64G-LT Routing Engine Front View

1— Extractor clips 6—ONLINE/OFFLINE Button

2— Auxiliary port (AUX) 7— SSD LEDs—DISK1 and DISK2

3— Console port (Con) 8—Ports—USB1 and USB2

4— Management port (MGMT) 9—RESET Button

5— LEDs—ONLINE, OK/FAIL, and MASTER 10—SSD card slot cover

RE-S-X6-64G and RE-S-X6-64G-LT Routing Engine Components

In MX240 routers with dual Routing Engines, both the Routing Engines must be
RE-S-X6-64G Routing Engines.

Each RE-S-X6-64G Routing Engine (shown in Figure 55 on page 278) consists of the
following components:

• CPU—Runs Junos OS to maintain the routing tables and routing protocols.

• EEPROM—Stores the serial number of the Routing Engine.

• DRAM—Provides storage for the routing and forwarding tables and for other Routing
Engine processes.

• One 10-Gigabit Ethernet interface between Routing Engine and Switch Control Board.

• Two 50 GB slim Solid State Drives—SSD1 (primary) and SSD2 (secondary)—Provide

storage for software images, configuration files, microcode, log files, and memory
dumps. The Routing Engine reboots from SSD2 when boot from primary SSD fails.

• Two USB ports (USB1 and USB2)—Provide a removable media interface through which
you can install Junos OS manually. The Junos OS supports USB versions 3.0, 2.0, and
1.1.

• Interface ports—The AUX, CONSOLE, and MGMT provide access to management

devices. Each Routing Engine has one 10/100/1000-Mbps Ethernet port for connecting
to a management network, and two asynchronous serial ports—one for connecting to
a console and one for connecting to a modem or other auxiliary device.

• RESET Button—Reboots the Routing Engine when pressed.

• ONLINE/OFFLINE Button—Makes the Routing Engine online or offline when pressed.

• Extractor clips—Control the locking system that secures the Routing Engine.

• LEDs—MX240 Routing Engine LEDs describes the functions of these LEDs.

282 Copyright © 2018, Juniper Networks, Inc.

 Chapter 14: RE, CB-RE, and RCB Descriptions

NOTE: For specific information about Routing Engine components (for

example, the amount of DRAM), issue the show vmhost hardware command.

Routing Engine Interface Ports

Three ports, located on the right side of the Routing Engine, connect the Routing Engine
to one or more external devices on which system administrators can issue Junos OS
command-line interface (CLI) commands to manage the router.

The ports with the indicated labels function as follows:

• AUX—Connects the Routing Engine to a laptop, modem, or other auxiliary device

through a serial cable with an RJ-45 connector.

• CONSOLE—Connects the Routing Engine to a system console through a serial cable

with an RJ-45 connector.

• ETHERNET or MGMT—Connects the Routing Engine through an Ethernet connection

to a management LAN (or any other device that plugs into an Ethernet connection)
for out-of-band management. The port uses an autosensing RJ-45 connector to support
10/100/1000-Mbps connections. Two small LEDs on the right of the port indicate the
connection in use: The LED on the left indicates speed—green for 1000-Mbps, yellow
for 100-Mbps and when the LED is dark, it indicates 10-Mbps speed. The LED on the
right indicates activity—flashing green when packets are passing through the port.

RE-S-X6-64G and RE-S-X6-64G-LT Routing Engine Interface Ports

Three ports, located on the left side of the Routing Engine, connect the Routing Engine
to one or more external devices on which system administrators can issue Junos OS
command-line interface (CLI) commands to manage the router.

The ports with the indicated labels function as follows:

• AUX—Connects the Routing Engine to a laptop, modem, or other auxiliary device

through a serial cable with an RJ-45 connector.

• CONSOLE—Connects the Routing Engine to a system console through a serial cable

with an RJ-45 connector.

• MGMT—Connects the Routing Engine through an Ethernet connection to a management

LAN (or any other device that plugs into an Ethernet connection) for out-of-band
management. The port uses an autosensing RJ-45 connector to support
10/100/1000-Mbps connections. Two small LEDs on the right of the port indicate the
connection in use: The LED on the left ndicates speed—green for 1000-Mbps, yellow
for 100-Mbps and when the LED is dark, it indicates 10-Mbps speed. The LED on the
right indicates activity—flashing green when packets are passing through the port.

Routing Engine Boot Sequence

The Routing Engine boots from the storage media in this order: the USB device (if present),
then the CompactFlash card, then the hard disk, then the LAN. The disk from which the

Copyright © 2018, Juniper Networks, Inc. 283

MX Series Interface Module Reference

router boots is called the primary boot device, and the other disk is the alternate boot
device.

NOTE: If the router boots from an alternate boot device, a yellow alarm lights
the LED on the router’s craft interface.

Booting in a RE-S-X6-64G and in a RE-S-X6-64G-LT Routing Engine follows this

sequence—the USB device, SSD1, SSD2, and LAN. SSD1 is the primary boot device. Boot
sequence is tried twice for SSD1 and SSD2.

Related • MX240 Routing Engine LEDs

Documentation
• Removing an MX240 Routing Engine

• Installing an MX240 Routing Engine

• MX240 Routing Engine Serial Number Label

MX5, MX10, MX40, and MX80 Routing Engine Description

The Routing Engine is built-in on the MX5, MX10, MX40, and MX80 baseboard and cannot
be replaced.

The Routing Engine consists of the following components:

• Processor—Runs Junos OS to maintain the router's routing tables and routing protocols.

• DRAM—Buffers incoming packets and provides storage for the routing and forwarding
tables and for other Routing Engine processes. To view the amount of DRAM installed
on your router, issue the show chassis routing-engine command.

• NAND flash—Provides primary storage for software images, configuration files, and
microcode.

Related • MX5, MX10, MX40, and MX80 Routing Engine LED

Documentation
• Maintaining the MX5, MX10, MX40, and MX80 Routing Engine

• show chassis routing-engine

MX2008 Routing and Control Board (MX2008 RCB) Description

The MX2008 Routing and Control Board (MX2008 RCB) is an integrated board and a
single FRU that provides Routing Engine and Control Board functionality.

• Supported RCB on page 285

• RCB Function on page 285
• RCB Slots on page 285

284 Copyright © 2018, Juniper Networks, Inc.

 Chapter 14: RE, CB-RE, and RCB Descriptions

• RCB Front Panel on page 285

• RCB Interface Ports on page 287

Supported RCB
The following are some key attributes of the MX2008 RCB:

• The RCB combined the Control Board and the Routing Engine in a single FRU.

• The RCB is hot-pluggable.

• The RCB is less than half the size of native MX2000 CB-RE.

The MX2008 router supports the following RCB:

• REMX2008-X8-64G

RCB Function
The RCB runs Junos OS. Software processes that run on the RCB maintain the routing
tables, manage the routing protocols used on the router, control the router interfaces,
control some chassis components, and provide the interface for system management
and user access to the router.

RCB Slots
The user can install one or two RCBs in the router. Each RCB is a combined Routing Engine
and Control Board in one unit. A USB port on the RCB accepts a USB storage device that
enables you to load Junos OS. You can install the RCBs into the front of the chassis in
vertical slots labeled 0 and 1. If two RCBs are installed, one functions as the master and
the other acts as the backup. If the master RCB fails or is removed and the backup is
configured appropriately, the backup takes over as the master. If no RCB is installed in
a slot, install a blank panel in the slot.

A minimum of one RCB must be installed in either slot 0 or slot 1 at all times.

CAUTION: If one of the RCBs fails, do not remove the failed RCB until you
have a replacement or blank panel to install.

RCB Front Panel

Table 30 on page 286 describes the Routing and Control Board (RCB).

Copyright © 2018, Juniper Networks, Inc. 285

MX Series Interface Module Reference

Figure 61: RCB Front View

Table 30: Components on the RCB

Function No. Label Description

1 ONLINE, MASTER, and There is one bicolor LED for each RCB
OK/FAIL control. The ONLINE LED indicates that
the RCB is transitioning online and
functioning properly. The MASTER LED
indicates that this board is a master
RCB, and the OK/FAIL LED indicates the
RCB has failed.

2 SSD0 and SSD1 LEDs shows the state of the two

solid-state drives (SSDs) in the RCB.

3 GPS, UT1, and BITS These ports shows the external clocking
interface status. There is one bicolor
4 LED for each external clock
interface—GPS, UTI and BITS.

5 RESET This button used to reboot the RCB.

6 AUX This port is used to connect a laptop,

modem, or other auxiliary unit.

7 CLK0 and CLK1 Connects the RCB to two external clock

interfaces for BITS and GPS function
12 through a serial cable with an RJ-45
connector.

286 Copyright © 2018, Juniper Networks, Inc.

 Chapter 14: RE, CB-RE, and RCB Descriptions

Table 30: Components on the RCB (continued)

Function No. Label Description

8 LNK-0 and LNK-1 Two SFP+ ports connects the RCB

through an Ethernet connection to
11 support hardware diagnostics and JCS
port testing. The port supports two
1–Gbps or 10-Gbps connections.

The LED on these ports are associated

with each of the SFP+ port (XGE-0 and
XGE-1) and indicates the connection in
use.

9 USB This port is used to install a USB flash

drive that contains Junos OS.

10 MGT This port is a dedicated management

channel for device maintenance. It is
also used for system administrators to
monitor and manage the MX2008
router remotely.

13 CONSOLE This port is used to configure the

MX2008 router.

RCB Interface Ports

Three ports, located on the RCB, connect the RCB to one or more external devices on
which system administrators can issue Junos OS CLI commands to manage the router.
In addition, four ports located on the RCB include, two 10-Gigabit Ethernet SFP+ interface
connectors supporting hardware diagnostics (JCS port testing), and two external clock
interfaces for BITS and GPS function.

The RCB interface ports with the indicated labels function as follows:

• AUX—Connects the RCB to a laptop, modem, or other auxiliary device through a serial
cable with an RJ-45 connector.

• CONSOLE—Connects the RCB to a system console through a serial cable with an RJ-45
connector.

• MGT—Connects the RCB through an Ethernet connection to a management LAN (or

any other device that plugs into an Ethernet connection) for out-of-band management.
The port uses an autosensing RJ-45 connector to support 10-Mbps, 100-Mbps, or
1000-Mbps connections. Two small LEDs on the bottom of the port indicate the
connection in use: the LED flashes yellow or green for a 10-Mbps, 100-Mbps, or
1000-Mbps connection, and the LED is lit green when traffic is passing through the
port.

The Control Board interface ports function as follows:

• USB—Provides a removable media interface through which you can install the Junos
OS manually. Junos OS supports USB version 1.0 and later.

Copyright © 2018, Juniper Networks, Inc. 287

MX Series Interface Module Reference

• LNK-0 and LNK-1—Two SFP+ port connect the RCB through Ethernet to support two
1-Gbps or 10-Gbps connections to any external control box. Two small LEDs on the
side of each SFP+ port indicate the connection in use: the LED flashes yellow when
there is no link, flashes green when there is activity, or is lit green for a 1-Gbps or 10-Gbps
connection.

• CLK-0 and CLK-1—Connect the RCB to an external clock device through a serial cable
with an RJ-45 connector.

Related • RJ-45 Connector Pinouts for MX Series CB-RE or RCB Auxillary and Console Ports
Documentation
• RJ-45 Connector Pinouts for an MX Series CB-RE or RCB Management Port

• Replacing an MX2008 RCB

• MX2008 Host Subsystem Description

• Supported Routing Engines by Router

• Routing Engine Specifications on page 291

MX10003 Routing and Control Board (RCB) Description

The host subsystem provides routing protocol processes, as well as software processes
that control the router’s interface, the chassis components, system management, and
user access to the router. These routing processes run on top of a kernel that interacts
with the Packet Forwarding Engine. The MX10003 host subsystem consists of two Routing
and Control Boards, or RCBs. The RCB is an integrated board and a single FRU that
provides Routing Engine (RE) and Control Board (CB) functionality. The RE performs all
route-processing functions, whereas the CB performs chassis control and management
plane functionality. The RCB provides control plane functions. You can install one or two
RCBs on the router. Each RCB functions as a unit.

NOTE: Install two RCBs for redundant protection. If you install only one RCB,
you can install it in slot 0 or slot 1. By default, slot 0 functions as the master.

CAUTION: If one of the RCBs fails, do not remove the failed RCB until you
have a replacement or blank panel to install.

Figure 62 on page 289 shows the front panel of the MX10003 RCB.

This topic covers:

• Routing and Control Board Functions on page 289

• Routing and Control Board Components on page 289
• RCB Front Panel on page 289
• RCB Interface Ports on page 290

288 Copyright © 2018, Juniper Networks, Inc.

 Chapter 14: RE, CB-RE, and RCB Descriptions

Routing and Control Board Functions

The Routing and Control Board integrates the Routing Engine and Control Board functions
into a single management unit. Each RCB provides all the functions needed to manage
the operation of the modular chassis:

• System control functions such as environmental monitoring

• Routing Layer 2 and Layer 3 protocols

• Communication to all components such as line cards, power, and cooling

• Transparent clocking

• Alarm and logging functions

Routing and Control Board Components

Each RCB consists of the following internal components:

• High-performance 1.6-GHz Intel 8 Core X86 CPU

• 64-GB DDR4 RAM

• 100-GB SATA SSD

RCB Front Panel

Figure 62 on page 289 shows the front panel of the MX10003 RCB.

Figure 62: Routing and Control Board (RCB) Ports

1 2 3 4 5 6 7 8 9 10

g009824

14 13 12 11

1— USB port 8—Time of day (ToD) port with LEDs

2— Management (MGMT) port 9—BITS port with LEDs

3— Console (CON) port 10—Clocking ports

4— SSD LEDs 11— OFFLINE button

5— SSD slots (0 and 1) 12—ONLINE LED

6—Master (MST) LED 13—OK/FAIL LED

7— Alarm (ALM) LED 14—RESET button

Copyright © 2018, Juniper Networks, Inc. 289

MX Series Interface Module Reference

RCB Interface Ports

The ports located on the RCB, connect the RCB to one or more external devices on which
system administrators can issue Junos OS CLI commands to manage the router. In
addition, ports to connect external clock interfaces for BITS and GPS function are also
available on the RCB.

The RCB interface ports with the indicated labels function are as follows (see
Figure 62 on page 289):

• CON—Connects the RCB to a system console through a serial cable with an RJ-45
connector.

• MGMT—Connects the RCB through an Ethernet connection to a management LAN (or

any other device that plugs into an Ethernet connection) for out-of-band management.
The port uses an autosensing RJ-45 connector to support 10-Mbps, 100-Mbps, or
1000-Mbps connections. Two small LEDs on the port indicate the connection in use:
the LED flashes yellow or green for a 10-Mbps, 100-Mbps, or 1000-Mbps connection,
and the LED is lit green when traffic is passing through the port.

• BITS—Building-integrated timing supply (BITS) external clocking interface for

connection to external clocking devices.

• ToD—Time-of-day (TOD) port on the front panel of the router allows you to connect
external timing signal sources.

• 10MHZ (one input and one output)—The 10-MHz timing connectors on the front panel
of the router connect to external clock signal sources. The clocking ports provide the
synchronized output clocks from any one of the reference clock inputs based on the
clock’s priority.

• PPS (one input and one output)—1-pulse-per-second (PPS) connectors on the front
panel of the router connect to external clock signal sources. The clocking ports provide
the synchronized output clocks from any one of the reference clock inputs based on
the clock’s priority.

• USB—Provides a removable media interface through which you can install Junos OS
manually. Junos OS supports USB version 1.0 and later.

Related • Replacing an MX10003 RCB

Documentation
• RJ-45 Connector Pinouts for MX Series CB-RE or RCB Auxillary and Console Ports

• RJ-45 Connector Pinouts for an MX Series CB-RE or RCB Management Port

• Supported Routing Engines by Router

• Routing Engine Specifications on page 291

290 Copyright © 2018, Juniper Networks, Inc.

 Chapter 14: RE, CB-RE, and RCB Descriptions

Routing Engine Specifications

Table 31 on page 291 lists the current specifications for Routing Engines supported on
M Series, MX Series, and T Series routers. Table 32 on page 293 lists the specifications for
end-of-life Routing Engines.

NOTE: For a list of the routing engines that are supported on the M Series,
MX Series, T Series, and PTX routers, see Supported Routing Engines by Router.

NOTE: For information about PTX Series Routing Engine specifications, see
Routing Engines Supported on PTX Series Routers. For information about

Table 31: Routing Engine Specifications

Routing Connection First Junos OS Switch Control

Engine Processor Memory to PFEs Disk Media Support Board

RE-400-768 400-MHz 768 MB Fast 40 GB hard 1 GB 9.0 –

Celeron Ethernet disk CompactFlash
card

RE-A-1000-2048 1.0-GHz 2048 MB Gigabit 40 GB hard 1 GB 8.1 –

Pentium Ethernet disk CompactFlash
card

RE-A-2000-4096 2.0-GHz 4096 MB Gigabit 40 GB hard 1 GB 8.1 –

Pentium Ethernet disk CompactFlash
card

RE-S-1300-2048 1.3-GHz 2048 MB Gigabit 40 GB hard 1 GB 8.2 SCB, SCBE

Pentium Ethernet disk CompactFlash
card

RE-S-2000-4096 2.0-GHz 4096 MB Gigabit 40 GB hard 1 GB 8.2 SCB, SCBE

Pentium Ethernet disk CompactFlash
card

Copyright © 2018, Juniper Networks, Inc. 291

MX Series Interface Module Reference

Table 31: Routing Engine Specifications (continued)

Routing Connection First Junos OS Switch Control

Engine Processor Memory to PFEs Disk Media Support Board

RE-C1800 1.8-GHz 8 GB Gigabit SSD 4 GB T1600 router in a CB-T for a

Ethernet CompactFlash routing matrix: standalone
card 9.6R2 router.

Standalone CB-LCC for a

T640 or T1600 router in a
router:11.2 routing matrix.

1.8 Ghz 16 GB Gigabit SSD 4 GB 32-bit Junos OS CB-T for a

Ethernet CompactFlash on a standalone standalone
card T1600 router: router.
11.4R2 32-bit
Junos OS on a CB-LCC for a
T1600 router in a router in a
routing matrix: routing matrix.
11.4R2

64-bit Junos OS
on a standalone
T1600 router:
11.4R2 64-bit
Junos OS on a
T1600 router in a
routing matrix:
11.4R2

RE-C2600 2.6-GHz 16 GB Gigabit SSD 4 GB TX Matrix Plus –

Ethernet CompactFlash router: 9.6R2
card

RE-A-1800x2 1800-MHz 8 GB or 16 Gigabit 32 GB SSD 4 GB 10.4 –

GB Ethernet CompactFlash
card

RE-S-1800x2 1800-MHz 8 GB or 16 Gigabit 32 GB SSD 4 GB 10.4 SCB, SCBE

GB Ethernet CompactFlash
card

RE-S-1800x4 1800-MHz 8GB or 16 Gigabit 32 GB SSD 4 GB 10.4 SCB, SCBE,

GB Ethernet CompactFlash SCBE2
card

RE-S-MX104 1.8-GHz 4 GB Gigabit – 8 GB NAND 13.2 –

Ethernet Flash

RE-B-1800x1-4G 1.73-GHz 4 GB Gigabit 64 GB SSD 4 GB 12.1R2, 11.4R4, –

Ethernet CompactFlash and 12.2R1
card

292 Copyright © 2018, Juniper Networks, Inc.

 Chapter 14: RE, CB-RE, and RCB Descriptions

Table 31: Routing Engine Specifications (continued)

Routing Connection First Junos OS Switch Control

Engine Processor Memory to PFEs Disk Media Support Board

RE-MX2000-1800x4 1.8- GHz 16 GB Gigabit 32 GB SSD 4 GB Fixed 12.3R2 SCB, SCBE

Ethernet Internal
CompactFlash
card

RE-S-1800X4-32G-S 1.8- Ghz 32 GB Gigabit 32 GB SSD 4 GB Fixed • 12.3R4 SCB, SCBE

Ethernet Internal • 13.2R1
CompactFlash SCBE2
card

REMX2K-1800-32G-S 1.8- Ghz 32 GB Gigabit 32 GB SSD 4GB Fixed • 12.3R4 –

Ethernet Internal • 13.2R1
CompactFlash
card

RE-S-X6-64G 2 Ghz 64 GB Gigabit Two - 15.1F4, 16.1 SCBE2

Ethernet 50-GB
SSDs

REMX2K-X8-64G 2.3 Ghz 64 GB Gigabit Two - 15.1F5-S1, 16.1R2, –

Ethernet 100-GB and 16.2R1
SSDs

REMX2008-X8-64G 2.3 Ghz 64 GB Gigabit Two - 15.1F7 –

Ethernet 50-GB
SSDs

NOTE: Use shielded CAT5e cable for connecting the AUX, CONSOLE, and
MGMT ports in RE-S-X6-64G, REMX2K-X8-64G, and REMX2008-X8-64G
Routing Engines.

Table 32: End-of-Life Routing Engine Specifications

Routing Connection First Junos OS

Engine Processor Memory to PFEs Disk Media Support EOL Details

RE-333-256 333-MHz 256 MB Fast 6.4 GB hard 80 MB 3.4 PSN-2003-01-063

Pentium II Ethernet disk CompactFlash
card

RE-333-768 333-MHz 768 MB Fast 6.4 GB hard 80 MB 3.4 PSN-2003-01-063

Pentium II Ethernet disk CompactFlash
card

RE-600-512 600-MHz 512 MB Fast 30 GB hard 256 MB 5.4 PSN-2004-07-019

Pentium III Ethernet disk CompactFlash
card

Copyright © 2018, Juniper Networks, Inc. 293

MX Series Interface Module Reference

Table 32: End-of-Life Routing Engine Specifications (continued)

Routing Connection First Junos OS

Engine Processor Memory to PFEs Disk Media Support EOL Details

RE-600-2048 600-MHz 2048 MB Fast 40 GB hard 1 GB 5.3 PSN-2008-02-018

Pentium III Ethernet disk CompactFlash
card

RE-850-1536 850-MHz 1536 MB Fast 40 GB hard 1 GB 7.2 PSN-2011-04-226

Pentium III Ethernet disk CompactFlash
card

RE-M40 200-MHz 256 MB Fast 6.4 GB hard 80 MB 3.2 FA-HW-0101-001

Pentium Ethernet disk CompactFlash
card

RE-M40-333-768 333-MHz 768 MB Fast 10 GB hard 80 MB 4.2 PSN-2003-01-063

Pentium II Ethernet disk CompactFlash
card

RE-M40-600-2048 600-MHz 2048 MB Fast 30 GB hard 128 MB 5.4 PSN-2004-11-020

Pentium III Ethernet disk CompactFlash
card

RE-1600-2048 1.6-GHz 2048 MB Gigabit 40 GB hard 1 GB 6.2 PSN-2008-02-019

Pentium M Ethernet disk CompactFlash
card

NOTE: The memory in Table 31 on page 291 indicates the amount of total
memory. To determine the amount of available memory, issue the show
chassis routing-engine CLI command.

On routers that accept two Routing Engines, you cannot mix Routing Engine types except
for a brief period (one minute or so) during an upgrade or downgrade to two Routing
Engines of the same type.

Related • Supported Routing Engines by Router

Documentation

294 Copyright © 2018, Juniper Networks, Inc.

PART 4

Protocol and Application Support

• DPC Protocol and Application Support for MX240, MX480, and MX960 on page 297
• MPC Protocol and Application Support for MX240, MX480, MX960, MX2010, MX2020,
and MX10003 on page 319

Copyright © 2018, Juniper Networks, Inc. 295

MX Series Interface Module Reference

296 Copyright © 2018, Juniper Networks, Inc.

CHAPTER 15

DPC Protocol and Application Support for

MX240, MX480, and MX960

• Protocols and Applications Supported by DPCs and Enhanced DPCs (DPC and
DPCE-R) on page 297
• Protocols and Applications Supported by Enhanced Ethernet Services DPCs
(DPCE-X) on page 303
• Protocols and Applications Supported by Enhanced Queuing IP Services DPCs
(DPCE-R-Q) on page 307
• Protocols and Applications Supported by Enhanced Queuing Ethernet Services DPCs
(DPCE-X-Q) on page 312
• Protocols and Applications Supported by the Multiservices DPC (MS-DPC) on page 317

Protocols and Applications Supported by DPCs and Enhanced DPCs (DPC and DPCE-R)

Table 33 on page 297 contains the first Junos OS Release support for protocols and
applications on the MX240, MX480, and MX960 DPCs and Enhanced DPCs. A dash
indicates that the protocol or application is not supported.

Table 33: Protocols and Applications Supported by the DPCs and Enhanced DPCs (DPC and DPCE-R)

First Junos OS Release Supported by DPC Model Number (DPC Name)

DPCE-R-
DPC-R- 4XGE-XFP
4XGE-XFP
DPCE-R- DPCE-R- DPCE-R- DPCE-R-
DPC-R- 2XGE-XFP 40GE-SFP 40GE-TX 20GE-2XGE
40GE-SFP
(Enhanced (Enhanced (Tri-Rate (Multi-Rate
Protocol or Application (DPC) DPC) DPC) Enhanced DPC) Enhanced DPC)

Access Node Control 9.4 9.4 9.4 9.4 9.4

Protocol (ANCP)

Accepts traffic destined for 8.2 9.1 8.4 9.1 9.2

GRE tunnels or DVMRP
(IP-in-IP) tunnels

Copyright © 2018, Juniper Networks, Inc. 297

MX Series Interface Module Reference

Table 33: Protocols and Applications Supported by the DPCs and Enhanced DPCs (DPC and DPCE-R) (continued)

First Junos OS Release Supported by DPC Model Number (DPC Name)

DPCE-R-
DPC-R- 4XGE-XFP
4XGE-XFP
DPCE-R- DPCE-R- DPCE-R- DPCE-R-
DPC-R- 2XGE-XFP 40GE-SFP 40GE-TX 20GE-2XGE
40GE-SFP
(Enhanced (Enhanced (Tri-Rate (Multi-Rate
Protocol or Application (DPC) DPC) DPC) Enhanced DPC) Enhanced DPC)

Bidirectional Forwarding 8.2 9.1 8.4 9.1 9.2

Detection protocol (BFD)

Border Gateway Protocol 8.2 9.1 8.4 9.1 9.2

(BGP)

BGP/Multiprotocol Label 8.2 9.1 8.4 9.1 9.2

Switching (MPLS) virtual
private networks (VPNs)

Distance Vector Multicast 8.2 9.1 8.4 9.1 9.2

Routing Protocol (DVMRP)
and generic routing
encapsulation (GRE)
support—access side and
server side

IEEE 802.1ag Ethernet OAM 8.4 9.1 8.4 9.1 9.2

Continuity Check protocol

IEEE 802.1ag Ethernet OAM 9.0 9.1 9.0 9.1 9.2

Linktrace protocol

IEEE 802.1ag Ethernet OAM 9.1 9.1 9.1 9.1 9.2

Loopback protocol

Firewall filters 8.2 9.1 8.4 9.1 9.2

Flexible Ethernet 8.2 9.1 8.4 9.1 9.2

encapsulation

Graceful Routing Engine 8.3 9.1 8.4 9.1 9.2

Switchover (GRES)

Ingress hierarchical quality – – – – –

of service (HQoS) shaping
and hierarchical-scheduler:

• Group of virtual LANs

(VLANs) level
• Virtual LAN (VLAN) level
• Port level

298 Copyright © 2018, Juniper Networks, Inc.

 Chapter 15: DPC Protocol and Application Support for MX240, MX480, and MX960

Table 33: Protocols and Applications Supported by the DPCs and Enhanced DPCs (DPC and DPCE-R) (continued)

First Junos OS Release Supported by DPC Model Number (DPC Name)

DPCE-R-
DPC-R- 4XGE-XFP
4XGE-XFP
DPCE-R- DPCE-R- DPCE-R- DPCE-R-
DPC-R- 2XGE-XFP 40GE-SFP 40GE-TX 20GE-2XGE
40GE-SFP
(Enhanced (Enhanced (Tri-Rate (Multi-Rate
Protocol or Application (DPC) DPC) DPC) Enhanced DPC) Enhanced DPC)

IPv4 8.2 9.1 8.4 9.1 9.2

IP multicast 8.2 9.1 8.4 9.1 9.2

IPv6 8.2 9.1 8.4 9.1 9.2

IPv6 multicast 8.2 9.1 8.4 9.1 9.2

IPv6 Neighbor Discovery 8.2 9.1 8.4 9.1 9.2

Intermediate 8.2 9.1 8.4 9.1 9.2

System-to-Intermediate
System (IS-IS)

Layer 2 frame filtering 8.2 9.1 8.4 9.1 9.2

IEEE 802.3ad link 8.2 9.1 8.4 9.1 9.2

aggregation

Link Aggregation Control 8.2 9.1 8.4 9.1 9.2

Protocol (LACP)

Local loopback 8.2 9.1 8.4 9.1 9.2

MAC learning, policing, 8.2 9.1 8.4 9.1 9.2

accounting, and filtering

IEEE 802.1s Multiple 8.4 9.1 8.4 9.1 9.2

Spanning Tree Protocol
(MSTP) (part of IEEE
802.1Q VLANs)

Multi-chassis link 10.0 10.0 10.0 10.0 10.0

aggregation (MC-AE)

Multiple tag protocol 8.2 9.1 8.4 9.1 9.2

identifiers (TPIDs)

Multiprotocol Label 8.2 9.1 8.4 9.1 9.2

Switching (MPLS)

Copyright © 2018, Juniper Networks, Inc. 299

MX Series Interface Module Reference

Table 33: Protocols and Applications Supported by the DPCs and Enhanced DPCs (DPC and DPCE-R) (continued)

First Junos OS Release Supported by DPC Model Number (DPC Name)

DPCE-R-
DPC-R- 4XGE-XFP
4XGE-XFP
DPCE-R- DPCE-R- DPCE-R- DPCE-R-
DPC-R- 2XGE-XFP 40GE-SFP 40GE-TX 20GE-2XGE
40GE-SFP
(Enhanced (Enhanced (Tri-Rate (Multi-Rate
Protocol or Application (DPC) DPC) DPC) Enhanced DPC) Enhanced DPC)

mvrp 10.1 10.1 10.1 10.1 10.1

IEEE 802.3ah OAM 8.2 9.1 8.4 9.1 9.2

• Discovery and link

monitoring
• Fault signaling and
detection
• Remote loopback

Multitopology Routing 9.0 9.1 9.0 9.1 9.2

(MTR)

Open Shortest Path First 8.2 9.1 8.4 9.1 9.2

(OSPF)

Packet mirroring 8.2 9.1 8.4 9.1 9.2

IEEE 802.1ah provider 10.0 10.0 10.0 10.0 10.0

backbone bridges (PBB)

Quality of service (QoS) 8.2 9.1 8.4 9.1 9.2

per port:

• 8 queues per port

• Shaping at queue level
• Scheduling of queues
based on weighted
round-robin (WRR) per
priority class
• Random early detection
(RED)
• Weighted random early
detection (WRED)

• Shaping at port level – – – – –

300 Copyright © 2018, Juniper Networks, Inc.

 Chapter 15: DPC Protocol and Application Support for MX240, MX480, and MX960

Table 33: Protocols and Applications Supported by the DPCs and Enhanced DPCs (DPC and DPCE-R) (continued)

First Junos OS Release Supported by DPC Model Number (DPC Name)

DPCE-R-
DPC-R- 4XGE-XFP
4XGE-XFP
DPCE-R- DPCE-R- DPCE-R- DPCE-R-
DPC-R- 2XGE-XFP 40GE-SFP 40GE-TX 20GE-2XGE
40GE-SFP
(Enhanced (Enhanced (Tri-Rate (Multi-Rate
Protocol or Application (DPC) DPC) DPC) Enhanced DPC) Enhanced DPC)

Quality of service (QoS) 8.2 9.1 8.4 9.1 9.2

per virtual LAN (VLAN):

• Accounting, filtering, and

policing
• IEEE 802.1p rewrite
• Classification
• Tricolor marking

Quality of service (QoS) – – – – –

queuing per virtual LAN
(VLAN)

IEEE 802.1w Rapid 8.4 9.1 8.4 9.1 9.2

Spanning Tree Protocol
(RSTP)

Per-VLAN Spanning Tree 9.0 9.1 9.0 9.1 9.2

(PVST)+

RSVP 8.2 9.1 8.4 9.1 9.2

Routing Information 8.2 9.1 8.4 9.1 9.2

Protocol (RIP)

SNMP 8.2 9.1 8.4 9.1 9.2

IEEE 802.1D Spanning Tree 8.4 9.1 8.4 9.1 9.2

Protocol (STP)

Subscriber Management: 9.2 9.2 9.2 9.2 9.2

NOTE: Starting in Junos OS

Release 15.1R4, MS-DPCs
are not supported for
subscriber management on
MX Series routers.

• Access Node Control 9.4 9.4 9.4 9.4 9.4

Protocol (ANCP)

• Dynamic profiles 9.2 9.2 9.2 9.2 9.2

Copyright © 2018, Juniper Networks, Inc. 301

MX Series Interface Module Reference

Table 33: Protocols and Applications Supported by the DPCs and Enhanced DPCs (DPC and DPCE-R) (continued)

First Junos OS Release Supported by DPC Model Number (DPC Name)

DPCE-R-
DPC-R- 4XGE-XFP
4XGE-XFP
DPCE-R- DPCE-R- DPCE-R- DPCE-R-
DPC-R- 2XGE-XFP 40GE-SFP 40GE-TX 20GE-2XGE
40GE-SFP
(Enhanced (Enhanced (Tri-Rate (Multi-Rate
Protocol or Application (DPC) DPC) DPC) Enhanced DPC) Enhanced DPC)

• Dynamic VLANs – 9.5 9.5 9.5 9.5

• Enhanced Dynamic Host 9.3 9.3 9.3 9.3 9.3

Configuration Protocol
(DHCP) local server

• Enhanced DCHP relay 9.3 9.3 9.3 9.3 9.3

• Firewall filters 9.2 9.2 9.2 9.2 9.2

• Internet Group 9.2 9.2 9.2 9.2 9.2

Management Protocol
(IGMP)

• QoS 9.2 9.2 9.2 9.2 9.2

• Subscriber Secure Policy 9.4 9.4 9.4 9.4 9.4

Two-Way Active 9.5 9.5 9.5 9.5 9.5

Measurement Protocol
(TWAMP)

IEEE 802.1Q VLANs: 8.2 9.1 8.4 9.1 9.2

• VLAN stacking and

rewriting
• Channels defined by two
stacked VLAN tags
• Flexible VLAN tagging
• IP service for
nonstandard TPID and
stacked VLAN tags

Virtual private LAN service 8.2 9.1 8.4 9.1 9.2

(VPLS)

Virtual private network 8.2 9.1 8.4 9.1 9.2

(VPN)

Virtual Router Redundancy 8.2 9.1 8.4 9.1 9.2

Protocol (VRRP) for IPv4

302 Copyright © 2018, Juniper Networks, Inc.

 Chapter 15: DPC Protocol and Application Support for MX240, MX480, and MX960

Related • DPCs Supported on MX240, MX480, and MX960 Routers on page 8

Documentation
• Protocols and Applications Supported by Enhanced Ethernet Services DPCs (DPCE-X)
on page 303

• Protocols and Applications Supported by Enhanced Queuing IP Services DPCs

(DPCE-R-Q) on page 307

• Protocols and Applications Supported by Enhanced Queuing Ethernet Services DPCs

(DPCE-X-Q) on page 312

• Protocols and Applications Supported by the Multiservices DPC (MS-DPC) on page 317

Protocols and Applications Supported by Enhanced Ethernet Services DPCs (DPCE-X)

Table 34 on page 303 contains the first Junos OS Release support for protocols and
applications on the MX240, MX480, and MX960 Enhanced Ethernet Services DPCs. A
dash indicates that the protocol or application is not supported.

Table 34: Protocols and Applications Supported by the Enhanced Ethernet Services DPCs (DPCE-X)

First Junos OS Release Supported by DPC Model Number (DPC Name)

DPCE-X-4XGE-XFP

DPCE-X-40GE-SFP DPCE-X-40GE-TX DPCE-X-20GE-2XGE

(Enhanced Ethernet (Tri-Rate Enhanced (Multi-Rate Enhanced

Protocol or Application Services DPC) Ethernet Services DPC) Ethernet Services DPC)

Access Node Control Protocol (ANCP) 9.4 9.4 9.4

Accepts traffic destined for GRE tunnels 8.4 9.1 9.2

or DVMRP (IP-in-IP) tunnels

Bidirectional Forwarding Detection 8.4 9.1 9.2

protocol (BFD)

Border Gateway Protocol (BGP) 8.4 9.1 9.2

BGP/Multiprotocol Label Switching 8.4 9.1 9.2

(MPLS) virtual private networks (VPNs)

Distance Vector Multicast Routing 8.4 9.1 9.2

Protocol (DVMRP) and generic routing
encapsulation (GRE) support—access side
and server side

IEEE 802.1ag Ethernet OAM Continuity 8.4 9.1 9.2

Check protocol

IEEE 802.1ag Ethernet OAM Linktrace 9.0 9.1 9.2

protocol

Copyright © 2018, Juniper Networks, Inc. 303

 MX Series Interface Module Reference

Table 34: Protocols and Applications Supported by the Enhanced Ethernet Services DPCs (DPCE-X) (continued)

First Junos OS Release Supported by DPC Model Number (DPC Name)

DPCE-X-4XGE-XFP

DPCE-X-40GE-SFP DPCE-X-40GE-TX DPCE-X-20GE-2XGE

(Enhanced Ethernet (Tri-Rate Enhanced (Multi-Rate Enhanced

Protocol or Application Services DPC) Ethernet Services DPC) Ethernet Services DPC)

IEEE 802.1ag Ethernet OAM Loopback 9.1 9.1 9.2

protocol

Firewall filters 8.4 9.1 9.2

(Limited filter terms) (Limited filter terms) (Limited filter terms)

Flexible Ethernet encapsulation 8.4 9.1 9.2

Graceful Routing Engine Switchover 8.4 9.1 9.2

(GRES)

Ingress hierarchical quality of service – – –

(HQoS) shaping and scheduling:

• Group of virtual LANs (VLANs) level

• Virtual LAN (VLAN) level
• Port level

Intermediate System-to-Intermediate 8.4 9.1 9.2

System (IS-IS)

IPv4 (No BGP) 8.4 9.1 9.2)

IP multicast (No BGP) 8.4 9.1 9.2

IPv6 (No BGP) 8.4 9.1 9.2)

IPv6 multicast (No BGP) 8.4 9.1 9.2)

IPv6 Neighbor Discovery (No BGP) 8.4 9.1) 9.2)

Layer 2 frame filtering 8.4 9.1 9.2

IEEE 802.3ad link aggregation 8.4 9.1 9.2

Link Aggregation Control Protocol (LACP) 8.4 9.1 9.2

Local loopback 8.4 9.1 9.2

MAC learning, policing, accounting, and 8.4 9.1 9.2

filtering

304 Copyright © 2018, Juniper Networks, Inc.

 Chapter 15: DPC Protocol and Application Support for MX240, MX480, and MX960

Table 34: Protocols and Applications Supported by the Enhanced Ethernet Services DPCs (DPCE-X) (continued)

First Junos OS Release Supported by DPC Model Number (DPC Name)

DPCE-X-4XGE-XFP

DPCE-X-40GE-SFP DPCE-X-40GE-TX DPCE-X-20GE-2XGE

(Enhanced Ethernet (Tri-Rate Enhanced (Multi-Rate Enhanced

Protocol or Application Services DPC) Ethernet Services DPC) Ethernet Services DPC)

IEEE 802.1s Multiple Spanning Tree 8.4 9.1 9.2

Protocol (MSTP) (part of IEEE 802.1Q
VLANs)

Multiple tag protocol identifiers (TPIDs) 8.4 9.1 9.2

Multiprotocol Label Switching (MPLS) 8.4 9.1 9.2

IEEE 802.3ah OAM 8.4 9.1 9.2

• Discovery and link monitoring

• Fault signaling and detection
• Remote loopback

Multitopology Routing (MTR) 9.0 9.1 9.2

Open Shortest Path First (OSPF) 8.4 9.1 9.2

Packet mirroring 8.4 9.1 9.2

Quality of service (QoS) per port: 8.4 9.1 9.2

• 8 queues per port

• Shaping at queue level
• Scheduling of queues based on
weighted round-robin (WRR) per priority
class
• Random early detection (RED)
• Weighted random early detection
(WRED)

Quality of service (QoS) per virtual LAN 8.4 9.1 9.2

(VLAN):

• Accounting, filtering, and policing

• IEEE 802.1p rewrite
• Classification
• Tricolor marking

Quality of service (QoS) queuing per virtual – – –

LAN (VLAN)

Copyright © 2018, Juniper Networks, Inc. 305

 MX Series Interface Module Reference

Table 34: Protocols and Applications Supported by the Enhanced Ethernet Services DPCs (DPCE-X) (continued)

First Junos OS Release Supported by DPC Model Number (DPC Name)

DPCE-X-4XGE-XFP

DPCE-X-40GE-SFP DPCE-X-40GE-TX DPCE-X-20GE-2XGE

(Enhanced Ethernet (Tri-Rate Enhanced (Multi-Rate Enhanced

Protocol or Application Services DPC) Ethernet Services DPC) Ethernet Services DPC)

IEEE 802.1w Rapid Spanning Tree Protocol 8.4 9.1 9.2

(RSTP)

Per-VLAN Spanning Tree (PVST)+ 9.0 9.1 9.2

RSVP 8.4 9.1 9.2

Routing Information Protocol (RIP) 8.4 9.1 9.2

SNMP 8.4 9.1 9.2

IEEE 802.1D Spanning Tree Protocol (STP) 8.4 9.1 9.2

Subscriber Management: 9.4 9.4 9.4

Starting in Junos OS Release 15.1R4,

MS-DPCs are not supported for subscriber
management on MX Series routers.

• Access Node Control Protocol (ANCP) 9.4 9.4 9.4

• Dynamic profiles 9.2 9.2 9.2

• Dynamic VLANs 9.5 9.5 9.5

• Enhanced Dynamic Host Configuration 9.3 9.3 9.3

Protocol (DHCP) local server

• Enhanced DCHP relay 9.3 9.3 9.3

• Firewall filters 9.2 9.2 9.2

• Internet Group Management Protocol 9.2 9.2 9.2

(IGMP)

• QoS 9.2 9.2 9.2

• Subscriber Secure Policy 9.4 9.4 9.4

Two-Way Active Measurement Protocol 9.5 9.5 9.5

(TWAMP)

306 Copyright © 2018, Juniper Networks, Inc.

 Chapter 15: DPC Protocol and Application Support for MX240, MX480, and MX960

Table 34: Protocols and Applications Supported by the Enhanced Ethernet Services DPCs (DPCE-X) (continued)

First Junos OS Release Supported by DPC Model Number (DPC Name)

DPCE-X-4XGE-XFP

DPCE-X-40GE-SFP DPCE-X-40GE-TX DPCE-X-20GE-2XGE

(Enhanced Ethernet (Tri-Rate Enhanced (Multi-Rate Enhanced

Protocol or Application Services DPC) Ethernet Services DPC) Ethernet Services DPC)

IEEE 802.1Q VLANs: 8.4 9.1 9.2

• VLAN stacking and rewriting

• Channels defined by two stacked VLAN
tags
• Flexible VLAN tagging
• IP service for nonstandard TPID and
stacked VLAN tags

Virtual private LAN service (VPLS) 8.4 9.1 9.2

Virtual private network (VPN) (L2 VPN 8.4 9.1 9.2

only)

Virtual Router Redundancy Protocol 8.4 9.1 9.2

(VRRP) for IPv4

Related • DPCs Supported on MX240, MX480, and MX960 Routers on page 8

Documentation
• Protocols and Applications Supported by DPCs and Enhanced DPCs (DPC and DPCE-R)
on page 297

• Protocols and Applications Supported by Enhanced Queuing IP Services DPCs

(DPCE-R-Q) on page 307

• Protocols and Applications Supported by Enhanced Queuing Ethernet Services DPCs

(DPCE-X-Q) on page 312

• Protocols and Applications Supported by the Multiservices DPC (MS-DPC) on page 317

Protocols and Applications Supported by Enhanced Queuing IP Services DPCs

(DPCE-R-Q)

Table 35 on page 308 contains the first Junos OS Release support for protocols and
applications on the MX240, MX480, and MX960 Enhanced Queuing IP Services DPCs.
A dash indicates that the protocol or application is not supported.

Copyright © 2018, Juniper Networks, Inc. 307

MX Series Interface Module Reference

Table 35: Protocols and Applications Supported by the Enhanced Queuing IP Services DPCs (DPCE-R-Q)

First Junos OS Release Supported by DPC Model Number (DPC

Name)

DPCE-R-Q-4XGE-XFP
DPCE-R-Q-20GE-2XGE
DPCE-R-Q-40GE-SFP DPCE-R-Q-20GE-SFP
Enhanced Queuing
Enhanced Queuing Enhanced Queuing IP Services
Protocol or Application IP Services DPC IP Services DPC Multi-Rate DPC

Access Node Control Protocol (ANCP) 9.4 9.4 9.4

Accepts traffic destined for GRE tunnels or 8.5 9.1 9.3

DVMRP (IP-in-IP) tunnels

Bidirectional Forwarding Detection protocol 8.5 9.1 9.3

(BFD)

Border Gateway Protocol (BGP) 8.5 9.1 9.3

BGP/Multiprotocol Label Switching (MPLS) 8.5 9.1 9.3

virtual private networks (VPNs)

Distance Vector Multicast Routing Protocol 8.5 9.1 9.3

(DVMRP) and generic routing encapsulation
(GRE) support—access side and server side

IEEE 802.1ag Ethernet OAM Continuity Check 8.5 9.1 9.3

protocol

IEEE 802.1ag Ethernet OAM Linktrace protocol 9.0 9.1 9.3

IEEE 802.1ag Ethernet OAM Loopback protocol 9.1 9.1 9.3

Firewall filters 8.5 9.1 9.3

Flexible Ethernet encapsulation 8.5 9.1 9.3

Graceful Routing Engine Switchover (GRES) 8.5 9.1 9.3

Ingress hierarchical quality of service (HQoS) 9.0 9.1 9.3

shaping and scheduling:

• Group of virtual LANs (VLANs) level

• Virtual LAN (VLAN) level
• Port level

Intermediate System-to-Intermediate System 8.5 9.1 9.3

(IS-IS)

IPv4 8.5 9.1 9.3

308 Copyright © 2018, Juniper Networks, Inc.

 Chapter 15: DPC Protocol and Application Support for MX240, MX480, and MX960

Table 35: Protocols and Applications Supported by the Enhanced Queuing IP Services DPCs
(DPCE-R-Q) (continued)

First Junos OS Release Supported by DPC Model Number (DPC

Name)

DPCE-R-Q-4XGE-XFP
DPCE-R-Q-20GE-2XGE
DPCE-R-Q-40GE-SFP DPCE-R-Q-20GE-SFP
Enhanced Queuing
Enhanced Queuing Enhanced Queuing IP Services
Protocol or Application IP Services DPC IP Services DPC Multi-Rate DPC

IP multicast 8.5 9.1 9.3

IPv6 8.5 9.1 9.3

IPv6 multicast 8.5 9.1 9.3

IPv6 Neighbor Discovery 8.5 9.1 9.3

Layer 2 frame filtering 8.5 9.1 9.3

IEEE 802.3ad link aggregation 8.5 9.1 9.3

Link Aggregation Control Protocol (LACP) 8.5 9.1 9.3

Local loopback 8.5 9.1 9.3

MAC learning, policing, accounting, and filtering 8.5 9.1 9.3

IEEE 802.1s Multiple Spanning Tree Protocol 8.5 9.1 9.3

(MSTP) (part of IEEE 802.1Q VLANs)

Multiple tag protocol identifiers (TPIDs) 8.5 9.1 9.3

Multiprotocol Label Switching (MPLS) 8.5 9.1 9.3

IEEE 802.3ah OAM 8.5 9.1 9.3

• Discovery and link monitoring

• Fault signaling and detection
• Remote loopback

Multitopology Routing (MTR) 9.0 9.1 9.3

Open Shortest Path First (OSPF) 8.5 9.1 9.3

Packet mirroring 8.5 9.1 9.3

Copyright © 2018, Juniper Networks, Inc. 309

MX Series Interface Module Reference

Table 35: Protocols and Applications Supported by the Enhanced Queuing IP Services DPCs
(DPCE-R-Q) (continued)

First Junos OS Release Supported by DPC Model Number (DPC

Name)

DPCE-R-Q-4XGE-XFP
DPCE-R-Q-20GE-2XGE
DPCE-R-Q-40GE-SFP DPCE-R-Q-20GE-SFP
Enhanced Queuing
Enhanced Queuing Enhanced Queuing IP Services
Protocol or Application IP Services DPC IP Services DPC Multi-Rate DPC

Quality of service (QoS) per port: 8.5 9.1 9.3

• 8 queues per port

• Shaping at port level
• Scheduling of queues based on weighted
round-robin (WRR) per priority class
• Random early detection (RED)
• Weighted random early detection (WRED)

Quality of service (QoS) per virtual LAN (VLAN): 8.5 9.1 9.3

• Accounting, filtering, and policing

• IEEE 802.1p rewrite
• Classification
• Tricolor marking
• Shaping at queue and port level
• Scheduling of queues based on weighted
round-robin (WRR) per priority class
• Random early detection (RED)
• Weighted random early detection (WRED)

Quality of service (QoS) queuing per virtual LAN 8.5 9.1 9.3
(VLAN)

IEEE 802.1w Rapid Spanning Tree Protocol 8.5 9.1 9.3

(RSTP)

Per-VLAN Spanning Tree (PVST)+ 9.0 9.1 9.3

RSVP 8.5 9.1 9.3

Routing Information Protocol (RIP) 8.5 9.1 9.3

SNMP 8.5 9.1 9.3

IEEE 802.1D Spanning Tree Protocol (STP) 8.5 9.1 9.3

310 Copyright © 2018, Juniper Networks, Inc.

 Chapter 15: DPC Protocol and Application Support for MX240, MX480, and MX960

Table 35: Protocols and Applications Supported by the Enhanced Queuing IP Services DPCs
(DPCE-R-Q) (continued)

First Junos OS Release Supported by DPC Model Number (DPC

Name)

DPCE-R-Q-4XGE-XFP
DPCE-R-Q-20GE-2XGE
DPCE-R-Q-40GE-SFP DPCE-R-Q-20GE-SFP
Enhanced Queuing
Enhanced Queuing Enhanced Queuing IP Services
Protocol or Application IP Services DPC IP Services DPC Multi-Rate DPC

Subscriber Management: 9.4 9.4 9.4

NOTE: Starting in Junos OS Release 15.1R4,

MS-DPCs are not supported for subscriber
management on MX Series routers.

• Access Node Control Protocol (ANCP) 9.4 9.4 9.4

• Dynamic profiles 9.2 9.2 9.2

• Dynamic VLANs 9.5 9.5 9.5

• Enhanced Dynamic Host Configuration 9.3 9.3 9.3

Protocol (DHCP) local server

• Enhanced DCHP relay 9.3 9.3 9.3

• Firewall filters 9.2 9.2 9.2

• Internet Group Management Protocol (IGMP) 9.2 9.2 9.2

• QoS 9.2 9.2 9.2

• Subscriber Secure Policy 9.4 9.4 9.4

• VLAN demux – – –

Two-Way Active Measurement Protocol 9.5 9.5 9.5

(TWAMP)

IEEE 802.1Q VLANs: 8.5 9.1 9.3

• VLAN stacking and rewriting

• Channels defined by two stacked VLAN tags
• Flexible VLAN tagging
• IP service for nonstandard TPID and stacked
VLAN tags

Virtual private LAN service (VPLS) 8.5 9.1 9.3

Virtual private network (VPN) 8.5 9.1 9.3

Copyright © 2018, Juniper Networks, Inc. 311

MX Series Interface Module Reference

Table 35: Protocols and Applications Supported by the Enhanced Queuing IP Services DPCs
(DPCE-R-Q) (continued)

First Junos OS Release Supported by DPC Model Number (DPC

Name)

DPCE-R-Q-4XGE-XFP
DPCE-R-Q-20GE-2XGE
DPCE-R-Q-40GE-SFP DPCE-R-Q-20GE-SFP
Enhanced Queuing
Enhanced Queuing Enhanced Queuing IP Services
Protocol or Application IP Services DPC IP Services DPC Multi-Rate DPC

Virtual Router Redundancy Protocol (VRRP) 8.5 9.1 9.3

for IPv4

Related • DPCs Supported on MX240, MX480, and MX960 Routers on page 8

Documentation
• Protocols and Applications Supported by DPCs and Enhanced DPCs (DPC and DPCE-R)
on page 297

• Protocols and Applications Supported by Enhanced Ethernet Services DPCs (DPCE-X)

on page 303

• Protocols and Applications Supported by Enhanced Queuing Ethernet Services DPCs

(DPCE-X-Q) on page 312

• Protocols and Applications Supported by the Multiservices DPC (MS-DPC) on page 317

Protocols and Applications Supported by Enhanced Queuing Ethernet Services DPCs

(DPCE-X-Q)

Table 36 on page 312 contains the first Junos OS Release support for protocols and
applications on the MX240, MX480, and MX960 Enhanced Queuing Ethernet Services
DPCs. A dash indicates that the protocol or application is not supported.

Table 36: Protocols and Applications Supported by the Enhanced Queuing Ethernet
Services DPCs (DPCE-X-Q)

DPCE-X-Q-4XGE-XFP

DPCE-X-Q-40GE-SFP

(Enhanced Queuing
Protocol or Application Ethernet Services DPC)

Access Node Control Protocol (ANCP) 9.4

Accepts traffic destined for GRE tunnels or DVMRP 8.5

(IP-in-IP) tunnels

Bidirectional Forwarding Detection protocol (BFD) 8.5

Border Gateway Protocol (BGP) 8.5

312 Copyright © 2018, Juniper Networks, Inc.

 Chapter 15: DPC Protocol and Application Support for MX240, MX480, and MX960

Table 36: Protocols and Applications Supported by the Enhanced Queuing Ethernet
Services DPCs (DPCE-X-Q) (continued)

DPCE-X-Q-4XGE-XFP

DPCE-X-Q-40GE-SFP

(Enhanced Queuing
Protocol or Application Ethernet Services DPC)

BGP/Multiprotocol Label Switching (MPLS) virtual private 8.5

networks (VPNs)

Distance Vector Multicast Routing Protocol (DVMRP) and 8.5

generic routing encapsulation (GRE) support—access
side and server side

IEEE 802.1ag Ethernet OAM Continuity Check protocol 8.5

IEEE 802.1ag Ethernet OAM Linktrace protocol 9.0

IEEE 802.1ag Ethernet OAM Loopback protocol 9.1

Firewall filters 8.5

(Limited filter terms)

Flexible Ethernet encapsulation 8.5

Graceful Routing Engine Switchover (GRES) 8.5

Ingress hierarchical quality of service (HQoS) shaping and 9.0

scheduling:

• Group of virtual LANs (VLANs) level

• Virtual LAN (VLAN) level
• Port level

Intermediate System-to-Intermediate System (IS-IS) 8.5

IPv4 (No BGP) 8.5

IP multicast (No BGP) 8.5

IPv6 (No BGP) 8.5

IPv6 multicast (No BGP) 8.5

IPv6 Neighbor Discovery (No BGP) 8.5

Layer 2 frame filtering 8.5

IEEE 802.3ad link aggregation 8.5

Copyright © 2018, Juniper Networks, Inc. 313

MX Series Interface Module Reference

Table 36: Protocols and Applications Supported by the Enhanced Queuing Ethernet
Services DPCs (DPCE-X-Q) (continued)

DPCE-X-Q-4XGE-XFP

DPCE-X-Q-40GE-SFP

(Enhanced Queuing
Protocol or Application Ethernet Services DPC)

Link Aggregation Control Protocol (LACP) 8.5

Local loopback 8.5

MAC learning, policing, accounting, and filtering 8.5

IEEE 802.1s Multiple Spanning Tree Protocol (MSTP) (part 8.5

of IEEE 802.1Q VLANs)

Multiple tag protocol identifiers (TPIDs) 8.5

Multiprotocol Label Switching (MPLS) 8.5

IEEE 802.3ah OAM 8.5

• Discovery and link monitoring

• Fault signaling and detection
• Remote loopback

Multitopology Routing (MTR) 9.0

Open Shortest Path First (OSPF) 8.5

Packet mirroring 8.5

Quality of service (QoS) per port: 8.5

• 8 queues per port

• Shaping at port level
• Scheduling of queues based on weighted round-robin
(WRR) per priority class
• Random early detection (RED)
• Weighted random early detection (WRED)

Shaping at queue level –

314 Copyright © 2018, Juniper Networks, Inc.

 Chapter 15: DPC Protocol and Application Support for MX240, MX480, and MX960

Table 36: Protocols and Applications Supported by the Enhanced Queuing Ethernet
Services DPCs (DPCE-X-Q) (continued)

DPCE-X-Q-4XGE-XFP

DPCE-X-Q-40GE-SFP

(Enhanced Queuing
Protocol or Application Ethernet Services DPC)

Quality of service (QoS) per virtual LAN (VLAN): 8.5

• Accounting, filtering, and policing

• IEEE 802.1p rewrite
• Classification
• Tricolor marking
• Shaping at port level
• Scheduling of queues based on weighted round-robin
(WRR) per priority class
• Random early detection (RED)
• Weighted random early detection (WRED)

Shaping at queue level –

Quality of service (QoS) queuing per virtual LAN (VLAN) 8.5

IEEE 802.1w Rapid Spanning Tree Protocol (RSTP) 8.5

Per-VLAN Spanning Tree (PVST)+ 9.0

Remote loopback 8.5

RSVP 8.5

Routing Information Protocol (RIP) 8.5

SNMP 8.5

IEEE 802.1D Spanning Tree Protocol (STP) 8.5

Subscriber Management: 9.4

Starting in Junos OS Release 15.1R4, MS-DPCs are not

supported for subscriber management on MX Series
routers.

• Access Node Control Protocol (ANCP) 9.4

• Dynamic profiles 9.2

• Dynamic VLANs 9.5

Copyright © 2018, Juniper Networks, Inc. 315

MX Series Interface Module Reference

Table 36: Protocols and Applications Supported by the Enhanced Queuing Ethernet
Services DPCs (DPCE-X-Q) (continued)

DPCE-X-Q-4XGE-XFP

DPCE-X-Q-40GE-SFP

(Enhanced Queuing
Protocol or Application Ethernet Services DPC)

• Enhanced Dynamic Host Configuration Protocol 9.3

(DHCP) local server

• Enhanced DCHP relay 9.3

• Firewall filters 9.2

• Internet Group Management Protocol (IGMP) 9.2

• QoS 9.2

• Subscriber Secure Policy 9.4

• VLAN demux –

Two-Way Active Measurement Protocol (TWAMP) 9.5

IEEE 802.1Q VLANs: 8.5

• VLAN stacking and rewriting

• Channels defined by two stacked VLAN tags
• Flexible VLAN tagging
• IP service for nonstandard TPID and stacked VLAN tags

Virtual private LAN service (VPLS) 8.5

Virtual private network (VPN) 8.5

(L2 VPN only)

Virtual Router Redundancy Protocol (VRRP) for IPv4 8.5

Related • DPCs Supported on MX240, MX480, and MX960 Routers on page 8

Documentation
• Protocols and Applications Supported by DPCs and Enhanced DPCs (DPC and DPCE-R)
on page 297

• Protocols and Applications Supported by Enhanced Ethernet Services DPCs (DPCE-X)

on page 303

• Protocols and Applications Supported by Enhanced Queuing IP Services DPCs

(DPCE-R-Q) on page 307

• Protocols and Applications Supported by the Multiservices DPC (MS-DPC) on page 317

316 Copyright © 2018, Juniper Networks, Inc.

 Chapter 15: DPC Protocol and Application Support for MX240, MX480, and MX960

Protocols and Applications Supported by the Multiservices DPC (MS-DPC)

Table 37 on page 317 contains the first Junos OS Release support for protocols and
applications on the MX240, MX480, and MX960 Multiservices DPCs. A dash indicates
that the protocol or application is not supported.

NOTE: The maximum number of supported MS-DPCs is as follows except

where noted in Table 37 on page 317:

• MX240 router: 2

• MX480 router: 4

• MX960 router: 8

Table 37: Protocols and Applications Supported by the Multiservices DPC (MS-DPC)

Protocol or Application MS-DPC

Accepts traffic destined for GRE tunnels 9.3

Active flow monitoring exports cflowd version 5 and 9.3

version 8 records

Active flow monitoring exports flow monitoring version 9 9.3

records, based on RFC 3954

Graceful Routing Engine Switchover (GRES) 9.4

GRE dont fragment 9.3

GRE Key 9.3

GRE reassembly 9.3

IP Security (IPSec) encryption 9.3

Network Address Translation (NAT) for IP addresses 9.3

NOTE: The MX960 supports 8 MS-DPCs using this

feature.

NAPT - Preserve parity 15.1

NAPT - Preserve range 15.1

No translation 15.1

Twice NAT 15.1

Copyright © 2018, Juniper Networks, Inc. 317

MX Series Interface Module Reference

Table 37: Protocols and Applications Supported by the Multiservices DPC

(MS-DPC) (continued)

Protocol or Application MS-DPC

Packet-triggered dynamic subscribers and policy control 10.2

(PTSP)

NOTE: Starting in Junos OS Release 13.1R1, the

packet-triggered subscribers and policy control (PTSP)
feature is no longer supported.

Port Address Translation (PAT) for port numbers 9.3

Real-time Performance Monitoring (RPM) 9.3

Stateful firewall with packet inspection: detects SYN 9.3

attacks, ICMP and UDP floods, and ping-of-death attacks

NOTE: The MX960 supports 8 MS-DPCs using this

feature.

Tunnel services:

• GRE unicast tunneling-Supports GRE fragmentation 9.3

• IP-IP unicast tunneling 9.4

• Multicast tunneling 9.4

• Protocol Independent Multicast (PIM) sparse mode 9.4

unicast tunneling

• Virtual loopback tunneling (VT) 9.4

Voice over IP (VoIP) services: 10.2

• Border Gateway Function (BGF) using external H.248/Ia

control
• Integrated Multi-Service Gateway (IMSG)–Session
Border Controller

Related • DPCs Supported on MX240, MX480, and MX960 Routers on page 8

Documentation
• Protocols and Applications Supported by DPCs and Enhanced DPCs (DPC and DPCE-R)
on page 297

• Protocols and Applications Supported by Enhanced Ethernet Services DPCs (DPCE-X)

on page 303

• Protocols and Applications Supported by Enhanced Queuing IP Services DPCs

(DPCE-R-Q) on page 307

• Protocols and Applications Supported by Enhanced Queuing Ethernet Services DPCs

(DPCE-X-Q) on page 312

318 Copyright © 2018, Juniper Networks, Inc.

CHAPTER 16

MPC Protocol and Application Support

for MX240, MX480, MX960, MX2010,
MX2020, and MX10003

• Protocols and Applications Supported on MPCs for MX Series Routers on page 319
• Protocols and Applications Supported on the MPC1E for MX Series Routers on page 328
• Protocols and Applications Supported by the MX240, MX480, MX960, MX2010, and
MX2020 MPC2E on page 334
• Protocols and Applications Supported by the MPC3E on MX Series Routers on page 343
• Protocols and Applications Supported on the MPC4E for MX Series Routers on page 351
• Protocols and Applications Supported by the MPC5E for MX Series Routers on page 359
• Protocols and Applications Supported by the MPC6E for MX2000 Routers on page 366
• Protocols and Applications Supported by the MPC7E for MX Series Routers on page 373
• Protocols and Applications Supported by the MPC8E and MPC9E on the MX2010 and
MX2020 Routers on page 382
• Protocols and Applications Supported by the MS-MIC and MS-MPC on page 389
• Protocols and Applications Supported by the MX10003 MPC (Multi-Rate) on the
MX10003 Router on page 391

Protocols and Applications Supported on MPCs for MX Series Routers

Table 38 on page 320 contains the first Junos OS Release support for protocols and
applications on the MX240, MX480, MX960, MX2010, and MX2020 MPCs.

NOTE: The MX2010 router supports protocols and applications in Junos OS

12.3R3 and later. Features added after the Junos OS 12.3R3 release are
supported on the MX2010 router in the release indicated.

NOTE: The MX2020 router supports protocols and applications in Junos OS

12.3R2 and later. Features added after the Junos OS 12.3R2 release are
supported on the MX2020 router in the release indicated.

Copyright © 2018, Juniper Networks, Inc. 319

MX Series Interface Module Reference

A dash indicates that the protocol or application is not supported.

Table 38: Protocols and Applications Supported by the MX240, MX480, MX960, MX2010, and MX2020 MPCs

First Junos OS Release Supported by MPC Model Number (MPC Name)

MPC-3D-
16XGE-SFPP MX-MPC1- MX-MPC2- MX-MPC1- MX-MPC2- MX-MPC2-
3D 3D 3D-Q 3D-Q 3D-EQ
(16x10GE
Protocol or Application MPC) (MPC1) (MPC2) (MPC1 Q) (MPC2 Q) (MPC2 EQ)

Access Node Control Protocol – 10.2 10.2 10.2 10.2 10.2

(ANCP)

Accepts traffic destined for GRE 10.0R2 10.2 10.1 10.2 10.1 10.1
tunnels or DVMRP (IP-in-IP)
tunnels

Active-active bridging in 13.1 13.1 13.1 13.1 13.1 13.1

multichassis link aggregation

Bidirectional Forwarding 10.0R2 10.2 10.1 10.2 10.1 10.1

Detection protocol (BFD)

Border Gateway Protocol (BGP) 10.0R2 10.2 10.1 10.2 10.1 10.1

BGP/Multiprotocol Label 10.0R2 10.2 10.1 10.2 10.1 10.1

Switching (MPLS) virtual private
networks (VPNs)

Distance Vector Multicast Routing 10.0R2 10.2 10.1 10.2 10.1 10.1
Protocol (DVMRP) and generic
routing encapsulation (GRE)
support—access side and server
side

Distributed denial-of-service 11.2 11.2 11.2 11.2 11.2

(DDoS) protection

IEEE 802.1ag Ethernet OAM 10.2 10.2 10.2 10.2 10.2 10.2
Continuity Check protocol
(bridge family (bridge (bridge (bridge (bridge (bridge
supported in family family family family family
10.4) supported supported in supported supported in supported in
in 10.4) 10.4) in 10.4) 10.4) 10.4)

IEEE 802.1ag Ethernet OAM 10.2 10.2 10.2 10.2 10.2 10.2
Linktrace protocol
(bridge family (bridge (bridge (bridge (bridge (bridge
supported in family family family family family
10.4) supported supported in supported supported in supported in
in 10.4) 10.4) in 10.4) 10.4) 10.4)

320 Copyright © 2018, Juniper Networks, Inc.

 Chapter 16: MPC Protocol and Application Support for MX240, MX480, MX960, MX2010, MX2020, and MX10003

Table 38: Protocols and Applications Supported by the MX240, MX480, MX960, MX2010, and MX2020
MPCs (continued)

First Junos OS Release Supported by MPC Model Number (MPC Name)

MPC-3D-
16XGE-SFPP MX-MPC1- MX-MPC2- MX-MPC1- MX-MPC2- MX-MPC2-
3D 3D 3D-Q 3D-Q 3D-EQ
(16x10GE
Protocol or Application MPC) (MPC1) (MPC2) (MPC1 Q) (MPC2 Q) (MPC2 EQ)

IEEE 802.1ag Ethernet OAM 10.2 10.2 10.2 10.2 10.2 10.2
Loopback protocol
(bridge family (bridge (bridge (bridge (bridge (bridge
supported in family family family family family
10.4) supported supported in supported supported in supported in
in 10.4) 10.4) in 10.4) 10.4) 10.4)

Firewall filters 10.0R2 10.2 10.1 10.2 10.1 10.1

Flexible Ethernet encapsulation 10.0R2 10.2 10.1 10.2 10.1 10.1

Graceful Routing Engine 10.0R2 10.2 10.1 10.2 10.1 10.1

Switchover (GRES)

Ingress Differentiated Services 10.0R2 10.2 10.1 10.2 10.1 10.1

code point (DSCP) rewrite

Ingress hierarchical 12.1R3 12.1R3 12.1R3 12.1R3 12.1R3 12.1R3

quality-of-service (HQoS)
shaping and scheduling:

• Group of virtual LANs (VLANs)

level
• Virtual LAN (VLAN) level
• Port level

Intelligent oversubscription 10.0R2 10.2 10.1 10.2 10.1 10.1

Integrated routing and bridging 10.1 10.2 10.1 10.2 10.1 10.1
(IRB)

Intermediate 10.0R2 10.2 10.1 10.2 10.1 10.1

System-to-Intermediate System
(IS-IS)

Internet Group Management 10.0R2 10.2 10.1 10.2 10.1 10.1

Protocol (IGMP) (excluding
snooping)

Internet Group Management 11.4 11.4 11.4 11.4 11.4 11.4

Protocol (IGMP) snooping

IPv4 10.0R2 10.2 10.1 10.2 10.1 10.1

Copyright © 2018, Juniper Networks, Inc. 321

MX Series Interface Module Reference

Table 38: Protocols and Applications Supported by the MX240, MX480, MX960, MX2010, and MX2020
MPCs (continued)

First Junos OS Release Supported by MPC Model Number (MPC Name)

MPC-3D-
16XGE-SFPP MX-MPC1- MX-MPC2- MX-MPC1- MX-MPC2- MX-MPC2-
3D 3D 3D-Q 3D-Q 3D-EQ
(16x10GE
Protocol or Application MPC) (MPC1) (MPC2) (MPC1 Q) (MPC2 Q) (MPC2 EQ)

IP multicast 10.0R2 10.2 10.1 10.2 10.1 10.1

IPv6 10.2 10.2 10.2 10.2 10.2 10.2

IPv6 MLD 10.2 10.2 10.2 10.2 10.2 10.2

IPv6 multicast 10.2 10.2 10.2 10.2 10.2 10.2

IPv6 Neighbor Discovery 10.2 10.2 10.2 10.2 10.2 10.2

Label Distribution Protocol (LDP) 10.0R2 10.2 10.1 10.2 10.1 10.1

Labeled switched paths (LSPs) 10.0R2 10.2 10.1 10.2 10.1 10.1
including accounting, policers, and
filtering

LAN-PHY mode 10.0R2 10.2 10.1 10.2 10.1 10.1

Layer 2 frame filtering 10.0R2 10.2 10.1 10.2 10.1 10.1

Layer 2 Tunneling Protocol

(L2TP):

(MX2010, MX2020: 12.3R4, 13.2R2,

13.3)

• L2TP access concentrator 10.4 10.4 10.4 10.4 10.4 10.4

(LAC)

• L2TP network server (LNS) 11.4 11.4 11.4 11.4 11.4 11.4

• LNS inline service support with 11.4 11.4 11.4 11.4 11.4 11.4
CoS per-session shaping

• LNS inline service support 11.4 11.4 11.4 11.4 11.4 11.4
without CoS per-session
shaping

• Peer interface – 11.4 11.4 11.4 11.4 11.4

• Inline IP reassembly 13.1 13.1 13.1 13.1 13.1 13.1

IEEE 802.3ad link aggregation 10.0R2 10.2 10.1 10.2 10.1 10.1

322 Copyright © 2018, Juniper Networks, Inc.

 Chapter 16: MPC Protocol and Application Support for MX240, MX480, MX960, MX2010, MX2020, and MX10003

Table 38: Protocols and Applications Supported by the MX240, MX480, MX960, MX2010, and MX2020
MPCs (continued)

First Junos OS Release Supported by MPC Model Number (MPC Name)

MPC-3D-
16XGE-SFPP MX-MPC1- MX-MPC2- MX-MPC1- MX-MPC2- MX-MPC2-
3D 3D 3D-Q 3D-Q 3D-EQ
(16x10GE
Protocol or Application MPC) (MPC1) (MPC2) (MPC1 Q) (MPC2 Q) (MPC2 EQ)

Link Aggregation Control Protocol 10.0R2 10.2 10.1 10.2 10.1 10.1
(LACP)

Local loopback 10.0R2 10.2 10.1 10.2 10.1 10.1

MAC learning, policing, 10.0R2 10.2 10.1 10.2 10.1 10.1

accounting, and filtering

Mobile IP – – – – – –

Multi-chassis link aggregation 11.1 11.1 11.1 11.1 11.1 11.1

Multiple Tag Protocol Identifiers 10.0R2 10.2 10.1 10.2 10.1 10.1
(TPIDs)

Multiprotocol Label Switching 10.0R2 10.2 10.1 10.2 10.1 10.1

(MPLS)

Nonstop active routing (NSR) 10.0R2 10.2 10.1 10.2 10.1 10.1

IEEE 802.3ah OAM 11.1 11.1 11.1 11.1 11.1 11.1

• Discovery and link monitoring

• Fault signaling and detection
• Remote loopback

Multi-topology routing (MTR) 10.0R2 10.2 10.1 10.2 10.1 10.1

Open Shortest Path First (OSPF) 10.0R2 10.2 10.1 10.2 10.1 10.1

Packet mirroring 10.0R2 10.2 10.1 10.2 10.1 10.1

IEEE 802.1ah provider backbone – – – – – –

bridges (PBB)

Copyright © 2018, Juniper Networks, Inc. 323

MX Series Interface Module Reference

Table 38: Protocols and Applications Supported by the MX240, MX480, MX960, MX2010, and MX2020
MPCs (continued)

First Junos OS Release Supported by MPC Model Number (MPC Name)

MPC-3D-
16XGE-SFPP MX-MPC1- MX-MPC2- MX-MPC1- MX-MPC2- MX-MPC2-
3D 3D 3D-Q 3D-Q 3D-EQ
(16x10GE
Protocol or Application MPC) (MPC1) (MPC2) (MPC1 Q) (MPC2 Q) (MPC2 EQ)

Quality of service (QoS) per port: 10.0R2 10.2 10.1 10.2 10.1 10.1

• Eight queues per port

• Excess-rate configuration at
the traffic-control-profile level
• Excess-rate and excess-priority
configuration at the queue level
• Shaping at port level
• Shaping at queue level
• Scheduling of queues based on
weighted round-robin (WRR)
per priority class
• Tricolor marking
• Weighted random early
detection (WRED)

Quality of service (QoS) per

virtual LAN (VLAN):

• Accounting, filtering, and 10.0R2 10.2 10.1 10.2 10.1 10.1

policing

• IEEE 802.1p rewrite 10.0R2 10.2 10.1 10.2 10.1 10.1

• Classification 10.0R2 10.2 10.1 10.2 10.1 10.1

• Excess-rate configuration at – – – 10.2 10.1 10.1

the traffic-control-profile level

• Excess-rate and excess-priority – – – 10.2 10.1 10.1

configuration at the queue level

• Tricolor marking 10.0R2 10.2 10.1 10.2 10.1 10.1

• Shaping at the queue level – – – 10.2 10.1 10.1

• Scheduling of queues based on – – – 10.2 10.1 10.1

weighted round-robin (WRR)
per priority class

• Weighted random early – – – 10.2 10.1 10.1

detection (WRED)

324 Copyright © 2018, Juniper Networks, Inc.

 Chapter 16: MPC Protocol and Application Support for MX240, MX480, MX960, MX2010, MX2020, and MX10003

Table 38: Protocols and Applications Supported by the MX240, MX480, MX960, MX2010, and MX2020
MPCs (continued)

First Junos OS Release Supported by MPC Model Number (MPC Name)

MPC-3D-
16XGE-SFPP MX-MPC1- MX-MPC2- MX-MPC1- MX-MPC2- MX-MPC2-
3D 3D 3D-Q 3D-Q 3D-EQ
(16x10GE
Protocol or Application MPC) (MPC1) (MPC2) (MPC1 Q) (MPC2 Q) (MPC2 EQ)

Quality of service (QoS) per

Point-to-Point Protocol over
Ethernet (PPPoE) or Dynamic
Host Configuration Protocol
(DHCP) subscriber interfaces:

• Accounting, filtering, and – 10.2 10.1 10.2 10.1 10.1

policing

• IEEE 802.1p rewrite – 10.2 10.1 10.2 10.1 10.1

• Classification – 10.2 10.1 10.2 10.1 10.1

• Excess-rate configuration at – – – 10.2 10.1 10.1

the traffic-control-profile level

• Excess-rate and excess-priority – – – 10.2 10.1 10.1

configuration at the queue level

• Tricolor marking – 10.2 10.1 10.2 10.1 10.1

• Shaping at the queue level – – – 10.2 10.1 10.1

• Scheduling of queues based on – – – 10.2 10.1 10.1

weighted round-robin (WRR)
per priority class

• Weighted random early – – – 10.2 10.1 10.1

detection (WRED)

RSVP 10.0R2 10.2 10.1 10.2 10.1 10.1

RIP 10.0R2 10.2 10.1 10.2 10.1 10.1

SNMP 10.0R2 10.2 10.1 10.2 10.1 10.1

Copyright © 2018, Juniper Networks, Inc. 325

MX Series Interface Module Reference

Table 38: Protocols and Applications Supported by the MX240, MX480, MX960, MX2010, and MX2020
MPCs (continued)

First Junos OS Release Supported by MPC Model Number (MPC Name)

MPC-3D-
16XGE-SFPP MX-MPC1- MX-MPC2- MX-MPC1- MX-MPC2- MX-MPC2-
3D 3D 3D-Q 3D-Q 3D-EQ
(16x10GE
Protocol or Application MPC) (MPC1) (MPC2) (MPC1 Q) (MPC2 Q) (MPC2 EQ)

Spanning Tree Protocols: 10.2 10.2 10.2 10.2 10.2 10.2

• IEEE 802.1D Spanning Tree

Protocol (STP)
• IEEE 802.1s Multiple Spanning
Tree Protocol
• Per-VLAN Spanning Tree
(PVST)+
• IEEE 802.1w Rapid Spanning
Tree Protocol (RSTP)

Subscriber management and

services:

(MX2010, MX2020: 12.3R4, 13.2R2,

13.3)

• Aggregated Ethernet over static – 10.2 10.1 10.2 10.1 10.1

VLANs

• Aggregated Ethernet over – 10.2 10.2 10.2 10.2 10.2

dynamic VLANs

Access Node Control Protocol – 10.2 10.2 10.2 10.2 10.2

(ANCP) and ANCP agent

• DHCP access model – 10.2 10.1 10.2 10.1 10.1

• Dynamic adjustment of shapers – 10.2 10.1 10.2 10.1 10.1

• Dynamic PPPoE subscriber – 10.2 10.1 10.2 10.1 10.1

interface creation based on
PPPoE service name table
configuration

• Dynamic profiles – 10.2 10.1 10.2 10.1 10.1

• Dynamic shaping, scheduling, – 10.2 10.1 10.2 10.1 10.1

and queuing

• Dynamic VLANs – 10.2 10.2 10.2 10.2 10.2

• Static and dynamic PPPoE – 10.2 10.1 10.2 10.1 10.1

subscriber interfaces

326 Copyright © 2018, Juniper Networks, Inc.

 Chapter 16: MPC Protocol and Application Support for MX240, MX480, MX960, MX2010, MX2020, and MX10003

Table 38: Protocols and Applications Supported by the MX240, MX480, MX960, MX2010, and MX2020
MPCs (continued)

First Junos OS Release Supported by MPC Model Number (MPC Name)

MPC-3D-
16XGE-SFPP MX-MPC1- MX-MPC2- MX-MPC1- MX-MPC2- MX-MPC2-
3D 3D 3D-Q 3D-Q 3D-EQ
(16x10GE
Protocol or Application MPC) (MPC1) (MPC2) (MPC1 Q) (MPC2 Q) (MPC2 EQ)

Synchronous Ethernet (SyncE) 11.2R4 12.3 with 12.3 with 12.3 with 12.3 with 12.3 with
SCBE and SCBE and SCBE and SCBE and SCBE and
later later later later later

Tunnel services: 10.0R2 10.2 10.1 10.2 10.1 10.1

• GRE unicast
tunneling-Supports GRE
fragmentation
• IP-IP unicast tunneling
• Multicast tunneling
• Protocol Independent Multicast
(PIM) sparse mode unicast
tunneling
• Virtual loopback tunneling (VT)

Two-Way Active Measurement 10.0R2 10.2 10.1 10.2 10.1 10.1

Protocol (TWAMP)

IEEE 802.1Q VLANs: 10.0R2 10.2 10.1 10.2 10.1 10.1

• VLAN stacking and rewriting

• Channels defined by two
stacked VLAN tags
• Flexible VLAN tagging
• IP service for nonstandard TPID
and stacked VLAN tags

Virtual Chassis redundancy 11.2 11.2 11.2 11.2 11.2 11.2

Virtual private LAN service (VPLS) 10.0R2 10.2 10.1 10.2 10.1 10.1

Virtual private network (VPN) 10.0R2 10.2 10.1 10.2 10.1 10.1

Virtual Router Redundancy 10.0R2 10.2 10.1 10.2 10.1 10.1

Protocol (VRRP) for IPv4

VRRP over integrated routing and 13.1 13.1 13.1 13.1 13.1 13.1
bridging (IRB) on multichassis link
aggregation

WAN-PHY mode – 10.2 10.2 10.2 10.2 10.2

Copyright © 2018, Juniper Networks, Inc. 327

MX Series Interface Module Reference

Related • MX Series MPC Overview on page 11

Documentation
• MPCs Supported by MX Series Routers on page 12

• ANCP and the ANCP Agent Overview

• Understanding BGP

• Understanding MPLS Inter-AS Link Protection

• IEEE 802.1ag OAM Connectivity Fault Management Overview

• Understanding IGMP

• Understanding IPv6

• Understanding LDP-IGP Synchronization

• mc-ae

Protocols and Applications Supported on the MPC1E for MX Series Routers

Table 39 on page 328 contains the first Junos OS Release support for protocols and
applications on the MX240, MX480, MX960, MX2010, and MX2020 Enhanced MPCs
(MPCEs).

NOTE: The MX2010 and M2020 routers support protocols and applications
in Junos OS 12.3 and later. Features added after the Junos OS 12.3 release are
supported on the MX2010 and MX2020 routers in the release indicated.

A dash indicates that the protocol or application is not supported.

Table 39: Protocols and Applications Supported by the MX240, MX480, MX960, MX2010, and MX2020 Enhanced
MPCs (MPC1Es)

First Junos OS Release Supported by MPC1E Model Number (MPCE Name)

MX-MPC1E-3D MX-MPC1E-3D-Q

Protocol or Application (MPC1E) (MPC1E Q)

Access Node Control Protocol (ANCP) 11.2R4 11.2R4

Accepts traffic destined for GRE tunnels or DVMRP (IP-in-IP) tunnels 11.2R4 11.2R4

Bidirectional Forwarding Detection protocol (BFD) 11.2R4 11.2R4

Border Gateway Protocol (BGP) 11.2R4 11.2R4

BGP/Multiprotocol Label Switching (MPLS) virtual private networks 11.2R4 11.2R4

(VPNs)

328 Copyright © 2018, Juniper Networks, Inc.

 Chapter 16: MPC Protocol and Application Support for MX240, MX480, MX960, MX2010, MX2020, and MX10003

Table 39: Protocols and Applications Supported by the MX240, MX480, MX960, MX2010, and MX2020 Enhanced
MPCs (MPC1Es) (continued)

First Junos OS Release Supported by MPC1E Model Number (MPCE Name)

MX-MPC1E-3D MX-MPC1E-3D-Q

Protocol or Application (MPC1E) (MPC1E Q)

Distance Vector Multicast Routing Protocol (DVMRP) and generic routing 11.2R4 11.2R4
encapsulation (GRE) support—access side and server side

IEEE 802.1ag Ethernet OAM Continuity Check protocol 11.2R4 11.2R4

IEEE 802.1ag Ethernet OAM Linktrace protocol 11.2R4 11.2R4

IEEE 802.1ag Ethernet OAM Loopback protocol 11.2R4 11.2R4

Firewall filters 11.2R4 11.2R4

Flexible Ethernet encapsulation 11.2R4 11.2R4

Graceful Routing Engine Switchover (GRES) 11.2R4 11.2R4

Ingress Differentiated Services code point (DSCP) rewrite 11.2R4 11.2R4

Hierarchical quality-of-service (HQoS) - 12.1R3

Intelligent oversubscription 11.2R4 11.2R4

Integrated routing and bridging (IRB) 11.2R4 11.2R4

Intermediate System-to-Intermediate System (IS-IS) 11.2R4 11.2R4

Internet Group Management Protocol (IGMP) (excluding snooping) 11.2R4 11.2R4

Internet Group Management Protocol (IGMP) snooping 11.2R4 11.2R4

IPv4 11.2R4 11.2R4

IP multicast 11.2R4 11.2R4

IPv6 11.2R4 11.2R4

IPv6 MLD 11.2R4 11.2R4

IPv6 multicast 11.2R4 11.2R4

IPv6 Neighbor Discovery 11.2R4 11.2R4

Label Distribution Protocol (LDP) 11.2R4 11.2R4

Copyright © 2018, Juniper Networks, Inc. 329

MX Series Interface Module Reference

Table 39: Protocols and Applications Supported by the MX240, MX480, MX960, MX2010, and MX2020 Enhanced
MPCs (MPC1Es) (continued)

First Junos OS Release Supported by MPC1E Model Number (MPCE Name)

MX-MPC1E-3D MX-MPC1E-3D-Q

Protocol or Application (MPC1E) (MPC1E Q)

Labeled switched paths (LSPs) including accounting, policers, and filtering 11.2R4 11.2R4

LAN-PHY mode 11.2R4 11.2R4

Layer 2 frame filtering 11.2R4 11.2R4

Layer 2 Tunneling Protocol (L2TP):

• L2TP access concentrator (LAC) 11.3 11.3

• L2TP network server (LNS) 11.4 11.4

• LNS inline service support with CoS per-session shaping 11.4 11.4

• LNS inline service support without CoS per-session shaping 11.4 11.4

• Peer interface 11.4 11.4

• Inline IP Reassembly 13.1 13.1

IEEE 802.3ad link aggregation 11.2R4 11.2R4

Link Aggregation Control Protocol (LACP) 11.2R4 11.2R4

Local loopback 11.2R4 11.2R4

MAC learning, policing, accounting, and filtering 11.2R4 11.2R4

Mobile IP – –

Multi-chassis link aggregation 11.2R4 11.2R4

Multiple Tag Protocol Identifiers (TPIDs) 11.2R4 11.2R4

Multiprotocol Label Switching (MPLS) 11.2R4 11.2R4

Nonstop active routing (NSR) 11.2R4 11.2R4

IEEE 802.3ah OAM 11.2R4 11.2R4

• Discovery and link monitoring

• Fault signaling and detection
• Remote loopback

330 Copyright © 2018, Juniper Networks, Inc.

 Chapter 16: MPC Protocol and Application Support for MX240, MX480, MX960, MX2010, MX2020, and MX10003

Table 39: Protocols and Applications Supported by the MX240, MX480, MX960, MX2010, and MX2020 Enhanced
MPCs (MPC1Es) (continued)

First Junos OS Release Supported by MPC1E Model Number (MPCE Name)

MX-MPC1E-3D MX-MPC1E-3D-Q

Protocol or Application (MPC1E) (MPC1E Q)

Multitopology routing 11.2R4 11.2R4

OSPF 11.2R4 11.2R4

Packet mirroring 11.2R4 11.2R4

Per-unit scheduling 12.1R3 12.1R3

Precision Time Protocol (PTP) or IEEE 1588v2 12.3 12.3

IEEE 802.1ah provider backbone bridges (PBB) 11.2R4 11.2R4

Quality of service (QoS) per port: 11.2R4 11.2R4

• Eight queues per port

• Excess-rate configuration at the traffic-control-profile level
• Excess-rate and excess-priority configuration at the queue level
• Shaping at port level
• Shaping at queue level
• Scheduling of queues based on weighted round-robin (WRR) per priority
class
• Tricolor marking
• Weighted random early detection (WRED)

Quality of service (QoS) per virtual LAN (VLAN):

• Accounting, filtering, and policing 11.2R4 11.2R4

• IEEE 802.1p rewrite 11.2R4 11.2R4

• Classification 11.2R4 11.2R4

• Excess-rate configuration at the traffic-control-profile level – 11.2R4

• Excess-rate and excess-priority configuration at the queue level – 11.2R4

• Tricolor marking 11.2R4 11.2R4

• Shaping at the queue level – 11.2R4

• Scheduling of queues based on weighted round-robin (WRR) per priority – 11.2R4

class

Copyright © 2018, Juniper Networks, Inc. 331

MX Series Interface Module Reference

Table 39: Protocols and Applications Supported by the MX240, MX480, MX960, MX2010, and MX2020 Enhanced
MPCs (MPC1Es) (continued)

First Junos OS Release Supported by MPC1E Model Number (MPCE Name)

MX-MPC1E-3D MX-MPC1E-3D-Q

Protocol or Application (MPC1E) (MPC1E Q)

• Weighted random early detection (WRED) – 11.2R4

Quality of service (QoS) per Point-to-Point Protocol over Ethernet (PPPoE)

or Dynamic Host Configuration Protocol (DHCP) subscriber interfaces:

• Accounting, filtering, and policing 11.2R4 11.2R4

• IEEE 802.1p rewrite 11.2R4 11.2R4

• Classification 11.2R4 11.2R4

• Excess-rate configuration at the traffic-control-profile level – 11.2R4

• Excess-rate and excess-priority configuration at the queue level – 11.2R4

• Tricolor marking 11.2R4 11.2R4

• Shaping at the queue level – 11.2R4

• Scheduling of queues based on weighted round-robin (WRR) per priority – 11.2R4

class

• Weighted random early detection (WRED) – 11.2R4

RSVP 11.2R4 11.2R4

RIP 11.2R4 11.2R4

SNMP 11.2R4 11.2R4

Spanning Tree Protocols: 11.2R4 11.2R4

• IEEE 802.1D Spanning Tree Protocol (STP)

• IEEE 802.1s Multiple Spanning Tree Protocol
• Per-VLAN Spanning Tree (PVST)+
• IEEE 802.1w Rapid Spanning Tree Protocol (RSTP)

Subscriber Management:

• Aggregated Ethernet over static VLANs 11.2R4 11.2R4

• Aggregated Ethernet over dynamic VLANs 11.2R4 11.2R4

332 Copyright © 2018, Juniper Networks, Inc.

 Chapter 16: MPC Protocol and Application Support for MX240, MX480, MX960, MX2010, MX2020, and MX10003

Table 39: Protocols and Applications Supported by the MX240, MX480, MX960, MX2010, and MX2020 Enhanced
MPCs (MPC1Es) (continued)

First Junos OS Release Supported by MPC1E Model Number (MPCE Name)

MX-MPC1E-3D MX-MPC1E-3D-Q

Protocol or Application (MPC1E) (MPC1E Q)

• DHCP access model 11.2R4 11.2R4

• Dynamic adjustment of shapers 11.2R4 11.2R4

• Dynamic PPPoE subscriber interface creation based on PPPoE service 11.2R4 11.2R4
name table configuration

• Dynamic profiles 11.2R4 11.2R4

• Dynamic shaping, scheduling, and queuing 11.2R4 11.2R4

• Dynamic VLANs 11.2R4 11.2R4

• Enhanced subscriber management 15.1R4 15.1R4

• Static and dynamic PPPoE subscriber interfaces 11.2R4 11.2R4

Synchronous Ethernet (SyncE) 11.2R4 11.2R4

Tunnel services: 11.2R4 11.2R4

• Clear DF-Bit (Don't Fragment Bit)

• GRE unicast tunneling-Supports GRE fragmentation
• IP-IP unicast tunneling
• Multicast tunneling
• Protocol Independent Multicast (PIM) sparse mode unicast tunneling
• Virtual loopback tunneling (VT)

Two-Way Active Measurement Protocol (TWAMP) 11.2R4 11.2R4

IEEE 802.1Q VLANs: 11.2R4 11.2R4

• VLAN stacking and rewriting

• Channels defined by two stacked VLAN tags
• Flexible VLAN tagging
• IP service for nonstandard TPID and stacked VLAN tags

Virtual Chassis redundancy 11.2R4 11.2R4

Virtual private LAN service (VPLS) 11.2R4 11.2R4

Virtual private network (VPN) 11.2R4 11.2R4

Copyright © 2018, Juniper Networks, Inc. 333

MX Series Interface Module Reference

Table 39: Protocols and Applications Supported by the MX240, MX480, MX960, MX2010, and MX2020 Enhanced
MPCs (MPC1Es) (continued)

First Junos OS Release Supported by MPC1E Model Number (MPCE Name)

MX-MPC1E-3D MX-MPC1E-3D-Q

Protocol or Application (MPC1E) (MPC1E Q)

Virtual Router Redundancy Protocol (VRRP) for IPv4 11.2R4 11.2R4

WAN-PHY mode 11.2R4 11.2R4

Related • MX Series MPC Overview on page 11

Documentation
• MPCs Supported by MX Series Routers on page 12

Protocols and Applications Supported by the MX240, MX480, MX960, MX2010, and
MX2020 MPC2E

Table 40 on page 334 contains the first Junos OS Release support for protocols and
applications on the MX240, MX480, MX960, MX2010, and MX2020 MPC2E.

A dash indicates that the protocol or application is not supported.

NOTE: The MX2010 and M2020 routers support protocols and applications
in Junos OS 12.3 and later. Features added after the Junos OS 12.3 release are
supported on the MX2010 and MX2020 routers in the release indicated.

A dash indicates that the protocol or application is not supported.

Table 40: Protocols and Applications Supported by the MX240, MX480, MX960, MX2010, and MX2020 MPC2E

First Supported Junos OS Release

MX-MPC2E-
MX-MPC2E- MX-MPC2E- MX-MPC2E- MX-MPC2E- MX-MPC2E- 3D-NG-Q
3D 3D-Q 3D-EQ 3D-P 3D-NG
(MPC2E
Protocol or Application (MPC2E) (MPC2E Q) (MPC2E EQ) (MPC2E P) (MPC2E NG) NG-Q)

Access Node Control 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

Protocol (ANCP)

334 Copyright © 2018, Juniper Networks, Inc.

 Chapter 16: MPC Protocol and Application Support for MX240, MX480, MX960, MX2010, MX2020, and MX10003

Table 40: Protocols and Applications Supported by the MX240, MX480, MX960, MX2010, and MX2020
MPC2E (continued)

First Supported Junos OS Release

MX-MPC2E-
MX-MPC2E- MX-MPC2E- MX-MPC2E- MX-MPC2E- MX-MPC2E- 3D-NG-Q
3D 3D-Q 3D-EQ 3D-P 3D-NG
(MPC2E
Protocol or Application (MPC2E) (MPC2E Q) (MPC2E EQ) (MPC2E P) (MPC2E NG) NG-Q)

Accepts traffic destined 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

for generic routing
encapsulation (GRE)
tunnels or Distance Vector
Multicast Routing
Protocol (DVMRP)
(IP-in-IP) tunnels

• Dynamic
• Manual

Bidirectional Forwarding 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

Detection protocol (BFD)

Border Gateway Protocol 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

(BGP)

BGP/MPLS virtual private 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

networks (VPNs)

DVMRP and GRE 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

support—access side and
server side

Dynamic Power — — — — 15.1 15.1

Management

Flexible Queuing Mode — — — — 15.1 —

NOTE: Flexible queuing

mode is supported only on
non-HQoS variants.

IEEE 802.1ag Ethernet 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

OAM Continuity Check
protocol

IEEE 802.1ag Ethernet 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

OAM Linktrace protocol

IEEE 802.1ag Ethernet 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

OAM Loopback protocol

Firewall filters 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

Copyright © 2018, Juniper Networks, Inc. 335

MX Series Interface Module Reference

Table 40: Protocols and Applications Supported by the MX240, MX480, MX960, MX2010, and MX2020
MPC2E (continued)

First Supported Junos OS Release

MX-MPC2E-
MX-MPC2E- MX-MPC2E- MX-MPC2E- MX-MPC2E- MX-MPC2E- 3D-NG-Q
3D 3D-Q 3D-EQ 3D-P 3D-NG
(MPC2E
Protocol or Application (MPC2E) (MPC2E Q) (MPC2E EQ) (MPC2E P) (MPC2E NG) NG-Q)

Flexible Ethernet 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

encapsulation

Graceful Routing Engine 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

Switchover (GRES)

Ingress Differentiated 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

Services code point
(DSCP) rewrite

Ingress hierarchical – – – – 15.1R1 15.1R1

quality-of-service (HQoS)
shaping and
hierarchical-scheduler:

• Group of virtual LANs

(VLANs) level
• Virtual LAN (VLAN)
level
• Port level

Hierarchical – 12.1R3 12.1R3 – - 15.1R1

quality-of-service (HQoS)

Intelligent 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

Oversubscription on MIC
and MPC Interfaces
Overview

Integrated routing and 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

bridging (IRB)

Unified In-service software 17.1R1 17.1R1

upgrade (Unified ISSU)

IS-IS 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

Internet Group 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

Management Protocol
(IGMP) (excluding
snooping)

336 Copyright © 2018, Juniper Networks, Inc.

 Chapter 16: MPC Protocol and Application Support for MX240, MX480, MX960, MX2010, MX2020, and MX10003

Table 40: Protocols and Applications Supported by the MX240, MX480, MX960, MX2010, and MX2020
MPC2E (continued)

First Supported Junos OS Release

MX-MPC2E-
MX-MPC2E- MX-MPC2E- MX-MPC2E- MX-MPC2E- MX-MPC2E- 3D-NG-Q
3D 3D-Q 3D-EQ 3D-P 3D-NG
(MPC2E
Protocol or Application (MPC2E) (MPC2E Q) (MPC2E EQ) (MPC2E P) (MPC2E NG) NG-Q)

Internet Group 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

Management Protocol
(IGMP) snooping

IPv4 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

IP multicast 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

IPv6 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

IPv6 MLD 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

IPv6 multicast 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

IPv6 Neighbor Discovery 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

Label Distribution 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

Protocol (LDP)

Labeled-switched-paths 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

(LSPs) including
accounting, policers, and
filtering

LAN-PHY mode 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

Layer 2 frame filtering 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

Layer 2 Tunneling 14.1R4 14.1R4

Protocol (L2TP):

• L2TP access 11.3 11.3 11.3 12.2 14.1R4 14.1R4

concentrator (LAC)

• L2TP network server 11.4 11.4 11.4 12.2 14.1R4 14.1R4

(LNS)

• LNS inline service 11.4 11.4 11.4 12.2 14.1R4 14.1R4

support with CoS
per-session shaping

Copyright © 2018, Juniper Networks, Inc. 337

MX Series Interface Module Reference

Table 40: Protocols and Applications Supported by the MX240, MX480, MX960, MX2010, and MX2020
MPC2E (continued)

First Supported Junos OS Release

MX-MPC2E-
MX-MPC2E- MX-MPC2E- MX-MPC2E- MX-MPC2E- MX-MPC2E- 3D-NG-Q
3D 3D-Q 3D-EQ 3D-P 3D-NG
(MPC2E
Protocol or Application (MPC2E) (MPC2E Q) (MPC2E EQ) (MPC2E P) (MPC2E NG) NG-Q)

• LNS inline service 11.4 11.4 11.4 12.2 14.1R4 14.1R4

support without CoS
per-session shaping

• Peer interface 11.4 11.4 11.4 12.2 14.1R4 14.1R4

• Inline IP Reassembly 13.1 13.1 13.1 13.1 14.1R4 14.1R4

Link aggregation (IEEE 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

802.3ad)

Link Aggregation Control 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

Protocol (LACP)

Local loopback 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

MAC learning, policing, 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

accounting, and filtering

Mobile IP – – – –

Multi-chassis link 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

aggregation

Multiple Tag Protocol 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

Identifiers (TPIDs)

Multiprotocol Label 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

Switching (MPLS)

Nonstop active routing 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

(NSR)

IEEE 802.3ah OAM 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

• Discovery and link

monitoring
• Fault signaling and
detection
• Remote loopback

Multitopology routing 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

338 Copyright © 2018, Juniper Networks, Inc.

 Chapter 16: MPC Protocol and Application Support for MX240, MX480, MX960, MX2010, MX2020, and MX10003

Table 40: Protocols and Applications Supported by the MX240, MX480, MX960, MX2010, and MX2020
MPC2E (continued)

First Supported Junos OS Release

MX-MPC2E-
MX-MPC2E- MX-MPC2E- MX-MPC2E- MX-MPC2E- MX-MPC2E- 3D-NG-Q
3D 3D-Q 3D-EQ 3D-P 3D-NG
(MPC2E
Protocol or Application (MPC2E) (MPC2E Q) (MPC2E EQ) (MPC2E P) (MPC2E NG) NG-Q)

OSPF 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

Packet mirroring 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

Precision Time Protocol 12.3 12.3 12.3 12.2 15.1R2 15.1R2

(PTP) or IEEE 1588v2

IEEE 802.1ah provider – – – – – –

backbone bridges (PBB)

Quality of service (QoS) 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

per port:

• Eight queues per port

• Excess-rate
configuration at the
traffic-control-profile
level
• Excess-rate and
excess-priority
configuration at the
queue level
• Shaping at port level
• Shaping at queue level
• Scheduling of queues
based on weighted
round-robin (WRR) per
priority class
• Tricolor marking
• Weighted random early
detection (WRED)

Quality of service (QoS) – 14.1R4 14.1R4

per virtual LAN (VLAN):

• Accounting, filtering, 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

and policing

• IEEE 802.1p rewrite 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

• Classification 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

Copyright © 2018, Juniper Networks, Inc. 339

MX Series Interface Module Reference

Table 40: Protocols and Applications Supported by the MX240, MX480, MX960, MX2010, and MX2020
MPC2E (continued)

First Supported Junos OS Release

MX-MPC2E-
MX-MPC2E- MX-MPC2E- MX-MPC2E- MX-MPC2E- MX-MPC2E- 3D-NG-Q
3D 3D-Q 3D-EQ 3D-P 3D-NG
(MPC2E
Protocol or Application (MPC2E) (MPC2E Q) (MPC2E EQ) (MPC2E P) (MPC2E NG) NG-Q)

• Excess-rate – 11.2R4 11.2R4 12.2 14.1R4 14.1R4

configuration at the
traffic-control-profile
level

• Excess-rate and – 11.2R4 11.2R4 12.2 14.1R4 14.1R4

excess-priority
configuration at the
queue level

• Tricolor marking 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

• Shaping at the queue – 11.2R4 11.2R4 12.2 14.1R4 14.1R4

level

• Scheduling of queues – 11.2R4 11.2R4 12.2 14.1R4 14.1R4

based on weighted
round-robin (WRR) per
priority class

• Weighted random early – 11.2R4 11.2R4 12.2 14.1R4 14.1R4

detection (WRED)

Quality of service (QoS) 14.1R4 14.1R4

per Point-to-Point
Protocol over Ethernet
(PPPoE) or Dynamic Host
Configuration Protocol
(DHCP) subscriber
interfaces:

• Accounting, filtering, 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

and policing

• IEEE 802.1p rewrite 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

• Classification 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

• Excess-rate – 11.2R4 11.2R4 12.2 14.1R4 14.1R4

configuration at the
traffic-control-profile
level

340 Copyright © 2018, Juniper Networks, Inc.

 Chapter 16: MPC Protocol and Application Support for MX240, MX480, MX960, MX2010, MX2020, and MX10003

Table 40: Protocols and Applications Supported by the MX240, MX480, MX960, MX2010, and MX2020
MPC2E (continued)

First Supported Junos OS Release

MX-MPC2E-
MX-MPC2E- MX-MPC2E- MX-MPC2E- MX-MPC2E- MX-MPC2E- 3D-NG-Q
3D 3D-Q 3D-EQ 3D-P 3D-NG
(MPC2E
Protocol or Application (MPC2E) (MPC2E Q) (MPC2E EQ) (MPC2E P) (MPC2E NG) NG-Q)

• Excess-rate and – 11.2R4 11.2R4 12.2 14.1R4 14.1R4

excess-priority
configuration at the
queue level

• Tricolor marking 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

• Shaping at the queue – 11.2R4 11.2R4 12.2 14.1R4 14.1R4

level

• Scheduling of queues – 11.2R4 11.2R4 12.2 14.1R4 14.1R4

based on weighted
round-robin (WRR) per
priority class

• Weighted random early – 11.2R4 11.2R4 12.2 14.1R4 14.1R4

detection (WRED)

RSVP 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

RIP 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

SNMP 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

Spanning Tree Protocols: 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

• IEEE 802.1D Spanning

Tree Protocol (STP)
• IEEE 802.1s Multiple
Spanning Tree Protocol
• Per-VLAN Spanning
Tree (PVST)+
• IEEE 802.1w Rapid
Spanning Tree Protocol
(RSTP)

Subscriber Management: 14.1R4 14.1R4

• Aggregated Ethernet 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

over static VLANs

• Aggregated Ethernet 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

over dynamic VLANs

• DHCP access model 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

Copyright © 2018, Juniper Networks, Inc. 341

MX Series Interface Module Reference

Table 40: Protocols and Applications Supported by the MX240, MX480, MX960, MX2010, and MX2020
MPC2E (continued)

First Supported Junos OS Release

MX-MPC2E-
MX-MPC2E- MX-MPC2E- MX-MPC2E- MX-MPC2E- MX-MPC2E- 3D-NG-Q
3D 3D-Q 3D-EQ 3D-P 3D-NG
(MPC2E
Protocol or Application (MPC2E) (MPC2E Q) (MPC2E EQ) (MPC2E P) (MPC2E NG) NG-Q)

• Dynamic adjustment of 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

shapers

• Dynamic PPPoE 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

subscriber interface
creation based on
PPPoE service name
table configuration

• Dynamic profiles 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

• Dynamic shaping, 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

scheduling, and
queuing

• Dynamic VLANs 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

• Enhanced subscriber 15.1R4 15.1R4 15.1R4 15.1R4 15.1R4 15.1R4

management

• Static and dynamic 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

PPPoE subscriber
interfaces

Synchronous Ethernet 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

(SyncE)

Tunnel services: 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

• Clear DF-Bit (Don't

Fragment Bit)
• GRE unicast
tunneling-Supports
GRE fragmentation
• IP-IP unicast tunneling
• Multicast tunneling
• Protocol Independent
Multicast (PIM) sparse
mode unicast tunneling
• Virtual loopback
tunneling (VT)

Two-Way Active 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

Measurement Protocol
(TWAMP)

342 Copyright © 2018, Juniper Networks, Inc.

 Chapter 16: MPC Protocol and Application Support for MX240, MX480, MX960, MX2010, MX2020, and MX10003

Table 40: Protocols and Applications Supported by the MX240, MX480, MX960, MX2010, and MX2020
MPC2E (continued)

First Supported Junos OS Release

MX-MPC2E-
MX-MPC2E- MX-MPC2E- MX-MPC2E- MX-MPC2E- MX-MPC2E- 3D-NG-Q
3D 3D-Q 3D-EQ 3D-P 3D-NG
(MPC2E
Protocol or Application (MPC2E) (MPC2E Q) (MPC2E EQ) (MPC2E P) (MPC2E NG) NG-Q)

VLANs IEEE 802.1Q 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

• VLAN stacking and

rewriting
• Channels defined by
two stacked VLAN tags
• Flexible VLAN tagging
• IP service for
nonstandard TPID and
stacked VLAN tags

Virtual Chassis 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

redundancy

Virtual private LAN service 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4
(VPLS)

Virtual private network 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

(VPN)

Virtual Router Redundancy 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

Protocol (VRRP) for IPv4

WAN-PHY mode 11.2R4 11.2R4 11.2R4 12.2 14.1R4 14.1R4

Related • MX Series MPC Overview on page 11

Documentation
• MPCs Supported by MX Series Routers on page 12

Protocols and Applications Supported by the MPC3E on MX Series Routers

Table 41 on page 344 lists the first supported Junos OS Release for MPC3E protocols and
applications for the MX240, MX480, MX960, MX2010, and MX2020 routers. The protocols
and applications support feature parity with Junos OS Release 10.4.

NOTE: The MX2010 and M2020 routers support protocols and applications
in Junos OS 12.3 and later. Features added after the Junos OS 12.3 release are
supported on the MX2010 and MX2020 routers in the release indicated.

Copyright © 2018, Juniper Networks, Inc. 343

MX Series Interface Module Reference

A dash indicates that the protocol or application is not supported.

Table 41: Protocols and Applications Supported by MPC3E Cards for MX Series Routers

First Supported Junos OS Release

Protocol or Application MPC3E-3D MPC3E–3D-NG MPC3E–3D-NG-Q

Access Node Control Protocol (ANCP) — 14.1R4 14.1R4

Bidirectional Forwarding Detection protocol (BFD) 12.1 14.1R4 14.1R4

Border Gateway Protocol (BGP) 12.1 14.1R4 14.1R4

Bridge protocol data units (BPDUs) 12.2 14.1R4 14.1R4

BGP/MPLS virtual private networks (VPNs) 12.1 14.1R4 14.1R4

Class of service (CoS): 12.1 14.1R4 14.1R4

• Maintain CoS across internal tunnel interfaces

• Packet rewrites
• Rate limit option for per-port queues
• Configurable 802.1p inheritance: push and swap from the hidden tag
• Configurable shaping overhead for scheduling
• Behavior aggregate (BA) classification
• BA classification based on 802.1p of “payload” for core-facing VPLS
interfaces
• BA DSCP classification of MPLS packets for L3VPN/VPLS LSI and MPLS
interfaces
• BA DSCP classification for VPLS/CCC family

Class of service (CoS) per port: 12.1 14.1R4 14.1R4

• Eight queues per port

• Excess-rate and excess-priority configurations at the queue level
• Shaping at the port level
• Shaping at the queue level
• Scheduling of queues based on the weighted round-robin (WRR) per
excess-priority class
• Round-robin scheduling of the queues per priority class
• Weighted random early detection (WRED)

NOTE: Fine-grained queuing and input queuing are not supported for the
MPC3E-3D.

Class of service (CoS) per virtual LAN (VLAN): 12.1 14.1R4 14.1R4

• Accounting, filtering, and policing

• IEEE 802.1p rewrite
• Classification
• Tricolor marking

344 Copyright © 2018, Juniper Networks, Inc.

 Chapter 16: MPC Protocol and Application Support for MX240, MX480, MX960, MX2010, MX2020, and MX10003

Table 41: Protocols and Applications Supported by MPC3E Cards for MX Series Routers (continued)

First Supported Junos OS Release

Protocol or Application MPC3E-3D MPC3E–3D-NG MPC3E–3D-NG-Q

Class of service (CoS) per Point-to-Point Protocol over Ethernet (PPPoE) — 14.1R4 14.1R4
or Dynamic Host Configuration Protocol (DHCP) subscriber interfaces:

• Accounting, filtering, and policing

• IEEE 802.1p rewrite
• Classification
• Excess-rate and excess-priority configuration at the queue level
• Tricolor marking
• Shaping at the queue level
• Scheduling of queues based on weighted round-robin (WRR) per priority
class
• Weighted random early detection (WRED)

Distributed Denial-of-Service (DDoS) Protection 12.1 14.1R4 14.1R4

DVMRP and GRE support—access side and server side — 14.1R4 14.1R4

Dynamic Power Management 15.1 15.1 15.1

Push a tag on Ethernet VPLS and Ethernet CCC tag encapsulations — 14.1R4 14.1R4

Enhanced subscriber management 15.1R4 15.1R4 15.1R4

Ethernet Ring Protection Switching with multiple G.8032 instances — 14.1R4 14.1R4

Flexible Queuing Mode 15.1 15.1 15.1

NOTE: Flexible queuing mode is supported only on non-HQoS variants.

IEEE 802.1ag Ethernet OAM Continuity Check protocol 12.2 14.1R4 14.1R4

IEEE 802.1ag Ethernet OAM Linktrace protocol 12.2 14.1R4 14.1R4

IEEE 802.1ag Ethernet OAM Loopback protocol 12.2 14.1R4 14.1R4

IEEE 802.1ag Maintenance Association Intermediate Point (MIP) support, 12.2 14.1R4 14.1R4
continuity check message (CCM), stacked VLAN tagging, trunk ports,
support for VPLS/VPWS, VLAN circuit cross-connect (CCC) encapsulation
and translational cross-connect (TCC) encapsulation

IEEE 802.1ag Optional type, length, and value (TLVs) support Port Status — 14.1R4 14.1R4
TLV and Interface Status TLV

IEEE 802.3ah distributed periodic packet management (PPM) process , 12.2 14.1R4 14.1R4
alarm indication signal (AIS), and remote defect indication (RDI)

Copyright © 2018, Juniper Networks, Inc. 345

MX Series Interface Module Reference

Table 41: Protocols and Applications Supported by MPC3E Cards for MX Series Routers (continued)

First Supported Junos OS Release

Protocol or Application MPC3E-3D MPC3E–3D-NG MPC3E–3D-NG-Q

Firewall filters and policers: 12.1 14.1R4 14.1R4

• Policer support for aggregated Ethernet

• Aggregate firewall-based policer for all families of a logical interface
• Intelligent hierarchial policers

NOTE: Intelligent hierarchial policers are supported from Junos OS

Release 13.3.

• Set forwarding class and loss priority for Routing Engine-generated

packets by using a firewall
• Physical interface policers, applying policers to the entire port
• Lower policer limit from 32K to 8K
• Egress IEEE 802.1p multi-field (MF) and BA classification for VPLS
• Differentiated Services Code Point (DSCP) rewrite for IPv4 and IPv6

NOTE: The packet length used for the policer included in the Layer 2 header
is not supported for the MPC3E-3D in release 12.2.

Flexible Ethernet encapsulation 12.1 14.1R4 14.1R4

Generic Routing Encapsulation (GRE) tunnels or Distance Vector Multicast 12.1 14.1R4 14.1R4
Routing Protocol (DVMRP) (IP-in-IP) tunnels

• Dynamic
• Manual

Graceful Routing Engine Switchover (GRES) 12.1 14.1R4 14.1R4

Hierarchical Quality of Service (HQoS) — 14.1R4 14.1R4

IGMP snooping with bridging, IRB, and VPLS — 14.1R4 14.1R4

IGMPv3 support with snooping disabled 12.1 14.1R4 14.1R4

Ingress and egress hierarchical class-of-service (CoS) shaping and — 14.1R4 14.1R4
hierarchical-scheduler:

• Group of virtual LANs (VLANs) level

• VLAN level
• Port level

Inline flow monitoring 12.2 14.1R4 14.1R4

Intelligent Oversubscription on MIC and MPC Interfaces Overview 12.1 14.1R4 14.1R4

Integrated routing and bridging (IRB) 12.2 14.1R4 14.1R4

346 Copyright © 2018, Juniper Networks, Inc.

 Chapter 16: MPC Protocol and Application Support for MX240, MX480, MX960, MX2010, MX2020, and MX10003

Table 41: Protocols and Applications Supported by MPC3E Cards for MX Series Routers (continued)

First Supported Junos OS Release

Protocol or Application MPC3E-3D MPC3E–3D-NG MPC3E–3D-NG-Q

Unified In-service software upgrade (Unified ISSU) 13.3 17.1R1 17.1R1

Interoperability with MPCs and existing DPCs 12.1 14.1R4 14.1R4

Interoperability with multiservices DPCs 12.2 14.1R4 14.1R4

Interoperability with MX Series Flexible PIC Concentrators (MX-FPC) — 14.1R4 14.1R4

IPv4 12.1 14.1R4 14.1R4

IPv4 multicast 12.1 14.1R4 14.1R4

IPv6 12.1 14.1R4 14.1R4

IPv6 MLD 12.1 14.1R4 14.1R4

IPv6 multicast 12.1 14.1R4 14.1R4

IPv6 Neighbor Discovery 12.1 14.1R4 14.1R4

IS-IS 12.1 14.1R4 14.1R4

ITU-T Y.1731 timestamping support on MX Series routers — 14.1R4 14.1R4

Flow monitoring and services: 12.2 14.1R4 14.1R4

• Active monitoring (multiple v8 version j-flow templates)

• Active monitoring (cflowed version 9 templates)
• Port mirroring family VPLS, bridge CCC encapsulation (VPWS)
• Packet slice for port mirroring
• Inline flow monitoring on MPC3E
• Flow monitoring on multiservices DPCs

NOTE: Flow monitoring on Multiservices DPCs is not supported for the

MPC3E-3D in release 12.2..

Labeled-switched-paths (LSPs) including accounting, policers, and filtering 12.1 14.1R4 14.1R4

Copyright © 2018, Juniper Networks, Inc. 347

MX Series Interface Module Reference

Table 41: Protocols and Applications Supported by MPC3E Cards for MX Series Routers (continued)

First Supported Junos OS Release

Protocol or Application MPC3E-3D MPC3E–3D-NG MPC3E–3D-NG-Q

Layer 2 features: 12.2 14.1R4 14.1R4

• Trunk ports
• Layer 2 support for MX Series Virtual Chassis
• Layer 2 and Layer 2.5, IRB and Spanning Tree Protocols (xSTP)
• IEEE 802.1ad provider bridges
• Layer 2 protocol tunneling (L2PT) support
• Layer 2 Tunneling Protocol (L2TP)
• Multi-chassis LAG—active/active and active/standby
• Multi-chassis LAG—active/active with IGMP snooping
• Link aggregation group (LAG)—VLAN-CCC encapsulation

NOTE: LAG features and IGMP snooping with bridging, IRB, and VPLS are
not supported for the MPC3E-3D in release 12.2.

Layer 2 VPN interfaces support VLAN ID list 12.1 14.1R4 14.1R4

Label Distribution Protocol (LDP) 12.1 14.1R4 14.1R4

Link aggregation (IEEE 802.3ad) 12.1 14.1R4 14.1R4

Link Aggregation Control Protocol (LACP) 12.1 14.1R4 14.1R4

Link Layer Discovery Protocol (LLDP) — 14.1R4 14.1R4

Local loopback 12.1 14.1R4 14.1R4

MAC learning, policing, accounting, and filtering 12.1 14.1R4 14.1R4

Mobile IP — 14.1R4 14.1R4

Multichassis link aggregation — 14.1R4 14.1R4

Multiple Tag Protocol Identifiers (TPIDs) 12.1 14.1R4 14.1R4

348 Copyright © 2018, Juniper Networks, Inc.

 Chapter 16: MPC Protocol and Application Support for MX240, MX480, MX960, MX2010, MX2020, and MX10003

Table 41: Protocols and Applications Supported by MPC3E Cards for MX Series Routers (continued)

First Supported Junos OS Release

Protocol or Application MPC3E-3D MPC3E–3D-NG MPC3E–3D-NG-Q

MPLS: 12.1 14.1R4 14.1R4

• Switching of pseudowire segments (multisegment pseudowires with

BGP-L2VPN)
• LDP signaling for VPLS (LDP-VPLS) and MAC flush message processing
(MAC-FLUSH-TLV)
• RSVP graceful restart interoperability with Cisco using Nodal Hello
• Failure action on BFD session down of RSVP LSPs
• OSPF and IS-IS loop-free alternates (LFA)
• 4/5 label MPLS operation
• Virtual circuit connectivity verification (VCCV) BFD
• Point to multipoint using the enhanced-ip command (support for
NG-MVPN and P2MP load balancing over aggregated Ethernet)
• MPLS-FRR bypass link protection
• Load sharing across 64 ECMP next hops
• MPLS-FRR VPLS instance prioritization
• Five label stack on ingress

MPLS node protection, link protection, and statistics for static LSPs 12.1 14.1R4 14.1R4

mvrp — 14.1R4 14.1R4

Multitopology routing 12.1 14.1R4 14.1R4

Nonstop active routing (NSR) 12.1 14.1R4 14.1R4

OSPF 12.1 14.1R4 14.1R4

Packet mirroring 12.2 14.1R4 14.1R4

IEEE 802.1ah Provider Bridging (PBB) — 14.1R4 14.1R4

RSVP 12.1 14.1R4 14.1R4

RIP 12.1 14.1R4 14.1R4

SNMP 12.1 14.1R4 14.1R4

Copyright © 2018, Juniper Networks, Inc. 349

MX Series Interface Module Reference

Table 41: Protocols and Applications Supported by MPC3E Cards for MX Series Routers (continued)

First Supported Junos OS Release

Protocol or Application MPC3E-3D MPC3E–3D-NG MPC3E–3D-NG-Q

Spanning Tree Protocols: 12.2 14.1R4 14.1R4

• IEEE 802.1s Multiple Spanning Tree Protocol (MSTP) (part of IEEE 802.1Q
VLANs)
• IEEE 802.1w Rapid Spanning Tree Protocol (RSTP)
• Spanning-Tree Protocols (STP)
• Per-VLAN Spanning Tree (PVST)
• Bridge protocol data units (BPDUs) guard and loop guard
• STP inter-protocol action profiles and MAC flush (in VPLS multi-homing,
flush all MACs when there is a change in the STP interface state due to
root protect)

Subscriber management and services (MX2010, MX2020: 12.3R4, 13.2R2, 12.1 14.1R4 14.1R4
13.3):

• Aggregated Ethernet over static VLANs

• Aggregated Ethernet over dynamic VLANs
• ANCP and the ANCP Agent Overview
• DHCP access model
• Dynamic adjustment of shapers
• Dynamic PPPoE subscriber interface creation based on PPPoE service
name tables
• Dynamic profiles
• Dynamic shaping, scheduling, and queuing
• Dynamic VLANs
• Per unit scheduling
• Static and dynamic PPPoE subscriber interfaces

Synchronous Ethernet 13.2 14.1R4 14.1R4

Two-Way Active Measurement Protocol (TWAMP) — 14.1R4 14.1R4

Tunnel services 12.1 14.1R4 14.1R4

• Clear DF-Bit (Don't Fragment Bit)

Unified in-service software upgrade (ISSU) 13.3 14.1R4 14.1R4

Unnumbered Ethernet Interface 12.1 14.1R4 14.1R4

VLANs IEEE 802.1Q: 12.1 14.1R4 14.1R4

• VLAN stacking and rewriting

• Channels defined by two stacked VLAN tags
• Flexible VLAN tagging
• IP service for nonstandard TPID and stacked VLAN tags

350 Copyright © 2018, Juniper Networks, Inc.

 Chapter 16: MPC Protocol and Application Support for MX240, MX480, MX960, MX2010, MX2020, and MX10003

Table 41: Protocols and Applications Supported by MPC3E Cards for MX Series Routers (continued)

First Supported Junos OS Release

Protocol or Application MPC3E-3D MPC3E–3D-NG MPC3E–3D-NG-Q

Virtual Chassis: MPLS IPv4 and IPv6, unicast, multicast forwarding, VPLS, — 14.1R4 14.1R4
NSR for Layer 3/MPLS services

Virtual private LAN service (VPLS): 12.1 14.1R4 14.1R4

• BGP multihoming for inter-AS VPLS

• Gigabit Ethernet as core-facing interface
• Configurable label block sizes
• Hashing L3/L4 fields under Ethernet pseudowire for VPLS encapsulation,
CCC encapsulation, and MPLS encapsulation
• VPLS flood forwarding table filter (FTF), input FTF
• Broadcast, unicast unknown, and multicast (BUM) traffic hashing over
LAG

Virtual private network (VPN) 12.1 14.1R4 14.1R4

Virtual Router Redundancy Protocol (VRRP) for IPv4 12.1 14.1R4 14.1R4

VPLS packet flooding to the right set of interfaces across mesh groups — 14.1R4 14.1R4

WAN-PHY mode 12.2 14.1R4 14.1R4

Related • MPC3E on page 113

Documentation
• MICs Supported by MX Series Routers on page 18

Protocols and Applications Supported on the MPC4E for MX Series Routers

Table 42 on page 351 contains the first Junos OS Release support for protocols and
applications on the MPC4E. The protocols and applications support feature parity with
Junos OS Release 12.2. A dash indicates that the protocol or application is not supported.

Table 42: Protocols and Applications Supported by the MX Series MPC4E

First Supported Junos OS

Protocol or Application Release

Bidirectional Forwarding Detection protocol (BFD) 12.3R2

Border Gateway Protocol (BGP) 12.3R2

Bridge protocol data units (BPDUs) 12.3R2

Copyright © 2018, Juniper Networks, Inc. 351

MX Series Interface Module Reference

Table 42: Protocols and Applications Supported by the MX Series MPC4E (continued)

First Supported Junos OS

Protocol or Application Release

Class of service (CoS): 12.3R2

• Behavior Aggregate (BA) classification

• Forwarding class loss priority through logical tunnels (LT)
• Static VLAN mapping to a specific forwarding class using a multi-field (MF) classifier
• Targeted traffic distribution for a logical subscriber interface across a Link Aggregate Group
(LAG) bundle
• Packet rewrites
• Configurable IEEE 802.1p inheritance
• Rate-limit option for per-port queues
• Configurable shaping overhead for scheduling
• Weighted Random Early Detection (WRED)
• Intelligent oversubscription on MIC and MPC interfaces
• Class of Service on Ethernet pseudowires on Logical Tunnel (LT) interfaces
• Fine-grained authentication for RE-generated packets
• IEEE 802.1ad S-TAG, exiting/incoming core with label-switched interfaces (LSIs)
• Egress IEEE 802.1p multifield (MF) and BA classification for VPLS (MX series only)

Class of service (CoS) per port: 12.3R2

• Eight queues per port NOTE: Fine-grained queuing

• Excess-rate and excess-priority configuration at the queue level and input queuing are not
supported.
• Shaping at the port level and queue level
• Scheduling of queues based on weighted round-robin (WRR) per excess-priority class
• Round-robin scheduling of the queues per priority class
• Weighted random early detection (WRED)
• Rate limit option for per-port queues

Class of service (CoS) per virtual LAN (VLAN): 12.3R2

• Accounting, filtering, and policing

• IEEE 802.1p rewrite
• Classification
• Tricolor marking

Class of service (CoS) per Point-to-Point Protocol over Ethernet (PPPoE) or Dynamic Host –
Configuration Protocol (DHCP) subscriber interfaces:

• Accounting, filtering, and policing

• IEEE 802.1p rewrite
• Excess-rate and excess-priority configuration at the queue level
• Tricolor marking
• Shaping at the queue level
• Scheduling of queues based on weighted round-robin (WRR) per priority class
• Weighted random early detection (WRED)

352 Copyright © 2018, Juniper Networks, Inc.

 Chapter 16: MPC Protocol and Application Support for MX240, MX480, MX960, MX2010, MX2020, and MX10003

Table 42: Protocols and Applications Supported by the MX Series MPC4E (continued)

First Supported Junos OS

Protocol or Application Release

Connectivity Fault Management (CFM) protocols and features (IEEE 802.1ag): 12.3R2

• Ethernet OAM Continuity Check Message (CCM) protocol

• Ethernet OAM Linktrace protocol
• Ethernet OAM Loopback protocol
• Maintenance Intermediate Points (MIPs)
• Stacked VLAN tagging
• Trunk ports
• VPLS/VPWS
• VLAN circuit cross-connect (CCC) encapsulation
• Transitional cross-connect (TCC) encapsulation

Distributed Denial-of-Service (DDoS) Protection 12.3R2

Distributed Periodic Packet Management Process (PPMP) 12.3R2

Distance Vector Multicast Routing Protocol (DVMRP) Tunnels—access side and server side 12.3R2

Ethernet Alarm Indication Signal (ETH-AIS) 12.3R2

Ethernet Ring Protection Switching with multiple G.8032 instances 12.3R2

Firewall filters and policers: 12.3R2

• Intelligent Hierarchical Policers

• Policer support for aggregated Ethernet
• Aggregate firewall-based policer for all families of a logical interface
• Layer 2 policers
• Set forwarding class loss priority for Routing Engine (RE)-generated packets by using a
firewall
• Physical interface policers, applying policer to the entire port
• Filter-specific counters and filters

Flexible Ethernet encapsulation 12.3R2

Graceful routing engine switchover (GRES) 12.3R2

Generic Routing Encapsulation (GRE) Tunneling—access side and server side 12.3R2

IGMPv3 support with snooping disabled 12.3R2

Ingress and egress hierarchical class-of-service (CoS) shaping and hierarchical-scheduler: –

• Group of virtual LANs (VLANs) level

• VLAN level
• Port level

Copyright © 2018, Juniper Networks, Inc. 353

MX Series Interface Module Reference

Table 42: Protocols and Applications Supported by the MX Series MPC4E (continued)

First Supported Junos OS

Protocol or Application Release

Inline flow monitoring 12.3R2

Intelligent oversubscription on the Trio MPC/MIC interfaces 12.3R2

Integrated Routing and Bridging (IRB) 12.3R2

Unified In-service software upgrade (Unified ISSU) 13.3

Interoperability with MX Series Flexible PIC Concentrators (MX-FPC) 12.3R2

Interoperability with MPCs and existing DPCs 12.3R2

Interoperability with Juniper Networks 100-Gigabit Ethernet PIC 12.3R2

Interoperability with MX Series Application Services Modular Line Card (AS-MLC) 12.3R2

IPv4 12.3R2

IPv4 multicast 12.3R2

IPv6 12.3R2

IPv6 Multicast Listener Discovery (MLD) 12.3R2

IPv6 multicast 12.3R2

IPv6 Neighbor Discovery Protocol (NDP) 12.3R2

Immediate System-to-Intermediate System (IS-IS) 12.3R2

ITU-T Y.1731 timestamping support (MX Series routers) 12.3R2

Flow monitoring and services: 12.3R2

• Active monitoring (multiple v9 j-flow templates)

• Active monitoring: cflowed v9 IPv6 templates
• Active Monitoring: cflowd V9 per-PFE sampling support
• Port mirroring for Layer 2 bridging traffic (family ethernet-switching)
• Port mirroring for Layer 2 VPLS traffic (family vpls)
• Port mirroring for Layer 2 VPN traffic over a circuit cross-connect (CCC)
• Virtual private wire service (VPWS)
• Flow monitoring on Multiservices DPCs
• Packet slice for port mirroring
• Inline Jflow monitoring (IPFIX)

Labeled-switched-paths (LSPs) including accounting, policers, and filtering 12.3R2

354 Copyright © 2018, Juniper Networks, Inc.

 Chapter 16: MPC Protocol and Application Support for MX240, MX480, MX960, MX2010, MX2020, and MX10003

Table 42: Protocols and Applications Supported by the MX Series MPC4E (continued)

First Supported Junos OS

Protocol or Application Release

Label Distribution Protocol (LDP) 12.3R2

Layer 2 features: Release

• Integrated Routing and Bridging (IRB) • 12.3R2

• Spanning Tree Protocols • 12.3R2
• Link Layer Discovery Protocol (LLDP) • 13.3R1 , 12.3R4
• Bridge Protocol Data Unit (BPDU) guard • 12.3R2
• Bridge Protocol Data Unit (BPDU) loop guard • 12.3R2
• Layer 2 Tunneling Protocol (L2TP) • 12.3R2
• Trunk ports • 13.3R1
• IEEE 802.1ad provider bridges • 13.3R1
• Multi-chassis Link Aggregation Group (MC-LAG)—active/active and active/standby • 13.3R1
• MC-LAG—active/active with IGMP snooping • –
• MC-LAG VLAN –ccc interface encapsulation • 13.3R1
• Layer 2 Protocol Tunneling (L2PT) support • 13.3R1
• IGMP snooping with bridging, IRB, and VPLS • 12.3R2
• Layer 2 forwarding support under logical systems • 12.3R2
• Static Route Support • 13.2R1
• 64 members in a link aggregation group • 13.2R1
• Periodic packet management daemon (ppmd) and distributed PPMD for Link Aggregation
Control Protocol process (LACPd)

Layer 3 Features: Release

• IPv6 • 12.3R2
• Protocol Independent Multicast Source-Specific Multicast (PIM SSM) • 12.3R2
• Bidirectional Forwarding Detection (BFD) • 12.3R2
• Any-source multicast (ASM) group override of source-specific multicast (SSM) range • 12.3R2
• Connectionless Network Service (CLNS) • 12.3R2
• Data Multicast Domain Tunnels (MDT) Subsequent Address Family Identifiers (SAFI) • 12.3R2
• Draft-Rosen 7 Multicast VPNs • 12.3R2
• Multicast over Integrated Routing and Bridging (IRB) interfaces • 12.3R2
• Composite next hop with External and Internal BGP (EIBGP) paths • 12.3R2
• VPN load balancing and IP header filtering of traffic across External and Internal BGP • 13.2R1
(EIBGP) paths • 13.2R1
• Multiprotocol Label Switching (MPLS) over Generic Routing Encapsulation (GRE) • 13.2R1
• Multicast routing on Integrated Routing and Bridging (IRB) interfaces using logical tunnel
interfaces systems with a Trio MPC/MIC module

Link aggregation (IEEE 802.3ad) 12.3R2

Link Aggregation Control Protocol (LACP) 12.3R2

Link Layer Discovery Protocol (LLDP) –

Copyright © 2018, Juniper Networks, Inc. 355

MX Series Interface Module Reference

Table 42: Protocols and Applications Supported by the MX Series MPC4E (continued)

First Supported Junos OS

Protocol or Application Release

Local loopback 12.3R2

MAC learning, policing, accounting, and filtering 12.3R2

Mobile IP –

Multiservices DPC (MS-DPC): 13.2R1

• Junos Address Aware Network Addressing Overview

• Intrusion Detection Service (IDS)
• Graceful Routing Engine Switchover (GRES) for NAT
• Intrusion Detection and Prevention (IDP) interoperability
• IP Security (IPSec) detection
• Two-Way Active Measurement Protocol (TWAMP) interoperability
• Real-Time Performance Monitor (RPM) interoperabilitiy
• GRE interoperability

Multi-chassis Link Aggregation (MC-LAG) 13.3R1

Multiple Tag Protocol Identifiers (TPIDs) 12.3R2

Multiprotocol Label Switching (MPLS): 12.3R2

• Switching of pseudowire segments (multi-segment pseudowires with BGP-L2VPN)

• LDP signaling for VPLS (LDP-VPLS) and MAC flush message processing (MAC-FLUSH-TLV)
• RSVP graceful restart interoperability with Cisco using Nodal Hello
• Failure action on BFD session down of RSVP LSPs
• OSPF and IS-IS loop-free alternates (LFA)
• 4/5 label MPLS operation
• Virtual circuit connection verification (VCCV) BFD
• Point-to-multipoint using the enhanced-ip command (support for NG-MVPN and P2MP
load balancing over aggregated Ethernet)
• MPLS-FRR bypass link protection
• Load sharing across 64 ECMP next hops
• MPLS-FRR VPLS instance prioritization
• Five label stack on ingress
• Generic Routing Encapsulation (GRE) keepalive messages
• MPLS node protection, link protection, and statistics for static LSPs

mvrp –

Multitopology routing (MTR) –

Nonstop Active Routing (NSR) 12.3R2

Open Shortest Path First (OSPF) 12.3R2

356 Copyright © 2018, Juniper Networks, Inc.

 Chapter 16: MPC Protocol and Application Support for MX240, MX480, MX960, MX2010, MX2020, and MX10003

Table 42: Protocols and Applications Supported by the MX Series MPC4E (continued)

First Supported Junos OS

Protocol or Application Release

Packet mirroring 12.3R2

Precision Time Protocol (IEEE 1588) 15.1R1

IEEE 802.1ah provider backbone bridges (PBB) –

Periodic Packet Management Process (PPMP) and Distributed PPMP 12.3R2

Push a tag on Ethernet VPLS and Ethernet CCC tag encapsulations –

Remote Defect Indication (RDI) 12.3R2

Resource Reservation Protocol (RSVP) 12.3R2

Routing Information Protocol (RIP) 12.3R2

SNMP 12.3R2

Spanning Tree Protocols: 12.3R2

• IEEE 802.1s Multiple Spanning Tree Protocol (MSTP) (part of IEEE 802.1Q VLANs)
• IEEE 802.1w Rapid Spanning Tree Protocol (RSTP)
• IEEE 802.1D Spanning Tree Protocol (STP)
• Per-VLAN Spanning Tree (PVST)
• Bridge Protocol Data Units (BPDUs) guard and loop guard
• STP interprotocol action profiles and MAC flush (in VPLS multihoming, flush all MACs
when there is a change in the STP interface state due to root protect)

Subscriber management and services: Release

(MX2010, MX2020: 12.3R4, 13.2R2, 13.3)

• Aggregated Ethernet over static VLANs • 12.3R2

• Aggregated Ethernet over dynamic VLANs • 12.3R2
• Access Node Control Protocol (ANCP) and the ANCP Agent • 12.3R2
• DHCP access model • 12.3R2
• Dynamic adjustment of shapers • 12.3R2
• Dynamic PPPoE subscriber interfaces creation based on PPPoE service name tables • 12.3R2
• Dynamic profiles • 12.3R2
• Dynamic shaping, scheduling, and queuing • 12.3R2
• Dynamic VLANs • 12.3R2
• Enhanced subscriber management • 15.1R4
• Static and dynamic PPPoE subscriber interfaces • 12.3R2

Synchronous Ethernet (SyncE) 12.3 with SCBE and later

Copyright © 2018, Juniper Networks, Inc. 357

MX Series Interface Module Reference

Table 42: Protocols and Applications Supported by the MX Series MPC4E (continued)

First Supported Junos OS

Protocol or Application Release

Two-Way Active Measurement Protocol (TWAMP) 13.2

Tunnel services 12.3R2

• Clear DF-Bit (Don't Fragment Bit)

Type, Length, and Value (TLVs) support (IEEE 802.1ag) –

Unnumbered Ethernet Interface 12.3R2

VLANs IEEE 802.1Q: 12.3R2

• VLAN stacking and rewriting

• Channels defined by two stacked VLAN tags
• Flexible VLAN tagging
• IP service for nonstandard TPID and stacked VLAN tags

Virtual Chassis (MX Series): 13.2R1 (12.3R4 TRD)

• Class of Service (CoS) Support for Virtual Ports

• Layer 2 support
• DHCP Access Model and authentication, authorization, and accounting (AAA) services
• Layer 3 Provider Edge (PE) router support
• Dynamic Lawful Intercept (DLI)
• Layer 2 Access Node Control Protocol (ANCP)
• Wireline Subscriber Management scaling to 64K subscribers
• Non-stop active routing (NSR) support for Layer 3 services
• Local, Global, and VCCP Graceful Routing Engine Switchover (GRES)
• SNMP trap generation when vc-port command fails
• Virtual Chassis Port (VCP) masking
• Access to the Virtual Chassis Through the Management Interface

Virtual Private LAN service (VPLS): 12.3R2

• BGP multihoming for inter-AS VPLS

• Gigabit Ethernet as core-facing interface
• Configurable label block sizes
• Hashing L3/L4 fields under Ethernet pseudowire for VPLS encapsulation, CCC
encapsulation, and MPLS encapsulation
• VPLS flood forwarding table filter (FTF), input FTF
• Broadcast, unicast unknown, and multicast (BUM) traffic hashing over LAG
• Configurable multichassis link aggregation (MC-LAG) interfaces to improve the Layer 2
and Layer 3 convergence time to subsecond values when a multichassis aggregated
Ethernet link goes down or comes up in a bridge domain
• MAC Pinning to control MAC moves in a bridging environment and in VPLS networks

358 Copyright © 2018, Juniper Networks, Inc.

 Chapter 16: MPC Protocol and Application Support for MX240, MX480, MX960, MX2010, MX2020, and MX10003

Table 42: Protocols and Applications Supported by the MX Series MPC4E (continued)

First Supported Junos OS

Protocol or Application Release

Virtual private network (VPN): 12.3R2

• Multiprotocol Label Switching (MPLS)

Virtual Router Redundancy Protocol (VRRP) for IPv4 12.3R2

• Scale VRRP using instance grouping

• Periodic Packet Management Process (PPMP) and Distributed Periodic Packet Management
Process (PPMP)

VPLS packet flooding to the right set of interfaces across mesh groups 12.3R2

WAN-PHY mode 12.3R2

Related • 32x10GE MPC4E on page 119

Documentation
• 2x100GE + 8x10GE MPC4E on page 120

• MICs Supported by MX Series Routers on page 18

• MPCs Supported by MX240, MX480, MX960, MX2010, and MX2020 Routers on page 12

Protocols and Applications Supported by the MPC5E for MX Series Routers

Table 43 on page 359 contains the first Junos OS Release support for protocols and
applications in the MPC5E installed on the MX240, MX480, MX960, MX2010, and MX2020
routers. The protocols and applications support feature parity with Junos OS Release
12.3.

A dash indicates that the protocol or application is not supported.

Table 43: Protocols and Applications Supported by the MX240, MX480, MX960, MX2010, and MX2020 MPC5E

First Supported Junos OS

Protocol or Application Release

Access Node Control Protocol (ANCP) -

Accepts traffic destined for generic routing encapsulation (GRE) tunnels or Distance Vector 13.3R3
Multicast Routing Protocol (DVMRP) (IP-in-IP) tunnels

• Dynamic
• Manual

Bidirectional Forwarding Detection protocol (BFD) 13.3R3

Border Gateway Protocol (BGP) 13.3R3

Copyright © 2018, Juniper Networks, Inc. 359

MX Series Interface Module Reference

Table 43: Protocols and Applications Supported by the MX240, MX480, MX960, MX2010, and MX2020
MPC5E (continued)

First Supported Junos OS

Protocol or Application Release

Bridge protocol data units (BPDUs) 13.3R3

BGP/MPLS virtual private networks (VPNs) 13.3R3

Class of service (CoS): 13.3R3

• Maintain CoS across internal tunnel interfaces

• Packet rewrites
• Behavior aggregate (BA) classification
• BA classification based on 802.1p of payload for core-facing VPLS interfaces
• BA DSCP classification of MPLS packets for Layer 3 VPN/VPLS LSI and MPLS interfaces
• Rate limit option for per-port queues
• BA DSCP classification for VPLS/CCC family
• Configurable .1p inheritance: push and swap from the hidden tag
• Configurable shaping overhead for scheduling

Class of service (CoS) per port: 13.3R3

• Eight queues per port

• Excess-rate and excess-priority configurations at the queue level
• Shaping at the port level
• Shaping at the queue level
• Scheduling of queues based on the weighted round-robin (WRR) per excess-priority class
• Round-robin scheduling of the queues per priority class
• Weighted random early detection (WRED)

Class of service (CoS) per virtual LAN (VLAN): 13.3R3

• Accounting, filtering, and policing

• IEEE 802.1p rewrite
• Classification
• Tricolor marking

Class of service (CoS) per Point-to-Point Protocol over Ethernet (PPPoE) or Dynamic Host 13.3R3
Configuration Protocol (DHCP) subscriber interfaces:

• Accounting, filtering, and policing

• IEEE 802.1p rewrite
• Classification
• Excess-rate and excess-priority configuration at the queue level
• Tricolor marking
• Shaping at the queue level
• Scheduling of queues based on weighted round-robin (WRR) per priority class
• Weighted random early detection (WRED)

Damping 15.1R2

360 Copyright © 2018, Juniper Networks, Inc.

 Chapter 16: MPC Protocol and Application Support for MX240, MX480, MX960, MX2010, MX2020, and MX10003

Table 43: Protocols and Applications Supported by the MX240, MX480, MX960, MX2010, and MX2020
MPC5E (continued)

First Supported Junos OS

Protocol or Application Release

Distributed Denial-of-Service (DDoS) Protection 13.3R3

DVMRP and GRE support—access side and server side 13.3R3

Ethernet Ring Protection Switching with multiple G.8032 instances 13.3R3

IEEE 802.1ag Ethernet OAM Continuity Check protocol 13.3R3

IEEE 802.1ag Ethernet OAM Linktrace protocol 13.3R3

IEEE 802.1ag Ethernet OAM Loopback protocol 13.3R3

IEEE 802.1ag Maintenance Association Intermediate Point (MIP) support, continuity check message 13.3R3
(CCM), stacked VLAN tagging, trunk ports, support for VPLS/VPWS, VLAN circuit cross-connect
(CCC) encapsulation and translational cross-connect (TCC) encapsulation

Port Status TLV and Interface Status TLV -

IEEE 802.3ah distributed periodic packet management (PPM) process, alarm indication signal 13.3R3
(AIS), and remote defect indication (RDI)

Firewall filters and policers: 13.3R3

• Policer support for aggregated Ethernet

• Aggregate firewall-based policer for all families of a logical interface
• Set forwarding class and loss priority for Routing Engine-generated packets by using a firewall
• Physical interface policers, applying policers to the entire port
• Lower policer limit from 32,000 to 8000
• Egress .1p MF and BA classification for VPLS
• Differentiated Services Code Point (DSCP) rewrite for IPv4 and IPv6

Flexible Ethernet encapsulation 13.3R3

Flexible Queuing Mode 14.1R1

NOTE: Flexible queuing mode is supported only on non-HQoS variants.

Graceful Routing Engine Switchover (GRES) 13.3R3

IGMPv3 support with snooping disabled 13.3R3

Ingress and egress hierarchical class-of-service (CoS) shaping and hierarchical-scheduler: 13.3R3

• Group of virtual LANs (VLANs) level

• VLAN level
• Port level

Copyright © 2018, Juniper Networks, Inc. 361

MX Series Interface Module Reference

Table 43: Protocols and Applications Supported by the MX240, MX480, MX960, MX2010, and MX2020
MPC5E (continued)

First Supported Junos OS

Protocol or Application Release

Hierarchical CoS on generic routing encapsulation (GRE) tunnels 15.1R2

Inline active flow monitoring 13.3R3

Intelligent Oversubscription 13.3R3

Integrated routing and bridging (IRB) 13.3R3

Unified In-service software upgrade (Unified ISSU) 16.1R1

Interoperability with MPCs and existing DPCs -

Interoperability with Multiservices DPCs 13.3R3

Interoperability with MX Series Flexible PIC Concentrators (MX-FPC) 13.3R3

Interoperability with Juniper Networks 100-Gigabit Ethernet PIC 13.3R3

Interoperability with MX Series Application Services Modular Line Card (AS-MLC) 13.3R3

IPv4 13.3R3

IPv4 multicast 13.3R3

IPv6 13.3R3

IPv6 MLD 13.3R3

IPv6 multicast 13.3R3

IPv6 Neighbor Discovery 13.3R3

IS-IS 13.3R3

ITU-T Y.1731 timestamping support on MX Series routers 13.3R3

Flow monitoring and services: Release

• Active monitoring (multiple version 8 j-flow templates) • 13.3R3

• Active monitoring (cflowed version 9 templates) • 13.3R3
• Port mirroring family VPLS, bridge CCC encapsulation (VPWS) • 13.3R3
• Packet slice for port mirroring • 13.3R3
• Flow monitoring on Multiservices DPCs • -
• Inline active flow monitoring on MPC5E • 13.3R3

362 Copyright © 2018, Juniper Networks, Inc.

 Chapter 16: MPC Protocol and Application Support for MX240, MX480, MX960, MX2010, MX2020, and MX10003

Table 43: Protocols and Applications Supported by the MX240, MX480, MX960, MX2010, and MX2020
MPC5E (continued)

First Supported Junos OS

Protocol or Application Release

Labeled-switched-paths (LSPs) including accounting, policers, and filtering 13.3R3

LDP 13.3R3

Layer 2 features: Release

• Trunk ports • 13.3R3

• Layer 2 support for MX Series Virtual Chassis • 13.3R3
• Layer 2 and Layer 2.5, IRB, and Spanning Tree Protocols (xSTP) • -
• IEEE 802.1ad provider bridges • 13.3R3
• Layer 2 protocol tunneling (L2PT) support • 13.3R3
• Layer 2 Tunneling Protocol (L2TP) • 13.3R3
• Multichassis LAG—active/active and active/standby • 13.3R3
• Multichassis LAG—active/active with IGMP snooping • 13.3R3
• Link aggregation group (LAG)—VLAN-CCC encapsulation • 13.3R3
• IGMP snooping with bridging, IRB, and VPLS • 13.3R3

Layer 2 VPN interfaces support VLAN ID list 13.3R3

Link aggregation (IEEE 802.3ad) 13.3R3

Link Aggregation Control Protocol (LACP) 13.3R3

Link Layer Discovery Protocol (LLDP) 13.3R3

Local loopback 13.3R3

MAC learning, policing, accounting, and filtering 13.3R3

Mobile IP -

Multichassis link aggregation -

Multiple Tag Protocol Identifiers (TPIDs) 13.3R3

Copyright © 2018, Juniper Networks, Inc. 363

MX Series Interface Module Reference

Table 43: Protocols and Applications Supported by the MX240, MX480, MX960, MX2010, and MX2020
MPC5E (continued)

First Supported Junos OS

Protocol or Application Release

MPLS: 13.3R3

• Switching of pseudowire segments (multisegment pseudowires with BGP-L2VPN)

• LDP signaling for VPLS (LDP-VPLS) and MAC flush message processing (MAC-FLUSH-TLV)
• RSVP graceful restart interoperability with Cisco using Nodal Hello
• Failure action on BFD session down of RSVP LSPs
• OSPF and IS-IS loop-free alternates (LFA)
• 4/5 label MPLS operation
• Virtual circuit connectivity verification (VCCV) BFD
• Point to multipoint using the enhanced-ip command (support for NG-MVPN and
point-to-multipoint load balancing over aggregated Ethernet)
• MPLS-FRR bypass link protection
• Load sharing across 64 ECMP next hops
• MPLS-FRR VPLS instance prioritization
• Five label stack on ingress

MPLS node protection, link protection, and statistics for static LSPs 13.3R3

mvrp -

Multitopology routing -

Nonstop active routing (NSR) 13.3R3

OSPF 13.3R3

Packet mirroring 13.3R3

Precision Time Protocol (IEEE 1588) 14.2R2

IEEE 802.1ah provider backbone bridging (PBB) -

Push a tag on Ethernet VPLS and Ethernet CCC tag encapsulations 13.3R3

RSVP 13.3R3

RIP 13.3R3

SNMP 13.3R3

364 Copyright © 2018, Juniper Networks, Inc.

 Chapter 16: MPC Protocol and Application Support for MX240, MX480, MX960, MX2010, MX2020, and MX10003

Table 43: Protocols and Applications Supported by the MX240, MX480, MX960, MX2010, and MX2020
MPC5E (continued)

First Supported Junos OS

Protocol or Application Release

Spanning Tree Protocols: 13.3R3

• IEEE 802.1s Multiple Spanning Tree Protocol (MSTP) (part of IEEE 802.1Q VLANs)
• IEEE 802.1w Rapid Spanning Tree Protocol (RSTP)
• IEEE 802.1D Spanning Tree Protocol (STP)
• Per-VLAN Spanning Tree (PVST)
• Bridge protocol data units (BPDUs) guard and loop guard
• STP inter-protocol action profiles and MAC flush

Subscriber management and services:(MX2010, MX2020: 12.3R4, 13.3R2, 13.3) Release

• Aggregated Ethernet over static VLANs • 13.3R3

• Aggregated Ethernet over dynamic VLANs • 13.3R3
• Access Node Control Protocol (ANCP) and the ANCP Agent • 13.3R3
• DHCP access model • 13.3R3
• Dynamic adjustment of shapers • 13.3R3
• Dynamic PPPoE subscriber interface creation based on PPPoE service name tables • 13.3R3
• Dynamic profiles • 13.3R3
• Dynamic shaping, scheduling, and queuing • 13.3R3
• Dynamic VLANs • 13.3R3
• Enhanced subscriber management • 15.1R4
• Static and dynamic PPPoE subscriber interfaces • 13.3R3

Synchronous Ethernet 13.3R3

Two-Way Active Measurement Protocol (TWAMP) 13.3R3

Tunnel services 13.3R3

• Clear DF-Bit (Don't Fragment Bit)

Unnumbered Ethernet Interface 13.3R3

VLANs IEEE 802.1Q: 13.3R3

• VLAN stacking and rewriting

• Channels defined by two stacked VLAN tags
• Flexible VLAN tagging
• IP service for nonstandard TPID and stacked VLAN tags

Virtual Chassis: MPLS IPv4 and IPv6, unicast, multicast forwarding, VPLS, NSR for Layer 3/MPLS 13.3R3
services

Copyright © 2018, Juniper Networks, Inc. 365

MX Series Interface Module Reference

Table 43: Protocols and Applications Supported by the MX240, MX480, MX960, MX2010, and MX2020
MPC5E (continued)

First Supported Junos OS

Protocol or Application Release

Virtual private LAN service (VPLS): 13.3R3

• BGP multihoming for inter-AS VPLS

• Gigabit Ethernet as core-facing interface
• Configurable label block sizes
• Hashing L3/L4 fields under Ethernet pseudowire for VPLS encapsulation, CCC encapsulation,
and MPLS encapsulation
• VPLS flood forwarding table filter (FTF), input FTF
• Broadcast, unicast unknown, and multicast traffic hashing over LAG

Virtual private network (VPN) 13.3R3

Virtual Router Redundancy Protocol (VRRP) for IPv4 13.3R3

VPLS packet flooding to the right set of interfaces across mesh groups 13.3R3

WAN-PHY mode 13.3R3

Related • 6x40GE + 24x10GE MPC5E on page 122

Documentation
• 6x40GE + 24x10GE MPC5EQ on page 124

• MICs Supported by MX Series Routers on page 18

Protocols and Applications Supported by the MPC6E for MX2000 Routers

Table 44 on page 366 contains the first Junos OS Release support for protocols and
applications on the MX2010 and MX2020 MPC6E. The protocols and applications support
feature parity with Junos OS Release 13.3.

A dash indicates that the protocol or application is not supported.

Table 44: Protocols and Applications Supported by the MX2010 and MX2020 MPC6E

First Supported Junos OS

Protocol or Application Release

Access Node Control Protocol (ANCP) -

Accepts traffic destined for generic routing encapsulation (GRE) tunnels or Distance Vector 13.3R3
Multicast Routing Protocol (DVMRP) (IP-in-IP) tunnels

• Dynamic
• Manual

Bidirectional Forwarding Detection protocol (BFD) 13.3R3

366 Copyright © 2018, Juniper Networks, Inc.

 Chapter 16: MPC Protocol and Application Support for MX240, MX480, MX960, MX2010, MX2020, and MX10003

Table 44: Protocols and Applications Supported by the MX2010 and MX2020 MPC6E (continued)

First Supported Junos OS

Protocol or Application Release

Border Gateway Protocol (BGP) 13.3R3

Bridge protocol data units (BPDUs) 13.3R3

BGP/MPLS virtual private networks (VPNs) 13.3R3

Class of service (CoS): 13.3R3

• Maintain CoS across internal tunnel interfaces

• Packet rewrites
• Behavior aggregate (BA) classification
• BA classification based on 802.1p of payload for core-facing VPLS interfaces
• BA DSCP classification of MPLS packets for L3VPN/VPLS LSI and MPLS interfaces
• Rate limit option for per-port queues
• BA DSCP classification for VPLS/CCC family
• Configurable .1p inheritance: push and swap from the hidden tag
• Configurable shaping overhead for scheduling

Class of service (CoS) per port: 13.3R2

• Eight queues per port

• Excess-rate and excess-priority configurations at the queue level
• Shaping at the port level
• Shaping at the queue level
• Scheduling of queues based on the weighted round-robin (WRR) per excess-priority class
• Round-robin scheduling of the queues per priority class
• Weighted random early detection (WRED)

Class of service (CoS) per virtual LAN (VLAN): 13.3R3

• Accounting, filtering, and policing

• IEEE 802.1p rewrite
• Classification
• Tricolor marking

Class of service (CoS) per Point-to-Point Protocol over Ethernet (PPPoE) or Dynamic Host 13.3R3
Configuration Protocol (DHCP) subscriber interfaces:

• Accounting, filtering, and policing

• IEEE 802.1p rewrite
• Classification
• Excess-rate and excess-priority configuration at the queue level
• Tricolor marking
• Shaping at the queue level
• Scheduling of queues based on weighted round-robin (WRR) per priority class
• Weighted random early detection (WRED)

Copyright © 2018, Juniper Networks, Inc. 367

MX Series Interface Module Reference

Table 44: Protocols and Applications Supported by the MX2010 and MX2020 MPC6E (continued)

First Supported Junos OS

Protocol or Application Release

Damping 15.1R2

Distributed Denial-of-Service (DDoS) Protection 13.3R3

DVMRP and GRE support—access side and server side 13.3R3

Ethernet Ring Protection Switching with multiple G.8032 instances 13.3R3

IEEE 802.1ag Ethernet OAM Continuity Check protocol 13.3R3

IEEE 802.1ag Ethernet OAM Linktrace protocol 13.3R3

IEEE 802.1ag Ethernet OAM Loopback protocol 13.3R3

IEEE 802.1ag Maintenance Association Intermediate Point (MIP) support, continuity check 13.3R3
message (CCM), stacked VLAN tagging, trunk ports, support for VPLS/VPWS, VLAN circuit
cross-connect (CCC) encapsulation and translational cross-connect (TCC) encapsulation

IEEE 802.1ag optional type, length, and value (TLV) (Port Status TLV and Interface Status -
TLV)

IEEE 802.3ah distributed periodic packet management (PPM) process, alarm indication 13.3R3
signal (AIS), and remote defect indication (RDI)

Firewall filters and policers: 13.3R3

• Policer support for aggregated Ethernet

• Aggregate firewall-based policer for all families of a logical interface
• Set forwarding class and loss priority for Routing Engine-generated packets by using a
firewall
• Physical interface policers, applying policers to the entire port
• Lower policer limit from 32,000 to 8000
• Egress .1p MF and BA classification for VPLS
• Differentiated Services Code Point (DSCP) rewrite for IPv4 and IPv6

Flexible Ethernet encapsulation 13.3R3

Graceful Routing Engine Switchover (GRES) 13.3R3

IGMPv3 support with snooping disabled 13.3R3

Ingress and egress hierarchical class-of-service (CoS) shaping and hierarchical-scheduler: 13.3R3

• Group of virtual LANs (VLANs) level

• VLAN level
• Port level

Inline active flow monitoring 13.3R3

368 Copyright © 2018, Juniper Networks, Inc.

 Chapter 16: MPC Protocol and Application Support for MX240, MX480, MX960, MX2010, MX2020, and MX10003

Table 44: Protocols and Applications Supported by the MX2010 and MX2020 MPC6E (continued)

First Supported Junos OS

Protocol or Application Release

Intelligent oversubscription on MIC and MPC interfaces 13.3R3

Integrated routing and bridging (IRB) 13.3R3

Unified In-service software upgrade (Unified ISSU) 16.1R1

Interoperability with MPCs and existing DPCs 13.3R3

Interoperability with Multiservices DPCs 13.3R3

Interoperability with MX Series Flexible PIC Concentrators (MX-FPC) 13.3R3

IPv4 13.3R3

IPv4 multicast 13.3R3

IPv6 13.3R3

IPv6 MLD 13.3R3

IPv6 multicast 13.3R3

IPv6 neighbor discovery 13.3R3

IS-IS 13.3R3

ITU-T Y.1731 timestamping support on MX Series routers 13.3R3

Flow monitoring and services: Release

• Active monitoring (multiple v8 version j-flow templates) • 13.3R3

• Active monitoring (cflowed version 9 templates) • 13.3R3
• Port mirroring family VPLS, bridge CCC encapsulation (VPWS) • 13.3R3
• Packet slice for port mirroring • 13.3R3
• Flow monitoring on Multiservices DPCs • -
• Inline active flow monitoring on MPC5E • 13.3R3

Labeled-switched-paths (LSPs) including accounting, policers, and filtering 13.3R3

LDP 13.3R3

Copyright © 2018, Juniper Networks, Inc. 369

MX Series Interface Module Reference

Table 44: Protocols and Applications Supported by the MX2010 and MX2020 MPC6E (continued)

First Supported Junos OS

Protocol or Application Release

Layer 2 features: Release

• Trunk ports • 13.3R3

• Layer 2 support for MX Series Virtual Chassis • 13.3R3
• Layer 2 and Layer 2.5, IRB and Spanning Tree Protocols (xSTP) • 15.1R2
• IEEE 802.1ad provider bridges • 13.3R3
• Layer 2 protocol tunneling (L2PT) support • 13.3R3
• Layer 2 Tunneling Protocol (L2TP) • 13.3R3
• Multichassis LAG—active/active and active/standby • 13.3R3
• Multichassis LAG—active/active with IGMP snooping • 13.3R3
• Link aggregation group (LAG)—VLAN-CCC encapsulation • 15.1R2
• IGMP snooping with bridging, IRB, and VPLS • 13.3R2

Layer 2 VPN interfaces

Link aggregation (IEEE 802.3ad) 13.3R3

Link Aggregation Control Protocol (LACP) 13.3R3

Link Layer Discovery Protocol (LLDP) -

Local loopback 13.3R3

MAC learning, policing, accounting, and filtering 13.3R3

Mobile IP -

Multichassis link aggregation -

Multiple Tag Protocol Identifiers (TPIDs) 13.3R3

370 Copyright © 2018, Juniper Networks, Inc.

 Chapter 16: MPC Protocol and Application Support for MX240, MX480, MX960, MX2010, MX2020, and MX10003

Table 44: Protocols and Applications Supported by the MX2010 and MX2020 MPC6E (continued)

First Supported Junos OS

Protocol or Application Release

MPLS: 13.3R3

• Switching of pseudowire segments (multisegment pseudowires with BGP-L2VPN)

• LDP signaling for VPLS (LDP-VPLS) and MAC flush message processing
(MAC-FLUSH-TLV)
• RSVP graceful restart interoperability with Cisco using Nodal Hello
• Failure action on BFD session down of RSVP LSPs
• OSPF and IS-IS loop-free alternates (LFA)
• 4/5 label MPLS operation
• Virtual circuit connectivity verification (VCCV) BFD
• Point to multipoint using the enhanced-ip command (support for NG-MVPN and P2MP
load balancing over aggregated Ethernet)
• MPLS-FRR bypass link protection
• Load sharing across 64 ECMP next hops
• MPLS-FRR VPLS instance prioritization
• Five label stack on ingress

MPLS node protection, link protection, and statistics for static LSPs 13.3R3

mvrp -

Multitopology routing -

Nonstop active routing (NSR) -

OSPF 13.3R3

Packet mirroring 13.3R3

Precision Time Protocol (IEEE 1588) -

IEEE 802.1ah provider backbone bridging (PBB) -

Push a tag on Ethernet VPLS and Ethernet CCC tag encapsulations 13.3R3

RSVP 13.3R3

RIP 13.3R3

SNMP 13.3R3

Copyright © 2018, Juniper Networks, Inc. 371

MX Series Interface Module Reference

Table 44: Protocols and Applications Supported by the MX2010 and MX2020 MPC6E (continued)

First Supported Junos OS

Protocol or Application Release

Spanning Tree Protocols: 13.3R3

• IEEE 802.1s Multiple Spanning Tree Protocol (MSTP) (part of IEEE 802.1Q VLANs)
• IEEE 802.1w Rapid Spanning Tree Protocol (RSTP)
• IEEE 802.1D Spanning Tree Protocol (STP)
• Per-VLAN Spanning Tree (PVST)
• Bridge protocol data units (BPDUs) guard and loop guard
• STP inter-protocol action profiles and MAC flush

Subscriber management and services(MX2010, MX2020: 12.3R4, 13.3R2, 13.3): Release

• Aggregated Ethernet over static VLANs • 13,3R3

• Aggregated Ethernet over dynamic VLANs • 13.3R3
• ANCP and the ANCP Agent Overview • 13.3R3
• DHCP access model • 13.3R3
• Dynamic adjustment of shapers • 13.3R3
• Dynamic PPPoE subscriber interface creation based on PPPoE service name tables • 13.3R3
• Dynamic profiles • 13.3R3
• Dynamic shaping, scheduling, and queuing • 13.3R3
• Dynamic VLANs • 13.3R3
• Enhanced subscriber management (uplink services) • 15.1R4
• Static and dynamic PPPoE subscriber interfaces • 13.3R3

Synchronous Ethernet 13.3R3

Two-Way Active Measurement Protocol (TWAMP) 13.3R3

Tunnel services 13.3R3

Unnumbered Ethernet Interface 13.3R3

VLANs IEEE 802.1Q: 13.3R3

• VLAN stacking and rewriting

• Channels defined by two stacked VLAN tags
• Flexible VLAN tagging
• IP service for nonstandard TPID and stacked VLAN tags

Virtual private LAN service (VPLS): 13.3R3

• BGP multihoming for inter-AS VPLS

• Gigabit Ethernet as core-facing interface
• Configurable label block sizes
• Hashing L3/L4 fields under Ethernet pseudowire for VPLS encapsulation, CCC
encapsulation, and MPLS encapsulation
• VPLS flood forwarding table filter (FTF), input FTF
• Broadcast, unknown unicast, and multicast traffic hashing over LAG

372 Copyright © 2018, Juniper Networks, Inc.

 Chapter 16: MPC Protocol and Application Support for MX240, MX480, MX960, MX2010, MX2020, and MX10003

Table 44: Protocols and Applications Supported by the MX2010 and MX2020 MPC6E (continued)

First Supported Junos OS

Protocol or Application Release

Virtual private network (VPN) 13.3R3

Virtual Router Redundancy Protocol (VRRP) for IPv4 13.3R3

VPLS packet flooding to the right set of interfaces across mesh groups 13.3R3

WAN-PHY mode 13.3R3

Related • MPC6E on page 129

Documentation
• MICs Supported by MX Series Routers on page 18

Protocols and Applications Supported by the MPC7E for MX Series Routers

Table 41 on page 344 contains the first Junos OS Release support for protocols and
applications on the MX240, MX480, MX960, MX2010, and MX2020 MPC7Es (“MPC7E
10G” on page 132 and “MPC7E (Multi-Rate)” on page 130). The protocols and applications
support feature parity with Junos OS Release 15.1R1.

A dash indicates that the protocol or application is not supported.

Table 45: Protocols and Applications Supported by MPC7Es in the MX240, MX480, MX960, MX2010, and MX2020
Routers

First Supported Junos OS Release for First Supported Junos OS Release for
Protocol or Application MPC7E-MRATE MPC7E-10G

Access Node Control Protocol (ANCP) - -

Accepts traffic destined for generic 15.1F4 15.1F5

routing encapsulation (GRE) tunnels or
Distance Vector Multicast Routing
Protocol (DVMRP) (IP-in-IP) tunnels

• Dynamic
• Manual

Bidirectional Forwarding Detection protocol 15.1F4 15.1F5

(BFD)

Border Gateway Protocol (BGP) 15.1F4 15.1F5

Bridge protocol data units (BPDUs) 15.1F4 15.1F5

BGP/MPLS virtual private networks 15.1F4 15.1F5

(VPNs)

Copyright © 2018, Juniper Networks, Inc. 373

MX Series Interface Module Reference

Table 45: Protocols and Applications Supported by MPC7Es in the MX240, MX480, MX960, MX2010, and MX2020
Routers (continued)

First Supported Junos OS Release for First Supported Junos OS Release for
Protocol or Application MPC7E-MRATE MPC7E-10G

Class of service (CoS): 15.1F4 15.1F5

• Maintain CoS across internal tunnel

interfaces
• Packet rewrites
• Behavior aggregate (BA) classification
• BA classification based on 802.1p of
payload for core-facing VPLS interfaces
• BA DSCP classification of MPLS
packets for L3VPN/VPLS LSI and MPLS
interfaces
• Rate limit option for per-port queues
• BA DSCP classification for VPLS/CCC
family
• Configurable .1p inheritance: push and
swap from the hidden tag
• Configurable shaping overhead for
scheduling

Class of service (CoS) per port: 15.1F4 15.1F5

• Eight queues per port NOTE: MPC7E-MRATE MPC supports 5 NOTE: MPC7E-10G MPC supports 5
• Excess-rate and excess-priority guaranteed and 4 excess priorities. guaranteed and 4 excess priorities.
configurations at the queue level
• Shaping at the port level
• Shaping at the queue level
• Scheduling of queues based on the
weighted round-robin (WRR) per
excess-priority class
• Round-robin scheduling of the queues
per priority class
• Weighted random early detection
(WRED)

Class of service (CoS) per virtual LAN 15.1F4 15.1F5

(VLAN):

• Accounting, filtering, and policing

• IEEE 802.1p rewrite
• Classification
• Tricolor marking

374 Copyright © 2018, Juniper Networks, Inc.

 Chapter 16: MPC Protocol and Application Support for MX240, MX480, MX960, MX2010, MX2020, and MX10003

Table 45: Protocols and Applications Supported by MPC7Es in the MX240, MX480, MX960, MX2010, and MX2020
Routers (continued)

First Supported Junos OS Release for First Supported Junos OS Release for
Protocol or Application MPC7E-MRATE MPC7E-10G

Class of service (CoS) per Point-to-Point - -

Protocol over Ethernet (PPPoE) or
Dynamic Host Configuration Protocol
(DHCP) subscriber interfaces:

• Accounting, filtering, and policing

• IEEE 802.1p rewrite
• Classification
• Excess-rate and excess-priority
configuration at the queue level
• Tricolor marking
• Shaping at the queue level
• Scheduling of queues based on
weighted round-robin (WRR) per
priority class
• Weighted random early detection
(WRED)

Distributed Denial-of-Service (DDoS) 15.1F4 15.1F5

Protection

DVMRP and GRE support—access side 15.1F4 15.1F5

and server side

Dynamic Power Management 15.1F4 15.1F5

Ethernet Ring Protection Switching with 15.1F4 15.1F5

multiple G.8032 instances

Flexible Queuing Mode 15.1F4 15.1F5

IEEE 802.1ag Ethernet OAM Continuity 15.1F4 15.1F5

Check protocol

IEEE 802.1ag Ethernet OAM Linktrace 15.1F4 15.1F5

protocol

IEEE 802.1ag Ethernet OAM Loopback 15.1F4 15.1F5

protocol

IEEE 802.1ag maintenance association 15.1F4 15.1F5

intermediate point (MIP) support,
continuity check message (CCM), stacked
VLAN tagging, trunk ports, support for
VPLS/VPWS, VLAN circuit cross-connect
(CCC) encapsulation and translational
cross-connect (TCC) encapsulation

Copyright © 2018, Juniper Networks, Inc. 375

MX Series Interface Module Reference

Table 45: Protocols and Applications Supported by MPC7Es in the MX240, MX480, MX960, MX2010, and MX2020
Routers (continued)

First Supported Junos OS Release for First Supported Junos OS Release for
Protocol or Application MPC7E-MRATE MPC7E-10G

IEEE 802.1ag optional type, length, and 15.1F4 15.1F5

value (TLVs) support Port Status TLV and
Interface Status TLV

IEEE 802.3ah distributed periodic packet 15.1F4 15.1F5

management (PPM) process , alarm
indication signal (AIS), and remote defect
indication (RDI)

Firewall filters and policers: 15.1F4 15.1F5

• Policer support for aggregated Ethernet NOTE: Layer 2 overhead adjustment NOTE: Layer 2 overhead adjustment
• Aggregate firewall-based policer for all (packet length used for the policer (packet length used for the policer
families of a logical interface included in the Layer 2 header) is not included in the Layer 2 header) is not
supported in 15.1F4. supported in 15.1F5.
• Intelligent hierarchial policers
• Set forwarding class and loss priority
for Routing Engine-generated packets
by using a firewall
• Physical interface policers, applying
policers to the entire port
• Lower policer limit from 32K to 8K
• Egress .1p MF and BA classification for
VPLS
• Differentiated Services Code Point
(DSCP) rewrite for IPv4 and IPv6

Flexible Ethernet encapsulation 15.1F4 15.1F5

Graceful Routing Engine Switchover 15.1F4 15.1F5

(GRES)

IGMPv3 support with snooping disabled 15.1F4 15.1F5

Ingress and egress hierarchical 15.1F4 15.1F5

class-of-service (CoS) shaping and
hierarchical-scheduler:

• Group of virtual LANs (VLANs) level

• VLAN level
• Port level

Inline flow monitoring 15.1F4 15.1F5

Intelligent Oversubscription on MIC and 15.1F4 15.1F5

MPC Interfaces Overview

Integrated routing and bridging (IRB) 15.1F4 15.1F5

376 Copyright © 2018, Juniper Networks, Inc.

 Chapter 16: MPC Protocol and Application Support for MX240, MX480, MX960, MX2010, MX2020, and MX10003

Table 45: Protocols and Applications Supported by MPC7Es in the MX240, MX480, MX960, MX2010, and MX2020
Routers (continued)

First Supported Junos OS Release for First Supported Junos OS Release for
Protocol or Application MPC7E-MRATE MPC7E-10G

Unified In-service software upgrade 17.4R1 17.4R1

(Unified ISSU)

Interoperability with MPCs 15.1F4 15.1F5

Interoperability with MS-DPCs - -

Interoperability with MX Series Flexible - -

PIC Concentrators (MX-FPC)

IPv4 15.1F4 15.1F5

IPv4 multicast 15.1F4 15.1F5

IPv6 15.1F4 15.1F5

IPv6 MLD 15.1F4 15.1F5

IPv6 multicast 15.1F4 15.1F5

IPv6 Neighbor Discovery 15.1F4 15.1F5

IS-IS 15.1F4 15.1F5

ITU-T Y.1731 timestamping support on MX 15.1F4 15.1F5

Series routers

First Supported Junos OS First Supported Junos OS

Flow monitoring and services Release for MPC7E-MRATE Release for MPC7E-10G

Inline IP Flow Information Export (IPFIX) 15.1F4 15.1F5

Active monitoring 15.1F4 15.1F5

Port mirroring family VPLS, bridge CCC encapsulation 15.1F4 15.1F5

(VPWS)

Packet slice for port mirroring 15.1F4 15.1F5

Flow monitoring on MS-MPCs 17.3R1 17.3R1

Inline flow monitoring 15.1F4 15.1F5

Labeled-switched-paths (LSPs) including 15.1F4 15.1F5

accounting, policers, and filtering

Copyright © 2018, Juniper Networks, Inc. 377

MX Series Interface Module Reference

Table 45: Protocols and Applications Supported by MPC7Es in the MX240, MX480, MX960, MX2010, and MX2020
Routers (continued)

First Supported Junos OS Release for First Supported Junos OS Release for
Protocol or Application MPC7E-MRATE MPC7E-10G

LDP 15.1F4 15.1F5

First Supported Junos OS First Supported Junos OS

Layer 2 Features Release for MPC7E-MRATE Release for MPC7E-10G

Trunk ports 15.1F4 15.1F5

Layer 2 support for MX Series Virtual Chassis 17.3R1 17.3R1

Layer 2 and Layer 2.5, IRB and Spanning Tree Protocols (xSTP) 15.1F4 15.1F5

IEEE 802.1ad provider bridges 15.1F4 15.1F5

Layer 2 protocol tunneling (L2PT) support 15.1F4 15.1F5

Layer 2 Tunneling Protocol (L2TP) 15.1F4 15.1F5

Multichassis LAG—active/active and active/standby 15.1F4 15.1F5

Multichassis LAG—active/active with IGMP snooping 15.1F4 15.1F5

Link aggregation group (LAG)—VLAN-CCC encapsulation 15.1F4 15.1F5

IGMP snooping with bridging, IRB, and VPLS 15.1F4 15.1F5

Layer 2 VPN interfaces support VLAN ID 15.1F4 15.1F5

list

Link aggregation (IEEE 802.3ad) 15.1F4 15.1F5

Link Aggregation Control Protocol (LACP) 15.1F4 15.1F5

Link Layer Discovery Protocol (LLDP) 15.1F4 15.1F5

Local loopback 15.1F4 15.1F5

378 Copyright © 2018, Juniper Networks, Inc.

 Chapter 16: MPC Protocol and Application Support for MX240, MX480, MX960, MX2010, MX2020, and MX10003

Table 45: Protocols and Applications Supported by MPC7Es in the MX240, MX480, MX960, MX2010, and MX2020
Routers (continued)

First Supported Junos OS Release for First Supported Junos OS Release for
Protocol or Application MPC7E-MRATE MPC7E-10G

MAC learning, policing, accounting, and 15.1F4 15.1F5

filtering

First Supported Junos OS First Supported Junos OS Release

MACSec Release for MPC7E-MRATE for MPC7E-10G

GCM-AES-128 MACSec Encryption, - 16.1R1

802.1AE-2006

GCM-AES-256 MACSec Encryption, - 16.2R1

802.1AEbn-2011

Mobile IP - -

Multichassis link aggregation 15.1F4 15.1F5

Multiple Tag Protocol Identifiers (TPIDs) 15.1F4 15.1F5

MPLS: 15.1F4 15.1F5

• Switching of pseudowire segments

(multisegment pseudowires with
BGP-L2VPN)
• LDP signaling for VPLS (LDP-VPLS)
and MAC flush message processing
(MAC-FLUSH-TLV)
• RSVP graceful restart interoperability
with Cisco using Nodal Hello
• Failure action on BFD session down of
RSVP LSPs
• OSPF and IS-IS loop-free alternates
(LFA)
• 4/5 label MPLS operation
• Virtual circuit connectivity verification
(VCCV) BFD
• Point to multipoint using the
enhanced-ip command (support for
NG-MVPN and P2MP load balancing
over aggregated Ethernet)
• MPLS-FRR bypass link protection
• Load sharing across 64 ECMP next
hops
• MPLS-FRR VPLS instance prioritization
• Five label stack on ingress

MPLS node protection, link protection, 15.1F4 15.1F5

and statistics for static LSPs

Copyright © 2018, Juniper Networks, Inc. 379

MX Series Interface Module Reference

Table 45: Protocols and Applications Supported by MPC7Es in the MX240, MX480, MX960, MX2010, and MX2020
Routers (continued)

First Supported Junos OS Release for First Supported Junos OS Release for
Protocol or Application MPC7E-MRATE MPC7E-10G

mvrp 15.1F4 15.1F5

Multitopology routing 15.1F4 15.1F5

Nonstop active routing (NSR) 15.1F4 15.1F5

OSPF 15.1F4 15.1F5

Packet mirroring 15.1F4 15.1F5

Precision Time Protocol (IEEE 1588) - -

IEEE 802.1ah provider backbone bridging - -

(PBB)

Push a tag on Ethernet VPLS and Ethernet 15.1F4 15.1F5

CCC tag encapsulations

RSVP 15.1F4 15.1F5

RIP 15.1F4 15.1F5

SNMP 15.1F4 15.1F5

Spanning Tree Protocols: 15.1F4 15.1F5

• IEEE 802.1s Multiple Spanning Tree

Protocol (MSTP) (part of IEEE 802.1Q
VLANs)
• IEEE 802.1w Rapid Spanning Tree
Protocol (RSTP)
• IEEE 802.1D Spanning Tree Protocol
(STP)
• Per-VLAN Spanning Tree (PVST)
• Bridge protocol data units (BPDUs)
guard and loop guard
• STP inter-protocol action profiles and
MAC flush (in VPLS multi-homing, flush
all MACs when there is a change in the
STP interface state due to root protect)

Subscriber management and services: 16.1R4; 17.1R1 16.1R4; 17.1R1

• Enhanced subscriber management

Synchronous Ethernet 16.1R1 16.1R1

380 Copyright © 2018, Juniper Networks, Inc.

 Chapter 16: MPC Protocol and Application Support for MX240, MX480, MX960, MX2010, MX2020, and MX10003

Table 45: Protocols and Applications Supported by MPC7Es in the MX240, MX480, MX960, MX2010, and MX2020
Routers (continued)

First Supported Junos OS Release for First Supported Junos OS Release for
Protocol or Application MPC7E-MRATE MPC7E-10G

Two-Way Active Measurement Protocol 16.1R4 16.1R4

(TWAMP)
NOTE: TWAMP is not supported on the NOTE: TWAMP is not supported on the
MX2020 and MX2010 chassis. MX2020 and MX2010 chassis.

Tunnel services 15.1F4 15.1F5

• Clear DF-Bit (Don't Fragment Bit)

Unified in-service software upgrade - -

(ISSU)

Unnumbered Ethernet Interface 15.1F4 15.1F5

VLANs IEEE 802.1Q: 15.1F4 15.1F5

• VLAN stacking and rewriting

• Flexible VLAN tagging
• IP service for nonstandard TPID and
stacked VLAN tags

Virtual Chassis: MPLS IPv4 and IPv6, 17.3R1 17.3R1

unicast, multicast forwarding, VPLS, NSR
for Layer 3/MPLS services

Virtual private LAN service (VPLS): 15.1F4 15.1F5

• BGP multihoming for inter-AS VPLS

• Gigabit Ethernet as core-facing
interface
• Configurable label block sizes
• Hashing L3/L4 fields under Ethernet
pseudowire for VPLS encapsulation,
CCC encapsulation, and MPLS
encapsulation
• VPLS flood forwarding table filter
(FTF), input FTF
• Broadcast, unicast unknown, and
multicast (BUM) traffic hashing over
LAG

Virtual private network (VPN) 15.1F4 15.1F5

Virtual Router Redundancy Protocol 15.1F4 15.1F5

(VRRP) for IPv4

VPLS packet flooding to the right set of 15.1F4 15.1F5

interfaces across mesh groups

Copyright © 2018, Juniper Networks, Inc. 381

MX Series Interface Module Reference

Table 45: Protocols and Applications Supported by MPC7Es in the MX240, MX480, MX960, MX2010, and MX2020
Routers (continued)

First Supported Junos OS Release for First Supported Junos OS Release for
Protocol or Application MPC7E-MRATE MPC7E-10G

WAN-PHY mode - -

Related • MPC7E (Multi-Rate) on page 130

Documentation
• MPC7E 10G on page 132

Protocols and Applications Supported by the MPC8E and MPC9E on the MX2010 and
MX2020 Routers

Table 41 on page 344 lists the protocols and applications supported by MPC8E and MPC9E
on the MX2010 and MX2020 routers.

An en dash indicates that the protocol or application is not supported.

Table 46: Protocols and Applications Supported by MPC8E and MPC9E on the MX2010 and MX2020 Routers

First Supported Junos OS Release

Protocol or Application MPC8E MPC9E

Access Node Control Protocol (ANCP) - -

Accepts traffic destined for generic routing encapsulation (GRE) tunnels or Distance 15.1F5 15.1F5
Vector Multicast Routing Protocol (DVMRP) (IP-in-IP) tunnels

• Dynamic
• Manual

Bidirectional Forwarding Detection protocol (BFD) 15.1F5 15.1F5

Border Gateway Protocol (BGP) 15.1F5 15.1F5

Bridge protocol data units (BPDUs) 15.1F5 15.1F5

BGP/MPLS virtual private networks (VPNs) 15.1F5 15.1F5

382 Copyright © 2018, Juniper Networks, Inc.

 Chapter 16: MPC Protocol and Application Support for MX240, MX480, MX960, MX2010, MX2020, and MX10003

Table 46: Protocols and Applications Supported by MPC8E and MPC9E on the MX2010 and MX2020
Routers (continued)

First Supported Junos OS Release

Protocol or Application MPC8E MPC9E

Class of service (CoS): 15.1F5 15.1F5

• Maintain CoS across internal tunnel interfaces

• Packet rewrites
• Behavior aggregate (BA) classification
• BA classification based on 802.1p of payload for core-facing VPLS interfaces
• BA DSCP classification of MPLS packets for L3VPN/VPLS LSI and MPLS
interfaces
• Rate-limit option for per-port queues
• BA DSCP classification for VPLS/CCC family
• Configurable .1p inheritance: push and swap from the hidden tag
• Configurable shaping overhead for scheduling

Class of service (CoS) per port: 15.1F5 15.1F5

• Eight queues per port

• Excess-rate and excess-priority configurations at the queue level
• Shaping at the port level
• Shaping at the queue level
• Scheduling of queues based on the weighted round-robin (WRR) per
excess-priority class
• Round-robin scheduling of the queues per priority class
• Weighted random early detection (WRED)

Class of service (CoS) per virtual LAN (VLAN): 15.1F5 15.1F5

• Accounting, filtering, and policing

• IEEE 802.1p rewrite
• Classification
• Tricolor marking

Class of service (CoS) per Point-to-Point Protocol over Ethernet (PPPoE) or - -

Dynamic Host Configuration Protocol (DHCP) subscriber interfaces:

• Accounting, filtering, and policing

• IEEE 802.1p rewrite
• Classification
• Excess-rate and excess-priority configuration at the queue level
• Tricolor marking
• Shaping at the queue level
• Scheduling of queues based on weighted round-robin (WRR) per priority class
• Weighted random early detection (WRED)

Damping 16.1R1 16.1R1

Copyright © 2018, Juniper Networks, Inc. 383

MX Series Interface Module Reference

Table 46: Protocols and Applications Supported by MPC8E and MPC9E on the MX2010 and MX2020
Routers (continued)

First Supported Junos OS Release

Protocol or Application MPC8E MPC9E

Distributed Denial-of-Service (DDoS) Protection 15.1F5 15.1F5

DVMRP and GRE support—access side and server side 15.1F5 15.1F5

Dynamic Power Management 15.1F5 15.1F5

Ethernet Ring Protection Switching with multiple G.8032 instances 15.1F5 15.1F5

Flexible Queuing Mode 15.1F5 15.1F5

IEEE 802.1ag Ethernet OAM Continuity Check protocol 15.1F5 15.1F5

IEEE 802.1ag Ethernet OAM Linktrace protocol 15.1F5 15.1F5

IEEE 802.1ag Ethernet OAM Loopback protocol 15.1F5 15.1F5

IEEE 802.1ag maintenance association intermediate point (MIP) support, continuity 15.1F5 15.1F5
check message (CCM), stacked VLAN tagging, trunk ports, support for VPLS/VPWS,
VLAN circuit cross-connect (CCC) encapsulation and translational cross-connect
(TCC) encapsulation

IEEE 802.1ag optional type, length, and value (TLVs) support Port Status TLV and 15.1F5 15.1F5
Interface Status TLV

IEEE 802.3ah distributed periodic packet management (PPM) process, alarm 15.1F5 15.1F5
indication signal (AIS), and remote defect indication (RDI)

Firewall filters and policers: 15.1F5 15.1F5

• Policer support for aggregated Ethernet

• Aggregate firewall-based policer for all families of a logical interface
• Intelligent hierarchical policers
• Set forwarding class and loss priority for Routing Engine-generated packets by
using a firewall
• Physical interface policers, applying policers to the entire port
• Lower policer limit from 32,000 to 8000
• Egress .1p MF and BA classification for VPLS
• Differentiated Services Code Point (DSCP) rewrite for IPv4 and IPv6

Flexible Ethernet encapsulation 15.1F5 15.1F5

Graceful Routing Engine Switchover (GRES) 15.1F5 15.1F5

IGMPv3 support with snooping disabled 15.1F5 15.1F5

384 Copyright © 2018, Juniper Networks, Inc.

 Chapter 16: MPC Protocol and Application Support for MX240, MX480, MX960, MX2010, MX2020, and MX10003

Table 46: Protocols and Applications Supported by MPC8E and MPC9E on the MX2010 and MX2020
Routers (continued)

First Supported Junos OS Release

Protocol or Application MPC8E MPC9E

Ingress and egress hierarchical class-of-service (CoS) shaping and 15.1F5 15.1F5
hierarchical-scheduler:

• Set of Interfaces
• VLAN level
• Port level

Inline flow monitoring 15.1F5 15.1F5

Intelligent Oversubscription 15.1F5 15.1F5

Integrated routing and bridging (IRB) 15.1F5 15.1F5

Unified In-service software upgrade (Unified ISSU) 17.4R1 17.4R1

Interoperability with existing MPCs 15.1F5 15.1F5

IPv4 15.1F5 15.1F5

IPv4 multicast 15.1F5 15.1F5

IPv6 15.1F5 15.1F5

IPv6 MLD 15.1F5 15.1F5

IPv6 multicast 15.1F5 15.1F5

IPv6 Neighbor Discovery 15.1F5 15.1F5

IS-IS 15.1F5 15.1F5

ITU-T Y.1731 timestamping support on MX Series routers 15.1F5 15.1F5

Flow monitoring and services: Release Release

• Active monitoring (cflowed version 9 templates) • 15.1F5 • 15.1F5

• Port mirroring family VPLS, bridge CCC encapsulation (VPWS) • 15.1F5 • 15.1F5
• Packet slice for port mirroring • 15.1F5 • 15.1F5
• Flow monitoring on MS-DPCs • - • -
• Inline flow monitoring on MPC8E and MPC9E • 15.1F5 • 15.1F5

Labeled-switched-paths (LSPs) including accounting, policers, and filtering 15.1F5 15.1F5

LDP 15.1F5 15.1F5

Copyright © 2018, Juniper Networks, Inc. 385

MX Series Interface Module Reference

Table 46: Protocols and Applications Supported by MPC8E and MPC9E on the MX2010 and MX2020
Routers (continued)

First Supported Junos OS Release

Protocol or Application MPC8E MPC9E

Layer 2 features: Release Release

• Trunk ports • 15.1F5 • 15.1F5

• Layer 2 support for MX Series Virtual Chassis • 17.3R1 • 17.3R1
• Layer 2 and Layer 2.5, IRB and spanning tree protocols (xSTP) • 15.1F5 • 15.1F5
• IEEE 802.1ad provider bridges • 15.1F5 • 15.1F5
• Layer 2 protocol tunneling (L2PT) support • 15.1F5 • 15.1F5
• Layer 2 Tunneling Protocol (L2TP) • 15.1F5 • 15.1F5
• Multichassis LAG—active/active and active/standby • 15.1F5 • 15.1F5
• Multichassis LAG—active/active with IGMP snooping • 15.1F5 • 15.1F5
• IGMP snooping with bridging, IRB, and VPLS • 15.1F5 • 15.1F5

Layer 2 VPN interfaces support VLAN ID list 15.1F5 15.1F5

Link aggregation (IEEE 802.3ad) 15.1F5 15.1F5

Link Aggregation Control Protocol (LACP) 15.1F5 15.1F5

Link Layer Discovery Protocol (LLDP) 15.1F5 15.1F5

Local loopback 15.1F5 15.1F5

MAC learning, policing, accounting, and filtering 15.1F5 15.1F5

Mobile IP - -

Multichassis Link Aggregation 15.1F5 15.1F5

Multiple Tag Protocol Identifiers (TPIDs) 15.1F5 15.1F5

386 Copyright © 2018, Juniper Networks, Inc.

 Chapter 16: MPC Protocol and Application Support for MX240, MX480, MX960, MX2010, MX2020, and MX10003

Table 46: Protocols and Applications Supported by MPC8E and MPC9E on the MX2010 and MX2020
Routers (continued)

First Supported Junos OS Release

Protocol or Application MPC8E MPC9E

MPLS: 15.1F5 15.1F5

• Switching of pseudowire segments (multisegment pseudowires with

BGP-L2VPN)
• LDP signaling for VPLS (LDP-VPLS) and MAC flush message processing
(MAC-FLUSH-TLV)
• RSVP graceful restart interoperability with Cisco using Nodal Hello
• Failure action on BFD session down of RSVP LSPs
• OSPF and IS-IS loop-free alternates (LFA)
• 4/5 label MPLS operation
• Virtual circuit connectivity verification (VCCV) BFD
• MPLS-FRR bypass link protection
• Load sharing across 64 ECMP next hops
• MPLS-FRR VPLS instance prioritization
• Five label stack on ingress

MPLS node protection, link protection, and statistics for static LSPs 15.1F5 15.1F5

mvrp - -

Multitopology routing 15.1F5 15.1F5

Nonstop active routing (NSR) 15.1F5 15.1F5

OSPF 15.1F5 15.1F5

Packet mirroring 15.1F5 15.1F5

Precision Time Protocol (IEEE 1588) - -

IEEE 802.1ah provider backbone bridging (PBB) - -

RSVP 15.1F5 15.1F5

RIP 15.1F5 15.1F5

SNMP 15.1F5 15.1F5

Copyright © 2018, Juniper Networks, Inc. 387

MX Series Interface Module Reference

Table 46: Protocols and Applications Supported by MPC8E and MPC9E on the MX2010 and MX2020
Routers (continued)

First Supported Junos OS Release

Protocol or Application MPC8E MPC9E

Spanning tree protocols: 15.1F5 15.1F5

• IEEE 802.1s Multiple Spanning Tree Protocol (MSTP) (part of IEEE 802.1Q VLANs)
• IEEE 802.1w Rapid Spanning Tree Protocol (RSTP)
• IEEE 802.1D Spanning Tree Protocol (STP)
• Per-VLAN Spanning Tree (PVST)
• Bridge protocol data units (BPDUs) guard and loop guard
• STP inter-protocol action profiles and MAC flush (in VPLS multi-homing, flush
all MACs when there is a change in the STP interface state due to root protect)

Subscriber management and services: 16.1R4; 17.1R1 16.1R4; 17.1R1

• Enhanced subscriber management

Synchronous Ethernet 16.1R1 16.1R1

Two-Way Active Measurement Protocol (TWAMP) - -

Tunnel services 15.1F5 15.1F5

• Clear DF-Bit (Don't Fragment Bit)

Unnumbered Ethernet Interface 15.1F5 15.1F5

VLANs IEEE 802.1Q: 15.1F5 15.1F5

• VLAN stacking and rewriting

• Channels defined by two stacked VLAN tags
• Flexible VLAN tagging
• IP service for nonstandard TPID and stacked VLAN tags

Virtual Chassis: MPLS IPv4 and IPv6, unicast, multicast forwarding, VPLS, NSR 17.3R1 17.3R1
for Layer 3/MPLS services

Virtual private LAN service (VPLS): 15.1F5 15.1F5

• BGP multihoming for inter-AS VPLS

• Gigabit Ethernet as core-facing interface
• Configurable label block sizes
• Hashing L3/L4 fields under Ethernet pseudowire for VPLS encapsulation, CCC
encapsulation, and MPLS encapsulation
• VPLS flood forwarding table filter (FTF), input FTF
• Broadcast, unicast unknown, and multicast (BUM) traffic hashing over LAG

Virtual private network (VPN) 15.1F5 15.1F5

388 Copyright © 2018, Juniper Networks, Inc.

 Chapter 16: MPC Protocol and Application Support for MX240, MX480, MX960, MX2010, MX2020, and MX10003

Table 46: Protocols and Applications Supported by MPC8E and MPC9E on the MX2010 and MX2020
Routers (continued)

First Supported Junos OS Release

Protocol or Application MPC8E MPC9E

Virtual Router Redundancy Protocol (VRRP) for IPv4 15.1F5 15.1F5

VPLS packet flooding to the right set of interfaces across mesh groups 15.1F5 -

MACSec Capabilities: Starting in Junos OS Release 17.4R1, the JNP-MIC-100G MIC 17.4R1 17.4R1
extends Media Access Control Security (MACsec) capabilities on MPC8E and
MPC9E MPCs installed in MX2010, MX2020, and MX2008 routers.

Only MPC8E/9E with JNP-MIC-100G MIC supports MACsec feature.

• GCM-AES-128 MACSec Encryption, 802.1AE-2006

• GCM-AES-256 MACSec Encryption, 802.1AEbn-2011
• GCM-AES-XPN-128 Cipher Suite, 802.1AEbw-2013
• GCM-AES-XPN-256 Cipher Suite, 802.1AEbw-2013

Release History Table Release Description

17.4R1 Starting in Junos OS Release 17.4R1, the JNP-MIC-100G MIC extends Media
Access Control Security (MACsec) capabilities on MPC8E and MPC9E MPCs
installed in MX2010, MX2020, and MX2008 routers.

Related • MPC8E on MX Series Routers Overview

Documentation
• MPC9E on MX Series Routers Overview

Protocols and Applications Supported by the MS-MIC and MS-MPC

Table 47 on page 389 contains the first Junos OS Release support for protocols and
applications on the MX104, MX240, MX480, MX960, MX2010, and MX2020 Multiservices
MIC (MS-MIC) and Multiservices MPC (MS-MPC). A dash indicates that the protocol or
application is not supported.

Table 47: Protocols and Applications Supported by the MS-MIC and MS-MPC

First Supported Junos OS

Software Feature Release

GRE Key –

GRE dont-fragment –

HTTP redirect services 15.1R4

Copyright © 2018, Juniper Networks, Inc. 389

MX Series Interface Module Reference

Table 47: Protocols and Applications Supported by the MS-MIC and MS-MPC (continued)

First Supported Junos OS

Software Feature Release

Stateful firewall 13.2R4

Network Address Translation (NAT) for IP addresses 13.2R4

Port Address Translation (PAT) for port numbers 13.2R4

IP Security (IPSec) encryption 13.2R4

Flow aggregation –

Active flow monitoring exports cflowd version 5 and version 8 records –

Active flow monitoring exports flow monitoring version 9 records, based on RFC 3954 13.2R4

Graceful Routing Engine Switchover (GRES) 13.3

NOTE: GRES is not supported for

MS-MIC on MX104 router.

Passive flow monitoring –

Passive flow collection –

Flow-tap –

Dynamic flow capture –

Real-time performance monitoring 13.3

Link Services –

MX Series Virtual Chassis with stateful firewall 14.2

MX Series Virtual Chassis with IPv4-to-IPv4 basic NAT, dynamic NAT, static destination 16.1R4
NAT, dynamic NAT with port mapping, and stateful NAT64.

Traffic sampling 13.2R4

Tunnel services: –

• IP-IP unicast tunneling

• GRE unicast tunneling—Supports GRE fragmentation
• Protocol Independent Multicast (PIM) sparse mode unicast tunneling

Virtual tunnel interface for Layer 3 VPNs –

Layer 2 Tunneling Protocol (L2TP) –

390 Copyright © 2018, Juniper Networks, Inc.

 Chapter 16: MPC Protocol and Application Support for MX240, MX480, MX960, MX2010, MX2020, and MX10003

Table 47: Protocols and Applications Supported by the MS-MIC and MS-MPC (continued)

First Supported Junos OS

Software Feature Release

Voice services: –

• Compressed Real-Time Transport Protocol (CRTP)

Encapsulations: –

• Multilink Frame Relay (MLFR)

• Multilink Point-to-Point Protocol (MLPP)

Related • MX Series MPC Overview on page 11

Documentation
• MPCs Supported by MX Series Routers on page 12

• Multiservices MIC on page 200

• Multiservices MPC on page 86

Protocols and Applications Supported by the MX10003 MPC (Multi-Rate) on the

MX10003 Router

Table 41 on page 344 lists the protocols and applications supported by MX10003 MPC
(Multi-Rate) on the MX10003 router.

An en dash indicates that the protocol or application is not supported.

Table 48: Protocols and Applications Supported by MX10003MPC on the MX10003 Router

First Supported Junos

Protocol or Application OS Release

Access Node Control Protocol (ANCP) -

Accepts traffic destined for generic routing encapsulation (GRE) tunnels or Distance Vector Multicast 17.3R1
Routing Protocol (DVMRP) (IP-in-IP) tunnels

• Dynamic
• Manual

Bidirectional Forwarding Detection protocol (BFD) 17.3R1

Border Gateway Protocol (BGP) 17.3R1

Bridge protocol data units (BPDUs) 17.3R1

BGP/MPLS virtual private networks (VPNs) 17.3R1

Copyright © 2018, Juniper Networks, Inc. 391

MX Series Interface Module Reference

Table 48: Protocols and Applications Supported by MX10003MPC on the MX10003 Router (continued)

First Supported Junos

Protocol or Application OS Release

Class of service (CoS): 17.3R1

• Maintain CoS across internal tunnel interfaces

• Packet rewrites
• Behavior aggregate (BA) classification
• BA classification based on 802.1p of payload for core-facing VPLS interfaces
• BA DSCP classification of MPLS packets for L3VPN/VPLS LSI and MPLS interfaces
• Rate-limit option for per-port queues
• BA DSCP classification for VPLS/CCC family
• Configurable .1p inheritance: push and swap from the hidden tag
• Configurable shaping overhead for scheduling

Class of service (CoS) per port: 17.3R1

• Eight queues per port

• Excess-rate and excess-priority configurations at the queue level
• Shaping at the port level
• Shaping at the queue level
• Scheduling of queues based on the weighted round-robin (WRR) per excess-priority class
• Round-robin scheduling of the queues per priority class
• Weighted random early detection (WRED)

Class of service (CoS) per virtual LAN (VLAN): 17.3R1

• Accounting, filtering, and policing

• IEEE 802.1p rewrite
• Classification
• Tricolor marking

Class of service (CoS) per Point-to-Point Protocol over Ethernet (PPPoE) or Dynamic Host 17.3R1
Configuration Protocol (DHCP) subscriber interfaces:

• Accounting, filtering, and policing

• IEEE 802.1p rewrite
• Classification
• Excess-rate and excess-priority configuration at the queue level
• Tricolor marking
• Shaping at the queue level
• Scheduling of queues based on weighted round-robin (WRR) per priority class
• Weighted random early detection (WRED)

Damping 17.3R1

Distributed Denial-of-Service (DDoS) Protection 17.3R1

DVMRP and GRE support—access side and server side 17.3R1

392 Copyright © 2018, Juniper Networks, Inc.

 Chapter 16: MPC Protocol and Application Support for MX240, MX480, MX960, MX2010, MX2020, and MX10003

Table 48: Protocols and Applications Supported by MX10003MPC on the MX10003 Router (continued)

First Supported Junos

Protocol or Application OS Release

Dynamic Power Management 17.3R1

Ethernet Ring Protection Switching with multiple G.8032 instances 17.3R1

Flexible Queuing Mode 17.3R1

IEEE 802.1ag Ethernet OAM Continuity Check protocol 17.3R1

IEEE 802.1ag Ethernet OAM Linktrace protocol 17.3R1

IEEE 802.1ag Ethernet OAM Loopback protocol 17.3R1

IEEE 802.1ag maintenance association intermediate point (MIP) support, continuity check message 17.3R1
(CCM), stacked VLAN tagging, trunk ports, support for VPLS/VPWS, VLAN circuit cross-connect
(CCC) encapsulation and translational cross-connect (TCC) encapsulation

IEEE 802.1ag optional type, length, and value (TLVs) support Port Status TLV and Interface Status 17.3R1
TLV

IEEE 802.3ah distributed periodic packet management (PPM) process, alarm indication signal 17.3R1
(AIS), and remote defect indication (RDI)

Firewall filters and policers: 17.3R1

• Policer support for aggregated Ethernet

• Aggregate firewall-based policer for all families of a logical interface
• Intelligent hierarchical policers
• Set forwarding class and loss priority for Routing Engine-generated packets by using a firewall
• Physical interface policers, applying policers to the entire port
• Lower policer limit from 32,000 to 8000
• Egress .1p MF and BA classification for VPLS
• Differentiated Services Code Point (DSCP) rewrite for IPv4 and IPv6

Flexible Ethernet encapsulation 17.3R1

Graceful Routing Engine Switchover (GRES) 17.3R1

IGMPv3 support with snooping disabled 17.3R1

Ingress and egress hierarchical class-of-service (CoS) shaping and hierarchical-scheduler: 17.3R1

• Set of Interfaces
• VLAN level
• Port level

Inline flow monitoring 17.3R1

Copyright © 2018, Juniper Networks, Inc. 393

MX Series Interface Module Reference

Table 48: Protocols and Applications Supported by MX10003MPC on the MX10003 Router (continued)

First Supported Junos

Protocol or Application OS Release

Intelligent Oversubscription 17.3R1

Integrated routing and bridging (IRB) 17.3R1

Interoperability with existing MPCs 17.3R1

IPv4 17.3R1

IPv4 multicast 17.3R1

IPv6 17.3R1

IPv6 MLD 17.3R1

IPv6 multicast 17.3R1

IPv6 Neighbor Discovery 17.3R1

IS-IS 17.3R1

ITU-T Y.1731 timestamping support on MX Series routers -

Flow monitoring and services: Release

• Active monitoring (cflowed version 9 templates) • 17.3R1

• Port mirroring family VPLS, bridge CCC encapsulation (VPWS) • 17.3R1
• Packet slice for port mirroring • 17.3R1
• Flow monitoring on MS-DPCs • -
• Inline flow monitoring • 17.3R1

Labeled-switched-paths (LSPs) including accounting, policers, and filtering 17.3R1

LDP 17.3R1

Layer 2 features: Release

• Trunk ports • 17.3R1

• Layer 2 support for MX Series Virtual Chassis • -
• Layer 2 and Layer 2.5, IRB and spanning tree protocols (xSTP) • 17.3R1
• IEEE 802.1ad provider bridges • 17.3R1
• Layer 2 protocol tunneling (L2PT) support • 17.3R1
• Layer 2 Tunneling Protocol (L2TP) • 17.3R1
• Multichassis LAG—active/active and active/standby • 17.3R1
• Multichassis LAG—active/active with IGMP snooping • 17.3R1
• IGMP snooping with bridging, IRB, and VPLS • 17.3R1

394 Copyright © 2018, Juniper Networks, Inc.

 Chapter 16: MPC Protocol and Application Support for MX240, MX480, MX960, MX2010, MX2020, and MX10003

Table 48: Protocols and Applications Supported by MX10003MPC on the MX10003 Router (continued)

First Supported Junos

Protocol or Application OS Release

Layer 2 VPN interfaces support VLAN ID list 17.3R1

Link aggregation (IEEE 802.3ad) 17.3R1

Link Aggregation Control Protocol (LACP) 17.3R1

Link Layer Discovery Protocol (LLDP) 17.3R1

Local loopback 17.3R1

MAC learning, policing, accounting, and filtering 17.3R1

MACSec with GCM-AES-256 Encryption and GCM-AES-XPN-256 Encryption 17.3R2

NOTE: MACSec is supported on JNP-MIC1-MACSEC only.

Mobile IP -

Multichassis Link Aggregation 17.3R1

Multiple Tag Protocol Identifiers (TPIDs) 17.3R1

MPLS: 17.3R1

• Switching of pseudowire segments (multisegment pseudowires with BGP-L2VPN)

• LDP signaling for VPLS (LDP-VPLS) and MAC flush message processing (MAC-FLUSH-TLV)
• RSVP graceful restart interoperability with Cisco using Nodal Hello
• Failure action on BFD session down of RSVP LSPs
• OSPF and IS-IS loop-free alternates (LFA)
• 4/5 label MPLS operation
• Virtual circuit connectivity verification (VCCV) BFD
• MPLS-FRR bypass link protection
• Load sharing across 64 ECMP next hops
• MPLS-FRR VPLS instance prioritization
• Five label stack on ingress

MPLS node protection, link protection, and statistics for static LSPs 17.3R1

mvrp -

Multitopology routing 17.3R1

Nonstop active routing (NSR) 17.3R1

OSPF 17.3R1

Copyright © 2018, Juniper Networks, Inc. 395

MX Series Interface Module Reference

Table 48: Protocols and Applications Supported by MX10003MPC on the MX10003 Router (continued)

First Supported Junos

Protocol or Application OS Release

Packet mirroring 17.3R1

Precision Time Protocol (IEEE 1588) 17.3R1

IEEE 802.1ah provider backbone bridging (PBB) -

RSVP 17.3R1

RIP 17.3R1

SNMP 17.3R1

Spanning tree protocols: 17.3R1

• IEEE 802.1s Multiple Spanning Tree Protocol (MSTP) (part of IEEE 802.1Q VLANs)
• IEEE 802.1w Rapid Spanning Tree Protocol (RSTP)
• IEEE 802.1D Spanning Tree Protocol (STP)
• Per-VLAN Spanning Tree (PVST)
• Bridge protocol data units (BPDUs) guard and loop guard
• STP inter-protocol action profiles and MAC flush (in VPLS multi-homing, flush all MACs when
there is a change in the STP interface state due to root protect)

Subscriber management and services: 17.3R1

• Enhanced subscriber management

Synchronous Ethernet 17.3R1

Two-Way Active Measurement Protocol (TWAMP) -

Tunnel services 17.3R1

• Clear DF-Bit (Don't Fragment Bit)

Unnumbered Ethernet Interface 17.3R1

VLANs IEEE 802.1Q: 17.3R1

• VLAN stacking and rewriting

• Channels defined by two stacked VLAN tags
• Flexible VLAN tagging
• IP service for nonstandard TPID and stacked VLAN tags

Virtual Chassis: MPLS IPv4 and IPv6, unicast, multicast forwarding, VPLS, NSR for Layer 3/MPLS --
services

396 Copyright © 2018, Juniper Networks, Inc.

 Chapter 16: MPC Protocol and Application Support for MX240, MX480, MX960, MX2010, MX2020, and MX10003

Table 48: Protocols and Applications Supported by MX10003MPC on the MX10003 Router (continued)

First Supported Junos

Protocol or Application OS Release

Virtual private LAN service (VPLS): 17.3R1

• BGP multihoming for inter-AS VPLS

• Gigabit Ethernet as core-facing interface
• Configurable label block sizes
• Hashing L3/L4 fields under Ethernet pseudowire for VPLS encapsulation, CCC encapsulation,
and MPLS encapsulation
• VPLS flood forwarding table filter (FTF), input FTF
• Broadcast, unicast unknown, and multicast (BUM) traffic hashing over LAG

Virtual private network (VPN) 17.3R1

Virtual Router Redundancy Protocol (VRRP) for IPv4 17.3R1

VPLS packet flooding to the right set of interfaces across mesh groups -

Copyright © 2018, Juniper Networks, Inc. 397

MX Series Interface Module Reference

398 Copyright © 2018, Juniper Networks, Inc.