ON THIS PAGE
Example: Configuring a Static Subscriber Interface for IP Access over Ethernet over ATM
This example illustrates a bridged IP-over-Ethernet-over-ATM (IPoE-over-ATM) configuration that creates a subscriber interface for IPv4 access 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 IPoE-over-ATM configuration enables you to provide access to subscribers on static IPv4 or IPv6 interfaces over an underlying ATM interface on an ATM network using ATM Adaptation Layer 5 (AAL5) permanent virtual circuits (PVCs).
IPoE-over-ATM configurations require static configuration of the IP interface, ATM interface, CoS attributes, and firewall fiters. Dynamic configuration is not supported.
To configure bridged IPoE-over-ATM subscriber access, you must
configure Ethernet-over-ATM logical link control (LLC) encapsulation
on the ATM underlying interface by including the encapsulation
ether-over-atm-llc statement at the [edit interfaces interface-name unit logical-unit-number] hierarchy level.
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 IPoE-over-ATM configurations, the subscriber interfaces are
associated with IPv4 or IPv6 addresses that are mapped to media access
control (MAC) addresses. To statically configure Address Resolution
Protocol (ARP) table entries that map IP address to MAC addresses,
use the arp statement at the [edit interfaces interface-name unit logical-unit-number family inet address address] hierarchy
level. In this example, the IPv4 address 10.0.50.2, configured with
the set arp 10.0.50.2 mac 00:00:5e:00:53:ff publish statement
at the [edit interfaces at-1/0/2 unit 0 family inet address 10.0.50.254/24] hierarchy level, represents the subscriber interface.
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/2.
Configure Ethernet-over-ATM LLC encapsulation, VCI 0.39 (VCI 39 on VPI 0), and the following IPv4 (
inet) protocol family characteristics on logical interface at-1/0/2.0 :IPv4 subscriber interface address 10.0.50.254/24
Static Address Resolution Protocol (ARP) table entries that provide explicit mappings between IP addresses and MAC addresses
IP source address validation (
rpf-check)Standard input (biz-customer-in-filter) and output (biz-customer-out-filter) firewall filters
Configure static access route 200.10.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/2 atm-options vpi 0 # # Logical Unit 0 set interfaces at-1/0/2 unit 0 encapsulation ether-over-atm-llc set interfaces at-1/0/2 unit 0 vci 0.39 set interfaces at-1/0/2 unit 0 family inet rpf-check set interfaces at-1/0/2 unit 0 family inet filter input biz-customer-in-filter set interfaces at-1/0/2 unit 0 family inet filter output biz-customer-out-filter set interfaces at-1/0/2 unit 0 family inet address 10.0.50.254/24 arp 10.0.50.2 mac 00:00:5e:00:53:ff set interfaces at-1/0/2 unit 0 family inet address 10.0.50.254/24 arp 10.0.50.2 publish # # Routing Properties set routing-options access route 10.200.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.
[edit interfaces at-1/0/2] user@host# edit atm-options
Configure one or more VPIs on the physical interface.
[edit interfaces at-1/0/2 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/2 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/2
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 Ethernet-over-ATM LLC encapsulation on the logical interface.
[edit interfaces at-1/0/2 unit 0] user@host# set encapsulation ether-over-atm-llc
Configure the VCI for the logical interface.
[edit interfaces at-1/0/2 unit 0] user@host# set vci 0.39
Configure the IPv4 (
inet) protocol family and address.[edit interfaces at-1/0/2 unit 0] user@host# set family inet address 10.0.50.254/24
Specify that you want to configure static ARP table entries to map between IP addresses and MAC addresses.
[edit interfaces at-1/0/2 unit 0 family inet] user@host# edit family inet address 10.0.50.254/24
Configure IP address 10.0.50.2, which maps to the MAC address, and MAC address 00:00:5e:00:53:ff, which maps to the IP address. Include the
publishoption to specify that the router reply to ARP requests for the specified IP address.[edit interfaces at-1/0/2 unit 0 family inet address 10.0.50.254/24] user@host# set arp 10.0.50.2 mac 00:00:5e:00:53:ff publish user@host# up
Enable IP source address validation, which checks whether traffic is arriving at the router on an expected path.
[edit interfaces at-1/0/2 unit 0 family inet] user@host# set rpf-check
Apply the previously defined standard firewall filters to the logical interface.
[edit interfaces at-1/0/2 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/2.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/2.0
encapsulation ether-over-atm-llc;
vci 0.39;
family inet {
rpf-check;
filter {
input biz-customer-in-filter;
output biz-customer-out-filter;
}
address 10.0.50.254/24 {
arp 10.0.50.2 mac 00:00:5e:00:53:ff publish;
}
}
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.
[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.
[edit routing-options] user@host# set access route 10.200.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 10.200.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 IPoE-over-ATM 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/2 physical interface is properly configured for use with ATM PVCs.
Action
From operational mode, issue the show interfaces
at-1/0/2 command.
For brevity, this show command output includes only
the configuration that is relevant to the at-1/0/2 physical interface.
Any other configuration on the system has been replaced with ellipses
(...).
user@host> show interfaces at-1/0/2
Physical interface: at-1/0/2, Enabled, Physical link is Down
Interface index: 175, SNMP ifIndex: 594
Link-level type: ATM-PVC, MTU: 2048, Clocking: Internal, SDH 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:97
Last flapped : 2012-09-06 12:11:39 PDT (05:45:45 ago)
Input rate : 0 bps (0 pps)
Output rate : 0 bps (0 pps)
SDH alarms : LOL, LOS
SDH defects : LOL, LOS, LOP, BERR-SF, HP-FERF
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/2. 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 IPoE-over-ATM access.
Action
From operational mode, issue the show interfaces
at-1/0/2.0 command.
user@host> show interfaces at-1/0/2.0
Logical interface at-1/0/2.0 (Index 336) (SNMP ifIndex 1983)
Flags: Device-Down Point-To-Multipoint SNMP-Traps 0x4000 Encapsulation: Ether-over-ATM-LLC
Input packets : 0
Output packets: 0
Protocol inet, MTU: 2016
Flags: Sendbcast-pkt-to-re, uRPF
Addresses, Flags: Dest-route-down Is-Preferred Is-Primary
Destination: 10.0.50/24, Local: 10.0.50.254, Broadcast: 10.0.50.255
VCI 0.39
Flags: Active, Multicast
Total down time: 0 sec, Last down: Never
Input packets : 0
Output packets: 0Meaning
Ether-over-ATM-LLC in the Encapsulation
field indicates that logical interface at-1/0/2.0 is properly configured
for Ethernet-over-ATM encapsulation with LLC. Protocol inet indicates that the IPv4 protocol family has been properly configured
on the logical interface. The destination address 10.0.50/24 identifies
the network in which the subscriber interface (10.0.50.2) resides. The Active flag for VCI 0.39 indicates that virtual circuit
identifier (VCI) 39 on VPI 0 is up and operational.