JUNOSe™ Software
for E Series™ Broadband Services Routers
Physical Layer Configuration Guide
Release 11.1.x
Juniper Networks, Inc.
1194 North Mathilda Avenue
Sunnyvale, California 94089
USA
408-745-2000
www.juniper.net
Published: 2010-03-22
Juniper Networks, the Juniper Networks logo, JUNOS, NetScreen, ScreenOS, and Steel-Belted Radius are registered trademarks of Juniper Networks, Inc. in
the United States and other countries. JUNOSe is a trademark of Juniper Networks, Inc. All other trademarks, service marks, registered trademarks, or
registered service marks are the property of their respective owners.
Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify, transfer, or
otherwise revise this publication without notice.
Products made or sold by Juniper Networks or components thereof might be covered by one or more of the following patents 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.
JUNOSe™ Software for E Series™ Broadband Services Routers Physical Layer Configuration Guide
Writing: Krupa Chandrashekar, Subash Babu Asokan, Mark Barnard, Bruce Gillham, Sarah Lesway-Ball, Helen Shaw, Brian Wesley Simmons, Fran Singer,
Michael Taillon
Editing: Benjamin Mann
Illustration: Nathaniel Woodward
Cover Design: Edmonds Design
Revision History
April 2010—FRS JUNOSe 11.1.x
The information in this document is current as of the date listed in the revision history.
YEAR 2000 NOTICE
Juniper Networks hardware and software products are Year 2000 compliant. The JUNOS Software has no known time-related limitations through the year
2038. However, the NTP application is known to have some difficulty in the year 2036.
ii■
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 OTHERWISE EXPRESSING YOUR AGREEMENT TO THE TERMS CONTAINED HEREIN, YOU (AS CUSTOMER
OR IF YOU ARE NOT THE CUSTOMER, AS A REPRESENTATIVE/AGENT AUTHORIZED TO BIND THE CUSTOMER) CONSENT TO BE BOUND BY THIS
AGREEMENT. IF YOU DO NOT OR CANNOT AGREE TO THE 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 the Americas) or Juniper Networks
(Cayman) Limited (if the Customer’s principal office is located outside the Americas) (such applicable entity being referred to herein as “Juniper”), and (ii)
the person or organization that originally purchased from Juniper or an authorized Juniper reseller the 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 which Customer
has paid the applicable license or support fees to Juniper or an authorized Juniper reseller, or which was embedded by Juniper in equipment which Customer
purchased from Juniper or an authorized Juniper reseller. “Software” also includes updates, upgrades and new releases of such software. “Embedded
Software” means Software which Juniper has embedded in or loaded onto the Juniper equipment and any updates, upgrades, additions or replacements
which are subsequently embedded in or loaded onto the equipment.
3. License Grant. Subject to payment of the applicable fees and the limitations and restrictions set forth herein, Juniper grants to Customer a 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 from Juniper
or an authorized Juniper reseller.
b. Customer shall use the Software on a single hardware chassis having a single processing unit, or as many chassis or processing units 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 containing any number of processors. Use of the
Steel-Belted Radius or IMS AAA software on multiple computers or virtual machines (e.g., Solaris zones) requires multiple licenses, 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 specify limits to
Customer’s use of the Software. Such limits may restrict use to a maximum number of seats, registered endpoints, concurrent users, 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 the Software
to be used only in conjunction with other specific Software. Customer’s use of the Software shall be subject to all such limitations and purchase of all applicable
licenses.
d. For any trial copy of the Software, Customer’s right to use the Software expires 30 days after download, installation or use of the Software. Customer
may operate the Software after the 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 the Steel-Belted Radius software may be used by Customer only to manage access to Customer’s enterprise network.
Specifically, service provider customers are expressly prohibited from using 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 provided herein 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 the Software (except as
necessary for backup purposes); (c) rent, sell, transfer, or grant any rights in and to any copy of the Software, in any form, to any third party; (d) remove
any proprietary notices, labels, or marks on or in any copy of the Software or any product in which the Software is embedded; (e) distribute any copy of
the Software to any third party, including as may be embedded in Juniper equipment sold in the secondhand market; (f) use any ‘locked’ or key-restricted
feature, function, service, application, operation, or capability without first purchasing the applicable license(s) and obtaining a valid key from Juniper, even
if such feature, function, service, application, operation, or capability is enabled without a key; (g) distribute any key for the Software provided by Juniper
to any third party; (h) use the Software in any manner that extends or is broader than the uses purchased by Customer from Juniper or an authorized Juniper
reseller; (i) use Embedded Software on non-Juniper equipment; (j) use Embedded Software (or make it available for use) on Juniper equipment that the
Customer did not originally purchase from Juniper or an authorized Juniper reseller; (k) disclose the results of testing or benchmarking of the Software to
any third party without the prior written consent of Juniper; or (l) use the Software in any manner other than as expressly provided herein.
5. Audit. Customer shall maintain accurate records as necessary to verify compliance with this Agreement. Upon request by Juniper, Customer shall furnish
such records to Juniper and certify its compliance with this Agreement.
■iii
6. Confidentiality. The Parties agree that aspects of the Software and associated documentation are the confidential property of Juniper. As such, Customer
shall exercise all reasonable commercial efforts to maintain the Software and associated documentation in confidence, which at a minimum includes
restricting access to the Software to Customer employees and contractors 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 any right, 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 the Software shall be as set forth in the warranty statement that
accompanies the Software (the “Warranty Statement”). Nothing in this Agreement shall give rise to any obligation to support the 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, OR COSTS OR PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES,
OR FOR ANY SPECIAL, INDIRECT, OR CONSEQUENTIAL DAMAGES ARISING OUT OF THIS AGREEMENT, THE SOFTWARE, OR ANY JUNIPER OR
JUNIPER-SUPPLIED SOFTWARE. IN NO EVENT SHALL JUNIPER BE LIABLE FOR DAMAGES ARISING FROM UNAUTHORIZED OR IMPROPER USE OF ANY
JUNIPER OR JUNIPER-SUPPLIED SOFTWARE. EXCEPT AS EXPRESSLY PROVIDED IN THE WARRANTY STATEMENT TO THE 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, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT DOES JUNIPER
WARRANT THAT THE SOFTWARE, OR ANY EQUIPMENT OR NETWORK RUNNING THE SOFTWARE, WILL OPERATE WITHOUT ERROR OR INTERRUPTION,
OR WILL BE FREE OF VULNERABILITY TO INTRUSION OR ATTACK. In no event shall Juniper’s or its suppliers’ or licensors’ liability to Customer, whether
in contract, tort (including negligence), breach of warranty, or otherwise, exceed the price paid by Customer for the Software that gave rise to the claim, or
if the Software is embedded in another Juniper product, the price paid by Customer for such other product. Customer acknowledges and agrees that Juniper
has set its prices and entered into this Agreement in reliance upon the disclaimers of warranty and the limitations of liability set forth herein, that the same
reflect an allocation of risk between the Parties (including the risk that a contract remedy may fail of its essential purpose and cause consequential loss),
and that the same form an essential basis of the bargain between the Parties.
9. Termination. Any breach of this Agreement or failure by Customer to pay any applicable fees due shall result in automatic termination of the license
granted herein. Upon such termination, Customer shall destroy or return to Juniper all copies of the Software 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, valid exemption documentation for each taxing jurisdiction shall be provided to Juniper prior
to invoicing, and Customer shall promptly notify 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 valid tax 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 all applicable tax laws and regulations, and Customer will promptly pay or reimburse Juniper for all costs and damages related
to 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 the Software or any direct product thereof in violation of any such restrictions, laws or regulations, or
without all necessary approvals. Customer shall be liable for any such violations. The version of the Software supplied to Customer may contain encryption
or other capabilities restricting Customer’s ability to export the Software without an export license.
12. Commercial Computer Software. The Software is “commercial computer software” and is provided with restricted rights. Use, duplication, or disclosure
by the United States government is subject to restrictions set forth in this Agreement and as provided 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 interoperability between the Software and another independently created program, on payment of applicable fee, if any.
Customer shall observe strict obligations of confidentiality with respect to such information and shall use such information in compliance with any applicable
terms and conditions upon which Juniper makes such information available.
14. Third Party Software. Any licensor of Juniper whose software is embedded in the Software and any supplier of Juniper whose products or technology
are embedded in (or services are accessed by) the Software shall be a third party beneficiary with respect to this Agreement, and such licensor or vendor
shall have the right to enforce this Agreement in its own name as if it were Juniper. In addition, certain third party software may be provided with the
Software and is subject to the accompanying license(s), if any, of its respective owner(s). To the extent portions of the Software are distributed under and
subject to open source licenses obligating Juniper to make the source code for such 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 the date of distribution. Such request can be made in writing to Juniper Networks, Inc., 1194
N. Mathilda Ave., Sunnyvale, CA 94089, ATTN: General Counsel. You may obtain a copy of the GPL at http://www.gnu.org/licenses/gpl.html, and
a copy of the LGPL at http://www.gnu.org/licenses/lgpl.html.
15. Miscellaneous. This Agreement shall be governed by the laws of the State of California without reference to its conflicts of laws principles. The provisions
of the U.N. Convention for the International Sale of Goods shall not apply to this Agreement. For any disputes arising under this Agreement, the Parties
hereby consent to the personal and exclusive jurisdiction of, and venue in, the state and federal courts within Santa Clara County, California. This Agreement
constitutes the entire and sole agreement between Juniper and the Customer with respect to the Software, and supersedes all prior and contemporaneous
iv■
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 nor any waiver of any rights hereunder shall be effective unless expressly assented to in
writing by the party to be charged. If any portion of this Agreement is held invalid, the Parties agree that such invalidity shall not affect the validity of the
remainder of this Agreement. This Agreement and associated documentation has been written in the English language, and the Parties agree that the English
version will govern. (For Canada: Les parties aux présentés confirment leur volonté que cette convention de même que tous les documents y compris tout
avis qui s'y rattaché, soient redigés en langue anglaise. (Translation: The parties confirm that this Agreement and all related documentation is and will be
in the English language)).
If the information in the latest release notes differs from the information in the
documentation, follow the JUNOSe Release Notes.
To obtain the most current version of all Juniper Networks® technical documentation,
see the product documentation page on the Juniper Networks website at
http://www.juniper.net/techpubs/.
Audience
This guide is intended for experienced system and network specialists working with
Juniper Networks E Series Broadband Services Routers in an Internet access
environment.
E Series and JUNOSe Text and Syntax Conventions
Table 1 on page xx defines notice icons used in this documentation.
E Series and JUNOSe Documentation and Release Notes■xix
JUNOSe 11.1.x Physical Layer Configuration Guide
Table 1: Notice Icons
Table 2 on page xx defines text and syntax conventions that we use throughout the
E Series and JUNOSe documentation.
DescriptionMeaningIcon
Indicates important features or instructions.Informational note
Indicates a situation that might result in loss of data or hardware damage.Caution
Alerts you to the risk of personal injury or death.Warning
Alerts you to the risk of personal injury from a laser.Laser warning
Table 2: Text and Syntax Conventions
Represents commands and keywords in text.Bold text like this
Bold text like this
Fixed-width text like this
Represents text that the user must type.
Represents information as displayed on your
terminal’s screen.
Italic text like this
Emphasizes words.
■
Identifies variables.
■
Identifies chapter, appendix, and book
■
names.
Plus sign (+) linking key names
keys simultaneously.
Syntax Conventions in the Command Reference Guide
ExamplesDescriptionConvention
Issue the clock source command.
■
Specify the keyword exp-msg.
■
host1(config)#traffic class low-loss1
host1#show ip ospf 2
Routing Process OSPF 2 with Router
ID 5.5.0.250
Router is an Area Border Router
(ABR)
There are two levels of access: user and
■
privileged.
clusterId, ipAddress.
■
Appendix A, System Specifications
■
Press Ctrl + b.Indicates that you must press two or more
terminal lengthRepresents keywords.Plain text like this
| (pipe symbol)
or variable to the left or to the right of this
symbol. (The keyword or variable can be
either optional or required.)
xx■E Series and JUNOSe Text and Syntax Conventions
mask, accessListNameRepresents variables.Italic text like this
diagnostic | lineRepresents a choice to select one keyword
Represent required keywords or variables.{ } (braces)
Obtaining Documentation
To obtain the most current version of all Juniper Networks technical documentation,
see the Technical Documentation page on the Juniper Networks Web site at
http://www.juniper.net/.
To download complete sets of technical documentation to create your own
documentation CD-ROMs or DVD-ROMs, see the Offline Documentation page at
Copies of the Management Information Bases (MIBs) for a particular software release
are available for download in the software image bundle from the Juniper Networks
Web site athttp://www.juniper.net/.
We encourage you to provide feedback, comments, and suggestions so that we can
improve the documentation to better meet your needs. Send your comments to
techpubs-comments@juniper.net, or fill out the documentation feedback form at
https://www.juniper.net/cgi-bin/docbugreport/. If you are using e-mail, be sure to include
the following information with your comments:
■Document or topic name
■URL or page number
■Software release version
Requesting Technical Support
Technical product support is available through the Juniper Networks Technical
Assistance Center (JTAC). If you are a customer with an active J-Care or JNASC support
contract, or are covered under warranty, and need post-sales technical support, you
can access our tools and resources online or open a case with JTAC.
■JTAC policies—For a complete understanding of our JTAC procedures and policies,
■JTAC hours of operation—The JTAC centers have resources available 24 hours a
day, 7 days a week, 365 days a year.
Self-Help Online Tools and Resources
For quick and easy problem resolution, Juniper Networks has designed an online
self-service portal called the Customer Support Center (CSC) that provides you with
the following features:
■Find solutions and answer questions using our Knowledge Base:
http://kb.juniper.net/
■Download the latest versions of software and review release notes:
http://www.juniper.net/customers/csc/software/
■Search technical bulletins for relevant hardware and software notifications:
https://www.juniper.net/alerts/
■Join and participate in the Juniper Networks Community Forum:
http://www.juniper.net/company/communities/
■
Open a case online in the CSC Case Management tool: http://www.juniper.net/cm/
To verify service entitlement by product serial number, use our Serial Number
Entitlement (SNE) Tool: 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 Management 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, see
■Configuring Unchannelized OCx/STMx Interfaces on page 73
■Configuring Channelized OCx/STMx Interfaces on page 109
■Configuring Ethernet Interfaces on page 175
■Managing Tunnel-Service and IPSec-Service Interfaces on page 215
Chapters■1
JUNOSe 11.1.x Physical Layer Configuration Guide
2■Chapters
Chapter 1
Configuring Channelized T3 Interfaces
Use the procedures described in this chapter to configure channelized T3 (CT3)
interfaces on E Series Broadband Services Routers.
This chapter contains the following sections:
■Overview on page 3
■Platform Considerations on page 5
■References on page 9
■Before You Configure an Interface on page 9
■Configuration Tasks on page 10
■Configuration Example on page 23
■Testing Interfaces on page 23
■Monitoring Interfaces on page 28
Overview
MDL/FDL Support
Channelized T3 interfaces are supported by the modules described in this chapter.
Configuration procedures for all channelized T3 physical interfaces are identical;
however, the capabilities of the modules differ. Each port on a CT3 module offers a
total bidirectional rate of 43.008 Mbps.
This section describes the features of channelized T3 interfaces. For information
about configuring channelized T3 interfaces over SONET/SDH, see “Configuring
Channelized OCx/STMx Interfaces” on page 109.
Channelized T3 interfaces on some line modules support maintenance data link
(MDL) messages at the T3 level and facilities data link (FDL) messages at the T1 level.
For a list of the line modules that support MDL and FDL, see ERX Module Guide,
Appendix A, Module Protocol Support.
You can use MDL and FDL messages to determine the status of a link and to display
statistics for the remote end of a connection. MDL and FDL messages do not interfere
with other data transmitted over the link.
Overview■3
JUNOSe 11.1.x Physical Layer Configuration Guide
MDL Standards
You can configure channelized T3 interfaces to send MDL messages that comply
with ANSI T1.107a-1990 Standard for Telecommunications—Digital Hierarchy –
Supplement to Formats Specification (August 1990). MDL messages identify a
particular link by sharing common codes for data such as the equipment identifier,
line identifier, frame identifier, and unit.
FDL Standards
Similarly, you can configure T1 channels to send FDL messages that comply with
either or both of the following standards:
■ANSI T1.403-1989 Standard for Telecommunications—Network and Customer
FDL messages that comply with the ANSI standard identify a particular link by
sharing common codes for data such as the equipment identifier, line identifier,
frame identifier, and unit.
■AT&T Technical Reference 54016—Requirements for Interfacing Digital Terminal
Equipment to Services Employing the Extended Superframe Format (September
1989)
FDL messages that comply with the AT&T standard identify a particular link by
sharing performance data and do not use common codes for data such as the
equipment identifier, line identifier, frame identifier, and unit.
Timeout of Received MDL and FDL Messages
When a line module receives an MDL or FDL message string, it stores the strings for
a period of 10 seconds after the last message was received. If the line module does
not receive another message of any type containing the same string within 10
seconds, it erases the local copy of the message.
Most MDL and FDL message strings are common to all three types of messages that
can be transmitted: path identifications, idle signals, and test signals. Certain message
strings, however, are unique to a particular message type. Table 3 on page 4 briefly
describes each MDL/FDL message string and indicates, with a checkmark (✓), the
types of messages in which it can be sent.
Table 3: MDL and FDL Message Strings and Message Types
Message
String
Path
MessageDescription
Idle Signal
Message
Test Signal
Message
4■Overview
✓✓✓Equipment identification codeeic
✓✓✓Frame identification codefic
✓––Generator numbergenerator
Chapter 1: Configuring Channelized T3 Interfaces
Table 3: MDL and FDL Message Strings and Message Types (continued)
Message
String
Path
MessageDescription
Idle Signal
Message
Test Signal
Message
✓✓✓Line identification codelic
––✓Facility identification codepfi
–✓–Equipment port numberport
✓✓✓Unit identification codeunit
As long as another message of any type containing the same string is received within
10 seconds, the line module retains the local copy of the message string and resets
the 10-second timer for that string.
For example, if a line module receives an MDL or FDL test signal message containing
an eic string, and then receives an idle signal message within 10 seconds that also
contains an eic string, it retains the local copy of the most recent eic string received
and resets the 10-second timer for that message. However, if 10 seconds pass without
the line module receiving a path identification, test signal, or idle signal message
containing an eic string, the line module erases the local copy of the eic message
string.
For message strings that are unique to a particular message type, the line module
must receive another message of the same type containing this string in order to
retain the local copy of the string and reset the timer. For example, if the line module
receives a test signal message containing a generator string and does not receive
another test signal message within 10 seconds, it will erase the local copy of the
generator string.
Frequency of FDL Path Messages
E Series Routers transmit FDL path identifier messages every second. This behavior
complies with the ANSI T1.403 specification (see “References” on page 9 for more
information) and is consistent with the MDL implementation for E Series Routers.
Higher-Level Protocols
See ERX Module Guide, Appendix A, Module Protocol Support for information about
the higher-level protocols that channelized T3 interfaces support.
Platform Considerations
You can configure channelized T3 interfaces on the following Juniper Networks E
Series Broadband Services Routers:
■ERX1440 router
■ERX1410 router
■ERX710 router
Platform Considerations■5
JUNOSe 11.1.x Physical Layer Configuration Guide
■ERX705 router
■ERX310 router
NOTE: The Juniper Networks E120 and E320 Broadband Services Routers do not
support configuration of channelized T3 interfaces.
For detailed information about the modules that support channelized T3 interfaces
on ERX7xx models, ERX14xx models, and the ERX310 router:
■See ERX Module Guide, Appendix A, Module Protocol Support for information about
the protocols and applications that channelized T3 modules support.
CT3/T3-F0 Line Modules and CT3/T3 12 I/O Modules
ERX7xx models, ERX14xx models, and the ERX310 router support the CT3/T3-F0
line module and CT3/T3 12 I/O module. The CT3/T3-F0 line module and CT3/T3 12
I/O module support both channelized and unchannelized T3 operation. You can
configure a mixture of channelized and unchannelized ports on these modules. For
information about configuring unchannelized T3 ports, see “Configuring Channelized
T3 Interfaces” on page 3.
ERX14xx models support up to 12 CT3/T3-F0 line modules and 12 CT3/T3 12 I/O
modules, ERX7xx models support up to 5 CT3/T3-F0 line modules and 5 CT3/T3 12
I/O modules, and the ERX310 router supports up to two CT3/T3-F0 line modules and
two CT3/T3 12 I/O modules. Each CT3/T3 12 I/O module has 12 physical T3 (DS3)
ports. Each port uses two SMB connectors: one for the transmit (TX) connection and
one for the receive (RX) connection.
CT3/T3-F0 line modules and CT3/T3 12 I/O modules support the following in
channelized mode:
■28 asynchronous T1 (DS1) channels per T3 port
■24 DS0 channels (64-Kbps) per T1 interface
■166 DS0 channels per T3 port
Exchanging Modules
If you replace a CT3/T3 line module and a CT3/T3 I/O module with a CT3/T3-F0 line
module and a CT3/T3 12 I/O module or vice versa, you must erase the configuration
of the existing modules. See the slot accept command in Managing Modules in the
JUNOSe System Basics Configuration Guide.
6■Platform Considerations
Interface Stack
Chapter 1: Configuring Channelized T3 Interfaces
Figure 1 on page 7 shows the stack for a channelized T3 interface. To configure a
channelized T3 interface, configure a T3 controller, followed by a T1 channel, and
then a fractional T1 channel. Finally, you must configure a High-Speed Data Link
Control (HDLC) data channel on the interface.
Figure 1: Stack for Channelized T3 Interface
Numbering Scheme
For more information about the layers in a channelized T3 interface, see “Numbering
Scheme” on page 7.
NOTE: For a detailed description of interface types and specifiers, see Interface Types
and Specifiers in JUNOSe Command Reference Guide. For information about interfaces,
see Planning Your Network in JUNOSe System Basics Configuration Guide.
This section describes how to identify each layer in a channelized T3 interface stack.
T3 Controllers
A T3 controller on a channelized T3 interface is identified using the slot/port format
where:
■slot—Number of the slot in which the line module resides in the chassis.
In ERX7xx models, line module slots are numbered 2-6; slots 0 and 1 are reserved
for SRP modules. In ERX14xx models, line module slots are numbered 0–5 and
8–13; slots 6 and 7 are reserved for SRP modules. In an ERX310 router, line
module slots are numbered 0–2; slot 0 is reserved for the SRP module.
■port—Number of the port on the I/O module. On a CT3/T3 12 I/O module, ports
are numbered 0–11.
For information about installing line modules and I/O modules in ERX routers, see
ERX Hardware Guide, Chapter 4, Installing Modules.
Platform Considerations■7
JUNOSe 11.1.x Physical Layer Configuration Guide
T1 Channels
A T3 line consists of 28 T1 channels (or data streams). A T1 channel is identified by
its number in the range 1–28.
Each T1 channel is an aggregate of 24 DS0 timeslots, as shown in Figure 2 on page 8.
To configure an entire T1 line, assign 24 timeslots to each channel.
Figure 2: T1 Channels and DS0 Timeslots on a T3 Line
Fractional T1
Fractional T1 is a portion of a T1 line. To configure fractional T1 on a channelized
T3 interface, you assign a range of DS0 timeslots to a T1 channel and subchannel. A
subchannel is group of timeslots. Subchannel numbers range from 1–24 and do not
necessarily correspond to DS0 timeslots. The subchannel number identifies a fractional
T1 channel.
For example, you might make the assignments for subchannels 1–6 as listed in Table
4 on page 8.