Book Srx Series Interfaces Hardware Guide

8/17/2019 Book Srx Series Interfaces Hardware Guide

1/214

SRX Series ServicesGateways for the Branch

Physical Interface Modules Hardware Guide

Published: 2010-10-21

Revision03

Copyright © 2010, Juniper Networks, Inc.


2/214

Juniper Networks, Inc.1194North Mathilda AvenueSunnyvale, California 94089USA408-745-2000www.juniper.net

Thisproduct includesthe Envoy SNMPEngine, developed by EpilogueTechnology,an IntegratedSystems Company.Copyright© 1986-1997,

Epilogue Technology Corporation.All rights reserved. This program and its documentation were developed at privateexpense, and no part

of them is in thepublic domain.

This product includes memory allocation software developed by Mark Moraes,copyright © 1988, 1989, 1993, University of Toronto.

This product includes FreeBSD software developed by the University of California, Berkeley, and its contributors. All of the documentation

and software included in the 4.4BSD and 4.4BSD-Lite Releases is copyrighted by the Regents of the University of California. Copyright ©

1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994. The Regents of the University of California. All rights reserved.

GateD software copyright © 1995, the Regents of the University. All rights reserved. Gate Daemon was originated and developed through

release 3.0 by Cornell University and its collaborators. Gated is based on Kirton’s EGP, UC Berkeley’s routing daemon (routed), and DCN’s

HELLO routing protocol. Development of Gated has beensupported in part by the National Science Foundation. Portions of the GateD

software copyright © 1988, Regentsof theUniversityof California.All rights reserved. Portionsof theGateD software copyright © 1991, D.

L. S. Associates.

This product includes software developed by Maker Communications, Inc., copyright © 1996, 1997, Maker Communications, Inc.

Juniper Networks, Junos, Steel-Belted Radius, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc.in the United

States and other countries. The Juniper Networks Logo, the Junos logo, and JunosE are trademarks of Juniper Networks, Inc.All other

trademarks, service marks, registered trademarks, or registered service marks are the property of theirrespective 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.

Products made or sold byJuniper Networks or components thereof might be covered by oneor more of thefollowingpatents that are

owned by or licensed to Juniper Networks: U.S. Patent Nos. 5,473,599, 5,905,725, 5,909,440,6,192,051, 6,333,650, 6,359,479, 6,406,312,

6,429,706, 6,459,579, 6,493,347, 6,538,518, 6,538,899, 6,552,918, 6,567,902, 6,578,186, and 6,590,785.

SRXSeriesServicesGatewaysfor the BranchPhysical InterfaceModulesHardwareGuideCopyright © 2010, Juniper Networks, Inc.

All rights reserved. Printed in USA.

Revision History

October 2010—Revision03

The informationin this document is currentas of thedatelisted in the revisionhistory.

SOFTWARE LICENSE

The terms and conditions for using this software are described in the software license contained in the acknowledgment to your purchase

order or, to the extent applicable, to any reseller agreement or end-user purchase agreement executed between you and Juniper Networks.

By using this software, you indicate that you understand and agree to be bound by those termsand conditions.

Generally speaking,the software license restricts the manner in which you are permitted to use the software and may contain prohibitions

against certain uses.The software license may state conditions under which the license is automatically terminated. You should consult

the license for further details.

For complete product documentation, please see the Juniper Networks Web site at www.juniper.net/techpubs.

Copyright © 2010, Juniper Networks, Inc.ii


3/214

END USER LICENSE AGREEMENT

READ THIS END USER LICENSE AGREEMENT (“AGREEMENT”)BEFORE DOWNLOADING, INSTALLING, OR USING THE SOFTWARE.

BY DOWNLOADING, INSTALLING,OR USING THE SOFTWARE OR OTHERWISEEXPRESSINGYOUR AGREEMENT TO THE TERMS

CONTAINED HEREIN, YOU (AS CUSTOMER OR IF YOU ARE NOT THE CUSTOMER, AS A REPRESENTATIVE/AGENT AUTHORIZED TO

BINDTHE CUSTOMER) CONSENT TOBE BOUND BY THISAGREEMENT. IF YOU DO NOT OR CANNOT AGREE TOTHE TERMS CONTAINED

HEREIN, THEN (A) DO NOT DOWNLOAD, INSTALL, OR USE THE SOFTWARE, AND (B) YOU MAY CONTACT JUNIPER NETWORKS

REGARDING LICENSE TERMS.

1. The Parties. The parties to this Agreement are (i)Juniper Networks, Inc. (if the Customer’s principal office is located in theAmericas) or

JuniperNetworks(Cayman)Limited (ifthe Customer’s principal office is locatedoutsidethe Americas) (such applicableentitybeingreferred

tohereinas “Juniper”),and (ii)the personor organizationthatoriginallypurchased from Juniperor anauthorizedJuniper resellerthe applicable

license(s) for use of the Software (“Customer”) (collectively, the “Parties”).

2. The Software. In this Agreement, “Software” means the program modules and features of the Juniper or Juniper-supplied software, for

whichCustomer has paid theapplicable license or support fees to Juniper or an authorized Juniper reseller, or whichwas embedded by

Juniper in equipmentwhich Customerpurchased fromJuniperor an authorized Juniper reseller.“Software” alsoincludes updates,upgrades

and new releases of suchsoftware. “Embedded Software” means Software which Juniper has embedded in or loaded ontothe Juniper

equipment and any updates, upgrades, additions or replacements which are subsequently embeddedin or loaded onto the equipment.

3. License Grant. Subjectto paymentof theapplicablefees andthe limitations andrestrictionsset forth herein,Junipergrants to Customera non-exclusive and non-transferable license, without right to sublicense, to use the Software, in executable form only, subject to the

following use restrictions:

a. Customer shall use Embedded Software solely as embedded in, and for execution on, Juniper equipment originally purchased by

Customer fromJuniper or an authorized Juniper reseller.

b. Customershalluse theSoftware on a single hardware chassis having a single processing unit, or as many chassis or processingunits

for which Customer has paid the applicable license fees; provided, however, with respect to the Steel-Belted Radius or Odyssey Access

Client software only,Customer shall use such Software on a single computer containing a single physical random access memory space

and containingany number of processors. Useof theSteel-Belted Radius or IMSAAA software on multiple computers or virtual machines

(e.g., Solaris zones) requires multiplelicenses, regardless of whether such computers or virtualizations are physically contained on a single

chassis.

c. Product purchase documents, paper or electronic user documentation, and/or the particular licenses purchased by Customer may

specifylimitsto Customer’s useof theSoftware. Such limits mayrestrictuse toa maximumnumber of seats,registered endpoints,concurrentusers, sessions, calls, connections, subscribers, clusters, nodes, realms, devices, links, ports or transactions, or require the purchase of

separate licenses to use particular features, functionalities, services, applications, operations, or capabilities,or provide throughput,

performance, configuration, bandwidth, interface,processing,temporal, or geographical limits. In addition,such limits may restrict the use

of the Software to managing certain kinds of networks or require theSoftware to be used only in conjunction with other specific Software.

Customer’s useof theSoftware shall be subject to allsuch limitations and purchase of allapplicable licenses.

d. Forany trial copy of theSoftware, Customer’s right to usethe Software expires 30 days afterdownload, installation or useof the

Software. Customermay operate theSoftware afterthe 30-day trial period only if Customer pays for a license to do so.Customer may not

extend or create an additional trial period by re-installing the Software after the 30-day trial period.

e. The Global Enterprise Edition of theSteel-Belted Radius software may be used by Customeronlyto manage access to Customer’s

enterprise network. Specifically, service provider customers are expressly prohibited fromusing the Global Enterprise Edition of the

Steel-Belted Radius software to support any commercial network access services.

The foregoing license is not transferable or assignable by Customer. No license is granted herein to any user who did not originally purchase

the applicable license(s) for the Software from Juniper or an authorized Juniper reseller.

4. Use Prohibitions. Notwithstanding the foregoing, the license providedherein does not permit the Customer to,and Customer agrees

not to and shall not: (a) modify,unbundle, reverse engineer, or create derivative works based on the Software; (b) make unauthorized

copies of theSoftware (exceptas necessary for backup purposes); (c) rent,sell,transfer, or grant any rightsin and to any copy of the

Software, in anyform,to anythird party;(d) remove anyproprietary notices,labels,or marks on or in anycopyof theSoftware or anyproduct

in which theSoftware is embedded;(e) distribute any copy of the Software to any third party, includingas may be embeddedin Juniper

equipmentsoldin thesecondhand market;(f) useany ‘locked’or key-restrictedfeature, function, service,application,operation,or capability

without first purchasing the applicable license(s) and obtaining a valid key fromJuniper, evenif such feature, function, service, application,

operation, or capabilityis enabled without a key; (g)distribute any key for theSoftware providedby Juniper to any third party; (h) usethe

iiiCopyright © 2010, Juniper Networks, Inc.


4/214

Software in any manner that extends or is broaderthanthe uses purchased by Customer from Juniper or an authorized Juniper reseller; (i)

use Embedded Software on non-Juniper equipment; (j) use EmbeddedSoftware (or make it available for use) on Juniper equipment that

the Customer did not originally purchase fromJuniper or an authorized Juniper reseller; (k) disclose the results of testing or benchmarking

of theSoftware toany thirdparty without theprior writtenconsent of Juniper; or (l)use theSoftwarein any manner other than asexpressly

provided herein.

5. Audit. Customer shall maintain accuraterecords as necessary to verify compliance with this Agreement. Uponrequest by Juniper,

Customer shall furnish such records to Juniper and certify its compliance with this Agreement.

6. Confidentiality. TheParties agree that aspectsof the Software and associated documentation are the confidential property of Juniper.

As such, Customershall exercise all reasonable commercial efforts to maintainthe Software andassociated documentation in confidence,

which at a minimum includes restricting access to the Software to Customeremployees andcontractors having a need to use the Software

for Customer’s internal business purposes.

7. Ownership. Juniper and Juniper’s licensors, respectively, retain ownership of all right, title, and interest (including copyright) in and to

the Software, associated documentation, and all copies of the Software. Nothing in this Agreement constitutes a transfer or conveyance

of anyright, title, or interest in the Software or associated documentation, or a sale of the Software, associated documentation, or copies

of the Software.

8. Warranty, Limitation of Liability, Disclaimer of Warranty. The warranty applicable to theSoftware shall be asset forthin thewarranty

statement that accompaniesthe Software(the “WarrantyStatement”). Nothingin thisAgreementshall giverise toany obligation tosupportthe Software. Support services may be purchased separately. Any such support shall be governed by a separate, written support services

agreement. TO THE MAXIMUM EXTENT PERMITTED BY LAW, JUNIPER SHALL NOT BE LIABLE FOR ANY LOST PROFITS, LOSS OF DATA,

ORCOSTSOR PROCUREMENTOF SUBSTITUTEGOODSOR SERVICES,OR FORANY SPECIAL, INDIRECT, OR CONSEQUENTIAL DAMAGES

ARISINGOUTOF THISAGREEMENT,THE SOFTWARE,OR ANYJUNIPER OR JUNIPER-SUPPLIEDSOFTWARE. IN NOEVENT SHALLJUNIPER

BE LIABLE FOR DAMAGES ARISING FROM UNAUTHORIZED OR IMPROPER USE OF ANY JUNIPER OR JUNIPER-SUPPLIED SOFTWARE.

EXCEPT AS EXPRESSLY PROVIDED IN THE WARRANTYSTATEMENT TOTHE EXTENT PERMITTED BY LAW, JUNIPER DISCLAIMS ANY

AND ALL WARRANTIES IN AND TO THE SOFTWARE (WHETHER EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE), INCLUDING ANY

IMPLIED WARRANTY OF MERCHANTABILITY, FITNESSFOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT DOES

JUNIPER WARRANT THAT THE SOFTWARE, OR ANY EQUIPMENT OR NETWORK RUNNINGTHE SOFTWARE,WILL OPERATE WITHOUT

ERROR OR INTERRUPTION, OR WILL BE FREE OF VULNERABILITYTO INTRUSION OR ATTACK. In no event shall Juniper’s or itssuppliers’

or licensors’ liability to Customer, whether in contract, tort (including negligence),breach of warranty, or otherwise, exceed the price paid

by Customerfor theSoftware that gave rise to theclaim, or if theSoftware is embeddedin another Juniper product,the price paid by

Customerfor such other product. Customer acknowledges and agrees that Juniper has setits prices and entered into this Agreement in

reliance upon thedisclaimersof warranty and thelimitations of liabilityset forthherein,thatthe same reflect an allocationof risk between

theParties(including the risk that a contract remedy may fail of its essentialpurpose and causeconsequential loss), and that thesameform an essentialbasis of thebargainbetweenthe Parties.

9. Termination. Any breach of this Agreementor failure by Customer to pay any applicable fees dueshallresult in automatic termination

of the license granted herein. Upon such termination, Customershalldestroy or return to Juniper allcopies of theSoftware and related

documentation in Customer’s possession or control.

10. Taxes. All license fees payable under this agreement are exclusive of tax.Customer shall be responsible for paying Taxes arising from

the purchase of the license,or importation or use of the Software. If applicable, validexemption documentation for each taxing jurisdiction

shall be providedto Juniper prior to invoicing, and Customer shall promptlynotify Juniper if their exemption is revoked or modified. All

payments made by Customer shall be net of any applicable withholding tax. Customer will provide reasonable assistance to Juniper in

connection with such withholding taxes by promptly: providing Juniper with validtax receipts and other required documentation showing

Customer’s payment of any withholding taxes; completing appropriate applications that would reduce the amount of withholding tax to

be paid; and notifying and assisting Juniper in any audit or tax proceeding related to transactions hereunder. Customer shall comply with

allapplicable tax laws and regulations, and Customerwill promptlypay or reimburse Juniper for allcosts and damages relatedto any

liability incurred by Juniper as a result of Customer’s non-compliance or delay with its responsibilities herein. Customer’s obligations under

this Section shall survive termination or expiration of this Agreement.

11. Export. Customer agrees to comply with all applicable export laws and restrictions and regulations of any United States and any

applicable foreign agency or authority, and not to export or re-export theSoftware or any direct productthereofin violation of any such

restrictions,laws or regulations, or without all necessary approvals. Customer shall be liable for any suchviolations. The version of the

Software supplied to Customer maycontain encryption or othercapabilities restricting Customer’s ability to export the Software without

an export license.

Copyright © 2010, Juniper Networks, Inc.iv


5/214

12. Commercial Computer Software. The Software is “commercial computer software” and is providedwith restricted rights. Use,

duplication, or disclosure bythe United States governmentis subject to restrictions setforthin this Agreement and asprovided in DFARS

227.7201 through 227.7202-4, FAR 12.212, FAR 27.405(b)(2), FAR 52.227-19, or FAR 52.227-14(ALT III) as applicable.

13. Interface Information. To the extent required by applicable law, and at Customer's written request,Juniper shall provide Customer

with the interface information needed to achieve interoperabilitybetween the Software and another independently created program, on

payment of applicable fee, if any. Customershall observe strict obligations of confidentiality with respect to suchinformation and shall use

such information in compliance with anyapplicable terms and conditions upon which Juniper makes suchinformation available.

14. Third Party Software. Anylicensor of Juniper whose software is embeddedin the Software andany supplier of Juniper whose products

or technology are embeddedin (or services areaccessed by)the Software shall be a third party beneficiary with respect to this Agreement,

and such licensoror vendorshall havethe right toenforce this Agreementin itsown name asif it wereJuniper. Inaddition, certain thirdparty

software may be providedwith theSoftware and is subject to theaccompanying license(s), if any, of itsrespectiveowner(s). To theextent

portions of theSoftware are distributed under and subject to open source licenses obligating Juniper to make thesource code forsuch

portions publicly available (such as the GNU General Public License (“GPL”) or the GNU Library General Public License (“LGPL”)), Juniper

will make such source code portions (including Juniper modifications, as appropriate) available upon request for a period of up to three

years from thedateof distribution. Such request can be made in writing to Juniper Networks, Inc.,1194N. Mathilda Ave., Sunnyvale, CA

94089, ATTN: General Counsel.You may obtaina copyof theGPL at http://www.gnu.org/licenses/gpl.html , and a copyof the LGPL

at http://www.gnu.org/licenses/lgpl.html .

15. Miscellaneous. This Agreement shall be governed by thelaws of theState of California without reference to its conflicts of laws

principles.The provisions of theU.N.Conventionfor theInternational Sale of Goods shall not apply to this Agreement.For any disputes

arising under this Agreement, theParties hereby consent to thepersonal and exclusive jurisdictionof, and venuein, the state and federal

courts within Santa Clara County, California.This Agreement constitutes the entire and soleagreement between Juniper and the Customer

with respect to the Software, and supersedes all prior and contemporaneous agreements relating to the Software, whether oral or written

(including any inconsistent terms contained in a purchase order), except that the terms of a separate written agreement executed by an

authorized Juniper representative and Customer shall govern to the extent such terms are inconsistent or conflict with terms contained

herein. No modification to this Agreement norany waiver of any rightshereundershallbe effective unlessexpressly assentedto in writing

by theparty to be charged. If any portion of this Agreement is held invalid, theParties agree that such invalidity shall not affect thevalidity

of the remainder of this Agreement. This Agreement and associated documentation has beenwritten in the English language, and the

Parties agree that the English version will govern. (For Canada: Les parties aux présentés confirment leurvolonté que cette convention de

mêmeque tousles documents y compris toutavis qui s'y rattaché,soient redigés en langue anglaise. (Translation: Theparties confirm that

this Agreement and allrelated documentation is and will be in theEnglish language)).

vCopyright © 2010, Juniper Networks, Inc.

http://www.gnu.org/licenses/gpl.htmlhttp://www.gnu.org/licenses/gpl.htmlhttp://www.gnu.org/licenses/lgpl.htmlhttp://www.gnu.org/licenses/lgpl.htmlhttp://www.gnu.org/licenses/gpl.html


6/214

Copyright © 2010, Juniper Networks, Inc.vi


7/214

Table of Contents

About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

SRX Series Documentation and Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii

Obtaining Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii

Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii

Requesting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii

Part 1 SRX Series Services Gateway Interface Overview

Chapter 1 Introduction to the SRX Series Services Gateway Interfaces . . . . . . . . . . . . . 3

SRX Series Services Gateway Interface Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3

SRX Series Services Gateway Mini-Physical Interface Modules Overview . . . . . . . 4

SRX Series Services Gateway Gigabit-Backplane Physical Interface Modules

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Supported SRX Series Services Gateway Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . 7

SRX Series Services Gateway Interfaces Models and Compatibility . . . . . . . . . . . . 8

MTU Default and Maximum Values for Physical Interface Modules . . . . . . . . . . . . 9

SRX Series Services Gateway Interfaces Power and Heat Requirements . . . . . . . 10

Power over Ethernet Support on SRX Series Services Gateway Interfaces . . . . . . 12

SRX Series Services Gateways Interfaces Port Naming Conventions . . . . . . . . . . . 13

Chapter 2 Installing and Removing Interfaces on the SRX Series Services

Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Replacing a Mini-Physical Interface Module in the SRX Series Services

Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Required Tools and Parts for Replacing a Mini-Physical Interface

Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Removing a Blank Mini-Physical Interface Module Faceplate from the SRX

Series Services Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Installing a Mini-Physical Interface Module in the SRX Series Services

Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

viiCopyright © 2010, Juniper Networks, Inc.


8/214

Removing a Mini-Physical Interface Module from the SRX Series Services

Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Replacing a Gigabit-Backplane Physical Interface Module in the SRX Series

Services Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Required Tools and Parts for Replacing a Gigabit-Backplane Physical

Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Preventing Electrostatic Discharge Damage to the SRX Series Services

Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Removing a Blank Gigabit-Backplane Physical Interface Module Faceplate

from the SRX Series Services Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Installing a Gigabit-Backplane Physical Interface Moduleon the SRX Series

Services Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Installinga Double-High, Double-Wide Gigabit-BackplanePhysical Interface

Module on the SRX Series Services Gateway . . . . . . . . . . . . . . . . . . . . . . 24

Removing a Gigabit-Backplane Physical Interface Module from the SRX

Series Services Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Part 2 Mini-Physical Interface Modules Supported on the SRX SeriesServices Gateway

Chapter 3 1-Port ADSL2+ Mini-Physical Interface Module . . . . . . . . . . . . . . . . . . . . . . . . 31

1-Port ADSL2+ Mini-Physical Interface Module Overview . . . . . . . . . . . . . . . . . . . . 31

1-Port ADSL2+ Mini-Physical Interface Module Hardware Specifications . . . . . . . 32

1-Port ADSL2+ Mini-Physical Interface Module Network Interface

Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

1-Port ADSL2+ Mini-Physical Interface Module Supported Standards . . . . . . . . . 35

1-Port ADSL2+ Mini-Physical Interface Module Key Features . . . . . . . . . . . . . . . . 35

1-Port ADSL2+ Mini-Physical Interface Module LEDs . . . . . . . . . . . . . . . . . . . . . . . 36

1-Port ADSL2+ Mini-Physical Interface Module Supported Loopback

Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

1-Port ADSL2+ Mini-Physical Interface Module Basic Configuration . . . . . . . . . . . 37

Using J-Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Using the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Chapter 4 1-Port DOCSIS Mini-Physical Interface Module . . . . . . . . . . . . . . . . . . . . . . . . 41

1-Port DOCSIS Mini-Physical Interface Module Overview . . . . . . . . . . . . . . . . . . . . 41

1-Port DOCSIS Mini-Physical Interface Module Key Features . . . . . . . . . . . . . . . . 42

1-Port DOCSIS Mini-Physical Interface Module Supported Standards . . . . . . . . . 43

1-Port DOCSIS Mini-Physical Interface Module Network Interface

Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

1-Port DOCSIS Mini-Physical Interface Module Hardware Specifications . . . . . . . 44

1-Port DOCSIS Mini-Physical Interface Module LEDs . . . . . . . . . . . . . . . . . . . . . . . 451-Port DOCSIS Mini-Physical Interface Module Basic Configuration . . . . . . . . . . . 46

Using J-Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Using the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Copyright © 2010, Juniper Networks, Inc.viii

SRX Series Services Gateways for the Branch Physical Interface Modules Hardware Guide


9/214

Chapter 5 1-Port Gigabit Ethernet SFP Mini-Physical Interface Module . . . . . . . . . . . . 49

1-Port Gigabit Ethernet SFP Mini-Physical Interface Module Overview . . . . . . . . . 49

1-Port Gigabit Ethernet SFP Mini-Physical Interface Module Hardware

Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

1-Port Gigabit Ethernet SFP Mini-Physical Interface Module Network Interface

Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

1-Port Gigabit Ethernet SFP Mini-Physical Interface Module Supported

Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

1-Port Gigabit Ethernet SFP Mini-Physical Interface Module Key Features . . . . . . 53

1-Port Gigabit Ethernet SFP Mini-Physical Interface Module LEDs . . . . . . . . . . . . 54

1-Port Gigabit Ethernet SFP Mini-Physical Interface Module Basic

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Using J-Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Using the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Chapter 6 1-Port G.SHDSL 8-Wire Mini-Physical Interface Module . . . . . . . . . . . . . . . . 59

1-Port G.SHDSL 8-Wire Mini-Physical Interface Module Overview . . . . . . . . . . . . 591-Port G.SHDSL 8-Wire Mini-Physical Interface Module Supported

Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

1-Port G.SHDSL 8-Wire Mini-Physical Interface Module Operating Modes . . . . . 60

1-Port G.SHDSL 8-Wire Mini-Physical Interface Module Key Features . . . . . . . . . . 61

1-Port G.SHDSL 8-Wire Mini-Physical Interface Module Hardware

Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

1-Port G.SHDSL 8-Wire Mini-Physical Interface Module LEDs . . . . . . . . . . . . . . . . 63

1-Port G.SHDSL 8-Wire Mini-Physical Interface Modules Basic Configuration . . . 64

Using J-Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Using the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Chapter 7 1-Port Serial Mini-Physical Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . 67

1-Port Serial Mini-Physical Interface Module Overview . . . . . . . . . . . . . . . . . . . . . 67

1-Port Serial Mini-Physical Interface Module Hardware Specifications . . . . . . . . . 68

1-Port Serial Mini-Physical Interface Module Supported Standards . . . . . . . . . . . 68

1-Port Serial Mini-Physical Interface Module Key Features . . . . . . . . . . . . . . . . . . 69

1-Port Serial Mini-Physical Interface Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . 69

1-Port Serial Mini-Physical Interface Module Interface Cables . . . . . . . . . . . . . . . 69

1-Port Serial Mini-Physical Interface Module Basic Configuration . . . . . . . . . . . . . 70

Using J-Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Using the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Chapter 8 1-Port SFP Mini-Physical Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

1-Port SFP Mini-Physical Interface Module Overview . . . . . . . . . . . . . . . . . . . . . . . 73

1-Port SFP Mini-Physical Interface Module Hardware Specifications . . . . . . . . . . 741-Port SFP Mini-Physical Interface Module Network Interface Specifications . . . . 74

1-Port SFP Mini-Physical Interface Module Supported Modules . . . . . . . . . . . . . . 75

1-Port SFP Mini-Physical Interface Module Key Features . . . . . . . . . . . . . . . . . . . . 76

1-Port SFP Mini-Physical Interface Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . 77

1-Port SFP Mini-Physical Interface Module Basic Configuration . . . . . . . . . . . . . . 78

Using J-Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Using the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

ixCopyright © 2010, Juniper Networks, Inc.

Table of Contents


10/214

Chapter 9 1-Port T1/E1 Mini-Physical Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . 81

1-Port T1/E1 Mini-Physical Interface Module Overview . . . . . . . . . . . . . . . . . . . . . . 81

1-Port T1/E1 Mini-Physical Interface Module Hardware Specifications . . . . . . . . . 82

1-Port T1/E1 Mini-Physical Interface Module Network Interface Specifications . . 82

1-Port T1/E1 Mini-Physical Interface Module Supported Standards . . . . . . . . . . . 83

1-Port T1/E1 Mini-Physical Interface Module Key Features . . . . . . . . . . . . . . . . . . . 84

1-Port T1/E1 Mini-Physical Interface Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . 84

1-Port T1/E1 Mini-Physical Interface Module Supported Loopback

Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

1-Port T1/E1 Mini-Physical Interface Module Basic Configuration . . . . . . . . . . . . . 86

Using J-Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Using the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Chapter 10 1-Port VDSL2 (Annex A) Mini-Physical Interface Module . . . . . . . . . . . . . . . 89

1-Port VDSL2 (Annex A) Mini-Physical Interface Module Overview . . . . . . . . . . . 89

1-Port VDSL2 (Annex A) Mini-Physical Interface Module Key Features . . . . . . . . 90

1-Port VDSL2 (Annex A) Mini-Physical Interface Module Supported Profiles . . . . 901-Port VDSL2 (Annex A) Mini-Physical Interface Module Hardware

Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

1-Port VDSL2 (Annex A) Mini-Physical Interface Module LEDs . . . . . . . . . . . . . . . 92

1-Port VDSL2 (Annex A) Mini-Physical Interface Module Basic Configuration . . . 93

Using J-Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Using the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Chapter 11 2-Port FXS/2-Port FXO Mini-Physical Interface Module . . . . . . . . . . . . . . . . 95

2-Port FXS/2-Port FXO Mini-Physical Interface Module Overview . . . . . . . . . . . . 95

2-Port FXS/2-Port FXO Mini-Physical Interface Module Key Features . . . . . . . . . 96

2-Port FXS/2-Port FXO Mini-Physical Interface Module Hardware

Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

2-Port FXS/2-Port FXO Mini-Physical Interface Module LEDs . . . . . . . . . . . . . . . . 97

2-Port FXS/2-Port FXO Mini-Physical Interface Module Basic Configuration . . . . 98

Chapter 12 4-Port FXO Mini-Physical Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . 99

4-Port FXO Mini-Physical Interface Module Overview . . . . . . . . . . . . . . . . . . . . . . 99

4-Port FXO Mini-Physical Interface Module Hardware Specifications . . . . . . . . 100

4-Port FXO Mini-Physical Interface Module Key Features . . . . . . . . . . . . . . . . . . 100

4-Port FXO Mini-Physical Interface Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . 101

4-Port FXO Mini-Physical Interface Module Basic Configuration . . . . . . . . . . . . . 102

Chapter 13 4-Port FXS Mini-Physical Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . 103

4-Port FXS Mini-Physical Interface Module Overview . . . . . . . . . . . . . . . . . . . . . 103

4-Port FXS Mini-Physical Interface Module Hardware Specifications . . . . . . . . . 104

4-Port FXS Mini-Physical Interface Module Key Features . . . . . . . . . . . . . . . . . . 104

4-Port FXS Mini-Physical Interface Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . 105

4-Port FXS Mini-Physical Interface Module Basic Configuration . . . . . . . . . . . . . 105

Copyright © 2010, Juniper Networks, Inc.x



11/214

Part 3 Gigabit-Backplane Physical Interface Modules Supported onthe SRX Series Services Gateway

Chapter 14 2-Port 10 Gigabit Ethernet XPIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

2-Port 10 Gigabit Ethernet XPIM Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1092-Port 10 Gigabit Ethernet XPIM Key Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

2-Port 10 Gigabit Ethernet XPIM Hardware Specifications . . . . . . . . . . . . . . . . . . . 111

2-Port 10 Gigabit Ethernet XPIM LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

2-Port 10 Gigabit Ethernet XPIM Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

2-Port 10 Gigabit Ethernet XPIM Basic Configuration . . . . . . . . . . . . . . . . . . . . . . 115

Using J-Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Using the Point and Click CLI to Set Interface Mode and Speed Options . . . 116

Using the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Chapter 15 16-Port Gigabit Ethernet XPIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

16-Port Gigabit Ethernet XPIM Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

16-Port Gigabit Ethernet XPIM Key Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

16-Port Gigabit Ethernet XPIM Hardware Specifications . . . . . . . . . . . . . . . . . . . 120

16-Port Gigabit Ethernet XPIM LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

16-Port Gigabit Ethernet XPIM Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

16-Port Gigabit Ethernet XPIM Basic Configuration . . . . . . . . . . . . . . . . . . . . . . . . 123

Using J-Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Using the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Chapter 16 24-Port Gigabit Ethernet XPIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

24-Port Gigabit Ethernet XPIM Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

24-Port Gigabit Ethernet XPIM Key Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

24-Port Gigabit Ethernet XPIM Hardware Specifications . . . . . . . . . . . . . . . . . . . 129

24-Port Gigabit Ethernet XPIM LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

24-Port Gigabit Ethernet XPIM Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13124-Port Gigabit Ethernet XPIM Basic Configuration . . . . . . . . . . . . . . . . . . . . . . . 133

Using J-Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Using the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Chapter 17 Dual CT1/E1 GPIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Dual CT1/E1 GPIM Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Dual CT1/E1 GPIM Key Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Dual CT1/E1 GPIM Network Interface Specifications . . . . . . . . . . . . . . . . . . . . . . . 138

Dual CT1/E1 GPIM Hardware Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Dual CT1/E1 GPIM LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Dual CT1/E1 GPIM Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Dual CT1/E1 GPIM Basic Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Using J-Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Using the CLI to Configure the CT1 Interface . . . . . . . . . . . . . . . . . . . . . . . . . 142

Using the CLI to Configure the CE1 Interface . . . . . . . . . . . . . . . . . . . . . . . . . 143

Chapter 18 Quad CT1/E1 GPIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Quad CT1/E1 GPIM Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Quad CT1/E1 GPIM Key Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Quad CT1/E1 GPIM Network Interface Specifications . . . . . . . . . . . . . . . . . . . . . . 146

Quad CT1/E1 GPIM Hardware Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

xiCopyright © 2010, Juniper Networks, Inc.

Table of Contents


12/214

Quad CT1/E1 GPIM LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Quad CT1/E1 GPIM Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Quad CT1/E1 GPIM Basic Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Using J-Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Using the CLI to Configure the CT1 Interface . . . . . . . . . . . . . . . . . . . . . . . . . 150

Using the CLI to Configure the CE1 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Part 4 Appendixes

Appendix A SRX Series Services Gateways Interface Cable Specifications and

Connector Pinouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

1-Port T1/E1 Mini-Physical Interface Module Cable Specifications . . . . . . . . . . . . 155

RJ-48 Connector to RJ-48 Connector (Straight) Pinouts for the 1-Port T1/E1

Mini-Physical Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

RJ-48 Connector to RJ-48 Connector (Crossover) Pinouts for the 1-Port

T1/E1 Mini-Physical Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

RJ-48 Connector to DB-15 Connector (Straight) Pinouts for the 1-PortT1/E1Mini-Physical Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

RJ-48 Connector to DB-15 Connector (Crossover) Pinouts for the 1-Port

T1/E1 Mini-Physical Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

1-Port ADSL2+ Mini-Physical Interface Module Cable Specifications . . . . . . . . . 159

RJ-11 Connector Pinouts for the 1-Port ADSL2+ Mini-Physical Interface

Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

FXO/FXS Mini-Physical Interface Module Cable Specifications . . . . . . . . . . . . . . 160

RJ-11 Connector Pinouts for the FXO/FXS Mini-Physical Interface

Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

1-Port Serial Mini-Physical Interface Module Cable Specifications . . . . . . . . . . . 160

EIA-530A DCE Cable Pinouts for the 1-Port Serial Mini-Physical Interface

Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

EIA-530A DTE Cable Pinouts for the 1-Port Serial Mini-Physical Interface

Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

RS-232 DCE Cable Pinouts for the 1-Port Serial Mini-Physical Interface

Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

RS-232 DTE Cable Pinouts for the 1-Port Serial Mini-Physical Interface

Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

RS-422/449(EIA-449) DCECable Pinoutsforthe 1-Port SerialMini-Physical

Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

RS-422/449(EIA-449)DTE Cable Pinouts forthe 1-Port Serial Mini-Physical

Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

V.35 DCE Cable Pinouts for the 1-Port Serial Mini-Physical Interface

Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

V.35 DTE Cable Pinouts for the 1-Port Serial Mini-Physical Interface

Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

X.21 DCE Cable Pinouts for the 1-Port Serial Mini-Physical Interface

Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Copyright © 2010, Juniper Networks, Inc.xii



13/214

X.21 DTE Cable Pinouts for the 1-Port Serial Mini-Physical Interface

Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

1-Port G.SHDSL Mini-Physical Interface Module Cable Specifications . . . . . . . . . 176

1-Port G.SHDSL 8-Wire Mini-PIM Wire Modes . . . . . . . . . . . . . . . . . . . . . . . . 176

RJ-45 Cable (RJ-45 to Four RJ-11 Connectors) Pin Assignment . . . . . . . . . . 178

RJ-45 Cable (RJ-45 to Two RJ-11 Connectors) Pin Assignment . . . . . . . . . . . 179

Standard RJ-45 Cable Pin Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

1-Port VDSL2 (Annex A) Mini-Physical Interface Module Cable

Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Appendix B ContactingCustomer SupportandReturning SRX SeriesServices Gateway

Hardware Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Return Procedure for SRX Series Services Gateway Hardware Components . . . 183

Locating the SRX Series Services Gateway Hardware Component Mini-PIM or

GPIM Serial Number Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

SRX Series Services Gateway Mini-PIM Serial Number Label . . . . . . . . . . . . 184

SRX Series Services Gateway GPIM Serial Number Label . . . . . . . . . . . . . . . 184

Information You Might Need to Supply to JTAC . . . . . . . . . . . . . . . . . . . . . . . . . . 184

Contacting Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Packing the Hardware Components for Shipment . . . . . . . . . . . . . . . . . . . . . . . . 186

Part 5 Index

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

xiiiCopyright © 2010, Juniper Networks, Inc.

Table of Contents


14/214

Copyright © 2010, Juniper Networks, Inc.xiv



15/214

About This Guide

• Objectives on page xv

• Audience on page xv

• Documentation Conventions on page xv

• SRX Series Documentation and Release Notes on page xvii

• Obtaining Documentation on page xvii

• Documentation Feedback on page xviii

• Requesting Technical Support on page xviii

Objectives

This guide describes hardware components and installation, basic configuration, and

basic troubleshooting procedures for the Juniper NetworksSRX Series Services Gateway

interfaces. It explains how to prepare your site for services gateway installation, unpack

and install the hardware, power on the services gateway, perform initial software

configuration, and perform routine maintenance. After completing the installation and

basic configuration procedures covered in this guide, see the Junos OS configuration

guides for information about further Junos OS configuration.

Audience

This guide is designed for network administrators who are installing and maintaining

Juniper Networks SRX Series Services Gateway interfaces or preparing a site for device

installation. To use this guide, you need a broad understanding of networks and the

Internet, networking principles, and network configuration. Any detailed discussion of

these concepts is beyond the scope of this guide.

Documentation Conventions

Table 1 on page xvi defines the notice icons used in this guide.

xvCopyright © 2010, Juniper Networks, Inc.


16/214

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 tothe risk of personal injury or death.Warning

Alerts you tothe risk of personal injury from a laser.Laser warning

Table 2 on page xvi 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 SystemBasics Configuration

Guide

• RFC 1997,BGPCommunities Attribute

• Introduces important new terms.

• Identifies book names.

• Identifies RFC and Internet draft titles.

Italic text like this

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 areaarea-id] hierarchy level.

• Theconsole portis labeledCONSOLE.

Represents names of configuration

statements, commands, files, and

directories; IP addresses; configuration

hierarchy levels; or labels on routing

platform components.

Text like this

stub ;Enclose optional keywords or variables.< > (angle brackets)

Copyright © 2010, Juniper Networks, Inc.xvi



17/214

Table 2: Text and Syntax Conventions (continued)

ExamplesDescriptionConvention

broadcast | multicast

( string1 | string2 | string3)

Indicates a choicebetween the mutuallyexclusive keywordsor variables on either

side of the symbol. The set of choices is

often enclosed in parentheses for clarity.

| (pipe symbol)

rsvp { # Required fordynamic MPLS onlyIndicates a comment specified on the

sameline asthe configuration statement

to which it applies.

# (pound sign)

communityname members[

community-ids ]

Enclose a variable for which you can

substitute one or more values.

[ ] (square brackets)

[edit]

routing-options {

static {route default {

nexthop address;

retain;

}

}

}

Identify a level in the configuration

hierarchy.

Indention and braces( { } )

Identifies a leaf statement at a

configuration hierarchy level.

; (semicolon)

J-Web GUI Conventions

• In the Logical Interfaces box, select

All Interfaces.

• To cancel the configuration, click

Cancel.

Represents J-Web graphical user

interface (GUI) items you click or select.

Bold text like this

In the configuration editor hierarchy,select Protocols>Ospf.

Separates levels in a hierarchy of J-Webselections.

> (bold right angle bracket)

SRX Series Documentation and Release Notes

For a list of related SRX Series documentation, see

http://www.juniper.net/techpubs/hardware/srx-series-main.html. If the information in the

latest Junos OS Release Notesdiffers from the information in the documentation, follow

the Junos OS Release Notes.

Obtaining Documentation

To obtain the most current version of all Juniper Networks technical documentation, seethe products documentation page on the Juniper Networks website at

http://www.juniper.net/techpubs.

To order printed copies of this guide and other Juniper Networks technical documents,

contact your sales representative.

Copies of the Management Information Bases (MIBs) available in a software release are

included on the documentation CDs and at http://www.juniper.net.

xviiCopyright © 2010, Juniper Networks, Inc.

About This Guide

http://www.juniper.net/techpubs/hardware/srx-series-main.htmlhttp://www.juniper.net/techpubs.http://www.juniper.net./http://www.juniper.net./http://www.juniper.net/techpubs.http://www.juniper.net/techpubs/hardware/srx-series-main.html


18/214

Documentation Feedback

We encourage you to provide feedback, comments, and suggestions so that we can

improve the documentation. You can send your comments to

[email protected], or fill out the documentation feedback form at

http://www.juniper.net/techpubs/docbug/docbugreport.html . If you are using e-mail, be

sure to include the following information with your comments:

• Document name

• Document part number

• Page number

• Software release version (not required for NetworkOperationsGuides [NOGs])

Requesting Technical Support

Technical productsupport is availablethrough the Juniper Networks TechnicalAssistance

Center (JTAC). If you are a customer with an active J-Care or JNASC support contract,

or are covered under warranty, and need postsales 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

http://www.juniper.net/customers/support/downloads/710059.pdf .

• Product warranties—For product warranty information, visit

http://www.juniper.net/support/warranty/ .

• JTAC Hours of Operation—The JTAC centers have resources available 24 hours a day,7 daysa 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:

• Find CSC offerings: http://www.juniper.net/customers/support/

• Find product documentation: http://www.juniper.net/techpubs/

• Download the latest versions of software and review release notes:

http://www.juniper.net/customers/csc/software/

• Find solutions and answer questions using our Knowledge Base: http://kb.juniper.net/

• Search technical bulletins for relevant hardware and software notifications:

https://www.juniper.net/alerts/

Copyright © 2010, Juniper Networks, Inc.xviii


http://www.juniper.net/techpubs/docbug/docbugreport.htmlhttp://www.juniper.net/customers/support/downloads/710059.pdfhttp://www.juniper.net/support/warranty/http://www.juniper.net/customers/support/http://www.juniper.net/techpubs/http://www.juniper.net/customers/csc/software/http://kb.juniper.net/https://www.juniper.net/alerts/https://www.juniper.net/alerts/http://kb.juniper.net/http://www.juniper.net/customers/csc/software/http://www.juniper.net/techpubs/http://www.juniper.net/customers/support/http://www.juniper.net/support/warranty/http://www.juniper.net/customers/support/downloads/710059.pdfhttp://www.juniper.net/techpubs/docbug/docbugreport.html


19/214

• Join and participate in the Juniper Networks Community Forum:

http://www.juniper.net/company/communities/

• Open a case online in the CSC Case Manager: http://www.juniper.net/cm/

To verify service entitlementby productserial number, use our Serial NumberEntitlement

(SNE) Tool located at https://tools.juniper.net/SerialNumberEntitlementSearch/.

Opening a Case with JTAC

You can open a case with JTAC on the Web or by telephone.

• Use the Case Manager tool in the CSC at http://www.juniper.net/cm/ .

• 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, visit us at

http://www.juniper.net/support/requesting-support.html .

xixCopyright © 2010, Juniper Networks, Inc.

About This Guide

http://www.juniper.net/company/communities/http://www.juniper.net/cm/https://tools.juniper.net/SerialNumberEntitlementSearch/http://www.juniper.net/cm/http://www.juniper.net/support/requesting-support.htmlhttp://www.juniper.net/support/requesting-support.htmlhttp://www.juniper.net/cm/https://tools.juniper.net/SerialNumberEntitlementSearch/http://www.juniper.net/cm/http://www.juniper.net/company/communities/


20/214

Copyright © 2010, Juniper Networks, Inc.xx



21/214

PART 1

SRX Series Services Gateway InterfaceOverview

• Introduction to the SRX Series Services Gateway Interfaces on page 3

• Installing and Removing Interfaces on the SRX Series Services Gateway on page 15

1Copyright © 2010, Juniper Networks, Inc.


22/214

Copyright © 2010, Juniper Networks, Inc.2



23/214

CHAPTER 1

Introduction to the SRX Series ServicesGateway Interfaces

• SRX Series Services Gateway Interface Overview on page 3

•

SRX Series Services Gateway Mini-Physical Interface Modules Overview on page 4• SRX Series Services Gateway Gigabit-Backplane Physical Interface Modules

Overview on page 5

• Supported SRX Series Services Gateway Interfaces on page 7

• SRX Series Services Gateway Interfaces Models and Compatibility on page 8

• MTU Default and Maximum Values for Physical Interface Modules on page 9

• SRX Series Services Gateway Interfaces Power and Heat Requirements on page 10

• Power over Ethernet Support on SRX Series Services Gateway Interfaces on page 12

• SRX Series Services Gateways Interfaces Port Naming Conventions on page 13

SRX Series Services Gateway Interface Overview

Mini-Physical Interface Modules (Mini-PIMs) and Gigabit-Backplane Physical Interface

Modules (GPIMs) are field-replaceable network interface cards (NICs) supported on the

Juniper Networks SRX Series Services Gateway for the branch. You can easily insert or

remove Mini-PIMs and GPIMs from the front slots of the SRX Series Services Gateway

chassis. The Mini-PIMs and GPIMs provide physical connections to a LAN or a WAN. The

Mini-PIMs and GPIMs receive incoming packets from the network and transmit outgoing

packets to thenetwork. During thisprocess,they performframing andline-speed signaling

for the medium type. The SRX Series Services Gateways run Junos OS.

CAUTION: The Mini-PIMs available on the SRX Series Services Gateway are

not hot-swappable. You must power off the device before removing orinstalling Mini-PIMs.

NOTE: GPIMs are hot-swappable.



24/214

Related

Documentation

SRX Series Services Gateway Mini-Physical Interface Modules Overview on page 4•

• SRX Series Services Gateway Gigabit-BackplanePhysical Interface Modules Overview

onpage 5


SRX Series Services Gateway Mini-Physical Interface Modules Overview

A Mini-Physical Interface Module (Mini-PIM) is a network interface card (NIC) that is

installed on the SRX Series Services Gateway to provide physical connections to a LAN

or a WAN. The Mini-PIM receives incoming packets from the network and transmits

outgoing packets to the network.

Table 3 on page 4 lists the Mini-PIMs and their model numbers.

Table 3: SRX Series Services Gateway Mini-PIMs Model Numbers

Model NumbersMini-PIMs

SRX-MP-1SFP1-Port Small Form-Factor Pluggable (SFP)

SRX-MP-1SFP-GE1-Port Gigabit Ethernet Small Form-Factor

Pluggable (SFP)

SRX-MP-VA222-Port Foreign Exchange Station (FXS)/2-Port

Foreign Exchange Office (FXO)

SRX-MP-VA044-Port Foreign Exchange Office (FXO)

SRX-MP-VA404-Port Foreign Exchange Station (FXS)

SRX-MP-1ADSL2-A (Annex A)

SRX-MP-1ADSL2-B (Annex B)

ADSL2+

SRX-MP-1DOCSIS3DOCSIS

SRX-MP-8GSHDSLG.SHDSL

SRX-MP-1SerialSerial

SRX-MP-1T1E1T1/E1

SRX-MP-1VDSL2-A (Annex A)VDSL2 (Annex A)

The Mini-PIMs supported on the SRX Series Services Gateway are field-replaceable. You

can install a Mini-PIM into the Mini-PIM slot on the front panel of the services gateway

chassis.




25/214


not hot-swappable. You must power off the device before removing or

installing Mini-PIMs.

Related

Documentation

Supported SRX Series Services Gateway Interfaces on page 7•




SRX Series Services Gateway Gigabit-Backplane Physical Interface Modules Overview

A Gigabit-Backplane Physical Interface Module (GPIM) is a network interface card (NIC)

that installs in the front slots of the SRX650 Services Gateway to provide physical

connections to a LAN or a WAN. The GPIM receives incoming packets from a network

and transmits outgoing packets to a network. These modules will complement the

onboard Ethernet interfaces to extend the types andport counts of network connections

for the LAN or WAN.

Interface module terminology:

• GPIM—TheGigabit-Backplane Physical Interface Module (GPIM) is a network interface

card (NIC) that installs in a single-high, single-wide GPIM front slot of the SRX650

Services Gateway that has gigabit connectivity to the system backplane.

• XPIM—The XPIM (10 Gigabit Ethernet GPIM) can be installed only in the 20-gigabit

GPIM slots (slots 2 and 6 on the front panel). It can haveone of the followingconfigurations:

• Single-high, single-wide LAN switch GPIM that uses one slot

• Double-high, single-wide LAN switch GPIM that uses two standard slots vertically

• Double-high, double-wide LAN switch GPIM that uses two standard slots vertically

and two standard slots horizontally

NOTE: Wheninstalling the 24-Port Gigabit Ethernet XPIM,which usesfour

slots, you must install it in the 20-gigabit GPIM slots 2 and 6, which refer,

tothe bottom four slots 1 to 4, or the top four slots 5 to 8.

Table 4 on page 5 lists the GPIMs and XPIMs and their model numbers.

Table 4: SRX Series Services Gateway GPIM/XPIMs Model Numbers

Model NumbersGPIM/XPIMs

SRX-GP-DUAL-T1-E1Dual CT1/E1 GPIM


Chapter 1: Introduction to the SRX Series Services Gateway Interfaces


26/214

Table 4: SRX Series Services Gateway GPIM/XPIMs ModelNumbers (continued)

Model NumbersGPIM/XPIMs

SRX-GP-QUAD-T1-E1Quad CT1/E1 GPIM

SRX-GP-2XE-SFPP-TX2-Port 10 Gigabit Ethernet XPIM

SRX-GP-16GE

SRX-GP-16GE-POE

16-Port Gigabit Ethernet XPIM

16-Port GigabitEthernet XPIM (with PoE)

SRX-GP-24GE

SRX-GP-24GE-POE


24-Port Gigabit Ethernet XPIM (with PoE)

Figure 1 on page 6 shows how the slots on the front panel of the SRX650 Services

Gateway are numbered.

Figure 1: SRX650 Services Gateway Slot Numbers

650

g 0 3 2 7 0 1

87

5

3

1

6

4

2

NOTE: GPIMs/XPIMs are hot-swappable. Because the services gateway

GPIMs communicate with the backplane at various performance levels, you

must install them in the correct slots.

Figure 2 on page 6, Figure 3 on page 6, and Figure 4 on page 7 show the three form

factors for the services gateway GPIMs.

Figure 2: Example of a Standard GPIM (Installs in One Standard Slot)

g 0 3 2 7 2 1

Figure 3: Example of a Double-High, Single-Wide XPIM

g 0 3 2 7 2 3




27/214

Figure 4: Example of a Double-High, Double-Wide XPIM

g 0 3 2 7 2 4

Related

Documentation

RequiredTools and Parts for Replacing a Gigabit-Backplane Physical Interface Module

on page 20

•

• Removing a Blank Gigabit-Backplane Physical Interface Module Faceplate from the

SRX Series Services Gateway on page 22

• Installing a Gigabit-Backplane Physical Interface Module on the SRX Series Services

Gateway on page 22

• Installing a Double-High, Double-Wide Gigabit-Backplane Physical Interface Module

on the SRX Series Services Gateway on page 24

Supported SRX Series Services Gateway Interfaces

TheSRX Series ServicesGatewayssupportthe following Mini-Physical Interface Modules

(Mini-PIMs):

• 1-Port Small Form-Factor Pluggable (SFP)

• 1-Port Gigabit Ethernet Small Form-Factor Pluggable (SFP)

• 2-Port Foreign Exchange Station (FXS)/2-Port Foreign Exchange Office (FXO)

• 4-Port FXO

• 4-Port FXS

• ADSL2+

• DOCSIS

• G.SHDSL

• Serial

• T1/E1

• VDSL2

The SRX Series Services Gateways support the following Gigabit-Backplane Physical

Interface Modules (GPIMs/XPIMs):

• Dual CT1/E1 GPIM

• Quad CT1/E1 GPIM

• 2-Port 10 Gigabit Ethernet XPIM




28/214

• 16-Port Gigabit Ethernet XPIM (with PoE)

• 24-Port Gigabit Ethernet XPIM (with PoE)

RelatedDocumentation



onpage 5


SRX Series Services Gateway Interfaces Models and Compatibility

Table 5 on page 8 shows the types of Mini-Physical Interface Modules (Mini-PIMs) with

the SRX Series devices and the Junos OS releases that support them.

Table 5: Mini-PIM Types and Hardware Platform Compatibility

Supported Platforms and Minimum Supported Junos OS Release

Name SRX240SRX220SRX210

Junos OS Release9.4N/A (Not Supported)Junos OS Release 9.41-Port Small

Form-Factor

Pluggable (SFP)

Junos OS Release10.4Junos OS Release 10.4Junos OS Release 10.41-Port Gigabit

Ethernet Small

Form-Factor

Pluggable (SFP)

JunosOS Release10.0N/A (Not Supported)Junos OS Release 10.02-Port Foreign

Exchange Station

(FXS)/2-Port

Foreign Exchange

Office (FXO)

JunosOS Release10.0N/A (Not Supported)Junos OS Release 10.04-Port FXO

Junos OS Release 10.2N/A (Not Supported)Junos OS Release 10.24-Port FXS

Junos OS Release9.5Junos OS Release 10.3Junos OS Release 9.5ADSL2+

Junos OS Release10.1Junos OS Release 10.3Junos OS Release 10.1DOCSIS

JunosOS Release10.0Junos OS Release 10.3Junos OS Release 10.0G.SHDSL

Junos OS Release9.5Junos OS Release 10.3Junos OS Release 9.5Serial

Junos OS Release9.4Junos OS Release 10.3Junos OS Release 9.4T1/E1

Junos OS Release10.1Junos OS Release 10.3Junos OS Release 10.1VDSL2




29/214

Table 6 on page 9 shows the types of Gigabit-Backplane Physical Interface Modules

(GPIMs and XPIMs), along with the SRX Series devices and the Junos OS Releases that

support them.

Table 6: GPIM and XPIM Types and Hardware Platform Compatibility

MinimumSupportedJunos

OS ReleaseSRX650NameType

Junos OS Release 9.5YesDual CT1/E1GPIMs

Junos OS Release 9.5YesQuad CT1/E1

Junos OS Release 9.5Yes16-Port GigabitEthernetXPIMs (Gigabit

Ethernet GPIM)

Junos OS Release 9.5Yes24-Port Gigabit

Ethernet

Junos OS Release 10.2Yes2-Port 10 Gigabit

Ethernet

NOTE: All Mini-PIMs, GPIMs, and XPIMs require the Junos operating system.

Related

Documentation



onpage 5



MTU Default and Maximum Values for Physical Interface Modules

Table 7 on page 9 lists maximum transmission unit (MTU) values for the SRX Series

Services Gateways Physical Interface Modules (PIMs).

Table 7: MTU Values for the SRX Series Services Gateways PIMs

Maximum MTU(Bytes)

Default MTU(Bytes)

Logical

Interface MTU(Bytes)

Physical

Interface MTU(Bytes)PIM

90101514150015141-Port Gigabit

Ethernet Small

Form-Factor

Pluggable (SFP)

Mini-PIM




30/214

Table 7: MTU Values for the SRX Series Services GatewaysPIMs (continued)

Maximum MTU(Bytes)Default MTU(Bytes)

Logical

Interface MTU(Bytes)

Physical

Interface MTU(Bytes)PIM

15181514150015141-Port Small

Form-Factor

Pluggable (SFP)

Mini-PIM

1512149614561496ADSL2+

Mini-PIM

1504150415001504DOCSIS

Mini-PIM

4482149614681496G.SHDSLMini-PIM

2000150415001504Serial Mini-PIM

2000150415001504T1/E1 Mini-PIM

1496149614821496VDSL2 Mini-PIM

9000150415001504Dual CT1/E1

GPIM

9000150415001504Quad CT1/E1

GPIM

Unspecified1514Unspecified15142-Port 10 Gigabit

Ethernet XPIM

Unspecified1514Unspecified151416-Port Gigabit

Ethernet XPIM

Unspecified1514Unspecified151424-Port Gigabit

Ethernet XPIM

Related

Documentation


•

Supported SRX Series Services Gateway Interfaces on page 7


SRX Series Services Gateway Interfaces Power and Heat Requirements

Table 8 on page 11 shows the power consumption values of each Physical Interface

Module (PIM).




31/214

Table 8: PIM Power Consumption Values

Power Consumption(Watts)PIM Model

4.291-Port Small Form-Factor Pluggable (SFP) Mini-PIM

3.181-Port Gigabit Ethernet Small Form-Factor Pluggable (SFP)

Mini-PIM

14.142-Port Foreign Exchange Station (FXS)/2-Port Foreign

Exchange Office (FXO) Mini-PIM

2.474-Port FXO Mini-PIM

124-Port FXS Mini-PIM

4.11ADSL2+ Mini-PIM

7.00DOCSIS Mini-PIM

8.31G.SHDSL Mini-PIM

4.29Serial Mini-PIM

1.92T1/E1 Mini-PIM

9.80VDSL2 Mini-PIM

16.81Dual CT1/E1 GPIM

16.81Quad CT1/E1 GPIM

202-Port 10 Gigabit Ethernet XPIM

40 (without PoE)16-Port Gigabit Ethernet XPIM

40 (without PoE)24-Port Gigabit Ethernet XPIM

Related

Documentation



onpage 5







32/214

Power over Ethernet Support on SRX Series Services Gateway Interfaces

Power over Ethernet (PoE) supports the implementation of the IEEE 802.3 af and IEEE

802.3 at standards, which allow both data and electric power to pass over a copper

Ethernet LAN cable.

The SRX650 Services Gateway provides PoE ports, which supply electric powerover the

same ports that are used for connecting 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 SRX650 Services Gateway reside on the individual XPIMs. The

SRX650 Services Gateway supports the following XPIMs with PoE:

• 16-Port Gigabit Ethernet XPIM

•


The active 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 9 on page 12 lists the SRX650 Services Gateway PoE specifications.

Table 9: SRX650 Services Gateway PoE Specifications

ValuesPower ManagementSchemes

• IEEE 802.3 af

• IEEE 802.3 at

• Legacy

Supported standards

PoE is supported on the following front panel slots:

• 2

• 4

• 6

• 8

Supported slots

The 645 W ACand 645 W DC power supplies support the

following capacities:

• 255 W @PoE on a singlepower supply, or with redundancy

using the two-power-supply option

• 510 W @PoEusing the two-power-supply option operating

as nonredundant

Total PoE power sourcing

capacity

31.2 WPer-port power limit

• Static: Power allocation for each interface can be

configured.

• Class: Power forinterfacesis allocated based on the class

of powered device connected.

Power management modes




33/214

Related

Documentation

SRX Series Services Gateway Gigabit-BackplanePhysical Interface Modules Overview

onpage 5

•

• 16-Port Gigabit Ethernet XPIM Overview on page 119

• 24-Port Gigabit Ethernet XPIM Overview on page 127

• Installing a Gigabit-Backplane Physical Interface Module on the SRX Series Services

Gateway on page 22

• Installing a Double-High, Double-Wide Gigabit-Backplane Physical Interface Module

on the SRX Series Services Gateway on page 24

SRX Series Services Gateways Interfaces Port Naming Conventions

When configuring a port on a Mini-Physical Interface Module (Mini-PIM) or

Gigabit-Backplane Physical Interface Module (GPIM), you must know the slot and port

numberassigned bythe system. Theslotnumber identifies thesloton thedevice in whichyou insertthe Mini-PIMor GPIM, and istypically named 1,2, 3,and soon. The portnumber

is the port on the Mini-PIM or GPIM that is being configured.

The name of each network interface has the following format to identify the physical

device that corresponds to a single physical network connector:

type-slot/pim/port

For SRX Series Services Gateways, pim equals 0 for the port-naming convention.

Table 10 on page 13 lists the typical interface names and port numbers.

Table 10: SRX Series Services Gateway Interface Port Numbers

Port NumberInterface

at-0/0/0ATM-over-ADSL

at-1/0/0G.SHDSL

t1-1/0/0T1

e1-1/0/0E1

ge-1/0/01-Port SFP

ge-1/0/01-Port Gigabit Ethernet SFP

se- pim/0/ port (se-1/0/0 to se-4/0/0)Serial

fxs-0/0/0FXS

fxo-0/0/0FXO




34/214

Table 10: SRX Series Services Gateway Interface PortNumbers (continued)

Port NumberInterface

cm-1/0/0DOCSIS

pt-1/0/0VDSL2

ge-1/0/016-Port Gigabit Ethernet XPIM

ge-2/0/024-Port Gigabit Ethernet XPIM

xe-2/0/0, xe-2/0/1, or

xe-6/0/0, xe-6/0/1

NOTE: Must be installed in 20-gigabit GPIM

slot 2 or 6. Represents two fiber andtwo

copper ports; user configured.

2-Port 10 Gigabit Ethernet XPIM

ct1-1/0/0

ce1-1/0/0

Dual CT1/E1 GPIM

ct1-1/0/0

ce1-1/0/0

Quad CT1/E1 GPIM

Related

Documentation

• SRX Series Services Gateway Mini-Physical Interface Modules Overview on page 4


onpage 5







35/214

CHAPTER 2

Installing and Removing Interfaces on theSRX Series Services Gateway

• Replacing a Mini-Physical Interface Module in the SRX Series Services

Gateway on page 15

• Replacing a Gigabit-Backplane Physical Interface Module in the SRX Series Services

Gateway on page 20

Replacing a Mini-Physical Interface Module in the SRX Series Services Gateway

• Required Tools and Parts for Replacing a Mini-Physical Interface Module on page 15

• Removing a Blank Mini-Physical Interface Module Faceplate from the SRX Series

Services Gateway on page 16

• Installing a Mini-Physical Interface Module in the SRX Series Services

Gateway on page 17

• Removing a Mini-Physical Interface Module from the SRX Series Services

Gateway on page 18

Required Tools and Parts for Replacing a Mini-Physical Interface Module

The following tools and parts are required for replacing Mini-Physical Interface Modules

(Mini-PIMs) on the SRX Series Services Gateway:

• Electrostatic bag or antistatic mat, for each component

• Electrostatic discharge (ESD) grounding wrist strap

• Flat blade (–) screwdriver, approximately 1/8 in. (3 mm)

• Phillips (+) screwdrivers, number 1

Related

Documentation

Removing a Blank Mini-Physical Interface Module Faceplate from the SRX Series

Services Gateway on page 16

•

• Installing a Mini-Physical Interface Module in the SRX Series Services Gateway on

page 17

• Removing a Mini-Physical Interface Module from the SRX Series Services Gateway on

page 18



36/214


Removing a Blank Mini-Physical Interface Module Faceplate from the SRX Series Services

Gateway

To maintain proper airflow through the services gateway, a blank faceplate should cover

any empty Mini-Physical Interface Module (Mini-PIM) slot.

CAUTION: Do not remove a blank faceplate unless you are installing a

Mini-PIM in the empty slot.




To remove a blank faceplate from the SRX Series Services Gateway:

1. Attachan electrostatic discharge (ESD)grounding strap to your bare wrist, andconnect

the strap to the ESD point on the device.

2. If the device is powered on, power off the device. Verify that the Power LED is off.

3. Loosen the screws on each side of the faceplate.

• On faceplates with handles, use a 1/8-in. (3-mm) flat-blade (–) screwdriver to

loosen but not remove the captive screws.

•

On faceplates without handles, use a number 1 Phillips screwdriver to remove thenoncaptive screws.

4. Remove the faceplate. See Figure 5 on page 16.

Figure 5: Removing a Blank Mini-PIM Faceplate from an SRX SeriesServices Gateway

Related

Documentation

Required Tools and Parts for Replacing a Mini-Physical Interface Module on page 15•




37/214

• Installing a Mini-Physical Interface Module in the SRX Series Services Gateway on

page 17

• Removing a Mini-Physical Interface Module from the SRX Series Services Gateway on

page 18


Installing a Mini-Physical Interface Module in the SRX Series Services Gateway




To install a Mini-Physical InterfaceModule(Mini-PIM) in theSRX SeriesServices Gateway:

1. Attachan electrostatic discharge (ESD)grounding strap to your bare wrist, andconnect

the strap to the grounding point on the back of the device.

2. Power off the device by briefly pressing the Power button on the front panel. Wait for

the Power LED

Documents

Book Srx Series Interfaces Hardware Guide