JUNOSe™ Software
for E Series™ Broadband Services Routers
Link Layer Configuration Guide
Release 11.1.x
Juniper Networks, Inc.
1194 North Mathilda Avenue
Sunnyvale, California 94089
USA
408-745-2000
www.juniper.net
Published: 2010-04-07
Juniper Networks, the Juniper Networks logo, JUNOS, NetScreen, ScreenOS, and Steel-Belted Radius are registered trademarks of Juniper Networks, Inc. in
the United States and other countries. JUNOSe is a trademark of Juniper Networks, Inc. All other trademarks, service marks, registered trademarks, or
registered service marks are the property of their respective owners.
Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify, transfer, or
otherwise revise this publication without notice.
Products made or sold by Juniper Networks or components thereof might be covered by one or more of the following patents that are owned by or licensed
to Juniper Networks: U.S. Patent Nos. 5,473,599, 5,905,725, 5,909,440, 6,192,051, 6,333,650, 6,359,479, 6,406,312, 6,429,706, 6,459,579, 6,493,347,
6,538,518, 6,538,899, 6,552,918, 6,567,902, 6,578,186, and 6,590,785.
JUNOSe™ Software for E Series™ Broadband Services Routers Link Layer Configuration Guide
Release 11.1.x
Copyright © 2010, Juniper Networks, Inc.
All rights reserved. Printed in USA.
Writing: Krupa Chandrashekar, Subash Babu Asokan, Pallavi Madhusudhan, Diane Florio, Bruce Gillham, Justine Kangas, Sarah Lesway-Ball, Helen Shaw,
Brian Wesley Simmons, Fran Singer
Editing: Benjamin Mann
Illustration: Nathaniel Woodward
Cover Design: Edmonds Design
Revision History
April 2010—FRS JUNOSe 11.1.x
The information in this document is current as of the date listed in the revision history.
YEAR 2000 NOTICE
Juniper Networks hardware and software products are Year 2000 compliant. The JUNOS Software has no known time-related limitations through the year
2038. However, the NTP application is known to have some difficulty in the year 2036.
ii ■
END USER LICENSE AGREEMENT
READ THIS END USER LICENSE AGREEMENT (“AGREEMENT”) BEFORE DOWNLOADING, INSTALLING, OR USING THE SOFTWARE. BY DOWNLOADING,
INSTALLING, OR USING THE SOFTWARE OR OTHERWISE EXPRESSING YOUR AGREEMENT TO THE TERMS CONTAINED HEREIN, YOU (AS CUSTOMER
OR IF YOU ARE NOT THE CUSTOMER, AS A REPRESENTATIVE/AGENT AUTHORIZED TO BIND THE CUSTOMER) CONSENT TO BE BOUND BY THIS
AGREEMENT. IF YOU DO NOT OR CANNOT AGREE TO THE TERMS CONTAINED HEREIN, THEN (A) DO NOT DOWNLOAD, INSTALL, OR USE THE SOFTWARE,
AND (B) YOU MAY CONTACT JUNIPER NETWORKS REGARDING LICENSE TERMS.
1. The Parties. The parties to this Agreement are (i) Juniper Networks, Inc. (if the Customer’s principal office is located in the Americas) or Juniper Networks
(Cayman) Limited (if the Customer’s principal office is located outside the Americas) (such applicable entity being referred to herein as “Juniper”), and (ii)
the person or organization that originally purchased from Juniper or an authorized Juniper reseller the applicable license(s) for use of the Software (“Customer”)
(collectively, the “Parties”).
2. The Software. In this Agreement, “Software” means the program modules and features of the Juniper or Juniper-supplied software, for which Customer
has paid the applicable license or support fees to Juniper or an authorized Juniper reseller, or which was embedded by Juniper in equipment which Customer
purchased from Juniper or an authorized Juniper reseller. “Software” also includes updates, upgrades and new releases of such software. “Embedded
Software” means Software which Juniper has embedded in or loaded onto the Juniper equipment and any updates, upgrades, additions or replacements
which are subsequently embedded in or loaded onto the equipment.
3. License Grant. Subject to payment of the applicable fees and the limitations and restrictions set forth herein, Juniper grants to Customer a non-exclusive
and non-transferable license, without right to sublicense, to use the Software, in executable form only, subject to the following use restrictions:
a. Customer shall use Embedded Software solely as embedded in, and for execution on, Juniper equipment originally purchased by Customer from Juniper
or an authorized Juniper reseller.
b. Customer shall use the Software on a single hardware chassis having a single processing unit, or as many chassis or processing units for which Customer
has paid the applicable license fees; provided, however, with respect to the Steel-Belted Radius or Odyssey Access Client software only, Customer shall use
such Software on a single computer containing a single physical random access memory space and containing any number of processors. Use of the
Steel-Belted Radius or IMS AAA software on multiple computers or virtual machines (e.g., Solaris zones) requires multiple licenses, regardless of whether
such computers or virtualizations are physically contained on a single chassis.
c. Product purchase documents, paper or electronic user documentation, and/or the particular licenses purchased by Customer may specify limits to
Customer’s use of the Software. Such limits may restrict use to a maximum number of seats, registered endpoints, concurrent users, sessions, calls,
connections, subscribers, clusters, nodes, realms, devices, links, ports or transactions, or require the purchase of separate licenses to use particular features,
functionalities, services, applications, operations, or capabilities, or provide throughput, performance, configuration, bandwidth, interface, processing,
temporal, or geographical limits. In addition, such limits may restrict the use of the Software to managing certain kinds of networks or require the Software
to be used only in conjunction with other specific Software. Customer’s use of the Software shall be subject to all such limitations and purchase of all applicable
licenses.
d. For any trial copy of the Software, Customer’s right to use the Software expires 30 days after download, installation or use of the Software. Customer
may operate the Software after the 30-day trial period only if Customer pays for a license to do so. Customer may not extend or create an additional trial
period by re-installing the Software after the 30-day trial period.
e. The Global Enterprise Edition of the Steel-Belted Radius software may be used by Customer only to manage access to Customer’s enterprise network.
Specifically, service provider customers are expressly prohibited from using the Global Enterprise Edition of the Steel-Belted Radius software to support any
commercial network access services.
The foregoing license is not transferable or assignable by Customer. No license is granted herein to any user who did not originally purchase the applicable
license(s) for the Software from Juniper or an authorized Juniper reseller.
4. Use Prohibitions. Notwithstanding the foregoing, the license provided herein does not permit the Customer to, and Customer agrees not to and shall
not: (a) modify, unbundle, reverse engineer, or create derivative works based on the Software; (b) make unauthorized copies of the Software (except as
necessary for backup purposes); (c) rent, sell, transfer, or grant any rights in and to any copy of the Software, in any form, to any third party; (d) remove
any proprietary notices, labels, or marks on or in any copy of the Software or any product in which the Software is embedded; (e) distribute any copy of
the Software to any third party, including as may be embedded in Juniper equipment sold in the secondhand market; (f) use any ‘locked’ or key-restricted
feature, function, service, application, operation, or capability without first purchasing the applicable license(s) and obtaining a valid key from Juniper, even
if such feature, function, service, application, operation, or capability is enabled without a key; (g) distribute any key for the Software provided by Juniper
to any third party; (h) use the Software in any manner that extends or is broader than the uses purchased by Customer from Juniper or an authorized Juniper
reseller; (i) use Embedded Software on non-Juniper equipment; (j) use Embedded Software (or make it available for use) on Juniper equipment that the
Customer did not originally purchase from Juniper or an authorized Juniper reseller; (k) disclose the results of testing or benchmarking of the Software to
any third party without the prior written consent of Juniper; or (l) use the Software in any manner other than as expressly provided herein.
5. Audit. Customer shall maintain accurate records as necessary to verify compliance with this Agreement. Upon request by Juniper, Customer shall furnish
such records to Juniper and certify its compliance with this Agreement.
■ iii
6. Confidentiality. The Parties agree that aspects of the Software and associated documentation are the confidential property of Juniper. As such, Customer
shall exercise all reasonable commercial efforts to maintain the Software and associated documentation in confidence, which at a minimum includes
restricting access to the Software to Customer employees and contractors having a need to use the Software for Customer’s internal business purposes.
7. Ownership. Juniper and Juniper’s licensors, respectively, retain ownership of all right, title, and interest (including copyright) in and to the Software,
associated documentation, and all copies of the Software. Nothing in this Agreement constitutes a transfer or conveyance of any right, title, or interest in
the Software or associated documentation, or a sale of the Software, associated documentation, or copies of the Software.
8. Warranty, Limitation of Liability, Disclaimer of Warranty. The warranty applicable to the Software shall be as set forth in the warranty statement that
accompanies the Software (the “Warranty Statement”). Nothing in this Agreement shall give rise to any obligation to support the Software. Support services
may be purchased separately. Any such support shall be governed by a separate, written support services agreement. TO THE MAXIMUM EXTENT PERMITTED
BY LAW, JUNIPER SHALL NOT BE LIABLE FOR ANY LOST PROFITS, LOSS OF DATA, OR COSTS OR PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES,
OR FOR ANY SPECIAL, INDIRECT, OR CONSEQUENTIAL DAMAGES ARISING OUT OF THIS AGREEMENT, THE SOFTWARE, OR ANY JUNIPER OR
JUNIPER-SUPPLIED SOFTWARE. IN NO EVENT SHALL JUNIPER BE LIABLE FOR DAMAGES ARISING FROM UNAUTHORIZED OR IMPROPER USE OF ANY
JUNIPER OR JUNIPER-SUPPLIED SOFTWARE. EXCEPT AS EXPRESSLY PROVIDED IN THE WARRANTY STATEMENT TO THE EXTENT PERMITTED BY LAW,
JUNIPER DISCLAIMS ANY AND ALL WARRANTIES IN AND TO THE SOFTWARE (WHETHER EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE), INCLUDING
ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT DOES JUNIPER
WARRANT THAT THE SOFTWARE, OR ANY EQUIPMENT OR NETWORK RUNNING THE SOFTWARE, WILL OPERATE WITHOUT ERROR OR INTERRUPTION,
OR WILL BE FREE OF VULNERABILITY TO INTRUSION OR ATTACK. In no event shall Juniper’s or its suppliers’ or licensors’ liability to Customer, whether
in contract, tort (including negligence), breach of warranty, or otherwise, exceed the price paid by Customer for the Software that gave rise to the claim, or
if the Software is embedded in another Juniper product, the price paid by Customer for such other product. Customer acknowledges and agrees that Juniper
has set its prices and entered into this Agreement in reliance upon the disclaimers of warranty and the limitations of liability set forth herein, that the same
reflect an allocation of risk between the Parties (including the risk that a contract remedy may fail of its essential purpose and cause consequential loss),
and that the same form an essential basis of the bargain between the Parties.
9. Termination. Any breach of this Agreement or failure by Customer to pay any applicable fees due shall result in automatic termination of the license
granted herein. Upon such termination, Customer shall destroy or return to Juniper all copies of the Software and related documentation in Customer’s
possession or control.
10. Taxes. All license fees payable under this agreement are exclusive of tax. Customer shall be responsible for paying Taxes arising from the purchase of
the license, or importation or use of the Software. If applicable, valid exemption documentation for each taxing jurisdiction shall be provided to Juniper prior
to invoicing, and Customer shall promptly notify Juniper if their exemption is revoked or modified. All payments made by Customer shall be net of any
applicable withholding tax. Customer will provide reasonable assistance to Juniper in connection with such withholding taxes by promptly: providing Juniper
with valid tax receipts and other required documentation showing Customer’s payment of any withholding taxes; completing appropriate applications that
would reduce the amount of withholding tax to be paid; and notifying and assisting Juniper in any audit or tax proceeding related to transactions hereunder.
Customer shall comply with all applicable tax laws and regulations, and Customer will promptly pay or reimburse Juniper for all costs and damages related
to any liability incurred by Juniper as a result of Customer’s non-compliance or delay with its responsibilities herein. Customer’s obligations under this
Section shall survive termination or expiration of this Agreement.
11. Export. Customer agrees to comply with all applicable export laws and restrictions and regulations of any United States and any applicable foreign
agency or authority, and not to export or re-export the Software or any direct product thereof in violation of any such restrictions, laws or regulations, or
without all necessary approvals. Customer shall be liable for any such violations. The version of the Software supplied to Customer may contain encryption
or other capabilities restricting Customer’s ability to export the Software without an export license.
12. Commercial Computer Software. The Software is “commercial computer software” and is provided with restricted rights. Use, duplication, or disclosure
by the United States government is subject to restrictions set forth in this Agreement and as provided in DFARS 227.7201 through 227.7202-4, FAR 12.212,
FAR 27.405(b)(2), FAR 52.227-19, or FAR 52.227-14(ALT III) as applicable.
13. Interface Information. To the extent required by applicable law, and at Customer's written request, Juniper shall provide Customer with the interface
information needed to achieve interoperability between the Software and another independently created program, on payment of applicable fee, if any.
Customer shall observe strict obligations of confidentiality with respect to such information and shall use such information in compliance with any applicable
terms and conditions upon which Juniper makes such information available.
14. Third Party Software. Any licensor of Juniper whose software is embedded in the Software and any supplier of Juniper whose products or technology
are embedded in (or services are accessed by) the Software shall be a third party beneficiary with respect to this Agreement, and such licensor or vendor
shall have the right to enforce this Agreement in its own name as if it were Juniper. In addition, certain third party software may be provided with the
Software and is subject to the accompanying license(s), if any, of its respective owner(s). To the extent portions of the Software are distributed under and
subject to open source licenses obligating Juniper to make the source code for such portions publicly available (such as the GNU General Public License
(“GPL”) or the GNU Library General Public License (“LGPL”)), Juniper will make such source code portions (including Juniper modifications, as appropriate)
available upon request for a period of up to three years from the date of distribution. Such request can be made in writing to Juniper Networks, Inc., 1194
N. Mathilda Ave., Sunnyvale, CA 94089, ATTN: General Counsel. You may obtain a copy of the GPL at http://www.gnu.org/licenses/gpl.html, and
a copy of the LGPL at http://www.gnu.org/licenses/lgpl.html.
15. Miscellaneous. This Agreement shall be governed by the laws of the State of California without reference to its conflicts of laws principles. The provisions
of the U.N. Convention for the International Sale of Goods shall not apply to this Agreement. For any disputes arising under this Agreement, the Parties
hereby consent to the personal and exclusive jurisdiction of, and venue in, the state and federal courts within Santa Clara County, California. This Agreement
constitutes the entire and sole agreement between Juniper and the Customer with respect to the Software, and supersedes all prior and contemporaneous
iv ■
agreements relating to the Software, whether oral or written (including any inconsistent terms contained in a purchase order), except that the terms of a
separate written agreement executed by an authorized Juniper representative and Customer shall govern to the extent such terms are inconsistent or conflict
with terms contained herein. No modification to this Agreement nor any waiver of any rights hereunder shall be effective unless expressly assented to in
writing by the party to be charged. If any portion of this Agreement is held invalid, the Parties agree that such invalidity shall not affect the validity of the
remainder of this Agreement. This Agreement and associated documentation has been written in the English language, and the Parties agree that the English
version will govern. (For Canada: Les parties aux présentés confirment leur volonté que cette convention de même que tous les documents y compris tout
avis qui s'y rattaché, soient redigés en langue anglaise. (Translation: The parties confirm that this Agreement and all related documentation is and will be
in the English language)).
■ v
vi ■
Abbreviated Table of Contents
About the Documentation xxix
Part 1 Chapters
Chapter 1 Configuring ATM 3
Chapter 2 Configuring Frame Relay 107
Chapter 3 Configuring Multilink Frame Relay 133
Chapter 4 Configuring Upper-Layer Protocols over Static Ethernet Interfaces 153
Chapter 5 Configuring VLAN and S-VLAN Subinterfaces 169
Chapter 6 Configuring 802.3ad Link Aggregation and Link Redundancy 199
Chapter 7 Configuring IEEE 802.3ah OAM Link-Fault Management 227
Chapter 8 Configuring Point-to-Point Protocol 263
Chapter 9 Configuring Multilink PPP 303
Chapter 10 Configuring Multiclass Multilink PPP 349
Chapter 11 Configuring Packet over SONET 363
Chapter 12 Configuring Point-to-Point Protocol over Ethernet 375
Chapter 13 Configuring Bridged IP 437
Chapter 14 Configuring Bridged Ethernet 443
Chapter 15 Configuring Transparent Bridging 467
Chapter 16 Configuring Cisco HDLC 505
Chapter 17 Configuring Dynamic Interfaces 515
Chapter 18 Configuring Dynamic Interfaces Using Bulk Configuration 623
Part 2 Index
Index 717
Abbreviated Table of Contents ■ vii
JUNOSe 11.1.x Link Layer Configuration Guide
viii ■
Table of Contents
About the Documentation xxix
E Series and JUNOSe Documentation and Release Notes ............................xxix
Audience ....................................................................................................xxix
E Series and JUNOSe Text and Syntax Conventions ....................................xxix
Obtaining Documentation ..........................................................................xxxi
Documentation Feedback ...........................................................................xxxi
Requesting Technical Support .....................................................................xxxi
Self-Help Online Tools and Resources .................................................xxxii
Opening a Case with JTAC ...................................................................xxxii
Part 1 Chapters
Chapter 1 Configuring ATM 3
Overview .........................................................................................................3
ATM Interfaces ..........................................................................................4
ATM Physical Connections ........................................................................4
ATM Virtual Connections ..........................................................................5
Virtual Channel Connection ................................................................5
Virtual Path Connection ......................................................................5
ATM SVCs .................................................................................................5
ATM Adaptation Layer ..............................................................................5
Local ATM Passthrough .............................................................................6
VCC Cell Relay Encapsulation ...................................................................6
Traffic Management ..................................................................................7
Connection Admission Control ...........................................................7
ILMI ..........................................................................................................9
VPI/VCI Address Ranges ............................................................................9
VP Tunneling ..........................................................................................10
Platform Considerations ................................................................................10
Module Requirements .............................................................................10
Interface Specifiers .................................................................................11
References ....................................................................................................11
Supported Features .......................................................................................12
Module Capabilities .................................................................................12
Virtual Channel Support ..........................................................................13
Table of Contents ■ ix
JUNOSe 11.1.x Link Layer Configuration Guide
ATM NBMA ....................................................................................................13
ARP Table ...............................................................................................14
Operations, Administration, and Management of ATM Interfaces .................15
End-to-End and Segment Endpoints .......................................................15
Fault Management ..................................................................................15
Continuity Verification ............................................................................17
Loopback ................................................................................................18
Automatic Disabling of F5 OAM Services ................................................20
Rate Limiting for F5 OAM Cells ...............................................................21
Before You Configure ATM ............................................................................21
Configuration Tasks .......................................................................................22
Creating a Basic Configuration ......................................................................22
Setting Optional Parameters ..........................................................................24
Optional Tasks on ATM 1483 Subinterfaces ............................................26
Configuring OAM ...........................................................................................33
Configuring F4 OAM ...............................................................................33
Configuring F5 OAM ...............................................................................35
Setting a Loopback Location ID ...............................................................36
Enabling OAM Flush ...............................................................................37
Running ATM Ping ..................................................................................38
Configuring an NBMA Interface .....................................................................39
Creating an NBMA Static Map ........................................................................40
Assigning Descriptions to Interfaces ..............................................................42
Sending Interface Descriptions to AAA ..........................................................43
Assigning Descriptions to Virtual Paths ...................................................44
Exporting ATM 1483 Subinterface Descriptions ......................................44
Configuring Individual ATM PVC Parameters .................................................45
Benefits ...................................................................................................46
Creating Control PVCs .............................................................................46
Creating Data PVCs .................................................................................47
Configuring the Service Category for Data PVCs .....................................48
Configuring Encapsulation for Data PVCs ...............................................50
Configuring F5 OAM for Data PVCs ........................................................51
Configuring Inverse ARP for Data PVCs ..................................................54
Static Map Versus Inverse ARP .........................................................14
Aging ................................................................................................14
Removing Circuits ............................................................................15
How the ATM Interface Handles AIS Cells ........................................16
How the ATM Interface Handles RDI Cells ........................................16
Activation and Deactivation Cells .....................................................17
Activating CC Cell Flow ....................................................................17
Deactivating CC Cell Flow .................................................................17
After CC Cell Flow Is Enabled ...........................................................18
VC Integrity ......................................................................................18
F4 OAM Cells ....................................................................................19
ATM Ping ..........................................................................................19
How the ATM Interface Handles Loopback Cells Received ................20
x ■ Table of Contents
Table of Contents
Configuring ATM VC Classes ..........................................................................55
Benefits ...................................................................................................55
Precedence Levels ..................................................................................56
Precedence Levels for Static PVCs ....................................................56
Precedence Levels for Dynamic PVCs ...............................................57
Precedence Level Examples .............................................................57
Upgrade Considerations ..........................................................................57
Configuring VC Classes ...........................................................................59
Assigning VC Classes to Individual PVCs .................................................64
Assigning VC Classes to ATM Major Interfaces ........................................65
Assigning VC Classes to Static ATM 1483 Subinterfaces ..........................66
Assigning VC Classes to Base Profiles for Bulk-Configured VC
Ranges .............................................................................................67
Precedence Level Examples for Assigning VC Classes .............................67
Example 1: Explicitly Changing the Service Category .......................67
Example 2: Changing the Encapsulation Method in the VC Class .....68
Example 3: Effect of Using the atm pvc Command ..........................68
Example 4: Overriding RADIUS Values .............................................68
Configuring Dynamic ATM 1483 Subinterfaces .............................................69
Monitoring ATM ............................................................................................69
Setting Statistics Baselines ......................................................................70
Displaying Interface Rate Statistics for ATM VCs and ATM VPs ...............70
Using ATM show Commands ..................................................................74
Chapter 2 Configuring Frame Relay 107
Overview .....................................................................................................107
Framing ................................................................................................107
Error Frames ........................................................................................108
Unicast and Multicast Addressing .........................................................108
User-to-Network and Network-to-Network Interfaces ............................108
Platform Considerations ..............................................................................109
Module Requirements ...........................................................................109
Interface Specifiers ...............................................................................110
References ..................................................................................................110
Before You Configure Frame Relay ..............................................................110
Configuring Frame Relay .............................................................................111
End-to-End Fragmentation and Reassembly ................................................119
Frame Fragmentation ...........................................................................119
Frame Reassembly ...............................................................................119
Map Class .............................................................................................120
Configuring End-to-End Fragmentation .................................................120
Monitoring Frame Relay ..............................................................................123
Chapter 3 Configuring Multilink Frame Relay 133
Overview .....................................................................................................133
T1/E1 Connections ................................................................................133
MLFR Link Integrity Protocol ................................................................134
Table of Contents ■ xi
JUNOSe 11.1.x Link Layer Configuration Guide
Interface Stacking .................................................................................135
Platform Considerations ..............................................................................135
Module Requirements ...........................................................................136
Interface Specifiers ...............................................................................136
References ..................................................................................................136
Supported MLFR Features ...........................................................................136
Unsupported MLFR Features .......................................................................137
Before You Configure MLFR ........................................................................138
Configuration Tasks .....................................................................................138
Configuration Example .........................................................................139
Configuring Frame Relay Versus MLFR .................................................139
Monitoring MLFR .........................................................................................140
Chapter 4 Configuring Upper-Layer Protocols over Static Ethernet
Interfaces 153
Upper-Layer Protocols over Static Ethernet Overview .................................153
Upper-Layer Protocols over Static Ethernet Platform Considerations ...........154
Module Requirements ...........................................................................155
Interface Specifiers ...............................................................................155
Upper-Layer Protocols over Static Ethernet References ...............................155
Configuring IP over a Static Ethernet Interface ............................................155
Configuring PPPoE over a Static Ethernet Interface .....................................156
Configuring IP and MPLS over a Static Ethernet Interface ...........................157
Configuring IP, MPLS, and PPPoE over Ethernet .........................................157
L2TP and Ethernet ......................................................................................159
Multinetting and Ethernet ............................................................................159
Monitoring Upper-Level Protocols over Ethernet .........................................159
Chapter 5 Configuring VLAN and S-VLAN Subinterfaces 169
VLAN Overview ...........................................................................................169
S-VLAN Overview ........................................................................................170
VLAN and S-VLAN Platform Considerations .................................................171
Module Requirements ...........................................................................171
Interface Specifiers ...............................................................................171
VLAN and S-VLAN References .....................................................................172
Creating a VLAN Subinterface .....................................................................172
Creating a VLAN Major Interface ...........................................................172
Configuring IP over VLAN .....................................................................173
Configuring PPPoE over VLAN ..............................................................174
Configuring MPLS over VLAN ................................................................175
Configuring IP over VLAN and PPPoE over VLAN ..................................176
Configuring an S-VLAN Subinterface ...........................................................180
Configuring an S-VLAN Subinterface .....................................................181
Configuring PPPoE over an S-VLAN ......................................................181
Configuring S-VLAN Tunnels for Layer 2 Services over MPLS ......................184
Advantages ...........................................................................................184
Interface Stacking .................................................................................185
Configuration Example .........................................................................185
xii ■ Table of Contents
Table of Contents
S-VLAN Oversubscription ............................................................................188
Monitoring VLAN and S-VLAN Subinterfaces ...............................................188
Displaying Interface Rate Statistics for VLAN Subinterfaces ..................189
Using Ethernet show Commands ..........................................................191
Chapter 6 Configuring 802.3ad Link Aggregation and Link Redundancy 199
802.3ad Link Aggregation for Ethernet Overview ........................................199
LACP .....................................................................................................200
Higher-Level Protocols ..........................................................................200
Load Balancing and QoS .......................................................................201
Ethernet Link Aggregation and MPLS ....................................................201
802.3ad Link Aggregation Platform Considerations .....................................201
Module Requirements ...........................................................................201
Interface Specifiers ...............................................................................202
802.3ad Link Aggregation References .........................................................202
Configuring 802.3ad Link Aggregation ........................................................202
Configuring an Ethernet Physical Interface ...........................................203
Configuring a LAG Bundle .....................................................................203
Configuring IP for a LAG Bundle ...........................................................204
Configuring a VLAN Subinterface for a LAG Bundle ...............................204
Configuring a PPPoE Subinterface for a LAG Bundle .............................204
Configuring MPLS for a LAG Bundle ......................................................205
Example: Configuring an IP Interface for a LAG Bundle ...............................207
Example: Configuring a PPPoE Subinterface for a LAG Bundle ....................208
Example: Configuring a PPPoE Subinterface over a VLAN for a LAG
Bundle ..................................................................................................209
Example: Configuring MPLS for a LAG Bundle .............................................209
Example: Configuring MPLS over a VLAN for a LAG Bundle ........................210
Ethernet Link Redundancy Overview ..........................................................211
Ethernet Link Redundancy Configuration Models .................................211
Ethernet Link Redundancy Configuration Diagrams .......................212
Ethernet Link Redundancy Behavior ...........................................................215
Link Failure and Acquisition ..................................................................216
Protecting Against Physical Link Failure .........................................216
Protecting Against Virtual Link Failure ............................................216
Reverting After a Failover ...............................................................217
LACP Configuration and Member Link Behavior ...................................217
Member Link with Non-LAG Partner .....................................................218
Ethernet Link Redundancy and RSTP .............................................218
Acquiring Initial Links .....................................................................219
Detecting Failures ...........................................................................219
Failing Over ....................................................................................220
Configuring Ethernet Link Redundancy .......................................................220
Monitoring 802.3ad Link Aggregation .........................................................222
Table of Contents ■ xiii
JUNOSe 11.1.x Link Layer Configuration Guide
Chapter 7 Configuring IEEE 802.3ah OAM Link-Fault Management 227
Ethernet OAM Link-Fault Management Overview ........................................228
Ethernet OAM Link-Fault Management Platform Considerations .................229
Module Requirements ...........................................................................229
Interface Specifiers ...............................................................................229
Ethernet OAM Link-Fault Management References .....................................230
OAM Messages ............................................................................................230
OAM Elements Overview ............................................................................231
OAM Client ..................................................................................................232
OAM Sublayer .............................................................................................232
Control Block ........................................................................................233
Multiplexer ............................................................................................233
Parser ...................................................................................................233
OAM Feature Overview ...............................................................................234
OAM Discovery Feature ...............................................................................234
Information OAM PDU Components .....................................................235
Transmission Settings for Information OAM PDUs ................................235
OAM Link Monitoring Feature .....................................................................236
Supported Error Events for Tracking Link Faults ...................................237
Actions Performed on Exceeding Threshold Values ..............................237
OAM Remote Fault Detection Feature .........................................................238
Link Fault ..............................................................................................238
Dying Gasp ...........................................................................................239
Critical Event ........................................................................................239
OAM Remote and Local Loopback Feature ..................................................240
Interrelationship of OAM Link-Fault Management with Ethernet
Subsystems ...........................................................................................240
Guidelines for Configuring 802.3ah OAM Link-Fault Management ...............242
Configuring 802.3ah OAM Link-Fault Management .....................................242
Example: Configuring 802.3ah OAM Link-Fault Management and Enabling
Remote Failure Monitoring on an Interface ...........................................249
Example: Enabling Remote Loopback Support on the Local Interface .........250
Monitoring OAM Link-Fault Management Discovery Settings for an
Interface ...............................................................................................250
Monitoring OAM Link-Fault Management Statistics for an Interface ............253
Monitoring OAM Link-Fault Management Configuration for an Interface .....255
Monitoring OAM Link-Fault Management Sessions on All Configured
Interfaces ..............................................................................................258
Chapter 8 Configuring Point-to-Point Protocol 263
Overview .....................................................................................................263
Framing ................................................................................................263
Error Frames ........................................................................................264
Link Control Protocol ............................................................................264
LCP Negotiation Parameters ...........................................................264
Validation of LCP Peer Magic Number ............................................265
B-RAS Support ......................................................................................266
xiv ■ Table of Contents
Table of Contents
Authentication ......................................................................................267
Rate Limiting for PPP Control Packets ..................................................267
Extensible Authentication Protocol .......................................................267
EAP Types ......................................................................................268
EAP Packet Retransmission ............................................................268
EAP Behavior in an L2TP Environment ..........................................269
Limitations .....................................................................................270
Performance ..................................................................................270
Remote Peer Scenarios During Negotiation of PPP Options ..................271
IPCP Lockout and Local IP Address Pool Restoration ............................272
Platform Considerations ..............................................................................273
Module Requirements ...........................................................................273
Interface Specifiers ...............................................................................273
References ..................................................................................................274
Before You Configure PPP ...........................................................................275
Configuration Tasks .....................................................................................275
Optional Configuration Tasks ......................................................................278
Configuring PPP Authentication ............................................................283
PPP Accounting Statistics ............................................................................285
Monitoring PPP Interfaces ...........................................................................286
Troubleshooting ..........................................................................................300
Chapter 9 Configuring Multilink PPP 303
Overview .....................................................................................................303
Application ...........................................................................................304
MLPPP LCP Extensions .........................................................................304
MLPPP Link Selection ...........................................................................305
Platform Considerations ..............................................................................306
Module Requirements ...........................................................................307
Interface Specifiers ...............................................................................307
References ..................................................................................................307
Supported MLPPP Features .........................................................................308
Unsupported MLPPP Features .....................................................................312
Before You Configure Static MLPPP .............................................................312
Configuring Static MLPPP ............................................................................312
Configuration Example .........................................................................314
Contextual Command Differences ........................................................314
Configuring Authentication ...................................................................315
Configuring Other PPP Attributes ..........................................................317
Configuring Dynamic MLPPP ......................................................................323
Configuring MLPPP Fragmentation and Reassembly ...................................324
Overview ..............................................................................................324
Application .....................................................................................325
Supported Configurations ...............................................................325
Module Requirements ....................................................................325
Link Configuration Parameters .......................................................325
Bundle Validation and Configuration Guidelines .............................326
Bundle Validation Failure ................................................................327
Table of Contents ■ xv
JUNOSe 11.1.x Link Layer Configuration Guide
Recovering from Bundle Validation Failure .....................................327
Configuring Fragmentation and Reassembly for Static MLPPP ..............327
Static MLPPP over ATM 1483 Example ..........................................328
Configuring Fragmentation and Reassembly for Dynamic MLPPP ........329
Dynamic MLPPP over PPPoE Example ...........................................330
Dynamic MLPPP over L2TP Example .............................................330
Configuring Fragmentation and Reassembly for MLPPP Bundles ..........333
Configuring Multiclass MLPPP .....................................................................333
Monitoring MLPPP .......................................................................................333
Chapter 10 Configuring Multiclass Multilink PPP 349
Multiclass MLPPP Overview .........................................................................349
Multiclass MLPPP Fragmentation and Reassembly ...............................349
Multiclass MLPPP Configuration Guidelines ...........................................350
Multiclass MLPPP Traffic Classes Overview .................................................350
Multiclass MLPPP LCP Extensions Overview ................................................351
Multiclass MLPPP Platform Considerations ..................................................351
Module Requirements ...........................................................................352
Interface Specifiers ...............................................................................352
Multiclass MLPPP References ......................................................................352
Configuring Multiclass MLPPP .....................................................................352
Enabling Multiclass MLPPP ..........................................................................353
Configuring Traffic Classes on Multiclass MLPPP Interfaces .........................354
Configuring Fragmentation on Multiclass MLPPP Interfaces ........................355
Configuring Reassembly on Multiclass MLPPP Interfaces ............................355
Example: Configuring Multiclass MLPPP on a Dynamic Interface ................356
Example: Configuring Multiclass MLPPP on a Static Interface ......................357
Monitoring Multiclass MLPPP ......................................................................358
Chapter 11 Configuring Packet over SONET 363
Overview .....................................................................................................363
POS Features ........................................................................................363
SONET/SDH ..........................................................................................364
Platform Considerations ..............................................................................364
Module Requirements ...........................................................................365
Interface Specifiers ...............................................................................365
References ..................................................................................................365
Before You Configure POS ...........................................................................366
Configuration Tasks .....................................................................................366
Monitoring POS ...........................................................................................371
xvi ■ Table of Contents
Table of Contents
Chapter 12 Configuring Point-to-Point Protocol over Ethernet 375
Overview .....................................................................................................375
PPPoE Stages ........................................................................................376
Discovery .......................................................................................376
Session ...........................................................................................377
PPPoE Service Name Tables .................................................................377
Features .........................................................................................378
Table Structure ...............................................................................378
Enabling the Service Name Table for Use .......................................379
Using the PPPoE Remote Circuit ID to Identify Subscribers ..................379
Application .....................................................................................379
PPPoE Remote Circuit ID Capture ..................................................380
PPPoE Remote Circuit ID Format ...................................................380
Use by RADIUS or L2TP .................................................................383
System Event Log ...........................................................................384
PPPoE MTU Configuration ....................................................................384
Platform Considerations ..............................................................................384
Module Requirements ...........................................................................385
Interface Specifiers ...............................................................................385
References ..................................................................................................386
Before You Configure PPPoE .......................................................................386
Configuring PPPoE over ATM ......................................................................386
Configuring PPPoE for Ethernet Modules .....................................................393
PPPoE Interface and Subinterface Limits ..............................................393
Configuring IPv4 and IPv6 over PPPoE with VLAN ................................393
Configuring PPPoE Without VLANs .......................................................397
Configuring PADM Messages .......................................................................401
Configuring PADN Messages .......................................................................403
Configuring PPPoE Service Name Tables .....................................................404
Creating and Populating PPPoE Service Name Tables ...........................404
Enabling PPPoE Service Name Tables for Use with Static Interfaces .....407
PPPoE over ATM Configurations .....................................................407
PPPoE over Ethernet Configurations ..............................................409
Enabling PPPoE Service Name Tables for Use with Dynamic
Interfaces .......................................................................................410
Configuring PADS Packet Content ...............................................................412
Configuring PPPoE Remote Circuit ID Capture ............................................413
Monitoring PPPoE .......................................................................................419
Troubleshooting ..........................................................................................434
Chapter 13 Configuring Bridged IP 437
Overview .....................................................................................................437
Proxy ARP ............................................................................................437
DHCP ....................................................................................................438
Platform Considerations ..............................................................................438
Module Requirements ...........................................................................438
Interface Specifiers ...............................................................................439
Table of Contents ■ xvii
JUNOSe 11.1.x Link Layer Configuration Guide
References ..................................................................................................439
Before You Configure Bridged IP .................................................................439
Configuring Bridged IP ................................................................................440
Chapter 14 Configuring Bridged Ethernet 443
Overview .....................................................................................................443
Bridged Ethernet Application ................................................................444
Assigning MAC Addresses .....................................................................444
VLAN and S-VLAN Configurations .........................................................445
Platform Considerations ..............................................................................446
Module Requirements ...........................................................................446
Interface Specifiers ...............................................................................447
References ..................................................................................................447
Configuring Bridged Ethernet ......................................................................447
Configuring IP with PPPoE Terminated at the Router ............................447
Alternative Configuration ......................................................................452
Configuring VLANs over Bridged Ethernet ...................................................453
Configuring VLAN Subinterfaces over Bridged Ethernet ........................453
Configuring Higher-Level Protocols over VLANs ....................................454
Configuring IP over VLAN ...............................................................454
Configuring PPPoE over VLAN ........................................................454
Configuring MPLS over VLAN .........................................................455
Configuring S-VLANs over Bridged Ethernet ................................................458
Configuring S-VLAN Subinterfaces over Bridged Ethernet .....................458
Configuring Higher-Level Protocols over S-VLANs .................................460
Configuring the MTU Size for Bridged Ethernet ...........................................460
Monitoring Bridged Ethernet .......................................................................461
Chapter 15 Configuring Transparent Bridging 467
Overview .....................................................................................................467
How Transparent Bridging Works .........................................................467
Bridge Groups and Bridge Group Interfaces ..........................................468
Bridge Interface Types and Supported Configurations ...........................469
Subscriber Policies ................................................................................470
Concurrent Routing and Bridging ..........................................................471
Transparent Bridging and VPLS ............................................................472
Unsupported Features ...........................................................................472
Platform Considerations ..............................................................................472
Module Requirements ...........................................................................472
Interface Specifiers ...............................................................................473
References ..................................................................................................473
Before You Configure Transparent Bridging ................................................473
Configuration Tasks .....................................................................................474
Creating Bridge Groups .........................................................................475
Configuring Optional Bridge Group Attributes .......................................476
Configuring Bridge Group Interfaces .....................................................478
Configuring Subscriber Policies .............................................................480
Enabling Concurrent Routing and Bridging ...........................................486
xviii ■ Table of Contents
Table of Contents
Configuring Explicit Routing .................................................................486
Configuration Examples ..............................................................................488
Example 1: Bridging with Bridged Ethernet ..........................................488
Example 2: Bridging with VLANs ..........................................................489
Monitoring Transparent Bridging .................................................................490
Setting Statistics Baselines ....................................................................491
Removing Dynamic MAC Address Entries ............................................492
Monitoring Bridge Groups .....................................................................493
Monitoring Bridge Interfaces .................................................................500
Monitoring Subscriber Policies ..............................................................502
Chapter 16 Configuring Cisco HDLC 505
Overview .....................................................................................................505
Framing ................................................................................................505
Error Frames ........................................................................................506
SLARP Keepalive ...................................................................................506
Platform Considerations ..............................................................................506
Module Requirements ...........................................................................506
Interface Specifiers ...............................................................................507
Before You Configure Cisco HDLC ...............................................................507
Configuration Tasks .....................................................................................507
Optional Tasks ......................................................................................508
Configuration Example .........................................................................510
Monitoring Cisco HDLC ...............................................................................511
Chapter 17 Configuring Dynamic Interfaces 515
Overview .....................................................................................................515
Autodetection .......................................................................................516
Types of Dynamic Interfaces ................................................................516
Upper-Layer Dynamic Interface Configurations ....................................517
Profiles .................................................................................................518
RADIUS Authentication .........................................................................518
ATM Oversubscription for Dynamic Interfaces .....................................519
How Oversubscription Works .........................................................519
Static ATM 1483 Subinterfaces .......................................................519
Bulk-Configured VC Ranges ............................................................520
Combination of Static ATM 1483 Subinterfaces and Bulk-Configured
VC Ranges ...............................................................................520
Ethernet Oversubscription for Dynamic Interfaces ...............................521
Platform Considerations ..............................................................................521
Module Requirements ...........................................................................521
Interface Specifiers ...............................................................................521
References ..................................................................................................522
About Configuring Dynamic Interfaces over Static ATM ..............................522
About Configuring RADIUS for Dynamic Interfaces ...............................523
subscriber Command .....................................................................523
Authenticating Subscribers on Dynamic Bridged Ethernet over Static
ATM Interfaces .........................................................................523
Table of Contents ■ xix
JUNOSe 11.1.x Link Layer Configuration Guide
auto-configure Command .....................................................................525
atm pvc Command ...............................................................................528
Configuring PPP and PPPoE Dynamic Interfaces over Static ATM ...............528
Configuring a PPP or PPPoE Dynamic Interface ....................................529
Terminating Stale PPPoA Subscribers and Restarting LCP
Configuring PPPoE Dynamic Interfaces over PPPoE Static Interfaces ..........534
Configuring Dynamic PPPoE over Static PPPoE with ATM Interface
Configuring Dynamic PPPoE over Static PPPoE with Ethernet Interface
Configuring Dynamic PPPoE over Static PPPoE with Ethernet and VLAN
Configuring IPv4 and IPv6 over Static and Dynamic PPPoE ..................538
Configuring Dynamic PPPoE over Static PPPoE with Ethernet and S-VLAN
Configuring Encapsulation Type Lockout for PPPoE Clients ..................548
Configuring IPoA Dynamic Interfaces ..........................................................553
Configuring a Dynamic IPoA Interface ..................................................554
Configuring Bridged Ethernet Dynamic Interfaces .......................................557
Configuring a Dynamic Bridged Ethernet Interface ...............................558
Configuring Subscriber Management for IP Subscribers on Dynamic
Configuring a Dynamic Interface from a Profile ..........................................563
Profile Considerations ...........................................................................563
Profile Characteristics ...........................................................................564
Working with Profiles ...........................................................................568
Configuring a Profile .............................................................................569
Assigning a Profile to an Interface .........................................................594
Profile Configuration Examples .............................................................597
Scripts and Macros ......................................................................................598
Monitoring Upper-Layer Dynamic Interfaces and Profiles ............................599
Troubleshooting PPP and PPPoE Dynamic Interfaces ..................................619
Placing Dynamic IP Routes in the Routing Table ............................525
Encapsulation Type Lockout ...........................................................525
Negotiations ...................................................................................533
Columns .........................................................................................534
Columns .........................................................................................535
Interface Columns ..........................................................................536
Interface Columns ..........................................................................542
S-VLAN Oversubscription ...............................................................544
Differences from Lockout Configuration for PPPoE over Static
ATM .........................................................................................548
Configuration Tasks ........................................................................549
Configuring and Verifying Lockout for PPPoE Clients .....................549
Clearing the Lockout Condition for a PPPoE Client .........................551
Bridged Ethernet Interfaces ............................................................561
Configuration Example Using subscriber Command .......................561
Equivalent Configuration Example Using IP Subscriber
Management ............................................................................562
Bridged Ethernet Characteristics ....................................................564
IP Characteristics ............................................................................564
IPv6 Characteristics ........................................................................565
L2TP Characteristics .......................................................................566
MLPPP and PPP Characteristics ......................................................566
PPPoE Characteristics .....................................................................567
VLAN Characteristics ......................................................................567
xx ■ Table of Contents
Table of Contents
Chapter 18 Configuring Dynamic Interfaces Using Bulk Configuration 623
Overview .....................................................................................................623
Bulk Dynamic Interface Configurations .................................................624
Profiles .................................................................................................624
ATM Oversubscription for Bulk-Configured VC Ranges .........................625
Bulk-Configured VC Ranges ............................................................625
Combination of Static ATM 1483 Subinterfaces and Bulk-Configured
VC Ranges ...............................................................................626
Platform Considerations ..............................................................................627
Module Requirements ...........................................................................627
Interface Specifiers ...............................................................................627
References ..................................................................................................628
Configuring ATM 1483 Dynamic Subinterfaces ...........................................628
About Configuring Dynamic ATM 1483 Subinterfaces ..........................629
Overview and Benefits ...................................................................629
ATM 1483 Base Profiles ..................................................................630
Nested Profile Assignments ............................................................630
Additional Profile Characteristics for Upper Interfaces ....................631
Bulk Configuration of VC Ranges ....................................................631
Bulk Configuration and VC Classes .................................................632
Bulk Configuration and CAC ...........................................................633
Dynamic Interface Creation ............................................................633
Overriding Base Profile Assignments ..............................................634
Changing VC Subranges .................................................................634
Static ATM Interfaces Within VC Subranges ....................................634
Terminating Stale PPPoA Subscribers and Restarting LCP
Negotiations .............................................................................635
Authenticating Subscribers on Dynamic Bridged Ethernet over
Dynamic ATM Interfaces ..........................................................636
Configuring a Dynamic ATM 1483 Subinterface ...................................637
Configuring Overriding Profile Assignments .........................................646
Assigning an Overriding Profile to an ATM PVC .............................646
Removing an Overriding Profile Assignment from an ATM PVC .....648
Removing Overriding Profile Assignments from a VC Range or
VC Subrange ............................................................................648
Changing VC Subranges ........................................................................651
Adding VC Subranges .....................................................................651
Removing VC Subranges ................................................................652
Modifying VC Subranges ................................................................652
Merging VC Subranges ...................................................................653
Changing the Administrative State of VC Subranges .......................654
Configuring Static ATM Interfaces Within VC Subranges .......................656
Creating Static ATM Interfaces Within VC Subranges .....................656
Creating VC Subranges That Include Static ATM Interfaces .............657
Configuring VLAN Dynamic Subinterfaces ...................................................658
About Configuring Dynamic VLAN Subinterfaces ..................................660
Overview and Benefits ...................................................................660
VLAN Base Profiles .........................................................................661
Table of Contents ■ xxi
JUNOSe 11.1.x Link Layer Configuration Guide
Configuring a Dynamic VLAN Subinterface ...........................................667
Configuring Dynamic VLAN Subinterfaces Based on Agent Circuit
Configuring Overriding Profile Assignments for VLAN Major
Changing VLAN Subranges ....................................................................680
Configuring Static VLAN Subinterfaces Within VLAN Subranges ...........686
Monitoring Dynamic Interfaces and Profiles ................................................689
Nested Profile Assignments ............................................................662
Additional Profile Characteristics for Upper Interfaces ....................663
Bulk Configuration of VLAN Ranges ................................................663
Bulk Configuration of VLAN Ranges Using Agent-Circuit-Identifier
Information ..............................................................................664
Dynamic Interface Creation ............................................................665
Overriding Base Profile Assignments ..............................................666
Changing VLAN Subranges .............................................................666
Static VLAN Subinterfaces Within VLAN Subranges ........................667
Identifier Information .....................................................................669
Interfaces .......................................................................................670
Removing an Overriding Profile Assignment from a VLAN .............671
Removing Overriding Profile Assignments from a VLAN Range or
VLAN Subrange ........................................................................672
Adding VLAN Subranges .................................................................681
Removing VLAN Subranges ............................................................681
Modifying VLAN Subranges ............................................................682
Merging VLAN Subranges ...............................................................683
Changing the Administrative State of VLAN Subranges ..................684
Creating Static VLAN Subinterfaces Within VLAN Subranges ..........686
Creating VLAN Subranges That Include Static VLAN
Subinterfaces ...........................................................................687
Part 2 Index
Index ...........................................................................................................717
xxii ■ Table of Contents
List of Figures
Part 1 Chapters
Chapter 1 Configuring ATM 3
Figure 1: ATM Interface Column ......................................................................4
Figure 2: NBMA Interface Stack .....................................................................14
Figure 3: Configuring an ATM Interface, Subinterface, and PVC ....................23
Chapter 2 Configuring Frame Relay 107
Figure 4: Interconnection and Relationship of NNIs and Subnetworks ........109
Chapter 3 Configuring Multilink Frame Relay 133
Figure 5: MLFR Aggregation of T1 Lines into a Single Bundle ......................134
Figure 6: Terminating the Bundle at an MLFR Bridge ..................................134
Figure 7: Structure of MLFR .........................................................................135
Chapter 4 Configuring Upper-Layer Protocols over Static Ethernet Interfaces 153
Figure 8: Multiplexing Multiple Protocols over a Single Physical Link ..........154
Figure 9: Example of IP over Ethernet Stacking Configuration Procedure ....156
Figure 10: Example of PPPoE Stacking Configuration Procedure .................157
Figure 11: Example of IP and MPLS Stacking Configuration Procedure .......157
Figure 12: Example of IP, MPLS, and PPPoE Stacking Configuration
Procedure .............................................................................................158
Chapter 5 Configuring VLAN and S-VLAN Subinterfaces 169
Figure 13: Use of VLANs to Multiplex Different Protocols over a Single Physical
Link ......................................................................................................170
Figure 14: Example of IP/VLAN/Fast Ethernet Stacking Configuration
Procedure .............................................................................................174
Figure 15: Example of PPPoE/VLAN/Fast Ethernet Stacking Configuration
Procedure .............................................................................................175
Figure 16: Example of MPLS/VLAN/Fast Ethernet Stacking Configuration
Procedure .............................................................................................176
Figure 17: Example of PPPoE over VLAN with IP over VLAN Stacking
Configuration Procedure .......................................................................178
Figure 18: Example of PPPoE over S-VLAN Stacking Configuration
Procedure .............................................................................................182
Figure 19: S-VLAN Tunnels for Ethernet Layer 2 Services over MPLS ..........185
Chapter 6 Configuring 802.3ad Link Aggregation and Link Redundancy 199
Figure 20: Interface Stack for 802.3ad Link Aggregation .............................200
Figure 21: Ethernet Link Redundancy Configuration Models .......................212
Figure 22: GE-2 Line Module Using Physical Port Redundancy ....................213
Figure 23: Single-Homed GE-2 Line Module Configuration ..........................213
Figure 24: Single-Homed FE-8 Line Module Configuration (1:N) ..................213
Figure 25: FE-8 Line Module with 4 Redundant Ethernet Links (1:1) ...........214
Figure 26: Single-Homed GE-4 IOA Configuration (1:4) ...............................214
List of Figures ■ xxiii
JUNOSe 11.1.x Link Layer Configuration Guide
Figure 27: GE-8 IOA Configuration Across IOAs (1:N) ..................................215
Figure 28: Dual-Homed Configuration (1:1) .................................................215
Figure 29: Dual-Homed Heterogeneous Configuration in an RSTP
Network ................................................................................................219
Chapter 7 Configuring IEEE 802.3ah OAM Link-Fault Management 227
Figure 30: OAM PDU Format .......................................................................230
Figure 31: OAM Sublayer Interfaces ............................................................232
Figure 32: OAM Sublayer Entities ................................................................233
Figure 33: Interrelationship Between 802.3ah OAM and 802.3ad LAG ........241
Chapter 8 Configuring Point-to-Point Protocol 263
Figure 34: Authentication with EAP .............................................................267
Chapter 9 Configuring Multilink PPP 303
Figure 35: MLPPP Aggregation of T1 Lines into a Single Bundle ..................304
Figure 36: Structure of MLPPP .....................................................................304
Chapter 12 Configuring Point-to-Point Protocol over Ethernet 375
Figure 37: PPPoE over ATM .........................................................................376
Figure 38: Example of PPPoE over ATM Stacking ........................................389
Figure 39: Example of Configuring IPv4 and IPv6 over PPPoE ....................394
Figure 40: Example of PPPoE Stacking ........................................................398
Chapter 14 Configuring Bridged Ethernet 443
Figure 41: Bridged Ethernet Topology, Router Terminating and Routing
Traffic ...................................................................................................444
Figure 42: Interface Stacking for VLANs over Bridged Ethernet ...................445
Chapter 15 Configuring Transparent Bridging 467
Figure 43: Bridge Group with Fast Ethernet and Gigabit Ethernet Bridge
Interfaces ..............................................................................................469
Chapter 17 Configuring Dynamic Interfaces 515
Figure 44: Configuring an ATM 1483 Interface to Support Dynamic
Interfaces ..............................................................................................522
Figure 45: Dynamic PPP Interface Columns ................................................529
Figure 46: Dynamic PPPoE Interface Columns ............................................529
Figure 47: Dynamic PPPoE over Static PPPoE with ATM Interface
Columns ...............................................................................................534
Figure 48: Dynamic PPPoE over Static PPPoE with Non-VLAN Interface
Columns ...............................................................................................536
Figure 49: Dynamic PPPoE over Static PPPoE with VLAN Interface
Columns ...............................................................................................537
Figure 50: IPv4 and IPv6 Interface Columns over Static and Dynamic
PPPoE ...................................................................................................538
Figure 51: Dynamic PPPoE over Static PPPoE with S-VLAN Interface
Columns ...............................................................................................543
Figure 52: Dynamic IPoA over Static ATM 1483 Interface Columns ............553
Figure 53: Dynamic Bridged Ethernet over Static ATM 1483 Interface
Columns ...............................................................................................558
Figure 54: Creating and Configuring a Profile ..............................................568
Figure 55: Assigning a Profile to a Static Interface .......................................569
Chapter 18 Configuring Dynamic Interfaces Using Bulk Configuration 623
xxiv ■ List of Figures
List of Figures
Figure 56: Dynamic Interface Columns over Dynamic ATM 1483
Subinterfaces ........................................................................................629
Figure 57: Dynamic Interface Columns over Dynamic VLAN
Subinterfaces ........................................................................................659
Figure 58: Dynamic IP and PPPoE over Single Dynamic VLAN
Subinterface ..........................................................................................659
Figure 59: Dynamic VLAN Subinterfaces for Subscribers .............................661
List of Figures ■ xxv
JUNOSe 11.1.x Link Layer Configuration Guide
xxvi ■ List of Figures
List of Tables
About the Documentation xxix
Table 1: Notice Icons ...................................................................................xxx
Table 2: Text and Syntax Conventions ........................................................xxx
Part 1 Chapters
Chapter 1 Configuring ATM 3
Table 3: Scheduling Priorities for Traffic Classes ..............................................7
Table 4: Traffic Parameters Used to Compute Bandwidth ................................8
Table 5: ATM Capabilities on Line Modules and I/O Modules .........................12
Table 6: Handling of F4 and F5 Loopback Cells Received ..............................20
Table 7: F5 OAM Configuration Tasks and Associated Commands ................51
Table 8: Commands to Configure VC Class Attributes ...................................59
Chapter 3 Configuring Multilink Frame Relay 133
Table 9: LIP Messages and Functions ..........................................................134
Chapter 6 Configuring 802.3ad Link Aggregation and Link Redundancy 199
Table 10: Behavior of Member Links Using Local and Remote LACP
Modes ...................................................................................................218
Chapter 7 Configuring IEEE 802.3ah OAM Link-Fault Management 227
Table 11: show ethernet oam lfm discovery Output Fields ..........................251
Table 12: show ethernet oam lfm statistics Output Fields ............................254
Table 13: show ethernet oam lfm status Output Fields ................................256
Table 14: show ethernet oam lfm summary Output Fields ..........................259
Chapter 8 Configuring Point-to-Point Protocol 263
Table 15: Supported EAP Types ..................................................................268
Chapter 9 Configuring Multilink PPP 303
Table 16: Supported Configurations for MLPPP Fragmentation and
Reassembly ..........................................................................................325
Chapter 10 Configuring Multiclass Multilink PPP 349
Table 17: show ppp interface mlppp Output Fields .....................................359
Chapter 11 Configuring Packet over SONET 363
Table 18: Most Common SONET/SDH Implementations ..............................364
Chapter 12 Configuring Point-to-Point Protocol over Ethernet 375
Table 19: Sample PPPoE Service Name Table .............................................378
Table 20: Configuring Nondefault Formats for the PPPoE Remote Circuit
ID .........................................................................................................380
Table 21: Interface Specifier Format Examples for dsl-forum-1 Keyword ....382
Table 22: Default PPPoE Service Name Table ..............................................404
Table 23: PPPoE Service Name Table with Entries ......................................405
List of Tables ■ xxvii
JUNOSe 11.1.x Link Layer Configuration Guide
Chapter 13 Configuring Bridged IP 437
Table 24: Prerequisite Tasks for Configuring Bridged IP ..............................440
Chapter 15 Configuring Transparent Bridging 467
Table 25: Sample Bridge Group Forwarding Table .......................................469
Table 26: Default Subscriber Policies for Bridge Group Interfaces ................470
Table 27: Prerequisite Tasks for Configuring Transparent Bridging .............474
Chapter 17 Configuring Dynamic Interfaces 515
Table 28: Differences in Lockout Operation for Dynamic PPPoE
Configurations ......................................................................................549
xxviii ■ List of Tables
About the Documentation
■ E Series and JUNOSe Documentation and Release Notes on page xxix
■ Audience on page xxix
■ E Series and JUNOSe Text and Syntax Conventions on page xxix
■ Obtaining Documentation on page xxxi
■ Documentation Feedback on page xxxi
■ Requesting Technical Support on page xxxi
E Series and JUNOSe Documentation and Release Notes
For a list of related JUNOSe documentation, see
http://www.juniper.net/techpubs/software/index.html .
If the information in the latest release notes differs from the information in the
documentation, follow the JUNOSe Release Notes.
To obtain the most current version of all Juniper Networks® technical documentation,
see the product documentation page on the Juniper Networks website at
http://www.juniper.net/techpubs/.
Audience
This guide is intended for experienced system and network specialists working with
Juniper Networks E Series Broadband Services Routers in an Internet access
environment.
E Series and JUNOSe Text and Syntax Conventions
Table 1 on page xxx defines notice icons used in this documentation.
E Series and JUNOSe Documentation and Release Notes ■ xxix
JUNOSe 11.1.x Link Layer Configuration Guide
Table 1: Notice Icons
Table 2 on page xxx defines text and syntax conventions that we use throughout the
E Series and JUNOSe documentation.
DescriptionMeaningIcon
Indicates important features or instructions.Informational note
Indicates a situation that might result in loss of data or hardware damage.Caution
Alerts you to the risk of personal injury or death.Warning
Alerts you to the risk of personal injury from a laser.Laser warning
Table 2: Text and Syntax Conventions
Represents commands and keywords in text.Bold text like this
Bold text like this
Fixed-width text like this
Represents text that the user must type.
Represents information as displayed on your
terminal’s screen.
Italic text like this
Emphasizes words.
■
Identifies variables.
■
Identifies chapter, appendix, and book
■
names.
Plus sign (+) linking key names
keys simultaneously.
Syntax Conventions in the Command Reference Guide
ExamplesDescriptionConvention
Issue the clock source command.
■
Specify the keyword exp-msg.
■
host1(config)#traffic class low-loss1
host1#show ip ospf 2
Routing Process OSPF 2 with Router
ID 5.5.0.250
Router is an Area Border Router
(ABR)
There are two levels of access: user and
■
privileged.
clusterId, ipAddress.
■
Appendix A, System Specifications
■
Press Ctrl + b.Indicates that you must press two or more
terminal lengthRepresents keywords.Plain text like this
| (pipe symbol)
or variable to the left or to the right of this
symbol. (The keyword or variable can be
either optional or required.)
xxx ■ E Series and JUNOSe Text and Syntax Conventions
mask, accessListNameRepresents variables.Italic text like this
diagnostic | lineRepresents a choice to select one keyword
Table 2: Text and Syntax Conventions (continued)
About the Documentation
ExamplesDescriptionConvention
[ internal | external ]Represent optional keywords or variables.[ ] (brackets)
[ ]* (brackets and asterisk)
that can be entered more than once.
Represent required keywords or variables.{ } (braces)
Obtaining Documentation
To obtain the most current version of all Juniper Networks technical documentation,
see the Technical Documentation page on the Juniper Networks Web site at
http://www.juniper.net/.
To download complete sets of technical documentation to create your own
documentation CD-ROMs or DVD-ROMs, see the Offline Documentation page at
http://www.juniper.net/techpubs/resources/cdrom.html
Copies of the Management Information Bases (MIBs) for a particular software release
are available for download in the software image bundle from the Juniper Networks
Web site athttp://www.juniper.net/.
Documentation Feedback
[ level1 | level2 | l1 ]*Represent optional keywords or variables
{ permit | deny } { in | out }
{ clusterId | ipAddress }
We encourage you to provide feedback, comments, and suggestions so that we can
improve the documentation to better meet your needs. Send your comments to
techpubs-comments@juniper.net, or fill out the documentation feedback form at
https://www.juniper.net/cgi-bin/docbugreport/. If you are using e-mail, be sure to include
the following information with your comments:
■ Document or topic name
■ URL or page number
■ Software release version
Requesting Technical Support
Technical product support is available through the Juniper Networks Technical
Assistance Center (JTAC). If you are a customer with an active J-Care or JNASC support
contract, or are covered under warranty, and need post-sales technical support, you
can access our tools and resources online or open a case with JTAC.
■ JTAC policies—For a complete understanding of our JTAC procedures and policies,
review the JTAC User Guide located at
http://www.juniper.net/customers/support/downloads/7100059-EN.pdf .
Obtaining Documentation ■ xxxi
JUNOSe 11.1.x Link Layer Configuration Guide
■ Product warranties—For product warranty information, visit
http://www.juniper.net/support/warranty/ .
■ JTAC hours of operation—The JTAC centers have resources available 24 hours a
day, 7 days a week, 365 days a year.
Self-Help Online Tools and Resources
For quick and easy problem resolution, Juniper Networks has designed an online
self-service portal called the Customer Support Center (CSC) that provides you with
the following features:
■
Find CSC offerings: http://www.juniper.net/customers/support/
■
Search for known bugs: http://www2.juniper.net/kb/
■
Find product documentation: http://www.juniper.net/techpubs/
■ Find solutions and answer questions using our Knowledge Base:
http://kb.juniper.net/
■ Download the latest versions of software and review release notes:
http://www.juniper.net/customers/csc/software/
■ Search technical bulletins for relevant hardware and software notifications:
https://www.juniper.net/alerts/
■ Join and participate in the Juniper Networks Community Forum:
http://www.juniper.net/company/communities/
■
Open a case online in the CSC Case Management tool: http://www.juniper.net/cm/
To verify service entitlement by product serial number, use our Serial Number
Entitlement (SNE) Tool: https://tools.juniper.net/SerialNumberEntitlementSearch/
Opening a Case with JTAC
You can open a case with JTAC on the Web or by telephone.
■
Use the Case Management tool in the CSC at http://www.juniper.net/cm/ .
■ Call 1-888-314-JTAC (1-888-314-5822 toll-free in the USA, Canada, and Mexico).
For international or direct-dial options in countries without toll-free numbers, see
http://www.juniper.net/support/requesting support.html .
xxxii ■ Requesting Technical Support
Part 1
Chapters
■ Configuring ATM on page 3
■ Configuring Frame Relay on page 107
■ Configuring Multilink Frame Relay on page 133
■ Configuring Upper-Layer Protocols over Static Ethernet Interfaces on page 153
■ Configuring VLAN and S-VLAN Subinterfaces on page 169
■ Configuring 802.3ad Link Aggregation and Link Redundancy on page 199
■ Configuring IEEE 802.3ah OAM Link-Fault Management on page 227
■ Configuring Point-to-Point Protocol on page 263
■ Configuring Multilink PPP on page 303
■ Configuring Multiclass Multilink PPP on page 349
■ Configuring Packet over SONET on page 363
■ Configuring Point-to-Point Protocol over Ethernet on page 375
■ Configuring Bridged IP on page 437
■ Configuring Bridged Ethernet on page 443
■ Configuring Transparent Bridging on page 467
■ Configuring Cisco HDLC on page 505
■ Configuring Dynamic Interfaces on page 515
■ Configuring Dynamic Interfaces Using Bulk Configuration on page 623
Chapters ■ 1
JUNOSe 11.1.x Link Layer Configuration Guide
2 ■ Chapters
Chapter 1
Configuring ATM
This chapter introduces basic Asynchronous Transfer Mode (ATM) concepts, describes
features of the ATM interfaces, and provides information for configuring ATM on E
Series routers.
This chapter contains the following sections:
■ Overview on page 3
■ Platform Considerations on page 10
■ References on page 11
■ Supported Features on page 12
■ ATM NBMA on page 13
■ Operations, Administration, and Management of ATM Interfaces on page 15
■ Before You Configure ATM on page 21
■ Configuration Tasks on page 22
■ Creating a Basic Configuration on page 22
■ Setting Optional Parameters on page 24
■ Configuring OAM on page 33
■ Configuring an NBMA Interface on page 39
■ Creating an NBMA Static Map on page 40
■ Assigning Descriptions to Interfaces on page 42
■ Sending Interface Descriptions to AAA on page 43
■ Configuring Individual ATM PVC Parameters on page 45
■ Configuring ATM VC Classes on page 55
■ Configuring Dynamic ATM 1483 Subinterfaces on page 69
■ Monitoring ATM on page 69
Overview
ATM is a high-speed networking technology that handles data in fixed-size units
called cells. It enables high-speed communication between edge routers and core
routers in an ATM network.
Overview ■ 3
JUNOSe 11.1.x Link Layer Configuration Guide
ATM Interfaces
An ATM port can have a major interface and one or more subinterfaces. An ATM
subinterface is a mechanism that enables a single physical ATM interface to support
multiple logical interfaces. Several logical interfaces can be associated with a single
physical interface.
ATM subinterfaces meet the specifications in RFC 2684—Multiprotocol Encapsulation
over ATM Adaptation Layer 5 (September 1999), which replaces RFC 1483. All
references to ATM subinterfaces in this chapter are still to ATM 1483 subinterfaces.
ATM 1483 subinterfaces are identified by user-defined numbers. To select a
subinterface, you append a subinterface number to the port-level interface atm
command.
When you create an ATM 1483 subinterface, you must configure a permanent virtual
circuit (PVC). Protocols such as ATM require one or more virtual circuits over which
data traffic is transmitted to higher layers in the protocol stack.
Figure 1 on page 4 shows a typical point-to-point ATM interface column.
Figure 1: ATM Interface Column
ATM Physical Connections
ATM interfaces and subinterfaces support two types of connections—point-to-point
and multipoint. The router defaults to point-to-point.
■ Point-to-point—Indicates a standard connection; for example, connecting two
ATM end stations
4 ■ Overview
■ Multipoint—Indicates a single-source end system connected to multiple
destination end systems. Multipoint indicates a nonbroadcast multiaccess (NBMA)
interface. See “ATM NBMA” on page 13.
Depending on the type of connection you choose, you can specify one or more PVCs
on each interface. For a standard point-to-point ATM interface, you configure only
one PVC. For NBMA ATM connections, you configure multiple circuits.
ATM Virtual Connections
A virtual connection (VC) defines a logical networking path between two endpoints
in an ATM network. ATM cells travel from one point to the other over a virtual
connection. An ATM cell is a package of information that is always 53 bytes in length,
unlike a frame or packet, which has a variable length. An ATM cell has a cell header
and a payload. The payload contains the user data.
The cell header includes an 8-bit virtual path identifier (VPI) and a 16-bit virtual
channel identifier (VCI).
An ATM network can have two types of VCs, depending on the addressing used to
switch the traffic:
■ Virtual channel connection (VCC)
Chapter 1: Configuring ATM
ATM SVCs
■ Virtual path connection (VPC)
Virtual Channel Connection
A VCC uses all the addressing bits of the cell header to move traffic from one link to
another. The VCC is formed by joining a series of virtual channels (VCs), which are
logical circuits uniquely identified for each link of the network. On a VCC, switching
is done based on the combined VPI and VCI values.
Virtual Path Connection
A VPC uses the higher-order addressing bits of the cell header to move traffic from
one link to another. A VPC carries many VCCs within it. A VPC can be set up
permanently between two points, and then switched.
VCCs can be assigned within the VPC easily and quickly. The VPC is formed by joining
a series of virtual paths, which are the logical groups of circuits uniquely defined for
each link of the network. On a VPC, switching is done based on the VPI value only.
JUNOSe software does not support configuration and monitoring of ATM switched
virtual circuits (SVCs) on the router.
ATM Adaptation Layer
The ATM Adaptation Layer (AAL) defines the conversion of user information into
cells by segmenting upper-layer information into cells at the transmitter and
reassembling them at the receiver. AAL1 and AAL2 handle intermittent traffic, such
as voice and video, and are not relevant to the router. AAL3/4 and AAL5 support data
communications by segmenting and reassembling packets.
Overview ■ 5
JUNOSe 11.1.x Link Layer Configuration Guide
E Series routers support the following AAL5 encapsulation types as specified in RFC
2684—Multiprotocol Encapsulation over ATM Adaptation Layer 5 (September 1999),
which replaces RFC 1483:
■ aal5snap—LLC/SNAP
■ aal5mux ip—VC-based multiplexing
■ aal5autoconfig—LLC/SNAP or VC-based multiplexing. (See “Configuring Dynamic
Interfaces” on page 515.)
■ aal5all—Martini encapsulation
NOTE: The Juniper Networks E120 and E320 Broadband Services Routers do not
support Martini encapsulation (aal5all) in the current release.
Local ATM Passthrough
E Series routers support local ATM passthrough for ATM layer 2 services over
Multiprotocol Label Switching (MPLS). Local ATM passthrough enables the router to
emulate packet-based ATM switching. The ATM passthrough feature is useful for
customers who run IP in most of their network but still have to carry a small amount
of native ATM traffic.
Local ATM passthrough uses ATM Martini encapsulation to emulate ATM switch
behavior. You can create pairs of cross-connected ATM VCs within the router. The
router then passes AAL5 traffic between two VCs, regardless of the contents of the
packets.
You can also use AAL0 encapsulation when you configure a local ATM passthrough
connection. AAL0 encapsulation causes the router to receive raw ATM cells on this
circuit and to forward the cells without performing AAL5 packet reassembly.
For more information, see chapter Configuring Layer 2 Services over MPLS in JUNOSe
BGP and MPLS Configuration Guide.
VCC Cell Relay Encapsulation
E Series routers support virtual channel connection (VCC) cell relay encapsulation
for ATM layer 2 services over MPLS. VCC cell relay encapsulation is useful for
voice-over-ATM applications that use AAL2-encapsulated voice transmission.
VCC cell relay encapsulation enables the router to emulate ATM switch behavior by
forwarding individual ATM cells over an MPLS pseudowire (also referred to as an
MPLS tunnel) created between two ATM VCCs, or as part of a local ATM passthrough
connection between two ATM 1483 subinterfaces on the same router. The E Series
implementation conforms to the required N-to-1 cell mode encapsulation method
described in the Martini draft, Encapsulation Methods for Transport of ATM Over
MPLS Networks—draft-ietf-pwe3-atm-encap-07.txt (April 2005 expiration), with the
provision that only a single ATM virtual circuit (VC) can be mapped to an MPLS tunnel.
6 ■ Overview
Traffic Management
Chapter 1: Configuring ATM
For more information, see chapter Configuring Layer 2 Services over MPLS in JUNOSe
BGP and MPLS Configuration Guide.
NOTE: The E120 and E320 routers do not support ATM over MPLS with VCC cell
relay encapsulation in the current release.
The scheduling priority for traffic classes depends on the type of router that you
have. Table 3 on page 7 describes the scheduling priorities for each type of router.
Table 3: Scheduling Priorities for Traffic Classes
Scheduling Priority
(from Highest to
Lowest)
1
2
ERX7xx Models, ERX14xx
Models, or the ERX310
Broadband Services Router
prioritized equally:
CBR
■
VBR-RT
■
prioritized equally:
VBR-NRT
■
UBR with a peak cell rate
■
(PCR)
E120 and E320 routers
CBRThe following traffic classes are
VBR-RTThe following traffic classes are
VBR-NRTUBR without PCR3
UBR with or without PCR–4
The level of support for traffic management depends on the specific I/O module or
IOA. See “Supported Features” on page 12.
Connection Admission Control
ATM networks use connection admission control (CAC) to determine whether to
accept a connection request, based on whether allocating the connection’s requested
bandwidth causes the network to violate the traffic contracts of existing connections.
CAC is a set of actions that the network takes during connection setup or
renegotiation.
The router supports CAC on PVCs on major ATM interfaces. This implementation of
CAC determines available bandwidth based on port subscription bandwidth. The
router maintains available bandwidth for each major ATM port. Bandwidth for VP
tunnels is included in CAC computations.
Overview ■ 7
JUNOSe 11.1.x Link Layer Configuration Guide
Table 4 on page 8 lists the traffic parameter that the router uses for each service
category to compute the bandwidth that the connection requires. For example, the
peak cell rate is used to calculate how much bandwidth is required for CBR
connections.
Table 4: Traffic Parameters Used to Compute Bandwidth
Traffic Parameter Used to Calculate Required BandwidthService Category
PCRCBR
SCRVBR-RT
SCRVBR-NRT
UBR bandwidth configured on the ATM major interfaceUBR
UBR bandwidth configured on the ATM major interfaceUBR with PCR
How CAC Works
With no connections, the available bandwidth is equal to the subscription port
bandwidth. While connections are requested, the required bandwidth, which is based
on the service category and traffic parameters of the connection, is compared against
the available port bandwidth. If sufficient bandwidth is available, the router accepts
the connection and updates the available port bandwidth accordingly.
Similarly, when a connection is deleted, the available port bandwidth is updated
accordingly.
Configuring CAC
You enable and configure CAC on an ATM major interface using “atm cac” on page 28
. When you enable CAC on an ATM interface, you can optionally specify a subscription
bandwidth and a UBR weight:
■ The subscription bandwidth can be greater than the effective port bandwidth to
allow oversubscription. The default value of the subscription bandwidth is the
effective bandwidth of the ATM port.
■ The UBR weight enables you to limit the number of UBR connections by assigning
a bandwidth or weight to each UBR or VBR with a PCR connection
CAC and ATM Bulk Configuration
8 ■ Overview
You cannot configure CAC on an ATM interface on which you have created a
bulk-configured virtual circuit (VC) range for use by a dynamic ATM 1483 subinterface.
Conversely, you cannot create a bulk-configured VC range on an ATM interface on
which you have configured CAC. The router rejects these configurations, which causes
them to fail.
ILMI
Chapter 1: Configuring ATM
If you are upgrading to the current JUNOSe software release from a lower-numbered
release, configurations that use CAC and bulk configuration on the same ATM interface
continue to work. However, we recommend that you disable CAC on these ATM
interfaces to ensure continued compatibility with future JUNOSe releases.
For information about how to use the atm cac command to configure CAC, see
“Setting Optional Parameters” on page 24. For information about how to use the
atm bulk-config command to create a bulk-configured VC range, see “Bulk
Configuration of VC Ranges” on page 631 in “Configuring Dynamic Interfaces Using
Bulk Configuration” on page 623.
ATM interfaces support the ATM Forum integrated local management interface (ILMI),
versions 3.0, 3.1, and 4.0. An important feature of ILMI is the ability to poll or send
keepalive messages across the UNI. ATM interfaces always respond to such messages,
which are sent by an ATM peer device. Optionally, you can configure ATM major
interfaces to generate keepalive messages, a process that enables a continuous
ATM-layer connectivity verification; if the ATM peer stops responding to keepalive
messages, the router disables the ATM interface.
The ATM interface is not reenabled until the keepalive message’s responses are
received (or until the keepalive feature is disabled on the ATM port). To enable ILMI
and control the generation of keepalive messages, use the atm ilmi-enable and atm
ilmi-keepalive commands.
VPI/VCI Address Ranges
The VPI/VCI address ranges allowed on ATM interfaces are module dependent. Certain
modules on ERX14xx models, ERX7xx models, or the Juniper Networks ERX310
Broadband Services Router have a fixed allocation scheme, whereas others have a
configurable allocation scheme. In the configurable allocation scheme, a bit range is
shared across the VPI and VCI fields.
For example, if an ATM interface has a bit range of 18, and 4 bits are allocated to
the VPI space, then 14 bits are left for the VCI space. The resulting numeric range is
0 to 2n-1, where n is the number of bits for each space. Completing the example, if
4 bits were allocated for the VPI space and 14 for the VCI space, the configurable
range would be 0 to 15 for VPI and 0 to 16,383 for the VCI space. To configure the
bit range, use “atm vc-per-vp” on page 31 .
See “Supported Features” on page 12 for details on how various line module and
I/O modules support configurable VPI/VCI address ranges.
NOTE: The E120 and E320 routers support the full VPI/VCI address range; therefore,
it has a fixed allocation scheme.
Overview ■ 9
JUNOSe 11.1.x Link Layer Configuration Guide
VP Tunneling
Virtual path (VP) tunneling enables traffic shaping to be applied to the aggregation
of all VCs within a single VP. Thus, VP tunnels can be used to ensure that the total
traffic transmitted on a VP does not exceed the specified PCR. VP tunneling uses a
round-robin algorithm to guarantee fairness among all of the VCs within the tunnel.
You can change the PCR associated with a tunnel even when VCs have already been
configured on the tunnel. The individual VCs within a tunnel must be specified as
UBR VCs. In other words, they may not have their own traffic-shaping parameters.
The level of support for VP tunneling is dependent on the specific I/O module. See
“Supported Features” on page 12 for details.
Platform Considerations
You can configure ATM interfaces on the following Juniper Networks E Series
Broadband Services Routers:
■ E120 router
■ E320 router
■ ERX1440 router
■ ERX1410 router
■ ERX710 router
■ ERX705 router
■ ERX310 router
Module Requirements
For information about the modules that support ATM interfaces on ERX14xx models,
ERX7xx models, and the ERX310 router:
■ See ERX Module Guide, Table 1, Module Combinations for detailed module
■ See ERX Module Guide, Appendix A, Module Protocol Support for information about
For information about the modules that support ATM interfaces on the E120 and
E320 routers:
specifications.
the modules that support ATM.
■ See E120 and E320 Module Guide, Table 1, Modules and IOAs for detailed module
■ See E120 and E320 Module Guide, Appendix A, IOA Protocol Support for information
10 ■ Platform Considerations
specifications.
about the modules that support MLPPP.
Interface Specifiers
Chapter 1: Configuring ATM
The configuration task examples in this chapter use the slot/port[.subinterface ] format
to specify an ATM interface. However, the interface specifier format that you use
depends on the router that you are using.
For ERX7xx models, ERX14xx models, and ERX310 router, use the
slot/port[.subinterface ] format. For example, the following command specifies
ATM 1483 subinterface 10 on slot 0, port 1 of an ERX7xx model, ERX14xx model,
or ERX310 router.
host1(config)#interface atm 0/1.10
For E120 and E320 routers use the slot/adapter/port[.subinterface ] format, which
includes an identifier for the bay in which the I/O adapter (IOA) resides. In the
software, adapter 0 identifies the right IOA bay (E120 router) and the upper IOA bay
(E320 router); adapter 1 identifies the left IOA bay (E120 router) and the lower IOA
bay (E320 router). For example, the following command specifies ATM 1483
subinterface 20 on slot 5, adapter 0, port 0 of an E120 or E320 router.
References
host1(config)#interface atm 5/0/0.20
For more information about supported interface types and specifiers on E Series
routers, see Interface Types and Specifiers in JUNOSe Command Reference Guide.
For more information about ATM interfaces, consult the following resources:
■ ATM Forum—ATM User-Network Interface Specification, Version 3.0 (September
1993)
■ ATM Forum—ATM User-Network Interface Specification, Version 3.1 (September
1994)
■ ATM Forum—Integrated Local Management Interface (ILMI) Specifications,
Versions 3.0, 3.1, and 4.0 (September 1996)
■ ATM Forum—Traffic Management Specification, Version 4.0 (April 1996)
■ ITU-T Draft Recommendation I.363 (AAL5 support) (January 1993)
■ RFC 2390—Inverse Address Resolution Protocol (September 1998)
■ RFC 2684—Multiprotocol Encapsulation over ATM Adaptation Layer 5 (September
1999) (RFC 2684 obsoletes RFC 1483)
■ ITU-T Recommendation I.610—B-ISDN Operation and Maintenance Principles
and Functions (February 1999)
■ Encapsulation Methods for Transport of ATM Over MPLS
Networks—draft-ietf-pwe3-atm-encap-07.txt (April 2005 expiration)
■ JUNOSe Release Notes, Appendix A, System Maximums—See the Release Notes
corresponding to your software release for information about maximum values
References ■ 11
JUNOSe 11.1.x Link Layer Configuration Guide
NOTE: IETF drafts are valid for only 6 months from the date of issuance. They must
be considered as works in progress. Please refer to the IETF Web site at
http://www.ietf.org for the latest drafts.
Supported Features
This section describes ATM feature support on E Series modules.
For more information about the physical layer characteristics of the modules described
in this section, including the numbering schemes, see the JUNOSe Physical Layer
Configuration Guide.
Module Capabilities
The level of support for certain ATM capabilities varies depending on the module.
Table 5 on page 12 lists the specific differences in the capabilities of the modules.
The number of VP tunnels varies with the number of ports in the associated line
module. For information about the maximum number of ATM VP tunnels supported
per port for all line modules, see JUNOSe Release Notes, Appendix A, System Maximums.
NOTE: Support for the OC3 (dual port) line module has been deprecated.
Table 5: ATM Capabilities on Line Modules and I/O Modules
VPI/VCI
Address
Range
Configurable
Bit Range
20Configurable1024OC3-4 I/O
20Configurable256OC12/STM4
Line
Module
OCx/STMx
ATM
OCx/STMx
ATM
I/O Module
or IOA
4xDS3 ATM
I/O
I/O
Number
of VP
Tunnels
Number of
VCs on
Each Port
8000
active
16,000
configured
8000
active
16,000
configured
ATM Circuit
Traffic
Management
Types
CBR, UBR,
UBR with
PCR,
VBR-NRT,
VBR-RT
CBR, UBR,
UBR with
PCR,
VBR-NRT,
VBR-RT
VP Tunnel
Traffic
Management
Types
CBR,
VBR-NRT
CBR,
VBR-NRT
OC3/STM1
GE/FE
APS I/O
12 ■ Supported Features
20Configurable1024OC3-2 GE
8000
active
16,000
configured
CBR, UBR,
UBR with
PCR,
VBR-NRT,
VBR-RT
CBR,
VBR-NRT
Table 5: ATM Capabilities on Line Modules and I/O Modules (continued)
Chapter 1: Configuring ATM
Number
Line
Module
ES2 4G LM
ES2 4G LM
I/O Module
or IOA
ES2-S1
OC3-8
STM1 ATM
IOA
ES2-S1
OC12-2
STM4 ATM
IOA
of VP
Tunnels
1 IOA
per slot:
2048
2 IOAs
per slot:
4096
1 IOA
per slot:
512
2 IOAs
per slot:
1024
Virtual Channel Support
The number of virtual channels (VCs) that the router supports on each port varies
depending on the E Series router and module you are using. For information about
the maximum number of ATM VCs supported per chassis, per module, and per port,
see JUNOSe Release Notes, Appendix A, System Maximums.
VPI/VCI
Address
Range
VPI: 0–255
VCI:
0–65535
VPI: 0–255
VCI:
0–65535
Configurable
Bit Range
–Fixed
–Fixed
Number of
VCs on
Each Port
8000
active
16,000
configured
8000
active
16,000
configured
ATM Circuit
Traffic
Management
Types
CBR, UBR,
UBR with
PCR,
VBR-NRT,
VBR-RT
CBR, UBR,
UBR with
PCR,
VBR-NRT,
VBR-RT
VP Tunnel
Traffic
Management
Types
CBR,
VBR-NRT
CBR,
VBR-NRT
ATM NBMA
The software supports nonbroadcast multiaccess (NBMA) networks, which
interconnect more than two routers and have no broadcast capabilities.
NOTE: The E120 and E320 routers do not support ATM NBMA in the current release.
An ATM NBMA network can be thought of as an interface stack with a single IP
interface at the top, eventually fanning out to multiple independent PVCs. See Figure
2 on page 14.
ATM NBMA ■ 13
JUNOSe 11.1.x Link Layer Configuration Guide
Figure 2: NBMA Interface Stack
Unlike standard point-to-point ATM interfaces and broadcast-oriented Ethernet
interfaces, NBMA interfaces form a point-to-multipoint connection. For example,
you can use NBMA to connect a router to multiple stations.
An NBMA interface consists of a single ATM 1483 subinterface that has two or more
VCs. You can add circuits to an existing ATM 1483 subinterface at any time. New
circuits become usable after they have valid ARP table entries. NBMA circuits support
only IP directly over ATM 1483.
ARP Table
The software restricts NBMA interfaces so that all circuits reside on the same physical
interface. An NBMA interface can use as many PVCs as are available on a physical
port.
To maintain the Address Resolution Protocol (ARP) table, you can use either static
mapping via the CLI or Inverse ARP (InARP). InARP provides a way of determining
the IP address of the device at the far end of a circuit. For NBMA interfaces, InARP
enables automatic creation of ARP table entries for each circuit on the interface.
You must enable InARP when you create a PVC by using the atm pvc command.
After you configure InARP, a protocol mapping between an ATM PVC and a network
address is learned dynamically as a result of the exchange of InARP packets.
Static Map Versus Inverse ARP
If the device at the other end of a circuit does not support InARP, static mapping is
required for that circuit. One of these two methods must be used to generate an ARP
table entry for each circuit of the NBMA interface.
InARP and static mapping are complementary within an NBMA subinterface, but are
not compatible with regard to individual circuits. If InARP is configured on a circuit,
the corresponding virtual circuit descriptor (VCD) cannot be present in a static map
applied to that interface.
14 ■ ATM NBMA
Aging
ARP table entries, with the exception of those declared static, are aged out based on
an aging interval defined on a subinterface basis. For the purposes of aging, entries
produced via a static map are treated as static ARP table entries. InARP-generated
entries are also treated as static; however, the InARP state machine automatically
removes entries that cannot be successfully refreshed after three successive failed
InARP requests.
Removing Circuits
If a circuit is removed, it is also removed from the ARP table, but not from the static
map. If the circuit is reconfigured, a new ARP table entry is generated from the
existing map entry. If the circuit uses InARP, the ARP table entry is immediately
removed on removal of the circuit.
If a subinterface is removed, all associated circuits and their associated ARP table
entries are removed.
Operations, Administration, and Management of ATM Interfaces
ATM interfaces support the OAM standards of the ITU, per recommendation I.610.
OAM provides VC/VP integrity and fault and performance management. The E Series
router supports F4 and F5 ATM OAM fault management, loopback, and continuity
check (CC) cells. These cells perform fault detection and notification, loopback testing,
and link integrity.
Chapter 1: Configuring ATM
ATM uses F4 and F5 cell flows as follows:
■ F4—Used in VPs
■ F5—Used in VCs
ATM interfaces always generate and validate CRC-10 checksums on OAM cells.
For information about configuring OAM on the router, see the following sections:
■ “Configuring OAM” on page 33
■ “Configuring F5 OAM for Data PVCs” on page 51
End-to-End and Segment Endpoints
An ATM connection consists of a group of points. This OAM implementation provides
management for the following points:
■ Connection endpoint—The end of a VC/VP connection where the ATM cells are
terminated
■ Segment endpoint—The end of a connection segment
Fault Management
ATM uses two types of fault management cells to convey defect information to the
endpoints of a VP/VC:
■ Alarm indication signal (AIS) cells, which are used to indicate a fault to the
downstream endpoint. AIS cells contain defect type and defect location fields,
Operations, Administration, and Management of ATM Interfaces ■ 15
JUNOSe 11.1.x Link Layer Configuration Guide
which optionally convey information about the type of defect detected and the
location of the defect.
■ Remote defect indication (RDI) cells, which are received from the remote endpoint
of the VP/VC and indicate an interruption in the cell transfer capability of the
VP/VC.
Connecting points in the VP/VC that detect a fault send AIS cells in the downstream
direction to the endpoint of the VP/VC. Upon receipt of AIS cells, the downstream
endpoint generates RDI cells in the upstream direction to alert all connecting points
and the remote endpoint of an interruption in the cell transfer capability of the VP/VC.
If fault management detects a failure condition (because of arrival of AIS or RDI cells),
the router disables the corresponding VC until the fault condition is no longer detected.
How the ATM Interface Handles AIS Cells
Nodes that detect a failure send AIS cells to the downstream endpoint. Because the
ATM interface is an endpoint and there is no downstream neighbor to an ATM
endpoint, the ATM interface never generates AIS cells. The ATM interface responds
to the receipt of AIS cells as follows:
1. When an ATM interface receives a configurable number of F4 or F5 AIS cells, it
enters the AIS state.
2. While in the AIS state, the ATM interface sends F4 or F5 RDI cells to the remote
endpoint. It sends the RDI cells at the rate of one cell per second for as long as
the AIS condition exists.
For all RDI cells sent, the defect type and defect location fields contain the values
from the received AIS cells.
3. RDI cell generation stops when one of the following conditions occurs:
■ The interface receives an F4 or F5 loopback cell or an F4 or F5 CC cell.
■ The interface does not receive an AIS cell for a configurable time period.
■ The OAM VC status field of “show atm vc atm” on page 94 shows that the
circuit is in AIS state.
How the ATM Interface Handles RDI Cells
RDI cells received from the remote endpoint of the VP/VC indicate an interruption
in the cell transfer capability of the VP/VC. For example, the remote endpoint of a
VC receives an F5 AIS cell, enters the AIS state, and transmits F5 RDI cells for the
duration of the AIS condition. On receipt of a configurable number of F4 or F5 RDI
cells, the ATM interface declares an RDI state but does not generate OAM fault
management cells in response to the condition. The ATM interface leaves the RDI
condition when no RDI cells have been received for a configurable time period.
The OAM VC status field of “show atm vc atm” on page 94 shows whether the circuit
is in RDI state.
16 ■ Operations, Administration, and Management of ATM Interfaces
Continuity Verification
CC cells provide continual monitoring of a connection on a segment or end-to-end
basis. To verify the integrity of the link, you can set up a VP or VC to regularly send
or receive CC cells at either the segment level or at the end-to-end level.
The CC cell source generates the CC cells, and the sink receives and processes the
cells. You can set up a VP or VC as the source, the sink, or both the source and the
sink. If you enable a VP or VC as a CC cell source, it generates CC cells. The VP or
VC counts CC cells whether or not CC cell flow is enabled. You can enable CC cells
only on data circuits, not on control circuits, such as ILMI or signaling circuits.
Activation and Deactivation Cells
To enable and disable CC cell flows, ATM OAM uses activation and deactivation cells:
■ To enable a CC cell flow, the router sends activation OAM cells to the peer. The
Chapter 1: Configuring ATM
peer replies with a confirmation or denial. If the CC sink point is not activated,
all received CC cells are dropped. (See “Activating CC Cell Flow” on page 17 for
more details.)
■ To disable a CC cell flow, the router sends deactivation OAM cells to the peer.
The peer replies with a confirmation or denial.
Activating CC Cell Flow
When the router sends a CC activation cell to the peer, one of the following occurs:
■ If the router receives a positive response (Activation Confirmed), the VC or VP
goes to CC active state, and CC is enabled on the VC or VP.
■ If the router receives a negative response (Activation Req. Denied), the VC or VP
goes to CC failed state, and CC is not enabled on the VC or VP.
■ If the router does not receive a response within 5 seconds, it sends another
activation cell. This process is repeated three times. If the router does not receive
a response, it stops the activation process.
If the VC or VP is the source point, CC cell generation starts as soon as the router
sends the activation request to the peer. CC cell generation stops if the CC fails, when
the maximum number of retries is reached, or when the deactivation process is
complete.
Deactivating CC Cell Flow
The process of sending a deactivation request is the same as for activation cells
except that deactivation cells are sent instead.
Also, the atm oam flush command causes the router to send a deactivation request
to the peer and suspend all CC operations. Therefore, we recommend that you disable
CC cell generation and transmission on all VCs before issuing atm oam flush.
Operations, Administration, and Management of ATM Interfaces ■ 17
JUNOSe 11.1.x Link Layer Configuration Guide
After CC Cell Flow Is Enabled
If the VC or VP is set up as the source point, the ATM interface sends one CC cell per
second. CC cell generation stops if one of the following conditions occur:
■ The ATM interface goes down.
■ You disable OAM CC on the circuit by using the atm pvc command.
■ The peer deactivates the OAM CC cell flow.
■ You disable OAM cell reception and transmission on the ATM interface by using
the atm oam flush command.
If the VP is set up as a CC sink point and no CC cell is received for 4 seconds, the VP
goes to AIS state and sends one RDI cell per second.
To view the current state of the activation or deactivation process, including statistics,
use the show atm oam command for VPs and the show atm vc atm interface
command for VCs.
Loopback
You can use loopback cells to verify connectivity between VP/VC endpoints, as well
as segment endpoints within the VP/VC. You can use these tests to perform fault
isolation over the VP/VC.
The ATM interface supports VC integrity, which generates F5 end-to-end loopback
cells. It also supports ATM ping, which generates F4 and F5 segment and end-to-end
loopback cells to test the reachability of an endpoint or a segment endpoint.
VC Integrity
VC integrity is used to monitor the operational status of an individual VC. VC integrity
provides continuous ATM VC-layer connectivity verification by periodically sending
F5 end-to-end loopback cells on individual PVCs to verify end-to-end connectivity.
You can set the frequency with which loopback cells are transmitted for an individual
VC.
If VC integrity is enabled, the peer ATM host must respond to the router’s loopback
cells, or the circuit will be disabled. The ATM interface does not reenable the circuit
until it receives loopback responses or until local VC integrity is disabled.
You can set the following VC integrity parameters for an individual VC with the
oam retry command. For more information, see “oam retry” on page 54.
■ The retry frequency with which loopback cells are transmitted when the router
verifies the down status of the circuit; that is, when the peer ATM host does not
respond to a loopback cell
■ The retry frequency with which loopback cells are transmitted when the router
verifies the up status of the circuit; that is, when the ATM host resumes
responding to a loopback cell
18 ■ Operations, Administration, and Management of ATM Interfaces
Chapter 1: Configuring ATM
■ The number of successive loopback cell responses missed before the router
determines that the circuit is down
■ The number of successive loopback responses received before the router
determines that the circuit is up
VC integrity is a best-effort mechanism that tries to adhere to the loopback cell
transmission frequency and retry frequency values configured for each VC without
consuming excessive processing time on the line module. When you configure
VC integrity for a large number of circuits on the line module, delays in transmitting
OAM loopback cells might occur so new subscribers can connect and to maintain
existing subscriber connections.
To set up the ATM interface to transmit F5 end-to-end loopback cells over a VC, use
the oam keyword and an optional frequency with the atm pvc command. To send
F5 segment loopback cells, use the ATM ping mechanism, described in “ATM Ping”
on page 19.
F5 loopback receive and transmit statistics are available with “show atm vc atm” on
page 94 .
F4 OAM Cells
You can generate F4 loopback cells using the atm oam command or the ATM ping
mechanism. F4 loopback receive and transmit statistics are available with the show
atm oam command and include statistics on incoming and outgoing F4 end-to-end
and segment loopback cells.
ATM Ping
With ATM ping you can verify whether a connection endpoint or segment point can
be reached on a VC or VP. ATM ping uses F4 and F5 loopback cells and is supported
only for data circuits and not control circuits (ILMI, signaling circuits). To generate:
■ F5 segment loopback cells or end-to-end loopback cells, issue the ping atm
command on a VC.
■ F4 segment loopback cells or end-to-end loopback cells, issue the ping atm
command on a VP.
You can specify the number of loopback cells that are sent, the location ID, and the
timer value. After the interface sends the loopback cells, the timer is started and the
interface waits for a response. On receiving the loopback response (or when the
timer expires) the ATM interface sends the next cell. This operation is repeated for
the number of cells specified.
Because F4 and F5 are OAM cells, disabling receipt and transmission of OAM cells
on the ATM interface (by using the atm oam flush command) stops all outstanding
ping operations on the ATM interface. You need to manually restart the ping operation
after you enable receipt and transmission of OAM cells for the interface.
Operations, Administration, and Management of ATM Interfaces ■ 19
JUNOSe 11.1.x Link Layer Configuration Guide
How the ATM Interface Handles Loopback Cells Received
The ATM interface responds to received F4 and F5 loopback cells as indicated in
Table 6 on page 20.
Table 6: Handling of F4 and F5 Loopback Cells Received
ATM Interface ResponseLoopback Cell Received
F4 and F5 end-to-end loopback cells and
segment loopback cells with the loopback
location field set to all 1s (ones) and the
loopback indication set.
F4 and F5 segment loopback cells with the
loopback location field set to all 0s (zeros) and
the loopback indication set.
F4 and F5 end-to-end loopback cells and
segment loopback cells with the loopback
location field set to the loopback location ID of
the ATM interface and the loopback indication
set.
location field set to a value other than all 1s and
the loopback location ID of the ATM interface.
location field set to other than all 1s (ones), set
to all 0s (zeros), or set to the loopback location
ID of the ATM interface.
Automatic Disabling of F5 OAM Services
The router automatically disables all F5 OAM fault management and VC integrity
services configured on a VC when you change the administrative status of the
corresponding ATM interface, ATM AAL5 interface, or ATM 1483 subinterface from
enabled to disabled.
Clears the loopback indication (sets it to all
zeros) and loops back the received cell.
Resets the loopback indication and the
location ID to all 1s (ones) and loops back the
received cells.
Clears the loopback indication and loops back
the received cell without resetting the location
ID.
Discards the cell.F5 end-to-end loopback cells with the loopback
Discards the cell.F5 segment loopback cells with the loopback
To set the administrative status of an interface to disabled, use the atm shutdown
command (for an ATM interface), the atm aal5 shutdown command (for an ATM
AAL5 interface), or the atm atm1483 shutdown command (for an ATM 1483
subinterface). You can also use the shutdown command to disable the interface.
When F5 OAM is disabled, the OAM VC status field in the show atm vc atm command
display indicates that the VC is not managed. The VC does not receive or transmit
F5 OAM cells while F5 OAM is disabled. For examples of the show atm vc atm
command display, see “show atm vc atm” on page 94.
When the corresponding ATM interface, ATM AAL5 interface, or ATM 1483
subinterface is reenabled, the router automatically restores F5 OAM services on the
associated VCs.
20 ■ Operations, Administration, and Management of ATM Interfaces
Rate Limiting for F5 OAM Cells
The router implements rate limiting for ATM F5 OAM cells to protect the
corresponding ATM interface from denial-of-service (DoS) attacks. The interface
discards control packets when the rate of control packets received exceeds the rate
limit for ATM interfaces.
An ATM interface has a rate limit control that is non-configurable and always in effect;
the rate limit is the same for all ATM interfaces. In addition, each ATM VC maintains
its own state and statistics counters for tracking the rate. The rate limit for ATM OAM
cells is approximately 5 packets per second.
For an ATM VC, the router increments the InOamCellDiscards statistics counter in
the show atm vc atm command display to track the number of OAM cells received
on this circuit that were discarded. The InOamCellDiscards counter operates on a
per-circuit basis, not on a per-interface basis.
Chapter 1: Configuring ATM
For examples of the show atm vc atm command display, see “show atm vc atm”
on page 94.
Before You Configure ATM
Before you configure an ATM interface, verify that you have installed the physical
module (such as an OC3 module) correctly. For more information about
preconfiguration procedures, see the ERX Hardware Guide or the E120 and E320
Hardware Guide.
Also have the following information available:
■ Interface specifiers for the ATM interfaces that you want to create
For more information about specifying ATM interfaces and subinterfaces on E
Series routers, see Interface Types and Specifiers in JUNOSe Command Reference
Guide.
■ Virtual path and channel numbers for each virtual circuit you want to create
■ IP addresses and subnet mask assignments for IP interfaces
You can configure the following types of dynamic interfaces over ATM:
■ IP over static ATM 1483 (IPoA)
■ IP over PPP over static ATM 1483
■ IP over PPPoE over static ATM 1483
■ IP over bridged Ethernet over static ATM 1483
■ IP over MLPPP over static ATM 1483
■ ATM 1483 over static ATM AAL5 over ATM
For information about creating these dynamic configurations, see “Configuring
Dynamic Interfaces” on page 515.
Before You Configure ATM ■ 21
JUNOSe 11.1.x Link Layer Configuration Guide
Configuration Tasks
The following sections describe how to perform these ATM configuration tasks:
Creating a Basic Configuration
To configure ATM, perform the following tasks. (Figure 3 on page 23 shows the
relationship of Steps 1 through 3.)
1. Configure an ATM physical interface.
host1(config)#interface atm 0/1
2. Configure an ATM 1483 subinterface.
host1(config-if)#interface atm 0/1.20
3. Configure a PVC by specifying the VCD, the VPI, the VCI, and the encapsulation
type.
host1(config-subif)#atm pvc 10 15 22 aal5snap
4. Assign an IP address and subnet mask to the PVC.
host1(config-subif)#ip address 192.32.10.20 255.255.255.0
5. (Optional) Verify your configuration using the appropriate show commands.
host1#show atm interface atm 0/1
host1#show atm vc atm 0/1 10
host1#show atm subinterface atm 0/1.20
22 ■ Configuration Tasks
Figure 3: Configuring an ATM Interface, Subinterface, and PVC
ERX14xx models (rear view)
Chapter 1: Configuring ATM
atm pvc
■ Use to configure a PVC on an ATM interface.
■ Specify one of the following encapsulation types:
■ aal5snap—Specifies an LLC encapsulated circuit; LLC/SNAP header precedes
the protocol datagram.
■ aal5mux ip—Specifies a VC-based multiplexed circuit. This option is used
for IP only.
■ aal5autoconfig—Enables autodetection of the 1483 encapsulation (LLC/SNAP
or VC multiplexed) for dynamic interfaces. See “Configuring Dynamic
Interfaces” on page 515, for more explanation.
■ ilmi—Defines the PVC for ILMI keepalive messages. You can set this option
only on major interfaces. After the PVC is set up for ILMI, use “atm
ilmi-keepalive” on page 30 to cause the router to generate ILMI keepalive
messages on the interface.
■ You can optionally set the peak, average, and burst sizes. To use VBR-RT or
VBR-NRT as the service type, you must specify each of these options.
■ The default service type is UBR. To set a different service type, specify one of
the following keywords:
■ rt—Selects VBR-RT as the service type. You can select rt only if you set the
peak, average, and burst parameters.
■ cbr—Selects CBR as the service type. You must set the CBR rate in Kbps.
Creating a Basic Configuration ■ 23
JUNOSe 11.1.x Link Layer Configuration Guide
■ To enable VC integrity and generation of OAM F5 loopback cells on this circuit,
use the oam keyword.
■ Example
host1(config-if)#atm pvc 6 0 11 aal5snap cbr 10000
■ Use the no version to remove the specified PVC.
■ See atm pvc.
interface atm
■ Use to configure an ATM interface or subinterface type.
■ To specify an ATM interface for ERX7xx models, ERX14xx models, and ERX310
router, use the slot/port.[subinterface ] format.
■ slot—Number of the chassis slot
■ port—Port number on the I/O module; on the OC3-2 GE APS I/O module,
you can specify ATM interfaces only in ports 0 and 1; port 2 is reserved for
a Gigabit Ethernet interface
■ subinterface—Number of the subinterface in the range 1–2147483647
■ To specify an ATM interface for the E120 or E320 router, use the
slot/adapter/port[.subinterface ] format.
■ slot—Number of the chassis slot
■ adapter—Identifier for the IOA within the E320 chassis, either 0 or 1, where:
■ 0 indicates that the IOA is installed in the right IOA bay (E120 router)
or the upper IOA bay (E320 router)
■ 1 indicates that the IOA is installed in the left IOA bay (E120 router) or
the lower IOA bay (E320 router).
■ port—Port number on the IOA
■ subinterface—Number of the subinterface in the range 1–2147483647
■ Specify the type of interface or subinterface: point-to-point or multipoint.
Point-to-point is the default.
■ Examples
host1(config-if)#interface atm 0/1.20
host1(config-if)#interface atm 0/0/4.20
■ Use the no version to remove the subinterface or the logical interface.
■ See interface atm.
Setting Optional Parameters
You can also set the following parameters:
24 ■ Setting Optional Parameters
Chapter 1: Configuring ATM
■ Set the administrative state of an ATM AAL5 interface to disabled.
host1(config-if)#atm aal5 shutdown
■ Enable CAC on the interface.
host1(config-if)#atm cac 3000000 ubr 3000
■ Configure the clock source.
host1(config-if)#atm clock internal
■ Configure framing on a T3/E3 physical interface.
host1(config-if)#atm framing g751adm
■ Enable ILMI on the interface.
host1(config-if)#atm ilmi-enable
■ Set the ILMI keepalive timer.
host1(config-if)#atm ilmi-keepalive 5
■ Specify the cable length (line build-out) for the ATM interface.
host1(config-if)#atm lbo long
■ Set the administrative state of the ATM interface to disabled.
host1(config-if)#atm shutdown
■ Configure SNMP link status traps on the interface.
host1(config-if)#atm snmp trap link-status
host1(config-if)#atm aal5 snmp trap link-status
■ Set the operational mode of the physical interface to SDH STM1.
host1(config-if)#atm sonet stm-1
■ Configure the UNI version of ILMI using one of the following methods:
■ Enable auto configuration of ILMI.
host1(config-if)#atm auto-configuration
■ Set the UNI version that the router uses when ILMI link autodetermination
is unsuccessful or ILMI is disabled.
host1(config-if)#atm uni-version 4.0
■ Configure the number of virtual circuits for each virtual path.
host1(config-if)#atm vc-per-vp 128
■ Configure a virtual path tunnel and its traffic parameters.
Setting Optional Parameters ■ 25
JUNOSe 11.1.x Link Layer Configuration Guide
host1(config-if)#atm vp-tunnel 2 128
■ Enable scrambling of the ATM cell payload on a T3 or an E3 interface.
host1(config-if)#ds3-scramble
■ Set the time interval at which the router records bit and packet rates.
host1(config-if)#load-interval 90
■ Place the interface into loopback mode for router-to-router testing.
host1(config-if)#loopback diagnostic
■ Disable an interface.
host1(config-if)#shutdown
Optional Tasks on ATM 1483 Subinterfaces
You can perform the following optional tasks on ATM 1483 subinterfaces:
■ Set the MTU.
host1(config-subif)#atm atm1483 mtu 7800
■ Configure SNMP link status traps.
host1(config-subif)#atm atm1483 snmp trap link-status
■ Set the administrative state of an ATM 1483 subinterface to disabled.
host1(config-subif)#atm atm1483 shutdown
■ Configure an advisory receive speed.
host1(config-subif)#atm atm1483 advisory-rx-speed 2000
atm aal5 shutdown
■ Use to set an ATM AAL5 interface administrative state to disabled.
■ When you set the administrative state of the ATM AAL5 interface to disabled,
the router automatically disables all F5 OAM services configured on the associated
VC, and prevents the VC from receiving or transmitting F5 OAM cells.
■ Example
■ Use the no version to enable a disabled interface.
■ See atm aal5 shutdown.
atm aal5 snmp trap link-status
26 ■ Setting Optional Parameters
host1(config-if)#atm aal5 shutdown
■ Use to enable SNMP link status traps on the AAL5 layer interface.
■ Example
■ Use the no version to disable the traps.
■ See atm aal5 snmp trap link-status.
atm atm1483 advisory-rx-speed
■ Use to set an advisory receive speed for an ATM 1483 subinterface. This setting
has no effect on data forwarding. You can use it to indicate the speed of the
client interface. When traffic is tunneled with L2TP, the advisory receive speed
is sent from the LAC to the LNS. See LAC Configuration Prerequisites for additional
information about the advisory receive speed.
NOTE: If you specify an advisory receive speed greater than 4294967 kbps, the speed
is not accurately represented in the L2TP AVP, which is in bits per second (bps).
Chapter 1: Configuring ATM
host1(config-if)#atm aal5 snmp trap link-status
atm atm1483 mtu
atm atm1483 shutdown
■ The range is 0–2147483647 kbps.
■ Example
host1(config-subif)#atm atm1483 advisory-rx-speed 2000
■ Use the no version to restore the default behavior—the RX speed is not sent to
the LNS.
■ See atm atm1483 advisory-rx-speed.
■ Use to set the MTU size for an ATM 1483 subinterface.
■ The range is 256–9180.
■ Example
host1(config-subif)#atm atm1483 mtu 7800
■ Use the no version to restore the default size of 9180.
■ See atm atm1483 mtu.
■ Use to set an ATM 1483 subinterface administrative state to disabled.
■ When you set the administrative state of the ATM 1483 subinterface to disabled,
the router automatically disables all F5 OAM services configured on the associated
VC, and prevents the VC from receiving or transmitting F5 OAM cells.
■ Example
host1(config-subif)#atm atm1483 shutdown
Setting Optional Parameters ■ 27
JUNOSe 11.1.x Link Layer Configuration Guide
■ Use the no version to enable a disabled subinterface.
■ See atm atm1483 shutdown.
atm atm1483 snmp trap link-status
■ Use to enable SNMP link status traps on an ATM 1483 layer subinterface.
■ Example
host1(config-subif)#atm atm1483 snmp trap link-status
■ Use the no version to disable the traps.
■ See atm atm1483 snmp trap link-status.
atm auto-configuration
■ Use to enable autoconfiguration of ILMI. Entering the atm auto-configuration
command overrides any previous configuration of the atm uni-version command.
atm cac
■ Autoconfiguration is enabled by default.
■ Example
host1(config-if)#atm auto-configuration
■ Use the no version to disable autoconfiguration and set the ILMI parameters to
the UNI version configured using the atm uni-version command, which has a
default value of UNI 4.0.
■ See atm auto-configuration.
■ Use to enable CAC on the interface. You can set a subscription limit, so you can
oversubscribe the port, and the UBR weight, so you can limit the number of UBR
connections.
■ You cannot configure CAC on an ATM interface on which you have created a
bulk-configured VC range for use by a dynamic ATM 1483 subinterface.
Conversely, you cannot create a bulk-configured VC range on an ATM interface
on which you have configured CAC. For information about creating
bulk-configured VC ranges, see “Bulk Configuration of VC Ranges” on page 631
in “Configuring Dynamic Interfaces Using Bulk Configuration” on page 623.
■ Example
host1(config-if)#atm cac 3000000 ubr 3000
■ Use the no version to disable CAC on the interface.
■ See atm cac.
atm clock internal
■ Use to cause the ATM interface to generate the transmit clock internally.
■ You must specify one of the following:
28 ■ Setting Optional Parameters
atm framing
Chapter 1: Configuring ATM
■ module—Internal clock is from the line module (the default)
■ chassis—Internal clock is from the configured system clock
■ Example
host1(config-if)#atm clock internal
■ Use the no version to cause ATM interfaces to recover the clock from the received
signal.
■ See atm clock internal.
■ Use to configure T3 or E3 framing on an ATM interface.
■ Specify one of the following framing types for a T3 (DS3) interface:
■ cbitadm—c-bit with ATM direct mapping
■ cbitplcp—c-bit with PLCP framing (default)
atm ilmi-enable
■ m23adm—M23 ATM direct mapping
■ m23plcp—M23 with PLCP framing
■ Specify one of the following framing types for an E3 interface:
■ g832adm—G.832 ATM direct mapping
■ g751adm—G.751 ATM direct mapping
■ g751plcp—G.751 PLCP mapping (default)
■ Example
host1(config-if)#atm framing g751adm
■ Use the no version to return framing to the default:
■ For a T3 interface, the default is cbitplcp
■ For an E3 interface, the default is g751plcp
■ See atm framing.
■ Use to enable ILMI on the interface.
■ Example
atm ilmi-keepalive
host1(config-if)#atm ilmi-enable
■ Use the no version to disable ILMI on the interface.
■ See atm ilmi-enable.
Setting Optional Parameters ■ 29
JUNOSe 11.1.x Link Layer Configuration Guide
■ Use to generate ILMI keepalive messages. This value sets the time interval in
seconds between poll PDU transmissions if no sequence data PDUs are pending.
■ Example
host1(config-if)#atm ilmi-keepalive 5
■ Use the no version to disable the generation of keepalive messages.
■ See atm ilmi-keepalive.
atm lbo
■ Use to specify the cable length (line build-out) for the ATM T3 or E3 interface.
The length of cable determines power requirements.
■ Specify one of the following keywords:
■ long—A cable length in the range 0–225 feet
■ short—A cable length in the range 226–450 feet (the default)
atm shutdown
atm snmp trap link-status
■ Example
host1(config-if)#atm lbo long
■ Use the no version to restore the default value, short.
■ See atm lbo.
■ Use to set an ATM interface administrative state to disabled.
■ When you set the administrative state of the ATM interface to disabled, the router
automatically disables all F5 OAM services configured on the associated VC, and
prevents the VC from receiving or transmitting F5 OAM cells.
■ Example
host1(config-if)#atm shutdown
■ Use the no version to enable a disabled interface.
■ See atm shutdown.
■ Use to enable SNMP link status traps on the ATM layer interface.
■ Example
■ Use the no version to disable the traps.
■ See atm snmp trap link-status.
atm sonet stm-1
30 ■ Setting Optional Parameters
host1(config-if)#atm snmp trap link-status
atm uni-version
Chapter 1: Configuring ATM
Use to set the mode of operation on the physical interface to Synchronous Digital
■
Hierarchy (SDH) Synchronous Transport Mode (STM).
host1(config-if)#atm sonet stm-1
■ Use the no version to restore the default value, SONET STS-3c operation.
■ See atm sonet stm-1.
■ Use to specify the UNI version for the interface to use.
■ Valid values are 3.0, 3.1, or 4.0.
■ Example
host1(config-if)#atm uni-version 4.0
■ There is no no version.
atm vc-per-vp
atm vp-tunnel
■ See atm uni-version.
■ Use to configure the number of VCs for each VP. The router does not execute
this command when any VCs are open on the interface.
■ VCs and VP tunnels must not exist when you issue this command. If they do,
you must delete the VC and VP tunnel configuration before you issue this
command.
■ The specified value must be a power of 2, or an error message is returned.
■ The minimum number of VCs per VP is 4096 for OCx/STMx ATM line modules.
If you enter a value that is below the minimum, the router uses the minimum
value.
■ The E120 and the E320 routers support the entire VPI/VCI range; therefore, it
does not support this command.
■ Example
host1(config-if)#atm vc-per-vp 128
■ Use the no version to restore the default value.
■ See atm vc-per-vp.
■ Use to define a VP tunnel and configure the rate of traffic flow within the tunnel.
■ You specify a tunnel rate in Kbps. All circuits in the VP are restricted to the rate
that you set.
■ The tunnel rate can be a value in the range 0–4294967295, when you specify
the rate of traffic flow without the constant bit rate (CBR) service category, and
can be a value in the range 1–4294967295, when you specify the rate of traffic
flow with the CBR service class. Because the CBR service category guarantees a
Setting Optional Parameters ■ 31
JUNOSe 11.1.x Link Layer Configuration Guide
fixed amount of bandwidth to be allotted to the client, an error message is
displayed if you configure a value of 0 for the tunnel rate for CBR traffic flows.
■ If any virtual circuits are open within the VPI before the tunnel is created, the
router does not execute this command.
■ For more information about configuring a shapeless VP tunnel for QoS, see ATM
Integrated Scheduler Overview.
■ Example
host1(config-if)#atm vp-tunnel 2 128
■ Use the no version to remove the VP tunnel. When circuits are open within the
tunnel, the router does not remove the tunnel.
■ See atm vp-tunnel.
ds3-scramble
e3-scramble
load-interval
loopback
■ Use to scramble the ATM cell payload on a T3 or an E3 interface. DS3 (T3) and
E3 scrambling assists clock recovery on the receiving end of the interface.
■ Example
host1(config-if)#ds3-scramble
■ Use the no version to disable scrambling.
■ See ds3-scramble.
■ See e3-scramble.
■ Use to set the time interval at which the router calculates bit and packet rate
counters for the ATM interface.
■ You can choose a multiple of 30 seconds, in the range 30–300 seconds.
■ Example
host1(config-if)#load-interval 90
■ Use the no version to return to the default setting, 300 seconds.
■ See load-interval.
■ Use to place the interface into loopback mode.
■ Specify either:
■ diagnostic—Places the interface into internal loopback.
■ line —Places the interface into external loopback.
■ Example
32 ■ Setting Optional Parameters
Configuring OAM
Chapter 1: Configuring ATM
host1(config-if)#loopback diagnostic
■ Use the no version to remove any loopback.
■ See loopback.
This section explains:
■ Configuring F4 OAM on page 33
■ Configuring F5 OAM on page 35
■ Setting a Loopback Location ID on page 36
■ Enabling OAM Flush on page 37
■ Running ATM Ping on page 38
Configuring F4 OAM
The ATM interface does not support sending F4 segment loopback cells, but it does
respond to F4 segment loopback cells that it receives.
F4 OAM flows need their own channel, and they are identified by the VCI on which
they are sent or received. The following VCIs are reserved for F4 OAM flows for each
virtual path, and you cannot open PVCs on them:
■ VCI 3—For segment F4 flows
■ VCI 4—For end-to-end F4 flows
NOTE: You cannot enable both loopback cells and CC cells at the same time.
To set up F4 OAM:
1. Enable F4 OAM on an interface or VP. The router enables F4 OAM at the interface
level unless you specify a VPI. This example opens both segment and end-to-end
F4 OAM circuits on VPI 10.
host1(config-if)#atm oam 10
2. (Optional) Enable only segment or end-to-end loopback.
host1(config-if)#atm oam 10 seg-loopback
host1(config-if)#atm oam 10 end-loopback
3. (Optional) To cause the interface to generate end-to-end loopback cells in addition
to receiving and responding to them, set the loopback timer.
host1(config-if)#atm oam 10 end-loopback loopback-timer 20
4. (Optional) Enable CC cell flows.
Configuring OAM ■ 33
JUNOSe 11.1.x Link Layer Configuration Guide
host1(config-if)#atm oam 10 seg-loopback cc source
atm oam
■ Use to configure F4 OAM on an interface or circuit. F4 OAM is configured at the
interface level unless you specify a VPI.
■ To open F4 OAM on either a segment or end-to-end basis, use the following
keywords:
■ seg-loopback—Enables F4 segment OAM
■ end-loopback—Enables F4 end-to-end OAM
NOTE: If you do not specify either segment or end-to-end loopback, the command
applies to both end-to-end and segment F4 OAM circuits.
■ To configure CC cell flow on the PVC, use the following keywords:
■ both—Enables the PVC as both the source and the sink endpoints.
■ sink—Enables the PVC as the sink endpoint.
■ source—Enables the PVC as the source endpoint.
■ loopback-timer—When F4 OAM is enabled, the interface or circuit accepts
and responds to F4 OAM cells. However, to generate F4 loopback cells, you
must configure the loopback timer in the range 1–600 seconds. This timer
represents the frequency with which F4 loopback cells are transmitted. You
can set the loopback timer only for end-to-end loopback.
■ Example 1—Opens both F4 end-to-end and segment OAM circuits for VPI 8
host1(config-if)#atm oam 8
■ Example 2—Opens the F4 end-to-end OAM circuit for VPI 10 and enables sending
F4 end-to-end loopback cells on the circuit at a frequency of 20 seconds
host1(config-if)#atm oam 10 end-loopback loopback-timer 20
■ Example 3—Opens both F4 end-to-end and segment OAM circuits on all VPs on
this interface
host1(config-if)#atm oam
■ Example 4—Opens F4 segment OAM circuits on all VPs on this interface
34 ■ Configuring OAM
host1(config-if)#atm oam seg-loopback
■ Example 5—Opens F4 end-to-end loopback on VPI 12
host1(config-if)#atm oam 12 end-loopback
■ Example 6—Opens an F4 segment OAM circuit for VPI 8 and enables CC cell
generation on the segment
Chapter 1: Configuring ATM
host1(config-if)#atm oam 8 seg-loopback cc source
■ Use the no version to delete F4 OAM circuits. Using the options, you can delete
all F4 OAM circuits on the interface, segment or end-to-end F4 OAM circuits, or
F4 OAM circuits on a specific VPI.
■ Example 1—Deletes all F4 OAM circuits on the interface
host1(config-if)#no atm oam
■ Example 2—Deletes all F4 segment OAM circuits on the interface
host1(config-if)#no atm oam segment
■ Example 3—Deletes the F4 end-to-end OAM circuit on VPI 8
host1(config-if)#no atm oam 8 end-loopback
■ See atm oam.
Configuring F5 OAM
F5 OAM flows run over existing PVCs. The ATM interface does not support sending
F5 segment loopback cells, but it does respond to F5 segment loopback cells that it
receives.
NOTE: You cannot enable both loopback cells and CC cells at the same time.
To set up F5 OAM:
1. To enable VC integrity, which causes the ATM interface to periodically send F5
end-to-end loopback cells over a VC, use the oam keyword with the atm pvc
command.
You can include the frequency (in seconds) with which the router sends F5
end-to-end loopback cells.
host1(config-if)#atm pvc 98 38 22 aal5snap oam 300
2. (Optional) To enable CC cell flows on a circuit, use the cc keyword with the
atm pvc command. You can enable cell flows on a segment or end-to-end basis,
and you can enable the PVC as a sink, source, or both a sink and a source.
host1(config-if)#atm pvc 50 0 50 aal5snap oam cc end-to-end sink
atm pvc
When you issue the appropriate shutdown command to change the administrative
status of the corresponding ATM interface, ATM AAL5 interface, or ATM 1483
subinterface from enabled to disabled, the router automatically disables all F5 OAM
services configured on the associated VC. For more information, see “Automatic
Disabling of F5 OAM Services” on page 20.
Configuring OAM ■ 35
JUNOSe 11.1.x Link Layer Configuration Guide
■ Use the atm pvc command with the oam keyword to set up the PVC to
periodically transmit F5 end-to-end loopback cells over a VC.
■ You can use the oam keyword only if you specify one of the following
encapsulation types:
■ aal5snap
■ aal5mux ip
■ aal5autoconfig
■ The oam keyword is not available with the aal5all, aal0, or ilmi
■ Optionally, you can configure the time interval in the range 1–600 seconds
between transmissions of OAM F5 end-to-end loopback cells.
■ Use the following keywords to enable and configure CC cell flows:
■ end-to-end—Opens an end-to-end CC cell flow
■ segment—Opens a segment CC cell flow
■ sink—Enables this VC as a sink point (cell receiver)
■ source—Enables this VC as the source point (cell generator)
■ both—Enables this VC as both a sink point and a source point
■ Example 1—Enables F5 end-to-end loopback cells
host1(config-if)#atm pvc 20 20 20 aal5snap oam
■ Example 2—Enables end-to-end CC cell flow and enables the PVC as the sink
host1(config-if)#atm pvc 5 0 5 aal5autoconfig oam cc end-to-end sink
■ Use the no version of the atm pvc command without the oam keyword to disable
F5 OAM on the PVC and without the cc keyword to disable CC cell flows on the
PVC. For example, the following command disables CC cell flow configured in
Example 2.
host1(config-if)#no atm pvc 5 0 5 aal5autoconfig
■ See atm pvc.
Setting a Loopback Location ID
To enable other nodes to specifically send OAM loopback cells to the ATM interface,
set the location ID of the ATM interface or circuit.
36 ■ Configuring OAM
host1(config-if)#atm oam loopback-location 01090708
NOTE: Because the router is a connection endpoint, the default loopback location
ID is all 1s (ones). This command enables you to specify a nondefault value.
atm oam loopback-location
■
■ Example
■ Use the no version to return the loopback location ID to the default value, all 1s
■ See atm oam loopback-location.
Chapter 1: Configuring ATM
Use to set the location ID of the ATM interface. The location ID is a 4-octet field,
and the default value is all 1s (ones).
■ You can set a specific value to identify this ATM interface as the intended
recipient of OAM loopback cells.
■ You can also set the location ID to all 0s (zeros).
For information about how the router handles loopback cells based on location
ID, see Table 6 on page 20.
host1(config-if)#atm oam loopback-location 01090708
(ones).
Enabling OAM Flush
atm oam flush
You can use the atm oam flush command to enable the OAM flush feature for an
ATM interface. When OAM flush is enabled, the router ignores all OAM cells received
on the interface, and stops sending OAM cells on this interface.
You can also issue the atm oam flush command with the optional alarm-cells
keyword to cause the router to ignore only AIS and RDI cells and to accept all other
OAM cells. This is useful in diagnostic situations when you might want to exclude
alarm conditions.
NOTE: The OAM flush feature is supported on all E Series ATM module combinations.
■ Use to configure the router to ignore all OAM cells received on an ATM interface,
and to stop sending OAM cells on this interface.
■ To cause the router to ignore only AIS and RDI cells and to accept all other OAM
cells, use the alarm-cells keyword.
■ Example
host1(config-if)#atm oam flush
■ Use the no version to disable OAM flush on the interface.
■ See atm oam flush.
Configuring OAM ■ 37
JUNOSe 11.1.x Link Layer Configuration Guide
Running ATM Ping
Keep in mind the following when you use ATM ping:
■ Before you can run ATM ping, you need to add a PVC for the VPI and VCI over
which you run the ping.
■ Because ATM ping requires the receipt of OAM cells, make sure that the receipt
and transmission of OAM cells is not disabled (using “atm oam flush” on page 37
). To reenable the receipt and transmission of OAM cells, enter no atm oam
flush.
■ Disabling receipt of OAM cells during a ping operation stops all outstanding ping
operations. You need to manually restart the ping operation after receipt of OAM
cells for the interface is enabled.
■ Because ATM ping is a dynamic (on-demand) operation, none of the configuration
related to ATM ping is saved. To avoid acquiring excessive bandwidth for OAM,
the number of outstanding ping operations on each interface is limited to 12.
ping atm interface atm
■ Use to send loopback cells from an ATM interface or circuit.
■ The VPI and VCI fields determine the type of loopback cells used for the ping
operation. By default F5 end-to-end loopback OAM cells are used.
■ To send F4 segment loopback cells, set the VCI to 3.
■ To send F4 end-to-end loopback cells, set the VCI to 4.
■ Use the end-loopback keyword to send the ping to the connection endpoint.
■ Use the seg-loopback keyword to send the ping to the first segment point (for
example, the next neighbor switch).
■ Use the destination option to specify the value of the location ID included in the
loopback cell. The location ID is a 16-octet field, and the destination portion is
4 octets. You can set the location ID to a specific destination or to 0s (zeros) or
1s (ones).
■ If you set the destination to 0, the loopback location ID in the loopback cell
is initialized to all 0s, and each segment point in the network responds to
the ping.
■ If you set the destination to 1s, the loopback location ID in the loopback cell
is initialized to all 1s, and only the connection endpoint responds to the ping.
■ If you use the default value of 0xFFFFFFFF, the loopback location ID in the
loopback cell is initialized to all 1s.
38 ■ Configuring OAM
For information about how the router handles loopback cells based on location
ID, see Table 6 on page 20.
■ The count keyword sets the number of OAM loopback cells to send to the
destination. The default value is 5. The maximum is 32.
■ The timeout keyword sets the amount of time to wait for a response to the sent
OAM loopback cell. The default value is 5 seconds.
Chapter 1: Configuring ATM
■ The following characters can appear in the display after the ping command has
been issued:
■ !—Each exclamation point indicates that a reply was received
■ .—Each period indicates that the ping timed out while waiting for a reply
■ Example 1—This example generates end-to-end loopback cells for VPI=0 and
VCI=105 on ATM interface 2/0. The count value is 5 OAM loopback cells, and
the timeout value is 2 seconds.
host1#ping atm interface atm 2/0 0 105 end-loopback count 5 timeout 2
Sending 5 53-byte OAM end-to-end loopback Echoes timeout is 2 secs
Press Ctrl+c to stop
!!!!!
Success rate = 100% (5/5), round-trip min/avg/max = 0/4/10 ms
■ Example 2—This example generates segment loopback cells for VPI=0 and
VCI=105 on ATM interface 2/0. The destination is set to 0xFFFFFFFF, the count
value is 3 OAM loopback cells, and the timeout value is 1 second.
host1#ping atm interface atm 2/0 0 105 seg-loopback 0xFFFFFFFF count 3
timeout 1
Sending 3 53-byte OAM segment loopback Echoes timeout is 1 secs
Press Ctrl+c to stop
!!!
Success rate = 100% (3/3), round-trip min/avg/max = 0/3/10 ms
■ There is no no version.
■ See ping atm interface atm.
Configuring an NBMA Interface
You configure an ATM NBMA 1483 subinterface in a manner similar to configuring
a standard ATM 1483 subinterface. When you specify a subinterface, however, you
must select the multipoint option if you plan to add multiple circuits to form an NBMA
interface. If you do not select multipoint, the subinterface defaults to point-to-point,
and only a single circuit can be affiliated with that subinterface.
You can configure one or more PVCs and associate them with the subinterface you
create. Also, you can enable InARP and identify a refresh rate on each specific circuit.
For each NMBA interface, either InARP must be enabled, or a static map entry must
be provided for each circuit owned by the interface; otherwise, transmitting over
that circuit is impossible.
NOTE: NBMA interfaces support only the aal5snap encapsulation.
To configure an NBMA interface:
1. Configure a physical interface.
host1(config)#interface atm 2/0
Configuring an NBMA Interface ■ 39
JUNOSe 11.1.x Link Layer Configuration Guide
2. Configure an ATM 1483 subinterface.
host1(config-if)#interface atm 2/0.2 multipoint
3. Configure PVCs by specifying the VCD, VPI, VCI, and encapsulation type.
host1(config-subif)#atm pvc 1 1 1 aal5snap inarp 10
host1(config-subif)#atm pvc 2 2 2 aal5snap
4. (Optional) Specify InARP and a refresh rate (also optional).
host1(config-subif)#atm pvc 3 3 3 aal5snap inarp 5
host1(config-subif)#atm pvc 4 4 4 aal5snap inarp
5. Assign an IP address and subnet mask to the PVC.
host1(config-subif)#ip address 192.32.10.20 255.255.255.0
6. (Optional) Use the appropriate show commands to verify your configuration.
host1#show atm interface atm 2/0
host1#show atm map
host1#show nbma arp atm 2/0
host1#show atm vc atm 2/0 2
host1#show atm subinterface atm 2/0.2
Creating an NBMA Static Map
Static mapping creates an association between IP address–ATM PVC pairs for one
or more member circuits of an ATM 1483 NBMA interface. Not every circuit
necessarily gets the required association from a static map.
In the following procedure, you can repeat Step 2 for each circuit you want to map.
You can associate with an interface a map group name that you have not already
established. When you define the map list, the name is associated with that interface.
You can perform Steps 3 and 4 before Steps 1 and 2 without affecting the results.
To set up a static map:
1. Create a map list by naming it.
host1(config)#map-list charlie
2. Associate a protocol and an address with a specific virtual circuit.
host1(config-map-list)#ip 192.168.13.13 atm-vc 1 broadcast
3. Specify an ATM interface.
host1(config-if)#interface atm 2/0
4. Associate the map list with the interface.
host1(config-if)#map-group charlie
40 ■ Creating an NBMA Static Map
atm pvc
Chapter 1: Configuring ATM
■ Use to configure a PVC on an ATM interface.
■ InARP and refresh rate are optional parameters.
■ InARP determines whether InARP requests are used and is specified on a
per-circuit basis. If you disable InARP, you must use a static map table entry.
Transmission over the circuit cannot occur unless you use either InARP or static
map table entries.
■ The default refresh rate is 15 minutes.
■ You can configure InARP only if you specify the aal5snap encapsulation type.
■ Example
host1(config-if)#atm pvc 6 0 11 aal5snap inarp 10
■ Use the no version to remove the specified PVC.
■ See atm pvc.
interface atm
ip atm-vc
■ Use to configure an ATM interface or subinterface type.
■ For information about specifying the ATM interface or subinterface, see “interface
atm” on page 24.
■ Specify multipoint to identify the subinterface as NBMA.
■ Examples
host1(config-if)#interface atm 0/1.20
host1(config-if)#interface atm 0/0/4.20
■ Use the no version to remove the subinterface or the logical interface.
■ See interface atm.
■ Use to associate a protocol and address with a specific virtual circuit.
■ Use this command repeatedly for each circuit to be mapped.
■ This command is available in Map List Configuration mode only.
■ Example
host1(config-map-list)#ip 192.168.13.13 atm-vc 1 broadcast
map-group
■ Use the no version to remove the association.
■ See ip atm-vc.
Creating an NBMA Static Map ■ 41
JUNOSe 11.1.x Link Layer Configuration Guide
■ Use to associate the map list with an NBMA interface when configuring static
mapping.
■ You can issue this command before or after the map-list command without
changing anything.
■ This command is available in Interface Configuration mode only.
■ See the map-list command.
■ Example
host1(config-if)#map-group charlie
■ Use the no version to remove the association.
■ See map-group.
map-list
■ Use to create a map list when configuring static mapped NBMA interfaces.
■ Limit the name of the map list to no more than 31 characters.
■ You can create multiple map lists; however, you can associate only one map list
with each physical interface.
■ If a map list contains an entry for a VCD that was previously configured to run
InARP, the map-group command fails. If this is the case, either reconfigure the
circuit with InARP disabled, or remove the entry for that circuit from the map
list.
■ Example
host1(config)#map-list charlie
■ Use the no version to remove the map list.
■ See map-list.
Assigning Descriptions to Interfaces
You can use the description commands to assign a text description or an alias to an
interface, so that other show commands can display that information.
atm aal5 description
■ Use to assign a text description or alias to an ATM AAL5 interface.
■ Use the show atm aal5 interface command to display the text description.
■ Example
host1(config-if)#atm aal5 description boston01
■ Use the no version to remove the text description or alias.
■ See atm aal5 description.
42 ■ Assigning Descriptions to Interfaces
atm atm1483 description
atm description
Chapter 1: Configuring ATM
■ Use to assign a text description or alias to an ATM 1483 subinterface.
■ The description can be a maximum of 255 characters.
■ Use the show atm subinterface command to display the text description.
■ Example
host1(config-subif)#atm atm1483 description nyc33
■ Use the no version to remove the text description or alias.
■ See atm atm1483 description.
■ Use to assign a text description or alias to the ATM interface.
■ The description can be a maximum of 255 characters and can include the
# (pound sign) character.
■ The first 32 characters of the ATM description are pushed out to RADIUS during
authentication and accounting.
■ Use the show atm interface command to display the description.
■ Example
host1(config-if)#atm description myAtm
■ Use the no version to remove the description or alias.
■ See atm description.
Sending Interface Descriptions to AAA
During authentication the router sends ATM interface descriptions to AAA. AAA
passes the descriptions to RADIUS, and they can appear in the Calling-Station-Id
attribute [31]. (For information about RADIUS and the Calling-Station-ID attribute,
see JUNOSe Broadband Access Configuration Guide.)
By default, the router sends the major interface descriptions to AAA on the SRP. You
can configure the router to send VP interface descriptions in place of the major
interface descriptions, or to send ATM 1483 subinterface descriptions to AAA on the
line module. As a result, the VP or ATM 1483 subinterface descriptions can provide
a convenient way to identify or group broadband access subscribers.
If you set up multiple interface descriptions, they have the following precedence:
1. ATM 1483 subinterface description
2. VP interface description
3. Major interface description
Sending Interface Descriptions to AAA ■ 43
JUNOSe 11.1.x Link Layer Configuration Guide
Assigning Descriptions to Virtual Paths
To assign a description to an individual VP on an ATM interface, use the atm
vp-description command. The VP description does not affect existing descriptions
configured for the ATM interface or ATM 1483 subinterface on which the VP resides.
However, if you delete the ATM interface, the descriptions of all VPs residing on that
interface are also deleted. In addition, if you decrease the VPI range by issuing the
atm vc-per-vp command, the router deletes the descriptions of any VPs that are
removed.
To display the VP description, use the show atm vp-description command, as
described in “Using ATM show Commands” on page 74. Although you need not
configure a VP tunnel to specify a VP description, the router also displays the VP
description in the output of the show atm vp-tunnel command.
Exporting ATM 1483 Subinterface Descriptions
To assign a description to an ATM 1483 subinterface and configure the router to
send the ATM 1483 VC interface descriptions to the line module:
1. Configure a text description for ATM 1483 subinterfaces with the atm atm1483
description command. This description is included in the interface identifier
that is sent to AAA.
To configure this feature for ATM 1483 subinterfaces, enter this command in
Profile Configuration mode. See “Configuring ATM 1483 Dynamic Subinterfaces”
on page 628 in “Configuring Dynamic Interfaces Using Bulk Configuration” on
page 623.
host1(config-subif)#atm atm1483 description VC_atm1
2. Set up the router to export ATM 1483 VC interface descriptions to the line module.
host1(config)#atm atm1483 export-subinterface-description
3. (Optional) Display the configuration of the export ATM 1483 VC interface
descriptions feature with the show atm atm1483 command.
host1#show atm atm1483
ATM1483 IF Descriptions exported
4. (Optional) Display the interface descriptions with the show atm subinterface
atm command.
atm atm1483 description
■ Use to assign a text description or alias to an ATM 1483 subinterface.
■ The description can be a maximum of 255 characters.
■ Example
host1(config-subif)#atm atm1483 description nyc33
44 ■ Sending Interface Descriptions to AAA
■ Use the no version to remove the text description or alias.
■ See atm atm1483 description.
atm atm1483 export-subinterface-description
■ Use to export ATM 1483 VC interface descriptions to the line module. Descriptions
for ATM 1483 subinterfaces are configured with the atm atm1483 description
command.
■ The description can have up to 255 characters; however, when the description
is sent to the line module, it is truncated to 32 characters.
■ Example
host1(config)#atm atm1483 export-subinterface-description
■ Use the no version to restore the default behavior, in which ATM 1483 interface
descriptions are not exported to the line module.
■ See atm atm1483 export-subinterface-description.
Chapter 1: Configuring ATM
atm vp-description
■ Use to assign a text description to an individual VP on an ATM interface or
subinterface.
■ You must specify the VPI of the VP to which you want to assign the description.
■ The description string can be a maximum of 32 characters.
■ The VP description is stored in NVS and persists after a reboot.
■ Use the show atm vp-description command to display the text description.
■ Example
host1(config-if)#atm vp-description 2 vpi2Subscribers
■ Use the no version to restore the default value, a null string.
■ See atm vp-description.
Configuring Individual ATM PVC Parameters
As an alternative to using the atm pvc command to configure ATM PVC parameters
with a single command, you can access ATM VC Configuration mode to configure
individual ATM PVC parameters with separate commands, one parameter at a time.
You can configure parameters for the service category, encapsulation method, F5
OAM options, and Inverse ARP.
The following sections explain the benefits of using ATM VC Configuration mode and
describes how to configure the ATM VC mode :
■ Benefits on page 46
■ Creating Control PVCs on page 46
■ Creating Data PVCs on page 47
Configuring Individual ATM PVC Parameters ■ 45
JUNOSe 11.1.x Link Layer Configuration Guide
■ Configuring the Service Category for Data PVCs on page 48
■ Configuring Encapsulation for Data PVCs on page 50
■ Configuring F5 OAM for Data PVCs on page 51
■ Configuring Inverse ARP for Data PVCs on page 54
Benefits
Using commands in ATM VC Configuration mode to configure individual ATM PVC
parameters provides the following benefits:
■ Commands in ATM VC Configuration mode are less complex and easier to use.
With the atm pvc command and keywords, you configure multiple PVC attributes
on a single command line. In addition, configuration attributes available only
for control (ILMI and signaling) PVCs or only for data PVCs are not mutually
exclusive.
By contrast, ATM VC Configuration mode provides commands to configure each
parameter individually, and makes a clearer distinction between configuration
of control PVCs and configuration of data PVCs.
■ ATM VC Configuration mode interoperates with the atm pvc command.
You can configure all of the parameters currently supported by the atm pvc
command from within ATM VC Configuration mode. In addition, you can create
a PVC with the atm pvc command and modify or delete the same PVC by using
ATM VC Configuration mode. Conversely, you can modify (with certain
restrictions) or delete a PVC created in ATM VC Configuration mode by using
the atm pvc command.
■ ATM VC Configuration mode supports additional F5 OAM alarm surveillance and
VC integrity options.
In most cases, you can use either an ATM VC Configuration mode command or
the atm pvc command to configure ATM PVC parameters. However, to configure
F5 OAM alarm surveillance parameters (by using the oam ais-rdi command) or
VC integrity parameters (by using the oam retry command), you must use only
ATM VC Configuration mode. There are no equivalent atm pvc commands to
configure these parameters.
You can, however, continue to use the atm pvc command to enable VC integrity
and modify the loopback frequency of an ATM data PVC.
NOTE: If you have existing configuration scripts that use the atm pvc command, we
recommend that you continue to use the atm pvc command to configure all ATM
PVC parameters except those that require you to use the oam ais-rdi command or
oam retry command in ATM VC Configuration mode.
Creating Control PVCs
A control PVC, also referred to as a control circuit, supports services such as ILMI to
manage and control ATM networks. You must create a control PVC on an ATM major
46 ■ Configuring Individual ATM PVC Parameters
pvc
Chapter 1: Configuring ATM
interface, and not on an ATM 1483 subinterface that is stacked above an ATM major
interface.
To create a control PVC, you issue the pvc command from Interface Configuration
mode. However, unlike the other tasks in this section, configuring a control PVC with
the pvc command does not access ATM VC Configuration mode.
For example, the following commands create a control PVC with VCD 10, VPI 0,
VCI 16, and ILMI encapsulation.
host1(config)#interface atm 3/0
host1(config-if)#pvc 10 0/16 ilmi
host1(config-if)#
Regardless of whether you use the pvc command or the atm pvc command to create
a control PVC, you cannot modify the VCD, VPI, or VCI values after they have been
configured.
Creating Data PVCs
■ Use from Interface Configuration mode to create a control PVC for Integrated
Local Management Interface (ILMI).
■ To create a control PVC, specify the VCD, VPI and VCI (in the format vpi/vci),
and the ilmi keyword.
■ Example
host1(config-if)#pvc 5 0/5 ilmi
■ Use the no version to remove the specified control PVC from the router.
■ See pvc.
A data PVC, also referred to as a data circuit, is an ATM PVC that carries data. You
must create a data PVC on an ATM 1483 subinterface that is stacked above an ATM
major interface, and not on the ATM major interface itself.
To create a data PVC, you issue the pvc command from Subinterface Configuration
mode to access ATM VC Configuration mode. From ATM VC Configuration mode,
you can then do either of the following:
■ Issue the exit command, which creates a data PVC that uses default values for
service category (unspecified bit rate without a peak cell rate), encapsulation
type (aal5snap), F5 OAM (disabled), and Inverse ARP (disabled).
■ Issue commands to configure or modify data PVC attributes including the service
category, encapsulation type, F5 OAM, and Inverse ARP.
For example, the following commands create a data PVC with VCD 32, VPI 0, VCI 100
and default values for the other attributes. Issuing the exit command causes the
configuration to take effect.
Configuring Individual ATM PVC Parameters ■ 47
JUNOSe 11.1.x Link Layer Configuration Guide
host1(config)#interface atm 3/2.2
host1(config-subif)#pvc 32 0/100
host1(config-subif-atm-vc)#exit
host1(config-subif)#
Regardless of whether you use the pvc command or the atm pvc command to create
a data PVC, you cannot modify the VCD, VPI, or VCI values after they have been
configured.
pvc
■ Use from Subinterface Configuration mode to create a data PVC and access ATM
VC Configuration mode, from which you can configure and modify individual
PVC attributes one at a time.
■ To create a basic data PVC with default values for service category, encapsulation
type, F5 OAM, and Inverse ARP, specify the VCD and the VPI and VCI (in the
format vpi/vci).
■ You must issue the exit command from ATM VC Configuration mode for the
configuration to take effect.
■ Example
host1(config-subif)#pvc 10 15/50
host1(config-subif-atm-vc)#exit
■ Use the no version to remove the specified data PVC from the router.
■ See pvc.
Configuring the Service Category for Data PVCs
You can use individual commands in ATM VC Configuration mode to configure each
supported service category on a data PVC, or to restore the default service category,
unspecified bit rate (UBR) without a peak cell rate (PCR).
For example, the following commands configure a data PVC that uses the constant
bit rate (CBR) service category with a nondefault PCR (10,000 Kbps). Issuing the exit
command causes the configuration to take effect.
host1(config)#interface atm 3/0.3
host1(config-subif)#pvc 6 0/100
host1(config-subif-atm-vc)#cbr 10000
host1(config-subif-atm-vc)#exit
host1(config-subif)#
cbr
■ Use to configure the CBR service category on an ATM data PVC.
■ You must specify a PCR, in Kbps, in the range 1–149760 (for OC3 ATM modules)
or 1–599040 (for OC12 ATM modules).
■ You must issue the exit command from ATM VC Configuration mode for the
configuration to take effect.
48 ■ Configuring Individual ATM PVC Parameters
ubr
Chapter 1: Configuring ATM
■ Example
host1(config-subif-atm-vc)#cbr 15000
host1(config-subif-atm-vc)#exit
■ Use the no version to restore the default service category, UBR without a PCR.
■ See cbr.
■ Use to configure the UBR service category on an ATM data PVC.
■ You can optionally specify a PCR, in Kbps, in the range 0–149760 (for OC3 ATM
modules) or 0–599040 (for OC12 ATM modules).
■ You must issue the exit command from ATM VC Configuration mode for the
configuration to take effect.
■ Example
vbr-nrt
host1(config-subif-atm-vc)#ubr 5000
host1(config-subif-atm-vc)#exit
■ Use the no version to restore the default service category, UBR without a PCR.
■ See ubr.
■ Use to configure the variable bit rate, nonreal time (VBR-NRT) service category
on an ATM data PVC.
■ You must specify all of the following parameters:
■ PCR, in Kbps, in the range 0–149760 (for OC3 ATM modules) or 0–599040
(for OC12 ATM modules)
■ SCR, in Kbps, in the range 0–149760 (for OC3 ATM modules) or 0–599040
(for OC12 ATM modules)
■ Maximum burst size (MBS), in cells, in the range 0–16777215
■ You must issue the exit command from ATM VC Configuration mode for the
configuration to take effect.
■ Example
host1(config-subif-atm-vc)#vbr-nrt 50000 10000 150
host1(config-subif-atm-vc)#exit
vbr-rt
■ Use the no version to restore the default service category, UBR without a PCR.
■ See vbr-nrt.
Configuring Individual ATM PVC Parameters ■ 49
JUNOSe 11.1.x Link Layer Configuration Guide
■ Use to configure the variable bit rate, real time (VBR-RT) service category on an
ATM data PVC.
■ You must specify all of the following parameters:
■ PCR, in Kbps, in the range 0–149760 (for OC3 ATM modules) or 0–599040
(for OC12 ATM modules)
■ SCR, in Kbps, in the range 0–149760 (for OC3 ATM modules) or 0–599040
(for OC12 ATM modules)
■ Maximum burst size (MBS), in cells, in the range 0–16777215
■ You must issue the exit command from ATM VC Configuration mode for the
configuration to take effect.
■ Example
host1(config-subif-atm-vc)#vbr-rt 200000 30000 400
host1(config-subif-atm-vc)#exit
■ Use the no version to restore the default service category, UBR without a PCR.
■ See vbr-rt.
Configuring Encapsulation for Data PVCs
The encapsulation method on a data PVC represents the format of the data units that
traverse the circuit. You can use the encapsulation command in ATM VC
Configuration mode to configure the encapsulation method for a data PVC, or to
restore the default encapsulation method, aal5snap.
For example, the following commands configure a data PVC that uses aal5all
encapsulation. Issuing the exit command causes the configuration to take effect.
host1(config)#interface atm 3/0.3
host1(config-subif)#pvc 6 0/250
host1(config-subif-atm-vc)#encapsulation aal5all
host1(config-subif-atm-vc)#exit
host1(config-subif)#
encapsulation
■ Use to configure the encapsulation method on an ATM data PVC.
■ Specify one of the following encapsulation types:
■ aal0—Causes the router to receive raw ATM cells on this PVC and forward
the cells without performing AAL5 packet reassembly
■ aal5all—Configures ATM over MPLS passthrough connections; the router
passes through all ATM AAL5 traffic without interpreting it
■ aal5autoconfig—Enables autodetection of the 1483 encapsulation (LLC/SNAP
or VC multiplexed)
50 ■ Configuring Individual ATM PVC Parameters
■ aal5mux ip—Configures a VC-based multiplexed circuit used for IP only
■ aal5snap—Configures an LLC encapsulated circuit; an LLC/SNAP header
precedes the protocol datagram; this is the default encapsulation method
■ You must issue the exit command from ATM VC Configuration mode for the
configuration to take effect.
■ Example
host1(config-subif-atm-vc)#encapsulation aal5mux ip
host1(config-subif-atm-vc)#exit
■ Use the no version to restore the default encapsulation method, aal5snap.
■ See encapsulation.
Configuring F5 OAM for Data PVCs
Chapter 1: Configuring ATM
In ATM VC Configuration mode, you can use the individual commands listed in Table
7 on page 51 to configure nondefault values for F5 OAM services.
Table 7: F5 OAM Configuration Tasks and Associated Commands
Use This CommandTo Configure
signal (AIS) and remote defect indication (RDI)
fault management cells
of VC integrity
oam ais-rdiSurveillance parameters for alarm indication
oam ccContinuity check (CC) verification
oam-pvcGeneration of F5 loopback cells and enabling
oam retryParameters for VC integrity
For more information about OAM parameters, see “Operations, Administration, and
Management of ATM Interfaces” on page 15.
NOTE: The oam-ais rdi command and the oam retry command are available only
in ATM VC Configuration mode. There is no equivalent atm pvc command to configure
these F5 OAM alarm surveillance and VC integrity parameters.
For example, the following commands enable VC integrity on a data PVC with a
nondefault loopback frequency (30 seconds). Issuing the exit command causes the
configuration to take effect.
host1(config)#interface atm 3/0.0
host1(config-subif)#pvc 32 0/32
host1(config-subif-atm-vc)#oam-pvc manage 30
Configuring Individual ATM PVC Parameters ■ 51
JUNOSe 11.1.x Link Layer Configuration Guide
host1(config-subif-atm-vc)#exit
host1(config-subif)#
The following commands, which are available only in ATM VC Configuration mode,
configure nondefault VC integrity and alarm surveillance parameters on a data PVC.
In this example, the VC integrity parameters configured with the oam retry command
include the up retry count (4), down retry count (6), and retry frequency (2). The
alarm surveillance parameters configured with the oam ais-rdi command include
the alarm down count (2) and alarm clear timeout duration (4 seconds). Issuing the
exit command causes the configuration to take effect.
host1(config)#interface atm 3/0.0
host1(config-subif)#pvc 32 0/32
host1(config-subif-atm-vc)#oam retry 4 6 2
host1(config-subif-atm-vc)#oam ais-rdi 2 4
host1(config-subif-atm-vc)#exit
host1(config-subif)#
oam ais-rdi
■ Use to configure surveillance parameters for AIS and RDI F5 OAM fault
management cells on an ATM data PVC.
■ You can optionally specify the following values:
■ alarmDownCount—Number of successive alarm cells, in the range 1–60, for
the router to receive before reporting that a PVC is down; the default value
is 1
■ alarmClearTimeout—Number of seconds, in the range 3–60, for the router
to wait before reporting that a PVC is up after the PVC has stopped receiving
alarm cells; the default value is 3
■ To configure these alarm surveillance parameters, you must use the oam ais-rdi
command in ATM VC Configuration mode. There is no equivalent atm pvc
command to configure these parameters.
■ You must issue the exit command from ATM VC Configuration mode for the
configuration to take effect.
■ Example
host1(config-subif-atm-vc)#oam ais-rdi 5 10
host1(config-subif-atm-vc)#exit
■ Use the no version to restore the default values for the alarm down count and
alarm clear timeout duration.
■ See oam ais-rdi.
oam cc
■ Use to enable F5 OAM CC verification on an ATM data PVC.
■ You can optionally specify one of the following values to configure CC cell flows:
■ segment—Opens an F5 OAM CC segment cell flow
■ end-to-end—Opens an F5 OAM CC end-to-end cell flow
52 ■ Configuring Individual ATM PVC Parameters
Chapter 1: Configuring ATM
■ You must specify one of the following values to enable CC verification:
■ source—Enables this VC as the source point (cell generator)
■ sink—Enables this VC as a sink point (cell receiver)
■ both—Enables this VC as both a sink point and a source point
■ You must issue the exit command from ATM VC Configuration mode for the
configuration to take effect.
■ Example 1—Enables CC verification with a source endpoint
host1(config-subif-atm-vc)#oam cc source
host1(config-subif-atm-vc)#exit
■ Example 2—Opens an F5 OAM CC segment cell flow and enables CC verification
with a sink endpoint
host1(config-subif-atm-vc)#oam cc segment sink
host1(config-subif-atm-vc)#exit
oam-pvc
■ Use the no version to disable F5 OAM CC verification and restore the default
setting for cell termination, end-to-end.
■ See oam cc.
■ Use to enable generation of F5 OAM loopback cells on an ATM data PVC and,
optionally, enable F5 OAM VC integrity features on the circuit.
■ Use this command only on data PVCs configured with aal5snap, aal5autoconfig,
or aal5 mux ip encapsulation; the command is not valid for data PVCs configured
with other encapsulation types.
■ To enable F5 OAM VC integrity on the PVC, use the manage keyword.
■ You can optionally specify the number of seconds, in the range 1–600, for the
router to wait between the transmission of loopback cells during normal
operation; the default value is 10.
■ You must issue the exit command from ATM VC Configuration mode for the
configuration to take effect.
■ Example
host1(config-subif-atm-vc)#oam-pvc manage 15
host1(config-subif-atm-vc)#exit
■ Use the no version to restore the default behavior, which disables F5 OAM VC
integrity on the router and restores the default value for loopback frequency,
10 seconds.
oam retry
■ See oam-pvc/
Configuring Individual ATM PVC Parameters ■ 53
JUNOSe 11.1.x Link Layer Configuration Guide
■ Use to configure F5 OAM VC integrity parameters on an ATM data PVC.
■ You can optionally specify the following values:
■ upRetryCount—Number of successive loopback cell responses, in the range
1–60, for the router to receive before reporting that a PVC is up; default
value is 3
■ downRetryCount—Number of successive loopback cell responses, in the range
1–60, for the router to miss before reporting that a PVC is down; default
value is 5
■ retryFrequency—Number of seconds, in the range 1–600, for the router to
wait between the transmission of loopback cells when it is verifying the state
of the PVC; default value is 1
■ To configure these VC integrity parameters, you must use the oam retry
command in ATM VC Configuration mode. There is no equivalent atm pvc
command to configure these parameters.
■ You must issue the exit command from ATM VC Configuration mode for the
configuration to take effect.
■ Example
host1(config-subif-atm-vc)#oam retry 5 6 3
host1(config-subif-atm-vc)#exit
■ Use the no version to restore the default values for the up retry count, down
retry count, and retry frequency parameters.
■ See oam retry.
Configuring Inverse ARP for Data PVCs
You can use the inarp command in ATM VC Configuration mode to enable Inverse
ARP (InARP) on a data PVC that resides on an ATM 1483 NBMA subinterface
configured with the multipoint option. The PVC must use the default encapsulation
method, aal5snap. For more information about InARP, see “Configuring an NBMA
Interface” on page 39.
For example, the following commands enable InARP with a nondefault refresh rate
(10 minutes) on a data PVC. The PVC uses aal5snap encapsulation by default. Issuing
the exit command causes the configuration to take effect.
host1(config)#interface atm 3/2.1 multipoint
host1(config-subif)#pvc 6 0/11
host1(config-subif-atm-vc)#inarp 10
host1(config-subif-atm-vc)#exit
host1(config-subif)#
inarp
54 ■ Configuring Individual ATM PVC Parameters
Chapter 1: Configuring ATM
■ Use to enable Inverse ARP on an ATM PVC that resides on an ATM 1483 NBMA
subinterface and uses the default encapsulation method, aal5snap.
■ You can optionally specify an Inverse ARP refresh rate, in the range 1–60 minutes;
the default value is 15.
■ You must issue the exit command from ATM VC Configuration mode for the
configuration to take effect.
■ Example
host1(config-subif-atm-vc)#inarp 5
host1(config-subif-atm-vc)#exit
■ Use the no version to restore the default behavior, which disables Inverse ARP
on the router.
■ See inarp.
Configuring ATM VC Classes
As an alternative to configuring individual parameters for ATM data PVCs, you can
access ATM VC Class Configuration mode to configure a class of attributes for an
ATM data PVC. A VC class is a set of attributes for a virtual circuit (VC) that can include
the service category, encapsulation method, F5 OAM options, and Inverse ARP.
After you configure the VC class, you then apply the attributes in the class as a group
by assigning the VC class to one of the following:
■ An individual PVC
■ All PVCs created on a specified static ATM major interface
■ All PVCs created on a specified static ATM 1483 subinterface
■ A base profile from which bulk-configured VC ranges are created on a dynamic
ATM 1483 subinterface
VC class assignments are valid only for ATM data PVCs created with the pvc
command. Assigning a VC class to a PVC created with the atm pvc command, or to
a control (ILMI) PVC, has no effect. For information about creating a data PVC by
using the pvc command, see “Creating Data PVCs” on page 47.
NOTE: For information about the total number of VC classes supported on the router,
see JUNOSe Release Notes, Appendix A, System Maximums.
Benefits
Using VC classes to configure and assign attributes to ATM data PVCs provides the
following benefits:
■ VC classes enable you to classify and group ATM PVCs based on the OAM and
traffic requirements of their associated subscribers.
Configuring ATM VC Classes ■ 55
JUNOSe 11.1.x Link Layer Configuration Guide
In a typical scenario, you might group subscribers based on their OAM and traffic
requirements, and then create a VC class for each subscriber group. For example,
you might create two VC classes: premium-subscriber-class and
economy-subscriber-class.
In premium-subscriber-class, you might enable F5 OAM VC integrity (with the
oam-pvc manage command), and configure a traffic class that has a higher
scheduling priority, such as CBR (with the cbr command). Conversely, in
economy-subscriber-class, you might retain the default setting that disables F5
OAM VC integrity, and configure a traffic class that has a lower scheduling priority,
such as UBR with or without a PCR (with the ubr command). By assigning each
VC class to the appropriate interfaces or individual circuits, you can group and
manage the PVCs associated with the VC class based on the network requirements
of the subscribers they serve.
■ VC classes facilitate modifications to PVC attributes.
If the OAM or traffic requirements change for a particular subscriber group, you
can simply reconfigure the VC class associated with the PVCs for that subscriber
group. This method is easier and less time-consuming than having to modify the
attributes for a large number of PVCs by using individual CLI commands.
Precedence Levels
Modifications to the attributes in a VC class affect PVCs that are already associated
with this VC class as well as PVCs subsequently created for this class.
Precedence levels play an important role in determining how the router assigns the
attribute values for statically created and dynamically created PVCs that have
associated VC classes.
Precedence Levels for Static PVCs
For PVCs that are statically created, the router determines the PVC attribute values
according to the following precedence levels, in order from highest precedence to
lowest precedence:
1. The most recent explicitly set value for a PVC attribute always has the highest
precedence and overrides any settings in the VC class. Explicitly set values for
PVC attributes are those values configured with the CLI (by using the atm pvc
command or commands in ATM VC Configuration mode), SNMP, or assigned
by RADIUS.
2. If an attribute value is not explicitly specified, the router takes the value for that
attribute from the assigned VC class, in the following order of precedence:
a. Attribute value specified in the VC class assigned to this PVC
b. Attribute value specified in the VC class assigned to the ATM 1483
c. Attribute value specified in the VC class assigned to the ATM major interface
3. If no PVC attributes are explicitly specified and no VC class assignments exist,
the router applies the default values for the commands listed in Table 8 on
56 ■ Configuring ATM VC Classes
subinterface on which this PVC is created
on which this PVC is created
Chapter 1: Configuring ATM
page 59. For information about the default value for each command, see the
command descriptions in “Configuring VC Classes” on page 59.
Precedence Levels for Dynamic PVCs
For PVCs that are dynamically created, the router determines the PVC attribute values
according to the following precedence levels, in order from highest precedence to
lowest precedence:
1. The attribute value specified in the VC class assigned in the base profile always
has the highest precedence.
2. If no VC class is assigned in the base profile, the router takes the value for that
attribute from the VC class assigned to the associated ATM major interface.
3. If neither the base profile nor the ATM major interface has a VC class assigned,
the router takes the value for that attribute from the individually specified
attributes in the base profile.
4. If neither the base profile nor the ATM major interface has a VC class assigned,
and no attributes are individually specified in the base profile, the router applies
the default values for the commands listed in Table 8 on page 59. For information
about the default value for each command, see the command descriptions in
“Configuring VC Classes” on page 59.
Precedence Level Examples
For examples that illustrate how precedence levels affect the assignment of VC
classes, see “Precedence Level Examples for Assigning VC Classes” on page 67.
To help you better understand these examples, we recommend that you first read
the following sections to learn how to configure and assign VC classes:
Upgrade Considerations
The following considerations apply to using ATM VC classes when you upgrade to
the current JUNOSe software release from a lower-numbered JUNOSe software
release:
■ It is possible to use VC classes for PVCs created in a lower-numbered release
with the atm pvc command. In such cases, the router uses the following rules
to determine the PVC attribute values:
■ Nondefault values explicitly specified for PVC attributes with the atm pvc
command take precedence over the attribute values specified in the
associated VC class. As a result, the router takes the values for these attributes
from the atm pvc command settings.
■ Default values implicitly specified for PVC attributes with the atm pvc
command have a lower precedence than the attribute values specified in
the associated VC class. As a result, the router takes the values for these
attributes from the assigned VC class.
■ The output of the show configuration command uses either the pvc command
format or the atm pvc command format to display ATM PVCs. The display format
Configuring ATM VC Classes ■ 57
JUNOSe 11.1.x Link Layer Configuration Guide
of configuration information for ATM PVCs created with the atm pvc command
depends on the JUNOSe software release from which you are upgrading, as
follows:
■ When you upgrade to the current JUNOSe software release from a JUNOSe
release numbered lower than Release 7.3.x, the output of the show
configuration command uses the pvc command format (pvc vcd vpi/vci) to
display configuration information for all ATM PVCs. This occurs even if those
PVCs were created in a JUNOSe release numbered lower than Release 7.3.x
with the atm pvc command. For example, assume that you created a PVC
in JUNOSe Release 7.2.x by issuing the command atm pvc 2 0 33 aal5snap
0 0 0. The show configuration command in the current JUNOSe software
release displays the identifier for this PVC as follows:
pvc 2 0/33
■ When you upgrade to the current JUNOSe software release from JUNOSe
Release 7.3.x or a higher-numbered release, the output of the show
configuration command uses the atm pvc command format to display
configuration information for ATM PVCs created with the atm pvc command.
For example, assume that you created a PVC in JUNOSe Release 7.3.x or
Release 8.0.x by issuing the command atm pvc 2 0 33 aal5snap 0 0 0. The
show configuration command in the current JUNOSe software release
displays the identifier for this PVC as follows:
atm pvc 2 0 33 aal5snap 0 0 0
For PVCs previously created in the lower-numbered release by using the pvc
command, the show configuration command displays configuration
information using the pvc command format, as described previously.
For information about how to use the show configuration command, see chapter
Managing the System in JUNOSe System Basics Configuration Guide.
To make the most efficient use of the VC class feature when you upgrade to the
current JUNOSe software release, we recommend that you follow these steps:
1. Delete any PVCs created with the atm pvc command and recreate them by using
the pvc command. For information about creating a data PVC by using the pvc
command, see “Creating Data PVCs” on page 47.
2. Configure the VC class as described in “Configuring VC Classes” on page 59.
3. Assign the VC class in one of the following ways:
58 ■ Configuring ATM VC Classes
Configuring VC Classes
To configure a VC class, you issue the vc-class atm command to create and name
the VC class. The vc-class atm command accesses ATM VC Class Configuration mode,
from which you configure a set of attributes to apply to an ATM data PVC.
Table 8 on page 59 lists the commands that you can use in ATM VC Class
Configuration mode to configure a set of attributes for a data PVC. These commands
are identical to the commands in ATM VC Configuration mode described in
“Configuring Individual ATM PVC Parameters” on page 45. For more information
about the syntax of each command, see the JUNOSe Command Reference Guide.
Chapter 1: Configuring ATM
■ Assign the VC class to the individual PVC when you create or modify the
PVC.
■ Assign the VC class to the associated ATM major interface or ATM 1483
subinterface before you create the PVC.
Table 8: Commands to Configure VC Class Attributes
oam-pvccbr
oam retryencapsulation
ubrinarp
vbr-nrtoam ais-rdi
vbr-rtoam cc
For example, the following commands configure two VC classes:
premium-subscriber-class and dsl-subscriber-class. You must issue the exit command
from ATM VC Class Configuration mode for each VC class configuration to take effect.
! Configure VC class premium-subscriber-class.
host1(config)#vc-class atm premium-subscriber-class
host1(config-vc-class)#encapsulation aal5autoconfig
host1(config-vc-class)#cbr 200
host1(config-vc-class)#oam-pvc manage 60
host1(config-vc-class)#oam ais-rdi 5
host1(config-vc-class)#exit
! Configure VC class dsl-subscriber-class.
host1(config)#vc-class atm dsl-subscriber-class
host1(config-vc-class)#encapsulation aal5autoconfig
host1(config-vc-class)#ubr
host1(config-vc-class)#exit
host1(config)#
In premium-subscriber-class:
■ The encapsulation command sets the encapsulation method to aal5autoconfig.
■ The cbr command sets the service category to CBR with a PCR of 200 Kbps.
Configuring ATM VC Classes ■ 59
JUNOSe 11.1.x Link Layer Configuration Guide
■ The oam-pvc command enables generation of F5 OAM loopback cells and F5
OAM VC integrity.
■ The oam ais-rdi command configures the alarm down count for successive AIS
and RDI alarm cells to 5.
In dsl-subscriber-class:
■ The encapsulation command sets the encapsulation method to aal5autoconfig.
■ The ubr command configures the UBR service category without a PCR.
To configure an ATM VC class with systemwide default values, you can issue the
vc-class atm command followed immediately by the exit command. For example,
the following commands create a VC class named default-vc-class. Because no attribute
values are explicitly specified in default-vc-class, the router applies the default values
for the commands listed in Table 8 on page 59. For information about the default
value for each command, see the command descriptions in this section.
cbr
encapsulation
! Configure VC class with default values.
host1(config)#vc-class atm default-subscriber-class
host1(config-vc-class)#exit
host1(config)#
To verify the VC class configuration, use the show atm vc-class command. For
information about how to use this command, see “show atm vc-class” on page 99.
■ Use to configure the CBR service category on an ATM data PVC.
■ For detailed information about how to use this command, see “cbr” on page 48.
■ You must issue the exit command from ATM VC Class Configuration mode for
the configuration to take effect.
■ Example
host1(config-vc-class)#cbr 15000
host1(config-vc-class)#exit
■ Use the no version to restore the default service category, UBR without a PCR.
■ See cbr.
■ Use to configure the encapsulation method on an ATM data PVC.
■ For detailed information about how to use this command, see “encapsulation”
on page 50.
■ You must issue the exit command from ATM VC Class Configuration mode for
the configuration to take effect.
■ Example
60 ■ Configuring ATM VC Classes
host1(config-vc-class)#encapsulation aal5mux ip
host1(config-vc-class)#exit
inarp
Chapter 1: Configuring ATM
■ Use the no version to restore the default encapsulation method, aal5snap.
■ See encapsulation.
■ Use to enable Inverse ARP on an ATM PVC that resides on an ATM 1483 NBMA
subinterface and uses the default encapsulation method, aal5snap.
■ For detailed information about how to use this command, see “inarp” on page 55.
■ You must issue the exit command from ATM VC Class Configuration mode for
the configuration to take effect.
■ Example
host1(config-vc-class)#inarp 5
host1(config-vc-class)#exit
■ Use the no version to restore the default behavior, which disables Inverse ARP
on the router.
oam ais-rdi
oam cc
■ See inarp.
■ Use to configure surveillance parameters for AIS and RDI F5 OAM fault
management cells on an ATM data PVC.
■ For detailed information about how to use this command, see “oam ais-rdi” on
page 52.
■ You must issue the exit command from ATM VC Class Configuration mode for
the configuration to take effect.
■ Example
host1(config-vc-class)#oam ais-rdi 5 10
host1(config-vc-class)#exit
■ Use the no version to restore the default values for the alarm down count
(1 successive alarm cell) and alarm clear timeout duration (3 seconds).
■ See oam ais-rdi.
■ Use to enable F5 OAM CC verification on an ATM data PVC.
■ For detailed information about how to use this command, see “oam cc” on
page 52.
■ You must issue the exit command from ATM VC Class Configuration mode for
the configuration to take effect.
■ Example 1—Enables CC verification with a source endpoint
host1(config-vc-class)#oam cc source
host1(config-vc-class)#exit
Configuring ATM VC Classes ■ 61
JUNOSe 11.1.x Link Layer Configuration Guide
■ Example 2—Opens an F5 OAM CC segment cell flow and enables CC verification
with a sink endpoint
host1(config-vc-class)#oam cc segment sink
host1(config-vc-class)#exit
■ Use the no version to disable F5 OAM CC verification and restore the default
setting for cell termination, end-to-end.
■ See oam cc.
oam-pvc
■ Use to enable generation of F5 OAM loopback cells on an ATM data PVC and,
optionally, enable F5 OAM VC integrity features on the circuit.
■ For detailed information about how to use this command, see “oam-pvc” on
page 53.
■ You must issue the exit command from ATM VC Class Configuration mode for
the configuration to take effect.
oam retry
■ Example
host1(config-vc-class)#oam-pvc manage 15
host1(config-vc-class)#exit
■ Use the no version to restore the default behavior, which disables F5 OAM VC
integrity on the router and restores the default value for loopback frequency,
10 seconds.
■ See oam-pvc.
■ Use to configure F5 OAM VC integrity parameters on an ATM data PVC.
■ For detailed information about how to use this command, see “oam retry” on
page 54.
■ You must issue the exit command from ATM VC Class Configuration mode for
the configuration to take effect.
■ Example
host1(config-vc-class)#oam retry 5 6 3
host1(config-vc-class)#exit
■ Use the no version to restore the default values for the up retry count
(3 successive loopback cell responses), down retry count (5 successive loopback
cell responses), and retry frequency (1 second).
■ See oam retry.
ubr
■ Use to configure the UBR service category on an ATM data PVC.
■ For detailed information about how to use this command, see “ubr” on page 49.
62 ■ Configuring ATM VC Classes
vbr-nrt
Chapter 1: Configuring ATM
■ You must issue the exit command from ATM VC Class Configuration mode for
the configuration to take effect.
■ Example
host1(config-vc-class)#ubr 5000
host1(config-vc-class)#exit
■ Use the no version to restore the default service category, UBR without a PCR.
■ See ubr.
■ Use to configure the VBR-NRT service category on an ATM data PVC.
■ For detailed information about how to use this command, see “vbr-nrt” on
page 49.
■ You must issue the exit command from ATM VC Class Configuration mode for
the configuration to take effect.
vbr-rt
vc-class atm
■ Example
host1(config-vc-class)#vbr-nrt 50000 10000 150
host1(config-vc-class)#exit
■ Use the no version to restore the default service category, UBR without a PCR.
■ See vbr-nrt.
■ Use to configure the VBR-RT service category on an ATM data PVC.
■ For detailed information about how to use this command, see “vbr-rt” on page 50.
■ You must issue the exit command from ATM VC Class Configuration mode for
the configuration to take effect.
■ Example
host1(config-vc-class)#vbr-rt 200000 30000 400
host1(config-vc-class)#exit
■ Use the no version to restore the default service category, UBR without a PCR.
■ See vbr-rt.
■ Use to create and name a VC class for an ATM data PVC.
■ You must specific a VC class name of up to 32 alphanumeric characters.
■ The vc-class atm command accesses ATM VC Class Configuration mode, from
which you can configure a set of attributes for the PVC including the service
category, encapsulation method, F5 OAM options, and Inverse ARP.
■ You must issue the exit command from ATM VC Class Configuration mode for
the VC class configuration to take effect.
Configuring ATM VC Classes ■ 63
JUNOSe 11.1.x Link Layer Configuration Guide
■ For information about the total number of VC classes supported on the router,
see JUNOSe Release Notes, Appendix A, System Maximums.
■ Example
host1(config)#vc-class atm dsl-subscriber-class
host1(config-vc-class)#exit
■ Use the no version to remove the named VC class from the router. You cannot
remove a VC class that is currently assigned to at least one ATM PVC, ATM 1483
subinterface, or ATM major interface without first issuing the no class-vc
command or the no class-int command to remove the VC class association with
the PVC, interface, or subinterface.
■ See vc-class atm.
Assigning VC Classes to Individual PVCs
To assign a previously configured VC class to an individual ATM data PVC, you use
the class-vc command from ATM VC Configuration mode. Issuing this command
applies the set of attributes configured in the specified VC class to the ATM data PVC.
NOTE: The class-vc command is valid only for a data PVC created with the pvc
command. It has no effect for data PVCs created with the atm pvc command, or for
control (ILMI) PVCs. For information about creating a data PVC by using the pvc
command, see “Creating Data PVCs” on page 47.
For example, the following commands assign the VC class named
premium-subscriber-class to the ATM data PVC with VCD 2, VPI 0, and VCI 200.
! Assign VC class premium-subscriber-class to PVC 2/0.200
host1(config)#interface atm 2/0.200
host1(config-subif)#pvc 200 0/200
host1(config-subif-atm-vc)#class-vc premium-subscriber-class
host1(config-subif-atm-vc)#exit
For those attributes that you do not explicitly specify for the ATM PVC, the router
applies the values specified in the VC class. As explained in “Precedence Levels” on
page 56, the values in a VC class assigned to an individual PVC take precedence over
both of the following:
■ Values in a VC class assigned to an ATM 1483 subinterface
■ Values in a VC class assigned to an ATM major interface
For examples that illustrate how precedence levels affect the assignment of VC
classes, see “Precedence Level Examples for Assigning VC Classes” on page 67.
class-vc
■ Use to assign a previously configured VC class to an individual ATM data PVC.
■ The class-vc command is valid only for data PVCs created with the pvc command.
64 ■ Configuring ATM VC Classes
■ You must issue the exit command from ATM VC Configuration mode for the VC
class association to take effect.
■ Example
host1(config-subif-atm-vc)#class-vc dsl-subscriber-class
host1(config-subif-atm-vc)#exit
■ Use the no version to remove the VC class association with the data PVC.
■ See class-vc.
Assigning VC Classes to ATM Major Interfaces
To assign a previously configured VC class to an ATM major interface, you use the
class-int command from Interface Configuration mode. Issuing this command applies
the set of attributes in the specified VC class to the ATM data PVCs statically or
dynamically created on this interface.
Chapter 1: Configuring ATM
class-int
For example, the following commands assign the VC class named dsl-subscriber-class
to an ATM major interface configured on slot 5, port 0.
! Assign VC class dsl-subscriber-class to ATM interface 5/0.
host1(config)#interface atm 5/0
host1(config-if)#class-int dsl-subscriber-class
host1(config-if)#exit
For those attributes that you do not explicitly specify for an ATM PVC, the router
applies the values specified in the VC class. As explained in “Precedence Levels” on
page 56, the values in a VC class assigned to an ATM major interface have a lower
precedence than both of the following:
■ Values in a VC class assigned to an individual ATM PVC
■ Values in a VC class assigned to an ATM 1483 subinterface
This means that if a VC class is assigned to an individual PVC or ATM 1483
subinterface configured on the major interface, the attribute values configured in the
VC class assigned to the PVC or subinterface override the attribute values configured
in the VC class assigned to the major interface.
For examples that illustrate how precedence levels affect the assignment of VC
classes, see “Precedence Level Examples for Assigning VC Classes” on page 67.
■ Use from Interface Configuration mode to assign a previously configured VC
class to an ATM major interface.
■ You must issue the exit command from Interface Configuration mode for the
VC class association to take effect.
■ Example
host1(config-if)#class-int gold-subscriber-class
host1(config-if)#exit
Configuring ATM VC Classes ■ 65
JUNOSe 11.1.x Link Layer Configuration Guide
■ Use the no version to remove the VC class association with the interface. Issuing
the no version causes the router to set the PVC attributes to their systemwide
default values, or to the values set in the associated VC class with the next highest
order of precedence.
■ See class-int.
Assigning VC Classes to Static ATM 1483 Subinterfaces
To assign a previously configured VC class to a static ATM 1483 subinterface, you
use the class-int command from Subinterface Configuration mode. Issuing this
command applies the set of attributes in the specified VC class to the ATM data PVCs
statically or dynamically created on this subinterface.
For example, the following commands assign the VC class named
premium-subscriber-class to an ATM 1483 subinterface configured on slot 5, port 0,
subinterface 100.
class-int
! Assign VC class dsl-subscriber-class to ATM 1483 subinterface 5/0.100.
host1(config)#interface atm 5/0.100
host1(config-subif)#class-int premium-subscriber-class
host1(config-subif)#exit
For those attributes that you do not explicitly specify for an ATM PVC, the router
applies the values specified in the VC class. As explained in “Precedence Levels” on
page 56, the values in a VC class assigned to an ATM 1483 subinterface take
precedence over the values in a VC class assigned to an ATM major interface, but
have a lower precedence than the values in a VC class assigned to an individual ATM
PVC.
This means that if a VC class is assigned to a PVC configured on the subinterface,
the attribute values configured in the VC class assigned to the individual PVC override
the attribute values configured in the VC class assigned to the subinterface.
For examples that illustrate how precedence levels affect the assignment of VC
classes, see “Precedence Level Examples for Assigning VC Classes” on page 67.
■ Use from Subinterface Configuration mode to assign a previously configured VC
class to a static ATM 1483 subinterface.
■ You must issue the exit command from Subinterface Configuration mode for
the VC class association to take effect.
■ Example
■ Use the no version to remove the VC class association with the subinterface.
Issuing the no version causes the router to set the VC attributes to their
66 ■ Configuring ATM VC Classes
host1(config-subif)#class-int silver-subscriber-class
host1(config-subif)#exit
systemwide default values, or to the values set in the associated VC class with
the next highest order of precedence.
■ See class-int.
Assigning VC Classes to Base Profiles for Bulk-Configured VC Ranges
To assign a VC class to a base profile for a dynamic ATM 1483 subinterface, you can
use the atm class-vc command from Profile Configuration mode. Issuing this
command applies the set of attributes in the specified VC class to all bulk-configured
VC ranges that are dynamically created from this profile.
For more information, see “Configuring ATM 1483 Dynamic Subinterfaces” on
page 628 in “Configuring Dynamic Interfaces Using Bulk Configuration” on page 623.
Precedence Level Examples for Assigning VC Classes
Chapter 1: Configuring ATM
The examples in this section illustrate how the precedence level rules described in
“Precedence Levels” on page 56 affect the assignment of VC classes and PVC attribute
values.
For all of these examples, assume that you have issued the following commands to
configure a VC class named my-premium-class:
host1(config)#vc-class atm my-premium-class
host1(config-vc-class)#encapsulation aal5autoconfig
host1(config-vc-class)#cbr 200
host1(config-vc-class)#oam-pvc manage 60
host1(config-vc-class)#oam ais-rdi 5
host1(config-vc-class)#exit
Example 1 and Example 2 illustrate the effect of precedence levels when you assign
the VC class my-premium-class to an individual PVC with VCD 200, VPI 0, and
VCI 200. Example 3 illustrates how using the atm pvc command affects VC class
assignment. Finally, Example 4 illustrates how modifications to a VC class affect PVC
attributes applied through RADIUS.
Example 1: Explicitly Changing the Service Category
Explicitly specified attribute values take precedence over attribute values specified
in a VC class. As a result, the following commands cause the router to use the most
recent explicitly specified value, UBR with a PCR of 200 Kbps, as the service category
for this PVC instead of the service category specified in my-premium-class, CBR with
a PCR of 200 Kbps. The router takes the values for the other attributes from the VC
class my-premium-class.
host1(config)#interface atm 2/0.200
host1(config-subif)#pvc 200 0/200
host1(config-subif-vc)#ubr 200
host1(config-subif-vc)#class-vc my-premium-class
host1(config-subif-vc)#exit
Configuring ATM VC Classes ■ 67
JUNOSe 11.1.x Link Layer Configuration Guide
The following commands change the service category for the PVC to VBR-RT because
this is the most recent explicitly specified value for this attribute. The router takes
the values for the other attributes from the VC class my-premium-class, which is still
assigned to the PVC.
host1(config)#interface atm 2/0.200
host1(config-subif)#pvc 200 0/200
host1(config-subif-vc)#vbr-rt 200 150 200
host1(config-subif-vc)#exit
The following commands cause the router to retain the VBR-RT service category for
the PVC because it is still the most recent explicitly specified value for this attribute.
The router takes the values for the other attributes from the VC class
my-premium-class.
host1(config)#interface atm 2/0.200
host1(config-subif)#pvc 200 0/200
host1(config-subif-vc)#class-vc my-premium-class
host1(config-subif-vc)#exit
Example 2: Changing the Encapsulation Method in the VC Class
The following commands change the value for the encapsulation method in the VC
class my-premium-class from aal5autoconfig to aal5snap. As a result, the router
now uses aal5snap instead of aal5autoconfig as the encapsulation method for the
PVCs to which this VC class is assigned.
host1(config)#vc-class atm my-premium-class
host1(config-vc-class)#encapsulation aal5snap
host1(config-vc-class)#exit
Example 3: Effect of Using the atm pvc Command
The following commands, which attempt to assign the my-premium-class VC class
to a PVC originally created with the atm pvc command, have no effect. The router
interprets all attribute values specified with the atm pvc command as explicitly
specified values, and therefore takes the values for these attributes from the atm
pvc command instead of from the VC class. As a result, the router continues to use
aal5mux ip as the encapsulation method for this PVC instead of the encapsulation
method specified in the VC class my-premium-class.
host1(config)#interface atm 2/0.300
host1(config-subif)#atm pvc 300 0 300 aal5mux ip
host1(config-subif)#pvc 300 0/300
host1(config-subif-vc)#class-vc my-premium-class
host1(config-subif-vc)#exit
Example 4: Overriding RADIUS Values
If RADIUS is configured to provide traffic parameters for PVCs, a more recent,
explicitly specified change in the VC class associated with that PVC overrides the
PVC values applied through RADIUS.
68 ■ Configuring ATM VC Classes
Loading...