Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Announcement: Try the Ask AI chatbot for answers to your technical questions about Juniper products and solutions.

close
header-navigation
keyboard_arrow_up
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

Resolved Issues

date_range 02-Jul-24

The following issues are resolved in Address Pool Manager 3.2.1:

  • APM does not accurately rename a partition which has a prefix. PR1773395

  • If the node hosting Redis primary pod shuts down, it can cause APM microservices such as addr-man, ent-man, or prov-man to become unresponsive. Workaround is to restart mgmt pod or restart apm-mgmt daemon from inside the mgmt pod/CLI by issuing. PR1773337

  • The apm logs command fails when multiple services are provided as arguments. PR1774774

The following issue is resolved in Address Pool Manager 3.2.2:

Configuring APM through the NETCONF SSH interface caused the apmd process in the apm-mgmt microservice to crash. As a result, configuration changes could not be committed through the NETCONF SSH interface. The workaround was to use the apm cli command to modify the APM configuration. The fix resolves the crashes to allow configuration commits to be made through the NETCONF SSH interface. PR1816290

footer-navigation