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.
ACX2000 and ACX2100 Universal Metro Router Hardware Guide
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 | 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
ACX2000 and ACX2100 System Overview | 17
ACX2000 and ACX2100 Universal Metro Router Overview | 17
Benefits of the ACX2000 and ACX2100 Routers | 18
ACX2000 Router Description | 18
ACX2100 Router Description | 19
ACX2000 and ACX2100 Routers Hardware and CLI Terminology Mapping | 20
ACX2000 Hardware and CLI Terminology Mapping | 20
ACX2100 Hardware and CLI Terminology Mapping | 22
Packet Flow on ACX Series Routers | 24
Protocols and Applications Supported by ACX Series Routers | 26
ACX2000 Chassis Components | 47
Front Panel of an ACX2000 Router | 47
Front Panel of an ACX2100 Router | 48
Uplink Ports on ACX2000 and ACX2100 Routers | 50
T1/E1 Ports | 51
Gigabit Ethernet RJ-45 Ports | 52
PoE Ports | 52
Gigabit Ethernet SFP Ports | 53
10-Gigabit Ethernet SFP+ Ports | 54
2
ACX2000 and ACX2100 Alarm Contact Port | 54
Clocking Ports on the ACX2000 and the ACX2100 Router | 56
LEDs on ACX2000 and ACX2100 Routers | 57
System LED on the Front Panel | 57
T1/E1 Port LEDs | 58
Ethernet Port LEDs | 58
PoE Port LEDs | 59
SFP and SFP+ Port LEDs | 59
Management and Console Port LEDs on the Front Panel | 60
Cooling System and Airflow in an ACX2000 and ACX2100 Router | 60
ACX2000 Power System | 61
ACX2000 and ACX2100 Power Overview | 62
iv
ACX2100 AC Power Specifications | 62
ACX2100 AC Power Cord Specifications | 63
ACX2000 and ACX2100 DC Power Specifications | 65
Site Planning, Preparation, and Specifications
Site Preparation Checklist for ACX2000 and ACX2100 Routers | 68
ACX2000 and ACX2100 Site Guidelines and Requirements | 69
General Site Guidelines | 70
Site Electrical Wiring Guidelines | 70
Clearance Requirements for Airflow and Hardware Maintenance on ACX2000 and ACX2100
Routers | 71
Chassis Physical Specifications for ACX2000 and ACX2100 Routers | 72
ACX2000 and ACX2100 Router Environmental Specifications | 73
ACX2000 and ACX2100 Chassis Grounding Cable and Lug Specifications | 74
Grounding Points Specifications | 74
Grounding Cable Lug Specifications | 75
Grounding Cable Specifications | 76
Cabinet Requirements for ACX2000 and ACX2100 Routers | 76
Rack Requirements for ACX2000 and ACX2100 Routers | 78
3
ACX2000 and ACX2100 Network Cable and Transceiver Planning | 80
Determining Transceiver Support and Specifications | 80
Calculating Power Budget and Power Margin for Fiber-Optic Cables | 81
How to Calculate Power Budget for Fiber-Optic Cable | 81
How to Calculate Power Margin for Fiber-Optic Cable | 82
Fiber-Optic Cable Signal Loss, Attenuation, and Dispersion | 83
Signal Loss in Multimode and Single-Mode Fiber-Optic Cable | 83
Attenuation and Dispersion in Fiber-Optic Cable | 84
ACX2000 and ACX2100 Alarm, Management, and Clocking Cable Specifications and
Pinouts | 85
Alarm Contact Port Pinouts on the ACX2000 and ACX2100 Router | 85
Management Port Connector Pinout Information for ACX Series Routers | 87
v
Console or Auxiliary Port Connector Pinout on ACX Series Routers | 88
USB Port Specifications for an ACX Series Router | 89
Clocking Ports Specifications on the ACX2000 and the ACX2100 Router | 89
External Clocking Port Connector Specifications | 90
External Clocking Input Port Specifications | 90
Initial Installation and Configuration
Installing and Connecting an ACX2000 or ACX2100 Router Overview | 93
Unpacking and Mounting the ACX2000 and ACX2100 Routers | 94
Unpacking an ACX2000 or ACX2100 Router | 94
Parts Inventory (Packing List) for an ACX2000 and ACX2100 Router | 95
Installing the ACX2000 or ACX2100 Mounting Brackets | 96
Installing the ACX2000 or ACX2100 Router in the Rack | 97
Connecting the ACX2000 and ACX2100 Routers to Power | 99
Connecting the ACX2000 or ACX2100 Router to Earth Ground | 100
Connecting DC Power Cables to the ACX2000 or ACX2100 Router | 102
Connecting AC Power Cords to the ACX2100 Router | 104
Connecting the ACX2000 and ACX2100 to External Devices | 105
4
5
Connecting ACX2000 or ACX2100 Routers to Management Devices | 106
Connecting the Router to a Network for Out-of-Band Management | 106
Connecting the Router to a Management Console or Auxiliary Device | 107
Connecting ACX2000 or ACX2100 Routers to External Clocking Devices | 108
Connecting 1-PPS and 10-MHz Timing Devices to the Router | 108
Connecting a T1 or E1 External Clocking Device to the Router | 109
Connecting ACX2000 or ACX2100 Routers to an External Alarm-Reporting Device | 110
Initially Configuring the ACX2000 or ACX2100 Router | 111
Maintaining Components
Maintaining ACX2000 and ACX2100 Components | 117
Routine Maintenance Procedures for the ACX2000 and ACX2100 Router | 117
vi
Maintaining Cables That Connect to ACX2000 or ACX2100 Network Ports | 117
Maintaining the ACX2000 and ACX2100 Uplink Ports | 118
Removing a Transceiver from the ACX2000 or ACX2100 | 119
Installing a Transceiver in the ACX2000 or ACX2100 | 121
Replacing an ACX2000 or ACX2100 Management Ethernet Cable | 122
Removing an ACX2000 or ACX2100 Management Ethernet Cable | 122
Installing an ACX2000 and ACX2100 Management Ethernet Cable | 123
Replacing an ACX2000 or ACX2100 Console or Auxiliary Cable | 123
Removing an ACX2000 or ACX2100 Console or Auxiliary Cable | 123
Installing an ACX2000 or ACX2100 Console or Auxiliary Cable | 124
Troubleshooting Hardware
Troubleshooting ACX2000 and ACX2100 | 126
Troubleshooting Resources for ACX2000 and ACX2100 Routers | 126
Command-Line Interface | 126
Front Panel LEDs | 126
Monitoring System Log Messages | 127
Alarm Types and Severity Classes on ACX Series Routers | 127
Alarm Types | 128
Alarm Severity Classes | 128
Verifying Active Alarms | 128
Contacting Customer Support and Returning the Chassis or Components
6
7
Contacting Customer Support and Returning the Chassis or Components | 131
How to Return a Hardware Component to Juniper Networks, Inc. | 131
Locating the Serial Number on a ACX2000 or ACX2100 Chassis or Component | 132
ACX2000 and ACX2100 Chassis Serial Number Label | 133
Guidelines for Packing Hardware Components for Shipment | 133
Packing the ACX Series Router for Shipment | 134
Safety and Compliance Information
General Safety Guidelines and Warnings | 137
Definitions of Safety Warning Levels | 138
Qualified Personnel Warning | 141
vii
Warning Statement for Norway and Sweden | 142
Installation Instructions Warning | 142
Chassis and Component Lifting Guidelines | 143
Restricted Access Warning | 144
Ramp Warning | 146
Rack-Mounting and Cabinet-Mounting Warnings | 147
Grounded Equipment Warning | 153
Radiation from Open Port Apertures Warning | 154
Laser and LED Safety Guidelines and Warnings | 155
General Laser Safety Guidelines | 155
Class 1 Laser Product Warning | 156
Class 1 LED Product Warning | 157
Laser Beam Warning | 158
Maintenance and Operational Safety Guidelines and Warnings | 158
Battery Handling Warning | 160
Jewelry Removal Warning | 161
Lightning Activity Warning | 163
Operating Temperature Warning | 164
Product Disposal Warning | 166
General Electrical Safety Guidelines and Warnings | 167
Action to Take After an Electrical Accident | 168
Prevention of Electrostatic Discharge Damage | 168
ACX2100 AC Power Electrical Safety Guidelines | 170
AC Power Disconnection Warning | 171
ACX2000 and ACX2100 DC Power Electrical Safety Guidelines | 172
DC Power Copper Conductors Warning | 173
DC Power Disconnection Warning | 174
viii
DC Power Grounding Requirements and Warning | 176
DC Power Wiring Sequence Warning | 178
DC Power Wiring Terminations Warning | 181
Midplane Energy Hazard Warning | 183
Multiple Power Supplies Disconnection Warning | 184
TN Power Warning | 185
Agency Approvals for ACX2000 and ACX2100 Routers | 185
Compliance Statements for NEBS for ACX2000 and ACX2100 Routers | 187
Compliance Statements for EMC Requirements for ACX2000 and ACX2100 Routers | 188
Canada | 188
European Community | 188
Israel | 188
Japan | 189
United States | 189
Compliance Statements for Environmental Requirements | 190
Compliance Statements for Acoustic Noise for ACX2000 and ACX2100 Routers | 190
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 ACX2000 and ACX2100 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.
ix
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;
}
}
}
}
x
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]
xi
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.
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:
Cooling System and Airflow in an ACX2000 and ACX2100 Router | 60
ACX2000 Power System | 61
ACX2000 and ACX2100 System Overview
IN THIS SECTION
ACX2000 and ACX2100 Universal Metro Router Overview | 17
ACX2000 and ACX2100 Routers Hardware and CLI Terminology Mapping | 20
Packet Flow on ACX Series Routers | 24
Protocols and Applications Supported by ACX Series Routers | 26
ACX2000 and ACX2100 Universal Metro Router Overview
17
IN THIS SECTION
Benefits of the ACX2000 and ACX2100 Routers | 18
ACX2000 Router Description | 18
ACX2100 Router Description | 19
The ACX2000 and ACX2100 Universal Metro Routers are 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.
The ACX Series router is a single-board router with a built-in Routing Engine and one Packet Forwarding
Engine. 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 compact routers are one rack unit (U; that is, 1.75 in., or 4.45 cm) tall. Several routers can be stacked
in a single floor-to-ceiling rack for increased port density per unit of floor space.
The chassis is a rigid sheet metal structure that houses all the other router components. 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 300-mm deep (or larger) enclosed cabinets, 19-in. equipment
racks, or telco open-frame racks.
18
Benefits of the ACX2000 and ACX2100 Routers
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.
ACX2000 Router Description
The ACX2000 router contains sixteen T1/E1 ports, six Gigabit Ethernet ports, and two PoE ports. The
ACX2000 router also supports installation of two Gigabit Ethernet SFP transceivers and two 10-Gigabit
Ethernet SFP+ transceivers.
The ACX2000 router has one “pseudo” Flexible PIC Concentrator (FPC 0), and four “pseudo” PICs (PIC 0
through 3).
Figure 1 on page 19 shows the front view of the ACX2000 router. Figure 2 on page 19 shows the rear
view.
Figure 1: Front View of the ACX2000 Router
g006402
ACX2000
0/0/12
0/0/13
0/0/14
0/0/4
0/0/5
0/0/6
0/0/7
0/0/15
0/0/8
0/0/9
0/0/10
0/0/11
0/1/0
0/1/1
0/1/2
0/1/3POE
0/1/4
0/1/5
0/1/6
0/1/7POE
EXTREFCLKIN
GE
GE
XE
g006403
g017844
g006403
Figure 2: Rear View of the ACX2000 Router
ACX2100 Router Description
The ACX2100 router contains sixteen T1/E1 ports, and four Gigabit Ethernet ports. The ACX2100 router
also contains two ports for installing Gigabit Ethernet SFP transceivers and two ports for installing 10-Gigabit
Ethernet SFP+ transceivers. The ports labeled COMBO PORTS provide an additional four copper Gigabit
Ethernet ports or four Gigabit Ethernet SFP ports. You can use only one set of combination ports at a time.
19
The ACX2100 router has two “pseudo” Flexible PIC Concentrators (FPC 0 and FPC 1), and four “pseudo”
PICs (PIC 0 through 3).
Figure 3 on page 19 shows the front view of the ACX2100 router. Figure 4 on page 19 shows the rear
view.
Figure 3: Front View of the ACX2100 Router
Figure 4: Rear View of the ACX2100 Router
SEE ALSO
Front Panel of an ACX2000 Router | 47
Front Panel of an ACX2100 Router | 48
ACX2000 and ACX2100 Routers Hardware and CLI Terminology Mapping
IN THIS SECTION
ACX2000 Hardware and CLI Terminology Mapping | 20
ACX2100 Hardware and CLI Terminology Mapping | 22
20
ACX2000 Hardware and CLI Terminology Mapping
Table 3 on page 20 describes the hardware terms used in ACX2000 router documentation and the
corresponding terms used in the Junos OS command line interface (CLI). Figure 5 on page 22 shows the
port locations of the interfaces.
Table 3: CLI Equivalents of Terms Used in Documentation for ACX2000 Routers
Hardware
Item (as
displayed
in the CLI)
FPC (n)
Description (as
displayed in the
CLI)
Abbreviated name of
the Flexible PIC
Concentrator (FPC)
Value (as
displayed in
the CLI)
Value of n is
always 0.
Router chassis–ACX2000Chassis
The router does not have
actual FPCs. In this case,
FPC refers to the router
itself.
Additional InformationItemin Documentation
“Chassis Physical Specifications
for ACX2000 and ACX2100
Routers” on page 72
Interface Naming Conventions
Used in the Junos OS Operational
Commands
Table 3: CLI Equivalents of Terms Used in Documentation for ACX2000 Routers (continued)
Hardware
Item (as
displayed
in the CLI)
Description (as
displayed in the
CLI)
Value (as
displayed in
the CLI)
Additional InformationItemin Documentation
21
PIC (n)
Abbreviated name of
the Physical Interface
Card (PIC)
6x 1GE (RJ-45)
•
2x 1GE (POE
•
RJ-45)
n is a value in
the range of
0–3.
PIC 016x T1/E1 (RJ-48)
PIC 1One of the following:
PIC 22x 1GE (SFP)
PIC 32x 10GE (SFP+)
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 network ports on
the front panel of the
router
Built-in network ports on
the front panel of the
router
Built-in uplink ports on
the front panel of the
router
Built-in uplink ports on
the front panel of the
router
Interface Naming Conventions
Used in the Junos OS Operational
Commands
“ACX2000 and ACX2100
Universal Metro Router
Overview” on page 17
“ACX2000 and ACX2100
Universal Metro Router
Overview” on page 17
“ACX2000 and ACX2100
Universal Metro Router
Overview” on page 17
“ACX2000 and ACX2100
Universal Metro Router
Overview” on page 17
Xcvr (n)
supply (n)
Abbreviated name of
the transceiver
Built-in power supplyPower
equivalent to
the number of
the port in
which the
transceiver is
installed.
always 0.
Optical transceiversn is a value
DC power supplyValue of n is
“Uplink Ports on ACX2000 and
ACX2100 Routers” on page 50
“ACX2000 and ACX2100 Power
Overview” on page 62
Table 3: CLI Equivalents of Terms Used in Documentation for ACX2000 Routers (continued)
ACX2000
MGMT
SYS01
CONSOLE/AUX
ALARM
1PPS
10MHz
INOUT
INOUT
T1/E1
0/0/4
0/0/12
0/0/5
0/0/13
0/0/6
0/0/14
0/0/7
0/0/15
0/0/0
0/0/8
0/0/1
0/0/9
0/0/2
0/0/10
0/0/3
0/0/11
0/1/0
0/1/4
0/1/1
0/1/5
0/1/2
0/1/6
0/1/3POE
0/1/7POE
GE
0/2/0
0/2/10/3/00/3/1
g006414
EXTREFCLKIN
GE
XE
FPC0,PIC2GE0/2/0-0/2/1
FPC0,PIC0T1/E10/0/0-0/0/15
FPC0,PIC1GE0/1/0-0/1/7
FPC0,PIC3XE0/3/0-0/3/1
Hardware
Item (as
displayed
in the CLI)
Description (as
displayed in the
CLI)
Value (as
displayed in
the CLI)
Additional InformationItemin Documentation
22
Fan
Fan–Fan
“Cooling System and Airflow in
an ACX2000 and ACX2100
NOTE: ACX2000
Router” on page 60
routers are fanless
models.
Figure 5: ACX2000 Interface Port Mapping
ACX2100 Hardware and CLI Terminology Mapping
Table 4 on page 22 describes the hardware terms used in ACX2100 router documentation and the
corresponding terms used in the Junos OS command line interface (CLI). Figure 6 on page 24 shows the
port locations of the interfaces.
Table 4: CLI Equivalents of Terms Used in Documentation for ACX2100 Routers
Hardware
Value (as
displayed in the
CLI)
n is a value in the
range of 0–1.
Router chassis–ACX2100Chassis
The router does not have
actual FPCs. In this case,
FPC refers to the router
itself.
Item (as
displayed
in the CLI)
FPC (n)
Description (as
displayed in the
CLI)
Abbreviated name of
the Flexible PIC
Concentrator (FPC)
Additional InformationItemin Documentation
“Chassis Physical Specifications
for ACX2000 and ACX2100
Routers” on page 72
Interface Naming Conventions
Used in the Junos OS Operational
Commands
Table 4: CLI Equivalents of Terms Used in Documentation for ACX2100 Routers (continued)
Hardware
Item (as
displayed
in the CLI)
Description (as
displayed in the
CLI)
Value (as
displayed in the
CLI)
Additional InformationItemin Documentation
23
PIC (n)
Abbreviated name of
the Physical
Interface Card (PIC)
4x 1GE (RJ-45)
•
4x 1GE (SFP)
•
n is a value in the
range of 0–3.
PIC 0 on FPC 016x T1/E1 (RJ-48)
PIC 0 on FPC 14x 1GE (RJ-45)
PIC 1 on FPC 1One of the following:
PIC 2 on FPC 12x 1GE (SFP)
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 network ports on
the front panel of the
router
Built-in network ports on
the front panel of the
router
Built-in uplink ports on
the front panel of the
router
Built-in uplink ports on
the front panel of the
router
Interface Naming Conventions
Used in the Junos OS Operational
Commands
“ACX2000 and ACX2100
Universal Metro Router
Overview” on page 17
“ACX2000 and ACX2100
Universal Metro Router
Overview” on page 17
“ACX2000 and ACX2100
Universal Metro Router
Overview” on page 17
“ACX2000 and ACX2100
Universal Metro Router
Overview” on page 17
Xcvr (n)
Power
supply (n)
Abbreviated name of
the transceiver
Built-in power
supply
PIC 3 on FPC 12x 10GE (SFP+)
equivalent to the
number of the
port in which the
transceiver is
installed.
always 0.
Built-in uplink ports on
the front panel of the
router
Optical transceiversn is a value
AC or DC power supplyValue of n is
“ACX2000 and ACX2100
Universal Metro Router
Overview” on page 17
“Uplink Ports on ACX2000 and
ACX2100 Routers” on page 50
“ACX2000 and ACX2100 Power
Overview” on page 62
Table 4: CLI Equivalents of Terms Used in Documentation for ACX2100 Routers (continued)
“Cooling System and Airflow in
an ACX2000 and ACX2100
NOTE: ACX2100
Router” on page 60
routers are fanless
models.
Figure 6: ACX2100 Interface Port Mapping
Packet Flow on ACX Series Routers
The class-of-service (CoS) architecture for ACX Series routers is in concept similar to that for MX Series
routers. The general architecture for ACX Series routers is shown in Figure 7 on page 24.
Figure 7: ACX Series Router Packet Forwarding and Data Flow
Based on the model, ACX Series 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
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 8 on page 25. 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.
25
Figure 8: ACX Series Router Packet Handling
SEE ALSO
ACX2000 and ACX2100 Routers Hardware and CLI Terminology Mapping | 20
Configuring CoS on ACX Series Routers
Protocols and Applications Supported by ACX Series Routers
Table 5 on page 26 contains the first Junos OS Release support for protocols and applications on ACX
Series 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.
The ACX Series routers does not support per-family maximum transmission unit (MTU)
•
configuration. The MTU applied to family inet gets applied to other families as well, even
though it can be configured though CLI and visible in show interface extensive output. The
only way to use higher MTU for a family is to manipulate the MTU, apply at interface or familyinet levels, and let it calculate for each family automatically. MTU values are not limited to
1500 but can range between 256 to 9216.
For more information, see the Knowledge Base (KB) article KB28179 at: