SRX100ServicesGatewayHardwareGuide for B and H Model Numbers
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.
SRX100ServicesGatewayHardwareGuideforBandHModelNumbers
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 | ix
Documentation and Release Notes | ix
Using the Examples in This Manual | ix
Merging a Full Example | x
Merging a Snippet | xi
Documentation Conventions | xi
Documentation Feedback | xiv
Requesting Technical Support | xiv
Self-Help Online Tools and Resources | xv
Creating a Service Request with JTAC | xv
1Overview
SystemOverview | 2
SRX100 Services Gateway Description | 2
About the SRX100 Services Gateway | 2
SRX100 Services Gateway Models | 3
Accessing the SRX100 Services Gateway | 3
SRX100 Services Gateway Features and Functions | 4
HardwareComponentOverview | 6
SRX100 Services Gateway LEDs | 6
SRX100 Services Gateway Front Panel LEDs | 6
SRX100 Services Gateway Ethernet Port LEDs | 8
SRX100 Services Gateway Power Supply | 9
SRX100 Services Gateway Boot Devices and Dual-Root Partitioning Scheme | 10
Boot Devices | 10
Dual-Root Partitioning Scheme | 10
iv
ChassisDescription | 12
SRX100 Services Gateway Front Panel and Back Panel Views | 12
SRX100 Services Gateway Front Panel | 12
SRX100 Services Gateway Back Panel | 13
SRX100 Services Gateway Built-In Interfaces | 14
2SitePlanningandSpecifications
PlanningandPreparingtheSite | 18
Site Preparation Checklist for the SRX100 Services Gateway | 18
General Site Guidelines for Installing the SRX100 Services Gateway | 21
SRX100 Services Gateway Specifications | 21
SRX100 Services Gateway Cabinet Requirements | 23
SRX100 Services Gateway Rack Requirements | 24
Clearance Requirements for Airflow and Hardware Maintenance of the SRX100 Services
Gateway | 25
PowerRequirementsandSpecifications | 27
SRX100 Services Gateway Site Electrical Wiring Guidelines | 27
SRX100 Services Gateway Electrical and Power Requirements | 29
SRX100 Services Gateway Power Specifications and Requirements | 29
CableSpecificationsandPinouts | 31
Interface Cable and Wire Specifications for the SRX100 Services Gateway | 31
RJ-45 Connector Pinouts for the SRX100 Services Gateway Ethernet Port | 32
RJ-45 Connector Pinouts for the SRX100 Services Gateway Console Port | 32
3InitialInstallationandConfiguration
InstallationOverview | 35
Installation Overview for the SRX100 Services Gateway | 36
Required Tools and Parts for Installing and Maintaining the SRX100 Services Gateway | 37
SRX100 Services Gateway Autoinstallation Overview | 38
UnpackingtheServicesGateway | 40
Unpacking the SRX100 Services Gateway | 40
Verifying Parts Received with the SRX100 Services Gateway | 41
v
InstallingtheMountingHardware | 43
Preparing the SRX100 Services Gateway for Rack-Mount Installation | 43
Preparing the SRX100 Services Gateway for Desk-Mount Installation | 44
Preparing the SRX100 Services Gateway for Wall-Mount Installation | 45
InstallingtheServicesGateway | 46
Installing the SRX100 Services Gateway in a Rack | 46
Installing the SRX100 Services Gateway on a Desk | 48
Installing the SRX100 Services Gateway on a Wall | 49
GroundingtheSRX100ServicesGateway | 52
Grounding the SRX100 Services Gateway | 52
ConnectingtheSRX100ServicesGatewaytoExternalDevices | 55
Connecting and Organizing Interface Cables to the SRX100 Services Gateway | 55
Connecting the Modem at the SRX100 Services Gateway End | 56
Connecting the Modem to the Console Port on the SRX100 Services Gateway | 57
Connecting to the CLI at the User End for the SRX100 Services Gateway | 58
ProvidingPowertotheSRX100ServicesGateway | 60
Connecting the SRX100 Services Gateway to the Power Supply | 60
Powering On and Powering Off the SRX100 Services Gateway | 61
Powering On the SRX100 Services Gateway | 61
Powering Off the SRX100 Services Gateway | 62
PerformingInitialConfiguration | 65
SRX100 Services Gateway Software Configuration Overview | 65
Preparing the SRX100 Services Gateway for Configuration | 66
Understanding the Factory Default Configuration | 66
Understanding Built-In Ethernet Ports and Initial Configuration | 67
Mapping the Chassis Cluster Ports | 67
Understanding Management Access | 68
Connecting to the SRX100 Services Gateway Setup Wizard | 69
SRX100 Services Gateway Secure Web Access Overview | 70
Connecting an SRX100 Services Gateway to the CLI Locally | 71
vi
Connecting an SRX100 Services Gateway to the CLI Remotely | 74
Viewing Factory-Default Settings of the SRX100 Services Gateway | 74
Performing Initial Software Configuration on the SRX100 Services Gateway Using the CLI | 83
Performing Initial Software Configuration on the SRX100 Services Gateway Using the J-Web
Interface | 87
Establishing Basic Connectivity | 88
Configuring Basic System Properties | 89
Upgrading the SRX100 Services Gateway Low Memory Version to a High Memory Version | 92
4MaintainingandTroubleshootingComponents
MaintainingComponents | 95
Maintaining the SRX100 Services Gateway Hardware Components | 95
TroubleshootingComponents | 97
Monitoring the SRX100 Services Gateway Chassis Using the CLI | 97
Monitoring the SRX100 Services Gateway Components Using LEDs | 100
Monitoring the SRX100 Services Gateway Using Chassis Alarm Conditions | 102
Monitoring the SRX100 Services Gateway Power System | 103
Using the Reset Config Button on the SRX100 Services Gateway | 104
Changing the Reset Config Button Behavior on the SRX100 Services Gateway | 106
Juniper Networks Technical Assistance Center | 107
5ReplacingComponents
ContactingCustomerSupportandReturningComponents | 109
Contacting Customer Support | 109
Return Procedure for the SRX100 Services Gateway | 110
Information You Might Need to Supply to Juniper Networks Technical Assistance Center | 111
Locating the SRX100 Services Gateway Component Serial Number and Agency Labels | 111
Packing the SRX100 Services Gateway and Components for Shipment | 113
vii
6SafetyandRegulatoryComplianceInformation
GeneralSafetyGuidelinesandWarnings | 116
SRX100 Services Gateway Definition of Safety Warning Levels | 116
SRX100 Services Gateway General Safety Guidelines and Warnings | 119
General Safety Guidelines and Warnings | 119
Qualified Personnel Warning | 121
Restricted Access Area Warning | 122
Preventing Electrostatic Discharge Damage to the Services Gateway | 124
SRX100 Services Gateway Safety Requirements, Warnings, and Guidelines | 125
FireSafetyRequirements | 127
SRX100 Services Gateway Fire Safety Requirements | 127
InstallationSafetyGuidelinesandWarnings | 129
SRX100 Services Gateway Installation Safety Guidelines and Warnings | 129
LaserandLEDSafetyGuidelinesandWarnings | 136
SRX100 Services Gateway Laser and LED Safety Guidelines and Warnings | 136
Laser and LED Safety Guidelines and Warnings | 136
General Laser Safety Guidelines | 136
Class 1 Laser Product Warning | 137
Class 1 LED Product Warning | 137
Laser Beam Warning | 138
Radiation from Open Port Apertures Warning | 139
MaintenanceandOperationalSafetyGuidelinesandWarnings | 141
SRX100 Services Gateway Maintenance and Operational Safety Guidelines and Warnings | 141
Safety Guidelines and Warnings | 142
Battery Handling Warning | 142
Jewelry Removal Warning | 143
Lightning Activity Warning | 145
Operating Temperature Warning | 146
Product Disposal Warning | 148
viii
ElectricalSafetyGuidelinesandWarnings | 150
SRX100 Services Gateway Electrical Safety Guidelines and Warnings | 150
Electrical Safety Guidelines and Warnings | 150
In Case of Electrical Accident | 150
General Electrical Safety Guidelines and Warnings | 150
AgencyApprovalsandRegulatoryComplianceInformation | 152
SRX100 Services Gateway Agency Approvals | 152
SRX100 Services Gateway Compliance Statements for EMC Requirements | 153
Canada | 154
European Community | 154
Japan | 154
Korean | 154
United States | 154
SRX100 Services Gateway Compliance Statements for Environmental Requirements | 155
ix
AbouttheDocumentation
INTHISSECTION
Documentation Conventions | xi
Documentation Feedback | xiv
Requesting Technical Support | xiv
Use this guide to install hardware and perform initial software configuration, routine maintenance, and troubleshooting for the SRX100 Services Gateway (B and H model numbers). After completing the installationandbasicconfigurationprocedurescoveredinthisguide,refertotheJunosOSdocumentation 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.
x
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
xi
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 xii defines notice icons used in this guide.
xii
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 xii 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
xiii
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
xiv
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
xv
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
PART
System Overview | 2
Hardware Component Overview | 6
Chassis Description | 12
2
CHAPTER 1
SystemOverview
INTHISCHAPTER
SRX100 Services Gateway Features and Functions | 4
SRX100ServicesGatewayDescription
INTHISSECTION
SRX100 Services Gateway Models | 3
Accessing the SRX100 Services Gateway | 3
This topic includes the following sections:
AbouttheSRX100ServicesGateway
TheJuniperNetworksSRX100ServicesGatewayoffersfeaturesthatprovidecompletefunctionalityand flexibility for delivering secure Internet and intranet access. The services gateway offers stable, reliable, and efficient IP routing in addition to switching support and LAN connectivity. The device provides IP Security(IPsec),virtualprivatenetwork(VPN),andfirewallservicesforsmallandmedium-sizedcompanies and enterprise branch and remote offices. The SRX100 Services Gateway can be connected directly to traditional private networks such as leased lines, Frame Relay, or Multi Protocol Label Switching (MPLS) or to the public Internet.
The SRX100 Services Gateway runs the Junos operating system (Junos OS).
3
SRX100ServicesGatewayModels
The following are the two models of the SRX100 Services Gateway available with 1 GB memory. For information on the models with 2 GB memory, see SRX100 Services Gateway Hardware Guide for H2 Model Numbers.
Table3:SRX100ServicesGatewayModels
Product Name |
Device Type |
Model Number |
SRX100 Services Gateway |
Low Memory |
SRX100B |
SRX100 Services Gateway |
High Memory |
SRX100H |
NOTE: You can upgrade from an SRX100 Services Gateway Low Memory version to a High Memory version through a license key. You need not order a separate High Memory device.
NOTE: SRX100HmodelprovidesadditionalsecurityfeaturessuchasUnifiedThreatManagement (UTM), which consists of IPS antispam, antivirus, and Web filtering.
NOTE: The SRX100 Services Gateway High Memory model ships with a license key.
All SRX100 Services Gateways run the Junos OS.
AccessingtheSRX100ServicesGateway
Twouserinterfacesareavailableformonitoring,configuring,troubleshooting,andmanagingtheSRX100
Services Gateway:
•J-Web interface: 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.
•JunosOScommand-lineinterface(CLI):JuniperNetworkscommandshellthatrunsontopofaUNIX-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.
4
RELATED DOCUMENTATION
SRX100 Services Gateway Specifications | 21
Upgrading the SRX100 Services Gateway Low Memory Version to a High Memory Version | 92
SRX100ServicesGatewayFeaturesandFunctions
TheSRX100ServicesGatewayisasecurityoptimized,fixedprocessingsystemthatprovidesthefollowing features for the Low Memory and High Memory models listed in Table 4 on page 4. For information on the models with 2 GB memory, see SRX100 Services Gateway Hardware Guide for H2 Model Numbers.
Table4:SRX100ServicesGatewayHardwareFeatures
|
SRX100 Services Gateway Low |
SRX100 Services Gateway High |
Features |
Memory |
Memory |
DDR Memory |
512 MB (software upgradable to High |
1 GB |
|
Memory through a license key) |
|
Power supply adapter |
30 watts |
30 watts |
AC input voltage |
100 to 240 VAC |
100 to 240 VAC |
Fast Ethernet ports |
8 |
8 |
Console port |
1 |
1 |
USB port |
1 |
1 |
LEDs |
4 |
4 |
NAND flash |
1 GB |
1 GB |
For more details on Junos OS features and licenses for the SRX100 Services Gateway, see the JunosOS AdministrationGuideforSecurityDevices.
For more information on upgrading an SRX100 Services Gateway Low Memory to High Memory, see “Upgrading the SRX100 Services Gateway Low Memory Version to a High Memory Version” on page 92.
RELATED DOCUMENTATION
5
SRX100 Services Gateway Description | 2
SRX100 Services Gateway Specifications | 21
Upgrading the SRX100 Services Gateway Low Memory Version to a High Memory Version | 92
6
CHAPTER 2
HardwareComponentOverview
INTHISCHAPTER
SRX100 Services Gateway Power Supply | 9
SRX100 Services Gateway Boot Devices and Dual-Root Partitioning Scheme | 10
SRX100ServicesGatewayLEDs
INTHISSECTION
SRX100 Services Gateway Ethernet Port LEDs | 8
This topic includes the following sections:
SRX100ServicesGatewayFrontPanelLEDs
Figure 1 on page 7 illustrates the front panel LEDs of the SRX100 Services Gateway.
NOTE: The numbers in Figure 1 on page 7 correspond to the numbers in Table 5 on page 7.
7
Figure1:SRX100ServicesGatewayFrontPanelLEDs
Table 5 on page 7 lists the LED indicators on the SRX100 Services Gateway front panel.
Table5:SRX100ServicesGatewayFrontPanelLEDs
Number |
Component |
Description |
Usage |
1 |
Alarm LED |
The Alarm LED has the |
|
|
following indicator colors: |
|
|
• Solid red indicates a |
|
|
major alarm. |
|
|
• Solid amber indicates a |
|
|
minor alarm. |
|
|
• Off indicates that there |
|
|
are currently no alarms. |
2 |
Power LED |
The Power LED has the |
|
|
following indicator colors: |
• Solid green indicates that the device is functioning normally.
• Solid amber indicates that the power button has been pressed and quickly released. The device is gracefully shutting down.
• Off indicates that the device is not receiving power.
The Alarm LED can be usedtogatherinformation on major or minor alarms or to determine if the device is functioning normally.
The Power LED can be used to determine if the device is receiving power.
8
Table5:SRX100ServicesGatewayFrontPanelLEDs (continued)
Number |
Component |
Description |
Usage |
3 |
HA LED |
The HA LED has the |
|
|
following indicator colors: |
|
|
• Solid green indicates |
|
|
thatallchassisclustering |
|
|
links are available. |
|
|
• Solid red indicates that |
|
|
the chassis clustering |
|
|
links are not working as |
|
|
expected. |
|
|
• Solid amber indicates |
|
|
that some chassis |
|
|
clustering links are not |
|
|
working as expected. |
|
|
• Off indicates that |
|
|
chassis clustering is not |
|
|
enabled. |
4 |
Status LED |
The Status LED has the |
|
|
following indicator colors: |
• Solid green indicates that the device is functioning normally.
• Solid amber indicates that the device is starting up.
• Solid red indicates that an error is detected in the device.
The HA LED can be used to determine if chassis clusteringisenabledonthe device.
The Status LED can be usedtodeterminewhether thedeviceisstartingup,is functioning normally, or has failed.
SRX100ServicesGatewayEthernetPortLEDs
On the SRX100 Services Gateway, each Fast Ethernet port has one functional LED on the left side that indicates Link and Activity. In Figure 2 on page 9, this LED is marked as 1.
9
Figure2:SRX100ServicesGatewayEthernetPortLEDs
The Table 6 on page 9 applies only to the TX/RX/LINK LED marked 1. Table 6 on page 9 describes the states of this LED.
Table6:SRX100ServicesGatewayBuilt-InEthernetPortLEDs
Function |
Color |
State |
Description |
TX/RX/LINK |
Green |
Blinking |
Link is active. Data communication |
|
|
|
is taking place. |
|
|
Steady |
Link is active. No data |
|
|
|
communication is taking place. |
|
Unlit |
Off |
Link is inactive. |
NOTE: The LED marked as 2 in Figure 2 on page 9 is not functional in this release.
RELATED DOCUMENTATION
SRX100 Services Gateway Specifications | 21
SRX100 Services Gateway Front Panel and Back Panel Views | 12
SRX100 Services Gateway Built-In Interfaces | 14
SRX100 Services Gateway Boot Devices and Dual-Root Partitioning Scheme | 10
SRX100ServicesGatewayPowerSupply
The power supply for the SRX100 Services Gateway is external. You must use the power supply adapter provided by Juniper Networks to provide power to the services gateway.
10
RELATED DOCUMENTATION
SRX100 Services Gateway Specifications | 21
SRX100 Services Gateway Front Panel and Back Panel Views | 12
SRX100 Services Gateway LEDs | 6
SRX100 Services Gateway Built-In Interfaces | 14
Monitoring the SRX100 Services Gateway Power System | 103
SRX100 Services Gateway Electrical and Power Requirements | 29
SRX100ServicesGatewayBootDevicesandDual-RootPartitioningScheme
INTHISSECTION
This topic includes the following sections:
BootDevices
The SRX100 Services Gateway can boot from the following storage media (in the order of priority):
•Internal NAND Flash (default; always present)
•USB storage key (alternate)
Dual-RootPartitioningScheme
Dual-root partitions allow the SRX100 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 becomes corrupted, the system will be able to boot from the backup Junos OS image located in the other root partition and remain fully functional.
11
When the SRX100 Services Gateway powers up, it tries to boot the Junos OS from the default storage media. Ifthedevicefailstobootfromthedefaultstoragemedia,ittriestobootfromthealternatestorage media. Withthedual-rootpartitioningscheme,theSRX100ServicesGatewayfirsttriestoboottheJunos OSfromtheprimaryrootpartitionandthenfromthebackuprootpartitiononthedefaultstoragemedia. If both primary and backup root partitions of a media fail to boot, then the device tries to boot from the next available type of storage media. The SRX100 Services Gateway remains fully functional even if it boots the Junos OS from the backup root partition of storage media.
NOTE: SRXSeriesdevicesthatshipfromthefactorywithJunosOSRelease10.0areformatted with the dual-root partitioning scheme.
The SRX100 Services Gateways that are running Junos OS Release 9.6 or earlier use the single-root partitioning scheme. While upgrading these devices to Junos OS Release 10.0, you can choose to format the storage media with dual-root partitions (strongly recommended) or retain the existing single-root partitioning.
For instructions on upgrading to Junos OS Release 10.0, see the following topics:
•Initial Configuration for Security Devices
•Monitoring and Troubleshooting for Security Devices
RELATED DOCUMENTATION
Installation Overview for the SRX100 Services Gateway | 36
SRX100 Services Gateway Software Configuration Overview | 65
12
CHAPTER 3
ChassisDescription
INTHISCHAPTER
SRX100 Services Gateway Built-In Interfaces | 14
SRX100ServicesGatewayFrontPanelandBackPanelViews
INTHISSECTION
SRX100 Services Gateway Back Panel | 13
ThistopiccontainsviewsofthefrontandbackpanelsoftheSRX100ServicesGateway.Thistopicincludes the following sections:
SRX100ServicesGatewayFrontPanel
Figure 3 on page 12 shows the front panel of the SRX100 Services Gateway.
Figure3:SRX100ServicesGatewayFrontPanel
<![if ! IE]><![endif]>g031001
13
Table 7 on page 13 lists the front panel components of the services gateway.
Table7:SRX100ServicesGatewayFrontPanelComponents
Number Component
1Power button
2LEDs: Alarm, Status, Power, HA
3Reset Config button
4Universal serial bus (USB) port
5Console port
6Fast Ethernet ports
For more information on the front panel components, see the following topics:
•SRX100 Services Gateway Built-In Interfaces on page 14
•SRX100 Services Gateway LEDs on page 6
•SRX100 Services Gateway Boot Devices and Dual-Root Partitioning Scheme on page 10
SRX100ServicesGatewayBackPanel
Figure 4 on page 13 illustrates the back panel of the SRX100 Services Gateway.
Figure4:SRX100ServicesGatewayBackPanel
<![if ! IE]><![endif]>g031002
Table 8 on page 14 lists the components available on the back panel of the SRX100 Services Gateway.
14
Table8:SRX100ServicesGatewayBackPanel
Number Component
1 |
Lock |
2 |
Grounding point |
3 |
Cable tie holder |
4 |
Power supply point |
NOTE: The cable tie holder provides support for holding the power cord on the power supply point.
The lock provides the option to lock and secure the device to the installation site.
RELATED DOCUMENTATION
SRX100 Services Gateway Specifications | 21
SRX100 Services Gateway LEDs | 6
SRX100 Services Gateway Boot Devices and Dual-Root Partitioning Scheme | 10
SRX100 Services Gateway Power Supply | 9
SRX100ServicesGatewayBuilt-InInterfaces
Table 9 on page 15 summarizes the interface ports supported on the SRX100 Services Gateway.
15
Table9:SRX100ServicesGatewayBuilt-InHardwareInterfaces
Interface Type |
Specifications |
Description |
Fast Ethernet |
The Fast Ethernet ports: |
|
• Consist of eight fixed ports |
|
• Arelabeledasport0/0toport0/7 |
|
on the front panel |
|
• Provide link speeds of 10/100 |
|
Mbps |
|
• Operate in full-duplex and |
|
half-duplex modes |
|
• Support flow control |
|
• Support autonegotiation |
|
• Support autosensing |
Universal Serial Bus (USB) |
The USB port: |
|
• Consists of one port |
|
• Supports the following modes: |
|
• Full speed |
|
• High speed |
|
• Complies with USB revision 2.0 |
Console |
The console port: |
• Consists of one port
• Uses an RJ-45 serial cable connector
• Supports the RS-232 (EIA-232)
standard
TheFastEthernetportscanbeused:
•To provide LAN connectivity to hubs, switches, local servers, and workstations.
•Toforwardincomingdatapackets to the device.
•To receive outgoing data packets from the device.
The USB port can be used:
•To support a USB storage device thatfunctionsasasecondaryboot device in case of internal flash failure on startup, if the USB storage device is installed and configured
NOTE: You must install and configuretheUSBstoragedevice on the USB port to use it as secondary boot device. Additionally,theUSBdevicemust have Junos installed.
•ToprovidetheUSBinterfacesthat are used to communicate with many types of Juniper-supported USB storage devices
The console port can be used:
•To provide the console interface.
•Tofunctionasamanagementport to log into a device directly.
•To configure the device using the CLI.