- play_arrow Configuring Dynamic VLANs for Subscriber Access Networks
- play_arrow Dynamic VLAN Overview
- Subscriber Management VLAN Architecture Overview
- Dynamic 802.1Q VLAN Overview
- Static Subscriber Interfaces and VLAN Overview
- Pseudowire Termination: Explicit Notifications for Pseudowire Down Status
- Configuring an Access Pseudowire That Terminates into VRF on the Service Node
- Configuring an Access Pseudowire That Terminates into a VPLS Routing Instance
- play_arrow Configuring Dynamic Profiles and Interfaces Used to Create Dynamic VLANs
- Configuring a Dynamic Profile Used to Create Single-Tag VLANs
- Configuring an Interface to Use the Dynamic Profile Configured to Create Single-Tag VLANs
- Configuring a Dynamic Profile Used to Create Stacked VLANs
- Configuring an Interface to Use the Dynamic Profile Configured to Create Stacked VLANs
- Configuring Interfaces to Support Both Single and Stacked VLANs
- Overriding the Dynamic Profile Used for an Individual VLAN
- Configuring a VLAN Dynamic Profile That Associates VLANs with Separate Routing Instances
- Automatically Removing VLANs with No Subscribers
- Verifying and Managing Dynamic VLAN Configuration
- play_arrow Configuring Subscriber Authentication for Dynamic VLANs
- Configuring an Authentication Password for VLAN or Stacked VLAN Ranges
- Configuring Dynamic Authentication for VLAN Interfaces
- Subscriber Packet Type Authentication Triggers for Dynamic VLANs
- Configuring Subscriber Packet Types to Trigger VLAN Authentication
- Configuring VLAN Interface Username Information for AAA Authentication
- Using DHCP Option 82 Suboptions in Authentication Usernames for Autosense VLANs
- Using DHCP Option 18 and Option 37 in Authentication Usernames for DHCPv6 Autosense VLANs
- play_arrow Configuring VLANs for Households or Individual Subscribers Using ACI-Based Dynamic VLANs
- Agent Circuit Identifier-Based Dynamic VLANs Overview
- Configuring Dynamic VLANs Based on Agent Circuit Identifier Information
- Defining ACI Interface Sets
- Configuring Dynamic Underlying VLAN Interfaces to Use Agent Circuit Identifier Information
- Configuring Static Underlying VLAN Interfaces to Use Agent Circuit Identifier Information
- Configuring Dynamic VLAN Subscriber Interfaces Based on Agent Circuit Identifier Information
- Verifying and Managing Agent Circuit Identifier-Based Dynamic VLAN Configuration
- Clearing Agent Circuit Identifier Interface Sets
- play_arrow Configuring VLANs for Households or Individual Subscribers Using Access-Line-Identifier Dynamic VLANs
- Access-Line-Identifier-Based Dynamic VLANs Overview
- Configuring Dynamic VLANs Based on Access-Line Identifiers
- Defining Access-Line-Identifier Interface Sets
- Configuring Dynamic Underlying VLAN Interfaces to Use Access-Line Identifiers
- Configuring Static Underlying VLAN Interfaces to Use Access-Line Identifiers
- Configuring Dynamic VLAN Subscriber Interfaces Based on Access-Line Identifiers
- Verifying and Managing Configurations for Dynamic VLANs Based on Access-Line Identifiers
- Clearing Access-Line-Identifier Interface Sets
- play_arrow High Availability for Service VLANs
-
- play_arrow Configuring DHCP Subscriber Interfaces
- play_arrow VLAN and Demux Subscriber Interfaces Overview
- play_arrow Configuring Sets of Demux Interfaces to Provide Services to a Group of Subscribers
- play_arrow Configuring Dynamic Demux Interfaces That are Created by DHCP
- play_arrow Configuring DHCP Subscriber Interfaces over Aggregated Ethernet
- Static and Dynamic VLAN Subscriber Interfaces over Aggregated Ethernet Overview
- Static or Dynamic Demux Subscriber Interfaces over Aggregated Ethernet Overview
- Configuring a Static or Dynamic VLAN Subscriber Interface over Aggregated Ethernet
- Configuring a Static or Dynamic IP Demux Subscriber Interface over Aggregated Ethernet
- Configuring a Static or Dynamic VLAN Demux Subscriber Interface over Aggregated Ethernet
- Example: Configuring a Static Subscriber Interface on a VLAN Interface over Aggregated Ethernet
- Example: Configuring a Static Subscriber Interface on an IP Demux Interface over Aggregated Ethernet
- Example: Configuring IPv4 Static VLAN Demux Interfaces over an Aggregated Ethernet Underlying Interface with DHCP Local Server
- Example: Configuring IPv4 Dynamic VLAN Demux Interfaces over an Aggregated Ethernet Underlying Interface with DHCP Local Server
- Example: Configuring IPv6 Dynamic VLAN Demux Interfaces over an Aggregated Ethernet Underlying Interface with DHCP Local Server
- Example: Configuring IPv4 Dynamic Stacked VLAN Demux Interfaces over an Aggregated Ethernet Underlying Interface with DHCP Local Server
- play_arrow Using Dynamic Profiles to Apply Services to DHCP Subscriber Interfaces
- play_arrow Configuring DHCP IP Demux and PPPoE Demux Interfaces Over the Same VLAN
- play_arrow Providing Security for DHCP Interfaces Using MAC Address Validation
- play_arrow RADIUS-Sourced Weights for Targeted Distribution
- play_arrow Verifying Configuration and Status of Dynamic Subscribers
-
- play_arrow Configuring PPPoE Subscriber Interfaces
- play_arrow Configuring Dynamic PPPoE Subscriber Interfaces
- Subscriber Interfaces and PPPoE Overview
- Dynamic PPPoE Subscriber Interfaces over Static Underlying Interfaces Overview
- Configuring Dynamic PPPoE Subscriber Interfaces
- Configuring a PPPoE Dynamic Profile
- Configuring an Underlying Interface for Dynamic PPPoE Subscriber Interfaces
- Configuring the PPPoE Family for an Underlying Interface
- Ignoring DSL Forum VSAs from Directly Connected Devices
- Example: Configuring a Dynamic PPPoE Subscriber Interface on a Static Gigabit Ethernet VLAN Interface
- play_arrow Configuring PPPoE Subscriber Interfaces over Aggregated Ethernet Examples
- Example: Configuring a Static PPPoE Subscriber Interface on a Static Underlying VLAN Demux Interface over Aggregated Ethernet
- Example: Configuring a Dynamic PPPoE Subscriber Interface on a Static Underlying VLAN Demux Interface over Aggregated Ethernet
- Example: Configuring a Dynamic PPPoE Subscriber Interface on a Dynamic Underlying VLAN Demux Interface over Aggregated Ethernet
- play_arrow Configuring PPPoE Session Limits
- play_arrow Configuring PPPoE Subscriber Session Lockout
- play_arrow Configuring MTU and MRU for PPP Subscribers
- play_arrow Configuring PPPoE Service Name Tables
- Understanding PPPoE Service Name Tables
- Evaluation Order for Matching Client Information in PPPoE Service Name Tables
- Benefits of Configuring PPPoE Service Name Tables
- Creating a Service Name Table
- Configuring PPPoE Service Name Tables
- Assigning a Service Name Table to a PPPoE Underlying Interface
- Configuring the Action Taken When the Client Request Includes an Empty Service Name Tag
- Configuring the Action Taken for the Any Service
- Assigning a Service to a Service Name Table and Configuring the Action Taken When the Client Request Includes a Non-zero Service Name Tag
- Assigning an ACI/ARI Pair to a Service Name and Configuring the Action Taken When the Client Request Includes ACI/ARI Information
- Assigning a Dynamic Profile and Routing Instance to a Service Name or ACI/ARI Pair for Dynamic PPPoE Interface Creation
- Limiting the Number of Active PPPoE Sessions Established with a Specified Service Name
- Reserving a Static PPPoE Interface for Exclusive Use by a PPPoE Client
- Example: Configuring a PPPoE Service Name Table
- Example: Configuring a PPPoE Service Name Table for Dynamic Subscriber Interface Creation
- Troubleshooting PPPoE Service Name Tables
- play_arrow Changing the Behavior of PPPoE Control Packets
- play_arrow Monitoring and Managing Dynamic PPPoE for Subscriber Access
-
- play_arrow Configuring ATM for Subscriber Access
- play_arrow Configuring ATM to Deliver Subscriber-Based Services
- play_arrow Configuring PPPoE Subscriber Interfaces Over ATM
- play_arrow Configuring ATM Virtual Path Shaping on ATM MICs with SFP
- play_arrow Configuring Static Subscriber Interfaces over ATM
- play_arrow Verifying and Managing ATM Configurations
-
- play_arrow Troubleshooting
- play_arrow Contacting Juniper Networks Technical Support
- play_arrow Knowledge Base
-
- play_arrow Configuration Statements and Operational Commands
Understanding Fragmented Packet Queuing
Fragmented Multilink PPP (MLPPP) packets have a multilink header containing a multilink sequence number. The sequence numbers on these fragments must be preserved so that the remote device receiving these fragments can correctly reassemble them into a complete packet. To accommodate this requirement, Junos OS queues all packets on member links of a multilink bundle with a MLPPP header into a single queue (q0) by default.
Traffic flows of a forwarding class that has MLPPP fragmentation configured are distributed from the inline services
sibundle interface queues to the member link queues (queue 0) following a round-robin method.Traffic flows of a forwarding class without MLPPP fragmentation are distributed from the
sibundle interface queues to the member link queues based on a hashing algorithm computed from the destination address, source address, and IP protocol of the packet.If the IP payload contains TCP or UDP traffic, the hashing algorithm also includes the source and destination ports. As a result, all traffic belonging to one traffic flow is queued to one member link.
Figure 1 shows how traffic is queued on an MLPPP multilink bundle and its member links. Packet flows in the figure use the notation Px,Fx; for example, P1,F1 represents Packet 1, Fragment 1.
There are four queues.
Forwarding classes be, af, and nc are mapped to queues q0, q1, and q3, respectively, on the multilink bundle. These are fragmented.
Forwarding class ef contains voice traffic, and is mapped to q2 and is not fragmented.
Interface
si-1/0/0.1is the bundle, andpp0.1andpp0.2are the member links for that bundle.
Queuing on member links proceeds as follows:
The packet fragments of forwarding classes be, af, and nc on the multilink bundle are mapped to q0 on Member Links 1 and 2. These packets are distributed from the
siqueues to the member links using a round-robin method.The packets of forwarding class ef (voice) from the multilink bundle are mapped to q2 on the member links. This forwarding class is not fragmented. The packets are distributed from the
siqueues to the member links based on a hashing algorithm.The network control packets from the multilink bundle are mapped to q0 on the member links. The bundle network control traffic is queued with the data flows on the member link. However, q3 on the member links transmits network control packets that exchange protocol information related to member links, such as packets exchanging hello messages on member links.
This section contains the following topics:
Queuing of Fragmented Packets to Member Links
On a multilink bundle, packet fragments from all forwarding classes with fragmentation enabled are transmitted to q0 on member links. On the q0 queues of member links, packets are queued using a round-robin method to enable per-fragment load balancing.
Figure 2 shows how fragmented packet queuing is performed on the member links. Packet flows in the figure use the notation Px,Fx; for example, P1,F1 represents Packet 1, Fragment 1.
Packet fragments from the multilink bundle are queued to member links one by one using a round-robin method:
Packet P1,F1 from q0 on the multilink bundle is queued to q0 on Member Link 1.
Packet P1,F2 from q0 on the multilink bundle is queued to q0 on Member Link 2.
Packet P1,F3 from q0 on the multilink bundle is queued to q0 on Member Link 1.
Packet P2,F1 from q1 on the multilink bundle is queued to q0 on Member Link 2, and so on.
Packets that are part of the fragmented forwarding class, but are not fragmented, follow the same procedure.
After exiting the si interface, Microcode
adds a header of approximately 40 bytes to the MLPPP packets. When
configuring the class-of-service shaping, you may need to adjust bytes
to account for this.
Queuing of LFI Packets to Member Links
On a multilink bundle, all non-MLPPP encapsulated traffic [link fragmenting and interleaving (LFI) traffic] from the multilink bundle are queued to the queue as defined by the forwarding class of that packet.
Figure 3 shows how LFI packet queuing is performed on the member links.
The packets are distributed from the si interface to the member links based on a hashing algorithm computed
from the source address, destination address, and IP protocol of the
packet.
If the IP payload contains TCP or UDP traffic, the hashing algorithm also includes the source and destination ports. As a result, all traffic belonging to one traffic flow is queued to one member link.
