- 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 MLPPP for Subscriber Access
- play_arrow MLPPP Support for LNS and PPPoE Subscribers Overview
- MLPPP Overview
- MLPPP Support for LNS and PPPoE Subscribers Overview
- Supported Features for MLPPP LNS and PPPoE Subscribers on the MX Series
- Mixed Mode Support for MLPPP and PPP Subscribers Overview
- Understanding DVLAN (Single/Dual tag) for Subscriber Services Scaling (Junos Evolved for ACX7100-48L Devices)
- play_arrow Configuring MLPPP Link Fragmentation and Interleaving
- play_arrow Configuring Inline Service Interfaces for LNS and PPPoE Subscribers
- play_arrow Configuring L2TP Access Client for MLPPP Subscribers
- play_arrow Configuring Static MLPPP Subscribers for MX Series
- play_arrow Configuring Dynamic MLPPP Subscribers for MX Series
- play_arrow Configuring Dynamic PPP Subscriber Services
- Dynamic PPP Subscriber Services for Static MLPPP Interfaces Overview
- Hardware Requirements for PPP Subscriber Services on Non-Ethernet Interfaces
- Configuring PPP Subscriber Services for MLPPP Bundles
- Enabling PPP Subscriber Services for Static Non-Ethernet Interfaces
- Attaching Dynamic Profiles to MLPPP Bundles
- Example: Minimum MLPPP Dynamic Profile
- Example: Configuring CoS on Static LSQ MLPPP Bundle Interfaces
- play_arrow Monitoring and Managing MLPPP for Subscriber Access
-
- play_arrow Troubleshooting
- play_arrow Contacting Juniper Networks Technical Support
- play_arrow Knowledge Base
-
- play_arrow Configuration Statements and Operational Commands
ON THIS PAGE
Example: Configuring a Static Subscriber Interface for IP Access over ATM
This example illustrates a routed IP-over-ATM (IPoA) configuration that creates a subscriber interface for a static IPv4 interface over a static ATM interface on an MX Series router. The router must have Module Port Concentrator/Modular Interface Card (MPC/MIC) interfaces that use an ATM MIC with small form-factor pluggable transceiver (SFP).
Requirements
This example uses the following software and hardware components:
MX Series 5G Universal Routing Platform
ATM MIC with SFP (Model Number MIC-3D-8OC3-2OC12-ATM) and compatible MPC1 or MPC2
Before you begin:
Make sure the MX Series router you are using has an ATM MIC with SFP installed and operational.
For information about compatible MPCs for the ATM MIC with SFP, see the MX Series Interface Module Reference.
For information about installing MPCs and MICs in an MX Series router, see the Hardware Guide for your MX Series router model.
Make sure you understand how to configure and use static ATM interfaces.
Define the static standard firewall filters (biz-customer-in-filter and biz-customer-out-filter) referenced in the configuration.
For information about creating standard firewall filters, see Guidelines for Configuring Firewall Filters.
For information about applying a firewall filter to an interface, see Guidelines for Applying Standard Firewall Filters.
Overview
By using the ATM MIC with SFP and a supported MPC, you can configure the MX Series router to support subscriber access for a statically created IPv4 or IPv6 interface over a static ATM underlying interface. An IPoA configuration enables you to provide access to subscribers on static IPv4 or IPv6 interfaces over an ATM network using ATM Adaptation Layer 5 (AAL5) permanent virtual circuits (PVCs).
IPoA configurations require static configuration of the IPv4 interface, IPv6 interface, CoS attributes, and firewall fiters. Dynamic configuration is not supported.
To configure IPoA subscriber access, configure the correct encapsulation
type: atm-snap for IPoA encapsulation with logical link
control (LLC), or atm-vc-mux for IPoA encapsulation with
virtual circuit (VC) multiplexing. This example configures atm-vc-mux as the encapsulation type on the ATM logical interface.
To provision the ATM AAL5 PVCs for access over the ATM network, you must also configure the virtual path identifiers (VPIs) on the ATM physical interface, and one or more virtual circuit identifiers (VCIs) for each VPI.
In IPoA configurations, the subscriber interfaces correspond
to the IPv4 or IPv6 addresses that are on the same network as the
statically configured ATM underlying interface. In this IPoA example,
the IPv4 address 10.0.0.2 represents the subscriber interface. You
can configure the destination address with the set address 10.0.0.254/32
destination 10.0.0.2 statement at the [edit interfaces
at-1/0/3 unit 0 family inet] hierarchy level.
This example includes the following basic steps to statically configure a single IPv4 subscriber interface over an ATM underlying interface:
Configure VPI 0 on ATM physical interface at-1/0/3.
Configure ATM VC multiplex encapsulation, VCI 0.39 (VCI 39 on VPI 0), and the following IPv4 (
inet) protocol family characteristics on logical interface at-1/0/3.0 :IP source address validation (
rpf-check)Standard input (biz-customer-in-filter) and output (biz-customer-out-filter) firewall filters
Interface address 10.0.0.254/32 with destination address 10.0.0.2
Configure static access route 10.200.10.0/24 with qualified-next-hop address at-1/0/0.0.
Configuration
To configure a static IPv4 subscriber interface over a static ATM underlying interface, perform these tasks:
- CLI Quick Configuration
- Configuring the ATM Physical Interface
- Configuring the Static IPv4 Subscriber Interface on Logical Unit 0
- Configuring Routing Properties
CLI Quick Configuration
To quickly configure this example, copy the
following commands, paste them in a text file, remove any line breaks,
change any details necessary to match your network configuration,
and then copy and paste the commands into the CLI at the [edit] hierarchy level.
# ATM Physical Interface set interfaces at-1/0/3 atm-options vpi 0 # # Logical Unit 0 set interfaces at-1/0/3 unit 0 encapsulation atm-vc-mux set interfaces at-1/0/3 unit 0 vci 0.39 set interfaces at-1/0/3 unit 0 family inet rpf-check set interfaces at-1/0/3 unit 0 family inet filter input biz-customer-in-filter set interfaces at-1/0/3 unit 0 family inet filter output biz-customer-out-filter set interfaces at-1/0/3 unit 0 family inet address 10.0.0.254/32 destination 10.0.0.2 # # Routing Properties set routing-options access route 200.10.10.0/24 qualified-next-hop at-1/0/0.0
Configuring the ATM Physical Interface
Step-by-Step Procedure
To configure the ATM physical interface:
Specify that you want to configure ATM-specific options on the physical interface.
content_copy zoom_out_map[edit interfaces at-1/0/3] user@host# edit atm-options
Configure one or more VPIs on the physical interface.
content_copy zoom_out_map[edit interfaces at-1/0/3 atm-options] user@host# set vpi 0
Results
From the [edit] hierarchy level in configuration
mode, confirm the results of the ATM physical interface configuration
by issuing the show interfaces at-1/0/3 command. If the
output does not display the intended configuration, repeat the instructions
in this example to correct it.
[edit]
user@host# show interfaces at-1/0/3
atm-options {
vpi 0;
}
If you are done configuring the ATM physical interface, enter commit from configuration mode.
Configuring the Static IPv4 Subscriber Interface on Logical Unit 0
Step-by-Step Procedure
To configure the static IPv4 subscriber interface on logical unit 0:
Configure ATM VC multiplex encapsulation on the logical interface.
content_copy zoom_out_map[edit interfaces at-1/0/3 unit 0] user@host# set encapsulation atm-vc-mux
Configure the VCI for the logical interface.
content_copy zoom_out_map[edit interfaces at-1/0/3 unit 0] user@host# set vci 0.39
Configure the IPv4 (
inet) protocol family, IPv4 address, and remote (destination) address of the connection.content_copy zoom_out_map[edit interfaces at-1/0/3 unit 0] user@host# set family inet address 10.0.0.254/32 destination 10.0.0.2
Specify that you want to configure additional attributes for the IPv4 protocol family.
content_copy zoom_out_map[edit interfaces at-1/0/3 unit 0] user@host# edit family inet
Enable IP source address validation, which checks whether traffic is arriving at the router on an expected path.
content_copy zoom_out_map[edit interfaces at-1/0/3 unit 0 family inet] user@host# set rpf-check
Apply the previously defined standard firewall filters to the logical interface.
content_copy zoom_out_map[edit interfaces at-1/0/3 unit 0 family inet] user@host# set filter input biz-customer-in-filter user@host# set filter output biz-customer-out-filter
Results
From the [edit] hierarchy level in configuration
mode, confirm the results of the static subscriber interface configuration
on logical unit 0 by issuing the show interfaces at-1/0/3.0 command. If the output does not display the intended configuration,
repeat the instructions in this example to correct it.
[edit]
user@host# show interfaces at-1/0/3.0
encapsulation atm-vc-mux;
vci 0.39;
family inet {
rpf-check;
filter {
input biz-customer-in-filter;
output biz-customer-out-filter;
}
address 10.0.0.254/32 {
destination 10.0.0.2;
}
}
If you are done configuring the static subscriber interface
on logical unit 0, enter commit from configuration
mode.
Configuring Routing Properties
Step-by-Step Procedure
To configure static routing properties:
Specify that you want to configure protocol-independent routing properties.
content_copy zoom_out_map[edit] user@host# edit routing-options
Configure a static access route for routing downstream traffic from the router, and a qualified-next-hop address for routing upstream traffic to the router.
content_copy zoom_out_map[edit routing-options] user@host# set access route 200.10.10.0/24 qualified-next-hop at-1/0/0.0
Results
From the [edit] hierarchy level in configuration
mode, confirm the results of the static routing properties configuration
by issuing the show routing-options command. If the output
does not display the intended configuration, repeat the instructions
in this example to correct it.
[edit]
user@host# show routing-options
access {
route 200.10.10.0/24 {
qualified-next-hop at-1/0/0.0;
}
}
If you are done configuring the static routing properties, enter commit from configuration mode.
Verification
To confirm that the IPoA configuration is working properly, perform the following tasks:
- Verifying the ATM Physical Interface Configuration
- Verifying the Static Subscriber Interface Configuration on Logical Unit 0
Verifying the ATM Physical Interface Configuration
Purpose
Verify that the at-1/0/3 physical interface is properly configured for use with ATM PVCs.
Action
From operational mode, issue the show interfaces
at-1/0/3 command.
For brevity, this show command output includes only
the configuration that is relevant to the at-1/0/3 physical interface.
Any other configuration on the system has been replaced with ellipses
(...).
user@host> show interfaces at-1/0/3
Physical interface: at-1/0/3, Enabled, Physical link is Down
Interface index: 168, SNMP ifIndex: 595
Link-level type: ATM-PVC, MTU: 2048, Clocking: Internal, SONET mode, Speed: OC3, Loopback: None,
Payload scrambler: Enabled
Device flags : Present Running Down
Link flags : None
CoS queues : 8 supported, 8 maximum usable queues
Schedulers : 0
Current address: 00:00:5e:00:53:18
Last flapped : 2012-08-28 07:14:48 PDT (08:28:47 ago)
Input rate : 0 bps (0 pps)
Output rate : 0 bps (0 pps)
SONET alarms : LOL, LOS
SONET defects : LOL, LOS, LOP, BERR-SF, RDI-P
VPI 0
Flags: Active
Total down time: 0 sec, Last down: Never
Traffic statistics:
Input packets: 0
Output packets: 0
...Meaning
ATM-PVC in the Link-level Type field indicates
that encapsulation for ATM permanent virtual circuits is being used
on ATM physical interface at-1/0/3. The Active flag for
VPI 0 indicates that the virtual path is up and operational.
Verifying the Static Subscriber Interface Configuration on Logical Unit 0
Purpose
Verify that the static subscriber interface on logical unit 0 is properly configured for IPv4 access over ATM.
Action
From operational mode, issue the show interfaces
at-1/0/3.0 command.
user@host> show interfaces at-1/0/3.0
Logical interface at-1/0/3.0 (Index 341) (SNMP ifIndex 1984)
Flags: Device-Down Point-To-Point SNMP-Traps 0x4000 Encapsulation: ATM-VCMUX
Input packets : 0
Output packets: 0
Protocol inet, MTU: 2040
Flags: Sendbcast-pkt-to-re, uRPF
Addresses, Flags: Dest-route-down Is-Preferred Is-Primary
Destination: 10.0.0.2, Local: 10.0.0.254
VCI 0.39
Flags: Active
Total down time: 0 sec, Last down: Never
Input packets : 0
Output packets: 0
Meaning
ATM-VCMUX in the Encapsulation field indicates
that the logical interface at-1/0/3.0 is properly configured for IPoA
encapsulation with VC multiplexing. Protocol inet indicates
that the IPv4 protocol family has been properly configured on the
logical interface. The local address 10.0.0.254 is the IPv4 address
of the logical interface. The destination address 10.0.0.2, which
is in the same network as the local address, is the IPv4 address of
the remote side of the connection and represents the static subscriber
interface. The Active flag for VCI 0.39 indicates
that virtual circuit identifier (VCI) 39 on VPI 0 is up
and operational.
