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

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. (For information about interface names, see Network Interface Naming.) Multiple encapsulation types are supported on both the physical and logical ATM-over-ADSL interface.

This section contains the following topics:

Configuring an ATM-over-ADSL Interface with Quick Configuration

The Quick Configuration pages allow you to configure ATM-over-ADSL interfaces on J-series devices.

To configure an ATM-over-ADSL interface with Quick Configuration:

  1. In the J-Web user interface, select Configuration>Quick Configuration>Interfaces.

    A list of the network interfaces present on the device is displayed. (See Network Interface Naming.)

  2. Select the at-pim/0/port interface name for the ADSL port you want to configure.

    The ATM-over-ADSL Quick Configuration page is displayed, as shown in Figure 23.

    Figure 23: ATM-over-ADSL Interfaces Quick Configuration Page

    Image s031007.gif

  3. Enter information into the ATM-over-ADSL Quick Configuration pages, as described in Table 54.
  4. From the ATM-over-ADSL Quick Configuration main page, click one of the following buttons:
  5. To verify that the ATM-over-ADSL interface is configured properly, see Verifying DSL Interface Configuration.

Table 54: ATM-over-ADSL Interface Quick Configuration Pages Summary

Field

Function

Your Action

Configuring Logical Interfaces

Logical Interfaces

Lists the logical interfaces for this ATM-over-ADSL physical interface.

  • To add a logical interface, click Add.
  • To edit a logical interface, select the interface from the list.
  • To delete a logical interface, select the check box next to the name and click Delete.
Adding or Editing a Logical Interface

Add logical interfaces

Defines one or more logical units that you connect to this physical ADSL interface.

Click Add.

Logical Interface Description

(Optional) Describes the logical interface.

Type a text description of the logical interface to more clearly identify it in monitoring displays.

Encapsulation

Specifies the type of encapsulation on the DSL logical interface.

From the list, select one of the following types of encapsulations.

For ATM-over-ADSL interfaces that use inet (IPv4) protocols only, select one of the following:

  • ATM VC multiplexing—Use ATM virtual circuit multiplex encapsulation.
  • ATM NLPID—Use ATM network layer protocol identifier (NLPID) encapsulation.
  • Cisco-compatible ATM NLPID—Use Cisco NLPID encapsulation.
  • Ethernet over ATM (LLC/SNAP)—For interfaces that carry IPv4 traffic, use Ethernet over logical link control (LLC) encapsulation. You cannot configure multipoint interfaces if you use this type of encapsulation.

For ATM-over-ADSL for PPP-over-ATM (PPPoA) interfaces only, select one of the following:

  • ATM PPP over AAL5/LLC—Use AAL5 logical link control (LLC) encapsulation.
  • ATM PPP over Raw AAL5—Use AAL5 multiplex encapsulation.

For other encapsulation types on the ATM-over-ADSL interfaces, select one of the following:

  • PPPoE over ATM (LLC/SNAP)—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.
  • Ethernet over ATM (LLC/SNAP)—Use ATM subnetwork attachment point (SNAP) encapsulation.

VCI

Configures the ATM virtual circuit identifier (VCI) for the interface.

In the VCI box, type the number for the VCI.

Add IPv4 address prefixes and destinations

Specifies one or more IPv4 addresses and destination addresses.

Click Add.

IPv4 Address Prefix

Specifies an IPv4 address for the interface.

Type an IPv4 address and prefix. For example:

10.10.10.10/24

Destination Address

Specifies the destination address.

  1. Type an IPv4 address for the destination.
  2. Click OK.
Configuring Physical Interface Properties

Physical Interface Description

(Optional) Adds supplementary information about the physical ATM-over-ADSL interface.

Type a text description of the physical ATM-over-ADSL interface to more clearly identify it in monitoring displays. Specify that it is an ADSL interface.

MTU (bytes)

Specifies the maximum transmit size of a packet for the ATM-over-ADSL interface.

Type a value from 256 to 9192.

Encapsulation

Selects the type of encapsulation for traffic on this physical interface.

From the list, select the type of encapsulation for this ATM-over-ADSL interface:

  • ATM permanent virtual circuits—Use this type of encapsulation for PPP over ATM (PPPoA) over ADSL interfaces. This is the default encapsulation for ATM-over-ADSL interfaces.
  • Ethernet over ATM encapsulation—Use this type of encapsulation for PPP over Ethernet (PPPoE) over ATM-over-ADSL interfaces that carry IPv4 traffic.

VPI

Configures the ATM virtual path identifier for the interface.

Type a VPI value between 0 and 255.

Configuring ADSL Options

Operating Mode

Specifies the type of DSL operating mode for the ATM-over-ADSL interface.

From the list, select one of the following types of DSL operating modes—for example auto.

For Annex A or Annex B, or Annex M (applicable to SRX 210 services gateways), select one of the following:

  • auto—Configure the ADSL interface to auto negotiate 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.

    For Annex M, the ADSL interface trains in ITU G.992.3 mode (applicable to SRX 210 services gateways).

  • itu-dmt-bis—Configure the ADSL interface to train in ITU G.992.3 mode. The ADSL interface trains in ITU G.992.5 mode.
  • adsl2plus—Configure the ADSL interface to train in ITU G.992.5 mode. You can configure this mode only when it is supported on the DSLAM.

For Annex A and Annex B, select the following:

  • itu-dmt—Configure the ADSL interface to train in ITU G.992.1 mode.
  • adsl2plus—Configure 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—Configure the ADSL interface to train in ITU G.992.3 mode. The ADSL interface trains in ITU G.992.5 mode.

For Annex A only, select the following:

  • ansi-dmt—Configure the ADSL interface to train in the ANSI T1.413 Issue II mode.

For Annex B only, select the following:

  • itu-annexb-ur2—Configure the ADSL line to train in the G.992.1 Deutsche Telekom UR-2 mode.

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:

  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 55.
  3. If you are finished configuring the J-series device, commit the configuration.
  4. Go on to one of the following procedures:
  5. To check the configuration, see Verifying DSL Interface Configuration.

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

Task

J-Web Configuration Editor

CLI Configuration Editor

Navigate to the Interfaces level in the configuration hierarchy.

  1. In the J-Web interface, select Configuration>View and Edit>Edit Configuration.
  2. Next to Interfaces, click Edit.

From the [edit] hierarchy level, enter

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 at-2/0/0.
  3. Click OK.
 
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
  • 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
  1. In the Interface name box, select at-2/0/0.
  2. Next to Atm options, click Configure.
  3. Next to Vpi, click Add new entry.
  4. In the Vpi number box, type 25.
  5. Click OK.
  6. In the Actions box, click Edit.
  7. Next to Oam liveness, click Configure.
  8. In the Down count box, type 200.
  9. In the Up count box, type 200.
  10. Click OK.
  11. Next to Oam period, click Configure.
  12. From the Oam period choices list, select Oam period.
  13. In the Oam period box, type 100.
  14. Click OK until you return to the Interface page.
  15. Next to Shaping, click Configure.
  16. In the Queue length box, type 200.
  17. From the Useless Shaping Choice list, select Cbr.
  18. In the Cbr value box, type 33000.
  19. In the Cdvt box, type 200, Click OK.
  20. From the Useless Shaping Choice list, select Vbr.
  21. In the Burst box, type 33000.
  22. In the Cdvt box, type 200.
  23. In the Peak box, type 33000.
  24. In the Sustained box, type 33000.
  25. Click OK.
  1. To configure the VPI value, enter

    set atm-options vpi 25

  2. To configure OAM liveness values on a VPI, enter

    set atm-options vpi 25 oam-liveness up-count 200 down-count 200

  3. To configure the OAM period, enter

    set atm-options vpi 25 oam-period 100

  4. To configure the CBR value, enter

    set interfaces at-1/0/0 unit 0 shaping cbr

  5. 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.
  1. Next to Dsl options, click Configure.
  2. From the Operating Mode list, select auto.
  3. Click OK.

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.

From the Encapsulation list, select ethernet-over-atm.

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.

  1. Scroll down the page to Unit, and click Add new entry.
  2. In the Interface unit number box, type 3.
  3. Enter other values in the fields 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. (For a sample PPPoA configuration, see Verifying Interface Configuration.)

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

From the Encapsulation list, select atm-nlpid.

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.
  1. Next to Oam liveness, click Configure.
  2. In the Down count box, type 200.
  3. In the Up count box, type 200.
  4. Click OK.
  5. Next to Oam period, click Configure.
  6. From the Oam period choices list, select Oam period.
  7. In the Oam period box, type 100.
  8. Click OK.
  1. To configure OAM liveness values for an ATM virtual circuit, enter

    set unit 3 oam-liveness up-count 200 down-count 200

  2. To configure the OAM period, enter

    set unit 3 oam-period 100

Add the Family protocol type—for example, inet.

  1. In the Inet box, select Yes and click Configure.
  2. Enter the values in the fields required by your network.
  3. Click OK.

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.
  1. From the Vci Type list, select vci.
  2. In the Vci box, type 35.
  3. Click OK until you return to the Interfaces page.
  1. To configure the VCI value, enter

    set unit 3 vci 35


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