APPENDIX G: License Migration and Merge

Last Updated: June 26, 2008

NOTE: This document supersedes all previously published versions of this document.

NOTE: Any deviations from the policy must be approved in writing by the product manager or their delegate for the region before proceeding.

NOTE: The pricing in this document is based on Global List Pricing. For regional list prices please refer to your local price list for more information.

As Avaya releases new, more powerful servers and higher-capacity gateways, customers can consolidate their systems onto one server and recognize cost savings through centralized operation.

Customers that want to consolidate their separate systems first can migrate and upgrade an older DEFINITY system to an Avaya Server running Communication Manager 5.x. Then they can convert other DEFINITY cabinets to become port networks or media gateways connected to the server.

The policies and procedures contained within this document are designed to address these prevalent market needs through Migrations and Merges for Communication Manager and Call Center licenses.

Definitions

Upgrades: Upgrades bring forward the customer's Avaya Server to the latest release of Communication Manager software on the same main server type (i.e., S8300/G700 Communication Manager 3.1 to Communication Manager 5.x). Some upgrades require additional hardware or upgrades to existing hardware and some upgrades may require parallel upgrades on adjunct equipment. Upgrades are not directly addressed in this document: please refer to the Commun­ication Manager Offer Definition and product documentation.

Migrations: Migrations are the movement from one Avaya Server type to another (e.g., one G3R to one S8730). The customer chooses one sever to migrate from. Avaya provides special pricing and entitles the customer to all of their existing software licenses to be used on the new server.

Merges: Merges are the consolidation of either software licenses and/or port hardware from one or more main servers (the “From” servers) to another existing main server (the “To” server). The customer value proposition is cost savings through network consolidation - moving from multiple servers into one for the purposes of centralized administration. Usually, this means that a customer is choosing to decommission multiple PPN systems in favor of converting them into PNs off an already existing server. Merges occur after a Migration has taken place for S8730 or S8500 C or S8400 Servers.

License Moves: Moving licenses (ports and stations) is an integral part of merges and migrations. A companion document (Appendix H: License Moves) covers the policies and procedures used to move licenses from one system to another.

Positioning

Migrations and Merges usually should be positioned sequentially with customers. First a migration is done to replace older technology with a new S8XXX server. Then, after the migrated system is established and running, use the merge processes to centralize the operation and attach port networks in a distributed fashion.

Migration Offer Description

Migrations are the change from one server type to another (i.e., one G3R to one S8730). Avaya provides special pricing and entitles the customer to use all of their existing software licenses on the new server as long as the old switch is decommissioned and the processor is returned to Avaya.

The attached matrix describes the supported and non supported paths for main server, WAN Spare Processor (WSP), Survivable Remote Processor (SRP), Local Survivable Processor (LSP) and Enterprise Survivable Server (ESS) migration.

For supported paths that are not in ASD, please contact the ATAC for clarifications before proceeding with the migration.

Platform Identification Codes for Migrations

The R9 & prior migration codes will create a new system license with features and RTU coming from other materials and tracking codes on the order. The R10 and later migration codes simply change the platform type in the existing system license with current features and RTU preserved. The existing RFA SID remains the same.

The migration material codes shown below must only be applied to Communication Manager 5.x systems: they will not change the software version. If convenient, upgrade material can also appear on the same SAP order if you need to upgrade from previous versions.

The platform type shown in the material code name is the target platform type.

SAP CODE	DESCRIPTION	MPG	GPL
Migrations
207939	R9&PRIOR TO CM5 S8400 MIG SFTW LIC	DA	$0
207940	R10+ TO CM5 S8400 MIG SFTW LIC	DA	$0
207942	R9&PRIOR TO CM5 S87XX MIG SFTW LIC	DA	$0
207943	R10+ TO CM5 S87XX MIG SFTW LIC	DA	$0
208023	CM5 S8300 W/G700 MIG SFTW LIC	DA	$0
208024	CM5 S8300 W/G350 MIG SFTW LIC	DA	$0
207945	R9&PRIOR TO CM5 S8500 MIG SFTW LIC	DA	$0
207946	R10+ TO CM5 S8500 MIG SFTW LIC	DA	$0
211384	CM5 S8300 W/G350 LSP MIG SFTW LIC	DA	$0
211385	CM5 S8300 W/G700 LSP MIG SFTW LIC	DA	$0
211386	CM5 S8300 W/G450 LSP MIG SFTW LIC	DA	$0

Merge Offer Description:

A Merge is the consolidation of software licenses and/or port hardware from one or more main servers (the “From” server(s)) to another existing main server (the “To” server). The customer value proposition is cost savings through network and administrative con­sol­i­dation - reducing multiple servers into only one for centralized administration, to lower the cost of ownership, and to allow remote sites to use powerful features. Usually, this means that a customer is decommissioning multiple PPN systems to convert them into port networks or Media Gateways off an existing server. This usually happens after migrating an older system to an S8700 or S8500 server.

The difference between the License Move offer as described in Appendix H: License Moves and the Merge offer is simple: A merge moves all of the “FROM” system port and station licenses to the “TO” system, and the “FROM” system is decommissioned. Merges from multiple systems into one combined system are allowed by simply designing several license moves. This can also be done with one combined SAP order, if more convenient. If only some of the licenses are moved, then the process described in Appendix H should be used.

Please refer to Appendix H for all the details, processes, restrictions, and forms required to perform a license move in support of a Merge.

There must be at least 1 license on the target server prior to the merge.

Return of Old Processors

The customer must disable the “From” system within 30 days after the merge or migration has taken place by returning the old processor to Avaya (applicable to older DEFINITY systems only).

• For Distributors, this policy is in accordance with SECTION 11: Upgrades of the U. S. Indirect Channel Returns Policy dated January 1, 2003.

Existing System	Circuit Pack to return
Avaya DEFINITY Server R	UN332C MSSNET board
Avaya DEFINITY Server SI	TN2404 processor board or pre-R9 processor
Avaya DEFINTIY Server CSI	TN2402 processor board or pre-R9 processor

If you have equipment to return associated with an upgrade, please return via FedEx or UPS for non-bulk. If it is a bulk pick then please follow the Bulk/large pick up process. For the RMA# use the original Migration SAP order number you installed with.

• BusinessPartners should request a no charge return order through the Avaya BP CCC, using a reason code of ZRU. The correct material code of the processor must be given to the CCC when placing the order.

• The BusinessPartner or end customer packs and returns the processor, indicating the Return Material Authorization (RMA) number on the packing list/mailing label (freight paid by BusinessPartner or end customer) to:

Avaya

RMA #___________

7424 Scott Hamilton Drive

Little Rock, AR 72209

USA

Activation Fees

RFA activation fees will be charged for license moves in support of merges, and also for migration orders. Please refer to Appendix H: License Moves for more details.

Maintenance Affected by the Merge

If your customer's switch has maintenance, the merge of licensed stations and other RTU may affect maintenance billing. Please refer to Appendix H: License Moves for more details.

Contact Information

If you have questions on Communication Manager or related solution elements please contact ATAC on:

ATAC Contact Information:
North America Regional Access [e-mail] 1 720-444-7700 or 888-297-4700 Hours of Operation: 5:00am-8:00pm EST Monday-Friday	EMEA Regional Access [e-mail] 31 70 414 8099 Hours of Operation: 11:00am-7:00pm CET, Monday-Friday
CALA Regional Access [e-mail] 1 720-444-7700 or 888-297-4700 Hours of Operation: 5:00am-8:00pm EST Monday-Friday	APAC Regional Access [e-mail] 65 6872-2693 Hours of Operation: 9am SGD to 18:30 SGD

For RFA related issues, please contact the RFA Helpdesk at:

Phone: [phone] (US) or [phone] (Outside the US)

Email: [e-mail]

Communication Manager 5.1 Product Definition

Page 5 of 5 Avaya Inc. - Proprietary & Confidential. June 26, 2008

The information contained in this document can not be distributed

or reproduced in whole or in part without express written consent of Avaya Inc.

---