Module Title

PON DIAGNOSIS

G
U
I

V
a
l
i
d
a
t
i
o PON DIAGNOSIS & History
n
PON DIAGNOSIS NAVIGATION

OPTICAL LINK DIAGNOSIS

NETWORK WIDE

PON VIEW REFRESH FAULTS

DISCOVERED ONT
 PON LOS

OPTICAL LINK
DIAGNOSIS

BACKUP-DB

O
P
E
R
A
T
I
O
N
 RESTORE-DB

O
P
E
R
A
T
I
O
N

REBOOT
Results
Passed
Failed
Blocked
 Test Description

Description
To verify the functionality of PON Diagnosis GUI page.
Initial State
The user is authenticated and logged in to the NA-F GUI.
Several hours of collection is completed.
ONTs are configured.
Several hours of bulk collection data is completed.
Test Sequence
1. Launch the PON Diagnosis page for a specific PON -> Select PON-> Reqd PON -> Show.
2. Check for GUI appropriateness of PON Diagnosis page - Latest link quality, Detected Faults
3. Verify for presence of button to start a new collection.
Expected Results
PON Diagnosis page is successfully displayed.
PON Diagnosis page shows Latest link quality, Detected Faults. Button to start a new
collection is present and PON basic details should be displayed.

Description
To verify the historical analysis chart in PON Diagnosis page.
Initial State
The user is authenticated and logged in to the NA-F GUI.
Several hours of collection is completed.
Several ONTs connected and up, at least one was switched off, interrupted for at least one
hour.
Test Sequence
1. Navigate to the PON diagnosis page.
2. Select tab History.
3. Verify the historical analysis chart.
Expected Results
The PON diagnosis report shows the analysis chart. values shown (as gradient) should
match the actual measured values.
historical Link quality transitions for an optical link are visible.
when clicking on an optical link chart row, the row expands and displays the power level
chart below.
Description
To verify report navigation to the Optical link Diagnosis (optical link view).

Initial State
The user is authenticated and logged in to the NA-F GUI.
Several hours of collection is completed.
Background collection was performed.

Test Sequence
1. Navigate to the PON diagnosis for the tested PON. PON-> Select PON-> click show
2. Select the Topology tab.
3. Click on the ONT number of one listed ONT.
Expected Results
Navigation to the PON diagnosis page should be successful.
Navigation to the Optical Link diagnosis page(for the ONT) from the PON page should be
successful when the ONT number is clicked
The GUI shows the Optical link diagnosis (optical link view) for the selected ONT.
Optical Link details, Faults history and link quality should be shown for the selected ONT

Description
The purpose of this test is to verify the functionality of optical Link Diagnosis GUI page.

Initial State
The user is authenticated and logged in to the NA-F GUI.
Several hours of collection is completed.
ONTs are configured.
Several hours of bulk collection data is completed.
Test Sequence
1 Navigate to the Optical Link Diagnosis page. Select a Optical link tab -> Select the ONT
under test -> Click on Go To Optical Link
2 Verify GUI for appropriateness of optical link diagnosis page - ONT address, ONT S/N,
ONTID, ONT SLID, OLT Card type, PON branch id, Distance to OLT, PON ID, , Feeder cable ID,
Latest Link Quality and Link Status.
3 Verify tabs: Link Quality, Quick Navigation, Charts & Faults, Power Validation, Real-time
Monitoring, and Diagnosis Metrics.
4 Verify button to start a new collection is present.
5 Verify the Link Quality evolution graph is shown.

Expected Results
Optical diagnosis GUI shows
ONT address, ONT S/N, ONT ID, SLID, OLT Card type, PON branch id, Distance to OLT, PON
ID, , Feeder cable ID, Latest Link Quality and Link Status.
Tabs Link Quality, Quick navigation, Charts & Faults, Power Validation, Real-time
Monitoring, Diagnostics Metrics are present
Button to start a new collection is present.
Link Quality tab should show the link quality evolution graph and filter should be available
for 3 days, 10 days and long term. Selecting the filter should update the evolution graph
appropriately.
Description
The purpose of this test is to verify the functionality of Network Wide Overview GUI.
Initial State
The user is authenticated and logged in to the NA-F GUI.
Several hours of collection is completed.
ONTs are configured.
Several hours of bulk collection data is completed.
Test Sequence
1. Launch the Network Wide overview page.
2. Check for GUI appropriateness of network wide view page - Most Impacting faults (latest
faults at the top), Link Quality, Faults per hour (last 48 hours), Link Quality evolution.
Expected Results
Network wide view page should show- Most Impacting Faults, Link Quality, Faults per hour
(last 48 hours), Link Quality evolution.
Link Quality graph should show how the link quality has evolved over a period time

Description
The purpose of this test is to verify Start button re-launches the fault detection and
localization algorithm.
Initial State
The user is authenticated and logged in to the NA-F GUI.
Several hours of bulk collection data is completed.
PON Diagnosis page has been launched and direct collection is complete.
Test Sequence
1. Launch PON Diagnosis page and wait for direct collection to complete.
2. Simulate some faults in the PON (locking an ONT will generate an equipment fault).
3. Click the Start button on top of the PON Diagnosis page.
4. The page should relaunch and trigger live collection of all connected ONT.
Expected Results
ONT equipment fault should be captured after pressing Start.

Description
Verify optical link status discovered.
Initial State
The user is authenticated and logged in to the NA-F GUI.
The alarm dispatcher is enabled and licensed and NA-F is connected to it (the NA-F alarm
dispatcher is an AMS OAD option).
Test Sequence
1. Connect an ONT without provisioning it.
2. Lookup the ONT through the Quick Search by its PON Port (OLT Address).
3. The user interface must show the ONT as being discovered.
Expected Results
The optical link status should be shown discovered
Description
To verify PON LOSS Alarm comes when fibre is unplugged at the LT end or all the connected
ONTs are unplugged
Initial State
NA Server installed and all NA-F processes are up and running. The user is authenticated
and logged in to the NA-F GUI.
ONT and OLTs are available as required
Several ONTs are connected to PON port
Data collection is done and minimum 6 hrs of data is available
Note: This test case is classified as destructive as unplugging the fibre lines is required.
Test Sequence
1. Unplug the fibre at the OLT/PON port end or unplug fibre from all the connected ONTs
2. Verify PONLOS alarm comes in the Alarm tab
3. Verify PONLOS Status should be with a red exclamation in Feeder cable page for the
associated PON
Expected Results
PONLOS Status should be with a red exclamation in Feeder cable page for the associated
PON
PONLOS alarm should come in the Alarm page.
PON diagnosis page should show the service as interrupted

Description
Restore DB from a previous back-up.
Initial State
The NA-F is running.
Ibbackup is installed and available
Test Sequence
1. Login to NA-F Server
2. Execute the command for hot backup ipm-hot-backup
3. Verify backup is successful and no errors are seen in the logs
Expected Results
Backup should be successful and measure the restore time. The restore time is dependant
of the DB size and amount of data to be re-imported.
Description
Restore DB from a previous back-up.
Initial State
The NA-F is running.
Ibbackup is installed and available
Latest hot backup is available.
Test Sequence
1. Login to NA-F GUI and delete some user
2. Login to NA-F Server
3. Connect to the mysql monitor and confirm the deleted user is not present.
ipm-mysql sdc
select * from NI_USER;
exit mysql monitor
4. Execute the command for hot backup restore ipm-restore-hot-backup as na user.
5. Verify the restore is successful
6. Verify the deleted user is created back again by connecting to mysql and attempting to
login with the deleted user.

Description
Verify if full restart of the server is less than 15min.
Initial State
The NA-F is running.
Test Sequence
1. Login to the NA-F Server as root user
2. Execute the command for reboot
3. Wait for the Server to reboot and login back if required
4. Execute the command ipm-server start as na user
5. Verify the restart of the server is less than 15 mins
Expected Results
Server restart should consume less than 15mins.
 Result Comment

Faults detected in PON : OLT0124:1-1-7-8, but do not

appear in Fault location. Some degradation faults (signal
degraded) appear in fault detection and others do not
appear.
Blocked

Loss of data during the the deleting empty splitters (11

Aug to 13 Aug), during synchronisation process (17 Aug
to 18 Aug) at [2pm-2am] and during the upgrade ( 18
Aug) (stared around 3 pm and finiched around 6 pm).
In the PON history, the loss of data is observed for all
Blocked ONTs during the upgrad, but in the charts and faults, the
loss of data for ONT9 (OLT0090:1-1-2-5-9) does not
appear (during upgrad period) and compared to ONU82
(OLT0090:1-1-2-5-82). No optical power in history tab for
this ONT OLT0053:1-1-3-2-97, but we oberve the power
in faults and charts.
 The power validation and history do not
Blocked appear in the PON OLT0019:1-1-1-6.

Passed
 Loss of data during upgrade
Blocked period.

Passed

Passed Ticket ouvert pour le second statut

 We are not alone in the
Blocked tree PON

Passed
 Title
GET ALL PONS

RUN_OPTICALLINKSTATISTICS

RUN OPTICAL LINK_DIAGNOSTICS

GetActiveFaultsOnBranch
 Test Description

Description
To verify NBI request for returning the entire list of PONs
Initial state
SOAP UI or equivalent of it is available
Test Sequence
1. Load interface from url http://${server_ip}/soap/naf/optical-nbi?wsdl
2. From SOAP UI invoke call GetAllPons
3. Enter startIndex and size

Expected Results
PONs listed should be nline with the provided startIndex and size and PON table in GUI

Description
To verify NBI request getOpticalLinkStatistics and verify the results of it.

Initial state
SOAP UI or equivalent of it is available.

Test Sequence
1. Load interface from url http://${server_ip}/soap/naf/optical-nbi?wsdl.
2. From SOAP UI invoke call getOpticalLinkStatistics.
3. Enter startTime and endTime

Expected Results
Results should be displayed in the NBI interface and inline with the optical measurement statistics
from the optical link report

Description
To verify NBI request to run the Optical Link Diagnostics and verify the results of it.

Initial state
SOAP UI or equivalent of it is available.

Test Sequence
1. Load interface from url http://${server_ip}/soap/naf/optical-nbi?wsdl.
2. From SOAP UI invoke call RunOpticalLinkDiagnostics.
3. Enter PON branchId or ONT address and invoke the call

Expected Results
Results shown in NBI response should be in sync with the latest detected faults as shown in the
PON GUI page
Description
To verify NBI request to run the GetActiveFaultsOnBranch and verify the results of it.

Initial state
SOAP UI or equivalent of it is available.

Test Sequence
1. Load interface from url http://${server_ip}/soap/naf/optical-nbi?wsdl.
2. From SOAP UI invoke call RunOpticalLinkDiagnostics.
3. Enter PON branchId or ONT address and invoke the call

Expected Results
Results shown in NBI response should be in sync with the latest detected faults as shown in the
PON GUI page
 Result Comment

Passed

Passed

Passed
Passed
 Title
Full injection of topology with the script

Full injection of topology with

incomplete/empty fields
Full injection of topology with empty or
corrupt files
 Test Description

Description
The purpose of this test is to verify the full injection of topology with the script.
Initial State
The NA-F is running.
Splitters and users files are created and available on CSV format.
Test Sequence
Connecting to the NA-F server with SSH and copy these files on /opt/naf_bytel/input :
NAF_Customer_Clients_AAAA_MM_JJ_HH.csv
NAF_Customer_Splitters_AAAA_MM_JJ_HH.csv
Return to /opt/naf_bytel/scripts and launch ./run_topology.sh
Expected Results
All topology/scenario update should be successful and the PON diagnosis page should be shown
with the updated splitter information
New customers are added in the topology with correct information (e.g:Optical tree, PM_NAME,
SRV_ID, PON Branch ID )
All csv output topologies are archived and saved in directory /opt/naf_bytel/output/archived
Check injection delay.

Description
The purpose of this test is to verify the full injection of topology with incomplete or empty fields.
Initial State
The NA-F is running.
Splitters and users files are created and available on CSV format with incomplete or empty fields
(e.g : SRV_ID, POSITION_PORT_OLT, SPL_RANG_0, SPLITTER_PORT_PM , REF_COUPL_PM,
PM_NAME)
Test Sequence
Connecting to the NA-F server with SSH and copy these files on /opt/naf_bytel/input :
NAF_Customer_Clients_AAAA_MM_JJ_HH.csv
NAF_Customer_Splitters_AAAA_MM_JJ_HH.csv
Return to /opt/naf_bytel/scripts and launch ./run_topology.sh
Expected Results
No impact for the rest of topology and customers.
[We still waiting for the expected results]
Description
The purpose of this test is to verify the full injection of topology with incomplete or empty fields.
Initial State
The NA-F is running.
Splitters and users files are created but empty or corrupt.
Test Sequence
Connecting to the NA-F server with SSH and copy these files on /opt/naf_bytel/input :
NAF_Customer_Clients_AAAA_MM_JJ_HH.csv
NAF_Customer_Splitters_AAAA_MM_JJ_HH.csv
Return to /opt/naf_bytel/scripts and launch ./run_topology.sh
Expected Results
No impact on the topology and customers.
[We still waiting for the expected results]
 Result Comment

The translation input to output works fine, but

we still have some issues with the
synchronization, it takes a lot of time (around
Failed 16 hours).

Blocked
 Title

OPE-Splitter KO and PONLOS

OPE-NEW ONT ADDED DWN OTHER

 Test Description

Description
A splitter default is detected, a PONLOS appear due to a client manipulation.
After the PONLOS clear, the splitter default come back.
Initial State
3 ONT are configured on a PON with two ONT on a splitter, the third one on another splitter.
A splitter default is detected (2 ONT are optically unplugged at the same time).
Test Sequence
1. Disconnect the third ONT, a PONLOS appear on the AMS.
2. Reconnect the third ONT, the PONLOS is cleared.
Expected Results
The Splitter fault is still present after the PONLOS.

Description
Verify the system capacity on fiber cut detection due to new customer added on the PM.
Initial State
The NA-F is running.
3 ONT placed on a PON, 2 are connected, one is not connected and has a nerver connected
status. These 3 ONT are on the same splitter.
Test Sequence
1. Login to the NA-F Server
2. Go to the PON tested
3. Connect the disconnected ONT and disconnect the two other at the same moment.
Expected Results
5530 NA-F detect an issue on the PON and the new added ONT is suspected.
 Result Comment

We are not alone in the

Blocked tree PON

faults detected in this PON

Blocked Type "collection failed"
Ticket N Description ALU comments

Internal error is thrown in NA-C GUI when navigating to Fix is expected to be delivered with
1-5807228 the Optical Link Diagnosis Page -> Charts&Faults -> Long release 9.1.2.
Term

requested data to start

1-5828462 AR Request ( Topology Syncroniation issue)
investigation.

1-5875936 New ONT alarms does not appears for all clients Under investigation in ALU side
1-5876561 Clients already connected once and pass to never_connecte Under investigation in ALU side

PON diagnostics failed: When we delete an ONT from AMS,

after that create the same ONT, the NA-F displays an error
1-5881290 by pressing " PON diagnosis failed. General live collection
failed "

This problem appears also after multiples ONT clean and

reconfigurations
Under investigation in ALU side

Loss of data during the delete empty splitters process

1-5885357 running
Under investigation in ALU side

1-5885399 Loss of data during topology synchronization

Under investigation in ALU side

1-5885483 Loss of data during NAF update

Under investigation in ALU side
Status

Passed.
But @Bytel: For different scenarios, we observe
the "Internal Error"
@ALU is due to the used browser (Chrome)
Blocked
It takes a lot of time (around 16 hours)

Blocked

Blocked

Blocked

Blocked

Blocked

Blocked
Tests Number of tests Tests OK Tests KO
Tests Blocked