Juniper ACX5048, ACX5096 User Manual
ACX5048 and ACX5096 Universal Metro
Published
2020-12-14
Router 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.
ACX5048 and ACX5096 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 | 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
ACX5048 and ACX5096 System Overview | 17
ACX5000 Universal Metro Router Overview | 17
Benefits of the ACX5048 and ACX5096 Routers | 18
ACX5048 Router | 18
ACX5096 Router | 19
ACX5000 Router Models | 19
Field-Replaceable Units in an ACX5000 Router | 20
Understanding Hardware Redundancy of an ACX5000 Router Components and
Functionality | 22
ACX5000 Routers Hardware and CLI Terminology Mapping | 22
ACX5048 Router Hardware and CLI Terminology Mapping | 23
ACX5096 Router Hardware and CLI Terminology Mapping | 24
Protocols and Applications Supported by ACX Series Routers | 26
ACX5048 and ACX5096 Chassis | 47
Management Panel of an ACX5000 Router | 47
Port Panel of an ACX5048 Router | 50
Port Panel of an ACX5096 Router | 51
Router Ports | 52
Channelizing Interfaces | 53
Chassis Status LEDs on an ACX5000 Router | 53
2
Management Port LEDs on an ACX5000 Router | 55
Access Port and Uplink Port LEDs on an ACX5000 Router | 57
ACX5048 and ACX5096 Cooling System | 60
Cooling System and Airflow in an ACX5000 Router | 60
Fan Modules | 60
Fan Module Status | 63
Fan Module LED on an ACX5000 Router | 64
ACX5048 and ACX5096 Power System | 65
AC Power Supply for an ACX5000 Router | 65
AC Power Supply LEDs on an ACX5000 Router | 67
DC Power Supply for an ACX5000 Router | 69
DC Power Supply LEDs on an ACX5000 Router | 72
iv
AC Power Specifications for an ACX5000 Router | 73
AC Power Cord Specifications for an ACX5000 Router | 74
DC Power Specifications for an ACX5000 Router | 75
Site Planning, Preparation, and Specifications
Site Preparation Checklist for an ACX5000 Router | 78
ACX5048 and ACX5096 Site Guidelines and Requirements | 79
General Site Guidelines | 80
Site Electrical Wiring Guidelines | 80
Clearance Requirements for Airflow and Hardware Maintenance for an ACX5000 Router | 81
Chassis Physical Specifications for an ACX5000 Router | 82
ACX5000 Router Environmental Specifications | 83
ACX5000 Chassis Grounding Cable and Lug Specifications | 84
Cabinet Requirements for an ACX5000 Router | 85
Rack Requirements for an ACX5000 Router | 86
3
ACX5048 and ACX5096 Network Cable and Transceiver Planning | 88
Determining Transceiver Support for the ACX5000 | 88
Cable Specifications for QSFP+ and QSFP28 Transceivers | 89
Calculating Power Budget and Power Margin for Fiber-Optic Cables | 91
How to Calculate Power Budget for Fiber-Optic Cable | 92
How to Calculate Power Margin for Fiber-Optic Cable | 92
Fiber-Optic Cable Signal Loss, Attenuation, and Dispersion | 94
Signal Loss in Multimode and Single-Mode Fiber-Optic Cable | 94
Attenuation and Dispersion in Fiber-Optic Cable | 94
ACX5048 and ACX5096 Management Cable Specifications and Pinouts | 95
Cable Specifications for Console and Management Connections for an ACX5000 Router | 95
Management Port Connector Pinouts for an ACX5000 Router | 96
v
Console Port Connector Pinouts for an ACX5000 Router | 97
USB Port Specifications for an ACX5000 Router | 98
Initial Installation and Configuration
ACX5048 and ACX5096 Installation Overview | 101
Unpacking and Mounting the ACX5048 and ACX5096 Routers | 102
Unpacking an ACX5000 Router | 102
Mounting an ACX5000 Router in a Rack or Cabinet | 103
Before You Begin Rack Installation | 104
Four Post Procedure | 106
Two Post Procedure | 108
Connecting the ACX5048 and ACX5096 to Power | 109
Connecting the ACX5000 Router to Earth Ground | 110
Connecting AC Power to an ACX5000 Router | 112
Connecting DC Power to an ACX5000 Router | 114
Connecting the ACX5048 and ACX5096 to External Devices | 120
Connecting an ACX5000 Router to a Management Console | 120
Connecting an ACX5000 Router to a Network for Out-of-Band Management | 121
Initially Configuring the ACX5000 Router | 122
Removing, Installing, and Maintaining Components
4
5
6
Maintaining ACX5048 and ACX5096 Components | 126
Removing a Transceiver from an ACX5000 Router | 126
Installing a Transceiver in an ACX5000 Router | 128
Disconnecting a Fiber-Optic Cable from an ACX5000 Router | 130
Connecting a Fiber-Optic Cable to an ACX5000 Router | 131
Maintaining Fiber-Optic Cables in an ACX5000 Router | 132
Removing a Fan Module from an ACX5000 Router | 133
Installing a Fan Module in an ACX5000 Router | 134
Removing a Power Supply from an ACX5000 Router | 136
Installing a Power Supply in an ACX5000 Router | 138
Powering Off an ACX5000 Router | 140
Removing an ACX5000 Router from a Rack or Cabinet | 143
vi
Troubleshooting Hardware
Troubleshooting ACX5048 and ACX5096 | 146
Understanding the ACX5000 Router Alarms | 146
ACX5000 Router Interface Alarm Messages | 147
Contacting Customer Support
Contacting Customer Support and Returning the Chassis or Components | 149
Contact Customer Support | 149
Returning an ACX5000 Router or Component for Repair or Replacement | 150
Locating the Serial Number on an ACX5000 Router or Component | 151
Listing the Chassis and Component Details Using the CLI | 151
Locating the Chassis Serial Number ID Label on an ACX5000 Router | 153
Locating the Serial Number ID Labels on FRU Components | 153
Packing an ACX5000 Router or Component for Shipping | 154
Packing an ACX5000 Router for Shipping | 154
Packing an ACX5000 Router Components for Shipping | 155
Safety and Compliance Information
7
General Safety Guidelines and Warnings | 158
Definitions of Safety Warning Levels | 159
Qualified Personnel Warning | 162
Warning Statement for Norway and Sweden | 163
Fire Safety Requirements | 163
Fire Suppression | 163
Fire Suppression Equipment | 163
Installation Instructions Warning | 165
Chassis and Component Lifting Guidelines | 165
vii
Restricted Access Warning | 167
Ramp Warning | 169
Rack-Mounting and Cabinet-Mounting Warnings | 170
Grounded Equipment Warning | 176
Radiation from Open Port Apertures Warning | 177
Laser and LED Safety Guidelines and Warnings for the ACX5000 Router | 178
General Laser Safety Guidelines | 178
Class 1M Laser Product Warning | 179
Class 1M Laser Radiation Warning | 179
Class 1 Laser Product Warning | 180
Class 1 LED Product Warning | 181
Laser Beam Warning | 182
Unterminated Fiber-Optic Cable Warning | 183
Maintenance and Operational Safety Guidelines and Warnings | 185
Battery Handling Warning | 187
Jewelry Removal Warning | 188
Lightning Activity Warning | 190
Operating Temperature Warning | 191
Product Disposal Warning | 193
General Electrical Safety Guidelines and Warnings | 194
Action to Take After an Electrical Accident | 195
Prevention of Electrostatic Discharge Damage | 196
AC Power Electrical Safety Guidelines | 197
AC Power Disconnection Warning | 199
ACX5000 DC Power Electrical Safety Guidelines and Warnings | 199
DC Power Copper Conductors Warning | 201
DC Power Disconnection Warning | 202
DC Power Grounding Requirements and Warning | 204
viii
DC Power Wiring Sequence Warning | 206
DC Power Wiring Terminations Warning | 209
Multiple Power Supplies Disconnection Warning | 212
TN Power Warning | 213
Agency Approvals for an ACX5000 Router | 213
Compliance Statements for EMC Requirements for the ACX5000 Router | 214
Canada | 215
European Community | 215
Israel | 216
Japan | 216
Korea | 216
United States | 217
Nonregulatory Environmental Standards | 217
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 ACX5048 and ACX5096 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:
[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]
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.
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/
•
xv
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
ACX5048 and ACX5096 System Overview | 17
ACX5048 and ACX5096 Chassis | 47
ACX5048 and ACX5096 Cooling System | 60
ACX5048 and ACX5096 Power System | 65
ACX5048 and ACX5096 System Overview
IN THIS SECTION
ACX5000 Universal Metro Router Overview | 17
ACX5000 Router Models | 19
Field-Replaceable Units in an ACX5000 Router | 20
Understanding Hardware Redundancy of an ACX5000 Router Components and Functionality | 22
ACX5000 Routers Hardware and CLI Terminology Mapping | 22
Protocols and Applications Supported by ACX Series Routers | 26
17
ACX5000 Universal Metro Router Overview
IN THIS SECTION
Benefits of the ACX5048 and ACX5096 Routers | 18
ACX5048 Router | 18
ACX5096 Router | 19
The ACX5000 Universal Metro Routers are Juniper Networks’ top-of-rack router solutions for data centers
and campus distribution or aggregation environments. The ACX5000 router portfolio consists of
high-performance fixed-configuration routers that add higher port densities, additional scalability, and
improved latency to the ACX Series. The ACX5000 routers are available in two models—ACX5048 and
ACX5096. See “ACX5000 Router Models” on page 19.
ACX5000 routers offer a compact 1 U model and a 2 U model that provide wire-speed packet performance,
very low latency, and a rich set of Layer 2 and Layer 3 features. These routers have a high-throughput
Packet Forwarding Engine, and the performance of the control plane running on ACX5000 routers is
enhanced by the 1.5 Ghz dual-core Intel CPU with 8 GB of memory and 32 GB of solid-state drive (SSD)
storage.
The ACX5000 routers include both 10-Gigabit Ethernet and 40-Gigabit Ethernet fixed configurations.
For more information about which features are supported on an ACX5000 routers, see “Protocols and
g000810
Applications Supported by ACX Series Routers” on page 26.
ACX5000 routers use the Junos operating system (OS), which provides Layer 2 and Layer 3 switching,
routing, and security services. Junos OS is installed on an ACX5000 router’s 32-gigabyte (GB) internal solid
state flash drive. The same Junos OS code base that runs on an ACX5000 routers also runs on all Juniper
Networks QFX and EX Series switches, and J Series, M Series, MX Series, ACX Series and T Series routers.
You manage the router using the Junos OS command-line interface (CLI), accessible through the console
and out-of-band management ports on the router.
Benefits of the ACX5048 and ACX5096 Routers
Performance—ACX5000 routers provide wire-speed packet performance, very low latency, and a rich
•
set of Layer 2 and Layer 3 features.
Service virtualization—ACX5000 routers offer service virtualization on a dedicated and customizable
•
KVM-compliant virtual machine that enables you to execute operational scripts and programs for network
performance monitoring and analysis.
18
ACX5048 Router
As shown in Figure 1 on page 18, the ACX5048 is a 10-Gigabit Ethernet enhanced small form-factor
pluggable (SFP+) top-of-rack router with 48 SFP+ ports and 6 quad SFP+ (QSFP+) ports. Each SFP+ port
can operate as a native 10-Gigabit Ethernet port or as a 1-Gigabit Ethernet port when 1-gigabit optics are
inserted. Each QSFP+ port (48 through 53) can operate as a 40-Gigabit Ethernet port or be channelized
to operate as four independent 10-Gigabit Ethernet ports (a total of 24 10-Gigabit Ethernet ports). The
6 QSFP+ ports can be used as either access ports or uplink ports. The ACX5048 provides full duplex
throughput of 1.44 Tbps. The ACX5048 has a 1 U form factor and is shipped with redundant fans and
redundant power supplies. The router can be ordered with front-to-back airflow (air out or AFO) and with
AC or DC power supplies.
Figure 1: ACX5048 Port Panel
ACX5048 can be used only as a standalone router.
ACX5096 Router
As shown in Figure 2 on page 19, the ACX5096 is a is a 10-Gigabit Ethernet enhanced small form-factor
pluggable (SFP+) top-of-rack router with 96 SFP+ ports and 8 quad SFP+ (QSFP+) ports. Each SFP+ port
can operate as a native 10-Gbps port or as a 1-Gbps port. The QSFP+ ports 96 and 100 can operate at
native 40 Gbps speed or can be channelized to 4 independent 10 Gbps port speeds. The 8 QSFP+ ports
can be used as either access ports or as uplinks. The ACX5096 has a 2 U form factor and is shipped with
redundant fans and redundant power supplies. The router can be ordered with front-to-back airflow (air
out or AFO) and with AC or DC power supplies.
Figure 2: ACX5096 Port Panel
19
ACX5096 can be used only as a standalone router.
SEE ALSO
Chassis Physical Specifications for an ACX5000 Router | 82
ACX5000 Router Models
Table 3 on page 20 lists the ACX5000 router models. The ACX5000 routers are available in 48 port or 96
port configurations. The routers are available with either AC or DC power supply and with airflow-out
(AFO) cooling.
Table 3: ACX5000 Router Model Numbers and Description
Power
SupplyPortsModel Number
Number
of
Management
Ports
20
Airflow
ACX5048-AC
ACX5048-DC
ACX5096-AC
ACX5096-DC
SEE ALSO
3AC48 SFP+ and 6 QSFP+
transceivers
3DC48 SFP+ and 6 QSFP+
transceivers
2AC96 SFP+ and 8 QSFP+
transceivers
2DC96 SFP+ and 8 QSFP+
transceivers
Air Out
(front-to-back)
Air Out
(front-to-back)
Air Out
(front-to-back)
Air Out
(front-to-back)
CAUTION: Do not mix different types (AC and DC) of power supplies in the same
chassis.
Determining Transceiver Support for the ACX5000 | 88
Field-Replaceable Units in an ACX5000 Router
Field-replaceable units (FRUs) are components that you can replace at your site. The ACX5000 FRUs are
hot-insertable and hot-removable: you can remove and replace them without powering off the router or
disrupting the routing function.
The following are the ACX5000 FRUs:
Power supplies
•
Fan modules
•
Table 4 on page 21 lists the FRUs for the ACX5000 and actions to take before removing them.
Table 4: FRUs in ACX5000 Routers and Action Required Before Removing Them
Required ActionFRUs
NonePower supplies
NoneFan modules
CAUTION: Replace a failed power supply with a blank panel or new power supply
within one minute of removal to prevent chassis overheating. The router continues to
operate with only one power supply running. Replace a failed fan module with a new
fan module within one minute of removal to prevent chassis overheating. Do not
operate the router with missing FRUs for longer than one minute.
NOTE: If you have a Juniper J-Care service contract, register any addition, change, or upgrade
of hardware components at
https://www.juniper.net/customers/csc/management/updateinstallbase.jsp . Failure to do so
can result in significant delays if you need replacement parts. This note does not apply if you
replace existing components with the same type of component.
21
NOTE: Before removing the optical transceivers, we recommend that you disable the interface
using the set interfaces interface-name disable command. See “Disconnecting a Fiber-Optic
Cable from an ACX5000 Router” on page 130.
SEE ALSO
Installing a Power Supply in an ACX5000 Router | 138
Removing a Power Supply from an ACX5000 Router | 136
Installing a Fan Module in an ACX5000 Router | 134
Removing a Fan Module from an ACX5000 Router | 133
Understanding Hardware Redundancy of an ACX5000 Router Components and Functionality
The following hardware components provide redundancy on an ACX5000 router:
Power supplies—The ACX5000 router has one or two power supplies. Each power supply provides
•
power to all components in the router. If two power supplies are installed, the two power supplies
provide full power redundancy to the device. If one power supply fails or is removed, the second power
supply balances the electrical load without interruption.
To provide power redundancy to the system both power supplies must be installed. Connect power
source feed A to one power supply and power source feed B to the second power supply.
CAUTION: Do not connect feed A and feed B to the same power supply input
terminal.
22
Cooling system—The 1 U ACX5048 router has five fan modules; the 2 U ACX5096 router has three fan
•
modules. If a fan module fails and is unable to keep the ACX5000 router within the desired temperature
thresholds, chassis alarms occur and the ACX5000 router can shut down.
SEE ALSO
AC Power Supply for an ACX5000 Router | 65
DC Power Supply for an ACX5000 Router | 69
Cooling System and Airflow in an ACX5000 Router | 60
ACX5000 Routers Hardware and CLI Terminology Mapping
IN THIS SECTION
ACX5048 Router Hardware and CLI Terminology Mapping | 23
ACX5096 Router Hardware and CLI Terminology Mapping | 24
ACX5048 Router Hardware and CLI Terminology Mapping
Table 5 on page 23 describes the hardware terms used in an ACX5048 router documentation and the
corresponding terms used in the Junos OS command line interface (CLI). Figure 3 on page 24 shows the
port locations of the interfaces.
Table 5: CLI Equivalents of Terms Used in Documentation for an ACX5048 Router
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
FPC (n)
PIC (n)
Xcvr (n)
Abbreviated name
of the Flexible PIC
Concentrator (FPC)
Abbreviated name
of the Physical
Interface Card (PIC)
Abbreviated name
of the transceiver
Value of n is always
0.
Value of n is always
0.
PIC 048x10G–6x40G
equivalent to the
number of the port
in which the
transceiver is
installed.
Router chassis–ACX5048Chassis
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 for
the equivalent item on
the router.
Built-in network ports
on the front panel of the
router
“Chassis Physical Specifications
for an ACX5000 Router” on
page 82
Interface Naming Conventions
Used in the Junos OS
Operational Commands
Interface Naming Conventions
Used in the Junos OS
Operational Commands
“ACX5000 Universal Metro
Router Overview” on page 17
Port and Interface SpecificationsOptical transceiversn is a value
supply (n)
Power supplyPower
n is a value in the
range of 0-1.
AC power supply
DC power supply
“AC Power Supply for an
ACX5000 Router” on page 65
“DC Power Supply for an
ACX5000 Router” on page 69
Table 5: CLI Equivalents of Terms Used in Documentation for an ACX5048 Router (continued)
g0008 0 9
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
FanFan
range of 0-4.
Fann is a value in the
“Cooling System and Airflow
in an ACX5000 Router” on
page 60
Figure 3: ACX5048 Interface Port Mapping
3—1— 40 Gigabit Ethernet ports (6)Electrostatic Discharge (ESD) terminal
2—10 Gigabit Ethernet ports (48)
ACX5096 Router Hardware and CLI Terminology Mapping
Table 6 on page 24 describes the hardware terms used in an ACX5096 router documentation and the
corresponding terms used in the Junos OS command line interface (CLI). Figure 4 on page 26 shows the
port locations of the interfaces.
Table 6: CLI Equivalents of Terms Used in Documentation for an ACX5096 Router
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–ACX5096Chassis
The router does not
have actual FPCs. In this
case, FPC refers to the
router itself.
Additional Information
“Chassis Physical
Specifications for an ACX5000
Router” on page 82
Interface Naming Conventions
Used in the Junos OS
Operational Commands
Table 6: CLI Equivalents of Terms Used in Documentation for an ACX5096 Router (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
25
PIC (n)
Xcvr (n)
Power
supply (n)
Abbreviated name
of the Physical
Interface Card (PIC)
Abbreviated name
of the transceiver
Built-in power
supply
Value of n is always
0.
PIC 096x10G–8x40G
equivalent to the
number of the port
in which the
transceiver is
installed.
n is a value in the
range of 0-1.
The router does not
have actual PIC devices;
see entries for PIC 0 for
the equivalent item on
the router.
Built-in network ports
on the front panel of the
router
AC power supply
DC power supply
Interface Naming Conventions
Used in the Junos OS
Operational Commands
“ACX5000 Universal Metro
Router Overview” on page 17
Port and Interface SpecificationsOptical transceiversn is a value
“AC Power Supply for an
ACX5000 Router” on page 65
“DC Power Supply for an
ACX5000 Router” on page 69
FanFan
range of 0-2 for
ACX5096
Fann is a value in the
“Cooling System and Airflow
in an ACX5000 Router” on
page 60
Figure 4: ACX5096 Interface Port Mapping
3—1— 40 Gigabit Ethernet ports (8)Electrostatic Discharge (ESD) terminal
2—10 Gigabit Ethernet ports (96)
Protocols and Applications Supported by ACX Series Routers
Table 7 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.
26
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 7: Protocols and Applications Supported by ACX Series Routers
Protocol or
Application
Interface and Encapsulation Types
ACX5448ACX500ACX5096ACX5048ACX4000ACX2200ACX2100ACX2000ACX1100ACX1000
Table 7: Protocols and Applications Supported by ACX Series Routers (continued)
Protocol or
Application
27
ACX5448ACX500ACX5096ACX5048ACX4000ACX2200ACX2100ACX2000ACX1100ACX1000
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
Layer 3
–––––SONET/SDH interfaces
-D10
(requires
a
MIC)
12.2R212.212.2R212.2Static routes
12.3X54
–D15
12.3x51
-D10
15.1X54
–D20
15.1X54
–D20
–D20
(Indoor)
12.3X54
–D25
(Outdoor)
––––12.3x51
18.2R112.3X54
Table 7: Protocols and Applications Supported by ACX Series Routers (continued)
Protocol or
Application
28
ACX5448ACX500ACX5096ACX5048ACX4000ACX2200ACX2100ACX2000ACX1100ACX1000
12.2R212.212.2R212.2OSPF
12.2R212.212.2R212.2IS-IS
12.2R212.212.2R212.2BGP
12.3X54
–D15
12.3X54
–D15
12.3X54
–D15
12.3x51
-D10
12.3x51
-D10
12.3x51
-D10
15.1X54
–D20
15.1X54
–D20
15.1X54
–D20
15.1X54
–D20
15.1X54
–D20
15.1X54
–D20
–D20
(Indoor)
12.3X54
–D25
(Outdoor)
–D20
(Indoor)
12.3X54
–D25
(Outdoor)
–D20
(Indoor)
12.3X54
–D25
(Outdoor)
18.2R112.3X54
18.2R112.3X54
18.2R112.3X54
Protocol (ICMP)
Protocol (ARP)
12.2R212.212.2R212.2Internet Control Message
12.2R212.212.2R212.2Address Resolution
12.3X54
–D15
12.3X54
–D15
12.3x51
-D10
12.3x51
-D10
15.1X54
–D20
15.1X54
–D20
15.1X54
–D20
15.1X54
–D20
–D20
(Indoor)
12.3X54
–D25
(Outdoor)
–D20
(Indoor)
12.3X54
–D25
(Outdoor)
18.2R112.3X54
18.2R112.3X54
Table 7: Protocols and Applications Supported by ACX Series Routers (continued)
Protocol or
Application
29
ACX5448ACX500ACX5096ACX5048ACX4000ACX2200ACX2100ACX2000ACX1100ACX1000
Detection (BFD) protocol
Configuration Protocol
(DHCP)
(OSPF, IS-IS)
12.2R212.212.2R212.2Bidirectional Forwarding
12.2R212.212.2R212.2Dynamic Host
12.2R212.212.2R212.2IP fast reroute (FRR)
12.3X54
–D15
12.3X54
–D15
12.3X54
–D15
12.3x51
-D10
12.3x51
-D10
12.3x51
-D10
15.1X54
–D20
15.1X54
–D20
15.1X54
–D20
15.1X54
–D20
15.1X54
–D20
15.1X54
–D20
–D20
(Indoor)
12.3X54
–D25
(Outdoor)
–D20
(Indoor)
12.3X54
–D25
(Outdoor)
–D20
(Indoor)
12.3X54
–D25
(Outdoor)
18.2R112.3X54
18.2R112.3X54
18.2R112.3X54
unit (MTU) range (256 to
9192)
12.2R212.212.2R212.2Maximum transmission
12.3R112.3R112.3R112.3R1Layer 3 VPNs
12.3X54
–D15
12.3X54
–D15
12.3x51
-D10
12.3x51
-D10
15.1X54
–D20
15.1X54
–D20
15.1X54
–D20
15.1X54
–D20
–D20
(Indoor)
12.3X54
–D25
(Outdoor)
–D20
(Indoor)
12.3X54
–D25
(Outdoor)
18.2R112.3X54
18.2R112.3X54
Table 7: Protocols and Applications Supported by ACX Series Routers (continued)
Protocol or
Application
30
ACX5448ACX500ACX5096ACX5048ACX4000ACX2200ACX2100ACX2000ACX1100ACX1000
MPLS, VPLS, VPNs
path (LSP)
12.2R212.212.2R212.2RSVP
12.2R212.212.2R212.2LDP (targeted and direct)
12.2R212.212.2R212.2Static label-switched
12.3X54
–D15
12.3X54
–D15
12.3X54
–D15
12.3x51
-D10
12.3x51
-D10
12.3x51
-D10
15.1X54
–D20
15.1X54
–D20
15.1X54
–D20
15.1X54
–D20
15.1X54
–D20
15.1X54
–D20
–D20
(Indoor)
12.3X54
–D25
(Outdoor)
–D20
(Indoor)
12.3X54
–D25
(Outdoor)
–D20
(Indoor)
18.2R112.3X54
18.2R112.3X54
18.2R112.3X54
12.3X54
–D25
(Outdoor)
12.2R212.212.2R212.2FRR
12.2R212.212.2R212.2Traffic engineering
12.3X54
–D15
12.3X54
–D15
12.3x51
-D10
12.3x51
-D10
15.1X54
–D20
15.1X54
–D20
15.1X54
–D20
15.1X54
–D20
–D20
(Indoor)
12.3X54
–D25
(Outdoor)
–D20
(Indoor)
12.3X54
–D25
(Outdoor)
18.2R112.3X54
18.2R112.3X54
Loading...