[Contents] [Prev] [Next] [Index] [Report an Error]

Configuring ATM-over-ADSL Interfaces

J4300 and J6300 Services Routers with asymmetrical DSL (ADSL) Annex A or Annex B PIMs can use an ATM interface to send network traffic through a point-to-point connection to a DSLAM. ATM-over-ADSL interfaces are not supported on J2300 Services Routers.

NOTE: You can configure J4300 and J6300 Services Routers with ADSL PIMs for connections through DSL only, not for direct ATM connections.

You configure the underlying ADSL as an ATM interface with an interface name of at-pim/0/port. Multiple encapsulation types are supported on both the physical and logical ATM-over-ADSL interface.

You can configure Point-to-Point Protocol over Ethernet (PPPoE) over ATM to connect through DSL lines. For PPPoE on an ATM-over-ADSL interface, you must configure encapsulation on both the physical and logical interfaces. To configure encapsulation on an ATM-over-ADSL physical interface, use Ethernet over ATM encapsulation. To configure encapsulation on an ATM-over-ADSL logical interface, use the PPPoE over AAL5 LLC encapsulation. LLC encapsulation allows a single ATM virtual connection to transport multiple protocols.

When you configure a point-to-point encapsulation such as PPP on a physical interface, the physical interface can have only one logical interface (only one unit statement) associated with it.

For more information about configuring PPPoE, see Configuring Point-to-Point Protocol over Ethernet.

To configure physical ATM interfaces for ADSL, include the vpi 0 statement at the [edit interfaces at-pim/0/port atm-options] hierarchy level, the operating-mode statement at the [edit interfaces at-pim/0/port dsl-options] hierarchy level, and the encapsulation statement at the [edit interfaces at-pim/0/port] hierarchy level:

    [edit interfaces at-pim/0/port]

        atm-options {

            vpi 0;

        dsl-options;

            operating-mode (adsl2plus | ansi-dmt | auto | etsi | itu-annexb-ur2 |

                itu-annexb-non-ir2 | itu-dmt | itu-dmt-bis);

        }

        encapsulation (atm-pvc | ethernet-over-atm);

        }

    }

Configure logical interface properties by including the encapsulation statement, family statement, and vci statement:

    unit logical-unit-number {

        encapsulation (atm-vc-mux | atm-nlpd | atm-cisco-nlpd | atm-snap |

            atm-ppp-vc-mux | atm-ppp-llc | ether-over-atm-llc | ppp-over-ether-over-atm-llc);

        family inet{

        vci vpi-identifier.vci-identifier;

        }

    }

You can include these statements at the following hierarchy levels:

To configure ATM-over-ADSL network interfaces for the J-series Services Router:

  1. Set the ATM virtual path identifier (VPI) to 0 (zero) by including the vpi 0 statement at the [edit interfaces interface-name atm-options] hierarchy level:
    2. [edit interfaces at-pim/0/port atm-options]

    vpi 0;
  2. Configure the ADSL operating mode on the physical ATM interface by including the operating-mode statement at the [edit interfaces interface-name dsl-options] hierarchy level:
    3. [edit interfaces at-pim/0/port dsl-options]

    operating-mode mode;

By default, the mode is auto, which means the ADSL line autonegotiates the setting to match the setting of the DSLAM located at the central office.

You can configure the operating mode to be one of the following for Annex A PIMS:

You can configure the operating mode to be one of the following for Annex B PIMS:

  1. Configure the physical interface encapsulation type by including the encapsulation statement at the [edit interfaces at-pim/0/port ] hierarchy level:
    2. [edit interfaces at-pim/0/port]

    encapsulation type;

ATM-over-ADSL interfaces support the following encapsulations on the physical interface:

  1. Configure the logical interface encapsulation type by including the encapsulation statement:
    2. encapsulation type;

You can include this statement at the following hierarchy levels:

ATM-over-ADSL interfaces support the following encapsulations on the logical interface:

  1. Configure the family protocol type by including the family statement:
    2. family family;

You can include this statement at the following hierarchy levels:

  1. Configure the virtual channel identifier (VCI) type and value by including the vci statement:
    2. vci vpi-identifier.vci-identifier;

You can include this statement at the following hierarchy levels:

[Contents] [Prev] [Next] [Index] [Report an Error]