Audiocodes Mediant msbr series User manual

Configuration Guide

Multi-Service Business Routers (MSBR) Product Series

Configuring Mediant™ MSBR

for WAN & LAN Access

Version 7.2

Version 7.2 3 WAN & LAN Access Interfaces

Configuration Guide Contents

Table of Contents

1Introduction .........................................................................................................7

2Wireless WAN Cellular Interface ........................................................................9

2.1 DHCP Type Cellular Interface................................................................................12

2.2PPP Cellular Type Example...................................................................................13

2.3 Debugging Cellular WAN Interface ........................................................................15

2.4 Troubleshooting Cellular WAN Interface................................................................16

3PPP and PPPoE .................................................................................................17

3.1 Examples ...............................................................................................................18

4ADSL/VDSL........................................................................................................19

4.1 ADSL Examples .....................................................................................................20

4.2 Examples ...............................................................................................................21

5ATM-based Interfaces and Encapsulation ......................................................23

5.1 Examples ...............................................................................................................24

6EFM Interfaces...................................................................................................27

6.1 Examples ...............................................................................................................27

7Configuring VLANs on WAN interface ............................................................29

7.1 Configuration Example...........................................................................................30

8SHDSL - EFM/ATM.............................................................................................31

8.1 Examples ...............................................................................................................32

9Ethernet OAM ....................................................................................................35

9.1 What is Ethernet OAM ...........................................................................................35

9.2 Ethernet CFM (CFM OAM) ....................................................................................35

9.2.1 Description...............................................................................................................35

9.2.1.1 Acronyms & Terms...................................................................................35

9.2.1.2 CFM Sub-Protocols ..................................................................................36

9.2.2 CFM MPID Configuration.........................................................................................36

10 Ethernet CFM Verification ................................................................................39

10.1.1 Show Data Ethernet CFM........................................................................................39

10.1.2 Ping Ethernet ...........................................................................................................40

10.1.3 Traceroute Ethernet.................................................................................................40

10.1.4 Show Remote Ethernet CFM Maintenance-points ..................................................40

11 Y.1731: OAM Functions and Mechanisms for Ethernet based Networks.....43

11.1 Description .............................................................................................................43

11.2 Functions for Fault Management ...........................................................................43

11.2.1 Alarm Indication Signal (AIS) Condition ..................................................................43

11.2.1.1 Ethernet Locked - Signal ETH-LCK .........................................................43

11.3 Functions for Performance Management (Y.1731) ................................................ 45

11.3.1 Set Frame Delay Measurement (ETH-DM) .............................................................45

11.3.1.1 1DM - One-way ETH-DM (using 1DM PDU)............................................45

11.3.1.2 DMM/DMR - Two-way ETH-DM (using DMM and DMR PDUs) ..............46

Configuration Guide 4 Document #: LTRT-31668

WAN & LAN Access Interfaces

11.3.1.3 DMM Reception and DMR Transmission.................................................46

11.4 EFM OAM ..............................................................................................................49

11.4.1 Description...............................................................................................................49

11.4.2 Features...................................................................................................................49

11.4.2.1 Discovery..................................................................................................49

11.4.2.2 Link Monitoring .........................................................................................49

11.4.2.3 Remote Failure Indication ........................................................................50

11.4.2.4 Remote Loopback ....................................................................................50

11.4.2.5 OAM Messages........................................................................................50

11.4.3 Configuration ...........................................................................................................51

11.4.4 Show Commands ....................................................................................................52

12 Multiple DSL Connection..................................................................................55

12.1 Examples ...............................................................................................................55

13 E1/T1 (PRI) .........................................................................................................57

13.1 Examples ...............................................................................................................58

14 Serial HDLC .......................................................................................................59

14.1 Examples ...............................................................................................................60

15 Fiber Optic .........................................................................................................61

15.1 Examples ...............................................................................................................61

16 WAN Failover.....................................................................................................63

16.1 Examples ...............................................................................................................64

16.1.1 Cold Backup WAN Failover .....................................................................................64

16.1.2 Hot Backup WAN Failover.......................................................................................65

16.1.3 Cellular as backup only............................................................................................66

17 Wi-Fi ...................................................................................................................67

17.1 Examples ...............................................................................................................71

17.2 Advanced Wi-Fi Example.......................................................................................73

18 LLDP...................................................................................................................75

18.1 Examples ...............................................................................................................75

Version 7.2 5 WAN & LAN Access Interfaces

Configuration Guide Notices

Notice

Information contained in this document is believed to be accurate and reliable at the time of

printing. However, due to ongoing product improvements and revisions, AudioCodes cannot

guarantee accuracy of printed material after the Date Published nor can it accept responsibility

for errors or omissions. Updates to this document can be downloaded from

https://www.audiocodes.com/library/technical-documents.

This document is subject to change without notice.

Date Published: February-02-2019

WEEE EU Directive

Pursuant to the WEEE EU Directive, electronic and electrical waste must not be disposed of

with unsorted waste. Please contact your local recycling authority for disposal of this product.

Customer Support

Customer technical support and services are provided by AudioCodes or by an authorized

AudioCodes Service Partner. For more information on how to buy technical support for

AudioCodes products and for contact information, please visit our website at

https://www.audiocodes.com/services-support/maintenance-and-support.

Stay in the Loop with AudioCodes

Abbreviations and Terminology

Each abbreviation, unless widely used, is spelled out in full when first used.

Configuration Guide 6 Document #: LTRT-31668

WAN & LAN Access Interfaces

Document Revision Record

LTRT Description

31660 Initial document release for Version 6.8.

31661 New chapter added for A/VDSL recovery.

31664 New chapters added for Ethernet OAM, Ethernet CFM Verification, Y.1731 and EFM

OAM. Removed support for interface termination CO mode.

31665 Updated to 7.2 (ADSL/VDSL and WAN Failover sections).

31667 Added Configuring VLANs on WAN Interface chapter.

31668 WAN cellular updated with LTE.

Documentation Feedback

AudioCodes continually strives to produce high quality documentation. If you have any

comments (suggestions or errors) regarding this document, please fill out the Documentation

Feedback form on our website at https://online.audiocodes.com/documentation-feedback.

Version 7.2 7 WAN & LAN Access Interfaces

Configuration Guide 1. Introduction

1 Introduction

This document describes the different types of WAN and LAN access interfaces and

protocols supported by the Mediant MSBR. It provides a description of the CLI commands

necessary to configure the type of access as well as typical configuration examples.

Configuration Guide 8 Document #: LTRT-31668

WAN & LAN Access Interfaces

This page is intentionally left blank.

Version 7.2 9 WAN & LAN Access Interfaces

Configuration Guide 2. Wireless WAN Cellular Interface

2 Wireless WAN Cellular Interface

The MSBR supports 3G and 4G Long-Term Evolution (LTE) WAN cellular interface. This

support is provided by the following:

Third-party cellular modem provided as a USB dongle that is plugged into the MSBR's

USB port.

Integrated cellular modem for 3G or 4G LTE. Note that in this model, the MSBR's USB

port is reserved for use by a USB storage stick.

Cellular WAN interface can serve as a primary WAN interface or as a backup WAN interface

for another primary WAN interface (e.g., ADSL).

The cellular WAN interface can operate in one of the following connection modes:

Point-to-Point Protocol (PPP) mode: If the external USB dongle uses serial

communication technology, it exposes an internal serial interface (tty) to the MSBR. In

this case, the cellular WAN interface acts as a PPP-type interface, acquiring its IP

address from the cellular provider using Internet Protocol Control Protocol (IPCP).

Dynamic Host Configuration Protocol (DHCP) interface mode is a name for all USB

modem technologies exposing an internal Ethernet interface to the MSBR (also known

as Communications Device Class / CDC Ethernet), as opposed to the serial PPP. The

cellular WAN interface acts as an Ethernet device acquiring its network address using

DHCP.

Note:

•The integrated cellular modem is applicable only to Mediant 500L MSBR.

•The integrated cellular modem supports only the DHCP mode.

•DHCP mode does not support PIN code protection for the USB dongle modem.

(The integrated cellular modem does support PIN code protection.)

•For the USB dongle modem, the cellular interface connection mode is according to

the modem technology.

•Cellular WAN interface is supported only if the MSBR's installed License Key

includes the cellular WAN interface license.

•Cellular WAN interface is not configured by default. However, any dongle plugged

into the USB port will be powered on and recognized by the MSBR (but network

connectivity will occur only once configured).

Prior to configuration, it is recommended to do the following:

1. (USB dongle cellular modem only) Check the mode of operation (PPP or DHCP)

according to the manufacturers specifications (Linux) and then configure the modem

accordingly.

2. Verify SIM connectivity with the cellular network using another device (e.g.,

smartphone). This verifies that the SIM has been activated and that the PIN code (if

relevant) is correct.

3. (USB dongle cellular modem only) Check that the MSBR supports your modem, by

using the command debug usb-3g devices. The output of this command must include

"Driver=<mode type" (e.g., "Driver=cdc-ether").

When plugged into the MSBR for the first time, some USB dongle modems usually act like

a flash storage initially and then once identified by the MSBR, switches to the modem.

When you plug the cellular modem into the MSBR, the MSBR immediately installs drivers.

After the MSBR successfully installs the driver, it configures the cellular interface

automatically (but not completely).

Configuration Guide 10 Document #: LTRT-31668

WAN & LAN Access Interfaces

Cellular WAN interface is configured under the following command:

(configure-data)# interface cellular 0/0

(conf-cellular)#

This command set provides the below commands:

CLI Command Default Description

mode {dhcp|ppp} ppp Defines the cellular mode, which can be modem serial port

(PPP) or DHCP Ethernet port.

[no] shutdown

shutdown

Brings the connection up or down.

[no] backup (no) Enables WAN backup mode, whereby the cellular connection is

used only when the primary WAN interface fails.

[no] pin <code>

(none)

Defines the PIN code to unlock the SIM card.

mtu (auto) Defines the Maximum Transmission Unit (MTU) of the cellular

interface. The value is usually negotiated automatically.

adv - Enables MSBR to check if it can operate with a new cellular

modem that is not supported by default.

modem-details default-product-id: USB device type

that the MSBR operates with when new mode is

plugged in to USB port

modem-details modem-product-id: The new USB

target product-id when used as a modem

modem-details vendor-id : The new USB modem type

vendor ID

option-enable: Enables the modem to work with the

serial driver (depending on the modem technology).

usb-modeswitch enable: Switches to new modem

according to the modem-details given.

Note: If you wish to operate with a new modem, please contact

AudioCodes to officially approve the new modem.

crypto {map|vpn-

client|vpn-server}

Defines encryption-decryption.

firewall enable

Enables the firewall.

DHCP Commands

profile

(cell-profile-

config)#

{apn|obscured-

pass|password|user

}

Defines a profile for DHCP modems:

apn: Defines the APN

obscured-pass: Defines the obscured password

password: Defines the password

user: Defines the username

Note: This command is applicable only to the integrated

cellular modem.

PPP Commands

initstr AT&F Defines the initialization string for the modem. The default string

AT&F restores factory defaults.

apn uinterne

Defines the Access Point Name (APN) used by the cellular

operator.

phone *99# Defines the phone number for the dial-up data service. Most

networks use the default *99#.

Version 7.2 11 WAN & LAN Access Interfaces

Configuration Guide 2. Wireless WAN Cellular Interface

CLI Command Default Description

ppp user

obscured-pass

(blank) Defines the username and password authentication when

using PPP on the interface.

pcui Defines the Serial User-Interface port for debugging.

[0-11] send: TTY port index and Attention (AT)

command to send

send <text>: AT command format

send AT+CSQ expect: Expect string to match

send AT+CSQ expect <text>

send AT+CSQ expect * reboot: Reboot on match

[no] napt (yes) Enables NAPT mode. This setting is mandatory unless your

service provider supports routable addresses for your LAN

hosts.

conditional-apn

(no)

Variable APN by operator name.

sms (no) Send an SMS message to verify the number of the SIM (only

when the interface is down).

tty {first|0-

11|last}

last

responsi

ve TTY

TTY is the serial port used to communicate with the Modem

(which is typically determined automatically). However, in case

the MSBR cannot communicate with the serial modem, you can

use a different serial port, set according to the Linux guide

provided by the cellular dongle manufacturer.

ppp authentication

{chap|pap|ms-

chap|ms-chap-v2}

Enables PPP authentication. No limit is placed on which

and how many authentication is used (all four can be

activated on the same interface).

pap: Password Authentication Protocol – normal login

when a connection has been made, the host sends a

username and password.

chap: Challenge Handshake Authentication Protocol –

CHAP does not have these deficiencies. With CHAP,

the authenticator (i.e. the server) sends a randomly

generated ``challenge'' string to the client, along with

its hostname. The client uses the hostname to look up

the appropriate secret, combines it with the challenge,

and encrypts the string using a one-way hashing

function. The result is returned to the server along with

the client's hostname.

ms-chap: Microsoft version of CHAP authentication.

vendor

Specific commands used by external dongles which don’t follow

the norm.

Configuration Guide 12 Document #: LTRT-31668

WAN & LAN Access Interfaces

2.1 DHCP Type Cellular Interface

Below shows typical configurations for the different cellular modes:

Typical configuration for the integrated cellular modem operating in DHCP mode:

interface Cellular 0/0

mode dhcp

ip address auto

ip dhcp-client default-route

firewall enable

napt

mtu auto

profile

apn uinternet

user myuser

obscured-pass YQwSAhcWEQgaDQ==

no ipv6 enable

no shutdown

ip dns server auto

exit

Typical configuration for the USB dongle cellular modem operating in DHCP mode:

interface cellular 0/0

mode dhcp

ip address auto

ip dhcp-client default-route

firewall enable

napt

mtu auto

no shutdown

ip dns server auto

exit

Note: When using a USB dongle modem, it usually connects automatically to the

cellular network without any required configuration (except for running the no shutdown

command, and a routing rule for the DHCP). This can be configured from the

manufacturer's Web interface when connected to a Windows host.

Version 7.2 13 WAN & LAN Access Interfaces

Configuration Guide 2. Wireless WAN Cellular Interface

2.2 PPP Cellular Type Example

The default interface mode for external USB dongles (after being dynamically created) is

PPP. If the serial drivers match the connected USB dongle, the MSBR will try to communicate

with it using AT command scripts.

Configured automatically:

(conf-cellular)# ip dns server auto

(conf-cellular)# initstr AT&F (means Restore factory settings)

(conf-cellular)# apn uinternet

(conf-cellular)# phone *99#

(conf-cellular)# firewall enable

(conf-cellular)# napt

(conf-cellular)# mtu auto

(conf-cellular)# tty last

(conf-cellular)# ip address auto

Configured manually:

(conf-cellular)# ppp user orange pass PASSWORD

(conf-cellular)# no shutdown

(conf-cellular)# pin 1111 (only if required)

(conf-cellular)# exit

# Add Default route to traffic through cellular interface:

(config-data)# ip route 0.0.0.0 0.0.0.0 Cellular 0/0

The following command displays the current status of the interface:

# show data interfaces cellular 0/0

Cellular 0/0 is Connected.

Description: 4G Cellular PPP connection

IP address negotiated using PPP is 10.170.120.150

State Time: 0:01:19

Time since creation: 0:02:25

Time since last counters clear : 0:01:19

mtu auto

napt

network wan

DNS is configured dynamic

DNS primary IP address is 82.102.139.10

DNS secondary IP address is 82.102.139.20

IPv6 is disabled

rx_packets 13 rx_bytes 594 rx_dropped 0 rx_errors 0

tx_packets 13 tx_bytes 416 tx_dropped 0 tx_errors 0

15-seconds input rate: 22 bits/sec, 0 packets/sec

15-seconds output rate: 16 bits/sec, 0 packets/sec

Tunnel destination server is (none)

Remote server IP: 10.64.64.64

ppp configuration:

username: orange, password: (not shown)

Configuration Guide 14 Document #: LTRT-31668

WAN & LAN Access Interfaces

enabled authentication methods: chap ms-chap ms-chap-v2 pap

lcp echo parameters: interval 6, fails

The following command displays all the cellular interface status:

MSBR# show data cellular status

Cellular interface status:

Modem status: UP

PPP status: UP

Cellular operator: IL ORANGE

Signal strength: -73 dBm

Roam status: HOME

KB sent: 0

KB received: 0

Packets sent: 6

Packets received: 6

Verify that the cellular installation has completed successfully, using the following command:

# show system assembly

Board Assembly Info:

| Slot No. | Ports | Module Type |

| 0/0 | 1 | WAN-Copper |

| 0/1 | 1 | WAN-Fiber |

| 0/2 | 1 | WAN-A/VDSL |

| 1 | 1-4 | LAN-GE |

| 2 | 1-4 | FXS |

USB Port 1: Manufacturer - ZTE,Incorporated, Product - ZTE WCDMA

Technologies MSM, Product Id - 0124, Vendor Id - 19d2, Type -

Cellular

USB Port 2: Empty

You can also use the cellular interface for WAN backup, as described in Section 16 on page

63.

Version 7.2 15 WAN & LAN Access Interfaces

Configuration Guide 2. Wireless WAN Cellular Interface

2.3 Debugging Cellular WAN Interface

The debugging commands are listed in the following table:

CLI Command Description

debug usb-3g devices Displays the hardware recognized by the MSBR of the plugged in USB

dongle cellular modem. The modem type is shown in the 'Vendor' and

'ProdID' fields and the serial modem driver chosen for the dongle is shown

in the 'Driver=' fields. For example:

debug usb-3g serial-

trace {cli|syslog}

Displays the serial (PPP) communication with the USB d

ongle. It shows the

AT command sequence for initialization of serial modems.

Note: The command is applicable only to USB dongle modems operating

with PPP.

show data cellular

status

Displays the status of the cellular WAN interface. For example:

show system assembly This command can be used to view the status of the integrated LTE and

SIM card. For example:

Configuration Guide 16 Document #: LTRT-31668

WAN & LAN Access Interfaces

2.4 Troubleshooting Cellular WAN Interface

The table below lists troubleshooting for the cellular WAN interface.

Issue Troubleshooting

No IP address received by

cellular interface, or cellular

interface remains down

although operational

The reason could be any of the following:

Bad Access Point Name (APN). Verify that the APN is correct

according to cellular operator site.

Authentication problem. Verify credentials are correct according

to the cellular account.

Incorrect PIN code or none configured

Bad serial port (TTY) selection

. Try changing the tty port number

(for PPP mode) according to the manufacturer's guide.

Bad SIM card. Verify on another device that the SIM card is

operational

Low reception. Check the signal strength by using the "show

data cellular status" command. Try to position the router in a

line-of-site location (window).

MSBR doesn't support USB

dongle modem by default

Contact AudioCodes support and provide them the following

information:

Full model name

Command output of the following: show run full

Command output of the following: debug usb-3g devices

Cellular interface is up and

running but no connection to

the internet

Check if there is a routing rule configured by using "show data ip

route" command.

Version 7.2 17 WAN & LAN Access Interfaces

Configuration Guide 3. PPP and PPPoE

3 PPP and PPPoE

Point-to-Point Protocol (PPP) and Point-to-Point Protocol over Ethernet (PPPoE) are

network protocols that allow data communication between two network hosts or points.

PPPoE is encapsulated in Ethernet frames. Both protocols exist at the network access layer

(also known as the data link layer). PPP can be encapsulated in a number of data link layer

protocols such as Ethernet (PPPoE).

PPP supports three types of user authentication protocols that provide varying levels of

security (CHAP/PAP/EAP).

PPPoE expands the original capability of PPP by allowing a virtual point-to-point connection

over a multipoint Ethernet network architecture, PPPoE is configured as a point-to-point

connection between two Ethernet ports. As a tunneling protocol, PPPoE is used as an

effective foundation for the transport of IP packets at the network layer.

Command Description

# configure data

Enter data configuration menu.

(config-data)# interface pppoe

[0-7 interface number]

Enter the PPPoE interface commands.

(conf-pppoe-[number])#

underlying [interface

slot/port]

Configures the interface with which the

PPPoE interface commands are

associated.

(conf-pppoe-[number])# ppp

user[user name] obscured-pass

[pass]

Configures the user and password

authentication by using PPP on that

interface.

(conf-pppoe-[number])# ppp

authentication [chap/pap/ms-

chap/ms-chap-v2]

Enables PPP authentication. No limit is

placed on which and how many

authentication is used (all four can be

activated on the same interface).

pap: Password Authentication Protocol –

normal login when a connection has

been made the host sends a username

and password.

chap: Challenge Handshake

Authentication Protocol – CHAP does

not have these deficiencies. With CHAP,

the authenticator (i.e. the server) sends

a randomly generated ``challenge''

string to the client, along with its

hostname. The client uses the hostname

to look up the appropriate secret,

combines it with the challenge, and

encrypts the string using a one-way

hashing function. The result is returned

to the server along with the client's

hostname.

ms-chap: Microsoft version of CHAP

authentication.

Configuration Guide 18 Document #: LTRT-31668

WAN & LAN Access Interfaces

Command Description

(conf-pppoe-[number])# ppp

lcp-echo [interval_sec_number]

[fails number]

PPP Link Control Protocol (LCP)

negotiates the link and PPP parameters to

dynamically configure the data link layer of

a PPP connection.

Interval option: determines how often

Echo-Request messages are sent on

idle links to check the viability and

integrity of the link.

Fails option: determines how many

echo-reply missed before announcing

that the link has been broken.

3.1 Examples

This example shows how to use PPP authentication after plugging in the cellular modem

device. You need to enter a username and encrypted password to make the cellular modem

authenticate with the server.

Figure 3-1: PPP and PPPoE Example

# configure data

MSBR(config-data)# int cellular 0/0

MSBR(conf-cellular)# ppp user user pass 012@pass

Another example is after a VDSL connection has been established, an EFM interface is

automatically configured, but you need to configure the PPPoE interface:

#configure data

(config-data)# interface EFM 0/2

(conf-if-efm 0/2)# ip address 10.3.90.26 255.255.0.0

(conf-if-efm 0/2)# desc "VDSL"

(conf-if-efm 0/2)# no shutdown

(conf-if-efm 0/2)# exit

(config-data)#int pppoe 0

(conf-pppoe-0)# ppp user user@ISP pass PASSWORD

(conf-pppoe-0)# ppp authentication chap

(conf-pppoe-0)# ppp authentication ms-chap

(conf-pppoe-0)# ppp authentication ms-chap-v2

(conf-pppoe-0)# ppp authentication pap

(conf-pppoe-0)# ppp lcp-echo 6 5

(conf-pppoe-0)# underlying EFM 0/2

(conf-pppoe-0)# no shutdown

(conf-pppoe-0)# exit

(config-data)# ip route 0.0.0.0 0.0.0.0 EFM 0/2

USB 3GCellular Modem

MSBR

Version 7.2 19 WAN & LAN Access Interfaces

Configuration Guide 4. ADSL/VDSL

4 ADSL/VDSL

Asymmetric Digital Subscriber Line (ADSL) is a technology for transmitting digital information

at a high bandwidth on existing phone lines to homes and businesses. ADSL is asymmetric

in that it uses most of the channel to transmit downstream to the user and only a small part

to receive information from the user.

ADSL is generally offered at downstream data rates from 512 Kbps to about 6 Mbps. It uses

standard telephone lines to upload and download data on a digital frequency, which sets

these data streams apart from the analog signals that telephones and fax machines use. The

telephone can be used at the same time when surfing the Web with DSL service because

the signal is operating on a different frequency.

Very-high-bit-rate digital subscriber line (VDSL or VHDSL) is a digital subscriber line (DSL)

technology providing data transmission faster than ADSL over a single flat untwisted or

twisted pair of copper wires (up to 52 Mbit/s downstream and 12 Mbit/s upstream), using the

frequency band from 25 kHz to 12 MHz. These rates mean that VDSL is capable of

supporting applications such as high-definition television, as well as telephone services

(voice over IP) and general Internet access, over a single connection.

The MSBR will set the modem to use ADSL or VDSL automatically by sensing the signals

on the wire. It is not possible and not required to set ADSL or VDSL manually.

To configure ADSL mode use these commands:

Command Description

# configure data

Enter data configuration menu.

(config-data)# interface dsl

slot/port

Enter the physical DSL port.

(conf-if-dsl slot/port)# no

shutdown

Shutdown is default configuration for this

kind of port; use it to enable the DSL

interface.

# show data interfaces dsl

slot/port

Displays DSL interface information such

as: current configuration, downstream and

upstream bandwidth and status

(connected, disconnected).

Configuration Guide 20 Document #: LTRT-31668

WAN & LAN Access Interfaces

4.1 ADSL Examples

In this example, MSBR connects to the Internet Service Provider using ADSL mode.

Figure 4-1: ADSL Example

# configure data

(config-data)# interface dsl 0/0

(conf-if-dsl 0/0)# no shutdown

Once the DSL port senses that it is connected to ADSL, the ADSL mode is automatically

selected and the show command displays the status of the interface:

# show data interfaces dsl 0/2

Hardware is ADSL/VDSL-WAN mezzanine, rev 1 on slot 0/2

Capabilities: CPE termination. ADSL Annex A/J, VDSL2

Framer XWAY VRX268 Firmware ver 1.5

DSL Link Info

Configuration: mode adsl, no shutdown

Line Termination: CPE, Annex: A

DSL mode: ADSL2+ (ITU-T G.992.5)

Status: Connected

Downstream info

Data rate (bps): Maximum Attainable 26488000/ Actual 26488000

Power 10.2, Line Attenuation 0.0, SNR Margin 10.6

Upstream info

Data rate (bps): Maximum Attainable 1239000/ Actual 1236000

Power 12.4, Line Attenuation 0.0, SNR Margin 6.0

Performance Monitoring

Current 15-min interval statistics (Assessed seconds: 67):

NearEnd - UAS: [ 39], ES: [ 0], SES: [ 0], LOSS: [ 0], LOFS: [ 0],