DEFINITY Made Easy Home Page Table of contents Previous page Next page Index Links Frequently asked questions
Go to Upgrades for si Go to Installation for MCC Go to Installation for SCC

Made Easy Tool for DEFINITY Media Server Configurations
Issue 5, October 2002



Upgrades to Avaya MultiVantageTM Software Made Easy

Before you start

The project manager, sales engineer, software specialist, software associate, and technician all have tasks that precede the upgrade. They must review and complete the preparation and process steps well in advance of the upgrade.

To prevent the most common upgrade problems, be sure that you have

Preparation and process steps

If the system includes TN750 or TN750B announcement packs, discuss with the customer whether they are willing to re-record announcements. Doing so can significantly reduce the time it takes to do the upgrade. Every save announcements or restore announcements command can add up to 45 minutes to the upgrade process. Note that you do not have to save and restore announcements on systems with only TN750C or TN2501AP announcement circuit packs.


Caution! You cannot resolve any upgrade problems without a valid craft or dadmin login and password. You may have to contact Avaya before or during the upgrade to get the dadmin password, and you may have to have ASG keys to use craft remotely.

For customers without an Avaya maintenance contract, the INADS database does not have a record of passwords. Discuss with the customer who is responsible for making the passwords available.

This information in these tables applies to all upgrades. Complete the work in the Upgrade preparation steps table before the upgrade. Use the Upgrade process steps table during the upgrade.

.

Upgrade preparation steps
What
When
Who
  1. Check that circuit packs vintages are inspected.

Before upgr

Project Mgr

  1. Check that all adjunct versions are compatible with the new switch version.

Before upgr

Project Mgr

  1. Verify expansion interface compatibility for packet bus applications:

    2. If the new system will have one or more expansion port network cabinets and will run any packet applications, do not reuse the TN776 expansion interface circuit packs; they must be replaced with TN570 circuit packs.

Before upgr

Project Mgr

  1. Identify proper TDM/LAN bus cables and terminators for the system.

    2. If PACCON is not currently enabled, the cables and terminators may need to be replaced for V3 and later si systems, R5/R6vs systems, and SRPs upgrading to Avaya MultiVantageTM.

    Packet applications currently running in one port network do not guarantee that the system has the correct hardware. Adding a packet application to another network without verifying the TDM/LAN bus cables and terminators frequently causes upgrade problems.

    We recommend that you schedule a time to replace the cables and terminators before the upgrade. Note that this requires a service outage.

Before upgr

Project Mgr

  1. Check for software upgrade compatibility:

    • current software patches that will need to be re-applied

    • software upgrades that include all relevant bug fixes

Before upgr

Project Mgr

  1. Use the latest software QPPCN to check the vintages of all circuit packs that will be reused in the upgrade.

    1. Replace circuit packs that have unusable vintages.

    2. Make a final vintage check.

      3. For current information about usable vintages in a DEFINITY ECS system, see the Stockable, Minimum Usable Vintages, & Certifiable Vintages, COMPAS ID 42751.

Before upgr

Design Spec

  1. For blowback upgrades only: Make the Blowback Tape. The blowback tape is converted and written to removable media. This takes 2 weeks and must be done before the upgrade.

Before upgr

Tech or Design Spec

  1. Schedule the upgrade with the customer and inform the customer of a service interruption (total outage) during the upgrade. If it is not an Avaya-maintained customer, get password information.

    2. You can obtain downtime from QPPCNs.

Before upgr

Project Mgr

  1. Verify with the customer that they do not use any login ID subject to ASG challenge. The craft, inads, and init login IDs must respond to a challenge. If necessary, set the required permissions for the cust login ID.

Before upgr

Project Mgr

  1. If the system is pre-R8, verify that the customer does not have a dadmin login set to craft level. If they do, remove the login and re-add it as dadmin set to Inads level. After the upgrade this login will be dadmin at the dadmin service level.

Before upgr

Project Mgr

  1. Coordinate the service interruption with the local account team.

Before upgr

Project Mgr

  1. To preclude a busy-out of network access trunks at the far end, inform the support organization for each public and private network accessed by the switch at least one day before the scheduled upgrade.

Before upgr

Project Mgr

  1. Provide translation information for the upgraded system.

Before upgr

Software Specialist

  1. Check that the inventory, tools, hardware, project manager binder, translation information, and crash kit are at the customer site.

Before upgr

Project Mgr

  1. Complete RFA training and registration. Allow up to 48 hours before attempting to access RFA.

Before upgr

Tech, SS, SA, Project Mgr

  1. Create the license file in RFA

Before upgr

Tech, SS, SA, Project Mgr

Upgrade process steps
What
When
Who
  1. Check that the software load version on the processor is the same as or higher than the version on the translation card.

    2. (Use the list configuration software-version memory-resident command.)

    1. Compare the software load version on the processor with the version on the translation card.

    2. If the version on the processor is not the same as or higher than the version on the card, download the software load from the orange card that is included in the crash kit.

During upgr

Design Spec

  1. Use the procedures in this information product to do the upgrade.

During upgr

Tech

  1. Verify that the translations are correct for the upgraded system. Make the needed changes.

After upgr

Software Assoc

Make the Blowback Tape

To upload the translations remotely, contact the CSA. If you choose to make a blowback tape, follow this procedure:


Note: There must always be 2 system tapes on site with the DEFINITY system. Do not send the system or backup tape to the CSA.

  1. Get a blank R1V3 tape from the regional CSA. This will be the blowback tape.

  2. Remove the backup tape, install the blowback tape, and wait for the tape to retension.


Note: The off-site CSA translation upgrade does not preserve the contents of recorded announcements on TN750/B or earlier circuit packs. Therefore, if a TN750/B or earlier circuit pack resides in the stack of single-carrier cabinets which is dismantled during the upgrade, any announcements stored on the circuit pack must be rerecorded.

  1. Enter save translation. Press RETURN.

  2. Remove the blowback tape and label it with IL information (customer name and customer contact).

  3. Reinstall the system tape.

  4. Use next-day delivery to mail the blowback tape to the CSA for use in making the translation memory cards for the upgrade.

Blowback vs. On site?

A blowback is an off-site replication and upgrade to the target release. You must schedule blowback upgrades in advance with the organization performing the software blowback.

Blowback upgrades are preferred over on site upgrades that require multiple-step hardware/software interim configurations. Although multiple-step on site upgrades are technically feasible, they require multiple-step hardware and software upgrades, which cause extended customer outages. They also require additional hardware to upgrade to the interim configurations prior to final required configuration.

Bottom line: on site multiple-step upgrades are normally not the way to go!

Upgrade
Considerations

R1 V3 and System 75

An on site upgrade is impractical for almost all upgrades of this type. This upgrade requires a blowback.

G1, G3i V1, G3s V1

Blowbacks are preferred. Although we have the capability to perform these upgrades on site, such upgrades are less desirable due to extensive down time or are not practical for other reasons.

G3iV1.1, G3iV2, G3iV3, G3iV4


G3s V1.1, G3s V2, G3s V3, G3s V4

On site or blowback upgrades can be performed. Considerations in selecting the upgrade method include the amount and complexity of any associated translation work related to -- or done in conjunction with -- the upgrade.

These upgrades require none of the multi-step interim procedures of the G1, G3i V1 or G3s V1 upgrades.

G3vs (V1 - R5/6)

All hardware must be replaced; the G3vs hardware is supported only through R6. Existing translations can be carried forward to the upgraded hardware and software.

What DEFINITY System Is This?

The table below will tell you what system you have based on Processor Board, Cabinet, and some other criteria. Click the link for the system type to proceed to the correct si upgrade procedure.

If the existing Processor Board is:
AND
Then this link takes you to this si upgrade:

TN786 or TN786B

The cabinet is wall-mounted with no CPP1 board and no slot on the carrier for a CPP1 board

G3V4vs/R5vs/R6vs to Avaya MultiVantageTM Software
(includes G3vs versions V1, V2, V3, or V4)

TN790 or TN790B

The cabinet is wall-mounted with no CPP1 board and no slot on the carrier label for a CPP1 board.

G3V4vs/R5vs/R6vs to Avaya MultiVantageTM Software

TN786 or TN786B

plus a CPP1 Memory Card

G3iV4 to Avaya MultiVantageTM Software

TN790 or TN790B

 

R5/R6/R7/R8si to Avaya MultiVantageTM Software

TN798 or TN798B

This type of upgrade is not covered in this documentation (Upgrades Made Easy)

DEFINITY Made Easy Home Page Table of contents Previous page Next page Index Links Frequently asked questions
Go to Upgrades for si Go to Installation for MCC Go to Installation for SCC
Copyright� 2002 Avaya Inc.
Send comments to MadeEasy Development Team



Always check at the Made Easy Web site for the most current information.