Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Example: Configuring the G.SHDSL Interface

 

This example shows how to configure the G.SHDSL interface.

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 network interfaces as necessary. See Understanding Ethernet Interfaces.

Overview

In this example, you specify the wire mode called 2-port-atm and create an interface called at-1/0/0. You then specify the annex type as annex-a and set the line rate to auto. Then you specify the encapsulation type as ethernet-over-atm and define a logical unit as unit 3 that you connect to this physical G.SHDSL interface. You can set a value from 0 through 7. Finally, you configure the encapsulation type as ether-over-atm-llc.

Configuration

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:

  1. Specify the wire mode.
    Note

    For configuring the G.SHDSL interface in chassis cluster mode, provide the node id also. For example, to configure an shdsl 2 port pic-mode in chassis cluster mode for the fpc slot 1 on the node 0, use the following command:

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

  2. Create an interface.
  3. Specify the annex type.
  4. Configure the line rate.
  5. Specify the encapsulation type.
  6. Define one or more logical units.
  7. Configure the encapsulation 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.

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.

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

Four-wire mode for interface at-1/0/0:

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.

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

    • LOS—Loss of signal. No signal was detected on the line.

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

    • Power status—A power failure has occurred.

    • 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, either two-wire or four-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.

  • Dying gasp—Ability of a device that has lost power to send a message informing the attached DSLAM that it is about to go offline.

  • Chipset version—Version number of the chipset on the interface

Examine the operational statistics for a SHDSL interface.

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

  • Transmit power (dB)—Amount of SHDSL.

  • Receiver gain (dB)—Maximum extraneous signal allowed without causing the output to deviate from an acceptable level.

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

  • Received cells—Number of cells received through the interface.

  • Transmitted cells—Number of cells sent through the interface.

  • HEC errors—Number of header error checksum errors.

  • Cell drop—Number of dropped cells on the interface.

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.