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 tothe 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
Connecting an MX960 Router to an External Alarm-Reporting Device . . . . 249
Connecting the MX960 Router to a Network for Out-of-Band Management . . 250
Connecting the MX960 Router to a Management Console or Auxiliary Device . . 251
Connecting an MX960 Router to an External Alarm-Reporting Device . . . . . . . . 252
Connecting DPC, MPC, MIC, or PIC Cables to the MX960 Router . . . . . . . . . . . . 253
Connecting the Alarm Relay Wires to the MX960 Craft Interface . . . . . . . . . . . . 255
Figure 52: Installing the Mounting Hardware for a Four-Post Rack or Cabinet . . 197
Figure53: Installing the Mounting Hardwarefor Front-Mountingin an Open-Frame
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:
•
MX960
Documentation Conventions
Table 1 on page xxvi defines notice icons used in this guide.
Represents names of configuration
statements, commands, files, and
directories;configurationhierarchylevels;
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
Indicatesa choice between the mutually
exclusivekeywordsor 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.
Representsgraphicaluser 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 starsto ratethe 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 totechpubs-comments@juniper.net. Includethe document
or topic name, URL or page number, and software version (if applicable).
Requesting Technical Support
Technicalproduct support is availablethrough the Juniper Networks TechnicalAssistance
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:
The MX960 3D Universal EdgeRouter is an Ethernet-optimized edge router that provides
both switching and carrier-class Ethernet routing. The MX960 router enables a wide
rangeof business and residential applicationsand services, including high-speed transport
and VPN services, next-generation broadband multiplay services, high-speed Internet
and data center internetworking.
The MX960 chassis provides redundancy and resiliency. The hardware system is fully
redundant, including power supplies, fan trays, Routing Engines, and Switch Control
Boards.
The MX960 router is 16 rack units (U) tall. Three routers can be stacked in a single
floor-to-ceilingrack, for increased port density per unit of floorspace. The router provides
14 slots that can be populated with 11 or 12 Dense Port Concentrators (DPCs) or Modular
Port Concentrators (MPCs), six Flexible PIC Concentrators (FPCs), and two Switch
Control Boards (SCBs) in nonredundant fabric configurations.
Fully populated, the MX960 router provides an aggregate switch fabric capacity of up
to 10.56 Tbps, with line-rate throughput on 264 10-Gigabit Ethernet ports, 22 100-Gigabit
Ethernet and 44 10-Gigabit Ethernet ports and 66 40-Gigabit Ethernet ports.
Table 3 on page 3 lists the MX960 router capacity.
Table 3: MX960 Router Capacity
CapacityDescription
10.56 Tbps half duplexSystem capacity
480 GbpsSwitch fabric capacity per slot
11 or 12 (depending on protection scheme)MPCs and DPCs per chassis
Several types of DPCs are available. Each DPC includes either two or four Packet
Forwarding Engines. Each Packet Forwarding Engine enables a throughput of 10 Gbps.
Up to two PICs can be installed in each FPC. Fully populated, the MX960 supports up to
12 PICs.
Up to two Modular InterfaceCards (MICs) can be installed in each MPC. Fully populated,
the MX960 supports up to 24 MICs.
MPCs support fixed interfaces or up to two Modular Interface Cards (MICs) that can be
installed in each MPC. Fully populated, the MX960 supports up to 22 MICs.
For a list of the supported DPCs, FPCs, MPCs, MICs, and PICs, see the MX Series Interface
Module Reference.
Three SCBs are available for the MX960 routers—the SCB, the SCBE, and the SCBE2.
Table 4 on page 4 lists the MX960 SCBs.
Table 4: SCB Comparison
Related
Documentation
Switch Fabric CapacityDescriptionModel Number
10.56 Tbps (half-duplex)Enhanced MX Switch Control Board (SCBE2)SCBE2- MX-BB
5.12TbpsEnhanced Switch Control Board (SCBE)SCBE-MX-BB
2.64 TbpsSwitch Control Board (SCB)SCB-MX-BB
The connections between interface cards and SCBs are organized in three groups:
•
Switchfabric—Connectsthe interface cardsand provides for packet transport between
DPCs, FPCs, and MPCs. Two SCBs provide one nonredundant fabric. Three SCBS are
required for a redundant fabric configuration.
•
Control Plane—Gigabit Ethernet links between the combined SCBs/Routing Engines
and each DPC, FPC, or MPC. All board-to-board information is passed over Ethernet
except for low-level status and commands.
•
Management signals—Provide low-level status diagnostic support.
• MX960 Component Redundancy on page 12
• MX960 Router Physical Specifications on page 121
Outstanding Issues with the MX960 Router on page 5
•
Errata with the MX960 Router Documentation on page 7
Outstanding Issues with the MX960 Router
This topic lists outstanding hardware issues with the MX960 3D Universal Edge router.
For information about software issues, see the Junos OS Release Notes.
•
Each MX960 high capacity AC power supply has an input mode switch, covered by a
small metalplate.The input mode switch tells the system the number of feeds it should
expect When the input mode switch is set to '0' (zero): expect one feed, an alarm will
be generated if two are providing power. When the input mode swtich is set to '1' (one):
expect two feeds, an alarm will be generated if less than two feeds are active. The
default setting is 1.
In Junos OS Releases 10.1R2 and 10.2R1. there are scenarios in which both the supply
and the system will generate a warning or alarm, and there is at least one scenario
where the supply is OK and the system will still give a warning message. [PR530872]
The power supply has a PEM FAIL and OK LED; the failure LED will light up in this
scenario:
•
Supply is expecting two feeds (input mode switch = 1) but receiving only one active
feed
The system will generate an alarm in the following scenarios:
•
Supply is expecting two feeds (input mode switch = 1) but receiving only one active
feed.
•
Supply is expecting one feed (input mode switch = 0) but receiving two active feeds
.
NOTE:
•
•
All supplies should have the same amount of feeds activated.
The correct usage of the feed selector is required in order to get to the
desired capacity of the supplies.
•
Juniper Networks strongly recommends that you install Junos OS Release 8.2R2 or
later before deploying the MX960 router into service.
•
Junos OS Release 8.2R1 does not allow you to complete an install from the USB
dongle. Use Junos OS Release 8.2R2 instead. [PR/98563]
•
In Junos OS Release 8.2R1, a condition can exist where both fan trays are shut down
by the system, but the system continues to operate. This can potentially result in
serious overheating and damage to the DPCs. Use Junos OS Release 8.2R2 instead.
[PR/94692] [PR/289154]
•
The XFP cages and optics on the MX960 router are industry standard parts which 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]
•
Althoughthe MX960router can support anycombination of 11 DPCsand the redundant
third SCB, the power supply cannot support all 12 DPCs if an Enhanced Queuing DPC
is inserted into any slot of a fully loaded chassis. The Enhanced Queuing DPCs exhibit
the following behavior:
•
When you insert an Enhanced Queuing DPC into slot 6 of a powered-on MX960
router, the DPC will not power on.
•
When you insert a DPC into slot 6 of an MX960 router containing an Enhanced
Queuing DPC in any slot, the DPC will not power on.
•
When you insert an Enhanced Queuing DPC into any slot of an MX960 router
containing a DPC already powered on in slot 6, the Enhanced Queuing DPC will not
power on.
These scenarios raise an FPC misconfiguration red alarm due to the DPC's high power
consumption. To clear the alarm, perform one of the following actions:
•
To temporarily take the DPC offline, use the request chassis fpc slot slot-number
offline command from the CLI.
NOTE: The router does not preserve the state after a reboot.
•
To take the DPC offline and preserve the state after a reboot, use the set chassis fpc
slot-number power off command from configuration mode.
•
Remove the powered-off DPC from the MX960 router.
Juniper Networks also recommends the following best practices:
•
Use all other slots before using slot 6.
•
Remove any unused DPCs plugged into the MX960 chassis.
Related
Errata with the MX960 Router Documentation on page 7•
Documentation
Errata with the MX960 Router Documentation
This topic lists outstanding documentation issues:
•
There are no outstanding documentation issues at this time.
Related
Documentation
• Outstanding Issues with the MX960 Router on page 5
MX960 Router Hardware and CLI Terminology Mapping on page 12
•
MX960 Rack-Mounting Hardware on page 14
•
MX960 Craft Interface Overview on page 15
•
MX960 Alarm Relay Contacts on the Craft Interface on page 15
•
MX960 Alarm LEDs and Alarm Cutoff/Lamp Test Button on page 16
•
MX960 Component LEDs on the Craft Interface on page 17
•
MX960 Cable Manager Description on page 19
MX960 Chassis Description
The router chassis is a rigid sheet metal structure that houses all the other router
components (see Figure 1 on page 10, Figure 2 on page 11, and Figure 3 on page 11). The
chassis installs in many types of racks, including 800-mm deep (or larger) enclosed
cabinets, standard 19-in. equipment racks, or telco open-frame racks. Two types of
chassis are available for the MX960 router:
•
The standard chassis measures 27.75 in. (70.49 cm) high, 17.37 in. (44.11 cm) wide
(excluding the mounting flanges and brackets), and 23.0 in. (58.42 cm) deep (from
the front-mounting flanges to the rear of the chassis). The standard cable manager
extends the depth to 28.0 in. (71.1 cm). Up to three routers can be installed in a 48-U
rack if the rack can handle their combined weight, which can be greater than 1,050 lb
(476.3 kg).
NOTE: The chassis depth with the high-capacity AC power supply is 30.6"
and the depth with high-capacity DC power supply is 32.8".
•
The chassis with the extended cable manager installed measures 36.5 in. (92.7 cm)
high, 17.37 in. (44.11 cm) wide, and approximately 29.00 in. (73.7 cm) deep (from the
front-mounting flanges to the rear of the extended cable manager). Up to two routers
with the extended cable manager can be installed in a 48-U rack if the rack can handle
their combined weight, which can be greater than 748 lb (339.28 kg).
• MX960 Router Grounding Specifications on page 145
MX960 Component Redundancy
A fully configured router is designed so that no single point of failure can cause the entire
system to fail. Only a fully configured router provides complete redundancy. All other
configurations provide partial redundancy. The following major hardware components
are redundant:
•
Host subsystem—The host subsystem consists of a Routing Engine and 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.
•
Power supplies—In the AC configuration with normal capacity AC power supplies, a
minimum of three power supplies is required to supply power to a fully configured
router. All AC power supplies share the load evenly. The addition of a fourth power
supply provides full power redundancy. If one power supply fails in a redundant
configuration, the three remaining power supplies provide full power. In the DC
configuration and the AC configuration with high capacity power supplies, two power
supplies are required to supply power to a fully configured router. One power supply
supports approximately half of the components in the router, and the other power
supply supports the remaining components. The addition of two power supplies
provides full power redundancy. If one or two power supplies fail, the remaining power
supplies can provide full power to the router.
•
Cooling system—The cooling system has redundant components, which are controlled
by the host subsystem. If one of the fans fails, the host subsystem increasesthe speed
of the remaining fans to provide sufficient cooling for the router indefinitely.
Related
Documentation
MX960 Router Overview on page 3•
• Displaying MX960 Router Components and Serial Numbers on page 507
• Guidelines for Packing Hardware Components for Shipment on page 524
• Returning a Hardware Component to Juniper Networks, Inc. on page 527
MX960 Router Hardware and CLI Terminology Mapping
The MX960 router supports the components in Table 5 on page 13.
Front-mounting flanges on the front of the chassis for front-mounting in a four-post
rack or cabinet
•
Two center-mounting brackets attached to the center of the chassis for
center-mounting in an open-frame rack. For an open-frame rack, center-mounting is
preferable because of the more even distribution of weight.
Related
Documentation
MX960 Chassis Description on page 9•
• MX960 Midplane Description on page 28
• Installing the MX960 Mounting HardwareforCenter-Mounting in an Open-FrameRack
on page 199
• Installing the MX960 Mounting Hardware for Front-Mounting in an Open-Frame Rack
on page 197
• Installing the MX960 Mounting Hardware for a Four-Post Rack or Cabinet on page 195
MX960 Craft Interface Overview
The craftinterface 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 4 on page 15.
Figure 4: 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
• Replacing the MX960 Craft Interface on page 307
• MX960 Craft Interface Serial Number Label on page 511
MX960 Alarm Relay Contacts on the Craft Interface
The craft interface has two alarm relay contacts for connecting the router to external
alarm devices (see Figure 5 on page 16). 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 5: Alarm Relay Contacts
Related
Documentation
Disconnecting the Alarm Relay Wires from the MX960 Craft Interface on page 307•
• Connecting the Alarm Relay Wires to the MX960 Craft Interface on page 255
MX960 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 located to 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 16 describes the alarm LEDs and alarm cutoff button in more detail.
Table 6: Alarm LEDs and Alarm Cutoff/Lamp Test Button
DescriptionStateColorShape
On steadilyRed
On steadilyYellow
––
Critical alarm LED—Indicatesa critical condition that
can cause the router to stop functioning. Possible
causes include component removal, failure, or
overheating.
WarningalarmLED—Indicatesa serious but nonfatal
error condition, such as a maintenance alert or a
significant increase in component temperature.
Alarm cutoff/lamptest button—Deactivatesredand
yellowalarms. Causes all LEDs on the craftinterface
to light (for testing) when pressed and held.
• MX960 Alarm Relay Contacts on the Craft Interface on page 15
• MX960 Router Overview on page 3
MX960 Component LEDs on the Craft Interface
•
MX960 Host Subsystem LEDs on the Craft Interface on page 17
•
MX960 Power Supply LEDs on the Craft Interface on page 17
•
MX960 DPC and MPC LEDs on the Craft Interface on page 18
•
MX960 FPC LEDs on the Craft Interface on page 18
•
MX960 SCB LEDs on the Craft Interface on page 18
•
MX960 Fan LEDs on the Craft Interface on page 19
MX960 Host Subsystem LEDs on the 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. Table 7 on page 17 describes the functions of the host subsystem LEDs.
Table 7: Host Subsystem LEDs on the Craft Interface
MX960 Power Supply LEDs on the 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 17 describes the functions of the power supply LEDs on the craft
interface.
Table 8: Power Supply LEDs on the Craft Interface
DescriptionStateColorLabel
Host is functioning as the master.On steadilyGreenMASTER
Host is online and is functioning normally.On steadilyGreenONLINE
Host is installed but the Routing Engine is offline.On steadilyRedOFFLINE
Host is not installed.Off–
DescriptionStateColorLabel
Power supply is functioning normally.On steadilyGreenPEM
Power supply has failed or power input has failed.On steadilyRed
Each DPC or MPC has LEDs on the craft interface that indicate its status. The LEDs,
labeled 0 through 5, 2/6, and 7 through 11, are located along the bottom of the craft
interface. Slot2/6 is foran additional DPC, FPC, MPC, or SCB. Table 9 on page 18 describes
the functions of the LEDs.
Table 9: DPC and MPC LEDs on the Craft Interface
DescriptionStateColorLabel
Card is functioning normally.On steadilyGreenOK
Card is transitioning online or offline.Blinking
The slot is not online.Off–
Card has failed.On steadilyRedFAIL
MX960 FPC LEDs on the Craft Interface
An FPC takes up two DPC slots when installed in an MX Series router. The LEDs, labeled
0 through 5, 2/6, and 7 through 11, are located along the bottom of the craft interface.
Slot 2/6 is for an additional DPC, FPC, MPC, or SCB. The LED corresponds to the lowest
DPC slot number in which the FPC is installed.Table10 on page18 describesthe functions
of the FPC LEDs.
Table 10: FPC LEDs on the Craft Interface
MX960 SCB LEDs on the Craft Interface
Each SCB has two LEDs on the craft interface that indicates its status. The SCB LEDs,
labeled 0, 1, and 2/6, are located along the bottom of the craft interface.
Table 11 on page 19 describes the functions of the SCB LEDs.
The fan LEDs are located on the top left of the craft interface. Table 12 on page 19
describes the functions of the fan LEDs.
Table 12: Fan LEDs on the Craft Interface
Chapter 3: Chassis Components and Descriptions
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
Related
Documentation
MX960 Craft Interface Overview on page 15•
• MX960 Alarm Relay Contacts on the Craft Interface on page 15
MX960 Cable Manager Description
The standard cable manager (see Figure 6 on page 20) is a tray located below the
line-cardcage,which has a row of fourteendividers forsecuring the cables foreach Dense
Port Concentrator (DPC), Modular Port Concentrator (MPC), Modular Interface Card
(MIC), or PIC.
You can use cable strips or other ties to gently secure the cables in the standard cable
manager. To secure the cables in place, loop the tie through the cable anchor and secure
the tie. You can pull the standard cable manager up and outward to lock it into the
maintenance position. This allows you to access the lower fan tray and the air filter.
The extended cablemanager allowsyou to route cablesaway from the front of the DPCs,
MPCs, MICs, and PICs, and provides additional access (see Figure 8 on page 21 and
The cooling system consists of the following components:
•
Upper front fan tray
•
Lower front fan tray
•
Front air filter
The cooling system components work together to keep all router components within the
acceptable temperature range (see Figure 9 on page 24, Figure 10 on page 24,
Figure 11 on page 24, and Figure 12 on page 24). The router has two fan trays located in
the front of the router that install horizontally above and below the card cage. Each
normal-capacity fan tray contains six fans. High-capacity fan trays that contain twelve
fans can be installedin the upper and lower fan tray slots. The fan traysare hot-insertable
and hot-removable.
The MX960 requires high-capacity fan trays to satisfy cooling requirements for
high-density DPCs and MPCs. When replacing normal-capacity fan trays with
high-capacity fan trays, you must replace them in both the upper and lower fan trays.
Additionally, you must replace the front air filter.
NOTE: If you install high-capacity fan trays, you must also install
high-capacity power supplies. Combinations of normal-capacity and
high-capacity power supplies and fan trays are not supported.
There is a single air intake in the front of the router. Air is pushed up through the card cage
and through the upper fan tray where it is exhausted out the upper rear of the system
through the larger air exhaust shown in Figure 9 on page 24.
At the bottom rear of the chassis, there is an air intake for power supply cooling. Air flows
over the power supplies and is exhausted out the rear of the chassis through the smaller
air exhaust below the main exhaust.
Figure 9: 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 RoutingEngine shuts down the systemby disabling output power
from each PEM.
Chapter 4: Cooling System Components and Descriptions
Figure 13: High-Capacity Fan Tray
Figure 14: High-Capacity Filter Tray with Air Filter
Related
Documentation
MX960 Fan LED
Related
Documentation
• Troubleshooting the MX960 Cooling System on page 490
• Maintaining the MX960 Air Filter on page 446
• Maintaining the MX960 Fan Trays on page 446
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 “MX960 Fan LEDs on the Craft Interface”
on page 19.
• MX960 Cooling System Description on page 23
• Maintaining the MX960 Fan Trays on page 446
• Troubleshooting the MX960 Cooling System on page 490
MX960 RE-S-1300 and RE-S-2000 Routing Engine LEDs on page 31
•
RE-S-1800 Routing Engine Description for MX Series on page 31
•
RE-S-1800 Routing Engine LEDs on page 33
•
RE-S-X6-64G Routing Engine Description on page 34
•
RE-S-X6-64G Routing Engine LEDs on page 36
•
Routing Engine Specifications on page 37
•
Supported Routing Engines by Router on page 40
MX960 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
MX960 Host Subsystem LEDs on page 28•
• Maintaining the MX960 Host Subsystem on page 448
• Effect of Taking the MX960 Host Subsystem Offline
• Replacing an MX960 Routing Engine on page 333
• Replacing an MX960 SCB on page 409
MX960 Host Subsystem LEDs
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 “MX960 Host
Subsystem LEDs on the Craft Interface” on page 17.
Related
Documentation
MX960 Host Subsystem Description on page 27•
• Maintaining the MX960 Host Subsystem on page 448
• Taking an MX960 Host Subsystem Offline
MX960 Midplane Description
The midplane is located toward the rear of the chassis and forms the rear of the card
cage (see Figure 15 on page 29). 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
MX960 Router Overview on page 3•
• MX960 Chassis Description on page 9
• MX960 Dense Port Concentrator Description on page 53
• MX960 Modular Port Concentrator Description on page 89
• MX960 SCB Description on page 107
• MX960 Routing Engine Description on page 29
• MX960 Flexible PIC Concentrator Description on page 62
• MX960 Power System Overview on page 97
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.
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
NOTE: The Routing Engine is equipped with limited encryption support
only.
Routing Engine Function
The Routing Engine runs the Junos OS. Softwareprocessesthat 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
RoutingEngine 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.
NOTE: If two Routing Engines are installed, they must both be the same
hardware model.
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:
Chapter 5: Host Subsystem Components and Descriptions
•
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)
forout-of-band management. The port usesan 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 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
Documentation
• RJ-45 Connector Pinouts for MX Series Routing Engine AUX and CONSOLE Ports on
page 149
• RJ-45 ConnectorPinouts for an MX Series Routing Engine ETHERNET Port on page148
• Replacing an MX960 Routing Engine on page 333
MX960 RE-S-1300 and RE-S-2000 Routing Engine LEDs
Each Routing Engine has four LEDs that indicate its status. The LEDs, labeled MASTER,
HDD, ONLINE, and FAIL, are located directly on the faceplate of the Routing Engine.
Table 13 on page 31 describes the functions of the Routing Engine LEDs.
Table 13: Routing Engine LEDs
DescriptionStateColorLabel
Routing Engine is the Master.On steadilyBlueMASTER
Indicates activity on the hard disk drive.BlinkingGreenHDD
Routing Engine is transitioning online.BlinkingGreenONLINE
Routing Engine is functioning normally.On steadily
Routing Engine has failed.On steadilyRedFAIL
Related
Documentation
MX960 Routing Engine Description on page 29•
• Replacing an MX960 Routing Engine on page 333
RE-S-1800 Routing Engine Description for MX Series
Figure 16 on page 32 shows the Routing Engine 1800.
Figure 17 on page 32 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.
•
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, configuration files,
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 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.
•
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.
RE-S-1800 Routing Engine Boot Sequence
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.
Chapter 5: Host Subsystem Components and Descriptions
•
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 storage media 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 on
page 149
• RJ-45 ConnectorPinouts for an MX Series Routing Engine ETHERNET Port on page148
• Replacing an MX960 Routing Engine on page 333
• Supported Routing Engines by Router on page 40
RE-S-1800 Routing Engine LEDs
Each Routing Engine has four LEDs that indicate its status. The LEDs, labeled MASTER,
STORAGE, ONLINE, and OK/FAIL, are located directly on the faceplate of the Routing
Engine. Table 14 on page 33 describes the functions of the Routing Engine LEDs.
Table 14: Routing Engine LEDs
DescriptionStateColorLabel
Routing Engine is the Master.On steadilyBlueMASTER
Indicates activity on the SSD or Compact Flash.BlinkingGreenSTORAGE
Chapter 5: Host Subsystem Components and Descriptions
•
DRAM—Provides storage for the routing and forwarding tables and for other Routing
Engine processes.
•
One 10-Gigabit Ethernet interface between the 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)—Providea removablemedia interfacethrough 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—Brings the Routing Engine online or takes it offline when
pressed.
NOTE: The ONLINE/OFFLINE button must be pressed for a minimum of 4
seconds for the power off or power on to occur.
•
Extractor clips—Control the locking system that secures the Routing Engine.
•
LEDs—“RE-S-X6-64G Routing Engine LEDs” on page 36 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. The boot sequence is tried twice for SSD1
and SSD2.
Related
Documentation
Routing Engine Specifications on page 37•
• Upgrading to the RE-S-X6-64G Routing Engine in a Redundant Host Subsystem on
page 345
• Upgrading to the RE-S-X6-64G Routing Engine in a Nonredundant Host Subsystem
On routersthat accepttwo Routing Engines, you cannot mix RoutingEngine 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 40•
Documentation
Supported Routing Engines by Router
The following tables list the Routing Engines 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 40
•
M10i Routing Engines on page 41
•
M40e Routing Engines on page 41
•
M120 Routing Engines on page 42
•
M320 Routing Engines on page 42
•
MX5, MX10, MX40, and MX80 Routing Engine on page 43
•
MX104 Routing Engines on page 43
•
MX240 Routing Engines on page 43
•
MX480 Routing Engines on page 44
•
MX960 Routing Engines on page 45
•
MX2008 Routing Engines on page 46
•
MX2010 Routing Engines on page 46
•
MX2020 Supported Routing Engines on page 47
•
PTX3000 Routing Engines on page 47
•
PTX5000 Routing Engines on page 48
•
T320 Routing Engines on page 48
•
T640 Routing Engines on page 48
•
T1600 Routing Engines on page 49
•
T4000 Routing Engines on page 50
•
TX Matrix Routing Engines on page 50
•
TX Matrix Plus Routing Engines on page 51
•
TX Matrix Plus (with 3D SIBs) Routing Engines on page 51
M7i Routing Engines
Table 18 on page 41 lists the Routing Engines supported by the M7i router. The M7i router
MX960 Dense Port Concentrator Description on page 53
•
MX960 Dense Port Concentrator LEDs on page 56
•
DPCs Supported on MX240, MX480, and MX960 Routers on page 56
•
MX960 DPC Port and Interface Numbering on page 59
MX960 Dense Port Concentrator Description
A Dense Port Concentrator (DPC) is optimized for Ethernet density. Figure 20 on page 54
showstwo examplesof DPCs. For a list of the DPCs supported, see the MX Series Interface
The DPC assembly combines packet forwarding and Ethernet interfaces on a single
board,with either twoor four 10-Gbps PacketForwarding Engines. Each Packet Forwarding
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 (CBs).
The router has 11 dedicated DPC slots. DPCs install vertically in the front of the router
(see Figure 21 on page 55). The dedicated DPC slots are numbered 0 though 5, and 7
though 11, left to right. An additional multifunction slot labeled 2/6 supports either an
SCB or a DPC. A DPC can be installed in any slot that supports DPCs. You can install any
combination of DPC types in the router.
If a slot is not occupied by a DPC, a DPC blank panel must be installed to shield the empty
slot and to allow cooling air to circulate properly through 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.
Figure 21: DPCs Installed Vertically in the MX960 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
MX960 Dense Port Concentrator LEDs on page 56•
• MX960 Field-Replaceable Units on page 263
• Replacing an MX960 DPC on page 355
MX960 Dense Port Concentrator 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 “MX960 DPC and MPC LEDs on the Craft Interface” on page 18.
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
MX960 Dense Port Concentrator Description on page 53•
• Maintaining MX960 DPCs on page 450
• Replacing an MX960 DPC on page 355
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
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.
Chapter 6: Line Card Components and Descriptions
•
fpc—Slotin which the DPC is installed.On the MX960 router, the DPCs are represented
in the CLI as FPC 0 through FPC 11.
•
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 56 in the MX Series Interface Module Reference.
•
port—Port number.
The MX960 router supports up to twelve DPCs that install vertically and are numbered 0
through 11 from left to right.
Figure 22 on page 60 shows a 40-port Gigabit Ethernet DPC with SFP installed in slot 3
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 3. The DPC is shown as FPC 3 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-3*
Interface Admin Link Proto Local Remote
ge-3/0/0 up up
ge-3/0/1 up down
ge-3/0/2 up up
ge-3/0/3 up up
ge-3/0/4 up up
ge-3/0/5 up up
ge-3/0/6 up up
ge-3/0/7 up up
ge-3/0/8 up up
ge-3/0/9 up up
ge-3/1/0 up down
ge-3/1/1 up down
ge-3/1/2 up down
ge-3/1/3 up down
ge-3/1/4 up up
ge-3/1/5 up up
ge-3/1/6 up up
ge-3/1/7 up up
ge-3/1/8 up up
ge-3/1/9 up down
ge-3/2/0 up down
ge-3/2/1 up down
ge-3/2/2 up down
ge-3/2/3 up down
ge-3/2/4 up down
ge-3/2/5 up down
ge-3/2/6 up down
ge-3/2/7 up down
ge-3/2/8 up down
ge-3/2/9 up down
ge-3/3/0 up down
ge-3/3/1 up down
ge-3/3/2 up down
ge-3/3/3 up down
ge-3/3/4 up down
ge-3/3/5 up down
ge-3/3/6 up down
ge-3/3/7 up down
ge-3/3/8 up down
ge-3/3/9 up down
Related
MX960 Router Hardware and CLI Terminology Mapping on page 12•
Documentation
Interface Modules—FPCs and PICs
•
MX960 Flexible PIC Concentrator Description on page 62
•
MX960 Flexible PIC Concentrator (FPC) LEDs on page 65
•
FPCs Supported by MX240, MX480, and MX960 Routers on page 65
•
MX960 PIC Description on page 66
•
MX960 PIC LEDs on page 66
•
MX960 PIC Port and Interface Numbering on page 66
•
PICs Supported by MX240, MX480, and MX960 Routers on page 68
MX960 Flexible PIC Concentrator Description
A Flexible PIC Concentrator (FPC) occupies two Dense Port Concentrator (DPC) slots
on an MX Series router. The MX960 router has 11 dedicated DPC slots and one
multifunction slot that supports either a DPC, FPC, or Switch Control Board (SCB). The
dedicated DPC slots are numbered 0 though 5, and 7 though 11, left to right. The
multifunction slot is labeled 2/6. Up to six FPCs can be installed vertically in any two
slots that support FPCs (see Figure 23 on page 63). The interface corresponds to the
lowest numbered DPC slot for which the FPC is installed.
Figure 24: Typical FPCs Supported on the MX960 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 forward 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 “MX960 Component
Redundancy” on page 12. 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.
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
•
FPC online/offline button, located on the craft interface above the FPC
Related
Documentation
MX960 Flexible PIC Concentrator (FPC) LEDs on page 65•
• MX960 FPC Terminology
• Replacing an MX960 FPC on page 361
• Maintaining MX960 FPCs on page 455
• Troubleshooting the MX960 FPCs on page 492
MX960 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 “MX960 FPC LEDs on the Craft Interface” on page 18.
Related
Documentation
MX960 FPC Terminology•
• Replacing an MX960 FPC on page 361
• Maintaining MX960 FPCs on page 455
• Troubleshooting the MX960 FPCs on page 492
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 41 on page 65 lists FPCs supported by MX Series routers.
Table 41: FPCs Supported by MX Series Routers
Related
Documentation
MX Series FPC and PIC Overview•
Maximum
Number of PICs
SupportedFPC Model NumberFPC NameFPC Type
• PICs Supported by MX240, MX480, and MX960 Routers on page 68
• High Availability Features
MX960 PIC Description
PICs provide the physicalconnection 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. Up to two PICs can be installed in the slots
in each FPC. Up to six FPCs can be installed in an MX960 router. 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.
Related
Documentation
PICs Supported by MX240, MX480, and MX960 Routers on page 68•
• MX960 PIC LEDs on page 66
• Replacing an MX960 PIC on page 382
• Maintaining MX960 PICs on page 466
• Troubleshooting the MX960 PICs on page 494
• MX960 PIC Serial Number Label on page 516
MX960 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 68•
• MX960 PIC Description on page 66
• Replacing an MX960 PIC on page 382
• Maintaining MX960 PICs on page 466
MX960 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
slot number (representedas 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 number from the PIC number and port number:
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—Lowestslot number in which the FPC is installed. On the MX960 router, the FPCs
occupy two slots and are represented in the CLI as FPC 0 through FPC 10.
•
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 68 in the MX Series Interface Module Reference.
•
port—Port number.
The MX960 supports up to six FPCs that install vertically and are numbered from left to
right. Each FPC accepts up to two PICs.
Figure 25 on page 67 shows a Channelized OC12/STM4 Enhanced IQ (IQE) PIC with SFP
installed in PIC slot0of an FPC installed in slot3 and slot4.
Figure 25: MX960 PIC Interface Port Mapping
The show chassis hardware command output displays a Channelized OC12/STM4
Enhanced IQ (IQE) PIC (4x CHOC12 IQE SONET) installed in an MX FPC Type 2.
user@host> show chassis hardware
...
FPC 3 REV 01 710-024386 JW9571 MX FPC Type 2
CPU REV 03 710-022351 KE2986 DPC PMB
Table 42: PICs Supported by MX240, MX480, and MX960 Routers (continued)
First Junos OS ReleaseTypePortsPIC Model NumberPIC Name
9.431PC-1OC192-SON-XFPSONET/SDH OC192c/STM64 PIC with
XFP
Related
Documentation
MX Series FPC and PIC Overview•
• FPCs Supported by MX240, MX480, and MX960 Routers on page 65
• High Availability Features
Interface Modules—MPCs and MICs
•
MX960 Application Services Modular Line Card Description on page 69
•
MX960 Application Services Modular Storage Card Description on page 72
•
MX960 Application Services Modular Processing Card Description on page 73
•
MX960 AS MSC LEDs on page 74
•
MX960 AS MXC LEDs on page 75
•
MIC/MPC Compatibility on page 75
•
MX960 Modular Interface Card Description on page 82
•
MX960 Modular Interface Card (MIC) LEDs on page 82
•
MICs Supported by MX Series Routers on page 82
•
MX960 MIC Port and Interface Numbering on page 86
•
MX960 Modular Port Concentrator Description on page 89
•
MX960 Modular Port Concentrator LEDs on page 92
•
MPCs Supported by MX Series Routers on page 92
MX960 Application Services Modular Line Card Description
The Application Services Modular Line Card (AS MLC) is an X86-based card for MX960,
MX480, and MX240 routers to deliver integrated application service solutions. The first
application that network operators can take advantage of is the Junos Content Encore
system, a high-throughput, solid state storage platform for media rich content delivery.
Additionally, the AS MLC can serve as the platform for Juniper Networks JunosV App
Engine, powering a host of network applications directly embedded into your MX Series
3D Universal Edge Routers.
The AS MLC is modular and decouples CPU and storage in individual field-upgradeable
units. The AS MLCs are designed to enable application throughput up to 50 Gbps and a
storage capacity of 400 gigabytes (GB) of NAND Flash.
Figure 26: Application Services Modular Line Card (AS MLC)
MX960 AS MLC Function
The AS MLC provides modular processing and modular storage. Installedon the AS MLC,
the Junos Content Encore system operates as a caching application, in either HTTP
reverse proxy mode or HTTP transparent proxy mode, to manage client requests for
content and the distribution of the content to clients from origin servers. In the future,
the AS MLC will run other Juniper Networks router services and applications, and serve
as a virtualized platform for third-party applications. The AS MLC provides Ethernet
switching and high-speed fabric interface to MX routers. Graceful Routing Engine
switchover is also supported on the AS MLC.
Integrated with application forwarding on MX Series routers, the AS MLC provides
increased service flexibility with reduced power and space requirements for the network
infrastructure.
The AS MLC Modular Carrier Card (AS MCC), the carrier card of the AS MLC, fits vertically
in the front of the MX960 router (see Figure 27 on page 71).