
• Virtual Provisioning System (VPS)
• IP Flow Manager (IPFM)
• Pod Utility Manager (PUM)
These applications are end of sale and end of support in Release 3.1.
Avaya Pod Fx upgrades to Release 3.1
Preexisting Avaya Pod Fx platforms can upgrade to Release 3.1 software. The following software
upgrade scenarios are supported:
• One step upgrade path for all Avaya Pod Fx platforms from Release 2.0.1, 2.1.1, 3.0, 3.0.1, or
3.0.2 to Release 3.1.
Important:
The Avaya Pod Utility Module has been removed from the Management Server Console
software in Release 3.1. All upgrades are now conducted using the procedures documented in
Using the Management Server Console for Avaya Pod Fx
(NN47204–303).
Avaya Pod Fx upgrades must be performed by Avaya Professional Services, or an Avaya Pod Fx
Select certified Business Partner. They must plan and prepare to perform the upgrades, such as
downloading and transferring all the upgrade files required before starting any component upgrades.
To perform an Avaya Pod Fx upgrade, update the following components to the Release 3.1 software
baseline:
• Avaya Aura
®
System Manager
• Avaya Pod Orchestration Suite (POS) software
• VMware vCenter and ESXi software
• Avaya network switches software and firmware
• EMC storage array software and firmware
• HPE Nimble storage array software and firmware
• HPE or Lenovo compute servers BIOS and firmware
• ServerTech Power Distribution Unit (PDU) firmware
• Remove Unisphere Remote and deploy Unisphere Central if applicable
Warning:
Avaya Pod Fx Release 3.1 requires an Avaya Aura 7.1 System Manager. Before performing any
upgrades, verify if your existing solution applications are supported on Avaya Aura 7.1 using the
product compatibility matrix available at
https://secureservices.avaya.com/compatibility-matrix/
.
You can upgrade ACM, and ANAV to the xCaaS 2.0 supported versions before performing an
upgrade of the Avaya Pod Fx infrastructure to Release 3.1.
New in this document
October 2017
Troubleshooting the Avaya Pod Fx
™
10