Download Print this page

Juniper JUNOSE SOFTWARE 11.2.X - LINK LAYER CONFIGURATION GUIDE 7-7-2010 Configuration Manual

Software for e series broadband services routers link layer configuration guide

Table of Contents

Advertisement

Quick Links

Download this manual

JunosE™ Software

for E Series™ Broadband

Services Routers

Link Layer Configuration Guide

Release

11.2.x

Published: 2010-07-07

Copyright © 2010, Juniper Networks, Inc.

Table of Contents

Advertisement

Chapters

Table of Contents

Troubleshooting

Need help?

Need help?

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

Questions and answers

Summary of Contents for Juniper JUNOSE SOFTWARE 11.2.X - LINK LAYER CONFIGURATION GUIDE 7-7-2010

Page 1 JunosE™ Software for E Series™ Broadband Services Routers Link Layer Configuration Guide Release 11.2.x Published: 2010-07-07 Copyright © 2010, Juniper Networks, Inc.
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 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...
Page 4 Customer shall be liable for any such violations. The version of the Software supplied to Customer may contain encryption or other capabilities restricting Customer’s ability to export the Software without an export license. Copyright © 2010, Juniper Networks, Inc.
Page 5 (including Juniper modifications, as appropriate) available upon request for a period of up to three years from the date of distribution. Such request can be made in writing to Juniper Networks, Inc., 1194 N. Mathilda Ave., Sunnyvale, CA http://www.gnu.org/licenses/gpl.html...
Page 6 Copyright © 2010, Juniper Networks, Inc.
Page 7: Table Of Contents
Index ............709 Copyright © 2010, Juniper Networks, Inc.
Page 8 JunosE 11.2.x Link Layer Configuration Guide viii Copyright © 2010, Juniper Networks, Inc.
Page 9 Removing Circuits ..........14 Copyright © 2010, Juniper Networks, Inc.
Page 10 Upgrade Considerations ......... . 54 Copyright © 2010, Juniper Networks, Inc.
Page 11 Configuring Frame Relay Versus MLFR ......137 Copyright © 2010, Juniper Networks, Inc.
Page 12 Interface Specifiers ..........200 Copyright © 2010, Juniper Networks, Inc.
Page 13 Information OAM PDU Components ....... . 231 Transmission Settings for Information OAM PDUs ..... 231 Copyright © 2010, Juniper Networks, Inc. xiii...
Page 14 Monitoring PPP Interfaces ......... . . 282 Copyright © 2010, Juniper Networks, Inc.
Page 15 Enabling Multiclass MLPPP ......... . 349 Copyright © 2010, Juniper Networks, Inc.
Page 16 Configuration Examples for ATM-to-Ethernet Interworking Functions ..392 Single DSLAM Connected to a PPPoE Access Concentrator Example ..392 Multiple DSLAMs Connected to a PPPoE Access Concentrator Example . . 393 Copyright © 2010, Juniper Networks, Inc.
Page 17 Configuring the MTU Size for Bridged Ethernet ......459 Copyright © 2010, Juniper Networks, Inc.
Page 18 Monitoring Cisco HDLC ..........508 xviii Copyright © 2010, Juniper Networks, Inc.
Page 19 Configuring and Verifying Lockout for PPPoE Clients ....545 Clearing the Lockout Condition for a PPPoE Client ....547 Copyright © 2010, Juniper Networks, Inc.
Page 20 Dynamic Interface Creation ........629 Copyright © 2010, Juniper Networks, Inc.
Page 21 Merging VLAN Subranges ........676 Changing the Administrative State of VLAN Subranges ... . 676 Copyright © 2010, Juniper Networks, Inc.
Page 22 Index ............709 xxii Copyright © 2010, Juniper Networks, Inc.
Page 23 Figure 23: Single-Homed GE-2 Line Module Configuration ....210 Figure 24: Single-Homed FE-8 Line Module Configuration (1:N) ... . . 210 Copyright © 2010, Juniper Networks, Inc. xxiii...
Page 24 Figure 57: Assigning a Profile to a Static Interface ......565 xxiv Copyright © 2010, Juniper Networks, Inc.
Page 25 Figure 60: Dynamic IP and PPPoE over Single Dynamic VLAN Subinterface . . . 654 Figure 61: Dynamic VLAN Subinterfaces for Subscribers ....655 Copyright © 2010, Juniper Networks, Inc.
Page 26 JunosE 11.2.x Link Layer Configuration Guide xxvi Copyright © 2010, Juniper Networks, Inc.
Page 27: List Of Tables
Table 19: Sample PPPoE Service Name Table ......374 Table 20: Configuring Nondefault Formats for the PPPoE Remote Circuit ID . . . 376 Table 21: Interface Specifier Format Examples for dsl-forum-1 Keyword ..378 Copyright © 2010, Juniper Networks, Inc. xxvii...
Page 28 Configurations ..........545 xxviii Copyright © 2010, Juniper Networks, Inc.
Page 29: About The Documentation
Audience This guide is intended for experienced system and network specialists working with Juniper Networks E Series Broadband Services Routers in an Internet access environment. E Series and JunosE Text and Syntax Conventions Table 1 on page xxx defines notice icons used in this documentation.
Page 30: Table 1: Notice Icons
Indicates that you must press two or more Press Ctrl + b. keys simultaneously. Syntax Conventions in the Command Reference Guide Plain text like this Represents keywords. terminal length Italic text like this Represents variables. mask, accessListName Copyright © 2010, Juniper Networks, Inc.
Page 31: Obtaining Documentation
CD-ROMs or DVD-ROMs, see the Portable Libraries page at http://www.juniper.net/techpubs/resources/index.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
Configuring Bridged IP on page 437 Configuring Bridged Ethernet on page 443 Configuring Transparent Bridging on page 465 Configuring Cisco HDLC on page 503 Configuring Dynamic Interfaces on page 511 Configuring Dynamic Interfaces Using Bulk Configuration on page 619 Copyright © 2010, Juniper Networks, Inc.
Page 34 JunosE 11.2.x Link Layer Configuration Guide Copyright © 2010, Juniper Networks, Inc.
Page 35: Configuring Atm
Monitoring ATM on page 66 Overview ATM is a high-speed networking technology that handles data in fixed-size units called cells. It enables high-speed communication between edge routers and core routers in an ATM network. Copyright © 2010, Juniper Networks, Inc.
Page 36: Atm Interfaces
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. Copyright © 2010, Juniper Networks, Inc.
Page 37: Atm Virtual Connections
E Series routers support the following AAL5 encapsulation types as specified in RFC 2684—Multiprotocol Encapsulation over ATM Adaptation Layer 5 (September 1999), which replaces RFC 1483: aal5snap—LLC/SNAP aal5mux ip—VC-based multiplexing Copyright © 2010, Juniper Networks, Inc.
Page 38: Local Atm Passthrough
VC-based multiplexing. (See “Configuring Dynamic Interfaces” on page 511.) 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: Configuring Atm
For example, the peak cell rate is used to calculate how much bandwidth is required for CBR connections. Table 4: Traffic Parameters Used to Compute Bandwidth Service Category Traffic Parameter Used to Calculate Required Bandwidth Copyright © 2010, Juniper Networks, Inc.
Page 40 Optional Parameters” on page 23. For information about how to use the atm bulk-config command to create a bulk-configured VC range, see “Bulk Configuration of VC Ranges” on page 627 in “Configuring Dynamic Interfaces Using Bulk Configuration” on page 619. Copyright © 2010, Juniper Networks, Inc.
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: Platform Considerations
JunosE 11.2.x Link Layer Configuration Guide Platform Considerations You can configure ATM interfaces on the following Juniper Networks E Series Broadband Services Routers: E120 router E320 router ERX1440 router ERX1410 router ERX710 router ERX705 router ERX310 router Module Requirements For information about the modules that support ATM interfaces on ERX14xx models, ERX7xx models, and the ERX310 router: See ERX Module Guide, Table 1, Module Combinations for detailed module specifications.
Page 43: References
JunosE Physical Layer Configuration Guide. Module Capabilities The level of support for certain ATM capabilities varies depending on the module. Table 5 on page 12 lists the specific differences in the capabilities of the modules. Copyright © 2010, Juniper Networks, Inc.
Page 44: Virtual Channel Support
E Series router and module you are using. For information about the maximum number of ATM VCs supported per chassis, per module, and per port, see JunosE Release Notes, Appendix A, System Maximums. Copyright © 2010, Juniper Networks, Inc.
Page 45: Atm Nbma
If the device at the other end of a circuit does not support InARP, static mapping is required for that circuit. One of these two methods must be used to generate an ARP table entry for each circuit of the NBMA interface. Copyright © 2010, Juniper Networks, Inc.
Page 46: Aging
An ATM connection consists of a group of points. This OAM implementation provides management for the following points: Connection endpoint—The end of a VC/VP connection where the ATM cells are terminated Segment endpoint—The end of a connection segment Copyright © 2010, Juniper Networks, Inc.
Page 47: Fault Management
RDI state but does not generate OAM fault management cells in response to the condition. The ATM interface leaves the RDI condition when no RDI cells have been received for a configurable time period. Copyright © 2010, Juniper Networks, Inc.
Page 48: Continuity Verification
Also, the atm oam flush command causes the router to send a deactivation request to the peer and suspend all CC operations. Therefore, we recommend that you disable CC cell generation and transmission on all VCs before issuing atm oam flush. Copyright © 2010, Juniper Networks, Inc.
Page 49: After Cc Cell Flow Is Enabled
ATM host does not respond to a loopback cell The retry frequency with which loopback cells are transmitted when the router verifies the up status of the circuit; that is, when the ATM host resumes responding to a loopback cell Copyright © 2010, Juniper Networks, Inc.
Page 50: F4 Oam Cells
OAM cells for the interface. 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 19. Copyright © 2010, Juniper Networks, Inc.
Page 51: Automatic Disabling Of F5 Oam Services
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. Copyright © 2010, Juniper Networks, Inc.
Page 52: Before You Configure Atm
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 21 shows the relationship of Steps 1 through 3.) Copyright © 2010, Juniper Networks, Inc.
Page 53: Figure 3: Configuring An Atm Interface, Subinterface, And Pvc
Use to configure a PVC on an ATM interface. Specify one of the following encapsulation types: aal5snap—Specifies an LLC encapsulated circuit; LLC/SNAP header precedes the protocol datagram. aal5mux ip—Specifies a VC-based multiplexed circuit. This option is used for IP only. Copyright © 2010, Juniper Networks, Inc.
Page 54 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). Copyright © 2010, Juniper Networks, Inc.
Page 55: Setting Optional Parameters
Set the operational mode of the physical interface to SDH STM1. host1(config-if)#atm sonet stm-1 Configure the UNI version of ILMI using one of the following methods: Enable auto configuration of ILMI. Copyright © 2010, Juniper Networks, Inc.
Page 56: Optional Tasks On Atm 1483 Subinterfaces
When you set the administrative state of the ATM AAL5 interface to disabled, the router automatically disables all F5 OAM services configured on the associated VC, and prevents the VC from receiving or transmitting F5 OAM cells. Example host1(config-if)#atm aal5 shutdown Copyright © 2010, Juniper Networks, Inc.
Page 57 Use to set the MTU size for an ATM 1483 subinterface. The range is 256–9180. Example host1(config-subif)#atm atm1483 mtu 7800 Use the no version to restore the default size of 9180. See atm atm1483 mtu. atm atm1483 shutdown Copyright © 2010, Juniper Networks, Inc.
Page 58 CAC. For information about creating bulk-configured VC ranges, see “Bulk Configuration of VC Ranges” on page 627 in “Configuring Dynamic Interfaces Using Bulk Configuration” on page 619. Example host1(config-if)#atm cac 3000000 ubr 3000 Copyright © 2010, Juniper Networks, Inc.
Page 59 Use the no version to return framing to the default: For a T3 interface, the default is cbitplcp For an E3 interface, the default is g751plcp See atm framing. atm ilmi-enable Use to enable ILMI on the interface. Example Copyright © 2010, Juniper Networks, Inc.
Page 60 Use the no version to enable a disabled interface. See atm shutdown. atm snmp trap link-status Use to enable SNMP link status traps on the ATM layer interface. Example host1(config-if)#atm snmp trap link-status Copyright © 2010, Juniper Networks, Inc.
Page 61 The tunnel rate can be a value in the range 0–4294967295, when you specify the rate of traffic flow without the constant bit rate (CBR) service category, and can be a value Copyright © 2010, Juniper Networks, Inc.
Page 62 Use the no version to return to the default setting, 300 seconds. See load-interval. loopback Use to place the interface into loopback mode. Specify either: diagnostic—Places the interface into internal loopback. line —Places the interface into external loopback. Copyright © 2010, Juniper Networks, Inc.
Page 63: Configuring Oam
(Optional) To cause the interface to generate end-to-end loopback cells in addition to receiving and responding to them, set the loopback timer. host1(config-if)#atm oam 10 end-loopback loopback-timer 20 (Optional) Enable CC cell flows. host1(config-if)#atm oam 10 seg-loopback cc source Copyright © 2010, Juniper Networks, Inc.
Page 64 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. Copyright © 2010, Juniper Networks, Inc.
Page 65: Configuring F5 Oam
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 Copyright © 2010, Juniper Networks, Inc.
Page 66: Setting A Loopback Location Id
1s (ones). You can set a specific value to identify this ATM interface as the intended recipient of OAM loopback cells. You can also set the location ID to all 0s (zeros). Copyright © 2010, Juniper Networks, Inc.
Page 67: Enabling Oam Flush
Because ATM ping requires the receipt of OAM cells, make sure that the receipt and transmission of OAM cells is not disabled (using “atm oam flush” on page 35 ). To reenable the receipt and transmission of OAM cells, enter no atm oam flush. Copyright © 2010, Juniper Networks, Inc.
Page 68 Example 1—This example generates end-to-end loopback cells for VPI=0 and VCI=105 on ATM interface 2/0. The count value is 5 OAM loopback cells, and the timeout value is 2 seconds. host1#ping atm interface atm 2/0 0 105 end-loopback count 5 timeout 2 Copyright © 2010, Juniper Networks, Inc.
Page 69: Configuring An Nbma Interface
(Optional) Specify InARP and a refresh rate (also optional). host1(config-subif)#atm pvc 3 3 3 aal5snap inarp 5 host1(config-subif)#atm pvc 4 4 4 aal5snap inarp Assign an IP address and subnet mask to the PVC. Copyright © 2010, Juniper Networks, Inc.
Page 70: Creating An Nbma Static Map
The default refresh rate is 15 minutes. You can configure InARP only if you specify the aal5snap encapsulation type. Example host1(config-if)#atm pvc 6 0 11 aal5snap inarp 10 Use the no version to remove the specified PVC. See atm pvc. Copyright © 2010, Juniper Networks, Inc.
Page 71 Use to create a map list when configuring static mapped NBMA interfaces. Limit the name of the map list to no more than 31 characters. You can create multiple map lists; however, you can associate only one map list with each physical interface. Copyright © 2010, Juniper Networks, Inc.
Page 72: Assigning Descriptions To Interfaces
The description can be a maximum of 255 characters and can include the # (pound sign) character. The first 32 characters of the ATM description are pushed out to RADIUS during authentication and accounting. Use the show atm interface command to display the description. Example Copyright © 2010, Juniper Networks, Inc.
Page 73: Sending Interface Descriptions To Aaa
To configure this feature for ATM 1483 subinterfaces, enter this command in Profile Configuration mode. See “Configuring ATM 1483 Dynamic Subinterfaces” on page 624 in “Configuring Dynamic Interfaces Using Bulk Configuration” on page 619. Copyright © 2010, Juniper Networks, Inc.
Page 74 The description string can be a maximum of 32 characters. The VP description is stored in NVS and persists after a reboot. Use the show atm vp-description command to display the text description. Example host1(config-if)#atm vp-description 2 vpi2Subscribers Copyright © 2010, Juniper Networks, Inc.
Page 75: Configuring Individual Atm Pvc Parameters
ATM VC Configuration mode supports additional F5 OAM alarm surveillance and VC integrity options. In most cases, you can use either an ATM VC Configuration mode command or the atm pvc command to configure ATM PVC parameters. However, to configure F5 OAM Copyright © 2010, Juniper Networks, Inc.
Page 76: Creating Control Pvcs
To create a control PVC, specify the VCD, VPI and VCI (in the format vpi/vci), and the ilmi keyword. Example host1(config-if)#pvc 5 0/5 ilmi Use the no version to remove the specified control PVC from the router. See pvc. Copyright © 2010, Juniper Networks, Inc.
Page 77: Creating Data Pvcs
You must issue the exit command from ATM VC Configuration mode for the configuration to take effect. Example host1(config-subif)#pvc 10 15/50 host1(config-subif-atm-vc)#exit Use the no version to remove the specified data PVC from the router. See pvc. Copyright © 2010, Juniper Networks, Inc.
Page 78: Configuring The Service Category For Data Pvcs
Use the no version to restore the default service category, UBR without a PCR. See ubr. vbr-nrt Use to configure the variable bit rate, nonreal time (VBR-NRT) service category on an ATM data PVC. You must specify all of the following parameters: Copyright © 2010, Juniper Networks, Inc.
Page 79: Configuring Encapsulation For Data Pvcs
PVC, or to restore the default encapsulation method, aal5snap. For example, the following commands configure a data PVC that uses aal5all encapsulation. Issuing the exit command causes the configuration to take effect. host1(config)#interface atm 3/0.3 Copyright © 2010, Juniper Networks, Inc.
Page 80: Configuring F5 Oam For Data Pvcs
(AIS) and remote defect indication (RDI) fault management cells Continuity check (CC) verification oam cc Generation of F5 loopback cells and enabling oam-pvc of VC integrity Parameters for VC integrity oam retry Copyright © 2010, Juniper Networks, Inc.
Page 81 ATM VC Configuration mode. There is no equivalent atm pvc command to configure these parameters. You must issue the exit command from ATM VC Configuration mode for the configuration to take effect. Example Copyright © 2010, Juniper Networks, Inc.
Page 82 To enable F5 OAM VC integrity on the PVC, use the manage keyword. You can optionally specify the number of seconds, in the range 1–600, for the router to wait between the transmission of loopback cells during normal operation; the default value is 10. Copyright © 2010, Juniper Networks, Inc.
Page 83: Configuring Inverse Arp For Data Pvcs
For example, the following commands enable InARP with a nondefault refresh rate (10 minutes) on a data PVC. The PVC uses aal5snap encapsulation by default. Issuing the exit command causes the configuration to take effect. host1(config)#interface atm 3/2.1 multipoint Copyright © 2010, Juniper Networks, Inc.
Page 84: Configuring Atm Vc Classes
PVC, has no effect. For information about creating a data PVC by using the pvc command, see “Creating Data PVCs” on page 45. NOTE: For information about the total number of VC classes supported on the router, see JunosE Release Notes, Appendix A, System Maximums. Copyright © 2010, Juniper Networks, Inc.
Page 85: Benefits
VC class, in the following order of precedence: Attribute value specified in the VC class assigned to this PVC Attribute value specified in the VC class assigned to the ATM 1483 subinterface on which this PVC is created Copyright © 2010, Juniper Networks, Inc.
Page 86: Precedence Levels For Dynamic Pvcs
Default values implicitly specified for PVC attributes with the atm pvc command have a lower precedence than the attribute values specified in the associated VC Copyright © 2010, Juniper Networks, Inc.
Page 87 For information about creating a data PVC by using the pvc command, see “Creating Data PVCs” on page 45. Configure the VC class as described in “Configuring VC Classes” on page 56. Assign the VC class in one of the following ways: Copyright © 2010, Juniper Networks, Inc.
Page 88: Configuring Vc Classes
In premium-subscriber-class: The encapsulation command sets the encapsulation method to aal5autoconfig. The cbr command sets the service category to CBR with a PCR of 200 Kbps. Copyright © 2010, Juniper Networks, Inc.
Page 89 For detailed information about how to use this command, see “encapsulation” on page 48. You must issue the exit command from ATM VC Class Configuration mode for the configuration to take effect. Example host1(config-vc-class)#encapsulation aal5mux ip host1(config-vc-class)#exit Copyright © 2010, Juniper Networks, Inc.
Page 90 Example 1—Enables CC verification with a source endpoint host1(config-vc-class)#oam cc source host1(config-vc-class)#exit 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 Copyright © 2010, Juniper Networks, Inc.
Page 91 For detailed information about how to use this command, see “ubr” on page 46. 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 Copyright © 2010, Juniper Networks, Inc.
Page 92 You must issue the exit command from ATM VC Class Configuration mode for the VC class configuration to take effect. 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 Copyright © 2010, Juniper Networks, Inc.
Page 93: Assigning Vc Classes To Individual Pvcs
The class-vc command is valid only for data PVCs created with the pvc command. 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 Copyright © 2010, Juniper Networks, Inc.
Page 94: Assigning Vc Classes To Atm Major Interfaces
PVC attributes to their systemwide default values, or to the values set in the associated VC class with the next highest order of precedence. See class-int. Copyright © 2010, Juniper Networks, Inc.
Page 95: Assigning Vc Classes To Static Atm 1483 Subinterfaces
Assigning VC Classes to Base Profiles for Bulk-Configured VC Ranges To assign a VC class to a base profile for a dynamic ATM 1483 subinterface, you can use the atm class-vc command from Profile Configuration mode. Issuing this command Copyright © 2010, Juniper Networks, Inc.
Page 96: Precedence Level Examples For Assigning Vc Classes
The router takes the values for the other attributes from the VC class my-premium-class, which is still assigned to the PVC. host1(config)#interface atm 2/0.200 host1(config-subif)#pvc 200 0/200 host1(config-subif-vc)#vbr-rt 200 150 200 host1(config-subif-vc)#exit Copyright © 2010, Juniper Networks, Inc.
Page 97: Example 2: Changing The Encapsulation Method In The Vc Class
CBR with a PCR of 600 Kbps as the service category for the PVC instead of the service category configured through RADIUS. host1(config)#interface atm 2/0.200 host1(config-subif)#pvc 200 0/200 Copyright © 2010, Juniper Networks, Inc.
Page 98: Configuring Dynamic Atm 1483 Subinterfaces
To set the baseline for an ATM VP, specify the VPI. The numeric range of the VPI depends on the line module capabilities and current configuration. Copyright © 2010, Juniper Networks, Inc.
Page 99: Displaying Interface Rate Statistics For Atm Vcs And Atm Vps
For information about logging in to the router, see section Accessing the CLI in JunosE System Basics Configuration Guide. Access User Exec mode or Privileged Exec mode. For information, see section Accessing Command Modes in JunosE System Basics Configuration Guide. Copyright © 2010, Juniper Networks, Inc.
Page 100 These values indicate that the router initially takes a baseline for each interface against which to measure subsequent statistics. The router continues to display subsequent lines of output for each interface at the specified load interval until you press Ctrl+c to stop the command. Copyright © 2010, Juniper Networks, Inc.
Page 101 VCD—Virtual circuit descriptor that identifies the VC (monitor atm vc command only) VPI—Virtual path identifier of the PVC (monitor atm vp command only) Seconds between polls—Number of seconds at which the router calculates bit rate and packet rate statistics Copyright © 2010, Juniper Networks, Inc.
Page 102 6637664/6482 6637664/6482 ATM 12/0 6637872/6482 6637872/6482 host1#^C Example 4—Displays bit rate and packet rate statistics over a 15-second load interval for two ATM VPs, with the time of day that the statistics were calculated Copyright © 2010, Juniper Networks, Inc.
Page 103: Using Atm Show Commands
ATM AAL5 interface disabled—Autodetection of the ATM 1483 dynamic encapsulation type is not currently enabled on the ATM AAL5 interface InPackets—Number of packets received on this interface InBytes—Number of bytes received on this interface Copyright © 2010, Juniper Networks, Inc.
Page 104 I/O module; on the OC3-2 GE APS I/O module, you can specify ATM interfaces only in ports 0 and 1; port 2 is reserved for a Gigabit Ethernet interface Copyright © 2010, Juniper Networks, Inc.
Page 105 ILMI keepalive—State and status of the ILMI (displayed only when ILMI is configured on the interface) Max VCI per VPI—Maximum number of virtual circuits on each virtual path CAC admin state—Enabled, disabled Subscription bandwidth—Maximum allowable bandwidth on the port (displayed only when CAC is enabled) Copyright © 2010, Juniper Networks, Inc.
Page 106 SONET path operational status SONET operational status—State of SONET interface: up, down, lowerLayerDown time since last status change—Time since last reported change to the SONET operational status Copyright © 2010, Juniper Networks, Inc.
Page 107 CAC admin state: enabled Subscription bandwidth: 3000000 kbps UBR weight: 3000 kbps Available bandwidth: 2992000 kbps SNMP trap link-status: enabled OAM cell receive status: enabled OAM cell filter : all cells atm oam loopback-location 0XFFFFFFFF Copyright © 2010, Juniper Networks, Inc.
Page 108 VCx—Name of protocol, the protocol address, and the VCD that the address is mapped to (for ATM VCs configured with the atm pvc command). VC—Number of the virtual circuit Copyright © 2010, Juniper Networks, Inc.
Page 109 End To End OAM CC verification—Whether end-to-end CC verification is enabled or disabled OAM CC Type—Whether the circuit is a sink or a source, or both a sink and a source OAM Current CC state Copyright © 2010, Juniper Networks, Inc.
Page 110 InOamF4EndLoopbackResponses—Number of F4 end-to-end loopback responses received InOamF4SegLoopbackCells—Total number of F4 segment loopback cells received on this interface, which is the sum of the following counts: InOamF4SegLoopbackCommands—Number of F4 segment loopback commands received Copyright © 2010, Juniper Networks, Inc.
Page 111 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 Copyright © 2010, Juniper Networks, Inc.
Page 112 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 InOamF4SegLoopbackCommands InOamF4SegLoopbackResponses InOamF4SegCCActDeActCells InOamF4SegCCCells OutOamF4SegmentCells OutOamF4SegLoopbackCells Copyright © 2010, Juniper Networks, Inc.
Page 113 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 Copyright © 2010, Juniper Networks, Inc.
Page 114 2/1 Interface VPI VCI CellCount TimeOut SentCellCount RespCount Status --------- --- --- --------- ------- ------------- ---------- ------- ATM 2/1 Ping Completed ATM 2/1 Ping Completed % Found 2 Entries in this Interface Copyright © 2010, Juniper Networks, Inc.
Page 115 To display status information only for ATM subinterfaces with a specific operating status, use the status keyword with one of the following status values. (See the Status field description for an explanation of these values.) dormant dormantLockout down Copyright © 2010, Juniper Networks, Inc.
Page 116 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: Copyright © 2010, Juniper Networks, Inc.
Page 117 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 Copyright © 2010, Juniper Networks, Inc.
Page 118 Circuit Interface Interface ATM-Prot VCD VPI VCI Type Encap MTU Status Type ----------- -------- --- --- --- ----- ----- ---- -------------- --------- ATM 2/0.101 RFC-1483 101 0 101 PVC AUTO 9180 dormantLockout Static Copyright © 2010, Juniper Networks, Inc.
Page 119 : pppoetest Assigned profile (any) : none assigned Interface Alias: atm20101 BridgedEnet subscriber info Username: elaine@jpeterman.com Password: putty Authenticate: enabled Assigned VC class : premium-subscriber-class SNMP trap link-status: disabled InPackets: InBytes: 1904 OutPackets: OutBytes: Copyright © 2010, Juniper Networks, Inc.
Page 120 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 Copyright © 2010, Juniper Networks, Inc.
Page 121 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 VCs with a VPI of zero (0) Copyright © 2010, Juniper Networks, Inc.
Page 122 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. Field descriptions VCD—Virtual circuit descriptor VPI—Virtual path identifier Copyright © 2010, Juniper Networks, Inc.
Page 123 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; waiting for response Copyright © 2010, Juniper Networks, Inc.
Page 124 Active—OAM CC cell flow is running 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 Copyright © 2010, Juniper Networks, Inc.
Page 125 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 Copyright © 2010, Juniper Networks, Inc.
Page 126 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 Copyright © 2010, Juniper Networks, Inc.
Page 127 OutCells: InErrors: OutErrors: InPacketDiscards: InPacketUnknownProtocol: InByteDiscards: 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: Copyright © 2010, Juniper Networks, Inc.
Page 128 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 Copyright © 2010, Juniper Networks, Inc.
Page 129 OAM VC Integrity Down Retry Count OAM VC Integrity Retry Frequency OAM alarm down count OAM alarm clear time out :3 seconds OAM continuity check :disabled Inverse ARP :disabled See show atm vc-class. show atm vp Copyright © 2010, Juniper Networks, Inc.
Page 130 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 Copyright © 2010, Juniper Networks, Inc.
Page 131 OAM fault conditions), AIS, RDI InOamF4SegmentCells—Number of F4 segment cells received 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 Copyright © 2010, Juniper Networks, Inc.
Page 132 InPacketDiscards InPacketUnknownProtocol InByteDiscards CrcErrors SAR time-outs Over-sized SDUs Sending End To End Loopback Cells Disabled: End To End OAM CC verification Disabled VP State VP Oam State :not managed InOamF4EndCells InOamF4EndCellsDropped InOamF4EndLoopbackCells InOamF4EndLoopbackCommands InOamF4EndLoopbackResponses Copyright © 2010, Juniper Networks, Inc.
Page 133 VPI number (Example 3). Field descriptions Interface—ATM interface identifier VPI—Virtual path identifier 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 Copyright © 2010, Juniper Networks, Inc.
Page 134 BGP and MPLS Configuration Guide for information about using the show mpls cross-connects atm command. See show mpls cross-connects atm. show nbma arp Use to display ARP table entries for ATM NBMA interfaces. Field descriptions IP Address—IP address of the entry Copyright © 2010, Juniper Networks, Inc.
Page 135 Chapter 1: Configuring ATM VPI/VCI—VPI and VCI of the entry Interface—Interface specifier of the entry Example host1#show nbma arp NBMA ARP Table Entries IP Address VPI/VCI Interface 1.1.1.2 0/100 2.2.2.2 0/101 See show nbma arp. Copyright © 2010, Juniper Networks, Inc.
Page 136 JunosE 11.2.x Link Layer Configuration Guide Copyright © 2010, Juniper Networks, Inc.
Page 137: Configuring Frame Relay
For a list of the modules on which you can configure Frame Relay, see ERX Module Guide, Appendix A, Module Protocol Support. Framing E Series routers support the following framing features: HDLC for data-link framing 2-byte addresses only Copyright © 2010, Juniper Networks, Inc.
Page 138: Error Frames
Frame Relay networks. These separate Frame Relay networks can be considered as subnetworks within a complete network service. Figure 4 on page 107 shows the interconnection of these types of subnetworks and the location of NNI between them. Copyright © 2010, Juniper Networks, Inc.
Page 139: Platform Considerations
See ERX Module Guide, Appendix A, Module Protocol Support for information about the modules that support Frame Relay. Interface Specifiers The interface specifier format that you use depends on the type of physical interface on which you want to configure Frame Relay. Copyright © 2010, Juniper Networks, Inc.
Page 140: References
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. host1(config)#interface serial 3/1:2/1 Copyright © 2010, Juniper Networks, Inc.
Page 141: Configuring Frame Relay
(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. host1#no frame-relay keepalive (Optional) Disable the interface. host1(config-if)#shutdown Copyright © 2010, Juniper Networks, Inc.
Page 142 Use the no version to remove the text description or alias. See frame-relay description. frame-relay interface-dlci ietf Use to configure a Frame Relay permanent virtual circuit (PVC) over a subinterface. The ietf keyword is mandatory and indicates RFC 2427 encapsulation. Copyright © 2010, Juniper Networks, Inc.
Page 143 If your router is connected by a point-to-point line, configure one end as the DTE and the other as the DCE. Example host1(config-if)#frame-relay intf-type dte Use the no version to set the default of DTE. See frame-relay intf-type. frame-relay keepalive Copyright © 2010, Juniper Networks, Inc.
Page 144 DTE version of the command is 4 events. The default for the DCE version is 2 events. Use the frame-relay lmi-t391dte command to set the T391 link integrity polling timer interval between status inquiries issued by the DTE. The network checks that the DTE Copyright © 2010, Juniper Networks, Inc.
Page 145 LMI The default is cisco. Example host1(config-if)#frame-relay lmi-type ansi Use the no version to return to the default LMI type. See frame-relay lmi-type. interface pos Use to configure a POS interface in slot/port format: Copyright © 2010, Juniper Networks, Inc.
Page 146 Use to assign an IP address and subnet mask to a subinterface. Example host1(config-subif)#ip address 192.32.10.2 255.255.255.0 Use the no version to remove an IP address or to disable IP processing. See ip address. Copyright © 2010, Juniper Networks, Inc.
Page 147 Use to enable SNMP link status processing for a Frame Relay major interface or subinterface. To enable SNMP link status processing for a Frame Relay major interface, you must issue the command from Interface Configuration mode. Copyright © 2010, Juniper Networks, Inc.
Page 148: End-To-End Fragmentation And Reassembly
If you disable fragmentation, all packets transmitted by the Frame Relay subinterface are transmitted intact. Frame Reassembly When reassembly is disabled and a data frame is received, a few scenarios may occur: Copyright © 2010, Juniper Networks, Inc.
Page 149: Map Class
Select Frame Relay as the encapsulation method for the interface. host1(config-if)#encapsulation frame-relay ietf Create a subinterface. host1(config-if)#interface serial 5/0:4/1.1 Add a circuit to a subinterface. host1(config-subif)#frame-relay interface-dlci 16 ietf Assign a local IP address to the circuit. Copyright © 2010, Juniper Networks, Inc.
Page 150 Make sure the maximum payload size is larger than any voice packet so that voice frames are not fragmented. Examples host1(config-map-class)#frame-relay fragment 100 host1(config-map-class)#frame-relay fragment fragmentation-only Use the no version to stop fragmentation and reassembly on the subinterface. See frame-relay fragment. frame-relay interface-dlci ietf Copyright © 2010, Juniper Networks, Inc.
Page 151 T1/channelized E1 interface use slot/port.channel-group.subinterface. NOTE: See “Before You Configure Frame Relay” on page 108 for more information about configuring the underlying physical interfaces. slot—Router chassis slot port—CT3, T3, or E3 module I/O port Copyright © 2010, Juniper Networks, Inc.
Page 152: Monitoring Frame Relay
See show Commands in JunosE System Basics Configuration Guide for details. 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 Copyright © 2010, Juniper Networks, Inc.
Page 153 Interface Types and Specifiers in JunosE Command Reference Guide. 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 Copyright © 2010, Juniper Networks, Inc.
Page 154 In bytes: 19728 Out bytes: 60702 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 Copyright © 2010, Juniper Networks, Inc.
Page 155 LMI request by the DTE on this interface Last sequence number sent—Last sequence number sent on this interface Last sequence number received—Last sequence number received on this interface For the DCE: Copyright © 2010, Juniper Networks, Inc.
Page 156 Enquiries received: 1233 Full enquiries received: 207 Enquiry responses sent: 1233 Full enquiry responses sent: 207 Async updates sent: 0 Last sequence number sent: 0 Last sequence number received: 0 See show frame-relay lmi. Copyright © 2010, Juniper Networks, Inc.
Page 157 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. Copyright © 2010, Juniper Networks, Inc.
Page 158 DE bit set. The DE bit may be set by the network or the user. Once it is set, it cannot be reset by the user. Out DE pkts—Number of packets transmitted with the DE bit set Dropped packets—Number of dropped packets Example Copyright © 2010, Juniper Networks, Inc.
Page 159 AdministrativelyDown—Traffic cannot flow because of manual administrative intervention Use the optional delta keyword to specify that baselined statistics are to be shown. The brief keyword displays only the operational status of all configured subinterfaces. Field descriptions Copyright © 2010, Juniper Networks, Inc.
Page 160 Time since last status change 01:21:26 In bytes: 0 Out bytes: 0 In frames: 0 Out frames: 0 In errors: 0 Out errors: 0 In discards: 0 Out discards: 0 In unknown protos: 0 See show frame-relay subinterface. Copyright © 2010, Juniper Networks, Inc.
Page 161 Unavailable—Traffic cannot flow because hardware is unavailable Example host1#show frame-relay summary 28 interface(s) defined, 28 up, 0 down 840 sub-interface(s) defined, 840 up, 0 down 840 circuit(s) defined, 840 up, 0 down See show frame-relay summary. Copyright © 2010, Juniper Networks, Inc.
Page 162 JunosE 11.2.x Link Layer Configuration Guide Copyright © 2010, Juniper Networks, Inc.
Page 163: Configuring Multilink Frame Relay
(ECMP) is one way to achieve a bandwidth greater than DS1 service without going to the expense and infrastructure required for DS3 service. MLFR is commonly used as an alternative to ECMP to deliver NxT1 service. Cost-analysis of NxT1 versus DS3 service Copyright © 2010, Juniper Networks, Inc.
Page 164: Mlfr Link Integrity Protocol
Member link sends this message to check the status of another member. Hello-Ack Member link sends this message when it receives a Hello message. Remove-Link Member link sends this message to request to leave a bundle. Copyright © 2010, Juniper Networks, Inc.
Page 165: Interface Stacking
You can configure MLFR 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 MLFR interfaces. Copyright © 2010, Juniper Networks, Inc.
Page 166: Module Requirements
On cOCx/STMx and COCX-F3 line modules, the router keeps track of the link with the least traffic. If this link cannot forward a packet, the router attempts to forward Copyright © 2010, Juniper Networks, Inc.
Page 167: Unsupported Mlfr Features
For example, if the router has multiple uplinks to a core router, packets might be received out of order across these links. Packet resequencing is therefore left as an exercise for the end station rather than the aggregation router. Copyright © 2010, Juniper Networks, Inc.
Page 168: Before You Configure Mlfr
Assign a DLCI for the subinterface. host1(config-subif)#frame-relay interface-dlci 16 ietf (Optional) Add a description to the subinterface. host1(config-subif)#frame-relay description bostonBundleSubOneDescription Assign an IP address to the subinterface. host1(config-subif)#ip address 10.10.100.1 255.255.255.0 Copyright © 2010, Juniper Networks, Inc.
Page 169: Configuration Example
Use theno version to disable MLFR on an interface. See encapsulation mlframe-relay ietf. 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 Copyright © 2010, Juniper Networks, Inc.
Page 170: Monitoring Mlfr
If a baseline has not been set, the message “ No baseline has been set” is displayed instead. The regular interface statistics and LMI statistics for interfaces are subject to the same baseline timestamp. You cannot set separate baselines for these statistics. Copyright © 2010, Juniper Networks, Inc.
Page 171 Status of the major Frame Relay 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 current protocol layer Copyright © 2010, Juniper Networks, Inc.
Page 172 Example 3 host1#show frame-relay interface mlframe-relay members Frame relay interface mlframe-relay TEST is up 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 Copyright © 2010, Juniper Networks, Inc.
Page 173 Hello Acknowledgments sent—Number of Hello messages sent from this interface 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 Copyright © 2010, Juniper Networks, Inc.
Page 174 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 Copyright © 2010, Juniper Networks, Inc.
Page 175 Last sequence number received—Last sequence number received on this interface DCE field descriptions: 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 Copyright © 2010, Juniper Networks, Inc.
Page 176 Time since last status change 00:05:39 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 Copyright © 2010, Juniper Networks, Inc.
Page 177 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: Copyright © 2010, Juniper Networks, Inc.
Page 178 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. Copyright © 2010, Juniper Networks, Inc.
Page 179 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 Copyright © 2010, Juniper Networks, Inc.
Page 180 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: Copyright © 2010, Juniper Networks, Inc.
Page 181 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 Copyright © 2010, Juniper Networks, Inc.
Page 182 2 multilink interface(s) defined, 2 up, 0 down 1 interface(s) defined, 1 up, 0 down 2 sub-interface(s) defined, 2 up, 0 down 2 circuit(s) defined, 2 up, 0 down See show frame-relay summary. Copyright © 2010, Juniper Networks, Inc.
Page 183: Configuring Upper-Layer Protocols Over Static Ethernet Interfaces
The Ethernet configuration examples in this section use combinations of these protocols. Figure 8 on page 152 illustrates how different protocols can be multiplexed over a single physical link without the use of VLANs. Copyright © 2010, Juniper Networks, Inc.
Page 184: Upper-Layer Protocols Over Static Ethernet Platform Considerations
Upper-Layer Protocols over Static Ethernet Platform Considerations You can configure upper-layer protocols over Ethernet on the following E Series Broadband Services Routers: E120 router E320 router ERX1440 router ERX1410 router ERX710 router ERX705 router ERX310 router Copyright © 2010, Juniper Networks, Inc.
Page 185: Configuring Upper-Layer Protocols Over Static Ethernet Interfaces
RFC 2516—Method for Transmitting PPP over Ethernet (PPPoE) (February 1998) Configuring IP over a Static Ethernet Interface To configure IP over an Ethernet interface: Specify a Fast Ethernet, Gigabit Ethernet, or 10-Gigabit Ethernet port. host1(config)#interface fastEthernet 4/1 Create an IP interface. Copyright © 2010, Juniper Networks, Inc.
Page 186: Configuring Pppoe Over A Static Ethernet Interface
164.10.6.51 255.255.255.0 (Optional) Configure additional PPPoE subinterfaces by completing Steps 3 through 5 using unique numbering. Figure 10 on page 154 illustrates this configuration. Figure 10: Example of PPPoE Stacking Configuration Procedure Copyright © 2010, Juniper Networks, Inc.
Page 187: Configuring Ip And Mpls Over A Static Ethernet Interface
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. Copyright © 2010, Juniper Networks, Inc.
Page 188: L2Tp And Ethernet
Use the no version to halt MPLS on the interface and delete the MPLS interface configuration. See mpls. L2TP and Ethernet Most Ethernet interfaces support L2TP. To use L2TP, you must first create a PPP interface. See L2TP Overview for information about configuring L2TP. Copyright © 2010, Juniper Networks, Inc.
Page 189: Multinetting And Ethernet
FastEthernet interfaceSpecifier—Status of the hardware on this interface up—Hardware is operational down—Hardware is not operational Administrative status—Operational state that you configured for this interface up—Interface is enabled down—Interface is disabled Hardware—Type of MAC device on this interface Copyright © 2010, Juniper Networks, Inc.
Page 190 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 Operational—Size of the largest packet processed Administrative—Setting for MTU size that you specified...
Page 191 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 ARP responses—Number of ARP responses Copyright © 2010, Juniper Networks, Inc.
Page 192 0: traffic class control, bound to FastEthernet2/0 Queue length 0 bytes Forwarded packets 1, bytes 46 Dropped committed packets 0, bytes 0 Dropped conformed packets 0, bytes 0 Dropped exceeded packets 0, bytes 0 See show interfaces. show interfaces gigabitEthernet Copyright © 2010, Juniper Networks, Inc.
Page 193 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 194 5 minute output rate—Data rates based on the traffic sent in the last 5 minutes 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 Copyright © 2010, Juniper Networks, Inc.
Page 195 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 Copyright © 2010, Juniper Networks, Inc.
Page 196 Queue length—Length of the queue, in bytes Forwarded packets, bytes—Number of packets and bytes that were forwarded on this queue Dropped committed packets, bytes—Number of committed packets and bytes that were dropped Copyright © 2010, Juniper Networks, Inc.
Page 197 In: Bytes 0, Unicast 0 Multicast 0, Broadcast 0 Errors 0, Discards 0, Mac Errors 0, Alignment 0 CRC 0, Too Longs 0, Symbol Errors 0 Out: Bytes 768, Unicast 0 Multicast 0, Broadcast 12 Copyright © 2010, Juniper Networks, Inc.
Page 198 Collisions: Single 0, Multiple 0, Late 0, Excessive 0 Policed Statistics: In: 0, Out: 0 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. Copyright © 2010, Juniper Networks, Inc.
Page 199: Configuring Vlan And S-Vlan Subinterfaces
This capability works very much like ATM encapsulation as described in RFC 2684—Multiprotocol Encapsulation over ATM Adaptation Layer 5 (September 1999). This encapsulation type enables multiplexing of multiple protocols over a single ATM virtual circuit (VC). Copyright © 2010, Juniper Networks, Inc.
Page 200: S-Vlan Overview
As described in “VLAN Overview” on page 167, VLANs permit multiplexing multiple IP interfaces and PPPoE interfaces over a single physical Ethernet port by creating VLAN subinterfaces. As specified in IEEE Standard 802.1q, the 12-bit VLAN identifier’s tagged Copyright © 2010, Juniper Networks, Inc.
Page 201: Vlan And S-Vlan Platform Considerations
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. Copyright © 2010, Juniper Networks, Inc.
Page 202: Interface Specifiers
“Configuring IP over VLAN and PPPoE over VLAN” on page 174 Creating a VLAN Major Interface To use VLANs, you must first configure the Ethernet interface for VLAN encapsulation. This creates the VLAN major interface. For example: Copyright © 2010, Juniper Networks, Inc.
Page 203: Configuring Vlan And S-Vlan Subinterfaces
(Optional) Configure additional VLAN subinterfaces by completing Steps 3 through Figure 14 on page 172 illustrates the IP/VLAN/Fast Ethernet stacking, showing two separate VLAN subinterfaces. Configure one VLAN subinterface entirely; then configure the next VLAN subinterface. Copyright © 2010, Juniper Networks, Inc.
Page 204: Configuring Pppoe Over Vlan
Assign a VLAN ID and the optional unique MAC address for the subinterface. host1(config-if)#vlan id 201 mac-address 0090.1a01.1234 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. Copyright © 2010, Juniper Networks, Inc.
Page 205: Configuring Mpls Over Vlan
To configure MPLS over VLAN over an Ethernet interface: 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. Copyright © 2010, Juniper Networks, Inc.
Page 206: Configuring Ip Over Vlan And Pppoe Over 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. Copyright © 2010, Juniper Networks, Inc.
Page 207 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. Copyright © 2010, Juniper Networks, Inc.
Page 208: Figure 17: Example Of Pppoe Over Vlan With Ip Over Vlan Stacking Configuration
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. Copyright © 2010, Juniper Networks, Inc.
Page 209 See pppoe subinterface. vlan description Use to assign an alias or description to a VLAN subinterface. You can use a maximum of 64 characters for the description or to name the alias. Example host1(config-if)#vlan description randolph56a Copyright © 2010, Juniper Networks, Inc.
Page 210: Configuring An S-Vlan Subinterface
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 Assign an S-VLAN ID and a VLAN ID for the subinterface. host1(config-if)#svlan id 4 255 Copyright © 2010, Juniper Networks, Inc.
Page 211: Configuring Pppoe Over An S-Vlan
(Optional) Configure additional PPPoE subinterfaces by completing Steps 7 through 9 using unique numbering. Figure 18 on page 180 shows one S-VLAN subinterface with multiple PPPoE subinterface stacks. NOTE: Before you can remove an S-VLAN/VLAN subinterface, you must remove the upper-layer interface stack. Copyright © 2010, Juniper Networks, Inc.
Page 212: Figure 18: Example Of Pppoe Over S-Vlan Stacking Configuration Procedure
Use the no version to remove an IP address or disable IP processing. See ip address. pppoe Use to configure PPPoE as the encapsulation method on the interface. Use the no version to disable PPPoE on the interface. See pppoe. Copyright © 2010, Juniper Networks, Inc.
Page 213 When you do not specify a unique MAC address, the VLAN uses the MAC address of the Ethernet interface. Examples host1(config-if)#svlan id 4 255 host1(config-if)#svlan id 4 255 mac-address 0090.1a01.1234 Issue the svlan id command before any upper bindings are made, such as IP or PPPoE. Copyright © 2010, Juniper Networks, Inc.
Page 214: Configuring S-Vlan Tunnels For Layer 2 Services Over Mpls
VLANs configured with an S-VLAN ID of 33 and any VLAN ID to the same destination across the MPLS network. In effect, this command tunnels traffic from all three VLANs shown in Figure 19 on page 182. host1(config-if)#svlan id 33 any Copyright © 2010, Juniper Networks, Inc.
Page 215: Interface Stacking
Layer 2 Services over MPLS in JunosE BGP and MPLS Configuration Guide. Repeat Steps 1 through 6 using unique values to configure the S-VLAN tunnel and MPLS tunnel interfaces on the remote E Series router. For example: host2(config)#interface fastEthernet 3/1 host2(config-if)#encapsulation vlan host2(config-if)#interface fastEthernet 3/1.1 Copyright © 2010, Juniper Networks, Inc.
Page 216 88a8—Specifies Ethertype value 0x88a8, as defined in draft IEEE Standard 802.1ad 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 Copyright © 2010, Juniper Networks, Inc.
Page 217: S-Vlan Oversubscription
As a result, you can oversubscribe S-VLANs by configuring up to the maximum number of S-VLANs supported on these I/O modules, knowing that no more than the maximum number of supported PPP sessions can be connected to the router at any one time. Copyright © 2010, Juniper Networks, Inc.
Page 218: Monitoring Vlan And S-Vlan Subinterfaces
Access User Exec mode or Privileged Exec mode. For information, see Accessing Command Modes in JunosE System Basics Configuration Guide. Specify the interface identifier for each VLAN subinterface that you want to monitor. host1#monitor vlan interface fastEthernet 0/0.1 fastEthernet 4/0.1 display-time-of-day Copyright © 2010, Juniper Networks, Inc.
Page 219 You must use the monitor vlan interface command in a dedicated console or terminal session for the duration of the monitoring session. Specify the interface identifier for each VLAN subinterface that you want to monitor. Copyright © 2010, Juniper Networks, Inc.
Page 220 ----------------------- -------- --------------- --------------- -------- FastEthernet 0/0.1 --/-- --/-- 10:50:33 FastEthernet 4/0.1 --/-- --/-- 10:50:33 FastEthernet 0/0.1 120120/100 120120/100 10:50:43 FastEthernet 4/0.1 120000/100 120000/100 10:50:43 FastEthernet 0/0.1 120000/100 120000/100 10:50:53 FastEthernet 4/0.1 120000/100 120000/100 10:50:53 host1#^C Copyright © 2010, Juniper Networks, Inc.
Page 221: Using Ethernet Show Commands
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 Copyright © 2010, Juniper Networks, Inc.
Page 222 Errors 0, Discards 0 See show interfaces. show interfaces gigabitEthernet show interfaces tenGigabitEthernet Use to display the status of Gigabit Ethernet interfaces, 10-Gigabit Ethernet interfaces, VLAN subinterfaces, or S-VLAN subinterfaces. You can specify the following keywords: Copyright © 2010, Juniper Networks, Inc.
Page 223 Broadcast—Number of broadcast packets sent on the VLAN or S-VLAN subinterface Errors—Total number of errors in all transmitted packets; some packets might contain more than one error Discards—Total number of discarded outgoing packets Example 1—Displays the status of a Gigabit Ethernet VLAN subinterface Copyright © 2010, Juniper Networks, Inc.
Page 224 Field descriptions Interface—Type and specifier of the VLAN subinterface Status—Status of the VLAN subinterface: up, down, dormant, lowerLayerDown, absent MTU—Maximum allowable size (in bytes) of the maximum transmission unit (MTU) for the VLAN subinterface Copyright © 2010, Juniper Networks, Inc.
Page 225 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 ARP responses—Number of ARP responses Copyright © 2010, Juniper Networks, Inc.
Page 226 Example 4—Displays full status and configuration information for all VLAN subinterfaces configured with a unique MAC address host1#show vlan subinterface mac-address Interface Svlan Id Vlan Id MAC Address ---------------------- -------- -------- -------------- FastEthernet 4/0.25 ---- 0090.dfad.2abd FastEthernet 4/0.10050 0090.adad.0abd 2 vlan subinterfaces found Copyright © 2010, Juniper Networks, Inc.
Page 227 Status Svlan Id Vlan Id Ethertype Type ------------------------ ------ ---- -------- -------- --------- ------- FastEthernet 0/0.1 1526 100 0x9100 Static FastEthernet 4/6.1 1526 100 0x9100 Dynamic 2 vlan subinterfaces found See show vlan subinterface. Copyright © 2010, Juniper Networks, Inc.
Page 228 JunosE 11.2.x Link Layer Configuration Guide Copyright © 2010, Juniper Networks, Inc.
Page 229: Configuring 802.3Ad Link Aggregation And Link Redundancy
100-Mbps Fast Ethernet link, creating a LAG bundle containing five 100-Mbps Fast Ethernet links is more cost effective than purchasing a single Gigabit Ethernet link. Copyright © 2010, Juniper Networks, Inc.
Page 230: Lacp
Fast Ether net Fast Ether net interf ace interf ace interf ace interf ace LA G b undle For information about configuring higher-level protocols over VLANs, see “Configuring VLAN and S-VLAN Subinterfaces” on page 167. Copyright © 2010, Juniper Networks, Inc.
Page 231: Load Balancing And Qos
See ERX Module Guide, Appendix A, Module Protocol Support for information about the modules that support 802.3ad link aggregation. For information about the modules that support 802.3ad link aggregation on the E120 and E320 routers: Copyright © 2010, Juniper Networks, Inc.
Page 232: Interface Specifiers
“Configuring an Ethernet Physical Interface” on page 201 “Configuring a LAG Bundle” on page 201 “Configuring IP for a LAG Bundle” on page 201 “Configuring a VLAN Subinterface for a LAG Bundle” on page 202 Copyright © 2010, Juniper Networks, Inc.
Page 233: Configuring 802.3Ad Link Aggregation And Link Redundancy
LAG interface to be considered up. host1(config-if)#minimum-links 2 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. Copyright © 2010, Juniper Networks, Inc.
Page 234: Configuring A Vlan Subinterface For A Lag Bundle
VLAN for a LAG Bundle” on page 206. Configuring MPLS for a LAG Bundle To configure MPLS for a LAG bundle, perform the following steps: Specify the LAG bundle. host1(config)#interface lag bundleBoston Copyright © 2010, Juniper Networks, Inc.
Page 235 The member with the lowest value has the highest priority, and is selected to join the LAG bundle first. Valid values are in the range 0–65535. Example host1(config-if)#lacp port-priority 100 Use the no version to restore the default value of 32768. See lacp port-priority. member-interface Copyright © 2010, Juniper Networks, Inc.
Page 236 Specify a value in the range 64–9188 bytes. The range for FE-8 I/O modules is 64–9042 bytes. This command does not work for the Fast Ethernet port on the SRP module. Example host1(config-if)#mtu 9000 Use the no version to specify the default, 1518. See mtu. pppoe subinterface lag Copyright © 2010, Juniper Networks, Inc.
Page 237: Example: Configuring An Ip Interface For A Lag Bundle
The following example displays LACP configuration for two Fast Ethernet interfaces in slot 4. The interfaces are enabled for passive LACP. The speed and duplex characteristics are the same for both interfaces. host1(config)#interface fastEthernet 4/0 host1(config-if)#speed 100 host1(config-if)#duplex full Copyright © 2010, Juniper Networks, Inc.
Page 238: Example: Configuring A Pppoe Subinterface Over A Vlan For A Lag Bundle
The following commands configure a VLAN subinterface for the LAG bundle named sunnyvale. In the LAG interface identification command (interface lag sunnyvale.1), the number 1 represents the subinterface number for the VLAN subinterface. host1(config-if)#encapsulation vlan host1(config)#interface lag sunnyvale.1 host1(config-if)#vlan id 100 Copyright © 2010, Juniper Networks, Inc.
Page 239: Example: Configuring Mpls For A Lag Bundle
5. The interfaces are enabled for active LACP. The speed and duplex characteristics are the same for both interfaces. host1(config)#interface fastEthernet 5/0 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 Copyright © 2010, Juniper Networks, Inc.
Page 240: Ethernet Link Redundancy Overview
The remote interfaces can be on the same module or on separate hardware. If LAG is not configured on the peers, LACP cannot be used to select ports; other protocols such as RSTP can be used. Copyright © 2010, Juniper Networks, Inc.
Page 241: Ethernet Link Redundancy Configuration Diagrams
GE-2 Line Module These diagrams compare physical port redundancy and link redundancy on a GE-2 line Configurations module. Figure 22 on page 210 displays a GE-2 line module with physical port redundancy on both ports. Copyright © 2010, Juniper Networks, Inc.
Page 242: Figure 22: Ge-2 Line Module Using Physical Port Redundancy
Figure 24 on page 210 displays an FE-8 line module with a link failure in a 1:N single-homed Configurations configuration. Figure 24: Single-Homed FE-8 Line Module Configuration (1:N) Figure 25 on page 211 displays an FE-8 line module with four redundant Ethernet links in a 1:1 configuration. Copyright © 2010, Juniper Networks, Inc.
Page 243: Figure 25: Fe-8 Line Module With 4 Redundant Ethernet Links (1:1)
Figure 26 on page 211 displays a single-homed 1:4 configuration on an E120 router. Figure 26: Single-Homed GE-4 IOA Configuration (1:4) Figure 27 on page 212 displays an E320 router with 1:N configuration across IOAs. Copyright © 2010, Juniper Networks, Inc.
Page 244: Ethernet Link Redundancy Behavior
When you create a LAG bundle, you can configure LACP with the Disabled, Passive, or Active states. For more information about these states, see “LACP” on page 198. The following sections describe link redundancy behavior when the: Copyright © 2010, Juniper Networks, Inc.
Page 245: Link Failure And Acquisition
It also determines whether the failover is successful. For more information, see “Member Link with Non-LAG Partner” on page 215. Copyright © 2010, Juniper Networks, Inc.
Page 246: Reverting After A Failover
For a remote end to include a member link in link aggregation, the two member links that are connected must have LACP configured. Table 10 on page 215 lists the acceptable configurations that enable redundant behavior for LACP modes at local and remote endpoints. Copyright © 2010, Juniper Networks, Inc.
Page 247: Member Link With Non-Lag Partner
The edge port designation instructs the local bridge that bridge loops do not exist through the interface, enabling it to skip the listening and learning states. Figure 29: Dual-Homed Heterogeneous Configuration in an RSTP Network Copyright © 2010, Juniper Networks, Inc.
Page 248: Acquiring Initial Links
When a network packet is received on the redundant port, the system retrieves the timestamp. If the difference in timestamps between that one and the most recent on the current active port is more than the configured failover delay time, then the Copyright © 2010, Juniper Networks, Inc.
Page 249: Configuring Ethernet Link Redundancy
By default, packet sampling is disabled. Use the optional delay keyword to control the minimum time difference to force packets on the active and redundant port to fail over. The default value is 0 milliseconds. Copyright © 2010, Juniper Networks, Inc.
Page 250: Monitoring 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 (slot/adapter/port). show interfaces lag Copyright © 2010, Juniper Networks, Inc.
Page 251 LAG bundle out-of-sync—Actor link is unable to join the correct LAG bundle collecting—Actor link is actively collecting incoming frames; if this field does not appear, the Actor link is not actively collecting incoming frames Copyright © 2010, Juniper Networks, Inc.
Page 252 Partner link’s receive machine is active port—Port number assigned to the Ethernet link by the Partner link priority—Priority assigned to the Ethernet link by the Partner link Copyright © 2010, Juniper Networks, Inc.
Page 253 Lag—Name of the LAG bundle Administrative status—Operational state that you configured for the LAG Configured MinimumLinks—Minimum number of member links are configured for the LAG bundle Member-interface—Status of the member interface in the bundle Copyright © 2010, Juniper Networks, Inc.
Page 254 (LACP active, state collecting/distributing) Lag actonBundle is Up, Administrative status is Up Member-interface FastEthernet4/0 is Up (LACP passive, state collecting/distributing) Member-interface FastEthernet4/6 is Up (LACP passive, state collecting/distributing) 2 lag interfaces found See show interfaces lag members. Copyright © 2010, Juniper Networks, Inc.
Page 255: Configuring Ieee 802.3Ah Oam Link-Fault Management
Monitoring OAM Link-Fault Management Statistics for an Interface on page 248 Monitoring OAM Link-Fault Management Configuration for an Interface on page 250 Monitoring OAM Link-Fault Management Sessions on All Configured Interfaces on page 253 Copyright © 2010, Juniper Networks, Inc.
Page 256: Ethernet Oam Link-Fault Management Overview
OAM. OAM PDUs are assigned a higher priority than regular data packets. Related Topics OAM Feature Overview on page 230 Ethernet OAM Link-Fault Management Platform Considerations on page 225 Ethernet OAM Link-Fault Management References on page 226 Copyright © 2010, Juniper Networks, Inc.
Page 257: Ethernet Oam Link-Fault Management Platform Considerations
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. Copyright © 2010, Juniper Networks, Inc.
Page 258: Ethernet Oam Link-Fault Management References
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. The format of the OAM Data/Pad field consists of TLV elements. Four types of OAM messages are supported: Copyright © 2010, Juniper Networks, Inc.
Page 259: Configuring Ieee 802.3Ah Oam Link-Fault Management
OAM clients. Figure 31 on page 228 shows the OAM sublayer interfaces. For effective interoperation and enhanced collaboration with 802.3ad link aggregation, the OAM sublayer exists below the LAG bundle. The LAG bundle is present between the OAM sublayer and the MAC client. Copyright © 2010, Juniper Networks, Inc.
Page 260: Oam Client
OAM PDUs to and from a client. 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 229 shows Copyright © 2010, Juniper Networks, Inc.
Page 261: Control Block
OAM PDUs are delivered to the control block. MAC client frames are transmitted to the superior sublayer. Loopback frames are distributed to the multiplexer. Related Topics OAM Client on page 228 OAM Elements Overview on page 227 Copyright © 2010, Juniper Networks, Inc.
Page 262: Oam Feature Overview
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, Copyright © 2010, Juniper Networks, Inc.
Page 263: Information Oam Pdu Components
You can configure the PDU timer, which is the rate at which Information OAM PDUs are sent to the remote peer to keep the OAM association active, in the range of milliseconds with Copyright © 2010, Juniper Networks, Inc.
Page 264: Oam Link Monitoring Feature
OAM peer, the OAM function attempts to alter the operational state of the link whenever the high threshold value is exceeded. The monitoring of the link continues with a new window or period as long as the operational state of the link is up. Copyright © 2010, Juniper Networks, Inc.
Page 265: Supported Error Events For Tracking Link Faults
OAM session is marked as down/nonfunctional after the configured action is taken on the link. Related Topics OAM Feature Overview on page 230 Copyright © 2010, Juniper Networks, Inc.
Page 266: Oam Remote Fault Detection Feature
The local entity influences the state of the link based on an Information OAM PDU with the Critical Event bit set in the Flags field that it receives from the remote peer. Copyright © 2010, Juniper Networks, Inc.
Page 267: Oam Remote And Local Loopback Feature
OAM entities from simultaneously placing each other into loopback mode by making sure that the lower valued source address is the entity that is placed in loopback mode (Figure 32 on page 229). Copyright © 2010, Juniper Networks, Inc.
Page 268: Interrelationship Of Oam Link-Fault Management With Ethernet Subsystems
LAC protocol. For example, if the configured symbol-period threshold is exceeded, you can configure the link aggregator to remove the member link from the bundle and rebalance the bundle. Where a LAG member link is designated as Copyright © 2010, Juniper Networks, Inc.
Page 269: Guidelines For Configuring 802.3Ah Oam Link-Fault Management
Ethernet OAM interface to be more than two seconds. 802.3ah OAM functionality is not supported on SRP Ethernet interfaces. Also, JunosE Software does not support unidirectional operation of Ethernet OAM links, which enable Copyright © 2010, Juniper Networks, Inc.
Page 270: Configuring 802.3Ah Oam Link-Fault Management
802.3ah OAM functionality. An OAM entity in active mode initiates the discovery process by sending an Information OAM PDU to the multicast address of the slow protocol (0180.c200.0002) at a configured rate. In a carrier environment, the Copyright © 2010, Juniper Networks, Inc.
Page 271 Errored Frame Event TLV to be sent to the remote OAM entity. The Errored Frame Event TLV counts the number of errored frames detected during the specified period. host1(config-if)#ethernet oam lfm link-monitor frame-seconds threshold high Copyright © 2010, Juniper Networks, Inc.
Page 272 Specify a period of time in which frame seconds summary error events are counted for both high and low threshold settings. The time period used for counting events is specified in seconds. host1(config-if)#ethernet oam lfm link-monitor frame-seconds-summary window Copyright © 2010, Juniper Networks, Inc.
Page 273 Ethernet OAM interface. You can configure the OAM application to influence the operational state of the link, when a link quality threshold is exceeded or a critical event PDU is received from the peer, or both. If you configured the action for an OAM Copyright © 2010, Juniper Networks, Inc.
Page 274 Enable the remote loopback operation on a remote OAM entity, which causes the remote entity at the specified Gigabit Ethernet interface to loop any received non-OAM PDUs back to the local entity. host1#ethernet oam lfm remote-loopback start interface gigabitEthernet 1/0 Copyright © 2010, Juniper Networks, Inc.
Page 275 Monitoring OAM Link-Fault Management Configuration for an Interface on page 250 Monitoring OAM Link-Fault Management Discovery Settings for an Interface on page 245 Monitoring OAM Link-Fault Management Statistics for an Interface on page 248 Copyright © 2010, Juniper Networks, Inc.
Page 276: Example: Configuring 802.3Ah Oam Link-Fault Management And Enabling Remote Failure Monitoring On An Interface
20 host1(config-if)#ethernet oam lfm link-monitor frame-seconds window 300 Related Topics Configuring 802.3ah OAM Link-Fault Management on page 238 ethernet oam lfm mode ethernet oam lfm high-threshold ethernet oam lfm link-monitor frame-seconds Copyright © 2010, Juniper Networks, Inc.
Page 277: Example: Enabling Remote Loopback Support On The Local Interface
Mode : active Capabilities : link events Mux Action : Forwarding Parser Action : Forwarding Remote(0090.690a.0202): Mode : passive Capabilities : link events, loopback, variable retrieval Mux Action : Forwarding Parser Action : Forwarding Copyright © 2010, Juniper Networks, Inc.
Page 278: Table 11: Show Ethernet Oam Lfm Discovery Output Fields
The default discovery mode of the OAM client is active passive—An OAM entity does not initiate the discovery process. You cannot perform link-fault management if you configure both the local client and the remote peer for passive mode operation Copyright © 2010, Juniper Networks, Inc.
Page 279 IEEE 802.3ah OAM functionality. passive—An OAM entity does not initiate the discovery process. You cannot perform link-fault management if you configure both the local client and the remote peer for passive mode operation Copyright © 2010, Juniper Networks, Inc.
Page 280: Monitoring Oam Link-Fault Management Statistics For An Interface
To display details about the Ethernet OAM link-fault management packets that are analyzed by a specific interface: host1#show ethernet oam lfm statistics GigabitEthernet 4/1 GigabitEthernet 4/1 Information OAMPDUs :291 Event Notification OAMPDUs Errored Frame Errored Symbol Duplicate Event Notification OAMPDUs Copyright © 2010, Juniper Networks, Inc.
Page 281: Table 12: Show Ethernet Oam Lfm Statistics Output Fields
Unsupported OAMPDUs Number of unsupported OAM PDUs sent Details about the types of PDUs that are received on the interface Information OAMPDUs Number of Information OAM PDUs received on the interface from the remote peer Copyright © 2010, Juniper Networks, Inc.
Page 282: Monitoring Oam Link-Fault Management Configuration For An Interface
Action To display the runtime settings of link-monitoring and general OAM operations for a particular interface: host1#show ethernet oam lfm status GigabitEthernet 4/0 GigabitEthernet 4/0 Mode: Passive Transmit-interval: 1000 ms Loss-threshold: 5 packets Copyright © 2010, Juniper Networks, Inc.
Page 283: Table 13: Show Ethernet Oam Lfm Status Output Fields
GE-2 and GE-HDE line modules that are paired with GE-2 SFP I/O modules with physical link redundancy, causes the transition of the link from active to redundant Copyright © 2010, Juniper Networks, Inc.
Page 284 Highest value for frame error events in number of frames, which when exceeded causes an action to be triggered Symbol-errors Error Monitor Displays a detailed classification of symbol errors event TLVs since the OAM sublayer was reset Copyright © 2010, Juniper Networks, Inc.
Page 285: Monitoring Oam Link-Fault Management Sessions On All Configured
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 Loopback: Supported, Remote enabled Copyright © 2010, Juniper Networks, Inc.
Page 286: Table 14: Show Ethernet Oam Lfm Summary Output Fields
Passive—An OAM entity does not initiate the discovery process. You cannot perform link-fault management if you configure both the local client and the remote peer for passive mode operation Remote address MAC Address of the remote peer Copyright © 2010, Juniper Networks, Inc.
Page 287 Send Local Remote Ok state. If at any time the settings on the local OAM client change resulting in the remote OAM client becoming unsatisfied with the settings, the OAM discovery process returns to the Send Local Remote Ok state Copyright © 2010, Juniper Networks, Inc.
Page 288 OAM PDUs to the local OAM entity Related Topics Configuring 802.3ah OAM Link-Fault Management on page 238 Copyright © 2010, Juniper Networks, Inc.
Page 289 Chapter 7: Configuring IEEE 802.3ah OAM Link-Fault Management show ethernet oam lfm summary Copyright © 2010, Juniper Networks, Inc.
Page 290 JunosE 11.2.x Link Layer Configuration Guide Copyright © 2010, Juniper Networks, Inc.
Page 291: Configuring Point-To-Point Protocol
The router supports dynamic PPP interfaces. For details, see “Configuring Dynamic Interfaces” on page 511. Framing The software restricts the use of the general HDLC protocol (RFC 1662) to unnumbered mode: HDLC address field is 0xFF (all stations) Copyright © 2010, Juniper Networks, Inc.
Page 292: Error Frames
Magic number—Randomly generated number used to identify one end of a point-to-point connection. Each side negotiates its magic number, taking note of each other’s magic number. If both sides discover that the magic numbers they are Copyright © 2010, Juniper Networks, Inc.
Page 293: Validation Of Lcp Peer Magic Number
In this situation, the router expects to receive a null magic number from the peer, and terminates the PPP connection unless you configure it to ignore the peer magic number mismatch and retain the connection. Copyright © 2010, Juniper Networks, Inc.
Page 294: B-Ras Support
Internet Protocol Control Protocol (IPCP) extensions for Windows Internet Name Service (WINS) and Domain Name System (DNS) name server addresses Password Authentication Protocol (PAP) Challenge Handshake Authentication Protocol (CHAP) Keepalive timeout Session timeout Inactivity timeout Accounting Copyright © 2010, Juniper Networks, Inc.
Page 295: Configuring Point-To-Point Protocol
EAP client on the peer. 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: Copyright © 2010, Juniper Networks, Inc.
Page 296: Eap Types
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. You cannot configure the number of retransmission attempts. Copyright © 2010, Juniper Networks, Inc.
Page 297: Eap Behavior In An L2Tp Environment
The size of EAP packets and fragments tends to be larger than the buffer exchange limit—1450 bytes—between the controllers. This intercontroller buffer exchange limit is tuned for the optimal system performance and scalability; also, when Copyright © 2010, Juniper Networks, Inc.
Page 298: Performance
EAP authentication methods fragment packets when the EAP packet size is greater than the link MTU. The EAP server must fragment the EAP packet to the size of the Framed-Mtu attribute contained in the RADIUS Access-Request packet. Copyright © 2010, Juniper Networks, Inc.
Page 299: Remote Peer Scenarios During Negotiation Of Ppp Options
This is treated as a renegotiation request and B-RAS sends an ACK/NAK until max renegotiation and max configure-nak counters are exceeded, respectively The CPE starts renegotiation without the prompted options B-RAS renegotiates, until max renegotiation is exceeded Copyright © 2010, Juniper Networks, Inc.
Page 300: Ipcp Lockout And Local Ip Address Pool Restoration
You can use the ppp peer-ip-address-optional command in Global Configuration mode to specify that the peer IP address is optional. By default, this command is disabled. This feature also supports high availability (HA) and unified in-service software upgrade (Unified ISSU). Copyright © 2010, Juniper Networks, Inc.
Page 301: Platform Considerations
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 PPP. Copyright © 2010, Juniper Networks, Inc.
Page 302: Interface Specifiers
RFC 2246—The TLS Protocol Version 1.0 (January 1999) RFC 2615—PPP over SONET/SDH (June 1999) RFC 2716—PPP EAP TLS Authentication Protocol (October 1999) RFC 3032—MPLS Label Stack Encoding (January 2001) RFC 3579—RADIUS EAP (September 2003) RFC 3748—Extensible Authentication Protocol (EAP) (June 2004) Copyright © 2010, Juniper Networks, Inc.
Page 303: Before You Configure Ppp
Assign an IP address and subnet mask for the interface. host1(config-if)#ip address 192.168.22.10 255.255.255.0 Verify that your configuration changes are correct. host1#show ppp interface serial 3/0:2/5 config encapsulation ppp Use to configure PPP as the encapsulation method. Example host1(config-if)#encapsulation ppp Copyright © 2010, Juniper Networks, Inc.
Page 304 PPP. To specify a POS interface for ERX7xx models, ERX14xx models, and ERX310 router, use the slot/port.[subinterface ] format. slot—Number of the chassis slot port—Port number on the I/O module subinterface—Number of the subinterface Copyright © 2010, Juniper Networks, Inc.
Page 305 Use to assign an IP address and subnet mask for a PPP interface. Example host1(config-if)#ip address 192.168.22.10 255.255.255.0 Use the no version to remove an IP address or disable IP processing. See ip address. Copyright © 2010, Juniper Networks, Inc.
Page 306: Optional Configuration Tasks
When the time interval elapses, the subscriber must connect again to negotiate IPCP. Example host1(config-subif)#ppp ipcp lockout Use the no version to disable the IPCP lockout option on the interface. See ppp ipcp lockout. ppp ipcp netmask Copyright © 2010, Juniper Networks, Inc.
Page 307 30 seconds. If the keepalive interval is 30 seconds, a failed link is detected between 90 and 120 seconds after failure. Use ppp keepalive without a value to restore the default, 30 seconds. Copyright © 2010, Juniper Networks, Inc.
Page 308 LCP, IPCP, and IPv6CP to the value you specify, or to the default value (30) if you omit the optional value for maximum renegotiation attempts. Copyright © 2010, Juniper Networks, Inc.
Page 309 576 Use the no version to restore the default value, which causes PPP to use the lower-layer MRU minus the PPP header length as the MRU value. See ppp mru. ppp passive-mode Copyright © 2010, Juniper Networks, Inc.
Page 310 Example host1(config)#ppp peer-ip-address-optional Use the no version to restore the default behavior See ppp peer-ip-address-optional. ppp shutdown ppp shutdown ip ppp shutdown ipv6 ppp shutdown mpls ppp shutdown osi Copyright © 2010, Juniper Networks, Inc.
Page 311: Configuring Ppp Authentication
VR. This means that RADIUS can override the default VR context with a new VR context during the authentication process. When the ppp authentication virtual-router command specifies the default VR, AAA returns either the default VR or the VR specified by RADIUS. Copyright © 2010, Juniper Networks, Inc.
Page 312 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. If PAP is also rejected, then PPP terminates the session. Copyright © 2010, Juniper Networks, Inc.
Page 313: Ppp Accounting Statistics
The acknowledgment is either a CHAP success or PAP acknowledgement packet. All subsequent traffic is counted up the point that PPP at the router terminates the subscriber's session. The statistics are reported in the following RADIUS attributes: Attribute Number Attribute Name Acct-Input-Octets Copyright © 2010, Juniper Networks, Inc.
Page 314: Monitoring Ppp Interfaces
You can set a statistics baseline for PPP interfaces using the baseline ppp commands. Use the optional delta keyword with PPP show commands to show baselined statistics. Copyright © 2010, Juniper Networks, Inc.
Page 315 Interface alias—Alias or description of the PPP interface Interface administrative status—Indicates whether the interface is administratively enabled (open), meaning that the no ppp shutdown command is operational; or Copyright © 2010, Juniper Networks, Inc.
Page 316 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) Copyright © 2010, Juniper Networks, Inc.
Page 317 (true or false) administrative-status—OSINLCP administrative status (open or closed) OSINLCP protocol status 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 Copyright © 2010, Juniper Networks, Inc.
Page 318 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 Copyright © 2010, Juniper Networks, Inc.
Page 319 LCP protocol statistics—Shows the following statistics for the life of the interface (since system boot or interface creation, whichever is later) Copyright © 2010, Juniper Networks, Inc.
Page 320 IP address mask peer-primary-dns-address—IP address to be used in negotiation of the peer primary DNS address peer-secondary-dns-address—IP address to be used in negotiation of the peer secondary DNS address Copyright © 2010, Juniper Networks, Inc.
Page 321 EAP protocol configuration Copyright © 2010, Juniper Networks, Inc.
Page 322 This applies to an interface only. max configure exceeded—Maximum number of configure requests was exceeded while negotiations were in progress. This means that there was no response from Copyright © 2010, Juniper Networks, Inc.
Page 323 OSINLCP protocol status operational-status not present Interface statistics packets octets 14515 11296 errors discards policed LCP protocol configuration max-receive-unit use lower layer authentication magic-number enabled magic-number-mismatch reject keepalive-timer 30 seconds restart-timer 3 seconds max-terminate max-configure max-failure Copyright © 2010, Juniper Networks, Inc.
Page 324 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 EAP Protocol Configuration request-retry request-timeout 3 seconds Example 2—Provides detailed output for a particular IPv6 interface Copyright © 2010, Juniper Networks, Inc.
Page 325 30 seconds restart-timer 3 seconds max-terminate max-configure max-failure passive-mode disabled LCP protocol status link-status initial LCP protocol statistics in-keepalive-requests out-keepalive-requests in-keepalive-replies out-keepalive-replies keepalive-failures Authentication configuration authenticate-retry authentication-router Copyright © 2010, Juniper Networks, Inc.
Page 326 IPv6CP , OSINLCP, or MPLS configured—Interface or protocol is configured notConfigured—Interface or protocol is not configured Administrative status—Indicates the administrative state of the PPP interface, IPCP, IPv6CP , OSINLCP, or MPLS open—Interface or protocol is administratively enabled Copyright © 2010, Juniper Networks, Inc.
Page 327 Ipv6 4000 4000 Mpls 4000 Operational status down notPresent noResources Interface 4000 4000 Ipv6 4000 4000 Mpls 4000 Operational status lowerDown passive tunnel Interface PPP Multilink Status Configuration status configured notConfigured Link Interface 8000 Copyright © 2010, Juniper Networks, Inc.
Page 328: Troubleshooting
Use to configure a trace log file for a PPP interface. Specify one of the following interface types and an interface specifier. For example, specify slot/port:channel/subchannel for a serial POS PPP interface. serial—Serial interface Copyright © 2010, Juniper Networks, Inc.
Page 329 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. Copyright © 2010, Juniper Networks, Inc.
Page 330 JunosE 11.2.x Link Layer Configuration Guide Copyright © 2010, Juniper Networks, Inc.
Page 331: Configuring Multilink Ppp
The router acts on MLPPP like another PPP Network Control Protocol (NCP). Packets received with an MLPPP header are subject to fragmentation, reassembly, and sequencing. Packets received without the MLPPP header cannot be sequenced and can be delivered only on a first-come, first-served basis. Copyright © 2010, Juniper Networks, Inc.
Page 332: Application
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 Copyright © 2010, Juniper Networks, Inc.
Page 333: Mlppp Link Selection
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. Copyright © 2010, Juniper Networks, Inc.
Page 334: Platform Considerations
“ppp hash-link-selection” on page 313. Platform Considerations You can configure MLPPP interfaces on the following E Series Broadband Services Routers: E120 router E320 router ERX1440 router ERX1410 router ERX710 router ERX705 router ERX310 router Copyright © 2010, Juniper Networks, Inc.
Page 335: Configuring Multilink Ppp
For more information about the MLPPP protocol and MLPPP fragmentation and reassembly, consult the following resources: 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) Copyright © 2010, Juniper Networks, Inc.
Page 336: Supported Mlppp Features
“MLPPP Link Selection” on page 301. For details on enabling MLPPP reassembly, see “Configuring MLPPP Fragmentation and Reassembly” on page 320. Multiclass MLPPP For information about multiclass MLPPP, see “Configuring Multiclass Multilink PPP” on page 345. Copyright © 2010, Juniper Networks, Inc.
Page 337 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) Copyright © 2010, Juniper Networks, Inc.
Page 338 On an ES2-S1 GE-4 IOA, ES2-S1 GE-8 IOA, ES2-S1 OC3-8 STM1 ATM IOA, and ES2-S1 OC12-2 STM4 ATM IOA modules that pair with an ES2 4G LM on E120 and E320 routers, you can configure: MLPPP bundles with one or more links per bundle for dynamic MLPPP-over-PPPoE-over-Ethernet configurations. Copyright © 2010, Juniper Networks, Inc.
Page 339: Unsupported Mlppp Features
Protocol Support. For information about the modules that support MLPPP on the E120 and E320 routers, see E120 and E320 Module Guide, Appendix A, IOA Protocol Support. Unsupported MLPPP Features The router does not support the following MLPPP features: Copyright © 2010, Juniper Networks, Inc.
Page 340: Before You Configure Static Mlppp
Static MLPPP configuration consists of two general tasks, each with several subtasks. To configure static MLPPP: Create the member links to be aggregated into a multilink bundle. From Global Configuration mode, specify the individual interface on which you want to configure MLPPP. Copyright © 2010, Juniper Networks, Inc.
Page 341: Configuration Example
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 Copyright © 2010, Juniper Networks, Inc.
Page 342: Contextual Command Differences
Perform the following optional tasks to configure authentication on interfaces with MLPPP encapsulation or MLPPP bundles. Specify one or more PPP authentication types. Modify the length of the CHAP challenge. Specify the maximum number of retries. Copyright © 2010, Juniper Networks, Inc.
Page 343 Example 2—Specify a virtual router for the authentication virtual router context. This command is available in static configurations and in profiles. host1(config-if)#ppp authentication virtual-router boston pap chap Use the no version to specify that the router does not require authentication. See ppp authentication. ppp chap-challenge-length Copyright © 2010, Juniper Networks, Inc.
Page 344: Configuring Other Ppp Attributes
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, also referred to as an MLPPP bundle member. Example host1(config)#interface serial 2/0:1/1 host1(config-if)#encapsulation mlppp Copyright © 2010, Juniper Networks, Inc.
Page 345 You can configure hash-based MLPPP link selection in any of the following ways: To configure hash-based link selection for an individual MLPPP member link interface, issue the ppp hash-link-selection command from Interface Configuration mode or Copyright © 2010, Juniper Networks, Inc.
Page 346 For more information about how the IPv4 addresses are restored, see Chapter 7, Configuring Point-to-Point Protocol. Example host1(config-subif)#ppp ipcp lockout Use the no version to disable the IPCP lockout option on the interface. See ppp ipcp lockout. Copyright © 2010, Juniper Networks, Inc.
Page 347 If issued in the context of an MLPPP bundle, the command affects all MLPPP link interfaces that are member links of that bundle. Issuing this command prevents the router from detecting loopback configurations. Example host1(config-if)#ppp magic-number disable Copyright © 2010, Juniper Networks, Inc.
Page 348 IPv4 interface and the IPv6 interface. Example 1—Sets the maximum number of LCP renegotiation attempts to 5 host1(config-if)#ppp max-negotiations lcp 5 Example 2—Sets the maximum number of IPCP renegotiation attempts to 30 (the default) Copyright © 2010, Juniper Networks, Inc.
Page 349 Use to force a static or dynamic PPP interface into passive mode, for a period of one second, before LCP negotiation begins. 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. See ppp passive-mode. Copyright © 2010, Juniper Networks, Inc.
Page 350 If you add new member links while a bundle is shut down, those new members are also in the shut-down state until the entire bundle is brought up. Use the no version to restart a disabled session. See ppp shutdown. Copyright © 2010, Juniper Networks, Inc.
Page 351: Configuring Dynamic Mlppp
MLPPP interfaces. See ppp multilink enable. profile Use to create a profile. Specify a profile name with up to 80 characters. Example host1(config)#profile dynmlppp1 Use the no version to remove a profile. See profile. Copyright © 2010, Juniper Networks, Inc.
Page 352: Configuring Mlppp Fragmentation And Reassembly
For a list of the line modules and corresponding I/O modules that support MLPPP fragmentation and reassembly on ERX7xx models, ERX14xx models, and the ERX310 router, see ERX Module Guide, Appendix A, Module Protocol Support. Copyright © 2010, Juniper Networks, Inc.
Page 353: Link Configuration Parameters
Guidelines for MLPPP Reassembly Use the following guidelines when you configure MLPPP reassembly on a link interface: Copyright © 2010, Juniper Networks, Inc.
Page 354: Bundle Validation Failure
4/0:1/1/1/1/1 Specify MLPPP as the encapsulation method on the link interface. host1(config-if)#encapsulation mlppp Enable fragmentation on the link interface, and optionally specify the maximum allowable fragment size to use. host1(config-if)#ppp fragmentation 128 Copyright © 2010, Juniper Networks, Inc.
Page 355: Static Mlppp Over Atm 1483 Example
2/0.2 host1(config-subif)#atm pvc 42 0 42 aal5snap host1(config-subif)#encapsulation mlppp host1(config-subif)#ppp fragmentation host1(config-subif)#ppp reassembly 1400 host1(config-subif)#ppp authentication pap chap host1(config-subif)#exit host1(config)#interface atm 2/0.3 host1(config-subif)#atm pvc 43 0 43 aal5snap host1(config-subif)#encapsulation mlppp host1(config-subif)#ppp fragmentation Copyright © 2010, Juniper Networks, Inc.
Page 356: Configuring Fragmentation And Reassembly For Dynamic Mlppp
You cannot specify the administrative MRRU for a link when reassembly is disabled. (Optional) Specify a virtual router to which dynamic IP interfaces created with this profile will be assigned. Copyright © 2010, Juniper Networks, Inc.
Page 357: Dynamic Mlppp Over Pppoe Example
1590 host1(config-profile)#ppp reassembly 1590 host1(config-profile)#ppp fragmentation 128 host1(config-profile)#pppoe session 8000 host1(config-profile)#exit host1(config)#l2tp destination profile lac ip address 193.1.1.2 host1(config-l2tp-dest-profile)#remote host xxx.com host1(config-l2tp-dest-profile-host)#enable proxy authenticate host1(config-l2tp-dest-profile-host)#tunnel password welcome Copyright © 2010, Juniper Networks, Inc.
Page 358 (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. Copyright © 2010, Juniper Networks, Inc.
Page 359: Configuring Fragmentation And Reassembly For Mlppp Bundles
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 Copyright © 2010, Juniper Networks, Inc.
Page 360: Configuring Multiclass Mlppp
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). baseline ppp interface Copyright © 2010, Juniper Networks, Inc.
Page 361 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 Copyright © 2010, Juniper Networks, Inc.
Page 362 The following command displays PPP interface (including MLPPP interface) statistics Baseline with baselining: 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 octets errors discards PPP interface serial 2/0:5/1 is up Copyright © 2010, Juniper Networks, Inc.
Page 363 PPP multilink member-interface serial 2/1:2/1 is up Time since last baseline 00:00:25 Interface statistics packets octets errors discards PPP multilink member-interface serial 2/1:3/1 is up Time since last baseline 00:00:30 Interface statistics Copyright © 2010, Juniper Networks, Inc.
Page 364 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 Copyright © 2010, Juniper Networks, Inc.
Page 365 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: Copyright © 2010, Juniper Networks, Inc.
Page 366 (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 Copyright © 2010, Juniper Networks, Inc.
Page 367 (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” for any negotiated option parameters if the option was not negotiated. Copyright © 2010, Juniper Networks, Inc.
Page 368 PPP multilink interface serial 2/1:3/1 is up Example 4—Displays configuration information about MLPPP member links configured in bundle group1 host1#show ppp interface mlppp group1 config PPP interface mlppp group1 is up Network interface administrative status is open Copyright © 2010, Juniper Networks, Inc.
Page 369 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 errors discards 1 mlppp interfaces found Copyright © 2010, Juniper Networks, Inc.
Page 370 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 Copyright © 2010, Juniper Networks, Inc.
Page 371 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 Copyright © 2010, Juniper Networks, Inc.
Page 372 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 Copyright © 2010, Juniper Networks, Inc.
Page 373 LCP confReq message tunnel—Interface is being redirected through a tunnel Copyright © 2010, Juniper Networks, Inc.
Page 374 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 2000 Ipv6 2000 2000 Copyright © 2010, Juniper Networks, Inc.
Page 375 Chapter 9: Configuring Multilink PPP Mpls 2000 Operational status lowerDown passive tunnel Link Interface Network Interface See show ppp interface summary. Copyright © 2010, Juniper Networks, Inc.
Page 376 JunosE 11.2.x Link Layer Configuration Guide Copyright © 2010, Juniper Networks, Inc.
Page 377: Configuring Multiclass Multilink Ppp
Fragmentation is the process by which a large packet is broken up into multiple smaller fragments for simultaneous transmission across multiple links of an MLPPP bundle. Reassembly is the process by which the destination router reassembles the fragments into the original packets. Copyright © 2010, Juniper Networks, Inc.
Page 378: Multiclass Mlppp Configuration Guidelines
The default traffic class is the best-effort traffic class. You can configure fragmentation and reassembly on all traffic classes. Any packet without a traffic-class-to-multilink-class mapping is transmitted without a multiclass MLPPP header. Copyright © 2010, Juniper Networks, Inc.
Page 379: Multiclass Mlppp Lcp Extensions Overview
Configuring Multiclass MLPPP on page 348 Link Control Protocol in Chapter 8, Point-to-Point Protocol Multiclass MLPPP Platform Considerations You can configure multiclass MLPPP on the following E Series Broadband Services Routers: E120 router E320 router Copyright © 2010, Juniper Networks, Inc.
Page 380: Module Requirements
MLPPP interface and assign QoS traffic classes to the multilink classes. You can configure multiclass MLPPP on a static MLPPP interface or in a dynamic profile for a dynamic MLPPP interface. To configure multiclass MLPPP: Copyright © 2010, Juniper Networks, Inc.
Page 381: Configuring Multiclass Multilink Ppp
From Global Configuration mode, specify the individual interface on which you want to configure multiclass MLPPP. 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. Copyright © 2010, Juniper Networks, Inc.
Page 382: Configuring Traffic Classes On Multiclass Mlppp Interfaces
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: Copyright © 2010, Juniper Networks, Inc.
Page 383: Configuring Reassembly On Multiclass Mlppp Interfaces
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. Copyright © 2010, Juniper Networks, Inc.
Page 384: Example: Configuring Multiclass Mlppp On A Dynamic Interface
Configuring a Profile in 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 low-loss low-latency Related Topics Configuring Multiclass MLPPP on page 348 Copyright © 2010, Juniper Networks, Inc.
Page 385: Example: Configuring Multiclass Mlppp On A Static Interface
Link interface administrative status is open PPP multilink multiclass is enabled PPP multilink multiclass classes 4 PPP multilink multiclass fragmentation is enabled on “voice”, otherData” PPP multilink multiclass reassembly is enabled on “voice”, ”otherData” Copyright © 2010, Juniper Networks, Inc.
Page 386 PPP multilink multiclass reassembly is enabled on “voice”, ”otherData” LCP negotiated options local peer max-receive-unit 1590 1590 max-receive-reconstructed-unit 1590 1590 authentication none none magic-number 0x78b5606f 0x5aa2de54 none none acfc none none multiclass-classes multiclass-sequence-format long long Copyright © 2010, Juniper Networks, Inc.
Page 387: Table 17: Show Ppp Interface Mlppp Output Fields
Copyright © 2010, Juniper Networks, Inc.
Page 388 (none or enabled) for the local and remote (peer) side of the link multiclass-classes—Number of multilink classes negotiated multiclass-sequence-format—Format of the negotiated sequence number: long or short Copyright © 2010, Juniper Networks, Inc.
Page 389 Chapter 10: Configuring Multiclass Multilink PPP Related Topics Configuring Multiclass MLPPP on page 348 show ppp interface Copyright © 2010, Juniper Networks, Inc.
Page 390 JunosE 11.2.x Link Layer Configuration Guide Copyright © 2010, Juniper Networks, Inc.
Page 391: Configuring Packet Over Sonet
The router supports PPP, Cisco High-Level Data Link Control (HDLC), and Frame Relay over SONET/SDH. POS Features POS supports the following features: Payload scrambling Clock source configuration Maximum transmission unit (MTU) size configuration Maximum receive unit (MRU) size configuration Copyright © 2010, Juniper Networks, Inc.
Page 392: Sonet/Sdh
4.876640 Gbps OC192 STM64 9.953280 Gbps Platform Considerations You can configure POS interfaces on the following E Series Broadband Services Routers: E120 router E320 router ERX1440 router ERX1410 router ERX710 router ERX705 router ERX310 router Copyright © 2010, Juniper Networks, Inc.
Page 393: Configuring Packet Over Sonet
Interface Types and Specifiers in JunosE Command Reference Guide. References For more information about POS interfaces, consult the following resources: RFC 1662—PPP in HDLC-like Framing (July 1994) RFC 2615—PPP over SONET/SDH (June 1999 RFC 2427—Multiprotocol Interconnect over Frame Relay (September 1998) Copyright © 2010, Juniper Networks, Inc.
Page 394: Before You Configure Pos
(Optional) Set the time interval at which the router calculates bit and packet rate counters. host1(config-if)#load-interval 90 (Optional) Set the type of loopback mode. host1(config-if)#loopback line (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. Copyright © 2010, Juniper Networks, Inc.
Page 395 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 Copyright © 2010, Juniper Networks, Inc.
Page 396 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 Copyright © 2010, Juniper Networks, Inc.
Page 397 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 interfaces pos” on page 367 to display the text description. Example Copyright © 2010, Juniper Networks, Inc.
Page 398: Monitoring Pos
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. See show Commands in JunosE System Basics Configuration Guide, for details. Copyright © 2010, Juniper Networks, Inc.
Page 399 Field descriptions POS interface status—State of the physical interface: up, down Description—Text description or alias if configured for the interface Copyright © 2010, Juniper Networks, Inc.
Page 400 Example host1#show interfaces pos 8/0 Packet over SONET interface 8/0 is ifOperUp Description: houston80 pos interface snmp trap link-status = disabled Encapsulation ppp SONET path operational status: up time since last status change: 00:20:37 Copyright © 2010, Juniper Networks, Inc.
Page 401 5 minute input rate 24910848 bits/sec, 1023242 packets/sec 5 minute output rate 24905728 bits/sec, 1023233 packets/sec Interface statistics Packets received 1066995954 Bytes received 3836558195 Errored packets received Packets sent 1055275550 Bytes send 3039550548 Errored packets sent See show interfaces. Copyright © 2010, Juniper Networks, Inc.
Page 402 JunosE 11.2.x Link Layer Configuration Guide Copyright © 2010, Juniper Networks, Inc.
Page 403: Configuring Point-To-Point Protocol Over Ethernet
E Series routers use PPP over Ethernet (PPPoE) to enable multiple hosts to open PPP sessions to the router using one or more bridging modems. When service providers want to maintain the session abstraction associated with PPP, PPPoE is used with Broadband Copyright © 2010, Juniper Networks, Inc.
Page 404: Pppoe Stages
One or more remote ACs respond to the PADI packet by sending a PPPoE Active Discovery Offer (PADO) packet, indicating that they can serve the client request. The PADO packet includes the name of the AC from which it was sent. Copyright © 2010, Juniper Networks, Inc.
Page 405: Configuring Point-To-Point Protocol Over Ethernet
The default action associated with the unknown service name tag depends on the PPPoE service name table configuration. If all the services in the table are configured to drop, the default action for the unknown service name tag is terminate. If all the Copyright © 2010, Juniper Networks, Inc.
Page 406: Features
(“ ” ) associated with the drop action; and an unknown service name tag associated with the drop action. Table 19: Sample PPPoE Service Name Table Service Name Action “myISPService” Terminate “myQOSClass1” Terminate “myQOSClass2” Drop Copyright © 2010, Juniper Networks, Inc.
Page 407: Enabling The Service Name Table For Use
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 Copyright © 2010, Juniper Networks, Inc.
Page 408: Pppoe Remote Circuit Id Capture
Include the NAS-Identifier [32] RADIUS attribute host1(config)#radius remote-circuit-id-format with either or both of the agent-circuit-id and nas-identifier agent-circuit-id agent-remote-id suboptions of the tags supplied by the PPPoE intermediate agent host1(config)#radius remote-circuit-id-format nas-identifier agent-remote-id host1(config)#radius remote-circuit-id-format nas-identifier agent-circuit-id agent-remote-id Copyright © 2010, Juniper Networks, Inc.
Page 409 If the DSLAM transmits empty data for agent-circuit-id, the router appends the value 0/0/0/0/0/0 to dslForum1InterfaceSpecifier. To obtain the value for dslForum1InterfaceSpecifier, the router translates an internally generated interface specifier into the format for the dsl-forum-1 keyword, using the following conventions: Copyright © 2010, Juniper Networks, Inc.
Page 410: Table 21: Interface Specifier Format Examples For Dsl-Forum-1 Keyword
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 vlanId to 4096 Uses other values as supplied Copyright © 2010, Juniper Networks, Inc.
Page 411: Use By Radius Or L2Tp
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. Copyright © 2010, Juniper Networks, Inc.
Page 412: System Event Log
Optional use of the PPPoE-Max-Mtu tag transmitted from the client Platform Considerations You can configure PPPoE interfaces on the following E Series Broadband Services Routers: E120 router E320 router ERX1440 router ERX1410 router ERX710 router ERX705 router ERX310 router Copyright © 2010, Juniper Networks, Inc.
Page 413: Module Requirements
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) Copyright © 2010, Juniper Networks, Inc.
Page 414: Access Nodes In Ethernet Aggregation Networks Overview
The DSL Forum defined the IWF to devise the process for conversion of PPP over ATM (PPPoA) and PPPoE over ATM sessions to PPPoE sessions at the DSLAM to the B-RAS Copyright © 2010, Juniper Networks, Inc.
Page 415 12 bits of the ATM cell VCI. The ATM logical interface uses its configured VPI when segmenting the Ethernet packets into cells. ATM-to-Ethernet interworking is supported on E Series routers with aggregated Ethernet, Gigabit Ethernet, and 10-Gigabit Ethernet interfaces. Copyright © 2010, Juniper Networks, Inc.
Page 416: Before You Configure Pppoe
PPPoE maximum session value with the PPPoE maximum session value returned by the RADIUS server in the Max-Clients-Per-Interface vendor-specific attribute (VSA) [26-143] in Access-Accept messages. host1(config-if)#pppoe max-session-vsa override Create a PPPoE subinterface. Copyright © 2010, Juniper Networks, Inc.
Page 417 8000, the RADIUS value in this case is ignored. See JunosE Release Notes, Appendix A, System Maximums corresponding to your software release for information about the maximum number of PPPoE subinterfaces supported for each line module. Copyright © 2010, Juniper Networks, Inc.
Page 418 PPP/PPPoE session down PPP session 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 387 illustrates the interface stack for this configuration. Copyright © 2010, Juniper Networks, Inc.
Page 419: Figure 38: Example Of Pppoe Over Atm Stacking
(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). Example Copyright © 2010, Juniper Networks, Inc.
Page 420 1 indicates that the IOA is installed in the left IOA bay (E120 router) or the lower IOA bay (E320 router). port—Port number on the IOA subinterface—Number of the subinterface in the range 1–2147483647 Copyright © 2010, Juniper Networks, Inc.
Page 421 IWF PPPoE sessions contain the MAC address of the DSLAM device. For PPPoE sessions with the IWF-Session VSA, duplication of MAC addresses is permitted by default. Regardless of whether the duplicate protection feature is enabled, Copyright © 2010, Juniper Networks, Inc.
Page 422 For example, if you specify the number of subinterfaces for the ES2 4G LM as 32,000 interfaces, the number of subinterfaces created is 16,000 which is the default maximum value for the ES2 4G LM. Copyright © 2010, Juniper Networks, Inc.
Page 423: Processing Of Iwf Pppoe Sessions With Duplicate Mac Addresses
Table 22 on page 392 describes the different scenarios in which duplicate MAC addresses are supported for IWF PPPoE sessions and non-IWF PPPoE sessions, when duplicate protection configuration is enabled or disabled on a router. Copyright © 2010, Juniper Networks, Inc.
Page 424: Configuration Examples For Atm-To-Ethernet Interworking Functions
S-VLAN ID or a unique (S-VLAN ID, C-VLAN ID) pair. The uniqueness of the mapping is maintained in the access node and across the aggregation network. The B-RAS PPPoE access concentrator demultiplexes the PPPoE sessions. Copyright © 2010, Juniper Networks, Inc.
Page 425: Multiple Dslams Connected To A Pppoe Access Concentrator Example
VLAN. Sample criteria for grouping multiple ports with the same S-VLAN ID comprise the same originating virtual path, same service, or same destination service provider. In this topology, multiple DSLAMs, which aggregate sessions from multiple PPPoE clients, are connected to one access concentrator. Copyright © 2010, Juniper Networks, Inc.
Page 426: Configuring Pppoe For Ethernet Modules
MPLS. For more information about specific Ethernet modules and the protocols and applications they support, see: ERX Module Guide, Appendix A, Module Protocol Support (for ERX7xx models, ERX14xx models, and ERX310 router) Copyright © 2010, Juniper Networks, Inc.
Page 427: Pppoe Interface And Subinterface Limits
The VLAN major interface is added. Create a VLAN subinterface by adding a subinterface number to the interface identification command. host1(config-if)#interface gigabitEthernet 2/0/1.1 Assign a VLAN ID for the subinterface. host1(config-if)#vlan id 1 Create a PPPoE subinterface. Copyright © 2010, Juniper Networks, Inc.
Page 428 See encapsulation vlan. ipv6 address Use to add an IPv6 address to an interface or a subinterface. Example host1(config)#interface gigabitEthernet 1/0.25 host1(config-if)#ipv6 address 1::1/64 Use the no version to remove an IPv6 address. See ipv6 address Copyright © 2010, Juniper Networks, Inc.
Page 429 If the peer refuses to use PAP, the router requests the CHAP protocol. If the peer refuses to use CHAP, the router requests the EAP protocol. If the peer refuses to negotiate authentication, the router terminates the PPP session. Copyright © 2010, Juniper Networks, Inc.
Page 430: Configuring Pppoe Without Vlans
Specify a Fast Ethernet, Gigabit Ethernet, or 10-Gigabit Ethernet interface. host1(config)#interface fastEthernet 4/1 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 Specify PPP as the encapsulation method on the interface. host1(config-subif)#encapsulation ppp Copyright © 2010, Juniper Networks, Inc.
Page 431: Figure 42: Example Of Pppoe Stacking
Use the no version to disable PPP on an interface. See encapsulation ppp. interface fastEthernet Use to select a Fast Ethernet interface. For more information, see chapter Configuring Ethernet Interfaces in JunosE Physical Layer Configuration Guide. Example Copyright © 2010, Juniper Networks, Inc.
Page 432 Use the no version to remove an IP address or disable IP processing. See ip address. pppoe Use to specify PPPoE as the encapsulation method for the interface. This command creates a PPPoE major interface. Example host1(config-if)#pppoe Copyright © 2010, Juniper Networks, Inc.
Page 433 391 for a list of considerations to be observed when you use the duplicate protection feature for IWF PPPoE sessions. Example host1(config-subif)#pppoe duplicate-protection Use the no version to disable duplicate protection. See pppoe duplicate-protection. pppoe subinterface fastEthernet Copyright © 2010, Juniper Networks, Inc.
Page 434: Configuring Padm Messages
The message string is not saved in nonvolatile storage (NVS). Use in Privileged Exec mode. Example host1#pppoe motm Router going down at 10:00 p.m. Use the no version to disable the message. See pppoe motm. Copyright © 2010, Juniper Networks, Inc.
Page 435 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. The message string is saved in nonvolatile storage (NVS). Copyright © 2010, Juniper Networks, Inc.
Page 436: Configuring Padn Messages
Use to map a domain name between a PPP client’s domain name and a virtual router. Example host1(config)#aaa domain-map xyz.com host1(config-domain-map)#padn 10.2.25.6 255.255.255.0 10 host1(config-domain-map)#padn 20.2.0.0 255.255.0.0 11 Use the no version to delete the map entry. See aaa domain-map. padn Copyright © 2010, Juniper Networks, Inc.
Page 437: Configuring Pppoe Service Name Tables
PADI requests containing an empty service name tag; and denies requests that contain a service name tag that has not been configured in the service name table. Table 23: Default PPPoE Service Name Table Service Name Action “ ” Terminate unknown-service-name Drop Copyright © 2010, Juniper Networks, Inc.
Page 438: Table 24: Pppoe Service Name Table With Entries
Use from Global Configuration mode to create a PPPoE service name table. You can create a maximum of 16 PPPoE service name tables per E Series router. Specify a table name of up to 31 alphanumeric characters. Copyright © 2010, Juniper Networks, Inc.
Page 439 Example 2 – Includes a custom service entry in the PPPoE service name table. The associated action for this service tag is drop. Use the optional action keyword with the service command to associate an action with the custom service entry. host1(config-pppoe-service-name-table)# service myQOSClass2 action drop Copyright © 2010, Juniper Networks, Inc.
Page 440: Enabling Pppoe Service Name Tables For Use With Static Interfaces
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 387. Example host1(config-if)#atm pvc 10 100 22 aal5snap Copyright © 2010, Juniper Networks, Inc.
Page 441: 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. This command creates the PPPoE major interface. host1(config-if)#pppoe Copyright © 2010, Juniper Networks, Inc.
Page 442 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 service-name-table Copyright © 2010, Juniper Networks, Inc.
Page 443: Enabling Pppoe Service Name Tables For Use With Dynamic Interfaces
Enable the PPPoE dynamic encapsulation type. host1(config-subif)#auto-configure pppoe 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 387. Copyright © 2010, Juniper Networks, Inc.
Page 444 Specify the name of the PPPoE service name table configured with the pppoe-service-name-table command from Global Configuration mode. Example host1(config-profile)#pppoe service-name-table myServiceTable1 Use the no version to remove the PPPoE service name table assignment. See pppoe service-name-table. profile Copyright © 2010, Juniper Networks, Inc.
Page 445: Configuring Pads Packet Content
Use the no version to restore the default behavior, which is to send the AC-Name and AC-Cookie tags in the PADS packet. See pppoe pads disable-ac-info. Configuring PPPoE Remote Circuit ID Capture To capture and use the PPPoE remote circuit ID: Copyright © 2010, Juniper Networks, Inc.
Page 446 The following command formats the PPPoE remote circuit ID 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. host1(config)#radius remote-circuit-id-format nas-identifier agent-circuit-id agent-remote-id Copyright © 2010, Juniper Networks, Inc.
Page 447 (Optional) Configure a fallback format for the L2TP Calling Number AVP 22. The fallback format is used only when you have configured the calling number format as anything other than fixed and the PPPoE agent ID is null or unavailable. host1(config)#aaa tunnel calling-number-format fallback fixed Copyright © 2010, Juniper Networks, Inc.
Page 448 The fallback format is used only when the configured calling number format includes either or both of the agent-circuit-id and agent-remote-id. The calling number format determines what element triggers use of the fallback format: Calling Number Format Fallback Trigger agent-circuit-id agent-circuit-id is empty Copyright © 2010, Juniper Networks, Inc.
Page 449 RADIUS attribute and instead use the PPPoE remote circuit ID transmitted from a DSLAM. Example host1(config)#radius override calling-station-id remote-circuit-id Use the no version to restore the default Calling-Station-Id value, which is the telephone number from which the call originated. See radius override calling-station-id remote-circuit-id. Copyright © 2010, Juniper Networks, Inc.
Page 450 PPPoE remote circuit ID only if the DSLAM transmits non-empty data for at least one of the agent-circuit-id or agent-remote-id values. If the DSLAM transmits empty data, then RADIUS does not override the Calling-Station-Id [31] or Copyright © 2010, Juniper Networks, Inc.
Page 451: Monitoring Pppoe
Monitoring PPPoE Use the commands described in this section to display information about PPPoE interfaces and subinterfaces. You can set a statistics baseline for PPPoE interfaces, subinterfaces, and circuits using the baseline pppoe interface command. Copyright © 2010, Juniper Networks, Inc.
Page 452 Tunnel nas-port-method—Default NAS port type Tunnel nas-port ignore—Whether the router uses the tunnel peer’s NAS-Port [5] attribute; enabled or disabled Tunnel nas-port-type ignore—Whether the router uses the tunnel peer’s NAS-Port-Type [61] attribute; enabled or disabled Copyright © 2010, Juniper Networks, Inc.
Page 453 PPP sessions configured mtu—Maximum transfer unit (MTU) value; when derived from the PPPoE MTU tag, the value can only be determined from an active session. acName—Name of PPPoE access concentrator Copyright © 2010, Juniper Networks, Inc.
Page 454 Invalid PAD Code—Number of control packets received with an invalid code Invalid PAD Tags—Number of control packets received with invalid tags Invalid PAD Tag length—Number of control packets received with an invalid tag length Copyright © 2010, Juniper Networks, Inc.
Page 455 PPPoE interface ATM 1/0.1 has 1 active connections, out of 1 configured subinterfaces Assigned profile (any) : baseProfile PPPoE Statistics Counters: PADI received PADI transmitted PADO received PADO transmitted PADR received PADR transmitted PADS received PADS transmitted PADT received Copyright © 2010, Juniper Networks, Inc.
Page 456 Example 3—Uses the default MTU value (1494) host1#show pppoe interface full PPPoE interface FastEthernet 2/0 is operStatusUp PPPoE interface FastEthernet 2/0 has max sessions = 8000 PPPoE interface FastEthernet 2/0 mtu 1494 PPPoE interface FastEthernet 2/0 has no acName set Copyright © 2010, Juniper Networks, Inc.
Page 457 PPPoE interface FastEthernet 2/0 has 1 active connections, out of 1 configured subinterfaces Assigned profile (any) : pppoetest PPPoE Statistics Counters: PADI received PADI transmitted PADO received PADO transmitted PADR received PADR transmitted PADS received Copyright © 2010, Juniper Networks, Inc.
Page 458 Up—Number of interfaces that are operational Down—Number of interfaces that are not operational LowerLayerDown—Number of interfaces that are not operational because an underlying interface is down NotPresent—Number of interfaces that are not operational because hardware is unavailable Example Copyright © 2010, Juniper Networks, Inc.
Page 459 Example 2—Displays the contents of a default PPPoE service name table with no specific service name entries host1#show pppoe-service-name-table name myDefaultTable Service Name Table myDefaultTable Empty service name action: terminate Unknown service name action: drop Copyright © 2010, Juniper Networks, Inc.
Page 460 URL String—URL string sent in the PADM message to PPPoE clients MOTM String—Message of the minute string sent in the PADM message to PPPoE clients session id—Session ID of the subinterface source MAC address—MAC address of PPPoE client Copyright © 2010, Juniper Networks, Inc.
Page 461 Total PPPoE subinterfaces—Number of configured PPPoE subinterfaces included in summary Administrative Status Up—Number of subinterfaces not affected by manual administrative intervention Down—Number of subinterfaces that cannot flow because of manual administrative intervention Operational Status Copyright © 2010, Juniper Networks, Inc.
Page 462 VR Directed Broadcast—Enabled or disabled ICMP Redirects—Enabled or disabled Access Route Addition—Enabled or disabled Network Address Translation—Enabled or disabled; domain location (inside or outside) Source-Address Validation—Enabled or disabled Copyright © 2010, Juniper Networks, Inc.
Page 463 PPP State Log—Enabled or disabled PPP Chap Challenge Length—Minimum and maximum Chap Challenge length PPP Passive Mode—Enabled or disabled PPP Multilink—Enabled or disabled PPP IPCP netmask option—Enabled or disabled PPP AAA Profile—AAA profile associated with this PPP interface Copyright © 2010, Juniper Networks, Inc.
Page 464 : Disabled Filter Option Packets : Disabled Administrative MTU : 1500 TCP MSS value Inactivity Timer : Disabled Route Map Name : Disabled Auto Detect : Disabled Auto Configure : Disabled IGMP : Enabled static-groups Copyright © 2010, Juniper Networks, Inc.
Page 465 Calling-Station-Id attribute; value is remote-circuit-id if configured with radius override calling-station-id remote-circuit-id command nas-info—Virtual router that generates the NAS-IP-Address and NAS-Identifier attributes for AAA broadcast accounting packets; current virtual router or authentication virtual router Example Copyright © 2010, Juniper Networks, Inc.
Page 466: Troubleshooting
Use to configure a packet trace log for a PPPoE interface. You must specify a PPPoE major interface. Specify one of the following interface types and a corresponding interface specifier. For more information, see Interface Types and Specifiers in JunosE Command Reference Guide. Copyright © 2010, Juniper Networks, Inc.
Page 467 DEBUG 07/25/2000 15:13:49 pppoeControlPacket (interface atm 10/0.1): PADR rx from 00-09-01-a0-00-2e DEBUG 07/25/2000 15:13:49 pppoeControlPacket (interface atm 10/0.1): PADS tx to 00-09-01-a0-00-2e, connection made using session id 4 on sub interface 1 RX-a0-00-2e:v0(config-if)# RX-a0-00-2e:v0(config-if)#exit See log severity. Copyright © 2010, Juniper Networks, Inc.
Page 468 JunosE 11.2.x Link Layer Configuration Guide Copyright © 2010, Juniper Networks, Inc.
Page 469: Configuring Bridged Ip
When an IP client broadcasts the ARP request across the Ethernet wire, the end node with the correct IP address responds to the ARP request and provides the correct MAC address. If the unrestricted Copyright © 2010, Juniper Networks, Inc.
Page 470: Dhcp
See ERX Module Guide, Appendix A, Module Protocol Support for information about the modules that support bridged IP. For information about the modules that support bridged IP interfaces on the E120 and E320 routers: Copyright © 2010, Juniper Networks, Inc.
Page 471: Interface Specifiers
Each configured line can transmit data to and receive data from your switch connections. Table 25 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. Copyright © 2010, Juniper Networks, Inc.
Page 472: Configuring Bridged Ip
(VPI), the virtual channel identifier (VCI), and the encapsulation type. host1(config-if)#atm pvc 10 22 100 aal5snap Configure bridged IP encapsulation. host1(config-if)#encapsulation bridge1483 Assign an IP address and subnet mask to the PVC. host1(config-subif)#ip address 192.168.10.20 255.255.255.0 Copyright © 2010, Juniper Networks, Inc.
Page 473 LLC/Subnetwork Access Protocol (LLC/SNAP) header precedes the protocol datagram. aal5muxip—Specifies a multiplexed circuit used for IP only. Example host1(config-if)#atm pvc 10 22 100 aal5snap Use the no version to remove the specified PVC. See atm pvc. encapsulation bridge1483 Copyright © 2010, Juniper Networks, Inc.
Page 474 For more information, see “Creating a Basic Configuration” on page 20 in “Configuring ATM” on page 3. Examples host1(config)#interface atm 3/1.20 host1(config)#interface atm 5/0/1.20 Use the no version to remove the ATM subinterface or the logical interface. See interface atm. Copyright © 2010, Juniper Networks, Inc.
Page 475: Configuring Bridged Ethernet
E Series router. Configuration of local cross-connects is supported on all E Series routers. For more information about configuring local cross-connects, see chapter Configuring Layer 2 Services over MPLS in JunosE BGP and MPLS Configuration Guide. Copyright © 2010, Juniper Networks, Inc.
Page 476: Bridged Ethernet Application
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 Copyright © 2010, Juniper Networks, Inc.
Page 477: Figure 44: Interface Stacking For Vlans Over Bridged Ethernet
Ethernet interfaces. For more information, see: “Configuring VLAN and S-VLAN Subinterfaces” on page 167 for introductory information about VLANs and S-VLANs. Copyright © 2010, Juniper Networks, Inc.
Page 478: Platform Considerations
For ERX7xx models, ERX14xx models, and ERX310 router, use the slot/port[.subinterface ] format. For example, the following command specifies ATM 1483 subinterface 10 on slot 0, port 1 of an ERX7xx model, ERX14xx model, or ERX310 router. host1(config)#interface atm 0/1.10 Copyright © 2010, Juniper Networks, Inc.
Page 479: References
Ethernet interface cannot have a peer interface stacked above the same lower-layer interface. host1(config-subif)#encapsulation bridge1483 Create a PPPoE major interface over the bridged Ethernet interface. This command does not use the encapsulation keyword. host1(config-subif)#pppoe Copyright © 2010, Juniper Networks, Inc.
Page 480 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: Copyright © 2010, Juniper Networks, Inc.
Page 481 Use to configure an ATM interface or subinterface type. To specify an ATM interface for ERX7xx models, ERX14xx models, and ERX310 router, use the slot/port.[subinterface ] format. slot—Number of the chassis slot port—Port number on the I/O module Copyright © 2010, Juniper Networks, Inc.
Page 482 Use the loose keyword to allow IP packets to pass through even though the packets do not have entries in the validation table. Only packets that have matching IP–MAC pair entries in the table are validated. This is the default setting. Copyright © 2010, Juniper Networks, Inc.
Page 483: Alternative Configuration
(encapsulation pppoe) cannot be used when a bridged Ethernet interface already exists, because it is intended to produce the old stacking for PPPoE over ATM 1483. Create the ATM 1483 subinterface and associated PVC: Copyright © 2010, Juniper Networks, Inc.
Page 484: Configuring Vlans Over Bridged Ethernet
NOTE: Before you can remove a VLAN subinterface, you must remove the upper-layer interface stack. For more information about specifying ATM interfaces and subinterfaces, see Interface Types and Specifiers in JunosE Command Reference Guide. Copyright © 2010, Juniper Networks, Inc.
Page 485: Configuring Vlan Subinterfaces Over Bridged Ethernet
453 to configure the VLAN subinterface. Assign an IP address and mask to the VLAN subinterface. host1(config-subif)#ip address 10.1.1.1 255.255.255.0 Configuring PPPoE over VLAN To configure PPPoE over VLAN over a bridged Ethernet interface: Copyright © 2010, Juniper Networks, Inc.
Page 486: Configuring Mpls Over Vlan
1 5 50 aal5snap 0 0 0 Use the no version to remove the specified PVC. See atm pvc. encapsulation bridge1483 Use to configure bridged Ethernet as the encapsulation method on an ATM 1483 subinterface. Example host1(config-subif)#encapsulation bridge1483 Copyright © 2010, Juniper Networks, Inc.
Page 487 Use the no version to remove the interface or subinterface. See interface atm. ip address Use to set an IP address for the interface. Note that you cannot add more than one IP address to bridged Ethernet interfaces. Copyright © 2010, Juniper Networks, Inc.
Page 488 Use to specify the VLAN ID. Use a VLAN ID that is in the range 0–4095 and is unique within the interface. Issue the vlan id command before any upper bindings are made, such as IP or PPPoE. Copyright © 2010, Juniper Networks, Inc.
Page 489: Configuring S-Vlans Over Bridged Ethernet
Create a VLAN major interface by specifying VLAN as the encapsulation method for the bridged Ethernet interface. host1(config-subif)#encapsulation vlan 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 Copyright © 2010, Juniper Networks, Inc.
Page 490: Configuring Higher-Level Protocols Over S-Vlans
This section provides an example for configuring PPPoE interfaces over S-VLAN subinterfaces configured on bridged Ethernet. For descriptions of the commands used in this procedure, see “Configuring Higher-Level Protocols over VLANs” on page 453. Copyright © 2010, Juniper Networks, Inc.
Page 491: Configuring The Mtu Size For Bridged Ethernet
You can also use the bridge1483 mtu command in a profile to configure a nondefault MTU size for a dynamic bridged Ethernet interface. For information, see “Configuring a Dynamic Interface from a Profile” on page 559 in “Configuring Dynamic Interfaces” on page 511. bridge1483 mtu Copyright © 2010, Juniper Networks, Inc.
Page 492: Monitoring Bridged Ethernet
Interface—Type and specifier of the lower-layer interface on which bridged Ethernet is configured Status—Status of the bridged Ethernet interface: up, down, lowerLayerDown, notPresent MAC Address—MAC address assigned to the bridged Ethernet interface, if configured Type—Type of interface: static or dynamic Copyright © 2010, Juniper Networks, Inc.
Page 493 Example 1—Displays full configuration and status information host1#show bridge1483 interface Oper/Admin Interface Status MAC Address Type ------------------------- ---------- -------------- ------- ---------- ATM 5/1.1 ----.----.---- Static 1500/1684 Copyright © 2010, Juniper Networks, Inc.
Page 494 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 Copyright © 2010, Juniper Networks, Inc.
Page 495 ATM 3/0.1.2 1522 ---- ---- Example 3—Displays only brief summary information for all VLAN subinterfaces configured on the router host1#show vlan subinterface summary Total VLAN interfaces: 6 subinterfaces, 3 major interfaces See show vlan subinterface. Copyright © 2010, Juniper Networks, Inc.
Page 496 JunosE 11.2.x Link Layer Configuration Guide Copyright © 2010, Juniper Networks, Inc.
Page 497: Configuring Transparent Bridging
(MAC) source address of every incoming packet. The bridge then creates an entry in the forwarding table consisting of the address and associated interface where the packet was received. Copyright © 2010, Juniper Networks, Inc.
Page 498: Bridge Groups And Bridge Group Interfaces
E Series router, see JunosE Release Notes, Appendix A, System Maximums. Figure 45 on page 467 shows an example of a simple transparent bridging network configuration that illustrates the concepts discussed so far in this section. Copyright © 2010, Juniper Networks, Inc.
Page 499: Bridge Interface Types And Supported Configurations
You can configure bridge interfaces to add transparent bridging capabilities to your existing network configurations. Currently, bridge interfaces can be stacked on: Copyright © 2010, Juniper Networks, Inc.
Page 500: Subscriber Policies
(DAs) are handled. Table 27: Default Subscriber Policies for Bridge Group Interfaces Packet/Attribute Type Default Subscriber Policy Default Trunk Policy Permit Permit Broadcast Deny Permit Permit Permit Copyright © 2010, Juniper Networks, Inc.
Page 501: Concurrent Routing And Bridging
IP, MPLS, or PPPoE interface that is the first occurrence of this protocol in the bridge group. (See “Configuring Explicit Routing” on page 483 for details about using the bridge route command.) Copyright © 2010, Juniper Networks, Inc.
Page 502: Transparent Bridging And Vpls
ERX310 router Module Requirements For information about the modules that support transparent bridging on ERX14xx models, ERX7xx models, and the ERX310 router: See ERX Module Guide, Table 1, Module Combinations for detailed module specifications. Copyright © 2010, Juniper Networks, Inc.
Page 503: Interface Specifiers
Before you configure transparent bridging on an E Series router, verify that: 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, Copyright © 2010, Juniper Networks, Inc.
Page 504: Configuration Tasks
(Optional) Set optional attributes for the bridge group. Configure bridge group interfaces. (Optional) Configure nondefault subscriber policies for bridge interfaces. (Optional) Enable concurrent routing and bridging. (Optional) If CRB is enabled, configure explicit routing for IP, MPLS, or PPPoE protocols. Copyright © 2010, Juniper Networks, Inc.
Page 505: Creating Bridge Groups
Enable or disable the bridge group’s ability to acquire dynamically learned MAC addresses; acquiring dynamic MAC addresses is enabled by default. host1(config)#bridge westford01 acquire Enable or disable the bridge group’s ability to filter (forward or discard) frames with a particular MAC source or destination address. Copyright © 2010, Juniper Networks, Inc.
Page 506 MAC address out the specified interface discard—Discards (drops) frames sent from or destined for the specified MAC address without further processing If you use the forward keyword, you must additionally specify the following: Copyright © 2010, Juniper Networks, Inc.
Page 507 E Series router, see JunosE Release Notes, Appendix A, System Maximums. The default value is 0 (zero) learned addresses. This default implies that there is no maximum number of learned entries for an individual bridge group; that is, an individual Copyright © 2010, Juniper Networks, Inc.
Page 508: Configuring Bridge Group Interfaces
(specified in the bridge command) to which you want to assign the interface. Optionally, you can also choose one of the following keywords: subscriber-trunk—Creates a trunk (server) bridge group interface Copyright © 2010, Juniper Networks, Inc.
Page 509 See interface fastEthernet. interface gigabitEthernet interface tenGigabitEthernet Use to select a Gigabit Ethernet interface or a 10-Gigabit Ethernet interface. Examples Copyright © 2010, Juniper Networks, Inc.
Page 510: Configuring Subscriber Policies
(forwards) or denies (filters or drops) ARP packets. Specify one of the following keywords: permit—Forwards packets of this type deny—Filters or drops packets of this type ARP packets are forwarded by default. Example Copyright © 2010, Juniper Networks, Inc.
Page 511 Broadcast packets are filtered or dropped by default. Example host1(config-policy)#broadcast permit Use the no version to restore the default value. See broadcast. Copyright © 2010, Juniper Networks, Inc.
Page 512 Specify one of the following keywords: permit—Forwards packets of this type deny—Filters or drops packets of this type Multicast packets are forwarded by default. Example host1(config-policy)#multicast deny Use the no version to restore the default value. See multicast. pppoe Copyright © 2010, Juniper Networks, Inc.
Page 513 You must specify an alphanumeric name for the subscriber policy; the name can be a maximum of 32 characters and can use any combination of alphanumeric characters. Example host1(config)#subscriber-policy client01 Use the no version to remove the nondefault subscriber policy. Copyright © 2010, Juniper Networks, Inc.
Page 514 Use to modify the subscriber policy for packets containing an unknown protocol to define whether a subscriber (client) bridge interface permits (forwards) or denies (filters or drops) these packets. An unknown protocol is any protocol other than ARP, IP, MPLS, or PPPoE. Copyright © 2010, Juniper Networks, Inc.
Page 515: Enabling Concurrent Routing And Bridging
After you enable concurrent routing and bridging, you may need to issue the bridge route command to configure explicit routing for IP, MPLS, or PPPoE protocols if both of the following conditions are true: Copyright © 2010, Juniper Networks, Inc.
Page 516 You must specify the alphanumeric name of the bridge group specified in the bridge command. Choose one of the following keywords to indicate the protocol type that the bridge group routes: ip, mpls, or pppoe. Example host1(config)#bridge westford02 route ip Copyright © 2010, Juniper Networks, Inc.
Page 517: Configuration Examples
Create a PPPoE major interface over the bridged Ethernet interface. Because this command does not use the encapsulation keyword, the PPPoE interface can have one or more peer interfaces stacked above the same bridged Ethernet interface. host1(config-subif)#pppoe Copyright © 2010, Juniper Networks, Inc.
Page 518: Example 2: Bridging With Vlans
Create a VLAN major interface by specifying VLAN as the encapsulation method for the interface. host1(config-if)#encapsulation vlan Create a VLAN subinterface by adding a subinterface number to the interface fastEthernet command. host1(config-if)#interface fastEthernet 2/0.1 Copyright © 2010, Juniper Networks, Inc.
Page 519: Monitoring Transparent Bridging
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). Copyright © 2010, Juniper Networks, Inc.
Page 520: Setting Statistics Baselines
Interface Types and Specifiers in JunosE Command Reference Guide for information Example host1#baseline bridge interface atm 3/3.1 There is no no version. See baseline bridge interface. Copyright © 2010, Juniper Networks, Inc.
Page 521: Removing Dynamic Mac Address Entries
1234.abcd.5678 host1#show bridge westford01 table Bridge: westford01 MAC Address Table Address Action Interface -------------- ---------- ------------------- ----- 0090.1a01.0205 forward ATM3/3.1 There is no no version. See clear bridge address. clear bridge interface Copyright © 2010, Juniper Networks, Inc.
Page 522: Monitoring Bridge Groups
Use to display configuration and statistics information for the specified bridge group. To display information about the MAC address table and bridge interfaces, use the all keyword. Field descriptions Copyright © 2010, Juniper Networks, Inc.
Page 523 Operational Status—Operational status of the physical interface: Up, Down, LowerLayerDown, NotPresent Admin Status—State of the physical interface: Up, Down Snmp Link Status Trap—Whether SNMP link status processing is enabled or disabled for the specified bridge interface Copyright © 2010, Juniper Networks, Inc.
Page 524 Link Status Snmp Traps: Disabled Subscriber Policy: default Subscriber Protocol Actions: Route Route PPPoE Port Count: Interface Count: Example 2—Displays information about configuration settings, MAC address table entries, and bridge group interfaces for the specified bridge group Copyright © 2010, Juniper Networks, Inc.
Page 525 To display the configuration settings for all bridge groups on your router, use the details keyword. Field descriptions BridgeGroup—Name assigned to the bridge group Bridge Mode—Bridging capability currently enabled, either concurrent routing and bridging (CRB) or default bridging Copyright © 2010, Juniper Networks, Inc.
Page 526 Interface Count: BridgeGroup: westford01 Bridge Mode: Aging Time: 300 secs Learning: Enabled Max Learn: Unlimited Link Status Snmp Traps: Disabled Subscriber Policy: default Subscriber Protocol Actions: Port Count: Interface Count: See show bridge groups. Copyright © 2010, Juniper Networks, Inc.
Page 527 Queue length—Length of the queue, in bytes Forwarded packets, Bytes—Number of packets and bytes forwarded on this queue Dropped committed packets, Bytes—Number of committed packets and bytes that were dropped Copyright © 2010, Juniper Networks, Inc.
Page 528 See show bridge port. show bridge table Use to display information about dynamic and static entries in the MAC address table for the specified bridge group. To display only static address entries, use the static keyword. Copyright © 2010, Juniper Networks, Inc.
Page 529: Monitoring Bridge Interfaces
Snmp Link Status Trap—Whether SNMP link status processing is enabled or disabled for the specified bridge interface Max Learn—Maximum number of dynamic MAC addresses that the bridge group interface can learn Subscriber Policy—Name of the subscriber policy currently in effect for the bridge group interface Copyright © 2010, Juniper Networks, Inc.
Page 530 Example 1—Displays information about a specified interface host1#show bridge interface fastEthernet 9/1.1 fastEthernet9/1.1 BridgeGroup: 1 Port Number: 1 Operational Status: Up Admin Status: Up Snmp Link Status Trap: Disabled Max Learn: Unlimited Subscriber Policy: atmfe1 Statistics: In Octets: In Frames: Copyright © 2010, Juniper Networks, Inc.
Page 531: Monitoring Subscriber Policies
Broadcast—Specifies how the bridge interface handles broadcast packets Multicast—Specifies how the bridge interface handles multicast packets Unknown Destination—Specifies how the bridge interface handles packets with unknown unicast DAs Unicast—Specifies how the bridge interface handles unicast (user-to-user) packets Copyright © 2010, Juniper Networks, Inc.
Page 532 Example 2—Displays the rules for a specified subscriber policy host1#show subscriber-policy client01 Subscriber: client01 : Permit Broadcast : Permit Multicast : Deny Unknown Destination : Deny : Permit Unknown Protocol : Permit Unicast : Permit PPPoE : Permit Copyright © 2010, Juniper Networks, Inc.
Page 533 Chapter 15: Configuring Transparent Bridging Relearn : Deny Mpls : Permit See show subscriber-policy. Copyright © 2010, Juniper Networks, Inc.
Page 534 JunosE 11.2.x Link Layer Configuration Guide Copyright © 2010, Juniper Networks, Inc.
Page 535: Configuring Cisco Hdlc
SLARP address-response message, which indicates that it cannot participate in a SLARP session. Cisco HDLC is compatible with Cisco Systems Cisco-HDLC protocol, the default protocol for all Cisco serial interfaces. Framing The router supports the following framing features: Copyright © 2010, Juniper Networks, Inc.
Page 536: Error Frames
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. Copyright © 2010, Juniper Networks, Inc.
Page 537: Before You Configure Cisco Hdlc
(Optional) Use the appropriate “show hdlc interface” on page 509 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 Copyright © 2010, Juniper Networks, Inc.
Page 538: Optional Tasks
Use the no version to remove the IP address of the interface. See ip address. Optional Tasks The following tasks are optional. Configure the SLARP keepalive interval. 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 Copyright © 2010, Juniper Networks, Inc.
Page 539 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. Copyright © 2010, Juniper Networks, Inc.
Page 540: Configuration Example
You can use the filtering feature of the show command to include or exclude lines of output based on a text string you specify. For details, see show Commands in JunosE System Basics Configuration Guide. Copyright © 2010, Juniper Networks, Inc.
Page 541 CLI output filter Field descriptions interface status—State of the interface: Up—Traffic can flow on the interface Down—Traffic cannot flow because of a problem in the interface at the current protocol layer Copyright © 2010, Juniper Networks, Inc.
Page 542 Interface maximum-transmission-unit is 1596 Interface keepalive time is 10 seconds Interface loop detection is disabled Interface statistics packets octets errors discards Cisco-HDLC interface serial 5/0:1/1 is NotPresent 2 Cisco-HDLC interfaces found See show hdlc interface. Copyright © 2010, Juniper Networks, Inc.
Page 543: Configuring Dynamic Interfaces
(VC) or a virtual LAN (VLAN) through a process known as autodetection. The layers of a dynamic interface are created based on the packets received on the link and can be configured through any one of the following: RADIUS authentication Profiles Copyright © 2010, Juniper Networks, Inc.
Page 544: Autodetection
Dynamic IP, PPPoE, PPP, MLPPP, and bridged Ethernet interfaces over a static ATM 1483 interface IP or PPPoE interfaces over VLAN interfaces and Ethernet, Gigabit Ethernet, and 10-Gigabit-Ethernet interfaces. NOTE: Ethernet interfaces in this chapter refer to any of these interfaces Fast Ethernet, Gigabit Ethernet, or 10–Gigabit-Ethernet. Copyright © 2010, Juniper Networks, Inc.
Page 545: Upper-Layer Dynamic Interface Configurations
Dynamic IPv6 over dynamic PPP over dynamic PPPoE subinterface over static PPPoE major interface (with or without VLANs) Dynamic IPv6 over dynamic MLPPP over dynamic PPPoE subinterface over static PPPoE major interface (with or without VLANs) Copyright © 2010, Juniper Networks, Inc.
Page 546: Profiles
For dynamic IPoA or dynamic bridged Ethernet, the RADIUS username and password are obtained from the information specified by the subscriber command. The RADIUS server returns a grant or deny indication. If authentication is granted, the RADIUS Copyright © 2010, Juniper Networks, Inc.
Page 547: Atm Oversubscription For Dynamic Interfaces
PPP or PPPoE. For ATM line modules that support ATM subinterface oversubscription, the maximum number of active subinterfaces supported per module is less than the maximum number of configured subinterfaces supported per module. Copyright © 2010, Juniper Networks, Inc.
Page 548: Bulk-Configured Vc Ranges
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 185 . Copyright © 2010, Juniper Networks, Inc.
Page 549: Platform Considerations
I/O adapter (IOA) resides. In the software, adapter 0 identifies the right IOA bay (E120 router) and the upper IOA bay (E320 router); adapter 1 identifies the left IOA bay (E120 router) and the lower IOA bay (E320 router). For Copyright © 2010, Juniper Networks, Inc.
Page 550: References
When you configure a dynamic interface, you must assign (or create and assign) a profile to the interface. Profile creation and assignment topics are discussed in depth in “Configuring a Dynamic Interface from a Profile” on page 559. Copyright © 2010, Juniper Networks, Inc.
Page 551: About Configuring Radius For Dynamic Interfaces
SRP switchover on the router or prevent stateful SRP switchover from becoming active. To bypass this limitation, you can use the subscriber management application to configure IP subscribers on dynamic bridged Ethernet interfaces. Copyright © 2010, Juniper Networks, Inc.
Page 552: Placing Dynamic Ip Routes In The Routing Table
For dynamic IP interfaces, the next hop might not be known when you create the user record. In this case, use the value 0.0.0.0 for the next hop; the E Series router then assigns the subinterface associated with the user as the next hop in the routing table. Copyright © 2010, Juniper Networks, Inc.
Page 553: Auto-Configure Command
RADIUS server. Locking out autodetection of the IP or bridged Ethernet encapsulation type for a configurable time period prevents detection of dynamic IPoA or bridged Ethernet interfaces and reduces loading on the RADIUS server. Copyright © 2010, Juniper Networks, Inc.
Page 554 For the IP and bridged Ethernet encapsulation types, temporary lockout occurs automatically on receipt of an authentication deny response from RADIUS when you attempt to create and configure a dynamic IPoA or dynamic bridged Ethernet interface. Copyright © 2010, Juniper Networks, Inc.
Page 555 The router increments the value of n when the time between lockout events is either within 15 minutes or the maximum lockout time, whichever is greater. Copyright © 2010, Juniper Networks, Inc.
Page 556 PPPoE sessions that originated with the same MAC address are not terminated (continue to remain logged in) if they are IWF sessions from different access loops (PPPoE clients) and this information is available to the B-RAS application. Copyright © 2010, Juniper Networks, Inc.
Page 557: Atm Pvc Command
MAC address retrieved from the client, is enabled by default only for IWF sessions. Configuring PPP and PPPoE Dynamic Interfaces over Static ATM E Series routers support dynamic PPP and PPPoE interfaces. The configuration procedure is very similar for each. Copyright © 2010, Juniper Networks, Inc.
Page 558: Figure 47: Dynamic Ppp Interface Columns
Figure 47: Dynamic PPP Interface Columns Figure 48 on page 526 shows dynamic PPPoE interface columns and illustrates how PPPoE supports multiple IP sessions over each ATM 1483 circuit. Figure 48: Dynamic PPPoE Interface Columns Copyright © 2010, Juniper Networks, Inc.
Page 559: Configuring A Ppp Or Pppoe Dynamic Interface
LLC/Subnetwork Access Protocol (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. Copyright © 2010, Juniper Networks, Inc.
Page 560 Example 4—Either command reenables encapsulation type lockout for the PPPoE encapsulation type using the default lockout time range host1(config-subif)#auto-configure pppoe host1(config-subif)#no auto-configure pppoe lockout-time Example 5—Permanently locks out the PPP encapsulation type until the auto-configure ppp command is issued host1(config-subif)#no auto-configure ppp Copyright © 2010, Juniper Networks, Inc.
Page 561 Use to assign a profile. You must specify the encapsulation type to which the profile applies: bridgedEthernet, ip, ppp, pppoe ,or any. Specify a profile name with up to 80 alphanumeric characters. Example host1(config-subif)#profile ppp foo Copyright © 2010, Juniper Networks, Inc.
Page 562: Terminating Stale Pppoa Subscribers And Restarting Lcp Negotiations
LCP negotiations more quickly. For CPEs that do not support PPP keepalive, receipt of an LCP terminate request packet from the router enables the CPE to detect the connection termination and restart LCP negotiations in response. Copyright © 2010, Juniper Networks, Inc.
Page 563: Configuring Pppoe Dynamic Interfaces Over Pppoe Static Interfaces
PPPoE to support multiple IP sessions over each ATM 1483 circuit. Figure 49: Dynamic PPPoE over Static PPPoE with ATM Interface Columns To configure an ATM 1483 subinterface to support a dynamic PPPoE subinterface: Copyright © 2010, Juniper Networks, Inc.
Page 564: Columns
5/0.1 host1#show pppoe interface atm 5/0.1 Configuring Dynamic PPPoE over Static PPPoE with Ethernet Interface Columns Figure 50 on page 533 shows dynamic PPPoE subinterface columns configured over an Ethernet interface without VLANs. Copyright © 2010, Juniper Networks, Inc.
Page 565: Configuring Dynamic Pppoe Over Static Pppoe With Ethernet And Vlan Interface Columns
Configuring Dynamic PPPoE over Static PPPoE with Ethernet and VLAN Interface Columns Figure 51 on page 534 shows dynamic PPPoE subinterface columns and illustrates an alternative method for PPPoE to support multiple IP sessions over each VLAN. Copyright © 2010, Juniper Networks, Inc.
Page 566: Configuring Ipv4 And Ipv6 Over Static And Dynamic Pppoe
Configure the interface to detect and accept dynamic PPPoE subinterfaces. host1(config-subif)#pppoe auto-configure 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 52 on page 535. Copyright © 2010, Juniper Networks, Inc.
Page 567: Figure 52: Ipv4 And Ipv6 Interface Columns Over Static And Dynamic Pppoe
Specify the interface. host1(config-if)#interface gigabitEthernet 4/0/6 Set the encapsulation type to PPPoE. 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 Copyright © 2010, Juniper Networks, Inc.
Page 568 For more information about how to configure a virtual router using RADIUS, see Configuring RADIUS Attributes in the JunosE Broadband Access Configuration Guide. Example host1(config-profile)#ip virtual-router VR1 Use the no version to remove the virtual router assignment. See ip virtual-router Copyright © 2010, Juniper Networks, Inc.
Page 569 IPv6 address. This interface cannot be another unnumbered interface. Example host1(config-if)#ipv6 unnumbered loopback 0 Use the no version to disable IPv6 processing on an interface. See ipv6 unnumbered Copyright © 2010, Juniper Networks, Inc.
Page 570 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. profile Copyright © 2010, Juniper Networks, Inc.
Page 571: Configuring Dynamic Pppoe Over Static Pppoe With Ethernet And S-Vlan Interface Columns
Figure 53: 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 Copyright © 2010, Juniper Networks, Inc.
Page 572: S-Vlan Oversubscription
For specific information about the maximum number of S-VLANs supported per I/O module or IOA and the maximum number of PPP interfaces and PPPoE subinterfaces supported per line module, see JunosE Release Notes, Appendix A, System Maximums. Copyright © 2010, Juniper Networks, Inc.
Page 573 See encapsulation pppoe. encapsulation vlan Use to configure VLAN as the encapsulation method for the interface. Example host1(config-if)#encapsulation vlan Use the no version to remove VLAN encapsulation from the interface. See encapsulation vlan. interface atm Copyright © 2010, Juniper Networks, Inc.
Page 574 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. See interface tenGigabitEthernet. ip address Copyright © 2010, Juniper Networks, Inc.
Page 575 9100—Specifies Ethertype value 0x9100, which is the default 9200—Specifies Ethertype value 0x9200 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 Copyright © 2010, Juniper Networks, Inc.
Page 576: Configuring Encapsulation Type Lockout For Pppoe Clients
You can also use the show pppoe interface lockout-time command to display detailed information about the current lockout condition for each PPPoE client, and the pppoe clear lockout interface command to clear (reset) the lockout condition for an individual PPPoE client. Copyright © 2010, Juniper Networks, Inc.
Page 577: Differences From Lockout Configuration For Pppoe Over Static Atm
Configuring and verifying lockout for PPPoE clients Clearing the lockout condition for a specific PPPoE client Configuring and Verifying Lockout for PPPoE Clients To configure and verify encapsulation type lockout for a PPPoE client: Configure the underlying physical interface. Copyright © 2010, Juniper Networks, Inc.
Page 578 PPPoE client (access loop) for PPPoE sessions that contain the IWF-Session DSL Forum VSA (26-154). host1#show pppoe interface atm 12/1/1.1.1 lockout-time PPPoE interface atm 12/1/1.1 Lockout Configuration (seconds): Min 90, Max 120 Total clients in active lockout: 1 Total clients in lockout grace period: 0 Copyright © 2010, Juniper Networks, Inc.
Page 579: Clearing The Lockout Condition For A Pppoe Client
You can use the pppoe clear lockout interface command to clear the lockout condition for an individual PPPoE client associated with a dynamic PPPoE subinterface column on a static PPPoE major interface. To identify the PPPoE client, you must specify its source MAC address. Copyright © 2010, Juniper Networks, Inc.
Page 580 603 and “show pppoe subinterface” on page 604. Clear the current lockout condition for the PPPoE client associated with the specified source MAC address on the static PPPoE major interface. host1#pppoe clear lockout interface atm 3/0.101 0090.1a10.165e Copyright © 2010, Juniper Networks, Inc.
Page 581 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. See pppoe clear lockout interface. Copyright © 2010, Juniper Networks, Inc.
Page 582: Configuring Ipoa Dynamic Interfaces
Configure a PVC by specifying the VCD, the VPI, the VCI, and the encapsulation type. If you want the router to autodetect the encapsulation type, use the aal5autoconfig option. host1(config-subif)#atm pvc 10 100 22 aal5snap host1(config-subif)#atm pvc 10 100 22 aal5autoconfig Assign a profile. Copyright © 2010, Juniper Networks, Inc.
Page 583 Example 1—Enables autodetection for the IP encapsulation type using the default lockout time range, 1–300 seconds host1(config-subif)#auto-configure ip Example 2—Enables autodetection for the IP encapsulation type using a nondefault lockout time range, 3600–21600 seconds (1–6 hours) Copyright © 2010, Juniper Networks, Inc.
Page 584 Use to configure a local subscriber on the E Series router to support authentication and configuration from RADIUS for a dynamic IPoA or bridged Ethernet interface. When you configure a subscriber, you must specify the following: Copyright © 2010, Juniper Networks, Inc.
Page 585: Configuring Bridged Ethernet Dynamic Interfaces
Use the no version to remove the subscriber. See subscriber. Configuring Bridged Ethernet Dynamic Interfaces A bridged Ethernet interface is IP over bridged Ethernet over ATM 1483 over ATM AAL5 over ATM. Copyright © 2010, Juniper Networks, Inc.
Page 586: Configuring A Dynamic Bridged Ethernet Interface
1–300 seconds. host1(config-subif)#auto-configure bridgedEthernet Configure the subinterface to detect and accept the dynamic bridged Ethernet encapsulation type with a nondefault lockout time range. For example, the Copyright © 2010, Juniper Networks, Inc.
Page 587 Example 2—Enables autodetection for the bridged Ethernet encapsulation type using a nondefault lockout time range of 3600–21600 seconds (1–6 hours) host1(config-subif)#auto-configure bridgedEthernet lockout-time 3600 21600 Example 3—Disables encapsulation type lockout for the bridged Ethernet encapsulation type host1(config-subif)#auto-configure bridgedEthernet lockout-time none Copyright © 2010, Juniper Networks, Inc.
Page 588 RADIUS for a dynamic bridged Ethernet or IPoA interface. For detailed information about how to use this command, see “subscriber” on page 552. Example host1(config-subif)#subscriber bridgedEthernet user-prefix charlie domain myisp password-prefix lucy Copyright © 2010, Juniper Networks, Inc.
Page 589: Configuring Subscriber Management For Ip Subscribers On Dynamic Bridged Ethernet Interfaces
The first part of the example shows how to use the subscriber command to configure RADIUS authentication for IP subscribers on a dynamic bridged Ethernet interface. This configuration method does not support running stateful SRP switchover on the router. Copyright © 2010, Juniper Networks, Inc.
Page 590: Equivalent Configuration Example Using Ip Subscriber Management
! 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. host1(config)#profile east Copyright © 2010, Juniper Networks, Inc.
Page 591: Configuring A Dynamic Interface From A Profile
In contrast to dynamic ATM 1483 subinterfaces, dynamic VLAN subinterfaces support recognition and creation of simultaneous IP and PPPoE upper dynamic interface types. The vlan auto-configure command identifies the encapsulation type. For flexibility, the Copyright © 2010, Juniper Networks, Inc.
Page 592: Profile Characteristics
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 Copyright © 2010, Juniper Networks, Inc.
Page 593: Ipv6 Characteristics
(or removes) a policy to (or from) an interface 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 Copyright © 2010, Juniper Networks, Inc.
Page 594: L2Tp Characteristics
MLPPP interfaces only, enables the creation of dynamic MLPPP 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 Copyright © 2010, Juniper Networks, Inc.
Page 595: Pppoe Characteristics
PPPoE service name table to dynamic interfaces created with this profile sessions—Specifies the maximum number of subinterfaces permitted on a PPPoE major interface url—Causes the PPPoE application to send a URL string to the new client Copyright © 2010, Juniper Networks, Inc.
Page 596: Vlan Characteristics
Figure 56 on page 564 shows how to create a profile and assign characteristics to it. Figure 56: Creating and Configuring a Profile Figure 57 on page 565 shows how to assign a profile to static interfaces. These static interfaces create dynamic interfaces above them. Copyright © 2010, Juniper Networks, Inc.
Page 597: Configuring A Profile
This command initiates either IPv4 or IPv6 in the event you are connecting to a passive client. bridge1483 mtu 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. Copyright © 2010, Juniper Networks, Inc.
Page 598 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 Copyright © 2010, Juniper Networks, Inc.
Page 599 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. For more information, see JunosE Broadband Access Configuration Guide. Example Copyright © 2010, Juniper Networks, Inc.
Page 600 See ip mtu. ip nat Use to mark interfaces that participate in NAT translation as residing on the inside or the outside network. Example host1(config-profile)#ip nat inside Copyright © 2010, Juniper Networks, Inc.
Page 601 Use the no version to delete the route map. See ip route-map ip-subscriber. ip sa-validate Use to enable source address validation on an IP interface. Source address validation verifies that a packet has been sent from a valid source address. Copyright © 2010, Juniper Networks, Inc.
Page 602 RADIUS, then any subsequent use of the profile to create a dynamic interface fails for lack of a VR. See ip virtual-router ipv6 address Use to configure an IPv6 address on an interface to which the profile is attached. Example Copyright © 2010, Juniper Networks, Inc.
Page 603 See ipv6 http redirectUrl. ipv6 mld Use to enable MLD on an interface, and set the MLD version to MLDv2. Example host1(config-profile)#ipv6 mld Use the no version to disable MLD on an interface. See ipv6 mld. Copyright © 2010, Juniper Networks, Inc.
Page 604 Use to specify which IPv6 prefixes the system includes in IPv6 router advertisements. Example host1(config-profile)#ipv6 nd prefix-advertisement 2002:1::/64 60000 45000 onlink autoconfig Use the no version to remove any prefixes from the IPv6 routing advertisements. See ipv6 nd prefix-advertisement. ipv6 nd ra-interval Copyright © 2010, Juniper Networks, Inc.
Page 605 LAN (Ethernet) interface See ipv6 nd suppress-ra. ipv6 policy Use to assign a policy list to the ingress or egress of an interface to which the profile is attached. Example host1(config-profile)#ipv6 policy secondary-input my-policy Copyright © 2010, Juniper Networks, Inc.
Page 606 Use to assign a policy list to the ingress or egress of an interface to which the profile is attached. Example host1(config-profile)#l2tp policy secondary-input my-policy Use the no version to remove the association between a policy list and a profile. See l2tp policy. ppp aaa-profile Copyright © 2010, Juniper Networks, Inc.
Page 607 If you specify a VR other than the default VR as the authentication VR, AAA tightly binds the user to the specified VR. This means that RADIUS cannot override the specified VR context with a new VR context during the authentication process. When Copyright © 2010, Juniper Networks, Inc.
Page 608 32 bytes) reduces the security of your router. Specify the minimum and maximum lengths in bytes in the range 8–63. The maximum length must be greater than or equal to the minimum length. Example host1(config-profile)#ppp chap-challenge-length 24 28 Copyright © 2010, Juniper Networks, Inc.
Page 609 Use to initiate IPv4 for passive clients. By default, PPP creates IP instances when it receives client requests. Example host1(config-profile)#ppp initiate-ip Use the no version to disable initiation of IP. See ppp initiate-ip. Copyright © 2010, Juniper Networks, Inc.
Page 610 Use to prompt the CPE (Customer Premises Equipment) to negotiate the IPCP primary and secondary DNS options that are locally available with the broadband remote access server. Use the no version to disable the command See ppp ipcp prompt-option dns ppp keepalive Copyright © 2010, Juniper Networks, Inc.
Page 611 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. Issuing this command prevents the router from detecting loopback configurations. Example host1(config-profile)#ppp magic-number disable Copyright © 2010, Juniper Networks, Inc.
Page 612 IPv4 interface and the IPv6 interface. Example 1—Sets the maximum number of LCP renegotiation attempts to 5 host1(config-profile)#ppp max-negotiations lcp 5 Example 2—Sets the maximum number of IPCP renegotiation attempts to 30 (the default) host1(config-profile)#ppp max-negotiations ipcp Copyright © 2010, Juniper Networks, Inc.
Page 613 Use the no version to cause the LNS to reject any incoming requests to create dynamic MLPPP interfaces. See ppp multilink enable. ppp multilink multiclass Use in a profile to enable multiclass MLPPP and the creation of multilink classes on a dynamic MLPPP interface. Example Copyright © 2010, Juniper Networks, Inc.
Page 614 This delay enables slow clients to start up and initiate the LCP negotiation. Example host1(config-profile)#ppp passive-mode Use the no version to disable passive mode. See ppp passive-mode. ppp peer Copyright © 2010, Juniper Networks, Inc.
Page 615 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 Copyright © 2010, Juniper Networks, Inc.
Page 616 Use to cause the PPPoE application to send the string to the new client created when the profile is dynamically attached to an IP interface. The message string is saved in nonvolatile storage (NVS). Example host1(config-profile)#pppoe motm string Copyright © 2010, Juniper Networks, Inc.
Page 617 Specify the name of the PPPoE service name table configured with the pppoe service-name-table command from Global Configuration mode. Example host1(config-profile)#pppoe service-name-table myServiceTable1 Use the no version to remove the PPPoE service name table assignment. See pppoe service-name-table. Copyright © 2010, Juniper Networks, Inc.
Page 618 The message string is saved in nonvolatile storage (NVS). PPPoE substitutes certain characters for information in the specified URL string before transmitting: %U username and domain name %u username %d domain name %D profile name %% % character Example host1(config-profile)#pppoe url http://www.relevanturl.com Copyright © 2010, Juniper Networks, Inc.
Page 619 Use to set an advisory connect speed for VLAN subinterfaces that are created with the profile that you are configuring.For detailed information about how to use this command, see “vlan advisory-tx-speed” on page 669. Example Copyright © 2010, Juniper Networks, Inc.
Page 620 See vlan description. vlan policy Use to assign a VLAN policy list to an interface. For more information about keywords, see “vlan policy” on page 672. Example host1(config-profile)#vlan policy input VlanPolicy33 statistics enabled preserve Copyright © 2010, Juniper Networks, Inc.
Page 621: Assigning A Profile To An Interface
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 Copyright © 2010, Juniper Networks, Inc.
Page 622 Example 1—Enables autodetection for the bridged Ethernet encapsulation type using the default lockout time range, 1–300 seconds host1(config-subif)#auto-configure bridgedEthernet Example 2—Enables autodetection for the bridged Ethernet encapsulation type using a nondefault lockout time range of 3600–21600 seconds (1–6 hours) Copyright © 2010, Juniper Networks, Inc.
Page 623: Profile Configuration Examples
Use the no version to remove the subscriber. See subscriber. Profile Configuration Examples The following examples show different ways to configure profiles. This example configures a new profile with IP characteristics only. Copyright © 2010, Juniper Networks, Inc.
Page 624 This example uses the three new profiles configured in the first three examples, and is implicitly assigned via the any encapsulation wildcard. Configuration of dynamic layers is the same regardless of incoming encapsulation detected by ATM. Copyright © 2010, Juniper Networks, Inc.
Page 625: Scripts And Macros
NOTE: For a list of vendor-specific attributes (VSAs) that apply to dynamic interfaces, see JunosE Broadband Access Configuration Guide. Monitoring Upper-Layer Dynamic Interfaces and Profiles You can use the show commands described in this section to monitor configurations created with dynamic interfaces and profiles. Copyright © 2010, Juniper Networks, Inc.
Page 626 3/0 AAL5 Interface ATM 3/0 operational status: lowerLayerDown time since last status change: 00:08:46 SNMP trap link-status: disabled Auto configure ATM 1483 status: disabled InPackets: InBytes: OutPackets: OutBytes: InErrors: OutErrors: InPacketDiscards: 0 OutDiscards: Copyright © 2010, Juniper Networks, Inc.
Page 627 VPI and VCI values, use the atm slot/port/vpi/vci format (for ERX7xx models, ERX14xx models, and ERX310 router) or the slot/adapter/port/vpi/vci format (for E120 and E320 routers) to identify the ATM subinterface (Example 5). Copyright © 2010, Juniper Networks, Inc.
Page 628 ATM 1483 subinterface has one or more upper-layer encapsulation types currently undergoing encapsulation type Copyright © 2010, Juniper Networks, Inc.
Page 629 Lockout state (seconds)—Settings of encapsulation type lockout for the upper-layer encapsulation type indicated Min—Minimum lockout time, in seconds Max—Maximum lockout time, in seconds Current—Current lockout time, in seconds; displays 0 (zero) if lockout is not occurring Copyright © 2010, Juniper Networks, Inc.
Page 630 Example 3—Displays status information for all ATM subinterfaces in the dormantLockout state host1#show atm subinterface status dormantLockout Circuit Interface Interface ATM-Prot VCD VPI VCI Type Encap MTU Status Type ---------- -------- --- --- --- ------ ----- ---- ------------- --------- Copyright © 2010, Juniper Networks, Inc.
Page 631 ATM 0/0.101 RFC-1483 101 0 101 PVC AUTO 9180 up Static Auto configure status : dynamic Auto configure interface(s) : PPPoE Detected 1483 encapsulation : SNAP Detected dynamic interface : PPPoE Interface types in lockout : none Copyright © 2010, Juniper Networks, Inc.
Page 632 VCI—Virtual channel identifier VCD—Virtual circuit descriptor Type—Type of circuit: PVC Encap—Encapsulation method: AUTO, AAL5, MUX, SNAP, ILMI, F4-OAM Category—Service type configured on the VC: UBR, UBR-PCR, NRT-VBR, RT-VBR, or CBR Rx/Tx Peak—Peak rate, in Kbps Copyright © 2010, Juniper Networks, Inc.
Page 633 Use to display static and dynamic interface counts for each interface column. Counts for PPP and PPPoE interface columns are updated when the PPP layer comes Counts for bridged Ethernet and IP over ATM columns are updated when the ATM layer comes up. Copyright © 2010, Juniper Networks, Inc.
Page 634 “Guidelines for Configuring Encapsulation Type Lockout for PPPoE sessions” on page 523 Example host1#show pppoe interface atm 3/0.101 . . . Lockout Configuration (seconds): Min 5, Max 60 Total clients in active lockouts: 0 Total clients in lockout grace period: 0 Copyright © 2010, Juniper Networks, Inc.
Page 635 PPPoE interface atm 12/1/1.1 Lockout Configuration (seconds): Min 90, Max 120 Total clients in active lockout: 1 Total clients in lockout grace period: 0 Client Address Current Elapsed Next -------------- ------- ------- ---- 0090.1a42.527c 0090.1a42.527c Copyright © 2010, Juniper Networks, Inc.
Page 636 Router—Name of the virtual router (VR) assigned to the profile; interfaces created by the profile are attached to this VR Directed Broadcast—Enabled or disabled ICMP Redirects—Enabled or disabled Access Route Addition—Enabled or disabled Copyright © 2010, Juniper Networks, Inc.
Page 637 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 PPP Packet Log—Enabled or disabled Copyright © 2010, Juniper Networks, Inc.
Page 638 PPPoE Log PPPoeControlPacket—Enabled or disabled PPPOE duplicate-protect—Enabled or disabled 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 Copyright © 2010, Juniper Networks, Inc.
Page 639 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 Copyright © 2010, Juniper Networks, Inc.
Page 640 IPv6 ND ManagedConfig—State of the Neighbor Discovery router advertisement managed flag; enabled or disabled IPv6 ND OtherConfig—State of the Neighbor Discovery router advertisement other config flag; enabled or disabled IPv6 ND SuppressRa—Status IPv6 router advertisement suppression; enabled or disabled Copyright © 2010, Juniper Networks, Inc.
Page 641 PPP Max-negotiations LCP : 30 PPP Max-negotiations IPCP : 30 PPP Max-negotiations IPv6CP : 30 PPP IPCP prompt-option DNS :enabled PPP Client Username PPP Client Password PPP Client Authentication PPP Client Ip Address : 0.0.0.0 Copyright © 2010, Juniper Networks, Inc.
Page 642 Discovery router advertisement host1#show profile name ipv6Profile IPv6 Unnumbered interface : loopback 0 IPv6 Router : default IPv6 Src-Addr Validation : Disabled IPv6 Administrative MTU IPv6 ND Enabled : Enabled IPv6 ND ManagedConfig : Disabled Copyright © 2010, Juniper Networks, Inc.
Page 643 IP, PPPoE, or (if no packet has been received) none Interface types in lockout—Encapsulation types currently experiencing lockout: IP, PPPoE, or none Lockout state (seconds)—Settings of encapsulation type lockout for the upper-layer encapsulation type indicated Copyright © 2010, Juniper Networks, Inc.
Page 644 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 ARP responses—Number of ARP responses Copyright © 2010, Juniper Networks, Inc.
Page 645 : Min Max Current Elapsed Next ------------------------------- --- --- ------- ------- ---- 1 300 PPPoE 1 300 In: Bytes 1040, Packets 15 Multicast 0, Broadcast 1 Errors 0, Discards 0 Out: Bytes 984, Packets 15 Copyright © 2010, Juniper Networks, Inc.
Page 646: Troubleshooting Ppp And Pppoe Dynamic Interfaces
JunosE Release Notes, Appendix A, System Maximums. For details about creating and using profiles, see “Configuring a Dynamic Interface from a Profile” on page 559. Access Privileged Exec mode at privilege level 5 or higher. host1>enable 5 Password: ********* host1# Copyright © 2010, Juniper Networks, Inc.
Page 647 0—The user can execute the help, enable, disable, and exit commands. 1—The user can execute commands in User Exec mode plus commands at level 0. 5—The user can execute Privileged Exec show commands plus the commands at levels 1 and 0. Copyright © 2010, Juniper Networks, Inc.
Page 648 JunosE 11.2.x Link Layer Configuration Guide 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 649 WARNING: Execution of this command will cause all dynamic interfaces over atm 2/0.101 to be torn-down. Proceed with profile reassignment? [confirm] yes Profile pppLogConfig replaced by profile pppConfig for ppp. There is no no version. See profile-reassign. Copyright © 2010, Juniper Networks, Inc.
Page 650 JunosE 11.2.x Link Layer Configuration Guide Copyright © 2010, Juniper Networks, Inc.
Page 651: Configuring Dynamic Interfaces Using Bulk Configuration
(CLI) or Simple Network Management Protocol (SNMP). For more information about dynamic interfaces, autodetection, and RADIUS, see “Overview” on page 511 in “Configuring Dynamic Interfaces” on page 511. Copyright © 2010, Juniper Networks, Inc.
Page 652: Bulk Dynamic Interface Configurations
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. Copyright © 2010, Juniper Networks, Inc.
Page 653: Atm Oversubscription For Bulk-Configured Vc Ranges
VCs waiting to become active. The router tears down at least one dynamic interface column in its entirety, which involves administratively shutting down the associated dynamic ATM 1483 subinterface. Copyright © 2010, Juniper Networks, Inc.
Page 654: Vc Ranges
ATM subinterface logs out, thereby making the associated subinterface inactive and eligible for replacement. Platform Considerations You can configure dynamic interfaces on the following E Series Broadband Services Routers: Copyright © 2010, Juniper Networks, Inc.
Page 655: Module Requirements
1 identifies the left IOA bay (E120 router) and the lower IOA bay (E320 router). For example, the following command specifies ATM 1483 subinterface 20 on slot 5, adapter 0, port 0 of an E320 router. host1(config)#interface atm 5/0/0.20 Copyright © 2010, Juniper Networks, Inc.
Page 656: References
Bridged Ethernet PPPoE Figure 58 on page 625 shows the dynamic upper-interface columns supported by dynamic ATM 1483 subinterfaces, and indicates which layers in the columns are static and dynamic. Copyright © 2010, Juniper Networks, Inc.
Page 657: About Configuring Dynamic Atm 1483 Subinterfaces
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 Copyright © 2010, Juniper Networks, Inc.
Page 658: Atm 1483 Base Profiles
You can create different profiles for each upper-interface encapsulation type, or you can create a single profile that includes attributes for multiple encapsulation types. Copyright © 2010, Juniper Networks, Inc.
Page 659: Additional Profile Characteristics For Upper Interfaces
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 Copyright © 2010, Juniper Networks, Inc.
Page 660: Bulk Configuration And Vc Classes
For details about configuring and using VC classes, including information about how precedence levels affect how the router determines attributes values for dynamically created circuits, see “Configuring ATM VC Classes” on page 52 in “Configuring ATM” on Copyright © 2010, Juniper Networks, Inc.
Page 661: Bulk Configuration And Cac
Overriding the base profile assignment for an ATM PVC with a profile that includes debugging attributes enables you to troubleshoot problems with ATM 1483 dynamic subinterface columns created on the specified PVC. The overriding profile, like the original Copyright © 2010, Juniper Networks, Inc.
Page 662: Changing Vc Subranges
Static ATM interfaces and circuits defined within a bulk-configured VC subrange are stored in NVS and preserved after a reboot. The base profile associated with the VC subrange does not apply to any statically defined ATM interfaces that fall within the subrange. Copyright © 2010, Juniper Networks, Inc.
Page 663: Terminating Stale Pppoa Subscribers And Restarting Lcp Negotiations
IP upper-layer interfaces when the CPE restarts LCP negotiations. For details about the operation and benefits of this feature, see “Terminating Stale PPPoA Subscribers and Restarting LCP Negotiations” on page 530 in “Configuring Dynamic Copyright © 2010, Juniper Networks, Inc.
Page 664: Authenticating Subscribers On Dynamic Bridged Ethernet Over Dynamic Atm Interfaces
If stateful SRP switchover is disabled or not running on your router, you can continue to use the atm atm1483 subscriber command to configure IP subscribers on dynamic bridged Ethernet interfaces to support RADIUS authentication. Copyright © 2010, Juniper Networks, Inc.
Page 665: Configuring A Dynamic Atm 1483 Subinterface
Configure the ATM 1483 subinterface for autodetection of the PPP upper-interface encapsulation type. Configure the ATM 1483 subinterface for autodetection of the IP upper-interface encapsulation type using a nondefault lockout time range of 3600–7200 seconds (1–2 hours). Copyright © 2010, Juniper Networks, Inc.
Page 666 For example, the following command creates a VC range named myBulkConfig made up of two VC subranges that configure a total of 5,000 virtual circuits. host1(config-if)#atm bulk-config myBulkConfig vc-range 0 2 101 1100 vc-range 3 6 201 700 Copyright © 2010, Juniper Networks, Inc.
Page 667 For the bridged Ethernet, IP, PPP, and PPPoE encapsulation types, you can optionally specify the lockout time range for the encapsulation type. For more information, see “Encapsulation Type Lockout” on page 521 . Examples host1(config-profile)#atm atm1483 auto-configure ip lockout-time 3600 7200 host1(config-profile)#atm atm1483 auto-configure pppoe Copyright © 2010, Juniper Networks, Inc.
Page 668 The router automatically postpends the physical location of the user to the username string. The username format is userName.slot.port.vpi.vci. The resulting username string is then used to authenticate the subscriber with the RADIUS server. Copyright © 2010, Juniper Networks, Inc.
Page 669 Each VC range consists of one or more nonoverlapping VC subranges. A VC subrange is a group of VCs that resides within the VPI and VCI ranges you specify. You can configure multiple VC ranges on an ATM AAL5 interface. Copyright © 2010, Juniper Networks, Inc.
Page 670 0 1 101 600 vc-range 3 5 201 3200 Use the no version to remove the specified VC range from the ATM AAL5 interface, to remove the specified subranges from the specified VC range, or to remove all subranges Copyright © 2010, Juniper Networks, Inc.
Page 671 VBR-RT as the service type; you can select rt only if you set the peak, average, and burst parameters cbr—Selects CBR as the service type; you must set the CBR rate in Kbps Copyright © 2010, Juniper Networks, Inc.
Page 672 IOA bay (E320 router). port—Port number on the IOA subinterface—Number of the subinterface in the range 1–2147483647 For more information, see “Creating a Basic Configuration” on page 20 in “Configuring ATM” on page 3. Examples Copyright © 2010, Juniper Networks, Inc.
Page 673: Configuring Overriding Profile Assignments
Configuring overriding profile assignments includes the following tasks: Assigning an overriding profile to an ATM PVC within a bulk-configured VC subrange Removing an overriding profile assignment from an ATM PVC Removing overriding profile assignments from a VC range or VC subrange Copyright © 2010, Juniper Networks, Inc.
Page 674: Assigning An Overriding Profile To An Atm Pvc
PVC with VPI 6 and VCI 901. This PVC exists within the second VC subrange (VPIs 5–7 and VCIs 21–2000) configured in Step 2. host1(config-if)#profile atm1483 bulk-config-name myBulkConfig pvc 6 901 myDebugProfile Copyright © 2010, Juniper Networks, Inc.
Page 675: Removing An Overriding Profile Assignment From An Atm Pvc
PVC. (Optional) Use the show atm bulk-config command to verify the removal of the overriding profile assignment. For more information about using this command, see “show atm bulk-config” on page 683. Copyright © 2010, Juniper Networks, Inc.
Page 676: Removing Overriding Profile Assignments From A Vc Range Or Vc Subrange
You must issue this command to enable creation of a dynamic ATM 1483 subinterface. Example host1(config-if)#auto-configure atm1483 Use the no version to terminate autodetection of the ATM 1483 encapsulation type. See auto-configure atm1483. profile atm1483 bulk-config-name Copyright © 2010, Juniper Networks, Inc.
Page 677 See profile atm1483 bulk-config-name pvc. shutdown Use to disable an interface. When you disable a dynamic ATM 1483 interface, the shutdown command deletes the ATM 1483 dynamic subinterface column and removes the dynamic ATM 1483 subinterface. Example host1(config-subif)#shutdown Copyright © 2010, Juniper Networks, Inc.
Page 678: Changing Vc Subranges
6 6 601 650 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 Copyright © 2010, Juniper Networks, Inc.
Page 679: Removing Vc Subranges
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. Copyright © 2010, Juniper Networks, Inc.
Page 680: Merging 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 Copyright © 2010, Juniper Networks, Inc.
Page 681 3 5 201 3200 Use the no version to remove the specified VC range from the ATM AAL5 interface, to remove the specified subranges from the specified VC range, or to remove all subranges Copyright © 2010, Juniper Networks, Inc.
Page 682: Configuring Static Atm Interfaces Within Vc Subranges
Use the no version to enable the specified VC subrange or all subranges in a VC range. See atm bulk-config shutdown. Configuring Static ATM Interfaces Within VC Subranges You can do either of the following on an E Series router: Copyright © 2010, Juniper Networks, Inc.
Page 683: Creating Static Atm Interfaces Within Vc Subranges
Create a bulk-configured VC range that includes the VPI and VCI values of the previously configured ATM PVC. In this example, the VPI range (0–2) includes VPI 1, and the VCI range (100–250) includes VCI 101. host1(config)#interface atm 3/1 Copyright © 2010, Juniper Networks, Inc.
Page 684 For information about specifying the ATM interface or subinterface, see “interface atm” on page 640. Examples host1(config)#interface atm 5/0.1 host1(config)#interface atm 4/0/2 Use the no version to remove the interface or subinterface. See interface atm. mpls-relay Copyright © 2010, Juniper Networks, Inc.
Page 685: Configuring Vlan Dynamic Subinterfaces
VLAN subinterfaces, and indicates which layers in the columns are static and dynamic. Figure 59: Dynamic Interface Columns over Dynamic VLAN Subinterfaces Unlike ATM 1483, you can configure both IP and PPPoE over a single dynamic VLAN subinterface (Figure 60 on page 654). Copyright © 2010, Juniper Networks, Inc.
Page 686: About Configuring Dynamic Vlan Subinterfaces
Dynamic VLAN subinterfaces function identically to static VLAN subinterfaces, except for the manner in which they are created and configured. However, dynamic VLANs Copyright © 2010, Juniper Networks, Inc.
Page 687: Vlan Base Profiles
For information, see “vlan advisory-rx-speed” on page 669. advisory-tx-speed—Sets an advisory connect speed for VLAN subinterfaces that are created with this profile. For information, see “vlan advisory-tx-speed” on page 669. Copyright © 2010, Juniper Networks, Inc.
Page 688: Nested Profile Assignments
IP attributes in vlanProfilePppoe. For information about creating profiles for upper-interface encapsulation types, see “Configuring a Dynamic Interface from a Profile” on page 559 in “Configuring Dynamic Interfaces” on page 511. Copyright © 2010, Juniper Networks, Inc.
Page 689: Additional Profile Characteristics For Upper Interfaces
VLAN subinterface until it receives incoming data traffic on the VLAN ID or S-VLAN ID. After you create a named VLAN range, you cannot remove the underlying VLAN major interface until you issue the no vlan bulk-config command to remove the VLAN range from that interface. Copyright © 2010, Juniper Networks, Inc.
Page 690: Information
Insertion of the agent-circuit-identifier string in DHCP or PPPoE messages For example, the following configurations uniquely identify subscribers by means of VLAN encapsulation: Subscriber packets received from the DSLAM are single-tagged with a VLAN ID Copyright © 2010, Juniper Networks, Inc.
Page 691: Dynamic Interface Creation
“profile vlan bulk-config” on page 667 . As a final step, you must issue “auto-configure vlan” on page 666 . This command configures the VLAN major interface to support autodetection of the VLAN dynamic encapsulation type. Copyright © 2010, Juniper Networks, Inc.
Page 692: Overriding Base Profile Assignments
S-VLAN ID on a static VLAN subinterface. Configuring static VLAN subinterfaces within VLAN subranges can be useful when you want to create a column statically for users who have difficulty logging on. You might also want to configure static Copyright © 2010, Juniper Networks, Inc.
Page 693: Configuring A Dynamic Vlan Subinterface
Step 5. host1(config)#profile myIpProfile host1(config-profile)#ip inactivity-timer 200 host1(config-profile)#ip auto-configure ip-subscriber include-primary Create the base profile for the dynamic VLAN subinterface by assigning the profile a name. Copyright © 2010, Juniper Networks, Inc.
Page 694 Assign the base profile configured for the VLAN subinterface to the VLAN range configured on the major VLAN interface. host1(config-if)#profile vlan bulk-config myBulkConfig vlanBaseProfile Configure the VLAN major interface to support autodetection of the VLAN dynamic encapsulation type. host1(config-if)#auto-configure vlan Copyright © 2010, Juniper Networks, Inc.
Page 695: Configuring Dynamic Vlan Subinterfaces Based On Agent Circuit Identifier Information
Assign the base profile configured for the VLAN subinterface to the VLAN range configured on the major VLAN interface. host1(config-if)#profile vlan bulk-config myNewBulkConfig vlanMyBaseProfile Configure the VLAN major interface to support autodetection of the VLAN dynamic encapsulation type. host1(config-if)#auto-configure vlan Copyright © 2010, Juniper Networks, Inc.
Page 696: Configuring Overriding Profile Assignments For Vlan Major Interfaces
VLAN range or within a different VLAN range. For example, the following command assigns the overriding profile overrideVoiceSubscriber to the VLAN ID 160. This S-VLAN ID exists within the VLAN subrange configured in Step 2. host1(config-if)#profile vlan override bulk-config-name myBulkConfig svlan 120 202 overrideVoiceSubscriber Copyright © 2010, Juniper Networks, Inc.
Page 697: Removing An Overriding Profile Assignment From A Vlan
VLAN ID or S-VLAN ID. (Optional) Use the show vlan profile override command to verify the removal of the overriding profile assignment. For more information about using this command, see “Monitoring Dynamic Interfaces and Profiles” on page 682. Copyright © 2010, Juniper Networks, Inc.
Page 698: Subrange
Use the no version to disable VLAN on an interface. See encapsulation vlan. interface fastEthernet Use to select a Fast Ethernet interface. For information about specifying a Fast Ethernet interface, see “interface fastEthernet” on page 666. Example host1(config)#interface fastEthernet 4/1 Copyright © 2010, Juniper Networks, Inc.
Page 699 You must specify both of the following: Name assigned to the VLAN range on a VLAN subinterface, as specified in “vlan bulk-config” on page 678 Name assigned to the base profile for a dynamic VLAN subinterface Example Copyright © 2010, Juniper Networks, Inc.
Page 700 Because the shutdown command removes the dynamic VLAN subinterface from the router, issuing a subsequent no version of this command has no effect; that is, it does not restart the disabled subinterface. See shutdown. svlan ethertype Copyright © 2010, Juniper Networks, Inc.
Page 701 The range is 0–2147483647 kbps; 0 indicates no advisory speed setting. Example 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 Copyright © 2010, Juniper Networks, Inc.
Page 702 When you create a bulk-configured VLAN range, you must specify the following: A name of up to 80 alphanumeric characters; this is also referred to as the bulk configuration name The starting and ending VLAN ID or S-VLAN ID values (inclusive) for each VLAN subrange Copyright © 2010, Juniper Networks, Inc.
Page 703 See vlan bulk-config. vlan description Use to assign a description to VLAN subinterfaces that are created with this profile. You can use a maximum of 64 characters for the description or to name the alias. Copyright © 2010, Juniper Networks, Inc.
Page 704 Forward Forward – ip classifier-list clTwo ip classifier-list clFour – Forward Forward – ip classifier-list clThree ip classifier-list clFive – Forward Forward – classifier-list * classifier-list * statistics from plOne are saved Copyright © 2010, Juniper Networks, Inc.
Page 705: Changing Vlan Subranges
See vlan service-profile. Changing VLAN Subranges Changing VLAN subranges within a bulk-configured VLAN range includes the following tasks: Adding new VLAN subranges to an existing VLAN range Removing VLAN subranges from an existing VLAN range Copyright © 2010, Juniper Networks, Inc.
Page 706: Adding Vlan Subranges
You can remove VLAN subranges from an existing VLAN range if no dynamic VLAN subinterfaces currently exists for any circuit within those subranges. The removal operation fails if any such dynamic VLAN subinterface exists. You must first remove the dynamic Copyright © 2010, Juniper Networks, Inc.
Page 707: Modifying Vlan Subranges
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. Copyright © 2010, Juniper Networks, Inc.
Page 708: Merging Vlan Subranges
2 and 5 are merged, the new merged subrange has an instance value of 2. Changing the Administrative State of VLAN Subranges VLAN subranges have an administrative state that enables you to remove dynamic VLAN subinterfaces on various subranges that belong to a single VLAN range. This functionality Copyright © 2010, Juniper Networks, Inc.
Page 709 VLAN ranges belonging to that bulk configuration, including those based on double-tagged S-VLANs or agent-circuit-identifier information, are disabled. The following command shuts down all four subranges belonging to the named VLAN range, test, regardless of their current state. Copyright © 2010, Juniper Networks, Inc.
Page 710 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 Copyright © 2010, Juniper Networks, Inc.
Page 711 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. host1(config-if)#interface gigabitEthernet 0/0.2100 Copyright © 2010, Juniper Networks, Inc.
Page 712 To fully configure the VLAN subinterface, assign an IP address or make it unnumbered. host1(config-if)#ip unnumbered loopback 0 encapsulation vlan Use to configure VLAN as the encapsulation method on an interface. Issuing this command creates the VLAN major interface. Example host1(config-if)#encapsulation vlan Copyright © 2010, Juniper Networks, Inc.
Page 713 Use the no version to remove the specified VLAN range from the VLAN major interface, to remove the specified subranges from the specified VLAN range, or to remove all subranges from the specified VLAN range. The no version also removes any overriding Copyright © 2010, Juniper Networks, Inc.
Page 714 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 Copyright © 2010, Juniper Networks, Inc.
Page 715 Assigned Profile—Base profile name for the dynamic ATM 1483 subinterface assigned to this VC subrange with “profile atm1483 bulk-config-name” on page 645 . When no profile is assigned to the VC subrange, the field displays none assigned. Copyright © 2010, Juniper Networks, Inc.
Page 716 ATM AAL5 3/0 test 1 161 overrideProfile1 Active 2 profile override(s) found Example 2—Displays information about base profile assignments and overriding profile assignments for all VC ranges configured on a specified ATM AAL5 interface Copyright © 2010, Juniper Networks, Inc.
Page 717 1 161 overrideProfile1 Active 2 profile override(s) found Example 5—Displays information only about overriding profile assignments for a particular VC range configured on a specified ATM AAL5 interface host1#show atm bulk-config atm 3/0 override Profile override(s): Copyright © 2010, Juniper Networks, Inc.
Page 718 To display status information only for ATM subinterfaces with a specific operating status, use the status keyword with one of the following status values. (See the Status field description for an explanation of these values.) dormant dormantLockout down lowerLayerDown Copyright © 2010, Juniper Networks, Inc.
Page 719 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: Copyright © 2010, Juniper Networks, Inc.
Page 720 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 Copyright © 2010, Juniper Networks, Inc.
Page 721 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 Static 3 interface(s) found Example 2—Displays summary information for all ATM subinterfaces shown in Example Copyright © 2010, Juniper Networks, Inc.
Page 722 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 Copyright © 2010, Juniper Networks, Inc.
Page 723 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 VCD—Virtual circuit descriptor Copyright © 2010, Juniper Networks, Inc.
Page 724 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. show columns Copyright © 2010, Juniper Networks, Inc.
Page 725 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; for more information about the lockout grace period, see Copyright © 2010, Juniper Networks, Inc.
Page 726 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 Copyright © 2010, Juniper Networks, Inc.
Page 727 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 interface is unnumbered Copyright © 2010, Juniper Networks, Inc.
Page 728 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 Copyright © 2010, Juniper Networks, Inc.
Page 729 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 enabled or disabled for a dynamic ATM 1483 subinterface Copyright © 2010, Juniper Networks, Inc.
Page 730 ATM1483 Profile—Name of the profile assigned to the specified upper-interface encapsulation type (bridged Ethernet, IP, PPP, or PPPoE); these profiles are referenced in the base profile for a dynamic ATM 1483 subinterface as nested profile assignments Copyright © 2010, Juniper Networks, Inc.
Page 731 Ignore DF Bit : Disabled Filter Option Packets : Disabled Administrative MTU : 1500 TCP MSS value Inactivity Timer : Disabled Route Map Name : Disabled Auto Detect : Disabled Auto Configure : Disabled Copyright © 2010, Juniper Networks, Inc.
Page 732 ATM1483 Advisory Rx Speed 2000000000 ATM1483 PVC OAM Administrative status: enabled ATM1483 PVC OAM Loopback frequency: ATM1483 Ip Subscriber information: user : elaine domain : jpeterman.com password : putty ATM1483 IP Profile : none assigned Copyright © 2010, Juniper Networks, Inc.
Page 733 VLAN subrange with “profile vlan bulk-config” on page 667 . When no profile is assigned to the VLAN subrange, the field displays none assigned. Admin State—Administrative state of the VLAN subrange: up or down Copyright © 2010, Juniper Networks, Inc.
Page 734 Use to display information about the dynamic VLAN subinterfaces that have been created with an overriding profile assignment. Use the bulk-config keyword to display information about bulk-configured ranges. Field descriptions Interface—Type and specifier of the VLAN subinterface Svlan Id—S-VLAN ID value, if configured Copyright © 2010, Juniper Networks, Inc.
Page 735 Status—Status of the VLAN subinterface: up, down, dormant, lowerLayerDown, absent MTU—Maximum allowable size (in bytes) of the MTU for the VLAN subinterface Svlan Id—S-VLAN ID value, if configured Vlan Id—VLAN ID value for the VLAN subinterface Ethertype—S-VLAN Ethertype value, if configured Copyright © 2010, Juniper Networks, Inc.
Page 736 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 Multicast—Number of multicast packets received on the VLAN or S-VLAN subinterface Copyright © 2010, Juniper Networks, Inc.
Page 737 100 53 Interface Status MTU Svlan Id Vlan Id Ethertype Type ------------------ ------ ---- ------- ------- --------- ------- FastEthernet 0/0.1 1526 100 0x9100 Static FastEthernet 4/6.1 1526 100 0x9100 Dynamic 2 vlan subinterfaces found Copyright © 2010, Juniper Networks, Inc.
Page 738 ---- ---- Dynamic 2 vlan subinterfaces found * Created via agent circuit identifier host1#show vlan subinterface agent-circuit-identifier Interface Svlan Id Agent-Circuit-Identifier ------------------------- -------- -------------------------- FastEthernet 4/0.1 ---- FastEthernet 4/0.2 0200D0CB2729E5 See show vlan subinterface. Copyright © 2010, Juniper Networks, Inc.
Page 739: Index
PART 2 Index Index on page 709 Copyright © 2010, Juniper Networks, Inc.
Page 740 JunosE 11.2.x Link Layer Configuration Guide Copyright © 2010, Juniper Networks, Inc.
Page 741 ATM passthrough..............5 interworking functions..........382 cable lengths..............28 accounting statistics CAC..................7 terminated PPP session..........281 CC cells................14 active discovery mode cell scrambling payload..........29 and OAM link-fault management......230 configuring...........20, 388, 406 configuration on dynamic interfaces............518 provider edge devices........230 Copyright © 2010, Juniper Networks, Inc.
Page 742 ATM VC Configuration mode..........43 restarting LCP negotiations for PPPoA ATM virtual circuit (VC)............167 clients................631 atm aal5 commands atm aal5 description............40 atm aal5 shutdown............24 atm aal5 snmp link-status.........24 ATM Adaptation Layer. See AAL Copyright © 2010, Juniper Networks, Inc.
Page 743 DSLAMs connected to an access monitoring..............487 concentrator.............392 bridge interfaces one DSLAM connected to an access configuring..............473 concentrator.............392 defined................466 usage of the IWF PPPoE tag monitoring..............487 in identifying IWF sessions......383 supported configurations.........467 B-RAS applications, with PPP sessions.......261 types of................467 Copyright © 2010, Juniper Networks, Inc.
Page 744 MAC addresses..........465, 487 MLPPP features............304 monitoring..............487 channelized T3 interfaces overview................465 end-to-end fragmentation and platform considerations...........470 reassembly..............116 prerequisites..............471 MLPPP features............304 references................471 CHAP (Challenge Handshake Authentication setting statistics baselines........487 Protocol)................261 subscriber policies............468 unsupported features..........470 broadcast command............478 Copyright © 2010, Juniper Networks, Inc.
Page 745 OAM PDUs to the clear bridge interface..........487 multiplexer............229 clock commands interface between clock source OAM client and internal sublayer POS interfaces.............362 elements............229 control PVCs, creating............44 Copyright © 2010, Juniper Networks, Inc.
Page 746 Duplicate event notification OAM PDUs frame-relay lmi commands ........108 viewing................248 show frame-relay lmi command ......121 debugging PPP and PPPoE dynamic interfaces................614 description, interface ATM 1483 subinterfaces, exporting......41 ATM interfaces..............40 ATM virtual paths............41 Frame Relay interfaces..........108 POS interfaces.............114, 364 Copyright © 2010, Juniper Networks, Inc.
Page 747 Ethernet interface columns....532 benefits................521 E120 and E320 routers........517, 623 configuring..........521, 528, 550 E320 routers..........152, 170, 517 criteria used in determining inserting dynamic IP routes intorouting for IWF PPPoE sessions........523 table................519 monitoring............593, 682 oversubscription, ATM........515, 621 Copyright © 2010, Juniper Networks, Inc.
Page 748 Event notification OAM PDUs types.................263 for tracking frame seconds summary ECMP (equal-cost multipath) errors..............233 MLFR alternative to............131 Errored Symbol Period TLV MLPPP alternative to..........299 in Event notification OAM PDUs enable commands for tracking symbol errors........233 enable................614 Copyright © 2010, Juniper Networks, Inc.
Page 749 CE-side load balancing......200 dying gasp..............242 interoperation with OAM link-fault link fault..............242 management configuring, procedure..........238 operation of 802.3ah below the LAG disabling sublayer..............236 remote loopback functionality on a remote IP interfaces peer..............242 example..............205 discovery, overview.............230 Copyright © 2010, Juniper Networks, Inc.
Page 750 E120 and E320 routers........225 viewing ERX7xx, ERX14xx, and ERX310 configurations for all interfaces on which models..............225 OAM is enabled..........253 prerequisite details about processing of packets, for configuring settings........238 statistics............248 Copyright © 2010, Juniper Networks, Inc.
Page 751 PPPoE............394 responding to received notices......235 specifying an interface....406, 473, 542, 666 supported TLVs for tracking link faults fault management, ATM............14 Errored Frame Event..........232 Errored Frame Seconds Summary Event..............232 Errored Symbol Period Event ......232 Copyright © 2010, Juniper Networks, Inc.
Page 752 SNMP link status processing........115 groups, bridge. See bridge groups unicast addressing............105 User-to-Network Interface........105 frame-relay commands.............108 hash-based packet distribution with MLPPP ..304 frame-relay class............116 HDLC (High-Level Data Link Control), Cisco. See frame-relay description..........108 Cisco HDLC frame-relay fragment..........116 Copyright © 2010, Juniper Networks, Inc.
Page 753 OAM association failure with remote peer not supporting loopback.............231 IEEE 802.1Q................167 timer setting IEEE 802.1w................200 maximum value............231 IEEE 802.1w (Rapid Reconfiguration of Spanning minimum value.............231 Tree)..................200 rate of transmission in milliseconds.....231 Copyright © 2010, Juniper Networks, Inc.
Page 754 IPv6 International Telecommunication Union. See ITU neighbor discovery, defining........570 Internet Protocol Control Protocol. See IPCP ipv6 commands interworking function See IWF ipv6 address..............570 Inverse ARP................51 ipv6 mld................570 ipv6 mtu................570 ipv6 nd................570 ipv6 nd managed-config-flag........570 Copyright © 2010, Juniper Networks, Inc.
Page 755 LACP (Link Aggregation Control Protocol)....198 with duplicate MAC addresses of clients PPPoE subinterfaces........202, 205 ATM-to-Ethernet interworking......383 redundant member link behavior......212 dependence on pppoe sessions command configuration............385 limit on maximum number of sessions.............385 Copyright © 2010, Juniper Networks, Inc.
Page 756 ATM interfaces..............29 when enabled on the local entity....227 POS interfaces.............364 impact on performance and memory usage when disabled on the local entity....227 when enabled on the local entity....227 Copyright © 2010, Juniper Networks, Inc.
Page 757 Ethernet........447 authentication...............310 validation on bridged Ethernet interfaces..447 bundle................299 MAC address bundle limits..............304 usage in dynamic encapsulation lockout bundle name and RADIUS........313 for IWF PPPoE sessions........523 commands, contextual differences of....310 Copyright © 2010, Juniper Networks, Inc.
Page 758 S-VLAN tunnels......182, 183 mpls commands NBMA....................13 mpls.................156, 202 NBMA (nonbroadcast multiaccess).........13 mpls (subscriber policies)........478 configuring................37 mpls atm vci range ............454 description.................13 mpls-relay..............652 Inverse ARP...............13 MPLS over VLAN over bridged Ethernet.....453 point-to-multipoint............13 MRRU LCP configuration option........300 Copyright © 2010, Juniper Networks, Inc.
Page 759 OAM PDUs received from the benefits of ..............230 remote peer............228 IEEE 802.3ah enhancements and......230 monitoring OAM PDUs from the remote supported...............230 peer................228 types of oam commands discovery..............230 oam ais-rdi..............49, 56 link monitoring.............230 oam cc................50, 56 Copyright © 2010, Juniper Networks, Inc.
Page 760 PDUs resent to the local entity..............235 Copyright © 2010, Juniper Networks, Inc.
Page 761 OAM association with link-fault event bit in Flags field status in show command output....232 higher preferential processing.......234 OAM state machine port in the down state until discovery process completion....231 Copyright © 2010, Juniper Networks, Inc.
Page 762 660 and OAM link-fault management......230 removing from PVC............642 configuration on removing from VC range or subrange....642 customer edge devices........230 removing from VLAN range or subrange...664 removing from VLAN subinterface......664 VLANs................664 Copyright © 2010, Juniper Networks, Inc.
Page 763 IP...............438 Async-Control-Character-Map (ACCM) Cisco HDLC..............504 option................259 dynamic interfaces........199, 517, 622 authentication..........261, 276, 310 Ethernet interfaces............169 configuring...............271 Frame Relay..............107 configuring dynamic interfaces......525 higher-level protocols over Ethernet.....152 E120 and E320 routers........269, 303 MLFR.................133 E320 routers..............270 Copyright © 2010, Juniper Networks, Inc.
Page 764 B-RAS..............392 ppp shutdown mpls............276 N:1 association between DSLAMs and the ppp shutdown osi............276 B-RAS..............392 See also show ppp commands dynamic encapsulation type PPP Multilink. See MLPPP lockout..............523, 544 clearing lockout condition.......547 configuring............544 Copyright © 2010, Juniper Networks, Inc.
Page 765 ATM 1483 subinterfaces....625 See also show pppoe commands for dynamic VLAN subinterfaces......654 PPPoE over S-VLAN over bridged Ethernet....458 monitoring............593, 682 PPPoE over VLAN over bridged Ethernet....453 overriding base profile assignments.........629, 641, 660 Copyright © 2010, Juniper Networks, Inc.
Page 766 418 by the remote peer..........235 radius remote-circuit-id-format....375, 418 remote OAM entity radius remote-circuit-id-format (dsl-forum-1 prerequisite for enabling loopback operation keyword)............377, 418 on...................242 ranges, VC. See VC ranges, bulk configuration of Copyright © 2010, Juniper Networks, Inc.
Page 767 Ethernet..............458 show frame-relay pvc.........121, 138 scrambling ATM cell payload..........29 show frame-relay subinterface......127, 148 scripts show frame-relay summary......127, 148 using to configure dynamic interfaces....593 show hdlc interface command........509 SDH (Synchronous Digital Hierarchy)....359, 360 Copyright © 2010, Juniper Networks, Inc.
Page 768 Keep-Alive protocol...........503 VLAN, dynamic.............653 keepalive interval............506 subnet mask overview................503 assigning to PPP interface........273 See also Cisco HDLC subnetwork attachment point. See SNAP subranges, VC. See VC subranges subscriber command...514, 519, 552, 556, 591, 593 Copyright © 2010, Juniper Networks, Inc.
Page 769 29, 72, 106, 116 in the show command output.......233 unicast addressing...............105 enabling on IOAs that do not support unicast command..............478 and events generation for that link....233 monitoring of on IOAs that do not support......233 Copyright © 2010, Juniper Networks, Inc.
Page 770 IPv4 and IPv6 over Dynamic PPPoE....534 overview................627 virtual path connection. See VPC restarting LCP negotiations for PPPoA virtual path descriptions, assigning........41 clients................631 virtual path identifier (VPI) tags mapped to C-VLAN tags in ATM-to-Ethernet conversion.....382 Copyright © 2010, Juniper Networks, Inc.
Page 771 VLAN subranges changing X.21/V.35 interfaces adding to VLAN range........673 MLPPP features............304 changing administrative state.......673 XFPs (10-gigabit small form-factor pluggable configuring.............673 transceivers)................161 merging..............673 monitoring.............695 overview..............660 Copyright © 2010, Juniper Networks, Inc.
Page 772 JunosE 11.2.x Link Layer Configuration Guide Copyright © 2010, Juniper Networks, Inc.

This manual is also suitable for:

Junose 11.2