Optical Network Manager EC-1

323-1091-230
SDH TRANSMISSION
Optical Network Manager EC-1
Network Upgrade Procedures
Release 19.1 Standard May 2007
SDH TRANSMISSION
Optical Network Manager EC-1
Document Number: 323-1091-230

Document Status: Standard
Product Release Number: Release 19.1
Date: May 2007
Copyright © 2005 Nortel Networks, All Rights Reserved.
Printed in England
The copyright of this document is the property of Nortel Networks. Without the written consent of Nortel Networks, given by contract
or otherwise, this document must not be copied, reprinted or reproduced in any material form, either wholly or in part, and the
contents of this document, or any methods or techniques available therefrom, must not be disclosed to any other person
whatsoever.
NORTEL NETWORKS CONFIDENTIAL: The information contained herein is the property of Nortel Networks and is strictly
confidential. Except as expressly authorized in writing by Nortel Networks, the holder shall keep all information contained herein
confidential, shall disclose it only to its employees with a need to know, and shall protect it, in whole or in part, from disclosure and
dissemination to third parties with the same degree of care it uses to protect its own confidential information, but with no less than
reasonable care. Except as expressly authorized in writing by Nortel Networks, the holder is granted no rights to use the information
contained herein.
So far as Nortel Networks is aware the contents of this document are correct. However, such contents have been obtained from a
variety of sources and Nortel Networks can give no warranty or undertaking and make no representation as to their accuracy. In
particular, Nortel Networks hereby expressly excludes liability for any form of consequential, indirect or special loss, and for loss of
data, loss of profits or loss of business opportunity, howsoever arising and whether sustained by the user of the information herein
or any third party arising out of the contents of this document.
*NORTEL NETWORKS, the Nortel Networks logo, the Globemark and Unified Networks are trademarks of Nortel Networks.
The trademarks and registered trademarks of particular suppliers mentioned in this publication are acknowledged on the page that
follows.
Optical Network Manager EC-1 Network Upgrade Procedures

ii
CDE,HP,HP-VUE,HP-UX are trademarks of the Hewlett-Packard Company

Ethernet is a trademark of the Xerox Corporation
Motif, X-Windows, CDE, Common Desktop Environment and UNIX are trademarks of The Open Group
Netscape and Netscape FastTrack are trademarks of Netscape Communications Corporation
Adobe, Acrobat and Reader are trademarks of Adobe Systems Incorporated.
323-1091-230 Release 19.1 Standard

iii
Publication history
May 2007
Release 19.1 Standard
April 2006
Release 19 Standard
April 2005
December 2004
Release 18 Standard
March 2004
Release 17 Standard
December 2002
June 2002
Release 16.1 Preliminary
April 2002
Release 16 Standard
February 2002
Release 15 SP2 Standard (Revision 1).
January 2002
Release 15 SP2 Standard.
February 2001
Release 15 Standard.
September 2000

iv Publication history
December 1998
Release 13.1 Standard.
October 1998
Release 13 Standard (Revised).
September 1998
September 1998

v
Contents
About this document xv
Technical support and information xxiv
Introduction 1-1
Background information 1-1
Supported NE types 1-2
Supported upgrade paths 1-2
Management platforms 1-3
Hardware requirements 1-5
EC-1 platform 1-5
Network elements 1-6
Software requirements 1-7
EC-1 platform 1-7
Network elements 1-7
Upgrade philosophy 1-8
EC-1 and NE software upgrade overview 1-8
Committing to and backing out from EC-1 and NE upgrades 1-10
Troubleshooting 1-10
Preparing for the upgrade 1-12
Upgrading EC-1 locally (via CD-ROM) 2-1

Overview 2-1
Additional reference information 2-1
Preparation 2-4
Backing up the EC-1 platform prior to upgrade 2-6
Increasing the size of the /home partition 2-7
Removing a redundant NE load image from the EC-1 platform 2-12
Removing redundant EC-1 load images from the EC-1 platform 2-14
Creating the required disk space on any HP platform 2-15
Loading EC-1 Release 19.1 software onto EC-1 2-18
Setting file permissions on EC-1 software 2-19
Upgrading the EC-1 software to Release 19.1 2-20
Post upgrade options 2-27
Upgrading EC-1 from the Optical Network Manager Application

Platform (CD-ROM) 3-1
Overview 3-1
Preparation 3-4
Logging onto the EC-1 platform remotely (from the Optical Network Manager
AP) 3-6

vi

Removing a redundant NE load image from the EC-1 platform 3-14
Loading EC-1 software from a CD-ROM on the Optical Network Manager Application
Platform 3-20
Upgrading EC-1 from the Optical Network Manager platform

(using ESWD) 4-1
Overview 4-1
Preparation 4-4
AP) 4-6
Removing a redundant NE load from image the EC-1 platform 4-14
Extracting EC-1 software from DAT onto the Optical Network Manager Application
Platform 4-20
Scheduling the EC-1 software release delivery 4-23
Deleting the EC-1 software release from the Optical Network Manager Application
Platform 4-26
Upgrading NE software 5-1

Overview 5-1
Preparation 5-4
Loading NE software 5-6
Loading NE software from a DAT drive on the EC-1 5-6
Loading NE software using ESWD from the Optical Network Manager Application
Platform 5-7
Installing the software load from CD-ROM 5-9
Downloading NE load images 5-16
Path protection switch alignment 5-17
Activating downloaded NE load images 5-18
Backing out of an NE upgrade 6-1

Backing out before software activation 6-2
Backing out after software activation 6-3
Committing to an NE upgrade 7-1
Backing out of an EC-1 upgrade 8-1

The backout procedure 8-1
Committing to an EC-1 upgrade 9-1

vii
The commit procedure 9-1

Removing the EC-1 redundant upgrade files from the EC-1 system 9-3
Solving EC-1 upgrade problems 10-1

The upgrade script (Upgrade_EC1) 10-1
Incorrect file permissions 10-1
Invalid upgrade user 10-2
Incorrect command line arguments 10-2
Upgrade directory problems 10-3
Release note problems 10-4
Environment and configuration 10-5
EC-1 not running 10-6
Alarms present 10-6
Communications check 10-7
Installing EC-1 Release 19.1 10-7
Shutting down the current EC-1 release 10-8
Switching EC-1 software 10-9
Starting EC-1 Release 19.1 10-9
The backout script (Backout_EC1) 10-10
Incorrect file permissions 10-10
Invalid user 10-10
Original EC-1 directory problems 10-10
Release note problems 10-11
Environment and configuration 10-13
EC-1 not running 10-14
Alarms present 10-14
Communications check 10-15
Shutting down EC-1 Release 19.1 10-15
Switching EC-1 software 10-16
Starting the original EC-1 release 10-16
Solving NE upgrade problems 11-1

Alarms to clear from the network before an upgrade 11-1
No response from network hosts 11-2
Investigating NE communications failures 11-3
Checking gateway NEs 11-3
Checking transport layer communications to NE 11-4
Checking gateway routing tables 11-5
Storing logs for further investigation 11-6
Appendix A: EC-1 recovery from DAT 12-1

Recovering the EC-1 platform from a backup 12-1
Appendix B: osi_comms.conf file 13-1

OSI over IP tunnelling 13-2
Level 2 routing principles 13-3
Level 1 areas 13-3
Level 2 subdomain 13-4
EC-1 osi_comms.conf file configuration 13-5
Default state of the osi_comms.conf file 13-6
Manual Area Addresses 13-7
ISIS Routing 13-7
LAN Card Routing 13-8

viii
Appendix C: Migration of HP-UX 10.20 to HP-UX 11i 14-1

Introduction 14-1
Supported preconditions: 14-2
Post conditions: 14-2
Requiremets: 14-2
References: 14-3
Required Nortel Networks software and PEC Codes 14-3
Supported hardware 14-3
Migration to HP-UX 11i on a standalone EC-1 14-4
Validate platform configuration data 14-4
Review EC-1 release level on a standalone EC-1 14-7
Validate the DAT drive on a standalone EC-1 14-8
Backing up NE software loads 14-9
Backing up network configuration data 14-10
Shut down the EC-1 platform 14-11
Install HP-UX 11i 14-11
Loading LAN configuration script 14-24
Configuring the second Ethernet port 14-26
Validate LAN cabling 14-28
Reinstall Optical Network Manager EC-1 R16.2 application software 14-29
Validating the EC-1 application 14-37
Restoring network configuration data 14-38
Restoring NE software loads 14-40
Validation of NE association 14-41
HP-UX 11i with a temporary 'warm standby' EC-1 14-42
Equipment check for temporary EC-1 platform 14-42
Obtain temporary platform configuration data 14-48
Set up temporary 'warm standby' EC-1 14-48
Installation of HP-UX 11i on temporary 'standby' EC-1 14-51
Updating the operating mode of the 'standalone' EC-1 14-77
Migration to HP-UX11i on primary and standby EC-1s 14-79
Validate platform configuration data 14-81
Review EC-1 release level on a primary/secondary EC-1 14-84
Validate the DAT drive on a primary/secondary EC-1 14-85
Backing up NE software loads on primary/secondary EC-1s 14-86
Synchronizing primary and secondary EC-1s 14-87
Backing up network configuration data on primary/secondary EC-1s 14-88
Shut down the target EC-1 platform 14-89
Validation of network visibility 14-91
Install HP-UX 11i on a primary/secondary EC-1 14-93
Restoring NE software loads 14-124
Restoring NE software loads on primary / secondary EC-1s 14-126

ix
Restoring EC-1 archives on secondary EC-1s 14-127

Switching back from a standby EC-1 to the target EC-1 14-127
Validation of NE association 14-130
Shutdown of any 'temporary' standby EC-1 14-131
Installing DDS1 DAT drivers 14-132
Changing the default RCA directory 14-133
Scheduling network configuration back ups to a remote system 14-134
Moving to a new HP-UX11i platform 14-135
Appendix D: DCN Guidelines 15-1

Introduction 15-1
Appendix E: PM Engineering
guidelines 16-1
Limits on PM collection 16-1
EC-1 Span of control guidelines 16-2
Performance monitoring point control script - pm_control 16-3
Requirements 16-4
Recommendations 16-4
PM Collection Enhancement - PM data collection time (24 hours) 16-8
Appendix F: EOW script 17-1

Introduction 17-1
Problem Denifition 17-2
Workaround 17-2
Using the EOW Script 17-2
Appendix G: LAN swap script 18-1

Introduction 18-1
Appendix H: Send_ne User Instructions 19-1

Introduction 19-1
Send_ne for specific network elements 19-2
Send_ne options 19-4
Send_ne help 19-4
NE_LISTING 19-4
Sending a CLUI file to an NE 19-6
Connecting to a network element 19-8
Software download 19-9
Booting the software on the network 19-11
Committing the software 19-12
Software listing 19-12
Card view listing 19-14
NE Backups 19-14
Restoring NE backups 19-16
Sync Report 19-17
DCN information 19-18
Index 20-1
Figures
Figure 1-1 Management platforms (including Optical Network Manager Applica-
tion) 1-4

x
Figure 1-2 Management platform (no Optical Network Manager Application

Platform) 1-5
Figure 1-3 Flowchart for Upgrading EC-1 and NE software 1-11
Figure 2-1 Flowchart - Upgrading to Release 16.2 locally (from the same
EC-1 platform) 2-3
Figure 3-1 Flowchart - Upgrading to Release 19.1 from the Optical Network
Manager 3-3
Figure 4-1 Flowchart - Upgrading to Release 19.1 from the Optical Network
Manager (using ESWD) 4-3
Figure 5-1 Flowchart - Upgrading NE load image software 5-3
Figure 14-1 HP B180L cable connections (back view) 14-49
Figure 14-2 HP B2600 cable connections (back view) 14-50
Figure 14-3 HP C3600 and C3750 cable connections (back view) 14-50
Table
Table 1-1 EC-1 Migration paths HP-UX 10.20 to HP-UX 11i June 2001 1-2
Table 1-2 EC-1 Upgrade Paths to EC-1 R19.1 1-3
Table 14-1 Summary of procedures 14-1
Table 14-2 Migration to HP-11i on a standalone EC-1 14-4
Table 14-3 System Parameters 14-18
Table 14-4 Migration to HP-11i with a tempoary ’warn standby’ EC-1 14-42
Table 14-5 B180L 14-43
Table 14-6 B2600 (prior to June 2003) 14-44
Table 14-7 B2600 (Post June 2003) 14-45
Table 14-8 C3600 14-46
Table 14-9 C3750 14-47
Table 14-10 System Parameters 14-56
Table 14-11 Migration to HP-11i on a standalone EC-1 14-79
Table 15-1 DCN Guidelines 15-1
Table 15-2 OSI Metrics summary 15-2
Table 16-1 PM points per NE 16-1
Procedures
Procedure 2-1 Backing up the EC-1 platform prior to upgrade 2-6
Procedure 2-2 Backing up the current network configuration prior to increasing
the size of the /home partition 2-8
Procedure 2-3 Increasing the size of the /home partition 2-9
Procedure 2-4 Removing a redundant NE load image from the EC-1 platform
2-12
Procedure 2-5 Removing a redundant EC-1 load image from the EC-1 platform
2-14
Procedure 2-6 Creating required disk space on any HP platform 2-15
Procedure 2-7 Loading the EC-1 software from CD-ROM 2-18
Procedure 2-8 Checking file permissions for EC-1 software 2-19
Procedure 2-9 Upgrading the EC-1 software to Release 19.1 2-21
Procedure 3-1 Logging onto the EC-1 platform remotely (from the Optical Net-
work Manager AP) 3-6
Procedure 3-3 Backing up the current network configuration prior to increasing
the size of the /home partition (locally, at the EC-1) 3-9
Procedure 3-4 Increasing the size of the /home partition (locally, at the EC-1)
3-11
Procedure 3-5 Removing a redundant NE load image from the EC-1 platform
3-14

xi
Procedure 3-6 Removing a redundant EC-1 load image from the EC-1 platform 3-16
Procedure 3-8 Loading EC-1 Release 19.1 from a CD-ROM mounted on the Optical
Network Manager Application Platform 3-20
Procedure 4-1 Logging onto the EC-1 platform remotely (from the Optical Network
Manager AP) 4-6
Procedure 4-3 Backing up the current network configuration prior to increasing the
size of the /home partition (locally, at the EC-1) 4-9
Procedure 4-4 Increasing the size of the /home partition (locally, at the EC-1) 4-11
Procedure 4-5 Removing a redundant NE load image from the EC-1 platform 4-14
Procedure 4-6 Removing a redundant EC-1 load image from the EC-1 platform 4-16
Procedure 4-8 Extracting EC-1 software from DAT onto the Optical Network Manager
Application Platform 4-20
Procedure 4-9 Scheduling the EC-1 software release delivery from the Optical Net-
work Manager Application Platform 4-23
Procedure 4-10 Deleting the EC-1 software release from the Optical Network Manager
Procedure 5-1 Extracting NE load images from DAT on the EC-1 5-6
Procedure 5-2 Extracting NE software from DAT onto the Optical Network Manager
Procedure 5-3 Copying the network element software load from the CD-ROM to the
Optical Network Manager EC-1 5-9
Procedure 5-4 Scheduling the NE software release delivery from the Optical Network
Manager Application Platform 5-12
Procedure 5-5 Deleting the NE software release from the Optical Network Manager
Procedure 5-6 Path protection switch alignment 5-17
Procedure 5-7 Activating downloaded NE software 5-18
Procedure 6-1 Backing out of an NE upgrade after activation 6-3
Procedure 8-1 Backing out of the EC-1 software upgrade 8-2
Procedure 9-1 Committing to EC-1 Release 19.1 9-1
Procedure 9-2 Removing the redundant upgrade files from the EC-1 system 9-3
Procedure 11-1 Resolving network host issues 11-2
Procedure 11-2 Checking gateway NEs 11-3
Procedure 11-3 Checking transport layer communications 11-4
Procedure 11-4 Checking gateway routing tables 11-5
Procedure 11-5 Storing logs for further investigation 11-6
Procedure 12-1 Recovering the EC-1 platform from a backup 12-1
Procedure 14-1 Validate platform configuration data 14-5
Procedure 14-2 Review EC-1 release level 14-7
Procedure 14-3 Validate the DAT drive on a standalone EC-1 14-8
Procedure 14-4 Backing up NE software loads 14-9
Procedure 14-5 Backing up network configuration data 14-10
Procedure 14-6 Shut down the EC-1 platform 14-11
Procedure 14-7 Booting the HP C3750/C3600/B2600/B180 platforms from the
CD-ROM drive 14-12
Procedure 14-8 Loading the HP-UX 11i operating environment from the DVD
CD-ROM drive 14-14
Procedure 14-9 Loading LAN configuration script 14-24
Procedure 14-10 Configuring the second Ethernet port 14-26
Procedure 14-11 Validate LAN cabling 14-28

xii
Procedure 14-12 Reinstall Optical Network Manager EC-1 R16.2 application soft-
ware 14-29
Procedure 14-13 Validating the EC-1 application 14-37
Procedure 14-14 Restoring network configuration data 14-38
Procedure 14-15 Restoring NE software loads 14-40
Procedure 14-16 Validation of NE association 14-41
Procedure 14-17 Equipment check for temporary EC-1 platform 14-43
Procedure 14-18 Obtain temporary platform configuration data 14-48
Procedure 14-19 Set up temporary 'warm standby' EC-1 14-49
Procedure 14-20 Booting the HP B2600/C3600/C3750/B180L platforms from either
the CD-ROM or DVD-ROM drives 14-51
Procedure 14-21 Loading the HP-UX 11i operating environment from the DVD/
CD-ROM drive 14-53
Procedure 14-25 Reinstall Optical Network Manager EC-1 R16.2 application soft-
ware 14-68
Procedure 14-27 Updating the operating mode of the 'standalone' EC-1 14-77
Procedure 14-28 Validate platform configuration data 14-82
Procedure 14-29 Review EC-1 release level 14-84
Procedure 14-30 Validate the DAT drive on a primary/secondary EC-1 14-85
Procedure 14-31 Backing up NE software loads on primary/secondary EC-1s 14-86
Procedure 14-32 Synchronizing primary and secondary EC-1 14-87
Procedure 14-33 Backing up network configuration data on primary/secondary
EC-1s 14-88
Procedure 14-34 Shut down the target EC-1 application 14-89
Procedure 14-35 Activation of 'warm standby' secondary EC-1 14-89
Procedure 14-36 Validation of network visibility 14-92
Procedure 14-37 Booting the HP B2600/C3600/C3750/B180L platforms from either
the CD-ROM or DVD-ROM drives 14-93
Procedure 14-38 Loading the HP-UXi operating environment from the DVD/
CD-ROM drive 14-95
Procedure 14-42 Reinstall Optical Network Manager EC-1 R16.2 SP2 application
software 14-111
Procedure 14-44 Validating a 'hot standby' secondary EC-1 application 14-121
Procedure 14-45 Validating a 'warm standby' secondary EC-1 application 14-121
Procedure 14-47 Restoring NE software loads 14-124
Procedure 14-49 Restoring NE software loads on primary / secondary EC-1s
14-126
Procedure 14-50 Restoring EC-1 archives on secondary EC-1s 14-127
Procedure 14-51 Switching back from a warm standby platform 14-127
Procedure 14-52 Switching back from a hot standby platform 14-129
Procedure 14-53 Validation of NE association 14-131
Procedure 14-54 Shutdown of any temporary 'standby' EC-1 14-131
Procedure 14-55 Installing DDS1 DAT drivers (B180L, B2600, C3600 and C3750)
14-132
Procedure 14-56 Creating a DDS1 DAT (B132L, B132L+, B180L, B2600, C3600 and

xiii
C3750) 14-132
Procedure 14-57 Changing the default RCA directory 14-133
Procedure 14-58 Scheduling network configuration back ups to a remote system 14-134
Procedure 14-59 Moving to a new HP-UX11i platform 14-136
Procedure 16-1 Run the pm_control script 16-5
Procedure 16-2 Editing the config.conf file 16-8
Procedure 17-1 Running the EOW script 17-4
Procedure 17-2 Exiting the EOW script 17-5
Procedure 17-3 Defining an EOW span of control 17-6
Procedure 17-4 Adding NEs to a span of control 17-8
Procedure 17-5 Deleting an NE from the EOW span of control 17-10
Procedure 17-6 Selecting an EOW span of control 17-11
Procedure 17-7 Deleting an EOW span of control 17-11
Procedure 17-8 Changing the sampling law of an EOW span of control 17-13
Procedure 17-9 Listing saved EOW span of controls 17-14
Procedure 17-10 Displaying details of NEs in active span of control 17-15
Procedure 17-11 Auditing the NEs in active span of control 17-17
Procedure 17-12 Fixing the NEs in active span of control 17-18
Procedure 17-13 Auditing and fixing span of controls using flags 17-20
Procedure 17-14 Auditing and fixinf span of controls using cronjobs 17-21
Procedure 18-1 LAN swap script 18-2
Procedure 19-1 Opening a new xterm 19-1
Procedure 19-2 Getting send_ne help 19-4
Procedure 19-3 Getting a network element listing using send_ne 19-4
Procedure 19-4 Sending a CLUI file to a network element using send_ne 19-6
Procedure 19-5 Connecting to a network element using send_ne 19-8
Procedure 19-6 Booting the software on the network using send_NE 19-11
Procedure 19-7 Committing the software using send_ne 19-12
Procedure 19-8 Listing software on network elements using send_ne 19-12
Procedure 19-9 Card view listing using send_ne 19-14
Procedure 19-10 Network element backups using send_ne 19-14
Procedure 19-11 Network element restore using send_ne 19-16
Procedure 19-12 Getting a sync report using send_ne 19-17
Procedure 19-13 Getting DCN information using send_ne 19-18

xv
About this document

Audience
This Nortel Networks technical publication is for Nortel Networks’ staff and
customers who are part of the Optical Network Manager EC-1 and
multiplexer upgrade process. This document also provides a guide to any
person who needs to have an overview of the upgrade process.
Prerequisites
This document is written with the assumption that you understand the
following:
• Hewlett-Packard UNIX (HP-UX).
• Hewlett-Packard’s ‘vuepad’ editor.
• Motif and X-Windows from The Open Group.
• The Nortel Networks multiplexers that are used within the network, for
example, Nortel Networks OPTera Metro 4200 (TN-16XE), OPTera
Metro 4100 and OPTera Metro 4150 (TN-4XE), TN-4T, TN-1X, TN-1X/
S, TN-1C, and TN-1P.
Scope of document
This document describes the Optical Network Manager EC-1 software
upgrade for three generic upgrade scenarios as follows:
• locally from the Optical Network Manager EC-1 platform, through

CD-ROM (and to install the HP-UX patches if required)
• through a remote telnet session from the Optical Network Manager
Application Platform, using CD-ROM to deliver the Optical Network
Manager EC-1 software (and to install the HP-UX patches if required)
• through a remote telnet session from the Optical Network Manager
Application Platform, using Electronic Software Download (ESWD) to
deliver the Optical Network Manager EC-1 software (and CD-ROM to
install the HP-UX patches if required)
This document also describes multiplexer software (network element)

upgrades. Hardware upgrades that are associated with multiplexer upgrades
are described in the appropriate Nortel Networks technical publications.
These documents are listed in the Associated documentation section that
follows.

xvi About this document
Some customers have special upgrade requirements which are relevant to

their type of platform and network use. These individual requirements are
outside the scope of this document and are documented in customer specific
bulletins.
ATTENTION
Read and follow all of the information contained in each chapter appropriate
to your upgrade scenario. Failure to do the actions in the described sequence
can cause problems during the upgrade.
Optical Network Manager Application Platform

The Optical Network Manager Application Platform replaces the Integrated
Network Manager (INM) and/or Network Resource Manager (NRM). NRM
Release 6 was followed by INM Release 4 (European version). The Optical
Network Manager Application Platform manages multiple Optical Network
Manager EC-1s.
Associated documentation
The following publications are referred to in the upgrade procedures, or
provides an overview of the documentation and safety issues for using the
selected product. Dependent on your network configuration, not all of these
need be required.
You can access many of these handbooks on the Nortel Networks Web site by
registering at:
http://app45.nortelnetworks.com/cgi-bin/WebObjects/CRS
When you have registered you can access the Web site by going to:
https://www21.nortelnetworks.com/NAIL180/ion-handbook/handbooks/
external/default.html
and entering your user name and password when required.
Optical Network Manager EC-1 Releases

The Optical Network Manager EC-1 documents have the same titles and
identity codes for each release. Only the release number is different. The
Optical Network Manager EC-1 documents are listed below. For the purposes
of this list, ‘nn’ is 10, 12, 13, 13.1, 14, 15, 15 SP2, 15 SP4, 16, 16.1, 16.1 SP1,
16.2, 16.2 SP1, 17 , 17 SP1, 18, 18.1, 19 or 19.1.
• Optical Network Manager EC-1 Installation Procedures
(323-1091-202), Release nn.
• Optical Network Manager EC-1 User Procedures
(323-1091-402), Release nn.
Note: Optical Network Manager EC-1 Release 15 SP3 uses
Release 15 SP2 documentation.

About this document xvii
OPTera Metro 4200 (Release 1, 2, 3.x, 4.x, 5 and 6).

• Nortel OPTera Metro 4200 Documentation Overview & Safety
(323-1233-090)
• Nortel OPTera Metro 4200 System Description
(323-1233-100).
• Nortel OPTera Metro 4200 User Interface Description
(323-1233-301)
• Nortel OPTera Metro 4200 Provisioning and Operations Procedures
(323-1233-310)
• OPTera Metro 4200 System and Data Administration Procedures
(323-1233-302)
• Nortel OPTera Metro 4200 Alarm Clearing Procedures
(323-1233-543)
• Nortel OPTera Metro 4200 Maintenance Procedures
(323-1233-547)
Note: Previous to Release 2 the OPTera Metro 4200 was known as

‘TN-16XE’ and the documents have a title accordingly
OPTera Metro 4100 (Release 2.x to 4.x) and OPTera Metro 4150
(Release 5, 6, 7, 7.1, 8 and 9).
(323-1123-100).
(323-1123-301)
(323-1123-310)
(323-1123-543)
(323-1123-547)
Note 1: Previous to Release 4.x, the OPTera Metro 4100 was known as
‘TN-4XE’ and the documents have a title accordingly.
Note 2: At Release 5, the OPTera Metro 4150 supersedes the OPTera
Metro 4100.
(323-1123-100).
(323-1123-301)
• Nortel OPTera Metro 4150 System and Data Administration Procedures
(323-1123-302)
(323-1123-310)

xviii About this document

(323-1123-543)
(323-1123-547)
TN-4T (Release 1 and 2)

• Nortel TN-4T Handbook Overview & Safety (323-1133-090).
• Nortel TN-4T System Description (323-1133-100).
• Nortel TN-4T Software and Hardware Description (323-1133-100).
TN-1X Release 8.x onwards

• Nortel TN-1X Documentation Overview and Safety (323-1061-090).
• Nortel TN-1X System Description (323-1061-100).
• Nortel TN-1X Browser User Interface Guide (323-1061-403)
• Nortel TN-1X Command Line User Interface Guide (323-1061-401)
• Nortel TN-1X Alarm Clearing Procedures (323-1061-543)
• Nortel TN-1X Module Replacement Procedures (323-1061-547)
TN-1C Release 3 onwards

• Nortel TN-1C Documentation Overview and Safety (323-1081-100)
• Nortel TN-1C System Description (323-1081-100)
• Nortel TN-1C Browser User Interface Guide (323-1081-403)
• Nortel TN-1C Command Line User Interface Guide (323-1081-401)
• Nortel TN-1C Alarm Clearing Procedures (323-1081-543)
• Nortel TN-1C Equipment Maintenance Procedures (323-1081-547)
Note: From Release 5.1 the technical documentation for TN-1C and
TN-1P is combined. The documents are renamed as TN-1C/TN-1P and use
the TN-1C document identity codes.
TN-1P Release 2 and Release 5.0

• Nortel TN-1P Documentation Overview and Safety (323-1071-090)
• Nortel TN-1P System Description (323-1071-100)
• Nortel TN-1P Command Line User Interface Guide (323-1071-401)
• Nortel TN-1P Alarm Clearing Procedures (323-1071-543)
• Nortel TN-1P Equipment Maintenance Procedures (323-1071-547)
Note: From Release 5.1 the technical documentation for TN-1C and
TN-1P is combined. The documents are renamed as TN-1C/TN-1P and use
the TN-1C document identity codes.

About this document xix
INM Release 4.0

• Integrated Network Manager Introduction
(323-4011-102)
• Integrated Network Manager Installation and Administration
(323-4011-202)
• Integrated Network Manager Interface Login,
(323-4011-053)
• Integrated Network Manager Configuration
(323-4011-054)
• Integrated Network Manager Fault Management
(323-4011-055)
Note: For Release 4.3 the identity codes change from 323-4011-nnn to
323-4001-nnn. For subsequent releases refer to ‘Optical Network Manager
Application Platform Release 5.0 onwards’.
Optical Network Manager Application Platform Release 5.0 onwards

• Optical Network Manager Application Platform Introduction
(450-3101-100)
• Optical Network Manager Application Platform Installation and
Administration
(450-4011-201)
• Optical Network Manager Application Platform Interface Login,
(450-3101-012)
• Optical Network Manager Application Platform Configuration
Management Guide (450-3101-013
• Optical Network Manager Application Platform Fault Management User
Guide (450-3101-014)
Note: Optical Network Manager Application Platform superseded INM

Release 4.0/4.3
Data Communications Networks

• Nortel Data Communications Networks Commissioning Guide
(323-4061-210) – Release 2.0 and 3.0 only
• Nortel Data Communications Networks Provisioning Guide
(323-4061-151) – Release 2.0 and 3.0 only
• Nortel Data Communications Networks SDH Internal DCN Design
Guidelines (323-4061-100) – Release 4.0 and 5.0 only
• SDH DCN Design Using Nortel Networks Routers (323-4061-101) –
Release 5.0 and 6.x only
• SDH DCN Design Using Cisco Routers (323-4061-102) – Release 5.0 and
6.x only
• SDH DCN Design for Access Products (323-4061-103) – Release 6.x only

xx About this document
General
• Installing Peripherals Series 700 HP Part No B2355- 90041 E0892.
Using this document

This document has the following structure:
• Chapter 1, ‘Introduction’ provides an overview of the Optical Network
Manager EC-1 upgrade process and the network element upgrade process.
Chapter 1 also describes important precautionary actions which must be
performed to ensure that your network is in the correct state before
applying an upgrade.
• Chapter 2, ‘Upgrading EC-1 locally (via CD-ROM)’ describes how to
download and install the Optical Network Manager EC-1 software locally,
from the CD-ROM drive of the Optical Network Manager EC-1.
• Chapter 3, ‘Upgrading EC-1 from the Optical Network Manager
Application Platform (CD-ROM)’ describes how to download and install
the Optical Network Manager EC-1 software at a distance using a telnet
session from the CD-ROM mounted on the Optical Network Manager
Applications Platform.
• Chapter 4, ‘Upgrading EC-1 from the Optical Network Manager platform
(using ESWD)’ describes how to download and install the Optical
Network Manager EC-1 software at a distance using a telnet session from
the Optical Network Manager Applications Platform using Electronic
Software Download (ESWD). The Optical Network Manager EC-1
software is extracted from Digital Audio Tape (DAT).
• Chapter 5, ‘Upgrading NE software’ describes how to extract network
element load images from Digital Audio Tape, and how to download and
activate these load images.
• Chapter 6, ‘Backing out of an NE upgrade’ describes how to back out of
an network element upgrade before a commit is performed.
• Chapter 7, ‘Committing to an NE upgrade’ describes how to commit to
using new network element software.
• Chapter 8, ‘Backing out of an EC-1 upgrade’ describes how to back out of
an Optical Network Manager EC-1 software upgrade before it is
committed to use.
• Chapter 9, ‘Committing to an EC-1 upgrade’ describes how to commit to
the use of Optical Network Manager EC-1 Release 19.1.
• Chapter 10, ‘Solving EC-1 upgrade problems’ describes a number of
common Optical Network Manager EC-1 upgrade issues, and possible
solutions.
• Chapter 11, ‘Solving NE upgrade problems’ describes a number of
common network element upgrade issues, and possible solutions.
• Appendix A: EC-1 recovery from DAT describes how to perform a restore
of the Optical Network Manager EC-1 platform from a backup DAT.
• Appendix B: osi_comms.conf file describes how to edit the
osi_comms.conf file.

About this document xxi
• Appendix C: Preventing a Sync problem caused by End Of Shelf card

programming tells you how to detect whether your EOS card has been
correctly programmed.

xxii About this document
List of abbreviations
ASDAutomatic Script Driver
CLUICommand Line User Interface
CDECommon Desktop Environment
CSMCentralised Software Management
DATDigital audio tape
DBDatabase
DCCData Communications Channel
ECElement Controller
EOSEnd Of Shelf
ESWDElectronic SoftWare Download
GIFGraphics Interchange Format
GNBGraphical Network Browser
GNEGraphical Network Editor
HTMLHypertext mark-up language
INMIntegrated Network Manager
IP Internet Protocol
IPCInput Port Controller
IPLInitial Program Load
ISLInitial System Load
LANLocal Area Network
LAPDLink Access Protocol, D Channel
LCAPLocal Craft Access Panel
LOSLoss of signal
LVMLogical Volume Management
MACMedia Access Control
MOAManaged Object Agent
MSMultiplex Section
NENetwork Element
NRMNetwork Resource Manager
NSAPNetwork Service Access Point
OSIOpen Systems Interconnect
OSROptical Solutions Release
PMPerformance Monitoring
PPIPlesiochronous digital hierarchy physical interface
RAURemote Access Unit
RCARemote Central Archive
RSRegenerator Section
SAMSystem Administration Manager
SCSISmall Computer Systems Interface
SOCSpan Of Control
SP1/SP2Service Pack 1/2
STMSynchronous Transport Module
TCP/IPTransmission Control Protocol / Internet Protocol
TFTotal Fail
TNMSTransportNode Management System
TMTrail Manager
UIUser Interface
VCVirtual Container
VUEVisual User Environment

About this document xxiii

xxiv Technical support and information
Technical support and information

As far as Nortel Networks knows, the information in this document is correct.
If, however, you discover any errors or have comments about the arrangement
of the content, send details by email to:
IONNTPS@nortelnetworks.com
Nortel Networks provides a full technical support service for its customers.
The Nortel Networks Service Desk can be called at any time on the following
numbers:
Within Europe: Freephone 00800 8008 9009
Outside of Europe: +44 20 8920 4618
As an option, you can contact technical support through the Nortel Networks
Web site:
http://www.nortelnetworks.com/help/contact/global/
EMC/Safety conformance
This product/product family complies with the essential
protection requirements of the EMC Directive 89/336/EEC as
amended by 92/31/EEC, when it is properly installed and
maintained and when it is used for the purposes for which it is
intended.

1
1-1
Introduction 1-
Background information
EC-1 Release 19.1 is the element controller for the Nortel Networks TN-1X,
TN-1X/S, TN-1C, TN-1P, TN-4T, OPTera Metro 4100, OPTera Metro 4150
and OPTera Metro 4200 network elements (NEs). Based on an HP UNIX
platform, EC-1 is capable of managing a mixed network of these NEs.
Each of the NEs within the EC-1’s span of control stores its own
configuration information. The EC-1 only stores minimal data regarding the
NEs within its span of control, but archives configuration information for
each NE each night.
The EC-1 Release 19.1 user interface (UI) uses a Motif-based graphical
interface, and is capable of supporting multiple concurrent user interface
sessions. It can also communicate and serve the Optical Network Manager
Application Platform high order manager via a separate TCP/IP upward
interface.
Note: Earlier releases of the Optical Network Manager Application

Platform were known as Integrated Network Manager (INM) or Network
Resource Manager (NRM). NRM Release 6 was followed by INM
Release 4 (International version).
The EC-1 Release 19.1 communicates with the NEs using a Command Line
User Interface (CLUI) , transported by a 4 layer Open Systems Interconnect
(OSI) stack on the EC-1 and each NE.

1-2 Introduction
Supported NE types
EC-1 Release 19.1 manages the following NE types:
• TN-1X and TN-1X/S (Release 7, 8 and 9)
• TN-1C (Release 3, 5, 5.1, 5.2, 5.21, 6, 6.01 and 7)
• TN-1P (Release 2, 5, 5.1, 5.2, 5.21 and 6)
• TN-4T (Release 1 and 2)
• OPTera Metro 4100 (Release 3, 4, 4.5, 4.6, 4.7, 4.8, 4.9, 4.95 and 4.96)
• OPTera Metro 4150 (Release 5, 6, 7, 7.1, 8, 9 and 9.5)
• OPTera Metro 4200 (Release 1, 2, 3, 3.1, 3.5, 4 , 4.1, 5, 6 and 6.5)
This handbook includes software download procedures for all NE types.
Supported upgrade paths

EC-1 R16 was the first EC-1 release which supported both HP-UX 10.20 and
HP-UX 11i. However HP discontinued support for HP-UX 10.20 in June
2003.
As a result EC-1 R17 was the first EC-1 release, which is supported on
HP-UX11i only. Subsequently EC-1 R19.1 is also supported on HP-UX 11i
only.
CAUTION
If a customer is still on a HP-UX 10.20 and a variant of R16

then a migration to HP-UX 11i must be performed before EC-1
R19.1 can be installed..
A migration is when a user moves
• from an initial EC-1 Release on HP-UX 10.20 to the

same EC-1 Release on a variant of HP-UX 11i OR
For example :
From EC-1 R16.2 on HP-UX 10.20 to EC-1 R16.2 on HP-UX

11i
Table 1-1
EC-1 Migration paths HP-UX 10.20 to HP-UX 11i June 2001
Path HP-UX 10.20 Step 2 Step 3 Step 4 Step 5
1 EC-1 R16.0 Install HP-UX 11i Migrate to Upgrade to Upgrade to

EC-1 R16.1 June 2001 EC-1 EC-1 R19 EC-1 R19.1
EC-1 R16.1 SP1 R16.0/16.1/16.2
EC-1 R16.2
EC-1 R16.2 SP1

Introduction 1-3
Table 1-2
EC-1 Upgrade Paths to EC-1 R19.1
1
Before Upgrade After Upgrade
HP-UX 11i HP-UX 11i
EC-1 R18.0 EC-1 R19.1
EC-1 R18.1 EC-1 R19.1
EC-1 R19 EC-1 R19.1
Management platforms
Both Optical Network Manager EC-1 and Optical Application Platform
Application management platforms can be used within a network. Typical
management platform configurations are shown in Figure 1-1 and Figure 1-2.

1-4 Introduction
Figure 1-1
Management platforms (including Optical Network Manager Application)
Optical Network Manager

Applications
Platform
LAN0 TCP/IP
HUB
LAN1 TCP/IP
EC-1
LAN0 OSI
LAN
Network
Elements

Introduction 1-5
Figure 1-2
Management platform (no Optical Network Manager Application Platform)
1
EC-1
LAN0 OSI
LAN
Network
Elements
Hardware requirements
This section lists hardware requirements.
EC-1 platform
You can use a CD-ROM drive for upgrade purposes. If you need to upgrade a
platform you can upgrade the EC-1 either:
• Locally (from CD-ROM),
• From the Optical Network Manager Application Platform (from
CD-ROM),
• From the Optical Network Manager Application Platform (from DAT
using ESWD). This involves transferring Optical Network Manager AP
Centralised Software Management (CSM) compatible EC-1 Release 19.1
files onto the EC-1 platform using electronic software delivery (ESWD).
All EC-1 platforms should have an internal DAT drive. If your EC-1 platform
does not, then install an internal DAT drive. This is needed to add X-terminal
software or NE load images and to ensure that the daily EC-1 backups operate
correctly.
The following additional hardware is required for the upgrade process:

1 x Blank HP DAT.

1-6 Introduction
Network elements
There is no additional hardware required for NE software upgrades.

Introduction 1-7
Software requirements 1
This section lists software requirements.
EC-1 platform
Optical Network Manager EC-1 R19.1 supports the following version of the
HP-UX 11i Operating system software.
• HP-UX 11i June 2001 for B180L, B2600, C3600, C3750 platforms.
• HP-UX11i June 2004 for RP3410, RP3440 platforms.
For B180L, B2600, C3600, C3750 platforms :
• Either HP-UX 11i June 2001 Software on CD-ROM.
— NTNM51ZCAF - Operating Environment Disk 1
— NTNM51ZDAF - Operating Environment Disk 2
— NTNM51ZEAF - Documentation
• Optical Network Manager EC-1 Release 19.1 application software on
CD-ROM. The CD-ROM, NTQJ30PH, contains Acrobat Reader and
product documentation.
• Optical Network Manager EC-1 Release 19.1 ESWD DAT tape
(NTQJ30QH).
• X-terminal software on DAT or CD-ROM. You do not require this item if
no X-terminals are in use.
For platform RP34x0 refer to Appendix J of the Optical Network Manager
EC-1 Installation procedures, 323-1091-202.
Network elements
For each NE type that you upgrade, you need an NE load on DAT or
CD-ROM.

1-8 Introduction
Upgrade philosophy
This section details the upgrade philosophy:
• You must be able to upgrade the network without affecting its traffic
carrying capabilities. Any traffic outages or ‘hits’ are costly and so must be
avoided. While traffic is not hit, there is an inevitable loss in network
surveillance between the shutdown of the current release of EC-1 and the
introduction of EC-1 Release 19.1.
• The upgrade of EC-1 and Optical Network Manager Application Platform
is decoupled from the upgrade of NEs within the network.
• Optical Network Manager Application Platform must remain static during
the upgrade procedures. Upgrade the EC-1 and NE before upgrading these
systems.
EC-1 and NE software upgrade overview
ATTENTION
For further information on Remote Central Archive (RCA)/Warm/Hot
Stand-by and SDH DCN Deployment Engineering Limits refer to the
Associated documentation which lists EC-1 Release 19.1 handbooks on
Page xvi. The stand-by platform must be upgraded BEFORE the primary
EC-1.
From Releases 16 onwards a feature was introduced which provides the user
with a “hands-free” upgrade procedure. You simply gather all the relevant
information before starting the upgrade. You then launch the upgrade and
need do nothing more.
The upgrade software runs the healthcheck tool automatically. The upgrade
continues in spite of recommendations made by the healthcheck tool.
However, if an error occurs the upgrade waits for your intervention.
When the upgrade finishes you can read a report which will help you with
subsequent diagnostics.
Figure 1-3 shows the linear process you must follow to upgrade EC-1 and NE
software.
Note: The EC-1 platform upgrade must be performed BEFORE the

upgrade of NEs within the network. It is strongly recommended that you
do not commit to NE upgrades while running an OLD release of EC-1 as
the NEs will not be fully supported by the old release of EC-1.
There are three alternative scenarios for upgrading EC-1 software as follows:
• Load EC-1 software from the local CD-ROM.
Perform the upgrade locally from the EC-1

Introduction 1-9
• Load EC-1 software remotely from the Optical Network Manager AP 1

CD-ROM. Perform the upgrade remotely from the Optical Network
Manager AP via a telnet session.
• Load EC-1 software remotely from the Optical Network Manager AP
(ESWD):
— Extract EC-1 software from DAT onto the Optical Network Manager
AP
— Schedule EC-1 software delivery from Optical Network Manager AP
to EC-1 using Electronic Software Download (ESWD)
Then perform the upgrade remotely from the Optical Network Manager
AP (once the software is delivered)
There are three main stages in upgrading network element software:

1 Load the NE upgrade software onto the EC-1 platform. There are three
alternative methods of loading the NE software:
— From the local EC-1 DAT drive,
— From the local EC-1 CD-ROM drive, or
— Remotely from the Optical Network Manager AP (ESWD), see
CAUTION below:
– Extract NE software from DAT onto the Optical Network
Manager AP
– Schedule NE software delivery from Optical Network Manager
AP to EC-1
using Electronic Software Download (ESWD)
2 Download the NE software to the inactive software bank of one or more
NEs using send_ne utility, see CAUTION below.
3 Activate the new NE software. This puts the downloaded software into the
active software bank of each NE, forcing a warm reboot.
CAUTION
Some procedures can only be performed locally, at the EC-1
platform
Be aware that procedures for increasing the size of the EC-1
/home partition (only applicable to HP platforms B180L, B2600, C3600)
can ONLY be performed locally at the EC-1 platform and cannot be
performed remotely from the Optical Network Manager Application
Platform.

1-10 Introduction
Committing to and backing out from EC-1 and NE upgrades
CAUTION
Running old EC-1 software with new NE software
If you commit to an NE upgrade without first committing to an EC-1
upgrade, the upgraded NEs (with new software) will not be fully supported
by the EC-1 (with old software).
It is strongly recommended that if a backout of both EC-1 Release 19 .1and

NE upgrades is required, the NE upgrade backout should be performed first.
Figure 1-3 shows when you can use procedures which allow you to ‘commit’
to or ‘backout’ from an EC-1 or NE upgrade as follows:
• Commit to an EC-1 upgrade:
The EC-1 commit procedure removes the original release of EC-1 software
from the EC-1 platform. Once the EC-1 has been committed, a backout
cannot be performed.
• Backout of an EC-1 upgrade:
The EC-1 backout procedure removes Release 19.1 from the EC-1
platform and reverts to using the original EC-1 release software. Once the
EC-1 has been committed, a backout cannot be performed.
CAUTION
Backing out of an EC-1 upgrade
It is strongly recommended that the EC-1 upgrade backout procedure is only
performed after full investigation by Nortel Networks support engineers,
and escalation through the support structure. Backouts should only be used
as a last resort, should all other attempts fail to rectify a problem.
• Commit to an NE upgrade:
When NE software has been loaded and activated, the original NE software
is in the inactive bank of the NE. The ‘commit’ procedure copies the new
software into the inactive bank, removing the original NE software.
• Backout of an NE upgrade:
You can backout of the NE upgrade both before and after the downloaded
software has been activated:
— Before the software has been activated, the new NE software has been
downloaded, the original software is in the active bank and running on
the NE, and the new software is in the inactive bank. A backout
performed at this time causes the original software in the active bank
to overwrite the new software in the inactive bank.
— After activation of downloaded software has been performed, each
affected NE has the new load image software in its active software
bank, and the original load image software in its inactive software
bank. A backout performed at this time causes a switch to return the
original software into use in the active bank.
Troubleshooting
Be aware that Chapter 10 and Chapter 11 contain solutions to a number of
problems that can arise during the upgrade of EC-1 and NEs within the
network.

Introduction 1-11
Figure 1-3
Flowchart for Upgrading EC-1 and NE software
1
START
Read Chapter 1 (this Chapter) to ensure that you have suitable

hardware/software and that your network is in a suitable state for
upgrade. This chapter gives an overview of the upgrade process.
Decide how you want to upgrade the EC-1 software. There are three alternative
methods:
Chapter 2: Load EC-1 software from the local CD-ROM.
Perform the upgrade locally from the EC-1
or
Chapter 3: Load EC-1 software remotely from the Optical Network Manager AP
CD-ROM. Perform the upgrade remotely from the Optical Network Manager AP
or
Chapter 4: Load EC-1 software remotely from the Optical Network Manager AP
(ESWD):
– Extract EC-1 software from DAT onto the Optical Network Manager AP
– Schedule EC-1 software delivery from Optical Network Manager AP to EC-1
Perform the upgrade remotely from the Optical Network Manager AP (once the
software is delivered)
You can backout of the EC-1 upgrade now, It is recommended that you commit the
Chapter 8. DO NOT backout if NE upgrade(s) EC-1 upgrade, Chapter 9, BEFORE
are committed as the NEs will not be fully committing NE upgrade(s).
Decide if/how you want to upgrade the NE software (Chapter 5):
Load the NE upgrade software onto the EC-1 platform. There are three
alternative methods:
– Load NE software from the local EC-1 DAT drive, or
– Load NE software remotely from the Optical Network Manager AP (ESWD):
– Extract NE software from DAT onto the Optical Network Manager AP
– Schedule NE software delivery from Optical Network Manager AP to EC-1
– Load NE software from the local EC-1 CD-ROM drive
Download the NE software to the inactive software bank of one or more NEs
using send_ne utility.
Note: you can backout of the NE upgrade at this point: Chapter 6
Activate the new NE software. This puts the downloaded software into the active
software bank of each NE, forcing a warm reboot
You can backout of NE upgrade now, Chapter 6. It is recommended that you commit the
Do so BEFORE you backout of an EC-1 EC-1 upgrade, Chapter 9, BEFORE NE
upgrade (if required). upgrades, Chapter 7.
STOP

1-12 Introduction
Preparing for the upgrade

Before the network can be upgraded a number of precautionary actions must
be performed to ensure that it is in a suitable state for upgrade. Read ALL of
the information in this section and perform all relevant actions before you
continue with the EC-1 or NE upgrade.
Note 1: The installation handbooks for EC-1 R19.1 and each NE type list
the hardware and software supplied and supported by Nortel Networks. If
the network has been modified to include non-standard modules, it is
recommend that EC-1 support staff are notified prior to an upgrade as the
modified network may not be a supported configuration.
CAUTION
OM4100 R4.5: Potential risk of synchronisation loss due to
incorrectly programmed EOS cards
Before upgrading to OM4100 release 4.5, you must run the EOS Inventory
Script to detect incorrectly programmed End of Shelf cards. Failure to
replace affected cards may result in synchronisation problems. For full
details of the problem and how to run the EOS Inventory script refer to
‘Appendix D: Preventing a Sync problem caused by End Of Shelf card
programming’.
The precautionary actions are:

1 Plan the upgrade in advance and time it to coincide with periods of known
low traffic levels on the network. This ensures that if traffic hits occur, they
will not impact a large amount of traffic.
2 The EC-1 installation handbook lists the platforms supported by Nortel
Networks. The upgrade can only be performed on HP B180L, B2600,
C3600, C3750 platforms running HP-UX 11i.
3 The network must be stable and well maintained and it is recommended

that you remove all alarm conditions from the network before commencing
an upgrade. Any intermittent alarms and alarms involving communications
failures must be resolved to prevent network instability during the upgrade.
Note 1: There are a number of alarms that must be cleared before the
network can be upgraded. These are listed in ‘Alarms to clear from the
network before an upgrade’ on page 11-1.
Note 2: When all alarms have been cleared down on a TN-1X R7 NE, it is
necessary to press the Receive and Attention buttons to clear down the
Local Craft Access Panel (LCAP) and Remote Access Unit (RAU) LEDs.
4 The on-site engineer MUST be aware of all user names, passwords and
subnet masks for all NEs and platforms, including Optical Network
Manager Application Platform. Access may be required at all levels of
security. All root user passwords must be known.

Introduction 1-13
5 At the start of an upgrade a configuration freeze must be observed. Any 1

configuration changes made on the Customer platform must occur before
the upgrade commences. Any urgent changes must be noted and
highlighted to the Nortel Networks engineer prior to the upgrade process.
ATTENTION
All Element Controller 15-Minute Performance Monitoring collection
should be turned OFF before starting the upgrade.
6 Check the contents of the host file (/etc/hosts). It should only contain valid
IP addresses with corresponding machine names. Any redundant entries
should be removed before the upgrade begins.
Note: If Optical Network Manager Application Platform is attached, a

Optical Network Manager Application Platform entry may be present in /
etc/hosts. Do not delete this entry.
7 Ensure LAN access points are made available for each LAN port. That is,
LAN0 if no Optical Network Manager Application Platform is supported,
or LAN0 and LAN1 if Optical Network Manager Application Platform is
supported.
8 Before the upgrade is started, the current setting of the sync source
hierarchy should be examined as part of the pre-upgrade network plan.
Each NE currently not on a primary source should be set to primary sync
source.
9 Disable high-order path trace consequent actions on all NEs within the
network. This is currently supported on TN-1X R7, TN-1P R2 and TN-1C
R1, R2 and R3. This ensures there are no high-order path trace alarms left
in the network. Consequent actions can be enabled after the upgrade. If
consequent actions are not disabled before the upgrade, traffic hits and
outages are likely.
10 Ensure the correct TN-1X CAT load image is available for the TN-1X NEs.
This software is only to be used in the event of a failure as directed in the
Failure Recovery section of this document.
11 There must be no CAT terminal operation during the upgrade.
12 A customer engineer must be made available to assist off site recovery

actions. The Nortel support pager number must be known.

1-14 Introduction
13 Release 7 NEs (7.72A/7.72M only) do not retain their data communication

channel (DCC) settings. If an NE has disabled comms channels prior to a
Release 8 NE upgrade, these will be enabled after the upgrade. Care must
be taken to prevent bridging of OSI networks which may result in the loss
of network visibility.
Before an upgrade:
a. On all NEs, identify all comms channel settings which have been
disabled. From a user interface session, perform the following
command:
Config/Comms_management/Lapd_link_service/View ↵
Disabled comms channels, are denoted by both the multiplex section
(MS) and regenerator section (RS) settings being marked as OFF for a
particular slot.
b. For NEs with disabled comms channels, ensure that both ends of the
Synchronous Transport Module (STM) link are disabled. That is,
disable the comms channels in the NE located at the other end of the
STM link.
When booting an NE to Release 8, if the NE has been identified as
previously having its comms channels disabled, ensure that the comms
channel is immediately disabled. To do this, perform the following
command from a user interface session:
Config/Comms_management/Lapd_link_service/Off_auto <slot> ↵
For example:
Off_Auto s6-1 ↵
14 Set designated router information during the upgrade. Refer to the upgrade
procedures of Chapter 2, Chapter 3 and Chapter 4. Further information on
the related osi_comms.conf file is contained in Appendix C. Refer to this
appendix before start the upgrade.
end of chapter

Introduction 1-15

2-1
2
Upgrading EC-1 locally (via CD-ROM) 2-
Overview
The information in this Chapter provides sequential procedures to upgrade a
single EC-1 platform to Release 19.1 The EC-1 software is loaded from a
CD-ROM on the EC-1. The upgrade is then performed locally.
ATTENTION
ALL of the information in this chapter is relevant to the upgrade and it is
important that you follow all the steps in the flowchart shown in Figure 2-1.
Once the upgrade is complete you can continue with a number of options
which include performing NE upgrades. You must also decide whether to
commit to using EC-1 Release 19.1, or to backout of the upgrade, reverting to
the original release of EC-1. The ‘Post upgrade options’ section on Page 2-27
describe the available options.
Note: If you commit to an NE upgrade without first committing to an EC-1

by the EC-1 (with old software). It is strongly recommended that if a
backout of both EC-1 Release 19.1 and NE upgrades is required, the NE
upgrade backout should be performed first.
Additional reference information

Before you start, be aware that, depending on your EC-1 deployment
configuration, you will need to refer to additional procedures from other
handbooks. Check these references NOW, and ensure that you have all the
relevant information to hand:
• ‘Preparation’ section on Page 2-4;

Procedure 2-2, step 1a., b. on page 2-8;
Procedure 2-3, step 2 on Page 2-9; step 15 on Page 2-11;
Refers to disabling and enabling various standby configuration functions
and performing archives. Refer to the procedures in Chapter 10 of the
Optical Network Manager EC-1 User Procedures, 323-1091-402.
• ‘Post upgrade options’ on Page 2-27:
Refers to installing Acrobat Reader 4.0 and the EC-1 on-line handbooks by
following the procedures in Appendix A of the Optical Network Manager
EC-1 Installation Procedures, 323-1091-202.

2-2 Upgrading EC-1 locally (via CD-ROM)

Refers to installing an NCD900XPC X-Terminal for use with Optical
Network Manager EC-1 Release 19.1 by following the procedures in
Chapter 6 of the Optical Network Manager EC-1 Installation Procedures,
323-1091-202.

Figure 2-1
Flowchart - Upgrading to Release 16.2 locally (from the same EC-1 platform)
START
2
Read Chapter 1 to ensure that you have suitable hardware/
software and that your network is in a suitable state for upgrade
Preparation:
– Backup the current release of EC-1 (recommended)
Procedure 2-1
–– Increase the size of the /home partition
(not applicable to some (non-LVM) platform types). Can only be
performed locally at the EC-1 platform:
Procedure 2-2 (backs up the current network configuration
prior to increasing the size of the /home partition)
Procedure 2-3 (increases the size of the /home partition)
– Remove redundant NE loads on any HP platform
Procedure 2-4
– Remove redundant EC-1 loads on any HP platform
Procedure 2-5
– Create required disk space on any HP platform
Procedure 2-6
Load EC-1 software from the local CD-ROM

Procedure 2-7
Set file permissions on EC-1 software

Procedure 2-8
Perform upgrade locally from the EC-1

Procedure 2-9
The main upgrade elements include:
– Disabling the hot-standby function (if used)
– Killing the EC-1 process
– Updating defaults to provide router functionality
STOP
Now refer to Post upgrade options on page 2-27 for

options on how to proceed.
Note: The upgrade of NEs in the network must be performed AFTER the EC-1
upgrade, see Chapter 5. If you commit to an NE upgrade without first committing
to an EC-1 upgrade, the upgraded NEs will not be fully supported by the EC-1.

Preparation
ATTENTION
It is important to follow all of the preparatory procedures described below.
Failure to do so can cause problems during the upgrade.
CAUTION
Warm/hot standby
If a warm/hot standby workstation is installed to protect the EC-1 platform,
this standby platform must be installed before the EC-1 platform is installed.
If you are upgrading either platform in a hot standby configuration, you

must disable the hot-standby function by following Procedure 10-21 of the
Optical Network Manager EC-1 User Procedures, 323-1091-402. This is
not required in a warm standby configuration.
CAUTION
If a secondary warm/hot standby workstation is protecting a primary EC-1
platform, before commencing the upgrade of either system, the primary
EC-1 must be checked to ensure that it is active and associated with the NEs
in its span of control.
The secondary EC-1 must also be checked to ensure that it is inactive.
The primary EC-1 is not active, or has current ‘comms fail’ alarms, or if the
secondary EC-1 is active, the upgrade should be halted until:
• The primary EC-1 is active

• All ‘comms fail’ alarms have been cleared
• The secondary EC-1 is inactive
The active status of an EC-1 can be determined by attempting to log into the
EC-1 application, as described in the EC-1 User Procedures, NTP
323-1091-402. If the EC-1 is inactive, it will not be possible to start an EC-1
session.
Note: If a secondary warm/hot standby workstation is protecting a primary

EC-1 platform, the secondary platform must be upgraded to the new
release prior to the upgrade of the primary EC-1.
Read Chapter 1, ‘Introduction’ to ensure that you have suitable hardware/

software and that your network is in a suitable state for upgrade. For example,
there are a number of alarms that must be cleared before the network can be
upgraded.
At the start of the upgrade process, the EC-1 platform should be managing the
network (unless you are upgrading a standby machine).

Note 1: It is recommended that during an upgrade, the Optical Network

Manager Application Platform Graphical Network Editor (GNE) layout is
unmodified, as there is a possibility that any modifications will be lost. The
Optical Network Manager Application Platform (Optical Network
Manager AP) was formerly known as the Integrated Network Manager
(INM) or Network Resource Manager (NRM). 2
Note 2: Before attempting any upgrade, ensure that:
— PM collection has been turned off.
— The upgrade is performed outside the autobackup period
Before performing the upgrade:
• Make a backup of the current release of EC-1 (Procedure 2-1)
• Increase the size of the /home partition (only applicable to HP platforms
B180L, B2600, C3600, C3750 ) (Procedure 2-2 and Procedure 2-3)
• Remove redundant NE loads from all platform types (Procedure 2-4)
• Remove redundant EC-1 loads from all platform types (Procedure 2-5)
• Create the required disk space on any HP platform (Procedure 2-6)
• Read Appendix B: osi_comms.conf file to check if you need to edit the
osi_comms.conf file during the upgrade procedure.
Chapter 10 provides solutions to a number of problems that can arise during
the EC-1 Release 19.1 upgrade.

Backing up the EC-1 platform prior to upgrade

Archive the EC-1 platform before commencing the upgrade. In the unlikely
event of an error occurring during the procedure, you can use the backup after
performing an EC-1 backout. Appendix A: EC-1 recovery from DAT shows
you how to recover the EC-1 from a backup.
Procedure 2-1
Step Action
1 Log into the EC-1 platform as root user.

2 Open a UNIX window.
3 Place a blank digital audio tape (DAT) in the EC-1 tape drive.
4 Enter the following command in the UNIX window:
cd / ↵
/etc/fbackup -f /dev/rmt/0m -i /etc -i /home -i /usr/users ↵
This archives the EC-1. This operation takes approximately 15 minutes to
complete. Perform this operation before the upgrade process commences.
The fbackup utility warns you about files which are open. For example:
WARNING File number 3239 (/usr/adm/syslog) was active
during attempt1
The fbackup utility retries the file, and backs it up when the file is no longer
active. All such warnings should be ignored.
CAUTION
Restricted utility
The fbackup command does not backup all UNIX files. It backs up /etc, /
home and /usr/users only. If this backup is to be restored (see Appendix A),
the EC-1 platform may need to be rebuilt from HP-UX CD. Acrobat, for
example will need to be re-installed if the EC-1 is rebuilt.
5 Once the backup is complete, remove the DAT from the drive, Write protect
the DAT, and label it. Place the tape in a safe location.
6 At this point you may, if you wish, perform a second system archive thereby
producing a second backup tape of the entire system. This second tape
should be stored in a different location to the first tape.
Note: No configuration modifications should be in operation.
—end—

Increasing the size of the /home partition

Due to the increased functionality in new NE load images in Releases 19.1,
the file sizes of these load images have also increased. For this reason, Nortel
recommends that you increase the size of the /home partition for all HP
B2600, C3600,C3750 platforms being upgraded from releases earlier than 2
Release 16:
• Procedure 2-2: backs up the current network configuration prior to

increasing the size of the /home partition
• Procedure 2-3: increases the size of the /home partition
ATTENTION
Procedure 2-2 and Procedure 2-3 must be performed locally at the EC-1
platform and cannot be performed remotely from the Optical Network
Manager Application Platform.
CAUTION
Potential partial loss of network configuration data
For the duration of Procedure 2-2 and Procedure 2-3, a network
configuration freeze must be observed, otherwise partial loss of
network configuration data may ensue. In all instances
Procedure 2-2 must be applied to back up current network
configuration data, prior to applying Procedure 2-3 to cut over
to any standby platform and increase the size of the /home
partition.
These procedures require that the EC-1 platform be booted into single user
mode. Consequently, the procedure must be run locally at the EC-1 platform
and, in EC-1 'standalone' installations, there will be a loss of network
visibility for the duration of the procedure (approximately 10 minutes). In
EC-1 standby configurations, the procedure should be applied first to the
standby EC-1.
In a hot standby configuration, shutting down the primary EC-1 to

reconfigure it, as detailed in Procedure 2-3, will cause the hot standby EC-1 to
start automatically and assume control of the network.
If it is desired that a warm standby EC-1 assume control of the network,

whilst a primary is being reconfigured, the warm standby system must be
manually activated, as detailed in Procedure 2-3.
For hot and warm standby installations, once the primary EC-1 has been
reconfigured, it is necessary to ensure that control of the network reverts to
the primary EC-1, as detailed in Procedure 2-3.

Procedure 2-2
Backing up the current network configuration prior to increasing the size of
the /home partition
Step Action
1 Back up the current network configuration according to the following criteria:

a. For stand alone and cold standby configurations:
Apply Procedure 10-8, 'Performing an on-line manual archive', of the
Optical Network Manager EC-1 User Procedures, 323-1091-402, to the
active EC-1.
b. For hot standby configurations:
Apply Procedure 10-16, 'Remotely archiving the primary EC
configuration to hot standby', of the Optical Network Manager EC-1 User
Procedures, 323-1091-402, to the active EC-1.
c. For warm standby configurations:
Log into the primary EC-1 as sdhmsusr and, in a shell window, type:
/home/sdhmsusr/sdhms/bin/remote_arch ↵
Log into the warm standby EC-1 as sdhmsusr and, in a shell window
type:
/home/sdhmsusr/sdhms/bin/arch_save ↵
—end—

Procedure 2-3
Step Action
1 Log into the EC-1 platform as user sdhmsusr and open an Xterm window by: 2
a. on a CDE workspace – click on the third icon from the right on the display
bar (a drawer with pencils and so on). In the Application Manager that
opens, double click Desktop tools. Scroll down the Desktop tool screen
and double click on the Xterm icon.
2 At the UNIX prompt in the open xterm window, type:
/home/sdhmsusr/sdhms/bin/killsdhms ↵
When prompted for the 'Enter shutdown reason:' type:
disk reconfig ↵
Note: The EC-1 application will now shut down.
• If the procedure is currently being applied to a primary EC-1 in a hot
standby configuration, the standby system will now activate automatically
and Procedure 10-20 'Switching to a hot standby platform' of Optical
Network Manager EC-1 User Procedures, 323-1091-402, should be
applied at this point.
• If the procedure is currently being applied to a primary EC-1 in a warm
standby configuration, and it is desired that the warm standby system will
control the network during the reconfiguration of the primary EC-1,
Procedure 10-18 'Switching to a warm standby platform' of Optical
• If the procedure is currently being applied to a primary EC-1 in a cold
standby configuration, and it is desired that the cold standby system will
Procedure 10-17 'Switching to a cold standby platform' of Optical
Network Manager EC-1 User Procedures 323-1091-402, should be
Once the cold standby platform is operational, Procedure 10-13
'Restoring data from DAT tape archive' of Optical Network Manager EC-1
User Procedures, 323-1091-402, should be applied to the standby
platform, using the DAT archive created at step 1 of Procedure 2-2.
3 On the EC-1 whose /home partition is being reconfigured, become root user
by typing in the open xterm window:
su - root ↵
When prompted enter the root password for the system and press ↵.
—continued—

Procedure 2-3
Increasing the size of the /home partition (continued)
Step Action
4 Reboot the system by typing:

init 2 ↵
During the reboot, the following messages appear, for example:
To select a new Graphics Monitor Type press the [TAB]
key now, otherwise EXIT by entering other key (or will
timeout in 15 seconds)
5 Log into EC-1 platform as root user.
6 At the # prompt type:
startx ↵
Wait for a few seconds and a UNIX window appears in the top left hand
corner.
sam ↵
The Administration Manager now starts.
8 Double click on Disks and File Systems.
9 Double Click on Logical Volumes. A message appears saying that the
system name is invalid. Select OK. Wait for a few seconds while it scans the
hardware.
The following information appears.
Logical Volume Volume Group Use Total Mbytes Mirror Copies Mount Directory
--------------------------------------------------------
lvol1 vg00 HFS 256 0 /stand

lvol2 vg00 swap/dump 256 0
lvol3 vg00 HFS 1792 0 /
lvol4 vg00 HFS 256 0 /home
10 Select /home line by clicking it with your mouse.

11 From the Main Menu Bar select Actions.
12 From the drop down menu select Increase Size....
A new window appears. This will indicate the free space available to add to
the /home partition. For example:
Space available in volume group (Mbytes): 11764
It also indicates the current space used in the /home partition. For example:
Current logical volume size (Mbytes): 1000
Make a note of the number of megabytes available in the volume group and
the current logical volume, as indicated in this message.
—continued—

Procedure 2-3
Increasing the size of the /home partition (continued)
Step Action
13 Add together the figure given for the space available in the volume group and 2
the figure given for the current logical volume. For example 11764 + 1000 =
12764
Type this new total in the New Size (Mbytes) box, for example:
12764
Select OK.
The new size of /home is now visible in the Logical Volumes window.
14 From the file menu, select Exit to leave the Logical volumes panel and,
again from the file menu, select Exit to leave 'sam'.
15 For hot standby, warm standby and primary EC-1s, at the # prompt type:
/etc/reboot ↵
The Workstation now reboots.
Note: At this point the EC-1 application will start up.
standby configuration, Procedure 10-15 'Restoring data from a hot
standby EC-1 and switching back to primary EC-1' of Optical Network
Manager EC-1 User Procedures, 323-1091-402, should be applied at this
point.
standby configuration, and the warm standby system was controlling the
network during the reconfiguration of the primary EC-1, Procedure 10-19
'Switching back from a warm standby platform' of Optical Network
point.
standby configuration, and the cold standby system was controlling the
'Switching to a cold standby platform' of Optical Network Manager EC-1
User Procedures, 323-1091-402, should be re-applied at this point.
For cold standby EC-1 platforms, at the # prompt type:
/etc/reboot -h ↵
The Workstation now shuts down and can be powered off, when indicated by
the on-screen message.
16 The procedure is complete.
—end—

Removing a redundant NE load image from the EC-1 platform

Procedure 2-4 shows you how to remove a particular NE load from the EC-1
platform, when the NE load is no longer in service in your network.
ATTENTION
It is recommended that Procedure 2-4 is applied for ALL EC-1 platforms as
good housekeeping practice.
Before applying this procedure, you should locate an original copy of the NE
software that is about to be deleted, and store it in a safe place. In this
instance, should it ever become necessary to reload this software, the
procedures for installing an NE load, either from DAT or via ESWD, can be
applied (detailed in Chapter 5).
As a precaution for the loss or corruption of the original, however, Procedure

2-4 makes a backup of the NE load to DAT, so a fresh blank DAT tape will
also be required for each NE load that is to be removed. You must apply this
procedure individually to each NE load that is to be removed from the
platform.
Procedure 2-4
Step Action
1 Log into the EC-1 platform as user sdhmsusr and open an Xterm window by:
2 Load the fresh blank DAT tape into the DAT drive and wait for the lights on
the drive to stop flashing.
—continued—

Procedure 2-4
Removing a redundant NE load image from the EC-1 platform (continued)
Step Action
3 In the UNIX window, check the NE load's details by performing the following 2
command:
ls -la /home/sdhmsusr/sdhms/data/NE_load/* | more ↵
If necessary, press the ↵ key to page through the resulting list of NE software
directories and identify the appropriate software path for the target NE load.
Note: The following software paths and NE loads are examples only.
Use the appropriate paths and loads for your actual configuration.
For example, 16XE (OPTera Metro 4200) Release 1.0 will be listed as follows:
/home/sdhmsusr/sdhms/data/NE_load/16XE:
drwxr-xr-x 2 sdhmsusr sdhms 1024 Jun 18 15:53 H1.01
Make a note of the target NE load's software path and name.
4 Back up the target NE load onto DAT tape by typing a command of the form:
tar cv /home/sdhmsusr/sdhms/data/NE_load/<NE type> <NE load image> ↵
Where <NE_type> is 1X, 1C, 1P, 4T, 4XE (OPTera Metro 4100/OPTera Metro
4150), or 16XE (OPTera Metro 4200) and <NE load image> is the NE
software directory identified at step 3. For example, if 16XE Release 1.0 is the
target NE load, back it up to DAT using the following command:
tar cv /home/sdhmsusr/sdhms/data/NE_load/16XE/H1.01 ↵
CAUTION
Invalid backup if wrong software path used
Be sure to use the full software path, as demonstrated
above. Abbreviating the software path may invalidate
this back up.
When the back up is complete, remove the DAT tape from the drive, label it
clearly with the NE type and NE software release and then store it safely.
5 Remove the target NE load image from the EC-1 platform by typing on a
single line:
rm -rf /home/sdhmsusr/sdhms/data/NE_load/<NE type>/<NE load image> ↵
software directory identified at step 3. For example, if 16XE (OPTera Metro
4200) Release 1.0 is the target NE load, remove it from the EC-1, using the
following command:
rm -rf /home/sdhmsusr/sdhms/data/NE_load/16XE/H1.01 ↵
—end—

Removing redundant EC-1 load images from the EC-1 platform

Prior to any upgrade of the EC-1 software, or as part of general housekeeping
on the EC-1 platform, Nortel Networks recommends that you perform
Procedure 2-5 to remove any redundant EC-1 software loads on the platform.
Note: Before applying this procedure, it is recommended that an original

copy of the current EC-1 software load, is located and stored in a safe
place.
Procedure 2-5
Removing a redundant EC-1 load image from the EC-1 platform
Step Action
1 Ensure that you are logged onto the EC-1 platform as a root user and have
an open Unix window.
2 In the UNIX window, identify all redundant EC-1 load image files, by typing:
find / -name "ec1*" -print ↵
Make a note of the full software path of each EC-1 load image file, identified
by this command, for example:
/tmp/ec161xx_hpp10.TNMS_COMMON.tar.Z
/tmp/ec161xx_hpp10_install.TNMS_COMMON.tar
/tmp/ec161xx_hpp10_install.tar
.
.
.
/eswd/ec161xx_hpp10.TNMS_COMMON.tar.Z
/eswd/ec161xx_hpp10_install.TNMS_COMMON.tar
/eswd/ec161xx_hpp10_install.tar
3 For each EC-1 load image file, identified at step 2, type the following
command:
rm -f <EC-1 tar file> ↵
where <EC-1 tar file> is the full software path, noted at step 2. For example,
to remove all the EC-1 Release 16.1 files listed in step 2, type:
rm -f /tmp/ec161xx_hpp10.TNMS_COMMON.tar.Z ↵
rm -f /tmp/ec161xx_hpp10_install.TNMS_COMMON.tar ↵
rm -f /tmp/ec161xx_hpp10_install.tar ↵
rm -f /eswd/ec161xx_hpp10.TNMS_COMMON.tar.Z ↵
rm -f /eswd/ec161xx_hpp10_install.TNMS_COMMON.tar ↵
rm -f /eswd/ec161xx_hpp10_install.tar ↵
—end—
Note: it is recommended, for good housekeeping practice, that you also

remove any redundant files in the /tmp directory.

Creating the required disk space on any HP platform

Perform Procedure 2-6 to ensure that there is sufficient disk space to perform
the upgrade. This procedure must be performed for all types of Optical
Network Manager EC-1 platform.
Procedure 2-6 2
Creating required disk space on any HP platform
Step Action
1 Ensure that you are logged onto the EC-1 platform as a root user.
In the UNIX window, perform the following command:
bdf /home ↵
The output should be similar to the following:
Filesystem kbytes used avail %used Mounted on
/dev/dsk/c0t5d0 498387 198000 300387 39% /home.
2 For platforms which have logical volume management:(B180L, B2600,
C3600, C3750):
If the ‘avail’ figure is: Then

Above 400,000 step 5
Below 400,000 step 3
—continued—

Procedure 2-6
Creating required disk space on any HP platform (continued)
Step Action
3 Remove old logs:

a. If the customer has a DAT drive connected to the EC-1:
i. In the UNIX window, perform the following command:
cd /home/sdhmsusr/sdhms/logs ↵
ii. If the logs are required to be saved, then insert a DAT into the DAT
drive, and perform the following command:
tar cv * ↵
When complete, remove the DAT and store it safely.
iii. Remove files:
rm -f *.EL *.PL *.GL *.Z ↵
iv. Go to step 4
b. If you do not have a DAT drive connected to the EC-1:
bdf /
/dev/dsk/c0t5d0 1795241 1105895 509821 68% /
If the ‘avail’ figure is: Then perform the following:

above or equal to cd /home/sdhmsusr/sdhms/logs ↵
1,200,000 mv *.EL /tmp ↵
mv *.PL /tmp ↵
mv *.GL /tmp ↵
mv *.Z /tmp ↵
This will preserve all logs and store them in the /tmp directory.
Once the upgrade has been completed and the new EC-1 load
committed these log files can be copied into /home/sdhmsusr/sdhms/
logs. Then Go to step 4.
If the ‘avail’ figure is: Then :

below 1,200,000 There is insufficient disk space to move the
logs to the /tmp directory. Contact Nortel
for Technical Support.
ii. Go to step 5
—continued—

Procedure 2-6
Step Action
4 Perform another disk check. In the UNIX Window, type: 2

bdf /home ↵
For platforms which have logical volume management: (B180L, B2600,
C3600, C3750):

Below 400,000 Contact Nortel Technical
Support
—end—

Loading EC-1 Release 19.1 software onto EC-1

Before an upgrade can be performed, you must load the EC-1 Release 19.1
software onto the EC-1 platform from the local CD-ROM, see Procedure 2-7.
Note: NE software (loaded via DAT) does not have to be loaded at this
time. This can be performed at a later stage (see ‘Loading NE software’ on
page 5-6).
Procedure 2-7
Loading the EC-1 software from CD-ROM
Step Action
1 Ensure that you are logged onto the EC-1 platform as a root user and have
an open UNIX window.
2 Insert the CD-ROM in the drive and type the following commands:
cd /tmp ↵
rm -rf install ↵
3 Check the system to ensure that the CD-ROM/DVD-ROM drive is available
by typing:
ioscan -fnC disk ↵
This command returns a list of disk devices. The CD-ROM/DVD-ROM device
should be in this list e.g. /dev/dsk/cXtXdX (where cXtXdX is the device name
of the CD-ROM/DVD-ROM). Take a note of this device because you must
enter it when mounting the CD-ROM (NTQJ30PH).
4 Create a directory in which you can mount the CD-ROM device by typing:
mkdir /cdrom ↵
5 Mount the CD-ROM onto the /cdrom directory by typing:
mount /dev/dsk/cXtXdX /cdrom ↵
Note: Replace the device name cXtXdX with the result obtained from the
ioscan command above.
6 List the contents of the CD-ROM by typing:
ls /cdrom/EC-1 ↵
This command displays the filename of the file to be loaded, that is:
ec191xx_hpp10_install.tar, where XX is the revision of the file.
7 To decompress and load the file, type the following command:
tar xvf /cdrom/EC-1/ec191xx_hpp10_install.tar ↵
Note: Remember to replace the letters XX with the result obtained from the
ls /cdrom command above.
The contents of the CD-ROM file are loaded into the /tmp/install directory.
—end—

Setting file permissions on EC-1 software

After the EC-1 software has been loaded onto the EC-1 platform, the file
permissions for the EC-1 scripts must be checked. The file permissions of
these scripts are paramount to the success of the upgrade.
Procedure 2-8
2
Checking file permissions for EC-1 software
Step Action
1 Ensure that you are logged into the EC-1 platform as root user and have an
open UNIX window.
2 In the UNIX window type:
chmod 777 /tmp/install ↵
3 Set the EC-1 script permissions by typing:
chown root:sys /tmp/install/* ↵
chmod 755 /tmp/install/* ↵
—end—

Upgrading the EC-1 software to Release 19.1

This section details the EC-1 Release 19.1 upgrade procedure.
This upgrade procedure has been modified from Release 15 to reduce the
need for your interaction when performing the upgrade. Please note that this
feature is not entirely hands-free. You still have to provide some input.
However this is mainly at the beginning of the upgrade script.
CAUTION

session.

If a warm/hot standby workstation is to protect the EC-1 platform, first

upgrade the warm/hot standby EC-1, then upgrade the active EC-1. Use this
procedure to upgrade the warm/hot standby first.
The EC-1 upgrade procedure is performed by the Upgrade_EC1 script.
If no errors occur, the upgrade script continues executing until completed.
The upgrade script exits on failure of a test condition. The reason for the
failure is displayed on the screen, allowing you the opportunity to take
appropriate action.
The upgrade script exits if it is interrupted. A re-run of the script is required to

return to the same point in the upgrade process.

Procedure 2-9
Step Action
1 Ensure that you are logged into the EC-1 platform as root user. Open an 2
xterm from an existing UNIX window by entering the following command.
xterm -l -lf /tmp/up_log & ↵
This command opens a window and logs every action performed within this
window into a log file. This log file (up_log) is stored in the upgrades
directory.
2 Select the new xterm window with the mouse.
3 In the new window, change into upgrade directory:
cd /tmp/install ↵
4 Start the upgrade process by entering the following command:
./Upgrade_EC1
5 Then script checks if the previous release has been committed. If the
previous release has not been committed there will be a warning message
prompting the user to commit the release.
EC-1 Release 181xx has not been committed
It will not be possible to continue with the upgrade until the
commit has been complted successfully.
To commit R181x:
1: run the script /home/sdhmsusr/sdhms/bin/Commit_EC1
2: rerun this script (Upgrade_EC1)
Leaving Upgrade_EC1 with failure.
6 The script begins by telling you the location of the log files, the current EC-1
version and the upgrade version.
The script then determines if any alarms are current on the EC-1,
and this information is reported. For example:
**********************************************
* *
* WARNING!!! *
* *
**********************************************
There are 14 alarms currently outstanding.
Key TOP NE Object AlarmType
1 51:1 50:5004 50:5004 NE-Card_Fail
2 51:1 50:5004 50:5004 NE-Wrong_Card

3 51:1 50:5004 50:5004 NE-Card_Out
4 51:1 50:5004 50:5004 NE-Card_Out
5 51:1 50:5004 50:5004 NE-Card_Out
6 51:1 50:5004 50:5004 NE-Card_Out
7 51:1 50:5004 50:5004 NE-Card_Out
8 51:1 50:5004 50:5004 NE-Card_Out
9 51:1 50:5004 50:5004 SYNC-Src_Not_Primary
Continued on next page
10 51:1 50:5004 50:5004 SYNC-SETG_holdover
11 51:1 50:5004 50:5004 RS-LOS
12 51:1 50:5004 50:5004 OS-Laser_Shutdown
13 51:1 50:5004 50:5004 LP-SF
14 30:1 32:5007 32:5007 Comms fail alarm
A list of alarms is included in the back of the upgrade document.

Before running this script the EC-1 must be free from alarms that
may affect the upgrade process.
7 A check is made for the diskspace available.
If there is not enough diskspace for the installation the upgrade is
discontinued. Within Optical Network Manager EC-1 Upgrade
Procedures, 323-1091-230 check Procedues 2-5 and 2-6 to remove
redundant NE and EC-1 load images.
—continued—

Procedure 2-9
Upgrading the EC-1 software to Release 19.1 (continued)
Step Action
8 If there is adequate diskspace you are asked: 2

Do you wish to perform the upgrade from CD-ROM? [y/n]
If you wish to upgrade from tar files type n
9 The script displays what packages the directory contains.
Directory /tmp contains the following s/w packages:
1. EC-1 Common Software TNMS_EC-1.191.xx
It then asks you:
Do you wish to install Package 1 {y/n]?
10 Enter y to continue. If you choose not to continue (by entering n (No) to the
above prompt), the script displays a message and exits. If you choose to
continue the script then displays the following information:
INSTALL: Commencing installation of package 1: EC-1
Common Software (TNMS_COMMON) version TNMS_EC-1.191.xx
INSTALL: Commencing installation of TNMS_COMMON TNMS_EC-1.191.xx
INSTALL: configured for HP-UX V11

11 You are now asked:
Do you want to make the system secure [y/n]?
Make your choice. Either:
a. Select n (No). The following message appears:
INSTALL: System is now INSECURE
b. Select y (Yes). The following message appears:
INSTALL: System is now SECURE
—continued—

Procedure 2-9
Step Action
12 Upon selecting security mode, the upgrade script displays the following
information.
INSTALL: Creating a new DB file in /home/upgrade/sdhms/data/dbase
INSTALL: Exporting R191 CRD file
INSTALL: Importing new DB file

INSTALL: Installing alarm aoieqt.text file
INSTALL: Installing aoitrat.text file
INSTALL: Installing aoienvt.text file
INSTALL: Installing new Template data file
INSTALL: Installing new Translator data file
CHANGE_PRIV: Setting privileges on programs:

CHANGE_PRIV: Checking log directories
Main Log directory exists
Enquiry Library Log directory does not
exist - creating it
INSTALL: Please select the EC-1 operating mode from

the following list:
1. Active EC-1 Standalone (no remote backups)

2. Active EC-1 backing up to RCA
3. Active EC-1 backing up to Warm standby
4. Active EC-1 backing up to Hot standby
5. Cold standby EC-1

6. Warm standby EC-1
7. Hot standby EC-1
Option [1-7]?
—continued—

Procedure 2-9
Step Action
13 If the active EC is protected by a standby, the standby workstation must be 2

upgraded before the active one. Select option 5, 6 or 7 for the standby
workstation. When repeating this procedure for the active workstation, select
option 2, 3 or 4. For a stand-alone, there is no backup, so that the procedure
is carried out only once.
a. Select cold, warm or hot standby by typing 5↵, 6↵ or 7↵ respectively.
The following message appears:
INSTALL: Disabling EC startup
INSTALL: Enter hostname of next active EC-1 or press
[ENTER] for no more.
Enter the hostname of the active EC-1
Enter the IP address for <hostname of active EC-1>
Enter the IP address.
<hostname of active EC-1> is already in /etc/hosts.
No change will be made.

Press Enter for no more.
Continue to step 15.
b. Enter 2↵, 3↵ or 4↵
If option 3 or 4 is selected, the following message appears:
Enter hostname of standby EC-1
If option 2 is selected, the following message appears:
Enter hostname of RCA
Enter the hostname of the remote central archive (RCA).
INSTALL: Enter the IP address of <hostname of standby>
Comms checked to <IP address of standby EC-1>
<hostname of standby> is already in /etc/hosts.
14 Enter 1↵
—continued—

Procedure 2-9
Step Action
15 The following message appears:

INSTALL: Building new HP-UX V11 kernel.
Note: The user will see a message indicating kernel completion.

****Preparation of new kernel completed sucessfully at xxxx ***.
16 The script then displays the following information:
INSTALL: Installation of package - TNMS_COMMON TNMS_EC-1.191.xx
complete.
INSTALL: FTPD update not required

Enquiry Library Log directory exists
The script then updates all EC-1 users.
hci_upgrade_users - Upgrading the configuration of all

EC-1 management users
syseng01
admin
netsurv
slat
master
operator
The script then displays the following information:
TNMS EC1 Upgrade Procedure has completed successfully

Note: At this point the EC-1 platform will perform a cold restart to start the
new EC-1 load.
17 The procedure ends.
—end—

Post upgrade options

After you have upgraded EC-1 to Release 19.1, there are several possible
courses of action:
2
• The NEs within the network can be upgraded, if required (see Chapter 5,
‘Upgrading NE software’).
• You can install Acrobat Reader 4.0 and the EC-1 on-line handbooks. This
can only be done from a locally mounted CD-ROM. Refer to Appendix A
of Optical Network Manager EC-1 Installation Procedures, 323-1091-202
for full details.
• You can decide to commit to EC-1 Release 19.1. This removes the original
release of EC-1 permanently (see Chapter 9, ‘Committing to an EC-1
upgrade’).
Note: You can configure the EC-1 for OSI over IP ‘Tunnelling’ by editing
the osi_comms.conf file (only after the upgrade has been committed).
Refer to the Optical Network Manager EC-1 User Procedures
323-1091-402 for further information on how to configure this facility.
• Following removal of the original release, if the EC-1 is managed by a

Optical Network Manager Application Platform, perform the post upgrade
procedure . Do not perform this procedure if the EC-1 is not managed by
a Optical Network Manager Application Platform.
• You can decide to backout of using EC-1 Release 19.1. This removes
Release 19.1 from the system, and reinstates the original release of EC-1
(see Chapter 8, ‘Backing out of an EC-1 upgrade’).
• The EC-1 R19.1 software can be used normally, until a decision is made
whether to commit or backout.
• You can install a NCD900XPC X-Terminal for use with Optical Network
Manager EC-1 Release 19.1 Refer to Chapter 6 of Optical Network
Manager EC-1 Installation Procedures, 323-1091-202 for full details.
end of chapter


3-1
Upgrading EC-1 from the Optical

Network Manager Application Platform 3
(CD-ROM) 3-
Overview
single EC-1 platform to Release 19.1. This upgrade is performed via a remote
telnet session from the Optical Network Manager Application Platform as
follows:
• Delivery of EC-1 software is from a CD-ROM mounted on the Optical
Network Manager Application Platform.
• The upgrade is performed from the Optical Network Manager Application
Platform via a telnet session, upgrading from the tar files in the /tmp
directory of the EC-1.
CAUTION
Some procedures MUST be performed locally at the EC-1
Procedure 3-3 and Procedure 3-4 show how to increase the size of the EC-1
/home partition. These procedures MUST be performed locally at the EC-1
ATTENTION
which include performing NE upgrades.
You must also decide whether to commit to using EC-1 Release 19.1, or to
backout of the upgrade, reverting to the original release of EC-1. The ‘Post
upgrade options’ section on Page 3-29 describe the available options.


3-2 Upgrading EC-1 from the Optical Network Manager Application Platform (CD-ROM)


Refers to installing a NCD900XPC X-Terminal for use with Optical
323-1091-202.

Upgrading EC-1 from the Optical Network Manager Application Platform (CD-ROM) 3-3
Figure 3-1
Flowchart - Upgrading to Release 19.1 from the Optical Network Manager
START
Read Chapter 1 to ensure that you have suitable hardware/

software and that your network is in a suitable state for upgrade
Preparation:
– Logon to the EC-1 remotely via a telnet session from the Optical
3
Network Manager AP
Procedure 3-1
Procedure 3-2
– Increasing the size of the /home partition
Procedure 3-5
Procedure 3-6
Procedure 3-7
Load EC-1 software from the Optical Network Manager AP

CD-ROM Procedure 3-8
Perform upgrade from the Optical Network Manager AP

Procedure 3-9
– Updating defaults to provide router functionality
STOP
Now refer to Post upgrade options on page 3-29 for options on

how to proceed.

Preparation
ATTENTION
CAUTION
Warm/hot standby

CAUTION

session.


upgraded.
You must know the IP addresses of both the EC-1 and the Optical Network
Manager Application Platform HP-UX workstations to telnet from the

Optical Network Manager Application Platform workstation to the EC-1

workstation.

(INM) or Network Resource Manager (NRM).
Note 2: Before attempting any upgrade, ensure that: 3
Before performing the upgrade:
• You need to remotely log onto the EC-1 via a telnet session as a root user
from the Optical Network Manager Application Platform (Procedure 3-1)
B180L, B2600, C3600, C3750) (Procedure 3-3 and Procedure 3-4). You
can only perform these procedures locally at the EC-1 platform: not
remotely from the Optical Network Manager Application Platform
• Remove redundant NE loads from your platform (Procedure 3-5)
• Remove redundant EC-1 loads from your platform (Procedure 3-6)
• Create the required disk space on any EC-1 HP platform (Procedure 3-7)

the EC-1 upgrade.

Logging onto the EC-1 platform remotely (from the Optical Network
Manager AP)
Procedure 3-1 shows you how to remotely log onto the EC-1 via a telnet
session as a root user from the Optical Network Manager Application
Platform. Step 6 shows you how to open an xterm window (if required).
Procedure 3-1
AP)
Step Action
1 Logon to the Optical Network Manager Application Platform as a

<username> user (usually a root user).
3 Enter the command:
xhost <ip address of EC-1> ↵
telnet <ip address of EC-1> ↵
If prompted, enter root as the username, and the appropriate password.
5 You are now logged onto the EC-1. Enter the commands:
DISPLAY=<ip address of Optical Network Manager AP>:0.0 ↵
export DISPLAY ↵
You are now remotely logged onto the EC-1 via a telnet session as a root
user from the Optical Network Manager AP.
6 If you need to open an xterm window from an existing UNIX window, enter the
following command.
directory.
Select the new xterm window with the mouse to activate the window.
You are now ready to use the new xterm window.
—end—


event of an error occurring during the procedure, the backup can be used after
an EC-1 backout has been performed. Appendix A shows you how to recover
the EC-1 from a backup.
CAUTION
Problems with external DAT drives
This backup procedure will only backup the EC-1 platform to an internal
DAT drive local to the EC-1.
3
All EC-1 platforms should have an internal digital audio tape (DAT) drive.
External DAT drives may have a different SCSI number (as selected by the
DIP switch on the back of the external DAT drive, for example: 3 instead of
0). Also, tape device special files can vary widely in UNIX. For example the
external device used in the example above might be /dev/rmt/3mn.
Contact Nortel Networks Technical Support if problems occur. Also, UNIX

Manual pages are available, for example: man mt, man 7 mt, which help to
explain this topic.
Procedure 3-2
Step Action
1 Ensure that you are still logged into the Optical Network Manager platform as
root, you have a current telnet session with the EC-1 and have an open UNIX
window and xterm window (as shown in Procedure 3-1).
2 Check that there is a blank, re-wound DAT in the EC-1 internal DAT tape drive
by entering the following command in the xterm window:
mt -t /dev/rmt/0m rew ↵
If the DAT is not present, the following error message appears:
/dev/rmt/0mn: No such device or address
If this error message appears, you must make arrangements to ensure that a
re-wound DAT is inserted in the EC-1 DAT drive.
—continued—

Procedure 3-2
Backing up the EC-1 platform prior to upgrade (continued)
Step Action
3 Enter the following command in the xterm window:

cd / ↵
complete. Perform this operation before the upgrade process commences.
during attempt1
CAUTION
Restricted utility
home and /usr/users only. If this backup is to be restored the EC-1 platform
may need to be rebuilt from HP-UX CD. Acrobat, for example, will need to
be reinstalled if the EC-1 is rebuilt.
4 Once the backup is complete, ensure that the DAT is removed from the EC-1
DAT drive, is write-protected and labelled. Place the tape in a safe location.
—end—


Due to the increased functionality in new NE load images for Releases 16
onwards, the file sizes of these load images have also increased. For this
reason, Nortel Networks recommends that you increase the size of the /home
partition for all HP B180L, B2600, C3600 , C3750 platforms being upgraded
from releases earlier than Release 16. Perform the following procedures:
•
Procedure 3-4: increases the size of the /home partition
3
ATTENTION
CAUTION
configuration freeze must be observed, otherwise partial loss of network
configuration data may ensue. In all instances Procedure 3-3 must be
applied to back up current network configuration data, prior to applying
Procedure 3-4 to cut over to any standby platform and increase the size of
the /home partition.
visibility for the duration of the procedure (approximately 10 minutes).
In EC-1 standby configurations, the procedure should be applied first to the

standby EC-1.

reconfigure it, as detailed in Procedure 3-4, will cause the hot standby EC-1 to
start automatically and assume control of the network. If you want a warm
standby EC-1 to assume control of the network, whilst a primary is being
reconfigured, the warm standby system must be manually activated, as
detailed in Procedure 3-4.
reconfigured, it is necessary to ensure that control of the network reverts to
the primary EC-1, as detailed in Procedure 3-4.
Procedure 3-3
the /home partition (locally, at the EC-1)
Step Action


active EC-1.
type:
—end—

Procedure 3-4
Increasing the size of the /home partition (locally, at the EC-1)
Step Action
1 Log into the EC-1 platform (locally, at the EC-1 platform) as user sdhmsusr
and open an xterm window by double clicking on the VUE menu bar's
'Toolbox' icon and selecting General -> Utilities -> xterm.
/home/sdhmsusr/sdhms/bin/killsdhms ↵ 3
disk reconfig ↵
su - root ↵
init 2↵
During the reboot, you will see messages similar to this:
To select a new Graphics Monitor Type press the [TAB]
key now, otherwise EXIT by entering other key (or will
timeout in 15 seconds)
—continued—

Procedure 3-4
Increasing the size of the /home partition (locally, at the EC-1) (continued)
Step Action

startx ↵
corner.
sam ↵
9 Double Click on Logical Volumes. A message will appear saying that the
hardware.
LogicalVolume Volume Group Use Total Mbytes Mirror Copies MountDirectory
---------------------------------------------------------------------

lvol3 vg00 HFS 1792 0 /

It will also indicate the current space used in the /home partition. For
example:
13 Add together the figure given for the space available in the volume group and
12764
Type this new total in the 'New Size (Mbytes)' box, for example:
12764
Select OK.
14 From the File menu, select Exit to leave the Logical volumes panel and,
again from the file menu, select Exit to leave 'sam'.
—continued—

Procedure 3-4
Step Action
/etc/reboot ↵
3
point.
point.
/etc/reboot -h ↵
—end—


ATTENTION

procedure individually to each NE load to be removed from the platform.
Procedure 3-5
Step Action
1 Ensure that you are logged into the Optical Network Manager platform as
3 In the UNIX window, check the NE load's details by performing the following
command:
4 Back up the target NE load onto DAT tape by typing on one line a command
of the form:
tar cv /home/sdhmsusr/sdhms/data/NE_load/<NE type>/<NE load
image> ↵

CAUTION
Invalid backup if wrong software path used
this back up.
3
single line:
rm -rf /home/sdhmsusr/sdhms/data/NE_load/<NE type>/<NE load
image> ↵
Where <NE type> is 1X, 1C, 1P, 4T, 4XE (OPTera Metro 4100/OPTera Metro
following command:
—end—


on the EC-1 platform, Nortel recommends that you perform Procedure 3-6 to
remove any redundant EC-1 software loads on the platform.

place.
Procedure 3-6
Step Action
.
.
.
command:
—end—

remove any redundant files in the EC-1 /tmp directory.


the upgrade. This procedure must be performed for all types of HP EC-1
platform.
Procedure 3-7
Step Action
3
bdf /home ↵
/dev/dsk/c0t5d0 498387 198000 300387 39% /home
C3600, C3750):

—continued—

Procedure 3-7
Step Action
3 Remove old logs:

a. If you have a DAT drive connected to the EC-1:
ii. If the logs are required to be saved, then insert a DAT into the DAT
tar cv * ↵
iii. Remove files:
rm -f *.EL *.PL *.GL *.Z ↵
iv. Go to step 4
bdf /
/dev/dsk/c0t5d0 1795241 1105895 509821 68% /

1,200,000 mv *.EL /tmp ↵
mv *.PL /tmp ↵
mv *.GL /tmp ↵
mv *.Z /tmp ↵
logs. Then go to step 4.

ii. Go to step 5
—continued—

Procedure 3-7
Step Action
4 Perform another disk check. In the UNIX Window, type:

bdf /home ↵
For platforms which have logical volume management: (B180L, B2600,
C3600, C3750, C8000):

3
Below 400,000 Contact Nortel Networks
Technical Support
—end—

Loading EC-1 software from a CD-ROM on the Optical Network

Manager Application Platform
Before an upgrade can be performed, you must load the EC-1 Release 19.1
software onto the EC-1 platform. Procedure 3-8 shows you how to load the
EC-1 software from a CD-ROM mounted remotely on the Optical Network
Note 1: You must have the IP address of the EC-1 so that you can establish
an ftp session with the EC-1. You must also have root access privileges.
Note 2: NE software (loaded via separate DAT(s)) does not have to be
loaded at this time. This can be performed at a later stage (see ‘Loading NE
software’ on page 5-6).
Procedure 3-8
Loading EC-1 Release 19.1 from a CD-ROM mounted on the Optical Network
Step Action
1 Log onto the Optical Network Manager Application Platform as root user.
Open an xterm window.
2 Check the system to ensure that the CD-ROM/DVD-ROM drive is available
by typing:
This command returns a list of disk devices. The CD-ROM /DVD-ROM device
should be in this list e.g. /dev/dsk/cXtXdX (where cXtXdX is the device name
of the CD-ROM). Take a note of this device because you must enter it when
mounting the CD-ROM (NTQJ30PH).
3 Create a directory in which you can mount the CD-ROM device by typing:
mkdir /cdrom ↵
4 Mount the CD-ROM onto the /cdrom directory by typing:
Note: Replace the device name cXtXdX with the result obtained from the
ioscan command above.
5 Telnet into the EC-1 as root user by typing:
telnet <IP address of EC-1> ↵
cd /tmp ↵
rm ec<XXX>* ↵
(where XXX is the previous EC-1 load)
6 Now type the following commands:
rm -rf install ↵
This removes the previous install directory.
—continued—

Procedure 3-8
Loading EC-1 Release 19.1 from a CD-ROM mounted on the Optical Network
Manager Application Platform (continued)
Step Action
7 Type the following commands to establish an ftp session to the Optical

Network Manager Application Platform:
Note: Login to the Optical Network Manager Application Platform as root
user
ftp <IP address of Optical Network Manager AP> ↵
3
cd /cdrom/EC-1 ↵
mget *.* ↵
bye ↵
This extracts the three ec191xx_ files required for the upgrade (where XX is
the revision of the file).
8 Check that the three files have been placed in the /tmp directory by typing:
ls /tmp ↵
This command displays the filename of the file to be loaded, i.e.
ec191xx_hpp10_install.tar, where XX is the revision of the file.
9 Decompress and load the file by typing:
tar xvf ec191xx_hpp10_install.tar ↵
Note: XX denotes the revision of the file.
10 The EC-1 software tar files are now in the /tmp directory on the EC-1. They
are now available for use during the upgrade procedure described in the
EC-1 software upgrade procedure.
Note: before you perform the EC-1 software upgrade described in Procedure
3-9, you must set the file permissions for the EC-1 software as described in
the following steps:
13 You can now proceed to Upgrading the EC-1 software to Release 19.1 on
Page 3-22.
—end—


This section details the EC-1 Release 19.1 upgrade procedure, carried out
from the Optical Network Manager Application Platform via a telnet session.
The EC-1 software files are accessed from the /tmp directory on the EC-1.
This upgrade procedure was modified for Release 16 to reduce the need for
your interaction when performing the upgrade. Please note that this feature is
not entirely hands-free. You still have to provide some input. However this is
mainly at the beginning of the upgrade script.

failure appears on the screen, allowing you the opportunity to take appropriate
action.
If the upgrade script exits if it is interrupted. A re-run of the script is required

to return to the same point in the upgrade process.

Procedure 3-9
Step Action
root, you have a current telnet session with the EC-1 and have an open xterm
window (as shown in Procedure 3-1).
2 In the xterm window, change into upgrade directory:
cd /tmp/install ↵ 3
3 Start the upgrade process using the tar files that are in the /tmp directory by
entering the following command:
./Upgrade_EC1
4 The script checks if the previous release has been committed. If the previous
release has not been committed there will be a warning message prompting
the user to commit the release.
EC-1 Release 181x has not been committed
To commit R181x:
The script then determines if any alarms are current on the EC-1, and this
information is reported. For example:
**********************************************
* *
* WARNING!!! *
* *
**********************************************
1 51:1 50:5004 50:5004 NE-Card_Fail
2 51:1 50:5004 50:5004 NE-Wrong_Card
3 51:1 50:5004 50:5004 NE-Card_Out

4 51:1 50:5004 50:5004 NE-Card_Out
5 51:1 50:5004 50:5004 NE-Card_Out
6 51:1 50:5004 50:5004 NE-Card_Out
7 51:1 50:5004 50:5004 NE-Card_Out
8 51:1 50:5004 50:5004 NE-Card_Out
Continued on next page
11 51:1 50:5004 50:5004 RS-LOS
13 51:1 50:5004 50:5004 LP-SF
14 30:1 32:5007 32:5007 Comms fail alarm
A list of alarms is included in the back of the upgrade

document. Before running this script the EC-1 must be free
from alarms that may affect the upgrade process.
6 A check is made for the diskspace available.
—continued—

Procedure 3-9
Step Action
7 The first question you are asked is:

3
It then asks you:
Do you wish to install Package 1 {y/n]?

—continued—

Procedure 3-9
Step Action
information.


exist - creating it

the following list:


7. Hot standby EC-1
Option [1-7]?
—continued—

Procedure 3-9
Step Action
12 If the active EC is protected by a standby, you MUST upgrade the standby

workstation before the active one. Select option 5, 6 or 7 for the standby
3

Go to step 14.
b. Enter 2↵, 3↵ or 4↵
Go to step 14.
13 Enter 1↵
—continued—

Procedure 3-9
Step Action

****Preparation of new kernel completed sucessfully at xxxx ***
complete.


syseng01
admin
netsurv
slat
master
operator
new EC-1 load.
—end—


courses of action:
the NEs will not be fully supported by the old release of EC-1. 3
for full details.
upgrade’).

procedure. Do not perform this procedure if the EC-1 is not managed by a
Optical Network Manager Application Platform.
• You can install a NCD900XPC X-Terminal for use with Optical Network
Manager EC-1 Release 19.1. Refer to Chapter 7 of Optical Network
end of chapter


4-1
Upgrading EC-1 from the Optical

Network Manager platform (using
ESWD) 4-
Overview 4
single EC-1 platform to Release 19.1. This upgrade is performed via a remote
telnet session from the Optical Network Manager Application Platform as
follows:
• Delivery of the EC-1 software to the EC-1 is performed using Electronic
Software Download (ESWD) which uses the Optical Network Manager
Application Platform Centralised Software Management (CSM) facility.
— The EC-1 software is first extracted from DAT onto the Optical
Network Manager Application Platform
— The EC-1 software is delivered from the Optical Network Manager
Application Platform to a /tmp directory on the EC-1 via a telnet
session
Note: The delivery of NE load images CAN also be performed using this
type of procedure. Delivery of NE load images are described in Chapter 5.
• The upgrade is performed from the Optical Network Manager Application

Platform via a telnet session, upgrading from the tar files in the /tmp
directory of the EC-1.
CAUTION
Some procedures MUST be performed locally at the EC-1
Procedure 4-3 and Procedure 4-4 show how to increase the size of the EC-1
/home partition. These procedures MUST be performed locally at the EC-1
ESWD provides a mechanism to store EC-1 and NE software releases on the

Optical Network Manager Application Platform and to electronically transfer
those releases to any EC-1 monitored by the Optical Network Manager
Application Platform.

4-2 Upgrading EC-1 from the Optical Network Manager platform (using ESWD)
Once the software release is delivered, you can log in and upgrade the EC-1
and associated NEs in the network. The software release must be delivered to
the EC-1 before the upgrade can be performed.
The software management tasks described in this section can be performed

only on EC-1 platforms running a software release that supports CSM. For
more information, see the Optical Network Manager Application Platform
Introduction, 450-3101-100 (see ‘Associated documentation’ on page xvi).
ATTENTION
which include performing NE upgrades. You must also decide whether to
commit to using EC-1 Release 19.1, or to backout of the upgrade, reverting to
the original release of EC-1. The ‘Post upgrade options’ section on Page 4-35
describe the available options.



Refers to installing a NCD900XPC X-Terminal for use with Optical
323-1091-202.

Upgrading EC-1 from the Optical Network Manager platform (using ESWD) 4-3
Figure 4-1
Flowchart - Upgrading to Release 19.1 from the Optical Network Manager (using ESWD)
START
Read Chapter 1 to ensure that you have suitable hardware/software
and that your network is in a suitable state for upgrade
Preparation:
– Logon to the EC-1 remotely via a telnet session from the Optical Network
Manager AP
Procedure 4-1
Procedure 4-2
– Increasing the size of the /home partition
4
Procedure 4-5
Procedure 4-6
Procedure 4-7
Load EC-1 software remotely from the Optical Network Manager AP:
– Extract EC-1 software from DAT onto the Optical Network Manager AP
Procedure 4-8
– Schedule EC-1 software delivery from Optical Network Manager AP to
EC-1 (ESWD)
Procedure 4-9
– Delete EC-1 software from Optical Network Manager AP once no longer
required
(can be performed at a later date)
Procedure 4-10
Perform upgrade (once EC-1 software is delivered) from the Optical

Network Manager AP
Procedure 4-11
– Setting file permissions on EC-1 software
STOP
Now refer to Post upgrade options on page 4-35 for options on how to

Preparation
ATTENTION
CAUTION
Warm/hot standby

CAUTION

session.


upgraded.
You must know the IP addresses of both the EC-1 and the Optical Network
Manager Application Platform HP-UX workstations to allow you to telnet

from the Optical Network Manager Application Platform workstation to the

EC-1 workstation.

(INM) or Network Resource Manager (NRM).
Note 2: Before attempting any upgrade, ensure that:
Before performing the upgrade: 4
• You need to remotely log onto the EC-1 via a telnet session as a root user
from the Optical Network Manager Application Platform (Procedure 4-1)
B180L, B2600, C3600, C3750) (Procedure 4-3 and Procedure 4-4). These
procedures can ONLY be performed locally at the EC-1 platform and
cannot be performed remotely from the Optical Network Manager
Application Platform
• Remove redundant NE loads from all platform types (Procedure 4-5)
• Remove redundant EC-1 loads from all platform types (Procedure 4-6)
• Create the required disk space on any EC-1 HP platform (Procedure 4-7)


Logging onto the EC-1 platform remotely (from the Optical Network
Manager AP)
Procedure 4-1 shows you how to remotely log onto the EC-1 via a telnet
session as a root user from the Optical Network Manager Application
Platform. The last step in the procedure shows you how to open an xterm
window (if required).
Procedure 4-1
AP)
Step Action
1 Logon to the Optical Network Manager Network Manager as a <username>

user (usually a root user).
xhost <ip address of EC-1> ↵
telnet <ip address of EC-1> ↵
If prompted, enter root as the username, and the appropriate password.
5 You are now logged onto the EC-1. Enter the commands:
DISPLAY=<ip address of Optical Network Manager AP>:0.0 ↵
export DISPLAY ↵
You are now remotely logged onto the EC-1 via a telnet session as a root
user from the Optical Network Manager AP.
6 If you need to open an xterm window from an existing UNIX window, enter the
following command.
directory.
Select the new xterm window with the mouse to activate the window.
You are now ready to use the new xterm window.
—end—


event of an error occurring during the procedure, the backup can be used after
an EC-1 backout has been performed. Appendix A: EC-1 recovery from DAT
shows you how to recover the EC-1 from a backup.
CAUTION
Problems with external DAT drives
This backup procedure will only backup the EC-1 platform to an internal
DAT drive local to the EC-1.
All EC-1 platforms should have an internal digital audio tape (DAT) drive.
External DAT drives may have a different SCSI number (as selected by the
DIP switch on the back of the external DAT drive, for example, 3 instead of
0). Also, tape device special files can vary widely in UNIX. For example the
external device used in the example above might be /dev/rmt/3mn. 4
Contact Nortel Networks Technical Support if problems occur. Also, UNIX
Manual pages are available, for example: man mt, man 7 mt, which help to
explain this topic.
Procedure 4-2
Step Action
2 Check that there is a blank, re-wound DAT in the EC-1 internal DAT tape drive
by entering the following command in the xterm window:
mt -t /dev/rmt/0m rew ↵
If the DAT is not present, the following error message appears:
/dev/rmt/0mn: No such device or address
If this error message appears, you must make arrangements to ensure that a
re-wound DAT is inserted in the EC-1 DAT drive.
—continued—

Procedure 4-2
Backing up the EC-1 platform prior to upgrade (continued)
Step Action
3 Enter the following command in the xterm window:

cd / ↵
complete. This operation should be performed before the upgrade process
commences.
during attempt1
CAUTION
Restricted utility
home and /usr/users only. If this backup is to be restored the EC-1 platform
may need to be rebuilt from HP-UX CD. Acrobat, for example, will need to
be reinstalled if the EC-1 is rebuilt.
4 Once the backup is complete, ensure that the DAT is removed from the EC-1
DATdrive, is write-protected and labelled. Place the tape in a safe location.
—end—


Due to the increased functionality in new NE load images for Releases from
16 onwards, the file sizes of these load images have also increased. For this
reason, Nortel Networks recommends that you increase the size of the /home
partition for all HP B180L, B2600 C3600, C3750 platforms being upgraded
from releases earlier than Release 16. Perform the following procedures:

• Procedure 4-4: increases the size of the /home partition
ATTENTION
platform and cannot be performed remotely from the Optical Network 4
CAUTION
configuration freeze must be observed, otherwise partial loss of network
configuration data may ensue. In all instances Procedure 4-3 must be
applied to back up current network configuration data, prior to applying
Procedure 4-4 to cut over to any standby platform and increase the size of
the /home partition.
visibility for the duration of the procedure (approximately 10 minutes).
In EC-1 standby configurations, apply the procedure first to the standby EC-1.

reconfigure it, as detailed in Procedure 4-4, causes the hot standby EC-1 to
start automatically and assume control of the network.
If you want a warm standby EC-1 to assume control of the network, whilst a
primary is being reconfigured, activate the warm standby system manually, as
detailed in Procedure 4-4.
reconfigured, ensure that control of the network reverts to the primary EC-1,
as detailed in Procedure 4-4.
Procedure 4-3
the /home partition (locally, at the EC-1)
Step Action


active EC-1.
type:
—end—

Procedure 4-4
Increasing the size of the /home partition (locally, at the EC-1)
Step Action
1 Log into the EC-1 platform as user sdhmsusr and open an Xterm window by:
/home/sdhmsusr/sdhms/bin/killsdhms ↵
disk reconfig ↵ 4
su - root ↵
—continued—

Procedure 4-4
Step Action

init 2↵
startx ↵
corner.
sam ↵
9 Double Click on Logical Volumes. A message will appear saying that the
hardware.
LogicalVolume VolumeGroup Use Total Mbytes MirrorCopies Mount Directory
---------------------------------------------------------------------

lvol3 vg00 HFS 1892 0 /

It will also indicate the current space used in the /home partition. For example:
—continued—

Procedure 4-4
Step Action
13 Add together the figure given for the space available in the volume group and
12764
Type this new total in the 'New Size (Mbytes)' box, for example:
12764
Select OK.
14 From the File menu, select Exit to leave the Logical volumes panel and,
again from the file menu, select Exit to leave 'sam'. 4
/etc/reboot ↵
point.
point.
/etc/reboot -h ↵
—end—

Removing a redundant NE load from image the EC-1 platform

ATTENTION

procedure individually to each NE load that is to be removed from the
platform.
Procedure 4-5
Step Action
1 Ensure that you are logged into the Optical Network Manager as root, you
have a current telnet session with the EC-1 and have an open UNIX window
and xterm window (as shown in Procedure 4-1).
3 In the UNIX window, check the NE load's details by performing the following
command:
—continued—

Procedure 4-5
Removing a redundant NE load image from the EC-1 platform (continued)
Step Action
4 Back up the target NE load onto DAT tape by typing a command of the form:
tar cv /home/sdhmsusr/sdhms/data/NE_load/<NE type>/<NE load image> ↵
CAUTION
Invalid backup if wrong software path used 4
this back up.
single line:
rm -rf /home/sdhmsusr/sdhms/data/NE_load/<NE type>/<NE load image> ↵
following command:
—end—

on the EC-1 platform, Nortel Networks recommends that you perform
Procedure 4-6 to remove any redundant EC-1 software loads on the platform.

place.

Procedure 4-6
Step Action
1 Ensure that you are still logged into the Optical Network Manager as root,
you have a current telnet session with the EC-1 and have an open UNIX
.
.
.
command:
—end—

remove any redundant files in the EC-1 /tmp directory.


the upgrade. This procedure must be performed for all types of HP EC-1
platform.
Procedure 4-7
Step Action
1 Ensure that you are still logged into the Optical Network Manager as root,
you have a current telnet session with the EC-1 and have an open UNIX
4
bdf /home ↵
/dev/dsk/c0t5d0 498387 198000 300387 39% /home
C3600, C3750):

—continued—

Procedure 4-7
Step Action
3 Remove old logs:

a. If the customer has a DAT drive connected to the EC-1:
ii. If you require the logs to be saved, then insert a DAT into the DAT
tar cv * ↵
iii. Remove files:
rm -f *.EL *.PL *.GL *.Z ↵
iv. Go to step 4
bdf /
/dev/dsk/c0t5d0 1895241 1105895 509821 68% /

1,200,000 mv *.EL /tmp ↵
mv *.PL /tmp ↵
mv *.GL /tmp ↵
mv *.Z /tmp ↵
logs. Then go to step 4.

ii. Go to step 5
—continued—

Procedure 4-7
Step Action
4 Perform another disk check. In the UNIX Window, type:

bdf /home ↵
For platforms which have logical volume management:(B180L, B2600,
C3600, C3750):

Below 400,000 Contact Nortel Networks
Technical Support 4
—end—

Extracting EC-1 software from DAT onto the Optical Network Manager
This section details the extraction of a software release from a digital audio
tape (DAT) onto the Optical Network Manager Application Platform for
future delivery to the EC-1.
Note 1: NE software (also loaded via separate DAT(s)) CAN be loaded at

this time. This can also be performed at a later stage (see ‘Loading NE
software’ on page 5-6).
Note 2: EC-1 software and NE load images are delivered on separate
DATs. EC-1 software and NE load images are stored in separate
directories. ‘Software requirements’ on Page 1-7 shows you what software
is contained on what media.
Once a release is no longer required, it can be deleted to free-up disk space on
the Optical Network Manager Application Platform. To delete a software
release from the Optical Network Manager Application Platform, see
‘Deleting the EC-1 software release from the Optical Network Manager
Application Platform’ on page 4-26. This can be done at a later date.
Perform Procedure 4-8 for each EC-1 software release.

Procedure 4-8
Step Action
1 Obtain the DAT that contains the software release to be extracted.

2 Ensure that you are logged onto the Optical Network Manager Application
Platform platform as the admin user.
3 Open the Graphical Network Browser (GNB). For more information, see the
Optical Network Manager Application Platform Interface Login NTP (see
‘Associated documentation’ on page xvi).
4 Display the network window Configuration menu and select the Show
Release Manager command.
The Delivery Status dialogue appears.
5 Select the Release Management button.
The Release Management dialogue appears. The software releases
currently stored on the Optical Network Manager Application Platform are
shown in the Release Name list at the top of the dialogue. The amount of
space (in Megabytes) available on the Optical Network Manager Application
Platform hard disk appears in the Disk Space Available field.

6 Move to the Tape Device field. This field shows the default tape device used
by your Optical Network Manager Application Platform. There can be more
than one tape device connected to your Optical Network Manager Application
Platform. To use a device other than the one shown in the Tape Device field,
go to step 7. Otherwise, go to step 8.
—continued—

Procedure 4-8
Application Platform (continued)
Step Action
7 Click the data selector button at the right of the Tape Device field and select
a tape device.
The data selector lists the default tape device and any other devices
connected to Optical Network Manager Application Platform. If required, you
can type the name of the device in the Tape Device field.
8 If there is a DAT in the tape drive, eject it and remove it from the tape drive.
9 Insert the DAT which contains the software release you want to extract. Wait
for the tape drive lights to stop flashing. Before extracting the release, it is
possible to query which software release the DAT contains. To query the
contents of the DAT, go to step 10. Otherwise, go to step 11.
10 Select the Query Tape button. After a short time, the name of the software
release stored on the DAT appears in the Release Name field beside the
Query Tape button. The size of the release (in Megabytes) appears in the
Release Size field. Verify that this software release is the one you want to
extract and that there is enough space to accommodate the release on the
Optical Network Manager Application Platform hard disk.
11 Click the data selector button at the right of the Release Directory field. A
menu appears.
The menu shows all known directories on Optical Network Manager
Application Platform that can be used to store a software release.
12 Select the directory to store the software release. You can type the name of
the directory in the Release Directory field rather than use the data selector.
If you type in the name of a directory that exists, Optical Network Manager
Application Platform validates that the directory can be written to.
13 Select the Extract Release button. The release extraction process begins.
The Progress field continually updates to show how much of the release,
expressed as a percentage, has been extracted from the tape.
To cancel an extraction in progress, select the Abort Extraction button. You
can only cancel an extraction while it is in progress. Once completed, it is not
possible to abort the extraction.
14 Select the Done button.
The Release Management dialogue is removed from the display.
—end—

Scheduling the EC-1 software release delivery

This section details how to schedule the delivery of an EC-1 software release
to a specific EC-1 monitored by Optical Network Manager Application
Platform. It allows you to select software releases to be delivered and the
EC-1 to be delivered to.
It is also possible to specify the time and date the delivery is to take place and
the rate of delivery.
If the connection to an EC-1 is interrupted, the Optical Network Manager

Application Platform continues attempting to deliver the software. This action
can interrupt subsequent deliveries scheduled to other EC-1s. You may have
to consider altering the delivery schedule.
For more information on software delivery, refer to Optical Network Manager 4

Application Platform Fault Management User Guide, 450-3101-014 listed
under ‘Associated documentation’ on page xvi.

Procedure 4-9
Scheduling the EC-1 software release delivery from the Optical Network
Step Action
Platform as the admin user, and open the GNB.
The GNB network window appears.
3 Select the Schedule Delivery button.
The Release Scheduler dialogue appears.
4 In the Release Scheduler dialogue, select the release you want to deliver
from the Select a Release list.
The release is highlighted. The release name appears in the Specify Earliest
Time to Deliver field below the release list.
5 In the Select a Target for Delivery list, select the EC-1 to which you want to
deliver the release.
This controller is highlighted. The controller name appears in the Specify
Earliest Time to Deliver field below the release list.
Note: If an Element Controller is in the inactive state, or a delivery is already
scheduled for that controller, its entry in the Select a Target for Delivery list
is disabled (greyed out). You can sort the controllers in the target list by
controller name, IP address or release number.
—continued—

Procedure 4-9
Step Action
6 Using the radio buttons in the Specify Earliest Time to Deliver field, either:
a. Schedule the delivery for the earliest possible time. Go to step 7.
b. Enter the specific time you want the release delivered to the specified
Element Controller. Go to step 8.
Note: Optical Network Manager Application Platform can deliver only one
release at a time, therefore delivery times are approximate. The exact time of
delivery is determined by the number of releases scheduled for delivery
ahead of this one.
7 Select the As soon as possible button. Optical Network Manager
Application Platform delivers the release to the Element Controller at the
earliest possible time. Go to step 11.
8 Select the At or after button. Optical Network Manager Application Platform
delivers the release to the specified EC-1 at, or after, the time and date you
enter in the fields beside this button.
9 In the Time field (hh:mm), enter the time of day you want the release
delivered to the controller.
This field uses a 24-hour clock format. If the time you specify has already
passed, and you do not specify a date, delivery is made at the specified time
tomorrow.
10 In the Date field (dd:mm), enter the date on which you want to deliver the
release to the controller.
You can schedule a delivery for any date in the next year. If the date has
passed, the delivery is scheduled for the same date next year.
11 You can set a specific rate for the delivery of the software release to the
controller, or let Optical Network Manager Application Platform deliver it at the
highest possible rate. Either:
a. Select the No Pacing button for the release to be delivered at the highest
possible rate of transfer. Go to step 13.
b. Select the Maximum Pace (bps) button to set a specific rate for the
delivery. Go to step 12.
12 In the Pace field, enter the rate, in bytes per second, that the software release
is to be delivered to the specified controller.
Optical Network Manager Application Platform transfers the software release
to the EC-1 at the rate you entered in this field.
Note: When specifying the rate of transfer, take into consideration any
limitations on the use of the communication channel between Optical
Network Manager Application Platform and the controller. Other applications
running on Optical Network Manager Application Platform can be affected if
you set too high a pace for a software delivery.
—continued—

Procedure 4-9
Step Action
13 Select the OK button. Optical Network Manager Application Platform

validates the schedule information you entered.
14 If the schedule information is valid, the delivery status schedule is updated
with the new software release delivery information.
15 When the EC-1 software release has been delivered successfully, log into the
EC-1 as root (see Procedure 4-1) from the Optical Network Manager AP and
remove the old EC-1software release files by typing:
cd /tmp ↵
rm ec* ↵
4
rm -rf install ↵
Note: Failure to remove the old files will result in there being two sets of EC-1
files (once the copyload script has been run), see step 16.
16 Run the copyload script. This moves the new software in the ESWD directory
to the correct software directory.
cd /eswd ↵
./copyload ↵
The results of this script depend on the software release. If it is an EC-1
software release, the following message appears:
EC-1 tar files have been copied to /tmp
Then, perform the following commands:
cd /tmp
tar xvf ec19*install.tar ↵
—end—

Deleting the EC-1 software release from the Optical Network Manager
This section details how to delete EC-1 software releases from the Optical
Network Manager Application Platform when they are no longer required.
You can perform this operation at a later date if required.
The Disk Space Available field in the Release Management dialogue shows
how much space is available on the hard disk. When a release is deleted, all
files in the directory where the release is stored are deleted along with the
directory.

Procedure 4-10
Step Action
Platform as the admin user, and open the GNB.
The Release Management dialogue appears.
4 Select the release you want to delete, and display the release list item menu.
The Release List menu appears.
5 Select the Delete Release command.
A confirmation dialogue appears. The message that appears in the
confirmation dialogue depends on the delivery schedule for the release.
If the release is currently being delivered to a controller, a box containing the
following confirmation message appears:
The <Release name> is currently being delivered to a
controller, it cannot be deleted while it is being
delivered.
To continue with the deletion, go to step 6. To abandon the deletion, go to
step 9.
—continued—

Procedure 4-10
Step Action
6 If the release is scheduled for delivery at some time in the future, the following
confirmation message appears:
The <Release name> is scheduled to be delivered to a
controller. If you delete it and do not extract it before
the time it is scheduled to be delivered, the delivery
will fail. Do you still want to delete the release?
If the release is deleted and not re-extracted before the specified future
delivery date, the delivery fails.
7 If the release is not currently being delivered, nor scheduled for delivery at 4
some time in the future, the following confirmation message appears.
Are you sure you want to delete <Release name>?
8 To continue with the deletion, select the OK button in the message box.
The release is removed from the Release List, and from the Optical Network
Manager AP. The directory, and all files in it, are also deleted from the Optical
Otherwise, select the Cancel button.
The confirmation dialogue is removed. The release remains in the Release
list.
9 Select the Done button to close the Release Management dialogue.
—end—


This section details the EC-1 Release 19 upgrade procedure, carried out from
the Optical Network Manager Application Platform via a telnet session. The
EC-1 software files are accessed from the /tmp directory on the EC-1.
This upgrade procedure has been modified from Release 15 to reduce the
need for your interaction when performing the upgrade. Please note that this
feature is not entirely hands-free. You still have to provide some input.
However this is mainly at the beginning of the upgrade script.

failure appears on the screen, allowing you the opportunity to take appropriate
action.
The upgrade script exits if it is interrupted. A re-run of the script is required to

return to the same point in the upgrade process.
Procedure 4-11
Step Action
1 Ensure that you are logged into the Optical Network Manager platform as
and xterm window (as shown in Procedure 4-1).
Note: before you perform the EC-1 software upgrade, you must first set the
file permissions for the EC-1 software as described in the following two steps:
4 In the xterm window, change into upgrade directory:
cd /tmp/install ↵
—continued—

Procedure 4-11
Step Action
5 Start the upgrade process using the tar files that are in the /tmp directory by
entering the following command:
./Upgrade_EC1
6 Then script checks if the previous release has been committed. If the
previous release has not been committed there will be a warning message
prompting the user to commit the release.
EC-1 Release 181xx has not been committed
4
To commit R181x:
8 The script then determines if any alarms are current on the EC-1, and this
**********************************************
* *
* WARNING!!! *
* *
**********************************************
There are 14 alarms currently outstanding

Procedure 4-11
Step Action.
1 51:1 50:5004 50:5004 NE-Card_Fail
2 51:1 50:5004 50:5004 NE-Wrong_Card
3 51:1 50:5004 50:5004 NE-Card_Out
4 51:1 50:5004 50:5004 NE-Card_Out
5 51:1 50:5004 50:5004 NE-Card_Out
6 51:1 50:5004 50:5004 NE-Card_Out
7 51:1 50:5004 50:5004 NE-Card_Out
8 51:1 50:5004 50:5004 NE-Card_Out
11 51:1 50:5004 50:5004 RS-LOS
13 51:1 50:5004 50:5004 LP-SF
14 30:1 32:5007 32:5007 Comms fail alarm
9
A list of alarms is included in the back of the upgrade document. Before
running this script the EC-1 must be free from alarms that may affect the
upgrade process.
10 A check is made for the disk space available.
—continued—

Procedure 4-11
Step Action
11 If there is adequate diskspace you are asked:


It then asks you:
Do you wish to install Package 1 {y/n]? 4

—continued—

Procedure 4-11
Step Action
information.


exist - creating it

the following list:


7. Hot standby EC-1
Option [1-7]?
—continued—

Procedure 4-11
Step Action
16 If the active EC is protected by a standby, you must upgrade the standby

workstation before the active one. Select option 5, 6 or 7 for the standby
4

b. Enter 2↵, 3↵ or 4↵
17 Enter 1↵
—continued—

Procedure 4-11
Step Action

****Preparation of new kernel completed sucessfully at xxxx ***.
complete.

hci_upgrade_users - Upgrading the configuration of all EC-1

management users
syseng01
admin
netsurv
slat
master
operator
new EC-1 load.
—end—


courses of action:
for full details. 4
upgrade’).

procedure. Do not perform this procedure if the EC-1 is not managed by a
Optical Network Manager Application Platform.
• You can install an NCD900XPC X-Terminal for use with Optical Network
Manager EC-1 Release 19.1. Refer to Chapter 7 of Optical Network
end of chapter

5-1
Upgrading NE software 5-
Overview
This chapter details the Network Element (NE) upgrade procedure. Although
it is possible to perform NE software downloads in advance of the EC-1
upgrade process, the NE upgrade must be performed AFTER the EC-1
upgrade.
Note: NE upgrades can take place either before or after the EC-1 software
is committed for permanent use.
5
CAUTION
Running old EC-1 software with new NE software
If you commit to an NE upgrade without first committing to an EC-1
by the EC-1 (with old software).
It is strongly recommended that if a backout of both EC-1 Release 19.1 and

NE upgrades is required, the NE upgrade backout should be performed first.
The NE software upgrade process comprises the following main steps:
1 Load the NE upgrade software onto the EC-1 platform:

— NE software from DAT. Install this using the DAT drive on the EC-1
platform.
— Electronic Software Delivery (ESWD) digital audio tape (DAT). Install
this using the DAT drive on the Optical Network Manager Application
Platform, and subsequently download it to the EC-1 from the Optical
— NE software from the local EC-1 CD-ROM drive.
2 Download the NE software to the inactive software bank of one or more
NEs using the send _ne utility.
3 Activate the new NE software. This puts the downloaded software into the
active software bank of each NE, forcing a warm reboot.


5-2 Upgrading NE software
Once software is in active use, you must decide whether to commit the new
software to both software banks for general use or to backout of the upgrade,
restoring the use of the original NE software. The ‘Post upgrade options’
section on Page 5-20 describe the available options.

Before you start, be aware that, depending on your network deployment
configuration, you may need to refer to additional information or procedures
from other handbooks. Check these references NOW, and ensure that you
have all the relevant information to hand:
• ‘Preparation’ section on Page 5-4

To check the software state of each NE to be upgraded, a reference is made
to the appropriate user interface guides for the NEs within the network
listed in ‘Associated documentation’ on page xvi.
• Procedure 5-2, step 3 on Page 5-8
Refers to the Optical Network Manager Application Platform Interface
Login, 450-3101-012 listed in ‘Associated documentation’ on page xvi.
• Page 5-11
Refers to software delivery information in the Optical Network Manager
Application Platform Fault Management User Guide, 450-3101-014 listed
in ‘Associated documentation’ on page xvi.

Figure 5-1
Flowchart - Upgrading NE load image software
START
Read Chapter 1 to ensure that have suitable hardware/software and that

your network is in a suitable state for upgrade
Preparation:
– Perform NE configuration backups before upgrading the software for
any NEs
– It is recommended that the software state of each NE to be upgraded
is checked. The state should ‘stable’.
– Read and act on any relevant ‘Cautions’ in the ‘Preparation’ section
on Page 5-4
Load the NE software onto the EC-1 platform:

– NE software from DAT drive on the EC-1 platform,
OR:
Procedure 5-1
– Load NE software remotely from the Optical Network Manager AP:

5
– Extract NE software from DAT onto the Optical Network Manager AP
Procedure 5-2
– Schedule NE software delivery from Optical Network Manager AP to EC-1
(ESWD)
Procedure 5-4
– Delete NE software from Optical Network Manager AP once no longer
required
(can be performed at a later date)
Procedure 5-5
–OR:
NE software from CD-ROM drive on the EC-1 platform,
Procedure 5-3-
Download the NE software to the inactive software bank of one or more
NEs using the send_ne utility.
Appendix I - Optical Network Manager EC-1 User Procedures
Apply the path protection script before the NEs are booted – ONLY if the
network contains Release 7 TN-1X NEs (7.72A/7.72M only)
Procedure 5-6
Activate the downloaded NE software. This puts the downloaded software

into the active software bank of each NE, forcing a warm reboot.
Procedure 5-7
STOP
Now refer to Post upgrade options on page 5-20 for options

on how to proceed.
upgrade. If you commit to an NE upgrade without first committing to an EC-1
upgrade, the upgraded NEs will not be fully supported by the EC-1.

Preparation
ATTENTION
It is important to read and follow all of the preparatory information below.
Failure to do so can cause problems during the NE software upgrade.
Read Chapter 1, ‘Introduction’ to ensure that have suitable hardware/software

and that your network is in a suitable state for upgrade. For example, there are
a number of alarms that must be cleared before the network can be upgraded.
Before initiating the NE upgrade procedure it is recommended that the

software state of each NE to be upgraded is checked. This process is
performed via a user interface session to each NE in turn. If an NE is in any
state other than ‘stable’, the software download fails. For details of this
process, refer to the appropriate user interface guides for the NEs within the
network (see ‘Associated documentation’ on page xvi).
The IP addresses of both the EC-1 and the Optical Network Manager
Application Platform HP-UX workstations must be known to allow you to
telnet from the Optical Network Manager Application Platform workstation
to the EC-1 workstation.
CAUTION
NE configuration backups
It is imperative that NE configuration backups are performed before
upgrading the software for any NEs. The backups are essential when a
software backout needs to be performed.
CAUTION
Before upgrading to OM4100 release 4.5, you must run the EOS Inventory
Script to detect incorrectly programmed End of Shelf cards. Failure to
replace affected cards may result in synchronisation problems. For full
details of the problem and how to run the EOS Inventory script refer to
‘Appendix D: Preventing a Sync problem caused by End Of Shelf card
programming’.
CAUTION
TN-1X LAPD settings after upgrade to Release 8
TN-1X Release 7 NEs (7.72A/7.72M only) do not retain their STM-1 LAPD
(DCC) channel settings. When a Release 7 NE is booted to Release 8, any
previously disabled data communication channels (DCCs) will be enabled.
Care must be taken to ensure that Open Systems Interconnect (OSI) routing
table limits are not exceeded, due to possible re-enabling of a previously
disabled DCC. This could lead to a loss of network visibility.

CAUTION
TN-1X STM-1 Optical Aggregate Unit (25U TM00 750 HWH)
TN-1X Release 8 supports a new STM-1 Optical Aggregate Unit,
25U TM00 750 HWH. TN-1X Release 7 is also able to support this unit by
equipping it as a 25U TM00 750 GWA unit. When an upgrade to Release 8
is performed, units equipped in this way will cause ‘Wrong Card’ alarms to
be raised. These units should be immediately re-equipped as the new
25U TM00 750 HWH unit. It is not necessary to unequip the slot, and
connections will not be lost.
CAUTION
TN-1X Release 8 VC-3 defragmentation
The internal bus of the TN-1X is mapped differently at Release 8 than at
earlier releases. While this does not affect the operation of current
connections, future connections are more likely to generate traffic hits. To
minimise future traffic hits, it is imperative that a VC-3 defragmentation is
performed on each TN-1X NE that is upgraded to Release 8. This should be
performed at a time of low network activity.
CAUTION
5
TN-1X Release 9 VC-12 defragmentation
The internal bus mapping of TN-1X Release 9.0 is different from earlier
releases. A VC-12 Defragmentation must be performed on each network
element that is upgraded to TN-1X Release 9.0. (For details of this process,
see Engineering Bulletin TN-1X Release 9.0 —Connections
Recommendations,SDH_E155.). This should be performed at a time of low
network activity.
CAUTION
Buffer alarm monitoring
Release 7.n of TN-1X does not store PPI_AIS, LP_DEG or INT_LP_
OP_Buffer alarm monitoring information in its configuration memory.
When an upgrade to Release 9.0 occurs, these settings default (PPI_AIS
alarm monitoring to on, LP_DEG to on and INT_LP_Buffer to off.) Any
Release 7.n TN-1X that has these ports provisioned to non-default settings
must be re-provisioned after it is upgraded to Release 9.0.
To upgrade the OPTera Metro 4150 or OPTera Metro 4200 software you must
firstly read the Pre-upgrade requirements detailed in Chapter 4 of the OPTera
Metro 4150 System and Data Administration Procedures (323-1123-302) or
OPTera Metro 4200 System and Data Administration Procedures
(323-1233-302) as appropriate.

the upgrade of NEs within the network.

Loading NE software
Before any NE downloads can be performed, you must load an NE load
image for each NE type to be upgraded onto the EC-1 platform.
Note: It is possible that NE software will have already been loaded onto
the EC-1 platform at the same time as the EC-1 software was loaded. If this
is the case, this section can be ignored, and this procedure can be continued
from ‘Downloading NE load images’ on Page 5-16.
NE load images are delivered in one of the following formats:

• NE software from DAT. Install this using the DAT drive on the EC-1
platform (Procedure 5-1). OR
• Electronic Software Delivery (ESWD) digital audio tape (DAT). This is
installed using the DAT drive on the Optical Network Manager Application
Platform, and subsequently downloaded to the EC-1 from the Optical
Network Manager Application Platform (Procedure 5-2 to Procedure 5-5).
OR
• NE software from CD. Install this using the CD-ROM drive on the EC-1
platform (Procedure 5-3)
Loading NE software from a DAT drive on the EC-1

To load NE software, perform Procedure 5-1 for each NE type.
Procedure 5-1
Extracting NE load images from DAT on the EC-1
Step Action
1 Log into HP platform as sdhmsusr.

2 Log into the EC-1 platform as sdhmsusr user and open an Xterm window by:
3 Select a new xterm window with your mouse.
—continued—

Procedure 5-1
Extracting NE load images from DAT on the EC-1 (continued)
Step Action
4 Change into the NE load image directory:

cd /home/sdhmsusr/sdhms/data/NE_load/<NE_type> ↵
Where <NE_type> is 1X, 1C, 1P, 4T, 4XE, or 16XE.
Note: The TN-4XE (OPTera Metro 4100 and OPTera Metro 4150)/TN-4T/
TN-16XE(OPTera Metro 4200) NEs make use of a number of separate load
images for the different cards within each NE. A TN-4XE/TN-4T/TN-16XE
software download will typically consist of a number of load images.
5 Place the appropriate load image DAT into the DAT drive. Wait until the tape
drive lights stop flashing.
6 Load the contents of the load image DAT into the current directory:
tar xv ↵
The load image is loaded onto the EC-1 platform. Make a note of the NE load
7
image filename.
When the download is over, remove the DAT.
5
8 Repeat step 4 to step 7 for other NE types if required.
—end—
Loading NE software using ESWD from the Optical Network Manager

Electronic Software Delivery (ESWD) digital audio tape (DAT). Install this
using the DAT drive on the Optical Network Manager Application Platform,
and subsequently download to the EC-1 from the Optical Network Manager
Application Platform.
Extracting NE software from DAT onto the Optical Network

This section details the extraction of a software release from a digital audio
tape (DAT) onto the Optical Network Manager Application Platform for
future delivery to the EC-1.
Note 1: EC-1 software and NE load images are delivered on separate

DATs. EC-1 software and NE load images are stored in separate
directories.
Once you no longer require a release, you can delete it to free-up disk space
on the Optical Network Manager Application Platform. To delete a software
release from the Optical Network Manager Application Platform, see
‘Deleting the NE software release from the Optical Network Manager
Application Platform’ on page 5-14. This can be done at a later date.
Perform Procedure 5-2 for each NE software release.

Procedure 5-2
Extracting NE software from DAT onto the Optical Network Manager
Step Action
1 Obtain the DAT that contains the software release to be extracted.

2 Log into the Optical Network Manager Application Platform platform as the
admin user.
3 Open the Graphical Network Browser (GNB). For more information, see the
Optical Network Manager Application Platform Interface Login NTP (see
‘Associated documentation’ on page xvi).
The Release Management dialogue appears. The software releases
currently stored on the Optical Network Manager Application Platform are
shown in the Release Name list at the top of the dialogue. The amount of
space (in Megabytes) available on the Optical Network Manager Application
Platform hard disk appears in the Disk Space Available field.
6 Move to the Tape Device field. This field shows the default tape device used
by your Optical Network Manager Application Platform. There can be more
than one tape device connected to your Optical Network Manager Application
Platform. To use a device other than the one shown in the Tape Device field,
continue with step 7. Otherwise, continue with step 8.
7 Click the data selector button at the right of the Tape Device field and select
a tape device. The data selector lists the default tape device and any other
devices connected to Optical Network Manager Application Platform. If
required, you can type the name of the device in the Tape Device field.
8 If there is a DAT in the tape drive, eject it and remove it from the tape drive.
9 Insert the DAT which contains the software release you want to extract. Wait
for the tape drive lights to stop flashing. Before extracting the release, it is
possible to query which software release the DAT contains. To query the
contents of the DAT, continue from step 10. Otherwise, continue from step 11.
10 Select the Query Tape button. After a short time, the name of the software
release stored on the DAT appears in the Release Name field beside the
Query Tape button. The size of the release (in Megabytes) appears in the
Release Size field. Verify that this software release is the one you want to
extract and that there is enough space to accommodate the release on the
Optical Network Manager Application Platform hard disk.
11 Click the data selector button at the right of the Release Directory field. A
menu appears.
The menu shows all known directories on Optical Network Manager
Application Platform that can be used to store a software release.
—continued—

Procedure 5-2
Extracting NE software from DAT onto the Optical Network Manager Application
Platform (continued)
Step Action
12 Select the directory to store the software release. You can type the name of
the directory in the Release Directory field rather than use the data selector.
If you type in the name of a directory that exists, Optical Network Manager
Application Platform validates that the directory can be written to.
13 Select the Extract Release button. The release extraction process begins.
The Progress field continually updates to show how much of the release,
expressed as a percentage, has been extracted from the tape.
To cancel an extraction in progress, select the Abort Extraction button. You
can only cancel an extraction while it is in progress. Once completed, it is not
possible to abort the extraction.
14 Select the Done button.
The Release Management dialogue closes.
5
—end—
Installing the software load from CD-ROM

Copying the software from CD-ROM to the EC-1 enables a faster turn around
time, faster installation and incurs lower costs than the use of either digital
audio tape (DAT) or 3.5-inch disks.
Procedure 5-3
Copying the network element software load from the CD-ROM to the Optical
Network Manager EC-1
Step Action
1 Insert the network element software CD-ROM in the CD-ROM drive.

2 In the Login dialog box, login as root user and enter the password. Type:
root ↵
<password> ↵
A copyright notice appears on your screen, followed by the HP CDE
workspace. You are now logged in.
3 Open a UNIX window by clicking the terminal icon at the bottom left-hand
corner of the dashboard.
—continued—

Procedure 5-3
Network Manager EC-1 (continued)
Step Action
4 Check the system to ensure that the CD-ROM drive is available, by typing:
This command returns a list of disk devices. The CD-ROM device must be in
this list, for example, /dev/dsk/cXtXdX (where cXtXdX is the device name of
the CD-ROM).
Record the device name because you must enter it when mounting the
CD-ROM.
5 Create a directory in which you can mount the CD-ROM device, by typing:
mkdir /cdrom ↵
6 Mount the CD-ROM on to the /cdrom directory by typing:
Note: Replace the device name cXtXdX with the name got from the ioscan
in step 4.
7 You are already logged in as root user from step 2. Open another UNIX
window and login as sdhmsusr, by typing:
su - sdhmsusr
8 You have to make a directory on the Optical Network Manager EC-1 before
you can copy the network element software from the CD-ROM, type:
mkdir /home/sdhmsusr/sdhms/data/NE_load/<NE_TYPE>/<NE_LOAD>
where, for example:
• for OPTera Metro 4100 network element load the entry is mkdir home/
sdhmsusr/sdhms/data/NE_load/4XE/<NE_LOAD>
•for OPTera Metro 4200 Release 3.1 the entry is mkdir home/sdhmsusr/
sdhms/data/NE_load/16XE/3.10
—continued—

Procedure 5-3
Network Manager EC-1 (continued)
Step Action
9 Copy the files as follows. There may be a directory structure so the -R switch
command must be used, type as one line:
cp -R /cdrom/NE_load/*
/home/sdhmsusr/sdhms/data/NE_load/<NE_TYPE>/<NE_LOAD>/
where, for example:
•for a OPTera Metro 4100 network element load the entry is
/home/sdhmsusr/sdhms/data/NE_load/4XE/<NE_LOAD>/
•for OPTera Metro 4200 Release 3.1 the entry is
/home/sdhmsusr/sdhms/data/NE_load/16XE/3.10/
Note: For clarity the command line entry is shown on two lines. A typical 5
screen display on one line appears as follows:
cd -R /cdrom/NE_load/* /home/sdhmsusr/sdhms/data/NE_load/<NE_TYPE>/<NE_LOAD>g
10 Open another UNIX window. Unmount the CD-ROM. Type:

umount /cdrom ↵
11 Eject and remove the CD-ROM.
12 Log out of the workspace by selecting the Exit button
—end—
Scheduling the NE software release delivery

This section details how to schedule the delivery of an NE software release to
a specific EC-1 monitored by Optical Network Manager Application
Platform. It allows you to select software releases to be delivered and the
EC-1 to be delivered to. It is also possible to specify the time and date the
delivery is to take place and the rate of delivery.
If the connection to an EC-1 is interrupted, the Optical Network Manager

Application Platform continues attempting to deliver the software. This action
can interrupt subsequent deliveries scheduled to other EC-1s. You may have
to consider altering the delivery schedule.
For more information on software delivery, see the Optical Network Manager
Application Platform Fault Management NTP (see ‘Associated
documentation’ on page xvi).

Procedure 5-4
Scheduling the NE software release delivery from the Optical Network
Step Action
1 Log in to the Optical Network Manager Application Platform as the admin

user, and open the GNB. The GNB network window appears.
3 Select the Schedule Delivery button. The Release Scheduler dialogue
appears.
4 In the Release Scheduler dialogue, select the release you want to deliver
from the Select a Release list.
The release is highlighted. The release name appears in the Specify Earliest
Time to Deliver field below the release list.
5 In the Select a Target for Delivery list, select the EC-1 to which you want to
deliver the release.
This controller is highlighted. The controller name appears in the Specify
Earliest Time to Deliver field below the release list.
Note: If an Element Controller is in the inactive state, or a delivery is already
scheduled for that controller, its entry in the Select a Target for Delivery list
is disabled (greyed out). You can sort the controllers in the target list by
controller name, IP address or release number.
6 Using the radio buttons in the Specify Earliest Time to Deliver field, either:
a. Schedule the delivery for the earliest possible time. Continue from step 7.
b. Enter the specific time you want the release delivered to the specified
Element Controller. Continue from step 8.
Note: Optical Network Manager Application Platform can deliver only one
release at a time, so delivery times are approximate. The exact time of
delivery is determined by the number of releases scheduled for delivery
ahead of this one.
7 Select the As soon as possible button. Optical Network Manager
Application Platform delivers the release to the Element Controller at the
earliest possible time. Continue from step 11.
8 Select the At or after button.
Optical Network Manager Application Platform delivers the release to the
specified EC-1 at, or after, the time and date you enter in the fields beside this
button.
9 In the Time field (hh:mm), enter the time of day you want the release
delivered to the controller.
This field uses a 24-hour clock format. If the time you give has already passed
and you do not specify a date, delivery is at the specified time tomorrow.
—continued—

Procedure 5-4
Scheduling the NE software release delivery from the Optical Network Manager
Step Action
10 In the Date field (dd:mm), enter the date when you want to deliver the release
to the controller. You can schedule a delivery for any date in the next year.
If the date has passed, the delivery is scheduled for the same date next year.
11 You can set a specific rate for the delivery of the software release to the
controller, or let Optical Network Manager Application Platform deliver it at the
highest possible rate. Either:
a. Select the No Pacing button for the release to be delivered at the highest
possible rate of transfer. Continue from step 13.
b. Select the Maximum Pace (bps) button to set a specific rate for the
delivery. Continue from step 12.
12 In the Pace field, enter the rate, in bytes per second, that the software release
is to be delivered to the specified controller. Optical Network Manager
Application Platform transfers the software release to the EC-1 at the rate you
entered in this field.
5
Note: When specifying the rate of transfer, take into consideration any
limitations on the use of the communication channel between Optical
Network Manager Application Platform and the controller. Other applications
running on Optical Network Manager Application Platform can be affected if
you set too high a pace for a software delivery.
13 Select the OK button. Optical Network Manager Application Platform
validates the schedule information you entered.
14 If the schedule information is valid, the delivery status schedule is updated
with the new software release delivery information.
15 When the NE software release has been delivered successfully, log into the
EC-1 as root and run the copyload script. This moves the software in the
ESWD directory to the correct software directory.
cd /eswd ↵
./copyload ↵
The NE load images have now been copied to the EC-1.
16 Exit from the EC-1 and return to the Optical Network Manager platform.
—end—

Deleting the NE software release from the Optical Network

This section details how to delete NE software releases from the Optical
Network Manager Application Platform when they are no longer required.
You can perform this operation at a later date if required.
The Disk Space Available field in the Release Management dialogue shows
how much space is available on the hard disk. When a release is deleted, all
files in the directory where the release is stored are deleted along with the
directory.

Procedure 5-5
Deleting the NE software release from the Optical Network Manager
Step Action
1 Log in to the Optical Network Manager Application Platform as the admin

user, and open the GNB.
The Release Management dialogue appears.
4 Select the release you want to delete, and display the release list item menu.
The Release List menu appears.
5 Select the Delete Release command. A confirmation dialogue appears. The
message that appears in the confirmation dialogue depends on the delivery
schedule for the release.
If the release is currently being delivered to a controller, a box containing the
following confirmation message appears:
The <Release name> is currently being delivered to a
controller, it cannot be deleted while it is being
delivered.
To continue with the deletion, continue from step 6. To abandon the deletion,
continue from step 9.
—continued—

Procedure 5-5
Deleting the NE software release from the Optical Network Manager Application
Platform (continued)
Step Action
6 If the release is scheduled for delivery at some time in the future, the following
confirmation message appears:
The <Release name> is scheduled to be delivered to a
controller. If you delete it and do not extract it before
the time it is scheduled to be delivered, the delivery
will fail. Do you still want to delete the release?
If the release is deleted and not re-extracted before the specified future
delivery date, the delivery fails.
7 If the release is not currently being delivered, nor scheduled for delivery at
some time in the future, the following confirmation message appears.
Are you sure you want to delete <Release name>?
8 To continue with the deletion, select the OK button in the message box.
The release is removed from the Release List, and from the Optical Network 5
Manager AP. The directory, and all files in it, are also deleted from the Optical
Otherwise, select the Cancel button. The confirmation dialogue is removed.
The release remains in the Release list.
9 Select the Done button to close the Release Management dialogue.
—end—

Downloading NE load images

Software download transfers the new NE software into the alternate bank.
The software download procedure uses send _ne (‘Appendix H: Send_ne User
Instructions’).
CAUTION
NE configuration backups
It is imperative that NE Configuration Backups are performed before
upgrading the software for any NEs. The backups are essential when a
software backout needs to be performed.
CAUTION
Before upgrading to OM4100 release 4.5, you must run the EOS
Inventory Script to detect incorrectly programmed End of Shelf cards.
Failure to replace affected cards may result in synchronisation problems.
For full details of the problem and how to run the EOS Inventory script
refer to ‘‘Appendix C: Preventing a Sync problem caused by End Of Shelf
card programming’’.
Attention
NE Software backouts
It is not possible to back out of a software download using send_ne. For more
information refer to NTP 323-1123-302, System and Data Administration
Procedures, NE software administration.
Software downloads are performed one at a time, and take between 10 and 20
minutes per NE.
Note: When you start the downloaded software, you must reboot each NE.
The order in which NEs are booted is pre-determined. You should choose
the NE furthest away from the gateway NE (i.e. the greatest number of NE
‘hops’ away). Then, select adjacent NEs in turn, moving towards the
gateway NE, until all are booted. For individual rings, the gateway NE
should be the last to be booted.
CAUTION
Risk of aborting download process
Do not attempt to change the EC-1 date or time during a download. All
processes running within the EC will be closed while the EC updates the
date or time.
ASD_main_menu.jpg
create_batch_file_name.jpg

Path protection switch alignment

If the network contains Release 7 TN-1X NEs (7.72A/7.72M only), then the
path protection script must be applied before the NEs are booted.
Procedure 5-6
Path protection switch alignment
Step Action
1 On the EC-1 login as user: syseng01.

2 Open the System Engineer UNIX window.
3 Enter:
cd /home/sdhmsusr/patches/1X/PPS↵
./PPS_nvram_update↵
4 Login as root:
su root↵
<password>↵
5 Enter: 5
cd /home/sdhmsusr/patches/1X/PPS/install↵
./install_pps_patch↵
6 Close the System Engineer’s UNIX window.
—end—

Activating downloaded NE load images

After software downloads have been performed, each affected NE has the
new load image software in its inactive software bank, and the original load
image software in its active software bank. The software state at this point
should be ‘Ready_to_activate’.
You must manually switch the contents of the software banks to put the
downloaded software into use. This results in a reboot of all affected NEs.
This is detailed in Procedure 5-7.
Note 1: The order in which NEs are booted is pre-determined. You should
choose the NE that is the most fibre hops away from the gateway NE. Then
select adjacent NEs in turn, moving towards the gateway NE, until all are
booted. For individual rings, the gateway NE should be the last to be
booted.
Note 2: It is possible to backout of the NE upgrade both before and after
the software has been activated. See Chapter 6, ‘Backing out of an NE
upgrade’ for details.
Procedure 5-7
Activating downloaded NE software
Step Action
1 Log into HP platform as user syseng01.

2 Log into the EC-1 software.
3 Select the Network Element Access option from the Main Menu.
The Network Element Access window appears.
4 Select an NE to which software has already been downloaded. Right click on
this NE to display the pop-up menu for the NE.
5 Select the Command Line option from the pop-up menu.
This starts a command line user interface session to the NE.
6 Check that the software state by executing the following command line
sequence:
~asv↵
If the software state is ‘Stable’, either the software download process failed,
or the downloaded software has been switched and committed to already.
If the software state for the ‘Ready_to_commit’, the download software has
already been activated.
If the software state is ‘Ready_to_activate’, continue from step 7.
7 Activate the software in the inactive bank by executing the following
command line sequence:
~ a s sl ↵
—continued—

Procedure 5-7
Activating downloaded NE software (continued)
Step Action
8 The NE prompts for confirmation:

Warning: This will switch software loads
Are you sure ? [Yes, No]
Select y (Yes) to reboot the NE.
The NE performs a warm restart, and swaps the software in its software
banks.
When prompted, close the window by pressing Enter.
Note: Rebooting an NE takes several minutes. During this time, the NE is not
managed by the EC-1. No operations should be performed for this NE. It is
possible that communications to other NEs may be lost while this action is
performed.
9 Once the NE has rebooted, wait for the NE to become managed by the EC-1.
10 Repeat step 4 to step 9 for each NE for which software is to be activated.
5
—end—
Once software is in active use, the software state becomes

‘Ready_to_commit’.


After you have upgraded the required NE software, there are several possible
courses of action:
• You can decide to commit to using the new software (see Chapter 7,
‘Committing to an NE upgrade’)
• You can decide to revert to the use of the original software (see Chapter 6,
‘Backing out of an NE upgrade’).
end of chapter


6-1
Backing out of an NE upgrade 6-

This chapter details how to backout of the NE upgrade process.
CAUTION
Traffic hits during NE upgrade backout
If an NE backout is performed, a traffic hit is caused permanently. To
recover from the traffic hit, restore the configuration backup that was
performed before the software download was initiated.
CAUTION
Switching from Release 8 to Release 7
If the TN-1X is switched from Release 8 software to Release 7 software, the
configuration will be lost, the TN-1X will enter detached mode, and traffic
will be hit. To recover from the traffic hit, restore the configuration backup
6
that was performed before the software download was initiated.
It is possible to backout of the NE upgrade both before and after the

downloaded software has been activated:
• To backout of an NE upgrade before software has been activated, see
‘Backing out before software activation’ on page 6-2.
• To backout of an NE upgrade after software has been activated, see
‘Backing out after software activation’ on page 6-3.
Note 1: If a backout of both EC-1 Release 19.1 and NE upgrades is
required, the NE upgrade backout should be performed first.
Note 2: At the start of a backout a configuration freeze must be observed.
Any configuration changes made on the Customer platform must occur
before the upgrade commences.

6-2 Backing out of an NE upgrade
Backing out before software activation

When new NE software has been downloaded, the original software is in the
active bank and running on the NE, and the new software is in the inactive
bank. The software state at this point should be ‘Ready_to_Activate’.
Attention
NE Software backouts
It is not possible to back out of a software download using send_ne. For more
information refer to NTP 323-1123-302, System and Data Administration
Procedures, NE software administration.

Backing out after software activation

After activation of downloaded software has been performed, each affected
NE has the new load image software in its active software bank, and the
original load image software in its inactive software bank. The software state
at this point should be ‘Ready_to_commit’.
To backout of the NE upgrade, the contents of the software banks must be

switched manually to return the original software into use. This results in a
reboot of all affected NEs. This is detailed in Procedure 6-1.
Procedure 6-1
Backing out of an NE upgrade after activation
Step Action
1 Log into HP platform as user syseng01.

2 Log into the EC-1 software.
3 Select the Network Element Access option from the Main Menu. The
Network Element Access window appears.
4 Select an NE to which software has already been downloaded. Right click on
this NE to display the pop-up menu for the NE.
5 Select the Open Command Line option from the pop-up menu.
This starts a command line user interface session to the NE. 6
6 Check the software state by executing the following command line sequence:
~asv↵
If the software status is ‘Stable’, either the software download process failed,
or the downloaded software has been switched and committed to already.
If the software state is ‘Ready_to_commit’, continue from step 7.
7 Reactivate the original software by executing the following command line
sequence:
~ a s so ↵
8 The NE prompts for confirmation:
Warning: This will switch software loads
Are you sure ? [Yes, No]
Select y (Yes) to reboot the NE.
The NE performs a warm restart, and reverts to using the original software.
When prompted, close the window by pressing Enter.
Note: Rebooting of an NE takes several minutes. During this time, the NE is
not managed by the EC-1. No operations should be performed for this NE. It
is possible that communications to other NEs may be lost while this action is
performed.
—continued—

6-4 Backing out of an NE upgrade
Procedure 6-1
Backing out of an NE upgrade after activation (continued)
Step Action
9 Once the NE has rebooted, wait for the NE to become managed by the EC-1.
10 For a TN-1X NE, perform the following additional stages:
a. In the Network Element Access window, select the NE. Right click on
this NE to display the pop-up menu for the NE. Select the Open
Command Line option from the pop-up menu. This starts a command
line user interface session to the NE.
b. Commit to using the original software by executing the following
command line sequence:
~ a s cm ↵
c. Once the commit is complete, close the command line session:
~l↵
11 For a TN-1X NE, you must restore the configuration for the NE that was
recommended in Chapter 5, ‘Upgrading NE software’. This process is
optional for TN-1C, TN-1P, TN-4XE (OPTera Metro 4100/OPTera Metro
4150), or TN-16XE (OPTera Metro 4200) NEs. To do this:
a. In the Network Element Access window, select the NE. Right click on
this NE to display the pop-up menu for the NE. Select the Restore as a
Copy option.
The Restore Files window appears.
b. Position the mouse pointer over the required backup file and select it by
pressing the left mouse button.
c. Press the Confirm button.
d. A final confirmation is requested. Accept this.
The restore process will then begin. The Messages window indicates the
progress of this operation.
e. When complete, the NE contains the restored information in its inactive
bank. To activate this information, start a User Interface (UI) session.
f. Switch to the restored bank:
~ a c sr ↵
The NE prompts:
Warning, this action will switch configuration
Are you sure ? [y/n]
Select y(yes) to activate the restored configuration.
The NE reboots.
Note: The UI commands described above are detailed in the relevant User
Interface handbook (see ‘Associated documentation’ on page xvi).
—continued—

Procedure 6-1
Backing out of an NE upgrade after activation (continued)
Step Action
Once communications to the NE have been restored:

a. Start a User Interface (UI) session.
b. Commit to the active configuration.
~ a c cm ↵
The NE prompts:
Warning, this action will overwrite standby
configuration bank
Are you sure ? [y/n]
Select y(yes) to commit to the active configuration. The NE reboots.
Note: The UI commands described above are detailed in the relevant User
Interface handbook (see “Associated documentation” on page xvi).
12 Repeat step 4 to step 11 for each NE for which a software backout is
required.
—end—
end of chapter

7-1
Committing to an NE upgrade 7-
Refer to (‘Appendix H: Send_ne User Instructions’)

8-1
Backing out of an EC-1 upgrade 8-

This chapter details how to backout of the EC-1 Release 19.1 upgrade.
CAUTION
Backing out of an EC-1 upgrade
It is strongly recommended that the EC-1 upgrade backout
procedure is only performed after full investigation by Nortel
Networks support engineers, and escalation through the
support structure. Backouts should only be used as a last resort,
should all other attempts fail to rectify a problem.
The backout procedure

The EC-1 backout procedure assumes that the upgrade has been performed up
to the point where Release 19.1 has been installed but has not been
committed. If the EC-1 has been committed then the backout CANNOT be
performed.
Note 1: If you backout of an EC-1 upgrade after you have upgraded NE

software, the upgraded NEs (with new software) will not be fully
supported by the EC-1 (with old software). It is strongly recommended that
if a backout of both EC-1 Release 19.1 and NE upgrades is required, the
NE upgrade backout should be performed first.
Note 2: No configuration modifications should take place throughout the 8
backout process.
Note 3: If a backout of both EC-1 Release 19.1 and NE upgrades is
required, the NE upgrade backout should be performed first (see
Chapter 6, ‘Backing out of an NE upgrade’).

8-2 Backing out of an EC-1 upgrade
Procedure 8-1
Backing out of the EC-1 software upgrade
Step Action
1 You must log onto the EC-1 platform as the root user either locally or
remotely from the Optical Network Manager Application Platform.
If Then
you are logging on locally Go to step 3
you are logging in remotely from the Optical Network Go to step 2
2 Type the following commands to Telnet into the EC-1 as root user:
xhost <Ip address of EC-1> ↵
DISPLAY=<IP address of Optical Network Manager AP>:0.0 ↵
export DISPLAY↵
3 Open an xterm from an existing UNIX window by entering the following
command.
xterm -l -lf /tmp/back_log & ↵
window into a log file. This log file (back_log) is stored in the /tmp directory:
5 Create a backout directory and copy the required files into this directory.
mkdir /tmp/backout ↵
cp /home/sdhmsusr/sdhms/bin/Backout_EC1 /tmp/backout↵
chown root:sys /tmp/backout/Backout_EC1 ↵
chmod 755 /tmp/backout/Backout_EC1 ↵
6 Start the backout by entering the following commands:
cd /tmp/backout ↵
./Backout_EC1 ↵
7 The script then inspects the environment/platform on which it is executing.
Environment variables are used throughout the backout script so their
definitions need to be checked and verified. If it is discovered that required
environment variables are not defined, then the script displays an error
message and it exits. See ‘Environment and configuration’ on page 10-13.
The existence of a remote standby platform and the presence of Optical
Network Manager Application Platform are also determined at this point.
—continued—

Procedure 8-1
Backing out of the EC-1 software upgrade (continued)
Step Action
8 The environment information appears and a prompt asks if the information is

correct. For example:
---------------------------------------------------
- -
- TNMS EC-1 R19.1 Backout Procedure -
- -
---------------------------------------------------
Checking environment and configuration

Username :root
Upgrade TNMS EC-1 Release :19.1
Current TNMS EC-1 Release :<release>
SDHMS :/home/sdhmsusr/sdhms
SDHMS_LIB :/home/sdhmsusr/sdhms/lib
SDHMS_DATA :/home/sdhmsusr/sdhms/data
Standby installed :No
Standby platform :None
Are the details above correct?

To confirm the variable definitions, answer y (Yes) to the above question and
the script continues. If n (No) is input the script exits. See ‘Environment and
configuration’ on page 10-13.
Note: It is essential at this point to check the correctness of the various
definitions and statements, as they are used throughout the backout.
9 The script then checks the EC-1 status. At this point the EC-1 software should
be running on the EC-1 platform. The script detects whether this is true.
If EC-1 is not running, the script displays an error message and it exits. See 8
‘EC-1 not running’ on page 10-14.
If the EC-1 is running then the script continues by displaying this message:
---------------------------------------------------
- -
- -
---------------------------------------------------
Checking status of TNMS on <hostname>
TNMS is running
Checking that alarms are cleared.
Press [RETURN]
Press Return to continue with the backout.
—continued—

Procedure 8-1
Step Action
10 The script then determines if any alarms are current on the EC-1, and this
---------------------------------------------------
- -
- -
---------------------------------------------------
**********************************************
* *
* WARNING!!! *
* *
**********************************************
Key TOP NE Object Alarm Type

1 -3:-1 -3:-1 21:1 Warning Disk Capacity
2 35:1 12:5008 12:5008 INT-NE-Config_Corrupt
3 29:1 31:5005 31:5005 Comms fail alarm
4 30:1 32:5002 32:5002 RS-LOS
5 30:1 32:5002 32:5002 RS-LOS
6 30:1 32:5002 32:5002 PPI-TF
7 30:1 32:5002 32:5002 PPI-LOS
8 30:1 32:5002 32:5002 PPI-LOS
9 30:1 32:5002 32:5002 PPI-LOS
10 30:1 32:5002 32:5002 PPI-LOS
11 30:1 32:5002 32:5002 PPI-LOS
12 30:1 32:5002 32:5002 PPI-LOS
13 30:1 32:5002 32:5002 SYNC-Holdover
14 30:1 32:5002 32:5002 NE-Door_Open
15 30:1 32:5002 32:5002 PS-Door_Open
16 30:1 32:5002 32:5002 EA-No
18 30:1 32:5002 32:5002 NE-Ext_Card_Out
18 51:1 50:5006 50:5006 NE-Card_Fail
19 51:1 50:5006 50:5006 NE-Card_Fail
20 51:1 50:5006 50:5006 NE-Card_Out
21 51:1 50:5006 50:5006 NE-Unexpected_Card
22 51:1 50:5006 50:5006 INT-NE-Unexp...
23 51:1 50:5006 50:5006 RS-LOS
24 30:1 50:5006 50:5006 Comms fail alarm
Press [RETURN]
—continued—

Procedure 8-1
Step Action

---------------------------------------------------
- -
- -
---------------------------------------------------
A list of alarms are included in the back of the

upgrades document.These alarms listed should be
cleared from your network. Use your EC-1 to examine
and clear the different alarm types.
You may proceed with the backout provided you are

confident that any outstanding alarms will not prove
to be problematic during the network upgrade.
Do you wish to continue with the Backout [yn]?
Note: A list of alarms that must be cleared down before the backout can
continue is provided in ‘Alarms to clear from the network before an upgrade’
on page 11-1. Additionally, all alarms with a high priority MUST be cleared
before the upgrade commences. Use the EC-1 Alarm Monitor window to
determine the type of alarms in the network.
You are given the option to continue with the backout even if alarms are
present. This is at your own risk. If you choose not to continue until the alarms
are clear, enter n (No) to the above prompt and the script displays a message
and exits. See ‘Alarms present’ on page 10-14.
You may also choose to continue with the backout by entering y (Yes),
assuming all the major alarms are cleared.
8
—continued—

Procedure 8-1
Step Action
12 The script then attempts to disable the Standby feature.

a. If Standby is not supported, the following message appears:
---------------------------------------------------
- -
- -
---------------------------------------------------
No Standby machine to disable
Press [RETURN]
b. If Standby is supported, a message appears and Standby is then

disabled.
---------------------------------------------------
- -
- -
---------------------------------------------------
Disabling Remote Archives.

Remote archive disabled
Checking for standby EC-1

This EC-1 is configured to backup to a
standby EC-1 34.56.78.90
Comms available to 34.56.78.90
Press [RETURN]

Note: Standby is re-enabled after the backout is completed.
—continued—

Procedure 8-1
Step Action
13 The script then checks if the comms running on the manager are OK. The
following messages appear:
---------------------------------------------------
- -
- -
---------------------------------------------------
Testing comms process
Manager comms is OK
Press [RETURN]

14 The script then shuts down EC-1 Release 19.1
---------------------------------------------------
- -
- -
---------------------------------------------------
To revert back to the original EC-1, the current EC-1

must be shutdown
**********************************************
* *
* WARNING!!! *
* *
**********************************************
8
This will cause the EC-1 to lose visibility of the
network
Are you ready to shutdown the EC-1 [yn]?

The script asks if you are ready to shutdown the EC-1. If the reply is y (Yes)
then the EC-1 is shutdown. If the reply is n (No) then the script exits. See
‘Shutting down EC-1 Release 19.1’ on page 10-15.
—continued—

Procedure 8-1
Step Action
15 The backout script then removes the EC-1 Release 19.1 entries from the
/etc/inittab file before shutting down EC-1.
---------------------------------------------------
- -
- -
---------------------------------------------------
Removing EC-1 entries from /etc/inittab
TNMS EC-1 Release 19.1 is shutting down, Please wait...
Enter shutdown reason:

Enter EC-1 Release 19.1 backout.
The following information appears:
** Shutting Down EC-1 **
....5....10....15
** Shutdown Complete **
Checking EC-1 status, Please wait...
—continued—

Procedure 8-1
Step Action
16 If the EC-1 has not shut down successfully, the backout script shuts down any
remaining EC-1 R19.1 processes. For example, the following appears if the
shutdown has failed.
Process **** NOT RUNNING ****: ocsmain
Process **** NOT RUNNING ****: hci_NodeConnec
Process **** NOT RUNNING ****: hci_alarm_moni
Process **** NOT RUNNING ****: hci_ne_access
Process **** NOT RUNNING ****: hci_main
Process **** NOT RUNNING ****: hci_messages
Process **** NOT RUNNING ****: hci_reports
Process **** NOT RUNNING ****: hci_login_clie
Process **** NOT RUNNING ****: hci_login_serv
Process **** NOT RUNNING ****: eh_uoc_proc
Process **** NOT RUNNING ****: ma_rm_proc
Process **** NOT RUNNING ****: hcoserv
Process **** NOT RUNNING ****: ned
Process **** NOT RUNNING ****: ctr
Process **** NOT RUNNING ****: hcoserv
Process **** NOT RUNNING ****: ftfmain
Process **** NOT RUNNING ****: nehmain
Process **** NOT RUNNING ****: nehactlg
Process **** NOT RUNNING ****: nehpars
Process **** NOT RUNNING ****: nsvmain
Process **** NOT RUNNING ****: macrecv
Process **** NOT RUNNING ****: cma_cim_router
Process **** NOT RUNNING ****: cma_cim_man
Process **** NOT RUNNING ****: cnx
Process **** NOT RUNNING ****: timer_proc
Process **** NOT RUNNING ****: ma_am_proc
Process
Process
****
****
NOT
NOT
RUNNING
RUNNING
****:
****:
eh_proc
core_lm_proc
8
Process **** NOT RUNNING ****: gmp_init
17 The backout script then shuts down any MOA processes currently running on
the platform.
Shutting down MOA Processes
Shutdown MOA Process: mnsd 3012

Shutdown MOA Process: kms 3464
Press [RETURN]
—continued—

Procedure 8-1
Step Action
18 The script then re-installs the original release of EC-1 that was running before
the upgrade was performed.
---------------------------------------------------
- -
- -
---------------------------------------------------
TNMS EC-1 R19.1 shutdown complete
WARNING: EC-1 <release> will now be reinstalled
Do you wish to continue [yn]?
The script asks if you are ready to re-install the original release of EC-1. If the
reply is y (Yes) then the Release 19.1 is removed from the platform and the
original release is installed. If the reply is n (No) then the script exits.
19 The script then removes all new users added using EC-1 Release 19.1. For
example:
Reverting to EC-1 <release> Users
About to delete users:
Deleting r191_user1
Deleting r191_user2
Press [RETURN]
Note: If there are no users to delete, a message to indicate this appears
instead.
—continued—

Procedure 8-1
Step Action
20 The script then displays the following information.

---------------------------------------------------
- -
- -
---------------------------------------------------
R19.1 will be replaced with <release>
The script asks if you wish to replace EC-1 Release 19.1. If the reply is y (Yes)
then the Release 19.1 is removed from the platform and the original release
is installed. If the reply is n (No) then the script exits.
21 The script replaces Release 19.1 with the original release of EC-1. When
complete, the following message appears:
EC-1 <release> installed successfully.
Press [RETURN]
22 The backout procedure then tidies up the original release of EC-1.
---------------------------------------------------
- -
- -
---------------------------------------------------

8
The EC-1 R19.1 Backout Procedure has completed.

TNMS EC-1 is now available.
The backout procedure involves adding users removed at

R18

The script asks if you wish to add users removed at Release 19.1. If the reply
is y (Yes) then the users are added. If the reply is n (No) then the script exits.
—continued—

Procedure 8-1
Step Action
23 The backout procedure then adds any users for the original EC-1 that were
removed using Release 19.1.
---------------------------------------------------
- -
- -
---------------------------------------------------
Adding <release> users:

syseng01
admin
netsurv
slat
master
operator
Press [RETURN]
24 The script then displays the following information.
---------------------------------------------------
- -
- -
---------------------------------------------------
EC-1 Release <release> is now available.
Are you ready to initiate TNMS EC-1 <release> [yn]?

The script asks if you are ready to initiate the EC-1. If the reply is y (Yes) then
the EC-1 is started. If the reply is n (No) then the script exits. See ‘Starting the
original EC-1 release’ on page 10-16.
—continued—

Procedure 8-1
Step Action
25 The script then starts the original release of EC-1.

---------------------------------------------------
- -
- -
---------------------------------------------------
TNMS EC-1 Release <release> is starting

Purging IPC information for all owners
................
Please wait......
TNMS EC-1 startup successful
This script has completed.
EC-1 R19.1 Backout Procedure has finished successfully
Exit
26 The backout procedure for the EC-1 Release 19.1 upgrade is now complete.
—end—
end of chapter

9-1
Committing to an EC-1 upgrade 9-

This chapter details how to commit to using EC-1 Release 19.1 and remove
redundant upgrade files from the EC-1.
The commit procedure

The EC-1 commit procedure removes the original release of EC-1 from the
EC-1 platform. Once the EC-1 has been committed, a backout cannot be
performed.
Procedure 9-1
Committing to EC-1 Release 19.1
Step Action
If Then
xhost <Ip address of EC-1> ↵
export DISPLAY↵
3 Open an xterm from an existing UNIX window by entering the following
command. 9
xterm -l -lf /tmp/commit_log & ↵
window into a log file. This log file (commit_log) is stored in the /tmp
directory:
5 Start commit procedure by entering the following command:
/home/sdhmsusr/sdhms/bin/Commit_EC1 ↵
—continued—

9-2 Committing to an EC-1 upgrade
Procedure 9-1
Committing to EC-1 Release 19.1 (continued)
Step Action
6 The commit script prompts you for confirmation before removing

the original release of EC-1.
**********************************************
* *
* WARNING!!! *
* *
**********************************************
EC-1 Commit will remove Release <release> from the

platform.
*** THIS ACTION IS PERMANENT ***
Are you sure [y|n] ?

7 To continue with the commit enter y (Yes) to confirm deletion of the original
EC-1 release, or n (No) to abandon the deletion.
a. If confirmed, the original release of EC-1 is removed and the following
message appears.
EC-1 R19.1 Commit Procedure has completed successfully
b. If abandoned, the original release of EC-1 remains on the EC-1 platform.
The following message appears and the script exits.
Commit Procedure aborted
Refer to Upgrade Documentation to continue
ABORTING
—end—

Committing to an EC-1 upgrade 9-3
Removing the EC-1 redundant upgrade files from the EC-1 system
Once all upgrade procedures have been sucessfully completed and the EC-1
load has been commited, to ensure effective operation of the system, some
redundant upgrade files should be deleted, as described in
Procedure 9-2
Removing the redundant upgrade files from the EC-1 system
Step Action
1 Log into the EC-1 platform as user sdhmsusr.

2 From the CDE menu bar, select 'Application manager' -> 'Desktop Apps' ->
'Terminal'. When prompted, set the terminal type to 'xterm'.
3 In the 'xterm' window, type 'find / $ -name "ec1*.tar" -o -name "ec1*.tar.Z" $
-exec rm {} \;↵'
4 Type 'rm -rf /tmp/install↵'
5 Click on the CDE menu bar's 'Exit' button and click on 'OK' to confirm the log
out from CDE.
—end—
end of chapter

10-1
Solving EC-1 upgrade problems 10-

This chapter provides solutions to a number of problems that can arise during
The upgrade script (Upgrade_EC1)

The upgrade script (Upgrade_EC1) cannot execute if any of the following
conditions exist:
• Incorrect file permissions.
• Invalid upgrade user.
• Incorrect command line arguments.
Incorrect file permissions

Procedure 2-8, Procedure 3-8 and Procedure 4-11 tell you how to check the
file permissions. These scripts cannot execute if the file permissions are
incorrect.
Incorrect permissions on upgrade script

The following error arises if the permissions are incorrect on the script
Upgrade_EC1.
./Upgrade_EC-1: Permission denied
This is resolved by typing the following command in an xterm as user root

and rerunning the upgrade script.
cd /tmp/install ↵
chmod 755 Upgrade_EC1 ↵
If the script fails again at the same point then you have a problem with your
manager and you should contact the Nortel Networks Technical Support
Group.
10

10-2 Solving EC-1 upgrade problems
Incorrect permissions on the “global” script

The following error arises if the permissions are incorrect on the “global”
script.
**********************************************
* *
* WARNING!!! *
* *
**********************************************
global does not have execute permission.

Cannot proceed.
This can be resolved by typing the following command in an xterm as root

user and rerunning the upgrade script.
cd /tmp/install ↵
chmod 755 global ↵
Group.
Invalid upgrade user

An EC-1 R19.1 upgrade can only be performed by the root user. The
following error appears if a user other than root attempts an upgrade.
*********************** NO-ENTRY *************************
* *
* TNMS EC-1 Upgrade Procedure must be run by root user *
* *
*********************** NO-ENTRY *************************
This can be resolved by logging into the HP platform as root, and rerunning
the upgrade script.
Group.
Incorrect command line arguments

The upgrade script reports invalid command line arguments.
Usage: Upgrade_EC1 -U <upg_dir> -cdrom | -d <tar_dir>
Rerun the upgrade script with the correct arguments. For more details on
Upgrade_EC1 command line arguments, see ‘Upgrading the EC-1 software
to Release 19.1’ on Page 2-20, Page 3-22 and Page 4-28.

Upgrade directory problems

The upgrade scripts perform a number of checks on the temporary upgrade
directory.
Note: For the purposes of this section, it is assumed that the temporary
upgrade directory is /home/upgrade.
Upgrade directory already exists

If you decide not to remove the existing temporary upgrade directory then
you can answer n (No) to the following question, and the script exits with the
following message.
Note: In the example below, the temporary upgrade directory is defined as

/home/upgrade.
WARNING: Directory /home/upgrade already exists.
Do you want to remove it [yn] ? n
**********************************************
* *
* WARNING!!! *
* *
**********************************************
ERROR: Upgrade cannot continue until /home/upgrade is removed

ABORTING
To resolve this, either:
1 Rerun script answering y (Yes) to the question.

2 Rerun script using a temporary directory other than /home/upgrade. Use
a new directory name.
Upgrade directory cannot be removed

The following error appears if the upgrade script cannot remove the
temporary upgrade directory.
**********************************************
* *
* WARNING!!! *
* *
**********************************************
10
ERROR: Problems removing /home/upgrade
LEAVING Upgrade_EC1 WITH FAILURE
TO CONTINUE, RERUN THIS SCRIPT (Upgrade_EC1)
Rerun the script using a temporary directory other than /home/upgrade. Use
a new directory name.

manager and you should contact the Nortel Technical Support Group.
Release note problems

Different variables are checked for each release, the release number being
determined from the current EC-1 running on the HP platform. If the release
number cannot be determined then an error is displayed.
Possible problems are:

• Incorrect release number.
• Missing release note file.
Incorrect release number

If the release number is incorrect the following message appears.
**********************************************
* *
* WARNING!!! *
* *
**********************************************
Could not determine what version of TNMS is running

Possible corruption of /home/sdhmsusr/sdhms/Release_Note or
this is not Release 19.1.
Check which release of TNMS software you are running
If the version of software is not supported then upgrade your
TNMS software to a supported version
Otherwise recreate /home/sdhmsusr/sdhms/Release_Note
with correct software version
Contact Nortel Networks Technical Support Group for assistance.
Once the release note file contains the correct release number, rerun the
upgrade script in order to return to this point in the upgrade process. To fix the
release note file it may be necessary to reinstall your EC-1.
Group.

Missing release note file

If the release note file is missing the following error appears.
**********************************************
* *
* WARNING!!! *
* *
**********************************************
/home/sdhmsusr/sdhms/Release_Note does not exist

If the version of software is not supported then

upgrade your TNMS software to a supported version

upgrade script order to return to this point in the upgrade process. To fix the
release note file you may need to reinstall your EC-1.
Group.
Environment and configuration

The environment and configuration definitions are displayed during the
upgrade procedure for you to check. If you reply y (Yes) then the upgrade
continues. If you decide that the configuration details are incorrect then you
can answer n (No) to the following question and the script exits with the
following message.
Are the details above correct [yn] ?n
**********************************************
* *
* WARNING!!! *
* *
********************************************** 10
There appears to be an anomaly with the configuration of this
TNMS. It is vital that the information above is correct before
upgrade can continue.
Check the above information and the corresponding
configuration for this TNMS.

If the any of the information displayed is incorrect contact the Nortel

Networks Technical Support Group.
EC-1 not running

If the EC-1 is not running you are warned and the script exits.
**********************************************
* *
* WARNING!!! *
* *
**********************************************
TNMS appears NOT to be running

To get TNMS running again reboot <hostname>
Ensure that TNMS is running, is error free, and no alarms are
resent before rerunning this script.
You can resolve this by rebooting the Element Controller:
/etc/reboot ↵
Once the manager is running you should rerun this script in order to return to
this point in the upgrade process.
Group.
Alarms present
You are given the option to continue with the upgrade, even if alarms are
present. This is at your own risk. A list of alarms that must not be present is
given in ‘Alarms to clear from the network before an upgrade’ on page 11-1.
If you choose not to continue until the alarms are clear, then you can enter n
(No) to the prompt and the script exits, displaying a message:
Do you wish to continue with the upgrade [yn]? n
**********************************************
* *
* WARNING!!! *
* *
**********************************************
Cannot proceed until all traffic affecting alarms are cleared.

Clear the alarms and rerun the upgrade script to return to this position in the
upgrade process. Alternatively, rerun the upgrade script and answer y (Yes) to
the prompt.
Communications check
Upgrade_EC1 checks if comms is running on the manager. If the EC-1
comms is not running then the script exits with a failure status, and displays a
message telling you that the upgrade should NOT be performed until the
communications are OK.
**********************************************
* *
* WARNING!!! *
* *
**********************************************
Could not find the comms process (cma_cim_man)

Release 19.1 upgrade should NOT be performed until the
standard comms process is installed and running. It could be
that the process has been renamed. Change it back to
cma_cim_man and change the entry in /home/sdhmsusr/sdhms/
lib/gmp_init.conf
Installing EC-1 Release 19.1

Upgrade_EC1 installs the new Release 19.1 into a temporary directory on the
HP platform.
Not upgrading EC-1 to Release 19.1

If you decide not to install EC-1 Release 19.1 then you can answer n (No) to
the following question and the script exits with the following message.
About to install EC-1 Release 19.1 manager files.
Are you ready to continue [yn]?n
**********************************************
* *
* WARNING!!! *
* *
**********************************************
Cannot proceed until EC-1 Release 19.1 is installed

TO CONTINUE, RERUN THIS SCRIPT (Upgrade_EC1) 10
You can resolve this by rerunning script in order to return to this point in the
upgrade process and answering y (Yes) to the question.

Failing to upgrade EC-1 to Release 19.1

If the installation of EC-1 Release 19.1 fails, the script exits displaying the
following message.
**********************************************
* *
* WARNING!!! *
* *
**********************************************
Failed to install TNMS EC-1 R19.1

Shutting down the current EC-1 release

The upgrade script asks you if you are ready to shutdown the EC-1. If the
reply is y (Yes) then the EC-1 is shutdown. If the reply is n (No) then the
script exits displaying the following message on the screen:
To continue the upgrade, TNMS EC-1 Release <release> must
be shutdown.
**********************************************
* *
* WARNING!!! *
* *
**********************************************
This will cause the EC-1 to lose visibility of the Network

Are you ready to shutdown the EC-1 <release> [yn]? n
**********************************************
* *
* WARNING!!! *
* *
**********************************************
Cannot proceed until TNMS EC-1 <release> is shutdown

You cannot proceed until EC-1 is shutdown. Rerun the upgrade script in order
to return to this point in the upgrade process and answer y (Yes) at the
prompt.

Switching EC-1 software

The upgrade procedure automatically switches the old EC-1 release for the
new release. If you decide not to switch EC-1 releases then you can answer n
(No) to the following question and the script exits with the following message.
**********************************************
* *
* WARNING!!! *
* *
**********************************************
TNMS EC-1 <release> has been shutdown
<release> will now be replaced with R19.1
Do you wish to continue [yn]?n
**********************************************
* *
* WARNING!!! *
* *
**********************************************
Cannot proceed
You cannot proceed until EC-1 R19.1 is copied into the active directories.
Rerun the upgrade script in order to return to this point in the upgrade process
and answer y (Yes) at the prompt.
Starting EC-1 Release 19.1

The upgrade script asks you if you are ready to start the EC-1 Release 19.1. If
the reply is y (Yes) then the EC-1 is initiated. If the reply is n (No) then the
script exits displaying the following message on the screen.
**********************************************
* *
* WARNING!!! *
* *
**********************************************
Cannot proceed until TNMS is restarted

You cannot proceed until EC-1 Release 19.1 is started. Although the upgrade
script has stated failure, the upgrade has been successful. To restart EC-1
10
reboot the HP platform by entering the following command:
/etc/reboot ↵

The backout script (Backout_EC1)

The backout script (Backout_EC-1) can only execute if neither of the
following conditions is satisfied:
• Incorrect file permissions.
• Invalid user.
Incorrect file permissions

The backout script is described in Procedure 8-1. This script cannot execute if
the file permissions are incorrect.
Incorrect permissions on backout script

The backout script cannot execute if the file permissions are not correct. The
following error arises if the permissions are incorrect on the script
Backout_EC1.
./Backout_EC1: Permission denied.
This can be resolved by typing the following command in an xterm as root

user and rerunning the upgrade script.
cd /tmp/backout ↵
chmod 755 Backout_EC1 ↵
Group.
Invalid user
An EC-1 R19.1 backout can only be performed by the root user. The
following error is displayed if a user other than root attempts a backout.
************************ NO-ENTRY ************************
* *
* TNMS EC-1 BAckout Procedure must be run by root user *
* *
************************ NO-ENTRY ************************
This can be resolved by logging into the HP platform as root user, and
rerunning the backout script.
Group.
Original EC-1 directory problems

The backout scripts perform a number of checks on the original EC-1
directory:
• Check for upgrade configuration file.
• Check for original EC-1 directory.

Upgrade configuration file does not exist

If the Upgrade Config File does not exist the backout script exits displaying
the following message:
ERROR: Upgrade config file
/home/sdhmsusr/sdhms/logs/upgrade.conf not found
LEAVING Backout_EC1 WITH FAILURE
TO CONTINUE, RERUN THIS SCRIPT (Backout_EC1)
Original upgrade directory does not exist

If the original EC-1 directory cannot be established the backout script exits
displaying the following message.
ERROR: /home/sdhmsusr/sdhms/logs/upgrade.conf file corrupt
SDHMSUSR_OLD variable not found
Release note problems

Different variables are checked for each release, the release number being
determined from the current EC-1 running on the HP platform. If the release
number cannot be determined then an error appears.
Possible problems are:

• Incorrect release number.
• Missing release note file.
10

Incorrect release number

If the release number is incorrect the following message appears.
**********************************************
* *
* WARNING!!! *
* *
**********************************************

Possible corruption of /home/sdhmsusr/sdhms/Release_Note or
this is not Release 19.1.


backout script in order to return to this point in the backout process.
EC-1. You should contact the Nortel Networks Technical Support Group.
Missing release note

If the release note file is missing the following error appears.
**********************************************
* *
* WARNING!!! *
* *
**********************************************
/home/sdhmsusr/sdhms/Release_Note does not exist


backout script (Backout_EC1) in order to return to this point in the upgrade
process.
Group.
Environment and configuration

The environment and configuration definitions are displayed during the
backout procedure for you to check. If you reply y (Yes) then the backout
continues.
If you decide that the configuration details are incorrect then you can answer
n (No) to the following question and the script exits with the following
message.
Are the details above correct [yn] ?
---------------------------------------------------
- -
- -
---------------------------------------------------
**********************************************
* *
* WARNING!!! *
* *
**********************************************
There appears to be an anomaly with the configuration of this

TNMS. It is vital that the information above is correct
before upgrade can continue.
Check the above information and the corresponding
configuration for this TNMS.
If the any of the information displayed is incorrect contact the Nortel
Networks Technical Support Group.
10

EC-1 not running

If the EC-1 is not running you are warned and the script exits.
**********************************************
* *
* WARNING!!! *
* *
**********************************************
TNMS appears NOT to be running

To get TNMS running again reboot <hostname>
Ensure that TNMS is running, is error free, and no alarms are
present before rerunning this script.
Resolve this by rebooting the Element Controller:
/etc/reboot ↵
Once the manager is running you should rerun this script in order to return to
this point in the backout process.
manager and should contact the Nortel Networks Technical Support Group.
Alarms present
You are given the option to continue with the backout even if alarms are
present but it is at your own risk. A list of alarms that must not be present is
given in ‘Alarms to clear from the network before an upgrade’ on page 11-1.
If you choose not to continue until the alarms are clear then you can enter n
(No) to the prompt and the script exits, displaying a message:
Do you wish to continue with the backout [yn]? n
**********************************************
* *
* WARNING!!! *
* *
**********************************************
Cannot proceed until all traffic affecting alarms are cleared.

Clear the alarms and rerun the backout script to return to this position in the
backout process. Alternatively, rerun the backout script and answer y (Yes) to
the prompt.

Communications check
The backout script checks if communications are running on the manager. If
the EC-1 comms is not running then the script exits with a failure status, and
displays a message telling you that the upgrade should NOT be performed
until the comms is OK.
**********************************************
* *
* WARNING!!! *
* *
**********************************************
Could not find the comms process (cma_cim_man)
Release 19.1 backout should NOT be performed until the
standard comms process is installed and running. It could be
that the process has been renamed. Change it back to
cma_cim_man and change the entry in /home/sdhmsusr/sdhms/
lib/gmp_init.conf
Shutting down EC-1 Release 19.1

The backout script asks you if you are ready to shutdown the EC-1. If the
reply is y (Yes) then the EC-1 is shutdown. If the reply is n (No) then the
script exits, displaying the following message on the screen:
To continue the backout, TNMS EC-1 Release 19.1 must be
shutdown.
**********************************************
* *
* WARNING!!! *
* *
**********************************************
This will cause the EC-1 to lose visibility of the Network
Are you ready to shutdown the EC-1 R19.1 [yn]? n
**********************************************
* *
* WARNING!!! *
* *
**********************************************
Cannot proceed until TNMS EC-1 R19.1 is shutdown
10
You cannot proceed until EC-1 is shutdown. Rerun the backout script in order
to return to this point in the process and answer y (Yes) at the prompt.

Switching EC-1 software

The backout procedure automatically switches back to the original EC-1
release. If you decide not to switch EC-1 releases then you can answer n (No)
to the following question and the script exits with the following message.
**********************************************
* *
* WARNING!!! *
* *
**********************************************
TNMS EC-1 R19.1 has been shutdown

R19.1 will now be replaced with <release>
**********************************************
* *
* WARNING!!! *
* *
**********************************************
Cannot proceed
You cannot proceed until the original release of EC-1 is copied into the active
directories. Rerun the backout script in order to return to this point in the
process and answer y (Yes) at the prompt.
Starting the original EC-1 release

The backout script asks you if you are ready to start the original release of
EC-1. If the reply is y (Yes) then the EC-1 is initiated.
If the reply is n (No) then the script exits, displaying the following message
on the screen.
**********************************************
* *
* WARNING!!! *
* *
**********************************************
Cannot proceed until TNMS is restarted
You cannot proceed until the original release of EC-1 is started. Although the
script reports a failure, the backout has been successful.
To restart EC-1 reboot the HP platform by entering the following command:
/etc/reboot ↵
end of chapter

11-1
Solving NE upgrade problems 11-

This chapter provides solutions to a number of problems that can arise during
the upgrade of NEs within the network.
Alarms to clear from the network before an upgrade

The following list of alarms must all be removed from the network before an
upgrade, in order to gain network stability. The alarms are listed in decreasing
order of priority:
• Comms Fail to NE
• QECC Comms Fail
• STM Loss Of Frame
• STM Loss Of Signal
• Unit Fail
• Wrong Card
• Card Fault
• Card Fail
• Int Comms Fail
• Card Out
• Int Config Corrupt
• Int RAM Fail
11

11-2 Solving NE upgrade problems
No response from network hosts

If the system does not respond to a ping request, there may be several reasons.
Investigate these in turn until resolution if found:
Procedure 11-1
Resolving network host issues
Step Action
1 Check the IP addresses of the system are as thought. Use SAM to check
these values. To do this:
a. Start SAM
b. Select Networking/Communications.
c. Select Network Interface Cards. SAM displays the IP addresses and
subnet masks.
2 Check that the /etc/host file is correct. Edit the file using an editor such as
Hewlett Packard’s `vuepad`. On a host with a single LAN card, the format for
the machine entry is as follows:
<lan0 IP address> <hostname>
For example:
121.35.23.1 xyzhost
If the host has two LAN cards, the machine would have two entries:
<lan0 IP address> <hostname with `_0` appended>
<lan1 IP address> <hostname>
For example:
121.35.23.1xyzhost_0
121.35.23.1 xyzhost
If the LAN card settings are incorrect:
a. Log into HP platform as user root.
b. Initiate the following command in a UNIX Window:
/home/sdhmsusr/sdhms/bin/addenetcard ↵
c. You are given the option to enable the second LAN card. To continue
enter y (Yes). If you choose not to continue (i.e. by entering n (No) to the
above prompt), the script exits.
This script should only be run when a second ethernet
card is being added to a TN-1X Element Controller. It
should be run only following the enabling of the lan1
port using SAM.
Do you wish to continue? [yn]
—end—

Investigating NE communications failures

The following sections identify some methods for investigating
communications failures. The communications diagnostic tools can be used
to investigate communications problems in the network. If communications
problems are found, the communications logs should be dumped to a file for
analysis by Nortel Networks staff (see ‘Storing logs for further investigation’
on page 11-6).
ATTENTION
The OSI Comms Stack is now configured in the file osi_comms.conf instead
of mfmMAA.dat. Please refer to Optical Network Manager EC-1 User
Procedures, 323-1091-402 for further information on configuring this file.
Checking gateway NEs

Use the osishowis tool to establish the full Network Service Access Point
(NSAP) addresses of each level 1, or level 1 2 IS NE that the EC-1 can see
connected to the LAN.
Note: TN-1P NEs are not visible from this tool.

Procedure 11-2
Checking gateway NEs
Step Action
1 In an sdhmsusr UNIX window type:

osishowis ↵
2 If any of the gateway NEs do not appear then:
a. Check LAN connections.
b. Carry out a site visit on the gateway NE.
3 Check the LAN connection at the NE, the NE S/W is running and the LAN port
is enabled.
—end—
11

Checking transport layer communications to NE

Providing the gateway NEs are visible using the osishowis command, the
osiping tool can be used to verify that the transport layer to a NEs is intact.
Procedure 11-3
Checking transport layer communications
Step Action

osiping -l <NE MAC Address>↵
Where:
• <NE MAC Address> is the 12 digit address which can be obtained from
the subrack configuration window on EC-1. For example, 000075400a1b
• The -l switch identifies the use of the EC-1 IS-IS element controller.
2 Failure to ping the NE indicates either a lower layer mux communications
problem, or an area address problem.
a. If the NE is a gateway site visit the NE. Use the failure recovery section
for comms failures to recover the NE.
b. For remote NEs perform the actions described in ‘Checking gateway
routing tables’ on page 11-5 to identify whether the problem is at the NE
itself or further up the network.
3 If the NE can be pinged, then the association is being refused at the
application layer. Typically, this indicates an attempt to establish a second
connection. It is also possible that the area addresses being used by the EC-1
and NE are causing a problem.
a. Check that there are no other managers on the LAN which have gained
an association with the NE.
b. Check the area addresses stored at the EC-1 for each NE.
—end—

Checking gateway routing tables

If the comms failure is to a remote NE, then the osigetrib tool can be used on
the gateway NE to examine its routing information. There should be an entry
for every NE in the network.
Note: This tool cannot be used to examine TN-1P NEs.

Procedure 11-4
Checking gateway routing tables
Step Action

osigetrib -l <NE MAC Address> ↵
ATTENTION
Care must be taken when using this command as the subrack
controller might reboot.
Where:
• <NE MAC Address> is the 12 digit address which can be obtained from
the subrack configuration window on EC-1. For example, 000075400a1b.
2 The output is in the following format:
Destination Dist Flag Adjacency
Where:
• The Destination field shows all the NEs that can be seen by the gateway.
All the NEs in a network should be listed under listed field providing valid
comms paths have been set up.
• The Dist field is a cost field and indicates how far away the NE is into the
network.
—end—
11

Storing logs for further investigation

Use the osigetlog command to obtain any extra information which may be
useful to Nortel Networks staff. This tool should be run on any NEs which are
experiencing comms problems but have a comms link to the EC-1. The output
is stored to a file for further investigation.
Note: This tool can only be used for TN-1X, OPTera Metro 4100/OPTera
Metro 4150 (TN-4XE), and OPTera Metro 4200 (TN16XE) NEs.
Procedure 11-5
Storing logs for further investigation
Step Action

osigetlog -l <NE MAC Address> -f <file name> ↵
Where:
• <NE MAC Address> is the 12 digit address which you can obtain from
the subrack configuration window on EC-1. For example, 000075400a1b.
• <file name> is the name of the file in which the log is to be stored.
—end—
Note: Archive the file created onto tape to be analysed by Nortel Networks
staff.
end of chapter

12-1
Appendix A: EC-1 recovery from DAT12-

Backing up the EC-1 platform is a recommended part of the EC-1 upgrade
process (see Chapter 2 to Chapter 4).
In the unlikely event of an error occurring during the upgrade procedure, the
backup can be used after an EC-1 backout has been performed.
Recovering the EC-1 platform from a backup

CAUTION
Restricted utility
The fbackup command does not backup all UNIX files. It backs
up /etc, /home and /usr/users only. If this backup is to be
restored the EC-1 platform may need to be rebuilt from HP-UX
CD. Netscape, Acrobat etc will need to be reinstalled if the
EC-1 is rebuilt.
Procedure 12-1 shows you how to recover the EC-1 platform from a backup
digital audio tape (DAT).
Procedure 12-1
Recovering the EC-1 platform from a backup
Step Action
If Then
export DISPLAY↵
—continued—
12
12-2 Appendix A: EC-1 recovery from DAT
Procedure 12-1
Recovering the EC-1 platform from a backup (continued)
Step Action
3 Place the archive DAT in the tape drive.

4 Enter the following command in the UNIX xterm window:
cd / ↵
rm -rf /home/* /usr/users/* ↵
/etc/frecover -rf /dev/rmt/0m ↵
This recovers the archived EC-1 platform. This operation takes approximately
one hour to complete.
—end—
end of chapter

13
13-1
Appendix B: osi_comms.conf file 13-

This Appendix describes the contents and significance of the Optical Network
Manager EC-1 osi_comms.conf configuration file. This file supports Level 1
and Level 2 routing, and up to three Manual Area Addresses. You can also set
a priority level to determine the designated router for multiple router LAN
configurations.
CAUTION
Risk to Network Integrity
The information in this chapter briefly describes EC-1 features
which have a direct effect on traffic carried by your network.
You must be aware of the implications of any changes you
make to the osi_comms.conf file. For further advice and
information, contact Nortel Networks Technical Support.
The existing osi_comms.conf file is preserved when upgrading from R16

upwards to R17(in /home/sdhmsusr/sdhms/lib/). The existing Manual Area
Address is maintained and hence there is usually no reason to edit the file
during the upgrade process.
Note: Note when upgrading from HPUX 10 to HPUX 11 a new

osi_comms.config file will be created. Any existing configuration setting
will be lost. Refer to Appendix E HPUX 10 to HPUX 11 Migration, for
more information
It is possible to change the existing OSI communications arrangement within

your network. If changes are required, you will need to edit the
osi_comms.conf configuration file. The edit(s) are made as part of the
following upgrade procedures:
• Procedure 2-9, or
• Procedure 4-11,

13-2 Appendix B: osi_comms.conf file
CAUTION
After a Optical Network Manager EC-1 installation or upgrade
to Release 19.1, the Optical Network Manager EC-1 can
become the assigned Open System Interconnection (OSI)
intermediate system (IS) router. Although the Optical Network
Manager EC-1 Release 19.1 software contains this
functionality, Nortel Networks recommends that networks use
either:
• an external router (such as a Nortel Networks Access Stack
Node (ASN) Router), or
• another network element device which supports this
functionality (for example, either a Nortel Networks OPTera
Metro 4100/OPTera Metro 4150 or Nortel Networks OPTera
Metro 4200 Multiservice Platforms).
OSI over IP tunnelling

Note: This feature is not relevant to the upgrade process and must be
performed only after an EC-1 upgrade has been committed.
After a Optical Network Manager EC-1 installation or upgrade, you can

configure the Optical Network Manager EC-1 for ‘tunnelling’ of the OSI
management traffic through an existing IP network to head-end network
elements using statically configured OSI over IP tunnels.
The head-end multiplexers are capable of terminating the tunnels and

extracting the OSI data from the IP packets.
The OSI data is then routed to the correct destination through the existing OSI
network.
The OSI over IP facility is also implemented on the EC-1 by adding

additional parameters to the osi_comms.conf configuration file. Refer to the
Optical Network Manager EC-1 User Procedures 323-1091-402 for further
information on how to configure this facility.

Level 2 routing principles 13

Network elements (multiplexers) within an OSI based management network
are addressed from the EC-1 using a Network Service Access Point (NSAP)
address.
This NSAP address is made up of two portions, an Area Address portion and
a Media Access Control (MAC) address portion. The MAC address portion is
stored in the backplane SIMM and is globally unique to that system. The Area
Address portion of the NSAP is administratively assigned and is configured
within the multiplexer at commissioning and also on the EC-1 when added to
the span of control.
It is possible to configure up to three area addresses on a multiplexer with the

default being 490000.
Level 1 areas
An OSI Level 1 area is a group of multiplexers, which have a configured area
address in common.
Example:
• MUX1 is configured with the area addresses 490000 and 490001.
• MUX2 is configured with the area addresses 490000 and 490002.
• MUX3 is configured with the area address 490001.
MUX1 and MUX2 have the 490000 area address in common so they will
combine into the same Level 1 area.
Also, MUX1 and MUX3 have the 490001 area address in common so they
will combine into the same Level 1 area.
MUX2 will also form a combined Level 1 area with MUX3 due to their
common linkages with MUX1.
This means that the Level 1 Area for the three multiplexers is defined by the
set of area addresses 490000, 490001 and 490002 and any other multiplexers
directly connected which are configured with any of these area addresses will
also become part of the same area.
Multiplexers within the same area use the MAC address portion of their
NSAP address to route packets to the correct destination.

Level 2 subdomain
A Level 2 subdomain is used to route packets between Level 1 Areas.
A multiplexer which is performing a Level 2 routing function will examine

the area address portion of the destination address for a packet.
Based on this it will either forward it to another Level 2 router which is

routing for a that Level 1 area or, if it believes the destination for the packet is
within the Level 1 area which it is routing for, it will examine the MAC
address portion of the destination address and attempt to route the packet
using this.
It can be seen from this that the configuration of area addresses within an OSI
network must be undertaken with great care if Level 2 routing is to be used as
it is possible to lose connectivity to large portions of a network through
simple misconfiguration.
At EC-1R17, the EC-1 is capable of performing a Level 2 routing function.

EC-1 osi_comms.conf file configuration 13

You can configure the OSI data communications functionality through
modifications to the osi_comms.conf file.
The osi_comms.conf configuration file supports Level 1 and Level 2 routing,

and up to three Manual Area Addresses.
You can also set a priority level to determine the designated router for
multiple router LAN configurations. This configuration information is stored
in the osi_comms.conf file.
CAUTION
Nortel Networks recommends that the EC-1 should not be the
designated router in the Network. Use the [Priority] settings in
the OSI comms file to ensure that priority is set lower than the
designated router.
Note that the EC-1 is capable of functioning as the designated

Level 2 router within the OSI area. However, in order to ensure
communications are available if the EC-1 is off-line, it is
strongly recommended that either an external router is used, or
an NE which supports Level 2 routing (for example OPTera
Metro 4200).

Default state of the osi_comms.conf file

The default osi_comms.conf file shown below is located in the /home/
sdhmsusr/sdhms/lib/ directory of the EC-1.
#
# EC-1 OSI Comms stack configuration file
#
#
# no entry implies default i.e. LEVEL1 routing and LEVEL1_ONLY
circuit
# NB the area address section MUST have at least 1 entry
#
[Manual Area Addresses]
#
# MAA[1..3]= manual area addresses
#
MAA1=490000
[ISIS Routing]
#
# ISIS_ROUTER = LEVEL1 | LEVEL2
#
ISIS_ROUTER=LEVEL1
#
# PRIORITY_L1 = 1..254
PRIORITY_L1=60
#
PRIORITY_L2=60
[LAN Card Routing]

#
# LAN0 = LEVEL1_ONLY | LEVEL2_ONLY | LEVEL1_AND_2
#
LAN0=LEVEL1_ONLY
#
# End of configuration file
#
The following sections give an explanation of the significant (configurable)

parameter values. If you need to configure any of these values, do so in the
following procedure steps:
• Procedure 4-11,

Manual Area Addresses 13

This parameter(s) identifies the Manual Area Address of all the network
devices within the (Level 1) local network area (LAN). The default value is
490000 but this can be different depending on the network configuration.
The manual area address is preserved during the upgrade process.
You can define up to three manual area addresses on the EC-1.
If the EC-1 is performing Level 2 routing then these are the area addresses for
which it will route.
You can add additional manual area addresses and/or edit the values, for
example:
MAA1=490000
MAA2=490010
MAA3=490020
#
Note 1: the existing Manual Area Address is preserved during the upgrade.
Note 2: do not use any punctuation within the manual area address value.
ISIS Routing
The ISIS_ROUTER parameter can be configured to be LEVEL1 or LEVEL2.
This determines the ISIS routing level that the EC-1 will perform. By default
the Optical Network Manager EC-1 must be set to Level 1 routing only.
If there is more than one router/EC-1 on a LAN, you can set the priority for
that router within the osi_comms.conf file contained on that router. You can
set separate priorities for Level 1 and Level 2 routing using the priority values
contained in the following lines:
PRIORITY_L1=Px
PRIORITY_L2=Py
where x and y can be any numeric value between 1 and 254 (60 is the default).
Within a single network, the network device with the highest priority will be
the assigned router. Where two or more devices have the same priority the one
with the highest MAC address will be the assigned router.
Level 1 priority
The Level 1 priority determines whether the EC-1 will be Level 1 designated
router for the LAN that it is attached to. Most multiplexers are configured to
have a Level 1 priority of 64 so if the EC-1 is configured with a value less
than this then it will not become designated router. The default value is 60.
Level 2 priority
The Level 2 priority determines whether the EC-1 will be Level 2 designated
router for the LAN that it is attached to. The default value is 60.

LAN Card Routing

Each EC-1 contains a LAN card to enable routing over the LAN. You can set
the routing level for the LAN card contained on the EC-1 router using the LAN
card routing section within the osi_comms.conf file contained on that
router. Edit the values contained in the following line:
LAN0=<routing level>
where <routing level> can be any of the following:

LEVEL1_ONLY
LEVEL2_ONLY
LEVEL1_AND_2
LAN0 can be left commented out with a #, or contain a different value.
An EC-1 may have more than one LAN card, for example where one LAN
card is dedicated to EC-1 with NE (downline) communications and one LAN
card is dedicated to EC-1 with Optical Network Manager Application
Platform (upline) communications. In this case, LAN0 is always dedicated to
EC-1 with NE communications.
If the ISIS_ROUTER is set to Level 1 routing only, then this value will be
LEVEL1_ONLY. If the ISIS_ROUTER is set to Level 2 routing, then this
value will be LEVEL1_AND_2 if there are multiplexers within the span of
control which reside in the same area as the EC-1. This value will be
LEVEL2_ONLY, if all the multiplexers within the span of control are within
other Level 1 areas.
end of chapter

14-1
14
Appendix C: Migration of HP-UX 10.20 to
HP-UX 11i 14-
Introduction
This bulletin provides a guide for the migration of an EC-1 on an initial EC-1
Release on R16.2 , running on HP-UX 10.20, to a target release of EC-1
R16.2 running on HP-UX 11i June 2001.
Throughout Appendix D , HP-UX 11i June 2001 is used as the HP-UX 11i
install. The procedures are similar for migration from the following
• EC-1 R16.0, EC-1 R16.1, EC-1 R16.1 SP1 and EC-1 R16.2 SP1.
Table 14-1
Summary of procedures
Summary Procedure
Procedures to migrate a ’standalone’ EC-1 to HP-UX 11i Procedure 14-1 to

June 2001 Procedure 14-16
Procedure to install a temporary ’warm standby’ EC-1 Procedure 14-17 to

Procedure 14-27
Procedures to migrate primary and standby EC-1s to Procedure 14-28 to

HP-UX 11i Procedure 14-54
Installing DDS1 DAT drivers Procedure 14-55 to

Procedure 14-56
Changing the default RCA directory Procedure 14-57
Scheduling network configuration back ups to a remote Procedure 14-58

system
Note 1: Since the migration will require a full rebuild of the EC-1 platform,
remote software delivery from Optical Network Manager AP (ESWD) is
not supported.
Note 2: The Netscape browser is not supported on HP-UX 11i.

14-2 Appendix C: Migration of HP-UX 10.20 to HP-UX 11i
Note 3: The term 'standalone' will be used generically, to describe a

standalone EC-1, a cold standby EC-1, or an EC-1 that backs up to an
RCA.
CAUTION
HP-UX 11i is not supported
These procedures should not be applied to Optical Network
Manager EC-1 running on HP 715/100, B132L and B132L+
platforms as they do not support HP-UX 11i.
Supported preconditions:
• Standalone EC-1 running R16.2 on HP-UX 10.20, where a back up EC-1
platform has not been provided for the duration of the upgrade.
• Standalone EC-1 running R16.2 on HP-UX 10.20, where a back up EC-1
platform has been provided for the duration of the upgrade.
• Standalone EC-1 running R16.2 on HP-UX 10.20, backing up to an RCA
server.
• Primary and warm standby EC-1s running R16.2 on HP-UX 10.20, with
and without N+1 protection.
• A resilient pair of primary and hot standby EC-1s running R16.2 on
HP-UX 10.20.
Post conditions:
• Standalone EC-1 running R16.2 on HP-UX 11i operating system.
• Primary and warm standby EC-1s running R16.2 running on HP-UX 11i
operating system, with and without N+1 protection.
• A resilient pair of primary and hot standby EC-1s running R16.2 running
on HP-UX 11i operating system.
Requiremets:
• A network configuration freeze must be maintained until all the required
migration procedures have been applied.
• A 4 hour maintenance window is required for each EC-1 platform that is
to be migrated to HP-UX11i.
Note: If a temporary standby EC-1 is supplied to manage the network for
the duration of the migration, an additional 3.5 hours will be required to set
it up and build it, although this can be done prior to the maintenance
window.
• The passwords for the 'root', 'sdhmsusr' and 'syseng01' logins must be
known.
• Optical Network Manager EC-1 R16.2 running on an HP B180L, B2600,
C3600 or a C3750 platform.
• Prior to the migration to HP-UX 11i all reach through sessions to the target
EC-1s and to the NEs in their span of control, from any Optical Network
Manager AP must be closed.

• If the migration is to be performed on a standalone EC-1 with no back up

EC-1 present, this will require a loss of visibility to all the Network
Elements during the migration period, a period of approximately 3 hours.
• If the upgrade is to be performed on a Primary/Backup configuration and
the EC-1s are not co-located then an engineer must be present at both the
EC-1 locations.
14
• The software specified in below must be available at each location where
these procedures are being applied.
• 3 DAT tapes, must be available at each location where these procedures are
applied (90m DDS1 Tape as minimum).
CAUTION
DAT tape compatible
It is important to ensure that these DAT tapes are compatible
with the DAT drive format in the target EC-1 platform, e.g.
DDS 2 or DDS 3.
References:
It is advised that the following documents are available during the course of
this procedure:
• NTP 323-1091-202 - Optical Network Manager EC-1 R16.2 Installation

Procedures
• NTP 323-1091-230 - Optical Network Manager EC-1 R16.2 Upgrade
Procedures
• NTP 323-1091-402 - Optical Network Manager EC-1 R16.2 User
Procedures
Required Nortel Networks software and PEC Codes
• HP-UX 11i June 2001 NTNM51ZCAF - Operating Environment Disk1.
• HP-UX 11i June 2001 NTNM51ZDAF - Operating Environment Disk2
• HP-UX 11i June 2001 NTNM51ZEAF - Documentation
• Optical Network Manager EC-1 R16.2 NTQJ30MW - CDROM
Supported hardware
The following procedures are supported on the following HP platforms.
• B180L with 9GB hard drive

• B2600
• C3600
• C3750
CAUTION
Hardware not supported
Applying these procedures to the B180L platform with a 4GB
hard drive is not supported.

Migration to HP-UX 11i on a standalone EC-1

The following procedures must be applied to any standalone EC-1 to ensure
its sucessful migration from HP-UX 10.20 to HP-UX 11i June 2001.
Table 14-2
Migration to HP-11i on a standalone EC-1
Procedure Description
Procedure 14-1 Validate platform configuration data
Procedure 14-2 Review EC-1 release level
Procedure 14-3 Validate the DAT drive on a standalone EC-1
Procedure 14-4 Backing up NE software loads
Procedure 14-5 Backing up network configuration data
Procedure 14-6 Shut down the EC-1 platform
Procedure 14-7 Booting the HP C3750/C3600/B2600/B180 platforms from the

CD-ROM drive
CD-ROM drive
Procedure 14-9 Loading LAN configuration script
Procedure 14-10 Configuring the second Ethernet port
Procedure 14-11 Validate LAN cabling
Procedure 14-12 Reinstall Optical Network Manager EC-1 R16.2 application

software
Procedure 14-13 Validating the EC-1 application
Procedure 14-14 Restoring network configuration data
Procedure 14-15 Restoring NE software loads
Procedure 14-16 Validation of NE association
Validate platform configuration data

As part of this overall procedure of migrating from HP-UX 10.20 to HP-UX
11i there is a cold installation of HP-UX 11i. During an HP-UX 11i
installation procedure all data on the EC-1 hard drive will be removed.
Consequently, from your network administrator, it is necessary to capture the
following data for the target EC-1, prior to proceeding with the migration
from HP-UX 10.20 to HP-UX 11i.
• hostname,

• LAN0 IP address
• LAN0 subnet mask
• LAN1 IP address
•
•
LAN 1 subnet mask
IP address of the default gateway, if it is remote from the target EC-1 (Note,
14
if there is no remote gateway for lan1 on the target EC-1 the default
gateway IP address should be the same as the IP address for lan1).
• 'root' user password
• 'sdhmsusr' password
• 'syseng01' user password
HP Platform
Name:
IP Address:
Subnet mask:
Default gateway:
’root’ user password:
’sdhmsusr’ user password:
’syseng01’ user password:
CAUTION
Optical Network Manager EC-1 does NOT support lan0 and
lan1 IP addresses in the same subnet. If the first three octets of
the IP addresses of lan0 and lan1 are the same and the subnet
masks of lan0 and lan1 are also the same, halt the migration to
HP-UX 11i and contact Nortel Technical Support.
Procedure 14-1
Step Action
1 Ensure that the EC-1 platform is correctly connected to the network and
powered on. (If necessary, refer to the connectivity diagrams Figure 14-1 on
page 14-49, Figure 14-2 on page 14-50 and Figure 14-3 on page 14-50.)
2 Log into the EC-1 platform as user sdhmsusr
'Terminal'. When prompted, set the terminal type to 'xterm'. (On VUE
desktops, select 'General' -> 'Utilies' -> 'Xterm'.)
4 Maximise the 'xterm' via the 'maximise' check button on its top right corner.
5 At the shell prompt, type 'more /etc/rc.config.d/netconf<RETURN>'. (Use the
'spacebar' to page through the file, as required.)
—continued—

Procedure 14-1
Validate platform configuration data (continued)
Step Action
6 Note the 'netconf' entry for 'HOSTNAME'. Check that this is exactly the same
as that provided by the network administrator. If not, halt the migration to
HP-UX 11i until the discrepancy is resolved.
7 Note the 'netconf' entry for 'LOOPBACK_ADDRESS'. This must be
'127.0.0.1'. If not, contact your network administrator and halt the migration to
HP-UX 11i, until the discrepancy is resolved.
8 Note the 'netconf' entry for 'IP_ADDRESS[0]'. Check that this is exactly the
same as the 'lan0' IP address provided by the network administrator. If not,
halt the migration to HP-UX 11i until the discrepancy is resolved.
9 Note the 'netconf' entry for 'SUBNET_MASK[0]'. This must be
'255.255.255.0'. If not, contact your network administrator and halt the
migration to HP-UX 11i, until the discrepancy is resolved.
10 Note the 'netconf' entry for 'ROUTE_GATEWAY[0]'. Check that this is exactly
the same as the IP address of the gateway route for the target EC-1 provided
by the network administrator. If not, halt the migration to HP-UX 11i until the
discrepancy is resolved.
12 Note the 'netconf' entry for 'SUBNET_MASK[1]'. Check that this is exactly the
same as the 'lan1' subnet mask provided by the network administrator. If not,
13 Press the 'spacebar' until the scrolling of the 'netconf' file ends and the shell
prompt returns.
14 At the shell prompt, type 'more /etc/hosts<RETURN>'. (Use the 'spacebar' to
page through the file, as required.)
15 Ensure that, in the 'hosts' file, there is a single entry for the lan0 IP address,
followed by a 'official hostname' field containing '<hostname of target
EC-1>_0'. If there are duplicate entries for the lan0 IP address with different
'official hostname' fields, or if a hostname field of '<hostname of target
EC-1>_0' is evident beside different IP addresses, halt the migration to
16 Ensure that, in the 'hosts' file there is a single entry for the lan1 IP address,
followed by an 'official hostname' field containing '<hostname of target
EC-1>'. If there are duplicate entries for the lan1 IP address with different
'official hostname' fields, or if a hostname field of '<hostname of target EC-1>'
is evident beside different IP addresses, halt the migration to HP-UX 11i until
the discrepancy is resolved.
17 Ensure that, in the 'hosts' file there is an entry: '127.0.0.1 localhost loopback'.
If not halt the migration to HP-UX 11i until the discrepancy is resolved.
18 If no discrepancies in the 'netconf' and 'hosts' files are evident, close the
'xterm' window and log out of CDE/VUE.
—end—

Review EC-1 release level on a standalone EC-1

The migration to HP-UX 11i is supported at EC-1 R16, R16.1 and R16.2 and
their respective Service Packs. Hence it is necessary to validate the EC-1
release on the target EC-1s. On the target EC-1 that is to be migrated to
HP-UX11i, perform Procedure 14-2 below:
14
Procedure 14-2
Review EC-1 release level
Step Action
1 Log into the EC-1 platform as user syseng01

2 From the CDE menu bar select 'Application Manager' -> 'PersonalToolbox'
(On VUE desktops, simply open the 'Personal Toolbox'.)
3 Double click on the EC-1 icon in the Personal Toolbox to start an EC-1 GUI
session.
4 From the EC-1 main menu, select 'System Information'.
5 Check that the EC-1 'Software Version' is a version of R16 e.g.
'TNMS_EC-1.16X.xx'. If not, log out of the EC-1 session, via the 'Log out'
button on the 'Main' menu. Then log out of CDE/VUE and apply the EC-1
upgrade procedures described in NTP 323-1091-230, Optical Network
Manager EC-1 R16.2 Network Upgrade Procedures. (These are available in
PDF format on the Optical Network Manager EC-1 R16.2 CD-ROM,
NTQJ30MW.). If it is, log out of CDE/VUE.
—end—

Validate the DAT drive on a standalone EC-1

CAUTION
Correct operation of the DAT drive and the compatibility of the

available DAT tapes are crucial to preventing the loss of
network configuration data and NE software. Procedure 15-3
below, MUST be applied at this point. If this procedure fails,
you MUST contact Nortel Technical Support before
proceeding.
Procedure 14-3
Validate the DAT drive on a standalone EC-1
Step Action

desktops, select 'General' -> 'Utilies' -> 'Xterm'.).
3 Insert a blank, compatible DAT tape into the EC-1 DAT drive and wait for the
lights on the drive to stop flashing.
4 In the 'xterm' window, type 'cd /tmp<RETURN>'
5 In the 'xterm' window, type 'touch /tmp/test.txt<RETURN>'
6 In the 'xterm' window, type 'rm -rf /tmp/test.txt<RETURN>'
7 In the 'xterm' window, type 'echo "This is a test!" > /tmp/test.txt<RETURN>'
8 In the 'xterm' window, type 'cat /tmp/test.txt<RETURN>'. If there is no output
from this command, repeat steps 4 - 8 before proceeding.
9 In the 'xterm' window, type 'tar cv /tmp/test.txt<RETURN>. Wait until the DAT
drive lights stop flashing and screen output indicats that the archive is
complete. (If these events are not observed, contact Nortel Technical
Support.)
10 In the 'xterm' window, type 'rm -rf /tmp/test.txt<RETURN>'
11 In the 'xterm' window, type 'tar xv /tmp/test.txt<RETURN>. Wait until the DAT
drive lights stop flashing and screen output indicats that the archive is
complete. (If these events are not observed, contact Nortel Technical
Support.)
12 In the 'xterm' window, type 'cat /tmp/test.txt<RETURN>'. If there is no output
from this command, contact Nortel Technical Support. Otherwise, repeat
steps 3 - 12 above using a second available DAT.
13 Log out of CDE/VUE
—end—

Backing up NE software loads

Consequently, it is necessary to ensure that all installed NE software loads are
preserved.
14
Procedure 14-4
Backing up NE software loads
Step Action

3 Insert the first DAT tape validated in Procedure 15-3 above, into the EC-1
DAT drive and wait for the lights on the drive to stop flashing.
4 In the 'xterm' window, type 'tar cv /home/sdhmsusr/sdhms/data/
NE_load<RETURN>'
5 Wait for the on-screen messages to complete and the lights on the DAT drive
to stop flashing.
6 Remove the DAT tape from the DAT drive
7 Clearly label the DAT tape with the hostname of the current EC-1 platform
and the legend 'NE s/w loads'.
—end—

Backing up network configuration data

Consequently, it is necessary to ensure that all network configuration data is
preserved
Procedure 14-5
Backing up network configuration data
Step Action

3 Insert the second DAT tape validated in Procedure 15-3 above, into the EC-1
4 In the 'xterm' window, type '/home/sdhmsusr/sdhms/bin/
.db_archive<RETURN>'
to stop flashing.
and the legend 'Database archive'.
8 Log out of CDE/VUE.
—end—

Shut down the EC-1 platform

To install the new HP-UX 11i it is necessary to shut down the EC-1 platform,
via Procedure 14-6, below:
Note: On a 'standalone' EC-1 platform there will now be a loss of network

visibility for the rest of the migration to Optical Network Manager EC-1 14
R16.2 running on HP-UX11i (Approximately 4 hours.)
Procedure 14-6
Shut down the EC-1 platform
Step Action
1 Log into the EC-1 platform as user root.

3 At the shell prompt type '/etc/reboot -h'. Wait until the platform has completed
its power down.
Install HP-UX 11i
This procedure describes how to install the Hewlett-Packard HP-UX 11i
operating environment.
Note 1: Optical Network Manager EC-1 only supports the installation of HP-UX 11i from
local CD-ROM.
Note 2: HP-UX 11i only supports HP CDE. HP-UX 11i does not support HP-VUE
Note 3: Optical Network Manager EC-1 with HP-UX 11i is supported on the following
platforms B180L, B2600, C3600, C3750
Note 4: Optical Network Manager EC-1 with HP-UX 11i is not supported on B132L or
B132L+
Note 5: The Netscape browser is not supported on HP-UX 11i.
CAUTION
Procedure 14-7 to Procedure 14-8 will destroy all current data on the
EC-1 hard drive. Check that Procedure 14-1 to Procedure 14-5 have
been applied and that a network configuration freeze is in place
before conducting Procedure 14-7

Procedure 14-7
Booting the HP C3750/C3600/B2600/B180 platforms from the CD-ROM drive
Step Action
1 Push in the power switch on the monitor. The LEDs on the front of the monitor
light up to indicate that power is on.
2 Push in the power switch to the Workstation. The power LED lights up to
indicate that the power is on.
3 Insert “HP-UX 11i June 2001 NTNM51ZCAF”, disk 1 of 2 into the DVD/
CD-ROM.
4 The following messages are displayed:
To select a new Graphics Monitor Type press the [TAB] key
now, otherwise EXIT by entering other key (or will time out
in 15 seconds)
Allow this to time out
5 Another message is then displayed:
Press any key or wait 10 seconds
Before this period times out, press any key.
6 The workstation Main Menu is displayed, as shown below
------Main Menu------
Command Description
------------ ---------------
BOot [PRI|ALT|<path>] Boot from specified path
PAth [PRI|ALT|CON|KEY] [<path>] Display or modify a path
SEArch [DIsplay|IPL] [<path>] Search for boot devices
…
…
HElp [<menu>|<command>] Display help for menu or command
RESET
-------------
Main Menu: Enter Command>
Search for SCSI devices using the following command:
search ↵
—continued—

Procedure 14-7
Booting the HP C3750/C3600/B2600/B180 platforms from the CD-ROM
drive (continued)
Step Action
14
SCSI devices are then identified. As a typical example:
Searching for Potential Boot device.
This may take several minutes
To discontinue, press ESCAPE
Path Device Path Device Type

----- ------------ ------------
P0 scsi.6.0 IBM DORS-32165
P1 scsi.4.0 TOSHIBA CD-ROM XM-540ITA
P2 scsi.3.0 HP HP35480A
7 Boot from the SCSI device that is identified as the DVD/CD-ROM drive. In
the above example, where the CD-ROM is path p1, you would type:
boot p1 ↵
8 The system displays the following question:
Interact with IPL (Y, N, Q)? >
Type:
n ↵
9 The operating system is then loaded from the CD-ROM drive. This process
is detailed in Procedure 14-8.
—end—

Procedure 14-8
Loading the HP-UX 11i operating environment from the DVD/CD-ROM drive
Step Action
1 Boot the platform from the DVD/CD-ROM drive (see Procedure 14-7)
2 A display of all available keyboard drivers is appears. Select the option you
require (for example "PS2_DIN_UK_English" ), and press Return. Press
Return again to confirm your selection.
3 The boot process starts, and the following menu is displayed.
Hardware Summary:System Model: 9000/778/B180L
+---------------------------------------------------+ [Scan Again]
|Disks: 1(8.5GB) | Floppies: 0 | Land Cards: 2 |
|CD/DVDs: 1 | Tapes : 1 | Memory : 256Mb|
|Graphics Ports: 1 | IO Buses: 3 | CPUs : 1 |
+---------------------------------------------------+ [H/W
Details]
[ Install HP-UX ]
[ Run a Recovery Shell ]
[ Advanced Options ]
[ Reboot ] [ Help ]
4
Note: If two LAN cards are installed, HP-UX 11i contains a new feature
where the system dynamically assigns device drivers to the two LAN
cards. LAN0 can be assigned to either the motherboard or the peripheral
LAN card. Take care to ensure that the LAN cable connected to LAN0
(either motherboard or peripheral) is connected to the head-end mux. If
this is not the case, swap the LAN cables before proceeding with this
installation.
Select the H/W Details tab in the menu above to find the LAN configuration.
LAN Hardware
Interface Path Type
Lan0 8/0/20/0 HP PCI 10/100 Base-TX Core
Lan1 8/0/1/0 HP AS230A/B5509BA PCI/10/100/Base-TX Addon
—continued—

Procedure 14-8
Loading the HP-UX 11i operating environment from the DVD/CD-ROM
drive (continued)
Step Action
14
In the example above, the LAN0 is attached to the motherboard LAN card.
The "Core" card denotes the LAN card attached to the motherboard.
LAN Hardware
Interface Path Type
Lan0 8/0/1/0 HP AS230A/B5509BAPCI/10/100/Base-TX Addon
In the example above, the LAN0 is attached to the peripheral LAN card. The
"Addon" card denotes the LAN card attached to the peripheral port.
5 The first option (install HP-UX) will be displayed as reverse video. Select the
option by pressing Return or Enter.
6 The following User Interface and Media Options screen is now displayed.
User Interface and Media Options
This screen lets you pick from options that will determine if an Ignite-UX
Server is used, and your user interface preference.
Source location options:
[ * ] Media Only Installation
[ ] Media with Network enabled (allows use of SD depots)
[ ] Ignite_UX Server based installation
User Interface Options:

[ ] Guided Installation (recommended for basic installs)
[ * ] Advanced Installation (recommended for disk and
filesystem management)
[ ] No User Interface - use all the defaults and go
Hint: If you need to make LVM size changes or want to set the
Final networking parameters during the install, you will
Need to use the Advanced mode (or remote graphical interface)
[ OK ] [ Cancel ] [ Help ]
—continued—

Procedure 14-8
drive (continued)
Step Action
From the Source Location Options ensure that "Media only installation" is
selected. For User Interface Options select "Advanced Installation".
Continue the installation by selecting "OK" and pressing Return or Enter.
7 The install utility continues by displaying the configuration menu.
Ensure that the following options are selected on the Basic configuration
screen:
/---------\
| Basic |
|
\-------------------------------------------------------------
Configurations:[ HP-UX B.11.11 Default->] [ Description…]
Environments :[ see below ->] (HP-UX B.11.00)
[ Root Disk …] QUANTUM_ATLAS5-9WS, 8/0/19/0.6.0, 8678 M
File System :[ Logical Volume Manager (LVM) with HFS->]
[Root Swap (MB)… ] see belowPhysical Memory (RAM) = see below
[Languages…] English [ Keyboards… ]
| |
\------------------------------------------------------------/
[ Show Summary … ] [ Reset Configuration ]
--------------------------------------------------------------
[ Go! ] [ Cancel ] [ Help ]
--------------------------------------------------------------
Note : If required, can also use VxFS file system support
—continued—

Procedure 14-8 (continued)
Step Action
Move between fields using the TAB key. Press Return on a selected field
to display its menu. Use the arrow keys to highlight an option from the 14
menu, and Return to select it
8 From the configuration menu, select the tab labeled System, using the TAB
key and <RETURN> so that the screen below appears. Then set the Final
System Parameters option to Ask at first boot
/--------\
| System |
/ \-------------------------------------------
Final System Parameters: [ Ask at first boot--> ]
All of the system parameters will be collected interactively

During the initial boot of the system.
If you wish to specify these parameters now, please select

"Set parameters now".
--------------------------------------------------------
[ Show Summary… ] [ Reset Configuration ]
--------------------------------------------------------
[ Go! ] [ Cancel ][ Help ]
--------------------------------------------------------
—continued—

Procedure 14-8
drive (continued)
Step Action
9 From the configuration menu, select the tab labelled File System, using the
TAB key and Return so that the following screen appears
/ --------- \
|File System|
/ \---------------------------------
Mount Dir Usage Size(MB) %Used Group S
/stand HFS 512 4 vg00 F

Primary SWAP+D 512 0 vg00 R
/ HFS 3000 54 vg00 F
/home HFS 4628 0 vg00 R
/
Usage: [ HFS -->] Group: [ vg00 --> ] Mount Dir: /home
Size: [ Range MB -->] Min: 0 Max: 4628 Avail 20MB
[ Add/Remove Disks... ] [ ----Additional Tasks---- -->]

| |
\------------------------------------------------------/
[Show Summary... ] [Reset Configuration]
--------------------------------------------------------
[Go! ] [Cancel] [ Help ]
--------------------------------------------------------
Enter the values given in Table 14-3 for your system into the table shown on
the screen.
Table 14-3
System Parameters
Machine Environments Partition Sizes Physical

Memory
B180L HP-UX 11i Root..............................512 256

with 9G Base OS - 32bit /..................................3000
hard drive June 2001 /stand...........................512
/home.........................4648
B2600 HP-UX11i Root............................2048 256

with 18G Base OS - 64bit /..................................3000
/home.....................~11800
—continued—

Table 14-3
System Parameters
NewB2600 HP-UX11i Root............................2048 512

with 18G Base OS - 64bit /..................................5000
/home.......................25000
14
C3600 HP-UX11i Root............................2048 1024
with 18G Base OS - 64bit /..................................3000
/home......................~11800
C3750 HP-UX11i Root............................2048 1024

with 36G Base OS - 64bit /..................................5000
/home......................~27160
RP34x0 HP-UX11i Root....................1024 (VxFS) 1024

with 36G Base OS - 64bit Root Swap..........3880 (swap)
hard drive June 2004 /var......................3072 (VxFS)
/usr......................4800 (VxFS)
/tmp.....................2048 (VxFS)
/stand......................400 (HFS)
/home................11800 (VxFS)
/opt......................6632 (VxFS)
RP34x0 HP-UX11i Root....................1024 (VxFS) 1024

with 72G Base OS - 64bit Root Swap..........4096 (swap)
hard drive June 2004 /var......................8704 (VxFS)
/usr......................5000 (VxFS)
/tmp.....................2048 (VxFS)
/stand......................400 (HFS)
/home................22056 (VxFS)
/opt....................10632 (VxFS)
free unpartitioned space

17600
10 You must remove all other file systems (/tmp, /opt, /usr and /var) by
highlighting the directory and selecting the Remove option.
Configure the following file systems as shown in Table 14-3.
Set the /stand, primary and / file systems to the values shown in the table
above. In larger workstations, you can set the /home file system to the
remaining disk space. After reconfiguring each file, select modify to save the
changes.
—continued—

Procedure 14-8
drive (continued)
Step Action
11 When you have entered all file system modifications have been completed
select Go! and press Return or Enter.
12 The confirmation screen now appears. If you are installing over a previous
version of HP-UX you will also see the following warning.
Itool Confirmation
All data will be destroyed on the following disks:
Addr Disk Size (MB) Description
/--------------------------------------------------------
| 8/0/19/0.6.0 8678 MB QUANTUM_ATLAS5-9WS |
| |
\-------------------------------------------------------
The results of the pre-install analysis are:
/-------------------------------------------------------\
| WARNING: The disk at: 8/0/19/0.6.0 (QUANTUM_ATLAS5-9WS) |
| appears to contain a file system and boot area. Continuing |
| the installation will destroy any remaining data on this disk
\------------------------------------------------------/
Select Go!
The installation routine begins. When the routine has finished the system
reboots. The routine and reboot takes approximately 60 minutes on a B180L
platform.
The following screen appears:
/------------------------------------------------------\
USER INTERACTION REQUIRED:
To complete the installation you must now insert the
"BXXXX 11i OE CD"
Once this is done, press the < Return > key to continue:
\------------------------------------------------------/
—continued—

Procedure 14-8
drive (continued)
Step Action
14
13 Remove “HP-UX 11i June 2001 NTNM51ZCAF”, disk 1 of 2. Then insert the
second boot CD-ROM ("HP-UX 11i June 2001 NTNM51ZDAF", disk 2 of 2)
into the CD-ROM drive and continue with the installation.
The screen showing all keyboard drivers available appears again.
require (for example "PS2_DIN_UK_English" ), and press Return.
Press Return again to confirm your selection.
15 A geocustoms screen appears. Choose a suitable language.
Select the Yes button to continue.
16 The Ask DHCP dialogue will then appear, offering to obtain networking
information via DHCP. Select the No button to continue.
17 Enter the system hostname.
18 The workstation name is displayed for confirmation. Confirm this by selecting
the Yes button.
19 A time zone dialogue is displayed. The following options are available:
• North America or Hawaii
• Central America
• South America
• Europe
• Africa
• Asia
• Australia, New Zealand
Click on the required location, and click on the OK button.
—continued—

Procedure 14-8
drive (continued)
Step Action
20 A more specific time zone dialogue is then displayed, based on your first
selection. Click on the required time zone, and click on the OK button.
21 The selected time zone is displayed. Confirm this using the OK button.
22 A date and time dialogue is then displayed. Either:
a.Confirm the displayed time and date with the OK button.
b.Reject the time and date displayed. You are then prompted to enter new
details.
Enter these and confirm them when requested.
23 The root password is requested. Enter this password, then re-enter it to
confirm it for use.
Note: Steps 23 -29 may or may not appear depending on user choices. If
they do not appear then goto step 30.
24 If there is more than one LAN card installed the following dialogue is
displayed:
Choose LAN interface
Before setting an IP address or using DHCP, please choose which network
interface card to use from the list below. The card should now be physically
connected to the network. Other network interfaces may be configured using
SAM after the system has booted. A * indicates the Lan that was used for
installing HP-UX, if known.
LAN Hardware
Interface Path Type
Lan1 8/0/1/0 HP AS230A / B5509BA PCI 10/100 Base-TX Addon
[ OK ]
Ensure that Lan0 is the LAN card that is connected to your head-end Network
Element. Select Lan1 by pressing the selection button.
25 The System Internet Address must then be set. The following dialogue is
displayed:
If you wish networking to operate correctly, you must also assign
the system a unique Internet Protocol (IP) address. The IP address
must:
• Contain 4 numeric components.
• Have a period (.) separating each numeric component.
• "Contain numbers between 0 and 255.
—continued—

Procedure 14-8
drive (continued)
Step Action
14
For example: 134.32.3.10
If you have not yet obtained an IP address from your local
System administrator, you may use the default address of
127.0.0.1 by selecting 'OK'.
Enter your Internet Protocol address and then press [return]
Type the IP address of LAN 1, and select the OK button.

26 An additional network parameter dialogue is then displayed, asking if further
network parameters are to be configured. Accept this using the Yes button.
27 The Subnet Mask and Default Gateway is displayed.
Enter a Subnetwork Mask of 255.255.255.0.
Enter the IP address of LAN port 0 and the Default Gateway IP Address.
Click OK to continue.
28 A dialogue box appears which lists the above selections, and any default
settings that are to be applied. Select Yes to confirm.
29 The Domain Name System window is then displayed, with entries for the
Local Domain Name and the DNS Server IP Address.
Select Cancel to close this screen without specifying any details.
30 The Network Information Service window is then displayed, with an entry
for the NIS Domain Name and the NIS server name or IP address.
31 The System Parameter window is then displayed.
Congratulations! Your system is now configured for networking, with
system name <hostname>, and internet address <ip address>.
You may later want to set up (or finish setting up) additional
network parameters for routing (gateways), DNS and or NIS. If so,
please run the following command (you may want to note this for
further reference):
/sbin/set_parms add1_netwrk [Return]
To fully utilize the capabilities of your system, you may have to

perform some additional system configuration tasks using the HP-UX
"sam" (System Administration Manager) command. Consult your local
administrator or the "HP-UX System Administrator Tasks" manual for
more information.
The system will now complete its boot process, and allow you to
login as 'root'.
—continued—

Procedure 14-8
drive (continued)
Step Action
Choose Close to begin the boot process!
Select Close to close this window.

32 The HP platform reboots. A series of system tests are run and there will be
additional automatic reboots of the platform. Once complete you will
eventually be presented with the HP-CDE login dialogue box.
33 Remove the HP-UX 11i CD and store safely.
—end—
Loading LAN configuration script

If the EC-1 platform is to communicate, via a TCP/IP network to a Optical
Network Manager AP system, it will be necessary to load the LAN
configuration script, once HP-UX 11i has been installed, via Procedure 14-9,
below:
Procedure 14-9
Step Action
1 Log in as root user by typing in the log in box with root as user name and
enter the password:
root ↵
<password> ↵
2 Insert the Optical Network Manager EC-1 Release 16.2 software CD-ROM
(NTQJ30MW) in the drive.
corner of the CDE dashboard.
4 Check the system to ensure that the CD-ROM drive is available. Type:
this list, for example /dev/dsk/cXtXdX (where cXtXdX is the device name of
the CD-ROM). Take a note of this device because you must enter it when
mounting the Optical Network Manager EC-1 Release 16.2 CD-ROM
(NTQJ30MW).
5 Create a directory in which you can mount the CD-ROM device. Type:
mkdir /cdrom ↵
—continued—

Procedure 14-9
Loading LAN configuration script (continued)
Step Action
7 Type the following commands: 14

cd /tmp ↵
ls /cdrom/EC-1 ↵
This command displays the file name of the file to be loaded, that is,
ec162XX_hpp10.TNMS_COMMON.tar.Z, where XX is the revision of the
file.
8 To decompress and load the file, type the following command on one line:
zcat /cdrom/EC-1/ec162XX_hpp10.TNMS_COMMON.tar.Z | tar xvf -
sdhms/bin/addenetcard ↵
Note: Remember to replace the letters XX with the result you got
from the ls /cdrom command above.
—end—

Configuring the second Ethernet port

Network Manager AP system, it will be necessary to run the LAN
configuration script has been loaded, via Procedure 14-10, below:
Procedure 14-10
Step Action
1 Open a UNIX window from the Personal Applications menu of the HP CDE
Workspace Manager bar. In the window type:
sam↵
If sam returns an option to run in text mode, select No.
Type:
csh↵
setenv DISPLAY :0↵
sam↵
2 The System Administration Manager appears on the screen. Use the
mouse to double-click on this menu to select Networking and
Communications.
3 A new menu appears. Double-click on this menu to select Network Interface
Cards.
4 To configure the LAN 0 card, highlight the LAN0 line by clicking the mouse
once.
5 Click the right-hand button of the mouse to bring up the background menu
with the following items:
Modify System name
Configure
6 With the right-hand button held down, move the mouse to highlight
Configure. Release the button.
7 To select the card type, use the mouse to highlight the appropriate Ethernet
card option. Enter the information provided by the System Administrator
before starting this installation; that is:
• Internet address (the IP address for LAN 0).
• Alias, an appropriate hostname which is different from that used for
LAN 0, for example <hostname>_lan0.
Note: When clicking the Add Host Name Aliases.. button, a note dialog
can appear regarding subnetting. Click on OK. Then click the Add Host
Name Aliases.. button again and enter the alias. Click the Add button.
Then click the OK button.
—continued—

Procedure 14-10
Configuring the second Ethernet port (continued)
Step Action
8 Click OK to configure the Ethernet card. 14

You are now returned to the Networking and Communications screen. This
shows the new card ‘LAN0’ with all its configuration parameters entered. The
Status parameter should now read Enabled.
Note: If the system rejects the attempted configuration, check that the
Ethernet cable is properly seated in the card and that the connection is active.
9 If the Default Gateway requires editing, go to the Networking and
Communication area in sam. Select Routes. Then right-click on IP address.
To edit the Default Gateway clcik on Modify Default Gateway. Enter the IP
Address of the machine you want to use as the Default Gateway.
10 Select Exit from the File menu and then Exit Sam from the System
Administration Manager.
11 Both LAN cards should now be operational. Check this by typing:
/etc/lanscan↵
The following should appear on the screen with both cards in an UP state:
HardwareStationCrd Hdw Net-Interface NM MAC HP-DLP1 DLPI
PathAddress ln# State NamePPA ID Type Support Mjr#
10/0/12/0 0x00306E13670A 0 UP lan0 snap0 1 ETHER Yes 119
10/1/2/0 0x00306E0603AB 1 UP lan1 snap1 2 ETHER Yes 119
12 Run the addenetcard script. Type:

/tmp/sdhms/bin/addenetcard ↵
13 The system now asks you if you wish to continue. Type:
y
14 View the hosts file. Type:
cat /etc/hosts ↵
You should see the LAN 0 line as:
<IP address of lan0> hostname_0
15 Unmount the CD-ROM by typing:
umount /cdrom ↵
16 Now reboot the machine.
17 With the LAN0 port connected, the workstation needs to be rebooted. Reboot
the workstation by typing:
/etc/reboot↵
Note: If you want to shut down the machine, do not shut down the
workstation platform while a reboot is occurring. Wait until the workstation
platform is in a stable state before powering down.
When the reboot finishes the LAN0 card is operational
—end—

Validate LAN cabling

It is crucial for the operation of the EC-1 platform that the correct LAN cable
is connected to the OSI network. Procedure 14-11 below validates this:
Procedure 14-11
Step Action

3 At the shell prompt type 'ioscan | grep "PCI Core I/O Adapter<RETURN>".
4 If there is no output from this command, repeat Step 3 above. If there is still
no output, try typing 'ioscan | more<RETURN>' and check the output for a line
containing the appropriate string for the target EC-1 platform's motherboard
lan port:
"PCI Core I/O Adapter" - C3750, C3600 and B2600
"HP PCI 10/100Base-TX Core" - B180L
"PCI(10110019) -- Built-in #3" -B132L+
( If required, use the spacebar to scroll through the output.).
Otherwise, if output is evident at step 3, it wiil be of the form
"<H/W Path> <Class> <Description>",
e.g. "10/0/14/1 ba PCI Core I/O Adapter".
Make a note of the 'H/W path' for the motherboard lan port,
e.g "10/0/14/1".
5 At the shell prompt type "lanscan<RETURN>". Note the 'Hardware path' for
'lan0'. If this is the same as the 'H/W path' recorded at step 4 then ensure that
the cable connected to the LAN port on the motherboard of the HP platform,
is connected to the OSI network of SDH multiplexors. If the 'H/W path'
recorded at step 4 is different from the 'Hardware path' for 'lan 0', ensure that
the LAN cable connected to the peripheral lan card is connected to the OSI
network of SDH multiplexors.
6 Log out of CDE.
—end—

Reinstall Optical Network Manager EC-1 R16.2 application software

It necessary to reload the Optical Network Manager EC-1 R16.2 application
software, using Procedure 14-12 below:
Procedure 14-12
Reinstall Optical Network Manager EC-1 R16.2 application software 14
Step Action
1 Log into the EC-1 platfrom as user root.

2 From the CDE menu bar, select ’Application manager’ -> ’Destop Apps’ ->
’Terminal’
When prompted, set the terminal type to ’xterm’.
(On VUE desktops, select ’General’ -> ’Utilies’ -> ’Xterm’).
3 Insert the CD-ROM (NTQJ30MW) in the drive.
4 Open a UNIX window (xterm or hpterm).
5 Check the system to ensure that the CD-ROM drive is available by typing:
this list, for example: /dev/dsk/cXtXdX (where cXtXdX is the device name of
the CD-ROM). Take a note of this device name because you must enter it
when mounting the CD-ROM in step 6.
mount /dev/dsk/<cXtXdX> /cdrom ↵
Where <cXtXdX> is the device name, see step 5.
7 Type the following commands:
cd /tmp ↵
rm -rf install ↵
ls /cdrom/EC-1 ↵
ec162XX_hpp10_install.tar, where XX is the revision of the file.
—continued—

Procedure 14-12
Reinstall Optical Network Manager EC-1 R16.2 application
software (continued)
Step Action
8 To decompress and load the file, type the following commands:

tar xvf /cdrom/EC-1/ec162XX_hpp10_install.tar ↵
cd install ↵
./Install_EC-1 -cdrom | tee /tmp/install/install.log ↵
Note: Remember to replace the letters XX with the result you get from the
ls /cdrom command in step 7.
The script warns about changes to the Element Controller related to the DCN
network as follows:
The EC-1 now runs as an OSI Intermediate System (IS) instead of an
End System (ES). Before you proceed with this upgrade, you should
consider whether or not this change will impact your OSI DCN
network.
Also note the OSI Comms Stack is now configured in the file
osi_comms.conf instead of mfmMAA.dat.
Do you wish to continue with the installation [y/n]?
Respond y to continue with the installation, or n to exit the script immediately.
—continued—

Procedure 14-12
Step Action
14
9 The following messages appear:
INSTALL: Add the sdhms group and sdhmsuser account
(if needed)
Directory /cdrom/EC-1 contains the following s/w packages:
1. EC-1 Common Software Preside_EC-1.162.xx
Do you wish to install Package 1 [y/n]?

Where, xx represents the version/load number. Type:
y ↵
In response to the confirmation, more messages appear:
INSTALL: Commencing installation of package 1:
EC-1 Common Software (PRESIDE_COMMON) version
Preside_EC-1.162.xx
INSTALL: Commencing installation of PRESIDE_COMMON

Preside_EC-1.162.xx
There is a two minute delay.
INSTALL: configured for HP-UX V10.
INSTALL: Adding EC-1 user and group

INSTALL: Searching for old users
INSTALL: None found
hci_upgrade_users - Upgrading the configuration of

all EC-1 management users
syseng01
admin
netsurv
slat
master
operator
—continued—

Procedure 14-12
Step Action
Set the security (login)

10 You are now asked whether the system should be secure or not secure.
A secure system uses a two stage login process. You log into the workstation,
and then into the Element Controller. A system which is not secure does NOT
require a login for the Optical Network Manager EC-1.
INSTALL: Do you want to make the system SECURE [y/n]?
If this is to be a secure system type:
y↵
Otherwise type:
n↵
Messages appear to indicate the choice made.
11 The following messages then appear:

INSTALL: No database file found - creating a new file
crdinst: creating new database file
The following messages then appear:
CHANGE PRIV: Setting privileges on programs
Main log directory exists
Enquiry Library Log directory does
not exist (creating it)
The following menu then appears:

the following list:

7. Hot standby EC-1
Option [1-7]?
—continued—

Procedure 14-12
Step Action
14
12 Select the appropriate operating mode for the EC-1:
Archive EC-1 backing up to remote central archive
If the EC-1 platform is to back up to an RCA server type 2 <return>
The screen prompts you for the hostname and IP address of the Remote
Central Archive (RCA) platform.
INSTALL: Enter hostname of RCA:
Enter the hostname of the RCA platform.
INSTALL: Enter IP address of <hostname>:
Enter the IP address of the RCA platform.
At this point, the installation process tries to ensure that communication is
available to the defined platform. This action is done using the TCP/IP ping
command. There are two possible results:
a. If comms are confirmed, the following appears:
Comms checked to <IP address>
b. If comms are not confirmed, the following appears:
Could not ping <IP address>
Please ensure that comms is established to this

EC-1 as soon as possible
Note: The installation continues if the comms check fails. However, the
backup facility does not function until TCP/IP comms are available.
Cold standby EC-1
If the EC-1 platform is to back up to an cold standby server type 5
<return>
Active EC-1 platform with no remote archives
If the EC-1 platform is to back up to an active EC-1 with no remote back
ups type 1 <return>
Reinstallation of Preside EC-1 16.2 (continued)
—continued—

Procedure 14-12
Step Action
13 Further messages are output:

INSTALL: Adding Preside AP Interface
INSTALL: Adding support for TN-1X mux
INSTALL: Adding support for TN-1P mux
INSTALL: Adding support for TN-1C mux
INSTALL: Adding support for TN-4XE mux
INSTALL: Adding support for TN-4T mux
14 The kernel is then installed:
Compiling /stand/build/conf.TNMS.c...
Loading the kernel...

/usr/ccs/bin/ld: (Warning) Linker features were used that may not
be supported in future releases. The +vallcompatwarnings option can
be used to display more details, and the ld(1) man page contains
additional information. This warning can be suppressed with the
+vnocompatwarnings option.
The message may be repeated. The kernel installation then ends:
INSTALL: Kernel installed successfully.
INSTALL: Installation of package - PRESIDE_COMMON
Preside_EC-1.162.xx complete
Setting Netscape Directory for ReachThrough

INSTALL: check for /bin/csh in etc/shells file
INSTALL: System should now be rebooted

INSTALL: Installation complete
16 A copy of the installation log is required. Type:
cd /tmp/install ↵
cp ./install.log /home/sdhmsusr ↵
Determine if you need to edit the osi_comms.conf file taking account of
the Caution:
—continued—

Procedure 14-12
Step Action
14
CAUTION
After a Optical Network Manager EC-1 installation or
upgrade to Release 16.2, the Optical Network
Manager EC-1 can become the assigned Open System
Interconnection (OSI) intermediate system (IS) router.
Although the Optical Network Manager EC-1
Release 16.2 software contains this functionality,
Nortel Networks recommends that networks use either:
• an external router (such as a Nortel Networks Access
Stack Node (ASN) Router), or
functionality (for example, either of Nortel Networks
OPTera Metro 4100 or Nortel Networks OPTera Metro
4200 Multiservice Platforms).
The osi_comms.conf file provides router functionality

external to Optical Network Manager EC-1 and is set
for ‘Level 1’ routing as default.
Appendix B: osi_comms.conf file, describes the significance of the

parameters within the osi_comms.conf file. If you want to change the
existing OSI communications arrangements in your network (for example, to
introduce ‘Level 2’ routing), you need to edit the osi_comms.conf file
accordingly.
If Then go to
you want to edit the osi_comms.conf file step 17
you do not want to edit the osi_comms.conf file step 21
—continued—

Procedure 14-12
Step Action
17 Type the command:

chmod +w /home/sdhmsusr/sdhms/lib/osi_comms.conf ↵
18 Use either ’vi’, ’vuepad’ or another text editor to edit the file with your required
changes (refer to Appendix B: osi_comms.conf file).
/home/sdhmsusr/sdhms/lib/osi_comms.conf.
The file looks similar to the following:
#
#
#
# no entry implies default i.e. LEVEL1 routing and LEVEL1_ONLY circuit
#
#
#
MAA1=490000
[ISIS Routing]
#
#
ISIS_ROUTER=LEVEL1
#
PRIORITY_L1=60
#
PRIORITY_L2=60
[LAN Card Routing]

#
#
LAN0=LEVEL1_ONLY
#
#
19 Make the required edits and save the edited file and exit the editor.
chmod -w /home/sdhmsusr/sdhms/lib/osi_comms.conf↵
21 Reboot the Optical Network Manager EC-1. type:
/etc/reboot ↵
—end—

Validating the EC-1 application

Following the reinstallation of Optical Network Manager EC-1 it is necessary
to validate the correct operation of the EC-1 application, via Procedure 14-13
below:
CAUTION
14
After a HP-UX Migration from 10.20 to 11i, it has been
identified on some occasions that LAN 0 and LAN 1become
swapped, i.e. what was LAN 0 on HP-UX 10.20 will become
LAN 1 at HP-UX 11i
There are two solutions to resolve this issue:

1. Physically swap the LAN cables at the back of the HP
workstation.
OR
Run the LAN swap script, which swaps LAN 0 and LAN 1 in
the software, refer to Appendix H, LAN swap Script.
Procedure 14-13
Step Action
1 Log into the EC-1 platform as user syseng01.

session.
4 If, after 2 minutes, an EC-1 session has not started, contact Nortel Technical
support, otherwise proceed to step 5.
5 Log out of the EC-1 session, via the 'Log out' button on the 'Main' menu. Then
log out of CDE. If no Optical Network Manager AP platform is to manage the
target EC-1, the procedure is complete.
6 If the EC-1 platform is managed by a Optical Network Manager AP system
(PAP), log into the PAP as user admin and from the CDE menu bar select
'Application Manager' -> 'PersonalToolbox' (On VUE desktops, simply open
the 'Personal Toolbox'.)
7 Double click on the GNB icon to start a GNB session.
8 Select 'Controllers' -> 'Show controller list' and, in the list of controllers, right
click on the target EC-1, to log into it, with an EC-1 GUI session.
select 'File' -> 'Exit to close the GNB log out of CDE/VUE on the PAP.
—end—

Restoring network configuration data

Once the re-installed Optical Network Manager EC-1 R16.2 application
software has been successfully validated, it is necessary to restore the network
configuration data, previously archived to DAT, via Procedure 14-14 below:
Procedure 14-14
Step Action
1 Mount the archive tape, labeled 'Database archive', which was created during
Procedure 14-5 into the tape drive, and wait for the tape drive lights to stop
flashing.
2 Login as sdhmsusr from the HP login banner by typing:
sdhmsusr ↵
<password> ↵
3 Open a UNIX window from the HP workspace manager. Then, shut down the
Optical Network Manager EC-1 software:
killsdhms ↵
Note: The killpros command must not be used for this purpose.
When prompted, enter the shutdown reason as follows:
Restoring data from DAT tape for <name>↵
The following messages appear:

....5....10....15....20
....25
4 Restore the database by typing:
db_restore ↵
DB_RESTORE: EC-1 Configuration Restore
WARNING!
--------
Restoring the configuration will overwrite current EC-1
configuration files. Please be sure you have a valid backup for
this machine should you wish to preserve any configuration
files.
To backup the EC-1, please refer to the EC-1 User procedures.
Do you wish to restore the configuration [y/n]?
Enter y to confirm the operation. Continue from step 6.
Enter n to cancel the operation. The script exits with the
following message:
No files have been restored
—continued—

Procedure 14-14
Backing up NE software loads (continued)
Step Action
6 The status of the tape is then checked. The following message appears: 14
Checking if tape drive is ready...
If there is no tape in the drive, the following message appears:
Tape is not in drive or drive not ready.
Try again [yn] ?
Check the tape is inserted, then enter y. If you enter n at this point, the
script exits with the following message:
The tape must be inserted before restore can continue
7 Files are then extracted from the tape. A number of tape restore messages
appear during this process.
8 The tape is ejected and the script completes with the following messages:
Ejecting tape
Restored files
DB_RESTORE: Complete.
9 Once the script has completed and the tape has been ejected, at the shell
prompt, type 'killsdhms<RETURN>'. When prompted for a shutdown reason,
type 'NE restore<RETURN>'. The EC-1 application will now shut down.
10 Once the EC-1 application has shutdown, at the shell prompt, type 'su -
root<RETURN>'. When prompted, enter the root password and press
<RETURN>.
11 Once the root login has completed, at the shell prompt, type '/etc/
reboot<RETURN>
12 Wait until the EC-1 platform has successfully restarted.
—end—

Restoring NE software loads

Once the network configuration data has been restored, it is necessary to
restore the NE software loads, previously archived to DAT, via Procedure
14-15 below.
Procedure 14-15
Step Action

3 Insert the second DAT tape labelled 'NE s/w loads', created in Procedure 14-5
above, into the EC-1 DAT drive and wait for the lights on the drive to stop
flashing.
4 In the 'xterm' window, type 'tar xv<RETURN>'
to stop flashing.
7 Log out of CDE.
—end—

Validation of NE association
Once the NE software loads have been successfully restored, as a
post-migration check, it is necessary to validate the association of all the NEs
in the EC-1's span of control, both with the EC-1 and, if a PAP is managing
the target EC-1, at the GNB, using Procedure 14-16 below:
14
Note: On large networks, after the completion of Procedure 14-14 above,
it may take up to an hour for the DCN to settle and the Optical Network
Manager EC-1 application to regain full association with the NEs in its
span of control.
Procedure 14-16
Step Action

session.
4 From the EC-1 main menu, select the 'Network Element Access Tool'(NAT).
5 From the EC-1 Alarm menu, select 'View active alarm list'
6 Monitor the NAT to ensure that all managed NEs eventually display their
software version, whilst also monitoring the 'Active alarm list' to ensure that
all unexpected comms fails to NEs clear and the EC-1 'Messages' window for
any 'Failed to control' messages. If, after an hour, there are NEs that still
display unexpected 'Comms fail alarms', contact the network administrator to
attempt to resolve the discrepancy.
7 Once all NE's have regain association with the EC-1, log into the Optical
Network Manager AP as user 'admin' and open the GNB view for the primary
'active' EC-1. If all NEs are 'blue' on the GNB, check the network configuration
and connections on the primary active EC-1.
—end—
The migration of a standalone Optical Network Manager EC-1 is now

complete

HP-UX 11i with a temporary 'warm standby' EC-1

The following procedures cover the set up and preparation required, prior to
the migration of one or more 'standalone' EC-1s, where a temporary Optical
Network Manager EC-1 platform has been shipped to site, to provide network
visibility, whilst the original platform is rebuilt to Optical Network Manager
EC-1 R16.2. These procedures allow for this temporary platform to be
installed as a 'warm standby' Optical Network Manager EC-1 R16.2, so
providing resiliency for the target EC-1(s) to be migrated to HP-UX 11i.
Table 14-4
Migration to HP-11i with a tempoary ’warn standby’ EC-1
Procedure 14-17 Equipment check for temporary EC-1 platform
Procedure 14-18 Obtain temporary platform configuration data
Procedure 14-19 Set up temporary 'warm standby' EC-1
Procedure 14-20 Booting the HP B2600/C3600/C3750/B180L platforms from

either the CD-ROM or DVD-ROM drives
CD-ROM drive
Procedure 14-25 Reinstall Optical Network Manager EC-1 R16.2 application

software
Procedure 14-27 Updating the operating mode of the 'standalone' EC-1
Equipment check for temporary EC-1 platform

Prior to commencing the migration to HP-UX 11i, the equipment provided to
act as temporary 'warm standby' EC-1, needs to be checked. One of the
equipment bundles defined in Procedure 14-17 will be required.

Procedure 14-17
Equipment check for temporary EC-1 platform
Step Action
1 Ensure that the equipment bundle delivered as a temporary is one of the 14

following
Table 14-5
B180L
HP Part # Quantity Description
A4323A 1 HP B180LL CPU
A4517A 1 HP 256Mb RAM
A4570A 1 HP 9Gb USCSI DISK
A4956A 1 HP Internal DAT 4GB (8Gb with

compression)
A4575A 1 19"/18.3 viewable Hitachi colour Monitor
A4199B - ACC 1 C-13 Power cord kit (UK power cords)
C4314A 1 SMART desktop DVD drive
B5509BA 1 100 BaseT PCI LAN Adapter
C2904A 1 SCSI terminator HDST50
C2957A 1 SCSI cable, 2M, HDST50
—continued—

Procedure 14-17
Equipment check for temporary EC-1 platform (continued)
Step Action
Table 14-6
B2600 (prior to June 2003)
HP Part number Quantity Description
A6070A 1 HP B2600L CPU
A7227A-0d1 1 HP Desktop enclosure kit for HP B2600
A4994A-0D1 1 HP 256-Mbyte SDRAM for B, C,& J-Class
A4998A-0D1 1 HP 18-Gbyte 10kr/min Ultra2 SCSI (LVD)

internal hard disk for B, C & J-Class
A4982B-OD1 1 HP Visualize fxe rev B graphics card
A7776A-0D1 1 HP internal DDS3 DAT drive
B5509BA-0D1 1 HP 100Base-T PCI LAN Adapter
A4974A-0D1 1 HP PCI Ultra-SCSI Single Ended Adapter
CM772ET 1 19-inch/18.3-inch viewable Hitachi Color

Monitor, CM772ET
A4983B-ABA-064 1 HP US-English USB keyboard and USB

3-button, scroll-wheel mouse
A4199B-ACC 1 HP C-13 Power cord kit (UK power cords)
C4314A 1 HP SMART desktop DVD drive
C2904A 1 HP SCSI terminator HDST50 (for use with

C2906A)
C2906A 1 HP SCSI cable, 2M, HDST50 to HDST68
A4168A 1 HP Adapter Cable ( EVC male to a female

15-pin D-subminiature connector)
B6846A 1 HP-UX MTOE LTU
C2904A 1 HP SE SCSI II Active Terminator
—continued—

Procedure 14-17
Step Action
14
Table 14-7
B2600 (Post June 2003)
A6070A 1 HP B2600L CPU
A4995A 1 512Mb mod
A6031A 1 36GB 10K SCSI LVD
A4982B 1 HP FXE (rev b) Graphics
A8068B 1 Internal DVD
B5509BA 1 HP 100Base-T PCI LAN Adapter
A4974A 1 HP PCI Ultra-SCSI Single Ended Adapter
A7227A 1 Deskside Kit
P9009A-ABB 1 19" HP Mointior
A4983B-ABA-064 1 HP VISUALIZE USB English Keyboard Kit

with scroll mouse
A4199B-ACC 1 HP VISUALIZE C-13 Power cord kit (UK

power cords)
C5687B-ABU 1 DDS4
C2911C 1 1M HD68 to HD68 cable
—continued—

Procedure 14-17
Step Action
Table 14-8
C3600
A5992A 1 HP Visualize C3600 CPU with 512-Mbyte

SDRAM
A4995A 1 HP 512-Mbyte SDRAM for B, C & J-Class

(Installed)
A4998A 1 HP 18-Gbyte 10kr/min Ultra2 SCSI LVD

Disk for B, C & J-Class (Installed)
CM771ET-301 1 19-inch/18.3-inch viewable Hitachi Color

Monitor
A4168A 1 HP Adapter Cable (EVC male to a female

15-pin D-subminiature connector)
A4982A 1 HP Visualise fxe 2D/3D Graphics card

(Installed)
A444983B-ABA 1 HP-UX Visualize CAD US-English

Localization Kit B, C & J-Class
A4199B-ACC 1 1 HP C-13 Power cord kit (UK power cords)
C6362A 1 HP SMART desktop DDS2 DAT drive
C2904A 1 HP SCSI terminator HDST50 (for use with

C2957A)
C2957A 1 HP SCSI cable, 2M, HDST50

Procedure 14-17
Step Action
14
Table 14-9
C3750
A9636A 1 C3750 Base System
A6016A 1 1024MB Menory Module
A6031A 1 36GB 10K SCSI LVD
P9009A-ABB 1 19" HP Mointior

(not needed)
A4982B 1 Visualize FXE 2D/3D Graphics card
A8068B 1 Internal DVD
A4983B-ABA-064 1 HP VISUALIZE USB English Keyboard Kit

with scroll mouse
A4199B-ACC 1 HP VISUALIZE C-13 Power cord kit (UK

power cords)
C5687B-ABU 1 DDS4
C2911C 1 1M HD68 to HD68 cable
Note: If the local power source does not come from UK three pin sockets,
you must also obtain three power cords, with the appropriate length and
local pin outs.

Obtain temporary platform configuration data

The temporary EC-1 platform will need to be installed on the same data
communications network as the target EC-1s. Consequently, from your
network administrator, it is necessary to capture the data defined in Procedure
14-18, below for the temporary 'warm standby' platform, prior to proceeding
with the migration from HP-UX 10.20 to HP-UX 11i
Procedure 14-18
Obtain temporary platform configuration data
Step Action
1 Ensure that the following configuration data is available for the temporary
standby platform: .
• "hostname,
• "LAN0 IP address
• "LAN0 subnet mask
• "LAN1 IP address
• "LAN 1 subnet mask
• "IP address of the default gateway.
• " 'root' user password
CAUTION

masks of lan0 and lan1 are also the same, refer this to your
network administrator
Set up temporary 'warm standby' EC-1

The temporary 'warm standby' EC-1 will require assembly and connection to
power sources and the appropriate data communications network. Procedure
14-19 details this:

Procedure 14-19
Set up temporary 'warm standby' EC-1
Step Action
1 Ensure that the temporary ’warn standby’ is set up and connected as detailed 14
in
Figure 14-1
HP B180L cable connections (back view)
ac power
supply 13W3
video
cable
SCSI CD-ROM
ac power supply
Printer Serial printer ports
LAN 1
Keyboard LAN 0
Mouse
Note: LAN 0 is used for Multiplexers

LAN 1 is used for Element Controllers,
X-terminals, and Optical Network Manager
Applications Platform
With HP-UX 11i the two physical ports may be reversed

Figure 14-2
HP B2600 cable connections (back view)
13W3
video
ac power cable
supply
ac power supply
LAN 1
Serial printer ports
Keyboard SCSI CD-ROM
Mouse
LAN 0
Printer

Figure 14-3
HP C3600 and C3750 cable connections (back view)
13W3
video
cable
LAN 1
ac power Serial printer ports
supply
LAN 0
SCSI CD-ROM
Keyboard ac power supply

Mouse
Printer

Note 1: T this stage the LAN0 port should be connected to the OSI network
and the LAN 1 port should be connected to the same TCP/IP sub-net as the
target EC-1(s).
Note 2: Connection of a printer is NOT required for completion of the
migration to HP-UX 11i

Installation of HP-UX 11i on temporary 'standby' EC-1

The temporary 'standby' EC-1 platform will require to be running HP-UX 11i.
The installation of this operating system software is described in Procedure
15-7 and Procedure 14-20 below.
CAUTION
14
Manually updating the network configuration on a built Optical
Network Manager EC-1 platform can disrupt the operation of
the EC-1 application. Also there is a risk that, if a platform has
been used at a previous site, it will have a conflicting
configuration on its hard drive. For these reasons, it is
important that the temporary 'standby' platform has a fresh
installation of HP-UX 11i and Optical Network Manager EC-1
R16.2 completed, prior to the migration of the target EC-1(s) to
HP-UX 11i.
Procedure 14-20
Booting the HP B2600/C3600/C3750/B180L platforms from either the CD-ROM
or DVD-ROM drives
Step Action
1 Push in the power switch on the monitor.

The LEDs on the front of the monitor light up to indicate that power is on.
2 Push in the power switch to the Workstation.
The power LED lights up to indicate that power is on.
CD-ROM.
To select a new Graphics Monitor Type press the [TAB] key now,
otherwise EXIT by entering other key (or will timeout in 15 seconds)
5 Allow this message to timeout.
6 Another message appears:
In both cases, before this period times out, press any key.
—continued—

Procedure 14-20
or DVD-ROM drives (continued)
Step Action
7 The workstation Main Menu appears, as shown below.

-----Main Menu-----
Command Description
------- -----------
PAth [PRI|ALT|CON|KEY] [<path>] Display of modify a path
...
...
RESET Restart the system
--------------
8 Search for SCSI devices. Type the following command:
search ↵

---- ----------- -----------
9 Boot from the SCSI device that is identified as the CD-ROM drive. In the
above example, where the CD-ROM is path p1, type:
boot p1 ↵
Respond as follows, type:
n↵
11 The operating system is then loaded from the CD-ROM/DVD-ROM drive.
This process is detailed in Procedure 14-21.
—end—

Procedure 14-21
Loading the HP-UX 11i operating environment from the DVD/CD-ROM drive
Step Action
1 Boot the platform from the DVD/CD-ROM drive (see Procedure 15-20) 14
+---------------------------------------------------+ [Scan Again]
+---------------------------------------------------+ [H/W
Details]
[ Install HP-UX ]
[ Reboot ] [ Help ]
4
installation.
LAN Hardware
Interface Path Type
—continued—

Procedure 14-21
drive (continued)
Step Action
LAN Hardware
Interface Path Type

—continued—

Procedure 14-21
drive (continued)
Step Action
14
screen:
/ ----- \
| Basic |
/ \-------------------------------------------------------
Configurations:[HP-UX B.11.11 Default ->][Description...]
Environments: [<see below>](HP-UX B.11.11)
[Root Disk... ] QUANTUM_ATLAS5-9WS,8/0/19/0.6.0,8678 M
File System: [Logical Volume Manager(LVM) with HFS ->]
[Root Swap(MB)...]<see below>Physical memory(RAM) <see below>
[Languages...]English [Keyboards... ]
--------------------------------------------------------------
[Show Summary...] [Reset Configuration]
--------------------------------------------------------------
Note : If required, can also use VxFS file system support.
---------------------------------------------------
—continued—

Step Action
to display its menu. Use the arrow keys to highlight an option from the
Table 14-10
System Parameters
Machine Environments Partition Sizes Physical Machine

Memory
B180L HP-UX 11i Root..............................512 256 B180L

with 9G Base OS - 32bit /..................................3000 with 9G
hard drive June 2001 /stand...........................512 hard drive
/home.........................4648
B2600 HP-UX11i Root............................2048 256 B2600

/home.....................~11800
NewB2600 HP-UX11i Root............................2048 512 NewB2600

/home.......................25000
C3600 HP-UX11i Root............................2048 1024 C3600

/home......................~11800
C3750 HP-UX11i Root............................2048 1024 C3750

/home......................~27160
RP34x0 HP-UX11i Root....................1024 (VxFS) 1024 RP34x0

with 36G Base OS - 64bit Root Swap..........3880 (swap) with 36G
hard drive June 2004 /var......................3072 (VxFS) hard drive
/usr......................4800 (VxFS)
/tmp.....................2048 (VxFS)
/stand......................400 (HFS)
/home................11800 (VxFS)
/opt......................6632 (VxFS)

Table 14-10
System Parameters
Machine Environments Partition Sizes Physical Machine

Memory
RP34x0 HP-UX11i Root....................1024 (VxFS) 1024 RP34x0

14
with 72G Base OS - 64bit Root Swap..........4096 (swap) with 72G
hard drive June 2004 /var......................8704 (VxFS) hard drive
/usr......................5000 (VxFS)
/tmp.....................2048 (VxFS)
/stand......................400 (HFS)
/home................22056 (VxFS)
/opt....................10632 (VxFS)
free unpartitioned space

17600
key and <RETURN> so that the following screen appears:
/--------\
| System |
/ \-------------------------------------------


--------------------------------------------------------
--------------------------------------------------------
--------------------------------------------------------
Set the Final System Parameters option to Ask at first boot.
—continued—

Procedure 14-21
drive (continued)
Step Action
TAB key and Return so that the following screen appears.
Enter the values from the sample table below.
/ --------- \
|File System|
/ \---------------------------------

/ HFS 3000 54 vg00 F
/

| |
\------------------------------------------------------/
--------------------------------------------------------
--------------------------------------------------------
You must remove all other file systems (/tmp, /opt, /usr and /var) by
Configure the following file systems as shown in Table 14-10.
Set the /stand, primary and / file systems to the values shown in the table
above. In larger workstations, you can set the /home file system to the
changes.
—continued—

Procedure 14-21
drive (continued)
Step Action
14
Itool Confirmation
/--------------------------------------------------------
| |
\-------------------------------------------------------
/-------------------------------------------------------\
\------------------------------------------------------/
Select Go!
reboots. The routine and reboot takes approximately 60 minutes on a B180L
platform.
The following screen appears:
/------------------------------------------------------\
"BXXXX 11i OE CD"
\---------------------------------------------------------------------------------------------/
—continued—

Procedure 14-21
drive (continued)
Step Action
second boot CD-ROM ("HP-UX 11i NTNM51ZDAF", disk 2 of 2) into the
CD-ROM drive and continue with the installation.
16 Enter the system hostname (workstation name, see ‘Hostnames and
addresses’ on page 2-3) by typing the workstation name and selecting OK.
the Yes button.
• Central America
• South America
• Europe
• Africa
• Asia
—continued—

Procedure 14-21
drive (continued)
Step Action
14
details.
confirm it for use.
displayed:
LAN Hardware
Interface Path Type
Lan1 8/0/1/0 HP AS230A / B5509BA
PCI 10/100 Base-TX Addon
[ OK ]
displayed:
If you wish networking to operate correctly, you must also assign the system
a unique Internet Protocol (IP) address. The IP address must:
—continued—

Procedure 14-21
drive (continued)
Step Action


26 The Subnet Mask and Gateway is displayed.
Enter the IP address of LAN port 0 and the Gateway IP Address.
Congratulations! Your system is now configured for networking, with system
name <hostname>, and internet address <ip address>.
You may later want to set up (or finish setting up) additional network
parameters for routing (gateways), DNS and or NIS. If so, please run the
following command (you may want to note this for further reference):
To fully utilize the capabilities of your system, you may have to perform some
additional system configuration tasks using the HP-UX "sam" (System
Administration Manager) command. Consult your local administrator or the
"HP-UX System Administrator Tasks" manual for more information.
The system will now complete its boot process, and allow you to login as
'root'.
—continued—

Procedure 14-21
drive (continued)
Step Action
14

—end—

configuration script, once HP-UX 11i has been installed, via Procedure
14-22, below:
Procedure 14-22
Step Action
enter the password:
root ↵
<password> ↵
(NTQJ30MW).
mkdir /cdrom ↵
—continued—

Procedure 14-22
Step Action

cd /tmp ↵
ls /cdrom/EC-1 ↵
file.
—end—


Procedure 14-23 14
Step Action
sam↵
Type:
csh↵
sam↵
Communications.
Cards.
once.
Modify System name
Configure
—continued—

Procedure 14-23
Step Action
8 Click OK to configure the Ethernet card.

9 If the Default Gateway requires editing, exit from the Networking and
Communication area in sam. Select Hosts from the menu. When the next
menu appears, select Local Hosts file. This opens the Hosts File screen. To
edit the Default Gateway, select the Actions tab and click on Modify Default
Gateway. Enter the IP Address of the machine you want to use as the Default
Gateway and remove the name in the alias text.
/etc/lanscan↵

y
cat /etc/hosts ↵
umount /cdrom ↵
/etc/reboot↵
—end—


Procedure 14-24
Validate LAN cabling 14
Step Action

lan port:
"PCI(10110019) -- Built-in #3" -B132L+
e.g "10/0/14/1".
6 Log out of CDE.


Procedure 14-25
Step Action

’Terminal’
cd /tmp ↵
rm -rf install ↵
ls /cdrom/EC-1 ↵
—continued—

Procedure 14-25
Step Action
14
cd install ↵
network as follows:
The EC-1 now runs as an OSI Intermediate System (IS) instead of an
End System (ES). Before you proceed with this upgrade, you should
consider whether or not this change will impact your OSI DCN
network.
Also note the OSI Comms Stack is now configured in the file
osi_comms.conf instead of mfmMAA.dat.
—continued—

Procedure 14-25
Step Action

(if needed)
Directory /cdrom/EC-1 contains the following s/w packages:

y ↵
Preside_EC-1.162.xx

Preside_EC-1.162.xx

INSTALL: None found

syseng01
admin
netsurv
slat
master
operator
—continued—

Procedure 14-25
Step Action
14
y↵
Otherwise type:
n↵


the following list:

7. Hot standby EC-1
Option [1-7]?
—continued—

Procedure 14-25
Step Action


Cold standby EC-1
<return>
ups type 1 <return>
—continued—

Procedure 14-25
Step Action
14


/usr/ccs/bin/ld: (Warning) Linker features were used that may not
be supported in future releases. The +vallcompatwarnings option can
be used to display more details, and the ld(1) man page contains
additional information. This warning can be suppressed with the
+vnocompatwarnings option.

cd /tmp/install ↵
the Caution:
—continued—

Procedure 14-25
Step Action
CAUTION


accordingly.
If Then go to
—continued—

Procedure 14-25
Step Action
14
#
#
#
#
#
#
MAA1=490000
[ISIS Routing]
#
#
ISIS_ROUTER=LEVEL1
#
PRIORITY_L1=60
#
PRIORITY_L2=60
[LAN Card Routing]

#
#
LAN0=LEVEL1_ONLY
#
#
/etc/reboot ↵
—end—


below:
CAUTION
LAN 1 at HP-UX 11i

workstation.
OR
Procedure 14-26
Step Action

session.
—end—

Updating the operating mode of the 'standalone' EC-1

Any 'standalone' EC-1 systems that are to be migrated to HP-UX11i while the
temporary 'standalone' EC-1 manages the NEs in the EC-1's span of control
(SOC) must now have their operating mode updated, so that they become
primary 'warm standby' EC-1s, backing up to the temporary platform. This is
described in Procedure 15.27, below:
14
CAUTION
This procedure changes the mode of the Optical Network
Manager EC-1 platform onto which you are currently logged.
It does not switch control of the network to another standby
Optical Network Manager EC-1.
Procedure 14-27
Updating the operating mode of the 'standalone' EC-1
Step Action
1 Log into the target 'standalone' Optical Network Manager EC-1 platform as
root user.
2 Open an xterm and change directory to /home/sdhmsusr/sdhms/bin:
cd /home/sdhmsusr/sdhms/bin ↵
3 Enter the change mode command:
./change_mode ↵
This command starts the change mode script and the following menu
appears:
7. Hot standby EC-1
8. Exit
Option [1-8]
4 Select 3<RETURN>
5 You are now prompted for the hostname and IP address of the temporary
Warm standby Optical Network Manager EC-1 platform.
6 Enter the hostname of the temporary warm standby platform by typing:
<hostname> ↵
—continued—

Procedure 14-27
Updating the operating mode of the 'standalone' EC-1 (continued)
Step Action
You are now prompted for the host address of the standby platform:
Enter IP address of <hostname>:
7 Enter the IP address of the standby platform by typing:
<IP address> ↵
At this point the change mode script tries to ensure that communication is
available to the specified platform. It does this using the TCP/IP ping
command. There are two possible outcomes:
i. If comms are confirmed, the following appears:
Checking comms to <hostname> (<IP address>)...
Note: If the hostname or IP address is duplicated in the /etc/hosts file, the
following warning appears:
WARNING: 'hostname/IP address' is already used as a
hostname/ IP address.
/etc/hosts entry: "<IP address> <hostname>".
Either the old entry must be removed or the current
hostname and IP address rejected.
Remove old entry? [y/n]
Choose Y if this message appears.
ii. If comms are not confirmed, the following appears:
Checking comms to <hostname> (<IP address>)... failed.
Warning: no comms to <hostname>
Write hostname and IP address anyway? [y/n]
Choose Y if this message appears. The following message appears:
Please ensure that comms is established to <hostname> as soon
as possible. Backups will fail until this is done.
Note: You must ensure that comms are established to the standby platform
as soon as possible. The backup functionality does not function until TCP/IP
comms are available and the standby platform network configuration records
are not updated.
8 For the new changes to be fully initiated the platform must be rebooted.
Reboot the machine (when logged in as root) by typing:
/etc/reboot.↵
9 Repeat this procedure for any other 'standalone' EC-1 systems, which are to
be migrated to HP-UX11i.
Note: At this point, the preparation of the temporary 'warm standby'

platform is complete. The following procedures should now be applied to
the target EC-1(s), to migrate them to HP-UX11i.

Migration to HP-UX11i on primary and standby EC-1s

The following procedures set out how to migrate resilient primary and
secondary 'hot-standby' pairs of EC-1s, as well as primary and secondary
'warm standby' EC-1s (1:1 or 1:many protection)
14
Table 14-11
Procedure 14-28 Validate platform configuration data
Procedure 14-29 Review EC-1 release level
Procedure 14-30 Validate the DAT drive on a primary/secondary EC-1
Procedure 14-31 Backing up NE software loads on primary/secondary EC-1s
Procedure 14-32 Synchronizing primary and secondary EC-1
Procedure 14-33 Backing up network configuration data on primary/secondary

EC-1s
Procedure 14-34 Shut down the target EC-1 application
Procedure 14-35 Activation of 'warm standby' secondary EC-1
Procedure 14-36 Validation of network visibility
Procedure 14-37 Booting the HP B2600/C3600/C3750/B180L platforms from

either the CD-ROM or DVD-ROM drives
Procedure 14-38 Loading the HP-UXi operating environment from the DVD/
CD-ROM drive
Procedure 14-42 Reinstall Optical Network Manager EC-1 R16.2 SP2

application software
Procedure 14-44 Validating a 'hot standby' secondary EC-1 application
Procedure 14-45 Validating a 'warm standby' secondary EC-1 application
Procedure 14-47 Restoring NE software loads
—continued—

Table 14-11
Procedure 14-49 Restoring NE software loads on primary / secondary EC-1s
Procedure 14-50 Restoring EC-1 archives on secondary EC-1s
Procedure 14-51 Switching back from a warm standby platform
Procedure 14-52 Switching back from a hot standby platform
Procedure 14-53 Validation of NE association
Procedure 14-54 Shutdown of any temporary 'standby' EC-1
CAUTION
When migrating either 'hot' OR 'warm' standby EC-1 systems,

the secondary 'back up' platform should be migrated to
HP-UX11i FIRST. Only once the secondary 'back up' platform
is successfully running EC-1 R16.2 on HP-UX11i should
primary EC-1 platforms be migrated to the new operating
environment.
CAUTION
In 'warm standby' configurations, with 1:many protection, only

ONE primary EC-1 should be migrated to HP-UX11i at a time.
Concurrent migrations of primary EC-1s backing up to the
same 'warm standby' secondary EC-1 are NOT supported.
The following procedures must be applied to any 'primary' or 'standby' EC-1

to ensure its successful migration from HP-UX 10.20 to HP-UX 11i.


Consequently, from your network administrator, it is necessary to capture the
following data for the target EC-1, prior to proceeding with the migration
14
from HP-UX 10.20 to HP-UX 11i.
• Hostname.
• LAN0 IP address
• LAN0 subnet mask
• LAN1 IP address
• LAN 1 subnet mask
• IP address of the default gateway, if it is remote from the target EC-1
(Note, if there is no remote gateway for lan1 on the target EC-1 the
default gateway IP address should be the same as the IP address for
lan1).
• ’root' user password
• ’sdhmsusr' password
• ’syseng01' user password.
For every primary EC-1, the following additional data will also be required:
• Operating mode of primary EC-1, e.g. 'hot' or 'warm' standby.
• hostname of secondary 'back up' EC-1,
• LAN1 IP address of secondary 'back up' EC-1
For every secondary 'back up' EC-1, the following additional data will also be
required:
• Operating mode of secondary EC-1, e.g. 'hot' or 'warm' standby.
• Hostname(s) of any primary EC-1(s) backing up to the target secondary
EC-1.
• LAN1 IP address(es) of any primary EC-1(s) backing up to the target
secondary EC-1.
CAUTION

masks of lan0 and lan1 are also the same, halt the migration to
HP-UX 11i and contact Nortel Technical Support.
Note: This information must be validated via Procedure 4.01 below:

Procedure 14-28
Step Action

4 Validate the operating mode of the target EC-1 by checking the shell prompt
label. This should indicate if the EC-1 is 'ACTIVE_HOT', 'STANDBY_HOT',
'ACTIVE_WARM' or 'STANDBY_WARM'.
5 At the shell prompt, type '
more/etc/rc.config.d/netconf↵
(Use the 'spacebar' to page through the file, as required.)
6 Note the 'netconf' entry for 'HOSTNAME'. Check that this is exactly the same
as that provided by the network administrator. If not, halt the migration to
7 Note the 'netconf' entry for 'LOOPBACK_ADDRESS'. This must be
'127.0.0.1'. If not, contact your network administrator and halt the migration to
HP-UX 11i, until the discrepancy is resolved.
—continued—

Procedure 14-28
Step Action
8 Note the 'netconf' entry for 'IP_ADDRESS[0]'. Check that this is exactly the 14
9 Note the 'netconf' entry for 'SUBNET_MASK[0]'. This must be
'255.255.255.0'. If not, contact your network administrator and halt the
migration to HP-UX 11i, until the discrepancy is resolved.
10 Note the 'netconf' entry for 'ROUTE_GATEWAY[0]'. Check that this is exactly
the same as the IP address of the gateway route for the target EC-1 provided
by the network administrator. If not, halt the migration to HP-UX 11i until the
discrepancy is resolved.
12 Note the 'netconf' entry for 'SUBNET_MASK[1]'. Check that this is exactly the
same as the 'lan1' subnet mask provided by the network administrator. If not,
13 Press the 'spacebar' until the scrolling of the 'netconf' file ends and the shell
prompt returns.
14 At the shell prompt, type
more /etc/hosts↵
(Use the 'spacebar' to page through the file, as required.)
15 Ensure that, in the 'hosts' file, there is a single entry for the lan0 IP address,
followed by a 'official hostname' field containing '<hostname of target
EC-1>_0'. If there are duplicate entries for the lan0 IP address with different
'official hostname' fields, or if a hostname field of '<hostname of target
EC-1>_0' is evident beside different IP addresses, halt the migration to
16 Ensure that, in the 'hosts' file there is a single entry for the lan1 IP address,
followed by an 'official hostname' field containing '<hostname of target
EC-1>'. If there are duplicate entries for the lan1 IP address with different
'official hostname' fields, or if a hostname field of '<hostname of target EC-1>'
is evident beside different IP addresses, halt the migration to HP-UX 11i until
the discrepancy is resolved.
17 Ensure that, in the 'hosts' file there is an entry: '127.0.0.1 localhost loopback'.
If not halt the migration to HP-UX 11i until the discrepancy is resolved.
18 18If the target EC-1 is a secondary system, ensure that the 'hosts' file
contains an entry with the hostname and lan1 IP address of every primary
EC-1 system that backs up to it.
—continued—

Procedure 14-28
Step Action
19 If the target EC-1 is a primary, ensure that the 'hosts' file contains an entry
with the hostname and lan1 IP address of the secondary EC-1 that it backs
up to.
20 If the EC-1 is a secondary system, test the IP comms to each primary EC-1
that backs up to it, by typing at the shell prompt,
/etc/ping <lan1 IP address of primary EC-1>↵
For each primary EC-1 backing up to the target secondary EC-1, wait 30
seconds before terminating the 'ping' with 'Cntr+C'. Note any reported loss of
data packets.
21 21If the EC-1 is a primary system, test the IP comms to the secondary EC-1
that stores its back up data, by typing at the shell prompt, '/etc/ping <lan1 IP
address of secondary EC-1><RETURN>'. Wait 30 seconds before
terminating the 'ping' with 'Cntr+C'. Note any reported loss of data packets
22 22If no discrepancies in the 'netconf' and 'hosts' files are evident, and all 'ping'
commands are successful, close the 'xterm' window and log out of CDE/VUE,
otherwise, contact your network administrator.
—end—
Review EC-1 release level on a primary/secondary EC-1

The migration to HP-UX 11i is only supported at EC-1 R16.2. Hence it is
necessary to validate the EC-1 release on the target EC-1s. On the target EC-1
that is to be migrated to HP-UX11i, perform Procedure 15-29 below:
Procedure 14-29
Review EC-1 release level
Step Action

4 At the shell prompt, type 'cat /home/sdhmsusr/tnmsinstall/
INSTALLED<RETURN>
5 Check that the output of this command is 'TNMS_COMMON
TNMS_EC-1.162.az'.If not, log out of CDE/VUE and apply the EC-1 upgrade
procedures described in NTP 323-1091-230, Optical Network Manager EC-1
R16.2 Network Upgrade Procedures. (These are available in PDF format on
the Optical Network Manager EC-1 R16.2 CD-ROM, NTQJ30MZ.). If it is, log
out of CDE/VUE.

Validate the DAT drive on a primary/secondary EC-1
CAUTION
Correct operation of the DAT drive and the compatibility of the

14
available DAT tapes are crucial to preventing the loss of
network configuration data and NE software. Procedure 15-30
below, MUST be applied at this point. If this procedure fails,
you MUST contact Nortel Technical Support before
proceeding.
Note: Procedure 14-55 describes how to add DDS1 compatibility to a DDS

2 or DDS 3 system.
Procedure 14-30
Validate the DAT drive on a primary/secondary EC-1
Step Action

3 Insert a blank, compatible DAT tape into the EC-1 DAT drive and wait for the
lights on the drive to stop flashing.
4 In the 'xterm' window,
type cd /tmp↵
5 In the 'xterm' window, type
touch /tmp/test.txt↵'
rm -rf /tmp/test.txt↵
echo "This is a test!" > /tmp/test.txt↵'
cat /tmp/test.txt↵
If there is no output from this command, repeat steps 4 - 8 before proceeding.
tar cv /tmp/test.txt↵
Wait until the DAT drive lights stop flashing and screen output indicats that the
archive is complete. (If these events are not observed, contact Nortel
Technical Support.)
—continued—

Procedure 14-30
Validate the DAT drive on a primary/secondary EC-1 (continued)
Step Action

rm -rf /tmp/test.txt↵
tar xv /tmp/test.txt↵
Wait until the DAT drive lights stop flashing and screen output indicats that
the archive is complete. (If these events are not observed, contact Nortel
Technical Support.)
cat /tmp/test.txt↵
If there is no output from this command, contact Nortel Technical Support.
Otherwise, repeat steps 3 - 12 above using the second available DAT tape
and then repeat steps 3 - 12 above, using the third available DAT tape.
—end—
Backing up NE software loads on primary/secondary EC-1s

Consequently, it is necessary to ensure that all installed NE software loads are
preserved.
Procedure 14-31
Backing up NE software loads on primary/secondary EC-1s
Step Action
1 Log into the target EC-1 platform as user sdhmsusr

3 Insert the first DAT tape validated in Procedure 14-30 above, into the EC-1
tar cv /home/sdhmsusr/sdhms/data/NE_load↵'
to stop flashing.
and the legend 'NE s/w loads' and store it safely..

Synchronizing primary and secondary EC-1s

Prior to migrating primary and secondary EC-1 systems, it is necessary to
ensure that the network configuration data held on the secondary EC-1
matches that held on the primary EC-1, via Procedure 14-32:
Procedure 14-32 14
Synchronizing primary and secondary EC-1
Step Action
1 If the target platform that is to be migrated to HP-UX11i is a 'primary' element

controller, log into the target EC-1 platform as user sdhmsusr, otherwise, if it
is a 'secondary' EC-1, log into the first EC-1 which backs its network
configuration data up to the target EC-1.
Note: If the target is a secondary EC-1 for a remote primary, telnet into the
primary by logging into the secondary, as described in step 1, opening a shell
window, as described in step 2, below and typing
telnet <IP address of remote primary EC-1>↵
When prompted login with the username and password for 'sdhmsusr'.
2 If logged in at the local EC-1 console, from the CDE menu bar, select
'Application manager' -> 'Desktop Apps' -> 'Terminal'. When prompted, set
the terminal type to 'xterm'. (On VUE desktops, select 'General' -> 'Utilies' ->
'Xterm'.)
3 At the shell prompt, initiate a network back from the primary EC-1 to the
secondary by typing
/home/sdhmsusr/sdhms/bin/remote_arch↵
If a message appears indicating 'ERROR: Could not ping <IP address of
secondary EC-1>, halt the migration to HP-UX 11i and contact your network
administrator, to have the lan1 fault traced, otherwise wait until the archive
from the primary EC-1 to the secondary completes, before proceeding.
4 If logged in via telnet to a remote primary EC-1, type 'exit<RETURN>'
5 If the target EC-1 is a 'warm standby' secondary system, providing 1:many
protection for a number of primary EC-1s, for each primary which backs up
its network data to the target secondary, repeat steps 1 - 4. Once this is
complete, or if the target EC-1 is not a 'warm standby' secondary, providing
'1:many' protection, proceed to step 6

Backing up network configuration data on primary/secondary EC-1s

Consequently, it is necessary to ensure that all network configuration data is
preserved
Procedure 14-33
Backing up network configuration data on primary/secondary EC-1s
Step Action
1 Log into the target EC-1 platform as user sdhmsusr

3 Insert the second DAT tape validated in Procedure 14-30 above, into the
EC-1 DAT drive and wait for the lights on the drive to stop flashing.
4 In the 'xterm' window, type '/home/sdhmsusr/sdhms/bin/
.db_archive<RETURN>'
to stop flashing.
and the legend 'Database archive' and store it safely.
8 If the target EC-1 is not a secondary 'standby' system, proceed to step 12,
otherwise, insert the third DAT tape validated in Procedure 14-30 above, into
the EC-1 DAT drive and wait for the lights on the drive to stop flashing.
9 At the shell prompt, type 'tar cv /home/sdhmsur/sdhms/data/
backup<RETURN>'. Wait until the tape archive has completed and the DAT
tape ejects from the drive.
10 Label the third DAT tape with the hostname of the target EC-1 and the legend
'Primary EC-1 archive' and store it safely.

Shut down the target EC-1 platform

To install the new HP-UX 11i it is necessary to shut down the target EC-1
platform, via Procedure 14-34, below.:
Note: As one half of the primary/secondary EC-1 pair will now be rebuilt,
there will now be a loss of network management resiliency for the rest of 14
the migration to Optical Network Manager EC-1 R16.2 running on
HP-UX11i (Approximately 4 hours for each platform that is migrated to
the new operating system software.)
If the target EC-1 is a primary in a resilient 'hot standby' pair, the secondary
'hot standby' EC-1 will, automatically, start up and manage the network. If the
target EC-1 is a primary element controller, backing up to a secondary 'warm
standby', the following procedures will manually activate the secondary
'warm standby' to manage the network.
Procedure 14-34
Shut down the target EC-1 application
Step Action

3 At the shell prompt type
killsdhms↵
When prompted for a shutdown reason, type
HP-UX migration↵
Wait until the EC-1 application has completed its shut down.
Note 1: If the target EC-1 is a primary, backing up to a 'hot standby'
secondary, at this point wait 3 minutes for the secondary platform to activate.
Note 2: If the target EC-1 is a primary, backing up to a 'warm standby'
secondary, the secondary platform must now be activated, via Procedure
15-35
Procedure 14-35
Activation of 'warm standby' secondary EC-1
Step Action
1 Ensure that OSI comms are available to the gateway network element. Also,
ensure that TCP/IP comms to the Optical Network Manager Application
Platform are available if required.
2 Log into the warm standby as sdhmsusr.
3 Execute the following command:
standbytoactive <primary> ↵
—continued—

Procedure 14-35
Activation of 'warm standby' secondary EC-1 (continued)
Step Action
Where <primary> is the IP address or hostname of the failed primary Optical

Network Manager EC-1.
Setting Element Controller to active mode
If you have not supplied the required parameter, the following message
appears, and the script exits.
Usage: standbytoactive <ec1_name>
where ec1_name is the name or IP address of the EC-1 of which this standby
is to assume the role
Valid EC-1s are as follows:
backup_1
backup_2
4 Various configuration parameters are then checked. The following errors
appear if the configuration is not valid:
BACKUP_PATH_LEADER not found in /home/sdhmsusr/sdhms/lib/
config.conf
If the above message appears, a mandatory line has been removed from the
above file, or the file cannot be opened. Contact Nortel Networks Support.
Could not find /home/sdhmsusr/sdhms/data/standby_mode
No backup_files.conf was copied across
Using the default on this platform
Note that this may produce incorrect results.
If the above message appears, the backup_files.conf cannot be copied
across. The restore process does not know where each file is to be restored
to, and uses the directory information in the current backup_files.conf file.
5 5 The following messages then appear:
Data has been restored. Please check configuration, then
reboot this EC-1.
Note: While this platform is running in active mode, no EC-1
configuration will be copied back to the active EC-1. Therefore, this
machine should not be used for configuration changes. You will be given
the option of copying back any NE configuration files to the active EC-1
when switching back to standby mode.
—continued—

Procedure 14-35
Activation of 'warm standby' secondary EC-1 (continued)
Step Action
6 As root user, reboot the warm standby Optical Network Manager EC-1. 14
7 Wait 3 minutes for the 'warm standby' system to restart
Note 1: When a warm standby platform operates in active mode, the Optical
Network Manager EC-1 users is not updated by default. User management
on the standby platform must be handled the same way as any Optical
Network Manager EC-1 (using the user administration function within the
Optical Network Manager EC-1 main menu).
Note 2: When running the warm standby platform as an active Optical
Network Manager EC-1, other Optical Network Manager EC-1s continue to
archive configuration files to it. The management capabilities of this Optical
Network Manager EC-1 are affected if a large number of Optical Network
Manager EC-1s are backing up to it at the same time. This is due both to the
additional comms on the TCP/IP network, and the extra processing that is
required as a result.
Note 3: The warm standby Optical Network Manager EC-1 does not perform
remote archives, but performs daily tape archives (the same action as a
primary Optical Network Manager EC-1). When working in active mode, you
are warned not to make configuration changes on the active standby
machine, as these changes are not copied back to the primary Optical
Network Manager EC-1 when it is brought back into operation.
—end—
Validation of network visibility

Prior to removing all data on the target EC-1, it is necessary to validate that
network visibility has been retained, via, either the original primary EC-1 (if
the target is aq secondary) or via the secondary EC-1 (if the target is a
primary). This is described in Procedure 14-36:
Note: If a switch to a secondary EC-1 has taken place, it may take up to 50

minutes for the standby EC-1 to gain association with all the NEs in the
network.

Procedure 14-36
Validation of network visibility
Step Action
1 With the target platform now shut down, as user 'sdhmsusr', log into the
'active' primary/secondary EC-1 which is to manage the network while the
target platform is to migrated to HP-UX11i. Note: If the target EC-1 is remote
to the 'active' EC-1, telnet into the 'active' system by logging into the target
EC-1, as described in step 1, opening a shell window, as described in step 2,
below and typing
telnet <IP address of active EC-1>↵
When prompted login with the username and password for 'sdhmsusr'.
2 If logged in at the local EC-1 console, from the CDE menu bar, select
'Application manager' -> 'Desktop Apps' -> 'Terminal'. When prompted, set
the terminal type to 'xterm'. (On VUE desktops, select 'General' -> 'Utilies' ->
'Xterm'.)
cd /tmp↵
4 At the shell prompt, type 'chkpros | grep gmp_init<RETURN>'. If there is
output from this command, proceed to step 5, otherwise check the syntax of
the command and type it again. If after, two attempts, this command fails to
produce output on the 'active' EC-1, contact Nortel Technical Support.
send_ne -l -commsok↵
'Wait until the message
Check File NE_LISTING for info.'
appears, before proceeding.
cat NE_LISTING↵
Take a note of the number of NEs cited as 'managed' and the number of NEs
cited as 'Associated'.
In the instance that a switch to a standby platform has taken place, if the
number of 'Associated' NEs is less than the number of NEs that are
'Managed' and the 'send_ne -l -commsok' command in step 5 has been run
less than ten times, wait 5 minutes and repeat steps 5 and 6; if the standby
platform still displays loss of association after 50 minutes, halt the migration
to HP-UX11i and contact Nortel Technical Support.
In the instance where no switch to a secondary platform has taken place, i.e.
the original primary is still running the network, if the number of 'Associated'
NEs is less than the number of NEs that are 'Managed' and the 'send_ne -l
-commsok' command in step 5 has been run less than four times, wait 5
minutes and repeat steps 5 and 6; if the primary platform still displays loss of
association after 20 minutes, halt the migration to HP-UX11i and contact
Nortel Technical Support.
If the active platform has been seen to have full association with the NEs in
the network, it is safe to proceed with the migration of the target EC-1 to
HP-UX11i.

Install HP-UX 11i on a primary/secondary EC-1

This procedure describes how to install the Hewlett-Packard HP-UX 11i
operating environment on the target EC-1 platform.
Note:
• "Optical Network Manager EC-1 only supports the installation of HP-UX 14
11i from local CD-ROM.
• "HP-UX 11i only supports HP CDE. HP-UX 11i does not support HP-VUE
• "Optical Network Manager EC-1 with HP-UX 11i is supported on the
following platforms B180L, B2600, C3600, C3750
• "Optical Network Manager EC-1 with HP-UX 11i is not supported on
B132L or B132L+
• "The Netscape browser is not supported on HP-UX 11i.
CAUTION
Procedure 14-37 to Procedure 14-38 will destroy all current

data on the EC-1 hard drive. Check that Procedure 14-28 to
Procedure 14-36 have been applied and that a network
configuration freeze is in place before conducting following
Procedure.
CAUTION
It must be certain that Procedure 14-37 to Procedure 14-38 are

applied to the shut down, target EC-1, NOT to any 'active'
EC-1.
Procedure 14-37
or DVD-ROM drives
Step Action
1 Push in the power switch on the monitor.

The LEDs on the front of the monitor light up to indicate that power is on.
2 Push in the power switch to the Workstation.
The power LED lights up to indicate that power is on.
CD-ROM.
To select a new Graphics Monitor Type press the [TAB] key now,
otherwise EXIT by entering other key (or will timeout in 15 seconds)
5 Allow this message to timeout.
—continued—

Procedure 14-37
or DVD-ROM drives (continued)
Step Action
6 Another message appears:

7 In both cases, before this period times out, press any key.The workstation
Main Menu appears, as shown below.
-----Main Menu-----
Command Description
------- -----------
PAth [PRI|ALT|CON|KEY] [<path>] Display of modify a path
...
...
RESET Restart the system
--------------
8 Search for SCSI devices. Type the following command:
search ↵

---- ----------- -----------
9 Boot from the SCSI device that is identified as the CD-ROM drive. In the
above example, where the CD-ROM is path p1, type:
boot p1 ↵
Respond as follows, type:
n↵
11 The operating system is then loaded from the CD-ROM/DVD-ROM drive.
This process is detailed in Procedure 14-21.
—end—

Procedure 14-38
Loading the HP-UXi operating environment from the DVD/CD-ROM drive
Step Action
1 Boot the platform from the DVD/CD-ROM drive (see Procedure 1-1) 14
+---------------------------------------------------+ [Scan Again]
+---------------------------------------------------+ [H/W
Details]
[ Install HP-UX ]
[ Reboot ] [ Help ]
4
installation.
Select the H/W Details tab in the menu above to find the LAN configuration.
LLAN Hardware
Interface Path Type
—continued—

Procedure 14-38
drive (continued)
Step Action
LAN Hardware
Interface Path Type

—continued—

Procedure 14-38
drive (continued)
Step Action
14
screen:
/---------\
| Basic |
|
\-------------------------------------------------------------
Configurations:[ HP-UX B.11.11 Default->] [ Description…]
Environments :[ see below ->] (HP-UX B.11.00)
[ Root Disk …] QUANTUM_ATLAS5-9WS, 8/0/19/0.6.0, 8678 M
File System :[ Logical Volume Manager (LVM) with HFS->]
[Root Swap (MB)… ] see belowPhysical Memory (RAM) = see below
[Languages…] English [ Keyboards… ]
| |
\------------------------------------------------------------/
[ Show Summary … ] [ Reset Configuration ]
--------------------------------------------------------------
--------------------------------------------------------------
—continued—

Step Action
to display its menu. Use the arrow keys to highlight an option from the
key and <RETURN> so that the following screen appears:
/--------\
| System |
/ \-------------------------------------------


--------------------------------------------------------
--------------------------------------------------------
--------------------------------------------------------
—continued—

Procedure 14-38
drive (continued)
Step Action
14
Set the Final System Parameters option to Ask at first boot.
TAB key and Return so that the following screen appears.
Enter the values given in Table 14-10 into the sample table below.
/ --------- \
|File System|
/ \---------------------------------

/ HFS 3000 54 vg00 F
/

| |
\------------------------------------------------------/
--------------------------------------------------------
--------------------------------------------------------
You must remove all other file systems (/tmp, /opt, /usr and /var) by
Configure the following file systems as shown:
Set the /stand, primary and / file systems to the values shown in the
Table 14-10 . In larger workstations, you can set the /home file system to the
changes.
—continued—

Procedure 14-38
drive (continued)
Step Action
Itool Confirmation
/--------------------------------------------------------
| |
\-------------------------------------------------------
/-------------------------------------------------------\
\------------------------------------------------------/
Select Go!
reboots. The routine and reboot takes approximately 45-60 minutes on a
B180L platform.
12 The following screen appears:
/------------------------------------------------------\
"BXXXX 11i OE CD"
\------------------------------------------------------/
—continued—

Procedure 14-38
drive (continued)
Step Action
14
second boot CD-ROM ("HP-UX 11i June 2001 NTNM51ZDAF", disk 2 of 2)
into the CD-ROM drive and continue with the installation.
14 A display of all available keyboard drivers appears. Select the option you
17 Enter the system hostname.
the Yes button.
—continued—

Procedure 14-38
drive (continued)
Step Action

• Central America
• South America
• Europe
• Africa
• Asia
details.
confirm it for use.
—continued—

Procedure 14-38
drive (continued)
Step Action
14
displayed:
LAN Hardware
Interface Path Type
Lan1 8/0/1/0 HP AS230A / B5509BA
PCI 10/100 Base-TX Addon
[ OK ]
displayed:
If you wish networking to operate correctly, you must also assign
the system a unique Internet Protocol (IP) address. The IP address
must:

—continued—

Procedure 14-38
drive (continued)
Step Action
27 The Subnet Mask and Gateway is displayed.

Enter the IP address of LAN port 0 and the Gateway IP Address.
Congratulations! Your system is now configured for networking, with
system name <hostname>, and internet address <ip address>.
You may later want to set up (or finish setting up) additional
network parameters for routing (gateways), DNS and or NIS. If so,
please run the following command (you may want to note this for
further reference):
To fully utilize the capabilities of your system, you may have to

perform some additional system configuration tasks using the HP-UX
"sam" (System Administration Manager) command. Consult your local
administrator or the "HP-UX System Administrator Tasks" manual for
more information.
The system will now complete its boot process, and allow you to
login as 'root'.
—continued—

Procedure 14-38
drive (continued)
Step Action
14

—end—

configuration script, once HP-UX 11i has been installed, via Procedure
14-39, below:
Procedure 14-39
Step Action
enter the password:
root ↵
<password> ↵
(NTQJ30MW).
mkdir /cdrom ↵
—continued—

Procedure 14-39
Step Action

cd /tmp ↵
ls /cdrom/EC-1 ↵
file.
—end—


Procedure 14-40 14
Step Action
sam↵
Type:
csh↵
sam↵
Communications.
Cards.
once.
Modify System name
Configure
—continued—

Procedure 14-40
Step Action
8 Click OK to configure the Ethernet card.

9 If the Default Gateway requires editing, exit from the Networking and
Communication area in sam. Select Hosts from the menu. When the next
menu appears, select Local Hosts file. This opens the Hosts File screen. To
edit the Default Gateway, select the Actions tab and click on Modify Default
Gateway. Enter the IP Address of the machine you want to use as the Default
Gateway and remove the name in the alias text.
/etc/lanscan↵

y
cat /etc/hosts ↵
umount /cdrom ↵
/etc/reboot↵
—end—


Procedure 14-41
Validate LAN cabling 14
Step Action

lan port:
"PCI(10110019) -- Built-in #3" -B132L+
e.g "10/0/14/1".
6 Log out of CDE.


Procedure 14-42
Reinstall Optical Network Manager EC-1 R16.2 SP2 application software
Step Action

’Terminal’
cd /tmp ↵
rm -rf install ↵
ls /cdrom/EC-1 ↵
—continued—

Procedure 14-42
Reinstall Optical Network Manager EC-1 R16.2 SP2 application
Step Action
14
cd install ↵
network as follows:
The EC-1 now runs as an OSI Intermediate System (IS)
instead of an End System (ES). Before you proceed with
this upgrade, you should consider whether or not this
change will impact your OSI DCN network.
Also note the OSI Comms Stack is now configured in the
file osi_comms.conf instead of mfmMAA.dat.
—continued—

Procedure 14-42
Step Action

(if needed)
Directory /cdrom/EC-1 contains the following s/w

packages:

y ↵
Preside_EC-1.162.xx

Preside_EC-1.162.xx

INSTALL: None found

syseng01
admin
netsurv
slat
master
operator
—continued—

Procedure 14-42
Step Action
14
y↵
Otherwise type:
n↵


the following list:

7. Hot standby EC-1
Option [1-7]?
—continued—

Procedure 14-42
Step Action


Cold standby EC-1
<return>
ups type 1 <return>


—continued—
14

Procedure 14-42
Step Action

/usr/ccs/bin/ld: (Warning) Linker features were used that may
not be supported in future releases. The +vallcompatwarnings
option can be used to display more details, and the ld(1) man
page contains additional information. This warning can be
suppressed with the +vnocompatwarnings option.

cd /tmp/install ↵
the Caution:
—continued—

Procedure 14-42
Step Action
14
CAUTION


accordingly.
If Then go to
—continued—

Procedure 14-42
Step Action

#
#
#
#
#
#
MAA1=490000
[ISIS Routing]
#
#
ISIS_ROUTER=LEVEL1
#
PRIORITY_L1=60
#
PRIORITY_L2=60
[LAN Card Routing]

#
#
LAN0=LEVEL1_ONLY
#
#
/etc/reboot ↵
—end—


below:
CAUTION
14
LAN 1 at HP-UX 11i

workstation.
OR
Procedure 14-43
Step Action

session.
—end—

Procedure 14-44
Validating a 'hot standby' secondary EC-1 application
Step Action

'Terminal'. When prompted, set the terminal type to 'xterm'. Maximise the
'xterm' via the 'maximise' check button on its top right corner.
3 At the shell prompt, type '/etc/ping <IP address of primary
EC-1><RETURN>', where <IP address of primary EC-1> is the IP address of
the primary EC-1 which backs its data onto the target EC-1. After 30 seconds
terminate the 'ping' with 'Cntr+C'. If any packet loss is noted in the 'ping'
output, check the network connections and configuration on the target EC-1.
4 Log out of CDE.
—end—
Procedure 14-45
Validating a 'warm standby' secondary EC-1 application
Step Action

'Terminal'. When prompted, set the terminal type to 'xterm'. Maximise the
'xterm' via the 'maximise' check button on its top right corner.
3 At the shell prompt, type '/etc/ping <IP address of primary
EC-1><RETURN>', where <IP address of primary EC-1> is the IP address of
the first primary EC-1 which backs its data onto the target EC-1. After 30
seconds terminate the 'ping' with 'Cntr+C'. If any packet loss is noted in the
'ping' output, check the network connections and configuration on the target
EC-1.
4 For each primary EC-1 which backs its data to the target EC-1, repeat step 3.
5 Log out of CDE
—end—


Procedure 14-46 14
Step Action
Procedure 14-5 Backing up network configuration data into the tape drive,
and wait for the tape drive lights to stop flashing.
sdhmsusr ↵
<password> ↵
killsdhms ↵

....5....10....15....20
....25
db_restore ↵
WARNING!
--------
Restoring the configuration will overwrite current EC-1 configuration files.
Please be sure you have a valid backup for this machine should you wish
to preserve any configuration files.
Enter n to cancel the operation. The script exits with the following
message:
6 The status of the tape is then checked. The following message appears:
—continued—

Procedure 14-46
Restoring network configuration data (continued)
Step Action

Try again [yn] ?
8 The tape is ejected and the script completes with the following messages:
Ejecting tape
Restored files
<RETURN>.
reboot<RETURN>
—end—


14-47 below.
Procedure 14-47 14
Step Action

3 Insert the second DAT tape labelled 'NE s/w loads', created in Procedure 14-5
above, into the EC-1 DAT drive and wait for the lights on the drive to stop
flashing.
to stop flashing.
7 Log out of CDE.
—end—

Procedure 14-48
Step Action
earlier procedure into the tape drive, and wait for the tape drive lights to stop
flashing.
sdhmsusr ↵
<password> ↵
—continued—

Procedure 14-48
Step Action
killsdhms ↵

....5....10....15....20
....25
db_restore ↵
WARNING!
--------
Restoring the configuration will overwrite current EC-1 configuration files.
Please be sure you have a valid backup for this machine should you wish
to preserve any configuration files.
Enter n to cancel the operation. The script exits with the following
message:
6 The status of the tape is then checked. The following message appears:
Try again [yn] ?
—continued—

Procedure 14-48
Step Action
8 The tape is ejected and the script completes with the following messages: 14
Ejecting tape
Restored files
<RETURN>.
reboot<RETURN>
—end—
Restoring NE software loads on primary / secondary EC-1s

14-15 below.
Procedure 14-49
Restoring NE software loads on primary / secondary EC-1s
Step Action

3 Insert the second DAT tape labelled 'NE s/w loads', created in Procedure
14-32 above, into the EC-1 DAT drive and wait for the lights on the drive to
stop flashing.
to stop flashing.
7 Log out of CDE.
—end—

Restoring EC-1 archives on secondary EC-1s

If the target platform is a secondary EC-1, it is necessary to restore the EC-1
network configuration archives, previously stored to DAT.
Note: This procedure does not apply to primary EC-1s

Procedure 14-50
Restoring EC-1 archives on secondary EC-1s
Step Action

3 Insert the second DAT tape labelled 'EC-1 archive', created in Procedure
14-32 above, into the EC-1 DAT drive and wait for the lights on the drive to
stop flashing.
to stop flashing.
7 Log out of CDE.
Note: If the target EC-1 was a standby system, the migration procedures
for the platform are at an end. Procedure 14-28 to Procedure 14-53 should
now be applied to all the primary EC-1s, whick back up their network
configuration data to this newly migrated, standby EC-1 system.
—end—
Switching back from a standby EC-1 to the target EC-1

If the target EC-1, which has just been migrated to HP-UX11i, is a primary, at
this point, it is necessary to switch control of the NEs back from the
secondary, which has been managing the network during the migration, back
to the primary EC-1. Procedure 14-51 describes switching back to the
primary from a 'warm standby' secondary EC-1. Procedure 15-52 describes
switching back to the primary from a 'hot standby' secondary EC-1.
Procedure 14-51
Switching back from a warm standby platform
Step Action
1 Ensure that OSI comms are available to the gateway network element. Also,
ensure that TCP/IP comms to the INM are available if required.
2 Log into the warm standby as sdhmsusr.
—continued—

Procedure 14-51
Switching back from a warm standby platform (continued)
Step Action
3 Execute the following command: 14

activetostandby ↵
Setting Element Controller to stand-by mode
Do you wish to copy NE backup files back to the primary

EC-1? [yn]
4 Enter n if you wish to abort the operation. The script exits.
Enter y if you wish to copy the network element backup files back to the
primary Optical Network Manager EC-1.
5 You are then prompted for the IP address of this platform:
Enter the IP address of the primary EC-1:
Enter the IP address. Comms to this IP address are then checked. The
following message appears:
Testing comms to <ip_address>
If comms can be established, the files are copied back to the primary Optical
Network Manager EC-1. The following message appears:
Copying NE backup files to <ip_address>
If comms cannot be established, the following message appears, and
execution of the script continues.
Can not communicate with <ip_address>
Reboot workstation to restore standby mode
7 As root user, reboot both the warm standby Optical Network Manager EC-1
and primary Optical Network Manager EC-1 platforms.
—end—

Procedure 14-52
Switching back from a hot standby platform
Step Action
1 1 Ensure that both IP and OSI comms are available to both the hot standby
and primary Optical Network Manager EC-1 platforms.
On the Primary Optical Network Manager EC-1
2 On the primary EC-1 platform, log in as user 'sdhmsusr', select from the CDE
menu bar 'Application manager' -> 'Desktop Apps' -> 'Terminal'. When
prompted, set the terminal type to 'xterm' and, at the shell prompt,
'killsdhms<RETURN>. When prompted for a shutdown reason, type 'Switch
from standby' and wait fro the EC-1 application to shut down.
3 On the primary Optical Network Manager EC-1 platform, log out of Optical
Network Manager EC-1 to the HP login banner.
On the Standby Optical Network Manager EC-1
4 Login to the active standby EC-1 as sdhmsusr from the HP login banner by
typing:
sdhmsusr↵
<password> ↵
Note: refer to Procedure 10-20 for further information on Hot Standby Login.
5 Open a UNIX window from the workspace manager and type the following:
/home/sdhmsusr/sdhms/bin/activetostandby ↵
Setting Element Controller to standby mode
Do you wish to copy NE backup files back to the primary
EC-1? [y, n]
6 Type:
y↵
Enter the IP address of the primary EC-1
7 Enter the IP address of the primary Optical Network Manager EC-1 platform
and press Enter.
Testing comms to <IP address>
Copying NE backup files to <IP address>
Where <IP Address> is the IP Address of the Primary EC-1
Hot standby functionality is currently ENABLED
Reboot workstation to restore standby mode.
ATTENTION: Do not reboot the Standby Optical Network Manager
EC-1 yet. This step must be performed later in the procedure.
∇χοντινυεδ∇

Procedure 14-52
Switching back from a hot standby platform (continued)
Step Action
8 Shut down the Optical Network Manager EC-1 by typing the following 14
command:
killsdhms↵
9 You are asked to enter a reason for the shut down command. This reason is
recorded in a log file. At the Reason: prompt, type:
EC-1 Switch Over ↵
On the Primary Optical Network Manager EC-1
10 On the primary Optical Network Manager EC-1 reboot the primary Optical
Network Manager EC-1.
This activates the primary Optical Network Manager EC-1 as the active
manager.
11 Wait until the primary Optical Network Manager EC-1 is up and running.
On the Standby Optical Network Manager EC-1
12 Then, on the hot standby platform, logout to the HP login banner.
13 On the hot standby platform login as root by typing:
root ↵
<password>↵
14 In a Unix window, reboot the hot standby Optical Network Manager EC-1
platform:
/etc/reboot↵
This re-establishes the hot standby Optical Network Manager EC-1 as the hot
standby manager.
—end—
As a post-migration check, on the active primary EC-1 platform it is
necessary to validate the association of all the NEs in the EC-1's span of
control, both with the EC-1 and, if a PAP is managing the primary EC-1, at
the GNB, using Procedure 14-53 below:
Note 1: On large networks, after the completion of Procedure 14-52 above,

it may take up to an hour for the DCN to settle and the Optical Network
Manager EC-1 application to regain full association with the NEs in its
span of control.
Note 2: Procedure 14-53 does not apply to an inactive secondary EC-1

Procedure 14-53
Step Action

session.
4 From the EC-1 main menu, select the 'Network Element Access Tool'(NAT).
5 From the EC-1 Alarm menu, select 'View active alarm list'
6 Monitor the NAT to ensure that all managed NEs eventually display their
software version, whilst also monitoring the 'Active alarm list' to ensure that
all unexpected comms fails to NEs clear and the EC-1 'Messages' window for
any 'Failed to control' messages. If, after an hour, there are NEs that still
display unexpected 'Comms fail alarms', contact the network administrator to
attempt to resolve the discrepancy.
7 Once all NE's have regain association with the EC-1, log into the Optical
Network Manager AP as user 'admin' and open the GNB view for the primary
'active' EC-1. If all NEs are 'blue' on the GNB, check the network configuration
and connections on the primary active EC-1.
Shutdown of any 'temporary' standby EC-1
If a temporary EC-1 platform was installed as a 'warm standby' secondary, it
can now be shut down, using Procedure 14-54.
Procedure 14-54
Shutdown of any temporary 'standby' EC-1
Step Action
1 Log into the EC-1 platform as user root

'Terminal'. When prompted, set the terminal type to 'xterm'.
/etc/reboot -h ↵
Note: Note: the temporary 'standby' EC-1 platform may now be
disconnected from the network.
The migration of a standby/primary Optical Network Manager EC-1 is

now complete.
—end—

Installing DDS1 DAT drivers

The HP B180L and C3600 platforms use DDS2 DAT drivers by default. The
HP C3750 platform uses DDS3 DAT drivers by default.
The process for installing DDS1 DAT drivers on the B180L, B2600, C3600
and C3750 platforms is given in Procedure 14-56. If you do not require this 14
facility, ignore this section of the installation process.
Procedure 14-55
Installing DDS1 DAT drivers (B180L, B2600, C3600 and C3750)
Step Action
1 Log in as root user and open a UNIX window.

2 Run a scan of devices, type:
/etc/ioscan ↵
3 Visually search the result for a tape entry, such as:
8/16/5.3.0 tape HP HP35480A
The first column of this line is the hardware path. Make a note of this.
4 Establish the required driver as follows:
/etc/mksf -H <hardware_path> -b DDS1 /dev/rmt/dds1 ↵
For example, using the hardware path described in step 3:
/etc/mksf -H 8/16/5.3.0 -b DDS1 /dev/rmt/dds1 ↵
To create a tape on the B132L, B132L+, B180L, C3600 and B2600 platforms
using these new drivers, perform the following procedure:
Procedure 14-56
Creating a DDS1 DAT (B132L, B132L+, B180L, B2600, C3600 and C3750)
Step Action
1 Change to the parent directory of the directory from which you wish to write
to tape, by typing:
cd <parent_directory> ↵
2 Use the tar command to write the directory to tape, specifying the new driver
for use. That is:
tar cvf /dev/rmt/dds1 <directory> ↵
CAUTION
All 'tar cv <directory>↵' and 'tar xv' commands, used in earlier

procedures, must be substituted by 'tar cvf /dev/rmt/dds1
<directory> ↵' and 'tar xvf /dev/rmt/dds1↵', respectively.
—end—

Changing the default RCA directory

This section describes how to change the default backup directory for the
Remote Central Archive (RCA) operations.
Note 1: Only perform Procedure 14-57 if an RCA is in use, and you want
to change the default destination directory. The default directory on the
RCA platform is:
/home/sdhmsusr/sdhms/data/backup/<IP address>/RCA_Dir
Note 2: All Warm standby platforms contain a remote central archive.

Independent platforms that do not use Optical Network Manager EC-1
software can also contain a remote central archive.
Procedure 14-57
Changing the default RCA directory
Step Action
1 Log into the EC-1 platform.

2 Click on its tick box to open the System Engineer section of the main menu
and select the UNIX window option to open a UNIX window.
3 To change the default directory for the RCA backup, use either ’vi’, ’vuepad’
or another text editor to edit the file:
/home/sdhmsusr/sdhms/lib/config.conf
Type:
cd /home/sdhmsusr/sdhms/lib/config.conf ↵
4 Edit the config.conf file with your required changes, for example:
a. Change the ‘leader’ element of the default address (that part of the
address that is before the <IP address>):
BACKUP_PATH_LEADER <leader>
b. Change the ‘trailer’ element of the default address (that part of the
address that is after the <IP address>):
BACKUP_RCA_TRAILER <trailer>
Note: The <IP address> element of the directory structure is mandatory.
For example, to backup to the directory:
/ec1/<ip_address>/backup,
Change the config.conf file as follows:
BACKUP_PATH_LEADER /ec1
BACKUP_RCA_TRAILER backup
—end—

Scheduling network configuration back ups to a remote system

This section describes how you can (optionally) configure the RCA schedule
(that is, the time at which information is sent to RCA platform):
Procedure 14-58
Scheduling network configuration back ups to a remote system
14
Step Action
1 Run the following command from a UNIX window:

crontab -e ↵
This action gives you a 'vi' editor window, containing the current cron settings.
2 Move the cursor down to the line containing:
/home/sdhmsusr/sdhms/bin/remote_arch
In this line, the first two fields identify the minutes and hours at which the
command must be executed. The default entries are 30 6, which refers to
06:30. Archives can be taken at any time during the day, or at a number of
times during the day. For example, replacing the first 2 fields with 0 * will
cause an archive to be taken every hour, on the hour. Also 0 0,6,12,18 will
cause an archive to be performed every 6 hours (at midnight, 06:00, 12:00,
and 18:00).
More information can be obtained by typing the following from a UNIX
window:
man crontab ↵ If you need more information about the values to which these
fields need to be set for your own requirements, contact Nortel Networks
Technical Support.
3 To configure the archive time, change the first two fields:
a. Ensure the cursor is at the left-most position, on the correct line.
b. Press x to delete the first two fields character by character. Ensure you
delete only the first two fields.
c. Press i to insert, then type the required values for the first two fields.
Ensure they are separated by a space, and do not enter more than two
fields. Also, ensure there is a space after the second field.
d. If the file is correct, press Escape, then :wq to exit and save the new file.
If the file is incorrect, press Escape then :q! to abort the operation, and leave
the file unchanged.
—end—

Moving to a new HP-UX11i platform

Note: These procedures should be applied to Optical Network Manager
EC-1 running on HP 715/100, B132L and B132L+ platforms, as they do
not support HP-UX 11i:
If HP-UX 11i is not supported on the current EC-1 platform, to migrate from
HP-UX 10.20, it will be necessary to swap out the existing platform and
replace it with a new one. This is described in procedure E-1, below.
Note 1: The following procedure requires that the old EC-1 platform is
deleted from the span of control of any Optical Network Manager AP and
that the new HP platform will be added in its place. This may result in the
loss of network connectivity diagrams laid out in the GNB on Optical
Network Manager AP.
Note 2: This procedure will require your network administrator to supply
new permanent IP addresses for LAN0, LAN1 and the gateway IP address
via which it will reach the TCP/IP network, plus a new hostname for the
new HP-UX 11i platform. The LAN1, LAN 0 IP addresses of the old
HP-UX 10.20 system and its hostname should NOT be applied to the new
system.
CAUTION
Risk of loss of network configuration data
To ensure that network configuration data is successfully
archived from the old HP-UX 10.20 platform to the new
HP-UX11i platform, it is crucial to use DAT tapes of the correct
format depending on the type of DAT drive installed in the
platform that is to be swapped out. The following table defines
the formats of the DAT tapes that should be used:
Tape Drive in old EC-1Media Options
DDS1 DAT DRIVE90m DDS1 DAT
DDS2 DAT DRIVE90m DDS1 DAT / DDS2 DAT
DDS3 DAT DRIVE90m DDS1 DAT / DDS2 DAT / DDS3 DAT

Procedure 14-59
Moving to a new HP-UX11i platform
Step Action
1 If the old HP-UX 10.20 platform is not currently running EC-1 R16.2, upgrade 14
it to this release using the EC-1 R16.2 upgrade procedures, set out in NTP
323-1091-202. Note: For the purpose of HP-UX11i migration, running EC-1
R16.2 on an HP 715/100 platform is supported for the duration of the
migration.
2 Record the hostname, LAN 0, LAN 1 and gateway IP addresses of the old
HP-UX 10.20 platform.
3 Apply Procedure 14-1 Validate platform configuration data to the old HP-UX
10.20 platform.
4 Apply Procedure 14-2 Review EC-1 release level to the old HP-UX 10.20
platform.
5 Apply Procedure 14-3 Validate the DAT drive on a primary/secondary EC-1
to the old HP-UX 10.20 platform.
6 Apply Procedure 14-4 Backing up NE software loads on primary/secondary
EC-1s to the old HP-UX 10.20 platform.
7 If the target EC-1 is part of a resilient standby configuration, apply Procedure
14-32 Synchronizing primary and secondary EC-1s to the old HP-UX 10.20
platform, otherwise got to step 8.
8 Apply Procedure 14-5 Backing up network configuration data on primary/
secondary EC-1s to the old HP-UX 10.20 platform.
9 Apply Procedure 14-8 Install HP-UX 11i on a primary/secondary EC-1 to the
new HP-UX 11i platform.
10 Apply Procedure 14-55 Installing DDS1 DAT drivers (B180L, C3600 and
B2600)
11 Apply Procedure 14-9 Loading LAN configuration script to the new HP-UX 11i
platform.
12 Apply Procedure 14-10 Configuring the second Ethernet port to the new
HP-UX 11i platform.
13 Apply Procedure 14-11 Validate LAN cabling to the new HP-UX 11i platform.
14 Apply Procedure 14-12 Reinstall Optical Network Manager EC-1 R16.2
application software to the new HP-UX 11i platform.
15 Apply Procedure 14-13 Validating the EC-1 application to the new HP-UX 11i
platform.
16 Apply Procedure 14-14 Restoring network configuration data on primary/
secondary EC-1s to the new HP-UX 11i platform.
17 Apply Procedure 14-15 Restoring NE software loads on primary/secondary
EC-1s to the new HP-UX 11i platform.
18 If the target EC-1 system is a 'standby' system, apply Procedure 14-50
Restoring EC-1 archives on secondary EC-1s to the new HP-UX 11i platform.
—continued—

19 Apply Procedure 14-34 Shut down the target EC-1 application to the old
HP-UX 10.20 platform.
20 Disconnect all power and lan cables from the old HP-UX 10.20 platform.
21 If the target EC-1 system is a 'primary' in a 'hot standby' resilient pair, apply
Procedure 14-52 Switching back from a hot standby platform to the 'hot
standby' system that the target EC-1 backs up to.
22 Apply Procedure 14-53 Validation of NE association to the new HP-UX 11i
platform.
23 Log into the new HP-UX 11i platform as 'root' user and from the CDE menu
bar, select 'Application manager' -> 'Desktop Apps' -> 'Terminal'. When
prompted, set the terminal type to 'xterm'. (On VUE desktops, select 'General'
-> 'Utilies' -> 'Xterm'.
24 If the old HP-UX 10.20 platform was managed by a Optical Network Manager
AP(PAP), it should be deleted from the PAP's span of control via the
'Controllers' -> 'Show list of controllers' menu in the GNE. In the list of
controllers, right click on the old HP-UX 10.20 platform and select 'Delete
controller'.
25 If the new HP-UX 11i platform is to be managed by a PAP, it should be added
the PAP's span of control via the 'Add a controller'menu on the GNE. In the
'Validation window, enter the LAN 1 address of the new HP-UX11i platform
and click on 'Validate'. If the new controller successfully validates, click on
'OK' and select 'File' -> 'Save' to save the GNE. If the new controller does not
validate, check the network connection between the PAP and the new EC-1
platform, before repeating this step..
26 The move to a new HP-UX 11i platform at an end.
—end—

14

15-1
Appendix D: DCN Guidelines 15-

15
Introduction
This appendix indicates the DCN guidelines.
Table 15-1
DCN Guidelines
Domain Engineering Limits and Considerations
EC-1 Maximum Managed NEs is 128
A single LAN may have no more than 32 ISs attached.

With LANs which exceed this limit, the size of the LSP
(link State Packet) exceeds the maximun allowed PDU
(Packet Data Unit) size of 512 bytes in an NE.
EC-1/SDH NE Maximum of 63 ISs between an SDH NE and its EC
Maximum of 3 Manual Area Addresses (MAA) per OSI

Level 1 area (see note 2)
A maximum of 150 ISs per OSI area (L1 IS-IS routing

area) with the number of ESs + ISs totalling no more than
260.
Supported Authority and Format Indicator (AFI) formats:

39, 49, 47, 59, 45, 57, 43, 55, 41, 53, 37
Variable lenght MAAs within the range of 3 (local format

e.g. 490000) to 13 bytes are supported (26 Digits)
Do not exceed 200, (155 for TN-1C and TN-1P), LSPs

(ISs and pseudonodes) in a single OSI area.
(Pseudonodes are additional LSPs generated, as a
result of IS to IS LAN connections.) i.e. one pseudonode
exists per LAN segment.
For example in an OSI area of 150 ISs, do not exceed 50
pseudonodes. In an OSI area of 140 ISs, 60
pseudonodes would be allowed.
SDH NE Max of 5 daisy chained NEs via LAN cable. closure is not
permitted
Ethernet LAN A 10 BaseT LAN segment can be a maximum of 100m

15-2 Appendix D: DCN Guidelines
Note 1: Since each DCC link creates an entry within a LSP, Nortel
Networks recommends that where possible one only of RS or MS DCC is
configured between adjacent NEs. This reduces redundancy in the routing
table, commonly referred to as "equal cost paths".
Note 2: Each MAA entry is automatically copied to the NE's CAA
(Computed Area Address) list. An NE can have a maximum of three CAA
entries in an L1 (Level-1) area. If a fourth address is computed, then the
area address with the highest left-hand digits will be dropped even if it is
one derived from an MAA entry.
Note 3: DCC links between different Level 1 areas should be disabled.
Note 4: NE links between IS-IS interface should be configured as the
same interface type e.g. Level 1 on NE should be Level 1 on router, Level
1-2 on NE should be configured as L1-2 on the router.
Note 5: On a single DCC link only RS or MS comms should be enabled,
having both enabled serves no purpose, RS has an OSI metric of 6 and
MS a metric of 5, comms would always be routed via MS since it has a
smaller metric.
Note 6: On the EC-1 LAN0 should be used for OSI traffic and LAN1 for
IP traffic. GRE tunnels (OSI over IP) should only be configured on
LAN1.
Table 15-2
OSI Metrics summary
Comms Medium OSI metric
RS DCC 6
MS DCC 5
Ethernet (L1 or L2) NE 4
GRE Tunnel (L1 or L2) 25
end of chapter

16-1
Appendix E: PM Engineering
guidelines 16-
This appendix describes the Performance Monitoring (PM) enhancements in
EC-1 rel 17 software. 16
Limits on PM collection
The maximum number of 24hr PM points, which should be enabled when,
spread evenly across a network and available for collection by the EC-1, is
15000. An additional maximum of 1000 15 minute PM points can be
collected by the EC-1 for fault diagnosis. ONLY the B2600, C Series and RP
Series platforms support these increased limits. The B180L platform supports
a maximum of 5000 24hr PM points and an additional 800 15 minute PM
points only.
In addition the following table also specifies the maximum number of PM

points that can be set per NE type
Table 16-1
PM points per NE
Ne type Maximum number of PMPs for a single

NE of this type
OM4200 Release 3.10 and 4.x 262 points
OM4100 Release 3.01 and 4.x 262
OM4150 Release 7.x 262
TN-1X Release 9 70
TN-1C Release 5.45 and 6 70
For the above NE specific limits, it should be noted that if 24 hour, 15 minute,
UAT or any combination of these durations are enabled on a single PM point,
this still counts as just one PM point., e.g.,
183, S2-2 , LP , 24H, PM_monitoring=On
183, S2-2 , LP , 15M, PM_monitoring=On

16-2 Appendix E: PM Engineering guidelines
The above counts as a single PMP.
To count the PM points enabled on the NEs in the EC-1's span of control,
'Performance monitoring point control script Version 1.24'
The above recommendations are only valid if:-

• the EC-1 PMP collection window has been set to a minimum of 4 hours.
Note: 15 minute PMs should only be used for fault diagnosis and
collection at the EC-1 should be disabled under any other circumstances.
EC-1 Span of control guidelines

The EC-1 Span of Control is based on the volume of data that the network
sends to the EC-1 and is dependent upon a large number of factors including
the following:
• EC-1 Platform
• Number and type of NEs
• Number of alarms being generated
• Number of connections
• Number of PM points enabled
• Enabling of 15M PMs
• Software downloads
• Configuration Backup and restore
• Number of Optical Network Manager AP connected
• Trail Manager running
• Trail Explorer running
• Number of CLUI sessions
A single EC-1 can support 128 NEs and 4 directly connected Optical
Network Manager platforms within its SOC. A maximum of 80 OM 4000s
are recommended within the span of control.
Of these 80 OM 4000s, a maximum of 50 can be OM 4200s.
Note: It is recommended that a B180L or higher spec platform is used to

manage OM 4200s. The EC-1 will be able to handle the following
simultaneous conditions without failure:
• 128 NEs (mixed) each configured as managed.

• A maximum of 80 OM 4000s.
• A maximum of 50 OM 4200s.
• 40 alarms/second from various NEs (not per NE)
• 2 EC-1 users logged in, each with 2 OCS windows
• 4 Optical Network Manager APs attached

Appendix E: PM Engineering guidelines 16-3
Performance monitoring point control script - pm_control
Note: This script does not provide any support for IPPM.
The script provides the followig features:-

• This script disables and enables the performance monitoring points
(PMPs), alarms and bit error rates required to provide the maximum
possible monitoring of network traffic, without significant degradation of
network performance. The script implements an 'optimal' PMPs, alarms
and bit error rates recommended by Nortel Networks. This consists of
'RS', 'MS' and 'LP near end PMPs and alarms, with specified alarm
thresholds. Note, for each PMP both the 24 hour and 15 minute durations
are enabled on the NE. (Refer to Section for the EC-1 collection 16
guidelines.)
• The script also provides the option to total the number of PMPs in the
network, so ensuring that there is an overall gauge on the network loading
produced by the performance monitoring (PM) within it. Note, a single
PMP is counted if it has 24 hour, or 15 minute, or UAT or any
combination of these durations enabled, e.g.
183, S2-2 , LP , 24H, PM_monitoring=On

183, S2-2 , LP , 15M, PM_monitoring=On
The above counts as a single PMP.
• In one pass, the script is capable of updating the PM settings of one or more
NEs, of various NE types. This is of considerable advantage to the user, as
it will cut out a large amount of manual CLUI configuration.
• The script operates with OM4200 R3.1 and R3.5, OM4100 R4.5, OM4150
R6.0, TN-1X R9.0, TN-1C R5 and TN-1P R5 NE software loads.
Variation in NE type will not affect the operation of the script. (NB: The
script does not currently support TN-4T, or NE releases that support
intermediate performance monitoring points, i.e., OM4200 Release 4 and
OM4150 Release 7.)
• The user has the option to turn PMs either 'OFF' or 'ON', on one or more
NEs.
• On OM4000 NEs, the script is not affected by alterations of the
connections in the NE but will, instead enable PMPs for cards, which are
logically equipped in the shelf. Hence, alterations in network connections
will not disturb the NE's PM configuration. Note, for TN-1X, TN-1C and
TN-1P NEs altering the connections within the NE will disturb its 'LP'
PMP settings on the PDH ports where connections have been altered.
However, with such an NE, the script can be run again to reset the
'optimal' set of PMPs. In this instance, only 'non-optimal' PM
configuration will be updated.
• Before applying this 'optimal' PM set, the script ensures that all
'non-optimal' PMPs on the NE are set 'OFF', so ensuring that only the
'optimal' supported PM configuration is implemented on the NEs in the

network. This ensures that that each NE has an accurate and sustainable
PM monitoring configuration.
• To minimize network loading, the script does not run during NE
configuration back ups.
• To minimize EC-1 CPU loading, the script uses a low UNIX 'nice' value.
• The script minimizes the login handling and processing required on the
NE.
• For each NE, the script logs the CLUI commands and responses generated,
as well as user selections, hence providing a record of PM network
configuration.
• The script prevents any attempt to re-engineer it, so providing security
against inappropriate network configuration.
Requirements
• A network configuration freeze must be in place for the duration of the

PMP updates.
• OM4200 R3.1, OM4200 R3.5, OM4100 R4.5, OM4150 R6.0, TN-1X
R9.0, TN-1C R5 or TN-1P R5 NE software loads.
• The script should not be run at a time when it is likely to conflict with the
routine back up of NE configurations to the EC-1.
• The EC-1 should be running.
• There should be NO Browser, CLUI or CAT sessions running when the
executable is run.
• All NEs targeted for update by the script must be MANAGED from the
EC-1 where the executable is run.
• There must be NO loss of comms between the EC-1 and a target NE.
• At least 10 Mb of available space in the EC-1's '/tmp' directory
Recommendations
The script is capable of updating the PMP configuration of up to 128 NEs in
one pass. However, since performance monitoring will place an additional
load on data communication network (DCN), it is strongly recommended that
the script is run against a 'batch' of NEs in the EC-1 SOC. Once this 'batch' of
NEs has had their PMP configuration updated by the script, the user should
check the EC-1 for any current 'loss of comms'(LOC) alarms and, if any new
LOC alarms have been raised since the script was run, investigate. The
number of NEs that should be included in such a 'batch' is dependant on the
following factors:
• The available maintenance window; depending on the NE configuration,
i.e., the number of 'non-optimal' PMPs that will need to be disabled and
the number of 'optimal' PMPs that need to be enabled, the script can take
between 5 minutes and two hours to process an individual NE.
• An estimate of total number of PMPs that will enabled in the 'batch'; this
will be dependant on the number of PM ports on each NE in the 'batch'.

• "N.B. NEs with a lot of 2M tributary cards will have a large number of
'LP' PMPs to be enabled.
As stated the script runtimes will vary for each NE, depending on the cards it
has logically equipped and the PMPs currently enabled on it. Consequently it
is only possible to give very broad estimates of the time required for the script
to enable the 'optimal set' of PMPs on a particular NE type. However, the
following estimates should give a reasonable guide to assessing the necessary
maintenance window required to reconfigure each NE:
Note: : the following calculations are based on NE's which do NOT have
any "non optimal" PMPs enabled. If 'non-optimal' PMPs need to be
removed from the NE configuration, the additional time required for this,
will depend on the number of 'non-optimal' PMPs enabled, calculated at
10 seconds per 'non-optimal' PMP. This should be summed for the target 16
NE and added to the times given below for enabling the 'optimal set' of
PMPs, for the appropriate NE type:
Saturn NE's
10 minutes + 14minutes per 2M tributary card
TN-1X NE's
10 minutes + 20 minutes per 2M tributary card
TN-1C NE's
5 minutes + 4 minutes (if 8x2M tributary card in spare slot)
or
5 minutes + 16 minutes (if 32x2M tributary card in spare slot)
TN-1P NE's
4 minutes
To run the executable run the following procedure

Procedure 16-1
Run the pm_control script
Step Action
1 Log into VUE/CDE as user 'syseng01'and start an EC-1 GUI session.

2 Click the 'Alarm Monitoring' menu's 'View Alarm Log List' option and check
the output for signs of comms loss to the target NE. If any 'Loss of comms to
SMX' alarms are noted, investigate before preceding.
3 If comms appears stable, check that there are no open Browser or CLUI
sessions running in the current EC-1 GUI session. If there are, close them.
NB: Browser sessions should always be closed via the NE 'Logout' menu
option. Do NOT simply close the 'X-Window' that the browser is running in.
4 If NE PMPs are to be disabled/enabled, click the 'Main' menu's 'Network
Element Access' option and view the 'Network Element Access' window to
ensure that the target NEs are MANAGED.

5 Click on each target NE in and use the right mouse button to 'View NE
Details'. Record the NE's Area address and MAC address before closing the
'View NE Details' window.
6 If NE PMPs are to be disabled/enabled, for each target NE back up its
configuration to the EC-1 via Procedure 5-14, page 5-20 of the EC-1 User
Procedures NTP 323-1091-402.
7 From the 'System Engineer' window, select 'UNIX window'. When the UNIX
window appears, type 'ps -elf | grep ocsmain | grep -v grep<RETURN>'. If
there is any output from this command, trace the source of the open CLUI
sessions, e.g. Optical Network Manager AP or an 'X-Terminal' and close them
before proceeding, otherwise continue from step 8.
8 Check that nobody is using a CAT terminal on the network.
9 Log out of the EC-1 and then exit CDE/VUE.
10 Log into the EC-1 at the CDE banner as 'sdhmsusr'
11 On the CDE menu bar, click on 'Application Manager' -> 'Desktop Apps' ->
'Terminal'. When the 'Terminal' window appears, set the terminal type to
'xterm' and maximise it by clicking on its 'maximise' button in the top right
corner.
12 Type '/home/sdhmsusr/patches/EC-1/pmp/pm_control<RETURN>'. The
script will then display the following menu:
PM CONTROL 1.24
================
The following options may be applied to one or more NEs.
1) Set all PM collection OFF.

2) Set optimal PM collection ON.
3) Count enabled PMPs in EC-1 SOC.
4) Exit.
Enter selection:
To disable PMPs on selected NEs, enter digit '1<RETURN>' and proceed to
step 14.
To enable 'optimal' PMPs on selected NEs, enter digit '2<RETURN>' and

proceed to step 14.
To total the enabled PMPs within the span of control (SOC) of the EC-1 enter
digit '3<RETURN>' and proceed to step 13.
To abort the script enter digit '4<RETURN>'. The script will terminate and the
procedure is now at an end.
—continued—

Procedure 16-1
Run the pm_control script (continued)
Step Action
13 If option 3 was selected, at step 12, the script will warn of any NEs that are
not properly associated with the EC-1, before executing, without further user
intervention, a count of the PMPs in the EC-1 SOC and creating a log file in
the '/tmp' directory. (NB: - on large networks, execution may take some time.)
In the event of any output error messages, contact Nortel Technical support
immediately. In this instance, the procedure is now at an end. Note, the script
will count the total PMPs enabled in the network, NOT necessarily those
PMPs that are collecting on the NEs.
14 If options 1 or 2 were selected, at step 12, to disable or enable PMPs, the
script will list the NEs within the EC-1 SOC. When asked, type in the LAST
SIX digits of the first target NE's MAC address, followed by <RETURN>. (NB:
16
- The script will display the NE; the user should ensure that NO TN-4T NEs
are selected.) The script will then analyze if the selected NE is properly
associated with the EC-1. If it is not in association, the NE will be logged for
attention.
15 If the NE is properly associated with the EC-1, confirm its selection for PMP
updates by typing 'y<RETURN>
16 If another target NE is to be selected for PMP updates, when prompted for
another NE, type 'y<RETURN>' and repeat steps 14 -16. If all target NEs
have been selected for PMP updates, respond to the prompt for another NE
by typing 'n<RETURN>' and proceed to step 17.
17 The script will now list the NEs selected for PMP update. Any NEs that failed
association analysis will be flagged and should be noted by the user. If the list
omits expected target NEs for PMP update, when prompted if you wish to
proceed, answer 'n<RETURN>, before investigating the NE(s) that failed
association analysis. If the list contains the expected target NE(s) for PMP
update answer 'y<RETURN>' and proceed to step 18.
18 The script will now execute and create a log file in the '/tmp' directory. In the
event of any output error messages, contact Nortel Technical support
immediately. The procedure is now at an end.
—end—

PM Collection Enhancement - PM data collection time (24 hours)
Note 1: All NEs in the EC-1 SOC must only have the Nortel
recommended optimal set of PMPs enabled. This procedure must be run
after the pm_control script has been run.
Note 2: The default values in the config.conf are not kept over an EC-1
upgrade
The enhancements to 24 hour PM collection are:

• A new field TOTAL_24H_PM_INTERVAL has been added to the
config.conf file
• This allows the interval used for PM collection to be set.
• The interval starts at midnight and all the 24 hour PMs will be scheduled
for collection within the chosen number of seconds.
• The field defaults to 86400 seconds (24 hours) to be consistent with the
existing mechanism.
• If the value of TOTAL_24H_PM_INTERVAL is changed then the EC-1
must be re-started for the change to take effect. ( killsdhms/runsdhms is
sufficient it does not need a reboot).
The PM reports are sent to the EC-1 as CLUI response lines. As they do not
use the file transfer mechanism then theoretically they can overlap. However,
if the chosen interval is too small making the scheduled times too close
together then the performance of the EC-1 may be affected. The minimum
supported collection window is 14400 seconds (4 hours).
The config.conf file can be edited using the following procedure.

Procedure 16-2
Editing the config.conf file
Step Action
1 1 Login as root from the login banner by typing:
root ↵
<password> ↵
2 Open an xterm and change directory to $SDHMS/LIB by typing:
cd $SDHMS/lib ↵
3 To be able to write to the $SDHMS_LIB/config.conf file and view using vi type:
chmod o+w config.conf ↵
vi config.conf ↵
—continued—

Procedure 16-2
Editing the config.conf file (continued)
Step Action
4 The config.conf shows the TOTAL_24H_PM_INTERVAL parameter

ARCHIVE_START_TIME 06:30
ARCHIVE_DURATION 30
TOTAL_24H_PM_INTERVAL 86400
CONFIG_BACK_START_TIME 01:00
CONFIG_BACKUP_DURATION 240
5 The EC-1 should then be restarted.
6 Exit vi by typing:
wq ↵
You can exit without updating the file, for example, if an error has been made,
16
by typing
q! ↵
7 Make the config.conf file read only again by typing:
chmod o-w config.conf ↵
—end—
end of chapter

17-1
Appendix F: EOW script 17-

Introduction
This document is a user guide for the EOW Script. The script has a menu
driven interface, and is designed to work with all OPTera Metro 4100 and
OPTera Metro 4200 Multiservice Platforms that use the Engineering
Order-Wire [EOW].
The script can be configured to build EOW Span of Controls that can then be
populated with OPTera Metro 4000 Network Elements [NEs]. The user can
specify which Pulse Code Modulated [PCM] encoding that the NEs are 17
required to run in i.e. -law or a-law and whether Slot 1 should be added to the
EOW bus to form a conference.
The TN-1X EOW uses a-law PCM encoding whilst the OM4000 EOW uses
-law. If any OM4000 NEs are required to inter-work with TN-1Xs, the PCM
encoding for all OM4000 NEs ,that form a Span of Control with any TN-1Xs,
need to match the TN-1X a-law encoding.
The script can be used to audit NEs and provides the user with an overview
of:
— the Make / Break states of the EOW cards.
— current running PCM encoding on EOW cards.
— any problems with serial numbers or PEC codes on EOW cards.
— the presence of TN-1Xs connected to Slot 1.
— the presence of an UEOS card which terminates the EOW bus.
Another feature of the EOW script is the ability to check and realign the
configuration periodically. This feature is implemented using the UNIX
cronjob facility, which execute automatically at a specified time.

17-2 Appendix F: EOW script
Problem Denifition
Some issues have been identified with the deployment of the EOW and the
stability of the EOW Span of Control. These are detailed below:
— On a warm / cold restart of the master SEMF / NE or SEMF switch /

software download, the PCM encoding defaults to -law. This is not desirable
under conditions that require a-law PCM encoding.
— During a restart of the EOW card buffers on the card may not be flushed
correctly; the serial number and PEC code may become corrupted.
— Introduction of loops, incorrect termination and RS-LOS on slot 1 can

introduce noise into the EOW conference.
Workaround
EOW PCM encoding is configurable and maintained over restarts in the
following software releases:
NE Type Release
OM4100 R4.7 onwards
OM4200 R4.X
PM4150 R7.X
As an interim solution to this issue, the EOW script will maintain the PCM
encoding following a restart.
The EOW script can be configured to remove Slot 1 from the conference.
This is used when no conference is required via Slot 1-1. It also corrects
serial number and PEC code corruptions.
Using the EOW Script

The EOW Script has a menu driven interface. This means that several options
are available to the user of the script at any one time.
The EOW Script Flowchart is a conceptual view of how the user arrives at
decisions to carry out the different procedures. A key aspect of the script is
that the user first defines a Span of Control for the EOW [Procedure 17-3].
The user should view an EOW Span of Control as a collection of NEs that the
user wishes to form an EOW communication link between.

Figure 17-1
EOW script flowchart
E O W S c r ip t F lo w c h a r t
I s t h e E O W s c r ip t
r u n n in g ? NO
YES
[S p a n o f C o n tr o l] C a rry o u t P ro c e d u re 1 9 -1 :
! A n E O W S p a n o f C o n t r o l is a c o lle c t io n o f
N E s t h a t t h e u s e r w is h e s t o f o r m a n E O W
R u n n in g t h e E O W s c r ip t .
c o m m u n ic a t io n lin k b e t w e e n .
H a s a n E O W S p a n o f C o n tro l
NO YES
b e e n d e f in e d ?
D o y o u w is h t o a d d N E s
C a rry o u t P ro c e d u re 1 9 -3 : t o t h e S p a n o f C o n t r o l? YES C a rry o u t P ro c e d u re 1 9 -4 :
D e f in in g a n E O W S p a n o f C o n t r o l. A d d in g N E s t o a S p a n o f C o n t r o l.
D o y o u w is h t o r e m o v e
NO
17
N E s fro m th e E O W D o y o u w is h t o a u d it
NO YES
S p a n o f C o n t r o l? th e E O W S p a n o f
YES
C o n t r o l?
C a rry o u t P ro c e d u re 1 9 -1 1 :
C a rry o u t P ro c e d u re 1 9 -5 : NO A u d it in g t h e N E s in a c t iv e
D e le t in g a n N E f r o m t h e E O W S p a n o f C o n t r o l. S p a n o f C o n t r o l.
D o y o u w is h t o f ix t h e
YES E O W S p a n o f C o n t r o l?
NO
F ix in g t h e N E s in a c t iv e S p a n o f C o n t r o l.
D o y o u w is h t o d is p la y
YES d e t a ils o f N E s in a c t iv e
S p a n o f C o n t r o l?
D is p la y in g d e t a ils o f N E s in
a c t iv e S p a n o f C o n t r o l. NO
NO D o y o u w a n t t o d e le t e
an EO W Span of
C o n t r o l?
D o y o u w is h t o c h a n g e t h e YES
s a m p lin g la w o f a n E O W S p a n
YES o f C o n t r o l?
C a rry o u t P ro c e d u re 1 9 -7 :
NO
C a rry o u t P ro c e d u re 1 9 -8 : D e le t in g a n E O W S p a n o f C o n t r o l.
C h a n g in g t h e s a m p lin g la w o f a n
E O W S p a n o f C o n t r o l.
D o y o u w is h t o lis t s a v e d E O W YES
NO S p a n o f C o n t r o ls ?
YES D o y o u w is h t o e x it t h e s c r ip t ? L is t in g s a v e d E O W S p a n o f C o n t r o l.
NO
E x it in g t h e E O W s c r ip t .
F lo w C h a r t is c o m p le t e s t a r t a t t o p o f p r o c e d u r e .

Procedure 17-1
Running the EOW script
Step Action
1 Login to the EC-1 as sdhmsusr.

2 Check for the existence of the EOW script.
cd /home/sdhmsusr/patches/16XE/ eow ↵
eow_fix ↵
Note: If the EOW script has not been run before, it automatically produces
two files: current.ne.file and .nelistfile.default.
3 With an instance of the EOW script running, the user should be displayed with
the main menu. More options will be available if a Span of Control has been
entered:
OM4000 EOW network script Version 2.0
=====================================
(1) Add NE to active EOW network
(2) Change to or create new active span list
(3) List saved span lists
(4) Delete a span
(x) Exit
Span of control for default = 0

Select option ->
Note: Only one instant ot the EOW script can be running at any time. If the
EOW script is already being run an error message is displayed:
Detected lock file /tmp/.EOW.script.lockfile
Warning - Script already running already
The running EOW script can be exited using Procedure 17-2.
4 The user can define an EOW Span of Control by carrying out Procedure 17-3.
Note: A Span of Control must be defined before any auditing or fixing of NEs
takes place.
—end—

Procedure 17-2
Exiting the EOW script
Step Action
1 Make sure an instance of the EOW script is running. If not follow Procedure
17-1. The user will be displayed with a menu similar to the one below:
=====================================
(4) Delete a span
(x) Exit
2
Select option ->
At the ‘Select option ->’ prompt the user should type:
17
X or x ↵
3 The EOW script responds by displaying the following to screen:
User selected exit.
4 The script has noe exited.
—end—

Procedure 17-3
Defining an EOW span of control
Step Action
1 Make sure an instance of the EOW script is running and all users are logged
out of the target NEs. If not follow Procedure 17-1.
The user will be displayed with a menu similar to the one below:
=====================================
(4) Delete a span
(x) Exit

Select option ->
2 At the ‘Select option ->’ prompt the user should type:
2↵
3 The EOW script responds by displaying the following to screen:
Existing list of Span files
===========================
default
Select existing span file or enter a new filename
4 The user should enter a descriptive name of the EOW Span of Control. e.g.
Ring_1_Top_to_Bottom ↵
Note: The script will not accept non-alpha numeric characters and will display
the following error message:
Select existing span file or enter a new filename Ring_1-1
Invalid character detected in file name!
Letters, numbers and _ are all valid
Only alpha numeric and _ characters are valid.
—continued—

Procedure 17-3
Defining an EOW span of control (continued)
Step Action
5 The main menu will change to indicate that a new Span of Control is being
used:
=====================================
(4) Delete a span
(x) Exit
Span of control for Ring_1_Top_to_bottom = 0
6
Select option ->
The span of control can now be populated by carrying out Procedure 17-4.
17
—end—

Procedure 17-4
Adding NEs to a span of control
Step Action
out of the target NEs. If not follow Procedure 17-1. If a Span of Control has
not be defined carry out Procedure 17-3.
2 The user should make sure that the appropriate Span of Control is selected.
If not then follow Procedure 17-6.
1↵
The following screen will be displayed:
Adding NE to script span of control
===================================
Enter OM4000 NE address (00007570xxxx) : 00007570
The user should enter the last 4 hexadecimal characters for the MAC
address.
4 The sampling law and Slot 1 conference state then needs to be selected:
Adding NE to script span of control
===================================
Setting NE Address 000075700040
Checking NE .........OK!
Please select the LAW for this span (U/A)? A
Do you wish to turn off Slot 1 for this NE? (y/n)? N
Note 1: Once the sampling law is entered it is set for the entire Span of
Control.
Note 1: The user can change the sampling law for the Span of Control by
following Procedure 17-8.
Note 2: If the NE is not under EC-1 control or the EC-1 is not running, an error
message is displayed
Checking NE .........FAILED!
NE not under EC-1 control or EC-1 not running.
Press RETURN to continue.
Note 3: If the user wishes to change the Slot 1 status for an NE, the NE
should be deleted from the EOW Span of Control by carrying out Procedure
17-5 and then re-added using Procedure 17-4 Step 3.
—continued—

Procedure 17-4
Adding NEs to a span of control (continued)
Step Action
5 The process of adding NEs should continue until the Span of Control is
completed. New menu options will appear when the first NE is added to the
Span of Control:
=====================================
(4) Delete a span
(5) Delete NE from active EOW span
17
6) Display active EOW span of control
(7) Fix active EOW network and quit script
(8) Audit active EOW network and quit script
(9) Change active span LAW

(x) Exit
Span of control for Ring_1_Top_to_Bottom = 4

Select option ->
—end—

Procedure 17-5
Deleting an NE from the EOW span of control
Step Action
2 The user should make sure that the appropriate Span of Control is selected.
5↵
The script will respond with the following:
Deleting NE from script span of control
=======================================
3 The user should enter the last 4 hexadecimal characters for the MAC address
and press <return>. The following will be displayed:
NE 000075700040 deleted.
Entering an invalid MAC address with display the following
ERROR - NE 000075701234 not found in EOW span of control.

4 The process of deleting further NEs can continueg by repeating this
procedure.
—end—

Procedure 17-6
Selecting an EOW span of control
Step Action
2↵
===========================
Ring_1_Top_to_Bottom
default
3
Select existing span file or enter a new filename
Enter name of the EOW Span of Control. e.g.
17
4 The Span of Control will now be available for editing.
—end—
Procedure 17-7
Deleting an EOW span of control
Step Action
2 The user should make sure that the appropriate Span of control is selected.

4↵
===========================
default
Select span file for deletion.
—continued—

Procedure 17-7
Deleting an EOW span of control (continued)
Step Action
3 Enter name of the EOW Span of Control. e.g.

Note: If the user attempts to delete an active span the following error
message is displayed.
Select span file for deletion. Ring_1_Top_to_Bottom
Cannot delete active span!
4 If the user wishes to delete an active Span of Control then they should first
change to another Span of Control following Procedure 17-6. e.g. Change to
the default Span of Control first.
5 The user can then delete the Span of Control as follows.
===========================
default
Select span file for deletion. Ring_1_Top_to_Bottom
Delete span Ring_1_Top_to_Bottom, are you sure? (y/n)
The user can then either enter:
Y or y ↵
To delete the Span of Control - the script responds with
Deleted!
N or n ↵
To stop the Span of Control deletion process. This return you to the main
menu.
Note: If any other character is entered the script responds with:
Yes or No response required
Note: If the user tries to delete the default Span of Control an error message
is displayed
Warning, default span will be not be deleted only emptied!
Delete span default, are you sure? (y/n
Note: If the Span of Control does not exist an error message is displayed.
not exist
—end—

Procedure 17-8
Changing the sampling law of an EOW span of control
Step Action

9↵
Please select the LAW for this span (U/A)?
Note: If the user enters an invalid response the following error message is
displayed.
3
U or A response required!
The user should enter the sampling law required for the EOW Span of
17
Control. e.g
u↵
Changing Span LAW to U ......
or
Changing Span LAW to A ......
…depending on the selected sampling law.
—end—

Procedure 17-9
Listing saved EOW span of controls
Step Action
out of the target NEs. If not follow Procedure 17-1.
3↵
The script will respond with the existing list of EOW span of controls e.g.
===========================
default
Press return to continue.

3 The user should enter ↵ to go back to the main menu.
—end—

Procedure 17-10
Displaying details of NEs in active span of control
Step Action
6↵
The script will respond with the list of NEs under the EOW span of control e.g
If the script has not performed an audit the following will be displayed:
EOW OM4000 script span of control
=================================
Address Law SEMF EOW PEC code Serial Number 1X Status EOS S1
------------ ----- ---- --- -------- ------------- --- --------- --- ----
000075700040 OFF
17
000075701f68 ON
00007570004A ON
000075700048 OFF
Span Ring_1_Top_to_Bottom law = A
The user can carry out an audit br performing Procedure 17-11
If the script has performed an audit the following will be displayed:
=================================
------------ ----- ---- --- -------- ------------- --- --------- --- ----
000075700040 U[09] S6 S10 NTEU43AA NNTM510E4401 NO Make[79] 1 OFF
000075701F68 A[0a] S6 S10 NTEU43AA NNTM510E444E NO Break[59] 1 ON
000075700048 A[0a] S6 S10 NTEU43AA NNTM510E4419 NO Make[79] 1 OFF
00007570004A U[09] S6 S10 NTEU43AA NNTM510E444C YES Make[79] 1 ON

Figure 19-1 shows a description of the data contained in this view. Figure
19-2 shows a example of what is displayed when the script displays a
problem.
3 The user should press ↵ to go back to the main menu.
—continued—

Procedure 17-10
Displaying details of NEs in active span of control (continued)
Step Action
Figure 19-1
Make / Break position
Make – Slot 6 in-conference
Break – Slot 6 removed from conference
Master SEMF Bracketed value indicates raw information from back-door
UEOS detected
MAC address of NEs
------------ ----- ---- --- -------- ------------- --- --------- --- ----
000075700040 U[09] S6 S10 NTEU43AA NNTM510E4401 NO Make[79] 1 OFF
000075701F68 A[0a] S6 S10 NTEU43AA NNTM510E444E NO Break[59] 1 ON
000075700048 A[0a] S6 S10 NTEU43AA NNTM510E4419 NO Make[79] 1 OFF
Indicates sampling law.

U – µ-law EOW Slot position
A – a-law
Bracketed value indicates raw information from back-door
—end—

Procedure 17-11
Auditing the NEs in active span of control
Step Action

8↵
The script will attempt to connect and audit all NEs under the EOW span of
control. The following is displayed:
EOW OM4000 Audit
================
Warning -- OCSMAIN session(s) active = 4
Checking if Manager is running.... OK!
17
Creating a List of NEs... Done!
Checking NE(s) for Association.... Done!
Wed May 7 15:18:59 Sending Script to 000075700040

Processing span Ring_1_Top_to_Bottom
Checking NE RACK4_2
Requesting inventory information ....OK!

Requesting Master SEMF...............OK!
Requesting DCN information ..........OK!
MON CARD Connection to SLOT S6 ......OK!
Requesting sampling law .............OK!
Requesting make break position ......OK!
Logging out of NE ...................OK!
Note: If the script can't connect to one of the NEs the following error message
is displayed
Wed May 7 15:20:06 Sending Script to 000075701F68 * Error
connecting to NE *
Note: If no EOW cards are present in the NE the following error message is
displayed
No EOW cards detected for this NE 0000757035C9
Warning - Script not completed successfully
—continued—

Procedure 17-11
Auditing the NEs in active span of control (continued)
Step Action
3 Once the script completes the EOW script is automatically exited. The script
will respond with the following completion message:
Script EOW completed successfully - Wed May 7 16:34:42
BST 2003
4 The results of the audit can be viewed by first carrying out Procedure 17-1 to
run the EOW script and then carry out Procedure 17-10 to view the audited
results.
—end—
Procedure 17-12
Fixing the NEs in active span of control
Step Action
Before running the EOW fix the user should identify if any problems exist on
the OM4000 NEs. An audit should be carried out first following Procedure
17-11.
Figure 19-2 shows a description of the data contained in this view.
Figure 19-2
EOW OM4000 audit showing aproblem
=================================
------------ ----- ---- --- -------- ------------- --- --------- --- ----
000075701F68 U[09] S6 S10 UNKOWN NNTM510E444E NO Break[59] 1 ON
000075700040 U[09] S6 S10 UNKOWN NNTM510E4401 NO Make[79] 1 OFF
000075700048 A[0a] S6 S10 NTEU43AA UNKOWN NO Make[79] 1 OFF
Three NEs are not operating in

the selected sampling law for
the EOW span of control UNKOWN indicates that the
inventory is corrupted and
the EOW card needs to be restarted


8↵
The script will attempt to connect and fix all NEs under the EOW Span of
Control
During the EOW fix the script will change sampling laws if appropriate e.g.
Changing sampling to A law...........OK!
Changing sampling to U law...........OK!
Law change not required .............OK!
…switch Slot 1 conference ON or OFF e.g.
Changing Slot One mode to OFF........OK!
Changing Slot One mode to ON ........OK!
…restart the EOW card e.g.
Reseting inventory ..................OK!
Set status manager poll .............OK!
17
BST 2003
The script automatically updates the values contained in the EOW Span of
Control. The results of this can be viewed by first carrying out Procedure 17-1
to run the EOW script and then carry out Procedure 17-10 to view the audited
results.
—end—

Note: To run this following procedure a span of control must be defined.

If a span of control has not beed defined carry out Procedure 17-3
Procedure 17-13
Auditing and fixing span of controls using flags
Step Action

In the UNIX window type
cd /home/sdhmsusr/patches/16XE/eow ↵
eow_fix -h ↵
The script will respond with the follow:
USAGE : eow_fix [-audit|-fix] [<Span file name>]
The EOW script is designed to accept a Span file name and two flags:
-audit [Which carries out Procedure 17-10]
-fix [Which carries out Procedure 17-11]
eow_fix -audit Ring_1_Top_to_Bottom ↵
OR
eow_fix -fix Ring_1_Top_to_Bottom ↵
The script will audit or fix the NEs contained within the
Ring_1_Top_to_Bottom file.
Note: If the user enters a Span of Control that does not exist or is empty the
following is displayed e.g. File name ABCDEFG does not exist.
/home/sdhmsusr/patches/16XE/eow/.nelistfile.ABCDEFG does
not exist or contains no OM4000 elements
USAGE : eow_fix [-audit|-fix] [<Span file name>]
Note: If no Span file name is specified the script will run the Span of Control
that was last run. This file is derived from information contained in the hidden
file:
.current.ne.file
Performing the following command will indicate what Span file name will be
used:
cat .current.ne.file ↵
/home/sdhmsusr/patches/16XE/eow/.nelistfile.Ring_1_Top_to_Bottom
BST 2003
4 Both flags automatically update the values contained in the EOW Span of
Control. The results of this can be viewed by first carrying out Procedure 17-1
to run the EOW script and then carry out Procedure 17-10 to view the audited
results.
—end—

Note: To run this following procedure a span of control must be defined.

If a span of control has not beed defined carry out Procedure 17-3
Procedure 17-14
Auditing and fixinf span of controls using cronjobs
Step Action

In the UNIX window type:
crontab -l ↵
This UNIX command lists the information contained in the crontab file. A
crontab file is a list of commands, one per line, which will execute
automatically at a given time.
Numbers are supplied before each command to specify the execution time.
The numbers appear in five fields, as follows:
Minute 0-59
Hour 0-23 17
Day of the month 1-31
Month 1-12
Day of the week 0-6, with 0 = Sunday
2 If the crontab does not exist, one can be created by typing the following
command:
crontab -e ↵
This command also puts the user into "edit mode", which is effectively vi
editor mode. Commands can be inputted using vi syntax.
The following crontab will run an audit on the .current.ne.file at 10:08 every
day and will produce a file called eow_audit.log which contains the progress
08 10 * * * cd /home/sdhmsusr/patches/16XE/eow ; touch eow_audit.log ; ./eow_fix -audit
>> eow_audit.log
The user can specify an exact Span of Control they wish the audit to be
performed on by using the following crontab
14 10 * * * cd /home/sdhmsusr/patches/16XE/eow ; touch eow_audit.log ; ./eow_fix -audit
ABC >> eow_audit.log
This crontab will run an audit on the Span of Control ABC at 10:14 every day
and will produce a file called eow_audit.log which contains the progress of the
audit run in the crontab. The format of audits is detailed in Procedure 17-13
—continued—

Procedure 17-14
Auditing and fixinf span of controls using cronjobs (continued)
Step Action
3 The user can also specify the - fix flag. The format of fixes is detailed in
Procedure 17-13. The crontab is edited as indicated in Procedure 17-14 Step
2. e.g. the crontab for a fix could follow the following format:
00 03 * * * cd /home/sdhmsusr/patches/16XE/eow ; touch eow_fix.log ; ./eow_fix -fix
ABC >> eow_fix.log
This crontab will run a fix on the Span of Control ABC at 03:00 every day and
will produce a file called eow_fix.log which contains the progress of the fix run
in the crontab.
Note: When running multiple cronjobs, make sure enough time is available
for the script to complete the first cronjob before moving onto the next
cronjob.
—end—

18-1
Appendix G: LAN swap script 18-

Introduction
Note: The LAN swap script is ONLY required for HP workstations with
TWO LAN cards
After a HP-UX Migration from 10.20 to 11.11, it has been identified on some
occasions that LAN 0 and LAN1 become swapped i.e. what was LAN 0 at
HP-UX 10.20 is now LAN1 at HP-UX 11. There are two solutions to resolve
this issue :-
1. Physically swap the LAN cables at the back of the HP workstation OR
2. Run the LAN swap script, which swaps LAN 0 & 1 in software.
Note 1: Before switching the LAN cards, the script will try to detect the 18
presence of OSI devices on LAN 0, if detected the script will prompt the
user to confirm that they really want to swap LAN ports, otherwise if no
OSI devices are detected on LAN 0, no prompt will be given and the
script will swap the LANs automatically.
Note 2: If a subsequence rebuild of the HP workstation is required, this
lan swap script may be required to be run, in order to the swap the LAN
ports.

18-2 Appendix G: LAN swap script
Procedure 18-1
LAN swap script
Step Action
1 Log into the HP-UX workstation as root.

2 Enter the following:
cd/home/sdhmsusr/sdhms/bin
3 Run, ./lan_swap.
After a few seconds the scripts will respond with
Done!
Workstation will REBOOT in 10 seconds (CTRL-C to

interrupt)
4 The workstation will reboot and the LAN ports will now be swapped
—end—

19-1
AppendixH:Send_neUserInstructions19-
Introduction
Send_ne is a utility that resides on the Optical Network Manager EC-1 and
enables you to get information on the Optical Network Manager EC-1
database and to directly communicate with network elements under the span
of control (SOC) of the Optical Network Manager EC-1. Send_ne resides on
the Optical Network Manager EC-1 in the following directory: /home/sdhms/
bin. You do not need to change to the /home/sdhms/bin directory to run
send_ne, it can be run from anywhere.
To use send_ne open a UNIX window from the Optical Network Manager
EC-1 Main Menu.
The Optical Network Manager EC-1 can autologout therefore you need to
open a new xterm, see Procedure 19-1.
Procedure 19-1
Opening a new xterm
Step Action
19
1 Open a UNIX window from the Optical Network Manager EC-1 main menu
2 Open a new UNIX window . Type:
xterm &
3 Close the System engineer’s UNIX window.
—end—
If connecting from a remote machine “telnet<EC-1IP address>”. When

prompted for a username enter ‘sdhmsusr’ and default password ‘sdhmsusr’.
Send_ne for specific network elements

Send_ne is the main program. There is only one program but six variants
exist:
send_1x
send_1c
send_1p
send_4x (TN_4XE / OPTera Metro 4100/4150 specific)
Optical Network Manager EC-1 Optical Network Manager EC-1 Network Upgrade Procedures
19-2 Appendix H: Send_ne User Instructions
send_4t
send_16x (TN_16XE / OPTera Metro 4200 specific)
Use the above variants to see information and talk to network elements of one
particular product group only. For example, to see information and talk to
TN-1Xs, use the send_1x command. If send_ne is used, the command is
applied to all network elements in the Span of Control (SOC).
To send to one network element only, use the -ne flag followed by the
network element address or the Optical Network Manager NE ID.
Most send_ne commands can be limited to one specific network element by

applying the -ne option. The syntax for this is
send_ne -ne <neid>.
The parameter <neid> that is supplied to the -ne option is one of:
ne_id For example, 1052
MAC address For example, 000075700001
NSAP For example, 490000000075700001
For example, send_ne -ne 1052
Note: If you are using the MAC address, the area address defaults to
490000. Refer to “Appendix C: Manual area addresses” on page 1-1.
To send to more than one network element, create a list of elements into a file
you want to use. See “Send_ne for specific network elements” on page 19-1.
The syntax for this is:
send_ne -n<ne_file>
To ignore a list of network element, create a list of elements into a file you
want to use. See “Send_ne for specific network elements” on page 19-1. The
syntax for this is:
send_ne -i<ignore_nes>

Send_ne options
Send_ne help
Use Procedure 19-2 to get send_ne help.
Procedure 19-2
Getting send_ne help
Step Action
1 Type any of the following to get help on other send_ne options:

send_ne
send_ne -h
send_ne -help
—end—
NE_LISTING
A useful feature of send_ne is the NE_LISTING option, see Procedure 19-3.
Procedure 19-3
Getting a network element listing using send_ne
Step Action
1 Type:
send_ne -l ↵
A file called NE_LISTING is created in the current UNIX directory containing
information about each network element in the Optical Network Manager
EC-1’s Span of Control.
19
—end—

Sending a CLUI file to an NE

Use Procedure 19-4 to send a CLUI file to a network element.
Procedure 19-4
Sending a CLUI file to a network element using send_ne
Step Action
1 Create a file containing the CLUI commands. Ensure that the last command
in the file is the logout command. For example:
~ asv
~ logout
The file name is user-definable.
Note: Always remember to put a ‘~ logout’ at the end of the clui file since
send_ne will hang and eventually timeout reporting an error.
2 Send the file. Type:
send_ne -f <clui_file> ↵
where <clui_file> is the name of the CLUI file.
By default, send_ne sends this file to every network element in the database
that is managed and associated. It sends it to the TN-1X, 1C, 1P, OPTera
Metro 4100, OPTera Metro 4150, 4T, OPTera Metro 4200 network element
types. (use the send_ne ‘-ne’ flag to send a list of network elements OR
send_ne ‘-I’ flag to ignore a list of netowrk elements.
3 By default, send_ne does not store the CLUI responses. To instruct send_ne
to log the information type:
send_ne -f <clui_file> -d <output.log> ↵
A file called <output.log> is generated containing the CLUI output (the
network element response).
send_ne -f <clui_file> -d <output.log>-i <ignore_nes> ↵
(sends to all network elements except those in the <ignore_nes> file).
send_ne -f <filename> -d <output.log>-n <ignore_nes> ↵
(sends to network elements in the <ne_file> file and ignores network
elements in the <ignore_nes> file).
—end—

Connecting to a network element

To log into a network element, first use NE_LISTING to identify the
network element address or NE id, then perform Procedure 19-5.
Procedure 19-5
Connecting to a network element using send_ne
Step Action
1 Type:
send_ne -c <neid> ↵
Where <neid> identifies for example, the neid of a network element you wish
to log into. See “Send_ne for specific network elements” on page 19-1. By
default, send_ne logs in as the config manager.
—end—
19

Software download
ATTENTION
NE software back out
It is NOT possible to back out of a software download using

send_ne. Refer to NTP 323-1123-302, Systen and Data
Administraion procedures, NE software administration.
It is possible to upgrade an entire network using send_ne, user intervention is

NOT required. You cannot directly use send_ne but you can use send_1x,
send_4x, send_4t, send_16x, send_1p and send_1c.
For example:
send_1x -swdl <load_path>
where <load_path> is the path of the location of the load to be downloaded

to the specified network elements. In the case of the previous example
send_1x -swdl NE_load/1X/tn1x772a.b
Other examples :
send_4x -swdl NE_load/4XE/7.00
send_16x -swdl NE_load/16XE/4.10
Send_ne upgrades all the network elements one at a time taking a note of any
software download failures. If any network element failures are detected,
send_ne repeats the software download after a full cycle of the network
element(s) in the Optical Network Manager EC-1 database has completed.
Note 1: You can use the ‘-ne’ flag to download to one network element
OR the ‘-n’ flag OR the ‘-i’ flag to only send to a group of network
elements.
Note 2: After downloading the software it is advisable to run a software
listing and a card view listing to check each network element for its
software status. See “Software listing” on page 19-8 for software listing
option usage, and see “Card view listing” on page 19-9 for card view
listing.

Booting the software on the network

When the software has been downloaded (see “Software download” on page
19-6) send_ne can then boot the software banks, see Procedure 19-6.
Procedure 19-6
Booting the software on the network using send_NE
Step Action
1 Type:
send_ne -swboot ↵
Note: Use the ‘-ne’ flag to send to individual network element OR the ‘-n’ flag
to send to a list of network elements OR the ‘-i’ flag to only ignore a list of
network elements.
Note: After booting the software, it is advisable to run a software listing and
a card view listing to ensure all banks have booted. See “Software listing” on
page 19-8 for software listing option usage and and see “Card view listing” on
page 19-9 for card view listing.
—end—
19

Committing the software
When the software banks are booted (see “Booting the software on the
network” on page 19-7) the software must be committed, see Procedure 19-7.
Procedure 19-7
Committing the software using send_ne
Step Action
1 Type:
send_ne -swcommit ↵
network elements.
Note: After committing the software, it is advisable to run a software listing
and a card view listing to ensure all banks have committed. See “Software
listing” on page 19-8 for software listing option usage and see “Card view
listing” on page 19-9 for card view listing.
—end—
Software listing
To view the software status of network elements (and produce a file called
SW_LISTING), use the software listing option, see Procedure 19-8.
Procedure 19-8
Listing software on network elements using send_ne
Step Action
1 Type:
send_ne -swlisting ↵
network elements.
—end—
Card view listing

On the OPTera Metro 4100, OPTera Metro 4150, TN-4T and OPTera Metro
4200 network elements, software is also held by individual tributary cards.
Use the card view option to create a file called CV_LISTING, see Procedure
19-9.
Procedure 19-9
Card view listing using send_ne
Step Action
1 Type:
send_ne -cv ↵
This command produces a file called CV_LISTING containing the individual
card status for OPTera Metro 4100, OPTera Metro 4150, TN-4T and OPTera
Metro 4200 network element types.
network elements.
—end—
NE Backups
Send_ne can be used to perform NE backups. Send_ne performs the same
type of backup as the automatic EC-1 backup, see Procedure 19-10.
Procedure 19-10
Network element backups using send_ne
Step Action
19
1 Type:
send_ne -backup ↵
This command produces a backup of all the network elements under the
Optical Network Manager EC-1 SOC.
network elements.
—end—

Restoring NE backups
ATTENTION
NE configuration back out
It is NOT possible to back out of a configuration download

using send_ne. Refer to NTP 323-1123-302, Systen and Data
Administraion procedures, NE software administration.
Send_ne can be used to restore NE backups. Send_ne looks for the automatic
backup file on the EC-1 for the specific NE and restores it, see Procedure
19-11.
Procedure 19-11
Network element restore using send_ne
Step Action
1 Type:
send_ne -restore ↵ (restores all NEs on the EC-1)
send_1x -restore ↵ (restore only 1X NEs)
send_ne -restore -ne 5123↵ (restoreto one NE)
send_ne -restore -n a_file ↵ (restorea group of NEs specified in ,A_file>)
Send_ne reports restore success of failures.
network elements.
—end—
Sync Report
You can get a sync report for the network managed by the Optical Network
Manager EC-1, see Procedure 19-12. A file called QL_LISTING is created.
Procedure 19-12
Getting a sync report using send_ne
Step Action
1 Type:
send_ne -ql ↵
A SYNC report of the Optical Network Manager EC-1 network is generated.
Note: You can use the ‘-ne’ flag to download to one network element OR the
‘-n’ flag OR the ‘-i’ flag to only send to a group of network elements.
—end—

DCN information
Send_ne can also get DCN information from a TN-1X, OPTera Metro 4100,
OPTera Metro 4150, TN-4T or OPTera Metro 4200 network element type, see
Procedure 19-13. Send_ne analyses the DCN data from the network element
and compares it with data in the Optical Network Manager EC-1 database.
Procedure 19-13
Getting DCN information using send_ne
Step Action
1 The -dcn flag requires the -ne flag. Type:

send_ne -dcn -ne <neid> ↵
where <neid> identifies the network element you want the DCN data from.
Refer to “Send_ne for specific network elements” on page 19-1.
—end—
end of chapter
19

20-1
Index 20-
A handbooks 1-xx
abbreviations, list of 1-xxii
associated documents 1-xvi N
NE Upgrade
C activate downloaded NE image 5-18
alarm clearance 11-1
connecting
HP B180L 14-49 backing out
HP B2600 14-50 after software activation 6-3
HP C3600 14-50 before software activation 6-2
connections comms failure
HP workstation 14-50 checking gateway NEs 11-3
checking gateway routing tables 11-5
checking transport layer 11-4
D storing data logs 11-6
DAT tape drivers 14-131 delete NE software from Optical Network
DCN guidelines 15-1 Manager AP 5-14
DDS1 tape drivers 14-131 download NE image 5-16
DDS2 tape drivers 14-131 flowchart 5-3
DDS3 tape drivers 14-131 loading NE software
from DAT on EC-1 5-6
E from DAT onto Optical Network
EOW script 17-1, 18-1 Manager AP 5-7 20
loading software 5-6
H no response from network host 11-2
handbooks overview 5-1
DCN 1-xix path protection switch 5-17
Hewlett-Packard 1-xx post-upgrade options 5-20
INM4.0 1-xix preparation 5-3
OPTera Metro 4100 1-xvii schedule delivery 5-11
OPTera Metro 4200 1-xvii
Optical Network Manager Application O
Platform 1-xix OPTera Metro 4100
Optical Network Manager EC-1 1-xvi handbooks 1-xvii
TN-1C 1-xviii OPTera Metro 4200
TN-1P 1-xviii handbooks 1-xvii
TN-1X 1-xviii Optical Network Manager Application
TN4-T 1-xviii Platform 3-1
Web access 1-xvi delete unwanted EC-1 software 4-26
Hewlett-Packard handbooks 1-xix

20-2 Index
historical names 1-xvi backups 3-7

Optical Network Manager EC-1 check HP-UX patches 3-9
background information 1-1 creating disk space 3-17
handbooks 1-xvi flowchart 3-3
hardware requirements load software from CD-ROM 3-20
EC-1 platform 1-5 overview 3-1
network elements 1-6 post-upgrade options 3-29
management platforms 1-3 preparation 3-4
recovery from DAT 12-1 remove redundant EC-1 image 3-16
software requirements remove redundant NE image 3-14
EC-1 platform 1-7 size of /home partition 3-9
network elements 1-7 incorrect file permissions 10-1, 10-10
supported NE types 1-2 incorrect release number 10-12
supported upgrade paths 1-2 invalid grade user 10-2
upgrade invalid user 10-10
backout procedure 8-1 locally
commitment 9-1 backups 2-6
from CD-ROM 3-1 check HP-UX patches 2-7
overview 1-8 creating disk space 2-15
philosophy 1-8 flowchart 2-3
post upgrade options 2-27 load software from CD-ROM 2-18
preparation 1-12 overview 2-1
solve problems 10-1 post-upgrade options 2-27
troubleshooting 1-10 preparation 2-4
using ESWD 4-1 remove redundant EC-1 image 2-12
remove redundant NE image 2-12
P setting file permissions 2-19
PM engineering guidelines 16-1 size of /home partition 2-7
missing release note 10-12
missing release note file 10-5
R original upgrade directory does not
Refer to (‘Appendix I exist 10-11
Send_ne User Instructions’) 7-1 recovery from DAT 12-1
release note problems 10-4, 10-11
T shutting down
technical support current software release 10-8
Nortel Networks 1-xxiv new software release 10-15
solving problems 10-1
U starting the original release 10-16
Upgrade EC-1 starting the software 10-9
alarms present 10-6, 10-14 switching EC-1 software 10-9, 10-16
backing out 8-1 upgrade directory cannot be removed 10-3
commit procedure 9-1 upgrade directory problems 10-3
communications check 10-7, 10-15 using ESWD
configuration file does not exist 10-11 backups 4-7
EC-1 not running 10-6, 10-14 creating disk space 4-17
environment and configuration 10-5, delete EC-1 software from Optical
10-13 Network Manager AP 4-26
failing to upgrade to latest release 10-8 extract software from digital audio
from Optical Network Manager AP tape 4-20

Index 20-3
flowchart 4-3
overview 4-1
post-upgrade options 4-35
preparation 4-4
remove redundant EC-1 image 4-15
remove redundant NE image 4-14
schedule delivery 4-23
size of /home partition 4-9
Upgrade EC-1 incorrect command line
arguments 10-2
20

So far as Nortel Networks is aware the contents of this document
are correct. However, such contents have been obtained from a
variety of sources and Nortel Networks can give no warranty or
undertaking and make no representation as to their accuracy. In
particular, Nortel Networks hereby expressly excludes liability for
any form of consequential, indirect or special loss, and loss of
data, loss of profits or loss of business opportunity, howsoever
arising and whether sustained by the user of the information
herein or any third party arising out of the contents of this
document.
*NORTEL NETWORKS, the Nortel Networks logo, the
Globemark and Unified Networks are trademarks of Nortel
Networks.
SDH TRANSMISSION
Optical Network Manager

EC-1
Copyright © 2005 Nortel Networks, All Rights Reserved.
The copyright of this document is the property of Nortel Networks.

Without the written consent of Nortel Networks, given by contract
or otherwise, this document must not be copied, reprinted or
reproduced in any material form, either wholly or in part, and the
contents of this document, or any methods or techniques
available therefrom, must not be disclosed to any other person
whatsoever.
NORTEL NETWORKS CONFIDENTIAL: The information
contained herein is the property of Nortel Networks and is strictly
confidential. Except as expressly authorized in writing by Nortel
Networks, the holder shall keep all information contained herein
confidential, shall disclose it only to its employees with a need to
know, and shall protect it, in whole or in part, from disclosure and
dissemination to third parties with the same degree of care it uses
to protect its own confidential information, but with no less than
reasonable care. Except as expressly authorized in writing by
Nortel Networks, the holder is granted no rights to use the
information contained herein.
Document Number: 323-1091-230
Product Release Number: Release 19.1
Document Status: Standard
Date: May 2007
Printed in England

Optical Network Manager EC-1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Optical Network Manager EC-1

Uploaded by

Copyright:

Available Formats

323-1091-230

Document Number: 323-1091-230

Copyright © 2005 Nortel Networks, All Rights Reserved.

Optical Network Manager EC-1 Network Upgrade Procedures

CDE,HP,HP-VUE,HP-UX are trademarks of the Hewlett-Packard Company

323-1091-230 Release 19.1 Standard

Optical Network Manager EC-1 Network Upgrade Procedures

323-1091-230 Release 19.1 Standard

Upgrading EC-1 locally (via CD-ROM) 2-1

Upgrading EC-1 from the Optical Network Manager Application

Optical Network Manager EC-1 Network Upgrade Procedures

Backing up the EC-1 platform prior to upgrade 3-7

Upgrading EC-1 from the Optical Network Manager platform

Upgrading NE software 5-1

Backing out of an NE upgrade 6-1

Committing to an NE upgrade 7-1

Backing out of an EC-1 upgrade 8-1

Committing to an EC-1 upgrade 9-1

The commit procedure 9-1

Solving EC-1 upgrade problems 10-1

Solving NE upgrade problems 11-1

Appendix A: EC-1 recovery from DAT 12-1

Appendix B: osi_comms.conf file 13-1

Optical Network Manager EC-1 Network Upgrade Procedures

Appendix C: Migration of HP-UX 10.20 to HP-UX 11i 14-1

323-1091-230 Release 19.1 Standard

Restoring EC-1 archives on secondary EC-1s 14-127

Appendix D: DCN Guidelines 15-1

Appendix F: EOW script 17-1

Appendix G: LAN swap script 18-1

Appendix H: Send_ne User Instructions 19-1

Optical Network Manager EC-1 Network Upgrade Procedures

Figure 1-2 Management platform (no Optical Network Manager Application

323-1091-230 Release 19.1 Standard

Optical Network Manager EC-1 Network Upgrade Procedures

323-1091-230 Release 19.1 Standard

Optical Network Manager EC-1 Network Upgrade Procedures

About this document

• locally from the Optical Network Manager EC-1 platform, through

This document also describes multiplexer software (network element)

Optical Network Manager EC-1 Network Upgrade Procedures

Some customers have special upgrade requirements which are relevant to

Optical Network Manager Application Platform

and entering your user name and password when required.

Optical Network Manager EC-1 Releases

323-1091-230 Release 19.1 Standard

OPTera Metro 4200 (Release 1, 2, 3.x, 4.x, 5 and 6).

Note: Previous to Release 2 the OPTera Metro 4200 was known as

Optical Network Manager EC-1 Network Upgrade Procedures

• Nortel OPTera Metro 4150 Alarm Clearing Procedures

TN-4T (Release 1 and 2)

TN-1X Release 8.x onwards

TN-1C Release 3 onwards

TN-1P Release 2 and Release 5.0

323-1091-230 Release 19.1 Standard

INM Release 4.0

Optical Network Manager Application Platform Release 5.0 onwards

Note: Optical Network Manager Application Platform superseded INM

Data Communications Networks

Optical Network Manager EC-1 Network Upgrade Procedures

Using this document

323-1091-230 Release 19.1 Standard

• Appendix C: Preventing a Sync problem caused by End Of Shelf card