Juniper ACX2200 Hardware Guide

ACX2200 Universal Metro Router

Published

2020-11-10

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.

ACX2200 Universal Metro 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.

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

iii

Overview

ACX2200 System Overview | 17

ACX2200 Universal Metro Router Overview | 17

Benefits of the ACX2200 Router | 17

Chassis Description | 18

ACX2200 Routers Hardware and CLI Terminology Mapping | 19

Packet Flow on ACX Series Routers | 21

Protocols and Applications Supported by the ACX2200 Router | 23

ACX2200 Chassis Components | 31

Front Panel of an ACX2200 Router | 31

Uplink Ports on ACX2200 Routers | 33

Gigabit Ethernet RJ-45 Ports | 34

Gigabit Ethernet SFP Ports | 34

10-Gigabit Ethernet SFP+ Ports | 35

Alarm Contact Port on the ACX2200 Router | 36

Clocking Ports on the ACX2200 Router | 37

LEDs on ACX2200 Routers | 38

System LED on the Front Panel | 39

Ethernet Port LEDs | 39

SFP and SFP+ Port LEDs | 39

Management and Console Port LEDs on the Front Panel | 40

Cooling System and Airflow in an ACX2200 Router | 41

ACX2200 Power System | 42

ACX2200 Power Overview | 42

ACX2200 AC Power Specifications | 42

ACX2200 AC Power Cord Specifications | 43

ACX2200 DC Power Specifications | 45

Site Planning, Preparation, and Specifications

Site Preparation Checklist for ACX2200 Routers | 48

ACX2200 Site Guidelines and Requirements | 49

General Site Guidelines | 50

Site Electrical Wiring Guidelines | 50

Chassis Physical Specifications for ACX2200 Routers | 51

ACX2200 Router Environmental Specifications | 51

ACX2200 Chassis Grounding Cable and Lug Specifications | 53

Grounding Points Specifications | 53

Grounding Cable Lug Specifications | 54

Grounding Cable Specifications | 55

Clearance Requirements for Airflow and Hardware Maintenance on ACX2200 Routers | 56

Cabinet Requirements for ACX2200 Routers | 57

Rack Requirements for ACX2200 Routers | 58

ACX2200 Network Cable and Transceiver Planning | 60

Determining Transceiver Support and Specifications | 60

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

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

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

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

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

Attenuation and Dispersion in Fiber-Optic Cable | 64

ACX2200 Alarm, Management, and Clocking Cable Specifications and Pinouts | 65

Alarm Contact Connector Pinouts | 65

Management Port Connector Pinout Information for ACX Series Routers | 68

Console or Auxiliary Port Connector Pinout on ACX Series Routers | 68

USB Port Specifications for an ACX Series Router | 69

Clocking Port Specifications on the ACX2200 Router | 70

External Clocking Port Connector Specifications | 70

External Clocking Input Port Specifications | 70

Initial Installation and Configuration

Installing and Connecting an ACX2200 Router Overview | 73

Unpacking and Mounting the ACX2200 | 73

Unpacking an ACX2200 Router | 74

Parts Inventory (Packing List) for an ACX2200 Router | 75

Installing the ACX2200 Mounting Brackets | 76

Installing the ACX2200 Router in the Rack | 77

Connecting the ACX2200 to Power | 79

Connecting the ACX2200 Router to Earth Ground | 79

Connecting AC Power Cords to the ACX2200 Router | 81

Connecting DC Power Cables to the ACX2200 Router | 82

Connecting the ACX2200 to External Devices | 85

Connecting ACX2200 Routers to Management Devices | 85

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

Connecting the Router to a Management Console or Auxiliary Device | 86

Connecting ACX2200 Routers to an External Alarm-Reporting Device | 87

Connecting ACX2200 Routers to External Clocking Devices | 88

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

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

Initially Configuring the ACX2200 Router | 90

Maintaining Components

Maintaining ACX2200 Components | 96

Routine Maintenance Procedures for the ACX2200 Router | 96

Maintaining Cables That Connect to ACX2200 Network Ports | 96

Maintaining the ACX2200 Uplink Ports | 97

Replacing ACX2200 Hardware Components | 98

Replacing an ACX2200 Console or Auxiliary Cable | 98

Replacing an ACX2200 Management Ethernet Cable | 99

Replacing an ACX2200 Fiber-Optic Cable | 100

Replacing an ACX2200 Transceiver | 102

Troubleshooting Hardware

Troubleshooting the ACX2200 | 107

Troubleshooting Resources for ACX2200 Routers | 107

Command-Line Interface | 107

Front Panel LEDs | 107

Monitoring System Log Messages | 108

Alarm Types and Severity Classes on ACX Series Routers | 108

Alarm Types | 109

Alarm Severity Classes | 109

Verifying Active Alarms | 109

Contacting Customer Support and Returning the Chassis or Components

Contacting Customer Support and Returning the Chassis or Components | 112

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

Locating the Serial Number on a ACX2200 Chassis or Component | 113

ACX2200 Chassis Serial Number Label | 114

Guidelines for Packing Hardware Components for Shipment | 114

Packing the ACX Series Router for Shipment | 115

Safety and Compliance Information

General Safety Guidelines and Warnings | 119

Definitions of Safety Warning Levels | 120

Qualified Personnel Warning | 123

Warning Statement for Norway and Sweden | 124

Fire Safety Requirements | 124

Fire Suppression | 124

Fire Suppression Equipment | 124

Installation Instructions Warning | 126

Chassis and Component Lifting Guidelines | 126

Restricted Access Warning | 128

Ramp Warning | 130

Rack-Mounting and Cabinet-Mounting Warnings | 131

Grounded Equipment Warning | 137

Radiation from Open Port Apertures Warning | 138

vii

Laser and LED Safety Guidelines and Warnings | 139

General Laser Safety Guidelines | 139

Class 1 Laser Product Warning | 140

Class 1 LED Product Warning | 141

Laser Beam Warning | 142

Maintenance and Operational Safety Guidelines and Warnings | 142

Battery Handling Warning | 144

Jewelry Removal Warning | 145

Lightning Activity Warning | 147

Operating Temperature Warning | 148

Product Disposal Warning | 150

General Electrical Safety Guidelines and Warnings | 151

Action to Take After an Electrical Accident | 152

Prevention of Electrostatic Discharge Damage | 152

AC Power Electrical Safety Guidelines | 154

AC Power Disconnection Warning | 155

ACX2200 DC Power Electrical Safety Guidelines | 156

DC Power Copper Conductors Warning | 157

DC Power Disconnection Warning | 158

DC Power Grounding Requirements and Warning | 160

DC Power Wiring Sequence Warning | 162

DC Power Wiring Terminations Warning | 165

Midplane Energy Hazard Warning | 167

Multiple Power Supplies Disconnection Warning | 168

TN Power Warning | 169

Agency Approvals for ACX2200 Routers | 169

Compliance Statements for NEBS for ACX2200 Routers | 171

viii

Compliance Statements for EMC Requirements for ACX2200 Routers | 172

Canada | 172

European Community | 172

Israel | 172

Japan | 173

United States | 173

Compliance Statements for Environmental Requirements | 174

Compliance Statements for Acoustic Noise for ACX2200 Routers | 174

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 ACX2200 Universal Metro 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.

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

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.

Table 1: Notice Icons

xii

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 xii 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)

xiii

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)

xiv

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/

•

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

CHAPTER

Overview

ACX2200 System Overview | 17

ACX2200 Chassis Components | 31

Cooling System and Airflow in an ACX2200 Router | 41

ACX2200 Power System | 42

ACX2200 System Overview

IN THIS SECTION

ACX2200 Universal Metro Router Overview | 17

ACX2200 Routers Hardware and CLI Terminology Mapping | 19

Packet Flow on ACX Series Routers | 21

Protocols and Applications Supported by the ACX2200 Router | 23

ACX2200 Universal Metro Router Overview

IN THIS SECTION

Benefits of the ACX2200 Router | 17

Chassis Description | 18

The ACX2200 Universal Metro Router is principally designed to provide superior management for rapid provisioning to the access network. The ACX Series routers support rich Gigabit Ethernet and 10-Gigabit Ethernet capabilities for uplink, along with support for legacy interfaces and Gigabit Ethernet interfaces for radio and NodeB connectivity in a compact form factor that is environmentally hardened and passively cooled. Seamless, end-to-end MPLS can be used to address legacy and emerging requirements to provide the foundation for a converged network that utilizes the same mobile backhaul infrastructure for business or residential services.

Benefits of the ACX2200 Router

Flexible design—A built-in service engine makes the ACX2200 fully customizable and future-proof for

•

LTE-Advanced and 5G requirements. The ACX2200 provides a seamless, end-to-end service delivery platform that can grow and adapt to changing subscriber expectations and traffic demands.

Improved operational efficiency with zero-touch deployment (ZTD)—The ACX Series routers support

•

a zero-touch deployment (ZTD) model that significantly reduces the time for any new equipment installation and provisioning, resulting in improved operational efficiency.

Installation flexibility with an environmentally hardened design—Most ACX Series routers are temperature

•

hardened and support passive cooling for outdoor deployments in extreme weather conditions.

Chassis Description

The ACX Series router is a single-board router with a built-in Routing Engine and one Packet Forwarding Engine that has one “pseudo” Flexible PIC Concentrator (FPC 0 in the CLI). Because there is no switching fabric, the single Packet Forwarding Engine takes care of both ingress and egress packet forwarding:

Routing Engine—Provides Layer 3 routing services and network management.

•

Packet Forwarding Engine—Performs Layer 2 and Layer 3 packet switching, route lookups, and packet

•

forwarding.

The ACX Series router is powered by Junos OS, supporting extensive L2 and L3 features, IP and MPLS with traffic engineering, rich network management, fault management, service monitoring and Operation, Administration, and Maintenance (OAM) capabilities, and an open software development kit (SDK) system that allows providers to customize and integrate operations with their own management systems. For a list of related Junos OS documentation, see https://www.juniper.net/documentation/software/junos/.

As part of the mobile backhaul, the ACX Series router at the cell site and the MX Series router at the aggregation layer provide comprehensive end-to-end Ethernet, MPLS, and OAM features with the one Junos OS running on both platforms.

The ACX2200 router is a compact gateway router that is one rack unit (U; that is, 1.75 in., or 4.45 cm) tall. Several gateway routers can be stacked in a single floor-to-ceiling rack for increased port density per unit of floor space.

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

Figure 1 on page 19 and Figure 2 on page 19). The chassis measures 1.75 in. (4.45 cm) high, 9.4 in. (24 cm)

deep, and 17.5 in. (44.5 cm) wide. The outer edges of the mounting brackets extend the width to 19 in. (48 cm) (from the front-mounting brackets to the rear of the chassis). The chassis installs in standard

11.81-in. (300-mm) deep (or larger) enclosed cabinets, 19-in. equipment racks, or telco open-frame racks.

The compact routers are 1 U tall. Several routers can be stacked in a single floor-to-ceiling rack for increased port density per unit of floor space.

The ACX2200 routers contain four Gigabit Ethernet RJ-45 ports, four Gigabit Ethernet combination ports (either Gigabit Ethernet RJ-45 ports or Gigabit Ethernet SFP ports), two Gigabit Ethernet SFP ports, and two 10-Gigabit Ethernet SFP+ ports. Use only one set of these combination ports (labeled COMBO PORTS) at a time.

Figure 1: Front Panel of the ACX2200 Router

g017847

g006403

Figure 2: Rear View of the ACX2200 Router

ACX2200 Routers Hardware and CLI Terminology Mapping

Table 3 on page 19 describes the hardware terms used in ACX2200 router documentation and the

corresponding terms used in the Junos OS command line interface (CLI). Figure 3 on page 21 shows the port locations of the interfaces.

Table 3: CLI Equivalents of Terms Used in Documentation for ACX2200 Routers

Hardware Item (as displayed in the CLI)

FPC (n)

Description (as displayed in the CLI)

Abbreviated name of the Flexible PIC Concentrator (FPC)

ACX2200

Value (as displayed in the CLI)

Value of n is always

Item in Documentation

Router chassis–ACX2200Chassis

The router does not have actual FPCs. In this case, FPC refers to the router itself

Additional Information

“Chassis Physical Specifications for ACX2200 Routers” on page 51

Interface Naming

Conventions Used in the

Junos OS Operational

Commands

Table 3: CLI Equivalents of Terms Used in Documentation for ACX2200 Routers (continued)

Hardware Item (as displayed in the CLI)

PIC (n)

Description (as displayed in the CLI)

Abbreviated name of the Physical Interface Card (PIC)

4x 1GE (RJ-45)

•

4x 1GE (SFP)

•

Value (as displayed in the CLI)

n is a value in the range of 0–3.

PIC 04x 1GE (RJ-45)

PIC 1One of the following:

Item in Documentation

The router does not have actual PIC devices; see entries for PIC 0 through PIC 3 for the equivalent item on the router

Built-in uplink ports on the front panel of the router

Additional Information

Interface Naming

Conventions Used in the

Junos OS Operational

Commands

“ACX2200 Universal Metro Router Overview” on page 17

Xcvr (n)

Abbreviated name of the transceiver

Built-in power supplyPower supply (n)

PIC 22x 1GE (SFP)

PIC 32x 10GE (SFP+)

n is a value equivalent to the number of the port in which the transceiver is installed.

Built-in uplink ports on the front panel of the router

Optical transceivers

DC power supplyValue of n is always

“ACX2200 Universal Metro Router Overview” on page 17

“Uplink Ports on ACX2200 Routers” on page 33

“ACX2200 Power Overview” on page 42

Table 3: CLI Equivalents of Terms Used in Documentation for ACX2200 Routers (continued)

g017872

ACX2200

MGMT CONSOLE/AUX

SYS

0 1

EXTREF CLKIN

ALARM

OUTIN IN OUT

1PPS 10MHz

0/0/0

0/0/2

0/0/1 0/1/10/1/0

0/0/3 0/1/2GE0/1/3

COMBOPORTS XE

0/3/0

0/3/1GE

0/1/2 0/1/3 0/2/1

0/1/0 0/1/1

0/2/0

FPC 0, PIC 0 GE 0/0/0-0/0/3

FPC 0, PIC 2 GE 0/2/0-0/2/1

FPC 0, PIC 1 GE 0/1/0-0/1/3

FPC 0, PIC 3 XE 0/3/0-0/3/1

Incoming packet

Ingress classification

In order of decreasing precedence:

MF classification (DFW) Fixed classification BA classification

Queuing Egress rewrite

Outgoing packet

g006408

Buffering Scheduling

Hardware Item (as displayed in the CLI)

Description (as displayed in the CLI)

Fan

NOTE: ACX2200

routers are fanless models.

Figure 3: ACX2200 Interface Port Mapping

Value (as displayed in the CLI)

Item in Documentation

Fan–Fan

Additional Information

“Cooling System and Airflow in an ACX2200 Router” on page 41

Packet Flow on ACX Series Routers

The class-of-service (CoS) architecture for ACX Series routers is in concept similar to that of MX Series routers. The general architecture for ACX Series routers is shown in Figure 4 on page 21.

Figure 4: ACX Series Router Packet Forwarding and Data Flow

Based on the model, ACX routers contain a built-in Routing Engine and Packet Forwarding Engine and can contain both T1/E1 and Gigabit Ethernet Ports.

The Packet Forwarding Engine has one or two “pseudo” Flexible PIC Concentrators. Because there is no switching fabric, the single Packet Forwarding Engine takes care of both ingress and egress packet forwarding.

Fixed classification places all packets in the same forwarding class, or the usual multifield (MF) or behavior aggregate (BA) classifications can be used to treat packets differently. BA classification with firewall filters

can be used for classification based on IP precedence, DSCP, IEEE, or other bits in the frame or packet

g006428

Rate limiting

BA and fixed classification

Forwarding class and packet loss priority

MF classification

Policing can overwrite forwarding class and packet loss priority

Forwarding class and packet loss priority determine rewrite value

Scheduling and shaping

Scheduling and shaping Forwarding class Qn + packet loss priority

WRED

header.

However, the ACX Series routers can also employ multiple BA classifiers on the same physical interface. The physical interfaces do not have to employ the same type of BA classifier. For example, a single physical interface can use classifiers based on IP precedence as well as IEEE 802.1p. If the CoS bits of interest are on the inner VLAN tag of a dual-tagged VLAN interface, the classifier can examine either the inner or outer bits. (By default, the classification is done based on the outer VLAN tag.)

Eight queues per egress port support scheduling using the weighted deficit round- robin (WDRR) mechanism, a form of round-robin queue servicing. The supported priority levels are strict-high and default (low). The ACX series router architecture supports both weighted random early detect (WRED) and weighted tail drop (WTD).

All CoS features are supported at line rate.

The packet pipeline through an ACX Series router is shown in Figure 5 on page 22. Note that the rate limiting is done with an integrated architecture along with all other CoS functions. Scheduling and shaping are supported on the output side.

Figure 5: ACX Series Router Packet Handling

Protocols and Applications Supported by the ACX2200 Router

Table 4 on page 23 contains the first Junos OS Release support for protocols and applications on ACX2200

routers. A dash indicates that the protocol or application is not supported.

NOTE: The [edit logical-systems logical-system-name] hierarchy level is not supported on ACX

Series routers.

Table 4: Protocols and Applications Supported by ACX2200 Routers

First Supported Junos OS ReleaseProtocol or Application

Interface and Encapsulation Types

Ethernet interfaces—10/100/1000, 1G, 10G

Layer 3

Static routes

OSPF

IS-IS

12.3X54 –D15

–ATM Interfaces (including IMA interfaces)

–E1 Interfaces

–T1 Interfaces

–Circuit emulation interfaces

12.3X54 –D15

Internet Control Message Protocol (ICMP)

Address Resolution Protocol (ARP)

12.3X54 –D15

Table 4: Protocols and Applications Supported by ACX2200 Routers (continued)

First Supported Junos OS ReleaseProtocol or Application

Bidirectional Forwarding Detection (BFD) protocol

Dynamic Host Configuration Protocol (DHCP)

IP fast reroute (FRR) (OSPF, IS-IS)

Maximum transmission unit (MTU) 1518

RSVP

LDP (targeted and direct)

MPLS, VPLS, VPNs

Static label-switched path (LSP)

12.3X54 –D15

FRR

Traffic engineering

Diffserv traffic engineering

E-LINE

Pseudowire Emulation Edge to Edge [PWE3 (signaled)]

Static Ethernet PWs

12.3X54 –D15

Table 4: Protocols and Applications Supported by ACX2200 Routers (continued)

First Supported Junos OS ReleaseProtocol or Application

Layer 2 circuits

IEE802.1ag CC monitoring on active and standby pseudowires

Edge protection using static (Virtual Private Wire Service (VPWS)

Ethernet Layer 2

802.3ah EFM OAM

802.1ag connectivity fault management (CFM)

IEE802.1ag interface-status type, length, and value (TLV)

QoS

12.3X54 –D15

Firewall filters (access control list—ACLs)— family inet

Match Conditions for MPLS Traffic (ACX Series Routers)

Firewall filters—family ccc/any

Policing—per logical interface

Policing—per physical interface

Policing—per family

12.3X54 –D15

Table 4: Protocols and Applications Supported by ACX2200 Routers (continued)

First Supported Junos OS ReleaseProtocol or Application

TrTCM (color aware, color blind)

SrTCM (color aware, color blind)

Host protection

8 queues per port

Priority queuing

Rate control

Scheduling with two different priorities

12.3X54 –D15

Low latency queue (LLQ)

WRED with two levels of DP

Classification—DSCP

Classification—MPLS EXP

Classification—IEEE 802.1p

Rewrite—DSCP

12.3X54 –D15

Table 4: Protocols and Applications Supported by ACX2200 Routers (continued)

First Supported Junos OS ReleaseProtocol or Application

Rewrite MPLS EXP

Rewrite 802.1p

Rewrite MPLS and DSCP to different values

Timing

Timing–1588-v2, 1588-2008–client clock

SyncE

Building-integrated timing supply (BITS)

Clock Sync

12.3X54 –D15

OAM, Troubleshooting, Manageability, Lawful Intercept

Network Time Protocol (NTP)

SNMP

802.1ag CFM

802.3ah EFM

Y.1731 fault and performance management

–Redundant clock (multiple 1588 primary clocks)

12.3X54 –D15

Table 4: Protocols and Applications Supported by ACX2200 Routers (continued)

First Supported Junos OS ReleaseProtocol or Application

MPLS OAM

RMON

Layer 2 traceroute

DNS

TFTP for software downloads

Port mirroring [local port mirroring]

Interface loopback

12.3X54 –D15

Interface byte and packet stats (full, as implemented in Junos OS)

Interface queue stats

Drop packet stats

Distinguish each 802.1ag connection by VLAN-ID

Interface passive-monitor-mode

Security

12.3X54 –D15

–Multipacket mirror

Table 4: Protocols and Applications Supported by ACX2200 Routers (continued)

First Supported Junos OS ReleaseProtocol or Application

TACACS AAA

RADIUS authentication

Control plane DOS prevention

High Availability

MPLS FRR

BFD

ATM Transport

ATM over PWE3

12.3X54 –D15

RFC4717 ATM encapsulation: S6.1 ATM N to one cell mode (required by standard)

RFC4717: S6.3—ATM AAL5 SDU encapsulation (optional)

ATM PWE3 control word

ATM PWE3 by means of dynamic labels

ATM VPI/VCI swapping

ATM idle/unassigned cell suppression

12.3X54 –D15

Table 4: Protocols and Applications Supported by ACX2200 Routers (continued)

First Supported Junos OS ReleaseProtocol or Application

ATM support for N to 1 PW promiscuous mode: 1 PW per port and 1 PW per VPI

Cell concatenation (1 to 30 cells per packet)

Packet/byte counters per VP and VC

ATM IMA

ATM Encapsulation

AAL5 SDU [n-to-1 cell relay]

ATM Queuing

ATM service categories (CBR, nrt-VBR, UBR) to the UNI

12.3X54 –D15

MAP ATM service categories to PW EXP bits

Input policing per VC

VC output shaping

Early packet discard

MIBs

Standard SNMP MIBs

Juniper Networks enterprise-specific MIBs

12.3X54 –D15

+ 144 hidden pages

Juniper ACX2200 Hardware Guide

Specifications and Main Features

Frequently Asked Questions

User Manual

Table of Contents

About the Documentation

Documentation and Release Notes

Using the Examples in This Manual

Merging a Full Example

Merging a Snippet

Documentation Conventions

Documentation Feedback

Requesting Technical Support

Self-Help Online Tools and Resources

Creating a Service Request with JTAC

Overview

ACX2200 System Overview

ACX2200 Universal Metro Router Overview

Benefits of the ACX2200 Router

Chassis Description

ACX2200 Routers Hardware and CLI Terminology Mapping

Packet Flow on ACX Series Routers

Protocols and Applications Supported by the ACX2200 Router