Upgrade Instructions
Upgrade Paths
The following table describes the tested upgrade paths.
Please note that here x and y refer to the following.
•x: Latest maintenance release version.
•y: Any previous release older than latest release.
|
Upgrade From |
Qualified |
Compatible |
|---|---|---|
|
9.1Rx |
Yes |
- |
|
9.1Ry |
Yes |
|
|
9.0Rx |
Yes |
|
|
9.0Ry |
Yes |
|
|
5.4Rx |
Yes |
|
|
5.4Ry |
Yes |
- For versions prior to 5.4, first upgrade to release 5.4Rx|5.4Ry, then to 9.0Rx|9.0Ry, and then upgrade to 9.1Rx.
- If your system is running beta software, roll back to the previously installed official software release before upgrading. This practice ensures the rollback version is a release suitable for production.
- On a IPS virtual appliance, we highly recommend to freshly deploy a PSA-V from 5.4Rx based OVF, when any of the following conditions are met:
-- If the disk utilization goes beyond 85%.
-- If an admin receives iveDiskNearlyFull SNMP Trap.
-- If the factory reset version on the PSA-V is 5.x.
Upgrade Scenario Specific to Virtual Appliances
PSA-V cannot be upgraded to current release without core license.
Follow these steps to upgrade to the current release:
1.If PSA-V is running 5.4Rx:
•Upgrade to 9.0Rx.
•Install Core license through Authcode.
•Upgrade to 9.1Rx.
2.If PSA-V is running 9.0Rx or later:
•Install Core license through Authcode.
•Upgrade to 9.1R11.