SRX320ServicesGatewayHardwareGuide
Published
2020-11-10
ii
Juniper Networks, Inc. 1133 Innovation Way Sunnyvale, California 94089 USA
408-745-2000 www.juniper.net
JuniperNetworks,theJuniperNetworkslogo,Juniper,andJunosareregisteredtrademarksofJuniperNetworks,Inc. in theUnitedStatesandothercountries. Allothertrademarks,servicemarks,registeredmarks,orregisteredservicemarks 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.
SRX320ServicesGatewayHardwareGuide
Copyright © 2020 Juniper Networks, Inc. All rights reserved.
The information in this document is current as of the date on the title page.
YEAR2000NOTICE
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.
ENDUSERLICENSEAGREEMENT
TheJuniperNetworksproductthatisthesubjectofthistechnicaldocumentationconsistsof(orisintendedforusewith) JuniperNetworkssoftware.UseofsuchsoftwareissubjecttothetermsandconditionsoftheEndUserLicenseAgreement (“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.
iii
AbouttheDocumentation | 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
1Overview
SRX320ServicesGatewayOverview | 16
SRX320 Services Gateway Description | 16
SRX320 Services Gateway Field Replaceable Units Overview | 17
Benefits of the SRX320 Services Gateway | 17
SRX320Chassis | 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
SRX320CoolingSystem | 23
SRX320PowerSystem | 24
Understanding the SRX320 Services Gateway Power Supply | 25
SRX320 Services Gateway Power Specifications and Requirements | 25
Power Cord Specifications for SRX320 | 26
iv
2SitePlanning,Preparation,andSpecifications
SRX320SitePreparationChecklist | 29
SRX320SiteGuidelinesandRequirements | 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
SRX320TransceiverSpecificationsandPinouts | 37
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
3InitialInstallationandConfiguration
SRX320InstallationOverview | 41
SRX320 Services Gateway Installation Overview | 41
SRX320 Services Gateway Autoinstallation Overview | 41
UnpackingandMountingtheSRX320 | 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
ConnectingtheSRX320toPower | 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
v
Powering On the SRX320 Services Gateway | 55
Powering Off the SRX320 Services Gateway | 56
ConnectingtheSRX320ServicesGatewaytoaManagementConsole | 57
ConfiguringJunosOSontheSRX320 | 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
Customize the Configuration for Junos OS Release 15.1X49-D170 | 67
Configure the Device Using ZTP with Juniper Networks Network Service Controller | 68
4MaintainingComponents
MaintainingtheSRX320Components | 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
5TroubleshootingHardware
TroubleshootingtheSRX320 | 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
vi
6ContactingCustomerSupportandReturningtheChassisorComponents
ReturningtheSRX320ChassisorComponents | 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
7SafetyandComplianceInformation
DefinitionsofSafetyWarningLevels | 87
GeneralSafetyGuidelinesandWarnings | 90
RestrictedAccessWarning | 92
QualifiedPersonnelWarning | 95
PreventionofElectrostaticDischargeDamage | 95
FireSafetyRequirements | 97
Fire Suppression | 97
Fire Suppression Equipment | 97
LaserandLEDSafetyGuidelinesandWarnings | 98
General Laser Safety Guidelines | 98
Class 1 Laser Product Warning | 99
Class 1 LED Product Warning | 100
Laser Beam Warning | 101
RadiationfromOpenPortAperturesWarning | 102
MaintenanceandOperationalSafetyGuidelinesandWarnings | 103
Battery Handling Warning | 104
Jewelry Removal Warning | 105
Lightning Activity Warning | 107
vii
Operating Temperature Warning | 108
Product Disposal Warning | 110
ActiontoTakeAfteranElectricalAccident | 111
GeneralElectricalSafetyGuidelinesandWarnings | 111
SRX320ServicesGatewayAgencyApprovals | 112
SRX320ServicesGatewayAcousticNoiseComplianceStatements | 113
SRX320ServicesGatewayEMCRequirements | 114
Canada | 114
European Community | 114
Israel | 114
Japan | 114
United States | 115
viii
AbouttheDocumentation
INTHISSECTION
Documentation Conventions | x
Documentation Feedback | xiii
Requesting Technical Support | xiii
Use this guide to install hardware and perform initial software configuration, routine maintenance, and troubleshootingfortheSRX320ServicesGateway.Aftercompletingtheinstallationandbasicconfiguration procedures covered in this guide, refer to the Junos OS documentation for information about further software configuration.
DocumentationandReleaseNotes
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/.
Iftheinformationinthelatestreleasenotesdiffersfromtheinformationinthedocumentation,followthe 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.
UsingtheExamplesinThisManual
If you want to use the examples in this manual, you can use the loadmerge or the loadmergerelative command. These commands cause the software to merge the incoming configuration into the current candidateconfiguration.Theexampledoesnotbecomeactiveuntilyoucommitthecandidateconfiguration.
ix
If the example configuration contains the top level of the hierarchy (or multiple hierarchies), the example is a fullexample. In this case, use the loadmerge command.
If the example configuration does not start at the top level of the hierarchy, the example is a snippet. In thiscase,usetheloadmergerelative command.Theseproceduresaredescribedinthefollowingsections.
MergingaFullExample
To merge a full example, follow these steps:
1.From the HTML or PDF version of the manual, copy a configuration example into a text file, save the file with a name, and copy the file to a directory on your routing platform.
For example, copy the following configuration to a file and name the file ex-script.conf. Copy the ex-script.conf file to the /var/tmp directory on your routing platform.
system { scripts {
commit {
file ex-script.xsl;
}
}
}
interfaces { fxp0 {
disable; unit 0 {
family inet {
address 10.0.0.1/24;
}
}
}
}
2.Merge the contents of the file into your routing platform configuration by issuing the loadmerge configuration mode command:
[edit]
user@host# loadmerge/var/tmp/ex-script.conf load complete
x
MergingaSnippet
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.Movetothehierarchylevelthatisrelevantforthissnippetbyissuingthefollowingconfigurationmode command:
[edit]
user@host# editsystemscripts
[edit system scripts]
3.Merge the contents of the file into your routing platform configuration by issuing the loadmerge relative configuration mode command:
[edit system scripts]
user@host# loadmergerelative/var/tmp/ex-script-snippet.conf load complete
For more information about the load command, see CLI Explorer.
DocumentationConventions
Table 1 on page xi defines notice icons used in this guide.
xi
Table1:NoticeIcons |
|
|
Icon |
Meaning |
Description |
|
Informational note |
Indicates important features or instructions. |
|
Caution |
Indicates a situation that might result in loss of data or hardware |
|
|
damage. |
|
Warning |
Alerts you to the risk of personal injury or death. |
|
Laser warning |
Alerts you to the risk of personal injury from a laser. |
|
Tip |
Indicates helpful information. |
|
Best practice |
Alerts you to a recommended use or implementation. |
Table 2 on page xi defines the text and syntax conventions used in this guide.
Table2:TextandSyntaxConventions
Convention |
Description |
Examples |
Boldtextlikethis |
Represents text that you type. |
To enter configuration mode, type |
|
|
the configure command: |
|
|
user@host> configure |
Fixed-width text like this
Italictextlikethis
Represents output that appears on the terminal screen.
•Introducesoremphasizesimportant new terms.
•Identifies guide names.
•Identifies RFC and Internet draft titles.
user@host> showchassisalarms
No alarms currently active
•A policy term is a named structure that defines match conditions and actions.
•JunosOSCLIUserGuide
•RFC 1997, BGPCommunities Attribute
xii
Table2:TextandSyntaxConventions (continued)
Convention |
Description |
Italictextlikethis |
Represents variables (options for |
|
which you substitute a value) in |
|
commands or configuration |
|
statements. |
Examples
Configure the machine’s domain name:
[edit]
root@# setsystemdomain-name domain-name
Textlikethis |
Represents names of configuration |
|
statements, commands, files, and |
|
directories; configuration hierarchy |
|
levels; or labels on routing platform |
|
components. |
•To configure a stub area, include the stub statement at the [edit protocolsospfareaarea-id] hierarchy level.
•The console port is labeled
CONSOLE.
< > (angle brackets) |
Encloses optional keywords or |
|
variables. |
| (pipe symbol) |
Indicates a choice between the |
|
mutually exclusive keywords or |
|
variablesoneithersideofthesymbol. |
|
The set of choices is often enclosed |
|
in parentheses for clarity. |
stub<default-metric metric>;
broadcast|multicast
(string1 | string2 | string3)
# (pound sign)
[ ] (square brackets)
Indention and braces ( { } )
; (semicolon)
Indicatesacommentspecifiedonthe |
rsvp{#RequiredfordynamicMPLS |
same line as the configuration |
only |
statement to which it applies. |
|
Enclosesavariableforwhichyoucan |
communitynamemembers[ |
substitute one or more values. |
community-ids ] |
Identifies a level in the configuration |
[edit] |
hierarchy. |
routing-options { |
|
static { |
Identifies a leaf statement at a |
route default { |
configuration hierarchy level. |
nexthop address; |
|
retain; |
|
} |
|
} |
|
} |
GUIConventions
xiii
Table2:TextandSyntaxConventions (continued) |
|
|
Convention |
Description |
Examples |
Boldtextlikethis |
Represents graphical user interface |
• IntheLogicalInterfacesbox,select |
|
(GUI) items you click or select. |
AllInterfaces. |
|
|
• To cancel the configuration, click |
|
|
Cancel. |
> (bold right angle bracket) |
Separates levels in a hierarchy of |
Intheconfigurationeditorhierarchy, |
|
menu selections. |
select Protocols>Ospf. |
DocumentationFeedback
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—Sendyourcommentstotechpubs-comments@juniper.net.Includethedocumentortopicname, URL or page number, and software version (if applicable).
RequestingTechnicalSupport
TechnicalproductsupportisavailablethroughtheJuniperNetworksTechnicalAssistanceCenter(JTAC). If you are a customer with an active Juniper Care or Partner Support Services support contract, or are
xiv
covered under warranty, and need post-sales technical support, you can access our tools and resources online or open a case with JTAC.
•JTACpolicies—ForacompleteunderstandingofourJTACproceduresandpolicies,reviewtheJTACUser Guide located at https://www.juniper.net/us/en/local/pdf/resource-guides/7100059-en.pdf.
•Productwarranties—Forproductwarrantyinformation,visithttps://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-HelpOnlineToolsandResources
Forquickandeasyproblemresolution,JuniperNetworkshasdesignedanonlineself-serviceportalcalled the Customer Support Center (CSC) that provides you with the following features:
•Find CSC offerings: https://www.juniper.net/customers/support/
•Search for known bugs: https://prsearch.juniper.net/
•Find product documentation: https://www.juniper.net/documentation/
•Find solutions and answer questions using our Knowledge Base: https://kb.juniper.net/
•Download the latest versions of software and review release notes: https://www.juniper.net/customers/csc/software/
•Search technical bulletins for relevant hardware and software notifications: https://kb.juniper.net/InfoCenter/
•Join and participate in the Juniper Networks Community Forum: https://www.juniper.net/company/communities/
•Create a service request online: https://myjuniper.juniper.net
To verify service entitlement by product serial number, use our Serial Number Entitlement (SNE) Tool: https://entitlementsearch.juniper.net/entitlementsearch/
CreatingaServiceRequestwithJTAC
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
SRX320 Services Gateway Overview | 16
SRX320 Chassis | 18
SRX320 Cooling System | 23
SRX320 Power System | 24
16
SRX320ServicesGatewayOverview
INTHISSECTION
SRX320 Services Gateway Field Replaceable Units Overview | 17
Benefits of the SRX320 Services Gateway | 17
SRX320ServicesGatewayDescription
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.
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.
17
SRX320ServicesGatewayFieldReplaceableUnitsOverview
Field-replaceableunits(FRUs)arecomponentsthatyoucanreplaceatyoursite.TheMini-PhysicalInterface 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
BenefitsoftheSRX320ServicesGateway
•Highperformance—TheSRX320supportsupto1-Gbpsfirewalland300-MbpsIPsecVPN,andissuited for small distributed enterprise branch office deployments.
•Simplifieddeploymentwithminimalmanualintervention—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.
•MultipleWANconnectivityoptions—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.
•Threatprotection—The SRX300 line supports IPsec VPN, Media Access Control Security (MACsec), JuniperSkyAdvancedThreatPrevention,andTrustedPlatformModule(TPM)toprotectagainstpotential vulnerabilities.
RELATED DOCUMENTATION
SRX320 Installation Overview | 41
18
SRX320Chassis
INTHISSECTION
SRX320 Services Gateway Back Panel | 21
SRX320 Services Gateway Interface Modules Overview | 23
SRX320ServicesGatewayChassisOverview
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: Beforeremovingorinstallingcomponentsofafunctioningservicesgateway, attach an electrostatic discharge (ESD) strap to an ESD point and place the other end ofthestraparoundyourbarewrist.FailuretouseanESDstrapcouldresultindamage to the device.
Theservicesgatewaymustbeconnectedtoearthgroundduringnormaloperation.Theprotectiveearthing terminal on the rear of the chassis is provided to connect the services gateway to ground.
SRX320ServicesGatewayFrontPanel
Figure 1 on page 19 shows the front panel of the SRX320 Services Gateway.
19
Figure1:SRX320ServicesGatewayFrontPanel
Table 3 on page 19 provides details about the front panel components.
Table3:SRX320ServicesGatewayFrontPanelComponents
Number |
Component |
Description |
1 |
Reset Config button |
Returnstheservicesgatewaytotherescueconfiguration |
|
|
or the factory-default configuration. |
2,6 |
Console port |
• 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 |
|
|
acceptsaMini-BtypeUSBcableplug.AUSBcablewith |
|
|
Mini-B and Type A USB plugs is supplied with the |
|
|
services gateway. |
|
|
Tousethemini-USBconsoleport,youmustdownload |
|
|
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. |
3 |
Mini-PIM slots |
Two slots for Mini-PIMs. Mini-PIMs can be used to |
|
|
provide LAN and WAN functionality along with |
|
|
connectivity to various media types. |
4 |
1-GbE small form-factor pluggable |
Two 1-GbE MACsec-capable ports for network traffic. |
|
(SFP) ports |
|
20
Table3:SRX320ServicesGatewayFrontPanelComponents (continued)
Number |
Component |
Description |
5 |
1-GbE RJ-45 ports |
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 |
|
|
• ProvideLANandWANconnectivitytohubs,switches, |
|
|
local servers, and workstations |
|
|
• Forwardincomingdatapacketstotheservicesgateway |
|
|
• Receive outgoing data packets from the services |
|
|
gateway |
7 |
USB port |
The services gateway has one USB port that accepts a |
|
|
USB storage device. |
8 |
LEDs |
Indicate component and system status at a glance. |
9 |
Power button |
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.
Figure2:SRX320ServicesGatewayFrontPanelLEDs
Table 4 on page 21 lists the front panel LEDs.
21
Table4:SRX320ServicesGatewayFrontPanelLEDs |
|
Component |
Description |
ALARM |
• Solid amber (noncritical alarm) |
|
• Solid red (critical alarm) |
|
• Off (no alarms) |
STAT |
• Solid green (operating normally) |
|
• Solid red (error detected) |
PWR |
• Solid green (receiving power) |
|
• Solid red (power failure) |
|
• Off (no power) |
HA |
• 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) |
mPIM0 and mPIM1 |
• 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) |
NetworkPortLEDs
The SFP and Ethernet ports have two status LEDs, LINK and ACT, located above the port.
Table5:NetworkPortLEDs
LED
LINK (LED on the left)
ACT (LED on the right)
Description
•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.
SRX320ServicesGatewayBackPanel
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.
22
Figure3:SRX320ServicesGatewayBackPanel
Table6:SRX320ServicesGatewayBackPanelComponents |
|
|
Number |
Component |
Description |
1 |
Lock |
Provides the capability to lock and |
|
|
securethedeviceattheinstallation |
|
|
site. |
2 |
Fans |
Keeps all the services gateway |
|
|
componentswithintheacceptable |
|
|
temperature range. |
3 |
Cable tie holder |
Secures the DC power cord |
|
|
connection to the adapter. |
4 |
Powersupplyinput(DCpowerinput) |
Connects the services gateway to |
|
|
the external power supply. |
5 |
Grounding point |
Connects the services gateway |
|
|
chassis to earth ground (optional). |
NOTE: Werecommendconnecting the services gateway to ground if required.
23
SRX320ServicesGatewayInterfaceModulesOverview
Mini-PhysicalInterfaceModules(Mini-PIMs)arefield-replaceablenetworkinterfacecards(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)
•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-FiMini-PhysicalInterfaceModule(SRX-MP-WLAN-US,SRX-MP-WLAN-IL,andSRX-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
SRX320CoolingSystem
The cooling system for the SRX320 Services Gateway includes two fixed fans. The fans draw air through ventsonthefrontofthechassisandexhausttheairthroughthebackofthechassis.Theairflowproduced by the fans keeps device components within the acceptable temperature range.
Figure 4 on page 24 shows the airflow through the chassis.
24
Figure4:AirflowThroughtheSRX320ServicesGatewayChassis
RELATED DOCUMENTATION
SRX320 Services Gateway Clearance Requirements for Airflow and Hardware Maintenance | 35
SRX320PowerSystem
INTHISSECTION
Understanding the SRX320 Services Gateway Power Supply | 25
SRX320 Services Gateway Power Specifications and Requirements | 25
Power Cord Specifications for SRX320 | 26
25
UnderstandingtheSRX320ServicesGatewayPowerSupply
ThepowersupplyfortheSRX320ServicesGatewayisexternal.Youmustusethefollowingpowersupply adapters provided by Juniper Networks to provide power to the services gateway.
• 75 W, 12 V power supply adapter for non-PoE models
Figure5:75W,12VPowerSupplyAdapter
<![if ! IE]><![endif]>g022478
• 280 W, 54 V power supply adapter for PoE models
Figure6:280W,54VPowerSupplyAdapter
<![if ! IE]><![endif]>g022479
EachPoEportdeliversamaximumpowerof30W. Becauseoflineloss,thepowereddeviceconnected 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.
SRX320ServicesGatewayPowerSpecificationsandRequirements
Table7onpage25liststhepowerspecificationsfortheSRX320ServicesGatewaypowersupplyadapter.
Table7:PowerSpecificationsfortheSRX320ServicesGatewayPowerSupplyAdapter
|
Specifications |
|
Power Supply Adapter |
|
|
Requirement |
Non-PoE model |
PoE model |
AC input |
100 to 240 VAC |
100 to 240 VAC |
AC input line frequency |
50 to 60 Hz |
50 to 60 Hz |
26
Table7:PowerSpecificationsfortheSRX320ServicesGatewayPowerSupplyAdapter (continued)
|
Specifications |
|
Power Supply Adapter |
|
|
Requirement |
Non-PoE model |
PoE model |
AC system current rating |
1.3 A maximum |
Maximum AC inrush current |
11 A at 220 V/50 Hz (with two |
|
Mini-PIMs installed) |
3.25 A maximum
15 A at 220 V/50 Hz (with two Mini-PIMs installed)
WARNING: TheACpowercordfortheservicesgatewayisintendedforusewithonly the power supply adapter provided with the device.
SEE ALSO
SRX320 Services Gateway Electrical Wiring Guidelines | 32
PowerCordSpecificationsforSRX320
Adetachablepowercordissuppliedwiththedevice.ThecoupleristypeC13asdescribedbyInternational 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: InNorthAmerica,ACpowercordsmustnotexceed4.5meters(approximately14.75feet) in length, to comply with National Electrical Code (NEC) Sections 400-8 (NFPA 75, 5-2.2) and 210-52andCanadianElectricalCode(CEC)Section4-010(3).Thecordssuppliedwiththedevice are in compliance.
Table8onpage26 liststheACpowercordspecificationsforthecountriesandregionslistedinthetable.
Table8:ACPowerCordSpecifications
Country/Region |
Electrical Specifications |
Plug Standards |
Juniper Model Number |
Australia |
250 VAC, 10 A, 50 Hz |
AS/NZZS 3112 Type |
CBL-JX-PWR-AU |
|
|
SAA/3 |
|
27
Table8:ACPowerCordSpecifications (continued) |
|
|
|
Country/Region |
Electrical Specifications |
Plug Standards |
Juniper Model Number |
China |
250 VAC, 10 A, 50 Hz |
GB1002-1996TypePRC/3 |
CBL-JX-PWR-CH |
Europe (except Italy, |
250 VAC, 10 A, 50 Hz |
CEE (7) VII Type VIIG |
CBL-JX-PWR-EU |
Switzerland, and United |
|
|
|
Kingdom) |
|
|
|
India |
250 VAC, 10 A, 50 Hz |
IS 1293 Type IND/3 |
CBL-EX-PWR-C13-IN |
Italy |
250 VAC, 10 A, 50 Hz |
CEI 23-16 Type I/3G |
CBL-JX-PWR-IT |
Japan |
125VAC,12A,50Hzor60 |
SS-00259 Type VCTF |
CBL-JX-PWR-JP |
|
Hz |
|
|
Korea |
250VAC,10A,50Hzor60 |
CEE (7) VII Type VIIGK |
CBL-JX-PWR-KR |
|
Hz |
|
|
Switzerland |
250 VAC, 10 A, 50 Hz |
SEV 6534-2 Type 12G |
CBL-EX-PWR-C13-SZ |
United Kingdom |
250 VAC, 10 A, 50 Hz |
BS 1363/A Type BS89/13 |
CBL-JX-PWR-UK |
United States |
125 VAC, 13 A, 60 Hz |
NEMA 5-15 Type N5-15 |
CBL-JX-PWR-US |
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.
Figure7:ACPlugTypes
2
CHAPTER
Site Planning, Preparation, and
Specifications
SRX320 Site Preparation Checklist | 29
SRX320 Site Guidelines and Requirements | 31
SRX320 Transceiver Specifications and Pinouts | 37
29
SRX320SitePreparationChecklist
Table 9 on page 29 provides a checklist of tasks you need to perform when preparing a site for installing the SRX320 Services Gateway.
Table9:SitePreparationChecklistforSRX320ServicesGatewayInstallation
Item or Task |
Additional Information |
Environment
Verify that environmental factors such as temperature and humidity do not exceed device tolerances.
Power
•Measure the distance between the external power sources and the device installation site.
•Locate sites for connection of system grounding.
•Calculatethepowerconsumption and requirements.
Rack Requirements
Verify that your rack meets the minimum requirements.
Rack Installation
•Plan the rack location, including required space clearances.
•Secure the rack to the floor and building structure.
Cabinet Requirements
•Verify that your cabinet meets the minimum requirements.
•Plan the cabinet location, including required space clearances.
“SRX320 Services Gateway Environmental Specifications” on page 31
“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 31
“Installing the SRX320 Services Gateway in a Rack” on page 48
“SRX320 Site Guidelines and Requirements” on page 31
30
Table9:SitePreparationChecklistforSRX320ServicesGatewayInstallation (continued)
Item or Task |
Additional Information |
Wall Installation |
|
• Verify that the area selected |
“Installing the SRX320 Services Gateway on a Wall” on page 45 |
meets the minimum |
|
requirements. |
|
•Verifythatyouhavetherequired hardware to proceed with the installation.
Desktop Installation |
|
• Verify that the area selected |
“Installing the SRX320 Services Gateway on a Desk” on page 45 |
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.
RELATED DOCUMENTATION
SRX320 Services Gateway General Site Guidelines | 31