Juniper MX150 Hardware Guide
MX150 Universal Routing Platform
Published
2020-11-11
Hardware Guide
Juniper Networks, Inc.
1133 Innovation Way
Sunnyvale, California 94089
USA
408-745-2000
www.juniper.net
Juniper Networks, the Juniper Networks logo, Juniper, and Junos are registered trademarks of Juniper Networks, Inc. in
the United States and other countries. All other trademarks, service marks, registered marks, or registered service marks
are the property of their respective owners.
Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right
to change, modify, transfer, or otherwise revise this publication without notice.
MX150 Universal Routing Platform Hardware Guide
Copyright © 2020 Juniper Networks, Inc. All rights reserved.
The information in this document is current as of the date on the title page.
ii
YEAR 2000 NOTICE
Juniper Networks hardware and software products are Year 2000 compliant. Junos OS has no known time-related
limitations through the year 2038. However, the NTP application is known to have some difficulty in the year 2036.
END USER LICENSE AGREEMENT
The Juniper Networks product that is the subject of this technical documentation consists of (or is intended for use with)
Juniper Networks software. Use of such software is subject to the terms and conditions of the End User License Agreement
(“EULA”) posted at https://support.juniper.net/support/eula/. By downloading, installing or using such software, you
agree to the terms and conditions of that EULA.
Table of Contents
1
About the Documentation | viii
Documentation and Release Notes | viii
Using the Examples in This Manual | viii
Merging a Full Example | ix
Merging a Snippet | x
Documentation Conventions | x
Documentation Feedback | xiii
Requesting Technical Support | xiii
Self-Help Online Tools and Resources | xiv
Creating a Service Request with JTAC | xiv
iii
Overview
MX150 Router Overview | 16
Benefits of MX150 Router | 16
MX150 Hardware | 17
System Software | 18
MX150 Chassis | 18
Chassis Physical Specifications for an MX150 | 18
Front Panel of an MX150 | 18
Rear Panel of an MX150 | 20
Chassis Status LEDs on MX150 | 20
Network Port and Uplink Port LEDs on MX150 | 22
Management Port LEDs on MX150 | 24
MX150 Cooling System | 25
MX150 Power System | 25
Power Supply in MX150 | 26
AC Power Supply Specifications for an MX150 | 26
AC Power Cord Specifications for an MX150 | 27
Site Planning, Preparation, and Specifications
2
Site Preparation Checklist for MX150 | 30
MX150 Site Guidelines and Requirements | 32
General Site Guidelines | 32
Site Electrical Wiring Guidelines | 32
Environmental Requirements and Specifications for an MX150 | 33
Clearance Requirements for Airflow and Hardware Maintenance for an MX150 | 34
Requirements for Mounting an MX150 on a Desktop or Other Level Surface | 35
Cabinet Requirements for an MX150 | 36
Rack Requirements for an MX150 | 37
MX150 Management and Console Port Specifications and Pinouts | 38
Mini-USB Type-B Console Port Specifications for an MX150 | 38
iv
Console Port Connector Pinouts for MX150 | 39
USB Port Specifications for an MX150 | 40
Network Port Connector Pinout Information for an MX150 | 41
RJ-45 to DB-9 Serial Port Adapter Pinout Information for an MX150 | 42
MX150 Network Cable and Transceiver Planning | 43
Pluggable Transceivers Supported on MX150 | 43
SFP+ Direct Attach Copper Cables for MX150 | 44
Cable Specifications | 45
Standards Supported by These Cables | 45
Cable Specifications for Console and Management Connections for the MX150 | 46
Understanding MX150 Fiber-Optic Cable Signal Loss, Attenuation, and Dispersion | 47
Signal Loss in Multimode and Single-Mode Fiber-Optic Cables | 47
Attenuation and Dispersion in Fiber-Optic Cable | 47
Calculating the Fiber-Optic Cable Power Budget for an MX150 | 48
Calculating the Fiber-Optic Cable Power Margin for an MX150 | 49
Initial Installation and Configuration
3
4
MX150 Installation Overview | 52
Unpacking and Mounting the MX150 | 52
Unpacking an MX150 | 53
Parts Inventory (Packing List) for an MX150 | 53
Register Products—Mandatory for Validating SLAs | 54
Mounting an MX150 | 55
Mounting an MX150 on a Desk or Other Level Surface | 56
Mounting an MX150 on Two Posts in a Rack | 57
Mounting an MX150 on Four Posts in a Rack or Cabinet | 59
Connecting the MX150 to Power | 62
Connecting Earth Ground to an MX150 | 62
v
Parts and Tools Required for Connecting an MX150 to Earth Ground | 62
Connecting Earth Ground to an MX150 | 63
Connecting AC Power to an MX150 | 64
Connecting the MX150 to the Network | 65
Connecting an MX150 to a Management Console | 65
Connecting an MX150 to a Management Console Using Mini-USB Type-B Console Port | 67
Performing the Initial Software Configuration for the MX150 | 68
Maintaining Components
Maintaining MX150 Transceivers and Fiber-Optic Cables | 72
Removing a Transceiver from an MX150 | 72
Installing a Transceiver in an MX150 | 74
Maintaining Fiber-Optic Cables in an MX150 | 76
Connecting a Fiber-Optic Cable to an MX150 | 76
Disconnecting a Fiber-Optic Cable from an MX150 | 78
Removing the MX150 | 79
Powering Off an MX150 | 79
Removing an MX150 from a Rack or Cabinet | 81
Troubleshooting Hardware
5
6
7
Understanding Alarm Types and Severity Levels on MX150 | 84
Contacting Customer Support and Returning the Chassis or Components
Contacting Customer Support and Returning the Chassis or Components | 86
Contacting Customer Support to Obtain a Return Materials Authorization for an MX150 | 86
Locating the Serial Number on an MX150 | 87
Listing the Device and Components Details with the CLI | 87
Locating the Chassis Serial Number ID Label on an MX150 | 88
Packing a MX150 Router or Component for Shipping | 89
Packing an MX150 for Shipping | 89
Packing MX150 Components for Shipping | 90
Returning a MX150 Router or Component for Repair or Replacement | 90
vi
Safety and Compliance Information
General Safety Guidelines and Warnings | 94
Definitions of Safety Warning Levels | 95
Qualified Personnel Warning | 98
Warning Statement for Norway and Sweden | 99
Fire Safety Requirements | 99
Fire Suppression | 99
Fire Suppression Equipment | 99
Installation Instructions Warning | 101
Chassis Lifting Guidelines for MX150 | 101
Restricted Access Warning | 103
Ramp Warning | 105
Rack-Mounting and Cabinet-Mounting Warnings | 106
Laser and LED Safety Guidelines and Warnings for the MX150 | 111
General Laser Safety Guidelines | 112
Class 1M Laser Product Warning | 113
Class 1M Laser Radiation Warning | 113
Class 1 Laser Product Warning | 114
Class 1 LED Product Warning | 115
Laser Beam Warning | 116
Unterminated Fiber-Optic Cable Warning | 117
Radiation from Open Port Apertures Warning | 120
Maintenance and Operational Safety Guidelines and Warnings | 121
Battery Handling Warning | 122
Jewelry Removal Warning | 123
Lightning Activity Warning | 125
Operating Temperature Warning | 126
Product Disposal Warning | 128
General Electrical Safety Guidelines and Warnings | 129
vii
Action to Take After an Electrical Accident | 130
Prevention of Electrostatic Discharge Damage | 130
AC Power Electrical Safety Guidelines | 132
AC Power Disconnection Warning | 133
TN Power Warning | 134
Agency Approvals for MX150 | 134
Compliance Statements for EMC Requirements for MX150 | 136
Canada | 136
European Community | 137
Israel | 137
Japan | 137
Korea | 138
United States | 138
FCC Part 15 Statement | 138
Nonregulatory Environmental Standards | 139
About the Documentation
IN THIS SECTION
Documentation and Release Notes | viii
Using the Examples in This Manual | viii
Documentation Conventions | x
Documentation Feedback | xiii
Requesting Technical Support | xiii
Use this guide to install hardware and perform initial software configuration, routine maintenance, and
troubleshooting for the MX150 Universal Routing Platform.
viii
Documentation and Release Notes
To obtain the most current version of all Juniper Networks®technical documentation, see the product
documentation page on the Juniper Networks website at https://www.juniper.net/documentation/.
If the information in the latest release notes differs from the information in the documentation, follow the
product Release Notes.
Juniper Networks Books publishes books by Juniper Networks engineers and subject matter experts.
These books go beyond the technical documentation to explore the nuances of network architecture,
deployment, and administration. The current list can be viewed at https://www.juniper.net/books.
Using the Examples in This Manual
If you want to use the examples in this manual, you can use the load merge or the load merge relative
command. These commands cause the software to merge the incoming configuration into the current
candidate configuration. The example does not become active until you commit the candidate configuration.
If the example configuration contains the top level of the hierarchy (or multiple hierarchies), the example
is a full example. In this case, use the load merge command.
If the example configuration does not start at the top level of the hierarchy, the example is a snippet. In
this case, use the load merge relative command. These procedures are described in the following sections.
Merging a Full Example
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;
}
}
}
}
ix
2. Merge the contents of the file into your routing platform configuration by issuing the load merge
configuration mode command:
[edit]
user@host# load merge /var/tmp/ex-script.conf
load complete
Merging a Snippet
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. Move to the hierarchy level that is relevant for this snippet by issuing the following configuration mode
command:
[edit]
user@host# edit system scripts
[edit system scripts]
x
3. Merge the contents of the file into your routing platform configuration by issuing the load merge
relative configuration mode command:
[edit system scripts]
user@host# load merge relative /var/tmp/ex-script-snippet.conf
load complete
For more information about the load command, see CLI Explorer.
Documentation Conventions
Table 1 on page xi defines notice icons used in this guide.
Table 1: Notice Icons
xi
DescriptionMeaningIcon
Indicates important features or instructions.Informational note
Caution
Indicates a situation that might result in loss of data or hardware
damage.
Alerts you to the risk of personal injury or death.Warning
Alerts you to the risk of personal injury from a laser.Laser warning
Indicates helpful information.Tip
Alerts you to a recommended use or implementation.Best practice
Table 2 on page xi defines the text and syntax conventions used in this guide.
Table 2: Text and Syntax Conventions
ExamplesDescriptionConvention
Fixed-width text like this
Italic text like this
Represents text that you type.Bold text like this
Represents output that appears on
the terminal screen.
Introduces or emphasizes important
•
new terms.
Identifies guide names.
•
Identifies RFC and Internet draft
•
titles.
To enter configuration mode, type
the configure command:
user@host> configure
user@host> show chassis alarms
No alarms currently active
A policy term is a named structure
•
that defines match conditions and
actions.
Junos OS CLI User Guide
•
RFC 1997, BGP Communities
•
Attribute
Table 2: Text and Syntax Conventions (continued)
xii
ExamplesDescriptionConvention
Italic text like this
Text like this
< > (angle brackets)
| (pipe symbol)
Represents variables (options for
which you substitute a value) in
commands or configuration
statements.
Represents names of configuration
statements, commands, files, and
directories; configuration hierarchy
levels; or labels on routing platform
components.
variables.
Indicates a choice between the
mutually exclusive keywords or
variables on either side of the symbol.
The set of choices is often enclosed
in parentheses for clarity.
Configure the machine’s domain
name:
[edit]
root@# set system domain-name
domain-name
To configure a stub area, include
•
the stub statement at the [edit
protocols ospf area area-id]
hierarchy level.
The console port is labeled
•
CONSOLE.
stub <default-metric metric>;Encloses optional keywords or
broadcast | multicast
(string1 | string2 | string3)
# (pound sign)
[ ] (square brackets)
Indention and braces ( { } )
; (semicolon)
GUI Conventions
Indicates a comment specified on the
same line as the configuration
statement to which it applies.
Encloses a variable for which you can
substitute one or more values.
Identifies a level in the configuration
hierarchy.
Identifies a leaf statement at a
configuration hierarchy level.
rsvp { # Required for dynamic MPLS
only
community name members [
community-ids ]
[edit]
routing-options {
static {
route default {
nexthop address;
retain;
}
}
}
Table 2: Text and Syntax Conventions (continued)
xiii
ExamplesDescriptionConvention
Bold text like this
> (bold right angle bracket)
Represents graphical user interface
(GUI) items you click or select.
Separates levels in a hierarchy of
menu selections.
In the Logical Interfaces box, select
•
All Interfaces.
To cancel the configuration, click
•
Cancel.
In the configuration editor hierarchy,
select Protocols>Ospf.
Documentation Feedback
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—Send your comments to techpubs-comments@juniper.net. Include the document or topic name,
•
URL or page number, and software version (if applicable).
Requesting Technical Support
Technical product support is available through the Juniper Networks Technical Assistance Center (JTAC).
If you are a customer with an active Juniper Care or Partner Support Services support contract, or are
covered under warranty, and need post-sales technical support, you can access our tools and resources
online or open a case with JTAC.
JTAC policies—For a complete understanding of our JTAC procedures and policies, review the JTAC User
•
Guide located at https://www.juniper.net/us/en/local/pdf/resource-guides/7100059-en.pdf.
Product warranties—For product warranty information, visit https://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-Help Online Tools and Resources
For quick and easy problem resolution, Juniper Networks has designed an online self-service portal called
the Customer Support Center (CSC) that provides you with the following features:
Find CSC offerings: https://www.juniper.net/customers/support/
•
Search for known bugs: https://prsearch.juniper.net/
•
xiv
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/
Creating a Service Request with JTAC
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/.
1
CHAPTER
Overview
MX150 Router Overview | 16
MX150 Chassis | 18
MX150 Cooling System | 25
MX150 Power System | 25
MX150 Router Overview
IN THIS SECTION
Benefits of MX150 Router | 16
MX150 Hardware | 17
System Software | 18
The MX150 Universal Routing Platform is a compact, high-performance edge router that is ideally suited
for lower bandwidth service provider applications and distributed service architectures, and for enterprise
WAN use-cases. The MX150 supports advanced technologies like telemetry that simplify your operations
environment, and maximize network uptime.
16
The MX150 is 1 rack unit (U) tall. The MX150 can be mounted on a desk or any other level surface, on
two posts in a Rack, and on four pots in a rack or Cabinet. The MX150 conserves space and contains costs
associated with power and cooling.
Benefits of MX150 Router
System Capacity—MX150 provides 20 Gbps of throughput and supports 1-Gigabit Ethernet and
•
10-Gigabit Ethernet interfaces.
The Programmable Chipset—The chipset implemented in the MX Series routers has a programmable
•
forwarding data structure that allows fast microcode changes in the hardware itself, and a programmable
lookup engine that allows inline service processing. the chip’s programmable QoS engine supports coarse
and fine-grained queuing to address the requirements of core, edge, and aggregation use cases.
Always-on infrastructure base—MX Series routers ensure network and service availability with a broad
•
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-Aware Networking—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.
Junos Continuity and Unified In-Service Software Upgrade (Unified ISSU)—With the Junos continuity
g006769
•
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.
Junos Telemetry Interface—Using the Junos telemetry interface data, you can stream component-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.
Integrated Hardware-Based Timing— You do not need to use external clocks because MX Series routers
•
support highly scalable and reliable hardware-based timing, including Synchronous Ethernet for frequency,
and the Precision Time Protocol (PTP) for frequency and phase synchronization. Synchronous Ethernet
and PTP can be combined in a hybrid mode to achieve a high level of frequency (10 ppb) and phase (<1.5
uS) accuracy.
17
MX150 Hardware
The MX150 provide carrier-grade level of a rich set of Layer 2 and Layer 3 features. The MX150 has eight
1-Gigabit Ethernet network ports, two 1-Gigabit Ethernet RJ-45 ports that can be used as either access
ports or as uplink ports, two SFP ports, two SFP+ ports, and one management port. The MX150 has a 1 U
form factor and is shipped with built-in fans and power supply.
Figure 1: MX150 Port Panel
The MX150 can be used as:
An integrated branch router.
•
A secure router for distributed enterprises.
•
System Software
The MX150 use the Junos OS CLI. You can manage the device by using the Junos CLI, accessible through
the console on the device.
MX150 Chassis
IN THIS SECTION
Chassis Physical Specifications for an MX150 | 18
Front Panel of an MX150 | 18
Rear Panel of an MX150 | 20
18
Chassis Status LEDs on MX150 | 20
Network Port and Uplink Port LEDs on MX150 | 22
Management Port LEDs on MX150 | 24
Chassis Physical Specifications for an MX150
MX150 chassis is a rigid sheet-metal structure that houses the hardware components. Table 3 on page 18
summarizes the physical specifications of the MX150 chassis.
Table 3: Physical Specifications for the MX150 Chassis
WeightDepthWidthHeightProduct SKU
9.4 lb (4.3 kg)12 in. (30.5 cm)17.36 in. (44.1 cm)1.72 in. (4.3 cm)MX150
Front Panel of an MX150
The front panel of an MX150 consists of the following components:
Eight 1-Gigabit Ethernet network ports
g006770
3 4 5 6 7
11 89
1 2
10
•
Two 1-Gigabit Ethernet RJ-45 access ports or uplink ports
•
Two 1-Gigabit SFP ports
•
Two 1/10-Gigabit SFP+ ports
•
Link (LINK) and status (ST) LEDs for SFP and SFP+ ports
•
1 Mini-USB Type-B console port
•
1 RJ-45 console port
•
1 USB port
•
1-Gigabit management port
•
4 system status LEDs
•
3 port parameter LEDs
•
1 Mode button
•
19
Figure 2: MX150 Front Panel Components
Mini-USB console port
6—1-Gigabit management (mgmt) port
7—1— system status LEDs and port parameter LEDs1-Gigabit Ethernet RJ-45 network ports
8—2— Mode buttonLink and Status LEDs for SFP and SFP+ ports
9—3— Port: 0 and 1 support SFP (1G) and SFP+(10G). In
Junos CLI, these ports are shown as xe-0/0/12 and
xe-0/0/13, respectively.
10—4— Port: 10 and 11 support SFP only;Console (CON) port
11—5— 1-Gigabit Ethernet RJ-45 network or uplink portsUSB port
CAUTION: Do not use the Reset button to restart the power sequence unless under
the direction of Juniper Networks Technical Assistance Center (JTAC).
SEE ALSO
Prevention of Electrostatic Discharge Damage | 130
Rear Panel of an MX150
The rear panel of the MX150 consists of the following components (see Figure 3 on page 20):
Ground area
•
Electrostatic discharge (ESD) point
•
Exhaust vents
•
Power switch
•
AC power cord inlet
•
20
Figure 3: MX150 Rear Panel
4—1— Power switchGround area
5—2— AC power cord inletElectrostatic discharge (ESD) point
3—Exhaust vents
Chassis Status LEDs on MX150
The front panel of an MX150 has chassis status LEDs (labeled ALM, SYS, MST and PH), next to the MGMT
port (see Figure 4 on page 21).
Figure 4: Chassis Status LEDs in an MX150
3—1— Mode buttonChassis status LEDs (ALM, SYS, MST, and PH)
2—Port parameter LEDs (SPD, DX, and EN)
Table 4 on page 21 describes the chassis status LEDs on an MX150, their colors and states, and the status
they indicate. You can view the colors of the four LEDs remotely through the CLI by issuing the operational
mode command show chassis craft-interface.
21
Table 4: Chassis Status LEDs in an MX150
State and DescriptionColorLED Label
There is no alarm or the device is halted.UnlitALM (Alarm)
There is a major alarm.Red
There is a minor alarm.Amber
GreenSYS (System)
GreenMST (Primary)
On steadily—Junos OS has been loaded on the device.
•
Blinking—The device is booting.
•
Off—The device is powered off or is halted.
•
On steadily—The device is functioning normally.
•
Off—The device is powered off or is halted.
•
This LED is not used. So, the status of this LED is off.UnlitPH
A major alarm (red) indicates a critical error condition that requires immediate action.
A minor alarm (amber) indicates a noncritical condition that requires monitoring or maintenance. A minor
alarm left unchecked might cause interruption in service or performance degradation.
All three LEDs can be lit simultaneously.
Network Port and Uplink Port LEDs on MX150
g041128
Link/
Activity
Status
Each network port and uplink port on the front panel of an MX150 has two LEDs that indicate link activity
and port status (see Figure 5 on page 22).
Figure 5: LEDs on the Network Port
Table 5 on page 22 describes the link activity of the LED.
Table 5: Link activity LED on the Network Ports and Uplink Ports in MX150
22
State and DescriptionColorLED
GreenLink activity
Blinking—The port and the link are active, and there is link activity.
•
On steadily—The port and the link are active, but there is no link
•
activity.
Off—The port is not active.
•
Figure 6 on page 23 shows the LEDs that indicate the status of one of the three port parameters—speed,
duplex mode, and administrative status. Use the Mode button on the far right side of the front panel to
display the status LED for the different port parameters. You can tell which port parameter (speed, duplex
mode, or administrative status) is indicated by the ST LED by looking at which port parameter LED (SPD,
DX, or EN) is lit.
Figure 6: Port Parameter LEDs of an MX150
3—1— Mode buttonChassis status LEDs (ALM, SYS, MST, and PH)
2—Port parameter LEDs (SPD, DX, and EN)
Table 6 on page 23 describes the port parameters LED.
Table 6: Port Parameter LED on the Network Ports and Uplink Ports in MX150
23
State and DescriptionPort Parameter LED
SPD (speed)
DX (duplex mode)
EN (administrative status)
Indicates the speed. The speed indicators for network ports and uplink ports
are:
One blink per second—10 Mbps
•
Two blinks per second—100 Mbps
•
Three blinks per second—1000 Mbps
•
Indicates the duplex mode. The status indicators are:
On steadily—Port is set to full-duplex mode.
•
Off—Port is set to half-duplex mode.
•
Indicates the administrative status. The status indicators are:
On steadily—Port is administratively enabled.
•
Off—Port is administratively disabled.
•
You can tell which port parameter is indicated by the Status LED on network ports by issuing the operational
mode command show chassis craft-interface.
Management Port LEDs on MX150
The management port on the front panel of an MX150 has two LEDs that indicate link activity and port
status (see Figure 7 on page 24).
Figure 7: LEDs on the Management Port of an MX150
24
2—1— StatusLink activity
Table 7 on page 24 describes the Link activity LED.
Table 7: Link activity LED on the Management Port of an MX150
State and DescriptionColorLED
GreenLink activity
Blinking—The port and the link are active, and there is
•
link activity.
On steadily—The port and the link are active, but there
•
is no link activity.
Off—The port is not active.
•
Table 8 on page 24 describes the status LED.
Table 8: Status LED on the Management Port of an MX150
State and DescriptionColorLED
GreenStatus
Indicates the speed. The speed indicators are:
One blink per second—10 Mbps
•
Two blinks per second—100 Mbps
•
Three blinks per second—1000 Mbps
•
SEE ALSO
MX150 Cooling System
The MX150 has front-to-back airflow. The air intake to cool the chassis is located at the front of the chassis.
Air is pulled into the chassis and pushed toward the fans, which are built-in. Hot air exhausts from the rear
of the chassis. See Figure 8 on page 25.
Figure 8: Front-to-Back Airflow Through the MX150 Chassis
25
RELATED DOCUMENTATION
Prevention of Electrostatic Discharge Damage | 130
MX150 Power System
IN THIS SECTION
Power Supply in MX150 | 26
AC Power Supply Specifications for an MX150 | 26
AC Power Cord Specifications for an MX150 | 27
Power Supply in MX150
The MX150 routers use a fixed, internal AC power supply. The power supply distributes different output
voltages to the device components according to their voltage requirements. The power supply is fixed in
the chassis and is not field-replaceable.
The power supply has a single AC appliance inlet that requires a dedicated AC power feed. The AC power
cord inlet is on the rear panel of the device.
SEE ALSO
Connecting AC Power to an MX150 | 64
AC Power Supply Specifications for an MX150
26
Table 9 on page 26 describes the AC power specifications for an MX150.
Table 9: AC Power Specifications for an MX150
SpecificationItem
AC input voltage
SEE ALSO
General Safety Guidelines and Warnings | 94
General Electrical Safety Guidelines and Warnings | 129
Operating range:
100 through 240 VAC
•
50–60 Hz nominalAC input line frequency
3 A at 240 VACAC input current rating
140 WMaximum power consumption
AC Power Cord Specifications for an MX150
A detachable AC power cord is supplied with the AC power supplies. The coupler is type C13 as described
by International Electrotechnical Commission (IEC) standard 60320. The plug at the male end of the power
cord fits into the power source outlet that is standard for your geographical location.
CAUTION: The AC power cord provided with each power supply is intended for use
with that power supply only and not for any other use.
NOTE: In North America, AC power cords must not exceed 4.5 meters 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 switch are in compliance.
27
Table 10 on page 27 gives the AC power cord specifications for the countries and regions listed in the
table.
Table 10: AC Power Cord Specifications
Juniper Model NumberPlug StandardsElectrical SpecificationsCountry/Region
CBL-EX-PWR-C13-ARIRAM 2073 Type RA/3250 VAC, 10 A, 50 HzArgentina
250 VAC, 10 A, 50 HzAustralia
SAA/3
Switzerland, and United
Kingdom)
CBL-EX-PWR-C13-AUAS/NZZS 3112 Type
CBL-EX-PWR-C13-BRNBR 14136 Type BR/3250 VAC, 10 A, 50 HzBrazil
CBL-EX-PWR-C13-CHGB 1002-1996 Type PRC/3250 VAC, 10 A, 50 HzChina
CBL-EX-PWR-C13-EUCEE (7) VII Type VIIG250 VAC, 10 A, 50 HzEurope (except Italy,
CBL-EX-PWR-C13-INIS 1293 Type IND/3250 VAC, 10 A, 50 HzIndia
Japan
CBL-EX-PWR-C13-ILSI 32/1971 Type IL/3G250 VAC, 10 A, 50 HzIsrael
CBL-EX-PWR-C13-ITCEI 23-16 Type I/3G250 VAC, 10 A, 50 HzItaly
CBL-EX-PWR-C13-JPSS-00259 Type VCTF125 VAC, 12 A, 50 Hz or 60
Hz
Table 10: AC Power Cord Specifications (continued)
28
Juniper Model NumberPlug StandardsElectrical SpecificationsCountry/Region
Korea
Hz
250 VAC, 10 A, 50 HzSouth Africa
ZA/13
Taiwan
50 Hz
CBL-EX-PWR-C13-KRCEE (7) VII Type VIIGK250 VAC, 10 A, 50 Hz or 60
CBL-EX-PWR-C13-USNEMA 5-15 Type N5-15125 VAC, 13 A, 60 HzNorth America
CBL-EX-PWR-C13-SASABS 164/1:1992 Type
CBL-EX-PWR-C13-SZSEV 6534-2 Type 12G250 VAC, 10 A, 50 HzSwitzerland
CBL-EX-PWR-C13-TWNEMA 5-15P Type N5-15P125 VAC, 11 A and 15 A,
CBL-EX-PWR-C13-UKBS 1363/A Type BS89/13250 VAC, 10 A, 50 HzUnited Kingdom
Figure 9 on page 28 illustrates the plug on the power cord for some of the countries or regions listed in
Table 10 on page 27.
Figure 9: AC Plug Types
SEE ALSO
General Safety Guidelines and Warnings | 94
General Electrical Safety Guidelines and Warnings | 129
Prevention of Electrostatic Discharge Damage | 130
2
CHAPTER
Site Planning, Preparation, and
Specifications
Site Preparation Checklist for MX150 | 30
MX150 Site Guidelines and Requirements | 32
MX150 Management and Console Port Specifications and Pinouts | 38
MX150 Network Cable and Transceiver Planning | 43
Site Preparation Checklist for MX150
The checklist in Table 11 on page 30 summarizes the tasks you need to perform when preparing a site for
MX150 router installation.
Table 11: Site Preparation Checklist
DatePerformed byFor More InformationItem or Task
Environment
30
Verify that environmental factors such as
temperature and humidity do not exceed
device tolerances.
Power
Measure distance between external power
sources and device installation site.
Locate sites for connection of system
grounding.
Calculate the power consumption and
requirements.
Hardware Configuration
Choose the number of devices you want to
install.
Rack or Cabinet
“Environmental Requirements and
Specifications for an MX150” on
page 33
“AC Power Supply Specifications
for an MX150” on page 26
“MX150 Router Overview” on
page 16
Verify that your rack or cabinet meets the
minimum requirements for the installation
of the device.
Plan rack or cabinet location, including
required space clearances.
“Rack Requirements for an
MX150” on page 37
“Cabinet Requirements for an
MX150” on page 36
“Clearance Requirements for
Airflow and Hardware
Maintenance for an MX150” on
page 34
Loading...