Accesswave Series Upgrade Guide 7.1x or 7.2.1 to 7.3.1 a00 En

AccessWave Series

Upgrade Guide

From V7.1.x or 7.2.1 to 7.3.1

Release 01

417006-2305-0H3-A04

AccessWave Series Upgrade Guide from V7.1.x or 7.2.1 to V7.31 Catalog No: X38138 Release 01, April 2010 © Copyright by ECI Telecom, 2010. All rights reserved worldwide.

This is a legal agreement between you, the end user, and ECI Telecom Ltd. (“ECI Telecom”). BY OPENING THE DOCUMENTATION AND/OR DISK PACKAGE, YOU ARE AGREEING TO BE BOUND BY THE TERMS OF THIS AGREEMENT. IF YOU DO NOT AGREE TO THE TERMS OF THIS AGREEMENT, PROMPTLY RETURN THE UNOPENED DOCUMENTATION AND/OR DISK PACKAGE AND THE ACCOMPANYING ITEMS (INCLUDING WRITTEN MATERIALS AND BINDERS OR OTHER CONTAINERS), TO THE PLACE FROM WHICH YOU OBTAINED THEM. The information contained in the documentation and/or disk is proprietary and is subject to all relevant copyright, patent, and other laws protecting intellectual property, as well as any specific agreement protecting ECI Telecom's rights in the aforesaid information. Neither this document nor the information contained in the documentation and/or disk may be published, reproduced, or disclosed to third parties, in whole or in part, without the express prior written permission of ECI Telecom. In addition, any use of this document, the documentation and/or the disk, or the information contained therein for any purposes other than those for which it was disclosed, is strictly forbidden. ECI Telecom reserves the right, without prior notice or liability, to make changes in equipment design or specifications. Information supplied by ECI Telecom is believed to be accurate and reliable. However, no responsibility whatsoever is assumed by ECI Telecom for the use thereof, nor for the rights of third parties, which may be affected in any way by the use and/or dissemination thereof. Any representation(s) in the documentation and/or disk concerning performance of ECI Telecom product(s) are for informational purposes only and are not warranties of product performance or otherwise, either express or implied. ECI Telecom's standard limited warranty, stated in its sales contract or order confirmation form, is the only warranty offered by ECI Telecom. The documentation and/or disk is provided “AS IS” and may contain flaws, omissions, or typesetting errors. No warranty is granted nor liability assumed in relation thereto, unless specifically undertaken in ECI Telecom's sales contract or order confirmation. Information contained in the documentation and in the disk is periodically updated, and changes will be incorporated in subsequent editions. If you have encountered an error, please notify ECI Telecom. All specifications are subject to change without prior notice. The documentation and/or disk and all information contained therein is owned by ECI Telecom and is protected by all relevant copyright, patent, and other applicable laws and international treaty provisions. Therefore, you must treat the information contained in the documentation and disk as any other copyrighted material (for example, a book or musical recording). Other Restrictions. You may not rent, lease, sell, or otherwise dispose of the documentation and disk, as applicable. YOU MAY NOT USE, COPY, MODIFY, OR TRANSFER THE DOCUMENTATION AND/OR DISK OR ANY COPY IN WHOLE OR PART, EXCEPT AS EXPRESSLY PROVIDED IN THIS LICENSE. ALL RIGHTS NOT EXPRESSLY GRANTED ARE RESERVED BY ECI TELECOM. All trademarks mentioned herein are the property of their respective holders. ECI Telecom shall not be liable to you or to any other party for any loss or damage whatsoever or howsoever caused, arising directly or indirectly in connection with this documentation and/or disk, the information contained therein, its use, or otherwise. Notwithstanding the generality of the aforementioned, you expressly waive any claim and/or demand regarding liability for indirect, special, incidental, or consequential loss or damage which may arise in respect of the documentation and/or disk and/or the information contained therein, howsoever caused, even if advised of the possibility of such damages. The end user hereby undertakes and acknowledges that they read the "Before You Start/Safety Guidelines" instructions and that such instructions were understood by them. It is hereby clarified that ECI Telecom shall not be liable to you or to any other party for any loss or damage whatsoever or howsoever caused, arising directly or indirectly in connection with you fulfilling and/or failed to fulfill in whole or in part the "Before You Start/Safety Guidelines" instructions.

Document History The following table records information regarding released editions of this document and briefly describes the changes made to them.

Rev. No. Release Date Responsible Approved by Description of Changes

A00 Yosi Avraham First version

Document Approvals Title Name Signature Date Remarks

ON Technical Presale

Ori Shinberg

Approved 7.4.10

ON Manager Oron Kfir Approved 7.4.10 ON PLM Yosi Avraham Approved 7.4.10

426006-2423-023-A00 ECI Telecom Ltd. Proprietary i

Contents About This Manual ................................................................... vii

Overview ............................................................................................................ vii Intended Audience ............................................................................................. vii Document Organization ...................................................................................... vii Document Conventions ..................................................................................... viii Obtaining Technical Documentation ................................................................... ix Technical Assistance ............................................................................................ x Features of the AccessWave Series ................................................................... xi

AccessWave Series Overview ................................................ 1-1

AccessWave Series Common Equipment ............................................................. 1-1 Shelf and Module Compatibility ............................................................................ 1-2 AccessWave Series Management Interfaces ........................................................ 1-5

Upgrading to Release 7.3.1 ..................................................... 2-1

Upgrade Task Flow ............................................................................................. 2-1 Before you Upgrade to Release 7.3.1 ................................................................... 2-2 Performing Database Backup .............................................................................. 2-3 Setting up the AccessWave Management System .......................................... 2-6 Loading, Invoking, and Committing the System Software Upgrade ............... 2-12 Equipment Installing and Provisioning ........................................................... 2-21 Auto-upgrade Support on Modules ................................................................ 2-21

Returning to an Earlier Version of the System Software ..... 3-1

Cancelling a System Software Upgrade Process using the AccessWave Management System ....................................................................................... 3-1 Cancelling a System Software Upgrade Process using TL1 ............................ 3-3 Downgrading the System Software using the AccessWave Management System ............................................................................................................. 3-5 Downgrading the System Software using TL1 ....................................................... 3-7

Useful Procedures ................................................................... 4-1

Determining System Software Release Numbers ............................................ 4-1 Database Restoring using the AccessWave Management System ................. 4-2 Database Restoring using TL1 ......................................................................... 4-4 Establishing an AccessWave Management System Session using Ethernet ............................................................................................................ 4-8 Establishing a TL1 Session using RS-232 ..................................................... 4-12

Contents AccessWave Series Upgrade Guide from V7.1.x or 7.2.1 to 7.3.1

ii ECI Telecom Ltd. Proprietary 426006-2423-023-A00

Troubleshooting ...................................................................... 5-1

Checking Failures ............................................................................................. 5-1 Loading Failures ............................................................................................... 5-4 Invoking Failure ................................................................................................ 5-7 Committing Failure ........................................................................................... 5-9 Cancelling Failure ............................................................................................. 5-9 Provisioning Failure ........................................................................................ 5-10 Module Upgrade Failure ................................................................................. 5-11 Database Recovery Failure ............................................................................ 5-11

426006-2423-023-A00 ECI Telecom Ltd. Proprietary iii

List of Figures Figure 4-1: Establishing an AccessWave Management System session using Ethernet .......................................................................................................................... 4-9 Figure 4-2: Establishing an AccessWave Management System session using Ethernet .......................................................................................................................... 4-9 Figure 4-3: Establishing a TL1 session using the RS-232 Craft serial port ................. 4-12 Figure 4-4: Establishing a TL1 session using the RS-232 Craft serial port ................. 4-12 Figure 4-5: DB-9 Pin Connector and 8 Pin RJ-45 Connector Numbering Schemes ...................................................................................................................... 4-14

List of Figures AccessWave Series Upgrade Guide from V7.1.x or 7.2.1 to 7.3.1

iv ECI Telecom Ltd. Proprietary 426006-2423-023-A00

426006-2423-023-A00 ECI Telecom Ltd. Proprietary v

List of Tables Table 1-1: Common equipment supported in Release 7.3.1 ......................................... 1-1 Table 1-2: Common equipment...................................................................................... 1-2 Table 1-3: Optical Amplifier modules ............................................................................. 1-2 Table 1-4: Dispersion Compensation modules .............................................................. 1-3 Table 1-5: Optical Multiplexing modules ........................................................................ 1-3 Table 1-6: Transponder modules ................................................................................... 1-4 Table 1-7: Muxponder modules ..................................................................................... 1-5 Table 1-8: Optical Packet Switch modules .................................................................... 1-5 Table 4-1: IP Addresses ................................................................................................. 4-8 Table 4-2: Pin Assignments for RS-232 DB-9 Pin Connectors and RS-232 RJ-45 Connectors ................................................................................................................... 4-15

List of Tables AccessWave Series Upgrade Guide from V7.1.x or 7.2.1 to 7.3.1

vi ECI Telecom Ltd. Proprietary 426006-2423-023-A00

426006-2423-023-A00 ECI Telecom Ltd. Proprietary vii

Overview This preface explains who should read the Upgrade Guide , how the guide is organized, related documentation, documentation conventions, how to obtain documentation, and how to obtain technical support.

Intended Audience This guide is primarily intended for technicians and network operation center (NOC) staff.

Document Organization This manual contains the following information:

Chapter Description

Chapter 1, AccessWave Series Overview

This chapter provides information about the common equipment, modules, and management interfaces supported by AccessWave Series Release 7.3.1.

Chapter 2, Upgrading to Release 7.3.1

This chapter provides information about upgrading the system software from Release 7.2.1 to Release 7.3.1.

Chapter 3, Returning to an Earlier Version of the System Software

This chapter provides information about returning the AccessWave Series to an earlier version of the system software.

Chapter 4, Useful Procedures This chapter provides information about other procedures you can perform when upgrading to Release 7.3.1.

Chapter 5, Troubleshooting This chapter provides information about troubleshooting the issues that might arise when upgrading from Release 7.2.1 to Release 7.3.1.

About This Manual

About This Manual AccessWave Series Upgrade Guide from V7.1.x or 7.2.1 to 7.3.1

viii ECI Telecom Ltd. Proprietary 426006-2423-023-A00

Document Conventions When applicable, this manual uses the following conventions.

Convention Indicates Example

Bold Names of windows, dialog boxes, menus, buttons and most other GUI elements

In the Alarms menu...

Menu > Option Selection from a menu, or leading to another command

Select Update > View Objects

Courier New Font Code syntax and code examples, UNIX commands, user-typed information

>>Starting default primary application, please wait...

Italics New terms and emphasized text

Examples in text

Borders around text Notes, cautions, warnings, laser warnings, EDS warnings, tips, and important notes

See examples below

NOTE: Text set off in this manner presents clarifying information, specific instructions, commentary, sidelights, or interesting points of information.

CAUTION: Text set off in this manner indicates that failure to follow directions could result in damage to equipment or loss of information.

WARNING: Text set off in this manner indicates that failure to follow directions could result in bodily harm or loss of life.

LASER WARNING: Text set off in this manner indicates how to avoid personal injury. All personnel involved in equipment installation, operation, and maintenance must be aware that laser radiation is invisible. Therefore, although protective devices generally prevent direct exposure to the beam, personnel must strictly observe the applicable safety precautions and, in particular, must avoid staring into optical connectors, either directly or using optical instruments.

AccessWave Series Upgrade Guide from V7.1.x or 7.2.1 to 7.3.1

About This Manual

426006-2423-023-A00 ECI Telecom Ltd. Proprietary ix

ESD: Text set off in this manner indicates information on how to avoid discharge of static electricity and subsequent damage to the unit.

TIP: Text set off in this manner includes helpful information and handy hints that can make your task easier..

IMPORTANT: Text set off in this manner presents essential information you must pay attention to.

Obtaining Technical Documentation

To obtain technical documentation related to ECI Telecom products, please contact:

ECI Telecom Ltd. Documentation Department 30 Hasivim St. Petach Tikva 49130 Israel

Fax: +972-3-9268060 Email: [email protected]

mailto:[email protected]�


x ECI Telecom Ltd. Proprietary 426006-2423-023-A00

Technical Assistance The configuration, installation, and operation of ECI Telecom products in a network are highly specialized processes. Due to the different nature of each installation, some planning aspects may not be covered in this manual.

If you have questions or concerns about your network design or if you require installation personnel to perform the actual installation process, ECI Telecom maintains a staff of design engineers and highly trained field service personnel. The services of this group are available to customers at any time.

If you are interested in obtaining design assistance or a network installation plan from ECI Telecom's Customer Support team, contact your ECI Telecom sales representative. With any support related issues, technical or logistic, please contact the ECI Telecom Customer Support center at your location. If you are not familiar with that location, please contact our central customer support center action line at:

Telephone +972-3-9266000

Telefax +972-3-9266370

Email [email protected]


About This Manual

426006-2423-023-A00 ECI Telecom Ltd. Proprietary xi

Features of the AccessWave Series

ECI Telecom AccessWave Series latest release resets the standard for metro service delivery with powerful new modules and tools designed to expand fiber capacity and reduce the complexity of optical-Ethernet engineering. Release 7.3 allows service providers to quickly deliver multi-service optical and packet network services while it delivers better performance for high-capacity enterprise network environments. Enhancements to AccessWave Series and Management System suite enable network planners and administrators to design and add new services and capacity efficiently and easily. Highlights of this release include:

Support for G.8032 ring protection switching on Optical Packet Switch

AccessWave Management System network and nodal management for all AW-60 modules and features

Tunable 10G XFPs—the next generation in Pluggable Optics for flexible wavelength planning

Release 7.3 introduces the following packet-optical enhancements:

Tunable XFPs supporting: 50GHz channel spacing Addresses AccessWave 40-ch wavelength plan at 100GHz Optical specification alignment with fixed 10G DWDM XFPs

Copper SFP support on the GE Muxponder, 10-port Muxponder, 8-port Muxponder

The Optical Packet Switch now supports: Ethernet ring protection switching (G.8032) Improved fault management with IEEE 802.1ag and ITU-T Y.1731 Ethernet service OAM, supporting CCMs, L2 ping and L2 trace-route Management VLAN Ethernet service statistics defined by UNI, C-VLAN and CoS New Ethernet PMs: Bandwidth utilization, Rx octets, Rx violate octets,

Rx conform and exceed octets

10-port Multiprotocol Muxponder now supports: OC-3/12 STM-1/4 Clients Basic SSM Enables provisioning of VCAT and CCAT on a per port basis


xii ECI Telecom Ltd. Proprietary 426006-2423-023-A00

8-port Multiprotocol Muxponder now supports: Basic SSM HD SDI Enables provisioning of VCAT and CCAT on a per port basis

Platform Improvements: BER PM 24 hour PM bins Security enhancements (TL1/SSH, secure FTP, 500 user-ids)

AccessWave Management System fully supports: New 7.3 Optical Packet Switch services New Muxponder module service provisioning Tunable XFPs New alarms and PMs

Release 7.3.1 of AccessWave Management System provides initial support for AccessWave Series NEs running release 7.3 software with the following limitations:

New alarms introduced at release 7.3 are not supported New PM points introduced at release 7.3 are not supported

The following table lists the shelves and other common equipment introduced as part of the AccessWave Series. For detailed information about the AccessWave Series, see the Product Guide and the Common Equipment Installation Guide.

AccessWave Series Common Equipment

Equipment Module Name AccessWave 60 platform AW-60 Shelf

AccessWave 60 platform with rear access -48V AW-60 SHELF REAR -48V

AccessWave 60 platform Cooling Unit (CU) AW-60 COOLING UNIT

AccessWave 60 platform Main Shelf Interface (MSI) AW-60 MSI

AccessWave 60 platform Expansion Shelf Interface (ESI) AW-60 ESI

AccessWave 60 platform System Control Processor (SCP) AW-60 SCP

AccessWave 60 platform AC Power Assembly Kit AW-60 AC PWR ASSY KIT

AccessWave 60 platform AC Power Module AW-60 AC POWER UNIT

AccessWave 30 platform AW-30 SHELF

AccessWave 30 platform Cooling Unit (CU) AW-30 COOLING UNIT

AccessWave 30 platform Main Shelf Interface (MSI) AW-30 MSI


About This Manual

426006-2423-023-A00 ECI Telecom Ltd. Proprietary xiii

Equipment Module Name AccessWave 30 platform System Control Processor (SCP) AW-30 SCP

AccessWave 30 platform AC Power Assembly Kit AW-30 AC PWR ASSY KIT

AccessWave 30 platform AC Power Module AW-30 AC POWER UNIT

AccessWave 20 platform AW-20 PASSIVE SHELF

The following table lists the AccessWave Series modules introduced as part of the AccessWave Series. For detailed information about these modules, see the Solutions Guide for the module portfolio.

AccessWave Series modules

IMPORTANT NOTE: All SDH CCAT cards have been consolidated with VCAT cards. As from Version 7.3 SDH cards consist of CCAT and VACT.

AccessWave Series Modules Module Name Dual 4G Multiprotocol Transponder 4-PORT 4G WT 3R

Dual 10G Multiprotocol Transponder DUAL 10G WM

Dual 10G Multiprotocol Transponder Lite DUAL 10G WM 3R(LITE)

10G Multiprotocol Transponder SINGLE 10G WM 3R+PM

8-Port Multiprotocol Muxponder — SONET 8P ANY MUX SONET

8-Port Multiprotocol Muxponder — SDH 8P ANY MUX SDH

10-Port Multiprotocol Muxponder — SONET 10P 10G MUX SONET

10-Port Multiprotocol Muxponder — SDH 10P 10G MUX SDH

Optical Packet Switch – 2 Lines 12 clients OPS 2-12



The management software suite was renamed for the AccessWave Series. The following table identifies the new name of each application in the suite. For detailed information about each application, see the Online Help for the application.

Management Software Suite Evolution

AccessWave Software Name AccessWave Network Manager AccessWave EMS

AccessWave Node Controller AW_LCT

AccessWave Network Designer AccessWave Builder


xiv ECI Telecom Ltd. Proprietary 426006-2423-023-A00

Equipment Compliance The following table provides agency-compliance information for AccessWave Series equipment.

Agency Compliance

Agency Compliance information

FDA This equipment is classified by the FDA under IEC 60825, parts 1 and 2, as a Class 1 laser product with a Class 1 hazard rating.

FCC This equipment complies with Part 15 of the FCC rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) This device must accept any interference received, including interference that may cause undesired operation.

Industry Canada

This Class A digital apparatus complies with Canadian ICES-003.

Organization of the AccessWave Series Documentation

The following guides are contained in the AccessWave Series documentation suite.

Common Equipment Installation Guide Quick Install Notes Upgrade Guide Operations Solution Guide Transponder Solutions Guide Muxponder Solutions Guide Optical Packet Switch Solution Guide Amplifier and DCM Solutions Guide Multiplexing Solutions Guide Alarm and Troubleshooting Guide SNMP Reference Guide TL1 Reference Guide Optical Packet Switch Command Line Interface Reference Guide Release Notes

426006-2423-023-A00 ECI Telecom Ltd. Proprietary 1-1

This section provides information about the common equipment, modules, and management interfaces supported by AccessWave Series Release 7.3.1.

AccessWave Series Common Equipment

The following table lists the AccessWave Series shelves and other common equipment supported in Release 7.3.1. For detailed information about the AccessWave Series, see the Product Guide and the Common Equipment Installation Guide.

Table 1-1: Common equipment supported in Release 7.3.1

Equipment Module Name

AW-60 AW-60 Shelf

AW-60 with rear access -48V AW-60 Shelf rear -48v

AW-60 Cooling Unit (CU) AW-60 Cooling Unit

AW-60 Main Shelf Interface (MSI) AW-60 MSI

AW-60 Expansion Shelf Interface (ESI) AW-60 ESI

AW-60 System Control Processor (SCP) AW-60 SCP

AW-60 AC Power Assembly Kit AW-60 AC PWR Assy kit

AW-60 AC Power Module AW-60 AC Power Unit

AW-30 AW-30 Shelf

AW-30 Cooling Unit (CU) AW-30 Cooling Unit

AW-30 Main Shelf Interface (MSI) AW-30 MSI

AW-30 System Control Processor (SCP) AW-30 SCP

AW-30 AC Power Assembly Kit AW-30 AC PWR Assy kit

AW-30 AC Power Module AW-30 AC Power Unit

AW-20 AW-20 Passive Shelf

1 AccessWave Series Overview

AccessWave Series Overview AccessWave Series Upgrade Guide from V7.1.x or 7.2.1 to 7.3.1

1-2 ECI Telecom Ltd. Proprietary 426006-2423-023-A00

Shelf and Module Compatibility The following tables identify the AccessWave Series modules that are supported on AW-60 shelves that have been upgraded to the AccessWave Series platform and on AccessWave Series shelves. For information about upgrading AW-60 shelves to the AccessWave Series platform, see the Upgrade Guide — Release 6.2 to Release 7.1.0.

NOTE: The AW-30 shelf cannot be upgraded to Release 7.3.1 and, therefore, cannot support AccessWave Series modules

Table 1-2: Common equipment

AccessWave Series modules Module Name AW-30 AW-60

AW-60 Cooling Unit (10,000 rpm) AW-60 Cooling Unit No No

AW-60 Main Shelf Interface AW-60 MSI No No

AW-60 Expansion Shelf Interface AW-60 ESI No No AW-60 Multiport System Control Processor

AW-60 SCP No Yes

AW-30 Cooling Unit AW-30 Cooling Unit Yes No

AW-30 Main Shelf Interface AW-30 MSI Yes No

AW-30 System Control Processor AW-30 SCP Yes No

Table 1-3: Optical Amplifier modules


DWDM C-Band Pre-Amplifier DWDM Pre_AMP UC Yes Yes

DWDM C-Band Booster Amplifier DWDM Boost_AMP UC Yes Yes

Optical Line Amplifier OLA SC Yes Yes

Optical Line Amplifier with mid-stage access

OLA w/ Mid_stage SC Yes Yes

Single Channel and Sub-band Booster Amplifier

Sub Band Boost_AMP UC

Yes Yes

Single Channel and Sub-band Pre-Amplifier

Sub Band Pre_AMP UC Yes Yes


AccessWave Series Overview


Table 1-4: Dispersion Compensation modules


SMF Dispersion Compensation Module 20km SMF DCF 20KM UC Yes Yes

SMF Dispersion Compensation Module 40km SMF DCF 40KM SC Yes Yes



SMF 100 GHz C-Band DCM 40km SMF C-Band DCM 40km

Yes Yes


Yes Yes


Yes Yes

Table 1-5: Optical Multiplexing modules


4-Channel CWDM Mux/Demux, Channel 1 - 4 4Ch CWDM M/D 1-4 Yes Yes

4-Channel CWDM Mux/Demux, Channel 5 - 8 4Ch CWDM M/D 5-8 Yes Yes

4-Channel CWDM Mux/Demux, Channel 9 - 12

4Ch CWDM M/ D 9-12

Yes Yes

4-Channel CWDM Mux/Demux, Channel 13- 16

4Ch CWDM M/ D 13-16

Yes Yes

1-Channel CWDM OADM 1Ch CWDM OADM Ch#1

Yes Yes

Double 1-Channel OADM Du 1Ch CWDM OADM Ch#1

Yes Yes

2-Channel CWDM OADM 2Ch CWDM OADM Ch#1&2

Yes Yes

32-Channel DWDM Mux/Demux Module 1 8Ch DWDM M/D 1-8 Yes Yes

32-Channel DWDM Mux/Demux Module 2 8Ch DWDM M/ D 9-16

Yes Yes


Yes Yes


Yes Yes

32-Channel DWDM Bidirectional Mux/ Demux1

8Ch Bi-dir DWDM MB2/DB4 8Ch Bi-dir DWDM MB4/DB2

No No

32-Channel DWDM Bidirectional Mux/ Demux2

8Ch Bi-dir DWDM MB1/DB3 8Ch Bi-dir DWDM MB3/DB1

No No

1-Channel DWDM OADM 1Ch DWDM OADM Ch#1

Yes Yes

2-Channel DWDM OADM 2Ch DWDM OADM Ch#1&2

Yes Yes




4-Channel DWDM OADM 4Ch DWDM OADM Ch#1-4

Yes Yes

4-Channel DWDM OADM, ECI Channels 53, 55, 57, 59

4Ch DWDM OADM Extra

Yes Yes

CWDM + DWDM Splitter Combiner CWDM+DWDM S/C Yes Yes

1310nm and C-Band Coupler/Splitter 1310nm & C-Band S/C

Yes Yes

DWDM Bidirectional Coupler/Splitter Du Bi-dir S/C Yes Yes 1Supported on AW-20 only 2Supported on AW-20 only.

Table 1-6: Transponder modules


1G Wavelength Translator 4-PORT 1G WT 2R Yes Yes

1G Wavelength Regenerator 4-PORT 1G WR 3R Yes Yes

2.5G Wavelength Regenerator 4-PORT 2.5G WR 3R Yes Yes

2.5G Wavelength Manager 4-PORT 2.5G WM 3R+PM

Yes Yes

Dual 4G Multiprotocol Transponder with PMs 4-PORT 4G WT 3R Yes Yes

Dual 10G Multiprotocol Transponder DUAL 10G WM 3R+PM

Yes Yes

Dual 10G Multiprotocol Transponder Lite DUAL 10G WM 3R(LITE)

Yes Yes

10G Multiprotocol Transponder SINGLE 10G WM 3R+PM

Yes Yes


AccessWave Series Overview


Table 1-7: Muxponder modules


2-Port GbE Muxponder (OC-48 with protection)

2.5G MUXPONDER OC-48

Yes Yes

2-Port GbE Muxponder (STM-16 with protection)

2.5G MUXPONDER STM-16

Yes Yes

8-Port Multiprotocol Muxponder - SONET 8P ANY MUX SONET

Yes Yes

8-Port Multiprotocol Muxponder - SDH 8P ANY MUX SDH Yes Yes

10-port 10G Multiprotocol Muxponder - SONET

10P 10G MUX SONET

Yes Yes

10-port 10G Multiprotocol Muxponder - SDH 10P 10G MUX SDH Yes Yes

IMPORTANT NOTE: All SDH CCAT cards have been consolidated with VCAT cards. As from Version 7.3 SDH cards consist of CCAT and VACT.

Table 1-8: Optical Packet Switch modules


Optical Packet Switch Integrated OPS 2-12 Yes Yes

Optical Packet Switch Integrated OPS 2-24 No Yes

Optical Packet Switch Integrated OPS 4-24 No Yes

AccessWave Series Management Interfaces

The AccessWave Series supports standard communication interfaces over serial and IP connections, including Telcordia Transaction Language One (TL1), SNMP, and GCC0. In addition, the AccessWave Series provides the AccessWave Management System, a Java-based craft management interface, for management of individual NEs.

The main tasks in this Upgrade Guide are described using both AccessWave Management System-based procedures and TL1-based procedures.

For information about the management interfaces that the AccessWave Series supports, refer to the following documentation:

AccessWave Management System Online Help

TL1 Reference Guide

SNMP Reference Guide

Management Communications Channel Solutions Guide


This section provides information about upgrading the system software from Release 7.1.x or 7.2.1 to Release 7.3.1.

Upgrade Task Flow The following list identifies the order of tasks in the process for upgrading a system from Release 7.1.x or 7.2.1 to Release 7.3.1.

1. Perform a database backup. For information, see Performing Database Backup.

2. If you use the AccessWave Management System to manage AccessWave Series nodes, set up the AccessWave Management System by uninstalling Release 7.2.1 of the AccessWave Management System, and then installing Release 7.3.1. For information, see Setting up the AccessWave Management System.

3. Load, invoke, and commit the system software upgrade. For information, see Loading, Invoking, and Committing the System Software Upgrade.

4. Install and provision new shelves and modules, and if necessary, replace common equipment such as the Cooling Unit. For information, see the Common Equipment Installation Guide, the Operations Solution Guide, and the Solutions Guide for the module portfolio.

2 Upgrading to Release 7.3.1

Upgrading to Release 7.3.1 AccessWave Series Upgrade Guide from V7.1.x or 7.2.1 to 7.3.1


Before you Upgrade to Release 7.3.1

The following is a check list to be reviewed before upgrading the system software from Release 7.1.x or 7.2.1 to Release 7.3.1.

The document Release Notes for Release 7.3.1 has been reviewed for information about upgrading the system software.

The "Troubleshooting" chapter of the Solutions Guide for each module type installed or to be installed on the system has been reviewed for information relating to a system software upgrade.

The management network is operating at an acceptable performance level.

There are no CONTCOM alarms on the system. See the Alarm and Troubleshooting Guide for information about clearing a CONTCOM alarm.

The location to which the database will be backed up has enough space to store the data.

NOTE: A fully configured AW-60 main shelf and its log files can create a backup file of several megabytes in size. For more information, see Performing Database Backup.

If you are replacing the SCP, ensure that both software banks on their placement SCP are loaded with the same software image of the release to which you are upgrading, and that the release numbers for the Active and Inactive software banks match.

If you use the AccessWave Management System to manage AccessWave Series nodes in the network, ensure the following:

The AccessWave Management System Release 7.2.1 is available to perform a database backup of the Release 7.2.1 configuration database.

The AccessWave Management System Release 7.3.1 is available for installation. For information, see Setting up the AccessWave Management System.

The computer on which the AccessWave Management System will be installed meets the minimum requirements for the software. For information, see Installing AccessWave Management System Release 7.3.1 on Microsoft Windows or Installing AccessWave Management System Release 7.3.1 on Solaris.


Upgrading to Release 7.3.1


NOTE: AFFECTED SERVICES DURING UPGRADE When a system-level upgrade has been completed, you must perform a cold restart of all 8-port & 10-port Multiprotocol Muxponders installed on the system. A cold restart is required to enable provisioning of Release 7.3.1 features and activation of software updates on these Muxponder modules.

Performing Database Backup The AW-60 SCP maintains all provisionable data in non-volatile storage so that configuration settings are retained during a system shutdown and restart. This configuration database is version controlled to facilitate the detection of an incompatible software load or database.

Before you upgrade the system software to Release 7.3.1, you can back up the database locally, to an FTP server, or to the AccessWave Series SCP.

IMPORTANT: ECI Telecom recommends that the database be backed up to the SCP and either locally or to an FTP server. Backing up to the SCP enables you to cancel the upgrade if necessary, and then revert to the configuration database stored on the SCP.

If you choose to back up to an FTP server, you can either specify a particular FTP server or use the FTP utility embedded in the AccessWave Management System.



Database Backup using the AccessWave Management System

Prerequisites If backing up to an FTP server, the server must be set up for remote

backups.

The backup location has enough space for the data.

NOTE: Data for either a main shelf only or for a main shelf and an expansion shelf requires several megabytes of free space.

To back up the database using the AccessWave Management System:

1. Select Administration from the View menu.

2. In the System pane, click Database Backup to display the database backup settings.

3. In the Backup Settings panel, do one of the following: a. Choose Local PC to back up the database to the local computer, enter a

name for the backup file in the File field, and then click Save As. b. Choose Remote PC to back up the database to an FTP server, specify

the connection settings to the server, and then enter the path to the file, including the file name, in the File field.

NOTE: Some UNIX systems may require you to enter the entire directory path and the database file name in the File field.

NOTE: If you use the embedded FTP server, the default directory will be the same as the AccessWave Management System installation directory.

c. Choose SCP to backup the database to the AccessWave Series SCP, and then enter a name for the backup file in the File field.

NOTE: If you select SCP, any backup file already stored on the SCP will be overwritten.




4. If alarms are present on the system, select the Ignore Alarms check box.

IMPORTANT: The database backup will not proceed if alarms are present on the system and the Ignore Alarms check box has not been selected.

5. Click Backup.

Messages indicating the progress of the database backup appear in the Status window. If the backup is successful, the message Backup Process Completed Successfully appears. If the backup fails, an error message appears.

Database Backup using TL1

Prerequisites If backing up to an FTP server, the server must be set up for remote

backups.

The backup location has enough space for the data.

NOTE: Data for either a main shelf only or for a main shelf and an expansion shelf requires several megabytes of free space.

To back up the database using TL1:

1. Enter the following at the TL1 command line interface: INVK-DB-BKUP:[TID]:::<CTAG>::TYPE=<TYPE>,[IPADDR=<IPADDR>], [PATH=<PATH>],[USERID=<USERID>],[PWD=<PWD>],[CHKALM=<CHKALM>];

where <TYPE> is FTP or SCP

<IPADDR> is the address of the FTP server where the backup file will be stored <PATH> is the path to the database backup file, including the file name

NOTE: The value <PATH> can contain a maximum of 54 alphanumeric characters when TYPE=FTP and 48 alphanumeric characters when TYPE=SCP.



NOTE: Some UNIX systems may require you to enter the entire directory path and the database file name.

<USERID> is the user ID for the FTP server

<PWD> is the password assigned to the user ID <CHKALM> is Y or N

IMPORTANT: If CHKALM=Y and alarms are present on the system, the database backup will not proceed

If the backup is successful, the system returns the following message: AccessWave Series 08-12-31 16:22:02

M 100 COMPLD

;

AccessWave Series>

AccessWave Series Series 08-12-31 16:22:05 A 103 REPT EVT EQPT

"SCP-1-5:DBBKUPPASS,,05-12-31,16-22-04,,,,,:\"Database Backup Completed Successfully.\",,,:," ;

If the backup fails, an error message appears.

Setting up the AccessWave Management System

If you use the AccessWave Management System to manage AccessWave Series nodes on the network, ECI Telecom recommends that Release 7.2.1 of AccessWave Management System be uninstalled before AccessWave Management System Release 7.3.1 is installed.

NOTE: If your network includes AccessWave Series nodes (i.e., nodes running Release 6.2 or earlier of the system software), the AccessWave Node Controller must be used for local GUI operation of these nodes. The AccessWave Management System must be used for local GUI operation of AccessWave Series nodes (i.e., nodes running Release 7.3 of the system software). The AccessWave Node Controller and AccessWave Management System can operate in the same network environment.




Uninstalling AccessWave Management System Release 7.2.1 on Microsoft Windows

Prerequisites Log out of and exit AccessWave Management System Release 7.2.1.

To uninstall AccessWave Management System on Windows:

1. Navigate to the directory where AccessWave Management System is installed, and open the folder Uninstaller Data.

2. Double-click the file Uninstall.exe. the AccessWave Management System uninstaller application starts, and displays the message Uninstall Complete when the process is completed.

3. Remove the AccessWave Management System directory from your computer.

You have successfully completed this procedure.

Uninstalling the AccessWave Management System Release 7.2.1 on Solaris

Prerequisites Log out of and exit AccessWave Management System Release 7.2.1.

To uninstall AccessWave Management System on Solaris:

1. Open a terminal window and navigate to the directory where AccessWave Management System is installed. and then type the following at the prompt:

2. At the prompt, type the following to open the folder Uninstaller Data:

cd UninstallerData

3. At the prompt, type the following to start the uninstaller application: / Uninstall

The AccessWave Management System uninstaller application displays the message Uninstall Complete when the uninstall process is completed.

4. At the prompt, type the following to remove the AccessWave Management System directory: rm -r <directoryname>




Installing AccessWave Management System Release 7.3.1 on Microsoft Windows

What you need AccessWave Management System CD-ROM

Prerequisites Ensure that the computer meets the following minimum requirements:

Operating system: Windows 2003 Server, or Windows XP

Windows-supported browsers: Internet Explorer version 6.0 or later, or any Mozilla-based browser version 2 or later

Recommended minimum screen resolution: 1024 x 768 pixels

Minimum color depth: 256 colors

1 GHz AMD/Intel

300 MB minimum of available disk space

2 GB minimum of RAM

To install AccessWave Management System on Windows:

1. Place the CD-ROM in your CD-ROM drive.

2. Open My Computer or use Windows Explorer to navigate to your CD-ROM drive.

3. Open the install.htm file located in the folder.

The AccessWave Management System software download web page opens.

4. Click Install AccessWave Management System 7.3.1.

A security warning may appear.

5. Click Open.

6. Follow the instructions that appear on the AccessWave Management System installer screen.

The AccessWave Management System installer guides you through the following steps:

Introduction Choose Install Folder Installation Warnings




NOTE: If the AccessWave Management System is already installed on the computer, you may be asked to uninstall the software or stop the installation procedure.

Choose Shortcut Folder Pre-Installation Summary Installing Install complete


Installing AccessWave Management System Release 7.3.1 on Solaris

What you need AccessWave Management System CD-ROM

Prerequisites Ensure that the UNIX workstation meets the following minimum requirements:

Operating System: Solaris 10

Solaris Supported Browsers: Mozilla, Netscape, FireFox, Konqueror, Opera, or Epiphany

Recommended minimum screen resolution: 1024 x 768 pixels

Minimum color depth: 256 colors

UltraSPARC III CPU

300 MB minimum of available disk space

2 GB minimum of RAM

To install AccessWave Management System on Solaris:

1. Place the CD-ROM in the CD-ROM drive, and then navigate to the directory where the CD-ROM drive is mounted.

2. Open the install.htm file located in the folder. A security warning may appear. Click Grant to close this dialog window.

3. Click Install Now.



4. Follow the instructions that appear on the AccessWave Management System installer screen. The AccessWave Management System installer guides you through the following steps:

Introduction Choose Installation Folder Installation Warnings

NOTE: If the AccessWave Management System is already installed on the workstation, you may be asked to uninstall the software or stop the installation procedure.

Pre-Installation Summary Installing Progress Install Complete

5. Set the PATH variable to the location where the web browser application resides.

NOTE: first browser found in the path is the default browser.


Troubleshooting Installation Problems An installation log file is available in the installation directory for both Windows and UNIX installations. The log file is titled: AccessWave Management System_InstallLog.log

The log file provides information on the software components that were installed successfully or failed to install.

Firewall Precaution If you have the Windows Firewall enabled, a firewall exception must be configured to allow the AccessWave Management System FTP server to function. The firewall exception should be configured with the java executable found in the AccessWave Management System Installation directory ("<installation directory>\jre\bin\javaw.exe).




Logging on to the AccessWave Series using the AccessWave Management System

To log on to the AccessWave Series system using the AccessWave Management System:

NOTE: The AccessWave Management System connects to the AccessWave Series system through either a craft or management LAN port. For more information, see Establishing an AccessWave Management System Session using Ethernet.

1. Start the AccessWave Management System.

2. In the Login dialog, enter the IP address that you want to connect to in the NE field.

The default IP address of the Management LAN on the AccessWave Management System is 10.0.0.1.

The default IP address of the Craft LAN port is 192.168.17.1.

3. In the User ID field, enter admin, which is the default user ID.

4. In the Password field, enter admin, which is the default password.

5. Click OK.

The AccessWave Management System starts and establishes a session with the AccessWave Series system.




Loading, Invoking, and Committing the System Software Upgrade

Release 7.3.1 of the system software can be loaded, invoked, and committed using either Release 7.3.1 of the AccessWave Management System or TL1.

What you need AccessWave Series CD.

NOTE: The AccessWave Series CD contains an encrypted manifest file, a binary image file, and a readme file. The manifest file contains a listing of all the software components contained in the binary image. The manifest file and the binary image file are required for upgrading the system software.

Prerequisites See Upgrade Task Flow and Before you Upgrade to Release 7.3.1.

IMPORTANT: Review the "Troubleshooting" chapter of the Solutions Guide for each module type installed on the system for information about additional procedures that might be required during or after the system software upgrade.

You must be logged on to the system using Release 7.3.1 of the AccessWave Management System.

NOTE: Release 7.3.1 of the AccessWave Management System is backward compatible and can be used to manage Release 7.2.1 versions of the system software before the system software is upgraded.

If you are using an external FTP server to access the AccessWave Series CD, the FTP root directory must be configured to serve files from the CD, or the CD files must be copied to the FTP root directory.

The FTP server and the AccessWave Series system must have IP connectivity.

There are no CONTCOM alarms on the system.




Recommendations The state of the AccessWave Series system is In Service.

Remove or install modules during the upgrade process only if you are instructed to do so.

Loading, Invoking, and Committing the Upgrade

To load, invoke, and commit the system software upgrade to Release 7.3.1 using the AccessWave Management System:

1. Insert the AccessWave Series CD into the CD-ROM drive.

NOTE: If you are using an FTP server other than the embedded FTP server (i.e., a remote PC), install the CD in the external FTP server.


3. In the System pane, click Software Upgrade to display the upgrade settings.

4. In the Load Settings panel, do one of the following: Choose Local PC (the default), and then click Browse to navigate to and

select the binary image file on the CD-ROM. Choose Remote PC, specify the connection settings to the FTP server,

and then enter the path to the binary image file in the Directory field.

NOTE: Some UNIX systems may require you to enter the entire directory path and file name in the Directory field.

5. Click Check to verify that the correct software upgrade file is available.

6. Click Load.

Release 7.3.1 of the system software takes several minutes to load.

7. In the Upgrade Settings panel, verify that Release 7.3.1 is specified in the Inactive Release Number field and Release 7.2.1 is specified in the Active Release Number field.



8. If alarms (other than CONTCOM) are present on the system, select the Ignore Alarms check box in the Upgrade Settings panel.

IMPORTANT: The system software upgrade will not proceed if alarms are present on the system and the Ignore Alarms check box has not been selected.

9. Click Invoke. The SYSUPGRDPROG (System Software Upgrade in Progress) alarm

is raised, and its severity is Minor. The modules in the system are loaded with Release 7.3.1 of the system

software. The alarm severity changes from Minor to Major and the system then restarts, starting with the SCP and followed by the modules, and then the AccessWave Management System session ends.

IMPORTANT: The amount of time that the invoke operation takes to complete depends on the configuration of the node. For example, for a full four-shelf system, the invoke operation may take up to one hour to complete.

NOTE: During re initialization, the red Fail LED on each module in the node may light temporarily while the green Active LED is lit.

10. When the red Fail LEDs turn off, start the AccessWave Management System, and log on to the system.

NOTE: It can take several minutes to connect to the system.

11. In the Alarms pane, check the severity of the SYSUPGRDPROG alarm. If the severity of the SYSUPGRDPROG alarm is Major, the system

upgrade is still in progress. Wait until the severity of the SYSUPGRDPROG alarm changes to Minor, which indicates that the system upgrade is complete, and then proceed to the next step.

NOTE: You can refresh the AccessWave Management System GUI while the system upgrade is in progress.

If the severity of the SYSUPGRDPROG alarm is Minor, the system upgrade is complete. Proceed to the next step.




NOTE: At this point, you may cancel the software system upgrade if necessary and revert to Release 7.2.1 of the system software. For information, see Cancelling a System Software Upgrade Process using the AccessWave Management System.

NOTE: If the invoke operation fails, see “Invoke failure” for information.


13. In the System pane, click Software Upgrade.

14. In the Upgrade Settings panel, verify that Release 7.3.1 is specified in the Active Release Number field.

15. Click Commit.

The SYSUPGRDPROG alarm clears, Release 7.3.1 is specified in the Active Release Number field, and Release 7.2.1 is specified in the Inactive Release Number field.

NOTE: If the commit operation fails, see Committing Failure for information.

16. When a system-level upgrade has been completed, you must perform a cold restart of all 8-port &10-port Multiprotocol Muxponders installed on the system.




Loading, Invoking, and Committing the System Software Upgrade using TL1

What you need AccessWave Series CD

NOTE: The AccessWave Series CD contains an encrypted manifest file, a binary image file, and a readme file. The manifest file contains a listing of all the software components contained in the binary image. The manifest file and the binary image file are required for upgrading the system software.

Prerequisites See Upgrade Task Flow and Before you Upgrade to Release 7.3.1.

IMPORTANT: Review the "Troubleshooting" chapter of the Solutions Guide for each module type installed on the system for information about additional procedures that might be required during or after the system software upgrade.

You must be logged on to the system.

If you are using an external FTP server to access the AccessWave Series CD, the FTP root directory must be configured to serve files from the CD, or the CD files must be copied to the FTP root directory.

The FTP server and the AccessWave Series system must have IP connectivity.



Remove or install modules during the upgrade process only if you are instructed to do so.




To load, invoke, and commit the system software upgrade to Release 7.3.1 using TL1:

1. Insert the AccessWave Series CD into the CD-ROM drive of the FTP server, and connect to the server.

2. Enter the following at the TL1 command line interface to verify that the correct software file is available: CHCK-SYS-UPGRD:[TID]::<CTAG>:::IPADDR=<IPADDR>,[PATH=<PATH>], [USERID=<USERID>],[PWD=<PWD>];

where

<IPADDR> is the IP address of the server where Release 7.3.1 of the system software is stored

<PATH> is the directory path to the upgrade software

NOTE: If Release 7.3.1 of the system software is stored in the root directory of the FTP server, the PATH parameter is not required.


<PWD> is the password assigned to the user ID

For example, CHK-SYS-UPGRD:AccessWave Series::100::IPADDR=112.23.45.62; AccessWave Series 2008-01-21 14:00:41

M100 COMPLD

;

AccessWave Series> AccessWave Series 2008-01-21 14:00:42

A8 REPT EVT EQPT "SCP-1-3:SYSCHKPASS,,2008-01-21,14-00-43,,,,,:\"Check Upgrade Completed Successfully.\",,,:,"

;

NOTE: If the check operation fails, see Checking Failures for information.



3. Enter the following at the TL1 command line interface to load Release 7.3.1 of thesystem software: LOAD-SYS-UPGRD:[TID]::CTAG:::IPADDR=<IPADDR>;

where

<IPADDR> is the IP address where Release 7.3.1 of the system software is stored For example,

LOAD-SYS-UPGRD:AccessWave Series::100:::IPADDR=112.23.45.62; AccessWave Series 2008-01-21 14:20:41 M100 COMPLD

;

AccessWave Series>

AccessWave Series 2008-01-21 14:22:10

A7 REPT EVT EQPT

"SCP-1-5:SYSLOADPASS,,2008-01-21,14-22-09,,,,,:\"Software Load Completed Successfully.\",,[/] [192.168.172.110] ,:,"

;

Release 7.3.1 of the system software takes several minutes to load. Note: if the load operation fails, see Loading Failures for information.

4. Enter the following at the TL1 command line to verify that Release 7.2.1 is stored in the active software bank and that Release 7.3.1 of the system software is stored in the inactive software bank: RTRV-SYS-RELNUM:[TID]::<CTAG>;

For example,

RTRV-SYS-RELNUM:AccessWave Series::100; AccessWave Series 2008-01-21 14:22:30

M100 COMPLD

"ACTIVE=7.1.1,INACTIVE=7.1.2,"

;

5. Enter the following at the TL1 command line interface to invoke the system software upgrade: INVK-SYS-UPGRD:[TID]::<CTAG>:::RELNUM=<relnum>,[CHKALM=<chkalm>];

where

<RELNUM> is the release number of the system software <CHKALM> is Y or N

For example, INVK-SYS-UPGRD:AccessWave Series::100:::RELNUM=7.1.2,CHKALM=N;




The SYSUPGRDPROG (System Software Upgrade in Progress) alarm is raised, and its severity is Minor.

The modules in the system are loaded with the upgraded system software. The alarm severity changes from Minor to Major and the system then restarts, starting with the SCP and followed by the modules, and then the TL1 session ends.


NOTE: During re initialization, the red Fail LED on each module may light temporarily while the green Active LED is lit.

6. When the red Fail LEDs turn off, log on to the system.


7. Enter the following at the TL1 command line interface to check the severity of the SYSUPGRDPROG alarm: RTRV-ALM-ALL:[TID]::CTAG::,,,,,;

For example, RTRV-ALM-ALL:AccessWave Series::100::,,,,,;

If the severity of the SYSUPGRDPROG alarm is MJ (Major), the system

upgrade is still in progress. Use the RTRV-ALM-ALL command to check the severity of SYSUPGRDPROG alarm until the severity changes to MN (Minor), which indicates that the system upgrade is complete, and then proceed to the next step.

If the severity of the SYSUPGRDPROG alarm is MN (Minor), the system upgrade is complete. Proceed to the next step.

NOTE: At this point, you may cancel the software system upgrade if necessary and revert to Release 7.2.1 of the system software. For information, see Cancelling a System Software Upgrade Process using TL1.

NOTE: If the invoke operation fails, see Invoking Failure for information.



8. Enter the following syntax at the TL1 command line interface to verify that Release 7.3.1 of the system software is stored in the active software bank. RTRV-NETYPE:[TID]::CTAG;

For example, RTRV-NETYPE:AccessWave Series::100;

AccessWave Series 2008-01-21 15:20:31 M100 COMPLD

AccessWave Series,AW-60,WDM,7.1.2 ;

9. Enter the following at the TL1 command line interface to commit the upgrade:

CMMT-SYS-UPGRD:[TID]::CTAG::;

For example,

CMMT-SYS-UPGRD:AccessWave Series::100::;

The SYSUPGRDPROG alarm clears. Optionally, you can use the RTRV-SYS-RELNUM command to verify that Release 7.3.1 of the system software is stored in the active software bank and that Release 7.2.1 is stored in the inactive software bank.

For example, RTRV-SYS-RELNUM:AccessWave Series::100; AccessWave Series 2008-01-21 16:22:30

M100 COMPLD


;


10. When a system-level upgrade has been completed, you must perform a cold restart of all 8-port &10-port Multiprotocol Muxponders installed on the system.

Enter the following at the TL1 command line interface to restart a module: INIT-SYS:[TID]:[AID]:CTAG::1:CMDMDE=FRCD;

For example: INIT-SYS:AW60:MXP-1-1:100::1:CMDMDE=FRCD;




Equipment Installing and Provisioning

After the upgrade to Release 7.3.1 is committed, any new shelves and modules to be deployed can be added and provisioned. For information, see the following documents:

Common Equipment Installation Guide

Operations Solution Guide

Solutions Guide for the module portfolio

Auto-upgrade Support on Modules

All modules (that is, Transponders, Muxponders, Optical Amplifiers, DCMs, and Multiplexers) ship with pre-loaded software. When a module is inserted into a shelf, the module software release number is checked to determine if it matches that of the system software. The module software is automatically upgraded if it is an earlier version than the system software.

During an auto upgrade, the following occurs:

The UPGRDPROG minor alarm is raised.

The module upgrade starts.

The module initializes.

The UPGRDPROG alarm clears.

IMPORTANT: Review the "Troubleshooting" chapter of the Solutions Guide for a module portfolio for information about additional procedures that might be required after an auto-upgrade is completed.


This section provides information about returning the AccessWave Series to an earlier version of the system software.

Cancelling a System Software Upgrade Process using the AccessWave Management System

Prerequisites You must be logged into the system using the AccessWave Management

System. The invoke operation of the system software upgrade process has been

performed. The commit operation of the system software upgrade process has not been

performed. All modules, including the SCP, have been upgraded and reinitialized. The SYSUPGRDPROG (System Software Upgrade in Progress) alarm is

raised and its severity is Minor.

3 Returning to an Earlier

Version of the System Software

Returning to an Earlier Version of the System Software



To cancel a system software upgrade process using the AccessWave Management System:

1. In the Alarms pane, verify that a SYSUPGRDPROG (System Software Upgrade in Progress) alarm is raised and its severity is Minor.



4. In the Upgrade Settings panel, verify that Release 7.3.1 is specified in the Active Release Number field and Release 7.2.1 is specified in the Inactive Release Number field.

5. Click Cancel.

The SYSUPGRDPROG alarm changes to Major, the system restarts, starting with the SCP and followed by the modules, and then the AccessWave Management System session ends.

NOTE: During re initialization, the red Fail LED on each module may light temporarily, while the green Active LED is lit.



7. In the Alarms pane, verify that the SYSUPGRDPROG alarm has cleared.




NOTE: If the cancel operation fails, see Cancelling Failure for information.





Cancelling a System Software Upgrade Process using TL1

Prerequisites You must be logged into the system.

The invoke operation of the system software upgrade process has been performed.

The commit operation of the system software upgrade process has not been performed.

All modules, including the SCP, have been upgraded and reinitialized.

The SYSUPGRDPROG (System Software Upgrade in Progress) alarm is raised and its severity is Minor.

To cancel a system software upgrade process using TL1:

1. Enter the following syntax at the TL1 command line interface to verify that a SYSUPGRDPROG (System Software Upgrade in Progress) alarm is raised and its severity is Minor: RTRV-ALM-ALL:[TID]::CTAG::,,,,,;

2. Enter the following syntax at the TL1 command line interface to cancel the system software upgrade and confirm that the SYSUPGRDPROG alarm clears. CANC-SYS-UPGRD:[TID]::CTAG;

For example, CANC-SYS-UPGRD:AccessWave Series::100;

The system returns the following message: AccessWave Series 2008-01-31 14:28:35

A10 REPT ALM EQPT

"SCP-1-5,CL,SYSUPGRDPROG,NSA,2008-01-31,14-28-35,,,,,,\"Clear Software Upgrade In Progress.\",,,,,"

;

The system restarts, starting with the SCP and followed by the modules, and then the TL1 session ends.

NOTE: During re initialization, the red Fail LED on each module may light temporarily, while the green Active LED is lit.






4. Enter the following syntax at the TL1 command line interface to verify that Release 7.2.1 is stored in the active software bank and Release 7.3.1 is stored in the inactive software bank. RTRV-SYS-RELNUM:[TID]::<CTAG>;

For example, RTRV-SYS-RELNUM:AccessWave Series::100;

The system returns the following message:

AccessWave Series 2008-01-31 14:28:45W

M100 COMPLD


;

NOTE: If the cancel operation fails, see Cancelling Failure for information.





Downgrading the System Software using the AccessWave Management System

Prerequisites See the Release Notes for Release 7.3.1 for information about downgrading

the system software.

You must be logged on to the system using Release 7.3.1 of the AccessWave Management System.



Remove or install modules during the downgrade process only if you are instructed to do so.

To downgrade the system software using the AccessWave Management System:

IMPORTANT: Any modifications provisioned on the system while Release 7.3.1 of the system software was running will be lost.

NOTE: If there are no active modules on the system, database recovery is not possible.


2. In the System pane, click Software Upgrade to display the upgrade settings.

3. In the Upgrade Settings panel, verify that Release 7.2.1 is specified in the Inactive Release Number field.




4. If alarms are present on the system, select the Ignore Alarms check box in the Upgrade Settings panel.

IMPORTANT: The system software downgrade will not proceed if alarms are present on the system and the Ignore Alarms check box has not been selected.

5. Click Invoke. The SYSUPGRDPROG (System Software Upgrade in Progress) is

raised, and its severity is Minor. The modules in the system are loaded with Release 7.2.1 of the system

software. The alarm severity changes to Major, and the system then restarts, starting with the SCP and followed by the modules, and then the AccessWave Management System session ends.


NOTE: During re-initialization, the red Fail LED on each module may light temporarily while the green Active LED is lit.



7. In the Alarms pane, check the severity of the SYSUPGRDPROG alarm. If the severity of the SYSUPGRDPROG alarm is Major, the system

downgrade is still in progress. Wait until the severity of the SYSUPGRDPROG alarm changes to Minor, which indicates that the system downgrade is complete, and then proceed to the next step.

If the severity of the SYSUPGRDPROG alarm is Minor, the system downgrade is complete. Proceed to the next step.








11. Click Commit.

The SYSUPGRDPROG alarm clears, Release 7.2.1 is specified in the Active Release Number field, and Release 7.3.1 is specified in the Inactive Release Number field.



Downgrading the System Software using TL1

Prerequisites See the Release Notes for Release 7.3.1 for information about downgrading

the system software.

You must be logged on to the system.



Remove or install modules during the downgrade process only if you are instructed to do so.




To downgrade the system software using TL1:

IMPORTANT: Any modifications provisioned on the system while Release 7.3.1 of the system software was running will be lost.

NOTE: If there are no active modules on the system, database recovery is not possible.

1. Enter the following at the TL1 command line to verify that Release 7.2.1 of the system software is stored in the inactive software bank and Release 7.3.1 is stored in the active software bank: RTRV-SYS-RELNUM:[TID]::<CTAG>;


M100 COMPLD

"ACTIVE=7.1.2,INACTIVE=7.1.1," ;

2. Enter the following at the TL1 command line interface to invoke the system software downgrade: INVK-SYS-UPGRD:[TID]::CTAG::[RELNUM=<RELNUM>],[CHKALM=<CHKALM>];

where

<RELNUM> is the release number of the system software

<CHKALM> is Y or N

For example, INVK-SYS-UPGRD:AccessWave Series::100::RELNUM=7.1.1,CHKALM=N;

IMPORTANT: The CHKALM parameter must be set to N for the downgrade to proceed as the RELNUMSWMEA alarm is raised.

The SYSUPGRDPROG (System Software Upgrade in Progress) alarm is raised, and its severity is Minor.

The modules in the system are loaded with the upgraded system software. The alarm severity changes to Major, and the system then restarts, starting with the SCP and followed by the modules, and then the TL1 session ends.





NOTE: During re initialization, the red Fail LED on each module may light temporarily while the green Active LED is lit.


4. Enter the following at the TL1 command line interface to check the severity of the SYSUPGRDPROG alarm: RTRV-ALM-ALL:[TID]::CTAG::,,,,,;

For example, RTRV-ALM-ALL:AccessWave Series::100::,,,,,;

If the severity of the SYSUPGRDPROG alarm is MJ (Major), the system downgrade is still in progress. Use the RTRV-ALM-ALL command to check the severity of the SYSUPGRDPROG alarm until the severity changes to MN (Minor), which indicates that the system downgrade is complete, and then proceed to the next step.

If the severity of the SYSUPGRDPROG alarm is MN (Minor), the system downgrade is complete. Proceed to the next step.


5. Enter the following at the TL1 command line interface to verify that Release 7.2.1 of the system software is stored in the active software bank: RTRV-NETYPE:[TID]::CTAG;

For example, RTRV-NETYPE:AccessWave Series::100;


M100 COMPLD

AccessWave Series, AW-60,WDM,7.1.1 ;

6. Enter the following at the TL1 command line interface to commit the downgrade: CMMT-SYS-UPGRD:[TID]::CTAG::;

For example, CMMT-SYS-UPGRD:AccessWave Series::100::;





The SYSUPGRDPROG alarm clears. Optionally, you can use the RTRV-SYS-RELNUM command to verify that Release 7.2.1 of the system software is stored in the active software bank and that Release 7.3.1 is stored in the inactive software bank.


M100 COMPLD

"ACTIVE=7.1.1,INACTIVE=7.1.2," ;




This section provides information about other procedures you can perform when upgrading to Release 7.3.1.

Determining System Software Release Numbers

To determine the system software release number using the BNC or the AccessWave Management System:


2. In the System pane, select Software Upgrade.

System release number information is provided in the Active Release Number and Inactive Release Number fields.

4 Useful Procedures

Useful Procedures AccessWave Series Upgrade Guide from V7.1.x or 7.2.1 to 7.3.1


Determining the System Software Release Number using TL1

The following table lists the TL1 commands that retrieve system software release numbers.

Command Release retrieved

RTRV-NETYPE Active release RTRV-SYS-RELNUM Active release and Inactive release

Database Restoring using the AccessWave Management System

What you need Backup file of the database

Prerequisites The database backup file corresponds to the network element to which it

will be restored.

NOTE: If restoring a database with communication port settings that are different from the current settings, connectivity can be lost. After the database restore operation is completed, reconnect using the communication port settings specified in the restored database.

IMPORTANT: Equipment provisioning cannot be performed during a database restore operation.


Useful Procedures


To restore the database using the AccessWave Management System:

1. Select Administration from the View menu. 2. In the System pane, click Database Restore. 3. In the Load Settings panel, do one of the following:

Choose Local PC to load a database backup file stored on the local PC, and then click Browse to navigate to and select the file.

Choose Remote PC to load a database backup file stored on an FTP server, enter the IP address of the FTP server, enter a user ID and a password in the FTP User ID and FTP Password fields, respectively, and then enter path to the file, including the file name, in the File field.

NOTE: Some UNIX systems may require you to enter the entire directory path and the database file name in the File field.

NOTE: Windows users should use a UNIX style directory name on a Windows FTP server. For example, if the files are stored in C:/Program Files/FTP Server/Files, omit the C: and enter the path as /Program Files/FTP Server/Files.

Choose SCP to load the database backup file stored on the SCP. 4. Click Load.

The file name of the database backup file appears in the Status window of the Database Restore Settings panel.

5. Click Invoke. 6. Do one of the following:

a. Click Accept, and then proceed to the next step. b. Click Cancel to cancel the database restore operation.

NOTE: Cancelling the database restore operation causes the system to restart and all AccessWave Management System sessions to end.

7. Click Commit to restore the database Messages indicating the progress of the database restore operation appear in the Status window.

If the database restore operation is successful, the message Restore Process Completed Successfully appears. If the operation fails, an error message appears.




Database Restoring using TL1

What you need Backup file of the database

Prerequisites All alarms on the system have been cleared.

The database backup file corresponds to the network element to which it will be restored.

NOTE: If restoring a database with communication port settings that are different from the current settings, connectivity can be lost. After the database restore operation is completed, reconnect using the communication port settings specified in the restored database.

IMPORTANT: Equipment provisioning cannot be performed during a database restore operation.

To restore the database using TL1:

1. Enter the following syntax at the TL1 command line interface to load the database file: LOAD-DB-RST:[TID]::<CTAG>:::TYPE=<TYPE>,[IPADDR=<IPADDR>],

[PATH=<PATH>],[USERID=<USERID>],[PWD=<PWD>],[TIDCHK=<TIDCHK>]; where <TYPE> is FTP or SCP <IPADDR> is the address of the FTP server where the backup file is stored <PATH> is the path to the database backup file, including the file name

NOTE: The value <PATH> can contain a maximum of 54 alphanumeric characters when TYPE=FTP and 48 alphanumeric characters when TYPE=SCP.

NOTE: Some UNIX systems may require you to enter the entire directory path and the database file name.


Useful Procedures



<PWD> is the password assigned to the user ID <TIDCHK> is Y or N

If the value <PATH> includes the TID, the TID in the database file name must match the TID of the system. However, if the default file name is changed, set the parameter TIDCHK to N.

The system returns the following message: NYC101 06-01-28 06:22:01

M100 COMPLD

;

AccessWave Series>

NYC101 06-01-28 06:22:03

A3 REPT EVT EQPT

"SCP-1-5:DBLOADPASS,,06-01-28,06-22-02,,,,,:\"Database Load

Completed Successfully.\",,\"[AccessWave Series_NYC101_January24_2006] [10.

1.1.100]\",:,"

;

2. Enter the following syntax at the TL1 command line to retrieve the database file: RTRV-DB-RST:[TID]::<CTAG>;

For example, RTRV-DB-RST:NYC101::100;

The system returns the following message, which indicates the name of the database file that is loaded: NYC101 06-01-28 06:22:02

M100 COMPLD

"[AccessWave Series_NYC101_January24_2006]";

;

3. Enter the following syntax at the TL1 command line to invoke the database restore process: INVK-DB-RST:[TID]::<CTAG>:::FILENAME=<FILENAME>, [CHKALM=<CHKALM>];

where

<FILENAME> is the name of the database file <CHKALM> is Y or N



NOTE: The system defaults to the following format for the file name: AccessWave Series_<NEName>_<MONTH><DAY>_<YEAR>. For the file name to function correctly, one or more alphabetic characters and the underscore must precede <NEName>.

For example, INVK-DB-RST:AccessWave Series::100:::

_NYC101_January24_2006,CHKALM=N;


M100 COMPLD

;

AccessWave Series>

NYC101 03-01-28 06:23:06 ** 4 REPT ALM EQPT

"SCP-1-5,MJ,DBRSTPROG,NSA,06-01-28,06-23-05,,,,,:\"Database Restore In Progess.\",,,:,"

;

NYC101 03-01-28 06:23:06

A5 REPT EVT EQPT

"SCP-1-5:INVKDBRSTPASS,,06-01-28,06-23-05,,,,,:\"Invoke Database Restore Completed Successfully.\",,,:," ;

4. Do one of the following: a. To accept the database file, enter the following syntax at the TL1

command line interface, and then proceed to the next step: ACPT-DB-RST:[TID]::<CTAG>; For example, ACPT-DB-RST:NYC101::100;


M FD COMPLD

;

AccessWave Series>

NYC101 06-01-28 06:23:33

A6 REPT EVT EQPT

"SCP-1-5:APPLDBRSTPASS,,06-01-28,06-23-32,,,,,:\"Apply Database Restore Completed Successfully.\",,,:," ;


Useful Procedures


b. To cancel the database restore operation, enter the following at the TL1 command line interface: CANC-DB-RST:[TID]::<CTAG>;

For example, CANC-DB-RST:NYC101::100;


A21 REPT ALM EQPT

"SCP-1-5,CL,DBRSTPROG,NSA,06-01-28,06-23-54,,,,,,\"Clear

Database Restore In Progress.\",,,,,"

;

NOTE: Cancelling the database restore operation causes the system to restart and all TL1 sessions to end.

5. Enter the following at the TL1 command line interface to commit the database restore operation: CMMT-DB-RST:[TID]::<CTAG>;

For example, CMMT-DB-RST:NYC101::100;

The system returns the following message: AccessWave Series>

06-01-28 06:23:54 M 100 COMPLD

;




Establishing an AccessWave Management System Session using Ethernet

Use Method One: Connecting through the Management LAN, or Method Two: Connecting through the Craft LAN Port to establish an Ethernet connection to the AccessWave Series system.

NOTE: The same functions are available through the craft LAN and the management LAN interfaces.

The following table lists the IP addresses for the AccessWave Series LAN communication ports.

Table 4-1: IP Addresses

Communications Port

Default IP Address

Default IP MaskDefault IP Gateway

Default IP Addresses: Management LAN Port

10.0.0.1 255.0.0.0 0.0.0.0

Craft LAN Port192 192168.17.1 1255.255.255.0 0.0.0.0 For a PC Connected To:1

Management LAN Port

10.x.y.z2 255.0.0.0

Craft LAN Port 192.168.17.z3 255.255.255.0 1You do not need to configure a default gateway on the PC. 2Where x and y are 0 to 255, and 2 ≤ z ≤ 254 3Where 2 ≤ z ≤ 254

NOTE: The Ethernet ports are set to Auto-Negotiate. To ensure optimum communication between the AccessWave Series system and your equipment, ECI Telecom recommends that you set your equipment to Auto-Negotiate, as well.

You do not need to configure a default gateway on the PC.


Useful Procedures


The following illustrations shows the two methods to use when establishing an AccessWave Management System session using Ethernet.

Figure 4-1: Establishing an AccessWave Management System session using Ethernet

Figure 4-2: Establishing an AccessWave Management System session using Ethernet



Method One: Connecting through the Management LAN

Prerequisites To connect a PC directly to the management LAN port on the shelf, you

require a CAT 5 shielded, grounded Ethernet cable of sufficient length with RJ-45 male connectors.

The Ethernet LAN ports automatically determine what device is attached, and they automatically configure the input and output signals for the Ethernet cable used.

To connect to the AccessWave Series equipment through the management LAN:

1. Provision the IP Address If not yet configured, provision the shelf with the IP address of your intended management Ethernet LAN.

2. Connect the AccessWave Series Ethernet Cables Insert one end of a shielded and grounded Ethernet cable in the management LAN port. Insert the other end of the shielded and grounded Ethernet cable in the RJ-45 female Ethernet LAN connector on your hub or switch.

3. Connect the Computer Ethernet Cables Insert one end of a shielded and grounded Ethernet cable in the RJ-45 female Ethernet LAN connector on your PC. Insert the other end of the shielded and grounded Ethernet cable in the RJ-45 female connector of your management LAN.

4. Start an AccessWave Management System Session

5. Log on to the AccessWave Series using the AccessWave Management System



Useful Procedures


Method Two: Connecting through the Craft LAN Port

Prerequisites None

To connect to the AccessWave Series shelf through the craft LAN port:

1. Provision the IP Address

If not yet configured, provision the AccessWave Series shelf with the IP address of your intended craft Ethernet LAN.

2. Connect the Ethernet Cable

Insert one end of the shielded and grounded Ethernet cable in the craft LAN port.

Insert the other end of the shielded and grounded Ethernet cable in the RJ-45 female Ethernet LAN connector on your PC or laptop.

3. Start an AccessWave Management System Session

4. Log on to the AccessWave Series using the AccessWave Management System




Establishing a TL1 Session using RS-232

Figure 4-3: Establishing a TL1 session using the RS-232 Craft serial port

Figure 4-4: Establishing a TL1 session using the RS-232 Craft serial port


Useful Procedures


To connect a PC to an AccessWave Series shelf through the RS-232 craft serial port on the shelf:

1. Connect the RS-232 Cable. Insert one end of the RS-232 cable in the craft serial port on the AccessWave Series shelf.

Insert the other end of the RS-232 cable in the RS-232 male connector on your PC or laptop.

2. Set the RS-232 Parameters Set the default RS-232 parameters for the PC to match the AccessWave

Series shelf: Rate: 9600 bps Data Bits: 8 bits Parity: None Stop Bits: 1 bit Flow Control: None

3. Establish a TL1 Session From a terminal emulator, establish a TL1 session to the AccessWave Series shelf by pressing the Return key.

Response

The system responds with the system prompt.

4. Log on to the AccessWave Series To log on to the AccessWave Series, enter the following at the TL1 command line interface: ACT-USER:[TID]:<uid>:<CTAG>::<pid>;

where

TID is the target identifier (AccessWave Series is the default target identifier)

uid is the user identifier (admin is the default system administrator uid) CTAG is the correlation tag (100 is the default correlation tag) pid is the password identifier (admin is the default system administrator

pid). Note: User identifier “admin” and password identifier “admin” are the default system administrator credentials.

Example ACT-USER:AccessWave Series:admin:100::*****;

Response

The AccessWave Series sends back a COMPLD message to indicate a successful log on.




RS-232 Serial Communications The AccessWave Series system has a craft serial port that uses the RS-232 protocol.

Cables Required When connecting a PC or laptop to the craft serial port, use a straight-through RS-232 cable with a DB-9 pin male connector.

If you anticipate using the RS-232 serial port, determine the length of cable required to connect the AccessWave Series system to your PC, and prepare the cable with the appropriate male connector.

RS-232 Pin Assignment The following figure shows the RS-232 DB-9 pin DCE connector as well as the RS-232 RJ-45 8 pin connector and the associated pin numbering schemes.

Figure 4-5: DB-9 Pin Connector and 8 Pin RJ-45 Connector Numbering Schemes


Useful Procedures


The following table lists the RS-232 pin assignment for the DB-9 pin connector and RJ-45 connector pin numbering schemes.

Table 4-2: Pin Assignments for RS-232 DB-9 Pin Connectors and RS-232 RJ-45 Connectors

DB-9 Pin Connector

DCE Purpose RJ-45 Connector

DCE Purpose

1 Data Terminal Ready 1 Request to Send 2 Transmitted Data 2 Data Terminal Ready 3 Received Data 3 Transmitted Data 4 DTE Ready 4 Signal Ground 5 Signal Ground 5 Signal Ground 6 DCE Ready 6 Received Data 7 Clear to Send 7 Data Carrier Detect / Data

Set Ready 8 Request to Send 8 Clear to Send 9 Ring Detector


This section provides information about troubleshooting the issues that might arise when upgrading from Release 7.2.1 to Release 7.3.1.

Checking Failures

CHK-SYS-UPGRD Failure when File is not found on FTP Server


A 17538 REPT EVT EQPT

"SCP-1-5:SYSCHKFAIL,,2008-04-29,08-46-46,,,,,:Check Upgrade Failure. Requested operation failed. No FTP file found.,,,:,"

;

CHK-SYS-UPGRD Failure when FTP Server is not Found



"SCP-1-5:SYSCHKFAIL,,2008-04-29,08-49-15,,,,,:Check Upgrade Failure. Requested operation failed. FTP Server not available.,,,:,"

;

5 Troubleshooting

Troubleshooting AccessWave Series Upgrade Guide from V7.1.x or 7.2.1 to 7.3.1


CHK-SYS-UPGRD Failure when Inventory does not Match Load



"SCP-1-5:SYSCHKFAIL,,2008-04-30,08-47-25,,,,,:Check Upgrade Failure. Inventory does not match Load provided.,,,:," ;

CHK-SYS-UPGRD Failure when an Invalid Manifest File is Found



"SCP-1-5:SYSCHKFAIL,,2008-04-30,08-55-33,,,,,:Check Upgrade Failure. Invalid Manifest file found.,,,:,"

CHK-SYS-UPGRD Failure when an Invalid Username or Password is Found


A529 REPT EVT EQPT

"SCP-1-5:SYSCHKFAIL,,12-19,10-55-44,,,,,:\"Check Upgrade Failure. Invalid username or password.\",,,:," ;

CHK-SYS-UPGRD Failure when the Wrong FTP Server is Accessed


A516 REPT EVT EQPT

"SCP-1-5:SYSCHKFAIL,,12-19,10-42-00,,,,,:\"Check Upgrade Failure. Requested operation failed. Internal system fault. \",,,:,"

;

CHK-SYS-UPGRD Failure when the Wrong Path is Specified


A536 REPT EVT EQPT

"SCP-1-5:SYSLOADFAIL,,12-19,10-58-19,,,,,:\"Software Load Failed. File does not exists.\",,,:,"

;


Troubleshooting


CHK-SYS-UPGRD Failure when Another Load or CHK-SYS-UPGRD was Already Started


A524 REPT EVT EQPT

"SCP-1-5:SYSCHKFAIL,,12-19,10-50-08,,,,,:\"Check Upgrade Failure. Invalid Upgrade Sequence.\",,,:," ;

CHK-SYS-UPGRD Failure when Gateway is not Set and IP Address is Outside the IP-NMS Subnet


A9 REPT EVT EQPT

"SCP-1-5:SYSCHKFAIL,,12-19,13-37-26,,,,,:\"Check Upgrade Failure. No route to host.\",,,:,"

;

CHK-SYS-UPGRD Failure when you do not Have Read Permission on the FTP Server


A12 REPT EVT EQPT

"SCP-1-5:SYSCHKFAIL,,12-19,13-52-36,,,,,:\"Check Upgrade Failure. Permission denied.\",,,:,"

;



Loading Failures

LOAD-SYS-UPGRD Failure when a Handshake Failure to the FTP Server Occurs



"SCP-1-5:SYSLOADFAIL,,2003-04-29,08-58-25,,,,,:\"Software Load Failed.\"Requested operation failed. FTP Not Defined.,,,:," ;

LOAD-SYS-UPGRD Failure when File is not Found on FTP Server



"SCP-1-5:SYSLOADFAIL,,2003-04-29,08-58-25,,,,,:\"Software Load Failed.\"Requested operation failed. No FTP file found.,,,:," ;

LOAD-SYS-UPGRD Failure when FTP Server is not Found



"SCP-1-5:SYSLOADFAIL,,2003-04-29,08-59-03,,,,,:\"Software Load Failed.\"Requested operation failed. FTP Server not available.,,,:,"

;

LOAD-SYS-UPGRD failure when an invalid FTP server IP address is specified


M100 DENY

IDNV

/* Data not valid. Invalid Address. Error #2819. */

;

LOAD-SYS-UPGRD failure when valid but wrong IP address is specified and there is no answer from the remote node AccessWave Series 06-12-19 11:04:02

A537 REPT EVT EQPT

"SCP-1-5:SYSLOADFAIL,,12-19,11-04-01,,,,,:\"Software Load Failed. Connection to FTP server timed out.\",,,:," ;


Troubleshooting


LOAD-SYS-UPGRD Failure when there is no FTP Server Running on the Designated IP Address


A540 REPT EVT EQPT

"SCP-1-5:SYSCHKFAIL,,12-19,11-07-13,,,,,:\"Check Upgrade

Failure. FTP server not available, connection refused.\",,,:," ;

LOAD-SYS-UPGRD Failure when Trying to Load while a Load is in Progress



"SCP-1-5:SYSLOADFAIL,,2003-04-29,09-00-34,,,,,:\"Software Load Failed. \"Requested operation failed. Upgrade Load Process Already Started.,,,:,"

;

LOAD-SYS-UPGRD Failure when a Bad Load is Found



"SCP-1-5:SYSLOADFAIL,,2003-04-30,09-00-19,,,,,:\"Software Load Failed.\"Bad Load found.,,,:,"

;

LOAD-SYS-UPGRD Failure when the Invoke Process is in Progress



"SCP-1-5:SYSLOADFAIL,,2003-04-30,09-09-05,,,,,:\"Software Load Failed.\"Requested operation failed. Upgrade Load Process Already

Started.,,,:," ;



LOAD-SYS-UPGRD Failure when the Inactive Software Bank has Failed


A4 REPT EVT EQPT

"SCP-1-5:SYSLOADFAIL,,04-13,19-22-23,,,,,:\"Software Load Failed.

Unmapped error code.\",,,:,"

;

NOTE: See the “Alarm and Troubleshooting Guide” for information about replacing the SCP.

LOAD-SYS-UPGRD Failure when a Circuit Pack is Unknown or the Circuit Pack has Corrupted Inventory Data


A547 REPT EVT EQPT

"SCP-1-5:SYSLOADFAIL,,12-19,11-29-44,,,,,:\"Software Load Failed. Inventory does not match Load provided.\",,,:,"

;


Troubleshooting


Invoking Failure

TL1 Invoke Failure Messages When the INVK-SYS-UPGRD command is issued, the software image on the inactive memory bank becomes active. If the invoke process is unsuccessful, the system generates an event response message that indicates why the invoke has failed. Listed below are some examples.

INVK-SYS-UPGRD Failure when Alarms are Present on the System


M100 DENY

SNVS

/* Not in Valid State. System must be alarm-free. */

;

INVK-SYS-UPGRD Failure when the Release Number is Already Active


M100 DENY

SROF

/* Upgrade to Requested Release not possible. */

;

INVK-SYS-UPGRD Failure when the System Upgrade has Already been Invoked


M100 DENY

SROF

/* Requested operation failed. Command not allowed while upgrade invoke stage is in progress. */

;

or AccessWave Series 2008-02-31 19:03:44

M100 DENY

SROF

/* Requested Operation Failed. Upgrade In Progress. */

;



Recommended Actions for Failure Invoking 1. Check for file transfer problems:

If the error message Database Load Failed is returned, check to see if there has been a problem during the file transfer process. Check that the:

Filename is correct Correct IP address is entered FTP server is running Gateway on the FTP server is correct FTP server can communicate with the AccessWave Series by pinging the

AccessWave Series from the FTP server That the path is set correctly. Some UNIX FTP servers require the user to

specify the complete directory path of the file UNIX permissions are set to global read-write access There was no network interruption during the system upgrade or database

restore If no apparent reason can be found for the file transfer failure, contact your next level of support.

2. Check the Alarms to see if any alarms are present. See the applicable alarm clearing procedure for instructions to clear the alarm.

3. If an alarm is present and you want to proceed with the Invoke, check to see if the Ignore Alarms option in the Software Upgrade window, is enabled.

4. If you are using TL1, INVK-SYS-UPGRD command may be blocked. The following conditions cause the INVK-SYS-UPGRD command to be blocked:

If alarms are present in the system, the INVK-SYS-UPGRD command is blocked. Clear the alarms that are present and then proceed with the INVKSYS-UPGRD command.

If the system has already upgraded to the new product release, the INVK-SYS-UPGRD command is blocked. You cannot upgrade the system to the product release that the system is currently running.

If the INVK-SYS-UPGRD command has already been issued, or if an upgrade is already in progress, the INVK-SYS-UPGRD command is blocked. A subsequent INVK-SYS-UPGRD command cannot be issued before the upgrade is completed.

If there is an attempt to downgrade the system software, the INVK-SYS-UPGRD command is blocked. Contact your next level of support if you need assistance.

For the scenarios described above, wait for any ongoing commands to complete and then determine where you are in respect to the current system status. If you cannot determine what state the system is in, contact your next level of support.


Troubleshooting


Committing Failure

CMMT-SYS-UPGRD Failure when the Software has not Been Loaded or Invoked .AccessWave Series 2008-04-30 08:52:39

M100 DENY

SROF

/* Requested operation failed. Upgrade ProcessNot Started. */

;

Ensure that you have invoked the system upgrade before issuing the CMMT-SYS-UPGRD command.

Cancelling Failure

CANC-SYS-UPGRD Failure when an Invoke has not been Started AccessWave Series 2007-12-31 19:02:05

M100 DENY

SROF

/* Requested operation failed. Upgrade Process Not Started. */

;

CANC-SYS-UPGRD Failure when an Invoke is in Progress AccessWave Series 2007-12-31 09:27:38

M100 DENY SROF

/* Requested operation failed. Command not allowed while upgrade invoke stage is in progress. */

;



CANC-SYS-UPGRD Failure after Upgrade has Already been Cancelled AccessWave Series 2007-12-31 19:01:34 M100 DENY

SROF

/* Requested operation failed. Upgrade Process Not Started. */

;

Recommended Actions for Cancelling Failures

The following conditions can cause the CANC-SYS-UPGRD command to be blocked:

If the INVK-SYS-UPGRD command has not been issued, the CANC-SYS-UPGRD command is blocked. Issue the INVK-SYS-UPGRD command and wait for the invoke process to complete before issuing the CANC-SYS-UPGRD command.

If an invoke operation is in progress, the CANC-SYS-UPGRD command is blocked. Wait for the invoke process to complete and then issue the CANC-SYS-UPGRD command.

If the CANC-SYS-UPGRD command has already been issued, the CANC-SYS-UPGRD command is blocked. There is no need to issue the CANC-SYS-UPGRD command again.

If you are unable to cancel the upgrade or determine what state the system is in, contact your next level of support.

Provisioning Failure

ENT-EQPT Failure when a System Software Upgrade is in Progress When the ENT-EQPT command is issued during a system software upgrade, the system attempts to enter new provisioning parameters. With the a system software upgrade in progress, the system generates an event response message that indicates that the command is blocked. Listed below is an example. AccessWave Series 2003-04-30 09:10:19

M100 DENY

SROF

/* Command blocked due to current system access level. */

;

Wait for the a system software upgrade to complete before issuing a provisioning command.


Troubleshooting


Module Upgrade Failure The AccessWave Series confirms when all modules have been successfully upgraded to a new software release. If a module fails to upgrade properly, the system raises a Circuit Pack Upgrade Failure alarm (PACKUPGRDFAIL). This alarm indicates which module failed to upgrade.

NOTE: The module upgrade failure is not a service affecting condition. The module continues to run its original software and continues to process optical signals properly.

While the PACKUPGRDFAIL alarm is active, both alarm reporting and performance monitoring data collection are disabled.

If a module upgrade fails, contact ECI Telecom Support.Chapter 3, “Returning to an earlier version of the system software”

Database Recovery Failure When an SCP is replaced, the new SCP automatically acquires the provisioning database from an active module in the system. This simplifies the replacement process because a manual database restore operation is not required.

The AccessWave Series confirms when the SCP has successfully recovered the

database from the system. If the database is not recovered, a Database Recovery Failure alarm (DBRECVRYFAIL) is raised. In this situation, the database must be restored manually from a remote FTP server. For information about clearing this alarm, see the Alarm and Troubleshooting Guide.

Accesswave Series Upgrade Guide 7.1x or 7.2.1 to 7.3.1 a00 En

Documents

Transcript of Accesswave Series Upgrade Guide 7.1x or 7.2.1 to 7.3.1 a00 En