Juniper Networks, Junos, Steel-Belted Radius, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the United
States and other countries. The Juniper Networks Logo, the Junos logo, and JunosE are trademarks of Juniper Networks, Inc. All other
trademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners.
Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify,
transfer, or otherwise revise this publication without notice.
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
http://www.juniper.net/support/eula.html. By downloading, installing or using such software, you agree to the terms and conditions of
Tools and Parts Required for MX240 Router Connections . . . . . . . . . . . . . . . . . . 205
Connecting the MX240 Router to Management and Alarm Devices . . . . . . . . . . 205
Connecting the MX240 Router to a Network for Out-of-Band
Connecting the MX240 Router to a Management Console or Auxiliary
Connecting the MX240 Router to an External Alarm-Reporting Device . . . . 207
Connecting the MX240 Router to a Network for Out-of-Band Management . . . 208
Connecting the MX240 Router to a Management Console or Auxiliary Device . . 209
Connecting the MX240 Router to an External Alarm-Reporting Device . . . . . . . 210
Connecting DPC, MPC, MIC, or PIC Cables to the MX240 Router . . . . . . . . . . . . . 211
To obtain the most current version of all Juniper Networks®technical documentation,
see the product documentation page on the Juniper Networks website at
http://www.juniper.net/techpubs/.
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 http://www.juniper.net/books.
Supported Platforms
For the features described in this document, the following platforms are supported:
•
MX240
Documentation Conventions
Table 1 on page xxvi defines notice icons used in this guide.
Represents names of configuration
statements, commands, files, and
directories;configurationhierarchy levels;
or labels on routing platform
components.
About the Documentation
ExamplesDescriptionConvention
•
To configure a stub area, include the
stub statement at the [edit protocols
ospf area area-id] hierarchy level.
•
The console port is labeled CONSOLE.
stub <default-metric metric>;Encloses optional keywords or variables.< > (angle brackets)
| (pipe symbol)
# (pound sign)
[ ] (square brackets)
Indention and braces ( { } )
; (semicolon)
GUI Conventions
Bold text like this
Indicates a choice between the mutually
exclusivekeywords or variables on either
side of the symbol. The set of choices is
often enclosed in parentheses for clarity.
same line as the configurationstatement
to which it applies.
Encloses a variable for which you can
substitute one or more values.
Identifies a level in the configuration
hierarchy.
Identifies a leaf statement at a
configuration hierarchy level.
Representsgraphical user interface (GUI)
items you click or select.
broadcast | multicast
(string1 | string2 | string3)
rsvp { # Required for dynamic MPLS onlyIndicates a comment specified on the
community name members [
community-ids ]
[edit]
routing-options {
static {
route default {
nexthop address;
retain;
}
}
}
•
In the Logical Interfaces box, select
All Interfaces.
•
To cancel the configuration, click
Cancel.
> (bold right angle bracket)
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 http://www.juniper.net/techpubs/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
http://www.juniper.net/techpubs/feedback/.
Separates levels in a hierarchy of menu
selections.
In the configuration editor hierarchy,
select Protocols>Ospf.
E-mail—Sendyour comments to techpubs-comments@juniper.net.Include the document
or topic name, URL or page number, and software version (if applicable).
Requesting Technical Support
Technical product support is available through the Juniper Networks Technical Assistance
Center (JTAC). If you are a customer with an active 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
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 solutions and answer questions using our Knowledge Base: http://kb.juniper.net/
•
Download the latest versions of software and review release notes:
http://www.juniper.net/customers/csc/software/
•
Search technical bulletins for relevant hardware and software notifications:
http://kb.juniper.net/InfoCenter/
•
Join and participate in the Juniper Networks Community Forum:
http://www.juniper.net/company/communities/
•
Open a case online in the CSC Case Management tool: http://www.juniper.net/cm/
To verify service entitlement by product serial number, use our Serial Number Entitlement
(SNE) Tool: https://tools.juniper.net/SerialNumberEntitlementSearch/
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 http://www.juniper.net/cm/.
•
Call 1-888-314-JTAC (1-888-314-5822 toll-free in the USA, Canada, and Mexico).
The MX240 3D Universal Edge Router is an Ethernet-optimized edge router that provides
both switching and carrier-class Ethernet routing. The MX240 enables a wide range of
business and residential applications and services, including high-speed transport and
VPN services, next-generation broadband multiplay services, high-speed Internet and
data center internetworking.
The MX240 router is five rack units (U) tall. Several routers can be stacked in a single
floor-to-ceiling rack, for increased port density per unit of floor space.
Fully populated, the MX240 provides a maximum aggregate switch fabric capacity of
up to 1.92 Tbps and line-rate throughput for up to 48 10-Gigabit Ethernet ports, or four
100-Gigabit Ethernet and eight 10-Gigabit Ethernet ports, or twelve 40-Gigabit Ethernet
ports.
Table 3 on page 3 lists the MX240 router capacity.
Table 3: MX240 Router Capacity
The router provides two dedicated line card slots for Dense Port Concentrators (DPCs),
Modular Port Concentrators (MPCs), or Flexible PIC Concentrators (FPCs). DPCs and
MPCs each install into a single line-card slot. The FPC installs into both slots. The router
also provides one dedicated slot for a Switch Control Board (SCB), and one multifunction
slot for either one DPC, MPC, or SCB. Optionally, an FPC can be installed in both the
multifunction slot and lowest dedicated line card slot. The line cards are connected to
one or two SCBs. See Table 4 on page 4 for the supported SCBs.
An FPC supports up to two PICs. An MPC supports up to two Modular Interface Cards
(MICs).
Each DPC includes two or four Packet Forwarding Engines. Each Packet Forwarding
Engine enables a throughput of 10 Gbps.
Several types of line cards, are available. For a list of the supported line cards, see the
MX Series Interface Module Reference.
Three SCBs are available for the MX240 routers—the SCB, the SCBE, and the SCBE2.
Table 4 on page 4 lists the MX240 SCBs.
Table 4: SCB Comparison
Switch Fabric CapacityDescriptionModel Number
1.92 Tbps half duplexEnhanced MX Switch Control Board (SCBE2)SCBE2- MX-BB
Related
Documentation
.96 TbpsEnhanced Switch Control Board (SCBE)SCBE-MX-BB
.48 TbpsSwitch Control Board (SCB)SCB-MX-BB
The connections between line cards and SCBs are organized in three groups:
•
Switch fabric—Connects the line cards and provides for packet transport between the
line cards.
•
Control plane—Gigabit Ethernet links between the combined SCBs/Routing Engines
and each DPC, MPC, or FPC. All board-to-board information is passed over Ethernet
except for low-level status and commands.
•
Management signals—Provide low-level status diagnostic support.
• MX240 Component Redundancy on page 7
• MX240 Chassis Description on page 8
• MX240 Host Subsystem Description on page 21
• MX240 Craft Interface Overview on page 12
• MX240 Power System Overview on page 85
• MX240 Cooling System Description on page 17
• MX240 Router Physical Specifications on page 103
Outstanding Issues with the MX240 Router on page 5
•
Errata with the MX240 Router Documentation on page 6
Outstanding Issues with the MX240 Router
This topic lists outstanding hardware issues with the MX240 3D Universal Edge router.
For information about software issues, see the Junos OS Release Notes.
•
On the MX240 DC high capacity power supplies, the input mode switch tells the system
what capacity feed is connected (60A or 70A). This is used for power inventory
management. When the input mode switch is set to '0' (zero): expect 60A feeds, with
a voltage range of -39V to -72VDC. When the input mode switch is set to '1' (one),
expect either a 70A feed or a 60A feed with minimum voltage of 42V and up. The
default setting of the input mode is 1 (e.g. 60A with voltages above 42VDC, or 70A).
Known bug: In Junos OS Releases 10.0R3, 10.1R2, and 10.2R1, the MX240 DC high
capacity power supply input mode switch status is not properly reflected in the power
inventory management, generating alarms incorrectly. This does not have any effect
on the operation of the supply. [PR532230]
Related
Documentation
Important notes:
•
All supplies should have the same feed setting.
•
Correct usage of the feed setting is required for all supplies in order to get the desired
power inventory management.
The XFP cages and optics on the MX240 router are industry standard parts that have
limited tactile feedback for insertion of optics and fiber. You need to insert the optics
and fiber firmly until the latch is securely in place. [PR/98055]
•
Do not mix AC and DC power supplies on an MX240 router. Mixing of AC supplies and
DC supplies may damage your chassis. [PR/233340]
Errata with the MX240 Router Documentation on page 6•
This topic lists the outstanding issues with the documentation:
•
In the low-line(110 V) AC power configuration (nonredundant), two AC power supplies
should be located horizontally at the rear of the chassis in slots PEM0 and PEM1 (left
to right).
Related
Documentation
• Outstanding Issues with the MX240 Router on page 5
MX240 Router Hardware and CLI Terminology Mapping on page 10
•
MX240 Craft Interface Overview on page 12
•
MX240 Alarm Relay Contacts on the Craft Interface on page 13
•
MX240 Alarm LEDs and Alarm Cutoff/Lamp Test Button on page 13
•
MX240 Component LEDs on the Craft Interface on page 14
MX240 Component Redundancy
The MX240 chassis provides redundancy and resiliency. The hardware system is fully
redundant, including power supplies, Routing Engines, and SCBs.
A fully configured router is designed so that no single point of failure can cause the entire
system to fail. Only a fully configured router provides complete redundancy. All other
configurations provide partial redundancy. The following major hardware components
are redundant:
•
Host subsystem—Thehost subsystem consists of a Routing Engine functioning together
with an SCB. The router can have one or two host subsystems. If two host subsystems
are installed, one functions as the master and the other functions as the backup. If the
master host subsystem (or either of its components) fails, the backup can take over
as the master. To operate, each host subsystem requires a Routing Engine installed
directly into in an SCB.
•
In the high-line (220 V) AC power configuration, the MX240 router contains one or two
AC power supplies, located horizontally at the rear of the chassis in slots PEM0 and
PEM2 (left to right). The high-line configuration requires one power supply, with the
second power supply providing redundancy. Each AC power supply provides power to
all components in the router. When two power supplies are present, they share power
almost equally within a fully populated system. If one power supply fails or is removed,
the remaining power supply assumes the entire electrical load without interruption.
One power supply can provide the maximum configuration with full power for as long
as the router is operational.
In the low-line (110 V) AC power configuration, the MX240 router contains either two
AC power supplies (nonredundant), located horizontally at the rear of the chassis in
slots PEM0 and PEM1 (left to right); or four AC power supplies (redundant), located in
slots PEM0 through PEM3 (left to right). The low-line configuration requires two power
supplies, and the third and fourth power supplies provide redundancy. Each AC power
supply provides power to all components in the router. When two power supplies are
present, they share power almost equally within a fully populatedsystem. If one power
supply in a redundant configuration fails or is removed, the remaining power supplies
assume the entire electrical load without interruption. Two power supplies provide the
maximum configuration with full power for as long as the router is operational.
•
Cooling system—Thecooling system has redundant components, which are controlled
by the host subsystem. If one of the fans fails, the host subsystem increases the speed
of the remaining fans to provide sufficient cooling for the router indefinitely.
Related
Documentation
MX240 Chassis Description on page 8•
• MX240 Midplane Description on page 22
MX240 Chassis Description
The router chassis is a rigid sheet metal structure that houses all the other router
components (see Figure 1 on page 8, Figure 2 on page 9, Figure 3 on page 9,
Figure 4 on page 10, and Figure 5 on page 10). The chassis measures 8.71 in. (22.1 cm)
high, 17.45 in. (44.3 cm) wide, and 24.5 in. (62.2 cm) deep (from the front-mounting
brackets to the rear of the chassis). The chassis installs in standard 800-mm deep (or
larger) enclosed cabinets, 19-in. equipment racks, or telco open-frame racks.
Figure 1: Front View of a Fully ConfiguredMX240 Router
Table 5: MX240 Router Hardware Components and CLI Terminology (continued)
DescriptionCLI NameHardware Model NumberComponent
PWR-MX480-2400-DC
panel
Related
Documentation
MX240 Router Overview on page 3•
• MX240 DPC Port and Interface Numbering on page 49
• MX240 MIC Port and Interface Numbering on page 72
• MX240 PIC Port and Interface Numbering on page 57
• MX Series Router Interface Names
MX240 Craft Interface Overview
The craft interface allows you to view status and troubleshooting information at a glance
and to perform many system control functions. It is hot-insertable and hot-removable.
The craft interface is located on the front of the router above the card cage and contains
LEDs for the router components, the alarm relay contacts, and alarm cutoff button. See
Figure 6 on page 12.
DC Power Entry ModulePWR-MX480-DCDC power supply
DC Power Entry ModulePWR-MX480-1600-DC
DC 2.4kW Power Entry
Module
N/APWR-BLANK-MX960Power supply blank
“MX240 DC Power Supply
Description” on page 88
“MX240 Power System Overview”
on page 85
Figure 6: Front Panel of the Craft Interface
NOTE: At least one SCB must be installed in the router for the craft interface
to obtain power.
Related
Documentation
MX240 Alarm LEDs and Alarm Cutoff/Lamp Test Button on page 13•
• MX240 Alarm Relay Contacts on the Craft Interface on page 13
• MX240 Component LEDs on the Craft Interface on page 14
The craft interface has two alarm relay contacts for connecting the router to external
alarm devices (see Figure 7 on page 13). Whenever a system condition triggers either the
red or yellow alarm on the craft interface, the alarm relay contacts are also activated.
The alarm relay contacts are located on the upper right of the craft interface.
Figure 7: Alarm Relay Contacts
Chapter 3: Chassis Components and Descriptions
Related
Documentation
MX240 Craft Interface Overview on page 12•
• MX240 Alarm LEDs and Alarm Cutoff/Lamp Test Button on page 13
• MX240 Component LEDs on the Craft Interface on page 14
• Connecting the MX240 Router to Management and Alarm Devices on page 205
MX240 Alarm LEDs and Alarm Cutoff/Lamp Test Button
Two large alarm LEDs are located at the upper right of the craft interface. The circular
red LED lights to indicate a critical condition that can result in a system shutdown. The
triangular yellow LED lights to indicate a less severe condition that requires monitoring
or maintenance. Both LEDs can be lit simultaneously.
A condition that causes an LED to light also activates the corresponding alarm relay
contact on the craft interface.
To deactivate red and yellow alarms, press the button labeled ACO/LT (for “alarm
cutoff/lamp test”), which is locatedto the right of the alarm LEDs. Deactivating an alarm
turns off both LEDs and deactivates the device attached to the corresponding alarm
relay contact on the craft interface.
Table 6 on page 14 describes the alarm LEDs and alarm cutoff button in more detail.
Table 6: Alarm LEDs and Alarm Cutoff/Lamp Test Button
DescriptionStateColorShape
Critical alarm LED—Indicatesa critical condition that
can cause the router to stop functioning. Possible
causes include component removal, failure, or
overheating.
Warningalarm LED—Indicates a serious but nonfatal
error condition, such as a maintenance alert or a
significant increase in component temperature.
Alarm cutoff/lamp test button—Deactivatesred and
yellowalarms. Causes all LEDs on the craft interface
to light (for testing) when pressed and held.
Related
Documentation
On steadilyRed
On steadilyYellow
––
MX240 Craft Interface Overview on page 12•
• MX240 Alarm Relay Contacts on the Craft Interface on page 13
• MX240 Component LEDs on the Craft Interface on page 14
• Connecting the Alarm Relay Wires to the MX240 Craft Interface on page 257
MX240 Component LEDs on the Craft Interface
•
Host Subsystem LEDs on the MX240 Craft Interface on page 14
•
Power Supply LEDs on the MX240 Craft Interface on page 15
•
DPC and MPC LEDs on the MX240 Craft Interface on page 15
•
FPC LEDs on the MX240 Craft Interface on page 15
•
SCB LEDs on the MX240 Craft Interface on page 16
•
Fan LED on the MX240 Craft Interface on page 16
Host Subsystem LEDs on the MX240 Craft Interface
Each host subsystem has three LEDs, located in the middle of the craft interface, that
indicate its status. The LEDs labeled RE0 show the status of the Routing Engine in slot
0 and the SCB in slot 0. The LEDs labeled RE1 show the status of the Routing Engine and
SCB in slot 1/0. Table 7 on page 14 describes the functions of the host subsystem LEDs.
Table 7: Host Subsystem LEDs on the Craft Interface
DescriptionStateColorLabel
Host is functioning as the master.On steadilyGreenMASTER
Host is online and is functioning normally.On steadilyGreenONLINE
Table 7: Host Subsystem LEDs on the Craft Interface (continued)
Power Supply LEDs on the MX240 Craft Interface
Each power supply has two LEDs on the craft interface that indicate its status. The LEDs,
labeled 0 through 3, are located on the upper left of the craft interface next to the PEM
label. Table 8 on page 15 describes the functions of the power supply LEDs on the craft
interface.
Table 8: Power Supply LEDs on the Craft Interface
Chapter 3: Chassis Components and Descriptions
DescriptionStateColorLabel
Host is installed but the Routing Engine is offline.On steadilyRedOFFLINE
Host is not installed.Off–
DescriptionStateColorLabel
Power supply is functioning normally.On steadilyGreenPEM
DPC and MPC LEDs on the MX240 Craft Interface
Each DPC or MPC has LEDs on the craft interface that indicate its status. The LEDs,
labeled 1/0, 1, and 2, (1/0 shows status of either SCB1, DPC0, MPC0, or FPC0 depending
on which component is installed in the slot), are located along the bottom of the craft
interface. See Table 9 on page 15.
Table 9: DPC and MPC LEDs on the Craft Interface
FPC LEDs on the MX240 Craft Interface
An FPC takes up two DPC slots when installedin an MX Series router. An FPC LED located
along the bottom of the craft interface indicates status. The LED corresponds to the
lowest DPC slot number in which the FPC is installed. See Table 10 on page 16.
Power supply has failed or power input has failed.On steadilyRed
Each SCB has two LEDs on the craft interface that indicates its status. The SCB LEDs,
labeled 0 and 1/0 (1/0 shows the status of either SCB1 DPC0, or FPC0 depending on
which component is installed in the multifunction slot), are located along the bottom of
the craft interface. Table 11 on page 16 describes the functions of the SCB LEDs.
DescriptionStateColorLabel
FPC is functioning normally.On steadilyGreenOK
FPC is transitioning online or offline.Blinking
The slot is not online.Off–
FPC has failed.On steadilyRedFAIL
Table 11: SCB LEDs on the Craft Interface
Fan LED on the MX240 Craft Interface
The fan LEDs are located on the top left of the craft interface. Table 12 on page 16
describes the functions of the fan LEDs.
Table 12: Fan LEDs on the Craft Interface
DescriptionStateColorLabel
SCB: Fabric and control board functioning normally.On steadilyGreenOK
SCB is transitioning online or offline.Blinking
The slot is not online.Off–
SCB has failed.On steadilyRedFAIL
DescriptionStateColorLabel
Fan is functioning normally.On steadilyGreenFAN
Fan has failed.On steadilyRed
Related
Documentation
• MX240 Craft Interface Overview on page 12
• MX240 Alarm LEDs and Alarm Cutoff/Lamp Test Button on page 13
• MX240 Alarm Relay Contacts on the Craft Interface on page 13
The cooling system consists of the following components:
•
Fan tray
•
Air filter
The cooling system components work together to keep all router components within the
acceptable temperature range (see Figure 8 on page 17, Figure 9 on page 18, and
Figure 10 on page 18). The router has one fan tray and one air filter that install vertically
in the rear of the router. The fan tray contains three fans. The MX Series high-capacity
fan trays satisfy cooling requirements for high-density DPCs and MPCs, and must be
upgraded for proper cooling.
The air intake to cool the chassis is located on the side of the chassis next to the air filter.
Air is pulled through the chassis toward the fan tray, where it is exhausted out the side
of the system.The air intake to cool the power supplies is located in the front of the router
above the craft interface. The exhaust for the power supplies is located on the rear
bulkhead power supplies.
Figure 8: Airflow Through the Chassis
The host subsystem monitors the temperature of the router components. When the
router is operating normally, the fans function at lower than full speed. If a fan fails or
the ambient temperature rises above a threshold, the speed of the remaining fans is
automatically adjusted to keep the temperature within the acceptable range. If the
ambient maximum temperature specification is exceeded and the system cannot be
adequately cooled,the Routing Engine shuts down the systemby disabling output power
from each power supply.
Figure 9: Fan Tray
Related
Documentation
MX240 Fan LED
Figure 10: Air Filter
MX240 Chassis Description on page 8•
• Troubleshooting the MX240 Cooling System on page 380
Each fan has an LED that displays its status. The fan LEDs are located on the top left of
the craft interface. For more information, see “Fan LED on the MX240 Craft Interface”
RE-S-1800 Routing Engine Description for MX Series on page 26
•
RE-S-X6-64G Routing Engine Description for MX Series on page 28
•
MX240 Routing Engine LEDs on page 30
•
RE-S-1800 Routing Engine LEDs on page 30
•
RE-S-X6-64G Routing Engine LEDs on page 31
•
Routing Engine Specifications on page 32
•
Supported Routing Engines by Router on page 34
MX240 Host Subsystem Description
The host subsystem provides the routing and system management functions of the
router. You can install one or two host subsystems on the router. Each host subsystem
functions as a unit; the Routing Engine must be installed directly into the Switch Control
Board.
NOTE: We recommend that you install two host subsystems for redundant
protection. If you install only one host subsystem, we recommend that you
install it in slot 0.
Each host subsystem has three LEDs that display its status. The host subsystem LEDs
are located in the middle of the craft interface.
Related
Documentation
Host Subsystem LEDs on the MX240 Craft Interface on page 14•
• Maintaining the MX240 Host Subsystem on page 358
Each host subsystem has three LEDs that display its status. The host subsystem LEDs
are located in the middle of the craft interface. For more information, see “Host Subsystem
LEDs on the MX240 Craft Interface” on page 14.
Related
Documentation
MX240 Host Subsystem Description on page 21•
• Maintaining the MX240 Host Subsystem on page 358
• Taking an MX240 Host Subsystem Offline
MX240 Midplane Description
The midplane is located toward the rear of the chassis and forms the rear of the card
cage (see Figure 11 on page 22). The line cards and SCBs install into the midplane from
the front of the chassis, and the power supplies install into the midplane from the rear
of the chassis. The cooling system components also connect to the midplane.
The midplane performs the following major functions:
•
Data path—Data packets are transferred across the midplane between the line cards
through the fabric ASICs on the SCBs.
•
Power distribution—The router power supplies connect to the midplane, which
distributes power to all the router components.
•
Signal path—The midplane provides the signal path to the line cards, SCBs, Routing
Engines, and other system components for monitoring and control of the system.
Chapter 5: Host Subsystem Components and Descriptions
Related
Documentation
MX240 Router Overview on page 3•
• MX240 Chassis Description on page 8
• MX240 Dense Port Concentrator (DPC) Description on page 47
• MX240 SCB Description on page 91
• MX240 Flexible PIC Concentrator (FPC) Description on page 54
• MX240 Power System Overview on page 85
MX240 Routing Engine Description
The Routing Engine is an Intel-basedPC 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, and
RE-S-X6-64G Routing Engines. See Figure 12 on page 23, Figure 13 on page 24, and
Figure 14 on page 24.
NOTE: If two Routing Engines are installed, they must both be the same
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 18 on page 31) 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.
6—1—
ONLINE/OFFLINE Button
7—2—
SSD LEDs—DISK1 and DISK2Auxiliary port (AUX)
8—3—
Ports—USB1 and USB2Console port (Con)
9—4—
RESET ButtonManagement port (MGMT)
10—5—SSD card slot cover
•
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 RoutingEngine 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” on page 30 describes the functions of these LEDs.
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.
Chapter 5: Host Subsystem Components and Descriptions
NOTE: For specific information about Routing Engine components (for
example,the amount of DRAM), issue the show vmhost hardware command.
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 connectorto 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.
RE-S-X6-64G 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—Connectsthe RoutingEngine 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 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 storagemedia 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 bootdevice.
NOTE: If the routerboots from an alternateboot device, a yellowalarm 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.
Related
Documentation
MX240 Routing Engine LEDs on page 30•
• Removing an MX240 Routing Engine on page 265
• Installing an MX240 Routing Engine on page 226
• MX240 Routing Engine Serial Number Label on page 403
RE-S-1800 Routing Engine Description for MX Series
Figure 15 on page 26 shows the Routing Engine 1800.
Figure 16 on page 27 shows the RE-S-1800 Routing Engine.
Each Routing Engine consists of the following components:
•
CPU—Runs Junos OS to maintain the router's routing tables and routing protocols..
•
DRAM—Provides storage for the routing and forwarding tables and for other Routing
Engine processes.
Chapter 5: Host Subsystem Components and Descriptions
•
USB port—Provides a removable media interface through which you can install Junos
OS manually. Junos OS supports USB version 1.0.
•
CompactFlash card—Provides primary storage for software images, configurationfiles,
and microcode. The CompactFlash card is fixed and is inaccessible from outside the
router.
•
Solid-state Drive (SSD)—Provides secondary storage for log files, memory dumps,
and rebooting the system if the CompactFlash card fails.
•
Interface ports—The AUX, CONSOLE, and ETHERNET provide access to management
devices.Each RoutingEngine 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.
•
EEPROM—Stores the serial number of the Routing Engine.
•
RESET button—Reboots the Routing Engine when pressed.
•
ONLINE/OFFLINE button—Takes the Routing Engine online or offline when pressed.
•
Extractor clips—Used for inserting and extracting the Routing Engine.
•
Captive screws—Secure the Routing Engine in place.
NOTE: For specific information about Routing Engine components (for
example, the amount of DRAM), issue the show chassis routing-engine
command.
The router is shipped with Junos OS preinstalled on the Routing Engine. There are three
copies of software:
•
One copy on the CompactFlash card in the Routing Engine.
•
One copy on the hard disk in the Routing Engine.
•
One copy on a USB flash drive that can be inserted into the slot on the Routing Engine
faceplate.
The Routing Engine boots from the storagemedia in this order: the USB device (if present),
then the CompactFlash card, then the Solid State Disk (SSD), then the LAN. Normally,
the router boots from the copy of the software on the CompactFlash card.
Related
Documentation
• RJ-45 Connector Pinouts for MX Series Routing Engine AUX and CONSOLE Ports
• RJ-45 Connector Pinouts for an MX Series Routing Engine ETHERNET Port
• Replacing an MX960 Routing Engine
• Supported Routing Engines by Router on page 34
RE-S-X6-64G Routing Engine Description for MX Series
Figure 17 on page 28 shows the Routing Engine.
Figure 17: RE-S-X6-64G Routing Engine Front View
Extractor clips
LEDs—ONLINE, OK/FAIL, and MASTER
6—1—
7—2—
8—3—
9—4—
10—5—SSD card slot cover
ONLINE/OFFLINE button
SSD LEDs—DISK1 and DISK2Auxiliary port (AUX)
Ports—USB1 and USB2Console port (CONSOLE)
RESET buttonManagement port (MGMT)
•
RE-S-X6-64G Routing Engine Components on page 28
•
RE-S-X6-64G Routing Engine Boot Sequence on page 29
RE-S-X6-64G Routing Engine Components
In routers with dual Routing Engines, both the Routing Engines must be RE-S-X6-64G
Routing Engines.
Chapter 5: Host Subsystem Components and Descriptions
Each RE-S-X6-64G Routing Engine (shown in Figure 17 on page 28) 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 RoutingEngine 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—Brings the Routing Engine online or takes it offline when
pressed.
•
Extractor clips—Control the locking system that secures the Routing Engine.
•
LEDs—“RE-S-X6-64G Routing Engine LEDs” on page 31 describes the functions of
these LEDs.
NOTE: For specific information about Routing Engine components (for
example,the amount of DRAM), issue the show vmhost hardware command.
RE-S-X6-64G Routing Engine Boot Sequence
Booting in a RE-S-X6-64G Routing Engine follows this sequence—the USB device, SSD1,
SSD2, LAN. SSD1 is the primary boot device. Boot sequence is tried twice for SSD1 and
SSD2.
Related
Documentation
Upgrading to the RE-S-X6-64G Routing Engine in a Redundant Host Subsystem on
•
page 271
• Upgrading to the RE-S-X6-64G Routing Engine in a Nonredundant Host Subsystem
NOTE: The memory in Table 16 on page 32 indicates the amount of total
memory. To determine the amount of available memory, issue the show
chassis routing-engine CLI command.
On routing platforms 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 on page 34•
Documentation
Supported Routing Engines by Router
The following tables list the RoutingEngines that each router supports, the first supported
release for the Routing Engine in the specified router,the management Ethernet interface,
and the internal Ethernet interfaces for each Routing Engine.
•
M7i Routing Engines on page 35
•
M10i Routing Engines on page 35
•
M40e Routing Engines on page 36
•
M120 Routing Engines on page 36
•
M320 Routing Engines on page 37
•
MX5, MX10, MX40, and MX80 Routing Engine on page 37
MX240 Dense Port Concentrator (DPC) Description on page 47
•
MX240 DPC Port and Interface Numbering on page 49
•
MX240 Dense Port Concentrator (DPC) LEDs on page 52
•
DPCs Supported on MX240, MX480, and MX960 Routers on page 52
MX240 Dense Port Concentrator (DPC) Description
A Dense Port Concentrator (DPC) is optimized for Ethernet density and supports up to
40 Gigabit Ethernet or four 10-Gigabit Ethernet ports (see Figure 19 on page 48). Other
combinations of Gigabit Ethernet and 10-Gigabit ports are available in various DPC
models. For more information about these models, see the MX Series Interface Module
Reference
The DPC assembly combines packet forwarding and Ethernet interfaces on a single
board, with either twoor four 10-Gbps PacketForwarding Engines. Each PacketForwarding
Engine consists of one I-chip for Layer 3 processing and one Layer 2 network processor.
The DPCs interface with the power supplies and Switch Control Boards (SCBs).
The router has two dedicated line card slots for DPCs, MPCs, or FPCs. DPCs install
horizontally in the front of the router (see Figure 19 on page 48). One multifunction slot
numbered 1/0 supports either one DPC or one SCB. The DPC slots are numbered 1/0, 1,
and 2, bottom to top. A DPC can be installed in any slot on the router that supports DPCs.
You can install any combination of DPC types in the router.
DPCs are hot-removable and hot-insertable. When you install a DPC in an operating
router, the Routing Engine downloads the DPC software, the DPC runs its diagnostics,
and the Packet Forwarding Engines housed on the DPC are enabled. Forwarding on other
DPCs continues uninterrupted during this process.
If a slot is not occupied by a DPC or an SCB, a blank panel must be installed to shield the
empty slot and to allow cooling air to circulate properly through the router.
Figure 19 on page 48 shows typical DPCs supported on the MX240 router. For more
information about DPCs, see the MX Series Interface Module Reference.
Figure 19: Typical DPCs Supported on the MX240 Router
Figure 20: DPC Installed Horizontally in the MX240 Router
DPC Components
Each DPC consists of the following components:
•
DPC cover, which functions as a ground plane and a stiffener.
•
Fabric interfaces.
•
Two Gigabit Ethernet interfaces that allow control information, route information, and
statistics to be sent between the Routing Engine and the CPU on the DPCs.
Two interfaces from the SCBs that enable the DPCs to be powered on and controlled.
•
Physical DPC connectors.
•
Two or four Packet Forwarding Engines.
•
Midplane connectors and power circuitry.
•
Processor subsystem, which includes a 1.2-GHz CPU, system controller, and 1 GB of
SDRAM.
•
Online button—Takes the DPC online or offline when pressed.
•
LEDs on the DPC faceplate. For more information about LEDs on the DPC faceplate,
see the MX Series Interface Module Reference.
Two LEDs, located on the craft interface above the DPC, display the status of the DPC
and are labeled OK and FAIL.
Related
Documentation
DPC and MPC LEDs on the MX240 Craft Interface on page 15•
• MX240 Field-Replaceable Units (FRUs) on page 219
• Replacing an MX240 DPC on page 279
MX240 DPC Port and Interface Numbering
Each port on a DPC corresponds to a unique interface name in the CLI.
In the syntax of an interface name, a hyphen (-) separates the media type from the DPC
number (representedas an FPC in the CLI). The DPC slot number corresponds to the first
number in the interface. The second number in the interface corresponds to the logical
PIC number. The last number in the interface matches the port number on the DPC.
Slashes (/) separate the DPC number from the logical PIC number and port number.
type-fpc/pic/port
•
type—Media type, which identifies the network device. For example:
•
ge—Gigabit Ethernet interface
•
so—SONET/SDH interface
•
xe—10-Gigabit Ethernet interface
For a complete list of media types, see Interface Naming Overview.
•
fpc—Slot in which the DPC is installed. On the MX240 router, the DPCs are represented
in the CLI as FPC 0 through FPC 2.
•
pic—Logical PIC on the DPC. The number of logical PICs varies depending on the type
of DPC. For example, a:
•
20-port Gigabit Ethernet DPC has two logical PICs, numbered 0 through 1.
•
40-port Gigabit Ethernet DPC has four logical PICs, numbered 0 through 3.
2-port 10-Gigabit Ethernet DPC has two logical PICs, numbered 0 through 1.
•
4-port 10-Gigabit Ethernet DPC has four logical PICs, numbered 0 through 3.
For more information on specific DPCs, see “DPCs Supported on MX240, MX480, and
MX960 Routers” on page 52 in the MX Series Interface Module Reference.
•
port—Port number.
The MX240 router supports up to three DPCs that install horizontally and are numbered
from bottom to top.
Figure 21 on page 50 shows a 40-port Gigabit Ethernet DPC with SFP installed in slot 2
on the MX240 router.
Figure 21: MX240 DPC Interface Port Mapping
The DPC contains four logical PICs, numbered PIC 0 through PIC 3 in the CLI. Each logical
PIC contains 10 ports numbered 0 through 9.
The show chassis hardware command output displays a 40-port Gigabit Ethernet DPC
with SFP (DPCE-R-40GE-SFP) installed in DPC slot 2. The DPC is shown as FPC 2 and
the DPC’s four logical PICs — 10x 1GE(LAN) — are shown as PIC 0 through PIC 3.
The show interfaces terse command output displays the Gigabit Ethernet interfaces that
correspond to the 40 ports located on the DPC.
user@host> show interfaces terse ge-2*
Interface Admin Link Proto Local Remote
ge-2/0/0 up up
ge-2/0/1 up down
ge-2/0/2 up up
ge-2/0/3 up up
ge-2/0/4 up up
ge-2/0/5 up up
ge-2/0/6 up up
ge-2/0/7 up up
ge-2/0/8 up up
ge-2/0/9 up up
ge-2/1/0 up down
ge-2/1/1 up down
ge-2/1/2 up down
ge-2/1/3 up down
ge-2/1/4 up up
ge-2/1/5 up up
ge-2/1/6 up up
ge-2/1/7 up up
ge-2/1/8 up up
ge-2/1/9 up down
ge-2/2/0 up down
ge-2/2/1 up down
ge-2/2/2 up down
ge-2/2/3 up down
ge-2/2/4 up down
ge-2/2/5 up down
ge-2/2/6 up down
ge-2/2/7 up down
ge-2/2/8 up down
ge-2/2/9 up down
ge-2/3/0 up down
ge-2/3/1 up down
ge-2/3/2 up down
ge-2/3/3 up down
ge-2/3/4 up down
ge-2/3/5 up down
ge-2/3/6 up down
ge-2/3/7 up down
ge-2/3/8 up down
ge-2/3/9 up down
Related
MX240 Router Hardware and CLI Terminology Mapping on page 10•
Documentation
MX240 Dense Port Concentrator (DPC) LEDs
Two LEDs, located on the craft interface above the DPC, display the status of the DPC
and are labeled OK and FAIL. For more information about the DPC LEDs on the craft
interface, see “DPC and MPC LEDs on the MX240 Craft Interface” on page 15.
Each DPC also has LEDs located on the faceplate. For more information about LEDs on
the DPC faceplate, see the “LEDs” section for each DPC in the MX Series Interface Module
Reference.
Related
Documentation
MX240 Field-Replaceable Units (FRUs) on page 219•
• MX240 Dense Port Concentrator (DPC) Description on page 47
• Replacing an MX240 DPC on page 279
DPCs Supported on MX240, MX480, and MX960 Routers
Table39 on page 52 lists the DPCs supported bythe MX240, MX480, and MX960 routers.
Table 39: DPCs Supported in MX240, MX480, and MX960 Routers
DPC Model
NumberDPC Name
Maximum
Throughput
per DPCPorts
First Junos
OSRelease
Gigabit Ethernet
Gigabit Ethernet DPC with SFP
with SFP
8.240 Gbps40DPC-R-40GE-SFP
EOL (see
PSN-2009-06-400)
8.440 Gbps40DPCE-R-40GE-SFPGigabit Ethernet Enhanced DPC with SFP
8.440 Gbps40DPCE-X-40GE-SFPGigabit Ethernet Enhanced Ethernet Services DPC with SFP
Table 39: DPCs Supported in MX240, MX480, and MX960 Routers (continued)
Maximum
DPC Model
NumberDPC Name
Throughput
per DPCPorts
First Junos
OSRelease
Tri-Rate Enhanced Ethernet Services DPC
Services
Related
Documentation
MX Series DPC Overview•
• Protocols and Applications Supported by DPCs and Enhanced DPCs (DPC and DPCE-R)
• Protocols and Applications Supported by Enhanced Ethernet Services DPCs (DPCE-X)
• Protocols and Applications Supported by Enhanced Queuing IP Services DPCs
(DPCE-R-Q)
• Protocols and Applications Supported by Enhanced Queuing Ethernet Services DPCs
(DPCE-X-Q)
• Protocols and Applications Supported by the Multiservices DPC (MS-DPC)
Interface Modules—FPCs and PICs
•
MX240 Flexible PIC Concentrator (FPC) Description on page 54
•
MX240 Flexible PIC Concentrator (FPC) LEDs on page 56
•
FPCs Supported by MX240, MX480, and MX960 Routers on page 57
•
MX240 PIC Description on page 57
•
MX240 PIC Port and Interface Numbering on page 57
•
MX240 PIC LEDs on page 59
•
PICs Supported by MX240, MX480, and MX960 Routers on page 59
EOL (see
PSN-2011-07-315.)
MS-DPCMultiservices DPC
9.140 Gbps40DPCE-X-40GE-TX
9.3–2 (Not
supported)
MX240 Flexible PIC Concentrator (FPC) Description
A Flexible PIC Concentrator (FPC) occupies two DPC slots on an MX Series router. The
DPC slots are numbered 1/0, 1, and 2, bottom to top.One FPC can be installedhorizontally
in either slots 1/0 and 1, or slots 1 and 2 on the front of the router (see Figure 23 on page 56).
The interface corresponds to the lowest numbered DPC slot for which the FPC is installed.
Figure 22 on page 55 shows typical FPCs supported on the MX240 router.
Figure 22: Typical FPCs Supported on the MX240 Router
If a slot is not occupied by a DPC, an FPC, or an SCB, a blank panel must be installed to
shield the empty slot and to allow cooling air to circulate properly through the router.
Each FPC supports up to two PICs. On an FPC2, one Packet Forwarding Engine receives
incoming packets from the PICs installed on the FPC and forwards them through the
switch planes to the appropriate destination port. On an FPC3, two Packet Forwarding
Engines receive incoming packets from the PICs installed on the FPC and forwards them
through the switch planes to the appropriate destination port. The FPCs interface with
the power supplies and SCBs.
FPCs are hot-removable and hot-insertable, as described in “MX240 Component
Redundancy” on page 7. When you install an FPC into a functioning router, the Routing
Engine downloads the FPC software, the FPC runs its diagnostics, and the PICs, housed
on the FPC, are enabled. Forwarding continues uninterrupted during this process. When
you remove or install an FPC, packet forwarding between other DPCs or FPCs is not
affected.
Figure 23: FPC Installed in the MX240 Router Chassis
FPC Components
Each FPC consists of the following components:
•
FPC card carrier, which includes two PIC slots.
•
Up to two Packet Forwarding Engines, each consisting of one I-chip for Layer 3
processing and one Layer 2 network processor.
•
Midplane connectors and power circuitry.
•
Processor subsystem (PMB), which includes a 1.2-GHz CPU, system controller, 1 GB of
SDRAM, and two Gigabit Ethernet interfaces.
•
Two LEDs, located on the craft interface above the FPC, that display the status of the
FPC and are labeled OK and FAIL. For more information about the FPC LEDs located
on the craft interface, see “FPC LEDs on the MX240 Craft Interface” on page 15.
•
FPC online/offline button, located on the craft interface above the FPC
Related
Documentation
MX240 FPC Terminology•
• Replacing an MX240 FPC on page 284
• Maintaining MX240 FPCs on page 364
• Troubleshooting the MX240 FPCs on page 382
MX240 Flexible PIC Concentrator (FPC) LEDs
Two LEDs, located on the craft interface above the FPC, that display the status of the
FPC and are labeled OK and FAIL. For more information about the FPC LEDs located on
the craft interface, see “FPC LEDs on the MX240 Craft Interface” on page 15.
Related
Documentation
MX240 Flexible PIC Concentrator (FPC) Description on page 54•
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 40 on page 57 lists FPCs supported by MX Series routers.
Table 40: FPCs Supported by MX Series Routers
Chapter 6: Line Card Components and Descriptions
Related
Documentation
• PICs Supported by MX240, MX480, and MX960 Routers on page 59
• High Availability Features
MX240 PIC Description
PICs provide the physical connection to various network media types, receiving incoming
packets from the network and transmitting outgoing packets to the network. During this
process, each PIC performs framing and line-speed signaling for its media type. Before
transmitting outgoing data packets, the PICs encapsulate the packets received from the
FPCs. Each PIC is equipped with an ASIC that performs control functions specific to the
media type of that PIC.
PICs are hot-removable and hot-insertable. You can install up to two PICs in the slots in
each FPC. PICs used in an FPC2 have captive screws at their upper and lower corners.
PICs used in a Type 3 FPC have an upper ejector handle and a lower captive screw.
Maximum
Number of PICs
SupportedFPC Model NumberFPC NameFPC Type
Maximum
Throughputper FPC
(Full-duplex)
First Junos OS
Release
9.420 Gbps2MX-FPC3FPC33
9.510 Gbps2MX-FPC2FPC22
MX Series PIC Overview•
Related
Documentation
PICs Supported by MX240, MX480, and MX960 Routers on page 59•
• MX240 PIC LEDs on page 59
• Replacing an MX240 PIC on page 297
MX240 PIC Port and Interface Numbering
Each port on a PIC corresponds to a unique interface name in the CLI.
In the syntax of an interface name, a hyphen (-) separates the media type from the FPC
number (represented as an FPC in the CLI). The FPC slot number corresponds to the first
number in the interface. The second number in the interface corresponds to the PIC
number. The last number in the interface matches the port number on the PIC. Slashes
(/) separate the FPC slot number from the PIC number and port number:
type-fpc/pic/port
•
type—Media type, which identifies the network device. For example:
•
ge—Gigabit Ethernet interface
•
so—SONET/SDH interface
•
xe—10-Gigabit Ethernet interface
For a complete list of media types, see Interface Naming Overview.
•
fpc—Lowest slot number in which the FPC is installed. On the MX240 router, the FPC
occupies two line card slots and is represented in the CLI as FPC 0 or FPC 1.
•
pic—PIC number, 0 or 1 depending on the FPC slot.
For more information on specific PICs, see “PICs Supported by MX240, MX480, and
MX960 Routers” on page 59 in the MX Series Interface Module Reference.
•
port—Port number.
The FPC installs horizontally in either slots 1/0 and 1, or slots 1 and 2 and accepts up to
two PICs.
Figure 24 on page 58 shows a Channelized OC12/STM4 Enhanced IQ (IQE) PIC with SFP
installed in PIC slot 0 of an FPC installed in slot 1 and slot 2.
The show interfaces terse command output displays the channelized SONET OC12
interfaces (coc12), that correspond to the four ports located on the PIC.
user@host> show interfaces terse coc12*
Interface Admin Link Proto Local Remote
coc12-1/0/0 up up
coc12-1/0/1 up up
coc12-1/0/2 up up
coc12-1/0/3 up up
Related
MX240 Router Hardware and CLI Terminology Mapping on page 10•
Documentation
MX240 PIC LEDs
Each PIC has LEDs located on the faceplate. For more information about LEDs on the
PIC faceplate, see the “LEDs” section for each PIC in the MX Series Interface Module
Reference.
Related
Documentation
PICs Supported by MX240, MX480, and MX960 Routers on page 59•
• MX240 PIC Description on page 57
• Replacing an MX240 PIC on page 297
• Maintaining MX240 PICs on page 372
PICs Supported by MX240, MX480, and MX960 Routers
Table 41 on page 59 lists the PICs supported by MX240, MX480, and MX960 routers.
Table 41: PICs Supported by MX240, MX480, and MX960 Routers
Channelized IQ PICs
IQ (IQE) PIC with SFP
First Junos OS ReleaseTypePortsPIC Model NumberPIC Name
Table 42 on page 61, Table 43 on page 62, Table 44 on page 64, and Table 45 on page 66
provide a compatibility matrix for the current MICs supported by MPC1, MPC2, MPC3,
and MPC6 on MX240, MX480, MX960, MX2010, and MX2020 routers. The 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.
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.
Tri-Rate MIC
MIC-3D-8OC3OC12-4OC48
SONET/SDH OC3/STM1
(Multi-Rate) MICs with SFP
MIC-3D-8CHOC3-4CHOC12
Channelized SONET/SDH
OC3/STM1 (Multi-Rate) MICs
with SFP
13.2R2MS-MIC-16G
—MIC-3D-40GE-TX
12.1MIC-3D-4OC3OC12-1OC48,
12.1MIC-3D-4CHOC3-2CHOC12,
14.1R4, 14.2R3 and Junos
Continuity
15.1
14.1R4, 14.2R3 and Junos
Continuity
15.1
14.1R4, 14.2R3 and Junos
Continuity
15.1
14.1R4, 14.2R3 and Junos
Continuity
15.1
14.1R4, 14.2R3 and Junos
Continuity
15.1
14.1R4, 14.2R3 and Junos
Continuity
15.1
14.1R4, 14.2R3 and Junos
Continuity
15.1
14.1R4, 14.2R3 and Junos
Continuity
15.1
12.1MIC-3D-8DS3-E3,
MIC-3D-8CHDS3-E3-B
DS3/E3 MIC
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.
Modular Interface Cards (MICs) install into Modular Port Concentrators (MPCs) and
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. Before transmitting outgoing data packets through the MIC interfaces,
the MPCs encapsulate the packets received.
MICs are hot-removable and hot-insertable. You can install up to two MICs in the slots
in each MPC.
Related
Documentation
MICs Supported by MX Series Routers on page 67•
• MX240 Modular Interface Card (MIC) LEDs on page 71
• Replacing an MX240 MIC on page 288
• Maintaining MX240 MICs on page 369
MICs Supported by MX Series Routers
The following tables list the first supported Junos OS release for the MX Series.
•
Table 46 on page 68 lists the first supported Junos OS release for MICs on MX240,
MX480, MX960, MX2010, and MX2020 routers.
•
Table 47 on page 70 lists the first supported Junos OS release for MICs on MX5, MX10,