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.
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 | x
Documentation and Release Notes | x
Using the Examples in This Manual | x
Merging a Full Example | xi
Merging a Snippet | xii
Documentation Conventions | xii
Documentation Feedback | xv
Requesting Technical Support | xv
Self-Help Online Tools and Resources | xvi
Creating a Service Request with JTAC | xvi
iii
Overview
PTX10001 System Overview | 18
PTX10001 Packet Transport Router Description | 18
Benefits of the PTX10001 Router | 18
System Overview | 19
Port Panel | 19
Management Panel | 20
PTX10001 Hardware Component Overview | 21
PTX10001 Component Redundancy | 21
PTX10001 Field-Replaceable Units | 22
PTX10001 Port Panel | 23
PTX10001 Port Panel | 23
Network Ports | 24
Expansion Module Bay | 25
PTX10001 Chassis Status LEDs | 25
PTX10001 Management Port LEDs | 27
PTX10001 Network Port LEDs | 28
PTX10001 Management Panel | 29
PTX10001 Management Panel | 29
PTX10001 Cooling System | 31
2
PTX10001 Cooling System Description | 31
Fan Modules | 31
Airflow Through the Chassis | 33
PTX10001 Fan Module LEDs | 33
PTX10001 Power System | 34
PTX10001 AC Power Supply Description | 35
PTX10001 AC Power Supply LEDs | 36
PTX10001 DC Power Supply Description | 37
PTX10001 DC Power Supply LEDs | 39
PTX10001 AC Power Specifications | 40
PTX10001 AC Power Cord Specifications | 40
PTX10001 DC Power Specifications | 42
iv
PTX10001 DC Power Cable Specifications | 42
Expansion Module for the PTX10001 | 44
JNP10001-16C-PIC | 44
Site Planning, Preparation, and Specifications
PTX10001 Site Preparation Checklist | 48
PTX10001 Site Guidelines and Requirements | 49
PTX10001 Environmental Requirements and Specifications | 50
General Site Guidelines | 51
PTX10001 Chassis Grounding Cable and Lug Specifications | 51
PTX10001 Clearance Requirements for Airflow and Hardware Maintenance | 52
PTX10001 Physical Specifications | 53
Site Electrical Wiring Guidelines | 53
PTX10001 Rack Requirements | 54
PTX10001 Cabinet Requirements | 56
PTX10001 Network Cable and Transceiver Planning | 57
Determining Transceiver Support for the PTX10001 | 57
Cable and Connector Specifications for MX and PTX Series Devices | 58
12-Fiber MPO Connectors | 58
24-Fiber MPO Connectors | 63
LC Duplex Connectors | 63
3
Fiber-Optic Cable Signal Loss, Attenuation, and Dispersion | 64
Signal Loss in Multimode and Single-Mode Fiber-Optic Cable | 64
Attenuation and Dispersion in Fiber-Optic Cable | 65
Calculating Power Budget and Power Margin for Fiber-Optic Cables | 65
How to Calculate Power Budget for Fiber-Optic Cable | 66
How to Calculate Power Margin for Fiber-Optic Cable | 66
PTX10001 Management Cable Specifications and Pinouts | 68
Cable Specifications for Console and Management Connections for the PTX10001 | 68
Management Port Connector Pinouts for the PTX10001 | 69
Console Port Connector Pinouts for the PTX10001 | 70
USB Port Specifications for the PTX10001 | 70
Initial Installation and Configuration
v
PTX10001 Installation Overview | 73
Overview of Installing the PTX10001 | 73
PTX10001 Installation Safety Guidelines | 74
General Installation Safety Guidelines | 74
PTX10001 Chassis Lifting Guidelines | 74
Unpacking and Mounting the PTX10001 | 75
Unpacking the PTX10001 | 75
Mounting the PTX10001 in a Rack or Cabinet | 77
Before You Begin Rack Installation | 77
Mounting the PTX10001 | 78
Connecting the PTX10001 to Power | 80
Connecting the PTX10001 to Ground | 81
Connecting AC Power to the PTX10001 | 83
Connecting DC Power to the PTX10001 | 86
Connecting the PTX10001 to External Devices | 91
4
Connecting the PTX10001 to a Management Ethernet Device | 91
Connecting the PTX10001 to a Management Console | 92
Performing the Initial Software Configuration for the PTX10001 | 94
Powering Off the PTX10001 | 96
Removing, Installing, and Maintaining Components
Maintaining the PTX10001 Fan Modules | 100
Removing a Fan Module from the PTX10001 | 100
Installing a Fan Module in the PTX10001 | 101
Maintaining the PTX10001 Power Supplies | 103
Removing a Power Supply from the PTX10001 | 103
Installing a Power Supply in a PTX10001 | 105
vi
Maintaining a PTX10001 Expansion Module | 106
Removing a PTX10001 Expansion Module | 107
Installing a PTX10001 Expansion Module | 108
Maintaining the PTX10001 Transceivers and Fiber-Optic Cables | 110
Remove a Transceiver | 111
Install a Transceiver | 114
Removing a QSFP28 Transceiver | 117
Installing a QSFP28 Transceiver | 118
Disconnecting a Fiber-Optic Cable from the PTX10001 | 119
Connecting a Fiber-Optic Cable to the PTX10001 | 120
Maintaining Fiber-Optic Cables in a PTX10001 | 121
Maintaining the SATA Solid State Drive in a PTX10001 | 122
Removing a SATA Solid State Drive in a PTX10001 | 123
Installing a SATA Solid State Drive in a PTX10001 | 124
Uninstalling the PTX10001 | 125
Removing a PTX10001 from a Rack or Cabinet | 126
Troubleshooting Hardware
5
6
7
Troubleshooting the PTX10001 | 129
PTX10001 Troubleshooting Resources Overview | 129
PTX10001 Alarm Messages Overview | 130
Chassis Alarm Messages on the PTX10001 | 130
Contacting Customer Support and Returning the Chassis or Components
Returning the PTX10001 Chassis or Components | 136
Contact Customer Support | 136
Locating the Serial Number on a PTX10001 Chassis or Component | 137
Listing the Chassis and Component Details by Using the CLI | 138
Locating the Chassis Serial Number ID Label on a PTX10001 | 139
Locating the Serial Number ID Labels on FRU Components | 139
vii
How to Return a Hardware Component to Juniper Networks, Inc. | 139
Guidelines for Packing Hardware Components for Shipment | 140
Packing a PTX10001 Chassis or Component for Shipping | 141
Packing a PTX10001 for Shipping | 141
Packing PTX10001 Components for Shipping | 142
Safety and Compliance Information
General Safety Guidelines and Warnings | 146
Definitions of Safety Warning Levels | 147
Qualified Personnel Warning | 150
Warning Statement for Norway and Sweden | 151
Fire Safety Requirements | 151
Fire Suppression | 151
Fire Suppression Equipment | 151
Installation Instructions Warning | 153
Chassis and Component Lifting Guidelines | 153
Restricted Access Warning | 155
Ramp Warning | 157
Rack-Mounting and Cabinet-Mounting Warnings | 158
Grounded Equipment Warning | 164
Laser and LED Safety Guidelines and Warnings | 165
General Laser Safety Guidelines | 165
Class 1 Laser Product Warning | 166
Class 1 LED Product Warning | 167
Laser Beam Warning | 168
Radiation from Open Port Apertures Warning | 169
Maintenance and Operational Safety Guidelines and Warnings | 170
Battery Handling Warning | 171
Jewelry Removal Warning | 172
Lightning Activity Warning | 174
viii
Operating Temperature Warning | 175
Product Disposal Warning | 177
General Electrical Safety Guidelines and Warnings | 178
Action to Take After an Electrical Accident | 179
Prevention of Electrostatic Discharge Damage | 180
AC Power Electrical Safety Guidelines | 181
AC Power Disconnection Warning | 183
DC Power Electrical Safety Guidelines | 184
DC Power Copper Conductors Warning | 185
DC Power Disconnection Warning | 186
DC Power Grounding Requirements and Warning | 188
DC Power Wiring Sequence Warning | 190
DC Power Wiring Terminations Warning | 193
Multiple Power Supplies Disconnection Warning | 196
TN Power Warning | 197
PTX10001 Agency Approvals and Compliance Statements | 197
PTX10001 Agency Approvals | 198
Compliance Statements for EMC Requirements | 199
Canada | 199
European Community | 199
Israel | 199
Japan | 200
United States | 200
Compliance Statements for Environmental Requirements | 200
Compliance Statements for NEBS | 200
PTX10001 Compliance Statements for Acoustic Noise | 201
ix
About the Documentation
IN THIS SECTION
Documentation and Release Notes | x
Using the Examples in This Manual | x
Documentation Conventions | xii
Documentation Feedback | xv
Requesting Technical Support | xv
Use this guide to plan, install, perform initial software configuration, perform routine maintenance, and to
troubleshoot PTX10001 Packet Transport Routers.
x
After completing the installation and basic configuration procedures covered in this guide, refer to the
Junos OS documentation for further software configuration.
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;
}
}
}
}
xi
2. Merge the contents of the file into your routing platform configuration by issuing the load merge
configuration mode command:
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]
xii
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 xiii defines notice icons used in this guide.
Table 1: Notice Icons
xiii
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 xiii 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)
xiv
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)
xv
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.
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:
Juniper Networks PTX10001 Packet Transport Router is a fixed-configuration MacSec enabled LSR core
router. It features a compact 1U form factor that is easily deployed in space-constrained Internet exchange
locations, remote central offices, and embedded peering points throughout the network.
Benefits of the PTX10001 Router
Scalability—The PTX10001 scales to 3.6 Tbps in a single chassis, supporting up to 144 10-Gigabit Ethernet
•
interfaces, 36 40-Gigabit Ethernet interfaces, and 36 100-Gigabit Ethernet interfaces, giving cloud and
service providers the performance and scalability needed as networks grow.
Performance—The PTX10001’s exceptional packet processing capabilities help alleviate the challenge
•
of scaling the network as traffic levels increase while optimizing IP/MPLS transit functionality around
superior performance. PTX10001 is tailored for LSR core router with support for 128K LSPs.
High availability hardware—The PTX10001 is engineered with hardware redundancy for cooling, power
•
supplies, and forwarding. With the PTX10001’s high availability, service providers can maintain an
always-on infrastructure base and to meet stringent SLAs across the core.
Space efficiency—The PTX10001’s ultra-compact 1U form factor efficiency is a critical requirement for
•
peering internet exchange points, peering collocations, central offices, and regional networks. The
PTX10001 is the first 1RU LSR router with MacSec support built in.
System Overview
The PTX10001 is a fixed-configuration router that supports 10-Gbps, 40-Gbps, and 100-Gbps port speeds
in a single 1U stackable platform.
Control operations are performed by the Routing Engine, which runs the Juniper Networks Junos
•
operating system (Junos OS). The Routing Engine handles routing protocols, traffic engineering, policy,
policing, monitoring, and configuration management. Junos OS is installed on the PTX10001 router’s
internal 2 x 50-gigabyte (GB) M.2 SATA solid-state drives (SSDs). The Routing Engine is enhanced by a
1.6-GHz 4 core Intel CPU and 24 GB of SDRAM.
19
Forwarding operations are performed by the Packet Forwarding Engine, which uses Juniper Networks
•
Express-based silicon. The custom ASICs enable the PTX10001 to provide up to 3.6 Tbps of throughput
and 2 Bpps of forwarding capacity.
TIP: For information about features supported on PTX Series routers, see Feature Explorer.
Port Panel
The port panel of the PTX10001 contains 20 network ports, port LEDs, one bay for an optional expansion
module, console and management ports, and system status LEDs. Figure 1 on page 20 shows the PTX10001
port panel.
Figure 1: PTX10001 Port Panel and Management Panel
g050851
1
6
23
45
4—1—Network port LEDsSystem status LEDs
5—2—Console portNetwork port
6—3—Management portExpansion bay
The 20 network ports on the port panel are QSFP28 ports. Table 3 on page 20 describes the maximum
number of ports for each interface type supported by the PTX10001 with the optional JNP10001-16C-PIC
expansion module installed.
20
Table 3: Maximum Supported Ports at Each Interface Speed
Maximum Supported PortsInterface Type
14410-Gigabit Ethernet
3640-Gigabit Ethernet
36100-Gigabit Ethernet
You manage the PTX10001 by using the Junos OS CLI, which is accessible through the console and
out-of-band management ports on the management panel. In addition, the management panel has system
status LEDs that alert you to minor or major alarms or other issues with the router, external clock
synchronization ports, and a USB port to support software installation and recovery.
Management Panel
The management panel of the PTX10001 is located on the FRU side of the device. It contains management
ports, the fan modules, and power supplies for the PTX10001. Figure 2 on page 21 shows the PTX10001
management panel.
Figure 2: PTX10001 Management Panel
PTP
MGMT
TOD
g050873
23
1
3—1—Power supplies (2)Management ports.
2—Fan modules (5)
PTX10001 Hardware Component Overview
The PTX10001 supports the components in Table 4 on page 21 listed in alphabetic order. See “PTX10001
Physical Specifications” on page 53 the dimensions and weight of the PTX10001.
21
Table 4: PTX10001 Hardware Components
Spare Juniper Model
NumberComponent
PTX10001-CHASChassis
JNP-FAN-1RUFan module
JNP10001-20c
[PTX10001]
PTX10001-M20C Fan
Controller
JPSU-850W-AC-AFOJPSU-850W-AC-AFOPower supplies
JPSU-850W-DC-AFOJPSU-850W-DC-AFO
PTX10001 Component Redundancy
The following hardware components provide redundancy on a PTX10001:
DescriptionCLI Output
“PTX10001 Packet Transport Router
Description” on page 18
“PTX10001 Cooling System” on
page 31
“PTX10001 Power System” on
page 34
Power supplies—The PTX10001 has two power supplies. Each power supply provides power to all
•
components in the device. The two power supplies provide full power redundancy to the device. If one
power supply fails or is removed, the second power supply balances the electrical load without
interruption. To provide power redundancy to the system both power supplies must be installed. Connect
power source feed A to one power supply and power source feed B to the second power supply.
CAUTION: Do not connect feed A and feed B to the same power supply input
terminal.
Cooling system—The PTX10001 has five fan modules. If a fan module fails and the remaining fan modules
•
are unable to keep the PTX10001 within the desired temperature thresholds, chassis alarms occur and
the PTX10001 can shut down.
PTX10001 Field-Replaceable Units
Field-replaceable units (FRUs) are components that you can replace at your site.
CAUTION: Replace a failed fan module with a new fan module within 30 seconds of
removal to prevent chassis overheating.
22
Table 5 on page 22 lists the FRUs for the PTX10001 and actions to take before removing them.
Table 5: Required Actions Before Removing a FRU from the PTX10001
Required Actions Before RemovalFRU
Power supplies (2)
Remove the power cord or cable for the power supply unit. See “Maintaining
the PTX10001 Power Supplies” on page 103.
See “Maintaining the PTX10001 Fan Modules” on page 100.Fan modules (5)
See “Maintaining a PTX10001 Expansion Module” on page 106.Expansion modules
See “Remove a Transceiver” on page 111.Optical transceivers
NOTE: If you have a Juniper Care service contract, register any addition, change, or upgrade of
hardware components at https://www.juniper.net/customers/support/tools/updateinstallbase/
. Failure to do so can result in significant delays if you need replacement parts. This note does
not apply if you replace existing components with the same type of component.
SEE ALSO
RELATED DOCUMENTATION
PTX10001 Port Panel | 23
PTX10001 Management Panel | 29
PTX10001 Cooling System | 31
PTX10001 Power System | 34
PTX10001 Port Panel
23
IN THIS SECTION
PTX10001 Port Panel | 23
PTX10001 Chassis Status LEDs | 25
PTX10001 Management Port LEDs | 27
PTX10001 Network Port LEDs | 28
PTX10001 Port Panel
IN THIS SECTION
Network Ports | 24
Expansion Module Bay | 25
The PTX10001 supports 10-Gbps, 40-Gbps, and 100-Gbps port speeds. Figure 3 on page 24 shows the
PTX10001 port panel.
Figure 3: PTX10001 Port Panel
g050851
1
6
23
45
identification (ID).
24
4—1—Network port LEDsStatus LEDs—Alarm (ALM), system (SYS),
Network ports
Expansion module bay
5—2—RJ-45 console port (CON) to support RS-232 serial
ports.
6—3—RJ-45 (1000BASE-T) management Ethernet port
(labeled MGMT). In the Junos OS CLI, this port is
identified as em0.
Network Ports
The PTX10001 uses 28-Gbps quad small-form factor pluggable plus (QSFP28) sockets that are configured
as 100 Gigabit Ethernet ports by default.
The PTX10001 network ports (0 to 19) support:
100 Gbps QSFP28 transceivers
•
40 Gbps QSFP+ transceivers
•
100 Gbps active optical cables (AOC)
•
40 Gbps AOC
•
QSFP28 direct attach copper (DAC) cables
•
QSFP+ DAC cables
•
QSFP+ direct attach copper break out (DACBO) cables
•
QSFP28 DACBO cables
•
NOTE: Port speeds are configured using the set chassis fpc 0 pic 0 port port-number speed
g050851
1
6
23
45
speed command. You configure ports to operate at a particular speed by using the appropriate
speed option. If you configure a port to operate at a certain speed, and you want to return the
port to the default configuration, delete the speed statement from the configuration at the
[chassis fpc 0 pic 0 port port-number] hierarchy level and commit the configuration. The network
port is reset to the default Ethernet interface.
Expansion Module Bay
The PTX10001 has one bay on the port panel for an optional expansion module. The expansion module
is an addition to the PTX10001 chassis and must be ordered separately.
The PTX10001 supports the JNP10001-16C-PIC expansion module. For more information, see “Expansion
Module for the PTX10001” on page 44.
25
PTX10001 Chassis Status LEDs
The PTX10001 has three status LEDs on the port panel of the chassis, next to the network ports (see
Figure 4 on page 25).
Figure 4: PTX10001 Port Panel
4—1—Network port LEDsStatus LEDs
5—2—RJ-45 console portNetwork ports
6—3—RJ-45 management Ethernet portExpansion module bay
Table 6 on page 26 describes the chassis status LEDs on a PTX10001, their colors and states, and the
status they indicate.
Table 6: Chassis Status LEDs on a PTX10001 Device
26
DescriptionStateColorName
OffUnlitALM–Alarm
On steadilyRed
On steadilyAmber
The device is halted or there is no
alarm.
A major hardware fault has occurred,
such as a temperature alarm or power
failure, and the device has halted.
Power off the device by setting the AC
power source outlet to the OFF (O)
position, or unplugging the AC power
cords. Correct any voltage or site
temperature issues, and allow the
device to cool down. Power on the
device and monitor the power supply
and fan LEDs to help determine where
the error is occurring.
A minor alarm has occurred, such as a
software error. Power off the device
by setting the AC power source outlet
to the OFF (O) position, or unplugging
the AC power cords. Power on the
device and monitor the status LEDs to
ensure that Junos OS boots properly.
The device is powered off or halted.OffUnlitSYS–System
Junos OS is loaded on the device.On steadilyGreen
OffUnlitID–Identification
BlinkingBlue
The beacon feature is not enabled on
the device. This feature is enabled
using the request chassis beacon
command.
The beacon feature is enabled on the
device. This feature is enabled using
the request chassis beacon command.
PTX10001 Management Port LEDs
g050880
21
There are two management ports on the PTX10001, Both ports are labeled MGMT. The RJ-45 management
port is for 10/100/1000BASE-T connections and is located on the port panel. The small form-factor
pluggable (SFP) management port is for 10/100/1000BASE-T and 1000BASE-X connections and is located
on the FRU end of the device.
The RJ-45 port has separate LEDs for status and activity. The SFP port has a LED to indicate both link and
activity. Figure 5 on page 27 shows the location of the LEDs.
Figure 5: Management Port LEDs on a PTX10001
27
2—1—Link activity LED (RJ-45)Status LED (RJ-45)
Table 7 on page 27 describes the RJ-45 management port LEDs.
Table 7: PTX10001 RJ-45 Management Port LEDs
DescriptionStateColorLED
OffUnlitLink activity
No link is established, there is a fault, or the link is
down.
A link is established, and there is link activity.Blinking or flickeringAmber
Either the port speed is 10 Mbps or the link is down.OffUnlitStatus
The port speed is 1000 Mbps.On steadilyGreen
Table 8 on page 28 describes the SFP management port LED.
Table 8: PTX10001 SFP Management Port LED
g050891
1
DescriptionStateColorLED
No link is established, there is a fault, or the link is down.OffUnlitLink
activity
A link is established, but there is no link activity.On steadilyGreen
A link is established, and there is link activity.Blinking or flickering
PTX10001 Network Port LEDs
Each PTX10001 network port uses a single bicolored LED to indicate link status and activity. The circular
LEDs are located underneath the ports. The triangular arrow next to the LED points either up or down
indicating whether the LED is associated with the top or bottom port. Figure 6 on page 28 shows the
location of the LEDs.
28
NOTE: All 36 network port LEDs behave the same. Including the 16 network port LEDs located
on the JNP10001-16C-PIC expansion module.
Figure 6: Network Port LEDs on a PTX10001
1—Network port LEDs
The number next to the LED indicates the port number that the LED belongs to and the arrow next to the
LED indicates if it is the top or bottom port.
NOTE: The same bicolored LED also indicates status when the port is configured to operate as
four 10-Gigabit Ethernet interfaces.
Table 9 on page 29 describes the network port LEDs.
Table 9: PTX10001 Network Port LEDs
29
DescriptionStateColor
OffUnlit
On steadilyAmber
RELATED DOCUMENTATION
PTX10001 System Overview | 18
PTX10001 Management Panel | 29
show chassis alarms
request chassis beacon
The port is administratively disabled, there is no power, the link is down,
or a transceiver is not present.
A link is established.On steadilyGreen
The beacon function was enabled on the port.Blinking
When the port is configured to operate as four 10-Gigabit Ethernet
interfaces, indicates that one or more interfaces (but not all four) are up.
There are one or more errors on the connections.Blinking
PTX10001 Management Panel
IN THIS SECTION
PTX10001 Management Panel | 29
PTX10001 Management Panel
The PTX10001 management panel is found on the Field Replaceable Unit (FRU) end of the device.
You manage the PTX10001 by using the Junos OS CLI, which is accessible through the console and
PTP
MGMT
TOD
g050853
546
910
8
3
2
1
7
out-of-band management ports on the management panel. In addition, the management panel has system
status LEDs that alert you to minor or major alarms or other issues with the router, external clock
synchronization ports, and a USB port to support software installation and recovery. See
Figure 7 on page 30for management panel details.
Figure 7: PTX10001 Management Panel
6—1—Power suppliesSFP PTP Ethernet (1000BASE-T) port (labeled PTP).
The PTP port is not currently supported. It is reserved
for future use.
30
SFP management Ethernet port (labeled MGMT). In
the Junos OS CLI, this port is identified as em2.
RS-232 Time-of-day port (labeled TOD). The TOD
port is not currently supported. It is reserved for
future use.
Electrostatic discharge (ESD) terminal
RELATED DOCUMENTATION
PTX10001 System Overview | 18
PTX10001 Port Panel | 23