Juniper SRX320 User Manual
SRX320 Services Gateway Hardware Guide
Published
2020-11-10
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.
SRX320 Services Gateway 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 | viii
Documentation and Release Notes | viii
Using the Examples in This Manual | viii
Merging a Full Example | ix
Merging a Snippet | x
Documentation Conventions | x
Documentation Feedback | xiii
Requesting Technical Support | xiii
Self-Help Online Tools and Resources | xiv
Creating a Service Request with JTAC | xiv
iii
Overview
SRX320 Services Gateway Overview | 16
SRX320 Services Gateway Description | 16
SRX320 Services Gateway Field Replaceable Units Overview | 17
Benefits of the SRX320 Services Gateway | 17
SRX320 Chassis | 18
SRX320 Services Gateway Chassis Overview | 18
SRX320 Services Gateway Front Panel | 18
Network Port LEDs | 21
SRX320 Services Gateway Back Panel | 21
SRX320 Services Gateway Interface Modules Overview | 23
SRX320 Cooling System | 23
SRX320 Power System | 24
Understanding the SRX320 Services Gateway Power Supply | 25
SRX320 Services Gateway Power Specifications and Requirements | 25
Power Cord Specifications for SRX320 | 26
Site Planning, Preparation, and Specifications
2
3
SRX320 Site Preparation Checklist | 29
SRX320 Site Guidelines and Requirements | 31
SRX320 Services Gateway General Site Guidelines | 31
SRX320 Services Gateway Environmental Specifications | 31
SRX320 Services Gateway Electrical Wiring Guidelines | 32
SRX320 Services Gateway Grounding Specifications | 34
SRX320 Services Gateway Physical Specifications | 34
SRX320 Services Gateway Clearance Requirements for Airflow and Hardware
Maintenance | 35
Rack Requirements | 35
Cabinet Requirements | 36
SRX320 Transceiver Specifications and Pinouts | 37
iv
SRX320 Transceiver Support | 37
RJ-45 Connector Pinouts for the SRX320 Services Gateway Ethernet Port | 37
RJ-45 Connector Pinouts for the SRX320 Services Gateway Console Port | 38
Mini-USB Connector Pinouts for the SRX320 Services Gateway Console Port | 39
Initial Installation and Configuration
SRX320 Installation Overview | 41
SRX320 Services Gateway Installation Overview | 41
SRX320 Services Gateway Autoinstallation Overview | 41
Unpacking and Mounting the SRX320 | 43
Unpacking the SRX320 Services Gateway | 43
Verifying Parts Received with the SRX320 Services Gateway | 44
Installing the SRX320 Services Gateway on a Desk | 45
Installing the SRX320 Services Gateway on a Wall | 45
Installing the SRX320 Services Gateway in a Rack | 48
Connecting the SRX320 to Power | 52
Required Tools and Parts for Grounding the SRX320 Services Gateway | 52
Connecting the SRX320 Services Gateway Grounding Cable | 53
Connecting the SRX320 Services Gateway to the Power Supply | 54
Powering On the SRX320 Services Gateway | 55
4
5
Powering Off the SRX320 Services Gateway | 56
Connecting the SRX320 Services Gateway to a Management Console | 57
Configuring Junos OS on the SRX320 | 58
SRX320 Services Gateway Factory-Default Settings | 59
How to View Factory-Default Settings | 60
Initial Configuration Using the CLI | 61
Connect to the Serial Console Port | 61
Connect to the Mini-USB Console Port | 62
Configure the SRX320 Using the CLI | 63
Initial Configuration Using J-Web | 64
Configure Using J-Web | 64
Customize the Configuration for Junos OS Release 19.2 | 66
v
Customize the Configuration for Junos OS Release 15.1X49-D170 | 67
Configure the Device Using ZTP with Juniper Networks Network Service Controller | 68
Maintaining Components
Maintaining the SRX320 Components | 71
Required Tools and Parts for Maintaining the SRX320 Services Gateway Hardware
Components | 71
Routine Maintenance Procedures for the SRX320 Services Gateway | 71
Maintaining the SRX320 Services Gateway Cooling System Components | 72
Maintaining the SRX320 Services Gateway Power Supply | 72
Replacing Mini-Physical Interface Modules in the SRX320 Services Gateway | 72
Troubleshooting Hardware
Troubleshooting the SRX320 | 75
Troubleshooting Resources for the SRX320 Services Gateway Overview | 75
Troubleshooting Chassis and Interface Alarm Messages on the SRX320 Services Gateway | 75
Troubleshooting the Power System on the SRX320 Services Gateway | 77
Using the RESET CONFIG Button | 77
Changing the RESET CONFIG Button Behavior | 78
Contacting Customer Support and Returning the Chassis or Components
6
7
Returning the SRX320 Chassis or Components | 80
Contacting Customer Support | 80
Returning a SRX320 Services Gateway Component to Juniper Networks | 81
Locating the SRX320 Services Gateway Chassis Serial Number and Agency Labels | 81
Locating the SRX320 Services Gateway Mini-Physical Interface Module Serial Number
Label | 82
Listing the SRX320 Services Gateway Component Details with the CLI | 82
Required Tools and Parts for Packing the SRX320 Services Gateway | 83
Packing the SRX320 Services Gateway for Shipment | 83
Packing SRX320 Services Gateway Components for Shipment | 84
Safety and Compliance Information
Definitions of Safety Warning Levels | 87
vi
General Safety Guidelines and Warnings | 90
Restricted Access Warning | 92
Qualified Personnel Warning | 95
Prevention of Electrostatic Discharge Damage | 95
Fire Safety Requirements | 97
Fire Suppression | 97
Fire Suppression Equipment | 97
Laser and LED Safety Guidelines and Warnings | 98
General Laser Safety Guidelines | 98
Class 1 Laser Product Warning | 99
Class 1 LED Product Warning | 100
Laser Beam Warning | 101
Radiation from Open Port Apertures Warning | 102
Maintenance and Operational Safety Guidelines and Warnings | 103
Battery Handling Warning | 104
Jewelry Removal Warning | 105
Lightning Activity Warning | 107
Operating Temperature Warning | 108
Product Disposal Warning | 110
Action to Take After an Electrical Accident | 111
General Electrical Safety Guidelines and Warnings | 111
SRX320 Services Gateway Agency Approvals | 112
SRX320 Services Gateway Acoustic Noise Compliance Statements | 113
SRX320 Services Gateway EMC Requirements | 114
Canada | 114
European Community | 114
Israel | 114
Japan | 114
United States | 115
vii
About the Documentation
IN THIS SECTION
Documentation and Release Notes | viii
Using the Examples in This Manual | viii
Documentation Conventions | x
Documentation Feedback | xiii
Requesting Technical Support | xiii
Use this guide to install hardware and perform initial software configuration, routine maintenance, and
troubleshooting for the SRX320 Services Gateway. After completing the installation and basic configuration
procedures covered in this guide, refer to the Junos OS documentation for information about further
software configuration.
viii
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;
}
}
}
}
ix
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]
x
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 xi defines notice icons used in this guide.
Table 1: Notice Icons
xi
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 xi 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)
xii
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)
xiii
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/
•
xiv
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
SRX320 Services Gateway Overview | 16
SRX320 Chassis | 18
SRX320 Cooling System | 23
SRX320 Power System | 24
SRX320 Services Gateway Overview
IN THIS SECTION
SRX320 Services Gateway Description | 16
SRX320 Services Gateway Field Replaceable Units Overview | 17
Benefits of the SRX320 Services Gateway | 17
SRX320 Services Gateway Description
The SRX320 Services Gateway consolidates security, routing, switching, and WAN interfaces for small
distributed enterprises. With advanced threat mitigation capabilities, the services gateway provides
cost-effective and secure connectivity across distributed enterprises.
16
With a desktop form-factor chassis, the SRX320 Services Gateway has six 1 G Ethernet ports, two 1 G
SFP ports, 4 GB of DRAM memory, 8 GB of flash memory, and two Mini-Physical Interface Module
(Mini-PIM) slots.
The SRX320 Services Gateway is available with or without Power over Ethernet (PoE) capability. In the
PoE model. the six Ethernet ports are PoE capable.
The SRX320 Services Gateway runs the Junos operating system (Junos OS) and supports the following
features:
Firewall support with key features such as IPsec and VPN
•
Intrusion Detection and Prevention (IDP)
•
High availability
•
QoS
•
MPLS
•
You can manage the SRX320 Services Gateway by using the same interfaces that you use for managing
other devices that run Junos OS—the CLI, the J-Web graphical interface, and Junos Space.
SRX320 Services Gateway Field Replaceable Units Overview
Field-replaceable units (FRUs) are components that you can replace at your site. The Mini-Physical Interface
Module (MPIM) is the only FRU on the SRX320 Services Gateway.
The Mini-PIMs are not hot-swappable. You must power off the services gateway before removing or
installing Mini-PIMs.
SEE ALSO
Replacing Mini-Physical Interface Modules in the SRX320 Services Gateway | 72
Benefits of the SRX320 Services Gateway
17
High performance—The SRX320 supports up to 1-Gbps firewall and 300-Mbps IPsec VPN, and is suited
•
for small distributed enterprise branch office deployments.
Simplified deployment with minimal manual intervention—The Zero Touch Provisioning (ZTP) feature
•
enables you to provision and configure the SRX300 line automatically, thereby reducing operational
complexity and simplifying the provisioning of new sites.
Multiple WAN connectivity options—The SRX320 supports multiple options such as Ethernet, serial,
•
T1/E1, VDSL2, and 3G/4G LTE wireless for WAN or Internet connectivity to link sites.
Threat protection—The SRX300 line supports IPsec VPN, Media Access Control Security (MACsec),
•
Juniper Sky Advanced Threat Prevention, and Trusted Platform Module (TPM) to protect against potential
vulnerabilities.
RELATED DOCUMENTATION
SRX320 Installation Overview | 41
SRX320 Chassis
IN THIS SECTION
SRX320 Services Gateway Chassis Overview | 18
SRX320 Services Gateway Front Panel | 18
SRX320 Services Gateway Back Panel | 21
SRX320 Services Gateway Interface Modules Overview | 23
SRX320 Services Gateway Chassis Overview
18
The SRX320 Services Gateway chassis measures 1.73 in. high, 11.81 in. wide, and 7.52 in. deep. The PoE
model weighs 3.4 lb. and the non-PoE model weighs 3.28 lb.
CAUTION: Before removing or installing components of a functioning services gateway,
attach an electrostatic discharge (ESD) strap to an ESD point and place the other end
of the strap around your bare wrist. Failure to use an ESD strap could result in damage
to the device.
The services gateway must be connected to earth ground during normal operation. The protective earthing
terminal on the rear of the chassis is provided to connect the services gateway to ground.
SRX320 Services Gateway Front Panel
Figure 1 on page 19 shows the front panel of the SRX320 Services Gateway.
Figure 1: SRX320 Services Gateway Front Panel
Table 3 on page 19 provides details about the front panel components.
Table 3: SRX320 Services Gateway Front Panel Components
DescriptionComponentNumber
19
Reset Config button1
Console port2,6
Returns the services gateway to the rescue configuration
or the factory-default configuration.
Serial—Connects a laptop to the services gateway for
•
CLI management. The port uses an RJ-45 serial
connection and supports the RS-232 (EIA-232)
standard.
USB—Connects a laptop to the services gateway for
•
CLI management through a USB interface. The port
accepts a Mini-B type USB cable plug. A USB cable with
Mini-B and Type A USB plugs is supplied with the
services gateway.
To use the mini-USB console port, you must download
a USB driver to the management device from the
Downloads page at
https://www.juniper.net/support/downloads/?p=junos-srx#sw.
To download the driver for Windows OS, select 6.5
from the Version drop-down list.
To download the driver for Mac OS, select 4.10 from
the Version drop-down list.
Mini-PIM slots3
4
(SFP) ports
Two slots for Mini-PIMs. Mini-PIMs can be used to
provide LAN and WAN functionality along with
connectivity to various media types.
Two 1-GbE MACsec-capable ports for network traffic.1-GbE small form-factor pluggable
Table 3: SRX320 Services Gateway Front Panel Components (continued)
DescriptionComponentNumber
20
1-GbE RJ-45 ports5
USB port7
Power button9
Six LAN ports (0/0 to 0/5)
The ports have the following characteristics:
Operate in full-duplex and half-duplex modes
•
Support autonegotiation
•
The ports can be used to:
Function as front-end network ports
•
Provide LAN and WAN connectivity to hubs, switches,
•
local servers, and workstations
Forward incoming data packets to the services gateway
•
Receive outgoing data packets from the services
•
gateway
The services gateway has one USB port that accepts a
USB storage device.
Indicate component and system status at a glance.LEDs8
Use the Power button to power on or power off the
services gateway.
Figure 2 on page 20 shows the LEDs on the front panel.
Figure 2: SRX320 Services Gateway Front Panel LEDs
Table 4 on page 21 lists the front panel LEDs.
Table 4: SRX320 Services Gateway Front Panel LEDs
21
DescriptionComponent
ALARM
STAT
PWR
HA
mPIM0 and mPIM1
Solid amber (noncritical alarm)
•
Solid red (critical alarm)
•
Off (no alarms)
•
Solid green (operating normally)
•
Solid red (error detected)
•
Solid green (receiving power)
•
Solid red (power failure)
•
Off (no power)
•
Solid green (all HA links are available)
•
Solid amber (some HA links are unavailable)
•
Solid red (HA links are not functional)
•
Off (HA is disabled)
•
Solid green (Mini-PIM is functioning normally)
•
Solid red (Mini-PIM hardware failure)
•
Off (Mini-PIM is not present or Mini-PIM is not
•
detected by the device)
Network Port LEDs
The SFP and Ethernet ports have two status LEDs, LINK and ACT, located above the port.
Table 5: Network Port LEDs
DescriptionLED
LINK (LED on the left)
ACT (LED on the right)
Solid green—There is link activity.
•
Off—There is no link established.
•
Blinking green—There is activity on the 1 G link.
•
Off—There is no link activity.
•
SRX320 Services Gateway Back Panel
Figure 3 on page 22 shows the back panel of the SRX320 Services Gateway and Table 6 on page 22 lists
the components on the back panel.
Figure 3: SRX320 Services Gateway Back Panel
Table 6: SRX320 Services Gateway Back Panel Components
22
DescriptionComponentNumber
Lock1
Fans2
Cable tie holder3
Power supply input (DC power input)4
Grounding point5
Provides the capability to lock and
secure the device at the installation
site.
Keeps all the services gateway
components within the acceptable
temperature range.
Secures the DC power cord
connection to the adapter.
Connects the services gateway to
the external power supply.
Connects the services gateway
chassis to earth ground (optional).
NOTE: We recommend connecting
the services gateway to ground if
required.
SRX320 Services Gateway Interface Modules Overview
Mini-Physical Interface Modules (Mini-PIMs) are field-replaceable network interface cards (NICs) supported
on the SRX300 line of services gateways. You can easily insert or remove Mini-PIMs from the front slots
of the services gateway chassis. The Mini-PIMs provide physical connections to a LAN or a WAN. The
Mini-PIMs receive incoming packets from the network and transmit outgoing packets to the network.
During this process, they perform framing and line-speed signaling for the medium type.
CAUTION: The Mini-PIMs are not hot-swappable. You must power off the services
gateway before removing or installing Mini-PIMs.
The following Mini-PIMs are supported on the SRX320 Services Gateway:
1-Port Serial Mini-Physical Interface Module (SRX-MP-1SERIAL-R)
•
1-Port T1/E1 Mini-Physical Interface Module (SRX-MP-1T1E1-R)
•
23
1-Port VDSL2 (Annex A) Mini-Physical Interface Module (SRX-MP-1VDSL2-R)
•
LTE Mini-Physical Interface Module (SRX-MP-LTE-AE and SRX-MP-LTE-AA)
•
Wi-Fi Mini-Physical Interface Module (SRX-MP-WLAN-US, SRX-MP-WLAN-IL, and SRX-MP-WLAN-WW)
•
For more information on the Mini-PIMs, see the SRX300 Series and SRX550 High Memory Gateway
Interface Modules Reference.
RELATED DOCUMENTATION
SRX320 Installation Overview | 41
SRX320 Cooling System
The cooling system for the SRX320 Services Gateway includes two fixed fans. The fans draw air through
vents on the front of the chassis and exhaust the air through the back of the chassis. The airflow produced
by the fans keeps device components within the acceptable temperature range.
Figure 4 on page 24 shows the airflow through the chassis.
Figure 4: Airflow Through the SRX320 Services Gateway Chassis
24
RELATED DOCUMENTATION
SRX320 Services Gateway Clearance Requirements for Airflow and Hardware Maintenance | 35
SRX320 Power System
IN THIS SECTION
Understanding the SRX320 Services Gateway Power Supply | 25
SRX320 Services Gateway Power Specifications and Requirements | 25
Power Cord Specifications for SRX320 | 26
Understanding the SRX320 Services Gateway Power Supply
g022478
g022479
The power supply for the SRX320 Services Gateway is external. You must use the following power supply
adapters provided by Juniper Networks to provide power to the services gateway.
75 W, 12 V power supply adapter for non-PoE models
•
Figure 5: 75 W, 12 V Power Supply Adapter
280 W, 54 V power supply adapter for PoE models
•
25
Figure 6: 280 W, 54 V Power Supply Adapter
Each PoE port delivers a maximum power of 30 W. Because of line loss, the powered device connected
to a PoE port can use only 25.5 W of power. Line loss is influenced by cable length, quality, and other
factors and is typically less than 16 percent of the maximum power.
SRX320 Services Gateway Power Specifications and Requirements
Table 7 on page 25 lists the power specifications for the SRX320 Services Gateway power supply adapter.
Table 7: Power Specifications for the SRX320 Services Gateway Power Supply Adapter
Specifications
Power Supply Adapter
Requirement PoE modelNon-PoE model
100 to 240 VAC100 to 240 VACAC input
50 to 60 Hz50 to 60 HzAC input line frequency
Table 7: Power Specifications for the SRX320 Services Gateway Power Supply Adapter (continued)
Specifications
Power Supply Adapter
Requirement PoE modelNon-PoE model
3.25 A maximum1.3 A maximumAC system current rating
26
Maximum AC inrush current
11 A at 220 V/50 Hz (with two
Mini-PIMs installed)
15 A at 220 V/50 Hz (with two
Mini-PIMs installed)
WARNING: The AC power cord for the services gateway is intended for use with only
the power supply adapter provided with the device.
SEE ALSO
SRX320 Services Gateway Electrical Wiring Guidelines | 32
Power Cord Specifications for SRX320
A detachable power cord is supplied with the device. The coupler is type C13 as described by International
Electrotechnical Commission (IEC) standard 60320. The plug end of the power cord fits into the power
source outlet that is standard for your geographical location.
NOTE: In North America, AC power cords must not exceed 4.5 meters (approximately 14.75 feet)
in length, to comply with National Electrical Code (NEC) Sections 400-8 (NFPA 75, 5-2.2) and
210-52 and Canadian Electrical Code (CEC) Section 4-010(3). The cords supplied with the device
are in compliance.
Table 8 on page 26 lists the AC power cord specifications for the countries and regions listed in the table.
Table 8: AC Power Cord Specifications
Juniper Model NumberPlug StandardsElectrical SpecificationsCountry/Region
250 VAC, 10 A, 50 HzAustralia
SAA/3
CBL-JX-PWR-AUAS/NZZS 3112 Type
Table 8: AC Power Cord Specifications (continued)
Switzerland, and United
Kingdom)
27
Juniper Model NumberPlug StandardsElectrical SpecificationsCountry/Region
CBL-JX-PWR-CHGB 1002-1996 Type PRC/3250 VAC, 10 A, 50 HzChina
CBL-JX-PWR-EUCEE (7) VII Type VIIG250 VAC, 10 A, 50 HzEurope (except Italy,
CBL-EX-PWR-C13-INIS 1293 Type IND/3250 VAC, 10 A, 50 HzIndia
CBL-JX-PWR-ITCEI 23-16 Type I/3G250 VAC, 10 A, 50 HzItaly
Japan
Hz
Korea
Hz
CBL-JX-PWR-JPSS-00259 Type VCTF125 VAC, 12 A, 50 Hz or 60
CBL-JX-PWR-KRCEE (7) VII Type VIIGK250 VAC, 10 A, 50 Hz or 60
CBL-EX-PWR-C13-SZSEV 6534-2 Type 12G250 VAC, 10 A, 50 HzSwitzerland
CBL-JX-PWR-UKBS 1363/A Type BS89/13250 VAC, 10 A, 50 HzUnited Kingdom
CBL-JX-PWR-USNEMA 5-15 Type N5-15125 VAC, 13 A, 60 HzUnited States
Figure 7 on page 27 illustrates the plug on the power cord for some of the countries or regions listed in
Table 8 on page 26.
Figure 7: AC Plug Types
2
CHAPTER
Site Planning, Preparation, and
Specifications
SRX320 Site Preparation Checklist | 29
SRX320 Site Guidelines and Requirements | 31
SRX320 Transceiver Specifications and Pinouts | 37
SRX320 Site Preparation Checklist
Table 9 on page 29 provides a checklist of tasks you need to perform when preparing a site for installing
the SRX320 Services Gateway.
Table 9: Site Preparation Checklist for SRX320 Services Gateway Installation
Additional InformationItem or Task
Environment
“SRX320 Services Gateway Environmental Specifications” on page 31Verify that environmental factors
such as temperature and humidity
do not exceed device tolerances.
Power
29
Measure the distance between
•
the external power sources and
the device installation site.
Locate sites for connection of
•
system grounding.
Calculate the power consumption
•
and requirements.
Rack Requirements
minimum requirements.
Rack Installation
Plan the rack location, including
•
required space clearances.
Secure the rack to the floor and
•
building structure.
Cabinet Requirements
“SRX320 Services Gateway Electrical Wiring Guidelines” on page 32
“SRX320 Services Gateway Power Specifications and Requirements” on
page 25
“SRX320 Site Guidelines and Requirements” on page 31Verify that your rack meets the
“Installing the SRX320 Services Gateway in a Rack” on page 48
Verify that your cabinet meets
•
the minimum requirements.
Plan the cabinet location,
•
including required space
clearances.
“SRX320 Site Guidelines and Requirements” on page 31
Table 9: Site Preparation Checklist for SRX320 Services Gateway Installation (continued)
Additional InformationItem or Task
Wall Installation
30
Verify that the area selected
•
meets the minimum
requirements.
Verify that you have the required
•
hardware to proceed with the
installation.
Desktop Installation
Verify that the area selected
•
meets the minimum
requirements.
Plan the installation location,
•
including required space
clearances and airflow
requirements.
Cables
Acquire cables and connectors.
•
Review the maximum distance
•
allowed for each cable. Choose
the length of cable based on the
distance between the hardware
components being connected.
Plan the cable routing and
•
management.
“Installing the SRX320 Services Gateway on a Wall” on page 45
“Installing the SRX320 Services Gateway on a Desk” on page 45
RELATED DOCUMENTATION
SRX320 Services Gateway General Site Guidelines | 31
Loading...