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

Open Issues

date_range 12-Aug-22

Learn about the open issues in APM 3.1.0.

  • The reclamation-hold-down attribute in the pool-domain-profile configuration statement is not supported in APM 3.1.0 PR1679496
  • APMi v0 entity connections close unexpectedly with too many pings error. There might be unexpected impact to the system during times of high load while APM reconnects. Workaround: On Junos OS Releases prior to 22.1R1, we recommend setting the grpc keep-alive interval to 60 seconds when interworking with APM. Set the grpc keep-alive interval to 60 by issuing the set system services extension-service request-response grpc grpc-keep-alive 60 statement. PR1681031

  • The warning message "W: Unable to read /etc/apt/sources.list.d/kubernetes.list - open (13: Permission denied)" might display after APM installation. There is no functionality impact due to this error message and you can ignore it. PR1681963

  • Pools synced in drained state never get reclaimed. On resync with a pool in the drain state, the BNG ignores the pool and operates normally as if it did not exist so it never reclaims the pool or cancels the drain, or even allow subscribers to use this lost pool. Workaround is to "restart authentication daemon" on the BNG. PR1680686

footer-navigation