Upgrade preparation steps |
What |
When |
Who |
- Check that circuit packs vintages are inspected.
|
Before upgr
|
Project Mgr
|
- Check that all adjunct versions are compatible with the new switch version.
|
Before upgr
|
Project Mgr
|
- 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
|
- 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 R10si.
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
|
- 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
|
- Use the latest software QPPCN to check the vintages of all circuit packs that will be reused in the upgrade.
- Replace circuit packs that have unusable vintages.
- 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
|
- For blowback upgrades only: Make the Blowback Tape. The blowback tape is converted and written to R10 removable media. This takes 2 weeks and must be done before the upgrade.
|
Before upgr
|
Tech or Design Spec
|
- 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
|
- 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
|
- 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
|
- Coordinate the service interruption with the local account team.
|
Before upgr
|
Project Mgr
|
- 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
|
- Provide translation information for the upgraded system.
|
Before upgr
|
Software Specialist
|
- Check that the inventory, tools, hardware, project manager binder, translation information, and crash kit are at the customer site.
|
Before upgr
|
Project Mgr
|
- Complete RFA training and registration. Allow up to 48 hours before attempting to access RFA.
|
Before upgr
|
Tech, SS, SA, Project Mgr
|
- Create the license file in RFA
|
Before upgr
|
Tech, SS, SA, Project Mgr
|