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.
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.
Troubleshooting the SRX5600 Services Gateway Power System | 395
Behavior of the SRX5400, SRX5600, and SRX5800 Services Gateways When the SRX5K-SCBE
and SRX5K-RE-1800X4 in a Chassis Cluster Fail | 401
Contacting Customer Support and Returning the Chassis or Components
Returning the SRX5600 Chassis or Components | 404
Contacting Customer Support | 404
Return Procedure for the SRX5600 Services Gateway | 405
Listing the SRX5600 Services Gateway Component Serial Numbers with the CLI | 406
xii
Locating the SRX5600 Services Gateway Chassis Serial Number Label | 407
Locating the SRX5600 Services Gateway Power Supply Serial Number Labels | 407
Locating the SRX5600 Services Gateway Craft Interface Serial Number Label | 408
Information You Might Need to Supply to JTAC | 409
Required Tools and Parts for Packing the SRX5600 Services Gateway | 409
Packing the SRX5600 Services Gateway for Shipment | 410
Packing SRX5600 Services Gateway Components for Shipment | 411
Safety and Compliance Information
General Safety Guidelines and Warnings | 414
Definitions of Safety Warning Levels | 415
Restricted Access Area Warning | 419
Fire Safety Requirements | 421
Fire Suppression | 421
Fire Suppression Equipment | 422
Qualified Personnel Warning | 423
Warning Statement for Norway and Sweden | 423
Installation Instructions Warning | 424
Chassis and Component Lifting Guidelines | 424
Ramp Warning | 425
Rack-Mounting and Cabinet-Mounting Warnings | 425
Grounded Equipment Warning | 431
Laser and LED Safety Guidelines and Warnings | 432
General Laser Safety Guidelines | 432
Class 1 Laser Product Warning | 433
Class 1 LED Product Warning | 434
Laser Beam Warning | 435
Radiation from Open Port Apertures Warning | 436
Maintenance and Operational Safety Guidelines and Warnings | 437
xiii
Battery Handling Warning | 438
Jewelry Removal Warning | 439
Lightning Activity Warning | 441
Operating Temperature Warning | 442
Product Disposal Warning | 444
General Electrical Safety Guidelines and Warnings | 445
Prevention of Electrostatic Discharge Damage | 446
AC Power Electrical Safety Guidelines | 447
AC Power Disconnection Warning | 449
DC Power Electrical Safety Guidelines | 450
DC Power Electrical Safety Guidelines | 450
DC Power Disconnection Warning | 452
DC Power Grounding Requirements and Warning | 454
DC Power Wiring Sequence Warning | 456
DC Power Wiring Terminations Warning | 459
DC Power Disconnection Warning | 462
DC Power Grounding Requirements and Warning | 464
DC Power Wiring Sequence Warning | 466
DC Power Wiring Terminations Warning | 469
Multiple Power Supplies Disconnection Warning | 472
TN Power Warning | 473
Action to Take After an Electrical Accident | 473
SRX5600 Services Gateway Agency Approvals | 474
SRX5600 Services Gateway Compliance Statements for EMC Requirements | 475
Canada | 475
European Community | 475
Israel | 476
Japan | 476
United States | 476
xiv
Statements of Volatility for Juniper Network Devices | 477
About the Documentation
IN THIS SECTION
Documentation and Release Notes | xv
Using the Examples in This Manual | xv
Documentation Conventions | xvii
Documentation Feedback | xx
Requesting Technical Support | xx
Use this guide to install hardware and perform initial software configuration, routine maintenance, and
troubleshooting for the SRX5600 Services Gateway.
xv
After completing the installation and basic configuration procedures covered in this guide, refer to the
Junos OS documentation for information about further software configuration.
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;
}
}
}
}
xvi
2. Merge the contents of the file into your routing platform configuration by issuing the load merge
configuration mode command:
1. From the HTML or PDF version of the manual, copy a configuration snippet into a text file, save the
file with a name, and copy the file to a directory on your routing platform.
For example, copy the following snippet to a file and name the file ex-script-snippet.conf. Copy the
ex-script-snippet.conf file to the /var/tmp directory on your routing platform.
commit {
file ex-script-snippet.xsl; }
2. Move to the hierarchy level that is relevant for this snippet by issuing the following configuration mode
command:
[edit]
user@host# edit system scripts
[edit system scripts]
xvii
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 xviii defines notice icons used in this guide.
Table 1: Notice Icons
xviii
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 xviii 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)
xix
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)
xx
ExamplesDescriptionConvention
Bold text like this
> (bold right angle bracket)
Represents graphical user interface
(GUI) items you click or select.
Separates levels in a hierarchy of
menu selections.
In the Logical Interfaces box, select
•
All Interfaces.
To cancel the configuration, click
•
Cancel.
In the configuration editor hierarchy,
select Protocols>Ospf.
Documentation Feedback
We encourage you to provide feedback so that we can improve our documentation. You can use either
of the following methods:
Online feedback system—Click TechLibrary Feedback, on the lower right of any page on the Juniper
•
Networks TechLibrary site, and do one of the following:
Click the thumbs-up icon if the information on the page was helpful to you.
•
Click the thumbs-down icon if the information on the page was not helpful to you or if you have
•
suggestions for improvement, and use the pop-up form to provide feedback.
E-mail—Send your comments to techpubs-comments@juniper.net. Include the document or topic name,
•
URL or page number, and software version (if applicable).
Requesting Technical Support
Technical product support is available through the Juniper Networks Technical Assistance Center (JTAC).
If you are a customer with an active Juniper Care or Partner Support Services support contract, or are
covered under warranty, and need post-sales technical support, you can access our tools and resources
online or open a case with JTAC.
JTAC policies—For a complete understanding of our JTAC procedures and policies, review the JTAC User
•
Guide located at https://www.juniper.net/us/en/local/pdf/resource-guides/7100059-en.pdf.
JTAC hours of operation—The JTAC centers have resources available 24 hours a day, 7 days a week,
•
365 days a year.
Self-Help Online Tools and Resources
For quick and easy problem resolution, Juniper Networks has designed an online self-service portal called
the Customer Support Center (CSC) that provides you with the following features:
The SRX5600 Services Gateway is a high-performance, highly scalable, carrier-class security device with
multi-processor architecture.
The SRX5600 Services Gateway is 8 rack units (U) tall. Three of these devices can be stacked in a single
floor-to-ceiling rack, for increased port density per unit of floor space.
The services gateway provides eight slots that you can populate with two Switch Control Boards (SCBs)
and six other cards of the following types:
Services Processing Cards (SPCs) provide the processing capacity to run integrated services such as
•
firewall, IPsec, and IDP.
Modular PIC Concentrators (MPCs) provide Ethernet interfaces that connect the services gateway to
•
your network.
I/O cards (IOCs) provide Ethernet interfaces that connect the services gateway to your network.
•
Flex IOCs are similar to IOCs, but have slots for port modules that allow you greater flexibility in adding
•
different types of Ethernet ports to your services gateway.
For detailed information about the cards supported by the services gateway, see the SRX5400, SRX5600,
and SRX5800 Services Gateway Card Reference at www.juniper.net/documentation/.
Benefits of the SRX5600 Services Gateway
The next generation SPCs and IOCs on the SRX5600 Services Gateway support up to 570 IMIX Gbps
•
firewall throughput, 180 million concurrent sessions, and 460 Gbps IPS.
The ability to support unique security policies per zone and ability to scale with the growth of the network
infrastructure, makes the SRX5600 an ideal deployment for consolidation of services in large enterprise,
service provider, or mobile operator environments.
IPS Capabilities - Juniper Networks IPS capabilities offer several unique features such as Protocol decodes,
•
Zero-day protection, Active/active traffic monitoring, and packet capture logging per rule assure the
highest level of network security.
Content Security UTM Capabilities - The UTM services offered on the SRX5000 line of Services Gateways
•
include industry-leading antivirus, antispam, content filtering, and additional content security services.
The UTM services provide sophisticated protection from:
Antivirus experts against malware attacks that can lead to data breaches and lost productivity.
•
Advanced persistent threats perpetrated through social networking attacks and the latest phishing
•
scams with sophisticated e-mail filtering and content blockers.
24
Lost productivity and the impact of malicious URLs and extraneous or malicious content on the network
•
to help maintain bandwidth.
Advanced Threat Prevention (ATP) - Juniper Sky ATP, a SaaS-based service, and the Juniper ATP
•
Appliance, an on-premises solution:
Protects enterprise users from a spectrum of advanced malware that exploits “zero-day” vulnerabilities.
•
Proactively blocks malware communication channels.
•
The Juniper ATP Appliance includes support for cloud-based e-mail services such as Office 365 and
•
Google Mail, and detects threats in SMB traffic.
Single pane-of-glass management with Security Director and JSA Series integration.
•
SRX5600 Services Gateway FRUs
Field-replaceable units (FRUs) are services gateway components that can be replaced at the customer site.
The services gateway uses the following types of FRUs:
Table 3 on page 25 lists the FRUs of the services gateway and the action to perform to install, remove, or
replace an FRU.
Table 3: Field-Replaceable Units
25
ActionField-Replaceable Units (FRUs)
Air filter
Fan tray
Craft interface
AC and DC power supplies (if redundant)
SFP and XFP transceivers
IOCs
Flex IOCs
Port modules of the Flex IOCs
Routing Engine
SCBs
SPCs
You need not power off the services gateway to install, remove, or
replace any of these FRUs.
Power off the services gateway to install, remove, or replace any of
these FRUs.
MPCs
MICs
SRX5600 Services Gateway Component Redundancy
The following major hardware components are redundant:
SCBs—The host subsystem consists of a Routing Engine installed in an SCB. The device must have one
•
host subsystem installed. You can install a second SCB for redundancy. If a second SCB is installed, the
host subsystem SCB functions as the primary and the other functions as the backup. If the SCB of the
host subsystem fails, the other SCB takes over as the primary.
Power supplies—In the low-line (110 V) AC power configuration, the device contains three or four AC
•
power supplies, located horizontally at the rear of the chassis in slots PEM0 through PEM3 (left to right).
Each AC power supply provides power to all components in the device. When three power supplies are
present, they share power almost equally within a fully populated system. Four AC power supplies
provide full power redundancy. If one power supply fails or is removed, the remaining power supplies
instantly assume the entire electrical load without interruption. Three power supplies provide the
maximum configuration with full power for as long as the device is operational.
In the high-line (220 V) AC power configuration, the device contains two or four AC power supplies
located horizontally at the rear of the chassis in slots PEM0 through PEM3 (left to right). Each AC power
supply provides power to all components in the device. When two or more power supplies are present,
they share power almost equally within a fully populated system. Four AC power supplies provide full
power redundancy. If one power supply fails or is removed, the remaining power supplies instantly
assume the entire electrical load without interruption. Two power supplies provide the maximum
configuration with full power for as long as the device is operational.
In the DC configuration, two power supplies are required to supply power to a fully configured device.
One power supply supports approximately half of the components in the device, and the other power
supply supports the remaining components. The addition of two power supplies provides full power
redundancy. If one power supply fails or is removed, the remaining power supplies instantly assume the
entire electrical load without interruption. Two power supplies provide the maximum configuration with
full power for as long as the device is operational.
26
Cooling system—The cooling system has redundant components, which are controlled by the host
•
subsystem. If one of the fans fails, the host subsystem increases the speed of the remaining fans to
provide sufficient cooling for the services gateway indefinitely.
The services gateway chassis is a rigid sheet metal structure that houses all the other components (see
Figure 1 on page 28, Figure 2 on page 28, and Figure 3 on page 29). The chassis measures 14.0 in. (35.6 cm)
high, 17.45 in. (44.3 cm) wide, and 24.5 in. (62.2 cm) deep (from the front to the rear of the chassis). The
chassis installs in standard 800-mm (or larger) enclosed cabinets, 19-in. equipment racks, or telco open-frame
racks. Up to five services gateways can be installed in one standard (48 U) rack if the rack can handle their
combined weight, which can be greater than 1100 lb (500 kg). See “SRX5600 Services Gateway Physical
Specifications” on page 29 for physical specifications for the SRX5600 Services Gateway.
27
CAUTION: Before removing or installing components of a services gateway, attach
an ESD strap to an ESD point and place the other end of the strap around your bare
wrist. Failure to use an ESD strap can result in damage to the services gateway.
WARNING: The services gateway must be connected to earth ground during normal
operation.
Figure 1: Front View of a Fully Configured Services Gateway Chassis
STATUS
SPU0
SERVICE
STATUS
SPU1
SERVICE
HA
OK/FAIL
CHASSISCLUSTERCONTROL0
ENABLE
LINK/ACT
CHASSISCLUSTERCONTROL1
ENABLE
LINK/ACT
STATUS
SPU0
SERVICE
STATUS
SPU1
SERVICE
HA
OK/FAIL
CHASSISCLUSTERCONTROL0
ENABLE
LINK/ACT
CHASSISCLUSTERCONTROL1
ENABLE
LINK/ACT
SPCs
g030218
IOCs
28
Figure 2: Rear View of a Fully Configured AC-Powered Services Gateway Chassis
Figure 3: Rear View of a Fully Configured DC-Powered Services Gateway Chassis
29
SRX5600 Services Gateway Physical Specifications
Table 4 on page 29 summarizes the physical specifications for the services gateway chassis.
Table 4: Physical Specifications
ValueDescription
Chassis dimensions
Services Gateway weight
14.0 in. (35.6 cm) high
17.45 in. (44.3 cm) wide
24.5 in. (62.2 cm) deep (from front-mounting bracket to
chassis rear)
Total depth (including cable management system):
27.75 in. (70.5 cm)
Chassis with midplane, fan tray, air filter, and cable
management system: 65.5 lb (29.7 kg)
Maximum configuration: 220 lb (100 kg)
Routing Engine weight
SRX5K-RE-13-20: 2.4 lb (1.1 kg)
SRX5K-RE-1800X4: 2.4 lb (1.1 kg)
Table 4: Physical Specifications (continued)
30
ValueDescription
SCB weight
supported on devices with SRX5K-SCB and
SRX5K-RE-13-20)
SRX5K-SCB: 9.6 lb (4.4 kg)
SRX5K-SCBE: 9.6 lb (4.4 kg)
SRX5K-SCB3: 10.14 lb (4.6 kg)
13.1 lb (5.9 kg)MPC weight (with two MICs)
13.1 lb (5.9 kg)IOC weight
1.1 lb (0.5 kg)Craft interface weight
4.2 lb (1.9 kg)Fan tray weight
1.0 lb (0.5 kg)Air filter weight
0.3 lb (0.14 kg)Cable management weight
3.8 lb (1.7 kg)Standard-capacity DC power supply weight (only
6.2 lb (2.8 kg)High-capacity DC power supply weight
5.0 lb (2.3 kg)Standard-capacity AC power supply weight (only
supported on devices with SRX5K-SCB and
SRX5K-RE-13-20)
6.6 lb (3.0 kg)High-capacity AC power supply weight
SRX5600 Services Gateway Midplane Description
The midplane is located toward the rear of the chassis and forms the rear of the card cage (see
Figure 4 on page 31). IOCs, Flex IOCs, SPCs, and SCBs install into the midplane from the front of the
chassis, and the power supplies install into the midplane from the rear of the chassis. The cooling system
components also connect to the midplane.
Loading...
+ 449 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.