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

Adding an ATM-for-ADSL Network Interface with a Configuration Editor

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

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-fpc/0/port. Multiple encapsulation types are supported on both the physical and logical ATM-for-ADSL interface.

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

  1. Navigate to the top of the interfaces configuration hierarchy in either the J-Web or CLI configuration editor.
  2. Perform the configuration tasks described in Table 25.
  3. When you are finished configuring the interface, click Commit.
  4. Go on to one of the following procedures:

Table 25: Adding an ATM-for-ADSL Network Interface

Task

J-Web Configuration Editor

CLI Configuration Editor

Navigate to the Interfaces level in the configuration hierarchy.
  1. In the configuration editor hierarchy, select Configuration>View and Edit>Edit Configuration.
  2. Next to Interfaces, click Edit.

From the top of the configuration hierarchy, create and name the interface:

edit interfaces at-2/0/0

Create the new interface—for example, at-2/0/0.
  1. Next to Interface, click Add new entry.
  2. In the Interface name box, type the name of the new interface.
  3. Click OK.
Configuring Physical Properties

Configure ATM options for the interface.

  1. Next to Atm options, click Configure.
  2. Next to Vpi, click Add new entry.
  3. In the Vpi number box, enter a value between 0 and 255 in the box—for example, 25.
  4. Click OK.

Enter

set atm-options vpi 25

Configure the ADSL operating mode.

Annex A and Annex B support the following operating modes:

Annex A supports an additional operating mode:

Annex B supports the following operating modes:

  • auto—Configures the ADSL interface to autonegotiate settings with the DSLAM located at the central office. For Annex A, the ADSL interface trains in either ANSI T1.413 Issue II mode or ITU G.992.1 mode. For Annex B, the ADSL interface trains in ITU G.992.1 mode.
  • itu-dmt—Configures the ADSL interface to train in ITU G.992.1 mode.
  • ansi-dmt—Configures the ADSL interface to train in the ANSI T1.413 Issue II mode.
  • etsi—Configures the ADSL line to train in the ETSI TS 101 388 V1.3.1 mode.
  • itu-annexb-ur2—Configures the ADSL line to train in the G.992.1 Deutsche Telekom UR-2 mode.
  • itu-annexb-non-ur2—Configures the ADSL line to train in the G.992.1 Non-UR-2 mode.
  1. Next to Dsl options, click Configure.
  2. From the Operating Mode drop-down list, select the type of DSL operating mode—for example, auto.

Enter

set dsl-options operating-mode auto

Configure the encapsulation type.

  • atm-pvc—ATM permanent virtual circuits.

    For PPP over ATM-for-ADSL (PPPoA) interfaces, use this type of encapsulation.

  • ether-over-atm—Ethernet over ATM encapsulation.

    For PPP over Ethernet (PPPoE) over ATM for ADSL interfaces that carry IPv4 traffic, use this type of encapsulation.

  1. From the Encapsulation drop-down list, select the encapsulation type—for example, ether-over-atm.
  2. Click OK to save the configuration so far.

Enter

set encapsulation ether-over-atm

Configuring Logical Properties

Add the logical interface.

  1. Scroll down the page to Unit, and click Add new entry.
  2. In the Interface unit number box, type a value from 0 to 16385—for example, 3.
  3. Enter values in the fields required by your network.

Enter

set unit 3

Configure encapsulation for the logical unit.

The ATM-for-ADSL interface supports the following encapsulations on the logical interface:

  • atm-vc-mux–Use ATM VC multiplex encapsulation. You can only configure the inet family when you use this type of encapsulation.
  • atm-nlpid–Use ATM network layer protocol identifier (NLPID) encapsulation. You can only configure the inet family when you use this type of encapsulation.
  • atm-cisco-nlpid–Use Cisco NLPID encapsulation. You can only configure the inet family when you use this type of encapsulation.
  • atm-snap–Use ATM SNAP encapsulation.
  • atm-ppp-vc-mux—Use PPP over ATM AAL5 multiplex encapsulation. (For PPPoA interfaces, use this type of encapsulation.)
  • atm-ppp-llc–Use PPP over ATM AAL5 LLC encapsulation. (For PPPoA interfaces, use this type of encapsulation.)
  • ether-over-atm-llc–For interfaces that carry IPv4 traffic, use Ethernet over LLC encapsulation. You cannot configure multipoint interfaces if you use this type of encapsulation.
  • ppp-over-ether-over-atm-llc–Use PPP over Ethernet over ATM LLC encapsulation. When you use this encapsulation type, you cannot configure the interface address. Instead you configure the interface address on the PPP interface.

From the Encapsulation drop-down list, select the type of encapsulation—for example, atm-nlpid.

Enter

set unit 3 encapsulation atm-nlpid

Add the Family protocol type.

Select the protocol type—for example, inet—and then click Configure.

Enter set unit 3 family inet

Commands vary depending on the protocol type.

Configure the virtual channel identifier (VCI) type and value.

  1. From the Vci type menu, select a value.
  2. Enter the ATM VCI value in the Vci field.
  3. Click OK.

Enter set unit 3 vci 10

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

[an error occurred while processing this directive]