Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

Example: Configuring a Static Subscriber Interface for IP Access over ATM

Requirements

• Junos OS Release 12.2
• MX Series 3D Universal Edge Router
• ATM MIC with SFP (Model Number MIC-3D-8OC3-2OC12-ATM) and compatible MPC1 or MPC2

1. 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 3D Universal Edge Routers Line Card Guide .
   • For information about installing MPCs and MICs in an MX Series router, see the Hardware Guide for your MX Series router model.
2. Make sure you understand how to configure and use static ATM interfaces.

   See ATM Interfaces Overview.

3. 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 Standard 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).

Note: IPoA configurations on MX Series routers require static configuration of the IPv4 interface, IPv6 interface, CoS attributes, and firewall fiters. Dynamic configuration is not supported.

To configure IPoA subscriber access on MX Series routers, you must 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 1.0.0.2 represents the subscriber interface. You can configure the destination address with the set address 1.0.0.2.254/32 destination 1.0.0.2 statement at the [edit interfaces at-1/0/3 unit 0 family inet] hierarchy level.

1. Configure VPI 0 on ATM physical interface at-1/0/3.
2. 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 1.0.0.254/32 with destination address 1.0.0.2
3. 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:

• 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.

Configuring the ATM Physical Interface

Step-by-Step Procedure

1. Specify that you want to configure ATM-specific options on the physical interface.
   [edit interfaces at-1/0/3]user@host# edit atm-options
2. Configure one or more VPIs on the physical interface.
   [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.

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

1. Configure ATM VC multiplex encapsulation on the logical interface.
   [edit interfaces at-1/0/3 unit 0]user@host# set encapsulation atm-vc-mux
2. Configure the VCI for the logical interface.
   [edit interfaces at-1/0/3 unit 0]user@host# set vci 0.39
3. Configure the IPv4 (inet) protocol family, IPv4 address, and remote (destination) address of the connection.
   [edit interfaces at-1/0/3 unit 0]user@host# set family inet address 1.0.0.254/32 destination 1.0.0.2
4. Specify that you want to configure additional attributes for the IPv4 protocol family.
   [edit interfaces at-1/0/3 unit 0]user@host# edit family inet
5. Enable IP source address validation, which checks whether traffic is arriving at the router on an expected path.
   [edit interfaces at-1/0/3 unit 0 family inet]user@host# set rpf-check
6. Apply the previously defined standard firewall filters to the logical interface.
   [edit interfaces at-1/0/3 unit 0 family inet]user@host# set filter input biz-customer-in-filteruser@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.

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

1. Specify that you want to configure protocol-independent routing properties.
   [edit]user@host# edit routing-options
2. 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 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.

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 (...).

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:1f:12:bc:4a:98
  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.

  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: 1.0.0.2, Local: 1.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 1.0.0.254 is the IPv4 address of the logical interface. The destination address 1.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.