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.
Table of Contents
1
About the Documentation | x
Documentation and Release Notes | x
Using the Examples in This Manual | x
Merging a Full Example | xi
Merging a Snippet | xii
Documentation Conventions | xii
Documentation Feedback | xv
Requesting Technical Support | xv
Self-Help Online Tools and Resources | xvi
Creating a Service Request with JTAC | xvi
iii
Overview
System Overview | 2
SRX550 Services Gateway Description | 2
SRX550 Services Gateway Hardware Features | 3
SRX550 Services Gateway Software Features and Licenses | 4
SRX550 Services Gateway Compliance Statements for EMC Requirements | 202
Canada | 202
European Community | 202
Israel | 202
Japan | 203
United States | 203
SRX550 Services Gateway Compliance Statements for NEBS | 203
Lithium Battery | 204
ix
About the Documentation
IN THIS SECTION
Documentation and Release Notes | x
Using the Examples in This Manual | x
Documentation Conventions | xii
Documentation Feedback | xv
Requesting Technical Support | xv
Use this guide to install hardware and perform initial software configuration, routine maintenance, and
troubleshooting for the SRX550 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.
x
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;
}
}
}
}
xi
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]
xii
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 xiii defines notice icons used in this guide.
Table 1: Notice Icons
xiii
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 xiii 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)
xiv
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)
xv
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:
SRX550 Services Gateway Software Features and Licenses | 4
SRX550 Services Gateway Power over Ethernet | 9
Accessing the SRX550 Services Gateway | 11
2
SRX550 Services Gateway Description
The SRX550 Services Gateway is a mid-range dynamic services gateway that consolidates network
infrastructure and security applications for regional offices, large branch offices, and small to medium
enterprises. The services gateway provides cost-effective, scalable integration of routing, security, and
other mid-range applications for these sites.
The SRX550 Services Gateway has a modular 2U chassis that fits a 19-inch rack with a depth of
approximately 18.1 inches.
Figure 1 on page 3 shows the SRX550 Services Gateway.
Figure 1: SRX550 Services Gateway
g034102
RELATED DOCUMENTATION
3
SRX550 Services Gateway Chassis | 14
Accessing the SRX550 Services Gateway | 11
SRX550 Services Gateway Software Features and Licenses | 4
SRX550 Services Gateway Hardware Features
The SRX550 Services Gateway provides the following features:
Symmetric Multiprocessing-based data forwarding.
•
Hardware-based control and data plane separation.
•
Six on-board 10/100/1000Base-T Gigabit Ethernet ports.
•
Four on-board SFP Gigabit Ethernet ports.
•
Support for dual AC or dual DC power supplies with a redundant configuration in the chassis. 645 W
•
AC and DC power supplies with or without Power over Ethernet (PoE) support. The AC and DC power
supplies are hot-swappable.
Junos OS support for advanced security and routing services on the Services and Routing Engine (SRE).
•
The services gateway supports Gigabit-Backplane Physical Interface Modules (GPIMs) and also Mini
•
Physical Interface Modules (Mini-PIMs). For details about the supported GPIMs and Mini-PIMs, see the
SRX Series Services Gateways for the Branch Physical Interface Modules Hardware Guide.
RELATED DOCUMENTATION
SRX550 Services Gateway Description | 2
Accessing the SRX550 Services Gateway | 11
SRX550 Services Gateway Software Features and Licenses | 4
Power over Ethernet (PoE) supports the implementation of the IEEE802.3 af and IEEE802.3 at standards,
which allow both data and electric power to pass over a copper Ethernet LAN cable.
The SRX550 Services Gateway provides PoE ports, which supply electric power over the same ports that
are used to connect network devices. PoE ports allow you to plug in devices that require both network
connectivity and electric power, such as Voice over IP (VoIP) and IP phones and wireless access points.
The PoE ports for the SRX550 Services Gateway reside on the individual XPIMs. The SRX550 Services
Gateway supports the following XPIMs with PoE:
16-Port Gigabit Ethernet XPIM
•
24-Port Gigabit Ethernet XPIM
•
The Services and Routing Engine (SRE) manages the overall system PoE power. You can configure the
services gateway to act as power sourcing equipment to supply the power to the GPIMs connected on
the designated PoE ports.
Table 4 on page 10 lists the SRX550 Services Gateway PoE specifications.
SRX550 Services Gateway Back Panel | 22
Physical Interface Modules
Accessing the SRX550 Services Gateway
You can use two user interfaces to monitor, configure, troubleshoot, and manage the Juniper Networks
Services Gateway:
The J-Web interface: A Web-based graphical interface that allows you to operate a services gateway
•
without commands. The J-Web interface provides access to all Junos OS functionality and features.
Junos OS command-line interface (CLI): Juniper Networks command shell that runs on top of a UNIX-based
•
operating system kernel. The CLI is a straightforward command interface. On a single line, you type
commands that are executed when you press the Enter key. The CLI provides command help and
command completion.
11
RELATED DOCUMENTATION
SRX550 Services Gateway Description | 2
SRX550 Services Gateway Hardware Features | 3
SRX550 Services Gateway Software Features and Licenses | 4
NOTE: When you explicitly boot the services gateway using the CLI and the services gateway
has two USBs installed (one in slot 0 and the second in slot 1), if the USB in slot 0 fails, the
booting sequence will not boot from the second USB installed in slot 1. Instead, the device will
boot using the next storage media in its storage media booting priority list, the internal
CompactFlash card.
The dual-root partitions allow the services gateways to remain functional if there is file system corruption
and facilitate easy recovery of the corrupted file system.
The dual-root partitioning scheme keeps the primary and backup Junos OS images in two independently
bootable root partitions. If the primary root partition is corrupted, the system will be able to boot from
the backup Junos OS image located in the other root partition and remain fully functional.
When the services gateway powers up, it tries to boot Junos OS from the default storage media. If the
device fails to boot from the default storage media, it tries to boot from the alternate storage media. With
the dual-root partitioning scheme, the device first tries to boot Junos OS from the primary root partition
and then from the backup root partition on the default storage media. If both primary and backup root
partitions of a media fail to boot, then the device tries to boot Junos OS from the next available type of
storage media. The services gateway remains fully functional even if it boots the Junos OS from the backup
root partition of storage media.
RELATED DOCUMENTATION
Installation Overview for the SRX550 Services Gateway | 60
Required Tools and Parts for Installing the SRX550 Services Gateway | 61
SRX550 Services Gateway Basic Connectivity Overview | 95
13
CHAPTER 3
Chassis Description
IN THIS CHAPTER
SRX550 Services Gateway Chassis | 14
SRX550 Services Gateway Front Panel | 15
SRX550 Services Gateway Front Panel LEDs | 19
SRX550 Services Gateway Back Panel | 22
14
SRX550 Services Gateway Chassis
The SRX550 Services Gateway chassis is a rigid sheet metal structure that houses all the other hardware
components.
Table 5 on page 14 provides information about the physical specifications for the services gateway.
Table 5: Physical Specifications for the SRX550 Services Gateway
ValuePhysical Specification
2 rack units (U)Chassis height
17.5 in. (44.4 cm)Chassis width
18.2 in. (46.2 cm)Chassis depth
21.96 lb (9.96 kg)Chassis weight (includes one power supply without any GPIMs or
Mini-PIMs)
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.
Loading...
+ 190 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.