MOP TO COLLECT DEBUG AND MIGRATION LOGS

Table of Contents
I. Installation debug tools on AMS server 2
1. Create new folder containing the tools under AMS server 2
2. Upload the tools (Octopus and Alexx) to target folder 2
3. Unzip and change the file to be executable 2
II. Collect ALEXX logs file 3
1. Execute ALEXX tool by folowing commands 3
2. To get the log files, use the filezilla to get them as illustrated as following: 3
III. Collect Octopus log file 3
1. Access the problematic OLT by octopus tool 3
2. Collect log of necessary commands at NT or LT level accurately 3
IV. Migration log collection 4
1. Click on “View Migration Log” on the problematic OLT node as below picture 4
2. Click on “View” to see the migration logs in below picture 5
3. Save one by one two main log of migration to client as illustration following 6
I. Installation debug tools on AMS server
1. Create new folder containing the tools under AMS server
SSH to AMS server by account root and input following commands
# cd ~
# mkdir dbgtools

2. Upload the tools (Octopus and Alexx) to target folder

Using filezilla to upload files to AMS server as illustratation following:

3. Unzip and change the file to be executable

SSH by account root to AMS server and input following commands
[root@RHEL67S1 ~]# cd /root/dbgtools/
[root@RHEL67S1 dbgtools]# ls
ALEXX_v1.6.3.tar.gz octopus
[root@RHEL67S1 dbgtools]# chmod +x octopus
[root@RHEL67S1 dbgtools]# gunzip ALEXX_v1.6.3.tar.gz
[root@RHEL67S1 dbgtools]# tar xvf ALEXX_v1.6.3.tar

The first execution of ALEXX requires a password and key. Input following command to run ALEX
for only first time.
# perl alexx.pl --isam <OLT_IP> --toolpass alexx73xx --toolkey escape81

For all the next time of execution, just run ALEXX as following (without toolpass and toolkey):
# perl alexx.pl --isam <OLT_IP>
 II. Collect ALEXX logs file
To gather the ALEXX log files, execute below steps:

1. Execute ALEXX tool by folowing commands

# perl alexx.pl --isam <OLT_IP>

The log files of each time execution of ALEEX will be generated into the folder named LOGS at
the same path of ALEXX tool.

2. To get the log files, use the filezilla to get them as illustrated as following:

III. Collect Octopus log file

To gather the error message at debug level on each problematic OLT, execute following steps:

1. Access the problematic OLT by octopus tool

# ./octopus STDIO <OLT_IP>:udp:23

Account to login octopus interface is: shell/ nt

The login successful of octopus interface looks like below:

[root@RHEL67S1 dbgtools]# ./octopus STDIO 135.241.120.201:udp:23

Login: shell

Password:
T&D console USR0 login.

{nt1102}[USR0-shell]>

2. Collect log of necessary commands at NT or LT level accurately

eqpt displayasam
xapi time
dbg rvt EPRT
dbg rvt NPRT self
dbg rvt RPRT self
login board peer_nt
xapi time
dbg rvt EPRT
dbg rvt NPRT self
dbg rvt RPRT self
IV. Migration log collection
To gather the migration logs on the unsuccessful OLT node, following illustrated pictures below to
retrieve it.

1. Click on “View Migration Log” on the problematic OLT node as below picture
2. Click on “View” to see the migration logs in below picture
 3. Save one by one two main log of migration to client as illustration following

On the right window, select one by one the file named: migrate_2017-11-14_09_03.log and
isamMigration.log; then click on the buttom “Save on Client”

The migration log files will be saved in to client PC at path:

<DRIVE>:\<path_to_amsclient_installation>\workspace\Downloads

For examample:

C:\Users\qnguy001\5520AMS\9.5\workspace\Downloads