Juniper PTX1000 User manual

PTX1000 Packet Transport Router

Hardware Guide

Published

2020-06-02

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.

PTX1000 Packet Transport Router Hardware Guide

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

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.

ii

Table of Contents

About the Documentation | ix

Documentation and Release Notes | ix

Using the Examples in This Manual | ix

Merging a Full Example | x

Merging a Snippet | xi

Documentation Conventions | xi

Documentation Feedback | xiv

Requesting Technical Support | xiv

Self-Help Online Tools and Resources | xv

Creating a Service Request with JTAC | xv

Overview

1

PTX1000 System Overview | 17

PTX1000 Packet Transport Router Description | 17

Benefits of the PTX1000 Router | 18

Port Panel and Management Panel | 19

FRU Panel | 20

PTX1000 Hardware Component Overview | 21

PTX1000 Component Redundancy | 21

PTX1000 Field-Replaceable Units | 22

PTX1000 Port Panel | 23

Example: Using Network Ports as 40-Gigabit Ethernet Interfaces | 25

Example: Using Network Ports as 100-Gigabit Ethernet Interfaces | 25

PTX1000 Port Mapping | 26

PTX1000 Network Port LEDs | 31

PTX1000 Management Panel | 32

PTX1000 Management Port LEDs | 33

PTX1000 Chassis Status LEDs | 35

iii

PTX1000 Cooling System | 36

PTX1000 Cooling System Description | 36

Fan Modules | 36

Airflow Through the Chassis | 37

PTX1000 Fan Module LEDs | 38

PTX1000 Power System | 39

PTX1000 AC Power Supply Description | 40

PTX1000 DC Power Supply Description | 41

PTX1000 Power Supply LEDs | 43

PTX1000 AC Power Specifications | 44

PTX1000 AC Power Cord Specifications | 45

PTX1000 DC Power Specifications | 46

PTX1000 DC Power Cable Specifications | 47

Site Planning, Preparation, and Specifications

2

PTX1000 Site Preparation Checklist | 50

PTX1000 Site Guidelines and Requirements | 51

PTX1000 Environmental Requirements and Specifications | 52

General Site Guidelines | 53

PTX1000 Chassis Grounding Cable and Lug Specifications | 53

PTX1000 Clearance Requirements for Airflow and Hardware Maintenance | 54

PTX1000 Physical Specifications | 55

Site Electrical Wiring Guidelines | 56

PTX1000 Rack Requirements | 56

PTX1000 Network Cable and Transceiver Planning | 58

Determining Transceiver Support for the PTX1000 | 58

Cable and Connector Specifications for MX and PTX Series Devices | 59

12-Fiber MPO Connectors | 60

24-Fiber MPO Connectors | 64

iv

LC Duplex Connectors | 64

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

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

Attenuation and Dispersion in Fiber-Optic Cable | 66

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

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

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

PTX1000 Management Cable Specifications and Pinouts | 69

Cable Specifications for Console and Management Connections for the PTX1000 | 69

Management Port Connector Pinouts for the PTX1000 | 70

Console Port Connector Pinouts for the PTX1000 | 70

USB Port Specifications for the PTX1000 | 71

Initial Installation and Configuration

3

PTX1000 Installation Overview | 73

Overview of Installing the PTX1000 | 73

PTX1000 Installation Safety Guidelines | 74

General Installation Safety Guidelines | 74

PTX1000 Chassis Lifting Guidelines | 74

Unpacking and Mounting the PTX1000 | 75

Unpacking the PTX1000 | 75

Mounting the PTX1000 in a Rack | 76

Before You Begin Mounting the PTX1000 | 77

Mounting the PTX1000 | 78

Connecting the PTX1000 to Power | 80

Connecting the PTX1000 to Ground | 81

Connecting AC Power to the PTX1000 | 82

Connecting DC Power to the PTX1000 | 85

v

Connecting the PTX1000 to External Devices | 89

Connecting the PTX1000 to a Management Ethernet Device | 89

Connecting the PTX1000 to a Management Console | 90

Performing the Initial Software Configuration for the PTX1000 | 92

Powering Off the PTX1000 | 94

Maintaining Components

4

Maintaining the PTX1000 Fan Modules | 98

Removing a Fan Module from the PTX1000 | 98

Installing a Fan Module in the PTX1000 | 99

Maintaining the PTX1000 Power Supplies | 101

Removing a Power Supply from the PTX1000 | 101

Installing a Power Supply in a PTX1000 | 103

Maintaining the PTX1000 Transceivers and Fiber-Optic Cables | 104

Removing a Transceiver from the PTX1000 | 105

Installing a Transceiver in the PTX1000 | 106

Disconnecting a Fiber-Optic Cable from the PTX1000 | 108

Connecting a Fiber-Optic Cable to the PTX1000 | 109

Maintaining Fiber-Optic Cables in a PTX1000 | 110

Uninstalling the PTX1000 | 111

Troubleshooting Hardware

5

Troubleshooting the PTX1000 | 114

PTX1000 Troubleshooting Resources Overview | 114

PTX1000 Alarm Messages Overview | 115

Chassis Alarm Messages on the PTX1000 | 115

Returning the Chassis or Components

6

Returning the PTX1000 Chassis or Components | 121

Locating the Serial Number on a PTX1000 Chassis or Component | 121

Listing the Chassis and Component Details by Using the CLI | 122

Locating the Chassis Serial Number ID Label on a PTX1000 | 123

vi

Locating the Serial Number ID Labels on FRU Components | 123

How to Contact Customer Support to Obtain Return Material Authorization | 123

Packing a PTX1000 Chassis or Component for Shipping | 124

Packing a PTX1000 for Shipping | 124

Packing PTX1000 Components for Shipping | 125

Safety and Compliance Information

7

PTX1000 General Electrical Safety Guidelines and Warnings | 129

Definitions of Safety Warning Levels | 130

Qualified Personnel Warning | 133

Warning Statement for Norway and Sweden | 134

Fire Safety Requirements | 134

Fire Suppression | 134

Fire Suppression Equipment | 134

Installation Instructions Warning | 136

Chassis and Component Lifting Guidelines | 136

Restricted Access Warning | 138

Ramp Warning | 140

Rack-Mounting and Cabinet-Mounting Warnings | 141

Grounded Equipment Warning | 147

Radiation from Open Port Apertures Warning | 148

Laser and LED Safety Guidelines and Warnings | 149

General Laser Safety Guidelines | 149

Class 1 Laser Product Warning | 150

Class 1 LED Product Warning | 151

Laser Beam Warning | 152

Maintenance and Operational Safety Guidelines and Warnings | 152

Battery Handling Warning | 154

Jewelry Removal Warning | 155

vii

Lightning Activity Warning | 157

Operating Temperature Warning | 158

Product Disposal Warning | 160

PTX1000 Compliance Statements for Acoustic Noise | 161

Action to Take After an Electrical Accident | 161

Prevention of Electrostatic Discharge Damage | 161

AC Power Electrical Safety Guidelines | 163

AC Power Disconnection Warning | 164

PTX1000 DC Power Electrical Safety Guidelines | 164

DC Power Copper Conductors Warning | 165

DC Power Disconnection Warning | 166

DC Power Grounding Requirements and Warning | 168

DC Power Wiring Sequence Warning | 170

DC Power Wiring Terminations Warning | 173

Multiple Power Supplies Disconnection Warning | 176

TN Power Warning | 177

PTX1000 Agency Approvals and Compliance Statements | 177

PTX1000 Agency Approvals | 178

Compliance Statements for EMC Requirements | 178

Canada | 179

European Community | 179

Israel | 179

Japan | 179

United States | 179

Compliance Statements for Environmental Requirements | 180

PTX1000 Compliance Statements for Acoustic Noise | 180

viii

About the Documentation

IN THIS SECTION

Documentation and Release Notes | ix

Using the Examples in This Manual | ix

Documentation Conventions | xi

Documentation Feedback | xiv

Requesting Technical Support | xiv

Use this guide to install hardware and perform initial software configuration, routine maintenance, and

troubleshooting for the PTX1000 Packet Transport Router.

After completing the installation and basic configuration procedures covered in this guide, refer to the

Junos OS documentation for information about 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.

ix

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;

}

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

x

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]

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 xii defines notice icons used in this guide.

xi

Table 1: Notice Icons

DescriptionMeaningIcon

Indicates important features or instructions.Informational note

Indicates a situation that might result in loss of data or hardware

damage.

Caution

Alerts you to the risk of personal injury or death.Warning

Alerts you to the risk of personal injury from a laser.Laser warning

Indicates helpful information.Tip

Alerts you to a recommended use or implementation.Best practice

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

Table 2: Text and Syntax Conventions

ExamplesDescriptionConvention

To enter configuration mode, type

the configure command:

user@host> configure

Represents text that you type.Bold text like this

user@host> show chassis alarms

No alarms currently active

Represents output that appears on

the terminal screen.

Fixed-width text like this

•

A policy term is a named structure

that defines match conditions and

actions.

•

Junos OS CLI User Guide

•

RFC 1997, BGP Communities

Attribute

•

Introduces or emphasizes important

new terms.

•

Identifies guide names.

•

Identifies RFC and Internet draft

titles.

Italic text like this

xii

Table 2: Text and Syntax Conventions (continued)

ExamplesDescriptionConvention

Configure the machine’s domain

name:

[edit]

root@# set system domain-name

domain-name

Represents variables (options for

which you substitute a value) in

commands or configuration

statements.

Italic text like this

•

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.

Represents names of configuration

statements, commands, files, and

directories; configuration hierarchy

levels; or labels on routing platform

components.

Text like this

stub <default-metric metric>;Encloses optional keywords or

variables.

< > (angle brackets)

broadcast | multicast

(string1 | string2 | string3)

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.

| (pipe symbol)

rsvp { # Required for dynamic MPLS

only

Indicates a comment specified on the

same line as the configuration

statement to which it applies.

# (pound sign)

community name members [

community-ids ]

Encloses a variable for which you can

substitute one or more values.

[ ] (square brackets)

[edit]

routing-options {

static {

route default {

nexthop address;

retain;

}

Identifies a level in the configuration

hierarchy.

Indention and braces ( { } )

Identifies a leaf statement at a

configuration hierarchy level.

; (semicolon)

GUI Conventions

xiii

Table 2: Text and Syntax Conventions (continued)

ExamplesDescriptionConvention

•

In the Logical Interfaces box, select

All Interfaces.

•

To cancel the configuration, click

Cancel.

Represents graphical user interface

(GUI) items you click or select.

Bold text like this

In the configuration editor hierarchy,

select Protocols>Ospf.

Separates levels in a hierarchy of

menu selections.

> (bold right angle bracket)

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 [email protected]. 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

xiv

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/

•

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

xv

1

CHAPTER

Overview

PTX1000 System Overview | 17

PTX1000 Port Panel | 23

PTX1000 Management Panel | 32

PTX1000 Cooling System | 36

PTX1000 Power System | 39

PTX1000 System Overview

IN THIS SECTION

PTX1000 Packet Transport Router Description | 17

PTX1000 Hardware Component Overview | 21

PTX1000 Component Redundancy | 21

PTX1000 Field-Replaceable Units | 22

PTX1000 Packet Transport Router Description

IN THIS SECTION

Benefits of the PTX1000 Router | 18

Port Panel and Management Panel | 19

FRU Panel | 20

The Juniper Networks PTX1000 Packet Transport Router is a fixed-configuration router that supports

10-Gbps, 40-Gbps, and 100-Gbps port speeds in a compact 2U form factor, enabling service providers to

organically distribute peering points throughout the network.

The system architecture cleanly separates control operations from packet forwarding operations. This

design eliminates processing and traffic bottlenecks, permitting the PTX1000 to achieve high performance.

•

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 PTX1000 router’s

internal 2 x 64-gigabyte (GB) M.2 SATA solid-state drives (SSDs). The 64-GB SSDs have 50 GB of usable

space—the remaining space is reserved. The Routing Engine is enhanced by a 2.5-GHz quad core Intel

CPU and 32 GB of SDRAM.

17

NOTE: The 2 x 64-GB SSDs installed in the PTX1000 support the request vmhost snapshot

command, which creates a recovery snapshot of the currently running and active file system

partitions, and request vmhost snapshot recovery command, which recovers the primary disk

from the snapshot content stored in the backup disk. In addition, the 64-GB SSDs support

enhanced hardware resiliency through storage partitioning and redundancy.

Earlier versions of the PTX1000 have 2 x 32-GB M.2 SATA SSDs. PTX1000 routers with 32-GB

SSDs do not support the request vmhost snapshot and request vmhost snapshot recovery

commands, and do not support enhanced hardware resiliency. To determine the size of the

SSDs installed in your device, issue the show vmhost hardware CLI command. The capacity

of Disk1 and Disk2 is displayed in the output as 32.0 GB if 32-GB SSDs are installed, and the

capacity is displayed as 50.0 GB if 64-GB SSDs are installed. See the Software Installation and

Upgrade Guide for more information.

•

Forwarding operations are performed by the Packet Forwarding Engines, which include ASICs designed

by Juniper Networks. The custom ExpressPlus ASICs enable the PTX1000 to provide up to 2.88 terabits

per second (Tbps) of forwarding capacity. The ExpressPlus ASICs are connected to Hybrid Memory

Cubes (HMCs). These high-efficiency memory modules provide packet buffering, virtual output queue

(VOQ) memory, and improved logical system scale.

TIP: For information about features supported on PTX Series routers, see Feature Explorer.

Benefits of the PTX1000 Router

•

Increased scalability—The PTX1000 scales to 3 Tbps in a single chassis, supporting up to 288 10-Gigabit

Ethernet interfaces, 72 40-Gigabit Ethernet interfaces, and 24 100-Gigabit Ethernet interfaces, giving

service providers the performance and scalability needed as networks grow. The purpose-built ASICs

in the PTX1000 provide enhanced packet processing for both full IP functionality and MPLS transport,

accommodating scale as traffic continues to increase and optimizing IP/MPLS transit functionality.

•

Space efficiency—Providing high capacity in a compact 2U form-factor, the PTX1000 meets installation

needs for peering Internet exchange points, peering collocations, central offices, and regional networks,

especially in emerging markets.

•

Always-on infrastructure base—The PTX1000 is engineered with full hardware redundancy for cooling,

power supplies, and forwarding, allowing service providers to meet stringent service-level agreements

across the core.

18

Port Panel and Management Panel

The port panel of the PTX1000 contains 72 network ports and port LEDs. The management panel of the

PTX1000 contains console and management ports, a reset button, system status LEDs, clocking ports, and

a USB port. Figure 1 on page 19 shows the PTX1000 port panel and management panel.

Figure 1: PTX1000 Port Panel and Management Panel

2—1— Management panelPort panel

Each of the 72 network ports on the port panel supports quad small form-factor pluggable plus (QSFP+)

transceivers, and is configured as a channelized 4 x 10-Gigabit Ethernet interface by default (for a maximum

of 288 10-Gigabit Ethernet ports). You can configure each of the 72 ports as a 40-Gigabit Ethernet interface.

You can also configure 24 of the 72 network ports as 100-Gigabit Ethernet interfaces. Table 3 on page 19

describes the maximum number of ports for each interface type supported by the PTX1000.

Table 3: Maximum Supported Ports at Each Interface Speed

Maximum Supported PortsInterface Type

28810-Gigabit Ethernet

7240-Gigabit Ethernet

24100-Gigabit Ethernet

NOTE: You can purchase a licensed model of the PTX1000 that allows you to use 18 of the 72

network ports. You can use 18 ports in any combination, for a maximum of 72 10-Gigabit Ethernet

interfaces, 18 40-Gigabit Ethernet interfaces, or 6 100-Gigabit Ethernet interfaces. You can

purchase additional licenses to enable the remaining network ports. Each license enables an

additional 18 of the 72 total network ports.

19

You manage the PTX1000 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.

For more information about the port and management panels, see “PTX1000 Port Panel” on page 23 and

“PTX1000 Management Panel” on page 32.

FRU Panel

The field-replaceable unit (FRU) panel of the PTX1000 contains the fan modules and power supplies for

the PTX1000. Figure 2 on page 20 shows the PTX1000 FRU panel.

Figure 2: PTX1000 FRU Panel

3—1— ESD pointPower supplies (4)

2—Fan modules (3)

The cooling system in a PTX1000 consists of three 80-W fan modules that operate at 150 cubic feet per

minute (CFM) at full speed as well as fans housed in the power supplies. Each fan module has dual

counter-rotating fans. These fan modules can be hot-swapped—you do not need to power off the router

or disrupt routing function to replace a fan module.

In the PTX1000 cooling system, cool air enters through the vents in the port panel and hot air exhausts

through the FRU panel. This type of airflow is known as airflow out or port-to-FRU airflow.

The PTX1000 has four 1600-W power supplies, either AC or DC depending on your configuration. Each

power supply provides 12-VDC output with a standby voltage of 12 VDC. The power supplies can be

hot-swapped—you do not need to power off the router or disrupt routing function to replace a power

supply

For more information about the components on the FRU panel, see “PTX1000 Cooling System Description”

on page 36, “PTX1000 AC Power Supply Description” on page 40, and “PTX1000 DC Power Supply

Description” on page 41.

20

Page is loading ...

Juniper PTX1000 User manual

Related papers

Other documents