Juniper M10i Hardware Guide

M10i System Redundancy on page 4

•

•

M10i System Architecture Overview on page 4

•

M10i Packet Forwarding Engine Architecture Overview on page 5

•

M10i Routing Engine Architecture Overview on page 7

M10i Router Description

The M10i Multiservice Edge Router provides high-speed interfaces for medium and large networks and network applications, such as those supported by Internet service providers

(ISPs). 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.

The M10i router supports up to eight Physical Interface Cards (PICs). The router height of 8.7 in. (22.1 cm) enables stacked installation of five M10i routers in a single floor-to-ceiling rack, for increased port density per unit of floor space.

The router’s maximum aggregate throughput is 12.8 gigabits per second (Gbps) simplex or 6.4 Gbps full duplex. Inserting a combination of PICs with an aggregate higher than the maximum throughput per FPC is supported, but constitutes oversubscription of the

FPC.

The router architecture cleanly separates control operations from packet forwarding operations, which helps to eliminate processing and traffic bottlenecks. 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.

Forwarding operations in the router are performed by the Packet Forwarding Engine, which consists of hardware, including ASICs, designed by Juniper Networks.

Documentation

•

M10i System Redundancy on page 4

•

•

•

M10i Multiservice Edge Router Hardware Guide

M10i System Redundancy

You can configure the router for system redundancy by using three AC or four DC load-sharing, fully-redundant power supplies to distribute power to the other components.

AC System Redundancy

AC system redundancy requires three independent AC power outlets. If one power supply fails, the other two power supplies provide full power to the router's components indefinitely.

You can set up increased AC system redundancy by using four AC power supplies. In this case, two power supplies are powered from two AC outlets, and the other two power supplies use two AC outlets from a UPS battery-backed power source. This lets the router run during AC power outages for the amount of time that the UPS allows.

DC System Redundancy

DC system redundancy requires two power sources from feed A and two power sources from feed B. If one feed fails or is shut down for service, the other feed powers two DC power supplies and can provide full power to the router's components indefinitely.

Documentation

•

•

•

M10i 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 1 on page 5

illustrates the relationship between the Packet

Forwarding Engine and the Routing Engine.

Chapter 1: System Overview and Architecture

Figure 1: System Architecture

Documentation

•

M10i Midplane Description on page 12

•

•

M10i Compact Forwarding Engine Board (CFEB) and Enhanced Compact Forwarding

M10i Packet Forwarding Engine Architecture Overview

The Packet Forwarding Engine performs Layer 2 and Layer 3 packet switching. It can forward up to 15 million packets per second (Mpps) for all packet sizes. The aggregate throughput is 4 gigabits per second (Gbps) full duplex per FPC (8 Gbps full-duplex total throughput rate). The Packet Forwarding Engine is implemented in application-specific integrated circuits (ASICs). It uses a centralized route lookup engine and shared memory.

The Packet Forwarding Engine architecture includes the following components:

• Midplane—Transports packets, notifications, and other signals between the PICs 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 2 on page 6

Packets arrive at an incoming networking interface.

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.

M10i Multiservice Edge Router Hardware Guide

The integrated ASIC on the CFEB or CFEB-E performs a route lookup for each packet and decides how to forward it.

If services are configured for the packet, the integrated ASIC reassembles the packet and passes them to the services interface.

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.

The integrated ASIC performs a second route lookup for each packet and decides how to forward it.

The integrated ASIC notifies the outbound networking interface.

The integrated ASIC reassembles data cells stored in shared memory into data packets as they are ready for transmission and passes them to the outbound networking interface.

The outbound networking interface transmits the data packets.

Figure 2: Packet Forwarding Engine Components and Data Flow

Documentation

•

Engine Board (CFEB-E) Description on page 67

•

•

Chapter 1: System Overview and Architecture

M10i Routing Engine Architecture Overview

The Routing Engine is an Intel-based PCI platform running 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 3 on page 7 ).

The Routing Engine has a dedicated 100-Mbps internal connection to the Packet

Forwarding Engine.

Figure 3: Routing Engine Architecture

Routing Engine Functions

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 top of a kernel that interacts with the Packet Forwarding Engine. For more information about the processes, see the CLI Explorer .

The Routing Engine includes the following functions and features:

• Processing of routing protocol packets—The Routing Engine handles all packets that concern routing protocols, freeing the Packet Forwarding Engine to handle only packets that represent Internet traffic.

• Software modularity—Because each 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 routing protocol is implemented with a complete set of Internet features and provides full flexibility for advertising, filtering, and modifying routes. Routing policies are set according to route parameters (for example, prefix, prefix lengths, and Border Gateway Protocol [BGP] attributes).

M10i Multiservice Edge Router Hardware Guide

• 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 and change management—Configuration files, system images, and microcode 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 4 on page 8

). 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 4: Control Packet Handling for Routing and Forwarding Table Updates

Documentation

•

Maintaining the M10i Routing Engine on page 222

•

•

Outstanding Issues with the M10i Router on page 9

CHAPTER 2

M10i Router Release Notes

•

•

Errata with the M10i Router Documentation on page 9

Outstanding Issues with the M10i Router

This section lists outstanding issues with the documentation.

• The default configuration of the Routing Engine does not include an CompactFlash card, which affects which media are available to the Routing Engine as it accesses the

Junos operating system (Junos OS) at boot time. For more information about the

Routing Engine’s use of boot media, see “Installation Overview” in the Junos OS

Administration Library .

• The long haul (LH) small form-factor pluggable transceiver (SFP) conforms to Class

A emissions standards on the M10i router when it is installed in the 1-port Gigabit

Ethernet SFP Physical Interface Card (PIC).

Documentation

•

Errata with the M10i Router Documentation on page 9

•

Outstanding Issues with the M10i Router on page 9

Errata with the M10i Router Documentation

There are currently no outstanding issues for the M10i router documentation.

Documentation

•

M10i Multiservice Edge Router Hardware Guide

CHAPTER 3

Chassis Components and Descriptions

•

M10i Midplane Description on page 12

•

•

M10i Cable Management System Description on page 13

•

M10i High-Availability Chassis Manager (HCM) Description on page 14

•

M10i HCM LEDs on page 16

•

M10i HCM Alarm LEDs on page 16

M10i Chassis Description

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 8.7 in. (22.1 cm) enables stacked installation of eight M10i routers in a single floor-to-ceiling rack. For more information, see

“Installation Safety Warnings for Juniper

Networks Devices” on page 269

The two mounting brackets (one on each side) extend the chassis width to 19 in.

(48.3 cm).

Figure 5 on page 11

and

“Displaying M10i Router Components and

show front and rear views of the router chassis.

Figure 5: Front of Chassis

M10i Multiservice Edge Router Hardware Guide

Figure 6: Rear of Chassis

Engine Boards

Grounding points optional feature optional feature

P/S 3

P/S 2

C-FEB 0

C-FEB 1

P/S 1

P/S 0

NOTE: A MINIMUM

BE PRESENT

TWO POWER

FOR NORMAL

TION.

MUST

Primary fan tray

Power supplies Redundant fan tray

The chassis includes an electrostatic discharge (ESD) point (banana plug receptacle) to protect electronic components from damage due to static electricity, at the front of the chassis, as shown in

Figure 5 on page 11

WARNING: Before removing 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 chassis serial number information , see

Serial Numbers” on page 247 .

Documentation

•

M10i System Redundancy on page 4

•

•

Figure 7 on page 13 ). All router components

M10i Midplane Description

The midplane is a panel located in the center of the chassis, running from side to side and forming the rear of the PIC card cage (see

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—After being processed by a PIC, an incoming data packet crosses the midplane to the CFEB or the CFEB-E. The CFEB or CFEB-E performs switching and

Chapter 3: Chassis Components and Descriptions forwarding functions and transfers outgoing packets back across the midplane to the

PICs for transmission to the network.

• Power distribution—The midplane distributes power to all router components from the power supplies attached to it. It also provides hot-plug protection for the PIC and

HCM slots.

• Signal connectivity—The midplane transports the signals exchanged by system components for monitoring and control purposes.

Figure 7: Midplane

For chassis serial number information , see

“Displaying M10i Router Components and

Serial Numbers” on page 247 .

Documentation

•

•

General Electrical Safety Warnings for Juniper Networks Devices on page 287

•

M10i Cable Management System Description

The cable management system consists of racks that attach vertically to each side of the chassis at the front, as shown in

Figure 8 on page 14 . 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.

M10i Multiservice Edge Router Hardware Guide

Figure 8: Cable Management System

Documentation

•

Installing the M10i Cable Management System on page 141

•

•

“M10i Routing Engine Description” on page 21

M10i High-Availability Chassis Manager (HCM) Description

The High-Availability Chassis Manager (HCM) works with its companion Routing Engine to provide control and monitoring functions for router components. The HCM also displays alarm status and takes PICs online and offline.

Two HCMs are installed into the midplane from the front of the chassis, as shown in

Figure 5 on page 11

. The master HCM performs all functions and provides PIC removal buttons for the first FPC. The backup HCM provides PIC removal buttons for the second

FPC. The HCM in the slot labeled HCM0 is paired with the Routing Engine in the slot labeled RE0 . Likewise, the HCM in the slot labeled HCM1 is paired with the Routing Engine in the slot labeled RE1 . By default, the HCM in the slot labeled HCM0 is the master.

NOTE: When HCM mastership changes because of failure, Routing Engine mastership will change as well. For a description of Routing Engine mastership, see

The HCM performs the following functions:

• Monitoring and control of router components—The HCM collects statistics from all sensors in the system. When it detects a failure or alarm condition, it sends a signal to the Routing Engine, which generates control messages or sets an alarm. The HCM also relays control messages from the Routing Engine to the router components.

• Controlling component power-up and power-down—The HCM controls the power-up sequence of router components as they start and powers down components when their offline buttons are pressed.

Chapter 3: Chassis Components and Descriptions

• Signaling of mastership—In a router with more than one Routing Engine, the HCM signals to all router components which Routing Engine is the master and which is the standby.

• Alarm display—If an alarm exists, the HCM displays the alarm condition. For more information, see

“M10i HCM Alarm LEDs” on page 16 .

• PIC removal—If a PIC offline button is pressed, the HCM relays the request to the CFEB or CFEB-E, which takes the PIC offline and informs the Routing Engine. Other PICs are unaffected, and system operation continues. For more information, see

“M10i HCM

LEDs” on page 16

Figure 9: M10i High-Availability Chassis Manager

Each HCM (shown in

Figure 9 on page 15 ) has the following components:

• 100-Mbps Fast Ethernet switch—Carries signals and monitoring data between router components.

• Two LEDs—Indicate HCM status. There is a green one labeled PWR and an blue one labeled MSTR .

“M10i HCM LEDs” on page 16

describes the LED states.

• Alarm LEDs—Display alarm conditions, if any exist.

• PIC offline buttons—Relays a request to the CFEB or CFEB-E, which prepares a PIC for removal from the router, or brings the PIC online when it is replaced.

Offline buttons for one row of PICs are located on each HCM (see

Figure 9 on page 15 ).

Pressing the button relays a request to the CFEB or CFEB-E, which prepares the PIC for removal from the router, or brings it online when it is replaced. The HCM in slot 0 controls PICs on FPC 0 . The HCM in slot 1 controls PICs on FPC 1 . The buttons are labeled with the PIC slot numbers. The PIC slots on the upper FPC are numbered from

0/0 (zero/zero) through 0/3 , right to left. The PIC slots in the lower FPC are numbered from 1/0 (one/zero) through 1/3 , right to left.

For PIC replacement instructions, see

“Replacing an M10i PIC” on page 179 .

Documentation

•

M10i HCM Serial Number ID Label on page 248

•

•

M10i High-Availability Chassis Manager (HCM) Description on page 14

M10i Multiservice Edge Router Hardware Guide

M10i HCM LEDs

Figure 10: M10i High-Availability Chassis Manager

Two LEDs Indicate HCM status. There is a green LED labeled PWR and an blue LED labeled

MSTR .

Table 3 on page 16

describes the LED states.

Table 3: States for HCM LEDs

Label Color State Description

PWR Green On steadily HCM is functioning normally.

MSTR Blue

Blinking

On steadily

HCM is starting up.

HCM is master.

Documentation

•

•

M10i HCM Alarm LEDs on page 16

•

Figure 10 on page 16 ). The

M10i HCM Alarm LEDs

Two alarm LEDs are located on the right of the HCM (see

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 17

describes the alarm LEDs in more detail.

Chapter 3: Chassis Components and Descriptions

Table 4: Alarm LEDs

Shape Color

Red

Yellow

State Description

On steadily Critical alarm LED—Indicates a critical condition that can cause the router to stop functioning, such as component removal, failure, or overheating.

On steadily Warning alarm LED—Indicates a serious but nonfatal error condition, such as a maintenance alert or a significant increase in component temperature.

Documentation

•

M10i High-Availability Chassis Manager (HCM) Description on page 14

•

•

M10i HCM Serial Number ID Label on page 248

M10i Multiservice Edge Router Hardware Guide

CHAPTER 4

Cooling System Components and

Descriptions

•

M10i Fan Tray Description on page 19

M10i Fan Tray Description

The fan trays installed along each side of the chassis draw room air into the chassis to maintain an acceptable operating temperature for the Routing Engine, PICs, CFEB or

CFEB-E, and other components. The router's cooling system consists of two fan trays, located along the left and right side of the chassis, that provide side-to-side cooling (see

Figure 11 on page 19 ). They connect directly to the router midplane. Each fan tray is a

single unit containing eight individually fault-tolerant fans. If a single fan fails, the remaining fans continue to function indefinitely. For proper airflow, the primary fan tray should be installed in slot 1 (the left slot looking at the chassis from the rear) and must be installed for proper cooling at all times. The redundant fan tray, if present, should be installed in slot 0 on the right. This fan tray provides additional cooling and redundancy.

Figure 11: Airflow Through the Chassis

The fan tray is hot-removable and hot-insertable, as described in

“M10i Field-Replaceable

Units (FRUs)” on page 139

. For instructions on replacing it, see

“Replacing an M10i Fan

Tray” on page 150 .

M10i Multiservice Edge Router Hardware Guide

CAUTION: Do not remove both fan trays for more than one minute while the router is operating. The fans are the sole source of cooling, and the router can overheat when they are absent.

Documentation

•

Installing an M10i Fan Tray on page 149

•

Maintaining the M10i Cooling System on page 221

•

•

Troubleshooting the M10i Fan Tray on page 230

CHAPTER 5

Host Subsystem Components and

Descriptions

•

•

M10i Routing Engine 400 LEDs on page 24

•

•

M10i Routing Engine 850 LEDs on page 26

•

•

M10i Routing Engine RE-B-1800 Description on page 27

•

M10i Routing Engine 1800 LEDs on page 28

•

Routing Engine Specifications on page 29

•

•

Supported Routing Engines by Router on page 34

M10i Routing Engine Description

The Routing Engine runs Junos OS. The software processes that run on the Routing Engine maintain the routing tables, manage the routing protocols used on the router, control the router's interfaces, control some chassis components, and provide the interface for system management and user access to the router.

For a description of the Routing Engine's role in router architecture, see

“M10i Routing

Engine Architecture Overview” on page 7

NOTE: The M10i router supports the Routing Engine 400, Routing Engine

850, and Routing Engine 1800.

One or two Routing Engines can be installed into the midplane from the front of the chassis, as shown in

Figure 5 on page 11 . If two Routing Engines are installed, the

High-Availability Chassis Manager (HCM) determines which is the master and which is backup (in standby mode and so performs no functions). By default, the Routing Engine in the slot labeled RE0 is the master. To change the default master Routing Engine, include the appropriate [edit chassis redundancy routing-engine] statement in the

M10i Multiservice Edge Router Hardware Guide configuration, as described in the section about Routing Engine redundancy in the Junos

OS Administration Library .

NOTE: If two Routing Engines are installed, they must both be the same hardware model.

The Routing Engine is hot-pluggable, as described in

“M10i Field-Replaceable Units

(FRUs)” on page 139

. If two Routing Engines are installed, removal or failure of the backup

Routing Engine does not affect router function. Removal or failure of the master Routing

Engine affects forwarding and routing based on the high availability configuration:

• Dual Routing Engines without any high availability features enabled—Traffic is interrupted while the Packet Forwarding Engine is reinitialized. All kernel and forwarding processes are restarted. When the switchover to the new master Routing Engine is complete, routing convergence takes place and traffic is resumed.

• Graceful Routing Engine switchover (GRES) is enabled—Graceful Routing Engine switchover preserves interface and kernel information. Traffic is not interrupted.

However, graceful Routing Engine switchover does not preserve the control plane.

Neighboring routers detect that the router has restarted and react to the event in a manner prescribed by individual routing protocol specifications. To preserve routing without interruption during a switchover, graceful Routing Engine switchover must be combined with nonstop active routing.

• Nonstop active routing is enabled (graceful Routing Engine switchover must be configured for nonstop active routing to be enabled)—Nonstop active routing supports

Routing Engine switchover without alerting peer nodes that a change has occurred.

Nonstop active routing uses the same infrastructure as graceful Routing Engine switchover to preserve interface and kernel information. However, nonstop active routing also preserves routing information and protocol sessions by running the routing protocol process (rpd) on both Routing Engines. In addition, nonstop active routing preserves TCP connections maintained in the kernel.

• Graceful restart is configured—Graceful restart provides extensions to routing protocols so that neighboring helper routers restore routing information to a restarting router.

These extensions signal neighboring routers about the graceful restart and prevent the neighbors from reacting to the router restart and from propagating the change in state to the network during the graceful restart period. Neighbors provide the routing information that enables the restarting router to stop and restart routing protocols without causing network reconvergence. Neighbors are required to support graceful restart. The routing protocol process (rpd) restarts. A graceful restart interval is required.

For certain protocols, a significant change in the network can cause graceful restart to stop.

If you do not configure graceful Routing Engine switchover, graceful restart, or nonstop active routing, you can configure automatic Routing Engine mastership failover. For information about configuring automatic mastership failover, see the Junos OS

Administration Library .

Chapter 5: Host Subsystem Components and Descriptions

NOTE: Router performance might change if the backup Routing Engine's configuration differs from the former master's configuration. For the most predictable performance, configure the two Routing Engines identically, except for parameters unique to each Routing Engine.

NOTE: For information about configuring graceful Routing Engine switchover, graceful restart, and nonstop active routing, see the High Availability Feature

Guide.

NOTE: The first supported release for graceful Routing Engine switchover and nonstop active routing on the M10i router is Junos OS Release 6.1 and

Junos OS Release 8.4, respectively. However, for graceful Routing Engine switchover we recommend Junos OS Release 7.0 or later. Graceful restart software requirements are dependent on the routing protocols configured on the router. For the minimum software requirements for graceful restart, see the High Availability Feature Guide.

For replacement instructions, see

“Replacing the M10i Routing Engine” on page 158 .

Documentation

•

•

•

Displaying M10i Router Components and Serial Numbers on page 247

M10i Routing Engine 400 Description

The Routing Engine 400 has the following major 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 drive is optional. If installed, it provides primary storage. It holds 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 a 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.

• I2C/EEPROM—Stores the serial number of the Routing Engine.

M10i Multiservice Edge Router Hardware Guide

The faceplate of the Routing Engine 400 contains the following:

• PC card slot—Accepts a removable PC card, which stores software images for system upgrades.

• 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.

• 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.

• 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.

The disk from which the router boots is called the primary boot device , and the other disk is the alternate boot device .

The boot sequence for the router:

• PC Card

• CompactFlash card

• Hard disk

NOTE: If the router boots from an alternate boot device, a yellow alarm lights the LED on the router’s craft interface.

M10i Routing Engine 400 LEDs

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 5 on page 24

describes the LED states.

Table 5: States for Routing Engine LEDs

Label Color State Description

Green Blinking There is read/write activity on the PC card.

HDD

MASTER

FAIL

ONLINE

Blue

Red

Green

On steadily Routing Engine is functioning as master.

On steadily Routing Engine is not operational.

On steadily Routing Engine is running normally.

Documentation

•

Chapter 5: Host Subsystem Components and Descriptions

•

M10i PIC LEDs on page 53

•

Displaying M10i Router Components and Serial Numbers on page 247

M10i Routing Engine 850 Description

NOTE: RE-850 routing engine is being replaced with RE-B-1800 from Junos

OS release 12.1. See the End-of-life (EOL) and End-of-sale (EOS) Notification

Policy and Procedures for the M10i products at https://www.juniper.net/support/eol/ . End of life (EOL) indicates that the product has been removed from the price list and is no longer available for purchase. End of support (EOS) indicates that no new support contracts are available on these products and the last contract will expire on the EOS date associated with each product. For more information about EOS or EOL products, see the product support notification (PSN) hardware end-of-life announcements. For PSN details for RE-850, see PSN-2011-09-369.

Figure 12: Routing Engine

The Routing Engine 850 has the following major components (see

Figure 12 on page 25 ):

• 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—Provides primary storage. It holds software images, configuration files, and microcode.

• Hard disk—Provides secondary storage for log files and memory dumps, and can reboot the system if the CompactFlash card fails.

• I2C/EEPROM—Stores the serial number of the Routing Engine.

M10i Multiservice Edge Router Hardware Guide

NOTE: For specific information about Routing Engine components (for example, the capacity of the hard drive), issue the show chassis routing-engine command.

The faceplate of the Routing Engine 850 contains the following:

• PC card slot—Accepts a removable PC card, which stores software images for system upgrades.

• 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.

• 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.

• 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.

The disk from which the router boots is called the primary boot device , and the other disk is the alternate boot device .

The boot sequence for the router:

• PC Card

• CompactFlash card

• Hard disk

NOTE: If the router boots from an alternate boot device, a yellow alarm lights the LED on the router’s craft interface.

Documentation

•

M10i PIC LEDs on page 53

M10i Routing Engine 850 LEDs

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 26

describes the LED states.

Table 6: States for Routing Engine LEDs

Label Color State Description

HDD Green Blinking There is read/write activity on the PC card.

Chapter 5: Host Subsystem Components and Descriptions

Table 6: States for Routing Engine LEDs (continued)

Label Color State Description

MASTER Blue

Red

On steadily Routing Engine is functioning as master.

On steadily Routing Engine is not operational.

FAIL

ONLINE Green On steadily Routing Engine is running normally.

Documentation

•

•

M10i Routing Engine 1800 LEDs on page 28

M10i Routing Engine RE-B-1800 Description

Figure 13: Routing Engine RE-B-1800

The Routing Engine RE-B-1800 has the following major components:

• CPU—Runs Junos OS to maintain the router's routing tables and routing protocols. It has Intel’s single core Jasper Forest processor.

• USB port—Provides a removable media interface through which you can install the

Junos OS manually. Junos OS supports USB version 2.0.

• DRAM—Provides storage for the routing and forwarding tables and for other Routing

Engine processes.

• CompactFlash card—Provides primary storage for software images, configuration files, and microcode. The CompactFlash card is field-replaceable.

• Solid-state Disk (SSD)—Provides secondary storage for log files and memory dumps, and can reboot the system if the CompactFlash card fails. SSD is front-pluggable and hot-swappable.

• Interface ports—The AUX , CONSOLE , and MGMT ports provide access to management devices. Each Routing Engine has one 10/100/1000-Mbps Ethernet port for connecting to a management network, and two asynchronous serial ports—one for connecting to a console and one for connecting to a modem or other auxiliary device.

• EEPROM—Stores the serial number of the Routing Engine.

• Reset button—Reboots the Routing Engine when pressed.

• Online/Offline button—Takes the Routing Engine online or offline when pressed.

M10i Multiservice Edge Router Hardware Guide

• Real-time clock—Provides real-time integrated clock with batter backup for data retention.

• Extractor handle—Used for inserting and extracting the Routing Engine.

• Captive screws—Secure the Routing Engine in place.

• Four LEDs—A green LED labeled STORAGE , a blue LED labeled MASTER , a red LED labeled FAIL , and a green LED labeled ONLINE indicate Routing Engine status.

NOTE: For specific information about Routing Engine components (for example, the capacity of the SSD), issue the show chassis routing-engine command.

The router is shipped with the Junos OS preinstalled on the Routing Engine. There are three copies of software:

• One copy on the CompactFlash card in the Routing Engine.

• One copy on the SSD in the Routing Engine.

• One copy on a USB flash drive that can be inserted into the slot on the Routing Engine faceplate.

The Routing Engine boots from the storage media in this order: the USB device (if present), then the CompactFlash card, then the SSD, then the LAN. Normally, the router boots from the copy of the software on the CompactFlash card.

Documentation

•

•

•

Replacing the SSD on an RE-B-1800 Routing Engine on page 169

•

M10i Routing Engine 1800 LEDs

Four LEDs—a blue LED labeled MASTER , a red LED labeled FAIL , a green LED labeled

STORAGE , and a green LED labeled ONLINE —located on the faceplate, indicate Routing

Engine status.

Table 7 on page 28

describes the LED states.

Table 7: States for Routing Engine LEDs

Label Color State Description

Blue On steadily Routing Engine is functioning as master.

MASTER

FAIL

STORAGE

Red

Green

On steadily Routing Engine is not operational.

Blinking Indicates activity on the SSD or Compact Flash.

Chapter 5: Host Subsystem Components and Descriptions

Table 7: States for Routing Engine LEDs (continued)

Label Color State Description

ONLINE Green On steadily Routing Engine is running normally.

Documentation

•

Displaying M10i Router Components and Serial Numbers on page 247

•

“M10i Routing Engine 850 LEDs” on page 25

M10i Routing Engine Interface Ports

Each Routing Engine has a set of ports for connecting to one or more external devices on which system administrators can issue Junos OS command-line interface (CLI) commands to manage the router (see

The ports with the indicated label in each set function as follows:

• AUX/MODEM — Connects the Routing Engine to a laptop, modem, or other auxiliary device through an RS-232 (EIA-232) serial cable.

• MGMT —Connects the Routing Engine through an Ethernet connection to a management

LAN (or any other device that plugs into an Ethernet connection) for out-of-band management. The port uses an autosensing RJ-45 connector to support both 10- and

100-Mbps connections.

To the left of each MGMT port is a link status indicator, which lights to show that a link has been established over the Ethernet connection. To the right of each MGMT port is an activity indicator, which flashes when data is being transferred.

• CONSOLE —Connects the Routing Engine to a system console through an RS-232

(EIA-232) serial cable.

For information about the pinouts for the connectors, see

“RJ-45 Connector Pinouts for the M10i Routing Engine MGMT Port” on page 100 .

Documentation

•

•

M10i Routing Engine Architecture Overview on page 7

•

Routing Engine Specifications

Table 8 on page 30

lists the current specifications for Routing Engines supported on

M Series, MX Series, and T Series routers.

Table 9 on page 33

lists the specifications for end-of-life Routing Engines.

M10i Multiservice Edge Router Hardware Guide

NOTE: For a list of the routing engines that are supported on the M Series,

MX Series, T Series, and PTX routers, see

“Supported Routing Engines by

Router” on page 34

NOTE: For information about PTX Series Routing Engine specifications, see

Routing Engines Supported on PTX Series Routers. For information about

Table 8: Routing Engine Specifications

Routing

Engine Processor Memory

Connection to PFEs Disk

RE-400-768 400-MHz

Celeron

768 MB Fast

Ethernet

RE-A-1000-2048 1.0-GHz

Pentium

RE-A-2000-4096 2.0-GHz

Pentium

RE-S-1300-2048 1.3-GHz

Pentium

2048 MB

4096 MB

2048 MB

Gigabit

Ethernet

Gigabit

Ethernet

Gigabit

Ethernet

Media

First Junos OS

Support

40 GB hard disk

1 GB

CompactFlash card

9.0

40 GB hard disk

1 GB

CompactFlash card

8.1

40 GB hard disk

1 GB

CompactFlash card

8.1

40 GB hard disk

1 GB

CompactFlash card

8.2

Switch Control

Board

–

SCB, SCBE

RE-S-2000-4096 2.0-GHz

Pentium

4096 MB Gigabit

Ethernet

40 GB hard disk

1 GB

CompactFlash card

8.2

SCB, SCBE

Chapter 5: Host Subsystem Components and Descriptions

Table 8: Routing Engine Specifications (continued)

Routing

Engine Processor Memory

Connection to PFEs Disk

RE-C1800 1.8-GHz 8 GB Gigabit

Ethernet

RE-C2600

1.8 Ghz

2.6-GHz

16 GB

Gigabit

Ethernet

Gigabit

Ethernet

RE-A-1800x2 1800-MHz 8 GB or 16

Gigabit

Ethernet

RE-S-1800x2 1800-MHz 8 GB or 16

Gigabit

Ethernet

Media

First Junos OS

Support

Switch Control

Board

SSD

4 GB

CompactFlash card

T1600 router in a routing matrix:

9.6R2

CB-T for a standalone router.

Standalone

T640 or T1600 router:11.2

CB-LCC for a router in a routing matrix.

4 GB

CompactFlash card

32-bit Junos OS on a standalone

T1600 router:

11.4R2 32-bit

Junos OS on a

T1600 router in a routing matrix:

11.4R2

CB-T for a standalone router.

CB-LCC for a router in a routing matrix.

64-bit Junos OS on a standalone

T1600 router:

11.4R2 64-bit

Junos OS on a

T1600 router in a routing matrix:

11.4R2

4 GB

CompactFlash card

TX Matrix Plus router: 9.6R2

–

– 32 GB SSD 4 GB

CompactFlash card

10.4

32 GB SSD 4 GB

CompactFlash card

10.4

SCB, SCBE

RE-S-1800x4 1800-MHz 8GB or 16

Gigabit

Ethernet

RE-S-MX104 1.8-GHz

RE-B-1800x1-4G 1.73-GHz

4 GB

Gigabit

Ethernet

Gigabit

Ethernet

32 GB SSD 4 GB

CompactFlash card

10.4

– 8 GB NAND

Flash

13.2

64 GB SSD 4 GB

CompactFlash card

12.1R2, 11.4R4, and 12.2R1

SCB, SCBE,

SCBE2

–

M10i Multiservice Edge Router Hardware Guide

Table 8: Routing Engine Specifications (continued)

Routing

Engine Processor Memory

Connection to PFEs Disk

RE-MX2000-1800x4 1.8- GHz 16 GB Gigabit

Ethernet

RE-S-1800X4-32G-S 1.8- Ghz

REMX2K-1800-32G-S 1.8- Ghz

RE-S-X6-64G,

RE-S-X6-64G-LT

2 Ghz

REMX2K-X8-64G 2.3 Ghz

32 GB

64 GB

Gigabit

Ethernet

Gigabit

Ethernet

Gigabit

Ethernet

Gigabit

Ethernet

Media

First Junos OS

Support

Switch Control

Board

32 GB SSD 4 GB Fixed

Internal

CompactFlash card

12.3R2

32 GB SSD 4 GB Fixed

Internal

CompactFlash card

•

12.3R4

13.2R1

SCB, SCBE

SCBE2

32 GB SSD 4GB Fixed

Internal

CompactFlash card

•

12.3R4

13.2R1

15.1F4, 16.1

Two 50-GB

SSDs

Two

100-GB

SSDs

15.1F5-S1, 16.1R2, and 16.2R1

–

SCBE2

–

REMX2K-X8-64G-LT 2.3 Ghz 64 GB Gigabit

Ethernet

17.2R1

–

REMX2008-X8-64G 2.3 Ghz

RE-S-1600x8 1.6 Ghz

REMX2008-X8-64G-LT 2.1 Ghz

REMX2008-X8-128G 2.3 Ghz

RE-S-X6-128G 2.1 Ghz

REMX2K-X8-128G 2.1 Ghz

JNP10003-RE1 1.6-GHz

64 GB

128 GB

64 GB

Gigabit

Ethernet

Gigabit

Ethernet

Gigabit

Ethernet

Gigabit

Ethernet

Gigabit

Ethernet

Gigabit

Ethernet

Gigabit

Ethernet

Two

100-GB

SSDs

Two 50-GB

SSDs

–

Two 50-GB

SSDs

–

Two

100-GB

SSDs

Two

200-GB

SSDs

Two

200-GB

SSDs

Two

200-GB

SSDs

Two 100

GB SSDs

15.1F7

17.3R1

17.2R1

18.2R1

18.1R1

17.3R1

–

Chapter 5: Host Subsystem Components and Descriptions

Table 8: Routing Engine Specifications (continued)

Routing

Engine Processor Memory

Connection to PFEs Disk

JNP10003-RE1-LT 1.6-GHz 64 GB

JNP10K-RE0 2.5 GhZ

JNP10K-RE1 2.3 GhZ

JNP10K-RE1-LT 2.3 GhZ

JNP10K-RE1-128 2.3 GhZ

32 GB

64 GB

128 GB

Gigabit

Ethernet

Gigabit

Ethernet

Gigabit

Ethernet

Gigabit

Ethernet

Gigabit

Ethernet

Media

Two 100

GB SSDs

Two 50 GB

SSDs

Two 200

GB SSDs

Two 200

GB SSDs

Two 200

GB SSDs

17.2R1

18.2R1

18.3R1

First Junos OS

Support

Switch Control

Board

18.1R1

NOTE: Use shielded CAT5e cable for connecting the AUX , CONSOLE , and

MGMT ports in RE-S-X6-64G, REMX2K-X8-64G, and REMX2008-X8-64G

Routing Engines.

Table 9: End-of-Life Routing Engine Specifications

Routing

Engine Processor Memory

Connection to PFEs Disk

RE-333-256 333-MHz

Pentium II

256 MB Fast

Ethernet

RE-333-768 333-MHz

Pentium II

768 MB Fast

Ethernet

Media

First Junos OS

Support

6.4 GB hard disk

80 MB

CompactFlash card

3.4

6.4 GB hard disk

80 MB

CompactFlash card

3.4

EOL Details

PSN-2003-01-063

RE-600-512 600-MHz

Pentium III

512 MB

RE-600-2048 600-MHz

Pentium III

2048 MB

RE-850-1536 850-MHz

Pentium III

1536 MB

RE-M40 200-MHz

Pentium

256 MB

Fast

Ethernet

Fast

Ethernet

Fast

Ethernet

Fast

Ethernet

30 GB hard disk

256 MB

CompactFlash card

5.4

40 GB hard disk

1 GB

CompactFlash card

5.3

40 GB hard disk

1 GB

CompactFlash card

7.2

6.4 GB hard disk

80 MB

CompactFlash card

3.2

PSN-2004-07-019

PSN-2008-02-018

PSN-2011-04-226

FA-HW-0101-001

M10i Multiservice Edge Router Hardware Guide

Table 9: End-of-Life Routing Engine Specifications (continued)

Routing

Engine Processor Memory

Connection to PFEs Disk Media

RE-M40-333-768 333-MHz

Pentium II

768 MB Fast

Ethernet

RE-M40-600-2048 600-MHz

Pentium III

2048 MB

RE-1600-2048 1.6-GHz

Pentium M

2048 MB

Fast

Ethernet

Gigabit

Ethernet

First Junos OS

Support

10 GB hard disk

80 MB

CompactFlash card

4.2

30 GB hard disk

128 MB

CompactFlash card

5.4

40 GB hard disk

1 GB

CompactFlash card

6.2

EOL Details

PSN-2003-01-063

PSN-2004-11-020

PSN-2008-02-019

NOTE: The memory in

Table 8 on page 30

indicates the amount of total memory. To determine the amount of available memory, issue the show chassis routing-engine CLI command.

On routers that accept two Routing Engines, you cannot mix Routing Engine types except for a brief period (one minute or so) during an upgrade or downgrade to two Routing

Engines of the same type.

Documentation

•

Supported Routing Engines by Router on page 34

Supported Routing Engines by Router

The following tables list the Routing Engines that each router supports, the first supported release for the Routing Engine in the specified router, the management Ethernet interface, and the internal Ethernet interfaces for each Routing Engine.

•

M7i Routing Engines on page 35

•

M10i Routing Engines on page 35

•

M40e Routing Engines on page 36

•

M120 Routing Engines on page 36

•

M320 Routing Engines on page 37

•

MX5, MX10, MX40, and MX80 Routing Engine on page 37

•

MX104 Routing Engines on page 38

•

MX240 Routing Engines on page 38

•

MX480 Routing Engines on page 39

•

MX960 Routing Engines on page 40

•

MX2008 Routing Engines on page 41

•

MX2010 Routing Engines on page 42

Chapter 5: Host Subsystem Components and Descriptions

•

MX2020 Supported Routing Engines on page 42

•

MX10003 Routing Engines on page 43

•

MX10008 Routing Engines on page 43

•

PTX1000 Routing Engines on page 44

•

PTX3000 Routing Engines on page 44

•

PTX5000 Routing Engines on page 45

•

PTX10008 and PTX10016 Routing Engines on page 45

•

T320 Routing Engines on page 46

•

T640 Routing Engines on page 46

•

T1600 Routing Engines on page 47

•

T4000 Routing Engines on page 48

•

TX Matrix Routing Engines on page 49

•

TX Matrix Plus Routing Engines on page 49

•

TX Matrix Plus (with 3D SIBs) Routing Engines on page 50

M7i Routing Engines

Table 10 on page 35

lists the Routing Engines supported by the M7i router. The M7i router supports 32-bit Junos OS only.

Table 10: M7i Routing Engines

Model Number

Name in CLI

Output

First Supported 32-bit

Junos OS Release

Management

Ethernet Interface

Internal Ethernet

Interface

RE-5.0

9.0

fxp0 fxp1 RE-400-768 (EOL details:

TSB16445 )

RE-850-1536 (EOL details:

TSB15553 )

RE-B-1800X1-4G

RE-850

RE-B-1800x1

7.2

fxp0 fxp0 fxp1 em0 11.4R4

12.1R2

M10i Routing Engines

Table 11 on page 35

lists the Routing Engines supported by the M10i router. The M10i router supports 32-bit Junos OS only.

Table 11: M10i Routing Engines

Model Number

Name in CLI

Output

First Supported

32-bit Junos OS

Release

Management

Ethernet Interface

Internal Ethernet

Interface

RE-400-768 (EOL details:

TSB16445 )

RE-5.0

9.0

fxp0 fxp1 fxp2

M10i Multiservice Edge Router Hardware Guide

Table 11: M10i Routing Engines (continued)

Model Number

RE-850-1536 (EOL details:

TSB15553 )

Name in CLI

Output

RE-850

First Supported

32-bit Junos OS

Release

7.2

Management

Ethernet Interface

Internal Ethernet

Interface fxp0 fxp0 fxp1 fxp2 em0 RE-B-1800X1-4G RE-B-1800x1 11.4R4

12.1R2

M40e Routing Engines

Table 12 on page 36

lists the Routing Engines supported by the M40e router.

Table 12: M40e Routing Engines

Model Number Name in CLI Output

First Supported

Junos OS Release

Management

Ethernet Interface

Internal Ethernet

Interface

RE-600-2048 (EOL details:

TSB14373 )

RE-3.0

or RE-3.0

(RE-600)

5.3

fxp0

RE-A-1000-2048 RE-A-1000 8.1

fxp0 fxp1 fxp2 fxp1 fxp2

M120 Routing Engines

Table 13 on page 36

lists the Routing Engines supported by the M120 router.

Table 13: M120 Routing Engines

Model Number

Name in CLI

Output

First Supported

32-bit Junos OS

Release

First

Supported

64-bit Junos

OS Release

Management

Ethernet

Interface

Internal Ethernet

Interface

RE-A-1000-2048 RE-A-1000 8.0R2

– fxp0

RE-A-2000-4096

RE-A-1800X2-8G

RE-A-2000

RE-A-1800x2

8.0R2

•

11.4R5

12.1R3

–

10.4

fxp0 fxp0 fxp1 fxp2 em0 bcm0 fxp1 fxp2

Chapter 5: Host Subsystem Components and Descriptions

Table 13: M120 Routing Engines (continued)

Model Number

RE-A-1800X2-16G

Name in CLI

Output

RE-A-1800x2

RE-A-1800X4-16G RE-A-1800x4

First Supported

32-bit Junos OS

Release

•

11.4R5

12.1R3

•

11.4R5

12.1R3

First

Supported

64-bit Junos

OS Release

10.4

Management

Ethernet

Interface

Internal Ethernet

Interface fxp0 fxp0 fxp1 fxp2 em0 em1

M320 Routing Engines

Table 14 on page 37

lists the Routing Engines supported by the M320 router.

Table 14: M320 Routing Engines

Model Number

Name in CLI

Output

First Supported

32-bit Junos OS

Release

First

Supported

64-bit Junos

OS Release

Management

Ethernet

Interface

Internal Ethernet

Interface

RE-1600-2048 (EOL details: TSB14374 )

RE-4.0

6.2

– fxp0

RE-A-2000-4096

RE-A-1800X2-8G

RE-A-2000

RE-A-1800x2

8.1

•

11.4R5

12.1R3

–

10.4

fxp0 fxp0 fxp1 fxp2 em0 bcm0 em0 bcm0

RE-A-1800X2-16G RE-A-1800x2 •

•

11.4R5

12.1R3

10.4

fxp0

RE-A-1800X4-8G RE-A-1800X4 •

•

11.4R5

12.1R3

12.2

10.4

fxp0 em0 bcm0 em0 em1

MX5, MX10, MX40, and MX80 Routing Engine

Table 15 on page 38

lists the Routing Engines supported by the MX5, MX10, MX40, and

MX80 routers.

M10i Multiservice Edge Router Hardware Guide

Table 15: MX5, MX10, MX40, and MX80 Routing Engine

Model

Number

Name in CLI

Output

First Supported

32-bit Junos OS

Release

First Supported

64-bit Junos OS

Release

Management

Ethernet

Interface Internal Ethernet Interface

Built-in Routing

Engine

Routing Engine

RE-MX80

12.3

fxp0 em0 em1

NOTE: em1 is used to communicate with the

MS-MIC when it is inserted.

MX104 Routing Engines

Table 16 on page 38

lists the Routing Engines supported by MX104 routers.

Table 16: MX104 Routing Engines

Model

Number

Name in CLI

Output

First Supported

32-bit Junos OS

Release

First Supported

64-bit Junos OS

Release

Management

Ethernet

Interface

Internal Ethernet

Interface

RE-S-MX104 Routing Engine 13.2

– fxp0 fxp1 fxp2

MX240 Routing Engines

Table 17 on page 38

lists the Routing Engines supported by MX240 routers.

Table 17: MX240 Supported Routing Engines

Model Number

Name in CLI

Output

First Supported

32-bit Junos OS

Release

First Supported

64-bit Junos OS

Release

Management

Ethernet

Interface

Internal Ethernet

Interface

9.0

– fxp0 fxp1 fxp2

RE-S-1300-2048

(EOL details:

TSB16556

RE-S-1300

RE-S-2000-4096

(EOL details:

TSB16735

RE-S-2000

RE-S-1800X2-8G

(EOL details:

TSB16556

RE-S-1800x2

RE-S-1800x2-16G

(EOL details:

TSB16556

RE-S-1800x2

9.0

•

11.4R5

12.1R3

•

11.4R5

12.1R3

–

10.4

fxp0 fxp0 fxp0 fxp1 fxp2 em0 em1 em0 em1

Chapter 5: Host Subsystem Components and Descriptions

Table 17: MX240 Supported Routing Engines (continued)

Model Number

Name in CLI

Output

First Supported

32-bit Junos OS

Release

First Supported

64-bit Junos OS

Release

Management

Ethernet

Interface

RE-S-1800X4-8G RE-S-1800X4 •

•

11.4R5

12.1R3

10.4

fxp0

RE-S-1800X4-16G RE-S-1800x4 •

•

11.4R5

12.1R3

10.4

fxp0

•

12.3R4

13.2R1

–

Internal Ethernet

Interface em0 em1 em0 em1 em0, em1 ixlv0, igb0

RE-S-1800X4-32G-S RE-S-1800X4

RE-S-X6-64G RE-S-2X00x6

•

12.3R4

13.2R1

15.1F4

16.1R1

17.2R1

fxp0 fxp0

RE-S-X6-64G-LT RE-S-2X00x6 -LT – fxp0 ixlv0, igb0 em0

RE-S-X6-128G RE-S-2X00x6-128 – 18.1R1

fxp0 ixlv0, igb0 em0

MX480 Routing Engines

Table 18 on page 39

lists the Routing Engines supported by MX480 routers.

Table 18: MX480 Supported Routing Engines

Model Number

Name in CLI

Output

First Supported

32-bit Junos OS

Release

First Supported

64-bit Junos OS

Release

Management

Ethernet

Interface

Internal Ethernet

Interface

8.4

– fxp0 fxp1 fxp2

RE-S-1300-2048

(EOL details:

TSB16556

RE-S-1300

RE-S-2000-4096

(EOL details:

TSB16735

RE-S-2000

RE-S-1800X2-8G

(EOL details:

TSB16556

RE-S-1800x2

RE-S-1800X2-16G

(EOL details:

TSB16556

RE-S-1800x2

8.4

•

11.4R5

12.1R3

•

11.4R5

12.1R3

–

10.4

fxp0 fxp0 fxp0 fxp1 fxp2 em0 em1 em0 em1

M10i Multiservice Edge Router Hardware Guide

Table 18: MX480 Supported Routing Engines (continued)

Model Number

Name in CLI

Output

First Supported

32-bit Junos OS

Release

First Supported

64-bit Junos OS

Release

Management

Ethernet

Interface

RE-S-1800X4-8G RE-S-1800X4 •

•

11.4R5

12.1R3

10.4

fxp0

RE-S-1800X4-16G RE-S-1800x4 •

•

11.4R5

12.1R3

10.4

fxp0

RE-S-1800X4-32G-S RE-S-1800X4

RE-S-X6-64G RE-S-2X00x6

•

12.3R4

13.2R1

–

•

12.3R4

13.2R1

15.1F4

16.1R1

17.2R1

fxp0 fxp0

RE-S-X6-64G-LT RE-S-2X00x6 -LT –

RE-S-X6-128G RE-S-2X00x6-128 – 18.1R1

fxp0 fxp0 ixlv0, igb0 em0 ixlv0, igb0 em0

MX960 Routing Engines

Table 19 on page 40

lists the Routing Engines supported by MX960 routers.

Table 19: MX960 Supported Routing Engines

Model Number

Name in CLI

Output

First Supported

32-bit Junos

OS Release

First

Supported

64-bit Junos

OS Release

Management

Ethernet

Interface

Internal

Ethernet

Interface

RE-S-1300-2048 (EOL details: TSB16556

RE-S-1300 8.2

– fxp0

RE-S-2000-4096 (EOL details: TSB16735

RE-S-1800X2-8G (EOL details: TSB16556

RE-S-2000

RE-S-1800x2

8.2

•

11.4R5

12.1R3

–

10.4

fxp0 fxp0 fxp1 fxp2 fxp1 fxp2 em0 em1

RE-S-1800X2-16G (EOL details: TSB16556

RE-S-1800x2 •

•

11.4R5

12.1R3

10.4

fxp0 em0 em1

Internal Ethernet

Interface em0 em1 em0 em1 em0 em1 ixlv0, igb0

Chapter 5: Host Subsystem Components and Descriptions

Table 19: MX960 Supported Routing Engines (continued)

Model Number

Name in CLI

Output

First Supported

32-bit Junos

OS Release

First

Supported

64-bit Junos

OS Release

Management

Ethernet

Interface

Internal

Ethernet

Interface

RE-S-1800X4-8G RE-S-1800x4 •

•

11.4R5

12.1R3

10.4

fxp0

RE-S-1800X4-16G RE-S-1800x4 •

•

11.4R5

12.1R3

10.4

fxp0 em0 em1 em0 em1

RE-S-1800X4-32G-S

RE-S-X6-64G

RE-S-1800x4

RE-S-2X00x6

•

12.3R4

13.2R1

–

•

12.3R4

13.2R1

fxp0 fxp0 em0 em1 ixlv0, igb0

RE-S-2X00x6 –

15.1F4

16.1R1

17.1R2

fxp0 ixlv0, igb0 RE-S-X6-64G (For

MX960-VC)

RE-S-X6-64G-LT RE-S-2X00x6 -LT – 17.2R1

fxp0

RE-S-X6-128G RE-S-2X00x6-128 – 18.1R1

fxp0 ixlv0, igb0 em0 ixlv0, igb0 em0

MX2008 Routing Engines

Table 20 on page 41

lists the Routing Engines supported by MX2008 routers.

Table 20: MX2008 Supported Routing Engines

Model Number

Name in CLI

Output

First Supported 64-bit Junos

OS Release

Management

Ethernet

Interface

Internal

Ethernet

Interface

REMX2008-X8-64G RE-MX2008-X8-64G 15.1F7

fxp0

REMX2008-X8-64G-LT

REMX2008-X8-128G

REMX2008-X8-64G-LT 17.2R1

RE-MX2008-X8-128G 18.2R1

fxp0 fxp0 ixlv0 ixlv1 ixlv0 ixlv1 ixlv0 ixlv1

M10i Multiservice Edge Router Hardware Guide

MX2010 Routing Engines

Table 21 on page 42

lists the Routing Engines supported by MX2010 routers.

Table 21: MX2010 Supported Routing Engines

Model Number

Name in CLI

Output

First Supported 64-bit Junos

OS Release

Management

Ethernet

Interface

Internal Ethernet

Interface

RE-MX2000-1800X4 RE-S-1800x4 12.3R2

fxp0

REMX2K-1800-32G-S

REMX2K-X8-64G

REMX2K-X8-64G-LT

REMX2K-X8-128G

RE-S-1800x4

RE-S-2X00x8

•

12.3R4

13.2R1

•

15.1F5-S1

16.1R2

16.2R1

17.2R1

RE-MX200X8-128G 18.1R1

fxp0 fxp0 fxp0 fxp0 ixlv0 ixlv1 em0 ixlv0 ixlv1 em0 ixlv0 ixlv1 em0 em1 em0 em1

MX2020 Supported Routing Engines

Table 22 on page 42

lists the Routing Engines supported by MX2020 routers.

Table 22: MX2020 Supported Routing Engines

Model Number

Name in CLI

Output

First Supported 64-bit Junos

OS Release

Management

Ethernet

Interface

Internal

Ethernet

Interface

RE-MX2000-1800X4 RE-S-1800x4 12.3R2

fxp0

REMX2K-1800-32G-S RE-S-1800x4 •

•

12.3R4

13.2R1

fxp0 em0 em1 em0 em1

Chapter 5: Host Subsystem Components and Descriptions

Table 22: MX2020 Supported Routing Engines (continued)

Model Number

Name in CLI

Output

First Supported 64-bit Junos

OS Release

Management

Ethernet

Interface

REMX2K-X8-64G RE-S-2X00x8 •

•

15.1F5-S1

16.1R2

16.2R1

fxp0

REMX2K-X8-64G-LT

REMX2K-X8-128G

RE-S-2X00x8 17.2R1

RE-MX200X8-128G 18.1R1

fxp0 fxp0 ixlv0 ixlv1 em0 ixlv0 ixlv1 em0

Internal

Ethernet

Interface ixlv0 ixlv1 em0

MX10003 Routing Engines

Table 23 on page 43

lists the Routing Engines supported by MX10003 routers.

Table 23: MX10003 Supported Routing Engines

Model Number

Name in CLI

Output

First Supported 64-bit Junos

OS Release

Management

Ethernet

Interface

Internal

Ethernet

Interface

JNP10003-RE1 RE-S-2X00x6 17.3R1

fxp0

JNP10003-RE1-LT RE-S-1600x8 18.1R1

fxp0 em3 em4 em3 em4

MX10008 Routing Engines

Table 24 on page 43

lists the Routing Engines supported on the MX10008 router.

Table 24: MX10008 Routing Engines

Model Number Name in CLI Output

First Supported

Junos OS Release

Management

Ethernet Interface

Internal Ethernet

Interface

JNP10K-RE1 RE X10 18.2R1

em0 bme0 bme1

M10i Multiservice Edge Router Hardware Guide

Table 24: MX10008 Routing Engines (continued)

Model Number Name in CLI Output

First Supported

Junos OS Release

JNP10K-RE1-LT RE X10 LT 18.3R1

JNP10K-RE1-128 RE X10 128G 18.3R1

Management

Ethernet Interface em0

Internal Ethernet

Interface em0 bme0 bme1 bme0 bme1

PTX1000 Routing Engines

Table 25 on page 44

lists the Routing Engine supported on the PTX1000.

NOTE: The PTX1000 supports 64-bit Junos OS only.

Table 25: PTX1000 Routing Engines

Model Number

Name in CLI

Output

Built-in Routing

Engine

RE-PTX1000

First Supported Junos OS

Release

Management

Ethernet Interface

•

16.1X65-D30

17.2R1

em0

Internal Ethernet

Interface bme0 em1

PTX3000 Routing Engines

Table 26 on page 44

lists the Routing Engines supported on the PTX3000.

Table 26: PTX3000 Routing Engines

Model Number

Name in CLI

Output

RE-DUO-C2600-16G RE-DUO-2600

RCB-PTX-X6-32G

NOTE: The PTX3000 supports 64-bit Junos OS only.

RE-PTX-2X00x6

First Supported Junos OS

Release

13.2R2

Management

Ethernet Interface

Internal Ethernet

Interface em0 ixgbe0 ixgbe1

16.1R4

17.1R1

This Routing Engine does not support Junos OS Release 16.2.

em0 ixlv0 ixlv1

Chapter 5: Host Subsystem Components and Descriptions

PTX5000 Routing Engines

Table 27 on page 45

lists the Routing Engines supported on the PTX5000.

NOTE:

• PTX5000 supports 64-bit Junos OS only.

• The PTX5000 router supports two midplanes. The midplane identified as

Midplane-8S in the CLI output is supported in Junos OS releases, 12.1X48,

12.3, and 13.2. The enhanced midplane, identified as Midplane-8SeP is supported from Junos OS release 14.1 onwards.

The RE-DUO-2600 routing engine with Junos OS 13.2 or earlier is not supported on the PTX5000BASE2 midplane.

Table 27: PTX5000 Routing Engines

Model Number Name in CLI Output

RE-DUO-C2600-16G RE-DUO-2600

First Supported Junos OS

Release

RE-PTX-X8-64G RE-PTX-2X00x8

Management

Ethernet

Interface

12.1X48

12.3

13.2

NOTE: The PTX5000 does not support Junos OS Releases 12.1,

12.2, or 13.1.

em0

15.1F4

16.1R1

em0

Internal Ethernet

Interface ixgbe0 ixgbe1

RE-PTX-X8-128G RE-PTX-2X00x8-128G 18.1R1

em0 ixlv0 ixlv1 em1 ixlv0 ixlv1 em1

PTX10008 and PTX10016 Routing Engines

Table 28 on page 46

lists the Routing Engines supported on the PTX10008 and PTX10016 routers.

M10i Multiservice Edge Router Hardware Guide

Table 28: PTX10008 and PTX10016 Routing Engines

Model Number Name in CLI Output

First Supported

Junos OS Release

JNP10K-RE0 RE-PTX-2X00x4 17.2R1

JNP10K-RE1

JNP10K-RE1-LT

JNP10K-RE1-128

RE X10

RE X10 LT

RE X10 128G

18.2R1

18.3R1

Management

Ethernet Interface em0, em1 em0 em0 em0

Internal Ethernet

Interface bme0 bme1 bme0 bme1 bme0 bme1 bme0 bme1

T320 Routing Engines

Table 29 on page 46

lists the Routing Engines supported by the T320 router.

Table 29: T320 Routing Engines

Model Number Name in CLI Output

First Supported

32-bit Junos OS

Release

Management

Ethernet Interface

Internal Ethernet

Interface

RE-600-2048 (EOL details:

TSB14373 )

RE-3.0

or RE-3.0

(RE-600)

5.3

fxp0 fxp1 fxp2

RE-1600-2048 (EOL details:

TSB14374

RE-4.0

6.2

fxp0

RE-A-2000-4096 RE-A-2000 8.1

fxp0 fxp1 fxp2 fxp1 fxp2

The T320 router supports the CB-T control board.

T640 Routing Engines

Table 30 on page 47

lists the Routing Engines supported by the T640 router.

Chapter 5: Host Subsystem Components and Descriptions

Table 30: T640 Routing Engines

Model Number

Name in CLI

Output

First Supported 32-bit

Junos OS Release

First Supported 64-bit

Junos OS Release

Management

Ethernet

Interface

Internal

Ethernet

Interface

RE-600-2048 (EOL details: TSB14373 )

RE-3.0

(RE-600)

RE-1600-2048 (EOL details: TSB14374

RE-4.0

5.3

6.2

–

– fxp0 fxp0 fxp1 fxp2

RE-A-2000-4096 RE-A-2000 8.1

– fxp0 fxp1 fxp2 em0 bcm0

RE-DUO-C1800-8G RE-DUO-1800 32-bit Junos OS on a standalone T640 router:

11.2

32-bit Junos OS on a

T640 router in a routing matrix: 11.4R9

64-bit Junos OS on a standalone T640 router:

11.3

em0

64-bit Junos OS on a

T640 router in a routing matrix: 11.4R9

RE-DUO-C1800-16G RE-DUO-1800 32-bit Junos OS on a standalone T640 router:

11.4R2

64-bit Junos OS on a standalone T640 router:

11.4R2

em0

32-bit Junos OS on a

T640 router in a routing matrix: 11.4R9

64-bit Junos OS on a

T640 router in a routing matrix: 11.4R9

bcm0 em1 bcm0 em1

The T640 standalone router supports CB-T control board and CB-LCC in a T640 routing matrix.

T1600 Routing Engines

Table 31 on page 47

lists the Routing Engines supported by the T1600 router.

NOTE: (Two RE-DUO-C1800-8G or two RE-DUO-C1800-16G are required to connect to a Routing Matrix)

Table 31: T1600 Routing Engines

Model Number

Name in CLI

Output

RE-600-2048 (EOL details: TSB14373 )

RE-3.0

(RE-600)

First Supported 32-bit

Junos OS Release

8.5

First Supported

64-bit Junos OS

Release

–

Management

Ethernet

Interface

Internal

Ethernet

Interface fxp0 fxp1 fxp2

M10i Multiservice Edge Router Hardware Guide

Table 31: T1600 Routing Engines (continued)

Model Number

RE-1600-2048 (EOL details: TSB14374

RE-A-2000-4096

Name in CLI

Output

RE-4.0

(RE-1600)

RE-A-2000

First Supported 32-bit

Junos OS Release

8.5

First Supported

64-bit Junos OS

Release

–

RE-DUO-C1800-8G RE-TXP-LCC or

RE-DUO-1800

32-bit Junos OS on a T1600 router in a routing matrix: 9.6

NOTE: Junos OS Releases

9.6 through 10.4 support

RE-DUO-C1800-8G only during upgrade to a line-card chassis (LCC) in a routing matrix.

64-bit Junos OS on a

T1600 router in a routing matrix: 9.6

64-bit Junos OS on a standalone T1600 router: 11.1

32-bit Junos OS on a standalone T1600 router: 11.1

em0

RE-DUO-C1800-16G RE-DUO-1800 32-bit Junos OS on a standalone T1600 router:

11.4R2

32-bit Junos OS on a T1600 router in a routing matrix:

11.4R2

64-bit Junos OS on a standalone T1600 router: 11.4R2

64-bit Junos OS on a

T1600 router in a routing matrix: 11.4R2

em0

Management

Ethernet

Interface

Internal

Ethernet

Interface fxp0 fxp0 fxp1 fxp2 em0 bcm0 bcm0 em1 bcm0 em1

T4000 Routing Engines

Table 32 on page 48

lists the Routing Engines supported by the T4000 router.

NOTE: The T4000 router supports 64-bit Junos OS only.

Table 32: T4000 Routing Engines

Model Number

Name in CLI

Output

RE-DUO-C1800-8G RE-DUO-1800

RE-DUO-C1800-16G RE-DUO-1800

First Supported 64-bit Junos OS

Release

Management

Ethernet

Interface

Standalone T4000 router: 12.1

T4000 router in a routing matrix: 13.1

em0

Standalone T4000 router: 12.1R2

T4000 router in a routing matrix: 13.1

em0

Internal Ethernet

Interface bcm0 em1 bcm0 em1

Chapter 5: Host Subsystem Components and Descriptions

The T4000 router supports the CB-LCC control board.

TX Matrix Routing Engines

Table 33 on page 49

lists the Routing Engines supported by the TX Matrix router.

Table 33: TX Matrix Routing Engines

Model Number

Name in CLI

Output

First

Supported

32-bit Junos

OS Release

First

Supported

64-bit Junos

OS Release

Management

Ethernet

Interface

Internal

Ethernet

Interface

RE-600-2048 (EOL details: TSB14373 )

RE-3.0

or RE-3.0

(RE-600)

7.0

– fxp0

RE-1600-2048 (EOL details: TSB14374

RE-4.0 (RE-1600) 7.0

– fxp0 fxp1 fxp2 fxp1 fxp2

RE-A-2000-4096

RE-DUO-C1800-8G

RE-DUO-C1800-16G

RE-A-2000

RE-DUO-1800

8.5

11.4R9

–

11.4R9

fxp0 em0 em0 em0 bcm0 bcm0 em1 bcm0 em1

The TXP router supports two control boards, CB-TX and CB-LCC. The CB-LCC is required for both RE-DUO-C1800-8G and RE-DUO-C1800-16G Routing Engines.

TX Matrix Plus Routing Engines

Table 34 on page 49

lists the Routing Engines supported by the TX Matrix Plus router.

Table 34: TX Matrix Plus Routing Engines

Model Number

Name in CLI

Output

First Supported

32-bit Junos OS

Release

First Supported

64-bit Junos OS

Release

Management

Ethernet

Interface

Internal

Ethernet

Interface

RE-DUO-C2600-16G RE-TXP-SFC or

RE-DUO-2600

32-bit Junos OS: 9.6

64-bit Junos OS: 11.4

em0 ixgbe0 ixgbe1

The TX Matrix Plus router supports the CB-TXP control board.

M10i Multiservice Edge Router Hardware Guide

TX Matrix Plus (with 3D SIBs) Routing Engines

Table 35 on page 50

lists the Routing Engines supported by the TX Matrix Plus router with 3D SIBs.

Table 35: Routing Engines on TX Matrix Plus with 3D SIBs

Model Number

Name in CLI

Output

First Supported

32-bit Junos OS

Release

First Supported

64-bit Junos OS

Release

Management

Ethernet

Interface

Internal

Ethernet

Interface

RE-DUO-C2600-16G RE-TXP-SFC or

RE-DUO-2600

64-bit Junos OS: 11.4

em0 ixgbe0 ixgbe1

Documentation

•

Routing Engine Specifications on page 29

• Understanding Internal Ethernet Interfaces

• Understanding Management Ethernet Interfaces

CHAPTER 6

Line Card Components and Descriptions

•

M10i Flexible PIC Concentrators (FPCs) Description on page 51

•

•

M10i PIC LEDs on page 53

•

M10i End-of-Life PICs Supported on page 56

•

•

M10i PIC/CFEB Compatibility on page 58

M10i Flexible PIC Concentrators (FPCs) Description

Flexible PIC Concentrators (FPCs) house the PICs that connect the router to network media (for information about PICs, see

“M10i PICs Description” on page 51

). On the M10i router, each FPC is built in (it cannot be removed from the chassis as on other M Series platforms) and corresponds to a horizontal row of PIC slots. The two FPCs on the M10i router are numbered 0 and 1 , top to bottom. Each FPC accommodates up to four PICs.

Documentation

•

Connecting M10i PIC Cables on page 121

•

M10i Midplane Description on page 12

•

“M10i Field-Replaceable Units (FRUs)” on page 139 . For information about PICs that use SFPs, see the “Cables and connectors”

M10i PICs Description

PICs provide the physical connection to various network media types. 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 Forwarding Engine 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, IP 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.

PICs are inserted into a slot in Flexible PIC Concentrators (FPCs), FPC0 and FPC1 , which are built in to the chassis. Up to eight PICs install into an M10i router, as shown in

M10i Multiservice Edge Router Hardware Guide

Figure 14 on page 52

. Four PIC slots are located in each Flexible PIC Concentrator (FPC).

The PIC slots on the upper FPC are numbered from 0/0 (zero/zero) through 0/3 , right to left. The PIC slots in the lower FPC are numbered from 1/0 (one/zero) through 1/3 , right to left. The PIC slot numbers are located above FPC0 , and below FPC1 . The number of ports on a PIC depends on the type of PIC.

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.

The M10i router has a maximum throughput of 3.2 Gbps full duplex for each FPC. Inserting a combination of PICs with an aggregate higher than the maximum throughput is supported, but constitutes oversubscription of the FPC.

Figure 14: M10i PIC Location

PICs are hot-removable and hot-insertable. A removed PIC no longer receives or transmits data, and removing or inserting a PIC briefly interrupts forwarding of traffic through the remaining PICs.

Most PICs supported on the M10i router have the following components.

• 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. For more information, see the description for each PIC.

• Ejector lever—Controls the locking system that secures the PIC in the card cage.

Some PICs accept small form-factor pluggables (SFPs), which are fiber-optic transceivers that can be removed from the PIC. Various SFPs have different reach characteristics.

You can mix them in a single PIC and change the combination dynamically. SFPs are hot-removable and hot-insertable, as described in

section for each PIC.

Chapter 6: Line Card Components and Descriptions

Documentation

•

M10i Flexible PIC Concentrators (FPCs) Description on page 51

•

•

Installing an M10i PIC on page 173

•

M10i PIC Serial Number ID Label on page 250

•

Replacing an M10i PIC on page 179

•

Troubleshooting the M10i PICs on page 235

•

Replacing an M10i SFP on page 187

M10i PIC LEDs

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 M10i Multiservice Edge Router

Interface Module Reference .

Documentation

•

Displaying M10i Router Components and Serial Numbers on page 247

•

•

M10i PICs Supported

Table 36 on page 53

lists the PICs supported in the M10i router. The PICs are listed alphabetically by PIC family.

NOTE: The M10i router is now end-of-life. See the JTAC support bulletin

TSB16809 for additional information about the PICs and other associated

FRUs that moved to end-of-life with the router. The

“M10i End-of-Life PICs

Supported” on page 56

topic lists PICs that moved to end-of-life before the

M10i router itself moved to end-of-life.

Table 36: PICs Supported in the M10i Router

Ports Model Number Connector

First

Junos OS

Release

Support PIC Family and Type

ATM2 IQ

M10i Multiservice Edge Router Hardware Guide

Table 36: PICs Supported in the M10i Router (continued)

PIC Family and Type

ATM2 DS3 IQ PIC (M10i Router)

Ports

ATM2 OC3/STM1 IQ PIC (M10i

Router)

ATM2 OC12/STM4 IQ PIC (M10i

Router)

Channelized Enhanced IQ (IQE)

Channelized DS3 and E3 Enhanced

IQ (IQE) PIC (M10i Router)

NOTE: Only the DS3 interface is channelized.

Channelized E1/T1 Enhanced IQ (IQE)

PIC (M10i Router)

Channelized OC3/STM1 Enhanced IQ

(IQE) with SFP (M10i Router)

Channelized OC12/STM4 Enhanced

IQ (IQE) PIC with SFP (M10i Router)

Circuit Emulation

Channelized OC3/STM1 Circuit

Emulation PIC with SFP (M10I Router)

E1/T1 Circuit Emulation PIC (M10i

Router)

Model Number

PE-4DS3-ATM2

PE-2OC3-ATM2-MM

PE-2OC3-ATM2-SMIR

PE-1OC12-ATM2-MM

PE-1OC12-ATM2-SMIR

PE-4CHDS3-E3-IQE-BNC • Standard DS3 BNC coaxial cable interfaces

10.2

PE-10CHE1-T1-IQE-RJ48 • 120-ohm RJ-48C connector

(female)

PE-2CHOC3-STM1-IQE-SFP • LC/PC

10.2

PE-1CHOC12STM4-IQE-SFP • LC/PC 10.2

PE-4CHOC3-CE-SFP

PE-12T1E1-CE-TELCO

Connector

First

Junos OS

Release

Support

Coaxial:

•

10 ft (3.05-m) posilock SMB to BNC (provided)

Four pairs of Rx and Tx coaxial cables

6.1

• SC/PC 6.0

• LC/PC 9.3

• RJ-21

NOTE: Cables are rated for intra-building connections only.

9.3

DS3, E1, E3, and T1

DS3/E3 Enhanced IQ (IQE) PIC (M10i

Router)

E1 PIC (M10i Router) 4

PE-4DS3-E3-IQE-BNC

PE-4E1-RJ48

• Standard DS3 BNC coaxial cable interfaces

10.2

• Four RJ-48 connectors (one per port)

6.0

Chapter 6: Line Card Components and Descriptions

Table 36: PICs Supported in the M10i Router (continued)

PIC Family and Type

E3 IQ PIC (M10i Router)

Ethernet

Fast Ethernet PICs (M10i Router) 4

Ports Model Number

4 PE-4E3-QPP

PE-4FE-TX

Connector

• Standard E3 BNC coaxial cable interfaces

Gigabit Ethernet PIC with SFP (M10i

Router)

Ethernet Enhanced IQ2 (IQ2E)

Gigabit Ethernet Enhanced IQ2 (IQ2E)

PIC with SFP (M10i Router)

Services

Multiservices 100 PIC (M10i Router) 0

Tunnel Services PIC (M10i Router) 0

Serial

EIA-530 PIC (M10i Router) 2

PE-1GE-SFP

PE-4GE-TYPE1-SFP-IQ2E • Duplex LC/PC connector (Rx and Tx)

9.4

PE-MS-100-1

PE-TUNNEL

PE-2EIA530

•

Two-pair, Category 5 unshielded twisted-pair connectivity through an RJ-45 connector

Pinout: MDI noncrossover

6.0

• LC/PC 6.3

• None

8.1

6.0

•

Two DB-25 male connectors

(one per port, included with

PIC)

V.35 requires an EIA-530 to

V.35 cable and connects to a

V.35 DTE 34-pin Winchester type male cable (one per port)

X.21 requires an EIA-530 to

X.21 cable and connects to a

X.21 DTE DB-15 male cable

6.0

First

Junos OS

Release

Support

6.1

SONET/SDH

SONET/SDH OC3/STM1 PIC with SFP

(M10i Router)

SONET/SDH OC3/STM1 Enhanced

IQ (IQE) PIC with SFP (M10i Router)

SONET/SDH OC3/STM1 (Multi-Rate)

PIC with SFP (M10i Router)

PE-2OC3-SON-SFP • LC/PC

PE-4OC3-STM1-IQE-SFP • LC/PC

PE-4OC3-1OC12-SON-SFP • LC/PC

8.4

10.2

8.4

M10i Multiservice Edge Router Hardware Guide

Table 36: PICs Supported in the M10i Router (continued)

PIC Family and Type

SONET/SDH OC12/STM4

(Multi-Rate) PIC with SFP (M10i

Router)

Ports Model Number

PE-1OC12-SON-SFP

Connector

• LC/PC

First

Junos OS

Release

Support

8.4

Documentation

•

M10i End-of-Life PICs Supported on page 56

•

•

M10i PIC/CFEB Compatibility on page 58

M10i End-of-Life PICs Supported

Table 37 on page 56

lists the end-of-life PICs supported in the M10i router. The PICs are listed alphabetically by PIC family.

NOTE: The M10i router is now end-of-life. See the JTAC support bulletin

TSB16809 for additional information about the PICs and other associated

FRUs that moved to end-of-life with the router. The

“M10i PICs Supported” on page 53

topic lists PICs that had not moved to end-of-life before the M10i router itself moved to end-of-life.

Table 37: End-of-Life PICs Supported in the M10i Router

Ports Model Number

First Junos OS

Release Support PIC Family and Type

ATM

ATM DS3 EOL PIC (M10i Router)

ATM E3 EOL PIC (M10i Router)

ATM2 IQ

ATM2 E3 IQ EOL PIC (M10i Router)

Channelized

Multichannel DS3 EOL PIC (M10i Router)

Channelized IQ

Channelized DS3 IQ EOL PIC (M10i Router)

PE-4DS3-ATM

PE-4E3-ATM

PE-2E3-ATM2

PE-2CHDS3

PE-4CHDS3-QPP

6.1

6.0

Chapter 6: Line Card Components and Descriptions

Table 37: End-of-Life PICs Supported in the M10i Router (continued)

PIC Family and Type

Channelized E1 IQ EOL PIC (M10i Router)

Ports

Model Number

PE-10CHE1-RJ48-QPP

PE-10CHE1-RJ48-QPP-N

Channelized OC3 IQ EOL PIC (M10i Router)

Channelized OC12 IQ EOL PIC (M10i Router)

Channelized STM1 IQ EOL PIC (M10i Router)

Channelized T1 IQ EOL PIC (M10i Router)

DS3, E1, E3, T1

DS3 EOL PIC (M10i Router)

E1 PIC (M10i Router)

E3 PIC (M10i Router)

T1 EOL PIC (M10i Router)

Ethernet

Fast Ethernet PICs (M10i Router)

Gigabit Ethernet EOL PIC (M10i Router)

Ethernet IQ

Gigabit Ethernet IQ EOL PIC with SFP (M10i Router) 1

Ethernet IQ2

Gigabit Ethernet IQ2 EOL PIC with SFP (M10i

Router)

Services

Adaptive Services EOL PIC (M10i Router)

PE-1CHOC3-SMIR-QPP

PE-1CHOC12SMIR-QPP

PE-1CHSTM1-SMIR-QPP

PE-10CHT1-RJ48-QPP

PE-2DS3

PE-4DS3

PE-4E1-COAX

PE-2E3

PE-4T1-RJ48

PE-8FE-FX

PE-12FE-TX-MDI

PE-12FE-TX-MDIX

PE-1GE-LH

PE-1GE-LX

PE-1GE-SX

PE-1GE-SFP-QPP

PE-4GE-TYPE1-SFP-IQ2

PE-AS

6.0

7.6R3

6.1

6.0

6.1

6.0

First Junos OS

Release Support

7.6

6.1

6.0

9.1R4

9.2R3

9.3

7.4

6.1

M10i Multiservice Edge Router Hardware Guide

Table 37: End-of-Life PICs Supported in the M10i Router (continued)

PIC Family and Type Ports

Adaptive Services II EOL PIC (M10i Router) 0

Adaptive Services II Layer 2 Services EOL PIC (M10i

Router)

Adaptive Services II FIPS EOL PIC (M10i Router)

ES EOL PIC (M10i Router)

Link Services EOL PIC (M10i Router)

Model Number

PE-AS2

PB-AS2-LAYER2SERVICES

PE-AS2-FIPS

PE-ES-800

PE-LS-4

PE-LS-32

PE-LS-128

PE-PM Monitoring Services EOL PIC (M10i Router)

SONET/SDH

SONET/SDH OC3c/STM1 EOL PIC (M10i Router)

SONET/SDH OC12c/STM4 EOL PIC (M10i Router) 1

PE-2OC3-SON-MM

PE-2OC3-SON-SMIR

PE-4OC3-SON-MM

PE-4OC3-SON-SMIR

PE-1OC12-SON-MM

PE-1OC12-SON-SMIR

PE-1OC12-STM4-IQE-SFP SONET/SDH OC12/STM4 Enhanced IQ (IQE) EOL

PIC with SFP (M10i Router)

SONET/SDH OC48c/STM16 EOL PIC with SFP 1 PE-1OC48-SON-SFP

6.0

10.2

6.4

7.2

6.1

First Junos OS

Release Support

6.4

8.0R2

6.1

Documentation

•

•

M10i PIC/CFEB Compatibility on page 58

•

M10i PIC/CFEB Compatibility

Table 38 on page 58

lists the PICs and CFEBs supported on the M10i router.

Table 38: PICs Supported in the M10i Router

PIC Family and Type Ports Model Number CFEB CFEB-E

ATM

Chapter 6: Line Card Components and Descriptions

Table 38: PICs Supported in the M10i Router (continued)

PIC Family and Type Ports Model Number

ATM DS3 EOL PIC (M10i Router) 4

ATM E3 EOL PIC (M10i Router) 4

PE-4DS3-ATM

EOL (see notification PSN-2003-10-018 )

PE-4E3-ATM

EOL (see notification PSN-2003-10-018 )

ATM2 IQ

ATM2 DS3 IQ

ATM2 E3 IQ

ATM2 OC3/STM1 IQ

ATM2 OC12/STM4 IQ

PE-4DS3-ATM2

PE-2E3-ATM2

PE-2OC3-ATM2-MM

PE-2OC3-ATM2-SMIR

PE-1OC12-ATM2-MM

PE-1OC12-ATM2-SMIR

Channelized

Multichannel DS3 EOL PIC (M10i

Router)

Channelized IQ

Channelized DS3 IQ

Channelized E1 IQ

PE-2CHDS3

EOL (see notification PSN-2004-10-026 )

PE-4CHDS3-QPP

PE-10CHE1-RJ48-QPP-N

Channelized OC12 IQ

Channelized OC3 IQ

Channelized STM1 IQ

Channelized T1 IQ

Channelized IQE

Channelized DS3 and E3

Enhanced IQ (IQE)

Channelized E1/T1 Enhanced IQ

(IQE)

Channelized OC3/STM1

Enhanced IQ (IQE) with SFP

Channelized OC12/STM4

Enhanced IQ (IQE) PIC with SFP

PE-1CHOC12SMIR-QPP

PE-1CHOC3-SMIR-QPP

PE-1CHSTM1-SMIR-QPP

PE-10CHT1-RJ48-QPP

PE-4CHDS3-E3–IQE-BNC

PE-10CHE-T1-IQE-RJ48

PE-2CHOC3-STM1-IQE-SFP

PE-1CHOC12STM4-IQE-SFP

6.1

CFEB

6.1

7.1

6.1

7.4

6.1

9.1R4

9.2R3

9.3

–

CFEB-E

9.4

10.2

M10i Multiservice Edge Router Hardware Guide

Table 38: PICs Supported in the M10i Router (continued)

PIC Family and Type Ports Model Number

Circuit Emulation

Channelized OC3/STM1 Circuit

Emulation

E1/T1 Circuit Emulation 12

PE-4CHOC3-CE-SFP

PE-12T1E1-CE-TELCO

DS3, E1, E3, and T1

DS3

DS3/E3 Enhanced IQ (IQE)

E3 IQ

E3 PIC (M10i Router)

PE-2DS3

PE-4DS3

PE-4DS3-E3-IQE-BNC

PE-4E1-COAX

PE-4E1-RJ48

PE-2E3

PE-4E3-QPP

PE-4T1-RJ48

PE-4E3

EOL (see notification PSN-2003-10-018 )

Ethernet

Fast Ethernet

Gigabit Ethernet EOL PIC (M10i

Router)

PE-4FE-TX

PE-8FE-FX

PE-12FE-TX-MDI

PE-12FE-TX-MDIX

PE-1GE-LH

EOL (see notification PSN-2004-06-014 )

PE-1GE-LX

EOL (see notification PF-HW-0103-001 )

PE-1GE-SX

EOL (see notification PF-HW-0103-001 )

CFEB

9.3

–

6.1

6.0

6.1

CFEB-E

9.5

9.4

10.2

9.4

Chapter 6: Line Card Components and Descriptions

Table 38: PICs Supported in the M10i Router (continued)

PIC Family and Type Ports Model Number

1 PE-1GE-SFP Gigabit Ethernet with SFP

Ethernet IQ

Gigabit Ethernet IQ 1 PE-1GE-SFP-QPP

Ethernet IQ2

Gigabit Ethernet IQ2 4

Ethernet Enhanced IQ2 (IQ2E)

Gigabit Ethernet IQ2E 4

Services

Link Services 0

PE-4GE-TYPE1-SFP-IQ2

PE-4GE-TYPE1-SFP-IQ2E

PE-LS-4

PE-LS-32

PE-LS-128

PE-MS-100-1 Multiservices 100 PIC (M10i

Router)

Tunnel Services PIC (M10i

Router)

Adaptive Services EOL PIC (M10i

Router)

Adaptive Services II EOL PIC

(M10i Router)

Adaptive Services II Layer 2

Services EOL PIC (M10i Router)

Adaptive Services II FIPS EOL PIC

(M10i Router)

ES EOL PIC (M10i Router) 0

Link Services EOL PIC (M10i

Router)

Monitoring Services EOL PIC

(M10i Router)

PE-TUNNEL

PE-AS

EOL (see notification PSN-2005-06-007 )

PE-AS2

EOL (see notification PSN-2007-12-036 )

PB-AS2-LAYER2SERVICES

EOL (see notification PSN-2008-11-080 )

PE-AS2-FIPS

EOL (see notification PSN-20011-09-381 )

PE-ES-800

EOL (see notification PSN-2010-04-734 )

PE-LS-4

EOL (see notification PSN-2008-11-080 )

PE-LS-32

EOL (see notification PSN-2008-11-080 )

PE-LS-128

EOL (see notification PSN-2008-11-080 )

PE-PM

EOL (see notification PSN-2005-06-007 )

Serial

CFEB

6.3

6.1

7.6R3

9.4

6.1

8.1

6.1

6.4

8.0R2

6.0

6.1

CFEB-E

9.4

9.5R2

–

9.4

M10i Multiservice Edge Router Hardware Guide

Table 38: PICs Supported in the M10i Router (continued)

PIC Family and Type Ports Model Number

PE-2EIA530 EIA-530 2

SONET/SDH

SONET/SDH OC3/STM1 PIC with

SFP (M10i Router)

2 PE-2OC3-SON-SFP

SONET/SDH OC3/STM1

Enhanced IQ (IQE) PIC with SFP

(M10i Router)

SONET/SDH OC3/STM1

(Multi-Rate) PIC with SFP (M10i

Router)

SONET/SDH OC12/STM4

Enhanced IQ (IQE) EOL PIC with

SFP (M10i Router)

SONET/SDH OC12/STM4

(Multi-Rate) PIC with SFP (M10i

Router)

SONET/SDH OC48c/STM16 EOL

PIC with SFP

SONET/SDH OC3c/STM1 EOL

PIC (M10i Router)

PE-4OC3-STM1-IQE-SFP

PE-4OC3-1OC12-SON-SFP

PE-1OC12-STM4-IQE-SFP

PE-1OC12-SON-SFP

PE-1OC48-SON-SFP

• SONET/SDH OC3c/STM1 PIC 2

• SONET/SDH OC3c/STM1 PIC 4

PE-2OC3-SON

EOL (see notification PSN-2007-12-037 )

PE-2OC3-SON-MM

PE-2OC3-SON-SMIR

PE-4OC3-SON-MM

PE-4OC3-SON-SMIR

SONET/SDH OC12c/STM4 EOL

PIC (M10i Router)

1 PE-1OC12-SON-MM

EOL (see notification PSN-2007-12-037 )

PE-1OC12-SON-SMIR

EOL (see notification PSN-2007-12-037 )

Documentation

•

•

CFEB

6.1

8.4

–

8.4

–

8.4

6.4

6.0

CFEB-E

9.4

–

9.4

9.6

10.2

9.4

10.2

9.4

CHAPTER 7

Power System Components and

Descriptions

•

•

•

M10i Power Supply LEDs on page 66

•

M10i Power System Description

The router uses either AC or DC power. You can install up to three AC power supplies or four DC load-sharing power supplies at the bottom rear of the chassis, as shown in

Figure

6 on page 12 . The power supplies connect to the midplane, which distributes power to

router components according to their individual voltage requirements. When the power supplies are installed and operational, they automatically share the electrical load.

An enable control pin 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.

Redundant power supplies are hot-removable and hot-insertable, as described in

“M10i

Field-Replaceable Units (FRUs)” on page 139

M10i Multiservice Edge Router Hardware Guide

NOTE: After powering off a power supply, wait at least 60 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 boots as the power supply completes its startup sequence.

If the Routing Engine finishes booting and you need to power off the router again, see

“Powering Off the M10i Router” on page 129

After a power supply is powered on, it can take up to 60 seconds for 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 indicate that the power supply is functioning normally. Ignore error indicators that appear during the first 60 seconds.

Figure 15: M10i Router Power Supplies

Documentation

•

•

Troubleshooting the M10i Power System on page 237

•

•

Replacing an M10i DC Power Supply on page 201

•

M10i AC Power Supply Description

An AC-powered router has up to three load-sharing AC power supplies, located at the bottom rear of the chassis, as shown in

“M10i Power System Description” on page 63 .

. For information about power supply redundancy and replaceability, see

The router must have at least two AC power supplies, and any two AC power supplies can provide full power to the router. Three power supplies are required for redundancy.

Chapter 7: Power System Components and Descriptions

Figure 16 on page 65

shows the power supply and

Table 45 on page 85

lists electrical specifications. For information about the LED, see

“M10i Power Supply LEDs” on page 66 .

Figure 16: AC Power Supply

Documentation

•

General Electrical Safety Guidelines and Electrical Codes for M10i Routers on page 291

•

M10i DC Power Supply Description

A DC-powered router has up to four load-sharing DC power supplies, located at the bottom rear of the chassis, as shown in

“M10i Power System Description” on page 63 .

. For information about power supply redundancy and replaceability, see

The router must have at least two DC power supplies, and any two DC power supplies can provide full power to the router. DC system redundancy requires two power sources from feed A and two power sources from feed B. If one feed fails or is shut down for service, the other feed powers two DC power supplies and can provide full power to the router's components indefinitely.

Figure 17 on page 65

shows the power supply and

Table 47 on page 89

lists electrical specifications. For information about the LED, see

“M10i Power Supply LEDs” on page 66 .

Figure 17: DC Power Supply

Documentation

•

Replacing an M10i DC Power Supply on page 201

•

General Electrical Safety Guidelines and Electrical Codes for M10i Routers on page 291

M10i Multiservice Edge Router Hardware Guide

M10i Power Supply LEDs

Table 39 on page 66

describes the LED on both AC and DC power supplies.

Table 39: States for Power Supply LED

Label Color State Description

OUTPUT OK Green On steadily Power supply is functioning normally, input is occurring, outputs are within range, and the temperature is within range.

Blinking Power supply is not functioning, is starting up, is not properly inserted, or airflow is not sufficient.

Documentation

•

Installing an M10i AC Power Supply on page 191

•

•

Troubleshooting the M10i Power System When LEDs on All Power Supplies Are Off on page 237

•

CHAPTER 8

Switch Fabric Components and

Descriptions

•

M10i Compact Forwarding Engine Board (CFEB) and Enhanced Compact Forwarding

Engine Board (CFEB-E) Description on page 67

•

M10i CFEB and CFEB-E LEDs on page 71

M10i Compact Forwarding Engine Board (CFEB) and Enhanced Compact Forwarding

Engine Board (CFEB-E) Description

The Compact Forwarding Engine Board (CFEB) or Enhanced Compact Forwarding Engine

Board (CFEB-E) performs route lookup, filtering, and switching on incoming data packets, then directs outbound packets to the appropriate FPC for transmission to the network.

It can process 15 million packets per second (Mpps).

One or two CFEBs or CFEB-Es can be installed into the midplane from the rear of the chassis, as shown in

“M10i Field-Replaceable Units (FRUs)” on page 139 . To

CAUTION: The M10i Internet router does not support a mixture of CFEB and

CFEB-E hardware. If you install two devices, they must both be CFEBs or they must both be CFEB-Es.

Only one CFEB or CFEB-E is active at a time; the optional second CFEB or CFEB-E is in standby mode. By default, the CFEB or CFEB-E in slot CFEB 0 is active. To modify the default, include the appropriate cfeb statement at the [edit chassis redundancy] hierarchy level of the configuration, as described in the section about CFEB or CFEB-E redundancy in the Junos OS Administration Library .

NOTE: For specific information about CFEB or CFEB-E components (for example, the amount of SDRAM), issue the show chassis cfeb command.

CFEBs or CFEB-Es are hot-pluggable when you replace a CFEB with a CFEB or a CFEB-E with a CFEB-E, as described in

upgrade from a CFEB to a CFEB-E or to downgrade from a CFEB-E to a CFEB requires a

M10i Multiservice Edge Router Hardware Guide system reboot as described in

“Upgrading or Downgrading an M10i CFEB or CFEB-E” on page 215

Removing the standby CFEB or CFEB-E has no effect on router function. If the active

CFEB or CFEB-E fails or is removed from the chassis, the effect depends on how many

CFEBs or CFEB-Es are installed:

• If there is one CFEB or CFEB-E, forwarding halts until the CFEB or CFEB-E is replaced and functioning again. For a minimum configuration, it takes approximately 2 minutes for the replaced CFEB or CFEB-E to boot and become active; reading in router configuration information can take additional time, depending on the complexity of the configuration.

• If there are two CFEBs or CFEB-Es, forwarding halts while the standby CFEB or CFEB-E boots and becomes active, which takes approximately 1 minute; synchronizing router configuration information can take additional time, depending on the complexity of the configuration.

For CFEB or CFEB-E replacement instructions, see

“Replacing, Upgrading, or Downgrading an M10i CFEB or CFEB-E” on page 212 .

The CFEB or CFEB-E communicates with the Routing Engine using a dedicated 100-Mbps

Fast Ethernet link that transfers routing table data from the Routing Engine to the forwarding table in the integrated ASIC. The link is also used to transfer from the CFEB or CFEB-E to the Routing Engine routing link-state updates and other packets destined for the router that have been received through the router interfaces.

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.

CFEB

Figure 18: CFEB

Chapter 8: Switch Fabric Components and Descriptions

The CFEB has the following major components:

• Processing components:

• 266-MHz CPU and supporting circuitry

• Integrated ASIC

• 33-MHz PCI bus

• Storage components:

• 128-MB SDRAM for packet memory

• 128-MB SDRAM for the microkernel

• 8-MB SSRAM for route lookup

• 4-MB SSRAM for control memory

• System interfaces:

• 100-Mbps Ethernet link for internal interface to the Routing Engine

• 19.44-MHz reference clock that generates clock signal for SONET/SDH PICs

• I2C controller to read the I2C/EEPROMs in the PICs and temperature sensors

• I2C/EEPROM containing the serial number and revision level

• Two 512-KB boot flash EPROMs (programmable on the board)

• One PowerPC 8245 integrated processor

• Three LEDs—A green LED labeled OK , a red LED labeled FAIL , and a blue LED labeled

MASTER indicate CFEB status. See

“M10i CFEB and CFEB-E LEDs” on page 71 .

• Online/Offline button—Prepares the CFEB for removal from the router when pressed.

• Ejector levers—Control the locking system that secures the CFEB in the chassis.

M10i Multiservice Edge Router Hardware Guide

CFEB-E

The CFEB-E provides the following enhanced features:

• Increased number of logical interfaces.

• Increased route, nexthop, and interface lookup memory.

• Increased FPC throughput.

• Enhanced class of service features, including:

• More queues and priority levels

• Increased drop precedence per queue

• Excess bandwidth allocation in proportion to weights

• Hierarchical policing

• Increased number of WRED profiles

• Independent EXP and DSCP rewrite

• Independent Layer 2 and Layer 3 classification on same port

Figure 19: CFEB-E

The CFEB-E has the following major components:

• Processing components:

• 1-GHz CPU and supporting circuitry

• Integrated ASIC

• 33-MHz PCI bus

• Storage components:

• Three 256-MB SDRAMs for packet memory

• 1-GB SDRAM for the microkernel

Chapter 8: Switch Fabric Components and Descriptions

• Two 64-MB RLDRAMs for route lookup

• Two 64-MB RLDRAMs for control memory

• System interfaces:

• 100-Mbps link for internal interface to the Routing Engine

• 19.44-MHz reference clock—Generates clock signal for SONET/SDH PICs

• I2C controller to read the I2C/EEPROMs in the PICs and temperature sensors

• I2C/EEPROM containing the serial number and revision level

• Two 512-KB boot flash EPROMs (programmable on the board)

• One MPC8545 integrated processor with 1-GB DDR2 SDRAM

• Three LEDs—A green LED labeled OK , a red LED labeled FAIL , and a blue LED labeled

MASTER indicate CFEB-E status.

• Offline button—Prepares the CFEB-E for removal from the router when pressed.

• Ejector levers—Control the locking system that secures the CFEB-E in the chassis.

Documentation

•

M10i Packet Forwarding Engine Architecture Overview on page 5

•

Installing an M10i CFEB or CFEB-E on page 211

• Configuring CFEB Redundancy on the M10i Router

•

•

M10i Compact Forwarding Engine Board (CFEB) and Enhanced Compact Forwarding

M10i CFEB and CFEB-E LEDs

Three LEDs—A green LED labeled OK , a red LED labeled FAIL , and a blue LED labeled

MASTER indicate CFEB-E status.

Table 40: States for CFEB or CFEB-E LEDs

Label Color State Description

OK Green On steadily CFEB/CFEB-E is running normally.

FAIL Red

Blinking

Off

CFEB/CFEB-E is starting up.

CFEB/CFEB-E is offline or is functioning as the backup CFEB/CFEB-E.

On steadily CFEB/CFEB-E is not operational or is in reset mode.

Off CFEB/CFEB-E is functioning properly

M10i Multiservice Edge Router Hardware Guide

Table 40: States for CFEB or CFEB-E LEDs (continued)

Label Color State Description

MASTER Blue On steadily CFEB/CFEB-E is functioning as master.

Off CFEB/CFEB-E is not functioning as master.

Documentation

•

Engine Board (CFEB-E) Description on page 67

PART 2

Site Planning, Preparation, and

Specifications

•

Preparation Overview on page 75

•

AC Power Requirements and Specifications on page 85

•

DC Power Requirements and Specifications on page 89

•

Network Cable and Transceiver Planning on page 93

•

Management Cable and Transceiver Specifications and Pinouts on page 99

M10i Multiservice Edge Router Hardware Guide

CHAPTER 9

Preparation Overview

•

•

•

Spacing of Mounting Holes on page 78

•

•

Connection to Building Structure on page 79

•

Clearance Requirements for Airflow and Hardware Maintenance on page 79

•

M10i Router Environmental Specifications on page 80

•

M10i Chassis Grounding Cable and Lug Specifications on page 81

•

“M10i Router Environmental

M10i Router Site Preparation Checklist

The checklist in

Table 41 on page 75

summarizes the tasks you need to perform when preparing a site for router installation.

Table 41: Site Preparation Checklist

Item or Task For More Information Performed By Date

Environment

Verify that environmental factors such as temperature and humidity do not exceed router tolerances.

Specifications” on page 80

Power

Measure distance between external power sources and router installation site.

Locate sites for connection of system grounding.

Calculate the power consumption and requirements.

“M10i Router DC Power Supply

Specifications” on page 89

“M10i Router AC Power Supply

Specifications” on page 85

“M10i Chassis Grounding Cable and

Lug Specifications” on page 81

“M10i Router Power Requirements” on page 82

M10i Multiservice Edge Router Hardware Guide

Table 41: Site Preparation Checklist (continued)

Item or Task For More Information

Hardware Configuration

Choose the configuration.

Rack

Verify that your rack meets the minimum requirements for the installation of the router.

“Installation Safety Warnings for

Juniper Networks Devices” on page 269

Plan rack location, including required space clearances.

“Clearance Requirements for Airflow and Hardware Maintenance” on page 79

“M10i Rack Size and Strength” on page 77

If a rack is used, secure rack to floor and building structure.

“Connection to Building Structure” on page 79

Cables

Acquire cables and connectors:

•

Determine the number of cables needed based on your planned configuration.

Review the maximum distance allowed for each cable. Choose the length of cable based on the distance between the hardware components being connected.

“Calculating Power Budget for

Fiber-Optic Cable for M Series, MX

Series, and T Series Routers” on page 95

“Calculating Power Margin for

Fiber-Optic Cable for M Series, MX

Series, and T Series Routers” on page 95

Plan the cable routing and management.

“Maintaining the M10i PICs and PIC

Cables” on page 223

Performed By Date

Documentation

•

•

•

M10i Router Environmental Specifications on page 80

M10i Router Physical Specifications

Table 42 on page 77

summarizes physical specifications for the router chassis.

Chapter 9: Preparation Overview

Table 42: M10i Chassis Physical Specifications

Description Weight

Chassis dimensions 79 lb (35.8 kg) maximum configuration

57 lb (25.9 kg) minimum configuration

Width Depth

•

17.5 in. (44.5 cm) for sides of chassis

19 in. (48.3 cm) with mounting brackets

18 in. (45.7 cm)

Height

8.7 in. (22.1 cm)

Documentation

•

•

•

“Clearance Requirements for Airflow and Hardware

M10i Rack Size and Strength

The router is designed for installation in a 19-in. rack as defined in Cabinets, Racks, Panels, and Associated Equipment (document number EIA-310-D) published by the Electronics

Components Industry Association ( http://www.ecianow.org/ ).

With the use of adapters, the router is designed to fit into a 600-mm-wide and

600-mm-deep rack, as defined in the four-part Equipment Engineering (EE); European telecommunications 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.

The rack rails must be spaced widely enough to accommodate the router chassis's external dimensions: 8.7 in. (22.1 cm) high, 18 in. (45.7 cm) deep, and 17.5 in. (44.5 cm) wide. The outer edges of the mounting brackets extend the width to 19 in. (48.3 cm). The spacing of rails and adjacent racks must also allow for the clearances around the router and rack that are specified in

Maintenance” on page 79 .

The chassis height of 8.7 in. (22.1 cm) is approximately 5 U. A U is the standard rack unit defined in Cabinets, Racks, Panels, and Associated Equipment (document number

EIA-310-D) published by the Electronics Components Industry Association. You can stack eight router in a rack that has at least 40 U (70 in. or 1.78 m) of usable vertical space.

The rack must be strong enough to support the weight of the fully configured router, up to approximately 79 lb (35.8 kg). If you stack eight fully configured routers in one rack, it must be capable of supporting about 632 lb (286.7 kg).

M10i Multiservice Edge Router Hardware Guide

Figure 20: Typical Open-Frame Rack

Documentation

•

•

Installation Safety Warnings for Juniper Networks Devices on page 269

•

•

Spacing of Mounting Holes on page 78

Spacing of Mounting Holes

The holes in the mounting brackets are spaced at 1 U (1.75 in. or 4.45 cm), so the router can be mounted in any rack that provides holes spaced at that distance.

Documentation

•

•

Installation Safety Warnings for Juniper Networks Devices on page 269

•

•

“Installation Safety Warnings for Juniper

Chapter 9: Preparation Overview

Connection to Building Structure

Always secure the rack to the structure of the building. If your geographical area is subject to earthquakes, bolt the rack to the floor. For maximum stability, also secure the rack to ceiling brackets. For more information, see

Networks Devices” on page 269

Documentation

•

•

•

Clearance Requirements for Airflow and Hardware Maintenance

When planning the installation site, you must allow sufficient clearance around the rack

(see

Figure 21 on page 80 ):

• For the cooling system to function properly, the airflow around the chassis must be unrestricted.

Figure 11 on page 19

depicts the airflow in the router. 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.

NOTE: We recommend that you do not install the router in a cabinet. If you mount the router in a cabinet, be sure that ventilation is sufficient to prevent overheating.

• For service personnel to remove and install hardware components, there must be adequate space at the front and back of the router. At least 24 in. (61 cm) is required both in front of and behind the router. NEBS GR-63 recommends that you allow at least 30 in. (76.2 cm) in front of the rack and 24 in. (61 cm) behind the rack.

M10i Multiservice Edge Router Hardware Guide

Figure 21: Chassis Dimensions and Clearance Requirements

Documentation

•

•

Installation Safety Warnings for Juniper Networks Devices on page 269

•

•

M10i Router Environmental Specifications

Table 43 on page 80

specifies the environmental specifications required for normal router operation. In addition, the site should be as dust-free as possible.

Table 43: M10i Router Environmental Specifications

Description Value

Altitude

Relative humidity

Temperature

No performance degradation to 10,000 ft (3048 m)

Normal operation ensured in relative humidity range of 5% to 90%, noncondensing

Normal operation ensured in temperature range of 32°F (0°C) to

104°F (40°C)

Nonoperating storage temperature in shipping crate: –40°F (–40°C) to 158°F (70°C)

Chapter 9: Preparation Overview

Table 43: M10i Router Environmental Specifications (continued)

Description Value

Seismic Tested to meet Telcordia Technologies Zone 4 earthquake requirements

Maximum thermal output •

•

AC: 3276 BTU/hour (960 W)

DC: 1965 BTU/hour (576 W)

NOTE: Install the router only in restricted areas, such as dedicated equipment rooms and equipment closets, in accordance with Articles 110-16, 110-17, and

110-18 of the National Electrical Code, ANSI/NFPA 70.

Documentation

•

•

•

General Safety Guidelines for Juniper Networks Devices on page 261

•

•

General Safety Warnings for Juniper Networks Devices on page 262

M10i Chassis Grounding Cable and Lug Specifications

You must supply one 14-AWG (2.08 mm

) single-strand-count wire cable for the grounding the router.

CAUTION: Before router installation begins, a licensed electrician must attach a cable lug to the grounding cable that you supply. One terminal lug, 14-AWG

(2.08 mm

) , two hole for grounding is provided in the accessory box.

Figure 22 on page 82

shows the grounding points on the router above the power supplies.

M10i Multiservice Edge Router Hardware Guide

Figure 22: Grounding Cable and Grounding Points

Documentation

•

Grounding the M10i Router on page 117

•

M10i Router Power Requirements

Table 44 on page 82

lists the power requirements for various hardware components when the router is operating under typical voltage conditions. For PIC power requirements, see the M10i Multiservice Edge Router Interface Module Reference .

Table 44: Component Power Requirements

Component

Power Requirement (Watts)

@ 48 V

Power Requirement (Amps) @

48 V

1.8 A (approximate) Base system including two HCMs, two power supplies, and one Routing Engine (with fans running at normal speed)

88.3

Routing Engine

CFEB/CFEB-E

33.6

67.2

0.7 A

1.4 A

Chapter 9: Preparation Overview

Table 44: Component Power Requirements (continued)

Component

Power Requirement (Watts)

@ 48 V

Power Requirement (Amps) @

48 V

HCM 10 0.2 A

You can use the information in

Table 44 on page 82

and the M10i Multiservice Edge Router

Interface Module Reference to calculate power consumption for various hardware configurations, input current from a different source voltage, and thermal output, as shown in the following examples. (The examples use a generalized value for PICs of

0.625 A @ 48 V each.)

• Power consumption for minimum configuration:

Base system + 1 CFEB + 1 PIC =

1.8 A + 0.625 A = 2.425 A @ 48 V = 116.4 W DC

• Power consumption for maximum configuration:

Base system + 2 CFEBs + 8 PICs + second Routing Engine =

1.8 A + 2(1.4 A) + 8(0.625_A) + 0.7 A =

1.8 A + 2.8 A + 5_A + 0.7 A = 10.3 A @ 48 V = 494.4 W DC

• Input current from a DC source other than 48 V (based on maximally configured router; applies to DC power supply only):

(54 VDC input) x (input current X) = (48 VDC input) x (input current Y)

54 x X = 48 x 8.9 A

X = 48 x 8.9 A / 54 = 7.9 A

• Example of calculating system thermal output for an AC-powered router:

Watts DC/65% AC PEM efficiency/0.293 = BTU/hr

494.4/0.65/0.293 = 2595.96 BTU/hr

• Example of calculating System thermal output for aDC-powered router:

Watts DC/0.293 = BTU/hr

494.4/0.293 = 1687.37 BTU/hr

NOTE: We recommend that you provision at least 9.1 A @ 48 VDC and use a facility circuit breaker rated for 15 A minimum. Doing so enables you to operate the router in any configuration without upgrading the power infrastructure, and allows the router to function at full capacity using multiple power supplies.

Documentation

•

M10i Router AC Power Supply Specifications on page 85

M10i Multiservice Edge Router Hardware Guide

CHAPTER 10

AC Power Requirements and

Specifications

•

M10i Router AC Power Supply Specifications on page 85

•

M10i AC Power Cord Specifications on page 86

M10i Router AC Power Supply Specifications

Table 45 on page 85

lists electrical specifications for the AC Power Supply.

Table 45: Electrical Specifications for AC Power Supply

Description Specification

Maximum power output

AC input voltage

AC input line frequency

293 WDC

Nominal: 100, 120, 200, 208, 220, 240 VAC

Operating range: 90–264 VAC

47–63 Hz

AC input current rating

Output voltages

6–3 A

+3.3 V @ 40 A, +2.5 V @ 20 A, +5.0 V @ 15 A, +12 V@ 3 A

Documentation

•

•

Replacing an M10i AC Power Cord on page 199

•

•

M10i AC Power Cord Specifications on page 86

•

M10i Multiservice Edge Router Hardware Guide

M10i AC Power Cord Specifications

Detachable AC power cords, each 2.5 m (approximately 8 ft) long, are supplied with the router. The C13 appliance coupler at the female end of the cord inserts into the AC appliance inlet coupler, type C14 as described by International Electrotechnical

Commission (IEC) standard 60320. The plug at the male end of the AC power cord fits into the power source receptacle that is standard for your geographical location.

NOTE: In North America, AC power cords must not exceed 4.5 m

(approximately 14.75 ft) in length, to comply with National Electrical Code

(NEC) Sections 400-8 (NFPA 75, 5-2.2) and 210-52, and Canadian Electrical

Code (CEC) Section 4-010(3). The cords supplied with the router are in compliance.

Table 46 on page 86

provides specifications and

Figure 23 on page 86

depicts the plug on the AC power cord provided for each country or region.

Table 46: AC Power Cord Specifications

Country Electrical Specification Plug Type

Australia 240 VAC, 50 Hz AC

Europe (except Italy and United Kingdom) 220 or 230 VAC, 50 Hz AC

Italy

North America

230 VAC, 50 Hz AC

120 VAC, 60 Hz AC

SAA/3

CEE 7/7

CEI 23-16

NEMA 5-15P

United Kingdom 240 VAC, 50 Hz AC BS89/10

Figure 23: AC Plug Types

Australia

(SAA/3)

China

(PSB-10)

Europe

(CEE 7/7)

Italy

(CEI 23-16/VII)

Japan

(L6-20P)

North America

(L6-20P)

North America

NEMA

(L6-20)

(BS89/13)

Chapter 10: AC Power Requirements and Specifications

NOTE: AC power cords must not block access to router components or drape where people could trip on them.

Documentation

•

Connecting Power on an AC-Powered M10i Router on page 123

•

•

Replacing an M10i AC Power Cord on page 199

•

•

M10i Router AC Power Supply Specifications on page 85

•

M10i Multiservice Edge Router Hardware Guide

CHAPTER 11

DC Power Requirements and

Specifications

•

M10i Router DC Power Supply Specifications on page 89

•

M10i DC Power Cable and Lug Specifications on page 90

M10i Router DC Power Supply Specifications

Table 47 on page 89

lists electrical specifications for the DC power supply.

Table 47: Electrical Specifications for DC Power Supply

Description Specification

Maximum power output

DC input voltage

Input DC current rating

293 W

Nominal: –48, –60 VDC

Operating range: –40.5 to –72 VDC

9.1 A @ –48 V

Output voltages +3.3 V @ 40 A, +2.5 V @ 20 A, +5.0 V @ 15 A, +12 V@ 3 A

NOTE: The DC power supply requires –42 VDC to power on.

NOTE: The DC power supplies are marked –48 VDC. This is the nominal voltage associated with the battery circuit. Any higher voltages are associated only with float voltages for the charging function.

Documentation

•

Replacing an M10i DC Power Supply on page 201

•

•

Replacing an M10i DC Power Cable on page 206

M10i Multiservice Edge Router Hardware Guide

•

M10i DC Power Cable and Lug Specifications on page 90

•

M10i DC Power Cable and Lug Specifications

You must provide two 14-AWG (2.08 mm

) single-strand-count wire cables for each power supply.

CAUTION: Before router installation begins, a licensed electrician must attach a cable lug to the DC power cables that you supply. The terminal fork lugs,

14-AWG (2.08 mm

), are provided in the accessories box for the DC power cables.

WARNING: For field-wiring connections, use copper conductors only.

Figure 24 on page 90

shows how to attach the power cables. The DC power cables insert into the field-wiring terminals located on each power supply—the input terminal is labeled

-48V and the return terminal is labeled RTN .

Figure 24: DC Power Cable Connections

Chapter 11: DC Power Requirements and Specifications

NOTE: DC power cables must not block access to router components or drape where people could trip on them.

The DC power supplies in slots P/S 0 and P/S 1 must be powered by dedicated power feeds derived from feed A, and the DC power supplies in slots P/S 2 and P/S 3 must be powered by dedicated power feeds derived from feed B. This configuration provides the commonly deployed A/B feed redundancy for the system. Most sites distribute DC power through a main conduit that leads to frame-mounted DC power distribution panels, one of which might be located at the top of the rack that houses the router. A pair of cables

(one input and one return) connects the field-wiring terminals to the power distribution panel.

Documentation

•

Connecting Power on an DC-Powered M10i Router on page 125

•

•

Disconnecting Power on an DC-Powered M10i Router on page 209

M10i Multiservice Edge Router Hardware Guide

CHAPTER 12

Network Cable and Transceiver Planning

•

Attenuation and Dispersion in Fiber-Optic Cable on M Series, MX Series, and T Series

Signal Loss in Multimode and Single-Mode Fiber-Optic Cable for M10i

•

Routers on page 94

•

Calculating Power Budget for Fiber-Optic Cable for M Series, MX Series, and T Series

Calculating Power Margin for Fiber-Optic Cable for M Series, MX Series, and T Series

•

Signal Loss in Multimode and Single-Mode Fiber-Optic Cable for M10i Routers on page 94

Attenuation and Dispersion in Fiber-Optic Cable on M Series, MX Series, and T Series

Routers

Correct functioning of an optical data link depends on modulated light reaching the receiver with enough power to be demodulated correctly.

Attenuation is the reduction in power of the light signal as it is transmitted. Attenuation is caused by passive media components, such as cables, cable splices, and connectors. While attenuation is significantly lower for optical fiber than for other media, it still occurs in both multimode and single-mode transmission. An efficient optical data link must have enough light available to overcome attenuation.

Dispersion is the spreading of the signal in time. The following two types of dispersion can affect an optical data link:

• Chromatic dispersion—Spreading of the signal in time resulting from the different speeds of light rays.

• Modal dispersion—Spreading of the signal in time resulting from the different propagation modes in the fiber.

For multimode transmission, modal dispersion, rather than chromatic dispersion or attenuation, usually limits the maximum bit rate and link length. For single-mode transmission, modal dispersion is not a factor. However, at higher bit rates and over longer distances, chromatic dispersion rather than modal dispersion limits maximum link length.

An efficient optical data link must have enough light to exceed the minimum power that the receiver requires to operate within its specifications. In addition, the total dispersion must be less than the limits specified for the type of link in Telcordia Technologies

M10i Multiservice Edge Router Hardware Guide document GR-253-CORE (Section 4.3) and International Telecommunications Union

(ITU) document G.957.

When chromatic dispersion is at the maximum allowed, its effect can be considered as a power penalty in the power budget. The optical power budget must allow for the sum of component attenuation, power penalties (including those from dispersion), and a safety margin for unexpected losses.

Documentation

•

•

Calculating Power Budget for Fiber-Optic Cable for M Series, MX Series, and T Series

Calculating Power Margin for Fiber-Optic Cable for M Series, MX Series, and T Series

•

Attenuation and Dispersion in Fiber-Optic Cable on M Series, MX Series, and T Series

Signal Loss in Multimode and Single-Mode Fiber-Optic Cable for M10i Routers

Multimode fiber is large enough in diameter to allow rays of light to reflect internally

(bounce off the walls of the fiber). Interfaces with multimode optics typically use LEDs as light sources. LEDs are not coherent sources, however. They spray varying wavelengths of light into the multimode fiber, which reflects the light at different angles. Light rays travel in jagged lines through a multimode fiber, causing signal dispersion. When light traveling in the fiber core radiates into the fiber cladding, higher-order mode loss (HOL) results. Together these factors limit the transmission distance of multimode fiber compared to single-mode fiber.

Single-mode fiber is so small in diameter that rays of light can reflect internally through one layer only. Interfaces with single-mode optics use lasers as light sources. Lasers generate a single wavelength of light, which travels in a straight line through the single-mode fiber. Compared with multimode fiber, single-mode fiber has higher bandwidth and can carry signals for longer distances. It is consequently more expensive.

The router uses optical lasers for SONET/SDH PIC single-mode interfaces. These optics comply with IR-1 of Bellcore GR-253-CORE Issue 2, December 1995 and ANSI TI.105.06.

For information about the maximum transmission distances and wavelength ranges supported by multimode and single-mode (ATM and SONET/SDH) PIC interfaces, see the interface module reference for your device. Exceeding the maximum transmission distances can result in significant signal loss, which causes unreliable transmission.

Documentation

•

Calculating Power Budget for Fiber-Optic Cable for M Series, MX Series, and T Series

•

Calculating Power Margin for Fiber-Optic Cable for M Series, MX Series, and T Series

•

Signal Loss in Multimode and Single-Mode Fiber-Optic Cable for M10i Routers on page 94

Chapter 12: Network Cable and Transceiver Planning

Calculating Power Budget for Fiber-Optic Cable for M Series, MX Series, and T Series

Routers

To ensure that fiber-optic connections have sufficient power for correct operation, you need to calculate the link's power budget, which is the maximum amount of power it can transmit. When you calculate the power budget, you use a worst-case analysis to provide a margin of error, even though all the parts of an actual system do not operate at the worst-case levels. To calculate the worst-case estimate of power budget ( P

), you assume minimum transmitter power ( P

) and minimum receiver sensitivity ( P

= P

– P

The following hypothetical power budget equation uses values measured in decibels

(dB) and decibels referred to one milliwatt (dBm):

= P

– P

= –15 dBm – (–28 dBm)

= 13 dB

Documentation

•

•

Attenuation and Dispersion in Fiber-Optic Cable on M Series, MX Series, and T Series

Calculating Power Margin for Fiber-Optic Cable for M Series, MX Series, and T Series

•

Signal Loss in Multimode and Single-Mode Fiber-Optic Cable for M10i Routers on page 94

Calculating Power Margin for Fiber-Optic Cable for M Series, MX Series, and T Series

Routers

After calculating a link's power budget you can calculate the power margin ( P

), which represents the amount of power available after subtracting attenuation or link loss ( LL ) from the power budget ( P

). A worst-case estimate of P

M assumes maximum LL :

= P

– LL

A P

M greater than zero indicates that the power budget is sufficient to operate the receiver.

Factors that can cause link loss include higher-order mode losses (HOL), modal and chromatic dispersion, connectors, splices, and fiber attenuation.

Table 48 on page 96

lists an estimated amount of loss for the factors used in the following sample calculations.

For information about the actual amount of signal loss caused by equipment and other factors, refer to vendor documentation.

M10i Multiservice Edge Router Hardware Guide

Table 48: Estimated Values for Factors Causing Link Loss

Link-Loss Factor Estimated Link-Loss Value

Higher-order mode losses Single-mode—None

Multimode—0.5 dB

Modal and chromatic dispersion

Connector

Splice

Fiber attenuation

Single-mode—None

Multimode—None, if product of bandwidth and distance is less than 500 MHz-km

0.5 dB

Single-mode—0.5 dB/km

Multimode—1 dB/km

The following example uses the estimated values in

Table 48 on page 96

to calculate link loss ( LL ) for a 2-km-long multimode link with a power budget ( P

) of 13 dB:

• Fiber attenuation for 2 km @ 1.0 dB/km= 2 dB

• Loss for five connectors @ 0.5 dB per connector = 5(0.5 dB) = 2.5 dB

• Loss for two splices @ 0.5 dB per splice =2(0.5 dB) = 1 dB

• Higher-order mode loss = 0.5 dB

• Clock recovery module = 1 dB

The power margin ( P

) is calculated as follows:

= P

– LL

= 13 dB – 2 km (1.0 dB/km) – 5 (0.5 dB) – 2 (0.5 dB) – 0.5 dB [HOL] – 1 dB [CRM]

= 13 dB – 2 dB – 2.5 dB – 1 dB – 0.5 dB – 1 dB

= 6 dB

The following sample calculation for an 8-km-long single-mode link with a power budget

( P

) of 13 dB uses the estimated values from

Table 48 on page 96

to calculate link loss

( LL ) as the sum of fiber attenuation (8 km @ 0.5 dB/km, or 4 dB) and loss for seven connectors (0.5 dB per connector, or 3.5 dB). The power margin ( P

) is calculated as follows:

= P

– LL

= 13 dB – 8 km (0.5 dB/km) – 7(0.5 dB)

= 13 dB – 4 dB – 3.5 dB

Chapter 12: Network Cable and Transceiver Planning

= 5.5 dB

In both examples, the calculated power margin is greater than zero, indicating that the link has sufficient power for transmission and does not exceed the maximum receiver input power.

Documentation

•

•

Attenuation and Dispersion in Fiber-Optic Cable on M Series, MX Series, and T Series

Calculating Power Budget for Fiber-Optic Cable for M Series, MX Series, and T Series

•

Routing Engine Interface Cable and Wire Specifications for M10i Routers on page 99

M10i Multiservice Edge Router Hardware Guide

CHAPTER 13

Management Cable and Transceiver

Specifications and Pinouts

•

•

RJ-45 Connector Pinouts for the M10i Routing Engine MGMT Port on page 100

•

DB-9 Connector Pinouts for the M10i Routing Engine AUX/MODEM and CONSOLE

Ports on page 100

Routing Engine Interface Cable and Wire Specifications for M10i Routers

Port

For management and service operations, you connect the Routing Engine to an external console or management network. (For more information, see

“M10i Routing Engine

Description” on page 21

Table 49 on page 99

lists the specifications for the cables that connect to management ports.

Table 49: Cable Specifications for Routing Engine Management Ports

Cable

Specification Cable Supplied

Maximum

Length

Router

Receptacle

DB-9 male Routing Engine console or auxiliary interface

Routing Engine

Ethernet interface

RS-232

(EIA-232) serial

One 6-ft

(1.83-m) length with DB-9/DB-9 connectors

6 ft (1.83 m)

Category 5 cable or equivalent suitable for

100Base-T operation

One 15-ft

(4.92-m) length with

RJ-45/RJ-45 connectors

328 ft (100 m) RJ-45 autosensing

Documentation

•

Replacing an M10i Ethernet Management Cable on page 171

•

•

Replacing an M10i Console or Auxiliary Cable on page 171

M10i Multiservice Edge Router Hardware Guide

RJ-45 Connector Pinouts for the M10i Routing Engine MGMT Port

The port on the Routing Engine labeled MGMT is an autosensing 10/100-Mbps Ethernet

RJ-45 receptacle that accepts an Ethernet cable for connecting the Routing Engine to a management LAN (or another device that supports out-of-band management). For more information, see

“M10i Routing Engine Interface Ports” on page 29 .

Table 50 on page 100

describes the RJ-45 connector pinout.

Table 50: RJ-45 Connector Pinout

Pin Signal

1 TX+

TX-

RX+

Termination network

RX-

Termination network

Documentation

•

Maintaining the M10i Routing Engine on page 222

•

•

Replacing an M10i Ethernet Management Cable on page 171

•

•

DB-9 Connector Pinouts for the M10i Routing Engine AUX/MODEM and CONSOLE

Ports on page 100

DB-9 Connector Pinouts for the M10i Routing Engine AUX/MODEM and CONSOLE

Ports

The ports on the Routing Engine labeled AUX/MODEM and CONSOLE are DB-9 receptacles that accept RS-232 (EIA-232) cable. The AUX/MODEM port connects the Routing Engine to a laptop, modem, or other auxiliary unit, and the CONSOLE port connects it to a management console. The ports are configured as data terminal equipment (DTE). For more information, see

“M10i Routing Engine Interface Ports” on page 29 .

Table 51 on page 101

describes the DB-9 connector pinouts.

Chapter 13: Management Cable and Transceiver Specifications and Pinouts

Table 51: DB-9 Connector Pinout

Pin Signal Direction

DCD

RxD

TxD

DTR

<–

–>

Ground

DSR

RTS

CTS

RING

—

<–

–>

<–

Description

Carrier Detect

Receive Data

Transmit Data

Data Terminal Ready

Signal Ground

Data Set Ready

Request To Send

Clear To Send

Ring Indicator

Documentation

•

Maintaining the M10i Routing Engine on page 222

•

•

Replacing an M10i Console or Auxiliary Cable on page 171

•

•

RJ-45 Connector Pinouts for the M10i Routing Engine MGMT Port on page 100

101

M10i Multiservice Edge Router Hardware Guide

PART 3

Initial Installation and Configuration

•

Installation Overview on page 105

•

Unpacking the M10i on page 107

•

Installing the M10i into a Rack on page 111

•

Connecting the M10i to Ground on page 117

•

Connecting the M10i to External Devices on page 119

•

Providing Power to the M10i on page 123

•

Configuring the Junos Software on page 131

103

M10i Multiservice Edge Router Hardware Guide

CHAPTER 14

Installation Overview

•

Site Preparation Checklist” on page 75 , you are ready to unpack and install the router. It

Overview of M10i Router Installation

After you have verified that your installation site is prepared as described in

“M10i Router

is important to proceed through the installation process in the following order:

Review the safety guidelines explained in

“General Safety Guidelines for Juniper

Networks Devices” on page 261

Unpack the router and verify that all parts have been received.

See

“Unpacking the M10i Router” on page 107

and

“Verifying the M10i Router Parts

Received” on page 109

If necessary, move the mounting brackets.

See

“Moving the Mounting Brackets” on page 111

Install the router.

See

“Installing the M10i Router into a Rack” on page 113 .

Connect the grounding cable.

See

“Grounding the M10i Router” on page 117 .

Connect a cables to a management device.

See

“Connecting to an M10I Management Console or Auxiliary Device” on page 120

Connect the AC power cords or DC power cables.

See

“Connecting Power on an AC-Powered M10i Router” on page 123

“Connecting

Power on an DC-Powered M10i Router” on page 125 .

105

M10i Multiservice Edge Router Hardware Guide

Power on the router as described in

“Powering On an AC-Powered M10i Router” on page 124

“Powering On a DC-Powered M10i Router” on page 128

Perform the initial system startup.

See

“Initially Configuring the M10i Router” on page 131

10.

Connect cables to the PICs. This can be performed either before or after the router is powered on. However, you can check the LEDs after you connect the cables if the router is powered on.

CHAPTER 15

Unpacking the M10i

•

Tools and Parts Required to Unpack the M10i Router on page 107

•

Unpacking the M10i Router on page 107

•

Verifying the M10i Router Parts Received on page 109

Tools and Parts Required to Unpack the M10i Router

To unpack the router and prepare for installation, you need the following tools:

• Utility knife for cutting the sealing tape on the shipping carton

• Phillips (+) screwdriver, number 2

Documentation

•

•

•

“Verifying the M10i Router Parts Received” on page 109 .

Unpacking the M10i Router

The router is shipped in a cardboard carton, held in place with foam packing material.

The crate also contains an accessory box, the front-mounting shelf, and the Quick Start.

NOTE: The router is maximally protected inside the shipping carton. Do not unpack it until you are ready to begin installation.

To unpack the router:

Move the shipping carton to a staging area as close to the installation site as possible.

Position the carton so that the arrows are pointing up.

Using a utility knife, cut through the sealing tape on the top seam of the carton. Open the top flaps of the carton.

107

M10i Multiservice Edge Router Hardware Guide

Remove the accessory box and packing material from the top of the router.

Open the accessory box and verify the contents against the parts inventory on the label attached to the box.

Remove the router from the shipping carton.

Verify the chassis components received against the packing list included with the router. A generic parts inventory appears in

Save the shipping carton, packing materials, and pallet in case you later need to move or ship the router.

Figure 25: Unpacking the Router

108

Documentation

•

•

Installation Safety Warnings for Juniper Networks Devices on page 269

•

Chapter 15: Unpacking the M10i

Verifying the M10i 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 52 on page 109 , and an accessory box, which contains the parts listed in

Table 53 on page 109 . The parts shipped with your router can vary.

Table 52: Parts List for a Fully Configured Router

Component Quantity

Fan tray

CFEB or CFEB-E

HCM

Mounting brackets

Up to 2

PIC

Power supply

Routing Engine

Blank panels for slots without components

Up to 8

Up to 4

Up to 2

One blank panel for each slot not occupied by a component

Table 53: Accessory Box Parts List

Part Quantity

Screws, Screw, Pan hd, Phil, 12-24 x 1/2", self-tapping

Screws, Flat Hd, Phil, 5 x 10.5mm Long, 1.6mm Pitch, self-tapping

Terminal lugs, 16-AWG to 14-AWG, #6 stud, ring terminal, vinyl insulated

2 (not used for the M10i router)

Terminal fork lugs, 14-AWG, #6, 0.25 Wide, insulation strain relieved, for DC power cables

9 are shipped, but only up to 8 are used for the M10i router (2 per each power supply)

Terminal lugs, 14-AWG, #8 stud, ring tongue, insulated 2 (not used for the M10i router)

109

M10i Multiservice Edge Router Hardware Guide

Table 53: Accessory Box Parts List (continued)

Part

Terminal lugs, 14-AWG, two hole for grounding

DB-9 (male) to DB-25 (female) serial adapter

Serial cable, Console, DB9F/DB9F

Label, contents, 3-1/3" x 4", M7i/M10i

Label, Accessory Kit Label, Green "Small Parts Enclosed" 1

Read me first document

JNPR Compliance Form Letter, RoHS Worldwide

Affidavit for T1 connection

Juniper Networks Product Warranty

End User License Agreement 1

Addendum, Documentation Card for Routing Platforms 1

Document sleeve

3" x 5" pink bag

9" x 12" pink bag, ESD

Accessory box, 19 x 12 x 3"

Ethernet cable, RJ-45/RJ-45, 4-pair stranded UTP,

Category 5E, 15'

ESD wrist strap with cable

Quantity

Documentation

•

•

•

Tools and Parts Required to Install the M10i Router Into a Rack on page 111

CHAPTER 16

Installing the M10i into a Rack

•

•

Moving the Mounting Brackets on page 111

•

Tools and Parts Required to Install the M10i Router Into a Rack

To install the chassis into a rack using a mechanical lift, you need the following tools and parts:

• Mechanical lift (recommended)

• Phillips (+) screwdrivers, numbers 1 and 2

Documentation

•

•

•

Figure 5 on page 11 . If you are center-mounting the router, you must move

Moving the Mounting Brackets

The router is shipped with the mounting brackets installed in the front-mounting position, as shown in

the brackets. To move the mounting brackets (see

Figure 26 on page 112 ):

Attach an ESD grounding strap to your bare wrist and connect the strap to one of the

ESD points on the chassis.

To install the mounting brackets in the center-mounting position, you must remove the fan trays: a.

Loosen the thumbscrew at the top of the fan tray faceplate, using a Phillips screwdriver if necessary.

Grasp the handle on the faceplate and slide the tray about halfway out of the chassis.

111

M10i Multiservice Edge Router Hardware Guide c.

Place one hand under the fan tray to support it and slide the tray completely out of the chassis.

Use a number 2 Phillips screwdriver to remove the screws securing the mounting brackets in the front-mounting position.

Remove the mounting brackets by tilting the top of the mounting bracket away from the chassis and sliding it out of the slot at the bottom of the chassis.

Insert the tab at the base of the mounting brackets at an angle into the slot at the bottom of the chassis in the center-mounting position (see

Figure 26 on page 112 ).

Replace the screws that secure the mounting brackets to the chassis.

Reinstall the fan trays: a.

Grasp the handle on the faceplate of the fan tray with one hand and place the other hand under the unit to support it. Orient the fan tray so that the thumbscrew is at the top of the tray.

Slide the tray into the slot.

Tighten the thumbscrew to seat the fan tray firmly in the chassis.

Figure 26: Moving the Mounting Brackets on the Chassis

112

Documentation

•

Preventing Electrostatic Discharge Damage to an M10i Router on page 264

•

Tools and Parts Required to Install the M10i Router Into a Rack on page 111

•

Installation Safety Warnings for Juniper Networks Devices on page 269

•

Chapter 16: Installing the M10i into a Rack

Installing the M10i Router into a Rack

NOTE: Using a mechanical lift to maneuver the router into the rack is recommended because of the router's size and weight. The lift must be able to accommodate the router's weight—between 57 lb (25.9 kg) and about

79 lb (35.8 kg) depending on configuration—and must fit between the support posts of the rack. If you do not use a mechanical lift, installing the chassis safely requires two people to lift and an additional person to insert the mounting screws.

If you are installing multiple routers in one rack, install the lowest one first and proceed upward in the rack.

First, perform the following prerequisite procedures:

• Verify that the router site meets the requirements described in

“M10i Router Site

Preparation Checklist” on page 75 .

• Place the rack in its permanent location, allowing adequate clearance for airflow and maintenance, and secure it to the building structure. For details, see

“Installation Safety

Warnings for Juniper Networks Devices” on page 269 .

• Read the following installation safety guidelines and warnings:

•

Installation Safety Warnings for Juniper Networks Devices on page 269

•

• Remove the router from the shipping carton, as described in

“Unpacking the M10i

Router” on page 107 .

Then perform the following procedures to install the router (see

Figure 27 on page 114

and

Figure 28 on page 115 ):

If you are center-mounting the router, move the mounting brackets on the chassis from the front-mounting position to the center-mounting position. For instructions, see

“Moving the Mounting Brackets” on page 111 .

Position the chassis at the appropriate height in the rack:

• If using a mechanical lift, load the router onto the lift, making sure it rests securely on the lift platform. Use the lift to raise the chassis to the correct height.

• If not using a mechanical lift, have one person stand behind the router and another person in front. Grasp the chassis, lift it, and position it at the correct height. Have a third person ready to install the mounting screws.

Align the bottom hole in both mounting brackets with a hole in each rack rail, making sure the chassis is level.

113

M10i Multiservice Edge Router Hardware Guide

Install a mounting screw into each of the two aligned holes. Use a Phillips screwdriver to tighten the screws.

Moving up the router, install a mounting screw into the remaining holes in each mounting. At least two screws in each mounting bracket are required, at the top and bottom of the mounting bracket.

Verify that the router is level.

If using a mechanical lift, move it away from the rack.

To continue the installation, proceed to

“Initially Configuring the M10i Router” on page 131

Figure 27: Installing the Chassis into a Open-Frame Rack

Chapter 16: Installing the M10i into a Rack

Figure 28: Installing the Chassis into a Four-Post Rack

Documentation

•

•

•

Grounding the M10i Router on page 117

115

M10i Multiservice Edge Router Hardware Guide

CHAPTER 17

Connecting the M10i to Ground

•

Grounding the M10i Router

You must provide the grounding cable. For grounding cable specifications, see

“M10i

Chassis Grounding Cable and Lug Specifications” on page 81

. To connect the grounding cable:

Verify that a licensed electrician has attached the two-hole cable lug provided with the router to the grounding cable.

Connect the grounding cable to a proper earth ground.

Attach an ESD grounding strap to your bare wrist and connect the strap to one of the

ESD points on the chassis.

Using a number 2 Phillips screwdriver, remove the screws next to the grounding symbol above the power supplies on the chassis rear (see

Figure 29 on page 118

). Secure the grounding cable lug to the chosen grounding point by reinstalling and tightening the screws.

Verify that the grounding cable is connected correctly, that it does not touch or block access to router components, and that it does not drape where people could trip on it.

117

M10i Multiservice Edge Router Hardware Guide

Figure 29: Connecting the Grounding Cable

Documentation

•

Preventing Electrostatic Discharge Damage to an M10i Router on page 264

•

Connecting Power on an AC-Powered M10i Router on page 123

•

•

Connecting Power on an DC-Powered M10i Router on page 125

CHAPTER 18

Connecting the M10i to External Devices

•

Connecting the M10i Router to External Devices on page 119

•

Connecting the M10i Router to a Network for Out-of-Band Management on page 119

•

Connecting to an M10I Management Console or Auxiliary Device on page 120

•

Connecting M10i PIC Cables on page 121

Connecting the M10i Router to External Devices

After you have grounded the M10i router, you can connect the following external devices:

• An external console or auxiliary device to the CONSOLE port on the Routing Engine.

See

“Connecting to an M10I Management Console or Auxiliary Device” on page 120

• A laptop, modem, or other auxiliary device to the AUX/MODEM port on the Routing

Engine.

See

“Connecting to an M10I Management Console or Auxiliary Device” on page 120 .

• A management network to the MGMT port on the Routing Engine.

See

“Connecting the M10i Router to a Network for Out-of-Band Management” on page 119 .

Documentation

•

•

•

•

Interface Cable and Wire Specifications for M10i Routers” on page 99 :

Connecting the M10i Router to a Network for Out-of-Band Management

To connect the Routing Engine to a network for out-of-band management, connect an

Ethernet cable with RJ-45/RJ-45 connectors to the MGMT port on the Routing Engine.

One such cable is provided with the router. For cable specifications, see

“Routing Engine

Turn off the power to the management device.

119

M10i Multiservice Edge Router Hardware Guide

Plug one end of the Ethernet cable (

Figure 30 on page 120

shows the connector) into the MGMT port on the Routing Engine (see

Figure 31 on page 120 ).

Plug the other end of the cable into the network device.

Figure 30: Routing Engine Ethernet Cable Connector

Figure 31: Routing Engine Management Ports

Documentation

•

•

•

•

“Routing Engine Interface Cable and Wire Specifications for M10i Routers” on page 99

Connecting to an M10I 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 appropriate AUX/MODEM port on the Routing Engine. Both ports accept an RS-232 (EIA-232) serial cable with DB-9/DB-9 connectors. One cable is provided with the router. If you want to connect a device to both ports, you must supply another cable. See

. To connect a management console or auxiliary device:

Turn off the power to the console or auxiliary device.

Plug the female end (shown in

Figure 32 on page 121

) of the provided console cable into the CONSOLE or AUX/MODEM port (see

Figure 33 on page 121 ).

NOTE:

For console devices, configure the serial port to the following values:

• Baud rate—9600

• Parity—N

• Data bits—8

• Stop bits—1

• Flow control—none

Chapter 18: Connecting the M10i to External Devices

Using a 2.5 mm flat-blade screwdriver, tighten the screws on the connector.

Attach the other end of the cable to the console or auxiliary device.

Figure 32: Console and Auxiliary Serial Port Connector

Figure 33: Routing Engine Management Ports

Documentation

•

•

•

•

Figure 34 on page 122 , which shows a fiber-optic PIC):

Connecting M10i PIC Cables

Now connect PICs to the network by plugging in network cable. To connect cable to the

PICs (see

Have ready a length of the type of cable used by the PIC. For cable specifications, see the M10i Multiservice Edge Router Interface Module Reference .

If the PIC cable connector port is covered by a rubber safety plug, remove the plug.

WARNING: Do not look directly into a fiber-optic transceiver or into the ends of fiber-optic cables. Fiber-optic transceivers and fiber-optic cable connected to a transceiver emit laser light that can damage your eyes.

CAUTION: Do not leave a fiber-optic transceiver uncovered except when you are inserting or removing cable. The safety cap keeps the port clean and prevents accidental exposure to laser light.

121

M10i Multiservice Edge Router Hardware Guide

Insert the cable connector into the cable connector port on the PIC faceplate.

Arrange the cable in the cable management system 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 excess cable out of the way in a neatly coiled loop in the cable management system. Placing fasteners on the loop helps to maintain its shape.

CAUTION: Avoid bending 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.

CAUTION: Do not let fiber-optic cable hang free from the connector. Do not allow fastened loops of cable to dangle, which stresses the cable at the fastening point.

Figure 34: Attaching Cable to a PIC

122

Documentation

•

•

•

Tools and Parts Required to Connect the M10i Router to External Devices on page 123

CHAPTER 19

Providing Power to the M10i

•

•

Connecting Power on an AC-Powered M10i Router on page 123

•

Powering On an AC-Powered M10i Router on page 124

•

Connecting Power on an DC-Powered M10i Router on page 125

•

Powering On a DC-Powered M10i Router on page 128

•

Powering Off the M10i Router on page 129

Tools and Parts Required to Connect the M10i Router to External Devices

To connect the router to management devices and PICs, you need the following tools and parts:

• Phillips (+) screwdrivers, numbers 1 and 2

• Flat-blade (-) screwdrivers, 2.5 mm for the connecting to the CONSOLE port or

AUX/MODEM port on a Routing Engine and 3 mm

• Electrostatic damage (ESD) grounding wrist strap

Documentation

•

Preventing Electrostatic Discharge Damage to an M10i Router on page 264

•

Connecting to an M10I Management Console or Auxiliary Device on page 120

•

Connecting the M10i Router to a Network for Out-of-Band Management on page 119

•

Connecting M10i PIC Cables on page 121

Connecting Power on an AC-Powered M10i Router

The AC power cord that plugs into the appliance inlet on the faceplate of each AC power supply provides direct connection to the external power source.

To connect AC power to the router:

Verify that the power supplies are fully inserted in the chassis and the thumbscrews on their faceplates are tightened.

123

M10i Multiservice Edge Router Hardware Guide

For each power supply, plug in the ends of the AC power cord firmly into the appliance inlet on the power supply faceplate and the external power source receptacle.

Documentation

•

M10i Router AC Power Supply Specifications on page 85

•

•

Preventing Electrostatic Discharge Damage to an M10i Router on page 264

•

Disconnecting Power on an AC-Powered M10i Router on page 208

•

General Electrical Safety Guidelines and Electrical Codes for M10i Routers on page 291

Powering On an AC-Powered M10i Router

To power on the router:

Verify that the power supplies are fully inserted in the chassis and the thumbscrews on their faceplates are tightened.

Verify that the ends of each AC power cord are firmly plugged into the appliance inlet on the power supply faceplate and the external power source receptacle.

Verify that an external management device is connected to one of the Routing Engine ports ( AUX/MODEM , CONSOLE , or MGMT ).

NOTE: The Ethernet MGMT port is not available until you complete the initial router software configuration after the router is powered on for the first time. You can monitor the startup process during the initial installation using devices connected to the AUX/MODEM or CONSOLE ports.

Turn on the power to the external management device.

Press the power switch on the faceplate of the power supplies in slots P/S 0 and P/S

1 to the ON ( | ) position.

NOTE: After a power supply is powered on, it can take up to 60 seconds for status indicators—such as LEDs on the power supply and command display output—to indicate that the power supply is functioning normally.

Ignore error indicators that appear during the first 60 seconds.

Chapter 19: Providing Power to the M10i

NOTE: If the LED does not light after 60 seconds, verify that the power supply is properly inserted into the chassis and repeat the cable installation procedures described in

“Connecting Power on an AC-Powered M10i

Router” on page 123

NOTE: The Routing Engine boots as the power supply completes its startup sequence. If the Routing Engine finishes booting and you need to power off the router again, see

“Powering Off the M10i Router” on page 129

Verify that the OUTPUT OK LED on each power supply faceplate eventually lights steadily.

Press the power switch for any additional power supplies to the ON ( | ) position and verify that the OUTPUT OK LED on each power supply faceplate lights steadily.

On the external management device connected to the Routing Engine, monitor the startup process to verify that the system has booted properly.

NOTE: After powering off a power supply, wait at least 60 seconds before turning it back on.

Documentation

•

M10i Router AC Power Supply Specifications on page 85

•

•

Connecting to an M10I Management Console or Auxiliary Device on page 120

•

Connecting the M10i Router to a Network for Out-of-Band Management on page 119

•

Preventing Electrostatic Discharge Damage to an M10i Router on page 264

•

General Electrical Safety Guidelines and Electrical Codes for M10i Routers on page 291

Connecting Power on an DC-Powered M10i Router

On a DC-powered router, the DC power cables from the external DC power sources connect to field-wiring terminals on each power supply.

Connect DC power to the router by inserting power cables into the field-wiring terminals on the faceplate of each power supply. DC power cables are not supplied with the router.

For information about the required cable type, see

“M10i DC Power Cable and Lug

Specifications” on page 90

125

M10i Multiservice Edge Router Hardware Guide

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 DC power cables that attach to the terminal studs on the power supply faceplate. You must ensure that power connections maintain the proper polarity. The power source cables might be labeled (+) and (–) to indicate their polarity.

To connect DC power to the router (see

Figure 35 on page 127 ):

Verify that there is no power flowing from either external power source, so that the voltage across the leads of the DC power cables is 0 V. Ensure that there is no chance that the cable leads might become active during the procedure.

For each power supply, verify that the power switch on the power supply faceplate is in the OFF ( O ) position.

Verify that a licensed electrician has attached a listed DC power cable lug to each power source cable.

Loop the DC power cables through the hook located on the faceplate to the right of the field-wiring terminals.

Depending on the type of DC power cable lugs used, loosen or remove the screws on the field-wiring terminals.

Insert the DC power cable lugs into the appropriate field-wiring terminals. Using a number 1 Phillips screwdriver, turn the screw on each field-wiring terminal clockwise to secure the DC power cable lug. Apply between 8 lb-in. (.9 Nm) and 9 lb-in. (1.02

Nm) of torque to each screw.

Insert the positive (+) source cable into the return terminal, which is labeled RTN .

Insert the negative (–) source cable into the input terminal, which is labeled –48V .

Chapter 19: Providing Power to the M10i

NOTE: The DC power supplies in slots P/S 0 and P/S 1 must be powered by dedicated power feeds derived from feed A, and the DC power supplies in slots P/S 2 and P/S 3 must be powered by dedicated power feeds derived from feed B. This configuration provides the commonly deployed A/B feed redundancy for the system.

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.

Figure 35: Connecting DC Power Cables to a DC Power Supply

Documentation

•

Preventing Electrostatic Discharge Damage to an M10i Router on page 264

•

General Electrical Safety Guidelines and Electrical Codes for M10i Routers on page 291

•

M10i Router DC Power Supply Specifications on page 89

•

127

M10i Multiservice Edge Router Hardware Guide

Powering On a DC-Powered M10i Router

To power on a DC-powered router:

Verify that the power supplies are fully inserted in the chassis and the thumbscrews on their faceplates are tightened.

For each power supply on a DC-powered router, verify that the source DC power cables are connected to the appropriate terminal 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 ).

Verify that an external management device is connected to one of the Routing Engine ports on the Routing Engine ( AUX/MODEM , CONSOLE , or MGMT ).

Turn on the DC power source so that voltage flows to the router.

Turn on the power to the external management device.

Press the power switch for the power supplies in slots P/S 0 and P/S 1 to the ON ( | ) position. The power switch is located on the power supply faceplate.

The Routing Engine boots as the power supply completes its startup sequence. If the

Routing Engine finishes booting and you need to power off the router again, see

“Powering Off the M10i Router” on page 129

. After powering on a power supply, wait at least 60 seconds before turning it off.

Ignore error indicators that appear during the first 60 seconds.

Press the power switch for any additional power supplies to the ON ( | ) position.

Verify that the green OUTPUT OK LED on each power supply faceplate lights steadily.

NOTE: If the LED does not light after 60 seconds, verify that the power supply is properly inserted into the chassis and repeat the cable installation procedures described in

“Connecting Power on an DC-Powered M10i

Router” on page 125

On the external management device connected to the Routing Engine, monitor the startup process to verify that the system has booted properly.

Chapter 19: Providing Power to the M10i

Documentation

•

Connecting to an M10I Management Console or Auxiliary Device on page 120

•

Connecting the M10i Router to a Network for Out-of-Band Management on page 119

•

Preventing Electrostatic Discharge Damage to an M10i Router on page 264

•

General Electrical Safety Guidelines and Electrical Codes for M10i Routers on page 291

•

M10i Router DC Power Supply Specifications on page 89

•

Powering Off the M10i Router

To power off the router:

On an external management device connected to the Routing Engine, issue the request system halt both-routing-engines operational mode command. The command shuts down the Routing Engines cleanly, so their state information is preserved. (If the router contains only one Routing Engine, issue the request system halt command.)

NOTE: The CFEB or CFEB-E might continue forwarding traffic for approximately 5 minutes after the request system halt command has been issued.

user@host> request system halt both-routing-engines

Wait until a message appears on the console confirming that the operating system has halted.

Halt the system ? [yes,no] (no) yes

*** FINAL System shutdown message from user@host ***

System going down IMMEDIATELY

Terminated

...

syncing disks... 11 8 done

The operating system has halted.

Please press any key to reboot.

For more information about the commands, see the CLI Explorer .

Attach an electrostatic discharge (ESD) grounding strap to your bare wrist, and connect the strap to one of the ESD points on the chassis.

129

M10i Multiservice Edge Router Hardware Guide

For each power supply, press the power switch on the power supply faceplate to the

OFF ( O ) position.

NOTE: After powering off a power supply, wait at least 60 seconds before turning it back on.

Documentation

•

•

Preventing Electrostatic Discharge Damage to an M10i Router on page 264

•

•

General Electrical Safety Guidelines and Electrical Codes for M10i Routers on page 291

CHAPTER 20

Configuring the Junos Software

•

Initially Configuring the M10i Router on page 131

Initially Configuring the M10i Router

The router is shipped with the Junos OS preinstalled and ready to be configured when the router is powered on. There are three copies of the software: one on a CompactFlash card (if installed) in the Routing Engine, one on the hard disk in the Routing Engine, and one on a PC card that can be inserted into the slot in the Routing Engine faceplate.

When the router boots, it first attempts to start 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 (if installed), 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

• IP address of a default router

• IP address of a DNS server

• Password for the root user

This procedure connects one 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:

Verify that the router is powered on, as described in

“Powering On an AC-Powered

M10i Router” on page 124

“Powering On a DC-Powered M10i Router” on page 128

131

M10i Multiservice Edge Router Hardware Guide

Amnesiac <ttyd0> login: root

Start the CLI.

root@% cli root>

Enter configuration mode.

root> configure

Entering configuration mode.

[edit] root@#

Add a password to the root administration user account. Enter a clear-text password.

For information about using an encrypted password, or an SSH public key string (DSA or RSA), see the Junos OS Administration Library .

[edit] root@# set system root-authentication plain-text-password

New password: password

Retype new password: password

Create a management console user account.

[edit] root# set system login user user-name authentication plain-text-password

New Password: password

Retype new password: password

Set the user account class to super-user .

[edit] root# set system login user user-name class super-user

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

Chapter 20: Configuring the Junos Software

NOTE: The DNS server does not use the host name to resolve to the correct

IP address. This host name is used to display the name of the routing engine in the CLI. For example, this host name shows on the command line prompt when the user is logged on to the CLI: user-name @ host-name >

Configure the IP address of the DNS server.

[edit] root# set system name-server address

10.

Configure the router’s domain name.

[edit] root@# set system domain-name domain-name

11.

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

12.

Configure the IP address of a backup router. The backup router is used while the local router is booting and if the routing process fails to start. After the routing process starts, the backup router address is removed from the local routing and forwarding tables. For more information on the backup router, see the Junos OS Administration

Library .

[edit] root# set system backup-router address

13.

(Optional) Configure the static routes to remote subnets with access to the management port. Access to the management port is limited to the local subnet. To access the management port from a remote subnet, you need to add a static route to that subnet within the routing table. For more information on static routes, see the

Junos OS Administration Library .

[edit] root# set routing-options static route remote-subnet next-hop destination-IP

retain no-readvertise

14.

Configure the telnet service at the [edit system services] hierarchy level.

[edit] set system services telnet

133

M10i Multiservice Edge Router Hardware Guide

134

15.

Optionally, display the configuration to verify that it is correct.

[edit] root@# show system { host-name host-name; domain-name domain-name; backup-router address; root-authentication {

authentication-method (password | public-key);

} name-server {

address;

}

} interfaces { fxp0 { unit 0 { family inet { address address/prefix-length;

}

16.

Commit the configuration to activate it on the router.

[edit] root@# commit

17.

Optionally, configure additional properties by adding the necessary configuration statements. Then commit the changes to activate them on the router.

[edit] root@host# commit

18.

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 router does not operate normally when it is booted from the removable media.

When the router boots from the storage media (removable media, CompactFlash card, or hard disk) it expands its search in the /config directory of the routing platform for the

Chapter 20: Configuring the Junos Software 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, the Junos

OS displays a message indication this when you log in to the router.

Documentation

• Configuring CFEB Redundancy on the M10i Router

•

Configuring the CompactFlash Card on an M10i Routing Engine on page 156

•

Overview of Installing and Replacing Components on page 139

135

M10i Multiservice Edge Router Hardware Guide

PART 4

Installing and Replacing Components

•

•

Replacing Chassis Components on page 141

•

Replacing Cooling System Components on page 149

•

Replacing Host Subsystem Components on page 153

•

Replacing Line Card Components on page 173

•

Replacing Power System Components on page 191

•

Replacing Switch Fabric Components on page 211

137

M10i Multiservice Edge Router Hardware Guide

CHAPTER 21

Overview of Installing and Replacing

Components

•

M10i Field-Replaceable Units (FRUs) on page 139

•

Tools and Parts Required to Replace M10i Hardware Components on page 140

M10i Field-Replaceable Units (FRUs)

Field-replaceable units (FRUs) are router components that can be replaced at the customer site. Replacing most FRUs requires minimal router downtime. The router uses the following types of FRUs:

• Hot-removable and hot-insertable FRUs—You can remove and replace these components without powering down the router or disrupting the routing functions.

• Hot-pluggable FRUs—You can remove and replace these components without powering down the router, but the routing functions of the system are interrupted when the component is removed.

• FRUs that require powering off the router—You must power off the router before removing these components.

Table 54 on page 139

lists the FRUs for the M10i router.

Table 54: Field-Replaceable Units

Hot-Removable and

Hot-Insertable FRUs Hot-Pluggable FRUs

FRUs that Require

Powering Off the Router

Fan tray

Physical Interface Card

(PIC)

Redundant power supply

(AC or DC)

Small form-factor pluggable (SFP)

Compact Forwarding

Engine Board (CFEB)

(when swapping for an existing CFEB)

Nonredundant power supply (AC or DC)

Enhanced Compact

Forwarding Engine Board

(CFEB-E) (when swapping for an existing CFEB-E)

High-Availability Chassis

Manager (HCM)

AC power cord or DC power cable on a nonredundant power supply (AC or DC)

Routing Engine

139

M10i Multiservice Edge Router Hardware Guide

Documentation

•

General Safety Guidelines for Juniper Networks Devices on page 261

•

General Safety Warnings for Juniper Networks Devices on page 262

•

Guidelines for Packing M10i Components for Shipment on page 256

•

Contacting Customer Support on page 245

•

Tools and Parts Required to Replace M10i Hardware Components

To replace hardware components, you need the tools and parts listed in

Table 55 on page 140 .

Table 55: Tools and Parts Required

Tool or part Components

Electrostatic bag or antistatic mat

Electrostatic discharge (ESD) grounding wrist strap

•

CFEB/CFEB-E

HCM

PIC

Routing Engine

All

Flat-blade (–) screwdriver, 2.5 mm Serial cable to AUX/MODEM or CONSOLE Routing Engine port

CompactFlash card Needlenose pliers

Phillips (+) screwdrivers, numbers 1 and 2

Rubber safety cap

•

Fan tray

CFEB/CFEB-E

DC power cables

PIC

Power supply (AC or DC)

Routing Engine

Fiber-optic PIC or PIC cable

Documentation

•

Displaying M10i Router Components and Serial Numbers on page 247

•

Guidelines for Packing M10i Components for Shipment on page 256

•

Contacting Customer Support on page 245

•

Routine Maintenance Procedures for the M10i Router on page 219

CHAPTER 22

Replacing Chassis Components

•

Installing the M10i Cable Management System on page 141

•

Installing an M10i HCM on page 142

•

Replacing an M10i HCM on page 143

Installing the M10i Cable Management System

The cable management system organizes and supports the PIC cables to prevent damage.

To install the cable management system (see

Figure 36 on page 141

Attach an ESD grounding strap to your bare wrist and connect the strap to one of the

ESD points on the chassis.

Locate the cable management racks and appropriate screws in the accessory box.

Slide the cable management rack into the slots at the front of the chassis.

Use a number 2 Phillips screwdriver to tighten the screws that secure the cable management system to the chassis.

Figure 36: Installing the Cable Management System

Documentation

•

Preventing Electrostatic Discharge Damage to an M10i Router on page 264

•

M10i Cable Management System Description on page 13

141

M10i Multiservice Edge Router Hardware Guide

•