Configuring ATM-over-ADSL Interfaces

J Series devices 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).

Note: You can configure J Series devices with ADSL PIMs for connections through ADSL only, not for direct ATM connections.

To configure Point-to-Point Protocol (PPP), see the Junos Network Interfaces Configuration Guide.

You configure the underlying ADSL interface 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.

This section contains the following topics:

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

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

To configure ATM-over-ADSL network interfaces for the J Series device with a configuration editor:

Navigate to the top of the interfaces configuration hierarchy.
Perform the configuration tasks described in Table 45.
If you are finished configuring the J Series device, commit the configuration.
Go on to one of the following procedures:
- To enable authentication on the interface, see Configuring CHAP on DSL Interfaces (Optional).
- To configure PPP over Ethernet (PPPoE) encapsulation on an Ethernet interface or on an ATM-over-ADSL interface, see Understanding Point-to-Point Protocol over Ethernet.
To check the configuration, see Verifying DSL Interface Configuration.

Table 45: Adding an ATM-over-ADSL Network Interface

Task	CLI Configuration Editor
Navigate to the Interfaces level in the configuration hierarchy.	From the [edit] hierarchy level, enter edit interfaces at-2/0/0
Create the new interface—for example, at-2/0/0.
Configuring Physical Properties
Configure ATM virtual path identifier (VPI) options for the interface—for example, at-2/0/0. ATM VPI—A number between 0 and 255—for example, 25. Operation, Maintenance, and Administration (OAM) F5 loopback cell thresholds (“liveness”) on ATM virtual circuits. The range is between 1 and 255, and the default is 5 cells. Down count—Number of consecutive OAM loopback cells an ATM virtual circuit must lose to be identified as unavailable—for example, 200. Up count—Number of consecutive OAM loopback cells an ATM virtual interface must receive to be identified as operational—for example, 200. OAM period—Interval, in seconds, at which OAM cells are transmitted on ATM virtual circuits—for example, 100. The range is between 1 and 900 seconds. Configure CBR for the Interface—for example, at-1/0/0. CBR – Range from 33000 through 1199920 CDVT – Range from 1 through 9999 Note: CDVT is not supported on J Series devices. Configure Vbr for the Interface—for example, at-1/0/0. MBS – Range from 33000 through 1199920 CDVT – Range from 1 through 9999 PCR – Range from 33000 through 1199920 SCR – Range from 33000 through 1199920	To configure the VPI value, enter set atm-options vpi 25 To configure OAM liveness values on a VPI, enter set atm-options vpi 25 oam-liveness up-count 200 down-count 200 To configure the OAM period, enter set atm-options vpi 25 oam-period 100 To configure the CBR value, enter set interfaces at-1/0/0 unit 0 shaping cbr To configure the VBR value, enter set interfaces at-1/0/0 unit 0 shaping vbr
Configure the type of DSL operating mode for the ATM-over-ADSL interface—for example auto. Annex A and Annex B support 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. Annex A supports the following operating modes: adsl2plus—Configures the ADSL interface to train in ITU G.992.5 mode. You can configure this mode only when it is supported on the DSLAM. itu-dmt-bis—Configures the ADSL interface to train in ITU G.992.3 mode. You can configure this mode only when it is supported on the DSLAM. ansi-dmt—Configures the ADSL interface to train in the ANSI T1.413 Issue II mode. Annex B supports the following operating modes: 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.	Enter set dsl-options operating-mode auto
Configure the encapsulation type—for example, ethernet-over-atm. atm-pvc—ATM permanent virtual circuits is the default encapsulation for ATM-over-ADSL interfaces. For PPP over ATM (PPPoA) over ADSL interfaces, use this type of encapsulation. ethernet-over-atm—Ethernet over ATM encapsulation. For PPP over Ethernet (PPPoE) over ATM-over-ADSL interfaces that carry IPv4 traffic, use this type of encapsulation.	Enter set encapsulation ethernet-over-atm
Configuring Logical Properties
Add the logical interface. Set a value from 0 and 16385—for example, 3. Add other values if required by your network.	Enter set unit 3
Configure encapsulation for the ATM-for-ADSL logical unit—for example, atm-nlpid. The following encapsulations are supported on the ATM-over-ADSL interfaces that use inet (IP) protocols only: atm-vc-mux–Use ATM virtual circuit multiplex encapsulation. atm-nlpid–Use ATM network layer protocol identifier (NLPID) encapsulation. atm-cisco-nlpid–Use Cisco NLPID 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. The following encapsulations are supported on the ATM-over-ADSL for PPP-over-ATM (PPPoA) interfaces only. atm-ppp-llc— AAL5 logical link control (LLC) encapsulation. atm-ppp-vc-mux—Use AAL5 multiplex encapsulation. Other encapsulation types supported on the ATM-over-ADSL interfaces: 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. atm-snap—Use ATM subnetwork attachment point (SNAP) encapsulation.	Enter set unit 3 encapsulation atm-nlpid
Configure Operation, Maintenance, and Administration (OAM) options for ATM virtual circuits: OAM F5 loopback cell thresholds (“liveness”) on ATM virtual circuits. The range is between 1 and 255, and the default is 5 cells. Down count—Number of consecutive OAM loopback cells an ATM virtual circuit must lose to be identified as unavailable—for example, 200. Up count—Number of consecutive OAM loopback cells an ATM virtual interface must receive to be identified as operational—for example, 200. OAM period—Interval, in seconds, at which OAM cells are transmitted on ATM virtual circuits—for example, 100. The range is between 1 and 900 seconds.	To configure OAM liveness values for an ATM virtual circuit, enter set unit 3 oam-liveness up-count 200 down-count 200 To configure the OAM period, enter set unit 3 oam-period 100
Add the Family protocol type—for example, inet.	Enter set unit 3 family inet Commands vary depending on the protocol type.
Configure ATM virtual channel identifier (VCI) options for the interface. ATM VCI type—vci. ATM VCI value—A number between 0 and 4089—for example, 35— with VCIs 0 through 31 reserved.	To configure the VCI value, enter set unit 3 vci 35

Task

CLI Configuration Editor

Navigate to the Interfaces level in the configuration hierarchy.

From the [edit] hierarchy level, enter

edit interfaces at-2/0/0

Create the new interface—for example, at-2/0/0.

Configuring Physical Properties

Configure ATM virtual path identifier (VPI) options for the interface—for example, at-2/0/0.

ATM VPI—A number between 0 and 255—for example, 25.
Operation, Maintenance, and Administration (OAM) F5 loopback cell thresholds (“liveness”) on ATM virtual circuits. The range is between 1 and 255, and the default is 5 cells.
- Down count—Number of consecutive OAM loopback cells an ATM virtual circuit must lose to be identified as unavailable—for example, 200.
- Up count—Number of consecutive OAM loopback cells an ATM virtual interface must receive to be identified as operational—for example, 200.
OAM period—Interval, in seconds, at which OAM cells are transmitted on ATM virtual circuits—for example, 100. The range is between 1 and 900 seconds.
Configure CBR for the Interface—for example, at-1/0/0.
- CBR – Range from 33000 through 1199920
- CDVT – Range from 1 through 9999
  Note: CDVT is not supported on J Series devices.
Configure Vbr for the Interface—for example, at-1/0/0.
- MBS – Range from 33000 through 1199920
- CDVT – Range from 1 through 9999
- PCR – Range from 33000 through 1199920
- SCR – Range from 33000 through 1199920

To configure the VPI value, enter
set atm-options vpi 25
To configure OAM liveness values on a VPI, enter
set atm-options vpi 25 oam-liveness up-count 200 down-count 200
To configure the OAM period, enter
set atm-options vpi 25 oam-period 100
To configure the CBR value, enter
set interfaces at-1/0/0 unit 0 shaping cbr
To configure the VBR value, enter
set interfaces at-1/0/0 unit 0 shaping vbr

Configure the type of DSL operating mode for the ATM-over-ADSL interface—for example auto.

Annex A and Annex B support 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.

Annex A supports the following operating modes:

adsl2plus—Configures the ADSL interface to train in ITU G.992.5 mode. You can configure this mode only when it is supported on the DSLAM.
itu-dmt-bis—Configures the ADSL interface to train in ITU G.992.3 mode. You can configure this mode only when it is supported on the DSLAM.
ansi-dmt—Configures the ADSL interface to train in the ANSI T1.413 Issue II mode.

Annex B supports the following operating modes:

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.

Enter

set dsl-options operating-mode auto

Configure the encapsulation type—for example, ethernet-over-atm.

atm-pvc—ATM permanent virtual circuits is the default encapsulation for ATM-over-ADSL interfaces.
For PPP over ATM (PPPoA) over ADSL interfaces, use this type of encapsulation.
ethernet-over-atm—Ethernet over ATM encapsulation.
For PPP over Ethernet (PPPoE) over ATM-over-ADSL interfaces that carry IPv4 traffic, use this type of encapsulation.

Enter

set encapsulation ethernet-over-atm

Configuring Logical Properties

Add the logical interface.

Set a value from 0 and 16385—for example, 3.

Add other values if required by your network.

Enter

set unit 3

Configure encapsulation for the ATM-for-ADSL logical unit—for example, atm-nlpid.

The following encapsulations are supported on the ATM-over-ADSL interfaces that use inet (IP) protocols only:

atm-vc-mux–Use ATM virtual circuit multiplex encapsulation.
atm-nlpid–Use ATM network layer protocol identifier (NLPID) encapsulation.
atm-cisco-nlpid–Use Cisco NLPID 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.

The following encapsulations are supported on the ATM-over-ADSL for PPP-over-ATM (PPPoA) interfaces only.

atm-ppp-llc— AAL5 logical link control (LLC) encapsulation.
atm-ppp-vc-mux—Use AAL5 multiplex encapsulation.

Other encapsulation types supported on the ATM-over-ADSL interfaces:

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.
atm-snap—Use ATM subnetwork attachment point (SNAP) encapsulation.

Enter

set unit 3 encapsulation atm-nlpid

Configure Operation, Maintenance, and Administration (OAM) options for ATM virtual circuits:

OAM F5 loopback cell thresholds (“liveness”) on ATM virtual circuits. The range is between 1 and 255, and the default is 5 cells.
- Down count—Number of consecutive OAM loopback cells an ATM virtual circuit must lose to be identified as unavailable—for example, 200.
- Up count—Number of consecutive OAM loopback cells an ATM virtual interface must receive to be identified as operational—for example, 200.
OAM period—Interval, in seconds, at which OAM cells are transmitted on ATM virtual circuits—for example, 100. The range is between 1 and 900 seconds.

To configure OAM liveness values for an ATM virtual circuit, enter
set unit 3 oam-liveness up-count 200 down-count 200
To configure the OAM period, enter
set unit 3 oam-period 100

Add the Family protocol type—for example, inet.

Enter

set unit 3 family inet

Commands vary depending on the protocol type.

Configure ATM virtual channel identifier (VCI) options for the interface.

ATM VCI type—vci.
ATM VCI value—A number between 0 and 4089—for example, 35— with VCIs 0 through 31 reserved.

To configure the VCI value, enter
set unit 3 vci 35