Juniper SRX5400 User manual

SRX5400, SRX5600, and SRX5800 Services
Gateway Card Reference
Published
2020-02-09

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.
SRX5400, SRX5600, and SRX5800 Services Gateway Card Reference
Copyright © 2020 Juniper Networks, Inc. All rights reserved.
The information in this document is current as of the date on the title page.
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.
ii

Table of Contents
About the Documentation | vii
Documentation and Release Notes | vii
Using the Examples in This Manual | vii
Merging a Full Example | viii
Merging a Snippet | viii
Documentation Conventions | ix
Documentation Feedback | xii
Requesting Technical Support | xii
Self-Help Online Tools and Resources | xiii
Creating a Service Request with JTAC | xiii
SRX5400, SRX5600, and SRX5800 Services Gateway Cards and Modules
1
Overview | 3
SRX5400, SRX5600, and SRX5800 Services Gateway Card Overview | 3
Cards Supported on SRX5400, SRX5600, and SRX5800 Services Gateways | 4
Services Processing Cards | 9
Services Processing Cards Specifications | 9
Services Processing Card SRX5K-SPC-2-10-40 Specifications | 9
Services Processing Card SRX5K-SPC-4-15-320 Specifications | 13
Services Processing Card SRX5K-SPC3 Specifications | 18
I/O Cards | 23
I/O Cards Specifications | 23
I/O Card SRX5K-40GE-SFP Specifications | 23
I/O Card SRX5K-4XGE-XFP Specifications | 25
Flex I/O Cards and Port Modules | 29
Flex I/O Cards and Port Modules Specifications | 29
Flex I/O Card (SRX5K-FPC-IOC) Specifications | 29
Flex I/O Card Port Module SRX-IOC-16GE-SFP Specifications | 31
Flex I/O Card Port Module SRX-IOC-16GE-TX Specifications | 33
iii

Flex I/O Card Port Module SRX-IOC-4XGE-XFP Specifications | 34
Modular Port Concentrators and Interface Cards | 37
Modular Port Concentrators and Interface Cards Specifications | 37
Modular Port Concentrator (SRX5K-MPC) Specifications | 37
MIC with 20x1GE SFP Interfaces (SRX-MIC-20GE-SFP) | 40
MIC with 10x10GE SFP+ Interfaces (SRX-MIC-10XG-SFPP) | 46
MIC with 1x100GE CFP Interface (SRX-MIC-1X100G-CFP) | 51
MIC with 2x40GE QSFP+ Interfaces (SRX-MIC-2X40G-QSFP) | 53
SRX5K-MPC3-40G10G Specifications | 54
SRX5K-MPC3-100G10G Specifications | 57
SRX5K-IOC4-10G Specifications | 60
SRX5K-IOC4-MRAT Specifications | 63
Switch Control Boards | 67
Switch Control Boards Specifications | 67
Switch Control Board SRX5K-SCB Specifications | 67
Switch Control Board SRX5K-SCBE Specifications | 70
SRX5K-SCBE LEDs | 71
Switch Control Board SRX5K-SCB3 Specifications | 72
SRX5K-SCB3 LEDs | 73
Switch Control Board SRX5K-SCB4 Specifications | 74
SRX5K-SCB4 LEDs | 75
Routing Engines | 77
Routing Engine Specifications | 77
Routing Engine SRX5K-RE-13-20 Specifications | 77
Routing Engine SRX5K-RE-1800X4 Specifications | 80
SRX5K-RE-1800X4 LEDs | 82
Routing Engine SRX5K-RE3-128G Specifications | 83
SRX5K-RE3-128G Routing Engine Components | 85
SRX5K-RE3-128G Routing Engine LEDs | 86
SRX5K-RE3-128G Routing Engine Boot Sequence | 87
iv

Handling and Storing Cards
2
Handling and Storing SRX5400, SRX5600, and SRX5800 Services Gateway Cards | 91
SRX5400, SRX5600, and SRX5800 Services Gateway Card Terminology | 91
Handling an SRX5400, SRX5600, or SRX5800 Services Gateway Card | 92
Storing an SRX5600, SRX5600, or SRX5800 Services Gateway Card | 94
v

About the Documentation
IN THIS SECTION
Documentation and Release Notes | vii
Using the Examples in This Manual | vii
Documentation Conventions | ix
Documentation Feedback | xii
Requesting Technical Support | xii
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
isafull 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.
vii

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;
}
}
}
}
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.
viii

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]
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 x defines notice icons used in this guide.
ix

Table 1: Notice Icons
DescriptionMeaningIcon
Indicates important features or instructions.Informational note
Indicates a situation that might result in loss of data or hardware
damage.
Caution
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 x defines the text and syntax conventions used in this guide.
Table 2: Text and Syntax Conventions
ExamplesDescriptionConvention
To enter configuration mode, type
the configure command:
user@host> configure
Represents text that you type.Bold text like this
user@host> show chassis alarms
No alarms currently active
Represents output that appears on
the terminal screen.
Fixed-width text like this
•A policy term is a named structure
that defines match conditions and
actions.
•Junos OS CLI User Guide
•RFC 1997, BGP Communities
Attribute
•Introduces or emphasizes important
new terms.
•Identifies guide names.
•Identifies RFC and Internet draft
titles.
Italic text like this
x

Table 2: Text and Syntax Conventions (continued)
ExamplesDescriptionConvention
Configure the machine’s domain
name:
[edit]
root@# set system domain-name
domain-name
Represents variables (options for
which you substitute a value) in
commands or configuration
statements.
Italic text like this
•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.
Represents names of configuration
statements, commands, files, and
directories; configuration hierarchy
levels; or labels on routing platform
components.
Text like this
stub <default-metric metric>;Encloses optional keywords or
variables.
< > (angle brackets)
broadcast | multicast
(string1 |string2 |string3)
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.
| (pipe symbol)
rsvp { # Required for dynamic MPLS
only
Indicates a comment specified on the
same line as the configuration
statement to which it applies.
# (pound sign)
community name members [
community-ids ]
Encloses a variable for which you can
substitute one or more values.
[ ] (square brackets)
[edit]
routing-options {
static {
route default {
nexthop address;
retain;
}
}
}
Identifies a level in the configuration
hierarchy.
Indention and braces ( { } )
Identifies a leaf statement at a
configuration hierarchy level.
; (semicolon)
GUI Conventions
xi