Juniper ACX500 User Manual
ACX500 Universal Metro Router Hardware
Published
2020-11-10
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.
ACX500 Universal Metro Router Hardware Guide
Copyright © 2020 Juniper Networks, Inc. All rights reserved.
The information in this document is current as of the date on the title page.
ii
YEAR 2000 NOTICE
Juniper Networks hardware and software products are Year 2000 compliant. Junos OS has no known time-related
limitations through the year 2038. However, the NTP application is known to have some difficulty in the year 2036.
END USER LICENSE AGREEMENT
The Juniper Networks product that is the subject of this technical documentation consists of (or is intended for use with)
Juniper Networks software. Use of such software is subject to the terms and conditions of the End User License Agreement
(“EULA”) posted at https://support.juniper.net/support/eula/. By downloading, installing or using such software, you
agree to the terms and conditions of that EULA.
Table of Contents
1
About the Documentation | xi
Documentation and Release Notes | xi
Using the Examples in This Manual | xi
Merging a Full Example | xii
Merging a Snippet | xiii
Documentation Conventions | xiii
Documentation Feedback | xvi
Requesting Technical Support | xvi
Self-Help Online Tools and Resources | xvii
Creating a Service Request with JTAC | xvii
iii
Overview
ACX500 System Overview | 19
ACX500 Universal Metro Router Overview | 19
Benefits of the ACX500 Router | 21
ACX500 Routers Hardware and CLI Terminology Mapping | 22
ACX500 Indoor Routers Hardware and CLI Terminology Mapping | 22
ACX500 Outdoor Routers Hardware and CLI Terminology Mapping | 24
ACX500 Outdoor Routers with PoE Hardware and CLI Terminology Mapping | 26
Packet Flow on ACX Series Routers | 28
Protocols and Applications Supported by ACX Series Routers | 29
ACX500 Chassis | 51
ACX500 Indoor Router Description | 51
ACX500 Outdoor Router Description | 52
ACX500 Outdoor Router with PoE Description | 54
Front Panel of an ACX500 Indoor Router | 55
Front Panel of an ACX500 Outdoor Router with PoE | 57
Alarm Contact Port on ACX500 Routers | 59
2
LEDs on ACX500 Routers | 61
System LED on the Front Panel | 61
Gigabit Ethernet SFP and RJ-45 Port LEDs | 62
Management Port LEDs on the Front Panel | 62
GPS 1 PPS LED on the Front Panel | 63
Uplink Ports on ACX500 Routers | 63
Gigabit Ethernet RJ-45 Ports | 64
Gigabit Ethernet SFP Ports | 64
PoE Ports | 65
Clocking Ports on ACX500 Routers | 66
Cooling System and Airflow in ACX500 Routers | 67
ACX500 Power System | 68
iv
ACX500 Power Overview | 68
ACX500 AC Power Specifications | 69
ACX500 Router AC Power Cord Specifications | 70
ACX500 DC Power Specifications | 72
Site Planning, Preparation, and Specifications
Site Preparation Checklist for ACX500 Routers | 75
ACX500 Site Guidelines and Requirements | 76
General Site Guidelines | 77
Site Electrical Wiring Guidelines | 77
Clearance Requirements for Airflow and Hardware Maintenance on ACX500 Routers | 78
ACX500 Indoor Router Chassis Dimensions and Clearance Requirements | 79
ACX500 Outdoor Router Chassis Dimensions and Clearance Requirements | 80
ACX500 Outdoor Router with PoE Chassis Dimensions and Clearance Requirements | 82
Chassis Physical Specifications for ACX500 Routers | 84
ACX500 Router Environmental Specifications | 86
ACX500 Router Grounding Specifications | 88
Grounding Points Specifications | 88
Grounding Cable Lug Specifications | 89
Grounding Cable Specifications | 90
ACX500 Mounting Requirements | 90
Cabinet Requirements for ACX500 Indoor Routers | 91
Wall Requirements for ACX500 Outdoor Routers | 93
Pole Requirements for ACX500 Outdoor Routers | 93
Rack Requirements for ACX500 Indoor Routers | 94
ACX500 Alarm and Management Cable Specifications and Pinouts | 95
Alarm Contact Port Pinouts for ACX500 Routers | 95
Console Port Connector Pinout on ACX500 Routers | 97
Management Port Connector Pinout Information for ACX500 Routers | 98
USB Port Specifications for ACX500 Routers | 99
External Clocking Ports Specifications on ACX500 Routers | 100
ToD RS-422 and 1 PPS RS-422 Port Connector Pinout on ACX500 Routers | 100
v
ACX500 Timing Server Specifications | 101
Requirements and Specifications for Installing a GNSS Antenna | 101
Requirements for Installing a GNSS Antenna | 102
ACX500 Router GNSS Antenna Signal Gain Requirements | 102
General ACX500 GNSS Antenna Mounting and Installation Recommendations | 103
Tools and Parts Required to Install the GNSS Antenna | 106
Installing the ACX500 GNSS Antenna | 107
ACX500 GNSS Antenna Power Specification | 108
ACX500 GNSS Antenna Surge Protection | 109
Antenna Installation Verification | 109
Requirements and Specifications for the Recommended GNSS Antenna | 110
Antenna Selection Guidelines | 110
Recommended GNSS Antenna Specifications | 110
Initial Installation and Configuration
3
ACX500 Installation Overview | 115
Installing and Connecting an ACX500 Indoor Router Overview | 115
Installing and Connecting an ACX500 Outdoor Router Overview | 116
Unpacking the ACX500 | 117
Unpacking the ACX500 Router | 117
Parts Inventory (Packing List) for ACX500 Routers | 118
Installing the ACX500 Router | 121
Installing the ACX500 Indoor Router in a Rack | 121
Mounting the ACX500 Outdoor Router on a Wall | 124
Mounting the ACX500 Outdoor Router on a Pole | 129
Weatherproofing the ACX500 Outdoor Router | 135
vi
Weatherproofing Overview | 135
Accessing and Weatherproofing the Interface Ports | 136
Accessing and Weatherproofing the Management Ports | 147
Connecting the ACX500 Router to Earth Ground | 149
Connecting the ACX500 to Power | 152
Connecting an AC Power Cord to the ACX500 Indoor Router | 153
Connecting DC Power Cables to the ACX500 Indoor Router | 154
Connecting an AC Power Cord to the ACX500 Outdoor Router | 157
Connecting a DC Power Cord to the ACX500 Outdoor Router | 162
Connecting the ACX500 to External Devices | 165
Connecting ACX500 Routers to Management Devices | 166
Connecting the Router to a Network for Out-of-Band Management | 166
Connecting the Router to a Management Console | 167
Connecting the ACX500 Router to an External Alarm-Reporting Device | 168
Connecting the ACX500 Router to External Clocking Devices | 169
Connecting 1 PPS Timing Devices to the Router | 170
Configuring Junos OS on the ACX500 Router | 170
Removing, Installing, and Maintaining Components
4
5
Maintaining ACX500 Components | 176
Routine Maintenance Procedures for the ACX500 Router | 176
Maintaining Cables That Connect to ACX500 Network Ports | 176
Maintaining the ACX500 Uplink Ports | 177
Replacing ACX500 Components | 178
Replacing a Console Cable | 178
Removing a Console Cable | 179
Installing a Console Cable | 179
Replacing a Management Ethernet Cable | 180
Removing a Management Ethernet Cable | 180
Installing a Management Ethernet Cable | 180
Replacing a Fiber-Optic Cable | 181
vii
Disconnecting a Fiber-Optic Cable | 181
Connecting a Fiber-Optic Cable | 182
Replacing an SFP Transceiver | 183
Removing an SFP Transceiver | 184
Installing an SFP Transceiver | 185
Troubleshooting Hardware
Troubleshooting ACX500 Components | 188
Troubleshooting Resources for ACX500 Routers | 188
Command-Line Interface | 188
Front Panel LEDs | 188
Monitoring System Log Messages | 189
Alarm Types and Severity Classes on ACX Series Routers | 189
Alarm Types | 190
Alarm Severity Classes | 190
Verifying Active Alarms | 190
Contacting Customer Support and Returning the Chassis or Components
6
7
Contacting Customer Support and Returning the Chassis or Components | 193
Contacting Customer Support | 193
Displaying ACX500 Components and Serial Numbers | 194
ACX500 Chassis Serial Number Label | 195
How to Return a Hardware Component to Juniper Networks, Inc. | 196
Packing the ACX Series Router for Shipment | 197
Guidelines for Packing Hardware Components for Shipment | 198
Safety and Compliance Information
General Safety Guidelines and Warnings | 201
Definitions of Safety Warning Levels | 202
Qualified Personnel Warning | 205
viii
Warning Statement for Norway and Sweden | 206
Fire Safety Requirements | 206
Fire Suppression | 206
Fire Suppression Equipment | 206
Installation Instructions Warning | 208
Chassis and Component Lifting Guidelines | 208
Restricted Access Warning | 210
Ramp Warning | 212
Rack-Mounting and Cabinet-Mounting Warnings | 213
Grounded Equipment Warning | 219
Radiation from Open Port Apertures Warning | 220
Laser and LED Safety Guidelines and Warnings | 221
General Laser Safety Guidelines | 221
Class 1 Laser Product Warning | 222
Class 1 LED Product Warning | 223
Laser Beam Warning | 224
Maintenance and Operational Safety Guidelines and Warnings | 224
Battery Handling Warning | 226
Jewelry Removal Warning | 227
Lightning Activity Warning | 229
Operating Temperature Warning | 230
Product Disposal Warning | 232
General Electrical Safety Guidelines and Warnings | 233
Action to Take After an Electrical Accident | 234
Prevention of Electrostatic Discharge Damage | 234
ACX500 AC Power Electrical Safety Guidelines | 236
ix
AC Power Disconnection Warning | 237
ACX500 DC Power Electrical Safety Guidelines | 238
DC Power Copper Conductors Warning | 239
DC Power Disconnection Warning | 240
DC Power Grounding Requirements and Warning | 242
DC Power Wiring Sequence Warning | 244
DC Power Wiring Terminations Warning | 247
Midplane Energy Hazard Warning | 249
Multiple Power Supplies Disconnection Warning | 250
TN Power Warning | 251
Agency Approvals and Compliance Statements | 251
Agency Approvals for ACX500 Routers | 252
Compliance Statements for NEBS for ACX500 Routers | 255
Compliance Statements for EMC Requirements for ACX500 Routers | 256
ACX500 Indoor Routers | 256
ACX500 Outdoor Routers | 257
Compliance Statements for Environmental Requirements | 258
Compliance Statements for Acoustic Noise for ACX500 Routers | 258
x
About the Documentation
IN THIS SECTION
Documentation and Release Notes | xi
Using the Examples in This Manual | xi
Documentation Conventions | xiii
Documentation Feedback | xvi
Requesting Technical Support | xvi
Use this guide to install hardware and perform initial software configuration, routine maintenance, and
troubleshooting for the ACX500 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.
xi
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;
}
}
}
}
xii
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]
xiii
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 xiv defines notice icons used in this guide.
Table 1: Notice Icons
xiv
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 xiv 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)
xv
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)
xvi
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/
•
xvii
Find product documentation: https://www.juniper.net/documentation/
•
Find solutions and answer questions using our Knowledge Base: https://kb.juniper.net/
•
Download the latest versions of software and review release notes:
•
https://www.juniper.net/customers/csc/software/
Search technical bulletins for relevant hardware and software notifications:
•
https://kb.juniper.net/InfoCenter/
Join and participate in the Juniper Networks Community Forum:
•
https://www.juniper.net/company/communities/
Create a service request online: https://myjuniper.juniper.net
•
To verify service entitlement by product serial number, use our Serial Number Entitlement (SNE) Tool:
https://entitlementsearch.juniper.net/entitlementsearch/
Creating a Service Request with JTAC
You can create a service request with JTAC on the Web or by telephone.
Visit https://myjuniper.juniper.net.
•
Call 1-888-314-JTAC (1-888-314-5822 toll-free in the USA, Canada, and Mexico).
•
For international or direct-dial options in countries without toll-free numbers, see
https://support.juniper.net/support/requesting-support/.
1
CHAPTER
Overview
ACX500 System Overview | 19
ACX500 Chassis | 51
Cooling System and Airflow in ACX500 Routers | 67
ACX500 Power System | 68
ACX500 System Overview
IN THIS SECTION
ACX500 Universal Metro Router Overview | 19
ACX500 Routers Hardware and CLI Terminology Mapping | 22
Packet Flow on ACX Series Routers | 28
Protocols and Applications Supported by ACX Series Routers | 29
ACX500 Universal Metro Router Overview
19
IN THIS SECTION
Benefits of the ACX500 Router | 21
Juniper Networks ACX500 Universal Metro Routers are principally designed to provide superior
management for rapid provisioning to the access network. The ACX500 routers support rich Gigabit
Ethernet capabilities for uplink, along with support for Gigabit Ethernet interfaces, 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 routers have a built-in Routing Engine and one Packet Forwarding Engine. The Packet Forwarding
Engine has one “pseudo” Flexible PIC Concentrator (FPC 0). Because there is no switching fabric, the single
Packet Forwarding Engine takes care of 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 Juniper Networks ACX Series Universal MetroRouters are powered by the Junos operating system
(Junos OS), which supports extensive Layer 2 and Layer 3 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 enables 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, an ACX Series router at the cell site and an 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.
20
The ACX500 routers can be installed indoors as well as outdoors:
ACX500 indoor—The compact ACX500 indoor 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 of the ACX500 indoor router 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.
ACX500 outdoor—The compact ACX500 outdoor routers are environmental hardened, and can be
•
deployed in an outdoor environment, such as on walls and poles. The chassis of the ACX500 indoor
router measures 1.75 in. (4.45 cm) high, 9.4 in. (24 cm) deep, and 17.5 in. (44.5 cm) wide. The chassis of
the ACX500 outdoor router with the Power over Ethernet (PoE) unit measures 16 in. (40.64 cm) high,
4.7 in. (11.93 cm) deep, and 10 in. (25.4 cm) wide. You need to purchase the pole-mounting kit or the
wall-mounting kit from Juniper Networks to mount the router in an outdoor environment.
Benefits of the ACX500 Router
21
Zero Touch Provisioning (ZTP)—ZTP enables quick deployment of a large number of ACX 500 routers.
•
As the ACX500 supports ZTP, it can be production-ready with little or no manual intervention. As
installation and provisioning is faster, overall operational efficiency is improved, and the MPLS deployment
in the access layer is simplified.
Integrated high-precision timing (Synchronous Ethernet and Precision Time Protocol)— You can use
•
the ACX500 routers for Synchronous Ethernet and PTP in a hybrid mode for the highest level of frequency
(10 ppb) and phase (<500 nS) accuracy required for LTE-A. The ACX500, ACX500-O, and ACX500-O-PoE
routers also provide an integrated GPS receiver and can act as a grandmaster (GM) clock for a distributed
PTP implementation, used for the aggregation of small cell traffic when the backhaul is transported over
the Internet.
Advanced security services— ACX500 routers support IPsec, Media Access Control Security (MACsec),
•
Network Address Translation (NAT), and Trusted Platform Module (TPM) features to protect against
potential vulnerabilities to the network as well as subscriber traffic.
Environmentally hardened design—ACX500 routers are temperature hardened and support passive
•
cooling for outdoor deployments in extreme weather conditions. The ACX500-O and ACX500-O-PoE
routers are based on environmentally hardened, ruggedized chassis and are IP65-compliant for outdoor
deployments (pole mount or stand mount) with no need for an enclosure or cabinet.
High availability and reliability— Junos Continuity on ACX500 eliminates OS upgrades and system
•
reboots when new hardware is added to ACX500 routers. A plug-in package provides the drivers and
support files needed to bring the hardware online.
Unified in-service software upgrade (unified ISSU), provides software upgrades between two different
Junos OS releases (major or minor) without disrupting network traffic.
ACX500 Routers Hardware and CLI Terminology Mapping
IN THIS SECTION
ACX500 Indoor Routers Hardware and CLI Terminology Mapping | 22
ACX500 Outdoor Routers Hardware and CLI Terminology Mapping | 24
ACX500 Outdoor Routers with PoE Hardware and CLI Terminology Mapping | 26
ACX500 Indoor Routers Hardware and CLI Terminology Mapping
Table 3 on page 22 describes the hardware terms used in ACX500 indoor router documentation and the
corresponding terms used in the Junos OS CLI. Figure 1 on page 24 shows the port locations of the
interfaces.
22
Table 3: CLI Equivalents of Terms Used in Documentation for ACX500 Indoor 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.
Item in
Documentation
Router chassis–ACX500Chassis
The router does not
have actual FPCs. In
this case, FPC refers to
the router itself.
Additional Information
“Chassis Physical
Specifications for ACX500
Routers” on page 84
Interface Naming
Conventions Used in the
Junos OS Operational
Commands
Table 3: CLI Equivalents of Terms Used in Documentation for ACX500 Indoor Routers (continued)
Hardware
Item (as
Displayed
in the CLI)
Description (as
Displayed in the CLI)
Value (as Displayed
in the CLI)
Item in
Documentation
Additional Information
23
PIC (n)
Xcvr (n)
Abbreviated name of
the Physical Interface
Card (PIC)
(COMBO PIC):
4x 1GE (RJ-45 with
•
PoE+ support)
4x 1GE (SFP)
•
Abbreviated name of
the transceiver
n is a value in the
range of 0–1.
PIC 02x 1GE (SFP)
PIC 1One of the following
equivalent to the
number of the port in
which the transceiver
is installed.
The router does not
have actual PIC
devices; see entries for
PIC 0 through PIC 1
for the equivalent item
on the router.
Built-in uplink ports on
the front panel of the
router
Built-in uplink ports on
the front panel of the
router
Optical transceiversn is a value
Interface Naming
Conventions Used in the
Junos OS Operational
Commands
“ACX500 Universal Metro
Router Overview” on
page 19
“ACX500 Universal Metro
Router Overview” on
page 19
“Uplink Ports on ACX500
Routers” on page 63
supply (n)
Fan
Xcvr (n)
Built-in power supplyPower
Fan
NOTE: ACX500routers
are fanless models.
Abbreviated name of
the transceiver
0.
“ACX500 Universal
Metro Router
Overview” on
page 19
equivalent to the
number of the port in
which the transceiver
is installed.
DC power supplyValue of n is always
Optical transceiversn is a value
“ACX500 Power Overview”
on page 68
“Uplink Ports on ACX500
Routers” on page 63
Table 3: CLI Equivalents of Terms Used in Documentation for ACX500 Indoor Routers (continued)
ACX500-DC
0/1/30/1/0 PoE++ 0/1/1 PoE+ 0/1/2 PoE+
0/1/30/1/20/1/10/1/00/0/10/0/0
GE
COMBO
POWER
1 2
SYS
MGMT TOD CONSOLE
GPS1PPS
GPSANTENNA
IN
OUT ALARM
g000699
1 2 3
Hardware
Item (as
Displayed
in the CLI)
Description (as
Displayed in the CLI)
Value (as Displayed
in the CLI)
Item in
Documentation
Additional Information
24
DC power supplyValue of n is always
Fan–Fan
supply (n)
Fan
Built-in power supplyPower
0.
NOTE: ACX500routers
are fanless.
Figure 1: ACX500 Indoor Router Interface Port Mapping—DC and AC Chassis
“ACX500 Power Overview”
on page 68
“Cooling System and
Airflow in ACX500
Routers” on page 67
FPC 0, PIC 0: 0/0/0–0/0/1 (2x1GE SFP)
3—1— FPC 0, PIC 1: 0/1/0 PoE++, 0/1/1 PoE+, 0/1/2 PoE+,
and 0/1/3 (4x1GE RJ-45)
2—FPC 0, PIC 1: 0/1/0–0/1/3 (4x1GE SFP)
ACX500 Outdoor Routers Hardware and CLI Terminology Mapping
Table 4 on page 25 describes the hardware terms used in ACX500 outdoor router documentation and the
corresponding terms used in the Junos OS CLI. Figure 2 on page 26 shows the port locations of the
interfaces.
Table 4: CLI Equivalents of Terms Used in Documentation for ACX500 Outdoor Routers
Hardware
Item (as
Displayed
in the CLI)
Description (as
Displayed in the
CLI)
Value (as
Displayed in the
CLI)
Additional InformationItem in Documentation
25
FPC (n)
PIC (n)
Abbreviated name of
the Flexible PIC
Concentrator (FPC)
Abbreviated name of
the Physical Interface
Card (PIC)
Value of n is
always 0.
n is a value in the
range of 0–1.
PIC 03x 1GE (SFP)
PIC 13x 1GE (RJ-45)
Router chassis–ACX500Chassis
The router does not have
actual FPCs. In this case,
FPC refers to the router
itself.
The router does not have
actual PIC devices; see
entries for PIC 0 through
PIC 1 for the equivalent
item on the router.
Built-in uplink ports on
the front panel of the
router
Built-in uplink ports on
the front panel of the
router
“Chassis Physical
Specifications for ACX500
Routers” on page 84
Interface Naming Conventions
Used in the Junos OS
Operational Commands
Interface Naming Conventions
Used in the Junos OS
Operational Commands
“ACX500 Universal Metro
Router Overview” on page 19
“ACX500 Universal Metro
Router Overview” on page 19
Xcvr (n)
supply (n)
Fan
Abbreviated name of
the transceiver
Built-in power supplyPower
NOTE: ACX500
routers are fanless.
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
Fan–Fan
“Uplink Ports on ACX500
Routers” on page 63
“ACX500 Power Overview”
on page 68
“Cooling System and Airflow
in ACX500 Routers” on
page 67
Figure 2: ACX500 Outdoor Router Interface Port Mapping
3—1— FPC 0, PIC 1: 0/1/0–0/1/2 (3x1GE RJ-45)GPS LED
2—FPC 0, PIC 0: 0/0/0–0/0/2 (3x1GE SFP)
26
ACX500 Outdoor Routers with PoE Hardware and CLI Terminology Mapping
Table 5 on page 26 describes the hardware terms used in ACX500 outdoor router with PoE documentation
and the corresponding terms used in the Junos OS CLI. Figure 3 on page 28 shows the port locations of
the interfaces.
Table 5: CLI Equivalents of Terms Used in Documentation for ACX500 Outdoor Routers with PoE
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–ACX500Chassis
The router does not have
actual FPCs. In this case,
FPC refers to the router
itself.
Additional InformationItemin Documentation
“Chassis Physical
Specifications for ACX500
Routers” on page 84
Interface Naming Conventions
Used in the Junos OS
Operational Commands
Table 5: CLI Equivalents of Terms Used in Documentation for ACX500 Outdoor Routers with PoE (continued)
Hardware
Item (as
Displayed
in the CLI)
Description (as
Displayed in the CLI)
Value (as
Displayed in the
CLI)
Additional InformationItemin Documentation
27
PIC (n)
Xcvr (n)
Abbreviated name of
the Physical Interface
Card (PIC)
PoE+ support)
Abbreviated name of
the transceiver
n is a value in the
range of 0–1.
PIC 03x 1GE (SFP)
PIC 13x 1GE (RJ-45 with
equivalent to the
number of the
port in which the
transceiver is
installed.
The router does not have
actual PIC devices; see
entries for PIC 0 through
PIC 1 for the equivalent
item on the router.
Built-in uplink ports on
the front panel of the
router
Built-in uplink ports on
the front panel of the
router
Optical transceiversn is a value
Interface Naming Conventions
Used in the Junos OS
Operational Commands
“ACX500 Universal Metro
Router Overview” on page 19
“ACX500 Universal Metro
Router Overview” on page 19
“Uplink Ports on ACX500
Routers” on page 63
supply (n)
Fan
Built-in power supplyPower
NOTE: ACX500
routers are fanless.
always 0.
DC power supplyValue of n is
Fan–Fan
“ACX500 Power Overview”
on page 68
“Cooling System and Airflow
in ACX500 Routers” on
page 67
Figure 3: ACX500 Outdoor Router Interface Port Mapping
Incoming packet
Ingress classification
In order of
decreasing precedence:
MF classification (DFW)
Fixed classification
BA classification
Queuing Egress rewrite
Outgoing packet
g006408
Buffering Scheduling
28
GPS LED
3—1— FPC 0, PIC 1: 0/1/0–0/1/2 (3x1GE RJ-45 with PoE+
support)
2—FPC 0, PIC 0: 0/0/0–0/0/2 (3x1GE SFP)
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 4 on page 28.
Figure 4: 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.
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
Qn
WRED
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 29. 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
29
SEE ALSO
ACX Series Universal Metro Router Configuration Guide
Protocols and Applications Supported by ACX Series Routers
Table 6 on page 30 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 family
inet 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:
https://kb.juniper.net/InfoCenter/index?page=content&id=KB28179.
Table 6: Protocols and Applications Supported by ACX Series Routers
Protocol or
Application
30
ACX5448ACX500ACX5096ACX5048ACX4000ACX2200ACX2100ACX2000ACX1100ACX1000
Interface and Encapsulation Types
10G
only)
interfaces (SAToP,
CESoP)
12.2R212.212.2R212.2Ethernet interfaces—1G,
12.3X54
–D15
-12.2R212.2–12.2Circuit emulation
12.3x51
-D10
––––––Ethernet interfaces—40G
-D10
15.1X54
–D20
15.1X54
–D20
15.1X54
–D20
–D20
–D20
(Indoor)
12.3X54
–D25
(Outdoor)
18.2R112.3X54
18.2R1–15.1X54
––––––12.2R212.2–12.2ATM interfaces (IMA
––––––12.2R212.2–12.2E1 interfaces
––––––12.2R212.2–12.2T1 interfaces
––––12.3x51
Loading...