Download Print this page

Juniper JUNOSE 11.1.X - LINK LAYER CONFIGURATION 4-7-2010 Configuration Manual

For e series broadband services routers - link layer configuration

Table Of Contents

Table of Contents

Advertisement

Quick Links

Download this manual

Enlarged version

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

Table of Contents

Advertisement

Table of Contents

Troubleshooting

Need help?

Need help?

Do you have a question about the JUNOSE 11.1.X - LINK LAYER CONFIGURATION 4-7-2010 and is the answer not in the manual?

Questions and answers

Summary of Contents for Juniper JUNOSE 11.1.X - LINK LAYER CONFIGURATION 4-7-2010

Page 1 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 408-745-2000 www.juniper.net Published: 2010-04-07...
Page 2 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.
Page 3 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”)
Page 4 (“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 http://www.gnu.org/licenses/gpl.html...
Page 5 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.
Page 7 Abbreviated Table of Contents About the Documentation xxix Part 1 Chapters Chapter 1 Configuring ATM Chapter 2 Configuring Frame Relay Chapter 3 Configuring Multilink Frame Relay Chapter 4 Configuring Upper-Layer Protocols over Static Ethernet Interfaces Chapter 5 Configuring VLAN and S-VLAN Subinterfaces Chapter 6 Configuring 802.3ad Link Aggregation and Link Redundancy Chapter 7...
Page 8 JUNOSe 11.1.x Link Layer Configuration Guide viii...
Page 9: Table Of Contents
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...
Page 10 JUNOSe 11.1.x Link Layer Configuration Guide ATM NBMA ....................13 ARP Table ....................14 Static Map Versus Inverse ARP ............14 Aging ....................14 Removing Circuits ................15 Operations, Administration, and Management of ATM Interfaces ....15 End-to-End and Segment Endpoints ............15 Fault Management ..................15 How the ATM Interface Handles AIS Cells ........16 How the ATM Interface Handles RDI Cells ........16 Continuity Verification ................17 Activation and Deactivation Cells .............17...
Page 11 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...
Page 12 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...
Page 13 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 802.3ad Link Aggregation for Ethernet Overview ........199 LACP .....................200 Higher-Level Protocols ................200 Load Balancing and QoS ...............201...
Page 14 JUNOSe 11.1.x Link Layer Configuration Guide Chapter 7 Configuring IEEE 802.3ah OAM Link-Fault Management 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...
Page 15 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...
Page 16 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...
Page 17 Table of Contents Chapter 12 Configuring Point-to-Point Protocol over Ethernet 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...
Page 18 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 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...
Page 19 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...
Page 20 JUNOSe 11.1.x Link Layer Configuration Guide Placing Dynamic IP Routes in the Routing Table ......525 auto-configure Command ..............525 Encapsulation Type Lockout ............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 Negotiations ...................533 Configuring PPPoE Dynamic Interfaces over PPPoE Static Interfaces ..534...
Page 21 Table of Contents Chapter 18 Configuring Dynamic Interfaces Using Bulk Configuration 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...
Page 22 JUNOSe 11.1.x Link Layer Configuration Guide 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 Configuring a Dynamic VLAN Subinterface ...........667...
Page 23 List of Figures Part 1 Chapters Chapter 1 Configuring ATM 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 Figure 4: Interconnection and Relationship of NNIs and Subnetworks ..109 Chapter 3 Configuring Multilink Frame Relay Figure 5: MLFR Aggregation of T1 Lines into a Single Bundle ......134...
Page 24 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 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...
Page 25 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...
Page 26 JUNOSe 11.1.x Link Layer Configuration Guide xxvi List of Figures...
Page 27: List Of Tables
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 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...
Page 28 JUNOSe 11.1.x Link Layer Configuration Guide Chapter 13 Configuring Bridged IP Table 24: Prerequisite Tasks for Configuring Bridged IP ......440 Chapter 15 Configuring Transparent Bridging 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...
Page 29: About The Documentation
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/...
Page 30: Table 1: Notice Icons
JUNOSe 11.1.x Link Layer Configuration Guide Table 1: Notice Icons Icon Meaning Description Informational note Indicates important features or instructions. Caution Indicates a situation that might result in loss of data or hardware damage. Warning Alerts you to the risk of personal injury or death. Laser warning Alerts you to the risk of personal injury from a laser.
Page 31: About The 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 at http://www.juniper.net/...
Page 32: Self-Help Online Tools And Resources
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/...
Page 33: Chapters
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...
Page 34 JUNOSe 11.1.x Link Layer Configuration Guide Chapters...
Page 35: Configuring Atm
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...
Page 36: Atm Interfaces
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.
Page 37: Atm Virtual Connections
Chapter 1: Configuring ATM 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.
Page 38: Local Atm Passthrough
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).
Page 39: 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. Traffic Management The scheduling priority for traffic classes depends on the type of router that you have.
Page 40: Table 4: Traffic Parameters Used To Compute Bandwidth
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.
Page 41: Ilmi
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.
Page 42: Vp Tunneling
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...
Page 43: Interface Specifiers
Chapter 1: Configuring ATM Interface Specifiers 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.
Page 44: Supported Features
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.
Page 45: Virtual Channel Support
Chapter 1: Configuring ATM Table 5: ATM Capabilities on Line Modules and I/O Modules (continued) ATM Circuit VP Tunnel Number VPI/VCI Number of Traffic Traffic Line I/O Module of VP Address Configurable VCs on Management Management Module or IOA Tunnels Range Bit Range Each Port...
Page 46: Arp Table
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.
Page 47: Removing Circuits
Chapter 1: Configuring ATM 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.
Page 48: How The Atm Interface Handles Ais Cells
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.
Page 49: Continuity Verification
Chapter 1: Configuring ATM 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.
Page 50: After Cc Cell Flow Is Enabled
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.
Page 51: F4 Oam Cells
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.
Page 52: How The Atm Interface Handles Loopback Cells Received
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 Loopback Cell Received ATM Interface Response F4 and F5 end-to-end loopback cells and...
Page 53: Rate Limiting For F5 Oam Cells
Chapter 1: Configuring ATM 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.
Page 54: Configuration Tasks
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.) Configure an ATM physical interface.
Page 55: Figure 3: Configuring An Atm Interface, Subinterface, And Pvc
Chapter 1: Configuring ATM Figure 3: Configuring an ATM Interface, Subinterface, and PVC ERX14xx models (rear view) 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.
Page 56: Setting Optional Parameters
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.
Page 57 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.
Page 58: Optional Tasks On Atm 1483 Subinterfaces
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.
Page 59 Chapter 1: Configuring ATM Use to enable SNMP link status traps on the AAL5 layer interface. Example host1(config-if)#atm aal5 snmp trap link-status 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.
Page 60 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.
Page 61 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.
Page 62 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.
Page 63 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. atm uni-version Use to specify the UNI version for the interface to use.
Page 64 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.
Page 65: Configuring Oam
Chapter 1: Configuring ATM host1(config-if)#loopback diagnostic Use the no version to remove any loopback. See loopback. Configuring OAM 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...
Page 66 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...
Page 67: Configuring F5 Oam
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...
Page 68: Setting A Loopback Location Id
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...
Page 69: Enabling Oam Flush
Chapter 1: Configuring ATM atm oam loopback-location 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.
Page 70: Running Atm Ping
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”...
Page 71: Configuring An Nbma Interface
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.
Page 72: Creating An Nbma Static Map
JUNOSe 11.1.x Link Layer Configuration Guide Configure an ATM 1483 subinterface. host1(config-if)#interface atm 2/0.2 multipoint 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 (Optional) Specify InARP and a refresh rate (also optional).
Page 73 Chapter 1: Configuring ATM atm pvc 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.
Page 74: Assigning Descriptions To Interfaces
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.
Page 75: Sending Interface Descriptions To Aaa
Chapter 1: Configuring ATM 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. 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.
Page 76: Assigning Descriptions To Virtual Paths
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.
Page 77: Configuring Individual Atm Pvc Parameters
Chapter 1: Configuring ATM 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.
Page 78: Benefits
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:...
Page 79: Creating Data Pvcs
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.
Page 80: Configuring The Service Category For Data Pvcs
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.
Page 81 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).
Page 82: Configuring Encapsulation For Data Pvcs
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)
Page 83: Configuring F5 Oam For Data Pvcs
Chapter 1: Configuring ATM 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.
Page 84 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).
Page 85 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.
Page 86: Configuring Inverse Arp For Data Pvcs
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;...
Page 87: Configuring Atm Vc Classes
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.
Page 88: Precedence Levels
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.
Page 89: Precedence Levels For Dynamic Pvcs
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: The attribute value specified in the VC class assigned in the base profile always...
Page 90 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.
Page 91: Configuring Vc Classes
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. Configuring VC Classes To configure a VC class, you issue the vc-class atm command to create and name the VC class.
Page 92 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.
Page 93 Chapter 1: Configuring ATM Use the no version to restore the default encapsulation method, aal5snap. See encapsulation. inarp 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”...
Page 94 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.
Page 95 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.
Page 96: Assigning Vc Classes To Individual Pvcs
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...
Page 97: Assigning Vc Classes To Atm Major Interfaces
Chapter 1: Configuring ATM 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.
Page 98: Assigning Vc Classes To Static Atm 1483 Subinterfaces
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.
Page 99: Assigning Vc Classes To Base Profiles For Bulk-Configured Vc Ranges
Chapter 1: Configuring ATM 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.
Page 100: Example 2: Changing The Encapsulation Method In The Vc Class
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.
Page 101: Configuring Dynamic Atm 1483 Subinterfaces
Chapter 1: Configuring ATM In the following example, assume that RADIUS has been configured to apply a service category of CBR with a PCR of 400 Kbps to the PVC. Initially, the PVC uses the service category configured in my-premium-class, CBR with a PCR of 200 Kbps. However, when the subscriber logs in through RADIUS, the router applies the RADIUS-configured service category, CBR with a PCR of 400 Kbps.
Page 102: Setting Statistics Baselines
JUNOSe 11.1.x Link Layer Configuration Guide Setting Statistics Baselines You can set a statistics baseline for ATM interfaces, ATM virtual circuits, and ATM virtual paths configured on the router. baseline atm vp interface Use to set a statistics baseline for an ATM virtual path (VP) interface. The router implements the baseline by reading and storing the statistics at the time the baseline is set and then subtracting this baseline whenever baseline-relative statistics are retrieved.
Page 103 Chapter 1: Configuring ATM To monitor the data rate for ATM VPs, use the monitor atm vp command. To monitor the data rate for ATM VCs and ATM VPs: Log in to the router by using a local console session or a virtual terminal (vty) session (such as a Telnet session).
Page 104 JUNOSe 11.1.x Link Layer Configuration Guide ATM 12/0 6635312/6479 6635312/6479 09:47:33 ATM 12/0 6635176/6479 6635176/6479 09:47:48 ATM 12/0 6634424/6478 6634424/6478 09:47:48 ATM 12/0 6635448/6479 6635448/6479 09:48:03 The monitor atm vc command and monitor atm vp command display similar information, except that the monitor atm vc command displays the VCD for each interface and the monitor atm vp command displays the VPI for each interface.
Page 105 Chapter 1: Configuring ATM To specify a nondefault time interval in the range 5–30 seconds (for ATM VCs) or 5–300 seconds (for ATM VPs) at which the router calculates bit rate and packet rate statistics, use the optional load-interval keyword. The default time interval for either command is 5 seconds.
Page 106: Using Atm Show Commands
JUNOSe 11.1.x Link Layer Configuration Guide ATM 12/0 6633264/6477 6633472/6478 17:33:11 ATM 12/0 6632856/6477 6632856/6477 17:33:16 ATM 12/0 6633264/6477 6633056/6477 17:33:16 host1# ^C Example 3 Displays bit rate and packet rate statistics over a 10-second load interval for two ATM VPs host1#monitor atm vp atm 12/0 0 atm 12/0 1 load-interval 10 Seconds between...
Page 107 Chapter 1: Configuring ATM AAL5 Interface operational status Operational status of the AAL5 interface: up, down, lowerlayerDown time since last status change Time since last reported change to the AAL5 interface operational status SNMP trap link-status Whether SNMP link status traps are enabled or disabled on the ATM AAL5 interface Auto configure ATM 1483 status Setting of the autoconfiguration feature for a dynamic ATM 1483 subinterface configured over the ATM AAL5...
Page 108 JUNOSe 11.1.x Link Layer Configuration Guide Example host1#show atm atm1483 ATM1483 IF Descriptions exported See show atm atm1483. show atm interface show interfaces atm Use to display configuration and state information and statistics about a specific ATM interface, or to display a brief description of all ATM interfaces configured in the router.
Page 109 Chapter 1: Configuring ATM UNI version UNI version: 3.0, 3.1, 4.0 Maximum VCs Maximum number of virtual circuits supported on this interface Current VCs Current number of virtual circuits configured ILMI VPI/VCI Number of VPI and VCI configured for ILMI (displayed only when ILMI is configured on the interface) VCD Number of VCD (displayed only when ILMI is configured on the interface)
Page 110 JUNOSe 11.1.x Link Layer Configuration Guide OutErrors Number of outgoing errors on this interface InPacketDiscards Number of incoming packets discarded on this interface InByteDiscards Number of incoming bytes discarded on this interface InCellErrors Increments when a T3 or an E3 ATM interface receives cells for a VPI or VCI that is not configured on that interface Field descriptions specific to the applicable physical interface.
Page 111 Chapter 1: Configuring ATM host1#show atm interface atm 2/0 ATM Interface 2/0 is down, line protocol is down AAL5 operational status: lowerLayerDown time since last status change: 22:08:21 ATM operational status: down time since last status change: 22:02:11 SONET path operational status: lowerLayerDown time since last status change: 1 day, 0 hours SONET operational status: down...
Page 112 JUNOSe 11.1.x Link Layer Configuration Guide ATM 4/0 ATM 6/0 lowerLayerDown See show atm interface. See show interfaces. show atm map Use to display the list of all configured ATM static maps to remote hosts on an ATM network. Field descriptions Map list Name of map list and method used to enter the map list.
Page 113 Chapter 1: Configuring ATM Use to display F4 OAM statistics for an ATM interface. You must specify a VPI value in addition to the required ATM interface specifier. You can use the following keywords. segment Displays information about segment loopbacks end-to-end Displays information about end-to-end loopbacks To see F4 OAM circuits that are open, use the show atm vc command.
Page 114 JUNOSe 11.1.x Link Layer Configuration Guide RDI Circuit is in RDI state InOamF4Cells Number of F4 OAM cells received InOamF4CellsDropped Number of incoming F4 OAM cells that were dropped InOamF4EndLoopbackCells Total number of F4 end-to-end loopback cells received on this interface, which is the sum of the following counts: InOamF4EndLoopbackCommands Number of F4 end-to-end loopback commands received InOamF4EndLoopbackResponses Number of F4 end-to-end loopback...
Page 115 Chapter 1: Configuring ATM OutOamF4SegLoopbackResponses Number of F4 segment loopback responses sent OutOamF4EndRdiCells Number of end-to-end RDI cells sent OutOAM F4SegRdiCells Number of segment RDI cells sent OutOamF4EndCCActDeActCells Number of F4 end-to-end activation or deactivation CC cells sent OutOamF4SegCCActDeActCells Number of F4 segment activation or deactivation CC cells sent OutOamF4EndCCCells Number of F4 end-to-end CC cells sent OutOamF4SegCCCells Number of F4 segment CC cells sent...
Page 116 JUNOSe 11.1.x Link Layer Configuration Guide Example 2 host1#show atm oam 2/1 0 segment Segment OAM CC verification enabled OAM CC Type : CC Sink End Point OAM Current CC state: Ready VP State :down VP Oam State :not managed InOamF4SegmentCells InOamF4SegmentCellsDropped InOamF4SegLoopbackCells...
Page 117 Chapter 1: Configuring ATM interfaceSpecifier Shows ping entries for this interface vpi Shows details of the last ping atm command on this VPI vci Shows details of the last ping atm command on this VCI Field descriptions Interface Interface number VPI Virtual path identifier VCI Virtual channel identifier CellCount OAM loopback cell count configured on the interface...
Page 118 JUNOSe 11.1.x Link Layer Configuration Guide --------- --- --- --------- ------- ------------- --------- ------- ATM 2/1 Ping Completed ATM 2/1 Ping Completed ATM 2/2 Ping Completed ATM 2/2 Ping Completed % Found 4 Entries in the system Example 2 Displays entries on an interface host1#show atm ping 2/1 Interface VPI VCI CellCount TimeOut...
Page 119 Chapter 1: Configuring ATM To display brief summary information for all ATM subinterfaces, or for ATM subinterfaces configured on a specified ATM physical interface, use the summary keyword. To display status information only for ATM subinterfaces with a specific operating status, use the status keyword with one of the following status values.
Page 120 JUNOSe 11.1.x Link Layer Configuration Guide Circuit Type Type of circuit: PVC Encap Administered encapsulation method based on what was configured with the atm pvc command MTU Maximum transmission unit size for the interface Status One of the following ATM 1483 subinterface states: absent Represents the notPresent state and indicates that, although the SRP detects the ATM 1483 subinterface, the module on which the subinterface resides has not completed booting up, has failed, or is...
Page 121 Chapter 1: Configuring ATM Detected dynamic interface Type of dynamic upper interface detected during autoconfiguration: bridged Ethernet, IP, PPP, PPPoE, or (if no packet has been received) none Interface types in lockout Encapsulation types currently experiencing lockout: bridged Ethernet, IP, PPP, PPPoE, or none Lockout state (seconds) Settings of encapsulation type lockout for the upper-layer encapsulation type indicated Min Minimum lockout time, in seconds...
Page 122 JUNOSe 11.1.x Link Layer Configuration Guide Example 1 Displays the current state of all ATM subinterfaces host1#show atm subinterface Circuit Interface Interface ATM-Prot VCD VPI VCI Type Encap MTU Status Type ----------- -------- --- --- --- ----- ----- ---- -------------- --------- ATM 2/0.101 RFC-1483 101 0 101 PVC AUTO...
Page 123 Chapter 1: Configuring ATM Assigned VC class : premium-subscriber-class SNMP trap link-status: disabled InPackets: InBytes: 1904 OutPackets: OutBytes: InErrors: OutErrors: InPacketDiscards: InPacketsUnknownProtocol: 0 OutDiscards: 1 interface(s) found Example 5 Displays the current state of a specific ATM subinterface created on the PVC with the specified VPI and VCI values host1#show atm subinterface atm 0/0/0/101 Circuit Interface...
Page 124 JUNOSe 11.1.x Link Layer Configuration Guide Use to display a summary of all configured ATM virtual circuits (VCs) and reserved VC ranges. You can specify one or more of the following keywords individually or in combination: vpi Displays VCs on a specific VPI category Displays VCs that have a specific service category status Displays VCs with a certain status You can also specify the reserved keyword with no other keywords to display...
Page 125 Chapter 1: Configuring ATM ATM 3/0.8099 1 8099 8099 PVC SNAP 0 UP ATM 3/0.8100 1 8100 8100 PVC SNAP 0 DOWN 8000 circuit(s) found Reserved VCC ranges: Start Start End End Interface VPI VCI --------- ----- ----- --- --- ATM 2/0 2 102 ATM 2/0...
Page 126 JUNOSe 11.1.x Link Layer Configuration Guide Use to display information about a specific VC. To specify the circuit to display, do one of the following: Enter the VCD. Use the vpi-vci keyword and enter the VPI and VCI. Enter the description configured for the ATM 1483 subinterface (with the atm atm1483 description command) on which the VC resides.
Page 127 Chapter 1: Configuring ATM Alarm clear timeout Number of seconds that the router waits before reporting that the PVC is up after the PVC stops receiving alarm cells OAM VC verification Whether OAM verification is enabled or disabled OAM loopback cell status: disabled VC integrity disabled for VC sent OAM loopback cell sent;...
Page 128 JUNOSe 11.1.x Link Layer Configuration Guide Activation Failed OAM CC activation failed Wait Activate Waiting for interface to come up before the software sends the activation request Wait Activation Confirmation Waiting for activation confirmation from the peer Wait DeActivate Waiting for interface to come up before the software sends the deactivation request Wait DeActivation Confirmation Waiting for deactivation confirmation from the peer...
Page 129 Chapter 1: Configuring ATM OutOamF5Cells Number of F5 OAM cells transmitted on this circuit OutF5EndLoopCells Total number of F5 end-to-end loopback cells transmitted on this circuit, which is the sum of the following counts: OutF5EndLoopCommands Number of F5 end-to-end loopback commands transmitted OutF5EndLoopResponses Number of F5 end-to-end loopback responses transmitted...
Page 130 JUNOSe 11.1.x Link Layer Configuration Guide SAR time-outs: Over-sized SDUs: Alarm drop count: Alarm clear timeout:3 OAM VC verification: enabled OAM loopback cell status: sent OAM VC status: up OAM loopback frequency: 10 second interval OAM up retry count: 3, OAM down retry count: 5 OAM loopback retry frequency: 1 second interval OAM CC verification: disabled InOamF5Cells:...
Page 131 Chapter 1: Configuring ATM CrcErrors: SAR time-outs: Over-sized SDUs: Alarm drop count: Alarm clear timeout: OAM VC verification: disabled OAM VC status: not managed OAM CC verification: disabled InOamF5Cells: InOamCellDiscards: 384723 InF5EndLoopCells: InF5EndLoopCommands: InF5EndLoopResponses: InF5SegLoopCells: InF5SegLoopCommands: InF5SegLoopResponses: InF5EndAisCells: InF5SegAisCells: InF5EndRdiCells: InF5SegRdiCells: InF5EndCCActDeActCells: InF5SegCCActDeActCells:...
Page 132 JUNOSe 11.1.x Link Layer Configuration Guide Peak Cell Rate Peak cell rate (PCR), in Kbps, configured for the service category OAM VC Integrity Status of F5 OAM VC integrity features on the PVC: enabled or disabled OAM VC Integrity loop-back timer Number of seconds the router waits between the transmission of loopback cells during normal operation OAM VC Integrity Up Retry Count Number of successive loopback cell responses that the router receives before reporting that a PVC is up...
Page 133 Chapter 1: Configuring ATM OAM alarm clear time out :3 seconds OAM continuity check :disabled Inverse ARP :disabled See show atm vc-class. show atm vp Use to display detailed statistics for a specific ATM VP configured on the router. Field descriptions ServiceCategory Service type on the VP tunnel, if configured: UBR, UBR-PCR, VBR-NRT, VBR-RT, or CBR Peak Cell Rate Peak cell rate in kilobits per second, if a VP tunnel is...
Page 134 JUNOSe 11.1.x Link Layer Configuration Guide VP State State of the VP: up, down VP Oam State OAM state of the VP: not managed (normal OAM state with no OAM fault conditions), AIS, RDI InOamF4EndCells Number of F4 end-to-end cells received InOamF4EndCellsDropped Number of incoming F4 end-to-end cells that were dropped InOamF4EndLoopbackCells Number of F4 end-to-end loopback cells...
Page 135 Chapter 1: Configuring ATM InOamF4SegmentCellsDropped Number of incoming F4 segment cells that were dropped InOamF4SegmentLoopbackCells Number of F4 segment loopback cells received InOamF4SegmentLoopbackCommands Number of F4 segment loopback commands received InOamF4SegmentLoopbackResponses Number of F4 segment loopback responses received InOamF4SegCCActDeActCells Number of F4 segment activation or deactivation CC cells received InOamF4SegCCCells Number of F4 segment CC cells received OutOamF4SegmentCells Number of F4 segment cells transmitted...
Page 136 JUNOSe 11.1.x Link Layer Configuration Guide End To End OAM CC verification Disabled VP State VP Oam State :not managed InOamF4EndCells InOamF4EndCellsDropped InOamF4EndLoopbackCells InOamF4EndLoopbackCommands InOamF4EndLoopbackResponses InOamF4EndAisCells InOamF4EndRdiCells InOamF4EndCCActDeActCells InOamF4EndCCCells OutOamF4EndCells OutOamF4EndLoopbackCells OutOamF4EndLoopbackCommands OutOamF4EndLoopbackResponses OutOamF4EndRdiCells OutOamF4EndCCActDeActCells OutOamF4EndCCCells Time since last status change :08:48:43 Segment OAM CC verification Disabled VP State...
Page 137 Chapter 1: Configuring ATM Description Text description configured for the VP Example 1 Displays all VP descriptions configured on the router host1#show atm vp-description Interface Description ATM 2/0 atm20Vpi0Subscribers ATM 2/0 atm20Vpi1Subscribers ATM 2/1 atm21Vpi0Subscribers Example 2 Displays all VP descriptions for the specified ATM interface host1#show atm vp-description atm 2/0 Interface Description...
Page 138 JUNOSe 11.1.x Link Layer Configuration Guide show nbma arp Use to display ARP table entries for ATM NBMA interfaces. Field descriptions IP Address IP address of the entry VPI/VCI VPI and VCI of the entry Interface Interface specifier of the entry Example host1#show nbma arp NBMA ARP Table Entries...
Page 139: Configuring Frame Relay
Chapter 2 Configuring Frame Relay This chapter describes how to configure a Frame Relay interface on E Series routers. This chapter contains the following sections: Overview on page 107 Platform Considerations on page 109 References on page 110 Before You Configure Frame Relay on page 110 Configuring Frame Relay on page 111 End-to-End Fragmentation and Reassembly on page 119 Monitoring Frame Relay on page 123...
Page 140: Error Frames
JUNOSe 11.1.x Link Layer Configuration Guide The router does not support: Protocol-dependent fragmentation Autodetection of the Local Management Interface (LMI) protocol type Error Frames The router relies on higher-layer protocols to detect and recover from Frame Relay data loss. All Frame Relay error frames are discarded. Unicast and Multicast Addressing Most Frame Relay services support both unicast (individual) and multicast (group) addressing.
Page 141: Platform Considerations
Chapter 2: Configuring Frame Relay Figure 4: Interconnection and Relationship of NNIs and Subnetworks Platform Considerations You can configure Frame Relay interfaces on the following E Series Broadband Services Routers: ERX1440 router ERX1410 router ERX710 router ERX705 router ERX310 router NOTE: The E120 and E320 Broadband Services Routers do not support configuration of Frame Relay interfaces.
Page 142: Interface Specifiers
JUNOSe 11.1.x Link Layer Configuration Guide Interface Specifiers The interface specifier format that you use depends on the type of physical interface on which you want to configure Frame Relay. For more information about supported interface types and specifiers on E Series routers, see Interface Types and Specifiers in JUNOSe Command Reference Guide.
Page 143: Configuring Frame Relay
Chapter 2: Configuring Frame Relay Configuring Frame Relay Configure a Frame Relay interface by entering Interface Configuration mode. The procedure that follows is an example of a Frame Relay configuration on a serial interface. All tasks are mandatory unless otherwise noted. To configure a Frame Relay interface: From Configuration mode, enter the physical interface on which you want to configure Frame Relay.
Page 144 JUNOSe 11.1.x Link Layer Configuration Guide Assign a local IP address to the circuit. host1(config-subif)#ip address 192.32.10.2 255.255.255.0 (Optional) Use show commands to verify that your configuration changes are correct by checking the state of the interfaces. host1#show frame-relay lmi host1#show frame-relay map host1#show frame-relay pvc (Optional) Disable the local management interface.
Page 145 Chapter 2: Configuring Frame Relay Use to assign a text description or an alias to a Frame Relay interface or subinterface. You can use this command to help you identify the interface and keep track of interface connections. The description or alias can be a maximum of 80 characters. Use “show frame-relay interface”...
Page 146 JUNOSe 11.1.x Link Layer Configuration Guide frame-relay intf-type Use to configure a Frame Relay interface circuit to operate as data communications equipment (DCE), data terminal equipment (DTE), or NNI. Frame Relay provides packet-switching data communications between user devices and network equipment across the interface. User devices are referred to as DTE.
Page 147 Chapter 2: Configuring Frame Relay Use to configure LMI counters and timers. LMI counters and timers have configurable ranges that allow you to control the state of the Frame Relay interface. In general, accept the default values for the timers and counters, unless you need to modify them according to a special arrangement with your customers.
Page 148 JUNOSe 11.1.x Link Layer Configuration Guide Use to configure one of the local management interface types. LMI provides configuration and status information relating to the virtual circuits operating over Frame Relay. LMI specifies polling mechanisms to receive incremental and full-status updates from the network.
Page 149 Chapter 2: Configuring Frame Relay NOTE: Before you configure Frame Relay, see the appropriate chapter in this guide for details on configuring physical interfaces. slot Router chassis slot port CT3, T3, or E3 module I/O port channel T1 (DS1) channel subchannel Set of DS0 timeslots.
Page 150 JUNOSe 11.1.x Link Layer Configuration Guide Use to assign a text description or an alias to a serial HDLC interface. You can use this command to help you identify the interface and keep track of interface connections. The description or alias can be a maximum of 80 characters. Use the show interfaces serial command to display information about the serial interfaces you configured.
Page 151: End-To-End Fragmentation And Reassembly
Chapter 2: Configuring Frame Relay End-to-End Fragmentation and Reassembly The fragmentation and reassembly feature reduces excessive delays of Frame Relay packets by breaking them up into smaller fragments and interleaving them with real-time frames. By doing this, real-time and non-real-time data frames can be carried together on lower-speed links without causing excessive delays to the real-time traffic.
Page 152: Map Class
JUNOSe 11.1.x Link Layer Configuration Guide Map Class Within Frame Relay, a map class acts as a container or context for fragmentation and reassembly parameters. Within the map class context, you can explicitly enable fragmentation and reassembly. After you define a map class, you can apply it to an unlimited number of subinterfaces.
Page 153 Chapter 2: Configuring Frame Relay host1((config-subif)#ip address 42.42.42.41 255.255.255.0 Associate a map class with a subinterface. host1(config-subif)#frame-relay class testmap encapsulation frame-relay ietf Use to specify Frame Relay as the encapsulation method for the interface. The router uses IETF format (RFC 2427 encapsulation). Example host1(config-if)#encapsulation frame-relay ietf Use the no version to remove Frame Relay configuration from an interface.
Page 154 JUNOSe 11.1.x Link Layer Configuration Guide frame-relay interface-dlci ietf Use to configure a Frame Relay PVC over a subinterface. The ietf keyword is mandatory and indicates RFC 2427 encapsulation. Define a DLCI in the range 16–1007. To configure a Frame Relay PVC, you must specify a DLCI. Frame Relay service is offered in the form of PVCs.
Page 155: Monitoring Frame Relay
Chapter 2: Configuring Frame Relay slot Router chassis slot port CT3, T3, or E3 module I/O port channel T1 (DS1) channel subchannel Set of DS0 timeslots; for information, see section Fractional T1 in JUNOSe Physical Layer Configuration Guide subinterface User-assigned nonnegative number that identifies a Frame Relay subinterface Example host1(config-if)#interface serial 5/0:4/1.1...
Page 156 JUNOSe 11.1.x Link Layer Configuration Guide If you do not specify an interface type for the appropriate show command, the output indicates whether a serial or POS interface is being displayed. baseline frame-relay interface Use to set a statistics baseline at the Frame Relay layer for multilink Frame Relay, POS, serial or GRE tunnel interfaces, subinterfaces, or circuits.
Page 157 Chapter 2: Configuring Frame Relay Use the brief keyword to display the operational status of all configured interfaces. Use the optional delta keyword to specify that baselined statistics are to be shown. Field descriptions status One of the following states: Up Traffic can flow on the interface Offline Traffic cannot flow because hardware is unavailable Down Traffic cannot flow because of a problem in the interface at the...
Page 158 JUNOSe 11.1.x Link Layer Configuration Guide In frames: 1233 Out frames: 1233 In errors: 0 Out errors: 0 In discards: 0 Out discards: 0 In unknown protos: 0 Frame relay interface 3/2:3/1, status is up Description: chicago03 Time since last status change 01:20:38 In bytes: 19696 Out bytes: 60744 In frames: 1231...
Page 159 Chapter 2: Configuring Frame Relay For the DCE: Enquiries received Total number of LMI status enquiries received by the DCE on this interface Enquiry responses sent Total number of LMI status responses sent by the DCE on this interface Full enquiry responses sent Total number of LMI full-status responses sent by the DCE on this interface Async updates sent Total number of LMI asynchronous updates sent by the DCE on this interface...
Page 160 JUNOSe 11.1.x Link Layer Configuration Guide Last sequence number sent: 0 Last sequence number received: 0 See show frame-relay lmi. show frame-relay map Use to display the current Frame Relay map entries and information about Frame Relay connections. Field descriptions Frame relay sub-interface Interface number and one of the following states: Up—Traffic can flow on the interface Offline—Traffic cannot flow because hardware is unavailable...
Page 161 Chapter 2: Configuring Frame Relay Use to display statistics about PVCs for Frame Relay layer on a multilink Frame Relay, POS, serial, or GRE tunnel interface or a specific PVC. Optionally, you can specify an interface using the interface type and specifier. For more information, see Interface Types and Specifiers in JUNOSe Command Reference Guide.
Page 162 JUNOSe 11.1.x Link Layer Configuration Guide Out DE pkts Number of packets transmitted with the DE bit set Dropped packets Number of dropped packets Example host1#show frame-relay pvc PVC information for frame relay NNI interface 3/2:1/1 DLCI 101 in sub-interface 3/2:1/1.1, status is active Number of circuit status inactive transitions is 0 Time since creation 03:27:29, last status change 01:21:29 In pkts: 0...
Page 163 Chapter 2: Configuring Frame Relay The brief keyword displays only the operational status of all configured subinterfaces. Field descriptions sub-interface Identifies the subinterface in slot/port:channel/subchannel.subinterface format status Status of the subinterface Description Text description or alias if configured for the subinterface Time since last status change Time since the last status change on the subinterface In bytes Number of inbound bytes received on the subinterface...
Page 164 JUNOSe 11.1.x Link Layer Configuration Guide In discards: 0 Out discards: 0 In unknown protos: 0 See show frame-relay subinterface. show frame-relay summary Use to scan all defined Frame Relay interfaces and circuits; reports aggregate status as one of the following: Up Traffic can flow on the interface Down Traffic cannot flow because of a problem in the network Unavailable Traffic cannot flow because hardware is unavailable...
Page 165: Configuring Multilink Frame Relay
Chapter 3 Configuring Multilink Frame Relay This chapter describes how to configure Multilink Frame Relay (MLFR) interfaces on E Series routers. This chapter contains the following sections: Overview on page 133 Platform Considerations on page 135 References on page 136 Supported MLFR Features on page 136 Unsupported MLFR Features on page 137 Before You Configure MLFR on page 138...
Page 166: Mlfr Link Integrity Protocol
JUNOSe 11.1.x Link Layer Configuration Guide This implementation of MLFR logically aggregates up to eight T1 or E1 connections into a single virtual connection, known as a bundle, to a given customer site. The connections can terminate at a CPE (Figure 5 on page 134) or a Multilink Frame Relay bridge (Figure 6 on page 134).
Page 167: Interface Stacking
Chapter 3: Configuring Multilink Frame Relay The DTE creates a link management interface (LMI) with the network by encapsulating the Frame Relay frame within an MLFR frame. You assign one or more data link control identifiers (DLCIs) to a bundle. Interface Stacking Because MLFR aggregates multiple link-layer channels onto a single network layer IP interface, protocol layering within the router is different than it is for nonmultilink...
Page 168: Module Requirements
JUNOSe 11.1.x Link Layer Configuration Guide Module Requirements For information about the modules that support MLFR interfaces on ERX14xx models, ERX7xx models, and the ERX310 router: See ERX Module Guide, Table 1, Module Combinations for detailed module specifications. See ERX Module Guide, Appendix A, Module Protocol Support for information about the modules that support MLFR.
Page 169: Unsupported Mlfr Features
Chapter 3: Configuring Multilink Frame Relay attempts to forward the traffic on a different link. If this attempt also fails, the router uses a round-robin approach. You can configure bundles as follows: On a cOCx/STMx line module and its corresponding I/O modules, you can configure: Member links from different OC3/STM1 ports in the same bundle The 336 available T1 channels combined in any manner that does not exceed...
Page 170: Before You Configure Mlfr
JUNOSe 11.1.x Link Layer Configuration Guide Before You Configure MLFR Before you begin configuring MLFR, you must configure the physical layer interfaces that will be aggregated by MLFR. The procedures described in this chapter assume that a physical layer interface, such as a T1 or T3 interface, has been configured.
Page 171: Configuration Example
Chapter 3: Configuring Multilink Frame Relay host1(config-subif)#frame-relay description bostonBundleSubOneDescription d. Assign an IP address to the subinterface. host1(config-subif)#ip address 10.10.100.1 255.255.255.0 Configuration Example The following commands configure three T1 lines and aggregate them into a multilink bundle named boston. host1(config)#interface serial 2/0:1 host1(config-if)#encapsulation mlframe-relay ietf host1(config-if)#exit host1(config)#interface serial 2/0:2...
Page 172: Monitoring Mlfr
JUNOSe 11.1.x Link Layer Configuration Guide interface mlframe-relay Use to create a Frame Relay major interface, also known as the MLFR bundle. Example host1(config-if)#interface mlframe-relay group2 Use the no version to delete the MLFR bundle. See interface mlframe-relay. member-interface Use to add an MLFR interface also known as an MLFR bundle member to an MLFR bundle.
Page 173 Chapter 3: Configuring Multilink Frame Relay You cannot set a baseline for groups of interfaces, subinterfaces, or circuits. You must set baselines one at a time. When baselining is requested, the time since the last baseline was set is displayed in hours:minutes:seconds or days/hours format.
Page 174 JUNOSe 11.1.x Link Layer Configuration Guide Up Traffic can flow on the interface Offline Traffic cannot flow because hardware is unavailable Down Traffic cannot flow because of a problem in the interface at the current protocol layer LowerLayerDown Traffic cannot flow because of a problem in an interface at a lower protocol layer AdministrativelyDown Traffic cannot flow because of manual administrative intervention...
Page 175 Chapter 3: Configuring Multilink Frame Relay Frame relay multilink member-interface 4/0:1 is up Frame relay multilink member-interface 4/1:1 is up See show frame-relay interface. show frame-relay lip Use to display the state of MLFR Link Integrity Protocol (LIP) on an MLFR link. Use the brief keyword to display the operational status of all configured interfaces.
Page 176 JUNOSe 11.1.x Link Layer Configuration Guide Hello Acknowledgments received Number of Hello messages received on this interface Remove Links sent Number of Remove Link messages sent from this interface Remove Links received Number of Remove Link messages received on this interface Remove Link Acknowledgments sent Number of Remove Link acknowledgments sent from this interface Remove Link Acknowledgments received Number of Remove Link...
Page 177 Chapter 3: Configuring Multilink Frame Relay Frame relay DTE interface mlframe-relay Name of the MLFR bundle N391 Value of the N391 full-status polling counter N392 Value of the N392 error threshold counter N393 Value of the N393 monitored events counter T391 Value of the T391 link integrity polling timer interval Configured LMI type One of the following options: ANSI ANSI T1.617 Annex D...
Page 178 JUNOSe 11.1.x Link Layer Configuration Guide Frame relay DCE interface mlframe-relay Name of the MLFR bundle N391 Value of the N391 full-status polling counter N392 Value of the N392 error threshold counter T392 Value of the T392 polling verification timer Configured LMI type: one of the following options: ANSI ANSI T1.617 Annex D Q933A ITU-T Q.933 Annex A...
Page 179 Chapter 3: Configuring Multilink Frame Relay Example 2 host1#show frame-relay lmi interface mlframe-relay TEST LMI information for frame relay DTE interface mlframe-relayTEST DTE parameter N391 is 6, N392 is 3, N393 is 4, T391 is 10 Configured LMI type is ANSI, status is up Number of interface down transitions is 0 Time since last status change 00:06:20 Enquiries sent: 39...
Page 180 JUNOSe 11.1.x Link Layer Configuration Guide Use to display the statistics about all MLFR interfaces or the specified MLFR interfaces. Field descriptions Multilink Frame relay interface Specifier for the Frame Relay interface State of the MLFR interface One of the following states: Up—Traffic can flow on the interface Offline—Traffic cannot flow because hardware is unavailable Down—Traffic cannot flow because of a problem in the interface at the...
Page 181 Chapter 3: Configuring Multilink Frame Relay show frame-relay pvc Use to display statistics about PVCs for Frame Relay interfaces. Specify a DLCI number or an interface type and location. Use the optional delta keyword to specify that baselined statistics are to be shown.
Page 182 JUNOSe 11.1.x Link Layer Configuration Guide Out DE pkts Number of packets transmitted with the DE bit set Dropped packets Number of dropped packets Example 1 host1#show frame-relay pvc brief PVC information for frame relay DTE interface mlframe-relayTEST DLCI 16 in sub-interface mlframe-relayTEST.1, status is active DLCI 17 in sub-interface mlframe-relayTEST.2, status is active Example 2 host1#show frame-relay pvc interface mlframe-relay TEST...
Page 183 Chapter 3: Configuring Multilink Frame Relay Use the optional delta keyword to specify that baselined statistics are to be shown. Field descriptions Frame relay sub-interface mlframe-relay Name and subinterface number of the MLFR bundle in the format bundle-name.subinterface-number status State of the subinterface, as follows: Up—Traffic can flow on the interface Offline—Traffic cannot flow because hardware is unavailable Down—Traffic cannot flow because of a problem in the interface at the...
Page 184 JUNOSe 11.1.x Link Layer Configuration Guide In bytes: 512 Out bytes: 0 In frames: 16 Out frames: 0 In errors: 0 Out errors: 0 In discards: 16 Out discards: 0 In unknown protos: 0 Frame relay sub-interface mlframe-relayTEST.2, status is up Number of sub-interface down transitions is 0 Time since last status change 00:07:50 In bytes: 512...
Page 185: Configuring Upper-Layer Protocols Over Static Ethernet Interfaces
Chapter 4 Configuring Upper-Layer Protocols over Static Ethernet Interfaces This chapter describes how to configure upper-layer protocols over static Ethernet interfaces on E Series routers. This chapter contains the following sections: Upper-Layer Protocols over Static Ethernet Overview on page 153 Upper-Layer Protocols over Static Ethernet Platform Considerations on page 154 Upper-Layer Protocols over Static Ethernet References on page 155 Configuring IP over a Static Ethernet Interface on page 155...
Page 186: Upper-Layer Protocols Over Static Ethernet Platform Considerations
JUNOSe 11.1.x Link Layer Configuration Guide Figure 8: Multiplexing Multiple Protocols over a Single Physical Link ERX14xx models (rear view) The following sections describe how to create the following common non-VLAN configurations, which you can configure on Fast Ethernet, Gigabit Ethernet, and 10-Gigabit Ethernet interfaces: IP over Ethernet PPPoE over Ethernet...
Page 187: Module Requirements
Chapter 4: Configuring Upper-Layer Protocols over Static Ethernet Interfaces Module Requirements For information about the modules supported on E Series routers: See the ERX Module Guide for modules supported on ERX7xx models, ERX14xx models, and the ERX310 router. See the E120 and E320 Module Guide for modules supported on the E120 and E320 routers.
Page 188: Configuring Pppoe Over A Static Ethernet Interface
JUNOSe 11.1.x Link Layer Configuration Guide Create an IP interface. host1(config-if)#ip address 192.5.127.8 255.255.255.0 Figure 9 on page 156 illustrates this configuration. Figure 9: Example of IP over Ethernet Stacking Configuration Procedure Configuring PPPoE over a Static Ethernet Interface To configure PPPoE over an Ethernet interface: Specify a Fast Ethernet, Gigabit Ethernet, or 10-Gigabit Ethernet port.
Page 189: Configuring Ip And Mpls Over A Static Ethernet Interface
Chapter 4: Configuring Upper-Layer Protocols over Static Ethernet Interfaces Figure 10: Example of PPPoE Stacking Configuration Procedure Configuring IP and MPLS over a Static Ethernet Interface To configure both IP and MPLS over an Ethernet interface: Specify a Fast Ethernet, Gigabit Ethernet, or 10-Gigabit Ethernet port. host1(config)#interface fastEthernet 4/0 Create an IP interface.
Page 190: Figure 12: Example Of Ip, Mpls, And Pppoe Stacking Configuration
JUNOSe 11.1.x Link Layer Configuration Guide host1(config-if)#ip address 192.5.127.8 255.255.255.0 Create an MPLS interface. host1(config-if)#mpls Create a PPPoE interface by specifying PPPoE as the encapsulation method on the interface. host1(config-if)#pppoe Create a PPPoE subinterface. host1(config-if)#pppoe subinterface fastEthernet 4/1.1 Specify PPP as the encapsulation method on the interface. host1(config-if)#encapsulation ppp Assign an IP address and mask.
Page 191: L2Tp And Ethernet
Chapter 4: Configuring Upper-Layer Protocols over Static Ethernet Interfaces Use to enable, disable, or delete MPLS on an interface. MPLS is disabled by default. Example host1(config)#mpls Use the no version to halt MPLS on the interface and delete the MPLS interface configuration.
Page 192 100BASE-LX-SM (100 Mbps) SFP (Empty) SFPs that are empty SFP (Non-compliant Juniper Part) SFPs that are installed in the FE-8 I/O module and do not have a Juniper Networks part number programmed MTU Size of the MTU for this interface...
Page 193 Chapter 4: Configuring Upper-Layer Protocols over Static Ethernet Interfaces Bytes Number of bytes received in error-free packets Unicast Number of unicast packets received Multicast Number of multicast packets received Broadcast Number of broadcast packets received Errors Total number of errors in all received packets; some packets might contain more than one error Discards Total number of discarded incoming packets Mac Errors Number of incoming packets discarded because of MAC...
Page 194 JUNOSe 11.1.x Link Layer Configuration Guide Late—Number of packets aborted during sending because of collisions after 64 bytes Excessive—Number of packets not sent because of too many collisions ARP Statistics Analysis of ARP traffic on this interface; In fields are for traffic received on the interface and Out fields are for traffic sent on the interface ARP requests Number of ARP requests...
Page 195 SFP 1000BASE-LH, 1000BASE-SX, 1000BASE-ZX; for SFPs that are empty, SFP (Empty) appears in this field; for SFPs that are installed in the OC3-2 GE APS I/O module and do not have a Juniper Networks part number programmed, SFP (GE Compliant) appears in this field XFP 10GBASE-SR (10 Gbps), 10GBASE-LR (10 Gbps), 10GBASE-ER (10 Gbps);...
Page 196 JUNOSe 11.1.x Link Layer Configuration Guide Duplex Mode Duplex option for this interface Operational Duplex option currently used Administrative Setting for duplex that you specified Speed Line speed for this interface Operational Current rate at which packets are processed Administrative Setting for line speed that you specified Debounce Debounce configuration for this interface State is Enabled, Disabled Interval is Number of seconds that this interface maintains a given...
Page 197 Chapter 4: Configuring Upper-Layer Protocols over Static Ethernet Interfaces In Analysis of inbound traffic on this interface Bytes Number of bytes received in error-free packets Unicast Number of unicast packets received Multicast Number of multicast packets received Broadcast Number of broadcast packets received Errors Total number of errors in all received packets;...
Page 198 JUNOSe 11.1.x Link Layer Configuration Guide Single Number of packets sent after one collision Multiple—Number of packets sent after multiple collisions Late—Number of packets aborted during sending because of collisions after 64 bytes Excessive—Number of packets not sent because of too many collisions Policed Statistics Number of packets that exceeded the number allowed and were policed (or dropped) ARP Statistics Analysis of ARP traffic on this interface;...
Page 199 Chapter 4: Configuring Upper-Layer Protocols over Static Ethernet Interfaces Dropped committed packets, bytes Number of committed packets and bytes that were dropped Dropped conformed packets, bytes Number of conformed packets and bytes that were dropped Dropped exceeded packets, bytes Number of exceeded packets and bytes that were dropped Example Displays the status of a Gigabit Ethernet interface host1#show interfaces gigabitEthernet 1/0...
Page 200 JUNOSe 11.1.x Link Layer Configuration Guide Monitoring Upper-Level Protocols over Ethernet...
Page 201: Configuring Vlan And S-Vlan Subinterfaces
Chapter 5 Configuring VLAN and S-VLAN Subinterfaces This chapter describes how to configure VLAN and S-VLAN subinterfaces on E Series routers. This chapter contains the following sections: VLAN Overview on page 169 S-VLAN Overview on page 170 VLAN and S-VLAN Platform Considerations on page 171 VLAN and S-VLAN References on page 172 Creating a VLAN Subinterface on page 172 Configuring an S-VLAN Subinterface on page 180...
Page 202: S-Vlan Overview
JUNOSe 11.1.x Link Layer Configuration Guide identifier (VCI) to multiplex the different channels over the physical link. The Ethernet protocol type serves the same function within a VLAN as the logical link control (LLC) subnetwork attachment point (SNAP) within a VC, to multiplex the different protocols over the channel.
Page 203: Vlan And S-Vlan Platform Considerations
Chapter 5: Configuring VLAN and S-VLAN Subinterfaces A stacked VLAN (S-VLAN) provides a two-level VLAN tag structure, which extends the VLAN ID space to more than 16 million VLANs. Creating an S-VLAN requires the use of a second encapsulation tag. The router performs decapsulation twice, once to get the S-VLAN tag and once to get the VLAN tag.
Page 204: Vlan And S-Vlan References
JUNOSe 11.1.x Link Layer Configuration Guide For ERX7xx models, ERX14xx models, and ERX310 router, use the slot/port[.subinterface ] format. For example, the following command specifies a VLAN subinterface configured on port 0 of an I/O module in slot 4. host1(config)#interface fastEthernet 4/0.1 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.
Page 205: Configuring Ip Over Vlan
Chapter 5: Configuring VLAN and S-VLAN Subinterfaces Specify VLAN as the encapsulation method. host1(config-if)#encapsulation vlan The router creates the VLAN major interface. You can now create multiple VLAN subinterfaces to carry higher-level protocols. For examples, see “Creating a VLAN Subinterface” on page 172, next. Configuring IP over VLAN To configure IP over VLAN over an Ethernet interface: Specify a Fast Ethernet, Gigabit Ethernet, or 10-Gigabit Ethernet port.
Page 206: Configuring Pppoe Over Vlan
JUNOSe 11.1.x Link Layer Configuration Guide Figure 14: Example of IP/VLAN/Fast Ethernet Stacking Configuration Procedure Configuring PPPoE over VLAN To configure PPPoE over VLAN over an Ethernet interface: Specify a Fast Ethernet, Gigabit Ethernet, or 10-Gigabit Ethernet port. host1(config)#interface fastEthernet 4/1 Specify VLAN as the encapsulation method.
Page 207: Configuring Mpls Over Vlan
Chapter 5: Configuring VLAN and S-VLAN Subinterfaces host1(config-if)#pppoe subinterface fastEthernet 4/1.1.1 Specify PPP as the encapsulation method on the interface. host1(config-if)#encapsulation ppp Assign an IP address and mask. host1(config-if)#ip address 192.6.129.5 255.255.255.0 (Optional) Configure additional VLAN subinterfaces by completing Steps 3 through Figure 15 on page 175 illustrates the PPPoE/VLAN/Fast Ethernet stacking, showing two separate VLAN subinterfaces.
Page 208: Configuring Ip Over Vlan And Pppoe Over Vlan
JUNOSe 11.1.x Link Layer Configuration Guide Specify VLAN as the encapsulation method. host1(config-if)#encapsulation vlan The VLAN major interface is added. Create a VLAN subinterface by adding a subinterface number to the interface identification command. host1(config-if)#interface fastEthernet 4/1.1 Do one of the following: Assign a VLAN ID for the subinterface.
Page 209 Chapter 5: Configuring VLAN and S-VLAN Subinterfaces The VLAN major interface is added. Create a VLAN subinterface by adding a subinterface number to the interface identification command. host1(config-if)#interface fastEthernet 4/1.1 Do one of the following: Assign a VLAN ID for the subinterface. host1(config-if)#vlan id 400 Assign a VLAN ID and the optional unique MAC address for the subinterface.
Page 210: Figure 17: Example Of Pppoe Over Vlan With Ip Over Vlan Stacking
JUNOSe 11.1.x Link Layer Configuration Guide Figure 17 on page 178 illustrates the configuration steps for two VLAN subinterfaces. In this example: VLAN subinterface 4/1.1 has an IP interface, a PPPoE interface, and multiple PPPoE subinterface stacks. VLAN subinterface 4/1.2 has only an IP interface. NOTE: Before you can remove a VLAN subinterface, you must remove the upper-layer interface stack.
Page 211 Chapter 5: Configuring VLAN and S-VLAN Subinterfaces encapsulation vlan Use to configure VLAN as the encapsulation method for the interface. Example host1(config-if)#encapsulation vlan Use the no version to disable VLAN on an interface. See encapsulation vlan. ip address Use to set a primary or secondary IP address for an interface or subinterface. Specify the layer 2 encapsulation before you set the IP address.
Page 212: Configuring An S-Vlan Subinterface
JUNOSe 11.1.x Link Layer Configuration Guide host1(config-if)#pppoe subinterface gigabitEthernet 4/2.1.1 Example 2 Creates a PPPoE subinterface on the E320 router host1(config-if)#pppoe subinterface tenGigabitEthernet 4/0/2.1.1 Use the no version to remove a PPPoE subinterface on a Gigabit Ethernet interface or on a 10-Gigabit Ethernet interface. See pppoe subinterface.
Page 213: Configuring An S-Vlan Subinterface
Chapter 5: Configuring VLAN and S-VLAN Subinterfaces “Configuring PPPoE over an S-VLAN” on page 181 Configuring an S-VLAN Subinterface To configure an S-VLAN subinterface: Specify a Fast Ethernet, Gigabit Ethernet, or 10-Gigabit Ethernet port. host1(config)#interface fastEthernet 4/0 Specify VLAN as the encapsulation method. host1(config-if)#encapsulation vlan The VLAN major interface is added.
Page 214: Figure 18: Example Of Pppoe Over S-Vlan Stacking Configuration
JUNOSe 11.1.x Link Layer Configuration Guide Specify PPPoE as the encapsulation method on the interface. host1(config-if)#pppoe Create a PPPoE subinterface. host1(config-if)#pppoe subinterface fastEthernet 4/1.1.1 Specify PPP as the encapsulation method on the interface. host1(config-if)#encapsulation ppp Assign an IP address and mask. host1(config-if)#ip address 164.10.6.61 255.255.255.0 (Optional) Configure additional PPPoE subinterfaces by completing Steps 7 through 9 using unique numbering.
Page 215 Chapter 5: Configuring VLAN and S-VLAN Subinterfaces Use to configure PPP as the encapsulation method for the interface. Use the no version to remove PPP as the encapsulation method on the interface. See encapsulation ppp. encapsulation vlan Use to configure VLAN as the encapsulation method for the interface. Use the no version to remove VLAN as the encapsulation method on the interface.
Page 216: Configuring S-Vlan Tunnels For Layer 2 Services Over Mpls
JUNOSe 11.1.x Link Layer Configuration Guide 9100 Specifies Ethertype value 0x9100, which is the default Use an Ethertype value that matches the Ethertype value set on the customer premises equipment (CPE) to which your router connects. Example host1(config-if)#svlan ethertype 8100 Use the no version to restore the default value, 9100.
Page 217: Interface Stacking
Chapter 5: Configuring VLAN and S-VLAN Subinterfaces Figure 19: S-VLAN Tunnels for Ethernet Layer 2 Services over MPLS In this example, traffic from three VLAN subinterfaces must traverse the MPLS network. To accomplish this using standard S-VLANs, you issue the following commands to configure three separate S-VLANs with the same S-VLAN ID value and different VLAN IDs, as follows: host1(config-if)#svlan id 33 10...
Page 218: Host1(Config-If)#Interface Fastethernet 8/1.1
JUNOSe 11.1.x Link Layer Configuration Guide To configure S-VLAN tunnels for Ethernet layer 2 services over MPLS: Specify a Fast Ethernet, Gigabit Ethernet, or 10-Gigabit Ethernet port. host1(config)#interface fastEthernet 4/0 Specify VLAN as the encapsulation method to create the VLAN major interface. host1(config-if)#encapsulation vlan Create a VLAN subinterface.
Page 219 Chapter 5: Configuring VLAN and S-VLAN Subinterfaces Use the no version to remove the interface or subinterface. You must issue the no version from the highest level down; you cannot remove an interface or subinterface if the one above it still exists. See interface fastEthernet.
Page 220: S-Vlan Oversubscription
JUNOSe 11.1.x Link Layer Configuration Guide host1(config-if)#svlan id 1000 any There is no no version. See svlan id. S-VLAN Oversubscription When you configure S-VLAN subinterfaces over Ethernet interfaces to support dynamic PPPoE subinterfaces, you can take advantage of S-VLAN oversubscription. The following module combinations support S-VLAN oversubscription: GE/FE line module and all of its associated I/O modules GE-2 line module and the GE-2 SFP I/O module...
Page 221: Displaying Interface Rate Statistics For Vlan Subinterfaces
Chapter 5: Configuring VLAN and S-VLAN Subinterfaces NOTE: The E120 and E320 routers output for monitor and show commands is identical to output from other E Series routers, except that the E120 and E320 routers output also includes information about the adapter identifier in the interface specifier (slot/adapter/port).
Page 222 JUNOSe 11.1.x Link Layer Configuration Guide Interface polls Input bps/pps Output bps/pps (UTC) ----------------------- -------- --------------- --------------- -------- FastEthernet 0/0.1 --/-- --/-- 10:50:07 FastEthernet 4/0.1 --/-- --/-- 10:50:07 FastEthernet 0/0.1 120240/100 120240/100 10:50:12 FastEthernet 4/0.1 120000/100 120000/100 10:50:12 FastEthernet 0/0.1 120240/100 120240/100 10:50:17 FastEthernet 4/0.1...
Page 223: Using Ethernet Show Commands
Chapter 5: Configuring VLAN and S-VLAN Subinterfaces Output bps/pps Number of bits per second (bps) and packets per second (pps) transmitted on this interface during the specified load interval Time Time of day, in hh:mm:ss format, at which the router calculates the bit rate and packet rate statistics for the current interval Example 1 Displays bit rate and packet rate statistics over the default (5-second) load interval for a single VLAN subinterface...
Page 224 JUNOSe 11.1.x Link Layer Configuration Guide brief Displays the operational status of all configured interfaces Field descriptions when you display the status of a Fast Ethernet VLAN or S-VLAN subinterface Subinterface number Location of the subinterface that carries the VLAN or S-VLAN traffic Administrative status Operational state that you configured for this interface;...
Page 225 Chapter 5: Configuring VLAN and S-VLAN Subinterfaces In: Bytes 39256, Packets 612 Multicast 0, Broadcast 0 Errors 0, Discards 0 Out: Bytes 4536220, Packets 70873 Multicast 0, Broadcast 70258 Errors 0, Discards 0 ARP Statistics: In: ARP requests 1, ARP responses 0 Errors 0, Discards 0 Out: ARP requests 1, ARP responses 0 Errors 0, Discards 0...
Page 226 JUNOSe 11.1.x Link Layer Configuration Guide In Analysis of inbound traffic on this interface Bytes Number of bytes received on the VLAN or S-VLAN subinterface Packets Sum of all unicast, broadcast, and multicast packets received on the VLAN or S-VLAN subinterface Multicast Number of multicast packets received on the VLAN or S-VLAN subinterface Broadcast Number of broadcast packets received on the VLAN or...
Page 227 Chapter 5: Configuring VLAN and S-VLAN Subinterfaces In: Bytes 2357, Packets 23 Multicast 0, Broadcast 0 Errors 0, Discards 0 Out: Bytes 4872, Packets 57 Multicast 0, Broadcast 57 ARP Statistics: In: ARP requests 0, ARP responses 0 Errors 0, Discards 0 Out: ARP requests 0, ARP responses 0 Errors 0, Discards 0 See show interfaces.
Page 228 JUNOSe 11.1.x Link Layer Configuration Guide Broadcast Number of broadcast packets received on the VLAN or S-VLAN subinterface Errors Total number of errors in all received packets; some packets might contain more than one error Discards Total number of discarded incoming packets Out Analysis of outbound traffic on this interface Bytes Number of bytes sent on the VLAN or S-VLAN subinterface Packets Number of packets sent on the VLAN or S-VLAN subinterface...
Page 229 Chapter 5: Configuring VLAN and S-VLAN Subinterfaces host1#show vlan subinterface fastEthernet 0/0.1 Interface Status Svlan Id Vlan Id Ethertype Type ------------------- ------ ---- -------- ------ --------- ------- FastEthernet 0/0.1 1526 0x9100 Static In: Bytes 39256, Packets 612 Multicast 0, Broadcast 0 Errors 0, Discards 0 Out: Bytes 4538652, Packets 70911 Multicast 0, Broadcast 70296...
Page 230 JUNOSe 11.1.x Link Layer Configuration Guide Monitoring VLAN and S-VLAN Subinterfaces...
Page 231: Configuring 802.3Ad Link Aggregation And Link Redundancy
Chapter 6 Configuring 802.3ad Link Aggregation and Link Redundancy This chapter describes how to configure 802.3ad link aggregation and link redundancy on E Series routers. This chapter contains the following sections: 802.3ad Link Aggregation for Ethernet Overview on page 199 802.3ad Link Aggregation Platform Considerations on page 201 802.3ad Link Aggregation References on page 202 Configuring 802.3ad Link Aggregation on page 202...
Page 232: Lacp
JUNOSe 11.1.x Link Layer Configuration Guide For information about the modules that support link aggregation, see ERX Module Guide, Appendix A, Module Protocol Support and E120 and E320 Module Guide, Appendix A, IOA Protocol Support. LACP The Link Aggregation Control Protocol (LACP) is a mechanism for exchanging port and system information to create and maintain LAG bundles.
Page 233: Load Balancing And Qos
Chapter 6: Configuring 802.3ad Link Aggregation and Link Redundancy NOTE: On the ES2 10G LM and ES2-S1 GE-8 IOA combination, you can only configure IP or VLAN over a LAG bundle. Load Balancing and QoS You can configure load balancing across 802.3ad links to provide quality of service (QoS).
Page 234: Interface Specifiers
JUNOSe 11.1.x Link Layer Configuration Guide For information about the modules that support 802.3ad link aggregation on the E120 and E320 routers: See E120 and E320 Module Guide, Table 1, Modules and IOAs for detailed module specifications. See E120 and E320 Module Guide, Appendix A, IOA Protocol Support for information about the modules that support 802.3ad link aggregation.
Page 235: Configuring An Ethernet Physical Interface
Chapter 6: Configuring 802.3ad Link Aggregation and Link Redundancy “Configuring IP for a LAG Bundle” on page 204 “Configuring a VLAN Subinterface for a LAG Bundle” on page 204 “Configuring a PPPoE Subinterface for a LAG Bundle” on page 204 “Configuring MPLS for a LAG Bundle”...
Page 236: Configuring Ip For A Lag Bundle
JUNOSe 11.1.x Link Layer Configuration Guide Configuring IP for a LAG Bundle To configure IP for a LAG bundle, perform the following steps: Specify the LAG bundle. host1(config)#interface lag bundleBoston Assign an IP address and mask. host1(config-if)#ip address 192.5.127.8 255.255.255.0 Configuring a VLAN Subinterface for a LAG Bundle To configure a VLAN subinterface for the LAG bundle, perform the following steps: Specify VLAN as the encapsulation method.
Page 237: Configuring Mpls For A Lag Bundle
Chapter 6: Configuring 802.3ad Link Aggregation and Link Redundancy Specify PPP as the encapsulation method on the PPPoE subinterface. host1(config-if)#encapsulation ppp Assign an IP address and mask. host1(config-if)#ip address 192.168.1.2 255.255.0.0 You can also configure a PPPoE subinterface over a VLAN subinterface over a LAG bundle.
Page 238 JUNOSe 11.1.x Link Layer Configuration Guide Use the no version to restore the default behavior. See lacp. lacp port-priority Use to set the priority for an Ethernet link in a LAG bundle. The member with the lowest value has the highest priority, and is selected to join the LAG bundle first.
Page 239: Example: Configuring An Ip Interface For A Lag Bundle
Chapter 6: Configuring 802.3ad Link Aggregation and Link Redundancy Use the no version to halt MPLS on the interface and delete the MPLS interface configuration. See mpls. Use to specify the MTU for a LAG bundle. Specify a value in the range 64–9188 bytes. The range for FE-8 I/O modules is 64–9042 bytes.
Page 240: Example: Configuring A Pppoe Subinterface For A Lag Bundle
JUNOSe 11.1.x Link Layer Configuration Guide host1(config-if)#lacp active host1(config-if)#interface fastEthernet 0/5 host1(config-if)#speed 100 host1(config-if)#duplex full host1(config-if)#lacp active The following commands create a virtual router, add the Ethernet physical interfaces to a LAG bundle named bundleBoston, and assign an IP address and mask to the bundle.
Page 241: Example: Configuring A Pppoe Subinterface Over A Vlan For A Lag Bundle
Chapter 6: Configuring 802.3ad Link Aggregation and Link Redundancy Example: Configuring a PPPoE Subinterface over a VLAN for a LAG Bundle The following example displays LACP configuration for two Fast Ethernet interfaces in slot 3. The interfaces are enabled for active LACP. The speed and duplex characteristics are the same for both interfaces.
Page 242: Example: Configuring Mpls Over A Vlan For A Lag Bundle
JUNOSe 11.1.x Link Layer Configuration Guide host1(config-if)#speed 100 host1(config-if)#duplex full host1(config-if)#lacp active host1(config-if)#interface fastEthernet 5/1 host1(config-if)#speed 100 host1(config-if)#duplex full host1(config-if)#lacp active The following commands create a virtual router, add the Ethernet physical interfaces to a LAG bundle named kanata, assign an IP address, and configure MPLS. host1(config)#virtual router kanata host1:kanata(config)#interface lag kanata host1:kanata(config-if)#member-interface fastEthernet 0/0...
Page 243: Ethernet Link Redundancy Overview
Chapter 6: Configuring 802.3ad Link Aggregation and Link Redundancy Ethernet Link Redundancy Overview You can use 802.3ad Link Aggregation (LAG) to configure Ethernet link redundancy for Fast Ethernet and Gigabit Ethernet interfaces. Ethernet link redundancy enables you to protect against physical link failure and account for network topology changes that redirect network traffic to redundant ports.
Page 244: Ethernet Link Redundancy Configuration Diagrams
JUNOSe 11.1.x Link Layer Configuration Guide NOTE: You cannot configure link redundancy across different types of line modules in a router. You also cannot configure link redundancy across two GE-4 IOAs on the E120 or the E320 routers. Figure 21 on page 212 illustrates the configuration models for Ethernet link redundancy.
Page 245: Figure 22: Ge-2 Line Module Using Physical Port Redundancy
Chapter 6: Configuring 802.3ad Link Aggregation and Link Redundancy Figure 22: GE-2 Line Module Using Physical Port Redundancy Figure 23 on page 213 displays a single-homed configuration with port 0 backing up port 1 on a GE-2 line module. Figure 23: Single-Homed GE-2 Line Module Configuration Figure 24 on page 213 displays an FE-8 line module with a link failure in a 1:N FE-8 Line Module single-homed configuration.
Page 246: Figure 25: Fe-8 Line Module With 4 Redundant Ethernet Links (1:1)
JUNOSe 11.1.x Link Layer Configuration Guide Figure 25: FE-8 Line Module with 4 Redundant Ethernet Links (1:1) Figure 26 on page 214 and Figure 27 on page 215 display link redundancy E120 and E320 Routers configurations on the E120 and E320 routers. Configurations Figure 26 on page 214 displays a single-homed 1:4 configuration on an E120 router.
Page 247: Ethernet Link Redundancy Behavior
Chapter 6: Configuring 802.3ad Link Aggregation and Link Redundancy Figure 27: GE-8 IOA Configuration Across IOAs (1:N) Figure 28 on page 215 displays how you can configure Ethernet link redundancy with Dual-Homed LACP disabled locally using a dual-homed configuration. LACP is disabled because Configurations with LAG there is no LAG at the peer.
Page 248: Link Failure And Acquisition
JUNOSe 11.1.x Link Layer Configuration Guide The following sections describe link redundancy behavior when the: Configuration and status of LACP changes during link failure and acquisition. Configuration of the endpoints of the member links is different. Configuration is LAG to non-LAG in an RSTP network. Link Failure and Acquisition Link failure on the local system occurs when the active link is no longer active.
Page 249: Reverting After A Failover
Chapter 6: Configuring 802.3ad Link Aggregation and Link Redundancy Reverting After a Failover When you specify the auto-revert keyword with the redundant-port command, the redundant link reverts back to redundant mode when the failed link becomes active again. The system uses the following processes when the auto-revert feature is enabled (by specifying the auto-revert keyword) or disabled.
Page 250: Member Link With Non-Lag Partner
JUNOSe 11.1.x Link Layer Configuration Guide Table 10: Behavior of Member Links Using Local and Remote LACP Modes Remote LACP Mode Disabled Passive Active Local LACP Mode Disabled – Passive Active – Member Link with Non-LAG Partner When a member link has a non-LAG partner, there are two separate links in a 1:1 configuration.
Page 251: Acquiring Initial Links
Chapter 6: Configuring 802.3ad Link Aggregation and Link Redundancy Figure 29: Dual-Homed Heterogeneous Configuration in an RSTP Network Figure 29 on page 219 displays a network with RSTP enabled on Gigabit Ethernet switches 1 and 2. The local port receives bridge PDUs (BPDU), Ethernet broadcasts, and flooded unicast packets.
Page 252: Failing Over
JUNOSe 11.1.x Link Layer Configuration Guide When the network cannot reach the active link because of topology changes, traffic appears on the redundant link. The redundant port detects the traffic and captures the latest timestamp. When the difference between the timestamp of the first non-bridged PDU and the time the last packet that was received on the active port is sufficiently large to account for the minimum spanning tree convergence time and latency for flooded and broadcast packets, then the port...
Page 253 Chapter 6: Configuring 802.3ad Link Aggregation and Link Redundancy host1(config-if)#redundant-port gigabitEthernet 1/1 force-failover (Optional) Configure the redundant link to revert back to redundant mode when the failed link becomes active again. host1(config-if)#redundant-port gigabitEthernet 1/1 auto-revert redundant-port Use to specify a member link in a LAG bundle as redundant. Use the failover timeout keyword to configure the amount of time between the current link event leading to failover or reversion and the previous link failover or reversion.
Page 254: Monitoring 802.3Ad Link Aggregation
JUNOSe 11.1.x Link Layer Configuration Guide host1(config-if)#redundant-port gigabitEthernet 4/0 force-failover There is no no version. See redundant-port force-failover. Monitoring 802.3ad Link Aggregation This section explains how to use the show commands to display the characteristics and the configured settings for 802.3ad link aggregation. NOTE: The E120 and E320 routers output for monitor and show commands is identical to output from other E Series routers, except that the E120 and E320 routers output also includes information about the adapter identifier in the interface specifier...
Page 255 Chapter 6: Configuring 802.3ad Link Aggregation and Link Redundancy LACP state active Actor link actively particulates in LACP passive Actor link transmits LACP PDUs timeout Timeout control value; this value is not configurable and is set to long timeout (30 seconds) aggregatable Actor link can be aggregated individual Actor link cannot be aggregated;...
Page 256 JUNOSe 11.1.x Link Layer Configuration Guide collecting Partner link is actively collecting incoming frames; if this field does not appear, the Partner link is not actively collecting incoming frames distributing Partner link is actively distributing outgoing frames; if this field does not appear, the Partner link is not actively distributing outgoing frames defaulted Partner link is using defaulted operational information about the Partner link that was administratively configured for Partner;...
Page 257 Chapter 6: Configuring 802.3ad Link Aggregation and Link Redundancy Marker Protocol response packets: received 0, transmitted 0 Discarded 0, unknown protocol received 0 See show interfaces lag. show interfaces lag members Use to display information about the Ethernet member links in all IEEE 802.3ad link aggregation group (LAG) bundles configured on the router, or about the member links in a specified IEEE 802.3ad LAG bundle.
Page 258 JUNOSe 11.1.x Link Layer Configuration Guide Monitoring 802.3ad Link Aggregation...
Page 259: Configuring Ieee 802.3Ah Oam Link-Fault Management
Chapter 7 Configuring IEEE 802.3ah OAM Link-Fault Management This chapter describes how to configure IEEE 802.3ah Operation, Administration, and Maintenance (OAM) link-fault management on your E Series router, and contains the following sections: Ethernet OAM Link-Fault Management Overview on page 228 Ethernet OAM Link-Fault Management Platform Considerations on page 229 Ethernet OAM Link-Fault Management References on page 230 OAM Messages on page 230...
Page 260: Ethernet Oam Link-Fault Management Overview
JUNOSe 11.1.x Link Layer Configuration Guide Ethernet OAM Link-Fault Management Overview The growth of Ethernet as a large-scale networking technology has propelled the necessity for a new set of Operation, Administration, and Maintenance (OAM) protocols. Service provider networks are large and expansive, with the need for different communication operators to work in a combined way to deliver end-to-end services to enterprise users.
Page 261: Ethernet Oam Link-Fault Management Platform Considerations
Chapter 7: Configuring IEEE 802.3ah OAM Link-Fault Management Ethernet OAM Link-Fault Management Platform Considerations on page 229 Ethernet OAM Link-Fault Management References on page 230 Ethernet OAM Link-Fault Management Platform Considerations You can configure 802.3ah link-fault management on the following E Series routers: E120 router E320 router ERX1440 router...
Page 262: Ethernet Oam Link-Fault Management References
JUNOSe 11.1.x Link Layer Configuration Guide interface specifier. For example, the following command specifies a Gigabit Ethernet interface on port 0 of the IOA installed in the upper adapter bay of slot 3. host1(config)#interface gigabitEthernet 3/0/0 For more information about interface types and specifiers on E Series models, see Interface Types and Specifiers in JUNOSe Command Reference Guide.
Page 263: Oam Elements Overview
Chapter 7: Configuring IEEE 802.3ah OAM Link-Fault Management The Flags field is used to inform the local state to the peer. This state is used in discovery and in remote failure detection. The Code field denotes the type of OAM packet.
Page 264: Oam Client
JUNOSe 11.1.x Link Layer Configuration Guide Figure 31: OAM Sublayer Interfaces OAM Client MAC Client OAM_CTL.req OAMPDU.req MAC:MA_DATA.req 802.3 OAM Client 802.3 MAC data service interface service interface OAM_CTL.ind OAMPDU.ind MAC:MA_DATA.ind OAM Sublayer 802.3 MAC data service interface MAC:MA_DATA.req MAC:MA_DATA.ind MAC control The following sections describe the OAM elements: OAM Client on page 232...
Page 265: Control Block
Chapter 7: Configuring IEEE 802.3ah OAM Link-Fault Management The OAM sublayer is made up of three entities: control block, multiplexer, and packet parser. The following sections describe each of the entities. Figure 32 on page 233 shows the entities of the OAM sublayer and the traversal of OAM PDUs among the different entities.
Page 266: Oam Feature Overview
JUNOSe 11.1.x Link Layer Configuration Guide OAM Elements Overview on page 231 OAM Feature Overview An important behavior of a carrier-class network element is the implementation of OAM capabilities. These capabilities relate to operational fields, such as link monitoring, fault signaling, and remote loopback across multi-vendor equipment, administrative boundaries, and diversified physical locations.
Page 267: Information Oam Pdu Components
Chapter 7: Configuring IEEE 802.3ah OAM Link-Fault Management The discovery mode that you set up for an OAM entity also determines certain other attributes that can be initiated by an OAM entity. For example, a passive mode OAM entity cannot initiate a variable request or a loopback procedure. In a carrier environment, the customer edge (CE) devices are normally configured for passive mode operation, whereas the provider edge (PE) equipment is configured for active mode operation.
Page 268: Oam Link Monitoring Feature
JUNOSe 11.1.x Link Layer Configuration Guide You can configure the OAM discovery function in JUNOSe Software per Ethernet major interface as either active or passive mode. The OAM state machine labels a port to be in the operational down state until the discovery process is completed successfully.
Page 269: Supported Error Events For Tracking Link Faults
Chapter 7: Configuring IEEE 802.3ah OAM Link-Fault Management You can monitor frame and symbol errors by setting up a monitoring period or window and a threshold value. If the number of errors observed during the window meets or exceeds the configured low threshold, an Event Notification PDU (in the appropriate TLVs) is generated and sent to the peer.
Page 270: Oam Remote Fault Detection Feature
JUNOSe 11.1.x Link Layer Configuration Guide Failover On GE-2 and GE-HDE line modules that are paired with GE-2 SFP I/O modules with physical link redundancy, this action attempts to transition the link from active to redundant. By default, no action is performed on the link. The operational status displayed in the output of the show commands for interfaces is down if the OAM session is marked as down/nonfunctional after the configured action is taken on the link.
Page 271: Dying Gasp
Chapter 7: Configuring IEEE 802.3ah OAM Link-Fault Management Dying Gasp This event type denotes that an unrecoverable condition, such as a power failure, has taken place. This type of condition is vendor specific. A notification about the condition might be sent immediately and continuously. If you configure this option, the local OAM entity detects unrecoverable error conditions that occurred in the receive path of the link.
Page 272: Oam Remote And Local Loopback Feature
JUNOSe 11.1.x Link Layer Configuration Guide OAM Remote and Local Loopback Feature Remote loopback mode ensures link quality between the router and a remote peer during installation or troubleshooting. JUNOSe Software can place a remote entity into loopback mode (if remote loopback mode is supported by the remote entity). When you place a remote entity into loopback mode, the interface receives the remote loopback request and puts the interface into remote loopback mode.
Page 273: Figure 33: Interrelationship Between 802.3Ah Oam And 802.3Ad Lag
Chapter 7: Configuring IEEE 802.3ah OAM Link-Fault Management page 241 shows the interconnection between OAM and LAG bundles. You can use the results of OAM link monitoring to configure the LAG sublayer accordingly to improve failover and recovery times. Figure 33: Interrelationship Between 802.3ah OAM and 802.3ad LAG MAC Client MAC data OAM Client...
Page 274: Guidelines For Configuring 802.3Ah Oam Link-Fault Management
JUNOSe 11.1.x Link Layer Configuration Guide Guidelines for Configuring 802.3ah OAM Link-Fault Management Keep the following points in mind when you configure OAM link-fault management on Ethernet interfaces: The OAM application transmits and receives an OAM PDU at a maximum frequency of every 100 milliseconds (10 OAM PDUs/sec) on every port on the set of IOAs for a line module.
Page 275 Chapter 7: Configuring IEEE 802.3ah OAM Link-Fault Management messages or OAM PDUs are of standard length, untagged Ethernet frames within the normal frame length limits in the range 64–1518 bytes. To configure OAM link-fault management on an Ethernet interface: Specify a Fast Ethernet, Gigabit Ethernet, or 10-Gigabit Ethernet interface, and enable IEEE 802.3ah OAM support on the interface.
Page 276 JUNOSe 11.1.x Link Layer Configuration Guide host1(config-if)#ethernet oam lfm pdu-lost-threshold 4 In this example, the local interface is set to wait for 4 OAM PDUs to be missed from the remote peer before it generates a link-fault event. You can configure the local interface to wait for a larger number of OAM PDUs to be missed from the remote peer in networks that are prone to high losses and fluctuating performances, such as jitter, higher latency, and poor transmission of packets.
Page 277 Chapter 7: Configuring IEEE 802.3ah OAM Link-Fault Management low threshold settings. The high and low threshold settings are reset whenever a new window, during which errors are counted, commences. d. Configure a low threshold value for errored frame seconds, which causes an Errored Frame Seconds Summary Event TLV to be sent to the OAM entity when the threshold is exceeded.
Page 278 JUNOSe 11.1.x Link Layer Configuration Guide host1(config-if)#ethernet oam lfm link-monitor symbol-period threshold low In this case, a low symbol errors threshold of 10 symbols is set. When this threshold is exceeded, the action configured on the interface using the ethernet oam lfm high-threshold action command is taken. Specify a period of time in which symbol error events are counted for both high and low threshold settings.
Page 279 Chapter 7: Configuring IEEE 802.3ah OAM Link-Fault Management host1(config-if)#ethernet oam lfm remote-failure dying-gasp action disable-interface host1(config-if)#ethernet oam lfm remote-failure link-fault action disable-interface The operational status of the interface is set to down when an OAM PDU is received from the remote peer by the local OAM entity to signal fault conditions at the remote entity.
Page 280 JUNOSe 11.1.x Link Layer Configuration Guide b. Alternatively, you can disable the remote loopback operation on the remote OAM entity by instructing it to not loop back any received non-OAM PDUs from the local OAM entity. host1#ethernet oam lfm remote-loopback stop interface gigabitEthernet When you halt the remote loopback operation to cause the remote peer to not loop back any PDUs that it receives from the local entity by using the ethernet oam lfm remote-loopback stop command, the number of frames...
Page 281: Example: Configuring 802.3Ah Oam Link-Fault Management And Enabling Remote Failure Monitoring On An Interface
Chapter 7: Configuring IEEE 802.3ah OAM Link-Fault Management Example: Configuring 802.3ah OAM Link-Fault Management and Enabling Remote Failure Monitoring on an Interface The following example shows how to enable the OAM link-fault management feature on an interface and configure a link monitoring operation for frame seconds events on the interface.
Page 282: Example: Enabling Remote Loopback Support On The Local Interface
JUNOSe 11.1.x Link Layer Configuration Guide ethernet oam lfm link-monitor frame-seconds-summary ethernet oam lfm link-monitor symbol-period ethernet oam lfm remote-failure Example: Enabling Remote Loopback Support on the Local Interface You can allow a remote entity to set a local interface into remote loopback mode on all Ethernet interfaces on the E Series routers in which OAM link-fault management support is present.
Page 283: Table 11: Show Ethernet Oam Lfm Discovery Output Fields
Chapter 7: Configuring IEEE 802.3ah OAM Link-Fault Management Capabilities : link events, loopback, variable retrieval Mux Action : Forwarding Parser Action : Forwarding Table 11 on page 251 lists the show ethernet oam lfm discovery command output Meaning fields. Table 11: show ethernet oam lfm discovery Output Fields Field Name Field Description Interface type/name...
Page 284 JUNOSe 11.1.x Link Layer Configuration Guide Table 11: show ethernet oam lfm discovery Output Fields (continued) Field Name Field Description Capabilities Functions that the interface of the local entity can perform, such as link monitoring or responding to remote loopback requests. With this information a peer can determine what functions are supported and accessible;...
Page 285: Monitoring Oam Link-Fault Management Statistics For An Interface
Chapter 7: Configuring IEEE 802.3ah OAM Link-Fault Management Table 11: show ethernet oam lfm discovery Output Fields (continued) Field Name Field Description Capabilities Functions that the interface of the remote peer can perform, such as link monitoring or responding to remote loopback requests. With this information a peer can determine what functions are supported and accessible;...
Page 286: Table 12: Show Ethernet Oam Lfm Statistics Output Fields
JUNOSe 11.1.x Link Layer Configuration Guide Event Notification OAMPDUs Errored Frame Errored Symbol Duplicate Event Notification OAMPDUs Loopback Control OAMPDUs Unsupported OAMPDUs Out: Information OAMPDUs :291 Event Notification OAMPDUs Errored Frame Errored Symbol Loopback Control OAMPDUs Duplicate Event Notification OAMPDUs Table 12 on page 254 lists the show ethernet oam lfm statistics command output Meaning fields.
Page 287: Monitoring Oam Link-Fault Management Configuration For An Interface
Chapter 7: Configuring IEEE 802.3ah OAM Link-Fault Management Table 12: show ethernet oam lfm statistics Output Fields (continued) Field Name Field Description Event Notification OAMPDUs Number of unique Event Notification PDUs received on the interface, when the number of errors equals or exceeds the configured low threshold for a specified time period.
Page 288: Table 13: Show Ethernet Oam Lfm Status Output Fields
JUNOSe 11.1.x Link Layer Configuration Guide Transmit-interval: 1000 ms Loss-threshold: 5 packets Event Action: disable High Threshold Action: disable Remote-loopback: supported Frame-seconds Error Monitor Window: 30 (100 millisecond units) Low threshold: 20 errored frames High threshold: none Remote-loopback: Frames sent: 104437 Bytes sent: 16167885...
Page 289 Chapter 7: Configuring IEEE 802.3ah OAM Link-Fault Management Table 13: show ethernet oam lfm status Output Fields (continued) Field Name Field Description Event Action Action to be performed on an interface when an Information OAM PDU is received from the remote peer by the local OAM entity to signal a fault condition at the remote entity.
Page 290: Monitoring Oam Link-Fault Management Sessions On All Configured Interfaces
JUNOSe 11.1.x Link Layer Configuration Guide Table 13: show ethernet oam lfm status Output Fields (continued) Field Name Field Description Low threshold Lowest value for frame error events in number of frames, which when exceeded causes an Errored Frame Event TLV to be sent to the peer High threshold Highest value for frame error events in number of frames, which...
Page 291: Table 14: Show Ethernet Oam Lfm Summary Output Fields
Chapter 7: Configuring IEEE 802.3ah OAM Link-Fault Management To display Ethernet OAM link-fault management settings for all interfaces on which Action OAM is enabled: host1#show ethernet oam lfm summary FastEthernet4/0 is Up, Administrative status is Up Ethernet OAM (ver 1) Mode: Active, Discovery State: Send any Remote address: 0090.0a38.0208 Flags: Remote-Stable Remote-State-Valid Local-Stable...
Page 292 JUNOSe 11.1.x Link Layer Configuration Guide Table 14: show ethernet oam lfm summary Output Fields (continued) Field Name Field Description Discovery State State of the discovery mechanism: Fault When the discovery process enters the Fault state, the local PDU value is set based on the value of local link status field.
Page 293 Chapter 7: Configuring IEEE 802.3ah OAM Link-Fault Management Table 14: show ethernet oam lfm summary Output Fields (continued) Field Name Field Description Flags Provides information about the physical link; displays one or more of the following values: Remote-Stable Indicates remote OAM client acknowledgment and acceptance of local OAM state information.
Page 294 JUNOSe 11.1.x Link Layer Configuration Guide Configuring 802.3ah OAM Link-Fault Management on page 242 Related Topics show ethernet oam lfm summary Monitoring OAM Link-Fault Management Sessions on All Configured Interfaces...
Page 295: Configuring Point-To-Point Protocol
Chapter 8 Configuring Point-to-Point Protocol This chapter describes how to configure a Point-to-Point Protocol (PPP) interface on E Series routers. This chapter contains the following sections: Overview on page 263 Platform Considerations on page 273 References on page 274 Before You Configure PPP on page 275 Configuration Tasks on page 275 Optional Configuration Tasks on page 278 PPP Accounting Statistics on page 285...
Page 296: Error Frames
JUNOSe 11.1.x Link Layer Configuration Guide The router does not support the following framing features: Numbered mode (RFC 1663) Autodetection of encapsulation Error Frames The router relies on higher-layer protocols to recover from PPP data loss. All unrecognized protocol data units (PDUs) are discarded; however, statistics are maintained for packets dropped.
Page 297: Validation Of Lcp Peer Magic Number
Chapter 8: Configuring Point-to-Point Protocol If they are not successful, and the magic numbers remain the same, the session terminates because of the loopback that is detected. Magic numbers are always accepted. By default, the router always attempts to negotiate a local magic number. The peer can also determine whether to negotiate its magic number the peer magic number.
Page 298: B-Ras Support
JUNOSe 11.1.x Link Layer Configuration Guide To configure the router to ignore the LCP peer magic number mismatch and retain the PPP connection, use the ppp magic-number ignore-mismatch command from Interface Configuration mode or Subinterface Configuration mode. For more information, see “ppp magic-number ignore-mismatch” on page 280. To verify configuration of LCP peer magic number validation on the router, you can use the show ppp interface command.
Page 299: Authentication
Chapter 8: Configuring Point-to-Point Protocol Authentication The router acts as an authenticator. It demands authentication from a remote PPP peer but refuses to authenticate itself. Rate Limiting for PPP Control Packets The router implements rate limiting for PPP control packets to protect the corresponding PPP interface from denial-of-service (DoS) attacks.
Page 300: Eap Types
JUNOSe 11.1.x Link Layer Configuration Guide The JUNOSe software forwards or discards packets received from the backend authentication router and the peer depending on the identifying code contained in the packet. The E Series router forwards: Packets received from the peer with a Response code Packets received from the backend authentication server with a Request, Success, or Failure code The E Series router discards:...
Page 301: Eap Behavior In An L2Tp Environment
Chapter 8: Configuring Point-to-Point Protocol governed by nonconfigurable values for retransmission attempts and interval. The configuration of the RADIUS client determines retransmission values for response packets to the RADIUS server. The retransmission values are as follows: PPP makes five attempts to retransmit an EAP request before the authentication attempt is terminated.
Page 302: Limitations
JUNOSe 11.1.x Link Layer Configuration Guide L2TP on an LNS processes the received Proxy Authen AVPs as described in L2TP Proxy Authenticate Extensions for EAP draft-ietf-l2tpext-proxy-authen-ext-eap-01.txt (December 2006 expiration). Limitations EAP is subject to internal limits. When the E Series router acts as a pass-through between the backend authentication server and the peer, EAP packets traverse the controllers within the router.
Page 303: Remote Peer Scenarios During Negotiation Of Ppp Options
Chapter 8: Configuring Point-to-Point Protocol Performance depends on the number of packets exchanged during the negotiation. When the number of packets exchanged increases that is, when the number of round-trips increases it takes longer to finish the interface negotiation. System resources are locked for a longer duration. As a result it takes longer to bring up all the interfaces.
Page 304: Ipcp Lockout And Local Ip Address Pool Restoration
JUNOSe 11.1.x Link Layer Configuration Guide If B-RAS sends an ACK, it ignores the options and brings up the link The CPE negotiates the prompted options but the option values are not acceptable B-RAS sends another NAK with the prompted options, until max configure-nak is exceeded The CPE negotiates the prompted options but some option values are not acceptable...
Page 305: Platform Considerations
Chapter 8: Configuring Point-to-Point Protocol Configuration modes. This command terminates the invalid subscriber entry and prevents additional IPCP negotiations. When IPv6CP is active and if the IPCP must close, the router does not terminate PPP and Link Control Protocol (LCP) and does not return the address to the pool.
Page 306: References
JUNOSe 11.1.x Link Layer Configuration Guide 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);...
Page 307: Before You Configure Ppp
Chapter 8: Configuring Point-to-Point Protocol Before You Configure PPP Before you configure a PPP interface, configure the interface or tunnel over which PPP traffic will flow. See the following chapters: Configuring Channelized T3 Interfaces in JUNOSe Physical Layer Configuration Guide Configuring T3 and E3 Interfaces in JUNOSe Physical Layer Configuration Guide Configuring Unchannelized OCx/STMx Interfaces in JUNOSe Physical Layer Configuration Guide...
Page 308 JUNOSe 11.1.x Link Layer Configuration Guide Use the no version to disable PPP on an interface. See encapsulation ppp. interface atm Use to specify a previously configured ATM interface on which you want to configure PPP. To specify an ATM interface for ERX7xx models, ERX14xx models, and ERX310 router, use the slot/port.[subinterface ] format.
Page 309 Chapter 8: Configuring Point-to-Point Protocol To specify a POS interface for E120 and E320 routers, use the slot/adapter/port 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).
Page 310: Optional Configuration Tasks
JUNOSe 11.1.x Link Layer Configuration Guide Optional Configuration Tasks You can perform the following optional PPP configuration tasks: Add a text description or alias to a PPP interface. Configure the IPCP netmask option (option 0x90). Specify the keepalive timeout value. Disable magic numbers.
Page 311 Chapter 8: Configuring Point-to-Point Protocol Use to specify the IPCP netmask option (option 0x90) for each PPP interface. By default, the IPCP netmask option is disabled on the interface. The IPCP netmask option is a nonstandard option that enables a peer to request the netmask associated with the assigned IP address.
Page 312 JUNOSe 11.1.x Link Layer Configuration Guide host1(config-if)#ppp keepalive 50 Use the no version to disable keepalive. See ppp keepalive. ppp magic-number disable Use to disable negotiation of the local magic number. Issuing this command prevents the router from detecting loopback configurations. Example host1(config-if)#ppp magic-number disable Use the no version to restore negotiation of the local magic number.
Page 313 Chapter 8: Configuring Point-to-Point Protocol default value (30) if you omit the optional value for maximum renegotiation attempts. When both IPv4 interface columns and IPv6 interface columns are configured over a PPP link-layer interface, the router terminates the PPP session only when the PPP client exceeds the configured maximum number of renegotiation attempts for both the IPv4 interface and the IPv6 interface.
Page 314 JUNOSe 11.1.x Link Layer Configuration Guide Use to force a static or dynamic PPP interface into passive mode before LCP negotiation begins, for a period of one second. This delay enables slow clients to start up and initiate the LCP negotiation. Example host1(config-if)#ppp passive-mode Use the no version to disable passive mode.
Page 315: Configuring Ppp Authentication
Chapter 8: Configuring Point-to-Point Protocol All PPP sessions are enabled by default. Example host1(config-if)#ppp shutdown Use the no version to restart a disabled session. See ppp shutdown. Configuring PPP Authentication Perform the following optional tasks to configure PPP authentication: Specify one or more PPP authentication types, and select an authentication virtual router context.
Page 316 JUNOSe 11.1.x Link Layer Configuration Guide You can specify one or more authentication protocols in order of preference. If the peer router refuses the first choice, then the local router requests the next authentication protocol, if specified. If the peer refuses that protocol, then the local router requests the third protocol, if specified.
Page 317: Ppp Accounting Statistics
Chapter 8: Configuring Point-to-Point Protocol Use to modify the length of the CHAP challenge by specifying the allowable minimum length and maximum length. Specify the minimum and maximum lengths in bytes in the range 8–63. CAUTION: Do not decrease the range. Increasing the range is acceptable, provided that you do not lower the minimum to do so.
Page 318: Monitoring Ppp Interfaces
JUNOSe 11.1.x Link Layer Configuration Guide Attribute Number Attribute Name Acct-Input-Packets Acct-Output-Packets PPP session termination can be initiated through a number of mechanisms: PPP shutdown at the client or router interface, subscriber logout at the router (by means of the logout subscriber command), lower layer down events, and silent client termination.
Page 319 Chapter 8: Configuring Point-to-Point Protocol You can use the output filtering feature of the show command to include or exclude lines of output based on a text string that you specify. Refer to the show Commands in JUNOSe System Basics Configuration Guide, for details. NOTE: The E120 and E320 routers output for monitor and show commands is identical to output from other E Series routers, except that the E120 and E320 routers output also includes information about the adapter identifier in the interface specifier...
Page 320 JUNOSe 11.1.x Link Layer Configuration Guide Interface administrative status Indicates whether the interface is administratively enabled (open), meaning that the no ppp shutdown command is operational; or administratively disabled (closed), which means that the ppp shutdown command is operational Configured network protocol Indicates the network protocol configured on the interface Baseline status Indicates whether a statistics baseline is set Interface statistics...
Page 321 Chapter 8: Configuring Point-to-Point Protocol max-negotiations Maximum number of renegotiation attempts that the router accepts before terminating a PPP session ipcp prompt-option dns Prompts the CPE (Customer Premises Equipment) to negotiate the IPCP primary and secondary DNS options that are locally available with the broadband remote access server (enabled or disabled) IPV6CP protocol configuration configured IPv6CP is configured on this interface (true or false)
Page 322 JUNOSe 11.1.x Link Layer Configuration Guide operational-status OSINLCP operational status (up, down, not present, or not present no resources) terminate-reason Reason for termination of OSINLCP service OSINLCP negotiated options npdu-alignment Negotiated NPDU alignment for the local and remote (peer) side of the link NOTE: The command displays a value of “none”...
Page 323 Chapter 8: Configuring Point-to-Point Protocol when the peer has not negotiated an LCP magic number: ignore (ignore the peer magic number mismatch and retain the PPP connection), or reject (router terminates the PPP connection if it detects a peer magic number mismatch) keepalive-timer Rate of LCP echo requests restart-timer Retry frequency during LCP, IPCP, OSINLCP, and MPLS...
Page 324 JUNOSe 11.1.x Link Layer Configuration Guide LCP protocol statistics Shows the following statistics for the life of the interface (since system boot or interface creation, whichever is later) in-keepalive-requests Number of received keepalive requests (LCP Echo Requests) out-keepalive-requests Number of transmitted keepalive requests in-keepalive-replies Number of received keepalive replies out-keepalive-replies Number of transmitted keepalive replies keepalive-failures Number of keepalive failures reported on the interface...
Page 325 Chapter 8: Configuring Point-to-Point Protocol peer-secondary-dns-address IP address to be used in negotiation of the peer secondary DNS address peer-primary-wins-address IP address to be used in negotiation of the peer primary WINS address peer-secondary-wins-address IP address to be used in negotiation of the peer secondary WINS address NOTE: The command displays the authentication status as “none”...
Page 326 JUNOSe 11.1.x Link Layer Configuration Guide EAP protocol configuration request-retry Maximum number of authentication requests retried before returning a deny request-timeout Maximum time, in seconds, to wait for an authentication request packet If the operational status is down for a specific interface, one of the following termination reasons might appear in parentheses: administrative disable Interface has been administratively disabled, which means that the ppp shutdown command is in effect.
Page 327 Chapter 8: Configuring Point-to-Point Protocol was no response from the peer, or the peer refused to negotiate. This applies to an interface, IPCP, IPv6CP, OSINLCP, and MPLS. peer requested termination Remote peer requested termination of the connection, which means that a terminate request was received while the session was in an open state.
Page 328 JUNOSe 11.1.x Link Layer Configuration Guide max-failure passive-mode disabled LCP protocol status link-status network LCP negotiated options local peer max-receive-unit 1492 1492 authentication none chap magic-number 0x3e51ca08 0x740bbf81 accm none none none none acfc none none LCP protocol statistics in-keepalive-requests out-keepalive-requests in-keepalive-replies out-keepalive-replies...
Page 329 Chapter 8: Configuring Point-to-Point Protocol host1#show ppp interface fastEthernet 12/0.1.1 full PPP interface FastEthernet 12/0.1.1 is lowerDown Interface administrative status is open Configured network protocol is IPV6CP IPCP protocol configuration configured false administrative-status open ip-address 0.0.0.0 dns-precedence local wins-precedence local ipcp-netmask-option disabled ipcp-lockout-option...
Page 330 JUNOSe 11.1.x Link Layer Configuration Guide aaa-profile Authentication status grant false terminate-reason lower layer down PAP protocol configuration request-timeout 20 seconds CHAP protocol configuration name challenge-retry challenge-timeout 4 seconds minimum-challenge-length maximum-challenge-length minimum-rechallenge-timeout 0 seconds maximum-rechallenge-timeout 0 seconds Example 3 Displays a termination reason (administrative disable) when the operational status of the interface is down host1#show ppp interface PPP interface pos 0/1:1 is lowerDown...
Page 331 Chapter 8: Configuring Point-to-Point Protocol closed Interface or protocol is administratively disabled Operational status (Interface) Indicates the operational state of the PPP interface up Interface is operational down Interface is not operational because of a problem in the PPP layer lowerDown Interface is not operational because a lower layer in the protocol stack is down notPresent Interface is not operational because the hardware is...
Page 332: Troubleshooting
JUNOSe 11.1.x Link Layer Configuration Guide PPP Multilink Status Configuration status configured notConfigured Link Interface 8000 Network Interface 2000 2000 Ipv6 2000 2000 Mpls 2000 Administrative status open closed Link Interface 8000 Network Interface 2000 2000 Ipv6 2000 2000 Mpls 2000 Operational status down...
Page 333 Chapter 8: Configuring Point-to-Point Protocol time: 0.01, rx lcp confReq, id = 156, length = 18, mru = 32759, magicNumber = 0x2d8eac91, pfc, acfc DEBUG 01/01/1970 00:16:58 pppPacket (1000001,*): interface: 0/0:1/11/0:1, time: 0.01, tx lcp confAck, id = 156, length = 18, mru = 32759, magicNumber = 0x2d8eac91, pfc, acfc Use the no version to return the severity changes to their default setting or to the systemwide setting.
Page 334 JUNOSe 11.1.x Link Layer Configuration Guide Troubleshooting...
Page 335: Configuring Multilink Ppp
Chapter 9 Configuring Multilink PPP This chapter describes how to configure a Multilink Point-to-Point Protocol (PPP) interface on E Series routers. This chapter contains the following sections: Overview on page 303 Platform Considerations on page 306 References on page 307 Supported MLPPP Features on page 308 Unsupported MLPPP Features on page 312 Before You Configure Static MLPPP on page 312...
Page 336: Application
JUNOSe 11.1.x Link Layer Configuration Guide Application Some users need more bandwidth than a T1 or an E1 channel can provide, but cannot afford the expense or do not need the bandwidth of T3 or E3. Equal-cost multipath (ECMP) is one way to achieve the desired bandwidth. MLPPP is commonly used as an alternative to ECMP to deliver NxT1 service.
Page 337: Mlppp Link Selection
Chapter 9: Configuring Multilink PPP the other end that the router supports MLPPP. When you enable multilink on your router, the router includes the MRRU option in LCP negotiation with the value set to the maximum received unit (MRU) value for PPP. If the remote system rejects this option, the local system determines that the remote system does not support multilink PPP and it terminates the link without negotiation.
Page 338: Platform Considerations
JUNOSe 11.1.x Link Layer Configuration Guide To ensure that the E Series router maintains the proper packet order when transmitting non-best-effort traffic, you can use the ppp hash-link-selection command to enable use of a hash-based algorithm to select the link on which the router transmits high-priority packets on an MLPPP interface.
Page 339: Module Requirements
Chapter 9: Configuring Multilink PPP ERX705 router ERX310 router Module Requirements For information about the modules that support MLPPP interfaces on ERX14xx models, ERX7xx models, and the ERX310 router: See ERX Module Guide, Table 1, Module Combinations for detailed module specifications.
Page 340: Supported Mlppp Features
JUNOSe 11.1.x Link Layer Configuration Guide RFC 1661 The Point-to-Point Protocol (PPP) (July 1994) RFC 1990 The PPP Multilink Protocol (MP) (August 1996) RFC 2233 The Interfaces Group MIB using SMIv2 (November 1997) Supported MLPPP Features The router currently supports both the static configuration of the links participating in a multilink bundle and the dynamic creation of MLPPP bundles over L2TP (only on the LNS) when the LNS detects multilink LCP option negotiation in LCP proxy data.
Page 341 Chapter 9: Configuring Multilink PPP For information about multiclass MLPPP, see “Configuring Multiclass Multilink PPP” on page 349. You can configure bundles as follows: On a COCX-F3 line module and its corresponding I/O modules, you can configure: Up to 8 member links from different ports in the same bundle, with the following restriction for MLPPP reassembly: For a COCX-F3 line module with either a 12-port E3-12 FRAME I/O module or a 12-port CT3/T3 12 I/O module, the restriction is based on...
Page 342 JUNOSe 11.1.x Link Layer Configuration Guide When MLPPP reassembly is disabled, this restriction is not in effect; for example, member links can span paths in different bundles. Any combination of bundles that does not exceed the 336 available T1 channels (for example, 336 single-link T1 bundles, 42 eight-link bundles, or 41 eight-link bundles and 8 single-link bundles) Any combination of bundles that does not exceed the 252 available E1 channels (for example, 252 single-link T1 bundles, 34 eight-link bundles, or...
Page 343 Chapter 9: Configuring Multilink PPP MLPPP bundles with one or more links per bundle for dynamic MLPPP-over-PPPoE-over-Ethernet configurations. MLPPP bundles with only one link per bundle when configuring static MLPPP-over-PPPoE-over-Ethernet. When you create multilink bundles in a static MLPPP-over-PPPoE-over-Ethernet configuration, PPPoE is unable to direct the PPPoE Active Discovery Initiation (PADI) packets received from the MLPPP bundle links on the client to the appropriate (matching) links in the MLPPP bundle on the server.
Page 344: Unsupported Mlppp Features
JUNOSe 11.1.x Link Layer Configuration Guide Unsupported MLPPP Features The router does not support the following MLPPP features: Short sequence numbers Resequencing out-of-order packets in the absence of fragmentation Given the location in the network where the router resides, the NxT1 links to a customer site represent one of many places across the IP network where packets might be received out of order.
Page 345 Chapter 9: Configuring Multilink PPP To configure static MLPPP: Create the member links to be aggregated into a multilink bundle. a. From Global Configuration mode, specify the individual interface on which you want to configure MLPPP. host1(config)#interface serial 2/0:1/1 b. Specify MLPPP as the encapsulation method on the interface. host1(config-if)#encapsulation mlppp (Optional) Specify the keepalive timeout value for the member link interface.
Page 346: Configuration Example
JUNOSe 11.1.x Link Layer Configuration Guide Configuration Example The following commands configure three T1 lines and aggregate them into a multilink bundle named group1. host1(config)#interface serial 2/0:1/1 host1(config-if)#encapsulation mlppp host1(config-if)#exit host1(config)#interface serial 2/0:2/1 host1(config-if)#encapsulation mlppp host1(config-if)#exit host1(config)#interface serial 2/0:3/1 host1(config-if)#encapsulation mlppp host1(config-if)#ppp keepalive 50 host1(config-if)#exit host1(config)#interface mlppp group1...
Page 347: Configuring Authentication
Chapter 9: Configuring Multilink PPP command, negotiation of the local magic number for this link and any member links subsequently added to the bundle is not disabled. Configuring Authentication Perform the following optional tasks to configure authentication on interfaces with MLPPP encapsulation or MLPPP bundles.
Page 348 JUNOSe 11.1.x Link Layer Configuration Guide The router requests the use of PAP as the authentication protocol (because it appears first in the command line). If the peer refuses to use PAP, the router requests the CHAP protocol. If the peer refuses to negotiate authentication, the router terminates the PPP session.
Page 349: Configuring Other Ppp Attributes
Chapter 9: Configuring Multilink PPP Configuring Other PPP Attributes The available ppp command options are the same for interfaces whether they are configured with PPP or MLPPP. encapsulation mlppp Use to configure MLPPP as the encapsulation method on an individual interface. Use this command only within the context of an individual interface.
Page 350 JUNOSe 11.1.x Link Layer Configuration Guide Use to enable use of a hash-based algorithm to select the link on which the router transmits non-best-effort (high-priority) packets, such as voice or video, on an MLPPP interface. Hash-based MLPPP link selection is available only for non-best-effort traffic. For best-effort traffic, the router uses a round-robin algorithm for link selection.
Page 351 Chapter 9: Configuring Multilink PPP ppp ipcp lockout Use to terminate invalid IPv4 subscribers and prevent additional IPCP negotiations. When Internet Protocol version 6 Control Protocol (IPv6CP) is active, this command enables unused IPv4 addresses, which are allocated for the IPv6 subscribers, to be available for the IPCP services for an internally defined time interval (10 seconds).
Page 352 JUNOSe 11.1.x Link Layer Configuration Guide NOTE: This command is equivalent to the log severity debug pppPacket and log severity debug pppStateMachine commands. Use the no version to disable packet or state machine logging. See ppp log. ppp magic-number disable Use to disable negotiation of the local magic number.
Page 353 Chapter 9: Configuring Multilink PPP When a PPP client exceeds the configured maximum number of renegotation attempts, the router sends a termination request to end the PPP session. When the PPP session is terminated and LCP goes into a stopped (closed) state, static PPP or MLPPP interfaces go into passive mode and wait for the other side of the connection to start the LCP negotiation process.
Page 354 JUNOSe 11.1.x Link Layer Configuration Guide If you issue the command in the context of an encapsulated MLPPP interface, it affects only that interface. If you issue the command in the context of an MLPPP bundle, it affects all member links within that bundle. Example host1(config-if)#ppp mru 576 Use the no version to restore the default value, which causes PPP to use the...
Page 355: Configuring Dynamic Mlppp
Chapter 9: Configuring Multilink PPP Use to terminate an MLPPP session. If you use the ip or osi keyword, disables the Internet Protocol Control Protocol (IPCP) or OSI Network Layer Control Protocol (OSINLCP) service for the MLPPP network interface (MLPPP bundle). Issue only in the context of a network interface.
Page 356: Configuring Mlppp Fragmentation And Reassembly
JUNOSe 11.1.x Link Layer Configuration Guide Specify an IP loopback interface with which dynamic IP interfaces created using this profile will be associated. host1(config-profile)#ip unnumbered loopback 0 (Optional) Set other desired PPP characteristics by using the ppp commands described in “Configuring Authentication” on page 315 and “Configuring Other PPP Attributes”...
Page 357: Application
Chapter 9: Configuring Multilink PPP Application You can use MLPPP fragmentation and reassembly to reduce transmission latency. You can also use the feature to implement a packet-prioritization scheme that allows smaller, delay-sensitive packets (such as high-priority voice packets) to be interleaved with or race ahead of larger, delay-insensitive packets (such as low-priority data packets) when they are transmitted in the network.
Page 358: Bundle Validation And Configuration Guidelines
JUNOSe 11.1.x Link Layer Configuration Guide When you use the ppp fragmentation command to enable fragmentation on a link, you can optionally specify the maximum fragment size to be used on the link interface. When you use the ppp reassembly command to enable reassembly on a link, you can optionally specify the administrative multilink maximum received reconstructed unit (MRRU) value for the link.
Page 359: Bundle Validation Failure
Chapter 9: Configuring Multilink PPP When reassembly is enabled, member links belonging to the same bundle can have different local MRU values. When reassembly is disabled, member links belonging to the same bundle must negotiate the same local MRU value. Bundle Validation Failure If an MLPPP link interface fails bundle validation because one or more of the preceding configuration guidelines are not met, the router’s actions differ depending on whether...
Page 360: Static Mlppp Over Atm 1483 Example
JUNOSe 11.1.x Link Layer Configuration Guide NOTE: You can specify the administrative MRRU value for a link only when you use the ppp reassembly command to enable reassembly on that link. You cannot specify the administrative MRRU for a link when reassembly is disabled. Exit Interface Configuration mode.
Page 361: Configuring Fragmentation And Reassembly For Dynamic Mlppp
Chapter 9: Configuring Multilink PPP host1(config-if)#ip address 10.10.200.1 255.255.255.0 Configuring Fragmentation and Reassembly for Dynamic MLPPP To configure fragmentation and reassembly for dynamic MLPPP, you must create a profile that includes commands to define the link and bundle attributes, just as you do for a static MLPPP configuration.
Page 362: Dynamic Mlppp Over Pppoe Example
JUNOSe 11.1.x Link Layer Configuration Guide (Optional) Specify an IP loopback interface with which dynamic IP interfaces created with this profile will be associated. host1(config-profile)#ip unnumbered loopback 0 (Optional) Set other PPP characteristics as needed by using the ppp commands described in “Configuring Multilink PPP”...
Page 363 Chapter 9: Configuring Multilink PPP host1(config-l2tp-dest-profile-host)#enable proxy authenticate host1(config-l2tp-dest-profile-host)#tunnel password welcome host1(config-l2tp-dest-profile-host)#profile l2tp-profile encapsulation mlppp Use to configure MLPPP as the encapsulation method on an individual interface. Use this command only within the context of an individual interface. Issuing this command creates an MLPPP link interface, which can be configured as a member of an MLPPP bundle.
Page 364 JUNOSe 11.1.x Link Layer Configuration Guide Do not configure both MLPPP fragmentation and IP fragmentation of L2TP packets (with the ip mtu command) on the same interface. Instead, you must choose only one of the fragmentation configurations by setting it to the necessary value and set the other fragmentation configuration to the maximum allowable value.
Page 365: Configuring Fragmentation And Reassembly For Mlppp Bundles
Chapter 9: Configuring Multilink PPP Use the no version to remove a profile. See profile. Configuring Fragmentation and Reassembly for MLPPP Bundles If you issue the ppp fragmentation command or the ppp reassembly command in the context of an MLPPP bundle, the command affects all the current member links in the bundle.
Page 366 JUNOSe 11.1.x Link Layer Configuration Guide You can use the output filtering feature of the show command to include or exclude lines of output based on a text string you specify. For details, see section show Commands in JUNOSe System Basics Configuration Guide. NOTE: The E120 and E320 routers output for monitor and show commands is identical to output from other E Series routers, except that the E120 and E320 routers output also includes information about the adapter identifier in the interface specifier...
Page 367 Chapter 9: Configuring Multilink PPP Interface statistics packets octets errors discards PPP interface serial 2/1:4/1 is up No baseline has been set Interface statistics packets octets errors discards PPP interface serial 2/1:5/1 is up No baseline has been set Interface statistics packets octets errors...
Page 368 JUNOSe 11.1.x Link Layer Configuration Guide octets errors discards 2 mlppp interfaces found The following command displays PPP interface (including MLPPP interface) statistics Sample Display with with baselining: Baseline host1#show ppp interface statistics delta PPP interface serial 2/0:4/1 is up Time since last baseline 00:00:35 Interface statistics packets...
Page 369 Chapter 9: Configuring Multilink PPP PPP interface mlppp group2 is up PPP multilink member-interface serial 2/1:1/1 is up Time since last baseline 00:00:23 Interface statistics packets octets errors discards PPP multilink member-interface serial 2/1:2/1 is up Time since last baseline 00:00:25 Interface statistics packets octets...
Page 370 JUNOSe 11.1.x Link Layer Configuration Guide Link interface reassembly Indicates whether MLPPP reassembly is enabled or disabled on the link interface Link interface administrative MRRU Administrative MRRU value, in octets, currently in use on the link interface Baseline status Indicates whether a statistics baseline has been set Interface statistics: packets Number of packets received (in) and sent (out) on the interface octets Number of octets received (in) and sent (out) on the interface...
Page 371 Chapter 9: Configuring Multilink PPP keepalive-timer Rate of LCP echo requests, in seconds restart-timer Retry frequency during LCP, IPCP, and OSINLCP negotiations, in seconds max-terminate Maximum number of terminate requests max-configure Maximum number of configure requests max-failure Maximum number of configure NAKs LCP protocol status: link-status Indicates the overall status of LCP negotiations, including the following states: initial (idle), starting (ready to negotiate),...
Page 372 JUNOSe 11.1.x Link Layer Configuration Guide LCP protocol statistics: in-keepalive-requests Number of received keepalive requests (LCP Echo Request) for the life of the interface (since either system boot or interface creation, whichever is later) out-keepalive-requests Number of transmitted keepalive requests for the life of interface in-keepalive-replies Number of received keepalive replies for the life of the interface...
Page 373 Chapter 9: Configuring Multilink PPP secondary-dns-address Negotiated secondary DNS address for the local and remote (peer) side of the link primary-wins-address Negotiated primary WINS address for the local and remote (peer) side of the link secondary-wins-address Negotiated secondary WINS address for the local and remote (peer) side of the link NOTE: The command displays a value of “none”...
Page 374 JUNOSe 11.1.x Link Layer Configuration Guide host1#show ppp interface mlppp links PPP multilink interface serial 2/0:1/1 is up PPP multilink interface serial 2/0:2/1 is up PPP multilink interface serial 2/0:3/1 is up PPP multilink interface serial 2/1:1/1 is up PPP multilink interface serial 2/1:2/1 is up PPP multilink interface serial 2/1:3/1 is up Example 4 Displays configuration information about MLPPP member links configured in bundle group1...
Page 375 Chapter 9: Configuring Multilink PPP PPP multilink member-interface ATM 10/0.12 is down (lower layer down) No baseline has been set Interface statistics packets octets errors discards PPP multilink member-interface ATM 10/0.13 is down (lower layer down) No baseline has been set Interface statistics packets octets...
Page 376 JUNOSe 11.1.x Link Layer Configuration Guide authentication none magic-number enabled magic-number-mismatch ignore keepalive-timer 30 seconds restart-timer 3 seconds max-terminate max-configure max-failure LCP protocol status link-status network LCP negotiated options local peer max-receive-unit 1590 1590 max-receive-reconstructed-unit 1590 1590 authentication none none magic-number 0x6c079eb0 0x2c5a5798...
Page 377 Chapter 9: Configuring Multilink PPP peer endpoint discriminator 0x31393933313030303800001b000002 LCP protocol statistics in-keepalive-requests out-keepalive-requests in-keepalive-replies out-keepalive-replies keepalive-failures PPP multilink member-interface serial 2/0:3/1 is up Link interface administrative status is open No baseline has been set Interface statistics packets octets 1568 2068 errors discards...
Page 378 JUNOSe 11.1.x Link Layer Configuration Guide IPCP protocol status operational-status IPCP negotiated options local peer ip-address 192.168.1.1 100.100.100.17 ip-address-mask none none primary-dns-address none none secondary-dns-address none none primary-wins-address none none secondary-wins-address none none IPV6CP protocol configuration configured true PPP multilink member-interface ATM 0/0.10 is up Link interface administrative status is open Link interface fragmentation is enabled Link interface fragment size is (use MTU)
Page 379 Chapter 9: Configuring Multilink PPP Operational status (Interface) Indicates the operational state of the PPP interface up Interface is operational down Interface is not operational because of a problem in the PPP layer lowerDown Interface is not operational because a lower layer in the protocol stack is down notPresent Interface is not operational because the hardware is unavailable...
Page 380 JUNOSe 11.1.x Link Layer Configuration Guide Link Interface 8000 Network Interface 2000 2000 Ipv6 2000 2000 Mpls 2000 Administrative status open closed Link Interface 8000 Network Interface 2000 2000 Ipv6 2000 2000 Mpls 2000 Operational status down notPresent noResources Link Interface 8000 Network Interface 2000...
Page 381: Configuring Multiclass Multilink Ppp
Chapter 10 Configuring Multiclass Multilink PPP Multiclass MLPPP Overview on page 349 Multiclass MLPPP Traffic Classes Overview on page 350 Multiclass MLPPP LCP Extensions Overview on page 351 Multiclass MLPPP Platform Considerations on page 351 Multiclass MLPPP References on page 352 Configuring Multiclass MLPPP on page 352 Enabling Multiclass MLPPP on page 353 Configuring Traffic Classes on Multiclass MLPPP Interfaces on page 354...
Page 382: Multiclass Mlppp Configuration Guidelines
JUNOSe 11.1.x Link Layer Configuration Guide On MLPPP bundles that consist of physical links of different types, MLPPP does not guarantee the receipt of high-priority data packets in sequence. Multiclass MLPPP enables you to fragment data packets of different priorities into multiple multilink classes.
Page 383: Multiclass Mlppp Lcp Extensions Overview
Chapter 10: Configuring Multiclass Multilink PPP traffic-class-to-multilink-class mapping is transmitted without a multiclass MLPPP header. Configuring Traffic Classes on Multiclass MLPPP Interfaces on page 354 Related Topics Multiclass MLPPP Overview on page 349 Traffic Class and Traffic-Class Groups Overview Multiclass MLPPP LCP Extensions Overview Link Control Protocol (LCP) establishes an MLPPP link by negotiating LCP options with the MLPPP peer at the receiving end of a proposed connection.
Page 384: Module Requirements
JUNOSe 11.1.x Link Layer Configuration Guide E120 router E320 router Module Requirements For information about modules that support multiclass MLPPP on the E120 and E320 Broadband Services Routers: See E120 and E320 Module Guide, Table 1, Module and IOAs for detailed module specifications.
Page 385: Enabling Multiclass Mlppp
Chapter 10: Configuring Multiclass Multilink PPP can configure multiclass MLPPP on a static MLPPP interface or in a dynamic profile for a dynamic MLPPP interface. To configure multiclass MLPPP: Enable multiclass MLPPP. See “Enabling Multiclass MLPPP” on page 353. Configure traffic classes on the multiclass MLPPP interface. See “Configuring Traffic Classes on Multiclass MLPPP Interfaces”...
Page 386: Configuring Traffic Classes On Multiclass Mlppp Interfaces
JUNOSe 11.1.x Link Layer Configuration Guide host1(config)#interface gigabitEthernet 3/0/0 Specify PPPoE as the encapsulation method on the interface. host1(config-if)#encapsulation pppoe Create a PPPoE subinterface. host1(config)#interface gigabitEthernet 3/0/0.10 Specify MLPPP as the encapsulation method on the subinterface. host1(config-if)#encapsulation mlppp Enable multiclass MLPPP and specify the number of miltilink classes to create. host1(config-if)#ppp multilink multiclass multilink-classes 8 Configuring a Dynamic Interface from a Profile in JUNOSe Link Layer Configuration Related Topics...
Page 387: Configuring Fragmentation On Multiclass Mlppp Interfaces
Chapter 10: Configuring Multiclass Multilink PPP Configuring Fragmentation on Multiclass MLPPP Interfaces You can configure fragmentation on a multiclass MLPPP interface with the same fragment size as that of the MLPPP interface. Before you configure fragmentation on the multiclass MLPPP interface: Ensure that fragmentation is enabled on the MLPPP interface.
Page 388: Example: Configuring Multiclass Mlppp On A Dynamic Interface
JUNOSe 11.1.x Link Layer Configuration Guide To configure reassembly on multilink classes in a dynamic profile: host1(config-profile)#ppp multilink multiclass reassembly best-effort voice otherData video To configure reassembly on multilink classes in a static MLPPP interface: host1(config-if)#ppp multilink multiclass reassembly best-effort voice otherData video The order of the QoS traffic classes does not affect the execution of the command.
Page 389: Example: Configuring Multiclass Mlppp On A Static Interface
Chapter 10: Configuring Multiclass Multilink PPP For more information about configuring a dynamic profile for multiclass MLPPP, see Configuring a Profile in JUNOSe Link Layer Configuration Guide, Chapter 17, Configuring Dynamic Interfaces. Configure fragmentation and reassembly on the multiclass MLPPP interface. host1(config-profile)#ppp multilink multiclass fragmentation best-effort voice low-loss low-latency host1(config-profile)#ppp multilink multiclass reassembly best-effort voice...
Page 390: Monitoring Multiclass Mlppp
JUNOSe 11.1.x Link Layer Configuration Guide Configuring Multiclass MLPPP on page 352 Related Topics Monitoring Multiclass MLPPP Display information about the status and configuration of multilink classes on an Purpose MLPPP Interface. To display configuration information about multiclass MLPPP member links configured Action in the specified MLPPP bundle: host1#show ppp interface mlppp bundle1 config...
Page 391: Table 17: Show Ppp Interface Mlppp Output Fields
Chapter 10: Configuring Multiclass Multilink PPP 0 fragments, 0x8 last sent sequence number Transmit Class 1: 0 fragments, 0x0 last sent sequence number 1 mlppp interfaces found To display complete configuration, statistics, and status information of multiclass MLPPP member links configured in the specified MLPPP bundle: host1#show ppp interface mlppp bundle1 full Bundle name: bundle1 MLPPP interface gigabitEthernet 3/0.1.1 is up...
Page 392 JUNOSe 11.1.x Link Layer Configuration Guide Table 17: show ppp interface mlppp Output Fields (continued) Field Name Field Description PPP multilink multiclass Configuration of reassembly of the multiclass MLPPP reassembly interface: enabled or disabled. If reassembly is enabled then it also lists the QoS traffic classes on which reassembly is enabled.
Page 393 Chapter 10: Configuring Multiclass Multilink PPP Table 17: show ppp interface mlppp Output Fields (continued) Field Name Field Description LCP negotiated options Negotiated LCP options for the local and peer systems: max-receive-unit Negotiated maximum receive unit, in octets, for the local and remote (peer) side of the link max-receive-reconstructed-unit Negotiated maximum receive reconstructed unit, in octets,...
Page 394 JUNOSe 11.1.x Link Layer Configuration Guide Monitoring Multiclass MLPPP...
Page 395: Configuring Packet Over Sonet
Chapter 11 Configuring Packet over SONET Use the procedures described in this chapter to configure packet over SONET (POS) on E Series routers. This chapter contains the following sections: Overview on page 363 Platform Considerations on page 364 References on page 365 Before You Configure POS on page 366 Configuration Tasks on page 366 Monitoring POS on page 371...
Page 396: Sonet/Sdh
JUNOSe 11.1.x Link Layer Configuration Guide POS framing Cyclic redundancy check (CRC) checking Loopback configuration SONET/SDH SONET is an ANSI standard for transmitting bits over fiber-optic cable. SDH is the international standard defined by the International Telecommunication Union (ITU). SONET/SDH is the physical infrastructure of choice for carrier ATM networks operating at speeds above 50 Mbps.
Page 397: Module Requirements
Chapter 11: Configuring Packet over SONET ERX705 router ERX310 router Module Requirements For information about the modules that support POS interfaces on ERX14xx models, ERX7xx models, and the ERX310 router: See ERX Module Guide, Table 1, Module Combinations for detailed module specifications.
Page 398: Before You Configure Pos
JUNOSe 11.1.x Link Layer Configuration Guide RFC 2615 PPP over SONET/SDH (June 1999 RFC 2427 Multiprotocol Interconnect over Frame Relay (September 1998) Before You Configure POS Before you configure a POS interface, verify that you have correctly installed the required module. For information about installing modules in ERX7xx models, ERX14xx models, and ERX310 router, see ERX Hardware Guide, Chapter 4, Installing Modules.
Page 399 Chapter 11: Configuring Packet over SONET (Optional) Set the MRU size. host1(config-if)#mru 1000 (Optional) Set the MTU size. host1(config-if)#mtu 1000 (Optional) Set the type of framing. host1(config-if)#pos framing sdh Disable payload scrambling. host1(config-if)#no pos scramble-atm (Optional) Disable an interface. host1(config-if)#shutdown clock source Use to set the clock source.
Page 400 JUNOSe 11.1.x Link Layer Configuration Guide Use to specify Frame Relay as the encapsulation method for the interface. The router uses IETF format (RFC 2427 encapsulation). Example host1(config-if)#encapsulation frame-relay ietf Use the no version to remove the Frame Relay configuration from an interface. See encapsulation frame-relay ietf encapsulation ppp Use to specify PPP as the encapsulation method for the interface.
Page 401 Chapter 11: Configuring Packet over SONET Use the no version to remove the POS interface. See interface pos. load-interval Use to set the time interval at which the router calculates bit and packet rate counters. 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 restore the default value, 300.
Page 402 JUNOSe 11.1.x Link Layer Configuration Guide Use theno version to restore the default value, 4470. See mtu. pos description Use to assign a text description or an alias to a POS HDLC interface. You can use this command to help you identify the interface and keep track of interface connections.
Page 403: Monitoring Pos
Chapter 11: Configuring Packet over SONET host1(config-if)#shutdown Use the no version to restart a disabled interface. See shutdown. Monitoring POS Use the show interfaces pos command to display information about the POS interface. You can set a statistics baseline for POS interfaces using the baseline interface pos command.
Page 404 JUNOSe 11.1.x Link Layer Configuration Guide 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).
Page 405 Chapter 11: Configuring Packet over SONET Packets received Number of incoming packets received on this interface Bytes received Number of incoming bytes received on this interface Errored packets received Number of incoming errors received on this interface Packets sent Number of outgoing packets transmitted on this interface Bytes sent Number of outgoing bytes transmitted on this interface Errored packets sent Number of outgoing errors on this interface Example...
Page 406 JUNOSe 11.1.x Link Layer Configuration Guide Monitoring POS...
Page 407: Configuring Point-To-Point Protocol Over Ethernet
Chapter 12 Configuring Point-to-Point Protocol over Ethernet This chapter describes how to configure the Point-to-Point Protocol (PPP) over Ethernet interfaces on E Series routers. This chapter contains the following sections: Overview on page 375 Platform Considerations on page 384 References on page 386 Before You Configure PPPoE on page 386 Configuring PPPoE over ATM on page 386 Configuring PPPoE for Ethernet Modules on page 393...
Page 408: Pppoe Stages
JUNOSe 11.1.x Link Layer Configuration Guide Figure 37: PPPoE over ATM The router handles the server part of PPPoE session management and never initiates a setup of a PPPoE session. The router only responds to session requests that are sent to it by the remote PPP client. After the sessions are set up, the router demultiplexes the sessions based on session identifiers assigned to a specific connection.
Page 409: Session
Chapter 12: Configuring Point-to-Point Protocol over Ethernet Session When Discovery is successfully completed, both the host and the selected remote AC have the information they need to build their point-to-point connection over Ethernet. The only parameter that you can configure is the number of PPPoE sessions. NOTE: The router supports dynamic PPPoE interfaces.
Page 410: Features
JUNOSe 11.1.x Link Layer Configuration Guide action for the unknown service name tag is drop. If both terminate and drop are configured for services in the table, all unknown service name tags are dropped by default. Features PPPoE service name tables enable an AC, such as an E Series router, to support multiple service name tags in addition to the empty service name tag and the unknown service name tag.
Page 411: Enabling The Service Name Table For Use
Chapter 12: Configuring Point-to-Point Protocol over Ethernet Table 19: Sample PPPoE Service Name Table (continued) Service Name Action “myQOSClass2” Drop “ ” Drop (empty-service-name) unknown-service-name Drop NOTE: You can associate the drop action with a maximum of eight service tags in a PPPoE service name table.
Page 412: Pppoe Remote Circuit Id Capture
JUNOSe 11.1.x Link Layer Configuration Guide By contrast, when the connection between the router and the DSLAM is on an Ethernet interface that does not use either virtual LANs (VLANs) or stacked VLANs (S-VLANs), the NAS-Port-Id value is the same for all subscribers on the Ethernet link. Enabling the router to capture the remote circuit ID sent from the DSLAM and use it as a RADIUS or L2TP attribute facilitates the process of identifying individual subscribers on an Ethernet link.
Page 413 Chapter 12: Configuring Point-to-Point Protocol over Ethernet Table 20: Configuring Nondefault Formats for the PPPoE Remote Circuit ID (continued) To Configure This Nondefault Format Use This Command Append the agent-circuit-id suboption to an host1(config)#radius remote-circuit-id-format interface specifier that is consistent with the dsl-forum-1 recommended format in the DSL Forum Technical Report (TR)-101 Migration to...
Page 414: Table 21: Interface Specifier Format Examples For Dsl-Forum-1 Keyword
JUNOSe 11.1.x Link Layer Configuration Guide The dsl-forum-1 format for ATM interfaces is atm slot/adapter/port:vpi.vci The dsl-forum-1 format for Ethernet interfaces is eth slot/adapter/port:svlanId.vlanId For the E120 or the E320 routers, the router uses the actual adapter value (0 or 1) in the dsl-forum-1 format.
Page 415: Use By Radius Or L2Tp
Chapter 12: Configuring Point-to-Point Protocol over Ethernet Table 21: Interface Specifier Format Examples for dsl-forum-1 Keyword (continued) Format of Interface Example Internal Router Format How Router Translates dslForum1InterfaceSpecifier Gigabit Ethernet interface on gigabitEthernet 2/0 Sets adapter to 0 eth 2/0/0:4096.4096 slot 2, port 0 with no VLAN Sets both svlanId and or S-VLAN subinterfaces...
Page 416: System Event Log
JUNOSe 11.1.x Link Layer Configuration Guide Issue the radius override nas-port-id remote-circuit-id command to substitute the remote circuit ID value for the standard NAS-Port-Id [87] RADIUS attribute. Issue the aaa tunnel calling-number-format command to generate L2TP Calling Number attribute value pair (AVP) 22 in a descriptive format that includes either or both of the agent-circuit-id (suboption 1) and agent-remote-id (suboption 2) suboptions of the PPPoE intermediate agent tags.
Page 417: Module Requirements
Chapter 12: Configuring Point-to-Point Protocol over Ethernet ERX1410 router ERX710 router ERX705 router ERX310 router Module Requirements For information about the modules that support PPPoE interfaces on ERX14xx models, ERX7xx models, and the ERX310 router: See ERX Module Guide, Table 1, Module Combinations for detailed module specifications.
Page 418: References
JUNOSe 11.1.x Link Layer Configuration Guide References For more information about PPPoE, consult the following resources: DSL Forum Technical Report (TR)-101 Migration to Ethernet-Based DSL Aggregation (April 2006) Extensions to a Method for Transmitting PPP over Ethernet (PPPoE) draft-carrel-info-pppoe-ext-00.txt (November 2000 expiration) IEEE 802.1q (Virtual LANs) RFC 2516 Method for Transmitting PPP over Ethernet (PPPoE) (February 1998) NOTE: IETF drafts are valid for only 6 months from the date of issuance.
Page 419 Chapter 12: Configuring Point-to-Point Protocol over Ethernet Configure a PVC by specifying the vcd (virtual circuit descriptor), the vpi (virtual path identifier), the vci (virtual channel identifier), and the encapsulation type. host1(config-if)#atm pvc 10 22 100 aal5snap Select PPPoE as the encapsulation method. host1(config-subif)#encapsulation pppoe Do one of the following to configure the maximum number of PPPoE sessions (subinterfaces) supported on the interface:...
Page 420 JUNOSe 11.1.x Link Layer Configuration Guide Use to override the current PPPoE maximum session value set with the pppoe sessions command with the PPPoE maximum session value returned by the RADIUS server in the Max-Clients-Per-Interface VSA [26-143]. RADIUS returns the Max-Clients-Per-Interface VSA value in Access-Accept messages for each subscriber during PPP authentication.
Page 421: Figure 38: Example Of Pppoe Over Atm Stacking
Chapter 12: Configuring Point-to-Point Protocol over Ethernet Example host1(config-if)#pppoe max-session-vsa override Use the no version to restore the default behavior, ignore. See pppoe max-session-vsa. Figure 38 on page 389 illustrates the interface stack for this configuration. Figure 38: Example of PPPoE over ATM Stacking atm pvc Use to configure a PVC on an ATM interface.
Page 422 JUNOSe 11.1.x Link Layer Configuration Guide aal5snap Specifies a logical link control (LLC) encapsulated circuit. An LLC/Subnetwork Access Protocol (LLC/SNAP) header precedes the protocol datagram. aal5mux ip Specifies a multiplexed circuit used for IP only. aal5autoconfig Enables the autodetection of a 1483 encapsulation (LLC/SNAP or VC multiplexed).
Page 423 Chapter 12: Configuring Point-to-Point Protocol over Ethernet 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).
Page 424 JUNOSe 11.1.x Link Layer Configuration Guide Example host1(config-subif)#pppoe duplicate-protection Use the no version to disable duplicate protection. See pppoe duplicate-protection. pppoe mtu Use to set the MTU using a combination of lower layer restrictions and controls. You can specify an MTU greater than the current maximum permitted by RFC 2516, in the range 66–65535.
Page 425: Configuring Pppoe For Ethernet Modules
Chapter 12: Configuring Point-to-Point Protocol over Ethernet Configuring PPPoE for Ethernet Modules You can configure PPPoE on Fast Ethernet (FE), Gigabit Ethernet (GE), and 10-Gigabit Ethernet (10GE) modules. You can configure Ethernet interfaces with IP only, with PPPoE only, with both IP and PPPoE, and with or without VLANs. This section provides information about configuring PPPoE without VLANs.
Page 426: Figure 39: Example Of Configuring Ipv4 And Ipv6 Over Pppoe
JUNOSe 11.1.x Link Layer Configuration Guide Figure 39: Example of Configuring IPv4 and IPv6 over PPPoE IPv4 IPv4 IPv6 PPP interface PPP interface PPPoE subinterface PPPoE subinterface PPPoE interface VLAN Gigabit Ethernet To configure IPv4 and IPv6 interface columns over static PPPoE: Specify a Fast Ethernet, Gigabit Ethernet, or 10-Gigabit Ethernet interface.
Page 427 Chapter 12: Configuring Point-to-Point Protocol over Ethernet host1(config-if)#ipv6 unnumbered loopback 0 Enable the IPv6 Neighbor Discovery process on an interface. host1(config-if)#ipv6 nd Specify which IPv6 prefixes the system includes in IPv6 router advertisements. host1(config-if)#ipv6 nd prefix-advertisement 2002:1::/64 60000 45000 onlink autoconfig (Optional) Configure additional VLAN subinterfaces by completing Steps 3 through encapsulation ppp...
Page 428 JUNOSe 11.1.x Link Layer Configuration Guide Use to enable the IPv6 Neighbor Discovery process on an interface. You can include the following commands in IPv6 profiles to configure Neighbor Discovery route advertisement characteristics. Command Description ipv6 nd Enables Neighbor Discovery on an interface ipv6 nd prefix-advertisement Specifies IPv6 prefix included in IPv6 router advertisements Example...
Page 429: Configuring Pppoe Without Vlans
Chapter 12: Configuring Point-to-Point Protocol over Ethernet the EAP protocol. If the peer refuses to negotiate authentication, the router terminates the PPP session. Example 2 Configures EAP or CHAP or PAP on a dynamic PPP interface host1(config)#profile ppptest host1(config-profile)#ppp authentication eap chap pap In this example, the router first attempts EAP negotiation.
Page 430: Figure 40: Example Of Pppoe Stacking
JUNOSe 11.1.x Link Layer Configuration Guide host1(config-if)#pppoe Create a PPPoE subinterface. host1(config-if)#pppoe subinterface fastEthernet 4/1.1 Specify PPP as the encapsulation method on the interface. host1(config-subif)#encapsulation ppp (Optional) Configure an access concentrator (AC) name on the PPPoE interface. host1(config-subif)#pppoe acname CYM9876 (Optional) Set up the router to prevent a client from establishing more than one session using the same MAC address.
Page 431 Chapter 12: Configuring Point-to-Point Protocol over Ethernet interface fastEthernet Use to select a Fast Ethernet interface. For more information, see chapter Configuring Ethernet Interfaces in JUNOSe Physical Layer Configuration Guide. Example host1(config)#interface fastEthernet 1/0 Use the no version to remove IP from an interface or subinterface. You must issue the no version from the highest level down;...
Page 432 JUNOSe 11.1.x Link Layer Configuration Guide Use to specify PPPoE as the encapsulation method for the interface. This command creates a PPPoE major interface. Example host1(config-if)#pppoe Use the no version to remove the PPPoE major interface. See pppoe. pppoe acName Use to configure an access concentrator (AC) name on the PPPoE interface.
Page 433: Configuring Padm Messages
Chapter 12: Configuring Point-to-Point Protocol over Ethernet Configuring PADM Messages You can configure PPPoE to issue and display a PPPoE Active Discovery Message (PADM). The PADM message is a control message that servers send to clients. The clients may act on the control message, but are not required to do so. There are two types of PADM messages: Message of the minute (MOTM) Informs clients of interesting system information URL Typically spawns an Internet browser with the specified URL as the initial...
Page 434 JUNOSe 11.1.x Link Layer Configuration Guide Use in Interface Configuration mode. Example host1(config-if)#interface fastEthernet 1/0.1.1 host1(config-if)#pppoe motm Router going down at 10:00 p.m. Use the no version to disable the message. See pppoe motm. pppoe motm Use in a profile to cause the PPPoE application to send the string to the new client that is created when the profile is dynamically attached to an IP interface.
Page 435: Configuring Padn Messages
Chapter 12: Configuring Point-to-Point Protocol over Ethernet %d domain name %D profile name %% % character Use in Profile Configuration mode. Example host1(config-profile)#pppoe url http://www.relevanturl.com Use the no version to disable the message. See pppoe url. Configuring PADN Messages You can configure PPPoE to receive PPPoE Active Discovery Network (PADN) messages.
Page 436: Configuring Pppoe Service Name Tables
JUNOSe 11.1.x Link Layer Configuration Guide Example host1(config-domain-map)#padn 10.2.25.6 255.255.255.255 13 Use the no version to delete PADN parameters for the domain name. See padn. Configuring PPPoE Service Name Tables To configure PPPoE service name tables on the router: Create the PPPoE service name table. (Optional) Add entries to populate the PPPoE service name table.
Page 437: Table 23: Pppoe Service Name Table With Entries
Chapter 12: Configuring Point-to-Point Protocol over Ethernet (Optional) From PPPoE Service Name Table Configuration mode, create entries to populate the PPPoE service name table. You can configure up to 16 specific service name entries per table, in addition to the empty and unknown service name tags. host1(config-pppoe-service-name-table)#service myISPService action drop host1(config-pppoe-service-name-table)#service myQOSClass1 action terminate host1(config-pppoe-service-name-table)#service myQOSClass2 action drop...
Page 438 JUNOSe 11.1.x Link Layer Configuration Guide Specify a table name of up to 31 alphanumeric characters. This command accesses PPPoE Service Name Table Configuration mode, which enables you to configure entries for the PPPoE service name table. Example host1(config)#pppoe-service-name-table myServiceTable1 Use the no version to remove the specified PPPoE service name table from the router.
Page 439: Enabling Pppoe Service Name Tables For Use With Static Interfaces
Chapter 12: Configuring Point-to-Point Protocol over Ethernet host1(config-pppoe-service-name-table)# service myQOSClass2 action drop Example 3 – Includes an unknown service name entry in the PPPoE service name table. The associated action for this service tag is terminate. Use the action keyword with the service command to associate an action with the unknown service name entry.
Page 440 JUNOSe 11.1.x Link Layer Configuration Guide atm pvc Use to configure a PVC on an ATM interface. For details about specifying the mandatory VCD, VPI, VCI, and encapsulation type parameters, see “atm pvc” on page 389. Example host1(config-if)#atm pvc 10 100 22 aal5snap Use the no version to remove the specified PVC.
Page 441: Pppoe Over Ethernet Configurations
Chapter 12: Configuring Point-to-Point Protocol over Ethernet PPPoE over Ethernet Configurations To enable a PPPoE service name table for use with a static interface in PPPoE over Ethernet configurations: Configure a Fast Ethernet, Gigabit Ethernet, or 10-Gigabit Ethernet physical interface. host1(config)#interface fastEthernet 4/1 Select PPPoE as the encapsulation method on the interface.
Page 442: Enabling Pppoe Service Name Tables For Use With Dynamic Interfaces
JUNOSe 11.1.x Link Layer Configuration Guide See interface gigabitEthernet. See interface tenGigabitEthernet. pppoe Use to specify PPPoE as the encapsulation method for the interface. This command creates a PPPoE major interface. Example host1(config-if)#pppoe Use the no version to remove the PPPoE major interface. See pppoe.
Page 443 Chapter 12: Configuring Point-to-Point Protocol over Ethernet Configure a physical interface. On ERX7xx models, ERX14xx models, and the ERX310 router: host1(config-if)#interface atm 3/0.1 Configure an ATM PVC by specifying the VCD, the VPI, the VCI, and the encapsulation type. host1(config-subif)#atm pvc 10 100 22 aal5snap Apply the profile to the interface.
Page 444: Configuring Pads Packet Content
JUNOSe 11.1.x Link Layer Configuration Guide host1(config)#interface atm 3/0.1 host1(config)#interface atm 3/0/0.1 Use the no version to remove the interface or subinterface. See interface atm. pppoe service-name-table Use from Profile Configuration mode to assign a PPPoE service name table to a profile for use by the dynamic PPPoE interface column associated with the profile.
Page 445: Configuring Pppoe Remote Circuit Id Capture
Chapter 12: Configuring Point-to-Point Protocol over Ethernet Use to prevent the router from sending the AC-Name and AC-Cookie tags in the PADS packet. The pppoe pads disable-ac-info command affects PADS packets sent only on PPPoE interfaces configured on the router after the command is issued. It has no effect on PADS packets sent on previously created PPPoE interfaces.
Page 446 JUNOSe 11.1.x Link Layer Configuration Guide For information about how to use these commands, see “show pppoe interface” on page 421 and “show profile” on page 430. (Optional) Configure the format of the captured PPPoE remote circuit ID value. a. Configure RADIUS to specify a nondefault format for the PPPoE remote circuit ID value.
Page 447 Chapter 12: Configuring Point-to-Point Protocol over Ethernet host1(config)#radius override nas-port-id remote-circuit-id b. Configure the E Series L2TP access controller (LAC) to generate L2TP Calling Number AVP 22 in fixed format or one of several formats that includes either or both of the agent-circuit-id (suboption 1) and agent-remote-id (suboption 2) suboptions of the tags supplied by the PPPoE intermediate agent.
Page 448 JUNOSe 11.1.x Link Layer Configuration Guide host1(config)#aaa tunnel calling-number-format descriptive include-agent-circuit-id Example 2 host1(config)#aaa tunnel calling-number-format descriptive include-agent-circuit-id include-agent-remote-id Example 3 host1(config)#aaa tunnel calling-number-format include-agent-circuit-id Use the no version to restore the default calling number format, descriptive. See aaa tunnel calling-number-format. aaa tunnel calling-number-format-fallback Use to configure the fallback format that the E Series LAC uses to generate the L2TP Calling Number AVP 22 in the event that the PPPoE agent ID is null or...
Page 449 Chapter 12: Configuring Point-to-Point Protocol over Ethernet Use to enable a static PPPoE interface (from Interface Configuration mode or Subinterface Configuration mode) or a dynamic PPPoE interface (from Profile Configuration mode) to capture and process a vendor-specific tag containing a remote circuit ID transmitted from a DSLAM.
Page 450 JUNOSe 11.1.x Link Layer Configuration Guide Use the no version to restore the default delimiter character, #. See radius remote-circuit-id-delimiter. radius remote-circuit-id-format Use to configure the format of the PPPoE remote circuit ID value captured from a DSLAM. By default, the router formats the PPPoE remote circuit ID to include only the agent-circuit-id suboption (suboption 1) of the tags supplied by the PPPoE intermediate agent.
Page 451: Monitoring Pppoe
Chapter 12: Configuring Point-to-Point Protocol over Ethernet Example 4 Formats the PPPoE remote circuit ID value to include the NAS-Identifier [32] RADIUS attribute with the agent-remote-id suboption of the tags supplied by the PPPoE intermediate agent. host1(config)#radius remote-circuit-id-format nas-identifier agent-remote-id Example 5 Formats the PPPoE remote circuit ID value to include the NAS-Identifier [32] RADIUS attribute with both the agent-circuit-id and agent-remote-id suboptions of the tags supplied by the PPPoE intermediate agent.
Page 452 JUNOSe 11.1.x Link Layer Configuration Guide When baselining is requested, the time since the last baseline was set is displayed in hours:minutes:seconds or days/hours format. If a baseline has not been set, the message “No baseline has been set” is displayed instead. Use the optional delta keyword with PPPoE show commands to specify that baselined statistics will be shown.
Page 453 Chapter 12: Configuring Point-to-Point Protocol over Ethernet Use to display parameters on a PPPoE interface or a PPPoE subinterface. If you do not specify an interface and subinterface, the router displays the PPPoE interface and Status parameters for all configured interfaces. If you specify an interface with no subinterface, the router displays the PPPoE interface and Status parameters for that interface.
Page 454 JUNOSe 11.1.x Link Layer Configuration Guide PADR received/PADR transmitted Number of request control packets received/transmitted PADS received/PADS transmitted Number of session confirmation control packets received/transmitted PADT received/PADT transmitted Number of termination control packets received/transmitted PADM received/PADM transmitted Number of message control packets received/transmitted PADN received/PADN transmitted Number of network control packets received/transmitted...
Page 455 Chapter 12: Configuring Point-to-Point Protocol over Ethernet Type Lockout for PPPoE Clients” on page 548 in “Configuring Dynamic Interfaces” on page 515 Min Minimum lockout time, in seconds Max Maximum lockout time, in seconds Total clients in active lockouts Number of PPPoE clients currently undergoing dynamic encapsulation type lockout Total clients in lockout grace period Number of PPPoE clients currently in a lockout grace period...
Page 456 JUNOSe 11.1.x Link Layer Configuration Guide Total clients in active lockouts: 0 Total clients in lockout grace period: 0 Example2 Uses the Fast Ethernet interface host1#show pppoe interface fastEthernet 9/4 PPPoE interface fastEthernet 9/4 is operStatusUp PPPoE interface fastEthernet 9/4 has max sessions = 8000 PPPoE interface fastEthernet 9/4 has no acName set PPPoE interface fastEthernet 9/4 is in test mode PPPoE interface fastEthernet 9/4 has 16 active connections,...
Page 457 Chapter 12: Configuring Point-to-Point Protocol over Ethernet PAD packets received PAD packets transmitted Invalid PAD Packets: Invalid Version Invalid PAD Code Invalid PAD Tags Invalid PAD Tag length Invalid PAD Type Invalid PADI Session Invalid PADR Session Invalid PAD packet length 0 Invalid PAD packets Total Invalid PAD packets Insufficient Resources 0...
Page 458 JUNOSe 11.1.x Link Layer Configuration Guide Total Invalid PAD packets Insufficient Resources 0 Lockout Configuration (seconds): Min 5, Max 60 Total clients in active lockouts: 0 Total clients in lockout grace period: 0 See show pppoe interface. show pppoe interface summary Use to display the operational and administrative status of all configured PPPoE interfaces.
Page 459 Chapter 12: Configuring Point-to-Point Protocol over Ethernet Use to display the contents of a PPPoE service name table configured on the router. The command displays the table name, the name of all service name entries in the table, and the action (terminate or drop) associated with the service name entries.
Page 460 JUNOSe 11.1.x Link Layer Configuration Guide Example 4 Displays the names of all PPPoE service name tables configured on the router host1#show pppoe-service-name-table brief Service-Name Table: myServiceTable1 myServiceTable2 See show pppoe-service-name-table. show pppoe subinterface Use to display parameters for PPPoE subinterfaces. If you do not specify a subinterface, the router displays the configured PPPoE subinterface number and status for all configured PPPoE subinterfaces.
Page 461 Chapter 12: Configuring Point-to-Point Protocol over Ethernet host1:v0#show pppoe subinterface fastEthernet 1/1.1.1 PPPoE subinterface fastEthernet 1/1.1.1 is operStatusUp URL String: http://www.urlofinterest.com MOTM String: a horse walks into a bar PPPoE subinterface fastEthernet 1/1.1.1 has a session id of 1 PPPoE Statistics In Octets: Out Octets: 256 In Packets:...
Page 462 JUNOSe 11.1.x Link Layer Configuration Guide host1:01#show pppoe subinterface summary Total PPPoE subinterfaces: 116 Administrative Status: Up: 115 Down: 1 Operational Status: Up: 115 Down: 1 LowerLayerDown: 1 NotPresent: 0 See show pppoe subinterface. show profile Use to display information about profiles. To display information about a specific profile, use the name keyword.
Page 463 Chapter 12: Configuring Point-to-Point Protocol over Ethernet Route Map Name Route map applied to the IP interface subscriber; enabled or disabled Auto Detect Router automatically detects packets that do not match any entries in the demultiplexer table; enabled or disabled Auto Configure Dynamic creation of subscriber interfaces on a primary IP interface;...
Page 464 JUNOSe 11.1.x Link Layer Configuration Guide PPP Initiate IPv6 Initiation of IPv6 over this PPP interface; enabled or disabled PPPoE Max Sessions Maximum number of PPPoE subinterfaces that can be on an interface PPPoE Always-offer Router offers to set up a session for the client, even if the router has insufficient resources to establish a session;...
Page 465 Chapter 12: Configuring Point-to-Point Protocol over Ethernet PPP Packet Log : disabled PPP State Log : disabled PPP Chap Challenge Length : 16 - 32 PPP Passive Mode : disabled PPP Multilink : disabled PPP IPCP Netmask Option : disabled PPP AAA Profile PPP Multilink Fragmentation : disabled PPP Multilink Fragment Size : (use MTU)
Page 466: Troubleshooting
JUNOSe 11.1.x Link Layer Configuration Guide Use to display the delimiter character configured to set off components in the PPPoE remote circuit ID value captured from a DSLAM. The default delimiter character is #. Example host1#show radius remote-circuit-id-delimiter See show radius remote-circuit-id-delimiter. show radius remote-circuit-id-format Use to display the format configured for the PPPoE remote circuit ID value captured from a DSLAM.
Page 467 Chapter 12: Configuring Point-to-Point Protocol over Ethernet You also configure logging to direct the output to a specific destination. For information, see Overview of System Logging. Example host1(config-if)#ip address 164.10.6.71 255.255.255.0 host1(config-if)#log severity debug pppoeControlPacket atm 10/0.1 host1:v0#DEBUG 07/25/2000 15:13:19 pppoeControlPacket (interface atm 10/0.1): PADI rx from 00-09-01-a0-00-2e DEBUG 07/25/2000 15:13:19 pppoeControlPacket (interface atm 10/0.1): PADO tx to 00-09-01-a0-00-2e...
Page 468 JUNOSe 11.1.x Link Layer Configuration Guide Troubleshooting...
Page 469: Chapter 13 Configuring Bridged Ip
Chapter 13 Configuring Bridged IP E Series routers support bridged IP (1483) interfaces. This chapter contains the following sections: Overview on page 437 Platform Considerations on page 438 References on page 439 Before You Configure Bridged IP on page 439 Configuring Bridged IP on page 440 Overview You can configure a bridged IP interface to manage IP packets that are encapsulated...
Page 470: Dhcp
JUNOSe 11.1.x Link Layer Configuration Guide unrestricted proxy ARP feature is enabled, the router response is redundant and might fool the IP client into determining that the destination MAC address within its own subnet is the same as the address of the router. DHCP DHCP provides a mechanism through which hosts using TCP/IP can obtain protocol configuration parameters automatically from a DHCP server on the network.
Page 471: Interface Specifiers
Chapter 13: Configuring Bridged IP For information about the modules that support bridged IP interfaces on the E120 and E320 routers: See E120 and E320 Module Guide, Table 1, Modules and IOAs for detailed module specifications. See E120 and E320 Module Guide, Appendix A, IOA Protocol Support for information about the modules that support bridged IP.
Page 472: Configuring Bridged Ip
JUNOSe 11.1.x Link Layer Configuration Guide Table 24 on page 440 lists the prerequisite tasks for configuring bridged IP and the resources that you can consult to learn how to perform these tasks. Table 24: Prerequisite Tasks for Configuring Bridged IP To Learn About Preconfiguration and hardware ERX Hardware Guide...
Page 473 Chapter 13: Configuring Bridged IP Assign an IP address and subnet mask to the PVC. host1(config-subif)#ip address 192.168.10.20 255.255.255.0 NOTE: You can also assign an IP template to the interface or create an unnumbered interface instead of assigning an IP address. For details, see chapter Configuring IP in JUNOSe IP, IPv6, and IGP Configuration Guide.
Page 474 JUNOSe 11.1.x Link Layer Configuration Guide encapsulation bridge1483 Use to configure bridged IP as the encapsulation method on an interface. Use the unrestrictedProxyArp keyword to allow the router to perform unrestricted processing of ARP requests even if the route is on the same interface on which the request is received.
Page 475: Configuring Bridged Ethernet
Chapter 14 Configuring Bridged Ethernet This chapter describes how to configure bridged Ethernet on E Series routers. E Series routers also support bridged Ethernet on dynamic interfaces. See “Configuring Dynamic Interfaces” on page 515, for details. This chapter contains the following sections: Overview on page 443 Platform Considerations on page 446 References on page 447...
Page 476: Bridged Ethernet Application
JUNOSe 11.1.x Link Layer Configuration Guide Bridged Ethernet Application Figure 41 on page 444 shows an example of a client computer using IP/PPP/PPPoE and an Internet gaming system running IP, connecting to the E Series router over the same ATM PVC. The client computer and gaming system can connect to an E Series router via an xDSL modem over a single ATM PVC, and the router can forward these two data streams independently.
Page 477: Vlan And S-Vlan Configurations
Chapter 14: Configuring Bridged Ethernet VLAN and S-VLAN Configurations Bridged Ethernet interfaces on E Series routers support the configuration of virtual local area networks (VLANs) and stacked virtual local area networks (S-VLANs). A VLAN permits multiplexing multiple higher-level protocols over a single physical port. An S-VLAN provides a two-level VLAN tag structure, which extends the VLAN ID space to more than 16 million VLAN tags.
Page 478: Platform Considerations
JUNOSe 11.1.x Link Layer Configuration Guide S-VLAN oversubscription is not supported on bridged Ethernet interfaces. After you configure the bridged Ethernet interface, you configure the VLANs, S-VLANs, and the supported higher-level protocols in the same way that you configure them over Ethernet interfaces.
Page 479: Interface Specifiers
Chapter 14: Configuring Bridged Ethernet Interface Specifiers The configuration task examples in this chapter use the slot/port[.subinterface ] format to specify the ATM physical interface on which you want to configure bridged Ethernet. However, the interface specifier format that you use depends on the router that you are using.
Page 480 JUNOSe 11.1.x Link Layer Configuration Guide Encapsulate the ATM 1483 subinterface with bridged Ethernet. The use of the encapsulation keyword implies that the bridged Ethernet interface is the only interface stacked directly above the ATM 1483 subinterface. As a result, the bridged Ethernet interface cannot have a peer interface stacked above the same lower-layer interface.
Page 481 Chapter 14: Configuring Bridged Ethernet Configure PPP encapsulation over the PPPoE subinterface, and the IP interface over the PPP interface. host1(config-subif)#encapsulation ppp host1(config-subif)#ip address 160.1.1.1 255.255.255.0 atm pvc Use to configure a PVC on an ATM interface. Specify one of the following encapsulation types: aal5snap Specifies a logical link control (LLC) encapsulated circuit;...
Page 482 JUNOSe 11.1.x Link Layer Configuration Guide Use the no version, without the MAC address, to remove bridged Ethernet as the encapsulation method on the interface. See encapsulation bridge1483. encapsulation ppp Use to configure PPP as the encapsulation method for an interface. Example host1(config-subif)#encapsulation ppp Use the no version to remove PPP as the encapsulation method on the interface.
Page 483 Chapter 14: Configuring Bridged Ethernet Use to set an IP address for the interface. Note that you cannot add more than one IP address to bridged Ethernet interfaces. Example host1(config-subif)#ip address 160.1.0.1 255.255.255.0 Use the no version to remove the IP address. See ip address.
Page 484: Alternative Configuration
JUNOSe 11.1.x Link Layer Configuration Guide Use to create a PPPoE subinterface on an ATM interface. On ERX7xx models, ERX14xx models, and the ERX310 router, use the slot/port.atmSubinterface.pppoeSubinterface format. On the E120 and E320 routers, use the slot/adapter/port.atmSubinterface.pppoeSubinterface format. RLI-1050 Examples host1(config)#pppoe subinterface atm 9/1.1.1 host1(config)#pppoe subinterface atm 5/0/1.1.1...
Page 485: Configuring Vlans Over Bridged Ethernet
Chapter 14: Configuring Bridged Ethernet Configuring VLANs over Bridged Ethernet This section describes how to create the following common static VLAN over bridged Ethernet configurations: IP over VLAN over bridged Ethernet PPPoE over VLAN over bridged Ethernet MPLS over VLAN over bridged Ethernet You can also configure transparent bridging over VLANs over bridged Ethernet.
Page 486: Configuring Higher-Level Protocols Over Vlans
JUNOSe 11.1.x Link Layer Configuration Guide Create a VLAN subinterface to carry the higher-level protocols by adding a subinterface number to the interface identification command. host1(config-subif)#interface atm 4/0.101.1 Assign a VLAN ID for the subinterface. host1(config-subif)#vlan id 10 (Optional) Configure additional VLAN subinterfaces by repeating Steps 4 and 5, using unique values.
Page 487: Configuring Mpls Over Vlan
Chapter 14: Configuring Bridged Ethernet host1(config)#pppoe subinterface atm 4/0.101.2.1 Specify PPP as the encapsulation method on the interface. host1(config-subif)#encapsulation ppp Assign an IP address and mask to the interface. host1(config-subif)#ip address 10.1.1.2 255.255.255.0 Configuring MPLS over VLAN To configure MPLS over VLAN over a bridged Ethernet interface: Follow the steps in “Configuring VLAN Subinterfaces over Bridged Ethernet”...
Page 488 JUNOSe 11.1.x Link Layer Configuration Guide Use to configure PPP as the encapsulation method on an interface. Example host1(config-subif)#encapsulation ppp Use the no version to remove PPP as the encapsulation method on the interface. See encapsulation ppp. encapsulation vlan Use to configure VLAN as the encapsulation method on an interface. Example host1(config-subif)#encapsulation vlan Use the no version to remove VLAN as the encapsulation method on the interface.
Page 489 Chapter 14: Configuring Bridged Ethernet host1(config-subif)#ip address 10.1.2.3 255.255.255.255 Use the no version to remove the IP address. See ip address. mpls Use to enable, disable, or delete MPLS on an interface. MPLS is disabled by default. Example host1(config)#mpls Use the no version to halt MPLS on the interface and delete the MPLS interface configuration.
Page 490: Configuring S-Vlans Over Bridged Ethernet
JUNOSe 11.1.x Link Layer Configuration Guide Use the optional keyword untagged to specify that frames be sent untagged. The keyword is valid only for VLAN ID 0. It allows tagged frames to be received, but sends out untagged frames. Example host1(config-subif)#vlan id 400 There is no no version.
Page 491 Chapter 14: Configuring Bridged Ethernet Create a VLAN subinterface to carry the higher-level protocols by adding a subinterface number to the interface identification command. host1(config-subif)#interface atm 3/1.1.1 Assign an S-VLAN ID and a VLAN ID for the subinterface. host1(config-subif)#svlan id 4 255 Assign an S-VLAN Ethertype.
Page 492: Configuring Higher-Level Protocols Over S-Vlans
JUNOSe 11.1.x Link Layer Configuration Guide Configuring Higher-Level Protocols over S-VLANs The procedures for configuring IP, PPPoE, and MPLS protocols over S-VLANs on bridged Ethernet interfaces are identical to the procedures for configuring these protocols over VLANs on bridged Ethernet interfaces. This section provides an example for configuring PPPoE interfaces over S-VLAN subinterfaces configured on bridged Ethernet.
Page 493: Monitoring Bridged Ethernet
Chapter 14: Configuring Bridged Ethernet MTU. For bridged Ethernet interfaces, the operational MTU is the lesser of the following two values: The administrative MTU of the bridged Ethernet interface The administrative MTU of the underlying ATM 1483 subinterface You can also use the bridge1483 mtu command in a profile to configure a nondefault MTU size for a dynamic bridged Ethernet interface.
Page 494 JUNOSe 11.1.x Link Layer Configuration Guide Use to display configuration and status information for all bridged Ethernet interfaces currently configured on the router. Use the atm keyword and an interface specifier to display information for a bridged Ethernet interface that is stacked over an ATM subinterface. Use the summary keyword to display only a count of all bridged Ethernet interfaces configured on the router.
Page 495 Chapter 14: Configuring Bridged Ethernet ARP requests Number of ARP requests ARP responses Number of ARP responses Errors Total number of errors in all ARP packets Discards Total number of discarded ARP packets Total bridge1483 interfaces Total number of bridged Ethernet interfaces configured on the router;...
Page 496 JUNOSe 11.1.x Link Layer Configuration Guide Address IP address of the entry Hardware Addr Physical (MAC) address of the entry Example host1:vr1#show ip mac-validate interface atm 8/0.1 ATM8/0.1: Strict Address Hardware Addr 180.1.0.2 0000.1111.2222 See show ip mac-validate interface. show vlan subinterface Use to display configuration and status information for a specified VLAN subinterface or for all VLAN subinterfaces configured on the router.
Page 497 Chapter 14: Configuring Bridged Ethernet Example 2 Displays full status and configuration information for the specified VLAN subinterface host1#show vlan subinterface atm 3/0.1.2 Interface Status Svlan Id Vlan Id Ethertype ------------------------- ---------- ---- -------- -------- --------- ATM 3/0.1.2 1522 ---- ---- Example 3 Displays only brief summary information for all VLAN subinterfaces configured on the router...
Page 498 JUNOSe 11.1.x Link Layer Configuration Guide Monitoring Bridged Ethernet...
Page 499: Configuring Transparent Bridging
Chapter 15 Configuring Transparent Bridging This chapter provides an introduction to transparent bridging and describes how to configure transparent bridging on E Series routers. This chapter contains the following sections: Overview on page 467 Platform Considerations on page 472 References on page 473 Before You Configure Transparent Bridging on page 473 Configuration Tasks on page 474 Configuration Examples on page 488...
Page 500: Bridge Groups And Bridge Group Interfaces
JUNOSe 11.1.x Link Layer Configuration Guide More specifically, a transparent bridge performs all of the following actions to learn the network topology: Learning The bridge examines the MAC address of every incoming packet, records the MAC address and associated interface in the forwarding table, and manages the database of MAC addresses and their associated interfaces.
Page 501: Bridge Interface Types And Supported Configurations
Chapter 15: Configuring Transparent Bridging Figure 43: Bridge Group with Fast Ethernet and Gigabit Ethernet Bridge Interfaces In Figure 43 on page 469, a bridge group named westford01 is configured on the E Series router, which allows the router to function as a transparent bridge between a Fast Ethernet LAN segment and a Gigabit Ethernet LAN segment.
Page 502: Subscriber Policies
JUNOSe 11.1.x Link Layer Configuration Guide Gigabit Ethernet interfaces 10-Gigabit Ethernet interfaces VLAN subinterfaces over Fast Ethernet, Gigabit Ethernet, 10-Gigabit Ethernet, or bridged Ethernet interfaces For sample configurations that include bridge interfaces, see “Configuration Examples” on page 488. For information about configuring Ethernet, ATM, and bridged Ethernet interfaces, see: “Configuring ATM”...
Page 503: Concurrent Routing And Bridging
Chapter 15: Configuring Transparent Bridging Table 26: Default Subscriber Policies for Bridge Group Interfaces (continued) Packet/Attribute Type Default Subscriber Policy Default Trunk Policy PPPoE Permit Permit Relearn Permit Permit Unicast (user-to-user) Permit Permit Unknown unicast DA Deny Permit Unknown protocol Permit Permit You cannot change the default subscriber policy values listed in Table 26 on page 470...
Page 504: Transparent Bridging And Vpls
JUNOSe 11.1.x Link Layer Configuration Guide Transparent Bridging and VPLS Except for the bridge crb and bridge route commands, you can use the existing transparent bridging commands to configure one or more instances of the Virtual Private LAN Service (VPLS), referred to as VPLS instances, on the router. VPLS employs a layer 2 virtual private network (VPN) to connect multiple individual LANs across a service provider’s MPLS core network.
Page 505: Interface Specifiers
Chapter 15: Configuring Transparent Bridging See ERX Module Guide, Appendix A, Module Protocol Support for information about the modules that support transparent bridging. For information about the modules that support transparent bridging on the E120 and E320 routers: See E120 and E320 Module Guide, Table 1, Modules and IOAs for detailed module specifications.
Page 506: Configuration Tasks
JUNOSe 11.1.x Link Layer Configuration Guide You have correctly installed a line module that supports transparent bridging. For a list of the line modules that support transparent bridging, see ERX Module Guide, Appendix A, Module Protocol Support or E120 and E320 Module Guide, Appendix A, IOA Protocol Support for information about the modules that support transparent bridging.
Page 507: Creating Bridge Groups
Chapter 15: Configuring Transparent Bridging (Optional) Enable concurrent routing and bridging. (Optional) If CRB is enabled, configure explicit routing for IP, MPLS, or PPPoE protocols. The following sections describe how to perform each of these tasks. See “Configuration Examples” on page 488 for detailed sample configurations. NOTE: For information about the maximum values that the router supports for transparent bridging, see JUNOSe Release Notes, Appendix A, System Maximums.
Page 508: Configuring Optional Bridge Group Attributes
JUNOSe 11.1.x Link Layer Configuration Guide Configuring Optional Bridge Group Attributes After you create a bridge group, you can configure the following optional attributes for the bridge group to manage the MAC address entries in the bridge group’s forwarding table: Enable or disable the bridge group’s ability to acquire dynamically learned MAC addresses;...
Page 509 Chapter 15: Configuring Transparent Bridging Use to enable or disable a specified bridge group’s ability to filter (forward or discard) frames based on their MAC address. Enables the bridge group to filter frames by their MAC address and add static (nonlearned) address entries to the forwarding table.
Page 510: Configuring Bridge Group Interfaces
JUNOSe 11.1.x Link Layer Configuration Guide Use to set the length of time, in seconds, that a dynamic (learned) MAC address entry can remain in a specified bridge group’s forwarding table. When a dynamic entry reaches its configured aging time, it “ages out” of the forwarding table.
Page 511 Chapter 15: Configuring Transparent Bridging From Global Configuration mode, select the ATM, Fast Ethernet, Gigabit Ethernet, or 10-Gigabit Ethernet interface or subinterface that you want to assign to the bridge group. Assign the interface or subinterface to an existing bridge group to create the bridge interface.
Page 512: Configuring Subscriber Policies
JUNOSe 11.1.x Link Layer Configuration Guide interface atm Use to select an ATM interface or subinterface type. Example host1(config)#interface atm 3/2.1 Use the no version to remove the interface or subinterface. See interface atm. interface fastEthernet Use to select a Fast Ethernet interface. Example host1(config)#interface fastEthernet 1/0.2 Use the no version to remove the interface or subinterface.
Page 513 Chapter 15: Configuring Transparent Bridging From Subscriber Policy Configuration mode, define the rules for each packet or attribute type for which you want to change the default value. (All other packet or attribute types will continue to use the default values listed in Table 26 on page 470.) host1(config-policy)#broadcast permit host1(config-policy)#multicast deny...
Page 514 JUNOSe 11.1.x Link Layer Configuration Guide host1(config)#bridge westford02 subscriber-policy client01 Use the no version to remove the association with the subscriber policy. NOTE: You cannot change the default subscriber policy values for a trunk (server) bridge interface. As a result, you cannot use the bridge subscriber-policy command to associate a nondefault subscriber policy with a trunk bridge interface.
Page 515 Chapter 15: Configuring Transparent Bridging Use to modify the subscriber policy for MPLS to define whether a subscriber (client) bridge interface permits (forwards) or denies (filters or drops) MPLS packets. Specify one of the following keywords: permit Forwards packets of this type deny Filters or drops packets of this type MPLS packets are forwarded by default.
Page 516 JUNOSe 11.1.x Link Layer Configuration Guide Use the no version to restore the default value. See pppoe. relearn Use to modify the relearning policy for a subscriber (client) bridge interface. The relearn command defines whether the bridge interface can relearn a MAC address entry on a different interface from the one initially associated with this entry in the forwarding table.
Page 517 Chapter 15: Configuring Transparent Bridging Use to modify the subscriber policy for the unicast (user-to-user) protocol to define whether a subscriber (client) bridge interface permits (forwards) or denies (filters or drops) unicast packets. Specify one of the following keywords: permit Forwards packets of this type deny Filters or drops packets of this type Unicast packets are forwarded by default.
Page 518: Enabling Concurrent Routing And Bridging
JUNOSe 11.1.x Link Layer Configuration Guide Use the no version to restore the default value. See unknown-protocol. Enabling Concurrent Routing and Bridging To enable concurrent routing and bridging (CRB) for all bridge groups on the router: From Global Configuration mode, issue the bridge crb command. host1(config)#bridge crb (Optional) Use the appropriate show command to verify that CRB is enabled for the bridge groups on your router.
Page 519 Chapter 15: Configuring Transparent Bridging crb command. The router detects the IP and MPLS interfaces and issues implicit bridge route commands to route these protocols. If you subsequently add a new IP interface to a bridge group, you do not need to issue the bridge route command because the implicit bridge route command for IP is still in effect.
Page 520: Configuration Examples
JUNOSe 11.1.x Link Layer Configuration Guide Configuration Examples This section provides examples that show how to configure transparent bridging on the router. With each step, an illustration shows how the router is building the interface column. Example 1: Bridging with Bridged Ethernet The following example illustrates how to configure transparent bridging with bridged Ethernet.
Page 521: Example 2: Bridging With Vlans
Chapter 15: Configuring Transparent Bridging Configure a subscriber (client) bridge group interface over the bridged Ethernet interface as a peer to the PPPoE interface. Assign the interface to the bridge group you created in Step 1. host1(config-subif)#bridge-group westford01 Example 2: Bridging with VLANs The following example illustrates how to configure transparent bridging with VLANs over a Fast Ethernet interface.
Page 522: Monitoring Transparent Bridging
JUNOSe 11.1.x Link Layer Configuration Guide Assign a unique VLAN ID to the VLAN subinterface. host1(config-if)#vlan id 100 Configure a subscriber (client) bridge group interface over the VLAN subinterface. Assign the interface to the bridge group you created in Step 1. host1(config-subif)#bridge-group westford02 Exit Subinterface Configuration mode.
Page 523: Setting Statistics Baselines
Chapter 15: Configuring Transparent Bridging Setting Statistics Baselines You can set a statistics baseline for a bridge group (by using the baseline bridge command) or for a bridge interface (by using the baseline bridge interface command). baseline bridge Use to set a statistics baseline for a specified bridge group. The router implements the baseline by reading and storing the statistics at the time the baseline is set and then subtracting this baseline whenever baseline-relative statistics are retrieved.
Page 524: Removing Dynamic Mac Address Entries
JUNOSe 11.1.x Link Layer Configuration Guide Removing Dynamic MAC Address Entries You can remove all dynamic (learned) MAC address entries from the forwarding table for a bridge group (using the clear bridge command) or for a bridge interface (using the clear bridge interface command). You can also use the clear bridge address command to remove a specific dynamic MAC address entry from the forwarding table for a bridge group.
Page 525: Monitoring Bridge Groups
Chapter 15: Configuring Transparent Bridging clear bridge interface Use to remove all dynamic MAC address entries for a network interface belonging to a bridge group from the forwarding table for that bridge group. You must specify the following: interfaceType One of the following bridge interface types listed in Interface Types and Specifiers in JUNOSe Command Reference Guide: fastEthernet gigabitEthernet...
Page 526 JUNOSe 11.1.x Link Layer Configuration Guide BridgeGroup Name assigned to the bridge group Bridge Mode Bridging capability currently enabled, either concurrent routing and bridging (CRB) or default bridging Aging Time Length of time, in seconds, that a MAC address entry can remain in the forwarding table Learning Whether acquisition of dynamically learned MAC addresses is currently enabled or disabled...
Page 527 Chapter 15: Configuring Transparent Bridging Subscriber Policy Name of the subscriber policy currently in effect for the bridge group interface In Octets Number of octets received on this interface In Frames Number of frames received on this interface In Discards Number of incoming packets discarded on this interface In Errors Number of incoming errors received on this interface Out Octets Number of octets transmitted on this interface Out Frames Number of frames transmitted on this interface...
Page 528 JUNOSe 11.1.x Link Layer Configuration Guide Learning: Enabled Max Learn: Unlimited Link Status Snmp Traps: Disabled Subscriber Policy: default Subscriber Protocol Actions: Route Route PPPoE Port Count: Interface Count: Address Table: Address Action Interface -------------- ---------- ------------------- ----- 1011.22b2.333c forward ATM3/3.1 1234.abcd.5678 discard...
Page 529 Chapter 15: Configuring Transparent Bridging Learning Whether acquisition of dynamically learned MAC addresses is currently enabled or disabled Max Learn Maximum number of dynamic MAC addresses that the bridge group can learn Link Status Snmp Traps Whether SNMP link status processing is enabled or disabled for all bridge interfaces in the bridge group Subscriber Policy Name of the subscriber policy currently in effect for the bridge group...
Page 530 JUNOSe 11.1.x Link Layer Configuration Guide Use to display configuration, statistics, and status information for all ports (interfaces) or for a specified port associated with a bridge group. To display only the port number, interface identifier, and status for each port, use the brief keyword.
Page 531 Chapter 15: Configuring Transparent Bridging Port Bridge group port number on which this interface resides Interface Interface type and specifier associated with the port (for example, ATM3/3.1) Status Operational status of the physical interface: Up, Down, LowerLayerDown, NotPresent Example 1 Displays configuration, statistics, and status information for all ports currently associated with the bridge group host1#show bridge westford01 port 1 ATM3/3.1...
Page 532: Monitoring Bridge Interfaces
JUNOSe 11.1.x Link Layer Configuration Guide Bridge Name of the bridge group for which the MAC address table is displayed Address MAC address of the entry Action Specifies how the bridge group handles this entry: forward or discard Interface Interface type and specifier on which the entry will be forwarded; this value does not appear for entries that are discarded Age Length of time that a dynamic entry has been in the forwarding table;...
Page 533 Chapter 15: Configuring Transparent Bridging In Octets Number of octets received on this interface In Frames Number of frames received on this interface In Discards Number of incoming packets discarded on this interface In Errors Number of incoming errors received on this interface Out Octets Number of octets transmitted on this interface Out Frames Number of frames transmitted on this interface Out Discards Number of outgoing packets discarded on this interface...
Page 534: Monitoring Subscriber Policies
JUNOSe 11.1.x Link Layer Configuration Guide Out Frames: Out Discards: 0 Out Errors: queue 0: traffic class best-effort, bound to bridge FastEthernet9/1.1 Queue length 0 Bytes Forwarded packets 0, Bytes 0 Dropped committed packets 0, Bytes 0 Dropped conformed packets 0, Bytes 0 Dropped exceeded packets 0, Bytes 0 Example 2 Uses the brief keyword to display a summary of all bridge interfaces configured on the router...
Page 535 Chapter 15: Configuring Transparent Bridging PPPoE Specifies how the bridge interface handles PPPoE packets Relearn Specifies whether the bridge interface can relearn a MAC address entry on a different interface from the one initially associated with this entry in the forwarding table; permit indicates that relearning is allowed, and deny indicates that relearning is prohibited Mpls Specifies how the bridge interface handles MPLS packets Example 1 Displays the rules for all default and nondefault subscriber policies...
Page 536 JUNOSe 11.1.x Link Layer Configuration Guide Relearn : Deny Mpls : Permit See show subscriber-policy. Monitoring Transparent Bridging...
Page 537: Chapter 16 Configuring Cisco Hdlc
Chapter 16 Configuring Cisco HDLC Cisco High-Level Data Link Control (HDLC) is an encapsulation protocol that governs information transfer. This chapter describes how to configure Cisco HDLC on E Series routers. This chapter contains the following sections: Overview on page 505 Platform Considerations on page 506 Before You Configure Cisco HDLC on page 507 Configuration Tasks on page 507...
Page 538: Error Frames
JUNOSe 11.1.x Link Layer Configuration Guide 18,000-byte information field size Error Frames All Cisco HDLC error frames are discarded. SLARP Keepalive One feature of Cisco HDLC is the exchange of keepalive messages. A keepalive message is a signal from one endpoint to the other that the first endpoint is still active.
Page 539: Interface Specifiers
Chapter 16: Configuring Cisco HDLC Interface Specifiers The configuration task examples in this chapter use the slot/port format to specify the physical interface on which you configure Cisco HDLC. 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 format.
Page 540: Optional Tasks
JUNOSe 11.1.x Link Layer Configuration Guide (Optional) Use the appropriate “show hdlc interface” on page 511 to verify that the configuration changes are correct. encapsulation hdlc Use to specify Cisco HDLC as the encapsulation method for the interface. Example host1(config-if)#encapsulation hdlc Use the no version to disable Cisco HDLC on the interface.
Page 541 Chapter 16: Configuring Cisco HDLC host1(config-if)#hdlc keepalive 10 Enable loopback detection on an interface. host1(config-if)#hdlc down-when-looped Disable an interface. host1(config-if)#hdlc shutdown hdlc down-when-looped Use to enable loopback detection on a Cisco HDLC interface. By default, loopback detection is disabled. Example host1(config-if)#hdlc down-when-looped Use the no version to disable loopback detection on a Cisco HDLC interface.
Page 542: Configuration Example
JUNOSe 11.1.x Link Layer Configuration Guide Use to terminate a Cisco HDLC session. This command administratively disables the interface. Example host1(config-if)#hdlc shutdown Use the no version to restart a disabled session. The default for each hdlc shutdown command is the no version. See hdlc shutdown.
Page 543: Monitoring Cisco Hdlc
Chapter 16: Configuring Cisco HDLC host1:vr1(config-if)#hdlc down-when-looped Assign an IP address to the interface. host1:vr1(config-if)#ip address 160.1.0.1 255.255.255.0 Monitoring Cisco HDLC You can monitor Cisco HDLC interfaces using the show hdlc interface command. You can set a statistics baseline for Cisco HDLC interfaces, subinterfaces, or circuits using the baseline hdlc interface serial command.
Page 544 JUNOSe 11.1.x Link Layer Configuration Guide lower-layer-down Displays interfaces with operational status LowerLayerDown not-present Displays interfaces with operational status NotPresent open Displays interfaces with administrative status Open up Displays interfaces with operational status Up full Displays configuration information, status, and statistics filter Specifies a CLI output filter Field descriptions interface status State of the interface:...
Page 545 Chapter 16: Configuring Cisco HDLC Example 2 host1#show hdlc interface full Cisco-HDLC interface serial 4/0:2 is Up Interface administrative status is open Interface maximum-transmission-unit is 1596 Interface keepalive time is 10 seconds Interface loop detection is disabled Interface statistics packets octets errors discards...
Page 546 JUNOSe 11.1.x Link Layer Configuration Guide Monitoring Cisco HDLC...
Page 547: Chapter 17 Configuring Dynamic Interfaces
Chapter 17 Configuring Dynamic Interfaces This chapter explains upper-layer dynamic interfaces and describes the procedures for configuring them on E Series routers. This chapter contains the following sections: Overview on page 515 Platform Considerations on page 521 References on page 522 About Configuring Dynamic Interfaces over Static ATM on page 522 Configuring PPP and PPPoE Dynamic Interfaces over Static ATM on page 528 Configuring PPPoE Dynamic Interfaces over PPPoE Static Interfaces on page 534...
Page 548: Autodetection
JUNOSe 11.1.x Link Layer Configuration Guide You create and configure each layer of a static interface manually through an existing configuration mechanism such as the command-line interface (CLI) or Simple Network Management Protocol (SNMP). Unlike static interfaces, dynamic interfaces are not restored through nonvolatile storage (NVS) after a reboot.
Page 549: Upper-Layer Dynamic Interface Configurations
Chapter 17: Configuring Dynamic Interfaces Upper-Layer Dynamic Interface Configurations E Series routers support the following types of upper-layer dynamic interface configurations: Dynamic IP over static ATM 1483 (IPoA) Dynamic IP over dynamic PPP over static ATM 1483 Dynamic IP over dynamic PPP over dynamic PPPoE over static ATM 1483 Dynamic IP over dynamic bridged Ethernet over static ATM 1483 Dynamic IP over dynamic MLPPP over static ATM 1483 Dynamic IP over dynamic MLPPP over dynamic PPPoE over static ATM 1483...
Page 550: Profiles
JUNOSe 11.1.x Link Layer Configuration Guide For more information about IPv4, see chapter Configuring IP in JUNOSe IP, IPv6, and IGP Configuration Guide. For more information about IPv6, see chapter Configuring IPv6 in JUNOSe IP, IPv6, and IGP Configuration Guide. Profiles You can use profiles to configure dynamic interfaces over ATM, VLAN, or Ethernet Interfaces.
Page 551: Atm Oversubscription For Dynamic Interfaces
Chapter 17: Configuring Dynamic Interfaces is granted, the RADIUS attributes are returned, a user login is created, and the dynamic interfaces are configured from the RADIUS attributes. ATM 1483 interfaces may receive configuration data from the RADIUS server in the form of traffic-shaping parameters.
Page 552: Bulk-Configured Vc Ranges
JUNOSe 11.1.x Link Layer Configuration Guide per module is less than the maximum number of configured subinterfaces supported per module. When the maximum number of active ATM 1483 subinterfaces has been reached, the router prevents all additional subscribers from connecting to the line module until at least one currently active subscriber logs out, which causes the router to tear down the dynamic interface column for that subscriber.
Page 553: Ethernet Oversubscription For Dynamic Interfaces
Chapter 17: Configuring Dynamic Interfaces Ethernet Oversubscription for Dynamic Interfaces When you configure S-VLAN subinterfaces over Ethernet interfaces to support dynamic PPPoE subinterfaces, you can take advantage of VLAN and S-VLAN oversubscription. For more information on S-VLAN oversubscription, see “S-VLAN Oversubscription” on page 188 .
Page 554: References
JUNOSe 11.1.x Link Layer Configuration Guide 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.
Page 555: About Configuring Radius For Dynamic Interfaces
Chapter 17: Configuring Dynamic Interfaces On receipt of a packet, the router creates all dynamic layers above the ATM 1483 layer, starting with the lowest dynamic layer. For example, in the case of a dynamic PPPoE interface, the router creates the PPPoE interface first, then the PPP interface, and then the IP interface.
Page 556 JUNOSe 11.1.x Link Layer Configuration Guide Configuration Method Using subscriber Command When you use the subscriber command to configure IP subscribers on dynamic bridged Ethernet over static ATM 1483 interface columns to support RADIUS authentication, the subscriber command provides the subscriber’s authentication parameters.
Page 557: Placing Dynamic Ip Routes In The Routing Table
Chapter 17: Configuring Dynamic Interfaces For more information about using the subscriber management application, see JUNOSe Broadband Access Configuration Guide. Placing Dynamic IP Routes in the Routing Table If you want to insert a dynamic IP route into the routing table of the relevant virtual router to point to the subscriber’s subinterface, you can use the Framed-Route [22] RADIUS attribute to do so.
Page 558 JUNOSe 11.1.x Link Layer Configuration Guide a received bridged Ethernet frame. Receiving an authentication denial from RADIUS causes the router to lock out bridged Ethernet. By locking out bridged Ethernet frames, the router can receive PPPoE frames unimpeded, facilitating rapid creation of dynamic PPPoE interfaces. Reduces loading on the RADIUS server.
Page 559 Chapter 17: Configuring Dynamic Interfaces Encapsulation type lockout is performed by default. You can configure the lockout time range by issuing the auto-configure command with the optional lockout-time keyword. The following guidelines describe lockout behavior: Any encapsulation type that you do not configure for autodetection with the auto-configure command is automatically locked out.
Page 560: Atm Pvc Command
JUNOSe 11.1.x Link Layer Configuration Guide A short-cycle event is a dynamic interface that is created and torn down within 60 seconds. The router tracks the time between short-cycle events to determine whether to increase the lockout time for a subsequent short-cycle event. NOTE: When the calculated lockout time is equal to or exceeds the maximum lockout time, the router uses the maximum lockout time value until the time to the next event exceeds the greater of 15 minutes or the maximum lockout time value.
Page 561: Configuring A Ppp Or Pppoe Dynamic Interface
Chapter 17: Configuring Dynamic Interfaces Figure 45: Dynamic PPP Interface Columns Figure 46 on page 529 shows dynamic PPPoE interface columns and illustrates how PPPoE supports multiple IP sessions over each ATM 1483 circuit. Figure 46: Dynamic PPPoE Interface Columns You can specify either or both ppp and pppoe for the interface by specifying the auto-configure command for each type of interface.
Page 562 JUNOSe 11.1.x Link Layer Configuration Guide Configure a physical interface. host1(config)#interface atm 5/0 Configure an ATM 1483 subinterface. host1(config-if)#interface atm 5/0.1 Configure a PVC by specifying the virtual circuit descriptor (VCD), the virtual path identifier (VPI), the virtual channel identifier (VCI), and the encapsulation type.
Page 563 Chapter 17: Configuring Dynamic Interfaces Use to configure a static ATM 1483 subinterface to support a dynamic interface. Specifies the types of dynamic encapsulation that the subinterface detects and accepts. This command creates the layers above ATM 1483 dynamically. You can enter the command repetitively to support multiple dynamic interface types.
Page 564 JUNOSe 11.1.x Link Layer Configuration Guide Use the no version to terminate detection of the specified encapsulation type or, if the lockout-time keyword is specified, to restore the lockout time range to its default value, 1–300 seconds. See auto-configure. interface atm Use to select an ATM interface or ATM 1483 subinterface.
Page 565: Terminating Stale Pppoa Subscribers And Restarting Lcp Negotiations
Chapter 17: Configuring Dynamic Interfaces Use the no version to remove a profile assignment. See profile. Terminating Stale PPPoA Subscribers and Restarting LCP Negotiations In configurations of dynamic IP over dynamic PPP over a static ATM 1483 subinterface, as shown in Figure 45 on page 529, any of the following conditions might cause the static ATM 1483 subinterface to transition to a dormant state as the result of an ungraceful subscriber logout: Rebooting the router...
Page 566: Configuring Pppoe Dynamic Interfaces Over Pppoe Static Interfaces
JUNOSe 11.1.x Link Layer Configuration Guide The router also sends an LCP terminate request packet to a PPPoA CPE device in configurations of dynamic IP over dynamic PPP over a dynamic (bulk-configured) ATM 1483 subinterface. For more information, see “Terminating Stale PPPoA Subscribers and Restarting LCP Negotiations”...
Page 567: Configuring Dynamic Pppoe Over Static Pppoe With Ethernet Interface Columns
Chapter 17: Configuring Dynamic Interfaces To configure an ATM 1483 subinterface to support a dynamic PPPoE subinterface: Configure a physical interface. host1(config)#interface atm 5/0 Configure an ATM 1483 subinterface. host1(config-if)#interface atm 5/0.1 Configure a PVC by specifying the virtual circuit descriptor (VCD), the virtual path identifier (VPI), the virtual channel identifier (VCI), and the encapsulation type.
Page 568: Configuring Dynamic Pppoe Over Static Pppoe With Ethernet And Vlan Interface Columns
JUNOSe 11.1.x Link Layer Configuration Guide Figure 48: Dynamic PPPoE over Static PPPoE with Non-VLAN Interface Columns To configure an Ethernet interface without VLANs to support a dynamic PPPoE subinterface: Specify a Fast Ethernet, Gigabit Ethernet, or 10-Gigabit Ethernet interface. host1(config)#interface fastEthernet 4/1 Assign an IP address and mask.
Page 569: Figure 49: Dynamic Pppoe Over Static Pppoe With Vlan Interface
Chapter 17: Configuring Dynamic Interfaces Figure 49: Dynamic PPPoE over Static PPPoE with VLAN Interface Columns To configure a VLAN subinterface to support a dynamic PPPoE subinterface: Specify a Fast Ethernet, Gigabit Ethernet, or 10-Gigabit Ethernet interface. host1(config)#interface fastEthernet 4/1 Specify VLAN as the encapsulation method.
Page 570: Configuring Ipv4 And Ipv6 Over Static And Dynamic Pppoe
JUNOSe 11.1.x Link Layer Configuration Guide Configuring IPv4 and IPv6 over Static and Dynamic PPPoE You can configure IPv4 and IPv6 interface columns over static and dynamic PPPoE, as shown in Figure 50 on page 538. Figure 50: IPv4 and IPv6 Interface Columns over Static and Dynamic PPPoE IPv4 IPv6 IPv6...
Page 571 Chapter 17: Configuring Dynamic Interfaces host1(config-subif)#pppoe Configure the interface to detect and accept dynamic PPPoE subinterfaces. host1(config-subif)#pppoe auto-configure Assign the profile to any autoconfigured encapsulation. host1(config-if)#pppoe profile any ipv4Ipv6Profile interface loopback Use to access and configure the loopback interface. Provides a stable address to minimize impact of a physical interface going down. Example host1(config)#interface loopback 20 host1(config-if)#ip address 10.10.20.5 255.255.255.254...
Page 572 JUNOSe 11.1.x Link Layer Configuration Guide Use to assign a virtual router to a profile. You can configure a virtual router using RADIUS instead of adding one to the profile by using the ip virtual-router command. For more information about how to configure a virtual router using RADIUS, see Configuring RADIUS Attributes in the JUNOSe Broadband Access Configuration Guide.
Page 573 Chapter 17: Configuring Dynamic Interfaces Use to set up an unnumbered interface. An unnumbered interface does not have an IPv6 address assigned to it. Unnumbered interfaces are often used in point-to-point connections where an IPv6 address is not required. This command enables IPv6 processing on an interface without your having to assign an explicit IPv6 address to the interface.
Page 574: Configuring Dynamic Pppoe Over Static Pppoe With Ethernet And S-Vlan Interface Columns
JUNOSe 11.1.x Link Layer Configuration Guide In this example, the router first attempts EAP negotiation. If PPP receives a NAK from the peer in response to the EAP request, then the router attempts CHAP negotiation. If PPP receives a NAK from the peer in response to the CHAP request, then the router attempts PAP negotiation.
Page 575: Figure 51: Dynamic Pppoe Over Static Pppoe With S-Vlan Interface
Chapter 17: Configuring Dynamic Interfaces Figure 51: Dynamic PPPoE over Static PPPoE with S-VLAN Interface Columns To configure an S-VLAN subinterface to support a dynamic PPPoE subinterface: Specify a Fast Ethernet, Gigabit Ethernet, or 10-Gigabit Ethernet interface. host1(config)#interface fastEthernet 4/1 Specify VLAN as the encapsulation method.
Page 576: S-Vlan Oversubscription
JUNOSe 11.1.x Link Layer Configuration Guide Configure the interface to detect and accept dynamic PPPoE subinterfaces. host1(config-subif)#pppoe auto-configure S-VLAN Oversubscription When you configure S-VLAN subinterfaces over Ethernet interfaces to support dynamic PPPoE subinterfaces, you can take advantage of S-VLAN oversubscription. The maximum number of S-VLANs that you can create per I/O module or IOA with PPPoE major interfaces stacked over them is greater than the maximum number of dynamic PPPoE subinterfaces.
Page 577 Chapter 17: Configuring Dynamic Interfaces aal5mux ip Specifies a VC multiplexed circuit. This option is used for IP only. Example host1(config-subif)#atm pvc 6 0 11 aal5autoconfig Use the no version to remove the specified PVC. See atm pvc. encapsulation pppoe Use to configure PPPoE as the encapsulation method for the interface.
Page 578 JUNOSe 11.1.x Link Layer Configuration Guide Use the no version to remove IP from an interface or a subinterface. You must issue the no version from the highest level down; you cannot remove an interface or a subinterface if the one above it still exists. See interface fastEthernet.
Page 579 Chapter 17: Configuring Dynamic Interfaces pppoe profile Use to assign a profile to a static PPPoE major interface. The profile configuration is used to dynamically configure an upper bridged Ethernet, IP, PPP, or PPPoE interface. Specify a profile name with up to 80 alphanumeric characters. The default encapsulation type, any, applies to any autoconfigured encapsulation that does not have a specific profile assignment.
Page 580: Configuring Encapsulation Type Lockout For Pppoe Clients
JUNOSe 11.1.x Link Layer Configuration Guide vlan id Use to specify the VLAN ID. Use a VLAN ID that is in the range 0–4095 and is unique within the Ethernet interface. Issue the vlan id command before any upper bindings are made, such as IP or PPPoE.
Page 581: Configuration Tasks
Chapter 17: Configuring Dynamic Interfaces Table 28: Differences in Lockout Operation for Dynamic PPPoE Configurations Dynamic PPPoE over Static PPPoE Dynamic PPPoE over Static ATM 1483 Encapsulation type lockout is disabled by Encapsulation type lockout is enabled by default default. with a lockout time range of 1–300 seconds.
Page 582 JUNOSe 11.1.x Link Layer Configuration Guide time range for the PPPoE clients associated with the dynamic PPPoE subinterface column. For example, the following command configures a lockout time in the range 5–60 seconds for the PPPoE clients associated with the dynamic PPPoE subinterface column on the PPPoE major interface.
Page 583: Clearing The Lockout Condition For A Pppoe Client
Chapter 17: Configuring Dynamic Interfaces Use the lockout-time keyword to set the minimum lockout time and maximum lockout time, each of which can be in the range 1–86400 seconds (24 hours). Use the none keyword to disable lockout for the PPPoE clients associated with the dynamic PPPoE subinterface column on the static PPPoE major interface.
Page 584 JUNOSe 11.1.x Link Layer Configuration Guide Total clients in active lockout: 0 Total clients in lockout grace period: 0 Client Address Current Elapsed Next -------------- ------- ------- ---- 0090.1a10.165e To display the source MAC address when a subscriber is connected to the router through an available PPPoE session, use either the show pppoe interface lockout-time command or the show pppoe subinterface full command.
Page 585: Configuring Ipoa Dynamic Interfaces
Chapter 17: Configuring Dynamic Interfaces tenGigabitEthernet interfaceSpecifier Particular interface; format varies according to interface type; see Interface Types and Specifiers in JUNOSe Command Reference Guide for information macAddress Source MAC address of the PPPoE client, specified as a dotted triple of four-digit hexadecimal numbers Example host1#pppoe clear lockout interface gigabitEthernet 2/1.1 1011.22c2.333d There is no no version.
Page 586: Configuring A Dynamic Ipoa Interface
JUNOSe 11.1.x Link Layer Configuration Guide When you configure dynamic IPoA interfaces, you must assign a profile. Optionally, you can also assign a subscriber identification. Configuring a Dynamic IPoA Interface To configure dynamic IPoA interfaces: Configure a physical interface. host1(config)#interface atm 5/0 Configure an ATM subinterface.
Page 587 Chapter 17: Configuring Dynamic Interfaces aal5snap Specifies an LLC encapsulated circuit; LLC/SNAP header precedes the protocol datagram. aal5mux ip Specifies a VC multiplexed circuit. This option is used for IP only. Example host1(config-subif)#atm pvc 6 0 11 aal5autoconfig Use the no version to remove the specified PVC. See atm pvc.
Page 588 JUNOSe 11.1.x Link Layer Configuration Guide Use to select an ATM interface or ATM 1483 subinterface. For information about specifying the ATM interface or subinterface, see “interface atm” on page 532. Examples host1(config)#interface atm 5/0.1 host1(config)#interface atm 4/0/2.1 Use the no version to remove the interface or subinterface. See interface atm.
Page 589: Configuring Bridged Ethernet Dynamic Interfaces
Chapter 17: Configuring Dynamic Interfaces password-prefix Use the password as a prefix to the interface physical location. The router automatically postpends the physical location of the user to the password string. The password format is password.slot.port.vpi.vci. The resulting password string is then used to authenticate with the RADIUS server.
Page 590: Configuring A Dynamic Bridged Ethernet Interface
JUNOSe 11.1.x Link Layer Configuration Guide Figure 53: Dynamic Bridged Ethernet over Static ATM 1483 Interface Columns Configuring a Dynamic Bridged Ethernet Interface When you configure dynamic bridged Ethernet interfaces, you must assign a profile. You may optionally assign a subscriber identification. To configure dynamic bridged Ethernet interfaces: Configure a physical interface.
Page 591 Chapter 17: Configuring Dynamic Interfaces Assign a profile to match the encapsulation type of bridged Ethernet. host1(config-subif)#profile bridgedEthernet foo (Optional) Assign subscriber identification. host1(config-subif)#subscriber bridgedEthernet user charlie domain myisp password lucy (Optional) Verify your configuration. host1#show atm subinterface atm 2/0.1 atm pvc Use to configure a PVC on an ATM interface.
Page 592 JUNOSe 11.1.x Link Layer Configuration Guide Example 4 Either command reenables encapsulation type lockout for the bridged Ethernet encapsulation type using the default lockout time range host1(config-subif)#auto-configure bridgedEthernet host1(config-subif)#no auto-configure bridgedEthernet lockout-time Example 5 Permanently locks out the bridged Ethernet encapsulation type until the auto-configure bridgedEthernet command is issued host1(config-subif)#no auto-configure bridgedEthernet Use the no version to terminate detection of the specified encapsulation type...
Page 593: Configuring Subscriber Management For Ip Subscribers On Dynamic Bridged Ethernet Interfaces
Chapter 17: Configuring Dynamic Interfaces host1(config-subif)#subscriber bridgedEthernet user-prefix charlie domain myisp password-prefix lucy Use the no version to remove the subscriber. See subscriber. Configuring Subscriber Management for IP Subscribers on Dynamic Bridged Ethernet Interfaces You can use the JUNOSe subscriber management application to configure and manage IP subscribers associated with a dynamic bridged Ethernet over static ATM 1483 interface column, as described in “Authenticating Subscribers on Dynamic Bridged Ethernet over Static ATM Interfaces”...
Page 594: Equivalent Configuration Example Using Ip Subscriber Management
JUNOSe 11.1.x Link Layer Configuration Guide interface. This configuration method does not support running stateful SRP switchover on the router. The second part of the example shows the commands required to re-create this configuration using the IP subscriber management application. This configuration method uses the bridge1483 service-profile command to assign the specified IP service profile to the interface profile, and does support running stateful SRP switchover on the router.
Page 595: Configuring A Dynamic Interface From A Profile
Chapter 17: Configuring Dynamic Interfaces ! interface. Include the desired attributes (in this case, IGMP), the name of the ! route map used to configure the IP subscriber interface (optional), and the name ! of the IP service profile containing the authentication parameters for the dynamic ! bridged Ethernet interface.
Page 596: Profile Characteristics
JUNOSe 11.1.x Link Layer Configuration Guide IPv6, Multilink PPP, PPP, and PPPoE interfaces. The auto-configure command identifies the encapsulation type. For flexibility, the router provides the ability to configure an ATM 1483 subinterface with distinct profile assignments for each encapsulation type supported by the auto-configure command. In contrast to dynamic ATM 1483 subinterfaces, dynamic VLAN subinterfaces support recognition and creation of simultaneous IP and PPPoE upper dynamic interface types.
Page 597: Ipv6 Characteristics
Chapter 17: Configuring Dynamic Interfaces ignore-df-bit Specifies that the don’t-fragment bit is ignored inactivity-timer Configures an inactivity timer value for IP interfaces inspection Associates an inspection list to the interface for firewalling mtu Configures the MTU for a network nat Configures the interface as inside or outside for Network Address Translation (NAT) policy Assigns a policy to the ingress or egress of an interface redirects Enables transmission of ICMP redirect messages...
Page 598: L2Tp Characteristics
JUNOSe 11.1.x Link Layer Configuration Guide sa-validate Enables source address validation unnumbered Configures IPv6 on this interface without a specific address virtual-router Specifies a virtual router to which interfaces created by this profile attach L2TP Characteristics A profile can contain the following L2TP characteristic: policy Assigns an L2TP policy list to a profile MLPPP and PPP Characteristics A profile can contain one or more of the following MLPPP or PPP characteristics:...
Page 599: Pppoe Characteristics
Chapter 17: Configuring Dynamic Interfaces multilink multiclass Enables the creation of multilink classes on a multiclass MLPPP interface multilink multiclass fragmentation Enables fragmentation on a multiclass MLPPP interface multilink multiclass reassembly Enables reassembly on a multiclass MLPPP interface multilink multiclass traffic-class Configures mapping of QoS traffic classes to multilink classes on a multiclass MLPPP interface passive-mode Forces the interface into passive mode before LCP negotiation begins, for a period of one second to enable slow clients to start up and initiate...
Page 600: Working With Profiles
JUNOSe 11.1.x Link Layer Configuration Guide advisory-rx-speed Sets an advisory receive speed for VLAN subinterfaces advisory-tx-speed Sets an advisory connect speed for VLAN subinterfaces auto-configure Specifies the types of upper-interface encapsulations that are accepted or detected by the dynamic VLAN subinterface auto-configure agent-circuit-identifier Enables the creation of VLAN subinterfaces that are based on agent-circuit-identifier information description Assigns a description to VLAN subinterfaces that are created with...
Page 601: Configuring A Profile
Chapter 17: Configuring Dynamic Interfaces Figure 55: Assigning a Profile to a Static Interface Configuring a Profile You can create a profile by using CLI commands similar to those used to create the equivalent static interfaces. You can configure a profile for bridged Ethernet, IP, IPv6, MLPPP, PPP, PPPoE, or VLAN interfaces.
Page 602 JUNOSe 11.1.x Link Layer Configuration Guide Use to set the maximum allowable size, in bytes, of the MTU for bridged Ethernet interfaces. Specify an MTU size in the range 64–9180 bytes. Example host1(config-profile)#bridge1483 mtu 1684 Use the no version to restore the default MTU size for bridged Ethernet interfaces, 1518 bytes.
Page 603 Chapter 17: Configuring Dynamic Interfaces Use the no version with the exclude-primary keyword to specify that the primary interface is assigned to a subscriber. See ip auto-configure ip-subscriber. ip auto-detect ip-subscriber Use to enable packet detection on the router and specify that IP automatically detect packets that do not match any entries in the demultiplexer table.
Page 604 JUNOSe 11.1.x Link Layer Configuration Guide Use to force the router to ignore the DF bit if it is set in the IP packet header for packets on an interface. NOTE: You can also use RADIUS VSA [26-70] to configure the router’s DF bit support. The action configured by the RADIUS VSA takes precedence over the action configured by the ip ignore-df-bit command.
Page 605 Chapter 17: Configuring Dynamic Interfaces Use to assign the maximum transmission unit size sent on an IP interface. Example host1(config-profile)#ip mtu 1000 Use the no version to restore the default value, 0, which means that the router takes the value from a lower protocol layer. See ip mtu.
Page 606 JUNOSe 11.1.x Link Layer Configuration Guide Use the no version to delete J-Flow statistics from the profile. See ip route-cache flow sampled. ip route-map ip-subscriber Use to configure an interface for route-map processing and specify the route map that is applied to the IP interface subscriber. Example host1(config-profile)#ip route-map ip-subscriber chicagoRouteMap Use the no version to delete the route map.
Page 607 Chapter 17: Configuring Dynamic Interfaces ip virtual-router Use to assign a virtual router (VR) to a profile. Interfaces created by the profile are attached to this VR. If the VR specified in a profile with the ip virtual-router command differs from the VR provided by AAA, IP uses the VR provided by AAA when the dynamic IP upper-layer interface is created.
Page 608 JUNOSe 11.1.x Link Layer Configuration Guide NOTE: The HTTP local server must be configured and enabled in the virtual router for the interface on which you use the ipv6 http redirectUrl command. Otherwise, the URL redirect operation will fail. See Configuring the HTTP Server to Support Guided Entrance in the JUNOSe Broadband Access Configuration Guide Example host1(config-if)#ipv6 http redirectUrl http://ispsite.redirect.com...
Page 609 Chapter 17: Configuring Dynamic Interfaces Use to set the “managed address configuration” flag in IPv6 router advertisements. Example host1(config-profile)#ipv6 nd managed-config-flag Use the no version to clear the flag from IPv6 router advertisements. See ipv6 nd managed-config-flag. ipv6 nd other-config-flag Use to set the “other stateful configuration”...
Page 610 JUNOSe 11.1.x Link Layer Configuration Guide Use the no version to restore the default lifetime, 1800 seconds. See ipv6 nd ra-lifetime. ipv6 nd reachable-time Use to specify the amount of time, in milliseconds, that the E Series router can reach a remote IPv6 node after some reachability confirmation event has occurred.
Page 611 Chapter 17: Configuring Dynamic Interfaces Use the no version to disable source address validation. See ipv6 sa-validate. ipv6 unnumbered Use to enable or disable IPv6 processing on an interface without assigning an explicit IPv6 address to that interface. Example host1(config-profile)#ipv6 unnumbered loopback 0 Use the no version to remove the IPv6 address from the interface.
Page 612 JUNOSe 11.1.x Link Layer Configuration Guide with the same name is added, the interface cannot authenticate until the AAA profile is reassigned. NOTE: Although an AAA profile and an interface profile have similar functionality, they are not related and you need to treat them differently. Example host1(config-profile)#ppp aaa-profile westford24 Use the no version to remove the AAA profile assignment.
Page 613 Chapter 17: Configuring Dynamic Interfaces command specifies pap as the primary authentication protocol and chap as the alternate. host1(config-if)#ppp authentication pap chap The router requests the use of PAP as the authentication protocol (because it appears first in the command line). If the peer refuses to use PAP, the router requests the CHAP protocol.
Page 614 JUNOSe 11.1.x Link Layer Configuration Guide host1(config-profile)#ppp fragmentation 128 Use the no version to disable fragmentation on the link and restore the default fragment size, which is the link’s MTU. See ppp fragmentation. ppp hash-link-selection Use to enable use of a hash-based algorithm to select the link on which the router transmits non-best-effort (high-priority) packets, such as voice or video, on the dynamic MLPPP interfaces created by this profile.
Page 615 Chapter 17: Configuring Dynamic Interfaces Use the no version to disable initiation of IPv6. See ppp initiate-ipv6. ppp ipcp lockout Use to terminate invalid IPv4 subscribers and prevent additional IPCP negotiations. When Internet Protocol version 6 Control Protocol (IPv6CP) is active, this command enables unused IPv4 addresses, which are allocated for the IPv6 subscribers, to be available for the IPCP services for an internally defined time interval (10 seconds).
Page 616 JUNOSe 11.1.x Link Layer Configuration Guide previous keepalive timeout interval). If both sides are configured with keepalive, receipt of an LCP echo request by one end suppresses the transmission of an LCP echo request by that end. You can specify a timeout value in the range 30–64800 seconds. The default value is 30 seconds.
Page 617 Chapter 17: Configuring Dynamic Interfaces Use to cause the router to ignore a mismatch of the LCP peer magic number and retain the PPP connection when the peer has not negotiated an LCP magic number. For more information about using this command, see “Validation of LCP Peer Magic Number”...
Page 618 JUNOSe 11.1.x Link Layer Configuration Guide host1(config-profile)#ppp max-negotiations 15 Example 4 Restores the maximum number of LCP, IPCP, and IPv6CP renegotiation attempts to the default value, 30 host1(config-profile)#no ppp max-negotiations Use the no version to restore the default value, 30 renegotiation attempts. See ppp max-negotiations.
Page 619 Chapter 17: Configuring Dynamic Interfaces Use the no version to disable multiclass MLPPP or to restore the number of multilink classes to the default value, 1. See ppp multilink multiclass. ppp multilink multiclass fragmentation Use to enable fragmentation on a multilink class on a dynamic MLPPP interface. Example host1(config-profile)#ppp multilink multiclass fragmentation best-effort voice low-loss video...
Page 620 JUNOSe 11.1.x Link Layer Configuration Guide ppp peer Use to resolve conflicts when the router and the PPP peer system have the primary and secondary DNS and WINS addresses configured with different values. By default, the DNS and WINS addresses configured on the router take precedence.
Page 621 Chapter 17: Configuring Dynamic Interfaces Use to set up the router to offer to set up a session for the client, even if the router has insufficient resources to establish a session. This feature is disabled by default. Example host1(config-profile)#pppoe always-offer Use the no version to disable this feature.
Page 622 JUNOSe 11.1.x Link Layer Configuration Guide Use to set the MTU using a combination of lower layer restrictions and controls. You can specify an MTU greater than the current maximum permitted by RFC 2516, in the range 66–65535. You can use the use-lower-layer keyword to use the lower layer interface value minus any PPPoE overhead.
Page 623 Chapter 17: Configuring Dynamic Interfaces Use to specify the maximum number of PPPoE subinterfaces permitted on an interface, in the range 1–8000 (ERX routers) or 1–32,000 (E120 and E320 routers). On the ES2 10G ADV LM (E120 and E320 routers), you can have PPPoE subinterfaces in the range 1–32,000.
Page 624 JUNOSe 11.1.x Link Layer Configuration Guide profile Use to create a profile. You specify a profile name with up to 80 alphanumeric characters. Example host1(config)#profile foo Use the no version to remove a profile. See profile. svlan ethertype Use to assign an Ethertype value for the S-VLAN subinterface in a profile. Choose one of the following Ethertype values: 8100 Specifies Ethertype value 0x8100, as defined in IEEE Standard 802.1q 88a8 Specifies Ethertype value 0x88a8, as defined in draft IEEE Standard...
Page 625 Chapter 17: Configuring Dynamic Interfaces host1(config-profile)#vlan advisory-tx-speed 2000 Use the no version to restore the default behavior the Tx speed is not sent to the LNS. See vlan advisory-tx-speed. vlan auto-configure Use to specify the types of dynamic upper-interface encapsulations that are accepted or detected by a dynamic VLAN subinterface.
Page 626: Assigning A Profile To An Interface
JUNOSe 11.1.x Link Layer Configuration Guide Example host1(config-profile)#vlan policy input VlanPolicy33 statistics enabled preserve Use the no version to remove the association between a policy list and an interface or a profile. See vlan policy. vlan profile Use to add a nested profile assignment to a base profile for a dynamic VLAN subinterface.
Page 627 Chapter 17: Configuring Dynamic Interfaces For example, the following commands cause the router to use ProfileB when an IPoA packet is received, and to use ProfileA for any other received encapsulation that is autoconfigured. When you omit the keyword, it defaults to any. host1(config-subif)#profile any ProfileA host1(config-subif)#profile ip ProfileB To assign a profile to an interface:...
Page 628 JUNOSe 11.1.x Link Layer Configuration Guide Use to configure an ATM subinterface to support a dynamic interface. Specifies one or more types of dynamic encapsulation that the ATM 1483 subinterface detects and accepts. For detailed information about how to use this command, see “auto-configure” on page 531.
Page 629: Profile Configuration Examples
Chapter 17: Configuring Dynamic Interfaces Use to configure a local subscriber on the router to support authentication and configuration from RADIUS for a dynamic IPoA or bridged Ethernet interface. For detailed information about how to use this command, see “subscriber” on page 556.
Page 630: Scripts And Macros
JUNOSe 11.1.x Link Layer Configuration Guide host1(config-subif)#auto-configure ppp host1(config-subif)#auto-configure pppoe host1(config-subif)#exit This example also uses the three new profiles configured in the first three examples. It shows one profile being used for all encapsulations. The configuration of dynamic layers is the same regardless of incoming encapsulations detected by ATM.
Page 631: Monitoring Upper-Layer Dynamic Interfaces And Profiles
Chapter 17: Configuring Dynamic Interfaces configure the interface as dynamic and to specify configuration sources for the dynamic upper layers. These files can then be executed by the router as though the commands were entered at the terminal. Scripts You can create script files containing a series of CLI commands. The resulting script can be executed via the configure file command.
Page 632 JUNOSe 11.1.x Link Layer Configuration Guide OutBytes Number of bytes transmitted on this interface InErrors Number of incoming errors received on this interface OutErrors Number of outgoing errors on this interface InPacketDiscards Number of incoming packets discarded on this interface OutDiscards Number of outgoing packets discarded on this interface Example host1#show atm aal5 interface atm 3/0...
Page 633 Chapter 17: Configuring Dynamic Interfaces To display brief summary information for all ATM subinterfaces, or for ATM subinterfaces configured on a specified ATM physical interface, use the summary keyword. To display status information only for ATM subinterfaces with a specific operating status, use the status keyword with one of the following status values.
Page 634 JUNOSe 11.1.x Link Layer Configuration Guide VCI Virtual circuit (or channel) identifier Circuit Type Type of circuit: PVC Encap Administered encapsulation method based on what was configured with the atm pvc command MTU Maximum transmission unit size for the interface Status One of the following ATM 1483 subinterface states: absent Represents the notPresent state and indicates that, although the SRP detects the ATM 1483 subinterface, the module on which the...
Page 635 Chapter 17: Configuring Dynamic Interfaces Detected 1483 encapsulation If the encapsulation type is set to aal5autoconfig, displays the 1483 encapsulation type detected on the subinterface (displays AUTO until a packet is detected) Detected dynamic interface Type of dynamic upper interface detected during autoconfiguration: bridged Ethernet, IP, PPP, PPPoE, or (if no packet has been received) none Interface types in lockout Encapsulation types currently experiencing...
Page 636 JUNOSe 11.1.x Link Layer Configuration Guide ----------- -------- --- --- --- ----- ----- ---- ----------- ------- ATM 2/0.101 RFC-1483 101 0 101 PVC AUTO 9180 dormantLockout Static ATM 2/0.102 RFC-1483 102 0 102 PVC AUTO 9180 up Dynamic ATM 2/0.103 RFC-1483 103 0 103 PVC AUTO 9180 dormant...
Page 637 Chapter 17: Configuring Dynamic Interfaces OutBytes: InErrors: OutErrors: InPacketDiscards: InPacketsUnknownProtocol: 0 OutDiscards: 1 interface(s) found Example 5 Displays the current state of a specific ATM subinterface created on the PVC with the specified VPI and VCI values host1#show atm subinterface atm 0/0/0/101 Circuit Interface Interface...
Page 638 JUNOSe 11.1.x Link Layer Configuration Guide To display only a summary of all reserved VC ranges on the router, specify the reserved keyword with no other keywords. This includes VPI/VCI ranges reserved for use by dynamic ATM 1483 subinterfaces. Field descriptions Interface Interface identifier VPI Virtual path identifier VCI Virtual channel identifier...
Page 639 Chapter 17: Configuring Dynamic Interfaces Example 2 Displays all reserved VC ranges on the router host1#show atm vc reserved Reserved VCC ranges: Start Start End End Interface VPI VCI --------- ----- ----- --- --- ATM 2/0 2 102 ATM 2/0 3 303 2 reservation(s) found See show atm vc.
Page 640 JUNOSe 11.1.x Link Layer Configuration Guide Field descriptions Lockout Configuration (seconds) Encapsulation type lockout settings for the PPPoE client associated with the dynamic PPPoE subinterface column Min Minimum lockout time, in seconds Max Maximum lockout time, in seconds Total clients in active lockouts Number of PPPoE clients currently undergoing dynamic encapsulation type lockout Total clients in lockout grace period Number of PPPoE clients currently in a lockout grace period;...
Page 641 Chapter 17: Configuring Dynamic Interfaces Elapsed Time elapsed into the lockout time, in seconds; displays 0 (zero) if the PPPoE client is not undergoing lockout Next Lockout time that the router uses for the next lockout event, in seconds Example host1#show pppoe interface atm 3/0.101 lockout-time PPPoE interface ATM 3/0.101 Lockout Configuration (seconds): Min 5, Max 60...
Page 642 JUNOSe 11.1.x Link Layer Configuration Guide Profile Name of the profile that is displayed IP address IP address and subnet mask of the interface, or none if the interface is unnumbered Unnumbered interface Specifier for the unnumbered interface, or none if the interface is numbered Router Name of the virtual router (VR) assigned to the profile;...
Page 643 Chapter 17: Configuring Dynamic Interfaces the peer has not negotiated an LCP magic number: ignore (ignore the peer magic number mismatch and retain the PPP connection), or reject (router terminates the PPP connection if it detects a peer magic number mismatch) PPP Peer DNS Priority Enabled or disabled PPP Peer WINS Priority Enabled or disabled PPP Authentication Type of authentication configured: PAP, CHAP, or none...
Page 644 JUNOSe 11.1.x Link Layer Configuration Guide PPPoE Always-offer Router offers to set up a session for the client, even if the router has insufficient resources to establish a session; enabled or disabled PPPoE Remote-Circuit-Id The router captures and processes a vendor-specific tag containing a remote circuit ID transmitted from a digital subscriber line access multiplexer (DSLAM);...
Page 645 Chapter 17: Configuring Dynamic Interfaces ATM1483 Description Text description assigned to ATM 1483 subinterfaces that are created with this profile ATM1483 Advisory Rx Speed Configured receive speed, in Kbps, for the dynamic ATM 1483 subinterface. The E Series LAC sends this value to the LNS in the RX Connect-Speed AVP [38].
Page 646 JUNOSe 11.1.x Link Layer Configuration Guide IPv6 Router Router name or default IPv6 Src-Addr Validation Source-Address Validation; enabled or disabled IPv6 Administrative MTU MTU size IPv6 ND Enabled State of the Neighbor Discovery; enabled or disabled IPv6 ND ManagedConfig State of the Neighbor Discovery router advertisement managed flag;...
Page 647 Chapter 17: Configuring Dynamic Interfaces PPP IPCP Lockout : disabled PPP AAA Profile PPP Multilink Fragmentation : disabled PPP Multilink Fragment Size : (use MTU) PPP Multilink Reassembly : disabled PPP Multilink Mrru : (use MRU) PPP Hash Link Selection : disabled PPP Initiate IP : disabled...
Page 648 JUNOSe 11.1.x Link Layer Configuration Guide VLAN Description : testing VLAN IP Profile : ipProfile VLAN PPPoE Profile : pppoeProfile VLAN Service Profile : none assigned Bridged Ethernet Mtu : 1971 Bridged Ethernet Service Profile : eastServiceProfile Example 4 Displays profile configuration information related to IPv6 Neighbor Discovery router advertisement host1#show profile name ipv6Profile IPv6 Unnumbered interface...
Page 649 Chapter 17: Configuring Dynamic Interfaces Dynamic VLAN or S-VLAN subinterface was configured dynamically Auto configure interface(s) Types of dynamic upper interfaces configured with the auto-configure command: IP or PPPoE Detected dynamic interface Type of dynamic upper interface detected during autoconfiguration: IP, PPPoE, or (if no packet has been received) none Interface types in lockout Encapsulation types currently experiencing lockout: IP, PPPoE, or none...
Page 650 JUNOSe 11.1.x Link Layer Configuration Guide Errors Total number of errors in all transmitted packets; some packets might contain more than one error Discards Total number of discarded outgoing packets ARP Statistics Analysis of ARP traffic on this interface; In fields are for traffic received on the interface and Out fields are for traffic sent on the interface ARP requests Number of ARP requests...
Page 651: Troubleshooting Ppp And Pppoe Dynamic Interfaces
Chapter 17: Configuring Dynamic Interfaces host1#show vlan subinterface fastEthernet 4/6.1000053 Interface Status Svlan Id Vlan Id Ethertype Type ------------------------- ------ ---- -------- -------- --------- ------- FastEthernet 4/6.1000053 1526 100 0x9100 Dynamic Auto configure interface(s) : IP PPPoE Detected dynamic interface : PPPoE Interface types in lockout : none...
Page 652 JUNOSe 11.1.x Link Layer Configuration Guide system maximums, see JUNOSe Release Notes, Appendix A, System Maximums. For details about creating and using profiles, see “Configuring a Dynamic Interface from a Profile” on page 563. Access Privileged Exec mode at privilege level 5 or higher. host1>enable 5 Password: ********* host1#...
Page 653 1 and 0. 10 The user can execute all commands except support commands, which may be provided by Juniper Networks Customer Service. 15 The user can execute support commands. Set a password for this mode by using either the enable password or the enable secret command in Global Configuration mode.
Page 654 JUNOSe 11.1.x Link Layer Configuration Guide Example 1 Facilitates debugging for the ppp encapsulation type by swapping profile pppConfig for profile pppLogConfig, which includes PPP packet–logging attributes host1#profile-reassign atm 2/0.101 ppp pppLogConfig WARNING: Execution of this command will cause all dynamic interfaces over atm 2/0.101 to be torn-down.
Page 655: Chapter 18 Configuring Dynamic Interfaces Using Bulk Configuration
Chapter 18 Configuring Dynamic Interfaces Using Bulk Configuration This chapter explains dynamic interfaces and describes the procedures for configuring them on E Series routers. This chapter contains the following sections: Overview on page 623 Platform Considerations on page 627 References on page 628 Configuring ATM 1483 Dynamic Subinterfaces on page 628 Configuring VLAN Dynamic Subinterfaces on page 658 Monitoring Dynamic Interfaces and Profiles on page 689...
Page 656: Bulk Dynamic Interface Configurations
JUNOSe 11.1.x Link Layer Configuration Guide Bulk Dynamic Interface Configurations E Series routers support dynamic interfaces on two types of static interfaces: ATM and VLAN. This chapter provides configuration information for ATM and then for VLANs. E Series routers support dynamic ATM 1483 subinterfaces over static ATM interfaces. E Series routers support the following types of dynamic interfaces over VLAN major interfaces: Dynamic VLAN subinterface over static VLAN major interface...
Page 657: Atm Oversubscription For Bulk-Configured Vc Ranges
Chapter 18: Configuring Dynamic Interfaces Using Bulk Configuration interface column. After you define the static lower layers, you assign a profile to the highest static layer of the interface column. When a dynamic interface is configured, the configuration data received from the RADIUS authentication server typically overrides configuration data obtained from a profile.
Page 658: Combination Of Static Atm 1483 Subinterfaces And Bulk-Configured Vc Ranges
JUNOSe 11.1.x Link Layer Configuration Guide At least one currently active subscriber logs out, which causes the router to tear down the dynamic interface column for that subscriber. Although the dynamic ATM 1483 subinterface and its associated VC remain configured on the router, the subinterface becomes inactive and can be replaced by one of the bulk-configured VCs waiting to become active.
Page 659: Platform Considerations
Chapter 18: Configuring Dynamic Interfaces Using Bulk Configuration Because the 4000 static ATM 1483 subinterfaces are already active, the router enables only 4000 of the bulk-configured VCs to create dynamic ATM 1483 subinterface columns and become active, yielding a combined total of 8000 active subinterfaces on the line module.
Page 660: References
JUNOSe 11.1.x Link Layer Configuration Guide 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.
Page 661: About Configuring Dynamic Atm 1483 Subinterfaces
Chapter 18: Configuring Dynamic Interfaces Using Bulk Configuration Figure 56: Dynamic Interface Columns over Dynamic ATM 1483 Subinterfaces About Configuring Dynamic ATM 1483 Subinterfaces This section introduces important concepts that you need to understand before you configure dynamic ATM 1483 subinterfaces. Overview and Benefits When you use dynamic interfaces over static ATM 1483 subinterfaces, you must configure the ATM interface and each ATM 1483 subinterface, including the ATM...
Page 662: Atm 1483 Base Profiles
JUNOSe 11.1.x Link Layer Configuration Guide Dynamic ATM 1483 subinterfaces function identically to static ATM 1483 subinterfaces, except for the manner in which they are created and configured. The creation of dynamic upper-layer encapsulation types is essentially the same regardless of whether they are configured over static ATM 1483 subinterfaces or dynamic ATM 1483 subinterfaces.
Page 663: Additional Profile Characteristics For Upper Interfaces
Chapter 18: Configuring Dynamic Interfaces Using Bulk Configuration each upper-interface encapsulation type, or you can create a single profile that includes attributes for multiple encapsulation types. For example, the following commands create a base profile named atm1483BaseProfile with two nested profile assignments. The first nested profile assignment references an IP profile named atm1483ProfileIp, and the second nested profile assignment references a PPP profile named atm1483ProfilePpp.
Page 664: Bulk Configuration And Vc Classes
JUNOSe 11.1.x Link Layer Configuration Guide bulk-config command. For example, the following commands create an ATM 1483 bulk configuration named myBulkConfig on the specified ATM AAL5 interface. host1(config)#interface atm 2/0 host1(config-if)#atm bulk-config myBulkConfig vc-range 0 3 101 1100 vc-range 4 7 201 700 In this example, the atm bulk-config command configures a VC range made up of two VC subranges.
Page 665: Bulk Configuration And Cac
Chapter 18: Configuring Dynamic Interfaces Using Bulk Configuration To assign a VC class to a bulk-configured VC range, you use the atm class-vc command from Profile Configuration mode to associate the VC class to a base profile. 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 base profile.
Page 666: Overriding Base Profile Assignments
JUNOSe 11.1.x Link Layer Configuration Guide Overriding Base Profile Assignments You can use the profile atm1483 bulk-config-name pvc command to assign an overriding profile to a single ATM PVC that exists within a bulk-configured VC subrange. The VC subrange that encompasses the PVC must have been previously configured with the atm bulk-config command for use by a dynamic ATM 1483 subinterface.
Page 667: Terminating Stale Pppoa Subscribers And Restarting Lcp Negotiations
Chapter 18: Configuring Dynamic Interfaces Using Bulk Configuration services over MPLS with Martini encapsulation to forward the traffic from the selected circuits. You must create the interface stack for ATM layer 2 statically and define the configuration parameters individually on a per-interface basis. The following rules apply when you configure either a static ATM interface within an existing bulk-configured VC subrange, or a subrange that includes an existing static ATM interface:...
Page 668: Authenticating Subscribers On Dynamic Bridged Ethernet Over Dynamic Atm Interfaces
JUNOSe 11.1.x Link Layer Configuration Guide The implementation of this feature for dynamic ATM 1483 subinterfaces is almost identical to the implementation for static ATM 1483 subinterfaces, with the following difference: For static ATM 1483 subinterfaces, the restart of LCP negotiations by the CPE causes the router to re-create the dynamic PPP and IP upper-layer interfaces above the static ATM 1483 subinterface.
Page 669: Configuring A Dynamic Atm 1483 Subinterface
Chapter 18: Configuring Dynamic Interfaces Using Bulk Configuration Configuration Method Using Subscriber Management Application You can use the JUNOSe subscriber management application to configure and manage IP subscribers associated with a dynamic bridged Ethernet interface column. The subscriber management application uses an IP service profile to manage and authenticate IP subscribers with RADIUS.
Page 670 JUNOSe 11.1.x Link Layer Configuration Guide (Optional) Configure profiles containing characteristics for the dynamic upper-interface encapsulation types to be created over the dynamic ATM 1483 subinterface. These profiles are referenced in the base profile for the dynamic ATM subinterface as nested profile assignments. For detailed instructions on creating profiles, see “Configuring a Dynamic Interface from a Profile”...
Page 671 Chapter 18: Configuring Dynamic Interfaces Using Bulk Configuration For example, the following commands configure nested profile assignments for the PPP and IP upper-interface encapsulation types, and define additional attributes for the PPPoE upper-interface encapsulation type. host1(config-profile)#atm atm1483 profile ppp myPppProfile host1(config-profile)#atm atm1483 profile ip myIpProfile host1(config-profile)#pppoe duplicate-protection host1(config-profile)#pppoe sessions 3000...
Page 672 JUNOSe 11.1.x Link Layer Configuration Guide Use to set an advisory receive speed for ATM 1483 subinterfaces that are created with the profile that you are configuring. 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.
Page 673 Chapter 18: Configuring Dynamic Interfaces Using Bulk Configuration Example host1(config-profile)#atm atm1483 profile pppoe atm1483ProfilePppoe Use the no version to remove the profile assignment for the upper-interface encapsulation type. See atm atm1483 profile. atm atm1483 subscriber Use to configure a local subscriber for a dynamic upper-interface encapsulation type configured over a dynamic ATM 1483 subinterface.
Page 674 JUNOSe 11.1.x Link Layer Configuration Guide Example 1 host1(config-profile)#atm atm1483 subscriber ip user-prefix boston01 domain myisp password-prefix abc123 Example 2 host1(config-subif)#atm atm1483 subscriber bridgedEthernet user westford003 domain acmecorp.east password xyz123 Use the no version to remove the subscriber. See atm atm1483 subscriber. atm bulk-config Use to create a bulk-configured VC range on a static ATM AAL5 interface for use by a dynamic ATM 1483 subinterface.
Page 675 Chapter 18: Configuring Dynamic Interfaces Using Bulk Configuration shutdown” on page 655 to remove dynamic ATM 1483 interfaces created within a subrange. Removal of a subrange automatically results in the removal of all overriding profile assignments on that subrange. You can create a bulk-configured VC subrange that includes the VPI and VCI addresses belonging to an existing ATM PVC on a static ATM interface.
Page 676 JUNOSe 11.1.x Link Layer Configuration Guide Use the no version to remove the VC class association with the base profile. See atm class-vc. atm pvc Use to apply encapsulation, traffic-shaping, and OAM parameters to the range of ATM PVCs configured on an ATM AAL5 interface for use by a dynamic ATM 1483 subinterface.
Page 677 Chapter 18: Configuring Dynamic Interfaces Using Bulk Configuration Use the no version to terminate autodetection of the ATM 1483 encapsulation type. See auto-configure atm1483. interface atm Use to select an ATM interface or ATM 1483 subinterface. To specify an ATM interface for ERX7xx models, ERX14xx models, and ERX310 router, use the slot/port.[subinterface ] format.
Page 678: Configuring Overriding Profile Assignments
JUNOSe 11.1.x Link Layer Configuration Guide NOTE: If VC ranges are configured for the dynamic ATM 1483 subinterface associated with the base profile you want to delete, you must use the no atm bulk-config command to remove the VC ranges before you can use the no profile command to remove the associated base profile.
Page 679 Chapter 18: Configuring Dynamic Interfaces Using Bulk Configuration Overriding profile for an ATM PVC within a bulk-configured VC subrange For information about configuring profiles, see “Configuring a Dynamic Interface from a Profile” on page 563 in “Configuring Dynamic Interfaces” on page 515. Create a bulk-configured range of VCs on a static ATM AAL5 interface.
Page 680: Removing An Overriding Profile Assignment From An Atm Pvc
JUNOSe 11.1.x Link Layer Configuration Guide For more information about using this command, see “show atm bulk-config” on page 690. Removing an Overriding Profile Assignment from an ATM PVC After you troubleshoot the ATM 1483 dynamic subinterface column created on the specified PVC, make sure that you remove the overriding profile assignment to restore the original base profile assignment.
Page 681 Chapter 18: Configuring Dynamic Interfaces Using Bulk Configuration When you issue the no atm bulk-config command to remove a particular VC subrange in a bulk-configured VC range, the router also removes any overriding profile assignments for PVCs within that VC subrange. However, overriding profile assignments for PVCs within other VC subranges in the VC range remain intact.
Page 682 JUNOSe 11.1.x Link Layer Configuration Guide Example host1(config-if)#profile atm1483 bulk-config-name test1 test1BaseProfile Use the no version to remove the base profile assignment. See profile atm1483 bulk-config-name. profile atm1483 bulk-config-name pvc Use to assign an overriding profile to a single ATM PVC that exists within a bulk-configured VC subrange.
Page 683: Changing Vc Subranges
Chapter 18: Configuring Dynamic Interfaces Using Bulk Configuration Changing VC Subranges Changing VC subranges within a bulk-configured VC range includes the following tasks: Adding new VC subranges to an existing VC range Removing VC subranges from an existing VC range Modifying a VC subrange by shortening or expanding the subrange values Merging multiple VC subranges belonging to an existing VC range Changing the administrative state of VC subranges...
Page 684: Removing Vc Subranges
JUNOSe 11.1.x Link Layer Configuration Guide You can create a placeholder VC range by specifying a VC range name without specifying any subrange parameters. This VC range has no circuit reservation, but you can assign a profile to it, and add subranges later as desired. The following commands illustrate this approach.
Page 685: Merging Vc Subranges
Chapter 18: Configuring Dynamic Interfaces Using Bulk Configuration The router retains any overriding profiles assigned to a subrange after you modify the subrange if the override assignment still falls within the modified subrange. If the assignment falls outside of the newly modified subrange, the router drops the overriding profile assignment.
Page 686: Changing The Administrative State Of Vc Subranges
JUNOSe 11.1.x Link Layer Configuration Guide Changing the Administrative State of VC Subranges VC subranges have an administrative state that enables you to remove dynamic ATM 1483 subinterfaces on various subranges that belong to a single VC range. This functionality is important because subrange removal requires that no dynamic ATM 1483 subinterfaces exist for any circuit on that subrange.
Page 687 Chapter 18: Configuring Dynamic Interfaces Using Bulk Configuration Use to create a bulk-configured VC range on a static ATM AAL5 interface for use by a dynamic ATM 1483 subinterface. For detailed information about how to use this command, see “atm bulk-config” on page 642.
Page 688: Configuring Static Atm Interfaces Within Vc Subranges
JUNOSe 11.1.x Link Layer Configuration Guide No dynamic ATM 1483 subinterfaces can subsequently be created for the subrange until you restore the administrative state to enabled by using the no atm bulk-config shutdown command. Example host1(config-if)#atm bulk-config test shutdown vc-range 2 2 201 250 Use the no version to enable the specified VC subrange or all subranges in a VC range.
Page 689: Creating Vc Subranges That Include Static Atm Interfaces
Chapter 18: Configuring Dynamic Interfaces Using Bulk Configuration Creating VC Subranges That Include Static ATM Interfaces You can configure a bulk-configured VC subrange that includes the VPI and VCI addresses belonging to an existing ATM PVC on a static ATM interface. This example is essentially the reverse of the procedure in “Creating Static ATM Interfaces Within VC Subranges”...
Page 690: Configuring Vlan Dynamic Subinterfaces
JUNOSe 11.1.x Link Layer Configuration Guide Use to configure a PVC on an ATM interface. Specify the VCD, the VPI, the VCI, and the encapsulation type. For more information about these parameters, see “Creating a Basic Configuration” on page 22 in “Configuring ATM” on page 3. You can create a PVC within an existing bulk-configured VC subrange, or a bulk-configured VC subrange that includes the VPI and VCI values of an existing PVC.
Page 691: Figure 57: Dynamic Interface Columns Over Dynamic Vlan Subinterfaces
Chapter 18: Configuring Dynamic Interfaces Using Bulk Configuration When you configure the dynamic VLAN subinterface, you can enable autodetection and dynamic creation of the following upper-layer encapsulation types: PPPoE NOTE: Unlike ATM, which supports dynamic upper interfaces over static ATM 1483 subinterfaces, you must configure a dynamic VLAN subinterface to enable autodetection and dynamic creation of IP and PPPoE interfaces.
Page 692: About Configuring Dynamic Vlan Subinterfaces
JUNOSe 11.1.x Link Layer Configuration Guide About Configuring Dynamic VLAN Subinterfaces This section introduces important concepts that you need to understand before you configure dynamic VLAN subinterfaces. Overview and Benefits When you configure dynamic VLAN subinterfaces over static VLAN major interfaces, you must configure the VLAN major interface, including the attributes of the VLAN major interface.
Page 693: Vlan Base Profiles
Chapter 18: Configuring Dynamic Interfaces Using Bulk Configuration Figure 59: Dynamic VLAN Subinterfaces for Subscribers For example, if an S-VLAN is assigned at the DSLAM, and each DSLAM subscriber at the DSLAM is assigned a unique VLAN ID, the JUNOSe software dynamically constructs a VLAN-based interface column using that S-VLAN/VLAN ID pair when the subscriber logs in.
Page 694: Nested Profile Assignments
JUNOSe 11.1.x Link Layer Configuration Guide auto-configure agent-circuit-identifier Enables the creation of VLAN subinterfaces that are based on agent-circuit-identifier information. For information, see “vlan auto-configure agent-circuit-identifier” on page 677. description Assigns a description to VLAN subinterfaces that are created with this profile.
Page 695: Additional Profile Characteristics For Upper Interfaces
Chapter 18: Configuring Dynamic Interfaces Using Bulk Configuration Additional Profile Characteristics for Upper Interfaces In addition to VLAN attributes and nested profile assignments, the base profile for a dynamic VLAN subinterface can also include individual characteristics for several upper-interface encapsulation types, provided that no nested profile assignment for the specified encapsulation type is in the base profile.
Page 696: Bulk Configuration Of Vlan Ranges Using Agent-Circuit-Identifier Information
JUNOSe 11.1.x Link Layer Configuration Guide Bulk Configuration of VLAN Ranges Using Agent-Circuit-Identifier Information Using bulk configuration to create S-VLAN IDs based on agent-circuit-identifier information is similar to the process of creating a bulk-configured VLAN range that is not based on agent-circuit-identifier information. However, when you issue the vlan bulk-config command with the svlan-range keyword to specify the S-VLAN ID range, you then specify the agent-circuit-identifier keyword instead of a VLAN ID range.
Page 697: Dynamic Interface Creation
Chapter 18: Configuring Dynamic Interfaces Using Bulk Configuration Subscriber packets received from the DSLAM are double-tagged with both an S-VLAN ID and a VLAN ID The DSL Forum Technical Report (TR)-101 Migration to Ethernet-Based DSL Aggregation (April 2006) refers to the behavior of these configurations as the 1:1 forwarding model because there is a one-to-one correspondence between an individual subscriber and the VLAN encapsulation.
Page 698: Overriding Base Profile Assignments
JUNOSe 11.1.x Link Layer Configuration Guide As a final step, you must issue “auto-configure vlan” on page 672 . This command configures the VLAN major interface to support autodetection of the VLAN dynamic encapsulation type. When the router receives an incoming data packet on a circuit, it dynamically creates the VLAN subinterface, using the attributes specified in the base profile.
Page 699: Static Vlan Subinterfaces Within Vlan Subranges
Chapter 18: Configuring Dynamic Interfaces Using Bulk Configuration Static VLAN Subinterfaces Within VLAN Subranges You can configure a static VLAN subinterface with a single-tagged VLAN ID or double-tagged S-VLAN ID, or an S-VLAN ID with agent-circuit-identifier information that falls within an existing bulk-configured VLAN subrange. Conversely, you can also create a bulk-configured VLAN subrange that includes the single-tagged VLAN ID or double-tagged S-VLAN ID on a static VLAN subinterface.
Page 700 JUNOSe 11.1.x Link Layer Configuration Guide Configure profiles containing characteristics for the dynamic upper-interface encapsulation types to be created over the dynamic VLAN subinterface. These profiles are referenced in the base profile for the dynamic VLAN subinterface as nested profile assignments. For detailed instructions on creating profiles, see “Configuring a Dynamic Interface from a Profile”...
Page 701: Configuring Dynamic Vlan Subinterfaces Based On Agent Circuit Identifier Information
Chapter 18: Configuring Dynamic Interfaces Using Bulk Configuration NOTE: For information about the maximum number of VLAN bulk configurations supported per chassis, see JUNOSe Release Notes, Appendix A, System Maximums. For example, the following command creates a VLAN range named myBulkConfig made up of two VLAN subranges.
Page 702: Configuring Overriding Profile Assignments For Vlan Major Interfaces
JUNOSe 11.1.x Link Layer Configuration Guide Configure the VLAN major interface. host1(config)#interface gigabitEthernet 5/0 host1(config-if)#encapsulation vlan On the VLAN major interface, configure a VLAN range that is based on agent-circuit-identifier information, and assign a name to this range. host1(config-if)#vlan bulk-config myNewBulkConfig svlan-range 50 100 agent-circuit-identifier Assign the base profile configured for the VLAN subinterface to the VLAN range configured on the major VLAN interface.
Page 703: Removing An Overriding Profile Assignment From A Vlan
Chapter 18: Configuring Dynamic Interfaces Using Bulk Configuration host1(config-if)#profile vlan bulk-config myBulkConfig vlanBaseProfile Assign the previously configured overriding profile to a single VLAN ID or double-tagged S-VLAN ID within the bulk-configured VLAN subrange. The following command assigns the overriding profile overrideVoiceSubscriber to the VLAN ID 202.
Page 704: Removing Overriding Profile Assignments From A Vlan Range Or Vlan Subrange
JUNOSe 11.1.x Link Layer Configuration Guide host1(config-if)#no profile vlan override bulk-config-name myBulkConfig vlan 202 overrideVoiceSubscriber Select the dynamic VLAN subinterface on which the VLAN dynamic subinterface column resides. host1(config)#interface gigabitEthernet 4/0.101 Use the shutdown command to disable the dynamic VLAN subinterface. The shutdown command deletes the VLAN dynamic subinterface column and removes the dynamic VLAN subinterface.
Page 705 Chapter 18: Configuring Dynamic Interfaces Using Bulk Configuration By default, all valid VLAN IDs and S-VLAN IDs are accepted. Example host1(config-if)#auto-configure vlan Use the no version to terminate autodetection of the VLAN dynamic interface type. See auto-configure vlan. encapsulation vlan Use to configure VLAN as the encapsulation method for the interface.
Page 706 JUNOSe 11.1.x Link Layer Configuration Guide Use the no version to remove IP from an interface. You must issue the no version from the highest level down; you cannot remove an interface or subinterface if the one above it still exists. See interface gigabitEthernet.
Page 707 Chapter 18: Configuring Dynamic Interfaces Using Bulk Configuration Example 1 Assigns an overriding profile (test1OverridingProfile) to the dynamic VLAN subinterface with VLAN ID 202 host1(config-if)#profile vlan override bulk-config vlan 202 test1OverridingProfile Example 2 Assigns an overriding profile (test1DebugProfile) to the S-VLAN subinterface with S-VLAN ID 100 within the VLAN subinterface with V-LAN ID host1(config-if)#profile vlan override bulk-config svlan 100 202 test1OverridingProfile...
Page 708 JUNOSe 11.1.x Link Layer Configuration Guide host1(config-profile)#svlan ethertype 8100 host1(config-profile)#svlan ethertype autoconfig Use the no version to restore the default value, autoconfig. See svlan ethertype. vlan advisory-rx-speed Use to set an advisory receive speed for VLAN subinterfaces that are created with the profile you are configuring.
Page 709 Chapter 18: Configuring Dynamic Interfaces Using Bulk Configuration host1(config-profile)#vlan auto-configure ip Use the no version to terminate detection of the specified encapsulation type. See vlan auto-configure. vlan auto-configure agent-circuit-identifier Use to create a VLAN subinterface that is based on the agent-circuit-id information in the option 82 field of DHCP messages or in the DSL Forum VSA 26-1 of PPPoE PADR and PADI packets.
Page 710 JUNOSe 11.1.x Link Layer Configuration Guide You can create a placeholder VLAN range by issuing the vlan bulk-config command without specifying any subranges. You can assign a profile to this placeholder and add subranges to it later. You can add and remove individual VLAN subranges. You cannot remove a VLAN subrange if any dynamic VLAN subinterfaces currently exist within the subrange.
Page 711 Chapter 18: Configuring Dynamic Interfaces Using Bulk Configuration vlan policy Use to assign a VLAN policy list to an interface. Use the input or output keyword to assign the policy list to the ingress or egress of the interface. You can enable or disable the recording of routing statistics for bytes and packets affected by the policy.
Page 712: Changing Vlan Subranges
JUNOSe 11.1.x Link Layer Configuration Guide Use the no version to remove the association between a policy list and an interface or a profile. See vlan policy. vlan profile Use to add a nested profile assignment to a base profile for a dynamic VLAN subinterface.
Page 713: Adding Vlan Subranges
Chapter 18: Configuring Dynamic Interfaces Using Bulk Configuration Adding VLAN Subranges You can add a new VLAN subrange to an existing VLAN range only when the new subrange does not overlap with any existing subrange. Any overlap causes the addition to fail.
Page 714: Modifying Vlan Subranges
JUNOSe 11.1.x Link Layer Configuration Guide a subrange automatically results in the removal of all overriding profile assignments on that subrange. You can remove only a single specific VLAN subrange at a time. The following example specifies the original VLAN subranges. host1(config-if)#vlan bulk-config test svlan-range 101 150 1 1 svlan-range 201 250 2 2 svlan-range 501 550 5 5 svlan-range 301 350 3 3 The following command removes one subrange encompassing S-VLAN IDs 101–150...
Page 715: Merging Vlan Subranges
Chapter 18: Configuring Dynamic Interfaces Using Bulk Configuration host1(config-if)#vlan bulk-config test modify svlan-range 501 550 agent-circuit-identifier The router retains any overriding profiles assigned to a subrange after you modify the subrange if the override assignment still falls within the modified subrange. If the assignment falls outside of the newly modified subrange, the router drops the overriding profile assignment.
Page 716: Changing The Administrative State Of Vlan Subranges
JUNOSe 11.1.x Link Layer Configuration Guide If you merge subranges by using SNMP, the new merged subrange takes the lowest instance value of the incorporated subranges. For example, if a VLAN range has three subranges with instance values of 2, 4, and 5 and the subranges with instance values of 2 and 5 are merged, the new merged subrange has an instance value of 2.
Page 717 Chapter 18: Configuring Dynamic Interfaces Using Bulk Configuration You can change the administrative state of all subranges in a bulk-configured VLAN range at the same time by issuing the command without specifying any subranges. When you shut down a named bulk configuration, all VLAN ranges belonging to that bulk configuration, including those based on double-tagged S-VLANs or agent-circuit-identifier information, are disabled.
Page 718: Configuring Static Vlan Subinterfaces Within Vlan Subranges
JUNOSe 11.1.x Link Layer Configuration Guide Example host1(config-if)#vlan bulk-config test modify svlan-range 200 250 1 3 There is no no version. See vlan bulk-config modify. vlan bulk-config shutdown Use to administratively disable (shut down) a specified VLAN subrange or all subranges in a VLAN range.
Page 719: Creating Vlan Subranges That Include Static Vlan Subinterfaces
Chapter 18: Configuring Dynamic Interfaces Using Bulk Configuration To create a static VLAN subinterface within a VLAN subrange: Create the VLAN major interface. host1(config)#interface gigabitEthernet 0/0 host1(config-if)#encapsulation vlan Create a bulk-configured VLAN range that includes one or more VLAN subranges. host1(config-if)#vlan bulk-config test vlan-range 200 250 Create a static VLAN subinterface by adding a subinterface number to the interface identification command.
Page 720 JUNOSe 11.1.x Link Layer Configuration Guide host1(config-if)#vlan id 201 mac-address 0090.1a01.1234 Create a bulk-configured VLAN range that includes the VLAN ID of the previously configured VLAN. In this example, the VLAN range 100–250 includes VLAN ID 201. host1(config)#interface gigabitEthernet 3/1 host1(config-if)#vlan bulk-config test2 vlan-range 100 250 To fully configure the VLAN subinterface, assign an IP address or make it unnumbered.
Page 721: Monitoring Dynamic Interfaces And Profiles
Chapter 18: Configuring Dynamic Interfaces Using Bulk Configuration You must specify an interface location, which is the identifier of another interface on which the router has an assigned IP address. This interface cannot be another unnumbered interface. Examples host1(config-if)#ip unnumbered fastEthernet 3/0 host1(config-if)#ip unnumbered loopback 10 Use the no version to disable IP processing on the interface.
Page 722 JUNOSe 11.1.x Link Layer Configuration Guide SNMP trap link-status Whether SNMP link status traps are enabled or disabled on the ATM AAL5 interface Auto configure ATM 1483 status Whether the autoconfiguration feature for a dynamic ATM 1483 subinterface configured over the ATM AAL5 interface is enabled or disabled InPackets Number of packets received on this interface InBytes Number of bytes received on this interface...
Page 723 Chapter 18: Configuring Dynamic Interfaces Using Bulk Configuration To display information only about overriding profile assignments configured for specific ATM PVCs within bulk-configured VC subranges, use the command with the override keyword. When you specify the override keyword, the command does not display information about base profile assignments.
Page 724 JUNOSe 11.1.x Link Layer Configuration Guide named atm1483BaseProfile assigned, and has an overriding profile named overrideProfile1 assigned to two ATM PVCs within the VC subrange. The VC range named test2 is a placeholder range that has no VC subranges configured and no base profile assigned.
Page 725 Chapter 18: Configuring Dynamic Interfaces Using Bulk Configuration Profile override(s): Bulk Config Interface Name VPI VCI Assigned Profile Status ------------ ------ --- --- ---------------- ------ ATM AAL5 3/0 test 1 151 overrideProfile1 Active ATM AAL5 3/0 test 1 161 overrideProfile1 Active 2 profile override(s) found Example 4 Displays information only about overriding profile assignments for all bulk-configured VC ranges on the router...
Page 726 JUNOSe 11.1.x Link Layer Configuration Guide 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).
Page 727 Chapter 18: Configuring Dynamic Interfaces Using Bulk Configuration Interface Interface identifier ATM-Prot One of the following ATM protocol types: RFC-1483 Multiprotocol encapsulation over AAL5 NBMA Nonbroadcast multiaccess interface ATM/MPLS Local ATM passthrough interface VCD Virtual circuit descriptor VPI Virtual path identifier VCI Virtual circuit (or channel) identifier Circuit Type Type of circuit: PVC Encap Administered encapsulation method based on what was configured...
Page 728 JUNOSe 11.1.x Link Layer Configuration Guide Auto configure status Setting of the autoconfiguration feature dynamic Autodetection is on; the router automatically detects the next upper interface static Autodetection is off Auto configure interface(s) Types of dynamic upper interfaces configured with the auto-configure command: bridged Ethernet, IP, PPP, or PPPoE Detected 1483 encapsulation If the encapsulation type is set to aal5autoconfig, displays the 1483 encapsulation type detected on the subinterface (displays AUTO until a packet is detected)
Page 729 Chapter 18: Configuring Dynamic Interfaces Using Bulk Configuration InPacketsUnknownProtocol Number of incoming packets with an unknown protocol type OutDiscards Number of outgoing packets discarded on this interface Example 1 Displays the current state of all ATM subinterfaces host1#show atm subinterface Circuit Interface Interface...
Page 730 JUNOSe 11.1.x Link Layer Configuration Guide BridgedEnet subscriber info Username: elaine@jpeterman.com Password: putty Authenticate: enabled SNMP trap link-status: disabled InPackets: InBytes: 1904 OutPackets: OutBytes: InErrors: OutErrors: InPacketDiscards: InPacketsUnknownProtocol: 0 OutDiscards: 1 interface(s) found Example 5 Displays the current state of a specific ATM subinterface created on the PVC with the specified VPI and VCI values host1#show atm subinterface atm 0/0/0/101 Circuit...
Page 731 Chapter 18: Configuring Dynamic Interfaces Using Bulk Configuration Use to display a summary of all configured ATM VCs and reserved VC ranges. You can specify one or more of the following keywords individually or in combination: vpi Displays VCs on a specific VPI category Displays VCs that have a specific service category status Displays VCs with a certain status To display only a summary of all reserved VC ranges on the router, specify the...
Page 732 JUNOSe 11.1.x Link Layer Configuration Guide ATM 3/0.8100 1 8100 8100 PVC SNAP 0 DOWN 8000 circuit(s) found Reserved VCC ranges: Start Start End End Interface VPI VCI --------- ----- ----- --- --- ATM 2/0 2 102 ATM 2/0 3 303 2 reservation(s) found Example 2 Displays all reserved VC ranges on the router host1#show atm vc reserved...
Page 733 Chapter 18: Configuring Dynamic Interfaces Using Bulk Configuration Use to display summary information about the encapsulation type lockout parameters configured for PPPoE clients on a dynamic PPPoE subinterface column. The following field descriptions and example include only the portion of the show pppoe interface command display relevant to lockout configuration for PPPoE clients.
Page 734 JUNOSe 11.1.x Link Layer Configuration Guide period, see “Guidelines for Configuring Encapsulation Type Lockout” on page 527 in “Configuring Dynamic Interfaces” on page 515 Client Address Source MAC address of the PPPoE client Current Current lockout time, in seconds; displays 0 (zero) if the PPPoE client is not undergoing lockout Elapsed Time elapsed into the lockout time, in seconds;...
Page 735 Chapter 18: Configuring Dynamic Interfaces Using Bulk Configuration show profile Use to display information about profiles. To display information about a specific profile, use the name keyword. To display a list of profiles configured on the router, use the brief keyword. Field descriptions Profile Name of the profile that is displayed IP address IP address and subnet mask of the interface, or none if the...
Page 736 JUNOSe 11.1.x Link Layer Configuration Guide Output policy Name of output policy and whether statistics are enabled or disabled PPP Keepalive PPP keepalive period, in seconds PPP Magic Number Enabled or disabled PPP Peer DNS Priority Enabled or disabled PPP Peer WINS Priority Enabled or disabled PPP Authentication Type of authentication configured: PAP, CHAP, or none PPP Authentication Router Name of authentication virtual router PPP Negotiate MRU MRU configured for the profile...
Page 737 Chapter 18: Configuring Dynamic Interfaces Using Bulk Configuration PPPoE ACNAME Access concentrator name PPPoE URL URL sent in PADM message to PPPoE clients PPPoE MOTM Message of the minute sent in the PADM message to PPPoE clients PPPoE Service-Name Table Name of the PPPoE service name table, if configured for the specified profile ATM1483 Auto-configure Whether autodetection of the specified upper-interface encapsulation type (bridged Ethernet, IP, PPP, or PPPoE) is...
Page 738 JUNOSe 11.1.x Link Layer Configuration Guide ATM1483 PVC OAM Loopback frequency Number of seconds between transmissions of OAM F5 end-to-end loopback cells on a circuit created with this profile ATM1483 Ip Subscriber information Subscriber login information for the specified dynamic interface type ATM1483 Profile Name of the profile assigned to the specified upper-interface encapsulation type (bridged Ethernet, IP, PPP, or PPPoE);...
Page 739 Chapter 18: Configuring Dynamic Interfaces Using Bulk Configuration ICMP Redirects : Disabled Access Route Addition : Enabled Network Address Translation: Disabled Source-Address Validation : Disabled Ignore DF Bit : Disabled Filter Option Packets : Disabled Administrative MTU : 1500 TCP MSS value Inactivity Timer : Disabled Route Map Name...
Page 740 JUNOSe 11.1.x Link Layer Configuration Guide ATM1483 PVC Peak rate : 10000, Avg rate : 2000, Burst size : 500 ATM1483 Description VC_atm1483 ATM1483 Advisory Rx Speed 2000000000 ATM1483 PVC OAM Administrative status: enabled ATM1483 PVC OAM Loopback frequency: ATM1483 Ip Subscriber information: user : elaine domain...
Page 741 Chapter 18: Configuring Dynamic Interfaces Using Bulk Configuration Start Svlan Id Starting S-VLAN ID (inclusive) of the S-VLAN group in the subrange End Svlan Id Ending S-VLAN ID (inclusive) of the S-VLAN group in the subrange Start Vlan Id Starting VLAN ID (inclusive) of the VLAN group in the subrange End Vlan Id Ending VLAN ID (inclusive) of the VLAN group in the subrange Assigned Profile Base profile name for the dynamic VLAN subinterface assigned to this VLAN subrange with “profile vlan bulk-config”...
Page 742 JUNOSe 11.1.x Link Layer Configuration Guide ---------------- -------- ----- ---- --------- ------ FastEthernet 4/6 vlanOnly 3 ipProfile Active FastEthernet 4/6 vlanOnly 4 ipProfile Active % 2 profile override(s) found See show vlan bulk-config. show vlan profile Use to display information about the dynamic VLAN subinterfaces that have been created with an overriding profile assignment.
Page 743 Chapter 18: Configuring Dynamic Interfaces Using Bulk Configuration option 82 field of DHCP messages or in the DSL Forum VSA 26-1 of PPPoE PADR and PADI packets. Using this keyword causes the router to display the agent-circuit-identifier string in the command output. Field descriptions Interface Type and specifier of the VLAN subinterface Status Status of the VLAN subinterface: up, down, dormant,...
Page 744 JUNOSe 11.1.x Link Layer Configuration Guide Multicast Number of multicast packets received on the VLAN or S-VLAN subinterface Broadcast Number of broadcast packets received on the VLAN or S-VLAN subinterface Errors Total number of errors in all received packets; some packets might contain more than one error Discards Total number of discarded incoming packets Out Analysis of outbound traffic on this interface...
Page 745 Chapter 18: Configuring Dynamic Interfaces Using Bulk Configuration Example 2 Displays full status and configuration information for the specified VLAN subinterface host1#show vlan subinterface fastEthernet 4/5.1 Interface Status MTU Svlan Id Vlan Id Ethertype Type ----------------- ------- ---- -------- -------- --------- ------- FastEthernet 4/5.1 1522 ---- ----...
Page 746 JUNOSe 11.1.x Link Layer Configuration Guide FastEthernet 4/0.1 ---- FastEthernet 4/0.2 0200D0CB2729E5 See show vlan subinterface. Monitoring Dynamic Interfaces and Profiles...
Page 747: Part 2 Index
Part 2 Index Index on page 717 Index...
Page 748 JUNOSe 11.1.x Link Layer Configuration Guide Index...
Page 749: Index
Index AIS (alarm indication signal) cells.........15 alarm indication signal cells. See AIS cells Symbols ARP (Address Resolution Protocol) table......14 10-Gigabit Ethernet interfaces arp commands for E120 and E320 routers....399, 546, 673 arp..............480 10-Gigabit Ethernet modules ARP, Inverse..............54 specifying an Asynchronous Transfer Mode. See ATM interface....399, 405, 480, 546, 673, 686 ATM (Asynchronous Transfer Mode)......13, 15 802.3ad link aggregation...
Page 750 JUNOSe 11.1.x Link Layer Configuration Guide ATM 1483 subinterfaces, dynamic atm vp-description..........43 assigning VC classes to......67, 630, 631 atm vp-tunnel............31 benefits of using..........629 monitor atm vc.............72 bulk configuration of VC ranges......631 monitor atm vp.............72 changing VC subranges.......634, 651 ping atm interface atm.........38 configuring............637 See also show atm commands creating static ATM interfaces inVC...
Page 751 Index bridge groups setting statistics baselines........490 configuring optional attributes......476 subscriber policies..........470 creating...............474 unsupported features..........472 defined...............468 broadcast command..........480 monitoring............490 bulk configuration of VC ranges.........631 bridge interfaces assigning VC classes......67, 630, 631 configuring............476 oversubscription.........519, 625 defined...............468 restarting LCP negotiations for PPPoA monitoring............490 clients.............635 supported configurations........469 with CAC............7, 631...
Page 752 JUNOSe 11.1.x Link Layer Configuration Guide troubleshooting...........381 bridged Ethernet, dynamic.........557 using in profiles..........564, 589 bridged Ethernet, static........447 Cisco HDLC Cisco HDLC............508 configuring............507 IPoA, dynamic............553 E120 and E320 routers........506 MLFR..............138 error frames............505 MLPPP, dynamic..........328 framing...............505 MLPPP, static..........312, 328 line modules supported........506 PPPoE, dynamic.........528, 534 monitoring............511 PPPoE, static..........386, 393...
Page 753 Index customer support............xxxi for PPPoE clients..........548 contacting JTAC..........xxxi clearing lockout condition......550 configuring..........548 differences from PPPoE over static ATM............548 data communication equipment. See DCE monitoring......548, 607, 608, 701 data PVCs, creating............47 grace period............527 data terminal equipment. See DTE guidelines............527 data-link connection identifier. See DLCI Dynamic Host Configuration Protocol.
Page 754 JUNOSe 11.1.x Link Layer Configuration Guide POS interfaces......275, 364, 368, 371 error frame seconds PPP interfaces..........273, 307 configuring PPPoE interfaces..........385 high threshold..........244 transparent bridging...........472 low threshold..........244 e3-scramble command..........31 window............244 E320 routers error frame seconds summary events ATM interfaces............10 configuring bridged Ethernet..........446 high threshold..........244 dynamic interfaces......154, 171, 521 low threshold..........244...
Page 755 Index S-VLANs............170, 186 disabling subnetwork attachment point (SNAP)....169 remote loopback functionality on a remote VLANs..............169 peer............247 Ethernet link aggregation discovery, overview..........234 CE-side load balancing........202 elements, overview configuring............202 client............231 enabling CE-side load balancing......202 sublayer............231 interoperation with OAM link-fault management enabling operation of 802.3ah below the LAG on a particular interface.......242 sublayer...........240 remote loopback functionality on a remote...
Page 756 JUNOSe 11.1.x Link Layer Configuration Guide setting ethernet oam lfm link-monitor the local entity into loopback mode.....247 symbol-period..........245 slow protocols ethernet oam lfm mode........243 destination address of OAM PDUs and..230 ethernet oam lfm pdu-lost-threshold....243 specifying ethernet oam lfm pdu-transmit-interval....243 action on exceeding high threshold, disabling ethernet oam lfm remote-failure......246 interface...........246 ethernet oam lfm remote-loopback start.....247...
Page 757 Index external loopback............31 interconnection and relationship of NNIs and subnetworks............107 map class............119 maximum payload size........119 F4 OAM cells, for ATM..........17 monitoring............123 configuring............33 multicast addressing...........107 handling of received cells........20 Network-to-Network Interface......107 F5 OAM cells, for ATM overview.............107 configuring............35, 51 platform considerations........109 disabling automatically.......20, 26, 30, 35 SNMP link status processing.......118 handling of received cells........20...
Page 758 JUNOSe 11.1.x Link Layer Configuration Guide Gigabit Ethernet modules configuring MLPPP..........308 IEEE 802.1Q..............169 configuring PPPoE..........393 IEEE 802.1w..............202 specifying an IEEE 802.1w (Rapid Reconfiguration of Spanning interface....399, 405, 480, 546, 673, 686 Tree)...............202 grace period, dynamic encapsulation type IEEE 802.3ad.............199 lockout..............527 IEEE 802.3ad (Link Aggregation)........202 group (multicast) addressing........107 IEEE 802.3ah OAM link-fault management See Ethernet...
Page 759 Index transmission to the remote entity ip igmp...............570 triggering of the discovery process and..235 ip ignore-df-bit............570 using the Flags field of ip inactivity-timer..........570 and OAM remote fault detection....238 ip mac-validate...........447 viewing...............253 ip mtu..............570 with Link Fault event bit set ip nat..............570 not containing TLV data.......239 ip policy..............570 integrated local management interface.
Page 760 JUNOSe 11.1.x Link Layer Configuration Guide Link fault information OAM PDUs detection of receive path failure......242 keepalive timer, setting..........30 sending of not supported..........242 Link Integrity Protocol. See LIP link monitoring L2TP (Layer 2 Tunneling Protocol)......159 frequent polling of error counters profile characteristics..........564 when enabled on the local entity....231 using PPPoE remote circuit ID....381, 413...
Page 761 Index loopback command map entries, Frame Relay........124, 140 ATM interfaces............31 map list, using to configure NBMA interfaces....40 POS interfaces............368 map-class frame-relay command.......119 Loopback control OAM PDUs map-group command..........42 description of............231 map-list command............42 sending of Marker response OAM PDUs for termination of loopback......240 circumstances of non-transmission of....241 start of loopback of remote peee link event caused by exceeding high threshold...
Page 762 JUNOSe 11.1.x Link Layer Configuration Guide overview.............303 Multilink Frame Relay. See MLFR packet distribution..........308 multilink maximum received reconstructed unit platform considerations........306 (MRRU)..............304 profiles..............564 Multilink PPP. See MLPPP protocol layering..........304 multinetting...............159 reassembly multiplexer configuring dynamic........328 pass-through of MAC client-generated frames configuring static.........326 without any modification......233 overview............324 transfer of loopback frames...
Page 763 Index successful rediscovery with the remote peer OAM elements link transition to the up state.......236 operations of tearing down of and link-fault management......231 generation of the link-fault event....235 parts of OAM client client............231 enabling and configuration of OAM sublayer............231 sublayer............232 OAM features enabling OAM operations on the link backward compatibility with older...
Page 764 JUNOSe 11.1.x Link Layer Configuration Guide repeated sending of Event notification PDUs settings for enabling and disabling remote preventing duplication.........237 loopback supported error events not stored across reboots......247 error frame..........237 viewing configuration.........253 error frame seconds summary.....237 warning message error symbol period........237 while placing local entity in remote supported frame errrors tracked loopback..........247...
Page 765 Index OAM PDU transmission rate placement of configuring............243 above the MAC layer........231 definition of below the LLC layer........231 range for configuration........236 presentation of interface to clients product of loss threshold and for MAC clients..........231 equals lost-link timer........236 for OAM clients..........231 viewing configured setting........255 OAM traffic OAM PDUs See OAM messages...
Page 766 JUNOSe 11.1.x Link Layer Configuration Guide PAP (Password Authentication Protocol)....265 POS..............364 passive discovery mode PPP..............273 and OAM link-fault management......234 PPPoE..............384 configuration on transparent bridging...........472 customer edge devices........234 point-to-multipoint, NBMA connection......14 enabled on local and remote entities Point-to-Point Protocol over ATM. See PPPoA and influence on discovery process.....234 Point-to-Point Protocol over Ethernet.
Page 767 Index PPP profiles............564 formatting...........379, 413 troubleshooting monitoring...........421 dynamic interfaces........619 overview............379 static interfaces..........300 sending to RADIUS or L2TP....381, 413 ppp commands............280 troubleshooting..........381 ppp aaa-profile............575 using in profiles........564, 589 ppp authentication......280, 315, 580 configuring dynamic interfaces over ATM...528 ppp chap-challenge-length......280, 580 configuring dynamic interfaces over PPPoE..534 ppp description...........278 configuring for Ethernet......393, 535 ppp fragmentation........328, 580...
Page 768 JUNOSe 11.1.x Link Layer Configuration Guide PPPoE service name tables configuring F5 OAM..........51 action, defined............376 configuring for bridged IP........440 configuring............404 configuring individual parameters for....45 creating and populating........404 configuring Inverse ARP........54 enabling for dynamic interfaces......405 configuring service category.........48 enabling for static interfaces.......405 creating control PVCs..........46 Ethernet configurations........405 creating data PVCs..........47...
Page 769 Index remote loopback operation configuring PPPoE over S-VLAN......170 halting configuring to support dynamic PPPoE....542 calculation and display of received data at configuring tunnel interfaces the prompt..........248 advantages..........184 calculation and display of transmitted data example............185 at the prompt...........248 interface stacking........185 viewing calculated loopback details.....248 displaying status..........190 prerequisite for enabling remote peer to loop back oversubscription..........188...
Page 770 JUNOSe 11.1.x Link Layer Configuration Guide show frame-relay pvc........124, 140 multicast address of show frame-relay subinterface....130, 150 and destination MAC address of remote show frame-relay summary......130, 150 entities.............235 show hdlc interface command........511 OAM messages and..........230 show interfaces commands SMs (Service modules) show interfaces fastEthernet.......159, 190 MLPPP features...........308 show interfaces gigabitEthernet....159, 190...
Page 771 Index ip................480 multicast.............480 technical support pppoe..............480 contacting JTAC..........xxxi relearn..............480 terminated PPP session accounting statistics.....285 show subscriber-policy........490 text and syntax conventions........xxx subscriber-policy..........480 traffic management, ATM unicast..............480 types..............13 unknown-destination..........480 traffic-class unknown-protocol..........480 Multiclass MLPPP........352, 354 subscribers traffic-shaping parameters.........519 authenticating on dynamic bridged Ethernet transmit clock source, configuring interfaces........523, 561, 636 ATM interfaces............28...
Page 772 JUNOSe 11.1.x Link Layer Configuration Guide VC classes virtual channel connection. See VCC assigning to virtual channel identifier. See VCI ATM major interfaces........65 virtual channel. See VC dynamic ATM 1483 virtual circuit descriptor. See VCD subinterfaces......67, 631, 643 virtual circuit. See VC, monitoring PVCs..............64 virtual connections, ATM..........5 static ATM 1483 subinterfaces.......66...
Page 773 Index removing from VLAN range......680 shortening or expanding......680 creating static VLAN interfaces in configuring..........686 monitoring...........703 VLANs (virtual local area networks) bridged Ethernet configurations......453 configuring............172 configuring dynamic subinterfaces for....658 configuring for dynamic IP.........658 configuring for dynamic PPPoE......658 configuring IPv4 and IPv6 over dynamic PPPoE.............538 configuring to support dynamic PPPoE....536 displaying status..........190...
Page 774 JUNOSe 11.1.x Link Layer Configuration Guide Index...

This manual is also suitable for:

Junose 11.1.x