Avaya 1000M Upgrade
Avaya Communication Server 1000M and
Meridian 1 61C to CS 1000M SG CP PIV
Upgrade
Avaya Communication Server 1000M and Meridian 1
Release 7.6
Document Status: Standard
Document Version: 06.03
Document Number: NN43021-461
Date: June 2014
© 2014 Avaya Inc. All Rights Reserved.
Notice
While reasonable efforts have been made to ensure t hat the information in this document is complete and accurate at the time of printing,
Avaya assumes no liability for any errors. Avaya reserves the right to make changes and correction s to the information in this document
without the obligation to notify any person or organization of such changes.
Documentation disclaimer
“Documentation” means information published by Avaya in varyin g mediums which may include product information, operating instructions
and performance specifications that Avaya generally makes available to users of its products. Documentation does not include marketing
materials. Avaya shall not be responsible fo r any modifications, additions, or deletions to the original published version of documentation
unless such modifications, additions, or deletions were perf ormed by Avaya. End User agrees to indemnify and hold harmless Avaya,
Avaya's agents, servants and employees against all claims,
lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this
documentation, to the extent made by End User.
Link disclaimer
Avaya is not responsible for the contents or reliability of any linked websites referenced within this site or documentation provided by Avaya.
Avaya is not responsible for the accur acy of an y informat ion , st at ement o r con tent provid ed on the se sites an d do es not necessar ily endorse
the products, services, or information described or offered within them. Avaya does not guarantee that these links will work all the time and
has no control over the availability of the linked pages.
Warranty
Avaya provides a limited warranty on its hardware and Sof tware (“Product(s)”). Refer to your sales agreement to establish the terms of the
limited warranty. In addit i on, Avaya’s standard warranty language, as well as information regarding support for this Product while under
warranty is available to Avaya customers and other parties through the Avaya Support website:
http://support.avaya.com
Please note that if you acquired the Product(s) from an authorized Avaya reseller outside of the United States and Canada, the warranty is
provided to you by said Avaya reseller and not by Avaya. “Software” means computer programs in object code, provided by Avaya or an
Avaya Channel Partner, whether as stand-alone products or pre-installed on hardware products, and any upgrades, updates, bug fixes, or
modified versions thereto.
Licenses
THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE, HTTP://SUPPORT.AVAYA.COM/LICENSEINFO
APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC., ANY
AVAYA AFFILIATE, OR AN AUTHORIZED AVAYA RESELLER (AS APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH AVAYA
OR AN AUTHORIZED AVAYA RESELLER. UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOES NOT EXTEND
THIS LICENSE IF THE SOFTWARE WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE OR AN AVAYA
AUTHORIZED RESELLER; AVAYA RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSE USING OR
SELLING THE SOFTWARE WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR USING THE SOFTWARE, OR AUTHORIZING
OTHERS TO DO SO, YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE INSTALLING, DOWNLOADING OR
USING THE SOFTWARE (HEREINAFTER REFERRED TO INTERCHANGEABLY AS “YOU” AND “END USER”), AGREE TO THESE
TERMS AND CONDITIONS AND CREATE A BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THE APPLICABLE AVAYA
AFFILIATE ( “AVAYA”).
Heritage Nortel Software
“Heritage Nortel Software” means the software that was acquired by Avaya as part of its purchase of the Nortel Enterprise Solutions
Business in December 2009. The Heritage Nortel Software cu rrently avail able f or license f rom A v aya i s the software contained within the list
of Heritage Nortel Products located at http://support.avaya.com/licenseinfo
Software, Avaya grants Customer a license to use Heritage Nortel Software provided hereunder solely to the extent of the authorized
activation or authorized usage level, solely for the purpose specified in the Documentation, and solely as embedded in, for execution on, or
(in the event the applicable Documentation permits inst allation on non-A vaya equipment) fo r communication with A vaya equipmen t. Charges
for Heritage Nortel Software may be based on extent of activation or use authorized as specified in an order or invoice.
Copyright
Except where expressly stated otherwise, no use shoul d be made of materials on this site, the Documentation, Software, or hardware
provided by Avaya. All content on this site, the documentation and the Product provided by Avaya including the selection, arrangement and
design of the content is owned either by Avaya or its licenso rs and is protected by copyrigh t and ot her intellectua l propert y la ws in clud ing the
sui generis rights relating to the protection of databases. You may not modify, copy, reproduce, republish, upload, post, transmit or distribute
in any way any content, in whole or in part, including any code and software unless expressly authorized by Avaya. Unauthorized
reproduction, transmission, dissemination, storage, and or use withou t the express written consent of Avaya can be a criminal, as well as a
civil offense under the applicable law.
Third-party components
“Third Party Components” mean certain software programs or portions thereof included in the Software that may contain software (including
open source software) distributed under third party agreements (“Third Party Components”), which contain terms regarding the rights to use
under the link “Heritage Nortel Products”. For Heritage Nortel
ARE
certain portions of the Software (“Third Party Terms”). Information regarding distributed Linux OS source code (for those Prod u cts that have
distributed Linux OS source code) and identifying the copyright holders of the Third Party Components and the Third Party Terms that apply
is available in the Documentation or on Avaya’ s website at: http://support.avaya.com/Copyright
such Third Party Components.
Note to Service Provid e r
The Product may use Third Party Components that have Third Party Terms that do not allow hosting and may need to be independently
licensed for such purpose.
Preventing Toll Fraud
“Toll Fraud” is the unauthorized use of your telecommunications system by an unauthorized party (for example, a person who is not a
corporate employee, agent, subcontractor, or is not working on your company's behalf). Be aware that there can be a risk of Toll Fraud
associated with your system and that, if Toll Fraud occurs, it can result in substantial additional charges for your telecommunications
services.
Avaya Toll Fraud intervention
If you suspect that you are being victimized by Toll Fraud and you need technical assistance or support, call Technical Service Center T oll
Fraud Intervention Hotline at +1-800-643-2353 for the United States and Canada. For additional support telephone numbers, see the Av aya
Support website: http://support.avaya.com
mail to: securityalerts@avaya.com.
Trademarks
The trademarks, logos and service marks (“Marks”) displayed in this site, the Documentation and Product(s) provided by Avaya are the
registered or unregistered Marks of Avaya, its af filiates, or other third p arties. Users a re not per mitted to u se such Ma rks without p rior writte n
consent from Avaya or such third party which may own the Ma rk. No thing con tain ed in t his site, the Do cument ation and Pr oduct(s) should be
construed as granting, by implication, estoppel, or otherwise, any license or right in and to the Marks without the express written permission
of Avaya or the applicable third party.
Avaya is a registered trademark of Avaya Inc.
All non-Avaya trademarks are the property of their respective owners, and “Lin ux” i s a registered trademark of Linus Torvalds.
Downloading documents
For the most current versions of documentation, see the Av aya Support website:
http://support.avaya.com
Contact Avaya Support
See the Avaya Support website: http://support.avaya.com
For a list of support telephone numbers and contact addresses, go to the Avaya Support website: http://support.avaya.com
bottom of the page, and select Contact Avaya Supp ort.
.Suspected security vulnerabilities with Avaya products should be reported to Avaya by sending
for product notices and articles, or to report a problem with your Avaya product.
. You agree to the Third Party Terms for any
, scroll to the
Page 4 of 212
NN43021-461 Standard 06.03 June 2014
Contents
New in this release . . . . . . . . . . . . . . . . . . . . . . . . . 9
Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Other . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Customer service . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Navigation .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Getting technical documentation .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Getting product training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Getting help from a distributor or reseller .. . . . . . . . . . . . . . . . . . . . . . 13
Getting technical support from the Avaya Web site .. . . . . . . . . . . . . . 14
System information . . . . . . . . . . . . . . . . . . . . . . . . . 15
Subject .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Applicable systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Conventions .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Related information .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Contents .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Meridian 1 Option 61C upgrade to Option 61C CP PIV . . . . . . . . . . . 21
Preparing and planning for the upgrade . . . . . . . . 25
Contents .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Page 6 of 212 Contents
Introduction .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Avaya Communication Server 1000 task flow .. . . . . . . . . . . . . . . . . . 29
Upgrade Checklists .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Preparing .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Identifying the proper procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Connecting a terminal .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Checking the Core ID switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Printing site data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Performing a template audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Backing up the database (data dump and ABKO) . . . . . . . . . . . . . . . . 39
Making the RMD bootable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Transferring the database from floppy disk to CF
(customer database media converter tool) . . . . . . . . . . . . . . . . . . . . . . 45
Identifying two unique IP addresses .. . . . . . . . . . . . . . . . . . . . . . . . . . 51
Check requirements for CNI to 3PE cables (NTND14) .. . . . . . . . . . . 52
Performing the upgrade . . . . . . . . . . . . . . . . . . . . . 53
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Reviewing upgrade requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Installing Core 1 hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Installing Core 0 hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Making the system redundant .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Completing the CP PIV upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
lnstalling a Signaling Server . . . . . . . . . . . . . . . . . 157
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Introduction .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Signaling Server task flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Readiness checklist .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Server card hardware installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
NN43021-461 Standard 06.03 June 2014
Contents Page 7 of 212
Connections .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Upgrading and reconfiguring the software . . . . . . . . . . . . . . . . . . . . . . 185
Appendix A: Upgrade checklists . . . . . . . . . . . . . . 199
Contents .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Introduction .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Site details .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Upgrade details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Preupgrade checklists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Preconversion steps .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Postconversion checks .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Quick reference .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
61C to CS 1000M SG CP PIV Upgrade
Page 8 of 212 Contents
NN43021-461 Standard 06.03 June 2014
12
Page 9 of 212
New in this release
This chapter contains information about Avaya Communication Server 1000
(Avaya CS 1000) Release 7.6 new features.
Features
There are no updates to the feature descriptions in this document.
Other
See the following sections for information about changes that are not
feature-related:
Revision history
June 2014
December 2013
March 2013
June 2012
Standard 06.03. This document is up-issued to include the updated
description for the update dbs command.
Standard 06.02. This document is up-issued to include the browser support
changes.
Standard 06.01. This document is up-issued to support Avaya
Communication Server 1000 Release 7.6.
Standard 05.07. This document is up-issued to include updates to
QPC441GE5 jumper designation.
61C to CS 1000M SG CP PIV Upgrade
Page 10 of 212 New in this release
March 2012
Standard 05.06. This document is up-issued to include updates to the
Installing a Signaling Server chapter.
November 2011
Standard 05.05. This document is up-issued to remove legacy feature and
hardware content that is no longer applicable to or supported by
Communication Server 1000 systems.
October 2011
Standard 05.04. This document is up-issued to remove legacy feature and
hardware content that is no longer applicable to or supported by
Communication Server 1000 systems.
March 2011
Standard 05.03. This document is up-issued to support Avaya
Communications Server 1000 Release 7.5.
November 2010
Standard 05.02. This document is published to support Avaya
Communication Server 1000 Release 7.5.
November 2010
Standard 05.01. This document is issued to support Avaya Communication
Server 1000 Release 7.5.
June 2010
Standard 04.02. This document is up-issued to update the Avaya
Communication Server 1000M task flow graphic and to include CP PM
version 2 content.
June 2010
Standard 04.01. This document is up-issued to support Avaya
Communication Server 1000 Release 7.0.
June 2009
Standard 03.03. This document is up-issued to update the CP PM BIOS
upgrade procedure.
NN43021-461 Standard 06.03 June 2014
May 2009
May 2009
November 2007
July 2007
June 2007
May 2007
New in this release Page 11 of 212
Standard 03.02. This document is up-issued to include task flow graphics for
Communication Server 1000 Release 6.0.
Standard 03.01. This document is issued to support Communication Server
1000 Release 6.0.
Standard 02.01. This document is issued to support Communication Server
1000 Release 5.5.
Standard 01.03. This document is upissued with corrections for invoking the
installation menu during CP PIV and CP P4 upgrades.
Standard 01.02. This document is upissued with corrections to requirements
for CNI to 3PE cables.
Standard 01.01. This document is issued for Communication Server 1000
Release 5.0.
May 2006
January 2006
August 2005
September 2004
Standard 5.00. This document is upissued with corrections installing clock
controllers and keycode upgrade procedure for CP PIV.
Standard 4.00. This document is upissued with corrections to various upgrade
procedures.
Standard 3.00. This document is upissued to support CP PIV and
Communication Server 1000 Release 4.5.
Standard 2.00. This document is upissued for Communication Server 1000
Release 4.0.
61C to CS 1000M SG CP PIV Upgrade
Page 12 of 212 New in this release
October 2003
Standard 1.00. This document is new for Succession 3.0. It was created to
support a restructuring of the Documentation Library. This document
contains information previously contained in the following legacy
document,now retired: Upgraded Systems Installation: Upgrade to Options
51C, 61C,81C (553-3001-258).
NN43021-461 Standard 06.03 June 2014
14
Page 13 of 212
Customer service
Visit the Avaya Web site to access the complete range of services and support
that Avaya provides. Go to www.avaya.com or go to one of the pages listed
in the following sections.
Navigation
• “Getting technical documentation” on page 13
• “Getting product training” on page 13
• “Getting help from a distributor or reseller” on page 13
• “Getting technical support from the Avaya Web site” on page 1 4
Getting technical documentation
To download and print selected technical publications and release notes
directly from the Internet, go to www.avaya.com/support.
Getting product training
Ongoing product training is available. For more information or to register,
you can access the Web site at www.avaya.com/support. From this Web site,
you can locate the Training contacts link on the left-hand navigation pane.
Getting help from a distributor or reseller
If you purchased a service contract for your Avaya product from a distributor
or authorized reseller, contact the technical support staff for that distributor
or reseller for assistance.
61C to CS 1000M SG CP PIV Upgrade
Page 14 of 212 Customer service
Getting technical support from the Avaya Web site
The easiest and most effective way to get technical support for Avaya
products is from the Avaya Technical Support Web site at www.avaya.com/
support.
NN43021-461 Standard 06.03 June 2014
20
Page 15 of 212
System information
This document is a global document. Contact your system supplier or your
Avaya representative to verify that the hardware and software described is
supported in your area.
Subject
Use this document to perform upgrades on Meridian 1 Large Syste ms. This
document also contains information about database transfers, Call Processor
card upgrades, and network group upgrades.
This document also contains information about converting Release 3.0 or
later software to Avaya Communication Server 1000 (Avaya CS 1000)
Release 7.6 on Meridian 1 Options 61C, CS 1000M SG and CS 1000M MG
systems. For software conversion procedures prior to Release 3.0, see the
Software conversion procedures (553-2001-320) document for software
Release 24.
IMPORTANT!
Database conversion for Meridian 1 Options 21E, 51, 61,
71, STE, NT, and XT must be completed by
Software Conversion Lab. Consult the current
price book for cost and contact information.
Note on legacy products and releases
This document contains information about systems, components, and features
that are compatible with Avaya Communication Server 1000 software. For
61C to CS 1000M SG CP PIV Upgrade
Avaya’s
Avaya
Page 16 of 212 System information
more information about legacy products and releases, go to Avaya home
page:
www.avaya.com
Applicable systems
This document applies to the following systems:
• Avaya Communication Server 1000M Single Group (CS 1000M SG)
• Avaya Communication Server 1000M Multi Group (CS 1000M MG)
• Meridian 1 Option 61C
Note: When upgrading software, memory upgrades may be required on
the Signaling Server, the Call Server, or both.
System migration
When particular Meridian 1 systems are upgraded to run CS 1000
Release 7.5 software and configured to include a Signaling Server, they
become CS 1000M systems. Table 1 lists each Meridian 1 system that
supports an upgrade path to a CS 1000M system.
Tab le 1
Meridian 1 systems to CS 1000M systems
This Meridian 1 system... Maps to this CS 1000M system
Meridian 1 Option 61C CS 1000M Single Gro up
Meridian 1 Option 81C CS 1000M Multi Group
Signaling Server configuration
Meridian 1 Large Systems can be configured to run one or more Signaling
Servers. The following Signaling Servers are supported in a Large System
configuration for CS 1000 Release 7.5:
• CP PM Signaling Server
• Common Processor Dual Core (CP DC)
NN43021-461 Standard 06.03 June 2014
• Commercial off-the-shelf (COTS) Signaling Server
For more information, see “lnstalling a Signaling Server” on page 157.
Upgrade paths
This document contains information about the following Large System
upgrades:
• Meridian 1 Options 61C, CS 1000M SG, and CS 1000M MG
• upgrades to FNF
• software upgrades
• network additions
The upgrades documented in this document are structured as source platform
to target platform upgrades.
Intended audience
This document is intended for individuals responsible for upgrading
Large Systems.
System information Page 17 of 212
Conventions
This document is intended for individuals responsible for software
conversion and memory upgrades.
Terminology
The following systems are referred to generically as “Large System”:
• Avaya Communication Server 1000M Single Group (CS 1000M SG)
• Avaya Communication Server 1000M Multi Group (CS 1000M MG)
• Meridian 1 Option 51C
• Meridian 1 Option 61C
61C to CS 1000M SG CP PIV Upgrade
Page 18 of 212 System information
• Meridian 1 Option 81C
• Commercial off-the-shelf (COTS) servers
— IBM x306m server (COTS1)
— HP DL320 G4 server (COTS1)
— IBM x3350 server (COTS2)
— Dell R300 server (COTS2)
In this document, the generic term COTS refers to all COTS servers. The term
COTS1 or COTS2 refers to the specific servers in the preceding list.
The Common Processor Pentium Mobile, Common Processor Dual Core (CP
DC), and Commercial off-the-Shelf (COTS) platforms are referred to as
server.
Related information
CAUTION — Data Loss
Only personnel who are familiar with the system and with
conversion procedures should perform the conversion.
Read the applicable procedures carefully before
beginning any the conversion.
Note: Converting software on single CPU systems disrupts call
processing and allows service only to those telephones connected to
Power Failure Transfer Units (PFTU).
CAUTION WITH ESDS DEVICES
To avoid damaging equipment from electrostatic
discharge, wear a properly connected antistatic wrist
strap when working on system equipment.
NN43021-461 Standard 06.03 June 2014
Perform pre-conversion and postconversion procedures for every system
conversion.
Throughout this document the term media refers to tape, disk, CD-ROM or
Compact Flash (CF), whichever applies to the system.
The term source refers to the hardware and software that is currently running.
The term target refers to the new hardware and software to which the system
is converting.
Documents
The following documents are referenced in this document:
• Product Compatibility (NN43001-256)
System information Page 19 of 212
CAUTION — Data Loss
Read “General software conversion information” in
CS 1000M and Meridian 1 Large System Upgrades
Overview (NN43021-458) before performing any
operations.
It contains information vital to the conversion process.
• Converging the Data Network with VoIP (NN43001-260)
• Circuit Card Reference (NN43001-311)
• Linux Platform Base and Applications Installation and Commissioning
(NN43001-315)
• IP Peer Networking Installation and Commissioning (NN43001-313)
• Features and Services (NN43001-106)
• Software Input/Output: Administration (NN43001-611)
• Element Manager System Reference - Administration (NN43001-632)
• IP Trunk: Description, Installation, and Operation (NN43001-563)
• Signaling Server IP Line Applications Fundamentals (NN3001-125)
• ISDN Basic Rate Interface: Features (NN43001-580)
61C to CS 1000M SG CP PIV Upgrade
Page 20 of 212 System information
• Software Input/Output: Maintenance (NN43001-711)
• Communication Server 1000M and Meridian 1 Large System Plann ing
and Engineering (NN43021-220)
• Communication Server 1000M and Meridian 1 Large System
Installation and Commissioning (NN43021-310)
• Communication Server 1000M and Meridian 1 Large System
Maintenance (NN43021-700)
• Communication Server 1000M and Meridian 1 Large System Upgrade
NTPs (NN43021-458 to NN43021-474)
Online
To access Avaya documentation online, go to Avaya home page:
www.avaya.com
NN43021-461 Standard 06.03 June 2014
24
Page 21 of 212
Introduction
Contents
This chapter contains the following topics:
Meridian 1 Option 61C upgrade to Option 61C CP PIV . . . . . . . . . . . 21
Meridian 1 Option 61C upgrade to Option 61C CP PIV
This document provides instructions for upgrading a source Meridian 1
Option 61C CP3, CP4 to a target platform of Meridian 1 Option 61C CP PIV.
The procedures in this section are written for a stacked configuration (Core/
Net 1 on top of Core/Net 0).
Note: For side-by-side configuration, additional equipment such as the
pedestal, top cap, shelf spacers, or NT4N41 module, and XSM cables
must be ordered separately. This equipment must be installed before
attempting this upgrade. All existing cables in Core/Net 1 must be
checked for proper length and routing to the new configuration.
Please see Communication Server 1000M and Meridian 1 Large System
Installation and Commissioning (NN43021-310) for instructions on how to
install a column.
Procedures are written with the intent to maintain partial service. The service
interruption will cause half the system to be down during most of the
procedure. Some thought should be given to a complete power down
hardware replacement process.
61C to CS 1000M SG CP PIV Upgrade
Page 22 of 212 Introduction
UEM
UEM
Core/Net 0
(replace UNIT with
CP card cage)
553-????
UEM
UEM
UEM
Core/Net 1
(replace UNIT with
CP card cage)
Figure 1 on page 22 shows an upgrad e from a Meridian 1 Opti on 61C to a
stacked Meridian 1 Option 61C CP PIV.
Figure 2 on page 23 shows an upgrad e from a Meridian 1 Opti on 61C to a
side-by-side Meridian 1 Option 61C CP PIV.
DANGER OF ELECTRIC SHOCK
In a DC-powered system, power to the column can
remain on during the following procedures. In an
AC-powered system, however, power to the entire
column must be shut down throughout the procedures.
Figure 1
Meridian 1 Option 61C to Meridian 1 Option 61C CP PIV stacked
NN43021-461 Standard 06.03 June 2014
Introduction Page 23 of 212
UEM
UEM
Core/Net 1
(replace UNIT with
CP card cage)
UEM
UEM
UEM
Core/Net 0
(replace UNIT with
CP card cage)
Figure 2
Meridian 1 Option 61C to Meridian 1 Option 61C CP PIV side-by-side
This upgrade takes a Meridian 1 Option 61C to a single-group Meridian 1
Option 61C with CP PIV. CP PIV cards are located in the Core/Net modules
or card cage (see Figure 3 on page 24).
• The card cages in the existing Core/Net modules are replaced with
NT4N40 CP card cages.
• Existing network cards are relocated to the NT4N40 CP card cage.
• The existing Clock Controllers are moved from the old Core/Net to the
CP PIV Core/Net in slot 9.
• An IPE module can be installed on top of CP PIV Core/Net 0 module.
61C to CS 1000M SG CP PIV Upgrade
Page 24 of 212 Introduction
PS
Net
NT8D17 Conference/TDS Card
NT8D04 Superloop Network Card
NT8D04 Superloop Network Card
NT8D04 Superloop Network Card
QPC43R Peripheral Signaling Card
QPC441 3-Port Extender Card
NTRB53 CIock Controller card
PS 01234567891011
SYS
UTIL
L
LAN 1
U
USB
CF
PWR
HDD
INIT
RESET
cCNI
A
B
Enb
Dis
L
LAN 2
CP
PIV
Core
C
COM 1
C
COM 2
Enb
Dis
c9 c10 c11c12 c13c14 c15 CP
Figure 3
NT4N41 CP Core/Net Module
Upgrading to Avaya Communication Server 1000M
The upgrade to Avaya CS 1000M (installing a Signaling Server) occurs after
completing the procedures in this section. See “lnstalling a Signaling Server”
on page 157.
NN43021-461 Standard 06.03 June 2014
52
Page 25 of 212
Preparing and planning for the upgrade
Contents
This chapter contains the following topics:
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Avaya Communication Server 1000 task flow . . . . . . . . . . . . . . . . . . . 29
Upgrade Checklists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Preparing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Identifying the proper procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Connecting a terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Checking the Core ID switches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Printing site data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Performing a template audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Backing up the database (data dump and ABKO) . . . . . . . . . . . . . . . . 39
Making the RMD bootable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Transferring the database from floppy disk to CF (customer database media
converter tool). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Identifying two unique IP addresses. . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Check requirements for CNI to 3PE cables (NTND14) . . . . . . . . . . . . 52
61C to CS 1000M SG CP PIV Upgrade
Page 26 of 212 Preparing and planning for the upgrade
Introduction
This document implements a “source- to-target” approach to performing an
upgrade. It is important to correctly identify the source platform, target
platform, and maintenance window required to perform the upgrade.
This upgrade requires that the PC you are working from is
equipped with a floppy disk drive and CF reader (or, if a
CF reader is not available, a PCMCIA CF adaptor).
Each section features check boxes indicating what state the system should be
in at that stage of the upgrade. If the system is not in the proper state steps
should be taken to correct this.
Each section is written to maintain Dial Tone where possible and limit service
interruptions.
Before attempting any software or hardware upgrade field personnel should
follow the steps in Table 2:
Tab le 2
Prepare for upgrade steps (Part 1 of 2)
IMPORTANT!
Procedure Step Page
Planning 27
Upgrade Checklists 31
Preparing 31
Identifying the proper procedure 31
Connecting a terminal 32
Checking the Core ID switches 33
Printing site data 35
Performing a template audit 38
NN43021-461 Standard 06.03 June 2014
Preparing and planning for the upgrade Page 27 of 212
Tab le 2
Prepare for upgrade steps (Part 2 of 2)
Procedure Step Page
Backing up the database (data dump and ABKO) 39
Planning
Transferring the database from floppy disk to CF (customer
database media converter tool)
Identifying two unique IP addresses 51
45
Database requirements
If the system is running prerelease 3.0 software or the source platform is a
Meridian 1 Option 21E, 51, 61, 71, STE, NT or XT, the database must be sent
to Avaya for conversion.
If the source platform is a Meridian 1 Option 51C, 61C, 81, or 81C equipped
with IOP/CMDU cards, the database must be converted with the Database
Transfer utility. See “Converting the 4 MByte database media to 2 MByte
database media” on page 42.
If the source platform is a Meridian 1 Option 51C, 61C, 81, or 81C equipped
with IODUC cards, the database should be data dumped (EDD) to a blank
2 MB floppy.
Note: All of the above listed system types can be converted by Avaya in
the software conversion lab. Please check the current price manual for
the requirements of this service.
Planning for an upgrade involves the following tasks:
• Read and understand the current release Product Bulletin.
• Conduct a site inspection to determine proper power and grounding.
• Review the site profile to determine proper foot space if adding new
columns or modules.
• Ensure sufficient power for new columns/modules or applications.
61C to CS 1000M SG CP PIV Upgrade
Page 28 of 212 Preparing and planning for the upgrade
• Identify all applications that are currently installed on the source
platform.
• Identify and correct outstanding service problems.
• Verify the site log is updated with current trunking, call routing,
application notes, and site contact information.
• Review all product bulletins and Avaya Alerts that impact the site.
• Determine if software can be converted on site or must be sent to Avaya.
• Prepare a contingency plan for backing out of the upgrade.
DANGER OF ELECTRIC SHOCK
In a DC-powered system, power to the column can
remain on during the following procedures. In an
AC-powered system, however, power to the entire
column must be shut down throughout the procedures.
NN43021-461 Standard 06.03 June 2014
Preparing and planning for the upgrade Page 29 of 212
Avaya Communication Server 1000 task flow
This section provides a high-level task flow for the installation or upgrade of
an Avaya CommunicationServer (Avaya CS 1000) system. The task flow
indicates the recommended sequence of events to follow when configuring a
system and provides the document number that contains the detailed
procedures required for the task.
For more information refer to the following documents, which are referenced
in Figure 4 on page 30:
• Linux Platform Base and Applications Installation and Commissioning
(NN43001-315)
• Communication Server 1000M and Meridian 1 Large System
Installation and Commissioning (NN43021-310)
• CS 1000M and Meridian 1 Large System Upgrades Overview
(NN43021-458)
61C to CS 1000M SG CP PIV Upgrade
Page 30 of 212 Preparing and planning for the upgrade
Figure 4
Avaya Communication Server 1000M task flow
NN43021-461 Standard 06.03 June 2014
Loading...