Juniper NETWORKS 3.4.0 Juniper Address Pool Manager Guide User

Juniper Address Pool Manager (APM) is a cloud-native, container-based application running on a Kubernetes cluster that manages address pools in a network.
APM monitors the IPv4 address pools on broadband network gateways (BNGs) in the network.

When the free address utilization drops below a specified threshold on a BNG, APM adds unused prefixes from a centralized pool to the BNG’s address pool.
APM, in cooperation with the BNG, monitors and links address pools in support of dynamic address allocation mechanisms for subscribers.

Ny tombony azo amin'ny APM dia toy izao manaraka izao:

Manatsara ny fahombiazan'ny fampiasana adiresy

Mampihena ny overhead sy ny fahasarotan'ny fanaraha-maso sy ny famatsiana amin'ny alàlan'ny automatique ny fanaraha-maso sy ny famatsiana.
Mamela ny famerenana ny prefix tsy ampiasaina mba hamerenana amin'ny dobo mila azy.
Enables APM to work with the BNG CUPS Controller.
These release notes accompany Juniper Address Pool Manager Release 3.4.0

Fametrahana

Address Pool manager 3.4.0 installation requires the minimum system requirements listed in this section.
FANAMARIHANA: The system requirements listed in Table 1 on page 2 are for a single geographically located installation of Address Pool Manager (APM).
For the system requirements of a multiple geographically located, multiple cluster setup, see Address Pool Manager Installation Guide.
APM installs on a Kubernetes cluster comprised of physical or virtual machines (VMs).
APM has been qualified against the single geographical cluster described in Table 1.
For information on how to install APM, see Address Pool Manager Installation Guide.

Table 1: Single Geographical Cluster Specifications

Sokajy

tsipiriany

sampahom-boaloboka

A single cluster with 3 hybrid nodes.

Kubernetes node

The Kubernetes nodes require the following:

• For the operating system, you can use either of the following:

• Ubuntu 22.04 LTS (for a BBE Cloud setup cluster)

• Red Hat Enterprise Linux CoreOS (RHCOS) 4.15 or later (for an OpenShift Container Platform cluster)

• CPU: 8 or 16 cores.

Use a 16-core node if you plan on running other applications on the cluster (such as the BNG CUPS Controller application).

• Memory: 64 GB

• Storage: 512 GB storage partitioned as 128 GB root (/), 128 GB /var/lib/docker, and 256 GB /mnt/ longhorn(application data

• Kubernetes role: Control plane etcd function and worker node

This specification establishes a cluster that can run APM as well as its companion applications, such as BBE Event Collection and Visualization, and BNG CUPS Controller simultaneously.

Sokajy

tsipiriany

Jump host

The jump host requires the following:

• Operating system: Ubuntu version 22.04 LTS or later

• CPU: 2-core

• Memory: 8 gigabytes (GiB)

• Storage: 128 gigabytes (GiB)

• Installed software:

• Python3-venv

• Helm utility

• Docker utility

• OpenShift CLI. Required if you are using a Red Hat OpenShift Container Platform cluster.

Cluster software

The cluster requires the following software:

• RKE version 1.3.15 (Kubernetes 1.24.4)— Kubernetes distribution

• MetalLB version 0.13.7—Network load balancer

• Keepalived version 2.2.8—Kubelet HA VIP Controller

• Longhorn version 1.2.6—CSI

• Flannel version 0.15.1—CNI

• Registry version 2.8.1—Container registry

• OpenShift version 4.15+—Kubernetes Distribution for RHOCP. Uses compatible versions of Longhorn (CSI), MetalLB, OVN (CNI), and OpenShift Image Registry

Sokajy	tsipiriany
Jump host software	The jump host requires the following software: • Kubectl version 1.28.6+rke2r1—Kubernetes client • Helm version 3.12.3—Kubernetes package manager • Docker-ce version 20.10.21—Docker engine • Docker-ce-cli version 20.10.21—Docker engine CLI • OpenShift version 4.15+—Kubernetes distribution for RHOCP clusters.
fitahirizana	A storage class named jnpr-bbe-storage.
Network load balancer address	One for APMi.
Registry storage	Each APM release requires approximately 3 gigabytes (GiB) of container images.

Fepetra fanampiny

The BNG is a Juniper Networks MX Series router running Junos or a Juniper BNG CUPS Controller (BNG CUPS Controller).

We recommend the following releases:

Junos OS Release 23.4R2-s5 or later
BNG CUPS Controller 24.4R1 or later
For APM, confirm that you have a juniper.net user account with permissions to download the APM software package.
Download and install the APM software from a machine that will not be part of the Kubernetes cluster.

Endri-javatra vaovao sy novana

We have introduced the following new feature in APM 3.4.0.
Support for geographic redundancy—Address Pool Manager can maintain continuous operation across multiple geographically distributed Kubernetes clusters.
By utilizing a multiple cluster architecture managed by Karmada for orchestration and Submariner for inter-cluster networking, APM can failover if a data center outage mitranga.

Olana misokatra

Learn about the open issues in Address Pool Manager 3.4.0
Deleting an entity-match entry does not completely clean up the show apm entity output. PR1874241
An in-service upgrade of the BBE-observer triggers a rollout. As part of an in-service upgrade of the observer microservice, it may appear as if all APM microservices are being upgraded.

The list of container images loaded or pushed in the rollout output indicates that all the microservices are being upgraded, but only the observer microservice is upgraded.
Other container images that are being loaded or pushed are not upgraded. PR1879715
Reverting network load balancer (MetalLB) annotations, followed by performing a rollout, does not reset the external IP address for the APMi.

vahaolana:

When the external address of the APMi that is bound to a particular IPAddressPool through the network load balancer annotations needs to be reverted to use an auto-assign IPAddressPool by removing the annotations, a stop command, and then a rollout command of APM must be performed.
PR1836255

Mangataka fanohanana ara-teknika

Ny fanohanana vokatra ara-teknika dia azo alaina amin'ny alàlan'ny Juniper Networks Technical Assistance Center (JTAC).
Raha mpanjifa manana fifanarahana fanohanana mavitrika Juniper Care na Partner Support Services ianao, na voarakotry ny fiantohana, ary mila fanohanana ara-teknika aorian'ny varotra, dia azonao atao ny miditra amin'ny fitaovana sy loharanon-karenay amin'ny Internet na manokatra tranga miaraka amin'ny JTAC.
JTAC policies—For a complete understanding of our JTAC procedures and policies, review ny JTAC User Guide hita ao amin'ny https://www.juniper.net/us/en/local/pdf/resource-guides/7100059-en.pdf.

Warranty vokatra—For product warranty information, visit https://www.juniper.net/support/warranty/.
JTAC hours of operation—The JTAC centers have resources available 24 hours a day, 7 days a week, 365 days a year.

Fitaovana sy loharanon-karena amin'ny Internet

For quick and easy problem resolution, Juniper Networks has designed an online self-service portal called the Customer Support Center (CSC) that provides you with the following features.
Mitadiava tolotra CSC: https://www.juniper.net/customers/support/
Hitady ny known bugs: https://prsearch.juniper.net/

Mitadiava antontan-taratasy momba ny vokatra: https://www.juniper.net/documentation/
Mitadiava vahaolana ary valio ny fanontaniana amin'ny alàlan'ny Tobim-pahalalanay: https://supportportal.juniper.net/s/knowledge
Ampidino ny kinova farany amin'ny rindrambaiko sy review naoty famoahana: https://www.juniper.net/customers/csc/software/

Mitadiava bulletin teknika momba ny fampandrenesana momba ny fitaovana sy rindrambaiko mifandraika: https://supportportal.juniper.net/s/knowledge
Midira ary mandray anjara amin'ny Forum Community Juniper Networks: https://www.juniper.net/company/communities/
Mamorona fangatahana serivisy amin'ny Internet: https://supportportal.juniper.net/

Mba hanamarinana ny fahazoan-dàlana amin'ny serivisy amin'ny alàlan'ny nomeraon'ny vokatra, ampiasao ny Fitaovana Serial Number Entitlement (SNE): https://entitlementsearch.juniper.net/entitlementsearch/

Mamorona fangatahana serivisy miaraka amin'ny JTAC

Azonao atao ny mamorona fangatahana serivisy miaraka amin'ny JTAC amin'ny Web na an-telefaonina.
FITSIDIHANA https://support.juniper.net/support/requesting-support/

Call 1888314JTAC (18883145822 toll-free in the USA, Canada, and Mexico).
Ho an'ny safidy iraisam-pirenena na antso mivantana any amin'ny firenena tsy misy laharana maimaim-poana, jereo https://support.juniper.net/support/requesting-support/.
Juniper Networks, ny logo Juniper Networks, Juniper, ary Junos dia mari-pamantarana voasoratra ao amin'ny Juniper Networks, Inc. any Etazonia sy any amin'ny firenena hafa.

All other trademarks, service marks, registered marks, or registered service marks are the property of their respective owners.
Juniper Networks dia tsy tompon'andraikitra amin'ny tsy fahatomombanana amin'ity antontan-taratasy ity. Ny Juniper Networks dia manana zo hanova, hanova, hamindra, na hanova ity publication ity tsy misy fampandrenesana.

Fanontaniana matetika

F: Inona no tokony hataoko raha sendra olana aho mandritra ny fametrahana?
- A: Refer to the Open Issues section in the user manual for troubleshooting tips or contact technical support for assistance.
Q: Can I run other applications on the same Kubernetes cluster as APM?
- A: Yes, you can run other applications on the cluster, but ensure to use a 16-core node as per the specifications.

Documents / Loharano

Juniper NETWORKS 3.4.0 Juniper Address Pool Manager [pdf] Torolàlana ho an'ny mpampiasa
APM-3-4-0, 3.4.0 Juniper Address Pool Manager, 3.4.0, Juniper Address Pool Manager, Address Pool Manager, Pool Manager, Manager

References

User Manual

Juniper NETWORKS 3.4.0 Juniper Address Pool Manager

Product Information

Torolàlana momba ny fampiasana vokatra

Sava lalana