AppNeta Upgrade Options - Upcoming AppNeta SaaS migration
Article ID: 386885
Updated On:
Products
Issue/Introduction
We received an email regarding an AppNeta upgrade for our monitoring points, related to the Upcoming AppNeta SaaS Migration, and require more information.
Environment
All AppNeta SaaS portal monitoring points. Please note the following important dates:
November 4th, 2025: Legacy infrastructure is decommissioned. Please upgrade your Monitoring Points before this date.
Resolution
Additional details about the migration can be found here:
In short, all AppNeta monitoring points, container, and software clients need to be upgraded to version 16.x in order to ensure ongoing connectivity.
AppNeta upgrades can be performed in a variety of methods:
Upgrades are most often completed through through the AppNeta SaaS portal. We recommend ensuring the Upgrade Type is set to Managed (default setting) which will ensure the upgrades are automated when available.
- Managed (default) – Upgrades are to be performed automatically when new software is released. This enables you to have the latest software running at all times. The software upgrade schedule is listed on the AppNeta service status page: http://status.appneta.com/.
- Manual – Upgrades are to be performed manually (no automation).
- Scheduled – Upgrades are to be performed automatically on a regularly scheduled interval. This enables you to schedule upgrades during your regular network maintenance window. You also have the option of skipping the next upgrade.
If the upgrades are unable to complete through the SaaS portal, a common cause is that the upgrade repository may be unreachable. This is a common reason to the issue, and may require firewall changes. Depending on your organization’s network, you may need to make changes to your firewall to ensure that your new Monitoring Points can connect to your AppNeta instance. Please see the Firewall Configuration page for more information on configuring your firewall.
| In/Out | Protocol | Port | Address | Comment |
| Out | TCP | 443 | *.pm.appneta.com | This is the recommended address to permit. If you restrict outbound 443, we recommended that you allow *.pm.appneta.com. |
|
|
If you are not able to allow *.pm.appneta.com, you can allow the following individual endpoints instead: the low latency communications (comms.pm.appneta.com), data upload (data.pm.appneta.com), content download (content.pm.appneta.com), appliance upgrade (appliance-repo.pm.appneta.com), and native Monitoring Point (nmp.pm.appneta.com) endpoints. | |||
| Out | TCP |
443 |
app-xx.pm.appneta.com | Based upon your App-xx server that you use in your deployment |
| Out | TCP | 443 | data.pm.appneta.com | |
| Out | TCP | 443 | content.pm.appneta.com | |
| Out | TCP | 443 | comms.pm.appneta.com | |
| Out | TCP | 443 | appliance-repo.pm.appneta.com | |
| Out | TCP | 443 | nmp.pm.appneta.com |
Additional methods can be used:
- Upgrades using USB
- Upgrades through API
- Upgrades through SSH / CLI
As needed, please open a support ticket should you require assistance with any upgrade.
Additional Information
Additional details about the migration can be found here:
Feedback
