1. Check that circuit packs vintages are inspected.

Before upgr

Project mgr

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

Before upgr

Project mgr

3. Verify expansion interface compatibility for packet bus applications:

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

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



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 R9si.

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

5. 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

Proj mgr

6. 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.



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

Before upgr

Design spec

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

Before upgr

Tech or design spec

8. 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.



You can obtain downtime from QPPCNs.

Before upgr

Project mgr

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

Before upgr

Project mgr

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

Before upgr

Project mgr

11. 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

12. Provide translation information for the upgraded system.

Before upgr

Software specialist

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

Before upgr

Project mgr

1. Check that the software load version on the processor is the same as or higher than the version on the translation card.



(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

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

During upgr

Tech

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

After upgr

Software assoc