Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Configuring G.SHDSL Interfaces

 

The Symmetric high-speed DSL (SHDSL) interfaces supports an SHDSL multirate technology which helps for data transfer between a between a single CPE subscriber and a central office (CO). The topics below describe the SHDSL interfaces, G.SHDSL mini-pim and its configuration, and examples of configuration of these interfaces on SRX series devices.

SHDSL Interface Overview

Symmetric high-speed DSL (SHDSL) interfaces on some SRX Series devices support an SHDSL multirate technology for data transfer between a single customer premises equipment (CPE) subscriber and a central office (CO). ITU-T G.991.2 is the official standard for describing SHDSL, also known as G.SHDSL.

Unlike ADSL, which delivers more bandwidth downstream than available upstream, SHDSL is symmetrical and delivers a bandwidth of up to 2.3 Mbps in both directions. Because business applications require high-speed digital transportation methods, SHDSL is becoming very popular and gaining wide acceptance in the industry. Additionally, SHDSL is compatible with ADSL and therefore causes very little, if any, interference between cables.

SHDSL is deployed on a network in much the same manner as ADSL.

SHDSL interfaces support Packet Transfer Mode (PTM). In PTM, packets (IP, PPP, Ethernet, MPLS, and so on) are transported over DSL links as an alternative to using Asynchronous Transfer Mode (ATM). PTM is based on the Ethernet in the First Mile (EFM) IEEE 802.3ah standard.

Note

Starting in Junos OS Release 15.1X49-D10 SHDSL interfaces are no longer supported on SRX300, SRX320, SRX340, SRX345, and SRX550HM devices.

G.SHDSL Mini-PIM Overview

Starting in Junos OS Release 15.1X49-D10 SHDSL interfaces are no longer supported on SRX300, SRX320, SRX340, SRX345, and SRX550HM devices.

The G.SHDSL Mini-Physical Interface Module (Mini-PIM) provides the physical connection to DSL network media types.

The G.SHDSL Mini-PIM provides the following Asynchronous Transfer Mode (ATM) key features:

  • 2-wire (4-port 2-wire) mode, 4-wire (2-port 4-wire) mode, and 8-wire (1-port 8-wire) mode support

  • Virtual circuits (VC) per Mini-PIM (10 maximum including OAM VC)

  • ATM-over-G.SHDSL framing

  • ATM OAM support

  • Maximum MTU size of 9180 bytes

  • Noise margin support

  • Point-to-Point Protocol over ATM and PPPoE over ATM encapsulation support

  • Local loopback mode support

  • Dying gasp support

The G.SHDSL Mini-PIM provides extended ATM CoS functionality to cells across the network. You can define bandwidth utilization, which consists of either a constant rate or a peak cell rate, with sustained cell rate and burst tolerance. By default, unspecified bit rate (UBR) is used because the bandwidth utilization is unlimited.

The following ATM traffic shaping features are supported:

  • Constant bit rate (CBR)—CBR is the service category for traffic with rigorous timing requirements like voice and certain types of video. CBR traffic needs a constant cell transmission rate throughout the duration of the connection.

  • Variable bit rate, non-real-time (VBR-NRT)—VBR-NRT is intended for sources such as data transfer, which do not have strict time or delay requirements. VBR-NRT is suitable for packet data transfers.

  • Variable bit rate, real-time (VBR-RT)—VBR-RT is intended for sources such as data transfer, which takes place in real time. VBR-RT requires access to time slots at a rate that can vary significantly from time to time.

Table 1 displays the traffic descriptors specified for an ATM network.

Table 1: Traffic Descriptors

Traffic Descriptors

Description

Peak cell rate (PCR)

Maximum rate at which traffic can burst.

Sustained cell rate (SCR)

Normal traffic rate averaged over time.

Maximum burst size (MBS)

Maximum burst size that can be sent at the peak rate.

The G.SHDSL Mini-PIM provides the following Packet Transfer Mode (PTM) Ethernet in the First Mile (EFM) key features:

  • EFM PIC mode support

  • Maximum MTU size of 1514 bytes

  • PPPoE encapsulation support

  • Local loopback mode support

  • Chassis cluster mode support

  • Dying gasp support

  • IPv6 support

  • VLAN over EFM support

The following four annexes are supported on the G.SHDSL Mini-PIM in both ATM and PTM EFM modes:

  • Annex A

  • Annex B

  • Annex F

  • Annex G

Operating Modes and Line Rates of the G.SHDSL Mini-PIM

The G.SHDSL Mini-PIM supports 2-wire (4-port 2-wire) mode, 4-wire (2-port 4-wire) mode, 8-wire (1-port 8-wire) mode, and EFM mode. The default operating mode is 2x 4-wire for this G.SHDSL Mini-PIM. G.SHDSL is supported on all SRX210, SRX220, SRX240, and SRX550 devices using the symmetrical WAN speeds shown in Table 2.

Table 2: Symmetrical WAN Speeds

Modes

Symmetrical WAN Speed Using Annex A and B

Symmetrical WAN Speed Using Annex F and G

2-wire

2.3 Mbps

From 768 Kbps to 5.696 Mbps

4-wire

4.6 Mbps

From 1.536 Mbps to 11.392 Mbps

8-wire

9.2 Mbps

From 3.072 Mbps to 22.784 Mbps

EFM mode

2.3 Mbps

From 768 Kbps to 5.696 Mbps

Note: A maximum of 16 Mbps is supported on SRX210, SRX220, SRX240, and SRX550 devices.

G.SHDSL Mini-PIM Configuration Overview

Note

Starting in Junos OS Release 15.1X49-D10 SHDSL interfaces are no longer supported on SRX300, SRX320, SRX340, SRX345, and SRX550HM devices.

Specify the wire mode on the G.SHDSL interface using one of the following options:

  • 1-port-atm—Configures an 8-wire (1-port, 8-wire) wire mode.

  • 2-port-atm—Configures a 4-wire (2-port, 4-wire) wire mode.

  • 4-port-atm—Configures a 2-wire (4-port, 2-wire) wire mode.

  • efm—Configures an efm (1-port, 2-wire) wire mode.

Note

The default wire mode is 4-wire (2-port, 4-wire).

Specify the annex type using one of the following options:

  • Annex A

  • Annex B

  • Annex F

  • Annex G

Note

The default annex type is auto.

Specify the SHDSL line rate (speed of transmission of data on the SHDSL connection) using one of the following values:

  • auto—Automatically selects a line rate.

  • value—Selects a value between 192 kbps and 22,784 kbps.

Note

The default line rate is auto.

Specify the encapsulation type using one of the following values:

Note

The pt interface does not require encapsulation types.

The at interface encapsulation types are as follows:

  • atm-pvc—ATM permanent virtual circuits is the default encapsulation for ATM-over-SHDSL interfaces. For PPP over ATM (PPPoA) over SHDSL interfaces, use this type of encapsulation. Use this type of encapsulation if you are using ATM DSLAM.

  • ethernet-over-atm—Ethernet over ATM encapsulation. For PPP over Ethernet (PPPoE) over ATM-over-SHDSL interfaces that carry IPv4 traffic, use this type of encapsulation. Use this type of encapsulation if you are using IP DSLAM.

Configure the encapsulation type using one of the following values:

  • atm-cisco-nlpid—Cisco NLPID encapsulation.

  • atm-mlppp-llc—ATM MLPPP over AAL5/LLC encapsulation.

  • atm-nlpid—ATM Network Layer protocol identifier (NLPID) encapsulation.

  • atm-ppp-llc—AAL5 logical link control (LLC) encapsulation.

  • atm-ppp-vc-mux—AAL5 multiplex encapsulation.

  • atm-vc-mux—ATM virtual circuit multiplex encapsulation.

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

Example: Configuring the G.SHDSL Interface on SRX Series Devices

This example shows how to configure the G.SHDSL interface on SRX Series devices.

Note

Starting in Junos OS Release 15.1X49-D10 SHDSL interfaces are no longer supported on SRX300, SRX320, SRX340, SRX345, and SRX550HM devices.

Requirements

Before you begin:

  • Configure the network interfaces as necessary. See Understanding Ethernet Interfaces.

  • Install the G.SHDSL Mini-PIM in the first slot of the SRX210 chassis.

  • Connect the SRX210 device to a DSLAM (IP DSLAM and ATM DSLAM).

Note

This example uses an SRX210 Services Gateway. The information is also applicable to the SRX220 and SRX240 devices.

Overview

Figure 1 shows the topology for the G.SHDSL Mini-PIM operating in 2X4-wire mode.

Figure 1: G.SHDSL Mini-PIM Operating in 2X4-Wire Mode
G.SHDSL Mini-PIM Operating
in 2X4-Wire Mode

Figure 2 shows the topology for the G.SHDSL Mini-PIM operating in 4X2-wire mode.

Figure 2: G.SHDSL Mini-PIM Operating in 4X2-Wire Mode
G.SHDSL Mini-PIM
Operating in 4X2-Wire Mode

Figure 3 shows the topology for the G.SHDSL Mini-PIM operating in 1X8-wire mode.

Figure 3: G.SHDSL Mini-PIM Operating in 1X8-Wire Mode
G.SHDSL Mini-PIM
Operating in 1X8-Wire Mode

Determine the operating wire mode (2-wire, 4-wire, or 8-wire) and corresponding CLI code listed in Table 3.

Table 3: Operating Wire Modes

Wire Mode Configuration

CLI Code

2x4-wire Configuration

set chassis fpc 1 pic 0 shdsl pic-mode 2-port-atm

Note: The 2x4-wire configuration is the default configuration and behavior.

4x2-wire Configuration

set chassis fpc 1 pic 0 shdsl pic-mode 4-port-atm

1x8-wire Configuration

set chassis fpc 1 pic 0 shdsl pic-mode 1-port-atm

Note

When the wire mode is set to 8-wire, one physical interface (IFD) is created. Similarly for 4-wire mode and 2-wire mode, two IFDs and four IFDs are created, respectively.

In this example, you first configure a basic G.SHDSL interface. You set the operation wire mode to 2-port-atm, the line rate to 4096, and the annex type to annex-a.

You then configure the G.SHDSL interface when the device is connected to an IP DSLAM. You set the type of encapsulation to ethernet-over-atm and the ATM VPI option to 0. Then you set the type of encapsulation on the G.SHDSL logical interface as ether-over-atm-llc and configure the ATM VCI option to 0.60. Also, you set the interface address for the logical interface to 1.1.1.1/24.

Then you configure the G.SHDSL interface when the device is connected to an ATM DSLAM. You set the type of encapsulation to atm-pvc and the ATM VPI to 0. Then you set the type of encapsulation on the G.SHDSL logical interface to atm-snap and the ATM VCI to 0.65. Also, you set the interface address for the logical interface to 2.1.1.1/24

Next you configure PPPoE over ATM for the G.SHDSL Interface. You then set the ATM VPI to 0 and set the type of encapsulation to ppp-over-ether-over-atm-llc. You specify a PPPoE interface with the PAP access profile, local-name, and local-password. Then you configure the passive option to handle incoming PAP packets and set the logical interface as the underlying interface for the PPPoE session to at-1/0/0.0. Also, you set the number of seconds to 120 to wait before reconnecting after a PPPoE session is terminated. (The range is 1 through 4,294,967,295 seconds.) You then specify the logical interface as the client for the PPPoE interface and obtain an IP address by negotiation with the remote end.

Finally, you configure PPPoA over ATM for the G.SHDSL Interface. You set the type of encapsulation to atm-pvc and the ATM VPI to 0. You then set the type of encapsulation for PPP over ATM adaptation layer 5 (AAL5) logical link control (LLC) on the logical interface and set the ATM VCI to 122. You configure the PPPoA interface with the CHAP access profile as juniper and set the local-name for the CHAP interface to srx-210. Finally, you obtain an IP address by negotiation with the remote end.

Configuration

Configuring a Basic G.SHDSL Interface

CLI Quick Configuration

To quickly configure this example, copy the following command, paste it into a text file, remove any line breaks, change any details necessary to match your network configuration, copy and paste the command into the CLI at the [edit] hierarchy level, and then enter commit from configuration mode.

Step-by-Step Procedure

The following example requires you to navigate various levels in the configuration hierarchy. For instructions on how to do that, see Using the CLI Editor in Configuration Mode.

To quickly configure a basic G.SHDSL interface:

  1. Select the operating wire mode.
  2. Create an interface and set options.
  3. Configure the line rates.
  4. Set the annex type.

Results

From configuration mode, confirm your configuration by entering the show interfaces at-1/0/0 and show chassis fpc 1 commands. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.

If you are done configuring the device, enter commit from configuration mode.

Configuring a G.SHDSL Interface When Connected to an IP DSLAM

CLI Quick Configuration

To quickly configure this example, copy the following command, paste it into a text file, remove any line breaks, change any details necessary to match your network configuration, copy and paste the command into the CLI at the [edit] hierarchy level, and then enter commit from configuration mode.

Step-by-Step Procedure

The following example requires you to navigate various levels in the configuration hierarchy. For instructions on how to do that, see Using the CLI Editor in Configuration Mode.

To configure the G.SHDSL interface on an SRX210 device when the device is connected to an IP DSLAM:

  1. Create an interface.
  2. Specify the type of encapsulation.
  3. Configure the ATM VPI option.
  4. Specify the type of encapsulation for logical interface.
  5. Configure the ATM VCI options for the logical interface.
  6. Configure the interface address.

Results

From configuration mode, confirm your configuration by entering the show interfaces at-1/0/0 command. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.

If you are done configuring the device, enter commit from configuration mode.

Configuring a G.SHDSL Interface When Connected to an ATM DSLAM

CLI Quick Configuration

To quickly configure this example, copy the following command, paste it into a text file, remove any line breaks, change any details necessary to match your network configuration, copy and paste the command into the CLI at the [edit] hierarchy level, and then enter commit from configuration mode.

Step-by-Step Procedure

The following example requires you to navigate various levels in the configuration hierarchy. For instructions on how to do that, see Using the CLI Editor in Configuration Mode.

To configure the G.SHDSL interface on an SRX210 device when the device is connected to an ATM DSLAM:

  1. Create an interface.
  2. Specify the type of encapsulation.
  3. Configure the ATM VPI option.
  4. Specify the type of encapsulation for the logical interface.
  5. Configure the ATM VCI option.
  6. Configure the interface address.

Results

From configuration mode, confirm your configuration by entering the show interfaces at-1/0/0 command. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.

If you are done configuring the device, enter commit from configuration mode.

Configuring PPPoE over ATM for the G.SHDSL Interface

CLI Quick Configuration

To quickly configure this example, copy the following command, paste it into a text file, remove any line breaks, change any details necessary to match your network configuration, copy and paste the command into the CLI at the [edit] hierarchy level, and then enter commit from configuration mode.

Step-by-Step Procedure

The following example requires you to navigate various levels in the configuration hierarchy. For instructions on how to do that, see Using the CLI Editor in Configuration Mode.

To configure PPPoE over ATM on the G.SHDSL interface:

  1. Create an interface.
  2. Specify the type of encapsulation.
  3. Configure the ATM VPI option.
  4. Specify the type of encapsulation on the logical interface.
  5. Configure the ATM VCI option.
  6. Configure a PPPoE interface with the PAP access profile.
  7. Configure a local-name for the PAP interface.
  8. Configure a local-password for the PAP interface.
  9. Set the passive option to handle incoming PAP packets.
  10. Specify the logical interface as the underlying interface for the PPPoE session.
  11. Specify the number of seconds.
  12. Set the logical interface as the client for the PPPoE interface.
  13. Obtain an IP address by negotiation with the remote end.

Results

From configuration mode, confirm your configuration by entering the show interfaces at-1/0/0 and show interfaces pp0 commands. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.

If you are done configuring the device, enter commit from configuration mode.

Configuring PPPoA over ATM for the G.SHDSL Interface

CLI Quick Configuration

To quickly configure this example, copy the following command, paste it into a text file, remove any line breaks, change any details necessary to match your network configuration, copy and paste the command into the CLI at the [edit] hierarchy level, and then enter commit from configuration mode.

Step-by-Step Procedure

The following example requires you to navigate various levels in the configuration hierarchy. For instructions on how to do that, see Using the CLI Editor in Configuration Mode.

To configure PPPoA over ATM on the G.SHDSL interface:

  1. Create an interface.
  2. Specify the type of encapsulation.
  3. Configure the ATM VPI option.
  4. Specify the type of encapsulation on the G.SHDSL logical interface.
  5. Configure the ATM VCI option.
  6. Configure a PPPoA interface with the CHAP access profile.
  7. Configure a local name for the CHAP interface.
  8. Obtain an IP address by negotiation with the remote end.

Results

From configuration mode, confirm your configuration by entering the show interfaces at-1/0/0 command. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.

If you are done configuring the device, enter commit from configuration mode.

Verification

Confirm that the configuration is working properly.

Verifying G.SHDSL Interface Properties

Purpose

Verify that the G.SHDSL interface properties are configured properly.

Action

From operational mode, enter the show interfaces at-1/0/0 extensive command.

Example: Configuring the G.SHDSL Interface in EFM Mode

This example shows how to configure the G.SHDSL interface in Ethernet in the First Mile (EFM) mode on an SRX210 device, but it applies to the SRX220, SRX240, and SRX550 devices as well.

Note

Starting in Junos OS Release 15.1X49-D10 SHDSL interfaces are no longer supported on SRX300, SRX320, SRX340, SRX345, and SRX550HM devices.

Requirements

This example uses the following hardware and software components:

  • An SRX210 device

  • Junos OS Release 12.1X44-D10 or later

Before you begin:

  • Configure the network interfaces as necessary. See Understanding Ethernet Interfaces.

  • Install the G.SHDSL Mini-PIM in the first slot of the SRX210 chassis.

  • Connect the SRX210 device to an EFM supported IP DSLAM.

Overview and Topology

In this example, you first configure a basic G.SHDSL interface by setting the operation wire mode to efm, the line rate to auto, and the annex type to annex-auto.

You then configure the G.SHDSL interface when the device is connected to an EFM IP DSLAM. You set the logical interface to 10.10.10.1/24.

Next you configure PPPoE for the G.SHDSL Interface. Configure the encapsulation as ppp-over-ether under unit 0 of pt-1/0/0 interface. You specify a PPPoE interface with the PAP access profile, local name, and local password. Then you configure the passive option to handle incoming PAP packets and set the logical interface as the underlying interface for the PPPoE session to pt-1/0/0.0. Also, you set the number of seconds to 120 to wait before reconnecting after a PPPoE session is terminated. (The range is 1 through 4,294,967,295 seconds.) Finally, you specify the logical interface as the client for the PPPoE interface and obtain an IP address by negotiation with the remote end.

Figure 4 shows the topology for the G.SHDSL Mini-PIM operating in EFM mode.

Figure 4: G.SHDSL Mini-PIM Operating in EFM Mode
G.SHDSL Mini-PIM Operating in EFM
Mode

Table 4 lists the operating wire mode for EFM and its corresponding CLI code.

Table 4: Operating Wire Mode for EFM

Wire Mode Configuration

CLI Code

EFM Configuration

set chassis fpc 1 pic 0 shdsl pic-mode efm

Note

When PIC mode is set to EFM, an interface called pt-1/0/0 is created.

Configuration

Configuring a Basic G.SHDSL Interface in EFM PIC Mode

CLI Quick Configuration

To quickly configure this example, copy the following command, paste it into a text file, remove any line breaks, change any details necessary to match your network configuration, copy and paste the command into the CLI at the [edit] hierarchy level, and then enter commit from configuration mode.

Step-by-Step Procedure

The following example requires you to navigate various levels in the configuration hierarchy. For instructions on how to do that, see Using the CLI Editor in Configuration Mode.

To configure a basic G.SHDSL interface:

  1. Specify the PIC mode.
    Note

    When configuring the G.SHDSL interface in chassis cluster mode, include the node ID. For example, to configure the G.SHDSL interface (operating in EFM PIC mode) in chassis cluster mode for fpc slot 1 on node 0, use the following command:

    set chassis node 0 fpc 1 pic 0 shdsl pic-mode efm

  2. Configure the IP address.
    Note

    By default, annex mode and line rate are set to auto. If you have to configure annex mode (annex-g) and line rate (5696 Kbps), follow Steps 3, 4, and 5.

  3. Configure SHDSL options.
  4. Specify the annex type.
  5. Configure the line rate.

Results

From configuration mode, confirm your configuration by entering the show interfaces pt-1/0/0 and show chassis fpc 1 commands. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.

If you are done configuring the device, enter commit from configuration mode.

Configuring PPPoE and VLAN for the G.SHDSL EFM Interface

CLI Quick Configuration

To quickly configure this example, copy the following command, paste it into a text file, remove any line breaks, change any details necessary to match your network configuration, copy and paste the command into the CLI at the [edit] hierarchy level, and then enter commit from configuration mode.

Note

In this configuration, we use PAP as the authentication mechanism. If Broadband Remote Access Server (BRAS) uses CHAP, PAP configuration should be replaced with CHAP.

Step-by-Step Procedure

The following example requires you to navigate various levels in the configuration hierarchy. For instructions on how to do that, see Using the CLI Editor in Configuration Mode.

To configure PPPoE for the G.SHDSL EFM Interface:

  1. Create an interface.
  2. Specify the type of encapsulation.
  3. Configure a PPPoE interface with the PAP access profile.
  4. Configure a local name for the PAP interface.
  5. Configure a local password for the PAP interface.
  6. Set the passive option to handle incoming PAP packets.
  7. Specify the logical interface as the underlying interface for the PPPoE session.
  8. Specify the number of seconds.
  9. Set the logical interface as the client for the PPPoE interface.
  10. Obtain an IP address by negotiation with the remote end.
  11. Configure VLAN on EFM.
  12. Specify the VLAN ID.

Results

From configuration mode, confirm your configuration by entering the show interfaces pt-1/0/0 and show interfaces pp0 commands. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.

If you are done configuring the device, enter commit from configuration mode.

Verification

Verifying G.SHDSL Interface Properties

Purpose

Verify that the G.SHDSL interface properties are configured properly.

Action

From operational mode, enter the show interfaces pt-1/0/0 extensive command.

user@host> show interfaces pt-1/0/0 extensive

EFM mode for interface pt-1/0/0:

Meaning

The output shows a summary of interface information. Verify the following information:

  • The physical interface is enabled. If the interface is shown as disabled, do either of the following:

    • In the CLI configuration editor, delete the disable statement at the [edit interfacesinterface-name] level of the configuration hierarchy.

    • In the J-Web configuration editor, clear the Disable check box on the Interfaces page (Interfaces>interface-name).

  • The physical link is up. A link state of down indicates a problem with the interface module, interface port, or physical connection (link-layer errors).

  • The last flapped time is an expected value. The last flapped time indicates the last time the physical interface became unavailable and then available again. Unexpected flapping indicates likely link-layer errors.

  • The traffic statistics reflect expected input and output rates. Verify that the number of inbound and outbound bytes and packets matches expected throughput for the physical interface. To clear the statistics and see only new changes, use the clear interfaces statistics interface-name command.

  • The following information is displayed for each line pair:

    No SHDSL alarms and defects appear that can render the interface unable to pass packets. When a defect persists for a certain amount of time, it is promoted to an alarm.

    • LOSW—Loss of sync word. A message ID was sent.

    • LOSD—Loss of signal was detected at the remote application interface.

    • ES—Errored seconds. One or more cyclic redundancy check (CRC) anomalies were detected.

    • SES—Severely errored seconds. At least 50 CRC anomalies were detected.

    • UAS—Unavailable seconds. An interval has occurred during which one or more LOSW defects were detected.

Examine the SHDSL interface status:

  • Line termination—SHDSL transceiver unit–remote (STU–R). (Only customer premises equipment is supported.)

  • Annex—Either Annex A or Annex B. Annex A is supported in North America, and Annex B is supported in Europe.

  • Line mode—SHDSL mode configured on the G.SHDSL interface pair, and it should be two-wire.

  • Modem status—Data. Sending or receiving data.

  • Bit rate (kbps)—Data transfer speed on the SHDSL interface.

  • Last fail code—Code for the last interface failure.

  • Framer mode—ATM framer mode of the underlying interface.

  • PAF Status—Either Active/Inactive depending upon whether link added to EFM group or not.

Examine the operational statistics for a SHDSL interface.

  • Loop attenuation (dB)—Reduction in signal strength.

  • Transmit power (dB)—Amount of SHDSL.

  • SNR sampling (dB)—Signal-to-noise ratio at a receiver point.

  • CRC errors—Number of cyclic redundancy check errors.

  • SEGA errors—Number of segment anomaly errors. A regenerator operating on a segment received corrupted data.

  • LOSW errors—Number of loss of signal defect errors. Three or more consecutively received frames contained one or more errors in the framing bits.

Release History Table
Release
Description
Starting in Junos OS Release 15.1X49-D10 SHDSL interfaces are no longer supported on SRX300, SRX320, SRX340, SRX345, and SRX550HM devices.
Starting in Junos OS Release 15.1X49-D10 SHDSL interfaces are no longer supported on SRX300, SRX320, SRX340, SRX345, and SRX550HM devices.
Starting in Junos OS Release 15.1X49-D10 SHDSL interfaces are no longer supported on SRX300, SRX320, SRX340, SRX345, and SRX550HM devices.
Starting in Junos OS Release 15.1X49-D10 SHDSL interfaces are no longer supported on SRX300, SRX320, SRX340, SRX345, and SRX550HM devices.
Starting in Junos OS Release 15.1X49-D10 SHDSL interfaces are no longer supported on SRX300, SRX320, SRX340, SRX345, and SRX550HM devices.