Update for: m25, m35, m50, m70, r45, r90, r1000, and v35
Release notes for Enterprise Monitoring Point version 12.2.0.
- Change r90 Usage interface to Delivery/Experience—Port 3 on the r90 can now be converted from Usage monitoring to Delivery and Experience monitoring. This provides an additional 10G Delivery/Experience monitoring interface if required.
- Restrict inbound access by interface—We have updated the PUT /access_control/acl/ API endpoint with the ability to configure inbound Monitoring Point access restrictions by interface. Previously, Access Control Lists (ACLs) applied to all interfaces on the Monitoring Point.
- Classification library enhancements—The Usage Monitoring classification library has been updated with new applications. The new applications supported include:
- Google Sites
- Mitel Suite
- Oman Airlines
- Microsoft WAMan
- Disable default NTP servers—We have added the ability to disable the default NTP servers preconfigured on the Monitoring Point. You can only disable the default servers if you have configured one or more custom NTP servers to replace the defaults. If you delete all custom configured servers, the defaults will be enabled automatically. You can disable or enable the default NTP servers using the NTP Servers screen in the Web Admin interface or via the PUT /ntp/default/ API endpoint.
- Communications security improvements—We have made security improvements to the connection between the Monitoring Point and the AppNeta Performance Manager application. TLS v1.2 connections are now required on APM-Public.
|MP-1457||Reachability||We fixed an issue where the Server Reachability page would display a “Failed to get reachability status” error when there was no proxy configured.|
|MP-1415||Wireless||We fixed an issue where the wireless interface on an m70 Monitoring Point was unable to connect to a wireless access point.|
|MP-1399||SFP module||We fixed an issue where, after upgrading to EMP 12.1.0, r90s with specific SFP modules were unable to connect to APM.|
|MP-1366||API||We fixed an issue with API endpoint PUT /access_control/acl/ where we were not properly validating whether from_port was <= to_port.|
|MP-1349||Virtual MP||We fixed an issue where a virtual Monitoring Point could go offline and not come online again without a manual intervention.|
|MP-1330||MP configuration||We fixed an issue where Monitoring Point interface information written to the “<MP name>.profile.html” file (accessible via USB) was incorrect.|
|MP-1317||curl||We found a workaround to an issue where, when using curl to access API endpoint PUT /access_control/acl/ with a large data set, the request would fail. The workaround is to include “-H ‘Expect: ’” in the curl request.|
|MP-1245||m70||We fixed an issue where an m70 Monitoring Point could require a manual intervention after restart.|
|MP-1241||Memory||We fixed an issue where, over time, available memory on a Monitoring Point could be depleted.|
|MP-1173||IPSec||We fixed an issue where, when using an IPSec tunnel, a Web Connectivity alert was not being triggered even though the IPSec tunnel was down.|
|MP-1159||r90||We fixed an issue where flow compression was not enabled by default on 10G Usage interfaces on r90 Monitoring Points.|
|MP-908||Daily updates||We fixed an issue where daily TCP updates were being made on port 9081.|
|APM-3032||User Resolution||We fixed an issue where the User resolution feature was not working properly after a recent software upgrade.|