3hh044590172fmzza01

7

3HH 04459 0172 FMZZA Ed01

RL- 13/Jun/2013

Push-button Migration Tool

V3.1.13

Release Note

All rights rese

rved. P

assing on and copying of this

docu

ment, use and communication of its co

ntents

not perm

itted w

ithout written authoriza

tion from Alcatel.

3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 2/176

Status Released

Change Note

Title Release Note

All rights reserved. Passing on and copying of this

document, use and communication of its contents not

permitted without written authorization from Alcatel.

All rights rese

rved. P


docu


ntents

not perm

itted w


tion from Alcatel.

3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 3/176

Contents

About this Document .......................................................................... 19

New about this toolset ........................................................................ 19

Support of SSH ................................................................................................. 19

Support of SNMPv2c or SNMPv3 .............................................................. 20

Support of ftp and sftp .................................................................................. 20

Support NE families ........................................................................................ 21

1 Content of the Release ................................................................. 22

1.1 V3.1.13 ...................................................................................................... 22 1.1.1 Error corrections .................................................................... 22

1.2 V3.1.12 skipped (delivery error) ....................................................... 23



1.5 V3.1.9 ......................................................................................................... 24 1.5.1 Error corrections .................................................................... 24








1.13 V3.1.0 & V3.1.1 (skipped) ................................................................... 27

1.14 V3.0.99 ...................................................................................................... 27 1.14.1 New requirements ................................................................ 27

1.15 V3.0.98 ...................................................................................................... 28

1.15.1 Error corrections

All rights rese

rved. P


docu


ntents

not perm

itted w


tion from Alcatel.

3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 4/176





















All rights rese

rved. P


docu


ntents

not perm

itted w


tion from Alcatel.

3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 5/176





















All rights rese

rved. P


docu


ntents

not perm

itted w


tion from Alcatel.

3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 6/176





















1.76 V3.0.37 ...................................................................................................... 56

All rights rese

rved. P


docu


ntents

not perm

itted w


tion from Alcatel.

3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 7/176

1.76.1 Error corrections .................................................................... 56

















1.93 V3.0.20 ...................................................................................................... 65 1.93.1 New requirements ................................................................ 65 1.93.2 Error corrections .................................................................... 65



All rights rese

rved. P


docu


ntents

not perm

itted w


tion from Alcatel.

3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 8/176



1.98 V3.0.15 ...................................................................................................... 67 1.98.1 Error corrections / Workarounds .................................... 67

1.99 V3.0.14 skipped ..................................................................................... 67

1.100 V3.0.13 .................................................................................................... 67 1.100.1 Error corrections .................................................................... 67

1.101 V3.0.12 skipped (delivery error) .................................................... 67














1.115 V2.1.63 skipped (delivery error) .................................................... 76


All rights rese

rved. P


docu


ntents

not perm

itted w


tion from Alcatel.

3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 9/176









1.125 V2.1.53 .................................................................................................... 80 1.125.1 New requirements ................................................................ 80







1.132 V2.1.46 .................................................................................................... 84 1.132.1 Error corrections .................................................................... 84 1.132.2 New requirements ................................................................ 84




1.136 V2.1.42 .................................................................................................... 87 1.136.1 Error corrections

All rights rese

rved. P


docu


ntents

not perm

itted w


tion from Alcatel.

3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 10/176


1.138 V2.1.40 .................................................................................................... 88 1.138.1 New requirements ................................................................ 88 1.138.2 Error corrections .................................................................... 88
















All rights rese

rved. P


docu


ntents

not perm

itted w


tion from Alcatel.

3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 11/176



1.156 V2.1.22 ................................................................................................. 100 1.156.1 Error corrections ................................................................. 100

1.157 V2.1.21 ................................................................................................. 100 1.157.1 New requirements ............................................................. 100






1.163 V2.1.15 ................................................................................................. 102 1.163.1 Error corrections ................................................................. 102 1.163.2 New requirements ............................................................. 103






1.169 V2.1.9 ................................................................................................... 105 1.169.1 Error corrections ................................................................. 105 1.169.2 New requirements ............................................................. 106

1.170 V2.1.8 ................................................................................................... 106 1.170.1 Error corrections ................................................................. 106



All rights rese

rved. P


docu


ntents

not perm

itted w


tion from Alcatel.

3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 12/176

1.173 V2.1.5 ................................................................................................... 108 1.173.1 New requirements ............................................................. 108

1.174 V2.1.4 (skipped) ............................................................................... 108

1.175 V2.1.3 ................................................................................................... 108 1.175.1 Error corrections ................................................................. 108 1.175.2 New requirements ............................................................. 108


1.177 V2.1.1 ................................................................................................... 109 1.177.1 New requirements ............................................................. 109 1.177.2 Error corrections ................................................................. 110

1.178 V2.1.0 (skipped) ............................................................................... 110







1.185 V2.0.34 ................................................................................................. 112 1.185.1 New requirements ............................................................. 112 1.185.2 Error corrections ................................................................. 113







1.192 V2.0.27 ................................................................................................. 116 1.192.1 New requirements

All rights rese

rved. P


docu


ntents

not perm

itted w


tion from Alcatel.

3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 13/176



1.195 V2.0.24 ................................................................................................. 118 1.195.1 New requirements ............................................................. 118 1.195.2 Error corrections ................................................................. 118 1.195.3 Improvements ..................................................................... 118











1.206 V2.0.13 skipped (delivery error) ................................................. 124




All rights rese

rved. P


docu


ntents

not perm

itted w


tion from Alcatel.

3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 14/176

1.210 V2.0.9 (skipped) ............................................................................... 126


1.212 V2.0.7 ................................................................................................... 126 1.212.1 New requirements ............................................................. 126 1.212.2 Error corrections ................................................................. 127

1.213 V2.0.6 (skipped) ............................................................................... 127



1.216 V2.03 .................................................................................................... 128 1.216.1 Error corrections ................................................................. 128

1.217 V2.0.2 (skipped) ............................................................................... 129













1.230 V1.7.8 ................................................................................................... 134

All rights rese

rved. P


docu


ntents

not perm

itted w


tion from Alcatel.

3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 15/176

1.230.1 New requirements ............................................................. 134














1.244 V1.5.24 ................................................................................................. 139 1.244.1 Error corrections ................................................................. 139 1.244.2 Improvements ..................................................................... 140




1.248 V1.5.20 (skipped) ............................................................................. 142


All rights rese

rved. P


docu


ntents

not perm

itted w


tion from Alcatel.

3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 16/176

1.250 V1.5.18 (skipped) ............................................................................. 143











1.261 V1.5.7 (skipped) ............................................................................... 148


1.263 V1.5.5 ................................................................................................... 148 1.263.1 Error corrections ................................................................. 148 1.263.2 Improvements ..................................................................... 148






All rights rese

rved. P


docu


ntents

not perm

itted w


tion from Alcatel.

3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 17/176








1.276 V1.4.64 ................................................................................................. 154 1.276.1 Improvements ..................................................................... 154











All rights rese

rved. P


docu


ntents

not perm

itted w


tion from Alcatel.

3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 18/176

1.287 V1.4.53 ................................................................................................. 158 1.287.1 Error corrections and workarounds ............................ 158 1.287.2 Improvements ..................................................................... 159

1.288 V1.4.52 ................................................................................................. 159 1.288.1 Error corrections and workarounds ............................ 159





1.293 V1.4.38 ................................................................................................. 166 1.293.1 Error corrections and workarounds ............................ 166 1.293.2 Improvements ..................................................................... 168 1.293.3 New requirements ............................................................. 168

Prerequisites ....................................................................................... 169

2 Delivery Information .................................................................. 170

3 Installation Guide ........................................................................ 176

4 Documentation ........................................................................... 176

About this Document

3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 19/176

About this Document This document provides information on content of release V3.1.13

of the Push-button migration tool and contains the changes

introduced versus V3.1.11. The complete overview of changes

since V1.4.38 is also maintained.

Please read this entire document before installing this release.

This release superseded the previous package and is functionally

backwards compatible.

New about this toolset Starting from V3.0.1 following feature has been incorporated in the toolset:

• TL1 support for ONT related operations

Starting from V2.1 some new features have been incorporated in the toolset:

• Support of SSH for CLI

• Support of SNMPv2c and SNMPv3

• Support of ftp and sftp

• Support of NE families

Support of SSH

PBMT tools can use SSH for CLI sessions when SSH is the only communication

channel configured in the ISAM. By default both CLI and TL-1 are enabled via both

the secured and non-secured communication channels. Communication via the

non-secure channels can be disabled by means of the appropriate CLI or LT-1

commands. The username and password defined for the CLI sessions still apply.

However in order to work in a sercured way it is recommended to add the ISAMs as

known nodes to the system’s configuration where PBMT will be executed (the nodes

end up in the /etc/ssh/known_hosts file). By doing so an SSH session to a node will

never be a session to a node not known to the system and hence the connection

will be accepted, if not the connection will be refused.

Note: from V2.1.17, PBMT scripts will autonomously determine whether CLI over

SSH or CLI over Telnet is available. Depending on the access possibilities PBMT will

either use SSH or Telnet:

• No CLI over Telnet: PBMT scripts will use SSH for CLI communication

• CLI over Telnet and SSH: PBMT scripts will

New about this toolset

3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 20/176

use Telnet for CLI communication

• TL1 over UDP: PBMT scripts will use UDP communication to port 13001 on

the ISAM.

• TL1 over SSH: PBMT scripts will use SSH for TL-1 communication.

Communication established using port 1022 on the ISAM.

• No TL1: all TL-1 access will be skipped.

Configuring SSH is described in DLP-170 of the Operations and Maintenance using

CLI customer documentation.

Support of SNMPv2c or SNMPv3

SNMPv2c and SNMPv3 support is provided in this new version of the toolset.

SNMPv2c can be enabled by providing the --v2 option (the SNMPv1 community

string still applies for SNMPv2c).

SNMPv3 is enabled by providing the --v3auth for SNMPv3 authentication and the

optional privacy parameters provided using the --v3priv command switch (or by

providing the requested information when running Config.pl to configure the PBMT

toolset).

--v3auth requires 3 option-fields separated by a ‘:’ character:

o A username

o A password (at least 8 characters are required)

o Authentication protocol (SHA or MD5. MD5 is default)

--v3priv requires 2 option-fields separated by a ‘:’ character:

o Privacy protocol (DES, 3DES or AES, DES is default)

o A password

Support of ftp and sftp

The PBMT tools now determines the protocol used to transfer files by checking the

settings in the ISAM itself. Depending on this setting files are stored and retrieved

from different locations:

• tftp: files are stored and retrieved relative to a “tftp-top” directory setting.

• ftp and sftp: files are stored and retrieved either relative to the user

performing the file upload (configured in the ISAM when configuring the

file transfer protocol (see DLP-203 of the Operations and Maintenance

using CLI of the customer documentation).

Because of this specifying the software package needs some

attention and PBMT looks for the OSWP using the following

New about this toolset

3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 21/176

search mechanism:

• First we check whether the OSWP as specified via the --swp parameter is

existing. If existing PBMT assumes that the node will be using ftp or sftp.

• If the OSWP is not found it next probes the home directory of the user

running PBMT. If existing PBMT assumes that the node will be using ftp

or sftp.

• If the OSWP is still not found we concatenate the OSWP file name with

the TFTP top-directory setting and check whether the OSWP can be

found. If existing we assume that the node will be using tftp as file

transfer mechanism

• If the OSWP is still not found an error is generated.

The assumed file transfer protocol is next compared to what is configured in the

node itself. An error is generated when a mismatch is detected between the

assumed setting by PBMT and the configured settings in the node.

One important remark about the OSWP and the file transfer protocol being

used.

The OSWP as provided by Alcatel-Lucent in the delivery is made assuming that tftp

is used as file transfer protocol. If ftp or sftp will be used the ASAM-CORE setting

needs to be adjusted in such a way that the file can be found at the specified

location when the user configured for the file transfer protocol initiates the transfer.

In case the specification is not correct, the file transfer will end in a failure stating

that a file could not be found.

For more information about the PBMT toolset please refer to the Software Upgrade

and Migration Application Procedures as provided in the customer documentation.

Support NE families

Starting from V2.1 a set of NE families is supported by the PBMT tools:

• The ISAM family (up to R3.7)

• The ESTI 7302 ISAM family (starting from R4.0) consisting of FD-only

equipment (includes 7330 equipment practise).

• The ANSI 7302 ISAM family (starting from R4.0) consisting of XD-only

equipment (includes 7330 equipment practise.

• The common ETSI/ANSI 7302 ISAM family (starting from R4.0) and

currently only includes one NT type: the AGNT-A N.

• The ETSI 7302 ISAM variant for NTT (starting from R4.0). The SW package

identifier is ‘AC’ as compared to ‘AA’ for the regular ETSI 7302.

• The HiCap 7302 ISAM family

Content of the Release

3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 22/176

(starting from R3.7.10)

• The ISAM 7354RU family

• The 1540Litespan family (support for NT GEB3-B)

Each NE family has a set of associated directories for storing the offline migration

tools:

• ./tools/NT and ./tools/Lanx for the ISAM family and ETSI 7302 ISAM family

• ./tools/NT_ANSI and ./tools/Lanx_ANSI for the ANSI 7302 ISAM family

• ./tools/NT_HICAP for the 7302 ISAM HiCap family

• ./tools/7354RU for the ISAM 7354RU family.

• ./tools/NT_LS and ./tools/Lanx_LS for the 1540Litespan NE family.

• ./tools/IVPS for storing the IVPS toolchain.

• ONT Release Mapping file present as ./tools/ONT_Release_Mapping.txt

1 Content of the Release

1.1 V3.1.13


� ALU01871278: PBMT: Use of :locked is deprecated

Problem: While running PBMT scripts using the PERL libraries of

AMS 9.2.10, the following warning message “Use of :locked is

deprecated” is observed due to the SNMP libraries.

Solution: The warning messages generated due to the

deprecated functions are suppressed in the PERL Net libraries

provided for AMS purpose in the PBMT package.

� ALU01877212: [Ontstage] warning: TIOCSCTTY failed, slave

might not be set


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 23/176

as controlling terminal

Problem: While running the ONT staging script above warnings

are displayed during the execution of ontstage.pl. But no

functional impact is caused due the warnings and the ONT

software is successfully downloaded to the NE.

Solution: To resolve the issue the warnings are disabled in the

block before the call to Pty PERL library for creating a new pseudo

terminal.

1.2 V3.1.12 skipped (delivery error)

1.3 V3.1.11


� ALU01881027: Migration script fails with error transaction

owner release period expired during migration

Problem: Migration from R4502 to R46 on duplex NANT-E setup

fails with error “Transaction owner release period expired” since

the migration script tries to trigger an upgrade via

SNMP when the active NT is still operational and standby NT is

starting up with migrated database.

Solution: The migration script would wait for takeover by the

standby NT as part of the restart process during activation with

migrated database. Now retry is also done on some SNMP error

conditions while activation is done via standby NT.

1.4 V3.1.10


� ALU01885341: PBMT : issue with statusCheckCmp.pl related

to bridge port configurations

Problem: PBMT script statusCheckCmp.pl fails reporting

mismatch in bridge port configurations post migration even when

there are no issues with these configurations.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 24/176

Solution: Multiple bridge configurations for the same LT slot are

handled properly for HiCap NT’s alone.

1.5 V3.1.9


� ALU01883846: PBMT: Updation of default installation path

for Linux utilities in param.cfg

Problem: The PBMT script uses Linux/Unix command and utilities

the path for which is specified inside param.cfg.

viz. for most of the linux/unix commands like ps, touch, mkdir, cp,

sleep etc. the path is specified as /usr/bin when param.cfg is

generated by running the PBMT configuration script under solaris

platform. The path for these commands need to be updated to

point to the default Linux installation path for these utilities.

Solution: For Linux the utilities will be appended with default

installation path in the PBMT configuration file

� ALU01884931: Conversion from NANT-D to NANT-E

conversion to check the NT type

Problem: NANT-D to NANT-E conversion script does not check

the NT present physically in the system.

Solution: The NANT-D to NANT-E conversion script would check

for NANT-D board to be physically present in the setup before

starting the conversion process

� ALU01883817: Migration fails due to Shub/NT version

mismatch

Problem: Migration in AGNT-A platform fails from 45.263 to

46.054 due to Shub/NT version mismatch.

Solution: Shub version has been upgraded in capability model of

PBMT

1.6 V3.1.8



3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 25/176

� ALU01879779: Conversion from NANT-A to NANT-D/NANT-E

conversion to check the NT type

Problem: NANT-A to NANT-D/NANT-E conversion scripts does

not check the NT present physically in the system.

Solution: The NANT-A to NANT-D/NANT-E conversion script

would check for NANT-A board to be physically present in the

setup before starting the conversion process.

1.7 V3.1.7


� ALU01880704: ISAM went unreachable after activation with

linked-db

Problem: The migrated database was having db version A4.400

while migrating to R4405 which is incompatible with the db

version B4.401 expected by R4405.

Solution: PBMT maintains a correlation between the DB version

and the Build numbers for any particular release. In earlier ISAM

releases we had mainstream builds only until 6xx build series but

in case the build number crosses to the next build series, the

PBMT tool needs an update. Capability model has been updated

to consider the 44.7xx builds as mainstream.

1.8 V3.1.6


� ALU01880147: PBMT support on RedHat Linux 6.3 64-bit

version

Problem: Red Hat Linux version 6.3 is having PERL version 5.10.1

which need to be supported by PBMT scripts.

Solution: Linux support is already available in PBMT with perl

V5.8.x but the shared objects pertaining to CPAN library modules

compiled in 5.8.x gives runtime issues while running the PBMT

script in perl 5.10.1 environment. Hence a recompilation of these

shared libraries was done for PERL version

5.10.1 and these libraries were included in


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 26/176

the PBMT tar package.

� ALU01871009: Add a cli retry when the first attempt times out

in PBMT

Problem: During migration from R4302c to R4302y, migration

failure was reported due to below error: "Timed out while waiting

for some alive indication" and the CLI session could not be

opened. But the migration of the node was successful without any

issues.

Solution: The reported Timed out error was not handled properly

and hence the retry was not happening. Now this has been

corrected.

1.9 V3.1.5


� ALU01852256: NANT-D/E EPF Not Work when Distributed SIP

Call on Same LT Board

Problem: Enable user to user hairpin when the user runs the

PBMT conversion scripts for NANT-A to NANT-D/NANT-E in

releases exceeding R4501 to support voice service.

Solution: User to User hairpinning configuration is now enabled

during conversion from NANT-A to NANT-D/NANT-E in the PBMT

conversion scripts in releases R4501 and above when the --voice

command line option is used.

1.10 V3.1.4


� No FR: PBMT support for Lanx migration tool 1.70.

Problem: A new SHUB migration tool 1.70 has been delivered

and need to be supported by the PBMT scripts.

Solution: Support for SHUB migration tool 1.70 has been added

in PBMT.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 27/176

1.11 V3.1.3


� ALU01868204: R4303f:NANT-A to NANT-E conversion is not

working

Problem: While trying to activate a database converted from

NANT-A to NANT-E in R4.3, an error occurs that the database is

not useful.

Solution: The DB version was wrongly printed in the config file of

the database which has been corrected

1.12 V3.1.2


� ALU01865738: Migration failing when migrating the ISAM

from R4302(43.393) to R4306(43.624).

Problem: While trying to migrate from R4302 (43.393) to R4306

the script fails with an error that the DB version is not as expected

due to the fact that DB version was considered as A4.300 instead

of B4.301 by the script.

Solution: PBMT Capability model adapted to accept R4306 builds

as mainstream for R43.

1.13 V3.1.0 & V3.1.1 (skipped) Above version labels skipped since they were reserved earlier in

Clearcase and we are unable to use them.

1.14 V3.0.99

1.14.1 New requirements


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 28/176

� ALU01864146: R46 PBMT TOOL drop.

Problem: PBMT to provide support for R4.6 release.

Solution: Support for R4.6 release has been added in the

Capability model of PBMT

1.15 V3.0.98


� ALU01864304: PBMT second password – software download

operation takes too long.

Problem: PBMT scripts that takes second password as parameter

takes too long and hence time to complete the operation needs

to be improved.

Solution: During SSH connection establishment a “Permission

Denied” error response occurs which is considered as a login

failure henceforth. The delay in the CLI connection establishment

wrapper routine has also been reduced.

1.16 V3.0.97


� ALU01863626: PBMT script command usage help for second

password not displayed.

Problem: Command help for second CLI password is not

displayed for PBMT scripts file.

Solution: Script help for second CLI password is provided for the

PBMT scripts

� ALU01863629: PBMT scripts do not work with second

password parameter when it takes input param.cfg.

Problem: PBMT scripts do not pick the second password

parameter from param.cfg when it is not provided as option via

the command line.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 29/176

Solution: Corrected hash containing the second password from

an undefined value to the value provided through the

configuration file.

1.17 V3.0.96


� ALU01863504: Use a second CLI password if the first one fails

(applicable only for SSH).

Problem: The PBMT scripts should include a possibility to try

connecting using a second CLI password if the first password fails

when “CLI over SSH” is configured as the communication channel

in the ISAM. Facility to provide a second password is to be

supported via command line option to the related scripts as an

optional parameter and also via the PBMT configuration file.

Solution: The second CLI password option is provided to the

relevant PBMT scripts in command line and also in the

configuration file.

1.18 V3.0.95


� ALU01849911: [ONT stage] Software Staging Failures exceeds

The Warning Threshold.

Problem: After TL1 command CANC-USER gets called inside the

ONT staging script, the session ends successfully, but LOGOFF

command was also called subsequently which gave rise to a denial

in the TL1 operation. The staging script was

trying to get the error description pertaining to the denied

operation by sending wrong OID using SNMP.

Solution: The SNMP get operation with wrong OID is not done

now.

� ALU01854309: Migration failure in R4502.

Problem: Migration fails in R4502 since PBMT need to support

for build ranges 4502.2xx.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 30/176

Solution: Capability model of PBMT updated to support OFLMT

build versions in the range 4502.2xx.

1.19 V3.0.94


� ALU01847573: Migration precheck fails: **FATAL** Could not

obtain NT offline migration tool version.

Problem: Pre-check script fails with an error that the NT OFLMT

tool version could not be obtained.

Solution: The PBMT tool has now been adapted to check and

display the build number when the version of OFLMT tool is not in

proper format. Pre-R45 ISAM releases use Clearcase environment

to build OFLMT, but R450x ISAM releases use mercurial

environment which causes the version number to be in

incompatible format. So PBMT will use build numbers instead of

version information to overcome this build environment change.

� ALU01824999: Pre/Post-op Status on ISAM NE without TL1

credentials, error message displayed does not provide clear

information.

Problem: When the TL1 credentials are not provided while

running the Pre/Post-op Status scripts the error message

displayed does not provide clear information about the error.

Solution: Status check script has been adapted to provide the

clear error message such as TL1 username or password is not

specified in case the same is not provided or incorrectly

mentioned while running the status script(statusCheck.pl)

� ALU01849616: [Migration] Postcheck fails due to uninitialized

value in Capability.pm.

Problem: While running the StatusCheck script in the post

migration phase, the script aborts with an error "Caught signal

'__DIE__".

Solution: The issue occurs due to non-initialization of a perl hash

variable (which was supposed to have contained the software

package name) when trying to find out the release version. Now

the release information is got from the


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 31/176

MIB version.

� ALU01844812: PBMT version check error: Version number of

NT OFLMT higher then the one known to this toolset.

Problem: While trying to migrate from R3.6 to R4.3 on an ECNT-

C setup using the tools for R4.3, an error occurs that the Version

number of NT OFLMT is higher than the one known to the toolset.

Solution: The regular expression check in PBMT has been

adapted to pick the proper version format from the OFLMT

version display.

1.20 V3.0.93


� ALU01809526: SW download fails if both OSWPs are loaded

and NE has NT Redundancy.

Problem: While trying to download ISAM software using PBMT

SW download script, an error occurs that the “SWDB management

is busy” when both OSWP's are loaded and NE has NT

Redundancy.

Solution After aborting the passive OSWP we increase the delay

before attempting to download the software. Additionally PBMT

will wait slightly longer to allow the OSWP to stabilize before

retrieving the OSWP information details and then proceed with

initiating the download.

1.21 V3.0.92


� ALU01847389: PBMT changes required as a result of SW

upgrade via Standby NT for NANT-E / FANT-F setup.

Problem: A new feature was introduced in ISR4501 wherein the

SW upgrade is done via standby NT (rather than active NT) for

redundant NANT-E/FANT-F setups. The impact of this feature on

the PBMT tool need to be investigated and changes made so that

PBMT tool should take care of both

upgrade scenarios viz. activation via active


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 32/176

NT (or) via standby NT while performing the upgradation.

Solution: Functionality introduced in PBMT to monitor the state

of the standby NT in redundant NANT-E/FANT-F setups for

releases from and beyond R450x while waiting for ISAM restart to

happen.

1.22 V3.0.91


� ALU01844317: Migration fails from 4403.509 to 45.053.

Problem: While trying to migrate from R4403 (4403.509) to R45

the script fails with an error that the DB version is not as expected

due to the fact that DB version was considered as A4.400 instead

of B4.401 by the script.

Solution: PBMT Capability model adapted to accept R4403.5xx

builds as mainstream for R44.

1.23 V3.0.90


� ALU01836902: OFMLT version issue on 45.040 build.

Problem: When we tried to execute OFMLT tool in R45 it returns

incorrect version information since from R45 builds are made in

the mercurial environment which uses revision numbers instead of

label versions to identify the OFLMT builds.

Solution: For backward compatibility we retain the version

number check for Releases prior to R45. Since mercurial is used

for R45 (and post R45 releases) the check on build number will be

used only when version info is unavailable. We would limit the

build number check to the next higher


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 33/176

range viz. for R45 the highest build oflmt will be 4500.099,

subsequently it will be R4501 (limited to 4501.199 and so on).

1.24 V3.0.89


� ALU01821914: ONT SW is also activated while DLONLY is set.

Problem: While running the OntDownloadActivate script using

DLONLY option the ONT SW also gets activated since the ONT SW

control table entries are not properly configured.

Solution: When creating the new SW control table, software

version planned and software planned version confirmation

should also be configured with the ONT software that is currently

active in order to resolve this issue.

1.25 V3.0.88


� ALU01830912: NANT-A to NANT-D db conversion fails.

Problem: NANT-A to NANT-D db conversion fails while

migrating from R42 to R45 with an error that the HW

configuration is unsupported and MIB version is too high.

Solution: R45 Support has been added for the NANT-A to

NANT-D conversion script in PBMT.

1.26 V3.0.87


� ALU01761938: PBMT migration fails with SNMPv3 in no

authentication and no privacy mode.

Problem: When PBMT is configured for SNMP v3 in no

authentication and no privacy mode, the script fails since the

option is not supported.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 34/176

Solution: Support has been added in PBMT for SNMP v3 with no

authentication and no privacy mode. While running via command

line the user need to specify only username for SNMP v3 setting.

Alternately while running Config.pl only the username can be set

and empty string be provided for authentication and privacy

passwords.

� ALU01828136: Migration fails from 4302 to 4403

Problem: Migration fails from R4302 to R4403 with an error that

the script died since it is unable to locate an object method in the

Hicap migrate library.

Solution: Syntax error in the Hicap migrate code library has been

corrected to resolve the script issue.

� ALU01836986: Migration for DTAG of ANCP parameters from

ISR41 to ISR44 fails

Problem: A new feature introduction in R43 by which the Pbit

can also be set in the ANCP message. A workaround in R41 which

had a fixed format introduced with ANCP appended with VLAN

label was extended in R43 to accommodate the Pbit information

along with existing message. During IHUB migration this

configuration was not migrated and the interface name is carried

over from R41 to R44 causing the issue. This requirement is

specifically targeted to the DTAG customer.

Solution: Introduced two new parameters NEW_VLANLABEL and

ACT_VLANLABEL in PBMT configuration file. These need to be

changed to the new and existing values for the ANCP requirement

before the migrate script is run. For DTAG customer this IHUB

configuration will be migrated from R41 to R4403.

� ALU01836984: Migration for DTAG "unconfigured multicast

channels" from ISR41 to ISR44 fails

Problem: For un-configured multicast channels in R4.1 the value

is 128. The software does multiply it with 8 for DTAG customer

making the value as 1024, if the configure mcast capacity max-

num-uncfg is 128. But in R4.3 the max-num-uncfg value is

natively configured to 1024 but the value is copied from the

original database as 128. The PBMT tool need to post-process this

parameter only for DTAG customer.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 35/176

Solution: During migration from R41 to R4403 PBMT will trigger

the offline migration tool to multiply this parameter value by 8

during database migration specifically for DTAG customer.


1.28 V3.0.85


� ALU01827726: Migration of customer DB from R3.6.03f to

R4.5 fails

Problem: Migration from R3603f to R45 fails with SHUB

migration failure error stating that the User-to-User Hairpin status

is not present in the SHUB configuration file which is used by the

SHUB migration tool.

Solution: During migration from R36xx to R44xx or higher ISAM

target releases, PBMT will update the User-to-User Hairpin Status

in the SHUB configuration file. Earlier PBMT was updating the

User-to-User hairpin status in SHUB configuration file only for

migration from R36xx to R43.

1.29 V3.0.84


� ALU01826095: Offline migration failed for R4402 -> R45

Problem: Offline migration fails from R4402 to R45 since the path

is not supported for offline databases.

Solution: Migration library modules modified to accommodate

R4402 release descriptor file name while using offline DB for

migration.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 36/176

1.30 V3.0.83


� ALU01821808: cvtNantA2D.pl fails to map the BITS

configuration of NANT-A to NANT-D

Problem: The NANT-A to NANT-D conversion script converts the

BITS configuration as auto-select irrespective of the actual

configuration of NANT-A being E1 or khz2048..

Solution: While creating the Clock management config table the

relevant field holding the configuration information was defined

with a field length of 1 instead of 2 which has been changed now.

1.31 V3.0.82


� ALU01824012: PBMT support for lanx migration 1.69

Problem: A new SHUB migration tool 1.69 has been delivered

which is not yet supported by the PBMT scripts.

Solution: Support for SHUB migration tool 1.69 has been added

in PBMT.

1.32 V3.0.81


� ALU01819262: Grouping of Igmp Multicast channel records

should be configurable by PBMT

Problem: PBMT tool will need to include command line option to

the migrate script in order to enable/disable grouping of IGMP

multicast entries and also provide user configurable option to

define the allowed gap size between multicast group ip-addresses

while grouping. These options should also be configurable by

running the Config.pl script.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 37/176

Solution: Command line options --confmcastgrp and –

confgapsize have been added to the migrate script for configuring

these options. The PBMT configuration file param.cfg also

contains the settings ENABLE_IGMP_GROUPING and

MAX_GIP_GAP to set these options. By default the IGMP multicast

entries grouping is enabled and default Gap size is set to 0 which

allows consecutive entries.

1.33 V3.0.80


� ALU01814545: PBMT & OFLMT tool need to be updated for

the FGN43 build

Problem: PBMT tool need to support FGN43 release stream.

Solution: Capability model of PBMT has been updated to

support FGN43 release stream.

1.34 V3.0.79


� ALU01797328: Request to include ssmoutvlan parameter in

param.cfg file of PBMT

Problem: PBMT tool need to include SSM_OUT_VLAN in

param.cfg file with a value to be selectable by the user so that

during migration the system reserved vlan can be set to a value

that the user selected in order to avoid conflict with existing

service vlan.

Solution: SSM OUT vlan has now been included in param.cfg, by

default it will be disabled (having value 0). The user needs to set

this parameter to desired value before running the migrate script.

1.35 V3.0.78



3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 38/176

� ALU01815081: Target release 'lower' then active seen with

swdl.pl

Problem: Download of R4403 software build over R4402 fails via

PBMT with an error that the target release is lower than the active

release.

Solution: Support for R4403 release has been added in the


1.36 V3.0.77


� ALU01815133: PBMT: Migration from R4.2.1d to R4.3.2c

failed when two NTs are two different ICS versions

Problem: In redundant setups when the NT boards have different

ICS versions the Migration is failed for NANT-E and other HiCap

boards.

Solution: The check for different ICS check is removed from

PBMT for Hicap boards since the ISAM software takes care of

supporting different ICS versions to accommodate hardware

replacement scenarios occurring in the field.

� ALU01814430: PBMT: ontDownloadandActivate.pl gives error:

No matching ONT SW CTRL table entry

Problem: ONT download script run for download only command

option fails with non-zero return code doe to an error that a

matching entry is not found in the ONT software control table.

Solution: Due to data corruption in the hash structures used to

maintain the ONT software information, the script tries to enter an

additional entry in the ONT software control table causing the

error which has been corrected.

1.37 V3.0.76


� ALU01804049: PBMT: ontDownloadandActivate.pl


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 39/176

operationmode DLONLY also activates ONT sw

Problem: The DLONLY command line parameter for operation-

mode of the ontDownloadandActivate.pl script also activates the

ONT sw on the ONT during the script run.

Solution: The ONT software control list parameters are now

updated correctly to resolve the issue.

1.38 V3.0.75


� ALU01813641: PBMT: download fails with --reduce option

when CLI password has "$" in it

Problem: When the CLI password contains $ character the script

fails to retrieve the OSWP file with reduce option since PBMT

script is stripping the "$" character (and every character after the

$) while it sends the password to the 7330.

Solution: While sending the password the script will now append

it with quotes so that truncation of the password does not happen

� ALU01808034: R45 migration path to be made available

Problem: PBMT to provide support for R4.5 release



1.39 V3.0.74


� ALU01788919: PBMT: swdl.pl with --reduce option fails when

ISAM configured for SFTP

Problem: During online software reduction PBMT has to upload

the descriptor file from the ISAM for manipulating it to contain

only the required board files. The descriptor upload and download

process have been forced to use TFTP till date. When SFTP is

configured as file transfer protocol


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 40/176

in the node the script fails to retrieve the descriptor files from the

ISAM and exits with Transfer timeout error.

Solution: An SFTP client has been introduced inside PBMT to

perform the transfer of descriptor files from/to the ISAM when the

node is configured for SFTP.

1.40 V3.0.73


� ALU01804629: R4302g NT OFLMT & PBMT tool delivery

Problem: PBMT tool support is required for R4302g release.

Solution: Support for R4302g release has been added in the

Capability model of PBMT.


1.42 V3.0.71


� ALU01800464: NT DB backup failed during Migration

Problem: While running migrate script the backup of the NT

database fails due to the Unix write permissions not available for

upload.

Solution: Write permissions granted during creation of dummy

backup file before attempting upload of NT database.

1.43 V3.0.70


� ALU01796575: PBMT: usage with older Lanx migration

package


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 41/176

gives error due to CalcIpCheckSum executable presence

Problem: Old Lanx packages have a checksum tool

CalcIpCheckSum for Solaris Sparc platform which was

discontinued with Lanx tool versions 1.66 and above. Instead they

started using CalcIpCheckSum_BE as the toolname. This caused

issues when PBMT tool versions greater than V3.0.57 were used

with Old Lanx packages (prior to v1.66) and an error was thrown

during migration. This has put the backward compatibility of

PBMT in jeopardy.

Solution: For Lanx version lesser than 1.67, PBMT will invoke the

CalcIpCheckSum tool instead of CalcIpCheckSum_BE for Solaris

Sparc platform

� ALU01719620: after configuring snmpv3, it is not possible to

migrate with snmpv1 or v2

Problem: When the user tries migration with snmpV3 settings for

a particular isam and then switches to snmpV1 or snmpV2 for

another isam by modifying the snmp settings via Config.pl script

run, the migration script fails since it continues to use snmpV3.

Solution: Once the user re-configures snmp settings to use

either snmpV1 or snmpV2 by re-running the Config.pl script the

earlier snmpV3 configurations will be reset to the default values

which would allow the usage of snmpV1 or snmpV2 again.

1.44 V3.0.69


� ALU01748732: Could not open TL1 error reported during

Migration post-check

Problem: When TL1 is disabled in the ISAM and status Check

script is run post migration, the script reports an error that a TL1

session cannot be opened and aborts with failure return code.

Solution: Inside status Check the fetching of alarms is done by

establishing a TL1 session. Now PBMT will detect the status of the

TL1 connection and skip the fetching of alarms if TL1 is disabled.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 42/176

1.45 V3.0.68


� ALU01792230: PBMT: Minimize.pl should not set NT software

to MINIMUMSET when using --minset option

Problem: The Minimize script sets the MINIMUMSET to YES for all

boards listed in the Board list file including the NT boards. During

download script run the software for both ECNT-A and ECNT-C

boards get downloaded causing significant amount of space to be

consumed in the /Sw directory of the ISAM. Occasionally the SW

is also unable to fit into the ISAM.

Solution: Inside the Minimize script, for NT boards we retain the

MINIMUMSET as NO so that during SW download only the

appropriate NT SW will be downloaded to the NE

� ALU01789702: World writeable directories need sticky bit to

be set.

Problem: For security reasons the world writeable directories

created by PBMT should have the sticky bit set to prevent users

from editing, removing or renaming of files they do not own in

that directory.

Solution: PBMT scripts enhanced to create world writeable

directories with sticky bit set

1.46 V3.0.67


� ALU01790650: PBMT not ok in R4401 & R4402

Problem: During Remote lab testing for migration using PBMT it

was observed that the DB version was taken as A4.400 for build

ranges in R4401.6xx causing issue during online migration.

Solution: Build range R4401.6xx to R4401.9xx will accommodate

the db version as B4.401 with update in the Capability model of

PBMT.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 43/176

1.47 V3.0.66


� ALU01787464: R44 dbase change for Fiber

Problem: PBMT to be updated to accept B4.401 dbase change for

R44a/R4401/R4402 release.

Solution: Capability model in PBMT updated to accommodate

B4.401 database change.

1.48 V3.0.65


� ALU01781801: Issues with upgrade.pl script in 7354

Problem: The upgrade.pl script had some issues after the

activation of 7354 with destination build when the script was

using the second cli password. The script reported a login failure

during activation since it was using the first cli password.

Solution: After activation the script will retry to login with second

password in case of login failure using the first password.

� ALU01778224 : Reduced software download fails in R44

Problem: Software reduction using PBMT fails prematurely since

the NT is unable to access the descriptor file and results in an

access violation error. This issue is observed only in R44 and works

for previous ISAM releases.

Solution: Workaround provided in PBMT to make software

reduction possible in R44. The correct path is written in the OSWP

overall descriptor file so that the SWP can be retrieved from this

location.

1.49 V3.0.64



3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 44/176

� ALU01778953: NANT-D can't come up after migrating from

R43 to R44

Problem: While performing NANT-D migration from R43 to R44

with 8 pairs of NVPS boards, the XVPS migration does not happen

and NANT-D cannot be activated with R44 migrated database.

Solution: Support for XVPS migration has been implemented for

NANT-D in PBMT

� ALU01783098: xVPS DB offline migration failure : DB

container found for XVPS8 while no community string has

been

Problem: During migration of ISAM-V (H248) customer databases

Offline using PBMT migrate script, the migration to R44 is

unsuccessful because no community-string is defined for "NVPSx"

context. For customer databases which do not have community

string defined in db the migrate script should not fail.

Solution: PBMT migrate script has been adapted to skip the

above check for offline migration case.

1.50 V3.0.63


� ALU01777956: Migration fails when NT-B is in protection

group locked state

Problem: When the standby NT is in protection group locked

state the migration fails since PBMT expects synchronization to

happen between NT-A and NT-B and waits till timeout is attained.

Solution: The check in pbmt for redundant NT in hot-standby is

now removed and not considered a criterion for migration. Hence

the script will not wait for NT synchronization to happen and is

able to proceed with the migration.

1.51 V3.0.62



3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 45/176

� ALU01777019: PBMT:Upgrade failure in 7354 using SSH

Problem: 7354 had issues in PBMT related to usage of SSH as

communication channel for CLI session. The PBMT scripts are

unable to get a response for the oswp software management

details command and exit with non-zero return code. On trying to

login to isam after the script failure the responses that should

have been received by the upgrade script are visible in the CLI

session.

Solution: Inside the PBMT net libraries the Telnet prompt has

been modified to intake one or more white spaces after the

prompt character and the SSH connection routines have been

adapted. Another issue found during release transaction has been

resolved by introducing a delay in the script.

1.52 V3.0.61


� ALU01748774: R4.0.0.1e migration via PBMT from 5520 AMS

GUI fails

Problem: In legacy 5520 AMS pre 9.1, migration is broken due to

command option name change for username and password to

cliusername and clipassword. AMS 8.4.1 is not aware of this

change done to the command options to send to migration script

and the migration fails. The command line change has been

implemented in the PBMT 3.x series,

Solution: PBMT scripts have been adapted to take in username

and password alternatively to cliusername and clipassword as

command line options.

� ALU01753789: Lanx: SHUB version pointing to R4.3.01

Problem: During activation with migrated db for R44 the script

reports an error that the new software is not activated due to NT

and SHUB being in different releases since the shub release is still

4.3 version. This version mismatch error of Lanx shub version is

reported in AGNT-A, NANT-A & NRNT-A causing pbmt to throw

any error like “lanx version mismatch".

Solution: Capability model adapted to consider lanx 4.3 version

for R44


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 46/176

1.53 V3.0.60


� ALU01755206: PBMT issues with DB version in 7354RU

Problem: During software download for 7354 using the PBMT

download script, it fails stating that the DB version is not defined

in the descriptor file.

Solution: For the 7354RU the DB version regular expression

format has changed as compared to 7302/7330 systems and this

is taken care of while parsing the DB version from the descriptor

file.

1.54 V3.0.59


� ALU01749178: Migration fails during SuperBatch run in R44

release on ERAM-A

Problem: Migration fails in ERAM-A for R44 release during offline.

Solution: Generation of Software package name for offline

migration in R4302 is included in pbmt since the build starts from

43.2xx build numbers.

1.55 V3.0.58


� ALU01742031: Offline migration failing for R44 release

Problem: Offline migration fails while migrating from R4302 to

R44 with a non-recoverable error record that the Version supplied

(A4.300) is different from the version of database(B4.301) resulting

in the Offline migration tool exiting unsuccessfully.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 47/176

Solution: Migration library modules modified to accommodate

R4302 release descriptor file name during offline DB migrations

� ALU01733408: Support needed to not use CalcIpCheckSum

executable inside PBMT for lanx migration tool version 1.67

Problem: The Lanx migration tool version 1.67 has only the

executables CalcIpCheckSum_BE or CalcIpCheckSum_LE, so one of

these has to be used by the PBMT tool depending on the

Operating system environment.

Solution: PBMT will henceforth not use CalcIpCheckSum

executable and use only the supported Lanx tool executables

instead.

1.56 V3.0.57


� ALU01496120: No appropriate error in result file when CLI

credentials are NOK

Problem: : While running the migration script with incorrect CLI

credentials PBMT identifies the error with different error

description like it is unable to set the logging directories properly .

Solution: The issue was caused due to improper error being

allocated during the error occurrence. Now the appropriate error

id is allocated to avoid the issue caused

1.57 V3.0.56


� ALU01524313: After configuring snmpV3, it is not possible to

migrate with snmpV1 or V2

Problem: : When the user tries migration with snmpV3 settings

for a particular isam and then switches to snmpV1 or snmpV2 for

another isam the migration script fails.

Solution: The param.cfg need not

be changed, and the values can be


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 48/176

passed in command line to accept that mode

1.58 V3.0.55


� ALU01470814: Problem on statusCheck.pl and

statusCheckCmp.pl scripts

Problem: On exectution of script statusCheck.pl with the option -

post (or pre) with the R42.03a NANT-D or NANT-A the

information on the status of XDSL lines is not obtained.

Solution: Starting R4010 the calculation of if-index for XDSL line

status has changed. The issue was caused due to improper slot id

translation during calculation of if-index for retrieval of XDSL

operational data. Now the if-index calculation strategy has been

modified for R430x.

� ALU01700004 (and clone ALU01704603): Shub Version higher

than one known to toolset

Problem: A new Lanx tool version 1.67 has been delivered which

need to be supported by the PBMT scripts.

Solution: Lanx tool version 1.67 upgraded in PBMT

1.59 V3.0.54


� ALU01643367: Precheck.pl script getting failed with errors

Problem: When the precheck.pl script in PBMT tool is executed,

script fails with " Use of uninitialized value" errors.

Solution: The issue was caused due to the user not providing --

swp parameter via the command line.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 49/176

The check has now been implemented to flag an error in case this

parameter is not given by the user.

� ALU01685170: Superbatch offline migration failed from

R423X to R4302

Problem: While performing Offline migration from 423X to 4302

the from database version is wrongly supplied to the offline

migration tool resulting in a non-recoverable error.

Solution: On executing with ISAM target the script is able to

fetch the source DB version from target and use it to determine

active Release versions in order to differentiate R4220/R4230 from

R42. But for offline db migration the script was using SWP

descriptors to determine release versions. Updation has now

been done to determine the Release version from the supplied

offline source DB.

1.60 V3.0.53


� ALU01630848: PreCheck fails on NANT-A with exit code 45

Problem: PBMT does not yet support version 6.1.2 of the xVPS

OFLMT.

Solution: Support for the xVPS tool version is included in PBMT.

� ALU01607596: PBMT support for R4.4

Problem: PBMT to provide support for R4.4 release.




1.62 V3.0.51



3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 50/176

� ALU01605960: Failing migration because of SHUB SW version

error

Problem: PBMT was expecting the response of the CLI command

for Shub release version to start with ‘Lanx’ and exits with an error

like obtaining SHUB software version has failed since the response

is not in expected format.

Solution: PBMT accepts the Lanx version format ‘R4.x.x.x’ starting

release R4302 in response to "show system shub entry version"

command.

� ALU01614269: Upgrade failure to R4106

Problem: While trying to upgrade from R4.1.04b (41.578) to

R4.1.04d (41.601), the script fails with an error that upgrade is not

possible since the target release is different from the active

release.

Solution: The Capability model in PBMT has been adapted to

accept 41.6xx as mainstream release for R41. Build numbers 41.7xx

and 41.8xx are only considered as belonging to R4010 release

stream.

1.63 V3.0.50


� ALU01595196: Unable to use PBMT for swdl in FGN4.0.01e

Problem: With R3350c build present in active OSWP, when a

software download of FGN4.0.01e build is tried using PBMT, the

download fails stating that the release stream R3350 is not a

known release for migration.

Solution: The Database version to release translation in the

Capability model has been updated to pick the proper release for

R3305 database to allow the download


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 51/176

1.64 V3.0.49


� ALU01584510: StatusCheck.pl displays child count as -1 when

run with 25 sessions

Problem: While running statusCheck.pl with pre or post option

using a hosts file which uses a minimum of two entries and with

25 sessions option, the script displays the child count as -1 for the

second child.

Solution: Some code optimization needed to be performed while

waiting for a particular child process to complete.

1.65 V3.0.48


� ALU01421954: StatusCheckCmp.pl script fails to run.

Problem: When running statusCheckCmp.pl script with --logfile

parameter including a directory, the script fails with file creation

error.

Solution: The directory specified in the –-logfile parameter

option has now been created so that the ONT status file can be

placed inside the respective result space folder

1.66 V3.0.47


� ALU01558101: Stageont.pl script fails with "Caught signal

'__DIE__'" error.

Problem: While trying to stage the ONT Software build to the

ISAM using stageont.pl, the script fails with an error "Caught

signal '__DIE__".

Solution: A minor correction has

been made in stageont.pl script during


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 52/176

the file open call to resolve the issue.

� ALU01558736: I386 Oflmt tools to be defined in a different

format for AMS.

Problem: AMS requires the format of the oflmt tools to be like

xx_NTOFLMT in the PBMT configuration file for the I386 oflmt

parameters. Since the I386 parameters have been defined in a

different format (NTOFLMT_I386), this fails the logic used in AMS.

Solution: The NTOFLMT_I386 entry have been renamed to

I386_NTOFLMT in the PBMT tool parameter settings.

1.67 V3.0.46


� ALU01518780: Status Check script run reports warnings

related to the use of uninitialized values in sprintf statements.

Problem: In R4010 release the ifindex calculation to retrieve the

XDSL Operational data was modified thus causing an error in the

ifindex calculation procedure used for R4301. The subsequent

snmp retrieval was returning empty data for XDSL line parameters.

Solution: The ifindex calculation has been modified in the script

to retrieve the proper XDSL operational data via snmp.


1.69 V3.0.44


� ALU01512804: PBMT Support for Solaris X86 based IVPS

OFLMT tool

Problem: The IVPS OFLMT tool need to be supported by PBMT on

the Solaris x86 platform.

Solution: PBMT support extended for IVPS OFLMT tool on Solaris

x86 platform. The default name for the IVPS OFLMT tool in Solaris

x86 will be specified in param.cfg as

“NBTW_i386”.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 53/176

1.70 V3.0.43


� ALU01492708: Precheck phase fails when doing migration

from FGN3.8 to FGN4.2

Problem: PreCheck script fails with an error message that the NT

OFLMT version is higher than the version known to the toolset.

Solution: During preCheck the PBMT was accessing the ETSI

version of the OFLMT tool for pre-R4.0 releases due to which the

failure occured, now this has been corrected to fetch the ANSI

tool version.

� ALU01393253: PBMT logs refer to 7302s not 7330s

Problem: While running statusCheck script during pre-migration

and post-migration PBMT generates the preOperCheck and

postOperCheck logfiles with 7302 naming instead of 7330 for

ANSI stream.

Solution: The preOperCheck and postOperCheck logs are

renamed to reflect 7330 instead of 7302 for ANSI stream

1.71 V3.0.42


� ALU01497319: Naming for Sparc/X86 OFMLT tools in

Param.cfg

Problem: As per AMS request, PBMT should have the x86 OFLMT

tool setting in the configuration file param.cfg as MJSH_i386. The

Sparc OFLMT tool setting in param.cfg should remain unchanged

viz. MJSH.exe.

Solution: The default name for the x86 OFLMT tool has been

changed in param.cfg as MJSH_i386.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 54/176

1.72 V3.0.41


� ALU01348790: PBMT should be able to pick the right

migration tool based on platform

Problem: PBMT should be able to determine the Offline migration

tool based on the Solaris Sparc and Solaris x86 platform at

runtime and also ensure backward compatibility.

Solution: PBMT will now invoke the correct offline migration tool

for the Solaris Sparc and Solaris x86 platform.

� ALU01316063: PBMT need to be updated with latest OFLMT

tool version.

Problem: PBMT need to support latest NT OFLMT version.

Solution: Updated the capability model of PBMT to support new

OFLMT version.

1.73 V3.0.40


� ALU01300398: Migration failure in NRNT-A

Problem: Offline Migration fails for SHUB Database due to

unknown SHUB NT type in the SHUB configuration file.

Solution: SHUB NT Type for NRNT-A updated in Capability

model of PBMT.

1.74 V3.0.39


� ALU01205527: NANT-D to NANT-E migration does not

maintain port speed in case of "default"

Problem: Ports with autonegotiate set to limited in NANT-D do

not come up after migration since the


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 55/176

link speed is not maintained after conversion to NANT-E.

Solution: For autonegotiate limited and autonegotiate disabled

the link speed default in NANT-D is maintained after conversion

to NANT-E.

� ALU01242257: Migration using R4.3 Lanx migration tool,

from R3.6 (36.434) to R4.3 (43.124) is failed.

Problem: The Lanx Migration tool expects an input from the

PBMT during migration from R3.6xx to R43 to enable or disable

the User to User Hairpin status. This results in a SHUB offline

migration failure.

Solution: During migration from R36xx to R43, only for 3604g

and 3604k emergency releases, an extra parameter "Hairpinstatus"

is set to TRUE in the Lanx tool configuration input file. The Lanx

Migration tool reads this setting to enable the User-to-User

hairpin configuration setting during offline migration.

� ALU01235321: NANT-D,migrate from L6GPAA42.401 to

43.118,migrate.pl execute fail with empty tmp cde path

Problem: During voice migration from R42 to R43 in NANT-D an

offline migration failure is reported by PBMT due to CDE path

being empty.

Solution: Migration failure corrected for R42 to R43 in voice

migration.

� ALU01288204: Enable User to User hairpin for R4230 to R43

migration in NANT-D

Problem: User to User Hairpin disabled is the default IPD setting

in R43. Hence while migrating from a native R4230 database the

User to User Hairpin feature should be enabled by the migrate

script.

Solution: User to User Hairpin feature enabled for IHUB NT's

when migrating from R4230 to R43 using PBMT migrate script.

1.75 V3.0.38


� ALU01261528: PBMT to be updated to support B4.301 dbase

variant for R4301


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 56/176

Problem: The offline migration tool and PBMT need to support

the B4.301 database variant.

Solution: NT OFLMT and PBMT has been updated to support

B4.301.

1.76 V3.0.37


� ALU01235324: 8 pairs nvps migration failed from R41.to R42

by ams

Problem: Migration of 8 pairs of nvps data fails from R41 to R42

fails after the first XVPS container is migrated.

Solution: We perform cleanup of the temporary CDE directory

after all XVPS containers migration is completed. Additionally

NVPS-A board will now be considered as voice board by PBMT.

� ALU01246291: PBMT ssmout help contains wrong default

value

Problem: The default value of ssmout parameter was changed

from 4091 to 4088. The help for the ssmout parameter need to be

updated in PBMT.

Solution: PBMT now considers value of 4088 as default for

ssmout vlan.

� ALU01255564: Lanx Migration Needs PBMT support

Problem: A new Lanx tool version 1.64 has been delivered which

need to be supported by the PBMT scripts.

Solution: Lanx tool version upgraded in PBMT

1.77 V3.0.36


� ALU01236674: Migration fails due to an undefined subroutine

call.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 57/176

Problem: Migration script ends abruptly with non-zero return

code due to call to an undefined subroutine SetAndLogError in

migration perl module.

Solution: Corrected the subroutine call SetAndLogError using

the proper calling convention.

� ALU01237623: Lanx OFLMT tool version v1.63 update in

PBMT.

Problem: Lanx OFLMT tool version V1.63 is not yet supported by

PBMT.

Solution: Support for Lanx OFMLT 1.63 has been added.

1.78 V3.0.35


� ALU01224557: Migration fails on NT-B slot, NT-A slot locked.

Problem: Migration fails when performed with NT-B slot in active

state and NT-A in locked state.

Solution: The failure was caused due the snmp retrieval of

Equipment inventory type for NT-A returning empty. The issue is

resolved by determining the snmp get for Equipment inventory

type of NT-B.

� ALU01178887: Make PERL libraries optional when using

PBMT.

Problem: 5520 AMS required only a subset of the complete perl

libraries from PBMT. The PBMT tool need to be usable in two

modes. One is the ‘standalone’ mode wherein the full perl libraries

delivered with PBMT can be used. The other mode ‘perlSupplied’

is provided for 5520 AMS where the perl libraries integrated with

AMS and certain perl libraries patched by PBMT can be used.

Solution: A new environment variable

LOAD_PERL_LIBS_LOCATION has been introduced in PBMT which

can be set to either ‘standalone’ or ‘perlSupplied’. The

‘standalone’ mode is the default mode and PBMT will work in this

mode with (or) without setting the environment variable to

‘standalone’. For 5520 AMS this variable can be set to

‘perlSupplied’ to use the patched libraries supplied along with

PBMT. The packaging of PBMT lib-perl


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 58/176

modules have been adapted accordingly in separate directories

bearing these names.

1.79 V3.0.34


� ALU01207252: Extend PBMT with ssm out parameter.

Problem: PBMT migration script need to support a command line

parameter in R43 for the operator to choose a different value for

SSM OUT Vlan in case the Default Vlan is already in use.

Solution: An new command option --ssmoutvlan has been added

to the migrate script to allow the user to specify an alternate value

for ssm out vlan.

� ALU01230116: PBMT is not migrating shub database.

Problem: Migration script returns failed error code while

migration of SHUB based NT to R43.

Solution: Capability model upgraded to allow SHUB migration to

R43.

� ALU01058609: PBMT should use a work around in order to

avoid "SWDB MGT is busy" Error.

Problem: While PBMT is checking the OSWP details, sometimes

an error like “SWDB MGT is busy” is encountered which normally

happens when auto-save is ongoing in the ISAM. PBMT gives up

the download of the OSWP after getting this error.

Solution: PBMT will wait longer for the OSWP to stabilize before

retrieving the OSWP information details and then proceed with

initiating the download.

� ALU01066530: PBMT Need to try few more times for Soft

download if they see "SWDBMGT busy"/"Not allowed in

current state

Problem: The Automated Batch Testing tool when using PBMT

internally quits with an error from SW management “OSWP

download not allowed in current state”.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 59/176

Solution: After aborting the passive OSWP we increase the delay

before attempting the download.

� ALU01131996: PBMT on ARAM-D: File only lists 4 LTs. Count

should not reflect 8.

Problem: While running the Status Check Compare script using

the "--hosts" command option the reported comparison log of

each node cumulatively adds the number of LT’s Out-of-Service

and XDSL lines that are down and displays an erroneous result.

Moreover the alarms that did not belong to a specific node are

wrongly reported as received from that node.

Solution: The state of the LT, XDSL lines and Alarms are

maintained by counters which are now reset to default values

whenever a new ISAM is handled.

� ALU01152509: PBMT report not detecting VSEM-C LTs.

Problem: The VSEM-C LT’s are missed out in the LT count by the

Status Check compare script despite being seen as LT in CLI.

PBMT was matching for LT’s based on suffix ‘LT’ in the board

name viz. EVLT, NVLT etc. resulting in VSEM-C being absent in the

reporting.

Solution: Status Check Script now matches the additional LT’s

which do not have suffix in their name and includes them while

reporting.

1.80 V3.0.33


� ALU01213090: Migration failure from R3.7 to R4.220.

Problem: While migrating an R3.7 XVPS database to R4.220 the

migration script reports an error that the database version B4.220

is not supported.

Solution: The XVPS migration support for R4220 is removed from

PBMT since there is no XVPS migration requirement for R4220.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 60/176

1.81 V3.0.32


� ALU01209264: R4230 PBMT support with AZ Software

variant.

Problem: Support required for R4230 with AZ Software variant.

Solution: PBMT upgraded to support R4230 release with AZ

Software variant.

1.82 V3.0.31


� ALU01186476: Latest version of NT OFLMT tool for ANSI

stream support in PBMT.

Problem: PBMT need to support latest NT OFLMT version for

ANSI stream.

Solution: The Highest version of NT OFLMT tool usable for ANSI

has been updated in PBMT

1.83 V3.0.30


� ALU01031457: PBMT to support R4220 release.

Problem: Support to be provided for R4220 release in PBMT.

Solution: PBMT upgraded to support R4220 with AY Software

variant.

1.84 V3.0.29



3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 61/176

� ALU01123774: OSWP file format handled by CLI for swdl but

not by PBMT for Reduce operation during next swdl.

Problem: SW reduction using swd.pl ends prematurely since

PBMT is not able to handle OSWP file format when the OSWP

information content in the file is split over multiple lines.

Solution: Instead of performing line-by-line parsing of the

descriptor file, we now continue to parse the OSWP information

content until the semi-colon delimiter is found during SW

download reduce operation.

� ALU01185809: Error records while migrating to 36.560.

Problem: Although migration is successful, Error records are seen

while migrating to Release R36, specifically 36.560 since the SHUB

SW release version is returned in lower case characters for this

release build when PBMT expects upper case characters.

Solution: The PBMT script library adapted to accommodate lower

case characters for detecting SHUB SW release version.

1.85 V3.0.28


� ALU01184513: CalcIpCheckSum is wrongly picked for Linux

platforms.

Problem: The CalcIpCheckSum executable which is used by LANX

for checksum calculation has different platform versions and the

PBMT script picks the wrong executable for the Linux platform.

Solution: The migration script has been adapted to pick the

correct CalcIpCheckSum executable for Linux platform

1.86 V3.0.27


� ALU01182632: Latest version of NT OFLMT tool need to be


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 62/176

supported in PBMT.

Problem: PBMT need to support latest NT OFLMT version for ETSI

stream.

Solution: The Highest version of NT OFLMT tool usable for ETSI

has been updated in PBMT.

1.87 V3.0.26


� ALU01179358: PBMT tool conversion of NANT-D to NANT-E

creates double entry for autonegotiate limited.

Problem: PBMT converts autonegotiate limited into two entries

autonegotiate limited and autonegotiate during NANT-D to

NANT-E conversion causing a restoration failure of the migrated

DB in case the NT port is part of a lag.

Solution: Enabling of Autonegotiation has been corrected.

1.88 V3.0.25


� ALU00966683: Support for PBMT in Linux environment.

Problem: Linux compatible version of PBMT is required for

execution of batch tests in Linux environment.

Solution: Linux 32bit and 64 bit compatible versions of PBMT

delivered

1.89 V3.0.24


� ALU01152372: Convertion script for NANT-D to NANT-E

requires an optional command parameter for link-speed.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 63/176

Problem: When the link-speed is set to 2.5G in NANT-D DB the

link speed remains the same after conversion to NANT-E. After

bringing up the system with the converted NANT-D DB, if the link-

speed needs to be set to 10G an extra system reset is required.

Solution: Script command option provided to allow enabling of

linkspeed to discrete values (1, 2.5 and 10 Gbps)

1.90 V3.0.23


� ALU01088438: Migration of Database fails for ECNT-E for

FGN42.

Problem: Shub migration fails due to missing configuration

setting in the Shub configuration file.

Solution: Shub parameter "InterfaceBase" value is set in Shub

configuration file to fix the issue.

� ALU01150963: Undo range check for Vmac Hostid parameter.

Problem: Vlan consistency check fails for DSLAM id greater than

8191 when migrating to R4202.

Solution: The Vmac host id range check done for ALU01033842

has been undone for migration to release R4202 and above due

to a change in migration tool

� ALU01033654: CDE values not migrated into MG and VSP cli

para when second time migrated.

Problem: The workaround done for ALU00975861 need to be

undone.

Solution: Untar of CDE files done via pbmt earlier has been

removed and Cleanup of CDE source directory is done to fix the

issue.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 64/176

1.91 V3.0.22


� ALU01033842: Vlan consistency check fails during migration

to R42 due to VMAC DSLAM ID shrinking to 8191.

Problem: Vlan consistency check fails for DSLAM id greater than

8191 when migrating to R42.

Solution: Check introduced to notify the user to re-configure

DSLAM id in the range 1 to 8191.

� ALU01079271: SNMP Community string is not read from

command line by status check comparison script.

Problem: When SNMP Community string is specified via

command line the Status Check compare script displays an

unknown option error.

Solution: SNMP community option is now accepted via command

line in Status Check compare script.

1.92 V3.0.21


� ALU01033654: CDE temporary directory not cleaned up after

migration.

Problem: While migration from R40 to R42 the CDE values are

migrated to media-gateway but a second migration fails to

migrate CDE values due to old CDE files existing in CDE temporary

directory.

Solution: Cleanup of the CDE temporary directory done to

resolve this issue.

� ALU01006984: Download SWP in passive OSWP if the

descriptor is same as the one existing in active OSWP.

Problem: While trying to download an OSWP existing in active

bank, a workaround was given via ALU00100007 to download to

the active bank again to overcome a TFTP write error encountered

while transferring missing files to the node. This workaround is

not needed anymore since the SW

Management issue has now been


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 65/176

resolved.

Solution: The workaround done in PBMT for ALU00100007 has

been undone.

1.93 V3.0.20


� A new script need to be developed for HW migration of a

NANT-D database to a NANT-E database within the current

release.

Problem: NANT-D to NANT-E HW migration script requirement.

Solution: New script cvtNantD2E.pl introduced into PBMT to

perform HW migration of NANT-D to NANT-E database within

current release.


� ALU01051477: After restoration of Nant-D to Nant-E

converted DB the NE is unreachable.

Problem: Restoration of the converted NANT-D to NANT-E is

successful but the NE is not reachable due to management port

‘nt-a:xfp:1’ speed mismatch.

Solution: Since NANT-D sfp ports 1 to 3 are ‘autonegotiate’ by

default and NANT-E xfp ports 1 to 3 are ‘no autonegotiate’ by

default, we need to insert autonegotiate in the ethernet section of

nt-a|b xfp ports 1 to 3.

1.94 V3.0.19


� ALU01038048: PBMT to be adapted for LRM.

Problem: The short summary of adaptations performed for LRM

is given below.

A separate PBMT zip file has been created for LRM. The lib-perl

components supported by LRM have been removed and a default

param.cfg been included in the zip

package. ONTDownload and


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 66/176

StageONT now support –id command parameter. Work files for

SFTP transfer will go in same directory as in TFTP.

Solution: PBMT has been adapted for LRM working.

1.95 V3.0.18


� ALU01032578: Parse of sip service configuration file failed

when doing function migration.

Problem: While performing H248 to SIP conversion the SIP

service configuration file parsing fails.

Solution: H248 to SIP conversion script modified to ensure that

the IP address is got for this host to resolve the issue.

1.96 V3.0.17


� ALU00981585: BITS interface parameters changes for NANT-A

to NANT-D migration.

Problem: The masks used to determine the clock settings were

not proper in the NANT-A to NANT-D conversion script.

Solution: The mask bit 0xffff and 0xffff0000 are now used instead

of 0xff and 0xff00 in ClockSource routine to resolve the issue

1.97 V3.0.16


� ALU00909611: PBMT support required for R4.3 release.

Problem: Currently PBMT does not have support for R4.3 release.




3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 67/176

1.98 V3.0.15

1.98.1 Error corrections / Workarounds

� ALU00975861: Untar for SIP CDE and MEGACO done in PBMT

for ALU00865237.

Problem: There was an issue in the TARUNTAR SW module

delivered for ALU00865237. PBMT need to be adapted to

overcome this issue.

Solution: The Untar of the CDE files for SIP and MEGACO is now

done in PBMT as a temporary workaround for ALU00865237

1.99 V3.0.14 skipped PBMT Delivery skipped due to an issue in UNTAR module

delivered for ALU00865237

1.100 V3.0.13


� ALU00954124: Revert back new naming convention for

Offline Migration tools.

Problem: The naming convention of Offline Migration tools which

was introduced via ALU00804222 need to be reverted back since

the AMS release used for R42 does not support this change.

Solution: The OFLMT and IVPS tool naming changed back to old

(previous) conventions viz. MJSH.exe, NBTW.exe and dbtool.cfg.


1.102 V3.0.11



3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 68/176

� ALU00926734: Status Check compare script picks up older

status check pre files for comparison.

Problem: During status check comparison, sometimes existing pre

files from a previous status check run causes the compare script to

compare the older files.

Solution: Status Check will remove the older pre and post files

while running a new pre or post status check to ensure that only

one pre or post status check file exists in the directory.

1.103 V3.0.10


� ALU00908459: Status Check compare script fails to parse a

hyphen character present in pre-migration status check report

file.

Problem: While reporting XDSL line and status information the

Status Check pre-migration file generates a hyphen character

instead of zeroes. The status Check compare script is unable to

parse the hyphen characters and reports a syntax error for these

XDSL line status information.

Solution: Status Check compare script adapted to accept the

hyphen char in the line section and consider the operational State

of these lines as ‘Down’ for comparison purposes.

1.104 V3.0.9


� ALU00906846: After conversion of NANT-A to NANT-D IHUB

CLI Access Rights not enabled.

Problem: After migration of NANT-A to R42 and conversion to

NANT-D the IHUB access rights were disabled.

Solution: During conversion new access rights which pertains to

R42 NANT-D default were enabled through the conversion script.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 69/176

1.105 V3.0.8


� ALU00825495: Lanx restoration failure - when migrating from

4002 to 4.2.

Problem: During migration from R4002 to R42 Lanx restoration

fails and the ISAM fails to come up since the reserved vlan 4089 is

already in use and cannot be used as internal network vlan. So a

new value need to be assigned for the internal network vlan

during migration.

Solution: A new command line option –intlnwvlan has been

introduced in the migration script through which an unused vlan

value can be specified by the user (if 4089 vlan is already used).

This will be used as the internal network vlan for NANT-D

migration. PBMT will add this vlan value to the configuration file

of the Offline Migration tool which will read this value and update

the network vlan field in the Management Vlan Table for R40 to

R41 migration path.

1.106 V3.0.7


� ALU00837444: PBMT download Script not working in R4.2

For ERAM-A.

Problem: In R4.2 for ERAM-A the CLI “show equipment slot”

command returns nt (instead of nt-a) for the NT slot since it is a

single NT system. Due to this modified CLI command response the

regular expression matching the response fails since PBMT scripts

use strict parsing mechanism. The Download script subsequently

fails since it is unable to determine the NT type.

Solution: The regular expression for the equipment slot retrieval

command has been enhanced to handle the response.

� ALU00858938: PreCheck.pl sourcing NT OFLMT files from

incorrect directories for ANSI release stream.

Problem: For ANSI release stream the PreCheck script expects the

NT Migration tool to be present in the tools/NT folder and Lanx

tool to be present in tools/Lanx folder


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 70/176

instead of tools/NT_ANSI and tools/Lanx_ANSI folder respectively.

Solution: The PreCheck.pl script has been corrected to source the

NT and Lanx migration tools from ANSI specific tools directories

for ANSI release stream.

� ALU00818866: TL1 command ENT-ONTSWCTRL is not

working.

Problem: The TL1 command ENT-ONTSWCTRL is not working

although the command is present in the build.

Solution: Extra Logging has been added in the

OntDownloadandActivation.pl to log appropriate error messages

on encountering this issue.

1.107 V3.0.6


� ALU00820178: PBMT:NANT-D redundancy migration not

happening with pbmtv3.0.4.

Problem: While migrating to R42 with NANT-D redundancy the

script exits without migrating with an error stating failure to

synchronize Software to Standby NT.

Solution: Increased the setting for default synchronization

timeout in script and made provision to override this setting with

a user defined value for sync timeout parameter in the PBMT

configuration file.

� ALU00808688: PBMT to support the --id parameter.

Problem: PBMT needs to support a –id command line parameter

in order to distinguish logfiles and result files by phase.

Solution: The user can now run the scripts with either the –id

option (or) the logfile option. The –id option has a restriction that

it cannot be used with –hosts option viz. it is usable on a single

ISAM basis and the generated result and logfiles have the format

as ID and script action represented as a four character mnemonic

appended together and file-extension log (or) result as the case

maybe.

� ALU00804222: Update default names for Migration tools.

Problem: LRM requires that the Migration tools should not be

renamed during PBMT tools installation and should retain the

same filenames present in the ISAM


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 71/176

delivery CD. The PBMT configuration file needs to set the

Migration tools to these filenames to avoid the renaming.

Solution: Changed the PBMT Configuration file to hold the same

tools names as the delivery CD.

� ALU00813833: ONT Release mapping file missing error.

Problem: The Status Check Compare script quits with an error

that the ONT Release Mapping file is missing from the PBMT

Tools folder for ANSI family ISAM equipment.

Solution: The status Check pre-migration report files are scanned

to determine whether the user has run the Status comparison

script for Converged ISAM Equipment (with GPON LT) or Normal

ISAM Equipment. ONT Release map file missing error is flagged

only when this file is missing for the Converged ISAM Equipment

by determining whether the ONT status is present in status check

pre-migration report files.

1.108 V3.0.5


� ALU00099810: NANT-A TO NANT-D MIGRATED DB IS NOT

OK.

Problem: The ISAM goes into continuous reboot when restoration

is tried on the NANT-A to NANT-D migrated database.

Solution: Support provided for R42 in PBMT for specific tables.

� ALU00820717: After Migrating huge SHUB databases the

Migration script loops indefinitely.

Problem: The Migration script loops indefinitely and is unable to

download the combined NT and SHUB database to the node. This

happens when migrating SHUB databases of size typically more

than 4MB observed in lab situations. The SHUB database

migration then takes more than an hour and the CLI session

initiated by the migration script is automatically timed out since

the timeout is set to half an hour. The script encounters a write

error due to the existing session handle not being open causing it

to loop indefinitely while trying to download the combined NT

and SHUB database

Solution: The CLI terminal timeout for migration script session

has been increased to two hours.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 72/176

1.109 V3.0.4


� ALU00441703: PBMT to provide path to the Migration tools

as command line parameters.

Problem: Requirement to specify the path of the Migration tools

dynamically via command line parameters for migrate and

preCheck scripts.

Solution: Support provided in PBMT to specify the Migration tool

paths via command line parameters.

� ALU00798337: PBMT need to support latest NTOFLMT

version.

Problem: Migration script fails with an error stating that the

Version number of NT OFLMT is higher than the one supported by

PBMT Toolset.

Solution: The Highest version of NT OFLMT usable has been

updated in PBMT for ETSI and HICAP ETSI stream

1.110 V3.0.3


� ALU00753972: PBMT displays error message that the NT

OFLMT version used is too high for the current toolset

version.

Problem: In PBMT the highest oflmt version number for ANSI

stream is maintained in the tool and the error occurs on running

migrate script since version number used is higher than that

supported by tool.

Solution: The Highest version of NT oflmt usable has been

updated in PBMT for ANSI stream.

� ALU00776272: Release streams for R4010 are not recognized

for migration by PBMT for NANT-A boards.

Problem: Migration support for R4.0.10 migration path is

currently not existing for NANT-A boards.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 73/176

Solution: Extended PBMT tool to support R4.0.10 migration path

for NANT-A board.

� ALU00776733: PBMT need to support latest NTOFLMT

version.

Problem: PBMT need to support latest NT OFLMT version for ETSI

stream.

Solution: The Highest version of NT oflmt tool for ETSI usable

has been updated in PBMT

1.111 V3.0.2


� ALU00441701: Provide default value for --oprid in param.cfg.

Problem: A default value for the parameter --oprid need to be

provided in param.cfg to be used by scripts migration.pl &

upgrade.pl.

Solution: The operator id is now added to param.cfg and can be

set to Y or N, and the migration and upgrade scripts are adapted.

� ALU00441702: Provide default value for --bufsiz in param.cfg.

Problem: A default value for the parameter --bufsiz used in

statusCheck.pl is required as a parameter in param.cfg.

Solution: BUFSIZE parameter has been added to param.cfg and

made configurable by user and defaulted to 15MB.

� ALU00719042: Migrate.pl not working for sftp and --ofldb

option.

Problem: The Backup of the DB fails when SFTP is configured in

the NE. Also while using the –ofldb command option a failure

happens when additionally not providing the –oflmt option also.

Solution: The Directory path for SFTP option in migration script

has been corrected to resolve this issue.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 74/176

1.112 V3.0.1


� ALU00363184: Converged PBMT implementation to support

GPON module migration.

Problem: For supporting GPON module migration the Upgrade

Engine Tool and Push Button Migration Tool will be integrated

and new Converted PBMT tool will be implemented.

Solution: The modifications to the PBMT Toolset include the

following:

New scripts stageont.pl and ontDownloadandActivate.pl

introduced for ONT operations. stageont.pl script performs

staging of the ONT Software package onto the node.

ontDownloadandActivate.pl script enables download of the ONT

software to the ONT from the NE and activates the ONT with the

newly downloaded software

StatusCheck script additionally collects and logs the pre and post

ONT status. The script additionally takes command options

--release for target release when ont is selected and

--ontreleasemap for dir path of ontreleasemapfile

StatusCheckCompare script will compare the ONT status and

displays warnings based on threshold levels set. The script

additionally takes command options --ontreleasemap for dir path

of ontreleasemapfile and --warn for taking threshold input.

Command options for TL1usename and TL1password included in

certain scripts viz. stageont.pl, ontDownloadandActivate.pl and

statusCheck.pl.

Command option username and password are renamed as

cliusername and clipassword whenever it is used in the respective

scripts.

Configuration parameters added to param.cfg for ONT operations,

NT Synchronization Timeout, and default SFTP username


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 75/176

1.113 V2.1.65


� ALU00735537: PBMT tries to TFTP a SW Board file although it

exists for another board.

Problem: SWDL script tries to TFTP a SW board file which is

incorrectly reported as “not-available” by Software Management

module when the board file is actually present on the disk. This

board file is actually shared between a board already known to NT

SW and board not yet known to NT. The SWDL script retrieves the

list of SW files and checks whether files that are marked as “not-

available” are related to boards defined for the node and TFTP the

missing files. The TFTP transfer results in a write access

permissions error and the SWDL script exits with a failed

download error code.

Solution: In case the SW for a particular board already exists in

the ISAM then PBMT will not perform TFTP of the same file.

1.114 V2.1.64


� ALU00717212: Migrating NT database from 400 to 417 not

possible: DB version not defined.

Problem: Due to release numbering being 4.1 for both R4.1 and

R4010 release streams the Capability model of PBMT was

upgraded to differentiate between the two releases. This

adaptation causes certain FGN41 release to not have a mapping

between the release and DB version.

Solution: The Capability model has been enhanced for ANSI

streams to provide the release to DB mapping for all FGN41

releases.

� ALU00417675: ipAware2Ibridge.pl script gives errors when

executed on two isams in row (within the same session).

Problem: ipAware2Ibridge.pl script errors for second isam when

executed in a row for lines configured in first isam but not on the

second one.

Solution: Initialization of array maintaining the reconfiguration


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 76/176

commands done to resolve the issue .


1.116 V2.1.62


� ALU00452708: cvtEcntA2C.pl doesn't use ANSI directories.

Problem: For FGN releases from FGN4.0 following the split of

ETSI and ANSI streams, PBMT still expects the Migration tools to

be present in the tools/NT and tools/Lanx directories instead of

tools/NT_ANSI and tools/Lanx_ANSI directories. Attempting to run

the ECNT-A to ECNT-C conversion script fails for these releases

with an error that it is unable to find the Migration tools.

Solution: The ECNT-A to ECNT-C conversion script now looks for

the Migration tools in the ANSI specific tools directory for releases

from FGN4.0 .

1.117 V2.1.61


� ALU00331457: Maximum number of sessions reached during

CLI session establishment using SSH.

Problem: When the Maximum session limit has been reached

and the PBMT script tries to establish a new CLI session using SSH

an error message for maximum session reached is not displayed.

Solution: Modified the script to display an error message that

the Maximum session limit is reached when it is unable to open a

new SSH session in this scenario.

� ALU00333275: Migration failed in FGN42 while using --

ofldb option.

Problem: Migration script terminated via Perl DIE signal while

migrating from FGN41 release to FGN42 since the script is unable

to determine the SW version using the offline version of the DB.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 77/176

Solution: In the case of ANSI stream with NT DB version Nx.yyy

the script has been modified to determine the SW version

correctly.

� ALU00386912: Update PBMT tool to support R4.0.10

migration path for NANT-D boards.

Problem: Migration support for R4.0.10 migration path is

currently not existing for NANT-D boards.

Solution: Extended PBMT tool to support R4.0.10 migration path

for NANT-D board.

1.118 V2.1.60


� ALU00358413: Voice IP inventory script missing in PBMT

package

Problem: Conversion from H.248 to SIP uses a voice-IP to OAM-

IP mapping inventory. The script generating this overview is

missing in the tar package.

Solution: Included the script in the tar package.

1.119 V2.1.59


� ALU00345808: 7330 not coming up with NANT-A to NANT-D

converted database

Problem: A 7330 NANT-D system is not coming up when

activated with a database converted from a NANT-A system.

Solution: A typo in the NTIO SFP information datastructure

resulted in an error in the CLI command when configuring SAPs

(there was a space character inserted for certain SFP ports).

1.120 V2.1.58


� ALU00340197: Modified NTIO handling


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 78/176

Problem: NANT-A to NANT-D conversion expects the planned

and configured NTIO to be identical. This also means that if an

NTIO is planned it is expected to be present too.

Solution: Allow a planned NTIO even if not HW-wise present, this

is now accepted by the NANT-D software too.

1.121 V2.1.57


� ALU00259276 : PBMT error with minimized download option

Problem: When using a board mnemonic file to minimize the

SWP and subsequently downloading the minimized package, in

case additional LT boards which are not mentioned in the board

mnemonic file are inserted in the ISAM, software download aborts

with an error that the support software for the additional boards

are not present in the minimized package.

Solution: When the “force” command option is used in the

download script, the download process will skip the check

whether the software for all the boards provided in the board

mnemonic file are present in the SWP.

1.122 V2.1.56


� ALU00268313 : New command option for ipAware2Ibridge

script.

Problem: A new command option to allow the setting of the

max-unicast-mac when converting an IP-aware bridge into an

enhanced I-bridge needs to be added to the ipAware2Ibridge

script.

Solution: The command option “bridgeportmac” has been added

to the ipAware2Ibridge script.

� ALU00257699 : PBMT support for LANX migration tool 1.58.

Problem: A new SHUB OFLMT has been delivered for

R4.2/FGN4.2 which is not yet supported by the PBMT scripts.

Solution: Support for SHUB OFMLT 1.58 and NT OFLMT 17.0.0

has been added


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 79/176

� No FR: Support for Mini-NT (NRNT-A) and NANT-E boards.

Problem: Currently PBMT does not support new boards NRNT-A

and NANT-E.

Solution: The new boards have been introduced into the


1.123 V2.1.55


� ANTmt91104/ALU00100007 : SW dir permissions not set

when not reducing.

Problem: When SW minimum-set files are tried to be

downloaded by the swdl.pl script the script fails although the

software files are successfully transferred to the node.

Solution: When a user tries to download an OSWP already

existing in the active bank, the download will be done to the

active bank rather than to the passive bank. This would resolve the

TFTP write failure when the missing software files are TFTP'ed to

the node and script run will be successful.

� ALU00194284 : Intermittant telnet session establishment

problem.

Problem: Telnet failure occurs after closing a telnet session and

re-opening the telnet session in quick succession resulting in data

not being read from the telnet session.

Solution: A delay was introduced after closure of a telnet session

to resolve the issue.

1.124 V2.1.54


� ANTmt90464/ALU00099810: NANT-A to NANT-D migrated

DB not OK.

Problem: The NT does not successfully restart with a converted

NANT-A database.

Solution: Added a check to prevent that the network and stacked

VLAN have identical values.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 80/176

1.125 V2.1.53


� ANTmt88407/ALU00160040: Porting of PBMT to INTEL

Solaris x86 platform.

Problem: Extend PBMT tool support for usage in the INTEL

Solaris x86 platform.

Solution: Recompilation of the PERL module scripts used by

PBMT was performed on the INTEL Solaris x86 platform and

updates to the Perl scripts done in order to look for the correct

platform libraries depending on the detected architecture.

1.126 V2.1.52


� ANTmt94769 / ALU00113599: TFTPDIR text for 5520 AMS

while running Config.pl to be modified.

Problem: While running Config.pl the prompt for the TFTP top

level directory is displaying outdated information.

Solution: Updated the Configuration script with the correct TFTP

top level directory information.

� ANTmg01050 / ALU00114408: Total_MiB label change from

Ex.x.y.z to Vx.x.x.y.z.

Problem: Due to the ISAM MiB label extension from E.x.x.y.z (4

digits) to V.x.x.x.y.z (5 digits) & where x.y.z. can be 2 digits each ,

the PBMT scripts need to be updated.

Solution: The MIB label change has been adapted in the PBMT

scripts.

� ANTmg00960 / ALU00114366 : Megaco Migration is failed in

4102.322.

Problem: Megaco Migration fails since the IVPS tool reports that

the configuration file name is too long since the total length of

the pathname and filename exceeds 128 chars.

Solution: The calling convention of the configuration file name

has been changed to overcome the length limitation.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 81/176

1.127 V2.1.51


� ANTmt92349 (ANTmt95207, ANTmt95208): Warning

generated during HW conversion NANT-A to NANT-D

Problem: When converting a NANT-A database to NANT-D in

certain cases a warning message is generated resulting in

incomplete warnings in the warning file generated by the script. A

typing error in a hash data structure has been corrected.

� ANTmt95140 (ANTmg01205, ANTmg01206): BITS setting not

ok when converting a NANT-A database to NANT-D.

Problem: Due to incomplete specifications the resulting database

displayed non-consistent results on a NANT-D system with

respect to the BITS setting. The specification has been completed

and implementation has been adapted.

1.128 V2.1.50


� ANTmt92967: Migration-err code not being picked up

correctly.

Problem: When software upgradation fails due to any reason the

error is not picked up and script exits successfully despite the old

software being still active.

Solution: A check has been added to see if the old software is still

active after upgrade in which case the proper exit code is used.

� ANTmt89558: StatusCheckCmp.pl incorrectly compares post

and pre.

Problem: The Status Check comparison of the lines out-of-service

pre and post migration displays an incorrect result since it

considers the admin-down lines as part of the configured lines.

Solution: Consider only lines which are admin-up for calculation

of lines out-of-service during status check compare.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 82/176

1.129 V2.1.49


� ANTmt90246 (ANTmt91017, ANTmt91018): NANT-A to

NANT-D HW migration problem.

Problem: The system does not restart with a converted database.

The problem was due to the usage of the value 0 for a customer

ID.

Solution: The HW conversion script now rejects invalid customer

and service IDs when provided as command-line arguments to the

script.

1.130 V2.1.48


� ANTmt88831 (ANTmt90935): ihub-link alarm : no details

available via cli-cmd.

Problem: After restarting a NANT-D system with a converted

NANT-A database ihub-link alarms are not displayed correctly.

Solution: Due to an incorrect setting of the port numbering

scheme in the converted DB ports are not correctly translated by

the system. This has been corrected by setting the port

addressing mode to the system default during the HW conversion

making sure that the NT initializes the port addressing scheme

with the correct value when the system restarts.

1.131 V2.1.47


� ANTmt83962: Change the Transaction Timeout to a finite

value in PBMT.

Problem: While performing a migration/upgrade, in rare cases

the system is left with a CLI/TL1 session transaction being taken

while the transaction timeout was set to indefinite.

Solution: Set the CLI/TL1 session transaction timeout to a value of

one hour when taking a CLI session during the PBMT operations.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 83/176

� ANTmt84679: Call to UNIX TAR utility is not properly

invoked.

Problem: Calling the UNIX TAR command fails because in one

occasion it is called without specifying a directory path. If

another TAR executable is found in the PATH environment setting

it is possible that the operation of the PBMT migration tool gets

disturbed.

Solution: Call the TAR utility as configured in PBMTs

configuration file.

� ANTmt84725: PBMT support required for FGN42.

Problem: Currently PBMT does not have support for R4.2.

Solution: Included support for R4.2 in all streams into the


� ANTmt86146: PBMT fails when on Octopus session is open.

Problem: In certain cases PBMT incorrectly assumes that an

Octopus session is open to the NE for which a PBMT script is

activated (e.g session open for ISAM with IP 10.10.10.10 while

migration is requested for ISAM with IP 10.10.10.100).

Solution: Extend the string match to include “:udp”

� ANTmt86148: DB version 1.10 need to be added for 7354RU.

Problem: Support for R1.1 of 7354RU need to be updated in

PBMT.

Solution: The new release version has been introduced in the


� ANTmt85862: SWDL fails if isadmin not in cli prompt.

Problem: The SWDL failure is due to the expected telnet prompt

delimiter not being present at the end of the prompt.

Solution: Prompt without delimiter is now correctly handled.

� No FR: In case of online SW reduction during SW download,

there is a need to eliminate TYPE-K files from the uploaded

SWP file.

Problem: Package reduction fails when PBMT tries to upload a

TYPE-K file for which it is not sure that this file is present on the

TFTP server.

Solution: Remove the TYPE-K file while performing reduction of

the SWP file


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 84/176

1.132 V2.1.46


� ANTmt80806: Software download fails when snmpV2 is

configured.

Problem: PBMT fails to determine the File transfer protocol when

snmpV2 option causing the software download not to happen.

Solution: Extended the check on the File transfer protocol format

returned by the SNMP Get request.

� ANTmt82134: Statuscheck script fails while running on

R2.4.01y nodes.

Problem: StatusCheck script fails since it cannot determine the

CLI slot number mode.

Solution: Return legacy-mode as CLI numbering in case the

release does not support the feature.

� ANTmt83235: Offline migration failure due to insufficient

arguments for migration subroutine.

Problem: While migrating using the -oflonly option the offline

migration fails due to missing arguments for migration subroutine

module.

Solution: Corrected the migration subroutine call

� ANTmt82666: CDE dir is empty in migrated DB when using --

ofldb.

Problem: On performing migration using –oflonly option the CDE

directory is empty in the migrated database.

Solution: Flag an error indicating unsuccessful migration when

CDE file is not present.

� ANTmt81165 (& clone ANTmt82012): CLI command timed-

out during NANT-A to D conversion.

Problem: While using large shub configuration the NANT-A to

NANT-D conversion fails with command timed-out error.

Solution: Long CLI response has been handled.


� No FR: Need to

configure


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 85/176

SNMPv2 and SNMPv3 settings using default option in

Config.pl script.

Problem: While running the Config.pl script using default option

the SNMPv2 and SNMPv3 settings are not set in param.cfg.

Solution: Introduced new subroutine in PBMTConfig.pm to set

the SNMPv2/SNMPv3 configurations only for default option.

1.133 V2.1.45


� ANTmt79820: HW migration from NANT-A to NANT-D fails:

stack erro.

Problem: NANT-D fails to come up due to VLAN 0 being used as

stacking VLAN value.

Solution: When converting a R4.0 NANT-A database the value for

the stacking VLAN (0 for NANT-A) needs to be changed to 4092

(default) of another value in case 4092 is used (see also

ANTmt79840).

� ANTmt79840: HW migration from NANT-A to NANT-D not

OK when VLAN 4092 is used on SHUB.

Problem: By default VLAN 4092 is used internally. This results I

conflicts when VLAN 4092 is used on the SHUB.

Solution: Determine a free VLAN to be allocated to the internal

stacking VLAN based on the VLAN IDs being defined on the

SHUB.

� ANTmt79475 (and clones ANTmt79477, ANTmt79478,

ANTmt79482, ANTmt79483, ANTmt79484, ANTmt79485): CLI

sometimes fails during migration.

Problem: It has been noticed in the field that sometimes opening

a telnet session for the second time fails.

Solution: A workaround has been included in PBMT where we will

make a number of connection attempts using a delay between the

connection attempts.

� ANTmt77547: Can’t locate warnings.pm

Problem: Sometimes the PBMT scripts exit with the warning

‘Can’t locate warnings.pm’.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 86/176

Solution: the file warnings.pm requires PERL 5.6.0. A ‘require

5.6.0’ has been included in the PBMT scripts resulting in an error

message that PERL 5.6.0 is required to run this version of the

package.

� ANTmt77854: StatusCheck.pl error for the ETSI HiCap NE

family.

Problem: Running statusCheck.pl an a NANT-D fails with an error

message that a certain function can’t be found.

Solution: Corrected the incorrect function call.

� ANTmt78632: NANT-A to NANT-D conversion problem with

LAGs.

Problem: It is not possible to create a LAG on a converted NANT-

A that has been downloaded on a NANT-D.

Solution: Unused ports and ports which have MSTP disabled will

not be considered when creating a SAP on VLAN 1 (reserved

VLAN in the SHUB) of on the m-VPLS (for the MSTP settings).

� ANTmt75927: Cache overflow error record when restoring

converted NANT-A database on a NANT-D.

Problem: When restoring a converted NANT-A database on a

NANT-D cache error records are showing up with each reset of

the NT.

Solution: This error record is a consequence of the fact that the

NT database still contains the TL-1 command set data related to

the NANT-A. The TL-1 command set is now recreated in function

of the NANT-D release.

1.134 V2.1.44


� ANTmt77648 (and clones ANTmt77748, ANTmt77749,

ANTmt77750, ANTmt77751, ANTmt77752, ANTmt77753):

PBMT V2.1.43 checks for CDE profile for non-ISAMV.

Problem: Migration of a non-ISAM-V fails due to a missing new

CDE file.

Solution: This is a side-effect of the fix for ANTmt77273 resulting

in a too strict test that should not be carried out for non-ISAMV

systems.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 87/176

1.135 V2.1.43


� ANTmt77273: ISAM-V migration fails using an offline-stored

database.

Problem: Migration of an ISAM-V of an offline stored database

(using the –ofldb command line option) fails.

Solution: Modified the code taking the correct settings into

account. Problem only applicable to lab environments (this mode

of working is not how field customers migrate the network).

� ANTmt76329: Restoration of converted NANT-A to NANT-D

database fails.

Problem: Restoration of a converted R4.1 database on a NANT-D

fails.

Solution: A new requirement with respect to a modified NT

database table has been implemented.

1.136 V2.1.42


� ANTmt76748: LAG going for shutdown after NANT-D

conversion.

Problem: When converting a NANT-A configuration to a NANT-D,

the status of the LAG is shutdown while the LAG should be

enabled.

Solution: Corrected the mapping between SHUB and IHUB values.

� ANTmt76329: Warning error is misleading during NANT-D

HW conversion.

Problem: The tool reports a warning not to download a converted

database onto the the NANT-D when null-SAPs are used on a

LAG. Earlier releases of the NANT-D did not accept the database

in that case.

Solution: Now that the error has been corrected in the NANT-D

code this warning is no longer required. It has been removed.

� ANTmt76317: Inconsistent MSTP forward-delay value causes

NANT- D to


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 88/176

rollback.

Problem: Due to a relationship between the hello time,

forwarding delay and bridge max age time usage of inconsistent

values leads to the NANT-D not accepting a converted database.

Solution: Introduced dependency checks when converting the

forward-delay and hello-time values.

1.137 V2.1.41


� ANTmt75743 : PBMT upgrade script behaves in an

unexpected way.

Problem: After upgrading a R4.1 ECNT-E based system, the NT

performed a rollback but the upgrade script indicated a successful

upgrade.

Solution: The code was not picking up all return codes when

determining that the active SW is actually the new SW. All

function return codes are checked now.

1.138 V2.1.40


� ANTmt76101: Latest SHUB OFLMT version is 1.55

Problem: A new SHUB OFLMT has been delivered for R4.1 which

is not yet supported by the PBMT scripts.

Solution: Support for SHUB OFMLT 1.55 has been added.


� ANTmt75942 : MSTP port parameters are not mapped to m-

VPLS SAP STP.

Problem: When converting a NANT-A configuration to a NANT-D,

the MSTP port parameters are not mapped to the m-VPLS SAP

STP configuration.

Solution: Added the missing mapping.

� ANTmt75993 (clones ANTmt76137, ANTmt76138,


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 89/176

ANTmt76139): Migration fails when NT is positioned at slot

NT-B.

Problem: In case the NT is positioned at slot NT-B (NT-A is

empty) migration fails.

Solution: The OID passed to the SNMP-get to retrieve the type of

the NT inserted at the NT-B slot position was passed by value

rather then by reference. This has been corrected.

1.139 V2.1.39


� ANTmt59610: Modified table layout in R4.1

Problem: R4.1 defines a new layout for clock management tables.

These modifications need to be taken into account during the

NANT-A to NANT-D HW conversion

Solution: Clock management tables according to the new layout.


� ANTmt74645 (clones ANTmt75670, ANTmt75671,

ANTmt75672, ANTmt75680, ANTmt75682, ANTmt75683) :

CLI session can be erroneously marked as being taken

Problem: It may happen when using the –host option that a CLI

session remains marked as being taken when the processing of a

certain ISAM fails. Opening a CLI session for a new ISAM is

rejected in that case.

Solution: Reworked the CLI session management to be host and

service (telnet and SSH) based.

� ANTmt75819: Could not migrate a simplex ISAM-V due to

exceeding a limit of the number of files in the migrated

backup.

Problem: In case too many files are stored in the migrated

database, downloading this on a duplex system results in a

continuous reset. A check is made to prevent this database from

being downloaded.

Solution: Check should only be done for duplex (active) systems.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 90/176

1.140 V2.1.38


� ANTmt73667: Change VLAN MAC aging timer when

converting IP-aware bridge to Enhanced I-bridge

Problem: The customer asked a reconfiguration of the VLAN MAC

aging timer when converting the IP-aware bridge into an enhande

I-bridge.

Solution: Added a new command option (--ageing <n>) to

enable specification of a MAC aging time (expressed in seconds).


� ANTmt62118: chgNwVlan.pl, VLAN deletion error

Problem: Deleting the VLAN to be reconfigured fails in case

MCAST SRC have been configured.

Solution: Remove and reconfigure the MCAST SRC when

reconfiguring the network VLAN. A new command option was

added (--sleep <n>) resulting in a delay (expressed in seconds,

default value is 5) when deleting the VLAN. In some cases

deletion of the VLAN may fail because the system did not free up

all resources associated to this VLAN.

� ANTmt72232: Conversion to ECNT-E looks in wrong directory

for offline migration tool

Problem: The ECNT-E is only defined in the ANSI stream and

consequently the ANSI offline migration tools should be used.

Solution: The offline migration tools are picked up from the

correct location.

� ANTmt73759, ANTmt74082: Restarting NANT-D with a

converted DB fails

Problem: The NANT-D system performs a rollback when restarted

with a DB converted from NANT-A.

Solution: Correct the FeatureFlags database table.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 91/176

1.141 V2.1.37


� ANTmt70296, ANTmt72975: preCheck.pl is not OK in 2.1.35

Problem: When running the pre-checks for a HiCap ISAM (NANT-

D) an unknown sub-routine is called.

Solution: Corrected the namespace problem.

� ANTmt72859: SW DL fails from R3.4.03e to R3.7.03 for NANT-

A

Problem: SW DL fails reporting that R3.7.03 is not a valid

migration path.

Solution: Corrected the check (hash structure check).

� ANTmt72875: SHUB SW version not updated in PBMT

Problem: The SHUB SW version has been modified for the ANSI

stream.

Solution: PBMT also considers the modified SHUB SW version

string.

� ANTmt72969: ipAware2Ibridge fails to delete VLAN

Problem: Conversion of an IP-aware bridge to an enhanced I-

bridge fails when deleting the VLAN (VLAN still in use).

Solution: A new command option was added (--sleep <n>)

resulting in a delay (expressed in seconds, default value is 5) when

deleting the VLAN. In some cases deletion of the VLAN may fail

because the system did not free up all resources associated to this

VLAN.

1.142 V2.1.36


� ANTmt71238

Problem: ECNT-A/C to ECNT-E Conversion Script.

Solution: Delivery of the ECNT-A/ECNT-C to ECNT-E conversion

script is done through the FR.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 92/176


� ANTmt71612: No sap configuration for vpls if ntio applique

not physically present

Problem: NTIO port configuration in NANT-A are not converted

to vpls sap configuration in NANT-D if NTIO is not physically

present.

Solution: Generate a warning in the warning file in case a planned

NTIO is not physically present but still perform the VPLS SAP

conversion.

� ANTmt70090: NANT-A to NANT-D: no SNMP reachability

after database conversion

Problem: No SNMP reachability to IHub after migrating from

NANT-A to NANT-D.

Solution: Convert the SHUB context to IHUB context.

� ANTmt70258: Conversion of NCNC-C to NCNC-E is not

working.

Problem: Conversion of NCNC-C to NCNC-E generates an

“undefined subroutine” error.

Solution: Namespace included in the conversion script to correct

the error.

� ANTmt70751: ErrorCodes.pm line 1722 warning issue in pbmt

Problem: Uninitialized value in sprintf occurs in while running

script exitcode.pl script.

Solution: Corrected the format in the error string conversion

routine.

� ANTmt70461: Warnings generated when upgrading R37.317

to R37.320

Problem: Warning Error records occurring while running upgrade

script for NANT-D upgrade.

Solution: Warnings resolved by calling appropriate library

function to fetch the NT DB version for release pertaining to the

Isam family.

� ANTmt70255: NTReset.pl is not working.

Problem: perl NTReset.pl is not working pbmt & not in use

conversion fails.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 93/176

Solution: Script is no longer applicable and has been removed

from this package.

1.143 V2.1.35


� ANTmt69142, ANTmt69157, ANTmt69158, ANTmt69160:

convertCcEngine.pl fails.

Problem: When trying to enable MAC@ concentration using

KPN’s adapted requirements, the conversion fails.

Solution: Corrected a misplaced if-statement resulting in no

deletion of CC clientports prior to deletion of the CC-egine.

1.144 V2.1.34


� ANTmt67832: No xVPS inventory script fails ISAM-V

migration.

Problem: When trying to migrate an ISAM-V from R3.6 to a

higher release the migration fails due to a missing xVPS inventory

script.

Solution: Relaxed the check on the existence of the xVPS

inventory script as it is not needed for migrations higher then

R3.5.

� ANTmt66776: NANT-D not pingable after restart with

converted DB

Problem: When restarting the node with a converted NANT-A

database the system is not pingable.

Solution: Make sure v-VPLS SAPs are created on the v-VPLS

carrying the management traffic. Problem occurred when a

management VLAN was passed on the command line that was

different from the management VLAN used on the NANT-A.

� ANTmt68267 and its cloned ANTmt68271, ANTmt68272,

ANTmt68274, ANTmt68275, ANTmt68276, ANTmt68277,

ANTmt68278, ANTmt68279: PBMT tools fail due to changed

CLI output


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 94/176

Problem: PNMT tools fail due to a change in CLI output. In some

releases the board serial number is enclosed between double

quotes while in other releases it is not.

Solution: Make sure the board serial is correctly parsed in both

conditions.

1.145 V2.1.33


� ANTmt65332: NTT OSWP/SWP identifiers are AC instead of

AA.

Problem: The SW package for NTT is identified by ‘AC’ rather ‘AA’

as used for ETSI SW packages.

Solution: Included support for NTT SW packages.

� ANTmt66776: cvtNantA2D command option issue

Problem: The node’s IP address is not correctly transferred.

Solution: The IP address as stored in the DB is correctly converted

and transferred to the IHUB configuration.

1.146 V2.1.32


� ANTmt63248: NANT-A to NANT-D HW conversion errors

Problem: When converting a NANT-A database to a NANT-D

database some incorrect conversions were done.

Solution: Initial fix is incomplete: do not handle SHUB ports that

are not part of the physical configuration (e.g. in case no NTIO is

present ports 2..7 should not be handled although they show up

in the SHUB configuration output).

1.147 V2.1.31


� ANTmt67268: Can’t create SAP on NTIO port


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 95/176

Problem: When converting a NANT-A configuration to NANT-D

SAP creation on an NTIO port fails.

Solution: Clear the internal command storage before retrieving

the appliqué info rather then after this step.

1.148 V2.1.30


� ANTmt67067: Support for SHUB OFMLT V1.54

Problem: SHUB offline migration requires OFLMT version 1.54.

Solution: Include support for SHUB OFLMT 1.54

� ANTmt65332: NTT OSWP/SWP identifiers are AC instead of

AA.

Problem: The SW package for NTT is identified by ‘AC’ rather ‘AA’

as used for ETSI SW packages.

Solution: Included support for NTT SW packages.


� ANTmt56708: convertCcEngine.pl deletes network-vlan from

a bridge port

Problem: The PPP cross-connect engine with MAC@

concentration is currently only required for ADSL configurations.

Solution: Include a command-line option (--efm) to also include

lines of non-ADSL boards in the conversion (by default the

conversion is limited to ADSL ports).

� ANTmt64026: Some IHUB LAG configs missing after

conversion

Problem: A port for which the lacp-mode is set to disable-lacp

will not be included in the LAG as configured on the IHUB.

Solution: This is by choice. The warning file will contain this

“failure”.

� ANTmt64946: Migration fails for MCAST configuration

Problem: A new command option was not parsed resulting in a

failure.

Solution: Include parsing of the

[no] inhibit-alarms option.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 96/176

� ANTmt65176: Configure LAG port command fails on DB

restoration

Problem: For ports part of a LAG, auto-negotiation must be set to

off or limited.

Solution: An incorrect code construction has been corrected.

� ANTmt67006: Converted DB restoration fails

Problem: IGMP snooping mrouter-port and send-queries can not

be enabled at the same time.

Solution: Configure mrouter-port on NT SAPs only and send-

queries only on LT SAPs.

� ANTmt66776: cvtNantA2D command option issue

Problem: command line options –host and –split are not

supported.

Solution: These command line options were originally foreseen

but have been suppressed in the official version.

� ANTmt64960: No mapping of admin-status auto-up

Problem: DB conversion fails in case the admin status of a port is

auto-up.

Solution: Admin status auto-up is mapped on no shutdown.

� ANTmt66221: Error in processing config file command

Problem: The query-response interval must be less then the

query interval for IGMP-snooping.

Solution: In case the query-response interval is greater then or

equal to the query interval, the value of the query-response

interval is set to value of the query interval minus 1.

� ANTmt65143: Warnings generated for some MSTP

configurations

Problem: When using the debug option a warning is generated

stating that “mstp” is not numeric.

Solution: Corrected the sprintf statement to print a string rather

then a decimal value.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 97/176

1.149 V2.1.29


� ANTmt64990, ANTmt65166: SWDL fail on ECNT-C using

PBMT 2.1.28

Problem: The defence added through ANTmt64836 includes a

call to Capability.pm from Octopus.pm. As such a “require

Capability” was included. A side effect of this apparently seems to

be that data structures do not get initialized properly.

Solution: Include the code in Octopus.pm required to achieve the

same functionality as we would call the function defined in

Capability.pm.

1.150 V2.1.28


� ANTmt64836: Warning message when parsing

readOswpFW.log

Problem: A warning message is generated when trying to

determine the active OSWP from the readOswpFW.log file when

using T&D command parsing.

Solution: Added a conditional to prevent the code from being

executed in case the variable is not yet initialized.

� ANTmt64530, ANTmt64534: Error when converting NANT-A

to NANT-D.

Problems:

• The IGMP leave-rsp-timer was incorrectly mapped.

• IGMP activation was attempted in case of an IGMP bundle

being present in the SHUB configuration while this should

not have been done.

Solution: Corrected these error conditions.

1.151 V2.1.27



3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 98/176

� ANTmt62662: Allow the usage of pub/priv keys for SSH

Problem: SSH also allows the usage of public/private keys for

authentication. PBMT does not yet fully support this.

Solution: Allow usage of private/public key pairs for SSH.


� ANTmt63037: Migration fails due to SNMP message too big

error

Problem: When using SNMPv2c or SNMPv3 there are conditions

where the resulting SNMP message is getting too big.

Solution: Call SNMP table-walk functions using the

“maxrepetitions” parameter to prevent the message from

becoming too big.

� ANTmt63248, ANTmt63707: NANT-A to NANT-D HW

conversion errors

Problem: When converting a NANT-A database to a NANT-D

database some incorrect conversions were done.

Solution: LAG reconfiguration errors have been corrected.

� ANTmt64040: PBMT determines incorrect active OSWP

Problem: In case the NT has not been restarted PBMT uses

alternative methods to determine the active OSWP due to the

regular commands not returning any information. The

workaround introduced in R2.4 for ECNT-A does not seem to work

in this case

Solution: Modified the workaround code to deal with the new

situation.

1.152 V2.1.26


� ANTmt62387, ANTmt63435: Warning message when

upgrading an ETSI (NANT-A based) ISAM using migrate.pl

Problem: Warning messages are generated when the migration

script is used to upgrade an ETSI ISAM. This is not the case when

using the upgrade.pl script.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 99/176

Solution: Call the ETSI ISAM upgrade plugs to upgrade an ETSI

ISAM rather then the general 7302 plugs.

1.153 V2.1.25


� ANTmt61239, ANTmt63218: Add support for 1540Litespan NE

family

Problem: The 1540Litespan supports a re-packaged NANT-A

variant (GEB3-B). PBMT has no support for migration of the NE

family.

Solution: PBMT now also supports the 1540Litespan NE family

(GEB3-B NT type).

1.154 V2.1.24


� ANTmt60891/ANTmt61120: Warning message when running

migrate.pl from AMS GUI

Problem: A warning message is generated when the migration

script is run from the AMS GUI. Apparently some initialization

from the param.cfg file is not complete when running PBMT from

AMS GUI windows.

Solution: Catch this uninitialized configuration.

1.155 V2.1.23


� ANTmt60738: No offline migration for xVPS R4.1/FGN4.1

Problem: No offline migration is required for xVPS in

R4.1/FGN4.1.

Solution: xVPS database version will remain as for R4.0/FGN4.0

� ANTmt61545: migrate.pl dies

Problem: The migrate.pl script results in a PERL DIE in certain

conditions.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 100/176

Solution: This problem has been corrected.

1.156 V2.1.22


� ANTmt60596: SHUB VLAN mode layer2-terminated not

supported by the change neytwork VLAN script.

Problem: The chgNwVlan.pl script does not support SHUB VLAN

mode layer2-terminated.

Solution: The script now also accepts layer2-terminated VLANs.

1.157 V2.1.21


� ANTmt60512: FGN4.1 NT database version is Nx.yyy.

Problem: The NT database version from FGN4.1 onwards is

Nx.yyy rather then Ax.yyy.

Solution: Include support for ANSI stream NT DB version Nx.yyy.

� ANTmt60515: DB table layout for table FeatureFlags has

changed.

Problem: The hardware conversion script to convert a NANT-A to

NANT-D database creates a new NT table introduced in R4.0.02.

A field of this table has a changed syntax.

Solution: Create the Feature field with the correct syntax

(UNSHINGED_LONG in stead of LONG).

1.158 V2.1.20


� ANTmt60167: ipAware2Ibridge takes too long.

Problem: Execution of ipAware2Ibridge script on a full customer

DB takes too long.

Solution: Suppressed the sleep statement between the issued CLI

commands. This is an official delivery of a test version tried

before.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 101/176

1.159 V2.1.19


� ANTmt60011: SW DL fails because no SSH access is possible

although SSH is not configured in the node.

Problem: The SW DL script complains that no SSH access is

possible to the node even though the node is not configured for

SSH.

Solution: By default both the secure and non-secure channels are

enabled. PBMT will only check the know-hosts file in case only

the secure channels are available in the node.

� ANTmt59954: SW minimization not ok in case of non-default

NT community string.

Problem: SW minimization fails when a non-default NT

community string is configured in the node.

Solution: The SW minimizer script now uses the NT community

setting as found in param.cfg. Usage of a board configuration file

is preferred above retrieving the list of boards from the node.

1.160 V2.1.18


� ANTmt60011: SW DL fails because no SSH access is possible

although SSH is not configured in the node.

Problem: The SW DL script complains that no SSH access is

possible to the node even though the node is not configured for

SSH.

Solution: Corrected bit-shift operator to be a bit-shift operator

and not a comparison operator.

1.161 V2.1.17


� ANTmt59036, ANTmt58787: Pre-check fails if TL-1 is not

allowed.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 102/176

Problem: The status check script exists with an error code in case

no TL-1 access is allowed.

Solution: PBMT tools check the TL-1 access bits and determine

whether TL-1/UDP, TL-1/SSH or no TL-1 access is allowed. The

status checking script acts accordingly.

1.162 V2.1.16


� ANTmt59034, ANTmt59720: Pre-check on database with SSH

fails.

Problem: The status check script uses telnet to connect to node

when SSH is required, even when the PBMT environment has been

configured for SSH.

Solution: Incorrect data initialisation resulted in usage of Telnet

rather then SSH. Using the –ssh command line option results in

correct CLI access.

1.163 V2.1.15


� ANTmt56637: Converting IP-aware bridge to enhanced I-

bridge fails.

Problem: It is not possible to remove a VRF as long as the related

DHCP agent has a broadcast-VLAN associated. The broadcast-

VLAN first needs to be reset to 0.

Solution: Due to a code change in the NT it is now required to

reset the broadcast VLAN of the associated DHCP agent before

the VRF can be removed.

� ANTmt56552, ANTmt57835, ANTmt57839: PPPox MAC@

configuration tool malfunction.

Problem: This FR expects that the reconfiguration tool would set

the dslf-iwf-tag option. This requirement is outside the scope of

the script.

Solution: When this option is required one has to make sure that

this option is enabled before the reconfiguration is done. The

script is modified to copy this option when

the engine is reconfigured.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 103/176


� ANTmt57304: Support of latest xVPS offline migration tool

Problem: PBMT does not yet support version 4.0.1 of the xVPS

OFLMT.

Solution: Support for this version is included.

1.164 V2.1.14


� ANTmt54684: Access operator ID not OK after migration.

Problem: The access operator ID is not applied when migrating a

system from a release higher then R3.6 to a new release and

specifying an access operator ID.

Solution: Since the access operator ID is introduced in R3.6 it is

only possible to introduce the access operator ID in the DB

through offline migration when migrating to R3.6. PBMT will set

the access operator ID (when requested) prior to migration of the

DB when migration is requested from R3.7 onwards.

� ANTmt56869: ECNT-C unknown for R4.0.

Problem: When trying to download R4.0 SW onto an ECNT-C

ISAM, it is getting rejected with the error message that this board

is not supported for R4.0.

Solution: The ECNT-C was accidently removed from the R4.0

capabilities.

1.165 V2.1.13


� ANTmt55717: PBMT warning for upgrade.pl.

Problem: When trying to upgrade an AGNT-A system, some

warning messages are issued by the script. The root-cause of the

problem is due to the fact that the AGNT-A can belong to both

ISAM stream (ETSI and ANSI).

Solution: Support AGNT-A in both ETSI and ANSI release streams.

� ANTmt56626: PBMT does not support SHUB OFLMT V1.52


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 104/176

Problem: PBMT does not support the latest SHUB offline

migration tool.

Solution: PBMT now support SHUB OFLMT V1.52 and NT OFLMT

15.0.2.

1.166 V2.1.12


� ANTmt54584: SW download failed

Problem: The SW download script dies in case of DL failure.

Solution: The PERL DIE was caused by calling an incorrect

subroutine, this has been corrected.

� ANTmt54730: Do not create an empty DB when using

migrate.pl --actonly

Problem: When performing migration in two steps (using the

options –noact and –actonly) an empty DB is also created in the

second step. This results in the DB uploaded in the first step to

get lost.

Solution: Do not create an empty DB when the –actonly option is

used as such preserving the DB uploaded in the step when –noact

was used.

� ANTmt54955: The SW DL script sometimes hangs

Problem: In case a SW DL ended abnormally and the transaction

could not be released, starting the DL again results in the SW DL

hanging forerver.

Solution: Make sure the script does not wait forever for the

transaction owner to be released.

� ANTmt55248: ECNT-A to ECNT-C convertion on R4.0 fails

Problem: Converting an ECNT-A to an ECNT-C on R4.0 fails.

Solution: The ISAM stream split was not applied for the

convertion script. This has been corrected.

� ANTmt55561: upgrade.pl fails due to DB backup failure

Problem: When upgrading an NT to a new maintenance or EF

release, the upgrade may get aborted due to a DB backup failure.

Solution: Make sure that an empty DB has been created before


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 105/176

attempting a DB upload (in case of tftp).

1.167 V2.1.11


� ANTmt54050: Error during SWDL for Legacy Systems.

Problem: For legacy systems the equipment LT slot retrieval

mechanism considers Alarm and Special Boards as LT's due to

which the SW Download script fails expecting descriptor files for

the Alarm boards. Additionally missing LT Board type information

is not properly displayed in error message during failure of SW

download.

Solution: Extra check implemented to filter Alarm/Special boards

and corrected SWDL error message display for missing LT.

1.168 V2.1.10


� ANTmt51710: PBMT does not support SHUB OFLMT V1.51

Problem: PBMT does not support the latest SHUB offline

migration tool.

Solution: PBMT now support SHUB OFLMT V1.51

� ANTmt52181: commit.pl results in a PERL die

Problem: When executing commit.pl the script aborts via a PERL

DIE.

Solution: Corrected a function call using the correct parameters.

1.169 V2.1.9


� ANTmt50504: Migration tool fails to create file

Problem: Depending on the file-transfer protocol defined in the

node, files need to be uploaded on different locations. For ISAM-

V there are some exceptions to that rule: prior to R3.5 xVPS

database are up- and downloaded using tftp only since this is the

only protocol supported by the xVPS.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 106/176

From R3.5 onwards the xVPS database is included in the NT

backup. Consequently different locations may be required for

uploading the NT and the xVPS database.

Solution: This problem has been fixed.


� No FR: Verify SW support of boards a SW package.

Problem: Some releases may no longer provide support for

certain boards. This is now not checked prior to downloading the

new SW.

Solution: Check SW support of the boards present and planned in

the node prior to downloading the new SW package.

1.170 V2.1.8


� ANTmt50138: Include support for V1.50 of the SHUB OFLMT

Problem: PBMT does not support V1.50 of the SHUB offline

migration tool.

Solution: Support for this version has been included.

� ANTmt50176: Removal of checksize.pl

Problem: The checksize.pl script is no longer applicable.

Solution: Script has been removed from the package.

� ANTmt50179: Removal of cleandb.pl

Problem: The cleandb.pl script is to be removed from the

package.

Solution: Script has been removed from the package.

� ANTmt50185: Error when using cleanUp.pl

Problem: The cleanUp.pl fails with an error.

Solution: Included a reference to a missing perl library.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 107/176

1.171 V2.1.7


� ANTmt49436: Download OSWP failed

Problem: A tftp session may be setup to the wrong ISAM in case

the /etc/hosts file contains two nodes with the same name (there

may be differences by using upper or lower case) but different IP

addresses.

Solution: Always use the IP address of the node rather then using

its name.

1.172 V2.1.6


� ANTmt18506: Load distribution of migration script

Problem: Load is not balanced equally when the number of PBMT

script instances is higher then the amount of ISAMs being

handled.

Solution: Load balancing is optimized in this situation by

spreading the load over the various PBMT script instances.

� ANTmt48683: Status check comparison reports warnings

Problem: In case the status check has not been carried out on the

same database the script reports warnings.

Solution: Some extra checks have been included to avoid the

generation of these warnings.

� ANTmt48688: Precheck aborts with SNMP error maxMsgSize

Problem: the per-check script generates and an error and aborts

further processing in case an SNMP message exceeds the

maximum message size set by this instance.

Solution: The maximum message size for an SNMP message has

been extended to the maximum size possible.

� ANTmt48958: SNMP error when migrating ISAM-V from R3.4

to a higher release

Problem: Migration fails due to a failure in establishing an SNMP

session to the xVPS.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 108/176

Solution: Correctly initialize the community string before setting

up an SNMP connection.

1.173 V2.1.5


� ANTmt47355: Support of SHUB OFLMT 1.49

Problem: PBMT does not yet support V1.49 of the SHUB OFLMT.

Solution: Support for this version is included.

1.174 V2.1.4 (skipped)

1.175 V2.1.3


� ANTmt47249: Warning generation running migrate.pl -v

Problem: Running migrate.pl may result in some warnings being

generated depending on how Config.pl has been executed. These

warnings are non-service affecting.

Solution: Modified PBMTConfig.pm to make sure that encrypted

empty strings are stored when needed.

� ANTmt47452: SW minimization results in a syntax error when

downloading OSWP

Problem: A minimized OSWP contained a double ‘;’ character at

the end of the ASAM-CORE line. This resulted in a DL failure due

to a syntaxt error.

Solution: Utils.pm has been adapted to make sure that the

secondary tftp-ip address does not have a trailing ‘;’ character.


� ANTmt47355: chgNwVlan fails on R4.0

Problem: The R4.0 bridge-port configuration has a new command

option that is not supported by the chgNwVlan script: max-

committed-mac.

Solution: This new option is

supported.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 109/176

1.176 V2.1.2


� ANTmt46670: PBMT does not recognize ANSI NE

Problem: The OSWP is not accepted for download on an ANSI

NE.

Solution: Contrary to the originally agreed OSWP/SWP naming

(L6GP/OSWPANxx.yyy) the common naming with the ETSI load

(L6GP/OSWPAAxx.yyy) is still used for the ANSI stream. PBMT was

expecting an ‘AN’ load and as such rejected the AA load for an

ANSI system. PBMT will now accept AA (but not AN) as load

identifier for an ANSI system.

1.177 V2.1.1


� ANTmt44696: Include support for HiCAP NT and NA-stream

Problem: Starting from R3.7.10 and R4.0 resp. new NE families

need to be supported by PBMT: the HiCAP NT and the split ETSI

and ANSI stream for ISAM.

Solution: An NE family concept has been introduced in PBMT.

This allows for plugs supporting specific NE families while keeping

the concept of PBMT tools generic.

� Support of SNMPv2c, SNMPv3, ftp, sftp and SSH

Problem: PBMT did not yet support all or the more reliable means

of communication with the node.

Solution: From V2.1 onwards support is included for these

additional communication means (note the TL1 over SSH is still

pending).

� ANTmt45511: Support of SHUB OFLMT V1.48

Problem: PBMT does not support the latest version of the SHUB

OFLMT.

Solution: Support for version 1.48 of the SHUB OFLMT is

included.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 110/176


� ANTmt45047: SW minimization error

Problem: Download of a minimized SW package resulted in a

failure to startup the node.

Solution: When using the minimizer script with the option to

create a target directory, copying may fail due to disk problems

(e.g. disk full). The process generates an error messages but does

not exit with an error code. This has been corrected.

1.178 V2.1.0 (skipped)

First delivery of V2.1 of the PBMT toolset. Version skipped due to

incomplete delivery

1.179 V2.0.40


� ANTmt37968: ipAware2Ibridge.pl fails

Problem: R3.7.01 no longer accepts deletion of a VRF network

interface if a DHCP agent is associated with (bcast-vlan is different

from 0).

Solution: First reset the BCAST-VLAN of the VRF’s DHCP agent

before removing the network interface (note that the side effect of

this change is that the script will fail on a R3.7.00).

� ANTmt40831: Bridge port lost after migration

Problem: Certain DB corruptions may result in loss of a bridge

port after migration.

Solution: PBMT has implemented a workaround to enable a clean

up action during the offline migration in case certain specific DB

corruptions are detected.

1.180 V2.0.39


� ANTmt37968: ipAware2Ibridge.pl fails

Problem: Starting from R3.7 the CLI command show pppoe

session is no longer supported.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 111/176

Solution: Only call the CLI command till (and including) R3.6.

� ANTmt39575: chgNwVlan.pl fails

Problem: When reconfiguring the network VLAN, VLAN-ports for

which the network VLAN is different from the VLAN being

changed are also reconfigured.

Solution: Only VLAN ports where the network VLAN matches to

the VLAN to be changed are reconfigured.

1.181 V2.0.38


� ANTmt38500: New version of NT offline migration tool

Problem: A new version of the NT offline migration tool has been

delivered in the context of R4.0.

Solution: Included support for NT OFLMT version 15.0.0

1.182 V2.0.37


� ANTmt35283: PBMT makefile should work in empty view

Problem: When running PBMT’s makefile in an empty CC view the

syntax check phase fails due to a missing library file.

Solution: Create the library file in a separate rule executed before

all other rules.

� ANTmt36445: swdl.pl checks octopus session wrongly

Problem: In case a part of an ISAM’s IP address overlaps there is a

risk that PBMT tools incorrectly decide that an octopus session is

active.

Solution: Refine the results when checking whether octopus is

active.

� ANTmt36711, ANTmt37854: MIB version is not correct for

R4.0

Problem: The MIB version of R4.0 is not recognized by PBMT

tools. As such they do not operate on R4.0 ISAMs.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 112/176

Solution: Include support for R4.0 MIB versions.

1.183 V2.0.36


� ANTmt33842: ipAware2Ibridge.pl fails for second VRF

Problem: When converting multiple IP-aware bridges to

Enhanced I-bridges, the reconfiguration failed for the second IP-

aware bridge because one of the VLAN-ports had a network VLAN

different then the VLAN associated with the IP-aware bridge.

Solution: Restrict verification of VLAN ports of a bridge port to

the VLAN port included as user-interface of the VRF (up till now all

VLAN ports were checked, so also these not included in the IP-

aware bridge to be reconfigured).

1.184 V2.0.35


� ANTmt28533, ANTmt30764, ANTmt30762: Login fails when

prompt is too long

Problem: There were still cases where the login succeeded but

later CLI commands resulted in a prompt being cut off.

Solution: After logging in to the ISAM, always reset the

environment prompt to the default value.

1.185 V2.0.34


� ANTmt29255: Implement RCR ANTmt29251

Problem: For security reasons some customers do not allow the

usage of ping to verify whether a node is alive.

Solution: A new command line option (--noping) has been

added. When providing this option, SNMP will be used to verify

whether the node is reachable. This option can also be configured

in the param.cfg file by running Config.pl and answering “Y” to the

prompt “Ping disabled in the network”.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 113/176


� ANTmt28533: Login fails when prompt is too long

Problem: In case the CLI prompt becomes too long there are

conditions where the prompt terminating character is no longer

present. As a result the regular expression looking for the end of

the prompt is failing.

Solution: In case of a login timeout, PBMT scripts will assume the

login was successful and will change the CLI prompt to its default

value using the environment command. If that fails too, login is

not successful.

� ANTmt29410: convertEngine adds wrong ports

Problem: After running the convertEngine script incorrect ports

have been added to the cross-connect engine.

Solution: The check on the VLAN id was not restrictive enough

and included ports having the CC engine’s VLAN ID as a part of

the VLAN ID associated with this port. The VLAN ID check has

been modified to remove these ports from the convertion.

1.186 V2.0.33


� ANTmt16940: Maximum number of MAC addresses per LT

exceeds limit per LT

Problem: R3.3 does not check on the correct maximum number

of MAC addresses possible for an LT. Some boards allow 4096

statuc unicast MAC-addresses for the complete LT. This limit has

to be made uniform for all the LTs and set to 1024.

Solution: The preCheck and migrate script include checks to

verify:

• That the sum of maximum MAC addresses per bridge does

not exceed the maximum value applicable for that LT.

• That the sum of the static unicast MAC addresses linked to

bridge ports of an LT does not exceed the maximum value

applicable for that LT. The upper limit is 1024. Boards that

currently have a setting higher the 1024 are:

o EVLT-C/D/E


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 114/176

o EBLT-G/H

o NVLT-A/B

When the limit is exceeded the operator will have to modify his

configuration in order to allow migration from R3.3 to a higher

release. There is no automatic correction possible.

1.187 V2.0.32


� ANTmt27866: New versions of NT offline migration tool


delivered.

Solution: Included support for NT OFLMT version 14.0.3.

1.188 V2.0.31


� ANTmt27224: Provide support for the latest xVPS offline

migration framework version.

Problem: The latest version of the xVPS offline migration tool

framework is 4.0.0 (for R4.0v).

Solution: Include support for the latest xVPS OFLMT framework

version.

� ANTmt26931: Change to preCheck.pl.

Problem: LRM expects a “pass-code” at the end of the run.

Currently 3 codes are generated:

• Success

• Failure

• Warning

LRM only considers Success and Failure as a pass-code.

Solution: Since the generated warnings are presented to the

operator it has been decided to end the run with a pass-code

(success in this case).

Note: Conditions that would lead to a


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 115/176

migration failure are not reported as warning but as a true failure.

1.189 V2.0.30







version.

1.190 V2.0.29


� ANTmt14347: Can’t run Config.pl twice.

Problem: On an AWS install it is not possible to run Config.pl

twice because the file is created with a read-only permission.

Solution: Make sure that the param.cfg is also writable after the

Config.pl run.

� ANTmt25573: EBLT-Q not coming up after migration.

Problem: When upgrading to R3.7, the EBLT-Q is a new board in

the ISAM. As such downloading the EBLT-Q SW is not happening

as the board is not known in the currently active SW load.

Solution: Using the Minimizer.pl script it is possible to include

certain boards in the minimum-set of a SW download. The SW

download script will determine which files are marked as ‘not-

available’ after a regular download. In case these files belong to

boards included in the minimum-set, the SW DL script will still

transfer these files using tftp.

1.191 V2.0.28


� ANTmt25387: No support for SHUB offline migration tool

1.47


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 116/176

Problem: The latest version of the SHUB offline migration tool is

1.47.

Solution: Include support for the latest SHUB OFLMT version.

� ANTmt24857 (ANTmt24872, ANTmt24874): Migration fails

from R3.3.05 to R3.7

Problem: During the migration process a call to an invalid

procedure is made.

Solution: Corrected the incorrect function call.

1.192 V2.0.27


� ANTmt24391: Provide support for the latest SHUB offline



1.46 (for R4.0).

Solution: Include support for the latest SHUB OFLMT version.

1.193 V2.0.26


� ANTmt23608: New versions of NT offline migration tool


delivered.

Solution: Included support for NT OFLMT version 14.0.2.

� ANTmt23460: Change Network VLAN script fails

Problem: VLAN deletion fails in case the network VLAN to be

modified is used as PVID on a bridge port in the SHUB.

Solution: Included an additional check: the network VLAN may

not be used as PVID for an SHUB bridge port.

1.194 V2.0.25



3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 117/176

� ANTmt17868: New versions of SHUB and NT offline migration

tools

Problem: New versions of SHUB and NT offline migration tools

have been delivered:

• 1.45 for SHUB

• 14.0.1 for NT

Solution: Included support for these new versions.

� ANTmt22054: Error in migrate.pl script

Problem: When migrating an ISAM-V system, the script looks for

an offline stored DB and does as such not try to obtain the xVPS

IP addresses – even if the script was not started with the offline-

stored DB option.

Solution: Correct the check for an offline-stored DB.

� ANTmt22055: Config.pl requested incorrectly

Problem: When launched from AWS/AMS, Config.pl is run with

the default option. AWS/AMS afterwards modifies some values

but the PbmtConfig check verifies the settings to the system

defaults and hence prompts to run Config.pl.

Solution: Only verify for newly added param.cfg options or a

PBMT version change. We no longer compare user-changed

values against system-defaults.

� ANTmt22359: SHUB VLAN config parsing failed.

Problem: R3.7 introduced a new SHUB VLAN parameter option

(user2-comm). This option was not known to the script to change

the network VLAN of an Enhanced I-bridge.

Solution: PBMT now parses the new option.

� ANTmt22633: Migration fails from R3.6 to R3.7 with EBLT-

C/EBLT-K)

Problem: Due to an error in a regular expression PBMT incorrectly

decides that the ISAM is equipped with voice (non-server) boards.

As such it tries to include a CDE file in the migrated database but

no CDE file was specified at the start of the migration.

Solution: Corrected the faulty regular expression.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 118/176

1.195 V2.0.24







version.

� ANTmt17699: Provide additional robustness.

Problem: A customer faced a particular migration issue resulting

in the loss of the socket carrying the CLI/telnet communication to

that ISAM.

Solution: The code has been modified to deal with this situation.

The reason of this socket loss is not explained (the telnet session

was still active on the ISAM – hence it was not closed by the

migration script but got lost due to some other reason.


� ANTmt16940: Maximum number of MAC addresses per LT

exceeds limit per LT

Problem: R3.3 does not check on the correct maximum number

of MAC addresses possible for an LT.

Solution: The preCheck and migrate script include checks to

verify:

• That the sum of maximum MAC addresses per bridge does

not exceed the maximum value applicable for that LT.

• That the sum of the static unicast MAC addresses linked to

bridge ports of an LT does not exceed the maximum value

applicable for that LT.

When the limit is exceeded the operator will have to modify his

configuration in order to allow migration from R3.3 to a higher

release. There is no automatic correction possible.

1.195.3 Improvements

Logging has been adjusted allow better


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 119/176

debugging. Traces to the now contain a reference to the PERL

file/module and the line number from where the logging was

performed.

1.196 V2.0.23


� ANTmt16653: Provide support for the latest NT offline


Problem: The latest version of the NT offline migration tool

framework is 14.0.0 (for R3.7).

Solution: Include support for the latest NT OFLMT framework

version.


� ANTmt17439: Incorrect board type for AGNT-A when

migrating the SHUB database

Problem: The SHUB-related board-type used by PBMT for the

AGNT-A is incorrect.

Solution: The board-type for AGNT-A when migrating the SHUB

database must be ECNTC.

� ANTmt17241: No IGMP XML extraction is required when

migrating from R3.1 or higher

Problem: It is not required to extract the IGMP MCAST

information from the NT into the IGMP XML file as input for SHUB

database migration when migrating from R3.1 or higher.

Solution: Suppress the extraction of the IGMP XML file when

migrating from R3.1 or higher.

1.197 V2.0.22


� ANTmt16192: Provide support for the latest XVPS offline


Problem: The latest version of the XVPS offline migration tool

framework is V2.2.2.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 120/176

Solution: Include support for the latest XVPS OFLMT framework

version.

1.198 V2.0.21


� ANTmt14453: NVPS database lost after migration

Problem: No xVPS migration was being performed even though

there was a voice server present in the ISAM.

Solution: Fixed a regular expression by removing a leading

‘space’ character.

1.199 V2.0.20


� ANTmt14021: Migration fails due to missing cde_profiles

directory

Problem: AMS is not supporting ISAM-V and hence does not

have a location to store CDE files.

Solution: The following CDE file handling has been applied as

from R3.6 onwards:

• In case the ISAM has no voice capable boards the migrated

database backup will contain an empty CDE directory

• The migration will fail in the following cases:

o ISAM has a voice server board but no CDE file could

be found

o ISAM has voice capable boards and no CDE file

could be found (in case when the actual release is

R3.6 or higher

• In case the ISAM has voice capable boards but the actual

release if lower the R3.6 a warning message will be printed

to the migration log file if no CDE file was found but the

migration will continue. It has to be taken into account

that in that case a manual installation and download of a

CDE file is required in order for the board to be usable.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 121/176

� ANTmt13345: CDE file in wrong location

Problem: Starting from R3.6 onwards, the CDE file is no longer in

the DB container of the xVPS but is stored in a directory at the

level of the NT database.

Solution: CDE file is stored in the correct location.

� ANTmt13251: Multi-user issue with the cvtEcntA2C script

Problem: In case multiple users would use the NT type convertion

script, the script will generate errors in case an attempt is made by

the script to remove files from the temporary workspace.

Solution: A two-level directory approach is used to overcome this

problem. The database to be converted will be stored in a sub-

directory where the path includes the name of the unix account of

that user and the name of the database itself to provide for a

directory name as unique as possible.

1.200 V2.0.19


� ANTmt13530: MIGR PBMT NT OFLMT version incorrect.

Problem: The version of the NT OFLMT framework has been

changed.

Solution: Include support for version 13.2.4.

� ANTmt09138: Migrate using PBMT - Nok.

Problem: AWS is not able to correctly execute the Config.pl script.

Solution: The AWS configuration option was corrected and 2

more default options have been added allowing configuration of

CDE file names for ISAM-V migration.

1.201 V2.0.18


� ANTmt13215: Creation of the CDE directory for the migrated

DB fails.

Problem: When migrating from R3.6 to R3.7 creation of the CDE

directory fails because it already exists.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 122/176

Solution: The contents of the CDE directory will be deleted in

case the CDE directory already exists.

� ANTmt09138: SNMP errors when running statusChec.pl.

Problem: The pre- and post status checks generate SNMP errors

in case of an FD in extended LT mode.

Solution: Include a mapping table for CLI LT numbering versus

the numbering used internally allowing a correct calculation of the

interface indexes.

� ANTmt04759: IP-aware bridge to Enhanced I-bridge

conversion results in possible loss of configured IGMP

channels.

Problem: IGMP channels are lost in the conversion process in

case IGMP channels have been configured on top of an IP

interface of an IP-aware bridge.

Solution: When removing an IP interface from an IP-aware

bridge, IGMP channels will be deleted in case one would have

been defined. The conversion script will now re-created in case an

IGMP channel was defined on top of an IP interface.

1.202 V2.0.17


� ANTmt10248: Latest version of NT OFLMT is 13.2.3

Problem: Latest version of the NT offline migration tool is 13.2.3.

Solution: Support for this version has been added.

1.203 V2.0.16


� ANTmt10004: ERAM-A Upgrade not OK with PBMT.

Problem: Downloading the minimized OSWP having the ERAM-A

inside failed. This was due to a too strict syntax check of the SWP

file (it expected an END-statement preceded by at least one space

for board description block).

Solution: The leading space has been removed from the check.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 123/176

1.204 V2.0.15


� ANTmt09937: Implement RCR ANTms78906 (customer

specific reconfiguration script).

Problem: In the scope of R3.7 a dedicated reconfiguration script

(change the network VLAN of an enhanced I-bridge) was

requested by one of our customers.

Solution: This script is included in this version.


� ANTmt09938: Include set and release transaction in

reconfiguration scripts

Problem: A number of reconfiguration scripts have been

developed in the scope of R3.5 and R3.6. These scripts did not

claim a transaction when starting the reconfiguration. As such

they may fail half-way during the reconfiguration while the

rollback would fail for the same reason and the DB - that was

uploaded prior to the start of the reconfiguration - needs to be

restored manually to return to the original situation.

Solution: The actual reconfiguration is enclosed by a claim and

release transaction.

1.205 V2.0.14


� ANTmt09296: Include release streams 346 (R3.4.06) and 347

(R3.4.07) in PBMT’s capability model.

Problem: R3.4 has defined 2 new CDE EF release streams:

• R3.4.06 for CDE EF releases based on R3.4.00/R3.4.01

• R3.4.07 for CDE EF releases based on R3.4.02 or higher

Due to 2 different database versions existing in the R3.4 stream,

all maintenance releases must be defined in PBMT’s capability

model.

Solution: PBMT now supports CDE EF release streams 3.4.06 and

3.4.07.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 124/176


� ANTmt09138: statusCheck.pl generates SNMP errors.

Problem: When the CLI user’s profile is in type-based slot

numbering, LTs start to number from 1 as opposed to 4 for the 2

other modes (position-based or legacy-based). The LT number is

used to generate ifIndex for SNMP MIB access.

Solution: In case of type-based slot-numbering, 3 will be added

to the LT number prior to ifIndex calculation.


1.207 V2.0.12


� ANTmt08500: CDE file not included in database of SUB node.

Problem: From R3.6 onwards all NT databases should contain a

CDE directory and CDE package. This was not very clear from the

specs and hence PBMT only included this for ISAMs having xVPS

boards configured.

Solution: PBMT now includes the CDE package in all migrated

databases for release 3.6 and higher.

1.208 V2.0.11


� ANTmt08354: Include release stream 338 (R3.3.06) in PBMT’s

capability model.

Problem: R3.3 has defined a new maintenance release (R3.3.06,

build number 33.8xx). Due to 2 different database versions

existing in the R3.3 stream, all maintenance releases must be

defined in PBMT’s capability model.

Solution: PBMT now supports R3.3.06 (build number 33.8xx).



3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 125/176

� ANTmt08912: Do not use CDE.tar as filename for the CDE tar

package.

Problem: Starting from R3.6V, the CDE file is stored in a different

directory. Currently the file was stored as CDE.tar but the real

name should be used rather then this overall name.

Solution: PBMT will now include the correct name for the CDE

package (either as defined when configuring the PBMT

environment or as determined from an NT backup).

� ANTmt08304: Make sure Config.pl correctly handles

commented-out parameters.

Problem: Although commenting out variables in param.cfg

should not be done, the new param.cfg contains empty variables

for these that have been commented-out.

Solution: Make sure commented-out variables get their system-

default value assigned.

1.209 V2.0.10


� ANTmt08360: Name of XVPS offline migration tool has

changed.

Problem: Starting from R3.6, the XVPS offline migration tool has a

different name (NBTWAAnn.exe).

Solution: PBMT now supports the new name of the XVPS offline

migration tool.


� ANTmt06468: XVPS CDE directory still present after

migration.

Problem: When migrating to R3.6V, the voice CDE file has moved

from the XVPS DB container to a directory at NT level. The CDE

directory in the XVPS DB container should be removed. This did

not happen under certain specific conditions.

Solution: PBMT will remove the CDE directory from the XVPS DB

container in all circumstances when migrating to R3.6V.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 126/176

1.210 V2.0.9 (skipped)

1.211 V2.0.8


� ANTmt05084: IVPS offline migration failures.

Problem: Due to possible remainders of previous (possible failed)

migrations for the same node it may happen that migration of the

same node (but with voice controller boards inserted in other

locations) may fail.

Solution: Remove all DB containers related to voice controller

boards before attempting a new migration for this ISAM-V.

� ANTmt05521: Provide support for the latest XVPS offline


Problem: The latest version of the XVPS offline migration tool

framework is V2.2.1.

Solution: Include support for the latest XVPS OFLMT framework

version.

� ANTmt05829: End with an error message in case an SWP file

is passed as parameter rather then an OSWP file.

Problem: In case an SWP file is passed as parameter to the PBMT

scripts rather then the OSWP file, the tools should exit gracefully

with an error message.

Solution: Move the check on the whether the file is an SWP or

OSWP directly after the file parsing.

1.212 V2.0.7


� ANTmt05023: ECNT-A to ECNT-C conversion script should

also handle gzipped ISAM backup files

Problem: AMS stores the ISAM periodic backups in a gzipped

format starting from AMS 6.3.0 SP1 P3. The script converting an

ECNT-A database into an ECNT-C database can’t handle these

files.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 127/176

Solution: The conversion script will first unzip the compressed file

before converting the database. The resulting database will NOT

be compressed (as uncompressing is required for download to the

ISAM anyway).

� ANTmt04599: Problem with release build number 999 and

998

Problem: SW download fails in case of a SW download of a 999

(or 998) release build number on a NANT-A system.

Solution: When downloading a release build with extension 999

(and 998), the script assumes that we are dealing with an OSWP

that has been online reduced using the first version of the on-line

SW reduction script. As such it looks for the real build number by

searching for the operational SW file name. For NANT-A this file

name has changed between R3.2 and R3.3 but the PBMT tools

were still using the pre-R3.3 file name. As a result the true

release number can’t be determined. The tooling has been

adjusted so that it can live with changing file names for the

operational NT board software.


� ANTmt04759: IP-aware bridge to Enhanced I-bridge

conversion results in possible loss of configured IGMP

channels.

Problem: IGMP channels are lost in the conversion process in

case IGMP channels have been configured on top of an IP

interface of an IP-aware bridge.

Solution: When removing an IP interface from an IP-aware

bridge, IGMP channels will be deleted in case one would have

been defined. The conversion script will now re-created in case an

IGMP channel was defined on top of an IP interface.

1.213 V2.0.6 (skipped)

1.214 V2.0.5


� ANTmt04156: Latest version of IVPS OFLMT is 2.2.0

Problem: Latest version of the

IVPS offline migration tool is 2.2.0


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 128/176


1.215 V2.0.4




Solution: Support for this version has been added. Also version

1.44 of the SHUB offline migration tool is supported.

� ANTms87260: Allow vlan-port and non-ATM bridges in the

convertion from IP-aware bridge to Enhanced I-bridge

Problem: The original scope of this script was R3.4 (after a

migration from R2.4) and was only required to support

bridges/PVCs on top of ATM lines. The scope needs to be

extended to R3.5 allowing support of VLAN-ports and non-ADSL

bridge ports as user interfaces of a VRF.

Solution: Scope of script is extended to R3.5.

� ANTmt02100: Migration from 24.936 to 33.517 fails

Problem: In the workaround introduced for the failing OSWP

activation it was still possible for the workaround to report an

incorrect result (migration failed but the node runs the new SW

version).

Solution: The problem occurred in case workaround determined

that the old release was still running after the SW activation and

hence the “rescue path” needed to be kicked in. Obtaining the

SHUB SW version when proceeding along this rescue path

returned no result because the NT had performed a reset in the

mean time. This condition is now covered.

1.216 V2.03






3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 129/176

� ANTmt02497: the upgrade script resets node when not

needed

Problem: In case an upgrade is attempted between the online

reduced and original OSWP, the upgrade script will reset the node

although this should not be done (side effect of ANTms55912)

Solution: The restart workaround will not be triggered in case the

new and previous release are the same.

1.217 V2.0.2 (skipped)

1.218 V2.0.1


� ANTms87671: Latest version of NT OFLMT is 13.1.0



1.219 V2.0.0


� ANTms88418: Deliver PBMT with non-FDT label

Problem: Allow PBMT deliveries as an non-FDT label.

Solution: This is a pure source-control administrative action.

From a functional point of view the content is exactly the same as

V1.7.18. We had to use a new baseline release number for this

change.

1.220 V1.7.18


� ANTms88054: Migration to R3.4.03 not OK

Problem: Maintenance release R3.4.03 is not known to PBMT’s

capability model. As such migration is defaulted to R3.4 which is

by default disabled.

Solution: Support for this release

has been added.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 130/176

1.221 V1.7.17


� ANTms87671: Latest version of SHUB OFLMT is 1.43

Problem: Latest version of the SHUB offline migration tool is 1.43.


� ANTms86893: ISAM migration tool exits with IP not valid

Problem: In case the SW upgrade or migration tool is called with

the --haip option the tool exits with an error message that the

IP address is not valid.

Solution: An error in the regular expression used to parse the IP

address has been corrected.

� ANTms87133: Software download script hangs in case of a

permanent failure (TEC-03994)

Problem: The SW download script waits till the SW download is

finished. In case of a link failure it will wait for the link failure to

be restored.

Solution: While waiting for the download to complete the script

will detect a timeout on the CLI command and will perform 4

retries. If not successful after the 5th command transmission the

SW download script will end all operations for this ISAM.

� ANTms87729: PPP CC with MAC address concentration

reconfiguration script does not cover all possible

combinations

Problem: The script to reconfigure a PPP cross-connect engine to

use MAC address concentration did not cover all possible

configuration possibilities.

Solution: All possible configuration possibilities are covered.

1.222 V1.7.16


� ANTms83783: Migration from R2.4.11g to R3.3.04 fails

Problem: On very specific setups of ARAM-D with expansion

shelves, an OSWP activation get accompanied by an NT reset. In

certain conditions this results in the script


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 131/176

returning a migration failed result while, due to guard timers

running in the node, it may happen that the NT is running the new

SW load. Sometimes the SHUB is not running the new SW load

while the NT is.

Solution: A specific workaround has been introduced to deal with

the fact that the NT experiences an unrecoverable error at the

time of OSWP activation. This is done using the low-level

debugging interface of the NT. The end result is that both the NT

and the SHUB will be running the new SW load in case of a

successful SW activation.

Specific notes about this workaround:

• Uses the NT T&D capabilities using the octopus

application. This requires access on all UDP ports and may

have implications to the network in case firewalls are being

used.

• The workaround is disabled by default and can be activated

in two ways :

o On the command line when running migrate.pl line

by using the --remap option.

o Using Config.pl. A new configuration parameter has

been defined and will be prompted for when

running the configuration utility :

>>>> Enable HOT RESET remapping (i.e. disable NT hot reset) prior to OSWP activation (requires

octopus T&D access)

Enable HOT RESET remapping (i.e. prevent NT hot reset) [N] :

A second option may be enable but is only usefull in case

the new SW load was not started up during the first

activation run but the restarting SW was always the old

load. A second run may be requested. Please note that

this option will have no effect on the migration result in

case the new SW load failed to finish the startup and rolled

back to the previous SW load. This option can only be

activated through the configuration utility :


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 132/176

>>>> Execute a second OSWP activation run in case migration failed after the first run

Enable second OSWP activation of the new software in case of failure the first time [N] :

1.223 V1.7.15


� ANTms85750: Allow ‘:’ in SWP name.

Problem: SW paths on High-Available systems may include a ‘:’ in

the name. PBMT currently does not allow the ‘:’ in the SWP name.

Solution: Allow ‘:’ in SWP name.

1.224 V1.7.14


� ANTms85515: Allow configuration of max MAC addresses

that can be learned on a bridge.

Problem: When converting an auto-detect:PPP PVC to

autodetect:PPP/IpoE multiple MAC addresses can be learned on

the bridge. The default setting is 1.

Solution: Allow configuration of the amount of MAC addresses

that can be learned on the bridge. The amount is specified as a

command line option of the ppp2pppipoe.pl script as –maxmac

<n> where n = 1…64.

1.225 V1.7.13


� ANTms85481: IP-aware bridge recovertion of Enhanced I-

brdige fails when certain options are enabled.

Problem: When retesting the reconfiguration script using R3.5 the

reconfiguration failed when certain options in the VLAN

reconfiguration have been set due to an incorrect CLI command

syntax.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 133/176

Solution: CLI command syntax has been corrected.

1.226 V1.7.12


� ANTms84960: Latest SHUB OFLMT version is 1.42


1.42. PBMT supports till version 1.39

Solution: PBMT supports till SHUIB OFLMT 1.42.

1.227 V1.7.11


� ANTms84727: PBMT migrate.pl ignores offline migration

failure.

Problem: The PBMT migrate.pl script ignores a possible offline DB

migration error and continues to execute. The remainder of the

script fails because the CLI session has been closed but the script

hangs for a long time.

Solution: Abort the process in case of offline migration failures.

1.228 V1.7.10


� ANTms45206: NANT-A to NANT-B reconfiguration

Problem: For R3.5 NANT-A to NANT-B DB conversion is required.

This is only required for the NT DB.

Solution: PBMT does not convert the SHUB database.

1.229 V1.7.9


� ANTms83707: Implement reconfiguration scripts

Problem: In the scope of R3.5 three reconfiguration scripts are

required:


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 134/176

• ANTms41225 to convert an IP-aware bridge to an

enhanced I-bridge. This reconfiguration is dealt with by

ipAware2Ibridge.pl.

• ANTms41059 to convert a PPPoX relay CC engine to use

MAC-address concentration. This reconfiguration is dealt

with by ppp2pppipoe.pl.

• ANTms80330 to convert auto-detect PPP PVCs to auto-

detect PPP-IPOE PVCs. This reconfiguration is dealt with by

convertEngine.pl.

Solution: The reconfiguration scripts are integral part of the

PBMT toolset.

1.230 V1.7.8


� ANTms82853: NT Offline migration tool version changed

Problem: The versions of the latest NT offline migration tools has

changed to 12.1.6

Solution: The PBMT supports the latest versions of the offline

migration tools.

1.231 V1.7.7


� ANTms80082: Offline migration for R3.6V

Problem: The migration scenario for migration to R3.6V is slightly

different from the migration to R3.5V

Solution: The PBMT supports migration for ISAM-V to R3.6.

� ANTms63550: Offline migration for R3.6

Problem: When migrating to R3.6 (or upgrading in R3.6) a new

variable needs to be introduced.

Solution: The PBMT supports migration for ISAM to R3.6.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 135/176

1.232 V1.7.6


� ANTms82688: xVPS Offline migration tool version changed

Problem: The versions of the latest xVPS offline migration tools

has changed to 1.2.1


migration tools.

1.233 V1.7.5


� ANTms81903: PBMT fails for FD in extended-LT mode

Problem: The PBMT scripts fail to operate on FD equipment

configured in extended-LT mode. Determining the NT type fails.

Solution: FD equipment configured in extended-LT mode does

not have an entry for the second NT in the equipment MIB. The

PBMT scripts retrieve the NT type for both NT locations at once,

which failed. It now retrieves the NT types in 2 separate requests.

1.234 V1.7.4


� ANTms81426: NT Offline migration tool version changed

Problem: The versions of the latest NT offline migration tools has

changed to 12.1.5


migration tools.

� Support of Release Stream 335 (R3.3.05) and 337 (CDE for

R3.3.*)

Solution: New release streams have been added to the Capability

model of PBMT to support these future release numbers.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 136/176

1.235 V1.7.3


� ANTms80071: Default NT community string is used by the

migration script

Problem: The migration script is using the default NT community

string rather then the one provided in the parameter

configuration file. Customers using a non-default value will

observe a failing migration.

Solution: Use the value as stored in the parameter configuration

file when opening an SNMP session to the ISAM.

1.236 V1.7.2


� ANTms78942: NT HOT reset during migration from R2.4.11g

Problem: When migrating from R2.4.11g to a higher release the

NT may perform a hot reset during the SW activation. As a result

of this PBMT will report a failed migration. However due to this

NT reset during OSWP activation, the system will timeout and

perform a restart upon this timeout. This time the system will

restart with the new release.

Solution: PBMT has been provided with a workaround for this

system problem. In case the system is still running the old release

after SW activation and the node is in this special condition, PBMT

will perform a second node restart in order to provoke a restart

with the correct SW. After this, when successful, PBMT will report

a successful migration.

1.237 V1.7.1


� ANTms78847: Offline migration tool versions changed

Problem: The versions of the latest NT and SHUB offline

migration tools have changed:

• NT: 12.1.4


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 137/176

• SHUB: 1.39


migration tools.

1.238 V1.7.0


� ANTms58800: Introduction of ISAM-V offline migration

Problem: Starting from R3.5V the voice database will also be

migrated in a way similar as the NT and SHUB. The migrated R3.5

DB will include the complete database set.

Solution: The PBMT migration script now also uploads, migrates

and includes the migrated voice database(s) in the complete

migrated DB.

1.239 V1.6.1


� ANTms77027: IGMP MCAST SRC package member check fails

Problem: Starting from NT OFLMT R3.4.01 a maximum of 64

package members in a multicast SRC are converted into a

maximum of 1024 on the condition that the highest package

member is 64. This is because “ALL packages” have been changed

from 64 to 1024 in R2.4 but the migration to R2.4 has not

changed this. This is corrected when migrating to R3.4 where the

maximum number of packages has been reduced to 20 (or 1024

to indicate “all packages”).

Solution: Allow 64 member packages as a maximum on the

condition that the highest package member is 64.

1.240 V1.6.0


� ANTms74803: Support for migration in R3.3 and R3.4 streams

Problem: Due to an internal linearization error the relationship

between the VLAN-port and its associated customer ID gets lost

after an NT reset. The persistent DB had to


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 138/176

be modified to make this relation reset-safe. This can only be

done via a migration.

Solution: Migration is required to upgrade the ISAM SW from

R3.3.0x to R3.3.04 and from R3.4.0x to R3.4.02.

� ANTms76707: PBMT reports “Unix success” even in case of

failure.

Problem: The PBMT upgrade script reports a Unix success code

upon termination, even in case of a failure.

Solution: The correct exit code is reported by the upgrade script:

success when successful, an error code in case of unsuccessful

upgrade.

1.241 V1.5.27


� ANTms60696: PBMT V1.5.26 does not support latest SHUB

OFLMT version


1.38 while PBMT only supports up to 1.36.

Solution: This version supports SHUB offline migration tools up to

1.38.

1.242 V1.5.26


� ANTms60696: SWDL hot reset R2.4 to R3.4

Problem: In case the SWP file is containing the MS-DOS end-of-

line character sequence (LF/CR) the reduction script incorrectly

reduces the SWP file. SWP files normally follow the UNIX

standard (LF only) but if SW packages have been unzipped on a

PC using WinZip and the file was downloaded from the PC, the

OSWP and the SWP files contain the MS-DOS EOL (end-of-line)

sequence as opposed to the UNIX EOL sequence

Solution: The complete EOL sequence is now removed from the

input read even if it includes the CR character.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 139/176

1.243 V1.5.25


� ANTms45206: NANT-A to NANT-B correction

Problem: The parameter configuration file generated for th SHUB

OFLMT contained an error with respect to the required

parameters.

Solution: The SHUB migration parameter file is now containing

the expected parameters.

� ANTms69045: Config.pl expects a fixed directory for

‘param.cfg’

Problem:

1. The parameter configuration file for PBMT is stored in the

directory where PBMT has been installed. Rather then

looking in ‘.’ It should look in the installation directory in

case the scripts are launched from another directory.

2. The check in counting the packages in a multicast source

did not take into account that an empty table in fact is

returned as an error when using the SNMP module.

Solution:

1. Use the path information contained in the name when the

script is executed rather then using ‘.’.

2. Do not treat “does not exist” as an error.

1.244 V1.5.24


� ANTms68358: NANT-B board code

Problem: The board code used to identify NANT-B was correct

after all.

Solution: The board code as originally used to identify a NANT-B

has been restored.

� ANTms67685: NT OFLMT version now 12.1.3


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 140/176

Problem: The framework version of the NT offline migration tool

has stepped up to 12.1.3.

Solution: This version is now recognized by the PBMT tools.


� ANTms68417: Check the number of packages in a multicast

source

Problem: From R3.4 onwards only 20 packages (or all, i.e. 1024)

are allowed in a multicast source. This is not checked and rejected

by the NT offline migration tool in R3.4.

Solution: A new migration pre-check has been added to the pre-

check script allowing an operator to detect and correct this. The

migration script also checks this condition.

� Provide a command-line option to allow setting of the

encrypted parameters

Problem: The automatic test tool ATX configures the parameter

configuration file of PBMT during the test run and it needs to this

is in a non-interactive way.

Solution: A new command line option has been made available

allowing specification of the parameters that need to be

encrypted. Using this option exposes the secret information as

the values to be entered are the original ones.

1.245 V1.5.23


� ANTms66037: cvtNantA2B.pl not successful

Problem: The board code used to identify NANT-B was not

correct.

Solution: NANT-A to NANT-B board conversion is now done

using the correct board code.

1.246 V1.5.22



3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 141/176

� ANTms65020: SHUB does not reboot

Problem: When restarting a R3.4 system with default database

after having downloaded a DB migrated to R3.4 the SHUB does

not reboot. This is due to the fact that the migrated SHUB

database erroneously includes the protected database of the old

release.

Solution: Remove the SHUB protected database from the

migrated database.

� ANTms66036: NT OFLMT version number not supported

Problem: The framework version of the NT OFLMT has changed

to 12.1.2. This version is not yet known to PBMT.

Solution: Framework 12.1.2 is supported.

� ANTms66037: cvtNantA2B.pl not successful

Problem: In case the database-to-be-converted has been stored

in PBMT’s temporary workspace converting the DB fails with error

‘copy failed: file identical’.

Solution: The conversion script will return a meaningful error

message indicating that the database can’t be put in PBMT’s

temporary workspace (PBMT copies the source DB itself for

backup purposes.

1.247 V1.5.21


� ANTms65540: Sometimes missing prompting during Config.pl

run

Problem: When running the PBMT configuration script multiple

times it may happen that not all expected parameters are

prompted for a value.

Solution: The encrypted parameters may contain the ‘=’

character. This disrupted the parameter parsing resulting in a

parameter name not found in the list to be prompted for. This

has been corrected.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 142/176

1.248 V1.5.20 (skipped)

1.249 V1.5.19

!!! IMPORTANT !!!

From this version onwards passwords,

usernames and SNMP community string

are expected to be encoded using the

included Config.pl script. So please run

this script BEFORE using any other PBMT

script (or they will abort with an error)


� ANTms64938: Remove CLI username and password from

logfiles

Problem: Currently CLI username and password are shown in the

logfiles for reason of debugging. In order to avoid issues with

security it has been decided to remove these from the logging

and to encrypt the default values in the parameter configuration

file.

Solution: PBMT scripts have been adjusted:

• No logging of user name and password. Only in case when

using the debug option one can still see the CLI username.

• The IP address can still be read when the debug option is

used.

• Light encryption is used to store the default values for CLI

user name, password and NT SNMP community string in

the parameter.cfg file. This requires running the

configuration utility in order to correctly set these values.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 143/176

1.250 V1.5.18 (skipped)

1.251 V1.5.17


� ANTms62648: Restart workaround not OK for redundant

systems

Problem: The low-level information used to trigger the restart

workaround in case an OSWP activation does not result in a

system restart behaves different on redundant systems.

Solution: The workaround has been modified in such a way that is

works for both simplex and redundant systems.

1.252 V1.5.16


� ANTms62454: PBMT: v1.5.15 exit with code 1 (failing

migration while migration is OK).

Problem: In certain cases the time to determine whether the NT

has performed a reset after OSWP activation is long enough to

allow SNMP to be available again on the new release. The

subsequent CLI command fails however due to the TELNET

session having closed due to the restart.

Solution: The time to determine that the node has performed a

restart has been shortened by reducing the SNMP

retransmissions. We also verify whether the TELNET session has

been closed.

� ANTms62398: Remove event messages from CLI output

Problem: Starting from R3.4 the system also generates event

messages. The date and time format is however different from

the alarm message date and time and were missed in the CLI

output parsing.

Solution: CLI command result parsing has been adapted to also

remove CLI event messages.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 144/176

1.253 V1.5.15


� ANTms55912: NT doesn’t reset after OSWP activation

Problem: The workaround used to reset the ASAM doesn’t

produce the expected result.

Solution: The workaround now consists of individual commands

to reset both the SHUB and NT.

1.254 V1.5.14


� ANTms54982: Upload of NT database results in CLI command

timeout

Problem: When migrating a system the CLI command to upload

the NT database times out under certain circumstances. The

release on which this is seen is R2.3.03 or higher.

Solution: From R2.3 a request to upload the NT database

implicitly results in an internal request to save the SHUB DB. The

migration script will no longer issue the CLI command to save the

SHUB database in these cases.

� ANTms60869: SNMP access uses fixed community string for

the NT

Problem: In case a customer is using another SNMP community

string for the NT, SNMP access by the PBMT tools is failing.

Solution: The NT SNMP community string has been made

configurable via either:

• A setting in the param.cfg file (NT_COMMUNITY variable)

or

• --comm command option for the individual scripts

� ANTms55912: NT doesn’t reset after OSWP activation

Problem: Under certain circumstances The NT is not performing a

system restart when the OSWP activation command is given.

Solution: The PBMT migration and SW upgrade script will verify

whether the NT is still running the “old” SW after the OSWP

activation command and will


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 145/176

provoke a system restart if this is the case.

� ANTms60501: Transaction information can’t be retrieved on

R3.4

Problem: Release 3.4 changed the output of the “info

configure system transaction” in a way that PBMT tools

can no longer obtain the transaction time-out value as set in the

ISAM.

Solution: The CLI command has been modified in such a way that

the R3.4 output is also obtained.

1.255 V1.5.13


� ANTms58361: Suppress Error message Stray Handler 18

Problem: When running the tool using debug mode error

messages are sent to the console (Stray Handler 18).

Solution: Both standard out and standard error streams will be

redirected to the null-device when running the NT offline

migration tool in debug mode.

� ANTms60348: NT OFLMT version will become 11.2.4

Problem: The highest NT OFLMT version supported is currently

11.2.2, it will become 11.2.4.

Solution: Include support till version 11.2.4 of the NT offline

migration tool.

1.256 V1.5.12


� ANTms59351: SHUB OFLMT version 1.36 expects a new

command parameter

Problem: The SHUB OFLMT version 1.36 expects a new parameter

in the command file (InterfaceBase) which was not yet supported

by PBMT.

Solution: The new parameter is added to the parameter file when

using version 1.36 of the SHUB OFLMT.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 146/176


� End upload/download in case of empty CLI upload response

Problem: When uploading a DB or downloading SW of a DB it

could happen (due to an internal ISAM error) that empty show

upload responses are returned. PBMT tools wait forever in this

situation,

Solution: Robustness has been added such that the upload or

download ends in case an empty response would be received.

1.257 V1.5.11


� ANTms57361: LRM expects ISAM IP address in NE output

directory

Problem: The NE output directory includes a variable part: the NE

identity. Depending on whether IP-to-name translation is

possible this NE identity is either the NE name or the NE’s IP

address. LRM expects the IP address.

Solution: A new option has been added (--noname) forcing the

NE’s IP address to be included in the NE output directory name.

� ANTms58736: Support for the latest version of offline

migration tool.

Problem: The latest versions of the NT offline migration tools is

11.2.1.

Solution: Latest NT offline migration tool version has been set to

11.2.1.

1.258 V1.5.10


Incorrect delivery of module ReduceSWP.pm. Correct module has

been included.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 147/176

1.259 V1.5.9


� ANTms45205: NCNC-C to NCNC-E conversion

Problem: The NTIO conversion script contains an incorrect array

initialization leading to a PERL undefined variable warning.

Solution: Array is correctly initialized.

� ANTms55014: Support for the latest version of offline

migration tools.

Problem: The latest versions of the offline migration tools are:

• NT: 11.2.0

• SHUB: 1.36

Solution: Support for these has been added.

� ANTms55243: Empty database in case of migrating an offline

stored database.

Problem: A logical flaw when using the --ofldb option resulted in

an attempt to migrate an empty database.

Solution: Logical flaw has been corrected.

� ANTms56107: VSEM down after migration R2.4 to R3.4

Problem: SFP reconfiguration was only attempted in the following

cases:

• From R2.4 to R3.3

• From R2.5 to R3.3

Solution: SFP reconfiguration is required when migrating from

R2.4/R2.5 to R3.3 or higher.

1.260 V1.5.8


� ANTms51632: PBMT needs root user to run

Problem: The correction introduced for the multi-user option did

not function properly in all circumstanced. The directories are

created as “rwxrwxrwx” but due the umask setting some access

rights got masked out leading to failure


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 148/176

in creating directories in other runs

Solution: Set the umask to 0 when the process starts.

1.261 V1.5.7 (skipped)

Skipped: incorrect delivery.

1.262 V1.5.6



Problem: An incorrect check was carried out resulting in an

incorrect SW path leading to a failing SW DL.

Solution: SW check has been corrected.

1.263 V1.5.5


� ANTms52362: Node status result files sometimes empty

Problem: In some specific cases the node status result file was left

empty after advancing to the next ISAM in the list of nodes to be

processed. This caused the LRM application to timeout.

Solution: Node status result file contains an termination result in

all cases.

� ANTms52361: Error in exitcode.pl

Problem: The ATX tool uses exitcode.pl to determine the result of

an operation. The script contained a call to ErrorCodes::xitString

in stead of ErrorCodes::ExitString.

Solution: This has been correct in this release.


� ANTms52356: Claiming transaction fails for HA systems

Problem: In case the AWS is configure as a High-Availability

system, multiple IP addresses are assigned to an interface. The

physical IP address is needed in case of an SNMP set transaction.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 149/176

Solution: An additional parameter has been added to param.cfg

in case the system is a HA system. It needs to be initialized with

the correct IP address. This one will be used for setting the

transaction.

1.264 V1.5.4


� ANTms51245: Fix flaw in transaction owner release

Problem: When trying to release a transaction owner, SNMP may

return a generic error.

Solution: Perform a number of retries before giving up on a

generic error failure (maybe a temporary failure).



Problem: This Fault Report mentions 2 problems:

• PBMT scripts need root access. This is due to the fact that

the tftp top directory is owned by root on an AWS.

Creating a sub-directory owned by root but accessible by

all users prevents the need from running PBMT scripts as

root user.

• PBMT does not allow different users to operate on the

same ISAM (at different moments in time).

Solution: in order to allow creation of log files owned by different

unix users, a new option has been added to the PBMT scripts

(where applicable): --multi. When used, a sub-directory with the

name of the unix user will be created in the temporary working

directory for that ISAM. All logging and operation-related files

will be created in this sub-directory.

� ANTms51884: Add robustness for slow SNMP response

Problem: In case SNMP access to an ISAM is slow, PBMT scripts in

some occasions give up prematurely where retrying could have

resulted in a successful completion.

Solution: Perform a number of retries before finally giving.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 150/176

1.265 V1.5.3


� ANTms51080: CREATE_STAT_FILE_FAILED bad error message

Problem: In case creation of the node status result file fails the

tools exits with an undefined error code.

Solution: The undefined error code has been corrected

(CREATE_STAT_FILE_FAIL)

� ANTms50447: SHUB Conf loss alarm after upgrade

Problem: In case of a redundant system, the new OSWP is

activated too soon: the SHUB database save operation triggered

during the upgrade has not ended.

Solution: Similar to migration for redundant systems, the script

will wait a predefined time before activating the new software

package.

1.266 V1.5.2


� ANTms50664: NT OFLMT version now 11.1.1

Problem: The latest version of the NT offline migration tool is

now 11.1.1.


� Makefile command option PBMTLABEL changed to BLDNUM

1.267 V1.5.1


� ANTms49877: NT reset during online SW reduction

Problem: On some NT boards the NT resets due a timing issue.

Solution: A small delay has been introduced between tftp and

SNMP set operations. This overcomes the NT reset.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 151/176

1.268 V1.5.0


� ANTms49911: Minor bug in Ctrl-C handling

Problem: When a PBMT script is interrupted using Ctrl-C, logic

has been implemented to also kill the child processes. This logic

did not take the child processes that already exited into account.

Solution: Child process already exited will not be killed during the

Ctrl-C processing.


� ANTms45205: NCNC-C to NCNC-E conversion

Problem: R3.4 introduces NTIO NCNC-E (14 sfp). A

reconfiguration has been requested for systems having NTIO

NCNC-C (12 sfp) configured.

Solution: PBMT now includes a script to convert NCNC-C to

NCNC-E.

� ANTms45206: NANT-A to NANT-B-E conversion

Problem: R3.5 introduces NT NANT-B. It conversion has been

requesting allowing replacement of NANT-A by NANT-B

Solution: PBMT now includes a script to convert NANT-A to

NANT-B.

� ANTms14535, ANTms49842: Migration status check

comparison

Problem: PBMT includes a tool to generate a status overview of

(parts of) the ISAM before and after an upgrade or migration. A

tool was needed to compare both results and generate a

migration result (OK, warning or error).

Solution: PBMT now includes a script to compare the status

before and after migration/upgrade.

� ANTms49896: Enable forwarding of TTL=0 packets for R3.5

Problem: After migration of the SHUB database forwarding ot

TTL=0 packets is required.

Solution: PBMT now enables forwarding of TTL=0 packets after

migration.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 152/176

1.269 V1.4.71


� ANTms49515: NT OFLMT version is now 11.1.0

Problem: The latest version of the NT offline migration tool is

now 11.1.0.


1.270 V1.4.70


� ANTms49521: MinimizeSWP.pl corrupts SWP file

Problem: Leaving out blank lines in the board definition section

unintentionally affected copying of the SWP header section

corrupting the resulting SWP.

Solution: Skip blank lines in the board definition section of the

SWP file only.

1.271 V1.4.69


� ANTms49179: MinimizeSWP.pl sometimes generates PERL

warning messages

Problem: The SWP parsing is rather strict in reading in the SWP

files. In case a blank line is present in the board definition section

it will be processed anyway since no blank lines are expected.

Solution: Skip blank lines in the board definition section of the

SWP file.

1.272 V1.4.68


� ANTms48813: Remove leading ‘/’ in tftp related CLI

commands


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 153/176

Problem: Due to differenced in tftp-deamon behaviour, some

ignore a leading ‘/’, while other use the leading ‘/’. The first

behaviour will look for the file relative to the tftp-root directory

while the second behaviour looks for the file following the

absolute path.

Solution: By removing the leading ‘/’ files will always be retrieved

relative to the tftp-root directory.

� ANTms48845: Check result of ‘chmod’ command

Problem: In case chmod would fail, the resulting database upload

will fail with an error message while the link to the file ownership

can’t be easily made.

Solution: The result of chmod is checked and an appropriate

error message is returned in case it fails (the script will also end).

1.273 V1.4.67


� ANTms45130: Mainstream is associated with R3.4

Problem: Due to the branching of R3.3, R3.4 has now become the

mainstream.

Solution: Fix in 1.4.62 was incomplete.

1.274 V1.4.66


� ANTms47155: SHUB offline migration tool version 1.34

Problem: Latest version for R3.4 of the SHUB offline migration

tool is 1.34


1.275 V1.4.65


� ANTms46024: SFP reconfiguration only needed for migrations

of R2.4 or R2.5 to R3.3


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 154/176

Problem: SFPs only need to be reconfigured for migrations of

R2.4/R2.5 to R3.3 and not when migrating from R3.1/R3.2 to R3.3

Solution: PBMT only reconfigures SFPs when migrating from R2.4

or R2.5 to R3.3



tool is 1.33


1.276 V1.4.64


� ANTms45965: Automate status check comparison

Problem: The node status check script creates a CSV file which is

made available for checks executed prior to and after an

operation. No automated comparison was available till now.

Solution: The status check files can now be compared by a

comparison script using configurable thresholds when generating

warnings:

• LTs out of service: default 0% difference

• Lines out of service: default 5% difference

• Alarms: no threshold (any new alarm is a reason for a

warning).

1.277 V1.4.63


� ANTms45601: Incorrect SFP re-assignment when migrating to

R3.3

Problem: When migrating from R2.4 and R2.5 to R3.3, PBMT is

responsible for re-configuring SFPs. R2.5 and R2.4 use type based

slot numbering which is a configurable feature from R3.1 onwards.

� Solution: The default R3.3 slot numbering is legacy based.

Therefore the slot number must be incremented by 3 when

configuring SFPs after migration.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 155/176

1.278 V1.4.62


� ANTms45130: Mainstream is associated with R3.4

Problem: Due to the branching of R3.3, R3.4 has now become the

mainstream.

� Solution: PBMT’s capability model has been updated and now

associates the mainstream development release with R3.4

1.279 V1.4.61


� ANTms44768: NT offline migration tool version 10.1.2

Problem: Latest version for R3.3 of the NT offline migration tool is

10.1.2.

� Solution: Support for this version has been included. Usage for

mainstream testing has been relaxed (no checks on offline

migration tool versions).

1.280 V1.4.60


� ANTms44318: No result written to commit status result file

Problem: The SW commit script creates an empty file in case the

SW commit was successful.

Solution: A success code is written to the status result, in line with

the other PBMT scripts.


� ANTms44293: Include LT status in the status checks

Problem: The node status check script includes a number of

checks allowing a status compare prior to and after an operation

(migration, SW upgrade). These checks do not include an

overview of the LT status.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 156/176

Solution: The status check file now also contains an option to

report the LT availability status.

1.281 V1.4.59




tool is 1.32


1.282 V1.4.58


� ANTms43293: Transaction sometimes not released

Problem: In certain special conditions there is a possibility that

the migration script ends pre-maturely due to a detected problem

without having released the transaction that was claimed prior to

the restart of the system with the new SW.

Solution: This problem has been addressed in this version.

1.283 V1.4.57




tool is 1.31

Solution: Support for this version has been included. Usage for




� Provide a capability option to the migration script

Problem: PBMT supports various NT board types and release

streams. No option was available to dump

this information.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 157/176

Solution: The option --cap has been added to print out this

information (and exit afterwards).

1.284 V1.4.56


� ANTms40631: NT offline migration tool version 10.1.2

Problem: Latest version for R3.3 of the NT offline migration tool is

10.1.2.

Solution: Support for this version has been included. Usage for




� IGMPXmlfile extraction confusion

Problem: Currently PBMT only extract the IGMPXmlfile under

certain conditions. It turns out that it is needed when migrating

to a release > R2.2.

Solution: Conditional extraction has been relaxed.

1.285 V1.4.55


� ANTms40019: Minor error in child exit monitoring

Problem: There is an error when monitoring the exit of a child

process resulting in incorrect information being returned.

Solution: This problem has been fixed by re-initializing a variable

for every iteration of the monitoring SW loop.

� ANTms40542: Transaction sometimes not released

Problem: Releasing the transaction after online SW reduction may

fail but the process continues without checking the error.

Solution: In case resetting the transaction owner IP address failed

a second attempt is made using the global IP address

(255.255.255.255) and an error is returned if that too fails. No SW

download will be attempted.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 158/176


� Ignore case in board config file

Problem: When minimizing an SWP a list board mnemonics can

be provided using a config file (case sensitive).

Solution: When reading the board config file all board

mnemonics are read as upper-case.

� Handle a fatal crash of the NT OFLMT when determining the

version information.

Problem: In case the NT offline migration tool crashes with a fatal

unix-level error the migration script continued. Functionally there

is no problem since migration will fail in the end in any case.

Solution: The migration script pre-maturely ends in case

determining the NT OFLMT version information results in a fatal

error.

� Reset transaction owner IP address in case of emergency exit.

Problem: In case of an emergency exit of the PBMT scripts it

could be that the transaction was taken using an SNMP set.

Solution: Reset the transaction owner IP address to 0.0.0.0 in case

of an emergency exit. Possible errors will be ignored.

1.286 V1.4.54


� ANTms38662: Provide environment check on toolset

Problem: There is a dependency with respect to versions of the

offline migration tools used by PBMT. Incorrect combinations will

lead to incompatibilities. This is checked at runtime.

Solution: This option is provided to verify at build time whether

the correct versions of the tools are included in the image that will

be put on the CD

1.287 V1.4.53

1.287.1 Error corrections and workarounds

� ANTms26421: Prepare PBMT for offline migration tools to

R3.3


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 159/176

Problem: PBMT only supported migration to R3.2.

Solution: This version of PBMT supports the offline migration

tools for migration to R3.3

� ANTms38950: FD Extended LT mode results in failure of

PBMT tools

Problem: No NT-B is present in the equipment overview when an

FD equipment is configure in extended LT mode. This leads to a

failure of the PBMT tools as the NT identification of the B NT

remains an empty string.

Solution: The default value for both NT positions has now been

set to “EMPTY”.


� Verify that the tool to calculate the checksum of the SHUB

database is executable

Problem: The SHUB migration tool uses a tool to compute a

checksum. In case this tool is not executable, the resulting

database is not usable as the checksum is missing.

Solution: From this release onwards the migration script will

verify that this tool is executable and will exit if this is not the case.

1.288 V1.4.52


� ANTms38406: IGMPXmlFile not extracted when migtrating to

R3.2

Problem: When migrating the SHUB DB to R3.2 extraction of the

IGMPXmlFile is required.

Solution: This version of PBMT also extracts the IGMPXmlFile

before attempting SHUB DB migration

1.289 V1.4.51


� ANTms26421 and ANTms37972: Support of SHUB OFLMT till

v1.30


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 160/176

Problem: PBMT supported SHUB OFLMT versions till 1.27. The

latest version is 1.30 (for support of migrations till R3.3. From

Version 1.28 one parameter has been suppressed in the SHUB

command configuration file.

Solution: PBMT support of SHUB OFLMT till v1.30

� ANTms35659: reconfiguration of SFP

Problem: When migrating a 7330 system from a release earlier

then R3.1 to R3.3 the SFP configuration data needs to be re-

configured as the data is not stored in the NT database

Solution: Obtain the SFP configuration before attempting the

migration and restore the data once the system is back running

the new SW package.

� INTERNAL: Temporary files for SW reduction not created in

temporary work directory

Problem: When online SW package reduction is attempted some

temporary files are created. These are not stored in the working

directory associated to this node but rather in the directory from

where the toolset gets activated. The creation fails when no write

access has been granted.

Solution: Create the temporary files in the work directory

associated to this NE.

1.290 V1.4.49


� INTERNAL: Default BW reduction for the SHUB to Yes

Problem: Currently the BW reduction option during the SHUB DB

migration has been defaulted to NO. This should be set to Yes in

order to take the BW into account that is extracted from the NT

database for MCAST streams.

Solution: Default has been set to Yes.

� INTERNAL: Fix clearcase admininistration issues

Problem: Currently


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 161/176

1.291 V1.4.47


� ANTms33845: Allow configurable arbergtag.

Problem: R2.4 of the ISAM was using a hard-coded value for the

Arbergtag (cli command configure pppox-relay cross-

connect max-payload-tag option in R3.1). After migration

for R3.1 (where the option is configurable) the default is different

from the hard-coded value. The NT offline migration tool has

been changed to allow configuration of the value.

Solution: Configuration of the max-payload-tag is now controlled

using a new command line option for the migrate.pl script: --

confarberg. Configuration of the desired value is done via the

param.cfg file: ARBERGTAG=1|0 (1 = INSERT, 0 = NOINSERT). In

case the option is not enabled all pppox-relay cross-connect

instances will have max-payload-tag set to NOINSERT.

� ANTms33348: Allow configurable DCHP option 82.

Problem: R2.4 of the ISAM was using hard-coded values for the

DHCP option 82 (cli commands configure system port-

num-in-proto and configure system loop-id-syntax

options in R3.1). After migration for R3.1 (where the option is

configurable) the default is different from the hard-coded values.

The NT offline migration tool has been changed to allow

configuration of the value.

Solution: Configuration is now controlled using a new command

line option for the migrate.pl script: --confopt82. Configuration of

the desired value is done via the param.cfg file:

• SYS_PORT_NUM_MED=1|2|3|4 (1: log-slot-num, 2: position-

based, 3: type-based, 4: legacy-num CLI options)

• ATM_BASED_SYNTAX=”Access_Node_ID atm

Rack/Frame/Slot/Port:VPI.VCI” (on one line)

• ETH_BASED_SYNTAX=” Access_Node_ID eth

Rack/Frame/Slot/Port:VPI.VCI” (on one line)

In case the option is not selected the following defaults will apply:

SYS_PORT_NUM_MED: log-slot-num

ATM_BASED_SYNTAX: Access_Node_ID atm


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 162/176

Rack/Frame/Slot/Port:VPI.VCI

ETH_BASED_SYNTAX: Access_Node_ID eth Rack/Frame/Slot/Port

� ANTms28460: tftp time out problem

Problem: Due to settings of the tftp timeout value on AWS and

the value used by the migration script (both 5 seconds) it

frequently occurs that downloading the database fails.

Solution: Lowering the timeout value for the PBMT tools resolves

the timeout clash and guarantees better DB download results.

� ANTms32709: Unitialized value in upgrade.pl script.

Problem: The value of SECUREDBSAVE is not initialized properly.

Consequently, the script does not perform a wait after the SHUB

database command.

Solution: The coding error has been corrected.

� INTERNAL: don’t suspend tftp in case --noact has been

supplied

Problem: When migrating from R2.2 to R2.3 it is required to

disable tftp on the NT to prevent the SHUB from starting

prematurely. In case migration is executed with the --noact

option tftp is disabled while it should not.

Solution: Don’t disable in case the option --noact has been

selected.

� INTERNAL: include perlTL1 interface

Problem: When executing the pre- and post-operation scripts,

calling the TL1 interface fails as the perl module is not included in

the package.

Solution: The perl TL1 interface library has been included in the

PBMT package.

� INTERNAL: Long running CLI commands may be interrupted

before completion

Problem: When executing the pre- and post-operation scripts,

long-running CLI commands may be interrupted before

completion due to a too short telnet timeout value.

Solution: The telnet timeout value is by default 10 minutes and

can be overridden by the --telnetto command line option

when launching the script.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 163/176

� ANTms31758: upgrade.pl generates perl error

Problem: When trying to upgrade an ISAM the PBMT generates

under specific conditions a perl error and does not run till

completion.

Solution: On detecting one of the following error, the call to the

error reporting function was not correct, this has been corrected:

• New SW has not been downloaded when trying to upgrade

to this new SW version

• The SW to be upgraded to was not downloaded

successfully, i.e. its availability is ‘disabled’

� ANTms28676: NANT is not supported by PBMT

Problem: When trying to upgrade a NANT-A based system, PBMT

scripts fail.

Solution: The problem was caused by the spinning wheel

introduced in the CLI output from R3.1 onwards. PBMT scripts

now first remove the character codes associated with this spinning

wheel before continuing with the response parsing.

� ANTms28838: Typo’s when calling pre- and post-upgrade

scripts

Problem: upgrade.pl contained some typos when calling the pre-

and post-upgrade scripts. Consequently these scripts were not

called.

Solution: Without the code change it is not possible to call pre-

and post-upgrade scripts. This has been corrected in this release.

� ANTms30214: SW download fails using PBMT

Problem: Under certain conditions SW download using PBMT fails

when releasing the transaction. As a result SW download does

not start.

Solution: Two changes were made:

• The OSWP abort is no longer called when the seconds

OSWP indicates that no SWP packages is loaded

• A small delay between aborting the OSWP and releasing

the transaction has been introduced.

� ANTms30899: show software-mgnt sometimes no response

Problem: Under certain conditions SW download using PBMT fails

because no response is received to the

show software-mngt command. The SW


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 164/176

download however continues and is most cases succeeds.

Solution: Three changes were made:

• Every show software-mngt command can be retransmitted,

not only the first one

• A delay of 2 seconds has been introduced between each

retransmission.

• Retransmission is tried up to 4 times before giving up.


� Skip SW migration or SW upgrade of ISAM when pre- or post-

procedure script fails

Problem: Till now, the pre- and post-upgrade or migrate scripts

were not treated as a vital part of the PBMT package hence the

exit code was ignored when the script ended.

Solution: From this release onwards the pre- and post-scripts’ exit

codes are taken into account, hence SW upgrade or migration will

end in case the script returns an error (a non-0 code on Unix level)

� Print the failure reason (SW DL, migration, SW upgrade) in

the overall log file and on terminal

Problem: Currently no details are passed on to the parent PBMT

script in case of a failure.

Solution: From this release onwards visual feedback is returned to

the log file of the calling PBMT script and is also getting printed to

the standard error device: the terminal from where the script was

launched.

� Force SW reduction even if not really needed

Problem: R3.1 implements an intelligent SW download. However

boards released to the field are factory flashed with the complete

package. As a result it could be that even in that case SW DL of a

new package may fail due to a disk threshold being exceeded.

Solution: From this release onwards a new option has been

added to the SW download script allowing someone to force

online SW reduction: --reduce.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 165/176

1.292 V1.4.42


� ANTms23976, ANTms14531: Post Migration script needed

Problem: When performing a network migration the customer

wants to execute a number of checks to determine whether a

migration can be labelled as successful.

Solution: A new script has been added to the PBMT toolset which

can be run before and after the migration (or upgrade). The

results of both runs can then be compared for the differences.

Based on this information a customer can add a node to the list of

successfully migrated nodes.

� Internal: SHUB migration for ECNT-C not ok

Problem: When starting migration for the SHUB the board type is

fixed to ECNT-A in case no migration to ECNT-C was requested.

In case the board type is ECNT-C, this should be indicated to the

SHUB migration process.

Solution: In case the NT type is ECNT-C, this information is

passed on to the SHUB migration process.


� Add R3.2 to the capability model

Problem: R3.2 is not known to the toolset in terms of build

number.

Solution: R3.2 has been added to the model and it is made sure

that an upgrade is needed rather then a migration (the database

remains the same)

� [R&D only] Allow looped migrations

Problem: Allow for batch migration runs simulating multiple

migrations to guarantee the migration process

Solution: An R&D script has been added to the toolset

(loopMig.pl) allowing the same migration to be carried out ‘n’

number of times.

� [R&D only] Allow migration scenarios

Problem: Allow for various migrations to be executed using a

migration scenario.


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 166/176

Solution: An R&D script has been added to the toolset

(migScenario.pl) allowing migrations, upgrades and downgrades

to be carried out using a scenario file.

1.293 V1.4.38


� ANTms19172: Migration R2.4.20 to R3.1 fails on RVLT-A

Problem: When trying to upgrade an ARAM-D from R2.4 to R3.1

the software download failed on an SNMP set error.

Solution: This specific problem occurs when the AWS is

connected with multiple Ethernet interfaces to an ISAM network.

Every Ethernet interface is configured with its own IP address. In

this specific case, the IP addresses did belong to a different sub-

net. Before performing the online SW reduction – which is part of

the download of the new SW – we try to set the transaction but

used the IP address of the AWS host in stead of the IP address

associated to that interface. The IP address used to set the

transaction is now taken from the OSWP file since the IP address

in the OSWP file has to be the address associated to the Ethernet

interface (it gets configured by the AWS).

� ANTms23105: PBMT needs to wait longer after SW activation

Problem: When migrating to a new SW release, the PBMT tools

activate the new OSWP and start a wait loop for the NT to

become reachable again after the activation. Due to the slow

response on this OSWP activation, the wait loop receives a

response to the ping of the current SW release (and not of the

newly activated SW) causing the loop to exit prematurely and

resulting in a telnet timeout when trying to log in via CLI again.

Solution: An extra configurable time-out parameter has been

added to param.cfg. The toolset will wait the amount of seconds

specified by this parameter (ACT_PING_WAIT) before starting the

wait loop. The default value has been set to 30 seconds.

� ANTms23395: SW upgrade fails due to SNMP set error

Problem: OSWP activation by the PBMT tools is achieved by an

SNMP set request. This may result in a

failure in case the transaction has been


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 167/176

taken by an NT application.

Solution: Set the transaction before trying to activate the new

OSWP using an SNMP set request.

� ANTms22321: Transaction time-out unit has changed from

R2.5 onwards

Problem: Prior to release 2.5 the transaction timeout value was

expressed in milliseconds while from R2.5 onwards it is expressed

in units of 1/100 of a second.

Solution: During the migration process the PBMT scripts take the

transaction and set the timeout to indefinite. After the migration

process the timeout gets reset to the initial value read before

modifying the transaction timeout value.

� ANTms22602: On-line SW reduction did not reduce anything

Problem: Due to the change in naming philosophy (in stead of

changing the extension we replace characters 5 and 6 of the

OSWP and SWP name) an internal check was skipped resulting in

no space being freed up in the NT after the on-line SW reduction.

Solution: The internal SW check has been corrected.

� ANTms23976: ARAM-D post-migration activity

Problem: Migrating an ARAM-D equipment type with extenders

present results in not all boards present in extender shelves

running the new SW.

Solution: A post-migration action has been defined to reset the

NT a second time after having restarted with the new SW (this

reset will not be done for nodes without extender shelves).

� ANTms24159: Transaction still taken after NT reset

Problem: Activation of the new OSWP is preceded by a set-

transaction. This transaction is persisted through the NT reset

resulting in failures of CLI commands involving configuration

changes. The transaction gets released when the transaction

timer runs out.

Solution: The transaction will be

explicitly released after the NT has


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 168/176

restarted and allow as such configuration changed from any

manager in the Network Management network.


� Skip blank lines in board config file

Problem: When minimizing the SW package to be downloaded

one can specify a configuration file containing a list of boards

identified by their board mnemonic. There can be one board per

line. Blank lines were not ignored and resulted in a warning when

the SW minimizer script was executed.

Solution: Skip blank lines in the board configuration file.


� ANTms19625/ANTms21731: Allow integration of PBMT in

Network Management applications

Problem: It should be possible to perform network-wide

upgrades and migrations using the Network Management

application used by the customer. Consequently, progress and

results should be visible through the GUI of the Network

Management application.

Solution: Various means have been provided allowing detailed

information exchange between the PBMT scripts and the Network

Management application.

� ANTms20447: Allow offline minimization of the SW package

to be downloaded

Problem: In order to improve the SW download time it should be

possible to minimize the SW package present on the disk to only

contain a list of boards that can be specified by means of a

configuration file.

Solution: Prior to downloading the new SW release it is now

possible to minimize the delivered (and complete) package to

only contain the boards used by a customer. This new package

canthen be used during the SW download process. By default

characters 5 and 6 are replaced by ‘ZZ’ after the minimization

process.

Prerequisites

3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 169/176

Prerequisites Please refer to the customer documentation about the generic

prerequisites.

In case a hardware migration of ECNT-A to ECNT-C is attempted,

it is required to use version 1.26 of the SHUB migration tool. The

PBMT toolset will issue warning in case this migration is

attempted and a too low version of the SHUB offline migration

tool is being used.

Hardware prerequisites

None.

Other prerequisites

The migration tools (for NT and Service HUB) used by the PBMT

toolset are delivered separately.

Delivery Information

3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 170/176

2 Delivery Information Alcatel Item

Number

Description

SWPA 3FE 28567 AAAA MigrateIsam.3.1.13.tar.gz

Gzipped tar file:

./migrate.pl

./swdl.pl

./upgrade.pl

./commit.pl

./cleanup.pl

./exitCode.pl

./MinimizeSWP.pl

./preCheck.pl

./Config.pl

./stageont.pl

./ontDownloadandActivate.pl

./statusCheck.pl

./statusCheckCmp.pl

./cvtEcntA2C.pl

./cvtEcntA2E.pl

./cvtEcntC2E.pl

./cvtNantA2D.pl

./cvtNantD2E.pl

./cvtNantA2E.pl

./cvtNcncC2E.pl

./cvtH248toSip.pl

./mapVoiceIp2oam.pl


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 171/176

./convertCcEngine.pl

./ppp2pppipoe.pl

./ipAware2Ibridge.pl

./chgNwVlan.pl

./CHKCwarning.txt

./PRCKwarnings.txt

./sftpClient.pl

./dbCheck.pl

./3EC-36420-3056-DGZZA.csv

./netypes.txt

./racktypes.txt

./shelftypes.txt

./boardtypes.txt

./lib/Capability.pm

./lib/DM.pm

./lib/ErrorCodes.pm

./lib/FamilyCommon.pm

./lib/IsamCli.pm

./lib/Isam7342TL1.pm

./lib/Isam7354RUCli.pm

./lib/MigrateIsam7302.pm

./lib/MigrateIsam7302Etsi.pm

./lib/MigrateIsam7302EtsiNtt.pm

./lib/MigrateIsam7302Ansi.pm


./lib/MigrateIsam7302HiCap.pm



./lib/CommitIsam7302.pm


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 172/176


./lib/CommitIsam7302Hicap.pm


./lib/DownloadIsam7302.pm

./lib/DownloadIsam7302Ansi.pm

./lib/DownloadIsam7302Etsi.pm


./lib/DownloadIsam7302EtsiNtt.pm

./lib/DownloadIsam7302HiCap.pm



./lib/Octopus.pm

./lib/PbmtConfig.pm

./lib/PreCheckIsam.pm

./lib/PreCheckIsam7302.pm

./lib/PreCheckIsam7302Etsi.pm

./lib/PreCheckIsam7302EtsiNtt.pm

./lib/PreCheckIsam7302Ansi.pm


./lib/PreCheckIsam7302HiCap.pm


./lib/ReduceSWP.pm

./lib/StatusCheckCmpIsam7302.pm

./lib/StatusCheckCmpIsam7302HiCap.pm

./lib/StatusCheckCmpIsam7302Ansi.pm

./lib/StatusCheckCmpIsam7302Etsi.pm

./lib/StatusCheckCmpIsam7302EtsiNtt.pm




3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 173/176


./lib/StatusCheckIsam7302.pm

./lib/StatusCheckIsam7302Etsi.pm

./lib/StatusCheckIsam7302EtsiNtt.pm

./lib/StatusCheckIsam7302Ansi.pm


./lib/StatusCheckIsam7302HiCap.pm


./lib/TAD.pm

./lib/ToolCommon.pm

./lib/Utils.pm

./lib/UpgradeIsam7302.pm

./lib/UpgradeIsam7302Ansi.pm

./lib/UpgradeIsam7302Etsi.pm

./lib/UpgradeIsam7302EtsiNtt.pm


./lib/UpgradeIsam7302HiCap.pm


./lib/version.pm

./lib/Net/Ping.pm

./lib/Net/SNMP.pm

./lib/Net/TFTP.pm

./lib/Net/Telnet.pm

./lib/perlTL1/UdpChannel.pm

./lib/perlTL1/SshChannel.pm

./lib/Crypt/Lite/pm

./lib-perl/

./lib-perl/standalone/Class

./lib-perl/standalone/Compress


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 174/176

./lib-perl/standalone/Convert

./lib-perl/standalone/Crypt

./lib-perl/standalone/Data

./lib-perl/standalone/Digest

./lib-perl/standalone/File

./lib-perl/standalone/IO

./lib-perl/standalone/Math

./lib-perl/standalone/Net

./lib-perl/standalone/Sort

./lib-perl/standalone/Tie

./lib-perl/standalone/User

./lib-perl/standalone/auto

./lib-perl/standalone/gmp-4.2.2

./lib-perl/standalone/sun4-solaris-64int

./lib-perl/standalone/i86pc-solaris-64int

./lib-perl/standalone/i386-linux-thread-multi

./lib-perl/standalone/x86_64-linux-thread-multi

./lib-perl/perlSupplied/Net

./tools/NT

./tools/NT_ANSI

./tools/NT_LS

./tools/NT_GPON

./tools/NT_HICAP

./tools/Lanx

./tools/Lanx_ANSI

./tools/Lanx_LS

./tools/Lanx_GPON

./tools/IVPS

./tools/ONT_Release_Mapping.txt


3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 175/176

./tools/octopus/delIssconf.sh

./tools/octopus/delLanxZ.sh

./tools/octopus/enableSw_RW.sh

./tools/octopus/mapNonRecov.sh

./tools/octopus/readOswpFW.sh

./tools/octopus/readSwMgntIni.sh

./tools/octopus/resetNT.sh

./tools/octopus/resetNTred.sh

./tools/octopus/shubLanxCopy.sh

./tools/octopus/shubSwCheck.sh

./tools/octopus/suspendTftp.sh

./tools/octopus/syncLanxZ.sh

./tools/octopus/resetShell.cmd

./tools/octopus/sun4-solaris-64int/octopus

./tools/octopus/i86pc-solaris-64int/octopus

./tools/octopus/i386-linux-thread-multi/octopus

Installation Guide

3HH 04459 0172 FMZZA

Ed01 RL- 13/Jun/2013 176/176

3 Installation Guide

This package can be unpacked using the Unix tar utility on top of

the previous installation after having removed the files belonging

to the previous package (most of the files have a read-only file

attribute).

4 Documentation The PBMT-toolset is documented in the ISAM SW Upgrade and

Migration Application Procedures are provided on the SW

distribution.

3hh044590172fmzza01

Documents