7342 isam fttu r4_8_x software migration mop rev2

7342 ISAM FTTU R4.8.X SOFTWARE MIGRATION MOP

Author: Mehmet SOZBILIR

Alcatel-Lucent Turkey

3FQ 24064 48XG PGZZA

TABLE OF CONTENTS

1. INTRODUCTION ................................................................................................. 3

1.1. HOW TO USE THIS DOCUMENT .................................................................................... 3

1.2. SCOPE OF THIS DOCUMENT ....................................................................................... 3

1.3. DOCUMENT REVISION HISTORY .................................................................................... 3

1.4. FEEDBACK......................................................................................................... 3

1.5. GLOBAL PRODUCT EXPERTISE CENTER – FIXED ACCESS LINKS ..................................................... 4

1.6. 7342 ISAM FTTU DOCUMENTS AT GPEC SITE ................................................................... 4

1.7. SUPPORTED HARDWARE LIST FOR RELEASE 4.8.X ................................................................. 5

2. SITE VISIT PREPARATION ..................................................................................... 6

2.1. INFORMATION CHECKLIST ......................................................................................... 6

2.2. TOOLS AND DEVICES .............................................................................................. 6

2.3. PERSONNEL IN CHARGE ........................................................................................... 7

2.4. ESCALATION PROCEDURE .......................................................................................... 7

2.5. BOX CONFIGURATIONS ............................................................................................ 8

2.6. DVDS OR CD-ROMS .............................................................................................. 8

2.7. TIMETABLE ........................................................................................................ 9

2.8. PRE-SOFTWARE MIGRATION CHECKLIST ........................................................................... 9

3. SOFTWARE MIGRATION ...................................................................................... 11

3.1. SOFTWARE MIGRATION CHECKLIST .............................................................................. 11

3.2. PREPARE SYSTEM SOFTWARE .................................................................................... 12

3.2.1 Using UNIX commands, copy the 7342 ISAM FTTU OSWP to your TFTP Servers .......... 12

3.2.2 Change the Overall Descriptor File on Your TFTP Server Using the UNIX Text Editor of Your Choice (VI, ED, CAT etc.) ............................................................................. 13

3.3. DOWNLOAD THE SYSTEM SOFTWARE ............................................................................ 14

3.4. DOWNLOAD ONT SOFTWARE TO THE P-OLT ................................................................... 16

3.5. DOWNLOAD SOFTWARE TO AN ONT ............................................................................. 18

3.6. DB BACKUP AND MIGRATE SYSTEM SOFTWARE TO TARGET SOFTWARE LOAD .................................... 19

3.7. ACTIVATE THE INSTALLED ONT SOFTWARE ..................................................................... 28

3.8. POST-SOFTWARE MIGRATION CHECKLIST ........................................................................ 30

APPENDIX A. INDEX OF TABLES ............................................................................... 31

APPENDIX B. INDEX OF FIGURES .............................................................................. 32

APPENDIX C. GLOSSARY ........................................................................................ 33

Internal Note: Do not manually change “Table of Contents” field. Update field for any changes by right clicking on field and selecting “Update Field” tab.

7342 ISAM FTTU R4.8.X SOFTWARE MIGRATION MOP of 33

Copyright © Alcatel-Lucent GPEC TEAM 3FQ 24064 48XG PGZZA

1. INTRODUCTION

1.1. How to Use This Document Internal Note: This document was prepared for internal use.

1.2. Scope of This Document This document was prepared by ALU GPEC team. The objective is to provide detailed information about migration of the product 7342 ISAM FTTU, Release 4.8.0 & 4.8.06, at the customer premises. The document gives all the information needed for migrating software and bringing up the product in service.

1.3. Document Revision History

Date Version Author Change

9th December 2011 1.0 Mehmet SOZBILIR Document Creation

20th December 2011 1.1 Ilker ALBAYRAK Document Review

9th August 2012 1.2 Taner Ustebay Updating Document with R4.8.06

Table 1 : Document Revision History

1.4. Feedback For any feedback on this document, please contact to GPEC Fixed Access mail list For document defects, raise a CARES ticket and assign it to “NPIf-FAD-TR” workgroup.



1.5. Global Product Expertise Center – Fixed Access Links Internal Note: Please check GPEC-Fixed Access Homepage for the most recent version of this document. You can visit the following page for other WLEN Fixed Access product documents. https://all1.na.alcatel-lucent.com/Teams/GCDNetworks/WirelineGPEC/default.aspx

1.6. 7342 ISAM FTTU Documents at GPEC Site

No Document Name 1

Hardware Installation MoP

2

Software Installation & Field Integration MoP

3

Acceptance Test Procedure

4

Software Upgrade MoP

5

Software Migration MoP

6

Backup and Restore Procedure

7

Password Recovery Procedure

8

NE Discovery Procedure

Table 2 : Document List



1.7. Supported Hardware List for Release 4.8.X

Release features for R04.08.06

None


None


None


None


40km bidirectional SFP

Support for the EXNT-A 3FE51230AC


None


None


New GLT4-D that supports C+ optics


ETSI hardware support:

Against ALTS-N shelf: AFAN-H, SANC-D, FILT-A, AACU-C, EHNT-A, GLT2-A, GLT2-B

Against OLTS-M shelf: AFAN-S, EHNT-B, EXNT-A, FILT-A, GLT4-A, GLT4-D, AACU-C

Table 3: Supported Hardware List



2. SITE VISIT PREPARATION This is the list of items recommended to take with you while going site. Go through this list before you go to a site-work.

2.1. Information Checklist Fill the form below:

No Information Explanation

1 Box Configurations See the “Box Configuration” section in this chapter. Do you have additional config file to apply the box?

2 Site Address & Location Do you have the information to go there?

3 Site Security Permission Did you arrange the site security permission for the planned date & time?

4 Site Contact Person Who (from the customer site) will be in charge for your visit?

5 Scope of Work Do you know what operations/tasks will you be responsible for? Do you have a written statement confirmed by the customer?

6 Remote Access Configurations Far end devices configurations needs to be done by the customer or 3rd parties or by yourself.

Table 4 : Site-Visit Information Checklist

2.2. Tools and Devices

No Material For Use

1 Console Cable To connect to the box locally

2 Antistatic wrist strap Always use the antistatic wrist strap before you touch the hardware

3 External USB Hard Disk To store Backups, SW loads, configurations

4 USB Flash Disk Document and file sharing/transfer with the customer or 3rd parties

5 USB Card Reader For accessing the flash cards of devices

6 Screw Driver To mount a fresh product on-site / To tighten the loose screws

7 Multimeter To check the electricity on a wire/plug/hw

8 Pen and paper To take notes while sharing some information with the customer

9 Labeling Stickers Different sized of stickers to label the box, cable endpoints etc.

10 Fiber Cable For uplink connections

11 Rack Mount Kits

12 Laptop with Com port or USB to Serial convertor (Male)

14 Terminal Program For example Putty, MS Terminal, Hummingbird

15 X-Windows Client For example XManager, Hummingbird - Exceed

Table 5 : Tools and Devices for site visit



2.3. Personnel in Charge The following personnel will be involved in the activity:

Name of personnel Role Contact numbers

Table 6: Personnel in Charge

2.4. Escalation Procedure During the activity, if any problem occurs then the following engineers and/or people in charge should be notified for further actions.



2.5. Box Configurations Fill and check the box configuration table with required information before going site. It is recommended to populate the form below for each box and attach on the equipment before delivering to the field. For each server, fill a separate form as below.

Box Specifications

Location Geographical location of device, e.g. Istanbul/Sisli

Serial Number Enter chassis serial number here

Role e.g. Subtending, Hub etc.

Redundancy e.g. power redundancy, NT redundancy etc.

Hardware Model e.g. 7302 ISAM FD, 7330 ISAM FTTN, 7342 ISAM FTTU etc.

Serial Number Enter chassis serial number here

Additional Cards and Serial Numbers

Enter the serial numbers of other cards (NT, LT, NTIO) here

Compact Flash Memory e.g. CF 2GB

Power Supply What are the power requirements of the device?

Faults Any faults observed at the end of installation?

Management TCP/IP Configuration e.g. IP address for accessing the device

Table 7 : Box Configuration

2.6. DVDs or CD-ROMs For the initial installation, the software package for the Alcatel 7342 ISAM FTTU is delivered on a set of several DVDs or CD-ROMs. On the other hand you can download any release from the site OLCS (https://market.alcatel-lucent.com/release/jsp/sso/login.jsp).



2.7. Timetable

Fill the activity timetable below according to your plan. Columns starts with “proposal” should be filled in before the activity and columns with “actual” will be filled in after the password recovery activity.

Activity Details and Coordination

Item Description

Proposed Start Date/Time

Proposed End Date/Time

Actual Start Date/Time

Actual End Date/Time

eg. Personnel Check 21st Dec 21:30 21st Dec 21:40

eg. Preliminary Work Lists … …

eg. Reboot the router … …

e.g Zero Config Startup…

e.g. Execute the original config

e.g. Service and Traffic Check

e.g. Rebooting the Box ( Service Interruption )

Table 8: Timetable

2.8. Pre-Software Migration Checklist Entrance Criteria

The “Site Visit Preparation” section should be completed.

Pre-Software Migration Checklist Applied 1 Verify that you have remote connection to management server 2 Verify that you have username and password for Unix login

3 Verify that you have usernames and passwords to login via CLI/TL1 to 7342 ISAM FTTU node

Table 9: Pre-Software Migration Checklist



3. SOFTWARE MIGRATION

3.1. Software Migration Checklist Software Migration Checklist Applied

1 Verify that 5520 AMS server is acting as a TFTP server Ex: bash-3.00# netstat -a | grep tftp *.tftp Idle

2 Ping the 7342 ISAM FTTU to verify that the system can be reached from the TFTP client

3 Verify the default /tftpboot folder resides on the system

4 Verify that all the files of 7342 ISAM FTTU OSWP are copied to your TFTP Server’s home directory

5 Verify the software package is extracted in TFTP Server’s home directory 6 Verify the descriptor file is edited according to Section 3.2.2

7 Display the OSWP list and see the available OSWP on 7342 ISAM FTTU EX: REPT-OPSTAT-OSWP::ALL::. Ref: Section 3.3

8 Verify that both OSWP1 and OSWP2 are not enabled, if both are enabled you must ABORT uncommitted OSWP to install new software package. Ref: Section 3.3

9 Verify that the download for new software from TFTP server to the NT card is completed Ref: Section 3.3

10 Verify that new software (OSWP) is committed after completing download operation

11 Verify the new software version

12 If the system has redundant NT cards, verify that the NTs are synchronized Section Ref: Section 3.3

13 Verify the character “3” is added to the beginning of the ONT software file due to a file naming restriction in the NT file system Ref: Section 3.5

14 Verify that ONT software is copied to the TFTP Server’s home directory

15 Verify that ONT software executable file is downloaded from TFTP server to P-OLT node via TFTP

16 Verify that the ONT software file resides on the NT file system 17 Verify that ONT software is downloaded in passive state 18 Verify that the 7342 ISAM FTTU is alarm free

19 Verify those system health check tool (SHC) and offline database migration tool (ODMT) are installed on the TFTP server as root user. Section 3.6

20 Verify the backup of the current database to be used for the migration

21 Verify that active databases are uploaded from the OLT to the TFTP server via the TL1 craft terminal. Section 3.6

22 Verify the upload status is changed from ongoing to success 23 Verify the backup copy of the dm_complete.tar file resides on a safe location 24 Verify the environment is set for the library path and actual path 25 Verify the migration sequence is completed

26 Verify that migrated database is prepared for downloading to the OLT by changing the file name to dm_complete.tar

27 Verify the operational status of the OSWP 28 Verify the status of the downloaded database. Section 3.6 29 Verify that the target software release is activated. Section 3.6

Table 10: Software Migration Checklist



3.2. Prepare System Software Note: When using a TFTP server that resides on the same workstation as the 5520 AMS, the default 5520 AMS directory is /ams/swm/ne/ directory. If there is a 5520 AMS on the workstation acting as a TFTP server, ensure that any “TFTP Root Folder” created in these procedures is removed once all procedures are complete. This ensures no conflict between multiple TFTP directories.

In our case default TFTP folder: ((((/ams/swm/ne//ams/swm/ne//ams/swm/ne//ams/swm/ne/))))

3.2.1 Using UNIX commands, copy the 7342 ISAM FTTU OSWP to your TFTP Servers

BEGIN PROCEDURE: Insert the 7342 ISAM FTTU OLT software CD-ROM in the TFTP server CD-ROM drive. Under the TFTP root folder, create a directory on your server for the software package:

cd cd cd cd /TFTP_ROOT_FOLDER/TFTP_ROOT_FOLDER/TFTP_ROOT_FOLDER/TFTP_ROOT_FOLDER mkdirmkdirmkdirmkdir directorydirectorydirectorydirectory

Where directory is the name of the directory you want to create:

bash-3.00# cd cd cd cd ams/swm/ne/ams/swm/ne/ams/swm/ne/ams/swm/ne/ bash-3.00# mkdir mkdir mkdir mkdir migrationmigrationmigrationmigration

Copy the software package from the CD to that directory:

cd cd cd cd directorydirectorydirectorydirectory cp cp cp cp /cdrom/cdrom0/FTTU/ML3NAAxx.yyy/cdrom/cdrom0/FTTU/ML3NAAxx.yyy/cdrom/cdrom0/FTTU/ML3NAAxx.yyy/cdrom/cdrom0/FTTU/ML3NAAxx.yyy /directory/ML3NAAxx.yyy/directory/ML3NAAxx.yyy/directory/ML3NAAxx.yyy/directory/ML3NAAxx.yyy

where xx is the 2-digit 7342 ISAM FTTU release number; see Customer Release Notes for the corresponding 7342 ISAM FTTU Feature Group number yyy is the 3- digit software package number (for example, ML3NAA47.012)

bash-3.00# cd cd cd cd migrationmigrationmigrationmigration bash-3.00# scpscpscpscp ML3NAA48.080 [email protected]:ML3NAA48.080 [email protected]:ML3NAA48.080 [email protected]:ML3NAA48.080 [email protected]:/ams/swm/ne/migration/ams/swm/ne/migration/ams/swm/ne/migration/ams/swm/ne/migration



Untar the software package:

tar tar tar tar ----xvf ML3NAAxx.yyyxvf ML3NAAxx.yyyxvf ML3NAAxx.yyyxvf ML3NAAxx.yyy bash-3.00# tar tar tar tar ----xvf ML3NAA48.080xvf ML3NAA48.080xvf ML3NAA48.080xvf ML3NAA48.080

If a Readme.txt file is included in the package, review the information in this file before continuing.

END PROCEDURE

3.2.2 Change the Overall Descriptor File on Your TFTP Server Using the UNIX Text Editor of Your Choice (VI, ED, CAT etc.)

BEGIN PROCEDURE Go to the OSWP1 directory: bash-3.00# cdcdcdcd /ams/swm/ne/migration/OSWP1/ams/swm/ne/migration/OSWP1/ams/swm/ne/migration/OSWP1/ams/swm/ne/migration/OSWP1

Change permissions:

Chmod Chmod Chmod Chmod 777 ML3MAAxx.yyy777 ML3MAAxx.yyy777 ML3MAAxx.yyy777 ML3MAAxx.yyy

bash-3.00# chmod chmod chmod chmod 777 ML3MAA48.080777 ML3MAA48.080777 ML3MAA48.080777 ML3MAA48.080

Open the overall descriptor file, ML3MAA48.yyy, using the UNIX text editor of your choice. Where yyy is the 3-digit software package number (for example, ML3MAA48.080) Enter the contents of the overall descriptor file as follows:

OVERALL-DESCRIPTOR-FILE ML3NAAxx.yyyML3NAAxx.yyyML3NAAxx.yyyML3NAAxx.yyy BEGIN SYNTAX-VERSION : 01.00; ASAM-CORE : <<<<SW PackageSW PackageSW PackageSW Package Path>Path>Path>Path>/ML3NAAxx.yyy/ML3NAAxx.yyy/ML3NAAxx.yyy/ML3NAAxx.yyy <tftp_server_iptftp_server_iptftp_server_iptftp_server_ip>>>> 0.0.0.0; END

Where directory is the directory created for the software package xx is the 2-digit 7342 ISAM FTTU release number; see Customer Release Notes for the corresponding 7342 ISAM FTTU Feature Group number yyy is the 3-digit software package number (for example, ML3NAA48.080) tftp_server_ip is the IP address of the TFTP server.

OVERALL-DESCRIPTOR-FILE ML3NAA48.080ML3NAA48.080ML3NAA48.080ML3NAA48.080 BEGIN SYNTAX-VERSION : 01.00;



ASAM-CORE : migration/ML3NAA48.080migration/ML3NAA48.080migration/ML3NAA48.080migration/ML3NAA48.080 172.29.7.249172.29.7.249172.29.7.249172.29.7.249 0.0.0.0; END

Save file. END PROCEDURE

3.3. Download the System Software BEGIN PROCEDURE

1. Retrieve and record the status information for OSWP-1 and OSWP-2:

REPTREPTREPTREPT----OPSTATOPSTATOPSTATOPSTAT----OSWP:OSWP:OSWP:OSWP:[tid][tid][tid][tid]::::aid_swaid_swaid_swaid_sw::::[ctag][:][ctag][:][ctag][:][ctag][:];;;; REPTREPTREPTREPT----OPSTATOPSTATOPSTATOPSTAT----OSWP::ALL;OSWP::ALL;OSWP::ALL;OSWP::ALL;

2. Is the availability status (AVAILSTAT) of either OSWP-1 or OSWP-2 shown to be EMPTY? a. If an OSWP is empty, go to step 4 to download the target OSWP. b. If an OSWP is not empty, the active OSWP needs to be committed. Go to

step 3 to commit the active OSWP (OSWP with ACTSTAT of ACTIVE from step 1).

3. Commit the active OSWP:

EDEDEDED----OSWP:OSWP:OSWP:OSWP:[tid][tid][tid][tid]::::aid_swaid_swaid_swaid_sw::::[ctag][ctag][ctag][ctag]::::::::::::[sw_nblk][sw_nblk][sw_nblk][sw_nblk] EDEDEDED----OSWP::OSWPOSWP::OSWPOSWP::OSWPOSWP::OSWP----2::::COMMITMENT=TRUE;2::::COMMITMENT=TRUE;2::::COMMITMENT=TRUE;2::::COMMITMENT=TRUE;

4. Download the OSWP from the TFTP server to the 7342 ISAM FTTU NT card:

DLDLDLDL----OSWP:OSWP:OSWP:OSWP:[tid][tid][tid][tid]::::::::[ctag][ctag][ctag][ctag]::::::::dlservpridlservpridlservpridlservpri,,,,[dlservsec][dlservsec][dlservsec][dlservsec],,,,swpackagenameswpackagenameswpackagenameswpackagename;;;;

Where: “TFTP server IP address” is the IP address of your primary TFTP server directory is the directory path set up for the software package.

DLDLDLDL----OSWP:::::OSWP:::::OSWP:::::OSWP:::::<<<<tftp_server_iptftp_server_iptftp_server_iptftp_server_ip>>>>,,,,,,,,<Path of SW Package><Path of SW Package><Path of SW Package><Path of SW Package>/ML3NAAxx.yyy/ML3NAAxx.yyy/ML3NAAxx.yyy/ML3NAAxx.yyy;;;; DLDLDLDL----OSWP:::::OSWP:::::OSWP:::::OSWP:::::172.29.7.249172.29.7.249172.29.7.249172.29.7.249,,,,,,,,migration/OSWP1/ML3MAA48.080migration/OSWP1/ML3MAA48.080migration/OSWP1/ML3MAA48.080migration/OSWP1/ML3MAA48.080;;;;



5. Monitor the progress of the download:

REPTREPTREPTREPT----OPSTATOPSTATOPSTATOPSTAT----OSWPDL::ALL::OSWPDL::ALL::OSWPDL::ALL::OSWPDL::ALL:: Execute ? (Y,N) [Y] : IP 0 < GPEC-7342-1 70-01-01 01:04:14 M 0 COMPLD /* rept-opstat-oswpdl::all:: */ "OSWP-1:DLPROGRESS,DOWNLOADINGDOWNLOADINGDOWNLOADINGDOWNLOADING" "OSWP-1:DLERROR,NOERROR" "OSWP-1:COMPSET,63" "OSWP-1:AVAILCOMPSET,33" "OSWP-1:TOTALDISK,536027136" "OSWP-1:FREEDISK,462848000" "OSWP-1:DLSERVPRI,172.29.7.249" "OSWP-1:DLSERVSEC,172.29.7.249" "OSWP-1:PACKNAME,migration/OSWP1/ML3MAA48.080migration/OSWP1/ML3MAA48.080migration/OSWP1/ML3MAA48.080migration/OSWP1/ML3MAA48.080" "OSWP-2:DLPROGRESS,ENABLED" "OSWP-2:DLERROR,NOERROR" "OSWP-2:COMPSET,63" "OSWP-2:AVAILCOMPSET,63" "OSWP-2:TOTALDISK,536027136" "OSWP-2:FREEDISK,462848000" "OSWP-2:DLSERVPRI,172.29.7.249" "OSWP-2:DLSERVSEC,172.29.7.249" "OSWP-2:PACKNAME,migration/OSWP1/ML3MAA47.581" ;

Track the software AID of the file being downloaded (OSWP-1 or OSWP-2). It will be OSWP-2 if you have not previously performed a download.

6. When the download completes with no errors, go to step 8. If a problem is detected with the download, go to step 7.

7. If there is a problem with the download (download failed or stalled, for

example): Abort the download by typing:

EDEDEDED----OSWP::OSWPOSWP::OSWPOSWP::OSWPOSWP::OSWP----OSWP#::::ABORT=TRUE;OSWP#::::ABORT=TRUE;OSWP#::::ABORT=TRUE;OSWP#::::ABORT=TRUE; EDEDEDED----OSWP::OSWP::OSWP::OSWP::OSWPOSWPOSWPOSWP----1111::::ACTIVATION=,COMMITMENT=,ABORT=TRUE;::::ACTIVATION=,COMMITMENT=,ABORT=TRUE;::::ACTIVATION=,COMMITMENT=,ABORT=TRUE;::::ACTIVATION=,COMMITMENT=,ABORT=TRUE;

Where OSWP# is the software AID of the new OSWP Return to step 4.

8. If the system has redundant NT cards, verify that the NTs are synchronized (for example, NTASTATUS=ACTIVE, NTBSTATUS=HOTSTBY):

REPTREPTREPTREPT----OPSTATOPSTATOPSTATOPSTAT----NE::COM:: NE::COM:: NE::COM:: NE::COM:: Execute ? (Y,N) [Y] :



IP 0 < GPEC-7342-1 70-01-01 19:26:50 M 0 COMPLD /* REPT-OPSTAT-NE::COM:: */ "COM:EPSNGRPCHG,2" "COM:EPSSOAKINT,30000" "COM:NUMPROTNSW,0" "COM:PROTGRPADM,UNLOCK" "COM:PROTGRPALM,STBYDEG" "COM:SWCAUSE,NOSW" "COM:NTASTATUS,ACTIVE" "COM:NTBSTATUS,IDLE" "COM:SWCTRL,NORM" "COM:EQPTPRAC,LEEU" ;

3.4. Download ONT Software to the P-OLT Note: Due to a file naming restriction in the NT file system, only 13-character file names can be accommodated, even though 14-character software version names are supported by the ONT units. When provisioning a software version for an ONT, it is necessary to add the character “3” to the beginning of the ONT software file name.

• ONT software file name used without the leading “3” (FE50853AHCA10): When retrieving filenames from the NT file system

(RTRV-ONTSWVER)

When deleting files from the NT file system

(DLT-ONTSWVER)

• ONT software file name used with the leading “3” (FE50853AHCA10): When provisioning software to run on the

ONT (ENT/ED-ONT)

• When setting planned software versions in ONT software control table

(ENT/ED-ONTSWCTRL) Procedure Use this procedure to copy the ONT software from the ONT software CD-ROM to the TFTP server and then download the software to the 7342 ISAM FTTU.



1. Copy the ONT software executable file from the CD to any directory on the TFTP client machine:

cp cp cp cp /cdrom/cdrom0/ONT/FE50645/cdrom/cdrom0/ONT/FE50645/cdrom/cdrom0/ONT/FE50645/cdrom/cdrom0/ONT/FE50645xxxxyyxxxxyyxxxxyyxxxxyy ////MyDirMyDirMyDirMyDir/FE50645/FE50645/FE50645/FE50645xxxxyyxxxxyyxxxxyyxxxxyy scp scp scp scp FE50853AHFE50853AHFE50853AHFE50853AHCA10CA10CA10CA10 [email protected]:/ams/swm/ne/migration/[email protected]:/ams/swm/ne/migration/[email protected]:/ams/swm/ne/migration/[email protected]:/ams/swm/ne/migration/

2. Ping the 7342 ISAM FTTU to verify that the system can be reached from the TFTP client:

pingpingpingping 172.29.7.251172.29.7.251172.29.7.251172.29.7.251

where: 172.29.7.249 identifies the IP management address.

3. Start a TFTP session to the 7342 ISAM FTTU:

tftp tftp tftp tftp 172.29.7.172.29.7.172.29.7.172.29.7.251251251251

4. Set transfer mode to binary:

binbinbinbin

5. Download the ONT software executable file from the TFTP client to the systems /pub/Sw/Download directory:

where: xxxxyy identifies the executable file for your particular ONT.

put put put put FE506FE506FE506FE50645454545xxxxyyxxxxyyxxxxyyxxxxyy /pub/Sw/Download/FE50645/pub/Sw/Download/FE50645/pub/Sw/Download/FE50645/pub/Sw/Download/FE50645xxxxyyxxxxyyxxxxyyxxxxyy put put put put FE50853AHCA10FE50853AHCA10FE50853AHCA10FE50853AHCA10 /pub/Sw/Download//pub/Sw/Download//pub/Sw/Download//pub/Sw/Download/FE50853AHCA10FE50853AHCA10FE50853AHCA10FE50853AHCA10

6. End the TFTP session:

qqqquituituituit



3.5. Download Software to an ONT

1. From the craft interface to the 7342 ISAM FTTU, log in as an administrator.

2. Verify that the ONT software file resides on the NT file system:

RTRVRTRVRTRVRTRV----ONTSWVER:::::ONTSWVER:::::ONTSWVER:::::ONTSWVER:::::FE50645FE50645FE50645FE50645xxxxyyxxxxyyxxxxyyxxxxyy;;;;

where xxxxyy identifies the executable file for the particular ONT

/* RTRV/* RTRV/* RTRV/* RTRV----ONTSWVER::COM:::ONTSWVER::COM:::ONTSWVER::COM:::ONTSWVER::COM:::FE50853AHCA10FE50853AHCA10FE50853AHCA10FE50853AHCA10 */*/*/*/ "COM::SWVER="COM::SWVER="COM::SWVER="COM::SWVER=\\\\"FE50853AHCA10"FE50853AHCA10"FE50853AHCA10"FE50853AHCA10\\\\",SWVERSIZE=9489208"",SWVERSIZE=9489208"",SWVERSIZE=9489208"",SWVERSIZE=9489208"

3. Download ONT software that will be in the passive state. Assign an ONT software image for download to the ONT:


SETSETSETSET----ONTDLSW::ONTONTDLSW::ONTONTDLSW::ONTONTDLSW::ONT----1111----1111----1111----1111----1::::DLSW=1::::DLSW=1::::DLSW=1::::DLSW=3FE506453FE506453FE506453FE50645xxxxyyxxxxyyxxxxyyxxxxyy;;;; /* SET/* SET/* SET/* SET----ONTDLSW::ONTONTDLSW::ONTONTDLSW::ONTONTDLSW::ONT----1111----1111----1111----1111----1::::DLSW=1::::DLSW=1::::DLSW=1::::DLSW=3FE50853AHCA103FE50853AHCA103FE50853AHCA103FE50853AHCA10 */*/*/*/

4. Retrieve the ONT information to verify that the software has successfully downloaded:

RTRVRTRVRTRVRTRV----ONT::ONTONT::ONTONT::ONTONT::ONT----1111----1111----1111----1111----1;1;1;1;

/* RTRV-ONT::ONT-1-1-1-1-1 */ "ONT-1-1-1-1-1::BTRYBKUP=NO,BERINT=8000,DESC1=\"NULL\",DESC2=\"NULL\", PROVVERSION=\"*\",SERNUM=ALCLF9A3A879,SUBSLOCID=\"WILDCARD\", SWVERPLND=\"UNPLANNED\",FECUP=DISABLE,SCHEDPROFID=1,

SCHEDPROFNM=\"defSubSchedProf\",POWERSHEDPROFID=0,POWERSHEDPROFNM=\"NULL\", ONTENABLE=AUTO,P2PENABLE=DISABLE,RATELIMITOPT=DISABLE,OPTICSHIST=DISABLE, PLNDVAR=\"\",DLSW=\"3FE50853AHCA10\",EQPTVERNUM=3FE50754ADAC01, SWVERACT=3FE50854AHAA26,SWVERPSV=3FE50853ADAA54,VENDORID=ALCL, EQUIPID=BVM4P10DRAI221EA,NUMSLOTS=3,NUMTCONT=21,NUMTRFSCH=21,NUMPQ=20,

RFFILTER=2:OOS-AU"

Note : If the ONT software was downloaded to an active ONT using the SET-ONTDLSW command, the active software (SWVERACT) will be different from the passive software (SWVERPSV). The passive software can be made the active software by entering the passive software number in the SWVERPLND parameter.



3.6. DB Backup and Migrate System Software to Target Software Load

1.Verify that the 7342 ISAM FTTU is alarm free:

RTRVRTRVRTRVRTRV----ALMALMALMALM----ALL:ALL:ALL:ALL:[tid]:[aid_all]:[ctag]::[ntfncde],,[serveff],[locn],[dirn][tid]:[aid_all]:[ctag]::[ntfncde],,[serveff],[locn],[dirn][tid]:[aid_all]:[ctag]::[ntfncde],,[serveff],[locn],[dirn][tid]:[aid_all]:[ctag]::[ntfncde],,[serveff],[locn],[dirn];;;;

RTRVRTRVRTRVRTRV----ALMALMALMALM----ALL;ALL;ALL;ALL;

2.Was non-root user set up for software migration? a) If a non-root user was set up, go to step 5. b) Otherwise, go to step 3.

SHC and ODMT software download

3.Install the system health check tool (SHC) on the TFTP server as root user.

I. Make a directory in the TFTP home directory (tftpboot) for the tools:

bash-3.00# cd cd cd cd /tftpboot/tftpboot/tftpboot/tftpboot bash-3.00# mkdir mkdir mkdir mkdir <<<<tools_dirtools_dirtools_dirtools_dir>>>> bash-3.00# cd cd cd cd <tools_dir><tools_dir><tools_dir><tools_dir>

where tools_dir is a directory for the necessary tools used by the integrated SHC-Migration script.

bash-3.00# cd cd cd cd /ams/swm/ne/ams/swm/ne/ams/swm/ne/ams/swm/ne bash-3.00# mkdir mkdir mkdir mkdir toolstoolstoolstools bash-3.00# cd cd cd cd toolstoolstoolstools

II. Insert the 7342 ISAM FTTU ODMT CD-ROM in the TFTP server CD-ROM drive.

III. Copy SHC file, SHC_package.tar, from the 7342 ISAM FTTU ODMT CD-ROM

to the new directory on the server:

cp cp cp cp /cdrom/cdrom0/ODMT//cdrom/cdrom0/ODMT//cdrom/cdrom0/ODMT//cdrom/cdrom0/ODMT/SHC_package.tarSHC_package.tarSHC_package.tarSHC_package.tar scp scp scp scp SHC_package.SHC_package.SHC_package.SHC_package.tartartartar [email protected]:/ams/swm/ne/[email protected]:/ams/swm/ne/[email protected]:/ams/swm/ne/[email protected]:/ams/swm/ne/tools

where SHC_package.tar is the SHC package name defined in the ODMT Customer Release Notes, for example, SHC4.7.4.1.0.tar



IV. Untar the SHC package:

tar tar tar tar ----xvf xvf xvf xvf SHC_package.tarSHC_package.tarSHC_package.tarSHC_package.tar tar tar tar tar ----xvf xvf xvf xvf SHC.tarSHC.tarSHC.tarSHC.tar tartartartar ----xvf xvf xvf xvf SHC_package.taSHC_package.taSHC_package.taSHC_package.tarrrr tar tar tar tar ----xvf xvf xvf xvf SHC.tarSHC.tarSHC.tarSHC.tar

4.Copy the migration tool from the 7342 ISAM FTTU ODMT CD-ROM to the <tools_dir> directory.

Note : Alcatel-Lucent recommends that you do not create the <tools_dir> directory in the default /opt/ALAshc directory.

I. With the 7342 ISAM FTTU ODMT CD-ROM in the TFTP server CD-ROM drive, copy the ODMT file from the CD to the <tools_dir> directory:

cp cp cp cp /cdrom/cdrom0/ODMT//cdrom/cdrom0/ODMT//cdrom/cdrom0/ODMT//cdrom/cdrom0/ODMT/MBYXAA47.yyy.tarMBYXAA47.yyy.tarMBYXAA47.yyy.tarMBYXAA47.yyy.tar tar tar tar tar ----xvf xvf xvf xvf MBYXAA47.yyyMBYXAA47.yyyMBYXAA47.yyyMBYXAA47.yyy

scpscpscpscp MBYXAA48.080MBYXAA48.080MBYXAA48.080MBYXAA48.080 [email protected]:/ams/swm/ne/[email protected]:/ams/swm/ne/[email protected]:/ams/swm/ne/[email protected]:/ams/swm/ne/tools tar tar tar tar ––––xvf xvf xvf xvf MBYXAA48.080MBYXAA48.080MBYXAA48.080MBYXAA48.080

II. Remove the 7342 ISAM FTTU ODMT CD-ROM from the TFTP server CD-ROM drive

Database backup

5.What kind of NT system do you have? a) For systems with a redundant NT configuration, go to step 6. b) For systems with a simplex NT configuration, go to step 7.

6.Prior to making a database back up, verify redundant NT status:

I. Verify that NTA and NTB are synchronized (for example, NTA ACTIVE and

NTB HOTSTBY):

REPTREPTREPTREPT----OPSTATOPSTATOPSTATOPSTAT----NE:NE:NE:NE:[tid][tid][tid][tid]::::[aid_com][aid_com][aid_com][aid_com]::::[ctag][ctag][ctag][ctag][:];[:];[:];[:]; REPTREPTREPTREPT----OPSTATOPSTATOPSTATOPSTAT----NE;NE;NE;NE;



II. Retrieve the current NT protection configuration, the protection switching mode should be allowed (ALW) and redundancy control state should be normal (NORMAL):

RTRVRTRVRTRVRTRV----SWDXSWDXSWDXSWDX----EQPT:EQPT:EQPT:EQPT:[tid][tid][tid][tid]::::[aid_dxeqpt][aid_dxeqpt][aid_dxeqpt][aid_dxeqpt]::::[ctag][ctag][ctag][ctag][:];[:];[:];[:]; RTRVRTRVRTRVRTRV----SWDXSWDXSWDXSWDX----EQPT;EQPT;EQPT;EQPT;

III. Does the response display ALW,NORMAL? If yes, go to step 7. If the response has INH or FRCD, go to step iv.

IV. Set the protection configuration to allowed and normal:

ALWALWALWALW----SWDXSWDXSWDXSWDX----EQPT:EQPT:EQPT:EQPT:[tid][tid][tid][tid]::::aid_dxeqptaid_dxeqptaid_dxeqptaid_dxeqpt::::[ctag][ctag][ctag][ctag][::];[::];[::];[::]; ALWALWALWALW----SWDXSWDXSWDXSWDX----EQPT::NT;EQPT::NT;EQPT::NT;EQPT::NT;

7.Create a backup of the current database to be used for the migration.

I. From the TFTP server terminal:

cd cd cd cd /tftpboot/<tools_dir>//tftpboot/<tools_dir>//tftpboot/<tools_dir>//tftpboot/<tools_dir>/ touch touch touch touch dm_complete.tardm_complete.tardm_complete.tardm_complete.tar chmod 777 chmod 777 chmod 777 chmod 777 dm_complete.tardm_complete.tardm_complete.tardm_complete.tar bash-3.00# cd cd cd cd /ams//ams//ams//ams/swmswmswmswm/ne/tools/ne/tools/ne/tools/ne/tools bash-3.00# touch touch touch touch dm_complete.tardm_complete.tardm_complete.tardm_complete.tar bash-3.00# chmod 777 chmod 777 chmod 777 chmod 777 dm_complete.tardm_complete.tardm_complete.tardm_complete.tar

II. From the TL1 craft terminal, upload the active databases from the OLT to the TFTP server:

ULULULUL----DB:DB:DB:DB:[tid][tid][tid][tid]::::::::[ctag][ctag][ctag][ctag]::::::::[ulserv][ulserv][ulserv][ulserv],,,,[ulpath][ulpath][ulpath][ulpath],,,,uldbuldbuldbuldb;;;;

Example: UL-DB:::::<tftp_server_ip>,/<tools_dir>/dm_complete.tar,AOSW PACTUAL; Where tftp_server_ip is the IP address of the TFTP server

ULULULUL----DB:::::DB:::::DB:::::DB:::::172.29.7.249172.29.7.249172.29.7.249172.29.7.249,,,,ODMT/dm_complete.tarODMT/dm_complete.tarODMT/dm_complete.tarODMT/dm_complete.tar,AOSWPACT,AOSWPACT,AOSWPACT,AOSWPACTUAL UAL UAL UAL Execute ? (Y,N) [Y] : IP 0 < GPEC-7342-1 70-01-01 05:28:27 M 0 COMPLD /* UL-DB:::::172.29.7.249,/tools/ODMT/dm_complete.tar,AOSWPACTUAL



*/ ;

III. Verify the database upload status:

REPTREPTREPTREPT----OPSTATOPSTATOPSTATOPSTAT----DBUL:DBUL:DBUL:DBUL:[tid][tid][tid][tid]::::::::[ctag][ctag][ctag][ctag][:];[:];[:];[:];

The upload status should change from “.ongoing,noerror” to “.success,noerror”

REPTREPTREPTREPT----OPSTATOPSTATOPSTATOPSTAT----DBUL:::: DBUL:::: DBUL:::: DBUL:::: Execute ? (Y,N) [Y] : Execute ? (Y,N) [Y] : Execute ? (Y,N) [Y] : Execute ? (Y,N) [Y] : IP 0 < GPEC-7342-1 70-01-01 05:29:10 M 0 COMPLD /* REPT-OPSTAT-DBUL:::: */ "SUCCESS,NOERROR,172.29.7.249,/tools/ODMT/dm_complete.tar" ;

8.Create a backup copy of the dm_complete.tar file, and store in a safe location on the TFTP server in another directory, or FTP the backup copy off the TFTP server to a secure, accessible site.

9.From the <tools_dir> directory using C-Shell or bash, set the environment for the library path:

bashbashbashbash export export export export PATH=<PATH=<PATH=<PATH=<pwdpwdpwdpwd>/bin:$PATH:<>/bin:$PATH:<>/bin:$PATH:<>/bin:$PATH:<pwdpwdpwdpwd>>>> export export export export LD_LIBRARY_PATH=<LD_LIBRARY_PATH=<LD_LIBRARY_PATH=<LD_LIBRARY_PATH=<pwdpwdpwdpwd>/lib:<>/lib:<>/lib:<>/lib:<pwdpwdpwdpwd>/sunlib:<>/sunlib:<>/sunlib:<>/sunlib:<pwdpwdpwdpwd>/library>/library>/library>/library

where <pwd> is the present working directory

#bashbashbashbash bash-3.00# bash-3.00# exportexportexportexport PATHPATHPATHPATH=/ams/swm/ne/ODMT/bin:$PATH:=/ams/swm/ne/ODMT/bin:$PATH:=/ams/swm/ne/ODMT/bin:$PATH:=/ams/swm/ne/ODMT/bin:$PATH: ////ams/swm/ne/ODMTams/swm/ne/ODMTams/swm/ne/ODMTams/swm/ne/ODMT bash-3.00# export export export export LD_LIBRARY_PATH=/var/pkg/TclPro1.4/solarisLD_LIBRARY_PATH=/var/pkg/TclPro1.4/solarisLD_LIBRARY_PATH=/var/pkg/TclPro1.4/solarisLD_LIBRARY_PATH=/var/pkg/TclPro1.4/solaris----sparc/lib:/opt/ALAshc/lib:/ams/swm/ne/ODMT/sunlib:/ams/swm/ne/ODMT/lsparc/lib:/opt/ALAshc/lib:/ams/swm/ne/ODMT/sunlib:/ams/swm/ne/ODMT/lsparc/lib:/opt/ALAshc/lib:/ams/swm/ne/ODMT/sunlib:/ams/swm/ne/ODMT/lsparc/lib:/opt/ALAshc/lib:/ams/swm/ne/ODMT/sunlib:/ams/swm/ne/ODMT/library:/ams/swm/ne/ODMT/libibrary:/ams/swm/ne/ODMT/libibrary:/ams/swm/ne/ODMT/libibrary:/ams/swm/ne/ODMT/lib

Necessary directories exported to the “PATH” and “LD_LIBRARY_PATH” So the running script can refer to the related files in the given directories while processing the migration. The result of the export can be checked by typing “set” to the bash console.



bash-3.00# setsetsetset BASH=/usr/bin/bash BASH_ARGC=() BASH_ARGV=() BASH_LINENO=() BASH_SOURCE=() BASH_VERSINFO=([0]="3" [1]="00" [2]="16" [3]="1" [4]="release" [5]="sparc-sun-solaris2.10") BASH_VERSION='3.00.16(1)-release' COLUMNS=132 DIRSTACK=() EUID=0 GROUPS=() HISTFILE=//.bash_history HISTFILESIZE=500 HISTSIZE=500 HOME=/ HOSTNAME=GPEC-5520AMS-1 HOSTTYPE=sparc IFS=$' \t\n' LD_LIBRARY_PATH=/var/pkg/TclPro1.4/solarisLD_LIBRARY_PATH=/var/pkg/TclPro1.4/solarisLD_LIBRARY_PATH=/var/pkg/TclPro1.4/solarisLD_LIBRARY_PATH=/var/pkg/TclPro1.4/solaris----sparc/lib:/opt/ALAshc/lib:/ams/swm/ne/ODMT/sunlib:/ams/swm/ne/ODMT/lsparc/lib:/opt/ALAshc/lib:/ams/swm/ne/ODMT/sunlib:/ams/swm/ne/ODMT/lsparc/lib:/opt/ALAshc/lib:/ams/swm/ne/ODMT/sunlib:/ams/swm/ne/ODMT/lsparc/lib:/opt/ALAshc/lib:/ams/swm/ne/ODMT/sunlib:/ams/swm/ne/ODMT/library:/ams/swm/ne/ODMT/libibrary:/ams/swm/ne/ODMT/libibrary:/ams/swm/ne/ODMT/libibrary:/ams/swm/ne/ODMT/lib LINES=48 LOGNAME=root MACHTYPE=sparc-sun-solaris2.10 MAIL=/var/mail//root MAILCHECK=60 OLDPWD=/ams/swm/ne OPTERR=1 OPTIND=1 OSTYPE=solaris2.10 PATH=/var/pkg/TclPro1.4/solarisPATH=/var/pkg/TclPro1.4/solarisPATH=/var/pkg/TclPro1.4/solarisPATH=/var/pkg/TclPro1.4/solaris----sparc/bin:/ams/swm/ne/ODMT/bin:/usr/sbin:/usr/bin:/ams/swm/ne/ODMTsparc/bin:/ams/swm/ne/ODMT/bin:/usr/sbin:/usr/bin:/ams/swm/ne/ODMTsparc/bin:/ams/swm/ne/ODMT/bin:/usr/sbin:/usr/bin:/ams/swm/ne/ODMTsparc/bin:/ams/swm/ne/ODMT/bin:/usr/sbin:/usr/bin:/ams/swm/ne/ODMT PIPESTATUS=([0]="0") PPID=916 PS1='\s-\v\$ ' PS2='> ' PS4='+ ' PWD=/ams/swm/ne/ODMT SHELL=/sbin/sh SHELLOPTS=braceexpand:emacs:hashall:histexpand:history:interactive-comments:monitor SHLVL=1 SSH_CLIENT='135.243.69.237 4475 22' SSH_CONNECTION='135.243.69.237 4475 172.29.7.249 22' SSH_TTY=/dev/pts/1 TERM=vt100 TZ=Turkey UID=0 USER=root _=R4.8

Note: The run time for the migration script will vary depending upon the size of the database. The typical database will complete migration in about 30 minutes, whereas a fully provisioned system (18 LTs and 128 ONTs per PON) may require more than 5 hours.

10. Understand the migration sequence:

I. Identify the ODMT package with which to perform the migration, as done in step 4, for example, MBYXAA48.080.



II. Use the following script to migrate:./migShcIntegration.tcl –in dm_complete.tar -from XXXXX -to YYYYY [-out < outputDBfile.tar >].

bash-3.00# ./migShcIntegration.tcl ./migShcIntegration.tcl ./migShcIntegration.tcl ./migShcIntegration.tcl ----in dm_complete.tar in dm_complete.tar in dm_complete.tar in dm_complete.tar ----from R4.7.50 from R4.7.50 from R4.7.50 from R4.7.50 ----to R4.8to R4.8to R4.8to R4.8 Checking If the Input database is valid... ## Executing DB Consistency check before migration on R4.7.50 database. (DB consistency check for big database might take upto one hour, please wait...) ## Executing DB Screening ..... ## DB Consistency check execution on R4.7.50 database before Migration is finished. ## !!! Migration process to migrate R4.7.50 database to R4.8 database is in progress !!! Migration Done! ************** Migration process Finished With Success ************** ############## Executing DB Consistency check on Migrated database(dm_migrated_120811.132544_16332.tardm_migrated_120811.132544_16332.tardm_migrated_120811.132544_16332.tardm_migrated_120811.132544_16332.tar) ############# (DB consistency check for big database might take upto one hour, please wait...) Executing DB Screening ..... ############## Executing DB Comparison between dm_complete.tar & dm_migrated_120811.132544_16332.tardm_migrated_120811.132544_16332.tardm_migrated_120811.132544_16332.tardm_migrated_120811.132544_16332.tar ############# (DB comparison check for big database might take upto one hour, please wait...) ============================================================== | MIGRATION REPORT | ============================================================== Pre Migration SHC Report - --------------------------- "dm_complete.tar" is free of violations Migration Status - ------------------- Migration is successful. Migrated database name is "dm_migrated_120811.132544_16332.tardm_migrated_120811.132544_16332.tardm_migrated_120811.132544_16332.tardm_migrated_120811.132544_16332.tar" Post Migration SHC Report - ---------------------------- "dm_migrated_120811.132544_16332.tar" is free of violations DB Comparison Check : There is no modification in the attributes from input database to migrated database. Attributes have been added in either of the release DB Comparison Check : For details please refer the file - /ams/swm/ne/ODMT/html/pdata_dm08-12-2011_13:28:03.html ==============================================================



Download migrated database

11. Prepare the migrated database for downloading to the OLT by changing the file name to dm_complete.tar: cp cp cp cp <<<<outputDBfileoutputDBfileoutputDBfileoutputDBfile>>>> dm_complete.tardm_complete.tardm_complete.tardm_complete.tar

where outputDBfile.tar is a specified file name for the migrated database (the default output file name format is dm_migrated_<Date>.<Time>_<Shellid>.tar).

cp cp cp cp dm_migrated_1208dm_migrated_1208dm_migrated_1208dm_migrated_120811.132544_16332.tar dm_complete.tar11.132544_16332.tar dm_complete.tar11.132544_16332.tar dm_complete.tar11.132544_16332.tar dm_complete.tar

12. Verify the operational status of the OSWP:

REPTREPTREPTREPT----OPSTATOPSTATOPSTATOPSTAT----OSWP:OSWP:OSWP:OSWP:[tid][tid][tid][tid]::::aid_swaid_swaid_swaid_sw::::[ctag][ctag][ctag][ctag];;;;

REPTREPTREPTREPT----OPSTATOPSTATOPSTATOPSTAT----OSWP::ALL;OSWP::ALL;OSWP::ALL;OSWP::ALL; /* rept-opstat-oswp::all:: */ "OSWP-1:AVAILSTAT,ENABLED" "OSWP-1:ACTSTAT,NOTACTIVE" "OSWP-1:COMMITSTAT,UNCOMMITTED" "OSWP-2:AVAILSTAT,ENABLED" "OSWP-2:ACTSTAT,ACTIVE" "OSWP-2:COMMITSTAT,COMMITTED"

13. Download the migrated database to the OLT:

I. Download the migrated database contained in the dm_complete.tar file:

DLDLDLDL----DB:DB:DB:DB:[tid][tid][tid][tid]::::::::[ctag][ctag][ctag][ctag]::::::::[dlserv][dlserv][dlserv][dlserv],,,,dlpathdlpathdlpathdlpath;;;;

DL-DB:::::<tftp_ip>,/<tools_dir>/dm_complete.tar; Where tftp_ip is the IP address of the TFTP server

DLDLDLDL----DBDBDBDB:::::172.29.7.249,:::::172.29.7.249,:::::172.29.7.249,:::::172.29.7.249,/tools/ODMT//tools/ODMT//tools/ODMT//tools/ODMT/dm_complete.tardm_complete.tardm_complete.tardm_complete.tar Execute ? (Y,N) [Y] : Execute ? (Y,N) [Y] : Execute ? (Y,N) [Y] : Execute ? (Y,N) [Y] : IP 0 < GPEC-7342-1 70-01-01 01:56:30 M 0 COMPLD /* DL-DB:::::172.29.7.249,/tools/ODMT/dm_complete.tar */ ;



II. Verify the database download status:

REPTREPTREPTREPT----OPSTATOPSTATOPSTATOPSTAT----DBDLDBDLDBDLDBDL:::::::::::::::: Execute ? (Y,N) [Y] : IP 0 < GPEC-7342-1 70-01-01 01:56:46 M 0 COMPLD /* REPT-OPSTAT-DBDL:::: */ "SUCCESS,NOERROR,172.29.7.249,/tools/ODMT/dm_complete.tar" ;

14. Verify the status of the downloaded database. REPTREPTREPTREPT----OPSTAT:DB;OPSTAT:DB;OPSTAT:DB;OPSTAT:DB; REPTREPTREPTREPT----OPSTATOPSTATOPSTATOPSTAT----DB::ALL:: DB::ALL:: DB::ALL:: DB::ALL:: Execute ? (Y,N) [Y] : IP 0 <

GPEC-7342-1 70-01-01 02:02:39 M 0 COMPLD /* REP-OPSTAT-DB::ALL:: */ "DB-1:DBNAME,dmMigrated" "DB-1:DBVERSION,A4.800" "DB-1:AOPERSTAT,NOTUSEFUL" "DB-1:NAOPERSTAT,ACTUAL" "DB-3:DBNAME,NO_NAME" "DB-3:DBVERSION,A4.750" "DB-3:AOPERSTAT,ACTUAL" "DB-3:NAOPERSTAT,NOTUSEFUL" ;

15. Activate the target software release OSWP, as recorded from step 19, with the migrated database:

Where OSWP-x is either OWSP-1 or OSWP-2

EDEDEDED----OSWP::OSWP::OSWP::OSWP::OSWPOSWPOSWPOSWP----xxxx::::ACTIVATION=WITHLINKEDDB;::::ACTIVATION=WITHLINKEDDB;::::ACTIVATION=WITHLINKEDDB;::::ACTIVATION=WITHLINKEDDB; EDEDEDED----OSWP::OSWP::OSWP::OSWP::OSWPOSWPOSWPOSWP----1111::::ACTIVATION=WITHLINKEDDB,COMMITMENT=,ABORT=::::ACTIVATION=WITHLINKEDDB,COMMITMENT=,ABORT=::::ACTIVATION=WITHLINKEDDB,COMMITMENT=,ABORT=::::ACTIVATION=WITHLINKEDDB,COMMITMENT=,ABORT= Execute ? (Y,N) [Y] : IP 0 < GPEC-7342-1 70-01-01 02:13:27 M 0 COMPLD /* ED-OSWP::OSWP-1::::ACTIVATION=WITHLINKEDDB,COMMITMENT=,ABORT= */ ; REPTREPTREPTREPT----OPSTATOPSTATOPSTATOPSTAT----OSWPDL::ALL:: OSWPDL::ALL:: OSWPDL::ALL:: OSWPDL::ALL::



Execute ? (Y,N) [Y] : IP 0 < GPEC-7342-1 70-01-01 02:42:00 M 0 COMPLD /* REPT-OPSTAT-OSWPDL::ALL:: */ "OSWP-1:DLPROGRESS,ENABLED" "OSWP-1:DLERROR,NOERROR" "OSWP-1:COMPSET,63" "OSWP-1:AVAILCOMPSET,63" "OSWP-1:TOTALDISK,536027136" "OSWP-1:FREEDISK,412409856" "OSWP-1:DLSERVPRI,172.29.7.249" "OSWP-1:DLSERVSEC,172.29.7.249" "OSWP-1:PACKNAME,OSWP1/ML3MAA48.080" "OSWP-2:DLPROGRESS,ENABLED" "OSWP-2:DLERROR,NOERROR" "OSWP-2:COMPSET,63" "OSWP-2:AVAILCOMPSET,63" "OSWP-2:TOTALDISK,536027136" "OSWP-2:FREEDISK,412409856" "OSWP-2:DLSERVPRI,172.29.7.249" "OSWP-2:DLSERVSEC,172.29.7.249" "OSWP-2:PACKNAME,taner/OSWP1/ML3MAA47.581" ; REPTREPTREPTREPT----OPSTATOPSTATOPSTATOPSTAT----OSWP::ALL:: OSWP::ALL:: OSWP::ALL:: OSWP::ALL:: Execute ? (Y,N) [Y] : IP 0 < GPEC-7342-1 70-01-01 02:42:27 M 0 COMPLD /* REPT-OPSTAT-OSWP::ALL:: */ "OSWP-1:AVAILSTAT,ENABLED" "OSWP-1:ACTSTAT,ACTIVEACTIVEACTIVEACTIVE" "OSWP-1:COMMITSTAT,UNCOMMITTED" "OSWP-2:AVAILSTAT,ENABLED" "OSWP-2:ACTSTAT,NOTACTIVENOTACTIVENOTACTIVENOTACTIVE" "OSWP-2:COMMITSTAT,COMMITTED" ;

For simplex NT systems, this initiates a restart of the active NT card. When the NT restart has completed, the LT cards are automatically downloaded with new software loads and restarted. For redundant NT systems, (for example with NT-A active and NT-B standby) this initiates the following system upgrade sequence:

• The standby NT (NT-B) is rebooted and will be brought up with the new software image and new (migrated) database. Management access to the shelf is lost, both IP access and serial craft port access.

• Formerly active NT (NT-A) remains active and continues to switch traffic. LT cards remain up and switching traffic. LANX switching is reduced by 50%, however if the system traffic can be handled by a single LANX, there is no traffic loss at this stage.



• The newly active NT (which is now NT-B) completes the migration and comes up with the new software image and new database.

• Formerly active NT (NT-A) starts the reboot process. Traffic stops at this stage.

• The LT cards are rebooted to receive the new software image and the ONT units are restarted.

• Management access will resume for both the IP access and craft access.

• The LT cards become operational and traffic will be reestablished as the ONT units come up.

• NT-A comes up with the new software image and syncs to the active NT (NT-B)

• NT-B remains the active NT after the system has restarted with the new software image and migrated database.

Note: Craft port access to the system is interrupted for approximately 20 minutes.

3.7. Activate the Installed ONT Software

1. Edit the target ONT by setting the planned software version to the new ONT software load name:


EDEDEDED----ONT::ONT::ONT::ONT::ONTONTONTONT----1111----1111----1111----1111----1111::::SWVERPLND=::::SWVERPLND=::::SWVERPLND=::::SWVERPLND=3FE506453FE506453FE506453FE50645xxxxyyxxxxyyxxxxyyxxxxyy;;;;

/* ED-ONT::ONT-1-1-1-1-1::::BTRYBKUP=,BERINT=,DESC1=,DESC2=,PROVVERSION=, */ /* SERNUM=,SUBSLOCID=,SWVERPLND=3FE50853AHCA10,FECUP=,SCHEDPROFID=,SCHEDP */ /* ROFNM=,POWERSHEDPROFID=,POWERSHEDPROFNM=,ONTENABLE=,OPTICSHIST=,PLNDVA */ /* R=,DLSW=,RFFILTER=,SLIDVISIBILITY=:IS */

"ONT-1-1-1-1-1:MN,SWDLIP,NSA,1-4,4-10-45:\"ONT SWDL In ProgressONT SWDL In ProgressONT SWDL In ProgressONT SWDL In Progress\"";

2. Retrieve the ONT information to verify that the software has successfully downloaded:

RTRVRTRVRTRVRTRV----ONT::ONTONT::ONTONT::ONTONT::ONT----1111----1111----1111----1111----1;1;1;1; RTRV-ONT::ONT-1-1-1-1-1::;

/* RTRV-ONT::ALL:: */ "ONT-1-1-1-1-1::BTRYBKUP=NO,BERINT=8000,DESC1=\"NULL\",DESC2=\"NULL\", PROVVERSION=\"*\",SERNUM=ALCLF9A3A879,YPSERNUM=UNKNOWN, SUBSLOCID=\"WILDCARD\",SWVERPLND=\"3FE50853AHCA10\",FECUP=DISABLE, SCHEDPROFID=1,SCHEDPROFNM=\"defSubSchedProf\",POWERSHEDPROFID=0,



POWERSHEDPROFNM=\"NULL\",ONTENABLE=AUTO,P2PENABLE=DISABLE, RATELIMITOPT=DISABLE,OPTICSHIST=DISABLE,PLNDVAR=\"\", DLSW=\"3FE50853AHCA10\",EQPTVERNUM=3FE50754ADAC01,SWVERACT=3FE50853AHCA103FE50853AHCA103FE50853AHCA103FE50853AHCA10, SWVERPSV=3FE50854AHAA26,VENDORID=ALCL,EQUIPID=BVM4P10DRAI221EA,NUMSLOTS=3,

NUMTCONT=21,NUMTRFSCH=20,NUMPQ=0,RFFILTER=2,SLIDVISIBILITY=DISABLED:IS-NR"

3. STOP. This procedure is complete.



3.8. Post-Software Migration Checklist Post- Software Migration Checklist Applied

1

Verify that 7342 ISAM FTTU is reachable by remote management system after the target software release is activated with linked DB

2 Verify that ONT software version is set to planned version according to Section 3.7

3 Verify that the software has successfully downloaded by retrieving the ONT information

Exit Criteria

The “Software Migration” section should be completed.

Table 11: Post-Software Migration Checklist



APPENDIX A. INDEX OF TABLES

TABLE 1 : DOCUMENT REVISION HISTORY .................................................................................. 3

TABLE 2 : DOCUMENT LIST ................................................................................................ 4

TABLE 3: SUPPORTED HARDWARE LIST .................................................................................... 5

TABLE 4 : SITE-VISIT INFORMATION CHECKLIST ............................................................................ 6

TABLE 5 : TOOLS AND DEVICES FOR SITE VISIT ............................................................................. 6

TABLE 6: PERSONNEL IN CHARGE .......................................................................................... 7

TABLE 7 : BOX CONFIGURATION ........................................................................................... 8

TABLE 8: TIMETABLE ...................................................................................................... 9

TABLE 9: PRE-SOFTWARE MIGRATION CHECKLIST .......................................................................... 9

TABLE 10: SOFTWARE MIGRATION CHECKLIST ........................................................................... 11

TABLE 11: POST-SOFTWARE MIGRATION CHECKLIST ..................................................................... 30



APPENDIX B. INDEX OF FIGURES

No table of figures entries found.



APPENDIX C. GLOSSARY

AMS Access Managament System DB Database FTP File Transfer Protocol FTTU Fiber to the User GPON Gigabit Passive Optical Network IP Internet Protocol ISAM Intelligent Services Access Manager LT Line Termination MOP Method of Procedure NE Network Element NT Network Termination

A card that provides a link to an Ethernet-based network. The 7342 ISAM FTTU uses the EHNT-A, EHNT-B or EXNT-A.

ODMT Offline Database Migration Tool OLT Optical Line Termination ONT Optical Network Termination OSWP Overall Software Package PC Personal Computer PON Passive Optical Network P-OLT Packet Optical Line Termination. The fully assembled shelf in the

7342 ISAM FTTU system. The P-OLT consists of two NT cards (for redundancy), one AACU card, and 18 LT cards.

GPEC Regional Product Expertise Center SHC System Health Check Tool SW Software TFTP Trivial File Transfer Protocol. A very simple means of transferring

files, popular in embedded systems because of its compactness. TL1 Transaction Language 1.

Human-machine language standard for controlling network elements. USB Universal Serial Bus

7342 isam fttu r4_8_x software migration mop rev2

Documents

unix text editor

lucent gpec team

file naming restriction

tl1 craft terminal

software migration mop

software migration checklist

db consistency check

redundant nt cards