08.TAC03001-HO10-I1.3-7302 7330 5520 XDSL Basic Configuration CE

xDSL Port Configuration
During class please switch off your mobile, pager or other that may interrupt.
Document Number | Document Title 1 © 2010 Alcatel-Lucent, All Rights Reserved

Objective
At the end of the module you will be able to
explain basic parameters on the physical layer
explain how to configure xdsl, direct ethernet subscribers using CLI

and AMS.

Physical configuration of ports
Physical port configuration
Ethernet ports on xHUB XDSL/Eth ports on ASAM-CORE
on xHub on ASAM-CORE
• Ethernet ports • xDSL user ports
• Ethernet Line Termination (NELT)
• SHDSL user ports

Configuration of xDSL port
Configure xDSL physical parameters
Content
Provider Client PC
Internet ASP/ISP ISAM
ANT
xDSL
LT
NT
NT
Eth
xDSL
LT
App App
HTTP HTTP
TCP connection
TCP TCP
Public
IP IP IP IP
IP
Phys routing Phys PPP PPP
PPPoE PPPoE
802.3 802.3 802.3 802.3 802.3 802.3
LLC LLC
VLAN VLAN SNAP SNAP Phys Phys
PHYS PHYS AAL5 AAL5
ATM ATM
ADSL
xDSL ADSL
xDSL

Configuration of port via AMS
Administrative state
• Locked or unlocked NETWORK
Transfer mode
• ATM for ADSLx, PTM for VDSL2
select port
• ATM or PTM for SHDSL Actions
Assign xDSL profiles: Configure
• xDSL line service profile select or even

• xDSL line spectrum profile
create XDSL profiles
For SHDSL ports no spectrum or service profiles are used!

• All parameters can be specified when you configure a port
Operational modes of the port
• ADSL flavors or VDSLx
minimum severity for alarm reporting on the port

5
For the configuration of SHDSL ports a separate chapter is available.

PTM = packet transfer mode = Ethernet in the first mile
For NVLT-C or NVLT-D (which both support ATM and PTM), you can configure the transfer mode.
For ports on NALT boards, there’s nothing you can take the default transfer mode (which in
that case is ATM, obviously).

XDSL Profiles on NE
XDSL service profile

• Rate adaptation mode
• Net bit rates
NETWORK
• Latency characteristics
NE XDSL spectrum profile

• supported modes (ADSL2, VDSL, …)
• noise parameters, carrier masking & RFI
Infrastructure
bands
Transmission
• mode specific power & PSD parameters
XDSL
XDSL DPBO profile

XDSL XDSL XDSL • DPBO = downstream power backoff
• overrules DPBO in spectrum profile
Spectrum Service DPBO
The XDSL line spectrum profile groups all parameters on physical level. These parameters are
mainly related to the environmental conditions of the line (spectrum management).
The spectrum configuration profile contains parameters which have a common value for all
ADSLx flavors (Common) and parameters which have a specific value depending on the ADSLx
flavor used (ADSL1/2, READSL2, ADSL2Plus). The actual selected operating mode determines
which set of ADSLx specific parameters is used. In case a common parameter is not supported
for a specific ADSLx flavor, this parameter will be ignored for that flavor.
The XDSL line service profile groups all parameters on service level (data rates, delay, …). These
parameters are mainly related to the configuration of the XDSL Channel interface.
The service parameters are common for all ADSLx flavors. In case a parameter is not supported
for a specific ADSLx flavor, this parameter will be ignored for that flavor.

xDSL line profiles: Where used ?
7302/7330
ISAM
NALT
Port 1
ASAM links
Port 2
NT I/O
1-16 Port 3 xDSL line configuration
•Service profile
•Spectrum profile
Port 4
NT
SMAS NALT
ASAM links
NT I/O
1-16
ACU Port 1
Port 2
NT
Port 3
SMAS Port 4
7302
ACU
7
ISAM

Profiles & Templates
“Templates Group” “Profiles on ISAM”

on AMS
Templates
Profile 2
Profile 1 DOWNLOAD TO NE Profile 5
Profile 2 Profile 6
Profile 3
Templates Profile 4
Profile 5
Profile 6
Profile Profile x
.
.
.
Create
ISAM
Profile Profile Profile

Type x Type y Type z
As well as creating the profiles on the NE, you can create templates at AMS level.
Use the template perspective to create templates at AMS level. They can be downloaded
afterwards to NE’s or NE-groups.

Template groups
Existing template groups can be:

• deleted
Templates
• downloaded to NE
Groups
• removed from NE
Create template group • renamed
• merged
A template group can contain several types of profiles. Whenever you create e.g. an XDSL
service profile, you have to specify to which template group it belongs.
You can download a template group to an NE or even to an NE group.

Create new template
Templates
Templates
Templates
Templates

select template / version
Create template
• create NE specific template
• clone to new version
• delete
• put into group
• upgrade on NE
• download to NE
• remove from NE
10
XDSL service profile template create NE specific template (in order to specify parameters
see screenshot further in this presentation)

Download template group to NE or NE group
Groups download to NE
• Select NE groups
• Select NE’s
11

Discover templates on NE
Upload templates from NE to AMS
NETWORK
select NE
Templates
Discover templates
12
Result is shown afterwards:

xDSL line service profile
Configuration of:
• Rate adaptation mode
• Net bit rates
• Latency characteristics
o max. interleaving delay
o min. INP
o Erasure detection
13
The defined interleaving delay will determine the interleaving depth (also taken into account is
the actual line rate). These decisions are taken by the xTU-C (in the DSLAM).
Reed-Solomon coding is used for impulse noise protection. In the xDSL line spectrum profile you
can fill in how many symbols may be affected by a noise burst without causing unrepairable
damage. This parameter will also have effect on the interleaving depth.
Most bursts of noise affect less than one DMT, but it is possible that a burst is longer (e.g. from
4 to 10 DMT symbols). If you fill in a value of 2 symbols to be protected, you already have a
good protection for data traffic (for video, it is recommended to have a minimum INP of 4 DMT
symbols). You don’t need to introduce too much delay (e.g. max. 8 or 16 ms is sufficient).
Obviously, the INP parameter is related to the interleaving delay.
When you fill in the bit rate values, there’s no link to which xDSL is used, so you’ll have to pay
attention to what port it will be applied (ADSLx, ADSL2+ & VDSL)!

What is erasure detection?
It is a mechanism to detect erroneous bytes in the Reed-Solomon codewords. If that
mechanism would work perfectly, it would mean that the Reed-Solomon overhead bytes can
be used for error correction only (that way doubling the amount of bytes that can be
corrected!). Unfortunately, the technology is not field proven yet. It would be dangerous to
rely on erasure detection. Maybe it works fine, but it is also possible that it only detects a few
erroneous bytes and it leaves some for Reed-Solomon to detect. (In the worst case, it would
even tell that a correct byte is erroneous!)
Alcatel-Lucent recommends that you don’t rely on erasure detection. This means that the
modem will at least try to reach the requested delay and INP value without erasure detection.
The modem can still choose to use erasure detection but this will then provide a higher INP. If
the modem is allowed to rely on erasure detection, it will use this mechanism to reach the
requested delay and INP value. Erasure detection is covered in more detail in the VDSL2
module.
More details in part 2 of the operator course

xDSL line spectrum profile: modes
Defines allowed modes on the port

• ADSL ... VDSL2
15
It is better to allow all VDSL2 profiles and restrict specific operational parameters via the other
configuration tabs. Like this you might avoid that a modem doesn´t want to enter showtime
because it couldn´t support the requested profile. By allowing all VDSL2 profiles you avoid this
…

Overview of the new standards
G.dmt = G.992.1 = ADSL

ITU-T
G.dmt = G.992.1 G.dmt.bis = G.992.3 = ADSL2

= current ADSL
• better performance
• loop diagnostics
• improved initialization & fast start-up
G.dmt.bis = G.992.3
= ADSL2
• power management
• …
G.adslplus = G.992.5 = ADSL2+
• More downstream bandwidth
G.adslplus = ∆ on G.992.3 o (spectrum 2.2 MHz)
= ADSL2+
• up to 24 Mbps / at least 16 Mbps
READSL2 = G.992.3 annex L
= Reach Extended ADSL2
READSL2 = Annex L G.992.3
• Reach Extended ADSL2
16
The G.dmt = G.992.1 standard describes the current ADSL technology.

The ADSL2 G.992.3 and G.992.4 standards, approved by the International Telecommunication
Union, improve data rate and reach performance, dynamic rate adaptation and diagnostics,
and include a power-saving standby mode as well.
ADSL2+ (G.992.5), more than doubles the downstream data rate of ADSL to 16 Mbit/sec, but
extending the frequency spectrum from 1,1Mhz to 2,2Mhz.
ADSL2 addresses the growing demand for bandwidth to support services such as video. ADSL2
and ADSL2+ gear will interoperate with existing ADSL equipment, allowing carriers to roll out
new high-speed services while gradually upgrading their legacy infrastructure.
Reach Extended ADSL2 (READSL2), which is annex L of ADSL2 (G.992.3), results in an increase in
reach of about 600 meters. With ADSL the reach was limited to an average of 5,4km. With
READSL2 this is extended up to 6km (for 0,4mm loops). This is done by adapting a specific PSD
(Power Spectrum Density) where the lower carriers of the downstream data are given a bit
more power, while the higher carriers are not used. The result is an overall lower bitrate,
allowed over a longer loop length, without needing a higher overall power.
For completeness, we also refer to the ADSL lite versions.
The lite version for the current ADSL is defined as G.lite or G992.2
For ADSL2 the lite version is defined as G.lite.bis or G.992.4

Some examples of ‘new’ annexes: Annex I, J and M
Annex A
POTS
UP DOWN
138kHz 1.1 MHz
Annex B
ISDN
UP
DOWN
120kHz 276kHz
Annex I
UP DOWN
All digital
Annex J
UP DOWN
Annex M
POTS
UP
UP DOWN
17
Annexes I and J are for all digital operation (full digital loop), while Annex M is over POTS.
Mnemonic: M = More upstream
up to tone 64
US masks similar to ADSL2 Annex J, but over POTS
Estimated US bitrates up to 3 Mbps
For Annex L (READSL2), there’s a dedicated section (see further).

ADSL2+ doubles the frequency spectrum
18
While the current ADSL standard (G.992.1) specifies a downstream frequency band up to 1.1
Mhz, ADSL2+ specifies a downstream frequency up to 2.2 Mhz. The result is a significant
increase in data rates on shorter phone lines.

Noise margins
for SRA only
19
SRA: Seamless Rate Adaptation
You specify a minimum noise margin, target noise margin and maximum noise margin.
The configured value for the maximum noise margin can be any value from 0 dB until 31
dB. The value of 51.1 dB means that there’s no limit.

DSL Line Profiles: SNR/QAM relationship
Relation between the SNR and the max. QAM.

(QAM is directly linked to the line rate)
To obtain a certain speed we need a min. SNR!
Bits/symbol QAM Signal/Noise ratio (dB)
for BER<10-7
4 QAM-16 21,8
6 QAM-64 27,8
8 QAM-256 33,8
9 QAM-512 36,8
10 QAM-1024 39,9
12 QAM-4096 45,9
14 QAM-16.384 51,9
15 QAM-32.768 54,9
20
Another way to look at the MinNM (= minimum noise margin):

A minimum noise margin >0 results in rescaling the third column of above table: e.g., if QAM-64
is assigned at SNR=SNRtable + MinNM, this means that the BER will decrease from 10-7 to a
lower value.
For ADSL on the carriers (1 to 255) we use Quadrature Amplitude Modulation (QAM). At startup
for each carrier the SNR is determined and the target noise margin (TNM) of 6dB is subtracted.
The resulting SNR is used to determine the maximum QAM we can use on that carrier.
In the ADSL course we have seen that for the data layer there are 4000 symbols per second.
So assume in the downstream direction we use at startup 200 carriers and the ATM rate
requested by the operator is 3,2Mbps per second.
With this we can calculate the average SNR needed.
Number of bits per symbol needed for 3,2Mbps 3,2M / 4000 = 800 bits
With 200 carriers this is an average of 4 bits per carrier (800/200)
To be able to get 4 bits on a carrier we need at least a SNR of 21,8dB per carrier. This is
not taken in account the TNM at startup.
With the TNM of 6dB we need so a SNR of AT LEAST 27,8 dB per carrier at startup.
This small calculation shows you the relation between the SNR and the requested line rate. This
calculation does not take into account the overhead generated by Trellis and Reed Solomon.

Noise margin parameters
SNR (dB) S1 = SNR for max. output power at startup

NM (dB)
STARTUP SHOWTIME
S2 = SNR needed for startup= S0 + TNM
S1 SNR measured at
startup (Pmax) S3 = SNR at startup = S2 + MANM
S3
MAX. Adjust output power

NOISE
MARGIN
(MaxNM)
S2 6dB
TARGET
NOISE
MARGIN
(TNM) MINIMUM NOISE MARGIN !
(MinNM) >1’: RESET
S0
t (s)
SNR needed for the configured line rate
21
In the ADSL line profile the maximum additional noise margin is used.
In the xDSL line spectrum profile the maximum noise margin is used.
ADSL1 modems always adjust their power settings in order to reach the maximum noise
margin whenever possible.
ADSL2(+) modems can do power savings and may go for a lower noise margin (no matter
what you configure as a maximum noise margin!)

xDSL Spectrum profile: carriers
Enable/disable carriers
• Not applicable for VDSL
Used carrier range

• Depends on actual operating mode
22
NSCds/us is the highest subcarrier that can be transmitted in the DS/US direction and depends
on the actual operating mode as illustrated below
Carrier masking is NOT applicable for VDSL.
DS = downstream = out
US = upstream = in
NSCds NSCus
ANSI T1.413 256 32
G.992.1 Annex A 256 32
G.992.1 Annex B 256 64
G.992.2 Annex A 128 32
G.992.3 Annex A 256 32
G.992.3 Annex B 256 64
G.992.3 Annex L (READSL2) 256 32
G.992.3 Annex M (Extended US ADSL2) 256 64
G.992.5 Annex A (ADSL2+) 512 32
G.992.5 Annex B 512 64
G.992.5 Annex M (Extended US ADSL2+) 512 64

xDSL spectrum profile: RFI (Hamming bands)
International amateur radio bands

(HAM)
Define modem behavior (PSD) for Band start Band stop Band stop
radio bands
ETSI/ITU/ANSI ETSI/ITU ANSI
kHz kHz kHz
1810 2000 2000
3500 3800 4000
7000 7100 7300
10100 10150 10150
14000* 14350* 14350*
18068* 18168* 18168*
21000* 21450* 21450*
24890* 24990* 24990*
28000* 29100* 29700*
23
For each RFI Band, the RFI type, egress control and the ingress level is specified.
The ingress level and RFI type are specified for information of the XDSL modem subsystem such
that it can be taken into account at initialization.
RF Band: [start frequency, stop frequency]
frequency: 0 – 12000 kHz
RFI Type:
HAM
AM (not included in standard)
Only HAM band support is defined in the standard. As HAM & AM are 2 different types of
signal modulation they will also behave differently PSD wise. So if the modem also supports
AM RFI signal types this might mean a different manipulation of the PSD mask in that
region.
HAM bands are standardized worldwide, but there are local differences.
In the XDSL line spectrum profile you can define 8 hamming bands. Default there are 4,
but you can create new ones (modify).
The fact that all this information can be provided means that it’s also part of the MIB and that it
can be signaled to the xDSL modem. The xDSL modem can then take appropriate actions based
upon this information. (philosophy: the more information we provide the better, what the
modem actually supports is another story)

RFI details: Egress vs. ingress
Egress control notched

PSDdBm/Hz
-60
or …
< -80
f1 f2 fMHz
• Notched: adapt PSD mask to –80dBm/Hz for that range
Ingress control
• Operator informs modem of possible disturbance level of RFI bands
• Modem could decide not to charge those frequencies too heavily
24
Egress control:
Notched: PSD level will be reduced below -80 dBm/Hz
No control: no notching required for that band
Ingress level:
Low: ingress level can be neglected
Weak: expected ingress level is weak (at -30dBm@LT / -20dBm@NT)
Strong: expected ingress level is strong (at -10dBm@LT / 0dBm@NT)
Egress and ingress can be activated separately.

By choosing egress notched the PSD mask is forced to at least –80dBM/Hz in that RFI band
region.
By specifying an ingress level for a RFI band we inform the modem of a possible disturbance
by the RFI on his receivers (see above). With this information the modem can decide not to
charge too heavily the frequencies in that band, as sudden noise could appear in that
range. In other words the modem could act pro-actively instead of reacting to sudden
disturbance in that frequency band. In fact the modem could increase the noise margins in
two ways :
by choosing a lower QAM
by emitting more power (there are limits to this: PSD.)

Although the result of egress and ingress control might result in something similar on the line
(lowering the PSD mask) the cause for it is different.
Egress > disturbance of the xDSL line on the HAM/AM band
Ingress > disturbance of the HAM/AM band on the xDSL line

Port configuration via CLI
. Configure profiles
• configure xdsl spectrum-profile <index> … DSL ports on ASAM-CORE
• configure xdsl service-profile <index> …

. Configure xDSL profiles
xDSL service profile (256)
. Configure physical parameters of xDSL line xDSL spectrum profile (256)
• Assign profiles to the port:
• configure xdsl line rack/shelf/slot/port . Configure xDSL line

service-profile <index>
spectrum-profile <index>
. Configure xdsl interface

. Configure xDSL-line
• configure interface port xdsl-line: rack/shelf/slot/port interface
25
Configure physical parameters of xDSL line

configure xdsl line racknumber/shelfnumber/slotnumber/portnumber
service-profile <profile index> ( range: [1...256] )
spectrum-profile <profile-index> ( range: [1...256] )
Optional parameters
tca-line-threshold
(no) op-mode <operational mode>
(no) carrier-data-mode <mode>
(no) admin-up
. Configuration of xdsl interface

configure interface port xdsl-line: racknmbr/shelfnmbr/slotnmbr/portnmbr
Optional parameters
(no) admin-up
(no) dis-link-updown-trap
(no) user <ExtCustomerId>
(no) severity <ExtAlmReportingSeverity>
Configuration of management parameters of the interface

Interworking configuration

Configuration of interworking
Logical flow Configure ATM TP (for ADSLx only)

configuration • VPI/VCI value
• AAL 5 parameters
. Configure ATM TP Configure Ethernet interworking point.

(only for ADSL flavors) • Configuration of bridge port
o With default parameters
• No VLAN association
. Configure Ethernet o Only necessary in case of L2 forwarding
interworking point on LT o mode on that particular port
27
AMS configures interworking function

For ADSL flavors:
Bridge port after creation of ATM TP
For VDSL2:
after configuration of the XDSL port (no further action is required. Only configure XDSL
and the interworking function is created automatically)
For Eth Line (NELT):
at creation of Bridge Port (On a NELT board, no ports need to be configured, but you
need to create an Ethernet to Bridge port on each port.)

Configuration of ATM termination point via AMS (ADSLx)
Network
Go to XDSL port – ATM itf
Create
VCL
28
ATM = Asynchronous Transfer Mode

VCL = Virtual Connection Link

Configuration of interworking via AMS for ADSLx
For ADSL flavors:

• Bridge port after creation of ATM TP
Network
Go to VCL interface
Create
•VCL to bridge port

•PPP CC port
•VCL to IPoX
•IPoA CC port
29

Configuration of interworking via AMS for P2P Eth
For Eth Port (NELT):

Network
• create Eth. to bridge port
Go to Eth. port on NELT
Create
•Eth to bridge port
30
You create an Ethernet to bridge port with default settings. The result after configuration looks
like this:

Configuration of interworking via CLI (1/2)
Configure ATM TP
• Only in case of ADSL flavors
configure atm pvc <rack/shelf/slot/ port:VPI:VCI)> aal5-encap-type < …>
Content
Client PC
Provider
Internet ASP/ISP ISAM
ANT
xDSL
LT
NT
NT
App
Eth App
xDSL
LT
HTTP HTTP
TCP connection
TCP TCP
IP IP IP
Public IP
IP
Phys routing Phys PPP PPP
PPPoE PPPoE
802.3 802.3 802.3 802.3 802.3 802.3
LLC LLC
VLAN VLAN SNAP SNAP Phys Phys
PHYS PHYS AAL5 AAL5
ATM ATM
31 ADSL ADSL
How to configure the ATM TP via the CLI
configure atm pvc (rack/shelf/slot/port:VPI:VCI) aal5-encap-type (type)

llc-snap ! logical link control encapsulation bridged protocol
llc-snap-routed ! logical link control encapsulation routed protocol
llc-nlpid ! logical link control encapsulation pppoa protocol
vc-mux-bridged-8023 ! virtual channel multiplex bridged protocol
vc-mux-routed ! virtual channel multiplex routed protocol
vc-mux-pppoa ! virtual channel multiplex pppoa protocol
automatic:<...> ! automatic detection of encapsulation type
Optional parameters:
[no] admin-down : disable traffic flow

Configuration of logical flow via CLI (2/2)
Configure Ethernet interworking point

• ADSL-flavors:
o configure bridge port <rack/shelf/slot/port:VPI:VCI>
• VDSL / Eth Line:
o configure bridge port <rack/shelf/slot/port>
x/Eth x/Phys layer x/Eth
LT x
EFM / Logical
user port
FW Engine
ASAM link
LT Y
IWF PVC / Logical
user port
FW Engine
x/Eth x/ATM/Phys. Layer x/Eth

32
In case of an IPoA or PPPoA encapsulation on the DSL line no bridge port is needed. More details
covered when we will discuss IPoA and PPPoA respectively.

Exercises - Questions

Basic equipment setup
With the Alcatel-Lucent 5520 AMS
And with the full CLI
Retrieval of equipment information
Perform these exercises with CLI and AMS unless specified differently
There is no way that you can physically go to the ISAM. How can you retrieve the
HW type of the shelf that you are working on? (NFXS-x, … )
Via AMS:
Via Full CLI:
Without going physically to the shelf, how can you see if there is an NT I/O
inserted in the ISAM?
Via AMS:
Via Full CLI:
How many boards are configured on the ISAM?

Via AMS:
Via Full CLI:
5 Which boards are actually inserted in the ISAM?

Via AMS:
Via Full CLI:
6 Find the inventory/FPBA code of one of the boards physically inserted in the
shelf. How do you find this information?
Via AMS:
Via Full CLI:.

Retrieving port /connection information
Ask the teacher which board and ports to use for the retrieval
exercises!
1 Which xDSL line profiles are present on the ISAM?
Via AMS:
Via Full CLI:
2. Which ports are configured on your board?

Via AMS:
Via Full CLI:
3. Which XDSL line profiles are installed on your user port – Training-a?
Via AMS:
Via Full CLI:
4. Which line rates are configured on your port?

Via AMS:
Via Full CLI:
5. What is the minimum alarm severity reported on your port?

Via AMS:
Via Full CLI:
6. How many ATM-connections are configured on the xDSL-port Training-a?

Display a list of all VP/VCs used on your port. How did you find this
information?
Via AMS:
Via Full CLI:

7. Which xHUB Ethernet ports are configured on the ISAM?
Via AMS:
Via Full CLI:
8. What is the configuration of network port 1?

Via AMS:
Via Full CLI:
You are not able to physically access the ISAM. How can you verify if your Ethernet
ports are up?
Via AMS:
Via Full CLI:
Basic configuration of ISAM

Ask the teacher which board and ports to use for the configuration
exercises!
1. Create an EBLT-C/NALT-C board in one of the free slots via the AMS/CLI.
What are the default settings? Verify your configuration on CLI/AMS.
Via AMS:
Via Full CLI:

2. Configure 2 ports, port x and port x+10, on the board assigned to you by the
teacher, so that they will operate in the following conditions.
- Operational mode: ADSL2+
- Upstream synchronizing at 350 kbps
- Downstream synchronizing at 7 Mbps
- Provide customer id to your liking
- For other parameters keep default profile settings. Use your own profiles!
Configure port x with AMS
configure port x + 10 with CLI
Only port x has a modem physically connected. Make sure that on that port the
modem synchronizes!
Note: x=ADSLx
Via AMS:
Via Full CLI:
From now on perform the exercises on the port where the modem is
connected. (= port x )
3. How do you know if the modem is synchronized?

Via AMS:
Via Full CLI:
4. What is the physical bit rate at which the modem is synchronized?

via AMS
Via Full CLI:

5. On the port where the modem is attached to, create an ATM termination point
using VPI/VCI value 8/35, encapsulation type LLC/SNAP for IPoE/PPPoE, with
AMS.
Via AMS:
Create an ATM termination point using VPI/VCI value 8/36, encapsulation type
LLC/SNAP for IPoE/PPPoE, with CLI.
Via Full CLI:

www.alcatel-lucent.com
www.alcatel-lucent.com
39

08.TAC03001-HO10-I1.3-7302 7330 5520 XDSL Basic Configuration CE

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

08.TAC03001-HO10-I1.3-7302 7330 5520 XDSL Basic Configuration CE

Uploaded by

Copyright:

Available Formats

xDSL Port Configuration

Document Number | Document Title 1 © 2010 Alcatel-Lucent, All Rights Reserved

At the end of the module you will be able to

explain basic parameters on the physical layer

explain how to configure xdsl, direct ethernet subscribers using CLI

Document Number | Document Title 2 © 2010 Alcatel-Lucent, All Rights Reserved

Physical port configuration

Ethernet ports on xHUB XDSL/Eth ports on ASAM-CORE

• Ethernet Line Termination (NELT)

• SHDSL user ports

Document Number | Document Title 3 © 2010 Alcatel-Lucent, All Rights Reserved

Configure xDSL physical parameters

Document Number | Document Title 4 © 2010 Alcatel-Lucent, All Rights Reserved

• ATM or PTM for SHDSL Actions

Assign xDSL profiles: Configure

• xDSL line service profile select or even

For SHDSL ports no spectrum or service profiles are used!

minimum severity for alarm reporting on the port

For the configuration of SHDSL ports a separate chapter is available.

Document Number | Document Title 5 © 2010 Alcatel-Lucent, All Rights Reserved

XDSL service profile

NE XDSL spectrum profile

XDSL DPBO profile

Document Number | Document Title 6 © 2010 Alcatel-Lucent, All Rights Reserved

Document Number | Document Title 7 © 2010 Alcatel-Lucent, All Rights Reserved

“Templates Group” “Profiles on ISAM”

Profile Profile Profile

Document Number | Document Title 8 © 2010 Alcatel-Lucent, All Rights Reserved

Existing template groups can be:

Document Number | Document Title 9 © 2010 Alcatel-Lucent, All Rights Reserved

XDSL service profile

Document Number | Document Title 10 © 2010 Alcatel-Lucent, All Rights Reserved

Document Number | Document Title 11 © 2010 Alcatel-Lucent, All Rights Reserved

Upload templates from NE to AMS

Result is shown afterwards:

Document Number | Document Title 12 © 2010 Alcatel-Lucent, All Rights Reserved

Document Number | Document Title 13 © 2010 Alcatel-Lucent, All Rights Reserved

Document Number | Document Title 14 © 2010 Alcatel-Lucent, All Rights Reserved

Defines allowed modes on the port

Document Number | Document Title 15 © 2010 Alcatel-Lucent, All Rights Reserved

G.dmt = G.992.1 = ADSL

G.dmt = G.992.1 G.dmt.bis = G.992.3 = ADSL2

The G.dmt = G.992.1 standard describes the current ADSL technology.

Document Number | Document Title 16 © 2010 Alcatel-Lucent, All Rights Reserved

138kHz 1.1 MHz

For Annex L (READSL2), there’s a dedicated section (see further).

Document Number | Document Title 17 © 2010 Alcatel-Lucent, All Rights Reserved

Document Number | Document Title 18 © 2010 Alcatel-Lucent, All Rights Reserved

for SRA only

SRA: Seamless Rate Adaptation

Document Number | Document Title 19 © 2010 Alcatel-Lucent, All Rights Reserved

Relation between the SNR and the max. QAM.

To obtain a certain speed we need a min. SNR!

Bits/symbol QAM Signal/Noise ratio (dB)

Another way to look at the MinNM (= minimum noise margin):

Document Number | Document Title 20 © 2010 Alcatel-Lucent, All Rights Reserved

SNR (dB) S1 = SNR for max. output power at startup

MAX. Adjust output power

Document Number | Document Title 21 © 2010 Alcatel-Lucent, All Rights Reserved

Used carrier range

Document Number | Document Title 22 © 2010 Alcatel-Lucent, All Rights Reserved

International amateur radio bands

Document Number | Document Title 23 © 2010 Alcatel-Lucent, All Rights Reserved