1. Passive Optical LAN Training: Module 3: ONT Architecture
3HV01415AAAGUNZZA r August 2016

2. Presentation Outline Section 1: ONT Infrastructure
Section 2: ONT Software
Section 3: ONT Build
Section 4: ONT Diagnostic Commands
Section 5: Perform Lab (module 3)

3. 1
ONT Infrastructure

4. ONT Infrastructure (POL) ONTs are built from ONT1 to ONT16/32 per PON.
The ONT serial number aligns the physical ONT to the logical ONT configuration
Forward Error Correction upstream is enabled, to compliment the PON downstream FEC
AES encryption (Advanced Encryption Standard) on a per ONU basis is enabled
The ONT is physically referenced and aligned to its respective serial number which is edited into the ONT configuration
Software file reference is set to ‘Automatic’ (triggering a software upgrade). The ONT ‘Model ‘ will obtain the correct s/w from the 7360 FX NT-A/B software control entries
Both the ONT Data Cards (and if analogue voice required) the ATA Voice Cards (I-240G-D, G-240G-C) also require declaration.

5. ONT Infrastructure: Data/Voice Ports
4 x Data Ports are configured for the I-240G-D and G-040P-P: 10/100/1000Mbps/auto-detect/ full duplex settings available.
Power over Ethernet is set optionally on the G-040P-P on an ‘as required’ port by port basis
Forwarding Queues, scheduling and bandwidth allocation per queues on a ‘per UNI port’ basis is set also
The I-240G-D has 2 analogue (RJ11) voice ports that can be configured

6. 2
ONT Software

7. ONT Software
ONT software are discrete files labeled 3FE12345ABCD01 where the ‘blue’ is ONT model specific, the ‘red’ is the software version for that ONT model
Each ONT variant will have a separate ONT software file
These ONT s/w files are located in the OLT controller card(s) and downloaded to the ONTs when the ONTs are connected to the PON (and provisioned)
ONTs are upgraded by adding new files to the OLT and ‘pointing’ the ONTs to the new s/w file. See a CLI and 5571 PCC reference below

8. ONT Software (cont)
The ONT software is delivered to the 5571 as a tar file (POL_ZBP1_1.tar’). The files listed per ONT type are included. The ONT s/w is then distributed to the OLT from the 5571 PCC and the 6 files listed are included with a ‘software control entry’ per ONT type to align the ONT hardware to the appropriate ONT s/w file
The ‘POL_BP1_1.tar’ file is provided to the customer via the local Channel Partner and is defined via the Nokia POL Blueprint1.1 Customer Release Note documentation.

9. ONT Software (cont)
The ONT software control entries that are created by the 5571 PCC are as follows (G-240G-C, G-040P-P/Q ONTs as examples)
The above 3 highlighted commands are the 5571 PCC ‘pushed’ entries with the ONT software files. They define the software that is to be downloaded and activated per ONT hardware model. Each ONT has ‘AUTO’ defined for software definition which then ‘points’ the ONT s/w definition to these ‘master software control entries’. Therefore if ONT upgrades are required in the future, modifying the software control entries avoids needing to redefine every ONT’s software release.

10. 3
ONT Build

11. ONT Infrastructure: CLI versus 5571 PCC
The Blueprint 1.1 release specifies 5571 PCC usage in all cases. The 5571 PCC specific training is via Module 9, and is a compulsory module. The other training modules mix CLI (with 5571 PCC) specifically to ensure trainees are familiar with the detailed configurations created via the 5571 PCC. Therefore, as of BP1.1, the removal of CLI for configuration does not apply to the training collateral, as it is essential in conveying and teaching the detailed POL configurations.

12. CLI Build: ONT Infrastructure: G-240G-C, I-240G-D
Note the POL solution will automatically upgrade the ONT based on the hardware variant discovered via the ‘AUTO’ referencing and the software alignment control table pushed via the 5571 PCC.

13. 5571 PCC Build: ONT Infrastructure: G-240G-C Example
The 5571 PCC ‘auto creates’ ONTs. The Operator does not need to create ONTs. Just ‘acknowledge’ them and physically locate them on a floor-plan: G-240G-C example below

14. CLI Build: ONT Infrastructure: G-040P-P G-040P-Q
Note the POL solution will automatically upgrade the ONT based on the hardware variant discovered via the ‘AUTO’ referencing and the software alignment control table pushed via the 5571 PCC.

15. CLI Build: ONT Infrastructure (continued)
The following command amends ONT serial numbers when ONTs are changed or installed at a later date and when serial numbers are not originally known:
When an ONT is suspected of equipment failure, all that is required is to ‘lock’ the ONT, substitute the serial number in the CLI, and ‘unlock’ the ONT again. The replacement ONT will upgrade and come into service, re-configured from the OLT.

16. 5571 PCC Build: ONT Infrastructure
The ONT ‘swap’ is achieved in the PCC via the yellow highlighted button and entering, or selecting a serial number via the ‘yet to be connected/existing’ option.

17. CLI Build: ONT Infrastructure (continued)
The following command shows ONTs connected to PONs that have not yet been associated to the 7360 FX configuration:
The command above shows an ONT with serial number ‘ALCLF2ACACCF’ has been connected to rack/shelf/LT1/PON1. Once this serial number is entered into the ONT CLI configuration, the ONT will be assigned to its logical configuration and will then disappear from this list.
As described earlier, ONTs are not always known by serial number when the logical build is performed. It is also feasible that the ONT arrives on site and is connected to the PON optical splitter with late, or no communication to the engineer building the service . To interrogate the 7360 FX as to what ONT is a new connect but not yet associated to a logical ONT configuration, perform the command above.
The command above shows an ONT with serial number ‘ALCLF2ACACCF’ has been connected to rack/shelf/LT1/PON1. Once this serial number is entered into the ONT configuration the ONT will be assigned to its logical configuration and will then disappear from this list.

18. CLI Build: ONT Infrastructure (continued)
The following command shows ONTs connected to PONs that have not yet been associated to the 7360 FX configuration:
The command above shows an ONT with serial number ‘ALCLF2ACACCF’ has been connected to rack/shelf/LT1/PON1. Once this serial number is entered into the ONT CLI configuration, the ONT will be assigned to its logical configuration and will then disappear from this list.
As described earlier, ONTs are not always known by serial number when the logical build is performed. It is also feasible that the ONT arrives on site and is connected to the PON optical splitter with late, or no communication to the engineer building the service . To interrogate the 7360 FX as to what ONT is a new connect but not yet associated to a logical ONT configuration, perform the command above.
The command above shows an ONT with serial number ‘ALCLF2ACACCF’ has been connected to rack/shelf/LT1/PON1. Once this serial number is entered into the ONT configuration the ONT will be assigned to its logical configuration and will then disappear from this list.

19. CLI Build: ONT Circuit Pack Infrastructure
The following commands are required per ONT. The ‘data’ and ‘voice’ circuit card is required for the I-240G-D/G-240G-C and only the ‘data’ card command for the G-040P-P/G-040P-Q ONT variant:
2 ‘circuit packs’ are required to be built: Card 1 (data) and card 2 (voice).

20. 4
ONT Diagnostic Commands

21. ONT Troubleshooting: ONT Operational Data
The following command shows the presence and absence of ONT fault conditions. Displayed below is also the estimated distance of the ONT from the PON LT port, 3.3 km.
Most, if not all ONT distance measurements will be ‘0.1’ (100 m) given the nature of the POL install being short run fibers in Small to Medium Enterprise environments.
This command if narrowed to a specific ONT would be ‘show equipment ont operational-data 1/1/3/2/5’ would provide details for LT3, PON Port 2, ONT5.

22. PON Troubleshooting: Operational Data
The following command shows bit error-rate statistics.
• show pon ber-stats 1/1/1/1
• admin pon ber-stats 1/1/1/1 clear-statistics
• show pon ber-stats 1/1/1/1 ont-num 1
Example is LT1/PON1. ‘1/1/3/5’ would indicate LT3 PON port 5.

23. PON Troubleshooting: Operational Data
The following command shows receive signal strength indicator for the PON statistics.
show pon optics 1/1/1/1
The example is LT1/PON1

24. ONT Troubleshooting: ONT Operational Data
The following command shows receive signal strength indicator for the ONT statistics.
show equipment ont optics 1/1/1/1/5
The example is of an ONT ‘5’ on LT1/PON1

25. 5571 PCC ONT Troubleshooting Statistics:
The following 5571 PCC GUI capabilities are available for the ONT statistics.
• Status : Serial number, hardware type, operational state (up/down), ONT ranging status, bit error rate
• Optical: TX/RX signal (a singular instance of the ONT power tx/rx listing as was at the PON level)
• WAN Traffic: The overall ONT upstream/downstream frame/xbps counters presented in graph format.
• Ethernet Traffic: All 4 x UNI traffic counter in graph format functionally equivalent in presentation to that of Figure 39.
• Ethernet Status: Port 1-4 UNIs operational state and MAC addresses learned
• 802.1x: Authentication Session status
• Alarms: ONT and UNI alarm displays of this particular ONT.

26. 5571 PCC ONT Troubleshooting Statistics (cont):
The following 5571 PCC GUI capabilities are for showing optical uplink statistics

27. 5571 PCC ONT Troubleshooting Statistics (cont):
The following 5571 PCC GUI capabilities are for showing optical uplink throughput traffic statistics for the ONT WAN

28. 5571 PCC ONT Troubleshooting Statistics (cont):
Per ONT alarms:
Per ONT UNI status, and location for listing MACs learned:

29. 5571 PCC ONT Troubleshooting Statistics (cont):
The following 5571 PCC GUI capability ‘related tasks’ are also able to be used as per a CLI equivalent was used previously.

30. 5
Perform Lab (module 3)

31. End of Module 3