Avaya Meridian 1, 1000M, CS 1000M SG, CS 1000M MG Upgrade Manual
Communication Server 1000M and
Meridian 1
CS 1000M SG CP PIV to CS 1000M MG CP PIV FNF Upgrade
Avaya Communication Server 1000
Release 7.6
Document Status: Standard
Document Version: 06.02
Document Number: NN43021-466
Date: December 2013
© 2013 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 for 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 Products 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 i s 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 Toll
Fraud Intervention Hotline at +1-800-643-2353 for the United States and Canada. For additional support telephone numbers, see the Avaya
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
136
Page 4 of 159
Contents
New in this release . . . . . . . . . . . . . . . . . . . . . . . . . 6
Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Other . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Revision history .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Customer service . . . . . . . . . . . . . . . . . . . . . . . . . . 10
System information . . . . . . . . . . . . . . . . . . . . . . . . . 12
Subject .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Applicable systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Conventions .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Related information .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Preparing and planning for the upgrade . . . . . . . . 18
Contents .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Introduction .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Planning .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Avaya Communication Server 1000 task flow . . . . . . . . . . . . . . . . . . . 21
Upgrade Checklists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Preparing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Identifying the proper procedure .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Connect a terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Printing site data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
CS 1000M SG CP PIV to CS 1000M MG CP PIV FNF Upgrade
Page 5 of 159 Contents
Performing a template audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Backing up the database (data dump) .. . . . . . . . . . . . . . . . . . . . . . . . . 28
Making the RMD bootable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Performing the upgrade . . . . . . . . . . . . . . . . . . . . . 34
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Reviewing upgrade requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Upgrading Core 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Upgrading Core 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Making the system redundant .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Completing the CP PIV upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
lnstalling a Signaling Server . . . . . . . . . . . . . . . . . 106
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Introduction .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Signaling Server task flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Readiness checklist .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Server card hardware installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Upgrading and reconfiguring the software . . . . . . . . . . . . . . . . . . . . . . 134
Appendix A: Upgrade checklists . . . . . . . . . . . . . 148
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Introduction .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Site details .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Upgrade details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Preupgrade checklists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Preconversion steps .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Postconversion checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Quick reference .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
NN43021-466 Standard 06.02 December 2013
136
Page 6 of 159
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
December 2013
Standard 06.02. This document is up-issued to include the browser support
changes.
March 2013
Standard 06.01. This document is up-issued to support Avaya
Communication Server 1000 Release 7.6.
May 2012
Standard 05.05. This document is up-issued to include an update to single-slot
FIJI card vintages.
March 2012
Standard 05.04. This document is up-issued to include changes to the
Installing a Signaling Server chapter.
CS 1000M SG CP PIV to CS 1000M MG CP PIV FNF Upgrade
Page 7 of 159 New in this release
January 2011
Standard 05.03. This document is published to support Avaya
Communication 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 upissued to update the Avaya CS 1000M
task flow graphic and to include CP PM version 2 content.
June 2010
Standard 04.01. This document is upissued to support Avaya Communication
Server 1000 Release 7.0.
June 2009
Standard 03.03. This document is upissued to update the CP PM BIOS
upgrade procedure.
May 2009
Standard 03.02. This document is upissued to include task flow graphics for
Communication Server 1000 Release 6.0.
May 2009
Standard 03.01. This document is issued to support Communication Server
1000 Release 6.0.
November 2007
Standard 02.01. This document is issued to support Communication Server
1000 Release 5.5.
July 2007
Standard 01.02. This document is upissued with corrections for invoking the
install menu during CP PIV and CP P4 upgrades.
NN43021-466 Standard 06.02 December 2013
May 2007
May 2006
January 2006
August 2005
September 2004
October 2003
New in this release Page 8 of 159
Standard 01.01. This document is upissued for Communication Server 1000
Release 5.0. This document contains information previously contained in the
following legacy document, now retired: Communication Server 1000M and
Meridian 1 Large System Upgrades (553-3021-258).
Standard 5.00. This document is upissued with corrections for installing clock
controllers and keycode database 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.
Standard 1.00. This is a new document 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).
CS 1000M SG CP PIV to CS 1000M MG CP PIV FNF Upgrade
Page 9 of 159 New in this release
NN43021-466 Standard 06.02 December 2013
136
Page 10 of 159
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 10
• “Getting product training” on page 10
• “Getting help from a distributor or reseller” on page 11
• “Getting technical support from the Avaya Web site” on page 11
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.
CS 1000M SG CP PIV to CS 1000M MG CP PIV FNF Upgrade
Page 11 of 159 Customer service
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.
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-466 Standard 06.02 December 2013
136
Page 12 of 159
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 Release 7.6 on Meridian 1
Options 51C, 61C, 81C, Avaya Communication Server 1000M SG (Avaya
CS 1000M SG), and Avaya 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 Avaya’s
Software Conversion Lab. Consult the current Avaya
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
CS 1000M SG CP PIV to CS 1000M MG CP PIV FNF Upgrade
Page 13 of 159 System information
more information about legacy products and releases, click the
Documentation link under Support on the Avaya home page:
www.avaya.com
Applicable systems
This document applies to the following systems:
• Communication Server 1000M Single Group (CS 1000M SG)
• Communication Server 1000M Multi Grou p (CS 1000M MG)
• Meridian 1 Option 61C
• Meridian 1 Option 81C
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.
Table 1
Meridian 1 systems to Avaya 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
NN43021-466 Standard 06.02 December 2013
• Common Processor Dual Core (CP DC)
• Commercial off-the-shelf (COTS) Signaling Server
For more information, see “lnstalling a Signaling Server” on page 106.
Upgrade paths
This document contains information about the following Large System
upgrades:
• Meridian 1 Options 51C, 61C, 81C, 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
System information Page 14 of 159
Conventions
This document is intended for individuals responsible for upgrading
Large Systems.
This document is intended for individuals responsible for software
conversion and memory upgrades.
Terminology
The following systems are referred to generically as “Large System”:
• Communication Server 1000M Single Group (CS 1000M SG)
• Communication Server 1000M Multi Grou p (CS 1000M MG)
• Meridian 1 Option 51C
CS 1000M SG CP PIV to CS 1000M MG CP PIV FNF Upgrade
Page 15 of 159 System information
• Meridian 1 Option 61C
• Meridian 1 Option 81C
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
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 — 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.
CAUTION WITH ESDS DEVICES
To avoid damaging equipment from electrostatic
discharge, wear a properly connected antistatic wrist
strap when working on system equipment.
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.
NN43021-466 Standard 06.02 December 2013
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)
• Converging the Data Network with VoIP (NN43001-260)
• Circuit Card Reference (NN43001-311)
• Linux Platform Base and Applications Installation and Commissioning
System information Page 16 of 159
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.
(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)
• Software Input/Output: Maintenance (NN43001-711)
• Communication Server 1000M and Meridian 1 Large System Planning
and Engineering (NN43021-220)
• Communication Server 1000M and Meridian 1 Large System
Installation and Commissioning (NN43021-310)
CS 1000M SG CP PIV to CS 1000M MG CP PIV FNF Upgrade
Page 17 of 159 System information
• 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, click the Documentation link under
Support on the Avaya home page:
www.avaya.com
NN43021-466 Standard 06.02 December 2013
136
Page 18 of 159
Preparing and planning for the upgrade
Contents
This chapter contains the following topics:
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Avaya Communication Server 1000 task flow . . . . . . . . . . . . . . . . . . . 21
Upgrade Checklists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Preparing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Identifying the proper procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Connect a terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Printing site data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Performing a template audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Backing up the database (data dump) . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Making the RMD bootable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
CS 1000M SG CP PIV to CS 1000M MG CP PIV FNF Upgrade
Page 19 of 159 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:
Table 2
Prepare for upgrade steps
IMPORTANT!
Procedure Step Page
Planning 20
Upgrade Checklists 23
Preparing 23
Identifying the proper procedure 23
Connect a terminal 24
Printing site data 24
Performing a template audit 27
Backing up the database (data dump) 28
NN43021-466 Standard 06.02 December 2013
Planning
Preparing and planning for the upgrade Page 20 of 159
Planning for an upgrade involves the following tasks:
• Read and understand the current release Product Bulletin.
• Review the current release product bulletin related specifically to the
software being upgraded.
• Conduct a site inspection to determin e proper power and grounding.
• Review the site profile to determine proper foot space if adding new
columns or modules.
Note: For information about adding new network shelves, see
Communication Server 1000M and Meridian 1 Large System Installation
and Commissioning (NN43021-310).
• Ensure sufficient power for new columns/modules or applications.
• 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.
CS 1000M SG CP PIV to CS 1000M MG CP PIV FNF Upgrade
Page 21 of 159 Preparing and planning for the upgrade
Avaya Communication Server 1000 task flow
This section provides a high-level task flow for the installation or upgrade of
an Avaya Communication Server 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 1 on page 22:
• 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)
NN43021-466 Standard 06.02 December 2013
Preparing and planning for the upgrade Page 22 of 159
Figure 1
Communication Server 1000M task flow
CS 1000M SG CP PIV to CS 1000M MG CP PIV FNF Upgrade
Page 23 of 159 Preparing and planning for the upgrade
Upgrade Checklists
Upgrade checklists can be found in “Upgrade checklists” on page 148.
Engineers may print this section for reference during the upgrade.
Preparing
Preparing for an upgrade involves the following tasks:
• Identify and become familiar with all procedures.
• Verify that all installed applications me et the minimum software
requirements for the target platform (see Communication Server 1000M
and Meridian 1 Large System Planning and Engineering
(NN43021-220)).
• Verify proper cable lengths for the target platform.
• Determine and note current patch or Dep lists installed at the source
platform.
• Determine required patch or Dep lists at the target platform for
system-patchable components.
• Determine the required patches or DEP lists installed on applicable
applications.
• Determine and communicate the required maintenance window,
contingency plan and the impact to the customer to complete the
procedure.
• Perform an inventory on required software and hardware.
• Secure the source software and key code.
• Secure the target software and key code.
• Verify the new key code using the DKA program.
• Print site data.
Identifying the proper procedure
Each procedure has been written in a “source-to-target” format. Each
procedure features warning boxes and check boxes placed at critical points.
NN43021-466 Standard 06.02 December 2013
Changing the procedure or ignoring the warning boxes could cause longer
End of Procedure
service interruptions.
Connect a terminal
Procedure 1
Connecting a terminal
A maintenance terminal is required to access the Core or Core/Net modules
during the upgrade procedure.
1 Connect a terminal to the J25 port on the I/0 panel in the inactive Core or
Core/Net module.
2 The settings for the terminal are:
a. 9600 baud
b. 8 data
c. parity none
d. 1 stop bit
e. full duplex
f. XOFF
3 If only one terminal is used for both Core or Core/Net modules, the
terminal must be connected from side-to-side to access each module.
An “A/B” switch box can also be installed to switch the terminal from side
to side.
Preparing and planning for the upgrade Page 24 of 159
Printing site data
Print site data to preserve a record of the system configuration (see Table 3
on page 25). Verify that all information is correct. Make corrections as
necessary.
CS 1000M SG CP PIV to CS 1000M MG CP PIV FNF Upgrade
Page 25 of 159 Preparing and planning for the upgrade
Note: Items marked with an asterisk (*) are required. Other items are
recommended for a total system status.
Table 3
Print site data (Part 1 of 3)
Site data Print command
Terminal blocks for all TNs LD 20
REQ
TYPE
CUST
Directory Numbers LD 20
REQ
TYPE
CUST
Attendant Console data block for all customers LD 20 LD 20
REQ
TYPE
CUST
*Customer data block for all customers LD 21 LD 21
REQ
TYPE
CUST
Route data block for all customers LD 21
REQ
TYPE
CUST
ROUT
ACOD
PRT
TNB
<cr>
PRT
DNB
<cr>
PRT
ATT, 2250
<cr>
PRT
CDB
<cr>
PRT
RDB
Customer number
<cr>
<cr>
*Configuration Record LD 22
REQ
TYPE
NN43021-466 Standard 06.02 December 2013
PRT
CFN
Preparing and planning for the upgrade Page 26 of 159
Table 3
Print site data (Part 2 of 3)
Site data Print command
*Software packages LD 22
REQ
TYPE
*Software issue and tape ID LD 22
REQ
REQ
* Peripheral software versions LD 22
REQ
TYPE
ACD data block for all customers LD 23
REQ
TYPE
CUST
ACDN
Superloop card IDs and software version
(peripheral controller, superloop network and
controller cards)
Multi-purpose ISDN Signaling Processor
(MISP) card
LD 32
LD 27
REQ
TYPE
LOOP
APPL
PH
PRT
PKG
ISS
TID
PRT
PSWV
PRT
ACD
Customer Number
ACD DN (or <CR>)
IDC loop
PRT
MISP
loop number (0-158)
<cr>
<cr>
DTI/PRI data block for all customers LD 73
REQ
TYPE
CS 1000M SG CP PIV to CS 1000M MG CP PIV FNF Upgrade
PRT
DDB
Page 27 of 159 Preparing and planning for the upgrade
Table 3
Print site data (Part 3 of 3)
Site data Print command
Print the configured host information LD 117 PRT HOST (provides
system IP addresses)
Superloops and XPEs LD 97
REQ
TYPE
SUPL
Note: Items marked with asterisks (*) are required printout for conversion. Other items are
recommended for a total system status.
CHG
SUPL
Vxxx
V stands for a virtual
superloop and xxx is
the number of the
virtual superloop.
xxx = 0-252 in
multiples of four for
Avaya CS 1000 Media
Gateway 1000E
(Avaya MG 1000E)
Performing a template audit
A template audit (LD 01) reviews the templates in your system. Corrupted
and duplicate templates are cleaned up. An example of the information
generated during the audit is listed below.
Note: The template audit may take an extended period of time on large
systems. Run the audit during a low traffic period.
CAUTION — Service Interruption
Loss of Data
Do not abort this overlay until the audit is complete. If the
overlay is interrupted, data will be corrupted.
NN43021-466 Standard 06.02 December 2013
Preparing and planning for the upgrade Page 28 of 159
LD 01 The audit begins as soon as LD 01 is entered.
TEMPLATE AUDIT
STARTING PBX TEMPLATE SCAN
TEMPLATE 0001 USER COUNT LOW CHECKSUM OK
TEMPLATE 0002 USER COUNT HIGH CHECKSUM OK
TEMPLATE 0003 NO USERS FOUND
STARTING SL1 TEMPLATE SCAN
TEMPLATE 0001 USER COUNT OK CHECKSUM OK
•
•
TEMPLATE 0120 USER COUNT OK CHECKSUM OK
TEMPLATE AUDIT COMPLETE
Backing up the database (data dump)
To back up system data, perform a data dump to save all system memory to
the hard disk.
Procedure 2
Performing a data dump
1 Log into the system.
2 Load the Equipment Data Dump Program (LD 43). At the prompt, enter:
LD 43 Load program
3 When “EDD000” appears on the terminal, enter:
EDD Begin the data dump
CS 1000M SG CP PIV to CS 1000M MG CP PIV FNF Upgrade
Page 29 of 159 Preparing and planning for the upgrade
CAUTION — Service Interruption
Loss of Data
If the data dump does not succeed, do not continue.
Contact your technical support organization. You must
correct a data dump problem before the system can be
upgraded.
4 The messages “DATADUMP COMPLETE” and “DATABASE BACKUP
COMPLETE” will appear once the data dump is complete.
**** Exit program
5 Remove and label the floppy disk.
Preserve database backup information for a minimum of
5 days.
Making the RMD bootable
IMPORTANT!
CAUTION — Data Loss
The PC utility used in the following procedure
(mkbootrmd.exe) does not validate whether the drive
letter entered is a valid RMD CF card. You must enter
the correct RMD drive letter when prompted or risk
formatting the incorrect drive.
Note: This utility is supported by all versions of
Microsoft Windows.
The installation RMD CF card must come preformatted and bootable from
Avaya. Consumer CF cards are not bootable by default and must be made
bootable as outlined in Procedure 3 on page 30.
NN43021-466 Standard 06.02 December 2013
Figure 2
mkbootrmd.bat
Preparing and planning for the upgrade Page 30 of 159
Procedure 3
Making the RMD bootable
1 After downloading the software image file, unzip it to a directory on your
PC.
2 Open the utilities folder.
3 Double click the mkbootrmd.bat file. Insert a blank 512 MByte CF card
(see Figure 2).
CS 1000M SG CP PIV to CS 1000M MG CP PIV FNF Upgrade
Loading...