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.
Products made or sold by Juniper Networks or components thereof might be covered by one or more of the following patents that are
owned by or licensed to Juniper Networks: U.S. Patent Nos. 5,473,599, 5,905,725, 5,909,440, 6,192,051, 6,333,650, 6,359,479, 6,406,312,
6,429,706, 6,459,579, 6,493,347, 6,538,518, 6,538,899, 6,552,918, 6,567,902, 6,578,186, and 6,590,785.
Writing: Elizabeth Gardner, Jerry Isaac, Sheila Nolte
Editing: Fran Mues
Illustration: Faith Bradford Brown
Cover Design: Edmonds Design
Revision History
October 2010—Updated AC power cords. Minor corrections.
August 2010— Corporate rebranding.
May 2010— Corrected the number of power supplies in the base system.
September 2009— Added related topics.
18 April 2008— 530-021109-01 Revision 2. Revised sections into modular topics for easier customer access.
29 June 2007— 530-021109-01 Revision 1. Added Enhanced III FPCs. Updated the DC input voltage operating range.
30 March 2007— 530-017396-01 Revision 2. Added RJ-48 pinouts for the Control Board external clock inputs. Corrected the AC power
plugs. Updated the mounting hardware procedures. Updated the rack and clearance requirements.
20 October 2006— 530-017396-01 Revision 1. Combined power supply and power system electrical specifications. Added European
Community EMC Declaration of Conformity.
28 June 2006—530-015181-01 Revision 4. Updated torque specification range for tightening nuts to the DC power supply terminal studs.
30 May 2006—530-015181-01 Revision 3. Added power cable warning in Japanese. Added lithium battery statement.
13 April 2006—530-015181-01 Revision 2. Deleted cautions that stated the power supplies must remain in the chassis for proper airflow.
Added torque specification range for tightening nuts to the DC power supply terminal studs. Updated Junos OS Release recommendation
for graceful switchover.
9 January 2006—530-015181-01 Revision 1. Added Enhanced II FPCs.
26 September 2005—530-014169-01 Revision 1. Added multi-option configurations.
1 March 2005—530-011923-01 Revision 3. Updated DC power illustration and revised replacement procedure.
19 November 2004—530-011923-01 Revision 2. Revised fuse replacement procedure.
19 August 2004—530-011923-01 Revision 1. Updated “AC Plug Types” figure and made general updates.
9 January 2004—530-010086-01 Revision 2. Corrected cabinet clearance requirements.
5 January 2004—530-010086-01 Revision 1.
The information in this document is current as of the date listed in the revision history.
YEAR 2000 NOTICE
Juniper Networks hardware and software products are Year 2000 compliant. The 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.
READ THIS END USER LICENSE AGREEMENT (“AGREEMENT”) BEFORE DOWNLOADING, INSTALLING, OR USING THE SOFTWARE.
BY DOWNLOADING, INSTALLING, OR USING THE SOFTWARE OR OTHERWISE EXPRESSING YOUR AGREEMENT TO THE TERMS
CONTAINED HEREIN, YOU (AS CUSTOMER OR IF YOU ARE NOT THE CUSTOMER, AS A REPRESENTATIVE/AGENT AUTHORIZED TO
BIND THE CUSTOMER) CONSENTTO BEBOUND BY THISAGREEMENT. IF YOUDO NOTOR CANNOT AGREE TO THE TERMS CONTAINED
HEREIN, THEN (A) DO NOT DOWNLOAD, INSTALL, OR USE THE SOFTWARE, AND (B) YOU MAY CONTACT JUNIPER NETWORKS
REGARDING LICENSE TERMS.
1. The Parties. The parties to this Agreement are (i) Juniper Networks, Inc. (if the Customer’s principal office is located in the Americas) or
Juniper Networks (Cayman) Limited(if the Customer’s principal office islocated outside the Americas) (suchapplicable entitybeing referred
to herein as “Juniper”), and (ii) the person or organization thatoriginally purchased fromJuniper oran authorizedJuniper reseller the applicable
license(s) for use of the Software (“Customer”) (collectively, the “Parties”).
2. The Software. In this Agreement, “Software” means the program modules and features of the Juniper or Juniper-supplied software, for
which Customer has paid the applicable license or support fees to Juniper or an authorized Juniper reseller, or which was embedded by
Juniper in equipment which Customer purchased fromJuniper or an authorized Juniper reseller. “Software” also includes updates, upgrades
and new releases of such software. “Embedded Software” means Software which Juniper has embedded in or loaded onto the Juniper
equipment and any updates, upgrades, additions or replacements which are subsequently embedded in or loaded onto the equipment.
3. License Grant. Subject to payment ofthe applicablefees andthe limitationsand restrictions set forth herein, Juniper grants to Customer
a non-exclusive and non-transferable license, without right to sublicense, to use the Software, in executable form only, subject to the
following use restrictions:
a. Customer shall use Embedded Software solely as embedded in, and for execution on, Juniper equipment originally purchased by
Customer from Juniper or an authorized Juniper reseller.
b. Customer shall use the Software on a single hardware chassis having a single processing unit, or as many chassis or processing units
for which Customer has paid the applicable license fees; provided, however, with respect to the Steel-Belted Radius or Odyssey Access
Client software only, Customer shall use such Software on a single computer containing a single physical random access memory space
and containing any number of processors. Use of the Steel-Belted Radius or IMS AAA software on multiple computers or virtual machines
(e.g., Solaris zones) requires multiple licenses, regardless of whether such computers or virtualizations are physically contained on a single
chassis.
c. Product purchase documents, paper or electronic user documentation, and/or the particular licenses purchased by Customer may
specify limitsto Customer’s use of the Software. Such limitsmay restrict use to a maximumnumber of seats,registered endpoints, concurrent
users, sessions, calls, connections, subscribers, clusters, nodes, realms, devices, links, ports or transactions, or require the purchase of
separate licenses to use particular features, functionalities, services, applications, operations, or capabilities, or provide throughput,
performance, configuration, bandwidth, interface, processing, temporal, or geographical limits. In addition, such limits may restrict the use
of the Software to managing certain kinds of networks or require the Software to be used only in conjunction with other specific Software.
Customer’s use of the Software shall be subject to all such limitations and purchase of all applicable licenses.
d. For any trial copy of the Software, Customer’s right to use the Software expires 30 days after download, installation or use of the
Software. Customer may operate the Software after the 30-day trial period only if Customer pays for a license to do so. Customer may not
extend or create an additional trial period by re-installing the Software after the 30-day trial period.
e. The Global Enterprise Edition of the Steel-Belted Radius software may be used by Customer only to manage access to Customer’s
enterprise network. Specifically, service provider customers are expressly prohibited from using the Global Enterprise Edition of the
Steel-Belted Radius software to support any commercial network access services.
The foregoing license is not transferable or assignable by Customer. No license is granted herein to any user who did not originally purchase
the applicable license(s) for the Software from Juniper or an authorized Juniper reseller.
4. Use Prohibitions. Notwithstanding the foregoing, the license provided herein does not permit the Customer to, and Customer agrees
not to and shall not: (a) modify, unbundle, reverse engineer, or create derivative works based on the Software; (b) make unauthorized
copies of the Software (except as necessary for backup purposes); (c) rent, sell, transfer, or grant any rights in and to any copy of the
Software,in any form, to any third party;(d) remove any proprietary notices, labels, or markson or in any copy ofthe Softwareor any product
in which the Software is embedded; (e) distribute any copy of the Software to any third party, including as may be embedded in Juniper
equipment sold in the secondhandmarket; (f) use any‘locked’ or key-restricted feature, function, service,application, operation,or capability
without first purchasing the applicable license(s) and obtaining a valid key from Juniper, even if such feature, function, service, application,
operation, or capability is enabled without a key; (g) distribute any key for the Software provided by Juniper to any third party; (h) use the
Software in any manner that extends or is broader than the uses purchased by Customer from Juniper or an authorized Juniper reseller; (i)
use Embedded Software on non-Juniper equipment; (j) use Embedded Software (or make it available for use) on Juniper equipment that
the Customer did not originally purchase from Juniper or an authorized Juniper reseller; (k) disclose the results of testing or benchmarking
of the Software to any third party without the prior written consent of Juniper; or (l) use the Software in any manner other than as expressly
provided herein.
5. Audit. Customer shall maintain accurate records as necessary to verify compliance with this Agreement. Upon request by Juniper,
Customer shall furnish such records to Juniper and certify its compliance with this Agreement.
6. Confidentiality. The Parties agree that aspects of the Software and associated documentation are the confidential property of Juniper.
As such, Customer shall exercise all reasonable commercial efforts to maintain the Software and associated documentation in confidence,
which at a minimum includes restricting access to the Software to Customeremployees and contractors having a need to use the Software
for Customer’s internal business purposes.
7. Ownership. Juniper and Juniper’s licensors, respectively, retain ownership of all right, title, and interest (including copyright) in and to
the Software, associated documentation, and all copies of the Software. Nothing in this Agreement constitutes a transfer or conveyance
of any right, title, or interest in the Software or associated documentation, or a sale of the Software, associated documentation, or copies
of the Software.
8. Warranty, Limitation of Liability, Disclaimer of Warranty. The warranty applicable to the Software shall be as set forth in the warranty
statementthat accompanies theSoftware(the “Warranty Statement”). Nothingin this Agreementshall give riseto any obligation tosupport
the Software. Support services may be purchased separately. Any such support shall be governed by a separate, written support services
agreement. TO THE MAXIMUM EXTENT PERMITTED BY LAW, JUNIPER SHALL NOT BE LIABLE FOR ANY LOST PROFITS, LOSS OF DATA,
OR COSTSOR PROCUREMENTOF SUBSTITUTE GOODSOR SERVICES,OR FORANY SPECIAL, INDIRECT,OR CONSEQUENTIALDAMAGES
ARISING OUTOF THIS AGREEMENT,THE SOFTWARE, ORANY JUNIPEROR JUNIPER-SUPPLIED SOFTWARE. INNO EVENT SHALLJUNIPER
BE LIABLE FOR DAMAGES ARISING FROM UNAUTHORIZED OR IMPROPER USE OF ANY JUNIPER OR JUNIPER-SUPPLIED SOFTWARE.
EXCEPT AS EXPRESSLY PROVIDED IN THE WARRANTY STATEMENT TO THE EXTENT PERMITTED BY LAW, JUNIPER DISCLAIMS ANY
AND ALL WARRANTIES IN AND TO THE SOFTWARE (WHETHER EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE), INCLUDING ANY
IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT DOES
JUNIPER WARRANT THAT THE SOFTWARE, OR ANY EQUIPMENT OR NETWORK RUNNING THE SOFTWARE, WILL OPERATE WITHOUT
ERROR OR INTERRUPTION, OR WILL BE FREE OF VULNERABILITY TO INTRUSION OR ATTACK. In no event shall Juniper’s or its suppliers’
or licensors’ liability to Customer, whether in contract, tort (including negligence), breach of warranty, or otherwise, exceed the price paid
by Customer for the Software that gave rise to the claim, or if the Software is embedded in another Juniper product, the price paid by
Customer for such other product. Customer acknowledges and agrees that Juniper has set its prices and entered into this Agreement in
reliance upon the disclaimers of warranty and the limitations of liability set forth herein, that the same reflect an allocation of risk between
the Parties (including the risk that a contract remedy may fail of its essential purpose and cause consequential loss), and that the same
form an essential basis of the bargain between the Parties.
9. Termination. Any breach of this Agreement or failure by Customer to pay any applicable fees due shall result in automatic termination
of the license granted herein. Upon such termination, Customer shall destroy or return to Juniper all copies of the Software and related
documentation in Customer’s possession or control.
10. Taxes. All license fees payable under this agreement are exclusive of tax. Customer shall be responsible for paying Taxes arising from
the purchase of the license, or importation or use of the Software. If applicable, valid exemption documentation for each taxing jurisdiction
shall be provided to Juniper prior to invoicing, and Customer shall promptly notify Juniper if their exemption is revoked or modified. All
payments made by Customer shall be net of any applicable withholding tax. Customer will provide reasonable assistance to Juniper in
connection with such withholding taxes by promptly: providing Juniper with valid tax receipts and other required documentation showing
Customer’s payment of any withholding taxes; completing appropriate applications that would reduce the amount of withholding tax to
be paid; and notifying and assisting Juniper in any audit or tax proceeding related to transactions hereunder. Customer shall comply with
all applicable tax laws and regulations, and Customer will promptly pay or reimburse Juniper for all costs and damages related to any
liability incurred by Juniper as a result of Customer’s non-compliance or delay with its responsibilities herein. Customer’s obligations under
this Section shall survive termination or expiration of this Agreement.
11. Export. Customer agrees to comply with all applicable export laws and restrictions and regulations of any United States and any
applicable foreign agency or authority, and not to export or re-export the Software or any direct product thereof in violation of any such
restrictions, laws or regulations, or without all necessary approvals. Customer shall be liable for any such violations. The version of the
Software supplied to Customer may contain encryption or other capabilities restricting Customer’s ability to export the Software without
an export license.
12. Commercial Computer Software. The Software is “commercial computer software” and is provided with restricted rights. Use,
duplication, or disclosure by the United States government is subject to restrictions set forth in this Agreement and as provided in DFARS
227.7201 through 227.7202-4, FAR 12.212, FAR 27.405(b)(2), FAR 52.227-19, or FAR 52.227-14(ALT III) as applicable.
13. Interface Information. To the extent required by applicable law, and at Customer's written request, Juniper shall provide Customer
with the interface information needed to achieve interoperability between the Software and another independently created program, on
payment of applicable fee, if any. Customer shall observe strict obligations of confidentiality with respect to such information and shall use
such information in compliance with any applicable terms and conditions upon which Juniper makes such information available.
14. Third Party Software. Any licensor of Juniper whose software is embedded inthe Software and any supplier of Juniper whose products
or technology are embedded in (or services are accessed by) the Software shall be a third party beneficiary with respect to this Agreement,
and such licensor or vendor shall have the right toenforce this Agreement in its own name as if it were Juniper. In addition, certain third party
software may be provided with the Software and is subject to the accompanying license(s), if any, of its respective owner(s). To the extent
portions of the Software are distributed under and subject to open source licenses obligating Juniper to make the source code for such
portions publicly available (such as the GNU General Public License (“GPL”) or the GNU Library General Public License (“LGPL”)), Juniper
will make such source code portions (including Juniper modifications, as appropriate) available upon request for a period of up to three
years from the date of distribution. Such request can be made in writing to Juniper Networks, Inc., 1194 N. Mathilda Ave., Sunnyvale, CA
94089, ATTN: General Counsel. You may obtain a copy of the GPL at http://www.gnu.org/licenses/gpl.html, and a copy of the LGPL
at http://www.gnu.org/licenses/lgpl.html .
15. Miscellaneous. This Agreement shall be governed by the laws of the State of California without reference to its conflicts of laws
principles. The provisions of the U.N. Convention for the International Sale of Goods shall not apply to this Agreement. For any disputes
arising under this Agreement, the Parties hereby consent to the personal and exclusive jurisdiction of, and venue in, the state and federal
courts within Santa Clara County, California. This Agreement constitutes the entire and sole agreement between Juniper and the Customer
with respect to the Software, and supersedes all prior and contemporaneous agreements relating to the Software, whether oral or written
(including any inconsistent terms contained in a purchase order), except that the terms of a separate written agreement executed by an
authorized Juniper representative and Customer shall govern to the extent such terms are inconsistent or conflict with terms contained
herein. No modification to this Agreement nor any waiver of any rights hereunder shall be effective unless expressly assented to in writing
by the party to be charged. If any portion of this Agreement is held invalid, the Parties agree that such invalidity shall not affect the validity
of the remainder of this Agreement. This Agreement and associated documentation has been written in the English language, and the
Parties agree that the English version will govern. (For Canada: Les parties aux présentés confirment leur volonté que cette convention de
même que tous les documents y compris tout avis qui s'y rattaché, soient redigés en langue anglaise. (Translation: The parties confirm that
this Agreement and all related documentation is and will be in the English language)).
Junos OS Documentation and Release Notes on page xxi
•
Objectives on page xxi
•
Audience on page xxii
•
Documentation Conventions on page xxii
•
Documentation Feedback on page xxiii
•
Requesting Technical Support on page xxiv
Junos OS Documentation and Release Notes
For a list of related Junos OS documentation, see
http://www.juniper.net/techpubs/software/junos/ .
If the information in the latest release notes differs from the information in the
documentation, follow the Junos OS Release Notes.
To obtain the most current version of all Juniper Networks®technical documentation,
see the product documentation page on the Juniper Networks website at
http://www.juniper.net/techpubs/.
Objectives
This documentation describes hardware components, installation, basic configuration,
and basic troubleshooting procedures for the Juniper Networks M320 router. It explains
how to prepare your site for router installation, unpack and install the hardware, power
on the router, perform initial software configuration, and perform routine maintenance.
After completing the installation and basic configuration procedures covered in this
documentation, see the Junos OS configuration guides for information about further
Junos OS configuration.
NOTE: For additional information about Juniper Networks routers and the
Physical Interface Cards (PICs) they support—either corrections to or
informationthat mighthave been omitted from this guide—see the hardware
release notes at http://www.juniper.net/.
This documentation is designed for network administrators who are installing and
maintaining a Juniper Networks router or preparing a site for router installation. To use
the documentation, you need a broad understanding of networks in general, the Internet
in particular, networking principles, and network configuration. Any detailed discussion
of these concepts is beyond the scope of this hardware documentation.
Documentation Conventions
Table 1 on page xxii defines the notice icons used in this guide.
Table 1: Notice Icons
DescriptionMeaningIcon
Indicates important features or instructions.Informational note
Table 2 on page xxii defines the text and syntax conventions used in this guide.
Table 2: Text and Syntax Conventions
Represents text that you type.Bold text like this
Fixed-width text like this
Italic text like this
Represents output that appears on the
terminal screen.
•
Introduces important new terms.
•
Identifies book names.
•
Identifies RFC and Internet draft titles.
Indicates a situation that might result in loss of data or hardware damage.Caution
Alerts you to the risk of personal injury or death.Warning
Alerts you to the risk of personal injury from a laser.Laser warning
ExamplesDescriptionConvention
To enter configuration mode, type the
configure command:
user@host> configure
user@host> show chassis alarms
No alarms currently active
•
A policy term is a named structure
that defines match conditions and
actions.
Represents variables (options for which
you substitute a value) in commands or
configuration statements.
Represents names of configuration
statements, commands, files, and
directories; IP addresses; configuration
hierarchy levels; or labels on routing
platform components.
Indicates a choice betweenthe mutually
exclusivekeywords or variables on either
side of the symbol. The set of choices is
often enclosed in parentheses for clarity.
same lineas theconfiguration statement
to which it applies.
Enclose a variable for which you can
substitute one or more values.
Identify a level in the configuration
hierarchy.
Identifies a leaf statement at a
configuration hierarchy level.
Configure the machine’s domain name:
[edit]
root@# set system domain-name
domain-name
•
To configure a stub area, include the
stub statement at the [edit protocols
ospf area area-id] hierarchy level.
•
The console portis labeled CONSOLE.
stub <default-metric metric>;Enclose optional keywords or variables.< > (angle brackets)
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;
}
}
}
J-Web GUI Conventions
Bold text like this
> (bold right angle bracket)
Documentation Feedback
We encourage you to provide feedback, comments, and suggestions so that we can
improve the documentation. You can send your comments to
techpubs-comments@juniper.net, or fill out the documentation feedback form at
Represents J-Web graphical user
interface (GUI) items you click or select.
Separates levels in a hierarchy of J-Web
selections.
•
In the Logical Interfaces box, select
All Interfaces.
•
To cancel the configuration, click
Cancel.
In the configuration editor hierarchy,
select Protocols>Ospf.
https://www.juniper.net/cgi-bin/docbugreport/. If you are using e-mail, be sure to include
the following information with your comments:
•
Document or topic name
•
URL or page number
•
Software release version (if applicable)
Requesting Technical Support
Technical product support is available throughthe 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:
https://www.juniper.net/alerts/
•
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 serviceentitlement by productserial number, useour Serial NumberEntitlement
(SNE) Tool: https://tools.juniper.net/SerialNumberEntitlementSearch/
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 the forwarding subsystem. Forwarding and 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 can be deployed in core, peering,and datacenter applications, butis 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.
Related
Documentation
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
routersupports 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.
M320 Flexible PIC Concentrator (FPC) Description on page 11
•
M320 FPCs Supported on page 14
•
M320 PIC Description on page 15
•
M320 Switch Interface Board (SIB) Overview on page 16
•
M320 Host Subsystem Overview on page 18
•
M320 Connector Interface Panel (CIP) Overview on page 25
•
M320 Craft Interface Overview on page 27
•
M320 Power System Overview on page 33
•
M320 Cooling System Description on page 37
•
M320 Cable Management System Description on page 38
M320 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:
•
Switch Interface Boards (SIBs)—A fully configured router has four SIBs. Each FPC has
a dedicated ASICwith four high-speed links that connect to the 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 RoutingEngine functioningtogether
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.
For information about the effect of taking the host subsystem offline, see “Taking the
M320 HostSubsystemOffline” onpage 160.For moreinformation about high availability
features, see the Junos OS High Availability Configuration Guide.
•
Powersupplies—A router with a minimum of three AC power supplies or four DC 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—Thecooling system has redundant components, which are controlled
by the host subsystem. If one of the fans fails, the host subsystem increases the speed
of the remaining fans to provide sufficient cooling for the router indefinitely.
Related
Documentation
M320 SIB Description on page 16•
• M320 Host Subsystem Description on page 18
• M320 Cooling System Description on page 37
• M320 Power System Description on page 33
M320 Chassis Description
The router chassis is a rigid sheet metal structure that houses all the other router
components (see Figure 1 on page 7). 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 rear of the chassis). The chassis canbe installed in many types of racks or cabinets.
For more information, see Requirements Reference Example: M320 Cabinet Size and
Clearance Requirements and “Rack Requirements for the M320 Router” on page 42
The chassis includes the following features (see Figure 1 on page 7, Figure 2 on page 8,
and Figure 3 on page 9):
•
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.
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 273.
Related
Documentation
M320 Router Description on page 3•
• Installing the M320 Router Using a Mechanical Lift on page 63
• Installing the M320 Chassis in the Rack Manually on page 79
• M320 Chassis Lifting Guidelines on page 216
• M320 Router Physical Specifications on page 245
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 10). 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 thesignal pathto the FPCs, SIBs, Routing Engines,
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
Using the CLI” on page 273.
• M320 Cabinet Size and Clearance Requirements on page 46
M320 Flexible PIC Concentrator (FPC) Description
Up to eight Flexible PIC Concentrators (FPCs) install vertically in the front of the router
(see Figure 5 on page 12). 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 14 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 includes a288-MHz CPU,system controller, 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 32.
•
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 FRU Description” on
page 137. When you install an FPC into a functioning router, theRouting Enginedownloads
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 175.
Table 3: FPCs Supported by the M320 Router (continued)
Chapter 2: M320 Hardware Components
Related
Documentation
• Replacing an M320 FPC on page 175
• Troubleshooting the M320 FPCs on page 131
M320 PIC Description
PICs provide the physical connection to various network media types, receiving incoming
packets from the network and transmitting outgoing packets to the network. During this
process, each PIC performs framing and line-speed signaling for its media type. Before
transmitting outgoing data packets, the PICs encapsulate the packets received from the
FPCs. Each PIC is equipped with an ASIC that performs control functions specific to the
media type of that PIC.
Maximum
FPC Model NumberFPC NameFPC Type
Number of PICs
Throughputper FPC
(Full-Duplex)
First Junos OS
Release
Supported
Maximum
7.516 Gbps4M320–FPC2–E2Enhanced II FPC22
8.416 Gbps4M320–FPC2–E3Enhanced III FPC22
6.220 Gbps2M320–FPC3FPC33
7.520 Gbps2M320–FPC3–E2Enhanced II FPC33
8.420 Gbps2M320–FPC3–E3Enhanced III FPC33
Maintaining M320 FPCs on page 113•
Related
Documentation
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,including ATM, Channelized, GigabitEthernet, IPServices,
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.
M320 PICs Supported•
• M320 End-of-Life PICs Supported
• Maintaining M320 PICs and PIC Cables on page 119
M320 Performance for Different SIB Configurations on page 17
M320 SIB Description
The Switch Interface Boards (SIBs) provide the switching function to the destination
FPC. The SIBs (see Figure 9 on page 16) create the switch fabric for the router, providing
up to a total of 385 million packets per second (Mpps) of forwarding with the maximum
configuration.
SIBs are located at the center rear of the router chassis in the slots labeled SIB0 through
SIB3 (top to bottom). The M320 router can be configured with two, three, or four SIBs.
You can upgrade from two to three SIBs or from three to four SIBs without resetting or
stopping Packet Forwarding Engines.
Each FPC has a dedicated ASIC with up to four high-speed links that connect to the SIBs
(one link per SIB).
SIBs are hot-insertable and hot-removable.
Figure 9: SIB-M
Each SIB consists of the following components:
•
Switch Fabric ASICs.
•
High-speed links (HSLs) to each FPC.
•
Three LEDs located on the SIB faceplate that display the status of the SIB. Table 4 on
page 16 describes the functions of the SIB LEDs. If all three LEDs are off, the SIB is not
receiving power. The OK and FAIL LEDs are replicated on the craft interface.
•
SIB online/offline button, located on the SIB faceplate.
Table 5 on page 17 describes expected performance per total active SIBs for different
FPC and PIC configurations. The packet forwarding rate of each FPC is independent of
the number and configuration of other FPCs in the chassis. The packet forwarding rate
depends on the total number of PICs in the FPC, the number of activeSIBs in the chassis,
and packet size.
Table 5: Performance per SIB/FPC Configuration
Number of Active
SIBs
are 4-port GE PICs)
PerformanceFPC Type and Number of PICs per FPC
Line rateFPC1 with up to four PICs1
Line rateFPC2 withup to two PICs(except whenboth PICs
Line rate not guaranteedFPC2 with two 4-port GE PICs
Line rate not guaranteedFPC2 with three or four PICs
are 4-port GE PICs)
Line rate not guaranteedFPC3 with one or two PICs
Line rateFPC1 with up to four PICs2
Line rateFPC2 with up to four PICs (except when all PICS
Line rate not guaranteedFPC2 with four 4-port GE PICs
Table 5: Performance per SIB/FPC Configuration (continued)
Number of Active
SIBs
PerformanceFPC Type and Number of PICs per FPC
Line rateFPC1 with up to four PICs3
Line rateFPC2 with up to four PICs
Line rate not guaranteedFPC3 with two PICs
Line rateFPC1 with up to four PICs4
Line rateFPC2 with up to four PICs
Line rateFPC3 with up to two PICs
Related
Documentation
Replacing an M320 SIB on page 172•
• Maintaining the M320 SIBs on page 121
M320 Host Subsystem Overview
•
M320 Host Subsystem Description on page 18
•
M320 Routing Engine Description on page 19
•
M320 Routing Engine 600 on page 20
•
M320 Routing Engine 1600 on page 21
•
M320 Routing Engine 2000 on page 22
•
M320 Control Board (CB) Description on page 23
•
M320 Control Board (CB) LEDs on page 25
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: Eachhost subsystemhas 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
Interface Host Subsystem LEDs” on page 30.
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 111•
• Replacing M320 Host Subsystem Components on page 160
• Taking the M320 Host Subsystem Offline on page 160
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 ofthe chassisin the slots labeled RE0 and RE1. Each RoutingEngine 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 Engine fails 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 isreplicatedon thebackup Routing Engine. 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 Configuration Guide.
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:
•
RE-600-2048
•
RE-1600-2048
•
RE-A-2000-4096
•
RE-A-1800x2
Related
Documentation
M320 Routing Engine Ports on page 26•
• Replacing an M320 Routing Engine on page 166
• M320 Routing Engine 600 on page 20
• M320 Routing Engine 1600 on page 21
• M320 Routing Engine 2000 on page 22
M320 Routing Engine 600
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 primarystoragefor software 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 activityfor theinternal IDE interface. It does not necessarilyindicate
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: Ifthe routerboots from analternateboot device,a yellowalarm lights
the LED on the router’s craft interface.
Related
Documentation
M320 Routing Engine Ports on page 26•
• M320 Routing Engine Description on page 19
• Replacing an M320 Routing Engine on page 166
M320 Routing Engine 1600
Figure 10: Routing Engine 1600
Each Routing Engine (shown in Figure 10 on page 21) 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 primarystoragefor software 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 activityfor theinternal IDE interface. It does not necessarilyindicate
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-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: Ifthe routerboots from analternateboot device,a yellowalarm lights
the LED on the router’s craft interface.
Related
Documentation
M320 Routing Engine Ports on page 26•
• M320 Routing Engine Description on page 19
• Replacing an M320 Routing Engine on page 166
M320 Routing Engine 2000
Figure 11: Routing Engine 2000
Each Routing Engine (shown in Figure 11 on page22 consistsof 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 primarystoragefor software 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 activityfor theinternal IDE interface. It does not necessarilyindicate
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: Ifthe routerboots from analternateboot device,a yellowalarm lights
the LED on the router’s craft interface.
Related
Documentation
M320 Routing Engine Ports on page 26•
• M320 Routing Engine Description on page 19
• Replacing an M320 Routing Engine on page 166
M320 Control Board (CB) Description
Each CB works with an adjacent Routing Engine to provide control and monitoring
functions for the router (see Figure 12 on page 24). These functions include determining
Routing Engine mastership,controlling power and reset 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). If two 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.
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
PCI bus—Provides the interface to the Routing Engine.
•
1000Base-T Ethernet controller—Provides a 1-Gbps link between the Routing Engine
and the on-board Fast Ethernet switch.
•
Fast Ethernet switch—Provides a 100-Mbps Ethernet link to each FPC for Routing
Engine data transfers.
•
Three LEDs, located on the CB faceplate, indicate the status of the CB. “M320 Control
Board (CB) LEDs” on page 25 describes the functions of the CB LEDs.
•
CB online/offline button, located on the CB faceplate.
NOTE: When the adjacent Routing Engine is online, the online/offline
button on the CB faceplate is nonfunctional. For more information, see
“Taking the M320 Host Subsystem Offline” on page 160.
•
Circuits that control fans and other hardware components in the chassis.
•
Internally-generated 19.44-MHz Stratum 3 reference clock for line timing.
•
Two RJ-48 connectors for external clock inputs for 19.44-MHz Stratum 3 reference
clocks.
Control board is functioning as the master.On steadilyBlueMASTER
Control board has failed.On steadilyYellowFAIL
Control board is online and is functioning normally.On steadilyGreenOK
Control board is powering up, but not online.Blinking
Related
Documentation
M320 Chassis Description on page 6•
• M320 Control Board (CB) Description on page 23
• Replacing an M320 CB on page 163
M320 Connector Interface Panel (CIP) Overview
•
M320 Connector Interface Panel (CIP) Description on page 25
•
M320 Routing Engine Ports on page 26
•
T640 Alarm Relay Contacts on page 27
M320 Connector Interface Panel (CIP) Description
The Connector Interface Panel (CIP) consists of Ethernet, console, and auxiliary
connectors for the Routing Engines and alarm relay contacts (see Figure 13 on page 26).
The front electrostatic discharge point is located near the bottom of the CIP. The CIP is
located at the left side of the FPC card cage.
The CIP has two sets of ports that you use to connect the Routing Engines to external
management devices. Fromthese management devices, youcan usethe CLIto configure
the router.
The upper set of ports, labeled HOST 0, connects to the Routing Engine in slot RE0; and
the lower set,labeled HOST 1, connects to the Routing Engine in 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.
Related
Documentation
M320 Alarm Relay Contacts•
• M320 Connector Interface Panel (CIP) Description on page 25
• Replacing the M320 CIP on page 140
• M320 RJ-48Connector Pinouts for the ControlBoard External ClockInputs onpage 269
T640 Alarm Relay Contacts
The CIPhas two alarm relay contactsfor connectingthe router to externalalarm devices.
Whenever a system condition triggers eitherthe redor yellow alarm on 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
T640 Connector Interface Panel (CIP) Description•
• Replacing the T640 Alarm Relay Wires
• T640 Routing Engine Interface Cable and Wire Specifications
• T640 Routing Engine Ports
M320 Craft Interface Overview
•
M320 Craft Interface Description on page 28
•
M320 Craft Interface Alarm LEDs and ACO/LT Button on page 28
•
M320 Craft Interface LED Display and Navigation Buttons on page 29
•
M320 Craft Interface Host Subsystem LEDs on page 30
M320 Craft Interface FPC LEDs and Online/Offline Buttons on page 32
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 on the front of the router above the FPCs. Figure 14 on
page 28 shows the front panel of the M320 craft interface.
Figure 14: Front Panel of the Craft Interface
Related
Documentation
• M320 Craft Interface Alarm LEDs and ACO/LT Button on page 28
• M320 Craft Interface Host Subsystem LEDs on page 30
• Replacing an M320 Craft Interface on page 158
M320 Craft Interface Alarm LEDs and ACO/LT 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 connector interface panel (CIP). The LED display 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 left of the alarm LEDs. Deactivating an alarm
turns off both LEDs and deactivates the device attached to the corresponding alarm
relaycontact on the CIP. However, the LED displaycontinues to report the alarmmessage
until you clear the condition that caused the alarm.
Table 7 on page 29 describes the alarm LEDs and alarm cutoff button in more detail.
Table 7: Alarm LEDs and Alarm Cutoff/Lamp Test Button
DescriptionStateColorShape
Critical alarm LED—Indicates a critical condition that
can cause the router to stop functioning. Possible
causes include component removal, failure, or
overheating.
Warningalarm LED—Indicates aserious but nonfatal
error condition, such as a maintenance alert or a
significant increase in component temperature.
Alarm cutoff/lamp test button—Deactivatesred and
yellowalarms. Causesall LEDs on the craft interface
to light (for testing purposes), when pressed and
held.
Related
Documentation
On steadilyRed
On steadilyYellow
——
M320 Craft Interface Description on page 28•
• M320 Alarm Relay Contacts
• M320 Craft Interface LED Display and Navigation Buttons on page 29
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:
•
LED display idle mode
•
LED display alarm mode
During normaloperation, the LED display operates in idle modeand reports current status
information, as shown in Figure 15 on page 29.
Figure 15: 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:
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 the set chassis display message command. For more information, see the Junos OSSystem Basics and Services Command Reference.
When a red or yellow alarm occurs, the LED display switches to alarm mode and reports
about the alarm condition, as shown in Figure 16 on page 30.
Figure 16: 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 on each line indicates whether the alarm is a red (R) or yellow (Y)
alarm.
For a list of alarm messages that can appear on the LED display, see “M320 Chassis and
Interface Alarm Messages” on page 127.
Related
Documentation
M320 Craft Interface Description on page 28•
• M320 Craft Interface Alarm LEDs and ACO/LT Button on page 28
• M320 Alarm Relay Contacts
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 8 on page 30 describes the functions of the host
subsystem LEDs.
Table 8: M320 Host Subsystem LEDs
DescriptionStateColorLabel
Host is offline.On steadilyRedFAIL
Host is online and is functioning normally.On steadilyGreenOK
Host is functioning as the master.On steadilyGreenMASTER
Related
Documentation
M320 Host Subsystem Description on page 18•
• M320 Craft Interface Description on page 28
• M320 Craft Interface Alarm LEDs and ACO/LT Button on page 28
• M320 Alarm Relay Contacts
M320 Craft Interface SIB LEDs
Each SIBhas two LEDs on the craft interface that indicate its status. TheSIB LEDs, labeled
SIB0 through SIB3, are located in the middle of the craft interface under the SIBS label.
The ACTIVE LED is not replicated on the craft interface. Table 9 on page 31 describes
the functions of the SIB LEDs.
Table 9: SIB LEDs on the Craft Interface
Related
Documentation
M320 SIB Description on page 16•
• M320 Craft Interface Description on page 28
DescriptionStateColorLabel
SIB has failed.On steadilyRedFAIL
SIB is functioning normally.On steadilyGreenOK
• M320 Alarm Relay Contacts
• Maintaining the M320 SIBs on page 121
M320 Craft Interface Power Supply LEDs
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 10 on page 31 describes the functions of the power supply LEDs.
Table 10: Power Supply LEDs on the Craft Interface
DescriptionStateColorLabel
Power supply has failed.On steadilyRedFAIL
Power supply is functioning normally.On steadilyGreenOK
M320 Flexible PIC Concentrator (FPC) Description on page 11•
• M320 Craft Interface Description on page 28
• M320 Alarm Relay Contacts
• Troubleshooting the M320 FPCs on page 131
M320 Power System Overview
•
M320 Power System Description on page 33
•
M320 AC Power Supply on page 33
•
M320 DC Power Supply on page 34
•
M320 Power Supply LEDs on page 35
•
M320 Fuses on page 36
•
M320 Fuse Specifications on page 36
M320 Power System Description
The M320 router uses either AC or DC power supplies. The router is configurable with
two,three, orfour AC powersupplies or two orfour DCpower supplies.The power supplies
connect to the midplane, which distributes the different output voltages produced by
the power supplies to the router components, depending on their voltage requirements.
All power supplies are hot-removable and hot-insertable. Each power supply is cooled
by its own internal cooling system.
Related
Documentation
• M320 Power Requirements on page 250
• Troubleshooting the M320 Power System on page 132
M320 AC Power Supply
In the AC power configuration, the router contains two to four load-sharing AC power
supplies (see Figure 17 on page 34), which are located at the lower rear of the chassis in
slots PEM0 through PEM3 (top to bottom). The router requires a minimum of two fully
functional power supplies to operate.
To provide power redundancy, you can upgrade the number of AC power supplies from
two to three or from three to four. Each AC power supply provides power to all
components in the router, as opposed to the DC power configuration (see “M320 DC
Power Supply” on page 34 for more information). Three AC power supplies provide full
CAUTION: Mixing AC and DC power supplies is not supported and prevents
power redundancy. If one power supply fails or is removed, the remaining power supplies
instantly assume the entire electrical load.
NOTE: In a router with two power supplies (no power supply redundancy),
if one power supply fails or is shut down, the other power supply goes into a
“check” state and does not operate even though it has not failed (this is
because the router requires two power supplies to operate).
For AC power supply and power system electrical specifications, see “M320 AC Power
Electrical Specifications” on page 252 and “M320 AC Power Cord Specifications” on
page 253.
Figure 17: AC Power Supply
Related
Documentation
• Grounding the M320 Router on page 95
• M320 AC Power Electrical Specifications on page 252
• M320 Power System Description on page 33
M320 DC Power Supply
In the DC power configuration, the router contains either two or four DC power supplies
(see Figure 18 on page 35), located at the lower rear of the chassis in slots PEM0 through
PEM3 (top to bottom). You can upgrade your DC power supply from two to four power
supplies. The DC power suppliesin slotsPEM0 and PEM2,when both are installed, provide
load-sharing and power to the FPCs in slots FPC3 through FPC7. The DC power supplies
in slots PEM1 and PEM3, when both are installed, provide load-sharing and power to the
FPCs in slots FPC0 through FPC2, SIBs, CBs, and Routing Engines. All DC power supplies
provide power to the fan trays.
When fully configured with four DC power supplies, the DC power supplies provide full
redundancy. The DC power supplies in slots PEM0 and PEM1 can provide full power to
the router. Likewise, the DC power supplies in slots PEM2 and PEM3 can also provide full
power. The DC power supply in PEM2 serves as the backup to the DC power supply in
slot PEM0, and the DC power supply in PEM3 serves as the backup to the DC power
supply in slot PEM1.
Connecting Power to an AC-Powered M320 Router on page 96•
Each DC power supply has a single DC input (-48 VDC and return) that requires a
dedicated60 A (–48 VDC) circuitbreaker. Forinformation about sitepower preparations,
see “Site Electrical Wiring Guidelines for M Series, MX Series, and T Series Routers” on
page 249. For information about connecting the router to power and ground, see
“Connecting Power to a DC-Powered M320 Router” on page 97.
For DC power supply and power system electrical specifications, see “M320 DC Power
Electrical Specifications” on page 255
Figure 18: DC Power Supply
Related
Documentation
M320 Power System Description on page 33•
• Grounding the M320 Router on page 95
• Maintaining the M320 Power Supplies on page 122
• Replacing an M320 DC Power Supply on page 196
M320 Power Supply LEDs
The OUTPUT OK LED on each power supply faceplate indicates the status of the power
supply (see Table 12 on page 35 , which applies to the AC and DC power supply). The
power supply status is also reflected in two LEDs on the craft interface (see “M320 Craft
Interface Power Supply LEDs” on page 31). In addition, a power supply failure triggers
the red alarm LED on the craft interface.
Table 12: Power Supply LED
Blinking
DescriptionStateColorLabel
No power applied to power supply.OffBlueOUTPUTOK
•
Power supply blinks for 5 seconds after initial power on.
•
Power supply is installed, but not powered on, and is receiving bias power from
a powered on power supply.
• Troubleshooting the M320 Power System on page 132
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 133. For fuse
replacement instructions, see “Replacing an M320 Fuse” on page 204.
Related
Documentation
M320 Fuse Specifications on page 36•
• Preventing Electrostatic Discharge Damage to an M320 Router on page 214
• Site Electrical WiringGuidelines forM Series,MX Series,and TSeries Routers onpage 249
• Site Electrical WiringGuidelines forM Series,MX Series,and TSeries Routers onpage 249
• Preventing Electrostatic Discharge Damage to an M320 Router on page 214
• Troubleshooting the M320 Fuses on page 133
M320 Cooling System Description
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 19 on page 38). All fan trays and filters are
hot-insertable and hot-removable. Thetwo frontfan 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 47•
• Maintaining the M320 Fan Trays on page 111
• Troubleshooting the M320 Cooling System on page 129
M320 Cable Management System Description
The cable management system (see Figure 20 on page 39) consists of a row of nine
semicircular plastic bobbins mounted on the front of therouter below the FPC card cage.
The PIC cables pass between the bobbins and into the tray, 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.
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.
Plan rack location, including required space
clearances.
If arack isused, secure rack to floorand building
structure.
Cables
Acquire cables and connectors:
•
Determine the number of cables needed
based on your planned configuration.
•
Review the maximum distance allowed for
each cable. Choosethe length of cable based
on the distance between the hardware
components being connected.
Plan the cable routing and management.
Related
Documentation
M320 Chassis Lifting Guidelines on page 216•
• General Safety Guidelines for M Series, MX Series, and T Series Routers on page 211
• Maintenance and Operational Safety Warnings for M Series, MX Series, and T Series
Routers on page 225
“M320 Clearance Requirements” on
page 44
“Rack Requirements for the M320
Router” on page 42
“Calculating Power Budget for
Fiber-Optic Cable for M Series, MX
Series, and T Series Routers” on
page 261
“Calculating Power Margin for
Fiber-Optic Cable for M Series, MX
Series, and T Series Routers” on
page 262
“Maintaining M320 PICs and PIC
Cables” on page 119
Rack Requirements for the M320 Router
The router can be installed in many types of racks, including four-post (telco) racks and
open-frame racks. An example of an open-frame rack is shown in Figure 21 on page 43.
For open-frame racks, center-mounting is preferable to front-mounting because the
more even distribution of weight provides greater stability.
The router is designed for installation ina 19-in. rack as defined in Cabinets, Racks, Panels,and Associated Equipment (document number EIA-310-D) published by the Electronics
Industry Association (http://www.eia.org).
With the use of adapters, the router can fit into a 600-mm-wide rack or cabinet, as
defined in the four-part Equipment Engineering (EE); European TelecommunicationsStandard for Equipment Practice (document numbers ETS 300 119-1 through 119-4)
published by the European Telecommunications Standards Institute(http://www.etsi.org).
Use approved wing devices to narrow the opening between the rails.
The rack rails must be spaced widely enough to accommodate the router chassis's
external dimensions: 34.80 in. (88.4 cm) high, 25.64 in. (65.1 cm) deep, and
17.43 in. (44.3 cm) wide, excluding the front and rear cable management systems. The
Chapter 3: Preparing the Site for M320 Router Installation
outer edges of the mounting brackets extend the width to 19 in. (48.3 cm). The spacing
of rails and adjacent racks must also allow for the clearances around the router and rack.
Two sets of holes are used in the mounting brackets and front-mount flanges to attach
the chassis to a rack. The holes within each set are spaced at 2 U (3.5 in. or 8.9 cm) and
3 U (5.25 in. or 13.3 cm). The router; can be mounted in any rack that provides holes
spaced at those distances.
The mounting holes for connecting the mounting brackets to the chassis are spaced
0.984 in. (25 mm) apart.
The chassis height of 34.80 in. (88.4 cm) is approximately 20 U. A U is the standard rack
unit defined in Cabinets, Racks, Panels, and Associated Equipment (document number
EIA-310-D) published by the Electronics Industry Association. You can stack two M320
routers in a rack that has at least 40 U (70 in. or 1.78 m) of usable vertical space.
The rack must be strong enough to support the weight of the fully configured router, up
to 439 lb (199.6 kg). If you stack two fully configured routers in one rack, it must be
capable of supporting about 878 lb (399.1 kg).
Two sets of holes are used in the mounting brackets and front-mount flanges to attach
the chassis to a rack. The holes within each set are spaced at 2 U (3.5 in. or 8.9 cm) and
3 U (5.25 in. or 13.3 cm). The router; can be mounted in any rack that provides holes
spaced at those distances.
Always secure the rack to the structure of the building. If your geographical area is subject
to earthquakes, bolt the rack to the floor. For maximum stability, also secure the rack to
ceiling brackets.
Related
Documentation
M320 Clearance Requirements on page 44•
• M320 Chassis Lifting Guidelines on page 216
M320 Clearance Requirements
When planning the installation site, you need to allow sufficient clearance around the
rack (see Figure 22 on page 44):
•
For the cooling system to function properly, the airflow around the chassis must be
unrestricted. “M320 Cooling System Description” on page 37 depicts the airflow in the
router.
•
For service personnel to remove and install hardware components, there must be
adequate space at the front and back of the router. We recommend that you allow at
least 30 in. (72.6 cm) in front of the rack and 24 in. (61.0 cm) behind the rack.
Figure 22: Chassis Dimensions and Clearance Requirements
The router has two adjustable center-mounting brackets that are initially attached to
the mounting holes closest to the rear ofthe chassis. Youcan movethe pair of adjustable
center-mounting brakcets to one of 11 positions on the side of the chassis. The mounting
holes for connecting the mounting brackets to the chassis are spaced 0.984 in. (25 mm)
apart.
Chapter 3: Preparing the Site for M320 Router Installation
For instructionsabout installingthe mountinghardware, see “Installing the M320 Mounting
Hardware for a Four-Post Rack or Cabinet” on page 56.
The chassis height of 34.80 in. (88.4 cm) is approximately 20 U. A U is the standard rack
unit defined in Cabinets, Racks, Panels, and Associated Equipment (document number
EIA-310-D) published by the Electronics Industry Association. You can stack two M320
routers in a rack that has at least 40 U (70 in. or 1.78 m) of usable vertical space.
The rack must be strong enough to support the weight of the fully configured router, up
to 439 lb (199.6 kg). If you stack two fully configured routers in one rack, it must be
capable of supporting about 878 lb (399.1 kg).
Figure 23: Typical Open-Frame Rack
Related
Documentation
M320 Site Preparation Checklist Requirements on page 41•
• M320 Chassis Lifting Guidelines on page 216
M320 Cabinet Requirements
•
M320 Cabinet Size and Clearance Requirements on page 46
The minimum size enclosed cabinet that can accommodate the router is 600 mm wide
and 800 mm deep. A cabinet larger than the minimum requirement provides better
airflow and reduces the chance of overheating. To accommodate a single router, the
cabinet must be at least 20 U (35 in. or 88.9 cm) high. If you provide adequate cooling
air and airflow clearance, you can stack two routers in a cabinet that has at least 40 U
(70 in. or 1.78 m) of usable vertical space.
The minimum front and rear clearance requirements depend on the mounting
configuration you choose. The minimum total clearance inside the cabinet is 30.70 in.
between the inside of the front door and the inside of the rear door. If you choose a
front-mount installation, you must maintain clearance of 4.80 in. (122 mm) between the
front-mounting flanges and the inside of the cabinet front door, and 25.90 in. (658 mm)
betweenthe front-mountingflanges and the insideof thecabinet rear door. If you choose
an adjustable-mount installation usingthe mounting brackets, the clearance requirements
depend on where you install the mounting brackets.
Table 15 on page 46 provides the clearance requirements for each of the 11 mounting
bracket positions on the side of the chassis (position 1 represents the mounting brackets
installed closest to the front of the chassis; position 11 represents the mounting brackets
installed closest to the rear of the chassis). The front clearance is measured between
the front of the front rack rail and the inside of the cabinet front door. The rear clearance
is measured between the front of the front rack rail and the inside of the cabinet rear
door.
M320 Site Preparation Checklist Requirements on page 41•
• M320 Chassis Lifting Guidelines on page 216
M320 Cabinet Airflow Requirements
When you mount the router in a cabinet, you must ensure that ventilation through the
cabinet issufficient to prevent overheating. Following is alist of requirements to consider
when planning for chassis cooling:
•
Ensure that the cool air supply youprovide through the cabinet canadequatelydissipate
the thermaloutput of the router.“M320 Environmental Specifications” on page 247 lists
the router's environmental specifications, including its operating temperature and
thermal output.
•
Ensure that the cabinet allows the chassis hot exhaust air to exit from the cabinet
without recirculating into the router. An open cabinet (without a top or doors) that
employs hot air exhaust extraction from the top allows the best airflow through the
chassis. If the cabinet contains a top or doors, perforations in these elements assist
with removing the hot air exhaust. For an illustration of chassis airflow, see “M320
Cooling System Description” on page 37.
•
Install the router as close as possible to the front of the cabinet so that the cable
management system just clears the inside of the front door. This maximizes the
clearance in the rear of the cabinet for critical airflow.
•
If you operate the router in an enclosed 800-mm cabinet, you must install a baffle on
the inside of the rear door of the cabinet to prevent the router from overheating at
elevated ambient temperatures. The baffle separates the cool air intake from the hot
air exhaust in the rear of the cabinet (for baffle dimensions and location, see Figure 24
on page 48). We recommend that the baffle be made of soft foam with a depth of
2.25 in. (57 mm) so that it slightly touches the rear of the router when the rear cabinet
door is closed.
•
Route and dress all cables to minimize the blockage of airflow to and from the chassis.
Tools and Parts Required to Unpack the M320 Router on page 49
•
Unpacking the M320 Router on page 50
•
Verifying the M320 Router Parts Received on page 51
M320 Router Installation Summary
After you have prepared your installation site as described in “M320 Site Preparation
Checklist Requirements” on page 41, you are ready to unpack and install the router. It is
important to proceed through the installation process in the following order:
1. Review the safety guidelines explained in “General Safety Guidelines for M Series, MX
Series, and T Series Routers” on page 211.
2. Unpack the router and verify the parts received.
3. Install the mounting hardware.
See “Installing the M320 Mounting Hardware for a Four-Post Rack or Cabinet” on
page 56or “Installingthe M320 Mounting Hardwarefor Open-Frame Racks”on page 60.
4. Install the chassis.
See “Installing the M320 Router Using a Mechanical Lift” on page 63 or “Installing the
M320 Chassis in the Rack Manually” on page 79.
5. Perform the initial system startup as described in “Initially Configuring the M320
Router” on page 103.
Related
Documentation
M320 Chassis Lifting Guidelines on page 216•
Tools and Parts Required to Unpack the M320 Router
To unpack the router and prepare for installation, you need the following tools:
•
Phillips (+) screwdriver, number 2
•
1/2-in. or 13-mm open-end orsocket wrench to remove bracket boltsfrom the shipping
pallet
Blank panels to cover any slots not occupied by a component
Related
M320 Chassis Lifting Guidelines on page 216•
Documentation
Unpacking the M320 Router
The Router is shipped in a wooden crate. A wooden pallet forms the base of the crate.
The router chassis is bolted to this pallet. Quick Start installation instructions and a
cardboard accessory box are also included in the shipping crate.
The shipping cratemeasures 50 in. (127 cm) high,30 in.(76.2 cm)wide, and41 in. (104 cm)
deep. The total weight of the crate containing the router and accessories can range from
413 lb (187.7 kg) to 533 lb (242.2 kg).
To unpack:
1. Move the shipping crate to a staging area as close to the installation site as possible,
where you have enough room to remove the components from the chassis. While the
chassis is bolted to the pallet, you can use a forklift or pallet jack to move it.
2. Position the shipping crate with the arrows pointing up.
NOTE: The router is maximally protected inside the shipping crate. Do not
unpack it until you are ready to begin installation.
3. Open all the latches on the shipping crate.
4. Remove the front door of the shipping crate cover and set it aside.
5. Slide the remainder of the shipping crate cover off the pallet.
6. Remove the foam covering the top of the router.
7. Remove the accessory box and the Quick Start documentation.
8. Verify the parts received.
9. Remove the vapor corrosion inhibitor (VCI) packs attached to the pallet, being careful
not to break the VCI packs open.
10. To remove the brackets holding the chassis on the pallet, use a 1/2-in. socket wrench
and anumber 2 Phillips screwdriver toremove the bolts and screwsfrom thebrackets.
11. Store the brackets and bolts inside the accessory box.
12. Save the shipping crate cover, pallet, and packing materials in case you need to move
Verifying the M320 Router Parts Received on page 51•
• Installing the M320 Router Using a Mechanical Lift on page 63
• Installing the M320 Chassis in the Rack Manually on page 79
Verifying the M320 Router Parts Received
A packing list is included in each shipment. Check the parts in the shipment against the
items on the packing list. The packing list specifies the part numbers and descriptions of
each part in your order.
If any part is missing, contact a customer service representative.
A fully configured router contains the router chassis with installed components, listed in
Table 16 on page 51, and an accessory box, which contains the parts listed in Table 17
on page 52. The parts shipped with your router can vary.
Table 16: M320 Router Parts List for a Fully Configured Router
QuantityComponent
1Cable cover
2 upper, 2 lowerCable guards
rack-mounting brackets
1Chassis, including midplane, craft interface, and
Verifying the M320 Rack-Mounting Hardware Received on page 55
•
M320 Mounting Hole Locations for Four-Post Racks or Cabinets on page 56
•
Installing the M320 Mounting Hardware for a Four-Post Rack or Cabinet on page 56
•
M320 Mounting Hole Locations for Open-Frame Racks on page 59
•
Installing the M320 Mounting Hardware for Open-Frame Racks on page 60
Verifying the M320 Rack-Mounting Hardware Received
The following mounting hardware is supplied with the router:
•
Large mounting shelf—Required for all mounting options.
•
Small mountingshelf—Required for a four-post rack orcabinet, or for center-mounting
in an open-frame rack.
Related
Documentation
•
Two front-mounting flanges attached to the front of the chassis—Required for a
four-post rack or cabinet, or for front-mounting in an open-frame rack.
•
Spacer bars attached to the rear of the front-mounting flanges—Required only for a
four-post rack or cabinet.
•
Two adjustable center-mounting brackets attached to the center of the chassis (in
the mounting holes closest to the rear of the chassis)—Required only for
center-mounting in an open-frame rack. You can move each mounting bracket to one
of 11 positions on the side of the chassis.
Cage nuts and screws are not provided.
M320 Chassis Description on page 6•
• Unpacking the M320 Router on page 50
• Verifying the M320 Router Parts Received on page 51
M320 Mounting Hole Locations for Four-Post Racks or Cabinets
Table 18 on page 56 specifies the holes in which you insert mounting screws (anX indicates
a mounting hole location), and cage nuts if needed. The hole distances are relative to
one of the standard U divisions on the rack. The bottom of all mounting shelves is at
0.04 in. (0.02 U) above a U division.
Table 18: Four-Post or Cabinet Rack Mounting Hole Locations
Related
Documentation
Large
ShelfDistance Above U DivisionHole
X9.86 U17.26 in. (43.8 cm)30
Spacer
Bars
X16.86 U29.51 in. (74.9 cm)51
X13.86 U24.26 in. (61.6 cm)42
X10.86 U19.01 in. (48.3 cm)33
X7.86 U13.76 in. (34.9 cm)24
X4.86 U8.51 in. (21.6 cm)15
X1.86 U3.26 in. (8.3 cm)6
Small
Shelf
X0.86 U1.51 in. (3.8 cm)3
XX0.50 U0.88 in. (2.2 cm)2
X0.14 U0.25 in. (0.6 cm)1
M320 Site Preparation Checklist Requirements on page 41•
Installing the M320 Mounting Hardware for a Four-Post Rack or Cabinet
To prepare to install the M320 router in a four-post rack or cabinet, you install the large
shelf and the spacer bars on the front rail, and the small mounting shelf on the rear rail
(see Figure 26 on page 57. You also remove the adjustable center-mounting brackets
from the chassis.
Chapter 5: Installing the M320 Router Mounting Hardware
Figure 26: Installing the Mounting Hardware for a Four-Post Rack or
Cabinet
1.
Installing Cage Nuts (If Needed) for M320 Four-Post Racks or Cabinets on page 57
2.
Installing the Large Mounting Shelf for M320 Four-Post Racks or Cabinets on page 58
3.
Installing theSmall Mounting Shelf for M320 Four-Post Racks or Cabinets on page 58
4.
Removing the Adjustable Center-Mounting Brackets for M320 Four-Post Racks or
Cabinets on page 58
Installing Cage Nuts (If Needed) for M320 Four-Post Racks or Cabinets
For racks without threaded holes, you must install cage nuts in the locations specified in
“M320 Mounting Hole Locations for Four-Post Racks or Cabinets” on page 56. To install
the cage nuts:
1. On the front rack rails, install cage nuts in the holes specified for the large shelf and
the spacer bars.
2. On the rear rack rails, install cage nuts in the holes specified for the small shelf.
Installing the Large Mounting Shelf for M320 Four-Post Racks or Cabinets
To install the large mounting shelf:
1. On the front of each front rack rail, partially insert a mounting screw into the lowest
hole.
2. Install the large shelf on the front rack rails. Rest the bottom slot of each ear on a
mounting screw.
3. Partially insert a mounting screw into the top hole in each ear of the large shelf.
4. Tighten all the screws completely.
5. The router isshipped with each spacerbar attached tothe rearof eachfront-mounting
flange. Remove each spacer bar by removing the seven screws that fasten the spacer
bar to the front-mounting flange.
6. Place one of the spacer bars over an ear of the installed large shelf. Position the notch
in the rear of the spacer bar so the upper part of the bar is flush with the rack rail and
the lower part is flush with the ear of the shelf.
7. Insert a mounting screw into each of the nonthreaded holes in the recesses of the
spacer bar to secure the spacer bar.
8. Repeat Steps 6 and 7 for the other spacer bar.
9. Tighten all the screws completely.
Installing the Small Mounting Shelf for M320 Four-Post Racks or Cabinets
1. On the back of each rear rack rail, partially insert a mounting screw into the lowest
hole.
2. Install the small shelf on the back rack rails. Rest the bottom slot of each ear on a
mounting screw. The small shelf installson theback ofthe rearrails, extending toward
the center of the rack. The bottom of the small shelf should align with the bottom of
the large shelf.
3. Partially insert screws into the open holes in the ears of the small shelf.
4. Tighten all the screws completely.
Removing the Adjustable Center-Mounting Brackets for M320 Four-Post Racks or Cabinets
To remove the adjustable center-mounting brackets:
1. Loosen the three screws at the top and bottom of each bracket (see Figure 27 on
Chapter 5: Installing the M320 Router Mounting Hardware
Figure 27: Center-Mounting Bracket Removal
Related
Documentation
M320 Site Preparation Checklist Requirements on page 41•
• M320 Chassis Lifting Guidelines on page 216
M320 Mounting Hole Locations for Open-Frame Racks
The mounting holes for the adjustable center-mounting brackets are spaced
0.984 in. (25 mm) apart. The adjustable center-mounting brackets have holes for
rack-mounting screws, spaced at 3.5 in. (8.89 cm).
For an open-frame rack, Table 19 on page 59 specifies the holes in which you insert
mounting screws (an X indicates a mounting hole location), and cage nuts if needed.
The hole distances are relative to one of the standard “U” divisions on the rack. For
reference, the bottom of all mounting shelves is at 0.04 in. (0.02 U) above a U division.
Table 19: Open-Frame Rack Mounting Hole Locations
Small ShelfLarge ShelfDistance Above “U” DivisionHole
Small ShelfLarge ShelfDistance Above “U” DivisionHole
X7.86 U13.76 in. (34.9 cm)24
X6.86 U12.01 in. (30.5 cm)21
X5.86 U10.26 in. (26.0 cm)18
X4.86 U8.51 in. (21.6 cm)15
X3.86 U6.76 in. (17.1 cm)12
X2.86 U5.01 in. (12.7 cm)9
X1.86 U3.26 in. (8.3 cm)6
XX0.86 U1.51 in. (3.8 cm)3
Related
M320 Site Preparation Checklist Requirements on page 41•
Documentation
Installing the M320 Mounting Hardware for Open-Frame Racks
To prepare to center-mount the router in an open-frame rack, you install both the large
and small mounting shelves. Optionally, you can move the adjustable center-mounting
brackets to any of 11 positions on the side of the chassis. The spacer bars are not needed
to center-mount thechassis; however,you canleave them attached to the front-mounting
flanges.
To prepare to front-mount the router in an open-frame rack, install the large mounting
shelf on the rack. The small mounting shelf and adjustable center-mounting brackets
are needed only if you are center-mounting the router. The spacer bars are not needed.
Chapter 5: Installing the M320 Router Mounting Hardware
Figure 28: Installing the Mounting Hardware for a Center-Mount
Open-Frame Rack
1.
Installing Cage Nuts (If Needed) for M320 Open Frame Racks on page 61
2.
Installing the Large Mounting Shelf for the M320 Open-Frame Racks on page 62
3.
Installing the Small Mounting Shelf for the M320 Open-Frame Racks on page 62
4.
Moving the Adjustable Center-Mounting Brackets for M320 Open-Frame
Racks on page 62
Installing Cage Nuts (If Needed) for M320 Open Frame Racks
For racks without threaded holes, you must install cage nuts in the locations specified in
“M320 Mounting Hole Locations for Four-Post Racks or Cabinets” on page 56. To install
the cage nuts:
1. On the front rack rails, install cage nuts in the holes specified for the large shelf.
2. On the rear rack rails, install cage nuts in the holes specified for the small shelf.
Installing the Large Mounting Shelf for the M320 Open-Frame Racks
1. On the rear of each rack rail, partially insert a mounting screw into the lowest hole
specified in “M320 Mounting Hole Locations for Open-Frame Racks” on page 59 for
the large shelf.
2. Install the large shelf on the rack. Rest the bottom slot of each ear on a mounting
screw.
3. Partially insert screws into the open holes in the ears of the large shelf.
Installing the Small Mounting Shelf for the M320 Open-Frame Racks
1. On the front of each rack rail, partially insert a mounting screw into the lowest hole
specified in “M320 Mounting Hole Locations for Open-Frame Racks” on page 59 for
the small shelf.
2. Install the small shelf on the rack. Rest the bottom slot of each ear on a mounting
screw. The small shelf installs on the front of the rails, extending away from the rack.
The bottom of the small shelf should align with the bottom of the large shelf
3. Partially insert screws into the open holes in the ears of the small shelf.
4. Tighten all the screws completely.
Moving the Adjustable Center-Mounting Brackets for M320 Open-Frame Racks
The router has two adjustable center-mounting brackets that are initially attached to
the mounting holes closest to the rear ofthe chassis. Youcan movethe pair of adjustable
center-mounting brackets to one of 11 positions on the side of the chassis. The mounting
holes for connecting the mounting brackets to the chassis are spaced 0.984 in. (25 mm)
apart.
To move the adjustable center-mounting brackets to a different location on the side of
the chassis:
1. Loosen the three screws at the top and bottom of each bracket (see “Removing the
Adjustable Center-Mounting Brackets for M320 Four-Post Racks or Cabinets” on
page 58).
2. Align each mounting bracket with the mounting holes on the chassis that correspond
to your rack mounting option.
3. Insert the three screws at the top and bottom of each mounting bracket, tightening
each partway.
4. Tighten all the screws completely.
Related
Documentation
• M320 Chassis Lifting Guidelines on page 216
• M320 Site Preparation Checklist Requirements on page 41
Installing the M320 Router Using a
Mechanical Lift
•
Tools Required to Install the M320 Router Using a Mechanical Lift on page 63
•
Installing the M320 Router Using a Mechanical Lift on page 63
•
Installing the M320 Cable Guards on page 68
Tools Required to Install the M320 Router Using a Mechanical Lift
To install the M320 router using a mechanical lift, you need the following tools:
•
Mechanical lift
•
Phillips (+) screwdrivers, number 2
Related
Documentation
M320 Chassis Lifting Guidelines on page 216•
• M320 Cabinet Size and Clearance Requirements on page 46
• M320 Chassis Description on page 6
Installing the M320 Router Using a Mechanical Lift
Because of the router's size and weight—up to 439 lb (199.6 kg) depending on the
configuration—we strongly recommend that you install the router using a mechanical
lift.
Before installing the router in the rack:
•
The “M320Site Preparation Checklist Requirements”on page41 summarizes the tasks
you need to perform when preparing a site for router installation.
•
Removethe router fromthe shipping crate as describedin “Unpackingthe M320 Router”
on page 50.
To avoid harmto yourself or therouter as you install and maintain it, followthe guidelines
for working with and near electrical equipment, as well as the safety procedures for
working with routers. However, providing an exhaustive set of guidelines for working with
electrical equipment is beyond the scope of this documentation.
1.
Attaching the Installation Handle to the M320 Router on page 64
2.
Mounting the M320 Chassis Using a Mechanical Lift on page 65
3.
Removingthe M320 Installation Handle and Reinstalling thePowerSupplies onpage 67
Attaching the Installation Handle to the M320 Router
To assist you with the installation of the router, attach the installation handle over the
three lowest power supply slots of the chassis. To remove the corresponding power
supplies and attach the handle:
Chapter 6: Installing the M320 Router Using a Mechanical Lift
Figure 29: Removing an M320 Power Supply Before Installing the
Installation Handle
Figure 30: Attaching the M320 Installation Handle
Mounting the M320 Chassis Using a Mechanical Lift
Before installing the chassis in the rack:
•
Read the safety information in “M320 Chassis Lifting Guidelines” on page 216
•
Removethe router fromthe shipping crate as describedin “Unpackingthe M320 Router”
on page 50.
•
Install themounting hardware as described in“Installing the M320 Mounting Hardware
for Open-Frame Racks” on page 60 or “Installing the M320 Mounting Hardware for a
Four-Post Rack or Cabinet” on page 56.
CAUTION: Before front-mounting the router in a rack, have a qualified
technician verify that the rack is strong enough to support the router's weight
and is adequately supported at the installation site.
To install the router using a lift (see Figure 31 on page 67):
1. Ensure that the rack is in its permanent location and is secured to the building. Ensure
that the installationsite allows adequate clearance for both airflow andmaintenance.
For details, see “M320 Clearance Requirements” on page 44.
2. Load the Router onto the lift, making sure it rests securely on the lift platform.
CAUTION: Do not lift the router using the craft interface, installation
handle, or the handles on top of the chassis. Use these handles only to
help position the router.
3. Using the lift, position the router in front of the rack or cabinet, centering it in front of
the mounting shelves.
4. Lift the chassis approximately 0.75 in. above the surface of the mounting shelves and
position it as close as possible to the shelves.
5. Carefully slide the router onto the mounting shelves so that the bottom of the chassis
and the mounting shelves overlap by approximately 2 inches.
6. With one person pulling on the installation handle from the rear of the rack or cabinet
while another person pushes on the front-mounting flanges, slide the router onto the
mounting shelves until the mounting brackets or front-mounting flanges contact the
rack rails or spacer bars (depending on your type of installation). The shelves ensure
that theholes inthe mounting brackets and the front-mounting flanges of the chassis
align with the holes in the rack rails.
7. Move the lift away from the rack.
8. If you are installing the router in a four-post rack or cabinet, install a mounting screw
and a cage nut into each of the holes aligned with the threaded holes in the spacer
bars. If you are installing the router in an open-frame rack, install a mounting screw
into each of the open mounting holes aligned with the rack, starting from the bottom.
9. Visually inspect the alignment of the router. If the router is installed properly in the
rack, all the mounting screws on one side of the rack should be aligned with the
mounting screws on the opposite side and the router should be level.
Chapter 6: Installing the M320 Router Using a Mechanical Lift
Figure 31: Installing the M320 Router in the Rack
NOTE: This illustration depicts the router being installed in an open-frame
rack.
Removing the M320 Installation Handle and Reinstalling the Power Supplies
After you have installed therouter,remove theinstallation handle and reinstall the power
supplies in the chassis, starting from the bottom (see Figure 32 on page 68):
6. Tighten the captive screws on each side of the power supply faceplate to secure the
power supply in the chassis.
7. Repeat the procedure for the remaining power supplies.
Figure 32: Reinstalling an M320 Power Supply
Related
Documentation
Preventing Electrostatic Discharge Damage to an M320 Router on page 214•
• M320 Chassis Lifting Guidelines on page 216
• M320 Chassis Description on page 6
• M320 Cabinet Size and Clearance Requirements on page 46
• M320 Site Preparation Checklist Requirements on page 41
• General Safety Guidelines for M Series, MX Series, and T Series Routers on page 211
• Maintenance and Operational Safety Warnings for M Series, MX Series, and T Series
Routers on page 225
• General Electrical Safety Warnings for M Series, MX Series, and T Series Routers on
page 231
Installing the M320 Cable Guards
After the chassis is installed in the rack or cabinet, you can install the four cable guards.
The cable guards protect the PIC and CIP cables from rubbing against the front edges
of the chassis.
To install the cable guards (see Figure 33 on page 69):
1. Place one of the upper cable guards over one of the front-mounting flanges of the
chassis, aligning the top of the cable guard with the top of the flange. Each of the
three captive screws on the guard should be aligned with a corresponding standoff
on the flange.
2. Tighten each of the three captive screws partway on the cable guard.
3. Tighten each of the three captive screws completely.
Chapter 6: Installing the M320 Router Using a Mechanical Lift
4. Repeat Steps 1 through 3 for the other upper cable guard.
5. Place one of the lower cable guards over one of the front-mounting flanges of the
chassis, aligning the cable guard with the standoffs on the flange. Each of the two
captive screws on the guard should be aligned with acorresponding hole in the flange.
6. Tighten each of the two captive screws partway on the cable guard.
7. Tighten each of the two captive screws completely.
8. Repeat Steps 5 through 7 for the other lower cable guard.
Figure 33: Installing the M320 Cable Guards
Related
Documentation
• M320 Chassis Lifting Guidelines on page 216
• M320 Chassis Description on page 6
• M320 Cabinet Size and Clearance Requirements on page 46
Two to four SIBs are installed in the router. The SIBs are located in the rear of the chassis
in the slots marked SIB0 through SIB3. SIBs are hot-insertable and hot-removable. Each
SIB weighs approximately 4 lb (1.8 kg).
To remove a SIB (see Figure 35 on page 73):
1. Place an electrostatic bag or antistatic mat on a flat, stable surface.
The router can have one or two CBs. They are located in the upper rear of the chassis in
the slots marked CB0 and CB1. Each CB weighs approximately 3.4 lb (1.5 kg).
To remove the CBs (see Figure 36 on page 74):
1. Place an electrostatic bag or antistatic mat on a flat, stable surface.
3. Loosen the captive screws on the ejector handles on both sides of the CB faceplate.
4. Flip the ejector handles outward to unseat the CB.
5. Grasp the ejector handles, and slide the CB about halfway out of the chassis.
6. Place one hand underneath the CB to support it, and slide it completely out of the
the strap to an approved site ESD grounding point. See the instructions for your site.
chassis. Place it on the antistatic mat.
7. Repeat the procedure for the second CB.
Figure 36: Removing a CB
Removing the M320 Rear Fan Tray
The rear fan tray is mounted vertically on the right side of the rear of the chassis. The rear
fan tray contains seven fans. The fan tray weighs about 8.4 lb (3.8 kg).
CAUTION: Do not stack hardware components on one another after you
remove them. Place each component on an antistatic mat resting on a
stable, flat surface.
CAUTION: To maintain proper cooling, do not operate the router with the
rear fan tray removed for more than 1 minute.