Juniper MX104 Hardware Guide

0 (0)

MX104 Universal Routing Platform

Hardware Guide

Published

2020-11-11

Juniper Networks, Inc. 1133 Innovation Way Sunnyvale, California 94089 USA

408-745-2000 www.juniper.net

JuniperNetworks,theJuniperNetworkslogo,Juniper,andJunosareregisteredtrademarksofJuniperNetworks,Inc. in theUnitedStatesandothercountries. Allothertrademarks,servicemarks,registeredmarks,orregisteredservicemarks are the property of their respective owners.

Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify, transfer, or otherwise revise this publication without notice.

MX104UniversalRoutingPlatformHardwareGuide

The information in this document is current as of the date on the title page.

YEAR2000NOTICE

Juniper Networks hardware and software products are Year 2000 compliant. Junos OS has no known time-related limitations through the year 2038. However, the NTP application is known to have some difficulty in the year 2036.

ENDUSERLICENSEAGREEMENT

TheJuniperNetworksproductthatisthesubjectofthistechnicaldocumentationconsistsof(orisintendedforusewith) JuniperNetworkssoftware.UseofsuchsoftwareissubjecttothetermsandconditionsoftheEndUserLicenseAgreement (“EULA”) posted at https://support.juniper.net/support/eula/. By downloading, installing or using such software, you agree to the terms and conditions of that EULA.

iii

AbouttheDocumentation | xii

Documentation and Release Notes | xii

Using the Examples in This Manual | xii

Merging a Full Example | xiii

Merging a Snippet | xiv

Documentation Conventions | xiv

Documentation Feedback | xvii

Requesting Technical Support | xvii

Self-Help Online Tools and Resources | xviii

Creating a Service Request with JTAC | xviii

1Overview

MX104UniversalRoutingPlatformOverview | 20

Benefits of MX104 Router | 20

System Overview | 21

MX104Chassis | 22

MX104 Chassis Overview | 22

MX104 Hardware and CLI Terminology Mapping | 24

MX104 Component Redundancy | 26

MX104 Alarm Contact Port Overview | 26

MX104 LEDs Overview | 28

Alarm LEDs on the Front Panel | 28

System LED on the Front Panel | 29

MIC LEDs | 30

Power Supply LED | 30

Routing Engine LEDs | 30

MX104CoolingSystemandAirflowOverview | 31

MX104PowerSystem | 32

MX104 Power Overview | 33

AC Power Supplies | 33

DC Power Supplies | 34

Power Supply LEDs | 35

MX104 Power Consumption | 35

MX104 AC Power Specifications | 36

MX104 AC Power Cord Specifications | 37

MX104 DC Power Specifications | 39

MX104 DC Power Cable and Lug Specifications | 40

DC Power Cable Lug Specifications | 41

DC Power Cable Specifications | 41

MX104HostSubsystem | 42

MX104 Routing Engine Overview | 42

MX104 Routing Engine Components | 43

MX104 Routing Engine Buttons | 44

MX104 Routing Engine LEDs | 44

MX104 Boot Sequence | 45

MX104 Routing Engine and its Specifications | 45

MX104InterfaceModules | 46

MX104 Modular Interface Card (MIC) Overview | 46

Front-Pluggable MICs | 47

Built-in 10-Gigabit Ethernet MIC | 47

MIC LEDs | 48

MX104 Port and Interface Numbering | 49

Identifying Interface Numbers on the Hardware | 49

Identifying Interface Numbers in the CLI | 51

2SitePlanning,Preparation,andSpecifications

PreparingtheSitefortheMX104RouterOverview | 57

MX104SiteGuidelinesandRequirements | 58

MX104 Router Physical Specifications | 58

MX104 Router Environmental Specifications | 59

MX104 Chassis Grounding Cable and Lug Specifications | 60

Grounding Points Specifications | 61

Grounding Cable Lug Specifications | 62

Grounding Cable Specifications | 63

Rack Requirements for MX104 Routers | 64

Cabinet Requirements for MX104 Routers | 65

Clearance Requirements for Airflow and Hardware Maintenance on MX104 Routers | 67

MX104NetworkCableandTransceiverPlanning | 68

Calculating Power Budget and Power Margin for Fiber-Optic Cables | 68

How to Calculate Power Budget for Fiber-Optic Cable | 68

How to Calculate Power Margin for Fiber-Optic Cable | 69

Fiber-Optic Cable Signal Loss, Attenuation, and Dispersion | 70

Signal Loss in Multimode and Single-Mode Fiber-Optic Cable | 70

Attenuation and Dispersion in Fiber-Optic Cable | 71

MX104ManagementandConsolePortSpecificationsandPinouts | 72

MX104 Clocking and Timing Ports Overview | 72

MX104 Routing Engine Ethernet Port Specifications | 73

Cable Specifications | 73

Pinouts | 74

MX104 Routing Engine Auxiliary and Console Ports Specifications | 74

Cable Specifications | 75

Pinouts | 75

MX104 Routing Engine USB Port Specifications | 76

MX104 Alarm Contact Port Specifications | 77

Cable Specifications | 77

Port Pinouts | 77

MX104 BITS Port Specifications | 79

Cable Specifications | 79

Port Pinouts | 80

MX104 1-PPS and 10-MHz GPS Port Specifications | 81

MX104 Time of Day Port Specifications | 81

Cable Specifications | 82

Port Pinouts | 82

3InitialInstallationandConfiguration

MX104InstallationOverview | 85

UnpackingtheMX104 | 86

Unpacking an MX104 Router | 86

Parts Inventory (Packing List) for an MX104 Router | 87

InstallingtheMX104 | 89

ConnectingtheMX104toPower | 91

Connecting the MX104 Router to Earth Ground | 92

Connecting AC Power Cords to the MX104 Router | 94

Connecting DC Power Cables to the MX104 Router | 95

ConnectingtheMX104totheNetwork | 99

Connecting the MX104 Router to Management Devices | 99

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

Connecting the Router to a Management Console Device | 100

Connecting the MX104 Router to External Clocking and Timing Devices | 101

Connecting 1-PPS and 10-MHz Timing Devices to the MX104 Router | 102

Connecting a T1 or E1 External Clocking Device to the MX104 Router | 102

Connecting a Time-of-Day Device to the MX104 Router | 102

Connecting Interface Cables to MX104 Routers | 103

InitiallyConfiguringtheMX104Router | 105

vii

4MaintainingComponents

MaintainingMX104Components | 111

MX104 Field-Replaceable Units (FRUs) | 111

Routine Maintenance Procedures for the MX104 Router | 112

Replacing an MX104 Console or Auxiliary Cable | 112

Removing an MX104 Console or Auxiliary Cable | 112

Installing an MX104 Console or Auxiliary Cable | 113

Replacing an MX104 Management Ethernet Cable | 113

Removing an MX104 Management Ethernet Cable | 114

Installing an MX104 Management Ethernet Cable | 114

Replacing an MX104 Fiber-Optic Cable | 114

Disconnecting an MX104 Fiber-Optic Cable | 115

Connecting an MX104 Fiber-Optic Cable | 115

Replacing an MX104 Alarm Cable | 117

Disconnecting the Router from an External Alarm-Reporting Device | 117

Connecting the MX104 Router to an External Alarm-Reporting Device | 117

MaintainingMX104CoolingSystemComponents | 119

Maintaining the MX104 Cooling System | 119

Replacing an MX104 Fan Tray | 120

Removing an MX104 Fan Tray | 121

Installing an MX104 Fan Tray | 122

Maintaining the MX104 Air Filter | 122

Replacing an MX104 Air Filter | 123

Removing an MX104 Air Filter | 123

Installing an MX104 Air Filter | 124

MaintainingMX104HostSubsystemComponents | 125

Maintaining the MX104 Routing Engines | 126

Replacing an MX104 Routing Engine | 128

Effect of Taking the MX104 Routing Engine Offline | 128

Taking an MX104 Routing Engine Offline | 130

Removing an MX104 Routing Engine | 131

Installing an MX104 Routing Engine | 133

viii

MaintainingMX104InterfaceModules | 135

Maintaining the MX104 MICs and Network Ports | 135

Replacing an MX104 MIC | 136

Removing an MX104 MIC | 136

Installing an MX104 MIC | 138

Replacing an MX104 Transceiver | 140

Removing an MX104 Transceiver | 140

Installing an MX104 Transceiver | 142

Maintaining Cables That Connect to MX104 Network Ports | 143

MaintainingMX104PowerSystemComponents | 144

Replacing an MX104 AC Power Supply | 144

Removing an MX104 AC Power Supply | 145

Installing an MX104 AC Power Supply | 147

Replacing an MX104 DC Power Supply | 148

Removing an MX104 DC Power Supply | 148

Installing an MX104 DC Power Supply | 151

5TroubleshootingHardware

TroubleshootingtheMX104 | 156

Troubleshooting Resources for MX104 Routers | 156

Command-Line Interface | 156

Front Panel LEDs | 156

Alarm Devices and Messages | 157

Understanding Alarm Types and Severity Classes on MX104 Routers | 157

Alarm Severity Classes | 158

Verifying Active Alarms on MX104 Routers | 158

Monitoring System Log Messages on MX104 Routers | 159

6ContactingCustomerSupportandReturningtheChassisorComponents

ContactingCustomerSupportandReturningtheChassisorComponents | 161

Contacting Customer Support | 161

How to Return a Hardware Component to Juniper Networks, Inc. | 162

Locating the MX104 Components and Serial Numbers | 163

MX104 Chassis Serial Number Label | 164

MX104 Fan Tray Serial Number Label | 164

MX104 MIC Serial Number Label | 165

MX104 Power Supply Serial Number Label | 166

MX104 Routing Engine Serial Number Label | 166

Guidelines for Packing Hardware Components for Shipment | 167

Packing the MX104 Router for Shipment | 167

7SafetyandComplianceInformation

DefinitionofSafetyWarningLevels | 171

GeneralSafetyGuidelinesforJuniperNetworksDevices | 174

GeneralSafetyWarningsforJuniperNetworksDevices | 175

Qualified Personnel Warning | 176

Restricted-Access Area Warning | 177

PreventingElectrostaticDischargeDamagetoanMX104Router | 179

InstallationSafetyWarningsforJuniperNetworksDevices | 181

Intrabuilding Ports Warning | 181

Installation Instructions Warning | 182

Rack-Mounting Requirements and Warnings | 182

Ramp Warning | 187

GeneralLaserSafetyGuidelinesforJuniperNetworksDevices | 188

LaserSafetyWarningsforJuniperNetworksDevices | 189

Class 1 Laser Product Warning | 189

Class 1 LED Product Warning | 190

Laser Beam Warning | 191

Radiation from Open Port Apertures Warning | 192

MaintenanceandOperationalSafetyWarningsforMX104Routers | 193

Battery Handling Warning | 194

Jewelry Removal Warning | 195

Lightning Activity Warning | 197

Operating Temperature Warning | 198

Product Disposal Warning | 200

InCaseofanElectricalAccident | 201

GeneralElectricalSafetyWarningsforJuniperNetworksDevices | 201

Grounded Equipment Warning | 202

Grounding Requirements and Warning | 202

Midplane Energy Hazard Warning | 203

Multiple Power Supplies Disconnection Warning | 204

Power Disconnection Warning | 205

GeneralElectricalSafetyGuidelinesandElectricalCodesforJuniperNetworks

Devices | 206

MX104ACPowerElectricalSafetyGuidelinesandWarnings | 207

MX104DCPowerElectricalSafetyGuidelines | 208

DCPowerElectricalSafetyWarningsforJuniperNetworksDevices | 209

DC Power Copper Conductors Warning | 210

DC Power Disconnection Warning | 211

DC Power Wiring Terminations Warning | 214

SiteElectricalWiringGuidelinesforMX104Routers | 216

Distance Limitations for Signaling | 216

Radio Frequency Interference | 216

Electromagnetic Compatibility | 217

AgencyApprovalsforMX104Routers | 218

ComplianceStatementsforNEBSforMX104Routers | 219

ComplianceStatementsforEMCRequirementsforMX104Routers | 220

Canada | 220

European Community | 220

Israel | 221

Japan | 221

United States | 221

ComplianceStatementsforEnvironmentalRequirements | 222

ComplianceStatementsforAcousticNoiseforMX104Routers | 222

StatementsofVolatilityforJuniperNetworkDevices | 222

xii

AbouttheDocumentation

INTHISSECTION

Documentation and Release Notes | xii

Using the Examples in This Manual | xii

Documentation Conventions | xiv

Documentation Feedback | xvii

Requesting Technical Support | xvii

Use this guide to install hardware and perform initial software configuration, routine maintenance, and troubleshooting for the MX104 Universal Routing Platform. After completing the installation and basic configurationprocedurescoveredinthisguide,refertotheJunosOSdocumentationforinformationabout further software configuration.

DocumentationandReleaseNotes

To obtain the most current version of all Juniper Networks® technical documentation, see the product documentation page on the Juniper Networks website at https://www.juniper.net/documentation/.

Iftheinformationinthelatestreleasenotesdiffersfromtheinformationinthedocumentation,followthe product Release Notes.

Juniper Networks Books publishes books by Juniper Networks engineers and subject matter experts. These books go beyond the technical documentation to explore the nuances of network architecture, deployment, and administration. The current list can be viewed at https://www.juniper.net/books.

UsingtheExamplesinThisManual

If you want to use the examples in this manual, you can use the loadmerge or the loadmergerelative command. These commands cause the software to merge the incoming configuration into the current candidateconfiguration.Theexampledoesnotbecomeactiveuntilyoucommitthecandidateconfiguration.

xiii

If the example configuration contains the top level of the hierarchy (or multiple hierarchies), the example is a fullexample. In this case, use the loadmerge command.

If the example configuration does not start at the top level of the hierarchy, the example is a snippet. In thiscase,usetheloadmergerelative command.Theseproceduresaredescribedinthefollowingsections.

MergingaFullExample

To merge a full example, follow these steps:

1.From the HTML or PDF version of the manual, copy a configuration example into a text file, save the file with a name, and copy the file to a directory on your routing platform.

For example, copy the following configuration to a file and name the file ex-script.conf. Copy the ex-script.conf file to the /var/tmp directory on your routing platform.

system { scripts {

commit {

file ex-script.xsl;

}

interfaces { fxp0 {

disable; unit 0 {

family inet {

address 10.0.0.1/24;

}

2.Merge the contents of the file into your routing platform configuration by issuing the loadmerge configuration mode command:

[edit]

user@host# loadmerge/var/tmp/ex-script.conf load complete

xiv

MergingaSnippet

To merge a snippet, follow these steps:

1.From the HTML or PDF version of the manual, copy a configuration snippet into a text file, save the file with a name, and copy the file to a directory on your routing platform.

For example, copy the following snippet to a file and name the file ex-script-snippet.conf. Copy the ex-script-snippet.conf file to the /var/tmp directory on your routing platform.

commit {

file ex-script-snippet.xsl; }

2.Movetothehierarchylevelthatisrelevantforthissnippetbyissuingthefollowingconfigurationmode command:

[edit]

user@host# editsystemscripts

[edit system scripts]

3.Merge the contents of the file into your routing platform configuration by issuing the loadmerge relative configuration mode command:

[edit system scripts]

user@host# loadmergerelative/var/tmp/ex-script-snippet.conf load complete

For more information about the load command, see CLI Explorer.

DocumentationConventions

Table 1 on page xv defines notice icons used in this guide.

Table1:NoticeIcons
Icon	Meaning	Description
	Informational note	Indicates important features or instructions.
	Caution	Indicates a situation that might result in loss of data or hardware
		damage.
	Warning	Alerts you to the risk of personal injury or death.
	Laser warning	Alerts you to the risk of personal injury from a laser.
	Tip	Indicates helpful information.
	Best practice	Alerts you to a recommended use or implementation.

Table 2 on page xv defines the text and syntax conventions used in this guide.

Table2:TextandSyntaxConventions

Convention	Description	Examples
Boldtextlikethis	Represents text that you type.	To enter configuration mode, type
		the configure command:
		user@host> configure

Fixed-width text like this

Italictextlikethis

Represents output that appears on the terminal screen.

•Introducesoremphasizesimportant new terms.

•Identifies guide names.

•Identifies RFC and Internet draft titles.

user@host> showchassisalarms

No alarms currently active

•A policy term is a named structure that defines match conditions and actions.

•JunosOSCLIUserGuide

•RFC 1997, BGPCommunities Attribute

xvi

Table2:TextandSyntaxConventions (continued)

Convention	Description
Italictextlikethis	Represents variables (options for
	which you substitute a value) in
	commands or configuration
	statements.

Examples

Configure the machine’s domain name:

[edit]

root@# setsystemdomain-name domain-name

Textlikethis	Represents names of configuration
	statements, commands, files, and
	directories; configuration hierarchy
	levels; or labels on routing platform
	components.

•To configure a stub area, include the stub statement at the [edit protocolsospfareaarea-id] hierarchy level.

•The console port is labeled

CONSOLE.

< > (angle brackets)	Encloses optional keywords or
	variables.
\| (pipe symbol)	Indicates a choice between the
	mutually exclusive keywords or
	variablesoneithersideofthesymbol.
	The set of choices is often enclosed
	in parentheses for clarity.

stub<default-metric metric>;

broadcast|multicast

(string1 | string2 | string3)

# (pound sign)

[ ] (square brackets)

Indention and braces ( { } )

; (semicolon)

Indicatesacommentspecifiedonthe	rsvp{#RequiredfordynamicMPLS
same line as the configuration	only
statement to which it applies.
Enclosesavariableforwhichyoucan	communitynamemembers[
substitute one or more values.	community-ids ]
Identifies a level in the configuration	[edit]
hierarchy.	routing-options {
	static {
Identifies a leaf statement at a	route default {
configuration hierarchy level.	nexthop address;
	retain;
	}
	}
	}

GUIConventions

xvii

Table2:TextandSyntaxConventions (continued)
Convention	Description	Examples
Boldtextlikethis	Represents graphical user interface	• IntheLogicalInterfacesbox,select
	(GUI) items you click or select.	AllInterfaces.
		• To cancel the configuration, click
		Cancel.
> (bold right angle bracket)	Separates levels in a hierarchy of	Intheconfigurationeditorhierarchy,
	menu selections.	select Protocols>Ospf.

DocumentationFeedback

We encourage you to provide feedback so that we can improve our documentation. You can use either of the following methods:

•Online feedback system—Click TechLibrary Feedback, on the lower right of any page on the Juniper Networks TechLibrary site, and do one of the following:

•Click the thumbs-up icon if the information on the page was helpful to you.

•Click the thumbs-down icon if the information on the page was not helpful to you or if you have suggestions for improvement, and use the pop-up form to provide feedback.

•E-mail—Sendyourcommentstotechpubs-comments@juniper.net.Includethedocumentortopicname, URL or page number, and software version (if applicable).

RequestingTechnicalSupport

TechnicalproductsupportisavailablethroughtheJuniperNetworksTechnicalAssistanceCenter(JTAC). If you are a customer with an active Juniper Care or Partner Support Services support contract, or are

xviii

covered under warranty, and need post-sales technical support, you can access our tools and resources online or open a case with JTAC.

•JTACpolicies—ForacompleteunderstandingofourJTACproceduresandpolicies,reviewtheJTACUser Guide located at https://www.juniper.net/us/en/local/pdf/resource-guides/7100059-en.pdf.

•Productwarranties—Forproductwarrantyinformation,visithttps://www.juniper.net/support/warranty/.

•JTAC hours of operation—The JTAC centers have resources available 24 hours a day, 7 days a week, 365 days a year.

Self-HelpOnlineToolsandResources

Forquickandeasyproblemresolution,JuniperNetworkshasdesignedanonlineself-serviceportalcalled the Customer Support Center (CSC) that provides you with the following features:

•Find CSC offerings: https://www.juniper.net/customers/support/

•Search for known bugs: https://prsearch.juniper.net/

•Find product documentation: https://www.juniper.net/documentation/

•Find solutions and answer questions using our Knowledge Base: https://kb.juniper.net/

•Download the latest versions of software and review release notes: https://www.juniper.net/customers/csc/software/

•Search technical bulletins for relevant hardware and software notifications: https://kb.juniper.net/InfoCenter/

•Join and participate in the Juniper Networks Community Forum: https://www.juniper.net/company/communities/

•Create a service request online: https://myjuniper.juniper.net

To verify service entitlement by product serial number, use our Serial Number Entitlement (SNE) Tool: https://entitlementsearch.juniper.net/entitlementsearch/

CreatingaServiceRequestwithJTAC

You can create a service request with JTAC on the Web or by telephone.

•Visit https://myjuniper.juniper.net.

•Call 1-888-314-JTAC (1-888-314-5822 toll-free in the USA, Canada, and Mexico).

For international or direct-dial options in countries without toll-free numbers, see https://support.juniper.net/support/requesting-support/.

CHAPTER

Overview

MX104 Universal Routing Platform Overview | 20

MX104 Chassis | 22

MX104 Cooling System and Airflow Overview | 31

MX104 Power System | 32

MX104 Host Subsystem | 42

MX104 Interface Modules | 46

MX104UniversalRoutingPlatformOverview

TheJuniperNetworksMX104UniversalRoutingPlatformisoptimizedforaggregatingmobile,enterprise WAN, business, and residential access services. The MX104 router is designed for high-density access andpre-aggregationandisenvironmentallyhardenedtoallowoutsidedeploymentsincabinetsandremote terminals. The router is a high-performance router functioning as a universal aggregation platform for mobilebroadbandandmetroEthernetapplications. Italsoactsasauniversaledgeplatformsupportingall typesofprivateWAN,datacenterinterconnect,Internetedge,businessedge,andresidentialedgeservices.

The router is powered by the Junos Trio chipset and runs the Junos® operating system (Junos OS) for high-performance routing and switching. For a list of related Junos OS documentation, see https://www.juniper.net/documentation/software/junos/.

BenefitsofMX104Router

•SystemCapacity—MX104 provides 80 Gbps of throughput. MX104 has four Modular Interface Card (MIC)slotsandsupportsredundantfixed10-GigabitEthernetinterfacesforflexiblenetworkconnectivity.

•TheProgrammableChipset—The chipset implemented in the MX Series routers has a programmable forwardingdatastructurethatallowsfastmicrocodechangesinthehardwareitself,andaprogrammable lookupenginethatallowsinlineserviceprocessing.thechip’sprogrammableQoSenginesupportscoarse and fine-grained queuing to address the requirements of core, edge, and aggregation use cases.

•Always-oninfrastructurebase—MXSeriesroutersensurenetworkandserviceavailabilitywithabroad set of multilayered physical, logical, and protocol-level resiliency aspects. Junos OS Virtual Chassis technology on MX Series routers supports chassis-level redundancy and enables you to manage two routers as a single element. Multichassis link aggregation group (MC-LAG) implementation supports stateful chassis, card, and port redundancy.

•Application-AwareNetworking—On MX Series routers you can use deep packet inspection to detect applications, and by using the user-defined policies, you can determine traffic treatment for each application. This feature enables highly customized and differentiated services at scale.

•JunosContinuityandUnifiedIn-ServiceSoftwareUpgrade(UnifiedISSU)—With the Junos continuity plug-in package, you can perform a smooth upgrade when new hardware is installed in your MX Series router.

Unified in-service software upgrade (unified ISSU) enables software upgrades and changes without disrupting network traffic.

•JunosTelemetryInterface—UsingtheJunostelemetryinterfacedata,youcanstreamcomponent-level data to monitor, analyze, and enhance the performance of the network. Analytics derived from this

streaming telemetry can identify current and trending congestion, resource utilization, traffic volume, and buffer occupancy.

•IntegratedHardware-BasedTiming—YoudonotneedtouseexternalclocksbecauseMXSeriesrouters supporthighlyscalableandreliablehardware-basedtiming,includingSynchronousEthernetforfrequency, andthePrecisionTimeProtocol(PTP)forfrequencyandphasesynchronization. SynchronousEthernet andPTPcanbecombinedinahybridmodetoachieveahighleveloffrequency(10ppb)andphase(<1.5 uS) accuracy.

SystemOverview

The chassis is a rigid sheet metal structure that houses all the other router components (see

Figure 1 on page 21 and Figure 2 on page 22). The hardware system provides resiliency and redundancy, includingpowersuppliesandRoutingEngines.Thechassisalsohasfourbuilt-in10-GigabitEthernetSFP+ ports and four slots that accept Modular Interface Cards (MICs). For a list of the supported MICs, see the

MXSeriesInterfaceModuleReference.

Therouterisenvironmentallyhardenedandis3.5rackunits(U;thatis,6.125in.,or15.55cm)tall.Several routers can be stacked in a single floor-to-ceiling rack, for increased port density per unit of floor space. The chassis is installed in standard 11.81 in. (30 cm)-deep (or larger) enclosed cabinets, 19-in. equipment racks, or telco open-frame racks.

Figure1:FrontPaneloftheMX104Router

<![if ! IE]>

<![endif]>g007600

Figure2:RearViewoftheMX104Router

MX104 Chassis Overview | 22

MX104 Hardware and CLI Terminology Mapping | 24

MX104 Component Redundancy | 26

MX104 Alarm Contact Port Overview | 26

MX104 LEDs Overview | 28

MX104ChassisOverview

TheMX104routercontainsafrontpanelwithslotsinwhichyoucaninstallfield-replaceableunits(FRUs). From the front of the chassis, you can see the following components (see Figure 3 on page 24):

•Alarm console port labeled ALARM, which accepts a DE-15 alarm cable.

•Alarm LEDs that indicate major or minor alarms.

•Built-in 10-Gigabit Ethernet MIC with four ports that accept 10-Gigabit Ethernet SFP+ transceivers.

•ONLINE/OFFLINE button.

•Chassis status LED labeled SYSOK

•External building integrated timing system (BITS) port labeled EXTREFCLOCK

•Time-of-day (TOD) port

•External clocking ports supporting 1-PPS and 10-MHz input and output

•ESD point

•Fan tray, which contains five fans and an air filter

•Four slots for installing MICs

NOTE: For a detailed description of the MX104 port and interface numbering see “MX104 Port and Interface Numbering” on page 49.

•Two slots for installing either AC or DC power supplies, labeled PS0 and PS1

•Two slots for installing Routing Engines, labeled RE0 and RE1

Figure3:FrontViewoftheMX104Router

<![if ! IE]>

<![endif]>g007602

1—Alarm input and output contacts	10—Grounding terminals
2—Alarm LEDs	11—Fan tray
3—10-Gigabit Ethernet SFP+ ports	12—MIC slots 0/1 and 1/1
4—Online/offline button	13—Routing Engine slot 1
5—System status LED	14—Routing Engine slot 0
6—External reference clocking port	15—Power supply slot 1
7—Time-of-day (ToD) port	16—Power supply slot 0
8—1-PPS and 10-MHz GPS input and output ports	17—MIC slots 0/0 and 1/0
9—ESD point

MX104HardwareandCLITerminologyMapping

The MX104 router supports the components in Table 3 on page 24, listed in alphabetic order.

Table3:MX104RoutersHardwareComponentsandCLITerminology

Hardware
Model
Component Number	CLI Name Description

Chassis

N/A

MX104

“MX104 Universal Routing Platform Overview” on page 20

Table3:MX104RoutersHardwareComponentsandCLITerminology (continued)

	Hardware
	Model
Component	Number	CLI Name	Description
Cooling system, including fan trays and air			“MX104 Cooling System and Airflow Overview” on page 31
filters
Air filter kit	FLTR-KIT-MX104	N/A
Fan tray	FANTRAY-MX104	FanTray
Power system components			“MX104 Power Overview” on page 33
Powerblank	PWR-BLANK-MX104	N/A
cover
Power	• AC:	PEM
supply	PWR-MX104-AC
	• DC:
	PWR-MX104-DC
MIC	N/A	4x	“MX104 Modular Interface Card (MIC) Overview” on page 46
	(built-in)	10GE(LAN)
		SFP+
	See MXSeriesInterface		“MX104 Modular Interface Card (MIC) Overview” on page 46
	ModuleReference.
MPC	N/A	FPC	“MX104 Modular Interface Card (MIC) Overview” on page 46
	(built-in)
Routing	RE-S-MX104	Routing	“MX104 Routing Engine Overview” on page 42
Engine		Engine
Transceiver	See MX	Xcvr	“MX104 Modular Interface Card (MIC) Overview” on page 46
	Series
	Interface
	Module
	Reference.

Alarm LEDs on the Front Panel | 28

System LED on the Front Panel | 29

MIC LEDs | 30

Power Supply LED | 30

Routing Engine LEDs | 30

AlarmLEDsontheFrontPanel

Two LEDs, located to the right of the alarm contact port indicates major and minor alarms for the router (see Figure 6 on page 29).

Figure6:AlarmLEDsontheMX104Router

<![if ! IE]>

<![endif]>g007638

Table 5 on page 29 describes the alarm LED in more detail.

Table5:AlarmLEDsontheFrontPanel

			LED Control
Shape	Color	State	Name	Description
	Red	On	Critical alarm	Indicates a critical
		steadily		condition that can cause
				the router to stop
				functioning. Possible
				causesincludecomponent
				removal, failure, or
				overheating.
	Yellow	On	Warning alarm	Indicates a serious but
		steadily		nonfatal error condition,
				such as a maintenance
				alert or a significant
				increase in component
				temperature.

SystemLEDontheFrontPanel

One bicolor LED labeled SYSOK indicates the status of the router. Table 6 on page 30 describes the system LED in more detail.

Table6:SystemLEDontheFrontPanel

Label	Color	State	Description
SYSOK	Green	Blinking	Router has no primary Routing Engine.
		On	Router is functioning normally.
		steadily
	Yellow	On	Router has reported a minor alarm.
		steadily
	Red	On	Router has failed.
		steadily

MICLEDs

Each hot-removable and hot-insertable MIC has LEDs located on the faceplate. For more information about LEDs on the MIC faceplate, see the “LEDs” section for each MIC in the MXSeriesInterfaceModule Reference.

For information about the built-in MIC LEDs, see “MX104 Modular Interface Card (MIC) Overview” on page 46.

PowerSupplyLED

OneLEDlabeledPSSTATUSindicatesthestatusofthepowersupply.Formoreinformation,see“MX104 Power Overview” on page 33.

RoutingEngineLEDs

ThreeLEDsindicatethestatusoftheRoutingEngine. Formoreinformation,see “MX104RoutingEngine Overview” on page 42.

ContactName	Contact Name	Function
Contact 1	Normally Open [NO]	CurrentisnotflowingthroughContact1andContact2[REF]when
		operating normally. When the current flows, the closed alarm is
		generated.
	Normally Closed [NC]	Current is flowing through Contact 1 and Contact 2 [REF] when
		operatingnormally.Whenthecurrentstopsflowing,theopenalarm
		is generated.
Contact 2	Reference [REF]	Provides the current path for the external alarm-reporting device
		and functions as a reference or negative potential terminal for
		Contact 1.

Juniper MX104 Hardware Guide

Table of Contents

Documentation and Release Notes | xii

Using the Examples in This Manual | xii

Overview

MX104 Chassis Overview | 22

Alarm LEDs on the Front Panel | 28