3 HH 12424 Aaaatczza 01

DPOE SOFTWARE MIGRATION GUIDE
Alcatel-Lucent 7360 ISAM FX

INTELLIGENT SERVICES ACCESS MANAGER FX | RELEASE 5.x
DPOE SOFTWARE MIGRATION GUIDE
3HH-12424-AAAA-TCZZA Edition 01
Alcatel-Lucent Proprietary
This document contains proprietary information of Alcatel-Lucent and is not to be disclosed
or used except in accordance with applicable agreements.
Copyright 2014 Alcatel-Lucent. All rights reserved.
Alcatel-Lucent assumes no responsibility for the accuracy of the information presented, which is
subject to change without notice.
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All
other trademarks are the property of their respective owners.
Copyright 2014 Alcatel-Lucent.
All rights reserved.
Disclaimers
Alcatel-Lucent products are intended for commercial uses. Without the appropriate network design
engineering, they must not be sold, licensed or otherwise distributed for use in any hazardous
environments requiring fail-safe performance, such as in the operation of nuclear facilities, aircraft
navigation or communication systems, air traffic control, direct life-support machines, or weapons
systems, in which the failure of products could lead directly to death, personal injury, or severe physical
or environmental damage. The customer hereby agrees that the use, sale, license or other distribution
of the products for any such application without the prior written consent of Alcatel-Lucent, shall be at
the customer's sole risk. The customer hereby agrees to defend and hold Alcatel-Lucent harmless from
any claims for loss, cost, damage, expense or liability that may arise out of or in connection with the
use, sale, license or other distribution of the products in such applications.
This document may contain information regarding the use and installation of non-Alcatel-Lucent
products. Please note that this information is provided as a courtesy to assist you. While Alcatel-Lucent
tries to ensure that this information accurately reflects information provided by the supplier, please refer
to the materials provided with any non-Alcatel-Lucent product and contact the supplier for
confirmation. Alcatel-Lucent assumes no responsibility or liability for incorrect or incomplete
information provided about non-Alcatel-Lucent products.
However, this does not constitute a representation or warranty. The warranties provided for
Alcatel-Lucent products, if any, are set forth in contractual documentation entered into by
Alcatel-Lucent and its customers.
This document was originally written in English. If there is any conflict or inconsistency between the
English version and any other version of a document, the English version shall prevail.
When printed by Alcatel-Lucent, this document is printed on recycled paper.
Preface
This preface provides general information about the DPoE Software Migration
Guide.
Scope
This document provides general and safety information and includes procedures for
DPoE software migration and upgrade procedures.
Applicable releases
This edition of the DPoE Software Migration Guide is applicable for all R5.x
releases from R5.0.01 on.
Audience
This documentation set is intended for planners, administrators, operators, and
maintenance personnel involved in installing, upgrading, or maintaining a DPoE
system.
Prerequired knowledge
The reader must be familiar with general telecommunications principles.
Alcatel-Lucent DPoE Software Migration Guide R5.0.01

June 2014 3HH-12424-AAAA-TCZZA Edition 01
iii
Preface
Assistance and ordering phone numbers

Alcatel-Lucent provides global technical support through regional call centers.
Phone numbers for the regional call centers are available at the following URL:
http://www.alcatel-lucent.com/myaccess
For ordering information, contact your Alcatel-Lucent sales representative.
Safety information
The following are examples of how special information is presented in this
document.
Danger Danger indicates that the described activity or situation
may result in serious personal injury or death; for example, high

voltage or electric shock hazards.
Warning Warning indicates that the described activity or situation
may, or will, cause equipment damage or serious performance

problems.
Caution Caution indicates that the described activity or situation
may, or will, cause service interruption.
Note A note provides information that is, or may be, of special
interest.
Document conventions
The following conventions are used in this documentation set.
Release notes
See the release notes (such as the customer release notes or emergency fix release
note) issued for software loads of the 7360 ISAM FX before you install or use the
7360 ISAM FX. The release notes provide important information about the software
load.
iv

Contents
Preface
iii
Scope
............................................................................................... iii
Applicable releases .................................................................................... iii
Audience ............................................................................................... iii
Prerequired knowledge ............................................................................... iii
Assistance and ordering phone numbers ........................................................... iv
Safety information ..................................................................................... iv
Document conventions ................................................................................ iv
Release notes........................................................................................... iv
Introduction
1.1
1.2
1-1
Introduction .............................................................................. 1-2

How to use this document ............................................................. 1-3
Non-Trouble Procedures (NTP)

NTP 100
Upgrade the software

NTP 100-1
Contents
Detailed Level Procedures (DLP)

DLP 100
Backup the database and upload to TFTP

server
DLP 100-1
DLP 101
Change the database name
DLP 101-1
DLP 102
Commit the current software release
DLP 102-1
DLP 103
Download a migrated database
DLP 103-1
DLP 104
Download the new software release
DLP 104-1
DLP 105
Activate the new software release and/or

database
DLP 105-1
Abort download of a new software release
DLP 106-1
DLP 106
vi

Introduction
1.1 Introduction
1-2
1.2 How to use this document

1-3
1-1
1 Introduction
1.1
Introduction
This document contains the DPoE migration and software update procedures.
This DPoE Software Migration Guide is intended to guide the user through the
process of doing major or minor release upgrades on the ISAM OLT. It is important
to understand how the software release and database containers are managed and
how the TFTP server(s) must be configured to successfully upload/download and
activate a software release updates.
Figure 1-1 shows the DPoE software migration process flow diagram.
Figure 1-1 DPoE software migration process flow diagram
Backup
Database
Upload File to
TFTP Server
Migrate DB
Off-line
Download
new
DB to ISAM
Yes
Off-line DB
Migration
Required?
No
Commit Current
Software Release
on ISAM
Download New
Software Release
from TFTP Server
Rollback to
Old Software
Release
Activate New
Software
Release
Complete
24310
There must not be any unexplained system alarms or other problems in the system
before you perform the procedures in this document. Alcatel-Lucent recommends
that you back up your current database before you perform an upgrade or migration.
1-2

1 Introduction
1.2
How to use this document

This document follows the task-oriented practice (TOP). The TOP method is a
documentation system that uses different types of layers, or documents, to describe
the installation, operations, and maintenance of telecommunications equipment and
software. Most layers in the TOP system provide step-by-step instructions for the
completion of a specific task or procedure.
A TOP document is structured so that experienced and less experienced users can
effectively use the material to perform work assignments. Less experienced users can
refer to detailed procedures to complete a task. Experienced users can bypass
detailed procedures and use only the level of information that they need.
TOP layers
TOP documentation is constructed in layers, which provide the user with easy access
to any point within the task description. This guide and other guides referenced from
this guide may contain any of the following layers:
Index List (IXL)

Non-Trouble Procedure (NTP)
Detailed Level Procedure (DLP)
Routine Task Procedure (RTP)
Trouble Analysis Procedure (TAP)
Training (TNG)
Figure 1-2 shows the major paths of TOP layers that may be used in this guide.
Figure 1-2 TOP layers and major paths
Index List
(IXL)
Non-Trouble
Procedure
(NTP)
Routine Task
Procedure
(RTP)
Trouble Analysis
Procedure
(TAP)
Training
(TNG)
Detailed Level
Procedure
(DLP)
17664
Task index list (IXL)
An IXL lists the available tasks in the TOP document. An IXL is used to find a task
category and the applicable procedures to perform a task.

1-3
1 Introduction
Non-trouble procedure (NTP)
An NTP describes how to perform a task, such as how to save a system after it has
been installed, turn up a system for service, or maintain a system according to a
maintenance plan. NTPs are made up of steps that often refer to DLPs or TNGs. Less
experienced users, or experienced users who need more information, can go to the
DLPs for detailed procedural and safety information, and TNGs for supporting
information. If users go to the referenced DLP or TNG, they must return to the NTP
to continue the procedure.
Detailed level procedure (DLP)
A DLP contains detailed steps that describe how to perform a task. In addition to
step-by-step information, a DLP contains any tables or illustrations that may be
required to perform the task.
DLPs are typically referenced from an NTP, always referenced from the IXL, and
sometimes referenced from other DLPs. When a DLP is referenced from another
layer, users must return to the layer at which the DLP was referenced to continue the
procedure.
Routine task procedure (RTP)
An RTP describes how to perform a routine maintenance task.

RTPs are typically referenced from the IXL.
Trouble analysis procedure (TAP)
A TAP describes how to identify and clear trouble in the system. TAPs are made up
of step-by-step instructions. For less experienced users, or experienced users who
need more information, some tasks provide a reference to a DLP or TNG. If users go
to the referenced DLP or TNG, they must return to the TAP to continue the
procedure.
Training (TNG)
A TNG contains supplementary information about a task or procedure. A TNG might

refer to a DLP or other document. If users go to the referenced document, they need
to return to the TNG to read the remaining information.
Step details
NTPs, DLPs, RTPs and TAPs use procedural steps and decision steps. Procedural
steps provide instructions, and decision steps provide a go-to choice.
Procedural steps may contain notations that refer to additional information such as
tables, figures, examples and other TOP layers. For example, a step in an NTP might
refer to a DLP.
Key information required to complete a step is shown at the beginning of the step.
More detailed information, which can be accessed according to experience level, is
provided at the end of the step, as shown in the example below:
Reconnect the power feeds; see DLP 106.
1-4

1 Introduction
The completion of a specific task or procedure is indicated as follows:

STOP. This procedure is complete.
Procedures with options or substeps

When there are options in a procedure, they are identified by letters. When there are
required substeps in a procedure, they are identified by Roman numerals.
Procedure 1-1 Example of options in a procedure

At step 1, you can choose option a or b. At step 2, you must do what the step indicates.
1
This step offers two options. You must choose one of the following:
a
This is one option.
This is another option.
You must perform this step.
Procedure 1-2 Example of required substeps in a procedure

At step 1, you must perform a series of substeps within a step. At step 2, you must do
what the step indicates.
1
This step has a series of substeps that you must perform to complete the step. You
must perform the following substeps:
i
This is the first substep.
ii
This is the second substep.
iii
This is the third substep.
You must perform this step.

1-5
1 Introduction
1-6

Non-Trouble Procedures (NTP)
NTP 100 Upgrade the software



Purpose
Use this NTP to upgrade the software for a DPoE system.
General
An upgrade is a system software update during which the database is not modified and
remains compatible with the original release. No new database is created.
Note Do not use this procedure when going from a major release to
another major release (for example from Release 4.0 to Release 4.1) or
if the Customer Release Notes for the new release indicates that you
need to perform a migration to go from the original release to the new
release. If you do, your current database will not be available to the
new software package.
Upgrading the software for NEs in a subtending configuration
In a subtending configuration, where subtended NEs are connected to the IP network
via a subtending NE, Alcatel-Lucent recommends that you upgrade all the subtended
NEs before upgrading the subtending NE. Because the subtended NEs use the
subtending NE for connectivity to the network, upgrading the subtended NEs and the
subtending NE at the same time can result in a communication disruption to the
subtended NEs, and a failed upgrade.
Prerequisites
Before you start this procedure, ensure that:
the DPoE system is operational

all operator commands have finished running

NTP 100-1
if you are using a customized operator profile, the defined prompt, if any, ends with
a trailing space; see the following documents for your product information about
configuring an operator profile:
Operations and Maintenance Using CLI for FD 100/320Gbps NT and FX NT
Operations and Maintenance Using TL1 for FD 100/320Gbps NT and FX NT
Procedure
Use this procedure to upgrade the DPoE system software using CLI. See the references
for detailed procedures.
NTP 100-2
Back up database and upload to TFTP server; see DLP 100.
Change the database name, see DLP 101.
Commit the current release; see DLP 102.
Download the migrated database; see DLP 103.
Download the new software release; see DLP 104.
Activate the new software release and/or database; see DLP 105.
Abort the new software download; see DLP 106.

Detailed Level Procedures (DLP)
DLP 100 Backup the database and upload to TFTP server

DLP 101 Change the database name
DLP 103 Download a migrated database
DLP 102 Commit the current software release
DLP 104 Download the new software release
DLP 105 Activate the new software release and/or database
DLP 106 Abort download of a new software release


DLP 100 Backup the database and

upload to TFTP server
Purpose
Use this DLP to use CLI to backup the database and upload to the TFTP server for a DPoE
system.
General
Before you upgrade the OS software, it is important to log information about the
existing system so that after the upgrade you can compare the same information to
verify that all components are installed and working as expected. During the process of
logging information, you might find an existing problem that you did not know about
and might have thought was caused by the upgrade.
Prerequisites
you have access to an EMS TFTP server accessible by the ISAM NEs
you are logged in as root to the EMS server
Procedure
Use this procedure to backup the database and upload to the TFTP server. You must be
logged in as root to perform this procedure. All the steps are performed using UNIX or
LINUX.
1
Backup the OLT and IHub database using the following commands:
admin save
admin software-mngt ihub database save-protected

DLP 100-1
DLP 100 Backup the database and upload to TFTP server
Save the current running database configuration to the TFTP server with the
following command:
admin software-mngt database upload actual-active:
10.10.10.1:dm_complete.tar
Note 1 If you desire to add a path to the filename, prefix the path
from TFTP root directory to the filename. In the following example,
ISAM/50 is the path:
admin software-mngt database upload
actual-active:10.10.10.1:ISAM/dm_complete.tar
Note 2 On the TFTP server, verify the dm_complete.tar file was

received and the size is greater than 0 bytes. This may take five minutes
to complete depending on the file size and connection speeds. File size
is expected to be from several hundred Kbytes to several Mbytes. This
will be dependent on the size of the OLT. If a paht is being used with
the file name, the read and write permissions must be allowed on every
directory, otherwise, this will lead to an upload failure. Use the
following command to show the file has been successfully uploaded on
the file server:
$ ls -ltr
Verify the database configuration has been written using the following command:
show software-mngt upload-download
DLP 100-2


Purpose
Use this DLP to change the database name on an off-line server.
General
The default name for the ISAM OLT database is NO_NAME or NoName.... The
database name can only be changed on an off-line server.
Prerequisites
the database is backed up and uploaded to the TFTP server
Procedure
Use this procedure to change the database name on an off-line system. You must be
logged in as root to perform this procedure. All the steps are performed using UNIX or
LINUX.
1
Create a temporary directory to change the database name and move the
database tar file to this directory using the following commands:
$ mkdir name_change
$ mv dm_complete.tar name_change/.
$ cd name_change
$ pwd
/tftpboot/name_change

DLP 101-1
Extract the files from the tar file (either dm.tar or dm_complete.tar) with the
following command:
$ tar -xof dm_complete.tar
$ ls
AutoSwitch
CDE
config
dm
dm.tar
Dpoe
Ipd
Edit the config file using the following command:

$ vi config
Check the file to make sure the name change is successful using the following
command:
$ cat config
name=NEW-OLT-NAME
version=A5.000
format=A5.000
tableIdFormat=1
errlog=false
trace=false
fileTraceType=0
fileTraceSize=0
traceTable=
traceTable1=
traceTable2=
traceTable3=
traceTable4=
Move the dm_complete.tar file to a temporary directory, so it is not accidentally

erased using the following commands:
$ cd /tftpboot
$ mkdir temp
$ mv name_change/dm_complete.tar temp/.
DLP 101-2

Create a new tar for the files in the name_change directory to a file named dm.tar
using the following commands:
$ cd name_change
$ tar -cvf dm.tar AutoSwitch CDE config dm/* Dpoe/* Ipd/*
$ ls -ltr dm.tar
-rw-r--r-- 1 root 1044480 2014-02-19 14:10 dm.tar
Note The dm.tar file is now located in the directory /tftpboot/temp

and is ready for download.

DLP 101-3
DLP 101-4

DLP 102 Commit the current software

release
Purpose
Use this DLP to commit the current software release for a DPoE system.
General
Committing the current software release is an action that is done before an upgrade.
When upgrading from a release A.0 to A.1. A.0 is only committed just before the A.1
software is downloaded. The commit action completes the following two actions:
changes the commit status from un-committed to committed

clears the non-active OSWP for download
Prerequisites
None.
Procedure
Use this procedure to commit the current software release.
1
Verify the software OSWP configuration using the following command:

show software-mngt oswp
Commit the active OSWP configuration using the following command:

admin software-mngt oswp 2 commit
Verify the post commit OSWP configuration using the following command:

DLP 102-1
DLP 102 Commit the current software release
DLP 102-2

DLP 103 Download a migrated

database
Purpose
Use this DLP to download a migrated database for a DPoE system.
General
The new database that was either migrated to the new release, or has a database name
change can be downloaded to the OLT using CLI.
Prerequisites
the database is either migrated to the new release or has a database name change
and the dm.tar or dm_complete.tar file is located in the directory ready for
download
Procedure
Use this procedure to download a new database (either migrated database or database
with a name change).
1
Download the new database using the following command:

admin software-mngt database download 10.10.10.1:/temp/dm.tar
Track the status of the download until you see a successful download using the
following command:
show software-mngt upload-download

DLP 103-1
DLP 103 Download a migrated database
Display the new database using the following command:

show software-mngt database
Note The system will show the new database is not loaded in the DB
container, however, the container labels (first/second/third) are not
important to note. It is important to note the following:
DLP 103-2
the name now matches the system name

the operational status is preferable
the version is correct

DLP 104 Download the new software

release
Purpose
Use this DLP to download the new software release for a DPoE system.
General
The new software release must be downloaded into an OSWP slot that has a name of
"NO_OSWP". The OSWP has two ways to get to this state. Committing the Active OSWP
or aborting a download that failed.
Prerequisites

download
the migrated or name changed database is downloaded
the current release must be committed
the new software release must be ready for download
Procedure
Use this procedure to download a new software release.
1
Verify the OSWP buffer configuration using the following command:


DLP 104-1
DLP 104 Download the new software release
Commit the active OSWP configuration using the following commands:

admin software-mngt oswp 1 commit
Verify the software servers have been configured using the following command:
info configure software-mngt oswp
configure software-mngt
If the server IP addresses are not configured, then configure the IP addresses using
the following commands:
configure software-mngt oswp 1 primary-file-server-id 10.10.10.1
configure the software-mngt oswp 2 primary-file-server-id
10.10.10.1
Download the new software release into the cleared OSWP slot using the following
command:
admin software-mngt oswp 2 download L6GPAA50.124
Verify the new software release is downloading using the following command:
Verify the new software release is downloaded using the following command:
DLP 104-2

DLP 105 Activate the new software

release and/or database
Purpose
Use this DLP to activate the new software release and/or database for a DPoE system.
Prerequisites

download
the migrated or name changed database is downloaded
the new software release must be downloaded
Procedure
Use this procedure to download a new software release.
1
Verify the OSWP buffer configuration using the following command:

Activate the new software release or database using the following command:
admin software-mngt oswp 2 activate with-linked-db
Note The process will take a few minutes.

DLP 105-1
DLP 105 Activate the new software release and/or database
Verify the status of the OSWP and the database using the following command:
show software-mngt database
Verify the new software release is downloaded using the following command:
DLP 105-2

DLP 106 Abort download of a new

software release
Purpose
Use this DLP to abort a download of a new software release for a DPoE system.
General
Occasionally, a software release will not download correctly. This can be from
specifying the wrong TFTP file location, having an incorrect L6GPAAxx.yyy file, or have
the directory permissions incorrectly set. This DLP provides steps on how to abort the
download so that another download can be attempted.
Prerequisites

Procedure
Use this procedure to abort a download of a new software release.
1
Clear the OSWP index 2 using the following command:

admin software-mngt oswp 2 abort-download
Display the OSWP table to verify that the OSWP index is cleared and ready for
download using the following command:

DLP 106-1
DLP 106 Abort download of a new software release
DLP 106-2

Customer documentation and product support
Customer documentation
http://www.alcatel-lucent.com/myaccess
Product manuals and documentation updates are available at
alcatel-lucent.com. If you are a new user and require access to this
service, please contact your Alcatel-Lucent sales representative.
Technical Support
http://support.alcatel-lucent.com
Documentation feedback
documentation.feedback@alcatel-lucent.com
2014 Alcatel-Lucent. All rights reserved.

3HH-12424-AAAA-TCZZA Edition 01

3 HH 12424 Aaaatczza 01

Uploaded by

Copyright:

Available Formats

3 HH 12424 Aaaatczza 01

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

3 HH 12424 Aaaatczza 01

Uploaded by

Copyright:

Available Formats

DPOE SOFTWARE MIGRATION GUIDE

Alcatel-Lucent 7360 ISAM FX

When printed by Alcatel-Lucent, this document is printed on recycled paper.

Alcatel-Lucent DPoE Software Migration Guide R5.0.01

Assistance and ordering phone numbers

may result in serious personal injury or death; for example, high

may, or will, cause equipment damage or serious performance

Note A note provides information that is, or may be, of special

Alcatel-Lucent DPoE Software Migration Guide R5.0.01

Introduction .............................................................................. 1-2

Non-Trouble Procedures (NTP)

Upgrade the software

Alcatel-Lucent DPoE Software Migration Guide R5.0.01

Detailed Level Procedures (DLP)

Backup the database and upload to TFTP

Change the database name

Commit the current software release

Download a migrated database

Download the new software release

Activate the new software release and/or

Abort download of a new software release

Alcatel-Lucent DPoE Software Migration Guide R5.0.01

1.2 How to use this document

Alcatel-Lucent DPoE Software Migration Guide R5.0.01

Alcatel-Lucent DPoE Software Migration Guide R5.0.01

How to use this document

Index List (IXL)

Task index list (IXL)

Alcatel-Lucent DPoE Software Migration Guide R5.0.01

Non-trouble procedure (NTP)

An RTP describes how to perform a routine maintenance task.

A TNG contains supplementary information about a task or procedure. A TNG might

Alcatel-Lucent DPoE Software Migration Guide R5.0.01

The completion of a specific task or procedure is indicated as follows:

Procedures with options or substeps

Procedure 1-1 Example of options in a procedure

This is one option.

This is another option.

You must perform this step.

Procedure 1-2 Example of required substeps in a procedure

This is the first substep.

This is the second substep.

This is the third substep.

You must perform this step.

Alcatel-Lucent DPoE Software Migration Guide R5.0.01

Alcatel-Lucent DPoE Software Migration Guide R5.0.01

Non-Trouble Procedures (NTP)

NTP 100 Upgrade the software

Alcatel-Lucent DPoE Software Migration Guide R5.0.01

Alcatel-Lucent DPoE Software Migration Guide R5.0.01

NTP 100 Upgrade the software

the DPoE system is operational

Alcatel-Lucent DPoE Software Migration Guide R5.0.01

NTP 100 Upgrade the software

Back up database and upload to TFTP server; see DLP 100.

Change the database name, see DLP 101.

Commit the current release; see DLP 102.

Download the migrated database; see DLP 103.

Download the new software release; see DLP 104.