Junos Security Swconfig Interfaces

Junos
OS
Interfaces Configuration Guide
for Security Devices
Release
10.4
Published: 2010-10-08
Revision 01
Copyright 2010, Juniper Networks, Inc.
Juniper Networks, Inc.
1194 North Mathilda Avenue
Sunnyvale, California 94089
USA
408-745-2000
www.juniper.net
This product includes the Envoy SNMPEngine, developedby Epilogue Technology, an IntegratedSystems Company. Copyright 1986-1997,
Epilogue Technology Corporation. All rights reserved. This programand its documentation were developed at private expense, and no part
of themis in the public 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 Kirtons EGP, UC Berkeleys routing daemon (routed), and DCNs
HELLOrouting protocol. Development of Gated has been supported in part by the National Science Foundation. Portions of the GateD
software copyright 1988, Regents of the University of California. All rights reserved. Portions of the GateD 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 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.
Junos OS Interfaces Configuration Guide for Security Devices
Release 10.4
Copyright 2010, Juniper Networks, Inc.
All rights reserved. Printed in USA.
Revision History
October 2010Revision 01
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 OS has no known time-related limitations through
the year 2038. However, the NTP application is known to have some difficulty in the year 2036.
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 terms and 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 website at www.juniper.net/techpubs.
Copyright 2010, Juniper Networks, Inc. ii
ENDUSER LICENSE AGREEMENT
READTHIS ENDUSER LICENSE AGREEMENT (AGREEMENT) BEFORE DOWNLOADING, INSTALLING, OR USINGTHE SOFTWARE.
BY DOWNLOADING, INSTALLING, OR USING THE SOFTWARE OR OTHERWISE EXPRESSING YOUR AGREEMENT TOTHE TERMS
CONTAINED HEREIN, YOU (AS CUSTOMER OR IF YOU ARE NOT THE CUSTOMER, AS A REPRESENTATIVE/AGENT AUTHORIZED TO
BINDTHE CUSTOMER) CONSENTTOBE BOUNDBYTHISAGREEMENT. IF YOUDONOTORCANNOTAGREE TOTHE TERMSCONTAINED
HEREIN, THEN (A) DONOT 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 Customers principal office is located in the Americas) or
Juniper Networks (Cayman) Limited(if theCustomers principal officeis locatedoutsidetheAmericas) (suchapplicableentity beingreferred
tohereinas Juniper), and(ii) thepersonor organizationthat originally purchasedfromJuniper or anauthorizedJuniper reseller theapplicable
license(s) for use of the Software (Customer) (collectively, the Parties).
2. The Software. In this Agreement, Software means the programmodules 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 fromJuniper or an authorized Juniper reseller. Software also includes updates, upgrades
and newreleases 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. LicenseGrant. Subject to payment of the applicable fees andthe limitations andrestrictions set forth herein, Juniper grants to Customer
a non-exclusive and non-transferable license, without right to sublicense, to use the Software, in executable formonly, 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. 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 randomaccess 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 toCustomers useof theSoftware. Suchlimits may restrict usetoamaximumnumber of seats, registeredendpoints, 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.
Customers 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, Customers 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 Customers
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 fromJuniper 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, toany thirdparty; (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 soldinthesecondhandmarket; (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, 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
iii Copyright 2010, Juniper Networks, Inc.
Software in any manner that extends or is broader than the uses purchased by Customer fromJuniper 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 fromJuniper 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.
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 minimumincludes restricting access to the Software to Customer employees and contractors having a need to use the Software
for Customers internal business purposes.
7. Ownership. Juniper and Junipers 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 theSoftware(theWarranty Statement). Nothinginthis Agreement shall giverisetoany obligationtosupport
the Software. Support services may be purchased separately. Any such support shall be governed by a separate, written support services
agreement. TOTHE MAXIMUMEXTENT PERMITTED BY LAW, JUNIPER SHALL NOT BE LIABLE FOR ANY LOST PROFITS, LOSS OF DATA,
ORCOSTSORPROCUREMENTOFSUBSTITUTEGOODSORSERVICES, ORFORANYSPECIAL, INDIRECT, ORCONSEQUENTIALDAMAGES
ARISINGOUTOFTHISAGREEMENT, THESOFTWARE, ORANYJUNIPERORJUNIPER-SUPPLIEDSOFTWARE. INNOEVENTSHALLJUNIPER
BE LIABLE FOR DAMAGES ARISING FROMUNAUTHORIZED OR IMPROPER USE OF ANY JUNIPER OR JUNIPER-SUPPLIED SOFTWARE.
EXCEPT AS EXPRESSLY PROVIDED IN THE WARRANTY STATEMENT TOTHE EXTENT PERMITTED BY LAW, JUNIPER DISCLAIMS ANY
AND ALL WARRANTIES IN AND TOTHE SOFTWARE (WHETHER EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE), INCLUDING ANY
IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NOEVENT 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 TOINTRUSION OR ATTACK. In no event shall Junipers 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
forman 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 Customers 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
Customers 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 Customers non-compliance or delay with its responsibilities herein. Customers 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 Customers ability to export the Software without
an export license.
Copyright 2010, Juniper Networks, Inc. iv
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. ThirdParty 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 fromthe 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 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 prsents confirment leur volont que cette convention de
mme que tous les documents y compris tout avis qui s'y rattach, soient redigs en langue anglaise. (Translation: The parties confirmthat
this Agreement and all related documentation is and will be in the English language)).
v Copyright 2010, Juniper Networks, Inc.
Copyright 2010, Juniper Networks, Inc. vi
Abbreviated Table of Contents
About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi
Part 1 Interfaces Overview
Chapter 1 Interfaces Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Part 2 Ethernet Interfaces
Chapter 2 Ethernet Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Chapter 3 Aggregated Ethernet Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Chapter 4 1-Port Gigabit Ethernet SFP Mini-PIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Chapter 5 2-Port 10-Gigabit Ethernet XPIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Chapter 6 Power over Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Part 3 DS1 and DS3 Interfaces
Chapter 7 DS1 and DS3 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Chapter 8 Channelized Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Part 4 ISDNand VoIP Interfaces
Chapter 9 ISDN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Chapter 10 Voice over Internet Protocol with Avaya . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Part 5 DSL and ModemInterfaces
Chapter 11 DSL Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Chapter 12 G.SHDSL Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Chapter 13 VDSL2 Mini-PIMInterfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
Chapter 14 3G Wireless Modems for WAN Connections . . . . . . . . . . . . . . . . . . . . . . . . . 353
Chapter 15 USB Modems for Dial Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
Chapter 16 DOCSIS Mini-PIM Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
Chapter 17 Serial Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
Part 6 Link Services and Special Interfaces
Chapter 18 Link Services Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
Chapter 19 Special Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
vii Copyright 2010, Juniper Networks, Inc.
Part 7 Encapsulation
Chapter 20 Interface Encapsulation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461
Chapter 21 Point-to-Point Protocol over Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
Part 8 Index
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489
Copyright 2010, Juniper Networks, Inc. viii
Table of Contents
About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi
J Series and SRX Series Documentation and Release Notes . . . . . . . . . . . . . . . . . xxi
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii
Supported Routing Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii
Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii
Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiv
Requesting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiv
Self-Help Online Tools and Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiv
Opening a Case with JTAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxv
Part 1 Interfaces Overview
Chapter 1 Interfaces Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Interfaces Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Understanding Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Network Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Services Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Special Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Interface Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Interface Logical Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Understanding Interface Logical Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Understanding Protocol Families . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Common Protocol Suites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Other Protocol Suites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Understanding IPv4 Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
IPv4 Classful Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
IPv4 Dotted Decimal Notation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
IPv4 Subnetting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
IPv4 Variable-Length Subnet Masks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
IPv6 Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Understanding IPv6 Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Configuring the inet6 IPv6 Protocol Family . . . . . . . . . . . . . . . . . . . . . . . . 18
Enabling Flow-Based Processing for IPv6 Traffic . . . . . . . . . . . . . . . . . . . 19
Understanding Virtual LANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Interface Physical Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Understanding Interface Physical Properties . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Understanding Bit Error Rate Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Understanding Interface Clocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Data Stream Clocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Explicit Clocking Signal Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
ix Copyright 2010, Juniper Networks, Inc.
Understanding Frame Check Sequences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Cyclic Redundancy Checks and Checksums . . . . . . . . . . . . . . . . . . . . . . . 25
Two-Dimensional Parity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
MTU Default and Maximum Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Understanding the Data Link Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Physical Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Network Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Error Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Frame Sequencing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Flow Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Data Link Sublayers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
MAC Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Part 2 Ethernet Interfaces
Chapter 2 Ethernet Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Understanding Ethernet Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Ethernet Access Control and Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Collisions and Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Collision Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Backoff Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Collision Domains and LAN Segments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Repeaters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Bridges and Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Broadcast Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Ethernet Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Example: Creating an Ethernet Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Example: Deleting an Ethernet Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Static ARP Entries on Ethernet Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Understanding Static ARP Entries on Ethernet Interfaces . . . . . . . . . . . . . . . 39
Example: Configuring Static ARP Entries on Ethernet Interfaces . . . . . . . . . . 39
Promiscuous Mode on Ethernet Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Understanding Promiscuous Mode on Ethernet Interfaces . . . . . . . . . . . . . . 42
Enabling and Disabling Promiscuous Mode on Ethernet Interfaces (CLI
Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Copyright 2010, Juniper Networks, Inc. x
Chapter 3 Aggregated Ethernet Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Aggregated Ethernet Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Understanding Aggregated Ethernet Interfaces . . . . . . . . . . . . . . . . . . . . . . . 45
LAGs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
LACP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Aggregated Ethernet Interfaces Configuration Overview . . . . . . . . . . . . . . . . 47
Device Count for Aggregated Ethernet Interfaces . . . . . . . . . . . . . . . . . . . . . . 48
Understanding the Aggregated Ethernet Interfaces Device Count . . . . . 48
Example: Configuring the Number of Aggregated Ethernet Interfaces
on a Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Example: Deleting Aggregated Ethernet Interfaces . . . . . . . . . . . . . . . . . 50
Physical Interfaces for Aggregated Ethernet Interfaces . . . . . . . . . . . . . . . . . . 51
Understanding Physical Interfaces for Aggregated Ethernet
Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Example: Associating Physical Interfaces with Aggregated Ethernet
Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Link Speed for Aggregated Ethernet Interfaces . . . . . . . . . . . . . . . . . . . . . . . . 52
Understanding Aggregated Ethernet Interface Link Speed . . . . . . . . . . . 52
Example: Configuring Aggregated Ethernet Link Speed . . . . . . . . . . . . . 53
Minimum Links for Aggregated Ethernet Interfaces . . . . . . . . . . . . . . . . . . . . 54
Understanding Minimum Links for Aggregated Ethernet Interfaces . . . . 54
Example: Configuring Aggregated Ethernet Minimum Links . . . . . . . . . . 54
Removal of Aggregated Ethernet Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Understanding Aggregated Ethernet Interface Removal . . . . . . . . . . . . . 55
Example: Deleting Aggregated Ethernet Interface Contents . . . . . . . . . . 55
Understanding VLAN Tagging for Aggregated Ethernet Interfaces . . . . . . . . . 57
Understanding Promiscuous Mode for Aggregated Ethernet Interfaces . . . . 57
Verifying Aggregated Ethernet Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Verifying Aggregated Ethernet Interfaces (terse) . . . . . . . . . . . . . . . . . . . 57
Verifying Aggregated Ethernet Interfaces (extensive) . . . . . . . . . . . . . . . 58
LACP for Standalone Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Understanding LACP on Standalone Devices . . . . . . . . . . . . . . . . . . . . . . . . . 59
Example: Configuring LACP on Standalone Devices . . . . . . . . . . . . . . . . . . . 60
Verifying LACP on Standalone Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Verifying LACP Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Verifying LACP Aggregated Ethernet Interfaces . . . . . . . . . . . . . . . . . . . . 63
LACP on Chassis Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Understanding LACP on Chassis Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
MinimumLinks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Sub-LAGs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Hitless Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
PDUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Example: Configuring LACP on Chassis Clusters . . . . . . . . . . . . . . . . . . . . . . . 66
Verifying LACP on Redundant Ethernet Interfaces . . . . . . . . . . . . . . . . . . . . . 68
Chapter 4 1-Port Gigabit Ethernet SFP Mini-PIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Understanding the 1-Port Gigabit Ethernet SFP Mini-PIM. . . . . . . . . . . . . . . . . . . . 71
Supported Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Interface Names and Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
xi Copyright 2010, Juniper Networks, Inc.
Table of Contents
Available Link Speeds and Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Link Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Example: Configuring the 1-Port Gigabit Ethernet SFP Mini-PIM Interface . . . . . . 73
Chapter 5 2-Port 10-Gigabit Ethernet XPIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Understanding the 2-Port 10-Gigabit Ethernet XPIM . . . . . . . . . . . . . . . . . . . . . . . 79
Supported Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Interface Names and Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Copper and Fiber Operating Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Link Speeds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Link Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Example: Configuring the 2-Port 10-Gigabit Ethernet XPIM Interface . . . . . . . . . . 82
Chapter 6 Power over Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Understanding Power over Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
SRX Series Services Gateway PoE Specifications . . . . . . . . . . . . . . . . . . . . . . 87
PoE Classes and Power Ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
PoE Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Example: Configuring PoE on All Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Example: Configuring PoE on an Individual Interface . . . . . . . . . . . . . . . . . . . . . . . 92
Example: Disabling a PoE Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Part 3 DS1 and DS3 Interfaces
Chapter 7 DS1 and DS3 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
DS1 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Understanding T1 and E1 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
T1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
E1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
T1 and E1 Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
T1 and E1 Framing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
T1 and E1 Loopback Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Example: Configuring a T1 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Example: Deleting a T1 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
DS3 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Understanding T3 and E3 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Multiplexing DS1 Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
DS2 Bit Stuffing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
DS3 Framing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Example: Configuring a T3 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Example: Deleting a T3 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Copyright 2010, Juniper Networks, Inc. xii
Chapter 8 Channelized Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Understanding Channelized Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Clear Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Understanding Channelized Interface Clear Channels . . . . . . . . . . . . . . . . . . 116
Example: Configuring a Channelized T1 Interface as a Clear Channel . . . . . . 117
Example: Configuring a Channelized E1 Interface as a Clear Channel . . . . . . 120
Verifying Clear-Channel Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Drop-and-Insert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Understanding Channelized Interface Drop-and-Insert . . . . . . . . . . . . . . . . . 124
Example: Configuring a Channelized Interface to Drop and Insert Time
Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Example: Configuring Complementary Clock Sources on Channelized
Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Verifying Channelized Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
ISDN PRI Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Understanding ISDN PRI Operation for Channelized Interfaces . . . . . . . . . . 136
Example: Configuring a Channelized Interface for ISDN PRI Operation . . . . 137
Verifying ISDN PRI Configuration on Channelized Interfaces . . . . . . . . . . . . . 138
Part 4 ISDNand VoIP Interfaces
Chapter 9 ISDN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Understanding ISDN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
ISDN Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Typical ISDN Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
NT Devices and S and T Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
U Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
ISDN Call Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Layer 2 ISDN Connection Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Layer 3 ISDN Session Establishment . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
ISDN Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
ISDN Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Understanding ISDN Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
ISDN BRI Interface Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
ISDN PRI Interface Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
ISDN Interface Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Example: Adding an ISDN BRI Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Dialer Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Understanding Dialer Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Example: Configuring Dialer Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Dial Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Understanding Dial Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Example: Configuring Dial Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Dial-on-Demand Routing Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Understanding Dial-on-Demand Routing Backup . . . . . . . . . . . . . . . . . 156
Example: Configuring Dialer Filters for Dial-on-Demand Routing
Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Example: Configuring Dial-on-Demand Routing Backup with OSPF
Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
xiii Copyright 2010, Juniper Networks, Inc.
Table of Contents
Dialer Watch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Understanding Dialer Watch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Example: Configuring Dialer Watch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Dial-In and Callback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Understanding Dial-In and Callback . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Example: Configuring Dial-In and Callback . . . . . . . . . . . . . . . . . . . . . . . 163
Bandwidth on Demand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Understanding Bandwidth on Demand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Example: Configuring Bandwidth on Demand . . . . . . . . . . . . . . . . . . . . . . . . 167
Disabling ISDN Processes (CLI Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Verifying the ISDN Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Displaying the ISDN Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Verifying an ISDN BRI Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Verifying an ISDN PRI Interface and Checking B-Channel Interface
Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Checking D-Channel Interface Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Displaying the Status of ISDN Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Verifying Dialer Interface Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Chapter 10 Voice over Internet Protocol with Avaya . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Avaya VoIP Modules Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Avaya VoIP Modules Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Supported Avaya VoIP Modules and Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Avaya VoIP Modules Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
J2320 and J2350 Avaya VoIP Module Summary . . . . . . . . . . . . . . . . . . 186
J4350 and J6350 Avaya VoIP Module Summary . . . . . . . . . . . . . . . . . . 187
TGM550 Telephony Gateway Module Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Understanding the TGM550 Telephony Gateway Module . . . . . . . . . . . . . . 189
TGM550 Guidelines and Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
TGM550 Access Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
TGM550 Console Port Pinouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
TGM550 RJ-11 Connector Pinout for Analog Ports . . . . . . . . . . . . . . . . . . . . . 194
TGM550 MaximumMedia Gateway Capacities . . . . . . . . . . . . . . . . . . . . . . . 195
TGM550 LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
TIM508 Analog Telephony Interface Module Overview . . . . . . . . . . . . . . . . . . . . 197
Understanding the TIM508 Analog Telephony Interface Module . . . . . . . . . 197
TIM508 Connector Pinout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
TIM508 Possible Port Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
TIM508 LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
TIM510 E1/T1 Telephony Interface Module Overview . . . . . . . . . . . . . . . . . . . . . . 201
Understanding the TIM510 E1/T1 Telephony Interface Module . . . . . . . . . . . 201
TIM510 RJ-45 Connector Pinout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
TIM510 LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
TIM514 Analog Telephony Interface Module Overview . . . . . . . . . . . . . . . . . . . . 203
TIM514 Connector Pinout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
TIM514 Possible Port Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
TIM514 LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Copyright 2010, Juniper Networks, Inc. xiv
TIM516 Analog Telephony Interface Module Overview. . . . . . . . . . . . . . . . . . . . . 207
TIM516 LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
TIM518 Analog Telephony Interface Module Overview . . . . . . . . . . . . . . . . . . . . . 211
Understanding the TIM518 Analog Telephony Interface Module . . . . . . . . . . 211
TIM518 LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
TIM521 BRI Telephony Interface Module Overview . . . . . . . . . . . . . . . . . . . . . . . . 215
Understanding the TIM521 BRI Telephony Interface Module . . . . . . . . . . . . . 215
TIM521 LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Avaya IG550 Integrated Gateway Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Media Gateway Controller Server Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Avaya Communication Manager Software Overview . . . . . . . . . . . . . . . . . . . . . . 220
Dynamic Call Admission Control Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Dynamic CAC Interface Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Supported Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Bearer Bandwidth Limit and Activation Priority . . . . . . . . . . . . . . . . . . . . 221
Rules for Determining Reported BBL . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Configuring VoIP Interfaces with EPW and Disk-on-Key . . . . . . . . . . . . . . . . . . . 222
Example: Configuring VoIP Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
TGM550 Module Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Connecting Through the TGM550 Module Console Port . . . . . . . . . . . . . . . 234
Connecting to the TGM550 with SSH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
TGM550 Module with Telnet Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Enabling Telnet Service on the TGM550 Module . . . . . . . . . . . . . . . . . . 235
Connecting to the TGM550 Module with Telnet . . . . . . . . . . . . . . . . . . 235
Disabling Telnet Service on the TGM550 Module . . . . . . . . . . . . . . . . . 236
Accessing the Services Router from the TGM550 Module . . . . . . . . . . . . . . 236
Resetting the TGM550 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Saving the TGM550 Module Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 237
TGM550 Module and VoIP Interface Troubleshooting . . . . . . . . . . . . . . . . . . . . . 237
Part 5 DSL and ModemInterfaces
Chapter 11 DSL Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
ADSL Interface Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
ADSL Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
ADSL2 and ADSL2+ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
ATM CoS Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
ADSL and SHDSL Interfaces Configuration Overview . . . . . . . . . . . . . . . . . . . . . 244
Example: Configuring ATM-over-ADSL Network Interface . . . . . . . . . . . . . . . . . 248
Example: Configuring ATM-over-SHDSL Network Interface . . . . . . . . . . . . . . . . 255
Example: Configuring CHAP on DSL Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Example: Configuring MLPPP over ADSL Interfaces . . . . . . . . . . . . . . . . . . . . . . . 270
xv Copyright 2010, Juniper Networks, Inc.
Table of Contents
Chapter 12 G.SHDSL Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
SHDSL Interface Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
G.SHDSL Mini-PIM Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Operating Modes and Line Rates of the G.SHDSL Mini-PIM . . . . . . . . . . . . . 274
ATM CoS Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
G.SHDSL Mini-PIM Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Example: Configuring the G.SHDSL Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Example: Configuring the G.SHDSL Interface on SRX Series Devices . . . . . . . . . 286
Chapter 13 VDSL2 Mini-PIMInterfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
VDSL2 Mini-PIM Interface Technology Overview . . . . . . . . . . . . . . . . . . . . . . . . . 295
VDSL2 Network Deployment Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
VDSL2 Mini-PIM Support on the SRX210 and SRX240 Services Gateways . . . . 297
VDSL2 Mini-PIM Supported Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
VDSL2 Mini-PIM Supported Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
Example: Configuring the VDSL2 Interface Properties . . . . . . . . . . . . . . . . . . . . . 299
Example: Configuring VDSL2 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
Example: Configuring ADSL Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
Chapter 14 3G Wireless Modems for WAN Connections . . . . . . . . . . . . . . . . . . . . . . . . . 353
3G Wireless Modem Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
3G Wireless Modem Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
Dialer Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
Understanding the Dialer Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
Example: Configuring the Dialer Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
3G Wireless Modem Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
Understanding the 3G Wireless Modem Physical Interface . . . . . . . . . . . . . 363
Example: Configuring the 3G Wireless Modem Interface . . . . . . . . . . . . . . . 363
GSM Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
Understanding the GSM Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
Example: Configuring the GSM Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
Account Activation for CDMA EV-DO Modem Cards . . . . . . . . . . . . . . . . . . . . . . 366
Understanding Account Activation for CDMA EV-DO Modem Cards . . . . . . 367
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
Activating the CDMA EV-DO Modem Card with OTASP Provisioning . . . . . 368
Activating the CDMA EV-DO Modem Card Manually . . . . . . . . . . . . . . . . . . 369
Activating the CDMA EV-DO Modem Card with IOTA Provisioning . . . . . . . . 371
Unlocking the GSM 3G Wireless Modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
Chapter 15 USB Modems for Dial Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
USB Modem Interface Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
Dialer Interface Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
USB Modem Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
Example: Configuring a USB ModemInterface for Dial Backup . . . . . . . . . . . . . . 376
Example: Configuring a Dialer Interface for USB Modem Dial Backup . . . . . . . . . 377
Example: Configuring Dialer Interface for USB Modem Dial-In . . . . . . . . . . . . . . 384
Example: Configuring PAP on Dialer Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . 386
Example: Configuring CHAP on Dialer Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . 387
Copyright 2010, Juniper Networks, Inc. xvi
Chapter 16 DOCSIS Mini-PIM Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
DOCSIS Mini-PIM Interface Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
Software Features Supported on DOCSIS Mini-PIMs . . . . . . . . . . . . . . . . . . . . . 392
Example: Configuring a DOCSIS Mini-PIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
Chapter 17 Serial Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
Serial Interfaces Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
Serial Transmissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
Signal Polarity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
Serial Clocking Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
Serial Interface Transmit Clock Inversion . . . . . . . . . . . . . . . . . . . . . . . . 403
DTE Clock Rate Reduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
Serial Line Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
EIA-530 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
RS-232 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405
RS-422/449 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405
V.35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
X.21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
Example: Configuring a Serial Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
Example: Deleting a Serial Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
Part 6 Link Services and Special Interfaces
Chapter 18 Link Services Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
Link Services Interfaces Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
Services Available on a J Series Link Services Interface . . . . . . . . . . . . . . . . . 414
Link Services Exceptions on J Series Services Routers . . . . . . . . . . . . . . . . . . 415
Configuring Multiclass MLPPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
Queuing with LFI on J Series Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
Queuing on Q2s of Constituent Links . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
Compressed Real-Time Transport Protocol Overview . . . . . . . . . . . . . . . . . . 417
Configuring Fragmentation by Forwarding Class . . . . . . . . . . . . . . . . . . . . . . 418
Configuring Link-Layer Overhead . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
Link Services Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
Configuring Link Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
Understanding MLPPP Bundles and Link Fragmentation and Interleaving
(LFI) on Serial Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
Example: Configuring an MLPPP Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422
Understanding Link Fragmentation and Interleaving Configuration . . . . . . . 424
Example: Configuring Link Fragmentation and Interleaving . . . . . . . . . . . . . 425
Understanding How to Define Classifiers and Forwarding Classes . . . . . . . 426
Example: Defining Classifiers and Forwarding Classes . . . . . . . . . . . . . . . . . 426
Understanding Howto Define and Apply Scheduler Maps . . . . . . . . . . . . . . 428
Example: Defining and Applying Scheduler Maps . . . . . . . . . . . . . . . . . . . . . 429
Understanding Interface Shaping Rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
xvii Copyright 2010, Juniper Networks, Inc.
Table of Contents
Example: Defining and Applying Interface Shaping Rates . . . . . . . . . . . . . . 432
Verifying the Link Services Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
Verifying Link Services Interface Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
Verifying Link Services CoS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 435
Multilink Frame Relay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
Understanding Multilink Frame Relay FRF.15 . . . . . . . . . . . . . . . . . . . . . . . . . 437
Example: Configuring Multilink Frame Relay MLFR FRF.15 . . . . . . . . . . . . . . 438
Understanding Multilink Frame Relay FRF.16 . . . . . . . . . . . . . . . . . . . . . . . . 439
Example: Configuring Multilink Frame Relay MLFR FRF.16 . . . . . . . . . . . . . . 440
Compressed Real-Time Transport Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
Understanding Compressed Real-Time Transport Protocol . . . . . . . . . . . . . 441
Example: Configuring Compressed Real-Time Transport Protocol . . . . . . . 442
Internal Interface ls-0/0/0 Upgrade and Configuration Rollback . . . . . . . . . . . . 443
Understanding the Internal Interface LSQ-0/0/0 Configuration . . . . . . . . . 443
Example: Upgrading Configuration to Change ls-0/0/0 to lsq-0/0/0 . . . . . 443
Troubleshooting the Link Services Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
Determine Which CoS Components Are Applied to the Constituent
Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
Determine What Causes Jitter and Latency on the Multilink Bundle . . . . . . 447
Determine If LFI and Load Balancing Are Working Correctly . . . . . . . . . . . . . 447
Determine Why Packets Are Dropped on a PVC Between a J Series Device
and Another Vendor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
Chapter 19 Special Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
Understanding Management Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
Understanding the Discard Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456
Understanding the Loopback Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
Part 7 Encapsulation
Chapter 20 Interface Encapsulation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461
Understanding Physical Encapsulation on an Interface . . . . . . . . . . . . . . . . . . . . 461
Understanding Frame Relay Encapsulation on an Interface . . . . . . . . . . . . . . . . 462
Virtual Circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
Switched and Permanent Virtual Circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . 463
Data-Link Connection Identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463
Congestion Control and Discard Eligibility . . . . . . . . . . . . . . . . . . . . . . . . . . . 463
Understanding Point-to-Point Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464
Link Control Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464
PPP Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465
Network Control Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465
Magic Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
CSU/DSU Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
Understanding High-Level Data Link Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
HDLC Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
HDLC Operational Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
Copyright 2010, Juniper Networks, Inc. xviii
Chapter 21 Point-to-Point Protocol over Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
Understanding Point-to-Point Protocol over Ethernet . . . . . . . . . . . . . . . . . . . . 469
PPPoE Discovery Stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470
PPPoE Session Stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
PPPoE Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
Understanding PPPoE Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
Example: Configuring PPPoE Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472
PPPoE Encapsulation on an Ethernet Interface . . . . . . . . . . . . . . . . . . . . . . . . . . 476
Understanding PPPoE Ethernet Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . 476
Example: Configuring PPPoE Encapsulation on an Ethernet Interface . . . . . 477
PPPoE Encapsulation on an ATM-over-ADSL or ATM-over-SHDSL Interface . . 478
Understanding PPPoE ATM-over-ADSL and ATM-over-SHDSL
Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
Example: Configuring PPPoE Encapsulation on an ATM-over-ADSL
Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479
CHAP Authentication on a PPPoE Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481
Understanding CHAP Authentication on a PPPoE Interface . . . . . . . . . . . . . 481
Example: Configuring CHAP Authentication on a PPPoE Interface . . . . . . . 481
PPPoE-Based Radio-to-Router Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483
Understanding the PPPoE-Based Radio-to-Router Protocol . . . . . . . . . . . . 483
Example: Configuring the PPPoE-Based Radio-to-Router Protocol . . . . . . 485
Part 8 Index
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489
xix Copyright 2010, Juniper Networks, Inc.
Table of Contents
Copyright 2010, Juniper Networks, Inc. xx
About This Guide
This preface provides the following guidelines for using the Junos OS Interfaces
Configuration Guide for Security Devices:
J Series and SRX Series Documentation and Release Notes on page xxi
Objectives on page xxii
Audience on page xxii
Supported Routing Platforms on page xxii
Document Conventions on page xxii
Documentation Feedback on page xxiv
Requesting Technical Support on page xxiv
J Series and SRX Series Documentation and Release Notes
For a list of related J Series documentation, see
http://www.juniper.net/techpubs/software/junos-jseries/index-main.html .
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 release notes differs fromthe information in the
documentation, followthe Junos OS 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/.
Juniper Networks supports atechnical bookprogramtopublishbooks byJuniper Networks
engineers and subject matter experts with book publishers around the world. These
books go beyond the technical documentation to explore the nuances of network
architecture, deployment, and administration using the Junos operating system(Junos
OS) and Juniper Networks devices. In addition, the Juniper Networks Technical Library,
published in conjunction with O'Reilly Media, explores improving network security,
reliability, and availability using Junos OS configuration techniques. All the books are for
sale at technical bookstores and book outlets around the world. The current list can be
viewed at http://www.juniper.net/books .
xxi Copyright 2010, Juniper Networks, Inc.
Objectives
This guide describes howto use and configure key security features on J Series Services
Routers and SRX Series Services Gateways running Junos OS. It provides conceptual
information, suggested workflows, and examples where applicable.
Audience
This manual is designed for anyone who installs, sets up, configures, monitors, or
administers a J Series Services Router or an SRX Series Services Gateway running Junos
OS. The manual is intended for the following audiences:
Customers with technical knowledge of and experience with networks and network
security, the Internet, and Internet routing protocols
Network administrators who install, configure, and manage Internet routers
Supported Routing Platforms
This manual describes features supported on J Series Services Routers and SRX Series
Services Gateways running Junos OS.
Document Conventions
Table 1 on page xxii defines the notice icons used in this guide.
Table 1: Notice Icons
Description Meaning Icon
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 froma laser. Laser warning
Table 2 on page xxiii defines the text and syntax conventions used in this guide.
Copyright 2010, Juniper Networks, Inc. xxii
Table 2: Text and Syntax Conventions
Examples Description Convention
To enter configuration mode, type the
configure command:
user@host> configure
Represents text that you type. Bold text like this
user@host> showchassis alarms
No alarms currently active
Represents output that appears on the
terminal screen.
Fixed-width text like this
A policy termis a named structure
that defines match conditions and
actions.
Junos SystemBasics Configuration
Guide
RFC1997, BGPCommunities Attribute
Introduces important newterms.
Identifies book names.
Identifies RFCand Internet draft titles.
Italic text like this
Configure the machines domain name:
[edit]
root@# set systemdomain-name
domain-name
Represents variables (options for which
you substitute a value) in commands or
configuration statements.
Italic text like this
To configure a stub area, include the
stub statement at the [edit protocols
ospf area area-id] hierarchy level.
Theconsoleport is labeledCONSOLE.
Represents names of configuration
statements, commands, files, and
directories; IP addresses; configuration
hierarchy levels; or labels on routing
platformcomponents.
Text like this
stub <default-metric metric>; Enclose optional keywords or variables. < > (angle brackets)
broadcast | multicast
(string1 | string2 | string3)
Indicates a choice between the mutually
exclusive keywords or variables on either
side of the symbol. The set of choices is
often enclosed in parentheses for clarity.
| (pipe symbol)
rsvp { #Required for dynamic MPLS only Indicates a comment specified on the
samelineas theconfigurationstatement
to which it applies.
# (pound sign)
community name 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
xxiii Copyright 2010, Juniper Networks, Inc.
About This Guide
Table 2: Text and Syntax Conventions (continued)
Examples Description Convention
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-Web
selections.
> (bold right angle bracket)
Documentation Feedback
We encourage you to provide feedback, comments, and suggestions so that we can
improve the documentation. You can send your comments to
techpubs-comments@juniper.net, or fill out the documentation feedback format
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 (if applicable)
Requesting Technical Support
Technical product support is availablethroughtheJuniper 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 postsales technical support, you can access
our tools and resources online or open a case with JTAC.
JTAC policiesFor a complete understanding of our JTAC procedures and policies,
reviewthe JTAC User Guide located at
http://www.juniper.net/us/en/local/pdf/resource-guides/7100059-en.pdf .
Product warrantiesFor 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 days a week, 365 days a year.
Self-Help Online Tools and Resources
For quick and easy problemresolution, 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/
Copyright 2010, Juniper Networks, Inc. xxiv
Find solutions and answer questions using our Knowledge Base: http://kb.juniper.net/
Download the latest versions of software and reviewrelease 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/
Toverify serviceentitlement by product serial number, useour 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, visit us at
http://www.juniper.net/support/requesting-support.html
xxv Copyright 2010, Juniper Networks, Inc.
About This Guide
Copyright 2010, Juniper Networks, Inc. xxvi
PART 1
Interfaces Overview
Interfaces Overviewon page 3
1 Copyright 2010, Juniper Networks, Inc.
Copyright 2010, Juniper Networks, Inc. 2
CHAPTER 1
Interfaces Overview
Interfaces Overviewon page 3
Interface Naming Conventions on page 9
Interface Logical Properties on page 11
Interface Physical Properties on page 22
Understanding the Data Link Layer on page 28
Interfaces Overview
Understanding Interfaces on page 3
Network Interfaces on page 4
Services Interfaces on page 5
Special Interfaces on page 8
Understanding Interfaces
Interfaces act as a doorway through which traffic enters and exits a device. J Series
Services Routers and SRX Series Service Gateways support a variety of interface types:
Network interfacesNetworking interfaces primarily provide traffic connectivity.
Services interfacesServices interfaces manipulate traffic before it is delivered to its
destination.
Special interfacesSpecial interfaces include management interfaces, the loopback
interface, and the discard interface.
Each type of interface uses a particular mediumto transmit data. The physical wires and
Data Link Layer protocols used by a mediumdetermine howtraffic is sent. To configure
and monitor J Series or SRXSeries device interfaces, you need to understand their media
characteristics, as well as physical andlogical properties such as IPaddressing, link-layer
protocols, and link encapsulation.
NOTE: Most interfaces are configurable, but some internally generated
interfaces are not configurable.
Related
Documentation
Junos OS Feature Support Reference for SRX Series and J Series Devices
Interface Naming Conventions on page 9
Understanding Interface Logical Properties on page 11
Understanding Interface Physical Properties on page 22
Understanding the Data Link Layer on page 28
Router Interfaces Overviewin the Junos OS Network Interfaces Configuration Guide
Network Interfaces
All Juniper Networks devices use network interfaces to make physical connections to
other devices. A connection takes place along media-specific physical wires through an
I/OCard (IOC) in the SRX Series Services Gateway or a port on a Physical Interface
Module (PIM) installed in the J Series Services Router. Networking interfaces primarily
provide traffic connectivity.
Youmust configureeachnetworkinterfacebeforeit canoperateonthedevice. Configuring
an interface can define both the physical properties of the link and the logical properties
of a logical interface on the link.
Table 3 on page 4 describes network interfaces that are available on SRX Series and J
Series devices.
Table 3: Network Interfaces
Description Interface Name
Aggregated Ethernet interface. See Understanding Aggregated Ethernet Interfaces on page 45. ae
ATM-over-ADSL or ATM-over-SHDSL WAN interface. See DSL Interfaces on page 241. at
Bearer channel on an ISDN interface. See ISDN on page 141. bc
Basic Rate Interface for establishing ISDN connections. See ISDN on page 141. br
Channelized E1 interface. See Channelized Interfaces on page 115. ce1
Channelized T1 interface. See Channelized Interfaces on page 115. ct1
Delta channel on an ISDN interface. See ISDN on page 141. dc
Dialer interface for initiating ISDN and USB modemconnections. See ISDN on page 141 and USB
Modems for Dial Backup on page 373.
dl
E1 (also called DS1) WAN interface. See DS1 and DS3 Interfaces on page 99. e1
E3 (also called DS3) WAN interface. See DS1 and DS3 Interfaces on page 99. e3
Fast Ethernet interface. See Understanding Ethernet Interfaces on page 33. fe
Table 3: Network Interfaces (continued)
Gigabit Ethernet interface. See Understanding Ethernet Interfaces on page 33. ge
VDSL2 interface. See DSL Interfaces on page 241. pt
For chassis cluster configurations only, redundant Ethernet interface. See Understanding Ethernet
Interfaces on page 33.
reth
Serial interface (either RS-232, RS-422/499, RS-530, V.35, or X.21). See Serial Interfaces on
page 401.
se
T1 (also called DS1) WAN interface. See DS1 and DS3 Interfaces on page 99. t1
T3 (also called DS3) WAN interface. See DS1 and DS3 Interfaces on page 99. t3
WXCIntegratedServices Module (ISM200) interface for WANacceleration. See the WXCIntegrated
Services Module Installation and Configuration Guide.
wx
10-Gigabit Ethernet interface. SeeUnderstandingthe2-Port 10-Gigabit Ethernet XPIM onpage79. xe
Related
Documentation
Services Interfaces
Services interfaces provide specific capabilities for manipulating traffic before it is
deliveredto its destination. On Juniper Networks MSeries andTSeries routing platforms,
individual services such as IP-over-IP encapsulation, link services such as multilink
protocols, adaptive services such as stateful firewall filters and NAT, and sampling and
logging capabilities are implemented by services Physical Interface Cards (PICs). On a
J Series device, these same features are implemented by the general-purpose CPU on
the main circuit board.
Although the same Junos OS image supports the services features across all routing
platforms, on a J Series device no Physical Interface Module (PIM) is associated with
services features. To configure services on a J Series device, you must configure one or
more internal interfaces by specifying PIMslot 0 and port 0for example, gr-0/0/0 for
GRE.
Table 4 on page 6 describes services interfaces that you can configure on SRX Series
Services Gateways and J Series Services Routers.
Chapter 1: Interfaces Overview
Table 4: Configurable Services Interfaces
Configurable generic routing encapsulation (GRE) interface. GRE allows the encapsulation of one
routing protocol over another routing protocol.
WithinaJ Series device, packets areroutedtothis internal interface, wherethey arefirst encapsulated
with a GRE packet and then re-encapsulated with another protocol packet to complete the GRE.
The GRE interface is an internal interface only and is not associated with a physical mediumor PIM.
You must configure the interface for it to performGRE. See Tunnel Services Overviewin the Junos
OS Services Interfaces Configuration Guide.
gr-0/0/0
Configurable IP-over-IP encapsulation (also called IP tunneling) interface. IP tunneling allows the
encapsulation of one IP packet over another IP packet.
Generally, IP routing allows packets to be routed directly to a particular address. However, in some
instancesyoumight needtorouteanIPpacket tooneaddressandthenencapsulateit for forwarding
to a different address. In a mobile environment in which the location of the end device changes, a
different IP address might be used as the end device migrates between networks.
Within a J Series device, packets are routed to this internal interface where they are encapsulated
with an IP packet and then forwarded to the encapsulating packet's destination address. The IP-IP
interface is an internal interface only and is not associated with a physical mediumor PIM. You must
configure the interface for it to performIP tunneling. See Tunnel Services Overviewin the Junos OS
Services Interfaces Configuration Guide.
ip-0/0/0
Configurable link services queuing interface. Link services include the multilink services MLPPP,
MLFR, and Compressed Real-Time Transport Protocol (CRTP).
WithinaJ Series device, packets areroutedtothis internal interfacefor link bundlingor compression.
The link services interface is an internal interface only and is not associated with a physical medium
or PIM. You must configure the interface for it to performmultilink services.
NOTE: The ls-0/0/0 interface has been deprecated. All multiclass multilink features supported by
ls-0/0/0 are nowsupported by lsq-0/0/0.
See Link Services Interfaces Overview on page 413.
lsq-0/0/0
Interface used to provide class-of-service (CoS) support for real-time performance monitoring
(RPM) probe packets.
Within a J Series device, packets are routed to this internal interface for services. The lt interface is
an internal interface only and is not associated with a physical mediumor PIM. You must configure
the interface for it to performCoS for RPMservices.
NOTE: The lt interface on the MSeries and T Series routing platforms supports configuration of
logical devicesthe capability to partition a single physical device into multiple logical devices that
performindependent routing tasks. However, the lt interface on the J Series device does not support
logical devices.
See the Junos OS Class of Service Configuration Guide for Security Devices.
lt-0/0/0
Table 4: Configurable Services Interfaces (continued)
Protocol Independent Multicast (PIM) de-encapsulationinterface. InPIMsparsemode, thefirst-hop
routing platformencapsulates packets destined for the rendezvous point device. The packets are
encapsulated with a unicast header and are forwarded through a unicast tunnel to the rendezvous
point. The rendezvous point then de-encapsulates the packets and transmits themthrough its
multicast tree.
Within a device, packets are routed to this internal interface for de-encapsulation. The PIM
de-encapsulationinterfaceis aninternal interfaceonly andis not associatedwithaphysical interface.
You must configure PIMwith the [edit protocol pim] hierarchy to performPIMde-encapsulation.
See Tunnel Services Overviewin the Junos OS Services Interfaces Configuration Guide.
pd-0/0/0
Protocol Independent Multicast (PIM) encapsulation interface. In PIMsparse mode, the first-hop
routing platformencapsulates packets destined for the rendezvous point device. The packets are
encapsulated with a unicast header and are forwarded through a unicast tunnel to the rendezvous
point. The rendezvous point then de-encapsulates the packets and transmits themthrough its
multicast tree.
Withinadevice, packets areroutedtothis internal interfacefor encapsulation. ThePIMencapsulation
interface is an internal interface only and is not associated with a physical interface. You must
configure PIMwith the [edit protocol pim] hierarchy to performPIMencapsulation. See Tunnel
Services Overviewin the Junos OS Services Interfaces Configuration Guide.
pe-0/0/0
Configurable PPPoE encapsulation interface. PPP packets being routed in an Ethernet network use
PPPoE encapsulation.
Within a J Series device, packets are routed to this internal interface for PPPoE encapsulation. The
PPPoE encapsulation interface is an internal interface only and is not associated with a physical
mediumor PIM. You must configure the interface for it to forward PPPoE traffic.
See Understanding Point-to-Point Protocol over Ethernet on page 469.
pp0
Secure tunnel interface used for IPSec VPNs. See Implementing Policy Based IPsec VPN Using SRX
Series Services Gateways at
http://www.juniper.net/us/en/local/pdf/app-notes/3500175-en.pdf .
st0
Configurable USB modemphysical interface. This interface is detected when an USB modemis
connected to the USB port on the device.
NOTE: The J4350and J6350devices have two USB ports. However, you can connect only one USB
modemto the USBports on these devices. If you connect USBmodems to both the USBports, only
the first USB modemconnected to the device is recognized.
See USB Modems for Dial Backup on page 373.
umd0
Table 5 on page 7 describes non-configuable services interfaces for SRX Series Services
Gateways and J Series Services Routers.
Table 5: Non-Configurable Services Interfaces
Internally generated GRE interface. The Junos OS generates this interface to handle GRE. It is not
a configurable interface.
gre
Table 5: Non-Configurable Services Interfaces (continued)
Internally generatedIP-over-IPinterface. The Junos OSgenerates this interface tohandle IP-over-IP
encapsulation. It is not a configurable interface.
ipip
Internally generatedlink services interface. The Junos OSgenerates this interface tohandle multilink
services like MLPPP, MLFR, and CRTP. It is not a configurable interface.
lsi
Internally configured interface used by the systemas a control path between the WXC Integrated
Services Module and the Routing Engine. It is not a configurable interface. See the WXC Integrated
Services Module Installation and Configuration Guide.
pc-pim/0/0
Internally generated Protocol Independent Multicast (PIM) de-encapsulation interface. The Junos
OS generates this interface to handle PIMde-encapsulation. It is not a configurable interface.
pimd
Internally generated Protocol Independent Multicast (PIM) encapsulation interface. The Junos OS
generates this interface to handle PIMencapsulation. It is not a configurable interface.
pime
Internally generated interface. The Junos OS generates this interface to monitor and record traffic
during passive monitoring. When packets are discarded by the Packet Forwarding Engine, they are
placed on this interface. It is not a configurable interface.
tap
Related
Documentation
Special Interfaces
Special interfaces include management interfaces, which are primarily intended for
accessing the device remotely, the loopback interface, which has several uses depending
on the particular Junos OS feature being configured, and the discard interface.
Table 6 on page 8 describes special interfaces for SRX Series Services Gateways and
J Series Services Routers.
Table 6: Special Interfaces
On J Series devices, the fxp0 interface is the management port, and fxp1 is used as the control link
interface in a chassis cluster. On SRX Series devices, the fxp0management interface is a dedicated
port located on the Routing Engine.
fxp0, fxp1
Loopbackaddress. Theloopbackaddress has several uses, dependingontheparticular Junos feature
being configured.
lo0
Discard interface dsc
Related
Documentation
Interface Naming Conventions
Each device interface has a unique name that follows a naming convention. If you are
familiar with Juniper Networks MSeries and T Series routing platforms, be aware that
device interface names are similar to but not identical with the interface names on those
routing platforms.
The unique name of each network interface identifies its type and location and indicates
whether it is aphysical interfaceor anoptional logical unit createdonaphysical interface:
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-or-ioc/port
Network interfaces that are fractionalized into time slots include a channel number in
the name, preceded by a colon (:):
type-slot/pim-or-ioc/port:channel
Each logical interface has an additional logical unit identifier, preceded by a period (.):
type-slot/pim-or-ioc/port:<channel>.unit
The parts of an interface name are summarized in Table 7 on page 9.
Table 7: Network Interface Names
Possible Values Meaning Name Part
See Network Interfaces on page 4, Special Interfaces on page 8, and
Services Interfaces on page 5.
Type of network medium
that can connect to this
interface.
type
Table 7: Network Interface Names (continued)
J Series Services Router: The slot number begins at 1 and increases as
follows fromtop to bottom, left to right:
J2320 routerSlots 1 to 3
J2350 routerSlots 1 to 5
J4350 or J6350 routerPIMslots 1 to 6
The slot number 0 is reserved for the out-of-band management ports.
SRX5600andSRX5800devices: Theslot number beginsat 0andincreases
as follows fromleft to right, bottomto top:
SRX5600 deviceSlots 0 to 5
SRX5800 deviceSlots 0 to 5, 7 to 11
SRX3400andSRX3600devices: TheSwitchFabric Board(SFB) is always
0. Slot numbers increase as follows fromtop to bottom, left to right:
SRX3400 devceSlots 0 to 4
SRX3600 deviceSlots 0 to 6
Number of the chassis slot in
which a PIMor IOC is
installed.
slot
J Series devices: This number is always 0. Only one PIMcan be installed in
a slot.
SRX5600 and SRX5800 devices: For 40-port Gigabit Ethernet IOCs or
4-port 10-Gigabit Ethernet IOCs, this number can be 0, 1, 2, or 3.
SRX3400 and SRX3600 devices: This number is always 0. Only one IOC
can be installed in a slot.
Number of the PIMor IOCon
which the physical interface
is located.
pim-or-ioc
J Series Services Routers:
On a single-port PIM, the number is always 0.
On a multiple-port PIM, this number begins at 0 and increases fromleft
to right, bottomto top, to a maximumof 3.
On SRX5600 and SRX5800 devices:
For 40-port Gigabit Ethernet IOCs, this number begins at 0andincreases
fromleft to right to a maximumof 9.
For 4-port 10-Gigabit Ethernet IOCs, this number is always 0.
On SRX3400 and SRX3600 devices:
For the SFB built-in copper Gigabit Ethernet ports, this number begins
at 0 and increases fromtop to bottom, left to right, to a maximumof 7.
For the SFB built-in fiber Gigabit Ethernet ports, this number begins at
8 and increases fromleft to right to a maximumof 11.
For 16-port Gigabit Ethernet IOCs, this number begins at 0toamaximum
of 15.
For 2-port 10-Gigabit Ethernet IOCs, this number is 0 or 1.
Port numbers appear on the PIMor IOC faceplate.
Number of the port on a PIM
or IOC on which the physical
interface is located.
port
Table 7: Network Interface Names (continued)
On an E1 interface, a value from1 through 31. The 1 time slot is reserved.
On a T1 interface, a value from1 through 24.
Number of thechannel (time
slot) on a fractional or
channelizedT1 or E1 interface.
channel
A value from0 through 16384.
If no logical interface number is specified, unit 0 is the default, but must
be explicitly configured.
Number of the logical
interface created on a
physical interface.
unit
For example, the interface name e1-5/0/0:15.0 on a J Series Services Router represents
the following information:
E1 WAN interface
PIMslot 5
PIMnumber 0 (always 0)
Port 0
Channel 15
Logical interface, or unit, 0
Related
Documentation
Interface Descriptors Overviewin the Junos OS Network Interfaces Configuration Guide
Services Interface Naming Overviewin the Junos OS Services Interfaces Configuration
Guide
Interface Logical Properties
Understanding Protocol Families on page 12
Understanding IPv4 Addressing on page 13
IPv6 Addressing on page 16
Understanding Virtual LANs on page 20
Understanding Interface Logical Properties
The logical properties of an interface are the characteristics that do not apply to the
physical interface or the wires connected to it. Logical properties include:
Protocol families running on the interface (including any protocol-specific MTUs)
IP address or addresses associated with the interface. A logical interface can be
configured with an IPv6 address, IPv4 address, or both. The IP specification requires a
unique address on every interface of each systemattached to an IP network, so that
traffic can be correctly routed. Individual hosts such as home computers must have a
single IP address assigned. Devices must have a unique IP address for every interface.
Virtual LAN (VLAN) tagging
Any firewall filters or routing policies that are operating on the interface
Related
Documentation
Understanding Protocol Families on page 12
Understanding Virtual LANs on page 20
Configuring the Interface Address in the Junos OS Network Interfaces Configuration
Guide
Understanding Protocol Families
Aprotocol family is agroupof logical properties withinaninterfaceconfiguration. Protocol
families include all the protocols that make up a protocol suite. To use a protocol within
a particular suite, you must configure the entire protocol family as a logical property for
aninterface. Theprotocol families includecommonandnot-so-commonprotocol suites.
This topic contains the following sections:
Common Protocol Suites on page 12
Other Protocol Suites on page 13
Common Protocol Suites
Junos OS protocol families include the following common protocol suites:
InetSupports IP protocol traffic, including OSPF, BGP, and Internet Control Message
Protocol (ICMP).
Inet6Supports IPv6 protocol traffic, including RIP for IPv6 (RIPng), IS-IS, and BGP.
ISOSupports IS-IS traffic.
MPLSSupports MPLS.
NOTE: Junos OS security features are flow-basedmeaning the device sets
up a flowto examine the traffic. Flow-based processing is not supported for
ISOor MPLS protocol families.
Other Protocol Suites
In addition to the common protocol suites, Junos protocol families sometimes use the
following protocol suites:
cccCircuit cross-connect (CCC).
mlfr-uni-nniMultilinkFrameRelay(MLFR) FRF.16user-to-networknetwork-to-network
(UNI NNI).
mlfr-end-to-endMultilink Frame Relay end-to-end.
mlpppMultilink Point-to-Point Protocol.
tccTranslational cross-connect (TCC).
tnpTrivial Network Protocol. This Juniper Networks proprietary protocol provides
communication between the Routing Engine and the device's packet forwarding
components. Junos OS automatically configures this protocol family on the device's
internal interfaces only.
Related
Documentation
Configuring the Protocol Family in the Junos OSNetwork Interfaces Configuration Guide
Understanding IPv4 Addressing
IPv4addresses are32-bit numbers that aretypically displayedindotteddecimal notation.
A 32-bit address contains two primary parts: the network prefix and the host number.
All hosts within a single network share the same network address. Each host also has an
address that uniquely identifies it. Depending on the scope of the network and the type
of device, the address is either globally or locally unique. Devices that are visible to users
outside the network (webservers, for example) must have a globally unique IP address.
Devices that are visible only within the network (J Series devices, for example) must have
locally unique IP addresses.
IP addresses are assigned by a central numbering authority called the Internet Assigned
Numbers Authority (IANA). IANA ensures that addresses are globally unique where
needed and has a large address space reserved for use by devices not visible outside
their own networks.
IPv4 Classful Addressing on page 14
IPv4 Dotted Decimal Notation on page 14
IPv4 Subnetting on page 14
IPv4 Variable-Length Subnet Masks on page 15
IPv4 Classful Addressing
Toprovide flexibility inthe number of addresses distributedtonetworks of different sizes,
4-octet (32-bit) IP addresses were originally divided into three different categories or
classes: class A, class B, and class C. Each address class specifies a different number of
bits for its network prefix and host number:
Class A addresses use only the first byte (octet) to specify the network prefix, leaving
3 bytes to define individual host numbers.
Class B addresses use the first 2 bytes to specify the network prefix, leaving 2 bytes to
define host addresses.
Class C addresses use the first 3 bytes to specify the network prefix, leaving only the
last byte to identify hosts.
In binary format, with an x representing each bit in the host number, the three address
classes can be represented as follows:
00000000 xxxxxxxx xxxxxxxx xxxxxxxx (Class A)
00000000 00000000 xxxxxxxx xxxxxxxx (Class B)
00000000 00000000 00000000 xxxxxxxx (Class C)
Because each bit (x) in a host number can have a 0 or 1 value, each represents a power
of 2. For example, if only 3 bits are available for specifying the host number, only the
following host numbers are possible:
111 110 101 100 011 010 001 000
IneachIPaddress class, thenumber of host-number bits raisedtothepower of 2indicates
howmany host numbers canbecreatedfor aparticular network prefix. Class Aaddresses
have 2
24
(or 16,777,216) possible host numbers, class B addresses have 2
16
(or 65,536)
host numbers, and class C addresses have 2
8
(or 256) possible host numbers.
IPv4 Dotted Decimal Notation
The 32-bit IPv4addresses are most often expressedin dotteddecimal notation, in which
each octet (or byte) is treated as a separate number. Within an octet, the rightmost bit
represents 2
0
(or 1), increasing to the left until the first bit in the octet is 2
7
(or 128).
Following are IP addresses in binary format and their dotted decimal equivalents:
11010000 01100010 11000000 10101010 = 208.98.192.170
01110110 00001111 11110000 01010101 = 118.15.240.85
00110011 11001100 00111100 00111011 = 51.204.60.59
IPv4 Subnetting
Because of the physical and architectural limitations on the size of networks, you often
must break large networks into smaller subnetworks. Within a network, each wire or ring
requires its own network number and identifying subnet address.
Figure 1 on page 15 shows two subnets in a network.
Figure 1: Subnets in a Network
Figure 1 on page 15 shows three devices connectedto one subnet and three more devices
connected to a second subnet. Collectively, the six devices and two subnets make up
the larger network. In this example, the network is assigned the network prefix 192.14.0.0,
a class B address. Each device has an IP address that falls within this network prefix.
In addition to sharing a network prefix (the first two octets), the devices on each subnet
share a third octet. The third octet identifies the subnet. All devices on a subnet must
have the same subnet address. In this case, the alpha subnet has the IP address
192.14.126.0 and the beta subnet has the IP address 192.14.17.0.
The subnet address 192.14.17.0 can be represented as follows in binary notation:
11000000 . 00001110 . 00010001 . xxxxxxxx
Because the first 24 bits in the 32-bit address identify the subnet, the last 8 bits are not
significant. To indicate the subnet, the address is written as 192.14.17.0/24 (or just
192.14.17/24). The /24 is the subnet mask (sometimes shown as 255.255.255.0).
IPv4 Variable-Length Subnet Masks
Traditionally, subnets were divided by address class. Subnets had either 8, 16, or
24 significant bits, corresponding to 2
24
, 2
16
, or 2
8
possible hosts. As a result, an entire /16
subnet had to be allocated for a network that required only 400 addresses, wasting
65,136 (2
16
400 = 65,136) addresses.
Tohelpallocate address spaces more efficiently, variable-length subnet masks (VLSMs)
wereintroduced. UsingVLSM, networkarchitects canallocatemoreprecisely thenumber
of addresses required for a particular subnet.
For example, suppose a network with the prefix 192.14.17/24 is divided into two smaller
subnets, one consisting of 18 devices and the other of 46 devices.
To accommodate 18 devices, the first subnet must have 2
5
(32) host numbers. Having
5 bits assigned to the host number leaves 27 bits of the 32-bit address for the subnet.
The IP address of the first subnet is therefore 192.14.17.128/27, or the following in binary
notation:
11000000 . 00001110 . 00010001 . 100xxxxx
The subnet mask includes 27 significant digits.
To create the second subnet of 46 devices, the network must accommodate 2
6
(64)
host numbers. The IP address of the second subnet is 192.14.17.64/26, or
11000000 . 00001110 . 00010001 . 01xxxxxx
By assigning address bits within the larger /24 subnet mask, you create two smaller
subnets that use the allocated address space more efficiently.
Related
Documentation
IPv6 Addressing
Configuring the inet6 IPv6 Protocol Family on page 18
Enabling Flow-Based Processing for IPv6 Traffic on page 19
Understanding IPv6 Addressing
To create a much larger address space and relieve a projected future shortage of IP
addresses, IPv6 was created. IPv6 addresses consist of 128 bits, instead of 32 bits, and
include a scope field that identifies the type of application suitable for the address. IPv6
does not support broadcast addresses, but instead uses multicast addresses for
broadcast. In addition, IPv6 defines a newtype of address called anycast.
IPv6 Address Representation on page 16
IPv6 Address Types on page 17
IPv6 Address Scope on page 17
IPv6 Address Structure on page 17
IPv6 Address Representation
IPv6 addresses consist of 8 groups of 16-bit hexadecimal values separated by colons
(:). IPv6 addresses have the following format:
aaaa:aaaa:aaaa:aaaa:aaaa:aaaa:aaaa:aaaa
Eachaaaaisa16-bit hexadecimal value, andeachaisa4-bit hexadecimal value. Following
is a sample IPv6 address:
3FFE:0000:0000:0001:0200:F8FF:FE75:50DF
You can omit the leading zeros of each 16-bit group, as follows:
3FFE:0:0:1:200:F8FF:FE75:50DF
You can compress 16-bit groups of zeros to double colons (::) as shown in the following
example, but only once per address:
3FFE::1:200:F8FF:FE75:50DF
An IPv6 address prefix is a combination of an IPv6 prefix (address) and a prefix length.
The prefix takes the formipv6-prefix/prefix-length and represents a block of address
space (or a network). The ipv6-prefix variable follows general IPv6 addressing rules. The
/prefix-length variable is a decimal value that indicates the number of contiguous,
higher-order bits of the address that make up the network portion of the address. For
example, 10FA:6604:8136:6502::/64 is a possible IPv6 prefix.
For more information on the text representation of IPv6 addresses and address prefixes,
see RFC 4291, IP Version 6 Addressing Architecture.
IPv6 Address Types
IPv6 has three types of addresses:
UnicastFor a single interface.
MulticastFor a set of interfaces on the same physical medium. A packet is sent to all
interfaces associated with the address.
AnycastFor a set of interfaces on different physical media. A packet is sent to only
one of the interfaces associated with this address, not to all the interfaces.
IPv6 Address Scope
Unicast and multicast IPv6 addresses support address scoping, which identifies the
application suitable for the address.
Unicast addresses support global address scope and two types of local address scope:
Link-local unicast addressesUsed only on a single network link. The first 10 bits of
the prefix identify the address as a link-local address. Link-local addresses cannot be
used outside the link.
Site-local unicast addressesUsed only within a site or intranet. A site consists of
multiple network links. Site-local addresses identify nodes inside the intranet and
cannot be used outside the site.
Multicast addresses support 16 different types of address scope, including node, link,
site, organization, andglobal scope. A4-bit fieldintheprefix identifies theaddress scope.
IPv6 Address Structure
Unicast addresses identify a single interface. Each unicast address consists of n bits for
the prefix, and 128 n bits for the interface ID.
Multicast addresses identify a set of interfaces. Each multicast address consists of the
first 8 bits of all 1s, a 4-bit flags field, a 4-bit scope field, and a 112-bit group ID:
11111111 | flgs | scop | group ID
The first octet of 1s identifies the address as a multicast address. The flags fieldidentifies
whether the multicast address is a well-known address or a transient multicast address.
Thescopefieldidentifies thescopeof themulticast address. The112-bit groupIDidentifies
the multicast group.
Similar to multicast addresses, anycast addresses identify a set of interfaces. However,
packets are sent to only one of the interfaces, not to all interfaces. Anycast addresses
are allocated fromthe normal unicast address space and cannot be distinguished from
a unicast address in format. Therefore, each member of an anycast group must be
configured to recognize certain addresses as anycast addresses.
Related
Documentation
Configuring the inet6 IPv6 Protocol Family
In configuration commands, the protocol family for IPv6 is named inet6. In the
configuration hierarchy, instances of inet6 are parallel to instances of inet, the protocol
family for IPv4. In general, you configure inet6 settings and specify IPv6 addresses in
parallel to inet settings and IPv4 addresses.
The following example shows the CLI commands you use to configure an IPv6 address
for an interface:
[edit]
user@host# showinterfaces
ge-0/0/0 {
unit 0 {
family inet {
address 10.100.37.178/24;
}
}
}
[edit]
user@host# set interfaces ge-0/0/0unit 0family ?
Possible completions:
+ apply-groups Groups from which to inherit configuration data
+ apply-groups-except Don't inherit configuration data from these groups
> ccc Circuit cross-connect parameters
> ethernet-switching Ethernet switching parameters
> inet IPv4 parameters
> inet6 IPv6 protocol parameters
> iso OSI ISO protocol parameters
> mpls MPLS protocol parameters
> tcc Translational cross-connect parameters
> vpls Virtual private LAN service parameters
[edit]
user@host# set interfaces ge-0/0/0unit 0family inet6 address 8d8d:8d01::1/64
ge-0/0/0 {
unit 0 {
family inet {
address 10.100.37.178/24;
}
family inet6 {
address 8d8d:8d01::1/64;
}
}
}
Related
Documentation
Junos OS Network Interfaces Configuration Guide
Enabling Flow-Based Processing for IPv6 Traffic
You have the following options for handling IPv6 traffic:
DropDo not forward IPv6 packets. This is the default behavior.
Packet-based forwardingDo not create a session and process according to
packet-based features only (includes firewall filters and class of service).
Flow-based forwardingCreate a session and process according to packet-based
features (including firewall filters and class of service) but also flow-based security
features, such as screens and firewall security policy.
NOTE: Packet-based forwarding is not supported for SRX3400, SRX3600,
SRX5600, or SRX5800 devices; and the option is unavailable in the CLI.
To enable flow-basedprocessing for IPv6traffic, modify the mode statement at the [edit
security forwarding-options family inet6] hierarchy level:
security {
forwarding-options {
family {
inet6 {
mode flow-based;
}
}
}
}
The following example shows the CLI commands you use to configure forwarding for
IPv6 traffic:
[edit]
user@host# set security forwarding-options family inet6 mode ?
Possible completions:
drop Disable forwarding
flow-based Enable flow-based forwarding
packet-based Enable packet-based forwarding
[edit]
user@host# set security forwarding-options family inet6 mode flow-based
user@host# showsecurity forwarding-options
family {
inet6 {
mode flow-based;
}
}
If you change the forwarding option mode for IPv6, you might need to performa reboot
to initialize the configuration change. Table 8on page 20summarizes device status upon
configuration change.
Table 8: Device Status Upon Configuration Change
Impact on NewTraffic
Before Reboot
Impact on Existing
Traffic Before Reboot
Reboot
Required
Commit
Warning Configuration Change
Dropped Dropped Yes Yes Drop to flow-based
Packet-based Packet-based No No Drop to packet-based
Flowsessions created None Yes Yes Flow-based to packet-based
Flowsessions created None Yes Yes Flow-based to drop
Packet-based Packet-based Yes Yes Packet-based to flow-based
Dropped Dropped No No Packet-based to drop
For details on packet-based and flow-based processing, see the Junos OS Security
Configuration Guide.
Related
Documentation
Understanding Virtual LANs
A LAN is a single broadcast domain. When traffic is broadcast, all hosts within the LAN
receive the broadcast traffic. ALANis determined by the physical connectivity of devices
within the domain.
Within a traditional LAN, hosts are connected by a hub or repeater that propagates any
incoming traffic throughout the network. Each host and its connecting hubs or repeaters
make up a LANsegment. LANsegments are connected through switches and bridges to
formthe broadcast domainof the LAN. Figure 2 onpage 21 shows atypical LANtopology.
Figure 2: Typical LAN
Virtual LANs (VLANs) allownetwork architects tosegment LANs intodifferent broadcast
domains based on logical groupings. Because the groupings are logical, the broadcast
domains are not determined by the physical connectivity of the devices in the network.
Hosts can be grouped according to a logical function, to limit the traffic broadcast within
the VLAN to only the devices for which the traffic is intended.
Suppose a corporate network has three major organizations: engineering, sales, and
support. UsingVLANtagging, hostswithineachorganizationcanbetaggedwithadifferent
VLAN identifier. Traffic sent to the broadcast domain is then checked against the VLAN
identifier and broadcast to only the devices in the appropriate VLAN. Figure 3 on page 21
shows a typical VLAN topology.
Figure 3: Typical VLAN
Related
Documentation
Understanding VPLS VLAN Encapsulation in the Junos OS MPLS Configuration Guide
Example: Configuring VPLS VLAN Encapsulation on Gigabit Ethernet Interfaces in the
Junos OS MPLS Configuration Guide for Security Devices
Interface Physical Properties
Understanding Bit Error Rate Testing on page 23
Understanding Interface Clocking on page 24
Understanding Frame Check Sequences on page 25
MTU Default and MaximumValues on page 26
Understanding Interface Physical Properties
The physical properties of a network interface are the characteristics associated with
the physical link that affect the transmissionof either link-layer signals or the dataacross
the links. Physical properties include clocking properties, transmission properties, such
as the maximumtransmission unit (MTU), and encapsulation methods, such as
point-to-point and Frame Relay encapsulation.
The default property values for an interface are usually sufficient to successfully enable
a bidirectional link. However, if you configure a set of physical properties on an interface,
thosesameproperties must beset onall adjacent interfaces towhichadirect connection
is made.
Table 9 on page 22 summarizes some key physical properties of device interfaces.
Table 9: Interface Physical Properties
Description Physical Property
Bit error rate (BER). The error rate specifies the number of bit errors in a particular bit error rate test
(BERT) period required to generate a BERT error condition. See Understanding Bit Error Rate
Testing on page 23.
bert-error-rate
Bit error rate test (BERT) time period over which bit errors are sampled. See Understanding Bit
Error Rate Testing on page 23.
bert-period
ChallengeHandshakeAuthenticationProtocol (CHAP). SpecifyingchapenablesCHAPauthentication
on the interface. See Understanding CHAP Authentication on a PPPoE Interface on page 481.
chap
Clock sourcefor thelink. Clockingcanbeprovidedby thelocal system(internal) or aremoteendpoint
on the link (external). By default, all interfaces use the internal clocking mode. If an interface is
configured to accept an external clock source, one adjacent interface must be configured to act as
a clock source. Under this configuration, the interface operates in a loop timing mode, in which the
clocking signal is unique for that individual network segment or loop. See Understanding Interface
Clocking on page 24.
clocking
A user-defined text description of the interface, often used to describe the interface's purpose. description
Table 9: Interface Physical Properties (continued)
Description Physical Property
Administratively disables the interface. disable
Type of encapsulation on the interface. Common encapsulation types include PPP, Frame Relay,
Cisco HDLC, and PPP over Ethernet (PPPoE). See Understanding Physical Encapsulation on an
Interface on page 461.
encapsulation
Frame check sequence (FCS). FCSis an error-detection scheme that appends parity bits to a digital
signal and uses decoding algorithms that detect errors in the received digital signal. See
Understanding Frame Check Sequences on page 25.
fcs
Maximumtransmission unit (MTU) size. MTU is the largest size packet or frame, specified in bytes
or octets, that can be sent in a packet-based or frame-based network. The TCP uses MTU to
determine the maximumsize of each packet in any transmission. See MTUDefault and Maximum
Values on page 26.
mtu
Disablingof keepalivemessages across aphysical link. Akeepalivemessageis sent betweennetwork
devices to indicate that they are still active. Keepalives help determine whether the interface is
operating correctly. Except for ATM-over-ADSL interfaces, all interfaces use keepalives by default.
See Configuring Keepalives in the Junos OS Network Interfaces Configuration Guide.
no-keepalives
Password Authentication Protocol (PAP). Specifying pap enables PAP authentication on the
interface. See Understanding CHAP Authentication on a PPPoE Interface on page 481.
pap
Scramblingof traffictransmittedout theinterface. Payloadscramblingrandomizes thedatapayload
of transmitted packets. Scrambling eliminates nonvariable bit patterns (strings of all 1s or all 0s)
that generate link-layer errors across some physical links. See Configuring E3 HDLC Payload
Scrambling, Configuring T3 HDLC Payload Scrambling, and payload-scrambler in the Junos OS
Network Interfaces Configuration Guide.
payload-scrambler
Related
Documentation
Understanding Bit Error Rate Testing on page 23
Understanding Interface Clocking on page 24
Understanding Frame Check Sequences on page 25
MTU Default and MaximumValues on page 26
Understanding Bit Error Rate Testing
In telecommunication transmission, the bit error rate (BER) is the percentage of bits that
have errors compared to the total number of bits received in a transmission, usually
expressed as 10 to a negative power. For example, a transmission with a BER of 10
6
received1 erroredbit in1,000,000bits transmitted. TheBERindicates howoftenapacket
or other data unit must be retransmitted because of an error. If the BER is too high, a
slower data rate might improve the overall transmission time for a given amount of data
if it reduces the BER and thereby lowers the number of resent packets.
A bit error rate test (BERT) is a procedure or device that measures the BER for a given
transmission. You can configure a device to act as a BERT device by configuring the
interface with a bit error rate and a testing period. When the interface receives a BERT
request froma BER tester, it generates a response in a well-known BERT pattern. The
initiating device checks the BERT-patterned response to determine the number of bit
errors.
Related
Documentation
Interface Diagnostics in the Junos OS Network Interfaces Configuration Guide
Understanding Interface Clocking
Clockingdetermines howindividual routingnodes or entirenetworks sampletransmitted
data. As streams of information are received by a device in a network, a clock source
specifies whentosample the data. Inasynchronous networks, the clock source is derived
locally, andsynchronous networks use a central, external clock source. Interface clocking
indicates whether the device uses asynchronous or synchronous clocking.
NOTE: Because truly synchronous networks are difficult to design and
maintain, most synchronous networks are really plesiochronous networks.
In a plesiochronous network, different timing regions are controlled by local
clocks that are synchronized (with very narrowconstraints). Such networks
approach synchronicity and are generally known as synchronous networks.
Most networks aredesignedtooperateas asynchronous networks. Eachdevicegenerates
its own clock signal, or devices use clocks frommore than one clock source. The clocks
within the network are not synchronized to a single clock source. By default, devices
generate their own clock signals to send and receive traffic.
Thesystemclockallows thedevicetosample(or detect) andtransmit databeingreceived
andtransmittedthroughits interfaces. Clockingenables thedevicetodetect andtransmit
the 0s and 1s that make up digital traffic through the interface. Failure to detect the bits
within a data flowresults in dropped traffic.
Short-termfluctuations in the clock signal are known as clock jitter. Long-termvariations
in the signal are known as clock wander.
Asynchronous clockingcaneither derivetheclock signal fromthedatastreamor transmit
the clocking signal explicitly.
Data StreamClocking on page 25
Explicit Clocking Signal Transmission on page 25
Data StreamClocking
Common in T1 links, data streamclocking occurs when separate clock signals are not
transmitted within the network. Instead, devices must extract the clock signal fromthe
data stream. As bits are transmitted across the network, each bit has a time slot of
648 nanoseconds. Within a time slot, pulses are transmitted with alternating voltage
peaks anddrops. Thereceivingdeviceuses theperiodof alternatingvoltages todetermine
the clock rate for the data stream.
Explicit Clocking Signal Transmission
Clock signals that are shared by hosts across a data link must be transmitted by one or
both endpoints on the link. In a serial connection, for example, one host operates as a
clock master and the other operates as a clock slave. The clock master internally
generates a clock signal that is transmitted across the data link. The clock slave receives
theclocksignal anduses its periodtodeterminewhentosampledataandhowtotransmit
data across the link.
This typeof clocksignal controls only theconnectiononwhichit is activeandis not visible
to the rest of the network. An explicit clock signal does not control howother devices or
even other interfaces on the same device sample or transmit data.
Related
Documentation
Configuring the Clock Source in the Junos OS Network Interfaces Configuration Guide.
Understanding Frame Check Sequences
All packets or frames within a network can be damaged by crosstalk or interference in
the network's physical wires. The frame check sequence (FCS) is an extra field in each
transmitted frame that can be analyzed to determine if errors have occurred. The FCS
uses cyclic redundancy checks (CRCs), checksums, and two-dimensional parity bits to
detect errors in the transmitted frames.
Cyclic Redundancy Checks and Checksums on page 25
Two-Dimensional Parity on page 26
Cyclic Redundancy Checks and Checksums
Onalink that uses CRCs for framechecking, thedatasourceuses apredefinedpolynomial
algorithmtocalculateaCRCnumber fromthedatait is transmitting. Theresult is included
in the FCS field of the frame and transmitted with the data. On the receiving end, the
destination host performs the same calculation on the data it receives.
If the result of the second calculation matches the contents of the FCS field, the packet
was sent and received without bit errors. If the values do not match, an FCS error is
generated, the frame is discarded and the originating host is notified of the error.
Checksums function similarly to CRCs, but use a different algorithm.
Two-Dimensional Parity
On a link that uses two-dimensional parity bits for frame checking, the sending and
receiving hosts examine each frame in the total packet transmission and create a parity
byte that is evaluated to detect transmission errors.
For example, a host can create the parity byte for the following frame sequence by
summing up each column (each bit position in the frame) and keeping only the
least-significant bit:
Frame 1 0 1 0 1 0 0 1
Frame 2 1 1 0 1 0 0 1
Frame 3 1 0 1 1 1 1 0
Frame 4 0 0 0 1 1 1 0
Frame 5 0 1 1 0 1 0 0
Frame 6 1 0 1 1 1 1 1
Parity Byte 1 1 1 1 0 1 1
If the sumof the bit values in a bit position is even, the parity bit for the position is 0. If
the sumis odd, the parity bit is 1. This method is called even parity. Matching parity bytes
onthe originating andreceiving hosts indicate that the packet was receivedwithout error.
Related
Documentation
MTUDefault and MaximumValues
Table 10 on page 26 lists MTU values for J Series devices.
Table 10: MTUValues for J2320, J2350, J4350, and J6350Interfaces
Default IP MTU
(bytes)
MaximumMTU
(bytes)
Default MediaMTU
(bytes) J4350 and J6350 Interfaces
1500 9018 1514 Gigabit Ethernet (10/100/1000) built-in interface
1500 9014 1514 6-Port, 8-Port, and 16-Port Gigabit Ethernet uPIMs
1500 9018 1514 Gigabit Ethernet (10/100/1000) ePIM
1500 9018 1514 Gigabit Ethernet (10/100/1000) SFP ePIM
1500 1514 1514 4-Port Fast Ethernet (10/100) ePIM
1500 9192 1514 Dual-Port Fast Ethernet (10/100) PIM
1500 9150 1504 Dual-Port Serial PIM
1500 9192 1504 Dual-Port T1 or E1 PIM
Table 10: MTUValues for J2320, J2350, J4350, and J6350Interfaces (continued)
Default IP MTU
(bytes)
MaximumMTU
(bytes)
Default MediaMTU
(bytes) J4350 and J6350 Interfaces
1500 4500 1504 Dual-Port ChannelizedT1/E1/ISDNPRI PIM(channelized
to DS0s)
1500 9150 1504 Dual-Port Channelized T1/E1/ISDN PRI PIM
(clear-channel T1 or E1)
1500 4098 1504 Dual-Port Channelized T1/E1/ISDN PRI PIM(ISDN PRI
dialer interface)
4470 9192 4474 T3 (DS3) or E3 PIM
1500 4092 1504 4-Port ISDN BRI PIM
4470 9150 4482 ADSL+2 PIM
4470 9150 4482 G.SHDSL PIM
Table 11 on page 27 lists MTU values for the SRX Series Services Gateways Physical
Interface Modules (PIMs).
Table 11: MTUValues for the SRX Series Services Gateways PIMs
MaximumMTU
(Bytes) Default MTU(Bytes)
Logical Interface
MTU(Bytes)
Physical Interface
MTU(Bytes) PIM
9010 1514 1500 1514 1-Port Gigabit Ethernet
Small Form-Factor
Pluggable (SFP)
Mini-PIM
1518 1514 1500 1514 1-Port Small
Form-Factor Pluggable
(SFP) Mini-PIM
1512 1496 1456 1496 ADSL2+ Mini-PIM
1504 1504 1500 1504 DOCSIS Mini-PIM
4482 1496 1468 1496 G.SHDSL Mini-PIM
2000 1504 1500 1504 Serial Mini-PIM
2000 1504 1500 1504 T1/E1 Mini-PIM
1496 1496 1482 1496 VDSL2 Mini-PIM
9000 1504 1500 1504 Dual CT1/E1 GPIM
Table 11: MTUValues for the SRX Series Services Gateways PIMs (continued)
MaximumMTU
(Bytes) Default MTU(Bytes)
Logical Interface
MTU(Bytes)
Physical Interface
MTU(Bytes) PIM
9000 1504 1500 1504 Quad CT1/E1 GPIM
Unspecified 1514 Unspecified 1514 2-Port 10 Gigabit
Ethernet XPIM
Unspecified 1514 Unspecified 1514 16-Port Gigabit
Ethernet XPIM
Unspecified 1514 Unspecified 1514 24-Port Gigabit
Ethernet XPIM
Related
Documentation
Understanding the Data Link Layer
The Data Link Layer is Layer 2 in the Open Systems Interconnection (OSI) model. The
Data Link Layer is responsible for transmitting data across a physical network link. Each
physical mediumhas link-layer specifications for network and link-layer protocol
characteristics such as physical addressing, network topology, error notification, frame
sequencing, and flowcontrol.
Physical Addressing on page 28
Network Topology on page 28
Error Notification on page 29
Frame Sequencing on page 29
FlowControl on page 29
Data Link Sublayers on page 29
MAC Addressing on page 29
Physical Addressing
Physical addressingis different fromnetworkaddressing. Networkaddresses differentiate
between nodes or devices in a network, allowing traffic to be routed or switched through
the network. In contrast, physical addressing identifies devices at the link-layer level,
differentiating between individual devices on the same physical medium. The primary
formof physical addressing is the media access control (MAC) address.
Network Topology
Network topology specifications identify howdevices arelinkedinanetwork. Somemedia
allowdevices to be connected by a bus topology, while others require a ring topology.
The bus topology is used by Ethernet technologies, which are supported on Juniper
Networks devices.
Error Notification
The Data Link Layer provides error notifications that alert higher layer protocols that an
error has occurred on the physical link. Examples of link-level errors include the loss of
a signal, the loss of a clocking signal across serial connections, or the loss of the remote
endpoint on a T1 or T3 link.
Frame Sequencing
Theframesequencingcapabilitiesof theDataLinkLayer allowframesthat aretransmitted
out of sequence to be reordered on the receiving end of a transmission. The integrity of
the packet can then be verified by means of the bits in the Layer 2 header, which is
transmitted along with the data payload.
FlowControl
Flowcontrol within the Data Link Layer allows receiving devices on a link to detect
congestion and notify their upstreamand downstreamneighbors. The neighbor devices
relay the congestion information to their higher layer protocols so that the flowof traffic
can be altered or rerouted.
Data Link Sublayers
The Data Link Layer is divided into two sublayers: logical link control (LLC) and media
access control (MAC). The LLC sublayer manages communications between devices
over a single link of a network. This sublayer supports fields in link-layer frames that
enable multiple higher layer protocols to share a single physical link.
The MAC sublayer governs protocol access to the physical network medium. Through
the MAC addresses that are typically assigned to all ports on a device, multiple devices
on the same physical link can uniquely identify one another at the Data Link Layer. MAC
addresses are used in addition to the network addresses that are typically configured
manually on ports within a network.
MAC Addressing
A MAC address is the serial number permanently stored in a device adapter to uniquely
identify the device. MAC addresses operate at the Data Link Layer, while IP addresses
operate at the Network Layer. The IP address of a device can change as the device is
movedarounda network todifferent IPsubnets, but the MACaddress remains the same,
because it is physically tied to the device.
Within an IP network, devices match each MAC address to its corresponding configured
IP address by means of the Address Resolution Protocol (ARP). ARP maintains a table
with a mapping for each MAC address in the network.
Most Layer 2 networks use one of three primary numbering spacesMAC-48, EUI-48
(extended unique identifier), and EUI-64which are all globally unique. MAC-48 and
EUI-48 spaces each use 48-bit addresses, and EUI-64 spaces use a 64-bit addresses,
but all three use the same numbering format. MAC-48 addresses identify network
hardware, and EUI-48 addresses identify other devices and software.
The Ethernet and ATMtechnologies supported on devices use the MAC-48 address
space. IPv6 uses the EUI-64 address space.
MAC-48 addresses are the most commonly used MAC addresses in most networks.
These addresses are 12-digit hexadecimal numbers (48 bits in length) that typically
appear in one of the following formats:
MM:MM:MM:SS:SS:SS
MM-MM-MM-SS-SS-SS
The first three octets (MM:MM:MMor MM-MM-MM) are the ID number of the hardware
manufacturer. Manufacturer ID numbers are assigned by the Institute of Electrical and
Electronics Engineers (IEEE). The last three octets (SS:SS:SS or SS-SS-SS) make up the
serial number for the device, which is assigned by the manufacturer. For example, an
Ethernet interface card might have a MAC address of 00:05:85:c1:a6:a0.
Related
Documentation
PART 2
Ethernet Interfaces
Ethernet Interfaces on page 33
Aggregated Ethernet Interfaces on page 45
1-Port Gigabit Ethernet SFP Mini-PIMon page 71
2-Port 10-Gigabit Ethernet XPIMon page 79
Power over Ethernet on page 87
CHAPTER 2
Ethernet Interfaces
Understanding Ethernet Interfaces on page 33
Example: Creating an Ethernet Interface on page 37
Example: Deleting an Ethernet Interface on page 38
Static ARP Entries on Ethernet Interfaces on page 39
Promiscuous Mode on Ethernet Interfaces on page 42
Understanding Ethernet Interfaces
Ethernet is aLayer 2technology that operates inasharedbus topology. Ethernet supports
broadcast transmission, uses best-effort delivery, and has distributed access control.
Ethernet is a point-to-multipoint technology.
In a shared bus topology, all devices connect to a single, shared physical link through
which all data transmissions are sent. All traffic is broadcast so that all devices within
the topology receive every transmission. The devices within a single Ethernet topology
make up a broadcast domain.
Ethernet uses best-effort delivery to broadcast traffic. The physical hardware provides
no information to the sender about whether the traffic was received. If the receiving host
is offline, traffic to the host is lost. Although the Ethernet data link protocol does not
informthesender about lost packets, higher layer protocols suchas TCP/IPmight provide
this type of notification.
Ethernet Access Control and Transmission on page 33
Collisions and Detection on page 34
Collision Domains and LAN Segments on page 35
Broadcast Domains on page 36
Ethernet Frames on page 36
Ethernet Access Control and Transmission
Ethernet's access control is distributedbecause Ethernet has nocentral mechanismthat
grants access to the physical mediumwithin the network. Instead, Ethernet uses
carrier-sense multiple access with collision detection (CSMA/CD). Because multiple
devices onanEthernet network canaccess thephysical medium, or wire, simultaneously,
each device must determine whether the physical mediumis in use. Each host listens on
the wire to determine if a message is being transmitted. If it detects no transmission, the
host begins transmitting its own data.
The length of each transmission is determined by fixed Ethernet packet sizes. By fixing
thelengthof eachtransmissionandenforcingaminimumidletimebetweentransmissions,
Ethernet ensures that no pair of communicating devices on the network can monopolize
the wire and block others fromsending and receiving traffic.
Collisions and Detection
When a device on an Ethernet network begins transmitting data, the data takes a finite
amount of time to reach all hosts on the network. Because of this delay, or latency, in
transmitting traffic, a device might detect an idle state on the wire just as another device
initially begins its transmission. As a result, two devices might send traffic across a single
wire at the same time. When the two electrical signals collide, they become scrambled
so that both transmissions are effectively lost.
Collision Detection
To handle collisions, Ethernet devices monitor the link while they are transmitting data.
The monitoring process is known as collision detection. If a device detects a foreign signal
while it is transmitting, it terminates the transmission and attempts to transmit again
only after detecting an idle state on the wire. Collisions continue to occur if two colliding
devices bothwait thesameamount of timebeforeretransmitting. Toavoidthis condition,
Ethernet devices use a binary exponential backoff algorithm.
Backoff Algorithm
With the binary exponential backoff algorithm, each device that sends a colliding
transmission randomly selects a value within a range. The value represents the number
of transmission times that the device must wait before retransmitting its data. If another
collision occurs, the range of values is doubled and retransmission takes place again.
Each time a collision occurs, the range of values doubles, to reduce the likelihood that
two hosts on the same network can select the same retransmission time. Table 12 on
page 34 shows collision rounds up to round 10.
Table 12: Collision Backoff AlgorithmRounds
Elements in the Set Size of Set Round
{0,1} 2 1
{0,1,2,3} 4 2
{0,1,2,3,...,7} 8 3
{0,1,2,3,4,...,15} 16 4
{0,1,2,3,4,5,...,31} 32 5
{0,1,2,3,4,5,6,...,63} 64 6
Table 12: Collision Backoff AlgorithmRounds (continued)
Elements in the Set Size of Set Round
{0,1,2,3,4,5,6,7,...,127} 128 7
{0,1,2,3,4,5,6,7,8,...,255} 256 8
{0,1,2,3,4,5,6,7,8,9,...,511} 512 9
{0,1,2,3,4,5,6,7,8,9,10,...,1023} 1024 10
Collision Domains and LANSegments
Collisions are confined to a physical wire over which data is broadcast. Because the
physical wires are subject to signal collisions, individual LAN segments are known as
collision domains. Although the physical limitations on the length of an Ethernet cable
restrict the length of a LAN segment, multiple collision domains can be interconnected
by repeaters, bridges, and switches.
Repeaters
Repeaters are electronic devices that act on analog signals. Repeaters relay all electronic
signals fromone wire to another. Asingle repeater can double the distance between two
devices onanEthernet network. However, theEthernet specificationrestricts thenumber
of repeaters between any two devices on an Ethernet network to two, because collision
detection with latencies increases in complexity as the wire length and number of
repeaters increase.
Bridges and Switches
Bridges and switches combine LAN segments into a single Ethernet network by using
multiple ports to connect the physical wires in each segment. Although bridges and
switches are fundamentally the same, bridges generally provide more management and
more interface ports. As Ethernet packets flowthrough a bridge, the bridge tracks the
source MAC address of the packets and stores the addresses and their associated input
ports in an interface table. As it receives subsequent packets, the bridge examines its
interface table and takes one of the following actions:
If the destination address does not match an address in the interface table, the bridge
transmits the packet toall hosts on the network using the Ethernet broadcast address.
If the destination address maps to the port through which the packet was received,
thebridgeor switchdiscards thepacket. Becausetheother devices ontheLANsegment
also received the packet, the bridge does not need to retransmit it.
If the destination address maps to a port other than the one through which the packet
was received, the bridge transmits the packet through the appropriate port to the
corresponding LAN segment.
Chapter 2: Ethernet Interfaces
Broadcast Domains
Thecombinationof all theLANsegments withinanEthernet network is calledabroadcast
domain. In the absence of any signaling devices such as a repeater, bridge, or switch, the
broadcast domain is simply the physical wire that makes up the connections in the
network. If a bridge or switch is used, the broadcast domain consists of the entire LAN.
Ethernet Frames
Data is transmitted through an Ethernet network in frames. The frames are of variable
length, ranging from64 octets to 1518 octets, including the header, payload, and cyclic
redundancy check (CRC) value. Figure 4 on page 36 shows the Ethernet frame format.
Figure 4: Ethernet Frame Format
Ethernet frames have the following fields:
The preamble (PRE) field is 7 octets of alternating 0s and 1s. The predictable format
in the preamble allows receiving interfaces to synchronize themselves to the data
being sent. The preamble is followed by a 1-octet start-of-frame delimiter (SFD).
The destination address (DA) and source address (SA) fields contain the 6-octet
(48-bit) MAC addresses for the destination and source ports on the network. These
Layer 2 addresses uniquely identify the devices on the LAN.
The Length/Type field is a 2-octet field that either indicates the length of the frame's
data field or identifies the protocol stack associated with the frame. Here are some
common frame types:
AppleTalk0x809B
AppleTalk ARP0x80F3
DECnet0x6003
IP0x0800
IPX0x8137
Loopback0x9000
XNS0x0600
The Data field contains the packet payload.
The frame check sequence (FCS) is a 4-octet field that contains the calculated CRC
value. This valueis calculatedby theoriginatinghost andappendedtotheframe. When
it receives the frames, the receiving host calculates the CRC and checks it against this
appended value to verify the integrity of the received frame.
Related
Documentation
Understanding Static ARP Entries on Ethernet Interfaces on page 39
Understanding Promiscuous Mode on Ethernet Interfaces on page 42
Example: Creating an Ethernet Interface
This example shows howto create an Ethernet interface.
Requirements on page 37
Overviewon page 37
Configuration on page 37
Verification on page 38
Requirements
No special configuration beyond device initialization is required before configuring an
interface.
Overview
In this example, you create the ge-1/0/0 Ethernet interface and set the logical interface
to 0. The logical unit number can range from0 to 16,384. You can also add values for
properties that youneedtoconfigureonthelogical interface, suchas logical encapsulation
or protocol family.
Configuration
Step-by-Step
Procedure
To configure an Ethernet interface:
Create the Ethernet interface and set the logical interface.
[edit]
1.
user@host# edit interfaces ge-1/0/0unit 0
2. If you are done configuring the device, commit the configuration.
[edit]
user@host# commit
Verification
To verify the configuration is working properly, enter the showinterfaces command.
Related
Documentation
ping in the Junos SystemBasics and Services Command Reference
showinterfaces detail in the Junos Interfaces Command Reference
Example: Deleting an Ethernet Interface
This example shows howto delete an Ethernet interface.
Overviewon page 38
Requirements
interface.
Overview
In this example, you delete the ge-0/0/0 interface.
NOTE: Performing this action removes the interface fromthe software
configuration and disables it. Network interfaces remain physically present,
and their identifiers continue to appear on J-Web pages.
Configuration
Step-by-Step
Procedure
To delete an Ethernet interface:
Specify the interface you want to delete. 1.
[edit]
user@host# delete interfaces ge-0/0/0
[edit]
user@host# commit
Verification
Related
Documentation
Static ARP Entries on Ethernet Interfaces
Example: Configuring Static ARP Entries on Ethernet Interfaces on page 39
Understanding Static ARP Entries on Ethernet Interfaces
By default, the device responds to an Address Resolution Protocol (ARP) request only
if the destination address of the ARP request is on the local network of the incoming
interface. For Fast Ethernet or Gigabit Ethernet interfaces, you can configure static ARP
entries that associate the IP addresses of nodes on the same Ethernet subnet with their
media access control (MAC) addresses. These static ARP entries enable the device to
respond to ARP requests even if the destination address of the ARP request is not local
to the incoming Ethernet interface.
Related
Documentation
Example: Configuring Static ARP Entries on Ethernet Interfaces on page 39
Example: Configuring Static ARP Entries on Ethernet Interfaces
Overviewon page 39
Requirements
No special configuration beyond device initialization is required before creating an
interface.
Overview
In this example, you configure a static ARP entry on the logical unit 0 of the ge-0/0/3
Gigabit Ethernet interface. The entry consists of the interfaces IP address (10.1.1.1/24)
and the corresponding MAC address of a node on the same Ethernet subnet
(00:ff:85:7f:78:03). The example also configures the device to reply to ARP requests
fromthe node using the publish option.
Configuration
CLI Quick
Configuration
To quickly configure static ARP entries on Ethernet interfaces, copy the following
commands and paste theminto the CLI:
[edit]
set interfaces ge-0/0/3 unit 0family inet address 10.1.1.1/24 arp 10.1.1.3 mac
00:ff:85:7f:78:03
set interfaces ge-0/0/3 unit 0family inet address 10.1.1.1/24 arp 10.1.1.3 publish
Step-by-Step
Procedure
The following example requires you to navigate various levels in the configuration
hierarchy. For instructions on howto do that, see Using the CLI Editor in Configuration
Mode.
To configure a static ARP entry on an Ethernet interface:
1. Create the Gigabit Ethernet interface.
[edit]
user@host# edit interfaces ge-0/0/3
2. Configure a static ARP entry.
[edit interfaces ge-0/0/3]
user@host# edit unit 0family inet address 10.1.1.1/24
3. Set the IP address of the subnet node and the corresponding MAC address.
[edit interfaces ge-0/0/3 unit 0 family inet address 10.1.1.1/24]
user@host# set arp 10.1.1.3 mac 00:ff:85:7f:78:03 publish
Results Fromconfiguration mode, confirmyour configuration by entering the showinterfaces
ge-0/0/3 command. If the output does not display the intended configuration, repeat
the configuration instructions in this example to correct it.
[edit]
user@host#showinterfaces ge-0/0/3
unit 0 {
family inet {
address 10.1.1.1/24 {
arp 10.1.1.3 mac 00:ff:85:7f:78:03 publish;
}
}
}
If you are done configuring the device, enter commit fromconfiguration mode.
Verification
To confirmthat the configuration is working properly, performthese tasks:
Verifying Static ARP Configurations on page 41
Verifying the Link State of All Interfaces on page 41
Verifying Interface Properties on page 41
Verifying Static ARP Configurations
Purpose Verify the IP address and MAC (hardware) address of the node.
Action Fromoperational mode, enter the showinterfaces ge-0/0/3 command.
Verifying the Link State of All Interfaces
Purpose Verify that all interfaces on the device are operational using the ping tool on each peer
address in the network.
Action For each interface on the device:
1. In the J-Web interface, select Troubleshoot>Ping Host.
2. In the Remote Host box, type the address of the interface for which you want to verify
the link state.
3. Click Start. The output appears on a separate page.
PING 10.10.10.10 : 56 data bytes
64 bytes from 10.10.10.10: icmp_seq=0 ttl=255 time=0.382 ms
Meaning If the interface is operational, it generates an ICMP response. If this response is received,
the round-trip time in milliseconds is listed in the time field. For more information about
the output, see the Junos OS Administration Guide for Security Devices.
Verifying Interface Properties
Purpose Verify that the interface properties are correct.
Action Fromoperational mode, enter the showinterfaces detail command.
user@host> showinterfaces detail
Physical interface: ge-1/0/0, Enabled, Physical link is Up
Interface index: 134, SNMP ifIndex: 27, Generation: 17
Link-level type: Ethernet, MTU: 1514, Speed: 100mbps, Loopback: Disabled,
Source filtering: Disabled, Flow control: Enabled
Device flags : Present Running
Interface flags: SNMP-Traps 16384
Link flags : None
CoS queues : 4 supported
Hold-times : Up 0 ms, Down 0 ms
Current address: 00:90:69:87:44:9d, Hardware address: 00:90:69:87:44:9d
Last flapped : 2004-08-25 15:42:30 PDT (4w5d 22:49 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes : 0 0 bps
Output bytes : 0 0 bps
Input packets: 0 0 pps
Output packets: 0 0 pps
Queue counters: Queued packets Transmitted packets Dropped packets
0 best-effort 0 0 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
3 network-cont 0 0 0
Active alarms : None
Active defects : None
Meaning The output shows a summary of interface information. Verify the following information:
The physical interface is Enabled. If the interface is shown as Disabled, do one of the
following:
In the CLI configuration editor, delete the disable statement at the [edit interfaces
ge-1/0/0] level of the configuration hierarchy.
In the J-Web configuration editor, clear the Disable check box on the Interfaces>
ge-1/0/0 page.
The physical link is Up. A link state of Down indicates a problemwith the interface
module, interface port, or physical connection (link-layer errors).
The Last Flapped time is an expected value. The Last Flapped time indicates the last
time the physical interface became unavailable and then available again. Unexpected
flapping indicates likely link-layer errors.
The traffic statistics reflect expected input and output rates. Verify that the number
of inbound and outbound bytes and packets matches expected throughput for the
physical interface. To clear the statistics and see only newchanges, use the clear
interfaces statistics ge-1/0/0 command.
Related
Documentation
Promiscuous Mode on Ethernet Interfaces
Enabling and Disabling Promiscuous Mode on Ethernet Interfaces (CLI
Procedure) on page 43
Understanding Promiscuous Mode on Ethernet Interfaces
When promiscuous mode is enabled on a Layer 3 Ethernet interface, all packets received
onthe interface are sent tothe central point or Services Processing Unit (SPU)regardless
of the destination MAC address of the packet. You can also enable promiscuous mode
on chassis cluster redundant Ethernet interfaces and aggregated Ethernet interfaces. If
you enable promiscuous mode on a redundant Ethernet interface, promiscuous mode is
then enabled on any child physical interfaces. If you enable promiscuous mode on an
aggregated Ethernet interface, promiscuous mode is then enabled on all member
interfaces.
Related
Documentation
Enabling and Disabling Promiscuous Mode on Ethernet Interfaces (CLI Procedure) on
page 43
Enabling and Disabling Promiscuous Mode on Ethernet Interfaces (CLI Procedure)
To enable promiscuous mode on an interface:
user@host# set interfaces interface-name promiscuous-mode
To disable promiscuous mode on an interface:
user@host# delete interfaces interface-name promiscuous-mode
Related
Documentation
CHAPTER 3
Aggregated Ethernet Interfaces
Aggregated Ethernet Interfaces on page 45
LACP for Standalone Devices on page 59
LACP on Chassis Clusters on page 64
Aggregated Ethernet Interfaces
Understanding Aggregated Ethernet Interfaces on page 45
Aggregated Ethernet Interfaces Configuration Overviewon page 47
Device Count for Aggregated Ethernet Interfaces on page 48
Physical Interfaces for Aggregated Ethernet Interfaces on page 51
Link Speed for Aggregated Ethernet Interfaces on page 52
MinimumLinks for Aggregated Ethernet Interfaces on page 54
Removal of Aggregated Ethernet Interfaces on page 55
Understanding VLAN Tagging for Aggregated Ethernet Interfaces on page 57
Understanding Promiscuous Mode for Aggregated Ethernet Interfaces on page 57
Verifying Aggregated Ethernet Interfaces on page 57
Understanding Aggregated Ethernet Interfaces
Link aggregationof Ethernet interfaces is definedintheIEEE802.3adstandard. TheJunos
OS implementation of 802.3ad balances traffic across the member links within an
aggregated Ethernet bundle based on Layer 3 information carried in the packet, Layer 4
information carried in the packet, or both, or based on session ID data. (The session ID
datahas higher precedence thanthe Layer 3or 4information.) This implementationuses
the same load-balancing algorithmused for per-packet load balancing.
Aggregated Ethernet interfaces can be Layer 3 interfaces (VLAN-tagged or untagged)
and Layer 2 interfaces.
NOTE: This topic is specific to the SRX3000and SRX5000line devices. For
information about link aggregation for other SRX Series devices and J Series
devices, see the Junos OS Layer 2 Bridging and Switching Configuration Guide
for Security Devices.
LAGs on page 46
LACP on page 46
LAGs
You can combine multiple physical Ethernet ports to forma logical point-to-point link,
known as a link aggregation group (LAG) or bundle, such that a media access control
(MAC) client can treat the LAGas if it were a single link. Support for LAGs based on IEEE
802.3ad makes it possible to aggregate physical interface links on your device. LAGs
provide increased interface bandwidth and link availability by linking physical ports and
load-balancing traffic crossing the combined interface. For the LAGto operate correctly,
it is necessary to coordinate the two end systems connected by the LAG, either manually
or automatically.
Internally, a LAGis a virtual interface presented on SRX3000 and SRX5000 line devices
or onany system(consistingof devices suchas routers andswitches) supporting802.3ad
link aggregation. Externally, a LAG corresponds to a bundle of physical Ethernet links
connected between an SRX3000 or SRX5000 line device and another systemcapable
of link aggregation. This bundle of physical links is a virtual link.
Followtheseguidelines for aggregatedEthernet support for theSRX3000andSRX5000
lines:
Thedevicessupport amaximumof 16physical interfacesper singleaggregatedEthernet
bundle.
Aggregated Ethernet interfaces can use interfaces fromthe same or different Flexible
PIC Concentrators (FPCs) and PICs.
On the aggregated bundle, capabilities such as MAC accounting, VLAN rewrites, and
VLAN queuing are available.
LACP
Junos OS supports the Link Aggregation Control Protocol (LACP), which is a
subcomponent of IEEE 802.3ad. LACP provides additional functionality for LAGs, but is
only supported on Layer 3.
LACPprovidesastandardizedmeansfor exchanginginformationbetweenpartner (remote
or far-end of the link) systems on a link. This exchange allows their link aggregation
control instances toreachagreement ontheidentity of theLAGtowhichthelink belongs,
and then to move the link to that LAG. This exchange also enables the transmission and
reception processes for the link to function in an orderly manner.
For example, when LACP is not enabled, a local LAG might attempt to transmit packets
to a remote individual interface, which causes the communication to fail. (An individual
interface is a nonaggregatable interface.) When LACP is enabled, a local LAG cannot
transmit packets unless a LAG with LACP is also configured on the remote end of the
link.
You configure an aggregated Ethernet virtual link by specifying the link number as a
physical device. Then you associate a set of ports that have the same speed and are in
full-duplex mode. The physical ports can be 100-megabit Ethernet, 1-Gigabit Ethernet,
and 10-Gigabit Ethernet.
When configuring LACP, followthese guidelines:
LACP does not support automatic configuration on SRX3000 and SRX5000 line
devices, but partner systems are allowed to performautomatic configuration. When
anSRX3000or SRX5000linedeviceis connectedtoafully802.3ad-compliant partner
system, static configuration of LAGs is initiated on the SRX3000 and SRX5000 line
device side, and static configuration is not needed on the partner side.
When an SRX3000 or SRX5000 line device is connected to a Juniper Networks MX
Series router, staticconfigurationof LAGs is neededat boththeactor (local or near-end
of the link) and partner systems.
Although the LACP functions on the SRX3000 and SRX5000 line devices are similar
totheLACPfeaturesonJuniper Networks MXSeriesrouters, thefollowingLACPfeatures
on MX Series routers are not supported on SRX3000 and SRX5000 line devices: link
protection, systempriority, andport priority for aggregatedEthernet interfaces. Instead,
SRX3000 and SRX5000 line devices provide active/standby support with redundant
Ethernet interface LAGs in chassis cluster deployments.
LACP is supported in standalone deployments, where aggregated Ethernet interfaces
aresupported, andinchassis cluster deployments, whereaggregatedEthernet interfaces
and redundant Ethernet interfaces are supported simultaneously.
Related
Documentation
Understanding LACP on Standalone Devices on page 59
Understanding LACP on Chassis Clusters on page 64
Understanding VLAN Tagging for Aggregated Ethernet Interfaces on page 57
Aggregated Ethernet Interfaces Configuration Overview
NOTE: This topic is specific to the SRX3000and SRX5000line devices. For
information about link aggregation for other SRX Series devices and J Series
devices, see the Junos OS Layer 2 Bridging and Switching Configuration Guide
for Security Devices.
Chapter 3: Aggregated Ethernet Interfaces
To configure an aggregated Ethernet interface:
1. Set the number of aggregated Ethernet interfaces on the device. See Example:
Configuring the Number of Aggregated Ethernet Interfaces on a Device on page 49.
2. Associate a physical interface with the aggregated Ethernet interface. See Example:
Associating Physical Interfaces with Aggregated Ethernet Interfaces on page 51.
3. (Optional) Set the required link speed for all the interfaces included in the bundle.
See Example: Configuring Aggregated Ethernet Link Speed on page 53.
4. (Optional) Configure the minimumnumber of links that must be up for the bundle as
awholetobelabeledas up. SeeExample: ConfiguringAggregatedEthernet Minimum
Links on page 54.
5. (Optional) Enable or disable VLAN tagging. See Understanding VLAN Tagging for
Aggregated Ethernet Interfaces on page 57.
6. (Optional) Enable promiscuous mode. See Understanding Promiscuous Mode for
Aggregated Ethernet Interfaces on page 57.
Related
Documentation
Example: Configuring LACP on Standalone Devices on page 60
Example: Configuring LACP on Chassis Clusters on page 66
Device Count for Aggregated Ethernet Interfaces
Understanding the Aggregated Ethernet Interfaces Device Count on page 48
Example: Configuring the Number of Aggregated Ethernet Interfaces on a
Device on page 49
Example: Deleting Aggregated Ethernet Interfaces on page 50
Understanding the Aggregated Ethernet Interfaces Device Count
By default, no aggregated Ethernet interfaces are created. You must set the number of
aggregated Ethernet interfaces on the routing device before you can configure them.
Once you set the device count, the systemcreates that number of empty aggregated
Ethernet interfaces. A globally unique MAC address is assigned to every aggregated
Ethernet interface. More aggregated Ethernet interfaces can be created by increasing
the parameter.
The maximumnumber of aggregated devices you can configure is 128. The aggregated
interfaces are numbered fromae0 through ae127.
Similarly, you can permanently remove an aggregatedEthernet interface fromthe device
configuration by deleting it fromthe device count. When you reduce the device count,
only the aggregated Ethernet interface objects at the end of the list are removed, leaving
the newly specified number of interfaces. That is, if you set the device count to 10 and
then reduce it to 6, the systemremoves the last 4 interface objects fromthe list.
WARNING: Be aware that this approach deletes the aggregated Ethernet
interface and all of its objects fromthe device configuration.
Related
Documentation
Example: Configuring the Number of Aggregated Ethernet Interfaces on a Device on
page 49
Example: Configuring the Number of Aggregated Ethernet Interfaces on a Device
This example shows howto configure the number of aggregated Ethernet interfaces on
a device.
Overviewon page 49
Requirements
interface.
Overview
In this example, you create two aggregate Ethernet interfaces, thereby enabling all the
interfaces that you need for your configuration in one step.
Configuration
Step-by-Step
Procedure
To configure the number of aggregated Ethernet interfaces on a device:
Set the number of aggregated Ethernet interfaces. 1.
[edit]
user@host# set chassis aggregated-devices ethernet device-count 2
[edit]
user@host# commit
Verification
To verify the configuration is working properly, enter the showchassis aggregated-devices
command.
Related
Documentation
Understanding the Aggregated Ethernet Interfaces Device Count on page 48
Example: Deleting Aggregated Ethernet Interfaces
This exampleshows howtodeleteaggregatedEthernet interfaces usingthedevicecount.
Overviewon page 50
Requirements
Before you begin, set the number of aggregated Ethernet interfaces on the device. See
page 49
Overview
This example shows howto clean up unused aggregated Ethernet interfaces. In this
example, you reduce the number of interfaces from10 to 6, thereby removing the last 4
interfaces fromthe interface object list.
Configuration
Step-by-Step
Procedure
To delete an interface:
Set the number of aggregated Ethernet interfaces. 1.
[edit]
user@host# delete chassis aggregated-devices ethernet device-count 6
[edit]
user@host# commit
Verification
To verify the configuration is working properly, enter the showchassis aggregated-devices
command.
Related
Documentation
Example: Deleting Aggregated Ethernet Interface Contents on page 55
Physical Interfaces for Aggregated Ethernet Interfaces
Understanding Physical Interfaces for Aggregated Ethernet Interfaces on page 51
Example: Associating Physical Interfaces with Aggregated Ethernet
Interfaces on page 51
Understanding Physical Interfaces for Aggregated Ethernet Interfaces
You associate a physical interface with an aggregated Ethernet interface. Doing so
associates the physical child links with the logical aggregated parent interface to form
a link aggregation group (LAG). You must also specify the constituent physical links by
including the 802.3ad configuration statement.
A physical interface can be added to any aggregated Ethernet interface as long as all
member links have the same link speedandthe maximumnumber of member links does
not exceed 16. The aggregated Ethernet interface instance number aex can be from0
through 127, for a total of 128 aggregated interfaces.
NOTE: If you specify (on purpose or accidentally) that a link already
associatedwithanaggregatedEthernet interfacebeassociatedwithanother
aggregatedEthernet interface, thelinkis removedfromtheprevious interface
(there is no need for you to explicitly delete it) and it is added to the other
one.
Related
Documentation
Example: Associating Physical Interfaces with Aggregated Ethernet Interfaces on
page 51
Example: Associating Physical Interfaces with Aggregated Ethernet Interfaces
This example shows howto associate physical interfaces with aggregated Ethernet
interfaces.
Overviewon page 51
Requirements
Before you begin, set the number of aggregated Ethernet interfaces on the device. See
page 49
Overview
Inthis example, youassociatethephysical childlinkof thege-1/0/0andge-2/0/0physical
interfaces with the logical aggregate parent, ae0, thereby creating a LAG. Similarly, you
create a LAG that associate the ge-3/0/0, ge-3/0/1, and ge-4/0/1 physical interfaces
with the ae1 aggregated Ethernet interface.
Configuration
Step-by-Step
Procedure
To associate physical interfaces with aggregated Ethernet interfaces:
Create the first LAG. 1.
[edit]
user@host# set interfaces ge-1/0/0gigether-options 802.3ad ae0
2. Create the second LAG.
[edit]
user@host# set interfaces ge-3/0/1 gigether-options 802.3ad ae1
user@host# sset interfaces ge-4/0/0gigether-options 802.3ad ae1
[edit]
user@host# commit
Verification
Related
Documentation
Understanding Physical Interfaces for Aggregated Ethernet Interfaces on page 51
Link Speed for Aggregated Ethernet Interfaces
Understanding Aggregated Ethernet Interface Link Speed on page 52
Example: Configuring Aggregated Ethernet Link Speed on page 53
Understanding Aggregated Ethernet Interface Link Speed
On aggregated Ethernet interfaces, you can set the required link speed for all interfaces
included in the bundle. All interfaces that make up a bundle must be the same speed. If
you include in the aggregated Ethernet interface an individual link that has a speed
different fromthe speed you specify in the link-speed parameter, an error message will
be logged.
The speed value is specified in bits per second either as a complete decimal number or
as a decimal number followed by the abbreviation k (1000), m(1,000,000), or g
(1,000,000,000).
Aggregated Ethernet interfaces on SRX3000 and SRX5000 line devices can have one
of the following speed values:
100mLinks are 100 Mbps.
10gLinks are 10 Gbps.
1gLinks are 1 Gbps.
Related
Documentation
Example: Configuring Aggregated Ethernet Link Speed on page 53
Understanding MinimumLinks for Aggregated Ethernet Interfaces on page 54
Example: Configuring Aggregated Ethernet Link Speed
This example shows howto configure the aggregated Ethernet link speed.
Overviewon page 53
Requirements
Before you begin:
1. Add the aggregated Ethernet interfaces using the device count. See Example:
2. Associate physical interfaces with the aggregated Ethernet Interfaces. See Example:
Overview
In this example, you set the required link speed for all interfaces included in the bundle
to 10 Gbps. All interfaces that make up a bundle must be the same speed.
Configuration
Step-by-Step
Procedure
To configure the aggregated Ethernet link speed:
Set the link speed. 1.
[edit]
user@host# set interfaces ae0aggregated-ether-options link-speed 10g
[edit]
user@host# commit
Verification
Related
Documentation
MinimumLinks for Aggregated Ethernet Interfaces
Understanding MinimumLinks for Aggregated Ethernet Interfaces on page 54
Example: Configuring Aggregated Ethernet MinimumLinks on page 54
Understanding MinimumLinks for Aggregated Ethernet Interfaces
On aggregated Ethernet interfaces, you can configure the minimumnumber of links that
must be up for the bundle as a whole to be labeled as up. By default, only one link must
be up for the bundle to be labeled as up.
On SRX3000 and SRX5000 line devices, the valid range for the minimumlinks number
is 1 through 16. When the maximumvalue (16) is specified, all configuredlinks of a bundle
must be up for the bundle to be labeled as up.
If the number of links configured in an aggregated Ethernet interface is less than the
minimum-linksvalueconfiguredintheminimum-linksstatement, theconfigurationcommit
fails and an error message is displayed.
Related
Documentation
Example: Configuring Aggregated Ethernet MinimumLinks on page 54
Example: Configuring Aggregated Ethernet MinimumLinks
This example shows howto configure the minimumnumber of links on an aggregated
Ethernet interface that must be up for the bundle as a whole to be labeled as up.
Overviewon page 55
Requirements
Before you begin:
3. Configure the aggregated Ethernet link speed. See Example: Configuring Aggregated
Ethernet Link Speed on page 53.
Overview
In this example, you specify that on interface ae0 at least eight links must be up for the
bundle as a whole to be labeled as up.
Configuration
Step-by-Step
Procedure
To configure the minimumnumber of links on an aggregated Ethernet interface:
Set the minimumnumber of links. 1.
[edit]
user@host# set interfaces ae0aggregated-ether-options minimum-links 8
[edit]
user@host# commit
Verification
Related
Documentation
Removal of Aggregated Ethernet Interfaces
Understanding Aggregated Ethernet Interface Removal on page 55
Understanding Aggregated Ethernet Interface Removal
You can delete an aggregated Ethernet interface fromthe interface configuration. The
Junos OS removes the configuration statements related to aex and sets this interface to
the down state. The deleted aggregated Ethernet interface still exists, but it becomes
an empty interface.
Related
Documentation
Example: Deleting Aggregated Ethernet Interface Contents
This example shows howto delete the contents of an aggregated Ethernet interface.
Overviewon page 56
Requirements
Before you begin:
1. Set the number of aggregated Ethernet interfaces on the device. See Example:
2. Associate a physical interface with the aggregated Ethernet interface. See Example:
3. Set the required link speed for all the interfaces included in the bundle. See Example:
Configuring Aggregated Ethernet Link Speed on page 53.
4. Configure the minimumnumber of links that must be up for the bundle as a whole to
be labeled as up. See Example: Configuring Aggregated Ethernet MinimumLinks on
page 54.
Overview
In this example, you delete the contents of the ae4 aggregated Ethernet interface, which
sets it to the down state.
Configuration
Step-by-Step
Procedure
To delete the contents of an aggregated Ethernet interface:
Delete the interface. 1.
[edit]
user@host# delete interfaces ae4
[edit]
user@host# commit
Verification
Related
Documentation
Understanding VLANTagging for Aggregated Ethernet Interfaces
Aggregated Ethernet interfaces can be either VLAN-tagged or untagged, with LACP
enabled or disabled. Aggregated Ethernet interfaces on the SRX3000 and SRX5000
lines support the configuration of native-vlan-id, which consists of the following
configuration statements:
inner-tag-protocol-id
inner-vlan-id
pop-pop
pop-swap
push-push
swap-push
swap-swap
Related
Documentation
Understanding Promiscuous Mode for Aggregated Ethernet Interfaces
YoucanenablepromiscuousmodeonaggregatedEthernet interfaces. Whenpromiscuous
mode is enabled on a Layer 3 Ethernet interface, all packets received on the interface
are sent to the central point or Services Processing Unit (SPU) regardless of the
destinationMACaddressof thepacket. If youenablepromiscuousmodeonanaggregated
Ethernet interface, promiscuous mode is then enabled on all member interfaces.
Related
Documentation
Verifying Aggregated Ethernet Interfaces
Verifying Aggregated Ethernet Interfaces (terse) on page 57
Verifying Aggregated Ethernet Interfaces (extensive) on page 58
Verifying Aggregated Ethernet Interfaces (terse)
Purpose Display status information in terse (concise) format for aggregated Ethernet interfaces.
Action Fromoperational mode, enter the showinterfaces ae0terse command.
user@host> showinterfaces ae0terse
ge-2/0/0.0 up up aenet --> ae0.0
ge-2/0/0.32767 up up aenet --> ae0.32767
ge-2/0/1.0 up up aenet --> ae0.0
ge-2/0/1.32767 up up aenet --> ae0.32767
ae0 up up
ae0.0 up up bridge
ae0.32767 up up multiservice
Meaning The output shows the bundle relationship for the aggregated Ethernet interface and the
overall status of the interface, including the following information:
Thelink aggregationcontrol PDUs runonthe.0childlogical interfaces for theuntagged
aggregated Ethernet interface.
The link aggregation control PDUs run on the .32767 child logical interfaces for the
VLAN-tagged aggregated Ethernet interface.
The .32767 logical interface is created for the parent link and all child links.
Verifying Aggregated Ethernet Interfaces (extensive)
Purpose Display status information and statistics in extensive (detailed) format for aggregated
Ethernet interfaces.
Action Fromoperational mode, enter the showinterfaces ae0extensive command.
user@host> showinterfaces ae0extensive
Physical interface: ae0, Enabled, Physical link is Up
...
Logical interface ae0.0 (Index 67) (SNMP ifIndex 628) (Generation 134)
...
LACP info: Role System System Port Port Port
priority identifier priority number key
ge-5/0/0.0 Actor 127 00:1f:12:8c:af:c0 127 832 1
ge-5/0/0.0 Partner 127 00:1f:12:8f:d7:c0 127 640 1
ge-5/0/1.0 Actor 127 00:1f:12:8c:af:c0 127 833 1
ge-5/0/1.0 Partner 127 00:1f:12:8f:d7:c0 127 641 1
LACP Statistics: LACP Rx LACP Tx Unknown Rx Illegal Rx
ge-5/0/0.0 12830 7090 0 0
ge-5/0/1.0 10304 4786 0 0
...
Logical interface ae0.32767 (Index 70) (SNMP ifIndex 630) (Generation 135)
...
LACP info: Role System System Port Port Port
priority identifier priority number key
ge-5/0/0.32767 Actor 127 00:1f:12:8c:af:c0 127 832 1
ge-5/0/0.32767 Partner 127 00:1f:12:8f:d7:c0 127 640 1
ge-5/0/1.32767 Actor 127 00:1f:12:8c:af:c0 127 833 1
ge-5/0/1.32767 Partner 127 00:1f:12:8f:d7:c0 127 641 1
ge-5/0/0.32767 12830 7090 0 0
ge-5/0/1.32767 10304 4786 0 0
...
Meaning The output shows detailed aggregated Ethernet interface information. This portion of
the output shows LACP information and LACP statistics for each logical aggregated
Ethernet interface.
Related
Documentation
LACP for Standalone Devices
Verifying LACP on Standalone Devices on page 62
Understanding LACP on Standalone Devices
Link AggregationControl Protocol (LACP) provides astandardizedmeans for exchanging
information between partner systems on a link. Within LACP, the local end of a child link
is known as the actor and the remote end of the link is known as the partner.
LACPis enabledonanaggregatedEthernet interfaceby settingthemodetoeither passive
or active. However, to initiate the transmission of link aggregation control protocol data
units (PDUs) andresponse link aggregationcontrol PDUs, youmust enable LACPat both
the local and remote ends of the links, and one end must be active:
Active modeIf either the actor or partner is active, they exchange link aggregation
control PDUs. The actor sends link aggregation control PDUs to its protocol partner
that convey what the actor knows about its own state and that of the partners state.
PassivemodeIf theactor andpartner arebothinpassivemode, they donot exchange
link aggregation control PDUs. As a result, the aggregated Ethernet links do not come
up. In passive transmission mode, links send out link aggregation control PDUs only
when they receive themfromthe remote end of the same link.
By default, the actor and partner transmit link aggregation control PDUs every second.
You can configure different periodic rates on active and passive interfaces. When you
configure the active and passive interfaces at different rates, the transmitter honors the
receivers rate.
You configure the interval at which the interfaces on the remote side of the link transmit
link aggregation control PDUs by configuring the periodic statement on the interfaces on
the local side. It is the configuration on the local side that specifies the behavior of the
remote side. That is, the remote side transmits link aggregation control PDUs at the
specified interval. The interval can be fast (every second) or slow(every 30 seconds).
Related
Documentation
Example: Configuring LACP on Standalone Devices
This example shows howto configure LACP on standalone devices.
Overviewon page 60
Requirements
Before you begin:
4. Configure the aggregated Ethernet minimumlinks speed. See Example: Configuring
Aggregated Ethernet MinimumLinks on page 54.
Overview
In this example, you set LACP to passive mode for the ae0 interface. You set the LACP
mode for the ae1 interface to active and set the link aggregation control PDU transmit
interval to slow, which is every 30 seconds.
Configuration
Step-by-Step
Procedure
Mode.
To configure LACP on standalone devices:
1. Set the first LACP.
[edit interfaces]
user@host# set ae0aggregated-ether-options lacp passive
2. Set the second LACP.
[edit interfaces]
user@host# set ae1 aggregated-ether-options lacp active
user@host# set ae1 aggregated-ether-options lacp periodic slow
[edit interfaces]
user@host# commit
Verification
Verifying LACP Statistics on page 61
Verifying LACP Aggregated Ethernet Interfaces on page 61
Verifying LACP Statistics
Purpose Display LACP statistics for aggregated Ethernet interfaces.
Action Fromoperational mode, enter the showlacp statistics interfaces ae0 command.
user@host> showlacp statistics interfaces ae0
Aggregated interface: ae0
ge-2/0/0 1352 2035 0 0
ge-2/0/1 1352 2056 0 0
ge-2/2/0 1352 2045 0 0
ge-2/2/1 1352 2043 0 0
Meaning The output shows LACP statistics for each physical interface associated with the
aggregated Ethernet interface, such as the following:
The LACP received counter that increments for each normal hello
The number of LACP transmit packet errors logged
The number of unrecognized packet errors logged
The number of invalid packets received
Use the following command to clear the statistics and see only newchanges:
user@host# clear lacp statistics interfaces ae0
Related
Documentation
For a complete description of showlacp statistics interfaces output, see the Junos OS
CLI Reference.
Verifying LACP Aggregated Ethernet Interfaces

Purpose Display LACP status information for aggregated Ethernet interfaces.
Action Fromoperational mode, enter the showlacp interfaces ae0 command.
user@host> showlacp interfaces ae0
LACP state: Role Exp Def Dist Col Syn Aggr Timeout Activity
ge-2/0/0 Actor No No Yes Yes Yes Yes Fast Active
ge-2/0/0 Partner No No Yes Yes Yes Yes Fast Active
LACP protocol: Receive State Transmit State Mux State
ge-2/0/0 Current Fast periodic Collecting distributing
Meaning The output shows aggregated Ethernet interface information, including the following
information:
The LACPstateIndicates whether the link in the bundle is an actor (local or near-end
of the link) or partner (remote or far-end of the link).
The LACP modeIndicates whether both ends of the aggregated Ethernet interface
are enabled (active or passive)at least one end of the bundle must be active.
The periodic link aggregation control PDU transmit rate.
The LACP protocol stateIndicates the link is up ifit is collecting and distributing
packets.
Related
Documentation
For a complete description of showlacp interfaces output, see the Junos OS CLI
Reference.
Related
Documentation
Verifying LACP on Redundant Ethernet Interfaces on page 68
Verifying LACP on Standalone Devices
Verifying LACP Statistics on page 62
Verifying LACP Aggregated Ethernet Interfaces on page 63
Verifying LACP Statistics
Purpose Display LACP statistics for aggregated Ethernet interfaces.
Action Fromoperational mode, enter the showlacp statistics interfaces ae0 command.
user@host> showlacp statistics interfaces ae0
ge-2/0/0 1352 2035 0 0
ge-2/0/1 1352 2056 0 0
ge-2/2/0 1352 2045 0 0
ge-2/2/1 1352 2043 0 0
Meaning The output shows LACP statistics for each physical interface associated with the
aggregated Ethernet interface, such as the following:
The LACP received counter that increments for each normal hello
The number of LACP transmit packet errors logged
The number of unrecognized packet errors logged
The number of invalid packets received
Use the following command to clear the statistics and see only newchanges:
user@host# clear lacp statistics interfaces ae0
Verifying LACP Aggregated Ethernet Interfaces
Purpose Display LACP status information for aggregated Ethernet interfaces.
Action Fromoperational mode, enter the showlacp interfaces ae0 command.
user@host> showlacp interfaces ae0
Meaning The output shows aggregated Ethernet interface information, including the following
information:
The LACP protocol stateIndicates the link is up ifit is collecting and distributing
packets.
Related
Documentation
LACP on Chassis Clusters
Understanding LACP on Chassis Clusters
Link aggregation groups (LAGs) can be established across nodes in a chassis cluster.
A redundant Ethernet interface has active and standby links located on two nodes in a
chassis cluster. All active links are located on one node, and all standby links are on the
other node. You can configure up to eight active links and eight standby links per node.
Link aggregation allows a redundant Ethernet interface to add multiple child interfaces
fromboth nodes and thereby create a redundant Ethernet interface LAG.
Having multiple active redundant Ethernet interface links reduces the possibility of
failover. For example, when an active link is out of service, all traffic on this link is
distributed to other active redundant Ethernet interface links, instead of triggering a
redundant Ethernet active/standby failover.
Standalone LAG interfaces are supported on clustered devices but cannot be added to
redundant Ethernet interfaces. Instead, aggregated Ethernet interfaces and redundant
Ethernet interfaces coexist. (Because the functionality of a redundant Ethernet interface
relies on the Junos OS aggregated Ethernet framework, you can think of it as a special
aggregated Ethernet interface.) Likewise, any child interface of an existing LAG cannot
be added to a redundant Ethernet interface and vice versa. The maximumnumber of
total combined standalone aggregate interfaces (ae) and redundant Ethernet interfaces
(reth) per cluster is 128.
You configure LACP on a redundant Ethernet interface by setting the LACP mode for the
parent link with the lacp statement. The LACP mode can be off (the default), active, or
passive.
MinimumLinks on page 64
Sub-LAGs on page 65
Hitless Failover on page 65
PDUs on page 65
MinimumLinks
Redundant Ethernet interfaceconfigurationincludes aminimum-links settingthat allows
you to set a minimumnumber of physical child links in a redundant Ethernet interface
LAG that must be working on the primary node for the interface to be up. The default
minimum-links value is 1. When the number of physical links on the primary node in a
redundant Ethernet interface falls belowthe minimum-links value, the interface will be
down even if some links are still working.
Sub-LAGs
LACP maintains a point-to-point LAG. Any port connected to the third point is denied.
However, a redundant Ethernet interface does connect to two different systems or two
remote aggregated Ethernet interfaces by design. To support LACP on both redundant
Ethernet interface active and standby links, a redundant Ethernet interface can be
modeled to consist of two sub-LAGs, where all active links forman active sub-LAG and
all standby links forma standby sub-LAG. In this model, LACP selection logic is applied
and limited to one sub-LAG at a time. In this way, two redundant Ethernet interface
sub-LAGs are maintained simultaneously while all the LACP advantages are preserved
for each sub-LAG.
It is necessary for the switches used to connect the nodes in the cluster to have a LAG
link configured and 802.3ad enabled for each LAG on both nodes so that the aggregate
links will be recognized as such and correctly pass traffic.
NOTE: The redundant Ethernet interface LAGchild links fromeach node in
the chassis cluster must be connectedto a different LAGat the peer devices.
If a single peer switch is used to terminate the redundant Ethernet interface
LAG, two separate LAGs must be used in the switch.
Hitless Failover
With LACP, it is essential for the redundant Ethernet interface to support hitless failover
between the active and standby links in normal operation. The termhitless means that
the redundant Ethernet interface state remains up during failover.
The lacpd process manages both the active and standby links of the redundant Ethernet
interfaces. A redundant Ethernet interface pseudolink is in the up condition when the
number of active up links is not less than the number of minimumlinks configured.
Therefore, to support hitless failover, the LACPstate on the redundant Ethernet interface
standby links must be collecting and distributing before failover occurs.
PDUs
By default, aggregated and redundant Ethernet links do not exchange link aggregation
control protocol data units (PDUs), which contain information about the state of the
link. You can configure Ethernet links to actively transmit link aggregation control PDUs,
or you can configure the links to passively transmit them, sending out link aggregation
control PDUs only when they receive themfromthe remote end of the same link. The
local end of a child link is known as the actor and the remote end of the link is known as
the partner. That is, the actor sends link aggregation control PDUs to its protocol partner
that convey what the actor knows about its own state and that of the partners state.
You configure the interval at which the interfaces on the remote side of the link transmit
link aggregation control PDUs by configuring the periodic statement on the interfaces on
the local side. It is the configuration on the local side that specifies the behavior of the
remote side. That is, the remote side transmits link aggregation control PDUs at the
specified interval. The interval can be fast (every second) or slow(every 30 seconds).
By default, the actor and partner transmit link aggregation control PDUs every second.
You can configure different periodic rates on active and passive interfaces. When you
configure the active and passive interfaces at different rates, the transmitter honors the
receivers rate.
Related
Documentation
Understanding Chassis Cluster Redundant Ethernet Interface Link AggregationGroups
in the Junos OS Security Configuration Guide
Example: Configuring LACP on Chassis Clusters
This example shows howto configure LACP on chassis clusters.
Overviewon page 66
Requirements
Before you begin:
4. Configure the aggregated Ethernet minimumlinks speed. See Example: Configuring
Aggregated Ethernet MinimumLinks on page 54.
5. Configure the LACP on standalone devices. See Example: Configuring LACP on
Standalone Devices on page 60.
Overview
In this example, you set LACP to passive mode for the reth0 interface. You set the LACP
mode for the reth1 interface to active and set the link aggregation control PDU transmit
interval to slow, which is every 30 seconds.
Configuration
Step-by-Step
Procedure
Mode.
To configure LACP on chassis clusters:
1. Set the first LACP.
{primary:node1} [edit interfaces]
user@host# set reth0redundant-ether-options lacp passive
2. Set the second LACP.
[edit interfaces]
user@host# set reth1 redundant-ether-options lacp active
user@host# set reth1 redundant-ether-options lacp periodic slow
[edit interfaces]
user@host# commit
Verification
To confirmthat the configuration is working properly, performthis task:
Verifying LACP on Redundant Ethernet Interfaces
Purpose Display LACP status information for redundant Ethernet interfaces.
Action Fromoperational mode, enter the showlacp interfaces reth0 command.
user@host> showlacp interfaces reth0
Aggregated interface: reth0
{primary:node1}
Meaning The output shows redundant Ethernet interface information, such as the following:
The LACP protocol stateIndicates the link is up if it is collecting and distributing
packets.
Related
Documentation
Junos OS CLI Reference
Verifying LACP on Redundant Ethernet Interfaces
Purpose Display LACP status information for redundant Ethernet interfaces.
Action Fromoperational mode, enter the showlacp interfaces reth0 command.
user@host> showlacp interfaces reth0
Aggregated interface: reth0
{primary:node1}
Meaning The output shows redundant Ethernet interface information, such as the following:
The LACP protocol stateIndicates the link is up if it is collecting and distributing
packets.
Related
Documentation
Junos OS CLI Reference.
CHAPTER 4
1-Port Gigabit Ethernet SFP Mini-PIM
Understanding the 1-Port Gigabit Ethernet SFP Mini-PIMon page 71
Example: Configuring the 1-Port Gigabit Ethernet SFP Mini-PIMInterface on page 73
Understanding the 1-Port Gigabit Ethernet SFP Mini-PIM
Small form-factor pluggables (SFPs) are hot-pluggable modular interface transceivers
for Gigabit and Fast Ethernet connections. Gigabit Ethernet SFP Mini-PIMs can be used
in copper and optical environments to provide maximumflexibility when upgrading from
an existing infrastructure to Metro Ethernet.
The 1-Port Gigabit Ethernet SFP Mini-PIMinterfaces a single Gigabit Ethernet device or
a network. It supports a variety of transceivers with data speeds of
10-Mbps/100-Mbps/1-Gbps with extended LAN or WAN connectivity.
Online insertion and removal of the transceivers is supported.
This topic includes the following sections:
Supported Features on page 71
Interface Names and Settings on page 72
Available Link Speeds and Modes on page 72
Link Settings on page 72
Supported Features
The following features are supported on the 1-Port Gigabit Ethernet SFP Mini-PIM:
10-Mbps/100-Mbps/1-Gbps link speed
Half-duplex/full-duplex support
Autonegotiation
Encapsulations
Maximumtransmission unit (MTU) size of 1514bytes (default) and9010bytes (jumbo
frames)
Loopback
Online insertion and removal of transceivers
Interface Names and Settings
The following format is used to represent the 1-Port Gigabit Ethernet SFP Mini-PIM
interface names:
type-fpc/pic/port
Where:
typeMedia type (ge)
fpcNumber of theFlexiblePICConcentrator (FPC) cardonwhichthephysical interface
is located
picNumber of the PIC on which the physical interface is located (0)
portSpecific port on a PIC (0)
Examples: ge-1/0/0 and ge-2/0/0
By default, the interfaces on the ports on the uplink module installed on the device are
enabled. You can also specify the MTU size for the Gigabit Ethernet interface. Junos OS
supports values from256 through 9010. The default MTU size for Gigabit Ethernet
interfaces is 1514.
Available Link Speeds and Modes
The 1-Port Gigabit Ethernet SFP Mini-PIMsupports the following link speeds:
10mSets the link speed to 10 Mbps.
1gSets the link speed to 1 Gbps.
The 1-Port Gigabit Ethernet SFP Mini-PIMsupports the following link modes:
Full-duplexAllows bidirectional communication at a given point in time.
Half-duplexAllows single directional communication at a given point in time.
Link Settings
The 1-Port Gigabit Ethernet SFP Mini-PIMincludes the following link settings:
auto-negotiationEnables autonegotation of link mode and speed.
NOTE: By default autonegotiation is enabled. To disable autonegotiation
use: set gigether-options no-autonegotiation
We recommend enabling autonegotiation.
loopbackEnables loopback.
no-auto-negotiationDisables autonegotation of link mode and speed.
no-loopbackDisables loopback.
By default a link speed of 1 Gbps in full-duplex mode is supported.
NOTE: 1-Port Gigabit Ethernet SFP mini-PIMdoes not support family
ehternet-switching.
Related
Documentation
Example: Configuring the 1-Port Gigabit Ethernet SFP Mini-PIMInterface on page 73
Example: Configuring the 1-Port Gigabit Ethernet SFP Mini-PIMInterface
This example shows howto performbasic configuration for the 1-Port Gigabit Ethernet
SFP Mini-PIM.
Overviewon page 73
Requirements
Before you begin:
1. Establish basic connectivity. See the Getting Started Guide for your device.
2. Configure network interfaces as necessary. See Example: Creating an Ethernet
Overview
In this example, you configure the ge-2/0/0 interface, set the operating speed to 100
Mbps, and define a logical interface that you can connect to the 1-Port Gigabit Ethernet
SFPMini-PIM. Youalsoset theMTUvalueto9010andset thelink optiontono-loopback.
Configuration
CLI Quick
Configuration
Toquicklyconfigurea1-Port Gigabit Ethernet SFPMini-PIM, copythefollowingcommands
and paste theminto the CLI.
[edit]
set interfaces ge-2/0/0link-mode full-duplex speed 100m
set interface ge-2/0/0gigether-options no-loopback
Chapter 4: 1-Port Gigabit Ethernet SFP Mini-PIM
J-Web Quick
Configuration
ConfiguringPhysical PropertiesTo quickly configure the physical properties of a 1-Port
Gigabit Ethernet SFP Mini-PIMusing J-Web, use the following steps:
1. Select Configure > Interfaces.
2. Under Interface, select ge-2/0/0 and then click Edit. A pop-up windowappears.
3. In the Description box, type the description for the SFP Mini-PIM.
4. In the MTU box, type 9010.
5. Fromthe Speed list, select 100Mbps.
6. Fromthe Link-mode list, select Full-duplex.
7. Select the Enable Auto-negotiation checkbox.
8. Select the Enable Per Unit Scheduler checkbox.
9. Click OK.
Disabling the InterfaceTo disable the 1Port Gigabit Ethernet SFP Mini-PIMusing
J-Web,
1. Select Configure > Interfaces .
2. Under Interface, select ge-2/0/0 and then click Disable.
Configuring Logical PropertiesTo quickly configure the physical properties of a 1-Port
Gigabit Ethernet SFP Mini-PIMusing J-Web, use the following steps:
2. Under Interface, select ge-2/0/0.0, and then click Add Logical Interface. A pop-up
windowappears.
3. In the Unit box, type 0.
4. In the Description box, type a description for the SFP Mini-PIM.
5. Fromthe Zone list, select untrust.
6. To edit the family protocol type to the Mini-PIMinterfaces, select the IPv4 tab, and
then select Enable address configuration.
7. Click Add, and then type IPv4 address.
8. Click OK.
EditingLogical PropertiesToquickly configurethephysical properties of a1-Port Gigabit
Ethernet SFP Mini-PIMusing J-Web:
1. Under Interface, select the logical interface added to the 1-Port Gigabit Ethernet SFP
Mini-PIMand then click Edit. A pop-up windowappears.
2. Under Interface, select ge-2/0/0.0, and then click Edit Logical Interface. A pop-up
windowappears.
3. Fromthe Zone list, select trust.
4. To enable DHCP client on the interface, select the IPv4 tab and then select Enable
DHCP.
5. Click OK.
NOTE: You cannot add or edit Description and Unit for a logical interface.
Deleting the Logical InterfaceTo delete the logical interface of 1Port Gigabit Ethernet
SFP Mini-PIMusing J-Web,
2. Under Interface, select ge-2/0/0.0, and then click Delete.
Step-by-Step
Procedure
Configuring the 1Port Gigabit Ethernet SFP Mini-PIMUsing the CLI Configuration
Editor
Mode.
To performbasic configuration for the 1-Port Gigabit Ethernet SFP Mini-PIM:
1. Configure the interface.
[edit]
2. Set the operating link-mode full-duplex speed of 100 Mbps for the SFP Mini-PIM.
user@host# set link-mode full-duplex speed 100m
3. Assign the MTU value.
user@host# set mtu 9010
4. Add the logical interface.
user@host# set unit 0family inet address 14.1.1.1/24
5. Set the link options.
user@host# set gigether-options no-loopback
[edit]
user@host# showinterfaces ge-2/0/0
mtu 9010;
speed 100m;
gigether-options {
no-loopback;
}
unit 0 {
family inet {
14.1.1.1/24
}
}
Verification
Verifying That the Correct Hardware Is Installed on page 76
Verifying the FPC Status on page 77
Verifying the Interface Settings on page 77
Verifying That the Correct Hardware Is Installed
Purpose Verify that the 1-Port Gigabit Ethernet SFP Mini-PIMis installed on the device.
Action Fromoperational mode, enter the showchassis hardware command.
user@host> show chassis hardware detail
Hardware inventory:
Item Version Part number Serial number Description
Chassis AG0309AA0004 SRX240b
Routing Engine REV 16 750-021792 VL3180 RE-SRX240B
da0 999 MB ST72682 Nand Flash
usb0 (addr 1) DWC OTG root hub 0 vendor 0x0000 uhub0
usb0 (addr 2) product 0x005a 90 vendor 0x0409 uhub1
usb0 (addr 3) ST72682 High Speed Mode 64218 STMicroelectronics umass0
FPC 0 FPC
PIC 0 16x GE Base PIC
FPC 1 750-023367 112009000278 FPC
PIC 0 1x T1E1 mPIM
FPC 2 REV 00 750-03273 AABC5081 FPC
PIC 0 1x GE High-Perf SFP mPIM
Xcvr 0 REV 02 740-011612 9101465 SFP-T
FPC 4 750-029145 122009000061 FPC
PIC 0 1x GE SFP mPIM
Xcvr 0 REV 01 740-011782 PBL0C3T SFP-SX
Power Supply 0
Meaning Verify that the output contains the following values:
FPC 2, PIC 01x GE High-Perf SFP mPIM
FPC 4, PIC 01x GE SFP mPIM
NOTE: In the example shown above, the output for 1-Port SFPMini-Physical
Interface Module is displayed as 1X GE SFP mPIMand the output for 1-Port
Gigabit Ethernet SFP Mini-Physical Interface Module is displayed as 1X GE
High-Perf SFP mPIM.
NOTE: The1-Port GESFPMini-PIMisinstalledinthesecondslot of thedevice
chassis; therefore the output displayed is 1x GE High-Perf SFPmPIMand the
Flexible PIC Concentrator (FPC) used here is fpc 2.
The 1-Port SFP Mini-PIMis installed in the fourth slot of the device chassis;
therefore the output displayed is 1x GE SFP mPIMand Flexible PIC
Concentrator (FPC) used here is fpc 4.
Verifying the FPC Status
Purpose Verify the FPC status.
Action Fromoperational mode, enter the showchassis fpc command.
show@host> show chassis fpc
Temp CPU Utilization (%) Memory Utilization (%)
Slot State (C) Total Interrupt DRAM (MB) Heap Buffer
0 Online -------------------- CPU less FPC --------------------
3 Empty
Meaning The output should showthe FPC status as online.
The 1-Port SFP Mini-PIMis installed in the fourth slot of the device chassis; the output
shows the FPC status for slot 4 as online.
The 1-Port Gigabit Ethernet SFP Mini-PIMis installed in the second slot of the device
chassis; the output shows the FPC status for slot 2 as online.
Verifying the Interface Settings
Purpose Verify that the interface is configured as expected.
Action Fromoperational mode, enter the showinterface ge-2/0/0 command.
user@host# run show interfaces ge-2/0/0
Physical interface: ge-2/0/0, Enabled, Physical link is Up
Interface index: 156, SNMP ifIndex: 552
Link-level type: Ethernet, MTU: 9010, Link-mode: Full-duplex, Speed: 100mbps,
BPDU Error: None, MAC-REWRITE Error: None,
Loopback: Disabled, Source filtering: Disabled, Flow control: Enabled,
Auto-negotiation: Enabled, Remote fault: Online
Interface flags: SNMP-Traps Internal: 0x0
Link flags : None
CoS queues : 8 supported, 8 maximum usable queues
Current address: 00:22:83:99:ac:f2, Hardware address: 00:22:83:99:ac:f2
Last flapped : 2010-08-17 12:20:33 UTC (00:00:20 ago)
Input rate : 0 bps (0 pps)
Output rate : 0 bps (0 pps)
Logical interface ge-2/0/0.0 (Index 88) (SNMP ifIndex 557)
Flags: SNMP-Traps Encapsulation: ENET2
Input packets : 108
Output packets: 1
Security: Zone: Null
Protocol inet, MTU: 8996
Flags: Sendbcast-pkt-to-re
Addresses, Flags: Is-Preferred Is-Primary
Destination: 14.1.1/24, Local: 14.1.1.1, Broadcast: 14.1.1.255
Meaning Verify the following information in the command output:
Physical interfacege-2/0/0, Enabled, Physical link is Up
MTU9010; Link-modeFull-duplex
Speed100 Mbps
LoopbackDisabled
Related
Documentation
Understanding the 1-Port Gigabit Ethernet SFP Mini-PIMon page 71
CHAPTER 5
2-Port 10-Gigabit Ethernet XPIM
Understanding the 2-Port 10-Gigabit Ethernet XPIMon page 79
Example: Configuring the 2-Port 10-Gigabit Ethernet XPIMInterface on page 82
Understanding the 2-Port 10-Gigabit Ethernet XPIM
The 10-Gigabit Ethernet (also known as 10GBASE-T or IEEE 802.3an) is a
telecommunication technology that offers data speeds up to 10 billion bits per second
over unshielded or shielded twisted pair cables.
The 2-Port 10-Gigabit Ethernet Physical Interface Module (XPIM) is a 2 x 10GBASE-T /
SFP+ XPIMline card. (SFP+ is a fiber optic transceiver module designed for 10-Gigabit
Ethernet and 8.5 Gbps-fiber channel systems.) The 2-Port 10-Gigabit Ethernet XPIM
provides a front-end interface connection that includes the following ports:
2 X copper ports. The copper ports support 10GBASE-T running with CAT6A or CAT7
Ethernet cable for up to 100 meters.
2 X fiber (SFP+) ports. The fiber ports support SFP+ multiple 10G modules.
The 2-Port 10-Gigabit Ethernet XPIMprovides interconnects for LANs, WANs, and
metropolitan area networks (MANs). The XPIMprovides multiple service levels (1Gigabit
Ethernet to 10-Gigabit Ethernet in increments) and a single connection option for a wide
range of customer needs and applications.
Supported Features on page 80
Interface Names and Settings on page 80
Copper and Fiber Operating Modes on page 80
Link Speeds on page 81
Link Settings on page 81
Supported Features
The following features are supported on the 2-Port 10-Gigabit Ethernet XPIM:
Multiple SFP+ 10G modules and the following SFP modules:
SFPP-10GE-SR
SFPP-10GE-LR
SFPP-10GE-ER
SFPP-10GE-LRM
Copper TWIN-AX 1Mand Copper TWIN-AX 3M
Online Insertion and Removal (OIR ) functionality
Link speeds of up to 10-Gbps
Full-duplex and half-duplex modes
Flowcontrol
Autonegotiation and autosensing
Quality of service (QoS)
Interface Names and Settings
The following format is used to represent the 2-Port 10-Gigabit Ethernet XPIMinterface
names:
type-fpc/pic/port
Where:
type Media type (xe)
fpc Number of the Flexible PIC Concentrator (FPC) card on which the physical
interface is located
pic Number of the PIC on which the physical interface is located (0)
port Specific port on a PIC (0 or 1)
Example: xe-6/0/0 or xe-2/0/0
By default, the interfaces on the ports on the uplink module installed on the device are
enabled. You can also specify the maximumtransmission unit (MTU) size for the Gigabit
Ethernet interface. Junos OS supports values from256 through 9216. The default MTU
for Gigabit Ethernet interfaces is 1514.
Copper and Fiber Operating Modes
On the 2-Port 10-Gigabit Ethernet XPIM, one copper port and one fiber port is grouped
together as port 0, and another copper port and fiber port are grouped as port 1. Only
two ports can be active at the same time (one port fromport 0 and another port from
port 1).
The 2-Port 10-Gigabit Ethernet XPIMcan be configured to operate in two copper mode,
twofiber mode, or mixedmode (one copper andone fiber). Inmixedmode, the twoports
should be fromdifferent port groups (one port fromport 1 and the other fromport 2).
Link Speeds
The 2-Port 10-Gigabit Ethernet XPIMports support the following link speeds for copper
and fiber:
Copper10/100/1000 Mbps or 10Gbps (full-duplex). Half duplex is only for 10/100
Mbps.
Fiber1000 Mbps or 10 Gbps (full-duplex)
To set the link speeds, use the following options:
Link Settings
The 2-Port 10-Gigabit Ethernet XPIMincludes the following link settings:
802.3adSpecifies an aggregated Ethernet bundle.
auto-negotiationEnables autonegotiation of flowcontrol, link mode, and speed.
loopbackEnables loopback.
no-auto-negotiationDisables autonegotiation of flowcontrol, link mode, and speed.
no-loopbackDisables loopback.
By default, flowcontrol is enabled on all ports, a link speed of 10 Gbps in full duplex is
supported, autonegotiationis disabledonthefiber ports, andauto-negotiationis enabled
on copper ports.
NOTE: Auto-negotiationisnot supportedwhenthe2-Port 10-Gigabit Ethernet
XPIMis operating in fiber mode at a link speed of 10 Gbps.
Related
Documentation
Example: Configuring the 2-Port 10-Gigabit Ethernet XPIMInterface on page 82
Chapter 5: 2-Port 10-Gigabit Ethernet XPIM
Example: Configuring the 2-Port 10-Gigabit Ethernet XPIMInterface
This example shows howto performbasic configuration for the 1-Port Gigabit Ethernet
SFP Mini-PIM.
Overviewon page 82
Requirements
Before you begin:
1. Establish basic connectivity. See the Getting Started Guide for your device.
2. Configure network interfaces as necessary. See Example: Creating an Ethernet
Overview
In this example, you configure the xe-6/0/0 interface, set the operating mode to copper
mode, set the operating speed to 10 Gbps, and define a logical interface that you can
connect to the 2-Port 10-Gigabit Ethernet XPIM. Additionally, you set the MTU value to
1514, set the link option to no loopback, and enable the interface.
Configuration
CLI Quick
Configuration
To quickly configure a 2-Port 10-Gigabit Ethernet XPIM, copy the following commands
and paste theminto the CLI.
[edit]
set interfaces xe-6/0/0media-type copper speed 10g unit 0family inet mtu 1514
set interface xe-6/0/0gigether-options no-loopback
Step-by-Step
Procedure
Mode.
To performbasic configuration for the 2-Port 10-Gigabit Ethernet XPIM:
[edit]
user@host# edit interfaces xe-6/0/0
2. Configure the operating mode.
[edit interfaces xe-6/0/0]
user@host# set media-type copper
3. Set the operating speed for the XPIM.
user@host# set speed 10g
4. Add the logical interface.
user@host# set unit 0family inet
5. Assign the MTU value.
user@host# set unit 0family inet mtu 1514
6. Set the link options.
user@host# set gigether-options no-loopback
7. Enable the interface.
user@host# set enable
xe-6/0/0 command. If the output does not display the intended configuration, repeat
[edit]
user@host# showinterfaces xe-6/0/0
speed 10g;
media-type copper;
gigether-options {
no-loopback;
}
unit 0 {
family inet {
mtu 1514;
}
}
Verification
Verifying That the Correct Hardware Is Installed on page 83
Verifying the FPC Status on page 84
Verifying the Interface Settings on page 84
Verifying That the Correct Hardware Is Installed
Purpose Verify that the 2-Port 10-Gigabit Ethernet XPIMis installed on the device.
Action Fromoperational mode, enter the showchassis hardware command.
Hardware inventory:
Item Version Part number Serial number Description
Chassis AJ0309AC0047 SRX650
Midplane REV 04 710-023875 TV3993
System IO REV 04 710-023209 TV4035 SRXSME System IO
Routing Engine REV 01 710-023224 DT5109 RE-SRXSME-SRE6
FPC 0 FPC
PIC 0 4x GE Base PIC
FPC 2 FPC
PIC 0 2x 10G gPIM
FPC 6 FPC
PIC 0 2x 10G gPIM
Power Supply 0 REV 01 740-024283 TA00049WSSSS PS 645W AC
Meaning Verify that the output contains the following values:
FPC 2 , PIC 02x 10G gPIM
FPC 6, PIC 02x 10G gPIM
Verifying the FPC Status
Purpose Verify the FPC status.
Action Fromoperational mode, enter the showchassis fpc command.
Temp CPU Utilization (%) Memory Utilization (%)
1 Empty
3 Empty
4 Empty
5 Empty
7 Empty
8 Empty
Meaning The output should display FPC status as online.
NOTE: The 2-Port 10-Gigabit Ethernet XPIMis installed in the second and
sixth slot of the SRX650 device chassis; therefore the FPC used here is fpc
2 and fpc 6.
Verifying the Interface Settings
Purpose Verify that the interface is configured as expected.
Action Fromoperational mode, enter the showinterface xe-6/0/0 command.
Physical interface: xe-6/0/0, Enabled, Physical link is Up
Link-level type: Ethernet, MTU: 1514, Link-mode: Full-duplex, Speed: 10Gbps,
BPDU Error: None, MAC-REWRITE Error: None, Loopback: Disabled,
Source filtering: Disabled, Flow control: Enabled
Link flags : None
Current address: 00:1f:12:e0:80:a8, Hardware address: 00:1f:12:e0:80:a8
Last flapped : 1970-01-01 00:34:22 PST (07:26:29 ago)
Logical interface xe-6/0/0.0 (Index 72) (SNMP ifIndex 503)
Input packets : 25
Output packets: 25
Security: Zone: HOST
Allowed host-inbound traffic : any-service bfd bgp dvmrp igmp ldp msdp nhrp
ospf pgm pim rip router-discovery rsvp sap vrrp
Flags: Sendbcast-pkt-to-re
Destination: 10.10.10/24, Local: 10.10.10.10, Broadcast: 10.10.10.255
Meaning Verify the following information in the command output:
Physical interfacexe-6/0/0, Enabled, Physical link is Up
MTU1514; Link-modeFull-duplex
Speed10 Gbps
LoopbackDisabled
FlowcontrolEnabled
Related
Documentation
Understanding the 2-Port 10-Gigabit Ethernet XPIMon page 79
CHAPTER 6
Power over Ethernet
Understanding Power over Ethernet on page 87
Example: Configuring PoE on All Interfaces on page 90
Example: Configuring PoE on an Individual Interface on page 92
Example: Disabling a PoE Interface on page 95
Understanding Power over Ethernet
Power over Ethernet (PoE) is the implementation of the IEEE 802.3 AF and IEEE 802.3
AT standards that allowboth data and electrical power to pass over a copper Ethernet
LAN cable.
The SRX Series devices support PoE on Ethernet ports. PoE ports transfer electrical
power and data to remote devices over standard twisted-pair cable in an Ethernet
network. PoE ports allowyou to plug in devices that require both network connectivity
and electrical power, such as VoIP and IP phones and wireless LAN access points.
You can configure the SRX Series device to act as power sourcing equipment (PSE),
supplying power to powered devices that are connected on designated ports.
SRX Series Services Gateway PoE Specifications on page 87
PoE Classes and Power Ratings on page 88
PoE Options on page 89
SRX Series Services Gateway PoE Specifications
Table 13 on page 87 lists the PoE specifications for the SRX210, SRX240 and SRX650
devices
Table13: PoESpecificationsfor theSRX210, SRX240andSRX650Devices
For SRX650 Device For SRX240 Device For SRX210 Devices Specifications
IEEE 802.3 AF
IEEE802.3AT(PoE+)
Legacy
(pre-standards)
IEEE 802.3 AF
IEEE802.3AT(PoE+)
Legacy
(pre-standards)
IEEE 802.3 AF
Legacy
(pre-standards)
Supported
standards
Table 13: PoE Specifications for the SRX210, SRX240and SRX650
Devices (continued)
For SRX650 Device For SRX240 Device For SRX210 Devices Specifications
Supported on the
following ports:
Slot 2 or 6 on 16
Gigabit Ethernet ports
ge-2/0/0to
ge-2/0/15
ge-6/0/0to
ge-6/0/15
Slot 2 or 6 on 24
ge-2/0/0to
ge-2/0/23
ge-6/0/0to
ge-6/0/23
Supported on all 16
(ge-0/0/0 to
ge-0/0/15).
Supported on two
and two Fast Ethernet
ports (ge-0/0/0,
ge-0/0/1, fe-0/0/2, and
fe-0/0/3).
Supported
ports
The 645 watts AC and
645 watts DC power
supplies support the
following capacities:
250 watts on a single
power supply, or with
redundancy usingthe
two-power-supply
option.
500 watts with the
two-power-supply
option operating as
nonredundant.
150 W 50 W Total PoE
power sourcing
capacity
15.4 W 15.4 W 15.4 W Default per port
power limit
30 W 30 W 30 W Maximumper
port power limit
Static: Power
allocated for each
interface can be
configured.
Class: Power
allocated for
interfaces is basedon
the class of powered
device connected.
Static: Power
allocated for each
interface can be
configured.
Class: Power
allocated for
device connected.
Static: Power
allocated for each
interface can be
configured.
Class: Power
allocated for
device connected.
Power
management
modes
PoE Classes and Power Ratings
A powered device is classified based on the maximumpower that it draws across all
input voltages and operational modes. When class-based power management mode is
configuredontheSRXSeriesdevices, power isallocatedtakingintoaccount themaximum
power ratings defined for the different classes of devices.
Table 14 on page 89 lists the classes and their power ratings as specified by the IEEE
standards.
Table 14: SRX Series Devices PoE Specifications
MinimumPower Levels
Output fromPoE Port Usage Class
15.4 W Default 0
4.0 W Optional 1
7.0 W Optional 2
15.4 W Optional 3
Class 4 power devices are
eligible to receive power up to
30 Waccording to IEEE
standards.
Reserved 4
PoE Options
When configuring PoE, you must enable the PoE interface in order for the port to provide
power to a connected, powered device. In addition, you can configure the following PoE
features:
Port prioritySets port priority. When it is not possible to maintain power to all
connectedports, lower priority ports are poweredoff before higher priority ports. When
anewdeviceis connectedonahigher-priority port, alower priority port will bepowered
off automatically if available power is insufficient to power on the higher priority port.
(For the ports with the same priority configuration, ports on the left are given higher
priority than the ports on the right.)
Maximumavailable wattage power available to a portSets the maximumamount
of power that can be supplied to the port. The default wattage per port is 15.4 watts.
PoE power consumption loggingAllows logging of per-port PoE power consumption.
Thetelemetries sectionmust beexplicitly specifiedtoenablelogging. If left unspecified,
telemetries is disabled by default. The default telemetry duration is 1 hour. The default
telemetry interval is 5 minutes.
PoE power management modeHas two modes:
ClassWhen a powered device is connected to a PoE port, the power allocated to
it is equal to the maximumpower for the class as defined by the IEEE standards.
Chapter 6: Power over Ethernet
StaticWhen a powered device is connected to a PoE port, the power allocated to
it is equal to the maximumpower configured for the port.
Reserve powerReserves the specified amount of power for the gateway in case of a
spike in PoE consumption. The default is 0.
Related
Documentation
Example: Configuring PoE on All Interfaces
This example shows howto configure PoE on all interfaces.
Overviewon page 90
Requirements
Before you begin, configure Ethernet interfaces. See Example: Creating an Ethernet
Overview
This example shows howto configure PoE on all interfaces on a device. In this example,
you set the power port priority to lowand the maximumpower available to a port to 15.4
watts. Then you enable the PoE power consumption logging with the default telemetries
settings, and you set the PoE management mode to static. Finally, you set the reserved
power consumption to 15 watts in case of a spike in PoE consumption.
Configuration
CLI Quick
Configuration
To quickly configure PoE on all interfaces, copy the following commands andpaste them
into the CLI:
[edit]
set poe interface all priority lowmaximum-power 15.4 telemetries
set poe management static guard-band 15
Step-by-Step
Procedure
Mode.
To configure PoE on all interfaces:
1. Enable PoE.
[edit]
user@host# edit poe interface all
2. Set the power port priority.
[edit poe interface all]
user@host# set priority low
3. Set the maximumPoE wattage available for a port.
user@host# set maximum-power 15.4
4. Enable logging of PoE power consumption.
user@host# set telemetries
5. Set the PoE management mode.
[edit]
user@host# set poe management static
6. Reserve power wattage in case of a spike in PoE consumption.
[edit]
user@host# set poe guard-band 15
Results Fromconfiguration mode, confirmyour configuration by entering the showpoe interface
all command. If the output does not display the intended configuration, repeat the
configuration instructions in this example to correct it.
[edit]
user@host# showpoe interface all
priority low;
maximum-power 15.4;
telemetries;
Verification
Verifying the Status of PoE Interfaces on page 91
Verifying the Status of PoE Interfaces
Purpose Verify that the PoE interfaces on the device are enabled and set to the desired priority
settings. (The device used here is the SRX240 Services Gateway.)
Action Fromoperational mode, enter the showpoe interface all command.
user@host> showpoe interface all
Interface Admin status Oper status Max power Priority Power consumption Class
ge-0/0/0 Enabled Searching 15.4W Low 0.0W 0
ge-0/0/1 Enabled Powered-up 15.4W High 6.6W 0
ge-0/0/2 Disabled Disabled 15.4W Low 0.0W 0
ge-0/0/3 Disabled Disabled 15.4W Low 0.0W 0
Meaning The showpoe interface all command lists PoE interfaces configured on the SRX 240
device, including information on status, priority, power consumption, and class. This
output shows that the device has four PoE interfaces of which two are enabled with
default values. One port has a device connected that is drawing power within expected
limits.
Related
Documentation
Example: Configuring PoE on an Individual Interface
This example shows howto configure PoE on an individual interface.
Overviewon page 92
Requirements
Before you begin:
1. Configure Ethernet interfaces. See Example: Creating an Ethernet Interface on
page 37.
2. Configure PoE on all interfaces. See Example: Configuring PoE on All Interfaces on
page 90.
Overview
This example shows howto configure PoE on the ge-0/0/0 interface. In this example,
you set the power port priority to high and the maximumpower available to a port to 15.4
watts. Then you enable the PoE power consumption logging with the default telemetries
settings, and you set the PoE management mode to static. Finally, you set the reserved
power to 15 watts in case of a spike in PoE consumption.
Configuration
CLI Quick
Configuration
To quickly configure PoE on an individual interface, copy the following commands and
paste theminto the CLI:
[edit]
set poe interface ge-0/0/0priority high maximum-power 15.4 telemetries
set poe management static guard-band 15
Step-by-Step
Procedure
Mode.
To configure PoE:
1. Enable PoE.
[edit]
user@host# edit poe interface ge-0/0/0
2. Set the power port priority.
[edit poe interface ge-0/0/0]
user@host# set priority high
3. Set the maximumPoE wattage available for a port.
user@host# set maximumpower 15.4
4. Enable logging of PoE power consumption.
user@host# set telemetries
5. Set the PoE management mode.
[edit]
user@host# set poe management static
6. Reserve power wattage in case of a spike in PoE consumption.
[edit]
user@host# set poe guard-band 15
Results Fromconfiguration mode, confirmyour configuration by entering the showpoe interface
[edit]
user@host# showpoe interface ge-0/0/0
priority high;
maximum-power 15.4;
telemetries;
Verification
Verifying the Status of PoE Interfaces on page 94
Verifying the Telemetry Data (History) for the Specified Interface on page 94
Verifying PoE Global Parameters on page 95
Verifying the Status of PoE Interfaces
Purpose Verify that the PoE interfaces on the device are enabled and set to the desired priority
settings. (The device used here is the SRX240 Services Gateway.)
Action Fromoperational mode, enter the showpoe interface ge-0/0/1 command.
user@host> showpoe interface ge-0/0/1
PoE interface status:
PoE interface : ge-0/0/1
Administrative status : Enabled
Operational status : Powered-up
Power limit on the interface : 15.4 W
Priority : High
Power consumed : 6.6 W
Class of power device : 0
Meaning Theshowpoeinterfacege-0/0/1 commandlists PoEinterfaces configuredontheSRX240
device, with their status, priority, power consumption, and class.
Verifying the Telemetry Data (History) for the Specified Interface
Purpose Verify the PoE interface's power consumption over a specified period.
Action Fromoperational mode, enter the showpoe telemetries interface command.
For all records:
user@host> showpoe telemetries interface ge-0/0/1 all
Sl No Timestamp Power Voltage
1 Fri Jan 04 11:41:15 2009 5.1 W 47.3 V
2 Fri Jan 04 11:40:15 2009 5.1 W 47.3 V
3 Fri Jan 04 11:39:15 2009 5.1 W 47.3 V
4 Fri Jan 04 11:38:15 2009 0.0 W 0.0 V
5 Fri Jan 04 11:37:15 2009 0.0 W 0.0 V
6 Fri Jan 04 11:36:15 2009 6.6 W 47.2 V
7 Fri Jan 04 11:35:15 2009 6.6 W 47.2 V
For a specific number of records:
user@host> showpoe telemetries interface ge-0/0/1 5
Sl No Timestamp Power Voltage
1 Fri Jan 04 11:31:15 2009 6.6 W 47.2 V
2 Fri Jan 04 11:30:15 2009 6.6 W 47.2 V
3 Fri Jan 04 11:29:15 2009 6.6 W 47.2 V
4 Fri Jan 04 11:28:15 2009 6.6 W 47.2 V
5 Fri Jan 04 11:27:15 2009 6.6 W 47.2 V
Meaning The telemetry status displays the power consumption history for the specified interface,
provided telemetry has been configured for that interface.
Verifying PoE Global Parameters
Purpose Verify global parameters such as guard band, power limit, and power consumption.
Action Fromoperational mode, enter the showpoe controller command.
user@host> showpoe controller
Controller Maximum Power Guard band Management
index power consumption
0 150.0 W 0.0 W 0 W Static
Meaning The showpoe controller command lists the global parameters configured on the SRX
Seriesdevicesuchascontroller index, maximumpower, power consumption, guardband,
and management mode along with their status.
Related
Documentation
Example: Disabling a PoE Interface
This example shows howto disable PoE on all interfaces or on a specific interface.
Overviewon page 95
Requirements
Before you begin:
Configure PoE on all interfaces. See Example: Configuring PoE on All Interfaces on
page 90.
ConfigurePoEonanindividual interface. SeeExample: ConfiguringPoEonanIndividual
Overview
In this example, you disable PoE on all interfaces and on a specific interface, which in
this case is ge-0/0/0.
Configuration
Step-by-Step
Procedure
To disable PoE on interfaces:
Disable PoE on all interfaces. 1.
[edit]
user@host# set poe interface all disable
2. Disable PoE on a specific interface.
[edit]
user@host# set poe interface ge-0/0/0disable
[edit]
user@host# commit
Verification
To verify the configuration is working properly, enter the showpoe interface command.
Related
Documentation
PART 3
DS1 and DS3 Interfaces
DS1 and DS3 Interfaces on page 99
Channelized Interfaces on page 115
CHAPTER 7
DS1 and DS3 Interfaces
DS1 Interfaces on page 99
DS3 Interfaces on page 106
DS1 Interfaces
Understanding T1 and E1 Interfaces on page 99
Example: Configuring a T1 Interface on page 102
Example: Deleting a T1 Interface on page 105
Understanding T1 and E1 Interfaces
T1 and E1 are equivalent digital data transmission formats that carry DS1 signals. T1 and
E1 lines can be interconnected for international use.
T1 Overviewon page 99
E1 Overviewon page 100
T1 and E1 Signals on page 100
Encoding on page 100
T1 and E1 Framing on page 101
T1 and E1 Loopback Signals on page 102
T1 Overview
T1 isadigital datatransmissionmediumcapableof handling24simultaneousconnections
running at a combined 1.544 Mbps. T1 combines these 24 separate connections, called
channels or time slots, onto a single link. T1 is also called DS1.
The T1 data streamis broken into frames. Each frame consists of a single framing bit and
24 8-bit channels, totaling 193 bits per T1 frame. Frames are transmitted 8,000 times
per second, at a data transmission rate of 1.544 Mbps (8,000 x 193 = 1.544 Mbps).
As each frame is received and processed, the data in each 8-bit channel is maintained
with the channel data fromprevious frames, enabling T1 traffic to be separated into
24separate flows across a single medium. For example, in the following set of 4-channel
frames (without a framing bit), the data in channel 1 consists of the first octet of each
frame, the data in channel 2 consists of the second octet of each frame, and so on:
Chan. 1 Chan. 2 Chan. 3 Chan. 4
Frame 1 [10001100][00110001][11111000][10101010]
Frame 2 [11100101][01110110][10001000][11001010]
Frame 3 [00010100][00101111][11000001][00000001]
E1 Overview
E1 is theEuropeanformat for DS1 digital transmission. E1 links aresimilar toT1 links except
that they carry signals at 2.048 Mbps. Each signal has 32 channels, and each channel
transmits at 64 Kbps. E1 links have higher bandwidth than T1 links because they use all
8 bits of a channel. T1 links use 1 bit in each channel for overhead.
T1 and E1 Signals
T1 and E1 interfaces consist of two pairs of wiresa transmit data pair and a receive data
pair. Clocksignals, whichdeterminewhenthetransmitteddatais sampled, areembedded
in the T1 and E1 transmissions.
Typical digital signals operate by sending either zeros (0s) or ones (1s), which are usually
represented by the absence or presence of a voltage on the line. The receiving device
need only detect the presence of the voltage on the line at the particular sampling edge
to determine whether the signal is 0or 1. T1 and E1, however, use bipolar electrical pulses.
Signals are represented by no voltage (0), positive voltage (1), or negative voltage (1).
The bipolar signal allows T1 and E1 receivers to detect error conditions in the line,
depending on the type of encoding that is being used.
Encoding
The following are common T1 and E1 encoding techniques:
Alternate mark inversion (AMI)T1 and E1
Bipolar with 8-zero substitution (B8ZS)T1 only
High-density bipolar 3 code (HDB3)E1 only
AMI Encoding
AMI encoding forces the 1s signals on a T1 or E1 line to alternate between positive and
negativevoltages for eachsuccessive1 transmission, as inthis sampledatatransmission:
1 1 0 1 0 1 0 1
+ - 0 + 0 - 0 +
When AMI encoding is used, a data transmission with a long sequence of 0s has no
voltage transitions on the line. In this situation, devices have difficulty maintaining clock
synchronization, because they rely on the voltage fluctuations to constantly synchronize
with the transmitting clock. To counter this effect, the number of consecutive 0s in a
datastreamis restrictedto15. This restrictionis calledthe1s density requirement, because
it requires a certain number of 1s for every 15 0s that are transmitted.
On an AMI-encoded line, two consecutive pulses of the same polarityeither positive or
negativeare called a bipolar violation (BPV), which is generally flagged as an error.
B8ZS and HDB3 Encoding
Neither B8ZS nor HDB3 encoding restricts the number of 0s that can be transmitted on
aline. Instead, theseencodingmethodsdetect sequencesof 0sandsubstitutebit patterns
for the sequences to provide the signal oscillations required to maintain timing on the
link.
The B8ZS encoding method for T1 lines detects sequences of eight consecutive 0
transmissions and substitutes a pattern of two consecutive BPVs (11110000). Because
the receiving end uses the same encoding, it detects the BPVs as 0s substitutions, and
no BPV error is flagged. A single BPV, which does not match the 11110000 substitution
bit sequence is likely to generate an error, depending on the configuration of the device.
The HDB3 encoding method for E1 lines detects sequences of four consecutive 0
transmissions andsubstitutes asingleBPV(1100). Similar toB8ZSencoding, thereceiving
device detects the 0s substitutions and does not generate a BPV error.
T1 and E1 Framing
J Series Services Router T1 interfaces use two types of framing: superframe (D4) and
extended superframe (ESF). E1 interfaces use G.704 framing or G.704 with no CRC4
framing, or can be in unframed mode.
Superframe (D4) Framing for T1
AD4frameconsists of 192databits: 248-bit channels andasingleframingbit. Thesingle
framing bit is part of a 12-bit framing sequence. The 193rd bit in each T1 frame is set to a
value, andevery 12consecutiveframes areexaminedtodeterminetheframingbit pattern
for the 12-bit superframe.
The following sample 12-frame sequence shows the framing pattern for D4 framing:
[data bits][framing bit]
[xxxxxxxxx][1]
[xxxxxxxxx][0]
[xxxxxxxxx][0]
[xxxxxxxxx][0]
[xxxxxxxxx][1]
[xxxxxxxxx][1]
[xxxxxxxxx][0]
[xxxxxxxxx][1]
[xxxxxxxxx][1]
[xxxxxxxxx][1]
[xxxxxxxxx][0]
[xxxxxxxxx][0]
The10001101110012-bit patternis repeatedineachsuccessivesuperframe. Thereceiving
device detects these bits tosynchronize withthe incoming datastreamandtodetermine
when the framing pattern begins and ends.
D4 framing requires the 8th bit of every byte (of every channel) within the frame to be
set to 1, a process known as bit robbing. The bit-robbing requirement ensures that the 1s
density requirements aremet, regardless of thedatacontents of theframes, but it reduces
the bandwidth on the T1 link by an eighth.
Chapter 7: DS1 and DS3 Interfaces
ESF Framing for T1
ESF extends the D4 superframe from12 frames to 24 frames. By expanding the size of
thesuperframe, ESFincreases thenumber of bits inthesuperframeframingpatternfrom
12 to 24. The extra bits are used for frame synchronization, error detection, and
maintenance communications through the facilities data link (FDL).
The ESF pattern for synchronization bits is 001011. Only the framing bits fromframes 4,
8, 12, 16, 20, and 24 in the superframe sequence are used to create the synchronization
pattern.
The framing bits fromframes 2, 6, 10, 14, 18, and 22 are used to pass a CRCcode for each
superframe block. The CRC code verifies the integrity of the received superframe and
detects bit errors with a CRC6 algorithm.
The framing bits for frames 1, 3, 5, 7, 9, 11, 13, 15, 17, 19, 21, and 23 are used for the data link
channel. These 12 bits enable the operators at the network control center to query the
remote equipment for information about the performance of the link.
T1 and E1 Loopback Signals
The control signal on a T1 or E1 link is the loopback signal. Using the loopback signal, the
operators at the network control center can force the device at the remote end of a link
to retransmit its received signals back onto the transmit path. The transmitting device
can then verify that the received signals match the transmitted signals, to perform
end-to-end checking on the link.
Two loopback signals are used to performthe end-to-end testing:
The loop-up command signal sets the link into loopback mode, with the following
command pattern:
...100001000010000100...
The loop-downsignal returns the link toits normal mode, withthe followingcommand
pattern:
...100100100100100100...
While the link is in loopback mode, the operator can insert test equipment onto the line
to test its operation.
Related
Documentation
T1 Interfaces Overviewin the Junos OS Network Interfaces Configuration Guide
E1 Interfaces Overviewin the Junos OS Network Interfaces Configuration Guide
Example: Configuring a T1 Interface
This example shows howto complete the initial configuration on a T1 interface.
Overviewon page 103
Requirements
Before you begin, install a PIM, connect the interface cables to the ports, and power on
the device. See Understanding the 2-Port 10-Gigabit Ethernet XPIM on page 79.
Overview
This example describes the initial configurationthat youmust complete oneachnetwork
interface. In this example, you configure the t1-1/0/0 interface as follows:
You create the basic configuration for the newinterface by setting the encapsulation
typetoppp. Youcanenter additional values for physical interfaceproperties as needed.
You set the logical interface to 0. Note that the logical unit number can range from0
through 16,384. You can enter additional values for properties you need to configure
on the logical interface, such as logical encapsulation or protocol family.
Configuration
CLI Quick
Configuration
To quickly configure a T1 interface, copy the following commands and paste theminto
the CLI:
[edit]
set interfaces t1-1/0/0encapsulation ppp unit 0
Step-by-Step
Procedure
Mode.
To configure a T1 interface:
1. Create the interface.
[edit]
user@host# edit interfaces t1-1/0/0
2. Create the basic configuration for the newinterface.
[edit interfaces t1-1/0/0]
user@host#set encapsulation ppp
3. Add logical interfaces.
user@host# set unit 0
command. If the output does not display the intended configuration, repeat the
For brevity, this showinterfaces command output includes only the configuration that is
relevant to this example. Any other configuration on the systemhas been replaced with
ellipses (...).
[edit]
...
t1-1/0/0 {
encapsulation ppp;
unit 0;
}
Verification
Purpose By using the ping tool on each peer address in the network, verify that all interfaces on
the device are operational.
the link state.
the round-trip time, in milliseconds, is listed in the time field. For more information about
Action Fromthe operational mode, enter the showinterfaces detail command.
following:
t1-1/0/0] level of the configuration hierarchy.
t1-1/0/0 page.
The Last Flapped time is an expected value. It indicates the last time the physical
interface became unavailable andthen available again. Unexpectedflapping indicates
likely link-layer errors.
interfaces statistics t1-1/0/0 command.
Related
Documentation
Configuring T1 Physical Interface Properties in the Junos OS Network Interfaces
Configuration Guide
Configuring E1 Physical Interface Properties in the Junos OS Network Interfaces
Configuration Guide
Example: Deleting a T1 Interface
This example shows howto delete a T1 interface.
Overviewon page 105
Requirements
interface.
Overview
In this example, you delete the t1-1/0/0 interface.
and their identifiers continue to appear on the J-Web pages.
Configuration
Step-by-Step
Procedure
To delete a T1 interface:
[edit interfaces]
user@host# delete t1-1/0/0
[edit interfaces]
user@host# commit
Verification
Related
Documentation
DS3 Interfaces
Example: Configuring a T3 Interface on page 111
Example: Deleting a T3 Interface on page 114
Understanding T3 and E3 Interfaces
T3 is a high-speed data-transmission mediumformed by multiplexing 28 DS1 signals
into seven separate DS2 signals, and combining the DS2 signals into a single DS3 signal.
T3 links operate at 43.736 Mbps. T3 is also called DS3.
E3 is the equivalent European transmission format. E3 links are similar to T3 (DS3) links,
but carry signals at 34.368 Mbps. Each signal has 16 E1 channels, and each channel
transmits at 2.048 Mbps. E3 links use all 8 bits of a channel, whereas T3 links use 1 bit in
each channel for overhead.
Multiplexing DS1 Signals on page 106
DS2 Bit Stuffing on page 107
DS3 Framing on page 107
Multiplexing DS1 Signals
Four DS1 signals combine to forma single DS2 signal. The four DS1 signals forma single
DS2 M-frame, which includes subframes M1 through M4. Each subframe has six 49-bit
blocks, for a total of 294 bits per subframe. The first bit in each block is a DS2 overhead
(OH) bit. The remaining 48 bits are DS1 information bits.
Figure 5 on page 107 shows the DS2 M-frame format.
Figure 5: DS2 M-Frame Format
The four DS2 subframes are not four DS1 channels. Instead, the DS1 data bits within the
subframes areformedby datainterleavedfromtheDS1 channels. The0
n
values designate
time slots devoted to DS1 inputs as part of the bit-by-bit interleaving process. After every
48 DS1 information bits (12 bits fromeach signal), a DS2 OH bit is inserted to indicate
the start of a subframe.
DS2 Bit Stuffing
Because the four DS1 signals are asynchronous signals, they might operate at different
line rates. To synchronize the asynchronous streams, the multiplexers on the line use bit
stuffing.
A DS2 connection requires a nominal transmit rate of 6.304 Mbps. However, because
multiplexers increase the overall output rate to the intermediate rate of 6.312 Mbps, the
output rate is higher than individual input rates on DS1 signals. The extra bandwidth is
used to stuff the incoming DS1 signals with extra bits until the output rate of each signal
equals the increased intermediate rate. These stuffed bits are inserted at fixed locations
in the DS2 M-frame. When DS2 frames are received and the signal is demultiplexed, the
stuffing bits are identified and removed.
DS3 Framing
A set of four DS1 signals is multiplexed into seven DS2 signals, which are multiplexed
into a single DS3 signal. The multiplexing occurs just as with DS1-to-DS2 multiplexing.
The resulting DS3 signal uses either the standard M13 asynchronous framing format or
the C-bit parity framing format. Although the two framing formats differ in their use of
control and message bits, the basic frame structures are identical. The DS3 frame
structures are shown in Figure 6 on page 108 and Figure 7 on page 109.
M13 Asynchronous Framing
ADS3 M-frame includes seven subframes, formed by DS2 data bits interleaved fromthe
seven multiplexed DS2 signals. Each subframe has eight 85-bit blocksa DS3 OH bit
plus 84 data bits. The meaning of an OHbit depends on the block it precedes. Standard
DS3 M13 asynchronous framing format is shown in Figure 6 on page 108.
Figure 6: DS3 M13 Frame Format
A DS3 M13 M-frame contains the following types of OH bits:
Framing bits (F-bits)Make up a frame alignment signal that synchronizes DS3
subframes. EachDS3framecontains 28F-bits (4bits per subframe). F-bits arelocated
at the beginning of blocks 2, 4, 6, and 8 of each subframe. When combined, the frame
alignment pattern for each subframe is 1001. The pattern can be examined to detect
bit errors in the transmission.
Multiframing bits (M-bits)Make up a multiframe alignment signal that synchronizes
the M-frames in a DS3 signal. Each DS3 frame contains 3 M-bits, which are located at
the beginning of subframes 5, 6, and 7. When combined, the multiframe alignment
patter for each M-frame is 010.
Bit stuffing control bits (C-bits)Serve as bit stuffing indicators for each DS2 input.
For example, C
11
, C
12
, andC
13
areindicators for DS2input 1. Their values indicatewhether
DS3 bit stuffing has occurred at the multiplexer. If the three C-bits in a subframe are
all 0s, no stuffing was performedfor the DS2 input. If the three C-bits are all 1s, stuffing
was performed.
Message bits (X-bits)Used by DS3 transmitters to embed asynchronous in-service
messages inthedatatransmission. EachDS3framecontains 2X-bits, whicharelocated
at the beginning of subframes 1 and 2. Within an DS3 M-frame, both X-bits must be
identical.
Parity bits (P-bits)Compute parity over all but 1 bit of the M-frame. (The first X-bit
is not included.) Each DS3 frame contains 2 P-bits, which are located at the beginning
of subframes 3 and 4. Both P-bits must be identical.
If the previous DS3 frame contained an odd number of 1s, both P-bits are set to 1. If the
previous DS3containedanevennumber of 1s, bothP-bits areset to0. If, onthereceiving
side, the number of 1s for a given frame does not match the P-bits in the following
frame, it indicates one or more bit errors in the transmission.
C-Bit Parity Framing
In M13 framing, every C-bit in a DS3 frame is used for bit stuffing. However, because
multiplexers first use bit stuffing when multiplexing DS1 signals into DS2 signals, the
incoming DS2 signals are already synchronized. Therefore, the bit stuffing that occurs
when DS2 signals are multiplexed is redundant.
C-bit parity framing format redefines the function of C-bits and X-bits, using themto
monitor end-to-end path performance and provide in-band data links. The C-bit parity
framing structure is shown in Figure 7 on page 109.
Figure 7: DS3 C-Bit Parity Framing
In C-bit parity framing, the X-bits transmit error conditions fromthe far end of the link to
the near end. If noerror conditions exist, bothX-bits are set to1. If anout-of-frame (OOF)
or alarmindication signal (AIS) error is detected, both X-bits are set to 0in the upstream
direction for 1 second to notify the other end of the link about the condition.
The C-bits that control bit stuffing in M13 frames are typically used in the following ways
by C-bit parity framing:
Application identification channel (AIC)The first C-bit in the first subframe identifies
the type of DS3 framing used. A value of 1 indicates that C-bit parity framing is in use.
N
a
A reserved network application bit.
Far-end alarmand control (FEAC) channelThe third C-bit in the first subframe is
used for the FEAC channel. In normal transmissions, the FEAC C-bit transmits all 1s.
Whenanalarmconditionis present, theFEACC-bit transmits acodewordintheformat
0xxxxxxx 11111111, in which x can be either 1 or 0. Bits are transmitted fromright to left.
Table 15 on page 110 lists some C-bit code words and the alarmor status condition
indicated.
Table 15: FEAC C-Bit Condition Indicators
C-Bit Code Word Alarmor Status Condition
0011001011111111 DS3 equipment failure requires immediate attention.
0001111011111111 DS3 equipment failure occurredsuch as suspended, not activated, or
unavailable servicethat is non-service-affecting.
0001110011111111 DS3 loss of signal.
0000000011111111 DS3 out of frame.
0010110011111111 DS3 alarmindication signal (AIS) received.
0011010011111111 DS3 idle received.
00011101 11111111 Common equipment failure occurred that is non-service-affecting.
0010101011111111 Multiple DS1 loss of signal.
0000101011111111 DS1 equipment failure occurred that requires immediate attention.
0000011011111111 DS1 equipment failure occurred that is non-service-affecting.
0011110011111111 Single DS1 loss of signal.
Data linksThe 12 C-bits in subframes 2, 5, 6, and 7 are data link (DL) bits for
applications and terminal-to-terminal path maintenance.
DS3 parityThe 3 C-bits in the third subframe are DS3 parity C-bits (also called
CP-bits). When a DS3 frame is transmitted, the sending device sets the CP-bits to the
same value as the P-bits. When the receiving device processes the frame, it calculates
the parity of the M-frame and compares this value to the parity in the CP-bits of the
following M-frame. If nobit errors have occurred, the twovalues are typically the same.
Farendblock errors (FEBEs)The3C-bits inthefourthsubframemakeupthefar-end
block error (FEBE) bits. If a framing or parity error is detected in an incoming M-frame
(via the CP-bits), the receiving device generates a C-bit parity error and sends an error
notification to the transmitting (far-end) device. If an error is generated, the FEBE bits
are set to 000. If no error occurred, the bits are set to 111.
Related
Documentation
T3 Interfaces Overviewin the Junos OS Network Interfaces Configuration Guide
E3 Interfaces Overviewin the Junos OS Network Interfaces Configuration Guide
Example: Configuring a T3 Interface
This example shows howto complete the initial configuration on a T3 interface.
Overviewon page 111
Requirements
Before you begin, install a PIM, connect the interface cables to the ports, and power on
the device. See the Getting Started Guide for your device.
Overview
interface. In this example, you configure the t3-1/0/0 interface as follows:
You create the basic configuration for the newinterface by setting the encapsulation
typetoppp. Youcanenter additional values for physical interfaceproperties as needed.
You set the logical interface to 0. Note that the logical unit number can range from0
to 16,384. You can enter additional values for properties you need to configure on the
logical interface, such as logical encapsulation or protocol family.
Configuration
CLI Quick
Configuration
To quickly configure a T3 interface, copy the following commands and paste theminto
the CLI:
[edit]
set interfaces t3-1/0/0encapsulation ppp unit 0
Step-by-Step
Procedure
Mode.
To configure a T3 interface:
[edit]
user@host#set encapsulation ppp
ellipses (...).
[edit]
...
t3-1/0/0 {
encapsulation ppp;
unit 0;
}
Verification
Purpose By using the ping tool on each peer address in the network, verify that all interfaces on
the device are operational.
the link state.
the round-trip time in milliseconds is listed in the time field. For more information about
Action Fromthe operational mode, enter the showinterfaces detail command.
following:
t3-1/0/0] level of the configuration hierarchy.
t3-1/0/0 page.
interfaces statistics t1-1/0/0 command.
Related
Documentation
Configuring T3 Physical Interface Properties in the Junos OS Network Interfaces
Configuration Guide
Configuring E3 Physical Interface Properties in the Junos OS Network Interfaces
Configuration Guide
Example: Deleting a T3 Interface
This example shows howto delete a T3 interface.
Overviewon page 114
Requirements
interface.
Overview
In this example, you delete the t3-1/0/0 interface.
and their identifiers continue to appear on the J-Web pages.
Configuration
Step-by-Step
Procedure
To delete a T3 interface:
[edit interfaces]
user@host# delete t3-1/0/0
[edit interfaces]
user@host# commit
Verification
Related
Documentation
CHAPTER 8
Channelized Interfaces
Understanding Channelized Interfaces on page 115
Clear Channels on page 116
Drop-and-Insert on page 124
ISDN PRI Operation on page 136
Understanding Channelized Interfaces
A channelized interface is an interface that is a subdivision of a larger interface.
Channelization minimizes the number of Physical Interface Modules (PIMs) that an
installationrequires, enablingdevices toprovide IPservices tousers withdifferent access
speeds andbandwidth requirements. Users share an interface that has been dividedinto
discrete time slots by transmitting in only their own time slots.
You can aggregate the channels on a channelized interface into bundles called channel
groups to aggregate customer traffic. A channel group is a combination of DS0 or
Integrated Services Digital Network Primary Rate Interface (ISDN PRI) B-channels
interfaces partitioned froma channelized interface into a single logical bundle.
Each port on a channelized T1/E1/ISDN PRI PIMis software configurable for a T1, E1, or
ISDN PRI service. Each channelized T1 or E1 interface can be configured as a single clear
channel or for fractional or channelized operation.
The J Series device supports these software-configurable interfaces on the following
PIMs:
Dual-Port Channelized T1 PIMA T1 interface is a physical WAN interface for
transmitting digital signals in the T-carrier systemused in the United States, Japan,
and Canada. The T1 signal format carries 24 pulse code modulation (PCM) signals
using time-division multiplexing (TDM) at an overall rate of 1.544 Mbps. Achannelized
T1 interface can be configured as a single clear-channel T1 interface or channelized
into as many as 24 discrete DS0 interfaces (channels 1 through 24), or up to 23 ISDN
PRI B-channels and1 D-channel. When the interface is configuredfor ISDNPRI service,
time slot 24 is reserved for the D-channel.
Dual-Port Channelized E1 PIMAn E1 interface is a physical WAN interface for
transmitting signals in European digital transmission (E1) format. The E1 signal format
transmits information at a rate of 2.048 Mbps and can carry 32 channels of 64 Kbps
each. AchannelizedE1 interfacecanbeconfiguredas asingleclear-channel E1 interface
or channelized into as many as 31 discrete DS0 interfaces (channels 1 through 31), or
up to 30 ISDN PRI B-channels and 1 D-channel.
Dual-Port Channelized ISDN PRI PIMA PRI is an ISDN service intended for higher
bandwidth applications than ISDN Basic Rate Interface (BRI). ISDN PRI consists of a
singleD-channel for control andsignaling, plusanumber of 64-KbpsB-channelseither
23 B-channels on a T1 line, or 30B-channels on an E1 lineto carry network traffic. The
E1 channelized interface can be partitioned into up to 23 ISDN PRI B-channels and
1 D-channel when the parent interface is channelized T1, and up to 30 ISDN PRI
B-channels and 1 Dchannel when the parent interface is channelized E1. Time slots on
the interface that are unused by ISDN PRI can operate normally as DS0 interfaces.
J Series ISDN PRI interfaces support the following switch types:
ATT5EAT&T 5ESS
ETSINET3 for the United Kingdomand Europe
NI2National ISDN-2
NTDMS100Northern TelecomDMS-100
NTTNTT Group switch for Japan
On J Series channelized interfaces, time slots are numbered from1 through 31, and time
slot 1 is reserved for framing. When the interface is configured for ISDN PRI service, time
slot 16 is reserved for the D-channel.
Channelized interfaces support class of service (CoS) configurations.
Related
Documentation
Understanding Channelized Interface Clear Channels on page 116
Understanding Channelized Interface Drop-and-Insert on page 124
Understanding ISDN PRI Operation for Channelized Interfaces on page 136
Understanding ISDN on page 141
Junos OS Class of Service Configuration Guide for Security Devices
Clear Channels
Example: Configuring a Channelized T1 Interface as a Clear Channel on page 117
Example: Configuring a Channelized E1 Interface as a Clear Channel on page 120
Verifying Clear-Channel Interfaces on page 123
Understanding Channelized Interface Clear Channels
Each port on a channelized T1/E1/ISDN PRI PIMis software configurable as a T1 or E1
clear channel. You can partition each port into up to 24 DS0 channels on a T1 interface
or up to 31 DS0 channels on an E1 interface, and can insert channels fromone port into
another with the drop-and-insert feature. Channelized T1/E1/ISDNPRI ports can also be
partitioned into channels for ISDN PRI service.
NOTE: When you configure a T1-specific or an E1-specific interface on the
SRX-GP-QUAD-T1-E1 or SRX-GP-DUAL-T1-E1, the line encoding and the
framing must be specified under the ct1-n/n/n interface, whereas the
remaining T1 or E1 specific configuration items must be configured under the
t1-n/n/n or e1-n/n/n interface, respectively. Channelized T1/E1/ISDNPRI
ports can also be partitioned into channels for ISDNPRI service.
Related
Documentation
Example: Configuring a Channelized T1 Interface as a Clear Channel
This example shows howto configure a channelized T1 interface as a clear channel.
Overviewon page 117
Requirements
No special configuration beyond device initialization is required before configuring this
feature.
Overview
In this example, you configure the ct1-3/0/0 interface as a clear channel. As part of the
configuration, you configure the following interface options:
Usethedevices systemclock(internal) insteadof asignal receivedfromtheT1 interface
(external) as the transmit clock source.
Label the physical interface (description) as clear t1 interface.
Delay the advertisement of interface transitions (hold time) fromup to and down to
500 milliseconds. Additionally, set the link hold-up time to 500 milliseconds.
Use the interface as a single clear channel (no partition).
Use subunit queuing on Frame Relay or VLAN IQinterfaces (per-unit-scheduler).
You also set E1 options:
Chapter 8: Channelized Interfaces
Set the BERT algorithmto all ones repeating.
Set the BERT error rate to 5.
Set the BERT period to 5 seconds.
Set the line buildout range, for cables to 0 through 132 feet.
Set the framing mode to ESF.
Set the line encoding method to alternate mark inversion (AMI).
Set the loopback mode to local.
Configuration
CLI Quick
Configuration
To quickly configure a channelized T1 interface as a clear channel, copy the following
[edit]
set interfaces ct1-3/0/0clocking internal
set interfaces ct1-3/0/0description cleart1interface hold-time down 500up 500
set interfaces ct1-3/0/0no-partition interface-type t1
set interfaces ct1-3/0/0per-unit-scheduler
set interfaces ct1-3/0/0t1-options bert-algorithmall-ones-repeating bert-error-rate 5
bert-period 5 buildout 0-132 framing esf line-encoding ami loopback local
set interfaces ct1-3/0/0traceoptions flag all
set interfaces ct1-3/0/0apply-groups test
Step-by-Step
Procedure
Mode.
To configure a channelized T1 interface as a clear channel:
[edit]
user@host# edit interfaces ct1-3/0/0
2. Configure interface options.
[edit interfaces ct1-3/0/0]
user@host# set clocking internal
user@host# set description cleart1 interface
user@host# set hold-time down 500up 500
user@host# set no-partition interface-type t1
user@host# set per-unit-scheduler
3. Configure T1 options.
[edit interfaces ct1-3/0/0 ]
user@host# set bert-algorithmall-ones-repeating
user@host# set bert-error-rate 5
user@host# set bert-period 5
user@host# set buildout 0132
user@host# set framing esf
user@host# set line-encoding ami
user@host# set loopback local
4. Configure trace options.
user@host# set buildout 0132
user@host# set framing esf
user@host# set line-encoding ami
user@host# set traceoptions flag all
ct1-3/0/0 command. If the output does not display the intended configuration, repeat
[edit]
user@host# showinterfaces ct1-3/0/0
apply-groups test;
description cleart1interface;
traceoptions {
flag all;
}
per-unit-scheduler;
hold-time up 500 down 500;
clocking internal;
t1-options {
loopback local;
buildout 0-132;
line-encoding ami;
framing esf;
bert-algorithmall-ones-repeating;
bert-error-rate 5;
bert-period 5;
}
no-partition interface-type t1;
Verification
Verifying Channelized Interfaces on page 119
Verifying Channelized Interfaces
Purpose Verify that your configurations for the channelized interfaces are correct.
Action Fromoperational mode, enter the showinterfaces ct1-3/0/1 command.
user@host>showinterfaces ct1-3/0/1
Physical interface: ct1-3/0/1, Enabled, Physical link is Up
Link-level type: Controller, Clocking: Internal, Speed: E1, Loopback: None,
Parent: ct1-3/0/1 Interface index 151
Framing: G704, Parent: None
Interface flags: Point-To-Point SNMP-Traps Internal: 0x4000
Link flags : None
Last flapped : 2006-10-05 21:11:48 PDT (06:45:04 ago)
DS1 alarms : None
DS1 defects : None
Line encoding: HDB3
Meaning The output shows a summary of information about the physical parent interfacea
channelized T1 interface in this example.
Related
Documentation
Example: Configuring a Channelized E1 Interface as a Clear Channel
This example shows howto configure a channelized E1 interface as a clear channel.
Overviewon page 120
Requirements
feature.
Overview
In this example, you configure the ce1-3/0/0 interface as a clear channel. As part of the
configuration, you configure the following interface options:
Usethedevices systemclock(internal) insteadof asignal receivedfromtheE1 interface
(external) as the transmit clock source.
Label the physical interface (description) as clear e1 interface.
Delay the advertisement of interface transitions (hold time) fromup to and down to
500 milliseconds. Additionally, set the link hold-up time to 500 milliseconds.
Use the interface as a single clear channel (no partition).
Use subunit queuing on Frame Relay or VLAN IQinterfaces (per-unit-scheduler).
You also set E1 options:
Set the BERT algorithmto all ones repeating.
Set the BERT error rate to 5.
Set the BERT period to 5 seconds.
Set the framing mode to G704.
Set the loopback mode to local.
Additionally, this example shows howto flag all trace option messages and howto apply
configuration settings to the test group.
Configuration
CLI Quick
Configuration
To quickly configure a channelized E1 interface as a clear channel, copy the following
[edit]
set interfaces ce1-3/0/0clocking internal
description cleart1interface hold-time down 500up 500
set interfaces ce1-3/0/0no-partition interface-type e1
set interfaces ce1-3/0/0per-unit-scheduler
set interfaces ce1-3/0/0e1-options bert-algorithmall-ones-repeating bert-error-rate 5
bert-period 5 framing g704 loopback local
set interfaces ce1-3/0/0traceoptions flag all
set interfaces ce1-3/0/0apply-groups test
Step-by-Step
Procedure
Mode.
To configure a channelized E1 interface as a clear channel:
[edit]
user@host# edit interfaces ce1-3/0/0
2. Configure interface options.
[edit interfaces ce1-3/0/0]
user@host# set clock internal
user@host# set description clear e1 interface
user@host# set hold-time down 500up 500
user@host# set no-partition interface-type e1
user@host# set per-unit-scheduler
3. Configure E1 options.
user@host# set framing g704
user@host# set traceoptions flag all
5. Configure advanced options.
user@host# set interfaces apply-groups test
ce1-3/0/0 command. If the output does not display the intended configuration, repeat
[edit]
user@host# showinterfaces ce1-3/0/0
apply-groups test;
description cleare1interface;
traceoptions {
flag all;
}
per-unit-scheduler;
clocking internal;
e1-options {
loopback local;
framing g704;
bert-algorithmall-ones-repeating;
bert-error-rate 5;
bert-period 5;
}
no-partition interface-type e1;
Verification
Verifying Clear-Channel Interfaces on page 122
Verifying Clear-Channel Interfaces
Purpose Verify that your configurations for the clear-channel interfaces are correct.
Action Fromoperational mode, enter the showinterfaces e1-3/0/1 command.
user@host> showinterfaces e1-3/0/1
Physical interface: e1-3/0/1, Enabled, Physical link is Up
Link-level type: PPP, MTU: 1504, Speed: E1, Loopback: None, FCS: 16,
Parent: ce1-3/0/1 Interface index 151
Link flags : Keepalives
Keepalive settings: Interval 10 seconds, Up-count 1, Down-count 3
Keepalive: Input: 1066 (00:00:02 ago), Output: 1066 (00:00:02 ago)
LCP state: Opened
NCP state: inet: Opened, inet6: Opened, iso: Not-configured, mpls:
Not-configured
CHAP state: Closed
DS1 alarms : None
DS1 defects : None
Logical interface e1-3/0/1.0 (Index 66) (SNMP ifIndex 238)
Flags: Point-To-Point SNMP-Traps 0x4000 Encapsulation: PPP
Bandwidth: 1984kbps
Flags: None
Destination: 47.47.47.0/30, Local: 47.47.47.2, Broadcast: 47.47.47.3
Protocol inet6, MTU: 1500
Flags: None
Destination: 8b8b:8b01::/64, Local: 8b8b:8b01::2
Addresses, Flags: Is-Preferred
Destination: fe80::/64, Local: fe80::205:85ff:fec5:d3d0
Meaning The output shows a summary of interface information. Although the parent interface is
ce1-3/0/1, the physical and logical clear-channel interfaces are named e1-3/0/1 and
e1-3/0/1.0.
Related
Documentation
showinterfaces (Channelized E1) in the Junos OS Interfaces Command Reference
Verifying Clear-Channel Interfaces
Purpose Verify that your configurations for the clear-channel interfaces are correct.
Action In operational mode, enter the showinterfaces e1-3/0/1 command.
Sample Output user@host> showinterfaces e1-3/0/1
Physical interface: e1-3/0/1, Enabled, Physical link is Up
Link-level type: PPP, MTU: 1504, Speed: E1, Loopback: None, FCS: 16,
Parent: ce1-3/0/1 Interface index 151
LCP state: Opened
NCP state: inet: Opened, inet6: Opened, iso: Not-configured, mpls:
Not-configured
CHAP state: Closed
DS1 alarms : None
DS1 defects : None
Logical interface e1-3/0/1.0 (Index 66) (SNMP ifIndex 238)
Flags: Point-To-Point SNMP-Traps 0x4000 Encapsulation: PPP
Bandwidth: 1984kbps
Flags: None
Destination: 47.47.47.0/30, Local: 47.47.47.2, Broadcast: 47.47.47.3
Protocol inet6, MTU: 1500
Flags: None
Destination: 8b8b:8b01::/64, Local: 8b8b:8b01::2
Addresses, Flags: Is-Preferred
Destination: fe80::/64, Local: fe80::205:85ff:fec5:d3d0
Meaning The output shows a summary of interface information. Although the parent interface is
ce1-3/0/1, the physical and logical clear-channel interfaces are named e1-3/0/1 and
e1-3/0/1.0.
Related
Documentation
Drop-and-Insert
Example: ConfiguringaChannelizedInterfacetoDropandInsert TimeSlots onpage125
Example: Configuring Complementary Clock Sources on Channelized
Interfaces on page 128
Understanding Channelized Interface Drop-and-Insert
On channelized T1/E1/ISDNPRI interfaces configured for channelized operation, you can
insert channels (time slots) fromone port (for example, channels carrying voice) directly
into the other port on the PIM, replacing channels coming through the Routing Engine.
This feature, known as drop-and-insert, allows you to integrate voice and data channels
on a single T1 or E1 link.
The drop-and-insert feature allows you to remove the DS0time slots of one T1 or E1 port
and replace themby inserting the time slots of another T1 or E1 interface. This process
saves you the cost of two lines.
Although you need not use the same time slots on both interfaces, the time slot count
must be the same.
You must ensure that the signaling channels (port 16 for an E1 interface and port 24 for
a T1 interface) are also part of the channels that are being switched through the
drop-and-insert functionality. Junosdoesnot support switchingof voiceanddatabetween
ports by default. The channels that are not configured for the drop-and-insert feature
are used for normal traffic.
Both ports involved in the drop-and-insert configuration must use the same clock
sourceeither the device's internal clock or an external clock. The following clock source
settings are valid:
When port 0 is set to use the internal clock, port 1 must also be set to use it.
When port 0 is set to use its external clock, port 1 must be set to run on the same
clockthe external clock for port 0.
Related
Documentation
Example: Configuring Complementary Clock Sources on Channelized Interfaces on
page 128
Example: Configuring a Channelized Interface to Drop and Insert Time Slots
This example shows howto configure a channelized interface to drop and insert time
slots.
Overviewon page 125
Requirements
feature.
Overview
This example integrates voice and data channels on a single T1 or E1 link. It also removes
the DS0 time slots of one T1 or E1 port and replace themby inserting the time slots of
another T1 or E1 interface.
Port 16 for an E1 interface and port 24 for a T1 interface involved in the drop-and-insert
configuration must use the same clock sourceeither the device's internal clock or an
external clock. The following clock source settings are valid:
When port 0 is set to use the internal clock, port 1 must also be set to use it, and vice
versa.
Configuration
CLI Quick
Configuration
To quickly configure a channelized interface to drop and insert time slots, copy the
following commands and paste theminto the CLI:
[edit]
set interfaces ct1-3/0/0clocking external
set interfaces ct1-3/0/0partition 1 timeslots 1-10interface-type ds
set interfaces ct1-3/0/1 clocking external interface ct1-3/0/0
set interfaces ct1-3/0/1 partition 1 timeslots 1-10interface-type ds
set interfaces ds-3/0/0:1 data-input interface ds-3/0/1:1
Step-by-Step
Procedure
Mode.
To configure the drop-and-insert feature on a channelized T1/E1/ISDN PRI interface:
2. Configure the clock source and partition on the interface.
[edit]
user@host# set clocking external
user@host# set partition 1 timeslots 1-10
user@host# set partition 1 interface-type ds
NOTE: While configuring the drop-and-insert feature, you must ensure
that both ports on the channelized T1/E1 PIMrun on the same clock.
3. Create another interface.
[edit]
4. Configure the clock source and partition on the interface.
user@host# set clocking external interface ct1-3/0/0
user@host# set partition 1 timeslots 1-10
user@host# set partition 1 interface-type ds
NOTE: While configuring the drop-and-insert feature, you must ensure
that both ports on the channelized T1/E1 PIMrun on the same clock.
5. Create additional interfaces and configure the drop-and-insert feature on those
interfaces.
[edit interfaces ds-3/0/0:1]
user@host# edit interfaces ds-3/0/0:1
user@host# set interfaces ds-3/0/0:1 data-input interface ds-3/0/1:1
NOTE: Both interfaces configuredfor the drop-and-insert feature must
exist on the same PIM. For example, you can configure ds-3/0/0:1 as
the data input interface for ds-3/0/1:1, but not for ds-4/0/0:1.
ellipses (...).
[edit]
...
ct1-3/0/0 {
clocking external;
partition 1 timeslots 1-10 interface-type ds;
}
ds-3/0/0:1 {
data-input {
interface ds-3/0/1:1;
}
}
ct1-3/0/1 {
clocking external interface ct1-3/0/0;
}
Verification
user@host>showinterfaces ct1-3/0/1
Parent: ct1-3/0/1 Interface index 151
Link flags : None
DS1 alarms : None
DS1 defects : None
Line encoding: HDB3
Related
Documentation
page 128
showinterfaces (Channelized E1) in the Junos OS Interfaces Command Reference
Example: Configuring Complementary Clock Sources on Channelized Interfaces
This example shows howto configure complementary clock sources on channelized
interfaces.
Overviewon page 129
Requirements
feature.
Overview
J Series devices connected to one another must have complementary clock sources
configured. In the following examples, device R1 is connected to devices R2 and R3. Port
0onthechannelizedT1/E1/ISDNPRI PIMof R1 is connectedtoR2, andport 1 is connected
to R3. The drop-and-insert feature is configured on R1 to insert input coming fromR2 on
port 0 into port 1 for transmission to R3.
Devices R1, R2, and R3 can be configured in three ways, depending on whether the
drop-and-insert clock source on R1 is the external clock for port 0, the external clock for
port 1, or the device's internal clock.
Configuration
Configuring the External Clock for Port 0 as the Clock Source on page 129
Configuring the External Clock for Port 1 as the Clock Source on page 131
Configuring the Internal Clock of the Device as the Clock Source on page 133
Configuring the External Clock for Port 0 as the Clock Source
CLI Quick
Configuration
To quickly configure the external clock for port 0 as the clock source, copy the following
For device R2
[edit]
set interfaces ds-6/0/0:1 unit 0family inet address 10.46.46.1/30
For device R3
[edit]
For device R1
[edit]
set interfaces ct1-3/0/1 clocking external interface ct1-3/0/0
Step-by-Step
Procedure
Mode.
To configure the drop-and-insert interfaces on device R1 to use the external clock for
port 0:
1. Configure device R2.
[edit interfaces]
user@host# set ct1-6/0/0partition 1 timeslots 1-10
user@host# set ct1-6/0/0partition 1 interface-type ds
user@host# set ds-6/0/0:1 unit 0family inet address 10.46.46.1/30
[edit interfaces]
user@host# set ct1-3/0/0clocking external
[edit interfaces]
user@host# set ds-3/0/0:1 data-input interface ds-3/0/1:1
user@host# set ct1-3/0/1 clocking external interface ct1-3/0/0
user@host# set ct1-3/0/1 partition 1 timeslots 1-10
user@host# set ct1-3/0/1 partition 1 interface-type ds
For device R2
[edit]
user@host# showinterfaces ct1-6/0/0 {
}
ds-6/0/0:1 {
unit 0 {
family inet {
address 10.46.46.1/30;
}
}
}
For device R3
[edit]
clocking external;
}
ds-3/0/0:1 {
unit 0 {
family inet {
address 10.46.46.2/30;
}
}
}
For device R1
[edit]
clocking external;
}
ds-3/0/0:1 {
data-input {
}
}
ct1-3/0/1 {
}
Configuring the External Clock for Port 1 as the Clock Source
CLI Quick
Configuration
To quickly configure the external clock for port 1 as the clock source, copy the following
For device R2
[edit]
For device R3
[edit]
For device R1
[edit]
set interfaces ct1-3/0/0clocking external interface ct1-3/0/1
set interfaces ct1-3/0/1 clocking external
Step-by-Step
Procedure
Mode.
To configure the drop-and-insert interfaces on device R1 to use the external clock for
port 1:
[edit interfaces]
[edit interfaces]
[edit interfaces]
user@host# set ct1-3/0/0clocking external interface ct1-3/0/1
user@host# set ct1-3/0/1 clocking external
For device R2
[edit]
clocking external;
}
ds-6/0/0:1 {
unit 0 {
family inet {
address 10.46.46.1/30;
}
}
}
For device R3
[edit]
}
ds-3/0/0:1 {
unit 0 {
family inet {
address 10.46.46.2/30;
}
}
}
For device R1
[edit]
}
ds-3/0/0:1 {
data-input {
}
}
ct1-3/0/1 {
clocking external;
}
Configuring the Internal Clock of the Device as the Clock Source
CLI Quick
Configuration
Toquickly configure the Internal clock of device R1 as the clock source, copy the following
For device R2
[edit]
For device R3
[edit]
For device R1
[edit]
set interfaces ct1-3/0/0clocking internal
set interfaces ct1-3/0/1 clocking internal
Step-by-Step
Procedure
Mode.
To configure the drop-and-insert interfaces on device R1 to use the internal clock of the
device:
[edit interfaces]
[edit interfaces]
[edit interfaces]
user@host# set ct1-3/0/0clocking internal
user@host# set ct1-3/0/1 clocking internal
For device R2
[edit]
clocking external;
}
ds-6/0/0:1 {
unit 0 {
family inet {
address 10.46.46.1/30;
}
}
}
For device R3
[edit]
clocking external;
}
ds-3/0/0:1 {
unit 0 {
family inet {
address 10.46.46.2/30;
}
}
}
For device R1
[edit]
clocking internal;
}
ds-3/0/0:1 {
data-input {
}
}
ct1-3/0/1 {
clocking internal;
}
Verification
user@host> showinterfaces ct1-3/0/1
Link flags : None
DS1 alarms : None
DS1 defects : None
Line encoding: HDB3
Related
Documentation
showinterfaces in the Junos OS Interfaces Command Reference.
Action In operational mode, enter the showinterfaces ct1-3/0/1 command.
Sample Output user@host> showinterfaces ct1-3/0/1
Link flags : None
DS1 alarms : None
DS1 defects : None
Line encoding: HDB3
Related
Documentation
page 128
showinterfaces in the Junos OS Interfaces Command Reference.
ISDNPRI Operation
Example: Configuring a Channelized Interface for ISDN PRI Operation on page 137
Verifying ISDN PRI Configuration on Channelized Interfaces on page 138
Understanding ISDNPRI Operation for Channelized Interfaces
The Dual-Port Channelized T1/E1/ISDN PRI PIMprovides support for ISDN PRI services
suchas dial-inat thecentral office, callback fromthecentral office, andprimary or backup
network connections frombranch offices. You can install channelized T1/EI/ISDN PRI
PIMs and ISDNBRI PIMs and configure both ISDNPRI and ISDNBRI service on the same
J Series device.
On a J Series device with Dual-Port Channelized T1/E1/ISDNPRI PIMs, you can configure
each port for T1, E1, or ISDN PRI service, or for a combination of ISDN PRI and either
channelizedT1 serviceor E1 service. Youcanconfigureupto23timeslots inachannelized
T1 PRI interface and up to 30 time slots in a channelized E1 PRI interface as B-channels.
Each B-channel supports 64 Kbps of traffic. The unconfigured time slots can be used as
regular DS0 interfaces on top of the T1 or E1 physical layer.
You must also explicitly configure a D-channel for signaling purposes: time slot 24 on a
channelized T1 interface and time slot 16 on a channelized E1 interface.
In addition, you can configure the following options:
B-channel allociation orderThis setting controls the allocation of free B-channels
for dial-out calls. Values include ascending (allocating fromthe lowest numbered to
highest numbered) anddescending(thedefault--allocatingfromthehighest numbered
to the lowest numbered).
Switch typeThe following ISDN switch types are compatible with J Series devices:
ATT5EAT&T 5ESS
ETSINET3 for the UK and Europe
NI2National ISDN-2
NTDMS-100Northern TelecomDMS-100
Q.931 timersQ.931 is a Layer 3 protocol for the setup and termination of connections.
Thedefault valuefor eachtimer is 10seconds, but thevaluecanbeconfiguredbetween
1 and 65,536 seconds.
Dialer poolThe dialer pool priority has a range from1 through 255, with 1 designating
the lowest-priority interfaces and 255 designating the highest-priority interfaces.
Trace options
Related
Documentation
Example: Configuring a Channelized Interface for ISDNPRI Operation
Setting up the J Series device for ISDNPRI operation is a multipart process. First, you add
ISDNPRI serviceonachannelizedinterfaceas shownhere. Second, youconfigureadialer
interface. You can then configure ISDN services such as dial-in, callback, and backup.
In this example, you create the ct12/0/0 interface and partition the interface into time
slots 1 through23for B-channels andtimeslot 24for theD-channel. Youset theB-channel
allocation order to ascending. You also set the traceoptions flag to q921. You select
National ISDN-2 (NI2) as the ISDN switch type, set the Q.931 timers to 15, and create a
dialer pool called ISDN-dialer-group with a priority of 1.
To configure an ISDN PRI network service on a channelized interface:
1. Create a newinterface.
[edit]
2. Configure the partition and interface type.
user@host# set partition 1-23 timeslots 1-23
user@host# set partition 1-23 interface-type bc
user@host# set partition 24 timeslots 24
user@host# set partition 24 interface-type dc
3. Configure a trace options flag.
user@host# set traceoptions flag q921
4. Configure the B-channel allocation order.
user@host# set isdn-options bchannel-allocation ascending
5. Select the ISDN switch type.
user@host# set isdn-options switch-type ni2
6. Configure Q.931 timers.
user@host# set isdn-options t31015
7. Configure dialer options.
user@host#set dialer-options pool isdn-dialer-group priority 1
Related
Documentation
Verifying ISDN PRI Configuration on Channelized Interfaces on page 138
Verifying ISDNPRI Configuration on Channelized Interfaces
Purpose Verify that your configuration of ISDN PRI service on a channelized interface is correct.
user@host# showinterfaces ct1-2/0/0
traceoptions {
flag q921;
file {
isdnback;
}
}
clocking external;
isdn-options {
switch-type ni2;
}
dialer-options {
isdn-dialer-group priority 1;
}
partition 24 timeslots 24 interface-type dc;
partition 1-23 timeslots 1-23 interface-type bc;
[edit]
Meaning Verify that the output shows your intended ISDN PRI interface configuration.
Related
Documentation
showinterfaces in the Junos OS Interfaces Command Reference
PART 4
ISDN and VoIP Interfaces
ISDN on page 141
Voice over Internet Protocol with Avaya on page 183
CHAPTER 9
ISDN
ISDN Configuration Overviewon page 144
ISDN Interfaces on page 145
Dialer Interfaces on page 150
Bandwidth on Demand on page 165
Disabling ISDN Processes (CLI Procedure) on page 170
Verifying the ISDN Configuration on page 171
Understanding ISDN
Integrated Services Digital Network (ISDN) is a set of standards for digital transmission
over different media. These standards were created by the Consultative Committee for
International Telegraph and Telephone (CCITT) and International Telecommunication
Union (ITU). ISDN is an all-digital dial-up (on-demand) service that carries voice, data,
and video transmissions over telephone lines. As a dial-on-demand service, it has fast
call setup and lowlatency as well as the ability to carry high-quality voice, data, and
video transmissions. ISDN is also a circuit-switched service that can be used on both
multipoint andpoint-to-point connections. ISDNcancarry voice, data, images, andvideo
across a telephony network, using a single interface for all transmissions.
ISDN connectivity is supported as a backup for a primary Internet connection. J Series
devices can be configured to fail over to an ISDN interface when the primary connection
experiences interruptions in Internet connectivity.
You can also use ISDN at the central office to terminate calls that originate at branch
office routers and for central office callback for security, accounting, or cost savings at
the branch office.
ISDN Channels on page 142
Typical ISDN Network on page 142
ISDN Call Setup on page 143
ISDNChannels
ISDN uses separate channels to transmit voice and data over the network. Channels
operate at bandwidths of either 64 Kbps or 16 Kbps, depending on the type of channel:
Bearer channels (B-channels) use64Kbps totransmit voice, data, video, or multimedia
information. This bandwidthis derivedfromthefact that analogvoicelines aresampled
at a rate of 64 Kbps (8,000 samples per second, using 8 bits per sample).
Delta channels (D-channels) are control channels that operate at either 16 Kbps or
64Kbps. D-channelsareusedprimarilyfor ISDNsignalingbetweenswitchingequipment
in an ISDN network. In ISDN Basic Rate Interface applications, a D-channel can also
support customer packet data traffic at speeds up to 9.6 Kbps.
Typical ISDNNetwork
Figure 8 on page 142 shows a typical ISDN network.
Figure 8: ISDNNetwork
InFigure8onpage142, twotypes of end-user devices areconnectedtotheISDNnetwork:
Terminal equipment type1 (TE1) deviceDesignedtoconnect directly throughanISDN
telephone line.
Terminal equipment type 2 (TE2) deviceNot designed for ISDN. TE2 devicesfor
example, analog telephones or modemsmust connect to the ISDNnetwork through
a terminal adapter (TA).
A terminal adapter allows non-ISDN devices on the ISDN network.
NT Devices and S and T Interfaces
The interface between the ISDN network and a TE1 device or terminal adapter is called
an S interface. The S interface connects to a network termination type 2 (NT2) device
suchas aprivatebranchexchange(PBX), or directly totheTE1 deviceor terminal adapter,
as shown in Figure 8 on page 142. The NT2 device is then connected to a network
termination type 1 (NT1) device through a T interface. The S and T interfaces are
electrically equivalent.
An NT1 device is a physical layer device that connects a home telephone network to a
service provider carrier network. ISDN devices that connect to an NT1 device fromthe
home network side use a 4-wire S/T interface. The NT1 device converts the 4-wire S/T
interfaceintothe2-wireUinterfacethat telephonecarriers useas their plainoldtelephone
service (POTS) lines.
In the United States, NT1 devices are user owned. In many other countries, NT1 devices
are owned by the telephone service providers.
UInterface
The U interface connects the ISDN network into the telephone switch through line
termination(LT) equipment. TheconnectionfromLTequipment toother switches within
the telephone network is called the exchange termination (ET).
ISDNCall Setup
Before traffic can pass through an ISDN network, an ISDN call must be set up. ISDN call
setup requires a Layer 2 connection to be initialized and then a Layer 3 session to be
established over the connection.
To specify the services and features to be provided by the service provider switch, you
must set service profile identifiers (SPIDs) on TE1 devices before call setup and
initialization. If you define SPIDs for features that are not available on the ISDN link,
Layer 2 initialization takes place, but a Layer 3 connection is not established.
A SPID is a number that specifies the services available to you on the service provider
switch and defines the feature set ordered when the ISDN service is provisioned.
A terminal endpoint identifier (TEI) is a number that identifies a terminal endpoint, an
ISDN-capable device attached to an ISDN network through an ISDN interface on the
device. The TEI is a number between 0 and 127. The numbers 0 through 63 are used for
static TEI assignment, numbers 64 through 126 are used for dynamic assignment, and
127 is used for group assignment.
Layer 2 ISDNConnection Initialization
The TE device and the telephone network initialize a Layer 2 connection for ISDN as
follows:
1. The terminal equipment (TE) device and the telephone network exchange Receive
Ready (RR) frames, to indicate that they are available for data transmission. A call
cannot be set up if either the TE device or the telephone network does not transmit
RR frames.
2. If both ends of the ISDNconnection are available to receive data, the TE device sends
an Unnumbered Information (UI) frame to all devices on the ISDN link.
3. When it receives the UI frame, the network responds with a message containing a
unique TEI that identifies the endpoint on the ISDN link for all subsequent data
transmissions.
Chapter 9: ISDN
4. When the TE device receives the TEI message, it sends out a call setup message.
5. The network sends an acknowledgement of the call setup message.
6. When the TE device receives the acknowledgement, a Layer 2 connection is initialized
on the ISDN link.
Layer 3 ISDNSession Establishment
The caller, switch, and receiver establish a Layer 3 ISDN connection as follows:
1. When a Layer 2 connection is initialized, the caller sends a SETUP message to the
switch in the telephone network.
2. If thesetupmessageis valid, theswitchresponds withacall proceeding(CALLPROC)
message to the caller and a SETUP message to the receiver.
3. When the receiver receives the SETUP message, it responds with an ALERTING
message to the telephone switch.
4. This ALERTING message is then forwarded to the caller.
5. The receiver then accepts the connection by sending a CONNECT message to the
switch.
6. The switch forwards the CONNECT message to the caller.
7. The caller responds with an acknowledgement message (CONNECT ACK).
8. When the CONNECT ACK message is received by the receiver, the ISDN call is set up
and traffic can pass.
Related
Documentation
Understanding ISDN Interfaces on page 145
Understanding Dialer Interfaces on page 150
Understanding Bandwidth on Demand on page 166
ISDNConfiguration Overview
To configure ISDN interfaces:
1. Order an ISDN line fromyour telecommunications service provider. Contact your
service provider for more information.
2. Configure at least one ISDN interface (physical interface). See Example: Adding an
ISDN BRI Interface on page 148.
3. Configure at least one dialer interface (logical interface). See Example: Configuring
Dialer Interfaces on page 152.
4. Configure one of the following back up methods on each dialer interface:
Configure dial backup if you want to use ISDN to backup the primary device
interfaces. See Example: Configuring Dial Backup on page 155.
Configure dialer filters for dial-on-demand routing backup. You can configure
dial-on-demand routing with or without OSPF support. See Example: Configuring
Dialer Filters for Dial-on-Demand Routing Backup on page 157 or Example:
Configuring Dial-on-Demand Routing Backup with OSPF Support on page 157.
Configure dialer watch. See Example: Configuring Dialer Watch on page 159.
Configure dial-in or callback. See Example: Configuring Dial-In and Callback on
page 163.
NOTE: You can configure only one back up method per dialer interface.
5. (Optional) Configure bandwidth on demand. See Example: Configuring Bandwidth
on Demand on page 167.
Related
Documentation
Configuring ISDN Services Physical and Logical Interface Properties in the Junos OS
Network Interfaces Configuration Guide
ISDNInterfaces
Example: Adding an ISDN BRI Interface on page 148
Understanding ISDNInterfaces
ISDNprovides two basic types of service, ISDNBasic Rate Interface (ISDNBRI) andISDN
Primary Rate Interface (ISDN PRI).
ISDN BRI Interface Types on page 146
ISDN PRI Interface Types on page 146
ISDN Interface Configuration on page 147
Chapter 9: ISDN
ISDNBRI Interface Types
ISDN BRI is an ISDN service intended for home and small enterprise applications. ISDN
BRI consists of two64-Kbps B-channels tocarryvoiceor dataandone16-Kbps D-channel
for control and signaling.
ISDNBRI is designed for high-bandwidth data transmissions through existing telephone
lines. The copper wires that make up much of the existing telephony infrastructure can
support approximately 160Kbps, which provides enough bandwidth for two B-channels
and a D-channel, leaving 16 Kbps for any data framing, maintenance, and link control
overhead.
Up to six of the following field-replaceable units (FRUs) are available for ISDN BRI
connectivity:
4-port S/T Physical Interface Module (PIM) supporting ITU-T I.430, ETSI TS 101080,
and GR-1089-Core Type III
4-port U PIMsupporting ANSI T.601 and GR-1089-Core
A J Series device with one or more ISDN BRI ports has the following types of ISDN
interfaces:
Physical ISDN BRI interfacebr-pim/0/port
Physical B-channel interfacebc-pim/0/port
Physical D-channel interfacedc-pim/0/port
Logical dialer interfacedln
Each ISDN BRI port has two B-channels for transport, identified as bc-pim/0/port:1 and
bc-pim/0/port:2, and one D-channel for control, identified as dc-pim/0/port. On ISDN
BRI interfaces, the B-channels and D-channel have no configurable settings, but you can
monitor themfor interface status and statistics.
To configure ISDN BRI service on a J Series device, you configure the physical ISDN BRI
interface and the logical dialer interface.
ISDNPRI Interface Types
ISDN PRI is designed for users with greater capacity requirements than can be met with
ISDN BRI. In the United States, the most common ISDN PRI supports 23 B-channels to
carry trafficand1 D-channel for control andsignaling, totaling1,536Kbps, whichis roughly
equivalent to a T1 link. In Europe, the most common ISDN PRI supports 30 B-channels
and 1 D-channel, totaling 1,984 Kbps, which is roughly equivalent to an E1 link.
For ISDN PRI, up to six Dual-Port Channelized T1/E1/ISDN PRI PIMs, supporting ITU-T
Q.920, Q.921: LAPD, Q.930, and Q.931, are available for ISDN connectivity.
On a J Series device with one or more Dual-Port Channelized T1/E1/ISDN PRI PIMs, you
can configure each port on the PIMfor either T1, E1, or ISDN PRI service, or for a
combination of ISDN PRI and either T1 or E1 service. For ISDN PRI service, you configure
the following types of ISDN interfaces as channels on the channelized T1 or E1 interface:
Physical B-channel interfacebc-pim/0/port:channel
On a channelized T1 interface, up to 23 time slots can be configured as ISDN PRI
B-channels.
On a channelized E1 interface, up to 30 time slots can be configured as ISDN PRI
B-channels.
Physical D-channel interfacedc-pim/0/port:channel
On a channelized T1 interface, you configure time slot 24 as the D-channel.
On a channelized E1 interface, you configure time slot 16 as the D-channel.
Logical dialer interfacedln
ISDNInterface Configuration
To enable ISDN interfaces to work properly, you must configure the interface properties:
Calling numberThis number represents the caller's number. It is sent to the ISDN
switch during the call setup.
SPID
Static TEIThis number comes fromyour service provider. Valid values range from0
to 63. If you are using a service provider that requires SPIDs, you cannot place calls
until the interface sends a valid, assigned SPIDto the service provider when accessing
the ISDN connection.
NOTE:
When configuring the static TEI value, please note the following:
If the field is left blank, the device dynamically acquires a TEI.
If you have configured a second SPID, you cannot set a static TEI value.
If you have an NTDMS-100 or NI1 switch, an additional box for a service
provider ID is provided.
Incoming called numberConfigure incoming call properties if you have remote
locations dialing into the device through the ISDN interface.
Chapter 9: ISDN
In addition to configuring ISDN properties, you must set the following additional ISDN
values:
Dialer poolDialer pool priority has a range from1 to 255, with 1 designating the
lowest-priority interfaces and 255 designating the highest-priority interfaces.
ISDN switch typeThe following switches are compatible with J Series devices:
ATT5EAT&T 5ESS
ETSINET3 for the UK and Europe
NI1National ISDN-1
NTDMS100Northern TelecomDMS-100
Q.931 timer intervalQ.931 is a Layer 3 protocol for the setup and termination of
connections. The default value for the timer is 10 seconds, but the value can be
configured between 1 and 65,536 seconds.
TEI negotiationvalueYoumust specifywhentheTEI negotiates withtheISDNprovider.
If you specify first-call, activation does not occur until a call is sent. If you specify
power-up, activation occurs when the device is powered on. This is the default value.
Related
Documentation
Example: Adding an ISDN BRI Interface on page 148
Example: Adding an ISDNBRI Interface
This example showhowto add an ISDN BRI interface.
Overviewon page 148
Requirements
feature.
Overview
Inthis example, youcreatethebr-1/0/3ISDNBRI interfaceandaddtheisdn-dialer-options
dialer pool to the interface. You set the pools priority to 255. When configuring ISDNBRI
properties, you set the calling number to 18005555555, the SPID to 00108005555555,
the static TEI value to23, andthe incoming callednumber to18883333456. Additionally,
you set the ISDN switch type to att5e, the Q.931 timer to 15 seconds, and you configure
the TEI to negotiate with the ISDN provider when the device is powered on.
Configuration
CLI Quick
Configuration
To quickly add an ISDN BRI interface, copy the following commands and paste them
into the CLI:
[edit]
set interfaces br-1/0/3 dialer-options pool isdn-dialer-group priority 255
setinterfacesbr-1/0/3isdn-optionscalling-number 18005555555spid1 00108005555555
static-tei-val 23 incoming-called-number 18883333456
set interfaces br-1/0/3 isdn-options switch-type att5e t31015 tei-option power-up
Step-by-Step
Procedure
Mode.
To configure an ISDN BRI network interface:
1. Create an ISDN interface.
[edit]
user@host# edit interfaces br-1/0/3
2. Configure the dialer pool.
[edit interfaces br-1/0/3]
user@host# set dialer-options pool isdn-dialer-group priority 255
3. Configure the ISDN BRI properties.
user@host# set isdn-options calling-number 18005555555
user@host# set isdn-options spid1 00108005555555
user@host# set isdn-options static-tei-val 23
user@host# set isdn-options incoming-called-number 18883333456
4. Select the ISDN switch type.
user@host# set isdn-options switch-type att5e
5. Specify the Q.931 timer interval.
user@host# set isdn-options t31015
6. Specify when the TEI negotiates with the ISDN provider.
user@host# set isdn-options tei-option power-up
[edit]
user@host# showinterfaces br-1/0/3
isdn-options {
switch-type att5e;
spid1 00108005555555;
Chapter 9: ISDN
calling-number 18005555555;
incoming-called-number 18883333456;
tei-option power-up;
static-tei-val 23;
t310 15;
}
dialer-options {
pool isdn-dialer-group priority 255;
}
Verification
Verifying an ISDN BRI Interface on page 150
Verifying an ISDNBRI Interface
Purpose Verify that the ISDN BRI interface is correctly configured.
Action Fromoperational mode, enter the showinterfaces extensive command.
Related
Documentation
Configuring ISDN Physical Interface Properties in the Junos OS Network Interfaces
Configuration Guide
Dialer Interfaces
Example: Configuring Dialer Interfaces on page 152
Dial Backup on page 154
Dial-on-Demand Routing Backup on page 156
Dialer Watch on page 158
Dial-In and Callback on page 161
Understanding Dialer Interfaces
A dialer interface (dln) is a logical interface for configuring dialing properties and the
control interface for a backup ISDN connection. You can configure multiple dialer
interfaces for different functions on the device. The dialer interface can performas a
backup interface for one primary interface, as a dialer filter, or as a dialer watch interface,
but these operations are mutually exclusive.
To enable dialer interfaces to work properly, you must configure the interface properties:
Encapsulation modeThe interface can be configured in the following modes:
Multilink mode using Multilink Point-to-Point Protocol (MLPPP)
encapsulationMLPPP is a protocol for aggregating multiple constituent links into
one larger PPP bundle. You can bundle up to eight B-channels.
Normal mode using Point-to-Point Protocol (PPP) encapsulationPPP is for
communicationbetweentwocomputers usingaserial interface. Usethis modewhen
the device is using only one B-channel.
Normal mode using Cisco High-Level Data Link Control (HDLC)
encapsulationCisco-compatibleHDLCis agroupof protocols for transmittingdata
betweennetworkpoints. Usethis modewhenthedeviceis usingonly oneB-channel.
NOTE: MPLS over ISDNis supported only with MLPPP encapsulation. If
you use PPP or Cisco HDLC, MPLS packets might be dropped.
Logical unitYou can set the logical unit to 0only, unless you are configuring the dialer
interface for MLPPP encapsulation.
Hold-time valueThe hold-time value is used to damp interface transitions. When an
interface goes fromup to down, it is not advertised as down to the rest of the system
until it remains unavailable for the hold-time period. Similarly, an interface is not
advertised as up until it remains operational for the hold-time period. The hold time is
three times the interval at which keepalive messages are sent.
Delay intervalsYou can configure the following delay intervals:
Activation delayTime to wait before activating the backup interface after the
primary interface is down. The default value is 0 seconds with a maximumvalue of
60 seconds. Use activation delay only for dialer backup and dialer watch.
Deactivation delayTime to wait before deactivating the backup interface after the
primary interface is up. The default value is 0 seconds with a maximumvalue of 60
seconds. Use deactivation delay only for dialer backup and dialer watch.
Redial delayNumber of seconds to wait before redialing a failed outgoing ISDN
call. The default value is 3 seconds, with a range from2 through 255.
Idle timeoutTime a connection is idle before disconnecting. The default value is 120
seconds, with a range from0 through 4,294,967,295. This option is used only to
configure a dialer filter.
Initial route checkTime to wait before checking if the primary interface is up. The
default value is 120seconds, with a range of 1 through 300seconds. This option is used
only to configure dialer watch.
PoolName of a group of ISDN interfaces configured to use the dialer interface.
Chapter 9: ISDN
NOTE: If you configure multiple dialer interfaces, ensure that the same IP
subnet address is not configured on different dialer interfaces. Configuring
the same IP subnet address on multiple dialer interfaces can cause both
inconsistency in the route and packet loss. The device might route packets
throughanother dialer interfacewiththeIPsubnet addressinsteadof through
the dialer interface to which the ISDNmodemcall is mapped.
Related
Documentation
Example: Configuring Dialer Interfaces on page 152
Understanding Dial Backup on page 154
Understanding Dial-on-Demand Routing Backup on page 156
Understanding Dialer Watch on page 158
Understanding Dial-In and Callback on page 161
Example: Configuring Dialer Interfaces
This example shows howto configure a logical dialer interface.
Overviewon page 152
Requirements
feature.
Overview
In this example, you create the dl0 dialer interface and set the encapsulation type for
the interface to Cisco HDLC. You set the hold-time value to 60 milliseconds. When
configuring delay intervals, you set the activation delay to 60 seconds, the deactivation
delay to 30 seconds, and the redial delay to 5 seconds. Additionally, you create the
isdn-dialer-group dialer pool, set the dial string to 5551212, specify 172.20.10.2 as the
source IP address for the dialer interface, and specify 172.20.10.1 as the destination IP
address for the dialer interface. (The destination IP address is optional.)
Configuration
CLI Quick
Configuration
To quickly configure a logical dialer interface, copy the following commands and paste
theminto the CLI:
[edit]
set interfaces dl0description T1-backup encapsulation cisco-hdlc hold-time down 60
up 60
set interfaces dl0unit 0dialer-options activation-delay 60deactivation-delay 30
redial-delay 5 pool isdn-dialer-group dial-string 5551212
set interfaces dl0unit 0family inet address 172.20.10.2 destination 172.20.10.1
Step-by-Step
Procedure
Mode
To configure a logical dialer interface:
1. Create and describe the interface.
[edit]
user@host# edit interfaces dl0
user@host# set description T1-backup
2. Configure the encapsulation mode.
[edit interfaces dl0]
user@host# set encapsulation cisco-hdlc
3. Enter the hold-time values.
user@host# set hold-time down 60
user@host# set hold-time up 60
4. Create the logical unit.
user@host# edit unit 0
5. Configure the delay intervals.
[edit interfaces dl0 unit 0 dialer-options]
user@host# set activation-delay 60
user@host# set deactivation-delay 30
user@host# set redial-delay 5
6. Configure the dialer pool.
user@host# set pool isdn-dialer-group
7. Specify which remote destination to call.
user@host# set dial-string 5551212
8. Configure source and destination IP addresses.
[edit]
user@host# set interfaces dl0unit 0family inet address 172.20.10.2 destination
172.20.10.1
Results Fromconfiguration mode, confirmyour configuration by entering the showinterfaces dl0
[edit]
Chapter 9: ISDN
user@host# showinterfaces dl0
showinterfaces dl0
hold-time up 60 down 60;
encapsulation cisco-hdlc;
unit 0 {
family inet {
address 172.20.10.2/32 {
destination 172.20.10.1;
}
}
dialer-options {
pool isdn-dialer-group;
dial-string 5551212;
redial-delay 5;
activation-delay 60;
deactivation-delay 30;
}
}
Verification
Verifying Dialer Interface Configuration on page 154
Verifying Dialer Interface Configuration
Purpose Verify that the dialer interface is correctly configured.
Action Fromoperational mode, enter the showinterfaces dl0 command.
Related
Documentation
Configuring ISDN Logical Interface Properties in the Junos OS Network Interfaces
Configuration Guide
Dial Backup
Example: Configuring Dial Backup on page 155
Understanding Dial Backup
Dial backup is a feature that reestablishes network connectivity through one or more
backup ISDNdialer interfaces after a primary interface fails. The backup dialer interfaces
areactivatedonly whentheprimary interfacefails. ISDNbackupconnectivity is supported
on all interfaces except lsq-0/0/0. When the primary interface is reestablished, the ISDN
interface is disconnected.
Related
Documentation
Example: Configuring Dial Backup on page 155
Example: Configuring Dial Backup
This example shows howto configure a primary backup connectivity.
Overviewon page 155
Requirements
Before you begin:
1. AddinganISDNBRI interface. SeeExample: AddinganISDNBRI Interface onpage148.
2. Configure dialer interfaces. See Example: Configuring Dialer Interfaces on page 152.
Overview
In this example, you select ge-0/0/0 unit 0 as the primary interface for backup ISDN
connectivity and configure dl0.0 as the backup dialer interface.
Configuration
Step-by-Step
Procedure
To configure a primary interface for backup connectivity:
Select the physical interface for backup ISDN connectivity. 1.
[edit]
user@host# edit interfaces ge-0/0/0unit 0
2. Configure the backup dialer interface.
[edit interfaces ge-0/0/0 unit 0]
user@host# set backup-options interface dl0.0
[edit]
user@host# commit
Verification
To verify the configuration is working properly, enter the showInterfaces ge-0/0/0
command.
Related
Documentation
Chapter 9: ISDN
Dial-on-Demand Routing Backup
Example: Configuring Dialer Filters for Dial-on-Demand Routing Backup on page 157
Example: ConfiguringDial-on-DemandRoutingBackupwithOSPFSupport onpage157
Understanding Dial-on-Demand Routing Backup
Dial-on-demand routing (DDR) backup is a feature that provides a J Series device with
full-timeconnectivity across anISDNline. YouconfigureDDRusingthefollowingfeatures:
Dialer filtersA dialer filter is a stateless firewall filter that enables DDR backup when
applied to a physical ISDN interface. Within this configuration, the dialer interface is
configured as a passive static route. The passive static route has a lower priority than
dynamic routes, meaning that the static route is used only when the dynamic routes
are no longer available.
Whenafloatingstatic routeis configuredonaninterfacewithadialer filter, theinterface
can be usedfor backup. Afloating static route is a route with an administrative distance
greater than the administrative distance of the dynamically learned versions of the
same route.
If all dynamic routes on a primary serial T1, E1, T3, E3, Fast Ethernet, Gigabit Ethernet,
or Point-to-Point Protocol over Ethernet (PPPoE) interface to an address are lost from
the routing table and the device receives a packet for that address, the dialer interface
initiates an ISDN backup connection. The dialer interface then sends the packet over
the backup connection. To save connection time costs, the device drops the ISDN
connection after a configured period of inactivity.
This DDRbackupmethodallows anISDNlinetobeactivatedonly whennetwork traffic
configured as an interesting packet arrives on the network. After the network traffic
is sent, an inactivity timer is triggered, and the connection is closed after the timer
expires. Youdefineaninterestingpacket as part of thedialer filter featureconfiguration.
DemandcircuitsAdemandcircuit is anetwork segment whosecost varies withusage,
according to a service-level agreement with a service provider. Demand circuits limit
traffic based on either bandwidth (bites or packets transmitted) or access time. For
example, ISDN interfaces can be configured for DDR backup. In OSPF, the demand
circuit reduces the amount of OSPF traffic by removing all OSPF protocols when the
routing domain is in a steady state.
Two types of routing protocol traffic are used by OSPF to establish and maintain
network structure. First, periodic hello packets are sent over each link for neighbor
discovery and maintenance. Second, OSPF protocol traffic achieves and maintains
link-statedatabasesynchronizationbetweendevices. TheOSPFdemandcircuit feature
removes the periodic nature of both traffic types and reduces the amount of OSPF
traffic by removing all OSPF protocol traffic froma demand circuit when the routing
domain is in a steady state. This feature allows the underlying data-link connections
to be closed when no application traffic is on the network.
Related
Documentation
Example: Configuring Dialer Filters for Dial-on-Demand Routing Backup
In this example, you create a dialer filter called int-packet and a corresponding dialer
filter rule called term1. Within term1, you configure an ICMP packet as the interesting
packet. You then apply to the dialer filter to the dl0 interface.
To configure a dialer filter for dial-on-demand backup:
1. Create the dialer filter.
[edit]
user@host# edit firewall family inet dialer-filter int-packet
2. Create the dialer filter rule.
[edit firewall family inet dialer-filter int-packet]
user@host# set termterm1 fromprotocol icmp then note
3. Select the dialer interface to apply to the filter.
[edit]
user@host# edit interfaces dl0 unit 0
4. Select the dialer filter and apply it to the dialer interface.
[edit interfaces dl0 unit 0]
user@host# set family inet filter dialer int-packet
Related
Documentation
Example: Configuring Dial-on-Demand Routing Backup with OSPF Support
This example shows howto configure a dial-on-demand routing backup with OSPF
support.
Overviewon page 158
Chapter 9: ISDN
Requirements
Before you begin, you must configure OSPF on the device.
Overview
Inthis example, youcreatethe0.0.0.0OSPFareaandconfigureOSPFon-demandcircuits
for thedl0ISDNdialer interface, whichis participatingas anon-demandroutinginterface.
Configuration
Step-by-Step
Procedure
To configure OSPF demand circuits:
Create the OSPF area. 1.
[edit]
user@host# edit protocols ospf area 0.0.0.0
2. Specify the on-demand routing interface.
[edit protocols ospf area 0.0.0.0]
user@host# set interface dl0demand-circuit
[edit]
user@host# commit
Verification
To verify the configuration is working properly, enter the showprotocols ospf command.
Related
Documentation
Dialer Watch
Example: Configuring Dialer Watch on page 159
Understanding Dialer Watch
Dialer watch is a DDR backup feature that provides dependable connectivity without
relying on a dialer filter to activate the ISDNinterface. The ISDNdialer interface monitors
the existence of each route on a watch list. If all routes on the watch list are lost from
the routing table, dialer watch initiates the ISDN interface for failover connectivity.
Configure dialer watch options for each ISDN interface participating in the dialer watch
feature. Each ISDN interface must have the same pool identifier to participate in dialer
watch.
Related
Documentation
Example: Configuring Dialer Watch on page 159
Example: Configuring Dialer Watch
This example shows howto configure a dialer watch interface.
Overviewon page 159
Requirements
Before you begin:
1. AddinganISDNBRI interface. SeeExample: AddinganISDNBRI Interface onpage148.
3. Configure dial backup. See Example: Configuring Dial Backup on page 155.
4. Configuredialer filters for dial-on-demandroutingbackup. SeeExample: Configuring
Dialer Filters for Dial-on-Demand Routing Backup on page 157.
5. Configure dial-on-demand routing backup with OSPF support. See Example:
Overview
In this example, you add a dialer watch to the dl0 interface. You then configure the ISDN
interface to participate as a dialer watch interface. You create the dw-group dialer pool
on the unit 0logical interface and specify that the dialer should watch the 172.27.27.0/24
list of routes. Once you have finished configuring the dialer watch interface, you select
the br-1/0/3 ISDN physical interface for ISDN BRI.
Configuration
CLI Quick
Configuration
To quickly configure a dialer watch interface, copy the following commands and paste
theminto the CLI:
[edit]
set interfaces dl0description dialer-watch
set interfaces dl0unit 0dialer-options pool dw-group watch-list 172.27.27.0/24
set interfaces br-1/0/3 dialer-options pool isdn-dialer-group
Chapter 9: ISDN
Step-by-Step
Procedure
Mode.
To configure a dialer watch interface:
1. Create the dialer watch interface.
[edit]
user@host# edit interfaces dl0set description dialer-watch
2. Specify a logical interface.
user@host# edit unit 0dialer-options
3. Specify a dialer pool.
user@host# set pool dw-group
4. Configure the list of routes for dialer watch.
user@host# set watch-list 172.27.27.0/24
5. Select the ISDN physical interface for ISDN BRI.
[edit]
user@host# edit interfaces br-1/0/3 dialer-options pool isdn-dialer-group
[edit]
description dialer-watch;
unit 0 {
dialer-options {
pool dw-group;
watch-list {
172.27.27.0/24;
}
}
}
Verification
Verifying a dialer watch interface on page 160
Verifying a dialer watch interface
Purpose Verify a dialer watch interface.
Action Fromoperational mode, enter the showinterfaces dl0 command.
Related
Documentation
Dial-In and Callback
Example: Configuring Dial-In and Callback on page 163
Understanding Dial-In and Callback
If you are a service provider or a corporate data center into which a remote location dials
in during an emergency, you can configure your Juniper Networks device to accept
incoming ISDNcalls originating fromthe remote location. The dial-in feature enables the
device to receive calls fromthe remote end of a backup ISDN connection. The remote
endof theISDNcall might beaserviceprovider, acorporatecentral location, or acustomer
premises equipment (CPE) branch office. Each dialer interface accepts calls fromonly
those callers whose caller IDs are configured on it.
NOTE: Incoming voice calls are currently not supported.
Alternatively, you can configure the device toreject the incoming ISDNcalls andcall back
theremotelocation. Thecallback featurelets youcontrol access by allowingonly specific
remote locations to connect to the device. The feature also enables the device to call
back the caller fromthe remote end of a backup ISDN connection. Instead of accepting
acall fromtheremoteendof theconnection, thedevicerejects thecall, waits aconfigured
period of time, and calls a number configured on the device's dialer interface.
Whenit receivesanincomingISDNcall, theJuniper Networksdevicematchestheincoming
call's caller ID against the caller IDs configured on the devices dialer interfaces. If an
exact match is not found and the incoming call's caller ID has more digits than the
configured caller IDs, the device performs a right-to-left match of the incoming call's
caller ID with the configured caller IDs and accepts the incoming call if a match is found.
For example, if the incoming call's caller ID is 4085550115 and the caller ID configured
onadialer interfaceis 5550115, theincomingcall is accepted. Eachdialer interfaceaccepts
calls fromonly those callers whose caller IDs are configured on it.
Dial-In and Callback Encapsulation on page 162
Dial-In Configuration on page 162
Callback Configuration on page 163
Chapter 9: ISDN
Dial-In and Callback Encapsulation
The dialer interface of the device and the dialer interface of the remote device must have
the same encapsulationPPP, MLPPP, or Cisco HDLC. If the encapsulation is different,
the ISDN call is dropped. Table 16 on page 162 describes howthe device monitors
encapsulation.
Table 16: Encapsulation Monitoring by Juniper Networks Devices
Encapsulation Monitoring
and Call Status
Possible Action on Juniper
Networks Device's Dialer
Interface
Encapsulation on Remote
Router's Dialer Interface
Encapsulation on Juniper
Networks Device's
Interface
Device performs
encapsulation monitoring.
ISDN call is successful
because encapsulation
matches.
Accepts an incoming call
Rejects an incoming call
and calls back the
incoming number when
callback is enabled on the
dialer interface
PPP PPP
MLPPP MLPPP
Device performs
ISDN call is dropped because
of encapsulation mismatch.
MLPPP or Cisco HDLC PPP
PPP or Cisco HDLC MLPPP
Device does not perform
Success of the ISDN call
dependsontheencapsulation
monitoring capability of the
remote device.
Dials out
as a result of having
originally dialed out,
because the dialer
interface of the remote
device has callback
enabled
PPP, MLPPP, or Cisco HDLC PPP or MLPPP
Dials out
as a result of having
originally dialed out,
because the dialer
interface of the remote
device has callback
enabled
Rejects an incoming call
and calls back the
incoming number when
callback is enabled on the
dialer interface
PPP, MLPPP, or Cisco HDLC Cisco HDLC
Dial-In Configuration
Whenyouenablethedial-infeatureonadialer interfaceassociatedwithanISDNphysical
interface, the device accepts incoming calls. You can specify that the interface accept
all incoming calls, or you can configure up to 15 specific incoming numbers per dialer
interface that you want the device to accept.
If multiple devices are connected to the same ISDN line, you can configure an ISDN
interface to screen incoming calls based on the incoming called number. Each interface
accepts only the calls whose called numbers are configured on it. If an exact match is
not found, the incoming call is ignored.
The same caller ID must not be configured on different dialer interfaces. However, you
can configure caller IDs with more or fewer digits on different dialer interfaces. For
example, you can configure the caller IDs 14085550115, 4085550115, and 5550115 on
different dialer interfaces. Additionally, if you configure one of the interfaces to accept
all calls, the device only uses that interface if the incoming call's caller IDdoes not match
the caller IDs configured on other dialer interfaces.
You can also configure the device to reject (ignore) calls fromspecific numbers. You
might choose to use this option if a the number belongs to another device connected to
the same ISDNline. For example, if another device on the same ISDNline has the called
number 4085551091, you can configure the called number 4085551091 with the reject
option on the ISDN interface so that it does not accept calls with that number.
Callback Configuration
When you enable the callback feature on a dialer interface, the ISDN interface rejects
incoming calls, waits for 5 seconds (the default callback wait period) or the interval you
specify, and then calls back the incoming number.
Before configuring callback on a dialer interface, ensure that the following conditions
exist:
The dialer interface is not configured as a backup for a primary interface.
The dialer interface does not have a watch list configured.
Only one dial string is configured for the dialer interface.
Dial-in is configured on the dialer interface of the remote device that is dialing in.
Related
Documentation
Example: Configuring Dial-In and Callback on page 163
Example: Configuring Dial-In and Callback
This example shows howto configure a dial-in and callback options.
Overviewon page 164
Requirements
Before you begin:
Chapter 9: ISDN
1. Add an ISDNBRI interface. See Example: Adding an ISDNBRI Interface on page 148.
3. Configuredialer backupinterfaces. SeeExample: ConfiguringDial Backup onpage155.
4. Configuredialer filters for dial-on-demandroutingbackup. SeeExample: Configuring
Dialer Filters for Dial-on-Demand Routing Backup on page 157.
5. Configure dial-on-demand routing backup with OSPF support. See Example:
6. Configure dialer watch. See Example: Configuring Dialer Watch on page 159.
Overview
In this example, you set the dialer interfaces as dl0 and set the incoming map options
for the dialer interface on a logical interface to 4085550115. Then, you set the callback
wait period to 5 and configure an ISDN interface to screen incoming ISDN calls. Finally,
you set the device to reject incoming calls fromthe specified number.
Configuration
CLI Quick
Configuration
To quickly configure dial-in and callback options, copy the following commands and
paste theminto the CLI:
[edit]
set interfaces dl0unit 0dialer-options incoming-map caller 4085550115
set interfaces dl0unit 0dialer-options callback callback-wait-period 5
set interfaces br-1/0/3 isdn-options incoming-called-number 4085550115
set systemprocesses isdn-signaling reject-incoming
Step-by-Step
Procedure
Mode.
To configure dial-in and callback options:
1. Create a dialer interface.
[edit]
user@host# edit interfaces dl0unit 0dialer-options
2. Configure the incoming map options for the dialer interface on a logical interface.
user@host# set incoming-map caller 4085550115
3. Configure callback options for the dialer interface.
user@host# set callback
user@host# set callback-wait-period 5
4. Configure an ISDN interface to screen incoming ISDN calls.
[edit interfaces br-1/0/3 ]
user@host# set isdn-options incoming-called-number 4085550115
5. Configure the device to reject incoming calls fromthe specified number.
[edit]
user@host# set systemprocesses isdn-signaling reject-incoming
[edit]
user@host showinterfaces
br-1/0/3 {
isdn-options {
incoming-called-number 4085550115;
}
}
dl0 {
unit 0 {
dialer-options {
callback;
callback-wait-period 5;
}
}
}
Verification
Verifying Dial-In and Callback Options on page 165
Verifying Dial-In and Callback Options
Purpose Verify dial-in and callback options.
Action Fromoperational mode, enter the showinterfaces command.
Related
Documentation
Bandwidth on Demand
Understanding Bandwidth on Demand on page 166
Example: Configuring Bandwidth on Demand on page 167
Chapter 9: ISDN
Understanding Bandwidth on Demand
Bandwidth on demand is an ISDN cost-control feature that defines the bandwidth
threshold that must be reached on all links before a device initiates additional ISDNdata
connections to provide more bandwidth.
You can define a threshold for network traffic on the device using the dialer interface and
ISDNinterfaces. A number of ISDNinterfaces are aggregated together into a bundle and
assigned a single dialer profile. A dialer profile is a set of characteristics configured for
the ISDN dialer interface. Dialer profiles allowthe configuration of physical interfaces to
be separated fromthe logical configuration of dialer interfaces required for ISDN
connectivity. This featurealsoallows physical andlogical interfaces tobeboundtogether
dynamically on a per-connection basis.
Initially, only one ISDNlink is active, and all packets are sent through this interface. When
a configured threshold is exceeded, the dialer interface activates another ISDN link and
initiates a data connection. The threshold is specified as a percentage of the cumulative
load of all UP links that are part of the bundle. When the cumulative load of all UP links,
not counting the most recently activated link, is at or belowthe threshold, the most
recently activated link is deactivated.
To enable bandwidth on demand, you must configure its properties:
Dialer interfaceYoucanconfiguremultipledialer interfacesfor bandwidth-on-demand
by incrementing the unit numberfor example, dl0.1, dl0.2, and so on. For ISDN BRI,
you can group up to four ISDN interfaces together when configuring bandwidth on
demand, for a total of eight B-channels (two channels per interface) providing
connectivity. For ISDNPRI, thepool limit is eight B-channels per channelizedT1/E1/ISDN
PRI port. Each ISDN interface must have the same pool identifier to participate in
bandwidth on demand.
Dialer optionsDialer options for bandwidth on demand include:
Dial stringTelephone number for the interface to dial that establishes ISDN
connectivity. You can configure a maximumof 15 dial strings per dialer interface.
Load intervalInterval of time used to calculate the average load on the dialer
interface. The default value is 60 seconds with a range of 20 through 180 seconds.
The value must be a multiple of 10.
Load thresholdThreshold above which an additional ISDN interface is activated,
specified as a percentage of the cumulative load of all UP links. The default value
is 100, with a range of 0 through 100.
PoolName of a group of ISDN interfaces configured to use the dialer interface.
Unit propertiesUnit properties include the F max period, which is the maximum
number of compressedpackets allowedbetweenthe transmissionof full packets. The
value can be between 1 and 65,535.
Logical propertiesLogical properties for bandwidth on demand include:
Fragment thresholdMaximumsize, in bytes, for multilink packet fragments. The
valuecanbebetween128and16,320bytes. Thedefault is 0bytes (nofragmentation).
Any nonzero value must be a multiple of 64 bytes.
Maximumreceivedreconstructedunit (MRRU)This valueis expressedas anumber
between 1500 and 4500 bytes.
Packet compressionYou can configure the following compression types:
ACFC(addressandcontrol fieldcompression)Conservesbandwidthbycompressing
the address and control fields of PPP-encapsulated packets.
PFC(protocol fieldcompression)Conservesbandwidthbycompressingtheprotocol
field of a PPP-encapsulated packet.
Related
Documentation
Example: Configuring Bandwidth on Demand on page 167
Example: Configuring Bandwidth on Demand
This example shows howto configure a bandwidth on demand.
Overviewon page 167
Requirements
Before you begin, enable bandwidth on demand and configure its properties. See
Understanding Bandwidth on Demand on page 166.
Overview
Inthis example, youcreatethedl0dialer interfaceanddefinethebw-profileCHAPaccess
profile with the client1 and my-secret password. You configure CHAP on the dl0 unit 0
interfaces and specify a unique profile called bw-profile that contains client list and
access parameters. You configure the ACFC compression type. Finally, you configure a
bandwidth on demand on each ISDNinterface that is participating in the aggregated link
(in this case, the br-1/0/3 ISDN BRI physical interface).
Configuration
CLI Quick
Configuration
To quickly configure a bandwidth on demand, copy the following commands and paste
theminto the CLI:
[edit]
set interfaces dl0encapsulation multilink-ppp
Chapter 9: ISDN
set interfaces dl0unit 0dialer-options dial-string 4085550115 load-interval 90
load-threshold 95 pool bw-pool
set interfaces dl0unit 0compression rtp f-max-period 500queues q3
set interfaces dl0unit 0fragment-threshold 1024
set access profile bw-profile client client1 chap-secret my-secret
set interfaces dl0unit 0ppp-options chap access-profile bw-profile
set interfaces dl0unit 0ppp-options compression acfc
set interfaces dl0unit 0family inet address 172.20.10.2 destination 172.20.10.1
set interfaces dl0unit 0family inet negotiate-address
set interfaces dl0unit 0family inet unnumbered-address lo0.0destination 192.168.1.2
set interfaces br-1/0/3 dialer-options pool bw-pool
Step-by-Step
Procedure
Mode.
To configure a dialer interface for bandwidth on demand:
1. Select a dialer interface.
[edit]
2. Configure multilink properties on the dialer interface.
user@host# set encapsulation multilink-ppp
3. Select the logical unit.
4. Configure the dialer options.
user@host# set dialer-options dial-string 4085550115
user@host# set dialer-options load-interval 90
user@host# set dialer-options load-threshold 95
user@host# set dialer-options pool bw-pool
5. Configure unit properties.
user@host# set compression rtp f-max-period 500queues q3
6. Configure logical properties.
user@host# set fragment-threshold 1024
7. Define a CHAP access profile with a client and a secret password.
[edit]
user@host# set access profile bw-profile client client1 chap-secret my-secret
8. Configure CHAP on the dialer interface.
user@host# set ppp-options chap access-profile bw-profile
9. Configure packet compression.
user@host# set ppp-options compression acfc
10. Configure the dialer interface to be assigned an IP address. Choose any of the
following:
Assign source and destination IP addresses.
user@host#set family inet address 172.20.10.2 destination 172.20.10.1
Obtain an IP address fromthe remote end.
user@host#set family inet negotiate-address
Derive the source address and assign the destination address.
user@host#set family inet unnumbered-address lo0.0destination 192.168.1.2
11. For each ISDN interface that is participating in the aggregated link, configure
bandwidth on demand.
user@host# set ppp-options compression acfc
[edit]
br-1/0/3 {
dialer-options {
pool bw-pool;
}
}
dl0 {
encapsulation multilink-ppp;
unit 0 {
ppp-options {
chap {
access-profile bw-profile;
}
compression acfc;
}
fragment-threshold 1024;
compression {
rtp {
f-max-period 500;
queues q3;
}
}
family inet {
address 172.20.10.2/32 {
Chapter 9: ISDN
destination 172.20.10.1;
}
unnumbered-address lo0.0 destination 192.168.1.2;
negotiate-address;
}
dialer-options {
pool bw-pool;
dial-string 4085550115;
load-threshold 95;
load-interval 90;
}
}
}
Verification
Verifying a Bandwidth on Demand on page 170
Verifying a Bandwidth on Demand
Purpose Verify a bandwidth on demand.
Related
Documentation
Disabling ISDNProcesses (CLI Procedure)
The Junos OS ISDN signaling process manages ISDN signaling by initializing ISDN
connections. The Junos OS ISDN dialer services process manages dialing out through
dialer interfaces.
To disable the ISDN signaling process, use the following CLI statement:
[edit]
user@host: set systemprocesses isdn-signaling disable
To disable the dialer services process, use the following CLI statement:
[edit]
user@host# set systemprocesses dialer-services disable
CAUTION: Never disable a software process unless you are instructed to do
so by a Customer Support engineer.
Related
Documentation
Disabling ISDN Processes in the Junos OS Network Interfaces Configuration Guide
Verifying the ISDNConfiguration
To verify an ISDN configuration, performthe following tasks:
Displaying the ISDN Status on page 171
Verifying an ISDN BRI Interface on page 172
VerifyinganISDNPRI InterfaceandCheckingB-Channel InterfaceStatistics onpage173
Checking D-Channel Interface Statistics on page 174
Displaying the Status of ISDN Calls on page 176
Verifying Dialer Interface Configuration on page 177
Displaying the ISDNStatus
Purpose Display the status of ISDN service on the ISDN interface. For example, you can display
ISDNBRI status onthebr-6/0/0interfaceandISDNPRI status onthect1-2/0/0interface.
Action Fromoperational mode, enter the showisdn status command.
Sample Output user@host> showisdn status
Interface: br-6/0/0
Layer 1 status: active
Layer 2 status:
CES: 0, Q.921: up, TEI: 12
Layer 3 status: 1 Active calls
Switch Type : ETSI
Interface Type : USER
T310 : 10 seconds
Tei Option : Power Up
user@host> showisdn status
Interface: ct1-2/0/0
Layer 1 status: active
Layer 2 status:
CES: 0, Q.921: up, TEI: 0
Layer 3 status: 8 Active calls
Switch Type : NI2
Interface Type : USER
T310 : 10 seconds
Tei Option : Power Up
Chapter 9: ISDN
InterfaceISDN interface currently active on the device. For ISDN BRI, the interface is
a br-pim/0/port interface, as shown in the first example for br-6/0/0. For ISDN PRI,
the interface displayed is a channelized T1 or channelized E1 interface, as shown in the
second example for ct1-2/0/0.
Layer 1 statusIndicates whether Layer 1 is active or inactive.
Layer 2 statusIndicates whether Q.921 (the D-channel protocol) is up or down.
TEIAssigned terminal endpoint identifier (TEI) number.
Layer 3 statusNumber of active calls.
Switch TypeType of ISDN switch that is connected to the device interface.
Interface TypeDefault value for the local interface.
Calling numberTelephone number configured for dial-out.
T310Q.931-specific timer.
TEI OptionIndicates when TEI negotiations occur on the interface.
Verifying an ISDNBRI Interface
Purpose Verify that the ISDN BRI interface is correctly configured.
Action FromtheCLI, enter theshowinterfacesextensivecommand. Alternatively, fromtheJ-Web
interface, select Monitor>Interfaces>interface.
Sample Output user@host> showinterfaces br-6/0/0extensive
Physical interface: br-6/0/0, Enabled, Physical link is Up
Type: BRI, Link-level type: Controller, MTU: 4092, Clocking: 1, Speed: 144kbps,
Parent: None
Link type : Full-Duplex
Link flags : None
Physical info : S/T
Traffic statistics:
Input errors:
Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Giants: 0, Policed discards:
0,
Resource errors: 0
Output errors:
Carrier transitions: 0, Errors: 0, Drops: 0, MTU errors: 0, Resource errors:
0
The physical interface is Enabled. If the interface is shown as Disabled, do either of the
following:
interface-name] level of the configuration hierarchy.
In the J-Web configuration editor, clear the Disable check box on the
Interfaces>interface-name page.
Thetraffic statistics reflect theexpectedinput andoutput rates. Verify that thenumber
of inbound and outbound bytes and packets matches the expected throughput for the
interfaces statistics interface-name command.
Verifying an ISDNPRI Interface and Checking B-Channel Interface Statistics
Purpose Verify that an ISDN B-channel interface is operating properly. For ISDN PRI, verify that a
B-channel interface is configured correctly. (To display a list of B-channel interfaces,
enter the showisdn calls command.)
Action Fromoperational mode, enter the showinterfaces extensive command. Alternatively,
Fromthe J-Web interface, select Monitor>Interfaces>interface.
Sample Output user@host> showinterfaces bc-0/0/4:1 extensive
Physical interface: bc-0/0/4:1, Administratively down, Physical link is Up
Type: Serial, Link-level type: Multilink-PPP, MTU: 1510, Clocking: Internal,
Speed: 64kbps,
Parent: br-0/0/4 Interface index 143
Interface flags: Admin-Test SNMP-Traps 16384
Link flags : None
Physical info : Unspecified
Current address: Unspecified, Hardware address: Unspecified
Alternate link address: Unspecified
Last flapped : Never
Traffic statistics:
Input errors:
6,
Resource errors: 0
Output errors:
Chapter 9: ISDN
0
Queue counters Queued packets Transmitted Packets Dropped packets
0 best-effort 314335 0 0
1 best-effort 0 0 0
2 best-effort 5 0 0
Packet Forwarding Engine configuration:
Destination slot: 5, PLP byte: 1 (0x00)
CoS transmit queue Bandwidth Buffer Priority
Limit
% bps % usec
0 best-effort 95 60800 95 0 low
none
3 network-control 5 3200 5 0 low
none
Logical interface bc-0/0/4:1.0 (Index 71) (SNMP ifIndex 61) (Generation 33)
Flags: Device Down Point-To-Point SNMP-Traps Encapsulation: PPP
Protocol mlppp, Multilink bundle: dl0.0, MTU: 1506, Generation: 18, Route
table: 0
Meaning The output shows a summary of B-channel interface information. Verify the following
information:
following:
For ISDNBRI, theParent interfaceis abr-pim/0/port interfacebr-0/0/4inthis example.
For ISDN PRI, the Parent interface is a channelized T1 or channelized E1
interfacect1pim/0/port or ce1pim/0/port.
flapping indicates possible link-layer errors.
Checking D-Channel Interface Statistics
Purpose Verify that the ISDN D-channel interface is operating properly. For ISDN PRI, verify that
the D-channel interface is configured correctly.
Action Fromoperational mode, enter the showinterfaces extensive command. Alternatively,
Sample Output user@host> showinterfaces dc-0/0/4 extensive
Physical interface: dc-0/0/4, Enabled, Physical link is Up
Type: Serial, Link-level type: 55, MTU: 4092, Clocking: Internal, Speed: 16kbps,
Parent: br-0/0/4 Interface index 143
Link flags : None
Traffic statistics:
Input errors:
0,
Resource errors: 0
Output errors:
0
ISDN alarms : None
ISDN media: Seconds Count State
LOF 0 1 0K
LOS 0 0 0K
Logical interface dc-0/0/4.32767 (Index 70) (SNMP ifIndex 72) (Generation 8)
Flags: Point-To-Point SNMP-Traps Encapsulation: 60
Traffic statistics:
Input bytes : 13407
Output bytes : 82129
Input packets: 3262
Output packets: 3262
Local statistics:
Input bytes : 13407
Input packets: 3262
Meaning The output shows a summary of D-channel interface information. Verify the following
information:
following:
Chapter 9: ISDN
For ISDNBRI, theParent interfaceis abr-pim/0/port interfacebr-0/0/4inthis example.
For ISDN PRI, the Parent interface is a channelized T1 or channelized E1
interfacect1pim/0/port or ce1pim/0/port.
Displaying the Status of ISDNCalls
Purpose Display the status of ISDN calls. This information helps you to verify the dialer interface
configuration as described in Verifying Dialer Interface Configuration on page 177. The
command also provides a list of the B-channels configured on an ISDN BRI or ISDN PRI
interface.
Action Fromoperational mode, enter the showisdn calls command.
Sample Output user@host> showisdn calls
Interface: bc-6/0/0:1
Status: No call in progress
Most recent error code: No error
Status: Connected to 384070
Call Duration: 43 seconds
Call Direction: Dialout
user@host> showisdn calls
Call Direction: Dialin
Most recent error code: destination out of order
...
Meaning The output shows a summary of B-channel interfaces and the active ISDN calls on the
interfaces. The first example shows the two B-channels on an ISDN BRI
interfacebc-2/0/0:1 and bc-2/0/0:2. The second example indicates B-channels
bc-2/0/0:1 through bc-2/0/0:23, the 23 B-channels on an ISDNPRI interface. Determine
the following information:
The interfaces on which ISDN calls are in progress
Whether the call is a dial-in call, dial-out call, or a callback call
Verifying Dialer Interface Configuration
Purpose Verify that the dialer interface is correctly configured. To determine the ISDN interfaces
on which calls are taking place, see Displaying the Status of ISDN Calls on page 176.
Action Fromoperational mode, enter the showinterfaces dl0extensive command. Alternatively,
Sample Output user@host> showinterfaces dl0extensive
Physical interface: dl0, Enabled, Physical link is Up
Type: 27, Link-level type: PPP, MTU: 1504, Clocking: Unspecified, Speed:
Unspecified
Interface flags: SNMP-Traps
Traffic statistics:
Input errors:
0,
Resource errors: 0
Output errors:
0
Chapter 9: ISDN
Logical interface dl0.0 (Index 76) (SNMP ifIndex 28) (Generation 148)
Flags: Point-To-Point SNMP-Traps 0x4000 LinkAddress 23-0 Encapsulation: PPP
Dialer:
State: Active, Dial pool: 1
Dial strings: 384070
Subordinate interfaces: bc-6/0/0:2 (Index 172)
Watch list: 11.12.13.14/32
Activation delay: 0, Deactivation delay: 0
Initial route check delay: 120
Redial delay: 3
Callback wait period: 5
Load threshold: 0, Load interval: 60
Bandwidth: 64kbps
Traffic statistics:
Input bytes : 24839
Input packets: 489
Output packets: 340
Local statistics:
Input bytes : 10980
Input packets: 172
Output packets: 340
Transit statistics:
Keepalive statistics:
Input : 0 (last seen: never)
Output: 36 (last sent 00:00:09 ago)
LCP state: Opened
NCP state: inet: Opened, inet6: Not-configured, iso: Not-configured,
mpls: Not-configured
CHAP state: Success
Protocol inet, MTU: 1500, Generation: 74, Route table: 0
Flags: Negotiate-Address
Addresses, Flags: Kernel Is-Preferred Is-Primary
Destination: 43.1.1.2, Local: 43.1.1.19, Broadcast: Unspecified,
Generation: 37
user@host> showinterfaces dl0extensive
Physical interface: dl0, Enabled, Physical link is Up
Link-level type: LinkService, MTU: 1504
Interface flags: Point-To-Point SNMP-Traps
Last flapped : 2007-02-27 01:50:38 PST (1d 15:48 ago)
Traffic statistics:
Frame exceptions:
Oversized frames 0
Errored input frames 0
Input on disabled link/bundle 0
Output for disabled link/bundle 0
Queuing drops 0
Buffering exceptions:
Packet data buffer overflow 0
Fragment data buffer overflow 0
Assembly exceptions:
Fragment timeout 0
Missing sequence number 0
Out-of-order sequence number 0
Out-of-range sequence number 0
Hardware errors (sticky):
Data memory error 0
Control memory error 0
Egress queues: 8 supported, 8 in use
0 q1 6 6 0
1 q2 0 0 0
3 q3 0 0 0
Logical interface dl0.0 (Index 66) (SNMP ifIndex 36) (Generation 133)
Flags: Point-To-Point SNMP-Traps 0x4000 Encapsulation: Multilink-PPP
Dialer:
State: Active, Dial pool: 1
Dial strings: 384010
Subordinate interfaces: bc-2/0/0:8 (Index 161), bc-2/0/0:7 (Index 160),
bc-2/0/0:6 (Index 159), bc-2/0/0:5 (Index 158), bc-2/0/0:4 (Index 157),
bc-2/0/0:3 (Index 156), bc-2/0/0:2 (Index 155), bc-2/0/0:1 (Index 154)
Activation delay: 0, Deactivation delay: 0
Initial route check delay: 120
Redial delay: 3
Callback wait period: 5
Load threshold: 100, Load interval: 60
Bandwidth: 512kbps
Bundle options:
MRRU 1504
Remote MRRU 1504
Drop timer period 0
Inner PPP Protocol field compression enabled
Sequence number format long (24 bits)
Fragmentation threshold 0
Links needed to sustain bundle 1
Interleave fragments Disabled
Bundle errors:
Packet drops 0 (0 bytes)
Fragment drops 15827 (759696 bytes)
MRRU exceeded 0
Exception events 0
Statistics Frames fps Bytes bps
Bundle:
Fragments:
Input : 963116 0 50963104 0
Output: 6 0 540 0
Packets:
Input : 934346 0 42980144 0
Output: 6 0 504 0
Link:
Chapter 9: ISDN
bc-2/0/0:1.0
Input : 119656 0 6341806 0
Output: 1 0 90 0
bc-2/0/0:2.0
Input : 120176 0 6369366 0
Output: 1 0 90 0
bc-2/0/0:3.0
Input : 119856 0 6352368 0
Output: 1 0 90 0
bc-2/0/0:4.0
Input : 120315 0 6376695 0
Output: 0 0 0 0
bc-2/0/0:5.0
Input : 120181 0 6369593 0
Output: 0 0 0 0
bc-2/0/0:6.0
Input : 121154 0 6421200 0
Output: 0 0 0 0
bc-2/0/0:7.0
Input : 121181 0 6340321 0
Output: 0 0 0 0
bc-2/0/0:8.0
Input : 120594 0 6391482 0
Output: 0 0 0 0
NCP state: inet: Opened, inet6: Not-configured, iso: Not-configured, mpls:
Not-configured
Flags: None
Destination: 1.1.1.0/30, Local: 1.1.1.2, Broadcast: Unspecified,
Generation: 134
Meaning The output shows a summary of dialer interface information. The first example is for
ISDN BRI service, and the second example is for ISDN PRI service. Verify the following
information:
following:
Subordinate interfaces correctly lists the B-channel interface or interfaces associated
with this dialer interface. The ISDN BRI output in the first example shows that dl0
supports bc-6/0/0:2.
TheISDNPRI output inthesecondexampleshowsthat dl0supportsbc-2/0/0:1 through
bc-2/0/0:8.
The dialer state is Active when an ISDN call is in progress.
The LCP state is Opened when an ISDN call is in progress. An LCP state of Closed or
Not Configured indicates a problemwith the dialer configuration that needs to be
debugged with the monitor traffic interface interface-name command. For information
about the monitor traffic command, see the Junos OS Administration Guide for Security
Devices.
Related
Documentation
showisdn status in the Junos Interfaces Command Reference
showisdn calls in the Junos Interfaces Command Reference
showinterfaces in the Junos Interfaces Command Reference
Chapter 9: ISDN
CHAPTER 10
Voice over Internet Protocol with Avaya
This section contains the following topics:
Avaya VoIP Modules Overviewon page 183
Avaya VoIP Modules Configuration Overviewon page 185
Supported Avaya VoIP Modules and Interfaces on page 186
TGM550 Telephony Gateway Module Overviewon page 189
TIM508 Analog Telephony Interface Module Overviewon page 197
TIM510 E1/T1 Telephony Interface Module Overviewon page 201
TIM521 BRI Telephony Interface Module Overviewon page 215
Avaya IG550 Integrated Gateway Overviewon page 217
Media Gateway Controller Server Overviewon page 219
Avaya Communication Manager Software Overviewon page 220
Dynamic Call Admission Control Overviewon page 221
Configuring VoIP Interfaces with EPWand Disk-on-Key on page 222
Example: Configuring VoIP Interfaces on page 225
TGM550 Module Administration on page 234
TGM550 Module and VoIP Interface Troubleshooting on page 237
Avaya VoIP Modules Overview
J2320, J2350, J4350, andJ6350Services Routers support voiceover IP(VoIP) connectivity
for branchoffices withthe AvayaIG550IntegratedGateway. The AvayaIG550Integrated
Gateway consists of four VoIP modulesa TGM550 Telephony Gateway Module and
three types of Telephony Interface Modules (TIMs).
The VoIP modules installed in a Services Router at a branch office connect the IP and
analog telephones and trunk lines at the branch to headquarters and to the
public-switched telephone network (PSTN).
Figure 9on page 184shows a typical VoIPtopology. The small branch office shown in the
expandedillustrationontheright is connectedover thecorporateWANtotheheadoffice
throughaJ6300Services Router withVoIPmodules installed. The AvayaMediaGateway
Controller, S8700 Media Server, and integrated Management tools at the head office
manage telephony services for headquarters and the branch offices on the WAN,
connecting the corporation's legacy analog telephones, VoIP telephones, PCs, and fax
machines to the PSTN.
Figure 9: Typical VoIP Topology
You must assign a local IP address to the vp-pim/0/0 interface on the Services Router
and also a destination IP address to the TGM550 so that they can communicate with
each other.
The following rules apply for configuring the source IPv4 address:
You cannot specify more than one IPv4 address.
Do not assign the following IPv4 addresses:
A broadcast address (255.255.255.255)
A class E address (240.0.0.0 to 255.255.255.254)
A loopback address (127.0.0.0 to 127.255.255.255)
A multicast address (224.0.0.0 to 239.255.255.255)
An address with 0 as the first byte or an address with 0 or 255 as the last byte
The VoIP interface needs a point-to-point connection to the TGM550. To configure
the point-to-point connection, specify /32 as the subnet mask in the IPv4 address.
The TGM550 uses the destination IP address to identify itself when communicating
with other devices, particularly the Media Gateway Controller (MGC).
CAUTION: Applying a newor modified IP address resets the TGM550. For
existing configurations, ensure that the TGM550 configuration is saved
(seeSavingtheTGM550ModuleConfiguration onpage237) andthat the
TGM550 module is carrying no voice traffic.
To provide telephony services, the TGM550 must be registered with at least one Media
Gateway Controller (MGC). You can configure the IP addresses of up to four MGCs that
the TGM550 can connect to in the event of a link failure. In addition to configuring the
MGC list fromJ-Web and the CLI, you can log in to the TGM550 and configure the list.
Related
Documentation
Understanding the TGM550 Telephony Gateway Module on page 189
Understanding the TIM508 Analog Telephony Interface Module on page 197
Understanding the TIM510 E1/T1 Telephony Interface Module on page 201
Understanding the TIM521 BRI Telephony Interface Module on page 215
Avaya VoIP Modules Configuration Overview
You can use either J-Web or the CLI configuration editor to configure VoIP. Alternatively,
you can download a complete router configuration that includes VoIPfroman Electronic
Preinstallation Worksheet (EPW) and a disk-on-key USB memory stick.
The Avaya VoIPmodules are installedin a J Series chassis like Physical Interface Modules
(PIMs), but they are controlled by Avaya Communication Manager software rather than
the Junos OS.
CAUTION: PIMs and VoIP modules are not hot-swappable. You must power
off the Services Router before removing or inserting a PIMor VoIP module.
Ensure that the PIMs and VoIP modules are installed in the router chassis
before booting up the system.
Chapter 10: Voice over Internet Protocol with Avaya
CAUTION: The grounding cable for J Series devices must be, at minimum, 14
AWGcable.
On each J Series device with Avaya VoIP, a single TGM550 Telephony Gateway Module
(TGM) and at least one telephony interface module (TIM) is required. No more than four
TIMs of any kind can be installed on a single chassis.
CAUTION: Do not install a combination of PIMs in a single chassis that
exceeds the maximumpower and heat capacity of the chassis. If power
management is enabled, PIMs that exceed the maximumpower and heat
capacity remain offline for a J Series device when the chassis is powered on.
Related
Documentation
Supported Avaya VoIP Modules and Interfaces
J2320, J2350, J4350, and J6350 Services Routers support VoIP connectivity for branch
offices with the Avaya IG550 Integrated Gateway.
Avaya VoIP Modules Summary
The following sections describe the supported Avaya VoIP modules and interfaces:
J2320 and J2350 Avaya VoIP Module Summary on page 186
J4350 and J6350 Avaya VoIP Module Summary on page 187
J2320and J2350Avaya VoIP Module Summary
Table 17 on page 187 provides the module names, slot and port numbers, maximum
number allowed on a chassis, and sample interface names (where applicable) for the
J2320 and J2350 Avaya VoIP modules.
Table 17: J2320and J2350Avaya VoIP Module Summary
Sample Interface
Name
(type-pim/0/port)
MaximumNumber on a
Chassis
Slot and Port
Numbering Also Called PIMName
vp-3/0/0 One (required)
If more than one TGM550 is
installed, only the one in the
lowest numbered slot is
enabled. For example, if
TGM550sareinstalledinslots
2 and 3, only the one in slot 2
is enabled.
J2320Slots 1
through 3
J2350Slots 1
through 5
TGM550GatewayModule
TGM550
TGM550
Telephony
Gateway Module
One on J2320
Three on J2350
J2320Slots 1
through 3
J2350Slots 1
through 5
TIM508 media module
TIM508
TIM508 Analog
Telephony
Interface Module
Two J2320Slots 1
through 3
J2350Slots 1
through 5
TIM510 E1/T1 media
module
TIM510
TIM510 E1/T1
Telephony
Interface Module
Two J2320Slots 1
through 3
J2350Slots 1
through 5
TIM514 analog media
module
TIM514
TIM514 Analog
Telephony
Interface Module
One on J2320
Three on J2350
J2320Slots 1
through 3
J2350Slots 1
through 5
TIM516 analog media
module
TIM516
TIM516 Analog
Telephony
Interface Module
One on J2320
Three on J2350
J2320Slots 1
through 3
J2350Slots 1
through 5
TIM518 analog media
module
TIM518
TIM518 Analog
Telephony
Interface Module
Two J2320Slots 1
through 3
J2350Slots 1
through 5
TIM521 BRI mediamodule
TIM521
TIM521 BRI
Telephony
Interface Module
J4350and J6350Avaya VoIP Module Summary
Table 18 on page 188 provides the module names, slot and port numbers, maximum
number allowed on a chassis, and sample interface names (where applicable) for the
J4350 and J6350 Avaya VoIP modules.
Table 18: J4350and J6350Avaya VoIP Module Summary
Sample Interface
Name
(type-pim/0/port)
MaximumNumber on
a Chassis
Slot and Port
Numbering Also Called PIMName
vp-3/0/0 One (required)
If more than one
TGM550 is installed,
only the one in the
lowest numbered slot is
enabled. For example, if
TGM550s are installed
in slots 2 and 3, only the
one in slot 2 is enabled.
Slots 1 through 6 TGM550
Gateway
Module
TGM550
TGM550
Telephony
Gateway
Module
Three Slots 1 through 6 TIM508 media
module
TIM508
TIM508
Analog
Telephony
Interface
Module
Two Slots 1 through 6 TIM510 E1/T1
media module
TIM510
TIM510 E1/T1
Telephony
Interface
Module
Four Slots 1 through 6 TIM514 analog
media module
TIM514
TIM514
Analog
Telephony
Interface
Module
Three Slots 1 through 6 TIM516 analog
media module
TIM516
TIM516
Analog
Telephony
Interface
Module
Three Slots 1 through 6 TIM518 analog
media module
TIM518
TIM518
Analog
Telephony
Interface
Module
Two Slots 1 through 6 TIM521 BRI
media module
TIM521
TIM521 BRI
Telephony
Interface
Module
Related
Documentation
TGM550Telephony Gateway Module Overview
TGM550 Access Requirements on page 192
TGM550 Console Port Pinouts on page 193
TGM550 RJ-11 Connector Pinout for Analog Ports on page 194
TGM550 MaximumMedia Gateway Capacities on page 195
TGM550 LEDs on page 197
Understanding the TGM550Telephony Gateway Module
The TGM550 Telephony Gateway Module (Figure 10 on page 190), also known as the
TGM550 Gateway Module, has two analog telephone ports, two analog trunk ports, and
a serial console port. A TGM550 and one or more TIMs installed in a Services Router
provide telephony exchange services to a branch office over IP networks. Different TIMs
have access ports for different types of VoIPand analog telephones and telephone lines.
You connect the telephones and lines to the ports on the TGM550 and the TIMs. VoIP
telephones require connection to a Power over Ethernet (PoE) adapter or switch that is
plugged into an Ethernet port on the Services Router.
VoIP capabilities on the TGM550 enable the Services Router to provide VoIP services to
telephones and trunks that do not directly support VoIP. The TGM550 translates voice
and signaling data between VoIP and the systemused by the telephones and trunks.
TIMs convert the voice path of traditional circuits such as analog trunk and T1 or E1 to a
TDMbus inside the router. The TGM550 then converts the voice path fromthe TDMbus
to compressed or uncompressed and packetized VoIP on an Ethernet connection.
Figure 10: TGM550Telephony Gateway Module
TGM550Guidelines and Features
TGM550 Firmware Compatibility with Junos OS on page 190
TGM550 IP Addressing Guidelines on page 190
TGM550 Features on page 191
TGM550 Firmware Compatibility with Junos OS
The TGM550 firmware version must be compatible with the Junos OS version installed
on the device.
CAUTION: If the TGM550firmware version is not compatible with the Junos
OS version on the device, the device does not detect the VoIP interface
(vp-pim/0/0) and the interface is unavailable. For more information, see
TGM550 Module and VoIP Interface Troubleshooting on page 237.
If you are upgrading both the TGM550 firmware and the Junos OS on the router, first
upgrade the TGM550 firmware, and then upgrade the Junos OS.
TGM550 IP Addressing Guidelines
For operational purposes, the TGM550 is identified as a host on the device. Hence, the
TGM550 needs to be assigned an IP address that is reachable both externally and
internally fromthe device. The TGM550 uses this IP address to identify itself when
communicating with other devices, particularly the Media Gateway Controller (MGC).
To assign the IP address for the TGM550, you configure the destination address on the
vp-pim/0/0 interface.
CAUTION: Applyinganewor modifiedIPaddress resets theTGM550. Before
modifying the IP address, take the following precautions:
Log into the TGM550 and enter copy running-config startup-config to save
theTGM550configuration. (For logininstructions, seeSavingtheTGM550
Module Configuration on page 237)
Ensure that the TGM550 is not currently handling voice traffic.
To enable easier administration of the TGM550, we recommend the following guidelines
for assigning the IP address of the TGM550:
Assign an address fromone of the subnets that is already configured in the branch
office where the device is installed.
Decide on a block of IPaddresses for VoIPservices, and assign an IPaddress fromthat
block to the TGM550.
Do not assign the following IP addresses to the TGM550:
A broadcast address (255.255.255.255)
A class E address (240.0.0.0 to 255.255.255.254)
A loopback address (127.0.0.0 to 127.255.255.255)
A multicast address (224.0.0.0 to 239.255.255.255)
An address with 0 as the first byte or an address with 0 or 255 as the last byte
TGM550 Features
The TGM550 provides the following features:
Voice
VoIP Media Gateway services.
Two analog telephone (LINE) ports to support two analog telephones or incoming
analog direct inward dialing (DID) trunks with either wink start or immediate start.
An analog relay supports emergency transfer relay (ETR).
Two analog trunk (TRUNK) ports to support loop start, ground start, centralized
automatic message accounting (CAMA), and direct inward and outward dialing
(DIOD) trunks (for Japan only).
Survivability features for continuous voice services.
Call center capabilities.
Provisioning
Avaya Communication Manager (CM) media server management.
Extensive alarmand troubleshooting features.
Survivability
Media Gateway Controller (MGC) automatic switchover, migration, and survivability
features.
Modembackup connection to the MGC.
Dynamic call admission control (CAC) for WAN interfaces.
Management: One serial port for console access over an RJ-45 connector cable.
NOTE: The RJ-45 console cable and DB-9 adapter supplied with the
TGM550 are different fromthose supplied with the Services Router. You
cannot use the RJ-45 cable and DB-9 adapter supplied with the Services
Router for console connections to the TGM550.
Related
Documentation
Hardware Description and Reference for Avaya Communication Manager at
http://support.avaya.com
SystemCapacities Table for Avaya Communication Manager on Avaya Media Servers at
Communication Manager Software &Firmware Compatibility Matrix at
Administration Guide and CLI Reference for the Avaya IG550 Integrated Gateway at
TGM550Access Requirements
The CLI on the TGM550allows you to configure, monitor, and diagnose the TGM550and
TIMs installed in a Services Router. You can access the TGM550 froma management
deviceattachedtotheTGM550consoleport or by openingaTelnet or secureshell (SSH)
session fromthe Junos OS CLI on the Services Router.
YoucanalsoopenaremoteTelnet or SSHsessiondirectly totheTGM550fromanetwork
location, or indirectly through the Junos OS CLI froma dial-up connection with a USB
modemattached to the router.
Administrators can use the root password to access the TGM550 initially, but all users
need a TGM550 user account (username and password) set up by the network
administrator for regular access to the module.
NOTE: Youcannot useaServicesRouter user account toaccesstheTGM550
CLI.
A console connection requires the Ethernet rollover cable and adapter provided with
the TGM550.
An SSH connection requires that the TGM550 have an IP address assigned.
A Telnet connection to the TGM550 requires that the module have an IP address and
that Telnet service be enabled on the module.
Related
Documentation
TGM550Console Port Pinouts
The console port on a TGM550 Telephony Gateway Module has an RJ-45 connector.
Table 19 on page 193 provides TGM550 RJ-45 console connector pinout information. An
RJ-45 cable is supplied with the TGM550.
NOTE: Two different RJ-45 cables and RJ-45 to DB-9adapters are provided.
Do not use the RJ-45 cable and adapter for the Services Router console port
to connect to the TGM550 console port.
To connect the console port to an external management device, you need an RJ-45 to
DB-9 serial port adapter, which is also supplied with the TGM550.
Table 19: TGM550RJ-45 Console Connector Pinouts
Terminal DB-9 Pin Signal
TGM550 RJ-45
Pin
NC For future use 1
3 TXD (TGM550 input) 2
2 RXD (TGM550 output) 3
4 CD 4
Table 19: TGM550RJ-45 Console Connector Pinouts (continued)
Terminal DB-9 Pin Signal
TGM550 RJ-45
Pin
5 GND 5
1 DTR 6
8 RTS 7
7 CTS 8
Related
Documentation
TGM550RJ-11 Connector Pinout for Analog Ports
The two analog telephone ports and two analog trunk ports on the TGM550use an RJ-11
cable. Table 20 on page 194 describes the TGM550 RJ-11 connector pinout.
Table 20: TGM550RJ-11 Connector Pinout
Signal Pin
No connection 1
No connection 2
Ring 3
Tip 4
No connection 5
No connection 6
Related
Documentation
TGM550MaximumMedia Gateway Capacities
Table 21 on page 195 lists the maximumnumber of media servers, telephones, and so on
that are supported by the TGM550 installed on a J4350, J6350, J2320, or J2350 device.
Table 21: TGM550MaximumMedia Gateway Capacities
Additional Information TGM550 MaximumCapacity Hardware or Feature
This number also applies if a combination of
Avaya G700 Media Gateways, G250 Media
Gateways, and G350 Media Gateways are
controlled by the same media server.
250 TGM550s that can be controlled by
an Avaya S8500 or S8700 Media
Server
This number also applies if a combination of
Avaya G700 Media Gateways, G250 Media
Gateways, and G350 Media Gateways are
controlled by the same media server.
an Avaya S8400 Media Server
This capacity is 50 if a combination of Avaya
G700 Media Gateways, G250 Media Gateways,
and G350Media Gateways are controlled by the
same media server.
TheS8300must resideinaG700or G350media
gateway. Therefore, the maximumof 50 H.248
gateways supported by the S8300 means that
only 49 of the 50 can be TGM550s.
an Avaya S8300 Media Server
If an MGC becomes unavailable, the TGM550
uses the next MGC on the list. The built-in SLS
module can be considered a fifth MGC, although
its functionality is limitedfromthat of afull-scale
media server.
4 Mediaservers that canberegistered
as Media Gateway Controllers
(MGCs) on a TGM550
2 Fixed analog line ports
2 Fixed analog trunk ports
Table 21: TGM550MaximumMedia Gateway Capacities (continued)
Additional Information TGM550 MaximumCapacity Hardware or Feature
For calls using voice codec sets with 20 ms or
higher packet sizes, the DSP supports:
80 channels
20 channels
10 channels
For calls with 10 ms or lower packet sizes, the
80channel DSP supports 40 channels.
For TTY, fax, or modemover IP calls, the
80channel DSP supports 40 channels.
1 (up to 80 channels) Digital signal processors (DSPs)
800 Busy hour call completion rate
(BHCC)
Maximumincludes a combination of analog and
IP telephones
70 (J4350)
100 (J6350)
Total of IP and analog telephones
that canbeconnectedtoaTGM550
and TIMs
Receivers 32 Touch-tone recognition (TTR)
As much as necessary for all TDM
calls.
Tone generation
16 playback channels for playing
announcements, one of which can
be used for recording.
20 minutes for G711-quality stored
announcements andmusic-on-hold.
256 maximumannouncements
stored.
Announcements (VAL)
Related
Documentation
TGM550LEDs
TGM550LEDs indicatelinkstatus andactivity. Table22onpage197describes themeaning
of the LEDs.
Table 22: LEDs for TGM550Gateway Module
Description State Color Label
Alarm. A failure in the TGM550
requiresmonitoringor maintenance.
On steadily Red ALM
Active. The TGM550 is online with
network traffic.
On steadily Yellow ACT
Alternate software bank. The
software is not running fromthe
selected boot bank.
On steadily Green ASB
Emergency transfer relay (ETR)
feature is active.
On steadily Green ETR
Related
Documentation
TIM508 Analog Telephony Interface Module Overview
TIM508 Connector Pinout on page 198
TIM508 Possible Port Configurations on page 200
TIM508 LEDs on page 200
Understanding the TIM508 Analog Telephony Interface Module
The TIM508 Analog Telephony Interface Module (Figure 11 on page 198), also known as
the TIM508 Analog Media Module, has eight analog telephone lines that can be used as
trunk ports.
Figure 11: TIM508 Analog Telephony Interface Module
g
0
0
3
8
6
5
ACT
1 8
TIM 508
ALM
Analog
LINES
NOTE: All eight analoglines canbeconfiguredas analogdirect inwarddialing
(DID) trunks.
The TIM508 provides the following features:
Three ringer loads, the ringer equivalency number for up to 2,000 ft (610 m), for all
eight lines
Up to eight simultaneously ringing lines
Type 1 caller ID and Type 2 caller ID for lines
Ring voltage generation for a variety of international frequencies and cadences
Related
Documentation
TIM508 Connector Pinout
The TIM508 Analog Telephony Interface Module uses a B25A unshielded 25pair
Amphenol cable. Table 23 on page 199 describes the TIM508 connector pinout.
Table 23: TIM508 Connector Pinout
Signal Pin
Tip 1
Tip 2
Tip 3
Tip 4
Tip 5
Tip 6
Tip 7
Tip 8
R - Receive 26
Ring 27
Ring 28
Ring 29
Ring 30
Ring 31
Ring 32
Ring 33
Related
Documentation
TIM508 Possible Port Configurations
You can configure TIM508 ports as described in Table 24 on page 200.
Table 24: TIM508 Possible Port Configurations
Possible Analog Telephone Line Configurations
Wink-start or immed-start DID trunk
Analog tip/ring devices such as single-line telephones with or without LED message-waiting indication
Related
Documentation
TIM508 LEDs
TIM508LEDsindicatelinkstatusandactivity. Table25onpage200describesthemeaning
of the LEDs.
Table 25: LEDs for TIM508
Alarm. A TIM508 failure requires
monitoring or maintenance.
On steadily Red ALM
Active. A device connected to the
TIM508 is in use. This situation can
include a telephone that is off the
hook.
Blinking Yellow ACT
Related
Documentation
TIM510E1/T1 Telephony Interface Module Overview
TIM510 RJ-45 Connector Pinout on page 202
Understanding the TIM510E1/T1 Telephony Interface Module
The TIM510E1/T1 Telephony Interface Module (Figure 12 on page 201), also known as the
TIM510E1/T1 mediamodule, terminates anE1 or T1 trunk. TheTIM510T1/E1 mediamodule
has a built-in channel service unit (CSU) so an external CSU is not necessary. The CSU
is used for a T1 circuit only. Up to two TIM510s can be installed in any of the slots on the
Services Router.
Figure 12: TIM510E1/T1 Telephony Interface Module
The TIM510 provides the following key features:
One E1 or T1 trunk port with up to 30 channels on an E1 port and 24 channels on a T1
port.
DS1-level support for a variety of E1 and T1 trunk types.
Trunk signaling to support U.S. and international central office (CO) or tie trunks.
Echo cancellation in either directionincoming or outgoing.
Related
Documentation
TIM510RJ-45 Connector Pinout
The TIM510 Telephony Interface Module uses an RJ-45 cable. Table 26 on page 202
describes the TIM510 RJ-45 connector pinout.
Table 26: TIM510RJ-45 Connector Pinout
Signal Pin
Ring 1
Tip 2
No connection 3
R1 - Transmit 4
T1 - Transmit 5
No connection 6
No connection 7
No connection 8
Related
Documentation
TIM510LEDs
TIM510LEDs indicatelink status andactivity. Table27 onpage203describes themeaning
of the LEDs.
On steadily Red ALM
Active. The TIM510 is online with
network traffic.
On steadily Green ACT
Test. A test is being performed on
the TIM510 through the Media
Gateway Controller (MGC).
On steadily Yellow TST
Signal. The link to the central office
(CO) is active.
On steadily Green SIG
Related
Documentation
the TIM514analog media module, has four analog telephone ports andfour analog trunk
ports.
NOTE: For analog direct inward dialing (DID) trunks, you must use the four
analogtelephone(LINE) ports. Youcannot usethefour analogtrunk(TRUNK)
ports for analog DID trunks.
Three ringer loads, the ringer equivalency number for up to 2,000 ft (610 m), for all
eight ports.
Up to four simultaneously ringing ports.
Type 1 caller ID and Type 2 caller ID.
Ring voltage generation for a variety of international frequencies and cadences.
Related
Documentation
The TIM514 Telephony Interface Module uses an RJ-11 cable. Table 28 on page 205
describes the TIM514 RJ-11 connector pinout information.
Table 28: TIM514 RJ-11 Connector Pinout
Signal Pin
No connection 1
No connection 2
Ring 3
Tip 4
No connection 5
No connection 6
Related
Documentation
You can configure TIM514 ports as described in Table 29 on page 205.
Possible Analog Trunk (TRUNK) Port Configurations
Possible Analog Telephone (LINE) Port
Configurations
Loop-start or ground-start central office trunk with a loop current of
18 to 120 mA.
Wink-start or immediate-start DID trunk
Table 29: TIM514 Possible Port Configurations (continued)
Possible Analog Trunk (TRUNK) Port Configurations
Possible Analog Telephone (LINE) Port
Configurations
Two-wireanalogoutgoingcentralizedautomaticmessageaccounting
(CAMA) emergency E911 trunk, for connectivity to the PSTN.
Multifrequency (MF) signaling is supported for CAMA ports.
Analog tip/ring devices such as single-line telephones
with or without LED message-waiting indication
Related
Documentation
TIM514 LEDs
TIM514LEDs indicatelinkstatus andactivity. Table30onpage206describes themeaning
of the LEDs.
On steadily Red ALM
hook.
Blinking Yellow ACT
Related
Documentation
the TIM516 analog media module, has 16 analog telephone lines.
6 1 5 M I T
A T C
S E N I L
S E N I L
7 1
4 2
1 8
M L A
g o l a n A
6
6
8
3
0
0
g
S E N I L
Three ringer loads, the ringer equivalency number for up to 2,000 ft (610 m), for all 16
lines
Up to 16 simultaneously ringing lines
Type 1 caller ID and Type 2 caller ID for line lines
Related
Documentation
Signal Pin
Tip 1
Tip 2
Tip 3
Tip 4
Tip 5
Tip 6
Tip 7
Tip 8
Tip 17
Tip 18
Tip 19
Tip 20
Tip 21
Tip 22
Tip 23
Tip 24
Table 31: TIM516 Connector Pinout (continued)
Signal Pin
Ring 26
Ring 27
Ring 28
Ring 29
Ring 30
Ring 31
Ring 32
Ring 33
Ring 42
Ring 43
Ring 44
Ring 45
Ring 46
Ring 47
Ring 48
Ring 49
Related
Documentation
You can configure TIM516 lines as described in Table 32 on page 210.
Possible Analog Telephone (LINE) Line Configurations
Analog tip/ring devices such as single-line telephones with or without LED message-waiting indication
Related
Documentation
TIM516 LEDs
TIM516LEDs indicatelinkstatus andactivity. Table33onpage210describes themeaning
of the LEDs.
On steadily Red ALM
hook.
Blinking Yellow ACT
Related
Documentation
the TIM518 analog media module, has eight analog telephone lines and eight analog
trunk lines.
ACT
LINES
LINES
17 24
1 8
TIM 51 8
ALM
Analog
g
0
0
3
8
6
7
NOTE: For analog direct inward dialing (DID) trunks, you can use all eight
analog telephone lines.
Three ringer loads, the ringer equivalency number for up to 2,000 ft (610 m), for all 16
lines
Up to 16 simultaneously ringing lines
Type 1 caller ID and Type 2 caller ID for line lines
Type 1 caller ID for trunk lines
Related
Documentation
Signal Pin
Ring 1
Ring 2
Ring 3
Ring 4
Ring 5
Ring 6
Ring 7
Ring 8
Ring 17
Ring 18
Ring 19
Table 34: TIM518 Connector Pinout (continued)
Signal Pin
Ring 20
Ring 21
Ring 22
Ring 23
Ring 24
Tip 26
Tip 27
Tip 28
Tip 29
Tip 30
Tip 31
Tip 32
33
Tip 42
Tip 43
44
Tip 45
Tip 46
Tip 47
Tip 48
Tip 49
Related
Documentation
You can configure eight TIM518 analog telephone lines as described in Table 35 on
page 214.
Possible Analog Trunk Port Configurations Possible Analog Telephone Port Configurations
Loop-start or ground-start central office trunk with a loop
current of 18 to 120 mA
Wink-start or immed-start DID trunk
Two-wire analog outgoing centralized automatic message
accounting (CAMA) emergency E911 trunk for connectivity to
the PSTN
Analog tip or ring devices such as single-line telephones with
or without LED message-waiting indication
Related
Documentation
TIM518 LEDs
TIM518LEDs indicatelink status andactivity. Table36onpage215describes themeaning
of the LEDs.
On steadily Red ALM
hook.
Blinking Yellow ACT
Related
Documentation
TIM521 BRI Telephony Interface Module Overview
Understanding the TIM521 BRI Telephony Interface Module
The TIM521 BRI Telephony Interface Module (Figure 16 on page 216), also known as the
TIM521 BRI media module, has four ports with RJ-45 jacks that can be administered as
ISDNBasicRateInterface(BRI) trunkconnections. EachISDNBRI port hastwoB-channels
plus a D-channel. Up to two TIM521 modules (with four BRI trunk ports each) can be
installed in any of the slots on the Services Router.
Figure 16: TIM521 BRI Telephony Interface Module
For ISDNBRI trunking, the TIM521 supports up to four BRI interfaces to the central office
at the ISDN T reference point. Information is communicated on each port in two ways:
Over two 64-Kbps B-channels, called B1 and B2, that can be circuit-switched
simultaneously.
NOTE: The TIM521 does not support BRI stations or combining both
B-channels together to forma 128-Kbps channel.
Over a 16-Kbps channel, called the D-channel, that is used for signaling. The TIM521
occupies one time slot for all four D-channels.
The circuit-switched connections have an a-lawor mu-lawoption for voice operation.
The circuit-switched connections operate as 64-Kbps clear channels transmitting data.
Related
Documentation
TIM521 LEDs
TIM521 LEDs indicate link status andactivity. Table 37 onpage 216describes the meaning
of the LEDs.
On steadily Red ALM
Table 37: LEDs for TIM521 (continued)
Active. A trunk connected to the
TIM521 is in use.
On steadily Yellow ACT
Related
Documentation
Avaya IG550Integrated Gateway Overview
The Avaya IG550 Integrated Gateway consists of the TGM550 Telephony Gateway
Module and one or more Telephony Interface Modules (TIMs) that are installed in the
slots ontheJ4350andJ6350Services Routers toprovideVoIPconnectivity. TheTGM550
is an H.248 media gateway that works with the TIMs to connect IP and legacy analog
telephones and trunks over IP networks and enable IP telephones to communicate
through analog telephone lines and trunks.
The TGM550 is also connected over a LAN or WAN to a Media Gateway Controller
(MGC)an Avaya media server running Avaya Communication Manager (CM) call
processing software. The telephony services on the TGM550 are managed by an MGC
located at headquarters or in a branch office. When the primary MGC is located at a
remote location, the TGM550 uses standard local survivability (SLS) for partial MGC
backup in the event that the connection to the primary MGC is lost. Devices can thereby
provide reliable telephony services to branch offices.
Four types of VoIPinterfaces on Avaya VoIPmodules provide VoIPconnectivity on J4350
and J6350 Services Routers:
Analog telephone or trunk port
T1 port
E1 port
ISDN BRI telephone or trunk port
These interfaces are available on the field-replaceable Avaya VoIP modules listed in
Table 38 on page 218.
Table 38: Interfaces on Avaya VoIP Modules
Junos OS Interface
(type-pim/0/port) VoIP Interfaces Description Module Name
vp-pim/0/0
On a VoIP interface, the port is
always 0.
Twoanalogtelephoneports
Two analog trunk ports
One serial port for console
access
Avaya Telephony Gateway
Module (TGM). See
Understanding the TGM550
TelephonyGatewayModule on
page 189.
TGM550
One E1/T1 trunk port providing
up to 30 E1 or 24 T1 channels
Avaya E1/T1 Telephony
Interface Module (TIM). See
Understanding the TIM510
E1/T1 Telephony Interface
Module on page 201.
TIM510
Four analogtelephoneports
Four analog trunk ports
Avaya Analog TIM. See
Understanding the TIM514
Analog Telephony Interface
Module on page 204.
TIM514
Four ISDN BRI trunk ports
providing up to eight channels
Avaya BRI TIM. See
Understanding the TIM521 BRI
Telephony InterfaceModule on
page 215.
TIM521
Only the TGM550has aJunos OSinterface. Because the TIMs donot have corresponding
physical interfaces, you cannot configure or administer themwith the J-Web interface
or the Junos OS CLI. However, you can display TGM550 and TIMstatus fromJ-Web
Monitor>Chassis pages and with the CLI showchassis command.
CAUTION: The TGM550 and TIMs are not hot-swappable. You must power
off the router before installing or removing the Avaya VoIP modules. Ensure
that theAvayaVoIPmodules areinstalledintherouter chassis beforebooting
up the system.
Related
Documentation
Media Gateway Controller Server Overview
A Media Gateway Controller (MGC) is a media server (call controller) that controls
telephoneservices ontheTGM550. AnAvayamediaserver runningAvayaCommunication
Manager (CM) software acts as an MGC for the TGM550.
The following media servers running Avaya Communication Manager can be used as an
MGC with the TGM550:
Avaya S8300 Media ServerControls up to 49 TGM550s.
To provide telephony services, the TGM550 must be registered with at least one Media
Gateway Controller (MGC). You can configure the IP addresses of up to four MGCs that
the TGM550 can connect to in the event of a link failure. The MGC list consists of the IP
addresses of the MGCs to connect to andthe order in which to reestablish the H.248link.
The first MGCon the list is the primary MGC. The TGM550searches for the primary MGC
first. If it cannot connect to the primary MGC or loses its connection to the primary MGC,
it attempts to connect to the next MGC in the list, and so on.
NOTE: The MGC list is stored in the TGM550. It is not written to the Junos
OS configuration file.
You must also administer Avaya Communication Manager on the configured Media
Gateway Controllers to support the TGM550. For more information, see the following
Avaya IG550 Integrated Gateway manuals at http://support.avaya.com:
Installing and Configuring the Avaya IG550 Integrated Gateway
Administration Guide and CLI Reference for the Avaya IG550 Integrated Gateway
Administrator Guide for Avaya Communication Manager
Avaya Maintenance Procedures for Communication Manager, Media Servers, and Media
Gateways
Avaya Maintenance Commands for Communication Manager, Media Servers, and Media
Gateways
Avaya Maintenance Alarms for Communication Manager, Media Servers, and Media
Gateways
Hardware Description and Reference for Avaya Communication Manager
SystemCapacities Table for Avaya Communication Manager on Avaya Media Servers
Related
Documentation
Avaya Communication Manager Software Overview
Avaya Communication Manager (CM) software manages the Media Gateway Controller
(MGC). Avaya CMallows you to do the following:
Assign numbers to local telephones.
Determine where to connect your telephone call based on the number you dial.
Play dial tones, busy signals, and prerecorded voice announcements.
Allowor prohibit access to outside lines for specific telephones.
Assign telephone numbers and buttons to special features.
Exchangecall switchinginformationwitholder telephoneswitches that donot support
VoIP.
NOTE: TheTGM550supports AvayaCommunicationManager (CM) release
4.0andlater releases. The TGM550does not support AvayaCommunication
Manager (CM) releases earlier than release 4.0.
Related
Documentation
Administrator Guide for Avaya Communication Manager at http://support.avaya.com
Dynamic Call Admission Control Overview
Dynamic call admission control (CAC) enables the Media Gateway Controller (MGC) to
automatically assign the bandwidth available for voice traffic on WAN interfaces and
block newcalls when the existing call bandwidth is completely engaged. You configure
dynamicCAConahigh-bandwidthprimaryinterfaceandononeor morebackupinterfaces
with less bandwidth.
Without dynamic CAC, the MGC cannot detect the switchover to the backup link or the
resulting changes in network topology and available bandwidth. As a result, the MGC
continues toadmit calls at thebandwidthof theprimarylink, causingnetworkcongestion
and possible jitter, delay, and loss of calls.
Dynamic CAC Interface Requirements
Supported Interfaces on page 221
Bearer Bandwidth Limit and Activation Priority on page 221
Rules for Determining Reported BBL on page 222
Supported Interfaces
Dynamic CAC must be configured on each Services Router interface responsible for
providing call bandwidth. You can configure dynamic CAC on the following types of
interfaces on Services Routers:
ADSL
E1
E3
Fast Ethernet
Gigabit Ethernet
GRE
G.SHDSL
ISDN BRI
Serial interfaces
T1
T3
Bearer Bandwidth Limit and Activation Priority
The dynamic CAC bearer bandwidth limit (BBL) configured on an interface specifies the
maximumbandwidth available for voice traffic on the interface. The TGM550 reports
the BBL to the MGC. When the call bandwidth exceeds the BBL, the MGC blocks new
calls and alerts the user with a busy tone.
You configure the dynamic CACactivation priority value on interfaces tospecify the order
in which the interfaces are used for providing call bandwidth.
Rules for Determining Reported BBL
To assess the WAN interfaces that have an activation priority value and determine a
single BBL to report to the MGC, the TGM550 uses the following rules. The reported BBL
(RBBL) allows the MGC to automatically control the call bandwidth when interfaces
responsible for providing call bandwidth become available or unavailable.
Report the BBL of the active interface with the highest activation priority. For example,
if one interface has the activation priority of 200 and a BBL of 1500 Kbps and another
interface has the activation priority of 100 and a BBL of 1000 Kbps, the RBBL is 1500
Kbps.
If more than one active interface has the same activation priority, report a BBL that is
the number of interfaces times their lowest BBL. For example, if two interfaces with
thesameactivationpriority haveBBLs of 2000Kbps and1500Kbps, theRBBLis 3000
Kbps (2 x 1500 Kbps).
If the interface with the highest activation priority is unavailable, report the BBL of the
active interface with the next highest activation priority.
If all the interfaces on which dynamic CAC is configured are inactive, report a BBL of
0. The MGC does not allowcalls to go through when the RBBL is 0.
NOTE: Dynamic CAC works in conjunction with the Avaya Communication
Manager (CM) Call Admission Control: Bandwidth Limitation (CAC-BL)
feature. If you configure dynamic CAC on WANinterfaces, you must also
configure CAC-BL on Avaya CM.
Related
Documentation
Configuring VoIP Interfaces with EPWand Disk-on-Key
If you have a newJ4350 or J6350 Services Router with the TGM550 and TIMs installed
in the router, you can use the Avaya Electronic Preinstallation Worksheet (EPW) and a
disk-on-key USB memory stick to configure VoIP on the router.
The EPWis a customizedMicrosoft Excel spreadsheet that you use to collect a complete
set of VoIP configuration information and create a configuration file named
juniper-config.txt. You can copy the juniper-config.txt file to a disk-on-key device and
boot the router fromthe device to configure VoIP on the router.
This configuration method has the following requirements:
A management device (PC or laptop) running Microsoft Excel version 2000 or later.
A disk-on-key device with one of the following 16-bit or 32-bit file allocation table
(FAT) file systems:
DOS 3.0+ 16-bit FAT (up to 32 MB)
DOS 3.31+ 16-bit FAT (over 32 MB)
WIN95 OSR2 FAT32
WIN95 OSR2 FAT32, LBA-mapped
WIN95 DOS 16-bit FAT, LBA-mapped
A Services Router with the factory configuration and the TGM550 and TIMs installed.
If other Junos OS configuration files exist on the Services Router, the router cannot
readthejuniper-config.txt filefromthedisk-on-key device. Toremovetheconfiguration
files fromthe router, press and hold the RESET CONFIG button for 15 seconds or more,
until the STATUS LED blinks red.
CAUTION: Pressing and holding the RESET CONFIG button for 15 seconds
or moreuntil the STATUS LED blinks reddeletes all configurations on
the router, including the backup configurations and rescue configuration,
and loads and commits the factory configuration.
To configure a VoIP interface using EPWand disk-on-key:
1. Download the EPWto a PC or laptop computer.
a. Go to http://support.avaya.com.
b. On the Avaya support page, click FindDocumentationandTechnical Information
by Product Name.
c. Scroll down and click Integrated Management Provisioning &Installation
Manager.
d. Select the 4.0 release fromthe select a release box and click Viewall documents.
e. Scroll down and double-click the Electronic Preinstallation Worksheet for
Provisioning Installation Manager link.
f. Scroll down and double-click the ViewXLS link.
g. In the File Open window, click the Open button.
h. In the Security Warning window, open the EPWby clicking Enable Macros. Be sure
to open the EPWin Microsoft Excel version 2000 or later versions.
2. Enter information in the individual worksheets. Ensure that all mandatory fields
(highlighted in blue color) are filled in.
3. Select File>Save.
4. Open the InitialConfig worksheet and click Create Configuration File.
The Select Location page is displayed.
5. Choose a location where you want to create the configuration file.
The configuration file with the name juniper-config.txt is created.
6. Copy the juniper-config.txt file to a disk-on-key device.
7. Press and release the power button to power off the router. Wait for the POWER LED
to turn off.
8. Plug the disk-on-key device into the USB port on the Services Router.
9. Press the POWER button on the front panel of the router. Verify that the POWER LED
on the front panel turns green.
The router reads the juniper-config.txt file fromthe disk-on-key device and commits
the configuration.
10. Remove the disk-on-key device.
Related
Documentation
Example: Configuring VoIP Interfaces
This example shows howto configure VoIP interfaces on a device.
Overviewon page 226
Verifying the VoIP Configuration on page 231
Requirements
Before you begin:
Install Services Router hardware, including the TGM550 and the TIMs. Before power
is connected, ensure that the router is grounded with a 10 AWG cable.
CAUTION: Theoriginal groundingcablefor SSGServicesRoutersis14AWG
only and must be replaced with a 10 AWGcable.
Verify that you have connectivity to at least one Avaya media server running Avaya
Communication Manager (CM) release 4.0 or later. For more information about Avaya
media servers, see Media Gateway Controller Server Overview on page 219.
Verify that the Services Router is running Junos OS Release 8.2R1 or later.
Downloadandinstall themost recent firmwarefor theTGM550. Verifythat theTGM550
firmware version is compatible with the Junos OS version installed on the Services
Router. For more information, see TGM550 Firmware Compatibility with Junos OS
on page 190.
If youareconfiguringVoIPusingtheAvayaElectronic PreinstallationWorksheet (EPW)
and a disk-on-key USB memory stick, order a disk-on-key USB memory stick. For
disk-on-key requirements, seeConfiguringVoIPInterfaces withEPWandDisk-on-Key
on page 222.
Establish basic connectivity.
If you do not already have a basic understanding of physical and logical interfaces and
Juniper Networks interface conventions, see Types of Interfaces Overview.
If you apply anIPaddress tothe TGM550, thenit resets the module. If you are updating
an existing VoIPconfiguration by modifying the TGM550IPaddress, take the following
precautions:
Log into the TGM550 and enter copy running-config startup-config to save the
TGM550 configuration. (For login instructions, see Saving the TGM550 Module
Configuration on page 237.)
Overview
In this example, a TGM550 installed in slot 2 of a Services Router has the IP address
10.10.10.2. The TGM550 needs to have registered a primary MGC at address 172.16.0.0,
and second and third MGC at addresses 10.10.10.30 and 10.10.10.10.40.
To configure dynamic call admission control (CAC), you define the bearer bandwidth
limit (BBL) and activation priority on each WAN interface responsible for providing call
bandwidth.
The activation priority has a range from1 through 255. The default value is 50.
The BBL has a range from0 Kbps through 9999 Kbps. The default BBL value of 1
Kbps indicates that the complete bandwidth of the interface is available for voice
traffic. Use a BBL of 0, which indicates that no bandwidth is available for bearer traffic
on the MGC, to use the interface for signaling only.
In this example, a Gigabit Ethernet, T1, and ISDN BRI interface are configured with the
BBL and activation priority values shown in Table 39 on page 226.
Table 39: Dynamic CAC Configuration Example
Activation Priority Value Bearer Bandwidth Limit (BBL) Value Interface Providing Call Bandwidth
200 3000 Kbps Gigabit Ethernet
150 1000 Kbps T1
100 128 Kbps ISDN BRI
The Gigabit Ethernet interface is used as the primary link for providing call bandwidth
because it has the highest activation priority value. When the Gigabit Ethernet interface
is active, the TGM550 reports its BBL value of 3000 Kbps to the MGC. If the Gigabit
Ethernet interface fails, the TGM550 automatically switches over to the T1 interface
because it has the next highest activation priority. The TGM550 nowreports the BBL
value of the T1 interface to the MGC. If the T1 interface also fails, the TGM550 switches
over to the ISDNBRI interface and reports the BBL value of the ISDNBRI interface to the
MGC. Configuring dynamic CAC on multiple WAN interfaces allows the MGC to
automatically control the call bandwidth when interfaces responsible for providing call
bandwidth are unavailable.
CAUTION: The TGM550 is reset when you commit the configuration after
modifying the IPaddress. Before modifying the TGM550IPaddress, take the
following precautions:
the TGM550 configuration.
Configuration
This example shows howto howto configure VoIP interfaces on a device. Performthe
following tasks marked (Required) and performother tasks if needed on your network.
Configuring the VoIP Interface (Required) on page 227
Configuring the Media Gateway Controller List (Required) on page 228
ConfiguringDynamicCall AdmissionControl onWANInterfaces (Optional) onpage229
Modifying the IP Address of the TGM550 on page 230
Configuring the VoIP Interface (Required)
CLI Quick
Configuration
To quickly configure the VoIP interface, copy the following commands and paste them
into the CLI.
[edit]
edit interfaces vp3/0/0
edit unit 0
set family inet address 10.10.10.1/32 destination 10.10.10.2
Step-by-Step
Procedure
To configure the VoIP interface:
Select the VoIP interface. 1.
[edit]
user@host# edit interfaces vp3/0/0
NOTE: You cannot configure more than one logical unit on the VoIP
interface. The logical unit number must be 0.
[edit]
3. Configure the source IPv4address anddestinationIPaddress for the VoIPinterface.
NOTE: You cannot specify more than one IP address.
[edit]
user@host# set family inet address 10.10.10.1/32 destination 10.10.10.2
[edit]
user@host# commit
5. Continue with Configuring the Media Gateway Controller List (Required) on
page 228. If you are done configuring the device, commit the configuration.
extensive command. If the output does not display the intended configuration, repeat
Configuring the Media Gateway Controller List (Required)
CLI Quick
Configuration
To quickly configure and clear the MGC list, in operational mode, copy the following
commands and paste theminto the CLI.
set tgmfpc 2 media-gateway-controller [172.16.0.010.10.10.3010.10.10.40]
ssh 10.10.10.2
ping 172.16.0.0
ping 10.10.10.30
ping 10.10.10.40
clear tgmfpc 2 media-gateway-controller
Step-by-Step
Procedure
To configure the MGC List in operational mode:
Configure the IP addresses of the Media Gateway Controllers. 1.
user@host> set tgmfpc 2 media-gateway-controller [172.16.0.010.10.10.30
10.10.10.40]
NOTE: Runningtheset tgmfpcslot media-gateway-controller command
updates the startup configuration on the TGM550. You do not need to
run the copy running-config start-config command to save the
configuration on the module.
2. Log in to the TGM550 with SSH, and verify that each MGC can be reached over the
network.
user@host> ssh 10.10.10.2
password> root
TGM550-00<root># ping 172.16.0.0
...
TGM550-00<root># ping 10.10.10.30
...
TGM550-00<root># ping 10.10.10.40
...
3. Do one of the following:
To control bandwidth assignments for voice traffic, see Configuring Dynamic
Call Admission Control on WAN Interfaces (Optional) on page 229.
To verify that VoIP is configured correctly on the router, see Verifying the VoIP
Step-by-Step
Procedure
To clear an MCG list in operational mode:
Remove all of the IP addresses fromthe MGC list. 1.
user@host> clear tgmfpc 2 media-gateway-controller
NOTE: The clear command removes all the MGC IP addresses. You
cannot clear the IP address of a single MGC with this command.
2. Add one or more newMGC IP addresses. See Modifying the IP Address of the
TGM550 on page 230.
Configuring Dynamic Call Admission Control on WANInterfaces (Optional)
CLI Quick
Configuration
To quickly configure dynamic CACon Services Router WANinterfaces, copy the following
edit interfaces ge-0/0/3
edit unit 0
set dynamic-call-admission-control activation-priority200bearer-bandwidth-limit 3000
edit interfaces t1-6/0/0
edit unit 0
set dynamic-call-admission-control activation-priority150bearer-bandwidth-limit 1000
edit interfaces br-1/0/3
edit unit 0
set dynamic-call-admission-control activation-priority 100bearer-bandwidth-limit 128
Step-by-Step
Procedure
To configure dynamic CAC on Services Router WAN interfaces:
Select the Gigabit Ethernet interface. 1.
[edit]
2. Configure dynamic CAC on logical unit 0 of the Gigabit Ethernet interface with the
activation priority and BBL values given in Table 39 on page 226.
[edit]
user@host# set dynamic-call-admission-control activation-priority 200
bearer-bandwidth-limit 3000
3. Select the T1 interface.
[edit]
4. Configure dynamic CAC on logical unit 0 of the T1 interface with the activation
priority and BBL values given in Table 39 on page 226.
[edit]
5. Select the ISDN BRI interface.
[edit]
user@host# edit interfaces br-1/0/3
6. ConfiguredynamicCAConlogical unit 0of theISDNBRI interfacewiththeactivation
priority and BBL values given in Table 39 on page 226.
[edit]
[edit]
user@host# commit
Modifying the IP Address of the TGM550
CLI Quick
Configuration
To quickly modify the IP address of the TGM550, copy the following commands and
paste theminto the CLI.
edit interfaces vp-3/0/0unit 0
set family inet address 10.10.10.1/32 destination 10.10.10.80
Step-by-Step
Procedure
To modify the IP address of the TGM550:
Select the logical VoIP interface. 1.
[edit]
user@host# edit interfaces vp-3/0/0unit 0
2. Modify the destination IP address for the TGM550 to a different address.
NOTE: You cannot specify more than one IP address.
[edit]
user@host# set family inet address 10.10.10.1/32 destination 10.10.10.80
[edit]
user@host# commit
Verifying the VoIP Configuration
Verifying the VoIP Interface on page 231
Verifying the Media Gateway Controller List on page 232
Verifying Bandwidth Available for VoIP Traffic on page 233
Verifying the VoIP Interface
Purpose Verify that the VoIP interface is correctly configured.
Action Fromoperational mode, enter the showinterfaces extensive command.
user@host> showinterfaces vp-3/0/0extensive
Physical interface: vp-3/0/0, Enabled, Physical link is Up
Type: VP-AV, Link-level type: VP-AV, MTU: 1518, Speed: 10mbps
Link flags : None
Last flapped : 2006-09-29 09:28:32 UTC (4d 18:35 ago)
Traffic statistics:
Input errors:
0,
Resource errors: 0
Output errors:
0
0 best-effort 65099 65099 0
Destination slot: 2
Limit
% bps % usec
0 best-effort 95 9500000 95 0 low
none
none
Logical interface vp-3/0/0.0 (Index 71) (SNMP ifIndex 47) (Generation 137)
Flags: Point-To-Point SNMP-Traps Encapsulation: VP-AV
Flags: None
Filters: Input: pcap, Output: pcap
Destination: 10.10.10.2, Local: 10.10.10.1, Broadcast: Unspecified,
Generation: 144
following:
The physical link is Up. A link state of Down indicates that the interface is disabled. Do
one of the following:
Verifying the Media Gateway Controller List
Purpose Verify that the Media Gateway Controller (MGC) list is correctly configured and that the
MGCs are reachable over the network.
Action Fromoperational mode, enter the showtgmfpc slot-number media-gateway-controller
command.
user@host> showtgmfpc 2 media-gateway-controller
Media gateway controller(s): 173.26.232.77
10.10.10.30
10.10.10.40
Meaning The output shows the configured MGC list. Verify the following:
The IPaddresses and the order of the IPaddresses in the MGClist are correct. The first
MGC on the list is the primary MGC. The TGM550 searches for the primary MGC first.
If it cannot connect to the primary MGC or loses its connection to the primary MGC, it
attempts to connect to the next MGC in the list, and so on.
Use the Junos OSCLI ping command or the J-Web ping host tool (Troubleshoot>Ping
Host) to verify that the configured MGCs can be reached over the network.
Verifying Bandwidth Available for VoIP Traffic
Purpose Verify that the dynamic call admission control (CAC) configuration supports sufficient
bandwidth for VoIP traffic.
Action Fromoperational mode, enter the showtgmdynamic-call-admission-control command.
user@host> showtgmdynamic-call-admission-control
Reported bearer bandwidth limit: 3000 Kbps
Interface State Activation Bearer bandwidth
priority limit (Kbps)
ge-0/0/3.0 up 200 3000
t1-6/0/0.0 up 150 1000
br-1/0/3.0 up 50 128
Meaning The output shows the dynamic CAC configuration. Verify the following information:
The activation priority and bearer bandwidth limit (BBL) configured on individual
interfaces are correct.
The Reported bearer bandwidth limit field displays the bandwidth available for VoIP
traffic. Ensure that the bandwidth is sufficient for VoIP traffic.
Related
Documentation
J4350 and J6350 Services Router Getting Started Guide
Administration for the Avaya IG550 Integrated Gateway at http://support.avaya.com
Junos Interfaces Command Reference
TGM550Module Administration
Connecting Through the TGM550 Module Console Port on page 234
Connecting to the TGM550 with SSH on page 235
TGM550 Module with Telnet Access on page 235
Accessing the Services Router fromthe TGM550 Module on page 236
Resetting the TGM550 Module on page 236
Saving the TGM550 Module Configuration on page 237
Connecting Through the TGM550Module Console Port
To connect to the TGM550 through its console port:
1. Turn off the power to the management device, such as a PC or laptop computer, that
you are using to access the TGM550.
2. Plug one end of an Ethernet rollover cable provided with the TGM550 into the RJ-45
to DB-9 serial port adapter provided with the TGM550.
CAUTION: Two different RJ-45 cables and RJ-45 to DB-9 adapters are
provided. Do not use the RJ-45 cable and adapter for the Services Router
console port to connect to the TGM550 console port.
3. Plug the RJ-45 to DB-9 serial port adapter provided with the TGM550 into the serial
port on the management device.
4. Connect the other end of the Ethernet rollover cable to the console port (CONSOLE)
on the TGM550.
5. Turn on power to the management device.
6. Start your asynchronous terminal emulation application (such as Microsoft Windows
Hyper Terminal), and select the appropriate COMport to use (for example, COM1).
7. Configure the port settings as follows:
Bits per second: 9600
Data bits: 8
Parity: None
Stop bits: 1
Flowcontrol: Hardware
8. At the login prompt, type your username and press Enter.
9. At the password prompt, type your password and press Enter.
Connecting to the TGM550with SSH
To connect to the TGM550 with SSH:
1. Ensure that the TGM550 has an IP address.
2. Fromthe Junos OS CLI or a remote connection, enter the following command:
ssh ip-address
TGM550Module with Telnet Access
Enabling Telnet Service on the TGM550 Module on page 235
Connecting to the TGM550 Module with Telnet on page 235
Disabling Telnet Service on the TGM550 Module on page 236
Enabling Telnet Service on the TGM550Module
By default, Telnet service is not enabled on the TGM550. You must enable Telnet service
on the TGM550 before you can telnet to the TGM550 fromother devices or fromthe
TGM550 to other devices.
CAUTION: Telnet connections are not encrypted and therefore can be
intercepted.
To enable Telnet service on the TGM550:
1. Connect to the TGM550 through the console port.
2. EnableincomingTelnet connections byenteringthefollowingcommand, andreplacing
port with the Telnet port number.
TGM550-004(super)# ip telnet port port
3. Enable outgoing Telnet connections fromthe TGM550 to other devices.
TGM550-004(super)# ip telnet-client
4. Save the configuration.
TGM550-004(super)# copy running-config startup-config
Connecting to the TGM550Module with Telnet
To connect to the TGM550 with Telnet:
1. Ensure that Telnet is enabled on the TGM550.
2. Ensure that the TGM550 has an IP address.
3. Fromthe Junos OS CLI or a remote connection, enter the following command.
telnet ip-address
Disabling Telnet Service on the TGM550Module
To disable Telnet service on the TGM550:
1. Connect to the TGM550 through the console port.
2. DisableincomingTelnet connectionsbyenteringthefollowingcommand, andreplacing
port with the Telnet port number.
TGM550-004(super)# no ip telnet
3. Disable outgoing Telnet connections fromthe TGM550 to other devices.
TGM550-004(super)# no ip telnet-client
Accessing the Services Router fromthe TGM550Module
You can access the Services Router fromthe CLI on its installed TGM550in the following
ways:
Enter the session chassis command.
Enter the telnet or ssh command.
NOTE: Before using the TGM550 CLI telnet command, ensure that Telnet
service is enabled on the TGM550.
Resetting the TGM550Module
CAUTION: Before resetting the TGM550, take the following precautions:
the TGM550 configuration.

You can reset the TGM550 fromthe module itself or fromthe Services Router.
To reset the TGM550 fromthe module itself, do one of the following:
Press the RST button on the TGM550.
Log into the TGM550, and enter the reset command.
To reset the TGM550 fromthe device:
1. Enter operational mode in the CLI.
2. Enter the request chassis fpc slot slot-number restart command.
For example, to reset a TGM550 installed in slot 2 on the router chassis, enter
user@host> request chassis fpc slot 2 restart
NOTE: Youcannot reset theTIMsusingtherequest chassisfpcslot slot-number
restart command. TIMs are administered only fromthe TGM550.
Saving the TGM550Module Configuration
To save the configuration on the TGM550:
1. Log in to the TGM550.
Related
Documentation
http://support.avaya.com.
TGM550Module and VoIP Interface Troubleshooting
Problem The TGM550 module is installed but the VoIP interface is unavailable.
The TGM550 module is installed and the VoIP interfacefor example, vp-3/0/0 is
configured, but the interface is not accessible. The showchassis hardware command
displays the TGM550 installed on slot 3. However, the showinterfaces terse command
does not display the vp-3/0/0 interface, and the showinterfaces vp-3/0/0 command
displays an error:
user@host> showinterfaces vp-3/0/0
error: device vp-3/0/0 not found
Solution The VoIP interface might be unavailable because the TGM550 firmware version is not
compatible with the Junos OS version installed on the device.
To correct the TGM550 firmware and Junos OS version compatibility error:
1. Check the router's systemlog messages for a version incompatibility error similar to
the following:
Jan 5 11:07:03 host fwdd[2857]: TGMT: RE (1.0) - TGM (2.0) major protocol
version mismatch: not marking TGM slot ready
2. If the error exists, connect to the TGM550 through the console port.
3. Viewthe TGM550 firmware version.
TGM550-003(super)# showimage version
Bank Version
----------- -------
A (current) 26.23.0
B 26.22.0
In this example, the current TGM550 firmware version is 26.23.0.
4. Identify the Junos OS version that is compatible with the current TGM550 firmware
version.
5. Upgrade the router with the compatible Junos OS version.
Related
Documentation
Communication Manager Software &Firmware Compatibility Matrix at
PART 5
DSL and ModemInterfaces
DSL Interfaces on page 241
G.SHDSL Interfaces on page 273
VDSL2 Mini-PIMInterfaces on page 295
3G Wireless Modems for WAN Connections on page 353
USB Modems for Dial Backup on page 373
DOCSIS Mini-PIMInterfaces on page 391
Serial Interfaces on page 401
CHAPTER 11
DSL Interfaces
ADSL Interface Overviewon page 241
ADSL and SHDSL Interfaces Configuration Overviewon page 244
Example: Configuring ATM-over-ADSL Network Interface on page 248
Example: Configuring ATM-over-SHDSL Network Interface on page 255
Example: Configuring CHAP on DSL Interfaces on page 261
Example: Configuring MLPPP over ADSL Interfaces on page 270
ADSL Interface Overview
The SRX210 and J Series devices support DSL features including ATM-over-ADSL and
ATM-over-SHDSL interfaces.
NOTE: Payloadloopbackfunctionalityisnot supportedonATM-over-SHDSL
interfaces.
Asymmetricdigital subscriber line(ADSL) technology is part of thexDSLfamily of modem
technologies that use existing twisted-pair telephone lines to transport high-bandwidth
data. ADSL lines connect service provider networks and customer sites over the "last
mile" of the networkthe loop between the service provider and the customer site.
ADSLtransmissionis asymmetricbecausethedownstreambandwidthis typically greater
than the upstreambandwidth. The typical bandwidths of ADSL, ADSL2, and ADSL2+
circuits are defined in Table 40 on page 241.
Table 40: Standard Bandwidths of DSL Operating Modes
Downstream Upstream Operating Modes
8 Mbps 800 Kbps1Mbps ADSL
1214 Mbps 11.5 Mbps ADSL2
2425 Mbps 11.15 Mbps ADSL2+
Table 40: Standard Bandwidths of DSL Operating Modes (continued)
Downstream Upstream Operating Modes
25 Mbps 4 Mbps ADSL2+ Annex M
SRX210 devices support ADSL, ADSL2, and ADSL2+, which comply with the following
standards:
For Annex A:
ITU G.992.1 (ADSL)
For Annex A only:
ANSI T1.413 Issue II
ITU G.992.3 (ADSL2)
ITU G.992.5 (ADSL2+)
For Annex M:
ITU G.992.3 (ADSL2)
For Annex B:
ITU G.992.1 (ADSL)
ITU G.992.3 (ADSL2)
For Annex B only
ETSI TS 101 388 V1.3
The ADSL Mini-PIMis supported on SRX210 devices. The ADSL Mini-PIMfacilitates a
maximumof 10 virtual circuits on SRX210 devices.
SRX210 devices with Mini-PIMs can use PPP over Ethernet over ATM(PPPoEoA) and
PPP over ATM(PPPoA) to connect through ADSL lines only.
ADSL Systems
ADSL links run across twisted-pair telephone wires. When ADSL modems are connected
to each end of a telephone wire, a dual-purpose ADSL circuit can be created. Once
established, the circuit can transmit lower-frequency voice traffic and higher-frequency
data traffic.
To accommodate both types of traffic, ADSL modems are connected to plain old
telephone service (POTS) splitters that filter out the lower-bandwidth voice traffic and
the higher-bandwidth data traffic. The voice traffic can be directed as normal telephone
voice traffic. The datatraffic is directedtothe ADSL modem, whichis typically connected
to the data network.
ADSL2 and ADSL2+
TheADSL2andADSL2+standards wereadoptedbytheITUinJuly2002. ADSL2improves
the data rate and reach performance, diagnostics, standby mode, and interoperability
of ADSL modems.
ADSL2+ doubles the possible downstreamdata bandwidth, enabling rates of 20 Mbps
on telephone lines shorter than 5000 feet (1.5 km).
ADSL2 uses seamless rate adaptation (SRA) to change the data rate of a connection
duringoperationwithnointerruptions or bit errors. TheADSL2transceiver detects changes
in channel conditionsfor example, the failure of another transceiver in a multicarrier
linkandsends a message to the transmitter to initiate a data rate change. The message
includes data transmission parameters such as the number of bits modulated and the
power on each channel. When the transmitter receives the information, it transitions to
the newtransmission rate.
ATMCoS Support
Certainclass-of-service(CoS) componentsfor AsynchronousTransmissionMode(ATM)
are provided to control data transfer, especially for time-sensitive voice packets. The
ADSLMini-PIMontheSRX210deviceprovides extendedATMCoSfunctionality toprovide
cells across the network. You can define bandwidth utilization, which consists of either
aconstant rate or apeak cell rate, withsustainedcell rate andburst tolerance. By default,
unspecified bit rate (UBR) is used because the bandwidth utilization is unlimited.
The following ATMtraffic shaping is supported for the SRX210 device:
CBR is the service category for traffic with rigorous timing requirements like voice and certain
types of video. CBR traffic needs a constant cell transmission rate throughout the duration of the
connection.
Constant bit rate (CBR)
VBR-NRT is intended for sources such as data transfer, which do not have strict time or delay
requirements. VBR-NRT is suitable for packet data transfers.
Variable bit rate non-real
- time (VBR-NRT)
UBR is ATMs best-effort service, which does not provide any CoS guarantees. This is suitable for
noncritical applications that can tolerate or quickly adjust to loss of cells.
Unspecifiedbit rate(UBR)
The ability of a network to guarantee class of service depends on the way in which the
source generates cells and also on the availability of network resources. The connection
contract between the user and the network thus contains information about the way in
which traffic is generated by the source.
A set of traffic descriptors is specified for this purpose. The network provides the class
of service for the cells that do not violate these specifications. The following are the
traffic descriptors specified for an ATMnetwork:
Peak cell rate (PCR)Top rate at which traffic can burst.
Sustained cell rate (SCR)Normal traffic rate averaged over time.
Chapter 11: DSL Interfaces
Maximumburst size (MBS)The maximumburst size that can be sent at the peak
rate.
Cell delay variation tolerance (CDVT)Allows the user to delay the traffic for a
particular time duration in microseconds to followa rhythmic pattern.
NOTE: CDVT is not supported on J Series devices.
For traffic that does not require the ability to periodically burst to a higher rate, you can
specify a CBR. You can configure VBR-NRTfor ATMinterfaces, which supports VBRdata
traffic with average and peak traffic parameters. VBR-NRT is scheduled with a lower
priority and with a larger sustained cell rate (SCR) limit, allowing it to recover bandwidth
if it falls behind.
Related
Documentation
Understanding Point-to-Point Protocol over Ethernet on page 469
ADSL and SHDSL Interfaces Configuration Overview
You can configure the following properties for the ADSL and SHDSL interfaces:
Physical properties
Logical properties
You can configure the following physical properties for the interface:
ATMvirtual path identifier (VPI) options for the interfacefor example, at-2/0/0:
ATMVPIA number from0 through 255for example, 25.
Operation, Maintenance, and Administration (OAM) F5 loopback cell thresholds
(liveness) on ATMvirtual circuits. The range is from1 through 255, and the default
is 5 cells.
Down countNumber of consecutive OAMloopback cells an ATMvirtual circuit
must lose to be identified as unavailablefor example, 200.
Up countNumber of consecutive OAMloopback cells an ATMvirtual interface
must receive to be identified as operationalfor example, 200.
OAMperiodInterval, in seconds, at which OAMcells are transmittedon ATMvirtual
circuitsfor example, 100. The range is from1 through 900 seconds.
Configure CBR for the interfacefor example, at-1/0/0.
CBRRange from33,000 through 1,199,920
CDVTRange from1 through 9,999
NOTE: CDVT is not supported on J Series devices.
Configure VBR for the interfacefor example, at-1/0/0.
MBSRange from33,000 through 1,199,920
CDVTRange from1 through 9,999
PCRRange from33,000 through 1,199,920
SCRRange from33,000 through 1,199,920
Type of DSL operating mode for the ATM-over-ADSL and ATM-over-SHDSL
interfacesfor example, auto:
Annex A (used in North American network implementations) and Annex B (used in
European network implementations) support the following operating modes:
autoConfigures the ADSL interface to autonegotiate settings with the DSLAM
located at the central office. For Annex A, the ADSL interface trains in either
ANSI T1.413IssueII modeor ITUG.992.1 mode. For Annex B, theADSLinterfacetrains
inITUG.992.1 mode. For theSHDSLinterface, thelinerateis availableonly intwo-wire
mode and is the default value.
itu-dmtConfigures the ADSL interface to train in ITU G.992.1 mode.
192 Kbps or higherSpeed of transmission of data on the SHDSL connection. For
the SHDSL interface, in the four-wire mode, the default line rate is 4,608 Kbps.
Annex A supports the following operating modes:
adsl2plusConfigures the ADSL interface to train in ITU G.992.5 mode. You can
configure this mode only when it is supported on the DSLAM.
itu-dmt-bisConfigures the ADSL interface to train in ITU G.992.3 mode. You can
configure this mode only when it is supported on the DSLAM.
ansi-dmtConfigures the ADSL interface to train in the ANSI T1.413 Issue II mode.
Annex B supports the following operating modes:
etsiConfigures the ADSL line to train in the ETSI TS 101 388 V1.3.1 mode.
itu-annexb-ur2Configures the ADSL line to train in the G.992.1 Deutsche Telekom
UR-2 mode.
itu-annexb-non-ur2Configures theADSLlinetotrainintheG.992.1 Non-UR-2mode.
Loopback option for testing the SHDSL connection integrityfor example, local
loopback.
The following values are available:
localUsed for testing the SHDSL equipment with local network devices.
payloadUsed to command the remote configuration to send back the received
payload.
remoteUsed to test SHDSL with a remote network configuration.
Signal-to-noiseratio(SNR) marginfor example, 5dBfor either or bothof thefollowing
thresholds:
currentLine trains at higher than current noise margin plus SNR threshold. The
range is from0 to 10 dB. The default value is 0.
snextLine trains at higher than self-near-end crosstalk (SNEXT) threshold. The
default value is disabled.
Setting the SNR creates a more stable SHDSL connection by making the line train at
a SNR margin higher than the threshold. If any external noise belowthe threshold is
applied to the line, the line remains stable. You can also disable the SNR margin
thresholds.
Encapsulation typefor example, ethernet-over-atm:
atm-pvcATMpermanent virtual circuits is the default encapsulation for
ATM-over-ADSL and ATM-over-SHDSL interfaces.
For PPP over ATM(PPPoA)-over-ADSL and over-SHDSL interfaces, use this type
of encapsulation.
ethernet-over-atmEthernet over ATMencapsulation.
For PPPover Ethernet (PPPoE) over ATM-over-ADSLandATM-over-SHDSLinterfaces
that carry IPv4 traffic, use this type of encapsulation.
You can configure the following logical properties for the interface:
Logical interface. Set a value from0 through 16,385for example, 3. Add other values
if required by your network.
Configure encapsulation for the ATM-for-ADSL or ATM-for-SHDSL logical unitfor
example, atm-nlpid.
The following encapsulations are supported on the ATM-over-ADSL and
ATM-over-SHDSL interfaces that use inet (IP) protocols only:
atm-vc-muxUse ATMvirtual circuit multiplex encapsulation.
atm-nlpidUse ATMnetwork layer protocol identifier (NLPID) encapsulation.
atm-cisco-nlpidUse Cisco NLPID encapsulation.
ether-over-atm-llcFor interfaces that carry IPv4 traffic, use Ethernet over LLC
encapsulation. You cannot configure multipoint interfaces if you use this type of
encapsulation.
The following encapsulations are supported on the ATM-over-ADSL or
ATM-over-SHDSL for PPP-over-ATM(PPPoA) interfaces only.
atm-ppp-llcAAL5 logical link control (LLC) encapsulation.
atm-ppp-vc-muxUse AAL5 multiplex encapsulation.
Other encapsulation types supported on the ATM-over-ADSL and ATM-over-SHDSL
interfaces are:
ppp-over-ether-over-atm-llcUse PPP over Ethernet over ATMLLC encapsulation.
When you use this encapsulation type, you cannot configure the interface address.
Instead you configure the interface address on the PPP interface.
atm-snapUse ATMsubnetwork attachment point (SNAP) encapsulation.
OAMoptions for the ATMvirtual circuits:
OAMF5 loopback cell thresholds (liveness) on ATMvirtual circuits. The range is
from1 through 255, and the default is 5 cells.
Down countNumber of consecutive OAMloopback cells an ATMvirtual circuit
must lose to be identified as unavailablefor example, 200.
Up countNumber of consecutive OAMloopback cells an ATMvirtual interface
must receive to be identified as operationalfor example, 200.
OAMperiodInterval, in seconds, at which OAMcells are transmittedon ATMvirtual
circuitsfor example, 100. The range is from1 through 900 seconds.
Family protocol typefor example, inet. Commands vary depending on the protocol
type.
ATMVCI options for the interface:
ATMVCI typevci
ATMVCI valueA number from0 through 4,089for example, 35with VCIs 0
through 31 reserved.
Related
Documentation
Understanding Point-to-Point Protocol over Ethernet on page 469.
Example: Configuring ATM-over-ADSL Network Interface
This example shows howtoconfigure ATM-over-ADSL network interfaces for the J Series
device.
Overviewon page 248
Requirements
Beforeyoubegin, configurenetworkinterfaces as necessary. SeeUnderstandingEthernet
Overview
J Series devices with ADSL Annex A or Annex B PIMs can use an ATMinterface to send
networktrafficthroughapoint-to-point connectiontoaDSLaccess multiplexer (DSLAM).
NOTE: You can configure J Series devices with ADSL PIMs for connections
through ADSL only, not for direct ATMconnections.
You configure the underlying ADSL interface as an ATMinterface, with an interface name
of at-pim/0/port. Multiple encapsulation types are supported on both the physical and
logical ATM-over-ADSL interface.
Because twisted-pair wiring has a length limit, ADSL modems are typically connected
to multiplexing devices. DSLAMs can process and route traffic frommultiple splitters.
Thistypical ADSLconfigurationisshowninFigure17onpage249andFigure18onpage249.
Figure 17: Typical ADSL IP DSLAMTopology
Figure 18: Typical ADSL ATMDSLAMTopology
This example shows howtoconfigure ATM-over-ADSL network interfaces for the J Series
device.
Configuration
CLI Quick
Configuration
To quickly configure ATM-over-ADSL network interfaces for the J Series device, copy the
following commands and paste theminto the CLI.
[edit]
edit interfaces at-2/0/0
set atm-options vpi 25
set atm-options vpi 25 oam-liveness up-count 200down-count 200
set atm-options vpi 25 oam-period 100
set interfaces at-1/0/0unit 0shaping cbr
set interfaces at-1/0/0unit 0shaping vbr
set dsl-options operating-mode auto
set encapsulation ethernet-over-atm
set unit 3
set unit 3 encapsulation atm-nlpid
set unit 3 oam-liveness up-count 200down-count 200
set unit 3 oam-period 100
set unit 3 family inet
set unit 3 vci 35
Step-by-Step
Procedure
To configure ATM-over-ADSL network interfaces for the J Series device:
Configure the interface. 1.
[edit]
user@host# edit interfaces at-2/0/0
2. Configure the physical properties for the interface: ATMVPI, OAMliveness values
on a VPI, OAMperiod, CBR value, and VBR value.
[edit]
user@host# set atm-options vpi 25
user@host# set atm-options vpi 25 oam-liveness up-count 200down-count 200
user@host# set atm-options vpi 25 oam-period 100
user@host# set interfaces at-1/0/0unit 0shaping cbr
user@host# set interfaces at-1/0/0unit 0shaping vbr
3. Configure the type of DSL operating mode for the ATM-over-ADSL interface.
[edit]
user@host# set dsl-options operating-mode auto
4. Configure the encapsulation type.
[edit]
user@host# set encapsulation ethernet-over-atm
5. Configure the logical interface.
[edit]
6. Configure the encapsulation for the ATM-over-ADSL logical unit.
[edit]
user@host# set unit 3 encapsulation atm-nlpid
7. Configure the OAMliveness values for an ATMvirtual circuit.
[edit]
user@host# set unit 3 oam-liveness up-count 200down-count 200
8. Configure the OAMperiod.
[edit]
user@host# set unit 3 oam-period 100
9. Add the Family protocol type.
[edit]
user@host# set unit 3 family inet
10. Configure the VCI value.
[edit]
user@host# set unit 3 vci 35
interface-name extensive command. If the output does not display the intended
configuration, repeat the configuration instructions in this example to correct it.
Continue by selecting one of the following procedures:
To enable authentication on the interface, see Example: Configuring CHAP on DSL
To configure PPP over Ethernet (PPPoE) encapsulation on an Ethernet interface or on
an ATM-over-ADSL interface, see Understanding Point-to-Point Protocol over
Ethernet on page 469.
Verification
Verifying ADSL Interface Properties on page 251
Displaying a PPPoA Configuration for an ATM-over-ADSL Interface on page 254
Verifying ADSL Interface Properties
Action Fromthe CLI, enter the showinterfaces interface-name extensive command.
user@host> showinterfaces at-1/0/0extensive
Physical interface: at-1/0/0, Enabled, Physical link is Up
Link-level type: ATM-PVC, MTU: 4482, Clocking: Internal, ADSL mode,
Speed: ADSL, Loopback: None
Link flags : None
Current address: 00:05:85:c3:17:f4
Traffic statistics:
Input errors:
Errors: 0, Drops: 0, Invalid VCs: 0, Framing errors: 0,Policed discards: 0,
L3 incompletes: 0, L2 channelerrors: 0, L2 mismatch timeouts: 0,
Resource errors: 0
Output errors:
Carrier transitions: 3, Errors: 0, Drops: 0, Aged packets: 0, MTU errors:
0, Resource errors: 0
ADSL alarms : None
ADSL defects : None
ADSL media: Seconds Count State
LOF 1 1 OK
LOS 1 1 OK
LOM 0 0 OK
LOP 0 0 OK
LOCDI 0 0 OK
LOCDNI 0 0 OK
ADSL status:
Modem status : Showtime (Adsl2plus)
DSL mode : Auto Annex A
Last fail code: None
Subfunction : 0x00
Seconds in showtime : 6093
ADSL Chipset Information: ATU-R ATU-C
Vendor Country : 0x0f 0xb5
Vendor ID : STMI IFTN
Vendor Specific: 0x0000 0x70de
ADSL Statistics: ATU-R ATU-C
Attenuation (dB) : 0.0 0.0
Capacity used(%) : 100 92
Noise margin(dB) : 7.5 9.0
Output power (dBm) : 10.0 12.5
Interleave Fast Interleave Fast
Bit rate (kbps) : 0 24465 0 1016
CRC : 0 0 0 0
FEC : 0 0 0 0
HEC : 0 0 0 0
Received cells : 0 49
Transmitted cells : 0 0
ATM status:
HCS state: Hunt
LOC : OK
ATM Statistics:
Uncorrectable HCS errors: 0, Correctable HCS errors: 0,Tx cell FIFO overruns:
0,Rx cell FIFO overruns: 0,Rx cell FIFO underruns: 0,
Input cell count: 49, Output cell count: 0,Output idle cell count: 0,Output
VC queue drops: 0Input no buffers: 0, Input length errors: 0,
Input timeouts: 0, Input invalid VCs: 0, Input bad CRCs: 0, Input OAM cell
no buffers: 0
Destination slot: 1
Direction : Output
Limit
% bps % usec
0 best-effort 95 7600000 95 0 low
none
none
But for ADSL MiniPim TI chipset does not send ADSL Chipset
Information. Also Adsl minipim does not send any alarms. So we can't
show alarm stats for minipim. So following information will not be
displayed in Minipim case.
ADSL alarms : None
ADSL defects : None
LOF 1 1 OK
LOS 1 1 OK
LOM 0 0 OK
LOP 0 0 OK
LOCDI 0 0 OK
LOCDNI 0 0 OK
following:
In the CLI, delete the disable statement at the [edit interfaces interface-name] level
of the configuration hierarchy.
In J-Web, clear the Disable check box on the Interfaces page
(Interfaces>interface-name).
No ADSL alarms and defects appear that can render the interface unable to pass
packets. When a defect persists for a certain amount of time, it is promoted to an
alarm. The following are ADSL-specific alarms:
LOCDILoss of cell delineation for interleaved channel
LOCDNILoss of cell delineation for noninterleaved channel
LOFLoss of frame
LOMLoss of multiframe
LOPLoss of power
LOSLoss of signal
FAR_LOFLoss of frame in ADSL transceiver unit-central office (ATU-C)
FAR_LOSLoss of signal in ATU-C
FAR_LOCDILoss of cell delineation for interleaved channel in ATU-C
FAR_LOCDNILoss of cell delineation for noninterleaved channel in ATU-C
Examine the operational statistics for an ADSL interface. Statistics in the ATU-R (ADSL
transceiver unitremote) column are for the near end. Statistics in the ATU-C (ADSL
transceiver unitcentral office) column are for the far end.
Attenuation (dB)Reduction in signal strength measured in decibels.
Capacity used (%)Amount of ADSL usage in %.
Noise Margin (dB)Maximumextraneous signal allowed without causing the output
to deviate froman acceptable level.
Output Power (dBm)Amount of power used by the ADSL interface.
Bit Rate (kbps)Data transfer speed on the ADSL interface.
Displaying a PPPoAConfiguration for an ATM-over-ADSL Interface
Purpose Verify that the PPPoA configuration for an ATM-over-ADSL interface is correct.
Action Enter the showinterfaces interface-name and the showaccess commands.
[edit]
user@host# showinterfaces at-1/0/0
at-1/0/0 {
encapsulation atm-pvc;
atm-options {
vpi 0;
}
dsl-options {
operating-mode auto;
}
unit 0 {
encapsulation atm-ppp-llc;
vci 0.100;
ppp-options {
chap {
access-profile A-ppp-client;
local-name A-at-1/0/0.0;
passive;
}
}
family inet {
negotiate address;
}
}
}
user@host# showaccess
profile A-ppp-client {
client A-ppp-server chap-secret "$9$G4ikPu0ISyKP5clKv7Nik.PT3"; ##SECRET-DATA
}
Meaning Verify that the output shows the intended configuration of PPPoA.
Related
Documentation
Types of Interfaces Overview
Example: Configuring ATM-over-SHDSL Network Interface
This example shows howto configure ATM-over-SHDSL network interfaces for the J
Series device.
Overviewon page 255
Requirements
Overview
J Series devices withG.SHDSL interfaces canuse anATMnterface tosendnetwork traffic
through a point-to-point connection to a DSLAM.
NOTE: You can configure J Series devices with a G.SHDSL interface for
connections through SHDSL only, not for direct ATMconnections.
J Series devices with a 2-port G.SHDSL interface installed support the following modes.
You can configure only one mode on each interface.
2-port two-wire mode (Annex A or Annex B)Supports autodetection of the line rate
or fixed line rates and provides network speeds from192 Kbps to 2.3 Mbps in 64-Kbps
increments. Two-wire mode provides two separate, slower SHDSL interfaces.
1-port four-wiremode(AnnexAor AnnexB)Supports fixedlinerates onlyandprovides
network speeds from384 Kbps to 4.6 Mbps in 128-Kbps increments, doubling the
bandwidth. Four-wire mode provides a single, faster SHDSL interface.
You configure the underlying G.SHDSL interface as an ATMinterface, with an interface
name of at-pim/0/port. Multiple encapsulation types are supported on both the physical
and logical ATM-over-SHDSL interface.
This example shows howto configure ATM-over-SHDSL network interfaces for the J
Series device.
Configuration
CLI Quick
Configuration
To quickly configure ATM-over-SHDSL network interfaces for the J Series device, copy
the following commands and paste theminto the CLI.
[edit]
set chassis fpc 6 pic 0shdsl pic-mode 1-port-atm
set atm-options vpi 25
set atm-options vpi 25 oam-liveness up-count 200down-count 200
set atm-options vpi 25 oam-period 100
set encapsulation ethernet-over-atm
set shdsl-options annex annex-a
set shdsl-options line-rate auto
set shdsl-options loopback local
set shdsl-options snr-margin current 5
set shdsl-options snr-margin snext 5
set unit 3
set unit 3 encapsulation atm-nlpid
set unit 3 oam-liveness up-count 200down-count 200
set unit 3 oam-period 100
set unit 3 family inet
set unit 3 vci 35
Step-by-Step
Procedure
To configure ATM-over-SHDSL network interfaces for the J Series device:
Set the ATM-over-SHDSL mode on the G.SHDSL interface, if required. By default,
G.SHDSL interfaces are enabled in two-wire Annex B mode.
1.
[edit]
user@host# set chassis fpc 6 pic 0shdsl pic-mode 1-port-atm
[edit]
3. Configure the physical properties for the interface: ATMVPI, OAMliveness values
on a VPI, and OAMperiod.
[edit]
user@host# set atm-options vpi 25 oam-liveness up-count 200down-count 200
user@host# set atm-options vpi 25 oam-period 100
[edit]
5. Set the annex type.
[edit]
user@host# set shdsl-options annex annex-a
6. Configure the SHDSL line rate for the ATM-over-SHDSL interface.
[edit]
user@host# set shdsl-options line-rate auto
7. Configure the loopback option for testing the SHDSL connection integrity.
[edit]
user@host# set shdsl-options loopback local
8. Configure the signal-to-noise ratio (SNR) margin.
[edit]
user@host# set shdsl-options snr-margin current 5
user@host# set shdsl-options snr-margin snext5
9. Configure the logical interface.
[edit]
10. Configure the encapsulation for the ATM-over-SHDSL logical unit.
[edit]
user@host# set unit 3 encapsulation atm-nlpid
11. Configure the OAMliveness values for an ATMvirtual circuit.
[edit]
user@host# set unit 3 oam-liveness up-count 200down-count 200
12. Configure the OAMperiod.
[edit]
user@host# set unit 3 oam-period 100
[edit]
user@host# set unit 3 family inet
14. Configure the VCI value.
[edit]
user@host# set unit 3 vci 35
Continue by selecting one of the following procedures:
To enable authentication on the interface, see Example: Configuring CHAP on DSL
To configure PPP over Ethernet (PPPoE) encapsulation on an Ethernet interface or on
an ATM-over-ADSL interface, see Understanding Point-to-Point Protocol over
Ethernet on page 469.
Verification
Verifying an ATM-over-SHDSL Configuration on page 258
Verifying an ATM-over-SHDSL Configuration
Link-level type: ATM-PVC, MTU: 4482, Clocking: Internal, ADSL mode, Speed: ADSL,
Loopback: None
Link flags : None
Current address: 00:05:85:c7:44:3c
Traffic statistics:
Input errors:
Errors: 0, Drops: 0, Invalid VCs: 0, Framing errors: 0, Policed discards: 0,
L3 incompletes: 0, L2 channel errors: 1, L2 mismatch timeouts: 0, Resource
errors: 0
Output errors:
Carrier transitions: 3, Errors: 0, Drops: 0, Aged packets: 0, MTU errors: 0,
Resource errors: 0
0 best-effort 4 4 0
SHDSL alarms : None
SHDSL defects : None
SHDSL media: Seconds Count State
LOSD 239206 2 OK
LOSW 239208 1 OK
ES 3 1 OK
SES 0 0 OK
UAS 3 1 OK
SHDSL status:
Line termination :STU-R
Annex :Annex B
Line Mode :2wire
Modem Status :Data
Last fail code :0
Framer mode :ATM
Dying Gasp :Enabled
Chipset version :1
Firmware version :R3.0
SHDSL Statistics:
Loop Attenuation (dB) :0.600
Transmit power (dB) :8.5
Receiver gain (dB) :21.420
SNR sampling (dB) :39.3690
Bit rate (kbps) :2304
Bit error rate :0
CRC errors :0
SEGA errors :1
LOSW errors :0
Received cells :1155429
Transmitted cells :1891375
HEC errors :0
Cell drop :0
following:
In the J-Web configuration editor, clear the Disable check box on the Interfaces page
No SHDSL alarms and defects appear that can render the interface unable to pass
alarm.
LOSLoss of signal. No signal was detected on the line.
LOSWLoss of sync word. A message ID was sent.
Power statusA power failure has occurred.
LOSDLoss of signal was detected at the remote application interface.
ESErrored seconds. One or more cyclic redundancy check (CRC) anomalies were
detected.
SESSeverely errored seconds. At least 50 CRC anomalies were detected.
UASUnavailableseconds. Aninterval hasoccurredduringwhichoneor moreLOSW
defects were detected.
Examine the SHDSL interface status:
Line terminationSHDSL transceiver unitremote (STUR). (Only customer premises
equipment is supported.)
AnnexEither Annex A or Annex B. Annex A is supported in North America, and Annex
B is supported in Europe.
Line ModeSHDSL mode configured on the G.SHDSL interface pair, either 2-wire or
4-wire.
ModemStatusData. Sending or receiving data.
Last fail codeCode for the last interface failure.
Framer modeFramer mode of the underlying interface: ATM.
DyingGaspAbilityof aJ Seriesdevicethat haslost power tosendamessageinforming
the attached DSL access multiplexer (DSLAM) that it is about to go offline.
Chipset versionVersion number of the chipset on the interface
Firmware versionVersion number of the firmware on the interface.
Examine the operational statistics for a SHDSL interface.
Loop Attenuation (dB)Reduction in signal strength measured in decibels.
Transmit power (dB)Amount of SHDSL usage in %.
Receiver gain (dB)Maximumextraneous signal allowed without causing the output
SNR sampling (dB)Signal-to-noise ratio at a receiver point, in decibels.
Bit Rate (kbps)Data transfer speed on the SHDSL interface.
CRC errorsNumber of cyclic redundancy check errors.
SEGAerrorsNumber of segment anomalyerrors. Aregenerator operatingonasegment
received corrupted data.
LOSWerrorsNumber of loss of signal defect errors. Three or more consecutively
received frames contained one or more errors in the framing bits.
Received cellsNumber of cells received through the interface.
Transmitted cellsNumber of cells sent through the interface.
HEC errorsNumber of header error checksumerrors.
Cell dropNumber of dropped cells on the interface.
Related
Documentation
Example: Configuring CHAP on DSL Interfaces
This exampleshows howtoconfigureCHAPontheATM-over-ADSLor ATM-over-SHDSL
interface.
Overviewon page 262
Requirements
Overview
For interfaces with PPPoA encapsulation, you can optionally configure interfaces to
support the PPP Challenge Handshake Authentication Protocol (CHAP). When you
enableCHAPonaninterface, theinterfacecanauthenticateits peer andbeauthenticated
by its peer.
If you set the passive option to handle incoming CHAP packets only, the interface does
not challengeits peer. However, if theinterfaceis challenged, it responds tothechallenge.
If you do not set the passive option, the interface always challenges its peer.
This exampleshows howtoconfigureCHAPontheATM-over-ADSLor ATM-over-SHDSL
interface.
Configuration
CLI Quick
Configuration
To quickly configure CHAP on the ATM-over-ADSL or ATM-over-SHDSL interface, copy
the following commands and paste theminto the CLI.
[edit]
set access profile A-ppp-client client client1 chap-secret my-secret
edit interfaces at-3/0/0unit 0
set ppp-options chap access-profile A-ppp-client
set ppp-options chap local-name A-at-3/0/0.0
set ppp-options chap passive
Step-by-Step
Procedure
To configure CHAP on the ATM-over-ADSL or ATM-over-SHDSL interface:
Define a CHAP access profile. 1.
[edit]
user@host# set access profile A-ppp-client client client1 chap-secret my-secret
[edit]
user@host# edit interfaces at-3/0/0unit 0
3. Configure CHAP on the ATM-over-ADSL or ATM-over-SHDSL interface and specify
a unique profile name containing a client list and access parameters.
[edit]
user@host# set ppp-options chap access-profile A-ppp-client
4. Specify a unique hostname to be used in CHAP challenge and response packets.
[edit]
user@host# set ppp-options chap local-name A-at-3/0/0.0
5. Set the passive option to handle incoming CHAP packets only.
[edit]
user@host# set ppp-options chap passive
Verification
Displaying a PPPoA Configuration for an ATM-over-ADSL Interface on page 266
Verifying an ATM-over-SHDSL Configuration on page 266
Speed: ADSL, Loopback: None
Link flags : None
Current address: 00:05:85:c3:17:f4
Traffic statistics:
Input errors:
Errors: 0, Drops: 0, Invalid VCs: 0, Framing errors: 0,Policed discards: 0,
L3 incompletes: 0, L2 channelerrors: 0, L2 mismatch timeouts: 0,
Resource errors: 0
Output errors:
Carrier transitions: 3, Errors: 0, Drops: 0, Aged packets: 0, MTU errors:
0, Resource errors: 0
ADSL alarms : None
ADSL defects : None
LOF 1 1 OK
LOS 1 1 OK
LOM 0 0 OK
LOP 0 0 OK
LOCDI 0 0 OK
LOCDNI 0 0 OK
ADSL status:
Modem status : Showtime (Adsl2plus)
Subfunction : 0x00
ADSL Statistics: ATU-R ATU-C
Capacity used(%) : 100 92
Noise margin(dB) : 7.5 9.0
Bit rate (kbps) : 0 24465 0 1016
CRC : 0 0 0 0
FEC : 0 0 0 0
HEC : 0 0 0 0
Received cells : 0 49
Transmitted cells : 0 0
ATM status:
HCS state: Hunt
LOC : OK
ATM Statistics:
Uncorrectable HCS errors: 0, Correctable HCS errors: 0,Tx cell FIFO overruns:
0,Rx cell FIFO overruns: 0,Rx cell FIFO underruns: 0,
Input cell count: 49, Output cell count: 0,Output idle cell count: 0,Output
VC queue drops: 0Input no buffers: 0, Input length errors: 0,
Input timeouts: 0, Input invalid VCs: 0, Input bad CRCs: 0, Input OAM cell
no buffers: 0
Destination slot: 1
Direction : Output
Limit
% bps % usec
0 best-effort 95 7600000 95 0 low
none
none
But for ADSL MiniPim TI chipset does not send ADSL Chipset
Information. Also Adsl minipim does not send any alarms. So we can't
show alarm stats for minipim. So following information will not be
displayed in Minipim case.
ADSL alarms : None
ADSL defects : None
LOF 1 1 OK
LOS 1 1 OK
LOM 0 0 OK
LOP 0 0 OK
LOCDI 0 0 OK
LOCDNI 0 0 OK
following:
No ADSL alarms and defects appear that can render the interface unable to pass
alarm. The following are ADSL-specific alarms:
LOCDILoss of cell delineation for interleaved channel
LOCDNILoss of cell delineation for noninterleaved channel
LOFLoss of frame
LOMLoss of multiframe
LOPLoss of power
LOSLoss of signal
FAR_LOFLoss of frame in ADSL transceiver unit-central office (ATU-C)
FAR_LOSLoss of signal in ATU-C
FAR_LOCDILoss of cell delineation for interleaved channel in ATU-C
FAR_LOCDNILoss of cell delineation for noninterleaved channel in ATU-C
Examine the operational statistics for an ADSL interface. Statistics in the ATU-R (ADSL
transceiver unitremote) column are for the near end. Statistics in the ATU-C (ADSL
transceiver unitcentral office) column are for the far end.
Attenuation (dB)Reduction in signal strength measured in decibels.
Capacity used (%)Amount of ADSL usage in %.
Noise Margin (dB)Maximumextraneous signal allowed without causing the output
Output Power (dBm)Amount of power used by the ADSL interface.
Bit Rate (kbps)Data transfer speed on the ADSL interface.
Displaying a PPPoAConfiguration for an ATM-over-ADSL Interface
Purpose Verify that the PPPoA configuration for an ATM-over-ADSL interface is correct.
Action Enter the showinterfaces interface-name and the showaccess commands.
[edit]
user@host# showinterfaces at-1/0/0
at-1/0/0 {
encapsulation atm-pvc;
atm-options {
vpi 0;
}
dsl-options {
}
unit 0 {
encapsulation atm-ppp-llc;
vci 0.100;
ppp-options {
chap {
local-name A-at-1/0/0.0;
passive;
}
}
family inet {
negotiate address;
}
}
}
user@host# showaccess
profile A-ppp-client {
client A-ppp-server chap-secret "$9$G4ikPu0ISyKP5clKv7Nik.PT3"; ##SECRET-DATA
}
Meaning Verify that the output shows the intended configuration of PPPoA.
Verifying an ATM-over-SHDSL Configuration
Link-level type: ATM-PVC, MTU: 4482, Clocking: Internal, ADSL mode, Speed: ADSL,
Loopback: None
Link flags : None
Current address: 00:05:85:c7:44:3c
Traffic statistics:
Input errors:
errors: 0
Output errors:
Resource errors: 0
0 best-effort 4 4 0
SHDSL alarms : None
LOSD 239206 2 OK
LOSW 239208 1 OK
ES 3 1 OK
SES 0 0 OK
UAS 3 1 OK
SHDSL status:
Line termination :STU-R
Annex :Annex B
Line Mode :2wire
Modem Status :Data
Last fail code :0
Framer mode :ATM
Dying Gasp :Enabled
Chipset version :1
Firmware version :R3.0
SHDSL Statistics:
Loop Attenuation (dB) :0.600
Transmit power (dB) :8.5
Receiver gain (dB) :21.420
SNR sampling (dB) :39.3690
Bit rate (kbps) :2304
Bit error rate :0
CRC errors :0
SEGA errors :1
LOSW errors :0
Received cells :1155429
Transmitted cells :1891375
HEC errors :0
Cell drop :0
following:
No SHDSL alarms and defects appear that can render the interface unable to pass
alarm.
LOSLoss of signal. No signal was detected on the line.
LOSWLoss of sync word. A message ID was sent.
Power statusA power failure has occurred.
LOSDLoss of signal was detected at the remote application interface.
ESErrored seconds. One or more cyclic redundancy check (CRC) anomalies were
detected.
SESSeverely errored seconds. At least 50 CRC anomalies were detected.
UASUnavailableseconds. Aninterval hasoccurredduringwhichoneor moreLOSW
defects were detected.
Examine the SHDSL interface status:
Line terminationSHDSL transceiver unitremote (STUR). (Only customer premises
equipment is supported.)
AnnexEither Annex A or Annex B. Annex A is supported in North America, and Annex
B is supported in Europe.
Line ModeSHDSL mode configured on the G.SHDSL interface pair, either 2-wire or
4-wire.
ModemStatusData. Sending or receiving data.
Last fail codeCode for the last interface failure.
Framer modeFramer mode of the underlying interface: ATM.
DyingGaspAbilityof aJ Seriesdevicethat haslost power tosendamessageinforming
the attached DSL access multiplexer (DSLAM) that it is about to go offline.
Chipset versionVersion number of the chipset on the interface
Firmware versionVersion number of the firmware on the interface.
Examine the operational statistics for a SHDSL interface.
Loop Attenuation (dB)Reduction in signal strength measured in decibels.
Transmit power (dB)Amount of SHDSL usage in %.
Receiver gain (dB)Maximumextraneous signal allowed without causing the output
SNR sampling (dB)Signal-to-noise ratio at a receiver point, in decibels.
Bit Rate (kbps)Data transfer speed on the SHDSL interface.
CRC errorsNumber of cyclic redundancy check errors.
SEGAerrorsNumber of segment anomalyerrors. Aregenerator operatingonasegment
received corrupted data.
LOSWerrorsNumber of loss of signal defect errors. Three or more consecutively
received frames contained one or more errors in the framing bits.
Received cellsNumber of cells received through the interface.
Transmitted cellsNumber of cells sent through the interface.
HEC errorsNumber of header error checksumerrors.
Cell dropNumber of dropped cells on the interface.
Related
Documentation
Example: Configuring MLPPP over ADSL Interfaces
This example shows howto configure MLPPP on an ADSL interface.
Overviewon page 270
Requirements
Overview
An SRX Series device or a J Series device with an ADSL interface support link
fragmentationandinterleaving(LFI) throughaMultilinkPoint-to-Point Protocol (MLPPP).
NOTE: Currently, Junos OS supports bundling of only one xDSL link under
bundle interface.
To support MLPPP encapsulation and the family mlppp on the ADSL interface on an
SRX Series or a J Series device, an existing Junos OS CLI is enabled.
To establish an ADSL link between network devices, you must use some intermediate
connections. First, useanRJ-11 cabletoconnect thecustomer premises equipment (CPE)
(for example, an SRX Series device or a J Series device) to a DSLAMpatch panel to form
an ADSL link. Then use OC3 or DS3 to connect the DSLAMto MSeries or E Series devices
toformanATMbackbone. Figure 19onpage 270shows atypical example of MLPPPover
ADSL end-to-end connectivity.
Figure 19: MLPPP over ADSL Interface
Configuration
CLI Quick
Configuration
To quickly configure MLPPP on an ADSL interface, copy the following commands and
[edit]
set interfaces at-5/0/0 unit 0 encapsulation atm-mlppp-llc
set interfaces at-5/0/0 unit 0 family mlppp bundle lsq-0/0/0.1
Step-by-Step
Procedure
To configure MLPPP on an ADSL interface:
Configure MLPPP encapsulation. 1.
[edit]
user@host# set interfaces at-5/0/0 unit 0 encapsulation atm-mlppp-llc
2. Configure the family mlppp.
[edit]
user@host# set interfaces at-5/0/0 unit 0 family mlppp bundle lsq-0/0/0.1
Verification
Related
Documentation
CHAPTER 12
G.SHDSL Interfaces
This section includes the following topics:
SHDSL Interface Overviewon page 273
G.SHDSL Mini-PIMOverviewon page 274
G.SHDSL Mini-PIMConfiguration Overviewon page 275
Example: Configuring the G.SHDSL Interface on page 277
Example: Configuring the G.SHDSL Interface on SRX Series Devices on page 286
SHDSL Interface Overview
Symmetric high-speed DSL (SHDSL) interfaces on J Series device support an SHDSL
multirate technology for data transfer between a single customer premises equipment
(CPE) subscriber and a central office (CO). ITU-T G.991.2 is the official standard for
describing SHDSL, also known as G.SHDSL.
Unlike ADSL, which delivers more bandwidth downstreamthan available upstream,
SHDSL is symmetrical and delivers a bandwidth of up to 2.3 Mbps in both directions.
Because business applications require higher-speed digital transportation methods,
SHDSLis becomingverypopular andgainingwideacceptanceintheindustry. Additionally,
SHDSL is compatible with ADSL and therefore causes very little, if any, interference
between cables.
SHDSL is deployed on a network in much the same manner as ADSL.
Related
Documentation
G.SHDSL Mini-PIMOverview
The G.SHDSL Mini-Physical Interface Module (Mini-PIM) is supported on SRX210 and
SRX240devices. TheG.SHDSLsupportedontheSRXSeries deviceprovides thephysical
connection to DSL network media types.
The G.SHDSL Mini-Physical Interface Module (Mini-PIM) provides the following key
features:
2-wire (4 port 2-wire) mode, 4-wire (2 port 4-wire) mode, and 8-wire (1 port 8-wire)
mode support
Virtual circuits per Mini-PIM(8 maximum)
ATM-over-G.SHDSL framing
ATMOAMsupport
MaximumMTU size of 9180 bytes
Noise margin support
Point-to-Point Protocol over ATMand PPPoE over ATMencapsulation support
Local loopback mode support
The following four annexes are supported on the G.SHDSL Mini-PIM:
Annex A
Annex B
Annex F
Annex G
Operating Modes and Line Rates of the G.SHDSL Mini-PIM
The G.SHDSL Mini-PIMsupports 2-wire, 4-wire, and 8-wire modes; the Mini-PIMcan be
usedin1x8-wire, 2x4-wire, and4x2-wiremodes. Thedefault operatingmodeis 2x4-wire
for this G.SHDSL Mini-PIM. G.SHDSL is supported on all SRX210 and SRX240 devices
using the symmetrical WAN speeds shown in Table 41 on page 274.
Table 41: Symmetrical WANSpeeds
Symmetrical WANSpeed Using Annex F and G
Symmetrical WANSpeed
Using Annex A and B Modes
From768 Kbps to 5.696 Mbps 2.3 Mbps 2-wire
From1.536 Mbps to 11.392 Mbps 4.6 Mbps 4-wire
From3.072 Mbps to 22.784 Mbps 9.2 Mbps 8-wire
NOTE: A maximumof 16 Mbps is supported on SRX210 and SRX240 devices.
ATMCoS Support
The G.SHDSL Mini-PIMon the SRX210 and SRX240 devices provide extended ATMCoS
functionality to cells across the network. You can define bandwidth utilization, which
consists of either a constant rate or a peak cell rate, with sustained cell rate and burst
tolerance. By default, unspecifiedbit rate(UBR) is usedbecausethebandwidthutilization
is unlimited.
The following ATMtraffic shaping is supported for SRX210 and SRX240 devices:
Constant bit rate (CBR)CBR is the service category for traffic with rigorous timing
requirements like voice and certain types of video. CBR traffic needs a constant cell
transmission rate throughout the duration of the connection.
Variable bit rate, non-real-time (VBR-NRT)VBR-NRT is intended for sources such as
datatransfer, whichdonot have strict time or delay requirements. VBR-NRTis suitable
for packet data transfers.
Variable bit rate, real-time (VBR-RT)VBR-RT is intended for sources such as data
transfer, which takes place in real time. VBR-RT requires access to time slots at a rate
that can vary significantly fromtime to time.
Table 42 on page 275 displays the traffic descriptors specified for an ATMnetwork.
Table 42: Traffic Descriptors
Description Traffic Descriptors
Maximumrate at which traffic can burst. Peak cell rate (PCR)
Normal traffic rate averaged over time. Sustained cell rate (SCR)
Maximumburst size that can be sent at the peak rate. Maximumburst size (MBS)
Related
Documentation
G.SHDSL Mini-PIMConfiguration Overview
NOTE: The G.SHDSL configuration details mentioned in this topic are
applicable to SRX Series devices.
Chapter 12: G.SHDSL Interfaces
Specify the wire mode on the G.SHDSL interface using one of the following options:
1-port-atmConfigures an 8-wire (1-port, 8-wire) wire mode.
2-port-atmConfigures a 4-wire (2-port, 4-wire) wire mode.
4-port-atmConfigures a 2-wire (4-port, 2-wire) wire mode.
NOTE: The default wire mode is 4-wire (2-port, 4-wire).
Specify the annex type using one of the following options:
Annex A
Annex B
Annex F
Annex G
NOTE: The default annex type is Annex B.
Specify the SHDSL line rate (speed of transmission of data on the SHDSL connection)
using one of the following values:
autoAutomatically selects a line rate.
valueSelects a value between 192 kbps and 22,784 kbps.
NOTE: The default line rate is auto.
Specify the encapsulation type using one of the following values:
atm-pvcATMpermanent virtual circuits is the default encapsulation for
ATM-over-SHDSL interfaces. For PPP over ATM(PPPoA) over SHDSL interfaces, use
this type of encapsulation. Use this type of encapsulation if you are using ATMDSLAM.
ethernet-over-atmEthernet over ATMencapsulation. For PPPover Ethernet (PPPoE)
over ATM-over-SHDSL interfaces that carry IPv4traffic, use this type of encapsulation.
Use this type of encapsulation if you are using IP DSLAM.
Configure the encapsulation type using one of the following values:
atm-cisco-nlpidCisco NLPID encapsulation.
atm-mlppp-llcATMMLPPP over AAL5/LLC encapsulation.
atm-nlpidATMNetwork Layer protocol identifier (NLPID) encapsulation.
atm-ppp-llcAAL5 logical link control (LLC) encapsulation.
atm-ppp-vc-muxAAL5 multiplex encapsulation.
atm-vc-muxATMvirtual circuit multiplex encapsulation.
atm-snapATMsubnetwork attachment point (SNAP) encapsulation.
ether-over-atm-llcFor interfaces that carry IPv4 traffic, use Ethernet over LLC
encapsulation. You cannot configure multipoint interfaces if you use this type of
encapsulation.
ppp-over-ether-over-atm-llcPPP over Ethernet over ATMLLC encapsulation. When
you use this encapsulation type, you cannot configure the interface address. Instead
you configure the interface address on the PPP interface.
Related
Documentation
Example: Configuring the G.SHDSL Interface
This example shows howto configure the G.SHDSL interface.
Overviewon page 277
Requirements
Overview
The G.SHDSL Mini-Physical Interface Module (Mini-PIM) is supported on SRX210 and
SRX240devices. TheG.SHDSLsupportedontheSRXSeries deviceprovides thephysical
connection to DSL network media types. This example shows howto configure the
G.SHDSL interface.
Configuration
CLI Quick
Configuration
To quickly configure the G.SHDSL interface, copy the following commands and paste
theminto the CLI:
[edit]
set interfaces at-1/0/0shdsl-options annex annex-a
set interfaces at-1/0/0shdsl-options line-rate auto
set interfaces at-1/0/0encapsulation ethernet-over-atm
set interfaces at-1/0/0unit 3
set interfaces at-1/0/0unit 0encapsulation
Step-by-Step
Procedure
To configure the G.SHDSL interface:
Specify the wire mode on the G.SHDSL interface. 1.
[edit]
[edit]
3. Specify the annex type.
[edit]
user@host# set interfaces at-1/0/0shdsl-options annex annex-a
4. Configure the line rates.
[edit]
user@host# set interfaces at-1/0/0shdsl-options line-rate auto
5. Specify the encapsulation type.
[edit]
user@host# set interfaces at-1/0/0encapsulation ethernet-over-atm
6. Defineoneor morelogical units that youconnect tothephysical G.SHDSLinterface.
[edit]
user@host# set interfaces at-1/0/0unit 3
[edit]
user@host# set interfaces at-1/0/0unit 0encapsulation
Verification
Verifying G.SHDSL Interface Properties on page 278
Verifying G.SHDSL Interface Properties
Purpose Verify that the G.SHDSL interface properties are configured properly.
user@host# run show interfaces at-1/0/0 extensive
For 4-wire mode (for interface at-1/0/0):
Link-level type: ATM-PVC, MTU: 1496, Clocking: Internal, Speed: SHDSL(4-wire)
Speed: SHDSL(4-wire), Loopback: None
Link flags : None
Current address: 00:24:dc:01:cf:a0
Statistics last cleared: 2009-09-24 00:18:24 PDT (00:01:33 ago)
Traffic statistics:
Input errors:
errors: 0
Output errors:
Resource errors: 0
0 best-effort 1 1 0
SHDSL alarms : None
LINE1_LOSD 32 0 OK
LINE1_LOSW 37 0 OK
LINE2_LOSD 32 0 OK
LINE2_LOSW 37 0 OK
ES 37
SES 37
UAS 48
SHDSL status:
Line termination : STU-R
Annex : Annex B
Line mode : 4-wire
Modem status : Data
Bit rate (kbps) : 4608
Last fail mode : No failure (0x00)
Framer mode : ATM
Dying gasp : Enabled
Framer sync status : In sync
Chipset version : 00
SHDSL statistics:
Loop attenuation (dB) : 0.0
Transmit power (dBm) : 0.0
Receiver gain (dB) : -inf
SNR sampling (dB) : inf
CRC errors : 0
SEGA errors : 0
LOSW errors : 0
Received cells : 0
Transmitted cells : 0
HEC errors : 0
Cell drop : 0
Destination slot: 1
CoS information:
Direction : Output
Limit
% bps % usec
0 best-effort 95 4377600 95 0 low
none
none
Logical interface at-1/0/0.0 (Index 76) (SNMP ifIndex 133) (Generation 402)
Flags: Point-To-Multipoint SNMP-Traps 0x0 Encapsulation: Ether-over-ATM-LLC
Traffic statistics:
Input bytes : 125
Output bytes : 116
Input packets: 2
Output packets: 1
Local statistics:
Input bytes : 125
Output bytes : 116
Input packets: 2
Output packets: 1
Transit statistics:
Flow Statistics :
Flow Input statistics :
Self packets : 0
ICMP packets : 0
VPN packets : 0
Multicast packets : 0
Bytes permitted by policy : 0
Connections established : 0
Flow Output statistics:
Flow error statistics (Packets dropped due to):
Address spoofing: 0
Authentication failed: 0
Incoming NAT errors: 0
Invalid zone received packet: 0
Multiple user authentications: 0
Multiple incoming NAT: 0
No parent for a gate: 0
No one interested in self packets: 0
No minor session: 0
No more sessions: 0
No NAT gate: 0
No route present: 0
No SA for incoming SPI: 0
No tunnel found: 0
No session for a gate: 0
No zone or NULL zone binding 0
Policy denied: 0
Security association not active: 0
TCP sequence number out of window: 0
Syn-attack protection: 0
User authentication errors: 0
Flags: None
Destination: 17.1.1/24, Local: 17.1.1.1, Broadcast: 17.1.1.255, Generation:
496
VCI 1.70
Flags: Active, Multicast
Total down time: 0 sec, Last down: Never
ATM per-VC transmit statistics:
Tail queue packet drops: 0
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Flags: Point-To-Multipoint No-Multicast SNMP-Traps 0x0 Encapsulation: ATM-VCMUX
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Local statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Flow Statistics :
Self packets : 0
ICMP packets : 0
VPN packets : 0
Address spoofing: 0
No minor session: 0
No more sessions: 0
No NAT gate: 0
No route present: 0
No tunnel found: 0
Policy denied: 0
VCI 1.4
Flags: Active
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
For 4-wire mode (for interface at-1/0/1):
Link-level type: Ethernet-over-ATM, MTU: 1496, Clocking: Internal, Speed:
SHDSL(4-wire)
Speed: SHDSL(4-wire), Loopback: None
Link flags : None
Current address: 00:24:dc:01:cf:a1
Traffic statistics:
Input errors:
L3 incompletes: 0, L2 channel errors: 0, L2 mismatch timeouts: 0,
Resource errors: 0
Output errors:
Resource errors: 0
0 best-effort 0 0 0
SHDSL alarms : None
LINE1_LOSD 0 0 OK
LINE1_LOSW 0 0 OK
LINE2_LOSD 0 0 OK
LINE2_LOSW 0 0 OK
ES 36
SES 36
UAS 47
SHDSL status:
Line termination : STU-R
Annex : Annex B
Line mode : 4-wire
Modem status : Data
Bit rate (kbps) : 4608
Last fail mode : No failure (0x00)
Framer mode : ATM
Dying gasp : Enabled
Framer sync status : In sync
Chipset version : 00
SHDSL statistics:
Loop attenuation (dB) : 0.0
Transmit power (dBm) : 0.0
Receiver gain (dB) : -inf
SNR sampling (dB) : inf
CRC errors : 0
SEGA errors : 0
LOSW errors : 0
Received cells : 0
Transmitted cells : 0
HEC errors : 0
Cell drop : 0
Destination slot: 1
CoS information:
Direction : Output
Limit
% bps % usec
0 best-effort 95 4377600 95 0 low
none
none
Flags: Point-To-Multipoint SNMP-Traps 0x0 Encapsulation: Ether-over-ATM-LLC
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Local statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Transit statistics:
Flow Statistics :
Self packets : 0
ICMP packets : 0
VPN packets : 0
Address spoofing: 0
No minor session: 0
No more sessions: 0
No NAT gate: 0
No route present: 0
No tunnel found: 0
Policy denied: 0
Flags: None
Destination: 18.1.1/24, Local: 18.1.1.1, Broadcast: 18.1.1.255, Generation:
498
VCI 1.71
Flags: Active, Multicast
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Flags: Point-To-Multipoint No-Multicast SNMP-Traps 0x0 Encapsulation: ATM-VCMUX
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Local statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Flow Statistics :
Self packets : 0
ICMP packets : 0
VPN packets : 0
Address spoofing: 0
No minor session: 0
No more sessions: 0
No NAT gate: 0
No route present: 0
No tunnel found: 0
Policy denied: 0
VCI 1.4
Flags: Active
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Related
Documentation
Junos Interfaces Command Reference Guide
Example: Configuring the G.SHDSL Interface on SRX Series Devices
This example shows howto configure the G.SHDSL interface on SRX Series devices.
Overviewon page 286
Requirements
Before you begin:
Configure network interfaces as necessary. See Understanding Ethernet Interfaces
on page 33.
Install the G.SHDSL Mini-PIMin the first slot of the SRX210 chassis.
Connect the SRX210 device to a DSLAM(IP DSLAMand ATMDSLAM).
NOTE: This example uses an SRX210 Services Gateway. The information is
also applicable to the SRX240 Services Gateway.
Overview
Figure20onpage287shows thetopologyfor theG.SHDSLMini-PIMoperatingin2X4-wire
mode.
Figure 20: G.SHDSL Mini-PIMOperating in 2X4-Wire Mode
Figure21 onpage287 shows thetopology for theG.SHDSLMini-PIMoperatingin4X2-wire
mode.
Figure22onpage287 shows thetopology for theG.SHDSLMini-PIMoperatingin1X8-wire
mode.
Determine the operating wire mode (2-wire, 4-wire, or 8-wire) and corresponding CLI
code listed in Table 43 on page 288.
Table 43: Operating Wire Modes
CLI Code Wire Mode Configuration
set chassis fpc 1 pic 0shdsl pic-mode 1-port-atm 1x8-wire Configuration
NOTE: The2x4-wireconfigurationis thedefault configurationandbehavior.
2x4-wire Configuration
set chassis fpc 1 pic 0shdsl pic-mode 4-port-atm 4x2-wire Configuration
NOTE: When the wire mode is set to 8-wire, one physical interface (IFD) is
created. Similarly for 2-wire mode and 4-wire mode, four IFDs and two IFDs
are created, respectively.
The FPC used in this example will be fpc 1.
Configuration
Basic Configuration of the G.SHDSL Interface on page 288
G.SHDSL Interface Configuration When Connected to an IP DSLAMon page 289
G.SHDSL Interface Configuration When Connected to an ATMDSLAMon page 289
Configuring PPPoE over ATMfor the G.SHDSL Interface on page 290
Configuring PPPoA over ATMfor the G.SHDSL Interface on page 292
Basic Configuration of the G.SHDSL Interface
CLI Quick
Configuration
To quickly performbasic configuration of the G.SHDSL interface, copy the following
[edit]
set interfaces at-1/0/0shdsl-options line-rate 4096
set interfaces at-1/0/0shdsl-options annex annex-a
Step-by-Step
Procedure
To performbasic configuration of the G.SHDSL interface:
Select the operating wire mode. 1.
[edit]
2. Configure the line rates.
[edit]
user@host# set interfaces at-1/0/0shdsl-options line-rate 4096
3. Set the annex type.
[edit]
user@host# set interfaces at-1/0/0shdsl-options annex annex-a
G.SHDSL Interface Configuration When Connected to an IP DSLAM
CLI Quick
Configuration
To quickly configure the G.SHDSL interface on an SRX210 device when it is connected
to an IP DSLAM, copy the following commands and paste theminto the CLI:
[edit]
set interfaces at-1/0/0atm-options vpi 0
set interfaces at-1/0/0unit 0encapsulation ether-over-atm-llc
set interfaces at-1/0/0unit 0vci 0.60
set interfaces at-1/0/0unit 0family inet address 1.1.1.1/24
Step-by-Step
Procedure
To configure the G.SHDSL interface on an SRX210 device when it is connected to an IP
DSLAM:
1. Specify the type of encapsulation on the G.SHDSL interface.
[edit]
2. Configure the ATMVPI options for the interface.
[edit]
user@host# set interfaces at-1/0/0atm-options vpi 0
3. Specify the type of encapsulation on the G.SHDSL logical interface.
[edit]
user@host# set interfaces at-1/0/0unit 0encapsulation ether-over-atm-llc
4. Configure the ATMVCI options for the logical interface.
[edit]
user@host# set interfaces at-1/0/0unit 0vci 0.60
5. Configure the interface address for the logical interface.
[edit]
user@host# set interfaces at-1/0/0unit 0family inet address 1.1.1.1/24
G.SHDSL Interface Configuration When Connected to an ATMDSLAM
CLI Quick
Configuration
To quickly configure the G.SHDSL interface on an SRX210 device when it is connected
to an ATMDSLAM, copy the following commands and paste theminto the CLI:
[edit]
set interfaces at-1/0/0encapsulation atm-pvc
set interfaces at-1/0/0unit 0encapsulation atm-snap
set interfaces at-1/0/0unit 0family inet address 2.1.1.1/24
Step-by-Step
Procedure
To configure the G.SHDSL interface on an SRX210device when it is connected to an ATM
DSLAM:
1. Specify the type of encapsulation on the G.SHDSL interface.
[edit]
user@host# set interfaces at-1/0/0encapsulation atm-pvc
[edit]
[edit]
user@host# set interfaces at-1/0/0unit 0encapsulation atm-snap
[edit]
5. Configure the interface address for the logical interface.
[edit]
Configuring PPPoE over ATMfor the G.SHDSL Interface
CLI Quick
Configuration
To quickly configure PPPoE over ATMon the G.SHDSL interface on an SRX210 device
when it is connected to an IP DSLAM, copy the following commands and paste them
into the CLI:
[edit]
set interfaces at-1/0/0unit 0encapsulation ppp-over-ether-over-atm-llc
set interfaces pp0unit 0ppp-options pap access-profile pap_prof
set interfaces pp0unit 0ppp-options pap local-name srx-210
set interfaces pp0unit 0ppp-options pap local-password
"$9$0tLw1SeN-woJDSr-wY2GU69Cp1RSre"
set interfaces pp0unit 0ppp-options pap passive
set interfaces pp0unit 0pppoe-options underlying-interface at-1/0/0.0
set interfaces pp0unit 0pppoe-options auto-reconnect 120
set interfaces pp0unit 0pppoe-options client
set interfaces pp0unit 0family inet negotiate-address
Step-by-Step
Procedure
To configuring PPPoE over ATMon the G.SHDSL interface on an SRX210 device when it
is connected to an IP DSLAM:
[edit]
[edit]
ppp-over-ether-over-atm-llc
[edit]
4. Configure a PPPoE interface with the PAP access profile.
[edit]
user@host# set interfaces pp0unit 0ppp-options pap access-profile pap_prof
5. Configure a local-name for the PAP interface.
[edit]
user@host# set interfaces pp0unit 0ppp-options pap local-name srx-210
6. Configure a local-password for the PAP interface.
[edit]
user@host# set interfaces pp0unit 0ppp-options pap local-password
"$9$0tLw1SeN-woJDSr-wY2GU69Cp1RSre"
7. Set the passive option to handle incoming PAP packets only.
[edit]
user@host# set interfaces pp0unit 0ppp-options pap passive
8. Specify the logical interface as the underlying interface for the PPPoE session.
[edit]
user@host#set interfacespp0unit 0pppoe-optionsunderlying-interfaceat-1/0/0.0
9. Specify the number of seconds (from1 through 4,294,967,295) to wait before
reconnecting after a PPPoE session is terminated.
[edit]
user@host# set interfaces pp0unit 0pppoe-options auto-reconnect 120
10. Specify the logical interface as the client for the PPPoE interface.
[edit]
user@host# set interfaces pp0unit 0pppoe-options client
11. Obtain an IP address by negotiation with the remote end.
[edit]
user@host# set interfaces pp0unit 0family inet negotiate-address
Configuring PPPoAover ATMfor the G.SHDSL Interface
CLI Quick
Configuration
To quickly configure PPPoA over ATMon the G.SHDSL interface on an SRX210 device
when it is connected to an IP DSLAM, copy the following commands and paste them
into the CLI:
[edit]
set interfaces at-1/0/0encapsulation atm-pvc
set interfaces at-1/0/0unit 0encapsulation atm-ppp-llc
set interfaces at-1/0/0unit 0ppp-options chap access-profile juniper
set interfaces at-1/0/0unit 0ppp-options chap local-name srx-210
set interfaces at-1/0/0unit 0family inet negotiate-address
Step-by-Step
Procedure
To configuring PPPoA over ATMon the G.SHDSL interface on an SRX210 device when it
is connected to an IP DSLAM:
[edit]
[edit]
3. Specify the type of encapsulation on the G.SHDSL logical interface for PPP over
ATMadaptation layer 5 (AAL5) logical link control (LLC).
NOTE: For PPPover ATMAAL5 multiplex, enter this code: set interfaces
at-1/0/0unit 0encapsulation atm-ppp-vc-mux
[edit]
user@host# set interfaces at-1/0/0unit 0encapsulation atm-ppp-llc
[edit]
5. Configure a PPPoA interface with the CHAP access profile.
[edit]
user@host# set interfaces at-1/0/0unit 0ppp-options chap access-profile juniper
6. Configure a local-name for the CHAP interface.
[edit]
user@host# set interfaces at-1/0/0unit 0ppp-options chap local-name srx-210
7. Obtain an IP address by negotiation with the remote end.
[edit]
user@host# set interfaces at-1/0/0unit 0family inet negotiate-address
Verification
Verifying G.SHDSL Interface Properties on page 293
Verifying G.SHDSL Interface Properties
Purpose Verify that the G.SHDSL interface properties are configured properly.
Related
Documentation
Junos Interfaces Command Reference Guide
CHAPTER 13
VDSL2 Mini-PIMInterfaces
VDSL2 Mini-PIMInterface Technology Overviewon page 295
VDSL2 Network Deployment Topology on page 296
VDSL2 Mini-PIMSupport on the SRX210and SRX240Services Gateways on page 297
Example: Configuring the VDSL2 Interface Properties on page 299
Example: Configuring VDSL2 Interfaces on page 303
Example: Configuring ADSL Interfaces on page 328
VDSL2 Mini-PIMInterface Technology Overview
Very-high-bit-rate digital subscriber line (VDSL) technology is part of the xDSL family of
modemtechnologies that provide faster data transmission over a single flat untwisted
or twisted pair of copper wires. The VDSL lines connect service provider networks and
customer sites to provide high bandwidth applications (Triple Play services) such as
high-speed Internet access, telephone services like voice over IP (VoIP), high-definition
TV (HDTV), and interactive gaming services over a single connection.
VDSL2is anenhancement toG.993.1 (VDSL) andpermits thetransmissionof asymmetric
and symmetric (full-duplex) aggregate data rates up to 100Mbps on short copper loops
using a bandwidth up to 30 MHz. The VDSL2 technology is based on the ITU-T G.993.2
(VDSL2) standard which is the International Telecommunication Union standard
describing a data transmission method for VDSL2 transceivers.
The VDSL2 uses discrete multitone (DMT) modulation. DMT is a method of separating
a digital subscriber line signal so that the usable frequency range is separated into 256
frequency bands (or channels) of 4.3125 KHz each. The DMT uses the Fast Fourier
Transform(FFT) algorithmfor demodulation or modulation for increased speed.
VDSL2 interface supports Packet Transfer Mode (PTM). The PTMmode transports
packets (IP, PPP, Ethernet, MPLS, and so on) over DSL links as an alternative to using
Asynchronous Transfer Mode(ATM). PTMis basedontheEthernet intheFirst Mile(EFM)
IEEE802.3ah standard.
VDSL2 provides backward compatibility with ADSL, ADSL2, and ADSL2+ because this
technology is based on both the VDSL1-DMT and ADSL2/ADSL2+ recommendations.
Related
Documentation
VDSL2 Network Deployment Topology
In standard telephone cables of copper wires, voice signals use only a fraction of the
available bandwidth. Like any other DSL technology, the VDSL2 technology utilizes the
remaining capacity to carry the data and multimedia on the wire without interrupting the
line's ability to carry voice signals.
This example depicts the typical VDSL2 network topology deployed using SRX Series
Services Gateways.
A VDSL2 link between network devices is set up as follows:
1. Connect an end-user device such as a LAN, hub, or PC through an Ethernet interface
to the customer premises equipment (CPE) (for example, an SRX Series device).
2. Use an RJ-11 cable to connect the CPE to a DSLAM.
3. The VDSL2 interface uses either Gigabit Ethernet or fiber as second mile to connect
to the Broadband Remote Access Server (B-RAS) as shown in Figure 23 on page 297.
4. The ADSL interface uses either Gigabit Ethernet (in case of IPDSLAM] as the second
mile to connect to the B-RAS or OC3/DS3 ATMas the second mile to connect the
B-RAS as shown in Figure 24 on page 297.
NOTE: TheVDSL2technology is backwardcompatiblewithADSL. VDSL2
provides an ADSL interface in an ATMDSLAMtopology and provides a
VDSL2 interface in an IP or VDSL DSLAMtopology.
The DSLAMaccepts connections frommany customers and aggregates themto a
single, high-capacity connection to the Internet.
Figure 23 on page 297 shows a typical VDSL2 network topology.
Figure23: Typical VDSL2End-to-EndConnectivityandTopologyDiagram
Figure 24on page 297 shows a backward-compatible ADSL topology using ATMDSLAM.
Figure 24: Backward-Compatible ADSL Topology (ATMDSLAM)
Related
Documentation
VDSL2 Mini-PIMSupport on the SRX210and SRX240Services Gateways
The SRX210 and SRX240 Services Gateways support the VDSL2 Mini-PIM(Annex A).
The VDSL2 Mini-Physical Interface Module (Mini-PIM) carries the Ethernet backplane.
When the Mini-PIMis plugged into the chassis, the Mini-PIMconnects to one of the ports
Chapter 13: VDSL2 Mini-PIMInterfaces
of the baseboard switch. The VDSL2 Mini-PIMon the SRX Series devices provides ADSL
backward compatibility.
The VDSL2 Mini-PIM(Annex A) is compatible with ITU-T G.993.2 (VDSL2) standard.
VDSL2 Mini-PIMSupported Profiles
A profile is a table that contains a list of preconfigured VDSL2 settings. Table 44 on
page298lists thedifferent profiles supportedontheVDSL2Mini-PIMandtheir properties.
Table 44: Supported Profiles on the VDSL2 Mini-PIM
Data Rate Profiles
50 8a
50 8b
50 8c
50 8d
68 12a
68 12b
100 17a
Auto mode (default) Auto
VDSL2 Mini-PIMSupported Features
The following features are supported on the VDSL2 Mini-PIM:
ADSL/ADSL2/ADSL2+ backward compatibility with Annex-A, Annex-Msupport
PTMor EFM(802.3ah) support
Operation, Administration, and Maintenance (OAM) support for ADSL/ADSL/ADSL2+
mode
ATMquality of service (QoS) (supported only when the VDSL2 Mini-PIMis operating
in ADSL2 mode)
Multilink Point-to-Point Protocol (MLPPP) (supported only when the VDSL2 Mini-PIM
is operating in ADSL2 mode)
MTU size of 1500 bytes (maximum)
Support for maximumof 10 permanent virtual connections (PVCs) (only in
ADSL/ADSL2/ADSL2+ mode)
Dying gasp support (ADSL and VDSL2 mode)
Related
Documentation
Example: Configuring the VDSL2 Interface Properties
This example shows howto configure the VDSL2 Mini-PIMproperties for the SRX210
and SRX240 Services Gateways.
Overviewon page 299
Requirements
Before you begin:
Establish basic connectivity. See the Quick Start for your services gateway.
Configure network interfaces as necessary. See Example: Creating an Ethernet
Overview
This example shows howto configure the VDSL2 Mini-PIMproperties for the SRX210
and SRX240 Services Gateways.
NOTE: The VDSL2 Mini-PIMhas backward compatibility with
ADSL/ADSL2/ADSL2+. TheVDSL2interfaceisrepresentedbythept interface
whenconfiguredtofunctionasVDSL2, andtheADSLinterfaceisrepresented
by the at interface when configured to function as ADSL.
Configuration
CLI Quick
Configuration
Toquickly configuretheVDSL2Mini-PIMproperties for theSRX210andSRX240Services
Gateways, copy the following commands and paste theminto the CLI.
[edit]
edit interfaces pt-1/0/0
set interfaces pt-1/0/0vdsl-options vdsl-profile auto
set interfaces pt-1/0/0unit 0
set interfaces pt-1/0/0unit 0encapsulation ppp-over-ether
set interfaces pt-1/0/0unit 0family inet
Step-by-Step
Procedure
To configure the VDSL2 Mini-PIMproperties for the SRX210 and SRX240 Services
Gateways:
1. Navigate to the Interfaces level in the configuration hierarchy.
[edit]
user@host# edit interfaces pt-1/0/0
2. Configure the type of VDSL2 profiles.
[edit]
user@host# set interfaces pt-1/0/0vdsl-options vdsl-profile auto
The following profiles are supported:
8a
8b
8c
8d
12a
12b
17a
auto (default)
3. Defines one or more logical units to connect to this physical VDSL interface. Set a
value from0 through 16385. Add other values if required by your network.
[edit]
user@host# set interfaces pt-1/0/0unit 0
4. Specify the type of encapsulationonthe VDSL logical interface. Use ppp-over-ether
for Point-to-Point Protocol over Ethernet (PPPoE) over VDSL interfaces that carry
IPv4 traffic.
NOTE: PPPoE is supported for the VDSL2 interface. You can also set
no encapsulation for the VDSL2 interface.
[edit]
user@host# set interfaces pt-1/0/0unit 0encapsulation ppp-over-ether
[edit]
user@host# set interfaces pt-1/0/0unit 0family inet
Results Fromconfiguration mode, confirmyour configuration by entering the run showinterface
pt-1/0/0command. If the output does not display the intended configuration, repeat the
NOTE: See ATM-over-ADSL Interfaces for details about configuring the
interface when operating in ADSL mode.
Verification
Verifying the Configuration on page 301
Verifying the Configuration
Purpose Verify the command output.
Action Enter run showinterface pt-1/0/0 and verify the following information in the command
output:
Status of interface pt-1/0/0 is displayed as physical link is up.
Modemstatus is displayed as Showtime (Profile-17a).
Time in seconds during which the interface stayed up is displayed as Seconds in
Showtime.
VDSL profile is displayed as Auto Annex A.
Physical interface: pt-1/0/0, Enabled, Physical link is Up
Type: PTM, Link-level type: Ethernet, MTU: 1496, VDSL mode, Speed: 45440kbps
Speed: VDSL2
Link flags : None
Current address: 00:b1:7e:85:84:ff
Traffic statistics:
Input bytes : 22438962 97070256 bps
Output bytes : 10866024 43334088 bps
Input errors:
Errors: 0, Drops: 0, Policed discards: 0, L3 incompletes: 0,
L2 channel errors: 0, L2 mismatch timeouts: 0, Resource errors: 0
Output errors:
Resource errors: 0
VDSL alarms : None
VDSL defects : None
VDSL media: Seconds Count State
LOF 0 0 OK
LOS 0 0 OK
LOM 0 0 OK
LOP 0 0 OK
LOCDI 0 0 OK
LOCDNI 0 0 OK
VDSL status:
Modem status : Showtime (Profile-17a)
VDSL profile : Profile-17a Annex A
Subfunction : 0x00
VDSL Chipset Information: VTU-R VTU-C
Vendor Country : 0xb5 0xb5
Vendor ID : BDCM BDCM
Vendor Specific: 0x9385 0x9385
VDSL Statistics: VTU-R VTU-C
Capacity used (%) : 0 0
Noise margin (dB) : 20.0 20.0
Bit rate (kbps) : 100004 0 45440 0
CRC : 0 0 0 0
FEC : 0 0 0 0
HEC : 0 0 0 0
Destination slot: 0 (0x00)
CoS information:
Direction : Output
Limit
% bps % usec
0 best-effort 95 43168000 95 0 low
none
none
Logical interface pt-1/0/0.0 (Index 71) (SNMP ifIndex 525) (Generation 136)
Traffic statistics:
Input bytes : 23789064
Input packets: 16052
Local statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Transit statistics:
Input bytes : 23789064 97070256 bps
Output bytes : 10866024 43334088 bps
Flow Statistics :
Self packets : 0
ICMP packets : 0
VPN packets : 0
Address spoofing: 0
No minor session: 0
No more sessions: 0
No NAT gate: 0
No route present: 0
No tunnel found: 0
Policy denied: 0
Flags: None
Destination: 10.10.10/24, Local: 10.10.10.1, Broadcast: 10.10.10.255,
Generation: 158
Related
Documentation
Understanding Interfaces on page 3.
Example: Configuring VDSL2 Interfaces
This exampleshows howtoconfigureVDSL2interfaces onSRXSeries Services Gateways.
Overviewon page 304
Requirements
Before you begin:
Install Junos OS Release 10.1 or later on the SRX Series devices.
Set up and performinitial configuration on the SRX Series devices.
Install the VDSL2 Mini-PIMon the SRX210 device chassis.
Connect the SRX210 device to a DSLAM.
On VDSL2 Mini-PIMs, by default the pt-1/0/0 interface is created when there is no
configuration already created for either the pt-1/0/0 or the at-1/0/0 interface. You can
switch to ADSL mode by just configuring at-1/0/0. If the configurations are already
created for pt-1/0/0 or at-1/0/0, then you need to deactivate pt-1/0/0 before you
create at-1/0/0 or deactivate at-1/0/0 to create pt-1/0/0.
Make sure that you have deleted the previous configurations on pt-1/0/0 and pp0.
Overview
This exampleuses SRX210devices. Theinformationis alsoapplicabletoSRX240devices.
The SRX210and SRX240devices support the VDSL2 Mini-PIM(Annex A), Which carries
the Ethernet backplane. When the Mini-PIMis plugged into the chassis, the Mini-PIM
connects to one of the ports of the baseboard switch. The VDSL2 Mini-PIMon the SRX
Series devices provides ADSL backward compatibility.
Figure 25 on page 304 shows typical SRX Series devices with VDSL2 Mini-PIMnetwork
connections.
Figure 25: SRX Series devices with VDSL2 Mini-PIMs in an End-to-End
Deployment Scenario
In this example, you begin a newconfiguration on a VDSL2 Mini-PIM. You first deactivate
previous interfaces and delete any old configuration fromthe device. Then you set the
interfaces with the VDSL profile and the Layer 3 configuration for the end-to-end data
path.
You then configure the PPPoE on the pt-1/0/0interface with a static IPaddress or CHAP
authentication. You configure PPPoE on the pt-1/0/0 interface with unnumbered IP
address (PAP authentication or CHAP authentication).
Finally, you configure PPPoE on the pt-1/0/0 interface with negotiated IP address (PAP
authentication or CHAP authentication).
Configuration
Beginning a NewConfiguration on a VDSL2 Mini-PIMon page 305
Configuring the VDSL2 Mini-PIMfor End-to-End Data Path on page 306
Configuring PPPoE on the pt-1/0/0 Interface with a Static IP Address on page 307
Configuring PPPoE on the pt-1/0/0 Interface with a Static IP Address (CHAP
Authentication) on page 308
Configuring PPPoE on the pt-x/x/x Interface with Unnumbered IP (PAP
Configuring PPPoE on the pt-1/0/0 Interface with Unnumbered IP (CHAP
Configuring PPPoE on the pt-1/0/0 Interface with Negotiated IP (PAP
Configuring PPPoE on the pt-1/0/0 Interface with Negotiated IP (CHAP
Beginning a NewConfiguration on a VDSL2 Mini-PIM
CLI Quick
Configuration
Toquickly beginanewconfigurationonaVDSL2Mini-PIM, copy thefollowingcommands
and paste theminto the CLI:
[edit]
deactivate interface pt-1/0/0
deactivate interface at-1/0/0
delete interface pt-1/0/0
delete interface pp0
Step-by-Step
Procedure
To begin a newconfiguration on a VDSL2 Mini-PIM:
Deactivate any previous interfaces. 1.
[edit]
user@host# deactivate interface pt-1/0/0
user@host# deactivate interface at-1/0/0
2. Delete any old configurations.
[edit]
user@host# delete interface pt-1/0/0
user@host# delete interface pp0
[edit]
user@host# commit
Results Fromconfiguration mode, confirmyour configuration by entering the showchassis fpc
[edit]
user@host# show chassis fpc
Temp CPU Utilization (%) Memory Utilization
(%)
1 Empty
2 Empty
3 Empty
4 Empty
Configuring the VDSL2 Mini-PIMfor End-to-End Data Path
CLI Quick
Configuration
To quickly configure the VDSL2 Mini-PIMfor end-to-end data path, copy the following
[edit]
set interfaces pt-1/0/0vdsl-options vdsl-profile 17a
set interfaces pt-1/0/0unit 0family inet address 11.11.11.1/24
Step-by-Step
Procedure
To configure the VDSL2 Mini-PIMfor end-to-end data path:
Configure the interfaces with the VDSL profile and the Layer 3 configuration for
end-to-end data path.
1.
[edit]
user@host# set interfaces pt-1/0/0vdsl-options vdsl-profile 17a
user@host# set interfaces pt-1/0/0unit 0family inet address 11.11.11.1/24
[edit]
user@host# commit
pt-1/0/0command. If the output does not display the intended configuration, repeat the
[edit]
user@host# showinterfaces pt-1/0/0
vdsl-options {
vdsl-profile 17a;
}
unit 0 {
family inet {
address 11.11.11.1/24;
}
}
Configuring PPPoE on the pt-1/0/0Interface with a Static IP Address
CLI Quick
Configuration
To quickly configure PPPoE on the pt-1/0/0 interface with a static IP address, copy the
[edit]
user@host#set interfacespp0unit 0ppp-optionspapaccess-profilepap_prof local-name
locky local-password india passive
user@host# set interfaces pp0unit 0pppoe-options underlying-interface pt-1/0/0.0
auto-reconnect 120client
user@host# set interfaces pp0unit 0family inet address 10.1.1.6/24
user@host# set access profile pap_prof authentication-order password client cuttack
pap-password india
Step-by-Step
Procedure
To configure the PPPoE on the pt-1/0/0 interface with a static IP address:
Configure the VDSL options and encapsulation for the interface. 1.
[edit]
2. Configure the PPP-options for the interface.
[edit]
user@host# set interfaces pp0unit 0ppp-options pap local-name locky
user@host# set interfaces pp0unit 0ppp-options pap local-password india
3. Configure the PPPoE-options for the interface.
[edit]
user@host#set interfacespp0unit 0pppoe-optionsunderlying-interfacept-1/0/0.0
4. Configure the IP address for the interface.
[edit]
5. Configure the access profile for the interface.
[edit]
user@host# set access profile pap_prof authentication-order password
user@host# set access profile pap_prof client cuttack pap-password india
pp0, showinterfaces pt-1/0/0and showaccess profile pap_prof commands. If the output
does not display the intended configuration, repeat the configuration instructions in this
example to correct it.
[edit]
user@host# showinterfaces pp0
unit 0 {
ppp-options {
pap {
access-profile pap_prof;
local-name locky;
local-password "$9$pZC701h7Nbg4ZKM87"; ## SECRET-DATA
passive;
}
}
pppoe-options {
underlying-interface pt-1/0/0.0;
auto-reconnect 120;
client;
}
family inet {
address 10.1.1.6/24;
}
}
[edit]
vdsl-options {
vdsl-profile 17a;
}
unit 0 {
encapsulation ppp-over-ether;
}
[edit]
user@host# showaccess profile pap_prof
authentication-order password;
client cuttack pap-password "$9$rkieMXaJDq.5bs2a"; ## SECRET-DATA
Configuring PPPoE on the pt-1/0/0Interface with a Static IP Address (CHAP
Authentication)
CLI Quick
Configuration
To quickly configure PPPoE on the pt-1/0/0 interface with a static IP address (CHAP
authentication), copy the following commands and paste theminto the CLI:
[edit]
user@host# set interfaces pp0unit 0ppp-options chap default-chap-secret india
local-name locky passive
Step-by-Step
Procedure
To configure the PPPoE on the pt-1/0/0 interface with a static IP address (CHAP
Authentication):
1. Configure the VDSL options and encapsulation for the interface.
[edit]
[edit]
user@host# set interfaces pp0unit 0ppp-options chap local-name locky
user@host# set interfaces pp0unit 0ppp-options chap passive
[edit]
[edit]
pt-1/0/0andshowinterfacespp0commands. If theoutput does not display theintended
[edit]
vdsl-options {
vdsl-profile 17a;
}
unit 0 {
}
[edit]
unit 0 {
ppp-options {
chap {
default-chap-secret "$9$9hAtAu18LNws4ylK8"; ## SECRET-DATA
local-name locky;
passive;
}
}
pppoe-options {
auto-reconnect 120;
client;
}
family inet {
address 10.1.1.6/24;
}
}
Configuring PPPoE on the pt-x/x/x Interface with Unnumbered IP (PAP
Authentication)
CLI Quick
Configuration
To quickly configure PPPoE on the pt-1/0/0 interface with unnumbered IP (PAP
[edit]
user@host# set interfaces lo0unit 0family inet address 10.1.1.24/32
user@host#set interfacespp0unit 0ppp-optionspapaccess-profilepap_prof local-name
locky local-password india passive
user@host#set interfaces pp0unit 0family inet unnumbered-address lo0.0destination
10.1.1.1
user@host# set access profile pap_prof authentication-order password client cuttack
pap-password india
Step-by-Step
Procedure
Toconfigure PPPoEonthe pt-1/0/0interface withunnumberedIP(PAPauthentication):
[edit]
[edit]
[edit]
user@host# set interfaces pp0unit 0ppp-options pap local-name locky
user@host# set interfaces pp0unit 0ppp-options pap local-password india
[edit]
5. Configure the unnumbered address and destination for the interface.
[edit]
user@host# set interfaces pp0unit 0family inet unnumbered-address lo0.0
user@host#set interfaces pp0unit 0family inet unnumbered-address destination
10.1.1.1
[edit]
user@host# set access profile pap_prof authentication-order password
user@host# set access profile pap_prof client cuttack pap-password india
Results Fromconfiguration mode, confirmyour configuration by entering the showinterfaces lo0,
showinterfaces pt-1/0/0, and showinterfaces pp0 commands. If the output does not
display the intended configuration, repeat the configuration instructions in this example
to correct it.
[edit]
user@host# showinterfaces lo0
unit 0 {
family inet {
address 10.1.1.24/32;
}
}
[edit]
vdsl-options {
vdsl-profile 17a;
}
unit 0 {
}
[edit]
unit 0 {
ppp-options {
pap {
access-profile pap_prof;
local-name locky;
local-password "$9$3vvL6CuKvL-dsEcyK"; ## SECRET-DATA
passive;
}
}
pppoe-options {
auto-reconnect 120;
client;
}
family inet {
}
}
Configuring PPPoE on the pt-1/0/0Interface with Unnumbered IP (CHAP
Authentication)
CLI Quick
Configuration
To quickly configure PPPoE on the pt-1/0/0 interface with unnumbered IP (CHAP
Authentication), copy the following commands and paste theminto the CLI:
[edit]
local-name locky passive
user@host#set interfaces pp0unit 0family inet unnumbered-address lo0.0destination
10.1.1.1
Step-by-Step
Procedure
ToconfigurePPPoEonthept-1/0/0interfacewithunnumberedIP(CHAPauthentication):
[edit]
[edit]
[edit]
user@host# set interfaces pp0unit 0ppp-options chap local-name locky
[edit]
5. Configure the unnumbered address and destination for the interface.
[edit]
user@host# set interfaces pp0unit 0family inet unnumbered-address lo0.0
user@host#set interfaces pp0unit 0family inet unnumbered-address destination
10.1.1.1
pp0, showinterfaces pt-1/0/0, and showinterfaces lo0 commands. If the output does
not display the intended configuration, repeat the configuration instructions in this
[edit]
unit 0 {
ppp-options {
chap {
default-chap-secret "$9$BqgIhrVb2JZj8X7V"; ## SECRET-DATA
local-name locky;
passive;
}
}
pppoe-options {
auto-reconnect 120;
client;
}
family inet {
}
}
[edit]
vdsl-options {
vdsl-profile 17a;
}
unit 0 {
}
[edit]
user@host# showinterfaces lo0
unit 0 {
family inet {
address 10.1.1.24/32;
}
}
Configuring PPPoE on the pt-1/0/0Interface with Negotiated IP (PAP
Authentication)
CLI Quick
Configuration
To quickly configure PPPoE on the pt-1/0/0 interface with negotiated IP (PAP
[edit]
user@host#set interfaces pp0unit 0ppp-options papaccess-profilemy_prf local-name
purple local-password Embe1mpls passive
user@host# set access profile my_prf authentication-order password
user@host# set access profile my_prf
Step-by-Step
Procedure
To configure PPPoE on the pt-1/0/0 interface with negotiated IP (PAP authentication):
[edit]
[edit]
user@host# set interfaces pp0unit 0ppp-options pap access-profile my_prf
user@host# set interfaces pp0unit 0ppp-options pap local-name purple
user@host#set interfaces pp0unit 0ppp-options pap local-password Embe1mpls
[edit]
4. Configure the negotiated IP address for the interface.
[edit]
[edit]
pt-1/0/0, showinterfaces pp0, and showaccess profile my_prf commands. If the output
does not display the intended configuration, repeat the configuration instructions in this
[edit]
vdsl-options {
vdsl-profile 17a;
}
unit 0 {
}
[edit]
unit 0 {
ppp-options {
pap {
access-profile my_prf;
local-name purple;
local-password "$9$2U4aGQz6CA0GD/CtOcSVwY2aUHqf"; ## SECRET-DATA
passive;
}
}
pppoe-options {
auto-reconnect 120;
client;
}
family inet {
negotiate-address;
}
}
[edit]
user@host# showaccess profile my_prf
authentication-order password;
Configuring PPPoE on the pt-1/0/0Interface with Negotiated IP (CHAP
Authentication)
CLI Quick
Configuration
To quickly configure PPPoE on the pt-1/0/0 interface with negotiated IP (CHAP
[edit]
user@host#set interfaces pp0unit 0ppp-options chapdefault-chap-secret Embe1mpls
local-name purple passive
Step-by-Step
Procedure
Toconfigure PPPoEon the pt-1/0/0interface with negotiatedIP(CHAPAuthentication):
[edit]
[edit]
user@host# set interfaces pp0unit 0ppp-options chap default-chap-secret
Embe1mpls
user@host# set interfaces pp0unit 0ppp-options chap local-name purple
[edit]
4. Configure the negotiated IP address for the interface.
[edit]
pp0andshowinterfaces pt-1/0/0commands. If the output does not display the intended
[edit]
unit 0 {
ppp-options {
chap {
default-chap-secret "$9$M4B8XNZGiq.5NdHqmT/9revMX-wYo"; ## SECRET-DATA
local-name purple;
passive;
}
}
pppoe-options {
auto-reconnect 120;
client;
}
family inet {
negotiate-address;
}
}
[edit]
vdsl-options {
vdsl-profile 17a;
}
unit 0 {
}
Verification
Verifying the VDSL2 Mini-PIMfor End-to-End Data Path on page 319
Verifying PPPoE on the pt-1/0/0 Interface with a Static IP Address on page 322
Verifying PPPoE on the pt-1/0/0 Interface with a Static IP Address (CHAP
Verifying PPPoE on the pt-1/0/0 Interface with Unnumbered IP (PAP
Verifying PPPoE on the pt-1/0/0 Interface with Unnumbered IP (CHAP
Verifying PPPoE on the pt-1/0/0 Interface with Negotiated IP (PAP
Verifying PPPoE on the pt-1/0/0 Interface with Negotiated IP (CHAP
Purpose Verify the FPC status and the command output.
Action Verify the FPC status by entering the showchassis fpc command. The output should
display FPC status as online.
1.
user@host# run show chassis fpc
Temp CPU Utilization (%) Memory Utilization
(%)
NOTE: The VDSL2 Mini-PIMis installed in the first slot of the SRX210
device chassis; therefore, the FPC used here is fpc 1. For SRX240 devices,
the FPC used will be fpc 1, fpc 2, fpc 3, or fpc 4.
2. Enter runshowinterfacept-1/0/0andverify thefollowinginformationinthecommand
output:
Status of interface pt-1/0/0 is displayed as physical link is up.
Modemstatus is displayed as Showtime (Profile-17a).
Time in seconds during which the interface stayed up is displayed as Seconds in
Showtime.
VDSL profile is displayed as Auto Annex A.
Type: PTM, Link-level type: Ethernet, MTU: 1496, VDSL mode, Speed:
45440kbps
Speed: VDSL2
Link flags : None
Traffic statistics:
Input bytes : 22438962 97070256 bps
Output bytes : 10866024 43334088 bps
Input errors:
Errors: 0, Drops: 0, Policed discards: 0, L3 incompletes: 0,
L2 channel errors: 0, L2 mismatch timeouts: 0, Resource errors: 0
Output errors:
Carrier transitions: 0, Errors: 0, Drops: 0, Aged packets: 0, MTU
errors: 0,
Resource errors: 0
VDSL alarms : None
VDSL defects : None
LOF 0 0 OK
LOS 0 0 OK
LOM 0 0 OK
LOP 0 0 OK
LOCDI 0 0 OK
LOCDNI 0 0 OK
VDSL status:
Subfunction : 0x00
Bit rate (kbps) : 100004 0 45440 0
CRC : 0 0 0 0
FEC : 0 0 0 0
HEC : 0 0 0 0
CoS information:
Direction : Output
Limit
% bps % usec
0 best-effort 95 43168000 95 0 low
none
none
Logical interface pt-1/0/0.0 (Index 71) (SNMP ifIndex 525) (Generation
136)
Traffic statistics:
Input bytes : 23789064
Input packets: 16052
Local statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
Transit statistics:
Input bytes : 23789064 97070256 bps
Output bytes : 10866024 43334088 bps
Flow Statistics :
Self packets : 0
ICMP packets : 0
VPN packets : 0
Address spoofing: 0
No minor session: 0
No more sessions: 0
No NAT gate: 0
No route present: 0
No tunnel found: 0
Policy denied: 0
Flags: None
Generation: 158
Verifying the VDSL2 Mini-PIMfor End-to-End Data Path
Purpose Verify the interface status and check traffic statistics.
Action Verify interfacestatus by usingtheshowinterfacetersecommandandtest end-to-end
data path connectivity by sending the ping packets to the remote end IP address.
1.
user@host# run show interfaces pt-1/0/0 terse
Interface Admin Link Proto Local Remote
pt-1/0/0 up up
pt-1/0/0.0 up up inet 11.11.11.1/24
[edit]
user@host# run ping 11.11.11.2 count 1000 rapid
PING 11.11.11.2 (11.11.11.2): 56 data bytes
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
- 11.11.11.2 ping statistics ---
1000 packets transmitted, 1000 packets received, 0% packet loss
round-trip min/avg/max/stddev = 16.109/17.711/28.591/2.026 ms
2. Verify the VDSL2 interface configuration and check the traffic statistics.
user@host# run show interfaces pt-1/0/0 extensive
Type: PTM, Link-level type: Ethernet, MTU: 1496, VDSL mode, Speed:
45440kbps
Speed: VDSL2
Link flags : None
Traffic statistics:
Input errors:
Errors: 0, Drops: 0, Policed discards: 0, L3 incompletes: 0, L2 channel
errors: 0, L2 mismatch timeouts: 0, Resource errors: 0
Output errors:
Carrier transitions: 0, Errors: 0, Drops: 0, Aged packets: 0, MTU
errors: 0, Resource errors: 0
Queue counters: Queued packets Transmitted packets Dropped
packets
0 best-effort 1000 1000
0
1 expedited-fo 0 0
0
2 assured-forw 0 0
0
3 network-cont 0 0
0
VDSL alarms : None
VDSL defects : None
LOF 0 0 OK
LOS 0 0 OK
LOM 0 0 OK
LOP 0 0 OK
LOCDI 0 0 OK
LOCDNI 0 0 OK
VDSL status:
Subfunction : 0x00
Interleave Fast Interleave
Fast
Bit rate (kbps) : 100004 0 45440
0
CRC : 0 0 0
0
FEC : 0 0 0
0
HEC : 0 0 0
0
CoS information:
Direction : Output
CoS transmit queue Bandwidth Buffer
Priority Limit
% bps % usec
0 best-effort 95 43168000 95 0
low none
3 network-control 5 2272000 5 0
low none
Logical interface pt-1/0/0.0 (Index 72) (SNMP ifIndex 521) (Generation
158)
Traffic statistics:
Input bytes : 84000
Input packets: 1000
Local statistics:
Input bytes : 84000
Input packets: 1000
Transit statistics:
Flow Statistics :
Self packets : 0
ICMP packets : 0
VPN packets : 0
Address spoofing: 0
No minor session: 0
No more sessions: 0
No NAT gate: 0
No route present: 0
No tunnel found: 0
Policy denied: 0
Flags: None
Destination: 11.11.11/24, Local: 11.11.11.1, Broadcast:
11.11.11.255, Generation: 189
Verifying PPPoE on the pt-1/0/0Interface with a Static IP Address
Purpose Verify the interface output and the end-to-end data path.
Action Verify the interface output. 1.
user@host# run show interfaces pp0
Physical interface: pp0, Enabled, Physical link is Up
Type: PPPoE, Link-level type: PPPoE, MTU: 1532
Link flags : None
Input packets : 0
Output packets: 0
Logical interface pp0.0 (Index 71) (SNMP ifIndex 522)
Flags: Hardware-Down Point-To-Point SNMP-Traps 0x0 Encapsulation:
PPPoE
PPPoE:
State: SessionDown, Session ID: None,
Configured AC name: None, Service name: None,
Auto-reconnect timeout: 120 seconds, Idle timeout: Never,
Underlying interface: pt-1/0/0.0 (Index 69)
Input packets : 57
Output packets: 56
LCP state: Down
NCP state: inet: Down, inet6: Not-configured, iso: Not-configured, mpls:
Not-configured
CHAP state: Closed
PAP state: Closed
Flags: Protocol-Down
Addresses, Flags: Dest-route-down Is-Preferred Is-Primary
Destination: 10.1.1/24, Local: 10.1.1.6
2. Verify the end-to-end data path on the interface.
pt-1/0/0 up up
pt-1/0/0.0 up up
[edit]
user@host# run show interfaces pp0 terse
pp0 up up
pp0.0 up up inet 10.1.1.6/24
[edit]
PING 10.1.1.1 (10.1.1.1): 56 data bytes
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
- 10.1.1.1 ping statistics ---
Verifying PPPoE on the pt-1/0/0Interface with a Static IP Address (CHAP
Authentication)
Purpose Verify the interface status and check the end-to-end data path connectivity.
Action Verify the interface status. 1.
Link flags : None
Input packets : 0
Output packets: 0
Flags: Point-To-Point SNMP-Traps 0x0 Encapsulation: PPPoE
PPPoE:
State: SessionUp, Session ID: 31,
Session AC name: cuttack, Remote MAC address: 00:03:6c:c8:8c:55,
Input packets : 12
Output packets: 10
Keepalive: Input: 1 (00:00:08 ago), Output: 0 (never)
LCP state: Opened
CHAP state: Success
PAP state: Closed
Flags: None
2. Verify the interface and check the end-to-end data path connectivity.
pt-1/0/0 up up
pt-1/0/0.0 up up
[edit]
pp0 up up
pp0.0 up up inet 10.1.1.6/24
[edit]
PING 10.1.1.1 (10.1.1.1): 56 data bytes
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
--- 10.1.1.1 ping statistics ---
Verifying PPPoE on the pt-1/0/0Interface with Unnumbered IP (PAP
Authentication)
Purpose Verify the interface status and the end-to-end data path testing.
Link flags : None
Input packets : 0
Output packets: 0
PPPoE:
Input packets : 22
Output packets: 20
LCP state: Opened
CHAP state: Closed
PAP state: Success
Flags: None
Destination: 10.1.1.1, Local: 10.1.1.24
2. Verify the end-to-end data path testing.
pt-1/0/0 up up
pt-1/0/0.0 up up
[edit]
pp0 up up
pp0.0 up up inet 10.1.1.24 -->
10.1.1.1
[edit]
PING 10.1.1.1 (10.1.1.1): 56 data bytes
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Verifying PPPoE on the pt-1/0/0Interface with Unnumbered IP (CHAP
Authentication)
Purpose Verify the interface status and end-to-end data path testing on the PPPoE interface.
Link flags : None
Input packets : 0
Output packets: 0
PPPoE:
Input packets : 25
Output packets: 22
LCP state: Opened
CHAP state: Success
PAP state: Closed
Flags: None
2. Verify the end-to-end data path testing on the PPPoE interface.
pt-1/0/0 up up
pt-1/0/0.0 up up
[edit]
pp0 up up
pp0.0 up up inet 10.1.1.24 -->
10.1.1.1
[edit]
PING 10.1.1.1 (10.1.1.1): 56 data bytes
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
-- 10.1.1.1 ping statistics ---
Verifying PPPoE on the pt-1/0/0Interface with Negotiated IP (PAP
Authentication)
Purpose Verify the PPPoE interface status and the end-to-end data path connectivity.
Action Verify the PPPoE interface status. 1.
Link flags : None
Input packets : 0
Output packets: 0
PPPoE:
Session AC name: belur, Remote MAC address: 00:90:1a:43:18:d1,
Input packets : 18
Output packets: 18
Keepalive: Input: 0 (never), Output: 11 (00:00:01 ago)
LCP state: Opened
CHAP state: Closed
PAP state: Success
2. Verify the end-to-end data path connectivity.
pt-1/0/0 up up
pt-1/0/0.0 up up
[edit]
pp0 up up
pp0.0 up up inet 12.12.12.11 -->
12.12.12.1
[edit]
PING 12.12.12.1 (12.12.12.1): 56 data bytes
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Verifying PPPoE on the pt-1/0/0Interface with Negotiated IP (CHAP
Authentication)
Purpose Verify the interface status and the end-to-end data path connectivity.
Action Verifying the interface status. 1.
Link flags : None
Input packets : 0
Output packets: 0
PPPoE:
Session AC name: belur, Remote MAC address: 00:90:1a:43:18:d1,
Input packets : 12
Output packets: 11
LCP state: Opened
CHAP state: Success
PAP state: Closed
pt-1/0/0 up up
pt-1/0/0.0 up up
[edit]
pp0 up up
pp0.0 up up inet 12.12.12.12 -->
12.12.12.1
[edit]
PING 12.12.12.1 (12.12.12.1): 56 data bytes
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Related
Documentation
Example: Configuring ADSL Interfaces
This example shows howto configure ADSL interfaces SRX Series Services Gateways.
Overviewon page 329
Requirements
Before you begin:
Install Junos OS Release 10.1 or later for the SRX Series devices.
Set up and performinitial configuration on the SRX Series device.
Install the VDSL2 Mini-PIMon the SRX210 device chassis.
SRX210 device is connected to a DSLAMthat supports VDSL2 to ADSL fallback.
Overview
The SRX210 and SRX240 devices support the VDSL2 Mini-Physical Interface Module
(Mini-PIM) (Annex A). The VDSL2 Mini-PIMcarries the Ethernet backplane. When the
Mini-PIMis plugged into the chassis, the Mini-PIMconnects to one of the ports of the
baseboard switch. The VDSL2 Mini-PIMon the SRX Series devices provides ADSL
backwardcompatibility. TheVDSL2usesEFMor PTMmodeasfirst mileandisrepresented
as pt-x/x/x. In case of ADSL fallback mode, the VDSL2 Mini-PIMoperates on the ATM
encapsulation interface as first mile and is represented as at-x/x/x.
Configuration
This example shows howtoconfigure ADSL interfaces onSRXSeries Services Gateways.
Configuring the ADSL Interface for End-to-End Data Path on page 329
Configuring PPPoA on the at-x/x/x Interface with Negotiated IP (CHAP
Configuring PPPoA on the at-x/x/x Interface with Negotiated IP (PAP
Configuring PPPoA on the at-x/x/x Interface with Static IP (CHAP
Configuring PPPoA on the at-x/x/x Interface with Static IP (PAP
Configuring PPPoA on the at-x/x/x Interface with Unnumbered IP (PAP
Configuring PPPoA on the at-x/x/x Interface with Unnumbered IP (CHAP
Configuring PPPoE over ATMon the at-x/x/x Interface with Negotiated IP (PAP
Configuring PPPoE over ATMon the at-x/x/x Interface with Negotiated IP (CHAP
Configuring the ADSL Interface for End-to-End Data Path
CLI Quick
Configuration
To quickly configure the ADSL Interface for end-to-end data path for "second mile" ATM,
copy the following commands and paste theminto the CLI.
[edit]
user@host# delete interfaces at-1/0/0
user@host# set interfaces at-1/0/0dsl-options operating-mode itu-dmt
Step-by-Step
Procedure
To configure the ADSL interface for end-to-end data path for "second mile" ATM:
Delete any previous configurations. 1.
[edit]
user@host# delete interfaces at-1/0/0
2. Configure the basic configuration details for the ADSL interface.
[edit]
user@host# set interfaces at-1/0/0dsl-options operating-mode itu-dmt
[edit]
user@host# commit
Results Fromconfigurationmode, confirmyour configurationby entering the showinterfaceterse
Configuring PPPoAon the at-x/x/x Interface with Negotiated IP (CHAP
Authentication)
CLI Quick
Configuration
To quickly configure PPPoA on the at-x/x/x interface with negotiated IP (CHAP
Authentication), copy the following commands and paste theminto the CLI.
[edit]
user@host# set interfaces at-1/0/0unit 0ppp-options chap access-profile jnpr
user@host# set interfaces at-1/0/0unit 0ppp-options chap local-name locky
user@host# set access profile jnpr client sringeri chap-secret india
Step-by-Step
Procedure
To configure PPPoAon the at-x/x/x interface with negotiated IP(CHAPAuthentication):
Configure encapsulation and atm-options for the ADSL interface. 1.
[edit]
2. Configure ppp-options for the ADSL interface.
[edit]
3. Configure the negotiated IP address for the ADSL interface.
[edit]
4. Configure the access profile for the ADSL interface.
[edit]
[edit]
user@host# commit
Results Fromconfiguration mode, confirmyour configuration by entering the run showinterfaces
at-1/0/0command. If the output does not display the intended configuration, repeat the
Configuring PPPoAon the at-x/x/x Interface with Negotiated IP (PAP
Authentication)
CLI Quick
Configuration
To quickly configure PPPoA on the at-x/x/x interface with negotiated IP (PAP
[edit]
user@host# set interfaces at-1/0/0dsl-options operating-mode auto
user@host# set interfaces at-1/0/0unit 0ppp-options pap access-profile jnpr
user@host# set interfaces at-1/0/0unit 0ppp-options pap local-name locky
user@host# set interfaces at-1/0/0unit 0ppp-options pap local-password india
user@host# set access profile jnpr client sringeri pap-password india
Step-by-Step
Procedure
To configure PPPoA on the at-x/x/x interface with negotiated IP (PAP Authentication):
[edit]
[edit]
[edit]
[edit]
[edit]
user@host# commit
ConfiguringPPPoAontheat-x/x/xInterfacewithStaticIP(CHAPAuthentication)
CLI Quick
Configuration
Toquickly configurePPPoAontheat-x/x/xinterfacewithstaticIP(CHAPAuthentication),
[edit]
Step-by-Step
Procedure
To configure PPPoA on the at-x/x/x interface with static IP (CHAP Authentication):
[edit]
[edit]
[edit]
[edit]
[edit]
user@host# commit
Configuring PPPoAon the at-x/x/x Interface with Static IP(PAPAuthentication)
CLI Quick
Configuration
To quickly configure PPPoAon the at-x/x/x interface with static IP(PAPAuthentication),
[edit]
Step-by-Step
Procedure
To configure PPPoA on the at-x/x/x interface with static IP (PAP Authentication):
[edit]
[edit]
[edit]
[edit]
[edit]
user@host# commit
Configuring PPPoAon the at-x/x/x Interface with Unnumbered IP (PAP
Authentication)
CLI Quick
Configuration
To quickly configure PPPoA on the at-x/x/x interface with unnumbered IP (PAP
[edit]
user@host# set interfaces at-1/0/0unit 0family inet unnumbered-address lo0.0
user@host# set interfaces at-1/0/0unit 0family inet unnumbered-address destination
100.100.100.6
user@host# set interfaces lo0.0unit 0family inet address 100.100.100.20/32
Step-by-Step
Procedure
To configure PPPoAon the at-x/x/x interface with unnumbered IP(PAPAuthentication):
[edit]
[edit]
3. Configure the IPaddress and unnumbered IPaddress and destination for the ADSL
interface.
[edit]
user@host# set interfaces at-1/0/0unit 0family inet unnumbered-address
destination 100.100.100.6
[edit]
[edit]
user@host# commit
Configuring PPPoAon the at-x/x/x Interface with Unnumbered IP (CHAP
Authentication)
CLI Quick
Configuration
To quickly configure PPPoA on the at-x/x/x interface with unnumbered IP (CHAP
[edit]
user@host# set interfaces at-1/0/0unit 0family inet unnumbered-address destination
100.100.100.6
Step-by-Step
Procedure
ToconfigurePPPoAontheat-x/x/xinterfacewithunnumberedIP(CHAPAuthentication):
[edit]
[edit]
3. Configure the IPaddress and unnumbered IPaddress and destination for the ADSL
interface.
[edit]
user@host# set interfaces at-1/0/0unit 0family inet unnumbered-address
destination 100.100.100.6
[edit]
[edit]
user@host# commit
Configuring PPPoE over ATMon the at-x/x/x Interface with Negotiated IP (PAP
Authentication)
CLI Quick
Configuration
To quickly configure PPPoE over ATMon the at-x/x/x interface with negotiated IP (PAP
[edit]
user@host# set interfaces at-1/0/0unit 0encapsulation ppp-over-ether-over-atm-llc
user@host# set interfaces pp0unit 0ppp-options pap local-password Embe1mpls
user@host# set interfaces pp0unit 0pppoe-options underlying-interface at-1/0/0.0
Step-by-Step
Procedure
To configure PPPoE over ATMon the at-x/x/x interface with negotiated IP (PAP
Authentication):
1. Configure encapsulation and atm-options for the ADSL interface.
[edit]
[edit]
user@host#set interfaces pp0unit 0ppp-options pap local-password Embe1mpls
3. Configure pppoe-options for the ADSL interface.
[edit]
[edit]
[edit]
[edit]
user@host# commit
pp0 command. If the output does not display the intended configuration, repeat the
Configuring PPPoEover ATMon the at-x/x/x Interface with NegotiatedIP(CHAP
Authentication)
CLI Quick
Configuration
To quickly configure PPPoE over ATMon the at-x/x/x interface with negotiated IP(CHAP
[edit]
user@host# set interfaces at-1/0/0unit 0encapsulation ppp-over-ether-over-atm-llc
user@host#set interfaces pp0unit 0ppp-options chapdefault-chap-secret Embe1mpls
user@host# set interfaces pp0unit 0pppoe-options underlying-interface at-1/0/0.0
Step-by-Step
Procedure
To configure PPPoE over ATMon the at-x/x/x interface with negotiated IP (CHAP
Authentication):
1. Configure encapsulation and atm-options for the ADSL interface.
[edit]
[edit]
user@host# set interfaces pp0unit 0ppp-options chap default-chap-secret
Embe1mpls
3. Configure pppoe-options for the ADSL interface.
[edit]
[edit]
[edit]
user@host# commit
Verification
Verifying the ADSL Interface for End-to-End Data Path on page 339
Verifying PPPoA on the at-x/x/x Interface with Negotiated IP (CHAP
Verifying PPPoA on the at-x/x/x Interface with Negotiated IP (PAP
Verifying PPPoA on the at-x/x/x Interface with Static IP (CHAP
Verifying PPPoA on the at-x/x/x Interface with Static IP (PAP
Verifying PPPoA on the at-x/x/x Interface with Unnumbered IP (PAP
Verifying PPPoA on the at-x/x/x Interface with Unnumbered IP (CHAP
Verifying PPPoE over ATMon the at-x/x/x Interface with Negotiated IP (PAP
Verifying PPPoE over ATMon the at-x/x/x Interface with Negotiated IP (CHAP
Verifying the ADSL Interface for End-to-End Data Path
Purpose Verify the interface status and traffic statistics.
Action Verify the interface status by using the showinterface terse command and test
end-to-end data path connectivity by sending the ping packets to remote end IP
address.
1.
user@host# run show interfaces at-1/0/0 terse
at-1/0/0 up up
at-1/0/0.0 up up inet 10.10.10.1/24
at-1/0/0.32767 up up
[edit]
PING 10.10.10.2 (10.10.10.2): 56 data bytes
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[edit]
user@host#
2. Verify the ADSL interface and traffic statistics.
user@host# run show interfaces at-1/0/0
Speed: ADSL
Speed: 832kbps, Loopback: None
Link flags : None
ADSL alarms : None
ADSL defects : None
ADSL status:
Modem status : Showtime (Itu-dmt)
DSL mode : Itu-dmt Annex A
Subfunction : 0x00
Logical interface at-1/0/0.0 (Index 69) (SNMP ifIndex 523)
Flags: Point-To-Point SNMP-Traps 0x0 Encapsulation: ATM-SNAP
Input packets : 1000
Flags: None
10.10.10.255
VCI 2.119
Flags: Active
Input packets : 1000
Flags: Point-To-Multipoint No-Multicast SNMP-Traps 0x0
Encapsulation: ATM-VCMUX
Input packets : 0
Output packets: 0
VCI 2.4
Flags: Active
Input packets : 0
Output packets: 0
Verifying PPPoAon the at-x/x/x Interface with Negotiated IP (CHAP
Authentication)
Purpose Verify the interface output and end-to-end data path connectivity.
Action Verify the interface output. 1.
Speed: ADSL
Link flags : None
ADSL alarms : None
ADSL defects : None
ADSL status:
Subfunction : 0x00
Flags: Point-To-Point SNMP-Traps 0x0 Encapsulation: ATM-PPP-LLC
Input packets : 26
Output packets: 29
LCP state: Opened
CHAP state: Success
PAP state: Closed
VCI 2.119
Flags: Active
Input packets : 26
Output packets: 29
Flags: Point-To-Multipoint No-Multicast SNMP-Traps 0x0 Encapsulation:
ATM-VCMUX
Input packets : 0
Output packets: 0
VCI 2.4
Flags: Active
Input packets : 0
Output packets: 0
at-1/0/0 up up
at-1/0/0.0 up up inet 100.100.100.1 -->
100.100.100.6
at-1/0/0.32767 up up
[edit]
PING 100.100.100.6 (100.100.100.6): 56 data bytes
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
--- 100.100.100.6 ping statistics ---
VerifyingPPPoAontheat-x/x/xInterfacewithNegotiatedIP(PAPAuthentication)
Purpose Verify the interface status and end-to-end data path connectivity.
Speed: ADSL
Link flags : None
ADSL alarms : None
ADSL defects : None
ADSL status:
Subfunction : 0x00
Input packets : 2
Output packets: 2
LCP state: Opened
CHAP state: Closed
PAP state: Success
VCI 2.119
Flags: Active
Input packets : 2
Output packets: 2
ATM-VCMUX
Input packets : 0
Output packets: 0
VCI 2.4
Flags: Active
Input packets : 0
Output packets: 0
2. Verify the interface and check end-to-end data path connectivity.
at-1/0/0 up up
at-1/0/0.0 up up inet 100.100.100.1 -->
100.100.100.6
at-1/0/0.32767 up up
[edit]
PING 100.100.100.6 (100.100.100.6): 56 data bytes
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
--- 100.100.100.6 ping statistics ---
Verifying PPPoAon the at-x/x/x Interface with Static IP (CHAP Authentication)
Purpose Verify the interface status and end-to-end data path testing.
Speed: ADSL
Link flags : None
ADSL alarms : None
ADSL defects : None
ADSL status:
Subfunction : 0x00
Input packets : 46
Output packets: 88
LCP state: Opened
CHAP state: Success
PAP state: Closed
Allowed host-inbound traffic : any-service bfd bgp dvmrp igmp ldp msdp
nhrp ospf pgm pim rip router-discovery rsvp sap vrrp
Flags: None
100.100.100.255
VCI 2.119
Flags: Active
Input packets : 46
Output packets: 88
ATM-VCMUX
Input packets : 0
Output packets: 0
VCI 2.4
Flags: Active
Input packets : 0
Output packets: 0
at-1/0/0 up up
at-1/0/0.0 up up inet 100.100.100.1/24
at-1/0/0.32767 up up
[edit]
PING 100.100.100.6 (100.100.100.6): 56 data bytes
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
--- 100.100.100.6 ping statistics ---
Verifying PPPoAon the at-x/x/x Interface with Static IP (PAP Authentication)
Speed: ADSL
Link flags : None
ADSL alarms : None
ADSL defects : None
ADSL status:
Subfunction : 0x00
Input packets : 28
Output packets: 29
LCP state: Opened
CHAP state: Closed
PAP state: Success
Flags: None
100.100.100.255
VCI 2.119
Flags: Active
Input packets : 28
Output packets: 29
ATM-VCMUX
Input packets : 0
Output packets: 0
VCI 2.4
Flags: Active
Input packets : 0
Output packets: 0
at-1/0/0 up up
at-1/0/0.0 up up inet 100.100.100.10/24
at-1/0/0.32767 up up
[edit]
PING 100.100.100.6 (100.100.100.6): 56 data bytes
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
--- 100.100.100.6 ping statistics ---
Verifying PPPoAon the at-x/x/x Interface with Unnumbered IP (PAP
Authentication)
Speed: ADSL
Link flags : None
ADSL alarms : None
ADSL defects : None
ADSL status:
Subfunction : 0x00
Input packets : 441
Output packets: 342
LCP state: Opened
CHAP state: Closed
PAP state: Success
Flags: None
100.100.100.255
VCI 2.119
Flags: Active
Input packets : 441
Output packets: 342
ATM-VCMUX
Input packets : 0
Output packets: 0
VCI 2.4
Flags: Active
Input packets : 0
Output packets: 0
at-1/0/0 up up
at-1/0/0.0 up up inet 100.100.100.20 -->
100.100.100.6
at-1/0/0.32767 up up
[edit]
PING 100.100.100.6 (100.100.100.6): 56 data bytes
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
--- 100.100.100.6 ping statistics ---
Verifying PPPoAon the at-x/x/x Interface with Unnumbered IP (CHAP
Authentication)
Purpose Verify the interface status and end-to-end data path connectivity.
Speed: ADSL
Link flags : None
ADSL alarms : None
ADSL defects : None
ADSL status:
Subfunction : 0x00
Input packets : 36
Output packets: 35
LCP state: Opened
CHAP state: Success
PAP state: Closed
Flags: None
VCI 2.119
Flags: Active
Input packets : 36
Output packets: 35
ATM-VCMUX
Input packets : 0
Output packets: 0
VCI 2.4
Flags: Active
Input packets : 0
Output packets: 0
at-1/0/0 up up
at-1/0/0.0 up up inet 100.100.100.10 -->
100.100.100.6
at-1/0/0.32767 up up
[edit]
PING 100.100.100.6 (100.100.100.6): 56 data bytes
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
--- 100.100.100.6 ping statistics ---
Verifying PPPoE over ATMon the at-x/x/x Interface with Negotiated IP (PAP
Authentication)
Purpose Verify the interface status and end-to-end data path connectivity
Link flags : None
Input packets : 0
Output packets: 0
PPPoE:
Session AC name: belur, Remote MAC address: 00:90:1a:41:03:c5,
Underlying interface: at-1/0/0.0 (Index 71)
Input packets : 464
Output packets: 241
LCP state: Opened
mpls:
Not-configured
CHAP state: Closed
PAP state: Success
at-1/0/0 up up
at-1/0/0.0 up up
at-1/0/0.32767 up up
[edit]
pp0 up up
pp0.0 up up inet 12.12.12.15 -->
12.12.12.1
[edit]
PING 12.12.12.1 (12.12.12.1): 56 data bytes
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Verifying PPPoE over ATMon the at-x/x/x Interface with Negotiated IP (CHAP
Authentication)
Purpose Verify the interface status and end-to-end data path connectivity
Link flags : None
Input packets : 0
Output packets: 0
PPPoE:
Session AC name: belur, Remote MAC address: 00:90:1a:41:03:c5,
Underlying interface: at-1/0/0.0 (Index 71)
Input packets : 14
Output packets: 13
LCP state: Opened
CHAP state: Success
PAP state: Closed
at-1/0/0 up up
at-1/0/0.0 up up
at-1/0/0.32767 up up
[edit]
pp0 up up
pp0.0 up up inet 12.12.12.16 -->
12.12.12.1
[edit]
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[edit]
user@host#
Related
Documentation
CHAPTER 14
3G Wireless Modems for WAN
Connections
3G Wireless ModemOverviewon page 353
3G Wireless ModemConfiguration Overviewon page 354
Dialer Interface on page 355
3G Wireless ModemInterface on page 363
GSMProfile on page 364
Account Activation for CDMA EV-DOModemCards on page 366
Unlocking the GSM3G Wireless Modemon page 372
3GWireless ModemOverview
3G refers to the third generation of mobile phone standards and technology based on
the International Telecommunication Union (ITU) International Mobile
Telecommunications-2000 (IMT-2000) global standard. 3G networks are wide area
cellular telephone networks that have evolved to include high-data rate services of up
to 3 Mbps. This increased bandwidth makes 3G networks a viable option as primary or
backup wide area network (WAN) links for a branch office.
Juniper Networks supports 3G wireless modemcards that you can install into the
ExpressCard slot in SRX210 devices. When used in a branch office, the SRX210 device
canprovidedial-out services toPCusers andforwardIPtrafficthroughaserviceproviders
cellular network.
Figure26onpage354illustrates abasic setupfor 3Gwireless connectivity for twobranch
offices. Branch Office A has a T1 leased line as the primary wide area network (WAN)
link and a 3G wireless modemconnection as the failover link. Branch Office B uses the
3G wireless modemconnection as the primary WAN link.
Figure 26: Wireless WANConnections for Branch Offices
Internet/carrier network
Related
Documentation
Understanding the Dialer Interface on page 355
Understanding the 3G Wireless ModemPhysical Interface on page 363
Understanding the GSMProfile on page 364
Understanding Account Activation for CDMA EV-DOModemCards on page 367
3GWireless ModemConfiguration Overview
Before you begin:
1. Install your SRX Series device and establish basic connectivity for your device. For
more information, see the SRX Series Hardware Guide for your device.
2. Obtain a supported 3G wireless modemcard for the device.
3. Establish an account with a cellular network service provider. Contact your service
provider for more information.
4. With the services gateway powered off, insert the 3G wireless modemcard into the
ExpressCard slot. Power on the device. The PIMLED on the front panel of the device
indicates the status of the 3G wireless modeminterface.
WARNING: The device must be powered off before you insert the 3G
wireless modemcardintheExpressCardslot. Youcannot insert or remove
the card when the device is powered on.
To configure and activate the 3G wireless modemcard, performthe following tasks:
1. Configureadialer interface. SeeExample: ConfiguringtheDialer Interface onpage357.
2. Configurethe3Gwireless modeminterface. SeeExample: Configuringthe3GWireless
ModemInterface on page 363.
3. Configure security zones and policies, as needed, to allowtraffic through the WAN
link. See Example: Creating Security Zones.
Related
Documentation
Dialer Interface
Example: Configuring the Dialer Interface on page 357
Understanding the Dialer Interface
The dialer interface, dln, is a logical interface for configuring properties for modem
connections. You can configure multiple dialer interfaces on an SRX Series device. A
dialer interface and a dialer pool (which includes the physical interface) are bound
together in a dialer profile.
Dialer Interface Configuration Rules on page 355
Dialer Interface Authentication Support for GSMHSDPA 3G Wireless
Modems on page 356
Dialer Interface Functions on page 356
Dialer Interface Operating Parameters on page 357
Dialer Interface Configuration Rules
The following rules apply when you configure dialer interfaces for 3G wireless modem
connections:
Chapter 14: 3G Wireless Modems for WAN Connections
The dialer interface must be configured to use the default Point-to-Point Protocol
(PPP) encapsulation. Youcannot configureCiscoHigh-Level DataLink Control (HDLC)
or Multilink PPP (MLPPP) encapsulation on dialer interfaces.
You cannot configure the dialer interface as a constituent link in a multilink bundle.
You cannot configure any dial-in options for the dialer interface.
You configure the following for a dialer interface:
A dialer pool to which the physical interface belongs.
Source IP address for the dialer interface.
Dial string (optional) is the destination number to be dialed.
Authentication, for GSMHSDPA 3G wireless modemcards.
Watch list, if the dialer interface is a backup WAN link.
Dialer Interface Authentication Support for GSMHSDPA 3GWireless Modems
For GSMHSDPA 3G wireless modems, you configure a dialer interface to support
authentication through Challenge Handshake Authentication Protocol (CHAP) or
Password Authentication Protocol (PAP).
CHAP is a server-driven, three-step authentication method that depends on a shared
secret password that resides on both the server and the client. When you enable CHAP
on a dialer interface, the device can authenticate its peer and be authenticated by its
peer.
PAPallows asimplemethodfor apeer toestablishits identity usingatwo-way handshake
duringinitial linkestablishment. After thelinkisestablished, anidentificationandpassword
pair is repeatedly sent by the peer to the authenticator until authentication is
acknowledged or the connection is terminated.
Dialer Interface Functions
The dialer interface can performbackup, dialer filter, and dialer watch functions, but
these operations are mutually exclusive. You can configure a single dialer interface to
operate in only one of the following ways:
As a backup interface for a single primary WAN connection. The dialer interfaces are
activated only when the primary interface fails. The 3G wireless modembackup
connectivity is supported on all interfaces except lsq-0/0/0.
As a dialer filter. The Dialer filter enables the 3G wireless modemconnection to be
activated only when specific network traffic is sent on the backup WAN link. You
configure a firewall rule with the dialer filter option, and then apply the dialer filter to
the dialer interface.
As a dialer watch interface. With dialer watch, the SRX Series device monitors the
status of a specified route and if the route disappears, the dialer interface initiates the
3G wireless modemconnection as a backup connection. To configure dialer watch,
you first add the routes to be monitored to a watch list in a dialer interface; specify a
dialer pool for this configuration. Then configure the 3G wireless modeminterface to
use the dialer pool.
Dialer Interface Operating Parameters
You can also specify optional operating parameters for the dialer interface:
Activation delayNumber of seconds after the primary interface is down before the
backup interface is activated. The default value is 0 seconds, and the maximumvalue
is 60 seconds. Use this option only if dialer watch is configured.
Deactivation delayNumber of seconds after the primary interface is up before the
backup interface is deactivated. The default value is 0 seconds, and the maximum
value is 60 seconds. Use this option only if dialer watch is configured.
Idle timeoutNumber of seconds the connection remains idle before disconnecting.
The default value is 120 seconds, and the range is from0 to 4,294,967,295 seconds.
Initial route checkNumber of seconds before the primary interface is checked to see
if it is up. The default value is 120 seconds, and the range is from1 to 300 seconds.
Related
Documentation
Example: Configuring the Dialer Interface on page 357
Example: Configuring the Dialer Interface
This example shows howto configure the dialer interface for 3G wireless modem
connections.
Overviewon page 357
Requirements
Before you begin, install your SRX Series device and establish basic connectivity for your
device. See 3G Wireless ModemConfiguration Overview on page 354.
Overview
In this example, you first configure the dialer interface as dl0, specify the PPP
encapsulation dialer pool as 1, specify the dial string as 14691, and negotiate the address
option for the interface IP address.
With GSMHSDPA 3G wireless modemcards, you might need to configure PAP or CHAP
for authentication with the service provider network. The service provider must supply
the username and password, which you configure in an access profile. You then specify
the access profile in a dialer interface.
Next you set the dialer interface as a backup WAN link to a primary interface. Then you
create a dialer watch to enable the device to monitor the route to a head office router
and set a dialer pool. Finally, you create a dialer filter firewall rule for traffic fromthe
branchofficetothemainofficerouter andassociatethedialer filter withadialer interface.
Configuration
Configuring a Dialer Interface on page 358
Configuring PAP on the Dialer Interface on page 359
Configuring CHAP on the Dialer Interface on page 359
Configuring the Dialer Interface as a Backup WAN Connection on page 360
Configuring Dialer Watch for the 3G Wireless ModemInterface on page 361
Configuring a Dialer Filter for the 3G Wireless ModemInterface on page 361
Configuring a Dialer Interface
CLI Quick
Configuration
To quickly configure a dialer interface, copy the following commands and paste them
into the CLI:
[edit]
set interfaces dl0description 3g-wireless encapsulation ppp unit 0dialer-options pool 1
dial-string 14691
set interfaces dl0unit 0family inet negotiate-address
Step-by-Step
Procedure
Set the interface and specify the PPP encapsulation, dialer pool, and dial string.
[edit]
1.
user@host# set interfaces dl0description 3g-wireless encapsulation ppp unit 0
dialer-options pool 1 dial-string 14691
2. Set the negotiate address option for the interface IP address.
[edit]
user@host# set interfaces dl0unit 0family inet negotiate-address
[edit]
description 3g-wireless;
encapsulation ppp;
unit 0 {
family inet {
negotiate-address;
}
dialer-options {
pool 1;
dial-string 14691;
}
}
Configuring PAP on the Dialer Interface
CLI Quick
Configuration
With GSMHSDPA 3G wireless modemcards, you may need to configure PAP for
authentication with the service provider network. The service provider must supply the
username and password, which you configure in an access profile. You then specify this
access profile in a dialer interface.
To quickly configure PAP on a dialer interface, copy the following commands and paste
theminto the CLI:
[edit]
set access profile pap-1 client clientX pap-password 7a^6b%5c
set interfaces dl0unit 0ppp-options pap access-profile pap-1
Step-by-Step
Procedure
Configure a PAP access profile.
[edit]
1.
user@host# set access profile pap-1 client clientX pap-password 7a^6b%5c
2. Associate the PAP access profile with a dialer interface.
[edit]
user@host# set interfaces dl0unit 0ppp-options pap access-profile pap-1
and showaccess profile pap-1 commands. If the output does not display the intended
[edit]
unit 0 {
ppp-options {
pap {
access-profile pap-1;
}
}
}
[edit]
user@host# showaccess profile pap-1
client clientX pap-password "$9$jnqTz3nCBESu01hSrKvZUDkqf"; ## SECRET-DATA
Configuring CHAP on the Dialer Interface
CLI Quick
Configuration
With GSMHSDPA 3G wireless modemcards, you may need to configure CHAP for
authentication with the service provider network. The service provider must supply the
username and password, which you configure in an access profile. You then specify this
access profile in a dialer interface.
To quickly configure CHAPon a dialer interface, copy the following commands and paste
theminto the CLI:
[edit]
set access profile chap-1 client clientX chap-secret 7a^6b%5c
set interfaces dl0unit 0ppp-options chap access-profile chap-1
Step-by-Step
Procedure
Configure a CHAP access profile.
[edit]
1.
user@host# set access profile chap-1 client clientX chap-secret 7a^6b%5c
2. Associate the CHAP access profile with a dialer interface.
[edit]
user@host# set interfaces dl0unit 0ppp-options chap access-profile chap-1
Results Fromconfiguration mode, confirmyour configuration by entering the showaccess profile
chap-1 and showinterfaces dl0 commands. If the output does not display the intended
[edit]
user@host# showaccess profile chap-1
client clientX chap-secret "$9$neYpCO1REyWx-Kv87-VsYQF39Cu"; ## SECRET-DATA
[edit]
unit 0 {
ppp-options {
chap {
access-profile chap-1;
}
}
}
Configuring the Dialer Interface as a Backup WANConnection
CLI Quick
Configuration
To quickly configure the dialer interface as a backup WANconnection, copy the following
[edit]
set interfaces ge-0/0/1 unit 0backup-options interface dl0
Step-by-Step
Procedure
Set interface back up option.
[edit]
1.
user@host# set interfaces ge-0/0/1 unit 0backup-options interface dl0
[edit]
user@host# showinterfaces ge-0/0/1
unit 0 {
backup-options {
interface dl0.0;
}
}
Configuring Dialer Watch for the 3GWireless ModemInterface
CLI Quick
Configuration
Toquickly configure dialer watchfor the 3Gwireless modeminterface, copy the following
[edit]
set interfaces dl0description dialer-watch unit 0dialer-options watch-list
200.200.201.1/32
set interfaces dl0description dialer-watch unit 0dialer-options pool dw-pool
Step-by-Step
Procedure
Create a dialer watch.
[edit]
1.
user@host# set interfaces dl0description dialer-watch unit 0dialer-options
watch-list 200.200.201.1/32
2. Set a dialer pool.
[edit]
user@host# set interfaces dl0description dialer-watch unit 0dialer-options pool
dw-pool
[edit]
description dialer-watch;
unit 0 {
dialer-options {
watch-list {
200.200.201.1/32;
}
}
}
Configuring a Dialer Filter for the 3GWireless ModemInterface
CLI Quick
Configuration
Toquickly configure adialer filter for the 3Gwireless modeminterface, copy the following
[edit]
set firewall familyinet dialer-filter corporate-traffic-onlytermterm1 fromsource-address
20.20.90.4/32
set firewall family inet dialer-filter corporate-traffic-only termterm1 from
destination-address 200.200.201.1/32
set firewall family inet dialer-filter corporate-traffic-only termterm1 then note
Step-by-Step
Procedure
Specify a dialer filter firewall rule fromthe source address.
[edit]
1.
user@host# set firewall family inet dialer-filter corporate-traffic-only termterm1
fromsource-address 20.20.90.4/32
2. Specify a dialer filter firewall rule fromthe destination address.
[edit]
fromdestination-address 200.200.201.1/32
3. Associate the dialer filter with a dialer interface.
[edit]
then note
Results Fromconfiguration mode, confirmyour configuration by entering the showfirewall family
inet dialer-filter corporate-traffic-only command. If the output does not display the
intended configuration, repeat the configuration instructions in this example to correct
it.
[edit]
user@host# showfirewall family inet dialer-filter corporate-traffic-only
termterm1 {
from{
source-address {
20.20.90.4/32;
}
destination-address {
200.200.201.1/32;
}
}
then note;
}
Verification
Purpose Verify the configuration output.
Action Verify the configuration output by entering the showinterfaces command.
Related
Documentation
3GWireless ModemInterface
Example: Configuring the 3G Wireless ModemInterface on page 363
Understanding the 3GWireless ModemPhysical Interface
You configure two types of interfaces for 3G wireless modemconnectivitythe physical
interface and a logical dialer interface.
The physical interface for the 3Gwireless modemuses the name cl-0/0/8. This interface
is automatically created when a 3G wireless modemis installed in the device.
You configure the following properties for the physical interface:
A dialer pool to which the physical interface belongs and the priority of the interface
in the pool. A physical interface can belong to more than one dialer pool. The dialer
pool priority has a range from1 to 255, with 1 designating the lowest-priority interfaces
and 255 designating the highest-priority interfaces.
Modeminitialization string (optional). These strings begin with AT and execute Hayes
modemcommands that specify modemoperation.
GSMprofile for establishing a data call with a GSMcellular network.
By default, the modemallows access to networks other than the home network.
Related
Documentation
Example: Configuring the 3G Wireless ModemInterface on page 363
Example: Configuring the 3GWireless ModemInterface
This example shows howto configure the 3G wireless modeminterface.
Overviewon page 364
Requirements
Before you begin, configure a dialer interface. See Example: Configuring the Dialer
Overview
In this example, you configure the physical interface as cl-0/0/8 for the 3G wireless
modemtouse dialer pool 1 andset the priority for the dialer pool to25. Youalsoconfigure
a modeminitialization string to autoanswer after two rings.
Configuration
Step-by-Step
Procedure
To configure the 3G wireless modeminterface:
Specify the dialer pool. 1.
[edit]
user@host# set interfaces cl-0/0/8 dialer-options pool 1 priority 25
2. Specify the modemoptions.
[edit]
user@host# set interfaces cl-0/0/8 modem-options init-command-string
ATSO=2\n
[edit]
user@host# commit
Verification
To verify the configuration is working properly, enter the showinterfaces cl-0/0/8modem
options command.
Related
Documentation
GSMProfile
Example: Configuring the GSMProfile on page 365
Understanding the GSMProfile
To allowdata calls to a Global Systemfor Mobile Communications (GSM) network, you
must obtain the following information fromyour service provider:
Username and password
Access point name (APN)
Whether the authentication is Challenge Handshake Authentication Protocol (CHAP)
or Password Authentication Protocol (PAP)
You configure this information in a GSMprofile associated with the 3G wireless modem
physical interface. You can configure up to 16 different GSMprofiles, although only one
profile can be active at a time.
NOTE: You also need to configure a CHAP or PAP profile with the specified
username and password for the dialer interface.
Subscriber information is written to the Subscriber Identity Module (SIM) on the GSM
HSDPA3Gwireless modemcard. If the SIMis locked, youmust unlock it before activation
by using the master subsidy lock (MSL) value given by the service provider when you
purchase the cellular network service.
Some service providers may preload subscriber profile information on a SIMcard. The
assigned subscriber information is stored in profile 1, while profile 0 is a default profile
created during manufacturing. If this is the case, specify profile 1 for the GSMprofile
associated with the 3G wireless modemphysical interface.
Related
Documentation
Example: Configuring the GSMProfile on page 365
Example: Configuring the GSMProfile
This exampleshows howtoconfiguretheGSMprofilefor the3Gwireless modeminterface
with service provider networks such as AT&T and T-Mobile.
Overviewon page 365
Requirements
Before you begin:
Configureadialer interface. SeeExample: ConfiguringtheDialer Interface onpage357
Configurethe3Gwirelessmodeminterface. SeeExample: Configuringthe3GWireless
ModemInterface on page 363.
Overview
In this example, you configure the following information provided by a service provider
in a GSMprofile called juniper99that is associated with the 3Gwireless modemphysical
interface cl-0/0/8:
Usernamejuniper99
Password1@#6ahgfh
Access point name (APN)apn.service.com
Authentication methodCHAP
Then you activate the profile by specifying the profile ID as profile-id 1.
Configuration
Step-by-Step
Procedure
To configure a GSMprofile for the 3G wireless modeminterface:
Create a GSMprofile. 1.
[edit]
user@host> request modemwireless gsmcreate-profile profile-id 1 sip-user-id
juniper99 sip-password 16ahgfh access-point-name apn.service.com
authentication-method chap
2. Activate the profile.
[edit]
user@host# set interface cl-0/0/8 cellular-options gsm-options select-profile
profile-id 1
[edit]
user@host# commit
Verification
To verify the configuration is working properly, enter the showinterfaces cl-0/0/8
command.
Related
Documentation
Account Activation for CDMAEV-DOModemCards
Activating the CDMA EV-DOModemCard with OTASP Provisioning on page 368
Activating the CDMA EV-DOModemCard Manually on page 369
Activating the CDMA EV-DOModemCard with IOTA Provisioning on page 371
Understanding Account Activation for CDMAEV-DOModemCards
Account activation is the process of enabling the CDMA EV-DOwireless modemcard to
connect to your service providers cellular network. This is a one-time process where your
subscriber information is saved in nonvolatile memory on the card. The procedure you
use to performaccount activation depends upon the the service provider network.
Beforeactivatinganaccount, youcanverify thesignal strengthonthe3Gwireless modem
interface by using the showmodemwireless interface cl-0/0/8rssi command. The signal
strength should be at least -90 dB and preferably better than -80 dB (-125 dB indicates
nil signal strength). If the signal strength is below-90dB, activation may not be possible
fromthat location. For example:
user@host> showmodemwireless interface cl-0/0/8 rssi
Current Radio Signal Strength (RSSI) = -98 dBm
Obtaining Electronic Serial Number (ESN) on page 367
Account Activation Modes on page 368
Obtaining Electronic Serial Number (ESN)
Theserviceprovider requires theelectronicserial number (ESN) of the3Gwireless modem
card to activate your account and to generate the necessary information you need to
activate the card. You can obtain the ESN number of the modemcard in the following
ways:
Inspect the modemcard itself; the ESN is printed on the card.
Use the CLI showmodemwireless interface cl-0/0/8 firmware command, as shown in
the following example, andnote the value for the Electronic Serial Number (ESN) field:
user@host> showmodemwireless interface cl-0/0/8 firmware
Modem Firmware Version : p2005600
Modem Firmware built date : 12-09-07
Card type : Aircard 597E - CDMA EV-DO revA
Manufacturer : Sierra Wireless, Inc.
Hardware Version : 1.0
Electronic Serial Number (ESN) : 0x6032688F
Preferred Roaming List (PRL) Version : 20224
Supported Mode : 1xev-do rev-a, 1x
Current Modem Temperature : 32 degrees Celsius
Modem Activated : YES
Activation Date: 2-06-08
Modem PIN Security : Unlocked
Power-up lock : Disabled
Account Activation Modes
For the CDMA EV-DO3Gwireless modemcard, account activation can be done through
one or more of the following modes:
Over the air service provisioning (OTASP)protocol for programming phones over the
air using InterimStandard 95 (IS-95) Data Burst Messages.
To activate the 3G wireless modemcard with OTASP, you need to obtain fromthe
service provider the dial number that the modemwill use to contact the network.
Typically, OTASP dial numbers begin with the feature code *228 to indicate an
activation call type to the cellular network's base transceiver station, followed by
additional digits specified by the service provider.
Internet-based over the air (IOTA) provisioningmethod for programming phones for
voice and data services
Manually providing the required information by entering in a CLI operational mode
command
Sprint uses manual and IOTA activation, whereas Verizon uses only OTASP.
NOTE: The 3Gwireless modemis set into Single-Carrier Radio Transmission
Technology (1xRTT) mode automatically when it is activated for Verizon
networks.
Related
Documentation
Activating the CDMAEV-DOModemCard with OTASP Provisioning
This topic describes the activation of the CDMA EV-DO3Gwireless modemcard for use
with service provider networks such as Verizon.
Before you begin:
Before you can activate the 3G wireless modemcard, you need to obtain fromthe
service provider the dial number that the modemwill use to contact the network.
The service provider must activate your account before OTASP provisioning can
proceed.
Use the CLI operational mode command to activate the 3G wireless modemcard.
In this example, the dial number fromthe service provider is *22864.
To activate the CDMA EV-DO3G wireless modemcard with OTASP provisioning:
user@host> request modemwireless interface cl-0/0/8 activate otasp dial-string *22864
OTASP number *22286*, Selecting NAM 0
Beginning OTASP Activation. It can take up to 5 minutes
Please check the trace logs for details.
To check the trace log for account activation details:
user@host> tail -f /var/log/wwand.log
Jun 25 04:42:55: OTASP cl-0/0/8 OTA SPL unlock... Success
Jun 25 04:43:42: OTASP cl-0/0/8 OTA PRL download... Success
Jun 25 04:43:55: OTASP cl-0/0/8 OTA Profile downloaded... Success
Jun 25 04:43:58: OTASP cl-0/0/8 OTA MDN download... Success
Jun 25 04:44:04: OTASP cl-0/0/8 Committing OTA Parameters to NVRAM... Success
Jun 25 04:44:45: Over the air provisioning... Complete
Related
Documentation
Activating the CDMAEV-DOModemCard Manually
Manual activation stores the supplied values into the 3G wireless modemcard's
nonvolatile memory. This topic describes the activation of the CDMAEV-DO3Gwireless
modemcard for use with service provider networks such as Sprint.
Before youbegin, the service provider must activate your account before youcanactivate
the CDMA EV-DO3G wireless modemcard.
Using the electronic serial number (ESN) you provided and your account information,
the service provider supplies you with the following information for manual activation of
the 3G wireless modemcard:
Master subsidy lock (MSL)activation code
Mobile directory number (MDN)10-digit user phone number
International mobile station identify (IMSI)Mobile subscriber information
Simple IP user identification (SIP-ID)Username
Simple IP password (SIP-Password)Password
You also need to obtain the following information fromthe 3G wireless modemcard
itself for the activation:
Systemidentification (SID)Number between 0 and 32767
Network identification (NID)Number between 0 and 65535
Use the CLI showmodemwireless interface cl-0/0/8 network command to display the
SID and NID, as shown in the following example:
user@host> showmodemwireless interface cl-0/0/8 network
Running Operating mode : 1xEV-DO (Rev A) and 1xRTT
Call Setup Mode : Mobile IP only
System Identifier (SID) : 3421
Network Identifier (NID) : 91
Roaming Status(1xRTT) : Home
Idle Digital Mode : HDR
System Time : Wed Jun6 15:16:9 2008
Use the CLI operational mode command to manually activate the 3G wireless modem
card.
This example uses the following values for manual activation:
MSL (fromservice provider)43210
MDN (fromservice provider)0123456789
IMSI (fromservice provider)0123456789
SIP-ID (fromservice provider)jnpr
SIP-Password (fromservice provider)jn9rl
SID (frommodemcard)12345
NID (frommodemcard)12345
To activate the CDMA EV-DO3G wireless modemcard manually:
user@host> request modemwireless interface cl-0/0/8 activate manual msl 43210mdn
0123456789 imsi 0123456789 sid 12345 nid 12345 sip-id jnpr sip-password jn9rl
Checking status...
Modem current activation status: Not Activated
Starting activation...
Performing account activation step 1/6 : [Unlock] Done
Performing account activation step 2/6 : [Set MDN] Done
Performing account activation step 3/6 : [Set SIP Info] Done
Performing account activation step 4/6 : [Set IMSI] Done
Performing account activation step 5/6 : [Set SID/NID] Done
Performing account activation step 6/6 : [Commit/Lock] Done
Configuration Commit Result: PASS
Resetting the modem ... Done
Account activation in progress. It can take up to 5 minutes
Jun 25 04:42:55: IOTA cl-0/0/8 Event: IOTA Start... Success
Jun 25 04:43:45: IOTA cl-0/0/8 OTA SPL unlock... Success
Jun 25 04:43:56: IOTA cl-0/0/8 Committing OTA Parameters to NVRAM... Success
Jun 25 04:44:02: IOTA cl-0/0/8 Over the air provisioning... Complete
Jun 25 04:44:04: IOTA cl-0/0/8 IOTA Event: IOTA End... Success
Related
Documentation
Activating the CDMAEV-DOModemCard with IOTAProvisioning
Manual activationstores thesuppliedvalues inthe3Gwireless modemcard's nonvolatile
memory. If the modemcard is reset or you need to update Mobile IP (MIP) parameters,
use the CLI operational mode command to activate the modemcard with IOTA.
Beforeyoubegin, activatetheCDMAEV-DO3Gwirelessmodemcard. SeeUnderstanding
Account Activation for CDMA EV-DOModemCards on page 367.
To activate the CDMA EV-DO3G wireless modemcard with IOTA:
user@host> request modemwireless interface cl-0/0/8 activate iota
Beginning IOTA Activation. It can take up to 5 minutes
Jun 25 04:42:55: IOTA cl-0/0/8 Event: IOTA Start... Success
Jun 25 04:43:45: IOTA cl-0/0/8 OTA SPL unlock... Success
Jun 25 04:43:56: IOTA cl-0/0/8 Committing OTA Parameters to NVRAM... Success
Jun 25 04:44:02: IOTA cl-0/0/8 Over the air provisioning... Complete
Jun 25 04:44:04: IOTA cl-0/0/8 IOTA Event: IOTA End... Success
Related
Documentation
Unlocking the GSM3GWireless Modem
Thesubscriber identity module(SIM) intheGSM3Gwireless modemcardis adetachable
smart card. Swapping out the SIMallows you to change the service provider network,
however some service providers lock the SIMto prevent unauthorized access to the
service provider's network. If this is the case, you will need to unlock the SIMby using an
personal identificationnumber (PIN), afour-digit number providedby theserviceprovider.
Before you begin, obtain the PIN fromthe service provider.
Use the CLI operational mode command to unlock the SIMon the GSM3G wireless
modemcard.
This example uses the PIN 3210 fromthe service provider.
To unlock the SIMon the GSM3G wireless modemcard:
user@host> request modemwireless gsmsim-unlock cl-0/0/8 pin 3210
A SIMis blocked after three consecutive failed unlock attempts; this is a security feature
to prevent brute force attempts to unlock the SIM. When the SIMis blocked, you need
tounblock the SIMwithaneight-digit PINunlocking key (PUK) obtainedfromthe service
provider.
Use the CLI operational mode command to unblock the SIM.
This example uses the PUK 76543210 fromthe service provider.
To unblock the SIM:
user@host> request modemwireless gsmsim-unblock cl-0/0/8 puk 76543210
NOTE: If you enter the PUK incorrectly ten times, you will need to return the
SIMto the service provider for reactivation.
Related
Documentation
CHAPTER 15
USB Modems for Dial Backup
USB ModemInterface Overviewon page 373
USB ModemConfiguration Overviewon page 374
Example: Configuring a USB ModemInterface for Dial Backup on page 376
Example: Configuring a Dialer Interface for USB ModemDial Backup on page 377
Example: Configuring Dialer Interface for USB ModemDial-In on page 384
Example: Configuring PAP on Dialer Interfaces on page 386
Example: Configuring CHAP on Dialer Interfaces on page 387
USB ModemInterface Overview
You can configure your device to fail over to a USBmodemconnection when the primary
Internet connection experiences interruption.
NOTE: Low-latency traffic such as VoIP traffic is not supported over USB
modemconnections.
NOTE: We recommend using a US Robotics USB 56k V.92 Modem, model
number USR Model 5637.
You configure two types of interfaces for USB modemconnectivity:
A physical interface which uses the naming convention umd0. The device creates this
interface when a USB modemis connected to the USB port.
A logical interface called the dialer interface. You use the dialer interface, dln, to
configure dialing properties for USB modemconnections. The dialer interface can be
configured using Point-to-Point Protocol (PPP) encapsulation. You can also configure
the dialer interface to support authentication protocolsPPP Challenge Handshake
(CHAP) or Password Authentication Protocol (PAP).
The USB modemprovides a dial-in remote management interface, and supports dialer
interface features by sharing the same dial pool as a dialer interface. The dial pool allows
the logical dialer interface and the physical interface to be bound together dynamically
on a per-call basis. You can configure the USB modemto operate either as a dial-in
console for management or as a dial-in WAN backup interface.
Dialer Interface Rules
The following rules apply when you configure dialer interfaces for USB modem
connections:
Thedialer interfacemust beconfiguredtousePPPencapsulation. Youcannot configure
Cisco High-Level Data Link Control (HDLC) or Multilink PPP (MLPPP) encapsulation
on dialer interfaces.
The dialer interface cannot be configured as a constituent link in a multilink bundle.
The dialer interface can performbackup, dialer filter, and dialer watch functions, but
these operations are mutually exclusive. You can configure a single dialer interface to
operate in only one of the following ways:
As a backup interfacefor one primary interface
As a dialer filter
As a dialer watch interface
Related
Documentation
USB ModemConfiguration Overview
Before you begin:
1. Install device hardware. For more information, see the Getting Started Guide for your
device.
2. Establish basic connectivity. For more information, see the Getting Started Guide for
your device.
3. Order a US Robotics USB 56k V.92 Modem, model number USR Model 5637 fromUS
Robotics (http://www.usr.com/).
4. Order apublicswitchedtelephonenetwork(PSTN) linefromyour telecommunications
service provider. Contact your service provider for more information.
5. Connect the USB modemto the device's USB port.
NOTE: J Series devices have two USB ports. However, you can connect
only one USB modemto the USB ports on these devices. If you connect
USB modems to both ports, the device detects only the first modem
connected.
NOTE: When you connect the USBmodemto the USBport on the device,
the USB modemis initialized with the modeminitialization string
configured for the USB modeminterface on the device.
a. Plug the modeminto the USB port.
b. Connect the modemto your telephone network.
Supposeyouhaveabranchofficerouter andaheadofficerouter eachwithaUSBmodem
interface and a dialer interface. This example shows you howto establish a backup
connection between the branch office and head office routers. See Table 45 on page 375
for a summarized description of the procedure.
Table 45: Configuring Branch Office and Head Office Routers for USB ModemBackup
Connectivity
Procedure Configuration Requirement Router Location
To configure the logical dialer interface,
see Configuring a Dialer Interface for
USB ModemDial Backup on page 378.
Configure the logical dialer interface on the
branch office router for USB modemdial
backup.
Branch Office
Configure the dialer interface using one
of the following backup methods:
To configure dl0 as a backup for
t1-1/0/0 see Configuring Dial Backup
for a USB ModemConnection on
page 380.
To configure a dialer filter on dl0, see
Configuring a Dialer Filter for USB
ModemDial Backup on page 381.
Toconfigureadialer watchondl0, see
Configuring a Dialer Watch for USB
ModemDial Backup on page 382.
Configure the dialer interface dl0 on the
branchofficerouter usingoneof thefollowing
backup methods:
Configure the dialer interface dl0 as the
backup interface on the branch office
router's primary T1 interface t1-1/0/0.
Configureadialer filter onthebranchoffice
router's dialer interface.
Configure a dialer watch on the branch
office router's dialer interface.
To configure dial-in on the head office
router, see Example: Configuring Dialer
Interface for USB ModemDial-In on
page 384.
Configure dial-in on the dialer interface dl0
on the head office router.
Head Office
Chapter 15: USB Modems for Dial Backup
Related
Documentation
USB ModemInterface Overviewon page 373
Example: Configuring a USB ModemInterface for Dial Backup
This example shows howto configure a USB modeminterface for dial backup.
Overviewon page 376
Requirements
feature.
Overview
In this example, you create an interface called as umd0 for USB modemconnectivity
and set the dialer pool priority to 25. Dialer pool priority has a range from1 to 255, with 1
designating the lowest priority interfaces and 255 designating the highest priority
interfaces. Youalsoconfigureamodeminitializationstringtoautoanswer after aspecified
number of rings. The default modeminitialization string is AT S7=45 S0=0V1 X4 &C1 E0
Q0&Q8 %C0. The modemcommand S0=0 disables the modemfromautoanswering
the calls. Finally, you set the modemto act as a dial-in WAN backup interface.
Configuration
CLI Quick
Configuration
Toquickly configureaUSBmodeminterfacefor thedevice, copy thefollowingcommands
and paste theminto the CLI:
[edit]
set interfaces umd0dialer-options pool usb-modem-dialer-pool priority 25
set modem-options init-command-string "ATS0=2 \n" dialin routable
Step-by-Step
Procedure
Mode.
To configure a USB modeminterface for dial backup:
1. Create an interface.
[edit]
user@host# edit interfaces umd0
2. Set the dialer options and priority.
[edit interfaces umd0]
user@host# set dialer-options pool usb-modem-dialer-pool priority 25
3. Specify the modemoptions.
user@host# set modem-options init-command-string "ATS0=2 \n"
4. Set the modemto act as a dial-in WAN backup interface.
user@host# set modem-options dialin routable
Results Fromconfigurationmode, confirmyour configurationby enteringtheshowinterfaceumd0
[edit]
user@host# showinterface umd0
modem-options {
init-command-string "ATS0=2 \n";
dialin routable;
}
dialer-options {
pool usb-modem-dialer-pool priority 25;
}
Verification
Purpose Verify a USB modeminterface for dial backup.
Action Fromoperational mode, enter the showinterface umd0 command.
Related
Documentation
Example: Configuring a Dialer Interface for USB ModemDial Backup
This example shows howto configure the dialer interface.
Overviewon page 378
Requirements
Before you begin, configure a USB modemfor the device. See Example: Configuring a
USB ModemInterface for Dial Backup on page 376.
Overview
The dialer interface (dl) is a logical interface configured to establish USB modem
connectivity. You can configure multiple dialer interfaces for different functions on the
device. After configuringthedialer interface, youmust configureabackupmethodeither
dialer backup, a dialer filter, or dialer watch.
See Table 46 on page 378 for details about available dialer options.
Table 46: Dialer Options
Description Option
Number of seconds to wait before activating the backupUSBmodeminterface
after the primary interface is down. The default value is 0 seconds, and the
maximumvalue is 60seconds. Use this option only for dialer backup and dialer
watch.
Activation delay
Number of seconds to wait before deactivating the backup USB modem
interface after the primary interface is up. The default value is 0 seconds, and
the maximumvalue is 60 seconds. Use this option only for dialer backup and
dialer watch.
Deactivation delay
Number of seconds aconnectionis idle before disconnecting. The default value
is 120 seconds, and the range is from0 to 4,294,967,295.
Idle timeout
Number of seconds to wait before checking if the primary interface is up. The
default value is 120 seconds, and the range is from1 to 300 seconds.
Initial route check
Name of the dialer pool to use for USB modemconnectivity. Pool
Configuration
Configuring a Dialer Interface for USB ModemDial Backup on page 378
Configuring Dial Backup for a USB ModemConnection on page 380
Configuring a Dialer Filter for USB ModemDial Backup on page 381
Configuring a Dialer Watch for USB ModemDial Backup on page 382
Configuring a Dialer Interface for USB ModemDial Backup
CLI Quick
Configuration
To quickly configure a logical dialer interface on the branch office router for the USB
modemdial backup, copy the following commands and paste theminto the CLI.
[edit]
edit interfaces dl0
set description USB-modem-backup
set encapsulation ppp
set unit 0
edit unit 0dialer-options
set activation-delay 60
set deactivation-delay 30
set idle-timeout 30initial-route-check 30pool usb-modem-dialer-pool
set dial-string 5551212
edit interfaces dl0unit 0
set family inet address 172.20.10.2 destination 172.20.10.1
Step-by-Step
Procedure
Mode.
To configure a logical dialer interface on the branch office router for the USB modem
dial backup:
1. Create the newinterface.
[edit]
2. Add a description to differentiate different dialer interfaces.
[edit]
user@host# set description USB-modem-backup
3. Configure Point-to-Point Protocol (PPP) encapsulation.
NOTE: Youcannot configureCiscoHigh-Level DataLinkControl (HDLC)
or Multilink PPP (MLPPP) encapsulation on dialer interfaces used in
USB modemconnections.
[edit]
user@host# set encapsulation ppp
NOTE: You can set the logical unit to 0 only.
[edit]
5. Configure the dialer options.
[edit]
user@host# set activation-delay 60
user@host# set deactivation-delay 30
user@host#set idle-timeout 30initial-route-check30pool usb-modem-dialer-pool
6. Configure the telephone number of the remote destination to call if the primary
interface goes down.
[edit]
user@host# set dial-string 5551212
7. Configure source and destination IP addresses for the dialer interface.
NOTE: If you configure multiple dialer interfaces, ensure that the same
IP subnet address is not configured on different dialer interfaces.
Configuring the same IP subnet address on multiple dialer interfaces
can result in inconsistency in the route and packet loss. Packets can be
routed through any of the dialer interfaces with the IP subnet address,
instead of being routed through the dialer interface to which the USB
modemcall is mapped.
[edit]
user@host# edit interfaces dl0unit 0
user@host# set family inet address 172.20.10.2 destination 172.20.10.1
8. Configure a backup method. Select one of the following methods:
Configuring Dial Backup for a USB ModemConnection on page 380
Results Fromconfiguration mode, confirmyour configuration by entering the showinterface dl0
Configuring Dial Backup for a USB ModemConnection
CLI Quick
Configuration
Dial backup allows one or more dialer interfaces to be configured as the backup link for
the primary serial interface. The backup dialer interfaces are activated only when the
primary interface fails. USB modembackup connectivity is supported on all interfaces
except lsq-0/0/0.
To quickly configure a primary interface for backup connectivity, copy the following
[edit]
edit interfaces t1-1/0/0unit 0
set backup-options interface dl0.0
Step-by-Step
Procedure
To configure a primary interface for backup connectivity:
Select the physical interface for USB modembackup connectivity. 1.
[edit]
user@host# edit interfaces t1-1/0/0unit 0
2. Configure the backup dialer interface.
[edit]
user@host# set backup-options interface dl0.0
Results Fromconfigurationmode, confirmyour configurationby enteringtheshowinterfacedl0.0
Configuring a Dialer Filter for USB ModemDial Backup
CLI Quick
Configuration
This dial-on-demand routing backup method allows a USB modemconnection to be
activated only when network traffic configured as an interesting packet arrives on the
network. Oncethenetworktrafficis sent, aninactivity timer is triggeredandtheconnection
is closed. You define an interesting packet using the dialer filter feature of the device. To
configuredial-on-demandroutingbackupusingadialer filter, youfirst configurethedialer
filter and then apply the filter to the dialer interface.
To quickly configure the dialer filter and apply it to the dialer interface, copy the following
[edit]
edit firewall
edit family inet
edit dialer-filter interesting-traffic
edit termterm1
set fromsource-address 20.20.90.4/32
set fromdestination-address 200.200.201.1/32
set then note
edit family inet filter
set dialer interesting-traffic
Step-by-Step
Procedure
Mode.
To configure the dialer filter and apply it to the dialer interface:
[edit]
user@host# edit firewall
2. Configure the dialer filter name.
[edit]
user@host# edit family inet
user@host# edit dialer-filter interesting-traffic
3. Configure the dialer filter rule name and termbehavior. In this example, the branch
office router has the IP address 20.20.90.4/32 and the head office router has the
IP address 200.200.201.1/32. To configure the termcompletely, include both from
and then statements.
[edit]
user@host# edit termterm1
user@host# set fromsource-address 20.20.90.4/32
user@host# set fromdestination-address 200.200.201.1/32
4. Configure the then part of the dialer filter to discard Telnet traffic between the
branch office router and the head office router.
[edit]
user@host# set then note
5. Select the dialer interface to apply the filter.
[edit]
6. Apply the dialer filter to the dialer interface.
[edit]
user@host#edit family inet filter
user@host#set dialer interesting-traffic
Configuring a Dialer Watch for USB ModemDial Backup
CLI Quick
Configuration
Dialer watch is a backup method that integrates backup dialing with routing capabilities
andprovides reliable connectivity without relying on a dialer filter totrigger outgoing USB
modemconnections. With dialer watch, the device monitors the existence of a specified
routeandif theroutedisappears, thedialer interfaceinitiates theUSBmodemconnection
as a backup connection.
In this example, you configure dialer watch to enable the device to monitor the existence
of the route to the head office router and initiate USB modembackup connectivity if the
route disappears. To configure dialer watch, you first add a dialer watch interface and
then configure the USB modeminterface to participate as a dialer watch interface.
The USB modeminterface must have the same pool identifier to participate in dialer
watch. For this example, the dialer pool name dw-pool is used when configuring the USB
modeminterface.
To quickly configure a dialer watch, copy the following commands and paste theminto
the CLI.
[edit]
edit interfaces
edit dl0
set description dialer-watch
edit unit 0dialer-options
set watch-list 200.200.201.1/32
set pool dw-pool
edit interfaces umd0dialer-options pool dw-pool
Step-by-Step
Procedure
Mode.
To configure a dialer watch:
[edit]
user@host# edit interfaces
2. Select a dialer interface and add a description to differentiate different dialer
interfaces.
[edit]
user@host# edit dl0
user@host# set description dialer-watch
3. On a logical interface, configure the route to the head office router for dialer watch.
[edit]
user@host# set watch-list 200.200.201.1/32
4. Configure the name of the dialer pool to use for dialer watch.
[edit]
user@host# set pool dw-pool
5. Select the USB modemphysical interface umd0.
[edit]
user@host# edit interfaces umd0dialer-options pool dw-pool
6. Configure dialer watch options for the USB modeminterface participating in the
dialer watch.
Results Fromconfigurationmode, confirmyour configurationby enteringtheshowinterfaceumd0
Verification
Purpose Verify the configuration output.
Action Verify the configuration output by entering the showinterface terse command.
Related
Documentation
Example: Configuring Dialer Interface for USB ModemDial-In
This example shows howto configure a dialer interface for USB modemdial-in.
Overviewon page 384
Requirements
feature.
Overview
You can configure a dialer interface to accept all incoming calls or accept only calls from
one or more caller IDs.
If the dialer interface is configuredto accept only calls froma specific caller ID, the device
matches the incoming call's caller ID against the caller IDs configured on its dialer
interfaces. If an exact match is not found and the incoming call's caller IDhas more digits
than the configured caller IDs, the device performs a right-to-left match of the incoming
call's caller ID with the configured caller IDs and accepts the incoming call if a match is
found. For example, if the incoming call's caller ID is 4085321091 and the caller ID
configured on a dialer interface is 5321091, the incoming call is accepted. Each dialer
interface accepts calls fromonly callers whose caller IDs are configured on it.
See Table 47 on page 384 for a list of available incoming map options.
Table 47: Incoming Map Options
Description Option
Dialer interface accepts all incoming calls.
You can configure the accept-all option for only one of the dialer interfaces
associated with a USB modemphysical interface. The dialer interface with the
accept-all option configuredis usedonly if the incoming call's caller IDdoes not
match the caller IDs configured on other dialer interfaces.
accept-all
Table 47: Incoming Map Options (continued)
Description Option
Dialer interface accepts calls froma specific caller ID. You can configure a
maximumof 15 caller IDs per dialer interface.
The same caller ID must not be configured on different dialer interfaces.
However, you can configure caller IDs with more or fewer digits on different
dialer interfaces. For example, you can configure the caller IDs 14085551515,
4085551515, and 5551515 on different dialer interfaces.
caller
This example shows howto configure a dialer interface for USB modemdial-in.
Configuration
CLI Quick
Configuration
To quickly configure a dialer interface for USB modemdial-in, copy the following
[edit]
edit interfaces dl0
edit unit 0
edit dialer-options
set incoming-map caller 4085551515
Step-by-Step
Procedure
To configure a dialer interface for USB modemdial-in:
Select a dialer interface. 1.
[edit]
2. On logical interface 0, configure the incoming map options.
[edit]
user@host# edit dialer-options
user@host# set incoming-map caller 4085551515
Verification
Action Enter showinterface dl0 and verify the information in the command output.
Related
Documentation
Example: Configuring PAP on Dialer Interfaces
This example shows howto optionally configure Password Authentication Protocol
(PAP) on the dialer interface.
Overviewon page 386
Requirements
feature.
Overview
You can configure dialer interfaces to support PAP. PAP allows a simple method for a
peer toestablish its identity using a two-way handshake during initial link establishment.
After the link is established, an IDand password pair is repeatedly sent by the peer to the
authenticator until authentication is acknowledged or the connection is terminated.
This example shows howto optionally configure PAP on the dialer interface.
Configuration
CLI Quick
Configuration
Toquickly configure PAPon the dialer interface, copy the following commands andpaste
theminto the CLI.
[edit]
set access profile pap-access-profile client pap-access-user pap-password my-pap
set ppp-options pap local-name pap-access-user local-password my-pap
Step-by-Step
Procedure
To configure PAP on the dialer interface:
Define a PAP access profile with a client (username) and a PAP password. 1.
[edit]
user@host# set access profile pap-access-profile client pap-access-user
pap-password my-pap
[edit]
3. Configure PAP on the dialer interface and specify the local name and password.
[edit]
user@host# set ppp-options pap local-name pap-access-user local-password
my-pap
Verification
Related
Documentation
Junos Network Interfaces Configuration Guide
Example: Configuring CHAP on Dialer Interfaces
ThisexampleshowshowtooptionallyconfigurePPPChallengeHandshakeAuthentication
Protocol (CHAP) on the dialer interface.
Overviewon page 388
Requirements
feature.
Overview
You can optionally configure dialer interfaces to support the CHAP. CHAP is a
server-driven, three-step authentication method that depends on a shared secret
password residing on both the server and the client. When you enable CHAP on a dialer
interface, the device can authenticate its peer and be authenticated by its peer.
This example shows howto optionally configure CHAP on the dialer interface.
Configuration
CLI Quick
Configuration
To quickly configure CHAP on the dialer interface, copy the following commands and
[edit]
set access profile usb-modem-access-profile client usb-modem-user chap-secret
my-secret
set ppp-options chap access-profile usb-modem-access-profile
Step-by-Step
Procedure
To configure CHAP on the dialer interface:
Define a CHAP access profile with a client (username) and a secret (password). 1.
[edit]
user@host# set access profile usb-modem-access-profile client usb-modem-user
chap-secret my-secret
[edit]
3. ConfigureCHAPonthedialer interfaceandspecify auniqueprofilenamecontaining
a client list and access parameters.
[edit]
user@host# set ppp-options chap access-profile usb-modem-access-profile
Verification
Related
Documentation
Junos Network Interfaces Configuration Guide
CHAPTER 16
DOCSIS Mini-PIMInterfaces
This section includes following topics:
DOCSIS Mini-PIMInterface Overviewon page 391
Software Features Supported on DOCSIS Mini-PIMs on page 392
Example: Configuring a DOCSIS Mini-PIMon page 393
DOCSIS Mini-PIMInterface Overview
Data over Cable Service Interface Specifications (DOCSIS) define the communications
and operation support interface requirements for a data-over-cable system. Cable
operators use DOCSIS to provide Internet access over their existing cable infrastructure
for both residential and business customers. DOCSIS3.0is the latest interface standard,
allowing channel bonding to deliver speeds higher than 100 Mbps throughput in either
direction, far surpassing other WANtechnologies such as T1/E1, ADSL2+, ISDN, and DS3.
DOCSISnetwork architecture includes a cable modemon SRXSeries Services Gateways
with a DOCSISMini-Physical Interface Module (Mini-PIM) located at customer premises
and a cable modemtermination system(CMTS) located at the head-end or data center
locations. Standards-basedDOCSIS3.0Mini-PIMis interoperablewithCMTSequipment.
The DOCSISMini-PIMprovides backward compatibility with CMTSequipment based on
the following standards:
DOCSIS 2.0
DOCSIS 1.1
DOCSIS 1.0
SRX210 and SRX240 Services Gateways support the DOCSIS Mini-PIM.
The cable modeminterface of Mini-PIMis managed and monitored by CMTS through
SNMP. This DOCSIS3.0Mini-PIMcanbedeployedinany multipleserviceoperator (MSO)
networks. The primary application is for distributed enterprise offices to connect to a
CMTS network through the DOCSIS 3.0 (backward compatible to 2.0, 1.1, and 1.0)
interface. The DOCSIS Mini-PIMuses PIMinfrastructure developed for third-party PIMs.
The Mini-PIMcan also be usedwith encapsulations other than GRE, PPPoE, andIP-in-IP.
Related
Documentation
Software Features Supported on DOCSIS Mini-PIMs
Table 48 on page 392 lists the software features supported on DOCSIS Mini-PIMs.
Table 48: Software Features Supported on DOCSIS Mini-PIMs
Description Software Feature
The DHCPand DHCPv6clients are used to get the IPaddress fromthe CMTSusing the DHCP
protocol. DHCP is supported on IPv4 and IPv6. One of the main components of the
configuration file is the static public IP address, which CMTS assigns to the cable modem.
Themanagement IPaddressisconfiguredontheMini-PIMshybridfiber coaxial (HFC) interface,
which performs the following tasks:
Allows CMTS to execute remote monitoring and management of the Mini-PIMs cable
interface.
Downloads the configuration file fromCMTSand uses it for configuring the cable interface.
DHCP and DHCPv6 clients
The SRX Series devices Routing Engine is configured through the existing QoS CLI. Because
the configuration on the SRX Series devices Routing Engine and Mini-PIMis done together,
theQoSconfigurationhas tobeconsistent betweentheRoutingEngineandthecablemodem
interface. The QoS mechanisms on the Routing Engine are decoupled fromthe QoS
mechanisms on the Mini-PIM.
TheconfigurationfiledownloadedfromCMTScontains parameters for primary andsecondary
flows. These parameters are programmed in the DOCSISMini-PIM. The Mini-PIMsends these
parameters to the Routing Engine through the PIMinfrastructure. The secondary flows are
prioritized over primary flows in the DOCSIS Mini-PIM.
QoS support
CMTS issues the SNMP requests that go to the cable modem. The DOCSIS MIB on the SRX
Series devices Routing Engine displays the Ethernet interface of the cable modem. The
following features are supported on the DOCSIS Mini-PIM:
NAT support
Dying gasp support
Back pressure information
SNMP support
TheMACaddressof theDOCSISMini-PIMis staticallyset at thefactoryandcannot bechanged.
The MAC address is retrieved fromthe Mini-PIMand assigned to the cable modeminterface
in the Junos OS.
MAC address
The DOCSIS Mini-PIMperforms transparent bridging by sending the packets received on the
Ethernet interface with the SRX Series device to the HFC interface and vice versa, without
any modifications to the packet. All the other services such as webserver, DHCP server, and
DNS server are disabled on the DOCSIS Mini-PIMduring transparent bridging.
Transparent bridging
Related
Documentation
Example: Configuring a DOCSIS Mini-PIM
This example shows howto configure DOCSIS Mini-PIMnetwork interfaces for SRX210
and SRX240 devices.
Overviewon page 393
Requirements
Before you begin, configure network interfaces as necessary. See Example: Creating an
Ethernet Interface on page 37.
Overview
The cable modeminterface of Mini-PIMis managed and monitored by CMTS through
SNMP. This DOCSIS 3.0 Mini-PIMcan be deployed in any multiple MSOnetworks. Figure
27 on page 393 illustrates a typical use of this Mini-PIMin a MSOnetwork.
Figure 27: Typical DOCSIS End-to-End Connectivity Diagram
Chapter 16: DOCSIS Mini-PIMInterfaces
Configure the physical properties by setting the interface trace options and flag option.
The following interface trace options are supported:
allEnable all interface trace flags
eventTrace interface events
ipcTrace interface IPC messages
mediaTrace interface media changes
criticalTrace critical events
majorTrace major events
Configure the logical properties by adding the logical interface and family protocol type,
and setting the DHCP client.
This example shows howto configure DOCSIS Mini-PIMnetwork interfaces for SRX210
and SRX240 devices.
Configuration
CLI Quick
Configuration
ToquicklyconfigureDOCSISMini-PIMnetworkinterfacesfor SRX210andSRX240devices,
[edit]
edit interfaces cm-1/0/0
set interfaces cm-2/0/0traceoptions
set interfaces cm-2/0/0traceoptions flag all
set interfaces cm-2/0/0unit 0
set interfaces cm-2/0/0unit 0family inet
set interfaces cm-2/0/0unit 0family inet dhcp
J-Web Quick
Configuration
To configure the logical interface of a DOCSIS Mini-PIM:
1. Select Interfaces>Configure.
2. Under Interface, select cm-4/0/0 and then click Add>Logical Interface. A pop-up
windowappears.
3. Fromthe Zone list, select None.
4. To add a family protocol type to the Mini-PIMinterfaces, select the following check
boxes as applicable:
INET: Supports IPprotocol trafficincluding, OpenShortest PathFirst (OSPF), Border
Gateway Protocol (BGP), and Internet Control Message Protocol (ICMP).
MPLS: Supports Multiprotocol Label Switching (MPLS).
5. Click OK to check your configuration and save it as a candidate configuration.
6. If you are done configuring the device, click Commit Options>Commit.
To edit the logical interface of a DOCSIS Mini-PIM:
1. Under Interface, select the logical interface added to the DOCSIS Mini-PIMand then
click Edit. A pop-up windowappears.
2. Fromthe Zone list, select None.
3. To add a family protocol type to the Mini-PIMinterfaces, select the following check
boxes as applicable:
INET: Supports IP protocol traffic, including OSPF, BGP, and ICMP.
MPLS: Supports MPLS.
NOTE: You cannot add or edit Interface Name, Description, and Unit for a
logical interface.
To delete the logical interface of a DOCSIS Mini-PIM:
2. Under Interface, select cm-4/0/0.0andthenclick Delete. Apop-upwindowappears.
3. Click Yes.
To edit the physical interface of a DOCSIS Mini-PIM:
2. Under Interface, select cm-4/0/0 and then click Edit. A pop-up windowappears.
3. In the Description box, enter a description to be updated for the configured Mini-PIM
interface.
4. In the MTUbox, enter an integer value between 256 and 9192 bytes.
To disable the physical interface of a DOCSIS Mini-PIM:
2. Under Interface, select cm-4/0/0.0andthenclickDisable. Apop-upwindowappears.
3. Click Yes.
Step-by-Step
Procedure
To configure DOCSIS Mini-PIMnetwork interfaces for SRX210 and SRX240 devices:
Configure the interface. 1.
[edit]
user@host# edit interfaces cm-1/0/0
2. Configure the physical properties.
[edit]
user@host# set interfaces cm-2/0/0traceoptions
user@host# set interfaces cm-2/0/0traceoptions flag all
NOTE: MTUis limited to 1518 bytes on this interface.
3. Configure the logical properties.
[edit]
user@host# set interfaces cm-2/0/0unit 0
user@host# set interfaces cm-2/0/0unit 0family inet
user@host# set interfaces cm-2/0/0unit 0family inet dhcp
Verification
Verifying DOCSIS Interfaces Properties on page 396
Verifying DOCSIS Interfaces Properties
Purpose Verify that the DOCSIS interface properties are configured properly.
Action Fromconfiguration mode, enter the showinterfaces interface-name extensive command.
show interfaces cm-1/0/0 extensive
Physical interface: cm-1/0/0, Enabled, Physical link is Up
Link-level type: Ethernet, MTU: 1518, Speed: 40mbps
Link flags : None
State : OPERATIONAL, Mode: 2.0, Upstream speed: 5120000 0 0 0
Downstream scanning: CM_MEDIA_STATE_DONE, Ranging: CM_MEDIA_STATE_DONE
Signal to noise ratio: 31.762909 21.390018 7.517472 14.924058
Power: -15.756125 -31.840363 -31.840363 -31.840363
Downstream buffers used : 0
Downstream buffers free : 0
Upstream buffers free : 0
Upstream buffers used : 0
Request opportunity burst : 0 MSlots
Physical burst : 0 MSlots
Tuner frequency : 555 0 0 0 MHz
Standard short grant : 0 Slots
Standard long grant : 0 Slots
Baseline privacy state: authorized, Encryption algorithm: ????, Key length: 0
MAC statistics: Receive Transmit
Total octets 1935 2036
Total packets 8 8
CRC/Align errors 0 0
Oversized frames 0
Current address: 00:24:dc:0d:76:19, Hardware address: 00:24:dc:0d:76:19
Traffic statistics:
Destination slot: 1
Direction : Output
Limit
% bps % usec
0 best-effort 95 38000000 95 0 low
none
none
Logical interface cm-1/0/0.0 (Index 69) (SNMP ifIndex 523) (Generation 134)
Flags: Point-To-Point SNMP-Traps Encapsulation: ENET2
Traffic statistics:
Input bytes : 710
Output bytes : 806
Input packets: 2
Output packets: 4
Local statistics:
Input bytes : 710
Output bytes : 806
Input packets: 2
Output packets: 4
Transit statistics:
Flow Statistics :
Self packets : 0
ICMP packets : 0
VPN packets : 0
Address spoofing: 0
No minor session: 0
No more sessions: 0
No NAT gate: 0
No route present: 0
No tunnel found: 0
Policy denied: 0
Flags: None
Generation: 144
Related
Documentation
CHAPTER 17
Serial Interfaces
Serial Interfaces Overviewon page 401
Example: Configuring a Serial Interface on page 407
Example: Deleting a Serial Interface on page 409
Serial Interfaces Overview
Serial links are simple, bidirectional links that require very fewcontrol signals. In a basic
serial setup, data communications equipment (DCE) installed in a user's premises is
responsible for establishing, maintaining, and terminating a connection. A modemis a
typical DCE device.
A serial cable connects the DCE to a telephony network where, ultimately, a link is
established with data terminal equipment (DTE). DTE is typically where a serial link
terminates.
The distinction between DCE and DTE is important because it affects the cable pinouts
on a serial cable. A DCE cable uses a female 9-pin or 25-pin connector, and a DTE cable
uses a male 9-pin or 25-pin connector, and .
To forma serial link, the cables are connected to each other. However, if the pins are
identical, eachside'stransmit andreceivelinesareconnected, whichmakesdatatransport
impossible. To address this problem, each cable is connected to a null modemcable,
which crosses the transmit and receive lines in the cable.
Serial Transmissions on page 401
Signal Polarity on page 403
Serial Clocking Modes on page 403
Serial Line Protocols on page 404
Serial Transmissions
In basic serial communications, nine signals are critical to the transmission. Each signal
is associatedwith a pin in either the 9-pin or 25-pin connector. Table 49on page 402 lists
and defines serial signals and their sources.
Table 49: Serial Transmission Signals
Signal Source Definition Signal Name
DTE Transmitted data TD
DCE Received data RD
DTE Request to send RTS
DCE Clear to send CTS
DCE Data set ready DSR
Grounding signal Signal Ground
Carrier detect CD
DTE Data terminal ready DTR
Ring indicator RI
When a serial connection is made, a serial line protocolsuch as EIA-530, X.21,
RS-422/449, RS-232, or V.35begins controlling the transmission of signals across the
line as follows:
1. The DCE transmits a DSR signal to the DTE, which responds with a DTR signal. After
this handshake, the link is established and traffic can pass.
2. When the DTE device is ready to receive data, it sets its RTS signal to a marked state
(all 1s) toindicatetotheDCEthat it cantransmit data. (If theDTEis not abletoreceive
databecause of buffer conditions, for exampleit sets the RTS signal to all 0s.)
3. When the DCE device is ready to receive data, it sets its CTS signal to a marked state
to indicate to the DTE that it can transmit data. (If the DCE is not able to receive data,
it sets the CTS signal to all 0s.)
4. When the negotiation to send information has taken place, data is transmitted across
the transmitted data (TD) and received data (RD) lines:
TDlineLine through which data froma DTE device is transmitted to a DCE device
RDlineLine through which data froma DCE device is transmitted to a DTE device
The name of the wire does not indicate the direction of data flow.
TheDTRandDSRsignals wereoriginally designedtooperateas ahandshakemechanism.
When a serial port is opened, the DTE device sets its DTR signal to a marked state.
Similarly, the DCE sets its DSR signal to a marked state. However, because of the
negotiation that takes place with the RTS and CTS signals, the DTR and DSR signals are
not commonly used.
The carrier detect and ring indicator signals are used to detect connections with remote
modems. These signals are not commonly used.
Signal Polarity
Serial interfaces use a balanced (also called differential) protocol signaling technique.
Two serial signals are associated with a circuit: the Asignal and the Bsignal. The Asignal
is denotedwith a plus sign (for example, DTR+), andthe Bsignal is denotedwith a minus
sign (for example, DTR). If DTR is low, then DTR+ is negative with respect to DTR. If
DTR is high, then DTR+ is positive with respect to DTR.
By default, all signal polarities are positive, but sometimes they might be reversed. For
example, signals might be miswired as a result of reversed polarities.
Serial Clocking Modes
By default, aserial interfaceuses loopclockingtodetermineits timingsource. For EIA-530
and V.35 interfaces, you can set each port independently to use one of the following
clocking modes. X.21 interfaces can use only loop clocking mode.
Loop clocking modeUses the DCE's receive (RX) clock to clock data fromthe DCE
to the DTE.
DCE clocking modeUses the transmit (TXC) clock, generated by the DCE specifically
to be used by the DTE as the DTE's transmit clock.
Internal clocking modeUses an internally generated clock. The speed of this clock is
configured locally. Internal clocking mode is also known as line timing.
Both loop clocking mode and DCE clocking mode use external clocks generated by the
DCE.
Figure28onpage403shows theclocksources for loop, DCE, andinternal clockingmodes.
Figure 28: Serial Interface Clocking Modes
Serial Interface Transmit Clock Inversion
When an externally timed clocking mode (DCE or loop) is used, long cables might
introduceaphaseshift of theDTE-transmittedclock anddata. At highspeeds, this phase
shift might cause errors. Inverting the transmit clock corrects the phase shift, thereby
reducing error rates.
Chapter 17: Serial Interfaces
DTE Clock Rate Reduction
Although the serial interface is intended for use at the default clock rate of 16.384 MHz,
you might need to use a slower rate under any of the following conditions:
The interconnecting cable is too long for effective operation.
The interconnecting cable is exposed to an extraneous noise source that might cause
an unwanted voltage in excess of +1 volt.
The voltage must be measured differentially between the signal conductor and the
point in the circuit fromwhich all voltages are measured (circuit common) at the
load end of the cable, with a 50-ohmresistor substituted for the generator.
Interference with other signals must be minimized.
Signals must be inverted.
Serial Line Protocols
Serial interfaces support the following line protocols:
EIA-530 on page 404
RS-232 on page 405
RS-422/449 on page 405
V.35 on page 406
X.21 on page 406
EIA-530
EIA-530 is an Electronic Industries Association (EIA) standard for the interconnection of
DTE and DCE using serial binary data interchange with control information exchanged
on separate control circuits. EIA-530 is also known as RS-530.
The EIA-530 line protocol is a specification for a serial interface that uses a DB-25
connector andbalancedequivalents of theRS-232signalsalsocalledV.24. TheEIA-530
lineprotocol is equivalent totheRS-422andRS-423interfaces implementedona25-pin
connector.
TheEIA-530lineprotocol supports bothbalancedandunbalancedmodes. Inunbalanced
transmissions, voltages are transmitted over a single wire. Because only a single signal
is transmitted, differences in ground potential can cause fluctuations in the measured
voltage across the link. For example, if a 3-V signal is sent fromone endpoint to another,
and the receiving endpoint has a ground potential 1 V higher than the transmitter, the
signal on the receiving end is measured as a 2-V signal.
Balancedtransmissions use twowires insteadof one. Rather thansending asingle signal
across thewireandhavingthereceivingendmeasurethevoltage, thetransmittingdevice
sends two separate signals across two separate wires. The receiving device measures
thedifferenceinvoltageof thetwosignals (balancedsampling) anduses that calculation
to evaluate the signal. Any differences in ground potential affect both wires equally, and
the difference in the signals is still the same.
The EIA-530 interface supports asynchronous and synchronous transmissions at rates
ranging from20 Kbps to 2 Mbps.
RS-232
RS-232 is aRecommendedStandard(RS) describing the most widely usedtype of serial
communication. The RS-232 protocol is used for asynchronous data transfer as well as
synchronous transfers using HDLC, Frame Relay, and X.25. RS-232 is also known as
EIA-232.
The RS-232 line protocol is very popular for low-speed data signals. RS-232 signals are
carried as single voltages referred to a common ground signal. The voltage output level
of these signals varies between 12 V and +12 V. Within this range, voltages between
3 V and +3 V are considered inoperative and are used to absorb line noise. Control
signals are considered operative when the voltage ranges from+3 V to +25 V.
The RS-232 line protocol is an unbalanced protocol, because it uses only one wire and
is susceptibletosignal degradation. Degradationcanbeextremelydisruptive, particularly
whenadifferenceingroundpotential exists betweenthetransmittingandreceivingends
of a link.
The RS-232 interface is implemented in a 25-pin D-shell connector and supports line
rates up to 200 Kbps over lines shorter than 98 feet (30 meters).
NOTE: RS-232 serial interfaces cannot function error-free with a clock rate
greater than 200 KHz.
RS-422/449
RS-422 is a Recommended Standard (RS) describing the electrical characteristics of
balancedvoltagedigital interfacecircuits that support higher bandwidths thantraditional
serial protocols like RS-232. RS-422 is also known as EIA-422.
The RS-449 standard (also known as EIA-449) is compatible with RS-422 signal levels.
The EIAcreatedRS-449todetail the DB-37 connector pinout anddefine a set of modem
control signals for regulating flowcontrol and line status.
The RS-422/499 line protocol runs in balanced mode, allowing serial communications
to extend over distances of up to 4,000 feet (1.2 km) and at very fast speeds of up to
10 Mbps.
In an RS-422/499-based system, a single master device can communicate with up to
10slavedevices inthesystem. Toaccommodatethis configuration, RS-422/499supports
the following kinds of transmission:
Half-duplex transmissionIn half-duplex transmission mode, transmissions occur in
only one direction at a time. Each transmission requires a proper handshake before it
is sent. This operation is typical of a balanced systemin which two devices are
connected by a single connection.
Full-duplex transmissionIn full duplex transmission mode, multiple transmissions
can occur simultaneously so that devices can transmit and receive at the same time.
This operation is essential when a single master in a point-to-multipoint systemmust
communicate with multiple receivers.
Multipoint transmissionRS-422/449 allows only a single master in a multipoint
system. The master can communicate to all points in a multipoint system, and the
other points must communicate with each other through the master.
V.35
V.35 is an ITU-T standard describing a synchronous, Physical Layer protocol used for
communications between a network access device and a packet network. V.35 is most
commonly used in the United States and Europe.
The V.35 line protocol is a mixture of balanced (RS-422) and common ground (RS-232)
signal interfaces. The V.35 control signals DTR, DSR, DCD, RTS, and CTS are single-wire
common ground signals that are essentially identical to their RS-232 equivalents.
Unbalanced signaling for these control signals is sufficient, because the control signals
aremostly constant, varyingat very lowfrequency, whichmakes single-wiretransmission
suitable. Higher frequency data and clock signals are sent over balanced wires.
V.35 interfaces operate at line rates of 20 Kbps and above.
X.21
X.21 is an ITU-T standard for serial communications over synchronous digital lines. The
X.21 protocol is used primarily in Europe and Japan.
The X.21 line protocol is a state-driven protocol that sets up a circuit-switched network
using call setup. X.21 interfaces use a 15-pin connector with the following eight signals:
Signal ground (G)Reference signal used to evaluate the logic states of the other
signals. This signal can be connected to the protective earth (ground).
DTE common return (Ga)Reference ground signal for the DCE interface. This signal
is used only in unbalanced mode.
Transmit (T)Binary signal that carries the data fromthe DTE to the DCE. This signal
can be used for data transfer or in call-control phases such as Call Connect or Call
Disconnect.
Receive (R)Binary signal that carries the data fromthe DCE to the DTE. This signal
can be used for data transfer or in call-control phases such as Call Connect or Call
Disconnect.
Control (C)DTE-controlled signal that controls the transmission on an X.21 link. This
signal must be on during data transfer, and can be on or off during call-control phases.
Indication (I)DCE-controlled signal that controls the transmission on an X.21 link.
This signal must be on during data transfer, and can be on or off during call-control
phases.
Signal Element Timing (S)Clocking signal that is generated by the DCE. This signal
specifies when sampling on the line must occur.
Byte Timing (B)Binary signal that is onwhendataor call-control informationis being
sampled. When an 8-byte transmission is over, this signal switches to off.
Transmissions across an X.21 link require both the DCE and DTE devices to be in a ready
state, indicated by an all 1s transmission on the T and R signals.
Related
Documentation
Example: Configuring a Serial Interface
This example shows howto complete the initial configuration on a serial interface.
Overviewon page 407
Requirements
Before you begin, install a serial PIMin the SRX Series device. See SRX Series Services
Gateways for the Branch Physical Interface Modules Hardware Guide.
Overview
interface.
In this example, you create the interface se-1/0/0. You create the basic configuration for
the newinterface by setting the encapsulation type to ppp. Then you set the logical
interface to 0. The logical unit number can range from0 through 16,384. You can enter
additional values for properties you need to configure on the logical interface, such as
logical encapsulation or protocol family. Finally, you set IPv4 address 10.10.10.10/24 on
the serial interface.
Configuration
CLI Quick
Configuration
To quickly configure a serial interface, copy the following commands and paste them
into the CLI:
[edit]
set interfaces se-1/0/0encapsulation ppp unit 0family inet address 10.10.10.10/24
Step-by-Step
Procedure
Mode.
To configure a serial interface:
[edit]
user@host# edit interfaces se-1/0/0
[edit interfaces se-1/0/0]
[edit interfaces se-1/0/0]
4. Specify an IPv4 address for the interface.
[edit interfaces se-1/0/0 unit 0]
user@host# set family inet address 10.10.10.10/24
se-1/0/0command. If the output does not display the intended configuration, repeat the
[edit]
user@host# showinterfaces se-1/0/0
encapsulation ppp;
unit 0 {
amily inet {
amily inet {
}
}
Verification
Purpose Use the ping tool on each peer address in the network to verify that all interfaces on the
device are operational.
the link state.
the round-trip time, in milliseconds, is listed in the time field. For more information about
Action Fromoperational mode, enter the showinterfaces detail command.
following:
se-1/0/0] level of the configuration hierarchy.
se-1/0/0 page.
interfaces statistics se-1/0/0 command.
Related
Documentation
Example: Deleting a Serial Interface
This example shows howto delete a serial interface.
Requirements
interface.
Overview
In this example, you delete the se-1/0/0 interface.
and their identifiers continue to appear on J-Web pages.
Configuration
Step-by-Step
Procedure
To delete a serial interface:
[edit]
user@host# delete se-1/0/0
[edit]
user@host# commit
Verification
Related
Documentation
PART 6
Link Services and Special Interfaces
Link Services Interfaces on page 413
CHAPTER 18
Link Services Interfaces
Link Services Interfaces Overviewon page 413
Link Services Configuration Overviewon page 420
Configuring Link Services on page 421
Verifying the Link Services Interface on page 433
Multilink Frame Relay on page 437
Compressed Real-Time Transport Protocol on page 441
Internal Interface ls-0/0/0 Upgrade and Configuration Rollback on page 443
Troubleshooting the Link Services Interface on page 445
Link Services Interfaces Overview
Link services include the multilink services Multilink Point-to-Point Protocol (MLPPP),
Multilink Frame Relay (MLFR), and Compressed Real-Time Transport Protocol (CRTP).
J Series devices support link services on the lsq-0/0/0 link services interface.
For information about which devices support the features documented in this chapter,
see the Junos OS Feature Support Reference for SRX Series and J Series Devices.
You configure the link services queuing interface (lsq-0/0/0) on a J Series device to
support multilink services and CRTP.
The link services interface on a J Series device consists of services provided by the
following interfaces on the Juniper Networks MSeries and T Series routing platforms:
multilink services interface (ml-fpc/pic/port), link services interface (ls-fpc/pic/port), and
linkservices intelligent queuinginterface(lsq-fpc/pic/port). Althoughthemultilinkservices,
link services, andlink services intelligent queuing (IQ) interfaces on MSeries andTSeries
routing platforms are installed on Physical Interface Cards (PICs), the link services
interface on a J Series device is an internal interface only and is not associated with a
physical mediumor Physical Interface Module (PIM).
NOTE: (ls-fpc/pic/port) is not supported on J series and SRX platforms.
For more information about the link services interfaces, see the Junos Services Interfaces
This section contains the following topics.
Services Available on a J Series Link Services Interface on page 414
Link Services Exceptions on J Series Services Routers on page 415
Configuring Multiclass MLPPP on page 415
Queuing with LFI on J Series Devices on page 417
Compressed Real-Time Transport Protocol Overviewon page 417
Configuring Fragmentation by Forwarding Class on page 418
Configuring Link-Layer Overhead on page 419
Services Available on a J Series Link Services Interface
On a J Series device, the link services interface is a logical interface available by default.
Table50onpage414summarizes theservices availableonaJ Series linkservices interface.
Table 50: Services Available on a J Series Link Services Interface
More Information Purpose Services
Example: Configuring an MLPPP Bundle on
page 422
Example: Configuring Multilink Frame Relay
MLFR FRF.15 on page 438
Example: Configuring Multilink Frame Relay
MLFR FRF.16 on page 440
Aggregates multiple constituent links into one
larger logical bundle to provide additional
bandwidth, load balancing, and redundancy.
Multilink bundles by means
of MLPPP and MLFR
encapsulation
Understanding Link Fragmentation and
Interleaving Configuration on page 424
Reduces delay and jitter on links by breaking
up large data packets and interleaving
delay-sensitivevoicepackets withtheresulting
smaller packets.
Link fragmentation and
interleaving (LFI)
Compressed Real-Time Transport Protocol
Overview on page 417
Reduces the overhead caused by Real-Time
Transport Protocol (RTP) on voice and video
packets.
Compressed Real-Time
Transport Protocol (CRTP)
Table 50: Services Available on a J Series Link Services Interface (continued)
More Information Purpose Services
Example: Defining and Applying Interface
Shaping Rates on page 432
Configuring Fragmentation by Forwarding
Class on page 418
Junos OSClass of ServiceConfigurationGuide
Provides a higher priority to delay-sensitive
packetsby configuring CoS, such as the
following:
ClassifiersTo classify different types of
traffic, such as voice, data, and network
control packets.
ForwardingclassesTodirect different types
of traffic to different output queues.
Fragmentation mapTo define mapping
betweenforwardingclassandmultilinkclass,
and forwarding class and fragment
threshold. In forwarding class and multilink
class mapping, drop timeout can be
configured.
Schedulers and scheduler mapsTo define
properties for the output queues such as
delay-buffer, transmission rate, and
transmission priority.
Shaping rateTo define certain bandwidth
usage by an interface.
Class-of-service (CoS)
classifiers, forwarding
classes, schedulers and
scheduler maps, and
shaping rates
Link Services Exceptions on J Series Services Routers
The link and multilink services implementation on a J Series Services Router is similar to
the implementation on the MSeries and T Series routing platforms, with the following
exceptions:
J Series devices support link and multilink services on the lsq-0/0/0 interface instead
of the ml-fpc/pic/port, lsq-fpc/pic/port, and ls-fpc/pic/port interfaces.
When LFI is enabled, fragmented packets are queued in a round-robin fashion on the
constituent links toenableper-packet andper-fragment loadbalancing. SeeQueuing
with LFI on J Series Devices on page 417.
J Series devices support per-unit scheduling on all types of constituent links (on all
types of interfaces).
J Series devices support Compressed Real-Time Transport Protocol (CRTP) with
MLPPP as well as PPP.
Configuring Multiclass MLPPP
For lsq-0/0/0 on SRX210, SRX240, SRX650, J2320, J2350, J4350, and J6350 devices,
with MLPPP encapsulation, you can configure multiclass MLPPP. If you do not configure
multiclass MLPPP, fragments fromdifferent classes cannot be interleaved. All fragments
for a single packet must be sent before the fragments fromanother packet are sent.
Nonfragmented packets can be interleaved between fragments of another packet to
reduce latency seen by nonfragmented packets. In effect, latency-sensitive traffic is
encapsulated as regular PPP traffic, and bulk traffic is encapsulated as multilink traffic.
This model works as long as there is a single class of latency-sensitive traffic, and there
Chapter 18: Link Services Interfaces
is nohigh-prioritytrafficthat takes precedenceover latency-sensitivetraffic. This approach
to LFI, used on the Link Services PIC, supports only two levels of traffic priority, which is
not sufficient tocarry the four-to-eight forwarding classes that are supportedby Mseries
and T series routing platforms.
Multiclass MLPPP makes it possible to have multiple classes of latency-sensitive traffic
that arecarriedover asinglemultilink bundlewithbulk traffic. Ineffect, multiclass MLPPP
allows different classes of traffic to have different latency guarantees. With multiclass
MLPPP, youcanmapeachforwardingclass intoaseparatemultilink class, thus preserving
priority and latency guarantees.
NOTE: Configuring both LFI and multiclass MLPPP on the same bundle is
not necessary, nor is it supported, because multiclass MLPPP represents a
superset of functionality. When you configure multiclass MLPPP, LFI is
automatically enabled.
The Junos OS PPP implementation does not support the negotiation of
address fieldcompressionandprotocol fieldcompressionPPPNCPoptions,
which means that the software always sends a full 4-byte PPP header.
The Junos OS implementation of multiclass MLPPP does not support
compression of common header bytes.
Multiclass MLPPPgreatly simplifies packet orderingissues that occur whenmultiplelinks
are used. Without multiclass MLPPP, all voice traffic belonging to a single flowis hashed
to a single link to avoid packet ordering issues. With multiclass MLPPP, you can assign
voice traffic to a high-priority class, and you can use multiple links. For more information
about voiceservices support onthelsq-0/0/0interface, seetheJunos OSFeatureSupport
Reference for SRX Series and J Series Devices.
To configure multiclass MLPPP on a link services IQinterface, you must specify how
many multilink classes should be negotiated when a link joins the bundle, and you must
specify the mapping of a forwarding class into an multiclass MLPPP class.
To specify howmany multilink classes should be negotiated when a link joins the bundle,
include the multilink-max-classes statement:
multilink-max-classes number;
You can include this statement at the following hierarchy levels:
[edit interfaces interface-name unit logical-unit-number]
[edit logical-routers logical-router-name interfaces interface-name unit
logical-unit-number]
The number of multilink classes can be 1 through 8. The number of multilink classes for
each forwarding class must not exceed the number of multilink classes to be negotiated.
To specify the mapping of a forwarding class into a multiclass MLPPP class, include the
multilink-class statement at the [edit class-of-service fragmentation-maps
forwarding-class class-name] hierarchy level:
edit class-of-service fragmentation-maps forwarding-class class-namemultilink-class
number
The multilink class index number can be 0 through 7. The multilink-class statement and
the no-fragmentation statement are mutually exclusive.
To viewthe number of multilink classes negotiated, issue the showinterfaces
lsq-0/0/0.logical-unit-number detail command.
Queuing with LFI on J Series Devices
LFI or non-LFI packets are placed into queues on constituent links based on the queues
in which they arrive. No changes in the queue number occur while the fragmented,
non-fragmented, or LFI packets are being queued.
For example, assume that Queue Q0 is configured with fragmentation threshold 128, Q1
is configured with no fragmentation, and Q2 is configured with fragmentation threshold
512. Q0 is receiving streamof traffic with packet size 512. Q1 is receiving voice traffic of
64 bytes, and Q2 is receiving streamof traffic with 128-byte packets. Next the streamon
Q0 gets fragmented and queued up into Q0 of a constituent link. The streamon Q1 is
considered to be LFI because no fragmentation is configured. Therefore, all packets on
Q1 are queued up on Q1 on constituent link. Because the fragmentation threshold of Q2
is more than the packet size it is receiving, the packet is queued on Q2 of a constituent
link without fragmenting, but with multilink header because it is a non-LFI packet.
Using lsq-0/0/0, CRTP can be applied on LFI and non-LFI packets. There will be no
changes in their queue numbers because of CRTP.
Queuing on Q2s of Constituent Links
When using class of service on a multilink bundle, all Q2 traffic fromthe multilink bundle
is queued to Q2 of constituent links based on a hash computed fromthe source address,
destination address, and the IP protocol of the packet. If the IP payload is TCP or UDP
traffic, the hash also includes the source port and destination port. As a result of this
hash algorithm, all traffic belonging to one traffic flowis queuedto Q2 of one constituent
link. This methodof traffic delivery to the constituent link is appliedat all times, including
when the bundle has not been set up with LFI.
Compressed Real-Time Transport Protocol Overview
Real-Time Transport Protocol (RTP) can help achieve interoperability among different
implementations of network audio and video applications. However, in some cases, the
header, which includes the IP, UDP, and RTPheaders, can be too large (around 40bytes)
on networks using low-speed lines such as dial-up modems. Compressed Real-Time
Transport Protocol (CRTP) can be configured to reduce network overhead on low-speed
links. CRTPreplaces theIP, UDP, andRTPheaders witha2-bytecontext ID(CID), reducing
the header overhead considerably.
Figure 29on page 418shows howCRTPcompresses the RTPheader in a voice packet by
reducing a 40-byte header to a 2-byte header.
Figure 29: CRTP
On J Series devices, you can configure CRTP with MLPPP or PPP logical interface
encapsulation on link services interfaces. See Example: Configuring an MLPPP Bundle
on page 422.
Real-time and non-real-time data frames are carried together on lower-speed links
without causing excessive delays to the real-time traffic. See Understanding Link
Fragmentation and Interleaving Configuration on page 424.
Configuring Fragmentation by Forwarding Class
you can specify fragmentation properties for specific forwarding classes. Traffic on each
forwarding class can be either multilink encapsulated (fragmented and sequenced) or
nonencapsulated (hashed with no fragmentation). By default, traffic in all forwarding
classes is multilink encapsulated.
Whenyoudonot configurefragmentationproperties for thequeues onMLPPPinterfaces,
the fragmentation threshold you set at the [edit interfaces interface-name unit
logical-unit-number fragment-threshold] hierarchy level is the fragmentation threshold
for all forwarding classes within the MLPPP interface. For MLFR FRF.16 interfaces, the
fragmentation threshold you set at the [edit interfaces interface-name
mlfr-uni-nni-bundle-options fragment-threshold] hierarchy level is the fragmentation
threshold for all forwarding classes within the MLFR FRF.16 interface.
If you do not set a maximumfragment size anywhere in the configuration, packets are
still fragmented if they exceed the smallest maximumtransmission unit (MTU) or
maximumreceived reconstructed unit (MRRU) of all the links in the bundle. A
nonencapsulated flowuses only one link. If the flowexceeds a single link, then the
forwarding class must be multilink encapsulated, unless the packet size exceeds the
MTU/MRRU.
Even if you do not set a maximumfragment size anywhere in the configuration, you can
configure the MRRU by including the mrru statement at the [edit interfaces lsq-0/0/0
unit logical-unit-number] or [edit interfaces interface-name mlfr-uni-nni-bundle-options]
hierarchy level. The MRRUis similar to the MTU, but is specific to link services interfaces.
By default the MRRUsize is 1504 bytes, and you can configure it to be from1500through
4500 bytes.
To configure fragmentation properties on a queue, include the fragmentation-maps
statement at the [edit class-of-service] hierarchy level:
[edit class-of-service]
fragmentation-maps {
map-name {
forwarding-class class-name {
fragment-threshold bytes;
multilink-class number;
no-fragmentation;
}
}
}
To set a per-forwarding class fragmentation threshold, include the fragment-threshold
statement in the fragmentation map. This statement sets the maximumsize of each
multilink fragment.
To set traffic on a queue to be nonencapsulated rather than multilink encapsulated,
include the no-fragmentation statement in the fragmentation map. This statement
specifies that an extra fragmentation header is not prepended to the packets received
onthis queueandthat staticlinkloadbalancingis usedtoensurein-order packet delivery.
For a given forwarding class, you can include either the fragment-threshold or
no-fragmentation statement; they are mutually exclusive.
Youusethemultilink-class statement tomapaforwardingclass intoamulticlass MLPPP.
For agivenforwardingclass, youcanincludeeither themultilink-class or no-fragmentation
statement; they are mutually exclusive.
To associate a fragmentation map with a multilink PPP interface or MLFR FRF.16 DLCI,
include the fragmentation-map statement at the [edit class-of-service interfaces
interface-name unit logical-unit-number] hierarchy level:
[edit class-of-service interfaces]
lsq-0/0/0 {
unit logical-unit-number { # Multilink PPP
fragmentation-map map-name;
}
}
lsq-0/0/0:channel { # MLFR FRF.16
unit logical-unit-number
fragmentation-map map-name;
}
}
Configuring Link-Layer Overhead
Link-layer overhead can cause packet drops on constituent links because of bit stuffing
on serial links. Bit stuffing is used to prevent data frombeing interpreted as control
information.
By default, 4 percent of the total bundle bandwidth is set aside for link-layer overhead.
In most network environments, the average link-layer overhead is 1.6 percent. Therefore,
we recommend 4 percent as a safeguard.
you can configure the percentage of bundle bandwidth to be set aside for link-layer
overhead. To do this, include the link-layer-overhead statement:
link-layer-overhead percent;
You can include this statement at the following hierarchy levels:
[edit interfaces interface-name mlfr-uni-nni-bundle-options]
[edit interfaces interface-name unit logical-unit-number]
[edit logical-routers logical-router-name interfaces interface-name unit
logical-unit-number]
You can configure the value to be from0 percent through 50 percent.
Related
Documentation
Understanding the Internal Interface LSQ-0/0/0 Configuration on page 443
Link Services Configuration Overview
Before you begin:
Install device hardware. See the J Series Services Routers Hardware Guide.
Establish basic connectivity. See the Getting Started Guide for your device.
Have a basic understanding of physical and logical interfaces and Juniper Networks
interface conventions. See Understanding Interfaces on page 3
Plan howyou are going to use the link services interface on your network. See Link
Services Interfaces Overview on page 413.
To configure link services on an interface, performthe following tasks:
1. ConfigureanMLPPPbundle. SeeExample: ConfiguringanMLPPPBundle onpage422.
2. Configure link fragmentation and interleaving (LFI). See Example: Configuring Link
Fragmentation and Interleaving on page 425.
3. Configure classifiers and forwarding classes. See Example: Defining Classifiers and
Forwarding Classes on page 426.
4. Configure scheduler maps. See Understanding Howto Define and Apply Scheduler
Maps on page 428.
5. Configure interface shaping rates. See Example: Defining and Applying Interface
Shaping Rates on page 432
6. To configure MLFR, see Example: Configuring Multilink Frame Relay MLFR FRF.15
onpage438or Example: ConfiguringMultilinkFrameRelay MLFRFRF.16 onpage440
7. To configure CRTP, see Example: Configuring Compressed Real-Time Transport
Protocol on page 442
Related
Documentation
Understanding Multilink Frame Relay FRF.15 on page 437
Understanding Compressed Real-Time Transport Protocol on page 441
Configuring Link Services
UnderstandingMLPPPBundles andLink FragmentationandInterleaving(LFI) onSerial
Links on page 421
Example: Configuring an MLPPP Bundle on page 422
Understanding Link Fragmentation and Interleaving Configuration on page 424
Example: Configuring Link Fragmentation and Interleaving on page 425
Understanding Howto Define Classifiers and Forwarding Classes on page 426
Example: Defining Classifiers and Forwarding Classes on page 426
Understanding Howto Define and Apply Scheduler Maps on page 428
Example: Defining and Applying Scheduler Maps on page 429
Understanding Interface Shaping Rates on page 431
Example: Defining and Applying Interface Shaping Rates on page 432
Understanding MLPPP Bundles and Link Fragmentation and Interleaving (LFI) on Serial Links
TheJ Series devicesupports MLPPPandMLFRmultilink encapsulations. MLPPPenables
you to bundle multiple PPP links into a single multilink bundle, and MLFR enables you to
bundle multiple Frame Relay data-link connection identifiers (DLCIs) into a single
multitlink bundle. Multilink bundles provide additional bandwidth, load balancing, and
redundancy by aggregating low-speed links, such as T1, E1, and serial links.
You configure multilink bundles as logical units or channels on the link services interface
lsq-0/0/0:
With MLPPP and MLFR FRF.15, multilink bundles are configured as logical units on
lsq-0/0/0for example, lsq-0/0/0.0 and lsq-0/0/0.1.
With MLFR FRF.16, multilink bundles are configured as channels on lsq-0/0/0for
example, lsq-0/0/0:0 and lsq-0/0/0:1.
After creating multilink bundles, you add constituent links to the bundle. The constituent
links are the low-speed physical links that are to be aggregated. You can create 64
multilink bundles, and on each multilink bundle you can add up to 8 constituent links.
The following rules apply when you add constituent links to a multilink bundle:
On each multilink bundle, add only interfaces of the same type. For example, you can
add either T1 or E1, but not both.
Only interfaces with a PPPencapsulation can be added to an MLPPPbundle, and only
interfaces with a Frame Relay encapsulation can be added to an MLFR bundle.
If an interface is a member of an existing bundle and you add it to a newbundle, the
interface is automatically deleted fromthe existing bundle and added to the new
bundle.
Related
Documentation
Example: Configuring an MLPPP Bundle on page 422
Example: Configuring Multilink Frame Relay MLFR FRF.15 on page 438
Example: Configuring an MLPPP Bundle
This example shows howto configure the MLPPP bundle and also shows howto verify
link services interface statistics. If you configure Class of Services (CoS) components
with LFI see Verifying Link Services CoS Configuration on page 435.
Overviewon page 422
Requirements
Before you begin, you should have two J Series devices configured with at least two serial
interfaces that communicate over serial links.
Overview
In this example, you create an MLPPP bundle (lsq-0/0/0.0) at the logical unit level of
the link services interface (lsq-0/0/0) on J Series devices R0 and R1. Then you add the
two serial interfaces se-1/0/0 and se-1/0/1 as constituent links to the multilink bundle.
Adding multiple links does not require you to configure and manage more addresses.
Figure30onpage423shows anetworktopology that is usedas anexampleinthis section.
In this example, your company's branch office is connected to its main branch using J
Series devices R0 and R1. You transmit data and voice traffic on two low-speed 1-Mbps
serial links. To increase bandwidth, you configure MLPPP and join the two serial links
se-1/0/0 and se-1/0/1 into a multilink bundle lsq-0/0/0.0. Then you configure LFI and
CoS on R0 and R1 to enable themto transmit voice packets ahead of data packets.
Figure 30: Configuring MLPPP and LFI on Serial Links
Configuring a multilink bundle on the two serial links increases the bandwidth by
70 percent fromapproximately 1 Mbps to 1.7 Mbps and prepends each packet with a
multilink header as specified in the FRF.12 standard. To increase the bandwidth further,
youcanaddupto8serial links tothebundle. Inadditiontoahigher bandwidth, configuring
the multilink bundle provides load balancing and redundancy. If one of the serial links
fails, traffic continues to be transmitted on the other links without any interruption. In
contrast, independent links require routing policies for load balancing and redundancy.
Independent links also require IP addresses for each link as opposed to one IP address
for thebundle. Intheroutingtable, themultilink bundleis representedas asingleinterface.
This example uses MLPPP for providing multilink services. For information about
configuring MLFR, see Example: Configuring Multilink Frame Relay MLFR FRF.15 on
page 438 and Example: Configuring Multilink Frame Relay MLFR FRF.16 on page 440.
You can use the LFI and CoS configurations provided in this example with MLFR FRF.15
and MLFR FRF.16 bundles, too. You can also use the same LFI and CoS configurations
for other interfaces, such as on T1 or E1.
Configuration
Step-by-Step
Procedure
To configure an MLPPP bundle on a J Series device:
Create the link services interface that will be configured. 1.
[edit]
edit interfaces lsq-0/0/0
2. Configure logical unit 0, family inet, and define the IP address on device R0.
[edit interfaces lsq-0/0/0]
set unit 0family inet address 10.0.0.10/24
3. Configure logical unit 0, family inet, and define the IP address on device R1.
set unit 0family inet address 10.0.0.9/24
4. Specify the names of the constituent links to be added to the multilink bundle from
the interfaces level and create the multilink bundle by specifying a logical unit on
each constituent link and defining it as an MLPPP bundle.
[edit interfaces]
edit se-1/0/0
set unit 0family mlppp bundle lsq-0/0/0.0
[edit interfaces]
edit se-1/0/1
5. Create the multilink bundle by specifying a logical unit on each constituent link and
defining it as an MLPPP bundlefor example, lsq-0/0/0.0.
[edit interfaces]
6. Set the serial options to the same values for both interfaces on R0se-1/0/0 and
se-1/0/1.
NOTE: Inthisexample, R0isset asadatacircuit-terminatingequipment
(DCE) device. The serial options are not set for interfaces on R1. You
can set the serial options according to your network setup.
[edit interfaces]
set se-1/0/0serial-options clocking-mode dce clock-rate 2.0mhz
set se-1/0/1 serial-options clocking-mode dce clock-rate 2.0mhz
Related
Documentation
UnderstandingMLPPPBundles andLink FragmentationandInterleaving(LFI) onSerial
Links on page 421
Understanding Link Fragmentation and Interleaving Configuration
As it does on any other interface, priority scheduling on a multilink bundle determines
theorder inwhichanoutput interfacetransmits trafficfromanoutput queue. Thequeues
areservicedinaweightedround-robinfashion. But whenaqueuecontaininglargepackets
starts using the multilink bundle, small and delay-sensitive packets must wait their turn
for transmission. Because of this delay, some slowlinks, such as T1 and E1, can become
useless for delay-sensitive traffic.
Link fragmentation and interleaving (LFI) solves this problem. It reduces delay and jitter
on links by fragmenting large packets and interleaving delay-sensitive packets with the
resultingsmaller packets for simultaneous transmissionacross multiplelinks of amultilink
bundle.
Figure31 onpage425illustrates howLFI works. Inthis figure, deviceR0anddeviceR1 have
LFI enabled. When device R0 receives large and small packets, such as data and voice
packets, it divides theminto two categories. All voice packets and any other packets
configured to be treated as voice packets are categorized as LFI packets and transmitted
without fragmentation or an MLPPP header. If CRTP is configured on the bundle, LFI
packetsaretransmittedthroughCRTPprocessing. Theremainingnon-LFI (data) packets
can be fragmented or unfragmented based on the configured fragmentation threshold.
The packets larger than the fragmentation threshold are fragmented. An MLPPP header
(containing a multilink sequence number) is added to all non-LFI packets, fragmented
and unfragmented.
The fragmentation is performed according to the fragmentation threshold that you
configure. For example, if youconfigureafragmentationthresholdof 128bytes, all packets
larger than 128 bytes are fragmented. When device R1 receives the packets, it sends the
unfragmentedvoicepacketsimmediatelybut buffersthepacket fragmentsuntil it receives
the last fragment for a packet. In this example, when device R1 receives fragment 5, it
reassembles the fragments and transmits the whole packet.
The unfragmented data packets are treated as a single fragment. Thus device R1 does
not buffer the unfragmented data packets and transmits themas it receives them.
Figure 31: LFI on a Services Router
Example: Configuring Link Fragmentation and Interleaving on page 425.
Related
Documentation
Example: Configuring Link Fragmentation and Interleaving on page 425
Example: Configuring Link Fragmentation and Interleaving
This example shows howto configure Link Fragmentation and Interleaving (LFI)
Requirements
Overview
To configure link fragmentation and interleaving (LFI), you define the MLPPP
encapsulation type and enable fragmentation and interleaving of packets by specifying
the following propertiesthe fragmentation threshold and fragmentationmaps with
a no-fragmentation knob mapped to the forwarding class of choice. In this example, a
fragmentationthresholdof 128bytes is set ontheMLPPPbundlethat applies toall traffic
on both constituent links, so that any packet larger than 128 bytes transmitted on these
links is fragmented.
Configuration
Step-by-Step
Procedure
To configure link fragmentation and interleaving:
Edit the lsq-0/0/0 interface. 1.
[edit interfaces]
user@host# edit interfaces lsq-0/0/0
2. Specify the multilink encapsulation type, enable LFI, and set the fragmentation
threshold for the multilink interface.
Fragment ThresholdSet the maximumsize, in bytes, for multilink packet
fragmentsfor example, 128. Any nonzero value must be a multiple of 64 bytes.
Thevaluecanbebetween128and16320. Thedefault is 0bytes (nofragmentation).
[edit]
user@host# set unit 0encapsulation multilink-ppp fragment-threshold 128
Related
Documentation
Understanding Link Fragmentation and Interleaving Configuration on page 424
Understanding Howto Define Classifiers and Forwarding Classes
By defining classifiers you associate incoming packets with a forwarding class and loss
priority. Based on the associated forwarding class, you assign packets to output queues.
To configure classifiers, you specify the bit pattern for the different types of traffic. The
classifier takes this bit pattern and attempts to match it to the type of packet arriving on
the interface. If the information in the packets header matches the specified pattern,
the packet is sent to the appropriate queue, defined by the forwarding class associated
with the classifier.
Related
Documentation
Example: Defining Classifiers and Forwarding Classes on page 426
Example: Defining Classifiers and Forwarding Classes
This example shows howto defining Classifiers and Forwarding Classes
Requirements
Overview
In this example, an IP precedence classifier, classify_input, is assigned to all incoming
traffic. The precedence bit value in the type of service (ToS) field is assumed to be 000
for all incoming data traffic and 010 for all incoming voice traffic. This classifier assigns
all data traffic to Q0 and all voice traffic to Q2, and fragmentation-map maps Q2 to
no-fragmentation. On a J Series device, when LFI is enabled, all traffic assigned to Q2 is
treated as LFI (voice) traffic. You do not need to assign network control traffic to a queue
explicitly, because it is assigned to Q3 by default.
For more information about configuring CoS components, see Junos OS Class of Service
Configuration Guide for Security Devices.
Configuration
Step-by-Step
Procedure
To define classifiers and forwarding classes:
Navigate to the Class of service level in the configuration hierarchy. 1.
[edit]
user@host# edit class-of-service
2. Configure a behavior aggregate (BA) classifier for classifying packets.
In this example, you specify the default IP precedence classifier, which maps IP
precedence bits to forwarding classes and loss priorities.
user@host# edit classifiers inet-precedence classify_input
3. For the classifier to assign an output queue to each packet, it must associate the
packet with a forwarding class.
Assign packets with IP precedence bits 000 to the DATA forwarding class, and
specify a lowloss priority.
user@host# set forwarding-classes DATAloss-priority lowcode-points 000
4. Assign packets with IP precedence bits 010 to the VOICE forwarding class, and
specify a lowloss priority.
user@host# set forwarding-class VOICE loss-priority lowcode-points 010
5. Assign each forwarding class one-to-one with the output queues.
DATAAssign to Queue 0.
VOICEAssign to Queue 2.
NC (Network Control)Assign to Queue 3. NC is assigned to Queue 3 by default.
user@host# set forwarding-classes queue 0DATA
user@host# set forwarding-classes queue 2 VOICE
user@host# set forwarding-classes queue 3 NC
6. Apply the behavior aggregate classifier to the incoming interface.
user@host# set unit 0classifiers inet-precedence classify_input
7. Configure fragmentation-map
user@host# set class-of-service fragmentation-maps FMforwarding-class VOICE
no-fragmentation
8. Attach fragmentation-map to lsq
user@host#set class-of-service interfaces lsq-0/0/0unit unit fragmentation-map
Related
Documentation
Understanding Howto Define Classifiers and Forwarding Classes on page 426
Understanding Howto Define and Apply Scheduler Maps
J Series devices support per-unit scheduling that allows youtoconfigure scheduler maps
on each MLPPP or MLFR multilink bundle. You can also configure scheduler maps on
constituent links, but you must maintain the same relative priority on the constituent
links and on the multilink bundle.
If you configure CoS components with LFI on a J Series device, we recommend that you
followcertain recommendations for shaping rate, scheduling priority, and buffer size. For
configurationinstructions, seeExample: ConfiguringanMLPPPBundle onpage422. For
more information about other CoS components, see Junos OS Class of Service
When you configure LFI, we recommend that you configure the shaping rate on each
constituent link of the multilink bundle. Shaping rate configuration on the constituent
links is required to limit the jitter on the LFI queue. If you anticipate no delay-sensitive or
jitter-sensitive traffic on the LFI queue, or if there is no LFI traffic at all, shaping rate
configuration is optional.
For information about howto configure a shaping rate, see Junos OS Class of Service
Table 51 on page 429 shows an example of correct and incorrect relative priorities on a
multilink bundle andits constituent link. Inthis example, youhave assignedahighpriority
to LFI packets and a lowpriority to data packets on the multilink bundle. To maintain the
relative priority on the constituent links, you can assign a high priority to the LFI packets
and a medium-high priority to the data packets, but you cannot assign a medium-high
priority to LFI packets and a high priority to data packets.
Table 51: Relative Priorities on Multilink Bundles and Constituent Links
Incorrect Constituent Link Priorities Correct Constituent Link Priorities Multilink Bundle
LFI packetMedium-high priority LFI packetsHigh priority LFI packetsHigh priority
Data packetsHigh priority Data packetsMedium-high priority Data packetsLowpriority
By defining schedulers you configure the properties of output queues that determine the
transmissionservicelevel for eachqueue. Thesepropertiesincludetheamount of interface
bandwidth assigned to the queue, the size of the memory buffer allocated for storing
packets, and the priority of the queue. After defining schedulers you associate themwith
forwarding classes by means of scheduler maps. You then associate each scheduler
map with an interface, thereby configuring the hardware queues and packet schedulers
that operate according to this mapping.
Related
Documentation
Example: Defining and Applying Scheduler Maps on page 429
Example: Defining and Applying Scheduler Maps
This example shows howto configure scheduler maps.
Requirements
Overview
In this example, you define and apply scheduler maps on device R0 and R1 as follows:
Enable per-unit scheduling that allows configurationof scheduler maps onthe bundle.
Create three schedulersDATA, VOICE, and NC. Define the VOICE and NC schedulers
to have a high priority and the DATA scheduler to have the default priority (low). These
priority assignments allowall voiceandnetwork control traffictobetransmittedahead
of data packets. For more information about scheduling priorities, see Queuing with
LFI on J Series Devices on page 417.
Create a scheduler map s_map that associates these schedulers with corresponding
forwarding classes.
Apply the scheduler map to the multilink bundle and the serial interfaces.
Go on to Understanding Interface Shaping Rates on page 431.
Configuration
Step-by-Step
Procedure
To configure scheduler maps:
Go to the interfaces hierarchy hierachy 1.
[edit]
2. ToconfigureCoScomponents for eachmultilink bundle, enableper-unit scheduling
on the interface.
[edit interfaces]
user@host# set lsq-0/0/0per-unit-scheduler
user@host# set se-1/0/0per-unit-scheduler
user@host# set se-1/0/1 per-unit-scheduler
3. Navigate to the Interfaces level in the Class of Service configuration hierarchy and
specify the link services intelligent queuing interface to be configured.
[edit]
user@host# edit class-of-services lsq-0/0/0
4. Define a scheduler mapfor example, s_map.
user@host# set unit 0scheduler-map s_map
5. Apply the scheduler map to the constituent links of the multilink bundlefor
example, se-1/0/0 and se-1/0/1.
Fromthe[edit interfaces] hierarchy level, specify theinterfaceandapply thesheduler
map.
[edit interfaces]
user@host# set interfaces se-1/0/0unit 0scheduler-map s_map
user@host# set interfaces se-1/0/1 unit 0scheduler-map s_map
6. Associate a scheduler with each forwarding class.
DATAA scheduler associated with the DATA forwarding class.
VOICEA scheduler associated with the VOICE forwarding class.
NCA scheduler associated with the NC forwarding class.
A scheduler receives the forwarding class and loss priority settings, and queues the
outgoing packet based on those settings.
Fromthe [edit class-of-service] hierarchy level, enter
user@host# set scheduler-maps s_map forwarding-class DATAscheduler DATA
user@host# set scheduler-maps s_map forwarding-class VOICE scheduler VOICE
user@host# set scheduler-maps s_map forwarding-class NC scheduler NC
7. Define the properties of output queues for the DATA scheduler:
Transmit rateSpecify a percentage of transmission capacity49.
Buffer sizeSpecify a percentage of total buffer49.
PriorityDo not specify the transmission priority for the DATA scheduler to apply
the default settinglow.
For more information about transmit rate and buffer size, see Junos OS Class of
Service Configuration Guide for Security Devices.
user@host# set schedulers DATAtransmit-rate percent 49
user@host# set schedulers DATAbuffer-size percent 49
8. Define the properties of output queues for the VOICE scheduler:
PrioritySpecify a transmission priorityhigh.
user@host# set schedulers VOICE transmit-rate percent 50
user@host# set schedulers VOICE buffer-size percent 5
user@host# set schedulers VOICE priority high
9. Define the properties of output queues for the NC scheduler:
PrioritySpecify a transmission priorityhigh.
user@host# set schedulers NC transmit-rate percent 1
user@host# set schedulers NC buffer-size percent 1
user@host# set schedulers NC priority high
Related
Documentation
Understanding Interface Shaping Rates
When you configure LFI, we recommend that you configure the shaping rate on each
constituent link of the multilink bundle. Shaping rate configuration on the constituent
links is required to limit the jitter on the LFI queue. If you anticipate no delay-sensitive or
jitter-sensitive traffic on the LFI queue, or if there is no LFI traffic at all, shaping rate
configuration is optional.
For information about howto configure a shaping rate, see Junos OS Class of Service
Related
Documentation
Example: Defining and Applying Interface Shaping Rates on page 432
Example: Defining and Applying Interface Shaping Rates
This example shows howto configure interface shaping rates.
Requirements
Overview
To control the voice traffic latency within acceptable limits, you configure the shaping
rate on constituent links of the MLPPP bundle. Shaping rate at the interface level is
required only when you enable LFI. To apply shaping rates to interfaces, you have to first
enable per-unit scheduling. For information about shaping rates and LFI, see
Understanding Interface Shaping Rates on page 431.
You must configure the shaping rate to be equal to the combined physical interface
bandwidth for the constituent links. In this example, the combined bandwidth capacity
of thetwoconstituent linksse-1/0/0andse-1/0/1is 2Mbps. Hence, configureashaping
rate of 2 Mbps on each constituent link.
Configuration
Step-by-Step
Procedure
To apply a shaping rate to the constituent links of the multilink bundle:
Navigate to the Class of service level in the configuration hierarchy. 1.
[edit]
user@host# edit class-of-service
2. Apply the shaping rate tothe constituent links of the multilink bundlefor example,
se-1/0/0 and se-1/0/1. The shaping rate specifies the amount of bandwidth to be
allocated for this multilink bundle.
user@host# set interfaces se-1/0/0unit 0shaping-rate 2000000
user@host# set interfaces se-1/0/1 unit 0shaping-rate 2000000
Related
Documentation
Verifying the Link Services Interface
Verifying Link Services Interface Statistics on page 433
Verifying Link Services CoS Configuration on page 435
Verifying Link Services Interface Statistics
Purpose Verify the link services interface statistics.
Action The sample output provided in this section is based on the configurations provided in
Example: ConfiguringanMLPPPBundle onpage422. Toverify that theconstituent links
are added to the bundle correctly and the packets are fragmented and transmitted
correctly, take the following actions:
1. On device R0 and device R1, the two J Series devices used in this example, configure
MLPPPandLFI as describedinExample: ConfiguringanMLPPPBundle onpage422.
2. Fromthe CLI, enter the ping command to verify that a connection is established
between R0 and R1.
3. Transmit 10 data packets, 200 bytes each, fromR0 to R1.
4. On R0, fromthe CLI, enter the showinterfaces interface-name statistics command.
Sample Output user@R0> showinterfaces lsq-0/0/0statistics detail
Physical interface: lsq-0/0/0, Enabled, Physical link is Up
Traffic statistics:
...
0 DATA 10 10 0
2 VOICE 0 0 0
3 NC 0 0 0
Logical interface lsq-0/0/0.0 (Index 67) (SNMP ifIndex 41) (Generation 133)
Bandwidth: 16mbps
Bundle options:
...
Drop timer period 0
Sequence number format long (24 bits)
Fragmentation threshold 128
Links needed to sustain bundle 1
Interleave fragments Enabled
Bundle errors:
Packet drops 0 (0 bytes)
Fragment drops 0 (0 bytes)
...
Bundle:
Fragments:
Input : 0 0 0 0
Output: 20 0 1920 0
Packets:
Input : 0 0 0 0
Output: 10 0 1820 0
Link:
se-1/0/0.0
Input : 0 0 0 0
Output: 10 0 1320 0
se-1/0/1.0
Input : 0 0 0 0
Output: 10 0 600 0
...
Destination: 10.0.0.9/24, Local: 10.0.0.10, Broadcast: Unspecified,
Generation:144
Meaning This output shows a summary of interface information. Verify the following information:
Physical interfaceThe physical interface is Enabled. If the interface is shown as
Disabled, do either of the following:
Physical linkThe physical link is Up. A link state of Down indicates a problemwith the
interface module, interface port, or physical connection (link-layer errors).
Last flappedThe Last Flapped time is an expected value. The Last Flapped time
indicates the last time the physical interface became unavailable and then available
again. Unexpected flapping indicates likely link-layer errors.
Traffic statisticsNumber and rate of bytes and packets received and transmitted on
the interface. Verify that the number of inbound and outbound bytes and packets
match the expected throughput for the physical interface. To clear the statistics and
see only newchanges, use the clear interfaces statistics interface-name command.
Queue countersName and number of queues are as configured. This sample output
shows that 10 data packets were transmitted and no packets were dropped.
Logical interfaceName of the multilink bundle you configuredlsq-0/0/0.0.
Bundle optionsFragmentation threshold is correctly configured, and fragment
interleaving is enabled.
Bundle errorsAny packets and fragments dropped by the bundle.
StatisticsThe fragments and packets are received and transmitted correctly by the
device. All references to traffic direction (input or output) are defined with respect to
the device. Input fragments received by the device are assembled into input packets.
Output packets are segmented into output fragments for transmission out of the
device.
In this example, 10 data packets of 200 bytes were transmitted. Because the
fragmentation threshold is set to 128bytes, all data packets were fragmented into two
fragments. The sample output shows that 10 packets and 20 fragments were
transmitted correctly.
LinkThe constituent links are addedto this bundle andare receiving andtransmitting
fragments and packets correctly. The combined number of fragments transmitted on
the constituent links must be equal to the number of fragments transmitted fromthe
bundle. This sample output shows that the bundle transmitted 20 fragments and the
two constituent links se-1/0/0.0 and se-1/0/1.0.0 correctly transmitted 10+10=20
fragments.
Destination and LocalIP address of the remote side of the multilink bundle and the
local side of the multilink bundle. This sample output shows that the destination
address is the address on R1 and the local address is the address on R0.
For a complete description of showinterfaces output, see the Junos Interfaces Command
Reference.
Verifying Link Services CoS Configuration
Purpose Verify CoS configurations on the link services interface.
Action Fromthe CLI, enter the following commands:
showclass-of-service interface interface-name
showclass-of-service classifier name classifier-name
showclass-of-service scheduler-map scheduler-map-name
The sample output provided in this section is based on the configurations provided
inExample: Configuring an MLPPP Bundle on page 422.
Sample Output user@R0> showclass-of-service interface lsq-0/0/0
Physical interface: lsq-0/0/0, Index: 136
Queues supported: 8, Queues in use: 4
Scheduler map: [default], Index: 2
Input scheduler map: [default], Index: 3
Chassis scheduler map: [default-chassis], Index: 4
Logical interface: lsq-0/0/0.0, Index: 69
Object Name Type Index
Scheduler-map s_map Output 16206
Classifier ipprec-compatibility ip 12
user@R0> showclass-of-service interface ge-0/0/1
Physical interface: ge-0/0/1, Index: 140
Queues supported: 8, Queues in use: 4
Scheduler map: [default], Index: 2
Input scheduler map: [default], Index: 3
Logical interface: ge-0/0/1.0, Index: 68
Object Name Type Index
Classifier classfy_input ip 4330
user@R0> showclass-of-service classifier name classify_input
Classifier: classfy_input, Code point type: inet-precedence, Index: 4330
Code point Forwarding class Loss priority
000 DATA low
010 VOICE low
user@R0> showclass-of-service scheduler-map s_map
Scheduler map: s_map, Index: 16206
Scheduler: DATA, Forwarding class: DATA, Index: 3810
Transmit rate: 49 percent, Rate Limit: none, Buffer size: 49 percent,
Priority:low
Drop profiles:
Loss priority Protocol Index Name
Low any 1 [default-drop-profile]
Medium low any 1 [default-drop-profile]
Medium high any 1 [default-drop-profile]
High any 1 [default-drop-profile]
Scheduler: VOICE, Forwarding class: VOICE, Index: 43363
Transmit rate: 50 percent, Rate Limit: none, Buffer size: 5 percent,
Priority:high
Drop profiles:
Scheduler: NC, Forwarding class: NC, Index: 2435
Transmit rate: 1 percent, Rate Limit: none, Buffer size: 1 percent, Priority:high
Drop profiles:
Meaning These output examples showa summary of configured CoS components. Verify the
following information:
Logical InterfaceName of the multilink bundle and the CoS components applied to
the bundle. The sample output shows that the multilink bundle is lsq-0/0/0.0, and
the CoS scheduler-map s_map is applied to it.
ClassifierCodepoints, forwardingclasses, andloss priorities assignedtotheclassifier.
The sample output shows that a default classifier, ipprec-compatibility, was applied
to the lsq-0/0/0 interface and the classifier classify_input was applied to the ge-0/0/1
interface.
SchedulerTransmit rate, buffer size, priority, and loss priority assigned to each
scheduler. The sample output displays the data, voice, andnetwork control schedulers
with all the configured values.
For complete descriptions of showclass-of-service commands andoutput, see the Junos
SystemBasics and Services Command Reference.
Multilink Frame Relay
Understanding Multilink Frame Relay FRF.15
J Series devices support Multilink Frame Relay end-to-end (MLFR FRF.15) on the link
services intelligent queuing interface lsq-0/0/0.
With MLFR FRF.15, multilink bundles are configured as logical units on the link services
intelligent queuinginterface, suchas lsq-0/0/0.0. MLFRFRF.15bundles combinemultiple
permanent virtual circuits (PVCs) into one aggregated virtual circuit (AVC). This process
provides fragmentation over multiple PVCs on one end and reassembly of the AVC on
the other end. For more informationabout multilink bundles, see UnderstandingMLPPP
Bundles and Link Fragmentation and Interleaving (LFI) on Serial Links on page 421.
You can configure LFI and CoS with MLFR in the same way that you configure themwith
MLPPP. For information about configuring LFI and CoS, see Example: Configuring an
MLPPP Bundle on page 422.
Related
Documentation
Example: Configuring Multilink Frame Relay MLFR FRF.15
This example shows howto configure MLFR FRF.15.
Overviewon page 438
Requirements
Overview
In this example, you aggregate two T1 links to create an MLFR FRF.15 bundle on two J
Series devicesDevice R0 and deviceR1.
Configuration
Step-by-Step
Procedure
To configure an MLFR FRF.15 bundle:
Navigate to the Interfaces level in the configuration hierarchy. Specify the link
services intelligent queuing interface as an interface to be configured.
1.
[edit]
user@host# edit interfaces lsq-0/0/0
2. Configure a logical unit on the lsq-0/0/0 interface, and define the family typefor
example, Inet.
Configure an IP address for the multilink bundle on the unit level of the link services
intelligent queuing interface.
On device R0, enter
On device R1, enter
3. Define the multilink bundle as an MLFR FRF.15 bundle by specifying the Multilink
Frame Relay end-to-end encapsulation type.
user@host# set unit 0encapsulation multilink-frame-relay-end-to-end
4. Specify the names of the constituent links to be added to the multilink bundlefor
example, t1-2/0/0 and t1-2/0/1.
Define the Frame Relay encapsulation type.
[edit interfaces]
user@host# set t1-2/0/0encapsulation frame-relay
user@host# set t1-2/0/1 encapsulation frame-relay
5. Define R0to be a data circuit-terminating equipment (DCE) device. R1 performs as
a data terminal equipment (DTE) device, which is the default with Frame Relay
encapsulation.
For more information about DCE and DTE, see Serial Interfaces Overview on
page 401.
On device R0 only, enter:
user@host# set dce
6. On the logical unit level of the interface, specify the data-link connection identifier
(DLCI). The DLCI field identifies which logical circuit the data travels over. DLCI is
a value from16through 1022for example, 100. (Numbers 1 through 15are reserved
for future use.)
Specify the multilink bundle to which the interface is to be added as a constituent
linklsq-0/0/0.0.
user@host# set unit 0dlci 100family mlfr-end-to-end bundle lsq-0/0/0.0
Related
Documentation
Understanding Multilink Frame Relay FRF.16
J Series devices support Multilink Frame Relay (MLFR) user-to-network interface (UNI)
network-to-network interface(NNI) (MLFRFRF.16) onthelink services intelligent queuing
interface lsq-0/0/0.
MLFR FRF.16 configures multilink bundles as channels on the link services intelligent
queuinginterface, suchas lsq-0/0/0:0. Amultilink bundlecarries FrameRelay permanent
virtual circuits (PVCs), identified by their data-link connection identifiers (DLCIs). Each
DLCI is configured at the logical unit level of the link services intelligent queuing interface
and is also referred as a logical interface. Packet fragmentation and reassembly occur
oneachvirtual circuit. For more informationabout multilink bundles, see Understanding
MLPPPBundlesandLinkFragmentationandInterleaving(LFI) onSerial Links onpage421.
You can configure LFI and CoS with MLFR in the same way that you configure themwith
MLPPP. For information about configuring LFI and CoS, see Example: Configuring an
MLPPP Bundle on page 422.
Related
Documentation
Example: Configuring Multilink Frame Relay MLFR FRF.16
This example shows howto configure MLFR FRF.16.
Overviewon page 440
Requirements
Overview
In this example, you aggregate two T1 interfaces to create an MLFR FRF.16 bundle on
two J Series devicesDevice R0 and Device R1.
Configuration
Step-by-Step
Procedure
To configure an MLFR FRF.16 bundle:
Navigate to the Chassis level in the configuration hierarchy. 1.
[edit]
user@host# edit chassis
2. Specify the number of multilink frame relay UNI NNI (FRF.16) bundles to be created
on the interface. You can specify a number from1 through 255.
[edit chassis]
user@host# set fpc 0pic 0mlfr-uni-nni-bundles 1
3. Specify the channel to be configured as a multilink bundle.
Navigate to the edit hierarchy.
[edit]
user@host# edit interfaces lsq-0/0/0:0
4. Define the multilink bundle as an MLFR FRF.16 bundle by specifying the Multilink
Frame Relay UNI NNI encapsulation type.
[edit interfaces lsq-0/0/0.0]
user@host# set encapsulation multilink-frame-relay-uni-nni
5. Define R0to be a data circuit-terminating equipment (DCE) device. R1 performs as
a data terminal equipment (DTE) device, which is the default with Frame Relay
encapsulation.
For more information about DCE and DTE, see Serial Interfaces Overview on
page 401.
On device R0 only, enter:
user@host# set dce
6. Configure a logical unit on the multilink bundle lsq-0/0/0:0, and define the family
typefor example, Inet.
Assign a data link connection identifier (DLCI) to the multilink bundle. The DLCI
field identifies which logical circuit the data travels over. DLCI is a value from16
through1022for example, 400. (Numbers 1 through15arereservedfor futureuse.)
Assign an IP address to the multilink bundle.
On device R0, enter:
user@host# set unit 0dlci 400family inet address 10.0.0.10/24
On device R1, enter:
user@host# set unit 0dlci 400family inet address 10.0.0.9/24
7. Create the T1 interfaces that are to be added as constituent links to the multilink
bundlet1-2/0/0 and t1-2/0/1.
Define the Frame Relay encapsulation type.
Navigate to the edit interfaces hierarchy.
[edit interfaces]
set t1-2/0/0 encapsulation multilink-frame-relay-uni-nni
set t1-2/0/1 encapsulation multilink-frame-relay-uni-nni
8. Specify the multilink bundle to which the interface is to be added as a constituent
linklsq-0/0/0:0.
[edit interfaces]
set unit 0 family mlfr-uni-nni bundle lsq-0/0/0:0
Related
Documentation
Compressed Real-Time Transport Protocol
Example: Configuring Compressed Real-Time Transport Protocol on page 442
Understanding Compressed Real-Time Transport Protocol
Compressed Real-Time Transport Protocol (CRTP) is typically used for compressing
voice and video packets. You can configure CRTP with LFI on the link services interface
of a J Series device.
On the J Series device, CRTP can be configured as a compression device on a T1 or E1
interface with PPP encapsulation, using the link services interface.
Related
Documentation
Example: Configuring Compressed Real-Time Transport Protocol on page 442
For more information about configuring CRTP on a single link, see the Junos Network
Interfaces Configuration Guide and the Junos Services Interfaces Configuration Guide.
Example: Configuring Compressed Real-Time Transport Protocol
This example shows howto configure CRTP.
Requirements
Overview
This examples shows howto add CRTP on a T1 or E1 interface. The interface t11/0/0 is
used in the example and will have an F-max period of 2500, minimumUDP port value
of 2000, and a maximumUDP port value of 64009.
Configuration
Step-by-Step
Procedure
To configure CRTP on the device:
Navigate to the Interfaces level in the configuration hierarchy. 1.
[edit]
2. Select an E1 or T1 interfacefor example, t11/0/0.
Set PPP as the type of encapsulation for the physical interface.
[edit interfaces]
user@host# edit t1-1/0/0
3. Add the link services intelligent queuing interface, lsq-0/0/0.0, to the physical
interface.
user@host# set compression-device lsq-0/0/0.0
4. Add the link services intelligent queuing interface, lsq-0/0/0, to the device.
Fromthe [edit interfaces] hierarchy level, enter:
[edit interfaces]
user@host# edit lsq-0/0/0unit 0
5. Configure the link services intelligent queuing interface, lsq-0/0/0, properties.
F-max periodMaximumnumber of compressed packets allowed between
transmission of full headers. It has a range from1 to 65535.
Maximumand MinimumUDP port values from1 to 65536 reserve these ports for
RTPcompression. CRTPis appliedtonetwork traffic on ports within this range. This
feature is applicable only to voice services interfaces.
[edit interfaces lsq-0/0/0.0]
user@host#set compressionrtpf-max-period2500port minimum2000maximum
64009
Related
Documentation
Internal Interface ls-0/0/0Upgrade and Configuration Rollback
Example: Upgrading Configuration to Change ls-0/0/0 to lsq-0/0/0 on page 443
Understanding the Internal Interface LSQ-0/0/0Configuration
The link services interface is an internal interface only. It is not associated with a physical
mediumor PIM. Within a J-Series or an SRX series device, packets are routed to this
interface for link bundling or compression.
It may be required that you upgrade your configuration to use the internal interface
lsq-0/0/0 as the link services queuing interface instead of ls-0/0/0, which has been
deprecated. You can also roll back your modified configuration to use ls-0/0/0.
Related
Documentation
Example: Upgrading Configuration to Change ls-0/0/0 to lsq-0/0/0 on page 443
Example: Upgrading Configuration to Change ls-0/0/0to lsq-0/0/0
This example shows howto change ls-0/0/0 to lsq-0/0/0.
Requirements
This procedureis only necessary if your deviceis still usingls-0/0/0insteadof lsq-/0/0/0.
Overview
This example will showyou howto rename the link services internal interface ls-0/0/0
to lsq-0/0/0 and also shows you howto reverse that change.
Configuration
Step-by-Step
Procedure
Rename all occurrences of ls-0/0/0 in the configuration to lsq-0/0/0.
[edit]
1.
user@host# rename interfaces ls-0/0/0to lsq-0/0/0
2. If interleave-fragments is configured under the [edit interfaces ls-0/0/0 unit
unit-number] hierarchy, followthese steps:
a. Configure the fragmentation map (fragmentation-map) by adding
no-fragmentation for the map under the [edit class-of-service
fragmentation-maps map-name forwarding-class ] hierarchy.
Specify no-fragmentation after the Q2 name, if Q2 is configured or after
assured-forwarding.
[edit class-of-service fragmentation-maps]
user@host# set map6 forwarding-class assured-forwarding no-fragmentation
b. Attach the fragmentation map configured in the preceding step to lsq-0/0/0
under the[edit class-of-serviceinterfaces lsq-0/0/0unit unit-number] hierarchy.
For unit-number, specify the unit number of the multilink bundle for which
interleave-fragments is configured.
[edit class-of-service ]
user@host# set interfaces lsq-0/0/0unit 6 fragmentation-map map6
3. Commit the configuration.
[edit]
user@host# commit
Step-by-Step
Procedure
To roll back the configuration fromlsq-0/0/0 to ls-0/0/0, followthese steps:
For all occurrences in the configuration, rename lsq-0/0/0 to ls-0/0/0. 1.
[edit]
user@host# rename interfaces lsq-0/0/0to ls-0/0/0
2. If thefragmentationmapis configuredunder the[class-of-service] hierarchy, delete
it.
[edit]
user@host delete class-of-service fragmentation-maps map6
3. If the fragmentation map is assigned to the lsq-0/0/0 interface under the [edit
class-of-service interfaces lsq-0/0/0] hierarchy, delete it.
[edit class-of-service interfaces]
user@host delete lsq-0/0/0unit 6 fragmentation-map map6
4. If multilink-max-classes is configured for lsq-0/0/0 under the [edit interfaces]
hierarchy, delete it.
NOTE: Multilink-max-classes is not supported and is most likely not
configured.
5. If link-layer-overhead is configured for lsq-0/0/0 under the interfaces hierarchy,
delete it.
[edit interfaces]
user@host# delete lsq-0/0/0unit 6 link-layer-overhead
6. If link-layer-overhead is configured under the [edit interfaces lsq-0/0/0:channel-id
mlfr-uni-nni-bundle-options] hierarchy, delete it.
[edit interfaces]
user@host# delete lsq-0/0/0:0mlfr-uni-nni-bundle-options link-layer-overhead
7. If no-fragmentation is configured on any forwarding-class under the [edit
class-of-service fragmentation-map map-name] hierarchy and the fragmentation
map is assigned to lsq-0/0/0 under the [edit class-of-service interfaces], follow
these steps:
a. Configure interleave-fragments for the ls-0/0/0 interface.
[edit interfaces]
user@host# set ls-0/0/0unit 6 interleave-fragments
b. Configure the classifier for LFI packets to refer to Q2. (The ls-0/0/0 interface
treats Q2 as the LFI queue.)
8. Commit the configuration.
[edit]
user@host# commit
Related
Documentation
Troubleshooting the Link Services Interface
To solve configuration problems on a link services interface:
Determine Which CoS Components Are Applied to the Constituent Links on page 445
Determine What Causes Jitter and Latency on the Multilink Bundle on page 447
Determine If LFI and Load Balancing Are Working Correctly on page 447
Determine Why Packets Are Dropped on a PVCBetween a J Series Device and Another
Vendor on page 454
Determine Which CoS Components Are Applied to the Constituent Links
Problem You are configuring a multilink bundle, but you also have traffic without MLPPP
encapsulation passing through constituent links of the multilink bundle. Do you apply all
CoS components to the constituent links, or is applying themto the multilink bundle
enough?
Solution On a J Series device you can apply a scheduler map to the multilink bundle and its
constituent links. Although you can apply several CoS components with the scheduler
map, configure only the ones that are required. We recommend that you keep the
configuration on the constituent links simple to avoid unnecessary delay in transmission.
Table52onpage446showstheCoScomponentstobeappliedonamultilinkbundleand
its constituent links.
Table 52: CoS Components Applied on Multilink Bundles and Constituent Links
Explanation
Constituent
Links
Multilink
Bundle Cos Component
CoS classification takes place on the incoming side of
the interface, not on the transmitting side, so no
classifiers are needed on constituent links.
No Yes Classifier
Forwarding class is associated with a queue, and the
queueis appliedtotheinterfaceby ascheduler map. The
queue assignment is predetermined on the constituent
links. All packets fromQ2 of the multilink bundle are
assigned to Q2 of the constituent link, and packets from
all the other queues are queuedtoQ0of the constituent
link.
No Yes Forwarding class
Apply scheduler maps on the multilink bundle and the
constituent link as follows:
Transmit rateMake sure that the relative order of the
transmit rate configured on Q0and Q2 is the same on
the constituent links as on the multilink bundle.
Scheduler priorityMake sure that the relative order
of the scheduler priority configured on Q0 and Q2 is
the same on the constituent links as on the multilink
bundle.
Buffer sizeBecause all non-LFI packets fromthe
multilink bundle transit on Q0of the constituent links,
makesurethat thebuffer sizeonQ0of theconstituent
links is large enough.
REDdrop profileConfigure a REDdrop profile on the
multilink bundleonly. ConfiguringtheREDdropprofile
on the constituent links applies a back pressure
mechanismthat changes the buffer size and
introduces variation. Because this behavior might
cause fragment drops on the constituent links, make
sure to leave the RED drop profile at the default
settings on the constituent links.
Yes Yes Scheduler map
Because per-unit scheduling is applied only at the end
point, apply this shapingratetotheconstituent links only.
Any configuration applied earlier is overwritten by the
constituent link configuration.
Yes No Shaping rate for a per-unit
scheduler or an
interface-level scheduler
The interface-level shaping applied on the constituent
links overrides any shaping on the queue. Thus apply
transmit-rateexact shapingonthemultilink bundleonly.
No Yes Transmit-rate exact or
queue-level shaping
Table 52: CoS Components Applied on Multilink Bundles and Constituent Links (continued)
Explanation
Constituent
Links
Multilink
Bundle Cos Component
Rewrite bits are copied fromthe packet into the
fragments automatically during fragmentation. Thus
what you configure on the multilink bundle is carried on
the fragments to the constituent links.
No Yes Rewrite rules
Virtual channel groups are identified through firewall
filter rules that are applied on packets only before the
multilink bundle. Thus you do not need to apply the
virtual channel group configuration to the constituent
links.
No Yes Virtual channel group
Determine What Causes Jitter and Latency on the Multilink Bundle
Problem To test jitter and latency on a J Series device, you send three streams of IP packets. All
packets havethesameIPprecedencesettings. After configuringLFI andCRTP, thelatency
increased even over a non congested link. Howcan you reduce jitter and latency?
Solution To reduce jitter and latency, do the following:
1. Make sure that you have configured a shaping rate on each constituent link.
2. Make sure that you have not configured a shaping rate on the link services interface.
3. Make sure that the configured shaping rate value is equal to the physical interface
bandwidth. SeeExample: DefiningandApplyingInterfaceShapingRates onpage432.
4. If shaping rates are configured correctly, and jitter still persists, contact the Juniper
Networks Technical Assistance Center (JTAC).
Determine If LFI and Load Balancing Are Working Correctly
Problem In this case, you have a single network that supports multiple services. The network
transmits data and delay-sensitive voice traffic. After configuring MLPPP and LFI, make
sure that voice packets are transmittedacross the network withvery little delay andjitter.
Howcan you findout if voice packets are being treatedas LFI packets andloadbalancing
is performed correctly?
Solution When LFI is enabled, data (non-LFI) packets are encapsulated with an MLPPP header
and fragmented to packets of a specified size. The delay-sensitive, voice (LFI) packets
are PPP-encapsulated and interleaved between data packet fragments. Queuing and
load balancing are performed differently for LFI and non-LFI packets.
To verify that LFI is performed correctly, determine that packets are fragmented and
encapsulated as configured. After you knowwhether a packet is treated as an LFI packet
or a non-LFI packet, you can confirmwhether the load balancing is performed correctly.
SolutionScenarioSuppose twoJ Series devices R0andR1 are connectedby amultilink
bundle lsq-0/0/0.0 that aggregates two serial links, se-1/0/0 and se-1/0/1. On R0 and
R1, MLPPP and LFI are enabled on the link services interface and the fragmentation
threshold is set to 128 bytes.
In this example, we used a packet generator to generate voice and data streams. You
can use the packet capture feature to capture and analyze the packets on the incoming
interface. See the Junos OS Administration Guide for Security Devices.
The following two data streams were sent on the multilink bundle:
100 data packets of 200 bytes (larger than the fragmentation threshold)
500 data packets of 60 bytes (smaller than the fragmentation threshold)
The following two voice streams were sent on the multilink bundle:
100 voice packets of 200 bytes fromsource port 100
300 voice packets of 200 bytes fromsource port 200
To confirmthat LFI and load balancing are performed correctly, first verify that the link
services interface is performing packet fragmentation as configured. Second, verify that
the interface is encapsulating packets as configured. Finally, use the results to verify load
balancing.
NOTE: Only the significant portions of command output are displayed and
described in this example. For more information, see Verifying the Link
Services Interface on page 433.
Step 1: Verifying Packet Fragmentation
Fromoperational mode, enter the showinterfaces lsq-0/0/0 command to check that
large packets are fragmented correctly.
user@R0#> showinterfaces lsq-0/0/0
Last flapped : 2006-08-01 10:45:13 PDT (2w0d 06:06 ago)
Logical interface lsq-0/0/0.0 (Index 69) (SNMP ifIndex 42)
Bandwidth: 16mbps
Bundle:
Fragments:
Input : 0 0 0 0
Output: 1100 0 118800 0
Packets:
Input : 0 0 0 0
Output: 1000 0 112000 0
...
Flags: None
MeaningThe output shows a summary of packets transiting the device on the multilink
bundle. Verify the following information on the multilink bundle:
The total number of transiting packets = 1000
The total number of transiting fragments=1100
The number of data packets that were fragmented =100
Thetotal number of packets sent (600+400) onthemultilinkbundlematchthenumber
of transiting packets (1000), indicating that no packets were dropped.
The number of transiting fragments exceeds the number of transiting packets by 100,
indicating that 100 large data packets were correctly fragmented.
CorrectiveActionIf thepacketsarenot fragmentedcorrectly, checkyour fragmentation
threshold configuration. Packets smaller than the specified fragmentation threshold are
not fragmented. See Example: Configuring Link Fragmentation and Interleaving on
page 425.
Step 2: Verifying Packet Encapsulation
To find out whether a packet is treated as an LFI or non-LFI packet, determine its
encapsulation type. LFI packets are PPP encapsulated, and non-LFI packets are
encapsulatedwithbothPPPandMLPPP. PPPandMLPPPencapsulations havedifferent
overheads resultingindifferent-sizedpackets. Youcancomparepacket sizes todetermine
the encapsulation type.
A small unfragmented data packet contains a PPP header and a single MLPPP header.
In a large fragmented data packet, the first fragment contains a PPP header and an
MLPPP header, but the consecutive fragments contain only an MLPPP header.
PPP and MLPPP encapsulations add the following number of bytes to a packet:
PPP encapsulation adds 7 bytes:
4bytes of header+2bytes of framecheck sequence(FCS)+1 bytethat is idleor contains
a flag
MLPPP encapsulation adds between 6 and 8 bytes:
4 bytes of PPP header+2 to 4 bytes of multilink header
Figure 32 on page 450 shows the overhead added to PPP and MLPPP headers.
Figure 32: PPP and MLPPP Headers
For CRTP packets, the encapsulation overhead and packet size are even smaller than
for anLFI packet. For moreinformation, seeExample: ConfiguringCompressedReal-Time
Transport Protocol on page 442.
Table 53 on page 450 shows the encapsulation overhead for a data packet and a voice
packet of 70 bytes each. After encapsulation, the size of the data packet is larger than
the size of the voice packet.
Table 53: PPP and MLPPP Encapsulation Overhead
Packet Size
after
Encapsulation Encapsulation Overhead
Initial
Packet Size Encapsulation Packet Type
77 bytes 4 + 2 + 1 = 7 bytes 70 bytes PPP Voice packet (LFI)
83 bytes 4 + 2 + 1 + 4 + 2 = 13 bytes 70 bytes MLPPP Data fragment (non-LFI)
with short sequence
85 bytes 4 + 2 + 1 + 4 + 4 = 15 bytes 70 bytes MLPPP Data fragment (non-LFI)
with long sequence
Fromoperational mode, enter the showinterfaces queue command to display the size
of transmitted packet on each queue. Divide the number of bytes transmitted by the
number of packets to obtain the size of the packets and determine the encapsulation
type.
Step 3: Verifying Load Balancing
Fromoperational mode, enter the showinterfaces queue command on the multilink
bundle and its constituent links to confirmwhether load balancing is performed
accordingly on the packets.
user@R0> showinterfaces queue lsq-0/0/0
Forwarding classes: 8 supported, 8 in use
Queue: 0, Forwarding classes: DATA
Queued:
Packets : 600 0 pps
Bytes : 44800 0 bps
Transmitted:
Packets : 600 0 pps
Bytes : 44800 0 bps
Tail-dropped packets : 0 0 pps
RED-dropped packets : 0 0 pps

Queue: 1, Forwarding classes: expedited-forwarding
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps

Queue: 2, Forwarding classes: VOICE
Queued:
Packets : 400 0 pps
Bytes : 61344 0 bps
Transmitted:
Packets : 400 0 pps
Bytes : 61344 0 bps

Queue: 3, Forwarding classes: NC
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps

user@R0> showinterfaces queue se-1/0/0
Physical interface: se-1/0/0, Enabled, Physical link is Up
Queued:
Packets : 350 0 pps
Bytes : 24350 0 bps
Transmitted:
Packets : 350 0 pps
Bytes : 24350 0 bps
...
Queued:
Packets : 0 0 pps
Bytes : 0 0 bps

Queued:
Packets : 100 0 pps
Bytes : 15272 0 bps
Transmitted:
Packets : 100 0 pps
Bytes : 15272 0 bps

Queued:
Packets : 19 0 pps
Bytes : 247 0 bps
Transmitted:
Packets : 19 0 pps
Bytes : 247 0 bps

user@R0> showinterfaces queue se-1/0/1
Physical interface: se-1/0/1, Enabled, Physical link is Up
Queued:
Packets : 350 0 pps
Bytes : 24350 0 bps
Transmitted:
Packets : 350 0 pps
Bytes : 24350 0 bps

Queued:
Packets : 0 0 pps
Bytes : 0 0 bps

Queued:
Packets : 300 0 pps
Bytes : 45672 0 bps
Transmitted:
Packets : 300 0 pps
Bytes : 45672 0 bps

Queued:
Packets : 18 0 pps
Bytes : 234 0 bps
Transmitted:
Packets : 18 0 pps
Bytes : 234 0 bps
MeaningTheoutput fromthesecommands shows thepackets transmittedandqueued
oneachqueueof thelink services interfaceandits constituent links. Table54onpage452
shows asummary of these values. (Because the number of transmittedpackets equaled
thenumber of queuedpackets onall thelinks, this tableshows only thequeuedpackets.)
Table 54: Number of Packets Transmitted on a Queue
Explanation
Constituent Link
se-1/0/1
Constituent Link
se-1/0/0
Bundle
lsq-0/0/0.0 Packets Queued
Thetotal number of packetstransiting
theconstituent links (350+350=700)
exceeded the number of packets
queued(600) onthemultilinkbundle.
350 350 600 Packets on Q0
Thetotal number of packetstransiting
the constituent links equaled the
number of packets on the bundle.
Table 54: Number of Packets Transmitted on a Queue (continued)
Explanation
Constituent Link
se-1/0/1
Constituent Link
se-1/0/0
Bundle
lsq-0/0/0.0 Packets Queued
The packets transiting Q3 of the
constituent links are for keepalive
messages exchanged between
constituent links. Thus no packets
were counted on Q3 of the bundle.
On the multilink bundle, verify the following:
The number of packets queued matches the number transmitted. If the numbers
match, no packets were dropped. If more packets were queuedthan were transmitted,
packets were dropped because the buffer was too small. The buffer size on the
constituent links controls congestion at the output stage. To correct this problem,
increase the buffer size on the constituent links. For more information, see Example:
Defining and Applying Scheduler Maps on page 429.
The number of packets transiting Q0 (600) matches the number of large and small
data packets received (100+500) on the multilink bundle. If the numbers match, all
data packets correctly transited Q0.
Thenumber of packetstransitingQ2onthemultilinkbundle(400) matchesthenumber
of voice packets received on the multilink bundle. If the numbers match, all voice LFI
packets correctly transited Q2.
On the constituent links, verify the following:
The total number of packets transiting Q0 (350+350) matches the number of data
packets and data fragments (500+200). If the numbers match, all the data packets
after fragmentation correctly transited Q0 of the constituent links.
Packets transited both constituent links, indicating that load balancing was correctly
performed on non-LFI packets.
The total number of packets transiting Q2 (300+100) on constituent links matches
the number of voice packets received (400) on the multilink bundle. If the numbers
match, all voice LFI packets correctly transited Q2.
LFI packets fromsource port 100 transited se-1/0/0, and LFI packets fromsource port
200 transited se-1/0/1. Thus all LFI (Q2) packets were hashed based on the source
port and correctly transited both constituent links.
Corrective ActionIf the packets transited only one link, take the following steps to
resolve the problem:
1. Determine whether the physical link is up (operational) or down (unavailable). An
unavailablelink indicates aproblemwiththePIM, interfaceport, or physical connection
(link-layer errors). If the link is operational, move to the next step.
2. Verify that the classifiers are correctly defined for non-LFI packets. Make sure that
non-LFI packets are not configured to be queued to Q2. All packets queued to Q2 are
treated as LFI packets.
3. Verify that at least one of the following values is different in the LFI packets: source
address, destination address, IPprotocol, source port, or destination port. If the same
values are configured for all LFI packets, the packets are all hashed to the same flow
and transit the same link.
Determine Why Packets Are Dropped on a PVC Between a J Series Device and Another Vendor
Problem You are configuring a permanent virtual circuit (PVC) between T1, E1, T3, or E3 interfaces
on my Juniper Networks device and another vendor's device, and packets are being
dropped and ping fails.
Solution If the other vendor's device does not have the same FRF.12 support as the J Series device
or supports FRF.12 in a different way, the J Series interface on the PVC might discard a
fragmented packet containing FRF.12 headers and count it as a "Policed Discard." As a
workaround for this problem, configure multilink bundles on both peers, and configure
fragmentation thresholds on the multilink bundles.
CHAPTER 19
Special Interfaces
Understanding Management Interfaces on page 455
Understanding the Discard Interface on page 456
Understanding the Loopback Interface on page 457
Understanding Management Interfaces
Management interfaces are the primary interfaces for accessing the device remotely.
Typically, a management interface is not connected to the in-band network, but is
connected instead to the device's internal network. Through a management interface
you can access the device over the network using utilities such as ssh and telnet and
configure it fromanywhere, regardless of its physical location. SNMP can use the
management interface to gather statistics fromthe device.
Management interfaces vary based on device type:
The J Series devices include four built-in Gigabit Ethernet interfaces located on the
front panel of the router chassis named ge-0/0/0, ge-0/0/1, ge-0/0/2, and ge-0/0/3
fromleft toright. Thesearenot physically dedicatedmanagement interfaces, although
the factory configuration for these routers automatically enables the J-Web user
interface on these interfaces. You can use themto pass traffic or you can segregate
one and place it in the management zone to be used as a management interface. To
use a built-in interface as a management Ethernet interface, configure it with a valid
IP address. See the J Series Services Routers Hardware Guide.
The SRX5600 and SRX5800 devices include a 10/100-Mbps Ethernet port on the
RoutingEngine(RE). This port, whichis labeledETHERNET, is adedicatedout-of-band
management interface for the device. Junos OS automatically creates the devices
management interface fxp0. To use fxp0 as a management port, you must configure
its logical port fxp0.0 with a valid IP address. While you can use fxp0 to connect to a
management network, you cannot place it into the management zone. See the SRX
Series Services Gateways for the Branch Physical Interface Modules Hardware Guide.
NOTE: On the SRX5600 and SRX5800 devices, you must first connect to
thedevicethroughtheserial consoleport beforeassigningauniqueIPaddress
to the management interface.
As a security feature, users cannot log in as root through a management interface. To
access the device as root, you must use the console port.
In a J Series chassis cluster configuration, configurable management interfaces are
created frombuilt-in interfaces on the connected J Series chassis. The fxp0 interface is
the management port, and fxp1 is used as the control link interface in a chassis cluster.
See Node Interfaces on Active J Series Chassis Clusters in the Junos OS Security
In an SRX Series device, the fxp0 management interface is a dedicated port located on
theRoutingEngine. InanSRXSeries chassis cluster configuration, thecontrol linkinterface
must be port 0 on an SPC. For each node in the chassis cluster, you must configure the
SPC that is used for the control link interface. See Node Interfaces on Active SRX Series
Chassis Clusters in the Junos OS Security Configuration Guide.
Related
Documentation
Understanding the Discard Interface
The discard(dsc) interface is not a physical interface, but a virtual interface that discards
packets. You can configure one discard interface. This interface allows you to identify
the ingress (inbound) point of a denial-of-service (DoS) attack. When your network is
under attack, the target host IP address is identified, and the local policy forwards
attacking packets to the discard interface. Traffic routed out the discard interface is
silently discarded.
Related
Documentation
Discard Interfaces Overviewin the Junos OS Network Interfaces Configuration Guide
Example: Discard Interface in the Junos OS Network Interfaces Configuration Guide
Forwarding Packets to the Discard Interface in the Junos OS Network Interfaces
Configuration Guide
showinterfaces (Discard) in the Junos OS Interfaces Command Reference
Understanding the Loopback Interface
The loopback address (lo0) has several uses, depending on the particular Junos feature
being configured. It can performthe following functions:
Device identificationThe loopback interface is used to identify the device. While any
interfaceaddress canbeusedtodetermineif thedeviceis online, theloopback address
is the preferred method. Whereas interfaces might be removed or addresses changed
based on network topology changes, the loopback address never changes.
When you ping an individual interface address, the results do not always indicate the
health of the device. For example, a subnet mismatch in the configuration of two
endpoints on a point-to-point link makes the link appear to be inoperable. Pinging the
interface to determine whether the device is online provides a misleading result. An
interface might be unavailable because of a problemunrelated to the device's
configuration or operation. See the Junos OS Administration Guide for Security Devices.
Routing informationThe loopback address is used by protocols such as OSPF to
determine protocol-specific properties for the device or network. Further, some
commands such as ping mpls require a loopback address to function correctly. See
Verifying an OSPF Configuration in the Junos OS Routing Protocols and Policies
Configuration Guide for Security Devices and Example: Configuring LDP-Signaled LSPs
in the Junos OS MPLS Configuration Guide for Security Devices.
Packet filteringStateless firewall filters can be applied to the loopback address to
filter packets originatingfrom, or destinedfor, theRoutingEngine. SeeStateless Firewall
Filter ConfigurationOverviewintheJunos OSRoutingProtocols andPolicies Configuration
Guide for Security Devices.
The Internet Protocol (IP) specifies a loopback network with the (IPv4) address
127.0.0.0/8. Most IP implementations support a loopback interface (lo0) to represent
theloopback facility. Any trafficthat acomputer programsends ontheloopback network
is addressedtothesamecomputer. Themost commonly usedIPaddress ontheloopback
network is 127.0.0.1 for IPv4 and ::1 for IPv6. The standard domain name for the address
is localhost.
Thedevicealsoincludes aninternal loopbackaddress (lo0.16384). Theinternal loopback
address is a particular instance of the loopback address with the logical unit number
16384. Junos OS creates the loopback interface for the internal routing instance. This
interface prevents any filter on lo0.0 fromdisrupting internal traffic.
Related
Documentation
Configuring the Loopback Interface in the Junos OS Network Interfaces Configuration
Guide
Chapter 19: Special Interfaces
PART 7
Encapsulation
Interface Encapsulation Overviewon page 461
Point-to-Point Protocol over Ethernet on page 469
CHAPTER 20
Interface Encapsulation Overview
Understanding Physical Encapsulation on an Interface on page 461
Understanding Frame Relay Encapsulation on an Interface on page 462
Understanding Point-to-Point Protocol on page 464
Understanding High-Level Data Link Control on page 466
Understanding Physical Encapsulation on an Interface
Encapsulation is the process by which a lower level protocol accepts a message froma
higher level protocol and places it in the data portion of the lower level frame. As a result,
datagrams transmitted through a physical network have a sequence of headers: the first
header for the physical network (or Data Link Layer) protocol, the second header for the
NetworkLayer protocol (IP, for example), thethirdheader for theTransport Layer protocol,
and so on.
The following encapsulation protocols are supported on physical interfaces:
Frame Relay Encapsulation. See Understanding Frame Relay Encapsulation on an
Point-to-Point Protocol. See Understanding Point-to-Point Protocol on page 464.
Point-to-Point Protocol over Ethernet. See Understanding Point-to-Point Protocol
over Ethernet on page 469.
High-Level Data Link Control. See Understanding High-Level Data Link Control on
page 466.
Related
Documentation
Understanding Frame Relay Encapsulation on an Interface on page 462
Understanding High-Level Data Link Control on page 466
Interface Encapsulations Overviewin the Junos OS Network Interfaces Configuration
Guide
Configuring Interface Encapsulation on Physical Interfaces in the Junos OS Network
Understanding Frame Relay Encapsulation on an Interface
The Frame Relay packet-switching protocol operates at the Physical Layer and Data
Link Layer in a network to optimize packet transmissions by creating virtual circuits
between hosts. Figure 33 on page 462 shows a typical Frame Relay network.
Figure 33: Frame Relay Network
Figure 33 on page 462 shows multiple paths fromHost A to Host B. In a typical routed
network, traffic is sent fromdevice to device with each device making routing decisions
based on its own routing table. In a packet-switched network, the paths are predefined.
Devices switch a packet through the network according to predetermined next-hops
established when the virtual circuit is set up.
Virtual Circuits on page 462
Switched and Permanent Virtual Circuits on page 463
Data-Link Connection Identifiers on page 463
Congestion Control and Discard Eligibility on page 463
Virtual Circuits
Avirtual circuit is abidirectional pathbetweentwohosts inanetwork. FrameRelay virtual
circuits are logical connections between two hosts that are established either by a call
setup mechanismor by an explicit configuration.
A virtual circuit created through a call setup mechanismis known as a switched virtual
circuit (SVC). A virtual circuit created through an explicit configuration is called a
permanent virtual circuit (PVC).
Switched and Permanent Virtual Circuits
Before data can be transmitted across an SVC, a signaling protocol like ISDN must set
up a call by the exchange of setup messages across the network. When a connection is
established, data is transmitted across the SVC. After data transmission, the circuit is
torn down and the connection is lost. For additional traffic to pass between the same
two hosts, a subsequent SVC must be established, maintained, and terminated.
Because PVCs are explicitly configured, they do not require the setup and teardown of
SVCs. Data can be switched across the PVC whenever a host is ready to transmit. SVCs
are useful in networks where data transmission is sporadic and a permanent circuit is
not needed.
Data-Link Connection Identifiers
An established virtual circuit is identified by a data-link connection identifier (DLCI). The
DLCI is avaluefrom16through1022. (Values 1 through15arereserved.) TheDLCI uniquely
identifies a virtual circuit locally so that devices can switch packets to the appropriate
next-hopaddress inthe circuit. Multiple paths that pass throughthe same transit devices
have different DLCIs and associated next-hop addresses.
Congestion Control and Discard Eligibility
Frame Relay uses the following types of congestion notification to control traffic within
a Frame Relay network. Both are controlled by a single bit in the Frame Relay header.
Forward explicit congestion notification (FECN)
Backward explicit congestion notification (BECN)
Traffic congestion is typically defined in the buffer queues on a device. When the queues
reach a predefined level of saturation, traffic is determined to be congested. When traffic
congestion occurs in a virtual circuit, the device experiencing congestion sets the
congestion bits in the Frame Relay header to 1. As a result, transmitted traffic has the
FECN bit set to 1, and return traffic on the same virtual circuit has the BECN bit set to 1.
When the FECN and BECN bits are set to 1, they provide a congestion notification to the
source anddestination devices. The devices can respondin either of two ways: to control
traffic on the circuit by sending it through other routes, or to reduce the load on the circuit
by discarding packets.
If devices discard packets as a means of congestion (flow) control, Frame Relay uses
the discard eligibility (DE) bit to give preference to some packets in discard decisions. A
DE value of 1 indicates that the frame is of lower importance than other frames and more
likely tobedroppedduringcongestion. Critical data(suchas signalingprotocol messages)
without the DE bit set is less likely to be dropped.
Related
Documentation
Configuring Frame Relay Interface Encapsulation in the Junos OS Network Interfaces
Configuration Guide
Chapter 20: Interface Encapsulation Overview
Understanding Point-to-Point Protocol
The Point-to-Point Protocol (PPP) is an encapsulation protocol for transporting IPtraffic
across point-to-point links. PPP is made up of three primary components:
Link Control Protocol (LCP)Establishes working connections between two points.
Authentication protocolEnables secure connections between two points.
Network control protocol (NCP)Initializes the PPP protocol stack to handle multiple
Network Layer protocols, such as IPv4, IPv6, and Connectionless Network Protocol
(CLNP).
Link Control Protocol on page 464
PPP Authentication on page 465
Network Control Protocols on page 465
Magic Numbers on page 466
CSU/DSU Devices on page 466
Link Control Protocol
LCPis responsible for establishing, maintaining, andtearing down a connection between
twoendpoints. LCPalsotests thelink anddetermines whether it is active. LCPestablishes
a point-to-point connection as follows:
1. LCP must first detect a clocking signal on each endpoint. However, because the
clocking signal can be generated by a network clock and shared with devices on the
network, the presence of a clocking signal is only a preliminary indication that the link
might be functioning.
2. When a clocking signal is detected, a PPP host begins transmitting PPP
Configure-Request packets.
3. If the remote endpoint on the point-to-point link receives the Configure-Request
packet, it transmits aConfigure-Acknowledgement packet tothesourceof therequest.
4. After receiving the acknowledgement, the initiating endpoint identifies the link as
established. At the same time, the remote endpoint sends its own request packets
andprocessestheacknowledgement packets. Inafunctioningnetwork, bothendpoints
treat the connection as established.
During connection establishment, LCP also negotiates connection parameters such as
FCS and HDLC framing. By default, PPP uses a 16-bit FCS, but you can configure PPP to
use either a 32-bit FCS or a 0-bit FCS (no FCS). Alternatively, you can enable HDLC
encapsulation across the PPP connection.
After aconnectionis established, PPPhosts generateEcho-Request andEcho-Response
packets to maintain a PPP link.
PPP Authentication
PPPs authentication layer uses a protocol to help ensure that the endpoint of a PPPlink
is a valid device. Authentication protocols include the Password Authentication Protocol
(PAP), the Extensible Authentication Protocol (EAP), and the Challenge Handshake
Authentication Protocol (CHAP). CHAP is the most commonly used.
NOTE: EAP is not currently supported on J Series devices.
CHAP ensures secure connections across PPP links. After a PPP link is established by
LCP, the PPP hosts at either end of the link initiate a three-way CHAP handshake. Two
separate CHAP handshakes are required before both sides identify the PPP link as
established.
CHAP configuration requires each endpoint on a PPP link to use a shared secret
(password) to authenticate challenges. The shared secret is never transmitted over the
wire. Instead, the hosts on the PPP connection exchange information that enables both
to determine that they share the same secret. Challenges consist of a hash function
calculated fromthe secret, a numeric identifier, and a randomly chosen challenge value
that changes with each challenge. If the response value matches the challenge value,
authentication is successful. Because the secret is never transmitted and is required to
calculate the challenge response, CHAP is considered very secure.
PAP authentication protocol uses a simple two-way handshake to establish identity.
PAPis usedafter thelinkestablishment phase(LCPup), duringtheauthenticationphase.
Junos OS can support PAP in one direction (egress or ingress), and CHAP in the other.
Network Control Protocols
After authentication is completed, the PPP connection is fully established. At this point,
any higher level protocols (for example, IPprotocols) can initialize andperformtheir own
negotiations and authentication.
PPP NCPs include support for the following protocols. IPCP and IPv6CP are the most
widely used on J Series devices.
ATCPAppleTalk Control Protocol
BCPBridging Control Protocol
BVCPBanyan Vines Control Protocol
DNCPDECnet Phase IV Control Protocol
IPCPIP Control Protocol
IPv6CPIPv6 Control Protocol
IPXCPNovell IPX Control Protocol
LECPLAN Extension Control Protocol
NBFCPNetBIOS Frames Control Protocol
OSINLCPOSI Network Layer Control Protocol (includes IS-IS, ES-IS, CLNP, andIDRP)
SDTPSerial Data Transport Protocol
SNACPSystems Network Architecture (SNA) Control Protocol
XNSCPXerox Network Systems (XNS) Internet DatagramProtocol (IDP) Control
Protocol
Magic Numbers
HostsrunningPPPcancreatemagic numbersfor diagnosingthehealthof aconnection.
APPPhost generates arandom32-bit number andsends it totheremoteendpoint during
LCP negotiation and echo exchanges.
In a typical network, each host's magic number is different. A magic number mismatch
inanLCPmessageinforms ahost that theconnectionis not inloopback modeandtraffic
is being exchanged bidirectionally. If the magic number in the LCP message is the same
as the configured magic number, the host determines that the connection is in loopback
mode, with traffic looped back to the transmitting host.
Looping traffic back to the originating host is a valuable way to diagnose network health
between the host and the loopback location. To enable loopback testing,
telecommunications equipment typically supports channel service unit/dataservice unit
(CSU/DSU) devices.
CSU/DSUDevices
Achannel serviceunit (CSU) connects aterminal toadigital line. Adataserviceunit (DSU)
performs protective and diagnostic functions for a telecommunications line. Typically,
the two devices are packaged as a single unit. A CSU/DSU device is required for both
ends of a T1 or T3 connection, and the units at both ends must be set to the same
communications standard.
A CSU/DSUdevice enables frames sent along a link to be looped back to the originating
host. Receipt of the transmitted frames indicates that the link is functioning correctly up
tothepoint of loopback. By configuringCSU/DSUdevices toloopback at different points
in a connection, network operators can diagnose and troubleshoot individual segments
in a circuit.
Related
Documentation
ppp-options in the Junos OS Network Interfaces Configuration Guide
Understanding High-Level Data Link Control
High-Level DataLink Control (HDLC) is abit-oriented, switchedandnonswitchedlink-layer
protocol. HDLC is widely used because it supports half-duplex and full-duplex
connections, point-to-point and point-to-multipoint networks, and switched and
nonswitched channels.
HDLC Stations on page 467
HDLC Operational Modes on page 467
HDLC Stations
Nodes within a network running HDLC are called stations. HDLC supports three types of
stations for data link control:
Primary stationsResponsible for controlling the secondary and combined other
stations on the link. Depending on the HDLC mode, the primary station is responsible
for issuing acknowledgement packets to allowdata transmission fromsecondary
stations.
Secondary stationsControlled by the primary station. Under normal circumstances,
secondary stations cannot control data transmission across the link with the primary
station, are active only when requested by the primary station, and can respond to the
primary station only (not to other secondary stations). All secondary station frames
are response frames.
Combined stationsA combination of primary and secondary stations. On an HDLC
link, all combined stations can send and receive commands and responses without
any permission fromany other stations on the link and cannot be controlled by any
other station.
HDLC Operational Modes
HDLC runs in three separate modes:
Normal Response Mode (NRM)The primary station on the HDLC link initiates all
information transfers with secondary stations. A secondary station on the link can
transmit a response of one or more information frames only when it receives explicit
permissionfromtheprimary station. Whenthelast frameis transmitted, thesecondary
station must wait for explicit permission before it can transmit more frames.
NRMis usedmost widely for point-to-multipoint links, inwhichasingle primary station
controls many secondary stations.
Asynchronous ResponseMode(ARM)Thesecondary stationcantransmit either data
or control traffic at any time, without explicit permission fromthe primary station. The
primary stationis responsiblefor error recovery andlink setup, but thesecondary station
can transmit information at any time.
ARMis usedmost commonly withpoint-to-point links, becauseit reduces theoverhead
on the link by eliminating the need for control packets.
Asynchronous Balance Mode (ABM)All stations are combined stations. Because no
other station can control a combined station, all stations can transmit information
without explicit permission fromany other station. ABMis not a widely used HDLC
mode.
Related
Documentation
Configuring Interface Encapsulation on Physical Interfaces in the Junos OS Network
CHAPTER 21
Point-to-Point Protocol over Ethernet
PPPoE Interfaces on page 471
PPPoE Encapsulation on an Ethernet Interface on page 476
PPPoEEncapsulationonanATM-over-ADSLor ATM-over-SHDSLInterfaceonpage478
CHAP Authentication on a PPPoE Interface on page 481
PPPoE-Based Radio-to-Router Protocol on page 483
Understanding Point-to-Point Protocol over Ethernet
Point-to-Point Protocol over Ethernet (PPPoE) combines PPP, which typically runs over
broadbandconnections, withtheEthernet link-layer protocol that allows users toconnect
to a network of hosts over a bridge or access concentrator. PPPoE enables service
providers tomaintainaccess control throughPPPconnections andalsomanagemultiple
hosts at a remote site.
PPPoE connects multiple hosts on an Ethernet LAN to a remote site through a single
customer premises equipment (CPE) devicea Juniper Networks device. Hosts share a
common digital subscriber line (DSL), a cable modem, or a wireless connection to the
Internet.
To use PPPoE, you must initiate a PPPoE session, encapsulate Point-to-Point Protocol
(PPP) packets over Ethernet, and configure the device as a PPPoE client. To provide a
PPPoE connection, each PPP session must learn the Ethernet address of the remote
peer and establish a unique session identifier during the PPPoE discovery and session
stages.
NOTE: Juniper Networks devices with asymmetric digital subscriber line
(ADSL) or symmetric high-speed DSL (SHDSL) interfaces can use PPPoE
over Asynchronous Transfer Mode (ATM) to connect through DSL lines only,
not for direct ATMconnections.
PPPoE has two stages, the discovery stage and the PPPoE session stage. In the discovery
stage, the client discovers the access concentrator by identifying the Ethernet media
access control (MAC) address of the access concentrator and establishing a PPPoE
session ID. In the session stage, the client and the access concentrator build a
point-to-point connection over Ethernet, based on the information collected in the
discovery stage.
PPPoE Discovery Stage on page 470
PPPoE Session Stage on page 471
PPPoE Discovery Stage
To initiate a PPPoE session, a host must first identify the Ethernet MAC address of the
remotepeer andestablishauniquePPPoEsessionIDfor thesession. Learningtheremote
Ethernet MAC address is called PPPoE discovery.
During the PPPoE discovery process, the host does not discover a remote endpoint on
the Ethernet network. Instead, the host discovers the access concentrator through which
all PPPoEsessions are established. Discovery is aclient/server relationship, withthe host
(a device running the Junos OS) acting as the client and the access concentrator acting
as the server. Because the network might have more than one access concentrator, the
discovery stage allows the client to communicate with all of themand select one.
NOTE: A device cannot receive PPPoE packets fromtwo different access
concentrators on the same physical interface.
The PPPoE discovery stage consists of the following steps:
1. PPPoEActiveDiscovery Initiation(PADI)Theclient initiates asessionby broadcasting
a PADI packet to the LAN to request a service.
2. PPPoE Active Discovery Offer (PADO)Any access concentrator that can provide
the service requested by the client in the PADI packet replies with a PADOpacket that
contains its own name, the unicast address of the client, and the service requested.
An access concentrator can also use the PADOpacket to offer other services to the
client.
3. PPPoE Active Discovery Request (PADR)Fromthe PADOs it receives, the client
selects one access concentrator based on its name or the services offered and sends
it a PADR packet to indicate the service or services needed.
4. PPPoE Active Discovery Session-Confirmation (PADS)When the selected access
concentrator receives the PADR packet, it accepts or rejects the PPPoE session:
To accept the session, the access concentrator sends the client a PADS packet
with a unique session IDfor a PPPoE session and a service name that identifies the
service under which it accepts the session.
To reject the session, the access concentrator sends the client a PADS packet with
a service name error and resets the session ID to zero.
PPPoE Session Stage
The PPPoE session stage starts after the PPPoE discovery stage is over. The access
concentrator can start the PPPoE session after it sends a PADS packet to the client, or
the client can start the PPPoE session after it receives a PADS packet fromthe access
concentrator. Adevice supports multiple PPPoE sessions on each interface, but no more
than 256 PPPoE sessions per device.
Each PPPoE session is uniquely identified by the Ethernet address of the peer and the
session ID. After the PPPoE session is established, data is sent as in any other PPP
encapsulation. The PPPoE information is encapsulated within an Ethernet frame and is
sent toaunicast address. Magicnumbers, echorequests, andall other PPPtrafficbehave
exactly as in normal PPP sessions. In this stage, both the client and the server must
allocate resources for the PPPoE logical interface.
After a session is established, the client or the access concentrator can send a PPPoE
ActiveDiscovery Termination(PADT) packet anytime toterminate the session. The PADT
packet contains the destination address of the peer and the session ID of the session to
be terminated. After this packet is sent, the session is closed to PPPoE traffic.
Related
Documentation
Understanding PPPoE Interfaces on page 471
Understanding PPPoE Ethernet Interfaces on page 476
Understanding PPPoE ATM-over-ADSL and ATM-over-SHDSL Interfaces on page 478
Understanding CHAP Authentication on a PPPoE Interface on page 481
Understanding the PPPoE-Based Radio-to-Router Protocol on page 483
PPPoE Interfaces
Example: Configuring PPPoE Interfaces on page 472
Understanding PPPoE Interfaces
The devices Point-to-Point Protocol over Ethernet (PPPoE) interface to the access
concentrator can be a Fast Ethernet interface, a Gigabit Ethernet interface, an
ATM-over-ADSL interface, or an ATM-over-SHDSL interface. The PPPoE configuration
is the same for all interfaces. The only difference is the encapsulation for the underlying
interface to the access concentrator:
If the interface is Ethernet, use a PPPoE encapsulation.
If the interface is ATM-over-ADSL or ATM-over-SHDSL, use a PPPoE over ATM
encapsulation.
Chapter 21: Point-to-Point Protocol over Ethernet
To configure a PPPoE interface, you create an interface with a logical interface unit 0,
then specify a logical Ethernet or ATMinterface as the underlying interface for the PPPoE
session. You then specify other PPPoE options, including the access concentrator and
PPPoE session parameters.
Related
Documentation
Example: Configuring PPPoE Interfaces on page 472
Example: Configuring PPPoE Interfaces
This example shows howto configure a PPPoE interface.
Overviewon page 472
Requirements
Before you begin, configure an Ethernet interface. See Example: Creating an Ethernet
Overview
In this example, you create the PPPoE interface pp0.0 and specify the logical Ethernet
interface ge-0/0/1.0 as the underlying interface. You also set the access concentrator,
set the PPPoE session parameters, and set the MTU of the IPv4 family to 1492.
Configuration
CLI Quick
Configuration
To quickly configure a PPPoE interface, copy the following commands and paste them
into the CLI:
[edit]
set interfaces pp0unit 0pppoe-options underlying-interface ge-0/0/1.0
access-concentrator ispl.comauto-reconnect 100idle-timeout 100client service-name
video@ispl.com
set interfaces pp0unit 0family inet mtu 1492 negotiate-address
Step-by-Step
Procedure
Mode.
To configure a PPPoE interface:
1. Create a PPPoE interface.
[edit]
user@host# edit interfaces pp0unit 0
2. Configure PPPoE options.
[edit interfaces pp0 unit 0]
user@host#set pppoe-optionsunderlying-interfacege-0/0/1.0access-concentrator
ispl.comauto-reconnect 100idle-timeout 100client service-namevideo@ispl.com
3. Configure the MTU.
user@host# set family inet mtu 1492
4. Configure the PPPoE interface address.
user@host# set family inet negotiate-address
[edit]
unit 0 {
pppoe-options {
underlying-interface ge-0/0/1.0;
idle-timeout 100;
access-concentrator ispl.com;
service-name "vide0@ispl.com";
auto-reconnect 100;
client;
}
family inet {
mtu 1492;
negotiate-address;
}
}
Verification
Verifying PPPoE Interfaces on page 473
Verifying PPPoE Sessions on page 474
Verifying the PPPoE Version on page 475
Verifying PPPoE Statistics on page 475
Verifying PPPoE Interfaces
Purpose Verify that the PPPoE device interfaces are configured properly.
Action Fromoperational mode, enter the showinterfaces pp0 command.
user@host> showinterfaces pp0
Link flags : None
Flags: Point-To-Point SNMP-Traps 16384 Encapsulation: PPPoE
PPPoE:
Session AC name: isp1.com, AC MAC address: 00:90:1a:40:f6:4c,
Service name: video@isp1.com, Configured AC name: isp1.com,
Auto-reconnect timeout: 60 seconds
Underlying interface: ge-5/0/0.0 (Index 71)
Input packets : 23
Output packets: 22
LCP state: Opened
NCP state: inet: Opened, inet6: Not-configured, iso: Not-configured, mpls:
Not-configured
CHAP state: Success
Meaning The output shows information about the physical and the logical interfaces. Verify the
The physical interface is enabled and the link is up.
The PPPoE session is running on the correct logical interface.
For state, the state is active (up).
For underlying interface, the physical interface on which the PPPoE session is running
is correct:
For an Ethernet connection, the underlying interface is Fast Ethernet or Gigabit
Ethernetfor example, ge-5/0/0.0.
For an ATM-over-ADSL or ATM-over-SHDSL connection, the underlying interface is
ATMfor example, at-2/0/0.0.
Verifying PPPoE Sessions
Purpose Verify that a PPPoE session is running properly on the logical interface.
Action Fromoperational mode, enter the showpppoe interfaces command.
user@host> showpppoe interfaces
pp0.0 Index 67
State: Session up, Session ID: 31,
Service name: video@isp1.com, Configured AC name: isp1.com,
Session AC name: belur, AC MAC address: 00:90:1a:40:f6:4e,
Auto-reconnect timeout: 1 seconds,
Underlying interface: ge-0/0/1.0 Index 69
Meaning Theoutput shows informationabout thePPPoEsessions. Verifythefollowinginformation:
The PPPoE session is running on the correct logical interface.
For state, the session is active (up).
For underlying interface, the physical interface on which the PPPoE session is running
is correct:
For an Ethernet connection, the underlying interface is Fast Ethernet or Gigabit
Ethernetfor example, ge-0/0/1.0.
For an ATM-over-ADSL or ATM-over-SHDSL connection, the underlying interface is
ATMfor example, at-2/0/0.0.
NOTE: To clear a PPPoE session on the pp0.0 interface, use the clear pppoe
sessions pp0.0command. To clear all sessions on the interface, use the clear
pppoe sessions command.
Verifying the PPPoE Version
Purpose Verify the version information of the PPPoE protocol configured on the device interfaces.
Action Fromoperational mode, enter the showpppoe version command.
user@host> showpppoe version
Point-to-Point Protocol Over Ethernet, version 1. rfc2516
PPPoE protocol = Enabled
Maximum Sessions = 256
PADI resend timeout = 2 seconds
PADR resend timeout = 16 seconds
Max resend timeout = 64 seconds
Max Configured AC timeout = 4 seconds
Meaning The output shows PPPoE protocol information. Verify the following information:
The correct version of the PPPoE protocol is configured on the interface.
For PPPoE protocol, the PPPoE protocol is enabled.
Verifying PPPoE Statistics
Purpose Verify the statistics information about PPPoE interfaces.
Action Fromoperational mode, enter the showpppoe statistics command.
user@host> showpppoe statistics
Active PPPoE sessions: 4
PacketType Sent Received
PADI 502 0
PADO 0 219
PADR 219 0
PADS 0 219
PADT 0 161
Service name error 0 0
AC system error 0 13
Generic error 0 0
Malformed packets 0 41
Unknown packets 0 0
Timeout
PADI 42
PADO 0
PADR 0
Meaning The output shows information about active sessions on PPPoE interfaces. Verify the
Total number of active PPPoE sessions running on the interfac
For packet type, the number of packets of each type sent and received during the
PPPoE session
Related
Documentation
Configuring PPPoE Interfaces in the Junos OS Network Interfaces Configuration Guide
showinterfaces (PPPoE) in the Junos Interfaces Command Reference.
showpppoe interfaces in the Junos Interfaces Command Reference
showpppoe version in the Junos Interfaces Command Reference.
showpppoe statistics in the Junos Interfaces Command Reference
PPPoE Encapsulation on an Ethernet Interface
Example: Configuring PPPoE Encapsulation on an Ethernet Interface on page 477
Understanding PPPoE Ethernet Interfaces
DuringaPoint-to-Point Protocol over Ethernet (PPPoE) session, thedeviceencapsulates
each PPP frame in an Ethernet frame and transports the frames over an Ethernet loop.
Figure 34 on page 477 shows a typical PPPoE session between a device and an access
concentrator on the Ethernet loop.
Figure 34: PPPoE Session on the Ethernet Loop
To configure PPPoE on an Ethernet interface, you configure encapsulation on the logical
interface.
Related
Documentation
Example: Configuring PPPoE Encapsulation on an Ethernet Interface on page 477
Example: Configuring PPPoE Encapsulation on an Ethernet Interface
This example shows howto configure PPPoE encapsulation on an Ethernet interface.
Overviewon page 477
Requirements
Before you begin:
Configure an Ethernet interface. See Example: Creating an Ethernet Interface on
page 37.
Configure a PPPoE encapsulation interface. See Example: Configuring PPPoE
Overview
In this example, you configure PPPoE encapsulation on the ge-0/0/1 interface.
Configuration
Step-by-Step
Procedure
To configure PPPoE encapsulation:
Enable PPPoE encapsulation on the interface. 1.
[edit]
user@host# set interfaces ge-0/0/1 unit 0encapsulation ppp-over-ether
2. Commit the configuration if you are done configuring the device.
[edit]
user@host# commit
Verification
To verify the configuration is working properly, enter the showinterfaces ge-0/0/1
command.
Related
Documentation
Configuring PPPoE in the Junos OS Network Interfaces Configuration Guide
PPPoE Encapsulation on an ATM-over-ADSL or ATM-over-SHDSL Interface
Example: ConfiguringPPPoEEncapsulationonanATM-over-ADSLInterfaceonpage479
Understanding PPPoE ATM-over-ADSL and ATM-over-SHDSL Interfaces
When an ATMnetwork is configured with a point-to-point connection, Point-to-Point
Protocol over Ethernet (PPPoE) can use ATMAdaptation Layer 5 (AAL5) for framing
PPPoE-encapsulatedpackets. The AAL5protocol provides avirtual connectionbetween
the client and the server within the same network. The device encapsulates each PPPoE
frame in an ATMframe and transports each frame over an asymmetric digital subscriber
line (ADSL) or symmetric high-speed DSL (SHDSL) loop and a digital subscriber line
access multiplexer (DSLAM). For example, Figure 35 on page 478shows a typical PPPoE
over ATMsession between a device and an access concentrator on an ADSL loop.
Figure 35: PPPoE Session on an ADSL Loop
For PPPoE on an ATM-over-ADSL or ATM-over-SHDSL interface, you must configure
encapsulation on both the physical and logical interfaces. To configure encapsulation
on an ATM-over-ADSL or ATM-over-SHDSL physical interface, use Ethernet over ATM
encapsulation. To configure encapsulation on an ATM-over-ADSL or ATM-over-SHDSL
logical interface, use PPPoE over AAL5 logical link control (LLC) encapsulation. LLC
encapsulation allows a single ATMvirtual connection to transport multiple protocols.
Related
Documentation
Example: ConfiguringPPPoEEncapsulationonanATM-over-ADSLInterfaceonpage479
Example: Configuring PPPoE Encapsulation on an ATM-over-ADSL Interface
This example shows howto configure a physical interface for Ethernet over ATM
encapsulation and howto create a logical interface for PPPoE over LLC encapsulation.
Overviewon page 479
Requirements
Before you begin:
Configurenetworkinterfaces. SeeExample: CreatinganEthernet Interface onpage37.
ConfigurePPPoEinterfaces. SeeExample: ConfiguringPPPoEInterfaces onpage472.
Configure PPPoE encapsulation on an Ethernet interface. See Example: Configuring
PPPoE Encapsulation on an Ethernet Interface on page 477.
Overview
In this example, you configure the physical interface at-2/0/0 for Ethernet over ATM
encapsulation. As part of the configuration, you set the virtual path identifier (VPI) on an
ATM-over-ADSL physical interface to 0, you set the ADSL operating mode to auto, and
you set the encapsulation type to ATM-over-ADSL. Then you create a logical interface
for PPPoE over LLC encapsulation.
Configuration
CLI Quick
Configuration
To quickly configure PPPoE encapsulation on an ATM-over-ADSL interface, copy the
[edit]
set interfaces at-2/0/0dsl-options operating-mode auto
set interfaces at-2/0/0unit 0encapsulation ppp-over-ether-over-atm-llc vci 0.120
Step-by-Step
Procedure
Mode.
To configure PPPoE encapsulation on an ATM-over-ADSL interface:
1. Configure the physical interface.
[edit]
2. Set the VPI on the interface.
[edit interfaces at-2/0/0]
3. Configure the ADSL operating mode.
user@host# set dsl-options operating-mode auto
4. Configure PPPoE encapsulation.
5. Create a logical interface and configure LLC encapsulation.
user@host# set unit 0encapsulation ppp-over-ether-over-atm-llc vci 0.120
at-2/0/0 command. If the output does not display the intended configuration, repeat
[edit]
user@host# showinterfaces at-2/0/0 {
encapsulation ethernet-over-atm;
atm-options {
vpi 0;
}
dsl-options {
}
unit 0 {
encapsulation ppp-over-ether-over-atm-llc;
vci 0.120;
}
}
Verification
Verifying a PPPoE Configuration for an ATM-over-ADSL or ATM-over-SHDSL
Interface on page 480
Verifying a PPPoE Configuration for an ATM-over-ADSL or ATM-over-SHDSL Interface
Purpose Verify the PPPoE configuration for an ATM-over-ADSL or ATM-over-SHDSL interface.
Related
Documentation
Configuring the ATM-over-ADSL Logical Interface Encapsulation Type in the Junos OS
CHAP Authentication on a PPPoE Interface
Understanding CHAP Authentication on a PPPoE Interface on page 481
Example: Configuring CHAP Authentication on a PPPoE Interface on page 481
Understanding CHAP Authentication on a PPPoE Interface
For interfaces with Point-to-Point Protocol over Ethernet (PPPoE) encapsulation, you
canconfigureinterfacestosupport thePPPChallengeHandshakeAuthenticationProtocol
(CHAP). When you enable CHAP on an interface, the interface can authenticate its peer
and be authenticated by its peer.
If you set the passive option to handle incoming CHAP packets only, the interface does
not challengeits peer. However, if theinterfaceis challenged, it responds tothechallenge.
If you do not set the passive option, the interface always challenges its peer.
You can configure Remote Authentication Dial-In User Service (RADIUS) authentication
of PPP sessions using CHAP. CHAP enables you to send RADIUS messages through a
routing instance to customer RADIUS servers in a private network.
Related
Documentation
Example: Configuring CHAP Authentication on a PPPoE Interface on page 481
Configuring RADIUSAuthentication in the Junos OS SystemBasics Configuration Guide
Example: Configuring CHAP Authentication on a PPPoE Interface
This example shows howto configure CHAP authentication on a PPPoE interface.
Overviewon page 482
Requirements
Before you begin:
Configure an Ethernet interface. See Example: Creating an Ethernet Interface on
page 37.
ConfigureaPPPoEinterface. SeeExample: ConfiguringPPPoEInterfaces onpage472.
Configure PPPoE encapsulation on an ATM-over-ADSL interface. See Example:
Configuring PPPoE Encapsulation on an ATM-over-ADSL Interface on page 479.
Overview
In this example, you configure a CHAP access profile, and then apply it to the PPPoE
interface pp0. You also configure the hostname to be used in CHAP challenge and
response packets, and set the passive option for handling incoming CHAP packets.
Configuration
CLI Quick
Configuration
To quickly configure CHAP authentication on a PPPoE interface, copy the following
[edit]
set access profile A-ppp-client client client1 chap-secret my-secret
set interfaces pp0unit 0ppp-options chap access-profile A-ppp-client local-name
A-ge-0/0/1.0passive
Step-by-Step
Procedure
Mode.
To configure CHAP on a PPPoE interface:
1. Configure a CHAP access profile.
[edit]
user@host# set access profile A-ppp-client client client1 chap-secret my-secret
2. Enable CHAP options on the interface.
[edit]
user@host# edit interfaces pp0unit 0ppp-options chap
3. Configure the CHAP access profile on the interface.
[edit interfaces pp0 unit 0 ppp-options chap]
user@host# set access-profile A-ppp-client
4. Configure a hostname for the CHAP challenge and response packets.
user@host# set local-name A-ge-0/0/1.0
5. Set the passive option to handle incoming CHAP packets only.
user@host# set passive
[edit]
pp0 {
unit 0 {
ppp-options {
chap {
local-name A-ge-0/0/1.0;
passive;
}
}
}
}
Verification
Verifying CHAP Authentication on page 483
Verifying CHAP Authentication
Purpose Verify that CHAP is enabled on the interface.
Related
Documentation
Configuring the PPP Challenge Handshake Authentication Protocol in the Junos OS
PPPoE-Based Radio-to-Router Protocol
Example: Configuring the PPPoE-Based Radio-to-Router Protocol on page 485
Understanding the PPPoE-Based Radio-to-Router Protocol
Point-to-Point Protocol over Ethernet (PPPoE)-based radio-to-router protocols include
messages that define howan external systemwill provide the device with timely
information about the quality of a links connection. They also include a flowcontrol
mechanismto indicate howmuch data the device can forward. The device can then use
the information provided in the PPPoE messages to dynamically adjust the interface
speed of PPP links.
For example, ahigh-bandnetworkingwaveform(HNW) radioprovides ground-to-ground
or ground-to-air communications withlikedevices. WhentheHNWpicks upasignal from
another device, it initiates a PPPoE session with a directly connected device (router).
The PPPoE session encapsulates the packets that are relayed over a PPP link between
the local and remote devices. The remote radio then forwards traffic to a remote device
using an independent PPPoE session. The two devices exchange Link Control Protocol
(LCP) and Internet Protocol Control Protocol (IPCP) messages to configure the link and
exchange OSPF messages to establish the network topology.
EachHNWradiomonitors thelinkevery 50milliseconds for changes inthelinkbandwidth,
quality, and utilization. If any changes are detected, the radios announce the newset of
metrics to the respective devices through a PPPoE Active Discovery Quality (PADQ)
message, whichis anonstandardextensiontothe PPPoEDiscovery Protocol (RFC2516).
Thedevicetransformsthesemetricsintoabandwidthvaluefor thePPPlinkandcompares
it to the value currently in use. When the device detects that the difference exceeds a
user-specified threshold, it adjusts the speed of the PPP link. OSPF is notified of the
change and announces any resulting routing topology changes to its neighbors.
The CLI statement, radio-router, indicates that metrics announcements received on the
interface will be processed by the device. When a PPPoE logical interface refers to this
as an underlying interface, the device then processes incoming PADQmessages and
uses information fromthe hosts messages to control the flowof traffic and manage the
speed of the link, resulting in a corresponding adjustment of the OSPF cost. If this option
is not specified, then PADQmessages received over the underlying interface are ignored.
The following options are available within the radio-router configuration statement:
bandwidth, resource, latency, and quality These statements provide control over the
weights used when transforming PADQlink metrics into an interface speed for the
virtual link:
bandwidthWeight of current (vs. maximum) data rate
resourceResource weight
latencyLatency weight
qualityRelative link quality weight
All four weights accept values from0through100. Thedefault valuefor all four weights
is 100.
creditThis statement supports the credit-based flowcontrol extensions described
in RFC 4938, The statement enables PPPoE peers to grant each other forwarding
credits. The grantee is then allowed to forward traffic to the peer only when it has a
sufficient number of credits todoso. Thesubsequent credit interval statement controls
howfrequently the device generates credit announcement messages. The interval
sub-statement, which controls the grant rate interval, accepts values from1 through
60 seconds.
thresholdThis statement specifies howmuch of a difference is required between the
calculated and the current interface speeds. The threshold value, expressed as a
percentage, defaults to 10.
Thefollowinghierarchyprovidesanother viewof theradio-router configurationstatements.
interfaces{
interface-name {
radio-router {
bandwidth;
credit {
interval;
}
latency;
quality;
resource;
threshold;
}
}
}
Related
Documentation
Example: Configuring the PPPoE-Based Radio-to-Router Protocol on page 485
Example: Configuring the PPPoE-Based Radio-to-Router Protocol
To configure the PPPoE-based radio-to-router protocol:
1. Enable the PPPoE-based radio-to-router protocol.
[edit ]
user@host# edit interfaces ge-3/0/3 unit 1 radio-router
2. Set the weights used when transforming PADQlink metrics into an interface speed
for the virtual link.
[edit interfaces ge-3/0/3 unit 1 radio-router]
user@host# set bandwidth 100resource 100latency 100quality 100
3. Set the required difference between the calculated and current interface speeds, as
a percentage.
[edit interfaces ge-3/0/3 unit 1 radio-router]
user@host# set threshold 10
4. Configure options on the logical interface.
user@host# set pppoe-options underlying-interface ge-3/0/3
user@host# set pppoe-options server test
user@host# set family inet unnumbered-address lo0.0destination 192.168.1.2
user@host# set family inet6 unnumbered-address lo0.0destination fec0:1:1:1::2
Related
Documentation
PART 8
Index
Index on page 489
Index
Symbols
#, comments in configuration statements.................xxiii
( ), in syntax descriptions..................................................xxiii
1-port four-wire mode, SHDSL See
ATM-over-SHDSL interfaces
2-port two-wire mode, SHDSL See
3G wireless modemSee wireless modem
< >, in syntax descriptions.................................................xxiii
[ ], in configuration statements......................................xxiii
{ }, in configuration statements......................................xxiii
| (pipe), in syntax descriptions........................................xxiii
A
AAL5 multiplex encapsulation
ATM-over-ADSL for PPP-over-ATM(PPPoA)
interfaces...................................................................248
ABM(Asynchronous Balance Mode), HDLC..............467
access concentrator
as a PPPoE server.......................................................469
account activation
CDMA cards...................................................................367
account activation, CDMA
IOTA....................................................................................371
manual............................................................................369
OTASP provisioning....................................................368
ACT LED....................................................................................197
TIM508...........................................................................200
TIM510.............................................................................203
TIM514.............................................................................206
TIM516..............................................................................210
TIM518..............................................................................215
TIM521...............................................................................216
activation priority
description.......................................................................221
range and default........................................................229
adapter, console port
TGM550...........................................................................192
addresses
physical, in Data Link Layer........................................28
ADSL interfaces See ATM-over-ADSL interfaces
ADSL ports See ATM-over-ADSL interfaces
ADSL2+ operating mode..................................................248
aggregated Ethernet
overview............................................................................45
aggregated Ethernet interfaces
configuring........................................................................45
verifying.......................................................................61, 63
aggregated virtual circuits (AVCs), with MLFR
FRF.15....................................................................................437
See also MLFR FRF.15; multilink bundles
ALM LED....................................................................................197
TIM508...........................................................................200
TIM510.............................................................................203
TIM514.............................................................................206
TIM516..............................................................................210
TIM518..............................................................................215
TIM521...............................................................................216
alternate mark inversion See AMI encoding
AMI (alternate mark inversion) encoding
overview..........................................................................100
analog media module See TIM514
analog telephone (LINE) ports
TGM550, pinouts.........................................................194
TIM508, possible configurations..........................200
TIM514, pinouts............................................................205
TIM514, possible configurations............................205
TIM516, possible configurations.............................210
analog trunk (TRUNK) ports
TGM550, pinouts.........................................................194
TIM508, possible configurations..........................200
TIM514, pinouts............................................................205
TIM514, possible configurations............................205
Annex A PIMs
ATM-over-ADSL interfaces.....................................248
See also ATM-over-ADSL interfaces
ATM-over-SHDSL interfaces...................................255
See also ATM-over-SHDSL interfaces
ATM-over-SHDSL modes.........................................255
G.SHDSL PIMs, setting annex type on.................255
operating modes (configuration editor).............248
Annex B PIMs
See also ATM-over-ADSL interfaces
ATM-over-SDSL interfaces......................................255
ATM-over-SHDSL modes.........................................255
G.SHDSL PIMs, setting annex type on.................255
ANSI DMT operating mode..............................................248
ANSI T1.413 Issue II operating mode.............................248
anycast IPv6 addresses.........................................................17
ARM (Asynchronous Response Mode), HDLC..........467
ASB LED....................................................................................197
asymmetric digital subscriber line (ADSL) See
ATM-over-ADSL interfaces
Asynchronous Balance Mode (ABM), HDLC..............467
asynchronous networks
data stream clocking....................................................25
explicit clocking signal transmission......................25
overview.............................................................................24
Asynchronous Response Mode (ARM), HDLC..........467
Asynchronous Transfer Mode (ATM) interfaces See
ATM-over-ADSL interfaces; ATM-over-SHDSL
interfaces
at-0/0/0 See ATM-over-ADSL interfaces;
ATMinterfaces See ATM-over-ADSL interfaces;
ATMNLPID encapsulation
ATMPPP over AAL5 LLC encapsulation
ATM-over-ADSL for PPP-over-ATM(PPPoA)
interfaces...................................................................248
ATMPVC encapsulation
ATMSNAP encapsulation
ATMVC multiplex encapsulation
ATM-over-ADSL interfaces..............................................248
adding..............................................................................248
ADSL overview...............................................................241
ADSL systems...............................................................242
ADSL2..............................................................................243
ADSL2+...........................................................................243
CHAP for PPPoA...........................................................261
description.....................................................................248
encapsulation types, logical (configuration
editor)..........................................................................248
encapsulation types, physical (configuration
editor)..........................................................................248
logical properties (configuration editor)............248
MTU default and maximum values........................26
physical properties.....................................................248
preparation....................................................................248
statistics................................................................254, 265
VCI ....................................................................................248
verifying..................................................................251, 263
verifying a PPPoA configuration..................254, 266
VPI ....................................................................................248
See also PPPoE; PPPoE over ATM-over-ADSL;
PPPoE over ATM-over-SHDSL
ATM-over-SHDSL interfaces............................................273
1-port four-wire mode................................................255
1-port four-wire mode, setting................................255
2-port two-wire mode, overview...........................255
2-port two-wire mode, setting...............................255
adding..............................................................................255
annex type, setting......................................................255
CHAP for PPPoA...........................................................261
description.....................................................................255
encapsulation types, physical (configuration
editor)..........................................................................255
logical properties (configuration editor)............255
overview...........................................................................273
preparation....................................................................255
SNEXT threshold.........................................................255
SNR margin....................................................................255
statistics...............................................................260, 269
status.....................................................................260, 268
verifying.................................................................258, 266
VPI ....................................................................................255
dying gasp........................................................260, 269
See also G.SHDSL PIMs
authentication
CHAP, for PPPoE interfaces.....................................481
auto operating mode..........................................................248
Avaya Communication Manager (CM)
CAC-BL requirement for WANs..............................222
description.....................................................................220
Avaya IG550 Integrated Gateway See Avaya VoIP
modules
Avaya Communication Manager (CM)...............220
Avaya manuals, list of.................................................219
description.......................................................................217
See also Avaya VoIP modules
dynamic CAC See dynamic CAC
TGM550Junos OS compatibility.........................190
Avaya Media Gateway Controller (MGC)
description.......................................................................217
MGC list............................................................................219
See also MGC list
supported models........................................................219
verifying MGC list.........................................................232
Avaya MGC See Avaya Media Gateway Controller
Avaya VoIP
Avaya Media Gateway Controllers
supported....................................................................219
bandwidth management See dynamic CAC
disk-on-key configuration.........................................222
EPW configuration......................................................222
interfaces..........................................................................217
IP addressing guidelines...........................................190
modules See Avaya VoIP modules
network............................................................................184
prerequisites..................................................................225
troubleshooting............................................................237
typical topology............................................................184
verifying available bandwidth.................................233
verifying configuration................................................231
version incompatibility, correcting.........................237
Avaya VoIP modules
accessing the router from........................................236
administration...............................................................192
Avaya CLI access..........................................................192
CLI access requirements...........................................192
console connection....................................................234
disk-on-key configuration.........................................222
grounding, 10 AWG replacement cable...............183
interface types................................................................217
IP address, modifying (configuration
editor)..........................................................................230
Junos OS configurability............................................218
LEDs See LEDs
MGC list, adding...........................................................228
MGC list, clearing.........................................................228
non-hot-swappability.......................................183, 218
overview............................................................................217
prerequisites..................................................................225
requirements.................................................................186
resetting TGM550.......................................................236
saving the configuration............................................237
SSH connection...........................................................235
summary..........................................................................187
Telnet access.................................................................235
TGM550...........................................................................189
TGM550 IP address, setting (configuration
editor)..........................................................................184
TGM550 maximum gateway capacities.............195
TIM508.............................................................................197
TIM510..............................................................................201
TIM514.............................................................................204
TIM516.............................................................................207
TIM518...............................................................................211
TIM521...............................................................................215
AVCs (aggregated virtual circuits), multilink
bundles, with MLFR FRF.15...........................................437
B
B-channel allocation order, on ISDN PRI
interfaces..............................................................................137
B-channels
description......................................................................142
naming convention......................................................146
verifying.............................................................................173
B8ZS encoding.......................................................................101
backoff algorithm, collision detection............................34
backup connection, ISDN....................................................141
backup connection, wireless modem
functions.........................................................................356
backward-explicit congestion notification (BECN)
bits.........................................................................................463
bandwidth for Avaya VoIP, managing See dynamic
CAC
Index
bandwidth on demand, ISDN
dialer interface..............................................................166
dialer pool.......................................................................166
ISDN BRI interface ......................................................166
overview...........................................................................166
BBL (bearer bandwidth limit)
description.......................................................................221
range and default........................................................229
reported (RBBL), description..................................222
bc-0/0/0
ISDN BRI interface.......................................................146
See also ISDN BRI interfaces; ISDN PRI
interfaces
ISDN PRI interface.......................................................146
bearer bandwidth limit See BBL
BECN (backward-explicit congestion notification)
bits.........................................................................................463
BERTs (bit error rate tests)
on channelized interfaces .................................117, 120
overview.............................................................................23
bipolar with 8zero substitution (B8ZS)
encoding...............................................................................101
bit error rate tests (BERTs) See BERTs
bit stuffing................................................................................107
blinking
TIM508 ACT (active) LED state...........................200
TIM514 ACT (active) LED state.............................206
TIM516 ACT (active) LED state..............................210
TIM518 ACT (active) LED state...............................215
br-0/0/0...................................................................................146
See also B-channels; ISDN BRI interfaces
braces, in configuration statements..............................xxiii
brackets
angle, in syntax descriptions...................................xxiii
square, in configuration statements.....................xxiii
BRI media module See TIM521
bridges, on LAN segments...................................................35
built-in Ethernet interfaces..............................................455
See also Fast Ethernet ports; Gigabit Ethernet
ports
C
C-bit parity frame format
overview..........................................................................109
cables
Avaya VoIP 10 AWG replacement grounding
cable.............................................................................183
TGM550 analog pinouts...........................................194
TGM550 console port, DB-9 connector
pinouts.........................................................................193
TGM550 console port, RJ-45 connector
pinouts.........................................................................193
TIM508 pinout..............................................................198
TIM510 E1/T1 pinouts.................................................202
TIM514 analog pinouts..............................................205
TIM516 pinouts............................................................208
TIM518 pinouts..............................................................212
CAC See dynamic CAC
CAC-BL requirement for dynamic CAC........................222
call admission control See dynamic CAC
Call Admission Control: Bandwidth Limitation
(CAC-BL), requirement for dynamic CAC...............222
call setup, ISDN......................................................................143
callback, ISDN
dialer interface (configuration editor)...................161
encapsulation matching............................................162
overview............................................................................161
rejecting incoming calls ............................................163
screening incoming calls ..........................................163
voice not supported.....................................................161
calling number, ISDN...........................................................145
carrier sense multiple access with collision
detection (CSMA/CD)......................................................33
ccc protocol family..................................................................13
CDMA (Code-Division Multiple Access)
IOTA....................................................................................371
manual account activation.....................................369
OTASP provisioning....................................................368
supported wireless modemcards.........................367
channel number, in interface name...................................9
channel service unit (CSU) device................................466
channelized E1 interfaces
adding...............................................................................120
BERTs ...............................................................................120
clear-channel operation ...........................................120
drop-and-insert ............................................................125
framing ............................................................................120
ISDN PRI ..........................................................................137
number of channels supported...............................116
overview............................................................................115
See also channelized E1 ports
verifying............................................................................135
verifying clear-channel interfaces..........................123
channelized E1 ports
clocking ..................................................................120, 125
clocking for drop-and-insert....................................125
configuring......................................................................120
drop-and-insert clock combinations
internal.....................................................................128
ISDN PRI ..........................................................................137
link hold time ................................................................120
overview............................................................................115
See also channelized E1 interfaces
per-unit scheduler .......................................................120
trace options .................................................................120
channelized T1 interfaces
adding.................................................................................117
BERTs .................................................................................117
clear-channel operation .............................................117
drop-and-insert ............................................................125
framing ..............................................................................117
ISDN PRI ..........................................................................137
line encoding ...................................................................117
number of channels supported...............................116
overview............................................................................115
See also channelized T1 ports
verifying............................................................................135
channelized T1 ports
clocking ....................................................................117, 125
clocking for drop-and-insert....................................125
configuring........................................................................117
drop-and-insert clock combinations
external....................................................................128
ISDN PRI ..........................................................................137
link hold time ..................................................................117
overview............................................................................115
See also channelized T1 interfaces
per-unit scheduler ........................................................117
trace options ...................................................................117
channelized T1/E1/ISDN PRI interfaces,
overview.................................................................................115
SeealsochannelizedE1 interfaces; channelized
T1 interfaces; ISDN PRI interfaces
channelized T1/E1/ISDN PRI ports, overview..............115
See also channelized E1 ports; channelized T1
ports; ISDN PRI interfaces
CHAP (Challenge Handshake Authentication
Protocol)
enabling for dialer interfaces..................................387
enabling for PPPoA.....................................................261
enabling on ATM-over-ADSL interfaces..............261
enabling on ATM-over-SHDSL interfaces...........261
enabling on dialer interfaces...................................387
overview..........................................................................465
PPP links.........................................................................465
PPPoE...............................................................................481
chassis clusters
aggregated Ethernet interfaces...............................64
configuring LACP...........................................................66
redundant Ethernet interfaces.................................64
understanding LACP....................................................64
checksum
overview.............................................................................25
Cisco NLPID encapsulation
classes and power ratings
PoE......................................................................................88
classful addressing.................................................................14
classifiers
defining example.........................................................426
understanding..............................................................426
clear-channel interface on channelized port
configuring...............................................................117, 120
verifying............................................................................123
CLI
Avaya VoIP......................................................................184
VoIP...................................................................................184
CLI configuration editor
channelized E1 interfaces..........................................120
channelized T1 interfaces............................................117
CHAP on ATM-over-ADSL interfaces...................261
CHAP on ATM-over-SHDSL interfaces................261
CHAP on dialer interfaces........................................387
ISDN connections.........................................................157
network interfaces, deleting.............................38, 105
PAP on dialer interfaces...........................................386
CLI, Avaya VoIP, accessing.................................................192
clock rate, serial interface
DTE default reduction...............................................404
clocking
channelized ports.................................................117, 120
data stream clocking....................................................25
overview.............................................................................24
possible combinations for
drop-and-insert........................................................128
requirement for drop-and-insert............................125
serial interface, inverting the transmit
clock............................................................................403
serial interface, modes..............................................403
Index
CM, Avaya See Avaya Communication Manager
collision detection
backoff algorithm..........................................................34
overview.............................................................................34
combined stations, HDLC.................................................467
comments, in configuration statements.....................xxiii
Communication Manager (CM), Avaya See Avaya
Communication Manager
congestion control, for Frame Relay, with DE
bits.........................................................................................463
connection process
ISDN BRI interfaces......................................................143
LCP, for PPP..................................................................464
serial interfaces............................................................402
connector pinouts
TIM508 ports................................................................198
TIM516 ports.................................................................208
TIM518 ports...................................................................212
console port
adapter (TGM550)......................................................192
on TGM550, DB-9 connector pinouts..................193
on TGM550, RJ-45 connector pinouts.................193
console port connection to TGM550...........................234
conventions
for interface names..........................................................9
notice icons.....................................................................xxii
text and syntax..............................................................xxii
copy running-config startup-config command.........237
CoS
link services verifying..................................................433
CoS components for link services
applying on constituent links..................................445
classifiers (configuration editor)...........................426
classifiers (example).................................................426
forwarding classes (configuration editor).........426
forwarding classes (example)...............................426
scheduler maps example.........................................429
shaping rate....................................................................431
shaping rates, configuring........................................432
understanding scheduler maps.............................428
verifying...........................................................................435
CPE device with PPPoE.....................................................469
See also PPPoE
CRC (cyclic redundancy check)........................................25
CRTP (Compressed Real-Time Transport Protocol)
E1 interfaces, configuring..........................................442
E1 interfaces, understanding....................................441
overview...........................................................................417
T1 interfaces, configuring..........................................442
T1 interfaces, understanding....................................441
CSMA/CD (carrier sense multiple access with
collision detection)............................................................33
CSU (channel service unit) device................................466
curly braces, in configuration statements...................xxiii
customer premises equipment (CPE) device with
PPPoE..................................................................................469
See also PPPoE
customer support.................................................................xxiv
contacting JTAC...........................................................xxiv
cyclic redundancy check (CRC)........................................25
D
D-channel
description......................................................................142
verifying.............................................................................174
D4 framing................................................................................101
data communications equipment See DCE
Data Link Layer
error notification.............................................................29
flow control......................................................................29
frame sequencing..........................................................29
MAC addresses...............................................................28
network topology...........................................................28
physical addressing.......................................................28
purpose..............................................................................28
sublayers...........................................................................29
data packets
integrating with voice, with
drop-and-insert........................................................125
LFI handling...................................................................424
data service unit (DSU) device......................................466
data stream clocking.............................................................25
data terminal equipment See DTE
data-link connection identifiers See DLCIs
DB-9 connector pinouts
TGM550 console port................................................193
dc-0/0/0
ISDN BRI interface.......................................................146
See also D-channel; ISDN BRI interfaces;
ISDN PRI interfaces
ISDN PRI interface.......................................................146
DCE (data communications equipment)
serial connection process........................................402
serial device ..................................................................401
DCE clocking mode.............................................................403
DDRSeedial-on-demandroutingbackup, ISDNSee
dial-on-demand routing backup, USB modem
DE (discard eligibility) bits
BECN bits.......................................................................463
FECN bits........................................................................463
delay-sensitive packets, LFI handling..........................424
See also LFI
deleting
network interfaces...............................................38, 105
serial interfaces...........................................................409
destination prefix lengths.....................................................15
Deutsche Telekom UR-2 operating mode..................248
device
Avaya VoIP module overview..................................183
DSL.....................................................................................241
diagnosis
BERT....................................................................................23
load balancing on the link services
interface.....................................................................450
packet encapsulation on link services
interfaces...................................................................449
PPP magic numbers..................................................466
verifying B-channels....................................................173
verifying D-channels....................................................174
verifying dialer interfaces...........................................177
verifying ISDN BRI interfaces....................................172
verifying ISDN call status...........................................176
verifying ISDN PRI interfaces....................................173
verifying ISDN status....................................................171
verifying link services CoS........................................435
verifying PPPoA for ATM-over-ADSL
configuration..................................................254, 266
VoIP interface................................................................237
dial backup
configuring.....................................................................380
configuring (configuration editor)..........................155
interfaces to back up........................................154, 380
dial-in, ISDN
dialer interface ...............................................................161
encapsulation matching............................................162
overview............................................................................161
rejecting incoming calls ............................................163
voice not supported.....................................................161
dial-in, USB modem
dialer interface ............................................................384
overview..........................................................................384
voice not supported....................................................373
dial-on-demand filter See dialer filter, ISDN
dial-on-demand routing backup, ISDN
dialer filter.......................................................................156
See also dialer filter, ISDN
dialer watch....................................................................158
See also dialer watch
OSPF support.................................................................157
dial-on-demand routing backup, USB modem
dialer filter.......................................................................381
See also dialer filter, USB modem
dialer watch...................................................................382
dialer filter, ISDN
applying to the dialer interface................................157
configuring.......................................................................157
overview...........................................................................156
dialer filter, USB modem
overview...........................................................................381
dialer filter, wireless modem
functions.........................................................................356
dialer interface, ISDN
adding...............................................................................152
bandwidth on demand..............................................166
callback ...........................................................................163
dial-in ................................................................................161
dialer filter.......................................................................156
See also dialer filter, ISDN
dialer watch See dialer watch
disabling dial-out ........................................................170
encapsulation matching for dial-in or
callback.......................................................................162
limitations.......................................................................150
rejecting incoming calls.............................................163
restrictions......................................................................150
secondary (backup) connection............................154
verifying.............................................................................177
dialer interface, USB modem
adding...............................................................................377
dial-in ..............................................................................384
dialer filter.......................................................................381
See also dialer filter, USB modem
dialer watch See dialer watch
limitations.......................................................................373
restrictions......................................................................373
secondary (backup) connection...........................380
Index
dialer interface, wireless modem...................................355
activation delay............................................................357
authentication..............................................................356
backup interface..........................................................356
See also backup connection, wireless
modem
CHAP authentication.................................................356
deactivation delay.......................................................357
dialer filter......................................................................356
See also dialer filter, wireless modem
dialer watch...................................................................356
See also dialer watch, wireless modem
idle timeout....................................................................357
initial route check.........................................................357
operating parameters................................................357
PAP authentication....................................................356
dialer interfaces
CHAP for PPP................................................................387
PAP for PPP...................................................................386
dialer options, ISDN
for ISDN PRI service.....................................................137
dialer pools, ISDN
for bandwidth on demand ......................................166
for dialer watch ............................................................159
ISDN BRI physical interface .....................................145
dialer pools, USB modem
for dialer watch............................................................382
dialer watch
adding a dialer watch interface..............................159
dialer pool ............................................................159, 382
ISDN interface for ........................................................159
overview.................................................................158, 382
watch list ..............................................................158, 382
dialer watch, wireless modem
functions.........................................................................356
DID on line ports..................................................198, 204, 211
digital subscriber line (DSL) See ATM-over-ADSL
interfaces; ATM-over-SHDSL interfaces; DSLAM
connection
direct inward dialing, on line ports...............198, 204, 211
discard eligibility bits See DE bits
discard interface...................................................................456
discovery packets, PPPoE.................................................470
disk-on-key configuration
description......................................................................222
procedure........................................................................224
requirements.................................................................223
RESET CONFIG button caution..............................223
dl0.....................................................................................150, 373
See also dialer interface, ISDN
DLCIs (data-link connection identifiers)
in MLFR FRF.16 bundles, understanding.............439
overview..........................................................................463
documentation
comments on................................................................xxiv
domains
broadcast domains.......................................................36
collision domains...........................................................35
dotted decimal notation.......................................................14
drop-and-insert of time slots, on channelized ports
clock source requirement..........................................125
configuring.......................................................................125
overview...........................................................................125
possible clock combinations...................................128
sample configuration..................................................128
signaling channel requirement................................125
DS0 time slots
channelization................................................................115
See also channelized E1 interfaces;
channelized T1 interfaces
drop-and-insert, on channelized T1/E1
interfaces.....................................................................125
DS1 signals
E1 and T1..........................................................................100
See also E1 interfaces; T1 interfaces
multiplexing into DS2 signal....................................106
DS2 signals
bit stuffing.......................................................................107
frame format..................................................................107
DS3 signals
DS3 C-bit parity frame format................................109
M13 frame format.........................................................107
dsc interface..........................................................................456
DSL See ATM-over-ADSL interfaces;
ATM-over-SHDSL interfaces; DSLAMconnection
DSL access multiplexer See DSLAMconnection
DSLAMconnection
ATM-over-ADSL interface for.................................248
ATM-over-SHDSL interface for..............................255
DSU (data service unit) device.......................................466
DTE (data terminal equipment)
default clock rate reduction....................................404
serial connection process........................................402
serial device ..................................................................401
DTE clocking mode See internal clocking mode
dying gasp message, SHDSL.................................260, 269
dynamic CAC
activation priority, description..................................221
BBL, description............................................................221
CAC-BL requirement for WANs..............................222
configuring on WAN interfaces (configuration
editor)..........................................................................229
overview...........................................................................221
supported interfaces...................................................221
dynamic call admission control See dynamic CAC
E
E1 interfaces
AMI encoding.................................................................100
CRTP, configuring........................................................442
CRTP, understanding..................................................441
data stream...................................................................100
encoding..........................................................................100
framing..............................................................................101
HDB3 encoding..............................................................101
loopback..........................................................................102
overview..........................................................................100
See also E1 ports; channelized E1 interfaces
signals..............................................................................100
E1 ports
fractional, channel number..........................................9
overview..........................................................................100
See also E1 interfaces; channelized E1 ports
E1 trunk ports, TIM510
description......................................................................201
pinouts.............................................................................202
E1/T1 media module See TIM508 See TIM510 See
TIM516 See TIM518
E3 interfaces
bit stuffing.......................................................................107
data stream....................................................................106
DS3 framing....................................................................107
multiplexing on..............................................................107
overview..........................................................................106
See also E3 ports
E3 ports
overview..........................................................................106
See also E3 interfaces
EIA-232....................................................................................405
EIA-422....................................................................................405
EIA-449...................................................................................405
EIA-530...................................................................................404
Electronic Preinstallation Worksheet (EPW), for
Avaya VoIP configuration..............................................222
See also EPWconfiguration
encapsulation overhead, PPP and MLPPP................450
encapsulation type
ATM-over-ADSL logical interfaces.......................248
ATM-over-ADSL physical interfaces....................248
ATM-over-SHDSL physical interfaces.................255
Frame Relay..................................................................462
HDLC................................................................................466
ISDN dial-in and callback, monitoring.................162
overview...........................................................................461
PPP...................................................................................464
PPPoE.............................................................................469
verifying for LFI and load balancing.....................449
encoding
AMI....................................................................................100
B8ZS..................................................................................101
channelized T1 .......................................................117, 120
HDB3..................................................................................101
EPW(Electronic Preinstallation Worksheet)
configuration
description......................................................................222
procedure........................................................................224
requirements.................................................................223
RESET CONFIG button caution..............................223
error notification, in the Data Link Layer........................29
ESF (extended superframe) framing............................102
Ethernet cable
TGM550 console DB-9 connector
pinouts.........................................................................193
TGM550 console, RJ-45 connector
pinouts.........................................................................193
Ethernet interfaces.................................................................33
access control.................................................................33
broadcast domains.......................................................36
collision detection.........................................................34
collision domains...........................................................35
CSMA/CD..........................................................................33
enabling promiscuous mode.....................................43
frame format...................................................................36
overview.............................................................................33
See also Fast Ethernet ports; Gigabit Ethernet
ports
Ethernet link aggregation
overview............................................................................45
Ethernet over ATM encapsulation.................................248
Index
Ethernet over ATMLLC encapsulation
ETR LED....................................................................................197
ETSI TS 101 388 V1.3.1 operating mode.......................248
EU-64 addresses....................................................................29
explicit clocking signal transmission...............................25
extended superframe (ESF) framing............................102
F
failover connection, ISDN....................................................141
FAQ(frequently asked questions)
Are LFI and load balancing working
correctly?....................................................................447
What causes jitter and latency on multilink
bundles?.....................................................................447
What clock combinations are possible for
channelized T1/E1 drop-and-insert?................128
Which CoS components apply on link services
interface?...................................................................445
Why Are Packets Dropped on a PVC Between
a J Series Device and Another Vendor?.........454
Why is the VoIP interface unavailable?...............237
Fast Ethernet ports
CHAP for PPPoA...........................................................261
overview.............................................................................33
PPPoE session on........................................................476
static ARP entries .........................................................39
FCS (frame check sequence)
checksums........................................................................25
CRCs....................................................................................25
overview.............................................................................25
two-dimensional parity...............................................26
FEAC C-bit condition indicators.......................................110
FECN (forward-explicit congestion notification)
bits.........................................................................................463
flowcontrol
Data Link Layer...............................................................29
font conventions....................................................................xxii
forward-explicit congestion notification (FECN)
bits.........................................................................................463
forwarding classes
defining example.........................................................426
understanding..............................................................426
four-wire mode (1 port), SHDSL See
fragmentation
configuration by forwarding class..........................418
fragmentation, verifying on the link services
interface..............................................................................448
frame check sequence See FCS
Frame Relay encapsulation
congestion control......................................................463
DLCIs................................................................................463
overview..........................................................................462
PVCs.................................................................................463
SVCs.................................................................................463
virtual circuits...............................................................462
Frame Relay network, typical..........................................462
frames
DS2 M-frame format...................................................107
DS3 C-bit parity frame format................................109
DS3 M13 frame format................................................107
Ethernet frame format.................................................36
sequencing, Data Link Layer......................................29
framing
channelized E1 ..............................................................120
channelized T1 ................................................................117
fxp interfaces, for chassis clusters.................................455
G
G.992.1 Deutsche TelekomUR-2 operating
mode....................................................................................248
G.992.1 Non-UR-2 operating mode...............................248
G.SHDSL interfaces
logical properties (configuration editor).............277
physical properties.......................................................277
G.SHDSL PIMs........................................................................273
Annex A or Annex B modes.....................................255
configuring.....................................................................255
default mode.................................................................255
standard supported....................................................273
Gateway Module See TGM550
ge-0/0/0, management interface................................455
See also Gigabit Ethernet ports
CHAP for PPPoA...........................................................261
dynamic CAC for voice packets (configuration
editor)..........................................................................229
See also Avaya VoIP
overview.............................................................................33
PPPoE session on........................................................476
static ARP entries..........................................................39
global unicast IPv6 addresses.............................................17
gr-0/0/0 interface....................................................................6
gre interface
overview................................................................................7
grounding
Avaya VoIP 10 AWG replacement cable..............183
grounding cable required for TGM550.........................225
GSM(Global Systemfor Mobile Communications)
profile...............................................................................364
unlocking SIM................................................................372
H
hardware
Avaya VoIP module overview..................................183
supported platforms...................................................xxii
hardware features
Avaya VoIP modules...................................................183
HDB3 encoding.......................................................................101
HDLC (High-Level Data Link Control)
encapsulation..............................................................466
HDLC operational modes.........................................467
HDLC stations...............................................................467
high-density bipolar 3 code (HDB3) encoding...........101
High-Level Data Link Control See HDLC
hostname
for PPPoA CHAP...........................................................261
I
IEEE 802.3ad standard
Ethernet link aggregation............................................45
IG550 Integrated Gateway See Avaya IG550
Integrated Gateway; Avaya VoIP modules See
Avaya VoIP modules
incoming calls
rejecting............................................................................163
screening.........................................................................163
inet protocol family.................................................................12
inet6 protocol family...............................................................12
Integrated Services Digital Network See ISDN
interface naming conventions..............................................9
interfaces
aggregated Ethernet.....................................................45
ATM-over-ADSL interfaces.......................................241
Avaya VoIP.......................................................................217
channelized T1/E1/ISDN PRI interfaces................115
clocking..............................................................................24
Data Link Layer...............................................................28
E1 interfaces.....................................................................99
E3 interfaces..................................................................106
Ethernet interfaces........................................................33
FCS......................................................................................25
G.SHDSL interfaces.....................................................273
IPv4 addressing...............................................................13
IPv6 addressing...............................................................16
ISDN interfaces.............................................................145
logical properties..............................................................11
MTU values.......................................................................26
overview...............................................................................3
See also ATM-over-ADSL interfaces;
ATM-over-SHDSL interfaces;
channelized interfaces; ISDNinterfaces;
link services interface; loopback
interface; management interfaces;
network interfaces; ports; special
interfaces
physical encapsulation..............................................461
See also encapsulation type
physical properties.........................................................22
protocol families..............................................................12
redundant Ethernet......................................................64
special interfaces..............................................456, 457
supported for dynamic CAC, for Avaya
VoIP................................................................................221
See also dynamic CAC
T1 interfaces.....................................................................99
T3 interfaces..................................................................106
VLANs................................................................................20
VoIP....................................................................................217
internal clocking mode......................................................403
Internet-based over the air See IOTA
IOCs (I/OCards) See IOC number
slot number........................................................................9
IOTA (Internet-based over the air), account
activation..............................................................................371
IP addresses...............................................................................13
Avaya VoIP module, guidelines for........................190
TGM550, guidelines for.............................................190
See also addresses; IPv4 addressing; IPv6
addressing
ip telnet port command.....................................................235
ip telnet-client command.................................................235
ip-0/0/0 interface....................................................................6
ip-ip interface
overview................................................................................7
Index
IPv4 addressing
classful addressing.........................................................14
dotted decimal notation..............................................14
MAC-48 address format.............................................29
overview..............................................................................13
subnets...............................................................................14
VLSMs.................................................................................15
IPv6 addressing
address format................................................................16
address scope...................................................................17
address structure.............................................................17
address types....................................................................17
overview.............................................................................16
IPv6, enabling............................................................................19
ISDN BRI interfaces
adding an interface......................................................148
B-channel interface.....................................................146
bandwidth on demand .............................................166
call setup.........................................................................143
callback See callback
calling number...............................................................145
connection initialization.............................................143
D-channel interface....................................................146
dial backup.....................................................................154
dial-in See dial-in
dial-on-demand routing backup, with
OSPF.............................................................................157
dialer filter.......................................................................156
dialer interface See dialer interface, ISDN
dialer watch....................................................................159
disabling dial-out.........................................................170
disabling ISDN signaling............................................170
ISDN channels...............................................................142
naming conventions....................................................146
NT1 devices.....................................................................142
overview...........................................................................146
See also ISDN connections
PIMs supported.............................................................146
Q.931 timer......................................................................145
requirements..................................................................144
S/T interfaces................................................................142
screening incoming calls...........................................163
session establishment...............................................144
SPID...................................................................................145
static TEI..........................................................................145
switch types...................................................................145
TEI option........................................................................145
typical network..............................................................142
U interface.......................................................................143
verifying call status......................................................176
verifying ISDN interfaces............................................172
ISDN BRI ports
for TIM521 See TIM521
ISDN connections
adding an ISDN BRI interface..................................148
adding an ISDN PRI interface...................................137
calling number...............................................................145
configuring.......................................................................141
dial-in See dial-in
dial-on-demand routing backup, with
OSPF.............................................................................157
dialer filter See dialer filter
disabling dial-out ........................................................170
disabling ISDN signaling ...........................................170
ISDN interface types...................................................145
overview...........................................................................145
See also dialer interfaces; ISDN BRI
interfaces; ISDN PRI interfaces
Q.931 timer......................................................................145
requirements..................................................................144
SPID...................................................................................145
static TEI..........................................................................145
switch types...........................................................136, 145
TEI option........................................................................145
verifying dialer interfaces...........................................177
verifying ISDN BRI interfaces....................................172
verifying ISDN PRI interfaces....................................173
ISDN PRI interfaces
adding................................................................................137
B-channel allocation order.......................................137
B-channel interface.....................................................146
channelized interface.................................................146
D-channel interface....................................................146
dial backup.....................................................................154
dial-in See dial-in
dialer filter.......................................................................156
dialer options..................................................................137
dialer watch....................................................................159
disabling dial-out.........................................................170
disabling ISDN signaling............................................170
naming conventions....................................................146
PIM supported...............................................................146
Q.931 timers.....................................................................137
screening incoming calls...........................................163
supported switch types.............................................136
transmission...................................................................136
verifying configuration................................................138
verifying ISDN interfaces............................................173
ISO protocol family..................................................................12
ITU Annex B non-UR-2 operating mode.....................248
ITU Annex B UR-2 operating mode...............................248
ITU DMT bis operating mode..........................................248
ITU DMT operating mode.................................................248
ITU G.992.1 operating mode............................................248
ITU G.992.5 operating mode...........................................248
J
J Series
Avaya VoIP connectivity............................................183
USB modem..................................................................373
J2320
TGM550...........................................................................189
TIM508.............................................................................197
TIM510..............................................................................201
TIM514.............................................................................204
TIM516.............................................................................207
TIM518...............................................................................211
TIM521...............................................................................215
J2320 routers
slot number........................................................................9
J2350
TGM550...........................................................................189
TIM508.............................................................................197
TIM510..............................................................................201
TIM514.............................................................................204
TIM516.............................................................................207
TIM518...............................................................................211
TIM521...............................................................................215
J2350 routers
slot number........................................................................9
J4300
TGM550...........................................................................189
TIM508.............................................................................197
TIM510..............................................................................201
TIM514.............................................................................204
TIM516.............................................................................207
TIM518...............................................................................211
TIM521...............................................................................215
J4350
J4350 routers
MTU values.......................................................................26
slot number........................................................................9
J6300
TGM550...........................................................................189
TIM508.............................................................................197
TIM510..............................................................................201
TIM514.............................................................................204
TIM516.............................................................................207
TIM518...............................................................................211
TIM521...............................................................................215
J6350
J6350 routers
MTU values.......................................................................26
slot number........................................................................9
jitter, removing on multilink bundles.............................447
Junos operating system(Junos OS)
Avaya VoIP configurability with..............................218
TGM550 firmware compatibility with.................190
Junos OS
USB modem..................................................................373
L
LACP (Link Aggregation Control Protocol)
configuring on chassis clusters................................66
configuring on standalone devices.........................60
understanding.................................................................46
understanding in chassis cluster mode................64
LANs
bridges on LAN segments...........................................35
collision domains ..........................................................35
Index
repeaters on LAN segments......................................35
topology..............................................................................21
latency, reducing on multilink bundles.........................447
LCP (Link Control Protocol), connection
process................................................................................464
LEDs
ACT (TGM550 active)................................................197
ACT (TIM508 active)................................................200
ACT (TIM510 active)..................................................203
ACT (TIM514 active)..................................................206
ACT (TIM516 active)...................................................210
ACT (TIM518 active)...................................................215
ACT (TIM521 active)....................................................216
ALM (TGM550 alarm)................................................197
ALM (TIM508 alarm)................................................200
ALM(TIM510 alarm)..................................................203
ALM(TIM514 alarm)..................................................206
ALM (TIM516 alarm)...................................................210
ALM (TIM518 alarm)...................................................215
ALM (TIM521 alarm)...................................................216
ASB (alternate software bank)...............................197
ETR (emergency transfer relay)..............................197
SIG (signal)....................................................................203
TGM550 port status....................................................197
TIM508 link status.....................................................200
TIM510 link status.......................................................203
TIM514 link status.......................................................206
TIM516 link status........................................................210
TIM518 link status.........................................................215
TIM521 link status.........................................................216
TST (test).......................................................................203
LFI (link fragmentation and interleaving)
enabling (configuration editor)..............................425
overview..........................................................................424
See also link services interface
LINE and TRUNK ports, on Avaya VoIP
TGM550...............................................................................189
LINE ports, TIM514...............................................................204
line timing...............................................................................403
Link Aggregation Control Protocol See LACP
link aggregation, Ethernet
overview............................................................................45
link fragmentation and interleaving See LFI
link hold time, channelized ports.............................117, 120
link services..................................................................................3
See also link services interface; lsq-0/0/0
link services intelligent queuing interface
channels, with MLFR FRF.16, configuring..........440
channels, with MLFR FRF.16,
understanding..........................................................439
classifiers and forwarding classes
(example)..................................................................426
MLFR FRF.16 bundles, configuring........................440
MLFR FRF.16 bundles, understanding.................439
scheduler maps (configuration editor)...............428
understanding classifiers and forwarding
classes........................................................................426
link services interface
applying CoS components on constituent
links..............................................................................445
fragmentation, troubleshooting............................448
J Series implementation exceptions.....................415
LFI See LFI
load balancing, troubleshooting...........................450
MLFR FRF.15 bundles, configuring........................438
MLFR FRF.15 bundles, understanding..................437
MLPPP header overhead.........................................449
modifying ls-0/0/0 to lsq-0/0/0.........................443
multilink bundles See multilink bundles
overview...........................................................................413
See also lsq-0/0/0
packet encapsulation, troubleshooting.............449
PPP header overhead...............................................449
preventing dropped packets on PVCs.................454
reducing jitter and latency on multilink
bundles........................................................................447
requirements.................................................................420
services on......................................................................414
troubleshooting LFI and load balancing.............447
understanding modifying ls-0/0/0 to
lsq-0/0/0 ..................................................................443
verifying CoS configuration.....................................435
verifying status.............................................................433
link states, verifying................................................41, 104, 112
link-layer overhead
configuration..................................................................419
link-local unicast IPv6 addresses......................................17
lo0 interface functions.......................................................457
See also loopback interface
lo0.16385, internal loopback address..........................457
load balancing on link services interfaces
FAQ....................................................................................447
troubleshooting............................................................447
verifying..........................................................................450
logical interfaces
ATM-over-ADSL (configuration editor)..............248
ATM-over-SHDSL........................................................255
logical units
number in interface name.............................................9
loop clocking mode.............................................................403
loopback address, internal, lo0.16385.........................457
loopback interface
functions.........................................................................457
loopback signals, E1 and T1...............................................102
lsi interface...................................................................................7
lsq-0/0/0
interface description.......................................................6
lt-0/0/0 interface.....................................................................6
M
M13 frame format..................................................................107
MAC (media access control) addresses
associating with IP addresses on Ethernet
subnets..........................................................................39
EUI-64 addresses..........................................................29
in static ARP entries......................................................39
MAC-48 address format.............................................29
overview.............................................................................29
physical addressing.......................................................28
MAC-48 addresses................................................................29
magic numbers, PPP..........................................................466
management interfaces
naming conventions........................................................9
overview..........................................................................455
manuals
Avaya VoIP......................................................................219
comments on................................................................xxiv
media access control See MAC addresses
Media Gateway Controller See Avaya Media
Gateway Controller; MGC list
media types supported...........................................................3
memory stick, USB, for Avaya VoIP
configuration......................................................................222
MGC See Avaya Media Gateway Controller; MGC
list
MGC list
clearing............................................................................228
configuring.....................................................................228
overview...........................................................................219
See also Avaya VoIP
verifying...........................................................................232
MLFR FRF.15
multilink bundles, configuring................................438
multilink bundles, understanding..........................437
MLFR FRF.16
multilink bundles, configuring................................440
multilink bundles, understanding.........................439
mlfr-end-to-end protocol family.......................................13
mlfr-uni-nni protocol family.................................................13
MLPPP (Multilink Point-to-Point Protocol)
configuring multilink bundles .................................422
sample topology..........................................................423
MLPPP encapsulation, on the link services
interface..............................................................................449
MLPPP over ADSL
description.....................................................................270
mlppp protocol family............................................................13
modemconnection to router USB port
connecting USB modem to router........................374
MPLS protocol family.............................................................12
MTU (maximumtransmission unit)
default values for all interfaces................................26
maximum values for all interfaces..........................26
multicast IPv6 addresses......................................................17
multiclass MLPPP
configuration..................................................................415
multilink bundles
(configuration editor)............................................426
(example)..................................................................426
LFI (configuration editor).........................................425
MLFR FRF.15, configuring.........................................438
MLFR FRF.15, understanding...................................437
MLFR FRF.16, configuring.........................................440
MLFR FRF.16, understanding..................................439
overview...........................................................................421
preventing dropped packets...................................454
queuing, on Q2 of constituent links.......................417
reducing latency...........................................................447
removing jitter...............................................................447
sample topology..........................................................423
shaping rate....................................................................431
understanding scheduler maps.............................428
Index
MultilinkFrameRelayend-to-endSeeMLFRFRF.15,
understanding
N
names, of network interfaces...............................................9
NCPs (Network Control Protocols)..............................465
Network Control Protocols (NCPs)..............................465
network interfaces
ATM-over-ADSL configuration...............................248
ATM-over-ADSL interfaces.......................................241
ATM-over-SHDSL configuration............................255
channelized E1 configuration...................................120
channelized T1 configuration............................117, 120
channelized T1/E1/ISDN PRI interfaces................115
clocking..............................................................................24
deleting.....................................................................38, 105
deleting serial interface............................................409
E1 interfaces.....................................................................99
E3 interfaces..................................................................106
Ethernet interfaces........................................................33
FCS......................................................................................25
G.SHDSL interfaces.....................................................273
IPv4 addressing...............................................................13
IPv6 addressing...............................................................16
ISDN interfaces.............................................................145
media types........................................................................3
MTU values.......................................................................26
names..............................................................................4, 9
physical encapsulation..............................................461
sample name.....................................................................9
T1 interfaces.....................................................................99
T3 interfaces..................................................................106
verifying ATM-over-ADSL properties..........251, 263
verifying ATM-over-SHDSL
configuration..................................................258, 266
verifying channelized interfaces.............................135
verifying ISDN PRI configuration............................138
verifying link states........................................41, 104, 112
verifying properties........................................41, 104, 113
VLANs................................................................................20
networks
Avaya VoIP......................................................................184
IPv4 subnets.....................................................................14
PPPoE session on an ATM-over-ADSL
loop...............................................................................478
PPPoE session on an Ethernet loop.....................477
sample LFI and multilink bundle
topology......................................................................423
sample multilink bundle and LFI
topology......................................................................423
VoIP...................................................................................184
no ip telnet command........................................................236
no ip telnet-client command...........................................236
non-LFI packets See data packets
non-UR-2 operating mode...............................................248
Normal Response Mode, HDLC......................................467
notice icons..............................................................................xxii
NRM, HDLC.............................................................................467
NT1 devices..............................................................................142
O
OSPF (Open Shortest Path First)
dial-on-demand routing backup support,
ISDN...............................................................................157
ISDN dial-on-demand routing backup
support.........................................................................157
OTASP (over the air service provisioning), account
activation............................................................................368
out-of-band management interfaces.........................455
over the air service provisioning See OTASP
P
packet encapsulation
overview...........................................................................461
troubleshooting on the link services
interface......................................................................447
verifying on the link services interface................449
packet fragmentation
troubleshooting on the link services
interface......................................................................447
verifying on the link services interface................448
packets
PPPoE discovery..........................................................470
PADI packets..........................................................................470
PADO packets........................................................................470
PADR packets........................................................................470
PADS packets........................................................................470
PADT packets..........................................................................471
PAP (Password Authentication Protocol)
enabling for dialer interfaces..................................386
enabling on dialer interfaces..................................386
parentheses, in syntax descriptions..............................xxiii
password
for TGM550 access.....................................................192
pd-0/0/0 interface...................................................................6
pe-0/0/0 interface...................................................................6
per-unit scheduler, channelized ports...................117, 120
permanent virtual circuits See PVCs
physical interface properties
BERT....................................................................................23
encapsulation................................................................461
FCS......................................................................................25
interface clocking...........................................................24
key properties..................................................................22
MTU values.......................................................................26
pimd interface.............................................................................7
pime interface.............................................................................7
PIMs (Physical Interface Modules)
Avaya VoIP modules See Avaya VoIP modules
G.SHDSL.........................................................................255
See also G.SHDSL PIMs
PIM number, always 0....................................................9
slot number........................................................................9
ping, verifying link states......................................41, 104, 112
pinouts
RJ-45 TGM550 console connector.......................193
TGM550 analog RJ-11 connector...........................194
TGM550 console DB-9 connector.........................193
TGM550 console port................................................193
TIM508............................................................................198
TIM510 E1/T1 RJ-45....................................................202
TIM514 analog RJ-11 connector..............................205
TIM516.............................................................................208
TIM518...............................................................................212
plesiochronous networks.....................................................24
PoE
classes and power ratings..........................................88
Specifications..................................................................87
SRX210 Services Gateway.................................87
SRX240 Services Gateway................................87
SRX650 Services Gateway...............................87
Point-to-Point Protocol See PPP
Point-to-Point Protocol over ATMSee PPPoA
Point-to-Point Protocol over Ethernet See PPPoE
polarity, signal.......................................................................403
ports
Avaya VoIP.......................................................................217
console (TGM550)......................................................189
interfaces overview..........................................................3
See also ATM-over-ADSL interfaces;
ATM-over-SHDSL interfaces; ISDN
interfaces; link services interface;
loopback interface; management
interfaces; network interfaces; special
interfaces
LINE and TRUNK, on Avaya VoIP
TGM550......................................................................189
telephone and trunk, on Avaya VoIP
TGM550......................................................................189
TGM550...........................................................................189
TIM510..............................................................................201
TIM514.............................................................................204
TIM521...............................................................................215
VoIP....................................................................................217
pp0
interface description.......................................................6
PPP
CHAP................................................................................387
PAP...................................................................................386
PPP encapsulation
CHAP authentication.................................................465
CSU/DSU devices.......................................................466
LCP connection process...........................................464
magic numbers............................................................466
NCPs................................................................................465
on the link services interface..................................449
overview.........................................................................464
PPP over ATMSee PPPoA
PPP over ATM-over-ADSL See PPPoA
PPP over ATM-over-SHDSL See PPPoA
PPP over Ethernet See PPPoE
PPPoA (Point-to-Point Protocol over ATM)
CHAP.................................................................................261
logical encapsulation.................................................248
logical encapsulation (ATM-over-ADSL)..........248
physical encapsulation
(ATM-over-ADSL)..................................................248
physical encapsulation
(ATM-over-SHDSL)...............................................255
verifying ATM-over-ADSL
configuration..................................................254, 266
Index
PPPoE (Point-to-Point Protocol over Ethernet)
CHAP, overview.............................................................481
client and server..........................................................469
discovery packets........................................................470
interfaces, overview.....................................................471
overview.........................................................................469
See also PPPoE over ATM-over-ADSL;
PPPoE over ATM-over-SHSDL
radio-router protocol.................................................485
sample topology..........................................................476
session overview...........................................................471
PPPoE Active Discovery Initiation (PADI)
packets................................................................................470
PPPoE Active Discovery Offer (PADO)
packets................................................................................470
PPPoE Active Discovery Request (PADR)
packets................................................................................470
PPPoE Active Discovery Session-Confirmation
(PADS) packets................................................................470
PPPoE Active Discovery Termination (PADT)
packets..................................................................................471
PPPoE over ATMLLC encapsulation
primary stations, HDLC......................................................467
profile, GSM............................................................................364
promiscuous mode
enabling on Ethernet interfaces...............................43
properties, verifying
for ATM-over-ADSL network
interfaces...........................................................251, 263
for ATM-over-SHDSL network
interfaces.........................................................258, 266
for network interfaces..................................41, 104, 113
protocol families
ccc.........................................................................................13
common protocol suites..............................................12
inet........................................................................................12
inet6.....................................................................................12
ISO........................................................................................12
mlfr-end-to-end..............................................................13
mlfr-uni-nni.......................................................................13
mlppp..................................................................................13
MPLS....................................................................................12
overview..............................................................................12
tcc..........................................................................................13
tnp.........................................................................................13
protocols
ARP......................................................................................39
CRTP..................................................................................417
EIA-530..........................................................................404
PPPoE See PPPoE
RS-232............................................................................405
RS-422/449..................................................................405
serial................................................................................404
V.35..................................................................................406
X.21...................................................................................406
publishing responses to ARP requests
static ARP entries..........................................................39
PVCs (permanent virtual circuits)
in multilink bundles, with MLFR FRF.15...............437
in multilink bundles, with MLFR FRF.16...............439
overview..........................................................................463
preventing dropped packets on.............................454
Q
Q.931 timer, ISDN..........................................................137, 145
queuing with LFI
on Q2 of constituent links.........................................417
R
RADIUS authentication, of PPP sessions....................481
RBBL See BBL
redundant Ethernet interfaces
understanding.................................................................64
rejecting incoming calls, ISDN..........................................163
Remote Authentication Dial-In User Service
(RADIUS) authentication, of PPP sessions...........481
remote connection to router
connecting USB modem to router........................374
remote management, USB modem..............................373
repeaters, on LAN segments..............................................35
reported bearer bandwidth limit See BBL
request chassis fpc slot slot-number restart
command............................................................................237
RJ-11 connector pinouts
TGM550 analog ports................................................194
TIM514 analog ports..................................................205
RJ-45 connector pinouts
TGM550 console port................................................193
TIM510 E1/T1 ports.....................................................202
RJ-45 to DB-9 serial port adapter
TGM550 console port.................................................192
routing
configuring PPPoE......................................................469
routing solutions
applying CoS components on link services
interface.....................................................................445
drop-and-insert clock combinations....................128
load balancing on link services interfaces..........447
managing VoIP bandwidth See dynamic CAC
point-to-point sessions over Ethernet...............469
preventing dropped packets on PVCs.................454
reducing jitter and latency on multilink
bundles........................................................................447
RS-232.....................................................................................405
RS-422/449...........................................................................405
RS-530....................................................................................404
RST (reset) button, TGM550..........................................236
S
S/T interface
overview...........................................................................142
PIMs...................................................................................142
samples
drop-and-insert clock combinations....................128
PPPoA for ATM-over-ADSL
configuration..................................................254, 266
scheduler maps
defining and applying example..............................429
understanding..............................................................428
scope, IPv6 addresses
global unicast....................................................................17
link-local unicast..............................................................17
multicast types.................................................................17
site-local unicast.............................................................17
screening incoming calls, ISDN........................................163
secondary stations, HDLC.................................................467
serial interfaces
clocking modes............................................................403
connection process....................................................402
deleting...........................................................................409
DTE default clock rate reduction..........................404
EIA-530..........................................................................404
inverting the transmit clock....................................403
line protocols................................................................404
overview..........................................................................401
See also serial ports
RS-232............................................................................405
RS-422/449..................................................................405
signal polarity...............................................................403
transmission signals...................................................401
V.35..................................................................................406
X.21...................................................................................406
serial numbers, in MAC addresses...................................29
serial ports
overview..........................................................................401
See also serial interfaces
services interfaces
summary.........................................................................6, 7
services interfaces, overview.................................................3
See also link services interface; multilink
services
sessions
ISDN session establishment....................................144
limit on PPPoE sessions.............................................471
PPPoE...............................................................................471
shaping rate
configuring.....................................................................432
overview...........................................................................431
understanding CoS.....................................................428
SHDSL ports See ATM-over-SHDSL interfaces
show access command...........................................254, 266
showclass-of-service classifier name
command...........................................................................435
show class-of-service interface command...............435
showclass-of-service scheduler-map
command...........................................................................435
show interfaces ae0 extensive command....................58
showinterfaces ae0 terse command..............................57
show interfaces at-3/0/0 command.................254, 266
showinterfaces bc-0/0/4:1 extensive
command.............................................................................173
showinterfaces br-6/0/0 extensive
command.............................................................................172
showinterfaces command
for channelized interfaces.........................................135
for clear-channel channelized interfaces............123
show interfaces ct1-3/0/1 command............................135
showinterfaces dc-0/0/4 extensive
command.............................................................................174
showinterfaces detail command.....................41, 104, 113
showinterfaces dl0 extensive command.....................177
show interfaces e1-3/0/1 command..............................123
showinterfaces extensive command..........251, 263, 271
explanation, for ATM-over-ADSL
interfaces..........................................................253, 264
explanation, for ATM-over-SHDSL
interfaces.....................................258, 259, 266, 268
explanation, for ISDN interfaces.............172, 173, 174
explanation, for VoIP interfaces.............................232
Index
showinterfaces lsq-0/0/0 statistics detail
command...........................................................................433
explanation....................................................................434
showinterfaces vp-3/0/0 extensive
command.............................................................................231
show isdn calls command.................................................176
show isdn status command...............................................171
show lacp interfaces ae0 command........................61, 63
show lacp interfaces reth0 command...........................68
showlacp statistics interfaces ae0
command........................................................................61, 62
showtgmdynamic-call-admission-control
command............................................................................233
showtgmfpc slot-number
media-gateway-controller command.....................232
SIG LED....................................................................................203
signals
DS1.....................................................................................100
E1 loopback (control).................................................102
ISDN, disabling..............................................................170
multiplexing DS1 into DS2 signal...........................106
serial polarity................................................................403
serial transmission......................................................401
T1 loopback (control).................................................102
V.35..................................................................................406
X.21...................................................................................406
SIM(subscriber identity module)
unlocking.........................................................................372
site-local unicast IPv6 addresses......................................17
SNEXT (self-near-end crosstalk) threshold,
SHDSL..................................................................................255
SNR (signal-to-noise ratio) margin, SHDSL..............255
special interfaces
CRTP..................................................................................417
dsc interface.................................................................456
IPv4 addressing...............................................................13
IPv6 addressing...............................................................16
loopback interface......................................................457
names...................................................................................9
services interfaces............................................................3
See also link services interface; multilink
services
SPID (service provider ID), ISDN.....................................145
SRX Series Services Gateways
MTU values.......................................................................27
SRX3400 Services Gateways
slot number........................................................................9
slot number........................................................................9
slot number........................................................................9
slot number........................................................................9
SSH connection to TGM550............................................235
st0 interface................................................................................6
static ARP entries
overview............................................................................39
static TEI (terminal endpoint identifier), ISDN..........145
statistics
ATM-over-ADSL interfaces............................254, 265
ATM-over-SHDSL interfaces........................260, 269
ISDN B-channel interfaces........................................173
ISDN D-channel interfaces........................................174
link services interface.................................................433
VoIP interface.................................................................231
status
ATM-over-SHDSL interfaces,
verifying............................................................260, 268
ISDN calls, verifying.....................................................176
ISDN interfaces, verifying............................................171
link states, verifying.......................................41, 104, 112
VoIP interface.................................................................231
subnet masks............................................................................15
subnets See subnetworks
subnetworks
IPv4 subnets.....................................................................14
subscriber identity module See SIM
superframe framing..............................................................101
support, technical See technical support
SVCs (switched virtual circuits).....................................463
switch types, supported, ISDN
for ISDN BRI service.....................................................145
for ISDN PRI service.....................................................136
switched virtual circuits (SVCs).....................................463
switches
on LAN segments...........................................................35
symmetric high-speed digital subscriber line
(SHDSL) See ATM-over-SHDSL interfaces
synchronous networks..........................................................24
syntax conventions...............................................................xxii
systemclock See clocking
T
T1 interfaces
AMI encoding.................................................................100
B8ZS encoding..............................................................101
D4 framing.......................................................................101
data stream.....................................................................99
dynamic CAC for voice packets (configuration
editor)..........................................................................229
See also Avaya VoIP
encoding..........................................................................100
ESF framing....................................................................102
framing..............................................................................101
loopback..........................................................................102
overview............................................................................99
See also T1 ports; channelized T1 interfaces
signals..............................................................................100
superframe framing.....................................................101
T1 ports
fractional, channel number..........................................9
overview............................................................................99
See also T1 interfaces; channelized T1 ports
T1 trunk ports, TIM510
description......................................................................201
pinouts.............................................................................202
T1/E1 media module See TIM508 See TIM510 See
TIM516 See TIM518
T3 interfaces
bit stuffing.......................................................................107
data stream....................................................................106
DS3 framing....................................................................107
multiplexing on..............................................................107
overview..........................................................................106
See also T3 ports
T3 ports
overview..........................................................................106
See also T3 interfaces
tap interface.................................................................................7
tcc protocol family...................................................................13
technical support
contacting JTAC...........................................................xxiv
TEI option, ISDN.....................................................................145
telephone and trunk ports, on Avaya VoIP
TGM550...............................................................................189
telephone calls
rejecting incoming ISDN............................................163
screening incoming ISDN..........................................163
verifying status...............................................................176
Telephony Gateway Module See TGM550
Telephony Interface Module See TIM510; TIM514;
TIM521
Telephony Interface Modules See TIM508; TIM510;
TIM514; TIM516; TIM518; TIM521
Telnet access to TGM550
connecting to TGM550.............................................235
disabling Telnet service.............................................236
enabling Telnet service..............................................235
overview..........................................................................235
security caution............................................................235
telnet command...................................................................235
terminal endpoint identifier See static TEI; TEI
option
TGM550
accessing the router from........................................236
administration...............................................................192
analog port pinouts.....................................................194
Avaya CLI access..........................................................192
Avaya Media Gateway Controllers
supported....................................................................219
CLI access requirements...........................................192
console connection....................................................234
console port pinouts...................................................193
description......................................................................189
grounding cable requirement..................................225
interfaces.........................................................................218
IP address change caution......................................230
editor)..........................................................................230
IP address, setting (configuration editor)...........184
IP addressing guidelines...........................................190
Junos OS compatibility..............................................190
maximum gateway capacities................................195
MGC list, adding...........................................................228
MGC list, clearing.........................................................228
MGCs supported...........................................................219
port LED states..............................................................197
ports..................................................................................189
reset on address change..........................................230
resetting..........................................................................236
RST (reset) button......................................................236
saving the configuration............................................237
SSH connection...........................................................235
Telnet access.................................................................235
Index
Telnet connection to router.....................................236
verifying MGC list.........................................................232
verifying VoIP interface...............................................231
TIM508
connector port pinout................................................198
description.......................................................................197
port configurations.....................................................200
ports, LED states.........................................................200
TIM510
description......................................................................201
E1 trunk ports.................................................................201
ports, LED states.........................................................203
RJ-45 connector port pinouts.................................202
T1 trunk ports.................................................................201
TIM510 interfaces..................................................................218
TIM514
analog port pinouts....................................................205
analog telephone ports............................................204
analog trunk ports......................................................204
description.....................................................................204
port configurations.....................................................205
ports, LED states.........................................................206
TIM514 interfaces..................................................................218
TIM516
connector port pinouts.............................................208
description.....................................................................207
port configurations......................................................210
ports, LED states..........................................................210
TIM518
connector port pinouts...............................................212
description........................................................................211
port configurations.......................................................214
ports, LED states...........................................................215
TIM521
description......................................................................215
ISDN BRI ports...............................................................215
ports, LED states...........................................................216
TIM521 interfaces..................................................................218
time slots
dropping and inserting, on channelized T1/E1
interfaces.....................................................................125
TIMs SeeTIM508; TIM510; TIM514; TIM516; TIM518;
TIM521
tnp protocol family..................................................................13
topology
Avaya VoIP......................................................................184
Data Link Layer...............................................................28
IPv4 subnets.....................................................................15
PPPoE session on an ATM-over-ADSL
loop...............................................................................478
PPPoE session on an Ethernet loop.....................477
sample Frame Relay network.................................462
sample ISDN network.................................................142
sample LAN.......................................................................21
sample LFI and multilink bundle network..........423
sample multilink bundle and LFI network..........423
sample VLAN....................................................................21
VoIP...................................................................................184
trace options, channelized ports.............................117, 120
troubleshooting
applying CoS components on link services
interface.....................................................................445
Avaya VoIP......................................................................237
dropped packets on PVCs.......................................454
jitter and latency on multilink bundles................447
LFI and load balancing on multilink
bundles........................................................................447
TRUNK and LINE ports, on Avaya VoIP
TGM550...............................................................................189
trunk ports, TIM508
pinouts.............................................................................198
TRUNK ports, TIM514.........................................................204
trunk ports, TIM516
pinouts............................................................................208
trunk ports, TIM518
pinouts..............................................................................212
TST LED...................................................................................203
two-dimensional parity........................................................26
two-wire mode (2 ports), SHDSL See
types of interfaces....................................................................9
U
U interface
overview...........................................................................143
PIMs...................................................................................143
umd0.........................................................................................373
umd0 interface..........................................................................6
unicast IPv6 addresses..........................................................17
UR-2 operating mode.........................................................248
URLs
Avaya VoIP support.....................................................219
USB memory stick, for Avaya VoIP
configuration......................................................................222
USB modem...........................................................................373
configuring......................................................................373
See also dialer interfaces; USB modem
interfaces
USB modemconnections
dial-in See dial-in
dialer filter See dialer filter
dialer interface See dialer interface, USB
modem
interface naming conventions................................373
requirements.................................................................374
USB modem interface types...................................373
USB modeminterface
overview...............................................................................6
USB modeminterfaces
dial-in See dial-in
dialer interface See dialer interface, USB
modem
V
V.35...........................................................................................406
variable-length subnet masks (VLSMs).........................15
VCI (virtual channel identifier)
ATM-over-ADSL interfaces ....................................248
VDSL2.......................................................................................295
Configuration
Example.......................................................299, 303
DMT..................................................................................295
ITU-T G.993.2...............................................................295
Key Features........................................................295, 298
Profiles.............................................................................295
PTM..................................................................................295
VDSL2 Interface
Configuration................................................................295
Examples...............................................................295
VDSL2 interfaces
logical properties.........................................................299
physical properties.....................................................299
VDSL2 Mini-PIM....................................................................295
ADSL2 Configuration
Example.................................................................328
verification
ATM-over-ADSL interface properties.........251, 263
ATM-over-SHDSL interface
configuration..................................................258, 266
Avaya VoIP.......................................................................231
B-channels......................................................................173
channelized interfaces...............................................135
clear-channel interfaces............................................123
D-channels......................................................................174
dialer interfaces.............................................................177
interface properties.......................................41, 104, 113
ISDN BRI interfaces......................................................172
ISDN call status.............................................................176
ISDN PRI interface configuration............................138
ISDN PRI interface operation...................................173
ISDN status......................................................................171
link services CoS..........................................................435
link services interface status...................................433
link states..........................................................41, 104, 112
load balancing on the link services
interface.....................................................................450
network interfaces........................................38, 104, 112
packet encapsulation on link services
interface.....................................................................449
PPPoA for ATM-over-ADSL
configuration..................................................254, 266
VoIP....................................................................................231
virtual circuits
DLCIs................................................................................463
overview..........................................................................462
PVCs.................................................................................463
SVCs.................................................................................463
virtual LANs See VLANs
VLANs (virtual LANs)
LAN comparison..............................................................21
overview............................................................................20
topology..............................................................................21
VLSMs (variable-length subnet masks).........................15
voice calls, not supported in dial-in ..............................373
voice calls, not supported in dial-in or callback.........161
voice over IP See Avaya VoIP See Avaya VoIP
modules
voice packets
integrating with data, with
drop-and-insert........................................................125
LFI handling...................................................................424
speeding transmission with CRTP................417, 441
voice traffic latency, controlling with shaping
rates......................................................................................432
See also multilink bundling
VoIP See Avaya VoIP modules
VoIP (voice over IP) See Avaya VoIP; VoIP interface
VoIP interface
addressing guidelines.................................................190
correcting version incompatibility
problem.......................................................................237
Index
editor)..........................................................................230
IP address, setting (configuration editor)...........184
unavailability, correcting............................................237
verifying............................................................................231
vp-0/0/0..................................................................................218
See also VoIP interface
VPI (virtual path identifier)
ATM-over-ADSL interfaces ....................................248
ATM-over-SHDSL interfaces ..................................255
W
WAN interfaces, configuring dynamic CAC on for
Avaya VoIP..........................................................................229
watch list, for ISDN backup...............................................158
watch list, for USB modem backup..............................382
wireless modem...................................................................355
configuration overview..............................................354
logical interface............................................................355
physical interface........................................................363
WAN connection..........................................................353
See also dialer interface, wireless modem
wireless modeminterface
dialer pool......................................................................363
GSM profile..........................................................363, 364
modem initialization string......................................363
X
X.21............................................................................................406

Junos Security Swconfig Interfaces

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Junos Security Swconfig Interfaces

Uploaded by

Copyright:

Available Formats

Junos

Verifying LACP Aggregated Ethernet Interfaces

Ensure that the TGM550 is not currently handling voice traffic.

You might also like