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—Corporate rebranding.
August 2010—Corporate rebranding.
May 2010—Updated VCCI class B compliance for Japan. Corrected the chassis grounding procedure.
July 2009—Updated product names.
10 April 2009—530-018005-01 Revision 3. Added related topics to aid in navigation.
26 January 2009—530-018005-01 Revision 2. Added Enhanced Compact Forwarding Engine Board (CFEB-E) support.
12 January 2007—530-018005-01 Revision 1. Corrected the input operating voltage range and the nominal input voltage for DC power
supplies and AC power supplies. Corrected the clearance requirements. Corrected the system architecture.
20 October 2006—530-017392-01 Revision 1. Added European Community EMC Declaration of Conformity.
28 June 2006—530–014300–01 Revision 3. Addedmaximum aggregate throughput of theFIC. Corrected the packet forwardingrate. Added
how much torque to apply when securing the cable on a power supply.
30 May 2006—530–014300–01 Revision 2. Corrected maximum aggregate throughput. Added power cable warning in Japanese. Added
Lithium battery statement.
14 September 2005—530–014300–01 Revision 1. General updates.
5 January 2004—530–009331–01 Revision 3. Cable management information.
22 September 2003—530–009331–01 Revision 2. DC power supply information.
24 July 2003—530–009331–01 Revision 1. First edition.
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 M7i Multiservice Edge
Router. It explains how to prepare your site for router installation, unpack and install the
hardware,power onthe router, perform initial software configuration, andperform 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 M7i Multiservice Edge Router is a complete routing system that provides ATM,
channelized, Ethernet, IP services, and SONET/SDH interfaces for large networks and
network applications, such as those supported by Internet service providers (ISPs).
The router accommodates up to four Physical Interface Cards (PICs). In addition to the
PICs, the Fixed Interface Card (FIC) provides two Fast Ethernet ports or one Gigabit
Ethernet port, depending on your configuration. The built-in tunnel interface on the
Compact Forwarding Engine Board (CFEB) and Enhanced Compact Forwarding Engine
Board (CFEB-E) provides tunneling services. The optional Adaptive Services Module
(ASM) on the CFEB and CFEB-E, and the optional MultiServices Module (MSM) on the
CFEB-E allow one or more services to be configured on this interface.
The router architecture cleanly separates control operations from packet forwarding
operations,which helps to eliminateprocessing and trafficbottlenecks.Control operations
in the router are performed by the Routing Engine, which runs Junos OS to handle routing
protocols,traffic engineering, policy, policing, monitoring, and configuration management.
Application-specific integrated circuits (ASICs), a definitive part of the router design,
enable the router to forward data at the high speeds demanded by current network
media. Forwarding operations in the router are performed by the Packet Forwarding
Engine, which consists of hardware, including ASICs, designed by Juniper Networks. The
Packet Forwarding Engine can forward up to 16 million packets per second (Mpps) for
all packet sizes. The aggregate throughput is 4 gigabits per second (Gbps), full duplex,
for the FPC with 4 PIC slots. The fixed interface card (FIC) has a maximum throughput
of 1 Gbps full duplex. Inserting a combination of PICs with an aggregate higher than the
maximum throughput of the FPC is supported, but constitutes oversubscription of the
FPC.
M7i Compact Forwarding Engine Board (CFEB) and Enhanced Compact Forwarding
Engine Board (CFEB-E) Description on page 8
•
M7i CFEB and CFEB-E LEDs on page 14
•
M7i Fixed Interface Card (FIC) Description on page 15
•
M7i FIC LEDs on page 16
•
M7i PICs Description on page 16
•
M7i PIC LEDs on page 17
•
M7i Flexible PIC Concentrators (FPCs) Description on page 18
•
M7i Routing Engine Description on page 18
•
M7i Routing Engine LEDs on page 21
•
M7i Power Supply Overview on page 21
•
M7i Cooling System Overview on page 24
•
M7i Cable Management System on page 25
M7i Component Redundancy
The router can be configured with two load-sharing, fully redundant power supplies to
distribute power to the other components. If one power supply fails, the second power
supply can provide full power to the router's components indefinitely.
The router chassis is a rigid sheet metal structure that houses the other hardware
components. The chassis is 17.5 in. (44.5 cm) wide and 18 in. (45.7 cm) deep. The chassis
height of 3.5 in. (8.9 cm) enables stacked installation of 21 M7i routers in a single
floor-to-ceiling rack. For more information, see “M7i Router Rack Requirements” on
page 36.
The two mounting brackets (one on each side) extend the chassis width to 19 in.
(48.2 cm).
Figure 1: Front of Chassis
Figure 2: Rear of Chassis
The chassis includes the following electrical safety components:
•
One electrostatic discharge (ESD) points (banana plug receptacles), at the front of
the chassis, as shown in Figure 1 on page 6.
•
Two internally threaded inserts providing grounding points for the router.
WARNING: Beforeremoving or installing components of a functioning 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.
The router must be connected to earth ground during normal operation.
For further safety information, see “General Safety Guidelines for M Series,
MX Series, and T Series Routers” on page 125 and “General Safety Warnings
for M Series, MX Series, and T Series Routers” on page 126.
For chassis serial number information, see “Displaying M7iRouter Components and Serial
Numbers” on page 187.
Related
Documentation
M7i Router Physical Specifications on page 159•
• Overview of M7i Router Installation on page 39
• M7i Router Description on page 3
M7i Midplane Description
The midplane is a panel located in the center of the chassis, running from side to side
and formingthe rear of the PIC card cage(see Figure 3 on page7). All router components
plug directly into the midplane. The midplane contains an EEPROM that stores the serial
number and revision level of the midplane.
The midplane performs the following functions:
•
Transfer of packets—An incoming data packet crosses the midplane to a CFEB or
CFEB-E. The CFEB or CFEB-E performs switchingand forwarding functionsand transfers
outgoing packets back across the midplane to the FIC or PICs for transmission to the
network.
•
Power distribution—The midplane distributes power to all router components from
the power supplies attached to it.
•
Signal connectivity—The midplane transports the signals exchanged by system
components for monitoring and control purposes.
Figure 3: Midplane
For midplane serial number information, see “Displaying M7i Router Components and
Serial Numbers” on page 187.
The M7i Multiservice Edge Router houses either a Compact Forwarding Engine Board
(CFEB) or an Enhanced Compact Forwarding Engine Board (CFEB-E), which is located
on the rear of the router above the power supplies, as shown in Figure 2 on page 6. It
provides route lookup, filtering, and switching on incoming data packets, then directs
outbound packets to the appropriate interface for transmission to the network. It can
process 16 million packets per second (Mpps). The CFEB or CFEB-E communicates with
the Routing Engine using a dedicated 100-Mbps link that transfers routing table data
from the Routing Engine to the forwarding table. The link is also used to transfer routing
link-state updates and other packets destined for the router from the CFEB or CFEB-E
to the Routing Engine.
The CFEB or CFEB-E provides the following functions:
•
Route lookups—Performs route lookups using the forwarding table stored in the
synchronous SRAM (SSRAM) on CFEBs or stored in the RLDRAM on CFEB-Es.
•
Management of shared memory —Uniformly allocates incoming data packets
throughout the router's shared memory.
•
Transfer of outgoing data packets—Passes data packets to the destination FIC or PIC
when the data is ready to be transmitted.
•
Transfer of exception and control packets—Passes exception packets to the
microprocessor on the CFEB or CFEB-E, which processes almost all of them. The
remainder are sent to the Routing Engine for further processing. Any errors originating
in the Packet Forwarding Engine and detected by the CFEB or CFEB-E are sent to the
Routing Engine using system log messages.
•
Built-in tunnel interface—Encapsulates arbitrary packets inside a transport protocol,
providing a private, secure path through an otherwise public network.
The built-in tunnel interface on the CFEB or CFEB-E is configured the same way as a
PIC. For information about configuring the built-in tunnel interface, see the Junos OSServices Interfaces Configuration Guide.
•
Optional Adaptive Services Module (ASM)—Provides one or more services on one PIC.
See “M7i Adaptive Services Module” on page 12 for more information.
The CFEB and CFEB-E are hot-pluggable when you replace a CFEB with a CFEB or a
CFEB-E with a CFEB-E. Upgrading or downgrading a CFEB device requires a system
reboot, as described in “Upgrading and Downgrading the CFEB and CFEB-E” on page88.
You can remove and replace the CFEB or CFEB-E without powering down the router, but
the routing functions of the system are interrupted when it is removed.
The Adaptive Services Module is an optional component of the CFEB and CFEB-E. The
Adaptive Services Module is similar to the standaloneAdaptive Services PIC,but operates
at a reduced bandwidth. The Adaptive Services Module enables you to perform one or
more services on the same PIC by configuring a set of services and applications.
The Adaptive Services Module provides the following services:
•
Stateful firewall—A type of firewall filter that considers state information derived from
previous communications and other applications when evaluating traffic.
•
Network Address Translation (NAT)—A security procedure for concealing host
addresses on a private network behind a pool of public addresses.
•
Intrusion detection services (IDS)—A set of tools for detecting, redirecting, and
preventing certain kinds of network attack and intrusion.
The configuration for these three servicescomprises aseries ofrules that you can arrange
in order of precedence as a rule set. Each rule follows the structure of a firewall filter,
with a from statement containing input or match conditions and a then statement
containing actions to be taken if the match conditions are met.
For information about configuring interfaces on the ASM, see the Junos OS ServicesInterfaces Configuration Guide.
M7i MultiServices Module
The MultiServices Module is an optional component of the CFEB-E. The CFEB does not
support the MultiServices Module. The MultiServices Module enables you to perform one
or more services on the same PIC by configuring a set of services and applications. Like
the standalone MultiServices 100 PIC, the MultiServices Module supports the following
services:
•
Layer 3 Services:
•
•
•
•
•
•
•
Stateful firewall—A type of firewall filter that considers state information derived
from previous communications and other applications when evaluating traffic.
Network Address Translation (NAT)—A security procedure for concealing host
addresses on a private network behind a pool of public addresses.
Intrusion detection services (IDS)—A set of tools for detecting, redirecting, and
preventing certain kinds of network attack and intrusion.
The configuration for these services comprises a series of rules that you can arrange in
order of precedence as a rule set. Each rule follows the structure of a firewall filter, with
a from statement containing input or match conditions and a then statement containing
actions to be taken if the match conditions are met.
NOTE: You can enable either Layer 2 or Layer 3 services on the MultiServices
Module,but you cannot enable both Layer 2and Layer3 services concurrently.
For information about configuring interfaces on the MSM, see the Junos OS Services
Interfaces Configuration Guide.
Related
Documentation
M7i CFEB and CFEB-E LEDs on page 14•
• M7i and M10i Packet Forwarding Engine Architecture on page 28
• M7i Router Description on page 3
• M7i Router Physical Specifications on page 159
M7i CFEB and CFEB-E LEDs
Table 3: States for CFEB or CFEB-E LEDs
DescriptionStateColorLabel
CFEB/CFEB-E is running normally.On steadilyGreenOK
CFEB-E is starting upBlinking
CFEB/CFEB-E is offline.Off
CFEB/CFEB-E is not operational or is in reset mode.On steadilyRedFAIL
CFEB/CFEB-E is functioning properly.Off
On steadilyBlueMASTER
CFEB/CFEB-E is functioning as master. On an M7i
router, this LED is always lit.
M7i Compact Forwarding Engine Board (CFEB) and Enhanced Compact Forwarding
•
Engine Board (CFEB-E) Description on page 8
M7i Fixed Interface Card (FIC) Description
The Fixed Interface Card (FIC) is built into the router chassis.
The FIC receives incoming packets from the network and transmits outgoing packets to
the network, providing support for Fast Ethernet ports or Gigabit Internet interfaces,
depending on which version of the FIC is installed in the router.
The FIC also allows you to view alarm status at a glance and to perform some system
control functions, such as taking PICs online and offline.
The FIC is located on the front of the chassis to the left of the Routing Engine and is not
a field-replaceable unit (FRU).
Each FIC consists of the following components:
•
The FIC has either two 100Base-TX Fast Ethernet ports or one Gigabit Ethernet port,
depending onwhich type of FIC is installed inthe router. Table 24 on page 173 describes
the interface connectors. See Figure 9 on page 15 and Figure 10 on page 15.
For more information about Fast Ethernet and Gigabit Ethernet interfaces, see the M7iMultiservice Edge Router PIC Guide. The networking interface on the FIC is configured
the sameway as aPIC. Formore information aboutconfiguring interfaces see the JunosOS Network Interfaces Configuration Guide.
Related
Documentation
•
Buttons on the FIC labeled PICS ON/OFF to take a Physical Interface Card (PIC) offline
when it needs to be removed, or bring it online when it is replaced.
•
Alarm LEDs and interface LEDs.
Figure 9: FIC with Fast Ethernet Ports
Figure 10: FIC with Gigabit Ethernet Port
M7i FIC LEDs on page 16•
• Connecting FIC and PIC Cables to the M7i Router on page 55
Two large alarm LEDs are located on the right of the FIC (see Figure 9 on page 15 and
Figure 10 on page 15). 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.
To deactivate red and yellow alarms,you must clear the condition that caused the alarm.
Table 4 on page 16 describes the alarm LEDs in more detail.
Table 4: Alarm LEDs
DescriptionStateColorShape
Related
Documentation
M7i PICs Description
On steadilyRed
On steadilyYellow
Critical alarm LED—Indicates a critical condition that
can cause the router to stop functioning, such as
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.
Table 5 on page 16 describes the FIC interface LEDs in more detail.
Table 5: FIC Interface LEDs
DescriptionStateColorLabel
The port is online.On steadilyGreenLINK
The port is receiving data.BlinkingGreenACTIVITY
The port might be on, but is not receiving data.Off
M7i Fixed Interface Card (FIC) Description on page 15•
• Connecting FIC and PIC Cables to the M7i Router on page 55
PICs physically connect the router to network media. PICs receive incoming packets from
the network and transmit outgoing packets to the network, performing framing and
line-speed signaling for their media type as required. PICs also encapsulate outgoing
packets received from the Compact ForwardingEngine Board (CFEB) or Enhanced CFEB
(CFEB-E) before transmitting them. The controller ASIC on each PIC performs additional
control functions specific to the PIC media type.
The router supports various PICs, including ATM, Channelized, Gigabit Ethernet, Services,
and SONET/SDH interfaces. You can install PICs of different media types on the same
router as long as the router supports those PICs.
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.
Four PIC slots are located in one Flexible PIC Concentrator (FPC), FPC0, which is built in
to the chassis. The PIC slots are numbered from 0 (zero) through 3, right to left. The
number of ports on a PIC depends on the type of PIC.
The M7i router has a maximum throughput of 3.2 Gbps full duplex for the FPC with 4 PIC
slots. Inserting a combination of PICs with an aggregate higher than the maximum
throughput is supported, but constitutes oversubscription of the FPC. The fixed interface
card (FIC) has a maximum throughput of 1 Gbps full duplex.
PICs are hot-removable and hot-insertable.
Most PICs supported on the M7i router have the following components.
Related
Documentation
M7i PIC LEDs
•
One or more cable connector ports—Accept a network media connector.
•
LEDs—Indicate PIC and port status. Most PICs have an LED labeled STATUS on the
PIC faceplate. Some PICs have additional LEDs, often one per port. The meaning of
the LED states differs for various PICs.
•
Ejector lever—Controls the locking system that secures the PIC in the card cage.
M7i PICs Supported.•
• M7i End-of-Life PICs Supported
• M7i PIC LEDs on page 17
• M7I Field-Replaceable Units (FRUs) on page 85
• M7i Flexible PIC Concentrators (FPCs) Description on page 18
• PIC Serial Number ID Label on page 189
• Replacing an M7i PIC on page 89
• Troubleshooting the M7i FIC or PICs on page 80
LEDs indicate PIC and port status. Most PICs have an LED labeled STATUS on the PIC
faceplate. Some PICs have additional LEDs, often one per port. The meaning of the LED
states differs for various PICs. For more information, see the M7i Multiservice Edge RouterPIC Guide.
Flexible PIC Concentrators (FPCs) house the PICs that connect the router to network
media (for information about PICs, see “M7i PICs Description” on page 16). On the M7i
router, each FPC is built in (it cannot be removed from the chassis as on other M Series
routers). The networking and services interfaces in the M7i router are grouped onto two
logical FPCs by the router, (see Figure 11 on page 18). PICs are located on FPC 0. On FPC
1 the FIC is located in slot 3 and the built-in tunnel interface is located in slot 2. If the ASM
is installed on the CFEB or CFEB-E, itis located on slot 2 with the built-in tunnel interface.
Figure 11: FPC Slot Numbering
Related
Documentation
M7i Router Description on page 3•
• M7i Router Physical Specifications on page 159
• Overview of M7i Router Installation on page 39
M7i Routing Engine Description
The Routing Engine runs Junos OS. Thesoftware processes that run on the Routing Engine
maintain the routing tables, manage the routing protocols used on the router, control
the router's interfaces, control some chassis components, and provide the interface for
system management and user access to the router.
The Routing Engine is installed into the midplane from the front of the chassis, as shown
in Figure 1 on page 6. When two Routing Engines are installed, both are powered on, but
only one is active (the master); the second Routing Engine is in standby mode and
performs no functions. At boot time, both Routing Engines run an arbitration algorithm
and elect one as master. For a more detailed description of the Routing Engine's role in
router architecture, see “Routing Engine Architecture” on page 29.
The Routing Engineis hot-pluggable. Ifyou have onlyone Routing Engine,you can remove
and replace the Routing Engine without powering down the router, but the routing
functions ofthe system areinterrupted whenit is removed.If the host systemis redundant,
the backup RoutingEngine is hot-removable and hot-insertable.A backupRouting Engine
can be removed without interrupting routing functions.
The Routing Engine (shown in Figure 12 on page 19) is a two-board system with the
following components:
•
CPU—Runs Junos OS to maintain the router's routing tables and routing protocols. It
has a Pentium-class processor.
•
SDRAM—Provides storage for the routing and forwarding tables and for other Routing
Engine processes.
•
CompactFlash card—This disk is optional. If installed, it provides primary storage. It
can accommodate software images, configuration files, and microcode.
•
Hard disk—If no CompactFlash card is installed, provides primary storage for software
images, configuration files, and microcode. If an CompactFlash card is installed, the
hard disk provides secondary storage for log files and memory dumps, and can reboot
the system if the CompactFlash card fails.
•
PC card slot—Accepts a removable PC card, which stores software images for system
upgrades.
•
Four LEDs—A green LED labeled HDD, a blue LED labeled MASTER, a red LED labeled
FAIL, and a green LED labeled ONLINE indicate Routing Engine status.
•
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 Routing Engine.
•
I2C/EEPROM—Stores the serial number of the Routing Engine.
•
Reset button—Reboots the Routing Engine when pressed.
•
Offline button—Powers down the Routing Engine when pressed.
•
Thumbscrews—Secure the Routing Engine in the chassis.
Boot Sequence
The disk from which the router boots is called the primary boot device, and the other disk
is the alternate boot device.
The router attempts to boot from three devices in this order:
•
PC Card
•
CompactFlash card
•
Hard disk
NOTE: If the router boots froman alternateboot device,a yellow alarm lights
the LED on the router’s craft interface.
M7i Routing Engine Management Ports
On the right half of the Routing Engine are ports for connecting the Routing Engine to
one or more external devices on which system administrators can issue Junos OS
command-line interface (CLI) commands to manage the router.
The ports are labeled and function as follows:
Related
Documentation
•
CONSOLE—Connects the Routing Engine to a system console through an RS-232
(EIA-232) serial cable.
•
AUX/MODEM— Connects the Routing Engine to a laptop, modem, or other auxiliary
device through an RS-232 (EIA-232) serial cable.
•
MGMT—Connectsthe RoutingEngine through an Ethernet connectionto 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 left edge of the port indicate the
connection in use: the yellow LED lights for a 10-Mbps connection and the green LED
lights for a 100-Mbps connection.
For information about the pinouts for the connectors, see “RJ-45 Connector Pinouts for
the M7i Routing Engine MGMT Port” on page 181.
Figure 13 on page 20 shows the ports that connect to the Routing Engine.
Four LEDs—A green LED labeled HDD, a blue LED labeled MASTER, a red LED labeled
FAIL, and a green LED labeled ONLINE indicate Routing Engine status. Table 6 on page 21
describes the LED states.
Table 6: States for Routing Engine LEDs
Chapter 2: M7i Hardware Components
DescriptionStateColorLabel
There is read/write activity on the PC card.BlinkingGreenHDD
Related
Documentation
M7i Routing Engine Description on page 18•
• M7i Router Description on page 3
• M7i Router Physical Specifications on page 159
• M7i Router Power Requirements on page 163
M7i Power Supply Overview
•
M7i Power System Description on page 21
•
M7i AC Power Supply on page 22
•
M7i DC Power Supply on page 23
•
M7i Power Supply LEDs on page 24
M7i Power System Description
On steadilyBlueMASTER
Routing Engine is functioning as master. On an M7i
router, this LED is always lit.
Routing Engine is not operational.On steadilyRedFAIL
Routing Engine is running normally.On steadilyGreenONLINE
The router uses either AC or DC power. You can install one or two load-sharing power
supplies at the bottom rear of the chassis, as shown in Figure 2 on page 6. The power
supplies connect to the midplane, which distributes power to router components
according to their individual voltage requirements.
For full redundancy, two power supplies are required. When the power supplies are
installed and operational, they automatically share the electrical load. If a power supply
stops functioning for any reason, the second power supply instantly begins providing all
the power the router needs for normal functioning. It can provide full power indefinitely.
An enable control signal on the output connector of each power supply ensures that the
supply is fully seated into the router midplane before the supply can be turned on. The
enable pin prevents a user-accessible energy hazard, so there is no interlocking
mechanism. The enable pin disables the voltage at the output connector if the power
supply is not turned off before removal.
Power supplies are hot-removable and hot-insertable, as described in “M7I
Field-Replaceable Units (FRUs)” on page 85. To avoid electrical injury, carefully follow
the instructions in “Replacing an M7i AC Power Supply” on page 106 and “Replacing a DC
Power Supply” on page 111.
NOTE: After powering off a power supply, wait at least 60 seconds before
turning itback on. Afterpowering on a power supply,wait at least 60 seconds
before turning it off.
If the router is completely powered off when you power on the power supply,
the Routing Engine bootsas thepower supplycompletesits startupsequence.
If the Routing Engine finishes booting and you need to power off the router
again, first issue the CLI request system halt command. For more information,
see .
Related
Documentation
M7i AC Power Supply
After a power supply is powered on, it can take up to 60 seconds for status
indicators—suchasthe output statusLED on thepower supply, thecommand
display output, and messages on the LED display on the craft interface—to
indicatethat the powersupply is functioning normally. Ignore errorindicators
that appear during the first 60 seconds.
M7i AC Power Supply on page 22•
• M7i DC Power Supply on page 23
• Removing an M7i AC Power Supply on page 107
• Troubleshooting the M7i Power System When the LED on One M7i Power Supply Is Off
on page 81
An AC-powered router has one or two load-sharing AC power supplies, located at the
bottom rear of the chassis, as shown in Figure 2 on page 6. For information about power
supply redundancy and replaceability, see “M7i Power System Description” on page 21.
• M7i AC Power Electrical Safety Guidelines and Warnings on page 149
• Removing an M7i AC Power Cord on page 110
• Replacing an M7i AC Power Supply on page 106
A DC-powered router has one or two load-sharing DC power supplies, located at the
bottom rear of the chassis, as shown in Figure 2 on page 6. For information about power
supply redundancy and replaceability, see “M7i Power System Description” on page 21.
Figure 15 on page 23 shows the power supply.
Figure 15: DC Power Supply
Related
Documentation
Table 23 on page 170•
• M7i Power Supply LEDs on page 24
NOTE: The DC power supplies are marked –48 VDC. This is the nominal
voltage associatedwith the battery circuit.Any higher voltages areassociated
only with float voltages for the charging function.
• DC Power Electrical Safety Warnings for M Series, MX Series, and T Series Routers on
page 150
• M7i DC Power Electrical Safety Guidelines on page 149
• Replacing a DC Power Supply on page 111
M7i Power Supply LEDs
Table 7 on page 24 describes the LED on both AC and DC power supplies.
Table 7: States for the M7i Power Supply LED
DescriptionStateColorLabel
On steadilyGreenOUTPUT OK
Blinking
Related
Documentation
Installing an M7i AC Power Supply on page 108•
• M7i Power System Description on page 21
• Replacing an M7i AC Power Supply on page 106
• Troubleshooting the M7i Power System When the LED on One M7i Power Supply Is Off
on page 81
M7i Cooling System Overview
The router cooling system consists of a fan tray, located along the left side of the chassis,
that provides side-to-side cooling (see Figure 17 on page 25). It connects directly to the
router midplane. The fan tray is a single unit containing four individually fault-tolerant
fans. If a single fan fails, the remaining fans continue to function indefinitely.
The fan tray is hot-removable and hot-insertable.
Figure 16: Fan Tray
Power supply is functioning normally, input is occurring, outputs are within range,
and the temperature is within range.
Power supply is not functioning, is starting up, or is not properly inserted, or airflow
is not sufficient.
The cable management system consists of racks that attach vertically to each side of
the chassis at the front. Pass PIC cables through the slots in the racks to keep the cables
organized and securely in place, and to avoid bending optical cables beyond the proper
bend radius. The cable management system evenly distributes the weight of a cable, so
that it is not subjected to undue stress at the connector.
Related
Documentation
• Installing the M7i Cable Management System on page 45
M7i and M10i Packet Forwarding Engine Architecture on page 28
•
Routing Engine Architecture on page 29
System Architecture Overview
The router architecture consists of two major components:
•
Packet Forwarding Engine—Performs Layer 2 and Layer 3 packet switching, route
lookups, and packet forwarding.
•
Routing Engine—Provides Layer 3 routing services and network management.
The Packet Forwarding Engine and the Routing Engine perform independently but
communicate constantly through a 100-Mbps internal link. This arrangement provides
streamlined forwarding and routing control and the ability to run Internet-scale networks
at high speeds. Figure 18 on page 27 illustrates the relationship between the Packet
Forwarding Engine and the Routing Engine.
M7i and M10i Packet Forwarding Engine Architecture
The Packet Forwarding Engineperforms Layer 2 and Layer 3packetswitching. The Packet
Forwarding Engine is implemented in application-specific integrated circuits (ASICs). It
uses a centralized route lookup engine and shared memory.
•
Packet Forwarding Engine Components on page 28
•
Data Flow Through the Packet Forwarding Engine on page 28
Packet Forwarding Engine Components
The Packet Forwarding Engine architecture includes the following components:
•
Midplane—Transports packets, notifications, and other signals between the FPCs and
the Packet Forwarding Engine (as well as other system components).
•
Physical Interface Card (PIC)—Physically connects the router to fiber-optic or digital
network media. A controller ASIC in each PIC performs control functions specific to
the PIC media type.
•
Compact Forwarding Engine Board (CFEB) or Enhanced Compact Forwarding Engine
Board (CFEB-E)—Hosts an integrated ASIC, which makes forwarding decisions,
distributes data cells to the shared memory, and directs data packets when they are
ready for transmission.
Data Flow Through the Packet Forwarding Engine
Use of ASICs promotes efficient movement of data packets through the system. Packets
flow through the Packet Forwarding Engine in the following sequence (see Figure 19 on
page 29):
1. Packets arrive at an incoming networking interface.
2. The networking interface passes the packets to the CFEB or CFEB-E, where the
integrated ASIC processes the packet headers, divides the packets into 64-byte data
cells, and distributes the data cells throughout the memory buffer.
3. The integrated ASIC on the CFEB or CFEB-E performs a route lookup for each packet
and decides how to forward it.
a. If services are configured for the packet, the integrated ASIC reassembles the
packet and passes them to the services interface.
b. The services interface passes the packet to the CFEB or CFEB-E, where the
integrated ASIC processes the packet, divides the packet into 64-byte cells, and
distributes the data cells throughout the memory buffer.
c. The integrated ASIC performs a second route lookup for each packet and decides
how to forward it.
4. The integrated ASIC notifies the outbound networking interface.
5. The integratedASIC reassembles data cells storedin sharedmemory intodata packets
as they are ready for transmission and passes them to the outbound networking
interface.
6. The outbound networking interface transmits the data packets.
Figure 19: Packet Forwarding Engine Components and Data Flow
Related
Documentation
M7i Compact Forwarding Engine Board (CFEB) and Enhanced Compact Forwarding
•
Engine Board (CFEB-E) Description on page 8
• M7i Router Description on page 3
Routing Engine Architecture
The Routing Engine runs the Junos OS, which Juniper Networks has developed and
optimized to handle large numbers of network interfaces and routes. The software
consists of a set of system processes running in protected memory modules on top of
an independent operating system. The Junos kernel supports Junos system processes,
which handle system management processes, routing protocols, and control functions
(see Figure 20 on page 30).
The Routing Engine has a dedicated 100-Mbps internal connection to the Packet
Forwarding Engine.
The Routing Engine handles all routing protocol processes, as well as the software
processes that control the router's interfaces, the chassis components, system
management, and user access to the router. These routing and software processes run
on topof a kernel that interacts withthe Packet ForwardingEngine. For more information
about the processes, see the Junos OS System Basics and Services Command Reference.
The Routing Engine includes the following functions and features:
•
Processing of routing protocol packets—The Routing Engine handles all packets that
concern routing protocols, freeingthe Packet Forwarding Engine to handle only packets
that represent Internet traffic.
•
Softwaremodularity—Becauseeach software process is devoted to a different function
and uses a separate process space, the failure of one process has little or no effect on
the others.
•
In-depth Internet functionality—Each routingprotocolis implemented witha complete
set ofInternet features and provides full flexibilityfor advertising, filtering,and modifying
routes. Routing policies are set according to route parameters (for example, prefix,
prefix lengths, and Border Gateway Protocol [BGP] attributes).
•
Scalability—The Junos routing tables have been designed to hold all the routes in
current networks with ample capacity for expansion. Additionally, the Junos OS can
efficiently support large numbers of interfaces and virtual circuits.
•
Management interface—Different levels of system management tools are provided,
including the Junos OS command-line interface (CLI), the Junos XML management
protocol, the craft interface, and SNMP.
•
Storage andchange management—Configurationfiles, system images, andmicrocode
can be held and maintained in primary and secondary storage systems, permitting
local or remote upgrades.
•
Monitoring efficiency and flexibility—The router supports functions such as alarm
handling and packet counting on every port, without degrading packet-forwarding
performance.
The Routing Engine constructs and maintains one or more routing tables (see Figure 21
on page 31). From the routing tables, the Routing Engine derives a table of active routes,
called the forwarding table, which is then copied into the Packet Forwarding Engine. The
design of the ASICs allow the forwarding table in the Packet Forwarding Engine to be
updated without interrupting forwarding performance.
Figure 21: Control Packet Handling for Routing and Forwarding Table
Updates
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 appears in Figure 22 on
page 37.Table 9 on page 36 summarizes rack requirements and specifications for an M7i
router.
Table 9: Rack Requirements and Specifications for an M7i Router
GuidelinesRack Requirement
Rack type and mounting bracket hole
spacing
Rack size and strength
Use a four-post rack or a two-post rack. You can mount the router on any four-post
or two-post rack that provides bracket holes or hole patterns spaced at 1 U
(1.75-in./4.44-cm) increments and that meets the size and strength requirements
specified in this table.
A U is the standard rack unit defined in Cabinets, Racks, Panels, and AssociatedEquipment (document number EIA-310–D) published by the Electronics Industry
Association (http://www.eia.org).
•
Ensure that the rack is a 19-in. rack as defined in Cabinets, Racks, Panels, and
AssociatedEquipment (document number EIA-310–D) publishedby theElectronics
Industry Association (http://www.eia.org).
•
Ensure that the rack is one of the following standard lengths:
•
23.62 in. (600 mm)
With the use of adaptors, the router can fit into a rack that is 600 mm wide and
600 mm deep as defined in the four-part Equipment Engineering (EE); Europeantelecommunications standard 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 as required.
•
30.0 in. (762 mm)
•
21.5 in. (800 mm)
•
The rack rails must be spaced widely enough to accommodate the router chassis's
externaldimensions: 3.5 in. (8.9cm) high,18 in. (45.7 cm) deep,and 17.5 in.(44.5 cm)
wide. The outeredges of the mounting brackets extendthe width to19 in. (48.2 cm).
The spacing of rails and adjacent racks must also allow for the clearances around
the router and rack that are specified in “M7i Router Clearance Requirements for
Airflow and Hardware Maintenance” on page 38.
•
The chassis height of 3.5 in. (8.9 cm) is approximately 2 U. A U is the standard rack
unit definedin Cabinets, Racks, Panels, and Associated Equipment (documentnumber
EIA-310-D) published by the Electronics Industry Association. You can stack 21 M7i
routers in a rack that has at least 42 U (73.5 in. or 1.87 m) of usable vertical space.
•
The rack must bestrong enough to supportthe weightof the fully configured router,
up to 36.5 lb (16.6 kg). If you stack multiple fully configured routers in one rack, it
must be capable of supporting the combined weight of the routers.
•
Ensure that the spacing of rails and adjacent racks allows for the proper clearance
around the switch and rack as specified in “M7i Router Clearance Requirements for
Airflow and Hardware Maintenance” on page 38.
M7i Router Clearance Requirements for Airflow and Hardware Maintenance
When planning the installation site, you need to allow sufficient clearance around the
rack (see Figure 23 on page 38):
•
For the cooling system of side-cooled routers to function properly, the airflow around
the chassis must be unrestricted. Allow at least 6 in. (15.2 cm) of clearance between
side-cooled routers. Allow 2.8 in. (7 cm) between the side of the chassis and any
non-heat-producing surface such as a wall.
•
For service personnel to remove and install hardware components, there must be
adequate space at the front and back of the router. Allow at least 24 in. (61 cm) both
in front of and behind the chassis. NEBS GR-63 recommends at least 30 in. (76.2 cm)
clearance in front of the chassis.
NOTE: We recommend that you do not install the router in a cabinet. If
mounting the router in a cabinet, you must be sure that ventilation is
sufficient to prevent overheating.
Figure 23: Chassis Dimensions and Clearance Requirements
After you haveprepared your installationsite as described in “M7i Router Site Preparation
Checklist” on page 35, 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 125 and “General Safety Warnings for M Series,
MX Series, and T Series Routers” on page 126.
2. Follow the instructions in “Unpacking the M7i Router” on page 41 and “Verifying the
M7i Router Parts Received” on page 42.
3. Install the cable management system as described in “Installing the M7i Cable
Management System” on page 45.
Related
Documentation
4. If you are center-mounting the router, move the mounting brackets as described in
“Moving the Mounting Brackets” on page 46.
5. Install the router as described in “Installing the M7i Router Into the Rack” on page 47.
6. Connect the grounding cable as described in “Connecting the Grounding Cable to the
M7i Router” on page 51.
7. Connect cables to external devices as described in “Connecting the M7i Router to
Management and Alarm Devices” on page 53.
8. Connect the AC power cords as described in “Connecting Power to an AC-Powered
M7i Router” on page 57 or DC power cables “Connecting Power to a DC-Powered
Router” on page 57.
9. Power on the router as described in “Powering on the M7i Router” on page 59.
10. Perform the initial system startup as described in“Initially Configuringthe M7i Router”
on page 63.
• Connecting the M7i Router to a Management Console or Auxiliary Device on page 54
• Connecting the M7i Router to a Network for Out-of-Band Management on page 54
Tools and Parts Required to Unpack the M7i Router on page 41
•
Unpacking the M7i Router on page 41
•
Verifying the M7i Router Parts Received on page 42
Tools and Parts Required to Unpack the M7i 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
Documentation
M7i Router Description on page 3•
• M7i Chassis Description on page 6
• M7i Chassis Lifting Guidelines on page 131
Unpacking the M7i Router
The router is shipped in a cardboard carton, secured with foam packing material. The
carton also contains an accessory box and the M7i Internet Router Installation Quick
Start.
To unpack the router, perform these steps (see Figure 24 on page 42):
1. Move the shipping carton to a staging area as close to the installation site as possible,
but where you have enough room to remove the system components.
2. Position the carton so that the arrows are pointing up.
NOTE: The router is maximally protected inside the shipping carton. Do not
unpack it until you are ready to begin installation.
4. Remove the accessory box and verify the contents against the parts inventory on the
label attached to the carton.
5. Pull out the packing material holding the router in place.
6. Verify the chassis components received against the packing list included with the
router. A generic parts inventory appears in Table 10 on page 43.
7. Save the shipping crate, packing materials, and pallet in case you later need to move
or ship the router.
Figure 24: Unpacking the Router
Related
Documentation
M7i Router Description on page 3•
• M7i Router Physical Specifications on page 159
• M7i Router Rack Requirements on page 36
Verifying the M7i 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 10 on page 43, and an accessory box, which contains the parts listed in Table 11 on
page 43. The parts shipped with your router can vary depending on the configuration you
ordered.
Table 10: Generic Inventory of Router Components Installed in the M7i
Chassis
QuantityComponent
Up to 4PIC
FIC
Table 11: Accessory Box Parts List
self-tapping
1 (2-port Fast Ethernet or 1-port Gigabit
Ethernet)
1Routing Engine
1Midplane
1CFEB or CFEB-E
1Fan tray
1 or 2Power supply
2Mounting brackets
Depends on router configurationBlank panels for slots without components
QuantityPart
4Screws, Screw, Pan hd, Phil, 12-24 x 1/2", self-tapping
4Screws, Flat Hd, Phil, 5 x 10.5mm Long, 1.6mm Pitch,
vinyl insulated
strain relieved, for DC power cables
2Terminal lugs, 16-AWG to 14-AWG, #6 stud, ring terminal,
9 (2 per power supply)Terminal fork lugs, 14-AWG, #6, 0.25 Wide, insulation
2Terminal lugs, 14-AWG, #8 stud, ring tongue, insulated
For anopen-frame rack, center-mountingis preferable,because themore even distribution
of weight provides greater stability. The router is shipped with the mounting brackets
already installed for front-mounting, as shown in Figure 1 on page 6.
To move the mounting brackets before center-mounting the router:
1. Move the mounting brackets to the center of the chassis.
2. Secure the mounting brackets to the chassis by installing screws along both the front
and rear of the brackets.
Related
Documentation
• Installation Safety Warnings for M Series, MX Series, and T Series Routers on page 131
• Installing the M7i Router Into the Rack on page 47
Tools and Parts Required to Install the M7i Router Into a Rack on page 47
•
Installing the M7i Router Into the Rack on page 47
Tools and Parts Required to Install the M7i Router Into a Rack
To install the chassis into a rack, you need the following tools and parts:
•
Phillips (+) screwdriver, number 2
Related
Documentation
Initially Configuring the M7i Router on page 63•
• M7i Chassis Description on page 6
• M7i Chassis Lifting Guidelines on page 131
Installing the M7i Router Into the Rack
CAUTION: Depending on configuration, the chassis weighs between 28.2 lb
(12.8 kg) and 36.5 lb (16.6 kg). Installing it into the rack requires at least one
person to lift and another person to secure the mounting screws.
First, perform the following prerequisite procedures:
•
Verify that the router site meets the requirements described in “M7i Router Site
Preparation Checklist” on page 35.
•
Place the rack in its permanent location, allowing adequate clearance for airflow and
maintenance, and secure it to the building structure. For details, see “M7i Router Rack
Requirements” on page 36.
•
Readthe information in “General Safety Guidelines for M Series, MX Series, and T Series
Routers”on page 125 and“General Safety Warnings for M Series, MX Series, and T Series
Routers” on page 126.
After installing the router into the rack as described in “Installing the M7i Router Into the
Rack” on page 47, complete the installation by performing the procedures described in
the following topics:
•
Tools and Parts Required for M7i Router Connections on page 53
•
Connecting the M7i Router to Management and Alarm Devices on page 53
•
Inserting an SFP into the 1-port Gigabit Ethernet FIC on page 55
•
Connecting FIC and PIC Cables to the M7i Router on page 55
Tools and Parts Required for M7i Router Connections
To connect the router to management devices and PICs and to power on the router, you
need the following tools and parts:
Connecting the M7i Router to a Network for Out-of-Band Management
To connect the Routing Engine to a network for out-of-band management, insert an
Ethernet cable with RJ-45/RJ-45 connectors into the MGMT port on the Routing Engine.
One such cable is provided with therouter (see “Routing Engine Interface Cable and Wire
Specifications for the M7i Router” on page 179). Follow this procedure:
1. Plug one end of the Ethernet cable (Figure 27 on page 54 shows the connector) into
the MGMT port on the Routing EngineFigure 28 on page 54 shows the layout of the
ports on the Routing Engine.
2. Plug the other end of the cable into the network device.
Connecting the M7i Router to a Management Console or Auxiliary Device
To use a system console to configure and manage the Routing Engine, connect it to the
CONSOLE port on the Routing Engine. To use a laptop, modem, or other auxiliary device,
connect it to the AUX/MODEM port on the Routing Engine. Both ports accept an RS-232
(EIA-232) serial cable with DB-9/DB-9 connectors. One such cable is provided with the
router. If you want to connect a device to both ports, you must supply another cable. See
“Routing Engine Interface Cable and Wire Specifications for the M7i Router” on page 179.
To connect a management console or auxiliary device:
1. Turn off the power to the console or auxiliary device.
2. Plug the female end (shown in Figure 29 on page 54) of the provided console cable
into the CONSOLE or AUX/MODEM port. “Connecting the M7i Router to a Network for
Out-of-Band Management” on page 54 shows the layout of the ports on the Routing
Engine.
3. Tighten the screws on the connector.
Figure 29: Console and Auxiliary Serial Port Connector
Related
Documentation
Routing Engine Interface Cable and Wire Specifications for the M7i Router on page 179.•
Chapter 10: Connecting the M7i Router to External Devices
• M7i Router Site Preparation Checklist on page 35
• Initially Configuring the M7i Router on page 63
• Connecting Power to an AC-Powered M7i Router on page 57
• Connecting Power to a DC-Powered Router on page 57
Inserting an SFP into the 1-port Gigabit Ethernet FIC
Before inserting cables into the 1-port Gigabit Ethernet FIC, you must install a small
form-factor pluggable (SFP). Small form-factor pluggable (SFP) optical transceiver
modules provide support for SX, LX, and LH optics.
To install an SFP into the FIC, follow this procedure:
1. Verify that each SFP has a rubber safety cap covering the optical transceiver. If it does
not, cover the transceiver with a safety cap.
2. Carefully align the SFP with the slot in the FIC. The connector should face down.
3. Slide the SFP until the connector is seated in the FIC slot. If you are unable to fully
insert the SFP, make sure the connector is facing the proper direction.
Related
Documentation
Installing an SFP into an M7i Router on page 96•
• Replacing an SFP on an M7i Router on page 94
Connecting FIC and PIC Cables to the M7i Router
WARNING: Do not look directlyinto transceivers or into the ends of fiber-optic
cables connected to a transceiver. Fiber-optic transceivers emit laser light
that can damage your eyes.
CAUTION: When handling fiber-optic transceivers and fiber-optic cable,
observe the following precautions:
•
Do not leave a fiber-optic transceiver uncovered except when inserting or
removing cable. The safety cap keeps the port clean and prevents
accidental exposure to laser light.
•
Do not bend fiber-optic cable beyond its minimum bend radius. An arc
smaller than a few inches in diameter can damage the cable and cause
problems that are difficult to diagnose.
•
Do not let fiber-optic cable hang free from the connector. Do not allow
fastenedloopsof cableto dangle,which stressesthe cableatthe fastening
point.
Plug network cables into the FIC and the PICs housed in the router.
To connect cables into the cable connector ports in the FIC or a PIC faceplate (see Figure
30 on page 56, which shows a fiber-optic PIC):
1. Have ready a length of the type of cable used by the FIC or PIC, as specified in “FIC
Specifications for the M7i Router” on page 173 or the M7i Multiservice Edge Router PICGuide.
2. If the cable connector port is covered by a rubber safety plug, remove the plug.
3. Insert the cable connector into the cable connector port on the FIC or PIC faceplate.
4. Arrange the cable to prevent it from dislodging or developing stress points. Secure
the cable so that it is not supporting its own weight as it hangs to the floor. Place
excesscable out of the wayin a neatly coiled loop.Placing fasteners on the loop helps
to maintain its shape.
Figure 30: Attaching the Cable to a PIC
Related
Documentation
• Fiber-Optic and Network Cable Specifications for the M7i Router on page 174
• M7i Fixed Interface Card (FIC) Description on page 15
• M7i Flexible PIC Concentrators (FPCs) Description on page 18
the strap to one of the ESD points on the chassis.
3. Verify that the switch on each power supply faceplate is in the OFF (O) position.
4. For each power supply, insert the appliance coupler end of a power cord into the
appliance inlet on a power supply faceplate and insert the plug into an AC power
source receptacle. Verify that the power cord does not block access to router
components or drape where people could trip on it.
Related
Documentation
Preventing Electrostatic Discharge Damage to an M7i Router on page 128•
• Removing an M7i AC Power Cord on page 110
• M7i AC Power Electrical Safety Guidelines and Warnings on page 149
• M7i AC Power Supply on page 22
• M7i Router AC Power Supply Specifications on page 166
Connecting Power to a DC-Powered Router
Connect DC power to the router by inserting power cables into the field-wiring terminals
on the faceplate of each power supply. Power cables are not supplied with the router.
For information about the required cable type, see .
To connect DC power to the router (see Figure 31 on page 59):
1. Verify that there is no power flowing from either external power source, so that the
voltage across the leads of the power cables is 0 V. Ensure that there is no chance
that the cable leads might become active during the procedure.
NOTE: The router must be connected to at least two separate external DC
power sources.
CAUTION: There is no standard color coding for DC power cables. The color
coding used by the external DC power source at your site determines the
color coding for the leads on the power cables that attach to the terminal
studs on each power supply. You must ensure that power connections
maintain the proper polarity. The power source cables might be labeled (+)
and (–) to indicate their polarity.
2. Verify that a licensed electrician has attached a listed power cable lug to each power
source cable.
3. Loop the power cables through the hook located on the faceplate to the right of the
field-wiring terminals.
4. Depending on the type of power cable lugs used, loosen or remove the screws on the
field-wiring terminals.
5. Insert thepower cable lugs intothe appropriate field-wiring terminals.Using a number
1 Phillips screwdriver, turn the screw on each field-wiring terminal clockwise to secure
the power cable lug. Apply between 8 lb-in. (.9 Nm) and 9 lb-in. (1.02 Nm) of torque
to each screw.
a. Insert the positive (+) source cable into the return terminal, which is labeled RTN.
b. Insert the negative (–) source cable into the input terminal, which is labeled –48V.
6. Verify that the DC source power cabling and the grounding cabling are correct, that
they are not touching or blocking access to router components, and that they do not
drape where people could trip on them.
• M7i DC Power Electrical Safety Guidelines on page 149
• M7i DC Power Supply on page 23
• M7i Router DC Power Supply Specifications on page 170
Powering on the M7i Router
To power on the router:
1. Verify that the power supplies are fully inserted in the chassis and the thumbscrews
on their faceplates are tightened.
2. For each power supply on an AC-powered router, verify that the ends of the power
cord are firmly plugged into the appliance inlet on the power supply faceplate and
the external power source receptacle.
For each power supply ona DC-powered router,verify that thesource DC powercables
are connected tothe appropriateterminal on the power supply faceplate: the positive
(+) source cable to the return terminal (labeled RTN) and the negative (–) source
cable to the input terminal (labeled –48V).
3. Verify that an external management device is connected to oneof the Routing Engine
ports onthe Routing Engine (AUX/MODEM, CONSOLE, or MGMT). For more information
on connecting management devices, see “Connecting the M7iRouter to Management
and Alarm Devices” on page 53.
4. Turn on the power to the external management device.
5. Press the power switch for one power supply to the ON ( | ) position. On both AC and
DC power supplies, the switch is located on the power supply faceplate.
7. Press the power switch for the second power supply to the ON ( | ) position and verify
that the OUTPUT OK LED lights steadily. If the LED does not light after 60 seconds,
verify that the power supply is properly inserted into the chassis and repeat the cable
installationprocedures described in “Connecting Power to an AC-PoweredM7i Router”
on page 57 or “Connecting Power to a DC-Powered Router” on page 57.
NOTE: After powering off a powersupply, wait at least60 seconds before
turning it back on. After powering on a power supply, wait at least 60
seconds before turning it off.
If the router is completely powered off when you power on the power
supply, the Routing Engine bootsas the power supplycompletesits startup
sequence. If the Routing Engine finishes booting and you need to power
off the router again, see “Powering Off the M7i Router” on page 60.
Aftera powersupply is poweredon, it can take upto 60 secondsfor status
indicators—such as the output status LED on the power supply, the
command display output, and messages on the LED display on the craft
interface—to indicatethat thepower supplyis functioning normally. Ignore
error indicators that appear during the first 60 seconds.
8. On the external management device connected to the Routing Engine, monitor the
startup process to verify that the system has booted properly.
Related
Documentation
Troubleshooting the M7i Power System When the LED on One M7i Power Supply Is Off
•
on page 81
• Troubleshooting the M7i Power System When the LEDs on All M7i Power Supplies Are
Blinking or Off on page 81
• General Electrical Safety Guidelines and Electrical Codes for M Series, MX Series, and
T Series Routers on page 148
Powering Off the M7i Router
To power off the router:
1. Onthe console or other managementdevice connected to the master Routing Engine,
enter CLI operational mode and issuethe following commandto shutdown therouter
software.(If two Routing Enginesare installed, also issuethe commandon thebackup
Routing Engine.)
user@host> request system halt
NOTE: Wait until a message appears on the console confirming that the
operating system has halted.
The router is shipped with the Junos OS preinstalled and ready to be configured when
the router is powered on.
The default bootorder forthe M7i Multiservice EdgeRouter is different from other Juniper
Networks routers, because the default configuration of the Routing Engine on the M7i
router does not include an CompactFlash card.
If the Routing Engine does not have an CompactFlash card, two copies of the Junos OS
are preinstalled on the router: one on a PC card that can be inserted into the slot in the
Routing Engine faceplate, and one on a rotating hard disk in the Routing Engine. When
the router boots, it first attempts to access the software image on the PC card. If a PC
card isnot inserted into the Routing Engine or the attempt otherwise fails, the router tries
the hard disk.
If the Routing Engine has an CompactFlash card, three copies of the Junos OS are
preinstalled on the router and the boot order is as follows. The router first attempts to
access the image on the PC card. If a PC card is not inserted into the Routing Engine or
the attempt otherwise fails, the router next tries the CompactFlash card, and finally the
hard disk.
You configure the router by issuing Junos OS command-line interface (CLI) commands,
either on a console device attached to the CONSOLE port on the Routing Engine, or over
a telnet connection to a network connected to the MGMT port on the Routing Engine.
Gather the following information before configuring the router:
•
Name the router will use on the network
•
Domain name the router will use
•
IP address and prefix length information for the Ethernet interface
This procedure connects the router to the network but does not enable it to forward
traffic. For complete information about enabling the router to forward traffic, including
examples, see the Junos OS configuration guides.
To configure the software:
1. Verify that the router is powered on as described in “Powering on the M7i Router” on
page 59.
2. Log in as the “root” user. There is no password.
3. Start the CLI.
root# cli
root@>
4. Enter configuration mode.
cli> configure
[edit]
root@#
5. Configure the name of the router. If the name includes spaces, enclose the name in
quotation marks (“ ”).
[edit]
root@# set system host-name host-name
6. Configure the router’s domain name.
[edit]
root@# set system domain-name domain-name
7. Configure the IP address and prefix length for the router’s Ethernet interface.
[edit]
root@# set interfaces fxp0 unit 0 family inet address address/prefix-length
8. Configure the IP address of a DNS server.
[edit]
root@# set system name-server address
9. Set the root authentication password by entering either a clear-text password, an
encrypted password, or an SSH public key string (DSA or RSA).
[edit]
root@# set system root-authentication plain-text-password
New password: password
Retype new password: password
or
[edit]
root@# set system root-authentication encrypted-password encrypted-password
or
[edit]
root@# set system root-authentication ssh-dsa public-key
11. Commit the configuration to activate it on the router.
[edit]
root@# commit
12. Optionally, configure additional properties by adding the necessary configuration
statements. Then commit the changes to activate them on the router.
[edit]
root@host# commit
13. When you have finished configuring the router, exit configuration mode.
[edit]
root@host# exit
root@host>
NOTE: To reinstall the Junos OS, you boot the router from the removable
media. Do not insert the removable media during normal operations. The
routerdoes not operate normallywhen it is booted fromthe removable media.
When therouter boots from the storage media(removablemedia, internalCompactFlash
card, or hard disk) it expands its search in the /config directory of the routing platform
for the following files in the following order: juniper.conf (the main configuration file),
rescue.conf (the rescue configuration file), and juniper.conf.1 (the first rollback
configuration file). When the search finds the first configuration file that can be loaded
properly, the file loads and the search ends. If none of the file can be loaded properly,
the routing platform does not function properly. If the router boots from an alternate
boot device, theJunos OSdisplays a message indicationthis whenyou log in to therouter.
This chapter describes how to maintain hardware components installed in the router.
For information about returning a part to Juniper Networks for repair or replacement, see
“Contacting Customer Support and Returning M7i Hardware” on page 187.
•
Routine Maintenance Procedures for the M7i Router on page 69
•
Maintaining the M7i CFEB and CFEB-E on page 69
•
Maintaining the M7i FIC and FIC Cables and PICs and PIC Cables on page 70
see “M7iCompactForwarding EngineBoard (CFEB) and Enhanced Compact Forwarding
Engine Board (CFEB-E) Description” on page 8.
• Issue the CLI show chassis cfeb command to check the status of the CFEB (first output
example) or the CFEB-E (second output example):
user@host> show chassis cfeb
CFEB status:
State Online
Intake Temperature 27 degrees C / 80 degrees F
Exhaust Temperature 33 degrees C / 91 degrees F
CPU utilization 3 percent
Interrupt utilization 0 percent
Heap utilization 8 percent
Buffer utilization 21 percent
Total CPU DRAM 128 MB
Internet Processor II Version 1, Foundry IBM, Part number 164
Start time: 2003-06-11 11:41:22 PDT
Uptime: 1 hour, 39 minutes, 31 seconds
user@host> show chassis cfeb
CFEB—E status:
State Online
Intake Temperature 27 degrees C / 80 degrees F
Exhaust Temperature 33 degrees C / 91 degrees F
CPU utilization 3 percent
Interrupt utilization 0 percent
Heap utilization 8 percent
Buffer utilization 21 percent
Total CPU DRAM 128 MB
Internet Processor II Version 1, Foundry IBM, Part number 164
Start time: 2003-06-11 11:41:22 PDT
Uptime: 1 hour, 39 minutes, 31 seconds
For further description of the output from the command, see the Junos OS System
Basics and Services Command Reference.
Related
Documentation
Replacing, Upgrading, and Downgrading the M7i CFEB and CFEB-E on page 86•
• Installing the M7i CFEB and CFEB-E on page 88
• Troubleshooting the M7i CFEB and CFEB-E on page 80
Maintaining the M7i FIC and FIC Cables and PICs and PIC Cables
PurposeFor optimum performance, verify the condition of the FIC and FIC cables and PICs and
PIC cables.
Action• Check the LEDs on the FIC faceplate. The Fast Ethernet and Gigabit Ethernet ports on
the FIC have LEDs that display the status of the ports. For more information, see “M7i
Fixed Interface Card (FIC) Description” on page 15.
• Check the LEDs on PIC faceplates. Most PIC faceplates have an LED labeled STATUS.
Some PICs have additional LEDs, often one per port. The meaning of the LED states
differs for various PICs. For more information, see the M7i Multiservice Edge Router PICGuide.
• Issue the CLI show chassis fpc pic-status command. The following example specifies
an FPC slot number (0), which is optional.
user@host> show chassis fpc pic-status 0
Slot 0 Online
PIC 0 2x OC-3 ATM, MM
PIC 1 2x CT3-NxDS0
PIC 2 2x OC-3 ATM, MM
For further description of the output from the command, see the Junos OS System
Basics and Services Command Reference.
• Support cables to prevent them from dislodging or developing stress points.
• Place excess cable out of the way, using the cable management system on the rack.
Do not allow fastened loops of cable to dangle from the ladder rack because this
stresses the cableat thefastening point. Putting fasteners on the loops help to maintain
their shape.
• Keep the cableconnections clean andfree ofdust and other particles,which cancause
drops in the received power level. Always inspect cables and clean them if necessary
before connecting an interface.
• Label all interface cables to identify them, labeling each end of the cable the same.
The following guidelines apply specifically to fiber-optic cable:
• When you unplug a fiber-optic cable from a FIC or PIC, always place a rubber safety
plug over the transceiver on the FIC or PIC faceplate and on the end of the cable.
• Anchor fiber-optic cable to avoid stress on the connectors. When attaching fiber to an
interface, be sure to secure the fiber so it is not supporting its own weight as it hangs
to the floor. Never let fiber-optic cable hang free from the connector.
• Avoid bending fiber-optic cable beyond its bend radius. An arc smaller than a few
inches can damage the cable and cause problems that are difficult to diagnose.
• Frequent plugging and unplugging of fiber-optic cable into and out of optical
instruments, such as ATM or SONET/SDH analyzers, can cause damage to the
instruments that is expensive to repair. Instead, attach a short fiber extension to the
optical equipment. Any wear and tear due to frequent plugging and unplugging is then
absorbed by the short fiber extension, which is easy and inexpensive to replace.
• Keep fiber-optic cable connections clean. Small micro-deposits of oil and dust in the
canal of the transceiver or cable connector can cause loss of light, reducing signal
power and possibly causing intermittent problems with the optical connection.
To clean the transceivers, use an appropriate fiber-cleaning device, such as RIFOCS
945/946 Fiber Optic Connector Cleaning System. Follow the directions for the cleaning
kit you use.
After you have cleaned the transceiver on the fiber-optic interface, make sure that the
connector tip of the fiber-optic cable is clean. Use only an approved alcohol-free
Action• Check that the green OUTPUT OK LED is lit on the faceplate of both power supplies.
For more information about the LED, see “M7i Power Supply LEDs” on page 24.
• Issue the following CLI command to check the status of the power supplies. As shown
in thesample output,the value OK in the Status column indicates that the power supply
is operating normally:
user@host> show chassis environment
Class Item Status Measurement
Power Power Supply 0 OK
Power Supply 1 OK
Temp Intake OK 24 degrees C / 75 degrees F
PICs OK 27 degrees C / 80 degrees F
Power Supplies OK 27 degrees C / 80 degrees F
CFEB Intake OK 27 degrees C / 80 degrees F
CFEB Exhaust OK 33 degrees C / 91 degrees F
Routing Engine OK 26 degrees C / 78 degrees F
Fans Left Fan Tray Present
Left Tray front fan OK Spinning at normal speed
Left Tray second fan OK Spinning at normal speed
Left Tray third fan OK Spinning at normal speed
Left Tray fourth fan OK Spinning at normal speed
Related
Documentation
For further description of the output from the command, see the Junos OS System
Basics and Services Command Reference.
• Check the red and yellow alarm LEDs on the FIC. Power supply failure or removal
triggers an alarm that causes one or both of the LEDs to light. You can display the
associated error messages by issuing the following CLI command:
user@host> show chassis alarms
For a list of possible alarm messages, see “Hardware and Interface Alarm Messages”
on page 76.
• Verify that the power source has the proper current rating and that each power supply
is connected to a separate power source.
• Verify that the cable or cord connecting the power supply to the external power source
is securely in place and that there is no moisture accumulating near the router.
• Verify that the cable or cord from the power source to the router is not damaged. If the
insulation is cracked or broken, replace the cable or cord immediately.
• Verify that the power cables or cord do not touch or obstruct access to other router
components, and that they do not drape where people could trip on them.
• Verify that the air flow in and out of cooling system components is not obstructed.
M7i Power System Description on page 21•
• M7i Router Power Requirements on page 163
• Troubleshooting the M7i Power System When the LED on One M7i Power Supply Is Off
• Troubleshooting the M7i Power System When the LEDs on All M7i Power Supplies Are
Blinking or Off on page 81
Maintaining the M7i Cooling System
PurposeFor optimum cooling, verify the condition of the fans.
ActionThe router has a single fan tray that installs into the back of the chassis, as shown in
Figure 2 on page 6.
To check the status of the fans in the fan tray, issue the show chassis environment
command. The output includes an entry for each fan in the fan tray:
user@host> show chassis environment
Class Item Status Measurement
Power Power Supply 0 OK
Power Supply 1 OK
Temp Intake OK 24 degrees C / 75 degrees F
PICs OK 27 degrees C / 80 degrees F
Power Supplies OK 27 degrees C / 80 degrees F
CFEB Intake OK 27 degrees C / 80 degrees F
CFEB Exhaust OK 33 degrees C / 91 degrees F
Routing Engine OK 26 degrees C / 78 degrees F
Fans Left Fan Tray Present
Left Tray front fan OK Spinning at normal speed
Left Tray second fan OK Spinning at normal speed
Left Tray third fan OK Spinning at normal speed
Left Tray fourth fan OK Spinning at normal speed
Related
Documentation
For further description of the output from the command, see the Junos OS System Basics
and Services Command Reference.