GPON basic configuration
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 - - 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
At the end of this session, you will … know what functions the NGLT-x is performing be capable to configure ONTs
Objective
2Table of Contents
1.PON provisioning 2.ONT Software Management 3.ONT provisioning
- 1. Basic ONT provisioning
- 2. ONT pre-provisioning
- 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
Remember this?
4Provisioning 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
TL1 based hierarchical breakdown + Identification
rack shelf pon lt
LT-1-1-5 PON-1-1-5-2 SHELF-1-1 RACK-1
6pon
- 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
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
7configure system security profile admin slot-numbering type-based
TL1-style of numbering
logout and login again to actually apply this change
PON provisioning
1
81
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
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
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
11PONs are created at LT creation time
- state admin-state down
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]
- 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]
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
13PONs are created at LT creation time
- state OOS = out of service
NT LT
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;
14bertm – 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]
ONT Software Management
2
152
ONT Software flow
ONT ONT FTP
16ONT ISAM AMS Download Download passive Download active
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
17RAM
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
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
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
19SWDLFILE
- 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
SW Perspective
20Download software to ISAM Options when using scenario 2
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
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
Step 2 : ONT Software file preparation : overview
23HW version: one ONT Type can have multiple hardware implementations
Step 2 : ONT Software file preparation : List of Hardware Info (OPTIONAL)
Allows to add a new type
- f Hardware
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)
25Load Type: using VoIP or not?
Step 3 : Download ONT software to NE
26- select NE(s)
- select ONT type
- select SW load
Step 3 : Which ONT software to use?
ONT software must be available on the NE before it can be downloaded
- nto the ONT!
when you plan the SW for the ONT, you have to add a “3’’ to the name 3FE50853AIAA05
ONT provisioning
3
283
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
Provisioning ONTs (cont.)
serial number based
- identify the ONT by its serial number
ALCLA0A28965 ONT not connected? ALARM
30Subscriber 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
Discovered ONT in case of basic provisioning
alarm at AMS: minor
Serial number of ONT
31alarm 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
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
Scenarios on ONT details
Planned software:
- ‘UNPLANNED’ -> scenario 1 and 2
- Specific version (‘3FE…’) -> scenario 1
- AUTO : automatic from NE -> scenario 3
- AUTO : automatic from NE -> scenario 3
ONT Post-provisioning
3.1
343.1
Provision ONT – Serial number based – AMS (1/3)
ONT id 1-1-3-1-64 serial number
Network
Rack Subrack NE
35ONT id 1-1-3-1-64
Subrack LT PON Port ONT (provisioned) Create ONT
Provision ONT – Serial number based – AMS (2/3)
36Provision ONT – Serial number based – AMS (3/3)
37check the SW and the status!
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
- 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
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
Provision ONT – Serial number based – TL1 (2/2)
- …
fecup=disable; powershedprofileid= powershedprofilenm=
- ntenable=
- pticshist=
plndvar= dlsw= rffilter= uspolicemode= (local,remote)
40uspolicemode= (local,remote) aesenable;
- ed-ont::ont-1-1-1-2-33 :::::is;
- is in service
- os out of service
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
ONT Operational data
42Show equipment ont operational-data 1/1/1/2/33 detail
ONT pre-provisioning
3.2
433.2
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
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
45powered 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
Pre-Provisioning SLID via webserver
PON doesn’t need to be disconnnected Available information
- product details
- vendor name, ONT type,
- product code, serial number
- product code, serial number
- SLID
- hexadecimal, alphanumeric
- PON status
- link status (up/down)
Pre-Provisioning ONT – SLID based – AMS (1/2)
Network
Rack Subrack NE
SLID
47ONT id 1-1-3-1-64
Subrack LT PON Port ONT (provisioned) Create ONT
Pre-Provisioning ONT – SLID based – AMS (2/3)
48Pre-Provisioning ONT – SLID based – AMS (3/3)
49check the SW and the status!
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
- 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
Pre-Provisioning ONT – SLID based – TL1
ent-ont::ont-1-1-1-2-33 :::: … sernum=ALCL00000000, subslocid=TEACHER, swverplnd=3FE50854AFCA10, … ;
51ONT pre-provisioning Automatic software management
3.3
52Automatic software management AMS based
3.3
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
53Object details
‘Planned Variant’ not filled in ‘Planned Software’ is set to UNPLANNED ‘Download Software’ is set to DISABLED
54AMS will set planned software first to ‘UNPLANNED’. Upon detection of ‘software version mismatch’ alarm, the AMS will fill in the correct version.
ONT pre-provisioning Automatic software management
3.4
55Automatic software management NE based
3.4
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
56Download to Passive bank Download to Active bank, which will trigger a reset of ONT
Object details
When provisioning the ONT , the AMS will set ‘planned software’ to AUTO and the ‘Planned Variant’ to DO
57Automatic download if hardware version and planned variant has a matching entry in the ONT software control table
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
HWVER VARNT PLNDSWVER PLNDSWVERCONF DLDSWVER 3FE29528AAAA06 I-020G-F 3FE50782BFQA29 3FE50782BFQA29 DISABLED
For more information on this feature, check the Operation and Maintenance Guide
Automatic ONT Software Management: from NE
Options when using NE for automatic software Management ‘From NE’
59Automatic ONT Software Management: from NE
60Compare Load list on AMS with Version Control Table on NE
Automatic ONT Software Management: from NE
61Update Version Control Table on NE based on Load List of AMS
ONT Card provisioning
4
624
Provision ONT Card – AMS (1/2)
example of a detected ONT Card:
63Provision ONT Card – AMS (2/2)
select node … ont 55 create planned ont-card
64Provision 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]
- 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
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
- 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
Ethernet Port provisioning
5
675
Provision Ethernet Port – AMS (1/2)
68Provision Ethernet Port – AMS (2/2)
provision the UNI
- With AMS this also automatically creates bridge port!
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
- See next chapter
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
71custinfo administrative data autodetect type of autonegotiation pwroverride …
you still need to provision the bridge port in the ISAM!
- the capability to learn MAC-addresses
Bridge port provisioning
6
726
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:
73if needed: e.g. increase #MAC addresses
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
74max-unicast-mac 4
LT x IWF
FW Engine
Basic GPON QoS
7
757
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
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
77configure 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!
Ingress QoS profile: AMS configuration
78Bandwidth 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>0Type 1 Type 2 Type 3 Type 4
Best-Effort Bandwidth Fixed Bandwidth
EIR>CIR CIR=AIR>0Type 5
Fixed Bandwidth
AIR=EIR>CIR CIR>0Assured Bandwidth
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
80delay-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)
Bandwidth profile: AMS configuration
81Hands-on
8
828
Hands-on
Hidden Slide, see Notes Page Exercises
83www.alcatel-lucent.com
www.alcatel-lucent.com
84www.alcatel-lucent.com