TechLibrary

Navigation Back up to About Overview

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.

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.

Note: This example uses an SRX210 Services Gateway. The information is also applicable to the SRX220, SRX240, and SRX550 Services Gateways.

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 1 shows the topology for the G.SHDSL Mini-PIM operating in EFM mode.

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

G.SHDSL Mini-PIM Operating in EFM
Mode

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

Table 1: Operating Wire Mode

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 commands, paste them into a text file, remove any line breaks, change any details necessary to match your network configuration, and then copy and paste the commands into the CLI at the [edit] hierarchy level.

set chassis fpc 1 pic 0 shdsl pic-mode efmset interfaces pt-1/0/0 shdsl-options annex annex-g set interfaces pt-1/0/0 shdsl-options line-rate 5696 set interfaces pt-1/0/0 unit 0 family inet address 10.10.10.1/24

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.
    [edit]user@host# set chassis fpc 1 pic 0 shdsl pic-mode efm

    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.
    [edit]user@host# set interfaces pt-1/0/0 unit 0 family inet address 10.10.10.1/24

    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.
    [edit]user@host# set interfaces pt-1/0/0 shdsl-options
  4. Specify the annex type.
    [edit interfaces pt-1/0/0 shdsl-options]user@host# set annex annex-g
  5. Configure the line rate.
    [edit interfaces pt-1/0/0 shdsl-options]user@host# set line-rate 5696

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.

[edit]user@host# show interfaces pt-1/0/0shdsl-options {annex annex-g;line-rate 5696;}unit 0 {family inet {address 10.10.10.1/24;}}[edit]user@host# show chassis fpc 1pic 0 {shdsl {pic-mode efm;}}

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 commands, paste them into a text file, remove any line breaks, change any details necessary to match your network configuration, and then copy and paste the commands into the CLI at the [edit] hierarchy level.

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.

set interfaces pt-1/0/0 unit 0 encapsulation ppp-over-etherset interfaces pp0 unit 0 ppp-options pap access-profile pap_prof local-name srx-210 set interfaces pp0 unit 0 ppp-options pap local-password "$9$0tLw1SeN-woJDSr-wY2GU69Cp1RSre" set interfaces pp0 unit 0 ppp-options pap passive set interfaces pp0 unit 0 pppoe-options underlying-interface pt-1/0/0.0 set interfaces pp0 unit 0 pppoe-options auto-reconnect 120 client set interfaces pp0 unit 0 family inet negotiate-address

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.
    [edit]user@host# set interfaces pt-1/0/0
  2. Specify the type of encapsulation.
    [edit interfaces pt-1/0/0]user@host# set unit 0user@host# set encapsulation ppp-over-ether
  3. Configure a PPPoE interface with the PAP access profile.
    [edit]user@host# set interfaces pp0 unit 0 ppp-options papuser@host# set access-profile pap_prof
  4. Configure a local name for the PAP interface.
    [edit interfaces pp0 unit 0 ppp-options pap]user@host# set local-name srx-210
  5. Configure a local password for the PAP interface.
    [edit interfaces pp0 unit 0 ppp-options pap]user@host# set local-password "$9$0tLw1SeN-woJDSr-wY2GU69Cp1RSre"
  6. Set the passive option to handle incoming PAP packets.
    [edit interfaces pp0 unit 0 ppp-options pap]user@host# set passive
  7. Specify the logical interface as the underlying interface for the PPPoE session.
    [edit]user@host# set interfaces pp0 unit 0 pppoe-optionsuser@host# set underlying-interface pt-1/0/0.0
  8. Specify the number of seconds.
    [edit interfaces pp0 unit 0 pppoe-options]user@host# set auto-reconnect 120
  9. Set the logical interface as the client for the PPPoE interface.
    [edit interfaces pp0 unit 0 pppoe-options]user@host# set client
  10. Obtain an IP address by negotiation with the remote end.
    [edit interfaces]user@host# set pp0 unit 0 family inet negotiate-address
  11. Configure VLAN on EFM.
    [edit interfaces]user@host# set pt-1/0/0 vlan-tagging
  12. Specify the VLAN ID.
    [edit interfaces]user@host# set pt-1/0/0 unit 0 vlan-id 99

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.

[edit]user@host# show interfaces pt-1/0/0vlan-tagging;
unit 0 {encapsulation ppp-over-ether;vlan-id 99;}
[edit]user@host# show interfaces pp0
unit 0 {ppp-options {pap {access-profile pap_prof;local-name srx-210;local-password "$9$0tLw1SeN-woJDSr-wY2GU69Cp1RSre";passive;}}pppoe-options {underlying-interface pt-1/0/0.0;auto-reconnect 120;client;}family inet {negotiate-address;}}

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:

Physical interface: pt-1/0/0, Enabled, Physical link is Up
  Interface index: 158, SNMP ifIndex: 575, Generation: 277
  Link-level type: Ethernet, MTU: 1514, Speed: SHDSL(8-Wire)
  Device flags   : Present Running
  Link flags     : None
  CoS queues     : 8 supported, 8 maximum usable queues
  Hold-times     : Up 0 ms, Down 0 ms
  Current address: 78:fe:3d:60:2f:99
  Last flapped   : 2012-10-11 00:03:13 PDT (00:28:57 ago)
  Statistics last cleared: 2012-10-11 00:32:05 PDT (00:00:05 ago)
  Traffic statistics:
   Input  bytes  :                    0                    0 bps
   Output bytes  :                    0                    0 bps
   Input  packets:                    0                    0 pps
   Output packets:                    0                    0 pps
  Input errors:
    Errors: 0, Drops: 0, Invalid VCs: 0, Framing errors: 0, Policed discards: 0, L3 incompletes: 0, L2 channel errors: 0, L2 mismatch timeouts: 0, Resource errors: 0
  Output errors:
    Carrier transitions: 0, Errors: 0, Drops: 0, Aged packets: 0, MTU errors: 0, Resource errors: 0
  EFM Group Statistics:
    Type                  : EFM bond
    Active Pairs          : 4
    Bit rate (in Kbps)    : 22784
  Line Pair  0  : Up
    Active alarms  : None
    Active defects : None
    SHDSL media:      Seconds   Count   State
      ES                    0
      SES                   0
      UAS                   0
    SHDSL status:
      Line  termination      : STU-R
      Annex                  : Annex G
      Line mode              : 2-wire
      Modem status           : Data
      Bit rate (kbps)        : 5696
      Last fail mode         : No failure (0x00)
      Framer mode            : EFM
      PAF Status             : Active
      Dying gasp             : Enabled
      Framer sync status     : In sync
    SHDSL statistics:
      Loop attenuation (dB)  : 0.0
      Transmit power (dBm)   : 14.0
      SNR sampling (dB)      : 14.0000
      CRC errors             : 2
      SEGA errors            : 0
      LOSW errors            : 0
  Line Pair  1  : Up                    
    Active alarms  : None
    Active defects : None
    SHDSL media:      Seconds   Count   State
      ES                    0
      SES                   0
      UAS                   0
    SHDSL status:
      Line  termination      : STU-R
      Annex                  : Annex G
      Line mode              : 2-wire
      Modem status           : Data
      Bit rate (kbps)        : 5696
      Last fail mode         : No failure (0x00)
      Framer mode            : EFM
      PAF Status             : Active
      Dying gasp             : Enabled
      Framer sync status     : In sync
    SHDSL statistics:
      Loop attenuation (dB)  : 0.0
      Transmit power (dBm)   : 14.0
      SNR sampling (dB)      : 19.0000
      CRC errors             : 0
      SEGA errors            : 0
      LOSW errors            : 0
  Line Pair  2  : Up
    Active alarms  : None
    Active defects : None
    SHDSL media:      Seconds   Count   State
      ES                    0
      SES                   0
      UAS                   0
    SHDSL status:
      Line  termination      : STU-R
      Annex                  : Annex G
      Line mode              : 2-wire
      Modem status           : Data
      Bit rate (kbps)        : 5696
      Last fail mode         : No failure (0x00)
      Framer mode            : EFM
      PAF Status             : Active
      Dying gasp             : Enabled
      Framer sync status     : In sync
    SHDSL statistics:
      Loop attenuation (dB)  : 0.0
      Transmit power (dBm)   : 14.0
      SNR sampling (dB)      : 14.0000
      CRC errors             : 0
      SEGA errors            : 0        
      LOSW errors            : 0
  Line Pair  3  : Up
    Active alarms  : None
    Active defects : None
    SHDSL media:      Seconds   Count   State
      ES                    0
      SES                   0
      UAS                   0
    SHDSL status:
      Line  termination      : STU-R
      Annex                  : Annex G
      Line mode              : 2-wire
      Modem status           : Data
      Bit rate (kbps)        : 5696
      Last fail mode         : No failure (0x00)
      Framer mode            : EFM
      PAF Status             : Active
      Dying gasp             : Enabled
      Framer sync status     : In sync
    SHDSL statistics:
      Loop attenuation (dB)  : 1.0
      Transmit power (dBm)   : 14.0
      SNR sampling (dB)      : 18.0000
      CRC errors             : 0
      SEGA errors            : 0
      LOSW errors            : 0
  Packet Forwarding Engine configuration:
    Destination slot: 0 (0x00)
  CoS information:
    Direction : Output 
    CoS transmit queue               Bandwidth               Buffer Priority   Limit
                              %            bps     %           usec
    0 best-effort            95       21644800    95              0      low    none
    3 network-control         5        1139200     5              0      low    none

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.
  • Dying gasp—Ability of a J Series device that has lost power to send a message informing the attached DSLAM that it is about to go offline.

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.

Published: 2013-01-07