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
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:
•
M320
Documentation Conventions
Table 1 on page xxiv defines notice icons used in this guide.
Represents names of configuration
statements, commands, files, and
directories;configuration hierarchylevels;
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 portis 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 lineasthe configuration statement
to which it applies.
Encloses a variable for which you can
substitute one or more values.
Identifies a level in the configuration
hierarchy.
Identifies a leaf statement at a
configuration hierarchy level.
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 at the Juniper Networks Technical
Documentation site at http://www.juniper.net/techpubs/index.html, simply click the
stars to rate thecontent, and usethe pop-upform to provide us with information about
your experience. Alternately, you can use the online feedback form at
https://www.juniper.net/cgi-bin/docbugreport/.
Separates levels in a hierarchy of menu
selections.
In the configuration editor hierarchy,
select Protocols>Ospf.
E-mail—Sendyourcomments to techpubs-comments@juniper.net.Includethe document
or topic name, URL or page number, and software version (if applicable).
Requesting Technical Support
Technical product support is availablethrough the Juniper Networks Technical Assistance
Center (JTAC). If you are a customer with an active J-Care or JNASC 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 byproductserial number, use ourSerial 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 M320 Multiservice Edge Router is a high-density edge aggregation, routing, and
service creation platform that builds on Juniper Networks service-built edge design.
Constructed with separations between the control plane, forwarding plane, and services
plane, the router supports multiple services on a single platform. The Junos OS runs on
a control subsystem with dedicated hardware, ensuring that control functions are
performed without affecting theforwardingsubsystem.Forwardingand packet processing
operations in the router are performed by dedicated programmable ASICs that enable
the router to achieve data forwarding rates that match current fiber-optic capacity. This
design eliminates processing and traffic bottlenecks, permitting the router to achieve
high performance.
The router canbe deployed in core,peering, and datacenter applications, but is optimized
for dense edge aggregation and service creation. The M320 router can provide a single
point of edge aggregation for thousands of customers over any access type, including
ATM, Frame Relay, Ethernet, and TDM, at any speed from DS0 up to OC192/STM64 and
10-Gigabit Ethernet.
The router is a half-rack chassis that supports up to eight Flexible PIC Concentrators
(FPCs) providing up to 64 SONET/SDH OC48/STM16, 16 SONET/SDH OC192/STM64,
or 160 Gigabit Ethernet ports for the router. In a standalone configuration, the router's
maximum aggregate throughput is 320 gigabits per second (Gbps), half duplex. The
router supports up to eight of these FPCs:
•
Type 1 FPCs—Rated at 4 Gbps full duplex, supports up to four PICs.
•
Type 2 FPCs—Rated at 16 Gbps full duplex, supports up to four PICs.
•
Type 3 FPCs—Rated at 20 Gbps full duplex, supports up to two PICs, including
higher-speed PICs.
The router can operate with any FPC type in any slot. Type 1 FPCs and Type 2 FPCs each
support four PICs, and Type 3 FPCs supports two PICs.
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:
•
Switch Interface Boards (SIBs)—A fully configured router has four SIBs. Each FPC has
a dedicated ASICwith fourhigh-speed links that connect tothe SIBs (one link per SIB).
In the event of a complete SIB failure, the traffic is forwarded across the remaining
three planes with a slight degradation in performance. When the failed SIB is replaced,
the router regains full forwarding capacity.
•
Host subsystem—The host subsystem consists of a Routing Engine functioning together
with a CB. To operate, each host subsystem requires a Routing Engine installed in an
adjacent slot to the CB. 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 or is taken
offline, the backup can take over as the master.
Related
Documentation
For information about the effect of taking the host subsystem offline, see “Taking the
M320 HostSubsystem Offline” on page213. Formore information about highavailability
features, see the Junos OS High Availability Library for Routing Devices.
•
Powersupplies—A router witha minimum of three AC power supplies or fourDC power
supplies is fully power redundant. In the AC configuration, all power supplies share the
load evenly. In the DC configuration, two power supplies share the load to some of the
components, and two other power supplies share the load to the remaining
components. In both configurations, if one power supply fails, the remaining power
supplies can provide full power to the router.
•
Cooling system—The coolingsystemhas 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.
Errata with the M320 Router Documentation on page 5
Outstanding Issues with the M320 Router
This section lists outstanding hardware issues with the M320 Multiservice Edge Router.
For information about software issues, see the Junos OS Release Notes.
•
There are currently no outstanding issues for the M320 router.
Related
Documentation
Errata with the M320 Router Documentation on page 5•
Errata with the M320 Router Documentation
There are currently no outstanding documentation issues for the M320 router.
Related
Documentation
• Outstanding Issues with the M320 Router on page 5
M320 Cable Management System Description on page 12
•
M320 Connector Interface Panel (CIP) Description on page 13
•
M320 Craft Interface Description on page 15
•
M320 Craft Interface Alarm LEDs and ACO/LT Button on page 16
•
M320 Craft Interface LED Display and Navigation Buttons on page 16
•
M320 Craft Interface Host Subsystem LEDs on page 18
•
M320 Craft Interface FPC LEDs and Online/Offline Buttons on page 18
•
M320 Craft Interface Power Supply LEDs on page 19
•
M320 Craft Interface SIB LEDs on page 19
M320 Chassis Description
The router chassis is a rigid sheet metal structure that houses all the other router
components (see Figure 1 on page 8). The chassis measures 34.80 in. (88.4 cm) high,
17.43 in. (44.3 cm) wide, and 25.64 in. (65.1 cm) deep (from the front-mounting flanges
to the rearof thechassis). The chassiscan be installedin many types of racks or cabinets.
For moreinformation,see “M320Cabinet Size and Clearance Requirements” on page88,
and “Rack Requirements for the M320 Router” on page 87.
The chassis includes the following features (see Figure 1 on page 8, Figure 2 on page 9,
and Figure 3 on page 10):
•
One pair of metal adjustable center-mounting brackets that can be attached to one
of 11 positions on the side of the chassis. You can use the brackets for mounting the
chassis in the rack or cabinet.
•
Two installation handles on the top to facilitate positioning the router in the rack. Do
not use the handles to lift the router.
•
Two electrostatic discharge points (banana plug receptacles): one front and one rear.
Figure 1: Front View of a Fully Configured Router Chassis
CAUTION: Before removing or installing components of a router, attach
an ESD strap to an ESD point and place the other end of the strap around
your bare wrist. Failure to use an ESD strap could result in damage to the
router.
Figure 3: Rear View of a Fully Configured DC-Powered Router Chassis
For chassis serial number information , see “Locating M320 Component Serial Numbers
Using the CLI” on page 299.
Related
Documentation
M320 Router Description on page 3•
• Installing the M320 Chassis Using a Mechanical Lift on page 136
• Installing the M320 Chassis in the Rack Manually on page 151
• M320 Installation Safety Guidelines on page 323
• M320 Router Physical Specifications on page 86
M320 Midplane Description
The midplane is located in the center of the chassis and forms the rear of the FPC card
cage (see Figure 4 on page 11). The FPCs install into the midplane from the front of the
chassis, and the SIBs, Routing Engines, and CBs install into the midplane from the rear
of the chassis. The power supplies and cooling system components also connect to the
midplane.
The midplane performs the following major functions:
•
Data path—Data packets are transferred across the midplane from the Packet
Forwarding Engine on the originating FPC to the SIBs, and from the SIBs across the
midplane to the Packet Forwarding Engine on the destination FPC.
•
Power distribution—The router power supplies are connected to the midplane, which
distributes power to all the router components.
•
Signal path—Themidplane provides the signal path to theFPCs, SIBs, RoutingEngines,
CB, and other system components for monitoring and control of the system.
Figure 4: Midplane
For chassis serial number information , see “Locating M320 Component Serial Numbers
• M320 Cabinet Size and Clearance Requirements on page 88
M320 Fuses
The router uses fuses from the Cooper Bussman brand GMT series for the CB, SIBs, and
FPCs. The fuses are located in the rear of the midplane behind the power supply in slot
PEM0. When the fuse for a component blows, the component stops functioning even
though it is installed correctly and the power supplies are providing power to the router.
For more information, see “Troubleshooting the M320 Fuses” on page 290. For fuse
replacement instructions, see “Replacing an M320 Fuse” on page 199.
Related
Documentation
M320 Fuse Specifications on page 99•
• Preventing Electrostatic Discharge Damage to an M320 Router on page 318
M320 Cable Management System Description
The cable management system (see Figure 5 on page 12) consists of a row of nine
semicircular plastic bobbinsmounted onthe front of the router below the FPCcard cage.
The PIC cables pass between the bobbins and into thetray, keeping the cables organized
and securely in place. The curvature of the bobbins also helps maintain the proper bend
radius for optical PIC cables.
You can pull the cable management system up and outward to lock it into the
maintenance position. This allows you to access the lower fan tray and the front air filter.
Figure 5: Cable Management System
The router; ships with an accessory box that contains four cable guards—two upper and
two lower—that you can install on the front-mounting flanges of the chassis after you
have mounted the chassis in a rack or cabinet. The cable guards protect the PIC and CIP
cables from rubbing against the front edges of the chassis.
Included with your router shipment is a clear plastic cable cover that you can attach to
slots in the cable guards without using tools. The cable cover prevents the PIC and CIP
cables from being disturbed or snagged.
The CIP is located at the left side of the FPC card cage. The front electrostatic discharge
point is located near the bottom of the CIP.
•
CIP Components on page 13
•
Routing Engine Ports on page 14
•
Alarm Relay Contacts on page 15
CIP Components
The Connector Interface Panel (CIP) consists of Ethernet, console, and auxiliary
connectors for the Routing Engines and alarm relay contacts (see Figure 6 on page 14).
The CIP has two sets of ports that you use to connect the Routing Engines to external
management devices. From thesemanagementdevices, you can use the CLIto configure
the router.
The upper set of ports, labeled HOST 0, connects to the Routing Engine in slot RE0; and
the lower set,labeledHOST1, connects to the Routing Enginein slot RE1. Each set includes
the following ports:
•
ETHERNET—Connects the Routing Engine through an Ethernet connection to a
management LAN (or any other device that plugs into an Ethernet connection) for
out-of-band management. The port uses an autosensing RJ-45 connector to support
both 10- and 100-Mbps connections. Two small LEDs on the right edge of the port
indicate the connection in use: the LED labeled ETHERNET lights yellow or green for a
10-Mbps or 100-Mbps connection, and the LED labeled ACT lights green when traffic
is passing through the port.
•
CONSOLE—Connects the Routing Engine to a system console through an RS-232
(EIA-232) serial cable.
•
AUX— Connects the Routing Engine to a laptop, modem, or other auxiliary device
through an RS-232 (EIA-232) serial cable.
The CIPhas two alarm relay contacts forconnecting the router to external alarm devices.
Whenever a system conditiontriggers either thered or yellow alarmon the craftinterface,
the alarm relay contacts are also activated. The alarm relay contacts are located below
the Routing Engine ports. The terminal blocks that plug into the alarm relay contacts are
supplied with the router. They accept wire of any gauge between 28-AWG and 14-AWG
(0.08 and 2.08 mm2), which is not provided. Use the gauge of wire appropriate for the
external device you are connecting.
Related
Documentation
M320 Craft Interface Description on page 15•
• Replacing the M320 CIP on page 189
M320 Craft Interface Description
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 onthe front of the routerabovethe FPCs.Figure 7 onpage 15
shows the front panel of the M320 craft interface.
Figure 7: Front Panel of the Craft Interface
Related
Documentation
• M320 Craft Interface Alarm LEDs and ACO/LT Button on page 16
• M320 Craft Interface Host Subsystem LEDs on page 18
Two large alarm LEDs are located at the upper left 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 connector interface panel (CIP). The LCD on the craft interface reports
the cause of the alarm.
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 CIP. However, the LCD continues to report the alarm message until
you clear the condition that caused the alarm.
Table 3 on page 16 describes the alarm LEDs and alarm cutoff button in more detail.
Table 3: Alarm LEDs and Alarm Cutoff/Lamp Test Button
DescriptionStateColorShape
Critical alarm LED—Indicates a criticalcondition that
can cause the router to stop functioning. Possible
causes include component removal, failure, or
overheating.
WarningalarmLED—Indicatesa serious butnonfatal
error condition, such as a maintenance alert or a
significant increase in component temperature.
Alarm cutoff/lamptestbutton—Deactivates red and
yellowalarms. Causes allLEDs onthe craft interface
to light (for testing purposes), when pressed and
held.
Related
Documentation
On steadilyRed
On steadilyYellow
——
M320 Craft Interface Description on page 15•
• M320 Connector Interface Panel (CIP) Description on page 13
• M320 Craft Interface LED Display and Navigation Buttons on page 16
M320 Craft Interface LED Display and Navigation Buttons
A four-line LED display is located in the craft interface, along with six navigation buttons.
The LED display operates in two modes:
During normaloperation, the LEDdisplay operatesin idle mode and reports current status
information, as shown in Figure 8 on page 17.
Figure 8: LED Display in Idle Mode
The lines in the display report the following information:
•
First line—Router name.
•
Second line—Length of time the router has been running, reported in the following
form:
Up days + hours:minutes
•
Third and fourth lines—Status messages, which rotate at 2-second intervals. Some
conditions, such as removal or insertion of a system component, can interrupt the
messages.
To add a message that alternates every 2 seconds with the default status messages,
use thesetchassis displaymessage command. For moreinformation,see the CLIExplorer.
When a red or yellow alarm occurs, the LED display switches to alarm mode and reports
about the alarm condition, as shown in Figure 9 on page 17.
Figure 9: LED Display in Alarm Mode
The lines in the display report the following information:
•
First line—Router name.
•
Second line—Number of active alarms.
•
Third and fourth lines—Individual alarm messages, with the most severe condition
shown first. The prefix oneach line indicates whether the alarmis ared (R) or yellow (Y)
alarm.
For a list of alarm messages that can appear on the LED display, see “M320 Chassis and
• M320 Craft Interface Alarm LEDs and ACO/LT Button on page 16
M320 Craft Interface Host Subsystem LEDs
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
RE0 and the CB in slot CB0. The LEDs labeled RE1 show the status of the Routing Engine
in slot RE1 and the CB in slot CB1. Table 4 on page 18 describes the functions of the host
subsystem LEDs.
Table 4: M320 Host Subsystem LEDs
Related
Documentation
M320 Host Subsystem Description on page 23•
• M320 Craft Interface Description on page 15
DescriptionStateColorLabel
Host is offline.On steadilyRedFAIL
Host is online and is functioning normally.On steadilyGreenOK
Host is functioning as the master.On steadilyGreenMASTER
• M320 Craft Interface Alarm LEDs and ACO/LT Button on page 16
M320 Craft Interface FPC LEDs and Online/Offline Buttons
Each FPC slot has two LEDs that indicate its status. The FPC LEDs, labeled FPC0 through
FPC7, are located along the bottom of the craft interface. Table 5 on page 18 describes
the functions of the FPC LEDs.
Table 5: FPC LEDs
DescriptionStateColorLabel
FPC has failed.On steadilyRedFAIL
FPC is functioning normally.On steadilyGreenOK
FPC is starting up.Blinking
Related
Documentation
M320 Flexible PIC Concentrator (FPC) Description on page 49•
• M320 Craft Interface Description on page 15
• M320 Connector Interface Panel (CIP) Description on page 13
Each power supply has two LEDs on the craft interface that indicate its status. The LEDs,
labeled 0 through 3, are located in the middle of the craft interface under the POWER
label. Table 6 on page 19 describes the functions of the power supply LEDs.
Table 6: Power Supply LEDs on the Craft Interface
Chapter 3: Chassis Components and Descriptions
DescriptionStateColorLabel
Power supply has failed.On steadilyRedFAIL
Power supply is functioning normally.On steadilyGreenOK
Related
Documentation
M320 Craft Interface Description on page 15•
• M320 AC Power Supplies Description on page 73
• M320 DC Power Supplies Description on page 74
M320 Craft Interface SIB LEDs
Each SIBhas two LEDson thecraftinterfacethat indicate its status. The SIB LEDs, labeled
SIB0 through SIB2, are located on the upper right of the craft interface. The ACTIVE LED
on the SIB faceplate is not replicated on the craft interface. Table 7 on page 19 describes
the functions of the SIB LEDs.
The cooling system consists of the following components:
•
Two front fan trays
•
Front air filter
•
Rear fan tray
•
Rear air filter
The cooling system components work together to keep all router components within the
acceptable temperature range (see Figure 10 on page 21). All fan trays and filters are
hot-insertable and hot-removable. The two front fan trays are interchangeable. The front
and rear fan trays are not interchangeable.
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 some or all of the hardware
components.
Related
Documentation
• M320 Cabinet Airflow Requirements on page 90
• Maintaining the M320 Fan Trays on page 268
• Troubleshooting the M320 Cooling System on page 287
M320 RE-A-1800 Routing Engine Description on page 28
•
RE-A-1800 Routing Engine LEDs on page 31
•
Routing Engine Specifications on page 31
•
Supported Routing Engines by Router on page 34
•
M320 Control Board (CB) Description on page 45
•
M320 Control Board (CB) LEDs on page 46
M320 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. To operate, each host
subsystem functions as a unit; the Routing Engine requires the corresponding Control
Board (CB) and vice versa.
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 RE0.
NOTE: Each host subsystem has three LEDs that display its status. The LEDs
that report host module status (including Routing Engine status) are located
in the middle of the craft interface rather than the Routing Engine faceplate.
For more information about the host subsystem LEDs, see “M320 Craft
NOTE: For specific information about Routing Engine components (for
example, the amount of DRAM), issue the show chassis routing-engine
command.
NOTE: If two Routing Engines are installed, they must both be the same
hardware model.
Related
Documentation
Maintaining the M320 Host Subsystem on page 269•
• Taking the M320 Host Subsystem Offline on page 213
M320 Routing Engine Description
The Routing Engine runs the Junos operating system (OS). The 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 upperrear of the chassis inthe slots labeled RE0 and RE1. Each Routing Engine requires
a CB to be installed in the adjacent slot. RE0 installs below CB0, and RE1 installs above
CB1. A Routing Engine does not power up if a CB is not present in the adjacent slot.
If two Routing Engines are installed, one functions as the master, and the other acts as
the backup. If themaster Routing Enginefails or is removed, and the backup is configured
appropriately, the backup can take over as the master. If the Routing Engines are
configured for nonstop active routing, the backup Routing Engine automatically
synchronizes its configuration and state with the master Routing Engine. Any update to
the master Routing Engine state is replicated onthe backup RoutingEngine. If the backup
Routing Engine assumes mastership, packet forwarding continues through the router
without interruption. For more information about nonstop active routing, see the JunosOS High Availability Library for Routing Devices.
The master Routing Engine (if nonstop active routing is configured) and the backup
Routing Engine are hot-removable and hot-insertable. A nonredundant Routing Engine
or master Routing Engine (if nonstop active routing is not configured) is hot-pluggable.
The M320 router supports the following Routing Engines:
Chapter 5: Host Subsystem Components and Descriptions
Related
Documentation
M320 Connector Interface Panel (CIP) Description on page 13•
• Replacing an M320 Routing Engine on page 216
• M320 Routing Engine 600 Description on page 25
• M320 Routing Engine 1600 Description on page 26
• M320 Routing Engine 2000 Description on page 27
• M320 RE-A-1800 Routing Engine Description on page 28
M320 Routing Engine 600 Description
Each M320 Routing Engine 600 consists of the following components:
•
CPU—Runs Junos OS to maintain the router's routing tables and routing protocols. It
has a Pentium-class processor.
•
DRAM—Provides storage for the routing and forwarding tables and for other Routing
Engine processes.
•
CompactFlash card—Provides primarystorage forsoftware images, configuration files,
and microcode. The CompactFlash card is inaccessible from outside the router.
•
Hard disk—Provides secondary storage for log files, memory dumps, and rebooting the
system if the CompactFlash card fails.
•
One PC card slot—Accepts a removable PC card, which stores software images for
system upgrades.
•
LED—Indicatesdisk activity forthe internalIDE interface. It does not necessarily indicate
routing-related activity.
•
Interfaces for out-of-band management access—Provide information about
Routing Engine status to devices (console, laptop, or terminal server) that can be
attached to access ports located on the Connector Interface Panel (CIP).
Each Routing Engine has one 10/100-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.
On the RE-600-2048 Routing Engine, the boot sequence for the storage media is as
follows: the PC card (if present), then the CompactFlash card (if present), then the hard
disk.
The device from which the router boots is called the primary boot device, and the other
device is the alternate boot device.
NOTE: If the router boots from an alternatebootdevice,a yellowalarmlights
M320 Connector Interface Panel (CIP) Description on page 13•
• M320 Routing Engine Description on page 24
• Replacing an M320 Routing Engine on page 216
M320 Routing Engine 1600 Description
Figure 11: Routing Engine 1600
Each Routing Engine(shown inFigure11 onpage26) consists of the following components:
•
CPU—Runs Junos OS to maintain the router's routing tables and routing protocols. It
has a Pentium-class processor.
•
DRAM—Provides storage for the routing and forwarding tables and for other Routing
Engine processes.
•
CompactFlash card—Provides primarystorage forsoftware images, configuration files,
and microcode. The CompactFlash card is inaccessible from outside the router.
•
Hard disk—Provides secondary storage for log files, memory dumps, and rebooting the
system if the CompactFlash card fails.
•
PC card slots—Accept removable PC cards, which store software images for system
upgrades.
•
LED—Indicatesdisk activity forthe internalIDE interface. It does not necessarily indicate
routing-related activity.
•
Interfaces for out-of-band management access—Provide information about
Routing Engine status to devices (console, laptop, or terminal server) that can be
attached to access ports located on the Connector Interface Panel (CIP).
Each Routing Engine has one 10/100-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.
Chapter 5: Host Subsystem Components and Descriptions
On the RE-1600-2048 Routing Engine, the boot sequence for the storage media is as
follows: the PC card in SLOT 0 (if present), then the PC card in SLOT 1 (if present), then
the CompactFlash card (if present), then the hard disk.
The device from which the router boots is called the primary boot device, and the other
device is the alternate boot device.
NOTE: If the router boots from an alternatebootdevice,a yellowalarmlights
the LED on the router’s craft interface.
Related
Documentation
M320 Connector Interface Panel (CIP) Description on page 13•
• M320 Routing Engine Description on page 24
• Replacing an M320 Routing Engine on page 216
M320 Routing Engine 2000 Description
Each Routing Engine (shown in Figure 12 on page 28) consists of the following
components:
•
CPU—Runs Junos OS to maintain the router's routing tables and routing protocols. It
has a Pentium-class processor.
•
DRAM—Provides storage for the routing and forwarding tables and for other Routing
Engine processes.
•
CompactFlash card—Provides primarystorage forsoftware images, configuration files,
and microcode. The CompactFlash card is inaccessible from outside the router.
•
Hard disk—Provides secondary storage for log files, memory dumps, and rebooting the
system if the CompactFlash card fails.
•
USB port—Provides a removable media interface through which you can install the
Junos OS manually. The Junos OS supports USB version 1.0.
•
LED—Indicatesdisk activity forthe internalIDE interface. It does not necessarily indicate
routing-related activity.
•
Interfaces for out-of-band management access—Provide information about
Routing Engine status to devices (console, laptop, or terminal server) that can be
attached to access ports located on the Connector Interface Panel (CIP).
Each Routing Engine has one 10/100-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.
On the RE-A-2000-4096 Routing Engine, the boot sequence for the storage media is as
follows: USB device (if present), then the CompactFlash card (if present), then the hard
disk.
The device from which the router boots is called the primary boot device, and the other
device is the alternate boot device.
NOTE: If the router boots from an alternatebootdevice,a yellowalarmlights
the LED on the router’s craft interface.
Related
Documentation
M320 Connector Interface Panel (CIP) Description on page 13•
• M320 Routing Engine Description on page 24
• Replacing an M320 Routing Engine on page 216
M320 RE-A-1800 Routing Engine Description
•
Routing Engine Components on page 28
•
Routing Engine Boot Sequence on page 30
Routing Engine Components
Each Routing Engine (shown in Figure 13 on page 29 and Figure 14 on page 29) 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 the
Junos OS manually. See Figure 15 on page 30. Junos supports USB version 1.0.
•
CompactFlash card—Provides primarystorage forsoftware images, configuration files,
and microcode. The disk is a fixed compact flash and is inaccessible from outside the
router.
Chapter 5: Host Subsystem Components and Descriptions
•
SSD—Provides storage for log files, memory dumps, and rebooting the system if the
CompactFlash card fails.
•
LED—Indicates disk activity. It does not necessarily indicate routing-related activity.
NOTE: The LEDs that report host module status (including Routing Engine
status) are on the craft interface rather than the Routing Engine faceplate.
•
Storage LED—Indicates disk activity for the solid state disk drive.
•
Interfaces for out-of-band management access—Provide information about
Routing Engine status to devices (console, laptop, or terminal server) that can be
attached to access ports located on the craft interface.
Each Routing Engine has one 10/100-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.
•
Offline button—Takes the Routing Engine offline when pressed.
•
Extractor clips—Control the locking system that secures the Routing Engine.
NOTE: For specific information about Routing Engine components (for
example, the amount of DRAM), issue the show chassis routing-engine
command.
Figure 15: USB Memory Device in an Routing Engine
Routing Engine Boot Sequence
The Routing Engine boots from the storage media in this order: the USB device, then the
CompactFlash card (if present), then the two solid state drives (SSD) and then the LAN.
The device from which the router boots is called the primary boot device, and the other
device is the alternate boot device.
Related
Documentation
• M320 Routing Engine Description on page 24
• M320 Host Subsystem Description on page 23
• RE-A-1800 Routing Engine LEDs on page 31
• Maintaining the M320 Host Subsystem on page 269
• Taking the M320 Host Subsystem Offline on page 213
NOTE: If the router boots from an alternatebootdevice,a yellowalarmlights
NOTE: The memory in Table 9 on page 31 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 Routing Enginesthat each router supports, the firstsupported
release for the Routing Engine inthe specified router, themanagement Ethernet interface,
and the internal Ethernet interfaces for each Routing Engine.
•
M7i Routing Engines on page 34
•
M10i Routing Engines on page 35
•
M40e Routing Engines on page 35
•
M120 Routing Engines on page 36
•
M320 Routing Engines on page 36
•
MX104 Routing Engines on page 37
•
MX240 Routing Engines on page 37
•
MX480 Routing Engines on page 38
•
MX960 Routing Engines on page 39
•
MX2010 Routing Engines on page 39
•
MX2020 Routing Engines on page 40
•
PTX3000 Routing Engines on page 40
•
PTX5000 Routing Engines on page 40
•
T320 Routing Engines on page 41
•
T640 Routing Engines on page 41
•
T1600 Routing Engines on page 42
•
T4000 Routing Engines on page 43
•
TX Matrix Routing Engines on page 44
•
TX Matrix Plus Routing Engines on page 44
•
TX Matrix Plus (with 3D SIBs) Routing Engines on page 44
M7i Routing Engines
Table 11 on page 35 lists the Routing Engines supported by the M7i router. The M7I router
Chapter 5: Host Subsystem Components and Descriptions
Table 30: Routing Engines on TX Matrix Plus with 3D SIBs
First Supported 32-bit
Junos OS Release
-RE-TXP-SFC
RE-DUO-C2600-16G
Related
Documentation
Name in CLI
OutputModel Number
or
RE-DUO-2600
Routing Engine Specifications on page 31•
• Understanding Internal Ethernet Interfaces
• Understanding Management Ethernet Interfaces
M320 Control Board (CB) Description
Each CB works with an adjacent Routing Engine to provide control and monitoring
functions for the router (see Figure 16 on page 45). These functions include determining
Routing Engine mastership, controlling power andreset for the other router components,
monitoring and controlling fan speed, and monitoring system status.
You can install one or two CBs in the router. They install into the upper rear of the chassis
in the slots labeled CB0 and CB1 (referred to as CB-0 and CB-1, top to bottom) (referred
to as CB-0 and CB-1, top to bottom). Iftwo CBs are installed, one functions as the master
CB and the other as its backup. If the master fails or is removed, the backup restarts and
becomes the master.
First Supported
64-bit Junos OS
Release
11.4
Management
Ethernet
Interface
em064-bit Junos OS:
Internal
Ethernet
Interface
ixgbe0
ixgbe1
Each CB requires a Routing Engine to be installed in the adjacent slot. CB0 installs above
RE0, and CB1 installs below RE1. A CB cannot function if a Routing Engine is not present
M320 Flexible PIC Concentrator (FPC) Description on page 49
•
M320 FPC Terminology on page 53
•
M320 FPCs Supported on page 53
•
M320 PIC Description on page 54
•
M320 PICs Supported on page 55
•
M320 End-of-Life PICs Supported on page 64
•
M320 PIC Combination Limitations on page 66
•
M320 PIC/FPC Compatibility on page 66
M320 Flexible PIC Concentrator (FPC) Description
Up to eight Flexible PIC Concentrators (FPCs) install vertically in the front of the router
(see Figure 17 on page 50). The FPC slots are numbered left to right from FPC0 to FPC7.
Depending on the FPC type, an FPC has either two or four slots into which a PIC can be
installed (see “M320 FPCs Supported” on page 53 for more information). An FPC can be
installed into any FPC slot on the router, regardless of which PICs it contains.
If a slot is not occupied by an FPC, an FPC blank panel must be installed to shield the
empty slot and to allow cooling air to circulate properly through the router.
Each FPC consists of the following components:
•
FPC card carrier, which includes the PIC slots.
•
One Packet Forwarding Engine consisting of Layer 2/Layer 3 Packet Processing ASICs,
Switch Interface ASICs, Internet Processor ASICs, and an MMB, which includes the
Queuing and Memory Interface ASICs.
•
Midplane connectors and power circuitry.
•
Processorsubsystem(PMB), which includesa 288-MHz CPU,systemcontroller, 256 MB
of SDRAM, and two Fast Ethernet interfaces.
•
Two LEDs, located on the craft interface above the FPC, that display the status of the
FPC. For more information about the FPC LEDs, see “M320 Craft Interface FPC LEDs
and Online/Offline Buttons” on page 18.
•
FPC online/offline button, located on the craft interface above the FPC.
The 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.
Each FPC contains a memory subsystem (MMB) that is managed by the Queuing and
Memory Interface ASICs.
FPCs are hot-removable and hot-insertable, as described in “M320 Field Replaceable
Units” on page 185. 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 is not affected. For FPC replacement
instructions, see “Replacing an M320 FPC” on page 227.
Figure 17: FPC Installed in Router Chassis
The M320 router supports the following types of FPCs (see Figure 18 on page 51 ):
•
FPC1, Enhanced II FPC1, and Enhanced III FPC1—Rated at 4 gigabits per second (Gbps)
full duplex
•
FPC2, Enhanced II FPC2, and Enhanced III FPC2—Rated at 16 Gbps full duplex
Regardless of whether you are holding an FPC vertically or horizontally, this document
uses the same terms for all four edges of the FPC (see Figure 21 on page 53):
•
Faceplate—Edge of the FPC that has slots into which you insert the PICs
•
Connectoredge—Edgeopposite the faceplate; this edgehas the connectors that attach
to the midplane
•
Top edge—Edge at the top of the FPC when it is vertical
•
Bottom edge—Edge at the bottom of the FPC when it is vertical
Figure 21: FPC Edges
Related
Documentation
M320 FPCs Supported
Table 32 on page 54 lists the FPCs that the M320 router supports. You can install any
combination of the following FPCs in the M320 router.
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. You can install up to four PICs in the slots
of each Type 1 and Type 2 FPC, and up to two PICs in the slots of each Type 3 FPC. Type
1 and Type 2 PICs have captive screws at their upper and lower corners. Type 3 PICs have
an upper ejector handle and a lower captive screw.
The router supportsvarious PICs, includingATM, Channelized, Gigabit Ethernet,IP Services,
and SONET/SDH interfaces. Blank PICs resemble other PICs but do not provide any
physical connection or activity. When a slot is not occupied by a PIC, you must insert a
blank PIC to fill the empty slot and ensure proper cooling of the system.
Table 46: End-of-Life PICs Supported in the M320 Router (continued)
First Junos OS
Release
SupportConnectorModel NumberPortsPIC Family and Type
1SONET/SDH OC192c/STM64 EOL
PICs (M320 Router)
Related
M320 PIC Description on page 54•
Documentation
M320 PIC Combination Limitations
In most cases, you can install PICs of different media types on the same FPC as long as
the FPC and the router support those PICs. However, configuration rules might limit
certain combinations of PICs on some platforms.
Newer Junos OS services for some PICs can require significant Internet Processor ASIC
memory.Ethernet and SONET PICs typically donot uselarge amounts of memory. Gigabit
Ethernet, ATM2, IQ serial PICs, and Multiservices PICs use more. To conserve memory,
you can group PICs in the same family together on the same FPC.
If you have different PIC families on a single FPC, review the configuration rules to plan
which PICs to install on the FPCs for your router. Consult technical bulletin
PSN-2007-01-023 for information about configuration rules for PIC combinations on the
Juniper Networks Support site at https://www.juniper.net/alerts/.
When you upgrade toJunos OS Release 7.5or later,a warning appears if any configuration
rules affect your PIC combinations. If you continue the installation, one or more PICs
might appear to be online (the LEDs are on), but the Junos OS cannot enable them and
they cannot pass traffic. As a workaround, you can:
5.4PC-1OC192-SON-LR
PC-1OC192-SON-SR2
•
Install a Junos OS release that supports the combination.
•
Install PICs on a different FPC.
•
Remove PICs from the affected FPC.
Related
Documentation
M320 PIC Description on page 54•
• M320 PICs Supported on page 55
• M320 FPCs Supported on page 53
• M320 PIC/FPC Compatibility on page 66
M320 PIC/FPC Compatibility
The PIC/FPC compatibility matrixes list the first Junos OS Release in which an FPC
supports each PIC currently supported for the M320 router. For example, JunosOS Release
7.5 is the first release in which the E-II-FPC1 supports the ATM2 OC3/STM1 IQ, 2-port PIC.