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. APPENDIX B. APPENDIX C. INDEX OF TABLES ............................................................................... 31 INDEX OF FIGURES .............................................................................. 32 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
Page 3 of 33
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 9th December 2011 20 December 2011 9th August 2012
th
Version 1.0 1.1 1.2
Author Mehmet SOZBILIR Ilker ALBAYRAK Taner Ustebay
Change Document Creation Document Review 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.
Copyright Alcatel-Lucent GPEC TEAM
Page 4 of 33
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.alcatellucent.com/Teams/GCDNetworks/WirelineGPEC/default.aspx
1.6. 7342 ISAM FTTU Documents at GPEC Site

No
1 2 3 4 5 6 7 8
Document Name
Hardware Installation MoP Software Installation & Field Integration MoP Acceptance Test Procedure Software Upgrade MoP Software Migration MoP Backup and Restore Procedure Password Recovery Procedure NE Discovery Procedure
Table 2 : Document List
Page 5 of 33
1.7. Supported Hardware List for Release 4.8.X

Release features for R04.08.06 None Release features for R04.08.0 None Release features for R04.07.81 None Release features for R04.07.50 None Release features for R04.07.20 40km bidirectional SFP Support for the EXNT-A 3FE51230AC Release features for R04.07.11 None Release features for R04.07.10 None Release features for R04.07.04 New GLT4-D that supports C+ optics Release features for R04.07.00 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
Page 6 of 33
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
1 2 3 4 5 6
Information
Box Configurations Site Address & Location Site Security Permission Site Contact Person Scope of Work Remote Access Configurations
Explanation
See the Box Configuration section in this chapter. Do you have additional config file to apply the box? Do you have the information to go there? Did you arrange the site security permission for the planned date & time? Who (from the customer site) will be in charge for your visit? Do you know what operations/tasks will you be responsible for? Do you have a written statement confirmed by the customer? 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
1 2 3 4 5 6 7 8 9 10 11 12 14 15
Material
Console Cable Antistatic wrist strap External USB Hard Disk USB Flash Disk USB Card Reader Screw Driver Multimeter Pen and paper Labeling Stickers Fiber Cable Rack Mount Kits Laptop with Com port or USB to Serial convertor (Male) Terminal Program X-Windows Client
For Use
To connect to the box locally Always use the antistatic wrist strap before you touch the hardware To store Backups, SW loads, configurations Document and file sharing/transfer with the customer or 3rd parties For accessing the flash cards of devices To mount a fresh product on-site / To tighten the loose screws To check the electricity on a wire/plug/hw To take notes while sharing some information with the customer Different sized of stickers to label the box, cable endpoints etc. For uplink connections
For example Putty, MS Terminal, Hummingbird For example XManager, Hummingbird - Exceed
Table 5 : Tools and Devices for site visit
Page 7 of 33
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.
Page 8 of 33
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 Serial Number Role Redundancy Hardware Model Serial Number Additional Cards and Serial Numbers Compact Flash Memory Power Supply Faults Management TCP/IP Configuration Geographical location of device, e.g. Istanbul/Sisli Enter chassis serial number here e.g. Subtending, Hub etc. e.g. power redundancy, NT redundancy etc. e.g. 7302 ISAM FD, 7330 ISAM FTTN, 7342 ISAM FTTU etc. Enter chassis serial number here Enter the serial numbers of other cards (NT, LT, NTIO) here e.g. CF 2GB What are the power requirements of the device? Any faults observed at the end of installation? 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.alcatellucent.com/release/jsp/sso/login.jsp).
Page 9 of 33
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 Proposed End Start Date/Time Date/Time
21st Dec 21:30 21st Dec 21:40
Actual Start Date/Time
Actual End Date/Tim e
eg. Personnel Check 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

1 2 3 Verify that you have remote connection to management server Verify that you have username and password for Unix login Verify that you have usernames and passwords to login via CLI/TL1 to 7342 ISAM FTTU node
Table 9: Pre-Software Migration Checklist
Applied
Page 11 of 33
3. SOFTWARE MIGRATION
3.1. Software Migration Checklist
Software Migration Checklist
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 Verify that 5520 AMS server is acting as a TFTP server Ex: bash-3.00# netstat -a | grep tftp *.tftp Idle Ping the 7342 ISAM FTTU to verify that the system can be reached from the TFTP client Verify the default /tftpboot folder resides on the system Verify that all the files of 7342 ISAM FTTU OSWP are copied to your TFTP Servers home directory Verify the software package is extracted in TFTP Servers home directory Verify the descriptor file is edited according to Section 3.2.2 Display the OSWP list and see the available OSWP on 7342 ISAM FTTU EX: REPT-OPSTAT-OSWP::ALL::. Ref: Section 3.3 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 Verify that the download for new software from TFTP server to the NT card is completed Ref: Section 3.3 Verify that new software (OSWP) is committed after completing download operation Verify the new software version If the system has redundant NT cards, verify that the NTs are synchronized Section Ref: Section 3.3 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 Verify that ONT software is copied to the TFTP Servers home directory Verify that ONT software executable file is downloaded from TFTP server to P-OLT node via TFTP Verify that the ONT software file resides on the NT file system Verify that ONT software is downloaded in passive state Verify that the 7342 ISAM FTTU is alarm free 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 Verify the backup of the current database to be used for the migration Verify that active databases are uploaded from the OLT to the TFTP server via the TL1 craft terminal. Section 3.6 Verify the upload status is changed from ongoing to success Verify the backup copy of the dm_complete.tar file resides on a safe location Verify the environment is set for the library path and actual path Verify the migration sequence is completed Verify that migrated database is prepared for downloading to the OLT by changing the file name to dm_complete.tar Verify the operational status of the OSWP Verify the status of the downloaded database. Section 3.6 Verify that the target software release is activated. Section 3.6
Table 10: Software Migration Checklist
Applied
Page 12 of 33
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/)
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 /TFTP_ROOT_FOLDER mkdir directory
Where directory is the name of the directory you want to create:

bash-3.00# cd ams/swm/ne/ bash-3.00# mkdir migration
Copy the software package from the CD to that directory:

cd directory cp /cdrom/cdrom0/FTTU/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 3digit software package number (for example, ML3NAA47.012)
bash-3.00# cd migration bash-3.00# scp ML3NAA48.080 root@172.29.7.249:/ams/swm/ne/migration root@172.29.7.249:/ams/swm/ne/migration
Page 13 of 33
Untar the software package:

tar -xvf ML3NAAxx.yyy bash-3.00# tar -xvf 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# cd /ams/swm/ne/migration/OSWP1
Change permissions:
Chmod 777 ML3MAAxx.yyy bash-3.00# chmod 777 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.yyy BEGIN SYNTAX-VERSION : 01.00; ASAM-CORE : <SW Package Path>/ML3NAAxx.yyy tftp_server_ip> Path>/ML3NAAxx.yyy <tftp_server_ip tftp_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.080 BEGIN SYNTAX-VERSION : 01.00; Copyright Alcatel-Lucent GPEC TEAM 3FQ 24064 48XG PGZZA
Page 14 of 33
ASAM-CORE END
: migration/ML3NAA48.080 172.29.7.249 0.0.0.0;
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:
REPTREPT-OPSTATOPSTAT-OSWP:[tid] OSWP:[tid]: [tid]:aid_sw: aid_sw:[ctag][:]; [ctag][:]; REPTREPT-OPSTATOPSTAT-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:
EDED-OSWP:[tid] OSWP:[tid]: [tid]:aid_sw: aid_sw:[ctag]::: [ctag]:::[sw_nblk] :::[sw_nblk] EDED-OSWP::OSWPOSWP::OSWP-2::::COMMITMENT=TRUE;
4. Download the OSWP from the TFTP server to the 7342 ISAM FTTU NT card:
DLDL-OSWP:[tid] OSWP:[tid]:: [tid]::[ctag] ::[ctag]:: [ctag]::dlservpri ::dlservpri, dlservpri,[dlservsec], [dlservsec],swpackagename; swpackagename;
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.
DLDL-OSWP:::::< OSWP:::::<tftp_server_ip> tftp_server_ip>,,<Path ,,<Path of SW Package>/ML3NAAxx.yyy Package>/ML3NAAxx.yyy; /ML3NAAxx.yyy; DLDL-OSWP:::::172.29.7.249 OSWP:::::172.29.7.249,, 172.29.7.249,,migration/OSWP1/ML3MAA48.080 ,,migration/OSWP1/ML3MAA48.080; migration/OSWP1/ML3MAA48.080;
Page 15 of 33
5. Monitor the progress of the download:

REPTREPT-OPSTATOPSTAT-OSWPDL::ALL:: Execute ? (Y,N) [Y] : IP 0 < M GPEC-7342-1 70-01-01 01:04:14 0 COMPLD /* rept-opstat-oswpdl::all:: */ "OSWP-1:DLPROGRESS,DOWNLOADING DOWNLOADING" DOWNLOADING "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.080 migration/OSWP1/ML3MAA48.080" migration/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:
EDED-OSWP::OSWPOSWP::OSWP-OSWP#::::ABORT=TRUE; EDED-OSWP::OSWP OSWP::OSWPOSWP-1::::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):
REPTREPT-OPSTATOPSTAT-NE::COM:: Execute ? (Y,N) [Y] : Copyright Alcatel-Lucent GPEC TEAM 3FQ 24064 48XG PGZZA
Page 16 of 33
IP 0 < M GPEC-7342-1 70-01-01 19:26:50 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.
Page 17 of 33
1. Copy the ONT software executable file from the CD to any directory on the TFTP client machine:
cp /cdrom/cdrom0/ONT/FE50645xxxxyy /MyDir/FE50645xxxxyy scp FE50853AHCA10 FE50853AHCA10 root@172.29.7.249:/ams/swm/ne/migration/
2. Ping the 7342 ISAM FTTU to verify that the system can be reached from the TFTP client:
ping 172.29.7.251
where: 172.29.7.249 identifies the IP management address. 3. Start a TFTP session to the 7342 ISAM FTTU:
tftp 172.29.7.251 172.29.7.251
4. Set transfer mode to binary:

bin
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 FE50645 FE50645xxxxyy /pub/Sw/Download/FE50645xxxxyy put FE50853AHCA10 /pub/Sw/Download/FE50853AHCA10 /pub/Sw/Download/FE50853AHCA10
6. End the TFTP session:

quit
Page 18 of 33
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:
RTRVRTRV-ONTSWVER:::::FE50645 ONTSWVER:::::FE50645xxxxyy;
where xxxxyy identifies the executable file for the particular ONT
/* RTRVRTRV-ONTSWVER::COM:::FE50853AHCA10 ONTSWVER::COM:::FE50853AHCA10 */ "COM::SWVER=\ \"FE50853AHCA10\ "COM::SWVER= "FE50853AHCA10\",SWVERSIZE=9489208"
3. Download ONT software that will be in the passive state. Assign an ONT software image for download to the ONT: where: xxxxyy identifies the executable file for your particular ONT.
SETSET-ONTDLSW::ONTONTDLSW::ONT-1-1-1-1-1::::DLSW=3FE50645 1::::DLSW=3FE50645xxxxyy; /* SETSET-ONTDLSW::ONTONTDLSW::ONT-1-1-1-1-1::::DLSW=3FE50853AHCA10 1::::DLSW=3FE50853AHCA10 */
4. Retrieve the ONT information to verify that the software has successfully downloaded:
RTRVRTRV-ONT::ONTONT::ONT-1-1-1-1-1; /* RTRV-ONT::ONT-1-1-1-1-1 */ "ONT-1-1-1-11::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.
Page 19 of 33
3.6. DB Backup and Migrate System Software to Target Software Load

1.Verify that the 7342 ISAM FTTU is alarm free:
RTRVRTRV-ALMALM-ALL:[tid]:[aid_all]:[ctag]::[ntfncde],,[serveff],[locn],[dirn] ALL:[tid]:[aid_all]:[ctag]::[ntfncde],,[serveff],[locn],[dirn]; [tid]:[aid_all]:[ctag]::[ntfncde],,[serveff],[locn],[dirn]; RTRVRTRV-ALMALM-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 /tftpboot bash-3.00# mkdir <tools_dir> bash-3.00# cd <tools_dir>
where tools_dir is a directory for the necessary tools used by the integrated SHCMigration script.
bash-3.00# bash-3.00# bash-3.00# cd /ams/swm/ne mkdir tools cd tools
II.
Insert the 7342 ISAM FTTU ODMT CD-ROM in the TFTP server CD-ROM drive. Copy SHC file, SHC_package.tar, from the 7342 ISAM FTTU ODMT CD-ROM to the new directory on the server:
III.
cp /cdrom/cdrom0/ODMT/SHC_package.tar /cdrom/cdrom0/ODMT/SHC_package.tar scp SHC_package.tar SHC_package.tar root@172.29.7.249:/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
Page 20 of 33
IV.
Untar the SHC package:
tar -xvf SHC_package.tar tar -xvf SHC.tar tar -xvf SHC_package.tar SHC_package.tar tar -xvf SHC.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 /cdrom/cdrom0/ODMT/MBYXAA47.yyy.tar /cdrom/cdrom0/ODMT/MBYXAA47.yyy.tar tar -xvf MBYXAA47.yyy scp MBYXAA48.080 root@172.29.7.249:/ams/swm/ne/tools tar xvf MBYXAA48.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):
REPTREPT-OPSTATOPSTAT-NE:[tid] NE:[tid]: [tid]:[aid_com]: [aid_com]:[ctag][:]; [ctag][:]; REPTREPT-OPSTATOPSTAT-NE;
Page 21 of 33
II.
Retrieve the current NT protection configuration, the protection switching mode should be allowed (ALW) and redundancy control state should be normal (NORMAL):
RTRVRTRV-SWDXSWDX-EQPT:[tid] EQPT:[tid]: [tid]:[aid_dxeqpt]: [aid_dxeqpt]:[ctag][:]; [ctag][:]; RTRVRTRV-SWDXSWDX-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:
ALWALW-SWDXSWDX-EQPT:[tid] EQPT:[tid]: [tid]:aid_dxeqpt: aid_dxeqpt:[ctag][::]; [ctag][::]; ALWALW-SWDXSWDX-EQPT::NT;
7.Create a backup of the current database to be used for the migration. I. From the TFTP server terminal:
cd /tftpboot/<tools_dir>/ touch dm_complete.tar chmod 777 dm_complete.tar bash-3.00# bash-3.00# bash-3.00# cd /ams/swm /ams/swm/ne/tools swm/ne/tools touch dm_complete.tar chmod 777 dm_complete.tar
II.
From the TL1 craft terminal, upload the active databases from the OLT to the TFTP server:
ULUL-DB:[tid] DB:[tid]:: [tid]::[ctag] ::[ctag]:: [ctag]::[ulserv] ::[ulserv], [ulserv],[ulpath], [ulpath],uldb; uldb; 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 ULUL-DB:::::172.29.7.249 DB:::::172.29.7.249, 172.29.7.249,ODMT/dm_complete.tar,AOSWPACT ODMT/dm_complete.tar,AOSWPACTUAL ,AOSWPACTUAL Execute ? (Y,N) [Y] : IP 0 < M GPEC-7342-1 70-01-01 05:28:27 0 COMPLD /* UL-DB:::::172.29.7.249,/tools/ODMT/dm_complete.tar,AOSWPACTUAL 3FQ 24064 48XG PGZZA
Page 22 of 33
*/ ;
III.
Verify the database upload status:
REPTREPT-OPSTATOPSTAT-DBUL:[tid] DBUL:[tid]:: [tid]::[ctag] ::[ctag][:]; [ctag][:];
The upload status should change from .ongoing,noerror to .success,noerror

REPTREPT-OPSTATOPSTAT-DBUL:::: Execute ? (Y,N) [Y] : IP 0 < M ; GPEC-7342-1 70-01-01 05:29:10 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:
bash export PATH=<pwd>/bin:$PATH:<pwd> export LD_LIBRARY_PATH=<pwd>/lib:<pwd>/sunlib:<pwd>/library
where <pwd> is the present working directory

#bash bash bash-3.00# bash-3.00# export PATH=/ams/swm/ne/ODMT/bin:$PATH: PATH=/ams/swm/ne/ODMT/bin:$PATH: /ams/swm/ne/ODMT bash-3.00# export LD_LIBRARY_PATH=/var/pkg/TclPro1.4/solarisLD_LIBRARY_PATH=/var/pkg/TclPro1.4/solarissparc/lib:/opt/ALAshc/lib:/ams/swm/ne/ODMT/sunlib:/ams/swm/ne/ODMT/l ibrary:/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.
Page 23 of 33
bash-3.00# set 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/solarissparc/lib:/opt/ALAshc/lib:/ams/swm/ne/ODMT/sunlib:/ams/swm/ne/ODMT/l ibrary:/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/solarissparc/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:interactivecomments: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.
Page 24 of 33
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 -in dm_complete.tar -from R4.7.50 -to 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.tar dm_migrated_120811.132544_16332.tar) dm_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.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.tar dm_migrated_120811.132544_16332.tar" dm_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-122011_13:28:03.html ==============================================================
Page 25 of 33
Download migrated database 11. Prepare the migrated database for downloading to the OLT by changing the file name to dm_complete.tar:
cp <outputDBfile> dm_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 dm_migrated_120811.132544_16332.tar dm_migrated_120811.132544_16332.tar dm_complete.tar
12. Verify the operational status of the OSWP:

REPTREPT-OPSTATOPSTAT-OSWP:[tid] OSWP:[tid]: [tid]:aid_sw: aid_sw:[ctag]; [ctag]; REPTREPT-OPSTATOPSTAT-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:
DLDL-DB:[tid] DB:[tid]:: [tid]::[ctag] ::[ctag]:: [ctag]::[dlserv] ::[dlserv], [dlserv],dlpath; dlpath;
DL-DB:::::<tftp_ip>,/<tools_dir>/dm_complete.tar; Where tftp_ip is the IP address of the TFTP server

DLDL-DB:::::172.29.7.249, DB:::::172.29.7.249,/tools/ODMT/ :::::172.29.7.249,/tools/ODMT/dm_complete.tar /tools/ODMT/dm_complete.tar Execute ? (Y,N) [Y] : IP 0 < M ; GPEC-7342-1 70-01-01 01:56:30 0 COMPLD /* DL-DB:::::172.29.7.249,/tools/ODMT/dm_complete.tar */
Page 26 of 33
II.
Verify the database download status:
REPTREPT-OPSTATOPSTAT-DBDL:::: DBDL:::: Execute ? (Y,N) [Y] : IP 0 < M ; GPEC-7342-1 70-01-01 01:56:46 0 COMPLD /* REPT-OPSTAT-DBDL:::: */ "SUCCESS,NOERROR,172.29.7.249,/tools/ODMT/dm_complete.tar"
14. Verify the status of the downloaded database.

REPTREPT-OPSTAT:DB; REPTREPT-OPSTATOPSTAT-DB::ALL:: Execute ? (Y,N) [Y] : IP 0 < M GPEC-7342-1 70-01-01 02:02:39 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
EDOSWPED-OSWP::OSWP -x::::ACTIVATION=WITHLINKEDDB; EDED-OSWP::OSWP OSWP::OSWPOSWP-1::::ACTIVATION=WITHLINKEDDB,COMMITMENT=,ABORT= Execute ? (Y,N) [Y] : IP 0 < M ; REPTREPT-OPSTATOPSTAT-OSWPDL::ALL:: Copyright Alcatel-Lucent GPEC TEAM 3FQ 24064 48XG PGZZA GPEC-7342-1 70-01-01 02:13:27 0 COMPLD /* ED-OSWP::OSWP-1::::ACTIVATION=WITHLINKEDDB,COMMITMENT=,ABORT= */
Page 27 of 33
Execute ? (Y,N) [Y] : IP 0 < M GPEC-7342-1 70-01-01 02:42:00 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"
; REPTREPT-OPSTATOPSTAT-OSWP::ALL:: Execute ? (Y,N) [Y] : IP 0 < M GPEC-7342-1 70-01-01 02:42:27 0 COMPLD /* REPT-OPSTAT-OSWP::ALL:: */ "OSWP-1:AVAILSTAT,ENABLED" "OSWP-1:ACTSTAT,ACTIVE ACTIVE" ACTIVE "OSWP-1:COMMITSTAT,UNCOMMITTED" "OSWP-2:AVAILSTAT,ENABLED" "OSWP-2:ACTSTAT,NOTACTIVE NOTACTIVE" NOTACTIVE "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.
Page 28 of 33
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 (NTB) 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: where: xxxxyy identifies the executable file for your particular ONT.
EDED-ONT::ONT ONT::ONTONT-1-1-1-1-1::::SWVERPLND=3FE50645 ::::SWVERPLND=3FE50645xxxxyy;
/* 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 ONT SWDL In Progress\""; Progress
2. Retrieve the ONT information to verify that the software has successfully downloaded:
RTRVRTRV-ONT::ONTONT::ONT-1-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, Copyright Alcatel-Lucent GPEC TEAM 3FQ 24064 48XG PGZZA
Page 29 of 33
POWERSHEDPROFNM=\"NULL\",ONTENABLE=AUTO,P2PENABLE=DISABLE, RATELIMITOPT=DISABLE,OPTICSHIST=DISABLE,PLNDVAR=\"\", DLSW=\"3FE50853AHCA10\",EQPTVERNUM=3FE50754ADAC01,SWVERACT=3FE50853AHCA10 3FE50853AHCA10, 3FE50853AHCA10 SWVERPSV=3FE50854AHAA26,VENDORID=ALCL,EQUIPID=BVM4P10DRAI221EA,NUMSLOTS=3, NUMTCONT=21,NUMTRFSCH=20,NUMPQ=0,RFFILTER=2,SLIDVISIBILITY=DISABLED:I S-NR"
3. STOP. This procedure is complete.
Page 30 of 33
3.8. Post-Software Migration Checklist

Post- Software Migration Checklist Verify that 7342 ISAM FTTU is reachable by remote management system after the target software release is activated with linked DB Verify that ONT software version is set to planned version according to Section 3.7 Verify that the software has successfully downloaded by retrieving the ONT information Exit Criteria Applied
1 2 3
The Software Migration section should be completed.
Table 11: Post-Software Migration Checklist
Page 31 of 33
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
Page 32 of 33
APPENDIX B. INDEX OF FIGURES

No table of figures entries found.
Page 33 of 33
APPENDIX C. GLOSSARY
AMS DB FTP FTTU GPON IP ISAM LT MOP NE NT Access Managament System Database File Transfer Protocol Fiber to the User Gigabit Passive Optical Network Internet Protocol Intelligent Services Access Manager Line Termination Method of Procedure Network Element 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. Offline Database Migration Tool Optical Line Termination Optical Network Termination Overall Software Package Personal Computer Passive Optical Network 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. Regional Product Expertise Center System Health Check Tool Software Trivial File Transfer Protocol. A very simple means of transferring files, popular in embedded systems because of its compactness. Transaction Language 1. Human-machine language standard for controlling network elements. Universal Serial Bus
ODMT OLT ONT OSWP PC PON P-OLT
GPEC SHC SW TFTP TL1 USB

7342 ISAM FTTU R4 - 8 - X Software Migration MOP Rev2

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

7342 ISAM FTTU R4 - 8 - X Software Migration MOP Rev2

Transféré par

Droits d'auteur :

Formats disponibles

7342 ISAM FTTU R4.8.

X SOFTWARE MIGRATION MOP

Author: Mehmet SOZBILIR Alcatel-Lucent Turkey

3FQ 24064 48XG PGZZA