ALU 7360 5520_gpon_basic_configuration

2
COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
At the end of this session, you will …
• know what functions the NGLT-x is performing
• be capable to configure ONTs
Objective

3
Table of Contents
1. PON provisioning
2. ONT Software Management
3. ONT provisioning
1. Basic ONT provisioning
2. ONT pre-provisioning
4. ONTCARD provisioning
5. ONTENET provisioning
6. Bridge port configuring
7. Basic GPON QoS
8. Hands-on

4
Remember this?
0

5
Provisioning tools – TL1 and CLI
• TL1 – Transaction Language number 1
- for the provisioning of the GPON transport layer
- lt equipment provisioning can also be done using CLI
- pon, ont, … up to ontenet provisioning can be done using TL1
• CLI – Command Line Interface
- for provisioning the ihub
- as well as the services/facilities on iacm

6
TL1 based hierarchical breakdown + Identification
rack
shelf
pon
ont
ontenet
lt
ontcard
LT-1-1-5
PON-1-1-5-2
ONT-1-1-5-2-12
ONTCARD-1-1-5-2-12-1
ONTENET-1-1-5-2-12-1-1
SHELF-1-1
RACK-1

7
Prepare the system for accepting HiCAP boards
configure system
max-lt-link-speed
link-speed forty-gb
[save IHUB database - requires a reboot]
configure system
security
profile admin
slot-numbering type-based
logout and login again to actually apply this change
TL1-style of numbering

8
PON provisioning
1

9
PON functions
• transport traffic
- GEM encapsulated
- ethernet frames
• polling for new ONTs
- based on ranging
- configurable polling freq.
• BER measurements
- BIP field in PCB
- configurable meas. period
BER
10-5
10-9
no alarm
signal degraded
signal failed
configurable

10
Provision PON – AMS
• PON is automatically created when you create
the board
- you can only modify it
• select node (NE)  rack  subrack  slot 
pon port  unlock
- save

11
Provision PON – CLI
Configure pon interface 1/1/1/2 admin-state up
- the (downstream) laser is activated
- ONTs which are connected/powered on start ranging
- this generates an alarm
minor alarm occurred for pon 1/1/1/2 : SERNUM = ALCLF9A0F50D, SLID = 12345
• PONs are created at LT creation time
- state  admin-state down

12
Provision PON – CLI
Configure pon interface 1/1/1/2
- Label -> name of the PON, string with length <= 80
- Ber-calc-period -> BER measurement period (unit 1/10 sec)
- Polling-period -> polling period for ONTs (unit 1/10 sec)
- Sig-degrade-th -> signal degraded threshold [4…10]
- Sig-fail-th -> signal failed threshold [3…8]
- Fec-dn -> Forward Error Detection for downstream (enable/disable)
- Raman-reduct -> Raman Reduction (enable/disable)
- Closest-ont -> distance of closest ONT [0 … 40km]

13
ONT Software Management
2

14
ONT Software flow
ONT
ISAM
ONT
AMS
FTP
DownloadDownload passive
Download active

15
ONT software banks
active bank
passive bank
RAM
planned software  what you intend to run in RAM
active sw  what is actually running in RAM
passive sw  what is in the passive bank
active bank:
what the ONT
tries to boot up with
if the ONT fails to
boot with what is
in the active bank
it will use the
passive bank
if the active software is different from the planned, the P-OLT tries
to download the planned software to the passive bank

16
ONT software banks
• Active and Passive banks can only be accessed via OMCI
- ONT must be in the “unlocked” state
• If Active and Planned SW are misaligned, a minor alarm is generated (CFG : SW
Version mismatch)
- ONT will not be operational as long as this alarm is active
- Copy/Paste Active SW into Planned SW field to get rid of the alarm.
m

17
ONT SW related alarms
• SWDLFAIL
- SW Download Failed
- Something went wrong with the download process
• SWACTFAIL
- SW Activation Failed
- Downloaded SW could not be activated on the ONT
• SWDLFILE
- File missing or file error
- The SW file string mentioned in the SWVERPLND doesn’t exist on the P-OLT
• SWDLIP (not really an alarm)
- SW Download In Progress
- SW is being downloaded from P-OLT towards the ONT over the OMCI channel
m
m
M
m

18
SW Perspective
• Download software to ISAM
• Options when using scenario 2

19
Necessary steps and scenario’s
1. FTP ONT software files to AMS server
2. Prepare ONT software files (per ONT type) on AMS server
3. Download ONT software onto NE
possible scenarios:
1. Manual sw management (basic or pre-provisioning)
2. Automatic sw management based on AMS
3. Automatic sw management based on NE

20
Step 1 : Copy ONT software from CD to AMS
• Prerequisite step
- ONT software files must be present on AMS
- directory:
- /var/opt/ams/shared/ams-<version>/ne/software/ONT
FTP
AMS

21
Step 2 : ONT Software file preparation : overview
HW version: one ONT Type can have multiple hardware implementations

22
Step 2 : ONT Software file preparation : List of Hardware Info
(OPTIONAL)
Allows to add a new type
of Hardware

23
Step 2 : ONT Software file preparation : Add ONT Load
• First select the correct ONT Type from
the hardware list
• ONT File Name: ONT software version
residing on AMS server
• Major NE SW Version: used for
automatic sw management (see later)
• Load Type: using VoIP or not?

24
Step 3 : Download ONT software to NE
- select NE(s)
- select ONT type
- select SW load

25
Step 3 : Which ONT software to use?
ONT software must be available on the NE before it can be downloaded onto the
ONT!
when you plan the SW for the ONT,
you have to add a “3’’ to the name
 3FE50853AIAA05

26
ONT provisioning
3

27
Provisioning ONTs
ONTs can be provisioned
- while already physically connected to the PON:
- while not physically connected to the PON at all:
 Pre-provisioning
 Post-provisioning

28
Provisioning ONTs (cont.)
• serial number based
- identify the ONT by its serial number
• Subscriber Location ID (SLID) based
- identify the ONT by its subscriber location id
- SLID  up to 10 characters long
- SLID is configured beforehand in the ONT
TEACHER
ALCLA0A28965
ONT not
connected?
NO ALARM
ALARM

29
Discovered ONT in case of basic provisioning
• alarm at AMS: minor
• alarm at CLI and TL1: minor
- … minor alarm occurred for pon 1/1/3/2 : SERNUM = …, SLID = …
- "PON-1-1-3-2,PON:MN,NEWONT,NSA,,,,:
CFG alarm: new ONT discovered
Serial number of ONT

30
Choosing the scenario
‘from AMS’: used for manual sw management and automatic based on AMS
‘from NE’: used for automatic sw management based on NE

31
Scenarios on ONT details
Planned software:
• ‘UNPLANNED’ -> scenario 1 and 2
• Specific version (‘3FE…’) -> scenario 1
• AUTO : automatic from NE -> scenario 3

32
ONT Post-provisioning
3.1

33
Provision ONT – Serial number based – AMS (1/3)
ONT id  1-1-3-1-64
serial
number
Network
Rack
Subrack
LT
NE
PON Port
ONT (provisioned)
Create ONT

34

35
check the SW and the status!

36
Provision ONT – Serial number based –CLI
• Configure equipment ont interface 1/1/1/2/33
- Sw-ver-pland -> software version planned (if not know, set to UNPLANNED)
- Sernum -> consists of 2 parts: <VendorID:serial_number> e.g. ALCL:A0A3F342
- Vendor ID: 4 char (e.g. ALCL for Alcatel-Lucent)
- Actual serial number : 8 char
- Subslocid -> left to its default value of WILDCARD
- Battery-bkup -> presence of battery backup
- Desc1 and Desc2 -> two description fields
- Enable-aes -> enable AES in downstream
- Admin-state -> set to up to bring In Service

37
Changing planned software version
CLI
Show equipment ont interface 1/1/1/2/33 detail
- To look up the active software version on the ONT
Configure equipment ont interface 1/1/1/2/33 sw-ver-pland ...

38
ONT Operational data
Show equipment ont operational-data 1/1/1/2/33 detail

39
ONT pre-provisioning
3.2

40
Pre-Provisioning on ONT – SLID based
once the ONT is connected to the PON
- the P-OLT records the SLID and the serial number
- automatic status change: to unlocked (in service)
this allows you to do pre-provisioning
- of the ONTCARD, services, … without the system generating any alarms!
TEACHER
connect the ONT to the PON
TEACHER
no alarm, even when the ONT is disconnected from the PON

41
Pre-Provisioning SLID on ONT
• ONT need configure SLID pre-provisioning. SLID configuration method is different
for each types of ONT.

42
Pre-Provisioning ONT – SLID based – AMS (1/2)
ONT id  1-1-3-1-64
Network
Rack
Subrack
LT
NE
PON Port
ONT (provisioned)
Create ONT
SLID

43

44
check the SW and the status!

45
Pre-Provisioning ONT – SLID based – CLI
• Configure equipment ont interface 1/1/1/2/33
- Sw-ver-pland -> software version planned (if not know, set to UNPLANNED)
- Subslocid -> Subscriber Location ID, string with maximum of 20 chars
- Sernum -> left to its default value: ALCL:00000000
- Battery-bkup -> presence of battery backup
- Desc1 and Desc2 -> two description fields
- Enable-aes -> enable AES in downstream
- Admin-state -> set to up to bring In Service

46
ONT Card provisioning
4

47
Provision ONT Card – AMS (1/2)
• example of a detected ONT Card:

48
Provision ONT Card – AMS (2/2)
• select node  …  ont 55  create  planned ont-card

49
Provision ONT Card - CLI
• The ONTs do report which ONT Cards (or ont slots in CLI) are available,
but they still need to be provisioned!
• Configure equipment ont slot 1/1/1/2/33/1
- Planned-card-type  10_100baset, pots, vdsl2, video,
ds1, e1, vdsl2pots, ethpots
- Plndnumdataports  [0…16]
- Plndnumvoiceports  [0…16]
• This will automatically provision the UNI
- but they will be in the status out of service
ShelfNT LT
PON-1
ONT33
Slot1
10_100BASET

50
Ethernet Port provisioning
5

51
Provision Ethernet Port – AMS (1/2)

52
Provision Ethernet Port – AMS (2/2)
• provision the UNI
- With AMS this also automatically creates bridge port!

53
Provision Ethernet Port - CLI
• The UNIs are automatically created during the provisioning
of the ont slot (ONT Card), they only still need to be configured!
• Configure interface port uni:1/1/1/2/33/1/1 admin-up
• you still need to provision the bridge port in the ISAM!
- See next chapter

54
Bridge port provisioning
6

55
Provision bridge port - AMS
• when the ONTENET and UNI was provisioned using AMS,
the bridge port was created automatically!
adapt bridge port settings,
if needed:
e.g. increase #MAC addresses

56
Provision bridge port
• also referred to as …
- … configuring the interworking function
• syntax:
- configure bridge port <rack/shelf/slot/port/ont/ontcard/ontenet>
• example:
- configure bridge port 1/1/3/3/33/1/1
max-unicast-mac 4
LT x
IWF
FWEngine

57
Basic GPON QoS
7

58
Ingress QoS profile: p-bits and traffic classes
• p-bit-to-queue mapping: 2-step configuration via Traffic Classes (TC)
- TC-to-queue mapping (fixed, system-wide setting)
- based on a 4 queue or 8 queue (fixed) constellation:
- p-bit-to-TC mapping (L2 FWR setting)
- ingress Profile: dot1p0  TCx1, dot1p1  TCx2, etc
TC Queue TC Queue
7 3 7 7
6 3 6 6
5 2 5 5
4 2 4 4
3 1 3 3
2 1 2 2
1 0 1 1
0 0 0 0
8 TC to 4 Queues 8 TC to 8 Queues
QO
Q7
…
TC0
TC7
…
8TC-to-8Q
mapping
Pbit-to-TC
mapping
Pbitx
Pbitz
…
QO
Q4
…
8TC-to-4Q
mapping
Pbit-to-TC
mapping
Pbitx
Pbitz
TC1
TC7
…
TC0
TC6
…

59
Ingress QoS profile: CLI configuration
configure qos profiles
ingress-qos all-in-one
dot1-p0-tc 0
dot1-p1-tc 0
…
dot1-p7-tc 0
configure vlan id 150 mode residential-bridge
(secure-forwarding)
in-qos-prof-name name:all-in-one
all p-bits are mapped to the same TC
hence all traffic enters one single queue
the p-bit mappings are actually/also needed on the ONT
they are downloaded to the ONT when provisioning the bridge port!

60
Ingress QoS profile: AMS configuration

61
Bandwidth profile: T-CONT types
- Bandwidth parameters of T-CONT define the T-CONT type
- DBA will issue grants to for the T-CONT to ensure that average rate does not exceed the maximum
of CIR, AIR and EIR
- fixed BW T-CONT type 1: rate limiting to CIR
- best-effort BW T-CONT type 4: rate limiting to EIR
Fixed
Bandwidth
Best-Effort Bandwidth
Assured
Bandwidth
Assured
Bandwidth
Non-Assured
Bandwidth
Best-Effort
Bandwidth
Non-Assured
Bandwidth
Assured
Bandwidth
Fixed
Bandwidth
CIR=AIR=EIR>0 AIR=EIR>0
CIR=0
EIR>AIR
AIR>CIR
CIR=0 CIR=AIR=0
EIR>0 EIR>AIR
AIR>CIR
CIR>0
Type 1 Type 2 Type 3 Type 4
Best-Effort
Bandwidth
Fixed
Bandwidth
EIR>CIR
CIR=AIR>0
Type 5
Fixed
Bandwidth
AIR=EIR>CIR
CIR>0
Assured
Bandwidth
T-CONT types
Type 1 Type 2 Type 3 Type 4 Type 5
CIR > 0 0 0 0 > 0
AIR = CIR > 0 > 0 0 >= CIR
EIR = CIR = AIR > AIR > 0 >= AIR

62
Bandwidth profile: CLI configuration
configure qos profiles
bandwidth CBR1000
committed-info-rate 1000
assured-info-rate 1000
excessive-info rate 1000
delay-tolerance 80
configure qos interface 1/1/5/1/33/1/1
upstream-queue 0 bandwidth-profile name:CBR1000
by default, one T-CONT will be assigned per queue,
unless bandwidth sharing is enabled!
by default, a T-CONT will have a burst
every 80 frames (every 10 ms)

63
Bandwidth profile: AMS configuration

64
Hands-on
8

65
Hands-on
• Hidden Slide, see Notes Page
• Exercises

66
www.alcatel-lucent.comwww.alcatel-lucent.com

67
www.alcatel-lucent.comwww.alcatel-lucent.com

ALU 7360 5520_gpon_basic_configuration

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to ALU 7360 5520_gpon_basic_configuration

Similar to ALU 7360 5520_gpon_basic_configuration (20)

More from Wahyu Nasution

More from Wahyu Nasution (9)

Recently uploaded

Recently uploaded (20)

ALU 7360 5520_gpon_basic_configuration