GPON basic configuration Objective At the end of this session, you - - PowerPoint PPT Presentation

gpon basic configuration
SMART_READER_LITE
LIVE PREVIEW

GPON basic configuration Objective At the end of this session, you - - PowerPoint PPT Presentation

GPON basic configuration Objective At the end of this session, you will know what functions the NGLT-x is performing be capable to configure ONTs 2 Table of Contents 1.PON provisioning 2.ONT Software Management 3.ONT provisioning


slide-1
SLIDE 1

GPON basic configuration

slide-2
SLIDE 2

At the end of this session, you will … know what functions the NGLT-x is performing be capable to configure ONTs

Objective

2
slide-3
SLIDE 3

Table of Contents

1.PON provisioning 2.ONT Software Management 3.ONT provisioning

  • 1. Basic ONT provisioning
  • 2. ONT pre-provisioning
3
  • 3. ONT pre-provisioning with automatic sw management

4.ONTCARD provisioning 5.ONTENET provisioning 6.Bridge port configuring 7.Basic GPON QoS 8.Hands-on

slide-4
SLIDE 4

Remember this?

4
slide-5
SLIDE 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
5

CLI – Command Line Interface

  • for provisioning the ihub
  • as well as the services/facilities on iacm
slide-6
SLIDE 6

TL1 based hierarchical breakdown + Identification

rack shelf pon lt

LT-1-1-5 PON-1-1-5-2 SHELF-1-1 RACK-1

6

pon

  • nt
  • ntenet
  • ntcard

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

slide-7
SLIDE 7

Prepare the system for accepting HiCAP boards configure system max-lt-link-speed link-speed twodotfive-gb

  • r

ten-gb [save IHUB database - requires a reboot] configure system

7

configure system security profile admin slot-numbering type-based

TL1-style of numbering

logout and login again to actually apply this change

slide-8
SLIDE 8

PON provisioning

1

8

1

slide-9
SLIDE 9

PON functions

transport traffic

  • GEM encapsulated
  • ethernet frames

polling for new ONTs

  • based on ranging

BER 10-5 signal degraded signal failed configurable

9
  • based on ranging
  • configurable polling freq.

BER measurements

  • BIP field in PCB
  • configurable meas. period

10-9 no alarm

slide-10
SLIDE 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
10
slide-11
SLIDE 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

11

PONs are created at LT creation time

  • state admin-state down
slide-12
SLIDE 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]
12
  • 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]
slide-13
SLIDE 13

Provision PON – TL1

ed-pon::pon-1-1-1-2:::::is;

  • the (downstream) laser is activated
  • ONTs which are connected/powered on start ranging
  • this generates an alarm
  • NEWONT ⇒ serial number + SLID

PON-1

13

PONs are created at LT creation time

  • state OOS = out of service

NT LT

slide-14
SLIDE 14

Provision PON – TL1

ed-pon::pon-1-1-1-2::::

  • label=
  • bertm=
  • pollingtm=
  • sdthresh=
  • sfthresh=

bertm – bit error rate timer (0.1 s)

fecdn= rmnreduc= closestont= is;

14

bertm – bit error rate timer (0.1 s) pollingtm – timer for polling to detect ONTs (0.1 s) sdthresh – BER threshold for signal degraded alarm [4-10] sfthresh – BER threshold for signal failed alarm [3-8] fecdn – forward error correction for downstream rmnreduc – raman reduction: enable/disable closestnont – [0km - 40km]

slide-15
SLIDE 15

ONT Software Management

2

15

2

slide-16
SLIDE 16

ONT Software flow

ONT ONT FTP

16

ONT ISAM AMS Download Download passive Download active

slide-17
SLIDE 17

ONT software banks

active bank 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

17

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

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

slide-18
SLIDE 18

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

m

18
  • Copy/Paste Active SW into Planned SW field to get rid of the alarm.

m

slide-19
SLIDE 19

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

M m

19

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

slide-20
SLIDE 20

SW Perspective

20

Download software to ISAM Options when using scenario 2

slide-21
SLIDE 21

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:

21
  • 1. Manual sw management (basic or pre-provisioning)
  • 2. Automatic sw management based on AMS
  • 3. Automatic sw management based on NE
slide-22
SLIDE 22

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
22

FTP

AMS

slide-23
SLIDE 23

Step 2 : ONT Software file preparation : overview

23

HW version: one ONT Type can have multiple hardware implementations

slide-24
SLIDE 24

Step 2 : ONT Software file preparation : List of Hardware Info (OPTIONAL)

Allows to add a new type

  • f Hardware
24
slide-25
SLIDE 25

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)

25

Load Type: using VoIP or not?

slide-26
SLIDE 26

Step 3 : Download ONT software to NE

26
  • select NE(s)
  • select ONT type
  • select SW load
slide-27
SLIDE 27

Step 3 : Which ONT software to use?

ONT software must be available on the NE before it can be downloaded

  • nto the ONT!
27

when you plan the SW for the ONT, you have to add a “3’’ to the name 3FE50853AIAA05

slide-28
SLIDE 28

ONT provisioning

3

28

3

slide-29
SLIDE 29

Provisioning ONTs

ONTs can be provisioned

  • while already physically connected to the PON:

Post-provisioning

29
  • while not physically connected to the PON at all:

Pre-provisioning Post-provisioning

slide-30
SLIDE 30

Provisioning ONTs (cont.)

serial number based

  • identify the ONT by its serial number

ALCLA0A28965 ONT not connected? ALARM

30

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 NO ALARM

slide-31
SLIDE 31

Discovered ONT in case of basic provisioning

alarm at AMS: minor

Serial number of ONT

31

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

slide-32
SLIDE 32

Choosing the scenario

32

‘from AMS’: used for manual sw management and automatic based on AMS ‘from NE’: used for automatic sw management based on NE

slide-33
SLIDE 33

Scenarios on ONT details

Planned software:

  • ‘UNPLANNED’ -> scenario 1 and 2
  • Specific version (‘3FE…’) -> scenario 1
  • AUTO : automatic from NE -> scenario 3
33
  • AUTO : automatic from NE -> scenario 3
slide-34
SLIDE 34

ONT Post-provisioning

3.1

34

3.1

slide-35
SLIDE 35

Provision ONT – Serial number based – AMS (1/3)

ONT id 1-1-3-1-64 serial number

Network

Rack Subrack NE

35

ONT id 1-1-3-1-64

Subrack LT PON Port ONT (provisioned) Create ONT

slide-36
SLIDE 36

Provision ONT – Serial number based – AMS (2/3)

36
slide-37
SLIDE 37

Provision ONT – Serial number based – AMS (3/3)

37

check the SW and the status!

slide-38
SLIDE 38

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
38
  • 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
slide-39
SLIDE 39

Provision ONT – Serial number based – TL1 (1/2)

ent-ont::ont-1-1-1-2-33 :::: btrybkup=no, berint=1000, desc1=TEACHER, desc2=ALUA, provversion=*, sernum=ALCLA0A3F342, subslocid=WILDCARD, swverplnd=3FE50854AIAA21, …

39

… btrybkup battery backup present or not berint accumulation interval for BER calculation

  • expressed in number of frames (125 µs)

desc1 and desc2 or optional free format textual descriptions sernum, the serial number, is 12 chars long, and case sensitive! the planned software version depends from model to model

slide-40
SLIDE 40

Provision ONT – Serial number based – TL1 (2/2)

fecup=disable; powershedprofileid= powershedprofilenm=

  • ntenable=
  • pticshist=

plndvar= dlsw= rffilter= uspolicemode= (local,remote)

40

uspolicemode= (local,remote) aesenable;

  • ed-ont::ont-1-1-1-2-33 :::::is;
  • is in service
  • os out of service
slide-41
SLIDE 41

Changing planned software version

TL1 ed-ont::ont-1-1-1-2-33 ::::swverplnd=…; CLI Show equipment ont interface 1/1/1/2/33 detail

41
  • To look up the active software version on the ONT

Configure equipment ont interface 1/1/1/2/33 sw-ver-pland ...

show equipment ont operational-data 1/1/8/1/44 detail

slide-42
SLIDE 42

ONT Operational data

42

Show equipment ont operational-data 1/1/1/2/33 detail

slide-43
SLIDE 43

ONT pre-provisioning

3.2

43

3.2

slide-44
SLIDE 44

Pre-Provisioning on ONT – SLID based

  • nce the ONT is connected to the PON
  • the P-OLT records the SLID and the serial number

TEACHER

no alarm, even when the ONT is disconnected from the PON

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

slide-45
SLIDE 45

Pre-Provisioning SLID on ONT

Pushbutton set

  • connect handset to POTS port 1
  • hook off, press * , dial SLID-code, press #,

hook on

Ethernet interface

  • ONT must be disconnected from PON and

powered on

ONT Make sure the ONT is disconnected from the PON and then powered on

45

powered on

  • connect PC to Ethernet port 1
  • define static IP-address of PC to 192.168.4.1
  • telnet to 192.168.4.254
  • user id / passwd

Webserver (http)

  • see next slide

ONT and then powered on

slide-46
SLIDE 46

Pre-Provisioning SLID via webserver

PON doesn’t need to be disconnnected Available information

  • product details
  • vendor name, ONT type,
  • product code, serial number
46
  • product code, serial number
  • SLID
  • hexadecimal, alphanumeric
  • PON status
  • link status (up/down)
slide-47
SLIDE 47

Pre-Provisioning ONT – SLID based – AMS (1/2)

Network

Rack Subrack NE

SLID

47

ONT id 1-1-3-1-64

Subrack LT PON Port ONT (provisioned) Create ONT

slide-48
SLIDE 48

Pre-Provisioning ONT – SLID based – AMS (2/3)

48
slide-49
SLIDE 49

Pre-Provisioning ONT – SLID based – AMS (3/3)

49

check the SW and the status!

slide-50
SLIDE 50

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
50
  • 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
slide-51
SLIDE 51

Pre-Provisioning ONT – SLID based – TL1

ent-ont::ont-1-1-1-2-33 :::: … sernum=ALCL00000000, subslocid=TEACHER, swverplnd=3FE50854AFCA10, … ;

51
slide-52
SLIDE 52

ONT pre-provisioning Automatic software management

3.3

52

Automatic software management AMS based

3.3

slide-53
SLIDE 53

Automatic software management using AMS

Building ONT Software File Preparation Table in AMS Priority: when looking for an ONT Type match, first entries with P1, then P2 and last P3 are being checked against availability on NE

53
slide-54
SLIDE 54

Object details

‘Planned Variant’ not filled in ‘Planned Software’ is set to UNPLANNED ‘Download Software’ is set to DISABLED

54

AMS will set planned software first to ‘UNPLANNED’. Upon detection of ‘software version mismatch’ alarm, the AMS will fill in the correct version.

slide-55
SLIDE 55

ONT pre-provisioning Automatic software management

3.4

55

Automatic software management NE based

3.4

slide-56
SLIDE 56

Automatic software management based on NE

When choosing ‘From NE’, the NE will be responsible for the SW Version Control Table. With each download of ONT Software towards NE, an entry will be created in the Version Control Table. Download to Passive bank

56

Download to Passive bank Download to Active bank, which will trigger a reset of ONT

slide-57
SLIDE 57

Object details

When provisioning the ONT , the AMS will set ‘planned software’ to AUTO and the ‘Planned Variant’ to DO

57

Automatic download if hardware version and planned variant has a matching entry in the ONT software control table

slide-58
SLIDE 58

ONT SW : Automatic download (HW based) ONT SW Control Management

  • Allows mass download of ONT software to ONTs that match key criteria specified in the

ONT SW Control Table (NE level)

  • The ONT SW CTRL table can have up to 250 entries
  • Table is only checked in this scenario, when planned and download software is set to AUTO
58

HWVER VARNT PLNDSWVER PLNDSWVERCONF DLDSWVER 3FE29528AAAA06 I-020G-F 3FE50782BFQA29 3FE50782BFQA29 DISABLED

For more information on this feature, check the Operation and Maintenance Guide

slide-59
SLIDE 59

Automatic ONT Software Management: from NE

Options when using NE for automatic software Management ‘From NE’

59
slide-60
SLIDE 60

Automatic ONT Software Management: from NE

60

Compare Load list on AMS with Version Control Table on NE

slide-61
SLIDE 61

Automatic ONT Software Management: from NE

61

Update Version Control Table on NE based on Load List of AMS

slide-62
SLIDE 62

ONT Card provisioning

4

62

4

slide-63
SLIDE 63

Provision ONT Card – AMS (1/2)

example of a detected ONT Card:

63
slide-64
SLIDE 64

Provision ONT Card – AMS (2/2)

select node … ont 55 create planned ont-card

64
slide-65
SLIDE 65

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]
65
  • Plndnumvoiceports

[0…16]

This will automatically provision the UNI

  • but they will be in the status out of service

Shelf NT LT PON-1 ONT33

Slot1 10_100BASET

slide-66
SLIDE 66

Provision ONTCARD – TL1 The ONTs do report which ONTCARDs are available, but they still need to be provisioned!

ent-ontcard::ontcard-1-1-1-2-33-1:::10_100baset,2,0:is; ent-ontcard::ontcard-1-1-1-2-33-2:::voice,0,2:is;

  • cardtype 10_100baset, pots, vdsl2, video,

ds1, e1, vdsl2pots, ethpots

  • planned number of data ports
66
  • planned number of data ports
  • planned number of voice ports

this will automatically provision the ONTENET

  • but they will be in the status out of service

Shelf NT LT PON-1 ONT33

Slot1 10_100BASET

slide-67
SLIDE 67

Ethernet Port provisioning

5

67

5

slide-68
SLIDE 68

Provision Ethernet Port – AMS (1/2)

68
slide-69
SLIDE 69

Provision Ethernet Port – AMS (2/2)

provision the UNI

  • With AMS this also automatically creates bridge port!
69
slide-70
SLIDE 70

Provision Ethernet Port - CLI The UNIs are automatically created during the provisioning

  • f 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
70
  • See next chapter
slide-71
SLIDE 71

Provision Ethernet Port – TL1 The ONTENETs are automatically created during the provisioning

  • f the ONTCARD, they only still need to be configured!

ed-ontenet::ontenet-1-1-1-2-33-1-1:::: custinfo= autodetect=auto pwroverride= :is; custinfo administrative data

71

custinfo administrative data autodetect type of autonegotiation pwroverride …

you still need to provision the bridge port in the ISAM!

  • the capability to learn MAC-addresses
slide-72
SLIDE 72

Bridge port provisioning

6

72

6

slide-73
SLIDE 73

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:

73

if needed: e.g. increase #MAC addresses

slide-74
SLIDE 74

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

74

max-unicast-mac 4

LT x IWF

FW Engine

slide-75
SLIDE 75

Basic GPON QoS

7

75

7

slide-76
SLIDE 76

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:
TC Queue TC Queue 7 3 7 7 6 3 6 6 5 2 5 5 4 2 4 4 3 1 3 3 8 TC to 4 Queues 8 TC to 8 Queues 76
  • p-bit-to-TC mapping (L2 FWR setting)
  • ingress Profile: dot1p0 TCx1, dot1p1 TCx2, etc
3 1 3 3 2 1 2 2 1 1 1 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 …
slide-77
SLIDE 77

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

all p-bits are mapped to the same TC hence all traffic enters one single queue

77

configure vlan id 150 mode residential-bridge (secure-forwarding) in-qos-prof-name name:all-in-one

the p-bit mappings are actually/also needed on the ONT they are downloaded to the ONT when provisioning the bridge port!

slide-78
SLIDE 78

Ingress QoS profile: AMS configuration

78
slide-79
SLIDE 79

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
T-CONT types Type 1 Type 2 Type 3 Type 4 Type 5 CIR > 0 > 0 AIR = CIR > 0 > 0 >= CIR EIR = CIR = AIR > AIR > 0 >= AIR 79

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

slide-80
SLIDE 80

Bandwidth profile: CLI configuration

configure qos profiles

bandwidth CBR1000 committed-info-rate 1000 assured-info-rate 1000 excessive-info rate 1000 delay-tolerance 80 by default, a T-CONT will have a burst

80

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)

slide-81
SLIDE 81

Bandwidth profile: AMS configuration

81
slide-82
SLIDE 82

Hands-on

8

82

8

slide-83
SLIDE 83

Hands-on

Hidden Slide, see Notes Page Exercises

83
slide-84
SLIDE 84

www.alcatel-lucent.com

www.alcatel-lucent.com

84

www.alcatel-lucent.com